Home   Package List   Routine Alphabetical List   Global Alphabetical List   FileMan Files List   FileMan Sub-Files List   Package Component Lists   Package-Namespace Mapping  
Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All
Print Page as PDF
Global: ^XMB(3.9

Package: MailMan

Global: ^XMB(3.9


Information

FileMan FileNo FileMan Filename Package
3.9 MESSAGE MailMan

Description

Directly Accessed By Routines, Total: 281

Package Total Routines
MailMan 123 ADDRESSED TO    RECIPIENT    XMA11A    XMA2B    XMA2R    XMA3    XMA30    XMA32
XMAH    XMAH1    XMAPBLOB    XMAPHOST    XMCSIZE    XMCTLK    XMDIRRCV    XMJMA
XMJMC    XMJMCODE    XMJMD    XMJMFA    XMJMFB    XMJMFC    XMJML    XMJMLN
XMJMLR    XMJMOI    XMJMOI1    XMJMOR    XMJMP    XMJMQ    XMJMQ1    XMJMR
XMJMS    XMKP    XMLSWP    XMP    XMRENT    XMRPOP    XMTDF    XMTDL
XMTDL1    XMTDO    XMTDT    XMUT41    XMUT4C    XMUT5Q    XMUTERM2    XMVVITAE
XMXEDIT    XMXGRP    XMXPRT    XMXREPLY    XMXSEC1    XMXSEC2    XMXTO    XMXUTIL
XMXUTIL1    XMXUTIL2    XMXUTIL3    XMXUTIL4    ^XMB(3.73    ^XMB(3.9    LATER DELIVERY TO    MESSAGE
OBJECTS - OTHER BODY PARTS    XMA2    XMA32A    XMBBLOB    XMD    XMFAX    XMGAPI0    XMGAPI2
XMJBL    XMJBM    XMJBN    XMJERR    XMJMLR1    XMJMP1    XMJMP2    XMJMR1
XMJMRO    XML4CRC    XMLSWP0    XMLSWP2    XMP2    XMP2A    XMP3    XMPC
XMPG    XMPH    XMPSEC    XMR    XMR1    XMR3    XMR3A    XMRPCTS0
XMRPCTS1    XMRPCTSA    XMS    XMS0BLOB    XMS1    XMS2    XMS3    XMTDL2
XMUPIN    XMUT1    XMUT1A    XMUT2    XMUT4    XMUTERM    XMVGRP    XMXANSER
XMXBSKT    XMXBULL    XMXGRP1    XMXLIST1    XMXLIST2    XMXMSGS    XMXMSGS1    XMXMSGS2
XMXPARM    XMXSEC    XMXSEND    
CMOP 23 PSXACT    PSXCOSTU    PSXDODAC    PSXDODB    PSXDODH    PSXDQUE    PSXDQUEC    PSXERR1
PSXMISC    PSXMSGS    PSXNOTE    PSXPURG1    PSXRCVRY    PSXRECV    PSXRECV1    PSXRSYU
PSXRTN    PSXRTR    PSXRTRA1    PSXRTRAN    PSXSITE    PSXVEND    PSXVND    
IFCAP 16 PRC5B4    PRCFAIS    PRCHMESE    PRCHMESH    PRCHMESP    PRCHMHL1    PRCHMHLS    PRCHMOL1
PRCHMOLS    PRCHMOP    PRCHMSE    PRCHMSHA    PRCHMSPD    PRCOESE1    PRCOINV1    PRCOSS5
Patient Data Exchange 14 VAQADM2    VAQCON    VAQCON0    VAQCON1    VAQCON2    VAQCON3    VAQCON4    VAQCON5
VAQCON6    VAQCON7    VAQCON8    VAQCON94    VAQCON97    VAQCON99    
Engineering 11 ENEXPT    ENPLSV    ENPLSV1    ENPLSV2    ENPLSV3    ENPLSV4    ENPLX1    ENPLX2
ENPLX3    ENPLX4    ENWO2    
Kernel 9 XIPSRVR    XPDIB    XPDIPM    XPDPINIT    XPDTP    XQSRV    XQSRV1    XUPCSRVR
XUSERNEW    
Registration 9 DG737PST    DGPTFTR    DGPTFTR3    DGPTFVC    DGPTR2    DGPTR4    DGPTRI2    DGPTRI4
DGPTRPO    
Accounts Receivable 8 RCCPCML    RCDPXPAY    RCRCAT    RCRCREC    RCRCSRV    RCRCVXM    RCRJR    RCTCSJS
Network Health Exchange 7 AFJXALRT    AFJXMABX    AFJXMBOX    AFJXPNHT    AFJXPNHX    AFJXSFAL    AFJXVER    
Clinical Reminders 5 PXRMEXCS    PXRMEXMM    PXRMG2M1    PXRMMSG    PXRMP19A    
Integrated Billing 5 IB20P150    IB20P336    IBARXMA    IBCIUT6    IBCNHSRV    
Asists 4 OOPSDOL    OOPSDOLX    OOPSNDB    OOPSNDBX    
Health Level Seven 4 HLEVSRV0    HLEVSRV1    HLLP    HLTRANS    
PAID 3 PRSATH    PRSDERR    PRSDPROC    
Radiology Nuclear Medicine 3 RAHLO4    RANEWPRO    RAONDEM    
Remote Order Entry System 3 RMPFED    RMPFQM    RMPFQT1    
Scheduling 3 SD53430P    SDHPIB    SDWLIFT    
Toolkit 3 XQABELOG    XTPMKPCF    XTPMKPTC    
EEO Complaint Tracking 2 EEOEEXE    EEOEXE1    
Functional Independence 2 RMIMRP    RMIMV    
HINQ 2 DVBHDBA1    DVBHQUS    
Order Entry Results Reporting 2 ORINQIV    ORWOD    
Problem List 2 GMPLP37I    GMPLUTL4    
Adverse Reaction Tracking 1 GMRAFA    
Automated Medical Information Exchange 1 DVBAPOST    
Consult Request Tracking 1 GMRCYP69    
Enrollment Application System 1 EASEZW    
Fee Basis 1 FBAAV01    
Lab Service 1 LRRMM    
ODS 1 A1B2T4    
Oncology 1 ONCOSCT3    
VA FileMan 1 DIFGO    
Voluntary Timekeeping 1 ABSVMS1    

Accessed By FileMan Db Calls, Total: 14

Package Total Routines
MailMan 11 XMJMFA    XMJMFC    XMJMSO    XMP    XMP2    XMPG    XMPH    XMXEDIT
XMXLIST    XMXSEND    XMXUTIL    
Mental Health 1 YTQAPI12    
ODS 1 A1B2T4    
Radiology Nuclear Medicine 1 RAHLO4    

Pointed To By FileMan Files, Total: 20

Package Total FileMan Files
MailMan 4 MAILBOX(#3.7)[57#3.702(.01)]
MESSAGES TO BE NEW AT A LATER DATE(#3.73)[2]    MESSAGE(#3.9)[1.35#3.9001(.01)]    MESSAGE STATISTICS(#4.2999)[2]    
Registration 3 PTF RELEASE(#45.83)[#45.831(2)]    PTF TRANSACTION REQUEST LOG(#45.87)[.03]    PTF(#45)[#45.04(3)]    
Remote Order Entry System 3 STATION ORDER(#791810)[#791810.0201(.02)]    TRANSMISSION BATCH(#791812)[.06]    ROES ELIGIBILITY CONFIRMATION(#791814)[1.02]    
Integrated Billing 2 HMS EXTRACT FILE STATUS(#355.35)[#355.3503(.01)#355.35051(.01)]    HMS RESULT FILE STATUS(#355.351)[#355.35103(.01)#355.35111(.01)]    
Barcode Medication Administration 1 BCMA UNABLE TO SCAN LOG(#53.77)[.07]    
Functional Independence 1 FUNCTIONAL INDEPENDENCE MEASUREMENT RECORD(#783)[.17]    
HINQ 1 HINQ SUSPENSE(#395.5)[7]    
IFCAP 1 INVOICE TRACKING(#421.5)[65]    
Order Entry Results Reporting 1 ORDER(#100)[#100.008(32)]    
PAID 1 TIME & ATTENDANCE RECORDS(#458)[#458.03(.01)]    
Quasar 1 AUDIOMETRIC EXAM DATA(#509850.9)[.13]    
VA FileMan 1 FILEGRAM HISTORY(#1.12)[.06]    

Pointer To FileMan Files, Total: 4

Package Total FileMan Files
MailMan 2 DOMAIN(#4.2)[#3.91(6)]    MESSAGE(#3.9)[1.35#3.9001(.01)]    
Imaging 1 IMAGE(#2005)[#3.92005(.01)]    
Kernel 1 NEW PERSON(#200)[#3.91(8.01)#3.914(2)]    

Fields, Total: 25

Field # Name Loc Type Details
.001 NUMBER NUMBER

  • INPUT TRANSFORM:  K:+X'=X!(X>999999999999999)!(X<0)!(X?.E1"."1N.N) X
  • LAST EDITED:  MAR 25, 2002
  • HELP-PROMPT:  Type a Number between 0 and 999999999999999, 0 Decimal Digits
  • DESCRIPTION:  This is the unique number which is assigned to a message at the time it is entered into the system. Messages are numbered sequentially. Numbers may be re-used if numbers get too big. See field 17.1, MAX DIGITS FOR
    MESSAGE NUMBER in file 4.3, MailMan Site Parameters, for more information.
    Numbers appear in the "Query" listing for the message, as @, where  is the message number for this message, and  is the name of the domain, as defined in the file 4.3.  This
    combination of number and domain name uniquely identifies ALL messages in the mailman network, and editing control is such that no two copies of the message at different domains are different; the message is either
    identical or missing.
    UNEDITABLE
.01 SUBJECT 0;1 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) S X=$$STRIP^XMXUTIL1(X),X=$$MAXBLANK^XMXUTIL1(X) K:$L(X)>65!($L(X)<3) X I $D(X),X["^" S X=$$ENCODEUP^XMXUTIL1(X)
  • OUTPUT TRANSFORM:  S:Y["~U~" Y=$$DECODEUP^XMXUTIL1(Y)
  • LAST EDITED:  MAY 26, 1998
  • HELP-PROMPT:  Answer must be 3-65 characters in length.
  • DESCRIPTION:  
    This is the subject of the message, and is shown whenever the message is displayed.  Leading and trailing blanks are deleted.  Any sequence of 3 or more blanks is reduced to 2 blanks.
  • TECHNICAL DESCR:  
    If the message happens to be a local reply, the message subject will be "R" followed by the message number of the original message for which this is a response.  This text contains ~U~ if the subject contains an up-arrow.
  • DELETE TEST:  1,0)= I 1 W *7," DELETION ONLY ALLOWED THROUGH MANAGER 'PURGE'"
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
  • CROSS-REFERENCE:  3.9^B
    1)= S ^XMB(3.9,"B",$E(X,1,30),DA)=""
    2)= K ^XMB(3.9,"B",$E(X,1,30),DA)
1 FROM 0;2 FREE TEXT
************************REQUIRED FIELD************************

  • INPUT TRANSFORM:  K:$L(X)>70!($L(X)<0) X
  • LAST EDITED:  AUG 13, 1997
  • HELP-PROMPT:  Answer must be 0-70 characters in length.
  • DESCRIPTION:  This is who the message is from. In the case of a local message, this is the internal entry number of the user in the NEW PERSON file. In the case of a networked message, it is the user's full network address, in the
    format .
  • TECHNICAL DESCR:  
    In a future patch, the field should be made longer, perhaps to 99.
    UNEDITABLE
1.1 SENDER 0;4 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<0) X
  • LAST EDITED:  OCT 04, 1985
  • HELP-PROMPT:  ANSWER MUST BE 0-30 CHARACTERS IN LENGTH
  • DESCRIPTION:  If the message is sent by a surrogate, this field holds the surrogate's identity.
    It is displayed on the message header in parentheses, with the text SENDER: preceding the sender's name.
    UNEDITABLE
1.3 CONFIRMATION REQUESTED? 0;5 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  JUL 28, 1997
  • DESCRIPTION:  
    This specifies whether or not the sender of a message will get an acknowledgement when the message is read by the recipient.
1.35 ORIGINAL MESSAGE 0;8 POINTER TO MESSAGE FILE (#3.9) MESSAGE(#3.9)

  • LAST EDITED:  JUL 22, 1988
  • DESCRIPTION:  
    This field is used for responses only.  If this message is a response, this field points to the original message.
1.4 SENT DATE/TIME 0;3 DATE

  • INPUT TRANSFORM:  S %DT="ETXR" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  JUL 30, 1997
  • DESCRIPTION:  This is the date and time at which this message was sent. It relates to the completion of the sending process, not the beginning, as previous versions did. Initiation and initial sending can be separated by days, e.g.
    due to equipment failure or illness of the sender, the time of the first send, rather than the time message editing began, is retained.
  • TECHNICAL DESCR:  In a future patch, as remote messages arrive, their date should be converted from clear text to FM, using CONVERT^XMA32A. If conversion is not possible, the current date/time should be used. Currently, the DD to the
    contrary, the clear text version of the date of the remote message is placed in this field.
1.6 PURGE DATE 0;6 DATE

  • INPUT TRANSFORM:  S %DT="FEST" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  OCT 25, 2000
  • HELP-PROMPT:  Enter a date in the future when this message should be purged.
  • DESCRIPTION:  
    This message will be set for all recipients to automatically delete on this date.
  • TECHNICAL DESCR:  
    As the message is delivered to each recipient, the AUTOMATIC DELETE DATE for the message in the recipient's basket is set to this purge date.  The recipient is free, of course, to change the AUTOMATIC DELETE DATE.
  • NOTES:  XXXX--CAN'T BE ALTERED EXCEPT BY PROGRAMMER
1.7 MESSAGE TYPE 0;7 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>3!($L(X)<1) X
  • LAST EDITED:  APR 22, 2002
  • HELP-PROMPT:  Answer must be 1-3 characters in length.
  • DESCRIPTION:  This field enables MailMan to differentiate among types of messages. Spooled documents must be handled partially through an interface to the 'spooler'. Word processing documents are handled differently from ordinary
    messages.
    This field is set within MailMan to any combination of the valid codes, e.g. "XPB" would indicate a PackMan message which includes a BLOB, and marked by the user for priority delivery.
    TYPE   MEANING
    D      Document
    S      Spooled Document
    X      DIFROM (PackMan) Installable Message
    O      ODIF Format
    B      BLOB (eg. MIME) contained within
    K      KIDS Distribution
    P      Priority
1.8 SCRAMBLE HINT 0;10 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>40!($L(X)<1) X
  • LAST EDITED:  FEB 25, 1997
  • HELP-PROMPT:  Answer must be 1-40 characters in length.
  • DESCRIPTION:  A scramble hint is used to suggest to the reader what the scramble password is. Since the password is not recoverable after it is entered, and since the reader must supply the password in order to read the message, the
    hint can be a helpful reminder to the reader of the message.
    The hint will be shown to the reader just before the reader is asked to enter the password.
1.85 SCRAMBLE KEY K;E1,200 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>200!($L(X)<3) X
  • LAST EDITED:  FEB 25, 1997
  • HELP-PROMPT:  Answer must be 3-20 characters in length.
  • DESCRIPTION:  
    The scramble password is a secret code which must be entered by the reader in order to see the message.  Upper and lower case characters are treated the same.  (The password is not case sensitive.)
  • TECHNICAL DESCR:  
    The key is stored in scrambled form.  First character=1 indicates that scrambling is done in standard bazaries cylinder form.  Other first characters are reserved.
    UNEDITABLE
1.95 CLOSED MESSAGE? 0;9 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  APR 19, 1985
  • HELP-PROMPT:  If closed, message may not be forwarded or copied by recipients.
  • DESCRIPTION:  
    This field, if set to 'yes', means that recipients may not forward or copy the message.
1.96 CONFIDENTIAL? 0;11 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  APR 19, 1985
  • HELP-PROMPT:  If confidential, surrogates may not read message.
  • DESCRIPTION:  
    This field, if set to "yes", means that surrogates of the recipients may not read this message.
1.97 INFORMATION ONLY? 0;12 SET
  • 'y' FOR YES;
  • 'n' FOR NO;

  • LAST EDITED:  FEB 10, 1986
  • HELP-PROMPT:  If "YES", the message will be considered "INFORMATION ONLY" for all recipients.
  • DESCRIPTION:  This field, if set to "YES", will cause all recipients to be considered "INFORMATION ONLY", which disables responses to the message.
    If a sender wishes to individually restrict responses, "INFO:" before the recipient's names will restrict their responses.
    Messages which are broadcast (by naming a recipient "*"), are automatically set to INFORMATION ONLY.
2 RECIPIENT 1;0 Multiple #3.91 3.91

  • DESCRIPTION:  This is a list of all recipients of this message. MailMan automatically tracks each recipient's progress through the response chain, when they last read it, who forwarded or copied the message, etc. This information is
    displayed with the Query option after reading the message.
3 TEXT 2;0 WORD-PROCESSING #3.92

  • DESCRIPTION:  
    This is the actual text of the message.  It is stored without the wrap-around logic, in a line-by-line format.
8 RESPONSE 3;0 POINTER Multiple #3.9001 3.9001

  • DESCRIPTION:  
    This is a list of the responses to the message.  Each response is a separate message, with a subject of "R" followed by this response number.
9 INCOMING MESSAGE ID 5;1 FREE TEXT

  • INPUT TRANSFORM:  K:X[""""!($A(X)=45) X I $D(X) K:$L(X)>110!($L(X)<2) X
  • LAST EDITED:  FEB 18, 1999
  • HELP-PROMPT:  Answer must be 2-110 characters in length.
  • DESCRIPTION:  If this is a message which has been received from a remote site, its Message ID, as contained in the message header, is stored here.
    Its format is usually .
    UNEDITABLE
  • CROSS-REFERENCE:  3.9^AI^MUMPS
    1)= I X["@",$L($P(X,"@",1)),$L($P(X,"@",2)) S ^XMBX(3.9,"AI",$E($P(X,"@",2),1,64),$E($P(X,"@",1),1,64),DA)=DT
    2)= Q
    This cross reference keeps track of messages that have already been received from other sites.
    This index is used to retrieve remote messages which have been transmitted from other domains.  For example, if message 123 from loma-linda has been sent to another site, that other site could inquire against message ID
    "loma-linda@123", to find out if the message had been received yet.
    This index is also used to prevent messages from looping around the network.  The MailMan receiver will not allow the same message to be received twice at the same site.
9.5 IN REPLY TO REMOTE MESSAGE ID IN;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>110!($L(X)<2) X
  • LAST EDITED:  JUL 28, 1997
  • HELP-PROMPT:  Answer must be 2-110 characters in length.
  • DESCRIPTION:  
    When a user responds to a message from a remote user, the INCOMING MESSAGE ID (field 9) of the original message is copied and placed here.  Its format is .
10 ADDRESSED TO 6;0 Multiple #3.911 3.911

  • DESCRIPTION:  There are two parts to addressing a message. The first part occurs when the user enters the 'names' (addresses) to which the message will be sent. The second part occurs when Mail Groups are 'Expanded'. The 'names' the
    user enters will be recorded here.  The expanded list is in a multiple titled 'Recipients'.  Old messages may not have 'ADDRESSED TO' data if they were originated before MailMan recorded these two pieces of data
    separately.
14 LATER DELIVERY TO 7;0 Multiple #3.914 3.914
21 DELIVERY BASKET .5;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>30!($L(X)<2) X
  • LAST EDITED:  MAY 13, 1998
  • HELP-PROMPT:  Answer must be 2-30 characters in length.
  • DESCRIPTION:  
    The Delivery Basket is the basket into which the message will be delivered for each recipient.  It overrides any filters.
31 LOCAL CREATE DATE .6;1 DATE

  • INPUT TRANSFORM:  S %DT="EX" D ^%DT S X=Y K:Y<1 X
  • LAST EDITED:  SEP 17, 1998
  • HELP-PROMPT:  Enter the date this message was created.
  • DESCRIPTION:  
    This is the date this message was created and added to the message file.  It is used, via the "C" xref, to select messages for purging.
  • CROSS-REFERENCE:  3.9^C
    1)= S ^XMB(3.9,"C",$E(X,1,30),DA)=""
    2)= K ^XMB(3.9,"C",$E(X,1,30),DA)
    This xref is used by the date purge and by the unreferenced messages purge.
41 ENVELOPE FROM .7;1 FREE TEXT

  • INPUT TRANSFORM:  K:$L(X)>99!($L(X)<1) X
  • LAST EDITED:  OCT 15, 1998
  • HELP-PROMPT:  Answer must be 1-99 characters in length.
  • DESCRIPTION:  
    This is the 'from' as stated in the message envelope on an incoming network message.  HELO ...  MAIL FROM: RCPT TO: ...
2005 OBJECTS - OTHER BODY PARTS 2005;0 POINTER Multiple #3.92005 3.92005

  • DESCRIPTION:  
    Pointers to the Object file are stored here as attachments to multimedia messages.
  • TECHNICAL DESCR:  
    The pointers in this field point at the OBJECT file (2005).

ICR, Total: 6

ICR LINK Subscribing Package(s) Fields Referenced Description
ICR #247
  • REMOTE ORDER/ENTRY SYSTEM
  • PCE PATIENT CARE ENCOUNTER
  • ICR #1034
  • VA FILEMAN
  • In ^DIFGO we display the subject online from the 0 nodeof message fileIn ^DIFGO we $O through the text lines in the message atone place to display the text, and in another place to process the Filegramcontents.
    ICR #2860
  • RADIOLOGY/NUCLEAR MEDICINE
  • DATE ENTERED (1.4).
    Access: Read w/Fileman

    ICR #3242
  • NATIONAL DRUG FILE
  • TEXT (3).
    Access: Direct Global Read & w/Fileman

    ICR #5526
  • SPINAL CORD DYSFUNCTION
  • (5).
    Access: Direct Global Read & w/Fileman

    "B" cross-reference on the SUBJECT field.First line of the TEXT multiple."C" cross-reference of the RECIPIENT sub-file.
    ICR #10113 TEXT (3).
    Access: Direct Global Write & w/Fileman

    FROM (1).
    Access: Read w/Fileman

    TEXT (3).
    Access: Write w/Fileman

    External References

    Name Field # of Occurrence
    ^%DT 1.4+1, 1.6+1, 31+1
    $$DECODEUP^XMXUTIL1 .01OT+1
    $$ENCODEUP^XMXUTIL1 .01+1
    $$MAXBLANK^XMXUTIL1 .01+1
    $$STRIP^XMXUTIL1 .01+1

    Global Variables Directly Accessed

    Name Line Occurrences  (* Changed,  ! Killed)
    ^XMB(3.9 - [#3.9] IXAFSL+1*, IXAFKL+1!, IXAFKEIC+1!, .01(XREF 1S), .01(XREF 1K), 31(XREF 1S), 31(XREF 1K)
    ^XMBX(3.9 9(XREF 1S)

    Local Variables

    Legend:

    >> Not killed explicitly
    * Changed
    ! Killed
    ~ Newed

    Name Field # of Occurrence
    >> %DT 1.4+1*, 1.6+1*, 31+1*
    >> DA IXAFSL+1, IXAFKL+1, .01(XREF 1S), .01(XREF 1K), 9(XREF 1S), 31(XREF 1S), 31(XREF 1K)
    >> DA(1 IXAFSL+1, IXAFKL+1
    DT 9(XREF 1S)
    X IXAFSL+1, IXAFSCC+1*, IXAFKL+1, .001+1!, .01+1!*, .01(XREF 1S), .01(XREF 1K), 1+1!, 1.1+1!, 1.4+1*!
    , 1.6+1*!, 1.7+1!, 1.8+1!, 1.85+1!, 9+1!, 9(XREF 1S), 9.5+1!, 21+1!, 31+1*!, 31(XREF 1S)
    31(XREF 1K), 41+1!
    >> Y .01OT+1*, 1.4+1, 1.6+1, 31+1
    >> Y(0 .01OT+1*
    Info |  Desc |  Directly Accessed By Routines |  Accessed By FileMan Db Calls |  Pointed To By FileMan Files |  Pointer To FileMan Files |  Fields |  ICR |  Found Entries |  External References |  Global Variables Directly Accessed |  Local Variables |  All