Difference between revisions of "Begin Configuration of Vista"
(→Set Up Menus for the System Manager) |
DavidWhitten (talk | contribs) m (Reverted edits by NeilArmstrong (talk) to last revision by Shabiel) |
||
| (13 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Vista Configuration on Linux running GT.M<br />'''Mark Street'''<br />Emulated from Nancy Anthracite's Vista Configuration HOWTO on | + | ---- |
| + | * '''Editor's note: This page was written in 2005. The settings it recommends seem to apply to FOIA VistA, and may not be appropriate for the newer versions of VistA such as WorldVistaEhr VOE, OpenVistA, or Astronaut. However, it is still a valuable reference for how to find and use the various configuration menus.''' | ||
| + | ---- | ||
| + | Vista Configuration on Linux running GT.M<br />'''Mark Street'''<br />Emulated from Nancy Anthracite's Vista Configuration HOWTO on [http://www.hardhats.org/ hardhats.org] | ||
| + | |||
The '''BOLD''' entries represent user supplied input during the configuration process.<br /> | The '''BOLD''' entries represent user supplied input during the configuration process.<br /> | ||
| Line 27: | Line 31: | ||
From the vista user's login prompt type the gtm command. | From the vista user's login prompt type the gtm command. | ||
| − | [vista@localhost]$ <b>gtm</b> | + | [vista@localhost]$ <b>gtm</b> |
| − | <br /> | + | <br /> |
ZTMGRSET - Define the Vista global variables and save the system M routines for your operating system.<br /><br /> | ZTMGRSET - Define the Vista global variables and save the system M routines for your operating system.<br /><br /> | ||
| − | GTM>'''D ^ZTMGRSET''' | + | GTM>'''D ^ZTMGRSET''' |
| − | <br /> | + | <br /> |
| − | ZTMGRSET Version 8.0 **34,36,69,94,121,127,136,191,275**<br /> | + | ZTMGRSET Version 8.0 **34,36,69,94,121,127,136,191,275**<br /> |
| − | HELLO! I exist to assist you in correctly initializing the current account.<br /><br /> | + | HELLO! I exist to assist you in correctly initializing the current account.<br /><br /> |
| − | + | ||
| − | THIS MAY NOT BE THE MANAGER UCI.<br /> | + | THIS MAY NOT BE THE MANAGER UCI.<br /> |
| − | I think it is VAH,ROU. Should I continue anyway? N//'''Y'''<br /> | + | I think it is VAH,ROU. Should I continue anyway? N//'''Y'''<br /> |
| − | I think you are using GT.M (Unix)<br /> | + | I think you are using GT.M (Unix)<br /> |
| − | Which MUMPS system should I install?<br /> | + | Which MUMPS system should I install?<br /> |
| − | <br /> | + | <br /> |
| − | 1 = VAX DSM(V6), VAX DSM(V7)<br /> | + | 1 = VAX DSM(V6), VAX DSM(V7)<br /> |
| − | 2 = MSM-PC/PLUS, MSM for NT or UNIX<br /> | + | 2 = MSM-PC/PLUS, MSM for NT or UNIX<br /> |
| − | 3 = OpenM for NT, Cache/NT, Cache/VMS<br /> | + | 3 = OpenM for NT, Cache/NT, Cache/VMS<br /> |
| − | 4 = Datatree, DTM-PC, DT-MAX<br /> | + | 4 = Datatree, DTM-PC, DT-MAX<br /> |
| − | 5 = MVX,ISM VAX<br /> | + | 5 = MVX,ISM VAX<br /> |
| − | 6 = ISM (UNIX, Open VMS)<br /> | + | 6 = ISM (UNIX, Open VMS)<br /> |
| − | 7 = GT.M (VMS)<br /> | + | 7 = GT.M (VMS)<br /> |
| − | 8 = GT.M (Unix)<br /> | + | 8 = GT.M (Unix)<br /> |
| − | System: 8//'''8'''<br /> | + | System: 8//'''8'''<br /> |
| − | <br /> | + | <br /> |
| − | I will now rename a group of routines specific to your operating system. | + | I will now rename a group of routines specific to your operating system. |
| − | Routine: ZOSVGUX Loaded, Saved as %ZOSV<br /> | + | Routine: ZOSVGUX Loaded, Saved as %ZOSV<br /> |
| − | Routine: ZTBKCGUX Missing<br /> | + | Routine: ZTBKCGUX Missing<br /> |
| − | Routine: ZIS4GTM Loaded, Saved as %ZIS4<br /> | + | Routine: ZIS4GTM Loaded, Saved as %ZIS4<br /> |
| − | Routine: ZISFGUX Missing<br /> | + | Routine: ZISFGUX Missing<br /> |
| − | Routine: ZISHGUX Loaded, Saved as %ZISH<br /> | + | Routine: ZISHGUX Loaded, Saved as %ZISH<br /> |
| − | Routine: XUCIGTM Loaded, Saved as %XUCI<br /> | + | Routine: XUCIGTM Loaded, Saved as %XUCI<br /> |
| − | Routine: ZISETGUX Missing<br /> | + | Routine: ZISETGUX Missing<br /> |
| − | Routine: ZOSV2GTM Loaded, Saved as %ZOSV2<br /> | + | Routine: ZOSV2GTM Loaded, Saved as %ZOSV2<br /> |
| − | Routine: ZISTCPS Loaded, Saved as %ZISTCPS<br /> | + | Routine: ZISTCPS Loaded, Saved as %ZISTCPS<br /> |
| − | <br /> | + | <br /> |
| − | NAME OF MANAGER'S UCI,VOLUME SET: VAH,ROU//<br /> | + | NAME OF MANAGER'S UCI,VOLUME SET: VAH,ROU//<br /> |
| − | The value of PRODUCTION will be used in the GETENV api.<br /> | + | The value of PRODUCTION will be used in the GETENV api.<br /> |
| − | PRODUCTION (SIGN-ON) UCI,VOLUME SET: VAH,ROU//<br /> | + | PRODUCTION (SIGN-ON) UCI,VOLUME SET: VAH,ROU//<br /> |
| − | The VOLUME name must match the one in PRODUCTION.<br /> | + | The VOLUME name must match the one in PRODUCTION.<br /> |
| − | NAME OF VOLUME SET: ROU//<br /> | + | NAME OF VOLUME SET: ROU//<br /> |
| − | The temp directory for the system: '/tmp/'//<br /> | + | The temp directory for the system: '/tmp/'//<br /> |
| − | ^%ZOSF setup<br /> | + | ^%ZOSF setup<br /> |
| − | <br /> | + | <br /> |
| − | <br /> | + | <br /> |
| − | Now to load routines common to all systems.<br /> | + | Now to load routines common to all systems.<br /> |
| − | Routine: ZTLOAD Loaded, Saved as %ZTLOAD<br /> | + | Routine: ZTLOAD Loaded, Saved as %ZTLOAD<br /> |
| − | Routine: ZTLOAD1 Loaded, Saved as %ZTLOAD1<br /> | + | Routine: ZTLOAD1 Loaded, Saved as %ZTLOAD1<br /> |
| − | Routine: ZTLOAD2 Loaded, Saved as %ZTLOAD2<br /> | + | Routine: ZTLOAD2 Loaded, Saved as %ZTLOAD2<br /> |
| − | Routine: ZTLOAD3 Loaded, Saved as %ZTLOAD3<br /> | + | Routine: ZTLOAD3 Loaded, Saved as %ZTLOAD3<br /> |
| − | Routine: ZTLOAD4 Loaded, Saved as %ZTLOAD4<br /> | + | Routine: ZTLOAD4 Loaded, Saved as %ZTLOAD4<br /> |
| − | Routine: ZTLOAD5 Loaded, Saved as %ZTLOAD5<br /> | + | Routine: ZTLOAD5 Loaded, Saved as %ZTLOAD5<br /> |
| − | Routine: ZTLOAD6 Loaded, Saved as %ZTLOAD6<br /> | + | Routine: ZTLOAD6 Loaded, Saved as %ZTLOAD6<br /> |
| − | Routine: ZTLOAD7 Loaded, Saved as %ZTLOAD7<br /> | + | Routine: ZTLOAD7 Loaded, Saved as %ZTLOAD7<br /> |
| − | Routine: ZTM Loaded, Saved as %ZTM<br /> | + | Routine: ZTM Loaded, Saved as %ZTM<br /> |
| − | Routine: ZTM0 Loaded, Saved as %ZTM0<br /> | + | Routine: ZTM0 Loaded, Saved as %ZTM0<br /> |
| − | Routine: ZTM1 Loaded, Saved as %ZTM1<br /> | + | Routine: ZTM1 Loaded, Saved as %ZTM1<br /> |
| − | Routine: ZTM2 Loaded, Saved as %ZTM2<br /> | + | Routine: ZTM2 Loaded, Saved as %ZTM2<br /> |
| − | Routine: ZTM3 Loaded, Saved as %ZTM3<br /> | + | Routine: ZTM3 Loaded, Saved as %ZTM3<br /> |
| − | Routine: ZTM4 Loaded, Saved as %ZTM4<br /> | + | Routine: ZTM4 Loaded, Saved as %ZTM4<br /> |
| − | Routine: ZTM5 Loaded, Saved as %ZTM5<br /> | + | Routine: ZTM5 Loaded, Saved as %ZTM5<br /> |
| − | Routine: ZTM6 Loaded, Saved as %ZTM6<br /> | + | Routine: ZTM6 Loaded, Saved as %ZTM6<br /> |
| − | Routine: ZTMS Loaded, Saved as %ZTMS<br /> | + | Routine: ZTMS Loaded, Saved as %ZTMS<br /> |
| − | Routine: ZTMS0 Loaded, Saved as %ZTMS0<br /> | + | Routine: ZTMS0 Loaded, Saved as %ZTMS0<br /> |
| − | Routine: ZTMS1 Loaded, Saved as %ZTMS1<br /> | + | Routine: ZTMS1 Loaded, Saved as %ZTMS1<br /> |
| − | Routine: ZTMS2 Loaded, Saved as %ZTMS2<br /> | + | Routine: ZTMS2 Loaded, Saved as %ZTMS2<br /> |
| − | Routine: ZTMS3 Loaded, Saved as %ZTMS3<br /> | + | Routine: ZTMS3 Loaded, Saved as %ZTMS3<br /> |
| − | Routine: ZTMS4 Loaded, Saved as %ZTMS4<br /> | + | Routine: ZTMS4 Loaded, Saved as %ZTMS4<br /> |
| − | Routine: ZTMS5 Loaded, Saved as %ZTMS5<br /> | + | Routine: ZTMS5 Loaded, Saved as %ZTMS5<br /> |
| − | Routine: ZTMS7 Loaded, Saved as %ZTMS7<br /> | + | Routine: ZTMS7 Loaded, Saved as %ZTMS7<br /> |
| − | Routine: ZTMSH Loaded, Saved as %ZTMSH<br /> | + | Routine: ZTMSH Loaded, Saved as %ZTMSH<br /> |
| − | Routine: ZTER Loaded, Saved as %ZTER<br /> | + | Routine: ZTER Loaded, Saved as %ZTER<br /> |
| − | Routine: ZTER1 Loaded, Saved as %ZTER1<br /> | + | Routine: ZTER1 Loaded, Saved as %ZTER1<br /> |
| − | Routine: ZIS Loaded, Saved as %ZIS<br /> | + | Routine: ZIS Loaded, Saved as %ZIS<br /> |
| − | Routine: ZIS1 Loaded, Saved as %ZIS1<br /> | + | Routine: ZIS1 Loaded, Saved as %ZIS1<br /> |
| − | Routine: ZIS2 Loaded, Saved as %ZIS2<br /> | + | Routine: ZIS2 Loaded, Saved as %ZIS2<br /> |
| − | Routine: ZIS3 Loaded, Saved as %ZIS3<br /> | + | Routine: ZIS3 Loaded, Saved as %ZIS3<br /> |
| − | Routine: ZIS5 Loaded, Saved as %ZIS5<br /> | + | Routine: ZIS5 Loaded, Saved as %ZIS5<br /> |
| − | Routine: ZIS6 Loaded, Saved as %ZIS6<br /> | + | Routine: ZIS6 Loaded, Saved as %ZIS6<br /> |
| − | Routine: ZIS7 Loaded, Saved as %ZIS7<br /> | + | Routine: ZIS7 Loaded, Saved as %ZIS7<br /> |
| − | Routine: ZISC Loaded, Saved as %ZISC<br /> | + | Routine: ZISC Loaded, Saved as %ZISC<br /> |
| − | Routine: ZISP Loaded, Saved as %ZISP<br /> | + | Routine: ZISP Loaded, Saved as %ZISP<br /> |
| − | Routine: ZISS Loaded, Saved as %ZISS<br /> | + | Routine: ZISS Loaded, Saved as %ZISS<br /> |
| − | Routine: ZISS1 Loaded, Saved as %ZISS1<br /> | + | Routine: ZISS1 Loaded, Saved as %ZISS1<br /> |
| − | Routine: ZISS2 Loaded, Saved as %ZISS2<br /> | + | Routine: ZISS2 Loaded, Saved as %ZISS2<br /> |
| − | Routine: ZISTCP Loaded, Saved as %ZISTCP<br /> | + | Routine: ZISTCP Loaded, Saved as %ZISTCP<br /> |
| − | Routine: ZISUTL Loaded, Saved as %ZISUTL<br /> | + | Routine: ZISUTL Loaded, Saved as %ZISUTL<br /> |
| − | Routine: ZTPP Loaded, Saved as %ZTPP<br /> | + | Routine: ZTPP Loaded, Saved as %ZTPP<br /> |
| − | Routine: ZTP1 Loaded, Saved as %ZTP1<br /> | + | Routine: ZTP1 Loaded, Saved as %ZTP1<br /> |
| − | Routine: ZTPTCH Loaded, Saved as %ZTPTCH<br /> | + | Routine: ZTPTCH Loaded, Saved as %ZTPTCH<br /> |
| − | Routine: ZTRDEL Loaded, Saved as %ZTRDEL<br /> | + | Routine: ZTRDEL Loaded, Saved as %ZTRDEL<br /> |
| − | Routine: ZTMOVE Loaded, Saved as %ZTMOVE<br /> | + | Routine: ZTMOVE Loaded, Saved as %ZTMOVE<br /> |
| − | Want to rename the FileMan routines: No//Y<br /> | + | Want to rename the FileMan routines: No//Y<br /> |
| − | Routine: DIDT Loaded, Saved as %DT<br /> | + | Routine: DIDT Loaded, Saved as %DT<br /> |
| − | Routine: DIDTC Loaded, Saved as %DTC<br /> | + | Routine: DIDTC Loaded, Saved as %DTC<br /> |
| − | Routine: DIRCR Loaded, Saved as %RCR<br /> | + | Routine: DIRCR Loaded, Saved as %RCR<br /> |
| − | Setting ^%ZIS('C')<br /> | + | Setting ^%ZIS('C')<br /> |
| − | + | ||
| − | Now, I will check your % globals........... | + | Now, I will check your % globals........... |
| − | ALL DONE<br /> | + | ALL DONE<br /> |
| − | GTM><br /> | + | GTM><br /> |
== Initialize FileMan to set the site name and number. == | == Initialize FileMan to set the site name and number. == | ||
| Line 137: | Line 141: | ||
You can run D ^DINIT again to see if you changes were successful and choose<br /> GT.M when offered a choice of MUMPS system you are using.<br /> | You can run D ^DINIT again to see if you changes were successful and choose<br /> GT.M when offered a choice of MUMPS system you are using.<br /> | ||
<br /> | <br /> | ||
| − | GTM>'''D ^DINIT'''<br /> | + | GTM>'''D ^DINIT'''<br /> |
| − | <br /> | + | <br /> |
| − | + | ||
| − | VA FileMan V.22.0<br /><br /> | + | VA FileMan V.22.0<br /><br /> |
| − | + | ||
| − | + | ||
| − | Initialize VA FileMan now? NO//'''YES'''<br /><br /> | + | Initialize VA FileMan now? NO//'''YES'''<br /><br /> |
| − | + | ||
| − | SITE NAME: OSWIZARDS VISTA//'''BONEZ OSWIZARDS VISTA'''<br /> | + | SITE NAME: OSWIZARDS VISTA//'''BONEZ OSWIZARDS VISTA'''<br /> |
| − | <br /> | + | <br /> |
| − | SITE NUMBER: 1234//'''1234'''..........................<br /> | + | SITE NUMBER: 1234//'''1234'''..........................<br /> |
| − | <br /> | + | <br /> |
| − | Now loading MUMPS Operating System File....<br /> | + | Now loading MUMPS Operating System File....<br /> |
| − | <br /> | + | <br /> |
| − | Now loading DIALOG and LANGUAGE<br /> Files........................................... | + | Now loading DIALOG and LANGUAGE<br /> Files........................................... |
| − | ...............<br /> | + | ...............<br /> |
| − | <br /> | + | <br /> |
| − | + | ||
| − | TYPE OF MUMPS SYSTEM YOU ARE USING: GT.M(UNIX)//<br /> | + | TYPE OF MUMPS SYSTEM YOU ARE USING: GT.M(UNIX)//<br /> |
| − | + | ||
| − | Now loading other FileMan files--please<br /> wait.................................... | + | Now loading other FileMan files--please<br /> wait.................................... |
| − | ................................................................................ | + | ................................................................................ |
| − | ................................................................................ | + | ................................................................................ |
| − | ............. | + | ............. |
| − | .......... | + | .......... |
| − | + | ||
| − | The following files have been installed:<br /> | + | The following files have been installed:<br /> |
.11 INDEX<br /> | .11 INDEX<br /> | ||
.2 DESTINATION<br /> | .2 DESTINATION<br /> | ||
| Line 200: | Line 204: | ||
1.52191 SQLI_ERROR_TEXT<br /> | 1.52191 SQLI_ERROR_TEXT<br /> | ||
1.52192 SQLI_ERROR_LOG<br /> | 1.52192 SQLI_ERROR_LOG<br /> | ||
| − | + | ||
| − | + | Re-indexing entries in the DIALOG file.....................<br /> | |
| − | Re-indexing entries in the DIALOG file.....................<br /> | + | |
| − | + | Compiling all forms ...<br /> | |
| − | Compiling all forms ...<br /> | + | |
| − | |||
DICATT (#.001)<br /> | DICATT (#.001)<br /> | ||
DIPTED (#.1001)<br /> | DIPTED (#.1001)<br /> | ||
| Line 333: | Line 336: | ||
BPS BPSOSPW (#102)<br /> | BPS BPSOSPW (#102)<br /> | ||
BPS INPUT 1 (#103)<br /> | BPS INPUT 1 (#103)<br /> | ||
| − | <br /> | + | <br /> |
| − | <br /> | + | <br /> |
| − | INITIALIZATION COMPLETED IN 13 SECONDS.<br /> | + | INITIALIZATION COMPLETED IN 13 SECONDS.<br /> |
| − | + | ||
| − | ------------------------- | + | ------------------------- |
== Determine the "BOX:VOLUME pair" for the machine. == | == Determine the "BOX:VOLUME pair" for the machine. == | ||
| Line 343: | Line 346: | ||
<br /> | <br /> | ||
| − | GTM>'''D GETENV^%ZOSV W Y''' | + | GTM>'''D GETENV^%ZOSV W Y''' |
| − | VAH^ROU^bonez^ROU:bonez | + | VAH^ROU^bonez^ROU:bonez |
| − | GTM | + | GTM> |
<br /> | <br /> | ||
The BOX:VOLUME pair for this machine is ROU:bonez<br /> | The BOX:VOLUME pair for this machine is ROU:bonez<br /> | ||
<br /> | <br /> | ||
UCI^VOL^NODE^BOX:VOLUME<br /> | UCI^VOL^NODE^BOX:VOLUME<br /> | ||
| + | VAH^ROU^bonez^ROU:bonez<br/> | ||
<br /> | <br /> | ||
UCI = VAH<br /> | UCI = VAH<br /> | ||
| Line 1,572: | Line 1,576: | ||
mupip rundown -r "*" | mupip rundown -r "*" | ||
-------------------- | -------------------- | ||
| + | |||
| + | [[Adding Users]] | ||
Latest revision as of 21:44, 6 August 2022
- Editor's note: This page was written in 2005. The settings it recommends seem to apply to FOIA VistA, and may not be appropriate for the newer versions of VistA such as WorldVistaEhr VOE, OpenVistA, or Astronaut. However, it is still a valuable reference for how to find and use the various configuration menus.
Vista Configuration on Linux running GT.M
Mark Street
Emulated from Nancy Anthracite's Vista Configuration HOWTO on hardhats.org
The BOLD entries represent user supplied input during the configuration process.
VistA's output is supplied in this guide so the user can follow along step by step as the configuration proceeds.
As a general rule user input is placed after the double slash at the VistA prompt.
Ex. Should I continue anyway? N//
no would be the default
If you would like to change the default value you must supply a Y or YES after the //.
Since this is a very long document I have created shorter documents that you can follow in order to a conclusion if you wish.
- Setting Mumps Routines
- Configuring A Domain
- Configuring An Institution and Facility
- Configuring An Administrator User
- Configuring Administration Menus and Devices
- Configuring Taskman, Mailman and RPC Broker
- Configuring CPRS Keys and Tabs
Contents
- 1 Let's begin configuration of VistA.
- 2 Initialize FileMan to set the site name and number.
- 3 Determine the "BOX:VOLUME pair" for the machine.
- 4 Create the domain.
- 5 Now to complete the DOMAIN set up by Christening the new domain.
- 6 Determine the internal entry of the new domain.
- 7 Adjust system files to new domain
- 8 Determine proper value for BOX-VOLUME PAIR
- 9 Update the RPC BROKER SITE PARAMETER File.
- 10 Setup a System Administrator Account
- 11 Determine System Administrator account number
- 12 Assign keys to System Administrator Account
- 13 Setup VistA Application Software Parameters
- 14 Add a Medical Center Division.
- 15 Enter additional information for the System Administrator user
- 16 Set Up Menus for the System Manager
- 17 Add the XMUSER Menu to Mailman Menu.
- 18 Change the default time before users are automatically signed off
- 19 Update the Devices, Start Taskman and Mail a Message
- 20 Check TaskMan's environement
- 21 Start TaskMan
- 22 Send a Message
- 23 Check Mail
- 24 Start and Test RPC Broker
- 25 Overview of starting and stopping components
Let's begin configuration of VistA.
From the vista user's login prompt type the gtm command.
[vista@localhost]$ gtm
ZTMGRSET - Define the Vista global variables and save the system M routines for your operating system.
GTM>D ^ZTMGRSET
ZTMGRSET Version 8.0 **34,36,69,94,121,127,136,191,275**
HELLO! I exist to assist you in correctly initializing the current account.
THIS MAY NOT BE THE MANAGER UCI.
I think it is VAH,ROU. Should I continue anyway? N//Y
I think you are using GT.M (Unix)
Which MUMPS system should I install?
1 = VAX DSM(V6), VAX DSM(V7)
2 = MSM-PC/PLUS, MSM for NT or UNIX
3 = OpenM for NT, Cache/NT, Cache/VMS
4 = Datatree, DTM-PC, DT-MAX
5 = MVX,ISM VAX
6 = ISM (UNIX, Open VMS)
7 = GT.M (VMS)
8 = GT.M (Unix)
System: 8//8
I will now rename a group of routines specific to your operating system. Routine: ZOSVGUX Loaded, Saved as %ZOSV
Routine: ZTBKCGUX Missing
Routine: ZIS4GTM Loaded, Saved as %ZIS4
Routine: ZISFGUX Missing
Routine: ZISHGUX Loaded, Saved as %ZISH
Routine: XUCIGTM Loaded, Saved as %XUCI
Routine: ZISETGUX Missing
Routine: ZOSV2GTM Loaded, Saved as %ZOSV2
Routine: ZISTCPS Loaded, Saved as %ZISTCPS
NAME OF MANAGER'S UCI,VOLUME SET: VAH,ROU//
The value of PRODUCTION will be used in the GETENV api.
PRODUCTION (SIGN-ON) UCI,VOLUME SET: VAH,ROU//
The VOLUME name must match the one in PRODUCTION.
NAME OF VOLUME SET: ROU//
The temp directory for the system: '/tmp/'//
^%ZOSF setup
Now to load routines common to all systems.
Routine: ZTLOAD Loaded, Saved as %ZTLOAD
Routine: ZTLOAD1 Loaded, Saved as %ZTLOAD1
Routine: ZTLOAD2 Loaded, Saved as %ZTLOAD2
Routine: ZTLOAD3 Loaded, Saved as %ZTLOAD3
Routine: ZTLOAD4 Loaded, Saved as %ZTLOAD4
Routine: ZTLOAD5 Loaded, Saved as %ZTLOAD5
Routine: ZTLOAD6 Loaded, Saved as %ZTLOAD6
Routine: ZTLOAD7 Loaded, Saved as %ZTLOAD7
Routine: ZTM Loaded, Saved as %ZTM
Routine: ZTM0 Loaded, Saved as %ZTM0
Routine: ZTM1 Loaded, Saved as %ZTM1
Routine: ZTM2 Loaded, Saved as %ZTM2
Routine: ZTM3 Loaded, Saved as %ZTM3
Routine: ZTM4 Loaded, Saved as %ZTM4
Routine: ZTM5 Loaded, Saved as %ZTM5
Routine: ZTM6 Loaded, Saved as %ZTM6
Routine: ZTMS Loaded, Saved as %ZTMS
Routine: ZTMS0 Loaded, Saved as %ZTMS0
Routine: ZTMS1 Loaded, Saved as %ZTMS1
Routine: ZTMS2 Loaded, Saved as %ZTMS2
Routine: ZTMS3 Loaded, Saved as %ZTMS3
Routine: ZTMS4 Loaded, Saved as %ZTMS4
Routine: ZTMS5 Loaded, Saved as %ZTMS5
Routine: ZTMS7 Loaded, Saved as %ZTMS7
Routine: ZTMSH Loaded, Saved as %ZTMSH
Routine: ZTER Loaded, Saved as %ZTER
Routine: ZTER1 Loaded, Saved as %ZTER1
Routine: ZIS Loaded, Saved as %ZIS
Routine: ZIS1 Loaded, Saved as %ZIS1
Routine: ZIS2 Loaded, Saved as %ZIS2
Routine: ZIS3 Loaded, Saved as %ZIS3
Routine: ZIS5 Loaded, Saved as %ZIS5
Routine: ZIS6 Loaded, Saved as %ZIS6
Routine: ZIS7 Loaded, Saved as %ZIS7
Routine: ZISC Loaded, Saved as %ZISC
Routine: ZISP Loaded, Saved as %ZISP
Routine: ZISS Loaded, Saved as %ZISS
Routine: ZISS1 Loaded, Saved as %ZISS1
Routine: ZISS2 Loaded, Saved as %ZISS2
Routine: ZISTCP Loaded, Saved as %ZISTCP
Routine: ZISUTL Loaded, Saved as %ZISUTL
Routine: ZTPP Loaded, Saved as %ZTPP
Routine: ZTP1 Loaded, Saved as %ZTP1
Routine: ZTPTCH Loaded, Saved as %ZTPTCH
Routine: ZTRDEL Loaded, Saved as %ZTRDEL
Routine: ZTMOVE Loaded, Saved as %ZTMOVE
Want to rename the FileMan routines: No//Y
Routine: DIDT Loaded, Saved as %DT
Routine: DIDTC Loaded, Saved as %DTC
Routine: DIRCR Loaded, Saved as %RCR
Setting ^%ZIS('C')
Now, I will check your % globals........... ALL DONE
GTM>
Initialize FileMan to set the site name and number.
GTM>D ^DINIT
Give the site a site name and 4 digit site number.
You can run D ^DINIT again to see if you changes were successful and choose
GT.M when offered a choice of MUMPS system you are using.
GTM>D ^DINIT
VA FileMan V.22.0
Initialize VA FileMan now? NO//YES
SITE NAME: OSWIZARDS VISTA//BONEZ OSWIZARDS VISTA
SITE NUMBER: 1234//1234..........................
Now loading MUMPS Operating System File....
Now loading DIALOG and LANGUAGE
Files........................................... ...............
TYPE OF MUMPS SYSTEM YOU ARE USING: GT.M(UNIX)//
Now loading other FileMan files--please
wait.................................... ................................................................................ ................................................................................ ............. .......... The following files have been installed:
.11 INDEX
.2 DESTINATION
.31 KEY
.4 PRINT TEMPLATE
.401 SORT TEMPLATE
.402 INPUT TEMPLATE
.403 FORM
.404 BLOCK
.44 FOREIGN FORMAT
.46 IMPORT TEMPLATE
.5 FUNCTION
.6 DD AUDIT
.7 MUMPS OPERATING SYSTEM
.81 DATA TYPE
.83 COMPILED ROUTINE
.84 DIALOG
.85 LANGUAGE
1 FILE
1.1 AUDIT
1.11 ARCHIVAL ACTIVITY
1.12 FILEGRAM HISTORY
1.13 FILEGRAM ERROR LOG
1.2 ALTERNATE EDITOR
1.521 SQLI_SCHEMA
1.52101 SQLI_KEY_WORD
1.5211 SQLI_DATA_TYPE
1.5212 SQLI_DOMAIN
1.5213 SQLI_KEY_FORMAT
1.5214 SQLI_OUTPUT_FORMAT
1.5215 SQLI_TABLE
1.5216 SQLI_TABLE_ELEMENT
1.5217 SQLI_COLUMN
1.5218 SQLI_PRIMARY_KEY
1.5219 SQLI_FOREIGN_KEY
1.52191 SQLI_ERROR_TEXT
1.52192 SQLI_ERROR_LOG
Re-indexing entries in the DIALOG file.....................
Compiling all forms ...
DICATT (#.001)
DIPTED (#.1001)
DIKC EDIT (#.1101)
DIKC EDIT UI (#.1102)
DIKK EDIT (#.3101)
DIBTED (#.40001)
DIETED (#.40101)
DIEDIT (#.40201)
DDGF BLOCK EDIT (#.40301)
DDGF PAGE ADD (#.40302)
DDGF PAGE EDIT (#.40303)
DDGF PAGE SELECT (#.40304)
DDGF FORM EDIT (#.40305)
DDGF HEADER BLOCK EDIT (#.40306)
DDGF FIELD ADD (#.40401)
DDGF FIELD CAPTION ONLY (#.40402)
DDGF FIELD DD (#.40403)
DDGF FIELD FORM ONLY (#.40404)
DDGF FIELD COMPUTED (#.40405)
DDGF BLOCK ADD (#.40406)
DDGF BLOCK DELETE (#.40407)
DDGF HEADER BLOCK SELECT (#.40408)
DDXP FF FORM1 (#.441)
DDMP SPECIFY IMPORT (#.461)
XPD EDIT BUILD (#1)
XUEDIT CHARACTERISTICS (#2)
XUEXISTING USER (#3)
XUDEVICE MT (#4)
XUDEVICE SDP (#5)
XUDEVICE SPL (#6)
XUDEVICE HFS (#7)
XUDEVICE CHAN (#8)
XU OPTION SCHEDULE (#9)
XUSERDEACT (#10)
XUTM UCI ASSOC (#11)
XUSITEPARM (#12)
XUAUDIT (#13)
XUREACT USER (#14)
PRSA TD EDIT (#15)
PRSA OT REQ (#16)
PRSA TD DISP (#17)
PRSA TL EDIT (#18)
PRSA TL DISP (#19)
PRSA LV REQ (#20)
PRSA ED REQ (#21)
PRSA VC POST (#22)
PRSA PM POST (#23)
PRSA TD TL (#24)
PRSA TP POST1 (#25)
PRSA TE EDIT (#26)
PRSA FEE POST (#27)
NURA-I-SERVICE (#28)
XU-PERSON CLASS (#29)
XUNEW USER (#30)
SPNLPFM1 (#31)
SPNFFRM1 (#32)
SPNFFRM2 (#33)
SPNLPFM2 (#34)
XPD EDIT MP (#35)
XPD EDIT GP (#36)
PRCHQ1 (#37)
PRCHQ2 (#38)
PRCHQ3 (#39)
PRCHQ4 (#40)
PRCHQ5 (#41)
SPNLP FUN MES (#42)
SPNLP FIM FM1 (#43)
SPNLP CHART FM1 (#44)
SPNLP MS FM1 (#45)
SPNE ENTER/EDIT SYNONYM (#46)
LREPI (#47)
ENPR MS (#48)
ENPR ALL (#49)
ENPR PRELIM (#50)
ENPR AE (#51)
ENPR CO (#52)
ENPR CHG (#53)
ABSV ADD/EDIT MASTER (#54)
XQEDTOPT (#55)
XU-INST-EDIT (#56)
LREPIPROT (#57)
XUTMKE ADD (#58)
WV PROC-FORM-1 (#59)
WV NOTIF-FORM-1 (#60)
WV PATIENT-FORM-1 (#61)
WV NOTIF-FORM-2 (#62)
WV PROC-FORM-2-COLP (#63)
WV NOTIFPURPOSE-FORM-1 (#64)
WV SITE PARAMS-FORM-1 (#65)
WV REFUSED PROCEDURE-ENTRY (#66)
WV PROC-FORM-LAB (#67)
XDR RESFILE FORM (#68)
HL SITE PARAMETERS (#69)
PSB PRN EFFECTIVENESS (#70)
PSB MED LOG EDIT (#71)
PSBO DL (#72)
PSBO WA (#73)
PSBO ML (#74)
PSBO MM (#75)
PSBO PE (#76)
PSB MISSING DOSE REQUEST (#77)
PSBO MH (#78)
PSBO MV (#79)
PSB MISSING DOSE FOLLOWUP (#80)
PSBO BL (#81)
PSBO MD (#82)
PSB NEW UD ENTRY (#83)
PSB NEW IV ENTRY (#84)
HL7 APP (#85)
HL7 LOGICAL LINK (#86)
HL7 INTERFACE (#87)
SPNLP ASIA MES (#88)
PSB MED LOG EDIT IV (#89)
SPNLP FAM FM1 (#90)
SPNLP DIENER FM1 (#91)
SPNLP DUSOI FM1 (#92)
XU-CLINICAL TRAINEE (#93)
XUSSPKI (#94)
INSTITUTION EDIT (#95)
PRSA LD POST (#96)
XUDEVICE LPD (#97)
XUDEVICE TRM (#98)
KMPD PARAMETERS EDIT (#99)
LREPI9 (#100)
BPS EOB TO BATCH (#101)
BPS BPSOSPW (#102)
BPS INPUT 1 (#103)
INITIALIZATION COMPLETED IN 13 SECONDS.
-------------------------
Determine the "BOX:VOLUME pair" for the machine.
GTM>D GETENV^%ZOSV W Y VAH^ROU^bonez^ROU:bonez GTM>
The BOX:VOLUME pair for this machine is ROU:bonez
UCI^VOL^NODE^BOX:VOLUME
VAH^ROU^bonez^ROU:bonez
UCI = VAH
VOL = ROU
NODE = bonez
BOX = ROU
VOLUME = bonez
Create the domain.
From the GTM prompt, start VA FileMan by typing "D Q^DI". At the Select OPTION: prompt. Type "1". (You can see why you typed 1 if you type "??" at the option prompt.
NB: If you are prompted for an ACCESS CODE, press ENTER until you get back to a simple prompt and enter "S DUZ=1" before running "D Q^DI".
That will give you the list of options you can choose from and 1 is ENTER OR EDIT FILE ENTRIES.) At INPUT TO WHAT FILE: type "DOMAIN" and accept the ALL// default to EDIT WHICH FIELD. At Select DOMAIN NAME: enter a local domain name. Substitute an appropriate value for VISTA.MYDOMAIN.COM in the example below.
GTM>D Q^DI
VA FileMan 22.0
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: DEVICE//DOMAIN (18 entries)
EDIT WHICH FIELD: ALL//
Select DOMAIN NAME:?
Answer with DOMAIN NAME, or TCP/IP POLL FLAG, or SYNONYM
Do you want the entire 18-Entry DOMAIN List?Y (Yes)
Choose from:
BONEZ.STREETCHIRO.COM
EPHARMACY.VITRIA-EDI.AAC.VA.GO
FHIE.MED.VA.GOV
FORUM.VA.GOV
GOV
MAIL.CIO.MED.VA.GOV
MPIDC-AUSTIN.MED.VA.GOV
Q-CLU.MED.VA.GOV
Q-CLW.MED.VA.GOV
Q-NPC.MED.VA.GOV
Q-NPP.MED.VA.GOV
Q-NPQ.MED.VA.GOV
Q-PSS.MED.VA.GOV
Q-SCD.MED.VA.GOV
TPB-AUSTIN.MED.VA.GOV
VISTA.MED.VA.GOV
VISTA.PLATINUM.MED.VA.GOV
VISTA.STREETCHIRO.COM
You may enter a new DOMAIN, if you wish
Answer must be 1-64 characters in length.
Select DOMAIN NAME:BONEZ.OSWIZARDS.COM
Are you adding 'BONEZ.OSWIZARDS.COM' as a new DOMAIN (the 19TH)? No//Y
(Yes)
FLAGS:^
Now to complete the DOMAIN set up by Christening the new domain.
Go back to the VISTA> prompt and type "D CHRISTEN^XMUDCHR".
GTM>D CHRISTEN^XMUDCHR
- * * * WARNING * * * *
You are about to change the domain name of this facility
in the MailMan Site Parameters file.
Currently, this facility is named: BONEZ.STREETCHIRO.COM
You must be extremely sure before you proceed!
Are you sure you want to change the name of this facility? NO// YES
Select DOMAIN NAME: BONEZ.STREETCHIRO.COM//BONEZ
1 BONEZ.OSWIZARDS.COM
2 BONEZ.STREETCHIRO.COM
CHOOSE 1-2: 1 BONEZ.OSWIZARDS.COM
The domain name for this facility is now: BONEZ.OSWIZARDS.COM
PARENT: VISTA.STREETCHIRO.COM//
TIME ZONE: PDT//PST PACIFIC STANDARD
VISTA.STREETCHIRO.COM has been initialized as your 'parent' domain.
(Forum is usually the parent domain, unless this is a subordinate domain.)
You may edit the MailMan Site Parameter file to change your parent domain.
We will not initialize your transmission scripts.
Use the 'Subroutine editor' option under network management menu to add your
site passwords to the MINIENGINE script, and the 'Edit a script' option
to edit any domain scripts that you choose to.
GTM>
Determine the internal entry of the new domain.
Remember this number as it will be used in subsequent steps.
Get back to the Select OPTION: prompt and enter "INQUIRE" or "5" (once again, you can type ?? to see the available options and 5 is INQUIRE TO FILE ENTRIES) then at the Select DOMAIN NAME: prompt, enter the new domain name you just created. Answer "N" to STANDARD CAPTIONED OUTPUT and at PRINT FIELD: answer "NUMBER". The domain number is "printed" to the screen.
GTM>D Q^DI
VA FileMan 22.0
Select OPTION: 5 INQUIRE TO FILE ENTRIES
OUTPUT FROM WHAT FILE: DOMAIN//
Select DOMAIN NAME:BONEZ
1 BONEZ.OSWIZARDS.COM
2 BONEZ.STREETCHIRO.COM
CHOOSE 1-2:1 BONEZ.OSWIZARDS.COM
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number
(IEN)
NUMBER: 22 NAME: BONEZ.OSWIZARDS.COM
LEVEL 1 NAME (c): COM LEVEL 2 NAME (c): OSWIZARDS.COM
LEVEL 3 NAME (c): BONEZ.OSWIZARDS.COM
LEVEL 4 NAME (c): BONEZ.OSWIZARDS.COM
Select DOMAIN NAME:
See, my number for the domain is 22 in this instance.
Adjust system files to new domain
From the GTM prompt repoint the KERNEL SYSTEM PARAMETERS and RPC BROKER PARAMETERS files to the new domain, go back to the GTM> prompt and enter 'S $P(^XTV(8989.3,1,0),"^")=3' and 'S $P(^XWB(8994.1,1,0),"^")=3' where 3 is the internal number of the new domain we just created in the previous step.
The domain instance of 22 is used below. I have NO idea what this command mean. I only know that it resets the kernel parameters and RPC broker parameters to my domain defined above.
GTM>S $P(^XTV(8989.3,1,0),"^")=22
GTM>S $P(^XWB(8994.1,1,0),"^")=22
GTM>
Then from the GTM> prompt again start FileMan with "D Q^DI". At Select OPTION: enter "6" (UTILITY FUNCTIONS) then select RE-INDEX FILE. At MODIFY WHAT FILE, enter "KERNEL SYSTEM PARAMETERS". Then do the same for the RPC BROKER PARAMETERS file. See example below for the rest of the dialogue.
GTM>D Q^DI
VA FileMan 22.0
Select OPTION: UTILITY FUNCTIONS
Select UTILITY OPTION: RE-INDEX FILE
MODIFY WHAT FILE: KERNEL SYSTEM PARAMETERS//
THERE ARE 13 INDICES WITHIN THIS FILE
DO YOU WISH TO RE-CROSS-REFERENCE ONE PARTICULAR INDEX? No// NO (No)
OK, ARE YOU SURE YOU WANT TO KILL OFF THE EXISTING 13 INDICES? No// YES (Yes)
DO YOU THEN WANT TO 'RE-CROSS-REFERENCE'? Yes// (Yes)
...SORRY, LET ME THINK ABOUT THAT A MOMENT...
FILE WILL NOW BE 'RE-CROSS-REFERENCED'................
Select UTILITY OPTION:
Select UTILITY OPTION: RE-INDEX FILE
MODIFY WHAT FILE: KERNEL SYSTEM PARAMETERS// RPC BROKER SITE PARAMETERS
(1 entry)
THERE ARE 5 INDICES WITHIN THIS FILE
DO YOU WISH TO RE-CROSS-REFERENCE ONE PARTICULAR INDEX? No// (No)
OK, ARE YOU SURE YOU WANT TO KILL OFF THE EXISTING 5 INDICES? No// YES (Yes)
DO YOU THEN WANT TO 'RE-CROSS-REFERENCE'? Yes// (Yes)
...SORRY, THIS MAY TAKE A FEW MOMENTS...
FILE WILL NOW BE 'RE-CROSS-REFERENCED'......
Select UTILITY OPTION:
Check the VOLUME SET File. The VOLUME SET File should not need any changes. At Select OPTION: enter "1" for EDIT OR ENTER FILE ENTRIES. The choice should be INPUT TO WHAT FILE: SOME OTHER CHOICE//VOLUME SET EDIT WHICH FIELD: ALL// At Select VOLUME SET prompt type "??" to see a list of entries. When asked which volume set again, type in whatever it is.
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: RPC BROKER SITE PARAMETERS// VOLUME SET
(1 entry)
EDIT WHICH FIELD: ALL//
Select VOLUME SET: ??
ROU
You may enter a new VOLUME SET, if you wish
Answer should be the name of a volume set.
When each cpu can have only one volume set, this is also the cpu name.
Answer will be used in extended global references to reach this volume.
Select VOLUME SET: ROU
VOLUME SET: ROU//
TYPE: GENERAL PURPOSE VOLUME SET//
INHIBIT LOGONS?: NO//
LINK ACCESS?: YES//
OUT OF SERVICE?: NO//
REQUIRED VOLUME SET?: NO//
TASKMAN FILES UCI: ROU//
TASKMAN FILES VOLUME SET: ROU//
REPLACEMENT VOLUME SET:
DAYS TO KEEP OLD TASKS: 4//
SIGNON/PRODUCTION VOLUME SET: Yes//
Select VOLUME SET:
Determine proper value for BOX-VOLUME PAIR
This step is to get the proper value for the BOX-VOLUME PAIR in the TASKMAN SITE PARAMETERS File. Edit the TASKMAN SITE PARAMETER File (# 14.7) to update the BOX-VOLUME PAIR. Note that when you enter a "?" at the BOX-VOLUME PAIR prompt, it tells you what the correct value should be.
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: VOLUME SET// TASKMAN SITE PARAMETERS
(1 entry)
EDIT WHICH FIELD: ALL//
Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ?
Answer with TASKMAN SITE PARAMETERS BOX-VOLUME PAIR:
ROU:bonez
You may enter a new TASKMAN SITE PARAMETERS, if you wish
Answer must be 3-30 characters in length.
The value for the current account is ROU:bonez
Select TASKMAN SITE PARAMETERS BOX-VOLUME PAIR: ROU:bonez
BOX-VOLUME PAIR: ROU:bonez//
RESERVED: ^
Update the RPC BROKER SITE PARAMETER File.
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: TASKMAN SITE PARAMETERS// RPC BROKER SITE PARAMETERS
(1 entry)
EDIT WHICH FIELD: ALL//
Select RPC BROKER SITE PARAMETERS DOMAIN NAME: BONEZ.OSWIZARDS.COM
...OK? Yes// YES (Yes)
DOMAIN NAME: BONEZ.OSWIZARDS.COM//
MAIL GROUP FOR ALERTS:
Select BOX-VOLUME PAIR: ROU:bonez//
BOX-VOLUME PAIR: ROU:bonez//
Select PORT: 9200//
PORT: 9200//
TYPE OF LISTENER: Original//
STATUS: STOPPED//
CONTROLLED BY LISTENER STARTER: NO//
Select RPC BROKER SITE PARAMETERS DOMAIN NAME:
Setup a System Administrator Account
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: RPC BROKER SITE PARAMETERS// NEW PERSON
(11 entries)
EDIT WHICH FIELD: ALL// .01 NAME
THEN EDIT FIELD: ACCESS CODE Want to edit ACCESS CODE (Y/N)
THEN EDIT FIELD:
Select NEW PERSON NAME: ADMINISTRATOR, SYSTEM
Are you adding 'ADMINISTRATOR,SYSTEM' as a new NEW PERSON (the 12TH)? No// YES (Yes)
Checking SOUNDEX for matches.
No matches found.
NEW PERSON INITIAL: SA
NEW PERSON MAIL CODE:
Want to edit ACCESS CODE (Y/N): Y
Enter a new ACCESS CODE <Hidden>: ********
Please re-type the new code to show that I have it right: ********
OK, Access code has been changed!
The VERIFY CODE has been deleted as a security measure.
The user will have to enter a new one the next time they sign-on.
Select NEW PERSON NAME:
Determine System Administrator account number
Inquire System Administrator account information and number
Select OPTION: 5 INQUIRE TO FILE ENTRIES
OUTPUT FROM WHAT FILE: NEW PERSON//
Select NEW PERSON NAME: ADMINISTRATOR,SYSTEM SA
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// Y (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// BOTH Computed Fields and Record Number
(IEN)
NUMBER: 10 NAME: ADMINISTRATOR,SYSTEM
INITIAL: SA ACCESS CODE: <Hidden>
DATE ENTERED: MAR 31, 2005 CREATOR: 0
Entry Last Edit Date: MAR 31, 2005 NAME COMPONENTS: 200
SIGNATURE BLOCK PRINTED NAME: SYSTEM ADMINISTRATOR
DATE ACCESS CODE LAST CHANGED (c): MAR 31,2005
PROVIDER KEY (c): 0
Select NEW PERSON NAME:
Assign keys to System Administrator Account
Now set the System Administrator and assign keys to the account.
Select OPTION:
GTM>SET DUZ=10
GTM>S $P(^VA(200,DUZ,0),"^",4)="@"
GTM>D ^XUP
Setting up programmer environment
This is a TEST account.
Select TERMINAL TYPE NAME: C-VT100
1 C-VT100 Digital Equipment Corporation VT-100 video
2 C-VT100HIGH Normal display of characters in BOLD !
CHOOSE 1-2: 1 C-VT100 Digital Equipment Corporation VT-100 video
Terminal Type set to: C-VT100
Select OPTION NAME: XUMAINT Menu Management
Select Menu Management Option: KEY Management
Select Key Management Option: ALLOCATION of Security Keys
Allocate key: XUMGR
Another key: XMMGR
Another key: XUPROGMODE
Another key: XUPROG
1 XUPROG
2 XUPROGMODE
CHOOSE 1-2: 1 XUPROG
Another key:
Holder of key: ADMINISTRATOR,SYSTEM SA
Another holder:
You've selected the following keys:
XUPROG XUMGR XUPROGMODE XMMGR
You've selected the following holders:
ADMINISTRATOR,SYSTEM
You are allocating keys. Do you wish to proceed? YES// YES
XUPROG being assigned to:
ADMINISTRATOR,SYSTEM
XUMGR being assigned to:
ADMINISTRATOR,SYSTEM
XUPROGMODE being assigned to:
ADMINISTRATOR,SYSTEM
XMMGR being assigned to:
ADMINISTRATOR,SYSTEM
Select Key Management Option:
Setup VistA Application Software Parameters
If you are planning to use the VistA applications such as Registration, Scheduling etc. you need to add new Institution to the INSTITUTION File.
Go back to the GTM> prompt and "SET XUMF=1" then "D Q^DI". Select Option #1 and edit File #4. Edit the field STATION NUMBER. For Station Number, you must enter the same number as the Site Number when you initialized FileMan. (See Start FileMan and Begin Setting Up Vista section.)
GTM>D Q^DI
VA FileMan 22.0
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: 4 INSTITUTION (67 entries)
EDIT WHICH FIELD: ALL// STATION NUMBER
THEN EDIT FIELD:
Select INSTITUTION NAME: OSWIZARDS MEDICAL CENTER
Are you adding 'OSWIZARDS MEDICAL CENTER' as
a new INSTITUTION (the 68TH)? No// YES (Yes)
STATION NUMBER: 1234
Select INSTITUTION NAME:
Add a Medical Center Division.
Select File #40.8 and edit fields FACILITY NUMBER and INSTITUTION FILE POINTER.
Enter the Institution STATION NUMBER for FACILITY NUMBER and the name of the Institution in INSTITUTION FILE POINTER.
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: INSTITUTION// 40.8 MEDICAL CENTER DIVISION
(2 entries)
EDIT WHICH FIELD: ALL// FACILITY NUMBER
THEN EDIT FIELD: INSTITUTION FILE POINTER
THEN EDIT FIELD:
Select MEDICAL CENTER DIVISION NAME: OSWIZARDS MEDICAL CENTER
Are you adding 'OSWIZARDS MEDICAL CENTER' as
a new MEDICAL CENTER DIVISION (the 3RD)? No// Y (Yes)
MEDICAL CENTER DIVISION NUM: 3//
MEDICAL CENTER DIVISION FACILITY NUMBER: 1234A
FACILITY NUMBER: 1234A//
INSTITUTION FILE POINTER: OSWIZARDS MEDICAL CENTER 1234
Select MEDICAL CENTER DIVISION NAME:
Enter additional information for the System Administrator user
PRIMARY MENU, VERIFY CODE etc.
From the GTM prompt, type "D ^XUP".
OPTION NAME: XUSEREDIT, it will give you two choices, select 1.
At Select NEW PERSON NAME: ADMINISTRATOR
1. EDIT AN EXISTING USER
Edit an Existing User
NAME: ADMINISTRATOR,SYSTEM Page 1 of 5
_______________________________________________________________________________
NAME... ADMINISTRATOR,SYSTEM INITIAL: SA
TITLE: NICK NAME: root
SSN: DOB:
DEGREE: MAIL CODE:
DISUSER: TERMINATION DATE:
Termination Reason:
PRIMARY MENU OPTION: EVE
Select SECONDARY MENU OPTIONS: OR CPRS GUI CHART
Want to edit ACCESS CODE (Y/N): FILE MANAGER ACCESS CODE: @
Want to edit VERIFY CODE (Y/N):
Select DIVISION:
SERVICE/SECTION: IRM
_______________________________________________________________________________
*** Press <RET> to edit the component parts of this name. ***
Press <PF1>H for help Insert
Multiple questions on the User Characteristic Fields Multiple signons, etc.
Set Up Menus for the System Manager
EVE is the System Manager menu
XUCOMMAND is a common menu available to all users.
Make FileMan, MailMan, and Manage MailMan menus accessible to the System Manager.
From the GTM prompt, type "D ^XUP".
At Select OPTION NAME: enter "XUMAINT".
Then at Select Menu Management, type "EDIT OPTIONS", then pick EVE.
Select 1 from the list then at NAME: EVE// type "^10".
At Select ITEM: enter "DIUSER".
Hit enter until you get to Select ITEM again (you may enter data for the other fields like SYNONYM if you wish).
At the next Select ITEM: enter "XMMGR".
GTM>D ^XUP
Setting up programmer environment
This is a TEST account.
Terminal Type set to: C-VT100
Select OPTION NAME: XUMAINT Menu Management
Select Menu Management Option: EVE ??
Select Menu Management Option: edit options
Select OPTION to edit: EVE
1 EVE Systems Manager Menu
2 EVENT CAPTURE (ECS) EXTRACT AU ECX ECS SOURCE AUDIT Event Capture
(ECS) Extract Audit
3 EVENT CAPTURE DATA ENTRY ECENTER Event Capture Data Entry
4 EVENT CAPTURE EXTRACT ECXEC Event Capture Extract
5 EVENT CAPTURE MANAGEMENT MENU ECMGR Event Capture Management Menu
Press <RETURN> to see more, '^' to exit this list, OR
CHOOSE 1-5: 1 EVE Systems Manager Menu
NAME: EVE// ^10 MENU
Select ITEM: XMMGR// DIUSER VA FileMan
...OK? Yes// (Yes)
ITEM: DIUSER//
SYNONYM:
DISPLAY ORDER:
Select ITEM: XMMGR Manage Mailman
...OK? Yes// YES (Yes)
ITEM: XMMGR//
SYNONYM:
DISPLAY ORDER:
Select ITEM:
CREATOR: SCHLEHUBER,CAMERON// ADMINISTRATOR,SYSTEM SA
HELP FRAME:
PRIORITY:
Select TIMES PROHIBITED:
Select TIME PERIOD:
RESTRICT DEVICES?:
Select PERMITTED DEVICE:
Select OPTION to edit:
Select Menu Management Option:
Add the XMUSER Menu to Mailman Menu.
GTM>D ^XUP
Setting up programmer environment
This is a TEST account.
Terminal Type set to: C-VT100
Select OPTION NAME: XUMAINT Menu Management
Select Menu Management Option: edit options
Select OPTION to edit: XUCOMMAND SYSTEM COMMAND OPTIONS
NAME: XUCOMMAND// ^10 MENU
Select ITEM: XMUSER// XMUSER MailMan Menu
...OK? Yes// YES (Yes)
MM
ITEM: XMUSER//
SYNONYM: MM// MM
DISPLAY ORDER:
Select ITEM:
CREATOR: STREET,MARK H// ^
Select OPTION to edit:
Change the default time before users are automatically signed off
To change the default time it takes before users are automatically signed off the system from the default of 300 seconds. This, again, is to give you more time to work as you are learning. Back out to the GTM prompt. At the GTM prompt, Type "D ^ZU".
At ACCESS CODE, type in the code you chose when setting up ADMINISTRATOR,SYSTEM.
At VERIFY CODE, hit ENTER. When asked for a new verify code enter and re-enter it.
GTM>D ^ZU
Volume set: ROU:bonez UCI: VAH Device: /dev/pts/1
ACCESS CODE: ********
VERIFY CODE:
Good afternoon root
You last signed on today at 14:24
You must change your VERIFY CODE at this time.
Enter a new VERIFY CODE: ********
Please re-type the new code to show that I have it right: ********
OK, Verify code has been changed!
WARNING -- TASK MANAGER DOESN'T SEEM TO BE RUNNING!!!!
Select Systems Manager Menu Option:
At Select Systems Manager Menu Option: Type "OPER"
(short for operations management) and hit enter.
You can see all of the choices available to you if you type "??".
At Select Operations Management Option: Type "KER"
(short for Kernel Management Menu) and hit enter.
At Select Kernel Management Menu Option: Type "ENT"
(short for Enter/Edit Kernel Site Parameters) and hit enter.
A similar screen as editing the SYSTEM MANAGER will be displayed.
Navigate the screen with the TAB key.
For DEFAULT TIMED-READ (SECONDS): change it to 3600
to allow an hour before being automatically signed off
Select Systems Manager Menu Option: OPERations Management
Select Operations Management Option: KERnel Management Menu
Select Kernel Management Menu Option: ENTer/Edit Kernel Site Parameters
Note: the TaskMan site parameters have been moved out of this file.
Use the Edit TaskMan Parameters option to edit those values.
Kernel Site Parameter edit
DOMAIN:BONEZ.OSWIZARDS.COM
DEFAULT # OF ATTEMPTS: 5 AGENCY CODE: VA
DEFAULT LOCK-OUT TIME: 600
DEFAULT MULTIPLE SIGN-ON: YES MULTIPLE SIGN-ON LIMIT:
DEFAULT AUTO-MENU: NO DEFAULT AUTO SIGN-ON: Disabled
DEFAULT LANGUAGE:
DEFAULT TYPE-AHEAD: YES
DEFAULT TIMED-READ (SECONDS): 3600 BROKER TIMEOUT: 180
BYPASS DEVICE LOCK-OUT: ASK DEVICE TYPE AT SIGN-ON:
LIFETIME OF VERIFY CODE: 90
DEFAULT INSTITUTION: SOFTWARE SERVICE
AUTO-GENERATE ACCESS CODES:
LOG RESOURCE USAGE?:
_______________________________________________________________________________
COMMAND: Press <PF1>H for help Insert
PAGE 2
Kernel Site Parameter edit
DOMAIN:BONEZ.OSWIZARDS.COM
Vol Set Max Sign-ons Log RT?
ROU 1000
VISTA 256 NO
ROUTINE MONITORING:
Routine Namespace's
PAGE 3
Kernel Site Parameter edit
DOMAIN:BONEZ.OSWIZARDS.COM
MAX SPOOL LINES PER USER: 9999999
MAX SPOOL DOCUMENTS PER USER:
MAX SPOOL DOCUMENT LIFE-SPAN:
LOG RESOURCE USAGE?:
DEFAULT DIRECTORY FOR HFS:
/tmp/
DNS IP: 192.168.1.3
NEW PERSON IDENTIFIERS:
PAGE 4
Kernel Site Parameter edit
DOMAIN:BONEZ.OSWIZARDS.COM
OPTION AUDIT: FAILED ACCESS ATTEMPTS:
INITIATE AUDIT: TERMINATE AUDIT:
Option to audit Namespace to audit
User to audit Device to audit
PAGE 5
Kernel Site Parameter edit
DOMAIN:BONEZ.OSWIZARDS.COM
IRM MAIL GROUP:
AFTER HOURS MAIL GROUP:
Update the Devices, Start Taskman and Mail a Message
These are basic devices to complete the setup. You can setup other devices, such as printers, later.
The system already comes with preconfigured devices.
It is best to leave the VOLUME SET(CPU) field blank. The help text for the field states: "If no name has been entered for this field, this device is assumed to be accessible from all CPUs in the network. In other words, when this device is referenced, the device handler will operate as if this device is resident on the local CPU".
The SIGN-ON/SYSTEM DEVICE: field should be set to NO or left blank for output devices and YES if the device is used to log on to the system.
Use FileMan to edit the CONSOLE, NULL, HFS, and TELNET devices.
- CONSOLE is the primary logon device.
- NULL device is used by the Vista RPC Broker
- HFS is used by the Kernel Installation and Distribution System (KIDS) to install application patches and new applications when they are released.
- TELNET device to allow remote access.
At the GTM> prompt, type "D Q^DI" to invoke VA Fileman.
At Select OPTION: type "1" (ENTER OR EDIT FILE ENTRIES)
at INPUT TO WHAT FILE:, enter "3.5"
GTM>D Q^DI
VA FileMan 22.0
Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
INPUT TO WHAT FILE: NEW PERSON// 3.5 DEVICE (41 entries)
EDIT WHICH FIELD: ALL//
Select DEVICE NAME: CONSOLE
1 CONSOLE CONSOLE |TRM|
2 CONSOLE GTM-UNIX-CONSOLE Console (GT.M) /dev/tty ROU
CHOOSE 1-2: 2 GTM-UNIX-CONSOLE Console (GT.M) /dev/tty ROU
NAME: GTM-UNIX-CONSOLE//
LOCATION OF TERMINAL: Console (GT.M)//
Select MNEMONIC: CONSOLE//
LOCAL SYNONYM:
$I: /dev/tty//
VOLUME SET(CPU): ROU//
SIGN-ON/SYSTEM DEVICE: YES//
TYPE: VIRTUAL TERMINAL//
SUBTYPE: C-VT100//
ASK DEVICE: YES//
ASK PARAMETERS:
ASK HOST FILE:
ASK HFS I/O OPERATION: ^
Select DEVICE NAME: TELNET
1 TELNET TELNET |TNT|
2 TELNET GTM-UNIX-TELNET TELNET /dev/pts/ ROU
CHOOSE 1-2: 2 GTM-UNIX-TELNET TELNET /dev/pts/ ROU
NAME: GTM-UNIX-TELNET//
LOCATION OF TERMINAL: TELNET//
Select MNEMONIC: TELNET//
LOCAL SYNONYM:
$I: /dev/pts///
VOLUME SET(CPU): ROU//
SIGN-ON/SYSTEM DEVICE: YES//
TYPE: VIRTUAL TERMINAL//
SUBTYPE: C-VT320// C-VT100
1 C-VT100 Digital Equipment Corporation VT-100 video
2 C-VT100HIGH Normal display of characters in BOLD !
CHOOSE 1-2: 1 C-VT100 Digital Equipment Corporation VT-100 video
ASK DEVICE: YES//
ASK PARAMETERS: ^
Select DEVICE NAME: HFS Host File Server /tmp/tmp.txt ROU
NAME: HFS//
LOCATION OF TERMINAL: Host File Server//
Select MNEMONIC:
LOCAL SYNONYM:
$I: /tmp/tmp.txt// /tmp/vista-tmp.txt
VOLUME SET(CPU): ROU//
SIGN-ON/SYSTEM DEVICE: ^
Select DEVICE NAME: NULL
1 NULL NT SYSTEM //./nul
2 NULL GTM-UNIX-NULL Bit Bucket (GT.M-Unix) /dev/null
3 NULL-DSM Bit Bucket _NLA0:
CHOOSE 1-3: 2 GTM-UNIX-NULL Bit Bucket (GT.M-Unix) /dev/null
NAME: GTM-UNIX-NULL//
LOCATION OF TERMINAL: Bit Bucket (GT.M-Unix) Replace
Select MNEMONIC: NULL//
LOCAL SYNONYM:
$I: /dev/null//
VOLUME SET(CPU):
SIGN-ON/SYSTEM DEVICE: NO//
TYPE: TERMINAL// ^
Check TaskMan's environement
From the GTM prompt
Enter "D ^ZTMCHK" to check if TaskMan's environment is OK.
This will display two screens with information on TaskMan's environment.
GTM> D ^ZTMCHK
Checking Task Manager's Environment.
Checking Taskman's globals...
^%ZTSCH is defined!
^%ZTSK is defined!
^%ZTSK(-1) is defined!
^%ZIS(14.5,0) is defined!
^%ZIS(14.6,0) is defined!
^%ZIS(14.7,0) is defined!
Checking the ^%ZOSF nodes required by Taskman...
All ^%ZOSF nodes required by Taskman are defined!
Checking the links to the required volume sets...
There are no volume sets whose links are required!
Checks completed...Taskman's environment is okay!
Press RETURN to continue or '^' to exit:
Here is the information that Taskman has:
Operating System: GT.M (Unix)
Volume Set: ROU
Cpu-volume Pair: ROU:bonez
TaskMan Files UCI and Volume Set: ROU,ROU
Log Tasks?
Default Task Priority:
Submanager Retention Time: 0
Min Submanager Count:
Taskman Hang Between New Jobs: 0
TaskMan running as a type: GENERAL
Logons Inhibited?: N
Taskman Job Limit: 9999
Max sign-ons: 1000
Current number of active jobs:
End of listing. Press RETURN to continue:
Start TaskMan
If TaskMan's environment is OK, start TaskMan.
Go back to the GTM prompt and type "D ^ZTMB" to start TASKMAN.
You will probably not see any output from this command.
To monitor TaskMan, enter "D ^ZTMON" from the GTM prompt.
Enter "^" at the UPDATE// prompt to exit the monitor or enter a "?" to see what the other options are.
GTM> D ^ZTMON
Checking Taskman. Current $H=59991,54440 (Apr 01, 2005@15:07:20)
RUN NODE=59991,54432 (Apr 01, 2005@15:07:12)
Taskman is current..
Checking the Status List:
Node weight status time $J
ROU:bonez RUN T@15:07:12 5933 Main Loop
Checking the Schedule List:
Taskman has no tasks scheduled.
Checking the IO Lists:
There are no tasks waiting for devices.
Checking the Job List:
There are no tasks waiting for partitions.
For VISTA:NTA there are 0 tasks. Out Of Service
For VISTA:NTB there are 0 tasks. Out Of Service
Checking the Task List:
There are 2 tasks currently running.
On node ROU:bonez there is 1 free Sub-Manager(s). Status: Run
Enter monitor action: UPDATE//^
Send a Message
Now send a message using Postmaster to your DUZ number.
From the GTM prompt type "S DUZ=.5 then D ^XUP".
You will get the response SETTING UP PROGRAMMER ENVIROMENT
then TERMINAL TYPE SET TO: (your default) and Select OPTION NAME:
Respond: "XMUSER".
At Select Mailman Menu Option: type "S" (for send).
At Subject: enter your subject, such as Test, and then hit enter.
You will then be prompted You may enter the text of the message and you will be offered the line number 1> where you can type your message, such as the infamous Hello world. Next will be line 2> and if you are done, just hit enter and at EDIT Option: you can do the same.
At Send mail to: POSTMASTER// enter the initials you used for your DUZ which were probably SM for System Manager.
You will then be told when MailMan was last used, which is probably NEVER. Hit enter at And Send to: and you should receive the message Select Message option: Transmit now// at which you hit enter and will hopefully receive the message Sending [1] Sent. Type "^" to exit.
GTM>S DUZ=.5
GTM>D ^XUP
Setting up programmer environment
This is a TEST account.
Terminal Type set to: C-VT100
Select OPTION NAME: XMUSER MailMan Menu
VA MailMan 8.0 service for POSTMASTER@BONEZ.OSWIZARDS.COM
You last used MailMan: 01/18/05@15:11
You have no new messages.
Select MailMan Menu Option: S Send a Message
Subject: TESTING
You may enter the text of the message...
1>Hello, this is a test of the Emergency Broadcast System
2>
EDIT Option:
Send mail to: POSTMASTER// SA ADMINISTRATOR,SYSTEM IRM
Last used MailMan: 04/01/05@14:23
And Send to: MHS STREET,MARK H IRM Last used MailMan: Never
And Send to:
Select Message option: Transmit now// Sending [1]...
Sent
Select MailMan Menu Option:
Check Mail
Now see if you received your mail.
Log on using "D ^ZU".
At the Systems Manager prompt, type "MAIL".
Then at the Select MailMan Menu Option: type "NEW" Messages and Responses. Read the mail.
GTM>D ^ZU
Volume set: ROU:bonez UCI: VAH Device: /dev/pts/1
ACCESS CODE: ********
VERIFY CODE: ********
Good afternoon root
You last signed on today at 15:18
Select Systems Manager Menu Option: MAILMan Menu
VA MailMan 8.0 service for ADMINISTRATOR.SYSTEM@BONEZ.OSWIZARDS.COM
You last used MailMan: 04/01/05@15:19
You have 1 new messages.
Select MailMan Menu Option:
NEW
Subj: TESTING [#1] 04/01/05@15:13 1 line
From: POSTMASTER In 'IN' basket. Page 1
Hello, this is a test of the Emergency Broadcast System
Enter message action (in IN basket): Ignore//
Start and Test RPC Broker
Start and test the RPC Broker.
The RPC Broker is VistA's Client/Server software and is needed by VistA's GUI client.
Type "D STRT^XWBTCP(port)" at the GTM prompt.
The system status should now show the broker listener (XWBTCPL) running.
GTM>D STRT^XWBTCP(9200)
Start TCP Listener...
Checking if TCP Listener has started...
TCP Listener started successfully.
GTM>
CPRS Key and Tab Assignment
Enter D Q^DI at the GTM> prompt and choose 'Option 1' and the NEW PERSON file.
Fields to edit, first choose KEY, then CPRS TAB.
Assign the key ORES for unrestricted ordering as if you were a physician. (See page 21 in the CPRS Setup Guide for other keys.)
Under CPRS TAB, type ?? and you will see two choices, RPT and COR. Enter RPT first, then complete COR.
GTM>D Q^DI VA FileMan 22.0 Select OPTION: '''1''' ENTER OR EDIT FILE ENTRIES INPUT TO WHAT FILE: DEVICES// '''NEW PERSON''' EDIT WHICH FIELD: ALL// '''KEYS''' 1 KEYS (multiple) 2 KEYSTROKES FROM LM WP CHOOSE 1-2: '''1''' KEYS (multiple) EDIT WHICH KEYS SUB-FIELD: ALL// (Hit enter here) THEN EDIT FIELD: '''CPRS TAB''' (multiple) EDIT WHICH CPRS TAB SUB-FIELD: ALL// (Hit enter here) THEN EDIT FIELD: '''RESTRICT PATIENT SELECTION''' THEN EDIT FIELD: (Hit enter here) Select NEW PERSON NAME: ''SA'' ADMINISTRATOR,SYSTEM Select KEY: // '''ORES''' ...OK? Yes// (Yes) KEY: ORES// REVIEW DATE: Select KEY: (Hit enter here) Select CPRS TAB: // '''RPT''' EFFECTIVE DATE:// '''APRIL 1,2005''' EXPIRATION DATE:// '''APRIL 1,2020''' CPRS TAB: RPT// '''COR''' - the CPRS GUI "core" tabs. Are you adding 'RPT' as a new CPRS TAB (the 2ND for this NEW PERSON)? No// '''Y''' EFFECTIVE DATE:// '''APRIL 1,2005''' EXPIRATION DATE:// '''APRIL 1,2020''' Select CPRS TAB: (Hit enter here) RESTRICT PATIENT SELECTION:// '''NO''' Select NEW PERSON NAME:(Hit enter here) Select OPTION:(Hit enter here) GTM>
Overview of starting and stopping components
A quick overview of starting and stopping TaskMan, HL Filer Monitor and RPC Broker Listener components is in order.
1. To start TaskMan;
GTM>D ^ZTMB
2. To start Background Filers
GTM>D ^XUP
Setting up programmer environment
Access Code:
Terminal Type set to: C-VT100
Select OPTION NAME: START BACKGROUND FILER XMMGR-START-BACKGROUND-FILER START background filer
START background filer
<< Background Filers will start soon. >>
3. To start HL Filer Monitor
GTM>D ^XUP Setting up programmer environment Terminal Type set to: C-VT100 Select OPTION NAME: HL FILER MONITOR Task Number of Asked Incoming Filer To Stop Last Known Date/Time Time Difference ** No incoming filers are running ** Task Number of Asked Outgoing Filer To Stop Last Known Date/Time Time Difference ** No outgoing filers are running ** (+I) Start incoming filer (-I) Stop incoming filer (*I) Delete incoming filer (+O) Start outgoing filer (-O) Stop outgoing filer (*O) Delete outgoing filer (N) Next 4 lines in list (B) Back 4 lines in list (Q) Quit Type selection:Q
4. Start the RPC Broker Listener, pick a port you want to run the listener on. ex. 9210
GTM>D STRT^XWBTCP(9210)
5. To Stop RPC Broker Listener.
GTM>D STOP^XWBTCP(9210)
6. To stop Mailman Background Filers
GTM>D ^XUP
Setting up programmer environment Access Code:
Terminal Type set to: C-VT100
Select OPTION NAME: STOP BACKGROUND FILER
7. To stop HL FILER MONITOR run the exact same command as above and pick the proper selection from the menu at the bottom of the monitor.
GTM>D ^XUP Setting up programmer environment Terminal Type set to: C-VT100 Select OPTION NAME: HL FILER MONITOR Task Number of Asked Incoming Filer To Stop Last Known Date/Time Time Difference ** No incoming filers are running ** Task Number of Asked Outgoing Filer To Stop Last Known Date/Time Time Difference ** No outgoing filers are running ** (+I) Start incoming filer (-I) Stop incoming filer (*I) Delete incoming filer (+O) Start outgoing filer (-O) Stop outgoing filer (*O) Delete outgoing filer (N) Next 4 lines in list (B) Back 4 lines in list (Q) Quit Type selection:-I
8. To stop TaskMan
GTM>D STOP^ZTMKU
Are you sure you want to stop TaskMan? NO//Y
Shutting down TaskMan
Should active submanagers shut down after finishing their current tasks? NO//Y
Okay!
9. Rundown the database, from the vista user's shell prompt you can choose the alias or you can run the mupip command
vista$ rundown
or
mupip rundown -r "*"
