{"aaData": [["1", "XQHELP", "USING THE 'Help Processor' OPTION\n", "", "", "\nThe Help processor is a frame-oriented display system which allows\n \n [DISPLAY/EDIT] - Displays the text of a help frame, and allows for the\n edit of the name, header, text, or related frames.\n \n [CROSS REFERENCE] - Lists all the help frames for a specified package,\n showing parent help frames, linked to menu option,\n and invoking routine.\n \n [LIST] - Lists the help frames in several different formats.\n \nusers and programmers to access and manage help text.\n [MORE OPTIONS]...\n \nThe system is driven off of the [HELP FRAME FILE].\n \nThere are several [LINKS] which will cause the help text to be\ndisplayed to the user. The system is interactive, and the user may\nselect which topic he/she wishes furthur information on.\nThe Help Frame Processor Menu contains the following options:\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["10", "XQHELP-DISP", "USING THE 'Display/Edit Help Frame' OPTION\n", "", "", "\nThis option is used to view help frames, and edit them, if the\nOther responses to the 'Select Action' prompt will enable you to\ndisplay a list of keywords and topics, switch from brackets to reverse\nvideo and vice versa, refresh the screen, and edit it, providing\nedit privileges are established.\n \n[BUILDING] a new help frame can be done by responding with a new name\nto the first 'HELP FRAME' prompt.\nuser has [EDIT PRIVILEGES].\n \nThe text of the frame is displayed, with the keywords highlighted\nin reverse video or brackets. A keyword indicates that there is more\ndetailed information about the topic indicated. Entering that keyword\nin response to the 'Select Action' prompt will display the frame\ncontaining the related information.\n \n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["100", "XUDOC SPOOL USE5", "MAKING SPOOL DOCUMENTS INTO MAIL MESSAGES\n", "", "", "\nThis option provides a way to use your spooled document just as you would\nrecently delivered ones to find your spool document now as a mail message.\n \nNote: Contact your IRM representative if you are not able to use this\noption; special access privileges are required.\nuse a mail message. All the MailMan functions would be available. You\ncould copy and edit the text. You could forward the message locally or\nacross the network. If you use this option, take care not to abuse the\nprivilege. Keep the number and size of your documents down to a minimum.\n \nWhen using this option, pick the spool document that you would like\nto make into a mail message and it will be instantly transformed! Now go\nto your MailMan Menu and 'Read' your IN basket mailbox. Scan the most\n
\n\n", "", "", "1992-04-15 11:39:00\n", "", "USER,ONE\n", "", ""], ["1000", "XM-U-B-NAVIGATE CLASSIC", "READING A MESSAGE AND NAVIGATING IN THE CLASSIC READER\n", "", "", "\n \nbecome the default.\n \nIf you enter a sequence number that doesn't exist, the message whose\nsequence number is closest to it becomes the default message.\n \nYou could also enter the internal message ID (the long number appearing in\nbrackets) of a message. Once you've read it, the next message after that\nwill become the default. If the message exists in another basket, you will\nbe moved from reading your current basket to reading the basket where the\nmessage exists. If the message is not in any basket, but is still on the\nThere are several ways to read messages and navigate in the Classic Reader.\nsystem, it will be put in your basket, as the last message.\n \nOne is to just press <Enter> to read the default message presented to you\nat the prompt. Once you've read it, the next message in the basket will\nbecome the default.\n \nYou could also enter its sequence number to go directly to the message\nyou wish to read. Once you've read it, the next message after that will\n
\n\n", "", "", "1998-12-28 08:40:00\n", "", "USER,ONE\n", "", ""], ["1001", "XM-U-BO-CLASSIC-2", "CLASSIC READER BASKET MESSAGE ACTIONS (CONTINUED)\n", "", "", "\n \n ?string Search for messages in this basket whose subject [CONTAINS]\n a certain keyword or phrase.\n \n ??string Search for messages anywhere on the system, whether in your\n mailbox or not, which you once sent or received, whose subject\n [BEGINS WITH] the specified string.\nEnter:\n \n [C] Change the name of this basket.\n I Ignore this message and go to the next one in this basket.\n [N] List only the new messages in this basket.\n [Q] Query (search for) messages in this basket.\n [R] Resequence messages in this basket.\n \n
\n\n", "\n- \n\n
\n", "", "1999-12-13 13:22:00\n", "", "USER,ONE\n", "", ""], ["1002", "XM-U-BO-FULL SCREEN", "FULL SCREEN READER BASKET MESSAGE ACTIONS\n", "", "", "\n \n [D] Delete messages.\n [F] Forward messages.\n [FI] Filter messages.\n [L] Later messages.\n [P] or [H] Print messages with or without a header.\n [NT] New Toggle messages.\n [S] Save messages to another basket.\n [T] Terminate messages.\n [V] Set a Vaporize date for messages.\n [X] Toggle transmit priority in remote message queues. (POSTMASTER only)\nEnter ^ to exit, or enter one of the [PAGE] commands to see more messages,\n \n [MORE]...\nor enter one of the following:\n n Read message n, where n is a sequence number in this basket or\n an internal message ID of any message on the system.\n \nThe following commands act on one or more messages in this basket.\nYou can [SELECT] the messages prior to entering the command or \nspecify a [RANGE] of messages after entering the command.\n
\n\n", "\n- \n\n
\n", "", "2000-06-12 07:14:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["1003", "XM-U-BO-FULL SCREEN-2", "FULL SCREEN READER BASKET MESSAGE ACTIONS (CONTINUED)\n", "", "", "\n \n ?string Search for messages in this basket whose subject [CONTAINS]\n a certain keyword or phrase.\n \n ??string Search for messages anywhere on the system, whether in your\n mailbox or not, which you once sent or received, whose subject\n [BEGINS WITH] the specified string.\nEnter:\n \n [C] Change the name of this basket.\n [CD] Change detail. (Toggle between [SUMMARY] and [DETAILED] display.)\n [N] List only the new messages in this basket.\n [Q] Query (search for) messages in this basket.\n [R] Resequence messages in this basket.\n \n
\n\n", "\n- \n\n
\n", "", "1999-03-19 14:56:00\n", "", "USER,ONE\n", "", ""], ["1004", "XM-U-M-CHOOSE SELECT", "SELECTING MESSAGES\n", "", "", "\n \n .* Select all of the messages in the list.\n \nMessages that you've selected are marked by a '>'.\n \nThe selections are cumulative. This means that once you have selected some\nmessages, you can select some more. (Subsequent selections do not wipe out\nprevious ones.) This is good, because if the messages you want to select are\non different pages, you can select the ones on one page and then go ahead and\nselect more on other pages.\n \nSelect messages for subsequent action (e.g., delete, filter, forward, later,\n [MORE]...\nprint, save, or terminate) by entering a period and then the message sequence\nnumber(s) in any of the following ways: \n \n .n Select one message. For example: .5\n .n-m,a,c-d Select several messages. For example: .1,5 or .1-9 or\n .1-3,5,8-10\n .n- Select all messages from this one onward. For example: .6-\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 16:07:00\n", "", "USER,ONE\n", "", ""], ["1005", "XM-U-M-CHOOSE SELECT-2", "SELECTING MESSAGES (CONTINUED)\n", "", "", "\n \n \nMessages that you've deselected are no longer marked by a '>'.\n \nThe deselections are also cumulative. You can select and deselect as much as\nyou want. Knock yourself out.\n \nOnce you've selected some messages, additional commands become available:\n \n [O] Opposite selection toggle.\n [Z] Zoom toggle.\nAfter you've selected messages, you may decide to deselect some of them.\nYou can do this by entering a period, followed by the minus sign, and then\nthe message sequence numbers(s) in any of the following ways:\n \n .-n DeSelect one message. For example: .-5\n .-n-m,a,c-d DeSelect several messages. For example: .-1,5 or .-1-3,5,8-10\n .-n- DeSelect all messages from this one onward. For example: .-6-\n .-* DeSelect all of the messages in the list.\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 11:04:00\n", "", "USER,ONE\n", "", ""], ["1006", "XM-U-B-NAVIGATE FULL SCREEN", "READING A MESSAGE AND NAVIGATING IN THE FULL SCREEN READER\n", "", "", "\n \npage with that message on it. If the message exists in a different basket, you\nwon't stay in that basket, as you would with the Classic Reader; you'll return\nto the page where you were. \n \nPress <Enter> to go to the next page, or enter:\n +n Page forward n pages. (+ is the same as +1)\n If +n is very high (like +999), you'll go to the last page.\n If you're on the last page and you page forward, you'll be given\n the option of going to the first page or exiting the list.\n -n Page backward n pages. (- is the same as -1)\nThere are several ways to read messages and navigate in the Full Screen Reader.\n 0 (zero) Go to the first page.\n = Refresh the display of the current page.\n\nEnter the sequence number of a message, and you'll read that message. Then\nyou'll be on the page with that sequence number in it. If the sequence number\ndoes not exist, you'll be on the page where it would be if it did exist. \n \nEnter the internal message ID (the long number appearing in brackets) of any\nmessage on the system, and you'll read that message. Then you'll be on the\n
\n\n", "", "", "1999-07-22 09:12:00\n", "", "USER,ONE\n", "", ""], ["1007", "XM-U-M-QUERY GENERAL", "GENERAL QUERY ON A MESSAGE\n", "", "", "\n \nforwarded at a later date. These addressees were targeted for [STAGGERED]\ndelivery.\n \nTo query a message for general addressee information, enter a 'Q' at the\n'Enter message action' prompt.\nYou can use the Query action code (i.e., 'Q') to inquire about general\naddressee information on a message.\n \nWhen doing a query on a message, besides the [BASIC] information, MailMan\nwill display a list of the addressees to whom the user addressed the message.\nAddressees include local and remote users and any mail groups.\n \nMailMan also displays a list of addresses to whom the message will be\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:31:00\n", "", "USER,ONE\n", "", ""], ["1008", "XM-U-M-QUERY DETAILED", "DETAILED QUERY ON A MESSAGE\n", "", "", "\n \nAlso, when you do a detailed query on a message that was sent to you and\nyou have your mail automatically forwarded to a remote address, the query\nclearly shows that you are the one who forwarded the message to that\naddress. \n \nTo query a message for detailed recipient information, enter a 'QD' at the\n'Enter message action' prompt.\nYou can use the Query Detailed action code (i.e., 'QD') to retrieve\ndetailed information for each recipient of a message.\n \nWhen doing a detailed query on a message, besides the [BASIC] information,\nMailMan displays detailed recipient information for all [LOCAL] and\n[REMOTE] users who are recipients of the message (including all members of\nany mail groups).\n \n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:06:00\n", "", "USER,ONE\n", "", ""], ["1009", "XM-U-M-QUERY SPECIFIC", "SPECIFIC QUERY ON A MESSAGE\n", "", "", "\n \nmessage.\n \nIf MailMan finds an addressee on the message that matches the person\nentered, MailMan will display the detailed information on that [LOCAL] or\n[REMOTE] addressee.\n \nIf MailMan cannot find a match, no recipient detailed information can be\ndisplayed.\n \nTo query a message for detailed information on a specific recipient, enter\nYou can use the Query Recipients action code (i.e., 'Q xxx' - where 'xxx'\na 'Q' and the recipient's name at the 'Enter message action' prompt.\nrepresents the name of a person) to inquire about specific local and\nremote recipients of a message. MailMan will display all recipients that\nmatch your entry. The more characters entered (not case sensitive), the\nmore closely MailMan can match your entry to the list of recipients.\n \nWhen doing a query on a message for a specific person, regardless of a\nmatch, MailMan will always display the [BASIC] information about the\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:01:00\n", "", "USER,ONE\n", "", ""], ["101", "XUDOC SPOOL TECH2", "TECHNICAL OVERVIEW OF SPOOLING (2)\n", "", "", "\nObsolete help frame.\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 11:47:00\n", "", "USER,ONE\n", "", ""], ["1010", "XM-U-BO-FULL SCREEN LIST", "FULL SCREEN READER MESSAGE LIST ACTIONS\n", "", "", "\n \nYou can [SELECT] the messages prior to entering the command or\nspecify a [RANGE] of messages after entering the command.\n \n [D] Delete messages.\n [F] Forward messages.\n [FI] Filter messages.\n [L] Later messages.\n [NT] New Toggle messages.\n [P] or [H] Print messages with or without headers.\n [S] Save messages to another basket.\nEnter ^ to exit, or enter one of the [PAGE] commands to see more messages,\n [T] Terminate messages.\nor enter one of the following:\n \n n Read message n, where n is a sequence number of a message in this\n list, or an internal message ID of any message on the system.\n [CD] Change detail. (Toggle between summary and detailed readers.)\n \nThe following commands act on one or more messages in this list.\n
\n\n", "\n- \n\n
\n", "", "1999-12-14 07:43:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["1011", "XM-U-M-QUERY NETWORK", "NETWORK QUERY ON A MESSAGE\n", "", "", "\n \n \nAlso, when messages are received from a non-MailMan remote sites, MailMan\ncaptures the 'From' address from the message header and not from the\nenvelope. However, the 'From' address from the envelope is captured in a\nfield and is displayed by the QN action code when it differs from the\nmessage header 'From' address.\n \nNOTE: The envelope contains the 'From' and 'To' address used by the mail\n transport system and is not part of the message itself.\n \nYou can use the Query Network action code (i.e., 'QN') to retrieve\n[MORE]... \nnetwork/trace header information and [DETAILED] information about each\naddressee ([LOCAL] and [REMOTE] recipients) of a message. However, it is\nprimarily used as a diagnostic tool.\n \nNOTE: The network/trace header information includes all the different mail\n server relay information while the message passed from server to\n server to get to you.\n
\n\n", "\n- \n\n
\n", "", "1999-04-28 07:12:00\n", "", "USER,ONE\n", "", ""], ["1012", "XM-U-Q-SEARCH MAILBOX", "SEARCHING FOR MESSAGES - SEARCHING YOUR MAILBOX\n", "", "", "\n \n * A specific mail basket in your mailbox -\n MailMan will look for the messages in a mail basket using\n the search criteria that you enter. \nUnder the 'Query/Search for Messages' option on the main MailMan menu,\nusing multiple search [CRITERIA], you can search for any messages you sent\nor that were sent to you in any of the following locations in your mailbox:\n \n * All mail baskets in your mailbox -\n MailMan will look for the messages in every basket in your mailbox\n using the search criteria that you enter.\n \n
\n\n", "\n- \n\n
\n", "", "2002-05-02 14:41:00\n", "", "USER,ONE\n", "", ""], ["1013", "XM-U-M-LATERED MESSAGE REPORT", "REPORT ON LATERED MESSAGES\n", "", "", "\n \n \n * Basket - The mailbox basket name where the 'latered' message is located.\n \n * Message - The MailMan internal message identification number of the\n 'latered' message.\n \n * Subject - The subject of the 'latered' message.\n \nTo list your 'Latered' messages, choose the Report on Later'd Messages\noption on the Other MailMan Functions menu. You can use this report to\nYou can use the Report on Later'd Messages option available on the Other\ndecide if you want to modify any of these dates or delete any of the\nentries using the [CHANGE]/Delete Later'd Messages option.\nMailMan Functions menu to display a list of messages that you've set to be\nnew at a future date and time ('Latered').\n \nThe report provides the following information:\n \n * Date - The date and time the message will be made new (i.e., 'latered'\n date and time).\n\n\n", "\n- \n\n
\n", "", "1999-01-14 10:56:00\n", "", "USER,ONE\n", "", ""], ["1014", "XM-U-M-LATERED MESSAGE CHANGE", "CHANGE/DELETE LATERED MESSAGES\n", "", "", "\n \n message will not appear as 'new' in your mailbox.\n \nTo change a 'Latered' date and time for a message, choose the\nChange/Delete Later'd Messages option on the Other MailMan Functions menu\nand then choose the 'Change this date' option.\n \nTo delete a 'Latered' date and time for a message, choose the\nChange/Delete Later'd Messages option on the Other MailMan Functions menu\nand then choose the 'Delete this date' option.\nYou can use the Change/Delete Later'd Messages option available on the\nOther MailMan Functions menu to do the following to any message with a\n'latered' date and time:\n \n * Change this Date - Modify the 'latered' date and time so that the\n message will appear as 'new' in your mailbox on that future date.\n \n * Delete this Date - Delete the 'latered' date and time so that the\n
\n\n", "", "", "1998-12-28 15:49:27\n", "", "USER,ONE\n", "", ""], ["1015", "XM-U-MO-REPLY", "REPLYING TO A MESSAGE - OPTIONS AT THE 'Transmit' PROMPT\n", "", "", "\n \nEnter ^ to abort the reply or press <Enter> to transmit it, or enter any\nof the following options before transmitting your reply:\n \n [B] Back up and read/review the original message or any responses.\n [E] Edit your reply.\n [I] Include the original message or any responses in your reply.\n [Q] Query recipients or network header info (Q, QD, or QN).\n [T] Transmit your reply now.\n
\n\n", "\n- \n\n
\n", "", "1998-12-29 12:37:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["1016", "XM-U-M-VAPORIZE DATE SEND", "SET A VAPORIZE DATE WHEN SENDING A MESSAGE\n", "", "", "\n \n \nAs MailMan delivers the message with a Vaporize Date into each recipient's\nmail basket, MailMan sets the AUTOMATIC DELETION DATE (i.e., vaporize\ndate) for the message. However, recipients are free to modify or remove\nthe AUTOMATIC DELETION DATE at any time prior to the vaporization date.\n \nTo set a 'Vaporize Date' for a message you are sending, enter a 'V' at the\n'Select Message option: Transmit now//' prompt.\nBefore sending a message, you can use the Vaporize Date Set action code to\nset a specified date and time for a message to be deleted ('vaporized')\nfrom each recipient's mailbox. Thus, all senders of messages have the\nability to set a Vaporize Date for a message.\n \nFor example, set a Vaporize Date for a message, if you are sure that the\nmessage is only needed until a certain date. MailMan will automatically\nremove it from the basket it is in at that date.\n\n\n", "", "", "1998-12-29 11:41:05\n", "", "USER,ONE\n", "", ""], ["1017", "XM-U-MO-SEND", "SENDING A MESSAGE - OPTIONS AT THE 'Transmit' PROMPT\n", "", "", "\n \n [L] Transmit your message later. (You'll be asked when.)\n [NS] Add your network signature to the message.\n [T] Transmit your message now.\n \n [MORE]...\nEnter ^ to abort the message or press <Enter> to transmit it, or enter any\nof the following commands before sending it:\n \n [B] Back up and review the message.\n [ER] Edit the Recipients of the message.\n [ES] Edit the Subject of the message.\n [ET] Edit the Text of the message.\n [IM] Include responses from another Message\n
\n\n", "\n- \n\n
\n", "", "2000-05-15 09:03:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["1018", "XM-U-MO-SEND-2", "MORE MESSAGE OPTIONS\n", "", "", "\n \n [I] Make the message Information Only. (Recipients can't reply to it,\n but you can.)\n [P] Make the message Priority. (Recipients are alerted to it.)\n [R] Return receipt requested as each recipient reads the message.\n [S] Scramble the text. (You'll be asked for a password and a hint.\n Recipients will be shown the hint and must enter the password to\n unscramble and read the message.)\n [V] Set a date on which the message will Vaporize (be deleted) from\n each recipient's Mailbox. (Recipients may override.)\n [X] Make the message Closed. (Recipients can't forward it, but you can.)\nThe following commands are toggles. Enter them once, and you perform the\nassociated action. Enter them again, and you undo it. If you forget what\nstate they're in (on or not), enter ? and MailMan will tell you.\n \n [C] Make the message Confidential. (Surrogates can't read it.)\n [D] Request a Delivery basket to which the message will be delivered in\n each recipient's Mailbox. (Whether the request is honored\n depends on each recipient's delivery basket privileges setting.)\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 13:12:00\n", "", "USER,ONE\n", "", ""], ["1019", "XM-U-MO-READ", "READING A MESSAGE - OPTIONS\n", "", "", "\n \n [L] Later the message. (Set a date/time at which the message will\n be made New again.)\n [N] Toggle the message New or not.\n [P] or [H] Print the message with or without headers.\n [QUERY] List the message's recipients and characteristics.\n [R] or [RI] Reply to the message. (The other recipients will see your reply.)\n [S] Save the message to another basket.\n [T] Terminate the message. (Delete it and stop receiving replies.)\n \n [MORE]...\nEnter ^ to ignore the message, or enter any of the following commands:\n \n <Enter> Accept the [DEFAULT]. (Usually Ignore, but can be Delete.)\n [B] Back up to read/review from the original message or any of the\n responses to the end.\n [D] Delete the message.\n [F] Forward the message to recipients.\n I Ignore the message. (Quit reading it and leave it where it is.)\n
\n\n", "\n- \n\n
\n", "", "1999-05-13 14:45:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["102", "XUDOC SPOOL TECH3", "TECHNICAL OVERVIEW OF SPOOLING (3)\n", "", "", "\nObsolete help frame.\n
\n\n", "", "", "1992-04-15 11:46:00\n", "", "USER,ONE\n", "", ""], ["1020", "XM-U-MO-READ-2", "READING A MESSAGE - OPTIONS (CONTINUED)\n", "", "", "\n \n [K] Toggle whether or not replies to a priority message are delivered\n to you as priority mail.\n [V] Set a date on which the message should Vaporize (be deleted)\n from your Mailbox.\n [W] Write (Send) a new message.\n [X] Use PackMan options with a PackMan message.\n \nSome of the commands may not be available in certain situations.\nEnter ? to see which commands are available.\nIf you enter a command which is not available, you will be told why it isn't.\n [A] Answer the message Internet-style. (Like Reply, but only to sender.)\n [BR] Print the message to the VA FileMan Browser and view it there.\n [C] Copy the message and/or any of its responses to create a new message.\n [E] Edit the message.\n [HG] Access mail group help to get information about a mail group.\n [HU] Access user help to get information about a user.\n [IN] Toggle whether or not the message is Information Only.\n (Recipients can't reply, but you, the sender, can.)\n
\n\n", "\n- \n\n
\n", "", "2000-05-25 07:22:00\n", "", "USER,ONE\n", "", ""], ["1021", "XM-U-M-BACKUP BEFORE SENDING", "BACKUP A MESSAGE TO REVIEW BEFORE SENDING\n", "", "", "\n \nWhen sending a message, you can use the Backup action code (i.e., 'B') to\nreview a message before you send it. Based on your review, you can then\nre-edit your message.\n \nTo review a message (back up) before sending it, enter a 'B' at the\n'Select Message Option: Transmit now//' prompt.\n
\n\n", "", "", "1998-12-29 16:00:11\n", "", "USER,ONE\n", "", ""], ["1022", "XM-U-MO-EDIT", "EDITING A MESSAGE\n", "", "", "\n \n [ES] Edit the Subject of the message.\n [ET] Edit the Text of the message.\n [IM] Include responses from another Message\n [NS] Add your Network Signature to the message.\n \n [MORE]...\n \nWhen you complete your edits, press <Enter> to return to this menu and\nthen [FORWARD] the message to the recipients.\nYou can use the Edit action code (i.e., 'E') to edit any message created\nby you and sent only to yourself, but not yet to other recipients.\nSuch a message is regarded as a work in progress, and still subject to change.\nOnce you send it to anyone else, or reply to it, you can no longer edit it.\n \nTo edit a message enter an 'E' at the 'Enter message option' prompt. You\ncan choose to edit the message as follows:\n \n
\n\n", "\n- \n\n
\n", "", "2000-05-15 09:35:00\n", "", "USER,ONE\n", "", ""], ["1023", "XM-U-M-CHOOSE RESPONSES", "SPECIFYING A LIST OR RANGE OF RESPONSES\n", "", "", "\n \n * Specify a range of numbers by separating the beginning and ending numbers\n with a dash/hyphen (e.g., '0-10', where '0' is the original message).\n \n * Specify at what response you want MailMan to include through the remaining\n responses by entering a specific number followed by a dash/hyphen\n (e.g., 20-, MailMan would include response 20 through the remaining\n responses).\n \n * Specify combinations of the above by putting ranges where numbers would go,\n etc. (e.g., '0-3,5,8-10,20-', where '0' is the original message).\nWhen you are printing or copying a message, or when you are including parts of\na message in a reply or a new message, MailMan allows you to specify the\noriginal message and/or any combination of responses. \n \nTo specify a range or list, use the following syntax:\n \n * Enter the message response numbers separated by commas (e.g., '1,5,9').\n \n
\n\n", "", "", "2000-05-15 09:06:00\n", "", "USER,ONE\n", "", ""], ["1024", "XM-U-B-READER FULL SCREEN", "FULL SCREEN MESSAGE READER\n", "", "", "\n \n \nWhereas with the Classic message reader, you must enter ? or ?? to see the\nmessages, the Full Screen message reader presents you with a screen full\nof messages at all times, in the [ORDER] you've specified.\n \nYou can enter one of the [BASKET] actions, read a message and perform [MESSAGE]\nactions on it, or [NAVIGATE] about the basket and beyond.\nThe Full Screen message reader enables you to read and manage messages in a\nsimulated full-screen environment. It has two levels of detail:\n \n Summary Provides [SUMMARY] information.\n Detailed Provides Summary information and additional [DETAILED] information.\n \nWhile you are in the Full Screen message reader, you can [CHANGE DETAIL]\n(toggle) between the Summary and Detailed displays.\n
\n\n", "\n- \n\n
\n", "", "1999-01-06 07:15:00\n", "", "USER,ONE\n", "", ""], ["1025", "XM-U-B-READER DETAILED", "DETAILED MESSAGE INFORMATION\n", "", "", "\n \n year).\n \n * Lines - Number of lines of text for each message in the mail basket.\n \n * Read/Rcvd - Total number of responses read and received for a message.\n If there are no responses to a message, no totals will be indicated.\nThe Detailed Full Screen message reader and the Classic message reader (upon\nentering a ??) provide, in addition to [SUMMARY] information, the following\ndetailed information for each message:\n \n * MailMan Internal Message Identification Number - The MailMan message\n numbers generated internally for each message (displayed in brackets).\n \n * Message Sent Date - The date each message was sent (i.e., day, month,\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 08:18:00\n", "", "USER,ONE\n", "", ""], ["1026", "XM-U-B-READER SUMMARY", "SUMMARY MESSAGE INFORMATION\n", "", "", "\n \n - Range of message numbers in the basket.\n - How many message are new in the basket.\n \n * Flags - Any special flags associated with the messages in the basket.\n For example: Priority (!) or New (*) flags.\n \n * Message Sequence Numbers - The numbers associated with the messages.\n (Meaningful only while the message remains in the basket or list.)\n \n * Subject - Subject of each message in the mail basket.\nThe Summary Full Screen message reader and the Classic message reader (upon\n \n * From - The name of the person who sent each message in the mail basket.\nentering a ?) provide the following summary information:\n \n * Basket - Basket containing the messages (e.g., 'IN').\n \n * Message Totals -\n \n - How many messages in the basket.\n
\n\n", "", "", "1998-12-31 00:00:00\n", "", "USER,ONE\n", "", ""], ["1027", "XM-U-B-READER CLASSIC", "CLASSIC MESSAGE READER\n", "", "", "\n \nand the message number in that basket. Optionally, the message reader\nwill also display a [PREVIEW] of the message subject and sender.\n \nAt this point you can enter one or two question marks to see a message list,\nenter one of the [BASKET] actions, read a message and perform [MESSAGE] actions\non it, or [NAVIGATE] about the basket and beyond.\nThe Classic message reader provides two levels of detail when listing\nmessages in a basket, depending on whether you enter one or two question marks:\n \n ? Provides [SUMMARY] information.\n ?? Provides Summary information and additional [DETAILED] information.\n \nThe Classic message reader indicates the next message to be read in a\nmail basket (in the [ORDER] you've specified) by displaying the basket name\n
\n\n", "\n- \n\n
\n", "", "1999-04-28 06:47:00\n", "", "USER,ONE\n", "", ""], ["1028", "XM-U-B-READER", "MAILMAN MESSAGE READERS\n", "", "", "\n \nMailMan should [PROMPT] you to choose a message reader whenever you read\nmessages.\n \nThe readers share most [BASKET] actions, which help you manage groups of\nmessages, but each reader has some actions which are unique to it. The readers\nshare the same [MESSAGE] actions, which help you manage individual messages. \nMailMan provides message readers for you to list, read, and manage your\nmessages when using the Read/Manage Messages option:\n \n * [CLASSIC]\n \n * [FULL SCREEN], either Detailed or Summary\n \nYou can set your [DEFAULT MESSAGE READER] and decide whether or not\n
\n\n", "\n- \n\n
\n", "", "1999-01-06 07:38:00\n", "", "USER,ONE\n", "", ""], ["1029", "XM-U-R-READ-2", "READING AND MANAGING YOUR MAIL (CONTINUED)\n", "", "", "\n \n \n [BASKET] - Choose from which basket you wish to process your mail. All\n users have an 'IN' basket and a 'WASTE' basket. Additionally,\n users may have created other 'save' baskets. When reading\n messages, the default is to start reading from the 'IN'\n basket.\n \n[MORE]...\nWhen reading/managing your mail, MailMan will ask you to choose the\nfollowing:\n \n [READER] - Optionally, MailMan may ask you to choose your message reader\n (i.e., Classic, Summary Full Screen, or Detailed Full\n Screen message readers. If you set the MESSAGE READER\n [PROMPT] to 'Do not ask,' MailMan will not ask for this\n information.\n
\n\n", "\n- \n\n
\n", "", "1999-01-13 15:43:00\n", "", "USER,ONE\n", "", ""], ["103", "XUFILE ACCESS USE2", "WHO NEEDS FILE ACCESS?\n", "", "", "\n \nFile called 'Accessible File'.\n \nOnly in special cases will you need to grant file access to users who do not\nhave VA FileMan privileges. This might arise if, within the template of an\nedit-type option, the user attempts to add or delete entries from a pointed-\nto file. Application programmers may either specify which files you need to\ngrant to whom, or modify their code or data dictionary specifications.\nVA FileMan users may be granted access to one or more files. The level of\naccess authority may range from simply reading data to modifying data\ndictionaries. If a non-programmer user has VA FileMan as a menu option,\nthat user will not have access to any file until so granted.\n \nYou, as the systems manager, will need to specify the particular files and\nlevels of access for your VA FileMan users. An option has been added to the\nUser Edit menu for this purpose. It involves a multiple field in the User\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1030", "XM-U-R-READ-3", "READING AND MANAGING YOUR MAIL (CONTINUED)\n", "", "", "\n \n action. Here, you can reply to the message or choose from\n several other options.\n \nNOTE: Messages contain message [HEADERS] that are displayed prior to the\n text of the message.\n \n Also, you can list all messages in an individual basket or list all\n messages in your mailbox through the Mailbox [CONTENTS] List option\n on the Other MailMan Functions menu.\n [LIST] - Using the full-screen message readers, you are presented with\n a list of messages, here you can choose from several options.\n Using the Classic message reader, MailMan will preview the\n message that will be read or you can enter one or two\n question marks to get a list of messages from which you can\n choose from several options.\n \n [ACTION] - After reading a message, you are prompted for a message\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 13:24:36\n", "", "USER,ONE\n", "", ""], ["1031", "XM-U-M-REPLY-2", "REPLYING TO A MESSAGE (CONTINUED)\n", "", "", "\n \n \nWhen you are given the opportunity to back up to see new responses, you\ncan enter a 'B' ([BACKUP]) at the 'Select Message option: Transmit now//'\nprompt. The default will be to back up to this new, unseen response,\ninstead of the original message (response 0). Thus, you can back up and\nread the latest response(s).\n \nSince you haven't transmitted your response yet, you may choose to revise\nyour own reply based on that new response. You simply enter 'E' (Edit your\nreply) at the 'Select Message option: Transmit now//' prompt, and you are\nAlso, if while composing a reply to a message another reply comes in to\nput back into the editor where you can modify your reply based on what you\njust read.\nthe same message, you will be prompted with the following text when\nexiting the editor (prior to sending your reply):\n \n >> Response n has arrived - you may backup to see it. <<\n ^\n |\n (n = the response number)\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 13:45:20\n", "", "USER,ONE\n", "", ""], ["1032", "XM-U-P-FILTER CRITERIA", "FILTERING MAIL CRITERIA\n", "", "", "\n \n \n * ADDRESSED TO - Addressee of the message. This includes users and mail\n groups. MailMan will check the addressees that you see when you\n [QUERY] (Q) the message.\n \nFor the filter to take effect, all criteria entered must be true (i.e.,\nmatch the characteristics of the message). For example, if you specify the\n'SUBJECT CONTAINS' and 'FROM,' the filter takes effect only if the subject\nof the message contains the string you specified in the 'SUBJECT CONTAINS'\nfield and the message is from the person you specified in the 'FROM' field.\nThe following three criteria can be used in any combination when filtering\n \n[MORE]...\nmail:\n \n * SUBJECT CONTAINS - Subject of the message. The string entered can\n appear anywhere in the subject.\n \n * FROM - The name of the person who sent the message (partial matching\n possible).\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:25:00\n", "", "USER,ONE\n", "", ""], ["1033", "XM-U-P-FILTER-2", "FILTERING MAIL (CONTINUED)\n", "", "", "\n \n field) whose criteria matches the message characteristics (i.e.,\n subject contents, sender of the message, and/or message addressee).\n \nFiltering takes place during message delivery. Filtering can also be\nselected as a [BASKET ACTION] (i.e., FI).\n \n[MORE]... \nIn addition to setting the filtering criteria, when you want MailMan to\nuse a specific filter the following conditions must be met:\n \n * Filtering must be turned on for your mailbox.\n \n * The filter's status must be active (i.e., STATUS field).\n \n * The filter must be the first filter (i.e., controlled by the [ORDER]\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 14:08:39\n", "", "USER,ONE\n", "", ""], ["1034", "XM-U-P-FILTER CRITERIA-2", "FILTERING MAIL CRITERIA (CONTINUED)\n", "", "", "\n \nIf you wish the filter to take effect upon either 'SUBJECT CONTAINS' or\n'FROM,' you must create two separate filters: one with 'SUBJECT CONTAINS'\nand another with 'FROM' as your filter criteria.\n
\n\n", "", "", "1998-12-31 14:19:18\n", "", "USER,ONE\n", "", ""], ["1035", "XM-U-M-QUERY INFO REMOTE", "REMOTE USER QUERY INFORMATION\n", "", "", "\n \n * Time - This is the time (in seconds) it took to transmit the message\n over the network to the remote recipient.\n \n * Remote Message ID - If sent to a remote MailMan user, MailMan displays\n the internal message identification number for the message and the\n remote user's MailMan location. This information is not displayed when\n the message is sent to a non-MailMan location.\n \n * Forwarding Information - If the message was forwarded to the remote\n recipient, MailMan indicates the name of the person who forwarded the\nFor each remote recipient, MailMan provides the following information\n message and the date and time the message was forwarded.\nwhen doing a Query:\n \n * Name - MailMan displays the name of the remote recipient.\n \n * Sent - The date and time the message was sent over the network to the\n remote recipient.\n \n
\n\n", "", "", "1998-12-31 14:39:30\n", "", "USER,ONE\n", "", ""], ["1036", "XM-U-M-QUERY INFO LOCAL", "LOCAL USER QUERY INFORMATION\n", "", "", "\n \n \n - Not read - If the local recipient hasn't read the message, MailMan\n displays this message.\n \n - First read date and time - The date and time the local recipient\n first read the message.\n \n - Last read date and time - The date and time the local recipient\n last read the message. Associated with this date is the number of\n responses read. If the message has any responses, MailMan\nFor each local recipient, MailMan provides the following information when\n indicates the total number of responses read (if any).\n \n - Terminated date and time-If the local recipient has terminated the\n message, MailMan displays the date that they terminated the\n message.\n \n NOTE: MailMan also indicates when a surrogate has read a message.\n \n * Forwarding Information - If the message was forwarded to the local\n recipient, MailMan indicates the name of the person who forwarded the\ndoing a Query:\n message and the date and time the message was forwarded.\n \n * Name - MailMan displays the name of the local recipient.\n \n * Status - This indicates the current status of the message in the local\n recipient's mailbox. For example, if and when the recipient read the\n message. This includes the following information:\n
\n\n", "", "", "1998-12-31 14:43:04\n", "", "USER,ONE\n", "", ""], ["1037", "XM-U-M-QUERY INFO BASIC", "BASIC QUERY INFORMATION\n", "", "", "\n \n \n * Number of Recipients - This is the total number of recipients of the\n message (including the total number of members in any mail groups).\nWhen doing a query on a message, MailMan will always display the following\nbasic information about the message:\n \n * Message Header - The message header includes the 'Subject,' and 'From'\n information of the message.\n \n * Local Message ID - This is the MailMan internal message identification\n number and MailMan location.\n
\n\n", "", "", "1998-12-31 15:06:07\n", "", "USER,ONE\n", "", ""], ["1038", "XM-U-M-QUERY NETWORK-2", "NETWORK QUERY ON A MESSAGE (CONTINUED)\n", "", "", "\n \nYou won't notice a difference with messages from other MailMan systems.\nHowever, other non-MailMan systems sometimes include clear-text names in\nthe 'From' address, in addition to the e-mail address. For example:\n \n "'Fred Smith' <fred@anydomain.com>"\n \nTo query a message for network and detailed recipient information, enter a\n'QN' at the 'Enter message action' prompt.\n
\n\n", "", "", "1998-12-31 15:14:19\n", "", "USER,ONE\n", "", ""], ["1039", "XM-U-M-QUERY-2", "QUERYING A MESSAGE FOR ITS STATUS (CONTINUED)\n", "", "", "\n \n * 'QT' (Query Terminated) displays detailed information for each\n [LOCAL] recipient who has [TERMINATED] the message.\n\nNOTE: Since [MAIL GROUP] membership is dynamic and message recipients are\n resolved at the time the message is addressed, messages addressed to\n the same Mail Group can have different lists of recipients.\n * 'QC' (Query Current) displays detailed information for each\n [LOCAL] recipient who is current on the message, that is,\n who has read the message and every response.\n\n * 'QNC' (Query Not Current) displays detailed information for each\n [LOCAL] recipient who is NOT current on the message, that is,\n who has NOT read the message and every response.\n\n
\n\n", "\n- \n\n
\n", "", "2001-03-05 15:56:00\n", "", "USER,ONE\n", "", ""], ["104", "XUFILE ACCESS USE1", "INTRODUCTION\n", "", "", "\nAs systems manager, you are responsible for granting access to your system.\nfile access. The only instance when file access is checked during the use \nof an option is when VA FileMan becomes directly involved.\n \nIn an option the application programmer controls access to the initial\nfile. File access is not checked. Within the option, however, the\napplication may call VA FileMan to point to another file. Then file access\nis checked since VA FileMan, not the application, is operative.\n \nSo you must grant file access whenever VA FileMan is directly governing\nuser activity. This will primarily concern your VA FileMan users, people\nYou must gauge the needs of each user and assign an appropriate degree of\nwith DIUSER as a menu option, who will need to have file access. Hence,\nthe [PURPOSE] of granting file access is to control the use of VA FileMan.\naccess authority. Too much may risk the security of your system while too\nlittle may inhibit productive activity.\n \nApplication packages are distributed with menus for different groups of\nusers. Menus and keys are provided which control access to the application\nfiles. File entries and associated attribute fields may be displayed,\nedited, or deleted according to the design of the option regardless of any\n
\n\n", "\n- \n\n
\n", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1040", "XM-U-I-GROUP-2", "MAIL GROUPS (CONTINUED)\n", "", "", "\n \n \n * Help (User/Group Info., etc.) - Use this option to get [INFORMATION]\n on mail groups. This option is located on the main MailMan Menu.\n \n * Enroll in (or Disenroll from) a Mail Group - Use this option to enroll\n in or disenroll from [PUBLIC] mail groups. This option is located on\n the Personal Preferences menu.\n \n * Personal Mail Group Edit - Use this option to create your own\n [PERSONAL] (Private) mail groups. This option is located on the\nIf a user attempts to send mail to a group that has one or more Authorized\n Personal Preferences menu.\nSenders, and they are not one of them, they are shown a list of Authorized\nSenders. They can send the message to one of these users who can forward\nit to the group, if desired. Remote users cannot send mail to any local\ngroup which has Authorized Senders. Any messages sent by a remote user to\na group with Authorized Senders will be rejected.\n \nThe MailMan interface provides three options to manage mail groups:\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 15:32:16\n", "", "USER,ONE\n", "", ""], ["1041", "XM-U-P-GROUP ENROLL", "PUBLIC MAIL GROUPS\n", "", "", "\n \n in that mail group when you use the Enroll in (or Disenroll from) a\n Mail Group option.\n \n * Disenrolling - If you already are a member of a particular mail group\n and the mail group allows self-enrollment, MailMan will confirm your\n membership and ask you if you want to disenroll yourself from the mail\n group when you use the Enroll in (or Disenroll from) a Mail Group option.\n Note: Depending on the site, you may be able to disenroll from a non-\n self-enrolling group. (This is controlled by field 22 in file 4.3.)\n \nMailMan gives you the opportunity to enroll in Public mail groups using\n[MORE]...\nthe Enroll in (or Disenroll from) a Mail Group option. You can also remove\nyourself (disenroll) from mail groups using the same option. The operation\nof this option depends on your current membership status and the\nenrollment capability of the mail group:\n \n * Enrolling - If you are not a member of a particular mail group and the\n mail group allows self-enrollment, MailMan will enroll you as a member\n
\n\n", "\n- \n\n
\n", "", "2001-02-13 10:03:00\n", "", "USER,ONE\n", "", ""], ["1042", "XM-U-P-GROUP ENROLL-2", "PUBLIC MAIL GROUPS (CONTINUED)\n", "", "", "\n \nIf you are not able to enroll in or disenroll from a mail group,\nand you think you need to, you should contact the Mail Group\n[COORDINATOR] or Organizer for that mail group and ask\neither to be enrolled in or disenrolled from the mail group.\n(You can find out who they are by doing a mail group [INQUIRY].)\n\nYour last resort is to contact IRM, or a CAC or ADPAC.\n
\n\n", "\n- \n\n
\n", "", "2001-02-13 10:16:00\n", "", "USER,ONE\n", "", ""], ["1043", "XM-U-P-GROUP PERSONAL", "PERSONAL MAIL GROUPS\n", "", "", "\n \nand send mail to the group.\n\nNon-members can neither see nor address Private or Personal mail groups.\nThe creator (i.e., Organizer) and members of the personal mail group can: \n \n * Display Information - Use the Group [INFORMATION] option on the Help\n (User/Group Info., etc.) menu to display information on that group.\n \n * List the Group - See the group listed when you enter two question\n marks (i.e., online help) at the 'Select MAIL GROUP NAME:' prompt.\nPersonal, or Private, mail groups are ones that you create and maintain for\n \n[MORE]... \nyour own use, and, possibly, the use of its local members.\n\nIf the 'Restrictions' field is set to 'Organizer only', then only the creator\nof the mail group (i.e., Organizer) can address and send mail to the group.\n\nIf the 'Restrictions' field is set to 'Unrestricted' or null, then both the\ncreator of the mail group (i.e., Organizer) and its local members can address\n
\n\n", "\n- \n\n
\n", "", "2001-02-13 09:16:00\n", "", "USER,ONE\n", "", ""], ["1044", "XM-U-H-GROUP", "MAIL GROUP INFORMATION\n", "", "", "\n \n * Type - The type of mail group determines who can send mail to it.\n Mail groups can be either of the following two types:\n \n - Public\n - Private ([PERSONAL])\n \n Provided there are no Authorized Senders specified, anyone can send\n mail to a public group and only its members can send mail to a private\n group. If there are Authorized Senders specified, only those users can\n address the group.\nMailMan gives you the opportunity to obtain information on a mail group\n \n[MORE]... \nthrough the Group Information option on the Help (User/Group Info., etc.)\nmenu option located on the main MailMan Menu.\n \nYou can obtain the following mail group information:\n \n * Name - The name of the mail group.\n \n
\n\n", "\n- \n\n
\n", "", "1999-01-20 11:46:00\n", "", "USER,ONE\n", "", ""], ["1045", "XM-U-H-GROUP-2", "MAIL GROUP INFORMATION (CONTINUED)\n", "", "", "\n \n * Restrictions - This field is only applicable to PRIVATE mail groups.\n It provides the opportunity for the Organizer of the mail group to\n decide who may address (send messages to) this PRIVATE mail group.\n If 0 (zero) or null, then the group is unrestricted, and all members\n may address the group. If 1, then only the organizer may address\n the group, and the group becomes a personal group.\n\n * Reference Count - How many times the mail group has been referenced\n (used).\n \n * Allow Self-Enrollment? - This field is only applicable to PUBLIC mail\n[MORE]... \n groups. Is self-enrollment allowed ('Yes' or 'No')?\n If 'Yes', you can enroll yourself in or disenroll yourself from a mail\n group. If 'No' or null, you must contact the Coordinator or Organizer\n of the mail group to either enroll you in or disenroll you from the group.\n Note: Depending on the site, you may be able to disenroll from a non-\n self-enrolling group. (This is controlled by field 22 in file 4.3.)\n \n\n\n", "\n- \n\n
\n", "", "2001-02-12 15:39:00\n", "", "USER,ONE\n", "", ""], ["1046", "XM-U-H-GROUP-3", "MAIL GROUP INFORMATION (CONTINUED)\n", "", "", "\n \n * Organizer - The organizer is the person who set up/created the mail\n group. An Organizer can add new members to a [PRIVATE] mail group.\n \n * Authorized Senders - Authorized Senders are the only users that are\n allowed to send mail to the mail group. If unspecified, it is assumed\n that anyone can send mail to the group, if [PUBLIC], or only members\n can send to it, if [PRIVATE]. Remote users cannot send mail to any\n local group which has Authorized Senders. Any messages sent by a\n remote user to a group with Authorized Senders will be rejected.\n \n * Last Referenced - The last date and time this group was referenced\n[MORE]... \n (sent a message).\n \n * [COORDINATOR] - The person responsible for maintaining the membership\n of the mail group. \n \n * Description - Description of the mail group.\n \n
\n\n", "\n- \n\n
\n", "", "2001-02-08 11:44:00\n", "", "USER,ONE\n", "", ""], ["1047", "XM-U-A-GROUP LARGE-2", "ADDRESSING MAIL TO LARGE MAIL GROUPS (CONTINUED)\n", "", "", "\n \nforeground as usual.\n \nFor example, let's assume that IRM set our [BIG GROUP SIZE] field to 100.\nIf we were to address a message to a mail group with 100 or more members,\nit would be considered a 'large' mail group and MailMan would ask us if we\nwanted to 'later' delivery to this group. Conversely, any mail addressed\nto a mail group whose total number of members was less than 100 would be\nconsidered a 'small-' to 'medium-sized' group and MailMan would not ask us\nif we wanted to deliver the message at a later date and time.\n \nIf you need to selectively remove (minus) members from the group, you\nNOTE: A mail group is also considered large if it contains another mail\n group or a distribution list.\nshould not 'later' the delivery of the message to that group.\n \nIf the total number of members in a mail group is equal to or greater than\nthe value in the [BIG GROUP SIZE] field, the mail group is considered to\nbe a 'large' mail group and treated accordingly. Conversely, if the total\nnumber of members in a mail group are less than this number, they will be\ntreated as 'small-' to 'medium-sized' mail groups and processed in the\n
\n\n", "\n- \n\n
\n", "", "1998-12-31 16:02:31\n", "", "USER,ONE\n", "", ""], ["1048", "XM-U-M-WRITE-2", "SENDING A NEW MESSAGE INSTEAD OF A REPLY (CONTINUED)\n", "", "", "\n \nThus, don't use 'Me too's,' Write a new message. Save the many recipients\nthe time of having to read responses that are only intended for the sender\nor a subset of recipients. \n
\n\n", "", "", "1999-01-06 14:38:36\n", "", "USER,ONE\n", "", ""], ["1049", "XM-U-M-FORWARD-2", "FORWARDING MESSAGES (CONTINUED)\n", "", "", "\n \n prompt.\n \n - MailMan will first ask you to select which messages you want to\n forward, including a [RANGE] of messages. Also, if you are using a\n full-screen reader, you can pre-[SELECT] messages and then forward\n them as a group.\n \n - MailMan will then ask to whom you wish to forward the messages.\nThe Forward action code allows you to forward individual messages or a\ngroup of messages in a mail basket:\n \n * Individually - After reading a message, enter an 'F' at the 'Enter\n message action' prompt. MailMan will ask to whom you wish to forward\n the message.\n \n * Group of Messages - Enter an 'F' at the basket option or command\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 10:53:00\n", "", "USER,ONE\n", "", ""], ["105", "XUFILE ACCESS USE3", "LEVELS OF ACCESS AUTHORITY\n", "", "", "\n READ ACCESS permits display of data on file. This allows use of the VA\n or transfer of entries with 'Transfer'. It does not permit\n deletion of the file or any of its attribute fields.\n \n LAYGO ACCESS permits adding a new entry to a file with the 'Enter/Edit'\n option as long as write access has also been enabled.\n \n DD ACCESS permits data dictionary access for changing or deleting the\n structure of the file itself. The 'Modify' and 'Utility'\n options are enabled.\n \n FileMan 'Print', 'Search', 'Inquire', 'Statistics', and\n AUDIT ACCESS allows the [AUDIT] of data changes provided that DD access\n has also been granted. [CONTINUE]\n 'List File Attributes' options.\n \n WRITE ACCESS permits changing data values that are currently on file via\n the 'Enter/Edit' option. It will not permit the adding of\n new entries to the file.\n \nDELETE ACCESS permits deletion of an entire file entry with 'Enter/Edit'\n
\n\n", "\n- \n\n
\n", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1050", "XM-U-M-PRINT-2", "PRINTING MESSAGES (CONTINUED)\n", "", "", "\n \n - MailMan will then ask if you want to print a recipient list. If\n you choose to print recipients, you can print either a summary or\n detailed recipient list.\n \nWhen your entries are complete, MailMan will ask you to select the device\nto which you wish to print.\n \nUnlike the [HEADERLESS] Print Messages action code, the Print Messages\naction code will print the [PRINT] header and the [MESSAGE] header.\n * Printing a Group of Messages - Enter a 'P' at the basket option or\n command prompt.\n \n - MailMan will first ask you to select which messages you want to\n print, including a [RANGE] of messages. Also, if you are using a\n full-screen reader, you can pre-[SELECT] messages and then print\n them as a group.\n \n
\n\n", "\n- \n\n
\n", "", "1999-01-20 09:36:00\n", "", "USER,ONE\n", "", ""], ["1051", "XM-U-M-PRINT NO HEADER-2", "HEADERLESS PRINTING (CONTINUED)\n", "", "", "\n \n - MailMan will then ask if you want to print a recipient list. If\n you choose to print recipients, you can print either a summary or\n detailed recipient list.\n \nWhen your entries are complete, MailMan will ask you to select the device\nto which you wish to print. \n \nUnlike the [PRINT] Messages action code, the Headerless Print Messages\naction code will NOT print the print [HEADER] and the [MESSAGE] header.\n * Printing a group of Messages - Enter an 'H' at the basket option or\n command prompt.\n \n - MailMan will first ask you to select which messages you want to\n print, including a [RANGE] of messages. Also, if you are using a\n full-screen reader, you can pre-[SELECT] messages and then print\n them as a group.\n \n
\n\n", "\n- \n\n
\n", "", "1999-01-20 09:52:00\n", "", "USER,ONE\n", "", ""], ["1053", "XM-U-M-TERMINATE-2", "TERMINATING MESSAGES (CONTINUED)\n", "", "", "\n \n - MailMan will first ask you to select which messages you want to\n terminate, including a [RANGE] of messages. Also, if you are using\n a full-screen reader, you can pre-[SELECT] messages and then\n terminate them as a group.\n \n - MailMan will then ask you to confirm the termination.\nTo terminate messages, do the following:\n \n * Individually - After reading a message, enter a 'T' at the 'Enter\n message action' prompt. MailMan will terminate the message.\n \n * Group of Messages - Enter a 'T' at the basket option or command\n prompt.\n \n
\n\n", "\n- \n\n
\n", "", "1999-01-14 11:02:00\n", "", "USER,ONE\n", "", ""], ["1054", "XM-U-M-LATER-2", "MAKE MESSAGES NEW LATER (CONTINUED)\n", "", "", "\n \n been 'latered' and then gives you the chance to:\n \n - Add another 'Later' date on which this message should appear new.\n \n - Change the current 'Later' date.\n \n - Delete the current 'Later' date.\n \n[MORE]...\nTo 'later' individual messages, do the following:\n \n * After reading a message, enter an 'L' at the 'Enter message action'\n prompt. MailMan will then ask you to enter the date and time at which\n you want the message made 'new' again (i.e., 'latered').\n \n * If you later an individual message and then try to later the same\n message again, MailMan will notify you that the message has already\n
\n\n", "\n- \n\n
\n", "", "1999-01-06 16:03:57\n", "", "USER,ONE\n", "", ""], ["1055", "XM-U-M-LATER-3", "MAKE MESSAGES NEW LATER (CONTINUED)\n", "", "", "\n \n \n - MailMan will then ask you to enter the date and time at which you\n want the messages made 'new' again (i.e., 'latered').\nTo 'later' a group of messages, do the following:\n \n * Enter an 'L' at the basket option or command prompt.\n \n - MailMan will first ask you to select which messages you want to\n 'later,' including a [RANGE] of messages. Also, if you are using\n a full-screen reader, you can pre-[SELECT] messages and then\n 'later' them as a group.\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 10:58:00\n", "", "USER,ONE\n", "", ""], ["1056", "XM-U-M-DELETE-2", "DELETING MESSAGES (CONTINUED)\n", "", "", "\n \n \n * Group of Messages - Enter a 'D' at the basket option or command\n prompt.\n \n - MailMan will first ask you to select which messages you want to\n delete, including a [RANGE] of messages. Also, if you are using a\n full-screen reader, you can pre-[SELECT] messages and then delete\n them as a group.\n \n - MailMan will then ask you to confirm the deletion.\nThe user can also retrieve deleted mail from the 'WASTE' basket by reading\n \n[MORE]...\nit, just like any other basket. If you want to keep the message, you can\n[SAVE] it to another basket.\n \nTo delete messages, do the following:\n \n * Individually - After reading a message, enter a 'D' at the 'Enter\n message action' prompt. MailMan will delete the message.\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 10:50:00\n", "", "USER,ONE\n", "", ""], ["1057", "XM-U-M-DELETE-3", "DELETING MESSAGES (CONTINUED)\n", "", "", "\n \nWhen all messages have been deleted from a basket, MailMan will ask you if\nthe entire basket may be eliminated. If you don't want to retain this\nempty basket in your mailbox, answer 'YES' to this prompt.\n
\n\n", "", "", "1999-01-06 16:24:14\n", "", "USER,ONE\n", "", ""], ["1058", "XM-U-I-SURROGATE-2", "MAILMAN SURROGATES (CONTINUED)\n", "", "", "\n \n your identity for the purpose of reading and/or sending mail.\n \nThe MailMan surrogate options are available on the main MailMan Menu and\nthe Personal Preferences menu.\n \n[MORE]... \nThe MailMan interface provides two options with regards to surrogates:\n \n * [BECOME A SURROGATE] (SHARED,MAIL or Other) - Use this option to act\n as a surrogate for SHARED,MAIL or another MailMan user.\n \n * [SURROGATE EDIT] - Use this option to select another user to act as\n your surrogate. Those assigned to as surrogates may have [READ] and\n [WRITE] access assigned to them. Thus, they have the ability to assume\n
\n\n", "\n- \n\n
\n", "", "1999-01-07 08:15:40\n", "", "USER,ONE\n", "", ""], ["1059", "XM-U-I-SURROGATE-3", "MAILMAN SURROGATES (CONTINUED)\n", "", "", "\n \n interest, however, you cannot send new mail. \n \nFor example, you may choose to become a surrogate, if you have been asked\nby someone else to act as their surrogate while they are out of the\noffice. As their surrogate, you can check their mail. Also, you may become\na surrogate of [SHARED,MAIL] in order to read about general information or\nspecial announcements available to all MailMan users.\n \n[MORE]... \nYou can [BECOME] (act as) a surrogate in two different ways:\n \n 1. Other Surrogate - Act as a surrogate for another user (i.e., Other)\n who has designated you as their surrogate and given you privileges\n to: read, reply to, and/or send messages.\n \n 2. [SHARED,MAIL] Surrogate - Act as a 'special user' surrogate (i.e.,\n SHARED,MAIL) where you can read and reply to messages of general\n
\n\n", "\n- \n\n
\n", "", "1999-01-07 09:03:35\n", "", "USER,ONE\n", "", ""], ["106", "XUFILE ACCESS USE4", "HOW IS FILE ACCESS GRANTED?\n", "", "", "\nThe options for granting file access privileges fall into three functional\n all user's profiles. Conversely, the file or range of\n files may be printed with associated users and the\n access levels of each.\n \n RESTRICTING to entirely limit access by user or by file, or to\n delele a range of files for a user or group of users.\n \nThe options are designed to facilitate queries by user or by file. You may\nadd or delete file access for one user or for many users. Or you may begin\nwith the file and list users with access or restrict access. When using the\ncategories: \noptions, there are a few [HINTS] for getting around.\n \n EDITING to assign file access to an individual user or a group\n of users. One user's profile may also be duplicated or\n copied to another user or group of users. To simplify\n adding files, number ranges may be specified.\n \n LISTING to display one user's profile or a name-sorted list of\n
\n\n", "\n- \n\n
\n", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1060", "XM-U-I-SURROGATE-4", "MAILMAN SURROGATES (CONTINUED)\n", "", "", "\n \npassword cannot read it.\nSurrogates may be allowed the following privileges:\n \n * [READ] only privileges.\n \n * Read and [WRITE] privileges.\n \nIf a message is sent [CONFIDENTIAL], a surrogate cannot view it. If a\nmessage has been [SCRAMBLED], a surrogate that does not know the\n
\n\n", "\n- \n\n
\n", "", "1999-01-07 09:10:30\n", "", "USER,ONE\n", "", ""], ["1061", "XM-U-P-SURROGATE READ PRIV", "SURROGATES - READ PRIVILEGES\n", "", "", "\n \n \n * [NEW]/Un New messages in any mail basket.\n \n * [READ] messages (except for [CONFIDENTIAL] ones) in any mail basket.\n \n * [REPLY] to messages in any mail basket.\n \n * [SAVE] messages to any mail basket.\nUsers who give surrogates 'Read' privileges allow the surrogates to do\nany of the following:\n \n * [DELETE] messages in any mail basket.\n \n * [FORWARD] messages in any mail basket to other recipients.\n \n * [LATER] messages in any mail basket.\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 14:04:00\n", "", "USER,ONE\n", "", ""], ["1062", "XM-U-P-SURROGATE WRITE PRIV", "SURROGATES - WRITE PRIVILEGES\n", "", "", "\n \n * [EDIT] messages.\n \n * [SEND] messages.\n \n * [WRITE] messages.\nUsers who give surrogates 'Read and Write' privileges, in addition to all\nthe privileges of [READ] access, allow the surrogates to do any of the\nfollowing:\n \n * [ANSWER] messages.\n \n * [COPY] messages.\n \n
\n\n", "\n- \n\n
\n", "", "1999-01-07 09:30:50\n", "", "USER,ONE\n", "", ""], ["1063", "XM-U-Q-SEARCH CRITERIA", "SEARCHING FOR MESSAGES - SEARCH CRITERIA\n", "", "", "\n \n \n * Sender of one of the Responses - [WHO] replied to the message.\n \n * Addressee of a Message - [WHO] the message was sent to.\n \n * Sent [DATE] - Approximate date range when the message was sent.\n \n * [CONTENTS] of the message - What's in the message or response text.\n \n * Lines of text - Message text contains this many lines or more.\nWhen searching for messages, you can specify any combination of the\n \n[MORE]...\nfollowing search criteria:\n \n * Subject Contents - Enter the 'S' ('Subject contains') search action\n code and then enter any portion of the subject string (not case\n sensitive). The string can be from 3 to 30 characters in length.\n \n * Sender of the Message - [WHO] sent the message.\n\n\n", "\n- \n\n
\n", "", "2000-08-31 13:34:00\n", "", "USER,ONE\n", "", ""], ["1064", "XM-U-Q-SEARCH CRITERIA-2", "SEARCH CRITERIA (CONTINUED)\n", "", "", "\n \ncancel a single search criterion without having to start over, use the\nat-sign ('@' Shift-2 key on most keyboards) to delete the specific search\ncriterion you no longer want.\n \nWhen you have completed your search criteria, enter 'G' (Go search) to\nstart the search. You are automatically placed in the full-screen message\nreader to manipulate any messages found from the search.\n \nTo end the query without searching, you can enter 'Q' (Quit) or enter the\nup-arrow ('^' Shift-6 key on most keyboards) to get out of the\nThe more search criteria you choose, the more specific (and slower!) the\nQuery/Search for Messages option.\nsearch becomes, resulting in a smaller list of messages from which to choose. \n \nAll criteria entered must be true in order to pass the search test. (This\nis similar to using the Boolean 'AND' in Internet search engines or\nprogram code).\n \nMailMan displays the entire list of search criteria you've selected. To\n\n\n", "", "", "2000-08-30 09:21:00\n", "", "USER,ONE\n", "", ""], ["1067", "XM-U-A-LOCAL USER NAME-2", "ENTERING A LOCAL USER'S NAME (CONTINUED)\n", "", "", "\n \n \n * [SEARCHING] for messages by sender, recipient, and/or responder\n \nThe DUZ is a person's unique numeric user ID. Thus, if multiple\naddressees, for example, have similar names, you can enter their local DUZ\ninstead of their name to choose the specific person.\n \nNOTE: You cannot substitute the DUZ for a name when creating members of a\n [PERSONAL] mail group or when [DESIGNATING] a surrogate for\n yourself.\nIn addition to entering a user's name, MailMan also allows you to enter a\nperson's local DUZ when performing the following functions:\n \n * Addressing a message (including [FORWARDING] messages).\n \n * [BECOMING] a surrogate.\n \n * [FILTERING] mail by sender and/or recipient.\n
\n\n", "\n- \n\n
\n", "", "1999-01-07 11:55:56\n", "", "USER,ONE\n", "", ""], ["1068", "XM-U-A-STAGGER DELIVERY-2", "STAGGER DELIVERY OF A MESSAGE (CONTINUED)\n", "", "", "\n \nAfter the message with staggered delivery dates and times has actually\nbeen delivered to the recipients, doing a [QUERY] (QD) on the message will\nindicate that the message was 'forwarded' to the recipients.\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:23:00\n", "", "USER,ONE\n", "", ""], ["1069", "XM-U-R-READ NEW-2", "PROCESSING NEW MAIL (CONTINUED)\n", "", "", "\n \n already indicated to be 'new' and you enter an 'N' (toggle), the\n message will no longer appears as new.\n \nAs messages sent by users to themselves are not considered 'new,' users\ncannot send messages to their baskets and read them using this option. To\nread those messages, you should use the [READ]/Manage Messages option.\n \nIf someone [REPLIES] to a message that was [DELETED] (but not\n[TERMINATED]) by the user, the message is redelivered to the user.\n \nAfter reading a message, you can make it 'new' again by:\nNOTE: Messages contain message [HEADERS] that are displayed prior to the\n text of the message.\n \n * Entering an 'L' ([LATER]) at the 'Enter message option' prompt. You\n then choose the date and time that the message will appear as new\n again.\n \n * Entering an 'N' ([NEW]) at the 'Enter message option' prompt will\n cause the message to appear as new in your mailbox. If a message is\n
\n\n", "\n- \n\n
\n", "", "1999-01-07 14:33:30\n", "", "USER,ONE\n", "", ""], ["107", "XUFILE ACCESS TECH1", "FILE ACCESS TECHNICAL OVERVIEW\n", "", "", "\nThere are two factors which influence how VA FileMan will control access to\nexcept when VA FileMan is called. Options that provide editing of word\nprocessing fields are calling VA FileMan's text editor. Options that\nreference other files may navigate via VA FileMan. If so, access to the\nfiles will be monitored as VA FileMan checks the user's file access.\n \nIn any file access attempt by a user without DUZ(0)=@, VA FileMan first\nchecks that read access is allowed. If so, data values may be displayed.\nRead access will also permit use of VA FileMan's 'Transfer' capability as\nan edit option within word processing fields. Write access will allow the\nchanging of data values. \nfiles. First is the FileMan Access Code, DUZ(0). If this variable is set\n \nAdding new entries or navigation to a pointed-to file are controlled by\nlaygo access. If a pointing field allows laygo, as specified in the data\ndictionary, and the pointed-to file also allows laygo, the user won't need\nexplicit file access. If the pointed-to file is protected, however, the\nuser will need to have been permitted laygo access to the file. Delete\naccess would be checked at the moment the user tried to delete a file entry.\n \nWhen coding calls, if DIC(0) contains an 'L', DIC will allow the user to\nadd a new entry if one of three conditions are met:\nto the programmer's at-sign (@), VA FileMan will allow complete file access.\n \n - the user has been granted laygo access to the file.\n \n - the user's DUZ(0) is equal to '@', or\n \n - the variable DLAYGO is defined equal to the file number.\nIf it is set to anything else, VA FileMan will use the 'Accessible File'\nspecifications in the User File to grant varying levels of file access.\nBut, as usual, for access to fields or templates, VA FileMan will check the\nuser's DUZ(0) character string for a match.\n \nUse of options, though, does not concern the user's specific file access\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1070", "XM-U-P-PRIORITY PROMPT-2", "PRIORITY RESPONSES PROMPT (CONTINUED)\n", "", "", "\n \n to decide each time you read a priority mail message whether you want\n the future responses to be delivered as priority mail. This value\n allows you to override the default value you set in the PRIORITY\n RESPONSES [FLAG] field.\n \n * 1, DO NOT ASK EACH TIME MESSAGE IS READ - MailMan will not prompt you\n to decide each time you read a priority mail message whether you want\n the future responses to be delivered as priority mail. The default\n value you set in the PRIORITY RESPONSES [FLAG] field will be in\n effect.\nMailMan will either ask or not ask you for a new value for this flag each\n \nIf you do not set this field, then you will be prompted to choose whether\nfuture responses will be delivered as priority or not.\ntime you read a priority message, depending on what you enter in the\nPRIORITY RESPONSES PROMPT field.\n \nThere are two possible choices when answering the 'PRIORITY RESPONSES\nPROMPT:' prompt:\n \n * 0, ASK EACH TIME MESSAGE IS READ (default) - MailMan will prompt you\n
\n\n", "\n- \n\n
\n", "", "1999-01-07 15:38:56\n", "", "USER,ONE\n", "", ""], ["1071", "XM-U-P-GROUP PERSONAL-2", "PERSONAL MAIL GROUPS (CONTINUED)\n", "", "", "\n\nMailMan will not allow you to create a personal mail group if a [PUBLIC]\nmail group with that same name already exists.\n\nIf you want to make your group Public, you must first set the 'Restrictions'\nfield to 'Unrestricted', if it isn't already. Then you must contact your\nIRM, CAC, or ADPAC to request that your group be edited to convert it from\nPrivate to Public.\nTo create a new or edit an existing personal mail group, use the Personal\nMail Group Edit option on the Personal Preferences menu. You can add or\ndelete members at any time. You can also use this option to delete the\nentire personal mail group. Even though you are the Organizer of the group,\nyou are not automatically made a member. Thus, you should also make yourself\na member of the personal mail group if you want to receive messages addressed\nto it.\n \n
\n\n", "\n- \n\n
\n", "", "2001-02-13 09:10:00\n", "", "USER,ONE\n", "", ""], ["1072", "XM-U-B-XMIT PRIORITY TOGGLE-2", "TOGGLING MESSAGE TRANSMISSION PRIORITY (CONTINUED)\n", "", "", "\n \n * Group of Messages - Enter an 'X' at the basket option or command prompt.\n\n - MailMan will first ask you to select which messages should have their\n transmit priority changed, including a [RANGE] of messages. Also, if\n you are using a full-screen reader, you can pre-[SELECT] messages and\n then change their transmit priority as a group.\n\n - MailMan will then ask you to confirm your intention.\n\n - Lastly, MailMan will ask you whether the messages should be high,\nTo change message transmission priority, do the following:\n normal, or low priority.\n \n * Individually - After reading a message, enter an 'X' at the 'Enter\n message action' prompt.\n\n - MailMan will ask you whether the message should be high, normal, or\n low priority.\n \n
\n\n", "\n- \n\n
\n", "", "2002-03-11 08:10:00\n", "", "USER,ONE\n", "", ""], ["1073", "XM-U-Q-SEARCH SYSTEM", "SEARCHING FOR MESSAGES - ANYWHERE ON THE SYSTEM\n", "", "", "\n \n * By Subject - You enter the string that the subject starts with, and\nMailMan will find all messages whose subject begins with the string. The\nstring must be in the exact upper/lower case. Case matters! This search\nis relatively quick.\n\n * By multiple [CRITERIA] - As with the [MAILBOX] search, you enter as\nmany criteria as you like to narrow the search, and MailMan will find all\nmessages matching the criteria. Unlike the Mailbox search, which covers only\nthe messages in your mailbox, this search covers all the messages on the\nsystem. This search can be very slow, depending on the criteria you enter.\nYou can search for any messages you ever sent or that were sent to you, if\nthey still exist anywhere on the system (i.e., located in the MESSAGE file),\nwhether they are in your mailbox or you deleted them long ago. If they're\nstill out there, MailMan will find them.\n\nUnder the 'Query/Search for Messages' option on the main MailMan menu,\nMailMan gives you two ways to search the entire system:\n\n
\n\n", "\n- \n\n
\n", "", "2002-05-02 14:37:00\n", "", "USER,ONE\n", "", ""], ["1074", "XM-U-H-GROUP-4", "MAIL GROUP INFORMATION (CONTINUED)\n", "", "", "\n \n - Distribution lists (nationwide mail groups)\n \n * Member of - list of mail groups to which the mail group belongs.\n \nThe group information can help you decide if you want to join a particular\nmail group (e.g., the description). Also, if a mail group doesn't allow\nself-enrollment, you can find out who the Coordinator or Organizer of the\ngroup is and ask if you can become a member of or remove yourself from a\nmail group. Also, if a mail group has Authorized Senders, you'll know to\nwhom you should send mail, if you want to address that particular mail group.\n * Member(s) - list of members for the mail group. Members will receive\n all mail addressed to the group. Members can include any of the\n following:\n \n - Local and remote users\n \n - Other mail groups (local mail groups)\n \n
\n\n", "", "", "2000-05-04 09:36:00\n", "", "USER,ONE\n", "", ""], ["1075", "XM-U-M-PRINT HEADER", "IDENTIFYING YOUR MESSAGE PRINTOUT\n", "", "", "\n \n \n * What time it was printed\nWhen you print a message, the print header appears at the top of the first\npage, and identifies it as yours.\n \nThe header includes:\n \n * Your name\n \n * At which site it was printed\n
\n\n", "", "", "1999-01-20 09:36:49\n", "", "USER,ONE\n", "", ""], ["1076", "XM-U-I-EDITOR FM SCREEN", "VA FILEMAN SCREEN EDITOR\n", "", "", "\n\ntext is immediately transferred to the selected editor.\nThe Full Screen Editor uses the PF set of function keys to perform word\nprocessing functions (e.g., setting margins and tabs, deleting text, and\nsaving text). Help text is available while using the editor. Users can\nalso switch from the Screen Editor directly to a different editor. The\noriginal text and formatting will then be transferred to the new editor.\n \nFor example, from within the VA FileMan Screen Editor, you can transfer\ntext to a different editor by entering PF1 and then the letter 'A'. Your\n
\n\n", "", "", "1999-01-20 16:17:00\n", "", "USER,ONE\n", "", ""], ["1077", "XM-U-Q-CLASSIC LOOKUP ??", "LOOKING FOR MESSAGES WHOSE SUBJECT BEGINS WITH A SPECIFIC STRING\n", "", "", "\n \nFor example, if you want to search for messages whose subject begins\nwith the words 'Schedule Reports', you would enter '??Schedule Reports'.\nSince this search is case sensitive, you must enter the string in the\ncorrect case. Thus, for example, 'SCHEDULE REPORTS' and 'Schedule Reports'\nare not considered by this search as being the same.\nWhile in a basket, you can search for messages anywhere on the system\nwhose subject begins with a certain string.\n \nAt the 'Basket Message' prompt, enter the string preceded by a '??'. You\nwill then be shown a list of those messages anywhere on the system, which\nyou ever sent or received, whose subject BEGINS with that string (case\nsensitive), and can choose which you would like to read.\n \n
\n\n", "", "", "1999-04-21 12:37:00\n", "", "USER,ONE\n", "", ""], ["1078", "XM-U-P-P-MESSAGE FROM", "P-MESSAGE FROM\n", "", "", "\n \nThere are two possible responses:\n * ME (default) - Answer ME if the message should be from you. It will\n not be delivered new to you, but you will be able to edit it.\n \n * POSTMASTER - Answer POSTMASTER if the message should be from the\n POSTMASTER. It will be delivered new to you, but you will not be able\n to edit it.\n \nNOTE: If you do not enter anything in this field, the default will be "ME."\n \nThe "P-MESSAGE FROM:" prompt pertains to anything you may print to the\nThe "P-MESSAGE FROM:" prompt can be set through the User Options Edit\noption on the Personal Preferences menu. \nP-MESSAGE device. MailMan allows you to decide from whom should the\nmessage be. The result is a message sent to you.\n \nIf you queue the print, this is from whom the message will be. If you\ndon't queue the print, this is the default that will appear in a dialogue\nwith MailMan to determine from whom the message will be.\n \n
\n\n", "", "", "1999-04-28 07:04:00\n", "", "USER,ONE\n", "", ""], ["1079", "XM-U-P-SHOW MESSAGE PREVIEW", "SHOW MESSAGE PREVIEW\n", "", "", "\n \nUse the "SHOW MESSAGE PREVIEW:" prompt (under Personal Preferences|\nUser Options Edit) to choose whether or not MailMan will display a preview\nof messages when you are scrolling through the messages in a basket using\nthe Classic message reader.\n \nThere are two possible responses:\n \n * YES - Preview messages when using the Classic message reader.\n \n * NO (default) - Don't preview messages when using the Classic message\nThe [CLASSIC] message reader can "preview" the next message to be read in\n reader.\na mail basket by displaying the message subject and sender, in addition to\nthe mail basket, and message number in that basket.\n \nSeeing the message subject and sender may help you decide whether or not\nyou wish to read the message. If you decide not to read the message, you\ncan "Ignore" it and move on to the next message.\n \n
\n\n", "\n- \n\n
\n", "", "1999-04-28 06:55:00\n", "", "USER,ONE\n", "", ""], ["108", "XUFILE ACCESS USE3.1", "AUDIT ACCESS TO FILES\n", "", "", "\nAudit privileges might be granted to advanced VA FileMan users who are\nin the Patient File, for example, could be audited. There are two choices\nfor the audit. An entry may be made in the Audit File when a value is\nentered or changed, or an entry may be made only when the value is changed,\nthat is, edited or deleted. The second may be all that's needed. In\nthe SSN example, you would monitor just the circumstances of the change, not\nof the initial SSN assignment.\n \nTo display the results of the audit, read access to the Audit File must be\ngranted. The Audit File, #1.1, may then be queried in the usual way.\ninterested in developing new audit capabilities. With audit access, which\nmust be accompanied by DD access, VA FileMan's 'Modify' option may be used\nto set an audit flag for a particular field within a file. (This access\ndoes not include setting audit conditions with MUMPS code which is\nreserved for the programmer-user, DUZ(0)=@.)\n \nThe data values for attribute fields may be recorded in the Audit File by\nsetting an audit flag in the data dictionary for that field. The SSN field\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1081", "XM-U-P-FILTER-3", "FILTERING MAIL (CONTINUED)\n", "", "", "\n \n * recipient, prior to delivery. This can be cumbersome for MailMan when*\n * a message has numerous recipients and each recipient has numerous *\n * active mail filters. Thus, to make the delivery process more *\n * efficient for everyone, we suggest you limit the number of active *\n * filters for your mailbox, use the least amount of filtering criteria *\n * necessary to positively identify the message, and prioritize each *\n * filter by using the ORDER field. Those filters that will be used the *\n * most should be given the highest priority (e.g., ORDER equals one, *\n * two, or three). *\n ************************************************************************\nAlso, when you create a mail filter and specify a mail basket that does\nnot currently exist in your mailbox, MailMan will allow you to create it\non the fly. Also, if you later delete a filter mail basket, MailMan will\nautomatically recreate it for you when the filter is used (activated) and\nmail is directed to that basket.\n \n ************************************************************************\n * MailMan's background processing checks active mail filters for each *\n
\n\n", "", "", "1999-04-27 15:17:56\n", "", "USER,ONE\n", "", ""], ["1082", "XM-U-M-NEW-2", "MAKE NEW MESSAGES NOT NEW AND VICE VERSA (CONTINUED)\n", "", "", "\n\n new toggle, including a [RANGE] of messages. Also, if you are using \n a full-screen reader, you can pre-[SELECT] messages and then new \n toggle them as a group. \n \n - MailMan will then make any new messages 'not new' and vice versa. \n \nEnter an 'L' ([LATER]) at the 'Enter message action' prompt to make the \nmessage appear new at a later date and time (even later today). The message\nwill be made new at the requested time. These actions can be used when a\nmessage cannot be handled immediately, or as a reminder of important\nTo toggle messages from New to 'Un New' or vice versa, do the following: \nactivities, making MailMan a personal reminder. \n \n * Individually - After reading a message, enter an 'N' at the 'Enter \n message action' prompt. \n \n * Group of Messages - Enter an 'NT' at the basket option or command prompt. \n \n - MailMan will first ask you to select which messages you want to \n
\n\n", "\n- \n\n
\n", "", "1999-12-13 14:44:00\n", "", "USER,ONE\n", "", ""], ["1083", "XM-U-M-NETWORK SIGNATURE", "ADD YOUR NETWORK SIGNATURE TO A MESSAGE\n", "", "", "\n \n \nBe careful. This is not a toggle. MailMan will add your network signature\nto the message every time you invoke the NS command.\nYou can use the Add Network Signature action code (i.e., 'NS') to add\nyour network signature to the end of your message.\n \nYou can create a [NETWORK SIGNATURE] using the User Options Edit option\nof the Personal Preferences menu.\n \nTo add your network signature to a message, enter 'NS' at the 'Select\nMessage option: Transmit now//' prompt.\n
\n\n", "\n- \n\n
\n", "", "1999-12-13 15:20:00\n", "", "USER,ONE\n", "", ""], ["1084", "XM-U-M-REPLY INCLUDE", "INCLUDE PREVIOUS RESPONSES IN YOUR REPLY\n", "", "", "\n \nto do it afterwards.)\n \nIf you enter 'I', you will be able to include the original message \nand/or any [COMBINATION] of responses in your reply. (With this feature, \nyou can more easily respond to what someone wrote, point by point.) \nEntering an 'I' at the 'Select Message option: Transmit now//' prompt\nenables you to add previous responses to your reply. You can then go back\nand edit your reply to comment on those responses you just added.\n \n(The usual method for commenting on previous responses is to enter 'RI'\nat the 'Enter message action' prompt to tell MailMan that you want to reply\nand include previous responses. The 'I' command is for those times when\nyou forgot to include responses before you composed your reply, and need\n
\n\n", "\n- \n\n
\n", "", "1999-12-13 15:46:00\n", "", "USER,ONE\n", "", ""], ["1085", "XM-U-M-INCLUDE MESSAGE", "INCLUDING A MESSAGE\n", "", "", "\n\nof the message to include, and then you will be able to include the\noriginal message and/or any [COMBINATION] of its responses in your message.\n \nAfter you've included the desired responses in the text of your message,\nyou can then [EDIT] the text your message.\nEntering an 'IM' enables you to include responses from another message\nin your message.\n \nThis command is available at the 'Select Message option: Transmit now//'\nprompt when creating a new message, or at the 'Select Edit option' prompt\nwhen editing a message you've sent only to yourself.\n \nIf you enter 'IM', you will be asked to enter the internal entry number\n
\n\n", "\n- \n\n
\n", "", "2000-05-15 09:36:00\n", "", "USER,ONE\n", "", ""], ["1086", "XM-U-P-FILTER ACTIONS", "FILTERING MAIL ACTIONS\n", "", "", "\n \na specified number of days after it is delivered to you. (Default is not\nto set any vaporize date.) This action will only apply to messages which\nare put into your mailbox (includes moving from the WASTE basket) as a\nresult of delivery or latering. It won't apply to messages which are\nalready in your mailbox.\n \n* Do NOT mark the message as NEW. (Default is to mark the message as NEW.)\nThis action will only apply to messages which you have not seen before.\n \n* Forward the message to others (including H. and D. devices). This action\nWhen a filter is activated during message delivery, in addition to directing\nwill only apply once per message. It won't apply to confidential, closed, or\notherwise sensitive messages. It won't apply to messages from you to yourself.\na message to a specific basket, you can direct MailMan to perform additional\noptional actions on the message. (Note that these actions are not performed\nwhen a filter is activated as a result of the 'FI' Filter basket action.)\n \nOptional filter actions during message delivery are:\n \n* Set the message VAPORIZE date to delete the message from your mailbox\n
\n\n", "", "", "2002-05-06 09:47:00\n", "", "USER,ONE\n", "", ""], ["1087", "XM-U-M-BROWSER", "PRINT TO THE VA FILEMAN BROWSER\n", "", "", "\n \n - Scroll forwards and backwards through a report. This means you don't lose\n reports "off the top" of the screen, like you do when you print to the\n HOME device. \n \n - Use the Search feature to find and immediately jump to any text.\n \n - Copy text from the message to the VA FileMan Clipboard; later, if you're\n editing a mail message or other WORD-PROCESSING-type field with the VA\n FileMan Screen Editor, you can paste from the clipboard.\n \nYour site manager may have set up an output device called BROWSER. If so,\nAs you become accustomed to using the BROWSER device, you may find that you\nstart to save paper by viewing messages that you'd otherwise end up printing.\nyou can view any message on it, rather than the conventional 'Backup' or\non paper. Do this by entering 'BR' at the "Enter Message Action: IGNORE//"\nprompt. (This has the same effect as Printing your message to the BROWSER\ndevice instead of the HOME device or a printer. It's a short cut.)\n\nThe Browser makes it easier to view messages on screen. Its main features are:\n \n
\n\n", "", "", "2000-05-25 00:00:00\n", "", "USER,ONE\n", "", ""], ["1088", "XM-U-M-VAPORIZE DATE EDIT-2", "VAPORIZE DATES (CONTINUED)\n", "", "", "\n\n to set the vaporize date for, including a [RANGE] of messages.\n Also, if you are using a full-screen reader, you can pre-[SELECT]\n messages and then set their vaporize date as a group.\n \n - MailMan will then ask you to confirm that you want to set the\n vaporize date, and will then ask you for that date.\nTo set a 'vaporize' date for messages, do the following:\n \n * Individually - After reading a message, enter a 'V' at the 'Enter\n message action' prompt. MailMan will ask you for the vaporize date.\n \n * Group of Messages - Enter a 'V' at the basket option or command prompt.\n \n - MailMan will first ask you to select which messages you want\n
\n\n", "\n- \n\n
\n", "", "2000-06-07 15:22:00\n", "", "USER,ONE\n", "", ""], ["1089", "XM-U-P-OPTIONS-4", "PERSONAL PREFERENCES (CONTINUED)\n", "", "", "\n \n * [P-MESSAGE FROM] - Choose who you want your P-MESSAGEs to be from.\n It makes a difference.\n\n[MORE]...\n * PRIORITY RESPONSES [FLAG] - Choose if you want to have responses to\n priority mail automatically delivered to you as priority or ordinary\n responses.\n \n * PRIORITY RESPONSES [PROMPT] - Choose if you want to be prompted each\n time to decide how future responses to a priority message are\n delivered to you.\n \n
\n\n", "\n- \n\n
\n", "", "2000-07-26 06:41:00\n", "", "USER,ONE\n", "", ""], ["109", "XUFILE ACCESS USE4.1", "HINTS FOR USE OF THE FILE ACCESS OPTIONS\n", "", "", "\n \n \n \n [DUZ] What's this DUZ# that shows next to the user's name?\n \n \n \n \n \nWhen using the file access options, you might have some questions about the\nfollowing topics:\n \n \n [QUEUING] What are the queuing questions all about?\n \n \n [FILE RANGES] How do I specify a range of file numbers?\n
\n\n", "\n- \n\n
\n", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1090", "XM-U-P-READ NEW MSGS BSKT", "READ NEW MESSAGES BASKET PRIORITY\n", "", "", "\n \n \nIf you deviate from the suggested priority basket, MailMan will stop\nsuggesting priority baskets, and will simply suggest the next basket in\nalphabetical order.\n \nOnce all the priority baskets have been read, MailMan will suggest baskets\nin alphabetical order.\n \nTo select baskets and their priority order, use the User Options Edit\noption on the Personal Preferences menu. \nWhen you read new messages by basket, MailMan suggests the IN basket to\nread first. If you want MailMan to suggest other basket(s) before\nsuggesting the IN basket, then select a basket and choose its relative\npriority (from 1 to 99). (You will not be able to choose the IN basket.)\n \nWhen you go to read new messages, if any of those baskets contain new\nmessages, MailMan will suggest reading them first, in the priority order\nyou set. The IN basket will be suggested last.\n
\n\n", "", "", "2000-07-26 07:09:11\n", "", "USER,ONE\n", "", ""], ["1091", "XM-U-P-NEW MESSAGES READ ORDER", "NEW MESSAGES READ ORDER\n", "", "", "\n \n \nGenerally, the basket message sequence number order will correspond to the\nmessage date sent order with the following exceptions:\n \n * Messages not originally sent to you but forwarded to you at a later\n date.\n \n * Messages sent from another location via the network (e.g., messages\n from a different site, FORUM messages).\n \nMailMan lets you choose the order in which you read your new messages:\nTo set your new message read order, use the User Options Edit option on the\nPersonal Preferences menu to answer the 'NEW MESSAGES READ ORDER:' prompt.\n\n 1. Newest First - This means that your new messages are read in reverse\n order (i.e., highest to lowest basket message sequence number order).\n \n 2. Oldest First - This means that your new messages are read in message\n number order (i.e., lowest to highest basket message sequence number\n order). This is the default if you don't choose an order.\n
\n\n", "", "", "2000-07-26 07:34:00\n", "", "USER,ONE\n", "", ""], ["1092", "XM-U-P-NEW MESSAGES OPTION", "NEW MESSAGES DEFAULT OPTION\n", "", "", "\n \nThe 'New Messages and Responses' option on the main menu brings up another\n[MENU] of choices. You may choose the default choice.\n \nIf you don't choose, then the default choice is 'Read new messages by basket'.\n\nTo set your default choice, use the User Options Edit option on the\nPersonal Preferences menu to answer the 'NEW MESSAGES DEFAULT OPTION:' prompt.\n
\n\n", "\n- \n\n
\n", "", "2000-07-26 07:53:00\n", "", "USER,ONE\n", "", ""], ["1093", "XM-U-Q-SEARCH CRITERIA USERS", "SEARCH CRITERIA - SENDERS AND ADDRESSEES\n", "", "", "\n\n or a mail group, server, or device. MailMan will check the addressees\n that you see when you [QUERY] ('Q') the message. MailMan will not check\n the expanded list of addresses that you see when you use the\n Query Detailed ('QD') action code.\n \n When searching on the addressee of a message, enter the 'T' ('Message\n to') search action code and then enter the [LOCAL] USER NAME or\n [REMOTE] USER NAME.\n * Sender of the Message - Enter the 'F' ('Message from') search action\n code and then enter the [LOCAL] USER NAME or [REMOTE] USER NAME.\n\n * Sender of a Response to the message - Enter the 'R' ('Response from')\n search action code and then enter the [LOCAL] USER NAME or\n [REMOTE] USER NAME.\n \n * Addressee of a Message - This includes messages addressed to a person\n\n\n", "\n- \n\n
\n", "", "2000-08-30 08:50:00\n", "", "USER,ONE\n", "", ""], ["1094", "XM-U-Q-SEARCH CRITERIA DATE", "SEARCH CRITERIA - DATE SENT\n", "", "", "\n \n * If you are searching for messages anywhere on the system, whether they\n are in your mailbox or not, then a date range is mandatory, and defaults\n to the last 30 days, which you are free to change. (If you are only\n searching your mailbox, then these are optional.)\n You may specify approximately when the message was sent.\n \n - Enter the 'DA' ('Message sent on or after') search action code\n to enter the lower end of the date range.\n \n - Enter the 'DB' ('Message sent on or before') search action code\n to enter to upper end of the date range.\n \n\n\n", "", "", "2002-07-12 10:25:00\n", "", "USER,ONE\n", "", ""], ["1095", "XM-U-Q-SEARCH CRITERIA TEXT", "SEARCH CRITERIA - TEXT CONTENTS\n", "", "", "\n \n \n - Only the message responses text.\n \n - Both the original message and responses text.\n \n NOTE: If the string you are searching for is not all on one line in\n the message/responses, the search will not be able to find it.\n * Specific Text in a Message - Enter the 'X' ('Message contains') search\n action code and then enter any portion of the message text string. The\n string can be from 3 to 30 characters in length (including spaces,\n symbols, and punctuation marks). MailMan prompts you to decide if the\n text search should be case sensitive. MailMan also prompts you to\n decide if the search should include:\n \n - Only the original message text.\n\n\n", "", "", "2000-08-30 09:16:27\n", "", "USER,ONE\n", "", ""], ["1096", "EAS EZ OPTION PROCESS", "10-10EZ PROCESSING\n", "", "", "\nThere are six Processing Status categories used to organize interaction \n \nBasic information about a 10-10EZ Application, including its\ncurrent Processing Status, can be obtained by using the 1010EZ\n[Quick Lookup] option on the main 10-10EZ Menu.\n \nFurther information is also available on the initial List Manager\ndisplay [screen].\nwith the 10-10EZ module:\n \n [NEW] [IN REVIEW] [PRINTED, PENDING SIGNATURE]\n \n [SIGNED] [FILED] [INACTIVATED]\n \nA given Application can be in only one Processing Status at any point \nin time. \n
\n\n", "\n- \n\n
\n", "", "2001-03-28 09:56:00\n", "", "USER,ONE\n", "", ""], ["1097", "EAS EZ STATUS NEW", "NEW\n", "", "", "\nA NEW Application is one that has been recently received by the VAMC via \nMailMan after being submitted by the veteran from the On-Line 10-10EZ \nwebsite. Its data has been filed into a 1010EZ HOLDING file (#712) record.\n \nActions that may be performed for NEW Applications are:\n \n[LZ] Link to Patient File\n[IZ] Inactivate 1010EZ\n \n
\n\n", "\n- \n\n
\n", "", "2001-03-28 10:06:02\n", "", "USER,ONE\n", "", ""], ["1098", "EAS EZ STATUS IN REVIEW", "IN REVIEW\n", "", "", "\nFor an application IN REVIEW, the link to the VISTA database has been\n \nActions that may be performed for IN REVIEW Applications are:\n \n[AF] Accept Field\n[AZ] Accept All\n[CZ] Clear All\n[RZ] Reset to New\n[PZ] Print 1010EZ\n[VZ] Verify Signature\n[UF] Update Field\nestablished. If the applicant is linked to an existing patient, the data\n[IZ] Inactivate 1010EZ\nfrom that patient record is displayed on the screen along side the 10-10EZ\ndata for comparison. If the applicant cannot be matched to an existing \npatient record, then a new patient record is created. Of course, in that\ncase, no comparison data can be displayed.\n \nIf the linkage is found to be incorrect, the enrollment clerk will need\nto reset the status of the application back to NEW and restart the process.\n
\n\n", "\n- \n\n
\n", "", "2001-03-28 10:07:33\n", "", "USER,ONE\n", "", ""], ["1099", "EAS EZ STATUS PRINTED", "PRINTED, PENDING SIGNATURE\n", "", "", "\nOnce an Application has been printed using the Print 1010EZ (PZ) action, \n \n[RZ] Reset to New\n[PZ] Print 1010EZ\n[VZ] Verify Signature\n[IZ] Inactivate 1010EZ\nits status becomes PRINTED, PENDING SIGNATURE. The printed form will \ncontain the accepted data elements from the 10-10EZ. Data elements which \nwere not accepted will not be used. If the applicant was matched to an \nexisting VISTA patient, then data from that patient record will be used \non the printed form in place of non-accepted 10-10EZ data elements. \n \nActions that may be performed for PRINTED, PENDING SIGNATURE Applications \nare:\n
\n\n", "\n- \n\n
\n", "", "2001-03-28 10:08:09\n", "", "USER,ONE\n", "", ""], ["11", "XQHELP-FILE", "THE HELP FRAME FILE\n", "", "", "\nThe Help Frame file is exported with the Kernel. Some of the fields are:\nINVOKING - routines which reference this help frame\nAUTHOR - the creator of this frame (triggered)\nDATE ENTERED - the date the frame was created (triggered)\nEDITOR - those users who may edit the frame\nDATE UPDATED - the last date the text was changed (computed)\n \nNAME - a short internal name with package prefix\nHEADER - a brief description of the frame to appear as a header\nTEXT - multiple lines of description information, containing\n keywords in brackets which will indicate a related frame.\nRELATED - a multiple field containing the name of the keyword\nFRAME which will invoke more help text, and the name of the\n help frame which contains this text.\n
\n\n", "", "", "1992-04-15 15:27:00\n", "", "USER,ONE\n", "", ""], ["110", "XUFILE ACCESS USE1.1", "THE PURPOSE FOR GRANTING FILE ACCESS\n", "", "", "\nWhat is the purpose of file access? Why bother specifying who has access to\n - to reserve DUZ(0), the VA FileMan access code, as a security measure\n to protect just templates and fields, not files.\n \nAs you grant file access, you will know who has access to which files and\nwhat kind of access they have. You may also retrieve this information by\nuser or by file. Privileges may also be entirely restricted for an\nindividual user or for a single file that may contain sensitive information.\nwhich files? The answer is threefold:\n \n - to monitor the use of VA FileMan,\n \n - to regulate the extent of VA FileMan access from among six forms\n which allow read, write, delete, laygo, data dictionary, or audit\n access,\n \n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1100", "EAS EZ STATUS SIGNED", "SIGNED\n", "", "", "\nAfter the enrollment clerk verifies that a 10-10EZ form has been received \nActions that may be performed for SIGNED Applications are:\n \n[PZ] Print 1010EZ\n[UF] Update Field\n[FZ] File 1010EZ\n \nIt is possible to remove signature verification from a 10-10EZ\nby invoking the [Remove Signature Verification] menu option.\nwith the Applicant's signature, its status is SIGNED.\n \nIt is not necessary to use Print 1010EZ before using Verify Signature. If\nthe enrollment clerk has not made any significant change to the original \n10-10EZ data, and if the Applicant sent a signed 10-10EZ to the site, then \nthe enrollment clerk can issue the VZ command when the application is \nIN REVIEW.\n \n
\n\n", "\n- \n\n
\n", "", "2001-03-28 10:08:33\n", "", "USER,ONE\n", "", ""], ["1101", "EAS EZ STATUS FILED", "FILED\n", "", "", "\nOnly data from a SIGNED form may be FILED to VISTA. Only accepted data will\n \nThe only Action that may be performed for FILED Applications is:\n \n[PZ] Print 1010EZ\nbe placed in the Patient record.\n \nAfter filing, the Applicant's data can be viewed and modified through other \nVISTA functions, such as Registration and Means Testing.\n \nApplications will remain on the FILED screen list for only 30 days after\nthe filing date. Use the 1010EZ [Quick Lookup] option to view basic\ninformation for any Application.\n
\n\n", "\n- \n\n
\n", "", "2001-03-28 10:08:47\n", "", "USER,ONE\n", "", ""], ["1102", "EAS EZ STATUS INACTIVE", "INACTIVATED\n", "", "", "\nIt may be determined that an Application is invalid, cancelled, or for\nafter the inactivation date. Use the 1010EZ [Quick Lookup] option to\nview basic information for any Application.\n \nThere are no Actions that may be used for INACTIVATED Applications.\nsome reason cannot be processed further. The enrollment clerk may \ninactivate (i.e., close) the application to prevent inadvertent filing of \nthe data.\n \nA 10-10EZ Application may be INACTIVATED at any time before it has been \nSIGNED.\n \nApplications will remain on the INACTIVATED screen list for only 30 days \n
\n\n", "\n- \n\n
\n", "", "2001-03-28 10:09:05\n", "", "USER,ONE\n", "", ""], ["1103", "EAS EZ SCREEN INITIAL", "INITIAL LIST MANAGER DISPLAY\n", "", "", "\nA listing will be displayed for the Processing Status selected which\nA specific Application is selected from the list by entering the \nappropriate [Line #]. In this example the Application appearing on\nLine #1 is selected for processing:\n \n Select Action: Next Screen//EZ=1\n \nshows all Applications in that status. The sort order of the list is by \nStation Number, and within Station Number by Applicant Name.\n \nThe data displayed on each line of the listing is as follows:\n \n[Line #] [Applicant] [SSN] [Vet. Type] [Rec'd] [Print] [To] [App.#]\n 1 JONES,RALPH R. 123-45-6789 NSC 11/12/00 VA 599GB 108\n \n
\n\n", "\n- \n\n
\n", "", "2001-03-28 19:45:00\n", "", "USER,ONE\n", "", ""], ["1104", "EAS EZ ACTION LZ", "LINK TO PATIENT FILE (LZ)\n", "", "", "\nThe veteran associated with a NEW Application must be 'linked' to\nthe VistA Patient database.\n \nThe VistA Patient Lookup function is employed to match the applicant\nto an existing Patient OR to establish a new Patient record.\n \nAfter this linkage is performed, the Processing Status of the \nApplication is IN REVIEW.\n
\n\n", "", "", "2001-03-28 11:29:59\n", "", "USER,ONE\n", "", ""], ["1105", "EAS EZ OPTION LOOKUP", "10-10EZ QUICK LOOKUP\n", "", "", "\n10-10EZ Quick Lookup is an option of the main 10-10EZ Menu. It can be \nmethods are used, the characters must be entered exactly as provided by \nthe veteran in the On-Line 10-10EZ application. An Applicant SSN must be \nentered as nnn-nn-nnnn. Likewise, a Web Submission ID must be entered as\nall numerics with hyphens inserted as needed. \nused to obtain basic data for any 10-10EZ Application, including its \ncurrent Processing Status.\n \nLookup can be done using the Application #, Web Submission ID, Applicant \nName, or Applicant SSN. \n \nThe Applicant Name method is the only one of the four lookup methods that \nuses alphabetic characters. If Web Submission ID or Applicant SSN \n
\n\n", "", "", "2001-03-28 13:50:28\n", "", "USER,ONE\n", "", ""], ["1106", "EAS EZ ACTION IZ", "INACTIVATE 1010EZ (IZ)\n", "", "", "\nOnce the Application is INACTIVATED, it will no longer be available\nfor processing. It cannot be re-activated.\n \nUse this action only if the Application is deemed invalid or is being\nreplaced by a new Application for the same veteran.\n
\n\n", "", "", "2001-03-28 14:10:53\n", "", "USER,ONE\n", "", ""], ["1107", "EAS EZ ACTION PZ", "PRINT 1010EZ (PZ)\n", "", "", "\nThe 10-10EZ form is printed using all 'accepted' data. VistA Patient \n \nThe PZ action prints the 10-10EZ form with data. But a simple printout\nof all data shown on the List Manager screens can be obtained by\nusing the hidden action Print Screen (PS).\ndata is used, if available, for any field not 'accepted'.\n \nForm printing done by Print 1010EZ (PZ) must be queued to a valid\nprint device capable of accommodating 132 characters per line.\n \nOnce the 10-10EZ is printed, actions of Accept Field, Accept All,\nClear All, and Update Field can no longer be used. The Processing\nStatus becomes PRINTED, PENDING SIGNATURE.\n
\n\n", "", "", "2001-03-28 14:13:26\n", "", "USER,ONE\n", "", ""], ["1108", "EAS EZ ACTION FZ", "FILE 1010EZ (FZ)\n", "", "", "\nAll 'accepted' data elements on the 10-10EZ are filed to the VistA \n Eligibility Status is "Verified" by HEC.\n(3) The Purple Heart indicator cannot be filed.\n(4) If the site holds an income test on the Patient for the current \n income year, then income data cannot be filed. This includes \n Spouse and Dependent data.\n \nAlso note, health insurance and Medicare data are not directly filed\nto the Patient record. Instead, this data is placed in the Insurance\nBuffer file for processing by Integrated Billing (MCCR).\nPatient database through the File 1010EZ (FZ) action, and the Processing\nStatus of the Application is FILED.\n \nIn most cases, 10-10EZ data elements will overwrite any existing data in\nVistA. Exceptions are as follows:\n \n(1) The Patient's Name, SSN, and Date of Birth cannot be overwritten.\n(2) Eligibility related data cannot be overwritten if the Patient's\n
\n\n", "", "", "2001-03-28 14:20:16\n", "", "USER,ONE\n", "", ""], ["1109", "EAS EZ ACTION AF", "ACCEPT FIELD (AF)\n", "", "", "\n10-10EZ data can be 'accepted' on a field-by-field basis for later filing\nthe List Manager screens with all data elements 'accepted'. If necessary,\nuse the ACCEPT FIELD action to remove the 'accepted' indicator.\n \nAlso note, financial data for all Applicants is automatically 'accepted', \nand the 'accepted' indicator cannot be removed. Financial data includes\nhealth insurance and Medicare information, Spouse and Dependent demographic\ndata, as well as all income data.\ninto the VistA Patient database by using the Accept Field (AF) action.\nAn 'accepted' data element is indicated by display of the data in\nreverse video format.\n \nUsing this action on a previously 'accepted' data element, removes the\n'accepted' indicator.\n \nApplications for persons who are new to the Patient database will appear on\n
\n\n", "", "", "2001-03-28 14:32:51\n", "", "USER,ONE\n", "", ""], ["111", "XUFILE ACCESS USE3.2", "LEVELS OF ACCESS CONTINUED\n", "", "", "\nThese are the six levels of access. Any or all may be enabled for each of\nVA FileMan access code, DUZ(0), will be checked. Access will be limited if\nthe user's DUZ(0) doesn't contain a character matching the field protection.\nAgain, DUZ(0)=@ will override this restriction.\n \nThe last two kinds of access - DD and audit - pertain to the structure of\nthe file itself. While this provides a generous scope for VA FileMan\ndata dictionary modification, it falls short of, for example, deleting a\nfile or field protected with '@'. \n \nThe same applies to templates. If the template is protected, the user who\nthe user's accessible files. This is done by changing the field value from\nhas access to the file will not have VA FileMan access to the template\nunless there is a match in the DUZ(0) character string.\nnull to 'YES'. This flag is overriden for programmer-users whose DUZ(0)=@.\n \nGranting all of the first four levels of access - read, write, delete, and\nlaygo - will permit adding and deleting file entries as well as editing\ntheir attribute field data values. This will be true unless the attribute\nfield has been protected. If so, that is, if there is a read, write, or\ndelete protection within the data dictionary for a given field, the user's\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1110", "EAS EZ ACTION AZ", "ACCEPT ALL (AZ)\n", "", "", "\nAll 10-10 EZ data elements can be 'accepted' for later filing into the \nand the 'accepted' indicator cannot be removed. Financial data includes\nhealth insurance and Medicare information, Spouse and Dependent demographic\ndata, as well as all income data.\nVistA Patient database by the Accept All (AZ) action.\n \nApplications for persons who are new to the Patient database will always \nappear on the List Manager screens with all data elements 'accepted'. If \nnecessary, use the ACCEPT FIELD action to remove the 'accepted' indicator\non individual fields.\n \nAlso note, financial data for all Applicants is automatically 'accepted', \n
\n\n", "", "", "2001-03-28 15:04:06\n", "", "USER,ONE\n", "", ""], ["1111", "EAS EZ ACTION CZ", "CLEAR ALL (CZ)\n", "", "", "\nThe CLEAR ALL (CZ) action will remove the 'accepted' indicator from any \nfields previously 'accepted' using ACCEPT FIELD (AF) or ACCEPT ALL (AZ).\n
\n\n", "", "", "2001-03-28 16:41:29\n", "", "USER,ONE\n", "", ""], ["1112", "EAS EZ ACTION RZ", "RESET TO NEW (RZ)\n", "", "", "\nThe Reset to New (RZ) action returns the Application to the NEW \nProcessing Status. All 'accepted' indicators are removed, any data\nentered through Update Field (UF) is deleted, and all processing\nhistory is cleared.\n \nThe Applicant can be re-linked to the VistA Patient database.\n
\n\n", "", "", "2001-03-28 16:46:13\n", "", "USER,ONE\n", "", ""], ["1113", "EAS EZ ACTION VZ", "VERIFY SIGNATURE (VZ)\n", "", "", "\nConfirmation that the Applicant's signature appears on the printed\n10-10EZ is done through the Verify Signature (VZ) action. The \nProcessing Status of the Application then becomes SIGNED.\n \nIt is possible to remove signature verification from a 10-10EZ\nby invoking the [Remove Signature Verification] menu option.\n
\n\n", "\n- \n\n
\n", "", "2001-03-28 16:56:34\n", "", "USER,ONE\n", "", ""], ["1114", "EAS EZ ACTION UF", "UPDATE FIELD (UF)\n", "", "", "\nThe original value of a 10-10 EZ data element can be overwritten by the \nuser through the Update Field (UF) action.\n \nThis action should be used to enter any hand-written changes the Applicant\nmakes to the signed 10-10EZ.\n \nAn 'updated' field is automatically 'accepted' for filing into the \nVistA Patient record. The 'accepted' indicator cannot be removed.\n
\n\n", "", "", "2001-03-28 16:57:35\n", "", "USER,ONE\n", "", ""], ["1115", "EAS EZ DEFINE LINE#", "Line # Column\n", "", "", "\nThe Line # column is the first column of the initial List Manager\nscreen display. It is a simple, sequential number used to select\nan Application for further processing.\n
\n\n", "", "", "2001-03-28 18:41:21\n", "", "USER,ONE\n", "", ""], ["1116", "EAS EZ DEFINE APPLICANT", "Applicant Column\n", "", "", "\nApplicant is the second column of the initial List Manager screen\ndisplay. The Applicant's Name as entered in the On-Line 10-10EZ\nappears in this column.\n
\n\n", "", "", "2001-03-28 18:42:29\n", "", "USER,ONE\n", "", ""], ["1117", "EAS EZ DEFINE VET TYPE", "Vet. Type Column\n", "", "", "\nVet. Type is the fourth column of the initial List Manager screen\n SC <50%\n SC 50-100%\n MIL. RETIREE\n POW\n PURPLE HEART\ndisplay. Veteran Type is derived from data that the Applicant has\nprovided in the On-Line 10-10EZ.\n \nThere are six possible values that may appear in the Vet. Type\ncolumn:\n \n NSC\n SC 0%\n
\n\n", "", "", "2001-03-28 18:43:48\n", "", "USER,ONE\n", "", ""], ["1118", "EAS EZ DEFINE REC'D", "Rec'd Column\n", "", "", "\nThe date appearing in the Rec'd column of the initial List Manager\ndisplay screen indicates the date on which the Application was\nelectronically received by the facility VistA system.\n
\n\n", "", "", "2001-03-28 18:44:26\n", "", "USER,ONE\n", "", ""], ["1119", "EAS EZ DEFINE PRINT", "Print Column\n", "", "", "\nPrint is the sixth column of the initial List Manager screen\ndisplay. One of two values will be displayed in this column:\n \n Vet ==> The veteran has indicated that he will print and\n sign the 10-10EZ and mail it to the VA facility.\n \n VA ==> The veteran has indicated that he will not print\n the 10-10EZ form. The VA facility should print\n the form and send it to the veteran for signature.\n
\n\n", "", "", "2001-03-28 18:44:58\n", "", "USER,ONE\n", "", ""], ["112", "XUFILE ACCESS USE4.11", "QUEUING FILE ACCESS SPECIFICATIONS\n", "", "", "\n \nrequested time of 'NOW'. Otherwise you'll need to wait patiently for the\njob to finish.\n \nWhen using the file access options, were you confused by the message about\nqueuing? Most of the options give you the opportunity to queue when you're\nfinished specifying who is to be granted which files. Queuing will send\nyour specifications to the Task Manager to assign to users at a later time.\n \nChoose to queue at an off-peak time, like midnight, when the system isn't\nbusy. The processing can be done then and you don't need to wait for the\nlong pause now. If the system isn't busy, you should still queue at the\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1120", "EAS EZ DEFINE TO", "To Column\n", "", "", "\nThe To column is the next-to-last column on the initial List Manager\nscreen display. This column shows the Station Number of the\nVHA facility which the Applicant has designated as his Preferred\nFacility.\n \nThe Applications appearing on the displayed list are sorted by\nStation Number, then within Station Number by Applicant Name.\n
\n\n", "", "", "2001-03-28 18:45:27\n", "", "USER,ONE\n", "", ""], ["1121", "EAS EZ DEFINE APP#", "App.# Column\n", "", "", "\nThe App.# column is the last column on the initial List Manager\nscreen display. The number appearing in this column is the \nunique number assigned by the 1010EZ module to the Application.\n
\n\n", "", "", "2001-03-28 18:46:01\n", "", "USER,ONE\n", "", ""], ["1122", "EAS EZ OPTION REMOVE SIG VERIF", "REMOVE SIGNATURE VERIFICATION\n", "", "", "\nThis 1010EZ menu option allows the user to remove signature\nverification from a 10-10EZ Application. The status of the\nApplication will revert from 'Signed' to either 'In Review'\nor 'Printed, Pending Signature' as appropriate for the\nApplication.\n
\n\n", "", "", "2001-04-06 17:24:04\n", "", "USER,ONE\n", "", ""], ["1123", "EAS EZ DEFINE SSN", "SSN Column\n", "", "", "\nSSN is the third column of the initial List Manager screen display.\nThis column shows the veteran's Social Security Number (SSN) as\nentered by the veteran in the On-Line 10-10EZ.\n
\n\n", "", "", "2001-05-14 16:34:12\n", "", "USER,ONE\n", "", ""], ["1124", "ECPERSONACCESS", "Access to DSS Units by User\n", "", "W @IOF\n", "\nThis menu option is used to allocate and deallocate DSS units for particular users.\n
\n\n", "", "", "2001-05-24 11:00:05\n", "", "USER,ONE\n", "", ""], ["1125", "ECSPREADSHEET", "Spreadsheet Upload\n", "", "W @IOF\n", "\nThis menu option is used to upload encounters into the Event Capture patient file. Errors are reported, and the user has the opportunity to correct the errors and upload the corrected records.\n
\n\n", "", "", "2001-05-24 11:47:24\n", "", "USER,ONE\n", "", ""], ["1126", "ECSSRECORD", "Record Number\n", "", "W @IOF\n", "\nThe record number is a unique number that is used to associate error messages with the correct row of data. This is a required field.\n
\n\n", "", "", "2001-05-29 13:27:19\n", "", "USER,ONE\n", "", ""], ["1127", "ECSSSTATION", "Location\n", "", "W @IOF\n", "\nThe location must exist in the Institution file (#4).\n \nFor State Home spreadsheet uploads, the location is automatically \npopulated and is the Internal Entry Number (IEN).\n \nFor regular spreadsheet uploads, the location is the station number.\n
\n\n", "", "", "2001-05-29 13:44:27\n", "", "USER,FIFTYFOUR\n", "", ""], ["1128", "ECSSPATSSN", "Patient SSN\n", "", "W @IOF\n", "\nThe patient SSN must exist on the Patient File (#2, ^DPT). If the SSN is\nshorter than 9 digits, it will be left filled with zeros.\n
\n\n", "", "", "2001-05-29 13:46:33\n", "", "USER,FIFTYFOUR\n", "", ""], ["1129", "ECSSPATLNAME", "Patient Last Name\n", "", "W @IOF\n", "\nThe patient's name (last name,first name) must match the name on the Patient file for that SSN.\n
\n\n", "", "", "2001-05-29 13:48:05\n", "", "USER,ONE\n", "", ""], ["113", "XUFILE ACCESS USE4.12", "USING RANGES OF FILE NUMBERS\n", "", "", "\n \n \nFile numbers are also used when printing a group of consecutive files. You\nwill be asked for a place to start with a default file name presented. To\nprint just this one file, respond to the next prompt with a carriage return\nand thereby accept the default of ending after printing that one file.\n \nTo print a consecutive range of files, enter the lowest number as the\nstarting point and the highest number as the ending point. All your files\nthat fall in this range will be printed.\nWere you able to specify files by number ranges? It will be useful to do\nthis when granting several files at once. First find out the number of the\nfiles. Typing a question mark at the 'to files:' prompt will display the\nnumber and name of the files. Note the numbers. Then put them together\non one line. You may uses dashes to indicate a consecutive range. Then \nuse commas to separate the single numbers and dashed groups as follows:\n \n 2,3,4,6,7,8,125,236,799 or 2-4,6-8,124,236,799\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1130", "ECSSPATFNAME", "Patient First Name\n", "", "W @IOF\n", "\nThe patient's name (last name,first name) must match the name on the Patient file for that SSN.\n
\n\n", "", "", "2001-05-29 13:49:50\n", "", "USER,ONE\n", "", ""], ["1131", "ECSSDSSNAME", "DSS Unit Name\n", "", "W @IOF\n", "\nThe DSS Unit Name is not required if the DSS Unit IEN is filled in.\n
\n\n", "", "", "2001-05-29 13:51:15\n", "", "USER,FIFTYFOUR\n", "", ""], ["1132", "ECSSDSSNUM", "DSS Unit Number\n", "", "W @IOF\n", "\nThe DSS Department is no longer being used to identify the DSS Unit as it\nisn't unique. If you enter a value in this field, it will be ignored. \nUse the DSS Unit Name or the DSS Unit IEN to identify the DSS Unit.\n
\n\n", "", "", "2001-05-29 13:53:12\n", "", "USER,FIFTYFOUR\n", "", ""], ["1133", "ECSSDSSIEN", "DSS Unit IEN\n", "", "W @IOF\n", "\nThe DSS Unit IEN is not required if the DSS Unit Name is filled in.\n
\n\n", "", "", "2001-05-29 13:54:02\n", "", "USER,FIFTYFOUR\n", "", ""], ["1134", "ECSSPROCCODE", "Procedure Code\n", "", "W @IOF\n", "\nThis is the procedure/cpt code value (not the description). The National Procedure, Local Procedure, and CPT code are all valid for this column. The procedure/cpt must exist on the EC National Procedure file (#725) or the CPT file (#81), and\nthe EC Event Code Screen must be 'active' for the Station, DSS Unit IEN, and Procedure/CPT combination.\n
\n\n", "", "", "2001-05-29 13:54:57\n", "", "USER,ONE\n", "", ""], ["1135", "ECSSVOLUME", "Volume\n", "", "W @IOF\n", "\nThe volume must be a number from 1 through 99.\n
\n\n", "", "", "2001-05-29 13:55:53\n", "", "USER,ONE\n", "", ""], ["1136", "ECSSORDSECT", "Ordering Section\n", "", "W @IOF\n", "\nThis is the name of the Ordering Section. If the user enters an ordering section into the spreadsheet, it will be validated against the "B" cross reference in the Medical Specialty file, #723. If the user leaves this field blank, the program\nwill derive the Ordering Section from DSS Unit file #724, using the DSS Unit IEN.\n
\n\n", "", "", "2001-05-29 13:56:51\n", "", "USER,ONE\n", "", ""], ["1137", "ECSSPROVLNAME", "Provider Name or IEN\n", "", "W @IOF\n", "\nThe provider's name (last name,first name) must have a "B" cross \nreference and exist in the New Person file (#200). The provider must \nhave an active Person Class unless the DSS unit is set to send no records \nto PCE. In that case, Non Licensed Providers, as identified by using the \n"Providers" option on the management menu, may be selected.\n \nThe provider's IEN may be entered instead of the name.\n
\n\n", "", "", "2001-05-29 13:57:59\n", "", "USER,FIFTYFOUR\n", "", ""], ["1138", "ECSSENCDATETIME", "Encounter Date/Time\n", "", "W @IOF\n", "\nThe Encounter Date/Time can be in any valid FileMan format. The 'seconds' are optional, and the month, day, and year can be separated by any of the 32 special characters (non numeric, non alpha) except '^' and '@'.\nN, N-1, N-5h, etc.\n \n \nExamples:\nmm/dd/yy @hh:mm:ss\nmm/dd/yyyy @hh:mm:ss\nmm-dd-yy @hh:mm\nmmm dd,yyyy @hhmm\nmmddyy@hhmm\n
\n\n", "", "", "2001-05-29 13:59:36\n", "", "USER,ONE\n", "", ""], ["1139", "ECSSDIAGCODE", "Diagnosis Code\n", "", "W @IOF\n", "\nThis is the primary diagnosis code value. It must exist in the ICD \nDiagnosis file (#80).\n \nNote: The Diagnosis Code is only required for records sent to PCE, and \nwill be ignored otherwise. For DSS units set up as 'OOS', the diagnosis \nfield will be ignored.\n
\n\n", "", "", "2001-05-29 14:02:31\n", "", "USER,FIFTYFOUR\n", "", ""], ["114", "XUFILE ACCESS USE4.13", "UNDERSTANDING DUZ - THE USER NUMBER\n", "", "", "\n \nused. That's what becomes the value of DUZ.\n \nYou'll notice that some users have low numbers while others have high ones.\nThis simply indicates the order of their names in the User File. Users\nwith low numbers are often people who began using your system some years\nago, while users with high numbers are recent members of your computing\ncommunity. Other than this curiosity, though, DUZ has no special meaning \nfor an individual user.\nWhen listing the file accesses by user or by file, you will see the user's\nname followed by a number in parentheses. The heading indicates that this\nis the DUZ#. What could it be?\n \nDUZ is a local variable which identifies the user who has signed-on. Once\nthe user enters an access and verify code, the Kernel sign-on program (XUS)\nuses this variable to select an entry in the User File. It must be\nunique, so the user's name won't do. Instead, the internal entry number is\n
\n\n", "", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1140", "ECSSASSOCCLIN", "Associated Clinic\n", "", "W @IOF\n", "\nAn associated clinic must be identified if the DSS unit is set to send \nall records to PCE. \n \nYou may enter either the associated clinic name or the associated clinic\nIEN in the appropriate field. If you enter both, the IEN will be the only\ndata used to identify the associated clinic.\n
\n\n", "", "", "2001-05-29 14:03:14\n", "", "USER,FIFTYFOUR\n", "", ""], ["1141", "ECSSCATEGORY", "Category\n", "", "W @IOF\n", "\nEnter the event capture category for this record. If this field is left blank, the category will be assigned a value of zero.\n
\n\n", "", "", "2001-06-04 11:48:26\n", "", "USER,ONE\n", "", ""], ["1142", "ECPAT0", "Enter/Edit Patient Procedures Selection\n", "", "W @IOF\n", "\nThis screen allows you to select a patient to either add, update or \nNext, select a patient. If there were procedures done within the date \nrange specified a list of those procedures will be displayed.\n \nSelect an existing procedure, then click the 'Delete' button to remove\nthat procedure.\n \nSelect an existing procedure, then click the 'Update' button to modify\nthat record.\n \nClick the 'Add' button to add a procedure for the selected patient.\ndelete procedures performed.\n \nYou must first select a Location, then a DSS Unit within that Location.\n \nThe system defaults to the current date as the Date Range. You can change \nthe date range if desired by entering dates for Procedures From and \nProcedures Through. \n \n
\n\n", "", "", "2001-06-28 09:23:36\n", "", "USER,FIFTYFOUR\n", "", ""], ["1143", "XUDOC DEVICE ALT SYNTAX", "Alternate Syntax for Device Specification\n", "", "", "\n \nseparating punctuation to delimit the pieces. These codes specify:\n \n B Boldface\n L Page length\n M Margin\n P Pitch\n Q Quality (can be Q, Q1, or Q2)\n \nFor example, you could specify:\n \nAn alternate syntax is available for specifying right margin and page\n DEVICE: LASER;P-LASER-LANDSCAPE;/M132L100P16BQ2\n \nIn this example, the margin is set to 132 (M132), the page length to 100\nlines (L100), the pitch to 16 (P16), the intensity to bold typeface (B),\nand the quality set to letter quality (Q2). An absence of the B would\nindicate normal intensity. The quality settings are Q, Q1, and Q2.\n \nYour IRM needs to confirm that the appropriate code to set the specified\nprinter attributes is set up for the device that you are using. Then, when\nthe Device Handler closes the device, IRM needs to be sure that\nlength when responding to the device prompt. Using the alternate format,\nappropriate reset code is in the Close Execute field so that the\ncharacteristics do not stay in effect. If, for example, someone requests a\nsmall pitch, subsequent reports will also use the small pitch unless reset\nin the close execute statement for that device (or altered by the open\nexecute statement of the next device called).\nyou can specify pitch, intensity, and quality. The success of specifying\nthese additional attributes, however, depends on whether the corresponding\nfields have been defined by IRM at your site.\n \nThe syntax requires the use of a slash (/) after the last semicolon. You\ncan then use the letters B, L, M, P, and Q in any order, without\n
\n\n", "", "", "2001-07-19 11:01:03\n", "", "USER,ONE\n", "", ""], ["1144", "XM-U-K-PACKMAN", "PACKMAN - MOVING ROUTINES AND DATA IN MESSAGES\n", "", "", "\n\n [PACKAGE] LOAD Loads a package as defined in the PACKAGE file. \n\nINSTALLING a PackMan message:\n [PRINT] MESSAGE Prints message, but recognizes content and puts it \n into a more easily read format than the standard \n message print. \n [SUMMARIZE] MESSAGE Summarizes the message content. \n [COMPARE] MESSAGE Compares routines in a PackMan message to those \n that are currently in use. \n [INSTALL] MESSAGE Installs the routines and globals. It will create \nPackMan is a method used to store and transport routines, data, and\n a backup message of any routines that will be \n over-written, if you request it to. \npackages via MailMan messages. PackMan messages can be secured with\na Scramble [PASSWORD]. Users must hold the XUPROG and XUPROGMODE\nsecurity keys in order to fully use PackMan.\n \nCREATING a Packman message:\n [ROUTINE LOAD] Loads routines into a message. \n [GLOBAL LOAD] Loads global data into a message. \n
\n\n", "\n- \n\n
\n", "", "2002-05-02 07:29:00\n", "", "USER,ONE\n", "", ""], ["1145", "XM-I-C-TALKMAN", "TALKMAN\n", "", "", "\n\n\n[CAPTURE] the session into a message\n\n[END] the session\n\nIf <CTRL>A was typed by mistake, simply press the <RETURN> key to continue\nthe session.\nTalkMan connects a user to a remote system and then hands off control\nto the user, who can then log onto the remote system.\n\nTalkMan can connect to any domain in the DOMAIN file whose FLAGS field\ncontains a "T", and which has a TELNET, or TalkMan type script.\n\nOnce in the TalkMan session, the user can get TalkMan's attention by\ntyping <CTRL>A (pressing the CTRL and A keys simultaneously) and can then\n
\n\n", "\n- \n\n
\n", "", "2002-05-02 09:01:00\n", "", "USER,ONE\n", "", ""], ["1146", "XM-I-C-TALKMAN END", "ENDING A TALKMAN SESSION\n", "", "", "\n\nTo end a TalkMan session, do the following:\n\nPress <CTRL>A to get TalkMan's attention. You will be at a command line.\n\nThen enter 'E' (for End). You will be back on the system from which the\nTalkMan session was invoked.\n
\n\n", "", "", "2002-05-02 09:02:32\n", "", "USER,ONE\n", "", ""], ["1147", "XM-I-C-TALKMAN CAPTURE", "CAPTURING A TALKMAN SESSION\n", "", "", "\n\nthan 75 characters will be broken up into 75-character lines. The captured\nsession may look strange if it includes any screen mode interaction.\n\nWhen you're ready to end the capture, press <CTRL>A to get TalkMan's\nattention, and then enter 'S' (for Stop capture) or 'E' (for End session).\n\nThe MailMan message will be sent to you. Its subject will be made up\nof your name and the current date/time, as follows:\n <last,first> CAPTURE <date@time>\nTo capture the TalkMan session in a MailMan message, do the following:\n\nPress <CTRL>A to get TalkMan's attention. You will be at a command line.\n\nThen enter 'C' (for Capture). Your session will be captured from that\npoint on, and you will be returned to your session.\n\nAll interaction is captured, minus any control characters. Any line longer\n
\n\n", "", "", "2002-05-02 09:28:00\n", "", "USER,ONE\n", "", ""], ["1148", "XM-I-D-RECOVER MSGS", "RECOVER MESSAGES FOR A USER\n", "", "", "\n\n 3. [SHOW] messages already in user's mailbox\n 4. [PUT] messages into user's 'IN' basket \n \nThe procedure may be followed steps 1 thru 4. Steps 2 and 3 exist only\nso that the user may see the message count, and determine whether all\nmessages should be recovered via the load option. If a user has received\n900 messages that are recovered, it may be well to allow him/her to recover\na small portion of them manually. \n \nAlternatively, the user should be encouraged to use the [SEARCH] option\nThe 'Recover Messages' option enables you to find all messages still on\nto find messages. This option is much more powerful, in that the user can\ntailor it with multiple search criteria.\nthe system which were ever sent to a particular user, and deliver them\nto that user if they're not already in that user's mailbox. Obviously,\nthis is sledgehammer approach to recovering from some disaster that\nhappened to that poor user. There are four parts to this process.\n\n 1. [FIND] lost messages\n 2. [LIST] the messages that were found\n
\n\n", "\n- \n\n
\n", "", "2002-05-02 13:51:00\n", "", "USER,ONE\n", "", ""], ["1149", "XM-I-D-RECOVER MSGS-FIND", "RECOVER MESSAGES FOR A USER - FIND THEM\n", "", "", "\n\nThe 'Find Messages' option goes through all the messages in the MAILBOX\nfile (not the MESSAGE file!) and creates a list (in a temp global) of\nall the messages addressed to the user, but not in the user's mailbox,\nand not terminated by the user.\n
\n\n", "", "", "2002-05-02 13:56:54\n", "", "USER,ONE\n", "", ""], ["115", "XUFILE ACCESS*", "GRANTING FILE ACCESS\n", "", "", "\n \n [LEVELS OF ACCESS AUTHORITY: WHAT ARE THEY?]\n \n \n [HOW IS ACCESS GRANTED?]\n \n \n [TECHNICAL OVERVIEW]\n \n \n \n \n [INTRODUCTION]\n \n \n [WHO NEEDS FILE ACCESS?]\n \n \n
\n\n", "\n- \n\n
\n", "", "1989-02-13 00:00:00\n", "", "USER,ONE\n", "", ""], ["1150", "XM-I-D-RECOVER MSGS-PUT", "RECOVER MESSAGES FOR A USER - PUT IN USER'S MAILBOX\n", "", "", "\n\nThis option presumes that you have finished\n 'Find' the messages\n 'List' the messages found\n\nThis option lets you (with the user looking over your shoulder) select\nwhich of the messages that were found should be placed into the user's\n'IN' basket. There might be hundreds or thousands of messages to consider.\n
\n\n", "", "", "2002-05-02 14:08:57\n", "", "USER,ONE\n", "", ""], ["1151", "XM-I-D-RECOVER MSGS-LIST", "RECOVER MESSAGES FOR A USER - LIST THEM\n", "", "", "\n\n\nThe 'List Messages Found' option will report on all the messages found\nand give sufficient information about them to allow searches to be made\neffectively. Give the user a copy of this report before continuing with\nthe series of routines and performing the load. \nThis option presumes that you have finished\n 'Find' messages for a user\n\nThis option lets you show the user which messages were found.\nUse the 'List Messages Found' option after searching for messages and\nbefore loading them into the user's 'IN' basket. The user may not want\nall the messages and may find it easier to access them one at a time\nusing the MailMan option that searches for messages.\n
\n\n", "", "", "2002-05-02 14:17:56\n", "", "USER,ONE\n", "", ""], ["1152", "XM-I-NEW FEATURES", "NEW FEATURES FOR SITE MANAGERS\n", "", "", "\n\naddress with the working one. In order to activate DNS awareness, this\nnew field in the MAILMAN SITE PARAMETERS file 4.3 must be set to 'yes':\n 4.3,8.22 DNS AWARE Yes or No?\nAlso, routine ^XLFNSLK must exist, and the following field in the\nKERNEL SYSTEMS PARAMETERS file 8989.3 must be properly filled in with\nan IP address:\n 8989.3,51 DNS IP IP address for DNS\n\n2. For TCP/IP connections, MailMan can now build transmission scripts on\nthe fly. For transmission scripts whose TYPE is "SMTP", "TCPCHAN", or null,\nMailMan 8.0 offers the following improvements over MailMan 7.1:\nthe transmission scripts (in the TEXT field 2, in the TRANSMISSION SCRIPT\nmultiple) in the DOMAIN file, 4.2, are no longer used if these new fields\nin the MAILMAN SITE PARAMETERS file 4.3 are filled in:\n 4.3,8.23 TCP/IP COMMUNICATIONS PROTOCOL Points to file 3.4\n 4.3,8.24 TCP/IP TRANSMISSION SCRIPT Points to file 4.6\n\n3. Messages in transmit queues can now be designated as low priority, as\nwell as high priority. If a message gets stuck in a transmit queue and is\nholding up the rest of the queue for whatever reason, MailMan will make\nthat message a low priority message, so that all the other messages are\n\ntransmitted ahead of it. The postmaster can also make these priority\nchanges. In the message queue, high-priority messages are now marked with\n'^', instead of '$'. Low priority messages are marked with 'v'.\n\nThe postmaster can now change the transmit priority at the message level\n(at the 'Message action: Ignore//' prompt). As at the basket level, the\ncommand to use is 'X'. (In a user basket, the 'X' at the message level is\na command to unload a PackMan message or KIDS build. In a remote transmit\nqueue, the 'X' changes the transmit priority. The difference is the\ncontext, and writers of MailMan front-ends should take note!)\n1. MailMan is now DNS aware. It can use the Kernel API MAIL^XLFNSLK\n\n4. MailMan date/times are now in a standard format, produced by the Kernel\nAPI: $$FMTE^XLFDT(datetime,"2Z"). Previously, 3020803.153204 would be\ndisplayed as '03 Aug 02 15:32'. Now, it is displayed as '08/03/02@15:32'.\nThis change is also carried through to all MailMan APIs which return\ndate/time in MailMan format.\n\n5. MailMan remote message IDs now include the message date, to ensure that\nif you are told that a message is a duplicate of a previously received\nmessage, it really is. Sites will no longer have problems sending messages\nto retrieve IP addresses. It is no longer necessary to manually update the\nfrom a production account to a test account which was created by "mirroring"\nthe production account. The remote message ID is now the message number\nfollowing by a period, followed by the 7-digit FileMan message creation\ndate. Before, a remote message ID might be 34561234@DOMAIN.EXT. Now it\nwould be 34561234.3020803@DOMAIN.EXT.\n\n6. The ^XMC*, ^XMR*, ^XMS* suite of routines, which are responsible for\nscheduling, transmitting to, and receiving messages from remote sites, have\nbeen completely overhauled to make them easier to understand and easier to\nmaintain.\nIP addresses in the DOMAIN file, 4.2. The IP address fields will remain in\n\n7. MailMan will no longer display user names by taking them directly from\nthe .01 field of the NEW PERSON file, 200. The API, $$NAMEFMT^XLFNAME,\nsupplied as part of the Name Standardization project, is used, instead.\nThus, the names of people whose last names, for instance, contain periods,\napostrophes, or spaces, are properly displayed (ST. IVES, O'MALLEY, and\nVAN DYKE), instead of improperly (STIVES, OMALLEY, and VANDYKE).\n\n8. Messages with responses may no longer be forwarded to broadcast to all\nusers. Such messages may have important information in the responses, and as\nfile 4.2, and MailMan will use them. However, if they don't work, MailMan\nwe all know, responses are not auto-forwarded to remote sites for users with\nauto-forward addresses. Users who attempt to broadcast messages with responses\nwill be encouraged to copy the message and its responses into a new message,\nwhich can be broadcast. \n\n9. Incoming PackMan and KIDS messages are no longer subject to the\nrestriction NETWORK - MAX LINES RECEIVE (field 8.31, file 4.3). Other kinds\nof messages continue to be subject to that restriction.\n\n10. If a task transmitting messages to another site fails and has to be\nwill use the Kernel API to retrieve a list of valid IP addresses. When\nrequeued, it really is requeued. Previously, that wasn't true. Previously,\nthe failing task queued up a new task to take its place, and then the\nfailing task stopped.\nMailMan finds one that works, MailMan will replace the non-working IP\n
\n\n", "", "", "2002-05-06 10:12:04\n", "", "USER,ONE\n", "", ""], ["1153", "XM-I-N-NETWORK", "NETWORK OVERVIEW\n", "", "", "\n\nIf the message should be sent immediately, MailMan schedules a [TASK], if one\nisn't already scheduled, to send it and any other messages in the queue. If\nthe task encounters any problems with the transmission, MailMan sends a\n[BULLETIN] to the Postmaster. \n\nOther possibilities for transmission include [SCHEDULE]ing a task, [PLAY]ing\na script, [POLL]ing the site, dumping to [TAPE], or [INTER-UCI] transfer. \nCertain fields in the [MAILMAN SITE PARAMETERS] file and all fields in the\n[DOMAIN] file are relevant to network transmission.\n\nWhen a user addresses a message to a remote site, MailMan checks the relevant\n[ADDRESS]ing fields in the Domain file to see how it should be handled. When\nthe user hits 'transmit', the message is placed in a basket, or [QUEUE],\nbelonging to the Postmaster.\n\n
\n\n", "\n- \n\n
\n", "", "2002-05-09 07:23:00\n", "", "USER,ONE\n", "", ""], ["1154", "XM-I-S-SITE PARAMETERS-LOCAL", "SITE PARAMETERS AFFECTING LOCAL MESSAGES\n", "", "", "\n\n Use [BIG GROUP SIZE] field (#7.2) to indicate when a mail group is\n considered 'large.'\n\n Use the [MAX DIGITS FOR MESSAGE NUMBER] field (#17.1) to set the maximum\n number of digits that can comprise a MailMan internal message\n identification number before they recycle back and start again from 100,000.\nHere are some Site Parameters in file 4.3 which can affect local messages:\n\n Use the COPY LIMIT fields (#5.11, 5.12, 5.13) to limit which messages may\n be copied, including setting a limit on number of lines and responses.\n \n Use the [P-MESSAGE LINE LIMIT] field (#16.1) to set the maximum\n number of lines that can be written to the P-MESSAGE [DEVICE].\n\n
\n\n", "\n- \n\n
\n", "", "2002-05-06 15:31:00\n", "", "USER,ONE\n", "", ""], ["1155", "XM-I-S-SITE PARAMETERS-USER", "SITE PARAMETERS AFFECTING USERS\n", "", "", "\n\n than the name. (Don't set this field if your site uses SSNs as DUZs.)\n\n Use SHOW ADDRESS ON USER LOOKUP (field #7.4) to show a user's address\n (fields #.111 through .116 in file 200) when showing help on that user.\n (Don't set this if your site puts home addresses in these fields.)\n\n Use MESSAGE ACTION DEFAULT (field #5.1) to set the default message action\n to either "Ignore" or "Delete" after a user has read a message. (Default\n is "Ignore".) The user can [OVERRIDE] this.\n\nHere are some Site Parameters in file 4.3 which can affect local users.\n[MORE]...\n(Default in each case is NO, except where specified.)\n\n Use REQUIRE INTRODUCTIONS? (field #7) to force a user to [INTRODUCE] himself.\n\n Use SHOW DUZ WHEN ADDRESS MESSAGE (field #7.3) to show a user's DUZ when a\n message is addressed to that user. If the user's name is a common one, it\n might be easier for some people to address a message using the DUZ, rather\n
\n\n", "\n- \n\n
\n", "", "2002-05-07 07:18:00\n", "", "USER,ONE\n", "", ""], ["1156", "XM-I-S-SITE PARAMETERS-USER-2", "SITE PARAMETERS AFFECTING USERS (CONTINUED)\n", "", "", "\n\n in file 200), other sites prefer SIGNATURE BLOCK TITLE (field #20.3 in file\n 200). The default is TITLE. A user's [TITLE] may be displayed during message\n addressing if the user doing the addressing has indicated that in his\n personal preferences. \n Use FORWARD PRIORITY MAIL TO GROUP (field #21) to allow users to forward\n priority messages to mail groups.\n\n Use DROP OUT OF RESTRICTED GROUP (field #22) to allow users to drop out of\n restricted mail groups. These are groups that don't allow self-enrollment.\n\n Use TITLE SOURCE (field #23) to indicate which field the user's title should\n should be taken from. Some sites prefer that it come from TITLE (field #8\n
\n\n", "\n- \n\n
\n", "", "2002-05-07 07:31:00\n", "", "USER,ONE\n", "", ""], ["1157", "XM-I-S-SITE PARAMETERS-ID", "SITE PARAMETERS AFFECTING THE SITE\n", "", "", "\n\n your production account, it would be either FORUM or GK. For other accounts,\n it may be the production account. In any case, an account can't be its own\n parent. The parent is the site that mail is directed to if your site can't\n figure out (it's not in your Domain file) how to direct mail to another site.\n The hope is, of course, that the parent site will know.\n\n NOTE: Do NOT change the NAME (field #.01) in your production account.\n Name changes must be coordinated with national VA DNS administrators and\n MailMan developers, and must be done via a MailMan patch. For non-production\n accounts, you should use the XMCHRIS option to perform any name changes, and\nHere are some Site Parameters in file 4.3 which affect the site:\n make sure these changes are reflected in the Domain files of other accounts\n which communicate with that account.\n\n Use TIME ZONE (field #1) to indicate which time zone your site is in. If\n your time zone shifts twice a year ("fall back and spring ahead"), then you\n must change this field manually. Don't forget! The time zone is attached\n to the date field of every message sent to another site.\n\n Use PARENT (field #3) to indicate the PARENT domain for your site. For\n\n\n", "", "", "2002-05-07 08:17:00\n", "", "USER,ONE\n", "", ""], ["1158", "XM-I-S-SITE PARAMETERS-REMOTE", "SITE PARAMETERS AFFECTING REMOTE MESSAGING\n", "", "", "\n\n Use DNS AWARE (field #8.22) to let MailMan use DNS to look up IP addresses.\n\n Use PREVENT MESSAGE RELAY (field #40) to prevent outside sites from routing\n messages to other outside sites through your site. Don't aid virus writers\n and spammers.\n\n Use MY DOMAINS (field #41) to identify sites for which you are willing to\n relay messages.\n\n Use TCP/IP COMMUNICATIONS PROTOCOL (field #8.23) and TCP/IP TRANSMISSION\nHere are some Site Parameters in file 4.3 which affect remote messaging:\n SCRIPT (field #8.24) to enable MailMan to automatically build TCP/IP\n transmission scripts to transmit messages to another site.\n\n Use XMITS TILL ERROR MESSAGE (field #8.21) to indicate the number of times\n the transmission may fail before the Postmaster is notified of a problem\n and MailMan moves on to try another script.\n\n Use RECORD NETMAIL TRANSCRIPT? (field #8.2) to record every communications\n session with another site. (Only 100 total sessions are kept.)\n\n Use NETWORK - MAX LINES SEND (field #8.3) to restrict the number of lines\n in a message that may be sent to another site.\n\n Use NETWORK - MAX LINES RECEIVE (field #8.31) to restrict the number of lines\n in a message that may be received from another site.\n\n
\n\n", "", "", "2004-02-18 06:58:00\n", "", "USER,ONE\n", "", ""], ["1159", "XM-I-S-SITE PARAMETERS-DISK", "SITE PARAMETERS AFFECTING DISK SPACE MANAGEMENT\n", "", "", "\n\n created messages.\n\n Use WEEKDAY DAYS TO PURGE (field #4.304) to limit the purge to messages\n created recently, when the purge is run on weekdays. When the purge is\n run on Saturdays, this field is ignored, and every message is considered.\n\n Use AUTOMATIC INTEGRITY CHECK (field #4.303) to indicate whether an integrity\n check of the Mailbox file 3.7 should be run before the purge.\n\nThese fields are used by option XMPURGE-BY-DATE:\nHere are some Site Parameters in file 4.3 which affect disk space management.\n\n Use DATE PURGE CUTOFF DAYS (field #10.03) to calculate a cutoff date.\n\n Use DATE PURGE GRACE PERIOD (field #10.04) to give users a warning.\n\nThese fields are used by option XMMGR-IN-BASKET-PURGE:\n\n Use IN-BASKET-PURGE DAYS (field #10) to indicate how many days a message\n may remain unread before being considered for purge.\n\nFor these fields, see both the options and the DDs for more information:\n Use IN-BASKET-PURGE TYPE (field #10.01) to indicate whether the purge\n applies to the IN basket only (default) or to all baskets.\n\nThese fields are used by option XMAUTOPURGE to purge unreferenced messages:\n\n Use NO-PURGE DAYS BUFFER (field #4.301) to protect the newest messages.\n\n Use NO-PURGE DAYS BUFFER (LOCAL) (field #142) to protect the newest locally\n
\n\n", "", "", "2002-05-07 09:41:00\n", "", "USER,ONE\n", "", ""], ["116", "XUDOC DEVICE PROMPT*", "RESPONDING TO THE DEVICE PROMPT\n", "", "", "\n \n DEVICE: P to select the closest printer if one is defined.\n (This may be disabled when using decservers or\n MICOM port contention.)\n \n DEVICE: Q to [QUEUE] your output to run in the background.\n \nYou may optionally specify a right margin or page length to override the\ndefault Device file settings:\n \n DEVICE: DVNM5;80;66 to use the DVNM5 device with a right margin of\nWhen prompted for a device, you may enter the name of the device or another\n 80 columns and page length of 66 lines.\n [CONTINUE]\nresponse as shown below:\n \n DEVICE: DVNM5 to specify the device with the name DVNM5.\n \n DEVICE: HOME to direct output to your terminal. Alternatively\n enter H, h, 0, or just press return.\n \n
\n\n", "\n- \n\n
\n", "", "1989-04-18 22:01:00\n", "", "USER,ONE\n", "", ""], ["1160", "XM-I-N-XMIT QUEUES", "TRANSMIT QUEUES\n", "", "", "\n\nit is deleted from the basket. (The message is not placed in the WASTE basket.)\n\nUsers who are surrogates of the Postmaster can "become" the Postmaster and\nread the baskets containing the messages waiting to be transmitted. They are\nnot able do anything that would let them see the text of the messages, but they\nare able to take other actions with them, like move them to the head or end of\nthe queue.\nWhen a message is addressed to a remote site, the message is placed in a\nspecial basket in the Postmaster's (DUZ=.5) mailbox (file 3.7). This basket\nis also called a queue. The basket IEN is 1000 plus the IEN of the Domain in\nthe Domain file (4.2). The basket name is the name of the Domain. For\nexample, if the message is addressed to someone at FORUM, and DOMAIN.EXT is\nat IEN 4 in file 4.2, then the message is placed in the Postmaster's mailbox,\nin a basket named DOMAIN.EXT, whose IEN is 1004. If the basket doesn't\nexist, it is created automatically. Once the message has been transmitted,\n
\n\n", "", "", "2002-05-08 08:34:00\n", "", "USER,ONE\n", "", ""], ["1161", "XM-I-N-DOMAIN FILE", "DOMAIN FILE\n", "", "", "\n\nThe DOMAIN file, 4.2, should contain a record for every domain your site\ncommunicates with on a regular basis. Here are some of the important fields:\n\nFields used during [ADDRESSING]\n\nFields used to establish a [CONNECTION]\n\nFields used during the transmit [SESSION]\n
\n\n", "\n- \n\n
\n", "", "2002-05-07 15:38:00\n", "", "USER,ONE\n", "", ""], ["1162", "XM-I-N-DOMAIN FILE-ADDRESSING", "DOMAIN FILE FIELDS INVOLVED IN ADDRESSING\n", "", "", "\n\n\n SYNONYM (multiple under field #5) lists other names by which this domain is\n known. (If a site has its name changed via a MailMan patch, the old name\n becomes a synonym.)\n\n RELAY DOMAIN (field #2) points to a domain through which messages addressed\n to the domain are routed.\n\n [FLAGS] (field #1) controls the method used to contact the domain.\n\nThe following fields in the DOMAIN file 4.2 are used when a message is\n SECURITY KEY (field #1.5), if present, allows only those users who hold the\n specified security key to address messages to the domain.\naddressed to a remote site:\n\n NAME (field #.01) is the name of the domain. (Names of production domains\n should only be changed by a MailMan patch. If a site needs to change its\n name, it must coordinate with the VA's national DNS team, as well as the\n MailMan developers. If a site changes its name unilaterally, communication\n between that site and other sites will be adversely affected.)\n
\n\n", "\n- \n\n
\n", "", "2002-05-08 10:05:00\n", "", "USER,ONE\n", "", ""], ["1163", "XM-I-N-DOMAIN FILE-FLAGS", "DOMAIN FILE - FLAGS FIELD\n", "", "", "\n\n\n S - Send immediately. Messages sent to the domain are transmitted ASAP.\n MailMan will schedule a Task to do so. S overrides Q. FLAGS may contain\n both S and P. If FLAGS does not contain S, messages are queued.\n\n Q - Queue. (Default) Messages sent to the domain are queued for later\n disposition. It may be that someone will play a script to the domain or\n from the domain to this site. Other possibilities exist, too.\n\n P - Poll. If the poller (option XMPOLL) is scheduled to run on a regular\nThe FLAGS field (#1) controls the method used to contact the domain.\n basis, the poller will schedule a task to communicate with the domain.\n Messages in the queue, if any, are transmitted then.\nThe field may contain any number of the following codes:\n\n C - Closed. If the field contains a C, the domain is closed and users may\n not send messages to the domain. C overrides all other codes.\n (Packages may still send messages if they use ^XMD, or if they set\n XMINSTR("ADDR FLAGS")="R", and use one of the ^XMXAPI commands, like\n SENDMSG^XMXAPI or FWDMSG^XMXAPI.)\n\n\n", "", "", "2002-05-08 06:33:00\n", "", "USER,ONE\n", "", ""], ["1164", "XM-I-N-DOMAIN FILE-SESSION", "DOMAIN FILE FIELDS USED WHILE TRANSMITTING\n", "", "", "\n\n sends messages to the domain.\nThe following fields in the DOMAIN file 4.2 are used once a connection with\na remote site has been established:\n\n [VALIDATION NUMBER] (field #1.6), if present, is used while communicating\n with another site to confirm that the site is really the intended one.\n\n [DISABLE TURN COMMAND] (field #1.7) controls whether your site will accept\n messages from the domain in the same session as the one in which your site\n
\n\n", "\n- \n\n
\n", "", "2002-05-07 15:34:15\n", "", "USER,ONE\n", "", ""], ["1165", "XM-I-N-DOMAIN FILE-CONNECT", "DOMAIN FILE FIELDS USED TO CONNECT TO A SITE\n", "", "", "\n\n of the script. MailMan chooses the highest priority script to try first.\n\n NUMBER OF ATTEMPTS (field #1.1) notes how many times this script should be\n tried before moving on to the next script and notifying the Postmaster (in\n a bulletin) that MailMan was unable to connect using the script.\n\n TYPE (field #1.2) is the script type (TCPCHAN, SMTP, FTP, TELNET, or OTHER).\n\n PHYSICAL LINK / DEVICE (field #1.3) points to the DEVICE file to indicate\n the port to be used for the connection. It may be the NULL DEVICE.\nThe following fields in the DOMAIN file 4.2 are used when establishing a\n\n[MORE]...\nconnection to a remote site. They all reside under the TRANSMISSION SCRIPT\nmultiple (field #4). Taken together, they provide the instructions on how to\nconnect. A domain may have one or more transmission scripts. \n\n TRANSMISSION SCRIPT (field #.01) is the name of the script.\n\n PRIORITY (field #1) is the relative priority (lower number = higher priority)\n
\n\n", "\n- \n\n
\n", "", "2002-05-08 07:04:00\n", "", "USER,ONE\n", "", ""], ["1166", "XM-I-N-DOMAIN FILE-CONNECT-2", "DOMAIN FILE FIELDS USED TO CONNECT TO A SITE (CONTINUED)\n", "", "", "\n\n\n TEXT (field #2) is a word-processing field containing the commands to be used\n to finalize the connection and begin the transmission process. If this field\n is empty, and field 1.2 is TCPCHAN, MailMan is able to build a TCP/IP script\n on-the-fly if the necessary [MAILMAN SITE PARAMETERS] (fields 8.23 and 8.24)\n are filled out.\n\n TRANSMISSION SCRIPT NOTES (field #99) is a word-processing field in which\n you or MailMan may place notes about the script. If MailMan places a new\n IP address in field #1.4, a note will be added, stating the date/time,\n NETWORK ADDRESS (MAILMAN HOST) (field #1.4) is the IP (Internet Protocol)\n the old IP address, and the new IP address.\n address of the site. The IP address is a unique address, much like a phone\n number. If it doesn't work (no one answers), MailMan uses DNS (Domain Name\n Server) to look up the IP address (using the Domain name). If the IP address\n returned by the DNS works, then MailMan puts it in this field, and makes a\n note to that effect in the TRANSMISSION SCRIPT NOTES field #99.\n\n OUT OF SERVICE (field #1.5) indicates that this script should not be used.\n
\n\n", "\n- \n\n
\n", "", "2002-05-08 09:43:00\n", "", "USER,ONE\n", "", ""], ["1167", "XM-I-N-DOMAIN FILE-VALIDATE", "DOMAIN FILE - VALIDATION NUMBER FIELD\n", "", "", "\n\nIf the validation numbers are not null, and they match, then the sites agree on\na new validation number to be used the next time, and the session continues.\n\nIf the validation numbers are not null, and they don't match, then the session\nis brought to an abrupt end, and a bulletin is sent to the Postmaster to notify\nsite managers of the 'bad validation number'. To correct this, someone at your\nsite must contact (by phone, usually) someone at the other site, and one of you\nmust change your validation number to match the other's. Once the fields have\nbeen edited to match, then you can re-schedule a task to transmit the messages.\nThe VALIDATION NUMBER (field #1.6) is used as an extra security precaution\nto confirm that the site really is who it says it is.\n\nAfter the connection has been established, the validation numbers are compared.\n\nIf the validation numbers are null, then the security precaution is not active,\nand the session continues.\n\n
\n\n", "", "", "2002-05-08 10:35:00\n", "", "USER,ONE\n", "", ""], ["1168", "XM-I-N-DOMAIN FILE-TURN", "DOMAIN FILE - DISABLE TURN COMMAND FIELD\n", "", "", "\n\nsimply end the session. The receiving site will have to start its own session\nto transmit its messages.\n\nIf the receiving site has the TURN command disabled, then it will refuse the\nopportunity to send its messages. It will send its messages in a session it\ninitiates.\n\nOn a production system, the TURN command might be disabled for the domain file\nentries for any test accounts to avoid any inadvertent receipt of messages\nfrom the test systems.\nThe DISABLE TURN COMMAND (field #1.7) is used to prevent two-way transmission.\n\nHere's the scenario. Once the connection has been established and the sending\nsite has sent all its messages, it generally issues a TURN command to give the\nreceiving site a chance to send all of its messages that it may have.\n\nIf the sending site has the TURN command disabled, then it will not give the\nreceiving site the chance to send its messages. The receiving site will\n
\n\n", "", "", "2002-05-08 07:57:57\n", "", "USER,ONE\n", "", ""], ["1169", "XM-I-N-XMIT TASK", "TRANSMIT TASK\n", "", "", "\n\nAfter the task has started, if anything goes wrong, MailMan will re-schedule\nthe task to begin again in one minute. If the problem was that the IP address\ndidn't work, then MailMan consults the DNS (if activated) to see if there's any\nother IP address to try. If there is, then that IP address will be used when\nthe task starts up in a minute. If not, the same IP address will be used. \n\nIf the task has failed a certain number of times (as specified in the script),\nMailMan sends a bulletin to the Postmaster to notify site managers of the\nproblem. Included in the bulletin is a transcript of the latest attempt. Then\nMailMan selects the next script to try, and re-schedules the task to begin\nA task to transmit messages to another site is scheduled ASAP after a message\nagain in one hour. If there's no other script, the same script is used.\n[MORE]...\nhas been addressed and "sent" to that site, if the [FLAGS] field of that site's\nDomain file entry contains an "S". Tasks can also be queued by the options\n'Transmit a Single Queue', 'Transmit All Queues', or 'Poll Remote'. \n\nMailMan uses fields in the [DOMAIN] file to select a script and set up the\ntask, and schedules the task to start immediately. \n\n
\n\n", "\n- \n\n
\n", "", "2002-05-08 09:48:00\n", "", "USER,ONE\n", "", ""], ["117", "XUDOC DEVICE PROMPT QUEUING", "QUEUING OUTPUT\n", "", "", "\n \n \n DEVICE: DVNM5\n DO YOU WANT YOUR OUTPUT QUEUED? NO// YES\n \nIn both cases, you will then be asked to specify a time for queuing. You\nmay accept the default (now) or indicate a later time in the usual format.\nQueuing sends your output to the Task Manager for processing. Meanwhile,\nyou may continue working without delay. TaskMan will process your job in\nthe background and send it to the device you had requested. (Freeing the\nhome device is not always possible since it involves detaching the home\nThere are two ways to invoke queuing at the device prompt. You may either\ndevice from the existing process, a procedure which is not supported by all\noperating systems.)\nrespond with Q, then specify a device as follows:\n \n DEVICE: Q\n DEVICE: DVNM5\n \nOr you may first specify a device, and then indicate that you would like to\nhave your output queued. For example:\n
\n\n", "", "", "1989-04-19 11:07:00\n", "", "USER,ONE\n", "", ""], ["1170", "XM-I-N-XMIT TASK-2", "TRANSMIT TASK (CONTINUED)\n", "", "", "\n\nIf the task is successful with an IP address that is different from the one\nin the script, then MailMan replaces the IP address in the script with the\nsuccessful one, and adds a comment to that effect in the transmission script\nnotes.\n
\n\n", "", "", "2002-05-08 09:29:21\n", "", "USER,ONE\n", "", ""], ["1171", "XM-I-N-BULLETINS", "BULLETINS SIGNALING TROUBLE IN NETWORK TRANSMISSION\n", "", "", "\n\n\n XM SEND ERR TRANSMISSION - Sent because there were problems connecting\n with the site or while transmitting to the site. This bulletin will\n include the number of times the transmission has failed, the reason\n (if known) for the problem, as well as a transcript of the latest\n attempt.\nThere are two bulletins which are sent to the Postmaster in the event that\nMailMan has any problems when communicating with a remote site. It is\nrecommended that mail groups be added to these bulletins so that programmers\nat your site who are responsible for MailMan will be notified, too.\n\n XMVALBAD - Sent because the [VALIDATION NUMBERS] at both sites don't\n match. The numbers must match in order for the transmission to be\n accepted.\n
\n\n", "\n- \n\n
\n", "", "2002-05-08 14:14:00\n", "", "USER,ONE\n", "", ""], ["1172", "XM-I-N-XMIT POLL", "POLL A SITE\n", "", "", "\n\nre-schedule it. The Poller will start it again the next time it is\nscheduled.\n \nXMPOLL can be scheduled through 'Schedule Tasks' on the Taskman menu.\nSet a time for transmission such as an off-peak evening hour. The device\nfor output may be null, the default being the device on which the Taskman\nwas started. \nThe Poller (option XMPOLL) schedules tasks to transmit to all domains\nwhose [FLAGS] contain a 'P'. The tasks will transmit to those domains\nwhether or not there are messages in the queues for those domains.\n\nThe TURN command (assuming it isn't [DISABLED]) will "pull" any messages\nqueued at the domains waiting to be transmitted to this one. \n\nIf a task initiated by the Poller has any problems, MailMan will not\n
\n\n", "\n- \n\n
\n", "", "2002-05-08 14:49:00\n", "", "USER,ONE\n", "", ""], ["1173", "XM-I-N-XMIT TAPE", "TRANSMIT VIA TAPE\n", "", "", "\n\nTransmission', and select the domain. The messages will be dumped to tape.\n\nSend the tape to a sister site (or to the site of the domain whose messages\nyou dumped).\n\nTo receive the messages from the tape, select option 'Sequential Media\nMessage Reception'. MailMan will take it from there.\nAs a backup method of transmitting messages, in case the WAN is down for a\nperiod of time, MailMan provides the ability to dump a queue (transmit the\nmessages) to tape (or any other sequential transportable medium), send that\ntape to another site whose WAN is up, and have that site mount the tape and\nreceive the messages, which will then be automatically transmitted onward\nfrom that site. (The site acts as your site's relay domain in this case.)\n\nTo dump a message queue to tape, select option 'Sequential Media Queue\n
\n\n", "", "", "2002-05-08 15:12:00\n", "", "USER,ONE\n", "", ""], ["1174", "XM-I-N-XMIT UCI", "TRANSMIT BETWEEN UCI'S VIA A GLOBAL\n", "", "", "\n\nTo transmit messages via a global:\n \n Log onto the UCI you wish to transmit messages from. \n \n Use the option 'Send Messages to Another UCI'. It will ask which domain\n and will then transmit the messages in the queue to the global.\n\n Log onto the UCI you wish to receive the messages into.\n\n Use the option 'Receive Messages from Another UCI'. It will look in the\nMailMan lets you transmit messages from one UCI to another via a global.\n global for entries directed to its domain, and will then receive the\n messages from those entries. MailMan will take it from there.\n\nThe following conditions must be met:\n - MailMan must be running in each UCI.\n - The global, ^%ZISL(4.281, must be translated and accessible from both UCIs.\n - The name of the receiving UCI must exactly match its domain file entry in\n the sending UCI. Synonyms will not work.\n \n
\n\n", "", "", "2002-05-09 08:35:00\n", "", "USER,ONE\n", "", ""], ["1175", "XM-I-N-XMIT PLAY", "TRANSMIT - PLAY A SCRIPT\n", "", "", "\n\n\nTo play a script, select the option 'Play a script'. You'll be asked to\nselect the domain and the transmission script (if there's more than one). If\na task is already scheduled to transmit to that domain, you'll be given the\nopportunity to cancel the task. If a task is already actively transmitting\nto that domain, the script will not play. If there's problems connecting\nusing the IP address, you'll observe how MailMan calls the DNS to retrieve\nanother IP address, and immediately tries it.\nIf you want to have total control and immediate gratification, you can play\na script to a domain to transmit any messages in its queue and, if the TURN\ncommand is not [DISABLED], retrieve any messages from that domain which are\nwaiting to be transmitted to this one. If there's any problem, you'll see\nit happening. You'll see every single interaction between the sites, \nincluding the message transmissions, in excruciating detail. It doesn't\nmatter what the [FLAGS] field in the Domain file indicates - as long as there's\nan entry in the [TRANSMISSION SCRIPT] multiple, you'll be able to play a script.\n
\n\n", "\n- \n\n
\n", "", "2002-05-09 07:04:51\n", "", "USER,ONE\n", "", ""], ["1176", "XM-I-N-XMIT SCHEDULE TASK", "TRANSMIT - SCHEDULE A TASK\n", "", "", "\n\nopportunity to cancel that task. If a task is already actively transmitting to\nthat domain, you will not be able to schedule another one. \n\n'Transmit all Queues' will look at every queue and consider whether to schedule\na task for it. If the queue has messages and its [FLAGS] field contains an 'S'\nand there's no task currently scheduled to transmit the queue or is actively\ntransmitting, then it will schedule a task to transmit that queue's messages.\n(MailMan will select the transmission script.)\nThere are two options which will enable you to schedule [TASK]s to transmit\nqueues with messages. (The queues must have messages to be considered.)\nThey are 'Transmit a Single Queue' and 'Transmit All Queues'. \n\n'Transmit a Single Queue' will let you select only those queues with messages.\nIt does not matter what the [FLAGS] field contains for the domain you select.\nYou will be asked to select the domain, as well as the transmission script.\nIf a task is already scheduled to transmit to that domain, you'll be given the\n
\n\n", "\n- \n\n
\n", "", "2002-05-09 07:24:14\n", "", "USER,ONE\n", "", ""], ["1178", "EC NTPCE", "ECS Records Failing Transmission to PCE\n", "", "W @IOF\n", "\nThis Event Capture report provides a list of encounters and the reasons \nwhy the records were not transmitted to PCE. The Procedure Date/Time,\nLocation, DSS Unit, Patient, Procedure, Category, last four \ndigits of the Patient's SSN, Provider(s) of care and Reasons for \ntransmission failure are listed on the report.\n
\n\n", "", "", "2004-02-19 15:06:05\n", "", "USER,FIFTYFOUR\n", "", ""], ["1179", "ORBA-SC", "ORBA-SC\n", "", "", "\nService-Connected (SC):\nVeterans are eligible for medical care for treatment\nof service-connected (SC) conditions without\nincurring copayment charges or claims against their\ninsurance. See 'Help' for additional information.\n
\n\n", "", "", "2004-02-09 13:28:19\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["118", "XUDOC DEVICE PROMPT SYNTAX", "GENERAL SYNTAX FOR DEVICE REQUEST\n", "", "", "\n \noptional but semicolons are retained to distinguish margin from page length.\n \n DEVICE: ;P-DEC if the home device is a video terminal, output\n would scroll without waiting for the user to\n enter return after a screen display.\n \n DEVICE: ;132 to use the home device, right margin of 132.\n \n DEVICE: ;;66 to use the home device, page length of 66 lines.\n To scroll on the home device, use ;;9999.\nThe general syntax for responding to the device prompt is as follows:\n \nWhen sending output to the [SPOOLER], the spool document may also be named.\n \n DEVICE: Device Name ; Subtype ; Right Margin ; Page Length\n \nIf the subtype is not specified, characteristics are taken from the Device\nfile. If a subtype is specified without a device name, characteristics are\ntaken from the Terminal Type file. Note that the second piece is optional\nand may be omitted, semicolon and all. The third and fourth pieces are also\n
\n\n", "\n- \n\n
\n", "", "1989-04-18 22:27:00\n", "", "USER,ONE\n", "", ""], ["1180", "ORBA-MST", "ORBA-MST\n", "", "", "\nMilitary Sexual Trauma (MST):\nVeterans who experienced sexual trauma while serving\non active duty in the military are eligible to\nreceive treatment and counseling services for the\nsexual trauma without incurring copayment charges or\nclaims against their insurance. See 'Help' for\nadditional information.\n
\n\n", "", "", "2004-02-09 13:30:03\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1181", "ORBA-AO", "ORBA-AO\n", "", "", "\nAgent Orange (AO): herbicide used in Vietnam.\nperipheral neuropathy and some cancers. See 'Help'\nfor additional information.\nVeterans who were present within the borders of the\nRepublic of Vietnam from January 1962 through May\n1975 are presumed to have been exposed to Agent\nOrange and are eligible to receive care of conditions\npossibly for AO exposure without incurring copayment\ncharges or claims against their insurance. Some\nconditions associated with AO exposure: diabetes\n(type 2), chloracne, porphyria cutanea tarda,\n
\n\n", "", "", "2004-02-09 13:32:18\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1182", "ORBA-IR", "ORBA-IR\n", "", "", "\nIonizing Radiation (IR):\ninformation.\nVeterans exposed to ionizing radiation (IR) as a\nPOW or while on active duty in Hiroshima and/or\nNagasaki, Japan, or who served at a nuclear device\natmospheric testing site are eligible to receive\ncare of any malignant condition and certain other\nnon-malignant conditions for IR exposure without\nincurring copayment charges or claims against\ntheir insurance. See 'Help' for additional\n
\n\n", "", "", "2004-02-09 13:36:24\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1183", "ORBA-EC", "ORBA-EC\n", "", "", "\nSouthwest Asia Conditions (SWAC):\ninformation.\nVeterans who served in Southwest Asia during the\nGulf War are eligible to receive treatment for\nconditions relating to this service, including\nexposure to depleted uranium, pesticides, anti-\nnerve gas pill, pyridostigmine bromide, infectious\ndiseases, chemical and biological warfare agents,\netc. without incurring copayment charges or claims\nagainst their insurance. See 'Help' for additional\n
\n\n", "", "", "2004-02-09 13:40:14\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1184", "ORBA-HNC", "ORBA-HNC\n", "", "", "\nHead and Neck Cancer (HNC):\nVeterans with cancer of the head or neck and a\nhistory of receipt of Nasopharyngeal (NP) radium\ntherapy while in the military are eligible to\nreceive treatment for the head or neck cancer\nwithout incurring copayment charges or claims\nagainst their insurance. See 'Help' for additional\ninformation.\n
\n\n", "", "", "2004-02-09 13:43:20\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1185", "ORBA-CV", "ORBA-CV\n", "", "", "\nCombat Veteran (CV): to receive CV exemption the veteran\nexemption should apply. See 'Help' for additional\ninformation.\nmust have served in combat operations after the Gulf\nWar or in combat against a hostile force after\nNovember 11, 1998. In addition, the condition for which\nthe veteran is treated must be related to that combat,\nthe veteran must have registered as a combat veteran,\nand be within two years of separation from active\nmilitary service. Finally, the condition must not be\nalready considered to be service related or that\n
\n\n", "", "", "2004-02-09 13:45:25\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1186", "FSC ACTION", "The NOIS Action File\n", "", "", "\nTHE ACTION FILE IS USED TO EXECUTE A BUNCH OF THINGS\n
\n\n", "", "", "1990-06-05 00:00:00\n", "", "USER,ONE\n", "", ""], ["1187", "FSC INDEX", "NOIS Topic Index\n", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n Topic 1\n Topic 2\n \n \n \n
\n\n", "\n- \n\n
\n", "", "1993-10-04 20:12:28\n", "", "USER,ONE\n", "", ""], ["1188", "FSC TOPIC 1", "Topic 1\n", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n THIS IS TOPIC 1 INFO....\n \n \n \n \n
\n\n", "", "", "1993-10-19 20:41:31\n", "", "USER,ONE\n", "", ""], ["1189", "FSC TOPIC 2", "Topic 2\n", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n THIS IS TOPIC 2 INFO...\n \n \n \n \n
\n\n", "", "", "1993-10-19 20:42:47\n", "", "USER,ONE\n", "", ""], ["119", "XUDOC DEVICE PROMPT SPOOLING", "SENDING OUTPUT TO THE SPOOLER\n", "", "", "\n \n \n DEVICE: SPOOL;P-OTHER80 to use the characteristics of the\n P-OTHER80 subtype (with an 80 column\n rather than 132 column page width).\n \nThe user is prompted for a spool document name once the spool device has\nbeen requested. As a shortcut, the spool document may be named when\nresponding to the device prompt:\n \n DEVICE: SPOOL;MYDOC to name the spool document MYDOC.\nOutput may be sent to the spool device with the optional specifications of\n \n DEVICE: SPOOL;P-OTHER80;MYDOC to use the P-OTHER80 characteristics.\nsubtype, right margin, or page length. For example:\n \n DEVICE: SPOOL to spool with defaults, often right\n margin of 132 and page length of 66.\n \n DEVICE: SPOOL;96;66 to use a margin of 96 and page length of\n 66 lines.\n
\n\n", "", "", "1989-04-19 11:17:00\n", "", "USER,ONE\n", "", ""], ["1190", "FSC MENU LIST", "List of NOIS Calls\n", "", "", "\n \nView Details - Display multiple calls - good for searching text in many calls\nSave As - Save the list as a non-active list (these lists are not auto updated)\nQuery - Use a search criteria to add, remove or have calls remain on the list\nSubquery - Calls meeting the criteria will remain on the list\nAdd - Add to the list using selected calls, other lists, or queries\nRemove - Remove calls using selected calls, other lists, queries, or all calls\nOther List - Switch to a different list\nDefine List - Display the definition of an active list\nNotify - Send a mail messsage or notify others using alerts\nPrint Selected Calls - Print only specific calls\nThis list of NOIS calls can be used to select calls for review or editing.\n \nOn any screen enter ? for help, ?? for other actions, or ??? for help topics.\nThe list can also be modified by adding and removing calls using queries\nor by using other lists. You can search for calls meeting your criteria\nand then use 'View Details' or 'Edit/Display' to review the calls.\n \n \nLog New Call - Enter a new NOIS call\nEdit/Display - Display multiple calls one call at a time and allow editing\n
\n\n", "", "", "1993-11-01 22:52:44\n", "", "USER,ONE\n", "", ""], ["1191", "FSC MENU EDIT", "Display/Edit NOIS Calls\n", "", "", "\n \nEdit All - Edit any editable portion of the call\nBasics/Description - Edit the fields that initiate and describe the call\nTake Action - Log an action entry\nClose Call - Enter the resolution summary and close out the call\nFormat Call - Change the display by selecting an alternate format\nNext Call - Displays next selected call\nPrevious Call - Displays previous selected call\nOther Call - Go to a selected call\n \n \nThese screens display one call at a time. You may edit a call by selecting\n \nOn any screen enter ? for help, ?? for other actions, or ??? for help topics.\na subject heading and editing those fields associated with the subject.\nThe display can be changed by selecting specific formats. Using 'SL' to\nsearch the list will only apply to the single call in the display. \n \n \nLog New Call - Enter a new NOIS call\nSpecialists - Shows NOIS users who's default lists will display this call\n
\n\n", "", "", "1993-11-01 23:11:02\n", "", "USER,ONE\n", "", ""], ["1192", "FSC MENU VIEW", "View Details of NOIS Calls\n", "", "", "\n \ntake awhile.\n \n \nLog New Call - Enter a new NOIS call\nEdit/Display - Switches to the edit screen to allow editing selected calls\nGo To Call - Go to a selected call\nNotify - Send a mail message or notify others using alerts\nFormat List - Change the display by selecting an alternate format\n \n \nThis screen is useful for displaying multiple calls within the same screen.\n \nOn any screen enter ? for help, ?? for other actions, or ??? for help topics.\nText searches (using 'SL' to search the list) are ideal using this display.\nThe STATISTICS format can show counts of items from the calls in the list.\nThe CUSTOM format can be used to only display specific fields of interest.\nThis display can be incorporated into a mail message that can be edited and\nsent to others. This display can also be used to review calls and the switch\nto Edit/Display to edit or close calls. Since this display loads all calls\ninto the scrolling region, a DETAILED format on a large list of calls may\n
\n\n", "", "", "1993-11-01 23:15:57\n", "", "USER,ONE\n", "", ""], ["1193", "FSC MENU MODIFY", "Define NOIS List\n", "", "", "\n \nRun - Use the current list definition to produce a list of calls\nSave - Save any changes to this definition\nSave As - Save a new list definition\nEdit a line - Change a line in the list definition\nInsert a line - Insert a new line in the list definition\nDelete a line - Delete a line from the list definition\nOther Definition - Switch to another list's definition\nView Description - Displays the definition of the list in narrative format\nEdit Description - Edit non-criteria descriptions of this list\n \nYou can use this screen to create and edit list definitions. These criteria\n \nOn any screen enter ? for help, ?? for other actions, or ??? for help topics.\nare used to actively update update calls on the list as calls are created\nor edited. Creating a new definition is similar to doing queries on calls.\nYou may want to take existing lists, modify them and save it as a new list\ndefinition\n \n \nNew Definition - Enter a new list definition\n
\n\n", "", "", "1993-11-01 23:20:02\n", "", "USER,ONE\n", "", ""], ["1194", "FSC DEMO", "NOIS v1.0T2\n", "", "", "\n \nIf you haven't used this version of NOIS please test the software with\na [Usability Test]. Record your evaluation by logging a NOIS call.\n \nIf you have any problems or questions, log a NOIS call on NOIS and \nrefer it to development.\n \n \n \n \n \n \n \nWelcome to NOIS. This screen is just for those logging in as a demo user.\n \nYou can select your ISC to become a different user for purposes of the demo.\n \nIf you'd like to read about NOIS first, enter [Help] and review some \nonline help.\n \n
\n\n", "\n- \n\n
\n", "", "1994-01-01 23:32:47\n", "", "USER,ONE\n", "", ""], ["1195", "FSC SPECIALIST LIST DISPLAY", "", "", "", "\nFSC LIST DISPLAY\nP - will show the current priority on all lists.\n \nThis field is a set of codes that changes the default data on all of \nyour nois lists.\nValid choices are S M U P or any combination of these four characters.\n \nS - will show the status of the call on all lists.\nM - will show the NOIS module on all lists.\nU - will show the primary specialist currently assigned to the call.\n
\n\n", "", "", "1994-01-06 08:38:00\n", "", "USER,ONE\n", "", ""], ["1196", "FSC TEST", "", "", "", "\n \nDevelopment - to resolve problems that require program changes.\nManagement - to ensure resources are being used appropriately and ensure\nproblems are resolved.\nVerification - to ensure that problems to be fixed in future releases are\ncorrected.\nDocumentation - to find common problems useful for incorporation into\ntroubleshooting guides.\nIRMS - to log problems at their local facility.\n What's NOIS\n \nNOIS stands for National On-Line Information Sharing. It is a computer\nprogram that provides a means of logging and tracking problems associated\nwith the daily operation of computer systems within DHCP. Documenting\nproblems provides a means to find and disseminate solutions to those\ninvolved in support, development, and management. Users include:\nSupport - to track and resolve reported problems.\n
\n\n", "", "", "1994-01-09 18:41:08\n", "", "USER,ONE\n", "", ""], ["1197", "FSC U10 WHAT'S NOIS", "", "", "", "\n \nSupport - to track and resolve reported problems.\nDevelopment - to resolve problems that require program changes.\nManagement - to ensure resources are being used appropriately and ensure\n problems are resolved.\nVerification - to ensure that problems to be fixed in future releases are\n corrected.\nDocumentation - to find common problems useful for incorporation into\n troubleshooting guides.\nIRMS - to log problems at their local facility.\n \n What's NOIS\n \n \n \nNOIS stands for National On-Line Information Sharing. It is a computer\nprogram that provides a means of logging and tracking problems associated\nwith the daily operation of computer systems within DHCP. Documenting\nproblems provides a means to find and disseminate solutions to those\ninvolved in support, development, and management. Users include:\n \n
\n\n", "", "", "1994-01-09 19:00:11\n", "", "USER,ONE\n", "", ""], ["1198", "FSC U20 WHAT'S NEW", "", "", "", "\n \nYou can define a criteria for the calls that you normally deal with.\nVirtually any type of call can be searched for.\nBrowsing information on calls is made easy by using ad hoc displays.\nNotifications can be made using MailMan or menu alerts. You can be\nnotified automatically of changes to calls you are interested in. Sites\ncan also be notified automatically.\nNOIS data can be easily extracted to PC applications and spreadsheets.\n \n \n \n What's New\n \n \n \nNOIS is intended to be used as a central database where all ISCs log calls\non the same system.\nCalls are not owned by any single user. Any NOIS call can be opened,\nedited, or closed by anyone having the authority to edit a call.\nList Manager is the primary user interface to display lists of calls and\ncall information.\n
\n\n", "", "", "1994-01-09 19:00:37\n", "", "USER,ONE\n", "", ""], ["1199", "FSC U30 GETTING STARTED", "", "", "", "\n Getting Started\ndischarge summary, etc.).\nTo learn to use NOIS, look at the examples in the Tour Guide, or just jump\nin, log some calls, browse around, and find some interesting calls. Every\nNOIS function (except for setting up files) can be done using the List\nCalls option.\nBefore you jump in, you may want to try a usability test on the software.\nA usability test tests how intuitive the software is to use (its not a\ntest of the user). Usually the test involves observing the user perform\ntasks - but since we cant do that on everyone, test the software and give\nus your opinions.\nLogging calls in NOIS is about the same as before. You enter a\nOther Topics:\n Screens Tour Guide\ndescription of the problem and a resolution, along with a few fields to\nidentify who called and when. Logging calls still uses prompts for the\nfields to enter and the editor youve chosen when working with FileMan word\nprocessing fields.\nList Manager is used for finding, reviewing, and editing calls. If you're\nnot familiar with using List Managers scroll region and XQORs menus, refer\nto several DHCP applications that are using this interface (scheduling,\n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:00:57\n", "", "USER,ONE\n", "", ""], ["12", "XQHELP-LINK", "INVOKING HELP TEXT\n", "", "", "\nThere are several ways in which help frames can be linked to the\n help text.\n \n - Another way to invoke help text is through a routine. Set XQH to\n the INTERNAL NAME or INTERNAL NUMBER of the frame and D EN^XQH.\n This can be used in place of including lengthy help text in a\n routine.\n \n - Similarly, the EXECUTABLE HELP field in the data dictionary\n can be filled in so that help text is invoked.\nsystem, and correspondingly, several ways of invoking them.\n \n - A help frame can be linked to a menu option. This is done by\n filling in the HELP FRAME field in the OPTION file for the\n option you wish to have help text. Then, when the menu system\n prompts for a selection including this option, a response of\n the option name preceeded with a '?' will invoke the help text.\n The '???' response will show which options have associated\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["120", "XUDOC-KERMIT", "KERMIT\n", "", "", "\n \nEnter ?? for more options, ??? for brief descriptions, ?OPTION for help text.\n\nSelect Kermit menu Option: R Receive KERMIT file\n\nIf you enter 'XXX' for the file name it will be replaced by the name sent.\nRECIEVE TO KERMIT FILE:XXX\n ARE YOU ADDING 'XXX' AS A NEW KERMIT HOLDING (THE 12TH)? Y (YES)\n KERMIT HOLDING Replace File Name: YES// \n KERMIT HOLDING KERMIT transfer mode: TEXT// \nStarting KERMIT receive.N3\nSample KERMIT session.\n\n...........\n This is were the Micro-Computer sends a text file using KERMIT.\n...........\n\nDone with recieve, File transfer was successful. (542 bytes)\n\nSelect Kermit menu Option: ?\n\n E Edit KERMIT holding file\n\n R Receive KERMIT file\n S Send KERMIT file\n\nEnter ?? for more options, ??? for brief descriptions, ?OPTION for help text.\n\nSelect Kermit menu Option: E Edit KERMIT holding file\n\nSelect KERMIT HOLDING NAME: ?\n ANSWER WITH KERMIT HOLDING NAME\nCHOOSE FROM:\nSelect Kermit menu Option: ?\n DATA INSTALL \n DATA MODE\n IMAGE MODE \n INSTALL VAX-DS\n DEMO\n YOU MAY ENTER A NEW KERMIT HOLDING, IF YOU WISH\n NAME MUST BE 3-30 CHARACTERS, NOT NUMERIC OR STARTING WITH\n PUNCTUATION\nSelect KERMIT HOLDING NAME: DEMO\nNAME: DEMO// \n\nReplace File Name: YES// \nKERMIT transfer mode: TEXT// \nSelect ACCESS ALLOWED TO USER: \nWant to edit the data?: YES\nDATA: . . .\n . . .\n 69>KERMIT FILE TO SEND:DEMO\n 70>KERMIT transfer mode: TEXT// \n 71>Starting KERMIT send.\n 72>\n E Edit KERMIT holding file\n 73>...........\n 74> This is where the Micro-Computer receives a text file using KERMIT.\n 75>...........\n 76>\n 77>Done with send, File transfer was successful. (542 bytes)\nEDIT Option: \n\nSelect KERMIT HOLDING NAME: \n\nSelect Kermit menu Option: S Send KERMIT file\n R Receive KERMIT file\nKERMIT FILE TO SEND:DEMO\nKERMIT transfer mode: TEXT// \nStarting KERMIT send.\n\n...........\n This is where the Micro-Computer receives a text file using KERMIT.\n...........\n\nDone with send, File transfer was successful. (542 bytes)\n S Send KERMIT file\n\n
\n\n", "", "", "1989-04-21 00:00:00\n", "", "USER,ONE\n", "", ""], ["1200", "FSC U301 SCREENS", "", "", "", "\n \nalso select calls to be edited.\n \nEdit Calls - displays a single call at a time from which you can edit.\n \nA menu of actions is available on each screen.\n \nA menu of hidden actions is also available. Entering ?? will display\nthese actions. These actions let you scroll the display, search the list,\nget printouts, and define your custom defaults.\n \n Screens\n \n \n \nThree main List Manager screens are used in NOIS:\n \nList Calls - displays a list of multiple calls from which you can view or\nedit\n \nView Calls - displays formatted information on multiple calls. You can\n
\n\n", "", "", "1994-01-09 19:01:25\n", "", "USER,ONE\n", "", ""], ["1201", "FSC U302 TOUR GUIDE", "", "", "", "\n Tour Guide\nsave this list as another list name\nchange back to your default list\nremove all calls\nadd a single call to the list\nadd calls from 3 or 4 other lists\nsort the list by subject\nsort the list by call ID (descending)\nsort the list by status, site, date opened (descending)\nremove all calls\nadd all Kernel calls\n \nadd all open, Lab calls\nselect only the open calls\nremove all calls\nuse the query action to create a list that has open calls for Lab,\nSurgery, Kernel, and IFCAP for Denver and Grand Junction or any calls from\nany site on OERR\nlook at how lists are defined (dont change the definitions)\nuse edit calls, select all calls\nenter return to go to the next call\ngo to the last call on the list\nlog a call, leave it open\nenter previous call to back up\nenter qt to quit back to your list\ndo this again entering only specific selections from the list\nenter qt to quit back to your list\nuse view calls, select all calls\nselect a brief format\ngo through some calls\nchange to a detailed format\nsearch the list for the word task\nprint the list to your screen\nlook at what lists the call is now on\nchange to a format for the fields package, status, and specialist\nchange to a statistic format for site, status, and package\nchange to a format for an extract reort\nenter exit to quit back to the menu\nbrowse calls for any open calls\nclose the call\ngo to the next call\nchange the status to referred to developer\nlook at other information on this call\nsee if the call is on ISC-ONE, USERs list, send him a notification by mail\nlist calls for your default list\nincluding the text of this call, you can include some comments of your\nown.\nnotify ISC-TWO, USER by alert for this call\nset yourself to be notified by alert when the status changes on this call.\ngo back to the menu, use the secondary menu option to become ISC-ONE, USER\nread your mail\nbecome ISC-TWO, USER\nread your alert, close the call\ngo back to yourself\nread your alert\nchange to someone elses list\nchange to a list for open calls for your ISC\nchange to a list for open calls for Kernel\nchange to a list for open calls for Denver\n
\n\n", "", "", "1994-01-09 19:01:41\n", "", "USER,ONE\n", "", ""], ["1202", "FSC U40 NOIS CALL", "", "", "", "\n \nQuite a bit of information is displayed when listing calls. The call ID\nhas several pieces of information.\nOther Topics:\n Fields Dates and Timestamps\n Call ID Description, Resolution, Notes\n Status Audit History\n \n \n \n \n NOIS Call\n \n \n \nA NOIS call is made of several fields. Most information concerning the\nproblem is displayed in the view and edit screens. Information that\nconcerns the logging of the call (timestamps, when last edited, audits,\nnotifications, etc.) is displayed using the Other Information action on\nthe Edit Screen.\n \n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:01:54\n", "", "USER,ONE\n", "", ""], ["1203", "FSC U401 FIELDS", "", "", "", "\n \n There is a word processing field for notes that describes any ongoing\ndialog towards resolving the problem.\n \n \n \n \n \n \n \n \n Fields\n \n \n \nNearly all fields can be used in searches and displays.\n \nSome fields are not editable (timestamps, audits).\n \nThree word processing fields are editable. The problem description\ndescribes the problem. The resolution summary describes how it was fixed.\n
\n\n", "", "", "1994-01-09 19:02:42\n", "", "USER,ONE\n", "", ""], ["1204", "FSC U402 CALL ID", "", "", "", "\n \nYYMM = year and month the problem was reported\nI = ISC for support of the site\nNNNN = a sequence number of all NOIS calls for the month reported\n \nSites using NOIS locally would see an abbreviation for the service\nreporting the problem and the ISC could be set up as something meaningful\n- otherwise it would be 0.\n \n \n \n Call ID\n \n \n \nThe call ID or reference number is used to uniquely identify the call. It\nis composed of the site, date reported, ISC and a log sequence number.\nSSS-YYMM-INNNN\nwhere:\n \nSSS = site abbreviation\n
\n\n", "", "", "1994-01-09 19:03:05\n", "", "USER,ONE\n", "", ""], ["1205", "FSC U403 STATUS", "", "", "", "\n Status\nAbbrev - status; sup status; dev status; available statuses to select\nO - open; O; null; C, R, V, X\nC - closed; C; null or C (if closed by dev); O\nR - refer to dev; R; O; O, C, E, P, N, F, X\nV - vendor; V; null; O, C, R, X\nE - refer to ep; R; E; O, C, R, P, N, F, X\nP - awaiting patch; R; P; O, C, R, E, N, F, X\nN - next release; R; N; O, C, R, E, P, F, X\nF - future release; R; F; O, C, R, E, P, N, X\nX - canceled; X; null or X (if canceled by dev); O\nThere are two fields that determine a status for a call. There is a field\nA call that has been closed or canceled can be reopened by changing the\nstatus to open. A status history is kept of all status changes.\nfor support status and a field for development status. When making status\nchanges, only a single status is entered (the two fields are filled in\ndepending on the entry). This allows for searches for calls that are\nspecific for support or development.\nA support status can be open, refer to dev, vendor, closed, or canceled.\nA development status can be open, awaiting patch, next release, future\nrelease, refer to ep, closed, or canceled.\n
\n\n", "", "", "1994-01-09 19:03:36\n", "", "USER,ONE\n", "", ""], ["1206", "FSC U404 DATES AND TIMESTAMPS", "", "", "", "\n \nmaking notes, and when statuses are changed. All status changes are kept\nin kept in a status history file. Users making status changes are also\nstored. The user making the last edit is also stored. The date/time\nchanges are kept in the audit history.\n \nInformation on timestamp information can be reviewed using the Other\nInformation action on the Edit screen.\nFields for days since call was entered, last edited, and last status\nchange can be used in queries.\n \n Dates and Timestamps\n \n \n \nWhen entering a NOIS call, the date the problem was reported has to be\nentered. This date is used to create the Call ID. When closing a call,\nthe date the problem was resolved is entered.\n \nSeveral date/times are captured when editing a call: the date/time the\ncall was first entered, the last time editing, the date is captured when\n
\n\n", "", "", "1994-01-09 19:03:53\n", "", "USER,ONE\n", "", ""], ["1207", "FSC U405 DESC, RES, NOTES", "", "", "", "\n \nwhen closing the call. If a call is reopened, this text is copied as an\nentry into the Notes text.\n \nMaking notes describes any ongoing dialog towards resolving the problem.\nThis text cannot be edited. It is a single word-processing field, when\nmaking a note you enter text and when the text is accepted the text is\nappended to the notes field.\n \nAny of these fields can be used when searching for text.\n \n Description, Resolution, Notes\n \n \n \nThree word processing fields can be used for entering a call.\n \nThe problem description is describes the problem. This text can be edited\nas long as the call is not closed or canceled.\n \nThe resolution summary describes how it was fixed. This text is entered\n
\n\n", "", "", "1994-01-09 19:04:11\n", "", "USER,ONE\n", "", ""], ["1208", "FSC U406 AUDIT HISTORY", "", "", "", "\n \nThis information cannot be edited or queried.\n \n \n \n \n \n \n \n \n \n Audit History\n \n \n \nWhen entries have been made and then reedited or changed, changes are\nstored in the calls audit history word-processing field.\n \nThis information can be viewed using the Other Information action on the\nEdit screen.\n \n
\n\n", "", "", "1994-01-09 19:04:28\n", "", "USER,ONE\n", "", ""], ["1209", "FSC U50 LIST MANAGER", "", "", "", "\n List Manager\nprograms. The advantage is that records can be displayed and several\nactions are available to perform without having to navigate through\nseveral options (where each time you would have to select the record\nagain).\n \nList Manager provides a hidden menu of actions that are also available to\nuse. NOIS uses the hidden menu to contain actions that can generally be\ndone on any display. These actions include actions for scrolling the\nscreen or to go to a specific page of the display.\nThe action 'Search List' is useful for finding text within the display.\n \nThe actions 'Print List' and 'Print Screen' provide for getting printouts\nor non scrolled displays.\n \nNOIS includes help using ?, ??, or ???.\n \nNOIS also has User Defaults and List Definition available on the hidden\nmenu.\n \nNOIS uses two ways to quit List Manager. QT will quit the current display\nand return to any previous display. EX will exit back to the option menu.\nList Manager provides applications a means of scrolling documents or lists\nof items. Items can be selected from the list by using the available\nactions at the bottom of the screen. Note: this is not always intuitive -\nwith List Manager, you select the action, then you select the item.\n \nDocumentation on List Manager is found in PIMS documentation.\nThe actions are protocols (XQOR) that are used as menus or items that run\n
\n\n", "", "", "1994-01-09 19:04:40\n", "", "USER,ONE\n", "", ""], ["121", "XUDOC-%Z", "THE %Z EDITOR\n", "", "", "\n \ncareful. When a routine is filed it is filed by the name it was loaded from \nnot the first line tag, if the routine file is found then the routine name\n \nadded if not already there and a entry made of the date/time and duz of \nthe user that filed it. The main prompt is EDIT: and entering a ? will give \nyou help. You can work in two modes, line shows a complete line and lets \nyou move around it or replace to do replace/with editing.\nExample:\nZL ZU X ^%Z\n^%Z routine editor\n \nThis is a routine editor that can be used on all current DHCP computers. It\n is installed in the manager account as the ^%Z global by ZTMGRSET. It can \n also be setup by D ^ZTEDIT.\n \nTo use this editor ZLOAD the routine you want to edit and then X ^%Z to \nstart the editor. You can exit the editor without saving your changes so be \n
\n\n", "", "", "1992-04-15 11:57:00\n", "", "USER,ONE\n", "", ""], ["1210", "FSC U60 OPTIONS", "", "", "", "\n \nList Calls and Query Calls allow for selecting multiple calls. List Calls\nuses a selected list to get to the NOIS Calls screen. Query Calls begins\nby letting you enter a query to get those calls of interest. From the\nNOIS Calls screen you can perform any routine NOIS operations.\n \nAn option is provided for file maintenance. File Setup allows printing,\nsearching, and inquiring NOIS files. Supervisors can also edit and add\nnew entries to these files (except for the NOIS Call file which must be\nedited using the NOIS programs.\n \n Options\n \n \n \nNOIS only uses a few menu options.\nLogging a Call is used to enter new NOIS calls. It doesn't use List\nManager unless you want to review other calls.\nIf you already know the call you want to edit or review, use Edit a Call.\nClose a Call is a similar option.\n \n
\n\n", "", "", "1994-01-09 19:04:54\n", "", "USER,ONE\n", "", ""], ["1211", "FSC U70 NOIS USERS", "", "", "", "\n NOIS Users\nSpecialist\nThe specialist is someone who is entered in the NOIS Specialist file. A\nspecialist can enter, edit, or close any NOIS call. There are no\ndifferent privileges between support and development specialists.\nSpecialists can edit their own list definitions, notifications, and\ndefaults.\nSupervisor\nThe supervisor is a NOIS specialist who has the field, Acts as Supervisor,\nin the NOIS Specialist file set to YES. A supervisor can edit NOIS files\n(add new packages, specialists, etc.). They can edit the Acts as\n \nSupervisor field in the NOIS Specialist file. They can also edit others\nlist definitions, notifications, and defaults.\nThere are three types of NOIS users. No security keys are used in the\nNOIS software.\n \nUser (non-NOIS specialist)\nA user is someone who has the NOIS option but is not entered as a NOIS\nspecialist. This user can use any NOIS options but is restricted from\nediting data.\n
\n\n", "", "", "1994-01-09 19:05:12\n", "", "USER,ONE\n", "", ""], ["1212", "FSC U80 WORKING WITH LISTS", "", "", "", "\n \nlists will do.\n \nOther Topics:\n Types of Lists Queries\n Default List & Ownership Adding to a List\n Selecting/Changing Lists Removing from a List\n Saving a List Selecting from a List\n Sorting a List Defining a List\n Changing the List Display\n \n Working with Lists\n \n \n \nBeing able to find outstanding problems from a site, package, and\nspecialist are just a few of the uses for lists. You can review calls\nfrom any NOIS list. You cant change the definition of others lists or\nstore calls on their lists. You can define your own custom lists. Youll\nfind that as you use lists its easy to find calls of interest without\nhaving to define criteria or store calls. Usually one or two personal\n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:05:29\n", "", "USER,ONE\n", "", ""], ["1213", "FSC U801 TYPES OF LISTS", "", "", "", "\n Types of Lists\nStorage Only\nThese lists simply hold calls. Calls must be added manually to these\nlists, and manually deleted. They are like mail baskets - you have to\nmaintain them. These lists can be owned or be public. Any specialist can\ncreate storage only lists.\n \nIndexed\nIndexed lists are part of the NOIS software. You cant create them or\ndelete them. Calls are not stored with these lists. The list simply uses\na cross reference in the call file to access these calls. They are fast\n \nto access and automatically maintained. Compound cross references require\nthat you enter a value. For example, Open Calls by Site would require\nentering the site.\n \nActive Update\nSpecialists can define a list for a specific criteria. An active update\nlist uses a query as the definition of what calls should be on the list.\nThe query is the same syntax as when searching for calls. These lists are\nmaintained whenever someone edits a call. When a call is edited, it is\nreviewed by every active update criteria as to whether the call will be\nThere four types of lists.\nincluded or removed from the list (fortunately all this updating is going\non in the background). Notification can also be used with these lists.\nNotification using lists requires that the lists be owned.\n \nTemporary\nWhen you browse calls or receive notifications, notice that the title of\nthe list is Temporary List. This list is not defined, nor are calls\nstored on this list. When you leave this list the calls are not saved.\n \n
\n\n", "", "", "1994-01-09 19:05:47\n", "", "USER,ONE\n", "", ""], ["1214", "FSC U802 DEFAULT LIST", "", "", "", "\n \n(for storage only list) or change the definition of the list. Anyone can\nuse a list. A public list means that anyone can store and change the\nlist. Supervisors can store or change the definition of any list.\n \n \n \n \n \n \n \n Default List and Ownership\n \n \n \nEach specialist can specify a list as being a default list. This is the\nlist that is displayed when they use the List Calls option. The default\ncan be changed using the UD (user default) action on the hidden menu.\n \nStorage Only and Active Update lists are either public or owned. An owned\nlist means it has a defined owner. Only the owner can store to that list\n
\n\n", "", "", "1994-01-09 19:06:07\n", "", "USER,ONE\n", "", ""], ["1215", "FSC U803 CHANGING LISTS", "", "", "", "\n \nlist of NOIS calls the call still appears on the list. If you go back to\nan option and enter the list, the call would now not be on the list\n(assuming the background process is completed). The same is true when you\nchange the list and reenter the same list.\n \n \n \n \n \n \n Selecting and Changing Lists\n \n \n \nUsing lists involves either using the options List Calls, Query Calls, or\nreceiving a menu alert that lets you process a temporary list.\nOnce in the NOIS Calls screen, you can change to any list using the Change\nList action. Any time you change to a list, the list is rebuilt. This is\nof interest when you are using a list and edit the list. Perhaps your\nlist only has open calls and you close a call. When you return to the\n
\n\n", "", "", "1994-01-09 19:06:28\n", "", "USER,ONE\n", "", ""], ["1216", "FSC U804 SAVING A LIST", "", "", "", "\n \ntemporary lists.\n \n \n \n \n \n \n \n \n \n Saving a List\n \n \n \nYou can save calls to a storage list using the File (Save) action. If the\nlist is public or you are the owner of the list, the calls are saved to\nthe same list; otherwise you will have to save them to another list. You\ncan enter a new list at this time.\n \nYou cannot save onto other's lists or any index, active update, or\n
\n\n", "", "", "1994-01-09 19:06:50\n", "", "USER,ONE\n", "", ""], ["1217", "FSC U805 SORTING A LIST", "", "", "", "\n \nObviously dates appear in time order, but other fields may sometimes only\ndisplay an abbreviation of the value. If the abbreviated value appears on\nthe screen, it may seem to be out of order.\nUp to five fields can be used in a sort.\nAny field may be selected to be in descending order (ascending order is\nthe default). This is useful for displaying most recent dates.\n \n \n \n \nSorting a List\n \n \n \nTheres no particular order to the calls on a list.\nSorting the list is helpful when doing reviews, printouts, or obtaining\nextracts.\nYou can sort by any field value that is searchable (except for word\nprocessing fields).\nThe sorted output is by the field value and not the display value.\n
\n\n", "", "", "1994-01-09 19:07:03\n", "", "USER,ONE\n", "", ""], ["1218", "FSC U806 LIST DISPLAY", "", "", "", "\n \nS displays the abbreviation of the Status. M displays the abbreviation of\nthe Module/Version. U displays the initials of the Specialist opening the\ncall. P displays an abbreviation of the Priority for the call. Any, all,\nor none of these letters may be entered. The order is always S, M, U, P\ndisplaying between the Call ID and Call Subject.\n \nWhen you edit these defaults, the list must be rebuilt to show the\nchanges. You can change to this same list to have it rebuilt.\n \n \n Changing the List Display\n \n \n \nThe default list display on the NOIS Calls screen is the Call ID and Call\nSubject.\n \nYou can add additional items to the display by editing your user defaults\non the hidden menu. There is a field, list display, in the NOIS\nSpecialist files. You can include any of the letters S, M, U, and/or P.\n
\n\n", "", "", "1994-01-09 19:07:25\n", "", "USER,ONE\n", "", ""], ["1219", "FSC U807 QUERIES", "", "", "", "\n \nThe selections for the condition and value depend on the field. For\nexample, pointer type fields do not allow a contains or greater than\ncondition. Word-processing fields do not allow an equal condition. The\nexists and not exits conditions (null, not null) do not prompt for values.\n The between condition uses two values and only applies to number or date\nfields. Entering question marks for help will show the available\nselections.\nThe criteria can be continued using an and or or. Multiple operations of\nadding, removing, selecting, along with ands and ors, can find most calls\nof interest.\n Queries\nQueries are used to define active update lists. The query is stored with\nthe list definition.\n \nQueries provide a way for finding calls that meet a certain criteria.\nThe calls found can be added to the list or removed from list.\nSelect means that those calls on the list meeting the criteria will remain\non the list and those not are removed.\nEntering a criteria involves selecting the field (attribute), condition,\nand value. This is similar to FileMans search.\n
\n\n", "", "", "1994-01-09 19:07:44\n", "", "USER,ONE\n", "", ""], ["122", "XUDOC XUCOMMAND", "System Command Menu - XUCOMMAND\n", "", "", "\nObsolete help frame.\n
\n\n", "", "", "1992-04-15 12:00:00\n", "", "USER,ONE\n", "", ""], ["1220", "FSC U808 ADD TO LIST", "", "", "", "\n \nIf you have a criteria that applies to all calls (ex. add where call ID\nexists) then all calls would be added to your list.\n \nChanges to the list are only temporary unless the list is a storage only\nlist and the list is saved. The list name is display as modified when\nchanges are made.\n \n \n \n \n Adding to a List\n \n \n \nCalls can be added to the list individually by selecting the calls.\n \nCalls can be added by selecting other lists. The calls on those lists are\nmerged into the existing list.\n \nCalls can also be added using a query statement.\n
\n\n", "", "", "1994-01-09 19:08:00\n", "", "USER,ONE\n", "", ""], ["1221", "FSC U809 REMOVE FROM LIST", "", "", "", "\n \n \nAll calls can also be removed. This clears your list to add a new set of\ncalls.\n \nRemoving a call from a list in no way changes the information on the call.\nChanges to the list are only temporary unless the list is a storage only\nlist and the list is saved. The list name is displayed as modified when\nchanges are made.\n \n \n Removing from a List\n \n \n \nCalls can be removed from the list individually by selecting the calls\n \nCalls can be removed by selecting other lists. If the calls on those\nlists are on your list then the calls are removed from your list.\n \nCalls can also be removed using a query statement.\n
\n\n", "", "", "1994-01-09 19:08:16\n", "", "USER,ONE\n", "", ""], ["1222", "FSC U810 SELECT FROM LIST", "", "", "", "\n \nSelection is useful for filtering those calls that are of interest from a\nlarge list.\n \nChanges to the list are only temporary, unless the list is a storage-only\nlist and the list is saved. The list name is displayed as modified when\nchanges are made.\n \n \n \n \n Selecting from a List\n \n \n \nSimilarly to adding and removing, calls can be selected individually, by\nlists, or queries.\n \nCalls that have been selected remain on the list; the other calls are\nremoved.\n \n
\n\n", "", "", "1994-01-09 19:08:38\n", "", "USER,ONE\n", "", ""], ["1223", "FSC U811 DEFINE LIST", "", "", "", "\n \nActive update lists require entering a query definition, this is similar\nto using a regular query for browsing.\nIts usually easier to change to someone elses list, save a copy of it as\nyour own and then edit it. Lines in the query definition can be replaced,\ninserted, or removed.\nAutomatic notifications are also part of the list definition. You can\nspecify that calls being updated onto the list will be flagged; so that\nanytime these calls are edited or their status changes you can be notified\nby mail or alert.\n \n Defining a List\n \n \n \nYou can see how a list is defined by using the DL, Define List, action\nfrom the hidden menu.\nIf the list is public or you are the owner of the list, you can edit the\ndefinition of the list.\nYou can create a new list using the DL option, or in the case of storage\nonly lists, you can also create those when doing a File (Save) operation.\n
\n\n", "", "", "1994-01-09 19:08:55\n", "", "USER,ONE\n", "", ""], ["1224", "FSC U90 EDIT CALLS", "", "", "", "\n \nsearched for.\n \nOther Topics:\n Logging a New Call Making Notes\n Closing a Call Cancelling a Call\n Referring a Call to Dev Reopening a Call\n Status Changes\n \n \n \n Entering/Editing Calls\n \n \n \nThe main NOIS activity is logging calls. The problem is entered, the\nsolution (if available) is entered, along with whatever other information\nneeded to document the call.\n \nAny specialist has access to edit any NOIS call. Anyone editing a call is\ndocumented as making an entry. Any calls not attended to can be easily\n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:09:09\n", "", "USER,ONE\n", "", ""], ["1225", "FSC U901 LOG NEW CALL", "", "", "", "\n \nIf a call is entered by a help desk with only minimal information, the\ncall can be edited to fill in the remaining information.\n \n \n \n \n \n \n \n \n Logging a New Call\n \n \n \nA new call can be entered from the option, New Call, or any of the List\nManager screens for NOIS calls, edit, or view.\n \nA call must have as a minimum: the location reporting the problem and the\ndate reported (this makes up the call ID).\n \n
\n\n", "", "", "1994-01-09 19:09:28\n", "", "USER,ONE\n", "", ""], ["1226", "FSC U902 CLOSE CALL", "", "", "", "\n \n \nA closed call can be reopened by changing the status to open.\n \n \n \n \n \n \n \n \n Closing a Call\n \n \n \nA call can be closed from the option, Close Call, or from the edit screen.\n \nA status change to close will require closing the call.\n \nTo close the call, enter the date the problem was resolved and the\nresolution summary.\n
\n\n", "", "", "1994-01-09 19:09:46\n", "", "USER,ONE\n", "", ""], ["1227", "FSC U903 REFER TO DEV", "", "", "", "\n \nA status can be referred back to support by changing the status to open.\n \n \n \n \n \n \n \n \n \n Referring a Call to Development\n \n \n \nChanging a status to refer to dev changes the support status to refer to\ndev and the development status to open. The status can now be changed to\nrefer to ep, next release, future release, and awaiting patch. The\nsupport status stays at refer to dev while any of these statuses are\nchosen. This permits support to view the call as being dependent on some\nactivity by the developers of the software.\n
\n\n", "", "", "1994-01-09 19:10:07\n", "", "USER,ONE\n", "", ""], ["1228", "FSC U904 STATUS CHANGE", "", "", "", "\n \nsupport and development status. The current status determines what the\nstatus can be changed to.\n \nStatus changes are recorded in a status history of the call.\n \nA status change is also an indicator that may trigger notification.\n \n \n \n \n Status Changes\n \n \n \nThe Status Change action on the edit screen changes the status of the\ncall.\n \nClosing a call changes the status to closed.\n \nWhen changing a call, only one selection is made. This status updates the\n
\n\n", "", "", "1994-01-09 19:10:25\n", "", "USER,ONE\n", "", ""], ["1229", "FSC U905 MAKING NOTES", "", "", "", "\n \nnotes.\n \nOnce a note has been entered, it cannot be re-edited (somewhat like\nreplying to a mail message). You can make additional notes, but not edit\nthose that have been entered.\n \nAll notes are viewed on a detailed display. The brief format only\ndisplays the first three lines of the last note entered.\n \n \n Making Notes\n \n \n \nNotes can be made to add comments concerning the progress of the call.\n \nNotes do not change the status of the call. A note does change the last\ntime the call was edited (of interest when specifying notification).\n \nNotes are appended to an ongoing word-processing field that contains all\n
\n\n", "", "", "1994-01-09 19:10:45\n", "", "USER,ONE\n", "", ""], ["123", "XUDOC KEY VARIABLES", "KEY VARIABLES\n", "", "", "\nObsolete help frame.\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 12:17:00\n", "", "USER,ONE\n", "", ""], ["1230", "FSC U906 CANCEL A CALL", "", "", "", "\n \nA canceled call can be reopened by changing its status to open.\n \n \n \n \n \n \n \n \n \n Canceling a Call\n \n \n \nCalls cannot be deleted.\n \nIf a call was made in error, it can be canceled.\n \nTo cancel a call, the status is changed to canceled.\n \n
\n\n", "", "", "1994-01-09 19:11:07\n", "", "USER,ONE\n", "", ""], ["1231", "FSC U907 REOPEN A CALL", "", "", "", "\n \n \nThere is no status of reopen. If any active lists uses status = open to\nadd to the list, reopening the call would have the call added back on\nlist.\n \n \n \n \n \n \n Reopening a Call\n \n \n \nA closed or canceled call can be reopened by changing its status to open.\n \nIf the call was closed, the resolution information is saved as a note.\n \nThere is a field that contains the last reopened date. This field is\nuseful for searching for any calls that have been reopened.\n
\n\n", "", "", "1994-01-09 19:11:21\n", "", "USER,ONE\n", "", ""], ["1232", "FSC U100 REVIEW CALLS", "", "", "", "\n Reviewing Calls\nThe edit screen allows only one call at a time to be displayed. You can\nchange the format of the display and that format will be used on any\nsubsequent displays.\nThe view screen allows multiple calls to be displayed. This format is\nbetter for text searches (the SL action), and for statistic and custom\nformats such as extracts.\nOther Topics:\n View Calls Statistics\n Format Changes Exporting to Spreadsheets\n Brief/Detailed Formats Printouts\n \n Fields Search for Text in List\n Custom\nCalls can be displayed using either the Edit Calls or View Calls.\nBoth actions allow for calls to be selected from the list. Calls don't\nhave to be displayed in order to be selected. Often you know that the\ncalls being selected are of interest because you have added and removed\ncalls, so that the remaining list consists of precisely those calls you're\ninterested in. You may also scroll through the list, jotting down calls\nof interest.\n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:12:07\n", "", "USER,ONE\n", "", ""], ["1233", "FSC U1001 VIEW CALLS", "", "", "", "\n \nreturn to the view screen. It is sometimes easier to review calls for\nspecific information and then editing only those calls.\n \n \n \n \n \n \n \n \n View Calls\n \n \n \nThe view screen allows multiple calls to be displayed.\n \nThe calls always begin with the line from the list and are separated by a\ndashed line.\n \nThe calls can be edited by selecting calls again. After editing you'll\n
\n\n", "", "", "1994-01-09 19:12:20\n", "", "USER,ONE\n", "", ""], ["1234", "FSC U1002 FORMAT CHANGES", "", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n Format Changes\n \n \n \nFormat changes can be selected when using view or edit screens. When\nentering the view screen you are also prompted with a format.\n \nThe formats are: Brief, Detailed, Fields, Custom, and Statistics\n \n \n
\n\n", "", "", "1994-01-09 19:12:34\n", "", "USER,ONE\n", "", ""], ["1235", "FSC U1003 BRIEF/DETAIL FORMAT", "", "", "", "\n \n \nThe detailed format displays all information about the call except\ninformation such as edits, audits, timestamps.\nThis format is good for searching for text using the SL action.\n \n \n \n \n \n \n Brief and Detailed Formats\n \n \n \nThe brief format is designed for a single screen (the edit screen only\ndisplays one call).\n \nOnly the first three lines of word processing entries are displayed.\n \nThe brief format displays the most common information on a call.\n
\n\n", "", "", "1994-01-09 19:12:58\n", "", "USER,ONE\n", "", ""], ["1236", "FSC U1004 FIELDS", "", "", "", "\n \n \nThis format is useful for viewing a profile of information on calls.\n \n \n \n \n \n \n \n \n Fields\n \n \n \nThe fields format displays any selected fields except audit, status\nhistory, and a few others.\n \nThe fields are displayed in the order selected.\n \nWord processing fields display all text.\n
\n\n", "", "", "1994-01-09 19:13:14\n", "", "USER,ONE\n", "", ""], ["1237", "FSC U1005 CUSTOM", "", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n Custom\n \n \n \nThe custom format can use a special routine that displays a hard-coded\nreport, a defined list of fields, or an extract report to display\ninformation to be imported into spreadsheets or tables.\n \n \n \n
\n\n", "", "", "1994-01-09 19:13:27\n", "", "USER,ONE\n", "", ""], ["1238", "FSC U1006 STATISTICS", "", "", "", "\n \ngiven, as well as the total and average for number-type fields\n \n \n \n \n \n \n \n \n \n Statistics\n \n \n \nThe statistic format is useful for a quick glance at type of activity.\n \nIt is best used when viewing calls.\n \nThe format shows the percentage of all selected calls for selected fields.\nThe percentages of fields for dates, pointer values, and numbers are\n
\n\n", "", "", "1994-01-09 19:13:39\n", "", "USER,ONE\n", "", ""], ["1239", "FSC U1007 SPREADSHEETS", "", "", "", "\n \nYou can now enter any fields that will be the headings for the columns of\nthe table.\n \nWhen youre done entering the fields, you will be prompted for a delimiter.\n You can enter any character. If the delimiter appears in the value, the\ndelimiter will be replaced by a space (ex. last name,first name -> last\nname first name).\n \nDates and times will be displayed in the format (m/d/y hh:mm).\n \n Exporting to Spreadsheets\n \n \n \nIf you are using NOIS through a terminal emulator on your PC, you can\ncapture data to a text file and then import the data into tables or\nspreadsheets.\n \nFrom your list of calls use View Calls for the calls you want to capture.\nUse the custom format and select extract.\n
\n\n", "", "", "1994-01-09 19:14:01\n", "", "USER,ONE\n", "", ""], ["124", "XUHFSPARAM-VXD", "HFS I/O OPERATION-VXD\n", "", "", "\n READONLY -- Only allows you to read from the specified file.\nREAD/WRITE -- Allows read and write operation to an existing file.\n If a write operation is performed, the data from\n the write operation is appended to the file.\n Writing to the file will not be allowed. Therefore,\n you will not be able to direct reports to the file.\n \nNEWVERSION -- A new file will be created with a higher version number.\n If NEWVERSION is not specified, an existing file is used.\n If the selected file does not exist, a new file will\n be created whether or not NEWVERSION is specified.\n \n
\n\n", "", "", "1989-06-06 00:00:00\n", "", "USER,ONE\n", "", ""], ["1240", "FSC U1008 PRINTOUTS", "", "", "", "\n \n \nWhen capturing the screen display to a terminal emulator or slave printer,\nuse the PL or PS action on the hidden menu to print the list or screen.\n \nThe reports option allows you to select a report to display. A report is\nmade up of a list, a format, and a sort format.\n \n \n \n \n Printouts\n \n \n \nNOIS will generally be used from remote locations. Printouts will be\nlimited to capturing information to a PC application or using slave\nprinters.\n \nYou can use a mail message to send calls to a local location whereby the\nmail message can be printed.\n
\n\n", "", "", "1994-01-09 19:14:14\n", "", "USER,ONE\n", "", ""], ["1241", "FSC U1009 SEARCH FOR TEXT", "", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n Search for Text in List\n \n \n \nNOIS uses a List Manager utility to search for text within the list.\n \nThe SL action is on the hidden menu.\n \nIt is most useful when viewing detailed formats of multiple calls.\n \n
\n\n", "", "", "1994-01-09 19:14:44\n", "", "USER,ONE\n", "", ""], ["1242", "FSC U110 NOTIFICATION", "", "", "", "\n \nto another person.\nNotifications can also be scheduled to be sent to sites.\nAny user can manually send notifications.\n \nOther Topics:\n Mail & Menu Alerts Automatic Notification\n Notifying Others Removing Notification\n Notifying Yourself Site Notification\n \n \n Notification\n \n \n \nNotifications allow sending messages and NOIS information to others or\nyourself.\nA notification can be sent by mail message or menu alerts.\nThe notification action appears on the list, edit, and view screens.\nYou can send notifications, schedule notifications to be sent to you, and\nremove scheduled calls from notifying. You can't schedule a notification\n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:15:04\n", "", "USER,ONE\n", "", ""], ["1243", "FSC U1101 MAIL, MENU ALERTS", "", "", "", "\n Mail, Menu Alerts\nNOIS should be used for documenting dialog on a problem instead of\nmultiple discussions on mail.\nNotifying with menu alerts allows you to send a simple message to someone\nthat will show up as an alert whenever the recipient is on the system.\nYou can optionally include any calls on your current list. This allows\nthe recipient to process the calls and immediately take some action (read,\nedit, close, call the site back, etc.).\nBesides receiving a list of calls with an alert, a short message with the\nreason of the notification is displayed.\n \n \n \n \nNotifying using mail allows you to send a message and/or load the list\ninto the message. You can thus send several calls in the same mail\nmessage with whatever format you've composed on the display (lists, custom\nformats, statistics, etc.). You can also edit this message before sending\nit.\nMail uses an email address that can be a remote domain, so that you can\nhave messages sent to you locally.\n
\n\n", "", "", "1994-01-09 19:15:20\n", "", "USER,ONE\n", "", ""], ["1244", "FSC U1102 NOTIFY OTHERS", "", "", "", "\n \nhowever you want it before using notification (sort, format, etc.).\n \nYou can add a short message to the notification. This shows up when\ndisplaying an alert or within the mail message.\n \n \n \n \n \n \n Notifying Others\n \n \n \nYou can notify others by mail or using menu alerts.\n \nBoth methods allow sending to multiple recipients including mail groups.\n \nUse the Notification action on the list, edit, or view screens. Since you\ncan include the list in a mail message you should format the screen\n
\n\n", "", "", "1994-01-09 19:15:33\n", "", "USER,ONE\n", "", ""], ["1245", "FSC U1103 NOTIFY YOURSELF", "", "", "", "\n \nbe notified.\n \nYou can be notified by mail or alert. Mail uses the email address in the\nNOIS Specialist file.\n \n \n \n \n \n \n Notifying Yourself\n \n \n \nYou can manually select calls and be notified whenever the calls are\nedited or when the calls status is changed.\n \nUse the Notification action on the list edit, or view screens.\n \nAny time someone else (not yourself) edits or changes the status you will\n
\n\n", "", "", "1994-01-09 19:15:49\n", "", "USER,ONE\n", "", ""], ["1246", "FSC U1104 AUTO NOTIFICATION", "", "", "", "\n \n \nWhenever calls are updated to your list, the calls are scheduled for\nnotification. Mail uses an email address in the NOIS Specialist file.\n \nSince the list is defined with a query, any criteria can be used for your\nnotification.\n \n \n \n \n Automatic Notification\n \n \n \nYou can be automatically notified when calls are edited or the status\nchanges.\n \nTo do this, you use a list that you own.\nYou can specify an event method - mail or alert, and event - edit or\nstatus change.\n
\n\n", "", "", "1994-01-09 19:16:10\n", "", "USER,ONE\n", "", ""], ["1247", "FSC U1105 REMOVE NOTIFICATION", "", "", "", "\n \nYou may get carried away with notifying yourself or just have some\nreoccurring notification on calls that your really not interested in. You\ncan turn off notification using the Notification action on the list, edit,\nand view screens by selecting those calls on your current list.\n \n \n \n \n \n \n Removing Notification\n \n \n \nOnce alerts have been displayed they are removed from further alerting.\n \nAlerts from others are alerted and processed individually.\n \nAlerts from your scheduled notifications are processed as the same alert.\n \n
\n\n", "", "", "1994-01-09 19:16:25\n", "", "USER,ONE\n", "", ""], ["1248", "FSC U1106 SITE NOTIFICATION", "", "", "", "\n \nalerts.\n \nIf mail is used then it is sent to the entry in the sites Email field.\nAn event is also entered: edit or status change.\n \n \n \n \n \n \n Site Notification\n \n \n \nSites (or services when NOIS is used locally) can schedule notification by\nediting the NOIS Location file. Supervisors can edit this file.\n \nA method is entered - mail or alert.\n \nIf an alert is entered, the user in the Site Contact field is sent menu\n
\n\n", "", "", "1994-01-09 19:16:38\n", "", "USER,ONE\n", "", ""], ["1249", "FSC U120 NOIS IN A WORKGROUP", "", "", "", "\n Using NOIS in a Workgroup\n \nNOIS is maintained by its own users. Users can review and act on the\ncalls they are responsible for.\n \nCalls can be grouped to meet your needs.\n \nCalls can be grouped that reflect a group of individuals (site\nspecialists, package specialists, package development) that remain within\nthe boundaries of an ISC or cross over ISCs, EPs, or sites.\n \n \nSupervisors can define other users lists, defaults, and notifications.\n They can also use NOIS to easily monitor what problems are being taken\ncare of and what arent.\n \nMailgroups can be used for sending notifications on calls.\n \nUsers can know of other users involved on a call by using the Other\nInformation action on the edit screen. This shows what lists this call is\non (with the lists owner and functional area) and users that have\nnotifications.\nWho supports what sites, packages, or systems is not always the same from\n \nSupport sections need to organize such that calls are directed to the\nappropriate person.\n \nDevelopment is involved in calls referred to them and can take appropriate\naction.\nISC to ISC or from day to day. To allow for variations in organizational\nstructure and changing events (changes in staff, vacations, training, site\nvisits, projects, etc.), the NOIS software is very flexible.\n \nNOIS is user-oriented and allows working in groups without imposing an\norganizational structure.\n
\n\n", "", "", "1994-01-09 19:16:58\n", "", "USER,ONE\n", "", ""], ["125", "XUHFSPARAM-MVX", "HFS I/O OPERATION-MVX\n", "", "", "\n READ ACCESS -- Pemits you to read from the specified file.\nSTREAM FORMAT -- Data written to the specified file will be in\n stream format with implied carriage return/line feed.\n \nNote: The default access is READ/WRITE. Writing to an existing file\n may cause part/all of the previously stored data to be deleted.\n \n NEWVERSION -- A new file will be created with a higher version number.\n If NEWVERSION is not specified, an existing file is used.\n If the selected file does not exist, a new file will\n be created whether or not NEWVERSION is specified.\n \n WRITE ACCESS -- Permits you to write to the specified file.\n \n
\n\n", "", "", "1989-06-06 00:00:00\n", "", "USER,ONE\n", "", ""], ["1250", "FSC U130 NOIS WITH HELP DESK", "", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n Using NOIS with a Help Desk\n \n \n \nCalls that are received by a help desk need only minimal information on\nthe call.\n \nA call reference requires the location and date the problem was reported.\n \n \n
\n\n", "", "", "1994-01-09 19:17:18\n", "", "USER,ONE\n", "", ""], ["1251", "FSC U140 ONLINE HELP", "", "", "", "\n \n \n \n \n \n \n \n \n \n \n \n On-line Help\n \n \n \nAll prompts will have on-line help.\n \nWhen using List Manager you can enter ?, ??, ???. A single question mark\nshows a help frame with an explanations for the menu actions. A double\nquestion mark shows the hidden menu actions. Three question marks gives a\nhelp frame with an index of NOIS subjects.\n
\n\n", "", "", "1994-01-09 19:17:38\n", "", "USER,ONE\n", "", ""], ["1252", "FSC U150 CUSTOM SETUP", "", "", "", "\n \neditable using NOIS programs.\n \nOther Topics:\n User Defaults\n Lists\n Notifications\n \n \n \n \n Custom User Setup\n \n \n \nMost custom changes can be done by using the UD and DL actions (user\ndefaults and define list) on the hidden menu.\n \nThere is also an option for file setup. This option allows FileMan\ninquiry, printouts, and searches on the NOIS files. Supervisors can edit\nthese files with the exception of the NOIS Call file which is only\n
\n\n", "\n- \n\n
\n", "", "1994-01-09 19:18:07\n", "", "USER,ONE\n", "", ""], ["1253", "FSC U1501 USER DEFAULTS", "", "", "", "\n \nYou can display others defaults but you can only edit your own.\n \nSupervisors can edit others defaults.\n \n \n \n \n \n \n \n User Defaults\n \n \n \nUser defaults apply to anyone in the NOIS Specialist file.\n \nThe UD action on the hidden menu allows editing prompts, dtime (during a\nNOIS session), protocol actions being displayed, default list, list\ndisplay, email address, etc.\n \n
\n\n", "", "", "1994-01-09 19:18:23\n", "", "USER,ONE\n", "", ""], ["1254", "FSC U1502 LISTS", "", "", "", "\n \na line. Its generally easier to change to a similar list that you want to\nuse, save it with a new name, and then edit any changes.\n \nAfter editing a list query, you should rebuild it This adds and removes\nany calls appropriate for the new definition.\n \nYou can display any list definition but you can only edit active update\nand storage-only lists that are public or you are the owner of.\nSupervisors can edit others lists.\n \n Lists\n \n \n \nThe DL action on the hidden menu allows creating, editing, and rebuilding\nlists.\n \nNotifications can be included in the list definition.\n \nQueries can be edited by inserting new lines, removing lines, or replacing\n
\n\n", "", "", "1994-01-09 19:18:39\n", "", "USER,ONE\n", "", ""], ["1255", "FSC U1503 NOTIFICATIONS", "", "", "", "\n \nand storage only lists that are public or you are the owner of.\n \nSupervisors can edit others lists.\n \n \n \n \n \n \n \n Notifications\n \n \n \nNotifications can be applied to list definitions (active update lists\nonly).\n \nThe DL action on the hidden menu allows editing notifications.\n \nYou can display any list definition but you can only edit active update\n
\n\n", "", "", "1994-01-09 19:18:54\n", "", "USER,ONE\n", "", ""], ["1256", "FSC U160 LOCAL NOIS", "", "", "", "\n \n \nThe NOIS ISC file could be filled in with names of specialties within\nIRMS.\n \nThe fields for ISC and Location in the NOIS Field file would have\nappropriate text names for specialty and service.\n \nProblems that would require help from an ISC could be put into a mail\nmessage and sent to the appropriate person at the ISC.\n \n Setting Up Local NOIS\n \n \n \nNOIS can be used by sites within a medical center.\n \nThe Location file would be entered with services (site names would not\nneed to be deleted).\n \nThe NOIS Parameter file would be set for local use.\n
\n\n", "", "", "1994-01-09 19:19:13\n", "", "USER,ONE\n", "", ""], ["1257", "FSC U170 IN THE WORKS", "", "", "", "\n \narchive/purge\nexpanded user defaults\npossibly: links to site tracking, links to patch module, window front end\n \n \n \n \n \n \n \n In the Works\n \n \n \nbatch entry\nclone a call\nimport entry\nword in text search\nsearch optimization\nsearch breakout\n
\n\n", "", "", "1994-01-09 19:19:27\n", "", "USER,ONE\n", "", ""], ["1258", "FSC U180 USABILITY TEST", "", "", "", "\n Usability Test\n2. Select some calls to edit.\n3. Find a call that is open -- close the call.\n4. Change the format of the call. (for example, if the call is in a\nBrief format, change it to Detailed).\n5. Return to your list of calls.\n6. View several calls in a format that displays only the fields:\nspecialist, package, and support status.\n7. Switch format to Detailed.\n8. Search the list for the word task. Use the Search List action from\nthe hidden actions.\n \n9. Return to your list of calls.\n10. Remove all calls from your list.\n11. Add calls where the support status is open and the support ISC is\nSalt Lake City (use a query to specify this criteria).\n12. Select only those calls about Kernel 7.1 (use a query to specify this\ncriteria).\n13. Switch the modified list back to your personal list of calls.\nThats it.\n \nAfter you're done, log and close a NOIS call (on NOIS) and describe any\nTest the software by performing the following tasks.\nproblems you had, places where the software was confusing, etc. In the\nresolution summary offer any suggestions, opinions, or questions you have.\nSituation:\nYou are a field support specialist with a personal list of NOIS calls set\nup to automatically update calls that you are interested in.\n(Only use the List Calls option)\nTasks:\n1. Review your list of calls.\n
\n\n", "", "", "1994-01-09 19:19:41\n", "", "USER,ONE\n", "", ""], ["1259", "FSC U1 NOIS", "", "", "", "\n NOIS USER MANUAL\n \n What's NOIS Reviewing Calls\n What's New Notification\n Getting Started NOIS in a Workgroup\n NOIS Call NOIS with a Help Desk\n List Manager Online Help\n Options Custom User Setup\n NOIS Users Setting up Local NOIS\n Working with Lists Usability Test\n Entering/Editing Calls Topic Index\n \n \n \n \nThe following topics can be selected by entering in the topic name.\nThis online help represents the information in the user manual except\nfor illustrations.\n \n \n \n
\n\n", "\n- \n\n
\n", "", "1994-01-09 21:15:24\n", "", "USER,ONE\n", "", ""], ["126", "XUHFSPARAM-MSM", "HFS I/O OPERATION-MSM\n", "", "", "\n READ -- Only allows you to read from the specified file.\n APPEND -- Data from a write operation will be appended to the file.\n Writing to the file will not be allowed. Therefore,\n you will not be able to direct reports to the file.\n \n WRITE -- Allows you to direct your reports(output)\n to the specified file.\n \n MIXED -- Allows read and write operation to the specified file.\n \n
\n\n", "", "", "1989-06-06 00:00:00\n", "", "USER,ONE\n", "", ""], ["1260", "ECSCPT", "Event Code Screens with CPT Codes\n", "", "W @IOF\n", "\nThis option allows you to print/display event code screens \n - National Number\n - CPT Code \n (Inactive CPT codes are flagged with an *I* when printing \n both active and inactive codes)\n - Event Code Screen Synonym\n - Associated Clinic\n - Stop Code\n - Credit Stop Code\n - CHAR4 Code\n - MCA Labor Code\nwith active/inactive/both CPT codes for all or a specific DSS\nUnit. The output includes:\n \n - Run Date and Time\n - Location\n - DSS Unit\n - Category (if applicable)\n - Procedure Name\n
\n\n", "", "", "2005-08-24 16:29:38\n", "", "USER,SIXTYFIVE\n", "", ""], ["1261", "ECINCPT", "National/Local Procedure Codes with Inactive CPT\n", "", "W @IOF\n", "\nThis report provides a list of National and Local Procedure Codes with \n- CPT Inactive Date\n \nYou can list the report in: \n- Ascending order\n- Descending order\n \nThe output includes:\n \n - Run Date \n - Selected sort criteria\ninactive CPT codes from file #725.\n - Procedure Number\n - Procedure Name\n - CPT Code\n - CPT Inactive Date\n \nYou can choose to include National or Local procedures or both.\n \nThe report can be sorted by:\n- Procedure Name\n- Procedure Number\n- CPT Code\n
\n\n", "", "", "2005-08-24 16:41:56\n", "", "USER,SEVENTEEN\n", "", ""], ["1262", "ORBA-SHD", "ORBA-SHD\n", "", "", "\nShipboard Hazard and Defense (SHD):\nno charge for care and medications provided for\ntreatment of conditions related to exposure.\nVeterans with conditions\nrecognized by VA as associated with Project 112/\nSHAD, shipboard and land-based biological and\nchemical testing conducted by the United States\n(U.S.) military between 1962 and 1973 are\neligible for enrollment in priority group 6,\nunless eligible for enrollment in a higher\npriority. In addition, veterans receive care at\n
\n\n", "", "", "2006-07-26 09:46:00\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["1263", "ECRDSSA", "DSS Unit Activity Report\n", "", "W @IOF\n", "\nThis option allows the user to print/display all patients for the\n - Procedure Code\n - Procedure Name\n - Volume\n - Primary Diagnosis\n - Associated Clinic, stop code, credit stop code, and CHAR4 code\n - Primary Provider\n - Synonym\n \nIf more than one location has been set up, you will be prompted to \nselect all or specific locations. You will also be prompted to select all\nspecified location(s) and DSS Unit(s) within a selected date range. The\nor specific DSS Units.\npatients may be sorted by Patient Name, SSN, or Provider Name. The output\nincludes:\n \n - Patient Name\n - Last four digits of Patient SSN\n - Inpatient/Outpatient Indicator\n - Procedure Date and Time\n
\n\n", "", "", "2007-10-23 12:45:44\n", "", "USER,FIFTYFOUR\n", "", ""], ["1264", "ECSTPCD", "DSS Units with any Associated Stop Code Errors\n", "", "W @IOF\n", "\nThis report provides a list of DSS Units with any error with the \nassociated Stop Code.\n \nThe report displays:\n - DSS Unit IEN\n - DSS Unit Name\n - Associated Stop Code IEN\n - Associated Stop Code Name\n - Error\n
\n\n", "", "", "2010-04-13 10:50:40\n", "", "USER,FIFTYFOUR\n", "", ""], ["1265", "ECRECER", "Event Capture Encounters Report\n", "", "", "\n** This report is formatted for a 132-column device. **\n - Last four digits of patient SSN\n - Inpatient/Outpatient Indicator\n - Procedure Date and Time\n - Primary provider\n - DSS unit\n - Total Procedure Volume (all procedures on same D/T and in same DSS unit)\n - Clinic\n - Stop Code\n - Credit Stop Code\n - CHAR4\n \n - MCA Labor Code\nThis option allows you to print/display/export Event Capture encounter\ndata within a specified date range for selected locations and DSS units.\nThe report can be sorted by patient, provider or clinic.\n \nThe output includes:\n \n - Patient name \n
\n\n", "", "", "2011-12-20 15:32:24\n", "", "USER,SEVENTEEN\n", "", ""], ["1266", "ECRECSIC", "EC SCREENS WITH INACTIVE DEFAULT ASSOCIATED CILNIC\n", "", "", "\n** This report is formatted for a 132-column device. **\n - Category\n - Procedure code\n - Clinic IEN\n - Clinic name\n \nThis option allows you to print/display/export inactive default\nassociated clinic data for specified locations and DSS units.\n \nThe output includes:\n \n - DSS unit name\n - Location\n
\n\n", "", "", "2011-12-20 16:15:59\n", "", "USER,FIFTYFOUR\n", "", ""], ["1267", "ECRECSPC", "DSS UNITS/EVENT CODE SCREENS FOR SELECTED PROCEDURE CODE\n", "", "", "\n** This report is formatted for a 132-column device. **\n - Location\n - Category\n - EC screen status\n \nThis option allows you to print/display/export DSS unit and EC\nscreen data for a selected procedure code and specified locations.\n \nThe output includes:\n \n - DSS unit IEN\n - DSS unit name\n
\n\n", "", "", "2011-12-20 16:18:02\n", "", "USER,FIFTYFOUR\n", "", ""], ["1268", "ECRDSSUA", "USER ACCESS TO DSS UNITS FOR SELECTED LOCATIONS/DSS UNITS\n", "", "", "\n** This report is formatted for a 132-column device. **\n - User IEN from NEW PERSON (#200) file\n - Person Class/Classification\n \nThis option allows you to print/display/export user access to DSS\nunit data for specified locations and DSS units.\n \nThe output includes:\n \n - DSS unit name\n - User name\n
\n\n", "", "", "2011-12-20 16:19:51\n", "", "USER,FIFTYFOUR\n", "", ""], ["1269", "ECINACTECS", "Inactivate Multiple Event Code Screens\n", "", "", "\nThis option allows you to identify active Event Code (EC) Screens that \ndefined.\n \nTo the left of each line in the list box will be a check box. Clicking \non an unchecked box will indicate the record is to be inactivated. \nClicking on a checked box will result in the check box being unchecked, \nand no longer a candidate for inactivation.\n \nWhenever one or more check boxes is checked, the 'Apply' button will be \nenabled. Clicking the 'Apply' button will result in the display of a \nconfirmation screen. If the user wants the selected records to be \nuse a selected EC product code. The EC product code can be a CPT code, a \ninactivated, then the 'OK' button should be clicked; all records that \nwere checked will now be inactivated. If the user does not want to \ninactivate the checked records, the 'Cancel' button should be clicked; \nthe user will then be free to check records, uncheck records or cancel \nout of the selection screen.\n \nOnce records have been inactivated, a list of inactivated records will \ndisplay on the screen. In addition to the 'Print' button being enabled, \nthe 'Apply' button will now be disabled. To print a hard copy of the EC \nScreens that were just inactivated, click the 'Print' button and follow \nnational EC procedure code or a local EC procedure code.\nthe printing instructions.\n \nAll active EC Screens that use the selected product code will be \ndisplayed in the list box below the selected EC product code, sorted by \nunique DSS Unit, Location and Category. The DSS Unit will be displayed \nfor the first EC Screen that contains the unique value; the Category will \nonly be displayed if a Category was selected when the EC Screen was \n
\n\n", "", "", "2011-12-22 17:27:18\n", "", "USER,SEVENTEEN\n", "", ""], ["127", "XUDOC ZOSF", "%ZOSF GLOBAL REFERENCE\n", "", "", "\nThe ^%ZOSF global is used to hold operating system-dependent logic so\nthat programs may be written independently of any specific operating\nsystem. Most of the nodes contain logic that must be executed to return\na value, e.g. X ^%ZOSF("SS"). See the Kernel documentation for a\nfunctional description of the nodes.\n\n\n", "", "", "1992-04-15 12:12:00\n", "", "USER,ONE\n", "", ""], ["1270", "LRCAPFF", "LRCAPFF\n", "", "", "\nThis LEDI Order Test Mapping option is used to identify where the data\n \nThe second step is to choose the local Laboratory Test Name (File #60). \n \nThe third step is to choose the associated National VA Lab Code for that\ntest (File 64 entry). Once a valid National VA Lab Code is chosen - the\nsystem will ask if the user wants to link the File 60 entry to the File \n#64 entry. It is strongly recommended to link the entries so that the\nassociated name fields will be activated allowing easier lookups of the\ntests in the future. \n \nis in File 60, so the HL7 messages can be created and the report can be\nThe last choice is to choose the report format for the lab test that will\nbe accepted for LEDI transmission. This is called the MI/AP Database Code\n(File #64.061). This code must contain the same lab area subscript as \nwell as the words "Rpt Date" in the name field of the Database code \n(ex: MI Gram Stain Rpt Date). \n \nThe test can now be reported electronically via HL7 messaging through \nthe LEDI interface with other labs. \n \n Example of the screens involved: \nsent to the collecting lab. This option must be completed for all tests\n \n \n Select one of the following: \n \n MI Microbiology \n SP Surgical Pathology \n CY Cytopathology \n \nChoose Lab Area Subscript: MI Microbiology \nEnter Laboratory Test Name: GRAM\nthat a lab performs as the "Host Site" in order for the report to be \n STAIN GRAM ST NATIONAL VA LAB CODE: Gram Stain// \n60 = GRAM STAIN \n64 = Gram Stain 87754.0000 \n \n Link the two entries? No// Y (Yes) \n o----LINKED----o \n \n MI/AP Database Code for this test is \n MI Gram Stain Rpt Date [9194] \n \ntransferred to HL7 messages. \nDo you want to keep this mapping? y YES \n \nThe first step of the option is to choose which Lab Subscript area the\ntest is located in. (MI for Microbiology, SP for Surgical Pathology and\nCY for Cytology). \n
\n\n", "", "", "2007-07-17 15:23:00\n", "", "USER,SEVENTEEN\n", "", ""], ["1271", "LA7V 62.47 ERROR CODES", "LAB CODE MAPPING ERROR CODES\n", "", "", "\n=========================================================================\nError #201\n No File #63 field mapping found for OBX-3\n \nStorage location unknown in LAB DATA file (#63). An organism, \nparasite, or susceptibility doesn't have a mapping to or \nstorage location in the LAB DATA file (#63). This is usually \ncaused by an incorrect or missing RELATED ENTRY field (#2.1)\nfor that code in the LAB CODE MAPPING file (#62.47).\n \n---------------------------------\n \n \nError #202\n No filing method for CONCEPT # n found for OBX-3\n \nThe Lab package does not have a routine to process the Concept.\n \n---------------------------------\n \nError #203\n No Coding System found in OBX-5\nError #200\n \nOBX-5 does not have a coding system specified.\n \n---------------------------------\n \nError #204\n Unknown entity in OBX-5\n \nThe organism, parasite, etc. being reported does not have \nan entry in its associated file (ie ETIOLOGY FIELD file (#61.2)).\n No File #62.47 mapping found for OBX-3\n \n---------------------------------\n \nError #205\n Invalid SubId in OBX-4\n \nThe SubId in OBX-4 is either empty or invalid. The processing\nlogic expected a valid SubId here and cannot continue processing.\nAction must be taken by the sender of the HL7 message to correct\nthe invalid SubId.\n \n \n---------------------------------\n \nError #206\n Could not create new entry in file #X (text)\n \nThe system needed to add a new entry "on-the-fly" to\nthe file specified to handle this incoming message but\nfailed to create the new entry. This may be a problem on\nthe sender's or the receiver's side. \nThe code set in OBX-3 was not found in the LAB CODE MAPPING file (#62.47).\n \n--------------------------------\n \n
\n\n", "", "", "2007-02-13 15:12:00\n", "", "USER,SEVENTEEN\n", "", ""], ["1272", "PRSA ENTER TW", "Enter Telework Hours Help\n", "", "", "\nAllowable range for telework hours is calculated, based on the length of\ntour of duty plus any additional work such as overtime and then less any\nposted leave. For example, an 8 hour tour with 2 hours of overtime and one\nhour of annual leave can have up to 9 hours of telework.\n \n 8 hour tour + 2 hrs OT - 1 hr AL = 9 hours of work\n \nAll work outside the tour of duty such as comptime or overtime must be Ad\nHoc/Situational Telework, by definition.\n
\n\n", "", "", "2012-05-03 13:14:53\n", "", "USER,SEVENTEEN\n", "", ""], ["1273", "ECREASON", "Activate/Inactivate Reasons\n", "", "", "\nThe Reasons table contains records with site-defined descriptions \nexplaining why a procedure was performed for the patient. Reasons that are\ninactive will not appear in the list of available reasons during data\nentry. Reasons can be inactivated and re-activated by site managers.\n \nNew reasons can be added and will immediately be available for use in \ndata entry.\n
\n\n", "", "", "2012-11-06 15:47:43\n", "", "USER,SEVENTEEN\n", "", ""], ["1274", "EC SCREEN COPY", "Copy EC Screens to another DSS Unit\n", "", "", "\n** Active (Current) Event Capture Locations must exist before using this \nCapture Management Menu. During data entry, only the procedures defined \nin Event Code Screens can be selected. **\n \nThis option allows the Event Capture System (ECS) manager to copy EC \nScreens from one DSS Unit to another.\n \n1. Select an existing DSS Unit.\n2. Select "Copy all EC Screens to another DSS Unit" from the Edit menu.\n3. Select the target DSS Unit (i.e. the DSS Unit to which the EC Screen \n will be copied).\noption. Update Location information through the Event Capture Management\n4. From the "Copy Event Code Screen" form, select the desired fields:\n Category (optional);\n Location (required);\n Default Associated Clinic (Enabled if the DSS unit is 'Send to \n PCE'. The field is disabled when the DSS Unit is 'Send no \n records' or 'OOS').\n5. When all desired fields are populated, clicking the "OK" button will \n apply all changes, effectively copying the EC Screen to the target DSS \n Unit.\n6. Clicking the "Skip this EC Screen" button will pass over the presently \nMenu. ** \n displayed record and prompt the user with the next EC Screen record.\n7. Clicking the "Close" button will stop processing and close the form.\n \nAdditional EC Screens can be copied by repeating the steps described \nabove.\n \n** DSS Units must exist before using this option. Add or update DSS \nUnits through the Event Capture Management Menu. ** \n \n** Event Code (EC) Screens define procedure information and must exist \nbefore using this option. Add or update EC Screens through the Event \n
\n\n", "", "", "2012-12-07 10:06:03\n", "", "USER,SEVENTEEN\n", "", ""], ["1275", "ECDSSSNR", "Send no records DSS Units report\n", "", "", "\nLists active DSS Units with send to PCE status of Send NO RECORDS. \nIncludes DSS Unit Name and IEN, Associated Stop Code (and Credit Stop\nand/or CHAR4 Code if present).\n
\n\n", "", "", "2015-10-21 16:53:15\n", "", "USER,FIFTYFOUR\n", "", ""], ["1276", "ECDISSUM", "Disabled Category & Procedure Summary Report\n", "", "", "\n** You must have locations, DSS Units, local categories, and procedures \nthose categories, this report displays the EC screens that now have \ndisabled categories.\n \nAll procedures print for each disabled category. \n \nThe print and preview report output includes the headers:\n \n - Run Date \n - Location \n - Service \ndefined before using this option. ** \n - DSS Unit\n - DSS Unit IEN\n - Send Status \n - DSS Dept \n - Procedure Code\n - Procedure Name\n - Synonym\n - Clinic IEN/Clinic Name/Stop Code/Credit Stop/CHAR4 code/MCA Labor Code\n \nThe report also includes, within the text of the report, the disabled \n \ncategory name, the DSS Unit status, and the Event Code Screen status.\n \nThe Excel export report output fields are the same as above along \nwith the CPT code. The exported report does not include the run date.\n** This report can be printed or exported as a reference guide for data \nentry personnel at your facility. **\n \nThis option allows you to print/display ECS categories that have been \ndisabled for one or all DSS Units within a specified location. If your \nDSS Units have categories enabled and have Event Code Screens defined to \n
\n\n", "", "", "2015-11-24 14:33:16\n", "", "USER,FIFTYFOUR\n", "", ""], ["1277", "ECSSCSS", "Patient eligibilities\n", "", "", "\nThis field is one of several related to a patient's eligibility. If the \neligibility is active at the time of the encounter you may enter Y if the \nencounter was related to the eligibility or N if it was not.\n \nEligibilities will be validated when you upload the spreadsheet.\n
\n\n", "", "", "2016-02-09 17:11:46\n", "", "USER,FIFTYFOUR\n", "", ""], ["1278", "ECSSMOD", "CPT Modifiers\n", "", "", "\nThis field is used to enter a modifier to the selected CPT procedure \ncode.\n \nYou may enter up to 5 unique modifier codes for the procedure. Modifiers\nwill be checked for validity during the upload process based on the \nselected CPT procedure code.\n
\n\n", "", "", "2016-02-09 17:21:30\n", "", "USER,FIFTYFOUR\n", "", ""], ["1279", "EC PROVIDER", "Event Capture Non Licensed Provider\n", "", "", "\nThis option allows you to create a list of Non Licensed Providers (those\nwithout a Person Class), so they may enter workload into DSS Units which\ndo not send records to PCE.\n \nBoth Non Licensed Providers, and providers with a Person Class, may be\nselected as providers for workload that does not send to PCE. Medical\ncenter staff without a Person Class may not be selected as a provider when\nthe workload will be sent to PCE.\n
\n\n", "", "", "2016-10-25 12:05:06\n", "", "USER,FIFTYFOUR\n", "", ""], ["128", "XUDOC XQDIC", "THE XQDIC MENU SYSTEM VARIABLE\n", "", "", "\nObsolete help frame.\n
\n\n", "", "", "1992-04-15 12:17:00\n", "", "USER,ONE\n", "", ""], ["1280", "EC DELETE TEST PATIENT DATA", "Delete event capture test patient data\n", "", "", "\nThis option will allow the user to delete existing test patient data from \nThe deletion of records will occur in the background and holders of the \nECMGR key will receive an email message upon completion of the task.\n \nThe user will be given the opportunity to confirm or cancel the request \nbefore the deletion occurs.\n \n*Note: This process will take a while to complete. The amount of time \nwill vary based on total number of records to be reviewed and the total \nnumber of records to be deleted.\nthe EVENT CAPTURE PATIENT file. Any record associated with a test \npatient, as determined by their SSN and/or TEST PATIENT INDICATOR status \nfrom the PATIENT file, will be permanently deleted from event capture.\n \nThe only exception to the deletion is if the test patient has workload in \nthe CH103 to CH109 procedure range. These procedures are allowed to be \nassigned to a test patient and represent valid workload.\n \n
\n\n", "", "", "2016-12-20 13:03:36\n", "", "USER,FIFTYFOUR\n", "", ""], ["1281", "RCDPE PAYER FLAGS GENERAL", "Flag Payers as CHAMPVA/Pharmacy/Tricare\n", "", "", "\nPH - Use this option to flag/un-flag a payer as a Pharmacy payer. The\n \nED - Use this option to edit the CHAMPVA, Pharmacy and Tricare flags on a\n single payer.\n \nFI - Use this option to change the filters on the list, to display only\n entries that match the filter criteria. You may filter the list by\n Date Added and by the status of the CHAMPVA, Pharmacy and Tricare\n flags.\n \nPRE-SELECTION\n selected entries will be toggled, so that un-flagged entries are\n - If you select any of the above options you will be prompted for\n the appropriate information to complete the action. However you\n may save time and keystrokes by preselection of the answers. Type\n the equals sign (=) after the option and specify the answers as\n follows:\n \n ED=Line to Edit\n e.g. ED=10 - Edit Pharmacy and Tricare flags for line 10\n \n CH=List of Lines\n flagged, and flagged entries are un-flagged.\n PH=List of Lines\n TR=List of Lines\n \n List of lines may be specified using the standard format. Use ';'\n to separate individual lines in the list. Use '-' to specify\n a range of lines.\n e.g. CH=10 - toggle CHAMPVA for line 10\n PH=1;4;8 - toggle pharmacy for lines 1, 4 and 8\n TR=3-9 - toggle Tricare for lines 3 through 9\n PH=1;3-9;12 - toggle pharmacy for lines 1, 3 through 9 and 12\n \n \n \n FI=Type;[Start];[End]\n \n Specify the type of filter and optionally the start and end date\n for filter by Date Added.\n e.g. FI=P - Change filter to show lines flagged pharmacy\n FI=A;T-7;T - Change filter to show all records added in the\n last 7 days.\nTR - Use this option to flag/un-flag a payer as a Tricare payer. The\n selected entries will be toggled, as for the PH option.\n \nCV - Use this option to flag/un-flag a payer as a CHAMPVA payer. The\n selected entries will be toggled, as for the PH option.\n
\n\n", "", "", "2017-05-12 08:30:00\n", "", "USER,EIGHTYNINE\n", "", ""], ["1282", "ECLATESH", "Possible Late State Home Entries Report\n", "", "", "\nThis option allows the user to print/display all possible late State Home \n- Procedure Date and Time\n- Entered Date and Time\n- Entered By (export only)\n- Procedure Code\n- Volume\n- Primary Provider\nentries for the selected date range. These are State Home patients that\nwere entered for previous months that could be included in the ECS Extract\nfor the time period you have selected. The output includes:\n \n- DSS Unit\n- Location\n- Patient Name\n- Last four digits of Patient SSN (full SSN on export)\n
\n\n", "", "", "2017-10-03 16:09:04\n", "", "USER,FIFTYFOUR\n", "", ""], ["1283", "EC SEARCH PREVIEW", "Report Preview Search\n", "", "", "\nYou can search for any text in the report. To do so, type the desired \n \nSearch From Start - This will begin the search each time from the start \nof the report. The default value is not checked. If this is not checked, \neach subsequent search will find the next instance of the search text. If \nthere are no further instances of the search text, the search will wrap \nto the beginning of the report.\nsearch text and click on the "Find Next" button. Note that one can also \nhit ALT-N or F3 to search.\n \nThere are two options for searching:\n \nIgnore Case - This will search for the desired text regardless of upper \nor lower case letters. The default value is checked. When this is not \nchecked, it will only find the search text with an exact match.\n
\n\n", "", "", "2019-08-26 13:36:09\n", "", "USER,SIXTYFIVE\n", "", ""], ["1284", "EC SCREEN COPY SINGLE", "Copy Single EC Screen to another DSS Unit\n", "", "", "\n** Active (Current) Event Capture Locations must exist before using this \nCapture Management Menu. During data entry, only the procedures defined \nin Event Code Screens can be selected. **\n \nThis option allows the Event Capture System (ECS) manager to copy a single\nEC Screen to one or more other DSS Units. Inactive Event Code screens\ncannot be copied.\n \n1. Select an existing DSS Unit.\n2. Select "Copy the selected EC Screen to other DSS Unit(s)" from the \n Edit menu. \noption. Update Location information through the Event Capture Management\n3. Select one or more target DSS Units (i.e. the DSS Unit to\n which the EC Screen will be copied).\n4. From the "Copy Event Code Screen" form, select the desired fields:\n Category (optional);\n Location (required);\n Default Associated Clinic (Enabled if the DSS unit is 'Send to \n PCE'. The field is disabled when the DSS Unit is 'Send no \n records' or 'OOS').\n5. When all desired fields are populated, clicking the "OK" button will \n apply all changes, effectively copying the EC Screen to the target DSS \nMenu. ** \n Unit.\n6. Clicking the "Skip this EC Screen" button will pass over the presently \n displayed record and prompt the user with the next DSS Unit target.\n7. Clicking the "Close" button will stop processing and close the form.\n \nAdditional EC Screens can be copied by repeating the steps described \nabove.\n \n** DSS Units must exist before using this option. Add or update DSS \nUnits through the Event Capture Management Menu. ** \n \n** Event Code (EC) Screens define procedure information and must exist \nbefore using this option. Add or update EC Screens through the Event \n
\n\n", "", "", "2020-12-31 10:29:16\n", "", "USER,SEVENTEEN\n", "", ""], ["1285", "ECRPROC", "Procedure Summary Report\n", "", "W @IOF\n", "\nThis report will display the number of patients seen with a specific \nThe output includes:\n- Location\n- DSS Unit\n- Provider \n- Category\n- CPT Code\n- Procedure Code\n- Procedure Name\n- # Patients Seen with Given Procedure by Provider\n- Volume\nProcedure for selected Providers within a given date range for selected \n- Total # Patients Seen with Given Procedure by Provider\n- Total Volume by Provider\n- Grand Total Patients Seen with Given Procedure by DSS Unit\n- Grand Total Volume by DSS Unit\nLocations or all Locations and selected DSS Units or all DSS Units.\nThis report is sorted by Location, DSS Unit and Provider. It will list \nthe total number of patients seen and the total number of procedures \nperformed by the selected provider. The report will also provide the \nGrand Total number of patients seen and the Grand Total number of \nProcedures performed at the bottom of each DSS Unit listing.\n \n
\n\n", "", "", "2021-10-06 12:41:12\n", "\n- \n\n
\n", "USER,EIGHTYSIX\n", "", ""], ["1286", "EC PROBLEM LIST", "Problem List\n", "", "", "\nThe Problem List displays information retrieved from the PROBLEM file \n(#9000011) for the selected patient.\n \nA diagnosis can be added to the list of diagnoses for the patient \nprocedure when:\n - the ICD code is active; and,\n - the value is not already listed.\n
\n\n", "", "", "2022-09-06 15:04:51\n", "", "USER,EIGHTYNINE\n", "", ""], ["1287", "ECREDIT", "Event Capture Edit Log Report\n", "", "", "\nThis report will display the provider and staff name for the specified\n - Last four digits of Patient SSN\n - Procedure Code \n - Procedure Date\n - Provider Name \n - Entered/Edited By Staff Name\n \nIf more than one location is set up the user will be able to select a\nsingle location or all locations.\n \nOne DSS Unit, multiple DSS Units, or all DSS Units can be selected.\nlocation(s) and DSS Unit(s) within a selected date range.\n \nThe report can be sorted by procedure date or by the name of the staff \nmember who added or edited the record.\n \nThis report may be sorted by procedure date or staff name. The output \nincludes:\n \n - Location\n - DSS Unit\n - Patient Name \n
\n\n", "", "", "2022-09-29 13:47:53\n", "", "USER,EIGHTYNINE\n", "", ""], ["1288", "ECCLIPRO", "Procedures by Clinic Report\n", "", "", "\nThis report will display procedures used in the selected clinic for the \n - Patient Name\n - Last four digits of Patient SSN\n - Procedure Date/Time\n - Procedure Code\n - Procedure Name\n - Procedure Volume\n - Provider Name\n \nOne DSS Unit, multiple DSS Units, or all DSS Units can be selected.\nspecified location and DSS Unit(s) within a selected date range.\n \nThis report may be sorted by procedure date or patient name. The output\nincludes:\n \n - Location \n - Clinic\n - DSS Unit\n
\n\n", "", "", "2022-11-02 14:16:10\n", "", "USER,EIGHTYNINE\n", "", ""], ["1289", "ECSSSECDX", "Secondary Diagnosis Code\n", "", "", "\nThis is a secondary diagnosis code. It must exist in the ICD Diagnosis \nfile (#80).\n \nNote: Secondary diagnosis codes are optional. For records NOT sent to PCE \n(including those with DSS set up as 'OOS'), the diagnosis codes will be\nignored.\n
\n\n", "", "", "2022-12-08 13:22:50\n", "", "USER,EIGHTYNINE\n", "", ""], ["129", "XQSRV HELP", "General Help For 'Server'-type Options\n", "", "", "\n A 'server'-type option is an option in the Option File that can\n1. Run routine, and 2. Action options. In the first case, the\nserver can be allowed to run the routine whose name is found\nin the 'Routine' field of that option. In the second case, \nwhen no routine is entered in that field, the menu system will\nexecute the MUMPS code found in the Action and Exit Action\nfields of the Option File for that server option.\n Typically, an application programmer will write a program\nand create a server type option to run that program which will\nbe shipped with an application package. The local IRM staff,\nshould they wish to put a server 'on-line' will fill in the\nreceive Mailman messages that can trigger background jobs. Each\nnecessary fields in the Option file for that server. If a\nserver is on-line a mail message arriving at the site addressed\nto S.(option name) will cause the server to do whatever is\nspecified invarious [fields of the Option File]. Option File.\n \nserver option can be individually tailored and monitored by the\nlocal IRM staff to insure security and efficiency. There are\nseveral fields in the Option File which help accomplish these\nlocal goals. No background jobs will be started by the menu\nsystem unless the local Option File has been specifically set\nup to allow a specific server to do so.\n Servers are analogous to two types of existing option types:\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: FIELDS OF THE OPTION FILE
\n- XQSRV-FIELDS
\n \n
\n
\n", "", "1989-07-11 10:30:00\n", "", "USER,ONE\n", "", ""], ["1290", "EPCSMAIN", "ePCS GUI Online Documentation\n", "", "W @IOF\n", "\nThe ePCS GUI provides the site an option for entering Drug Enforcement \nAdministration (DEA) Controlled Substance schedules for VA Prescribers. \nAccess is granted only to those individuals with the appropriate security \nkey.\n \nInformation pertaining to DEA Numbers records that are added or edited \nwill be saved to an audit file for DEA tracing purposes.\n
\n\n", "", "", "2021-11-04 13:59:49\n", "", "USER,EIGHTYNINE\n", "", ""], ["1291", "EPCSPROV", "ePCS GUI Prescriber Screen\n", "", "", "\nThis screen allows the user to update information pertaining to the \nprescriber, including the Subject Alternative Name (SAN), the \n"Authorized to Write Med Orders?" value, and the Prescriber VA#;\nthese fields are found in the NEW PERSON file (#200).\n \nIn addition, the user can view DEA Numbers assigned to the selected \nprescriber. New DEA Numbers can be assigned; an existing DEA Number \nrecord can be edited or deleted.\n
\n\n", "", "", "2021-11-04 15:01:03\n", "", "USER,EIGHTYNINE\n", "", ""], ["1292", "EPCSADDDEA", "ePCS GUI Add DEA Number\n", "", "", "\nThis screen allows the user to add a DEA Number for the selected \nNumber.\n \nIf an institutional DEA Number is added, a Suffix must be entered; the\nunique Suffix helps the site identify the provider writing Controlled \nSubstance prescriptions using the institutional DEA Number. The \nExpiration Date cannot be changed for institutional DEA Numbers. The \n"Use for Inpatient Orders?" box will be unchecked and disabled. \n \nThe schedules assigned will default to the schedules found on the \nDepartment of Justice (DOJ) server, but can be changed. Checking the "All \nprescriber.\nSchedules" box will check all of the schedules; from there, schedules can \nbe individually unchecked.\n \nIf an individual DEA Number is added, an Expiration Date must be entered. \nIf this is the first individual DEA Number entered for the prescriber, \nthe "Use for Inpatient Orders?" box is checked and cannot be changed. If \nthe prescriber has one or more other DEA Numbers currently on file, \nchecking the "Use for Inpatient Orders?" box will automatically set the \nflag for the new DEA Number and remove the flag from the other DEA \n
\n\n", "", "", "2021-11-04 15:29:57\n", "", "USER,EIGHTYNINE\n", "", ""], ["1293", "EPCSEDITDEA", "ePCS GUI Edit a DEA Number Record\n", "", "", "\nThis screen allows the user to edit a DEA Number for the selected \nNumber. The schedules will be retrieved from the DEA NUMBERS file \n(#8991.9), but can be changed. Checking the "All Schedules" box will \ncheck all of the schedules; from there, schedules can be individually \nunchecked.\n \nIf an institutional DEA Number record is being updated, the existing \nSuffix may be edited; the unique Suffix helps the site identify the \nprovider writing Controlled Substance prescriptions using the \ninstitutional DEA Number. The Expiration Date cannot be changed for \ninstitutional DEA Numbers. The "Use for Inpatient Orders?" check box will\nprescriber.\nbe unchecked and disabled. The schedules will be retrieved from the NEW \nPERSON file (#200), but can be changed. Checking the "All Schedules" box \nwill check all of the schedules; from there, schedules can be \nindividually unchecked.\n \nClicking the "Mirror DOJ Schedules" button will automatically check the \nboxes for the schedules associated with that DEA Number on the Department \nof Justice (DOJ) server.\n \nIf an individual DEA Number record is being updated, the Expiration Date \ncan be changed. If this is the only individual DEA Number on file for the\nprescriber, the "Use for Inpatient Orders?" box is checked and cannot be \nchanged. If the prescriber has more than one individual DEA Number on \nfile, checking the "Use for Inpatient Orders?" box will automatically set\nthe flag for this DEA Number and remove the flag from the other DEA \n
\n\n", "", "", "2021-11-04 15:55:14\n", "", "USER,EIGHTYNINE\n", "", ""], ["1294", "EPCS200", "ePCS GUI Schedules from File 200\n", "", "", "\nThis screen allows the user to edit schedules that are not associated \nwith a DEA Number. The provider has not been assigned any DEA Numbers, \nbut is still authorized to prescribe Controlled Substance medications.\n
\n\n", "", "", "2021-11-04 16:36:50\n", "", "USER,EIGHTYNINE\n", "", ""], ["13", "XQKEYEDIT", "THE 'Enter/Edit Security Key' OPTION\n", "", "", "\nThis option provides only for the entry of security keys and their\ndescription. The description of exisiting keys can be modified\nhere. A user needs to have the proper filemanager security to be able\nto add to the security key file.\n \nHolders are not assigned through this option. Instead use the\n'Allocation of Security Key' option.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["130", "XQSRV-FIELDS", "Setting up a Server Option\n", "", "", "\n \n(#220), 2. [Server Action] (#221), 3. [Server Mail Group] (#222), \n4. [Server Audit] (#223), 5. [Time to Run] (#224), and 6. [Day to Run]\n(#225).\n \n There are several fields in the Option File which have an effect\non server options. Some of these fields are common to other option\ntypes, and some a specific to servers only. Those fields that are\n[common] to other types of options are: 1. Name (.01), 2. Out of Order\nMessage (#2), 3. Type (#4), 4. Priority (#3.8), 5. Exit Action (#15),\n6. Action (#20), and 7. Routine (#25).\n In addition, the local IRM staff have several fields available to \ncontrol the operation of servers. They are: 1. [Server Bulletin]\n
\n\n", "\n- \n\n
\n", "", "1989-07-11 13:35:00\n", "", "USER,ONE\n", "", ""], ["131", "XQSRV-TIME/DAY CONTROL", "Controlling the Day and Time a Server Runs\n", "", "", "\n \navailable time and day that the server can be run and asks\nTaskMan to run the server during that time slot.\n When entering data in the TIMES field the user will be\nprompted for two times in military format between which the\nserver will be prohibited. By entering 0800-1630, for instance,\nthe server will be prohibited from running between 8 AM and\n4:30 PM.\n If no days are entered in the DAYS field then the software\nassumes that the server is prohibited on all days of the week.\nIf days are entered, using the first two letters of the day,\n A server-type option, like any other type of option, may be\nthen the server is prohibited on that day only during the\nspecified times. MO, for instance, will prohibit the server\non Monday during the times entered. You may also enter strings\nof days, such as MO,TU,WE or ranges of days, such as MO-FR.\nprohibited from running by entering the desired data in the\nTIMES/DAYS PROHIBITED field of the Option File. This multiple\nor subfile allows you to specify any range of times and/or days\nduring which a server task will not be scheduled by TaskMan.\n When a server request is recieved from MailMan the server\nsoftware looks at this multiple to see if there are prohibited\ndays or times. If there are, the software finds the next \n
\n\n", "", "", "1990-05-23 11:06:00\n", "", "USER,ONE\n", "", ""], ["132", "XQSRV-SETUP", "Setting up the Option File for a Server\n", "", "", "\n \nsomething in the Out of Order Message field (#2) the server request\nwill be ignored, as with any option. The Prohibited Times field\n(#3.9) may, if the server specific time control fields are left\nblank, effect the time a server option is queued. The Type\nfield (#4) in the Option File must be set to "S" for Server for\na server to be activated. Priority (#3.8) will determine the priority\nat which a server option (and its routine) will run.\n Every server request that runs will first execute the Action\nfield (#20), as with any option. If after executing this field the\nvariable XQUIT exists the server software will issue a bulletin\n There are several fields in the Option File that the server\nand go no further. If there is a routine name in the Routine\nfield (#25) the software will run this routine. The software \nwill, finally, execute the MUMPS code (if any) in the Exit\nAction field (#15). [Errors] are trapped and handled by Menuman.\nsoftware uses in common with other option types to the control\nthe way servers behave when a server request arrives from the\nmail system. There are also other, important fields used\nexclusively for servers which are covered in other, related\nhelp frames.\n The name of an option (.01 field) must be exactly referenced\nin the mail message in order to activate a server. If there is\n
\n\n", "\n- \n\n
\n", "", "1989-07-11 14:35:00\n", "", "USER,ONE\n", "", ""], ["133", "XQSRV-ACTION CODES", "Server Option Action Codes\n", "", "", "\n \n at some other time, which is determined by other fields in\n the Option File.\n \nN - Notify the mail group with a bulletin that a server request\n has been recieved, but don't run anything. The option will\n be queued and then dequeued and the Taskman number will be\n reported so that the server option can be requeued easily.\n \nI - Ignore all requests to this server option. Auditing may\n still take place, however.\n Field #221 'Server Action' in the Option File controls the way\n \na server request is handled by the menu system. These are the\nfour possible codes and what they mean:\n \nR - Run immediately. When the message arrives at the menu system\n run the option. \n \nQ - [Queue] the Option. The server option should be queued to run\n
\n\n", "\n- \n\n
\n", "", "1989-07-11 14:48:00\n", "", "USER,ONE\n", "", ""], ["134", "XQSRV-AUDIT", "Auditing Server Options\n", "", "", "\n \nthe return address of the Sender, the Subject of the message,\nand the Action taken by the menu system on this request.\n The message that is sent to an option to request a server\nmay very well have information stored in it that the server\nroutine will unload from that message. The Action taken by\nthe menu system may simply be "Routine XXX completed normally",\nor it might be an [error message] of some kind.\n A server option will also be audited in like fashion if\nthe server's name-space is being audited by the regular option\nauditing software, or if an audit has been specifically requested\n Server options are auditted in the same way that other option\nfor that option thorugh the regular auditing menus. Even if\n'Server Audit' (Field #223) is marked "N" (no audit) the server\nwill still be audited if it is targeted by the regular audit\nsoftware through the Security Officer's menu.\ntypes are, with a few added features. Field #223 'Server Audit'\nwill insure that each request appears in the Audit Log for Options\nif it is set to "Y". In addition to the regular information that\nis stored about any audited option (Option, User, Device, Job,\nDate/Time of Exit from Option, and CPU) audited servers also\nleave a trail to the requester by recording the Message Number\nof the requesting message in the Message File ^XMB(3.9),\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: ERROR MESSAGE
\n- XQSRV-ERROR
\n \n
\n
\n", "", "1989-07-11 15:05:00\n", "", "USER,ONE\n", "", ""], ["135", "XQSRV-BULLETINS", "Using Bulletins with Servers\n", "", "", "\n \ninformation that the program associated with the server\nhas placed in the array [XQSTXT] while it was running.\n There is also a field called MAIL GROUP for each\nserver-type option. If there is a mail group entered in\nthis field then the server software will send the bulletin\nto the members of this group IN ADDITION TO the members\nof the mail group associated with the bulletin in the \nBulletin File.\n The server software makes sure that there is a current\nuser (at least one) in the mail group(s) associated with\n Associated with ever server is at least one bulletin. If\nthe server option. If there is not, a warning message is\nsent to the Postmaster of that domain, the server \nrequest is aborted and the request is automatically audited.\nnothing is entered in the BULLETIN field for a particular\nserver-type option then the default bulletin XQSERVER is \nassummed. The bulletin is used to notify a site that a \nserver request has been recieved from the mail system, \nwhat action was taken on that request (depending upon the\n[action code] specified for that server), errors that might\nhave occurred during execution of that server, and any\n
\n\n", "\n- \n\n
\n", "", "1990-05-23 11:34:00\n", "", "USER,ONE\n", "", ""], ["136", "XQSRV-MAIL", "Local and Network Server Mail\n", "", "", "\n \nbe sent for this request. The possible codes in this field include:\n"N" for no, don't send any reply; "R" for reply in all cases; and \n"E" for reply only in the case of an error.\n If a reply is to be sent the software composes a mail message and\ncalls MailMan to send it to the person who originated the server \nrequest. This may be a local message, or a network mail message.4\n The programmer who writes a program to be run by a server-type\noption may include information in the bulletins or reply messages\nby loading that information into the local array XQSTXT. This\narray will automatically be appended to the end of the reply message\n Servers are heavily dependant upon the Mail System. The server\nand/or bulletin after the program has been run.\noption is awakened by a mail message (called a "server request"),\nand once awakened it uses the mail to notify the local site of the\nrequest and it's disposition using [bulletins]. The server can also\nsend a message in reply if requested to do so by the Site Manager.\n When a server request is recieved the server software captures\nthe name and return address of the sender. It then checks a set of\ncodes in the REPLY field of the Option File to see if a reply is to\n
\n\n", "\n- \n\n
\n", "", "1990-05-23 13:42:00\n", "", "USER,ONE\n", "", ""], ["137", "XQSRV-ERROR", "Error Handling\n", "", "", "\n \nby the server.\n When a server error occurs, such as a request for an option that\nis not of the type "server" the software will likewise report it\nin the bulletin or return mail message. In both these cases the\nerror will also be logged by the audit software into the OPTIONS\nAUDIT LOG file. System and server errors will cause the server to abort.\n When the application program run by the server option sees an\nerror that needs to be reported it is the job of that program to\nhandle the error. One way to do this is to enter text into the\narray XQSTXT, using as many of the array nodes as desired (e.g.\n There are 3 types of errors which a server may encounter when\nXQSTXT(1), XQSTXT(2), etc.) which will automatically be appended\nto the end of the bulletin or return mail message associated\nwith that server.\ntrying to run: system errors, reported by the operating system;\nserver errors, reported by the server software; and application\nerrors, detected by the program associated with the server-type\noption.\n When a system error occurs, such as an undefined variable\n(<UNDEF>) the server software will trap that error and report\nit to the user in the bulletin or return mail message triggered\n
\n\n", "", "", "1990-05-23 11:19:00\n", "", "USER,ONE\n", "", ""], ["138", "XUSER COMPUTER ACCOUNT", "Batch user access document\n", "", "", "\n|INDENT(10)| |WIDTH(70)|\n|#20.2|\n|#29| (|#29:MAIL SYMBOL|)\n|XUVT(19)|\n---\n |WRAP|\n \n \nA user account has been created in your name to enable you to access\non-line clinical and/or administrative data required to perform your\nduties as an employee of the Department of Veterans Affairs. Please read\n|NOWRAP|\nthe enclosed NEW USER INFORMATION before you attempt your first log-on to\nthe system. Questions about access should be referred to the AIS\nApplication Coordinator in your service, your facility Information\nSecurity Officer (ISO), or your IRM Service.\n \n |NOWRAP|\nYour Computer Access Coordinator is:\n|TAB(36)||#29:COORDINATOR|\n|TAB(36)||#29:COORDINATOR:ROOM|\n|TAB(36)||#29:COORDINATOR:OFFICE PHONE|\n|CENTER("USER ACCOUNT NOTIFICATION")|\nYour Facility Information Security Officer:\n|TAB(36)|\nYour Alternate Information Security Officer:\n|TAB(36)|\n|XUVT(41)|\n---\n|XUVT(49)|\n|TAB(45)|Access Code: |VAR("XUU")|\n|TAB(45)|Verify Code: |VAR("XUU2")|\n|TOP|\n \n|INDENT(5)||WIDTH(75)||NOWRAP|\n|CENTER("COMPUTER ACCOUNT ACCESS POLICY")|\n \n|CENTER("Department of Veterans Affairs")|\n|CENTER("Your VA Facility")|\n|XUVT(6)|\n|#20.2|\n|#29| (|#29:MAIL SYMBOL|)\n|INDENT(1)||WIDTH(77)||WRAP|\n \n|CENTER("Department of Veterans Affairs")|\nAs an authorized user of VHA automated information systems (AISs) and\nhaving access to data stored in them, I will be given sufficient access to\nperform my assigned duties. I will use this access ONLY for its intended\npurpose and understand the following policies that apply to VA data and\ncomputer systems:\n \nI agree to safeguard all passwords (e.g., Access/Verify codes, electronic\nsignature codes) assigned to me and am strictly prohibited from disclosing these\ncodes to anyone including family, friends, fellow workers, supervisor(s), and\nsubordinates for ANY reason.\n|CENTER("SuperStar VAMC")|\n \nI understand that I may be held accountable for all entries/changes made\nto any government AIS using my passwords.\n \nI am aware of the regulations and facility AIS security policies designed\nto ensure the confidentiality of all sensitive information. I am aware\nthat information about patients or employees is confidential and\nprotected from unauthorized disclosure by law. I understand that my\nobligation to protect VA information does not end with either the\ntermination of my access to this facility's systems or with the\n|CENTER("123 anywhere")|\ntermination of my government employment.\n \nI will exercise common sense and good judgment in the use of electronic\nmail. I understand that electronic mail is not inherently confidential\nand I have no expectation of privacy in using it. I understand that\ntechnical or administrative problems may create situations which requires\nviewing of my messages. I also understand that facility management\nofficials may authorize access to my electronic mail messages whenever\nthere is a legitimate purpose for such access.\n \n|CENTER("anytown, state, zip")|\nI understand that a violation of this notice constitutes disregard of a\nlocal and/or VHA policy and will result in appropriate disciplinary action\nas defined in VA employee conduct Regulations (VAR 820(b)) as well as\nsuspension/termination of access privileges.\n \nI affirm with my signature that I have read, understand, and agree to\nfulfill the provisions of this User Access notice.\n \n|INDENT(5)||WIDTH(75)||NOWRAP|\nSignature:________________________\n|XUVT(12)|\n |#20.2| |#29|\nRETURN THIS FORM TO: IRMS - NEW ACCTS (xxx/xxx)\n\n\n", "", "", "1989-10-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["139", "XUDOC SERVERS", "SERVERS\n", "", "", "\n OVERVIEW\ncode (found in field #20 of the Option file), run the routine\n o TYPE (#4) - This field must always contain the code "s" for\n Server or the request will be denied and an error will\n result. \n \n o ENTRY ACTION (#20) - The MUMPS code that is entered in this\n field will be executed if the server request is honored.\n If, as with other options, the variable XQUIT exists\n after the Entry Action is executed, the request will\n be terminated at that point and an error will be \n generated.\nindicated in the Routine field (#25), and execute any MUMPS code in the \n \n o ROUTINE (#25) - If there is a routine name in this field in \n the forms PROGRAM, ^PROGRAM, or ENTRY^PROGRAM the \n routine will be run.\n \n o EXIT ACTION (#15) - The MUMPS code stored in this field will\n be executed just before the server exits.\n \n o SERVER BULLETIN (#220) - This field is a pointer to the \n to the Bulletin file which indicates the bulletin that\nExit Action field (#15). A server-type option is similar to a run routine-\n is to be used to notify the local mail group of a\n server request on their system. If there is no bulletin\n entered in this field the default bulletin XQSERVER will\n be used. If the mail group(s) pointed to by XQSERVER\n (or the bulletin pointed to in this field) do not\n contain an active user (i.e., a user possessing a verify code\n and no effective termination date) the software will\n turn on auditing (see below) and send a MailMan message\n to the local Postmaster.\n \ntype option. The difference is that a server option is activated by a mail\n o SERVER ACTION (#221) - This 'set of codes' field allows the local\n IRM staff to decide how a server request is to be treated. The action \n codes are:\n \n R - Run immediately. This will cause the server request to be\n honored in real time as soon as it is received from MailMan\n provided that it is not prevented by a setting in the Times/\n Days Prohibited field.\n \n Q - Queue server. This will cause the server request to be honored\nmessage while a run routine option is activated by a user when being chosen\n as soon as permitted by the Times/Days Prohibited field.\n \n N - Notify local authorities. This will cause the server software\n to create a TaskMan entry which is not scheduled to run, and\n notify the local mail group with the task number so that it may\n be approved locally and then scheduled to run using TaskMan's\n Requeue Tasks option.\n \n I - Ignore any requests. This code will cause the software to ignore\n all requests for this server. A bulletin or MilMan message may\nfrom a menu. The form of the mail message that activates the server may be\n still be sent, however.\n \n o SERVER MAIL GROUP (#222) - This field is a pointer to \n another mail group (the first is pointed to by\n XQSERVER and/or the bulletin in field #220) to\n which server notifications are to be sent. The\n software will notify all legitimate users in all\n mail groups pointed to.\n \n o SERVER AUDIT (#223) - This field will cause the server\nidentical to any other mail message except that it is adressed to S.<option \n request to be audited in File 19.081 (Audit Log\n for Options). The default is 'YES'. The information\n stored for an audited server includes: Option,\n User (always Postmaster), Device, Job #, Date/Time,\n CPU, message number, return address of sender,\n subject of the message, and error message. A\n server can also be audited using the normal option\n auditing software. Auditing the Postmaster or\n the namespace "XQSRV" will capture all server\n requests.\nname>. The "S." (like the "G." form for sending to mail groups) routes \n \n o SUPRESS BULLETIN (#224) - This field of codes will, if set\n to "Y" (YES) prevent a bulletin from being sent\n under normal conditions. If there is an error\n or a possible security breach, a bulletin will\n still be fired. If the field is not filled in\n it takes the default of "N", the sending of\n bulletins is not supressed.\n \n o SERVER REPLY (#225) - This set of codes controls the\nthe message to the server request software.\n MailMan reply to a server request. If a reply is requested\n the software uses the return address of the sender as\n supplied by MailMan to send a local or network reply (see\n the standard form below). The possible codes are:\n N - No reply is sent (the default).\n E - A reply is sent to the return address of the sender only in \n the event of an error.\n R - A reply is always sent. \n \n \n \n\n CUSTOMIZING A SERVER BULLETIN OR MAILMAN REPLY\n ==============================================\n \nServers use bulletins and MailMan messages to communicate with the\nlocal IRM staff when a server request is received, or with the sender of a\nserver request, usually in the event of an error. These two kinds of \ndocuments look very similar and must contain certain key pieces of data. \nIt is also possible, however, for the sender or the local IRM staff to \nappend other information to the bulletin or MailMan message by setting that \n ========\nCan server requests be denied?\ninformation into the array XQSTXT, one line per node. In other words, if\nthis array exists, for example:\n \n|TAB|XQSTXT(1)="Please append these two lines of text"\n|TAB|XQSTXT(47)="to the end of the bulletin XQSERVER."\n \nThe information in the array will be appended to the bulletin and/or \nMailman reply message. In the case of bulletins, the subscripts of the\narray XQSTXT must be integers greater than zero, for the reply mail any\nsubscripts will be appended. In this example, the default bulletin,\n------------------------------\nXQSERVER, would then look like this:\n \n Subj: Server request notice\n From: <Postmaster>\n ----------------------------------------------------- \n \n Dec. 21, 1989 3:08 PM \n \n A request for execution of a server option was received.\n \nOnly server-type options can be activated by mail messages. They \n Sender: <Child,Your@HOME.DOMAIN.EXT>\n Option name: ZZUPDATECL\n Subject: UPDATE CHRISTMAS LIST DATA BASE\n Message #: 136771\n \n Menu system Action: No error(s) detected by the menu system.\n \n Please append these two lines of text\n to the end of the bulletin XQSERVER.\n \nmust be given the type "s" in the Type field (#4) of the Option file. If \n\n Select MESSAGE Action: IGNORE (in IN basket)//\n \n\n Please note that the first 6 data elements will always be 1) date and \ntime the request was received, 2) the sender, 3) requested option's name, \n4) subject of the message requesting a server, 5) the message number, and \n6) a brief statement of the menu system's action or an error message. If\na customized bulletin is used instead of XQSERVER these data elements will \nstill be printed first.\nthe type is not "s" and a request is received it results in an error which,\nby default, is recorded in the Audit Log For Options file. The option name \nmust be complete and exact when a server request is made or the request\nwill be denied. \n \nWhat can servers do?\n \n--------------------\nSeveral other things can happen when a server request is received,\ndepending upon how the fields in the Option file for that server option\nare filled in. A server request might trigger a bulletin, send a MailMan\nreply, and/or initiate an audit of itself. The programmer or local IRM \nstaff may also customize the bulletins or MailMan replies.\n \nWhat variables monitor server activity?\n---------------------------------------\nServer options are linked to messages in the Message file, stored in\nWhat is a Server?\n^XMB(3.9). These messages may have data in them for the program which is \nactivated by the server. Along with the data, the server supplies an \n'unloader' variable XMREC which, when executed, returns the next line of \ndata from the message in the variable XMRG. The return code variable, \nXMER, which will equal 0 for a successful read, and -1 when the end of the \nmessage has been reached.\n \n \n SETTING UP A SERVER-TYPE OPTION\n ===============================\n-----------------\n \nA server-type option (henceforth called simply a server) has many\nfields in common with other option types, and is set up using the Menu\nManagement option called 'Edit options'. This option calls the FileMan\nedit template XUEDITOPT which will prompt for data to be entered in \nthe following fields:\n \n o NAME (Field # .01) - This should be a namespaced set of 3 to 30\n uppercase letters.\n \nA server is a special type of option, found in the Option file, to\n o MENU TEXT (#1) - Since there is never a menu prompt for a server\n this field should instead contain an accurate description of\n what this server does, as it is used by the server software\n in error messages, bulletins, and MailMan replies.\n It should be be 3 to 50 characters in length. \n \n o OUT OF ORDER MESSAGE (#2) - If this field contains between 1 and\n 80 characters of text, the server is placed 'out of order'\n and will not be activated by a server request. The message\n itself will be included in bulletins or MailMan replies\nwhich mail messages can be addressed. Addressing a mail message to\n which report the failure.\n \n o LOCK (#3) - Since servers have no on-line user associated with \n them, the existence of a lock in this field will prevent\n the execution of a server, much like an out of order \n message. The 'user' for all servers is the Postmaster.\n The originator of a server request is recorded, however,\n in the return address variable. \n \n o DESCRIPTION (#3.5) - This word processing field should contain\na server is termed a 'server request', a request that will awaken the \n an extensive description of the server intended for the\n local Site Manager and IRM staff. The description should\n include an exact description of what the server does and\n the resources it requires.\n \n o PRIORITY (#3.8) - This field will determine the priority at \n which the server runs.\n \n o TIMES/DAYS PROHIBITED (#3.91) - This multiple allows the local\n IRM staff to control the days and times during which the\noption given certain conditions and cause it to execute any Entry Action \n server request is honored. If data is entered which\n prevents the server from being honored immediately the \n software will determine the next available time slice\n which is not prohibited and queue the request for that\n time. Servers which are marked 'R' for Run Immediately\n in the 'Server Action' field will instead be queued to\n run at the next non-prohibited time period. If there\n is no time period when the server is not prohibited, an\n error results.\n \n
\n\n", "", "", "1990-01-18 14:10:00\n", "", "USER,ONE\n", "", ""], ["14", "XQMENUMAN", "USING MENU MANAGEMENT\n", "", "", "\nMenu Management is the system by which options can be linked together\n \n[LOCKS] can be applied to any option, to prohibit access to individual users.\nThere are also several other ways of [RESTRICTING] access to the system.\n \n[HELP FRAMES] can be accessed with the option name prefaced by a '?'.\nThese frames provide extended information on how to use options.\n \nMenu Management provides ways of [SETTING UP] the tree structures, assigning\nkeys to users, restricting access to options, providing help text for\noptions, [INQUIRING] to the options, [CROSS-REFERENCING] the options, and\nand made accessible to users. A hierarchical structure is set up which\n[DIAGRAMING] menus.\nallows the user to gain access to different functions in the system by\nprogressing thru a tree.\n \nEvery user has a [PRIMARY MENU] option. This is the top level in the tree.\nUsers may also have one or more [SECONDARY MENU] options. These are options\nspecifically assigned to an individual user which can be accessed at any time.\nThe [XUCOMMAND] menu is accessible to all users at any time.\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: PRIMARY MENU
\n- XQPRIMENU
\n \n- \n
- RELATED FRAME KEYWORD: INQUIRING
\n- XQINQUIRE
\n \n- \n
- RELATED FRAME KEYWORD: LOCKS
\n- XQLOCKS
\n \n- \n
- RELATED FRAME KEYWORD: RESTRICTING
\n- XQRESTRICT
\n \n- \n
- RELATED FRAME KEYWORD: SECONDARY MENU
\n- XQSECMENU
\n \n- \n
- RELATED FRAME KEYWORD: XUCOMMAND
\n- XQ-USER-AUTOMATIC
\n \n- \n
- RELATED FRAME KEYWORD: HELP FRAMES
\n- XQHELP
\n \n- \n
- RELATED FRAME KEYWORD: CROSS-REFERENCING
\n- XQXREF
\n \n- \n
- RELATED FRAME KEYWORD: DIAGRAMING
\n- XQDIAGRAM
\n \n- \n
- RELATED FRAME KEYWORD: SETTING UP
\n- XQEDIT
\n \n
\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["140", "XQTCREATE", "Creating a Menu Template\n", "", "", "\n A menu template is a set of menu options that can be called at\nNo jumping is allowed during the creation of a template because how\nyou got there may be as important as the target option. All templates\nbegin execution with your primary (sign-on) menu.\n \n At the "Select...Option" prompt you may respond by typing:\n \n 1. An option from the menu presented to include that\n option in the template you are creating,\n 2. '?' to get a brief help message,\n 3. '??' to see your primary, secondary, and common options,\nany menu prompt. This list of options will be executed from the top\n 4. '+' to store the template in your Person file, or\n 5. '^' to abandon the creation process and return to \n the regular menu system.\nof the list to the bottom and then the user will be asked if he/she\nwants to execute that set of options again. Each menu template is\nstored in the person file with a unique name associated with it. A\nmenu template is envoked by typing a [left, square bracket] followed by \nthe template name.\n To create a menu template you will be led step-by-step through\nyour menu trees, selecting an option from each menu presented.\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: LEFT, SQUARE BRACKET
\n- XQTRUN
\n \n
\n
\n", "", "1998-08-17 10:12:00\n", "", "USER,ONE\n", "", ""], ["141", "XQTRUN", "Invoking a Menu Template\n", "", "", "\n Menu templates are activated by typing a left, square bracket\n<RETURN> (since "Y" is the default) the template will be executed again.\nIf you answer "N" you will be returned to your regular menus at the point\nwhere you invoked the template.\nfollowed by the name you have assigned to the template. For example,\nto invoke a menu template called CHECK, you would enter [[CHECK.\n \n Select Menu option: [[CHECK\n ------\n \n After the list of options in the template has been run, you will see\nthe prompt: "Run CHECK Again? {Y/N} Y/" and if you answer "Y" or simply\n\n\n", "", "", "1992-04-15 11:11:00\n", "", "USER,ONE\n", "", ""], ["142", "XQTNAM", "Naming a Menu Template\n", "", "", "\n \n To name your new Menu Template simply choose a short name (6 characters or\nless) that you will remember. If you forget the name you can list your\ntemplates and it will show you all that you have. A template name may not\ninclude the characters "^" or "?". It must be composed of alphbetic and/or\nnumeric characters, A to Z and 0 to 9.\n A Menu Template might be named "MAIL", for instance, if it navigates to the\nMailMan options. Or "REG" if it registers a patient. It can be almost\nanything that you choose.\n
\n\n", "", "", "1991-01-10 14:37:00\n", "", "USER,ONE\n", "", ""], ["143", "XQTREPEAT", "Repeating a Template\n", "", "", "\n \nyou answer 'No' to this question then the template will run once and drop you\nback into your regular menu system.\n When you create a new menu template you are asked if you want to repeat the\ntemplate over and over when it is envoked. If you answer 'Yes' to the\nquestion:\n \n After you have finished using 'TEMPLAT' will you want it to repeat? N//\n \nyou will see the prompt 'Again Y//' when you finish running the template. This\nfeature is designed for users who repeat the same functions over and over. If\n
\n\n", "", "", "1991-01-15 11:59:00\n", "", "USER,ONE\n", "", ""], ["144", "XQNAMSPAC", "Naming Options (and Other Things) Correctly\n", "", "", "\n \nwith one of these.\n You personally may have been assigned a name space by your IRM staff if\nyou are part of the Menu Delegation System, in which case, you should use\nthat. If you have not been allowed to copy an option because you have no name\nspace, talk to your IRM Service.\n Finally, the name space 'ZZ' is reserved for general field use, but it\nis not as safe as being more specific with a site or personal name space\nbecause anybody can use 'ZZ', and we all do.\n It is very important to name things like options, templates, help\nframes, etc. properly to avoid them being clobbered by new packages. The way\nwe do this is by "name spacing" things. All lab things start with the letters\n'LR', for instance, and no one else is allowed to give names beginning with\nthose two letters.\n Local names should begin with the letters assigned to your facility by\nCentral Office. The American Lake VAMC, for instance, has been assigned the\nname spaces 'ACA', 'ACB', and 'ACC; so all options created there should begin\n
\n\n", "", "", "1991-03-29 07:18:00\n", "", "USER,ONE\n", "", ""], ["145", "XUHFSPARAM-DTM", "HFS I/O OPERATION-DTM\n", "", "", "\n READ -- Only allows you to read from the specified file.\n Writing to the file will not be allowed. Therefore,\n you will not be able to direct reports to the file.\n \n WRITE -- Allows you to direct your reports(output)\n to the specified file.\n \n APPEND -- Data from a write operation will be appended to the file.\n
\n\n", "", "", "1995-04-10 13:20:58\n", "", "USER,ONE\n", "", ""], ["146", "XQOO", "Out of Order Manager\n", "", "", "\n \n or - with any of the above to remove items already selected,\n or ^ to quit and exit the program,\n or ^PR to switch from working with options to protocols,\n or ^OP to switch from working with protocols to options,\n or ? to see a brief help prompt,\n or ?? to see this help screen again,\n or ??? to see the list of items chosen so far,\n or ???? to see the Option or Protocol File,\n You are building a list of options and/or protocols to be marked 'Out\nOf Order'. You may enter them in several different ways:\n \n You may simply enter an option or protocol name,\n or NAM* to specify all that begin with the characters 'NAM'\n or NAM1-NAM2 to specify all the options or protocols that fall\n alphabetically between NAM1 and NAM2 inclusive,\n or * to select all options or protocols,\n
\n\n", "", "", "1995-05-18 11:11:00\n", "", "USER,ONE\n", "", ""], ["147", "XQOO-NAME", "Naming An Option/Protocol Set\n", "", "", "\n We are about to build a set or collection of options and/or\nthat exsisting set.\nprotocols. The name that you are being prompted for will be the name of\nthis collection or set. It should be from 1 to 8 characters in length.\nHereafter the software will recognize the set by this name. Since you may\nhave more than one set at any given time, the unique name will distinguish\nbetween multiple sets.\n If you choose a name for which a set already exsists, you will be\nnotified of that and asked if you want to continue building that option\nset. If you chooses to do so, you may then add or subtract options from\n
\n\n", "", "", "1994-04-26 10:43:00\n", "", "USER,ONE\n", "", ""], ["148", "XQOO-KIDSNAME", "Naming Option/Protocol Sets for KIDS\n", "", "", "\n You are creating one or more sets of options and/or protocols that\nmultiple packages you may create one option/protocol set that will disable\nall the options for the entire installation, or you can create multiple\noption/protocol sets that will disable only those options and protocols\nconnected to one of the packages at a time. KIDS will disable the options\nin one set, install that package, and then reenable that option set, and\nso on, for each package being installled.\ncan be marked "Out Of Order" so that they will be disabled during a\npackage installation. You are being prompted for the name of this set of\noptions and protocols. This unique name should be from 1 to 8 characters\nin length. Since you may have more than one set of options defined, this\nname will distinguish among them.\n \n The Kernel Installation and Distribution System (KIDS) will allow you\nto install multiple packages at the same time. If you are installing\n
\n\n", "", "", "1994-04-26 11:04:00\n", "", "USER,ONE\n", "", ""], ["149", "XQOO-MESS", "The Out Of Order Message\n", "", "", "\n You are being asked to enter and "Out Of Order Message". This\n The Marketing Computer Will be Down Until 6PM\n \n Buzz Off, Hard Rock, This System Is Down!!\nstring of text will be used to disable the options and/or protocols that\nyou will begin selecting next. Each time an end user tries to envoke an\noption or protocol that has been disabled this message will be printed on\nhis or her screen. The message should be from 1 to 50 characters, and\nshould obviously have some meaning. A few examples might be:\n \n Lab installation in progress, try later.\n \n
\n\n", "", "", "1994-04-26 11:13:00\n", "", "USER,ONE\n", "", ""], ["15", "XQEDIT", "USING THE 'Edit the Option File' OPTION\n", "", "", "\nThis is the main option in Menu Management. It is used to create and edit\n '???' response.\n \n[HELP FRAME]- the name of a help frame which will provide extended text\n describing this option\n \nType - a single letter indicating whether this option is an\n intermediate <M>enu option, or one of several bottom level\n type options.\noptions, the building blocks of the menu system. Options have the following\nattributes:\n \nNAME - a short internal name prefixed with the package namespace\n \nMENU TEXT - an external name which appears to the user\n \nDESCRIPTION - a brief text which will be displayed to the user with a \n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: HELP FRAME
\n- XQHELP
\n \n
\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["16", "XQINQUIRE", "USING THE 'Inquire to the Option File' OPTION\n", "", "", "", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["165", "XMHELP-MANUAL", "THE ONLINE MAILMAN USER MANUAL\n", "", "", "\n\n To start reading, enter [MORE]...\n\n\n\n\n\n\n\n\n\n January 1999\n\n Department of Veterans Affairs\n\n\n\n\n\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: MORE
\n- XMHELP
\n \n
\n
\n", "", "1999-01-21 07:18:00\n", "", "USER,ONE\n", "", ""], ["17", "XQRESTRICT-TIMES", "RESPONDING TO THE 'PROHIBITED TIMES' PROMPT\n", "", "", "\n An option which has a 'PROHIBITED TIME' can not be accessed during the\n If an option has a prohibited time, it will appear as such when \ndisplayed in the menu system with '??'.\n \n Responding to this prompt with an '@' will delete any PROHIBITED\nTIME currently specified for any of the options chosen, leaving the\nfield null so that there are no prohibited times for those options.\n \nhours specified. It is often useful to restrict access to print and\nsearch type options to hours when the system is not very busy.\n \n Specify a 'prohibited time' using military format, for example:\n \n 0900-1600 (to prohibit access from 9AM-4PM)\n 1800-0600 (to prohibit access overnight 6PM-6AM)\n \n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["18", "XQRESTRICT-OOO", "RESPONDING TO THE 'OUT OF ORDER' PROMPT\n", "", "", "\n To temporarily disable an option, the 'OUT OF ORDER' field should\n \n Entering an '@' in response to this prompt will delete the OUT\nOF ORDER message for the options selected leaving the field null,\nwhich removes the OUT OF ORDER restriction for these options.\n \nhave a message indicating the inavailability of the option. This is\npreferable to removing the option from its menu if it is a temporary\ncondition.\n \n When there is a message in the 'OUT OF ORDER' field, the text\n'NOT AVAILABLE' will appear next to the option when displayed by the menu\nsystem. If that option is selected by the user, then the 'OUT OF ORDER'\nmessage will be displayed.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["189", "XM-MASTER", "VA ELECTRONIC MAIL SYSTEM\n", "", "", "\n \nremote systems. The latest version of MailMan has several [NEW FEATURES]\nfor site management. [PACKMAN] may be used to load data, software, and\npackages into messages. Communications with remote systems may be\nperformed using [TALKMAN].\n\n[USING] MailMan is no chore. Message actions allow users great flexibility\nin managing personal mail. Users can address mail to individuals and groups\nat local and remote sites, with the tedium of waiting for process completion\nbeing reduced by the system's background filer. In addition, the system has\nextensive online documentation, which may be reproduced in manual form.\nMailMan, The Veterans Administration Electronic Mail System, is a\ncommunications tool which is locally useful due to its teleconferencing\nvia chained responses. MailMan (along with HL7) is the transport vehicle\nfor all VA M applications. MailMan is also used to preserve updated copies\nof software and data.\n \n[MAILMAN SITE PARAMETERS] allow site managers to tailor MailMan to your\nsite. [NETWORK] features allow users and packages to send messages to\n
\n\n", "\n- \n\n
\n", "", "2002-05-09 09:38:00\n", "", "USER,ONE\n", "", ""], ["19", "XQRESTRICT-PRIORITY", "RESPONDING TO THE 'PRIORITY' PROMPT\n", "", "", "\n \noptions help conserve machine resources for options with high\nprioity, but they tend to run very slowly on heavily loaded machines.\n \n Entering an '@' at this prompt will delete whatever priority\nis currently entered in this field and cause the options chosen to\nrevert to the system default priority.\n \n This restriction modifies the priority at which an option will be\nrun. The priority should be a number between 1 and 10, with 1 being\nthe lowest priority and 10 being the highest. \n \n An option with a priority of 10 will compete with other high-\npriority options for machine resources, while an option with a\npriority of 1 will run only after all of the other options with\nhigher priorities have been satisfied by the CPU. Low priority\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["2", "XQKEYALLOCATE-KEY", "RESPONDING TO THE 'Allocate/De-Allocate security key' PROMPT\n", "", "", "\n \n^ - To exit this option.\n \n?? - To see the list of keys you've already specified.\n \n??? - To see the list of keys from which you may choose, the current \n holders of a key, the User File, or the members of a mail\n group.\n \n-KEY - To take a key off the list specified preceed it with a minus sign.\nYou can specify the keys you wish to allocate or de-allocate. You can \nspecify a single key, or a set of keys.\n \nRespond with the name of the key(s), one at a time. You may assign only\npre-existing keys which you already hold.\n \nYou may also respond with one of the following:\n \n
\n\n", "", "", "1989-03-08 08:08:00\n", "", "USER,ONE\n", "", ""], ["20", "XQRESTRICT-LOCK", "RESPONDING TO THE 'LOCK' PROMPT\n", "", "", "\n An option which is locked can only be accessed by users who possess\nlocks currently associated with the options chosen, leaving the\nfield null, or unlocked.\n \n In order to specify a new lock for an option or set of options\nyou must first create a key in the KEY FILE, if one does not already\nexist, which matches exactly what you are trying to enter in this\nfield.\n \nthat key. Locks are useful in restricting access to certain options\nto whole groups of users.\n \n If an option has a lock, it will be displayed as such by the menu\nsystem, whether or not the user possesses the key. However, it is only\nselectable with the key.\n \n By responding to this prompt with an '@' you will delete any\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["21", "XQPRIMENU", "THE PRIMARY MENU OPTION\n", "", "", "", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["22", "XQLOCKS", "SECURITY KEYS\n", "", "", "\nSecurity keys can be used to restrict access to options in the menu system.\n \nA lock appears as a field in the option file. It can be assigned thru\nthe [RESTRICT] availability option.\nAn option which is locked is not available to users who don't have the key.\nKeys are also used within application software packages to control access.\n \nSecurity keys are stored in the Security key file. They are namespaced by\npackage. You can create and provide descriptions for keys with the\n[ENTER/EDIT] option. You can also [ALLOCATE] and deallocate keys with\nother options. The person allocating a key as well as the date allocated\nare automatically assigned by the system.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["23", "XQSECMENU", "PERSONAL COMMAND SPACE\n", "", "", "\nThe personal command space (also referred to as 'secondary menu options'\nuseful in attaching an option which is otherwise not part of a user's\ntree without building an entirely new menu.\nallows for individual users to have their own XUCOMMAND.\n \nThe site manager can make entries to the SECONDARY MENU OPTION field in\nthe user file to give a user access to one or more options at all times.\nIt is the responsibility of the site manager to ascertain that each\noption assigned does not require a predecessor to set up variables.\n \nKeeping in mind the ^JUMP feature, the personal command space is most\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["237", "XMHELP", "USING MAILMAN\n", "", "", "\n \nit to others, or replying to it. Replies generate new messages seen by all\nrecipients, creating an ongoing dialog among the recipients. \n \nUsers can [FILTER] their mail and [SEARCH] for specific messages. Also, users\ncan designate [SURROGATES] to manage mail for them. Users can 'introduce'\nthemselves, provide contact information, and create a banner to be\ndisplayed when a message is sent to them. Users can also choose a message\n[READER] and further [CUSTOMIZE] the MailMan interface to suit their\nneeds. [GROUPS] of users may also be created.\n \nMailMan is a general purpose electronic messaging (e-mail) system. Messages\nThere are some [NEW FEATURES] for MailMan users. Some commonly asked\n[QUESTIONS] and answers on MailMan may be useful in solving typical problems. \ncan be exchanged over communication lines, modems, and other networks. A\nmessage is created with the [SEND] option. The message then appears in\neach recipient's mailbox, to be [READ] after signon. Messages are tracked\nelectronically, so that each message's author and readers are identified.\n \nAfter reading a message, a recipient can select from a variety of message\n[ACTIONS], such as saving it into other mail baskets, deleting it, forwarding\n
\n\n", "\n- \n\n
\n", "", "1999-02-01 13:46:00\n", "", "USER,ONE\n", "", ""], ["24", "XQ-USER-AUTOMATIC", "THE COMMON OPTIONS\n", "", "", "\nThe COMMON menu is a list of options which are available to all\n [EDIT] USER CHARACTERISTICS USER HELP\n [HALT] TIME\n RESTART SESSION\n MAILMAN\n \nIn addition there may be options assigned to individual users which appear\nas part of the COMMON menu. These are called [PERSONAL COMMANDS].\nusers from any point in the menu system. These options are not displayed\nunless the user enters '??'. However, they are always selectable.\nTo resolve ambiguity between COMMON menu options and primary options\nwhich begin with the same letters, preceeding an option with a " (double \nquote) will make the selection from the COMMON menu.\nThe following are included in this menu.\n \n [CONTINUE] DISPLAY USER CHARACTERISTICS\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 14:44:00\n", "", "USER,ONE\n", "", ""], ["25", "XUCONTINUE", "HOW TO USE THE 'Continue' OPTION\n", "", "", "\nThe 'Continue' option is similar to 'Halt' in that it allows a \ncomputer will want to re-affirm that you really wish to halt.\nuser to exit without having to back up through the tree of menus.\n \nHalting with 'Continue' will cause the computer to remember what the\nlast option being executed was, and next time the user signs on,\nthere will be the choice of resuming processing at that option.\n \nIf you enter 3 letters or more of the word 'CONTINUE', the computer\nwill halt immediately. Otherwise, if you enter 'CO' or 'C', the\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["26", "XUHALT", "HOW TO USE THE 'Halt' OPTION\n", "", "", "\nThe HALT option will exit you from the computer. This is useful\nif you are several levels deep in a menu and do not want to\n'carriage return' back to the beginning in order to exit.\n \nIf you enter 'HAL' or 'HALT' you will be exited immediately.\n \nIf you enter 'H' or 'HA', the computer will want to re-affirm whether\nyou really wanted to halt.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["27", "XQDIAGRAM", "USING THE 'Diagram Menu' OPTION\n", "", "", "\nThis option will produce a 'tree-structure' diagram of the menu system.\nYou will be prompted for a USER or OPTION name. If you enter a USER\nname, that person's primary menu option will be used as the top of the\ntree, otherwise the OPTION specified will be used.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["28", "XQXREF", "USING THE 'Options By Parents/Other Utilities' OPTION\n", "", "", "\nThis option produces a listing of options cross-referenced by parents.\nparents, are not held by any users as primary or secondary menus, and are\nnot tasked. Each unreferenced option in the package specified is presented\nwith all its fields and then the choice can be made to delete or not.\nIt also indicates whether an option is in use as a primary, secondary or\ntasked menu. It can be run by package by entering a 2-4 letter package\nprefix, or can be run on the entire option file.\n \nThis option also allows you to inquire to who holds specified options as\na primary or secondary menu option.\n \nYou may also delete unreferenced options. These are options which have no \n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["286", "XMNET-MULTIMEDIA", "HOW MULTIMEDIA MAILMAN WORKS\n", "", "", "\n \n control where images will be received.\n FTP Address for BLOB Receive : This field contains an IP address so\n that the receiver can dynamically control the machine that the\n sender will connect to when it send the image.\n FTP Username : It contains the username that the FTP process has to \n use in order to log into this system.\n FTP Password : It contains the logic that the sender will have to make\n in order to log into this system via FTP. \n [FTP RECEIVE NETWORK LOCATION]\n 1. Multimedia [TECHNICAL OVERVIEW]\n 2. Sending and Receiving BLOBs across a [BLOB NETWORK] \n 3. Basic [COMPONENTS] needed to run Multimedia mail\n 4. Kernel site parameters that are used by the Multimedia sender\n and receiver\n FTP Receive Directory : This field stores the information that is\n passed from the receiver to the sender about where to put the\n file that is coming. In this way the receiver can dynamically\n
\n\n", "\n- \n\n
\n", "", "1993-12-06 20:21:00\n", "", "USER,ONE\n", "", ""], ["287", "XMNET-MULTIMEDIA-OVERVIEW", "Multimedia Technical Overview\n", "", "", "\n When using an imaging workstations, a user can view images that are linked\n The network transmission works by sending a message first. During the\n exchange of message protocol data units, information is exchanged about\n the [BLOB] that is going to be sent via FTP. The sender indicates that\n there is a BLOB to send. The receiver replies with the IP address to \n send the message to and the directory to put it in. The sender then\n constructs a series of commands that will access the FTP software\n running on that machine, stores in as a file that can be executed in\n batch mode and puts an entry MUMPS global to indicate that the file needs\n to be executed. A background process in MUMPS (XMRTCP), polls this file\n every few seconds and when it sees an entry, it makes a request to the\n to a message on a second screen. This works using standard calls to the\n imaging API to move the appropriate image into the export directory. \n When the image is in the export directory the aforementioned file is\n executed and the image is FTP'd to receiver of the message. \n API of the imaging product. Images are brought off of a file server on\n the local area network via ethernet and displayed. Network transmissions \n of messages are performed from a platform that has both NFS capabilities\n and TCP/IP. Images are delivered off of the file server that is on the\n local area network into a directory that is mounted via NFS onto this \n platform, again by a call to the imaging API. The relationships of\n multimedia [HARDWARE] must be setup correctly.\n
\n\n", "\n- \n\n
\n", "", "1993-12-06 20:30:00\n", "", "USER,ONE\n", "", ""], ["288", "XMNET-BLOB-HARDWARE", "BLOBs (Binary Large Objects) Message\n", "", "", "\n \nUsing Multimedia MailMan without a network capability is fairly simple.\nThe imaging workstation has the ability to direct an image that is stored\non large disk drives on a Local Area Network (LAN) to a high resolution\ndisplay monitor. BLOBs can be captured and recorded in the IMAGE file and\nthen attached to a message easily at any terminal. If one attempts to read\nthem from a terminal that is not capable of viewing the binary portion,\nthe user will see a textual summary of what is attached, but no BLOB. At\nan imaging workstation, the user will be asked which BLOBs he wishes to\nview.\nBLOBs exist in messages as pointers to the IMAGE file (#2005). In order to\nattach a BLOB to a message, the BLOB must exist in that file. Each entry\nin the IMAGE file than has the data necessary for it to be found and used\nby the system. MailMan uses calls to the VistA Imaging package in order to\nmanipulate these non-textual Body parts. Entries in the IMAGE file are\nlooked up, displayed and moved to a disk drive where they can be\ntransmitted using FTP by calls to the VistA Imaging package.\n \n
\n\n", "", "", "1993-12-06 20:14:00\n", "", "USER,ONE\n", "", ""], ["289", "XMNET-MULTIMEDIA-HARDWARE", "The relationships of Multimedia hardware\n", "", "", "\n \n NAF0:[export.mail] and is where the Imaging API places files that\n MailMan has indicated via a call that it needs to send to a remote\n system. The second, called NAF0:[import.mail], is where files are\n received.\n The platform that network transmission are done from, the imagimg\n workstation and the file server are all connected to the local area\n network. Each is DDP'd to the same MUMPS database. At least one\n directory that is known on the network platform (if it is a VAX) as\n NFA0: is mounted via NFS client software onto it from the file server, \n which is running NFS server software. This directory appears, then,\n as a logical device. The two subdirectories that MailMan uses during\n network mail transmissions must be created. The first is called\n
\n\n", "", "", "1993-12-06 20:23:00\n", "", "USER,ONE\n", "", ""], ["29", "XQ-USER-MENU", "USING THE MENU SYSTEM\n", "", "", "\nThe menu system is the way thru which options are accessed. Menus are \nthis level. You can also [JUMP] to options which are accessible to you\nbut not in the current menu by using an '^' or '^^'.\n \nThere is a group of options called the [COMMON MENU] which is available\nat all times. \n \nIf you find that you need more information to be able to respond to a\n'Select ... Option' prompt, entering [QUESTION] marks will be of help.\narranged in a hierarchical or tree structure. Starting at the top\nyou can progress thru levels to get to all your options.\n \nWhen you are in the menu system you will see the prompt:\n \n 'Select ... Option:'\n \nYou can respond to this prompt by [NAMING] an option which is available at\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 14:55:00\n", "", "USER,ONE\n", "", ""], ["290", "XMNET-BLOB-NETWORK", "Sending and Receiving BLOBs across a Network\n", "", "", "\n \n the file off of the LAN and a second to put the file onto the remote\n machine. The use of NFS halved the time it took to deliver images.\n Imagings have been transmitted across a wide area network, they\n take from 7 to 15 minutes usually to be sent this way. Adding a very\n high speed channel that is capable of transmitting images in less than\n a minute makes the system really impress. In both cases, it is \n necessary to make the system as efficient as possible. Our second pass\n at making this work included an Network File System (NFS) capability.\n This allowed us to perform only one FTP to get an image from site A to\n site B. The first scenario tested required at least two, one to get \n
\n\n", "", "", "1993-11-05 09:23:00\n", "", "USER,ONE\n", "", ""], ["291", "XMNET-FTP-REC-NETWORK-LOCATION", "FTP Receive Network Location\n", "", "", "\n \n This fields contains the name of the entry in the Network:Location file\n that corresponds to the FTP Receive Directory field so that the entry\n that is created in the image file to represent the BLOB can be found\n and displayed.\n
\n\n", "", "", "1993-10-28 14:04:00\n", "", "USER,ONE\n", "", ""], ["292", "XMNET-FTP-COMPONENTS", "Basic components in setting up the Multimedia Mail\n", "", "", "\n \n o FileMan 20 or later version\n \n o Imaging system components:\n \n Abstractor code (also handles part of network mail\n interface)\n File Server (currently DHCP uses Novell)\n Imaging Workstation and appropriate $ZCALLS installed\n Summary of needs:\n o MailMan 7.1 or later version\n \n XMRTCP must running on the node that has TCPIP\n capability and the NFS drive mounted on it.\n \n o Kernel 7 or later version\n \n
\n\n", "", "", "1993-12-06 20:20:00\n", "", "USER,ONE\n", "", ""], ["3", "XQKEYALLOCATE-HOLDER", "RESPONDING TO THE 'Holder of security key' PROMPT\n", "", "", "\n \n?? - To see the list of recipients you've already specified.\n \n??? - To see the list of keys from which you may choose, the current\n holders of a particular key, the User File, or the members of\n a mail group.\n \n-USER - To take a user off the list specified preceed it with a minus sign.\n \nG.GROUP - To specify a set of users as defined by a mailgroup, preceed the\n group name with 'G.'\nAt this prompt you should select users. You may choose a single user \nor a set of users. You can use a mailgroup to specify a group of users.\nRespond with the name of the user(s), one at a time.\n \nYou may also respond with one of the following:\n \n^ - To exit this option.\n \n
\n\n", "", "", "1989-03-08 08:15:00\n", "", "USER,ONE\n", "", ""], ["30", "XQ-USER-QMARK", "USING QUESTION MARKS IN THE MENU SYSTEM\n", "", "", "\nThere are different sorts of 'help' available thru entering question marks\n which are always available to the user.\n \n ??? - Three question marks will show brief descriptions for each\n option in the menu.\n \n ???? - Four question marks shows extended help for this menu.\n \n ?OPTION - An option name preceeded with a '?' shows extended help for\n that option.\nat a 'Select ... Option' prompt:\n \n ? - A single question mark lists all options which can be accessed\n from the current one. It has the same effect as [AUTO-MENU].\n \n ?? - Two question marks lists all options, showing their formal\n names and [LOCKS]. \n Also listed will be the common menu containing options\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 14:53:00\n", "", "USER,ONE\n", "", ""], ["31", "XQ-USER-AUTOMENU", "THE AUTO-MENU SWITCH\n", "", "", "\nThe 'Auto-menu' switch, when turned on, will show all options which\n \n \n \n \n \n \n \ncan be accessed at a 'Select ... Option' prompt. If the switch is\nturned off, the same list will be displayed on entering a '?'.\n \nOnce a user is familiar with their menu, it is preferable to have this\nswitch turned off for speedier navigation thru menus.\n \nThe list of options may include options which are temporarily\n[NOT AVAILABLE] as well as options which have [PROHIBITED TIMES].\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 14:57:00\n", "", "USER,ONE\n", "", ""], ["32", "XQ-USER-LOCKS", "THE LOCKING OF OPTIONS\n", "", "", "\nSometimes an option will be displayed with the words 'LOCKED:' following\nit. This will only be shown in response to '??'.\n \nIf an option is locked, only users possessing the appropriate key can\nhave access to that option. The site manager is responsible for assigning\nkeys to users.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["33", "XQ-USER-OOO", "OPTIONS WHICH ARE NOT AVAILABLE\n", "", "", "\nSometimes an option is displayed in the menu system with the words\n'(NOT AVAILABLE)' following it. This means that the site manager or\npackage developer has temporarily disabled this option.\n \nIf you attempt to select the option, there is sometimes additional\ntext explaining the out-of-order condition.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["332", "XDR IDENTIFY", "DUPLICATES: FINDING THEM\n", "", "", "\nThe option 'CHECK FILE FOR DUPLICATES' will help you to find duplicate\nbasic search on the entire file, or a search using only new or edited\nentries.\n \nYou may interrup any of these searches and continue it at another time.\nIf you have an incomplete (halted) search, you will be asked if you want\nto [CONTINUE] it, or initiate a new one.\n \nThe potential duplicate pairs are placed in the Duplicate Record file.\nTo [LIST] them, use the 'PRINT LIST OF FILE DUPLICATES' option.\nentries in a selected file.\n \nThis utility searches the selected file, marking entries it considers to\nbe probable duplicates and entering the pair in the Duplicate Record file.\nYou will need to look at each of these and verify whether they are\nactual duplicates or not.\n \nYou can choose one of two [METHODS FOR SEARCHING] the file:\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["333", "XDR IDENTIFY METHODS", "DUPLICATES: METHODS FOR FINDING\n", "", "", "\nBASIC SEARCH\n \nThe amount of time the search will take depends on the number of records\nin the file. When you start a Basic search it will be placed in a\nTaskman Queue to be run in a background job. This search can be halted\nand restarted any number of times if necessary.\n \n \nNEW SEARCH\n \nThis method checks only newly added and edited records. It should\n \nbe completed in one night, but can be halted and restarted just as\nthe basic search if necessary.\nThis method checks the entire selected file for duplicates. It starts\nat the beginning of a file and checks each record against a subgroup\nof records (defined by the candidate collection routine written by\nthe package developer) for possible duplicates. If two records are\ndetermined to be potential duplicates they are placed in the Duplicate\nRecord file as Potential Duplicates. These records will then be\nverified as either Verified Duplicates or Verified Non-Duplicates.\n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["334", "XDR PRINTLIST", "DUPLICATES: LISTING\n", "", "", "\nThis utility produces various [DUPLICATE RECORD LISTINGS].\nlist all fields that contain data from the Duplicate Record file.\nYou may select whether you want a listing of Potential Duplicates,\nReady to Merge Verified Duplicates, or Not Ready to Merge Verified\nDuplicates.\n \nYou may select based on 'Date Found'. If you want to see only those\nduplicates identified recently, enter a recent date range.\n \nThe type of listing you get is a captioned format report, that will\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["335", "XDR IDENTIFY CONTINUE", "DUPLICATES: CONTINUING A SEARCH\n", "", "", "\nAnytime a search has been interrupted before completion, you will be\nrestarted during slack times.\ngiven an opportunity to continue that search where it left off.\n \nThe Duplicate Resolution file is used to keep track of the last\nrecord checked for duplicates when a search is halted.\n \nThis is especially useful on the basic search of a file as it is\nlikely that it will take more than a few nights to complete. This\nalso allows the search to be halted during peak operation times and\n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["336", "XDR DUPLICATE RECORD LISTINGS", "DUPLICATE RECORD LISTINGS\n", "", "", "\nPotential Duplicates:\nThis is a listing of all Verified Duplicate Pairs for a selected file that\nhave a status of ready to merge. These are record pairs that can be merged\nbecause all package interactive merges have been completed.\n \nNot Ready to Merge Verified Duplicates:\n \nThis is a listing of all Verified Duplicate Pairs for a selected file that\nhave a status of not ready to merge. These are record pairs that can not\nbe merged yet due to a package interactive merge process that has not\ncompleted. This listing is useful to find out which packages are keeping\n \nthis duplicate pair from being merged and the appropriate department can\nbe encouraged to finish the interactive process.\nThis provides a listing of all Potential Duplicate Pairs for a selected file\nin a captioned format. These are records that have not been verified as\neither Verified Duplicates or Verified Non-Duplicates. It prints all\nfields that have data from the Duplicate Record file.\n \nReady to Merge Verified Duplicates:\n \n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["337", "XDR PURGE", "PURGE DUPLICATES\n", "", "", "\nThis utility is used by the Duplicate Manager to purge the Duplicate\nThe actual purging is put into a Taskman Queue and done in a background\njob.\nRecord file of entries of a selected file.\n \nYou may purge just the Potential Duplicates, the Verified Non-Duplicates,\nor both for a selected file.\n \nYou can only purge entries for those files that you have Fileman Access\nfor.\n \n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["338", "XDR VERIFY ALL", "VERIFY POTENTIAL DUPLICATES\n", "", "", "\nThis option is used to verify Potential Duplicates as either Verified\n***IF THE OPERATOR CANNOT MAKE A DETERMINATION AT THIS TIME WHETHER\nTHE PAIR ARE DUPLICATES OR NOT, THEY CAN JUST ENTER A <RETURN> WHICH\nWILL LEAVE THE PAIR AS POTENTIAL DUPLICATES. THEN AT A LATER TIME\nAFTER THEY HAVE RECEIVED THE APPROPRIATE INFORMATION THEY CAN CHANGE\nTHE PAIR TO A DIFFERENT STATUS.***\n \nYou may quit this option by entering a '^' and then answering 'YES'\nto the question asking if you want to quit.\n \nIf you verify the pair as Verified Duplicates a bulletin will be\nDuplicates or Verified Non-Duplicates.\nsent to all members of the Verified Mail Group notifying them about\nthe records that have been identified as verified duplicates getting\nready to merge. It will also begin the [MERGE] process.\n \nThis starts with the first Potential Duplicate pair and displays\nthe two records side by side with field headings at the left.\nBy looking at the entries and any supporting documents the operator\nmakes a choice whether to change the Potential Duplicate pair to\na Verified Duplicate pair or a Verified Non-Duplicate pair.\n \n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["339", "XDR MERGE PROCESS", "MERGE PROCESS\n", "", "", "\nThe merge process really begins when two records are Verified as\nif they have their own special merge routine or if an interactive\nspecial merge process has to occur for them. This is done for all\npackages.\n \nIf none of the packages have an interactive merge (which means the\nmain merge has to wait until that packages merge has taken place)\nthe merge process will continue. If there is an interactive merge\nprocess that has to occur for a particular package a bulletin will\nbe sent to all members of the Verified Duplicate Mail Group notifying\nthem about the records that have been identified as Verified duplicates.\nDuplicates. When two records are verified as duplicates the operator\n \nOnce all the package interactive merge processes have been completed\nthe two records will be merged and a Merged Bulletin sent to all them\nmembers of the Merged Mail Group.\nis asked which record they wish to merge to the other record (the From\nand To records). After the From record is established the following\nsteps occur:\n \nThe packages that have a file entry for the 'Affects Record Merge'\nare first checked to see if they have data for the From record which\nis being merged. If they do have data they are then checked to see\n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["34", "XQ-USER-PROTIMES", "OPTIONS WITH PROHIBITED TIMES\n", "", "", "\nSometimes an option will be displayed with 'prohibited times'.\nWhat this means is that the site manager has decided that this option\ncan only be run during certain times of the day.\n \nAn option is usually assigned a prohibited time if it uses a lot of\nsystem resource, and is best not run during peak production hours.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["340", "XDR ADD VERIFIED", "ADD VERIFIED DUPLICATES\n", "", "", "\nThis option allows the operator to place two records that they know\n \nAfter adding them as a Verified Duplicate pair the [MERGE] process\nwill begin.\nare duplicates that are not already identified as a Potential or\nVerified Duplicate pair into the Duplicate Record file.\n \nIt will run them through the Kernel Duplicate Resolution\nalgorithm and record there scores.\n \nThe normal process of [VERIFICATION] will not occur since these are\na known duplicate pair.\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["341", "XDR AUTO MERGE", "AUTOMATICALLY MERGE ALL READY TO MERGE VERIFIED DUPLICATES\n", "", "", "\nThis option is used to merge all Verified Duplicate pairs for a\n \nSome sites may choose to place this option in a Taskman Queue to run\nin the background but it is not known what effect Fileman dictionaries\nthat write messages to the screen will have on this process.\n \nThe merge process may take quite some time depending on the amount of\ninformation and the number of files that have to be merged. This option\nif not queued should only be run on a terminal that can be dedicated to\nthis task for some large amount of time.\nselected file that have a merge status of READY TO MERGE.\n \nThis merges all records that were not previously merged in the\nnormal [MERGE] process due to special package merges that needed\nto occur before the final merge could occur.\n \nWhen this option is used there will be no interaction with the operator\nand no messages written to the screen.\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["342", "XDR CHECK PAIR", "CHECK PAIR OF RECORDS TO SEE IF DUPLICATES\n", "", "", "\nThis utility allows the operator to select two records from a selected\nif the pair received a high enough total score during the check.\nIf through this option you determine that they are indeed duplicates,\nthe operator should add them as Verified Duplicates through the\n'[ADD VERIFIED DUPLICATE PAIR]' option.\nfile and run them through the Duplicate Resolution [ALGORITHM].\n \nIt will display for them on the screen or they can have it print out\nto a printer a listing of the two records side by side with the field\nnames on the left. It will also print the scores the records received\nthrough the duplicate resolution algorithm.\n \nThis option does not add the pair to the Duplicate Record file even\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["343", "XDR DUP ALGORITHM", "DUPLICATE RESOLUTION ALGORITHM\n", "", "", "\nThe Kernel Duplicate Resolution software uses a algorithm obtained from\nFor example in the Name test, the software will take the names from\nthe two records and compare them and assign them either a\nSuccessful Match Weight or a Unsuccessful Match Weight (defined in\nthe Duplicate Resolution file) and pass this value back to the\nDuplicate Resolution software.\n \nOnce all of the tests have been applied to the two records in question\na total score will be computed and then checked to see if it exceeds\nthe Potential Duplicate Threshold% (defined in the Duplicate Resolution\nfile), if it does the two records will be added to the Duplicate Record\nthe Duplicate Resolution file for determining if two records from the\nfile as Potential, Unverified Duplicates.\nsame file are potential duplicates.\n \nIn the Duplicate Resolution File entry for a given file there are a\nseries of tests which will be applied against the two records in\nquestion. Examples of these tests would be Name, SSN, Mother's Maiden\nName, etc for the VA Patient file.\n \n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["344", "XDR EDIT DUP RESOLUTION FILE", "EDIT DUPLICATE RESOLUTION FILE\n", "", "", "\nThis utility is used to edit the fields for a selected file entry\nduplicate tests for the selected file. It also contains information\non the status of the duplicate search, ie., beginning date, completion\ndate, last record checked, total number of records checked, type of\nsearch being run.\n \nYou may see the fields of the [DUPLICATE RESOLUTION FILE] by entering\nthe key word.\nof the Duplicate Resolution File.\n \nThe Duplicate Resolution file is the control file which a package\ndeveloper would create an entry from which to allow the operator\nto check a selected file for duplicates.\n \nThis file contains the values associated with the various\nthreshold percentages, and holds the scoring for the specified\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["345", "XDR DUPLICATE RESOLUTION FILE", "FIELDS OF THE DUPLICATE RESOLUTION FILE\n", "", "", "\nFIELD # FIELD NAME\n.08 Last Record Processed\n.09 Candidate Collection Routine\n.11 Duplicate Manager Mail Group\n.15 Potential Duplicate Threshold%\n.16 Verified Duplicate Mail Group\n.17 Verified Duplicate Msg Routine\n.18 Verified Duplicate Threshold%\n \n[CONTINUE]\n \n.01 File to be Checked\n.02 Duplicate Search Status\n.03 Search Beginning Date\n.04 Search Completion Date\n.05 Type of Search\n.06 Cross-Ref for New Search\n.07 Number of Records Processed\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["346", "XDR DUP RESOLUTION FILE CONT", "DUPLICATE RESOLUTION FILE FIELDS CONTINUED\n", "", "", "\nFIELD # FIELD NAME\n \n1100 Duplicate Tests\n .01 Duplicate Test\n .02 Order of Test\n .03 Duplicate Test Routine\n .04 Field to be Checked\n .05 Successful Match Weight\n .06 Unsuccessful Match Weight\n \n1200 Dinum Files for Merge\n \n .01 Dinum file for Merge\n.25 Merge Style\n.26 Delete From Entry\n.27 Pre-Merge Routine\n.28 Post-Merge Routine\n.29 Merge Mail Group\n.31 Merge Msg Routine\n.32 Auto Merge Status\n
\n\n", "", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["347", "XDR MERGE VERIFIED DUPLICATES", "MERGE READY TO MERGE VERIFIED DUPLICATES\n", "", "", "\nThis option is used to merge all duplicate pairs for a selected\ndetermined by the Merge Style field in the Duplicate Resolution file.\n \nThis process will begin with a double check through the package file\nlooking to see if any new packages that affect this file merge have\nbeen added and if any of the packages that previously did not have\nrecord data now do. If any new packages have been added and they\ncontain record data and have an interactive merge process, the\nMerge Status field will be reset to Not Ready to Merge and the [MERGE]\nprocess will not be started.\nfile that have a merge status of Ready to Merge and a status of\nVerified Duplicates.\n \nThese are duplicate pairs that were not merged during the\nverification process due to interactive package merges that\nneeded to occur before the main merge could occur.\n \nThe style of merge (Interactive versus Non-Interactive) will be\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["348", "XDR MERGE SELECTED PAIR", "MERGE SELECTED READY TO MERGE VERIFIED DUPLICATE PAIR\n", "", "", "\nThis option is used to merge a operator selected Ready to Merge\nThe style of merge will depend on the Merge Style field of the\nDuplicate Resolution file.\n \nAfter selecting the pair of records to merge the first thing to occur is\nthe rechecking of the package file to see if any new packages that affect\nrecord merge have been added since the day the records were verified as\nduplicates. If any new packages or if any packages that previously did\nnot contain record data now contain data and they have interactive\nmerge processes that need to occur the [MERGE] process will not be\nstarted.\nVerified Duplicate Pair.\n \nReady to Merge Verified Duplicates are pairs of duplicates that were\nnot merged during the verification process due to package interactive\nmerges that needed to occur before the main merge.\n \nThe operator is only allowed to select duplicate pairs that have\na Merge Status of 'Ready to Merge' and a Status of 'Verified Duplicates'.\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["349", "XDR VERIFY SELECTED PAIR", "VERIFY SELECTED POTENTIAL DUPLICATE PAIR\n", "", "", "\nThis option is used to allow the operator to select a Potential\nVerified Non-Duplicate pair.\n \n***IF THE OPERATOR CANNOT MAKE A DETERMINATION AT THIS TIME WHETHER\nTHE PAIR ARE DUPLICATES OR NOT, THEY CAN ENTER A <RETURN> WHICH\nWILL LEAVE THE PAIR AS POTENTIAL DUPLICATES. AT A LATER TIME\nAFTER THEY HAVE RECEIVED THE APPROPRIATE INFORMATION THEY CAN CHANGE\nTHE PAIR TO A DIFFERENT STATUS.***\n \nIf you verify the pair as Verified Duplicates a bulletin will be\nsent to all members of the Verified Mail Group notifying them about\nDuplicate pair for a selected file and verify them as either\nthe records that have been identified as Verified Duplicates getting\nready to merge. It will also begin the [MERGE] process.\nVerified Duplicates or Verified Non-Duplicates.\n \nAfter selecting the Potential Duplicate pair to verify, the\nsystem will display the two records side by side with field\nheadings to the left. By looking at the entries and any supporting\ndocuments the operator makes a choice whether to change the\nPotential Duplicate pair to a Verified Duplicate pair or to a\n
\n\n", "\n- \n\n
\n", "", "1991-06-24 00:00:00\n", "", "POSTMASTER\n", "", ""], ["35", "XQ-USER-JUMP", "JUMPING TO AN OPTION\n", "", "", "\nIf you know the name or synonymn of an option, you can 'jump' to\n \nYou need only enter enough characters to uniquely identify the option.\nIf what you've entered matches with other options, you will be prompted for\na choice. \n \nYou may occasionally see a message about 'rebuilding-menus'. In such a\ncase, a menu has been changed and the system must take a few moments to\nrebuild some internal structures. In such cases, you may access the option\nthrough the menu tree.\n \nit directly by using the '^'. This means that you do not need to\nEntering '^?' will display all options in your tree.\nstep thru several levels of menus to get to an option.\n \nIn response to the 'Select ... Option' prompt,\nenter ^OPTION NAME, where OPTION NAME is the name or synonym of the\noption you wish to jump to. Enter ^^OPTION NAME to jump out to the option\nand back again (as a rubber band jump). Or just enter ^^ to return to\nthe menu that is presented when you first sign on (your primary menu).\n
\n\n", "", "", "1992-04-15 14:52:00\n", "", "USER,ONE\n", "", ""], ["350", "LRMITS DEFAULTS", "Micro Trend Default Reports\n", "", "", "\n Default Reports\nquestions for entering the types of reports and criteria are not asked.\nAt least one type of report must be defined.\n \nDefaults for criteria are not defined in file 69.9, they are defined by the\nprogram. Default criteria is set to report all bacteria types of\norganisms, not have a length of stay restriction, not be restricted to any\nantibiotic pattern, merge isolates from the same specimen, and not include\na detailed report.\n \nReport types include: Organism, Specimen, Collection Sample, Patient,\nProvider, and Location. Each report can be selected to be printed for all\nvalues, selected values or not printed.\n \nDefaults can be set for the different report types. The defaults for\nreport types can be defined in the Laboratory Site file All values for a\ndefined report are printed. (69.9). If default reports are selected, the\n
\n\n", "", "", "1992-10-01 12:16:17\n", "", "POSTMASTER\n", "", ""], ["351", "LRMITS TIME RANGE", "Micro Trend Time Range\n", "", "", "\n \ncollection dates within the time range.\n \nThe dates entered determine a time range. It does not matter if the start \ndate is earlier or later than the end date. The time range applies to all \ntypes of reports selected.\n \n \n \n \n \n Time Range\n \n \nThe start and end dates determine the time range for the report. The \ndate range can uses the dates entered. You can also enter months. \nFor example 1/93 to 3/93 will report all data for those three months.\nA date range of 1/14/93 to 3/15/93 does not include all three months.\n \nThe report uses the time range to restrict the data to those specimen \n
\n\n", "", "", "1992-10-01 12:16:58\n", "", "POSTMASTER\n", "", ""], ["352", "LRMITS SORG", "Micro Trend Specific Organisms\n", "", "", "\n Specific Organisms\nmust have been previously selected.\n \nThis criteria is useful in tracking specific organisms.\n \nAll reports can be restricted to specific organisms. Any organisms can be\nselected so long as that organisms type was also selected in the prompts to\ninclude specific types of organisms. The default is to include only\nbacteria.\n \nFor example, if you wanted all reports to include Mycobacteria tuberculosis\nand Coccidioides immitis then Mycobacteria and Fungus types of organisms\n
\n\n", "", "", "1992-10-01 12:17:29\n", "", "POSTMASTER\n", "", ""], ["353", "LRMITS LOS", "Micro Trend Length of Stay\n", "", "", "\n \n \nThe length of stay (LOS) is printed as part of the detailed report. All \ninpatient cultures would have a length of stay displayed.\n \nThis criteria is useful for tracking nosocomial (hospital acquired) \ninfections. Note - there is no check that a similar isolate was recorded \nbefore the length of stay restriction.\n \n \n \n Length of Stay\n \n \nAll reports can be restricted to include only isolates that were collected \nafter a specified time from admission. Only isolates from inpatients (at \nthe time of specimen collection) would be included.\n \nFor example, if a length of stay of '3' is entered then reports would only \ninclude data on specimens collected 3 days after the admission date.\n
\n\n", "", "", "1992-10-01 12:17:55\n", "", "POSTMASTER\n", "", ""], ["354", "LRMITS AP", "Micro Trend Antibiotic Pattern\n", "", "", "\n \n \nFor example, a pattern is entered to be penicillin resistant, tetracycline \nsensitive, and nafcillin resistant. An isolate that has several \nantibiotics reported, including penicillin resistant, but no tetracycline \nor nafcillin tested would be included in the report. An isolate with \npenicillin resistant, tetracycline resistant, and nafcillin resistant would \nnot be included in the report.\n \nReporting isolates with specific antibiotic patterns may be useful in \ntracking specific types of infections.\n Antibiotic Pattern\n \n \nAll reports can be restricted to include only those isolates with a \nspecific antibiotic pattern. An antibiotic pattern can be created by \nentering a sequence of antibiotics with corresponding interpretations. In \norder for any isolates to be included on the antibiotic trend report, an \nisolate must be tested for antibiotics and have no conflicts with the \npattern.\n
\n\n", "", "", "1992-10-01 12:18:18\n", "", "POSTMASTER\n", "", ""], ["355", "LRMITS MERGE", "Micro Trend Merge Criteria\n", "", "", "\n \npattern, and 4) either the same specimen, the same collection sample, or \nany sample.\n \nThe same antibiotic pattern means that isolates being merged do not have \nconflicting interpretations for antibiotics that are reported.\n \nSelections of merge criteria include: none (no merges are done), by \nspecimen, collection sample, or any sample.\n \nA detailed report can be obtained to review isolates that were merged.\n Merge Criteria\n \n \nIsolates that are identical but reported multiple times can interfere with \nan accurate count on the antibiotic trend report. Ideally identical \nisolates would only be counted once. Defining identical isolates is \ndifficult when relying solely on computer data. Merging isolates on the \nantibiotic trend report can be done by defining those isolates having four \ncriteria: 1) the same patient, 2) the same organism, 3) the same antibiotic \n
\n\n", "", "", "1992-10-01 12:18:37\n", "", "POSTMASTER\n", "", ""], ["356", "LRMITS DETAIL", "Micro Trend Detailed Reports\n", "", "", "\n \nThis report can be used to confirm the percentage of susceptibility and \ncounts of organisms. It can also be used as a survey tool, providing more \ndetailed information to track areas of interest.\n \nA detailed report does not take much longer to process than a non-detailed \nreport but it does print out many more pages of information.\n \n \n \n \n Detailed Reports\n \n \nA detailed report can be included in the antibiotic trend report. In \naddition to totals of susceptibilities, this report includes information on \neach isolate. The patient, antibiotic interpretations, accession, \ncollection date, a flag if the isolate was merged with a previous isolate, \nand the length of stay since the collection date.\n \n
\n\n", "", "", "1992-10-01 12:19:03\n", "", "POSTMASTER\n", "", ""], ["357", "LRMITS REPORT TYPES", "Micro Trend Report Types\n", "", "", "\n \nselected it can report all values of that type or selected values. For\nexample, a report for all organisms, and a report for urine and sputum\nspecimens could be selected.\n \nCriteria can be entered that effects all report types. The criteria can\ndetermine the organisms to be reported, the time range, merge criteria,\ndetailed information, and antibiotic patterns.\n Report Types\n \nSix report types are available: 1) organism, 2) specimen, 3) patient, 4)\nphysician, 5) location, 6) collection sample. Data are sorted by these\ntypes. Each type the data are then sorted by organism type (bacteria,\nfungus, mycobacteria, parasites, and virus) and then by organisms.\n \nEach type of report can be selected to be printed. If the report is\n
\n\n", "", "", "1992-10-01 12:19:24\n", "", "POSTMASTER\n", "", ""], ["358", "LRMITS OPTION", "Micro Trend Option\n", "", "W @IOF\n", "\n Antibiotic Trends Report\n Report Types\n Criteria for Reports\n Time Range\n Types of Organisms\n Specific Organisms\n Length of Stay\n Antibiotic Pattern\n Merge Criteria\n Detailed Reports\n Printing Reports\n \n \nThis report is used by the Laboratory to look for changes or trends in\nsusceptibility patterns. Select a specific topic for further information.\n \n Topics:\n \n General Description\n Default Reports\n
\n\n", "\n- \n\n
\n", "", "1992-10-01 12:24:38\n", "", "POSTMASTER\n", "", ""], ["359", "LRMITS OTYPE", "Micro Trend Organism Types\n", "", "", "\n \norganisms will not report values for susceptibility testing. Mycobacteria \nwill display antimicrobial testing on detailed reports only. Including \nother types of organisms can be helpful where it is useful to see all \norganisms isolated.\n \nThe types of organisms selected restricts any specific organism that might \nbe selected. Therefore, if you wish to obtain reports for only the \norganisms of Giardia lamblia and Salmonella, then Parasite and Bacteria \nmust have been selected in order to select those organisms at the 'Select \nOrganism:' prompts.\n Types of Organisms\n \n \nAll reports can be restricted to specific types of organisms. The types of \norganisms include: Bacteria, Fungus, Mycobacteria, Parasite, and Virus. \nAny or all of the types can be selected. The default for all reports is to \ninclude only Bacteria.\n \nSince only bacteria have the usual antibiotic data, other types of \n
\n\n", "", "", "1992-10-05 15:10:56\n", "", "POSTMASTER\n", "", ""], ["36", "XQ-USER-SELECTOPT", "HOW TO SELECT AN OPTION BY NAME\n", "", "", "\nTo select an option by name, you need only enter enough characters\nsufficient to make a choice because it matches with two options. In this\ninstance, the computer will list out the ambiguity and then you can select\nby number or name.\n \nSometimes an option will have a 'synonym' displayed to the left of its\ntext. This is an abbreviation of the option name which can also be used\nto select it.\nof its name to uniquely identify it. For example if you have a menu\nwhich consists of the following options:\n \n Patient Inquiry\n Print Summary\n Medication Profile\n \nEntering an 'M' will select Medication Profile. Entering a 'P' is not\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["360", "LRMITS GENERAL", "Micro Trend General Description\n", "", "", "\n \nSite file (69.9). Reports can be restricted to specific types of values \n(i.e. specific patients, specific specimens, etc.). The reports can be \nrestricted to criteria that effect all types of reports.\n \nThe criteria and types of reports are selected by the user. The report \nis forced to be queued - preferably to be run during off hours. \nMerges can be done so that isolates from the same patient and same \norganism, and non-conflicting antibiotic patterns will only be \ncounted once. Merges also depend on being isolated from the same \nspecimen, collection sample or any sample. A detailed report showing \n General Description\neach isolate's values can be used to confirm the counts reported.\n \nThe antibiotic trend report is used to compare counts of organisms and \npatterns of antibiotic susceptibility. Different types of reports can be \ngenerated. Reports can be sorted by organism, patient, location, \nphysician, specimen, and collection sample. For each type, the report is \nsorted by organisms. The different types of reports can be selected by the \nuser. Defaults for these report types can be defined in the Laboratory \n
\n\n", "", "", "1992-10-05 15:11:26\n", "", "POSTMASTER\n", "", ""], ["361", "LRMITS CRITERIA", "Micro Trend Report Criteria\n", "", "", "\n \nall isolates.\n \nMany varieties of reports are possible. If default reports are used then \ncriteria will not be asked. Defaults will report all bacteria, not \nconsider length of stay or antibiotic pattern, merge by specimen, and not \ninclude a detailed report.\n \n \n \n \n Criteria for Reports\n \n \nCriteria can be entered that effect all of the report types printed. The \ncriteria include: restricting reports to only certain organisms (bacteria, \nfungus, mycobacteria, parasites, and virus), selection of specific \norganisms, reporting only isolates where the culture was collected a \nspecified time after admission, isolates matching an antibiotic pattern, \ncriteria to merge isolates, and whether to include detailed information on \n
\n\n", "", "", "1992-10-05 15:13:39\n", "", "POSTMASTER\n", "", ""], ["362", "LRMITS PRINT", "Micro Trend Printing Reports\n", "", "", "\n Printing Reports\nIf a report is queued or in the process of printing and needs to be\nstopped, the task can be stopped using the TaskMan User option in the\nUser's Toolbox.\n \n \nIf the report is queued to a spool device then multiple copies can be\nprinted from the spooled report. Separate copies could be sent to\ndifferent printers.\n \nThe antibiotic trend report is process intensive and should be run during\noff hours. The report should be queued. The report has no fixed margin\nlength. Any antibiotics with abbreviations in the Antibiotic\nSusceptibility file (62.06) are printed as a header. If there are more\nantibiotics that can fit on a page then the report will wrap and be\ndifficult to read.\n \n
\n\n", "", "", "1992-10-05 15:14:47\n", "", "POSTMASTER\n", "", ""], ["363", "GECQ PICKUP CODES", "DDCSS Standard Pickup Schedule Codes\n", "", "", "\n \nThese are the standard pickup schedule codes, (as published in Appendix\nB of the DDCSS User Guide). You may refer to that appendix, or find\nout more about the codes for [1 one-day], [2 two-day], [3 three-day],\n[4 four-day], [5 five-day], [6 six-day], or [7 seven-day] schedules\nand their corresponding codes.\n
\n\n", "\n- \n\n
\n", "", "1991-05-29 15:03:00\n", "", "POSTMASTER\n", "", ""], ["364", "GECQ 1-DAY PICKUP CODES", "DDCSS One-Day Pickup Codes\n", "", "", "\n \n Sunday 1G\n Pickup Days Code\n \n Monday 1A\n Tuesday 1B\n Wednesday 1C\n Thursday............................................................1D\n Friday 1E\n Saturday 1F\n
\n\n", "", "", "1991-05-29 14:16:00\n", "", "POSTMASTER\n", "", ""], ["365", "GECQ 2-DAY PICKUP CODES", "DDCSS Two-Day Pickup codes\n", "", "", "\n \n Tue, Wed 2G\n \n Tue, Thu 2H\n Tue, Fri 2J\n Tue, Sat 2K\n Tue, Sun............................................................2L\n Wed, Thu 2M\n Wed, Fri 2N\n Wed, Sat 2P\n \n Pickup Days Code\n Wed, Sun 2Q\n Thu, Fri 2R\n Thu, Sat 2S\n Thu, Sun............................................................2T\n Fri, Sat 2U\n Fri, Sun 2V\n Sat, Sun 2W\n \n Mon, Tue 2A\n Mon, Wed 2B\n Mon, Thu 2C\n Mon, Fri............................................................2D\n Mon, Sat 2E\n Mon, Sun 2F\n
\n\n", "", "", "1991-05-29 14:27:00\n", "", "POSTMASTER\n", "", ""], ["366", "GECQ 3-DAY PICKUP CODES", "DDCSS Three-Day Pickup Codes\n", "", "", "\n \n Mon, Wed, Fri 3G\n \n Mon, Wed, Sat 3H\n Mon, Wed, Sun 3J\n Mon, Thu, Fri 3K\n Mon, Thu, Sat.......................................................3L\n Mon, Thu, Sun 3M\n Mon, Fri, Sat 3N\n Mon, Fri, Sun 3P\n \n Pickup Days Code\n Mon, Sat, Sun 3Q\n Tue, Wed, Thu 3R\n Tue, Wed, Fri 3S\n Tue, Wed, Sat.......................................................3T\n Tue, Wed, Sun 3U\n Tue, Thu, Fri 3V\n Tue, Thu, Sat 3W\n \n Tue, Thu, Sun 3X\n Tue, Fri, Sat 3Y\n \n Tue, Fri, Sun 3Z\n Tue, Sat, Sun.......................................................31\n Wed, Thu, Fri 32\n Wed, Thu, Sat 33\n Wed, Thu, Sun 34\n \n Wed, Fri, Sat 35\n Wed, Fri, Sun 36\n Wed, Sat, Sun 37\n Thu, Fri, Sat.......................................................38\n Mon, Tue, Wed 3A\n Thu, Fri, Sun 39\n Thu, Sat, Sun 3*\n Fri, Sat, Sun 3#\n Mon, Tue, Thu 3B\n Mon, Tue, Fri 3C\n Mon, Tue, Sat.......................................................3D\n Mon, Tue, Sun 3E\n Mon, Wed, Thu 3F\n
\n\n", "", "", "1991-05-29 14:32:00\n", "", "POSTMASTER\n", "", ""], ["367", "GECQ 4-DAY PICKUP CODES", "DDCSS Four-Day Pickup Codes\n", "", "", "\n \n Mon, Tue, Thu, Sun 4G\n \n Mon, Tue, Fri, Sat 4H\n Mon, Tue, Fri, Sun 4J\n Mon, Tue, Sat, Sun 4K\n Mon, Wed, Thu, Fri..................................................4L\n Mon, Wed, Thu, Sat 4M\n Mon, Wed, Thu, Sun 4N\n Mon, Wed, Fri, Sat 4P\n \n Pickup Days Code\n Mon, Wed, Fri, Sun 4Q\n Mon, Wed, Sat, Sun 4R\n Mon, Thu, Fri, Sat 4S\n Mon, Thu, Fri, Sun..................................................4T\n Mon, Thu, Sat, Sun 4U\n Mon, Fri, Sat, Sun 4V\n Tue, Wed, Thu, Fri 4W\n \n Tue, Wed, Thu, Sat 4X\n Tue, Wed, Thu, Sun 4Y\n \n Tue, Wed, Fri, Sat 4Z\n Tue, Wed, Fri, Sun..................................................41\n Tue, Wed, Sat, Sun 42\n Tue, Thu, Fri, Sat 43\n Tue, Thu, Fri, Sun 44\n \n Tue, Thu, Sat, Sun 45\n Tue, Fri, Sat, Sun 46\n Wed, Thu, Fri, Sat 47\n Wed, Thu, Fri, Sun..................................................48\n Mon, Tue, Wed, Thu 4A\n Wed, Thu, Sat, Sun 49\n Wed, Fri, Sat, Sun 4*\n Thu, Fri, Sat, Sun 4#\n Mon, Tue, Wed, Fri 4B\n Mon, Tue, Wed, Sat 4C\n Mon, Tue, Wed, Sun..................................................4D\n Mon, Tue, Thu, Fri 4E\n Mon, Tue, Thu, Sat 4F\n
\n\n", "", "", "1991-05-29 14:42:00\n", "", "POSTMASTER\n", "", ""], ["368", "GECQ 5-DAY PICKUP CODES", "DDCSS Five-Day Pickup Codes\n", "", "", "\n \n Mon, Tue, Thu, Fri, Sat 5G\n \n Mon, Tue, Thu, Fri, Sun 5H\n Mon, Tue, Thu, Sat, Sun 5J\n Mon, Tue, Fri, Sat, Sun 5K\n Mon, Wed, Thu, Fri, Sat.............................................5L\n Mon, Wed, Thu, Fri, Sun 5M\n Mon, Wed, Thu, Sat, Sun 5N\n Mon, Wed, Fri, Sat, Sun 5P\n \n Pickup Days Code\n Mon, Thu, Fri, Sat, Sun 5Q\n Tue, Wed, Thu, Fri, Sat 5R\n Tue, Wed, Thu, Fri, Sun 5S\n Tue, Wed, Thu, Sat, Sun.............................................5T\n Tue, Wed, Fri, Sat, Sun 5U\n Tue, Thu, Fri, Sat, Sun 5V\n Wed, Thu, Fri, Sat, Sun 5W\n \n Mon, Tue, Wed, Thu, Fri 5A\n Mon, Tue, Wed, Thu, Sat 5B\n Mon, Tue, Wed, Thu, Sun 5C\n Mon, Tue, Wed, Fri, Sat.............................................5D\n Mon, Tue, Wed, Fri, Sun 5E\n Mon, Tue, Wed, Sat, Sun 5F\n
\n\n", "", "", "1991-05-29 14:47:00\n", "", "POSTMASTER\n", "", ""], ["369", "GECQ 6-DAY PICKUP CODES", "DDCSS Six-Day Pickup Codes\n", "", "", "\n \n Tue, Wed, Thu, Fri, Sat, Sun 6G\n Pickup Days Code\n \n Mon, Tue, Wed, Thu, Fri, Sat 6A\n Mon, Tue, Wed, Thu, Fri, Sun 6B\n Mon, Tue, Wed, Thu, Sat, Sun 6C\n Mon, Tue, Wed, Fri, Sat, Sun........................................6D\n Mon, Tue, Thu, Fri, Sat, Sun 6E\n Mon, Wed, Thu, Fri, Sat, Sun 6F\n
\n\n", "", "", "1991-05-29 14:05:00\n", "", "POSTMASTER\n", "", ""], ["37", "XQ-USERHELP", "USER HELP\n", "", "", "\nInformation on how to use the system is available thru 'Help Frames'.\nYou can access this online help by entering the 'keyword' for the system\non which you would like information. Help frames are arranged in a \nhierarchical structure, so you can obtain more detailed information on\ntopics of your choice.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["370", "GECQ 7-DAY PICKUP CODES", "DDCSS Seven-Day Pickup Codes\n", "", "", "\nPickup Days Code\n \nMon, Tue, Wed, Thu, Fri, Sat, Sun...................................7A\n
\n\n", "", "", "1991-05-29 14:13:00\n", "", "POSTMASTER\n", "", ""], ["38", "XQ-USER-SIGNON", "SIGNING ON TO THE SYSTEM\n", "", "", "\nIn order to prevent unauthorized use of the computer system, each user\npatient). When you sign-on, you may see a message stating the last time\nyou were on. If you suspect someone is using your codes, it is important\nthat they be changed.\n \nYou can change your own VERIFY CODE thru the [COMMON MENU] option,\n[EDIT USER CHARACTERISTCS]. You may be required to change your VERIFY\ncode periodically. Your site manager can change your ACCESS CODE.\n \nACCESS and VERIFY can be entered on one line separated with a ';' to\nspeed up the sign-on process.\nis assigned codes allowing access.\n \nOn entering the system, you will be prompted for an ACCESS CODE, then\na VERIFY CODE. These codes are initially assigned by the site manager.\nOn recieving your codes, do not write them down, and never share them\nwith another user. Entering these codes will identify you to the computer,\nand your name will be associated with many of the functions you perform\nthru the computer. (ie. Sending messages, Entering an RX, Registering a\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 14:34:00\n", "", "USER,ONE\n", "", ""], ["382", "OR PATIENT LOOKUP", "Enhanced Patient Look-up\n", "", "", "\n \n LIST: You may modify the list from which you are selecting\n by entering a [LOCATION], [TREATING SPECIALTY],\n [PROVIDER], [PERSON] or [PATIENT LIST] name at the\n Select Patient(s): prompt. The [PRECEDENCE] in which\n these are searched may effect the list which is retrieved.\n \n To limit the search to a Treating Specialty, Provider/Person\n or Patient List, you may use the following optional syntax:\n S.<specialty name>,\n P.<provider or person name> or\nYou may wish to choose patients who do not appear on the CURRENT LIST, or\n L.<list name>\n respectively.\n \nFor detailed help on highlighted keywords, enter all or part of the\nkeyword below.\nto change the list from which selections are to be made. Either of\nthese may be accomplished by:\n \n PATIENT: You may select an INDIVIDUAL patient by entering his/her\n NAME, SSN, ROOM/BED, or ["LAST INITIAL_LAST FOUR"]\n at the Select Patient(s): prompt.\n \n
\n\n", "\n- \n\n
\n", "", "1991-11-06 15:09:00\n", "", "POSTMASTER\n", "", ""], ["383", "OR LASTI_LAST4", "'Last Initial_Last Four'\n", "", "", "\n \n2 FUNOF,IT (9876) 8 NIVEK,GAMMA (4324)\n3 MARLEY,JACOB (5678) 9 NIVEK,SIGMA (2379)\n4 MUFFET,LITTELLA M (7689) 10 SPRAT,JACK (2342)\n5 NEW,PATIENT (1234) 11 TURNER,TOMMY (2342)\n6 NIVEK,ALPHA (8796)\n \nSelect Patient(s): D6572\n \nThe program will respond with:\n \nConsistent with the existing DHCP convention you may enter the Patient's\nSelect Patient(s): D6572 DOE,WILLIAM C. 09-12-44 234236572\nLast Initial followed by the last four digits of his/her SSN to unambig-\nuously select a given patient. For example, if you wish to select William\nC. Doe, whose DOB is SEP 12, 1944 and whose SSN is 234236572, you enter:\n \n 1A ward list\n \n1 DOE,WILLIAM C. (6572) 7 NIVEK,BETA (3242)\n
\n\n", "", "", "1991-09-11 15:37:00\n", "", "POSTMASTER\n", "", ""], ["384", "OR LOCATION", "Hospital Location List Look-up\n", "", "", "\n \n2 ESSTEPON,GLORD (3234) 6 SPRAT,JACK (2342)\n3 KAPLON,DENNIS (3242) 7 TURNER,TOMMY (2342)\n4 MARLEY,JACOB (5678)\n \nSelect Patient(s): 1A \nThe current patient list will be cleared.\nLoading Ward Patient List...\n \n \n \nEntering all or part of a valid Hospital Location name at the prompt\n \n \n \n \n 1A ward list\n \n1 DOE,WILLIAM C. (6572) 7 NIVEK,BETA (3242)\n2 FUNOF,IT (9876) 8 NIVEK,GAMMA (4324)\n3 MARLEY,JACOB (5678) 9 NIVEK,SIGMA (2379)\n4 MUFFET,LITTELLA M (7689) 10 SPRAT,JACK (2342)\nSelect Patient(s) will cause the list to be rebuilt to include the\n5 NEW,PATIENT (1234) 11 TURNER,TOMMY (2342)\n6 NIVEK,ALPHA (8796)\n \nSelect Patient(s): 1-4 DOE,WILLIAM C. (6572) FUNOF,IT (9876) \n MARLEY,JACOB (5678) MUFFET,LITTELLA M (7689) \npatients at that location, and presented to you anew. For example,\nif you wish to choose from all patient's at ward 1A, you may enter:\n \n METHUSELA, O.C. patient list\n \n1 DOE,WILLIAM C. (6572) 5 MUFFET,LITTELLA M (7689)\n
\n\n", "", "", "1991-09-17 13:19:51\n", "", "POSTMASTER\n", "", ""], ["385", "OR PROVIDER", "Provider List Look-up\n", "", "", "\n \n1 DOE,WILLIAM C. (6572) 7 NIVEK,BETA (3242)\n2 FUNOF,IT (9876) 8 NIVEK,GAMMA (4324)\n3 MARLEY,JACOB (5678) 9 NIVEK,SIGMA (2379)\n4 MUFFET,LITTELLA M (7689) 10 SPRAT,JACK (2342)\n5 NEW,PATIENT (1234) 11 TURNER,TOMMY (2342)\n6 NIVEK,ALPHA (8796)\n \nSelect Patient(s): METHUSELA,O.C.\nThe current patient list will be cleared.\nLoading Provider Patient List...\nEntering all or part of a valid Provider's name at the prompt to\n \n \n \n \n METHUSELA,O.C. patient list\n \n1 DOE,WILLIAM C. (6572) 5 MUFFET,LITTELLA M (7689)\n2 ESSTEPON,GLORD (3234) 6 SPRAT,JACK (2342)\n3 KAPLON,DENNIS (3242) 7 TURNER,TOMMY (2342)\n4 MARLEY,JACOB (5678)\nSelect Patient(s) will cause the list to be rebuilt to include the\n \nSelect Patient(s): \npatients whose attending physician is listed as that provider, and\npresented to you anew. For example, if you wish to choose from all\npatient's assigned to Dr. Oldin C. Methusela, you may enter:\n \n 1A ward list\n \n
\n\n", "", "", "1991-09-17 13:43:31\n", "", "POSTMASTER\n", "", ""], ["386", "OR PERSON", "Personal Patient List Look-up\n", "", "", "\n \n1 DOE,WILLIAM C. (6572) 5 MUFFET,LITTELLA M (7689)\n2 ESSTEPON,GLORD (3234) 6 SPRAT,JACK (2342)\n3 KAPLON,DENNIS (3242) 7 TURNER,TOMMY (2342)\n4 MARLEY,JACOB (5678)\n \nSelect Patient(s): SMALLPOTATOES,WILLIAM A.\nThe current patient list will be cleared.\n \n \n \nEntering all or part of a valid (non-provider) Person's name at the \n \n \n \n \n BILL'S 1A patient list\n \n1 BLANDRU,AB (3333) 5 NIVEK,BETA (3242)\n2 MARLEY,JACOB (5678) 6 NIVEK,GAMMA (4324)\n3 NEW,PATIENT (1234) 7 NIVEK,SIGMA (2379)\n4 NIVEK,ALPHA (8796)\nprompt Select Patient(s) will cause the list to be rebuilt to include\n \nSelect Patient(s): ALL,'BLANDRU MARLEY,JACOB (5678) \n NEW,PATIENT (1234) NIVEK,ALPHA (8796)\n NIVEK,BETA (3242) NIVEK,GAMMA (4324) \n NIVEK,SIGMA (2379) \nthe patients in that person's PRIMARY patient list, and presented to\nyou anew. For example, if you wish to choose from all patient's\nin Mr. Bill Smallpotatoe's primary patient list, you may enter:\n \n METHUSELA,O.C. patient list\n \n
\n\n", "", "", "1991-09-17 13:37:57\n", "", "POSTMASTER\n", "", ""], ["387", "OR PATIENT LIST", "Patient List Look-up\n", "", "", "\n \n1 BLANDRU,AB (3333) 5 NIVEK,BETA (3242)\n2 MARLEY,JACOB (5678) 6 NIVEK,GAMMA (4324)\n3 NEW,PATIENT (1234) 7 NIVEK,SIGMA (2379)\n4 NIVEK,ALPHA (8796)\n \nSelect Patient(s): TEAM\n 1 TEAM 1A\n 2 TEAM 2B\n 3 TEAM 7B\nCHOOSE 1-3: 3 \nEntering all or part of a valid PATIENT LIST name at the prompt to\nThe current patient list will be cleared.\n \n \n TEAM 7B patient list\n \n1 BLANDRU,AB (3333) 9 NEW,PATIENT (1234)\n2 DOE,WILLIAM C. (6572) 10 NIVEK,ALPHA (8796)\n3 ESSTEPON,GLORD (3234) 11 NIVEK,BETA (3242)\n4 FUNOF,IT (9876) 12 NIVEK,EPSILON (4723)\n5 KAPLON,DENNIS (3242) 13 NIVEK,SIGMA (2379)\nSelect Patient(s) will cause the list to be rebuilt to include\n6 LATHAM,RASTY (1111) 14 SIMPSON,HOMER (9999)\n7 MARLEY,JACOB (5678) 15 SPRAT,JACK (2342)\n8 MUFFET,LITTELLA M (7689) 16 TURNER,TOMMY (2342)\n \nSelect Patient(s): 1-2,10-14 BLANDRU,AB (3333) DOE,WILLIAM C. (6572) \n NIVEK,ALPHA (8796) NIVEK,BETA (3242) \n NIVEK,EPSILON (4723) NIVEK,SIGMA (2379) \n SIMPSON,HOMER (9999) \nthe patients in that patient list, and presented to you anew.\nFor example, if you wish to choose from all patient's in the list\nnamed TEAM 7B you could enter:\n \n BILL'S 1A patient list\n \n
\n\n", "", "", "1991-09-17 13:31:25\n", "", "POSTMASTER\n", "", ""], ["388", "OR SEARCH PRECEDENCE", "Search Precedence for Patient Look-up\n", "", "", "\n \n LOCATION (WARD or CLINIC) --> PATIENT --> TREATING SPECIALITY -->\n PERSON (PROVIDER or NOT) --> PATIENT LIST --> CURRENT LIST.\n \nTherefore, if the user wishes to produce Dr. James Doe's PROVIDER list,\nand enters DOE,J and the search encounters a patient named DOE,JOHN, it\nwill ALWAYS return the patient first. Likewise, if the PATIENT LIST\nnames are prefixed with characters which exactly match Hospital locations,\nthen the WARD or CLINIC list will always be identified before the\ncorresponding PATIENT or TEAM list. We therefore recommend that you name\npersonal PATIENT LISTs by their owner's initials, followed by a number,\nThe precedence in which the Patient Look-up will search to determine what\nand TEAM LISTs by the word "TEAM" followed by a location or speciality,\netc.\nthe user's input means may influence the way in which input is interpreted,\nparticularly if patient's, provider's, or person's names coincide, or if\nteam lists are named identically with Hospital Locations.\n \nWhen input is received, the look-up will proceed to try to find a match\nin the following sequence:\n \n
\n\n", "", "", "1991-09-17 13:45:02\n", "", "POSTMASTER\n", "", ""], ["389", "OR TREATING SPECIALTY", "Treating Specialty Look-up\n", "", "", "\n \n1 BLANDRU,AB (3333) 9 NEW,PATIENT (1234)\n2 DOE,WILLIAM C. (6572) 10 NIVEK,ALPHA (8796)\n3 ESSTEPON,GLORD (3234) 11 NIVEK,BETA (3242)\n4 FUNOF,IT (9876) 12 NIVEK,EPSILON (4723)\n5 KAPLON,DENNIS (3242) 13 NIVEK,SIGMA (2379)\n6 LATHAM,RASTY (1111) 14 SIMPSON,HOMER (9999)\n7 MARLEY,JACOB (5678) 15 SPRAT,JACK (2342)\n8 MUFFET,LITTELLA M (7689) 16 TURNER,TOMMY (2342)\n \nSelect Patient(s): MEDICINE MEDICAL ICU/CCU \nEntering all or part of a valid TREATING SPECIALTY name at the prompt\nThe current patient list will be cleared.\nLoading Specialty Patient List...\n \n MEDICINE specialty list\n \n1 DOE,WILLIAM C. (6572) 8 NEW,PATIENT (1234)\n2 ESSTEPON,GLORD (3234) 9 NIVEK,ALPHA (8796)\n3 FUNOF,IT (9876) 10 NIVEK,BETA (3242)\n4 KAPLON,DENNIS (3242) 11 NIVEK,EPSILON (4723)\n5 LATHAM,RASTY (1111) 12 NIVEK,SIGMA (2379)\nto Select Patient(s) will cause the list to be rebuilt to include the\n6 MARLEY,JACOB (5678) 13 SPRAT,JACK (2342)\n7 MUFFET,LITTELLA M (7689) 14 TURNER,TOMMY (2342)\n \nSelect Patient(s): 1,2,8-11 DOE,WILLIAM C. (6572) \n ESSTEPON,GLORD (3234) NEW,PATIENT (1234) \n NIVEK,ALPHA (8796) NIVEK,BETA (3242) \n NIVEK,EPSILON (4723) \npatients assigned to that specialty, and presented to you anew. For\nexample, if you wish to choose from all patient's in the MEDICINE\ntreating specialty, you could enter:\n \n TEAM 7B patient list\n \n
\n\n", "", "", "1991-09-17 13:46:43\n", "", "POSTMASTER\n", "", ""], ["39", "XQ-USER-PATLKUP", "IDENTIFYING A PATIENT TO THE COMPUTER\n", "", "", "\nWhen the computer prompts 'PATIENT NAME:', there are a variety\n \n - PATIENT'S WARD - To identify an inpatient, you can enter a ward name,\n All patients currently on that ward will be displayed.\n \nSometimes, more than one patient will match what you have entered. The\nmatching names will be displayed with date of birth and SSN. You will be\nprompted to make a selection. Only 5 names are displayed at a\ntime, enter an '^' to stop the list or carriage return to see more.\n \n[EXAMPLES]...\nof ways you can respond to identify the patient to the computer.\n \n - FIRST LETTER OF LAST NAME AND LAST FOUR DIGITS OF SSN\n This is the quickest way for the computer to find the patient.\n \n - LAST 4 DIGITS OF SSN\n \n - LAST NAME, FIRST NAME - Partial names can be entered.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["390", "OR LASTI_LAST 4", "'Last Initial_Last Four'\n", "", "", "\n \n2 FUNOF,IT (9876) 8 NIVEK,GAMMA (4324)\n3 MARLEY,JACOB (5678) 9 NIVEK,SIGMA (2379)\n4 MUFFET,LITTELLA M (7689) 10 SPRAT,JACK (2342)\n5 NEW,PATIENT (1234) 11 TURNER,TOMMY (2342)\n6 NIVEK,ALPHA (8796)\n \nSelect Patient(s): D6572\n \nThe program will respond with:\n \nConsistent with the existing DHCP convention you may enter the Patient's\nSelect Patient(s): D6572 DOE,WILLIAM C. 09-12-44 234236572\nLast Initial followed by the last four digits of his/her SSN to unambig-\nuously select a given patient. For example, if you wish to select William\nC. Doe, whose DOB is SEP 12, 1944 and whose SSN is 234236572, you enter:\n \n 1A ward list\n \n1 DOE,WILLIAM C. (6572) 7 NIVEK,BETA (3242)\n
\n\n", "", "", "1991-11-06 15:10:00\n", "", "POSTMASTER\n", "", ""], ["391", "PRCHPM CS MENU", "LOG 1 CODE SHEETS MENU\n", "", "", "\nThis option allows the user to electronically generate LOG 1 code sheet\nequivalents. These 'code sheets' will provide a printout of the same data\nwhich goes on manually entered code sheets. The printout may be keypunched\nfrom in lieu of writing out code sheets by hand.\n
\n\n", "", "", "1991-06-14 00:00:00\n", "", "USER,ONE\n", "", ""], ["392", "PRCS-2237", "ENTERING REQUESTS\n", "", "", "\nSelect Item Display from the\nestimated and a contract is in place.\n \nCHOOSE FROM:\n 2 NON-REPETITIVE (2237) ORDER\n 3 REPETITIVE (PR CARD) ORDER\n 4 REPETITIVE AND NON-REP ORDER\n 5 ISSUE BOOK/INTERVAL ISSUE \n \n YOU MAY ENTER A NEW CPA FORM TYPE, IF YOU WISH\n ANSWER MUST BE 3-30 CHARACTERS IN LENGTH\nRequestors Menu.\n \nIf the item isn't in the Item Master File, create a Non-Repetitive Order.\nIf the item is in the Item Master File and lists the warehouse as one of\nthe vendors, create an Issue Book Request. If the item is in the Item \nMaster File, but doesn't list the warehouse as one of the vendors, create \na Repetitive/Non-Repetitive Order. The use of the Repetitive Order is \ndiscouraged. Create a 1358 order to request a service if the cost is\n
\n\n", "", "", "1994-04-21 16:06:04\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["393", "PRCHITEM HELP", "Help frame for Item Master No. field\n", "", "", "\n This X-REF will copy information from the ITEM MASTER\n NDC NATIONAL DRUG CODE\n UNIT COST ACTUAL UNIT COST\n UNIT OF PURCHASE UNIT OF PURCHASE\n PACKAGING MULTIPLE PACKAGING MULTIPLE\n MAXIMUM ORDER MAXIMUM ORDER \n UNIT CONVERSION FACTOR UNIT CONVERSION FACTOR\n SKU SKU \n NSN NSN \n FSC FEDERAL SUPPLY\n CLASSIFICATION\n file into the\n SUBACCOUNT SUBACCOUNT \n CONTRACT NUMBER CONTRACT # \n QUANTITY(442)*UNIT COST TOTAL COST \n AMENDMENTS file.\n Here is a list of the fields in the ITEM MASTER file\n and the fields in\n the AMENDMENTS file that the data is copied into. \n \n File 441 File 443.6\n VENDOR STOCK # VENDOR STOCK NUMBER\n
\n\n", "", "", "1994-07-06 12:47:33\n", "", "USER,ONE\n", "", ""], ["394", "PRCB ADD NEW TRANSACTION", "Add New Transaction (Ceiling)\n", "", "", "\nThis function allows the user to add a transaction to reflect the\nFTEE assignments and quarterly costs.\n \nYou can also use this option to withdraw funds from a Fund Control Point\nby entering a minus sign before the transaction dollar amounts.\n
\n\n", "", "", "1994-11-08 10:23:20\n", "", "USER,ONE\n", "", ""], ["395", "PRCD LOAD STANDARD DICTIONARY", "Load Standard Dictionary\n", "", "", "\nUse this option to load a standard dictionary.\n \n N O T E:\n \nSome users will see a "Fix Value:" prompt after the Status: \nprompt. This prompt is for users that have access to IFCAP \ncode. This prompt represents IFCAP code assigned to the \nentry.\n
\n\n", "", "", "1994-11-08 10:53:21\n", "", "USER,ONE\n", "", ""], ["396", "PRCB SINGLE TRANSFER", "Transfer From/To Control Point\n", "", "", "\nThis option will allow transferring of funds from control point to control\npoint. The Fund Distribution file will then be updated and transactions\nmade ready for release.\n \nYou can transfer funds among Control Points if the Control Points receive \ntheir money from the same fund and the funds are for the same quarter.\n
\n\n", "", "", "1994-11-08 13:31:40\n", "", "USER,ONE\n", "", ""], ["397", "PRCB ROLLOVER FCP BALANCE", "Quarterly Rollover Fund Control Point Balance\n", "", "", "\nThis report allows you to determine the amount of rollover funds for the \nquarter, the Control Points from which the rollover came, and the Control \nPoints that received the rollover funds.\n
\n\n", "", "", "1994-11-08 14:02:10\n", "", "USER,ONE\n", "", ""], ["398", "PRCB PRINT RANGE OF TRANS", "Range of Transactions\n", "", "", "\nUse this option to generate a listing of a range of funds distribution \ntransactions that you select. This report prints the transaction number, \nControl Point number, TDA number, transaction date, and a breakdown of \nfunding by quarter.\n
\n\n", "", "", "1994-11-08 14:15:57\n", "", "USER,ONE\n", "", ""], ["399", "PRCF INQ 410", "Control Point Activity File Inquiry\n", "", "", "\nThis option lists all of the transaction information available for a\ntransaction, including its source of funds, the date it was obligated,\nand who made the request.\n
\n\n", "", "", "1994-11-08 14:42:30\n", "", "USER,ONE\n", "", ""], ["4", "XQKEYALLOCATE", "USING THE 'Key Allocation' OPTIONS\n", "", "", "\nThese options are used to allocate and deallocate holders\n \nWhen done specifying the lists, you will be shown those keys and users\nyou have selected and you will be asked if you wish to proceed. If you\nrespond with a 'no' you may go back and edit your selection. Otherwise\nthe keys will then be assigned to the users specified. \n \nYou may 'de-select' a key or user by prefacing it with a '-'. You can\nalso use a MAIL GROUP to select a group of users.\nof security keys. The assignment of keys can be done in groups, or\nindividually. You will be prompted to list keys and users. You may assign\na single key to a group of users, or multiple keys to an individual user\nor multiple keys to a group of users.\n \nYou will be prompted for the [KEY] and the [HOLDER].\nSpecify each, one at a time, terminating the last with a <return>.\nFor additional help on these prompts type '?'.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["40", "XQ-USER-PATLKUP-EX", "EXAMPLES OF IDENTIFYING A PATIENT\n", "", "", "\nConsider the following patients:\n S4444 - would also uniquely identify and be much quicker\n SMITH - would match JOE and JANE and you be prompted for a choice.\n \nTo identify #3, you could enter:\n 4141 - this would match ALICE and JAMES\n S4141 - would uniquely identify ALICE\n SMY - this would also uniquely identify ALICE\n \n1. SMITH,JOE 222-33-4444\n2. SMITH,JANE 222-44-5555\n3. SMYTHE,ALICE 555-33-4141\n4. JONES,JAMES 222-33-4141\n \nTo identify #1, you could enter: \n 4444 - this would uniquely identify the patient\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["400", "PRCF INQ 442", "Procurement and Accounting Transactions Inquiry\n", "", "", "\nThis option creates a report of the processing history of the transaction, \nincluding the Control Point, the budget object code (BOC), and the item\ndescription.\n
\n\n", "", "", "1994-11-08 14:49:33\n", "", "USER,ONE\n", "", ""], ["401", "PRCB BOC ADD/EDIT", "Add/Edit BOC\n", "", "", "\nThis option allows you to add a new budget object code or change the \nname of an existing budget object code. Whenever the program offices \nin VA Central Office change the budget object codes that you use, you \nwill have to use this option to make the necessary changes to the \nBudget Object Code File. You can use this option to create new entries \nor to change the name or number of existing entries.\n
\n\n", "", "", "1994-11-08 14:59:24\n", "", "USER,ONE\n", "", ""], ["402", "PRCB CC LISTING/W BOC", "List Cost Centers with Associated BOC\n", "", "", "\nThis listing is similar to the cost center listing, but includes all the \nassociated budget object codes. The report generated by this option can \nbe very long unless you limit the report to a range of cost centers.\n
\n\n", "", "", "1994-11-08 15:16:21\n", "", "USER,ONE\n", "", ""], ["403", "PRCB ENTER CEILING TRANS", "Place Released Ceiling Transaction in CP File\n", "", "", "\nUse this option after you have Released all\noriginal transaction was posted. Fiscal service uses \nthis option to enter a ceiling transaction into a Control\nPoint file. Only use this option when a Control Point \nis being automated after funds have already been \nreleased through the funds distribution option.\nFunding (Ceiling) Transactions for your facility and\na Control Point is just now being automated, in other\nwords, the funds have already been released \nautomatically. You cannot re-release the ceiling, but\nyou can use this option to enter the ceiling amount \ninto the Control Point Official's balance. This option \nwill not place an entry onto the budget balance for the \nControl Point; because this entry was made when the \n
\n\n", "", "", "1994-11-08 15:33:05\n", "", "USER,ONE\n", "", ""], ["404", "PRCB RECALCULATE ALL FCP", "Recalculate All Fund Control Point Balances\n", "", "", "\nUse this option to recalculate all Fund Control Balances \nfor the Control Point Activity user. This option is \nincluded in your menu to update balances for all \nautomated Fund Control Points. This recalculation is \nnecessary when the computer "crashes" (loses power). \nThe transactions being processed when a "crash" occurs \ndo not update the Control Point records. Therefore, \nyou may need to use this option to recalculate the Fund \nControl Point balances in Fiscal.\n
\n\n", "", "", "1994-11-08 15:52:37\n", "", "USER,ONE\n", "", ""], ["405", "PRCB CLEAR LOCK", "Clear Program Lock\n", "", "", "\nThis option allows the user to clear a program lock and \ncontinue processing. This option clears a lock that \nhas been placed on batch transmission or on releasing \nthe budget figures for a station. This can occur when \nsomeone else is using the option and the system will \nnot allow a second person to perform the same function, \nor when a system error or power problem interrupts a \nfunction. Never proceed with further processing after \na lock until you have used this option to clear the lock.\n
\n\n", "", "", "1994-11-08 16:17:52\n", "", "USER,ONE\n", "", ""], ["406", "PRCSENRS", "Enter a Request (Section)\n", "", "", "\nThis function permits users with Requestor privileges to enter the\ninformation necessary for a 2237, 1358 and other requests.\nThe request is then available for review by the designated budget\nclerk before being passed to the Control Point Official for final\napproval.\n
\n\n", "", "", "1994-11-10 11:15:47\n", "", "USER,ONE\n", "", ""], ["407", "PRCSEDRS", "Edit a Request (Section)\n", "", "", "\nUse this option to change a temporary request that you already created. \nControl Point Requestors can only edit temporary requests that they created.\n
\n\n", "", "", "1994-11-10 11:19:34\n", "", "USER,ONE\n", "", ""], ["408", "PRCSDT", "Delete a Request (Section)\n", "", "", "\n \nUse this option to delete the request and remove it from the IFCAP system. \nControl Point Requestors can only delete temporary requests.\n \nWARNING: Once you delete a request from IFCAP using this option, you \n can not retrieve it.\n \n
\n\n", "", "", "1994-11-10 11:26:28\n", "", "USER,ONE\n", "", ""], ["409", "PRCS1358", "New 1358 Request (Section)\n", "", "", "\nUse a 1358 Order request to budget money for ongoing service \nexpenses, such as the utility bill, copier repair, rent, or postage. A 1358 \nOrder allows the Control Point to "obligate funds," or establish a budget \nfor ongoing services, so there will be money to pay the vendor when the \nmonthly or quarterly statement is due.\n
\n\n", "", "", "1994-11-10 11:32:16\n", "", "USER,ONE\n", "", ""], ["41", "XQRESTRICT-OPTION", "RESPONDING TO THE 'Select OPTION NAME' PROMPT\n", "", "", "\nYou can specify the options for which to restrict access.\n?? - To see the list of options you've already specified.\n \n??? - To see the list of options from which you may choose.\n \n-OPTION - To take a option off the list specified preceed it with a minus sign.\nspecify a single option, or a set of options.\n \nRespond with the name of the option(s), one at a time.\n \nYou may also respond with one of the following:\n \n^ - To exit\n \n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["410", "PRCS1358A", "Edit 1358 Request (Section)\n", "", "", "\nThis option allows requestors to edit 1358 requests\nwhich they have entered.\n
\n\n", "", "", "1994-11-10 11:37:15\n", "", "USER,ONE\n", "", ""], ["411", "PRCSTSS", "Request Status Report (Section)\n", "", "", "\nYou have to know the temporary transaction number to determine the status \nrejected. IFCAP tracks the status of all the items on your request, \nregardless of how many transactions were created from it. Therefore, the \nonly way to determine the status of your request AS YOU CREATED IT \nis to enter the temporary transaction number you created.\n \nNote: You can only display or print requests that you created.\nof a request. From the Requestors Menu, select Request Status Report \n(Section). At the Select Transaction Number: prompt, enter the temporary \ntransaction number you assigned to the request when you created it in \nIFCAP.\n \nYou cannot enter the PO number or permanent transaction number at the \nSelect Transaction Number: prompt because requests can be split into \nmultiple transactions of different types or some of your items can be \n
\n\n", "", "", "1994-11-10 11:40:32\n", "", "USER,ONE\n", "", ""], ["412", "PSO INTERVENTION MENU", "Description of Intervention Menu option\n", "", "", "\n PHARMACY INTERVENTION MENU\n \n \n INTM Pharmacy Intervention Menu\n \nThe menu it generates gives access to the options involved with the Pharmacy \nIntervention system. A short description of each module follows. More \ndetailed information appears under each option.\n \n \nPharmacy Intervention Menu\n \n \n \n NINT Enter Pharmacy Intervention\n EINT Edit Pharmacy Intervention\n PINT Print Pharmacy Intervention\n DINT Delete Intervention\n VINT View Intervention\n \n \n'Enter Pharmacy Intervention'\nThe PHARMACY INTERVENTION MENU option is the main menu for the \n This option is used to enter a entry into the APSP\n INTERVENTION file. This is where all interventions\n are recorded.\n \n'Edit Pharmacy Intervention'\n This option is used to edit an already existing entry in the Intervention f\nile\n \n'Print Pharmacy Intervention'\n This option is used to obtain a captioned printout of Pharmacy\nIHS Pharmacy Intervention system. The Pharmacy Intervention system is a \n Interventions for a certain date range. It will print out on\n normal width paper and can be queued to print at a later time.\n \n'Delete Intervention'\n This option is used to delete a intervention from the APSP INTERVENTION\n file. You may only delete a intervention that was entered on the same\n day.\n \n'View Intervention'\n This option is used to display Pharmacy Interventions in a captioned format\nmean to make the gathering and collection of interventions easier. It also allows \n.\n You may view more than one Intervention at a time.\n \nSelect Pharmacy Intervention Menu Option:\n \nfor more rapid analysis of the type of interventions occuring. The Pharmacy \nIntervention Menu generates a secondary menu of the options involved in the \nPharmacy Intervention system. This option appears both on the QA Main \nMenu option and the RX (Prescriptions) option as:\n
\n\n", "", "", "1990-09-16 00:00:00\n", "", "USER,ONE\n", "", ""], ["413", "PSO DELETE INTERVENTION", "", "", "", "\n DELETE INTERVENTION\nYou can choose the option by entering DINT at the\n \n Select Pharmacy Intervention Menu option:\n \nprompt.\n \nYou will be asked for the Intervention Date, however it is much easier to put \nin the patient's chart number or the patient's name in the usual manner. In the \nexample we will first enter a date that is in the past and you will see that the \ncomputer will not allow you to delete one in the past.\n \n \nSelect APSP INTERVENTION INTERVENTION DATE: T-15 JUN 30, 1990 ??\nSelect APSP INTERVENTION INTERVENTION DATE: T JUL 15, 1990 7-15-\n THATCHER,KATE IBUPROFEN 400MG TAB\nSURE YOU WANT TO DELETE THE ENTIRE ENTRY? YES\n \nThe DELETE INTERVENTION option is used to delete a Pharmacy \nIntervention that was made in error. You may only delte a intervention that \nwas entered on the same day that you are deleting. The option appears on the \nINTM (Pharmacy Intervention Menu) menu as:\n \n DINT Delete Intervention\n \n
\n\n", "", "", "1990-09-16 00:00:00\n", "", "USER,ONE\n", "", ""], ["414", "PSO EDIT INTERVENTION", "", "", "", "\n EDIT PHARMACY INTERVENTION\nYou can choose this option by entering EINT at the\n \n Select Pharmacy Intervention Menu option:\n \nprompt.\n \nYou are first asked to enter the intervention that you wish to edit. You may \nenter the date and then select from the choices shown (if more than one \nentered on the date selected) or you may enter the patient's chart number \nwhich is the prefered method. Once you have slected the intervention to edit \n \nyou may edit any of the fields in the manner you are used to. You may also an\nup arrow with the field name if you want to go directly to that field. The \nfollowing is an example of selecting the correct intervention by both entering \nthe date and then by entering the patient's name.\n \nSelect APSP INTERVENTION INTERVENTION DATE: T JUL 15, 1990 \nTHATCHER,KATE IBUPROFEN 400MG TAB\nINTERVENTION DATE: JUL 15,1990//\nPATIENT: THATCHER,KATE//\nPROVIDER: SHORR,GREGORY//\n \nPHARMACIST: MCCAIN,JAMES//\nDRUG: IBUPROFEN 400MG TAB//\nINSTITUTED BY: PHARMACY//\nINTERVENTION: INAPPROPRIATE DRUG//\nOTHER FOR INTERVENTION:\n 1>\nRECOMMENDATION: CHANGE DRUG//\nOTHER FOR RECOMMENDATION:\n 1>\nWAS PROVIDER CONTACTED: YES//\nThe EDIT PHARMACY INTERVENTION option is used to edit any \nPROVIDER CONTACTED: SHORR,GREGORY//\nRECOMMENDATION ACCEPTED: NO//\nAGREE WITH PROVIDER: NO//\nREASON FOR INTERVENTION:\n 1>\n \n \nSelect APSP INTERVENTION INTERVENTION DATE: THATCHER,KATE\n F 11-18-31 000820008 SE 1000\n28 7-15-1990 THATCHER,KATE IBUPROFEN 400MG TAB\nexisting Pharmacy Interventions. The option appears on the INTM \nINTERVENTION DATE: JUL 15,1990//\n(Pharmacy Intervention Menu) menu as:\n \n EINT Edit Pharmacy Intervention\n \n
\n\n", "", "", "1990-09-16 00:00:00\n", "", "USER,ONE\n", "", ""], ["415", "PSO ENTER INTERVENTION", "", "", "", "\n ENTER PHARMACY INTERVENTION\n \nPROVIDER CONTACTED: SHORR,GREGORY PHYSICIAN \n \nThe next question asked is if your recommendtaion was accepted. If you \nenter a 'N' you will then be asked if you agree with the provider for not \naccepting your recommendation.\n \nRECOMMENDATION ACCEPTED: NO\nAGREE WITH PROVIDER: NO\n \nThe next fields asked are word processing fields that you can use to enter a \nYou can choose this option by entering NINT at the\nmore descriptive account of the intervention and the possible impacts of the \ninterventions. None of these fields are used in the reporting process for sorting \nor anything but they will be displayed with the entry.\nIf you do not wish to enter anything you must hit the Enter or Return key for \neach field.\n \nREASON FOR INTERVENTION:\n 1>\nACTION TAKEN:\n 1>\n \nCLINICAL IMPACT:\n 1>\nFINANCIAL IMPACT:\n 1>\n Select Pharmacy Intervention Menu option:\n \nprompt.\n \nYou are first asked to put in the date of the intervention, you may enter any \nvalid Fileman format for dates. If you are not sure what they are you can \nenter a '?' at the prompt. If you are recording the intervention on the day it \n \noccured it is easiest just to enter a 'T' which stands for today.\n \nSelect APSP INTERVENTION INTERVENTION DATE: T JUL 15, 1990\n ARE YOU ADDING 'JUL 15, 1990' AS A NEW APSP INTERVENTION (THE\n4TH)? Y (YES)\n \nYou are then asked for the name of the patient. You can use the patient's chart number \nor enter the patient's lastname, first name.\n \n APSP INTERVENTION PATIENT: THATCHER,KATE\nThe ENTER PHARMACY INTERVENTION option is used to create any \n F 11-18-31 000820008 SE 100028\n \nNext enter the Drug name involved in the intervention. This drug must be in \nyour local drug file.\n APSP INTERVENTION DRUG: IBUPROFEN 400MG TAB\n \nEnter the provider involved:\nPROVIDER: SHORR,GREGORY PHYSICIAN IHS \n \nThen you are asked to enter the department which initiated the intervention.\nnew Pharmacy Intervention records. The recording of pharmacy \nThe default is the pharmacy. You can see the choices by entering '??' at the \nprompt.\n \nINSTITUTED BY: PHARMACY// ??\n This field is asking who initially brought up the need for an\n intervention. You should enter a '?' to see your choices.\n The choices currently offered include : Pharmacy, Nursing, Provider,\n Patient or Family, and Other (to catch everybody else).\n CHOOSE FROM:\n 1 PHARMACY\ninterventions allows the pharmacy to document any interventions it is doing \n 2 PROVIDER\n 3 NURSING\n 4 PATIENT OR FAMILY\n 5 OTHER\nINSTITUTED BY: PHARMACY//\n \nNext you will enter the type of intervention or the cause of the intervention. If \nnone of the categories fit the intervention you may enter Other for the \nintervention. If you enter 'Other' you will next see a word processing field \nwhich you can use to enter your own description. If you use 'Other' you will \nalong with allowing rapid retrieval and anyalysis of the types of interventions. \nnot be able to sort on what you enter.\n \nINTERVENTION: ??\n You are given Other'.\nCHOOSE FROM:\n 1 INAPPROPRIATE DRUG\n 2 INCORRECT DOSE\n 3 INCORRECT FORM OR ROUTE OF ADMINISTRATION\n 4 INCORRECT DOSING INTERVAL OR SCHEDULE\n 5 CONTRAINDICATION FOR USE\nThe option appears on the INTM (Pharmacy Intervention Menu) menu as:\n 6 ALLERGY\n 7 INCORRECT PATIENT\n 8 DRUG OF CHOICE NOT PRESCRIBED WITH NO APPARENT\n JUSTIFICATION\n 9 EXCESSIVE LENGTH OF THERAPY OR QUANTITY\n 10 NON-FORMULARY MEDICATION\n 11 OMMISSION ORDER\n 12 ORDER FOR DISCONTINUED MEDICATION\n 13 THERAPEUTIC DUPLICATION ORDERED\n 14 MEDICATION NOT PREPARED OR ADMINISTERED\n \n 15 TRANSCRIPTION ERROR\n 16 CLARIFICATION OF ORDER\n 17 OTHER\n \nEnter in your recommendation. You may also use 'Other" here and you will \nagain see a word processing field to enter your own recommendation. Same \nlimitations appply regarding sorting of reports.\n \n 7 CHANGE DOSING INTERVAL\n 8 NO CHANGE\n NINT Enter Pharmacy Intervention\n 9 OTHER\n \nRECOMMENDATION: 1 CHANGE DRUG\n \nIf a provider was contacted about your recommendation enter a 'Yes' at the \nnext prompt. If you enter a 'Y" you will then be asked for the name of the \nprovider contacted since many times they may be different from the original \nprovider.\n \nWAS PROVIDER CONTACTED: YES\n
\n\n", "", "", "1990-09-16 00:00:00\n", "", "USER,ONE\n", "", ""], ["416", "PSO PRINT INTERVENTIONS", "", "", "", "\n PRINT PHARMACY INTERVENTION\nYou can choose this option by entering PINT at the\n \n Select Pharmacy Intervention Menu option:\n \nprompt.\n \nFirst you enter the date range of the report by entering the start and go to \ndates. You may enter the standard Fileman formats for the dates.\n \n START WITH INTERVENTION DATE: FIRST// T-120\n \n GO TO INTERVENTION DATE: LAST// T\n \nNext you enter the device to print the report on. It is always recommended to \nenter a 'Q' to queue the report for some later time after the clinic or hospital is \nnot as busy. You cannot queue a report to your terminal or to a slave printer.\n \nDEVICE: \n \nThe report will print out sorted by the type of Intervention over a date range. \nYou will get a subcount and total count for the interventions. The subtotal and \nThe PRINT PHARMACY INTERVENTION option is used to print a report \ntotal will give you the number of interventions that your recommendation was \naccepted while the subcount and count will give you the number of \ninterventions of each type and the total number of interventions over the \nspecified date range.\n \nThe following is an example of printing a Pharmacy Intervention report.\n \n \n Example\n Print Pharmacy Intervention\nby date range of all the interventions sorted by the intervention type or what \n \n START WITH INTERVENTION DATE: FIRST// T-120\n GO TO INTERVENTION DATE: LAST// T\nDEVICE: 0;75;10\n \nPHARMACY INTERVENTION LISTING JUL 15,1990 13:18 PAGE 1\n \n \n \nINTERVENTION: ALLERGY\nthe reason for the intervention was. The option appears on the INTM \n \nINTERVENTION DATE: JUN 13,1990 PATIENT: KENNEDY,ANITA\nPROVIDER: CURTIS,CLAYTON PHARMACIST: ADAM,ADAM\nDRUG: PENICILLIN VK 250MG TAB INSTITUTED BY: PHARMACY\nRECOMMENDATION: CHANGE DRUG\nWAS PROVIDER CONTACTED: YES RECOMMENDATION \nACCEPTED: YES\nPROVIDER CONTACTED: CURTIS,CLAYTON\nREASON FOR\nPatient allergy to penicillin.\n(Pharmacy Intervention Menu) menu as:\nACTION TAKEN:\nPrescribed erythromycin\n \nSUBTOTAL 1\nSUBCOUNT 1\n \nINTERVENTION: INAPPROPRIATE DRUG\n \nINTERVENTION DATE: JUN 14,1990 PATIENT: WATERMAN,RAE\nPROVIDER: STRUMSTEAD,BARBARA PHARMACIST: MASON,BILL\n \nDRUG: IBUPROFEN 400MG TAB 40S: MCCAIN,JAMES\nDRUG: IBUPROFEN 400MG TAB INSTITUTED BY: PHARMACY\nRECOMMENDATION: CHANGE DRUG\nWAS PROVIDER CONTACTED: YES RECOMMENDATION \nACCEPTED: NO\nPROVIDER CONTACTED: SHORR,GREGORY\n -------------------\n--\nSUBTOTAL 1\nSUBCOUNT 2\n PINT Print Pharmacy Intervention\n \n--\nTOTAL 3\nCOUNT 4\n \n \n \n \n
\n\n", "", "", "1990-09-16 00:00:00\n", "", "USER,ONE\n", "", ""], ["417", "PSO VIEW INTERVENTIONS", "Describes option to view interventions in captioned format\n", "", "", "\n VIEW INTERVENTION\n \n Select Pharmacy Intervention Menu option:\n \nprompt.\n \nYou will first be asked which intervention you wish to view. You may either \nenter the date of the intervention and choose the correct one when listed or \nyou may enter the patient's chart number or name. The chart number or \nname would be the prefered method. You may keep entering another one, \nthen when you have entered all the ones you wish to view just enter a return at \n \nthe 'Another One' prompt.\n \nSelect APSP INTERVENTION INTERVENTION DATE: 6-13 JUN 13, 1990\n 1 6-13-1990 WATERMAN,RAE IBUPROFEN 400MG TAB\n 2 6-13-1990 KENNEDY,ANITA PENICILLIN VK 250MG TAB\nCHOOSE 1-2: 1\nANOTHER ONE: KENNEDY,ANITA F 12-24-22 002300023 SE 1000\n78 6-13-1990 KENNEDY,ANITA PENICILLIN VK 250MG TAB\nANOTHER ONE\n \nThe VIEW INTERVENTION option is used to view one or more \nYou will then be displayed the entries selected in a captioned format.\n \nINTERVENTION DATE: JUN 13, 1990 PATIENT: WATERMAN,RAE\n PROVIDER: MARTIN,GRETCHEN PHARMACIST: MASON,BILL\n DRUG: IBUPROFEN 400MG TAB INSTITUTED BY: PHARMACY\n INTERVENTION: INCORRECT DOSE RECOMMENDATION: CHANGE \nDOSE\n WAS PROVIDER CONTACTED: YES PROVIDER CONTACTED: \nMARTIN,GRETCHEN\n RECOMMENDATION ACCEPTED: YES\ninterventions in a captioned format. The option appears on the INTM \n REASON FOR INTERVENTION:\n OVERDOSE\n ACTION TAKEN:\n CONTACTED PROVIDER\n \nINTERVENTION DATE: JUN 13, 1990 PATIENT: KENNEDY,ANITA\n PROVIDER: CURTIS,CLAYTON PHARMACIST: ADAM,ADAM\n DRUG: PENICILLIN VK 250MG TAB INSTITUTED BY: PHARMACY\n INTERVENTION: ALLERGY RECOMMENDATION: CHANGE \nDRUG\n(Pharmacy Intervention Menu) menu as:\n WAS PROVIDER CONTACTED: YES PROVIDER CONTACTED: \nCURTIS,CLAYTON\n RECOMMENDATION ACCEPTED: YES\n REASON FOR INTERVENTION:\n Patient allergy to penicillin.\n ACTION TAKEN:\n Prescribed erythromycin\n CLINICAL IMPACT:\n None due to intervention\n FINANCIAL IMPACT:\n \n none\n \n VINT View Intervention\n \nYou can choose this option by entering VINT at the\n
\n\n", "", "", "1990-09-16 00:00:00\n", "", "USER,ONE\n", "", ""], ["42", "XQHELP-ASSIGNEDITOR", "ASSIGNING AND DE-ASSIGNING EDITORS\n", "", "", "\nThese options are used to assign editors of help frames.\n \nWhen done specifying the lists, you will be shown those frames and users\nyou have selected and you will be asked if you wish to proceed. If you\nrespond with a 'no' you may go back and edit your selection. Otherwise\nthe frames will then be assigned to the users specified. \n \nYou may 'de-select' a frame or user by prefacing it with a '-'. You can\nalso use a MAIL GROUP to select a group of users.\nThe assignment of frames can be done in groups, or individually\nYou will be prompted to list frames and users. You may assign\na single frame to a group of users, or multiple frames to an individual user\nor multiple frames to a group of users.\n \nYou will be prompted for the [HELP FRAME] and the [EDITOR].\nSpecify each, one at a time, terminating the last with a <return>.\nFor additional help on these prompts type '?'.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["43", "XQHELP-ASSIGNEDITOR-U", "RESPONDING TO THE 'Editor of help frame' PROMPT\n", "", "", "\n \n \n??? - To see the Help Frame File, editors of a particular help frame,\n the User File, or members of a mail group.\n \n-USER - To take a user off the list preceed it with a minus sign.\n \nG.GROUP - To specify a set of users as defined by a mailgroup, preceed the\n group name with 'G.'\nAt this prompt you can select users. You can assign a single user \nor a set of users. You can use a mailgroup to specify a group of users.\nRespond with the name of the user(s), one at a time.\nYou may also respond with one of the following:\n \n^ - To exit this option.\n \n?? - To see the list of editors you've already specified.\n
\n\n", "", "", "1989-03-08 10:19:00\n", "", "USER,ONE\n", "", ""], ["430", "YSCENP", "INPATIENT TEST LOOK UP OPTIONS\n", "", "", "\n This option searches all patients on a ward by team. If ALL TESTS\npunctuation.\n\nAdministration dates are also displayed. If only the last date is\nselected (optional) the last administration date is displayed along\nwith a letter. An "a" indicates only one test completion was found,\nwhile an "e" indicates 5 test completions. If ALL dates are selected,\nthe date of each administration will be shown.\nare selected, all administrations are displayed. If RECENT TESTS are\nselected, only administrations within the past 45 days are displayed.\n\nIf either CUSTOM or STANDARD batteries are selected, the names and\na running count of these patients are displayed. Test NAMES are\nprinted out (whether there was an actual test administration or not.)\nAn XXXXXXX indicates no completion was found. You may enter as many\ntests or interviews as you like. Enter test one at a time without\n
\n\n", "", "", "1989-04-13 00:00:00\n", "", "POSTMASTER\n", "", ""], ["431", "YSDIAG", "DSM-III Diagnosis Enter/edit\n", "", "", "\nHelp text has not yet been written for this section. \nIt will be, soon.\n
\n\n", "", "", "1989-04-13 00:00:00\n", "", "POSTMASTER\n", "", ""], ["432", "YS-GAF SCALE", "GLOBAL ASSESSMENT OF FUNCTIONING SCALE (GAF SCALE)\n", "", "", "\n100-91 Superior functioning in a wide range of activities, life's\n \n80-71: If symptoms are present, they are transient and expectable\n reactions to psychosocial stressors (e.g., difficulty \n concentrating after family argument); no more than slight\n impairment in social, occupational, or school functioning\n (e.g., temporarily falling behind in school work).\n \n70-61: Some mild symptoms (e.g., depressed mood and mild insomina) OR\n some difficult in social, occupational or school functioning\n (e.g., occasional truancy, or theft within the household), but\n problems never seem to get out of hand, is sought out by others\n generally functioning pretty well, has some meaningful \n interpersonal relationships.\n \n60-51: Moderate symptoms (e.g., flat affect and circumstantial speech,\n occasional panic attacks) OR moderate difficulty in\n social, occupational, or school functioning (e.g., few\n friends, conflicts with co-workers).\n \n50-41: Serious symptoms (e.g., suicidal ideation, severe obsessional\n rituals, frequent shoplifting) OR any serious impairment in\n because of his or her many positive qualities. No symptoms.\n social, occupational, or school functioning (e.g., no friends,\n unable to keep a job).\n \n40-31: Some impairment in reality testing or communication (e.g., \n speech is at time illogical, obscure or irrelevant) OR\n major impairment in several areas, such as work or school,\n family relations, judgment, thinking, or mood (e.g., \n depressed man avoids friend, neglects family, and is unable\n to work; child frequently beats up younger children, is\n defiant at home and is failing at school).\n \n \n30-21: Behavior is considerably influenced by delusions or \n hallucinations OR serious impairment in communication or\n judgment (e.g., sometimes incoherent, acts grossly\n inappropriately, suicidal preoccupation) OR inability to\n function in almost all areas (e.g., stays in bed all day,\n no job, home or friends).\n \n20-11 Some danger of hurting self or others (e.g., suicide attempts\n without clear expectations of death, frequently violent, manic\n90-81: Absent or minimal symptoms (e.g., mild anxiety before an exam),\n excitement) OR occasionally fails to maintain minimal personal\n hygiene (e.g., smears feces) OR gross impairment in communication\n (e.g., largely incoherent or mute).\n \n10-1: Persistent danger of severely hurting self or others (e.g.,\n recurrent violence) OR persistent inability to maintain\n minimal personal hygiene OR serious suicidal act with clear\n expectation of death.\n good functioning in all areas, interested and involved in a wide\n range of activities, socially effective, generally satisfied\n with life, no more than everyday problems or concerns (e.g., an\n occasional argument with family members).\n
\n\n", "", "", "1993-08-09 16:00:00\n", "", "USER,ONE\n", "", ""], ["433", "YS-AXIS 4", "SEVERITY OF PSYCHOSOCIAL STRESSORS SCALE: ADULTS\n", "", "", "\nCODE CATASTROPHIC ACUTE EVENTS (EXAMPLES) ENDURING CIRCUMSTANCES (EXAMPLE)\n school; child left neighborhood\n home \n \n 3 MODERATE Marriage; marital Marital discord; \n separation; loss of serious financial \n job; retirement; problems; trouble with\n miscarriage boss; being a single\n parent\n \n 4 SEVERE Divorce; birth of Unemployment; poverty\n \n first child \n \n 5 EXTREME Death of spouse; Serious chronic illness\n serious physical in self or child;\n illness diagnosed; ongoing physical or sexual\n victim of rape abuse \n \n 6 CATASTROPHIC Death of child; Captivity as hostage;\n suicide of spouse; concentration camp\n devastating natural experience\n 1 NONE No acute events that No enduring circumstances\n disaster \n \n 0 INADEQUATE INFORMATION or no change in condition\n \n may be relevant to the that may be relevant to the\n disorder disorder\n \n 2 MILD Broke up with boy Family arguments; job\n friend or girl friend; dissatisfaction;\n or graduated from residence in high-crime\n
\n\n", "", "", "1989-04-13 00:00:00\n", "\n- \n\n
\n", "POSTMASTER\n", "", ""], ["434", "YS-PSYCHOSOCIAL STRESSORS", "PSYCHOSOCIAL STRESSORS\n", "", "", "\nTYPES OF PSYCHOSOCIAL STRESSORS TO BE CONSIDERED:\nassociates or nonconjugal family members, e.g., illness of best friend,\ndiscordant relationship with boss.\n \n 4. OCCUPATIONAL: includes work, school, homemaking, e.g., unemployment\nretirement, school problems.\n \n 5. LIVING CIRCUMSTANCES: e.g., change in residence, threat to\npersonal safety, immigration.\n \n 6. FINANCIAL: e.g., inadequate finances, change in financial\n \nstatus.\n \n 7. LEGAL: e.g., arrest, imprisonment, lawsuit, or trial.\n \n 8. DEVELOPMENTAL: phases of the life cycle, e.g., puberty,\ntransition to adult status, menopause, "becoming 50".\n \n 9. PHYSICAL ILLNESS OR INJURY: e.g., illness, accident, surgery,\nabortion.\n \n 1. CONJUGAL (MARITAL AND NONMARITAL): e.g., engagement, marriage, \n 10. OTHER PSYCHOSOCIAL STRESSORS: e.g., natural or man-made\ndisaster, persecution, unwanted pregnancy, out-of-wedlock birth,\nrape.\n \n 11. FAMILY FACTORS (children and adolescents): In addition to the\nabove, for children and adolescents the following stressors may be\nconsidered: cold, hostile, intrusive, abusive, conflictual or\nconfusingly inconsistent relationship between parents or toward child;\nphysical or mental illness in a family member; lack of parental \nguidance or excessively harsh or inconsistent parental control,\ndiscord, separation, death of spouse.\ninsufficient, excessive, or confusing social or cognitive stimulation,\nanomalous family situation, e.g., complex or inconsistent parental\ncustody and visitation arrangements; foster family; institutional\nrearing; loss of nuclear family.\n \n \n 2. PARENTING: e.g., becoming a parent, friction with child, illness\nof child.\n \n 3. OTHER INTERPERSONAL: problems with one's friends, neighbors,\n
\n\n", "", "", "1993-08-09 15:55:00\n", "\n- \n\n
\n", "POSTMASTER\n", "", ""], ["435", "YS-GEN MODIFIER", "SPECIFYING CURRENT SEVERITY OF DISORDER\n", "", "", "\nMILD: Few, if any, symptoms in excess of those required to make the\n diagnosis. Symptoms markedly interfere with occupational\n functioning or with usual social activities or relationships\n with others.\n \nIN PARTIAL REMISSION OR RESIDUAL STATE: The full criteria for the\n disorder were previously met, but currently only some of the\n symptoms or signs of the illness are present. In partial\n remission should be used when there is expectation that the\n person will completely recover (or have a complete remission)\n within the next few years, as, for example, in the case of a\n diagnosis. Symptoms result in only minor impairment in occuptional\n Major Depressive Episode. Residual state should be used when\n the next few years, as, for example, in the case of Autistic\n Disorder or Attention Deficit Hyperactivity Disorder. (Residual\n state should not be used with Schizophrenia, since by tradition\n there is a specific residual type of Schizophrenia.) In some\n cases the distinction between in partial remission and residual\n state will be difficult to make.\n \nIN FULL REMISSION: There are no longer any symptoms or signs of the\n disorder. The differentiation of in full remission from\n functioning or in usual social activities or relationships with\n recovered (no current mental disorder) requires consideration\n of the length of time since the last period of disturbance, and\n the need for continued evaluation or prophylactic treatment.\n others.\n \nMODERATE: Symptoms or functional impairment between "mild" and \n "severe".\n \nSEVERE: Several symptoms in excess of those required to make the\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: AXIS 4
\n \n
\n
\n", "", "1993-08-09 15:49:00\n", "", "POSTMASTER\n", "", ""], ["436", "YS-LIST-OF-TESTS", "LISTING OF TESTS & INTERVIEWS\n", "", "", "\n"CODE" presents names of tests and interviews listed in alphabetical\norder by code designation only.\n \n"TITLE" presents names of tests and interviews listed in alphabetical\norder by code designation followed by full title of the instrument.\n \n"DESCRIPTION" presents a detailed summary of each test and\ninterview which includes code and name of test or interview, author,\npublisher ,form, number of items, scales (if applicable), etc.\n
\n\n", "", "", "1989-04-13 00:00:00\n", "\n- \n\n
\n", "POSTMASTER\n", "", ""], ["437", "YS-PHY-EXAM-NORM", "IS THE PHYSICAL EXAM NORMAL\n", "", "", "\n"NO" allows you to omit the system or enter an abnormal description\nof the system.\n \n"YES" automatically enters a "within normal limits" description of\nthe system.\n
\n\n", "", "", "1989-04-13 00:00:00\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["438", "NURA-ASSIGNMENT SELECTION", "Selecting Assignments\n", "", "", "\nWHEN MAKING SELECTIONS, A RANGE OF NUMBERS CAN BE SELECTED BY USING A \nDELETED AND FOLLOW THAT SELECTION BY AN @.\n E.G. 1@ 1-2@ 1@,3@ 1-2@,4-5@ 1@,3-4@\n ARE EXAMPLES OF VALID SELECTIONS.\n \nTO ADD NEW POSITIONS ENTER AN 'N' INTO THE SELECTION LIST.\n \nEDITING, DELETING AND ADDING POSITIONS CAN BE DONE THE SAME IN\nSELECTION.\n E.G. 1@,2,N 1-2,3@ 1,N 2@,N\n ARE EXAMPLES OF VALID SELECTIONS.\nHYPHEN AND MULTIPLE SELECTIONS CAN BE MADE BY SEPARATING THEM BY COMMAS.\n \n E.G. 1 1-2 1,3 1-2,4-5 1,3-4\n ARE EXAMPLES OF VALID SELECTIONS.\n \nTO EDIT POSITIONS, SELECT THE NUMBER(S) OF THE ASSIGNMENT(S) TO BE EDITED.\nTHE EXAMPLE ABOVE SHOWS VALID SELECTIONS.\n \nTO DELETE POSITIONS, SELECT THE NUMBER(S) OF THE ASSIGNMENT(S) TO BE\n
\n\n", "", "", "1990-07-12 09:17:00\n", "", "USER,ONE\n", "", ""], ["439", "GMRV-BLOOD PRESSURE RATE HELP", "Blood Pressure\n", "", "", "\nAnswer must be 5-11 characters in one of the following format.\n \nE.g. 120/80 (systolic pressure/diastolic pressure) or\n 120/100/80 (systolic/intermediate/diastolic)\n \n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["44", "XQHELP-ASSIGNEDITOR-H", "RESPONDING TO THE 'Select help frame' PROMPT\n", "", "", "\n \n editors of a help frame, the User File, or members of a mail\n group.\n \n-FRAME To take a frame off the list specified preceed it with a minus sign.\nAt this prompt you can select help frames. Respond with the name of the\nhelp frames, one at a time. You may also respond with one of the following:\n \n^ - To exit this option.\n \n?? - To see the list of help frames you've already specified.\n \n??? - To see the list of frames from which you may choose, the current\n
\n\n", "", "", "1989-03-08 10:44:00\n", "", "USER,ONE\n", "", ""], ["440", "GMRV-TEMPERATURE RATE HELP", "Temperature\n", "", "", "\nAnswer must be numeric with a maximum of one decimal place.\n \n O = ORAL C=CORE\n R = RECTAL T=TYMPANIC\n A = AXILLARY S=SKIN or\n site defined types.\n \nDefault: Site configurable\n \nE.g., 37R read as 37 C RECTAL\n 98.6O read as 98.6 F ORAL\n \n \nA number that is larger than or equal to 45 will be considered as a\nFarenheit temperature, and any number less than 45 will be considered as a \nCentigrade temperature.\n \nA letter qualifier can be appended to the end of the temperature reading. \nIf no letter is added the reading will be considered as an ORAL temperature.\nThe following is a list of valid letters and the types of temperature:\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["441", "GMRV-RESPIRATION RATE HELP", "Respiration\n", "", "", "\nAnswer must be numeric between 0 and 99 with no decimal places.\n \nA qualifier is optional. If an alpha qualifier is appended to the end of\nthe number, the qualifier has to be defined in the Vital Site File 120.52.\n \nE.g., 23C or 23c read as 23 CONTROLLED VENTILATOR\n \n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["442", "GMRV-PULSE RATE HELP", "Pulse\n", "", "", "\nAnswer must be numeric between 0 and 300 with no decimal places.\n C = CAROTID O=OTHER or\n site defined qualifiers.\n \nDefault: Site configurable\n \nE.g., 76 or 76R for 76 RADIAL\n 76A or 76a for 76 APICAL\n \n \nIf no letter is appended to the end of the pulse, the reading will be\nconsidered as a RADIAL pulse. If a letter is appended to the end of\nthe reading then the following is a list of valid letters, and the types\nof pulse they represent:\n \n R = RADIAL P=PERIPHERAL\n A = APICAL B=BILATERAL PERIPHERALS\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["443", "GMRV-HEIGHT RATE HELP", "Height\n", "", "", "\nThe entry for height must be a number appended with a qualifier to\nSome examples of valid entries are:\n \n 72I,E (for ESTIMATED)\n 147C\n 160CM\n 5F10I\n 6FT1IN\n 5'9"\nrepresent the value either in the English scale or the Metric system. If\nyou wish to enter a height in Metric system, append 'C' or 'CM' at the end\nof the number. Add 'F' or 'FT' or ' for feet and 'I' or 'IN' or '"' for\ninches to represent the value in English scale.\n \nAn optional qualifier from the GMRV Qualifier file (#120.52) can be\nappended to the end of value separated with ','.\n \n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["444", "GMRV-WEIGHT RATE HELP", "Weight\n", "", "", "\nThe weight entered must be a number + L(or l) or K(k) + an alpha \n \nSome examples of valid entries are:\n 176l or 176LA\n 80KE or 80ke\nDO NOT enter a number such as 120.0 for 120.\n \ncharacter for weight (optional).\n \nThe character L or l expresses the weight in the English scale pound,\nwhile K or k in the Metric scale kilogram.\n \nThe alpha character for weight is the first character for types of weight\nsuch as A=ACTUAL, E=ESTIMATED, D=DRY or site defined qualifiers for weight.\nThis character is optional. The default is ACTUAL.\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["445", "GMRV WARD/PAT SEL", "", "", "", "\n Type an A to get all patients on the unit,\n an S to get be able to select certain rooms on the unit,\n a P to get single patients\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["446", "GMRV NO ROOM", "", "", "", "\n NO ROOMS EXIST IN THE WARD LOCATION FILE (#42) FOR THIS WARD!!\n \n You must either select the (A)ll patients on this ward or (P)atient\n options to edit vitals on this ward.\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["447", "GMRV-CHOOSE RATE HELP", "Additional Vitals Help\n", "", "", "\nInformation regarding data entry is available for the following\nvitals/measurements.\n \n 1. [TEMPERATURE] 2. [PULSE]\n 3. [RESPIRATION] 4. [BLOOD/PRESSURE]\n 5. [HEIGHT] 6. [WEIGHT]\n
\n\n", "\n- \n\n
\n", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["448", "GMRV-ADMIN SCHED", "Schedule\n", "", "", "\nThe administration schedule is the frequency that an order will be\nadministered to the patient. Some examples are:\n \n QID (0900-1300-1700-2100)\n ONE TIME\n BID\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["449", "GMRV-ORD. ADDL INFO", "Additional Order Information\n", "", "", "\nAdditional order information includes any special instructions that\naccompany this order that have not been accounted for in the previous\nqueries.\n \n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["45", "XQHELP-NEWFRAMES", "USING THE 'New/Revised Help Frame' OPTION\n", "", "", "\nThis option will produce a fileman generated print of all those\nThe listing will show the help frame header, formal name, date entered,\nlast date updated, and author.\nhelp frames which have been updated during a certain specified time\nrange. It can be used for the purpose of determining which help\nframes have been created or revised recently.\n \nIt will first prompt for a range of help frame names. This allows\nfor the selective viewing of new frames by package prefix.\n \nIt will then prompt for the LAST DATE UPDATED range.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["450", "GMRVOR-ADMIN SCHED", "Schedule\n", "", "", "\nThe administration schedule is the frequency that an order will be\nadministered to the patient. Some examples are:\n \n QID (0900-1300-1700-2100)\n ONE TIME\n BID\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["451", "GMRVOR-ORD. ADDL INFO", "Special Instructions\n", "", "", "\nThis data represents any special instructions that accompany this order\nthat have not been accounted for in the previous queries.\n \n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["452", "NURS-LOCATION-DELETE", "Deleting a Nursing Location\n", "", "", "\nA NURSING LOCATION CANNOT BE DELETED!!\n \n 3. Assign the corresponding MAS location(s) for the inactivated nursing\n location to a new or already existing nursing location, remembering\n that all FILE 42 ward location entries must be associated with an\n active (WARD STATUS FIELD) nursing location, including MASONLY.\n \n 4. Delete the MAS location entry(s) for the old/original nursing\n location to be deactivated.\n \n 5. Deactivate nursing locations which are receiving the MAS locations\n \n referenced in step 3 (excluding MASONLY). Reactivate these wards\n using the WARD ACTIVATION PATIENT UPDATE option (NURSPT-WRDACT). This\n process will place patients from the closed unit on their new locations\n in the Nursing System.\nTo simulate a deletion:\n \n 1. Run the WARD DEACTIVATION PATIENT UPDATE OPTION (NURSPT-WRDINA) to: a)\n remove patients from the unit of the simulated deletion and b) set the\n PATIENT CARE STATUS Field of this nursing location to inactive.\n \n 2. Set the WARD STATUS Field of the nursing location to (I) inactive. \n
\n\n", "", "", "1992-01-30 08:16:00\n", "", "USER,ONE\n", "", ""], ["453", "NURS-PRINTER QUEUE", "Selecting a printer for reports\n", "", "", "\n[Printed] Nursing reports must be queued!!\n to be used.\n \n e.g. DEVICE: PRINTER<RET>\nTo queue a report, execute the following steps:\n \n 1. At the DEVICE: prompt, type in a 'Q'.\n \n e.g. DEVICE: Q<RET>\n \n \n 2. At the second DEVICE: prompt, type in the name of the printer\n
\n\n", "\n- \n\n
\n", "", "1996-01-23 18:36:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["454", "NURS-PRINTED", "Printed Reports\n", "", "", "\nPRINTED - Data sent to a printer versus data which is viewed on a\n terminal screen.\n
\n\n", "", "", "1990-07-10 00:00:00\n", "", "USER,ONE\n", "", ""], ["455", "NURS-PATIENT FLAG", "Explanation of the Patient Care Flag/Status\n", "", "", "\nDoes Nursing provide patient care on this ward?\nother means may cause the NURS Patient File to contain incorrect data.\n \nFor additional help on how this field should be set please type [MORE].\n \nA Patient Care Status flag of "A" (ACTIVE) indicates that direct patient care\nis being provided on the Nursing location. This field will contain an "I"\n(Inactive) if no patient care activity is present or if the location is used\nfor other Nursing education and administrative functions.\n \nThe Ward Activation (NURSPT-WRDACT) and Ward Deactivation (NURSPT-WRDINA)\nOptions should be used to update this field. Editing of this field via any\n
\n\n", "\n- \n\n
\n", "", "1992-03-02 08:43:00\n", "", "USER,ONE\n", "", ""], ["456", "NURS-INACTIVE FLAG", "Explanation of the ward status/inactive flag.\n", "", "", "\nIs this location used by the Nursing package?\nFor additional help on how this field should be set please type [MORE].\n \nThe Ward Status field indicates active and inactive locations in the\nNursing System. To designate this field as "A" (ACTIVE), enter an "A"\nin the Ward Status field. If this location has been closed and all Nursing\nactivities (e.g., patient care, Nursing education, active staff and\nadministration functions) have ceased, then enter an "I" for "Inactive" in\nthe Ward Status field.\n \n
\n\n", "\n- \n\n
\n", "", "1991-03-25 10:38:00\n", "", "USER,ONE\n", "", ""], ["457", "NURS-ADDITIONAL STATUS HELP", "Additional Help on Setting Status Flags\n", "", "", "\nSeveral different scenarios may arise when setting the Patient Care Status and\n wards that have no corresponding Nursing location. The Patient Care Status\n field should be set to "I" (Inactive) and the Ward Status field should be\n set to "A" (to indicate ACTIVE).\n \n3. A non-clinical Nursing location converted to performing patient care, OR a\n newly created patient care location: Run the Ward Activation\n (NURSPT-WRDACT) Option to change the Patient Care Flag to "A" (Active).\n \n4. A Nursing location converted from patient care to administrative/other\n function: Run the Ward Deactivation (NURSPT-WRDINA) Option, which will\nthe Ward Status fields. Below are some examples on how both fields should be \n change the Patient Care Flag to "I" (Inactive).\n \n5. A Nursing location terminates all Nursing functions:\n a. The Ward Deactivation (NURSPT-WRDINA) Option should be run for this\n location. This will set the Patient Care Flag to "I" (Inactive).\n b. Any corresponding MAS wards for this Nursing location should be moved\n to new/existing Nursing locations which have a Ward Status of Active.\n c. Set the Ward Status to "I" (Inactive) for the Nursing location that\n has terminated its Nursing function.\n \nset.\n6. A Nursing location which has a Ward Status of Inactive in the Nurs\n Location File, now performs some Nursing function: Enter an "A" in the\n Ward Status field and set the Patient Care Statis field to "I" (Inactive).\n \n1. Creating a new Nursing location: The Ward Status field should be set to\n an "A" to indicate active, and the Patient Care Status field should\n be set to "I" (Inactive).\n \n2. The MASONLY Nursing location: This location is used to associate all MAS\n
\n\n", "", "", "1991-03-25 10:53:00\n", "", "USER,ONE\n", "", ""], ["458", "GMRG-MENU LEGEND", "Menu Features\n", "", "", "\nTo interpret the above list of selections use the following legend:\n \n When text appears within an entry surrounded by square brackets:\n 1. If the entry was previously selected, this text was entered to\n further clarify the entry.\n 2. If the entry was not previously selected, then what is inside will\n be used as a default value.\n \n A '**' before an entry means the entry has been previously selected\n on this patient's care plan. On certain terminals, the\n entry will also be highlighted.\n \n A '+' before an entry means that another list of choices exists for\n this entry. Thus if this entry is chosen, another list of\n selections will appear to further define this entry.\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["459", "GMRG-DELETING ENTRIES", "Deleting Selections\n", "", "", "\nTo delete a previously selected entry from the patient data, enter a\nNOTE: Data is not actually being deleted because an audit trail has been\n established to track the patient data at any point in time.\nselection number, or range of selections separated by a hyphen (-), and \nthen enter an '@' afterwards.\n \n E.g. 1@ - deletes selection 1.\n 1@,3@ - deletes selections 1 and 3.\n 1-2@ - deletes selections 1 and 2.\n 2@,4-5@ - deletes selections 2, 4 and 5.\n \n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["46", "XQHELP-MOREOPT", "MORE OPTIONS IN THE HELP PROCESSOR\n", "", "", "\nThe Help Processor also includes the following options:\n last updated.\n \n \n \n \n \n \n \n[ASSIGN EDITORS] - Allows the author of a help frame to assign editors\n to one or more frames.\n \n[DE-ASSIGN EDITORS] - Allows the author of a frame to take away editorship\n privileges for one or more frames.\n \n[NEW/REVISED FRAMES] - Produces a listing of frames by package, and date\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 15:33:00\n", "", "USER,ONE\n", "", ""], ["460", "GMRG-APPEND TEXT", "Adding Text\n", "", "", "\nTo add/append text to clarify an entry:\n text.\n \nOR if you are only appending text to one entry, you may type the\n entry number followed by a ';' and the text you wish to append.\n \n E.g. 1;further information,3;additional clarification\n \n 1. Enter the entry number, or range of entries separated by a hypen (-),\n and enter a ';' afterwards.\n \n E.g. 1; or 1;,3; or 1-3; or 2;,4-6;\n \n 2. After this an enter/edit the 'appended text' prompt for each selected\n entry will be displayed at which time you may enter/edit appended\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["461", "GMRG-INTERNAL TEXT", "Bracketed Text\n", "", "", "\nTo edit/add text within the square brackets for an entry:\n \nOR if there is only one set of square brackets for an entry containing\n bracketed text that you wish to edit, you may enter the entry number\n followed by a '/' and the text you wish to insert in the brackets.\n \n E.g. 1/clarifier,4/text to clarify\n \n \nREMEMBER: If you select an entry with bracketed text, and do not edit the\n text you will be given the default value.\n \n 1. Enter the entry number, or a range of entries separated by a hyphen (-),\n and enter a '/' afterward.\n \n E.g. 1/ or 1/,3/ or 3-4/ or 2/,6-8/\n \n 2. For each of the entries you have selected, you will be asked to\n edit/add the text within the square brackets.\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["462", "GMRG-SELECTIONS", "Making Selections\n", "", "", "\nWhen prompted to select the numbers of the desired entry(ies)\n selection list to add additional text for the term.\n 6. OR you can do a [COMBINATION] of any of the above options.\nyou may do the following:\n 1. [ADD] the entry to the patient data.\n 2. [DELETE] the entry from the patient data.\n 3. [APPEND] text to the entry to further clarify the entry for\n the patient.\n 4. If the entry has square brackets in it, you can edit the\n [INTERNAL TEXT] of the entry.\n 5. Type an 'A' if 'Additional Text: ' appears at the end of the\n
\n\n", "\n- \n\n
\n", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["463", "GMRG-ADD ENTRIES", "Add selections\n", "", "", "\nTo add an entry to the patient data do the following:\n \n 1. Enter the entry number, or range of entries separated by a hypen(-).\n \n E.g. 1 or 1,3 or 1-3 or 2,4-6,8\n \nNOTE: If you append text to, or edit internally bracketed text\n of an entry not previously selected, you add it by default.\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["464", "GMRG-COMBINED ENTRY", "Combined Selections\n", "", "", "\nThe following are examples of some combined options that can be executed\n selection 4).\n 2/text,3;/ will insert 'text' between the brackets for\n selection 2, allow appending of text and editing\n of bracketed text for selection 3. Also these\n entries will be added if not previously chosen.\n 1-3,A will add selections 1, 2, 3 and additional text\n for this term.\nat the selection prompt:\n \n E.g. 1;text,4-5 will add selections 4, 5 and append 'text' to\n selection 1 (if selection 1 was not previously\n chosen this will also add selection 1).\n 2-3@,4/ will delete selections 2, 3 and allow you to\n edit the bracketed text of selection 4 (if selection\n 4 was not previously chosen this will also add\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["465", "GMRG-COMPLETE SELECTION HELP", "Detailed Selection Help\n", "", "", "\nWhen prompted to select the number(s) of the entry(ies) you wish to choose,\n 7. Type '??' to get this help screen.\n 8. Type '???' to see a definition of terms on this screen\n 9. Type <return> to go back up to a previous level of selections.\nAlso if you need help understanding the [selection list], please choose\nthe appropriate related help frame.\nin addition to making selections you may:\n 1. Type '^R' to Relist the above menu.\n 2. Type '^P' to Print/View the patient's data previously entered.\n 3. Type '^D' to Print/View the patients demographic data.\n 4. Typing '-' will allow you to view the previous frame if such\n a screen exists.\n 5. Type an '^' to exit the application.\n 6. Type '?' for help on how to [make selections].\n
\n\n", "\n- \n\n
\n", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["466", "GMRG-EDIT CHOICES", "Edit choices\n", "", "", "\nYou may make the following choices at this prompt:\n 6. You may change the display order of an item by entering the item\n number from the list followed by a 'D'. E.g. 1D will edit the\n display order of item number 1.\n 1. Enter 'A' to add more items for the current term.\n 2. Enter 'T' to edit the information that is displayed in the header\n for the current term.\n 3. You may choose one of the items in the above list and edit the\n information it contains by entering the item number from the list.\n 4. To delete a selection from the above list, enter a number followed\n by an '@'. E.g. 2@\n 5. Enter 'R' to redisplay the selection list.\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["467", "GMRG-MORE HELP", "Advanced Selection Help\n", "", "", "\nThere are three advanced features of the Text Generator that can be used\n select the appropriate one. If there are multiple ways to get to that\n aggregate term within a prime document, the user will be asked which path\n to use to get to it.\nSCRIPTING:\n By typing an open square bracket followed by the name of a template, the\n user can select a template to use in data entry. This template is a pre-\n selected set of data that can be selected and modified for the patient.\nTRAILING COMMA NOREDISPLAY:\n If the user ends a selection list with a comma then the selection list\n will not be reviewed for that frame after it has been processed.\nto facilitate data entry. For further information on these features, see\n E.g. 1-3,\n 1@,2;appended text,3-4,\nthe Text Generator Users Manual.\n \nJUMPING:\n By typing a ^^ followed by the name of an aggregate term, the user can go\n right to that aggregate term without having to go through any of the \n intervening frames or selection process. If there are multiple aggregate\n terms that match the text entered after the ^^ the user will be asked to\n
\n\n", "", "", "1990-10-31 00:00:00\n", "", "POSTMASTER\n", "", ""], ["47", "XQHELP-DISP-EP", "WHO CAN EDIT A HELP FRAME\n", "", "", "\nA help frame is editable under one of the following three conditions:\n \nIf a user has edit privileges for a frame, then she/he can enter\n'^E' at the 'Select action' prompt to edit a frame. '^EN', '^EH',\n'^ER', 'ET', are also valid responses to edit individual fields in \na frame. These will cause a switch to [EDIT MODE].\n \n \n - The user holds the XUAUTHOR key, enabling edit of all frames.\n \n - The user is the author of the frame being displayed.\n \n - The user is one of the editors of the frame being displayed.\n Editors can be assigned by the author with the option\n [ASSIGN EDITOR].\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 15:29:00\n", "", "USER,ONE\n", "", ""], ["48", "XQHELP-BUILD", "HOW TO BUILD AND EDIT HELP FRAMES\n", "", "", "\nOn entering a help frame, you will be prompted for the following fields\nRELATED FRAMES. This is done by filling in the multiple field RELATED \nFRAME KEYWORD.\n \nIf a keyword appears in the text and not the related frame list, or\nvice versa, this will be indicated on attempting to edit the related\nframes.\nin the help frame file:\nNAME, HEADER, TEXT, and RELATED FRAMES.\nThe AUTHOR field will automatically become your DUZ, the DATE ENTERED field\nwill automatically become 'TODAY's date. Each time the TEXT of a frame\nis updated, the DATE LAST UPDATED field will be changed.\n \nOn entering the text, any words surrounded by brackets [[ ]] will \nautomatically become keywords. These keywords must be tied into \n
\n\n", "", "", "1992-04-15 15:30:00\n", "", "USER,ONE\n", "", ""], ["49", "XUUSER-PURGEATT-VER", "PURGING MAIL AND KEYS IN VERIFY MODE\n", "", "", "\nIf you answer 'YES' to the prompt 'Do you wish to verify each user?',\n \nTo interrupt the process, enter an '^' at any prompt.\nthe computer will show you each user who has been terminated in the past,\nand issue three prompts about retaining mail, keys, and groups.\n \nBefore each prompt, it will display information about what mail, keys,\nand groups are associated with this user.\n \nIf you answer 'N' to the 'RETAIN' prompts, the associated 'attribute'\nwill be removed for that particular user.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["5", "XUUSER-DEACT", "USING THE 'Deactivate user' OPTION\n", "", "", "\nThe 'Deactivate user' option terminates a user's access to the system.\nthem from any mail groups, and recall their keys. It is recommended\nthat you respond to the 'DELETE...' prompts with a 'YES', unless it\nis likely that a user will be re-activated.\nYou may request termination for a future date, or terminate immediately.\n \nYou will first be prompted for the termination date. If the date you enter\nis today, the access code will be deleted immediately. Otherwise,\nthe termination date is recorded, and a nightly-run utility will\nremove the access codes for users on their termination date.\n \nOn termination of a user, you may chose to purge all their mail, remove\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["50", "XUUSER-MENU", "USING THE 'User Edit' OPTION\n", "", "", "\nThis menu contains options for setting up users, editing them,\n [INQUIRE ABOUT A USER] to obtain information about keys held and attributes.\nand deactivating them.\n \nIn addition, it contains options to\n \n [PURGE LOG] of old access and verify codes\n \n [SWITCH IDENTITIES] to test another user's menu\n \n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: INQUIRE ABOUT A USER
\n- XUUSER-INQ
\n \n- \n
- RELATED FRAME KEYWORD: PURGE LOG
\n- XUAOLDPURGE
\n \n- \n
- RELATED FRAME KEYWORD: SWITCH IDENTITIES
\n- XUSER-TEST
\n \n
\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["51", "XUUSER-PURGEATT", "PURGING MAIL AND KEYS FOR INACTIVE USERS\n", "", "", "\nThis option will purge mail and keys for users who have already been\nunlikely that the message will ever get purged.\n \nThere are two modes of running this option. You can [VERIFY] the process\nfor each user whom the computer selects as eligible. Or you can run\nthe option on 'automatic'. In such case, for every user with a \nnon-future termination date, their set of keys, mail groups, messages, and\nmail baskets will be deleted.\nterminated. In the KERNEL version 5.0, the 'DEACTIVATE USER' option\nwas enhanced to permit purging of these items when a user is deactivated.\nHowever, users de-activated during previous versions may still have\nmessages, mail baskets, keys and mail groups associated with them.\n \nThis is particularly significant with mail, as a message cannot be\ncompletely removed from a system until all recipients have deleted it from\ntheir mail baskets, and if a user is no longer active, then it becomes\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["52", "XQBUILDTREE", "FORCING THE REBUILD OF TREES\n", "", "", "\nThis option can be used whenever a modification has been made to items\n \nThe rebuild process for a single primary menu can take between a few seconds\nand several minutes depending on the size of the menu and the state of the\nsystem.\n \nThe option can be run by [VERIFYING] each primary menu or automatically.\nin a menu requiring that the primary menu trees get rebuilt. A modification\ncould be a LOCK added, and option made NOT AVAILABLE, a SYNONYM changed,\netc. In such cases all primary menu trees need to be rebuilt.\n \nThis can happen automatically, whenever the ^JUMP feature is used to go\ndirectly to an option, or the rebuild can be 'forced'. If done auto-\nmatically, it is done per primary menu tree, per CPU. Separate copies\nof the tree are stored on each CPU.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["53", "XQBUILDTREE-VER", "VERIFY MODE FOR REBUILDING MENUS\n", "", "", "\nThe option which forces the rebuilding of menus on a CPU can be run in\nIf the option is run in AUTOMATIC mode, all primary menus listed will\nhave a tree built. This could be time-consuming. If run in VERIFY mode,\nyou will be prompted for each primary menu, one at a time, and you\ncan decide which you would like to build, based on last date accessed\nand number of users accessing it.\none of two modes: automatic or verify.\n \nThe option will first go thru the user file, and compile a list of primary\nmenus of active users (those with access codes). It will list these \nprimary menus, along with how many users have each, and the most recent\ndate accessed. If there is an existing tree built, the date it was\ncreated will also print.\n \n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["54", "XUKERNEL-USER", "FEATURES OF THE KERNEL\n", "", "", "\nWELCOME TO THE KERNEL!\nMassachusetts General Hospital Utility Multiprogramming System.)\n \nYou use the Kernel when you sign-on, navigate among menus, print reports,\nor send electronic mail messages. The Help Processor, the system you are\nusing right now, is also part of the Kernel. \n \nEnter [CONTINUE] to learn more about the Kernel.\n \nThe Kernel is the central set of DHCP utility programs. This includes\nthe VA File Manager, Menu Manager, Sign-on/Security System, Device\nHandler, Task Manager, and MailMan. All DHCP application packages,\nsuch as Laboratory or Pharmacy, rest upon the central Kernel utilities.\n \n(As you know, the VA's Decentralized Hospital Computer Program is called\nDHCP. It primarily uses the computer language called MUMPS, that's the\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["55", "XUKERNEL-USER2", "LIST OF KERNEL FEATURES\n", "", "", "\n [JUMP] ............. Direct access to any option, jumping thru levels.\n \n [HELP PROCESSOR] ... You're using it right now.\n \n [SIGN-ON] .......... The sign-on procedure to access the computer.\n \nEnter highlighted or bracketed keyword for more information.\n \n [CONTINUE] ......... Halting and being able to continue where you left off.\n \n [MENU DISPLAY] ..... The display of menu option choices.\n \n [PERSONAL COMMANDS] Individualized options which are always accesible.\n \n [THE COMMON MENU] .. The menu available to all users\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 15:10:00\n", "", "USER,ONE\n", "", ""], ["56", "XUKERNEL-USER-DISP", "KERNEL MENU DISPLAY\n", "", "", "\nThe Kernel menu display can be recognized by the line of text following the\n \n \n \n \n \n \nlist of menu items which indicates how help text can be obtained with the\nuse of [QUESTION] marks.\n \nThe list of options in the [COMMON] menu is available to all users. The\nlist can be displayed by entering two question marks at any Kernel menu\nprompt.\n \n \n
\n\n", "\n- \n\n
\n", "", "1992-04-15 15:08:00\n", "", "USER,ONE\n", "", ""], ["57", "XUKERNEL-USER-PER", "PERSONAL COMMANDS\n", "", "", "\nPersonal commands (also called 'secondary menu options') are options\nwhich are assigned to an individual user which may be accessed at\nany time.\n \nThe personal command list is displayed before the 'common options'\non entering '??'.\n \nUsers are given secondary menu options thru the 'USER EDIT' option.\n
\n\n", "", "", "1992-04-15 14:40:00\n", "", "USER,ONE\n", "", ""], ["58", "XUKERNEL-USER-SIGNON", "SIGNING ONTO THE SYSTEM\n", "", "", "\nTo sign-on, you need to enter an access code and a verify code.\n \nThen, when you sign-off, you'll be reminded to remember your new verify\ncode for the next time you sign-on.\n \nIf you do not already have a verify code, just enter a carriage return\nat the verify code prompt and you will be asked to enter a verify\ncode.\n \nEvery so often, as a security measure, you will be asked to change your\nverify code. The system will prompt you for a new code which you can\nthen enter.\n
\n\n", "", "", "1992-04-15 15:37:00\n", "", "USER,ONE\n", "", ""], ["59", "XUKERNEL-USER-XUCOMMAND", "KERNEL COMMON MENU\n", "", "", "\nThe common menu is the list of menu options displayed when entering\n [EDIT USER CHARACTERISTICS] to edit some of these characteristics,\n \n HALT to finish your processing session,\n \n MAILMAN to use the electronic mail system, called MailMan,\n \n RESTART SESSION to restart at sign-on without dropping your line\n (if you have logged-in using a telecommunications line),\n \n TIME to display the time of day,\ntwo question marks in response to a Kernel menu prompt, such as 'Select\n \n USER HELP to see a series of help frames, this one included!\nMailMan Menu Option:'. You will see several options which are available\nfor you to use:\n \n [CONTINUE] to use instead of 'halt',\n \n DISPLAY USER CHARACTERISTICS to show your sign-on characteristics,\n \n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: CONTINUE
\n- XUCONTINUE
\n \n- \n
- RELATED FRAME KEYWORD: EDIT USER CHARACTERISTICS
\n- XUEDITSELF
\n \n
\n
\n", "", "1992-04-15 15:03:00\n", "", "USER,ONE\n", "", ""], ["6", "XUEDITSELF", "USING THE 'Edit User Characteristics' OPTION\n", "", "", "\nThis option, which is accessible thru the Common Menu at all times,\nAUTO-MENU will be effective immediately.\nenables the user to change certain of his/her own attributes.\n \nIt will first prompt for 'changing the devices terminal type'.\nOnly the current device's 'subtype' can be changed thru this option.\n \nThen it will prompt for several fields in the New Person file. This can\nvary according to site. The standard option will present VERIFY CODE,\nINITIALS, NICKNAME, AUTO-MENU, and TYPE-AHEAD. Any change on\n
\n\n", "", "", "1992-04-15 14:38:00\n", "", "USER,ONE\n", "", ""], ["60", "XUUSERSTATUS", "THE 'User status report' OPTION\n", "", "", "\nThis listing will provide supplemental information to the operating\nspecific status report.\n \nAs you will see, it lists the current users by name, and which option\nthey are currently running. It also shows when they have signed-on\nto the system and what their job and device numbers are.\n \nThis report is specific to a single UCI, and only logs users who have\nentered the system thru the sign-on routine.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["61", "XUKERNEL-MGR2", "KERNEL FEATURES (SITE MGR)\n", "", "", "\n[SECURITY KEYS] ........... Bulk allocation of security keys\n \n[PERSONAL COMMAND SPACE] .. Individualized XUCOMMANDs per user\n \n[KERNEL SITE PARAMETERS] .. A file containing system defaults\n \n[DEVICE PASSWORDS] ........ Additional device specific security\n \n[SWITCH IDENTITIES] ....... Provides for testing of another user's menus\n \n[STATUS REPORT] ........... User Status Report\n \n[DEACTIVATE USER] ......... Option to terminate users\n \n[RESTRICT OPTIONS] ........ Ways to restrict options\n \n[REBUILD MENUS] ........... Option used with the [JUMP] feature\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["62", "XUSITEPARAM", "THE 'Site Parameter Editing' OPTION\n", "", "", "\nThis option is used to edit the kernel site parameter file.\nThe fields that a user is allowed to edit through the XUCOMMAND option,\nEDIT USER CHARACTERISTICS, can be modified by creating a [USER EDIT]\ntemplate and supplying its name in the kernel site parameters.\n \nIn addition there are fields for [LIMITING ACCESS] to the system.\n \nIt is here that you may specify [AUTO-GENERATION] of access codes,\nand the [VERIFY CODE] lifetime.\n \nThe log-on default parameters are also specified here. These are used in\nthe case that there is no parameter specified in the user or device\nfile for attributes such as 'time-out', and 'number of attempts allowed'.\n \n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["63", "XUSITEPARAM-AUTOCODE", "AUTO-GENERATION OF ACCESS CODES\n", "", "", "\nAccess codes may be chosen by the person assigning them, or automatically\ngenerated by the computer.\n \nIf they are automatically generated, the computer will assign a code\nof three letters and three numbers. You will then re-enter this code\nto verify it.\n \nThe kernel site parameter file has a field indicating whether auto-generate\nis in effect.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["64", "XUSITEPARAM-VERIFYLIFE", "LIFETIME OF VERIFY CODE\n", "", "", "\nThe verify code should be changed periodically for the purpose of\nbe used as the default.\nsecurity. The site manager can decide how often a user must change\ntheir verify code by setting the 'lifetime of verify code' field\nin the kernel site parameters file.\n \nWhen the time period has elapsed for changing a verify code, the user\nwill be prompted when they sign on to enter a new verify code. They\nmay not use the same one, however they can re-enter an old one.\nIf the user prefers, the code which the computer has generated can\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["65", "XUAOLDPURGE", "PURGING THE LOG OF OLD ACCESS AND VERIFY CODES\n", "", "", "\nNone\nA log of all the access codes that have ever been used is kept on the\nYou may specify the number of days worth of codes you wish to keep.\n \nA log is also kept for each user of old verify codes. This same option\npurges all inactive verify codes older than the number of days specified.\n\nsystem. This prevents a user from having an access code which used to\nbelong to someone else. This is valuable for security reasons.\n \nHowever, in time, it may be desirable to reduce the size of this file,\nand make available those access codes which haven't been used in quite\na while.\n \nThis is done through the option which purges the log of old access codes.\n
\n\n", "", "Y\n", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["66", "XUKERNEL-MGR", "THE KERNEL FOR SITE MANAGERS\n", "", "", "\nWith each installation of the Kernel, you will notice a variety of new\n \n \n \n \n \n \nfeatures. The intent is to provide you with features to make your job\neasier, such as bulk allocation of security keys, and more informative\nuser status reports.\n \nIf you have not yet read the help frames outlining the basic [FEATURES]\nof the Kernel for the users, please enter the word 'FEATURES' or 'F'.\nOtherwise, enter [CONTINUE] to see a list of basic features for the site \nmanager.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["67", "XUSITEPARAM-USEREDIT", "WHAT FIELDS THE USERS THEMSELVES MAY EDIT\n", "", "", "\nUsers can edit certain of their own attributes through the 'Edit\n'User Characteristic Template' in the kernel site parameter file.\nUser Characteristics' option in XUCOMMAND. As a site manager, you may\nvary the fields which a user is allowed to edit.\n \nThe default on the system is to use the fields specified in the 'EDIT\nCHARACTERISTIC' input template. These are verify code, initials, nickname,\nauto menu, and type-ahead. If you want the users at your site to be able\nto edit different fields, construct an input template for the user file\ncontaining those fields. Supply the name of this template as the\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["68", "XUSITEPARAM-LIMITACCESS", "LIMITING ACCESS TO THE SYSTEM\n", "", "", "\nThe site manager can limit sign-on access to the system completely,\n \nIf the SYSTEM UNAVAILABLE field is set to 'yes', then users may not sign\non and taskmanager will not start any jobs.\nor by specifying the maximum number of jobs allowed.\n \nThis is done by setting the SYSTEM UNAVAILABLE field and MAXIMUM NUMBER\nOF JOBS field in the KERNEL SITE PARAMETER file. These fields are defined\nper VOLUME set, and are found as multiples under this field.\n \nThe maximum number of jobs refers to active partitions. This includes\ncaretaker and taskman generated jobs as well as standard interactive jobs.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["681", "ONCO FOLLOW-UP METHOD", "Follow-up Method\n", "", "", "\nCode 0 (reported hospitalization) refers to a hospitalization at another\n hospital, NOT at your institution.\n \nCode 1 (readmission) refers to hospitalization or outpatient visit at your\n institution.\n \nCode 8 (other) refers to a friend or relative.\n
\n\n", "", "", "1991-04-03 00:00:00\n", "", "POSTMASTER\n", "", ""], ["682", "ONCO NEXT FOLLOW-UP METHOD", "Next Follow-Up Method\n", "", "", "\nThis item reflects the type of follow-up recommended\nfor the next follow-up sequence for the patient.\n \nCode 9 (not followed) refers to those cases that the registry\nmay not routinely follow, for example, nonanalytic cases (class\nof case codes 3, 4, and 5), carcinoma in situ of the cervix, or\ncases of foreign residents.\n
\n\n", "", "", "1991-04-03 00:00:00\n", "", "POSTMASTER\n", "", ""], ["683", "ONCO UNUSUAL FOLLOW-UP METHOD", "Unusual Follow-up Method\n", "", "", "\nThis item is used to flag cases with unusual follow-up\nconditions. Specific codes can be assigned by the tumor\nregistry as needed. These codes should be documented for\nconsistency in use, such as 1 (patient unaware of diagnosis).\n
\n\n", "", "", "1991-04-03 00:00:00\n", "", "POSTMASTER\n", "", ""], ["684", "ONCO DRINKS/DAY", "ENTER A QUANTITY EQUAL TO WHISKEY EQUIVALENT\n", "", "", "", "", "", "1991-04-03 00:00:00\n", "", "POSTMASTER\n", "", ""], ["685", "ONCO SURGERY", "*************Determine Surgery Codes***********\n", "", "", "\nEnter '0' for NO Cancer-Directed Surgery (codes 00 to 09)\n \nEnter '1' for any type Cancer-Directed Surgery (codes 10-99)\n \nYour answer will determine which sets of codes are displayed on the\nsite-specific surgery question i.e. 00-09 or the specific 10-99.\n
\n\n", "", "", "1991-04-03 00:00:00\n", "", "POSTMASTER\n", "", ""], ["686", "ONCO DOCUMENTATION OVERVIEW", "DHCP ONCOLOGY TUMOR REGISTRY\n", "", "", "", "", "", "1991-04-23 00:00:00\n", "", "POSTMASTER\n", "", ""], ["687", "ONCO GRADE", "******Determine Grade/Differentiation/Cell Type******\n", "", "", "\n \nCode the degree of differentiation or grade stated in the\nFINAL pathologic diagnosis only.\n \nFor example:\n \n Microscopic Description: Moderately differentiated squamous cell\n carcinoma with poorly differentiated areas\n \n Final Pathologic Diagnosis: Moderately differentiated squamous\n cell carcinoma\n Grade, differentiation\n \n Code to the final diagnosis: Moderately differentiated '2'.\n \nUsually there will be no statement as to grade for in situ lesions.\nHowever, if a grade is stated, it should be coded.\n \nWhen there is variation in the usual terms for degree of differentiation,\ncode to the higher grade as specified below:\n \n TERM GRADE CODE\n ======================\n \n Low grade I-II 2\n Medium grade II-III 3\n High grade III-IV 4\n \n Partially well differentiated I-II 2\n Moderately undifferentiated III 3\n Relatively undifferentiated III 3\n \nGrade coding for prostate cases using Gleason's score or pattern.\n \n \n 1. If Gleason's score (2-10) is given code as follows:\n \n Gleason's score Grading\n 2, 3, 4 I Well Differentiated\n 5, 6, 7 II Moderately Differentiated\n 8, 9, 10 III Poorly Differentiated\n \n 2. If Gleason's pattern (1-5) is given code as follows:\n \nIf a diagnosis indicates two different degrees of grade or\n Gleason's pattern Grading\n 1-2 I Well Differentiated\n 3 II Moderately Differentiated\n 4-5 III Poorly Differentiated\n \nFor lymphomas and leukemias designation of T-cell, B-cell, and null cell:\n========================================================================\n \nCode the results of marker studies. Code the final pathologic diagnosis\nof T-cell, B-cell or null cell if marker studies are not documented\ndifferentiation (e.g. "well and poorly differentiated"; or "grade\nin the patient record. (See page 2 of ICD-O, FT, 1987.)\n \nFor lymphomas and leukemias, information on T-cell, B-cell or null cell\nhas precedence over information on grading or differentiation.\nII-III"; or "well differentiated grade II"), code to the higher grade\ncode (Rule 10, page xxxi in ICD-O, 1990).\n \n
\n\n", "", "", "1992-03-05 11:41:51\n", "", "POSTMASTER\n", "", ""], ["688", "ONCO ACOS DOCUMENTATION", "************ ACOS CALL FOR DATA - DOCUMENTATION ***********\n", "", "", "\n ONCOANC0\n Documentation for running ONCOANC0.EXE.\n \n COUNT = COUNT + 1\n \n FOR A = 1 TO 8\n D$ = D$ + A$(A)\n NEXT A\n \n E$ = SPACE$(326)\n D$ = D$ + E$\n \n \n PRINT #2, D$\n PRINT ".";\n \n D$ = ""\n E$ = ""\n \n FOR A = 1 TO 8\n A$(A) = ""\n NEXT A\n \n ONCOANC0.EXE is a compiled QuickBasic MSDOS program that is the\n GOTO START\n \n OVER:\n CLOSE #1\n CLOSE #2\n \n CLS\n PRINT "DONE! Processed "; COUNT; " Records."\n companion to mumps program ONCOANC0. The DOS portion is required to\n turn the captured output of Mumps program ONCOANC0 into the 850 byte\n record format that Data Acquisition Manual requires.\n \n You will need an IBM compatible hooked up to DHCP (either by modem or\n direct connect) and a terminal emulator . The terminal emulator must\n be able to capture data from the screen into a disk log file. We\n \n used Procomm v2.01 for our tests.\n \n \n Operating instructions.\n \n After compiling, place ONCOANC0.EXE into your terminal emulator's\n directory.\n \n Log onto DHCP and get into programmer.\n \n ONCOANC0 is a Mumps program that will search oncology primary file,\n Run ONCOANC0 (MUMPS)\n \n After inputting the date and hitting enter you must open a log file.\n You will have approximately 1 minute to do so. The log file MUST be\n named ONCOANC0.DTA - It is VERY important to name it exactly as\n shown.\n \n Close the log file when ONCOANC0 returns you to the programmer prompt.\n \n Log/out of DHCP.\n ^ONCO(165.5, and oncology patient file, ^ONCO(160, for CALL FOR DATA\n \n Quit your terminal emulator.\n \n Run ONCOANC0 (MSDOS) - The resulting file (ONCOANC0.DAT) will be the\n one sent to DAM.\n \n ******************************************************************\n \n Below is part of an actual DHCP session.\n \n information. Information is validated as it is retrieved. Program\n >D ^ONCOANC0\n \n ENTER DAM 6 DIGIT HOSPITAL REGISTRY ID: 123456\n \n ENTER ACCESSION YEAR (85/90): 90\n \n ********************************************************************\n * Here is where you will open your log file with a filename of *\n * ONCOANC0.DTA It is VERY important to name it exactly as shown.*\n * In ProComm you will do an ALT F1 to start your logging. *\n is invoked by D ^ONCOANC0. Six-digit DAM registry ID and Accession\n * Data begins below. Only 1 record is shown. You will have more. *\n * Mailman will probably cause the word wrapping of the data to be *\n * off. *\n ********************************************************************\nIB7632000361234560SIOUX FALLS IA999571050000 401301083121719\n06^\n05399 010110199019990812033991 90 123456^\n900002 0116199001221990110000001 9992200900 2^\n3 0 1 101181990 ^\n011819901000000000 042019901000000^\n year (85 OR 90) is required. Program must be rerun if more than one\n 12071990^\n028 0420199019 92449^\n 2 2^\n>\n ********************************************************************\n * At this point, close your log file (ALT F1 again), quit Procomm *\n * and exit to DOS. You should still be in your Procomm directory *\n * Type ONCOANC0 to run the conversion to 850 byte records that DAM*\n * requires. The resulting file will be called ONCOANC0.DAT. *\n ********************************************************************\n year is to be searched.\n \n \n QuickBasic "source" for ONCOANC0.EXE follows.\n \n CLS\n \n PRINT "WORKING";\n OPEN "ONCOANC0.DTA" FOR INPUT AS #1\n OPEN "ONCOANC0.DAT" FOR OUTPUT AS #2\n \n \n START:\n \n FOR A = 1 TO 8\n LINE INPUT #1, A$(A)\n IF EOF(1) THEN GOTO OVER\n IF A$(A) = "" THEN GOTO START\n IF ASC(A$(A)) < 16 THEN GOTO START\n B = LEN(A$(A)) - 1\n A$(A) = MID$(A$(A), 1, B)\n NEXT A\n
\n\n", "", "", "1992-08-16 10:56:20\n", "", "POSTMASTER\n", "", ""], ["689", "RMPR-ELECTRONIC SIGNATURE", "ELECTRONIC SIGNATURE HELP\n", "W X\n", "", "\nEnter your Electronic Signature code to complete this action.\nConsult with your local Application Coordinator if you need help changing \nyour Electronic Signature code, or need help setting up an Electronic \nSignature code.\n
\n\n", "", "", "1994-11-10 13:23:05\n", "\n- \n\n
\n", "POSTMASTER\n", "", ""], ["69", "XQDEVICE-PASSWORDS", "DEVICE PASSWORDS\n", "", "", "\nFor devices such as modems, it is often useful to have an additional level\nof security. This can be done by assigning a PASSWORD in the DEVICE file.\n \nWhen a user attempts to log on, they will be prompted for the PASSWORD\nbefore being prompted for ACCESS and VERIFY code. The maximum number of\nattempts will be in effect for the DEVCIE PASSWORD.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["690", "ECDSS1", "National/Local Procedure Reports\n", "", "W @IOF\n", "\nThis option allows you to display a listing of Event Capture procedures. \n \nIf you choose active procedures, you are prompted to choose a preferred \nreport (National, Local, or Both) and a sort method (Procedure Name, \nProcedure Number). The output includes:\n \n - Procedure Name\n - Procedure Number\n - CPT\nYou can to choose to include active or inactive procedures. \n \nIf you choose inactive procedures, the output includes:\n \n - Procedure Name \n - Procedure Number \n - CPT \n - Inactive Date \n
\n\n", "", "", "1996-05-01 14:41:00\n", "\n- \n\n
\n", "USER,SEVENTEEN\n", "", ""], ["691", "ECDSAC", "Event Capture Active Procedures\n", "", "", "\nThe Event Capture Active Procedures option will allow you to select from a\nsubset of either National or Local procedures, or allow you to select a\ncombined report of both National and Local procedures.\n
\n\n", "", "", "1995-03-21 06:25:45\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["692", "ECDSAC1", "Event Capture Active Procedures\n", "", "", "\nThis prompt from the active procedures option allows you to select the\norder of presentation for the National procedures. You may select to\npresent the National procedures in either alphabetical order by procedure\nname, or in numberical order by National Number.\n \nIf you have selected a report of both National and Local procedures, the\nLocal procedures will be presented in alphabetical order by procedure name\nregardless of the option you choose for the presentation of the National\nProcedures.\n
\n\n", "", "", "1995-03-21 06:26:12\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["693", "ECMGR", "Event Capture Management Menu\n", "", "W @IOF\n", "\nThis menu option accesses the menus needed for management of the Event\nCapture software. It includes, but is not limited to:\n \n - allocation of DSS units\n - assignment of users to DSS units\n - addition of local procedures and categories\n - formation of Event Code Screens\n
\n\n", "\n- \n\n
\n", "", "1997-03-05 07:51:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["694", "ECENTER", "Event Capture Data Entry\n", "", "W @IOF\n", "\nThis menu option accesses the data entry options of the Event Capture\nsoftware. The three options allow the user to enter data by:\nindividual patient and procedure; multiple patients for a given \nprocedure; multiple dates and procedures for multiple patients.\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: INDIVIDUAL
\n- ECPAT
\n \n- \n
- RELATED FRAME KEYWORD: BATCH
\n- ECBATCH
\n \n- \n
- RELATED FRAME KEYWORD: BATCH BY PROCEDURE
\n- ECBATCH PROC
\n \n- \n
- RELATED FRAME KEYWORD: MULT DATES/MULT PROCS
\n- ECMULT PROC
\n \n
\n
\n", "", "1996-04-03 08:46:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["695", "ECREPS", "Event Capture Reports\n", "", "W @IOF\n", "\nThis menu allows you to access a variety of workload-related reports in\nPCE Data Summary\nInactive/Missing Person Class Report\nProcedure Reason Report\nthe Event Capture software.\n \n \nPatient Summary - Event Capture\nDSS Unit Workload Summary \nProvider Summary Report\nOrdering Section Summary Report\nProvider (1-3) Summary Report\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: PATIENT
\n- ECPAT SUM
\n \n- \n
- RELATED FRAME KEYWORD: DSS WORKLOAD
\n- ECAMIS
\n \n- \n
- RELATED FRAME KEYWORD: ORDERING
\n- EC OS SUM
\n \n- \n
- RELATED FRAME KEYWORD: SUMMARY
\n- EC PRO SUM
\n \n- \n
- RELATED FRAME KEYWORD: PROVIDER
\n- ECPROV
\n \n- \n
- RELATED FRAME KEYWORD: PCE
\n- ECPCER
\n \n- \n
- RELATED FRAME KEYWORD: INACTIVE PERS
\n- ECRPERS
\n \n- \n
- RELATED FRAME KEYWORD: PROC REASON
\n- ECRPRSN
\n \n
\n
\n", "", "1997-01-22 07:50:00\n", "", "USER,ONE\n", "", ""], ["696", "ECDSAI", "Activate/Inactivate\n", "", "W @IOF\n", "\nThis menu option will allow you to use other options which will create or\ninactivate event code screens, inactivate local categories and procedures,\nand otherwise toggle to on/off other parameters of the Event Capture\nsoftware.\n \nIncluded are the options for [Current] Locations; [Local] Categories;\n[Event] Code Screens; [Inactivate] Event Code Screens; and\n[Activate]/Deactivate Local Procedures.\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: ACTIVATE
\n- ECDSDEAC
\n \n- \n
- RELATED FRAME KEYWORD: EVENT
\n- ECSCREEN
\n \n- \n
- RELATED FRAME KEYWORD: INACTIVATE
\n- ECNACT
\n \n- \n
- RELATED FRAME KEYWORD: LOCAL
\n- ECDS CATEGORY DEAC
\n \n- \n
- RELATED FRAME KEYWORD: CURRENT
\n- ECLOC
\n \n
\n
\n", "", "1995-04-24 08:38:23\n", "", "USER,ONE\n", "", ""], ["697", "ECDSRPT", "Management Reports\n", "", "W @IOF\n", "\nThis menu allows you to access the menu options that print a variety \nof managment reports for categories and procedures.\n \nNational/Local Procedure Reports \nCategory Reports \nPrint Category and Procedure Summary \nSummary of Procedures and Categories (Old File) \n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: LOCAL
\n- ECDSS1
\n \n- \n
- RELATED FRAME KEYWORD: CATEGORIES
\n- ECDSS3
\n \n- \n
- RELATED FRAME KEYWORD: SUMMARY
\n- ECCP
\n \n- \n
- RELATED FRAME KEYWORD: PROCEDURE
\n- ECCP1
\n \n
\n
\n", "", "1995-04-24 08:43:52\n", "", "USER,ONE\n", "", ""], ["698", "ECLOC", "Current Locations (Create/Remove)\n", "", "W @IOF\n", "\nThis option creates or removes access to an Event Capture location\nand flags it as active or inactive for use in the Event Capture \nSoftware.\n \nWhen creating a location, your selection can be an individual facility, \nor a division if your facility is multidivisional, and has to exist in \nthe INSTITUTION file (#4). You must create locations before using \nany of the other Event Capture menu options.\n
\n\n", "", "", "1995-04-24 09:05:54\n", "", "USER,FIFTYFOUR\n", "", ""], ["699", "ECDS CATEGORY", "Local Category (Enter/Edit)\n", "", "W @IOF\n", "\nThis option allows you to ENTER or EDIT, but NOT DELETE, local \nfacility. For the DSS Units at your facility that do not use categories \nto group procedures, you can ignore this option. \ncategories in the EVENT CAPTURE CATEGORY file (#726). \n \nDSS Units can be defined to use categories to group procedures during \ndata entry. Categories are facility-specific, so you can use names that \nbest suit your facility. For example, if you have a DSS Unit named \nAudiology and Speech, you might have categories named Speech Evaluation \nand Audiology Testing. It is acceptable to have both DSS Units that DO \nuse categories and DSS Units that DO NOT use categories defined at your \n
\n\n", "", "", "1995-04-24 09:16:21\n", "", "USER,ONE\n", "", ""], ["7", "XQHELP-LIST", "USING THE 'List Help Frame' OPTION\n", "", "", "\nThe 'List Help Frame' option will print a help frame series, starting\nThe simplest is text only. Other formats will show internal names of\nhelp frames, keywords and related frames.\n \n \n \n \n \nat the help frame you specify, and progressing automatically thru\nthe tree. For example, if you select XMREAD, you will see all help\nframes which are descendents of XMREAD.\n \nThe listing will include a table of contents, showing page numbers\nfor each help frame printed.\n \nThere are a variety of [FORMATS] for the listing.\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 15:32:00\n", "", "USER,ONE\n", "", ""], ["70", "XUSER-TEST", "THE 'Switch Identity' OPTION\n", "", "", "\nThis option will allow you to simulate signing on as another user\nto test the user's menus and keys. \n \nIt will not allow you to execute any bottom level menu options, such\nas reading mail, or registering a patient.\n \nYou will be reminded at each prompt whose menu it is you are testing.\nTo exit this mode and return to your own menus, simply enter a '*'.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["700", "ECDS CATEGORY DEAC", "Activate/Inactivate Local Category\n", "", "W @IOF\n", "\n** You might want to use the Category Reports option on the Management \ncategory. \n \nIf the DT INACTIVE field is turned OFF for the category you selected, \nthe software asks if you want to INACTIVATE the category. If this \nfield is turned ON for the category you selected, the software asks \nif you want to REACTIVATE the category. \nReports menu to print a list of inactive categories before using this \noption. ** \n \n** You must create local categories before using this option. ** \n \nThis option allows you to INACTIVATE or REACTIVATE, but NOT DELETE \nlocal categories. It toggles the DT INACTIVE field (#2) of the \nEVENT CAPTURE CATEGORY file (#726) on/off. You are prompted for a \n
\n\n", "", "", "1995-04-24 09:21:10\n", "", "USER,ONE\n", "", ""], ["701", "ECDS CATEGORY EDIT", "Local Category (Edit)\n", "", "W @IOF\n", "\nThis option will allow you to edit the name of local categories. If you\nentered the category ACUTE CAKE meaning to enter ACUTE CARE, this option\nwill allow you to correct the mistake.\n \nYou may not delete entries in the local category file by entering "@"\nwhile editing, but you may change the name.\n
\n\n", "", "", "1995-04-24 09:26:08\n", "", "USER,ONE\n", "", ""], ["702", "ECSCREEN", "Event Code Screens (Create)\n", "", "W @IOF\n", "\n** You must create Event Capture Locations with the Current Locations \nThis option allows you to create Event Code Screens for one or all \nEvent Capture locations. Event Code Screens define procedure information.\nDuring data entry, users can select only the procedures defined in the\nEvent Code Screens. For each screen, you are prompted to enter the\nfollowing information:\n \n - DSS Unit \n - Category (If DSS Units are defined to group procedures by categories) \n - Procedure \n \n(Enter/Edit) option before using this option. ** \nWhen creating the screens for specific locations, you are prompted to \nenter the following additional information: \n \n - Location name (If you chose not to create the screen for ALL \n locations)\n - Associated Clinic (If the DSS Unit is defined to send data to PCE) \n - Synonym (The locally-recognized name for a local or national \n procedure)\n - Volume (The number of times the procedure was performed or the \n length of time it took)\n \n \nWhen deleting an Event Code Screen, the prompt "The selected Event Code\nScreen will be deleted. Continue?" will check for any workload on the \nEvent Code Screen.\n \n - If there is workload on the selected Event Code Screen, then the\n Event Code Screen will not be deleted.\n - If there is no workload on the selected Event Code Screen, then the \n Event Code Screen will be deleted.\n** You must create DSS Units with the DSS Units for Event Capture \n(Enter/Edit) option before using this option. ** \n \n** You must define Event Code Screens in order to enter Event Capture \ndata. ** \n \n
\n\n", "", "", "1997-03-26 09:42:00\n", "", "USER,EIGHTYSIX\n", "", ""], ["703", "ECNACT", "Inactivate Event Code Screens\n", "", "W @IOF\n", "\n** You must define DSS Units, categories, procedures, and Event Code \n - Category (If DSS Units use categories to group procedures) \n - Procedure \n \nIf the INACTIVE DATE field is turned OFF for the procedure you select, \nthe software asks if want to INACTIVATE the procedure. If this field \nis already turned ON for the procedure you select, the software tells \nyou that the Event Code Screen for the selected procedure has a status \nof inactive and asks if you want to ACTIVATE it.\n \n** PLEASE NOTE: This option inactivates the selected procedure in \nScreens before using this option. ** \nthe specified Event Code Screen ONLY; IT DOES NOT INACTIVATE THE \nPROCEDURE ITSELF. **\n \nThis option allows you to INACTIVATE or REACTIVATE, but NOT DELETE \nEvent Code Screens. It toggles the INACTIVE DATE field (#1) in the \nEC EVENT CODE SCREENS file (#720.3) on/off. You are prompted for \n \n - Location \n - DSS Unit \n
\n\n", "", "", "1996-04-30 21:18:00\n", "", "USER,ONE\n", "", ""], ["704", "ECDSDEAC", "Activate/Inactivate Local Procedures\n", "", "W @IOF\n", "\n** You must create local procedures before using this option. ** \na procedure. \n \nIf the INACTIVE DATE field is turned OFF for the procedure you selected, \nthe software asks if you want to INACTIVATE the procedure. If this \nfield is turned ON for the procedure you selected, the software asks \nif you want to REACTIVATE the procedure.\n \n** You might want to use the National/Local Procedure Reports option on \nthe Management Reports Menu to print a list of the inactive procedures \nbefore using this option. ** \n \nThis option allows you to INACTIVATE or REACTIVATE, but NOT DELETE, \nlocal procedures. It toggles the INACTIVE DATE field (#2) in the \nEC NATIONAL PROCEDURE file (#725) on/off. You are prompted for \n
\n\n", "", "", "1995-04-24 10:08:18\n", "", "USER,ONE\n", "", ""], ["705", "ECSECT", "DSS Units for Event Capture (Enter/Edit)\n", "", "W @IOF\n", "\n** You must define your DSS Units with this option for subsequent options \n - An entire service\n - A section of a service \n - A small section within a section \n - A medical equipment item used in patient procedures\n \nWhen a DSS Unit is inactivated, all associated Event Code Screens will \nalso be inactivated. When an inactive DSS Unit is reactivated, you will\nchoose whether or not to reactivate the associated Event Code Screens by \nchoosing "Reactivate" or "Remain Inactive."\n \nin the Event Capture Software to work. **\nWhen creating DSS Units, your response to the "Allow Category Use" prompt \ndetermines whether or not procedures are grouped by categories during \ndata entry. When editing DSS Units, the "Allow Category Use" prompt may\nbe changed until there are event code screens defined. Once event code\nscreens have been defined the user may only change the category setting\nfrom "Yes" to "No" to remove the use of categories. Once set to "No",\nwhen event code screens are defined, the user can no longer change this\nfield.\n \nThe allow duplicate override prompt controls whether or not workload\n \nentered via spreadsheet upload can create duplicate records. If set to no\nthen the user may not create duplicate workload during spreadsheet \nupload. If set to yes, the user is allowed to override the duplicate \nrecord message and file a duplicate record. The default value is no as \ncreation of duplicate workload is not typical.\n \nWhen creating or editing DSS Units, you can choose what (if any) data \nis sent to PCE, and the method used to send it: \n \n A - Send All Records \nThis option allows you to ENTER and EDIT, ACTIVATE and INACTIVATE DSS\n N - Send No Records\n OOS - Send Occasion Of Service Records\n \nThe advantage of using Event Capture to send data to PCE is that it \neliminates the duplicate effort of entering the same workload data in the \nScheduling software, then transmitting to PCE. \n \nIf a DSS Unit is set up NOT to send to PCE (No records), then:\n \n 1.) An Associated Stop Code is required to be entered for the DSS Unit\nUnits for use with Event Capture. DSS Units typically represent the\n during setup. \n 2.) A Credit Stop Code may be added. \n 3.) A CHAR4 Code may be added.\n \nIf a DSS Unit is set up to send OOS records to PCE then:\n \n 1.) An Associated Stop Code is required to be entered for the DSS Unit\n during setup. \n \nOnce a DSS unit is stored, its 'Send to PCE' value cannot be changed from \nsmallest identifiable work unit in a clinical service at the medical\nor to 'OOS'.\n \nWhen deleting a DSS Unit, the prompt "The selected DSS Unit will be \ndeleted. Continue?" is displayed. If "Yes" is selected, the system will\ncheck for any workload on the DSS Unit and its associated Event Code \nScreens.\n \n - If there is workload on the selected DSS Unit, then the DSS Unit will \n not be deleted.\n - If there is no workload on the selected DSS Unit, then the DSS Unit and\ncenter and are defined by the VAMCs. A DSS Unit can represent any of the\n its associated Event Code Screens will be deleted.\nfollowing:\n \n
\n\n", "", "", "1997-03-26 09:23:00\n", "", "USER,EIGHTYSIX\n", "", ""], ["706", "ECDSSYN", "Procedure Synonym/Default Volume (Enter/Edit)\n", "", "W @IOF\n", "\n** You must have access to locations, DSS Units, and categories in order \nnational procedure. This option allows you to enter, edit, and delete \nthe procedure synonym, Associated Clinic, and Volume. \n \nIt is acceptable to have multiple synonyms for a procedure, because \nthe synonyms are associated with the Event Code Screens that define \nthe procedures. For data entry and reports, the software uses the \nprocedure synonym, if one exists. \n \nProcedures that are being passed to PCE must have an Associated Clinic. \nWhen you enter or edit an Associated Clinic using this option, it \nto use this option. ** \nbecomes the default clinic during data entry. Likewise, when you \nenter or edit the Volume with this option, it becomes the Default \nVolume during data entry.\n \n** You must create Event Capture locations, DSS Units, and procedures \nbefore using this option. If the DSS Units use categories to group \nprocedures, you must also define the categories before using this \noption. ** \n \nA procedure synonym is the locally-recognized name for a local or \n
\n\n", "", "", "1997-03-26 09:42:00\n", "", "USER,ONE\n", "", ""], ["707", "ECDSS PROCEDURE", "Local Procedure (Enter/Edit)\n", "", "W @IOF\n", "\n** You might want to print a list of procedures with their associated CPT \nare being passed to the PCE software must have an associated CPT code.\nFor new procedures, you must also enter a local procedure code number. \nThe local procedure code must be 5 characters: 1 uppercase alpha \ncharacter followed by 4 alphanumeric characters. This \nnumber will be used as the national code number for your local procedure. \ncodes to use as a reference BEFORE USING THIS OPTION. If so, use the \nNational/Local Procedure Reports option on the Management Reports \nsubmenu of the Event Capture Management Menu. This report can be \nlengthy if you opt to include national procedures, so you should queue \nit to print during nonpeak hours. **\n \nThis option allows you to ENTER or EDIT, but NOT DELETE local \nprocedures in the EC NATIONAL PROCEDURE file (#725). Procedures that \n
\n\n", "", "", "1997-03-26 09:25:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["708", "ECDSS PROCEDURE EDIT", "Local Procedure (Edit)\n", "", "W @IOF\n", "\nThis option allows you to edit existing local procedures, but will not\nallow you to delete procedures.\n
\n\n", "", "", "1995-04-24 11:35:20\n", "", "USER,ONE\n", "", ""], ["709", "ECDSS3", "Category Reports\n", "", "W @IOF\n", "\nThis option allows you to print/display the local categories which you\nhave established. You can print this report by active categories, inactive\ncategories, or all categories. For inactive categories, the inactive\ndate is included in the output.\n
\n\n", "", "", "1996-05-01 14:42:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["71", "XQOPTWHO", "USING THE 'Option Access By User' HELP FRAME\n", "", "", "\nThis option will produce a listing of users who have access to the\nand will show the last sign-on time.\noption which you specify. \n \nYou will be prompted first for the OPTION you wish to trace. You will\nthen be asked if you want to show menu paths. If you answer 'YES',\nthe listing will include the paths that each user has to the specified\noption.\n \nThe option will include active users only (those with an access code)\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["710", "ECCP", "Print Category and Procedure Summary\n", "", "W @IOF\n", "\n** You must have locations, DSS Units, local categories, and procedures \ntogether by category. The output includes:\n \n - Run Date \n - Location \n - Service \n - DSS Unit\n - Send Status\n - DSS Dept. \n - Category (if applicable) \n - Procedure Code\ndefined before using this option. ** \n - Procedure Name\n - Synonym \n - Associated Clinic IEN (if applicable) \n - Associated Clinic (if applicable)\n - Stop Code\n - Credit Stop Code\n - CHAR4\n - MCA Labor Code\n \n** You might want to print this report as a reference guide for data \nentry personnel at your facility. **\n \nThis option allows you to print/display the Event Code Screens for one, \nmany or all DSS Units within a specified location. If your DSS Units are\ndefined to group procedures by categories then procedures will print \n
\n\n", "", "", "1995-04-24 13:46:16\n", "", "USER,FIFTYFOUR\n", "", ""], ["711", "ECDSUNIT", "Assign User Access to DSS Units\n", "", "W @IOF\n", "\n** You must create DSS Units with the DSS Units for Event Capture \nTo assign the ECALLU security key for access to ALL DSS units, use the \nAllocate Security Keys option in the Key Management Submenu of the \nMenu Management Menu.\n \nPlease Note: Even if users have the Event Capture options on their\nVISTA menus, they cannot begin entering data until the appropriate \naccess is assigned.\n(Enter/Edit) option before using this option. **\n \nThis option allows you to assign access to DSS Units for specified \nusers of the Event Capture Software. (Contact each service for a list \nof its Event Capture users and the DSS Units for which they should be \ngiven access.) Access should be limited to only those individuals who \nare responsible for entering procedure data into the specified DSS Units. \n \n
\n\n", "", "", "1995-04-25 05:57:20\n", "", "USER,FIFTYFOUR\n", "", ""], ["712", "ECDEAL", "Remove User Access to a DSS Unit\n", "", "W @IOF\n", "\nThis option allows you to remove access to one or all DSS Units for one \neven if the Event Capture menu options appear in his/her VISTA menu.\nor all users. If you remove access to a DSS Unit for ALL users, the \nsoftware asks if you want to inactivate the DSS Unit. \n \nTo remove access to DSS Units for users holding the ECALLU security key, \nyou must use the De-allocation of Security Keys option on the Key \nManagement submenu of the Menu Management Menu.\n \nPlease Note: Removing a user's access prevents him/her from entering data \n
\n\n", "", "", "1995-04-25 06:00:25\n", "", "USER,ONE\n", "", ""], ["713", "ECDSUSR", "User Access\n", "", "W @IOF\n", "\nThis menu option leads to the options for controlling access to DSS Units\nEvent Capture software.\n \nUnder this menu you will be able to [assign] and [remove] user access.\nfor data entry. You may assign access to any DSS Units which have been\nestablished to anyone within the NEW PERSON file. It is suggested that\nassignment of access to DSS Units be limited to those individuals who have\nthe responsibility for data input into those units.\n \nAssigning access will still require the assignment of options within the\nMenu Manager. It should be remembered that for access to the DSS Units to\nbe complete, access must be granted through both the Menu Manager and the\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: ASSIGN
\n- ECDSUNIT
\n \n- \n
- RELATED FRAME KEYWORD: REMOVE
\n- ECDEAL
\n \n
\n
\n", "", "1995-04-25 06:03:56\n", "", "USER,ONE\n", "", ""], ["714", "ECPAT", "Enter/Edit Patient Procedures\n", "", "W @IOF\n", "\n** If only one or no Category is defined for the specified DSS Unit, you \n** Procedures being passed to PCE must have an active Associated Clinic.\nProcedures being passed to PCE in association with an OOS DSS unit do not\nrequire a clinic be selected; a clinic will automatically be assigned when\nthe entry is added. **\n \nThis option allows you to enter patient procedures performed on an\nindividual patient. You should use it when you have an individual\npatient record to add or update. \n \nAfter selecting a Procedure, enter the Volume.\ncannot edit the Category. **\n \n*** The ECS volume field does NOT capture the number of patients seen by\nECS providers. ***\n \nVolume is usually associated with the number of procedures performed.\nThe volume field can be used to record and track 3 different values:\n \n1. Number of Procedures: When a selected procedure code CONTAINS inherent\ntime elements (such as "30M Massage Therapy"), a volume of one is usually\nentered, meaning 1 of this specific procedure/service was provided.\n \n \n = OR =\n \n2. Time: Amount of time shown in increments of minutes (M). When a \nselected procedure code does NOT have inherent time elements, the volume\nfield is used to capture the time spent completing the procedure/service:\n1 = 15M; 2 = 30M; 3 = 45M.\n \n = OR =\n \n** If only one Procedure is defined in the DSS Unit, the Procedure field \n3. Days: Number of days patient was in VA paid facilities such as a State \nHome, DOM, or Nursing Home. When entering workload for a patient in a VA \npaid facility, a volume of '1' means 1 day, '2' means 2 days, etc.\n \nNOTE: It is imperative to understand and keep track of the values entered\nin the volume field, and what they represent for the patients being\ntreated.\n \nClick the 'Problem List' button to open a patient's list of problems. The\nProblem List contains the following details:\nwill be populated. **\n\n - Problem Status\n - ICD Code\n - Code Description\n - Date of Onset\n - Date of Last Modified\n - Provider\n \nIf no Problems List information exists for the selected patient, a \nmessage dialog is displayed stating "There are no items in the problem \n \nlist for NAME, PATIENT (XXX-XX-XXXX) DOB: m/d/yyyy."\n \nOne or more procedures may be entered for a single patient encounter. Once\nall required fields have been entered, click the 'OK' button to save the\nrecord. Click the 'Cancel' button to exit the screen without filing the\nrecord. Click the 'Add' button to file the current record, and to \ninitialize the form for a new procedure to be added.\n \nNOTE: The 'Add' button will be disabled if the Multiple Procedures\nfeature was used to add patient procedures.\n** You must answer exposure and service-connected indicators if fields \n \nSee the User Manual for additional details on features such as Recent\nVisits.\nare not disabled. ** \n \n
\n\n", "", "", "1997-03-26 09:28:00\n", "", "USER,EIGHTYNINE\n", "", ""], ["715", "ECBATCH", "Batch Enter Event Capture Data\n", "", "W @IOF\n", "\n** You must define locations, DSS Units, categories, procedures, and \n** You will be prompted for exposure and service-connected indicators \nfor OUTPATIENT PROCEDURES ONLY. \n \nUse this option to enter multiple procedures for multiple patients as \na batch entry. After you enter the ICD-10 (Diagnosis) and inpatient or\noutpatient information for the first patient, the "Select Next Patient:"\nprompt appears. This prompt will repeat, allowing you to select multiple\npatients, until you press the RETURN or ENTER key to indicate that patient\nselection is complete.\n \nEvent Code Screens before using this option. ** \nYou will be prompted to select a category if the specified DSS Unit is\ndefined to group procedures by category. After each procedure entry, the\nsoftware asks you to verify that the the data you entered is correct,\nand the "Enter Procedure:" prompt repeats, allowing you to enter multiple\nprocedures, until you press the RETURN or ENTER key to indicate that\nprocedure entry is complete. \n \nThe software tells you the total number of procedures you entered, and\nasks if you want to enter them in the file. If you respond YES, they are\nprocessed in the background and added to the EVENT CAPTURE PATIENT file\n \n(#721).\n** If only one category is defined for the specified DSS Unit, you will \nnot be prompted for category. **\n \n** Use the Enter/Edit Patient Procedure option to correct erroneous \npatient data. **\n \n
\n\n", "\n- \n\n
\n", "", "1997-03-26 09:28:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["716", "ECPAT SUM", "Patient Summary - Event Capture\n", "", "W @IOF\n", "\n** This report is formatted for a 132-column device. **\n - Location\n - DSS unit name and IEN\n - Associated Clinic, stop code, credit stop, CHAR4 code and MCA Labor Code \n - Service\n - Section where performed\n - Procedure reason(s) (optional)\n - Ordering Section\n - Provider\n \nThis option allows you to print/display procedure-related data within a\nspecified date range for a selected patient. The output includes:\n \n - Procedure date and time\n - Procedure\n - Volume\n - Modifier(s)\n
\n\n", "", "", "1995-04-25 06:45:10\n", "", "USER,FIFTYFOUR\n", "", ""], ["717", "ECAMIS", "DSS Unit Workload Summary Report\n", "", "W @IOF\n", "\nThis report will display the number of procedures performed in each of the\nselected DSS Units. If the DSS Unit uses categories, it will list the\nprocedures in each category and how many were performed. It will also\nlist the total number of procedures for the unit at the bottom of the unit\nlisting.\n \nIf more than one location has been set up, you will be prompted to select\nall or specific locations. You will also be prompted to select all or\nspecific DSS Units.\n
\n\n", "", "", "1995-04-25 06:49:06\n", "", "USER,FIFTYFOUR\n", "", ""], ["718", "ECPROV", "Provider Summary Report\n", "", "W @IOF\n", "\n** This report is formatted for 132-column output. It could be a lengthy\n - Location\n - DSS unit\n - Provider\n - Category (if applicable)\n - CPT Code\n - Procedure Code\n - Procedure Name\n - Procedure Reason\n - Volume\n - Modifier(s)\nreport, so you might want to queue it to print during nonpeak hours. **\n - Total number of procedures performed by the provider within the \n specified date range\n \nThis option allows you to print/display the number of procedures performed\nfor one or all locations and one or all DSS Units within a specified date\nrange. Within each DSS Unit for each location, the report is sorted by\nprovider, category (if the DSS Unit is defined to sort procedures by\ncategory), and procedures (listed alphabetically). The output includes:\n \n
\n\n", "", "", "1995-04-25 07:01:21\n", "", "USER,FIFTYFOUR\n", "", ""], ["719", "EC OS SUM", "Ordering Section Summary Report\n", "", "W @IOF\n", "\n** This report is formatted for 132-column output. **\n - Procedure\n - Volume\n - Provider(s)\n - Synonym\n - Modifier(s)\n \nThis option allows you to print/display procedures ordered within a\nspecified date range for a selected ordering section. The output\nincludes:\n \n - DSS unit\n - Patient name\n - Last four of patient SSN\n
\n\n", "", "", "1995-04-25 07:05:17\n", "", "USER,FIFTYFOUR\n", "", ""], ["72", "XUS UCI UPDATE", "UCI UPDATE FOR VERSIONS PRIOR TO 4.3\n", "", "", "\nThe sign-on portion of the Kernel (the "XUS" routines) now allows users\n 1 TST\n 2 MGR:STA\n \nIn this example, if the user just hits return, he enters his normal PRIMARY MENU\nOPTION. If he types 'TST' or '1', he jumps to the "XUS" sign-on in the 'TST'\nUCI (where he must enter another ACCESS CODE). If he types\n'MGR:STA' or '2', he jumps to the 'STA" routine in 'MGR'.\n \nAs before, UCI fields are editable within the "XUSEREDIT" Option of the\n"XUSER" Menu Option in the Kernel (multiple field #20 in File 3).\nwho have PRIMARY MENU OPTIONS to route themselves to different UCIs.\n \nThe XUS and XUS3 routines have been modified, and a new XUINEND1\nroutine exists to wipe out old "UCI" fields that might now be\ninappropriate. XUINIT invokes XUINEND1 It shows any users who currently\nhave "UCI" fields, and who ALSO have "ZJOB" or "PRIMARY MENU OPTION" fields. \nSuch users formerly did not see the "UCI:" question, but they WILL see that\nquestion starting with the installation of KERNEL 4.3 or greater. Hence, the\n"UCI"s for such users should probably be deleted. XUINEND1 will do that\ndeleting automatically, if you answer "Y" to its "...OK? YES//" question.\nThus, a user who customarily gets a restricted Menu Option in the\n"production" UCI might now also be allowed to jump to a "test" UCI\nin which he has different privileges.\n \nA typical sign-on dialogue might now look like:\n ACCESS CODE:\n HIT 'RETURN' TO GET YOUR USUAL OPTION IN 'VAH,AAA', OR SELECT:\n
\n\n", "", "Y\n", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["720", "EC PRO SUM", "Provider (1-7) Summary Report\n", "", "W @IOF\n", "\n** This report is formatted for 132-column output. **\n - Matrix showing how many times a specific procedure was performed on a\n specific patient with the selected provider as Provider 1, Provider 2, \n to Provider 7\n - Modifier(s)\n - Subtotals by procedure\n - Grand Total of procedures\n \nThis option allows you to print/display workload within a specified date\nrange for a selected provider. The output includes:\n \n - Procedure code\n - Procedure name\n - Patient name\n - Last four digits of patient SSN\n
\n\n", "", "", "1995-04-25 07:08:23\n", "", "USER,FIFTYFOUR\n", "", ""], ["721", "ECDSONLINE", "Event Capture Online Documentation\n", "", "W @IOF\n", "\nThe Event Capture Software offers a variety of options for entering and\nreporting data through Event Capture for the Decision Support System. \nYou must have the appropriate security key to see the management and\nspreadsheet menus; otherwise, you will only see the data entry menu\nand selective reports.\n \nThe interactive help portion of this option lets you quickly navigate \nto specific help frames within the Event Capture software by first \nselecting a menu, then selecting the applicable option from that menu.\n
\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: MANAGEMENT
\n- ECMGR
\n \n- \n
- RELATED FRAME KEYWORD: DATA
\n- ECENTER
\n \n- \n
- RELATED FRAME KEYWORD: REPORTS
\n- ECREPS
\n \n
\n
\n", "", "1996-04-01 08:01:00\n", "", "USER,ONE\n", "", ""], ["722", "ECCP1", "Summary of Procedures and Categories (Old File)\n", "", "W @IOF\n", "\n** If your facility currently has Event Capture V. 1.6 installed, you\nshould run the Summary of Procedures and Categories (Old) option to print \ndata from the pilot EVENT CODE SCREENING file (#720.2) for use in \nconverting data to the current data formats. **\n \nThis option allows you to print/display the Event Code Screens for one \nor all DSS Units within a specified location. If DSS Units are \ndefined to group procedures by category, you can select one or all \ncategories. All procedures will print for the selected categories. \n
\n\n", "", "", "1995-05-12 06:17:31\n", "", "USER,ONE\n", "", ""], ["723", "ECBATCH PROC", "Data Entry (Batch) by Procedure\n", "", "", "\nThis option allows you to enter a single procedure for multiple patients \n** Procedures being passed to PCE must have an active Associated\nClinic. Procedures being passed to PCE in association with an OOS DSS \nunit do not require a clinic to be selected, it will automatically\nbe assigned when the entry is added.**\n \nAfter selecting a Procedure, enter the Volume. \n \n***The ECS volume field DOES NOT capture the number of patients seen by \nECS providers.***\n \nas a batch entry.\nVolume is usually associated with the number of procedures performed.\nThe volume field can be used to record and track 3 different values:\n \n1. Number of Procedures: When a selected procedure code CONTAINS inherent\ntime elements (such as "30M Massage Therapy") then a volume of one is\nusually entered, meaning 1 of this specific procedure/service was\nprovided.\n \n OR\n \n \n2. Time: Amount of time shown in increments of minutes (M). When a \nselected procedure code DOES NOT have inherent time elements THEN the\nvolume field is used to capture the time spent completing the\nprocedure/service: 1 = 15M, 2 = 30M, 3= 45M\n \n OR\n \n3. Days: Number of days patient was in VA paid facilities such as State \nHome, DOM, or a Nursing Home. When entering workload for a patient in a \nVA-Paid facility, volume of 1 means 1 day, 2 means 2 days, etc.\n** If only one or no Category is defined for the specified DSS Unit, you \n \nNOTE: It is imperative to understand and keep track of the values you are \nentering in the volume field and what they represent for the patients you \nare treating.\n \nAfter you verify that the procedure information is correct, enter the \nfirst Patient. When you finish entering data for the first patient, \nclick the Add button and repeat until all Patients are entered.\n \n** You must answer exposure and service-connected indicators if fields \ncannot edit Category.**\nare not disabled.** \n \nUse the View button to ensure all data has been entered before completing \nthe entry by clicking the OK button.\n \n** If only one Procedure is defined in the DSS Unit, the Procedure field \nwill be populated. **\n \n
\n\n", "", "", "1997-03-26 09:29:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["724", "PRCH VENDOR TYPE HELP", "VENDOR TYPE HELP\n", "", "", "\nAGENT CASHIER This is the person who dispenses cash.\n \nGSA GENERAL SERVICES ADMINISTRATION.\n \n[Continue]\n \nCOMMERCIAL This is a non-government vendor.\n \nEMPLOYEE This is a person that works in the Department of Veterans\n Affairs, normally at your SITE.\n \nFEDERAL GOVERNMENT This is any federal government agency or office where\n items or services can be purchased.\n
\n\n", "\n- \n\n
\n", "", "1997-01-07 11:35:00\n", "", "USER,ONE\n", "", ""], ["725", "PRCH VENDOR TYPE HELP 2", "VENDOR TYPE HELP SCREEN 2\n", "", "", "\nINDIVIDUALS-OTHER Any person supplying an item or a service that is not\nUTILITY COMPANIES Any company regulated by local or federal government.\n \nVETERANS Anyone that served in the armed services.\n \nCANTEEN The store in a Department of Veterans Affairs facility.\n a Department of Veterans Affairs employee.\n \nOTHER COUNTRIES Any country supplying items or services other than\n the United States of America.\n \nCOMMERCIAL-RECURRING PMTS Any non-government source that will supply goods\n or services on a repetitive basis.\n \n
\n\n", "", "", "1997-01-07 11:37:00\n", "", "USER,ONE\n", "", ""], ["726", "LREPILK", "LINKER HELP\n", "", "", "\n\n Semi-Auto - Looks for entries in that are not currently linked and prompts\n the user to select the corresponding entry in the WKLD CODE\n file.\n \n Should there be no entry in the WKLD CODE file (#64) that the entry in the\n ANTIMICROBIAL SUSCEPTIBILITY file (#62.06) can be linked to please use\n the 'Additional Workload and Workload Codes Suffixes Request Form'\n available in the Emerging Pathogen Documentation (EPI) Patch LR*5.2*132\n\n\n Allows a choice on how to link the ANTIMICROBIAL SUSCEPTIBILITY file (#62.06)\n\n\n with the WKLD CODE file (#64).\n\n Auto - Will attempt to link any entries that are not currently linked.\n\n Manual - This option can create or edit links. Selection is by the\n the entry in the ANTIMICROBIAL SUSCEPTIBILITY file (#62.06)\n\n
\n\n", "", "", "1996-11-29 09:49:37\n", "", "USER,ONE\n", "", ""], ["727", "PSD ORDER ENTRY REG", "", "", "", "", "", "", "1995-05-15 15:13:00\n", "", "USER,ONE\n", "", ""], ["728", "PSD ORDER ENTRY BATCH", "", "", "", "", "", "", "1995-05-15 15:12:00\n", "", "USER,ONE\n", "", ""], ["729", "PSD ORDER ENTRY", "Scheduled/Unscheduled\n", "", "", "\n \n Orders for drugs that are not normally stocked on an NAOU.\n Your orders will be limited to the package amount specified for\n that drug. These can be entered through the Scheduled or\n Unscheduled route.\n \n \n \n \n \n \nScheduled Delivery\n Orders for drugs which are input during the scheduled delivery time. \n \nUnscheduled Pick Up\n Orders that are being requested at an unscheduled time.\n \n \nOne-Time Request\n
\n\n", "", "", "1995-05-25 07:30:00\n", "", "USER,ONE\n", "", ""], ["73", "XUUSER-INQ", "THE 'User Inquiry' OPTION\n", "", "", "\nThis option displays information pertaining to the user selected.\nIf the user is currently signed on, it will show what their job and\ndevice numbers as well as the option(s) they are executing.\nIf the user is not currently signed on, it will show the last sign-on time.\nIf the user has been terminated, the date of termination is displayed.\n \nIn addition, it displays the keys a user holds, as well as a number of\nother attributes from the user file.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["730", "PSD ESIG", "Electronic Signature Code\n", "", "", "\n \nA new feature in CS V. 3.0 is you MUST have an Electronic Signature code.\n \nAt any menu option enter "EDIT E and follow the prompts or type \nin TBOX and chose Edit Electronic Signature Code. \n \nHint: Use your access code as your Electronic Signature Code, this \n will make it easier to remember. \n \n
\n\n", "", "", "1995-06-08 07:13:00\n", "", "USER,ONE\n", "", ""], ["731", "PSD HL7", "Interface to Narcotic Dispensing Equipment Systems\n", "", "", "\n \nAPPLICATION PARAMETER (#771), HL LOWER LEVEL PROTOCOL PARAMETER (#869.2),\nand HL LOGICAL LINK (#870) files. You will be asked to identify an HL7\ndevice which must exist as entry in your DEVICE file (#3.5).\n \n The PSDHLK routine is invoked by the Controlled Substances post-init.\nThe routine, PSDHL7 is also independantly invokable at any time that a site\nneeds to set up their interface for Narcotic Dispensing Equipment Systems.\n \n If you do NOT want to perform this step at the time of the post-init,\nyou can simply D ^PSDHL7 when you're ready.\n Version 3.0 of the Controlled Substances package uses the HL7 package\nto provide a generic interface to Narcotic Dispensing Equipment Systems\n(NDES). HL7 or Health Level Seven is a standard protocol which specifies\nthe implementation of interfaces between two computer applications (sender\nand receiver) from different vendors for electronic data exchange in\nhealth care environments. If your Pharmacy Service is using an NDES such\nas Access, Meditrol, Pyxis, or Suremed you may wish to set up the\ninterface. This will be accomplished by adding entries to the HL7\n
\n\n", "", "", "1996-12-20 09:06:00\n", "", "USER,ONE\n", "", ""], ["732", "PSD HL7 ADT", "PSD PAT ADT PROTOCOL\n", "", "", "\n The PSDHL7 routine is invoked by the Controlled Substances post-init.\nyou can simply D ^PSDHL7 when you're ready.\nThis routine is also independantly invokable at any time that a site needs\nto set up their interface for narcotic dispensing equipment systems. One\nof the steps this routine performs is to add the PSD PAT ADT Protocol to\nthe DGPM MOVEMENT EVENTS driver. When this is done, any admits, transfers,\nor discharges will invoke the PSDADT1 routine to build and transmit an ADT\nmessage using the HL7 package.\n \n If you do NOT want to perform this step at the time of the post-init,\n
\n\n", "", "", "1996-03-29 08:56:00\n", "", "USER,ONE\n", "", ""], ["733", "PSD ORDER ENTRY PRIORITY", "Priority Orders\n", "", "", "\n \nOrders that are being requested at an unscheduled time.\n
\n\n", "", "", "1995-05-15 15:52:00\n", "", "USER,ONE\n", "", ""], ["734", "PSD ORDER ENTRY ONE TIME", "One-Time Requests\n", "", "", "\n \nOrders for drugs that are not normally stocked on an NAOU.\n
\n\n", "", "", "1995-05-18 07:53:00\n", "", "USER,ONE\n", "", ""], ["735", "PSD NURSE RECEIVE", "RECEIVING\n", "", "", "\n \nAfter physically receiving the GS (VA FORM 10-2638), it is important to\nupdate the status on your computer so that your account is correct.\n \n \n
\n\n", "", "", "1995-05-24 14:35:00\n", "", "USER,ONE\n", "", ""], ["736", "PSD NURSE TRANSFER", "TRANSFERRING\n", "", "", "\n \n \nReprint any Green Sheet transferred from your NAOU in place of using\nthe VA FORM 2321.\n -Reprint Transfer Between NAOUs VA FORM 2321 option\nTransferring drugs between NAOUs requires the completion of a 2 step \nprocess!\n \n (1) Transferring the Green Sheet to another NAOU\n -Transfer Green Sheet and Drug to another NAOU option\n \n (2) The Green Sheet being received onto the other NAOU \n -Receive Green Sheet & Drug from another NAOU\n
\n\n", "", "", "1995-05-24 14:43:00\n", "", "USER,ONE\n", "", ""], ["737", "PSD NURSE", "ONLINE HELP FOR NURSES\n", "", "", "\n \n [Order Entry Banner]\n [Filled Not Delivered]\n \n All about Green Sheets\n [Receiving]\n [Completing]\n [GS History]\n [Transfer]\n \n [Electronic Signature Code]\n All about [Dispensing]\n Dispensing\n Report of Dispensing Activity\n Patient ID List Print\n \n All about [Ordering]\n Scheduled/Unscheduled\n One Time Request\n
\n\n", "\n- \n\n
\n", "", "1996-03-18 16:09:00\n", "", "USER,ONE\n", "", ""], ["738", "PSD ORDER ENTRY BANNER", "Order Entry Banner\n", "", "", "\n \nUsed for messages/reminders such as the scheduled pharmacy fill times.\n
\n\n", "", "", "1995-05-16 07:14:00\n", "", "USER,ONE\n", "", ""], ["739", "PSD Green Sheets", "Green Sheet History\n", "", "", "\n \nProvides a detailed account of every transaction affecting a\nVA Form 10-2638.\n
\n\n", "", "", "1995-05-15 15:10:00\n", "", "USER,ONE\n", "", ""], ["74", "XQRESTRICT", "Using the RESTRICT OPTIONS Option\n", "", "", "\n Several restrictions can be placed upon the use of any option\n \n o Adjust the priority of an option so that runs at a lower or\n higher [PRIORITY].\n \n o Disallow the use of an option at certain [TIMES].\n \n o Restrict the use of an option to certain, specified [DEVICES].\n \n o Or any combination of the above restrictions on one or more\n [OPTIONS].\nin the OPTION file. The Site Manager or Security officer can\ndisallow the use of a particular option by:\n \n o Marking that option as '[OUT-OF-ORDER]' so that no one can use \n it.\n \n o Place a [LOCK] on an option so that only those users with the\n proper key can use it.\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["740", "PSD BALANCE ADJUSTMENT REPORT", "Balance Adjustment Report\n", "", "", "\n \n jump, split screen, etc. \nAllows for the selection of drug(s) and a date range for which\nyou wish to review the balance adjustments.\n \nThe Browser:\n \n To view all of the Browser's funcitons press the <F1>H key\n sequence at any time in the browser. This will give you the\n help you need in utilizing the browser to cut, paste, copy,\n
\n\n", "", "", "1995-05-25 12:12:00\n", "", "USER,ONE\n", "", ""], ["741", "PSD NURSE FILLED NOT DEL", "Orders Filled but Not Delivered\n", "", "", "\nThis will list all of the Controlled Substances orders that have been\nfilled but not yet delivered. A summary total sorted by drug is also\nprinted.\n
\n\n", "", "", "1995-06-08 07:10:00\n", "", "USER,ONE\n", "", ""], ["742", "PSD NURSE DISPENSING", "Dispensing to Patients\n", "", "", "", "", "", "1996-02-16 13:03:44\n", "", "USER,ONE\n", "", ""], ["743", "ECPCER", "PCE Data Summary\n", "", "", "\n** This report is formatted for 132-column output. **\n - Procedure name as sent to PCE\n - Volume\n - Provider\n - Location\n - Associated Clinic (Stop Code/Credit Stop/CHAR4 Code/MCA Labor Code)\n - CPT code\n - ICD-10 code\n - Modifier(s)\n \nThis option allows you to print/display procedure data that was sent to\nthe Patient Care Encounter (PCE) software for a selected patient within a\nspecified date range. The output includes:\n \n - Patient name\n - Date Range\n - Date and time of procedure\n
\n\n", "", "", "1997-01-23 00:45:00\n", "", "USER,FIFTYFOUR\n", "", ""], ["744", "GMRV-CIRCUM/GIRTH RATE HELP", "Circumference/Girth\n", "", "", "\nThe entry for circumference/girth must be a number appended with a qualifier\nto represent the value either in the English scale or the Metric system. If\nyou wish to enter a circumference/girth in metric system, append 'C' at the\nend of the number. Add 'I' for inches to represent the value in English\nscale. Some examples of valid entries are:\n \n 41.25I, 41.25i, 72.25C, 72.25c\n
\n\n", "", "", "1996-09-10 10:57:30\n", "", "USER,ONE\n", "", ""], ["745", "GMRV-CVP RATE HELP", "CVP\n", "", "", "\nCVP measurements are documented in cmH2O and mmHG. The default is cmH2O.\nIf the measurement is in mmHg, append 'G' at the end of number. For\nexampl: 34G or 34g.\n \nNormal range: 12-25 mmHg\n
\n\n", "", "", "1996-09-11 10:32:54\n", "", "USER,ONE\n", "", ""], ["746", "GMRV-PO2 RATE HELP", "Pulse Oximetry\n", "", "", "\nThis field stores the patient's oxygen saturation (SaO2) measured by pulse\noximetry. The value is interpreted as a percent.\n Normal values are usually 95-99% but this might vary according to the\ntype of presenting disease, e.g. there are many patients that tolerate a\npulse oximetry of 70-80.\n
\n\n", "", "", "1996-09-11 10:47:10\n", "", "USER,ONE\n", "", ""], ["747", "PRCH BOA", "", "", "", "\nThe BOA number is not correct.\nEnter '??' at 'CONTRACT FLAG' prompt to find more details.\n
\n\n", "", "", "1997-02-28 08:25:00\n", "", "USER,ONE\n", "", ""], ["748", "PRCH CONTRACT FLAG HELP", "", "", "", "\n \n \n If Contract Flag is selected to be a 'C' the 'Contract Number' \n field will accept any characters as Contract #.\n \n \nException: \n Whenever the Source Code of the P.O. is selected to be an 'Open\n Market' the Contract Flag must be set to 'C'. The Contract Number\n field is not allowed to accept the BOA # when Source Code is 'Open\n Market'.\n Contract Flag Field Help\n \n \n The field 'Contract Flag' is an indicator for 'Contract Number'\n (.01) field. It can be a Contract # or BOA # as appropriate. \n \n If Contract Flag is selected to be a 'B' the 'Contract Number'\n field will only accept Alpha or Numeric characters as BOA #.\n
\n\n", "", "", "1997-02-28 08:25:00\n", "", "USER,ONE\n", "", ""], ["749", "ECRPERS", "Inactive/Missing Person Class Report\n", "", "W @IOF\n", "\nThis report will allow users to identify those providers entered as part\nof the patient procedure data entry process that do not have an assigned\nperson or active person class. Patients reported will be those having\nprocedures in the Event Capture system.\n \nYou will be prompted to enter a date range for the procedures entered into\nEvent Capture.\n
\n\n", "", "", "1997-08-26 13:24:32\n", "", "USER,FIFTYFOUR\n", "", ""], ["75", "XQRESTRICT-RESDEV", "RESPONDING TO THE 'RESTRICT DEVICES' PROMPT\n", "", "", "\n You may restrict the use of a particular option to certain devices\nis set to NO or left blank then any devices listed in the PERMITTED\nDEVICES field will be ignored and no device restrictions will be used\nfor the option in question.\n \n Responding to this prompt with an '@' will delete whatever is\nalready in this field, turning the PERMITTED DEVICE restriction off\nfor all of the options selected.\n \non your system. The RESTRICT DEVICES field in the option file, which\nis the field being filled in by this question, is set to either YES\nor NO. This field is used by the system to tell the log-on software\nwhether or not it should look through the list of PERMITTED DEVICES\nwhich is stored in another, multiple field.\n \n If this field is set to YES then only those devices listed in the\nPERMITTED DEVICES will be permitted to use the option. If this field\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["750", "ECRPRSN", "Procedure Reason Report\n", "", "W @IOF\n", "\nThis report will list the reasons entered for Event Capture Procedures.\nand end date to report procedures.\nThe report will include the Location, DSS unit, Procedure Reason, the\nnumber of times the reason was used, Procedure Code, Procedure Name,\nPatient Name, last four digits of patient SSN, Provider Name and Date and\nTime of the procedure.\n \nThe report may be printed for one or selected locations as well as one\nor selected DSS Units. You may also select specific procedure reasons\nor print all procedure reasons. You will also be prompted for a begin\n
\n\n", "", "", "1997-08-26 13:35:23\n", "", "USER,FIFTYFOUR\n", "", ""], ["751", "ECMULT PROC", "Multiple Dates/Multiple Procedures Data Entry\n", "", "W @IOF\n", "\nThis option allows entry of multiple procedures on multiple dates for one \n***The ECS volume field DOES NOT capture the number of patients seen by \nECS providers.***\n \nVolume is usually associated with the number of procedures performed.\nThe volume field can be used to record and track 3 different values:\n \n1. Number of Procedures: When a selected procedure code CONTAINS inherent\ntime elements (such as "30M Massage Therapy") then a volume of one is\nusually entered, meaning 1 of this specific procedure/service was\nprovided.\nor more patient(s). This option does not require the user to exit the \n \n OR\n \n2. Time: Amount of time shown in increments of minutes (M). When a \nselected procedure code DOES NOT have inherent time elements THEN the\nvolume field is used to capture the time spent completing the\nprocedure/service: 1 = 15M, 2 = 30M, 3= 45M\n \n OR\n \noption to change dates or procedures for data entry.\n3. Days: Number of days patient was in VA paid facilities such as State \nHome, DOM, or a Nursing Home. When entering workload for a patient in a \nVA-Paid facility, volume of 1 means 1 day, 2 means 2 days, etc.\n \nNOTE: It is imperative to understand and keep track of the values you are \nentering in the volume field and what they represent for the patients you \nare treating.\n \nThen enter patients and information specific to each patient (Ordering\nSection, Agent Orange, Associated Clinic, etc.).\n \n \n** You must answer exposure and service-connected indicators if fields \nare not disabled.** \n \nSee the User Manual for further details.\nYou may enter any number of procedure dates and then any number of \nprocedures. \n \nAfter selecting a Procedure, enter the Volume. \n \n
\n\n", "", "", "1997-08-26 13:49:49\n", "", "USER,FIFTYFOUR\n", "", ""], ["752", "XUDOC NEW FEATURES*", "KERNEL NEW FEATURES\n", "", "", "\n \nno longer be upgraded as new fields are added, unless you want to do it.\n As changes are made to the Kernel, the major new features will be\nlisted here.\n \n The processing of the [XQUIT] variable by the Menu System has been\nsignificantly changed.\n \n Updates to the Option File required the introduction of a new\nSreen-based Option Editor, [OPED]. The old editor [XUEDITOPT] will\n
\n\n", "\n- \n\n
\n", "", "1998-04-15 20:09:00\n", "", "USER,ONE\n", "", ""], ["753", "XQUIT PROCESSING", "Changes in XQUIT Processing\n", "", "", "\n \n \n 2. The Menu System just stopped and the programmer had no [control]\n over what happened next, while the Menu System itself had no\n idea what the problem was.\n \n 3. The users recieved a [message] about an XQUIT being encountered \n that made little or no sense to them.\n \nWe have corrected these 3 problems. Notice we do not say "3 features."\n During the execution of an [Entry Action] of an option the\napplication programmer has always had the option of setting the XQUIT\nvariable. When the menu system found this variable it would stop. There\nwere 3 major problems inherent in this approach:\n \n 1. The user was [left] at the option where the XQUIT was detected,\n which could well be in the middle of a jump, which caused\n major confusion.\n
\n\n", "\n- \n\n
\n", "", "1998-04-15 13:04:00\n", "", "USER,ONE\n", "", ""], ["754", "XQ XQUTL PRINT", "Simple Kernel Array Printer\n", "", "", "\n \n \n <Return> or <Enter> will cause the next set of lines to be written\n to the screen.\n "B" or "b" will back up to the beginning of the message\n + or - a number will change the screen length by that much. For\n instance "-5" would cause the software to print 15 lines \n at a time instead of 20, and it restarts the print.\n ? will show you this help screen and restart the print.\n ^ has the usual effect of stopping the print.\n A call to PRINT^XQUTL(.array name) will cause the succesive lines of\nthe array to be printed to the screen. When the number of lines printed\nreaches the limit found in IOSL-3, a pause will occurr, and the following\nline will appear:\n \n RETURN to continue, "^" to halt, "B" to backup, or "?" for more options:\n \nAt this point the user can respond in any of the following ways:\n
\n\n", "", "", "1998-04-15 13:09:00\n", "", "USER,ONE\n", "", ""], ["755", "XQUIT MESSAGE", "A Message To The User When An XQUIT Is Encountered\n", "", "", "\n \n You are being returned to:\n '{The menu the user jumped or stepped from}.'\n \n If there is code in the EXQUIT EXECUTABLE field no message is printed\non the assumption that the application programmer has taken care of it.\nIf there is no such code but there is message text in the XQUIT MESSAGE\nfield then that text is displayed instead of the default message through\na Menu System call to [DISPLAY]^XQUTL. The programmer has access to this\nentry point, as well as [PRINT]^XQUTL(.array name) for posting messages on\nthe user's screen. These are both supported entry points.\n When the XQUIT variable is detected by the Menu System and there is\nno code in the XQUIT EXECUTABLE field a message is printed on the user's\nscreen. The default message looks like this:\n \n **> Sorry, access to this option has been denied by the application.\n \n The variable XQUIT was encountered at the option\n '{The menu text of the option that defined XQUIT}.'\n\n\n", "\n- \n\n
\n", "", "1998-04-15 12:48:00\n", "", "USER,ONE\n", "", ""], ["756", "XQUIT CONTROL", "Passing Control To The Application\n", "", "", "\n \n When an XQUIT is encountered this field is executed. If the XQUIT\ndisappears then the Menu Sytem proceeds along satisfying the user's\ninstructions as if nothing happened. If the XQUIT is not killed then the\nuser will be returned to the previous menu. If XQUIT EXECUTABLE is blank\nthen the users will be shown a [message] before being sent back to where\nthey came from. If there is code in this field, however, no message will\nbe printed on the assumption that the application took care of informing\nthe user.\n \n Code can be entered in this field by a programmer, but only by using\n When the Application (Lab, IFCAP, etc.) defined the variable XQUIT in\nthe screen-based Option Editor, [OPED]. It is not supported by the\ntraditional editor XUEDITOPT.\nthe Entry Action of one of their options, control used to pass to the Menu\nSystem and it would prevent the user from running that option. It makes\nmore sense, however, for the application to take control so that problem\nthat caused it to set the XQUIT might be corrected. A new executable\nfield has therefore been added to the Option File to which control will be\npassed. It is called XQUIT EXECUTABLE: ^DIC(19,Option IEN,21).\n \n
\n\n", "\n- \n\n
\n", "", "1998-04-15 11:34:00\n", "", "USER,ONE\n", "", ""], ["757", "XQUIT LEFT", "Leaving The User Dangling. NOT!\n", "", "", "\n \n The reaction of the Menu System has now been standardized: we return\nthe user to the menu from whence he or she came. For instance, if the\nuser is sitting at their Primary Menu -- or any other menu, for that\nmatter -- and they step or jump into an Entry Action that defines the\nvariable XQUIT by setting it equal to something, then the user is returned\nto their Primary Menu or whatever menu they were seeing when they touched\nthe keys last. The Menu System executes the appropriate [headers] and\n[exit actions], just as if the user was jumping back to the original menu.\nOther things happen (see [control] and [message]) but basically it is a\nsimple jump or step back to the original menu by popping the user stack.\n It was very confusing to the user to be left dangling in the middle\nof a jump when the variable XQUIT was defined by the Application in the\nEntry Action Field: ^DIC(19,Option IEN,20). If the user was not jumping\nbut stepping through the menu trees then the Menu System stopping made\nmore sense to them, but if a rubber-band jump ("^^Option name") was in\nprogress then the result was different from either simple jumping or\nstepping.\n \n\n\n", "\n- \n\n
\n", "", "1998-04-21 11:51:00\n", "", "USER,ONE\n", "", ""], ["758", "XQ ENTRY ACTIONS", "Entry Actions\n", "", "", "\n \n The Option File is tree-structured so if you think of a tree with a\nPrimary Menu as its trunk, as you move up the branches the ENTRY ACTION\nfields will be executed at each new option; if you move back down the\nbranch toward the Primary Menu trunk they will not. See [EXIT ACTIONS]\nand [HEADERS], because they will.\n \n If, after an ENTRY ACTION has been executed, the variable XQUIT is\nfound in the partition, then the Menu System passes control to the XQUIT\nProcessing Software described elsewhere. Only after the ENTRY ACTION is\nrun does the Menu System check for XQUIT, and setting it elsewhere is not\n Each option in the Option File has several fields of executable M\npermitted or advised.\n(a.k.a. MUMPS) code associated with it that are executed or run under\nspecific conditions. The ENTRY ACTION Field is one of these and it is\nexecuted each time a new option is pushed onto the user stack. From the\nuser's view this means each time an option is invoked -- whether by the\nselection from a menu, called "stepping into an option", or by jumping to\nthe target option -- this field is executed.\n \n
\n\n", "\n- \n\n
\n", "", "1998-04-15 20:28:00\n", "", "USER,ONE\n", "", ""], ["759", "XQ EXIT ACTIONS", "The Use and Abuse of Exit Actions\n", "", "", "\n \nField will be executed as you move down. "Neither the twain shall\nmeet." The HEADER, by the way, will run no matter which way you are\ngoing. Think of that.\n \n The EXIT ACTION is often used to clean up after an option has been\nrun, sometimes with a call to the Kernel utility KILL^XUSCLEAN. If there\nare variables that the application wishes to protect from this call,\n[protected variables], there is a field in the Option File where these\nvariables may be entered, and they will not be killed.\n Each option in the Option File has an EXIT ACTION Field\nassociated with it: ^DIC(19,{Option IEN},15). This field may contain M\nprogramming code which will be executed each time that this option is\npopped from the user stack. EXIT ACTIONS are the opposite or ENTRY\nACTIONS, not surprisingly.\n \n If you think of a menu as a tree with a Primary Menu trunk, the ENTRY\nACTION will be executed as you move up the branches, and the EXIT ACTION\n\n\n", "\n- \n\n
\n", "", "1998-04-20 09:43:00\n", "", "USER,ONE\n", "", ""], ["76", "XQRESTRICT-DEVICE", "RESPONDING TO THE 'DEVICE' PROMPT\n", "", "", "\n You may respond to this prompt with an exact device name which matches\n \n Devices entered at this prompt become PERMITTED DEVICES for the options\nyou have already selected. If the RESTRICT DEVICES field for a particular\noption is set to YES then the kernel software will look through the list of\nPERMITTED DEVICES to insure that the user can run that option from that\ndevice. If the device being used is not in the PERMITTED DEVICE list the\noption will not work. If the RESTRICT DEVICES field for an option is set \nto NO or is null then no check is made.\n \n When the program encounters a device name preceeded by a minus sign\na device in the DEVICE FILE; a device name preceeded by a minus sign; or\nit will first of all try to remove that device from the list you have\nalready entered. If it cannot find it in that list it will assume that\nit has been entered in a previous session and will attempt to remove it\nfrom the PERMITTED DEVICE list already associated with the options\nselected.\n \n Great care should be used if your system uses port contention as the\n'device' may be somewhat arbitrary from the CPU end. Device restriction\nworks best, of course, with hard-wired devices.\n1, 2, or 3 question marks.\n \n '?' will show you this help screen again.\n '??' will show you the lists of devices you have already selected and\n deselected.\n '???' will show you the DEVICE FILE, which is the list of devices from\n which you may choose.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["760", "XQ HEADERS", "The Execution of Headers\n", "", "", "\n \nagain as you move down toward the trunk. The trunk could also be the\nparent of a secondary menu or XUCOMMAND for the Common Options. So as you\nmove up the tree the ENTRY ACTION and then the HEADER are eexecuted. The\noption does it's thing, exits, and the EXIT ACTION is run. Next comes the\nHEADER of the menu just under the one we are returning from. Notice that\nthe ENTRY ACTION did not get executed on this menu because we are moving\ndown the tree.\n Headers can be associated with each option in the Option File by\nentering valid MUMPS code in to the HEADER Field: ^DIC(19,Option IEN,26).\nFrom the front page of OPED go to "Executables" and answer "YES" to edit\nit. The code in the header field is executed each time an option is\nreferenced on the user stack.\n \n If you think of a menu tree with a Primary Menu as it's trunk, the\nHEADER will be executed as you move up the tree into the branches, and\n
\n\n", "", "", "1998-04-21 12:11:00\n", "", "USER,ONE\n", "", ""], ["761", "XQ OPED", "The Screen-based Option Editor\n", "", "", "\n \n This new Option Editor (OPED) replaces the old text-based editor,\nalthough both editors currently appear on the Menu Management Menu. The\nold editor (XUEDITOPT) was based upon an edit template that became more\nand more difficult to maintain as changes were made to the Option File. \nThis editor will remain available, for the time being, but it will no\nlonger upgraded. All changes to the Option File will, however, be\nreflected in the screen-based OPED. Try it, you'll like it.\n
\n\n", "", "", "1998-04-20 08:53:00\n", "", "USER,ONE\n", "", ""], ["762", "XQ XQUTL DISPLAY", "Displaying the XQUIT MESSAGE Field\n", "", "", "\n \n A call to the supported entry point DISPLAY^XQUTL will take the text\nof the message in the XQUIT MESSAGE Field of the current option load it\ninto a local array, and cause it to be printed on the user's screen\nthrough a call to [PRINT]^XQUTL(.array name). The message used is that\nentered under the current option as specified in the variable XQY, that\nis, ^DIC(19,+XQY,22).\n
\n\n", "\n- \n\n
\n", "", "1998-04-21 11:49:00\n", "", "USER,ONE\n", "", ""], ["763", "XQ XUEDITOPT", "Late Great XUEDITOP Option Editor\n", "", "", "\n \n The traditional way of editing options is still there, but it will\nnot be upgraded. If it does what you want then go for it. If you want\nnew features, you do it by modifying the XUEDITOPT Edit Template.\n
\n\n", "", "", "1998-04-21 12:15:00\n", "", "USER,ONE\n", "", ""], ["764", "XQ PROTECTED VARIABLES", "Protected Variables\n", "", "", "\n \nEditor (^XUEDITOPT), only the newer one OPED. Note also that this field\nis option specific, that is, when a particular option calls KILL^XUSCLEAN\nonly the variables listed in that otion are protected.\n Using the screen-based Option Editor (OPED) you may enter a string of\nvariables protected from a call to KILL^XUSCLEAN in the form: VAR1,VAR2,\netc. From the opening page of OPED go to "Restrictions" and answer\n"YES" to edit this field. The variablers are delimited by commas and\nstored in a field associated with the particular option {^DIC(19,Option\nIEN,"NOKILL")}. \n \n Note that this field is not available through the traditional option\n\n\n", "", "", "1998-04-20 10:14:00\n", "", "USER,ONE\n", "", ""], ["765", "GMRV-PAIN RATE HELP", "Pain\n", "", "", "\nEnter a numeric value using the following pain scale codes:\n \n99=patient unable to respond/communicate pain level.\n 0=patient verbalizes no pain.\n1 to 10= patient verbalizes having pain. Enter the patient's stated pain\nlevel using a scale of 1(slightly uncomfortable/minimal pain) throught\n10(worst imaginable pain). For example: 99 or 5.\n
\n\n", "", "", "1999-02-04 10:12:10\n", "", "USER,ONE\n", "", ""], ["77", "XQSMD-MAIN*", "Secure MenuMan Delegation\n", "", "", "\n This Menu Management system allows the Site Manager to delegate the\nall the chemistry menus to the head of the Chemistry Section, and so \non, creating another [level] of delegation.\n The Site Manager may also [replicate] an existing set of previously\ndelegated options to duplicate the delegation to another user or replace\na delegate who has left or changed jobs.\n Certain menus are judged to be too sensitive to be delegated.\nThey are marked as '[non-delegable]' in the Option File and must be\nallocated by the Site Manager using other methods.\n There are 2 main menus in the XQSMD system. The Manager's menu\ncontains options to create new [delegates], modify their Delegated\nmanagement of certain menu [options] to another user. This user may then\nOptions File, and assign [keys]. The User's menu contains options to\nallow a delegate to assign those options to other users as primary or\nsecondary menu options.\nassign these as primary or secondary options (along with their keys) to\nusers who fall under his or her administrative jurisdiction.\n For example, the Site Manager might delegate the management of the\nlaboratory options to the Lab Application Coordinator (LAC), and the\nLAC could then allocate or remove options from everybody in lab. The\nsystem is set up in such a way that the LAC could also delegate, with\nthe Site Manager's permission and manager's menu, the management of\n
\n\n", "\n- \n\n
\n", "", "1989-04-12 00:00:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["78", "XQSMD-USER", "Creating the List of Users\n", "", "", "\n \n \n At the prompt 'Name: ' you may enter a users name,\n or - preceding a user's name to remove that user\n from the list you are building,\n or ^ to quit and exit the program,\n or ? for a brief help prompt,\n or ?? to see this help screen again,\n or ??? to see a list of Users and Options chosen so far,\n or ???? to see the User File,\n or ????? to get more information about Secure Menu\n You are creating a list of users who will have the authority\n Management Delegation,\n or <RETURN> to begin building the list of options.\n \nand the responsibility to manage a set of options. This list may\ncontain one or more users. In a moment you will begin building the\nsubset of options which will be either added to, or removed from, the\nset of options that the people on this list are allowed to manage.\nAll options specified apply to all people on this list. For instance,\nif you specify a list of 20 people and a set of 5 options to be \nadded, all 20 people will be allowed to manage those 5 options. \n
\n\n", "", "", "1989-01-24 15:19:00\n", "", "USER,ONE\n", "", ""], ["79", "XQSMD-OPTION", "Building Option Lists for MenuMan Delegation\n", "", "", "\n \n alphabetically between OPT1 and OPT2 inclusive,\n or * to select all delegable options,\n or - followed by any of the above to remove options\n you have already selected,\n or ^ to quit and exit the program,\n or ? to see a brief help prompt,\n or ?? to see this help screen again,\n or ??? to see the list of Users and Options chosen so far,\n or ???? to see the Option File,\n or ????? to learn more about Menu Management Delegation.\n You are building a list of options to be added to, or deleted\nfrom, the users you have already specified. You may enter these\noptions in several different ways:\n \n You may simply enter an option name from the Option File,\n or NAM* to specify all options that begin with the\n characters 'NAM',\n or OPT1-OPT2 to specify all the options that fall\n
\n\n", "", "", "1989-01-24 15:06:00\n", "", "USER,ONE\n", "", ""], ["8", "XQHELP-LIST-FORMAT", "HELP FRAME LIST FORMATS\n", "", "", "\nThere are three formats possible for the help frame listings.\n FRAMES a sublist of related frames and keywords for each frame.\n There will be page numbers given for all related frames.\n \n COMPLETE - This format will list the text, cross referenced by page\n number, and also indicate internal names.\n \nYou can specify which you prefer by responding to the 'FORMAT' prompt.\n \n TEXT ONLY- This format will produce a listing of help frame texts.\n The listing will be in the order that the frames are\n encountered traversing the tree.\n \n RELATED - This format will produce a listing of help frames including\n
\n\n", "", "", "1989-01-20 00:00:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["80", "XQSMD-KEYS", "Allocating Keys\n", "", "", "\n \nof the keys that you possess which are needed to run the options\nyou delegated. You will then be asked "Do you wish to proceed Y//"\nIf you answer 'Y' to this second yes/no prompt the keys listed\nwill be awarded to all delegates listed. If you answer 'N' to this\nquestion you will be allowed to add or subtract users and/or keys\nbefore returning to the "Do you wish to proceed" question.\n In order to award a key you must first possess the key yourself.\nIf an option that you have delegated is locked with a key you do\nnot own the option will remain locked. Keys, like options, may\nbe distributed through regular channels as well as through this\n At least one of the options you have selected has been locked\nMenuMan Delegation system.\nwith a key that you possess. You may now award the key(s) required\nto the delegates you have selected if you want to. If you answer\n'Y' to this prompt you will branch to the key distribution program.\nIf you answer 'N' to this prompt no key distribution will be \nattempted.\n Should you choose to allocate keys at this time by answering 'Y'\nyou will see a list of the delegates you have selected and a list\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["81", "XQSMD-REPLICATE", "Replicate an exsisting user's delegated options\n", "", "", "\n You may choose to copy the Delegated Options of one user\nset of options. If you say yes ('Y') all Delegated Options\nwill be removed from John Smith and he will no longer be an\nactive delegate.\n In order to remove the options from the first user, John\nSmith, in this case, you must have a [Delegation Level] lower \nthan John Smith. Your Delegation Level is a number indicating the\nsteps in the delegation process you are away from the original\ndelegation of the Site Manager. The Site Manager will have a\nlevel of 0 (zero). When she delegates options to someone that\nperson will have a Delegation Level of 1. If, in turn, that \nto another user. For instance, if John Smith has been\nperson further delegates options recieved from the Site Manager\nto a third person that person will have a level of 2, and so forth.\ndelegated a set of options to manage you may choose to\ndelegated that same set of options to another user, say,\nMarcie Madona.\n You will also be asked if, after the options set has\nbeen delegated to the second user, Marcie Madona in the example,\nthose options should be removed from the first user (John\nSmith). If you say no ('N') John Smith will retain the\n\n\n", "\n- \n
\n- \n
- RELATED FRAME KEYWORD: DELEGATION LEVEL
\n- XQSMD-LEVEL
\n \n
\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["82", "XQSMD-REMOVE", "Remove all options from a user\n", "", "", "\n If you answer yes ('Y') to this prompt all of the options\ntrying to remove from the Delegation System. If you do not,\nthe existing delegate will retain the options already delegated\nto her. Delegation Level may be changed by a programmer using\nFileMan. The Delegation Level is automatically set to the number\nof steps a delegate is away from the original delegation of the\nSite Manager.\nthat have been delegated to this user will be removed after\nthey have been transferred to a second user. In this way\na new delegate will take the place of the former delegate\nand the former delegate will no longer have any options to\nmanage.\n In order to remove all options from an existing delegate you\nmust have a Delegation [Level] in the User File that is numerically\nlower than the Delegation Level of the person that you are\n\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["83", "XQSMD-REPLACEMENT", "Moving a set of Delegated Options to a new user\n", "", "", "\n The user you are being asked to identify will recieve all of\nmenu options. He will also be able to create new menus which\ncontain the options he has been delegated.\n The menu options that you are transfering to this user will not\nreplace any options the user has been previously delegated. They\nwill be added to those options, if any.\nthe options now delegated to the user you previously specified.\nNote that you will later be allowed to add or subtract options\nfrom this list and even specify yet another user to recieve this\nsame set of options.\n You may enter a user's name or DUZ. You may also enter an '^'\nto exit from this program with no action taken.\n The person you here specify will be allowed to assign the options\ndelegated to him to other users either as primary or secondary\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["84", "XQSMD-OK", "Do we understand each other?\n", "", "", "\n This question is giving you one, last chance to verify\nwill be taken and the program will cycle back to choose\nanother user who's options you wish to transfer, etc.\n After you have answered yes to this prompt, and after\nall of the options of the first user have been removed\n(if you choose to remove them) then you will be shown\nthe list of options you have specified and allowed to\nadd or subtract options from this list and/or specify\nyet another user who will be delegated the options in the\nfinal list.\nwhat you are about to do. If you answer yes ('Y') you\nwill transfer the options currently held by the first\nuser you specified to the second user you chose. In\naddition, if you have answered yes to the question:\n"Should ALL delegated options be removed...." the \noptions currently held by the first user will be removed\nfrom him and he will no longer be a delegate of anyone.\n If you answer no ('N') to this prompt then no action\n\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["85", "XQSMD-LEVEL", "Delegation Level\n", "", "", "\n The Delegation Level of a particular delegate is a field\n No attempt is actually made to determine who actually\nworks for whom since those data are not available to the\nsoftware. Delegation chains should therefore be constructed \nwith some care.\n In order to modify the set of options delegated to a \nparticular person you must have a Delegation Level equal to,\nor less than, the person you are trying to modify. \n If you create a new delegate by delegating some (or all)\nof the options delegated to you that person will have a Delegation\nLevel equal to your level +1.\nin the User File that contains a number specifying the number\n It may be necessary to modify Delegation Levels using the\nVA FileMan as the organization's stucture changes over time.\nof steps that that person is away from the original delegation\nof options by the Site Manager (who's Delegation Level is 0)\n For instance, if the Site Manager delegates all laboratory\noptions to the Lab Application Coordinator (LAC), the LAC\nwill have a Delegation Level of 1. Should the LAC further\ndelegate a set of those options to the Chief of Chenistry, \nthe Chief would have a level of 2, and so on.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["86", "XQSMD-NONDEL", "'Non-delegable' options\n", "", "", "\n Certain options, such as Programmer's Options, are considered\nis the responsibility of each site to insure that the security\nof that system is not violated.\n It should be noted that a higher level option, such as 'EVE'\nwould still give the delegate access to lower level options, SUCH\nas 'XUMAINT' even though 'XUMAINT' is itself marked in the Option\nFile as 'Nondelegable'. The Delegation software does not follow\nthe options trees down to insure that options of options are not\ndelegable.\ntoo sensitive or powerful to be delegated. They are marked as\n'not delegable' in the option file, and the Secure MenuMan\nDelegation software will not delegate these options. The tradi-\ntional methods of assigning these menu options must be employed\nby the Site Manager.\n It is highly recommended that the Site Manager, Security\nOfficer or IRM Chief review the options so marked and add, using\nthe VA FileMan, any locally sensetive options to this list. It\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["87", "XUDOC DEVICE HUNTGROUPS*", "DEVICE HUNT GROUPS\n", "", "", "\nHunt groups associate printing devices that can share work. If one printer\nAs you assign devices to hunt groups, note that a device, or rather a Device\nFile entry, may only belong to one group. Also note that you may create a\ngroup with members from different CPUs to handle such tasks as Network mail.\n \nis busy the job will be routed the next available printer in the hunt group.\n \nYou decide which printers to group. For example, your registration area may\nhave two similar printers that can be used interchangeably. Pick a name\nfor your hunt group, like ADMITAREA. Then add devices to the group by\nusing the appropriate hunt group option. Now try sending output to one of\nthe printers while it's busy to see the other one act in its place! \n \n
\n\n", "", "", "1992-04-15 11:53:00\n", "", "USER,ONE\n", "", ""], ["878", "XM-U-M-PRIORITY SEND", "SENDING MESSAGES WITH A PRIORITY STATUS\n", "", "", "\n \ntake precedence over any other mail in another recipient's mailbox.\nBecause of that, MailMan notifies recipients when they have priority mail\nand highlights that mail in their list of messages (i.e., places an\nexclamation point ('!') to the left of each priority message).\n \nNo [FORWARDING] is allowed to mail groups except by the sender of the\nmessage. MailMan also provides recipients with the ability to control how\nresponses to priority mail are handled through the PRIORITY RESPONSES [FLAG]\nand the PRIORITY RESPONSES [PROMPT] fields in the User Options Edit option.\n \nYou can use the Priority Delivery action code (i.e., 'P') to send a\nTo send a priority message, enter a 'P' at the 'Select Message option:\nTransmit now//' prompt.\nmessage as priority. This is a toggle action code. If you enter 'P' again,\nthe message will not be sent as priority. Priority messages are not sent\nbefore other messages. However, when recipients are reading new mail,\npriority messages are displayed first.\n \nMailMan allows users to send a message as priority mail. By sending mail\npriority, the sender indicates the message is very important and should\n\n\n", "\n- \n\n
\n", "", "2002-07-18 13:48:00\n", "", "USER,ONE\n", "", ""], ["879", "XM-U-I-SHARED MAIL", "SHARED,MAIL - A LIBRARY OF MESSAGES\n", "", "", "\n \nprivileges. Therefore, the surrogate is able to read any piece of mail in\nany SHARED,MAIL basket, and they can respond to any message. However, in\nthe case the user has been assigned the XMNOPRIV key, they cannot access\nSHARED,MAIL.\n \nAll users can send messages to SHARED,MAIL as they would send them to any\nother user. However, messages sent to SHARED,MAIL must be given 'Automatic\nDeletion Dates' and be sent to a particular basket so that readers can\nmore easily find them.\n \nSHARED,MAIL is a good way to distribute data, request help, and search for\nSHARED,MAIL never has any new messages.\nthings you need.\n \nAfter you choose the Become a Surrogate (SHARED,MAIL or Other) option and\nif another MailMan user has not designated you as a [SURROGATE], you are\nautomatically made a surrogate of SHARED,MAIL.\n \nAs a surrogate to SHARED,MAIL, the user is only allowed Read access\n
\n\n", "\n- \n\n
\n", "", "1993-12-22 14:10:00\n", "", "USER,ONE\n", "", ""], ["88", "XUDOC DEVICE HUNTGROUP TECH", "TECHNICAL OVERVIEW: HUNT GROUPS\n", "", "", "\nObsolete help frame.\n
\n\n", "", "", "1992-04-15 11:23:00\n", "", "USER,ONE\n", "", ""], ["880", "XM-U-M-VAPORIZE DATE EDIT", "VAPORIZE MESSAGE WITH AUTOMATIC DELETION DATE\n", "", "", "\n \n\nVaporize dates set by MailMan (during the IN-BASKET PURGE) remain with\nthe message only as long as the message remains dormant, or until the\nmessage is deleted. As soon as you read the message or save it to another\nbasket or it becomes new, the vaporize date will be removed.\n \nA message that is scheduled for vaporization will be deleted on the scheduled\ndate. However, you are free to modify or remove the AUTOMATIC DELETION DATE\n(i.e., Vaporize Date) at any time prior to the vaporization date.\n\nYou can use the Vaporize Date Edit action code (i.e., 'V') to set a\n [MORE]... \nmessage or group of messages to be deleted from your mailbox at a\nspecific date and time or to modify a Vaporize Date already set.\nVaporize means automatically delete.\n \nVaporize dates set by you (or by MailMan during message delivery) remain with\nthe message until the message is deleted or until you remove the vaporize date.\nThe vaporize date remains in effect even if the message becomes new.\n
\n\n", "\n- \n\n
\n", "", "2000-06-07 15:26:00\n", "", "USER,ONE\n", "", ""], ["881", "XM-U-I-GROUP MEMBER", "MEMBERS OF MAIL GROUPS\n", "", "", "\n \n \n DISTRIBUTION LIST - Distribution Lists can be set up through VA FileMan.\n A Distribution List has a name and a list of\n domains. If a Distribution list is a member of a\n Mail Group (and more than one can be) then the\n expansion of it will cause the message to be sent to\n the Distribution List name at each of the domains in\n the list. [PRIVATE] Mail Groups, however, cannot\n contain Distribution Lists.\n \nMail Groups can contain any combination of the following types of members:\n REMOTE - Members that are in none of the other categories.\n \n LOCAL - Members that are individuals that use the local\n system.\n \n MEMBER GROUP - A mail group may be a member of other mail groups.\n More than one mail group can concurrently be members\n of the same mail group.\n
\n\n", "\n- \n\n
\n", "", "1993-12-06 20:02:00\n", "", "USER,ONE\n", "", ""], ["882", "XM-U-M-WRITE", "SENDING A NEW MESSAGE INSTEAD OF A REPLY\n", "", "", "\n \nmessage you are reading. Rather than having to go through the Send a Message\noption, you could simply enter the Write action code.\n \nThe 'Write' command allows you to compose a new message, address it to a\nseparate set of [RECIPIENTS], and deliver it. After composing and sending\nyour message, MailMan will automatically return you to the original\nmessage where you can continue with your reading.\n \nTo write and send a new message while reading another message, enter a 'W'\nat the 'Enter message action' prompt.\nYou can use the Write action code (i.e., 'W') to 'write' (compose) a new\n \n[MORE]... \nmessage while reading a message. The steps of creating a message using the\nWrite action code are the same as if you used the [SEND] a Message option.\n \nUse the Write action code to immediately send a message while reading another\nmessage. For example, if after reading a message, you suddenly remember that\nyou need to send a message about an unrelated matter to somebody else or if\nyou just want to send a message to the sender or one of the recipients of the\n
\n\n", "\n- \n\n
\n", "", "1999-04-28 07:19:00\n", "", "USER,ONE\n", "", ""], ["883", "XM-U-I-EDITOR FM LINE", "VA FILEMAN LINE EDITOR\n", "", "", "\n \n * Add Lines * Join List Line(s)\n * Break a Line * Move Line \n * Change Every String * Print Line(s)\n * Delete Line(s) * Repeat Line(s)\n * Edit a Line * Search & Transfer\n * Insert Line(s)\n \nThe Transfer command allows you to use all VA FileMan text fields (via\nextended references) and especially MailMan messages as a scratch pad. To\nuse the Transfer command enter a 'T' after the 'Edit option:' prompt and\nWhen using the Line Editor, one line is entered at a time, with a carriage\nenter a message subject, internal message identification number, or an\nextended reference to any other file with a TEXT field.\nreturn being entered at the end of each line. Line numbers which appear at\nthe left of the screen are used for reference while editing and are not\npart of the message. When the entire message is entered, the user enters a\ncarriage return at the line number of the next line. The 'Edit Option:'\nprompt then appears. Entering '??' will display the editor options, which\ninclude:\n \n
\n\n", "", "", "1999-01-20 16:19:00\n", "", "USER,ONE\n", "", ""], ["884", "XM-U-B-XMIT PRIORITY TOGGLE", "TOGGLING MESSAGE TRANSMISSION PRIORITY\n", "", "", "\n \ncould be very unimportant (i.e., it should let the others go first).\n \nMailMan usually sends out the messages in the queue according to their date\nof creation. However, the POSTMASTER may use the 'toggle transmit priority'\ncommand (i.e., 'X'), to change the transmit priority. Thus, some messages\ncan be flagged to transmit before the rest (high priority), while others can\nbe flagged to transmit after the rest (low priority).\n \n[MORE]...\nMessages waiting to be sent to remote domains are placed in special baskets\nowned by the POSTMASTER. We call these the transmit queues. The POSTMASTER\nis able to manipulate, to a certain degree, the order in which they are sent.\n \nSometimes, messages stack up in the transmit queues waiting to be delivered.\nOne or more of these messages could be very important (i.e., it needs to go\nfirst). For example, one of the messages could be a site's payroll data\ndestined for FOC-AUSTIN.DOMAIN.EXT. Conversely, one or more of these messages\n
\n\n", "\n- \n\n
\n", "", "2002-02-22 12:28:00\n", "", "USER,ONE\n", "", ""], ["885", "XM-U-M-PRIORITY TOGGLE", "PRIORITY REPLIES TOGGLE\n", "", "", "\n \n'Enter message action' prompt.\n \nThe PRIORITY RESPONSES [FLAG] field is available through the User Options\nEdit option located on the Personal Preferences menu. It controls the\ndelivery of responses to messages with a priority status.\n \nIn addition, you can also control whether or not you are prompted in the\nfirst place by editing the PRIORITY RESPONSES [PROMPT] field also\navailable through the User Options Edit option located on the Personal\nPreferences menu.\nWhen messages are sent with a priority status, recipients can control\nwhether future responses will be delivered as priority on a message by\nmessage basis.\n \nYou can use the Priority Replies Toggle action code (i.e., 'K') to switch\nfrom receiving responses to a priority message as priority or not\ndepending on how you set your PRIORITY RESPONSES [FLAG]. To toggle between\n'Responses are ORDINARY' and 'Responses are PRIORITY', enter a 'K' at the\n
\n\n", "\n- \n\n
\n", "", "1992-09-30 16:13:00\n", "", "USER,ONE\n", "", ""], ["886", "XM-U-M-ANSWER", "ANSWERING A MESSAGE (INTERNET STYLE)\n", "", "", "\n \n 2. The text of your answer.\n 3. The three lines of your Network Signature.\n \nWhen you answer a message the original message is copied before you are\nplaced in the editor. Thus, 'Answer' first copies the original message,\nadds your network signature, and then puts you into the editor. Once\nyou're finished with your answer, it is sent as a separate message to the\nsender of the original message.\n \nIn order to use the Answer command, you must have a [NETWORK SIGNATURE].\nYou can use the Answer action code (i.e., 'A') to answer a message. While\n \nTo 'Answer' a message, enter an 'A' at the 'Enter message action' prompt.\n[REPLYING] to a message chains the new response to the original message,\nthe Answer command issues a new message to send to the sender of the original\nmessage, a new message that will not be chained to the original message.\n \nThe 'Answer' message consists of three components in the following order:\n \n 1. A copy of the message being answered.\n
\n\n", "\n- \n\n
\n", "", "1999-04-28 06:57:00\n", "", "USER,ONE\n", "", ""], ["887", "XM-U-H-Q DISAPPEARED", "'DISAPPEARED' MESSAGES WHICH HAVE NOT BEEN DELETED\n", "", "", "\n \ntext you've already seen.\n \nHowever, the text is there. At the 'Enter message option' prompt, respond\nwith a 'B' for [BACKUP]. You can then choose the reply you wish to read.\nEnter zero ('0') to see the original message.\nSometimes the [READ] option will show only the message header without\nthe text. What happened to the original message?\n \nMessages will not 'disappear' unless you specifically [DELETE] them.\n \nAfter a message has been read, replied to, and the reply has been read,\nthe message text will no longer be displayed automatically when you\nattempt to read the message. This is to avoid forcing you to read thru\n\n\n", "\n- \n\n
\n", "", "1993-10-23 16:49:00\n", "", "USER,ONE\n", "", ""], ["888", "XM-U-I-GROUP COORDINATOR", "MAILMAN MAIL GROUP COORDINATORS\n", "", "", "\n \nMailMan allows for package coordinators to establish and edit mail groups.\nHowever, this option does not allow coordinators to edit mail groups they\ndid not create.\n
\n\n", "", "", "1993-11-26 11:53:00\n", "", "USER,ONE\n", "", ""], ["889", "XM-U-M-INFO ONLY", "MESSAGES MARKED AS INFORMATION ONLY\n", "", "", "\n \noption: Transmit now//' prompt.\n \nIn addition to making the entire message Information Only, you can also\nsend a message as Information Only to just one individual recipient.\nDuring the addressing portion of the message for a recipient, by\nspecifying the [PREFIX] 'I:xxx' (where 'xxx' represents the recipient's\nname) after the 'And Send to:' prompt, you are telling MailMan to deliver\nthe message to this individual recipient as Information Only.\nYou can use the Information Only action code (i.e., 'I') to send a message\nas Information Only. Sending a message Information Only prevents all\nrecipients from [REPLYING] to your message. (You, the sender will still\nbe able to reply to the message.) Messages can have an Information Only\nstatus placed on them by the sender at anytime. This is a toggle action\ncode. If you enter 'I' again, the message will no longer be Information Only.\n \nTo send a message Information Only, enter an 'I' at the 'Select Message\n
\n\n", "\n- \n\n
\n", "", "2002-07-18 13:53:00\n", "", "USER,ONE\n", "", ""], ["89", "XUDOC DEVICE LOOKUP", "DEVICE LOOKUP\n", "", "", "\nThere are several ways to select a device when using the Device Editor\n DEVICE NAME Logical device name (.01 Field of the Device File).\n \n PORT/DEVICE $I Physical port connection on the residing CPU.\n \n VOLUME SET/CPU The volume set or central processing unit.\n \n SIGN-ON SYSTEM Flag indicating whether the device can be used to\n sign-on and access the computer system.\n \nThe Device File is cross-referenced which is the [TECHNICAL INFORMATION]\noptions. They are ways of responding to the following prompt:\nused to provide these four alternative lookup methods.\n \n Select DEVICE NAME:\n \nWhen you enter the name of a device, a lookup is done on the Device File\nto find a device by that name. Along with name, there are several other\ndevice attributes that can be used for lookup:\n \n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["890", "XM-U-M-PRINT DEVICE P-MESSAGE", "P-MESSAGE DEVICE\n", "", "", "\n \nor the 'Postmaster'. If it's from yourself, it will NOT be delivered 'new'\nto you, but you will be able to edit it, if you send it ONLY to yourself.\nIf you choose to have it come from the Postmaster and send it to yourself,\nit will be delivered 'new' to you, but you will NOT be able to edit it.\n \nYou can set the [P-MESSAGE FROM] default using the User Options Edit\noption on the Personal Preferences menu.\nRather than printing information (e.g., a report or listing) to the screen\nor a printer, the P-MESSAGE device can be used to send a mail message to\nyourself and/or others that contains the information.\n \nFor example, you may want to keep a copy of a report by sending it to\nyourself in a mail message by directing the report to the P-MESSAGE device.\n \nMailMan gives you the choice of having the message come from yourself\n
\n\n", "\n- \n\n
\n", "", "1999-02-13 10:36:00\n", "", "USER,ONE\n", "", ""], ["891", "XM-U-B-NEW MAIL LIST", "LIST OF NEW MESSAGES IN A BASKET\n", "", "", "\n \nThe New Message List action code (i.e., 'N') will just display the new\nmessages from a list of messages in a mail basket. This can be useful if\nyou have a mail basket with a large number of messages and you just want\nto see/read the new messages.\n \nTo list just the new messages in a mail basket, enter an 'N' at the 'Enter\nmessage number or command:' prompt.\n
\n\n", "", "", "1993-12-22 15:39:00\n", "", "USER,ONE\n", "", ""], ["892", "XM-U-H-USER", "USER INFORMATION\n", "", "", "\n \n * Banner - The user's current MailMan banner, if any has been entered using\n the User Options Edit option located on the Personal Preferences menu.\n \n * General MailMan Information - The last date and time the user used\n MailMan and the status of messages in their mailbox.\n \n * Introduction - The user's introduction, if any has been entered using\n the User Options Edit option located on the Personal Preferences menu.\n \n * Office Information - The user's office information, if any has been\nMailMan gives you the opportunity to obtain information on a local MailMan\n entered using the User Options Edit option located on the Personal\n Preferences menu.\n \n * Mail Group Information - A list of the mail groups to which this user\n belongs, if any.\n \n * Surrogate Information - A list of the MailMan users for whom and in\n what capacity (i.e., privileges) this user may act as a surrogate, if\n any. Also, a list of MailMan users who can be surrogates for this user\n and in what capacity (i.e., privileges).\nuser through the User Information option on the Help (User/Group Info.,\n \nTo display general information on a local MailMan user, choose the User\nInformation option on the Help (User/Group Info., etc.) menu.\netc.) menu option located on the main MailMan Menu.\n \nYou can obtain the following local user information:\n \n * Name - The MailMan user's name.\n \n
\n\n", "", "", "1999-01-19 13:37:00\n", "", "USER,ONE\n", "", ""], ["893", "XM-U-M-LATER", "MAKE MESSAGES NEW LATER\n", "", "", "\n \nwill be redelivered to your mailbox as a 'new' message.\n \nMailMan gives you the option to review ([LIST]) all messages with\n'latered' dates and times using the Report on Later'd Messages option and\nmake any modifications to those dates and times using the [CHANGE]/Delete\nLater'd Messages option. Both of these options are available on the Other\nMailMan Functions menu.\n \n[MORE]... \nYou can use the Later action code (i.e., 'L') to have messages made 'new'\nat a specified later date and time. Use this action to remind yourself of\nimportant activities. Users can schedule a reminder now and not worry\nabout remembering to do it later. MailMan will act as though it were a\npersonal reminder.\n \nIf the message already resides in your mailbox, it will simply be made\n'new' again. However, if the message no longer resides in your mailbox, it\n
\n\n", "\n- \n\n
\n", "", "1991-10-03 08:55:00\n", "", "USER,ONE\n", "", ""], ["894", "XM-U-K-PACKMAN SUMMARIZE", "SUMMARIZE PACKMAN MESSAGE\n", "", "", "\n \nThe PackMan option for Displaying a summary of a PackMan message does just\nthat. Packages (and their parts), Routines, Globals (anything that can be\nloaded) will be listed as in the message when this option is chosen.\n
\n\n", "", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["895", "XM-U-K-PACKMAN COMPARE", "COMPARE PACKMAN MESSAGE ROUTINES AGAINST THOSE INSTALLED NOW\n", "", "", "\n \nThe PackMan Compare option will check the data in the PackMan message\nagainst the routines, globals, data dictionaries on disk, and list out all\ndifferences.\n
\n\n", "", "", "1991-07-16 06:31:00\n", "", "USER,ONE\n", "", ""], ["896", "XM-U-K-PACKMAN LOAD GLOBALS", "LOADING GLOBAL DATA INTO A PACKMAN MESSAGE\n", "", "", "\n \nMailMan allows global data to be loaded into a message and saved there or\ntransported via Network Mail. The data must conform to VistA standards in\norder to ensure that this option will work properly. When the global data\nis loaded, the address is put onto one line and the data for that address\nonto a second line. Global data can be secured, but not scrambled. It can\nbe reinstalled. Do not expect MailMan to be able to make a backup message\nproperly when installing global data.\n
\n\n", "", "", "1991-07-16 06:30:00\n", "", "USER,ONE\n", "", ""], ["897", "XM-U-K-PACKMAN INSTALL", "INSTALLING A PACKMAN MESSAGE\n", "", "", "\n \nand if the sums do not match, the message cannot be installed.\nPackMan messages can be installed by using the Install option under the\nPackMan options by entering an 'X' at the 'Enter message option' prompt.\nInstalling a message will replace the data on disk, but a BACK-UP message\ncan be created before the installation takes place. Automatic BACK-UP is\nprompted for before installation is allowed.\n \nIf a message is secured, a security check takes place during the\ninstallation. The message is checked against previously calculated sums,\n
\n\n", "", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["898", "XM-U-K-PACKMAN LOAD PACKAGE", "LOADING AN ENTIRE PACKAGE INTO A PACKMAN MESSAGE\n", "", "", "\n \nmessage. In this way a message can be created, secured, and sent as a part\nof a DIFROM and the creator need never invoke a separate MailMan process.\n \nStoring a message directly into a message offers the following advantages:\n \n 1. The message can be sent over the network faster. It is shorter.\n 2. The message can be secured.\n 3. The security is checked at installation.\n 4. The installation goes directly from the message into the INIT saving\n steps for the installer.\nNOTE: KIDS is the preferred method for transporting packages.\n 5. The installer need never be in programming mode since the install\n does not require any direct mode code.\n\nYou cannot actually load an entire package through MailMan from MailMan.\nThis is an option given to the creator of a set of INITS for a package\nduring a DIFROM. This is a somewhat complex option, but the programmer\nneed only answer that s/he wants the set of information he is compiling\nvia a DIFROM to be loaded into a message. He or she will then be prompted\nfor a Subject for the message and asked whether or not to secure the\n
\n\n", "", "", "2002-05-02 07:06:00\n", "", "USER,ONE\n", "", ""], ["899", "XM-U-K-PACKMAN PRINT", "PRINTING PACKMAN MESSAGES\n", "", "", "\n \nThere is a special option for printing PackMan messages. This is available\nunder the PackMan option (X) at the 'Enter message option' prompt. This\nprint is particularly useful for routines that are reformatted so that the\ntags and lines of code are functionally aligned.\n
\n\n", "", "", "1991-07-16 06:39:00\n", "", "USER,ONE\n", "", ""], ["9", "XQHELP-XREF", "USING THE 'Cross reference Help Frame' OPTION\n", "", "", "\nThe 'Cross Reference Help Frame' option will produce a listing of\n with a '?' from the menu driver.\n \nRoutines - all routines which invoke this help frame.\nall help frames for the specified package prefix.\n \nFor each frame it will show the following information:\n \nParent frames - all the help frames which have text which reference\n this one.\n \nMenu option - all the menu options which could invoke this help frame\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["90", "XUDOC DEVICE LOOKUP TECH", "TECHNICAL OVERVIEW: DEVICE LOOKUP\n", "", "", "\nThe Device Name, .01 Field of the Device File, may be used for lookup.\n \n Select DEVICE NAME: BBB.75\n \nDevices are also cross-referenced by the flag which indicates whether\nit is a sign-on system device. Entering 'SYS' will display all devices\nwith the flag set to 'yes'. This may be combined with the CPU and $I\nas above to futher limit the lookup choices:\n \n Select DEVICE NAME: SYS.BBB.75\n \nIf several names match the character string entered, a choice is presented.\nThese lookup methods are possible since the Device File contains a number\nof cross-references: by name, $I, Volume Set(CPU), and Sign-on/System.\n \nThe device $I (port number) may also be used for lookup. The search will\nfind all devices on all volume sets/CPUs that use a port of this number.\n \nSpecifying the volume set/CPU will narrow the lookup search. Entering\nthe CPU name will display a choice of devices on that CPU. Entering the\nCPU name and $I, separated by a decimal point, will shorten the list:\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["900", "XM-U-K-PACKMAN LOAD ROUTINES", "LOADING ROUTINES INTO PACKMAN MESSAGES\n", "", "", "\n \nRoutines can be loaded into a PackMan message. If secured, the message\ncannot be edited. The installation feature will recognize message\ncorruption and automatically notify the installer, and perhaps, even abort\nthe installation process.\n \nOnce they are in a message, the [PRINT] option in PackMan does a much\nbetter job of formatting the output.\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["901", "XM-U-A-INFO ONLY", "ADDRESSING A RECIPIENT AS INFORMATION ONLY\n", "", "", "\n \nRecipients who are addressed as 'Information Only' cannot respond to\nthe message.\n\nTo indicate an 'Information Only' addressee, prefix the\naddressee with 'INFO:' or 'I:' (e.g., 'I:SMITH,JOHN', or 'I:G.GROUP').\n \nNOTE: The sender of a message can always respond to it.\n
\n\n", "", "", "1999-01-20 06:58:00\n", "", "USER,ONE\n", "", ""], ["902", "XM-U-A-CC", "ADDRESSING A RECIPIENT AS 'CARBON COPY'\n", "", "", "\n \nA recipient who receives a message as a 'CARBON COPY' ('cc:') knows that\na response is not expected. However, there are no limitations on the\nrecipient. A [QUERY] of the message shows this recipient as 'cc:USER,NAME'.\n \nTo address a message to someone in this manner prefix the address with 'CC:'\n(e.g., 'CC:SMITH,R').\n\n\n", "\n- \n\n
\n", "", "1999-01-20 07:01:00\n", "", "USER,ONE\n", "", ""], ["903", "XM-U-M-PRINT NO HEADER", "HEADERLESS PRINTING\n", "", "", "\n \n detailed recipient list.\n \n - MailMan will then ask you what you want to print. The default\n response will always be to print the original message and all\n responses. However, you can choose to print any [COMBINATION] of\n responses (single or range), with or without the original message.\n \n[MORE]... \nThe Headerless Print action code (i.e., 'H') allows you to print individual\nmessages or a group of messages in a mail basket without a header: \n \n * Printing Individual messages - After reading a message, enter an 'H'\n at the 'Enter message action' prompt.\n \n - MailMan will first ask if you want to print a recipient list. If\n you choose to print recipients, you can print either a summary or\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 09:48:00\n", "", "USER,ONE\n", "", ""], ["904", "XM-U-M-COPY-2", "RESPONSES TO THE COPY OPTION PROMPTS\n", "", "", "\n \n addresses the message to the same recipients. Recipients may be\n added or deleted from the message at the 'And Send to' prompt.\n \n * At the 'Select the responses to copy: 0//' prompt, you can enter the\n original message (default, zero) and/or any [COMBINATION] of\n responses you wish to include. If the message you are copying doesn't\n have any responses, MailMan will automatically copy the original\n message and not prompt you to choose any responses. If you are unsure\n of the responses to include, MailMan lets you enter two question\n marks at the 'Select the responses to copy: 0//' prompt in order to\nOptions for copying a message are as follows:\n display an index of respondents to the message.\n \n * At the 'List original recipients in text?' prompt, entering 'YES'\n inserts the recipient list at the end of the copied text.\n The recipients are those to whom the original message was forwarded\n or sent.\n \n * At the 'Deliver to the same recipients?' prompt, entering 'YES'\n
\n\n", "\n- \n\n
\n", "", "1999-01-22 14:11:00\n", "", "USER,ONE\n", "", ""], ["905", "XM-U-Q-SEARCH", "SEARCHING FOR MESSAGES\n", "", "", "\n \n * Search for messages anywhere in your [MAILBOX].\n \nWhen searching for messages, you can specify a variety of search [CRITERIA].\nThe MailMan interface provides the Query/Search for Messages option for you\nto search for messages. This option is located on the main MailMan Menu.\n \nYou can search for any messages you sent or that were sent to you. MailMan\nallows you to choose in what location you want to search for mail:\n \n * Search for messages anywhere on the [SYSTEM].\n \n
\n\n", "\n- \n\n
\n", "", "2000-08-30 06:50:00\n", "", "USER,ONE\n", "", ""], ["906", "XM-U-B-BASKET CONTENTS LIST", "DIRECTORY OF BASKETS\n", "", "", "\n \n * Message Information - A summary list of information is provided for\n each message found in the basket. This information includes:\n \n - Message number in that basket.\n - MailMan internal message identification number (in brackets).\n - Date the message was sent.\n - Subject of the message.\n \nTo list all of the messages in one mail basket, choose the Mailbox\nContents List option on the Other MailMan Functions menu and enter 'O'\nMailMan allows you to list your messages in one or all of your mail\n(one) after the 'List contents of: All Baskets//' prompt.\n \nTo list all of the messages in your mailbox, choose the Mailbox\nContents List option on the Other MailMan Functions menu and enter 'A'\n(all) after the 'List contents of: All Baskets//' prompt or accept the\ndefault by pressing the Return/Enter key.\nbaskets in your mailbox through the Mailbox Contents List option on the\nOther MailMan Functions menu.\n \nThe report provides the following information:\n \n * Basket - The mail basket name.\n \n
\n\n", "", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["907", "XM-U-B-RESEQUENCE MESSAGES", "RESEQUENCING MESSAGE NUMBERS\n", "", "", "\n \nThe Resequence action code (i.e., 'R') allows you to renumber the message\nnumbers in a list of messages in a mail basket. All messages will be\nresequenced in the order of their MailMan internal message identification\nnumbers. This helps keep your mail basket messages more orderly by\nremoving any 'gaps' in message number sequence.\n \nTo resequence the message numbers for a group of messages in a mail\nbasket, enter an 'R' at the 'Enter message number or command:' prompt.\n
\n\n", "", "", "1991-10-03 08:56:00\n", "", "USER,ONE\n", "", ""], ["908", "XM-U-P-FORWARDING ADDRESS", "HOW TO USE THE FORWARDING ADDRESS FEATURE\n", "", "", "\n \nNOTE: This option may or may not be available to you. It depends on\n whether or not your site restricts access to this option to users\n holding the XMNET security key. For example, if your site requires\n users to hold the XMNET security key and you don't hold that key,\n you won't be able to use this option.\n \nThe Forwarding Address Edit option asks you to enter the following\ninformation:\n \n * Forwarding Address - To what remote address should the mail be routed?\nMailMan gives you the opportunity to have your mail automatically\n \n * Local Delivery Flag - Should the mail be sent both remotely and\n locally or just remotely?\n \nThe FORWARDING ADDRESS field contains the name of the remote address to\nwhich any MailMan messages addressed to you are routed. Only the original\nmessage gets forwarded, replies to messages are not forwarded.\nMessages sent by you to yourself are not forwarded.\n \nNOTE: Broadcast messages will be forwarded like any other messages sent to\nforwarded to a remote e-mail address. MailMan also gives you the option to\n your mailbox. However, since the Secretary's daily broadcast message\n on FORUM is sent to all sites, it will NOT be forwarded from FORUM.\n \nThe remote address must contain the remote name, an at-sign ('@' Shift-2\nkey on most keyboards), and the remote domain name (i.e., name@domain).\nThe entry can be up to 50 characters in length.\n \nThe value in the LOCAL DELIVERY FLAG field works in conjunction with the\nFORWARDING ADDRESS field. If the FORWARDING ADDRESS field contains a\nremote e-mail address, you should also set the LOCAL DELIVERY FLAG field.\ncontinue to receive e-mail at your local address as well.\n \nMailMan gives you two possible entries for this field:\n \n * No Local Delivery (default) - If you have a FORWARDING ADDRESS and you\n do not want your messages delivered locally, set the LOCAL DELIVERY\n FLAG field to 'Off' (i.e., '0'). Your messages will only be delivered\n to your remote addresses.\n \n * Local Delivery On - If you have a FORWARDING ADDRESS and you want your\n messages delivered locally as well as remotely, set the LOCAL DELIVERY\n \n FLAG field to 'On' (i.e., '1'). Your messages will be delivered to\n both your local and remote addresses.\n \nAlso, if you've set the LOCAL DELIVERY FLAG field to continue to receive\nmail locally, you may want to choose another MailMan user to act as your\n[SURROGATE] so that they can read your local mail.\nThe MailMan interface provides the Forwarding Address Edit option located\non the Personal Preferences menu to allow you to have your mail\nautomatically forwarded.\n \n\n\n", "\n- \n\n
\n", "", "2001-04-20 07:57:00\n", "", "USER,ONE\n", "", ""], ["909", "XM-U-R-READ", "READING AND MANAGING YOUR MAIL\n", "", "", "\n \nThe Read/Manage Messages option lets you better manage your e-mail. It\nallows you to perform numerous actions on both new and existing messages\nstored on the system (e.g., in a particular mail basket, mailbox, etc.).\n \nThe Read/Manage Messages option can be used to read and reply to messages.\nIt can also be used to delete, print, forward, save, copy, query, filter,\nlater, or terminate messages. You can also select messages for subsequent\ngroup actions. As long as a message is still on the system and you were a\nrecipient or sender of the message, it is available to you for processing.\n \nThe MailMan interface provides two options to read and manage your mail:\n[MORE]...\n \n * [NEW] Messages and Responses (NML)\n \n * Read/Manage Messages (RML)\n \nThese options are located on the main MailMan Menu.\n \n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["91", "XUDOC DEVICE FILE*", "DEVICE FILE STRUCTURE\n", "", "", "\nAll connected Volume Sets (CPUs) make use of a single, replicable, Device\nEach CPU has several ports to which devices may be connected. The port\nnumber is the $I value. Most physical devices are thus connected to one\nCPU via one $I. When using the device, however, different specifications\nmay be used for output. It is the device name which distinguishes the\nspecifications such as open and close execute or use parameters. Each\nentry in the Device File, then, uniquely identifies a set of instructions\nto send to a $I location on a particular CPU.\nFile. All information concerning a particular device is stored in just one\nplace which facilitates device management. \n \nOne way to demonstrate the structure of the Device File is to experiment\nwith [DEVICE LOOKUP] by using an option like Device Edit. Notice the\nfields 'Name', 'Device $I', and 'Volume Set(CPU)'. Together, these three\nattributes characterize an entry in the Device File.\n \n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["910", "XM-U-R-READ NEW", "PROCESSING NEW MAIL\n", "", "", "\n \n \n * [READ] new mail by basket (default).\n * [LIST BASKETS] with new mail.\n * List [ALL] new messages.\n * List all [PRIORITY] messages.\n * [PRINT] all new messages.\n * [SCAN] all new messages.\n * Quit - Use the Quit option to 'quit' processing your new mail. \n\nYou can set the default [CHOICE].\nThe New Messages and Responses (NML) option is the option you use when you\n \n[MORE]... \nspecifically wish to process new mail in your mailbox (i.e., messages and\nresponses not previously read). MailMan notifies you when you have new\nmail and precedes each new (unread) message in a list of messages with an\nasterisk.\n \nThis option provides you with the following choices of how you choose to\nread your new mail:\n
\n\n", "\n- \n\n
\n", "", "2000-07-26 07:55:00\n", "", "USER,ONE\n", "", ""], ["911", "XM-U-M-DELETE", "DELETING MESSAGES\n", "", "", "\n \nsystem until all recipients of the messages have deleted them from their\nmailbox. If mail is deleted from the 'WASTE' basket, it is not permanently\ngone. It can still be retrieved by a system [SEARCH] until MailMan purges\nthe message from the system.\n \nIf you delete a message, and someone else then replies to it, the message\nwill be redelivered to you so that it can be read again. Contrast this to\nthe [TERMINATE] action code, which prevents the message from being redelivered.\n \n[MORE]... \nThe Delete action code (i.e., 'D') allows you to delete individual\nmessages or a group of messages in a mail basket by moving them to the\n'WASTE' basket.\n \nGenerally, a batch job is run nightly (determined by IRM at your site) to\nremove messages from your 'WASTE' basket, and thus, from your mailbox. You\ncan immediately remove messages from your mailbox by, again, deleting the\nmessages from your 'WASTE' basket. However, the messages remain on the\n
\n\n", "\n- \n\n
\n", "", "2000-08-30 07:00:00\n", "", "USER,ONE\n", "", ""], ["912", "XM-U-M-QUERY", "QUERYING A MESSAGE FOR ITS STATUS\n", "", "", "\n \n \n * 'Q xxx' is used to inquire about a [SPECIFIC] individual by entering\n 'Q' and the individual's name (i.e., xxx = a person's name). For\n example, 'Q SMITH' will show the status of all 'SMITH' recipients.\n \n * 'QD' (Query [DETAILED]) displays detailed information for each\n individual recipient.\n \n * 'QN' (Query [NETWORK]) displays a message's network header\n (if it originated from a remote location).\nAt the 'Enter message action' prompt, the user may enter a 'Q' to inquire\n \n[MORE]... \nabout the status of the message. The 'Query' option shows you who has read\nthe message, when the message was read, how many responses were read, and\nother pertinent facts.\n \nThe query option has several forms:\n \n * 'Q' is the [GENERAL] query that tells you how the message was addressed.\n
\n\n", "\n- \n\n
\n", "", "2001-03-05 15:52:00\n", "", "USER,ONE\n", "", ""], ["913", "XM-U-M-FORWARD", "FORWARDING MESSAGES\n", "", "", "\n \n \nForwarding cancels any previous [TERMINATION] of a message. This is true\nwhen you forward a message to yourself or to other recipients.\n \n[MORE]... \nYou can use the Forward action code (i.e., 'F') to forward messages to\ndifferent recipients. As forwarding sends the message to other users, you\nwill be prompted to [ADDRESS] the message to individuals or [MAIL GROUPS].\n \nThe person who forwarded the message and the time the message was\nforwarded are displayed when you do a [QUERY] (QD) on the message.\nIf a message is defined to be [CLOSED], you cannot forward the message,\nunless you sent it.\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:33:00\n", "", "USER,ONE\n", "", ""], ["914", "XM-U-M-BACKUP", "BACKING UP THE MESSAGE DISPLAY\n", "", "", "\n \n \n * Any specific response (if any)\n \nThe Backup function is also useful when viewing a new response to an old\nmessage and you can't recall the previous responses. Backing up allows you\nto review the previous responses.\n \nTo back up to the original message or any specific response, enter a 'B'\nat the 'Enter message action' prompt.\nAfter a message has been read, replied to, and the reply has been read,\nMailMan will no longer display the message text automatically when you\nattempt to read the message. This is to avoid forcing you to read through\ntext you've already seen. However, the text is still there. You can use\nthe Backup action code (i.e., 'B') to back up to any part of a message and\nread the message from that point on:\n \n * Original message\n
\n\n", "", "", "1991-10-03 08:42:00\n", "", "USER,ONE\n", "", ""], ["915", "XM-U-M-SAVE", "SAVING MESSAGES\n", "", "", "\n \n you for a basket to save it to.\n \n * Group of Messages - Enter an 'S' at the basket option or command\n prompt.\n \n - MailMan will first ask you to select which messages you want to\n save, including a [RANGE] of messages. Also, if you are using a\n full-screen reader, you can pre-[SELECT] messages and then save\n them as a group.\n \nThe Save action code (i.e., 'S') allows you to save (move) individual\n - MailMan will then save the messages after prompting you for a\n basket to save them to.\nmessages or a group of messages in a mail basket to a different existing\nmail basket in your mailbox or to a new mail basket you create on the fly.\n \nTo save messages, do the following:\n \n * Individually - After reading a message, enter an 'S' at the 'Enter\n message action' prompt. MailMan will save the message after prompting\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 11:01:00\n", "", "USER,ONE\n", "", ""], ["916", "XM-U-M-TERMINATE", "TERMINATING MESSAGES\n", "", "", "\n \nyou may recover the message from your 'WASTE' basket, and [FORWARD] the\nmessage to yourself. This will cancel the effect of your previous\ntermination. If the message is no longer in your 'WASTE' basket, you could\nask another recipient of the message to forward it to you.\n \n[MORE]... \nThe Terminate action code (i.e., 'T') allows you to permanently delete\nindividual messages or a group of messages in a mail basket by moving them\nto the 'WASTE' basket.\n \nUnlike [DELETING] messages, terminating messages also stops any subsequent\nreplies to those messages from being delivered to you.\n \nIf you accidentally terminate a message and want to receive responses,\n
\n\n", "\n- \n\n
\n", "", "1993-11-13 23:43:00\n", "", "USER,ONE\n", "", ""], ["917", "XM-U-M-REPLY", "REPLYING TO A MESSAGE\n", "", "", "\n \n You will also be able to include responses from another message.\n \nYou are then prompted to enter the text of the new reply.\n \n'Reply' immediately attaches your reply to the response chain so everyone\non the message sees your reply, making it instantly available to anyone\ncurrently reading the message. This helps facilitate 'real-time'\nconversations among message recipients.\n \n[MORE]...\nEntering an 'R' or 'RI' at the 'Enter message action' prompt enables\nyou to reply to the message.\n \n * If you enter 'R', you will simply reply to the message.\n \n * If you enter 'RI', you will be able to include the original message\n and/or any [COMBINATION] of responses in your reply. (With this feature,\n you can more easily respond to what someone wrote, point by point.)\n
\n\n", "\n- \n\n
\n", "", "2000-05-15 08:57:00\n", "", "USER,ONE\n", "", ""], ["918", "XM-U-M-SEND", "USING THE 'Send a message' OPTION\n", "", "", "\n \n editor. You can later go back and edit the [TEXT] before sending the\n message.\n \n 3. Address the message (e.g., send it to individual [RECIPIENTS] or a\n [MAIL GROUP]). You can later go back and edit the [ADDRESSEES] before\n sending the message.\n \n 4. [SEND] the message. Before sending the message, you can edit it or add\n attributes to it at the 'Select Message option: Transmit now//' prompt\n (e.g., make the message: priority, closed, confidential, information only,\nThe 'Send a message' option is used to create and distribute messages.\n etc.). You can send it now or later. (If you send it only to yourself,\n you can [EDIT] it further before forwarding it on to others.)\nMailMan allows you to send new mail in four easy steps:\n \n 1. Enter the subject of the message. It must be no more than 65 characters.\n You can later go back and edit the [SUBJECT] before sending the message.\n \n 2. Enter the text of your message. MailMan automatically places you in your\n [PREFERRED EDITOR]. When you have completed your text entry, exit the\n
\n\n", "\n- \n\n
\n", "", "2002-05-06 11:36:00\n", "", "USER,ONE\n", "", ""], ["919", "XM-U-A-ADDRESS", "SENDING A MESSAGE - ADDRESSING\n", "", "", "\n \nservers (S.option_name), or [MAIL GROUPS]. Select a mail group by entering 'G.'\nfollowed by enough characters to ensure identification. For example, 'G.SOUTH'\nidentifies the SOUTH mail group. If the group is [LARGE], MailMan will suggest\ndeferring delivery to save you time. Messages can also be addressed to REMOTE\nusers. Sending to remote users is facilitated by a directory. \n \nRecipients may be marked as [INFORMATION ONLY] or [CARBON COPY].\nRecipients who are 'Information Only' may not respond to the message. You\ncan also [STAGGER] the delivery of the message to individual recipients.\n \nYou can address a message at the 'Send mail to:' or 'And send mail to:'\nTo remove recipients from the recipient list, enter a minus sign (hyphen)\nimmediately followed by the user's name (e.g., -SMITH,JOE).\nprompts. As a default, MailMan will always let you send a message to yourself\nby automatically placing your name as the default response after the first\n'Send mail to:' prompt. As an addressee, you can [QUERY] the message to see if\nor when the other recipients opened the message you sent. Whether you initially\nmake yourself an addressee or not, you will receive all replies to the message.\n \nMessages can be addressed locally to: [USERS], devices (H. or D.device_name),\n
\n\n", "\n- \n\n
\n", "", "2002-04-11 07:35:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""], ["92", "XUDOC SPOOL*", "SPOOLING TOPICS\n", "", "", "\n \n \n [SPOOL MANAGEMENT] Guidelines for Site Managers and Application\n Coordinators on Managing Spooling Activities\n \n \n \n \n \n \n \n \n \n [INSTALLATION] Notes for Site Managers on Installation of\n the Kernel Spooler\n \n \n [USING THE SPOOLER] Instructions for Users\n \n
\n\n", "\n- \n\n
\n", "", "1992-04-15 11:53:00\n", "", "USER,ONE\n", "", ""], ["920", "XM-U-M-SCRAMBLE", "SCRAMBLING A MESSAGE BEFORE SENDING\n", "", "", "\n \n \nIf this option is chosen, prompts appear for entering the scramble\npassword and scramble hint. The password can be from 3 to 20 characters in\nlength, with upper- and lowercase characters treated the same. The hint\nwill be shown to the recipient before s/he is asked to enter the password.\nAs the password cannot be recovered after being entered, the hint can be a\nhelpful reminder to the reader of the message.\nYou can use the Scramble action code (i.e., 'S') to have MailMan scramble\n(encode) your message so only those recipients who know the [PASSWORD] can\nunscramble (decode) your message. You may decide to send a message as\nscrambled for security or privacy reasons. The sender can provide a\n'[SCRAMBLE HINT]' to facilitate guessing the password.\n \nYou scramble a message by entering an 'S' after the 'Select Message\noption: Transmit now//' prompt.\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["921", "XM-U-M-CONFIRM RECEIPT", "REQUESTING CONFIRMATION BEFORE SENDING A MESSAGE\n", "", "", "\n \noption: Transmit now//' prompt.\n \nYou can request a Confirm Receipt from recipients at remote locations\nas well as from local recipients.\n \nAs an alternative, when reading a message, you can find out if and when\nany local user has read it. At the 'Enter message option' prompt, you can\nquery ('QD') [ALL] users or query ('Q xxx') [SPECIFIC] ones. \nYou can use the Confirm Receipt action code (i.e., 'R') to have MailMan\nnotify you (confirm) when each recipient has opened your message.\nUnfortunately, however, we can't guarantee that every recipient will\nactually read your message! The confirmation is in the form of a new\nmessage sent to you. This is a toggle action code. If you enter 'R' again,\nyou will not receive a confirm receipt.\n \nTo request a confirmation receipt enter an 'R' after the 'Select Message\n\n\n", "\n- \n\n
\n", "", "1999-01-14 13:55:00\n", "", "USER,ONE\n", "", ""], ["922", "XM-U-B-BASKET SELECT", "RESPONDING TO THE 'MAIL BASKET' PROMPT\n", "", "", "\n \nmessages in a 'DONE' basket, would clear out the 'PENDING' basket.\n \nWhen you select either the Read/Manage Messages or New Messages and\nResponses option and choose to read your mail by basket, if you have mail\nin more than one basket, MailMan will ask you to indicate which basket\nfrom which to start reading. You can do any of the following:\n \n <Enter> Press the Return/Enter key to read messages from your 'IN'\n basket (default basket).\n \nEach user has at least an 'IN' basket, into which incoming mail is stored,\n BASKET NAME Enter the name of a specific basket from which you\n wish to start reading.\n \n '??' Enter two question marks to see the list of existing\n baskets in your mailbox.\n \n '^' Enter the up-arrow ('^' uppercase 6 on most keyboards) to\n exit the option.\nand a 'WASTE' basket, which holds old mail temporarily before permanent\ndeletion. You may add new baskets by [SAVING] messages or create [FILTER]\nbaskets as you wish to sort out your mail for future use.\n \nFor example, a 'PENDING' basket might be used to store messages that\nrequire some future action. By [PRINTING] out your 'PENDING' basket, you\ncould have a quick reference for pending actions. Deleting or saving\n\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["923", "XM-U-B-READER DIFF", "BASKET ACTION CODES\n", "", "", "\n \n\n These act on one or more messages in this basket:\n [D] Delete messages.\n [F] Forward messages.\n [FI] Filter messages.\n [L] Later messages.\n [P] or [H] Print messages with or without a header.\n [S] Save messages to another basket.\n [T] Terminate messages.\n [X] Toggle transmit priority in remote message queues. (POSTMASTER only)\nThe following basket action codes are available with all message readers:\n \n [MORE]...\n\n n Read message n, where n is a sequence number in this basket or\n an internal message ID of any message on the system.\n [C] Change the name of this basket.\n [N] List only the new messages in this basket.\n [Q] Query (search for) messages in this basket.\n [R] Resequence messages in this basket.\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 15:31:00\n", "", "USER,ONE\n", "", ""], ["924", "XM-U-M-CHOOSE RANGE", "SPECIFYING A LIST OR RANGE OF MESSAGES\n", "", "", "\n \n * Specify a range of numbers by separating the beginning and\n ending numbers with a dash/hyphen (e.g., '0-10', where '0' is the\n original message).\n \n * Specify at what message you want MailMan to include through the\n remaining messages by entering a specific number followed by a\n dash/hyphen (e.g., 20-, MailMan would include message 20 through\n the remaining messages).\n \n * Specify combinations of the above by putting ranges where \nMailMan allows you to specify a range or list of messages for deletion,\n numbers would go, etc. (e.g., '0-3,5,8-10,20-', where '0' is the\n original message).\nfiltering, forwarding, latering, printing, saving, or termination from a\nbasket.\n \nTo specify a range or list, use the following syntax:\n \n * Enter the message numbers separated by commas (e.g., '1,5,9').\n \n
\n\n", "", "", "1991-10-03 09:03:00\n", "", "USER,ONE\n", "", ""], ["925", "XM-U-M-MESSAGE HEADER", "WHAT APPEARS IN THE MESSAGE HEADER\n", "", "", "\n \n \n * The date the message was sent. \n \n * How many lines there are in the original message.\n \n * Who sent the message. \n \n * How many total responses there are and how many you've read.\n \n * Whether the message is *NEW*.\nA message header is displayed or printed at the top of every screen or page\n\n * Which basket the message is in.\nwhen you read or print a message.\n \nThe message header contains:\n \n * The subject. \n \n * The MailMan internal message identification number.\n
\n\n", "", "", "1999-01-20 09:46:00\n", "", "USER,ONE\n", "", ""], ["926", "XM-U-M-PRINT", "PRINTING MESSAGES\n", "", "", "\n \n detailed recipient list.\n \n - MailMan will then ask you what you want to print. The default\n response will always be to print the original message and all\n responses. However, you can choose to print any [COMBINATION] of\n responses (single or range), with or without the original message.\n \n[MORE]... \nThe Print action code (i.e., 'P') allows you to print individual messages\nor a group of messages in a mail basket:\n \n * Printing Individual messages - After reading a message, enter a 'P' at\n the 'Enter message action' prompt.\n \n - MailMan will first ask if you want to print a recipient list. If\n you choose to print recipients, you can print either a summary or\n
\n\n", "\n- \n\n
\n", "", "1992-08-24 09:36:00\n", "", "USER,ONE\n", "", ""], ["927", "XM-U-M-SCRAMBLE HINT", "RESPONDING TO 'Enter Scramble Hint'\n", "", "", "\n \nA scramble hint is used to suggest to the reader what the scramble\n[PASSWORD] is. Since the password is not recoverable after it is entered, \nthe hint can be a helpful reminder to the reader of the message.\n \nThe hint will be shown to the recipient before being asked to enter the\nscramble password.\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["928", "XM-U-M-SCRAMBLE PASSWORD", "RESPONDING TO 'Enter Scramble Password'\n", "", "", "\n \nThe scramble password is a private code which must be exactly correct for\na reader to unscramble a message and make it legible. It can be from 3 to\n20 characters long. Upper- and lowercase characters are treated the same.\nThe scramble [HINT] that accompanies the scrambled message can help\ndecipher the password.\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["929", "XM-U-I-GROUP", "MAIL GROUPS\n", "", "", "\n \nusers can save time by putting them in mail groups.\n \nMembers can be added or removed at any time. They can be local and remote\nusers, other mail groups, or distribution lists (nationwide mail groups). \n \nMail groups can also be restricted to a limited set of Authorized Senders.\nThus, only certain users are allowed to send mail to the mail group. If\nunspecified, then it is assumed that anyone can send mail to a group,\nif [PUBLIC], or only members can send to it, if [PRIVATE].\n \nMail groups consist of MailMan users ([MEMBERS]) with similar interests in\n[MORE]... \na particular topic. Mail groups provide a forum for group discussion where\nmembers can share ideas and concepts related to the group. \n \nAs a member of a mail group, you, along with other members, receive\nmessages directed to that mail group. One can address a message to a\ngroup of recipients without having to specify them individually by name.\nThus, whenever mail is repeatedly sent to the same list of recipients,\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 11:43:00\n", "", "USER,ONE\n", "", ""], ["93", "XUDOC SPOOL INSTALL", "INSTALLING THE KERNEL SPOOLER\n", "", "", "\nYou may currently be using some form of spooling on your computer system.\n and will need to learn a slightly different system for spooling.\n \n - Disable any operating system-specific routines, such as ZISPLDSM.\n \n - Disable any spooling options that invoked those routines.\n \n - For DSM, use SPL in the Manager Account to clear out any remaining\n documents by deallocating and then reallocating the spool space.\n \n - Use the Spool Management Menu to set system defaults (site parameters)\nMost operating systems provide a mechanism for spooling and you may have\n and assign spooling privileges to users.\nestablished a method for your users. The Kernel Spooler has been designed\nso that concurrent use with a pre-existing mechanism will not pose a\nparticular problem, but it wouldn't have any benefit either. So, if you\nlike the Kernel Spooler, you would eventually need to do a few things:\n \n - Identify users who have spooling privileges (that is, have menu options\n for spooling). They will suffer some inconvenience during the transition\n
\n\n", "", "", "1989-04-27 12:45:00\n", "", "USER,ONE\n", "", ""], ["930", "XM-U-M-COPY", "COPYING A MESSAGE INTO A NEW MESSAGE\n", "", "", "\n \n \nAs with any other message you are [SENDING], MailMan will also ask\nyou to enter the [RECIPIENTS] to receive this copied message. \n \nTo copy the original message and any responses, enter a 'C' at the 'Enter\nmessage action' prompt.\nYou can use the Copy action code (i.e., 'C') to copy a message.\n \nWhen you copy a message, you are given several [OPTIONS] as to what should be\nincluded in the copy and whether to deliver the copy to the same recipients. \n \nYou can edit the copied message's subject and any part of the message text or\nresponses (e.g., delete unwanted portions or add additional text anywhere in\nthe copy).\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 13:09:00\n", "", "USER,ONE\n", "", ""], ["931", "XM-U-M-NEW", "MAKE NEW MESSAGES NOT NEW AND VICE VERSA\n", "", "", "\n \n it was already opened/read.\n \nYou can toggle between these two actions with this one action code.\n \n [MORE]...\nThe New Toggle action code allows you to make existing messages appear new\nor make new messages not new. The toggle works as follows:\n \n * Make a message 'new' - MailMan adds the new flag (i.e., '*' asterisk)\n next to the message, as if it hasn't been opened/read yet.\n \n * Make a 'new' message not appear as 'new' (i.e., Un New) - MailMan\n removes the new flag (i.e., '*' asterisk) next to the message, as if\n
\n\n", "\n- \n\n
\n", "", "1999-12-13 14:43:00\n", "", "USER,ONE\n", "", ""], ["932", "XM-U-Q-CLASSIC LOOKUP ?", "LOOKING FOR MESSAGES WHOSE SUBJECT CONTAINS A SPECIFIC STRING\n", "", "", "\n \nsubject contains the word 'SCHEDULE', you would enter '?SCHEDULE'.\nThis search is with uppercase and lowercase treated identically.\nThus, for example, 'SCHEDULE' and 'Schedule' would both be found\nwith the search.\nWhile in a basket, you can search for messages in the basket whose subject\ncontains a specific string.\n \nAt the 'Basket Message' prompt, enter the string preceded by a '?'. You\nwill then be shown a list of those messages in the basket which CONTAIN\nthat string in their subject, and can choose which you would like to read.\n \nFor example, if you want to search for messages in the basket whose\n
\n\n", "", "", "1999-04-21 12:37:00\n", "", "USER,ONE\n", "", ""], ["933", "XM-U-H-QUESTIONS", "FREQUENTLY ASKED QUESTIONS ABOUT MAILMAN\n", "", "", "\n \n the text. What happened to the original message?\n 5. [REPLIES] TO MESSAGES FROM UNKNOWN RECIPIENTS\n Why replies appear in a mailbox to a message which I didn't originate?\n 6. [DELETED] MESSAGES\n Once a message is deleted, is it actually gone from the system?\n 7. [INTERRUPTED] MESSAGES\n Can a message be saved temporarily after an interruption?\n 8. [FILTERING] MAIL\n Can certain messages be automatically directed to specific baskets?\n 1. [RECALLING] OR EDITING A MESSAGE AFTER TRANSMISSION\n Is there a way to recall or edit a message once it's been sent?\n 2. [REMOVING] A RECIPIENT FROM THE LIST\n How can an accidentally chosen recipient be removed from the list?\n 3. [LOOKING UP] A MESSAGE TO BE READ\n Is there a way of finding a message if you cannot recall the number?\n 4. [DISAPPEARED] MESSAGES WHICH HAVE NOT BEEN DELETED\n Sometimes the read option will show only the message header without\n
\n\n", "\n- \n\n
\n", "", "2002-05-06 11:19:00\n", "", "USER,ONE\n", "", ""], ["934", "XM-U-H-Q RECALL", "RECALLING OR EDITING A MESSAGE AFTER TRANSMISSION\n", "", "", "\n \n \nUsing the [READ]/Manage Messages option, after displaying the text of the\nmessage, you will be prompted with the 'Enter message option'. Enter an\n'E' ([EDIT]) and choose from any number of edit options.\nIs there a way to recall or edit a message once it's been sent?\n \nYou cannot completely recall a message once it's been sent. However, you\ncan edit the message, provided that:\n \n * You created the message and did not send it to anyone except yourself.\n \n * The message you wish to edit is the original message and not a reply.\n
\n\n", "\n- \n\n
\n", "", "1991-10-01 06:29:00\n", "", "USER,ONE\n", "", ""], ["935", "XM-U-H-Q REMOVE", "REMOVING A RECIPIENT FROM THE LIST\n", "", "", "\n \nTo take someone off the recipient list, enter their name preceded with a\nminus or hyphen ('-'). This will delete them from the list.\n \nNOTE: You cannot remove a recipient from the list after the message has\n been sent. Think of the [TRANSMIT] option as dropping a message in a\n post office mail box. You cannot recall a message once it has been\n sent.\nIf a user is accidently chosen as a recipient for a message, how can they\nbe removed from the list?\n \nA message is not actually sent to anyone until you respond to the 'Select\nMessage option: Transmit now//' prompt with 'T' for transmit. Enter an\n'ER' for [EDIT RECIPIENTS] at this prompt if you wish to delete a\nrecipient.\n \n\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["936", "XM-U-H-Q LOOKUP", "LOOKING UP A MESSAGE TO BE READ\n", "", "", "\n \n \nTo see a list of messages using the [CLASSIC] message reader, enter ONE or\nTWO question marks after the 'Basket Message' prompt. You can then choose\nfrom this list by message number.\n\nIn either of the message readers, you can look up a message based on what\nthe subject [BEGINS WITH] or [CONTAINS]. You can also use the Query ('Q')\naction code to search for messages in a basket based on multiple [CRITERIA].\n\nOn the main MailMan Menu, you can use the Query/Search for Messages option\nIs there a way of finding a message if you cannot recall the number?\nto search for messages [ANYWHERE] in your mailbox or on the system.\n \nYes, there are several ways to look up a message. \n \nWhen you are using one of the [FULL SCREEN] message readers, MailMan\ndisplays a list of messages in a basket. You can then choose from this\nlist by entering a message number after the 'Enter message number or\ncommand:' prompt.\n\n\n", "\n- \n\n
\n", "", "1999-03-19 14:47:00\n", "", "USER,ONE\n", "", ""], ["937", "XM-U-H-Q REPLIES", "REPLIES TO A MESSAGE FROM AN UNKNOWN RECIPIENT\n", "", "", "\n \nany of the recipients to reply, make the message [INFORMATION ONLY]. If\nyou don't want specific recipients to reply, [PREFIX] the recipient names\nwith 'INFO:'.\nWhy do replies appear in the mailbox to a message I didn't originate?\n \nThis occurs when you are the recipient of a message that has been sent to\nothers. If one of the other recipients [REPLIES] to the message, all of\nthe other recipients receive the reply. This feature is similar to\nteleconferencing.\n \nIf you are sending a message to a group of recipients and you don't want\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["938", "XM-U-H-Q DELETE", "DELETED MESSAGES\n", "", "", "\n \nsystem until all recipients of the message have deleted it from their\nmailbox.\nOnce a message is deleted, is it actually gone from the system?\n \nNo. When you [DELETE] messages, they are put into your 'WASTE' basket.\nTo access these deleted messages, read messages in your 'WASTE' basket.\nYou can then [SAVE] them to a different basket.\n \nThe message will be deleted from your 'WASTE' basket automatically when\nthe MailMan purge utility is run. However, the message remains in the\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["939", "XM-U-P-BANNER", "THE MAILMAN BANNER\n", "", "", "\n \n * Your MailMan banner is displayed to anyone addressing a message to\n you. This is useful, for example, if you will be on vacation and\n wish to let others know that mail will not be regularly checked.\n \n * Your banner is also displayed whenever you enter the MailMan menu,\n so that you will not forget to change or delete it when it is no\n longer appropriate.\n \n * Your MailMan Banner is also displayed to you or others when using the\n User Information option on the Help (User/Group Info., etc.) menu to\nThe MailMan Banner is used to display any information that you want other\n obtain information about you.\n \nBanners can range from 2 to 200 characters in length and can contain\nany combination of numbers, alphabetic characters, symbols (e.g., #,\n$, %, &, *), and punctuation marks.\n \nYou can enter or change your banner using either of two methods:\n \n * Use the User Options Edit option with the 'BANNER:' prompt.\n \nMailMan users to see. Banners can be used to list business information,\n * Use the Banner Edit option on the Personal Preferences menu.\n \nNOTE: The banner is not displayed when a group of users is selected.\npersonal information, favorite quotes, etc., whatever you feel is\nappropriate in a business environment. You are not required to have a\nMailMan Banner; it is up to you to decide.\n \nBanners are displayed in the following three instances:\n \n
\n\n", "", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["94", "XUDOC SPOOL MGT1", "MANAGING THE SPOOLER\n", "", "", "\nYou, the systems manager, will need to use the Spool Management Menu to\nwrite to the spool device? If not, a message to that effect will be issued\nwhen the user attempts to use the spool device.\n \nSecond, when printing a spool document, may this user send output to more\nthan one printer? If so, the system will continue to prompt for another\ndevice until the response is null.\n \nThird, may this user make spool documents into mail messages? If so, the\nuser may treat the spool document just like a mail message, to copy, edit,\nor send over the network.\nset system defaults and assign spooling privileges. This menu is part of\nthe Systems Manager Menu.\n \nSystem defaults (site parameters) set a maximum for the number of documents\nper user, the maximum spool lines per user, and the maximum lifetime of\nspool documents. The Kernel Site Parameter File holds this data.\n \nUser access involves 3 New Person file attributes. First, may this user\n
\n\n", "", "", "1992-04-15 11:44:00\n", "", "USER,ONE\n", "", ""], ["940", "XM-U-P-INTRODUCTION", "INTRODUCING YOURSELF IN MAILMAN\n", "", "", "\n \nYour Introduction is only displayed when users do a lookup on you via the\nUser Information option on the Help (User/Group Info., etc.) menu.\n \nSince the Introduction field is a word processing field there is no upper\nlimit on the number of characters you can enter. You can also include any\ncombination of numbers, alphabetic characters, symbols (e.g., #, $, %, &,\n*), and punctuation marks.\n \nThe 'INTRODUCTION:' field can be set through the User Options Edit option\non the Personal Preferences menu.\nIn order that other users of the system can get to know new users,\nthe latter may enter several lines of introductory text, as well as an\naddress, phone number, and other [CONTACT INFORMATION]. The Introduction\nfield provides you with the opportunity to 'introduce' yourself to other\nMailMan users. Since it is a word processing field, MailMan allows you to\nenter as much information as you wish. You may or may not be required to\nenter an Introduction depending on your site's policy.\n \n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["941", "XM-U-I-SURROGATE", "MAILMAN SURROGATES\n", "", "", "\n \nco-worker to read their mail while they are out of the office so that\ncritical or important messages can be read and responded to without delay.\n \n[MORE]... \nA surrogate is someone who substitutes for someone else. MailMan gives all\nusers the opportunity to [DESIGNATE] someone to act as their surrogate. It\nalso allows all users to [BECOME] a surrogate.\n \nThere are several occasions when you may wish to designate someone as your\nsurrogate. For example, if you are going on vacation, you may ask someone\nto be a surrogate for you while you are out of the office. Specifically, a\nmanager or project team member may ask their administrative assistant or\n
\n\n", "\n- \n\n
\n", "", "1993-12-06 20:53:00\n", "", "USER,ONE\n", "", ""], ["942", "XM-U-P-ASK BASKET", "THE 'ASK BASKET' PROMPT\n", "", "", "\n \n * If 'YES' is entered, you will be asked 'What basket?' when sending a \n message to yourself.\n \n * If 'NO' is entered, the message will go to your 'IN' basket.\nMailMan allows you to decide up front whether you want to be prompted each\ntime to choose a mail basket whenever you send yourself e-mail. You can\neither choose to be prompted at each occurrence or automatically have the\nmail default to the 'IN' basket.\n \nTo set your mail basket prompt, use the User Options Edit option on the\nPersonal Preferences menu to answer the 'ASK BASKET?:' prompt.\n \n
\n\n", "", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["943", "XM-U-M-CONFIDENTIAL", "MAKING A MESSAGE CONFIDENTIAL\n", "", "", "\n \nYou can use the Confidential action code (i.e., 'C') to only allow the\ndesignated recipient(s) and not their [SURROGATE](s) to read the message\nyou are sending, unless a surrogate trying to read the message is the\nsame surrogate that sent it. This is a toggle action code. If you enter\n'C' again, the message will no longer be confidential.\n \nTo send a confidential message, enter a 'C' at the 'Select Message option:\nTransmit now//' prompt.\n
\n\n", "\n- \n\n
\n", "", "1989-06-09 00:00:00\n", "", "USER,ONE\n", "", ""], ["944", "XM-U-I-SURROGATE BECOME", "BECOMING A SURROGATE\n", "", "", "\n \nmay act as a surrogate, as well as your access privileges ([READ] or [WRITE])\nand whether the user has any new mail. \n \nWhen acting as a surrogate, you will be using your own MailMan message center\n[PREFERENCES] when reading mail and not the other user's preferences. For\nexample, if you have set your message reader to use the Detailed Full Screen\nmessage reader and the user who designated you as the surrogate uses the\nClassic message reader, you will still view that user's messages in the\nDetailed full screen and not in the Classic message reader. \nAll users of MailMan are given the option to act as a Surrogate for\n[SHARED,MAIL]. If you have been [DESIGNATED] as a surrogate by other MailMan\nusers, you may act as a surrogate for those users, too.\n\nTo become a surrogate, choose the Become a Surrogate (SHARED,MAIL or Other)\noption on the MailMan menu. If you are not anyone's surrogate, you will become\nSHARED,MAIL. If you are someone's surrogate, you will be asked whom you wish\nto become. If you enter a '?', MailMan will show you the users for whom you\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 08:15:00\n", "", "USER,ONE\n", "", ""], ["945", "XM-U-P-SURROGATE EDIT", "SURROGATES - DESIGNATING SURROGATES\n", "", "", "\n \nability to [ASSUME] your identity for the purposes of reading and/or sending\nyour mail. \n \nIf a message is sent [CONFIDENTIAL], surrogates cannot view it. If a\nmessage has been [SCRAMBLED], surrogates that don't know the password\ncannot read it. Thus, you would be wise to inform people from whom you\nreceive mail of a private nature (not to be read by your surrogate) to\nsend it confidential or to scramble it.\n \nMailMan will record the fact that a surrogate has sent messages or\nMailMan provides you with the Surrogate Edit option for designating\n[REPLIED] while assuming your identity in the message. You can see this\nwhen you read or [QUERY] ('QD') the message.\nsurrogates to read and send your own e-mail. This option is available on\nthe Personal Preferences menu.\n \nYou can use the Surrogate Edit option when you know you will not be able to\nread your mail for a period of time but still want your mail monitored and\ntaken care of in a timely fashion. The people you designate as surrogates can\nbe given [READ] or read and [WRITE] access to your mail. These people have the\n\n\n", "\n- \n\n
\n", "", "1999-01-14 14:02:00\n", "", "USER,ONE\n", "", ""], ["946", "XM-U-H-Q INTERRUPT", "INTERRUPTED MESSAGES\n", "", "", "\n \n \nAlso, if you are disconnected in the middle of entering a message or\nreply, the system will attempt to save your text in a message buffer. The\nnext time you signon, Mailman will notify you that you have an unsent\nmessage or response in your buffer. You may return to complete the message\nor response.\nCan a message be saved temporarily after an interruption?\n \nYes. If you are in the middle of entering a message, and you receive a\nphone call or some other interruption, it is often useful to transmit the\nincomplete message to yourself. You can later return to that same message\nthrough the [READ]/Manage Messages option, and complete the message using\nthe [EDIT] action. You can then [FORWARD] the message to the original\nintended recipients.\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 11:35:00\n", "", "USER,ONE\n", "", ""], ["947", "XM-U-NEW FEATURES", "NEW FEATURES AND FUNCTIONALITY\n", "", "", "\n \nStandardization project, is used, instead. Thus, the names of people whose\nlast names, for instance, contain periods, apostrophes, or spaces, are\nproperly displayed (ST. IVES, O'MALLEY, and VAN DYKE), instead of\nimproperly (STIVES, OMALLEY, and VANDYKE). \n\n3. Messages with responses may no longer be forwarded to broadcast to all\nusers. Such messages may have important information in the responses, and\nas we all know, responses are not auto- forwarded to remote sites for users\nwith auto-forward addresses. Users who attempt to broadcast messages with\nresponses will be encouraged to copy the message and its responses into a\nMailMan 8.0 offers you the following improvements over MailMan 7.1:\nnew message, which can be broadcast. \n\n4. You can now send, forward, or filter-forward messages to H.device\n(Headerless print). It will print the message, without a header, on the\ndevice. As before, sending messages to D.device will print them with\na header.\n\n1. MailMan date/times are now in a standard format, produced by a Kernel\nAPI. For example, what used to be displayed as '03 Aug 02 15:32' is now\ndisplayed as '08/03/02@15:32'.\n\n2. MailMan no longer displays user names by taking them directly from the\n.01 field of the NEW PERSON file. An API supplied as part of the Name\n
\n\n", "", "", "2002-05-09 08:54:00\n", "", "USER,ONE\n", "", ""], ["948", "XM-U-P-FILTER", "FILTERING MAIL\n", "", "", "\n \nOptionally, the filters can also take additional [ACTIONS] on your messages\nduring message delivery.\n \nThe MailMan interface provides the Message Filter Edit option located on\nthe Personal Preferences menu to create and edit message filters.\n \n[MORE]...\nYou can filter your mail! MailMan can use message filters, created by you,\nto assist you with organizing your mail.\n \nYou can think of MailMan and message filters performing the duties of an\n'executive assistant,' such as sorting through all of the incoming mail\nbefore it reaches your 'desk.' These filters screen and categorize your\nmail, directing it to mail baskets you specify based on certain\n[CRITERIA]. (You can even direct 'junk mail' right to the 'WASTE' basket!)\n
\n\n", "\n- \n\n
\n", "", "2000-05-15 13:21:00\n", "", "USER,ONE\n", "", ""], ["949", "XM-U-P-OPTIONS", "PERSONAL PREFERENCES\n", "", "", "\n \n displayed (i.e., newest or oldest messages first).\n \n * [NEW] MESSAGES READ ORDER - Choose the order in which you want to read\n your new messages (i.e., newest or oldest messages first).\n \n * MESSAGE [READER] - Choose how you display your messages when using\n the Read/Manage Messages option (i.e., Classic, Summary Full Screen,\n or Detailed Full Screen.\n \n[MORE]...\nThe User Options Edit option on the Personal Preferences menu allows you\nto customize the MailMan interface to suit your needs. You can choose\nfrom the following options:\n \n * [BANNER] - Create or edit your banner. (You can also use the Banner\n Edit option on the Personal Preferences menu to do the same thing.)\n \n * MESSAGE [ORDER] - Choose the order in which your messages are\n
\n\n", "\n- \n\n
\n", "", "2000-07-26 06:25:00\n", "", "USER,ONE\n", "", ""], ["95", "XUDOC SPOOL TECH1", "TECHNICAL OVERVIEW OF SPOOLING (1)\n", "", "", "\nObsolete help frame.\n
\n\n", "\n- \n\n
\n", "", "1992-04-15 11:47:00\n", "", "USER,ONE\n", "", ""], ["950", "XM-U-B-FILTER", "FILTERING MESSAGES - BASKET ACTION\n", "", "", "\n \n(determined by your mail filters).\n \nTo filter messages in a basket, enter an 'FI' at the basket option or\ncommand prompt.\n \n * MailMan will first ask you to select which messages you want to\n filter, including a [RANGE] of messages. Also, if you are using a\n full-screen reader, you can pre-[SELECT] messages and then filter them\n as a group.\n \nMailMan allows you to [FILTER] your mail. You can create any number of\n * MailMan will then filter the messages. \nfilters to automatically send your mail to any specified mail basket in\nyour mailbox based on various filtering [CRITERIA].\n \nSometimes, when managing mail in your mail baskets, you may find old\nmessages that came into your mailbox prior to your creation of mail\nfilters. Thus, you can use the Filter messages action code (i.e., 'FI')\nto filter these 'old' messages and move them to the proper mail basket\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 09:40:00\n", "", "USER,ONE\n", "", ""], ["951", "XM-U-P-FILTER ORDER", "FILTERING MAIL - ORDER FIELD\n", "", "", "\n \nA message may match several filters, depending on the conditions\n(filtering criteria) you have set. The ORDER field is used to determine in\nwhich order filters will be checked. It is here that you specify relative\nfilter priority. The value entered must be a whole number between 1 and\n999 (no decimal digits). All filters are checked in numeric order. If\nseveral filters have the same number, then the first one you entered\nreceives priority.\n
\n\n", "", "", "1998-12-10 09:10:47\n", "", "USER,ONE\n", "", ""], ["952", "XM-U-P-DELIVERY BASKET PRIV", "DELIVERY BASKET PRIVILEGES\n", "", "", "\n \nThe Delivery Basket Edit option allows you to customize the way you\nreceive messages from other MailMan users who have targeted messages for\ndelivery to specific baskets. With this option you can, for example,\npermit other MailMan users to direct mail to a specific mail basket in\nyour mailbox and/or create new baskets for you automatically.\n \nSpecifically, you can choose to do any of the following:\n \n * YES, ACCEPT IT - Choose this response if you will accept the mail in\n whatever mail basket is specified by the sender. If the mail basket\nSenders of mail messages can specify or target the mail basket into which\n specified does not already exist, it will automatically be created in\n your mailbox and the message will be delivered to this new mail\n basket. This is the most permissive setting.\n \n * NO, DON'T ACCEPT IT (default) - Choose this response if you will not\n accept the mail in the mail basket specified by the sender. Thus,\n regardless of what the sender specifies, the mail will be delivered as\n usual (i.e., to your 'IN' basket or, via your mail filters, to a\n different mail basket). With this default setting, no new mail baskets\n can be created by others in your mailbox. This is the least permissive\na message should be delivered for all recipients. Recipients of such\n setting.\n \n * EXISTING BASKETS ONLY - Choose this response if you will accept the\n mail in the specified mail basket, only if that mail basket already\n exists in your mailbox. Otherwise, if the specified mail basket\n doesn't exist, the mail will be delivered as usual (i.e., to your 'IN'\n basket or, via your mail filters, to a different mail basket). With\n this setting, no new mail baskets can be created by others in your\n mailbox.\n \nmessages can decide whether to accept or reject delivery to any targeted\n * SELECTED BASKETS ONLY - Choose this response if you will accept the\n mail in the specified mail basket, only if that mail basket already\n exists in your mailbox and you have specified that the basket will\n accept such messages. These mail baskets are also specified through\n the Delivery Basket Edit option. Otherwise, if the specified mail\n basket doesn't exist or is not set to accept the mail, the mail will\n be delivered as usual (i.e., to your 'IN' basket or, via your mail\n filters, to a different mail basket). With this setting, no new mail\n baskets can be created by others in your mailbox.\nbasket by setting up their delivery privileges beforehand.\n \nTo set up your mail delivery privileges, use the Delivery Basket Edit\noption on the Personal Preferences menu.\n \n
\n\n", "", "", "1998-12-10 10:25:42\n", "", "USER,ONE\n", "", ""], ["953", "XM-U-P-READER DEFAULT", "DEFAULT MESSAGE READER\n", "", "", "\n \nTo choose and set your message [READER] default, use the User Options Edit\noption on the Personal Preferences menu. Press the Return key until you\nreach the 'MESSAGE READER:' prompt. You can choose from the Classic,\nSummary Full Screen, or Detailed Full Screen message readers.\n \nOnce you have decided on a message reader, you can specify whether the\nreader you just chose should be used all the time or whether you want to\nbe [PROMPTED] each time you use the Read/Manage Messages option.\n
\n\n", "\n- \n\n
\n", "", "1999-01-13 15:38:00\n", "", "USER,ONE\n", "", ""], ["954", "XM-U-P-MESSAGE ORDER", "MESSAGE LIST ORDER\n", "", "", "\n \n \nGenerally, the basket message sequence number order will correspond to the\nmessage date sent order with the following exceptions:\n\n * Messages not originally sent to you but forwarded to you at a later\n date.\n \n * Messages sent from another location via the network (e.g., messages\n from a different site, FORUM messages).\n \nMailMan allows you to choose the order in which your messages are displayed:\nTo set your message order, use the User Options Edit option on the\nPersonal Preferences menu to answer the 'MESSAGE ORDER?:' prompt.\n\n 1. Newest First - This means that your messages are displayed in reverse\n order (i.e., highest to lowest basket message sequence number order).\n \n 2. Oldest First - This means that your messages are displayed in message\n number order (i.e., lowest to highest basket message sequence number\n order).\n
\n\n", "", "", "2000-07-26 07:29:00\n", "", "USER,ONE\n", "", ""], ["955", "XM-U-M-DELIVERY BASKET SET", "DELIVERY BASKET SET OPTION\n", "", "", "\n \n \nSetting a delivery basket overrides any filters created by a recipient of\nthe message. Also, if allowed by a recipient and the mail basket specified\ndoes not already exist, MailMan will create the new delivery mail basket\nfor that recipient.\n \nTo set the delivery basket for a message, enter a 'D' at the 'Select\nMessage option: Transmit now//' prompt.\nYou can use the Delivery Basket Set action code (i.e., 'D') to specify the\nintended delivery mail basket for all recipients of the message you are\nsending. Depending on how each recipient has set their delivery basket\n[PRIVILEGES] using the Delivery Basket Edit option on the Personal\nPreferences menu, the message may or may not be delivered to the intended\nbasket set by you. However, the message will still be delivered to each\nrecipient's mailbox. The delivery basket specified remains in effect, even\nif a recipient forwards the message to another MailMan user.\n
\n\n", "\n- \n\n
\n", "", "1998-12-10 10:29:20\n", "", "USER,ONE\n", "", ""], ["956", "XM-U-M-TRANSMIT LATER", "SEND A MESSAGE LATER (DEFER)\n", "", "", "\n \nYou can use the Transmit Later action code (i.e., 'L') to send a message\nto all recipients at a later specified date and time (up to one year).\nThis action code uses TaskMan to schedule the delivery of the 'latered' or\ndeferred message. You would use this action code after you've taken all\nother actions on your message.\n \nTo send a message at a later date and time, enter an 'L' at the 'Select\nMessage option: Transmit now//' prompt.\n
\n\n", "", "", "1998-12-10 10:30:03\n", "", "USER,ONE\n", "", ""], ["957", "XM-U-A-STAGGER DELIVERY", "STAGGER DELIVERY OF A MESSAGE\n", "", "", "\n \nof your message to receive the message at a much later date and time, you\ncould first use the staggered delivery function to specify the later\ndelivery date and time for those specific recipients and then send the\nmessage using either the TRANSMIT NOW or DEFERRED SEND action codes.\n \nAfter the message with staggered delivery dates and times has been sent, and\nbefore it has been delivered to the staggered recipients, doing a [QUERY] (Q)\non the message will show the intended delivery dates and times for those\nrecipients. \n \nWhen addressing a message at the 'send to:' prompt, the 'L:xxx' prefix code\n[MORE]... \n(where 'xxx' represents the addressee's name), allows you to individually enter\na specific delivery date and time (from at least five minutes into the future\nup to one month) for each addressee of a message. You can use this prefix code\nin conjunction with either the [TRANSMIT NOW] (send the message now) or the\n[DEFERRED SEND] (send the message later) action codes. \n\nFor example, if you want a few recipients from the list of the recipients\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 13:21:00\n", "", "USER,ONE\n", "", ""], ["958", "XM-U-B-BASKET NAME", "NAMING BASKETS\n", "", "", "\n \ngrave accent mark or back tick (`).\nMailMan allows you to give your mail baskets names starting with\nalphabetic characters, symbols, or numbers and when you list your baskets,\nthey will be in alphabetical order (those baskets beginning with numbers\nor symbols will be listed first). Mail basket names can be from 2 to 30\ncharacters in length.\n \nWhen you wish to choose a mail basket by its basket number (e.g., '.5' for\nthe 'WASTE' basket), you must now precede the mail basket number with a\n
\n\n", "", "", "1998-12-10 10:58:15\n", "", "USER,ONE\n", "", ""], ["959", "XM-U-P-MESSAGE ACTION DEFAULT", "MESSAGE ACTION DEFAULT\n", "", "", "\n \n 1. Ignore (default) - Leaves the message in the same MailMan basket.\n \n 2. Delete - Moves the message to your MailMan 'WASTE' basket.\n \nIf you do not enter anything in this field, the default will be whatever\nIRM has set for your site in the [MAILMAN SITE PARAMETERS] file (#4.3). If\nIRM has not set a value, the default will be 'Ignore.'\n \nThe 'MESSAGE ACTION DEFAULT:' can be set through the User Options Edit\noption on the Personal Preferences menu.\nMailMan allows you to decide the default response after reading a message\nin your 'IN' mail basket via the 'MESSAGE ACTION DEFAULT:' prompt.\nWhatever you enter into this field will control the default for the 'Enter\nmessage option' prompt that you answer after reading each MailMan message\nin your 'IN' mail basket.\n \nThere are two possible responses:\n \n
\n\n", "\n- \n\n
\n", "", "2002-05-07 07:20:00\n", "", "USER,ONE\n", "", ""], ["96", "XUDOC SPOOL USE1", "USING THE SPOOLER\n", "", "", "\nHave you ever used the spooler? If not, you might like to know the reasons\nwhere you would like spooling to occur. If you are not queuing, choose the\none on your current CPU.\n \n DEVICE: SPOOL\n \n 1 SPOOL AAA\n 2 SPOOL BBB\n Choose 1-2>\n \nTo queue, respond to the device prompt with 'Q'. This will allow use of a\nfor spooling. What are the advantages? [WHY SPOOL?]\nspooler on another CPU. It will also allow spooling to occur at a later\ntime. [CONTINUE]\n \nTo create a spool document, just send it to the spool device by responding\nto the device prompt as follows:\n \n DEVICE: SPOOL\n \nIf your system has several networked processors, you may need to specify\n
\n\n", "\n- \n\n
\n", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["960", "XM-U-P-SHOW TITLES", "SHOW TITLES\n", "", "", "\n \n \n * No (default) - Do not display a sender's title in the message header.\n \nIf you do not set this field, the sender's title will not appear in the\nmessage header.\n \nThe 'SHOW TITLES:' field can be set through the User Options Edit option\non the Personal Preferences menu.\nMailMan allows you to decide if you want a message sender's title to be\ndisplayed in the message header. If you elect to show titles, they will be\npreceded by a hyphen (i.e., generated by MailMan) and appear after the\nsender's name in the 'From' portion of the message header.\n \nThere are two possible responses to this question:\n \n * Yes - Display a sender's title in the message header.\n
\n\n", "", "", "2002-05-07 07:31:00\n", "", "USER,ONE\n", "", ""], ["961", "XM-U-P-PRIORITY FLAG", "PRIORITY RESPONSES FLAG\n", "", "", "\n \n \nThere are two possible values from which to choose when answering the\n'PRIORITY RESPONSES FLAG:' question:\n \n * 0, Responses are PRIORITY (default) - Responses to priority mail will\n be delivered to you as priority responses.\n \n * 1, Responses are ORDINARY - Responses to priority mail will be\n delivered to you as ordinary responses.\n \nThe PRIORITY RESPONSES FLAG field works in conjunction with the PRIORITY\nIf you do not set this field, then responses will be priority. \nRESPONSES [PROMPT] field. Both of these fields can be set through the User\nOptions Edit option available on the Personal Preferences menu.\n \nMailMan allows you to decide whether or not you want to have responses to\npriority mail delivered to you as priority or ordinary responses. Setting\nthe PRIORITY RESPONSES FLAG field allows you to choose what your default\nshould be.\n
\n\n", "\n- \n\n
\n", "", "1998-12-11 10:44:25\n", "", "USER,ONE\n", "", ""], ["962", "XM-U-P-PRIORITY PROMPT", "PRIORITY RESPONSES PROMPT\n", "", "", "\n \nis delivered. Setting the PRIORITY RESPONSES PROMPT field allows you to\nchoose what your default will be.\n \nThis prompt allows you to determine on a message-by-message basis whether\nor not MailMan will deliver responses to a priority message as priority\nmail, regardless of what the default is for the PRIORITY RESPONSES [FLAG].\n \n[MORE]... \nThe PRIORITY RESPONSES PROMPT field works in conjunction with the PRIORITY\nRESPONSES [FLAG] field. Both of these fields can be set through the User\nOptions Edit option available on the Personal Preferences menu.\n \nMailMan allows you to decide whether or not you will be prompted to choose\nto have future responses to an individual priority message delivered to\nyou as priority or ordinary mail. The answer you give here determines\nwhether or not MailMan will ask you to choose each time a priority message\n
\n\n", "\n- \n\n
\n", "", "1998-12-11 10:45:06\n", "", "USER,ONE\n", "", ""], ["963", "XM-U-P-INSTITUTION", "MAILMAN INSTITUTION\n", "", "", "\n \nuser must enter a MailMan Institution to better identify themselves.\n \nYour MailMan Institution is displayed to others when they receive messages\nfrom you. It is shown in parentheses following your name and title in the\nheading of every local message or response that you send.\n \nThe MailMan Institution can range from 3 to 30 characters in length and\ncan contain any combination of numbers, alphabetic characters, symbols\n(e.g., #, $, %, &, *), and punctuation marks.\n \nThe MailMan Institution is a piece of information that helps identify you\nThe 'MAILMAN INSTITUTION:' field can be set through the User Options Edit\noption on the Personal Preferences menu.\nto other MailMan users. It is usually the office or site where you are\nlocated (i.e., your physical location) and is most useful in systems such\nas FORUM where people from many different sites interact.\n \nMailMan allows you to enter your own MailMan Institution that will be\ndisplayed to other users. You are not required to enter a MailMan\nInstitution on local mail. However, on FORUM, it is a policy that every\n
\n\n", "", "", "1998-12-11 10:47:00\n", "", "USER,ONE\n", "", ""], ["964", "XM-U-P-NETWORK SIGNATURE", "NETWORK SIGNATURE\n", "", "", "\n \nmarks. In order to have a valid Network Signature recognized by MailMan,\nyou must enter data in at least one of the three Network Signature lines.\nAny line of the three is acceptable as long as one line contains data.\n \nThe 'NETWORK SIGNATURE LINE n OF 3:' field (where n equals one, two, or\nthree) can be set through the User Options Edit option on the Personal\nPreferences menu.\nThe Network Signature is a piece of information that helps identify you to\nother MailMan users. It consists of three separate lines of information.\nMailMan allows you to enter your own Network Signature. You must enter a\nNetwork Signature in order to use the '[ANSWER]' command on a message.\n \nEach of the three lines comprising the Network Signature can range from 3\nto 70 characters in length and can contain any combination of numbers,\nalphabetic characters, symbols (e.g., #, $, %, &, *), and punctuation\n
\n\n", "\n- \n\n
\n", "", "1998-12-11 10:49:03\n", "", "USER,ONE\n", "", ""], ["965", "XM-U-P-EDITOR", "PREFERRED EDITOR\n", "", "", "\n \ncases.\n \nYour choice of editors is based on the editors available at your particular\nlocation. MailMan lets you choose from the list of available editors. \n \nThe 'PREFERRED EDITOR:' field can be set through the User Options Edit option\non the Personal Preferences menu. \nThe Preferred Editor field provides you with the opportunity to choose the\neditor you wish to use while in MailMan. You use an editor when editing a\nVA FileMan word processing field (e.g., when you respond to or type a new\nmessage). If you have chosen a Preferred Editor and you are editing a word\nprocessing field, MailMan will automatically transfer you into your\nPreferred Editor. If you don't enter a specific editor in the Preferred\nEditor field, MailMan will default to either the VA FileMan [SCREEN] editor\nwhen editing within ScreenMan or the VA FileMan [LINE] Editor in all other\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 16:21:00\n", "", "USER,ONE\n", "", ""], ["966", "XM-U-P-OFFICE INFO", "CONTACT INFORMATION\n", "", "", "\n \n * STATE - This is the user's state.\n \n * ZIP CODE - This is the user's postal ZIP code.\n \n * OFFICE PHONE - This is the user's business/office contact telephone.\n \n * FAX NUMBER - This field contains the telephone number for a user's FAX\n machine. It needs to be in a format that can be understood by a\n sending modem.\n \nYour contact information is comprised of the following fields, which\n * VOICE PAGER - This field contains the telephone number for a user's\n analog pager. It needs to be in a format that can be understood by a\n sending modem.\n \n * DIGITAL PAGER - This field contains the telephone number for a user's\n digital page. It needs to be a format that can be understood by a\n sending modem.\n \n * ADD'L PHONE 1 - This is an alternate (additional) telephone number\n where the user might also be reached.\nreside in the NEW PERSON file (#200):\n \n * ADD'L PHONE 2 - This is another alternate (additional) telephone\n number where the user might also be reached.\n \nThese fields are all self-explanatory. You can use these fields to store\nyour business (or personal) information. MailMan does not require you to\nenter any information into these fields.\n \nMailMan displays your contact information when users do a lookup on you\nthrough the User Information option on the Help (User/Group Info., etc.)\n \nmenu.\n \nThe contact information fields can be set through the User Options Edit\noption on the Personal Preferences menu.\n * STREET ADDRESS 1, 2, & 3 - These three fields are the 3 lines of the\n user's address.\n \n * CITY - This is the user's city.\n \n
\n\n", "", "", "2002-05-07 07:26:00\n", "", "USER,ONE\n", "", ""], ["97", "XUDOC SPOOL USE2", "WHY SPOOL?\n", "", "", "\nThere are several reasons to spool:\n \n - The program can run to completion without printer problems interfering.\n \nSpooling saves output in a buffer area for printing at a later time. This\nhappens when you send or queue to the spool device. It's a good way to\nstore the results of a time-consuming calculation, such a complex VA File\nManager search or print option. It also provides on-line storage so you\ncan quickly print multiple copies at any time.\n \n - The printer may not be free.\n \n - Multiple copies may be desired.\n \n - Your program may require intensive processing time and is best run at\n night when the computer is lightly used. Output can then be printed\n during the day when someone can attend the printer.\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["970", "XM-U-M-TRANSMIT NOW", "SEND A MESSAGE NOW ('Transmit Now')\n", "", "", "\n \nMailMan automatically gives the message an internal message identification\nnumber and puts the message in the delivery queue to be delivered to the\nrecipients.\n \nMailMan will then notify you that the message has been sent.\nYou can use the Transmit Now action code (i.e., 'T') to have MailMan\nsend your message to all recipients. You would use this action code after\nyou've taken all other actions on your message.\n \nTo send a message now, enter a 'T' or press the Return/Enter key to accept\nthe 'Transmit now' default at the 'Select Message option: Transmit now//'\nprompt.\n \n
\n\n", "", "", "1998-12-14 13:58:07\n", "", "USER,ONE\n", "", ""], ["971", "XM-U-M-CLOSED", "CLOSED MESSAGES\n", "", "", "\n \nTransmit now//' prompt.\nWhen you are sending a message, you can use the Closed Message action code\n(i.e., 'X') to prevent recipients of your message from [FORWARDING] that\nmessage on to other recipients not originally included in the recipient\nlist. (You, the sender, will still be able to forward the message.)\nThis is a toggle action code. If you enter 'X' again, the message will no\nlonger be closed.\n \nTo make a message 'closed,' enter an 'X' at the 'Select Message option:\n
\n\n", "\n- \n\n
\n", "", "2002-07-18 13:53:00\n", "", "USER,ONE\n", "", ""], ["972", "XM-U-M-EDIT SUBJECT", "EDIT THE SUBJECT OF A MESSAGE\n", "", "", "\n \nTo edit the subject of a message prior to sending it, enter an 'ES' at the\n'Select Message option: Transmit now//' prompt or enter an 'E' at the\n'Enter message option' prompt and then enter 'ES' at the 'Select Edit\noption:' prompt.\nYou can use the Edit Subject action code (i.e., 'ES') to change the\nsubject text of a message you intend on sending.\n \nThe subject of the message is shown whenever the message is displayed. It\ncan be from 3 to 65 characters in length. Any leading and trailing blanks\nare deleted. Also, any sequence of three or more blanks is reduced to two\nblanks.\n \n
\n\n", "", "", "1999-12-13 13:35:00\n", "", "USER,ONE\n", "", ""], ["973", "XM-U-M-EDIT TEXT", "EDIT THE TEXT OF A MESSAGE\n", "", "", "\n \nYou can use the Edit Text action code (i.e., 'ET') to change the text\n(body) of the message you intend on sending. You can add to, modify, or\ndelete any part of the text within the body of the message.\n \nTo edit the text of a message prior to sending it, enter an 'ET' at the\n'Select Message option: Transmit now//' prompt or enter an 'E' at the\n'Enter message option' prompt and then enter 'ET' at the 'Select Edit\noption:' prompt.\n
\n\n", "", "", "2000-05-15 09:34:00\n", "", "USER,ONE\n", "", ""], ["974", "XM-U-M-EDIT RECIPIENTS", "EDIT RECIPIENTS\n", "", "", "\n \n'And Send to:' prompt. For example: '-SMITH,JOE'.\nYou can use the Edit Recipients action code (i.e., 'ER') to add or remove\nrecipients from a message you intend on sending. \n \nTo edit the recipients of a message prior to sending it, enter an 'ER' at\nthe 'Select Message option: Transmit now//' prompt.\n \nFor example, to remove a recipient, type a minus sign or hyphen (i.e.,\n'-') followed by the first portion of the recipient's last name after the\n
\n\n", "", "", "1998-12-15 10:38:00\n", "", "USER,ONE\n", "", ""], ["975", "XM-U-B-READER DIFF-2", "BASKET ACTION CODES (CONTINUED)\n", "", "", "\n\n \nFor commands which act on one or more messages, you can [SELECT] the messages\nprior to entering the command, or specify a [RANGE] of messages after entering\nthe command. If you select messages, additional commands become available: \n \n [O] Opposite selection toggle.\n [Z] Zoom toggle.\n \nWhen you have a basket with a long list of messages, you can [NAVIGATE] about\nthe basket by paging through the messages.\n ?string Search for messages in the basket whose subject\n \n [MORE]...\n [CONTAINS] the string entered.\n ??string Search for messages anywhere on the system, which you ever sent\n or received, whose subject [BEGINS WITH] the string entered.\n \nThe following are available only with the Full Screen message reader:\n \n [CD] Change detail. (Toggle between summary and detailed display.)\n
\n\n", "\n- \n\n
\n", "", "1999-03-19 14:51:00\n", "", "USER,ONE\n", "", ""], ["976", "XM-U-B-ZOOM TOGGLE", "ZOOM SELECTION TOGGLE\n", "", "", "\n \nmessage, a right-angle bracket ('>') is displayed to the left of the\nselected message in the list.\n \nTo zoom in on just the selected messages (and zoom out again), you enter\n'Z' after the 'Enter message number or command:' prompt.\nThe Zoom Selection Toggle is used to 'zoom' in on a group of messages that\nhave been selected for subsequent group action. Using this action code\nallows you to just display those selected messages and not the entire list\nof messages in the mail basket. This can be useful when you have a long\nlist of messages and have selected messages throughout the entire list.\n \nIn order to use the Zoom Selection Toggle, you must have first selected at\nleast one message in the list of messages. When you have selected a\n\n\n", "", "", "1998-12-15 14:35:19\n", "", "USER,ONE\n", "", ""], ["977", "XM-U-B-OPPOSITE TOGGLE", "OPPOSITE SELECTION TOGGLE\n", "", "", "\n \nwon't be changing, and then, using the Opposite Selection Toggle, to\nreverse your selection and perform the action on the majority of the\nopposite messages in the message list.\n \nIn order to use the Opposite Selection Toggle, you must have first\nselected at least one message in the list of messages. When you have\nsuccessfully selected a message, a right-angle bracket ('>') is displayed\nto the left of the selected message in the list.\n \nTo toggle from the selected messages to the unselected messages (and vice\nYou can use the Opposite Selection Toggle action code (i.e., 'O') to\nversa), you enter 'O' after the 'Enter message number or command:' prompt.\nreverse or choose the opposite of your selected messages in a list of\nmessages that have been selected for subsequent group action. \n \nUsing this action code allows you to simply select unselected\nmessages and deselect previously selected messages. This can be useful\nwhen you have a long list of messages and the majority of the messages\nwill undergo the same action. It's easier to select a smaller group that\n\n\n", "", "", "1998-12-15 14:39:27\n", "", "USER,ONE\n", "", ""], ["978", "XM-U-B-CHANGE DETAIL", "CHANGE DETAIL\n", "", "", "\n \nSummary Full Screen), this command either removes several columns from the\ndisplay giving the remaining columns space to display more information in\na more streamlined fashion or adds several columns from the display giving\nyou more information about each message.\n \nTo change detail, enter a 'CD' after the 'Enter message number or\ncommand:' prompt.\nWhen viewing a list of messages using either the Summary or Detailed Full\nScreen message reader, you can use the Change Detail action code (i.e.,\n'CD') to toggle between the [SUMMARY] and [DETAILED] Full Screen message\nreaders list of messages. Simply entering the Change Detail ('CD') command\nat the 'Enter message number or command:' prompt causes the message reader\nto toggle.\n \nDepending on which message reader you've selected (i.e., Detailed or\n\n\n", "\n- \n\n
\n", "", "1999-01-14 12:53:00\n", "", "USER,ONE\n", "", ""], ["979", "XM-U-B-BASKET NAME CHANGE", "CHANGE A MAIL BASKET NAME\n", "", "", "\n \nThe Change Basket action code (i.e., 'C') allows you to rename the mail\nbasket you are currently processing to any [VALID] mail basket name.\nHowever, you are not allowed to change the 'WASTE' or 'IN' mail basket\nnames.\n \nTo change a mail basket name, enter a 'C' at the 'Enter message number or\ncommand:' prompt.\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 12:29:00\n", "", "USER,ONE\n", "", ""], ["98", "XUDOC SPOOL USE3", "RETRIEVING YOUR SPOOLED DOCUMENTS\n", "", "", "\nNow that you have created some spool documents, go to the Spooler Menu to\n LIST This will display a listing of spool documents.\n \n [PRINT] This option allows the printing of documents.\n \n DELETE Each user is allocated a limited amount of space\n for spooling. As a general rule you should\n delete unnecessary documents, and you will have\n to delete some if you run out of space.\n \n [MAKE INTO MAIL MESSAGE] This option is not generally available since\nfind out how you can retrieve your documents. The Spooler Menu is usually\n the MailMan storage space is limited. See your\n IRM representative if you need this option.\nincluded in the Common menu, what you see when you type two question\nmarks at any main menu prompt. For quick access to the Spooler Menu, enter\nthe first few letters of the menu text preceded by a double quote ("SP). \n \n GIVE ACCESS TO OTHERS Use this option to specify who may access which of\n your spool documents.\n \n\n\n", "\n- \n\n
\n", "", "1992-04-15 11:41:00\n", "", "USER,ONE\n", "", ""], ["980", "XM-U-B-READER DIFF-3", "BASKET ACTION CODES (CONTINUED)\n", "", "", "\n \n \n I Ignore the default message to be read and make the\n next message in the basket the default.\n\nFor the commands which act on one or more messages, you must specify a [RANGE]\nof messages after entering the command. \nAvailable only with the Classic message reader, are the following basket\naction codes:\n \n ? View a summary listing of messages in a basket.\n \n ?? View a detailed listing of messages in a basket.\n \n ???? or ?HELP Display detailed help. \n
\n\n", "\n- \n\n
\n", "", "1999-03-19 13:51:00\n", "", "USER,ONE\n", "", ""], ["981", "XM-I-S-SITE PARAMETERS", "MAILMAN SITE PARAMETERS FILE\n", "", "", "\n \n\n [LOCAL] Messaging\n\n [REMOTE] Messaging\n\n [DISK] Space Management\nThe MAILMAN SITE PARAMETERS file (#4.3) lets site managers tailor MailMan\nfor your site.\n \nSite managers should be aware of the following areas:\n\n [IDENTITY] Settings\n\n [USER] Settings\n
\n\n", "\n- \n\n
\n", "", "2002-05-07 08:20:00\n", "", "USER,ONE\n", "", ""], ["982", "XM-I-S-BIG GROUP SIZE", "BIG GROUP SIZE FIELD\n", "", "", "\n \n \n * At least one or more distribution lists.\n \nThe BIG GROUP SIZE (Field #7.2) in the MAILMAN SITE PARAMETERS file (#4.3)\nallows IRM to set the number used to indicate when a mail group is\nconsidered 'large.' This helps eliminate the 'dots of death' when\naddressing mail to a large group.\n \nIRM can populate this field with a number ranging from 50 to 10,000 (no\ndecimal points). There is no default for this field. If BIG GROUP SIZE\nWhen addressing messages to mail groups, mail groups can be classified as\nequates to zero, then groups are processed in the foreground, as usual.\n \nIf IRM populates this field and if the group being addressed contains any\nmember groups, or distribution lists, or the number of local members plus\nremote members exceeds or equals the BIG GROUP SIZE, then the user is\nasked whether or not they want to queue the group for [LATER] delivery and\navoid waiting while the group is processed. The user is also warned that\nif they choose to queue the delivery, then recipients cannot be 'minused'\nfrom the group.\n \n'large' (site-specified) and processed differently from 'small-' to\nIf the user chooses to queue the delivery to the group, they are asked\nwhen the delivery should take place. The group will be queued for\nprocessing and delivery at the specified date and time by the same\nbackground job that 'news' messages.\n \nIf the user chooses not to queue the delivery to the group, then\nprocessing proceeds in the foreground, as usual.\n'medium-sized' mail groups. A mail group may be considered 'large' when it\nhas any of the following:\n \n * A large number of local and remote members.\n \n * At least one or more member groups.\n
\n\n", "\n- \n\n
\n", "", "1999-06-29 13:07:00\n", "", "USER,ONE\n", "", ""], ["983", "XM-I-S-MESSAGE LINE LIMIT", "P-MESSAGE LINE LIMIT FIELD\n", "", "", "\n \nIf this field is null, there is no limit set when writing to the P-MESSAGE\ndevice.\n \nIf a value is entered into this field, the number of lines written to the\nP-MESSAGE device is limited to that value. If the number of lines exceeds\nthis value, MailMan will truncate the report when it reaches the maximum\nnumber of lines and puts the following message (between lines of\nasterisks) at the end of the message text:\n \n *******************************************************************\nThe P-MESSAGE LINE LIMIT field (#16.1), in the MAILMAN SITE PARAMETERS\n P-MESSAGE line limit of nnnn reached. Rest of file ignored.\n *******************************************************************\nfile (#4.3), allows IRM to set the maximum number of lines that can be\nwritten to the [P-MESSAGE] device. This helps MailMan to operate more\nefficiently when using the P-MESSAGE device.\n \nIRM can populate this field with a number ranging from 2000 to 9,999,999\n(no decimal points). There is no default for this field.\n \n
\n\n", "\n- \n\n
\n", "", "1998-12-16 09:54:57\n", "", "USER,ONE\n", "", ""], ["984", "XM-I-S-MAX DIGITS FOR MSG NUM", "MAX DIGITS FOR MESSAGE NUMBER FIELD\n", "", "", "\n \n \nNOTE: MailMan internal message identification numbers start at 100,000\n to avoid any confusion between message numbers and message\n sequence numbers in baskets.\n \nIRM can populate this field with a number ranging from 7 to 14 (no decimal\npoints). If this field is left null, the default will be eight digits.\n \nIf the MailMan internal message identification number exceeds the number\nof digits stored in this field, the message number will recycle back to\nMailMan can reuse/recycle internal message identification numbers when\nthe next vacant message number after 99999.\n \nIf MailMan is not able to find a vacant message number less than the\nallowable number (i.e., value stored in the MAX DIGITS FOR MESSAGE NUMBER\nfield), then MailMan will take the next available message number, no\nmatter how many digits it has, and automatically change this field to\nreflect the new maximum. Thus, it is very important that the unreferenced\nmessages purge and/or date purge be run on a regular basis.\n \n \ncreating messages. Thus, MailMan can avoid creating huge message numbers,\nOTHER RELATED FIELDS:\n \nBecause of the MAX DIGITS FOR MESSAGE NUMBER field, the purge routines\noperate off the LOCAL CREATE DATE field (#31), in the MAIL BOX file (#3.9)\nand its 'C' cross-reference.\n \nThis field is set with the current date (no time) when a new message stub\nis created. (For locally created messages, this will usually, but not\nnecessarily, be the same as the date sent. For incoming messages from\nremote sites, this acts as a 'date-received' stamp.)\nmaking them more manageable in size.\n \nThe date purge routine runs fast, because it has an appropriate\ncross-reference to work with.\n \nOther fields in Files #3.7 and #4.3, that refer to date include:\n \n MAIL BOX File (#3.7):\n \n Field Number Field Name\n ------------ -----------------------\n \n 3.7,1.2 DATE @ REINSTATEMENT\n \n \n MAILMAN SITE PARAMETERS File (#4.3):\n \n Field Number Field Name\n ------------ ------------------------\n 4.3,4.301 NO-PURGE DAYS BUFFER\n 4.302,3 START PURGE DATE\n 4.302,4 STOP PURGE DATE\nThe MAX DIGITS FOR MESSAGE NUMBER field (#17.1),in the MAILMAN SITE\n 4.302,8 LAST DATE PROCESSED\n 4.3,4.304 WEEKDAY DAYS TO PURGE\nPARAMETERS file (#4.3), allows IRM to set the maximum number of digits\nthat can comprise a MailMan internal message identification number before\nthey recycle back and start again from 100,000.\n
\n\n", "", "", "2002-05-06 15:37:00\n", "", "USER,ONE\n", "", ""], ["985", "XM-U-P-OPTIONS-2", "PERSONAL PREFERENCES (CONTINUED)\n", "", "", "\n \n 'IN' basket (e.g., ignore or delete messages).\n \n * [MESSAGE ACTION] DEFAULT - Choose your default message action for the\n 'IN' basket (e.g., ignore or delete messages).\n \n * [ASK BASKET] - Decide whether you want to be prompted each time to\n choose a mail basket whenever you send yourself e-mail.\n \n * SHOW [TITLES] - Decide whether you want a a sender's title displayed.\n \n * MESSAGE [READER] PROMPT - Specify whether the reader you've chosen\n[MORE]...\n should be used all the time or whether you want to be asked each time\n you use the Read/Manage Messages option.\n \n * [NEW] MESSAGES DEFAULT OPTION - Choose your default option to appear\n when you select the 'New Messages and Responses' option.\n \n * SHOW MESSAGE [PREVIEW] - Choose your default message action for the\n
\n\n", "\n- \n\n
\n", "", "2000-07-26 07:43:00\n", "", "USER,ONE\n", "", ""], ["986", "XM-U-P-OPTIONS-3", "PERSONAL PREFERENCES (CONTINUED)\n", "", "", "\n \n you'd like to read from first, if they contain new messages.\n \n * PREFERRED [EDITOR] - Choose your preferred MailMan editor when sending\n new or responding to messages.\n \n * [OFFICE INFORMATION] - Enter or edit your office information (e.g.,\n business address, telephones, etc.).\n * MAILMAN [INSTITUTION] - Enter or edit your MailMan institution.\n \n * [NETWORK SIGNATURE] - Enter or edit your Network Signature (three\n lines), required when [ANSWERING] messages.\n \n * [INTRODUCTION] - Enter or edit your MailMan introduction.\n \n * READ NEW MESSAGES [BASKET] PRIORITY - Choose which, if any, baskets\n
\n\n", "\n- \n\n
\n", "", "2000-07-26 07:08:00\n", "", "USER,ONE\n", "", ""], ["987", "XM-U-A-LOCAL USER NAME", "ENTERING A LOCAL USER'S NAME IN MAILMAN\n", "", "", "\n \nfrom a list. However, you'll narrow your choices by entering more\ncharacters of the name.\n\nYou can get detailed [INFORMATION] about a user in two ways:\n\n * From the mail MailMan menu, select Help!User Information.\n\n * At the 'And Send to:' prompt, enter ??, then select User Information.\n \n[MORE]... \nLocal users can be selected by last name, initials, or nickname (often the\nfirst name). \n \nWhen entering a local user name, MailMan only requires that you enter the\nfirst portion of the last name (user names are not case sensitive);\nMailMan will find the appropriate person based on your partial entry and\nautomatically display the rest of the name to you. If more than one person\nis found based on your partial entry, MailMan will allow you to choose\n
\n\n", "\n- \n\n
\n", "", "1999-01-21 08:30:00\n", "", "USER,ONE\n", "", ""], ["988", "XM-U-Q-REMOTE USER NAME", "ENTERING A REMOTE USER'S NAME WHEN FILTERING OR SEARCHING MAIL\n", "", "", "\n \n * Enter any portion of the remote user's name (not case sensitive),\n the at-sign ('@' Shift-2 key on most keyboards), and any portion of\n their domain name (not case sensitive, i.e., name@domain). The name\n and domain name strings entered must be from 1 to 45 characters in\n length (not case sensitive).\n \n * Enter the at-sign ('@' Shift-2 key on most keyboards) and any portion\n of their domain name (not case sensitive, i.e., @domain). The domain\n name string entered must be from 1 to 45 characters in length (not\n case sensitive).\nWhen entering the name of a user at a remote location (not located at your\n \nNOTE: The more characters you provide, the narrower the search will be.\nsite) for filtering or searching for mail, do any of the following:\n \n * Enter any portion of the remote user's name (not case sensitive)\n followed by the at-sign ('@' Shift-2 key on most keyboards, i.e.,\n name@). The name string entered must be from 1 to 45 characters in\n length (not case sensitive).\n \n\n\n", "", "", "1998-12-17 08:04:49\n", "", "USER,ONE\n", "", ""], ["989", "XM-U-A-GROUP LARGE", "ADDRESSING MAIL TO LARGE MAIL GROUPS\n", "", "", "\n \nopportunity to queue (i.e., [LATER]) the message for delivery to that group at\na later date and time (background processing). Thus, you don't have to wait\nwhile all members of the mail group are added to the recipient list (i.e., you\navoid the 'dots of death') and you are not prevented from taking other actions.\n \nAddressing a message to a 'small-' or 'medium-sized' mail group is processed in\nthe foreground as usual. Also, if you choose to 'Later' a message to a 'large'\nmail group, you will not be able to remove (minus) members from the group\nbefore sending the message. \n \nWhen addressing messages to mail groups, mail groups can be classified as\n[MORE]... \n'large' (site-specified) and processed differently from 'small-' to\n'medium-sized' mail groups. A mail group may be considered 'large' when it has\na large number of local and remote members, member groups, or distribution\nlists (nationwide mail groups). IRM sets the number used to indicate when a\nmail group is considered 'large' (i.e., [BIG GROUP SIZE] field). \n \nIf you address a message to a 'large' mail group, MailMan gives you the\n
\n\n", "\n- \n\n
\n", "", "1999-01-20 12:20:00\n", "", "USER,ONE\n", "", ""], ["99", "XUDOC SPOOL USE4", "PRINTING SPOOLED DOCUMENTS\n", "", "", "\nHow do you print out what you've spooled? Where did the job go when you\n from the spooler and\n /\n /\n sends it to\n /\n /\n a printer (or several printers).\n \nTry printing. Use a margin of 132 characters and page length of 66 lines\nto match the spool format even though your document may not be this big.\nsent it to the spooler? How can you get it back?\nThen specify the number of copies, and the printing device. If you need to\nuse several printers, the device prompt will reappear and you may respond.\n \n Spooling --------- sends to --------------> the spooler (spool space).\n =================\n |"your document"|\n =================\n /\n Printing ---- gets your document /\n
\n\n", "", "", "1989-01-20 00:00:00\n", "", "USER,ONE\n", "", ""], ["990", "XM-U-P-READER PROMPT", "MESSAGE READER PROMPT\n", "", "", "\n \nMailMan message reader when reading your messages.\n \nFor example, if you wish to use the Detailed Full Screen reader\nexclusively, set the MESSAGE READER to 'Detailed Full Screen' and the\nMESSAGE READER PROMPT to 'No, don't ask me, just use the default' via the\nUser Options Edit option.\nOnce you have decided on a message reader, you can specify whether the\nreader you just chose should be used all the time or whether you want to\nbe asked each time you use the [READ]/Manage Messages option.\n \nUse the User Options Edit option on the Personal Preferences menu and\nPress the Return/Enter key until you reach the the 'MESSAGE READER\nPROMPT:' question. The default for this prompt is 'Yes, ask me.' By\nanswering 'No' to this prompt, you avoid being asked each time to choose a\n
\n\n", "\n- \n\n
\n", "", "1998-12-22 11:10:15\n", "", "USER,ONE\n", "", ""], ["991", "XM-U-R-NEW READ", "READ NEW MAIL BY BASKET\n", "", "", "\n \nMailMan would immediately begin displaying your first new message in that\none basket. It would continue to display all subsequent new messages in\nthat basket until all new messages have been read or you quit that option\nby entering an up-arrow ('^' Shift-6 key on most keyboards) at the message\noption prompt.\n \nAs the default, MailMan will start processing new mail in your "IN"\nbasket. If you choose a basket other than "IN," MailMan "cycles" through\nall new mail in all baskets in basket name order (alphabetically).\nYou can read all of your new mail basket by basket when you choose the\nRead new mail by basket option. This is the default. When you have new\nmail in more than one [BASKET], MailMan will ask you to choose from which\nbasket you wish to begin reading your mail.\n \nWhen you have read all your mail in one basket and still have new mail in\nother mail baskets, MailMan will prompt you to choose another mail basket\nto continue reading your new mail. If you only had new mail in one basket,\n\n\n", "\n- \n\n
\n", "", "1998-12-23 11:35:16\n", "", "USER,ONE\n", "", ""], ["992", "XM-U-R-NEW LIST BASKETS", "LIST BASKETS WITH NEW MAIL\n", "", "", "\n \n \nTo list baskets with new mail, enter an 'LB' after the 'Select New mail\noption: Read new mail by basket//' prompt.\nYou can list all of your mail baskets with new mail by choosing the List\nBaskets with new mail option available with the New Messages and Responses\noption.\n \nMailMan will display a list of all of your mail baskets with new mail.\nMailMan also tells you how many new messages reside in each mail basket.\nWith this information, you can choose another new mail option to read your\nnew mail (e.g., Read new mail by basket option).\n
\n\n", "", "", "1998-12-23 11:37:50\n", "", "USER,ONE\n", "", ""], ["993", "XM-U-R-NEW LIST ALL", "LIST ALL NEW MESSAGES\n", "", "", "\n \noption: Read new mail by basket//' prompt.\n \nAfter displaying the list of new messages, MailMan asks you to enter a\nmessage number or specific command at the 'Enter message number or\ncommand:' prompt. You have several [OPTIONS].\nYou can list all of your new mail in your mailbox, regardless of the mail\nbasket, when you choose the List all new messages option available with\nthe New Messages and Responses option.\n \nMailMan displays [DETAILED] information on each message using the Full Screen\nmessage reader.\n \nTo list all new messages, enter an 'LN' after the 'Select New mail\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 10:12:00\n", "", "USER,ONE\n", "", ""], ["994", "XM-U-R-NEW LIST PRIORITY", "LIST ALL PRIORITY MESSAGES\n", "", "", "\n \nmail basket, when you choose the List all priority messages option\navailable with the New Messages and Responses option.\n \nMailMan displays [DETAILED] information on each message.\nAfter displaying the list of new messages, MailMan asks you to enter a\nmessage number or specific command at the 'Enter message number or\ncommand:' prompt. You have several [OPTIONS].\n \nTo list all priority messages, enter an 'LP' after the 'Select New mail\noption: Read new mail by basket//' prompt. If you use this option and you\nWhen MailMan delivers priority mail to your mailbox, you get a special\ndon't have any new priority messages, MailMan will display the following\nmessage: 'You have no new Priority messages.'\nnotification. For example, when first entering the MailMan Menu, MailMan\ndisplays any new priority message(s) before displaying the MailMan Menu\nand displays a message (i.e., 'There is PRIORITY Mail!'). As a further\nhighlight, all priority messages displayed to you in a list will be\npreceded by an exclamation point.\n \nYou can list all of your priority mail in your mailbox, regardless of the\n
\n\n", "\n- \n\n
\n", "", "1999-01-14 10:37:00\n", "", "USER,ONE\n", "", ""], ["995", "XM-U-R-NEW PRINT", "PRINT ALL NEW MESSAGES\n", "", "", "\n \n \n * When - When was the message printed as opposed to when it was sent.\n \nTo print all of your new mail, enter a 'P' after the 'Select New mail\noption: Read new mail by basket//' prompt.\n \nPressing the Return/Enter key after each page tells MailMan to continue\nprinting your new messages in succession. To exit this option, before\nyou've finished printing all new messages, you must enter the up-arrow\n('^' Shift-6 key on most keyboards).\nYou can print all of your new mail in your mailbox, regardless of the mail\nbasket, when you choose the Print all new messages option available with\nthe New Messages and Responses option. MailMan prints each message with\nprint header information. This print information helps you differentiate:\n \n * Who - For whom was the message printed.\n \n * Where - At what location was the message printed.\n\n\n", "", "", "1998-12-23 11:52:45\n", "", "USER,ONE\n", "", ""], ["996", "XM-U-R-NEW SCAN", "SCAN ALL NEW MESSAGES\n", "", "", "\n \nthe New Messages and Responses option.\n \nTo scan all of your new messages, enter an 'S' after the 'Select New mail\noption: Read new mail by basket//' prompt.\n \nAs you continuously press the Return/Enter key, MailMan automatically\ndisplays your new mail until there is no more new mail. If you want to\nquit scanning your new mail before reaching the end, simply enter the\nup-arrow ('^' Shift-6 key on most keyboards) to exit the option.\nScanning your new messages is similar to [READING] your new messages by\nbasket. However, when scanning messages, you are not prompted between\nbaskets. You automatically pass from reading new messages in one basket to\nreading the new messages in the next basket without any user prompts or\nuser action required between baskets.\n \nYou can scan all of your new mail in your mailbox, regardless of the mail\nbasket, when you choose the Scan all new messages option available with\n\n\n", "\n- \n\n
\n", "", "1998-12-23 11:53:29\n", "", "USER,ONE\n", "", ""], ["997", "XM-U-B-READER DETAILED LIST", "DETAILED INFORMATION DISPLAYED WITH MESSAGE LISTS\n", "", "", "\n \n \n * Basket - Basket containing the message (e.g., 'IN').\n \n * MailMan Internal Message Identification Number - The MailMan message\n number generated internally for the message (displayed in brackets).\n\n * Message Sent Date - The date the message was sent (i.e., day, month, year).\n \n * Subject - Subject of the message.\n \nMailMan provides detailed information on each message when displaying a\n * Lines - Number of lines of text in the message.\n \n * From - The name of the person who sent the message.\n \n * Read/Rcvd - Total number of responses read and received for that message.\n If there are no responses to a message, no totals will be indicated.\nmessage list. This information includes the following:\n \n * Flags - Any special flag associated with the message. For example:\n Priority (!) or New (*) flags.\n \n * Message Number - The number associated with the message (meaningful\n for this list only).\n
\n\n", "", "", "1999-01-14 10:18:00\n", "", "USER,ONE\n", "", ""], ["998", "XM-U-P-PERSONAL PREFERENCES", "PERSONAL PREFERENCES MENU\n", "", "", "\n \n * Enroll in (or Disenroll from) a [MAIL GROUP]\n * [PERSONAL] Mail Group Edit\n * [FORWARDING] Address Edit\n \nTo access this menu from the main MailMan Menu, enter 'Personal\nPreferences' at the 'Select MailMan Menu Option:' prompt.\nThe MailMan interface includes a Personal Preferences menu. It consists of\nthe following options:\n \n * [USER] Options Edit\n * [BANNER] Edit\n * [SURROGATE] Edit\n * Message [FILTER] Edit\n * [DELIVERY] Basket Edit\n
\n\n", "\n- \n\n
\n", "", "1998-12-23 15:51:29\n", "", "USER,ONE\n", "", ""], ["999", "XM-U-BO-CLASSIC", "CLASSIC READER BASKET MESSAGE ACTIONS\n", "", "", "\n \n [D] Delete messages.\n [F] Forward messages.\n [FI] Filter messages.\n [L] Later messages.\n [P] or [H] Print messages with or without a header.\n [NT] New Toggle messages.\n [S] Save messages to another basket.\n [T] Terminate messages.\n [V] Set Vaporize date for messages.\n [X] Toggle transmit priority in remote message queues. (POSTMASTER only)\nEnter ^ to exit, or press <Enter> to read the default message, or enter:\n\n [MORE]...\n ? or ?? See a [SUMMARY] or [DETAILED] list of messages in this basket,\n beginning with the default message.\n n Read message n, where n is a sequence [NUMBER] in this basket or\n an internal message ID of any message on the system.\n \nThe following commands act on one or more messages in this basket. You\nwill be asked to specify a [RANGE] of messages after entering the command.\n
\n\n", "\n- \n\n
\n", "", "2000-06-07 14:35:00\n", "\n- \n\n
\n", "USER,ONE\n", "", ""]]}