Home

KERNEL SYSTEMS MANAGEMENT GUIDE Version 8.0

1. SYSTEMS MANAGER MENU EVE Spool Management XU SPL MGR Delete A Spool Document XU SPL DELETE List Spool Documents XU SPL LIST Print A Spool Document XU SPL PRINT July 1995 Kernel Systems Management Guide 17 7 Revised June 2008 Version 8 0 Spooling Spooler Site Parameters Edit Option Figure 17 14 Spooler Site Parameters option SYSTEMS MANAGER MENU EVE Spool Management XU SPL MGR Spooler Site Parameters Edit AUS PSS EE The Spool Management menu also has the Spooler Site Parameters Edit option XU SPL SITE for setting the spooler site parameters system wide defaults for the spooler The initial settings are defined when installing Kernel but can be edited afterwards The spooler site parameters control the total number of documents a user can create and the total number of lines for all documents When the limits are reached the user cannot create new documents The effects of the three spooler site parameter fields are as follows Table 17 1 Spooler site parameter fields MAX SPOOL LINES PER USER This field holds the MAX number of lines of spooled output a user is allowed If the user has more than this number then they will not be permitted to spool any more until some of their spool documents are deleted This only controls allowing the creation of new spool documents and does not terminate a job that is running that has gone over the limit Recommended value 9999
2. Select Help Processor Option July 1995 Kernel Systems Management Guide 12 3 Revised June 2008 Version 8 0 Help Processor System Management Help frames are entries in the HELP FRAME file 9 2 The Header and Text of help frames can be displayed to users to provide instruction about software or other topics Help frames can be distributed with software or can be created locally to provide information about local policies and procedures The options used to create edit and link help frames are on the Help Processor menu XQHELP MENU shown below Figure 12 5 Help Processor menu options SYSTEMS MANAGER MENU EVE Menu Management XUMAINT Help Processor XOHELP MENU Display Edit Help Frames XQHELP DISPLAY List Help Frames XOHELP LIST New Revised Help Frames XOHELP UPDATE Cross Reference Help Frames XOHE LP XREF Assign Editors XOHELP ASSIGN Unassign Editors XQHELP DEASSIGN Fix Help Frame File Pointers XOHELPFIX Use of the Help Processor options is explained by help frames associated with the options Display Edit Help Frames Option The help frames can be displayed with the Display Edit Help Frames option XQHELP DISPLAY You can use the option syntax at the select prompt as follows Figure 12 6 Display Edit Help Frames option Displaying help using the option syntax Select Help Processor Option DISPLAY lt Enter gt Edit Help Frames List Help Fra
3. ssessssssseeeeeeeeesesessssssssssseseeereee 28 4 Figure 28 7 ACTION menu Sample user entrics cccccccccssecssenssssnsnsssssessesssccececceeccceaeaenasseessees 28 5 July 1995 Kernel Systems Management Guide XX1X Revised June 2008 Version 8 0 Figures and Tables Tables Table 2 1 User s Toolbox menu options and documentation references ccccccseeeeeeeceeeeeeaeeseeeeeeeeeees 2 8 Table S i Kernel Sisnom AUGtiIne Piles sesei ovee saa sovessnwededis cocaoes sues eato zac EEE EA AE 3 29 Table 5 1 File Access Security level properties isein and voncuhie a e a E a iea Sie thins 5 5 Table 7 1 Menu diagramming options to discover tree roots and relationships between OPUONS SUDOPUONS eure eee a E aE a E A A AON 7 5 Table 7 2 Menu Manger variables always defined ccccsseeeseccceccceeeeeeseececceeeaaeeeeecceeseesaeeseeeeeess 7 20 Table 9 1 Secure Menu Delegation Menu lt OPtiOns ssccssassaczecccanadasussaiancaveicessussasancnianadpeasadsaneseabeessuasearaneenen 9 7 Table TO L Art process no COMES sannan pak esasicd sneha mae canna teas os iadenade amas N E tase 10 2 Table 11 1 SERVER ACTION field 221 security values for server requests cccccessssseeeeeeeeeees 11 2 Table 11 2 OPTION file 19 field values when setting up a server option ccecceceeeeeeeeeeeeeeeeeeees 11 3 Table 11 3 XQSCHK server option Error Warning messages essessssoeeressssssseerrssssssseseeressss
4. Reindexing All Users Security Keys Option Figure 8 6 Reindex the users Key s option SYSTEMS MANAGER MENU EVE User Management XUSER Manage User File XUSER FILE MGR Reindex the users key s XUSER KEY RE INDEX You can use the Reindex the users key s option XUSER KEY RE INDEX to re index all users security keys in the NEW PERSON file 200 If a user has a security key but is lacking the corresponding XUSEC cross reference for the key you can use this option to regenerate the X USEC cross reference While the XUSEC cross reference is being rebuilt there can be an impact on all users with security key lookups failing in XUSEC until the index is entirely rebuilt therefore this option should be used with caution and is best delayed until users are not signed on Using Security Keys with Reverse Locks If a security key is associated with an option via the REVERSE NEGATIVE LOCK field rather than the LOCK field 3 it functions to lock out users who hold the key The security key used for a reverse lock is just like any other key differing only in the way it is associated with an option Menu Management s Diagram Menus option indicates the existence of any reverse locks such as the use of the XMNOPRIV security key to prevent access to MailMan s shared mail facility The typical use of a security key with the REVERSE NEGATIVE LOCK field is to restrict access to options otherwise available to
5. You can select tasks either by task number or list number In the list of tasks the list number is at the left hand side of the each task listing and is followed by the task number for each task in parentheses The rest of the information helps identify where the task came from and what it will do Tasks in the Task List You can only select tasks that are still in TaskMan s task list When a task finishes running it usually removes itself from the task list Thus you should not get a listing of every task you have run in the last year Tasks that do not clean up their entries usually get cleaned out by TaskMan several days after they July 1995 Kernel Systems Management Guide 19 3 Revised June 2008 Version 8 0 TaskMan User Interface complete You should only have to select tasks that are still actively waiting to start currently running or encountered some kind of problem while running Display Status of Tasks Once you ve selected a task to work with you can ask to see the status of that task using the Display status option D TaskMan uses a task s status to try to explain how soon the task will run and why The possible normal statuses for a task include e Scheduled for lt date and time gt e Being inspected by TaskMan e Waiting for a partition e Being prepared e Currently running e Completed lt date and time gt NOTE Please keep in mind that TaskMan can only guess whether a task is currently
6. REF Multi Term Look Up MTLU Application Programming Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml Once you are in VA FileMan do the following Figure 25 20 VA FileMan Utility Functions option Sample user entries Select OPTION UTILITY FUNCTIONS Select UTILITY OPTION CROSS REFERENCE A FIELD MODIFY WHAT FILE ICD DIAGNOSIS lt Enter gt ICD DIAGNOSIS 12535 entries Select FIELD DESCRIPTION CURRENT CROSS REFERENCE IS MUMPS D INDEX OF FILE CHOOSE E EDIT D DELETE C CREATE C WANT TO CREATE A NEW CROSS REFERENCE FOR THIS FIELD NO Y lt Enter gt YES CROSS REFERENCE NUMBER 2 lt Enter gt Select TYPE OF INDEXING REGULAR MUMPS WANT CROSS REFERENCE TO BE USED FOR LOOKUP AS WELL AS FOR SORTING YES N lt Enter gt NO SET STATEMENT S ICD9 AIHS I DA D S XTLKWIC KILL STATEMENT S ICD9 AIHS I DA D K XTLKWIC INDEX AC AIHS NO DELETION MESSAGE lt Enter gt DESCRIPTION lt Enter gt Edit NO lt Enter gt DO YOU WANT TO CROSS REFERENCE EXISTING DATA NOW YES Y lt Enter gt YES EXCUSE ME THIS MAY TAKE A FEW MOMENTS 25 20 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU Figure 25 21 Add Entries To Look
7. e Compare one or more current routines to previous versions July 1995 Kernel Systems Management Guide 27 1 Revised June 2008 Version 8 0 Verification Tools The Verifier Tools Menu XTV MENU consists of the following options that are described below Figure 27 1 Verifier Tools Menu options SYSTEMS MANAGER MENU EVE Verifier Tools Menu XTV MENU Update with current routines XTVR UPDATE Routine Compare Current with Previous XTVR COMPARE Routine Compare Update with Current Routines Option The Update with Current Routines option XTVR UPDATE records the text of the routines indicated in the file used to maintain changes in routines Only the last version entered is kept intact previous entries reflect only the changes in lines added and or deleted to make the next version This option is used to record the current routine structure so that it can be compared with future versions of the routine using the Routine Compare Current with Previous option XTVR COMPARE After editing the routine the Update with Current Routines option can again be used to store changes Rather than storing all minor changes the user can choose to wait and use the Update with Current Routines option only after extensive edits have been made Lines are compared and changes including inserted or deleted lines are recorded Alteration of the routine s second line are usually insignificant and are ignored The Update with
8. 81 Device IOP value 1F 82 SIO value 2F 83 gt Device Type 3F 84 Device Sub Type 4F 85 Device elo MOdit rer SEI F26 Hose File Address TOET 6 7 Sync Flag 7F 88 IO gt Reschedule Count 8N task 22 gt COS devices file entry ae T1 task 25 D7 device parameters 1 task 26 D10 hunt group name 1 task 26 SIO values of hunt group members SZTSK OO Lil Bs SZTSK STO The remaining nodes of each entry are used to pass variables to the task If the task has been manipulated only using TaskMan s Program Interface then the entries look like this Figure 22 30 TASKS File 14 4 nodes 2 of 2 SSA SK task name F2 value of saved variable ZTSK task array node F2 value of saved variable ZTSK task array node F2 value of saved variable The distinguishing characteristic here is the fact that the variables to be passed are all subscripted under the 3 node July 1995 Kernel Systems Management Guide 22 31 Revised June 2008 Version 8 0 TaskMan System Management Operation Task Status Codes This topic lists the various codes that may be found in the first piece of the 1 node the text displayed for that code by the List Tasks option and the meaning of that code These codes are set into the tasks at every point in processing where the status changes along with a time
9. Selecting Common Options with the Double Quote Since Common options are intended to be readily accessible there is a shortcut method to reach them While you could use an Up arrow Jump it is quicker to enter a quotation mark followed by the option specification name Figure 6 8 selects the User s Toolbox menu from the Common menu via its synonym TBOX Figure 6 8 Selecting common options via the double quote User s Toolbox menu option Select Sample Menu Option TBOX Display User Characteristics Edit User Characteristics Electronic Signature code Edit Menu Templates Spooler Menu TaskMan User User Help Select User s Toolbox Option Menu Templates Option Menu templates are like scripts You can use them to execute a fixed series of options in sequence Tools for creating deleting listing and renaming templates are options on the Menu Templates menu part of the User s Toolbox TBOX menu Figure 6 9 Menu Templates Option Select Menu Templates Option Create a new menu template Delete a Menu Template List all Menu Templates Rename a menu template Show all options in a Menu Template Select Menu Templates Option When you create a MENU template you are prompted for a series of options that lead to a final non menu 1 e executable destination option Once you choose one non menu option to be executed you can navigate to other options and choose them to be executed as well if you wish When
10. The Print 2 occurrences of errors on T 1 QUEUED option XUERTRP PRINT T 1 2 ERR lists the first two occurrences of each error recorded on the previous day T 1 represents Today 1 Yesterday It can be queued to run shortly after midnight If a device is specified the output is sent to the specified device If a device is not specified the output is placed in a mail message and sent to the individual who queued the option to run It should be set to automatically requeue at a 1 day D interval Clean Error Trap Option You can use the Clean Error Trap option XUERTRP CLEAN to purge the error log It is locked with the XUPROGMODE security key You can use the corresponding direct mode utility XTERPUR in programmer mode There is also a queuable version Error Trap Auto Clean option XUERTRP AUTO CLEAN Purging is a partial clearing of the ERROR LOG file 3 075 stored in the ZTER 1 global This global node should not be deleted directly since potentially important recent errors would be purged Deletion of the entire ZTER global would be a greater mistake since the standard reference data contained in the ERROR MESSAGES file 3 076 stored in ZTER 2 would be lost You are first prompted for the number of days to leave in the error trap If you enter a number of days to retain errors all errors older than the specified number of days are immediately purged Figure 13 6 Choosing the number of days to leave errors in the e
11. ZTER The error log can be displayed with D XTER or with the corresponding option Also the error log can be purged with D XTERPUR Errors can also be purged from within the menu system with an option that is locked with the XUPROGMODE security key The corresponding direct mode utilities can be used in programmer mode as follows e Record an Error gt D ZTER e Display Error Trap gt D XTER e Purge Error Log gt D XTERPUR i REF For more information on Error Processing please refer to Chapter 13 Error Processing in this manual Kernel Toolkit Application Program Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml 27 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Verification Tools July 1995 Kernel Systems Management Guide 27 5 Revised June 2008 Version 8 0 Verification Tools 27 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 28 Miscellaneous Programmer Tools Programmer Options Menu User Interface Figure 28 1 Programmer Options menu options Toolkit miscellaneous tools SYSTEMS MANAGER MENU EVE Programmer Options lt locked with XUPROG gt XUPROG KIDS Kernel Installation amp Distribution System XPD MAIN lt locked with XUP
12. pid Log S SAY write output Fa Sk open and build the input tide 5 OPEN wrrte output Main tLe SAY Taskman temp file to run a submanager SAY Sch Derete chi ee Tile ack it iS Oe open SAY S set verity CAT Nios PPLE sand par SAY 1S gsegaion TI ple Vag Bape es UV START S27 TMSt SAY S exit gt Close ourput 9 1 S If a log file is needed change _NLAO to outfile S name ZTMS_ pid S Un Sysssystem loginout exe Jeo tee en Ves output _NLAO detach process name GA S Wait for loginout to run it then delete the file S wait 00 01 gt del TMP_ ZTMS 1 Sapo ane July 1995 Kernel Systems Management Guide 21 19 Revised June 2008 Version 8 0 TaskMan System Management Configuration Figure 21 18 Example of OpenVMS User TASKMAN on ALPHA AXP Systems Username TASKMAN Account Cle Default LGICMD Flags Primary days Secondary days NO access restrictions Expiration Pwdlifetime bast Login interactive Maxjobs Maxaccljobs Maxdetach Prelim Prio DCL USERS TASKMAN LOGIN none 180 00 00 20 NOV 1992 10 34 Fillm Shrfillm BIOlm DOM ASTlm Queprio TOEI1m CPUS none Enqlm Authorized Privileges CMKRNL TMPMBX OPER NETMBX Default Privileges CMKRNL TMPMBX OPER NETMBX Pwdminimum 6 Pwdchange interactive 300 0 300 900 600 10 4096 Owner UIC Tables pEOyA0 DCLTABLES DisCtlY Restricted DisWelcome DisReport Mon T
13. 22 30 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation The following diagram Figure 22 29 describes the nodes 0 through 26 for each entry in the TASKS file 14 4 Figure 22 29 TASKS File 14 4 nodes 1 of 2 SGhalonk cask Fy 0 R01 Entry Point TIEN o 2 Routine Name 2F oO G S User gt 3P 200 4 Requested UCI 4F 5 Creation Time H gt 5F 6 Scheduled Run Time SH 6F 7 Type of Task gt 7F 8 Option Number 8N 9 Option Name 9F 10 gt Creator Name 10F gt 11 Creation UCI 11F 12 Creation Volume Set 12F gt 13 RESERVED 13F 14 Requested Volume Set 14F 15 gt Priority 15N 16 Original Create date H 16F SEHALSK task fy lt 0L 21 Original Destination UCL 1E 22 Original gt Destination Volume 2F ZTSK task 02 31 Current Destination UCI 1F 32 Current gt Destination Volume Set 2F 33 Hop Count SN ZTSK task 03 41 Task Description E1 240F ZTSK DO 04 42 Schedule Time Seconds 1N ZTSK task 1 51 Status Code 1F 52 Last Update H 2F 53 gt Status Notes 3F 54 Job 4N 59 8 Remember sae UNe ia ok geo SeOp Flag TLORIS ZTSK task 12 71 Error Count 1N 72 Error H 2F 73 Error gt Message 3F SZTSK task 2
14. HFS device EDIT A HOST FILE SERVER DEVICE LOCATION Host Disk File Sil USERS TEMP MIXED TXT Alt I tmp mixed txt SUBTYPE P OTHER ASK PARAMETERS YES MARGIN WIDTH ASK HOST FILE YES PAGE LENGTH ASK HFS I O OPERATION NO VOLUME SET CPU OPEN PARAMETERS NWS PRE OPEN EXECUTE POST CLOSE EXECUTE QUEUING ALLOWED SUPPRESS FORM FEED The following example shows a NULL device using the TRM or VTRM Device Edit option XUDEVEDITTRM to update Field 52 15 4 Sample user dialogue updating the SECONDARY I field 52 NULL device Edit a TRM or VTRM device NAME NULL LOCATION Bit Bucket SI _NLAO Alt I dev null TYPE TERMINAL SUBTYPE P OTHER SIGN ON SYSTEM DEVICE VOLUME SET CPU ASK DEVICE N MARGIN WIDTH ASK PARAMETERS NO PAGE LENGTH QUEUING SUPPRESS FORM FEED 15 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler System Management The following example shows a printer set up as an HFS device with the Terminal Type CLOSE EXECUTE which submits the file to the OS print queue 15 5 Sample user dialogue EDIT A HOST FILE SERVER DEVICE NAME SDD P10 LOCATION Printer next to Raul SI USERS TEMP SDD DN2SPRT TXT Alt SI SUBTYPE P HP8000 TCP S ASK PARAMETERS NO MARGIN WIDTH ASK HOST FILE NO PAGE LENGTH ASK HFS I O OPERATION NO VOLUME SET CPU OPEN PARAMETERS NWS CLOSE PARAMETERS PRE OPEN EXECUTE POST CLOSE EXECU
15. If you want to the run the startup option on multiple CPUs make multiple entries in the OPTION SCHEDULING file 19 2 and use the QUEUED TO RUN ON VOLUME SET field to specify on what Volume Set CPU each should run La STARTUP PERSISTENT TaskMan will queue the job as it does for STARTUP It will mark it as a PERSISTENT task to be restarted if it stops unexpectedly PERSISTENT IaskMan will run it on its normal schedule marking it as Persistent TaskMan will restart the task if it stops unexpectedly If the task completes in a normal fashion it is treated like any other regularly scheduled task and it is rescheduled based on the value in the RESCHEDULING FREQUENCY field 6 in the OPTION SCHEDULING file 19 2 Table 22 2 Option Scheduling frequency code formats nM entry entry Every n months at each entry in the parameter list the entries in the parameter list for every n months only can be Entry Format Frequency dd time Day of month e g 15 nday time Nth day of week in month e g 1W 3W L time Last day of month Lday time Last specific DAY in month e g LM LT LW 22 22 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Table 22 3 Day codes used in Option Scheduling frequency code formats Table 22 4 Examples of Option Scheduling frequency code formats ar IML 25 45 1M LS The last Saturday of the month 3M
16. KERNEL SYSTEMS MANAGEMENT GUIDE Version 8 0 July 1995 Revised June 2008 Department of Veterans Affairs VA Office of Information amp Technology OI amp T Common Services CS Revision History Documentation Revisions The following table displays the revision history for this document Revisions to the documentation are based on patches and new versions released to the field Table i Documentation revision history Date Revision Description Author 07 95 1 0 Initial Kernel V 8 0 software and San Francisco CA Office of documentation release Information Field Office Software Version 8 0 OIFO e Project Manager Hans Von Blanckensee Developers Kernel Development Team Technical Writer Kyle Clarke 12 09 04 2 0 Kernel V 8 0 documentation Technical Writer Thom reformatting revision Blom Oakland OIFO This is the initial complete reformatting of the Kernel Systems Management Guide since its original release in July 1995 The largest change with the Kernel Systems Management Guide is that all developer specific content has been extracted and placed into a new Kernel Developer s Guide Also at this point in time only minimal content updates have been made based on select released Kernel patches Due to time constraints not all released Kernel patches with content changes have been added at this time We wanted to get a new baseline document published so that in the future we can more easily up
17. Queuing File Access Specifications Most of the options provide the opportunity to queue after specifying who is to be granted which files Queuing sends the specifications to TaskMan to assign to users at a later time TaskMan can work at an off peak time e g midnight to avoid consuming system resources during the daytime If the system is not busy queuing is still a good idea since your terminal will otherwise be tied up while the report is being printed Running the File Access Security Conversion Advantages To implement File Access Security you need to run a conversion Some advantages of implementing File Access Security include e Easier to identify levels of access Running the conversion makes it possible to identify the levels of access each individual user has to each file e Enhanced system performance Checking file access by user is slightly faster in terms of global accesses and CPU time Advance Preparation for the Conversion The File Access Security conversion is designed to allocate access privileges to all of your users according to their current FILE MANAGER ACCESS CODE field 3 value in the NEW PERSON file 200 DUZ O combined with information about their file access through options stored in the DISV global After the conversion you should get only a few user requests for file access The File Access Security menu XUFILEACCESS an option on the User Management menu XUSER should then be used to ad
18. When a user enters invalid Access and Verify code pairs the number of attempts is recorded and the device appears to lock after the site parameter limit of failed access attempts is reached After this point Signon Security continues to record what the user types but only to create a record in the FAILED ACCESS ATTEMPTS LOG file 3 05 If a valid Access code is entered Signon Security can link the attempt with a known user and will record that user s name in the log Since it is a valid code its text is not recorded in the log The text of subsequently entered invalid Verify codes can however be recorded as clues to the source of the access attempt If the Access code is not valid a user s name cannot be associated but the text of the attempt can be recorded The log also records the time of day device used and CPU UCI location 3 28 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management Kernel Signon Auditing Files Table 3 1 Kernel Signon Auditing Files Global Set Display Initiate Print Location Parameters Parameters Terminate Reports Purge Logs SIGN ON LOG XUSEC 0 Predefined Always done Print Sign Purge Sign on 3 081 on Log Log XUSC XUSCZONK LIST FAILED ACCESS a ZUA 3 05 Establish Display the On Off switch Devices Failed Access ATTEMPTS LOG System Kernel Audit Device Attempts Log 3 05 Audit Parameters Failed Purge Parameters XU SPY Acc
19. You can list all devices In addition to printers this list shows other types of devices you can use to handle output An example of a partial printer listing is shown below Figure 14 6 Sample printer listing Select one A P C D or E P GENICOM10P 6th Floor 301 GENICOM16P 6th Floor 301 HP LASER DEV 10P HP LASER DEV 12P REF Unusual device types e g Hunt Groups and Resource devices are discussed in the Special Device Issues chapter in this manual Specifying Right Margin and Page Length Ordinarily when choosing an output device you only need to specify the device name There can be times however when you may find it useful to specify the right margin and or the page length for your output The syntax to specify margin and page length uses semicolon delimiters The format is DEVICE Device Name Right Margin Page Length 14 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler User Interface The following examples show how to use the additional semicolon delimited pieces at the DEVICE prompt Table 14 1 Sample semicolon delimited pieces at the DEVICE prompt DEVICE DVNM5 80 66 Use the DVNM5 device with a right margin of 80 columns and page length of 66 lines DEVICE 132 Use the home device right margin of 132 DEVICE 5 66 Use the home device and format the output with page breaks at 66 lines DEVICE 9999 Scroll output on the home device without needi
20. lt Enter gt No Enter the software name Routine XDRMAIN you want to check with Routine lt Enter gt XINDEX 1 routine Select BUILD NAME XT 7 3 102 lt Enter gt TOOLKIT Include the compiled template routines N lt Enter gt Print more than compiled errors and warnings YES lt Enter gt Print summary only NO lt Enter gt Or enter S for an Print routines YES lt Enter gt indented report Print R egular S tructured or B oth R lt Enter gt Print the DDs Functions and Options YES lt Enter gt Or enter YES to store the Save parameters in ROUTINE file NO lt Enter gt parameters Index all called routines NO lt Enter gt Print errors and warnings with each routine YES lt Enter gt July 1995 Kernel Systems Management Guide 26 3 Revised June 2008 Version 8 0 Routine Tools The following is a list of the error conditions that the XINDEX utility flags The 1995 ANSI M Standard is taken into account with new syntax and other checks Figure 26 3 XINDEX List of the error conditions that the XINDEX utility flags UNDEFINED COMMAND rest of line not checked Non standard Undefined Z command Undefined Function Undefined Special Variable Must be manually checked by the WO OnAHNDOABWN EF Unmatched Parenthesis programmer Unmatched Quotation Marks ELSE Command followed by only one space FOR Command drid Moc COMceamm t T QUIT
21. 11 3 XUPROGMODE 26 5 System Management 11 1 Security Keys Testing 11 5 XUPROGMODE 26 5 What Can Server Options Do 11 1 Security Keys What is a Server Option 11 1 XUPROGMODE 26 5 XQSCHK Utility 11 6 Security Keys XQSPING Utility 11 5 XUPROGMODE 26 6 SERVER REPLY Field 225 11 5 Security Keys Servers XUPROGMODE 26 8 Compute Mode 21 4 Security Keys General Processor 21 4 XUPROG 26 8 Other Non TaskMan 21 4 Security Keys Print Server Mode 21 4 XUPROGMODE 27 4 SERVICE SECTION Field 3 17 3 21 Security Keys SERVICE SECTION File 49 3 17 3 21 XUPROG 28 1 Set Backup Reviewer for Alerts Option 10 10 Security Keys SET LOGINS INTERACTIVE DCL Command XUPROGMODE 28 1 3 3 Security Keys Setting up a Server Option 11 3 XUPROGMODE 28 1 Setup Index 36 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan and DCL Context in Cache VMS 21 15 SEX Field 4 NEW PERSON File 200 3 9 Shared Device and Terminal Type Attributes How are They Used 15 9 Shortcuts Double Quote and Option Name 6 8 Multi Term Look Up MTLU 25 1 25 12 Point to a Single Word or Phrase 25 2 Signon 2 5 Up arrow Jump 6 5 6 8 Shortcuts Option Multi Term Look Up MTLU 25 2 25 13 Example 25 18 Show a Delegate s Options 9 11 Show Error Log Option 22 25 Show the Security Keys of a Particular User Option 9 9 Show Users with Selected Primary Menu Option 7 6 SIGNATURE BLOCK PRINTED NAME Field 4 1 4 2 SIGNA
22. 13 7 INTERACTIVE USER S PRIORITY Field 3 5 INTRO TEXT Field 3 1 3 7 Introduction 1 1 Multi Term Look Up MTLU 25 1 System Manager 1 2 User 1 1 Introductory Text Signon Security 3 1 Introductory text edit Option 3 1 INVOKED BY ROUTINE Field 12 5 Invoking Non VistA Applications Options 7 4 IO List 22 9 22 10 Variables 7 4 IONOFF Variable 18 6 IRM Setup to Enable Building Options from Templates 9 5 J JOB Command 20 2 21 3 21 4 21 5 22 29 Job List 20 6 22 10 Node 22 28 Jobs KILL 22 10 Jumbled Screen Escaping from 2 6 Jump Nodes 7 16 XUTL Global 7 19 Jump Start Signon 2 5 Jumps Error Messages During Menu Jumping 7 14 Kernel Systems Management Guide Index 17 Version 8 0 Index Options 6 5 Phantom 7 14 7 15 Rubber band Jump 6 6 Up arrow 6 1 6 5 6 7 6 8 6 9 7 13 K KAAJEE Documentation Web Address 2 2 KEEP AT TERMINATE Field 8 4 Kernel Error Trapping and Reporting 27 4 Home Page Web Address xxxvi Installation and Distribution System KIDS 23 1 KIDS 23 1 Menus 7 1 Signon Auditing Files 3 29 Kernel Installation amp Distribution System Menu 23 2 KERNEL PARAMETERS File 8989 2 3 23 KERNEL SYSTEM PARAMETERS file 8989 3 15 5 KERNEL SYSTEM PARAMETERS File 8989 3 3 1 3 2 3 3 3 4 3 5 3 6 3 7 3 9 3 23 21 3 22 28 Key Management Menu 8 3 8 4 9 8 9 9 Key Word In Context K WIC 25 2 25 20 Keys Delegating 9 8 Delegation Levels 8
23. 18 16 18 17 18 18 Home Pages Acronyms Home Page Web Address Glossary 6 Adobe Web Address xxxvii Glossary Home Page Web Address Glossary 6 Health Systems Design and Development Web Address xxxvi KAAJEE Documentation 2 2 Kernel Home Page Web Address xxxvi RPC Broker Documentations 2 1 VA FileMan Documentations 3 20 5 1 5 5 VHA Software Document Library VDL Home Page Web Address xxxvii VI 2 VI 3 HOME ZIS 7 4 Host File Server 15 4 15 9 16 1 16 2 18 15 21 13 23 1 23 5 23 6 23 7 23 9 23 10 Host File Server Device Edit Option 15 6 16 2 Host Files 16 1 Cach Devices Setup 16 2 GT M Devices Setup 16 2 Host File Server Device Edit Option 16 2 System Management 16 2 User Interface 16 1 How Can the Number of Instances of a Server Option Be Controlled 11 2 How Shared Device and Terminal Type Attributes are Used 15 9 How the File Access Security Conversion Works Summary 5 12 How to Delete a Regularly Scheduled Task 22 19 July 1995 Revised June 2008 Grant File Access 5 8 Obtain Technical Information Online xxxv Requeue a Regularly Scheduled Task 22 20 Restart TaskMan when Running in a DCL Context 21 18 Use this Manual xxxul Hunt Groups Device on Another CPU 18 8 Queuing to a Hunt Group Device 18 8 System Management 18 8 TaskMan 19 4 User Interface 18 7 Using a Hunt Group Device Without Using the Hunt Group 18 9 ICD DIAGNOSIS File 80 25 1 25 2 ICD OPERAT
24. 2 These nodes describe the entire primary menu tree rather than just the single level tree Examples of the jump nodes for a single primary menu are shown in Figure 7 25 and Figure 7 26 Since these nodes can be very extensive in number some nodes have been removed from the examples to save space In the first example Figure 7 25 are the lookup nodes where the jump software tries to match a menu text or synonym with what the user has entered at the terminal Each node is set to its internal number in the OPTION file 19 and in the second piece a O if it is a synonym or a 1 if it is menu text In the second example Figure 7 26 the menu pathway entries below the P580 node show all of the options that can be jumped to from the primary menu whose internal entry number IEN is 580 Each entry contains list s of the series of options that must be navigated through in a jump from the primary menu In the case of the option DILIST 17 the list of options that will have to be processed is 520 519 518 411 17 If as in the case of ZZTEST4 318 there is more than one possible pathway then each is listed along with various other necessary pieces of information e g locks time restraint etc Figure 7 25 Jump Nodes example Lookup nodes XUTL XUTL SKRITE XUTL XUTL PRIEL OOR E E XOO BESO M194 394020 TXOO PSSO gt ZND SECOND LEVEL MENU TESIS 575d eG oll age 518 0 OO
25. 23 10 XPD MAIN 23 2 XPD PRINT BUILD 24 2 XPD PRINT CHECKSUM 23 12 XPD PRINT INSTALL 23 12 XPD PRINT INSTALL FILE 24 3 XPD PRINT PACKAGE PATCHES 24 7 XPD PURGE FILE 24 7 XPD RESTART INSTALL 23 20 XPD ROLLUP PATCHES 24 9 XPD ROUTINE UPDATE 24 10 XPD UNLOAD DISTRIBUTION 23 20 23 21 XPD UTILITY 24 1 XPD VERIFY BUILD 24 10 XPD VERIFY INTEGRITY 24 11 XQ UNREF D OPTIONS 7 8 28 1 XQ XUTL J NODES 7 12 7 13 XQAB ACTUAL OPTION USAGE 23 23 XQAB AUTO SEND 23 23 XQAB ERR DATE SITE NUM ROU ERR 23 23 XQAB ERROR LOG XMIT 23 23 Index XQAB LIST LOW USAGE OPTS 23 23 XQAB MENU 23 23 XQAL ALERT LIST FROM DATE 10 8 XQAL CRITICAL ALERT COUNT 10 8 XQAL PATIENT ALERT LIST 10 9 XQAL REPORTS MENU 10 8 XQAL SET BACKUP REVIEWER 10 10 XQAL SURROGATE FOR WHICH USERS 10 10 XQAL USER ALERTS COUNT 10 9 XQAL VIEW ALERT TRACKING ENTRY 10 9 XQALERT 2 7 XQALERT BY USER DELETE 10 7 XQALERT DELETE OLD 10 6 XQALERT MAKE 10 7 XQALERT MGR 10 6 XQALERT SURROGATE SET REMOVE 10 4 10 6 XQBUILDTREEQUE 7 13 XQCOPY OP 9 4 XQDISPLAY OPTIONS 7 5 XQHELP ASSIGN 12 5 XQHELP DEASSIGN 12 5 XQHELP DISPLAY 12 4 XQHELPFIX 12 5 XQHELP LIST 12 4 XQHELP MENU 12 4 XQHELP UPDATE 12 5 XQHELP XREF 12 5 XQKEYALTODEL 8 3 XQKEYDEL 8 3 9 8 XQLOCK1 8 3 XQLOCK2 8 3 XQOOFF 7 10 XQOOMAIN 7 10 XQOOMAKE 7 10 XQOON 7 10 7 11 XQOOREDO 7 10 XQOOSHOFIL 7 11 XQOOSHOPRO
26. 26 6 CLOSE EXECUTE TERMINAL TYPE File 3 2 14 7 15 8 18 6 18 16 18 18 CLOSE PRINTER PORT 18 16 18 18 COMMERCIAL PHONE 3 22 COORDINATOR IRM 3 17 DAY S FOR TIME PERIOD 02 7 11 DAYS FOR BACKUP REVIEWER 15 10 10 DAYS TO KEEP OLD TASKS 21 8 22 17 DEFAULT OF ATTEMPTS 3 2 DEFAULT INSTITUTION 3 6 DEFAULT LANGUAGE 3 23 DEFAULT LOCK OUT TIME 3 2 DEFAULT MULTIPLE SIGN ON 3 4 DELEGATED KEYS Multiple 8 3 8 4 9 8 DELEGATION LEVEL 8 6 DELETE ALL MAIL ACCESS 3 25 DELETE KEYS AT TERMINATION 3 25 DESCRIPTION 22 21 DESCRIPTION 3 5 OPTION File 19 11 3 DESPOOL DEVICES Multiple 17 9 DEVICE FOR QUEUED JOB OUTPUT 22 19 22 20 DIGITAL PAGER 2 9 3 23 4 1 DISABLE USER 3 24 DISPLAY OPTION 7 3 DISPLAY TEXT 02 10 10 DISUSER 3 22 3 24 3 26 DIVISION Multiple 3 6 3 21 EDIT HISTORY Multiple 28 3 ENTRY ACTION 20 7 11 11 1 11 3 ENVIRONMENT FOR DCL 21 5 21 15 EXIT ACTION 15 7 4 7 11 11 1 11 3 FAX NUMBER 3 22 FILE MANAGER ACCESS CODE 3 3 19 3 20 3 24 3 26 5 2 5 3 5 4 5 7 5 8 5 10 5 11 5 12 5 13 7 2 8 3 9 5 15 8 FILE RANGE 3 22 FORM FEED TERMINAL TYPE File 3 2 15 8 18 10 18 11 FROM UCI 21 9 FROM VOLUME SET 21 9 GLOBAL LOCK 36 18 12 HEADER 26 7 11 11 1 11 4 HELP FRAME 7 3 12 5 12 7 INDEPENDENTLY INVOCABLE 7 8 INHIBIT LOGONS 3 8 21 7 INITIAL 1 3 9 NEW PERSON File 200 2 9 3 17 3 18 4 1 INSTALL ANSWERS Multiple
27. 28 3 Edit Menu Line Editor 5 2 Edit option Menu 3 20 Edit options Option 7 2 7 3 7 8 7 11 7 13 11 3 12 7 Edit task Option 19 5 Edit TaskMan Parameters Menu 21 2 21 13 Edit User Characteristics Form and Template 3 23 Edit User Characteristics Option 2 6 2 9 2 11 3 7 3 19 3 23 Kernel 3 21 MailMan 3 21 Edit User s Spooler Access Option 17 7 Editing Device Types 15 2 Devices 15 13 Help Frames 12 6 Network Channel Devices 18 11 Resource Devices 18 14 Security Keys 8 4 Tasks 19 5 Terminal Types 15 8 Editing in Line Mode Help 28 4 Editing Routines Routine Tools 26 5 Editors AKQZ 26 5 28 3 28 5 User Interface 28 3 Line 2 10 3 20 3 21 5 2 5 5 Screen 2 6 3 5 3 20 3 21 Edits and Distribution Menu 23 2 Electronic Signature Block Edit Option 4 2 Electronic Signature code Edit Option 4 1 4 2 Index 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Electronic Signature code Option User s Toolbox 4 1 Electronic Signatures 4 1 System Management 4 2 User Interface 4 1 Enable Building Options from Templates 9 5 ENABLE XUFILE3 API 5 14 Enabling Disabling Logons 3 8 Enhanced Error Processing 13 4 Enter or Edit File Entries Option 5 4 5 6 5 7 Enter Edit Kernel Site Parameters Option 3 1 3 2 3 7 15 5 Enter Edit of Security Keys Option 8 4 Entering Option to Display Option Help 6 2 One Question Mark to List Options 6 2 Three Question Marks to D
28. 7 11 XQOOSHOW 7 11 XQOOTOG 7 10 XQOPTFIX 7 9 XQRESTRICT 7 11 XQSMD ADD 9 9 XQSMD BUILD MENU 9 4 XQSMD COPY USER 9 4 XQSMD EDIT OPTIONS 9 2 Example 9 3 XQSMD LIMITED FM OPTIONS 9 5 Kernel Systems Management Guide Index 29 Version 8 0 Index Example 9 6 XQSMD MGR 9 7 9 9 XQSMD REPLICATE 9 9 9 10 XQSMD SET PREFIX 9 5 XQSMD USER MENU 9 2 9 4 9 5 9 7 9 9 XTFCE 26 5 XTFCR 26 4 XTLKLKUP 25 1 25 5 XTLKMODKY 25 2 25 16 XTLKMODPARK 25 1 25 8 XTLKMODPARS 25 1 25 8 25 9 XTLKMODSH 25 2 XTLKMODSH 25 13 XTLKMODSY 25 2 25 17 XTLKMODUTL 25 2 25 8 25 12 XTLKPRTUTL 25 1 25 6 XTLKUSER2 25 3 XTLKUTILITIES 25 8 XTMENU 25 3 XT OPTION TEST 28 2 XTRDEL 26 8 XTRGRPE 26 5 XT ROUTINE COMPARE 26 7 XTSUMBLD CHECK Programmer Options Menu 27 3 XTV MENU Menu 27 1 27 2 XT VARIABLE CHANGER 26 5 XT VERSION NUMBER 26 6 XTVR COMPARE 27 2 XTVR UPDATE 27 2 XU BLOCK COUNT 28 1 XU CHECKSUM LOAD 26 8 XU CHECKSUM REPORT 23 12 24 11 24 12 26 6 26 7 27 4 XU DA EDIT 15 11 XU FINDUSER 3 27 XU OPTION QUEUE 22 24 XU SWITCH UCI 2 12 XU USER SIGN ON 3 7 XUAUDIT 7 4 XUAUDIT MENU 7 4 XUAUTODEACTIVATE 3 25 XUCOMMAND 7 1 7 7 7 8 XUDEVEDIT 18 10 XUDEVEDITCHAN 18 11 XUDEVEDITHES 15 6 16 2 XUDEVEDITRES 18 14 XUDEVEDITSPL 17 9 XUDEVEDITTRM 15 6 XUEDITOPT 11 3 XUERRS 13 4 XUERTRAP 13 6 XUERTRP AUTO CLEAN 13 5 XUERTRP CLEAN 13 5 XUERTRP PRINT ERRS 13 7 XU
29. 8 0 Patch Revisions For the current patch history related to this software please refer to the Patch Module on FORUM July 1995 Kernel Systems Management Guide vii Revised June 2008 Version 8 0 Revision History Vill Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Contents PREV tis LOM Fels VOI 5 Sa taks et tan eh iececue det E a capes sarees ean il BUGS AIC A Steric eastern cachet tac otra cheney owing tetas S tote ealeencte tees tectetecdene XXi Oaa e a REEE E S E ost E E A E E E E E E E nee deees XXXI L Tar GUC GO th nesse Sodan 2s e gles dp cacao ena Ma E sta bidet aa Ns sehen ES 1 1 I SISO NM SECUTI Y osia I 1 2 SIONO SCCUTILY U Ser MET ACe ar o bch GaueaasainanshcuGaaatundueensaeeaumnneacetasa reuse ieuseaeaneceass 2 1 PS NAD att ca acces a cates anen aa Redan aitanme sa neia otk cece eatena niall S 2 1 Detinmo a Strone Vernty C 0d 6 cisisksiicietihaa ints tories ata R es 2 3 BLOGIN Meni Tem plate actin aaa r e e e re a E 2 4 O 608 O a A a E a A 2 5 Normal Signo essre E T T 2 5 Abnormal Signoff and Error Handling cccccccesseesecccecccceseeseeeeeeceeeaeaeseeceeeeeeuaaaeseeees 2 6 Terminal Type Pr onpas S iene ndedeeetn naa 2 6 Escapine Troma JUMbIEd SCEE Mersinin a a baneneiadnahts 2 6 PICTUS nieni A A E ben eeagaseaee 2 7 User s PoOlbOxX MEM asso a r e a a a rE Gaangniaued nueuwas 2 7 Chang ey DIV ROrODIO Desea a a e a E 2 8 Pdt User nara teristics Oi seeiis E
30. Blank Blank 60 400 1 GENERAL PROCESSOR Blank Blank 2 Blank Yes 30 2 5 lower than Max Signons 21 10 Kernel Systems Management Guide Version 8 0 July 1995 Revised June 2008 TaskMan System Management Configuration Manager Startup You may want to configure your system so that on CPUs where the Manager should run a Manager starts up every time the CPU starts up Otherwise you will need to manually start up the Manager each time you start up those nodes that should run the Manager For most sites only one Manager is needed to cover each environment Therefore this topic focuses on starting up only a single Manager Neither the Manager nor the Submanagers will start up on a BOX VOLUME PAIR pair of the wrong type so pay attention to how you fill in the MODE OF TASKMAN field of the TASKMAN SITE PARAMETERS file 14 7 If you want the Manager to start you must make sure this field is set to either a Print Server or a General Processor Getting the Manager to start up when the system does is accomplished in the VA by the ZSTU routine in the SYS namespace This routine is provided by Enterprise Product Support EPS Multiple TaskMan Managers and Load Balancing TaskMan supports the running of multiple Manager processes but only one Manager process should run per CPU Running multiple Managers is probably useful only at large sites at a large site doing this can enable tasks to be processed more quic
31. Data entered in the I and OPEN PARAMETERS fields depends on the type of M system you are running the type of tape unit and the desired format REF For examples of the type of data required in these fields please refer to the Device Handler System Management chapter in this manual REF For further details please refer to your specific M implementation manuals 18 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues Network Channel Devices System Management Network channel devices are typically high speed channel devices e g TCP IP Currently this Network Channel Device Support exists under the Cach and GT M operating system In most cases these devices are used for specialized purposes rather than for general output For example network mail could use such devices to move enormous amounts of mail through high speed communication channels The use of network channel devices requires at least two processes on each end of the communication channel a server and a client which can then exchange information e Server Process One process must be available at all times It can be actively running or triggered to run at a given moment This process is commonly known as a server The server waits until another process makes a request to exchange information e Client Process The other process is known as the client The two processes can be hosted by two CPUs using network
32. Figure 21 13 Create system logical name for the directory with the COM files INIT QUEUE BATCH OWNER TASKMAN prot S M O D G R W S JOB 5 AUTOSTART_ON isfva2 TMSisfva2 5 Load the following DCL command files into the TASKMAN directory e GET_METRIC COM e LOGIN COM e METRIC_SCHEDULE COM e ZTM2WDCL COM e ZTMS2WDCL COM 21 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration These command files are located in the cache taskman subdirectory in the Anonymous FTP site NOTE Get the files in ASCII mode Figure 21 14 Sample user dialogue to retrieve DCL command files ISC6A2SSET DEF USERS TASKMAN ISC6A2S Etp ftp fo oakland med va gov 2470 ISCOAZ 15C SF MED VA GOV FIP Server Version 5 3 Ready Connected to FTP FO OAKLAND MED VA GOV Name FTP FO OAKLAND MED VA GOV fort anonymous 331 Guest login OK send ident as password Password XXXXXXXXXX 230 Guest login OK access restrictions apply FTP gt cd cache taskman FTP gt ls 150 Opening data connection for USRS ANONYMOUS CACHE TASKMAN GET_METRIC COM LOGIN COM METRIC _ SCHEDULE COM ZTM2WDCL COM ZIMS2WDCL COM FTP gt ascii 200 TYPE set to ASCII FTP gt get get_metric com FTP gt get login com FTP gt get metric_schedule com FTP gt get ztm2wdcl com FTP gt get ztms2wdcl com FTP gt bye 221 Goodbye NOTE Repeat for each node in the TASKMAN SITE PA
33. Figure 5 6 Enabling File Access Security Sample user dialogue ccccccccccceceeeeeeeeeeaeeeeeesssseeeeees 5 14 Figure 5 7 XUINCON conversion routine Sample user dialogue ccccccccccceeeeeeeeeeeaaeeeeeeesseeees 5 14 Figure 5 8 Running a conversion Sample user dialogue ccccccccsssssssessssseeeecccceeeeeeeeeeeeaaaaeseeseseeees 5 14 Figure 5 9 Creating a PRINT template to display file access security Sample user dialogue 5 15 Figure 6 1 One question mark help Sample user dialogue eeeeccccccceceeeseeeeeeeeeeeeeaeeeeeeeeeeeees 6 2 Figure 6 2 Using Option to get help on a named option Sample user dialogue cceeeeeeeeeeeeeeeees 6 2 Figure 6 3 Two question marks help Listing Primary Secondary and Common menu options 6 4 Figure 6 4 Three question marks help Sample user dialogue ccccseseesseeecccececeeeeeseeeeeeeeaes 6 5 Figure 6 5 Using the Up arrow Jump Sample user dialogue eeceeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeens 6 6 Figure 6 6 Listof choices Sample USer dial ou ueia era ra E A Eaa 6 6 Figure 6 7 Rubber band jump Sample user dialogue ccccccccccccccesseeseeeecceeeaaeesseseceeeeeeaaeeeeeeeeeeeas 6 6 Figure 6 8 Selecting common options via the double quote User s Toolbox menu option 6 8 Fis re 6 9 Menu Templates OPU Onscreen tia E A 6 8 Figure 6 10 Invoking a template Sample user dialo
34. GOV BECKLEY VA GOV Col gt 1 lt PF1 gt H Help PF1 gt E Exit Line gt 22 of 297 Screen gt 1 of 14 of 18 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues System Management You can set up VA FileMan s Browser as a device to which users can send their output When a user sends output to a Browser device the Browser device performs the following steps 1 Output is sent to a host file 2 When the output completes the host file is closed 3 The contents of the host file are read back into a scratch global 4 The host file is deleted 5 The Browser is called which displays the data in the global to the user through the Browser interface 6 When the user exits the Browser the scratch global is deleted This provides a quick way to generate a report and view the report through the scrollable Browser potentially saving paper and wear and tear on printers To support the Browser device you need to set up a special terminal type P BROWSER and a special device type BROWSER REF For sample entries of the special Browser terminal type and device entries for the Cach and GT M operating systems please refer to Figure 18 3 and Figure 18 4 The Browser Device tests the current terminal to see whether it supports e A scrolling region e Reverse indexing If the terminal does not support these features the Browser device issues a message saying that it 1s not selec
35. List Users Option The List Users option XUSERLIST lists all users known to the system Print Sign on Log Option The Print Sign on Log option XUSC LIST prints out the SIGN ON LOG file 3 081 Figure 3 17 Sample Kernel Sign On Log report USERS WHO HAVE SIGNED ONTO THE COMPUTER MAY 3 2006 Lb 220 PAGE 1 ELAPSED TIME Sign on time MINUTES USER NODE NAME IP ADDRESS t0 XUUSER ONE ISC6A2 oO adi 2720060 10 gt XUUSER TWO ISC6A2 Osako 472006 12 XUUSER TWO i ISC6A2 E EE A Ap ZOO As XUUSER TWO ISC6A2 TesLa LYI 27 2006 daz XUUSER TWO ISC6A2 s Ord gL Oi Zra 006 Pas XUUSER TWO ISC6A2 E AR Al Release user Option If multiple signons are prohibited problems can occur 1f users experience an abnormal exit such that the signon record cannot be cleared IRM can use the Release user option XUSERREL to remedy the problem for individual users To clear all users on startup schedule the Clear all users at startup option User Inquiry Option The User Inquiry Option option XUSERINQ displays various attributes of a specified user If the user is currently signed on it displays the job and device numbers the signon time and what option is being executed Otherwise it displays the last signon time It also displays which security keys are held by the user July 1995 Kernel Systems Management Guide 3 27 Revised June 2008 Version 8 0 Signon Security System Management User Status Report Option
36. MAX SPOOL DOCUMENTS PER USER This field limits the number of spool documents that any user can have on the system Recommended value 10 100 MAX SPOOL DOCUMENT LIFE SPAN This field controls the number of days that a spooled document will be allowed to remain in the spooler before deletion by the XU SPL PURGE option that needs to be setup to run in the background Purge old Spool documents Option Figure 17 15 Purge old spool documents option PARENT OF QUEUABLE OPTIONS ZTMQUEUABLE OPTIONS Purge old spool documents XU SPL PURGE A spool document is automatically deleted when its life span in days is reached The purge is carried out by the Purge old spool documents option XU SPL PURGE This option is listed on the PARENT OF 17 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Spooling QUEUABLE OPTIONS menu ZTMQUEUABLE OPTIONS along with others that should not be invoked interactively but should be scheduled to run through TaskMan Defining Spool Device Types The DEVICE file 3 5 entries for spooler device types make use of information about the underlying operating system s spooling mechanism Examples for several operating systems are provided below Cach and GT M Cach and GT M use an OpenVMS directory for spooling As indicated in the VistA Cookbook for VAX sites the directory should be established with full privileges for System Owner Group and World The directory spe
37. MTLU Main Menu 25 3 Navigating 6 1 Operations Management 3 26 23 23 Out Of Order Set Management 7 10 PARENT OF QUEUABLE OPTIONS 3 28 7 1 7 12 17 9 22 18 Primary 2 2 2 5 2 6 3 1 3 8 3 19 6 1 6 6 6 7 7 2 7 5 7 7 7 8 7 16 7 19 7 20 Assigning 3 8 Managing 7 7 Trees 7 13 7 15 7 19 7 20 Programmer Options 8 2 23 2 26 1 26 3 27 3 28 1 Rebuilding 7 13 Report Menu for Alerts 10 8 Routine Tools 26 1 Secondary 3 22 6 3 6 6 7 5 7 6 7 7 7 8 7 15 7 18 8 3 9 2 9 3 Assigning 7 7 Trees 7 7 7 16 Secure Menu Delegation 9 7 9 9 Secure Menu Management 9 2 9 5 Spool Management 17 7 Spooler Menu 17 3 Systems Manager Menu 7 1 23 2 27 1 Taskman Error Log 13 2 22 24 Taskman Management 13 2 TaskMan Management Menu 22 1 Taskman Management Utilities 13 2 22 7 Testing 7 9 User Management 3 24 5 1 User Management Menu 3 26 5 8 5 10 5 14 User s Toolbox 2 3 2 6 2 7 2 8 2 9 2 11 4 1 4 2 6 7 6 8 17 3 19 2 Utilities For MTLU 25 8 Utilities Menu KIDS 24 1 Utility Functions 5 6 VA FileMan 5 1 Verifier Tools 27 1 Verifier Tools Menu 27 1 27 2 XPD DISTRIBUTION MENU 23 2 XPD INSTALLATION 23 8 XPD INSTALLATION MENU 23 3 XPD MAIN 23 2 XPD UTILITY 24 1 XQAB MENU 23 23 XQAL REPORTS MENU 10 8 XQALERT MGR 10 6 XQDISPLAY OPTIONS 7 5 XQHELP MENU 12 4 XQOOMAIN 7 10 XQSMD MGR 9 7 9 9 XQSMD USER MENU 9 2 9 4 9 5 9 7 9 9
38. One time Option Queue XU OPTION QUEUE To run the One time Option Queue option XU OPTION QUEUE at a special time one day without affecting its established schedule use the One time Option Queue option It queues a task to run once without affecting the option s normal schedule in any way This lets you handle the condition where you have an option queued to run periodically and you would like to queue it once to run at an irregular time without affecting its normal periodic schedule Taskman Error Log Menu The Manager and Submanagers keep track of all errors caused by their own software or by the tasks they start They log their own errors in two places e ERROR LOG file 3 075 e Taskman Error Log Those errors caused by tasks are also recorded in the entries of the tasks themselves and can be seen with any of the various task listing options List Tasks TaskMan User etc Just as there are options to display and purge the ERROR LOG file 3 075 there are options to do the same for the Taskman Error Log When the XUTM QCLEAN option cleans tasks from the TASKS file 14 4 it also cleans any corresponding entries in the Taskman Error Log since it is hard to make sense of an error log entry without the task data Kernel strongly recommends that you report new errors to your OIFOs and follow up to ensure expeditious patching If you do this over time the number of errors occurring on your system will diminish This also
39. REF Building and rearranging menus is discussed in the Menu Manager System Management chapter in this manual SECONDARY MENU OPTIONS The SECONDARY MENU OPTIONS can be used to assign particular options to individual users to customize their menu choices While a user may have a standard primary menu to carry out the usual functions of a department or service additional special functions just for this user can be assigned as secondary options This is a multiple field unlike the PRIMARY MENU OPTION so additional items can easily be added ACCESS CODE VERIFY CODE Edit These fields can be used to edit a user s Access or Verify Code as needed If a user has forgotten the Verify code or needs a new one IRM ISO should delete the existing code so that when the user logs on and presses the lt Enter gt key at the VERIFY CODE prompt a new secret password VERIFY CODE can be entered To accomplish this Y should be entered at the Want to edit VERIFY CODE Y N prompt An at sign should then be entered to delete the existing code The change will be filed immediately unlike other changes that will be processed as part of the overall transaction when leaving the ScreenMan form Users can edit their Verify code at any time via the Edit User Characteristics option on the Common menu If this option uses a local template the ability to edit the VERIFY CODE field should probably remain as a security measure IRM can choose to add the ab
40. SZTSCH STARTUP UCI option SH when option was first queued for gt startup ZTSCH STATUS SJ of Manager SH when Manager last checked in 1 gt slacus lal description Of Status 3 SAZTSCH STOP iM SZTSCH SUB count of Submanagers waiting for tasks SSAVSCH TASK task A2 entry point 1 A3 routines 2 A4 gt option 3 A5 option name 4 C6 gt description 5 device name 6 El UCI 7 9 gt C3 creation time 8 C1 creator DUZ or C2 gt creator name 9 J of running task 10 SH gt when task actually started running 11 SZTSCH UPDATE J of Manager SH when the Manager last updated its gt parameters SZTSCH WAIT TASKS File 14 4 ZTSK holds this partially VA FileMan compatible file of tasks It is structured with a descriptor node followed by sequential entries The data dictionary for this file is 14 4 TASKS It is a read only file The TASKS file 14 4 has no cross references not even a top level B cross reference and its descriptor node is updated by the purge option XUTM QCLEAN Each entry itself contains a zero node and several decimal nodes followed by a number of storage nodes Like the SCHEDULE file the TASKS file 14 4 1s not available for direct manipulation or examination by application software Site managers however can print out information on entries in the TASKS file 14 4 using VA FileMan
41. TO RUN ON VOLUME SET field to specify the Volume Set CPU where each scheduled task should run If you leave the DEVICE FOR QUEUED JOB OUTPUT field blank the task that performs the option runs without a device or tries to If you also leave the QUEUED TO RUN ON VOLUME SET field blank the task runs on the current CPU without a device If you fill in both fields TaskMan uses the value of the QUEUED TO RUN ON VOLUME SET field unless overridden by the VOLUME SET CPU field in the DEVICE file 3 5 entry of the selected device 22 20 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation RESCHEDULE FREQUENCY Whenever a task starts running an option it looks to see what is in the RESCHEDULE FREQUENCY field If the field is blank the option does not reschedule itself If you have filled in this field the task uses the value you placed in the field to figure out when you want it to run next Then it updates the QUEUVED TO RUN AT WHAT TIME field to reflect the new scheduled time When this field is updated the next task in the sequence is scheduled If you change the existing value in the RESCHEDULE FREQUENCY field the new increment is used beginning after the next time the option runs There are several formats you can use in this field e Every n seconds e Hours e Days e months incremental e A particular day of the month e A list of times every n months
42. TaskMan Managers and Load Balancing topic in the TaskMan System Management Configuration chapter in this manual ERROR State The Manager lists itself in this state after trapping errors On some systems the process of recording an error is slow so the presence of a distinct state helps identify the source of delay to the system manager A troubleshooter who sees this state for TaskMan should immediately check the TaskMan Error list to see what kind of error is being recorded Because TaskMan s code is structured as a series of nested loops it can very easily generate thousands of errors a day under certain conditions 22 36 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation PAUSE State The PAUSE state means that some external condition is preventing the Manager from processing tasks The description always indicates the cause While in the PAUSE state the Manager waits until the problem is resolved checking once every 60 seconds The pause states are as follows Table 22 8 TaskMan PAUSE states The following required ZOSF nodes are When the Manager starts restarts or recovers from a undefined lt list of nodes gt trapped error its first order of business is to drop through some setup code that checks TaskMan s environment If any critical ZOSF nodes are missing it enters a PAUSE state and waits until the system manager restores the nodes Required link
43. UCIs on the system for TaskMan Every kind of VistA site needs one entry of this kind for each UCI to which tasks can be queued or from which tasks are created Cach sites only need to fill in the first two fields FROM UCI and FROM VOLUME SET REF For a sample configuration please refer to the Sample Configuration Standardized VA Cach and GT M Configuration topic in this chapter Entries with all four fields completed collectively build a UCI ASSOCIATION TABLE A complete UCI ASSOCIATION TABLE tells TaskMan which UCI to use for tasks that must switch Volume Sets in order to reach an I O device This situation arises when an I O device is located in a different Volume Set than the Volume Set where the task was created In such situations the Manager knows exactly where the task originated and knows to which Volume Set it must be moved but it does not know in which UCI on that Volume Set it should run the task A UCI ASSOCIATION TABLE entry supplies the missing information by linking equivalent UCIs together When building a full UCI ASSOCIATION TABLE you can omit entries where the UCIs on both Volume Sets have the same name because TaskMan assumes that same named UCIs are equivalent if no entry is present FROM UCI The FROM UCI field should be set to the name of a UCI on your system For entries requiring only two fields this catalogues all the UCIs on your system and there should be an entry for each For four field entries th
44. Want to edit VERIFY CODE Y N PREFERRED EDITOR Select DIVISION GREAT BRITAIN SERVICE SECTION INFORMATION RESOURCES MGMT Save Next Page Refresh command or followed by a caption to jump to a specific field comma i cress lt pricn for help EET SSN The SSN field 9 is not a required field in the data dictionary for the NEW PERSON file 200 SSN is required when using the User Management options to add a new user unless the XUSPF200 security key is held by the person using the option It is highly recommended that each new user have the SSN field 9 filled in to minimize the problem of subsequent duplicate entries Since many existing users do not have an SSN entered however the Edit an Existing User option does not require that one be entered MAIL CODE The user s MAIL CODE can be entered for purposes of interoffice routing of manually delivered mail PRIMARY MENU OPTION required for functional access Users must be assigned a PRIMARY MENU OPTION in order to reach Menu Manager after successfully entering Access and Verify codes 3 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management The PRIMARY MENU OPTION should provide a route to all the computing functions the user can be expected to need The XUMGR security key must be held by the person assigning the menu unless delegated options are available for use with the Secure Menu Delegation system
45. XPD INSTALLATION MENU contains the following options Figure 23 5 KIDS Installation menu options OOP WN EF Select Kernel Installation amp Distribution System Option Installation gt Locked with XUPROGMODE Load a Distribution XPD LOAD DISTRIBUTION Verify Checksums in Transport Global XPD PRINT CHECKSUM Print Transport Global XPD PRINT INSTALL Compare Transport Global to Current System XPD COMPARE TO SYSTEM Backup a Transport Global XPD BACKUP Install Package s XPD INSTALL BUILD Restart Install of Package s XPD RESTART INSTALL Unload a Distribution XPD UNLOAD DISTRIBUTION The number next to the options indicates the order of the option entries you should follow when performing a KIDS installation 23 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations Loading a Standard Distribution The first step in installing a standard distribution is to load the transport globals from the Distribution The Load a Distribution option XPD LOAD DISTRIBUTION does the following e Lists what transport globals are contained in the distribution and asks you if you want to continue e Creates entries in the INSTALL file 9 7 for each transport global in the distribution that passed its environment check e Loads transport globals from the distribution HFS file into the XTMP global if you answer YES to continue e Prompts the user to se
46. can also be entered Exit the alert processing screen MO List pending alerts in a mail message and deliver the message to your IN basket The Alert Handler ordinarily deletes alerts once you have processed the alert If you have processed all pending alerts and try to select the View Alerts VA option nothing is displayed View Alerts only offers a listing when there are pending alerts if no alerts are pending View Alerts simply returns you to the menu prompt 10 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Alerts Figure 10 2 View Alerts VA option Sample user dialogue ACCESS CODES 8 X2 VERIFY CODES xkxkx k Good evening Jim You last signed on Jan 9 2004 at 14 39 Dr You need to enter a progress note on KRNPATIENT ONE Enter VA VIEW ALERTS to review alerts Select Clinic Manager Menu Option VA Pa Dr You need to enter a progress note on KRNPATIENT ONE Poa Alk Phos elevated schedule fu bone scan 2a For your information meeting at 12 noon room 223 Select from 1 to 3 or enter A I F S P M R or to exit 2 YOU MAY ENTER One or more numbers in the range 1 to 3 to select specific alert s for processing This may be a series of numbers e g 2 3 6 9 to process all of the pending alerts in the order shown to process all of the INFORMATION ONLY alerts if any without further ado to add or remove a surrogate to receive alerts for you to forward one or more
47. can be restricted This flag does not affect the choice of devices used for the output from options It instead controls the processing involved in the use of the option itself QUEUING REQUIRED Flag Using the option Edit options you can allow users to invoke an option but force any output to be queued outside of certain times of day by editing the option s QUEUING REQUIRED field Multiple In this multiple s TIME PERIOD 01 and DAY S FOR TIME PERIOD 02 fields enter the time periods and days in which you do not want the option s output to be produced During these time periods the output of the options can only be queued When a user requests a time for queuing the menu system will determine the next permissible day and time for output Thus users can July 1995 Kernel Systems Management Guide 7 11 Revised June 2008 Version 8 0 Menu Manager System Management invoke the option and use it to define the parameters for the subsequent processing but the actual work will be done during a later time period presumably when the system is less busy Menu Manager Options that Should Be Scheduled This topic describes the two Menu Manager options that should be regularly scheduled Kernel exports a number of other options that should be scheduled to run at regular intervals Most of these are located on the PARENT OF QUEUABLE OPTIONS menu REF For a complete list along with suggested scheduling frequencies please refer to the Kernel
48. chapter in this manual Most of the lists in the SCHEDULE file describe tasks as follows e Schedule List Sorts all scheduled tasks by time according to when they are supposed to begin running e Waiting List Stores each task whose running was delayed because its I O device was busy e Job List Holds those tasks that can begin running immediately e Link List Stores tasks whose running is delayed because of a dropped link to another Volume Set e Task List Describes all actively running tasks e Compute Server Job List Describes all tasks waiting to start on a Compute Server cross CPU queuing The role of tracking the status of TaskMan itself is split between lists of information and individual nodes and flags The Status List is where the Manager keeps track of its current condition it is a list because IRM may choose to run more than one Manager in the same TaskMan environment The RUN Node is a place where TaskMan stamps the current time this node reveals when TaskMan stops running The Taskman Error Log is a simple list in which TaskMan stores each error that occurs either within TaskMan itself or within the tasks that it runs The Error Screens are screens that can be established by IRM to prevent the recording of certain errors 20 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Overview These lists and nodes as well as others not described here are t
49. is present Managers will not start new Submanagers Submanagers waiting for tasks quit immediately and those currently running tasks quit as soon as the tasks finish A ZTSCH SUB This node counts the number of Submanagers waiting for new tasks It is updated regularly by Submanagers as they run tasks The Manager uses this value to decide whether to JOB out new Submanagers and adjusts its value during the idle loop whenever it believes it to be inaccurate AMZTSCH TASK task This node holds the tasks TaskMan believes are currently running Since entries are cleaned up when tasks quit or encounter errors those that are forcibly exited by the system manager are left on the list even though they are not running The Manager clears the list whenever the system starts up and the system manager can manually remove inaccurate entries by using the exit action of the KILL off a users job option XURESJOB The task data stored at each node allows TaskMan to list the tasks even when they clean out their TASKS file 14 4 records when they start instead of when they quit A ZTSCH UPDATE J of Manager This node records when the Manager last updated its local information about the site parameters This node is KILLed whenever the Manager should update e g site parameters are changed AZT SCH WAIT This node puts the Manager into a WAIT state July 1995 Kernel Systems Management Guide 22 29 Revised June 2008 Version 8
50. or hardware specific code is isolated to Kernel Therefore porting VistA to a new environment requires modification only to a handful of Kernel routines As a whole Kernel provides a computing environment that permits controlled user access presents menus for choosing from various computing activities allows device selection for output enables the tasking of background processes and offers numerous tools for system management and application programming Kernel also provides tools for software distribution and installation VistA users see the same user interface regardless of the underlying system architecture because VistA applications are built using Kernel facilities for signon database access option selection and device selection As a result user interaction with the system is constant across VistA applications User Introduction Kernel provides the doorway into the VistA computer system the menus that tie together the options and utilities to enhance those options For the doorway Kernel provides the Access and Verify code system that you use to establish your identity to the VistA computer system Once you have signed on Kernel provides your menus Each user on the computer system as identified by their Access code has their own individual set of menus and options The person or department managing the computer system organizes each user s menus From your menu you can run any application the computer system managers
51. or invoke the menu system s Up arrow Jump feature as a shortcut To jump to an option enter a caret before the option specification the option s menu text or synonym in upper or lowercase letters You only need to enter the first few characters needed to July 1995 Kernel Systems Management Guide 6 5 Revised June 2008 Version 8 0 Menu Manager User Interface uniquely identify the option You can use the option s synonym to limit ambiguity especially if the synonym is distinct from other synonyms or menu texts Figure 6 5 Using the Up arrow Jump Sample user dialogue Select Systems Manager Menu Option INTRO lt Enter gt ductory text edit The menu system carries out the necessary footwork to reach the desired option If along the way there are pathway restrictions e g locks or prohibited times access to the option will be denied just as when stepping to an option If a match is found within the primary or secondary menus that option is executed the menu system will not search the Common menu if it can find a match in the primary or secondary menus If the menu system finds more than one matching option on either the primary secondary or Common menu tree the menu system presents a list of matching choices Entering a caret followed by a question mark will display all of the options available to you Figure 6 6 List of choices Sample user dialogue Select Systems Manager Menu Option Lis
52. this status has a different meaning Stopped irregularly while waiting for a partition on a Compute Server L Preparing this task caused the Submanager an error lt date and time gt lt error msg gt The Submanager uses this status when it traps an error after claiming a task but 22 34 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Task Rejection Messages Under certain conditions TaskMan can avoid trapping obvious errors by checking the tasks themselves for internal consistency Whenever it finds tasks with bad data it reyects them This involves unscheduling them setting their status codes to B and adding a brief explanatory message These messages can help identify bugs in application queuing software in the local system configuration or in TaskMan itself Table 22 7 TaskMan rejection messages BAD DESTINATION UCI The Manager rejects a task for this reason under three different conditions e If the task is bound for the Manager s own Volume Set whatever value has been passed for the destination UCI must be a valid UCI on the current Volume Set If A ZOSF UCICHECK rejects the UCI TaskMan rejects the task If the task is bound for a different Volume Set and the destination UCI is not listed in the UCI ASSOCIATION file 14 6 under that Volume Set the UCI must be accepted as a valid UCI on the current Volume Set so TaskMan can use File 14 6 to det
53. using the Edit User Characteristics option available through the User s Toolbox menu discussed below The Edit User Characteristics option lets you edit a setting ASK DEVICE TYPE AT SIGN ON that allows you to decide whether to bypass the usual terminal type query If you always work at the same terminal and want to save a small amount of time during the signon process you can set ASK DEVICE TYPE AT SIGN ON to DON T ASK Kernel then assumes that your last terminal type should be used as the default If you have ASK DEVICE TYPE AT SIGN ON set to DON T ASK and sign on using a terminal whose terminal type is different from the one normally used you should signon by including a colon after your Access code This forces Kernel to query the terminal for its identity Alternatively once signed on you could invoke the Edit User Characteristics option to change your terminal type to the one currently in use Or you could use this option to reset the ASK DEVICE TYPE AT SIGN ON question to ASK log off and sign back on whereby Signon Security will obtain the correct terminal type identification Escaping from a Jumbled Screen One consequence of your signon terminal type not matching the actual one being used is that full screen display could appear jumbled To escape from a ScreenMan form e g Edit User Characteristics all you need to do is enter two carets each followed by the lt Enter gt key To escape from VA FileMan s Screen E
54. 0 TaskMan System Management Operation Figure 22 28 ZTSCH Global Structure SZTSCH SZTSCH next run time task SZTSCH next run time task D1 device IOP value AZTSCH C volume set count SEZTSCH C volume set next run time task device SIO SZTSCH DEV device IO H when device was allocated for a specific gt task Si oGH ERY A1 or ee SZTSCH ER SH when error happened error message SZTSCH ER SH when error happened 0 context of error ATSCH ES error screen 0 s ATSCH ES error screen 1 screened errors count SZTSCH IDLE H when the Manager s idle loop checks were last performed SZTSCH IO SH when device waiting list was last checked without finding gt an available device SIO of last device tried IO device 10 device type TO device SIO run time task JOB run time task device SIO LINK or SH when dropped link was last checked LINK volume set 1 if link has dropped LINK volume set next run time task LOAD load rating cpu SH when rating was checked LOADA cpu whether TM should wait load rating SH gt when rating was checked J of Manager 6 a LEG EL els Cs Gg La OOF SAP oCH So Li eT SIA OL goes Gi SGiOoCH Se AvoGH t hOGRSRG EM SLILSCH NO OPTION S ZTSCH RUN SH when Manager last checked in
55. 1 Figure 8 2 Figure 8 3 Figure 8 4 Figure 8 5 Figure 8 6 Figure 9 1 Figure 9 2 Figure 9 3 Figure 9 4 Figure 10 1 Figure 10 2 Figure 10 3 Figure 10 4 Figure 11 1 Figure 11 2 Figure 12 1 Figure 12 2 Figure 12 3 Figure 12 4 Figure 12 5 Figure 12 6 Figure 12 7 July 1995 Display User Characteristics option Sample Output ccccccccsssssseccececeeeeesesecceeeeeseaeeeeeeees 8 1 Diagram Menus option Sample user dialogue osseeeeeeessessssssssssseetteereereeessssssssssseeeeeeeee 8 2 Key Minacement Nent Opon aseri a e mosh ianaahe dest icosatenss 8 2 Attributes for the Provider security key Sample user dialogue ccccsseseeeeeeeeeeeeeeeeees 8 4 Remdex the Users keys Opioaren a e e teh sieWeatandiscubuatease 8 5 Delegate s Menu Management Option sccis crne e shana vocab dn ivan ne wi an aa eais 9 2 Edit a User s Options Sample user dialogue eecccccccccccessseesecccceecaeessseeeceeeeeeaaaeeeeeeees 9 3 Limited File Manager Options Build Sample user dialogue 2 00 0 ceeececcceeeeeeseeeeeeeeeeeees 9 6 Delegating Options Select Options to be Delegated option Sample user dialogue 9 8 Aler o AMIPle SEP ANESS ASC i a a ash acnabenettseniaiss 10 1 View Alerts VA option Sample user dialogue cccccccccssssesseccccceeeseeseeeeeeeeeeaaesseeees 10 3 Alert Management Menu Options cccccssessssseecccccneeessseeccccesseeessseececcessaees
56. 1 Virtual Terminals 15 10 Device Management Menu 15 2 15 12 Device Waiting List Node 22 28 Devices BROWSER 18 1 18 3 Cross references 15 12 15 13 15 14 Editing 15 13 File Entries 18 16 HES 15 4 15 6 15 9 16 1 16 2 18 15 21 13 23 1 23 5 23 6 23 7 23 9 23 10 Home 14 1 14 3 15 10 18 16 18 17 18 18 Hunt Groups Device on Another CPU 18 8 15 10 15 13 Identification 15 12 SUBTYPE Field 15 1 15 2 15 4 15 8 18 IO List 22 10 10 18 11 Magtape 18 10 Index 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Network Channel 18 11 NULL 15 6 Printing 14 1 Queuing to a Hunt Group Device 18 8 RESOURCES Type 11 2 SDP 18 15 Security 15 7 Sequential Disk Processor SDP 15 9 18 15 Signon 15 10 Slaved 18 15 Special Device Issues 18 1 SPOOLER 17 1 Synonyms 15 12 Using a Hunt Group Device Without Using the Hunt Group 18 9 VMS Systems Virtual Devices 15 10 DI DDU Menu 5 6 Diagram Menus Option 8 2 8 5 Diagramming Options 7 5 DIAUDIT DD Option 5 5 DIAUDIT PURGE DATA Option 5 5 DIAUDIT PURGE DD Option 5 5 DIAUDIT TURN ON OFF Option 5 5 DIAUDITED FIELDS Option 5 5 DIC API 5 5 DIC Routine 5 3 DIDEL Variable 5 3 5 5 DIE API 5 4 5 5 DIE Routine 5 3 DIEDFILE Option 5 11 DIEDIT Option 5 4 5 6 5 7 DIFROM Utility 23 1 23 4 23 6 DIGITAL PAGER Field 2 9 3 23 4 1 DIINQUIRE Option 5 6 5 8 DILIST Option 5 6 DIMODIFY Option 5 6 5 8 DIP Routi
57. 16 23 17 INSTALL CHECK MESSAGE PackMan 23 7 23 9 Installation KIDS 23 3 23 8 23 16 Interactive Print of Error Messages 13 7 Introductory text edit 3 1 Invoking Non VistA Applications 7 4 Kernel 7 1 Kernel Installation amp Distribution System 23 2 Key Management 8 3 8 4 9 8 9 9 Keys For a Given Menu Tree 8 3 Keyword Multi Term Look Up MTLU Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Example 25 19 Keywords Multi Term Look Up MTLU 25 2 25 16 KIDS 23 2 KILL off a users job 22 10 22 29 Limited File Manager Options Build 9 5 9 11 Example 9 6 List Alerts for a user from a specified date 10 8 List Delegated Options and their Users 9 11 List Error Screens 13 3 List File Attributes xxxv 5 6 List Global 28 1 List Help Frames 12 4 12 7 List of tasks 22 3 List Options by Parents and Use 7 5 List own tasks 19 5 List Routines 26 6 List Tasks 22 2 22 5 22 11 22 12 22 32 All your tasks 22 3 Future tasks 22 4 List of tasks 22 3 Running tasks 22 4 Tasks waiting for a device 22 4 Unsuccessful tasks 22 4 Your future tasks 22 3 List the Defined Options Sets 7 11 List Users 3 27 Load a Distribution 23 5 23 7 23 9 23 10 23 21 Load refresh checksum values into ROUTINE file 26 8 Locked Identifying 8 2 Locks 7 7 7 11 Loopback Test of Device Port 15 12 Low Usage of Alpha Beta Test Options 23 23 Make an
58. 18 11 Network Channel Device Edit option Sample output EDIT A NETWORK CHANNEL DEVICE SDD DIRECT PAGE 1 OF 1 NAME SDD DIRECT LOCATION OF TERMINAL HP 8000 near Raul I TCP 9100 VOLUME SET CPU TYPE NETWORK CHANNEL SIGN ON SYSTEM DEVICE NO SUBTYPE P HP8000 TCP S MARGIN WIDTH PAGE LENGTH ASK DEVICE NO USE TIMEOUT ON OPENS ASK PARAMETERS NO OPEN TIMEOUT OPEN PARAMETERS 10 6 21 138 9100 M USE LOCK The GLOBAL LOCK field 3 5 in the DEVICE file 3 5 stores a YES NO Set of Codes This is important especially if the application expects that only one client at a given time is able to open the device If this field is set to YES an M lock on ZIS lock IO will be obtained before the device is opened It will remain until a call to ZISC to close the device It can be used with any type of device 18 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues Resources System Management A resource is a type of device that can only be used by tasks They cannot be used for input or output I O As such they are not available for user selection at the device prompt The purpose of a resource is to provide a mechanism of limiting the number of concurrent jobs that can run at any one time When creating a task a task can request the resource as an input variable for the ZTLOAD call The resource itself as defined in the DEVICE file 3 5 has a field calle
59. 23 16 Actual Usage of Alpha Beta Test Options Option 23 23 Add a New User Option 3 9 Add a New User to the System Option 3 9 Add Entries To Look Up File Option 25 8 25 9 Example 25 12 Multi Term Look Up MTLU 25 1 Add Error Screens Option 13 3 Add Modify Utility Option 25 8 25 12 Multi Term Lookup MTLU 25 2 Multi Term Look Up MTLU Examples 25 18 Adding Explicit File Access for IRM 5 11 Adding New Users 3 8 Add a New User to the System Option 3 9 July 1995 Kernel Systems Management Guide Index 1 Revised June 2008 Version 8 0 Index Grant Access by Profile 3 9 Grant Access by Profile Option 3 9 NEW PERSON IDENTIFIERS 3 9 Primary Menu 3 8 Security Forms 3 9 3 10 SSN Field 9 NEW PERSON File 200 3 9 XUMGER Security Key 3 8 3 9 XUSPF200 Security Key 3 9 Additional Attributes Editable by Users 3 23 After the Conversion File Access Security 5 15 AGENCY Field 3 6 AGENCY File 4 11 3 6 AHG Cross references 18 8 AK Cross reference 8 4 ALERT DATE TIME Multiple Field 01 10 10 ALERT File 8992 10 5 10 6 10 7 10 8 10 9 10 10 Alert Management Menu 10 4 10 6 ALERT TRACKING File 8992 1 10 3 10 5 10 6 10 7 10 8 10 9 Alerts 2 7 10 1 Deleting 10 3 Forwarding 10 4 Make an Alert on the Fly Option 10 7 Processing 10 1 Purging 10 6 10 7 Reports 10 8 10 9 10 10 Surrogates 10 4 10 6 System Management 10 5 User Interface 10 1 Alerts Set Remove Surrogate f
60. 23 17 INTERACTIVE USER S PRIORITY 3 5 INTRO TEXT 3 1 3 7 INVOKED BY ROUTINE 12 5 KEEP AT TERMINATE 8 4 KEYS Multiple 8 2 8 3 9 4 LANGUAGE 3 23 LAT PORT SPEED 64 15 7 LAT SERVER NODE 61 15 7 LAT SERVER PORT 62 15 7 LIFETIME OF VERIFY CODE 3 6 LINK ACCESS 21 7 LOAD BALANCE ROUTINE 21 5 21 12 LOCAL SYNONYM 15 12 LOCK 3 8 2 8 5 11 1 11 3 LOG RESOURCE USAGE 22 28 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 July 1995 Revised June 2008 LOG TASKS 21 3 MAIL CODE 3 18 MARGIN WIDTH 18 10 18 11 MAX SIGNON ALLOWED 3 1 3 3 21 3 MAX SPOOL DOCUMENT LIFE SPAN 17 8 MAX SPOOL DOCUMENTS PER USER Field 17 8 MAX SPOOL LINES PER USER Field 17 8 MENU item Multiple 7 1 MENU TEMPLATE Multiple 6 9 MENU TEXT 1 11 3 MESSAGES 23 17 23 20 Mixed OS Environment DEVICE File 3 5 15 5 MNEMONIC 15 12 MODE OF TASKMAN 21 4 21 7 21 11 MULTIPLE SIGN ON 3 21 NAME 01 BUILD File 9 6 23 4 DEVICE File 3 5 15 2 15 12 NEW PERSON File 200 3 17 4 2 OPTION File 19 7 3 11 3 PARAMETER DEFINITION file 8989 51 10 10 RESOURCES File 3 54 18 13 SECURITY KEY File 19 1 8 5 TERMINAL TYPE File 3 2 15 8 NEW PERSON IDENTIFIERS 3 9 NICK NAME 2 9 3 18 OFFICE PHONE 2 9 3 22 4 1 OPEN EXECUTE TERMINAL TYPE File 3 2 14 7 15 8 18 16 18 17 OPEN PARAMETERS DEVICE File 3 5 15 4 15 9 16 2 17 9 18 3 18 10 18 11 OPEN PRINTER PO
61. 23 7 LOCAL KEYWORD File 8984 1 VI 1 25 1 25 2 25 3 25 8 25 9 25 12 LOCAL LOOKUP File 8984 4 VI 1 25 1 25 2 25 5 25 6 25 8 25 9 25 12 25 22 Index 20 Kernel Systems Management Guide Version 8 0 LOCAL SHORTCUT File 8984 2 VI 1 25 1 25 2 25 3 25 5 25 8 25 9 LOCAL SYNONYM Field 15 12 LOCAL SYNONYM File 8984 3 VI 1 25 1 25 2 25 3 25 8 25 12 LOCK Field 3 8 2 8 5 11 1 11 3 Locked Options Identifying 8 2 Lock out Times 3 2 Locks Negative 7 11 Options 7 7 7 11 Reverse 7 11 8 3 8 5 LOG RESOURCE USAGE Field 22 28 Log Resources Node 22 28 LOG TASKS Field 21 3 LOGIN Menu Template 2 4 6 9 Logon 2 1 Logs Add Error Screens Option 13 3 AUDIT LOG FOR OPTIONS File 419 081 7 4 11 1 11 4 Clean Error Log Over Range Of Dates Option 22 25 Clean Error Trap Option 13 5 Delete Error Log Option 22 26 Edit Error Screens Option 13 3 Error Log 13 7 27 4 ERROR LOG File 3 075 13 2 13 5 22 24 Error Log Node 22 27 Error Log Purge 13 5 FAILED ACCESS ATTEMPTS LOG File 3 05 3 28 3 29 List Error Screens Option 13 3 LOG RESOURCE USAGE Field 22 28 Log Resources Node 22 28 LOG TASKS Field 21 3 Old Access Codes Stored in the Whole file AOLD Cross reference in File 200 3 29 Old Verify Codes Stored in the Whole file VOLD Cross reference in File 200 3 29 Purge Error Log Of Type Of Error Option 22 26 Queuable Task Log Clean Up Option 22 17 Remove Error Screens Opti
62. 25 11 1 11 3 11 9 SCHEDULING RECOMMENDED 209 7 4 22 19 22 22 SE TIMEOUT ON OPENS 18 11 SECONDARY I 52 15 6 SECONDARY MENU OPTIONS Multiple 3 19 3 22 7 7 7 18 9 4 Kernel Systems Management Guide Index 11 Version 8 0 Index SECURITY 3 2 3 20 15 7 15 8 SELECTABLE AT SIGN ON TERMINAL TYPE File 3 2 3 6 15 8 15 11 SERVER ACTION 221 11 2 11 3 11 4 11 5 SERVER AUDIT 223 11 4 SERVER BULLETIN 220 11 4 SERVER DEVICE 227 11 2 11 5 SERVER MAIL GROUP 222 11 4 SERVER REPLY 225 11 5 SERVICE SECTION 3 17 3 21 SEX 4 NEW PERSON File 200 3 9 SIGNATURE BLOCK PRINTED NAME 4 1 4 2 SIGNATURE BLOCK TITLE 4 1 SIGN ON SYSTEM DEVICE DEVICE File 3 5 15 4 15 10 15 13 SLAVE FROM DEVICE 18 18 SPECIAL QUEUEING 22 19 SPECIAL QUEUEING 9 22 22 SSN PATIENT File 2 5 8 SSN 9 NEW PERSON File 200 3 9 3 18 START NEXT 22 16 STATUS 23 19 SUBMANAGER RETENTION TIME 21 3 21 4 SUBORDINATE KEY Multiple 8 4 SUBTYPE DEVICE File 3 5 15 1 15 2 15 4 15 TIED ROUTINE 3 1 TIME PERIOD 01 7 11 TIMED READ 3 7 3 21 TIMES DAYS PROHIBITED 3 91 Multiple 11 2 11 3 TITLE 3 18 TO UCI 21 9 TO VOLUME SET 21 9 TRANSPORT BUILD NUMBER 63 23 12 24 12 26 7 TYPE DEVICE File 3 5 15 2 15 3 21 13 VOLUME SET File 14 5 21 7 TYPE 4 OPTION File 19 11 3 TYPE AHEAD 2 10 3 7 3 22 UCI ASSOCIATION TABLE 21 9 USE PARAMETERS DEVICE File
63. 25 19 Figure 25 20 VA FielMan Utility Functions option Sample user entries ccceececeeeeeeeeeeseeeeeeees 25 20 Figure 25 21 Add Entries To Look Up File Sample user entries ccccccceeeeeeeeeeeeeeeeeeeeeeeeeees 25 21 Figure 25 22 VA FileMan Edit File option Sample user entries ccccceceecececeeeeeeeeeeeaaeaeeeeeees 25 22 Figure 26 1 Routine Tools MENUOPMONS scenen treen a E OAE 26 1 Figure 26 2 XINDEX Imdex of Routines option direct mode utilities sample user entries 26 3 Figure 26 3 XINDEX List of the error conditions that the XINDEX utility flags ce eeeeeeeeeees 26 4 Pigure 2 1 Vernier Took Ment Opon eissegar ae teem baowacasanes 21 2 Figure 27 2 Programmer Options menu options Toolkit verifaction tools eseeesesseeeserereeererrerrerrrreee 27 3 Figure 28 1 Programmer Options menu options Toolkit miscellaneous tools 2 0 0 eeeeeeeeeeeeeeeeeees 28 1 Figure 28 2 Calling the Z Editor Sample user entries csseeeeeseeeeeececcccceeeeeaaaeaeseeeeeeeeeeeeess 28 3 Figure 28 3 Z Editor Displaying a routine using the ZP command ee ccceeeeneeteeeeeeeeeeeeeeeees 28 3 Figure 28 4 Z Editor Listing edit commands seresa AE A EE EAE E 28 4 Figure 28 5 Z Editor Line mode help information eeeeeeeesereseeeeeeeeeeeeeseseeeeeeeeeeeeeeeeeeeeeeeseseees 28 4 Figure 28 6 Z Editor Replace mode editing help information
64. 28 SPOOL DATA 3 519 17 6 SPOOL DOCUMENT 3 51 14 6 15 9 17 6 17 10 TaskMan 20 5 TASKMAN ERROR 22 11 TASKMAN SITE PARAMETERS 14 7 3 3 20 5 20 7 21 1 21 2 21 7 21 10 21 11 21 12 21 17 22 9 BOX VOLUME PAIR Field 21 3 ENVIRONMENT FOR DCL Field 21 5 Load Balance Routine 21 12 LOAD BALANCE ROUTINE Field 21 5 LOG TASKS Field 21 3 MODE OF TASKMAN Field 21 4 Standardized VA Cach and GT M Configuration 21 10 SUBMANAGER RETENTION TIME Field 21 3 21 4 TASK PARTITION SIZE Field 21 3 TASKMAN HANG BETWEEN NEW JOBS Field 21 4 TASKMAN JOB LIMIT Field 21 3 TASKS 14 4 19 4 20 1 20 2 20 3 20 5 20 7 21 1 21 2 21 4 22 2 22 3 22 4 22 6 22 17 22 19 22 24 22 25 22 27 22 29 22 30 22 31 22 34 22 36 TERMINAL TYPE 3 2 3 5 3 6 14 4 15 1 15 8 15 9 15 11 18 6 18 16 BACK SPACE Field 15 8 18 10 18 11 CLOSE EXECUTE Field 14 7 15 8 18 6 18 16 18 18 FORM FEED Field 15 8 18 10 18 11 Global Location 15 1 NAME Field 01 15 8 Naming Conventions 15 9 OPEN EXECUTE Field 14 7 15 8 18 16 18 17 PAGE LENGTH Field 15 8 18 10 18 11 RIGHT MARGIN Field 15 8 SELECTABLE AT SIGN ON Field 3 6 15 8 15 11 Terminal Type File Entries 18 16 TITLE 3 1 3 18 Transfer Entries 5 6 5 7 Transfer File Entries 5 7 5 7 UCI ASSOCIATION 14 6 20 5 20 7 21 1 21 8 22 35 FROM UCI Field 21 9 FROM VOLUME SET Field 21 9 Standardized VA Cach and GT M Configuration 21 10
65. 3 8 6 9 3 9 9 Exported 8 5 Management Security Keys 8 2 Provider 3 25 8 3 8 4 KEYS Field Multiple 8 2 8 3 9 4 Keys For a Given Menu Tree Option 8 3 Keyword Option Multi Term Look Up MTLU Example 25 19 Keywords Help Frames 12 7 Multi Term Look Up MTLU 25 1 25 12 Associated with a Single Term and Multiple Terms 25 2 Keywords Option Multi Term Look Up MTLU 25 2 25 16 KIDS 23 21 24 4 24 10 Aborted Installations 23 20 Recovering From 23 20 Alpha Beta Tracking 23 23 Answering Installation Questions for Transport Globals in a Distribution 23 7 Backup a Transport Global Option 23 15 Build Entry Definition 23 1 BUILD File 9 6 23 4 Build File Print Option 24 2 Changes in the Role of the PACKAGE File 9 4 23 5 Checkpoints 23 20 Checksums 23 7 23 12 24 9 24 11 Comparing Loaded Transport Globals to the Current System 23 13 Components 23 12 Definition 23 1 Convert Loaded Package for Redistribution Option 24 4 Definitions 23 1 Deleting Security Keys 8 5 Display Patches for a Package Option 24 7 Distributions 23 2 Definition 23 1 Global 23 6 23 21 Split Across Diskettes 23 10 Standard 23 6 Transport Mechanism 23 5 Environment Check 23 7 23 9 Exported Components 23 12 Files 23 4 Global Distributions 23 6 23 7 Information Stored in the INSTALL File 9 7 23 17 INSTALL File 9 7 23 4 Information 23 17 Install File Print Option 24 3 Installations 22 28 23 2 2
66. 3 17 Edit Devices by Specific Types 18 10 Edit Error Screens 13 3 Edit File 5 11 Edit Line Editor 5 2 Edit options 3 20 7 2 7 3 7 8 7 11 7 13 11 3 12 7 Edit task 19 5 Edit TaskMan Parameters 21 2 21 13 Edit User Characteristics 2 6 2 9 2 11 3 7 3 19 3 23 Kernel 3 21 MailMan 3 21 Edit User s Spooler Access 17 7 Edits and Distribution 23 2 Electronic Signature Block Edit 4 2 Electronic Signature code Edit 4 1 4 2 Enter or Edit File Entries 5 4 5 6 5 7 Enter Edit Kernel Site Parameters 3 1 3 2 3 7 15 5 Enter Edit of Security Keys 8 4 Error Processing 13 4 Error Trap Auto Clean 13 5 Error Trap Display Option 13 6 Errors Logged in Alpha Beta Test QUEUED 23 23 Establish System Audit Parameters 7 4 EVE 7 1 7 17 7 18 9 10 13 2 23 2 Exported 7 1 Fields Being Audited 5 5 File Access Security 5 8 5 9 5 10 5 13 5 14 5 15 FileMan edit template 11 3 FileMan Inquire to File Entries option 25 2 Find a User 3 27 Fix Help Frame File Pointers 12 5 Fix Option File Pointers 7 9 Flow Chart Entire Routine 26 4 Flow Chart from Entry Point 26 5 Future tasks 22 4 Global Block Count 28 1 Grant Access by Profile 3 9 3 21 Group Routine Edit 26 5 Halt 6 7 Help Processor 12 4 Host File Server Device Edit 15 6 16 2 Input Routines 26 8 Inquire 7 6 Inquire to File Entries 5 6 5 8 Install File Print 23 17 23 19 24 3 Install Package s 23 7 23
67. 5 23 4 24 9 24 11 Transport Global 23 8 Compute Server Job List 20 6 22 10 22 34 Node 22 27 Mode 21 4 COMPUTE SERVER Type 21 7 Computer Access Policy 3 10 Computer Account Notification 3 10 Configuration Multiple Managers TaskMan 21 11 TaskMan 21 1 Cach and GT M 21 10 Contents 1x Continue Option 6 7 Control How Can the Number of Instances of a Server Option Be Controlled 11 2 Conversion After File Access Security 5 15 File Access Security 5 10 Convert Loaded Package for Redistribution Option 23 5 24 4 COORDINATOR IRM Field 3 17 Copy Everything About an Option to a New Option Option 9 4 9 11 Copy One Users Menus and Keys to others Option 9 4 Copy Print Mode 18 15 CPT File 81 25 1 CPU Cross references 15 2 15 3 15 4 21 2 Definition 20 8 CPU Service User Device Stats Option 3 21 3 28 Create a Set of Options to Mark Out Of Order Option 7 10 Creating Another Level of Delegation 9 1 Delegates 9 7 Device Types 15 2 Distributions 23 2 Help Frames 12 6 Menus and Options 7 2 New User Account 3 8 Index 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Options and Menus 7 2 Resource Devices 18 14 Security Keys 8 4 Several Dummy Users 3 10 Spooled Document 17 6 Tasks 18 13 TaskMan User Interface 19 1 Terminal Types 15 8 Transport Globals 24 10 24 11 Critical Alerts Count Report Option 10 8 Cross Reference Help Frames Option 12
68. 5 Cross references XUSEC 8 5 AHG 18 8 AK 8 4 AOLD 3 29 B 18 8 22 30 CPU 15 2 15 3 15 4 21 2 CUR 3 27 Devices 15 12 15 13 15 14 Errors 22 25 Lookup type 3 17 3 18 Options 12 5 Parents 12 5 Routines 12 5 VOLD 3 29 CUR Cross reference 3 27 D DA Return Code Edit Option 3 5 15 11 DA RETURN CODES File 3 22 3 5 15 11 Global Location 15 1 Dangling Pointers OPTION File 19 7 9 Data Dictionaries Being Audited Option 5 5 Data Dictionary Data Dictionary Utilities Menu xxxv Listings xxxv DATA DICTIONARY Access 5 1 5 4 5 5 5 7 5 8 5 13 Data Dictionary Utilities Menu 5 6 DAY S FOR TIME PERIOD Field 02 7 11 DAYS FOR BACKUP REVIEWER Field 15 10 10 DAYS TO KEEP OLD TASKS Field 21 8 22 17 DCL Command Files 21 5 21 15 DCL Commands SET LOGINS INTERACTIVE 3 3 DCL Context Index Batch Queues 21 20 Restarting 21 18 Running TaskMan with a DCL Context 21 14 Set up for TaskMan and DCL Context in Cache VMS 21 15 TASKMAN Account 21 20 TaskMan Cache VMS 21 15 TASKMAN Queue 21 20 ZTMSWDCL COM 21 19 ZTMWDCL COM 21 18 Deactivate a User Option 3 24 3 25 Deactivating Users 3 24 Automatically 3 25 De allocating Security Keys 8 3 De allocation of Security Keys Option 8 3 9 9 De assigning Help Frame Editors 12 5 DEFAULT OF ATTEMPTS Field 3 2 Default Institution 3 21 DEFAULT INSTITUTION Field 3 6 DEFAULT LANGUAGE Field 3 23 DEFAULT
69. 7 Export 23 2 Install 23 3 Load from Distribution 23 3 23 7 23 9 Load from PackMan Messages 23 3 23 7 Print 23 3 23 7 23 12 Processing 23 16 Verify 24 10 Verifying Checksums 23 12 Transport Mechanism Distributions 23 5 Index Update Routine File Option 24 10 Verify a Build Option 24 10 Verify Package Integrity Option 24 11 Verifying Checksums in a Transport Global 23 12 Versions to Retain 24 8 When the Distribution is Split Across Diskettes 23 10 When the Installation 1s Queued 23 17 KILL ADISV Global 5 11 5 13 TMP Global 7 12 AUTILITY J Global 7 12 XTMP Global INSTALL File 9 7 Entries and Transport Globals 23 7 Device Allocation List Node 22 27 IO Variables 7 4 Jobs 22 10 Signon Nodes 7 13 Software wide Variables 7 8 Subscript J or Namespace J in the AUTILITY J or TMP Global 7 13 TaskMan Process 22 16 Tasks 22 10 Update Node 22 29 KILL off a users job Option 22 10 22 29 KWIC 25 2 25 20 L LANGUAGE Field 3 23 LAT PORT SPEED Field 64 15 7 LAT SERVER NODE Field 61 15 7 LAT SERVER PORT Field 62 15 7 LAYGO Access 3 18 5 1 5 3 5 4 5 6 5 7 5 13 5 15 7 2 Levels of File Access Authority 5 5 LIFETIME OF VERIFY CODE Field 3 6 Limited File Manager Options Build Option 9 5 9 11 Example 9 6 Limiting Simultaneous Running of a Particular Task 18 13 Line Editor VA FileMan 2 10 3 20 3 21 5 2 5 5 Line Mode Editing Help 28 4
70. 8 Edit User Characteristics Screen Man Torm oirrasan ae aaa eile ei ea 2 9 Figure 2 9 Display User Characteristics option Sample output and user dialogue cceeeeeeeeeeeeees 2 11 Fieure 3 1 Introductory text edit Option siea a E ee 3 1 Figure 3 2 Enter Edit Kernel Site Parameters option s ssseeeeeeeeeesseessesssssssssssseeeeereeressssssssssseeeeereeeeees 3 2 Figure 3 3 Enter Edit Kernel Site Parameters option ScreenMan form ccccceeccccccccceeeeeeeeeeeeeeeeeeeeeees 3 2 Fiure 5 4 518mm TOW CAL siosana e gesaussaaasieeunncoeneehiascubaaseaaussaundewinacocesantaemmeraseueenass 3 4 Pour 325 POSt sient Text Pie Op Ul OM tedcohest Aine ith cat as Sadtc crated oat E ncosageloaiede 3 7 Figure 3 6 Clear all Users at Startup Opto seis cevecesd ie cewiniedscedss tac asnoiansebantaveres a E aeiaraeweonlans 3 8 Figure 3 7 User Management menu options Associated menu options when adding a new uset 3 8 Figure 3 5 Reprint Access agreement letter option isiicseccicnciasiiic nena E 3 10 Figure 3 9 Security Forms Sample user entries 1 Of 4 oo cecccccccccccsssseeeeeececceeeeeeeeeceeeeessaeeeeeeeeeeeees 3 11 Figure 3 10 Security Forms Sample user entries 2 Of 4 oo cceesessessseseeeccccccceeeecceeeeaaaaaaeeseeseeeeeeeeess 3 13 Figure 3 13 Security Forms Sample User Account Notification form 3 Of 4 eeeeeeeeeeeeeeeeees 3 15 Figure 3 14 Security Forms Sample Computer Account Access Policy form 4 of 4
71. AEA 7 5 Dirac rari OPUOns es a a balun sidan h Attaches dustih tl catenin eee 7 5 OPMOM DESCHIP MONS Seacssnactidiecettcnnstsnccthacastsceiatautadedalt a a 7 5 DisplayinS OpuOms lt yis25 tens otc ecncedacieo A me tekeneneg ate eames 7 6 Opuon Access Dy UST OC pM Megan c6icbonsdaedscdenhrn Geuatecdsoanasie Sanat ar 7 6 Manag me Memis mE Opt Ons ae bites sthnckecnedttzsb sine a a S 7 7 Manas me FPrmmary SUVS i a ea negana tel eluate E E E 7 7 Assigning Secondary MenuS sseeeesssssssecrresssssssseccresssssseccressssssecceesssssseeceeesssssseereesssssss 7 7 ALWAYS SHOW SECONDARIES Field eocen einne eean a i a 7 7 Rede niin the Comin Menier a dahs gent dedita wisatstesaiatsaas 7 7 Auten o EXP ed WIENUS wags oes aces na aren ace sevtacd ne eaanec aed E eaveicaemetaee 7 8 Delete Unireferenced Options OPUOI sorene oer r e a 7 8 Pix Option Bile Pomters ODUONssiireesn a E E 7 9 July 1995 Kernel Systems Management Guide Xi Revised June 2008 Version 8 0 Contents 9 xii Tes ne a Users Menis monera a a a i 7 9 Managins Out Or Order Opon SeS srei E E E ben meesneten ese 7 10 ReStrich ne OPUN Usa anana A se aaacencnwemn ds iushacsseneinneauntes 7 11 Menu Manager Options that Should Be Scheduled cesssesseeeeceeeeaeeeeeeeceeeeeeeaeeees 7 12 Clean Old Job Nodes in XUTL Option eeccccccccccsssesseeeecceeeeaeeseseeeeeeeesaeeneeeeeeeseeeeaaas 7 12 Rebuildme Primary Ment Pre OS ssc5sacoaiacase Sasnsandidaciehtscosdseuaadecastscosaiantid
72. Aces siasn ciec saeszedas cules easszdss R 28 1 SOA EJOT essai cite ahha as sciatic E Sealed hae sich a 28 3 User Into ACE iiaa N ange aanasatiennaehceeetancaantgacsuMeandesekeeacaslenc 28 3 29 XGF Function Library System Management cccccsssssssccccccccesseeeeeececeeeeeesseeeeeeeeeeeeaaees 29 1 OO SSI E EE ET E tea tec E E tear E E E E NE E E beater E E Glossary 1 1a 6 Cap r E O S a e ee AP EEE Index 1 XX Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Figures and Tables Figures Figure 2 1 Signing on to VistA Sample roll and scroll user authentication dialogue cceeeeeeeee 2 2 Figure 2 2 Access denied due to no primary menu or menu out of order MEeSSAE eeeeeeeeeeeeeeeees 2 3 Figure 2 3 Entering the Access and Verify codes at the Same tiMe eeeeeeeeecccccccccececeeeeeeeeeeeeeseeeeeeeeees 2 5 Figure 2 4 Entering the Access and Verify codes at the same time and jumping directly to a specified DP LO goat ah rate T ohana tele senate aeaGaatencacbadasatane E E named eae 2 5 Figure 2 5 System commands Menu options for SIgnoff ccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeens 2 5 Figure 2 6 System commands View Alerts VA option cccccccssssssseseeeseeeeececceecceeeeeaaeeaesaseeeeseeeeeeees 2 7 Pisure 2 7 USers 100 POX MENU OPtron S achat ch cscacasacet an sedissnagsaead eat sit cqeosiaed a amoseqetentonneeeatias 2 7 Figure 2
73. Alerts 10 1 Processing Each Transport Global KIDS 23 16 Producing Reports Searches and Statistics Through Standardized Encoding of Diagnoses and Procedures 25 1 Programmer mode Option 3 22 8 2 Programmer Options Menu 8 2 23 2 26 1 26 3 27 3 28 1 Progress Bar KIDS Installations 23 19 Prohibited Times Options 7 11 PROHIBITED TIMES FOR SIGN ON Field 3 23373 3 22 Prompts Terminal Type 2 6 Protocols Marked Out of Order in Protocol File Option 7 11 July 1995 Revised June 2008 Provider Key 8 3 8 4 Provider Security Key 3 25 Purge Alerts for a User Option 10 7 Purge Build or Install Files Option 24 7 Purge Data Audits Option 5 5 Purge DD Audits Option 5 5 Purge Error Log Of Type Of Error Option 22 26 Purge Inactive Users Attributes Option 3 26 Purge Log of Old Access and Verify Codes Option 3 29 Purge old spool documents Option 17 8 Purging AUTILITY J 7 12 XTMP 7 12 Alerts 10 6 10 7 Audited options 7 4 BUILD File 23 21 Error Trap 13 5 Failed Access Attempts Log Purge 3 29 Inactive Users Attributes 3 26 INSTALL File 23 21 Mail for Inactive Users 3 26 Old Access and Verify Codes 3 29 Old Job Nodes in XUTL 7 12 Options unreferenced 7 8 Security Keys for Inactive Users 3 26 Selected Entries KIDS 24 9 SIGN ON LOG File 3 081 3 28 3 29 Signon Nodes 7 12 Spool Documents 17 3 17 8 Taskman Error Log 13 4 22 25 22 26 Tasks 22 17 22 30 Purpose for Gra
74. Command followed by only one space 10 Unrecognized argument in SET command Ii Invalid local variable name 12 Invalid global variable name 13 Blank s at end of line 14 Missing LABEL REFERENCED in this routine TO Duplicate label 16 Error in pattern code Ly First line tag NOT routine name 18 Line contains a CONTROL non graphic character 19 Line is longer than 245 bytes 20 View command used 21 General Syntax Error 22 Exclusive Kill ZS Unargumented Kill 24 Kill of an unsubscripted global 25 Break command used Exclusive or Unargumented NEW command SView function used Non standard Z special variable used Close command should be invoked through D ZISC TAGTOPP ORT syntax Non standard Z function used HALT command should be invoked through G XUSCLEAN Read command doesn t have a timeout OPEN command should be invoked through S ZIS Routine exceeds SACC maximum size of 5000 Should use TASKMAN instead of JOB command Tag vs Mow Valid Call to this MISSING LABEL see INVOKED BY list Kill of a protected variable Space where a command should be Star or pound READ used Null line no commands or comment Invalid or wrong number of arguments to a function Version number not found on 2nd line of routine Set to a global Quoted string not followed by a separator Lowercase
75. DEVICE file 3 5 It uses the associated operating system s spool facility whether it s a global device or host file Kernel manages spooling so that the underlying OS mechanism is transparent In any environment the same method can be used to send output to the spooler Kernel will subsequently transfer the text to a global for subsequent despooling printing A field in the OPTION file 19 Options can be selected by their menu text or synonym See also MENU TEXT The Kernel module that schedules and processes background tasks also called Task Manager The amount of time Kernel will wait for a user response to an interactive READ command before starting to halt the process In the menu system entering a caret sometimes referred to as an up arrow followed by an option specification name accomplishes a jump to the target option without needing to take the usual steps through the menu pathway A Kernel utility used to verify routines and other M code associated with a software application Checking is done according to current ANSI MUMPS standards and VistA programming standards This tool can be invoked through an option or from direct mode gt D XINDEX Kernel Systems Management Guide Glossary 5 Version 8 0 Glossary Z EDITOR Z A Kernel tool used to edit routines or globals It can be invoked with an option or from direct mode after loading a routine with gt X Z ZOSF GLOBAL 4 ZOSF The Operati
76. E E E 18 1 SYSE VI aM ase Mie MG enea aa anise 18 3 Form Feci esaa E soe einanecenesnseuieoncncesseeennoeet 18 5 User Interlace eean a E T EA 18 5 Sy Stein Manase n M iea a e E E E in ate 18 6 Hon CrO a aac ett ca ttt lac a tated tis al cae aiea oe naa dns eseea 18 7 MSS i PS Ae ENE salts E E E A EEE E E E T E EE ae ial 18 7 SV Stemi Manase MeN esisin a a 18 8 MaA e a O S outenedamueaaea euncamean taeda 18 10 System Manae menies ann nan E eacaes 18 10 Network hammel DEyviCoS sase E E EEA 18 11 Sy Stein Manas erie eiia a a E vans Sinetieaese 18 11 TS OCS aha tery ce A 18 13 Sy Sten Manas emei aise east aa a 18 13 SDP ODSGlE C aa se A a 18 15 lave T ag Whe ESPERO Cee ree en etc ee en E Ter Dace NER et rene rer cre reer O errr acest treet es 18 15 July 1995 Kernel Systems Management Guide XV Revised June 2008 Version 8 0 Contents User IMEI AC Gi ata ciac saisazadasacatleseaesndts sa yuse ceesnataueaatiesl eatsadseunssacstasseonia mean sets anbaets taeda 18 15 Sy Ste tia Matas CIC Niopen A hate aire ieee edt oust lds E A a binrseegatnaduels 18 15 WP Task MN orire ea eE E E E E E IV 1 e E AD A a e e AE E E E E E A A EA E E E E A A A 19 1 Coane AGG e a a a a leuscont tamale siaieakeateseire 19 1 WOLRIS WI TASES a E E E Ouest 19 2 SECUN TIS k ec oa sacs ancuatiaeaeasicimanou ceeuoae ciseanecseaaaensecche ses 19 3 AS Se IMIS AS MEISE eiee tedaetaae ctl scadinianaet eatin Dailant tae ean lacunae heel ttcan 19 3 Display St
77. Edit option XUDEVEDITHFS lets you to edit Host File Server device attributes using a ScreenMan form Cach and GT M HES Device Setup Cach and GT M require the name of the host file to be part of the device I and not part of the parameter list Table 16 2 HFS I O operation modes for Cach and GT M NEWVERSION A new file will be created on VMS with a higher version number this file can be used for WRITEs only READONLY READs are allowed from the specified file WRITEs are not allowed READ WRITE Both READs and WRITEs are allowed for the specified file if a WRITE operation is performed output is appended to the file 16 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Host Files Figure 16 3 Host File Server device for Cach and GI M Sample settings Name HFS SI TMP TMP Type HFS Ask Parameters NO Ask Host File NO Ask HFS I O Operation NO Open Parameters NWS July 1995 Kernel Systems Management Guide 16 3 Revised June 2008 Version 8 0 Host Files 16 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 17 Spooling User Interface Spooling privileges can be granted by IRM to users who prepare and manage reports By sending your output to the spooler rather than to a printer you can benefit in several ways Since spooling saves the output online in a holding area you can easily print multiple copies of the report at a later time Spooling
78. Edit options Select OPTION to edit XQHELP MENU lt Enter gt Help Processor NAME XQHELP MENU HELP FRAME HELP FRAME XQHELP July 1995 Kernel Systems Management Guide 12 7 Revised June 2008 Version 8 0 Help Processor 12 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 13 Error Processing User Interface When an option you are using encounters an error condition you are usually returned to the menu system A message is displayed indicating that an error has occurred You are then presented with the last menu prompt and can continue There are certain error conditions however that may prohibit or prevent return to the menu system In these situations you will be halted off the system July 1995 Kernel Systems Management Guide 13 1 Revised June 2008 Version 8 0 Error Processing System Management The Error Processing menu handles errors for Cach systems It provides access to options pertaining to the error trap displaying printing and purging errors Like the error traps provided by the operating systems the utility allows the investigation of program execution errors or the examination of system errors by capturing a picture of the environment for later reconstruction The ZTER routines are called from ERR ZU to trap errors and store them in the ZTER global a Manager account global that should be translated so that all errors are included on one report The XTER routines ar
79. Enter or Edit File Entries DIEDIT Print File Entries DIPRINT Search File Entries DISEARCH Inquire to File Entries DIINQUIRE If the File Access Security system is implemented the only files you can access directly through VA FileMan options are those listed in your ACCESSIBLE FILE Multiple field 32 in the NEW PERSON file 200 IRM grants file access by using a sub menu on the User Management menu XUSER There are six File Access Security level properties listed alphabetically AUDIT DATA DICTIONARY DD DELETE DEL LAYGO READ RD WRITE WR July 1995 Kernel Systems Management Guide 5 1 Revised June 2008 Version 8 0 File Access Security REF These File Access Security level properties are described in Table 5 1 Each level of access is granted as YES or NO If the File Access Security system is implemented file access is controlled by these YES NO flags not by the matching of your FILE MANAGER ACCESS CODE field 3 string in the NEW PERSON file 200 with security placed on the file If you have not been granted any security access to VA FileMan files entering two question marks when prompted for a file name number shows no files to access Figure 5 2 User has not been granted security access to any VA FileMan files Sample user dialogue Select VA FileMan Option Enter or Edit File Entries INPUT TO WHAT FILE No files displayed here indicates that the user has
80. Exported 8 5 Key Management 8 2 Person Lookup 8 4 Provider 3 25 8 3 8 4 Purging 3 26 Reverse Locks 8 5 Subordinate Keys 8 4 System Management 8 2 User Interface 8 1 XMNOPRIV 8 5 XQAL DELETE 10 7 XQSMDFM 9 5 XTLKZMGR 25 1 25 8 XUAUTHOR 12 5 12 6 XUMGER 3 8 3 9 3 19 4 2 8 3 8 4 9 9 17 7 XUPROG 3 22 7 8 8 1 8 2 23 2 XUPROGMODE 3 22 8 2 13 5 XUSPF200 3 9 3 18 ZTMQ 20 8 22 2 22 5 22 6 Security Keys XUMGER 28 2 Select another task Option 19 6 Select Options to be Delegated Option 9 7 9 9 9 10 SELECTABLE AT SIGN ON Field TERMINAL TYPE File 3 2 3 6 15 8 15 11 Selecting Common Options with the Double Quote 6 8 Software Names for Purging KIDS 24 8 Tasks TaskMan User Interface 19 3 Send Alpha Beta Usage to Programmers Option 23 23 Send Test Pattern to Terminal Option 15 12 Sending Output to the Spooler 17 1 Sequential Disk Processor SDP 18 15 Device Types 15 9 18 15 SERVER ACTION Field 221 11 2 11 3 11 4 11 5 SERVER AUDIT Field 223 11 4 SERVER BULLETIN Field 220 11 4 SERVER DEVICE Field 227 11 2 11 5 SERVER MAIL GROUP Field 222 11 4 Security Keys Server Options 11 1 XUPROG 26 1 Denying Server Requests 11 1 Security Keys Errors and Warnings 11 8 XUPROGMODE 26 1 How Can the Number of Instances of a Server Security Keys Option Be Controlled 11 2 XUPROG 26 1 Server Request 11 1 Security Keys Setting up a Server Option
81. F05 100 Complete Once the Installation Finishes When the installation runs its output is sent to the device you specified when you answered the installation questions If for example you queued the installation to a printer the output is sent to the printer You can find out whether an installation finished by looking up the entry in the INSTALL file 9 7 for that installation use the Install File Print option You should check whether an installation completed successfully or not If the install completed successfully the STATUS field in the INSTALL file 9 7 entry will be set to Install Completed If the install errored out the STATUS field in the INSTALL file July 1995 Kernel Systems Management Guide 23 19 Revised June 2008 Version 8 0 KIDS System Management Installations 9 7 entry will still be set to Install Started If it errored out you need to find out what went wrong and restart the installation REF For information on restarting an installation please refer to the Restarting Aborted Installation topic that follows If you disabled scheduled options options and protocols KIDS should have re enabled those unless the install errored out You should refer to the instructions that came with the software you installed to see what post installation tasks if any you should perform Restarting Aborted Installations A feature of KIDS is the ability to restart an aborted installation KIDS u
82. Figure 24 7 Display Patches for a Package option Sample user dialogue ccccccccecceseseeeeeeeeeeees 24 7 Figure 24 8 Purge or Install Files option Sample user dialogue ccceecccccccsssseeeeeceeeeeeaeeeseeeeeeeesenes 24 8 Figure 24 9 Rollup Patches into a Build option Sample user dialogue 2 00 0 eeeccecccecceeeseeeeeeeeeeeeeees 24 9 Figure 24 10 Updatie Routine File option Sample user dialogue ec cececcccsessseseeeeeeeeeeseseeeeeeeees 24 10 Figure 24 11 Verify a Build option Sample user dialogue cc ceeeecesecceccceeeeeeeeeceeeeeeaeaneeeeeeeeeees 24 11 Figure 25 1 Multi Term Lookup Main Menu options ccccccccccssssssssesssseeeecceeceeeeeeeaeaaaeeeessessseeeeeeees 25 3 Preure 25 2 Standard Device Cha srei cathe han da cde sist ean to eter 25 4 Figure 25 3 Multi Term Lookup MTLU option process chart sssessseeeeeeeeeeeeeeeeeeaaaaeeeeseesseees 25 5 Figure 25 4 Multi Term Lookup MTLU option Sample user entries 0ccceeeeeeeeeeeeeeeeeeeeeees 25 6 Figure 23 5 Print Utility option process Chart sc2dstcsnsosssnsed aeiacenstosnadansacediewussebuesaceedtestncd ucsanatseedendiaees 25 7 Figure 25 6 Print Utility option Sample user entries and sample output eeseeeseeeeeesesereeererrrrrerrereen 25 8 xxviii Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Figures and Tables Figure 25 7 Delete Entries From Look Up opti
83. File Security Access Examples of the VA FileMan options that this property controls are as follows e Fields Being Audited DIAUDITED FIELDS Data Dictionaries Being Audited DIAUDIT DD Purge Data Audits DIAUDIT PURGE DATA Purge DD Audits DIAUDIT PURGE DD Turn Data Audit On Off DIAUDIT TURN ON OFF The DATA DICTIONARY security property DIC lt file number gt 0 DD lt value gt DICTIONARY controls who has access to modify the data dictionary Examples of the VA FileMan July 1995 Kernel Systems Management Guide 5 5 Revised June 2008 Version 8 0 File Access Security Security Property Description Property Location Classic VA FileMan options that this property controls are as follows e Modify File Attributes DIMODIFY e Utility Functions DIUTILITY e Data Dictionary Utilities DI DDU For example to use the Map Pointer Relations option DD access is needed to the PACKAGE file 9 4 and to the files one selects for mapping The DELETE security property controls ADIC lt file number gt 0 DEL lt value gt who can delete an existing record that is contained within the file It does not permit deletion of the file or any of its attribute fields Examples of the VA FileMan options that this property controls are as follows e Enter or Edit File Entries DIEDIT e Transfer Entries DITRANSFER LAYGO The LAYGO Learn As You Go security ADIC lt file property controls who can
84. Guide July 1995 Version 8 0 Revised June 2008 Figures and Tables Figure 7 16 Menu jump error message 1 Of 6 cccceccccccccccessssseeeccceeeaeeeeeecceseeeesaeseeeeeeseesseeeseeeeeeeeeaees 7 14 Fieure 7 17 Menu jump error message 2 Of sans seis weet E a naa aa ee Rae 7 14 Fieure 7 138 Menu jump error message 3 Ol oust cadccbon senses E 7 14 Figire 7 19 Menu jump error message AOLO ssa ssassadd naazajideassahodasavad E 7 15 Figure 7 20 Menu jump error message D OL 6 iy mae iaass vein apace es anna ee ana E 7 15 Figure 21 Menu Jump error message 0 OF 6 x ssncaccesinsyscosacastadesiattiansbaacecleas saesaiaetedeciattiaws bancsitaventeansanss 7 15 Pisure 7 22 User Stace x aiple sn haut ieee San acave sean a a Pepetan the acest 7 17 Figure 7 23 Display Nodes for EVE example ems svc sedaseiavcsasaavnnlacecns ceeecncet soncaadaveoetectantenscneaietaduec 7 18 Figure 7 24 Display Nodes for a secondary MeNU cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeenneneenneeaaagas 7 19 Figure 7 25 Jump Nodes example Lookup nodes ccccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeens 7 19 Figure 7 26 Jump Nodes example Menu PathwayS cccccccccccccccsssnsessseseeeeeeeeeeccceccceeeeeeaeaaaeaeeeaaeeees 7 20 Figure 8 1 Sample locked menu options showing required security key Entering two question MRS eaten ots cerpcabans a antets A E E E nal use tant oakeuceisahe E E AA A 8
85. Installation Guide Clean Old Job Nodes in XUTL Option The Clean old Job Nodes in the XUTL option XQ XUTL J NODES is Kernel s purge option for Kernel globals This option purges the following globals e AXUTL e AUTILITY e TMP e XTMP e AXUSEC Figure 7 14 Clean old Job Nodes in XUTL Operations Management XUSITEMGR Clean old Job Nodes in XUTL XQ XUTL J NODES User stacks for each user s job are stored in the XUTL global REF For more information please refer to the XUTL Global Structure and Function topic in this chapter This is also called the compiled menu system If a job ends abnormally e g upon error UCI switching or developer exits that bypass XUS the entries remain in the global this explains why developers are advised to halt out of programmer mode with D XUSCLEAN rather than simply halting The purge routine sets a purge date of seven days in the past Any user stack in XUTL older than seven days is purged Any entries with a matching J at the top level of UTILITY and TMP are also KILLed 7 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Next after cleaning out the user stacks in XUTL the purge routine checks UTILITY and TMP Any entry at subscript J or namespace J that does not have a matching entry in the user stacks in XUTL is KILLed Next the purge routine checks XTMP Any entry
86. June 2008 Version 8 0 TaskMan System Management Operation List Tasks Option Figure 22 1 List Tasks Option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR List Tasks XUTM INQ Beginning with Kernel V 8 0 the TASKS file 414 4 Gin ZTSK is VA FileMan compatible i e you can use VA FileMan to print out information about a task However the List Tasks option XUTM INQ also provides a way to examine tasks in the TASKS file 14 4 The List Tasks option allows you to choose between several useful ways of selecting tasks When you choose this option it presents you with the following menu Figure 22 2 List Tasks option submenu options List Tasks Option All your tasks Your future tasks Every task List of tasks Unsuccessful tasks Future tasks Tasks waiting for a device Running tasks Select Type Of Listing Several choices only appear on the list when there are tasks in those collections to be displayed Remember the TASKS file 414 4 can be Volume Set CPU specific This means that the option can only display tasks from the TASKS file 14 4 on the current Volume Set CPU Holders of the ZTMQ security key see a slightly different list of selections Instead of All your tasks and Your future tasks they see All of one user s tasks and One user s future tasks These two selections are generic versions of those available to normal users They allow the holder to see a
87. LINK ACCESS Field 21 7 Link List 20 6 Link List Node 22 28 July 1995 Kernel Systems Management Guide Index 19 Revised June 2008 Version 8 0 Index Linking a Help Frame as Help for an Option or Menu 12 7 List Alerts for a user from a specified date Option 10 8 List Delegated Options and their Users Option 9 11 List Error Screens Option 13 3 List File Attributes Option xxxv 5 6 List Global Option 28 1 List Help Frames Option 12 4 12 7 List of tasks Option 22 3 List Options by Parents and Use Option 7 5 List own tasks Option 19 5 List Routines Option 26 6 List Tasks Option 22 2 22 5 22 11 22 12 22 32 All your tasks 22 3 Future tasks 22 4 List of tasks 22 3 Running tasks 22 4 Tasks waiting for a device 22 4 Unsuccessful tasks 22 4 Your future tasks 22 3 List the Defined Options Sets Option 7 11 List Users Option 3 27 Listing and Printing Tasks 19 5 Listing Primary Secondary and Common Menu Options 6 4 LKUP XTLKMGER API 25 22 Load a Distribution Option 23 5 23 7 23 9 23 10 23 21 Load Balance Routine TASKMAN SITE PARAMETERS File 14 7 21 12 LOAD BALANCE ROUTINE Field 21 5 21 12 Load Balancing and Multiple Managers 21 11 Load List Node 22 28 Load Node 22 28 Load Routines 26 8 Load refresh checksum values into ROUTINE file Option 26 8 Loading Standard Distributions KIDS 23 9 Transport Globals from a Distribution or PackMan Message KIDS
88. LOCK OUT TIME Field 3 2 DEFAULT MULTIPLE SIGN ON Field 3 4 Defining Environments TaskMan 21 1 Primary Menu 7 2 Spool Device Types 17 9 Cach 17 9 GT M 17 9 Verify Codes Passwords 2 3 Definitions KIDS 23 1 Delegate keys Option 8 3 9 8 DELEGATED KEYS Field Multiple 8 3 8 4 9 8 Delegate s Menu Management Menu 9 2 9 4 9 5 9 7 9 9 Delegating 9 1 Options 8 3 9 7 9 9 Security Keys 8 3 9 8 DELEGATION LEVEL Field 8 6 DELETE Access 3 20 5 1 5 3 5 4 5 6 5 7 DELETE ALL MAIL ACCESS Field 3 25 Delete Entries From Look Up Option 25 8 Example 25 9 Multi Term Look Up MTLU 25 1 Delete Error Log Option 22 26 July 1995 Kernel Systems Management Guide Index 5 Revised June 2008 Version 8 0 Index DELETE KEYS AT TERMINATION Field 3 25 Delete Old gt 14 d Alerts Option 10 6 10 7 Delete Routines Option 26 8 Delete Tasks Option 20 8 22 6 Delete Unreferenced Options Option 7 8 28 1 Deleting Alerts 10 3 Routines Routine Tools 26 8 Security Keys 8 5 Dequeue Tasks Option 20 8 22 4 22 5 22 6 22 33 DESCRIPTION Field 22 21 DESCRIPTION Field 3 5 OPTION File 19 11 3 Descriptions Options 7 5 DESPOOL DEVICES Field Multiple 17 9 Device Allocation List 22 9 Node 22 27 Device Chart Multi Term Look Up MTLU 25 4 DEVICE File 3 5 1 2 3 1 3 2 3 3 3 4 3 5 3 20 11 2 11 5 15 1 15 2 15 6 15 7 15 8 15 9 15 10 17 9 17 10 18 3 18 6 18 8 18 13 18 14 18 15
89. LOWER and obtain 10 matches Though the term malignancies may not exist in the lookup file MTLU might still produce a match When a term contains a suffix that does not produce a match MTLU removes the suffix and continues the search REF For more information on the Inquire to File Entries option please refer to the How to Display and Print File Data chapter in the VA FileMan User Manual Three additional files are supplied that can dramatically alter the predictable behavior described above They are checked in the following order against the user s entry 1 LOCAL SHORTCUT file 8984 2 Shortcuts are used to point to a single term They can be a word or phrase MTLU checks the user s entry against this file first for an exact match If found the lookup displays only the associated entry A single shortcut cannot point to multiple terms 2 LOCAL SYNONYM file 8984 3 Synonyms can be associated with many terms in a file because they can be associated with multiple tokens rather than a specific term For example CANCER can be defined as a synonym of MALIG TUMOR and LEUKEMIA When the user enters CANCER the lookup finds all terms associated with the three tokens as if each had been entered separately Compared with the example above CANCER returns 534 matches CANCER LIP returns the same 12 matches as MALIG LIP 3 LOCAL KEYWORD file 8984 1 A keyword or phrase can be associated with a single term much like a short
90. Management User Management Select Systems Manager Menu Option USER MANAGEMENT Add a New User to the System Grant Access by Profile Edit an Existing User Deactivate a User Reactivate a User List users User Inquiry Switch Identities File Access Security Clear Electronic signature code Electronic Signature Block Edit Manage User File OAA Trainee Registration Menu Person Class Edit Reprint Access agreement letter Select User Management Option REPRINT ACCESS AGREEMENT LETTER Select NEW PERSON NAME REQUEST ACCESS lt Enter gt AR COMPUTER SPECIALIST Is REQUEST ACCESS the one you want YES lt Enter gt DEVICE 0 80 60 lt Enter gt Telnet Terminal 3 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management Figure 3 11 Security Forms Sample User Account Notification form 3 of 4 USER ACCOUNT NOTIFICATION Department of Veterans Affairs superstar VAMC 123 Any Street Any LOW Ols 99999 The name of the user and location is displayed here For this example the user s name is Access Request at the Superstar VAMC ACCESS REQUEST Superstar VAMC A user account has been created in your name to enable you to access on line clinical and or administrative data required to perform your duties as an employee of the Department of Veterans Affairs Please read the enclosed NEW USER INFORMATION before you attempt your first log on to
91. N 0 bong CS c Hs Raine nen perenne ene nee On bEN Tne A 3 24 Automatically Deactivating Users icsatsccssscssvecnsiecvsnsasasvecataddaseassaawhaceladseansabessacsadesdetwidueans 3 25 Purging Mail and Security Keys for Inactive USers cc ceeccsccecccccceesseseeeeeeeeeeaeeeeseees 3 26 Reactrvaline Usei a deissncetcatese inate iaaiedeun souk satisan eh cts su caaeeetees Sonseatenen ek cab sousea enone cate seas 3 26 User Management Options on the Operations Menu ccccccccsssseesececceeeeeeeeeeeeeeeeeeeaeeeeees 3 26 Perri aU Si On gcesi as cece ce aurea teases det ocg eat ena E anes oe T O E 3 27 ESCUSO 101 c ene eo Cree eae cete Mira suy E ON Cason tee Rint ee eres 3 27 PnC ROR EO RODO 10 pemnene nner ben nee ents Reneente epeteee ore T 3 27 Rer ASE Ter Opio casscuce tastes ceria dahes a ae datat isa hicste SMealchdaistus cided 3 27 User TING Uy PO Misites nian ceieaistcnmch in oasaninet a a 3 27 User Status Repon OPUlOW ieren a E ete hanendat eee nese 3 28 SOOT AICS stood carat te Ganiaasee derias bua guerra bea a toe bas esaGaant me ES 3 28 SNO DEATESUICS nae cetiadsaen ares A A Ta are TR 3 28 Filed Access ACUI US AU aa E unten ie wc de ace iu kas eine Ananaalesusaisles 3 28 Purge Old Access and Ver YC OES inci aenasccasassunnaessts docndeasapeaisbodenegenddapesetehseaadeacsercetyachenar 3 29 A Electronic Senare Sae a mean taescaeua ne meckenensgecten a cantascawent 4 User Tater ICE eis 4 1 Sylen Mana ene Mao a S a use
92. NEXT Field 22 16 Starting Up Pausing and Stopping Multiple Managers 21 11 Startup List Node 22 29 States Messages TaskMan 22 36 Statistics Signon 3 28 Statistics Option 5 6 Status Codes TaskMan 22 32 STATUS Field 23 19 Status List 20 6 22 8 Node 22 29 Stop Node 22 29 Stop Task Manager Option 22 16 Stop task Option 19 4 Stop TaskMan Option 22 27 22 38 Stopping Tasks 19 4 Storing Host Files in a Specific Directory 18 3 Sub Node 22 29 SUBMANAGER RETENTION TIME Field 21 3 21 4 Submanagers TaskMan 20 1 20 3 SUBORDINATE KEY Field Multiple 8 4 Subordinate Keys 8 4 SUBTYPE Field DEVICE File 3 5 15 1 15 2 15 4 15 8 18 10 18 11 Summary Device Handler 14 7 How the File Access Security Conversion Works 5 12 Menu Manager 6 9 Signon Security 2 12 TaskMan User Interface 19 6 SUPPRESS BULLETIN Field 224 11 5 SUPPRESS FORM FEED AT CLOSE Field 18 6 Surrogate for which Users Option 10 10 Surrogates Alerts 10 4 10 6 Switch Identities Option 7 9 Switch UCI Option 2 12 Switching UCIs 7 12 21 2 Symbols Found in the Documentation xxxiv SYNC FLAG Field 22 16 SYNC flag file control Option 22 16 SYNC FLAGs 18 13 22 16 Synonym Options 6 3 Synonym Option Multi Term Look Up MTLU Example 25 19 Synonyms Devices 15 12 Multi Term Look Up MTLU 25 1 25 12 Associated with Multiple Terms 25 2 Multiple Tokens 25 2 Options 6 1 6 3 6 5 6 6 7 3 7 19 12 2 Synonyms Option Mu
93. OPENS Field 18 11 Search File Entries Option 5 6 SECONDARY I Field 52 15 6 Secondary Menu 3 22 6 3 6 6 7 5 7 6 7 7 7 8 7 15 7 18 8 3 9 2 9 3 Assigning 7 7 Trees 7 7 7 16 SECONDARY MENU OPTIONS Field Multiple 3 19 3 22 7 7 7 18 9 4 Secure Menu Delegation 3 19 3 24 9 1 Build a New Menu Option 9 4 Copy Everything About an Option to a New Option Option 9 4 Copy One Users Menus and Keys to others Option 9 4 Delegate s Menu Management Menu 9 2 Delegating Keys 9 8 Delegating Options Select Options to be Delegated 9 7 Delegation Levels 9 9 Edit a User s Options 9 2 Limited File Manager Options Build 9 5 Menu Prefix 9 11 Options too Sensitive to Delegate 9 10 Remove Options Previously Delegated Option 9 10 Replicate or Replace a Delegate 9 10 Reports 9 11 System Management 9 7 User Interface Acting as a Delegate 9 2 Secure Menu Delegation Menu 9 7 9 9 Utilities 8 1 Secure Menu Management Menu 9 2 9 5 Security Devices 15 7 File Access Security 5 5 SECURITY Field 3 2 3 20 15 7 15 8 Security Forms 3 9 3 10 SECURITY KEY File 19 1 8 2 8 4 8 5 12 6 Security Keys XTLKZMGR 25 8 25 9 Security Keys 7 7 8 1 Allocating Keys 8 3 Creating 8 4 De allocating Keys 8 3 July 1995 Kernel Systems Management Guide Index 35 Revised June 2008 Version 8 0 Index Delegating 8 3 9 8 Delegation Levels 8 3 8 6 9 3 9 9 Deleting 8 5 Editing 8 4 Exploding Key 8 4
94. Of Dates Option Figure 22 25 Clean Error Log Over Range Of Dates SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Clean Error Log Over Range Of Dates XUTM ERROR LOG CLEAN RANGE After prompting for a First date to purge and a Final date to purge the Clean Error Log Over Range Of Dates option XUTM ERROR LOG CLEAN RANGE removes the entries for all errors that occurred on and between the two dates It prints the number of entries removed If the first date is not earlier than the final date no entries are removed Use this option to delete all but recent errors that deserve your attention It is better to resolve specific kinds of errors as you encounter them However 1f there is a period during which you cannot resolve them fast enough to keep the log clean this option will help you focus on the recent ones July 1995 Kernel Systems Management Guide 22 29 Revised June 2008 Version 8 0 TaskMan System Management Operation Purge Error Log Of Type Of Error Option Figure 22 26 Purge Error Log Of Type Of Error option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Purge Error Log Of Type Of Error XUTM ERROR PURGE TYPE With the Purge Error Log Of Type Of Error option XUTM ERROR PURGE TYPE you can delete
95. Option Device Edit Select DEVICE NAME LABEL PRINTER NAME LABEL PRINTER SUPPRESS FORM FEED AT CLOSE SUPPRESS FORM FEED AT CLOSE YES The Device Handler also checks the TERMINAL TYPE file 3 2 to see if form feeds have been suppressed for that terminal type It checks for the existence of the IONOFF variable Thus for certain terminal types e g laser printers IRM can set this no form feed variable in the corresponding terminal type s CLOSE EXECUTE field ONOFF can also be set by the calling program to suppress form feeds Figure 18 6 Terminal Type Edit option Sample user dialogue Select Systems Manager Menu Option Device Handler Select Device Handler Option Terminal Type Edit Select TERMINAL TYPE NAME P DEC LABEL NAME P ZPK80 CLOSE EXECUTE CLOSE EXECUTE S IONOFF 18 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues Hunt Groups User Interface Hunt groups are a set of printers that IRM can set up to share print workload If one printer in the hunt group 1s busy output is directed to another one that is free This results in less waiting time for printouts and helps prevent any particularly long print job on one printer from holding up other output directed to the same printer Hunt group devices are defined by IRM and would typically include similar printers located near each other Users can send to the hunt group device or to any member of the hun
96. P E 1I D I Enter Print Template Name Optional LRZ REFERRAL PRINT Option Name LRZ REFERRAL INQUIRE Located in the LR LAB SERVICE namespace ARE YOU ADDING LRZ REFERRAL INQUIRE AS A NEW OPTION THE 996TH Y lt Enter gt YES OPTION MENU TEXT Display a Referral MENU TEXT Display a Referral Replace lt Enter gt DESCRIPTION 1 gt Display Lab Referral entries option created by LAB ADPAC 2 gt lt Enter gt EDIT Option lt Enter gt Select Delegate s Menu Management Option 9 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Secure Menu Delegation System Management Managing Delegates The options for creating and managing delegates are on the Secure Menu Delegation menu XQSMD MGR which is on the Menu Management menu Typically IRM would be the sole holder of this menu The options on this menu are Table 9 1 Secure Menu Delegation menu options opona rn The main options to create and manage delegates are e Select Options to be Delegated e Replicate or Replace a Delegate Delegating Options Select Options to be Delegated Option To delegate options use the Select Options to be Delegated option from the Secure Menu Delegation menu Using this option is a two step process 1 Choose the users to whom options are delegated 2 Choose which options to delegate to that group of users You can choose to set up one user or many users as delegates You can choose one option or a
97. PS0 On AACA 0 KROONDE S On SALE 22000 July 1995 Kernel Systems Management Guide 7 19 Revised June 2008 Version 8 0 Menu Manager System Management Figure 7 26 Jump Nodes example Menu Pathways AXUTL XQO P580 LIST FILE ATTRIBUTES 1741 AXUTL XQO P580 TEST 4 3181 YE EX O08 EP SO gn POOLE 04 0 AXUTL XQO P580 X TYPE OPTION TEST 57641 AXUTE XOO MP580 TXAT 576 0 AXUTL XQO P580 ZDAVE 411 1 AXUTL XQO P580 4 5 XUEDITOPT Edit OPTICOS E Soli OOO a O ie ae AUTI ROO pogon TS 1 ADILISTiist Pile Attribuces nann 5205519 51 A Thee Cy a RO Ta OO RD OF ges Soy eee a ee eee BA OP 57 0615091 gs ep a Oa ARGTI OO E580 ON 6180 2 KUTA Y KOO MPS 80 MO 18 0nd 620757525 18 a a AUTH XOO p P5809 S180 22 i 520 575 578 218 AXUTL XQO P580 4 579 ZZLEVEL3B Phantom Moecher OOM 500 575 57 0 RAL AUTH TXOON TP 580 ot 580 AZZTISTEM Primary MenuOOMA AF 44g TAAT ATSA AXUTL XQO P580 581 ZZLUKTOOLS Luke s TOC LS AM O y PAAAASACA TAD AAT Menu Manager Variables Troubleshooting There is a group of Menu Manager variables that is always defined It may be useful for IRM staff to know what these variables signify when investigating errors If an error 1s reported in VA FileMan s DIP routine for example knowing the value of XQY at the time of the error indicates which option was invoking the DIP
98. RECOMMENDED field 209 in the OPTION file 19 must be set to YES QUEUED TO RUN AT WHAT TIME To queue an option select the option and enter a time at least two minutes in the future into the QUEUED TO RUN AT WHAT TIME field When you enter a time and date for the task to run the task is immediately put on the Schedule List for that time How to Delete a Regularly Scheduled Task Deleting a scheduled task is as simple as entering the at sign at the QUEUED TO RUN AT WHAT TIME field TaskMan then searches the current TASKS file 14 4 for the task that corresponds to the entry in the OPTION SCHEDULING file 419 2 and deletes it If your system has multiple copies of the TaskMan globals you must use Schedule Unschedule Options on the same Volume Set CPU where your task originated when you delete the task Otherwise the future July 1995 Kernel Systems Management Guide 22 19 Revised June 2008 Version 8 0 TaskMan System Management Operation task in the TASKS file will not be found and deleted when you enter an at sign in the QUEUED TO RUN AT WHAT TIME field How to Requeue a Regularly Scheduled Task Requeuing merely involves placing a new value in the QUEUED TO RUN AT WHAT TIME field When you do this the currently scheduled task is deleted exactly as described above when deleting a scheduled task Then a new task is created at the new time to replace the previously scheduled task If your system has mul
99. Reviewer for Alerts XOAL SET BACKUP REVIEWER Surrogate for which Users XOAL SURROGATE FOR WHICH USERS Alerts Set Remove Surrogate for Users Option The Alerts Set Remove Surrogate for User option XQALERT SURROGATE SET REMOVE is provided so that IRM or ADPAC personnel can do the following e Set a surrogate to receive alerts for a user e Remove a surrogate from receiving alerts for a user The option asks for a user to be selected then is ready to specify a new surrogate for the selected user or to remove the current surrogate for that user This option is not needed by the individual users who may select to name or remove a surrogate as one of the options while processing alerts or if no alerts are present for the user as his her only option on selecting alert processing Delete Old gt 14 d Alerts Option The Delete Old gt 14 d Alerts option XQALERT DELETE OLD performs the following functions e Purges unprocessed alerts from the ALERT file 8992 e Purges alert tracking information from the ALERT TRACKING file 8992 1 e Forwards unprocessed alerts to supervisors and or surrogates You can use the Delete Old gt 14 d Alerts option to purge all alerts that have been unprocessed for longer than a specified retention period the default is 14 days It is assumed that an alert becomes obsolete within this period and can be purged by IRM staff This option also performs additional functions which are des
100. Set Management XQOOOMAIN Create a Set of Options To Mark Out Of Order XOOOMAKE List Defined Option Sets XQOOSHOW Mark Option Set Out Of Order XQOOFF Options in the Option File that are Out of Order XQOOSHOFTIL Protocols Marked Out of Order in Protocol File XQOOSHOPRO Recover Deleted Option Set XQOOREDO Remove Out Of Order Messages from a Set of Options XOOON Toggle options protocols on and off XQOOTOG Menu Manager starting with Kernel V 8 0 provides a mechanism for defining sets of options and protocols and a way to disable and enable access for these pre defined option and protocol sets via options on the Out Of Order Set Management menu XQOOMAIN This can be handy when you need to repeatedly disable and enable sets of options and protocols Use the Create a Set of Options to Mark Out Of Order option XQOOMAKE to define a set of options You are prompted first to select options and then to select protocols For both options and protocols you can use the following to e Add a group of options to the set Use the wildcard asterisk with or without a namespace e Add a range of options to a set Use NAM1 NAM2 to add a range of options from NAMI to NAM2 to the set where NAM represents a namespace e Subtract Remove a group of options from a set Use the minus sign 1 e hyphen followed by a namespace Use the Mark Option Set Out Of Order option XQOOFF to disable access to a s
101. TYPE entries is needed to describe the attributes of the slaved printer including escape codes to adjust fonts pitches The OPEN EXECUTE and CLOSE EXECUTE fields of the TERMINAL TYPE file 3 2 can be used to hold such codes Additionally the device entry for the slaved printer must have a value of 0 zero entered into the I field This I value identifies the DEVICE file 3 5 entry as one for a slaved device The following examples show the setup for a home device and the setup for slaved printers Figure 18 15 Home Device example VT320 DEVICE file 3 5 entry NAME TELNET DEVICE SL TNA ASK DEVICE YES ASK PARAMETERS NO VOLUME SET CPU KDE SIGN ON SYSTEM DEVICE YES LOCATION OF TERMINAL Network MARGIN WIDTH 80 FORM FEED C 27 91 50 74 27 91 72 PAGE LENGTH 24 BACK SPACE C 8 SUBTYPE C VT320 TYPE VIRTUAL TERMINAL TIMED READ OF SECONDS 400 18 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues Figure 18 16 Home Device example VT320 _TERMINAL TYPE file 3 2 entry NAME C VTI320 SELECTABLE AT SIGN ON YES FORM FEED 93C 27 91 50 14 27 917 72 RIGHT MARGIN 80 PAGE LENGTH 24 BACK SPACE SC 3 DESCRIPTION Digital Equipment Corporation VT 320 video OPEN PRINTER PORT W 27 5i CLOSE PRINTER PORT W 27 4i Figure 18 17 Slaved Printer example DEC LA50 DEVICE file 3 5 entry NAME SLAVELAS5O0 Sie 0 ASK DEVICE YES AS
102. Table 15 3 Queuing settings Setting Queuing Deseripion SSCS oO ALLOWED Jobs can be queued or run directly default FORCED Queuing is forced unless disallowed by application NOT ALLOWED Queuing to device is not allowed OPEN PARAMETERS and USE PARAMETERS Fields Magtape SDP obsolete and HFS device types use the value of the OPEN PARAMETERS field as the default if the ASK PARAMETERS flag is set Users would then be prompted for address parameters If the ASK PARAMETERS flag is not set and if there is a value in the OPEN PARAMETER field this value is used when opening the device or file The Device Handler also takes information from the USE PARAMETERS field when opening and using such devices as the tape drive Each operating system has its own way of specifying parameters For example under Cach margins are set with both the OPEN and USE command PRE OPEN EXECUTE POST CLOSE EXECUTE These fields can be used to execute a line of M code prior to opening the device and after the device is closed 15 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler System Management NOTE If you define the variable ZISQUIT in the PRE OPEN EXECUTE code the device open will fail With this variable you can use the PRE OPEN EXECUTE as a screen on whether the device should be opened or not Mixed OS Environment NOTE This is for Cach only Cach can use ECP to run in an appl
103. Term Look Up MTLU All shortcuts synonyms and keywords associated with the reference file you wish to delete must be canceled before you attempt to delete the file It should be noted that when a reference file is killed through this option all variable pointers from the LOCAL KEY WORD 8984 1 and LOCAL SHORTCUT 8984 2 files are deleted The special lookup routine for the file is also deleted Only holders of the XTLKZMGR security key can access this option NOTE Due to the brevity of this option no process chart has been provided The following is an example of what might appear on your screen when using the Delete Entries From Look Up option Figure 25 7 Delete Entries From Look Up option Sample user entries Select LOCAL LOOKUP NAME PROCEDURE MODIFIERS Are you sure you want to delete PROCEDURE MODIFIERS YES Deleting from Local Lookup file Deleting variable pointers from Local Keyword and Shortcut files Deleting special lookup routine from PROCEDURE MODIFIERS DD Add Entries To Look Up File Option The Add Entries To Look Up File option XTLKMODPARS is used to add edit reference files to a site s LOCAL LOOKUP file 8984 4 Examples of files that a site might wish to enter in their LOCAL LOOKUP file 8984 4 include ICD DIAGNOSIS 80 ICD OPERATION PROCEDURE 80 1 and CPT 81 Only holders of the XTLKZMGR security key can access this option In order to add entries with this option DUZ 0 mu
104. The User Status Report option XUUSERSTATUS produces a report of the users currently signed on to this CPU and UCI It shows the option each user is running and when they signed on as well as their device and job numbers Signon Audits Signon events are recorded in the SIGN ON LOG file 3 081 Statistics such as the time of access and the user s identity are stored for audit purposes If the user exits normally is not bumped off the system the signon record will include the time of exit If the user exits abnormally with an error or enters programmer mode the signon record cannot include a time of exit Information about signon activity can be reviewed with options on the Operations and System Security menus The SIGN ON LOG file 3 081 is purged with the XUSCZONK option that should be tasked to run on a regular schedule e g every night This option cannot be reached from Menu Manager like other options that should only be queued it is on the PARENT OF QUEUABLE OPTIONS menu Signon Statistics Statistics about active sessions can be obtained with the CPU Service User Device Stats option XUSTAT This option permits sorting by CPU by the user s Service Section e g MAS by individual users or by particular devices Figure 3 18 CPU Service User Device Stats option SYSTEMS MANAGER MENU EVE Operations Management XUSITEMGR CPU Service User Device Stats XUSTAT Failed Access Attempts Audit
105. Up File Sample user entries gt D XUP Setting up programmer environment Terminal Type set to C vT100 Select OPTION NAME APP lt Enter gt LICATION UTILITIES XTMENU Application Utilities Multi Term Lookup Main Menu Select Application Utilities Option Multi lt Enter gt Term Lookup Main Menu Multi Term Lookup MTLU Print UCELICY Utilities for MTLU Select Multi Term Lookup Main Menu Option Util lt Enter gt ities for MTLU Delete Entries From Look up Add Entries To Look Up File Add Modify Utility Select Utilities for MTLU Option ST lt Enter gt Add Entries To Look Up File Select LOCAL LOOKUP NAME ICD DIAGNOSIS ARE YOU ADDING ICD DIAGNOSIS AS A NEW LOCAL LOOKUP THE 3RD Y lt Enter gt YES LOCAL LOOKUP NAME ICD DIAGNOSIS lt Enter gt LOCAL LOOKUP DISPLAY PROTOCOL DSPLYD XTLKKWLD INDEX AIHS Ok will now setup KEYWORD and SHORTCUT file DD s to allow terms for ICD DIAGNOSIS entries Enter the PREFIX M Variable Answer must be a unique prefix 1 10 characters in leng Pointer prefix PREFIX M D lt REMINDER gt Using Edit File set the lookup routine XTLKDICL in ICD DIAGNOSIS DD Select LOCAL LOOKUP NAME lt Enter gt July 1995 Kernel Systems Management Guide 25 21 Revised June 2008 Version 8 0 Multi Term Look Up MTLU If all references to a file by all packages are to behave as MTLU lookups add the special lookup routine XTLKDICL to the file s DD using the File
106. Verifying Checksums in a Transport Global KIDS 23 12 VERSION Field Multiple 23 5 Version Number Update Option 26 6 Versions to Retain KIDS 24 8 VHA Software Document Library VDL Home Page Web Address xxxvii VI 2 VI 3 View Alerts VA Option 2 7 6 7 10 1 10 2 View data for Alert Tracking file entry Option 10 9 Virtual Devices VMS Systems 15 10 Virtual Terminals 15 10 VMS Systems Virtual Devices 15 10 VMS DEVICE TYPE Field 63 15 7 VOICE PAGER Field 2 9 3 23 4 1 VOLD Cross reference 3 29 Volume Set Definition 20 8 VOLUME SET CPU Field DEVICE File 3 5 15 2 15 3 15 4 15 10 15 13 15 14 21 13 22 20 Volume Set Edit Option 21 5 VOLUME SET Field VOLUME SET File 14 5 21 6 VOLUME SET Field Multiple KERNEL SYSTEM PARAMETERS File 8989 3 3 3 21 3 VOLUME SET File 14 5 3 8 20 5 20 7 21 1 21 5 21 9 22 17 22 35 22 37 DAYS TO KEEP OLD TASKS Field 21 8 INHIBIT LOGONS Field 21 7 LINK ACCESS Field 21 7 July 1995 Revised June 2008 OUT OF SERVICE Field 21 7 REPLACEMENT VOLUME SET Field 21 8 REQUIRED VOLUME SET Field 21 7 Standardized VA Cach and GT M Configuration 21 10 TASKMAN FILES UCI Field 21 8 TASKMAN FILES VOLUME SET Field 21 8 TYPE Field 21 7 VOLUME SET Field 21 6 W Wait Node 22 29 WAIT State 22 29 TaskMan 21 11 22 15 22 16 22 38 Waiting List 20 6 Web Pages Acronyms Home Page Web Address Glossary 6 Adobe Home Page Web Address xx
107. a given software application This information is useful as a record of each installation Rollup Patches into a Build Option The Rollup Patches into a Build option XPD ROLLUP PATCHES finds all the patches for a software application and add their individual BUILD file 9 6 definitions to the software s BUILD file 9 6 definition This will enable you to create a single BUILD file 9 6 entry that contains the definition for the patched software KIDS checks the BUILD file 9 6 and lists all KIDS patches with a matching software name and version number The list of patches is not necessarily displayed in patch sequence number This list only includes KIDS patches Also it does not include any pre or post install routines You can use the Edit a Build option to further modify the build and add any additional patches Figure 24 9 Rollup Patches into a Build option Sample user dialogue Select Utilities Option Rollup Patches into a Build ROMP palLehes into Bua hd KERNEL 8 0T20 lt Enter gt KERNEL This package already contains the following patches XU 8 0T20 4 The following patches can be rolled into Package RON 8 0T20 KUO OT20F5 KUFO sUTZ0H XU 8 0T20 7 XUZ 8 OT2Z0 33 LUSO 7012 0a OK to continue YES lt Enter gt July 1995 Kernel Systems Management Guide 24 9 Revised June 2008 Version 8 0 KIDS System Management Utilities Update Routine File Option The Update Routine File option XPD ROUTINE UPDATE up
108. a file entry a user is unable to add or delete entries in the primary file because the application did not set the DLAYGO or DIDEL variables e lt A user needs to use the VA FileMan Line Editor s Transfer Lines from Another Document option Application developers can document which files need to be granted to whom or can modify their code or data dictionary DD specifications to allow access Levels of File Access Security There are six file access security properties involved with File Access Security If a file access security property is not defined 1 e the value is null the VA FileMan exported menu option s for that property are not open to full access for users REF The following table is taken from the VA FileMan Version 22 0 and Kernel Version 8 0 File Access Security supplemental documentation located on the VHA Software Document Library VDL at the following Web address http www va gov vdl application asp appid 5 Table 5 1 File Access Security level properties Access Security Property Description Property Location Classic VA FileMan The AUDIT security property controls the ADIC lt file number gt 0 AUDIT lt value gt setting of auditing characteristics and the deletion of audit trails This property only deals with the auditing of data and not the auditing of data dictionary DD changes To audit DD changes users would enter YES at the DD AUDIT NO prompt when modifying a file s
109. after a successful signon Like the introductory text you can edit the message text using the Enter Edit Kernel Site Parameters option alternately you can use the Post sign in Text Edit option XUSERPOST which is specially designed for this purpose Figure 3 5 Post sign in Text Edit option SYSTEMS MANAGER MENU EVE Operations Management XUSITEMGR Post sign in Text Edit XUSERPOST Applications can append information to the POST SIGN IN MESSAGE on a per user per signon basis only by attaching to the new XU USER SIGN ON option REF For more information on the XU USER SIGN ON option please refer to the Signon Security Developer Tools chapter in the Kernel Developer s Guide XU USER SIGN ON Option The XU USER SIGN ON option can attach action type options to this extended action type option so that software specific actions can be performed at signon REF For more information please refer to the Signon Security Developer Tools chapter in the Kernel Developer s Guide July 1995 Kernel Systems Management Guide 3 7 Revised June 2008 Version 8 0 Signon Security System Management Clear all users at startup Option Figure 3 6 Clear all users at startup option PARENT OF QUEUABLE OPTIONS ZTMQUEUABLE OPTIONS Clear all users at startup XUSER CLEAR ALL If multiple signons are prohibited users may be prevented from signing on to the system when it is brought up a
110. after bad sign on 3 Prohibited time for sign on 4 Time to wait for a response TIED ROUTINE Check if device is tied to a function No Enter Access and Verify codes Yes Check if DISUSER flag is set for user Retrieve Post Sign in Text Append one line greeting Execute XU USER SIGN ON extended action option Display Post Sign in Text Update system parameters from NEW PERSON File Query Terminal Type DEVICE PRIMARY MENU Check if terminal is tied to a menu No USER PRIMARY MENU Check if user is tied to a menu No Execute the Routine Multiple Sign On Restriction The DEFAULT MULTIPLE SIGN ON field in the KERNEL SYSTEM PARAMETERS file 8989 3 controls whether users can create two or more simultaneous sessions by signing on to more than one device The setting is overridden by comparable fields in the DEVICE 3 5 and NEW PERSON 200 files respectively The value is checked at signon to prevent unauthorized multiple sessions If multiple signons are prohibited problems can occur if users experience an abnormal exit such that the signon record cannot be cleared To clear an individual user the Release User option can be used described later in this chapter To make sure all users are clear when the system is brought up after a crash IRM can use the Clear all users at startup option 3 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management INTERA
111. all users e g MailMan User and other options on the Common menu July 1995 Kernel Systems Management Guide 8 5 Revised June 2008 Version 8 0 Security Keys Security Key Delegation Levels Starting with Kernel V 8 0 security keys are subject to delegation levels just as options are subject to delegation levels A field in the NEW PERSON file 200 DELEGATION LEVEL stores a user s delegation level for security keys and options When a security key is delegated the person to whom it is delegated is assigned a level one number lower than the delegation level of the person doing the delegating This is to prevent the delegated to person from removing DELEGATED KEYS from someone with a lower delegation level REF For more information about delegation levels please refer to the Secure Menu Delegation chapter in this manual 8 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 9 Secure Menu Delegation The job of allocating menu options to users can be a time consuming activity so site managers may want to consider delegating this responsibility to application coordinators Application coordinators are familiar with the menus for their software and can learn how to assign these to new users in their service area Secure Menu Delegation allows the Site Manager to delegate the management of certain menu options to another user e g an application coordinator This user now a delegate can then assign the
112. an option delegated to you Copy Everything About an Option to a New Option Option Using the Copy Everything About an Option to a New Option option XQCOPYOP you can copy any option on the computer system into a new option First you are asked which existing option you would like to copy then you are asked for a name for the copied option The option name must begin with a namespace assigned to you by IRM Copy One Users Menus and Keys to others Option Using the Copy One Users Menus and Keys to others option XQSMD COPY USER you can copy the menus and security keys of one user to another user Each menu or security key you copy however must have been delegated to you otherwise they are skipped in the copy process What gets copied from one user into the other user are e PRIMARY MENU OPTION and all descendant menus e SECONDARY MENU OPTIONS e KEYS The PRIMARY MENU OPTION of the user you re copying from replaces the PRIMARY MENU OPTION of the user you are copying to The SECONDARY MENU OPTIONS and the KEYS of the user you re copying from are merged into the SECONDARY MENU OPTIONS and the KEYS of the user you re copying to 9 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Secure Menu Delegation Limited File Manager Options Build Option The Secure Menu Delegation system provides a way for delegates to create options out of VA FileMan templates Delegates who have enough access to VA FileMan t
113. any you can specify an alert action type of routine or option It then generates the alert on the fly This option is recommended primarily for IRM personnel and ADPACs it may or may not be appropriate for other selected users NOTE This option does not allow the user to set the CAN DELETE WITHOUT PROCESSING field 1 in the ALERT file 8992 Purge Alerts for a User Option The Purge Alerts for a User option XQALERT BY USER DELETE allows you to delete alerts for a user The main purpose of this option is to provide a way to delete alerts for a user who has been inactive for a period of time e g on leave and who has accumulated a number of alerts that should not need processing This option is locked with the XQAL DELETE security key and should only be used by IRM personnel and or ADPACs July 1995 Kernel Systems Management Guide 10 7 Revised June 2008 Version 8 0 Alerts Report Menu for Alerts Menu The Report Menu for Alerts menu XQAL REPORTS MENU This menu provides several options for generating reports on alerts for users or patients It consists of the following submenu items Figure 10 4 Report Menu for Alerts menu options Select Report Menu for Alerts Option Critical Alerts Count Report XOAL CRITICAL ALERT COUNT List Alerts for a user from a specified date XOAL ALERT LIST FROM DATE Patient Alert List for specified date XQAL PATIENT ALERT LIST User Alerts Count Report XOAL USER ALERTS CO
114. are locally added to the standard XUCOMMAND menu set new installations of Kernel will not overwrite the changes During installation items on the local XUCOMMAND menu are compared with the exported items Any previously exported items that were removed by the site will not be added back Brand new items however will be added and any matching items will be updated Other items that the site may have added will be left in place Altering Exported Menus Generally speaking exported menu structures should stay intact If local modifications to exported menus are made great care must be taken to preserve any logic that may exist in the exported structure For example the entry action of one option can set up key variables that are then assumed to exist when another option one further down on the menu tree is invoked Although each one of a software s options should be able to be invoked independently once the steps described in the Kernel Technical Manual for creating and KILLing software wide variables have been taken according to the Programming Standards and Conventions SAC this is not always the case and cannot be assumed If an option cannot be invoked independently the developer can set that option s INDEPENDENTLY INVOCABLE field to NO as an alert that some other option or action must be done before the option can be called To give users the options associated with new software applications IRM should try to allocate the menus as w
115. can only run tasks in the UCIs it can reach TASKMAN SITE PARAMETERS File 14 7 Figure 21 1 Site Parameters Edit option SYSTEMS MANAGER MENU EVE Task Manager XUTM MGR Taskman Management Utilities XUTM UTIL Edit Taskman Parameters XUTM PARAMETER EDIT Site Parameters Edit XUTM BVPAIR System managers must enter one set of site parameters into the TASKMAN SITE PARAMETERS file 14 7 for each Manager that runs in a different Volume Set CPU This set of parameters tells each Manager how it should process tasks The parameters are organized both by Volume Set and by CPU This allows two CPUs that share a Volume Set to be treated differently if one is more powerful than the other 21 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration BOX VOLUME PAIR The BOX VOLUME PAIR field identifies a Volume Set and the CPU on which it 1s available It contains the name of a Volume Set concatenated to the CPU box name first the Volume Set name and then the CPU name For example if the Volume Set name is KRN and the name of the CPU e g box is ISC6A1 then the BOX VOLUME PAIR would be KRN ISC6A1 For systems on which each CPU tends to have a unique Volume Set and vice versa you can enter just the Volume Set name e g PSA or AAA This field s value for the current process can be found by doing GETENV ZOSV and checking the fo
116. check for July 1995 Kernel Systems Management Guide 22 35 Revised June 2008 Version 8 0 TaskMan System Management Operation the routine s existence is done by the Submanager prior to starting the task TaskMan State Messages When the Manager does not run all background processing grinds to a halt For this reason the Manager s condition is of vital importance to system managers When problems are detected with background processing at a site checking the Manager s condition should be the first step The Manager periodically records its state in the Status List The Monitor TaskMan option XUTM ZTMON displays this list near the top of the screen The various states and their meanings are described in the topics that follow BALANCE State The Manager lists itself in this state if other Managers that are processing the same files appear to have more CPU capacity available than the current Manager While in the BALANCE state the Manager does not process any tasks or start any new Submanagers The Manager removes itself from the BALANCE state when it appears to have at least as much CPU capacity as the active Manager In general when many Managers are working out of the same TASKS 14 4 and SCHEDULE files most of them will be in the BALANCE state at any given time with only the one or two least loaded Managers actually processing tasks REF For more information about TaskMan load balancing please refer to the Multiple
117. cleanup to run automatically each night XUTM QCLEAN has been distributed to provide this feature XUTM QCLEAN should not be run interactively indeed it is not available from any of TaskMan s menus To queue this option use Schedule Unschedule Options to queue it to run The date XUTM QCLEAN starts purging the TASKS file 14 4 is controlled by the DAYS TO KEEP OLD TASKS parameter in the VOLUME SET file 14 5 A value of seven days is recommended XUTM QCLEAN does not need an output device therefore you can leave that field blank Once set up the task automatically runs periodically cleaning out inactive task entries that are older than the time period specified in the DAYS TO KEEP OLD TASKS parameter If you want to run this on all of your machines create an entry in the OPTION SCHEDULING file 19 2 for each machine on which you want to run it July 1995 Kernel Systems Management Guide 22 17 Revised June 2008 Version 8 0 TaskMan System Management Operation Scheduling Options TaskMan lets you the site manager schedule options that run regularly as tasks Menu Manager and TaskMan work together to give you this ability All you have to do is tell TaskMan which option you want to queue and how you want to queue it Which Options to Queue The first requirement for queuing regards the option type Only the run print and action types of options can be queued The second requirement is that the option if a run or action type m
118. command s used in line Missing argument to a command post conditional Command missing an argument Extended reference Block structure mismatch Reference to routine That isn t in this UCI Bad Number Access to SSVN s restricted to Kernel NO V H AANAAN ANN AANN NAAN NN NN NN NM NNN NNN NA NUNEZ EZM gH Hgg Agg Hm m m m m mj A FA Flow Chart Entire Routine Option The Flow Chart Entire Routine option XTFCR generates a flow chart showing the processing performed within an entire routine 26 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Routine Tools The following corresponding direct mode utility can be used in programmer mode gt D XTFCR Flow Chart From Entry Point Option The Flow Chart from Entry Point option XTFCE generates a flow chart of the processing performed from a specified entry point to its termination of processing It also allows the user to expand the code in other routines or entry points referenced by DO or GOTO commands The following corresponding direct mode utility can be used in programmer mode gt D XTFCE Editing Routines Group Routine Edit Option The Group Routine Edit option XTRGRPE calls the XTRGRPE routine to edit a group of routines Once several routines are identified the Kernel Toolkit Z editor is called This option is locked with XUPROGMODE The corresponding direct mode utility can be used in programmer mo
119. cross reference Thus Verify codes are not necessarily unique between users while Access codes are 3 30 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 4 Electronic Signatures User Interface An electronic signature is a security tool that software applications can use as an additional identification check Software can for example require that an electronic signature be applied to a particular form or document before subsequent processing can continue If you need create an electronic signature for yourself you can choose the Electronic Signature code Edit option XUSESIG available from the User s Toolbox menu You can enter a new electronic signature code or change an existing code The length of the code must be between 6 and 20 uppercase characters Requiring all uppercase allows the code to be verified with either uppercase or lowercase input since lowercase will be converted to uppercase in the matching process You should choose a code that other users are not likely to guess as this code verifies that it 1s actually you who are signing off on some important action Figure 4 1 Electronic Signature code Edit option SYSTEM COMMAND OPTIONS XUCOMMAND User s Toolbox TBOX XUSERTOOLS Electronic Signature code Edit XUSESIG The Electronic Signature code Edit option XUSESIG also allows you to edit the following fields INITIAL SIGNATURE BLOCK PRINTED NAME SIGNATUR
120. device here DEVICE Requested time to print NOW lt Enter gt Request queued After you answer this series of prompts the output is queued for TaskMan to start at the requested time and you can continue with other work while TaskMan prints the output When many tasks need the same device at the same time TaskMan runs them in order based on the time they were requested July 1995 Kernel Systems Management Guide 19 1 Revised June 2008 Version 8 0 TaskMan User Interface Other Sources of Tasks An application can create other kinds of tasks without your interaction The application might offer to queue other kinds of work like large filing or complex data analysis jobs Sometimes applications queue tasks without asking For example the delivery of MailMan messages is performed by a job running as a task If that task 1s not running when someone uses the MailMan options MailMan automatically uses their foreground job to queue the task without asking them Although people may knowingly or unknowingly queue these other kinds of tasks output remains the most common kind of work to queue Working with Tasks Figure 19 2 TaskMan User option System Command Options XUCOMMAND User s Toolbox TBOX XUSERTOOLS TaskMan User XUTM USER TaskMan also allows you to examine or modify your own tasks You can do this by using the TaskMan User option XUTM USER located in the User s Toolbox menu on your Common menu T
121. e Alerts provide an integrated notification system e Device Handler provides a common device interface e Electronic Signature Codes provide a secure electronic approval system e File Access Security system manages access to VA FileMan files e Kernel Installation and Distribution System KIDS provides an application distribution and installation system e Menu Manager provides a common menu management system e Signon Security organizes users and allows secure logons e TaskMan provides a common job queuing system Kernel provides the system manager the means to manage a secure multi user M based computer system Some typical daily tasks performed by system managers using Kernel system management tools include e Setting up accounts for new users and terminating accounts for expired users e Adding and subtracting options from users menus e Controlling file access for users e Monitoring TaskMan task queues e Terminating unwanted tasks e Monitoring devices e Creating and modifying links to output devices in the DEVICE file 3 5 e Installing software applications 1 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Introduction Within chapters and sub chapters of this manual you can find general user information in the User Interface topic and system manager information in the System Management topic REF For information on developer tools e g Direct Mode Utilities and Applicatio
122. each step that the Manager goes through when it starts or restarts and reports the results If your Manager is failing to start this screen should identify any problem with the environment July 1995 Kernel Systems Management Guide 22 13 Revised June 2008 Version 8 0 TaskMan System Management Operation Figure 22 14 Check TaskMan s Environment option Second screen Here is the information that TaskMan has A Operating Systems Openi T This group identifies the Volume Set ROU current TaskMan Cpu volume Pair ROU KDAISC6A2 operating environment TaskMan Files UCI and Volume Set VAH ROU Log Tasks N Submanager Retention Time 30 Min Submanager Count 10 Taskman Hang Between New Jobs 1 TaskMan running as a type TaskMan is using VAX DSM environment ISC6A2 important to TaskMan TaskMan is using SSCACHE for load balancing Balance Interval 10 This group reports the values of some Kernel site CENERAL parameters that are Logons Inhibited This group shows if logons Taskman Job Limit 35 are being inhibited and ae o pa lence oe how many partitions are urrent number of active jobs available End of listing Press RETURN to continue The second screen see Figure 22 14 reports more information about the current TaskMan environment The first group of four items identifies the current TaskMan operating environment The next group of items reports the values of some Kernel site parameters that are important
123. eee 3 16 Figure 3 15 Screen 1 of Edit an Existing User Option 0 cccccccssssssssssssessseeeecceeeeeeeeeeeaaaasasssesseeeeeeeees 3 18 Figure 3 16 VA FileMan Line Editor Sample user dialogue cc ceeccccccccccceeseeeeeeceeeeeeaeeeseeeeeeeees 3 21 Fieure 3 17 User Management menu opuionssncccac ine ee ee 3 24 Figure 3 18 User Management Menu Options csiccenciicucosnateavenasactawsainadieestheeJonaehidienns wxsneombendanceteueeanthensee 3 26 Picute 3 lt 19 Sample Keme Sren Om Woe Tepi ear a A 3 27 Figure 3 20 CPU Seryice User Device Stats Opu Oiss i A E A 3 28 Figure 3 21 Purge Log of Old Access and Verify Codes option ssssessesessssseseseeerererrererererererererrrrereeee 3 29 Figure 4 1 Electronic Signature code Edit Option ccccccccsssssssecceccccceeasesseeceeeeeeeaeeeseceeeeeseaaeeeeeeeseeaas 4 1 July 1995 Kernel Systems Management Guide XXi Revised June 2008 Version 8 0 Figures and Tables Pietre 4 2 User Edit menu oponi esena E A censedoawebaed ars 4 2 FPieure 5 1 Sample VA FileMan ment Options osii deine eee nana ioe 5 1 Figure 5 2 User has not been granted security access to any Va fileMan files Sample user dilaogue 5 2 Poue S A Pile ACCess SeCunty MENU OPUONS oa a bea ad patoabeatediael eae 5 9 Pioure 5 4 KIL bine DIS V Saiiple COG sneer aidan een ena 5 11 Figure 5 5 Updating file access settings before conversion ccsssssesesssseeeeccecceeceeeeeaaaaaasssseseseeeeeeess 5 12
124. electronic signature code This option is locked with the XUMGR security key This option can be used to clear a user s electronic signature code if the user has forgotten the code The user can then enter a new code with the Electronic Signature code Edit option XUSESIG in the User s Toolbox menu 4 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 5 File Access Security The File Access Security system is an optional Kernel module It provides an enhanced security mechanism for controlling user access to VA FileMan files REF For more information on File Access Security please refer to the VA FileMan Version 22 0 and Kernel Version 8 0 File Access Security supplemental documentation located on the VHA Software Document Library VDL at the following Web address http www va gov vdl application asp appid 5 User Interface As a user you typically access VistA data by use of application options You enter data into files and retrieve information from files through the menu options within the software Except under a few unusual circumstances your use of the system will not be affected by the File Access Security system If you need to work directly with files by using VA FileMan options however you will be affected VA FileMan options provide direct access to data files Figure 5 1 lists some sample VA FileMan options Figure 5 1 Sample VA FileMan menu options Select VA FileMan Option
125. entry in the OPTION file 19 but items on menus are themselves pointers to other entries in the OPTION file 19 You should also understand the difference between types of options be familiar with menu trees and be sufficiently reluctant to assign great numbers of secondary menus Delegate s Menu To delegate options to users you need to be assigned a menu called Delegate s Menu Management XQSMD USER MENU which is located under the Secure Menu Management menu The options on the Delegate s Menu Management menu are as follows Figure 9 1 Delegate s Menu Management options Delegate s Menu Management XOSMD USER MENU Build a New Menu XOSMD BUILD MENU Fdit a User s Options XOSMD EDIT OPTIONS Copy Everything About an Option to a New Option XOCOPYOP Copy One Users Menus and Keys to others XQSMD COPY USER Limited File Manager Options Build XOSMD LIMITED FM OPTIONS Each of these options on the delegate s menu is discussed in the topics that follow Edit a User s Options Using the Edit a User s Options option XQSMD EDIT OPTIONS allows you to edit a user s primary and secondary menus This is the chief method you can use to add and subtract options on your users menus Most of your work will be in adding and deleting options on your users secondary menus You are only able to add or delete options from a user s secondary menu if the option in question has been delegated to you That means that you do not h
126. error log Figure 13 10 Choosing to examine the operating system s error log Sample user dialogue Do you want to check the OPERATING SYSTEM ERROR TRAP too NO Interactive Print of Error Messages Option The Interactive Print of Error Messages option XUERTRP PRINT ERRS provides for an interactive print of the first n of occurrences of an error where n is user selectable over a specified date range July 1995 Kernel Systems Management Guide 13 7 Revised June 2008 Version 8 0 Error Processing 13 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 lil Device Handler July 1995 Kernel Systems Management Guide M 1 Revised June 2008 Version 8 0 Device Handler M 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 14 Device Handler User Interface Applications that are designed for the Kernel environment perform output in a consistent manner using Kernel s Device Handler This ensures consistency both for how you are asked to select devices for output and also for how output is actually performed When you respond to the DEVICE prompt you are using the Device Handler Printing to Devices At the DEVICE prompt to send output to your terminal you can simply press the lt Enter gt key This tells the Device Handler to display the report on the home device that is on your terminal as shown below Figure 14 1 Choosing the home device HEVTORS
127. group of options to delegate to them You also need to assign not delegate the Delegate s Menu Management menu XQSMD USER MENU to the delegate this menu gives delegates the means to assign delegated options to users July 1995 Kernel Systems Management Guide 9 7 Revised June 2008 Version 8 0 Secure Menu Delegation Figure 9 4 Delegating Options Select Options to be Delegated option Sample user dialogue Select Secure Menu Delegation Option Select Options to be Delegated Enter the name s of your delegate s one at a time Name KRNUSER THREE Name KRNUSER FOUR Name lt Enter gt Enter options you wish to DELEGATE TO these users Add option s XUINQUIRE Add option s XUUSERACC Add option s lt Enter gt For the following user s 1 KRNUSER THREE 2 KRNUSER FOUR You will delegate the following options XUINQUIRE Inquire XUUSERACC Diagram Menus Delegated by KRNUSER FIVE on Jul 21 2004 3 55 PM Ready to delegate these options to these people Y lt Enter gt Request to add delegated options has been queued task 465 named KRNUSER FIVE adding delegated options Delegating Security Keys If options that you intend to delegate are locked with security keys you need to delegate the matching keys to the delegate otherwise the delegate will not be able to assign keys to unlock options they have assigned to their users If the option is locked with a security key that you possess the Select
128. has dropped it saves the task in a list of tasks waiting for that Volume Set and checks periodically to see whether it has been restored When the link recovers the Manager will send in sequence all the waiting tasks to the other Volume Set The Manager never actually runs the task but merely places it in a list as a task now available to be run by a Submanager Submanagers Submanagers are the processes that actually run tasks A Manager starts Submanagers whenever more are needed to handle the current workload of tasks and they only last as long as they are needed Submanagers loop back and forth between finding new tasks to run and running them To run each task the Submanager first removes the task from the list of waiting tasks on which it reside e g the Job or the I O list Then it looks up the task s entry in the TASKS file 414 4 unloading all of the information about the task If the task needs a device the Submanager calls the Device Handler to get ownership of it and issues a USE command for it Then the Submanager sets up the partition for the task and does the following e Sets the priority e Cleans out unwanted variables e Sets up requested variables e Prints a page header on the device if one was requested etc Next the Submanager starts the task running at the task s entry point The Submanager uses a DO command and runs the task s entry point in its own partition When the task finishes the Submanager cleans
129. have made available to you Kernel s menu system is what is used to make VistA applications e g Scheduling Nursing and Personnel available to users July 1995 Kernel Systems Management Guide 1 1 Revised June 2008 Version 8 0 Introduction To produce output from VistA applications e g to printers or to the terminal screen Kernel provides a common device interface called the Device Handler To queue a job rather than run it directly the Device Handler links to a common queuing system called TaskMan This manual contains information about these and other parts of Kernel The intent of this manual is to help you learn to use Kernel and take fullest advantage of the facilities it provides This manual also includes information for system managers and developers to find the information of interest to you the general user look for chapters and sub chapters containing the phrase User Interface in their titles ADP Application Coordinators ADPACs may want to skim through the Kernel Systems Management Guide and concentrate on the user interface chapters and sub chapters particularly issues concerning every Kernel user e g signon process and menu navigation System Manager Introduction Kernel provides the backbone of an M computing platform providing a mechanism to organize M programs as options and a way to organize those options into a menu system for users Kernel provides the following major system management components
130. improves the value of the various error logging systems as indicators of significant events deserving investigation Allocation and store errors are often not logged in Kernel s ERROR LOG file 3 075 because the process of logging errors is complicated and usually requires the use of local variables Local variables take up space and there is no excess space when these errors occur However TaskMan makes its simple entries in the Taskman Error Log prior to calling the Kernel error logging utility Thus these errors are often recorded in the Taskman Error Log but not Kernel s You are encouraged to carefully monitor both places 22 24 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Show Error Log Option Figure 22 24 Show Error Log option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Show Error Log XUTM ERROR SHOW The Show Error Log option XUTM ERROR SHOW displays the errors currently stored in the Taskman Error Log showing the date and time that the error occurred in a readable format and showing the error message After the listing the option gives the number of errors in the error log Errors stored in the Taskman Error Log historically are also cross referenced to the TASKS file 14 4 linking tasks to the errors they cause Clean Error Log Over Range
131. in the future Primary menus can be customized with security keys REF For more information on security keys please refer to the Security Keys chapter in this manual If there are a few menu options that require special privilege they can be locked and the security keys assigned to the appropriate users In this way a smaller number of primary menus can serve the needs of a larger number of users Also while putting new master menus onto users secondary menus can be a quick fix it is not a good idea to do this Too many options on a user s secondary menu can be cumbersome for the user In addition in the long run it is easier for IRM to manage access to a menu reached from a few well defined primary menus than to manage access to a menu reached from a large number of users secondary menus Assigning Secondary Menus An easy way to allocate menu options is to assign them to users individually as SECONDARY MENU OPTIONS Secondary options are unique for each user and are stored in a multiple in the user s NEW PERSON file 200 entry Assignment of SECONDARY MENU OPTIONS should be limited to the essential few and should not involve deep structures with multiple levels Instead new primary menus should be built or existing ones modified During menu jumping all branches of both the primary and secondary menu trees are searched each time a jump request is received by the menu system Greater efficiency and user convenience will result
132. in which case every Manager must check access to it when they start up e A task needs to run on the Volume Set in which case the Manager must look up how to get the task there The following is what we have set up for FORUM 21 3 Sample Volume Set setup on FORUM VOLUME SET 14 5 VOLUME SET ROU INHIBIT LOGONS NO LINK ACCESS JNO TASKMAN FILES UCI VAH DAYS TO KEEP OLD TASKS 1 TYPE GENERAL PURPOSE VOLUME SET SIGNON PRODUCTION VOLUME SET Yes UCI ASSOCIATION 14 6 Empty TASKMAN SITE PARAMETERS 14 7 BOX VOLUME PAIR ROU FORFORUM1 LOG TASKS NO O SUBMANAGER RETENTION TIME 60 TASKMAN JOB LIMIT 400 TASKMAN HANG BETWEEN NEW JOBS 1 MODE OF TASKMAN GENERAL PROCESSOR OUT OF SERVICE NO MIN SUBMANAGER CNT 10 LOAD BALANCE ROUTINE SSCACHE IAC Auto Delete Tasks Yes Manager Startup Delay 30 The value of PZOSE VOL is FOR VOLUME SET The VOLUME SET field should be set to the name of a Volume Set It is used in extended global references to reach this Volume Set and can be used in UCI switching software to move Submanagers between UCIs If you are unsure how your Volume Sets are named you can look at the value of A ZOSF VOL in the Volume Set in question 21 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration TYPE The TYPE field is used to help resolve where tasks should run it should properly identify the type of the Volume Set
133. is contained within the file It will not permit the adding of new entries to the file Examples of the VA FileMan options that this property controls are as follows e Enter or Edit File Entries DIEDIT e Transfer Entries DITRANSFER To transfer text the user needs READ access to the file from which text is being transferred Similarly WRITE access is needed for the file to which entries are being transferred with this option Transfer File Entries transfer to file Compare Merge File Entries These are the six levels of access Any or all can be enabled for each of the user s accessible files This is done by changing the field value from NULL to YES This flag is overridden for developers whose DUZ 0 Granting the READ WRITE DELETE and LAYGO levels of access permits adding and deleting file entries as well as editing their attribute field data values This is true unless the attribute field has been protected If so e if there is READ WRITE or DELETE protection within the data dictionary DD for a given field the user s FILE MANAGER ACCESS CODE field 3 DUZ Q is checked Access is denied if the user s DUZ 0 does not contain a character matching the field protection Again DUZ O overrides this restriction The DATA DICTIONARY DD and AUDIT levels of access pertain to the structure of the file itself While this provides a generous scope for VA FileMan data dictionary DD modification
134. menu you can use the Fix Option File Pointers option XQOPTFIX see Figure 7 10 to remove any dangling pointers that may have been left in the Item multiple Running this option is an alternative to having VA FileMan update the pointers each time an individual option is deleted Figure 7 10 Fix Option File Pointers option Sample user dialogue Select OPTION NAME ZZTEST3 lt Enter gt Test Option NAME ZZTEST3 SURE YOU WANT TO DELETE THE ENTIRE ZZTEST3 OPTION Y lt Enter gt YES SINCE THE DELETED ENTRY MAY HAVE BEEN POINTED TO BY ENTRIES IN THE USER FILE ETC DO YOU WANT THOSE POINTERS UPDATED WHICH COULD TAKE QUITE A WHILE NO lt Enter gt Testing a User s Menus Figure 7 11 Switch Identities option User Management XUSER Switch Identities XUTESTUSER You can test a user s menus using the Switch Identities option XUTESTUSER It lets you test the user s menus and security keys It does not allow you to execute any bottom level menu options however it only lets you navigate menu trees You are reminded at each prompt whose menu it is that you are testing To exit this mode and return to your own menus simply enter an asterisk July 1995 Kernel Systems Management Guide 7 9 Revised June 2008 Version 8 0 Menu Manager System Management Managing Out Of Order Option Sets Figure 7 12 Out Of Order Set Management menu options Menu Management XUMAINT Out Of Order
135. more than one Institution the user will be prompted at signon to select a division In this way the local variable DUZ 2 can be set to the appropriate value If the user s DIVISION field Multiple is blank the DEFAULT INSTITUTION field File 8989 3 is used to define DUZ 2 Since the INSTITUTION file 4 contains a pointer to the AGENCY file 4 11 the signed on user s agency affiliation can also be determined The KERNEL SYSTEM PARAMETERS file 8989 3 also contains a field named AGENCY This field is not a pointer but is instead a SET OF CODES e g N for Navy This field is presented for editing during Kernel installation Its value is used at signon to set the DUZ AG local variable Thus the agency associated with the overall Kernel system can be determined AUTO MENU The AUTO MENU flag stored in the local variable DUZ AUTO is used by Menu Manager to control whether all items on a menu are presented automatically after each cycle through the menu system If the items are not displayed the user can always invoke the display by entering a question mark New users often like to see all the menu choices Experienced users probably do not need to see the choices and the display can be suppressed to save system resources The user setting for AUTO 3 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management MENU in the NEW PERSON file 200 will override any compara
136. name itself Figure 17 3 Spool document name prompt DEVICE SPOOL Select SPOOL DOCUMENT NAME To skip the Select SPOOL DOCUMENT NAME prompt you can specify the spool document name at the DEVICE prompt by entering the name in the second semicolon piece A name entered here is not used if the spooler is set up to generate names itself however Because of the format used the Device Handler knows that a spool document name rather than a device subtype is being specified Subtypes begin with one or two letters followed by a dash e g P DEC while spool document names cannot Figure 17 4 Specifying the spool device and document name DEVICE SPOOL MYDOC DEVICE SPOOL P OTHER80 MYDOC If the computing environment is composed of several networked processors you may need to specify where spooling should take place The spooler on the current CPU should be chosen unless the output is queued Figure 17 5 Spooling output to a spool device on the same CPU DEVICE SPOOL 1 SPOOL AAA 2 SPOOL BBB Choose 1 2 gt If the output is queued you can choose a spooler on another CPU and a time to schedule the job to run Figure 17 6 Queuing output to a spool device DEVICE Q DEVICE SPOOL BBB 17 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Spooling Figure 17 7 Spooler Parameters at the Device prompt Summary DEVICE Spooler DEVICE Spooler Right Margin Page Length DEVIC
137. not been granted any security access to VA FileMan files INPUT TO WHAT FILE In this case you need to contact IRM and be granted access to the VA FileMan files you need File Access Security is also invoked when an option uses the VA FileMan line editor In particular the Transfer Lines from Another Document option on the line editor s Edit menu does not permit access to other word processing documents in the current file or other files unless READ access to that file has been explicitly granted If you need to transfer text from other files using the line editor contact IRM to request access to those files 5 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security System Management Prior to introduction of the File Access Security system user access to VA FileMan files through VA FileMan options was controlled by matching a character in a user s FILE MANAGER ACCESS CODE field 3 the DUZ O string in the NEW PERSON file 200 with a character in the file s top level file security fields Kernel s optional File Access Security system uses a different method It allows you to control access to files for any user using VA FileMan options directly Access is granted or denied by adding or removing a file from a user s ACCESSIBLE FILE Multiple field 32 in their NEW PERSON file 200 entry The File Access Security system does not affect access to files through non VA FileMan options
138. number username IO value date time UCI Volume Set error type last global reference and the line of code that caused the error It then prompts for a listing of variables enter L to list all or a letter such as X to list those starting with 13 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Error Processing X The listing can be printed to the screen or to an output device You can page through the screen listing one screen at a time and enter Q to quit or enter to exit at the end of each screen A restore feature can be invoked by entering R provided that the user is working in programmer mode Programmer mode is required as a protection against restoration of variables from within the menu system To the extent possible the environment at the time of the error is restored with the routine and local symbol table intact Figure 13 9 Local symbol table help Which symbol gt Enter O to EXIT nsr to return to the last question Leading character s of symbol s you wish to examine S to get a display of the system variables Te COs obtain es ust OL all Symbols R to restore the symbol table and and enter direct mode After reviewing the error log you are given the opportunity to examine the operating system s error log Now that most VistA applications record their errors in Kernel s error log however there is less need to track VistA errors in the operating system
139. occur regardless of how variables may have been NEWed beforehand Stack levels for the routine call stack are recorded in the error trap in the STACK variable The descriptions of the Error Processing menu option topics that follow are arranged in the same order as the options appear on the Error Processing menu XUERRS Figure 13 5 Error processing options SYSTEMS MANAGER MENU EVE Programmer Options XUPROG Error Processing XUERRS P1 Print 1 occurrence of Gach error for T 1 QUEUE XUERTRP PRINT T 1 1 ERR P2 Print 2 occurrences of errors on T 1 QUEUED XUERTRP PRINT T 1 2 ERR Clean Error Trap XUERTRP CLEAN Error Trap Display XUERTRAP Interactive Print of Error Messages XUERTRP PRINT ERRS Print 1 Occurrence of Each Error for T 1 QUEUE Option The Print 1 occurrence of each error for T 1 QUEUE option XUERTRP PRINT T 1 1 ERR lists the first occurrence of each error recorded on the previous day T 1 represents Today 1 Yesterday You can queue it to run shortly after midnight If a device is specified the output is sent to the specified device If a device is not specified the output is placed in a mail message and sent to the individual who queued the option to run It should be set to automatically requeue at a 1 day D interval 13 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Error Processing Print 2 Occurrences of Errors on T 1 QUEUED Option
140. on each menu are not displayed TY PE AHEAD This setting controls whether characters you type faster than the system can process end up being processed or not Normally you should set TYPE AHEAD to YES so that keystrokes you enter are not lost due to system slowness TEXT TERMINATOR The TEXT TERMINATOR is a setting used by VA FileMan s Line editor When you are using the Line editor and are importing text from an external source you may not want a blank line to indicate the end of file which could prematurely terminate the text transfer By default the TEXT TERMINATOR in the VA FileMan line editor is the carriage return character lt Enter gt Setting this to another character string like ZZ something that will not be encountered in the target text can permit downloading without interruption If you change the setting of the TEXT TERMINATOR from the default of the carriage return character you will need to remember your TEXT TERMINATOR when using the Line editor otherwise you will be unable to exit the Line editor REF For more information on the TEXT TERMINATOR please refer to the VA FileMan Getting Started Manual PREFERRED EDITOR You can choose which editor Kernel uses when you edit word processing fields on the system You can choose any editor defined on your system VERIFY CODE You can change your VERIFY CODE by answering YES to this field First enter your current VERIFY CODE then enter a new VERIFY CODE You will be a
141. operating system dependent You can use the corresponding direct mode utility XTER from programmer mode The error trap tries to capture a description of the error the local symbol table the last global reference and other signon statistics For Cach ZC calls are used to record IO counts CPU time and page faults Figure 13 8 Error trap display option Sample user dialogue In response to the DATE prompt you can enter S to specify text to be matched in error or routine name Which date gt T 1 1 error logged on 2 9 95 1 lt ECODETRAP gt PRGMODE 5 Z0SV 2 07 41 52 KDE KDE 20801D46 _TNA4523 No disconnect error Which error gt 1 Process ID 2020107A 538972282 JAN 18 1992 17 19 21 Username EXAMPLE Process Name VISTA User UCI VOL NXT NXT ISC6A2 NXT KDAISC6A2 SZA 0 SZB AOT Current SEO _TNA4523 Current ZIO LTA 001294201 96A CPU time CRNIN Page Faults 1204 Direct WO Q1 Buriered 170 96 SZE lt ECODETRAP gt PRGMODE 5 ZOSV 2 D XQZ G OUT Last Global Ref XUSEC 0 CUR 24 2950209 074142 Which symbol gt Errors can be reported by searching for a date range or character string Question marks show a count of errors for the selected range Two question marks exclude disconnects and three include disconnects A string search could be used to find XQ in all routines or an UNDEF in the definition of all errors Once an error is identified the report generator shows the job
142. output to an HFS device if such a device type has been established on the system Depending upon how IRM defines the HFS device you may be prompted for a host file name and for an input output operation Figure 16 1 Choosing a Host File Server HFS device Sample user dialogue DEVICE HFS lt Enter gt DISK FILE HOST FILE NAME TMP TMP lt Enter gt INPUT OUTPUT OPERATION Enter one of the following host file input output operation READONLY NEWVERSION READ WRITE Not all input output modes are available on all systems The possible modes for input output operation work as follows Table 16 1 HFS input output modes of operation APPEND Data from a WRITE operation will be appended to the file MIXED Both READs and WRITEs are allowed for the specified file NEWVERSION A new file will be created with a higher version number this file can be used for WRITEs only READ READs are allowed from the specified file WRITEs are not allowed READONLY READs are allowed from the specified file WRITEs are not allowed READ WRITE Both READs and WRITEs are allowed for the specified file if a WRITE operation is performed output is appended to the file WRITE WRITEs are allowed output can be sent to the specified file July 1995 Kernel Systems Management Guide 16 1 Revised June 2008 Version 8 0 Host Files System Management To provide access to host files through the Device Handler set up device entries of type HFS Th
143. package now stores static package information The only part of the PACKAGE file 9 4 entry that installations update automatically now is the VERSION field Multiple A patch sent with KIDS does not transport the entire PACKAGE file 9 4 entry It only sends the information that is needed to update the PACKAGE file 9 4 Patch installations will update the PATCH APPLICATION HISTORY field Multiple which is within the VERSION field Multiple KIDS saves patch names along with their sequence numbers in this multiple Most other fields have been designated for removal at the top level of the PACKAGE file 9 4 The PACKAGE file 9 4 now stores mainly static software information that is not version specific as well as the patch history of the software Transport Mechanism Distributions Distributions are the mechanism KIDS uses to export software They are more flexible than the previous mechanism INIT routines Distributions are usually in the form of an HFS file The developer creates transport globals from build entries KIDS stores transport globals in a global KIDS can WRITE the global in a format readable only by KIDS to an HFS file the HFS file is the distribution The HFS file can then be distributed by a variety of methods including FTP file transfer protocol diskette and tape For example if your system is a PC you can also move the Transport Global to a new medium 1 e to multiple floppy disks so you can install on
144. process chart 2 of 2 IF USER AT THIS PROMPT ANSWERS TERM term entered at Step 3 lt Enter gt to accept default Correct synonym term The entry made at this step must be in all upper case letters Select SYNONYM term synonym was entered for lt Enter gt COFrEece Return to the menu The following are examples of what might appear on your screen when using the Add Modify Utility option The first example is for a new shortcut entry the second example shows a new keyword entry and the third shows the editing of an existing synonym entry Example 1 Illustration of a new Shortcut entry Figure 25 17 Shortcut option Sample user entries SH Shortcuts KE Keywords SY Synonyms Select Add Modify Utility Option SH lt Enter gt Shortcuts Additions Modifications to Shortcuts in which file CPT Select LOCAL SHORTCUT FREQUENTLY USED NARRATIVE COUGH ARE YOU ADDING COUGH AS A NEW LOCAL SHORTCUT Y lt Enter gt YES LOCAL SHORTCUT FREQUENTLY USED NARRATIVE COUGH lt Enter gt LOCAL SHORTCUT ENTRY 31659 Searching tor a GEPET 31659 BRONCHOSCOPIC PROCEDURES OK YES lt Enter gt YES 25 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU Example 2 Illustration of a new Keyword entry Figure 25 18 Keyword option Sample user entries SH Shortcuts KE Keywords SY Synonyms Select Add Modify Utility Option KE lt Enter g
145. protocols Network Channel Device Edit Figure 18 10 Network Channel Device Edit option Device Management XUTIO J Edit Devices by Specific Types XUDEVEDIT Network Channel Device Edit XUDEVEDITCHAN The Network Channel Device Edit option XUDEVEDITCHAN allows you to edit network channel device attributes When editing Network Channel devices the contents of the SUBTYPE FORM FEED BACK SPACE MARGIN WIDTH and PAGE LENGTH fields are not necessarily needed for using Network Channel devices However these fields are provided in case the application calling the Device Handler is not able to distinguish between a printer and a Network Channel device when sending output The timeout on the M open command may not be applicable with network channel devices Therefore it may be necessary to answer NO to the USE TIMEOUT ON OPENS field REF For more information about device timeout applicability please refer to the appropriate Cach manual For Network Channel devices that use TCP IP data is required for the OPEN PARAMETERS field For the client device setup this field stores the remote Internet address to which the host connects July 1995 Kernel Systems Management Guide 18 11 Revised June 2008 Version 8 0 Special Device Issues REF For examples of the type of data required for these fields please refer to the System Management topic under the Network Channel Devices topic in this chapter Figure
146. r E E N 2 9 Display User Characteristics Option sssssssoeeesssssssooerrsssssseeeresssssseceressssssseeeressssssecereessssseeeee 2 11 SWK UCT OPIO eesi a a teers Sree tree rie evar nant eee ert ne Tiie 2 12 gt PISHON SECUIMY SY Stemi Management ecrini n r aee au rE a 3 1 SEO OMe FOC CS eoo E sat cnease acme tens salt oneaoee ia clestacneMnstaanaata casein 3 1 Introductory Torenia a E A a 3 1 Parameters Checked dunne SISMON ax aon oow su a N AaS 3 2 XU USERSIGN ON OPON ngea ea a a a enn Hite iets 3 7 Clearall sers attrap ONION yi epealinniutiesbaseseedtbuatcamians omtenraluneheaeatttalans 3 8 Enaphne and Disabling Log ons srci a 3 8 Addn IN W USCS aiian a ecel te uiaal hata Metals 3 8 Add a New User to the System Option ccccccsssssssscccccceneesssecccccesaeeesseecceeeseeeeesseeceess 3 9 GrantAccess by Profle Opu0nxi5an es cies ceo ew aieioece 3 9 SC CUTIE FOr naa a tenes se bGeantmen a ease oe acen wana taan eave teeon 3 10 Edane an Existing User pion orse tidevastecenentdinomalgalceetshucbele 3 17 July 1995 Kernel Systems Management Guide 1X Revised June 2008 Version 8 0 Contents Additional Attributes Editable by Users cc ccseeesseccccccceeeeeeeceeececaeeeenseeceseeeeaeeenses 3 23 Edit User Characteristics Form and Template cticins ccacs ccasesedcicen oct eavaedcgaresoeeiaeiiiecnentiievselen 3 23 Deactvatine and React vatine USCS cdnn as eome ds iachacsseteennet neu 3 24 Perc ies
147. responding Checking the Task List There are 5 tasks currently running Enter monitor action UPDATE 7 Status List The Status List is where each Manager periodically reports its current status The job number of the Manager is reported both for ease of location on a system status report and also to distinguish between multiple Managers 1f there are more than one Under normal circumstances the Manager removes its entry from the Status List when it shuts down but if a Manager stops abnormally e g RJD or FORCEX its entry is usually left on the list The list is updated and cleaned out whenever a new Manager is started or restarted 22 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation The status of a Manager consists of three parts e Date and time This date and time should equal the RUN node s date and time and like that node it should be close to the current HOROLOG e Manager s state e Description of special circumstances The Manager can be in one of five states at any given time e BALANCE e ERROR e PAUSE e RUN e WAIT RUN is the normal state with a description of Main Loop The Manager s status is the most important piece of information the monitor gives and it should always be the first thing checked when troubleshooting problems REF For a detailed list and description of the possible state messages please refer to the Trou
148. routine The option can then be reviewed to discover the name of the routine that was calling DIP Table 7 2 Menu Manger variables always defined XQABTST Flag that signals whether alpha beta testing is in effect XQDIC Internal entry number IEN of the option s parent which must be a menu in the OPTION file if an option is executing If the user is in a menu XQDIC is set to the IEN of the current menu s parent unless they are in their primary menu in which case XQDIC is set to the IEN of the primary menu The value of XQDIC also corresponds to the second subscript in the display nodes portion of the XUTL global XUTL XQO for the menu in question XQPSM Like XQDIC a lookup value into the second subscript of XUTL the compiled menu global XQPSM points to the tree of the target option in the jump It resulted from the ability to jump to any option not just ones on the primary menu tree It can help identify X jumps from a primary secondary or Common option Current option s type e g M for menu A for action XQUR User s response to the menu prompt replaces A 7 20 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management XQUSER User s name in the form SEVEN A KRNUSER XQY Internal entry number IEN of the current option or menu replaces Y XQY0 First node subscript of zero of the current option replaces Y 0 XQXFLG Contains several flags i
149. running One of the following messages may show up if the task needs some system resource not currently available e Waiting for hunt group s lt list of hunt groups gt e Waiting for device lt name of device gt e Waiting for the link to lt name of CPU gt to be restored When you display the status of a task waiting for a device TaskMan shows you how many tasks are in line for that device ahead of your task Additional statuses exist for tasks that have encountered some kind of problem For each situation it lists a different explanation of the problem For example if you use the Stop task option to stop a task its status shows up as Stopped by you Stopping Tasks Under certain conditions you may want to stop a task The TaskMan User option allows you to do this through the Stop task option ST Your ability to stop a task depends on the task s status however If the task has already been stopped is finished or it encountered a problem while running and you try to stop it the Stop task option tells you that the task has already stopped If the task has not yet started running on the other hand you can always stop it If the task has started running the Stop task option will succeed in stopping it only if the developer who wrote the task has designed the task to be stopped by a user At any rate it does not cause any problems if you try to stop a running task To stop a task use the Stop task option Once you stop a tas
150. s auto generated Access code and the name of the service section coordinator who can answer questions 2 The Computer Access Policy A contract to which users must adhere It states the terms of granting access to sensitive information the user must accept these terms as a condition of being given system access These security forms are stored in the XUSER COMPUTER ACCOUNT help frame and should be edited for local use as follows 1 Copy the XUSER COMPUTER ACCOUNT help frame into a new site help frame e g SFO COMPUTER ACCOUNT 2 Edit the security forms for local use Replace the placeholder text with the actual name and address of the facility 3 Repoint the Kernel Parameter to the new site XUSER COMPUTER ACCOUNT help frame using VA FileMan 3 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management For example Figure 3 9 Security Forms Sample user entries 1 of 4 gt D XUP Setting up programmer environment This is a TEST account Terminal Type set to C VT320 You have 13 new messages Select OPTION NAME SYSTEMS MANAGER MENU Device Management Programmer Options Operations Management Spool Management Information Security Officer Menu Taskman Management User Management Application Utilities Capacity Management Manage Mailman Menu Management VA FileMan Verifier Tools Menu Select Systems Manager Menu Option VA FileMan VA FileMan Vers
151. set up mappings for new terminals or to map different terminals to a common type For example a site could map all codes returned by all DEC VT type terminals to a single C VT102 type terminal type The DA RETURN CODES file 3 22 is a small static file managed by the DA Return Code Edit option XU DA EDIT You can use the DA Return Code Edit option to automate the population of the DA RETURN CODES file 3 22 When you select this option the terminal you are using is queried and you are shown the terminal s DA code response You are then asked for the terminal type and description for this return code Enter the terminal type name for the terminal you are using The option updates the DA RETURN CODES file 3 22 and all terminals responding with this code will be recognized at signon You can quickly populate the DA RETURN CODES file 3 22 by using this option from several different types of terminals Kernel pre populates the DA RETURN CODES file 3 22 with a set of standard Terminal Type entries You may need to add more entries as needed to handle all terminals at your site July 1995 Kernel Systems Management Guide 15 11 Revised June 2008 Version 8 0 Device Handler System Management Troubleshooting Figure 15 8 Device management Troubleshooting options SYSTEM MANAGER MENU EVE Device Management XUTIO Loopback Test of Device Port XUTLOOPBACK Send Test Pattern to Terminal XUTTEST Out of Service Set Clear XU
152. shown below Figure 26 1 Routine Tools menu options SYSTEMS MANAGER MENU EVE Programmer Options lt locked with XUPROG gt XUPROG Routine Tools XUPR ROUTINE TOOLS SIndex of Routines XUINDEX Compare local national checksums report Compare routines on tape to disk Compare two routines Delete Routines lt locked with XUPROGMODE gt Flow Chart Entire Routine Flow Chart from Entry Point Group Routine Edit lt locked with XUPROGMODE gt Input routines lt locked with XUPROG gt List Routines Load refresh checksum values into ROUTINE file Output routines Routine Edit lt locked with XUPROGMODE gt Routines by Patch Number Variable changer lt locked with XUPROGMODE gt Version Number Update lt locked with XUPROGMODE gt XU CHECKSUM REPORT XUPR RTN TAPE CMP XT ROUTINE COMPARE XTRDEL XTFCR XTFCE XTRGRPE XUROUTINE IN XUPRROU XU CHECKSUM LOAD XUROUTINE OUT XUPR RTN EDIT XUPR RTN PATCH XT VARIABLE CHANGER XT VERSION NUMBER These options are documented below grouped by routine type July 1995 Kernel Systems Management Guide 26 1 Revised June 2008 Version 8 0 Routine Tools User Interface Analyzing Routines XINDEX oIndex of Routines Option Kernel Toolkit s XINDEX utility formerly known as INDEX utility Index of Routines option XUINDEX is a verification tool for developers It reviews a routine according to the 1995 ANSI M Standard a
153. stamp and an explanation where necessary Several of the codes correspond to the status of the SCHEDULE file entry for the task If all applications used the Program Interface the status code would always agree with the task s real status In fact many applications still directly manipulate ZTSCH and ZTSK and they often neglect to update the status codes Whenever the SCHEDULE file disagrees with the status code the SCHEDULE file is correct This is the reason many of the codes listed in Table 22 6 have multiple meanings Status codes through 6 represent one of two common paths a task takes through TaskMan The other common path replaces code 3 with A where the task s device is not immediately available Table 22 6 TaskMan task status codes Status Code Incomplete or still being created Scheduled for lt date and time gt TaskMan uses this status in every option and entry point that schedules a task If the task fails or errors out and TaskMan cannot trap the error this status has a different meaning Stopped irregularly while scheduled Being inspected by TaskMan The Manager sets this status when the time comes for a task to run As it removes the task from the SCHEDULE file it sets this code into the task Being prepared The Submanager gives a task this code when it removes the task from the Job list or Busy Device Waiting list in order to run it Currently running The Submanager gives a task this status ju
154. subsequently change your mind you can use the Requeue Tasks option XUTM REQ to requeue the task exactly the way that it was You can also use this option to change some of the details of a task that is already queued As with XUTM DQ you are first prompted for a Task Number with the same help available Here you can only enter a single task not a range The task is then displayed and you are asked for a new run time with the default being either the original or current run time whichever applies The next question is Do you wish to requeue this task to a device with the default depending on whether the task originally requested an output device If you answer YES the option asks you to specify an output device using the original output device if there was one as a default The option also allows you to adjust the task s priority The task is requeued according to your specifications Requeuing involves completely dequeuing the task so that your task does not run twice making the changes you requested and placing the task back on the Schedule List Notice that the task is not dequeued until after you specify the changes you want to make If you want to modify a task that may start running soon it is usually a good idea to dequeue it first The ZTMQ security key affects this option in two ways e Users who do not hold the security key are limited to requeuing only their own tasks e Users are not prompted to change the priority July
155. the choices you made if you say to proceed a task is queued that removes the options you selected from the delegates you specified 9 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Secure Menu Delegation Specify Allowable New Menu Prefix Option Use the Specify Allowable New Menu Prefix option to assign allowable menu prefixes to your delegates Your delegates need to be given allowable new menu prefixes if they e Build new menus e Copy options e Create options from VA FileMan templates Typically if your delegate works with one particular software application you would assign them that software s namespace as an allowable prefix Options that the delegate creates must then be prefixed with that namespace appended with a Z If you do not specify an allowable prefix for a delegate they will not be able to use the following options e Build a New Menu e Copy Everything About an Option to a New Option e Limited File Manager Options Build You can specify multiple new menu prefixes for a given delegate Reports You can use the following options to generate reports about delegates on your system e List Delegated Options and their Users Sort by delegated option e Print All Delegates and their Options Sort by delegate name e Show a Delegate s Options Display all delegated options for one delegate July 1995 Kernel Systems Management Guide 9 1 Revised June 2008 Version 8 0 Secure
156. the load is used to tell the Submanagers on those CPUs that they too should wait A LTSCH LOGRSRC This node flags whether Submanagers should log resources for the capacity management software This node is set for every Volume Set whenever the LOG RESOURCE USAGE field of the KERNEL SYSTEM PARAMETERS file 8989 3 is edited A cross reference keeps the ZTSCH LOGRSRC node in synchronization with the LOG RESOURCE USAGE field A ZTSCH NO OPTION if set this node stops the Submanagers from running any scheduled options This is for the KIDS install process 22 28 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation A LZTSCH RUN This node is where the Manager periodically stamps the current time leaving a way to determine whether it is currently active Invoking the XUTM STOP option removes this node see Figure 22 28 AMZTSCH STARTUP UCI option This node holds the Startup List This list holds the internal number of all options that are specially queued to run every time the Manager starts up The HOROLOG value reflects when the option was placed on this list AMZTSCH STATUS J of Manager This node holds the Status List This list holds the periodically updated entries for each Manager active on your machine and reflects each Manager s own perception of its current state A ZTSCH STOP This node prevents Submanagers from running While it
157. the operating system s spool area If the user s line limit is not exceeded before initiating the report Kernel permits sending of an unlimited amount of output to the operating system s spooler This should be considered by IRM when granting spooling privileges Users who are allowed to spool should be trained accordingly Users need to anticipate the results of a process they send to the spooler If they are not sure what to expect they should be instructed to test the process by sending it directly to an output device If unexpected results such as an endless loop or meaningless sort should occur they can interrupt and cancel the process Users should also be advised about appropriate use of processing time Methods of efficient VA FileMan searching and sorting should be used when invoking the spooler Gust as when printing directly For example as described in the VA FileMan documentation the first sort by field should be a cross referenced field when possible and search criteria should be specified with the most likely conditions first 17 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Spooling Granting Spooling Privileges Options on the Spool Management menu can be used to grant spooling privileges to users Figure 17 11 Edit User s Spooler Access option SYSTEMS MANAGER MENU EVE Spool Management XU SPL MGR Egit User s Spooler Access XU SPL USER The ability to invoke the spo
158. to lt volume set name gt Is The other key check in the setup code is to ensure that all down Volume Sets listed in the VOLUME SET file 14 5 as required can actually be reached The Manager tests each required link and enters the PAUSE state if any tests cause an error The Manager remains in the PAUSE state periodically testing the links until they are restored Logons Inhibited When the system manager sets the INHIBIT LOGONS field of the VOLUME SET file 14 5 TaskMan enters a PAUSE state and waits until the flag is cleared No Signons Allowed The system manager can use the software switch to stop logons which places TaskMan in the PAUSE state RUN State The RUN state indicates that the Manager is going about its business in a relatively normal manner managing background tasks on your system Table 22 9 TaskMan RUN states RUN State Description Start The Manager sets this value before and after executing the setup code at system startup Setup The Manager identifies when it executes the setup code to test its environment The Manager sets this value after executing the setup code during a restart Main Loop This should be the Manager s usual state This indicates the Manager is executing the main loop that checks the environment processes the Schedule list and performs idle loop activities when appropriate TaskMan Job Limit When the total number of processes on the Manager s CPU exceeds the TaskMan Job Limi
159. to TaskMan REF These parameters as well as all the other parameters that TaskMan uses are described in detail in the TASKMAN SITE PARAMETERS File 14 7 topic in the TaskMan System Management Configuration chapter in this manual The last four items show if logons are being inhibited and how many partitions TaskMan currently has to work with These values show how busy your system is as well as how busy it can become Their importance is also described in the discussion of parameters Restart Task Manager Option Figure 22 15 Restart Task Manager option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Restart Task Manager XUTM RESTART The Manager generally starts automatically when your system comes up If the Manager crashes or is stopped you can use the Restart Task Manager option XUTM RESTART to restart it The option first checks the RUN node and calculates whether it thinks the Manager is currently running If this option believes the Manager is running it will ask you if you are sure you want to restart another TaskMan you must answer YES to start the Manager If XUTM RESTART thinks the Manager has stopped it will ask 22 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation you for confirmation before jobbing out a new Manager If XUTM RESTART believes the Manager to be activ
160. trap the error this status has a different meaning Stopped irregularly while waiting for a link Edited without being scheduled The Requeue Tasks KUTM REQ and TaskMan User KUTM USER options and the REQ ZTLOAD entry point use this status when edited tasks are not subsequently rescheduled July 1995 Kernel Systems Management Guide 22 33 Revised June 2008 Version 8 0 TaskMan System Management Operation Status Code Discarded by TaskMan because its record was incomplete The Manager or the Submanager uses this status for tasks listed in the SCHEDULE file that lack critical information in the corresponding TASKS file 14 4 entries Currently being edited This status has been set aside for possible use in future versions of TaskMan Created without being scheduled The ZTLOAD entry point uses this status for tasks when the application passes ZTDTH Kernel Toolkit utility ZTMOVE uses this value for the tasks it creates to transfer routines between Volume Sets manually before starting it The Manager does not yet record a corresponding status for the analogous situation Tasks that never start that are left with a status of 2 have usually caused the Manager an error while it tried to examine them Waiting for a partition on a Compute Server The Manager gives a task this code when it places the task in the Compute Server Job List If the task fails or errors out and TaskMan cannot trap the error
161. used for options in a user s secondary menu tree A pointer in the node XUTL XQ J T indicates which option in this list of numbered nodes the menu driver is currently using This pointer is set and reset by the menu driver as the user moves up and down the menu tree In the example XUPROGMODE is the option that the menu driver is currently using Other XQ nodes of the global that have a non numeric third subscript are used to store various pieces of Kernel information that are set up at signon XKUTL XQ J XQM points to the user s primary menu 7 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management In the following example Figure 7 22 the user s primary menu is OPTION file 19 entry 29 Figure 7 22 User Stack example XUTL XQ 541065826 0 2970113081624 XUTL XQ 541065826 1 29P29 EVE Systems Manager M nu SMS Boe Oe eee AEA XUTL XQ0 541065826 2 31P29 XKUPROG Programmer Options M XUP ROG ANARA OA XUTL XQ0 541065826 3 49P29 XUPROGMODE Programmer mode R OO RUE ROGCMOD Ee Oren Oe n s X0 541065826 DUZ 63 XO DAOC S826 DUA O ELPP XO 541065826 DUAZ Z 16000 SKUTE PXU LE XUTL OC daly XUTL SXUTE SKUTE UXO 7 De LUGO 626 TION TNAS LOS ROA DANO OO OL G Lobo XO S41 065826 10 42 5C 2 77 917 50 p44 2 lr oly TZ XO 841065626 10M 79 SC 8 XUTL XUTL XUTL XUTL SK
162. will print the description of the patch All the displayed information comes from the PACKAGE file 9 4 Figure 24 7 Display Patches for a Package option Sample user dialogue Select Utilities Option Display Patches for a Package Select PACKAGE NAME KERNEL Select VERSION 8 0 lt Enter gt OV Z S95 Do you want to see the Descriptions NO lt Enter gt DEVICE HOME lt Enter gt SYSTEM PACKAGE KERNEL Oct 09 2004 1 32 pm PATCH INSTALLED INSTALLED BY KRNUSER TEN KRNUSER NINE KRNUSER NINE KRNUSER NINE KRNUSER TEN KRNUSER ELEVEN KRNUSER TEN KRNUSER NINE KRNUSER TEN KRNUSER ELEVEN KRNUSER TEN KRNUSER NINE Purge Build or Install Files Option Each KIDS installation adds one entry to the BUILD 9 6 and INSTALL 9 7 files for every transport global installed from the distribution You can use the Purge Build or Install Files option XPD PURGE FILE to purge entries in these files The first question the option asks is which file to purge the BUILD 9 6 or INSTALL file 9 7 Choose one of these files The next question asked is the number of versions to retain July 1995 Kernel Systems Management Guide 24 7 Revised June 2008 Version 8 0 KIDS System Management Utilities Versions to Retain When you choose to retain some number entries for a software application the option must decide which entries are most recent The Purge Install or Build Files option uses numeric order based on so
163. 0 Dye mileage Enter F dot file at the edit prompt to change files When saving with dot file an edit comment can be entered This text is stored in the EDIT HISTORY multiple in the ROUTINE file 9 8 as programmer documentation The following example shows how an entire routine can be displayed by entering the ZP print command followed by a space at the M prompt Dot file File is then used to file A dot is then used to exit The dot exit does not automatically file changes Figure 28 3 Z Editor Displaying a routine using the ZP command gt ZL ZZTEST ASZ 6Z Editing ZZTEST Terminal type C VT100 Edit ZP lt SPACE gt lt Enter gt ZZTEST test routine Length 20 lt Enter gt Line ZZTEST ZZTEST test routine Edit Insert after ZZTEST lt Enter gt First either a lt tab gt or line Line next line label is entered Line oO Line lt Enter gt Edit File ZZTEST Edit comment 1 gt This text is stored in the Routine file s Edit History multiple lt Enter gt 2 gt lt Enter gt EDIT Option lt Enter gt Edit lt Enter gt gt Routines are filed by the name used when loading not by the first line tag If a ROUTINE file 9 8 exists then the routine is added if not already there and an entry is made of the date time and DUZ of the user that filed it When filing the editor updates the third piece of the first line of the routine with the date time July 1995 Kernel Systems Manageme
164. 10 18 13 18 14 18 16 22 33 22 35 ASK HES I O OPERATION Field 16 2 ASK HOST FILE Field 16 2 ASK PARAMETERS Field 16 2 Cross references 15 12 Fields 15 2 Global Location 15 1 Mixed OS Environment Fields 15 5 NAME Field 01 15 2 OPEN PARAMETERS Field 15 4 OpenVMS Specific DEVICE Fields 15 7 POST CLOSE EXECUTE Field 15 2 15 4 18 3 PRE OPEN EXECUTE Field 15 2 15 4 15 5 QUEUING Field 15 4 SIGN ON S YSTEM DEVICE Field 15 4 15 10 15 13 SUBTYPE Field 15 1 15 2 15 4 15 8 18 10 18 11 TYPE Field 15 2 15 3 USE PARAMETERS Field 15 4 VOLUME SET CPU Field 15 2 15 3 15 4 Device File Entries 18 16 DOMAIN 4 2 5 11 5 13 ERROR LOG 3 075 13 2 13 5 22 24 ERROR MESSAGES 3 076 13 5 Exported 3 18 FAILED ACCESS ATTEMPTS LOG 3 05 3 28 3 29 File Access Security Conversion Instructions 5 13 FORUM ROUTINE 9 8 23 12 24 12 26 7 FUNCTION 5 3 20 HELP FRAME 9 2 12 4 12 6 Host 16 1 How to Grant Access 5 8 ICD DIAGNOSIS 80 25 1 25 2 ICD OPERATION PROCEDURE 80 1 25 1 INSTALL 9 7 23 4 23 5 23 7 23 9 23 17 23 19 23 20 23 21 24 3 24 7 24 9 INSTITUTION 4 3 6 KERNEL PARAMETERS 8989 2 3 23 July 1995 Kernel Systems Management Guide Index 13 Revised June 2008 Index 14 Index KERNEL SYSTEM PARAMETERS 8989 3 3 1 3 2 3 3 3 4 3 5 3 6 3 7 3 9 3 23 21 3 22 28 KIDS 23 4 Levels of File Access Security 5 5 LOCAL KEYWORD 8984 1
165. 12 5 Assigning De assigning Help Frame Editors cccccccccccccsssseeeecececeeaeeseseceeeeesaaaeeneeees 12 5 Dirk Spice Concern S cass h outs cde tiara leh a S 12 6 Creatine and Editi ne Help Frame S sac cciaxeat decrsannitacieht nasdaq cuiasastesossionsetewe aeaa 12 6 T EATON Pr OCES SVG ccisurs cotta ane daclilg eho T sanes aceael Mop a a Saco 13 1 July 1995 Kernel Systems Management Guide xiii Revised June 2008 Version 8 0 Contents User Titer ACE icone aes n NN dnd ee can baista eaiecmeataeenads 13 1 Sy Ste Ma Wana 6 CMe MU tesa cataracts E E A E E nel ae E EE E S E 13 2 EnO SCE I eea a a a seers 13 2 Ean ieee TLL Er o a A A ee ue tne ee aneaaes 13 4 Print 1 Occurrence of Each Error for T 1 QUEUE Option eseesssssssssssssssssssseeereessses 13 4 Print 2 Occurrences of Errors on T 1 QUEUED Option eeeesssessssssssssesssseserrrresssssss 13 5 Clean Error Trap ODIOM caan a poke opie etaencaiesaae 13 5 Error Trap Display pu iisasssncecssnste savant A actos andes vesnech eaucnaceanheins oonceds 13 6 Interactive Print of Error Messages Option eeeeseeessssssssssssssseseeereersssssssssssssssssseseeeee 13 7 II Device Handler seeniori eeose EEE E AE EE EN E ERa HI 1 t4 Device Handler User IME iC Osaketa E E N 14 1 Panone 10 DOVES E E S 14 1 OUE UME oraa a ere set ee mnt aT Te nenare enn aT ee 14 3 SPCOU Vill Sa SPECIAL SUDLY De eea aa a 14 4 Alternate Syntax for Device Specification nesses a eras yi E a a 1
166. 15 12 00 L 12 00 Noon on the 15th and last days every 3 months W 4pm Each Wednesday at 4 pm Problems With Scheduled Options Once an option has been put on a schedule it stays on that schedule unless one of the following happens e You delete the task e The running task aborts while setting up the next task in the sequence the schedule sequence is broken e You dequeue the task that is scheduled to run the option You must either requeue the task or use the Schedule Unschedule Options option to start the cycle over e You change the value in the RESCHEDULE FREQUENCY field The new increment is used beginning after the next time the option runs e You change the value in the QUEUED TO RUN AT WHAT TIME field The currently scheduled task will be unscheduled and a new one will be scheduled for the time you specify Another peculiarity in this process involves using a monthly scheduling frequency What should happen if on January 31st you queue an option and give it a monthly scheduling frequency Other months lack a July 1995 Kernel Systems Management Guide 22 23 Revised June 2008 Version 8 0 TaskMan System Management Operation 31st day In this situation the task pretends there is a 31st day in every month To avoid this you can use the RESCHEDULE FREQUENCY code 1M L time One time Option Queue Option Figure 22 23 One time Option Queue option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR
167. 18 16 18 18 20 7 21 13 22 20 I Field 15 1 15 2 15 3 15 4 15 10 15 12 15 13 16 2 17 9 18 10 18 13 18 14 18 16 22 33 22 35 ASK HES I O OPERATION Field 16 2 ASK HOST FILE Field 16 2 ASK PARAMETERS Field 16 2 Cross references 15 12 Fields 15 2 Global Location 15 1 Identification 15 12 Mixed OS Environment Fields 15 5 NAME Field 01 15 2 OPEN PARAMETERS Field 15 4 OpenVMS Specific DEVICE Fields 15 7 POST CLOSE EXECUTE Field 15 2 15 4 PRE OPEN EXECUTE Field 15 2 15 4 15 5 PRIORITY AT RUN TIME Field 21 13 QUEUING Field 15 4 SIGN ON S YSTEM DEVICE Field 15 4 TaskMan Configuration 21 13 TASKMAN PRINT A HEADER PAGE Field 21 13 TYPE Field 15 2 15 3 21 13 USE PARAMETERS Field 15 4 VOLUME SET CPU Field 15 2 15 3 15 4 21 13 DEVICE FOR QUEUED JOB OUTPUT Field 22 19 22 20 Device Handler 1 2 3 5 3 20 7 4 7 18 14 1 14 4 14 7 15 1 15 2 15 4 15 9 15 10 15 11 15 12 16 2 17 2 18 6 18 7 18 8 18 9 18 11 18 13 18 16 18 17 20 3 Alternate Syntax 14 6 DA Return Codes 15 11 Home Device 15 10 Influence on TaskMan 21 13 Loopback Test 15 12 Out of Service Devices 15 12 Page Length 14 2 Queuing 14 3 Right Margin 14 2 Security Devices 15 7 Selecting Devices 15 11 Spool Document Formats 14 6 Subtypes 14 4 Summary 14 7 System Management 15 1 Terminal Type Information Retained by User 15 10 Test Pattern 15 12 Troubleshooting 15 12 User Interface 14
168. 1995 Kernel Systems Management Guide 22 5 Revised June 2008 Version 8 0 TaskMan System Management Operation Delete Tasks Option Figure 22 6 Delete Tasks option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Delete Tasks XUTM DEL The Delete Tasks option XUTM DEL has the same structure as the Dequeue Tasks option The only difference is that where dequeuing a task just removes it from the lists unschedules it the Delete Tasks option also deletes the task from the TASKS file 14 4 When you have deleted a task there is no reference to that task anywhere in TaskMan s files Only holders of the ZTMQ security key can delete any task Others can only delete their own tasks as identified by their DUZ Cleanup Task List Option Figure 22 7 Cleanup Task List option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Cleanup Task List XUTM TL CLEAN You can use the Cleanup Task List option XUTM TL CLEAN to remove a task entry from a task list for a job that is no longer running This might happen when a process is forcibly exited but TaskMan still believes the task is running You can use this option to tell TaskMan which tasks you forcibly exited TaskMan then removes those tasks from its list of running tasks 22 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Taskman Management Utilities A su
169. 2 23 17 23 21 24 7 24 9 24 11 24 12 26 7 Purging 24 7 July 1995 Revised June 2008 Index Build File Print Option 24 2 Build Primary Menu Trees Option 7 13 Building Options 9 5 BULLETIN File 3 6 11 4 11 8 Bulletins Server Request 11 1 11 2 11 4 11 5 11 8 11 9 XQSERVER 11 4 11 8 BYPASS DEVICE LOCK OUT Field 3 2 C Cach Systems DCL Context 21 15 ENVIRONMENT FOR DCL Field 21 5 Cache VMS DCL Context Setup 21 15 Calculate and Show Checksum Values Option Programmer Options Menu 27 3 Callout Boxes xxxiv Calls ZC 13 6 CAN DELETE WITHOUT PROCESSING Field 1 10 7 CAN MAKE INTO A MAIL MESSAGE Field 3 22 Can Server Requests Be Denied 11 1 Change my Division Option 2 8 Change user s allocated keys to delegated keys Option 8 3 Changes in the Role of the PACKAGE File 9 4 KIDS 23 5 Characteristics of Intended Users 9 5 CHCK XTSUMBLD Direct Mode Utility 27 4 CHCK1 XTSUMBLD API 27 3 27 4 CHCKSUM XTSUMBLD API 27 3 27 4 Check Taskman s Environment Option 22 13 CHECKI XTSUMBLD API 23 12 24 11 26 6 Checkpoints KIDS 23 20 CHECKSUM REPORT Field 26 6 CHECKSUM REPORT Field 6 24 10 CHECKSUM VALUE Field 26 6 CHECKSUM XTSUMBLD API 27 4 Checksums 23 7 24 9 26 8 27 3 28 5 KIDS 23 12 24 11 Choosing Options 6 1 Clean Error Log Over Range Of Dates Option 22 25 Clean Error Trap Option 13 5 Kernel Systems Management Guide Index 3 Version 8 0 Index Clean
170. 2 5 NICK NAME Field 2 9 3 18 No Options Node 22 28 Nodes AQZIS 14 5 LOGON volume set 3 8 AMLOSF 22 37 AGLOSF VOL 21 6 A ZTVSK task 0 20 7 A LZTVSK task 3 20 7 XUSEC 0 CUR DUZ DATE 7 13 SXUTL XQ J T Node 7 16 SXUTL XQ J XQM Node 7 16 Compute Server Job List 22 27 Device Allocation List 22 27 Device Waiting List 22 28 Display 7 16 7 17 Error Log 22 27 Error Screens 22 28 Idle 22 28 Job List 22 28 Jump 7 16 7 19 Link List 22 28 Load 22 28 Index 24 Kernel Systems Management Guide Version 8 0 Load List 22 28 Log Resources 22 28 No Options 22 28 RUN 20 6 22 8 22 9 22 14 22 29 Schedule List 22 27 Startup List 22 29 Status List 22 29 Stop 22 29 Sub 22 29 Task List 22 29 Taskman Error Log 22 27 Update 22 29 User Stacks 7 16 Wait 22 29 XQ 7 16 XQT MENU Templates 7 17 Normal Signoff 2 5 NULL Device 15 6 NVSTNSET Routine 15 7 O Obtaining Data Dictionary Listings xxxv OFFICE PHONE Field 2 9 3 22 4 1 OLD ACCESS AND VERIFY CODES File 200 XREF 3 29 Once the Installation Finishes KIDS 23 19 One time Option Queue Option 22 24 Online Documentation XXXV Technical Information How to Obtain xxxv OPEN EXECUTE Field TERMINAL TYPE File 3 2 14 7 15 8 18 16 18 17 OPEN PARAMETERS Field DEVICE File 3 5 15 4 15 9 16 2 17 9 18 3 18 10 18 11 OPEN PRINTER PORT Field 18 16 18 17 OpenVMS Interactive Logins Parameter 3
171. 25 Revised June 2008 Version 8 0 Signon Security System Management Purging Mail and Security Keys for Inactive Users You can use the Purge Inactive Users Attributes option XUSERPURGEATT to clean up files It removes all mailboxes messages mail groups and security keys for users who have been terminated If any of these users still retain Access codes they are deleted This is particularly significant with mail A mail message cannot be completely removed from a system until all recipients have deleted it from their mail baskets If a user is no longer active then it becomes unlikely that the message will ever get purged There are two modes of running this option You can VERIFY the process for each user that the computer selects as eligible If you choose not to verify the process for each user then for every user with a non future TERMINATION DATE their set of security keys mail groups messages and mail baskets will be deleted Reactivating Users You can use the Reactivate a User option XUSERREACT to re enable access for a user who has either been terminated or whose access has been temporarily disabled To re enable access for someone whose account is merely disabled with the DISUSER field set to YES use this option to simply clear the DISUSER field Otherwise using this option you can fill in all the fields needed for an active account i e FILE MANAGER ACCESS CODE field 3 PRIMARY MENU OPTION etc When yo
172. 28 1 Revised June 2008 Version 8 0 Miscellaneous Programmer Tools Test an option not in your menu Option The Test an option not in your menu option XT OPTION TEST is used for in house testing of options only It allows the selection of an option from the OPTION file 19 and then executes it This option is locked with the XUMGER security key CAUTION No security checks are performed in the XT OPTION TEST option therefore it should only be given to programmers REF Kernel Toolkit Application Programming Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml 28 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Miscellaneous Programmer Tools A 7 Editor User Interface The Z editor routine editor is installed in the Manager account as the Z global by ZTMGRSET during installation It can also be installed with D ZTEDIT To use the editor load the routine it must pre exist and then X Z The following example creates a one line routine in Cach and then calls the A Z Editor Figure 28 2 Calling the Z Editor Sample user entries gt ZR The editor fills in the third gt ZS ZZTEST date time that the routine is gt ZL ZZTEST X filed 6Z Editing ZZTEST Terminal type C VT10
173. 3 OpenVMS Specific DEVICE Fields DEVICE File 3 5 15 7 Operations Management Menu 3 26 23 23 Option Access by User Option 7 6 Option Audit Display Option 7 4 OPTION File 19 3 20 6 3 6 5 6 9 7 1 7 2 7 3 7 4 7 8 7 9 7 14 7 15 7 16 7 17 7 18 7 19 8 2 9 2 9 10 11 1 11 2 11 6 11 8 11 9 12 6 12 7 22 19 22 22 28 2 Dangling Pointers 7 9 12 5 Option Restrictions 6 3 July 1995 Revised June 2008 July 1995 Revised June 2008 Option Scheduling Deleting and requeuing 22 19 List Background Options 22 18 One time Option Queue Option 22 24 PARENT OF QUEUABLE OPTIONS Menu 22 18 Problems 22 23 Queuing an option 22 19 Schedule Unschedule Options Option 22 19 Scheduling Frequency Code Formats 22 22 Special Queueing settings 22 22 TaskMan 22 18 Through the OPTION SCHEDULING File 19 2 TaskMan 20 2 Which Options to Queue 22 18 OPTION SCHEDULING File 19 2 7 13 10 7 20 1 20 2 20 7 22 17 22 18 22 19 22 20 22 22 Options Index of Routines 26 2 ACTION 28 5 Actual Usage of Alpha Beta Test Options 23 23 Add a New User 3 9 Add a New User to the System 3 9 Add Entries To Look Up File 25 8 25 9 Example 25 12 Multi Term Look Up MTLU 25 1 Add Error Screens 13 3 Add Modify Utility 25 8 25 12 Multi Term Lookup MTLU 25 2 Multi Term Look Up MTLU Examples 25 18 Alert Management 10 4 10 6 Alerts Set Remove Surrogate for User 10 6
174. 3 2 holds device vendor specific code to characterize a terminal type For example escape sequences can be entered in the OPEN EXECUTE and CLOSE EXECUTE fields to set pitch or font Every device in the DEVICE file 3 5 must be assigned a terminal type in the SUBTYPE field The most common fields to populate for TERMINAL TYPE file 3 2 entries are e NAME e SELECTABLE AT SIGN ON e RIGHT MARGIN e FORM FEED e PAGE LENGTH e BACK SPACE e OPEN EXECUTE e CLOSE EXECUTE The TERMINAL TYPE file 3 2 has many more fields where additional specific information for particular terminal types can be entered Kernel provides the following options to facilitate creating and editing terminal types Figure 15 6 Terminal type edit options Device Management XUTIO Terminal Type Edit XUTERM Change Device s Terminal Type XUCHANGE List Terminal Types XULIST 15 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler System Management Terminal Type Naming Conventions The convention for naming terminal types is as follows Table 15 4 Terminal type naming conventions Terminal Type Description C Video terminals e g C VT320 Printers with keyboards Printers without keyboards e g P LASER Modems The general format is limited to two alphabetic characters a hyphen and alphanumeric characters As mentioned previously a spool document name cannot use this format t
175. 3 3 Answering Questions 23 16 Global Distributions 23 21 Menu 23 8 Progress 23 19 Progress Bar 23 19 Queued 23 17 Re answering Questions 23 17 Restarting 23 20 Sequence 23 7 Software 23 8 Standard Distributions 23 7 Loading Standard Distributions 23 9 Index 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Transport Globals from a Distribution or PackMan Message 23 7 Once the Installation Finishes 23 19 Options 23 2 OVERWRITE 23 21 Package Definition 23 1 PACKAGE File 9 4 23 5 Patches 23 5 23 6 23 15 24 9 Printing Loaded Transport Globals 23 12 Processing Each Transport Global 23 16 Progress Bar Installations 23 19 Purge Build or Install Files Option 24 7 Purging BUILD File 23 21 INSTALL File 23 21 Selected Entries 24 9 Re answering Installation Questions 23 17 Reasons to Retain BUILD and INSTALL File Entries 24 9 Recovering from an Aborted Distribution Load 23 20 REPLACE 23 21 Restarting Aborted Installations 23 20 Rollup Patches into a Build Option 24 9 ROUTINE File 9 8 24 10 Running Installations 23 16 Scheduling Installations 23 16 Selecting Software Names for Purging 24 8 Software Installation 23 8 Standard Distributions 23 6 23 7 System Management Installations 23 1 Utilities 24 1 Transport Global 23 1 Backup 23 15 Checksums 23 12 Compare 23 3 23 7 23 13 Create 23 2 23 5 24 10 24 11 Definition 23 1 Environment Check 23
176. 3 5 15 4 USER CHARACTERISTICS TEMPLATE 3 23 VERIFY CODE 2 10 3 19 VERSION Multiple 23 5 VMS DEVICE TYPE 63 15 7 VOICE PAGER 2 9 4 1 VOLUME SET VOLUME SET File 14 5 21 6 VOLUME SET CPU DEVICE File 3 5 15 2 15 3 15 4 15 10 15 13 15 14 21 13 22 20 VOLUME SET Multiple KERNEL SYSTEM PARAMETERS File 8989 3 3 3 21 3 8 18 10 18 11 SUPPRESS BULLETIN 224 11 5 SUPPRESS FORM FEED AT CLOSE 18 6 Fields Being Audited Option 5 5 Figures xxi File Access Security 3 17 3 19 5 1 5 2 5 3 Index 12 SYNC FLAG 22 16 TASK PARAMETERS 3 29 10 6 10 7 13 6 22 19 22 21 TASK PARTITION SIZE 21 3 TASKMAN FILES UCL 21 8 TASKMAN FILES VOLUME SET 21 8 TASKMAN HANG BETWEEN NEW JOBS 21 4 TASKMAN JOB LIMIT 3 3 21 2 21 3 TASKMAN PRINT A HEADER PAGE 21 13 TELNET PORT 66 15 7 TERMINATION DATE 3 10 3 22 3 24 3 25 3 26 11 4 TEXT TERMINATOR 2 10 3 23 Access Level 5 5 AUDIT 5 1 5 4 5 5 5 7 5 8 Conversion Advance Preparation 5 10 Advantages 5 10 After 5 15 Instructions 5 13 Summary 5 12 DATA DICTIONARY 5 1 5 4 5 5 5 7 5 8 5 13 DELETE 5 1 5 3 5 4 5 6 5 7 DELETE Access 3 20 5 3 LAYGO 3 18 5 1 5 3 5 4 5 6 5 7 5 13 5 15 7 2 LAYGO Access 5 3 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu 5 8 5 9 5 10 5 13 5 14 5 15 Properties 5 5 READ 5 1 5 4 5 6 5 7 5 15 7 2 READ Access 3 20 5 11 Ru
177. 4 34 01 eke eRe RH Running TaskMan with a DCL Context When run from a DCL context TaskMan runs as an OpenVMS user The Manager runs as a job that originates from a node specific OpenVMS batch queue and by default submits new Submanagers to the same queue as needed 21 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration One advantage to running TaskMan from a DCL context is that it allows jobs to be queued to specific CPUs When a program calls ZTLOAD it can request that the job run on a specific CPU node in your cluster via the ZTCPU input variable Unless you are running TaskMan in a DCL context on Cach systems only this request will probably fail and possibly cause the task not to run When TaskMan runs with a DCL context however the Manager can submit the job as a new submanager to a given CPU s TaskMan batch queue Depending on the ZTSK and ZTSCH mapping multiple Cache environments on the same CPU can each run TaskMan in a DCL context Although TaskMan in each Cache environment shares the same account directory DCL command files and batch queue jobs will run in the environment specified in each environment s ENVIRONMENT FOR DCL site parameter NOTE Kernel Patch XU 8 0 355 added the CACHE2 routine for TaskMan load balancing and provides support for DCL context in Cach Setup for Running TaskMan in a DCL Context in a Cache VMS Envir
178. 4 6 15 Device Handler System Mana Cement senikan a ack GansbinGaaubinadenrtanee 15 1 WT TG ee aaa eres ees eee iet teens se a teach ecneneeebacena 15 1 TERMINAL TYPE File Gi3 2 horren aa a a A 15 8 Terminal Type Namina Convent Ons msie a r en e r A 15 9 How Shared Device and Terminal Type Attributes are Used nonessssseeesssssssseerreesss 15 9 Terminal Type Information Retained by User ou cccccccccceccesessseeseseeeeeeeeeeeeeeeeeaaas 15 10 B eh iavererce 11a Roy bos 010 eeenenee ener r A NTs tre aeeet 15 10 Device Selection at Signon and Virtual Terminal DevViceS ccccccseeeeseeeeeeeeeneeees 15 10 Terminal Type Selecion al SIS Non sss atancedevad nacbia cchanaat desanennededat aaedizpomwnaeeabanest cosa 15 11 TroubleshoounSiisiasciceisietinietrie asses Bannister ae ae cae 15 12 Loopback Festol Device Port Option zesert r ia 15 12 send Test Pattern to Termina OpUONnesirs n e 15 12 OW OL SERVICE Se VE ler OPU Oseaan T eta thee denen stl ceaaaeieeaehs 15 12 Device Identification and Cross Teleren Ces sescesceecserei iieii iiaa enlai r ai 15 12 tO Host FES a E a E teenie ae aaicesnewede eee 16 1 User Tne ICC ena a Cirla ie dh teen ele tad duiagicast 16 1 Dy Ste Mana Se Iie NU e o a neneslasiacne a deat eacoescs 16 2 Host File Server Device Edit Opuon snc citation 16 2 Cacheand OLM HFSDovice Set pises ssc ae a E 16 2 NI SOONG aena a E a A chan A 17 1 XIV Kernel Systems Management Guide July 1995 Ver
179. 414 7 standardized VA Cach and GT M COn HS ur aO Mee S lita na ys A E Aan eieraaseemiene 21 10 Figure 21 8 Customized Header Page routine s onnesssssssoeresesssssceeessssssseeeesssssssecerrsssssssseeeresssssseeees 21 14 Pisure 2i97 Customized Header Pai Ce N AES 21 14 Fissure a UOC ree ae Fi IN og ta a Sate E as asia tase Sam a see esac 21 15 Poore 21 1 Create the TASKMAN Give CtOry Aaea E taiedecettensaacdedeatehanels 21 15 Figure 21 12 Create system logical name for the directory with the COM files cc eeeeeeeeeeeees 21 16 Figure 21 13 Create system logical name for the directory with the COM files eeeeeeeeeeeeeees 21 16 XXVI Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Figures and Tables Figure 21 14 Sample user dialogue to retrieve DCL command files eeccccccecceeeeeeeeeeeeeeeeeees 21 17 Figure 21 15 Sample user dialogue to edit TaskMan parameters 0 ccseeeeeeeeeeeeeeseeeeeeseeeeeeeeens 21 17 Figure 21 16 Z 1 MI2W DEL OM Command Pile sipssacessaiseivessasineanncocuecncaioaesndeseeasadascucanecdineiacasenetnaeteas 21 18 Figure 21 17 ZTMS2WDCLE COM Command Pile sis cciicehescaciccaehacccenthoce nad ngseaiiacd eadsddnceab ddan esthiaadee 21 19 Figure 21 18 Example of OpenVMS User TASKMAN on ALPHA AXP Systems eee 21 20 Figure 21 19 Example of OpenVMS TASKMAN Queue cccccnnseeeeeeeeeeeeeeeeceececeeeeeeaeaaaeeeeeees 21 20 Feur 22 12 ist Pack OPHION s
180. 5 18 Standard Device Chart 25 4 Synonym Option Example 25 19 Synonyms 25 1 25 12 Associated with Multiple Terms 25 2 Multiple Tokens 25 2 Synonyms Option 25 2 25 17 Systems Management 25 20 Usage Considerations 25 2 User Interface 25 3 Utilities for MTLU Menu 25 8 Multi Term Lookup MTLU Main Menu 25 3 Multi Term Lookup MTLU Option 25 1 25 5 Example 25 6 N Name Options 6 3 NAME Field 01 BUILD File 9 6 23 4 DEVICE File 3 5 15 2 15 12 NEW PERSON File 200 3 17 4 2 OPTION File 19 7 3 11 3 July 1995 Kernel Systems Management Guide Index 23 Revised June 2008 Version 8 0 Index PARAMETER DEFINITION file 8989 5 1 10 10 RESOURCES File 3 54 18 13 SECURITY KEY File 19 1 8 5 TERMINAL TYPE File 3 2 15 8 Namespaces Help Frames 12 6 XQSRV 11 5 XUFI 5 12 XUTM TaskMan 20 5 Z 9 11 ZTM TaskMan 20 5 Naming Conventions TERMINAL TYPE File 3 2 15 9 Navigating Kernel s Menus 6 1 Network Channel Device Edit Option 18 11 Network Channel Devices 18 11 Editing 18 11 System Management 18 11 NEW PERSON file 200 2 8 2 12 3 19 NEW PERSON File 200 2 3 2 9 3 1 3 3 3 4 3 5 3 6 3 7 3 8 3 9 3 10 3 17 3 18 3 20 3 24 3 25 3 29 3 30 4 2 5 1 5 2 5 3 5 8 5 9 5 10 5 12 5 13 5 15 6 9 7 7 7 18 8 2 8 4 8 5 8 6 9 8 9 9 11 9 15 10 17 7 22 3 Required Fields 3 9 NEW PERSON IDENTIFIERS Field 3 9 New Revised Help Frames Option 1
181. 6 XUEDIT CHARACTERISTICS Template 3 23 XUEDITOPT Option 11 3 XUERRS Menu 13 4 XUERTRAP Option 13 6 XUERTRP AUTO CLEAN Option 13 5 XUERTRP CLEAN Option 13 5 XUERTRP PRINT ERRS Option 13 7 XUERTRP PRINT T 1 1 ERR Option 13 4 XUERTRP PRINT T 1 2 ERR Option 13 5 XUFI Namespace 5 12 XUFILEACCESS Menu 5 8 5 9 5 10 5 13 5 14 5 15 XUINCON Routine 5 14 XUINDEX Option 26 2 XUKEYALL Option 8 3 XUKEYDEALL Option 8 3 XUKEYEDIT Option 8 4 XUMGER Security Key 3 8 3 9 3 19 4 2 8 3 8 4 9 9 17 7 28 2 XUOPTDISP Option 7 4 July 1995 Revised June 2008 Index XUOPTPURGE Option 7 4 XUOPTUSER Menu 3 26 XUOPTWHO Option 7 6 XUOUT Option 15 12 XUP API 18 3 XUPR RTN EDIT 26 5 XUPR RTN PATCH Option 26 5 XUPRGL Option 28 1 XUPRINT Option 7 5 XUPROG Menu 23 2 26 1 26 3 27 3 XUPROG Security Key 3 22 7 8 8 1 8 2 23 2 26 1 26 8 28 1 XUPROGMODE Option 7 16 XUPROGMODE Security Key 3 22 8 2 13 5 26 1 26 5 26 6 26 8 27 4 28 1 XUPRROU Option 26 6 XUPR ROUTINE TOOLS Menu 26 1 XUPR RTN TAPE CMP Option 26 7 XURESJOB Option 22 10 22 29 XUROUTINE IN Options 26 8 XUROUTINE OUT Option 26 8 XUSC LIST Option 3 27 XUSCLEAN Routine 7 12 XUSCZONK Option 3 28 XUSEC Cross reference 8 5 XUSEC 0 Global 3 29 7 12 XUSEC 0 CUR DUZ DATE 7 13 XUSER COMPUTER ACCOUNT Help Frame 3 10 XUSER DIV CHG Option 2 8 XUSER KEY RE INDEX Option 8 5 XUSER Menu 3 24 5 1 5 8 5 10 5 14
182. 7 POST CLOSE EXECUTE Field DEVICE File 3 5 15 2 15 4 18 3 PREFERRED EDITOR Field 2 10 3 20 3 21 PRE OPEN EXECUTE Field DEVICE File 3 5 15 2 15 4 15 5 Primary Menu 2 2 2 5 2 6 3 1 3 8 3 19 6 1 6 6 6 7 7 5 7 7 7 8 7 16 7 19 7 20 Assigning 3 8 Defining 7 2 Managing 7 7 Rebuilding Menu Trees 7 13 Trees 7 13 7 15 7 19 7 20 PRIMARY MENU OPTION Field 3 1 3 8 3 18 3 19 3 26 9 3 9 4 Print 2 occurrences of errors on T 1 QUEUED Option 13 5 Print All Delegates and their Options 9 11 Print Alpha Beta Errors Date Site Num Rou Err Option 23 23 Print File Entries Option 5 6 Print Option File Option 7 5 Index 32 Kernel Systems Management Guide Version 8 0 Print Options Recommended for Queueing Option TaskMan 22 18 Print Options that are Scheduled to run Option 22 18 Print Server Mode 21 4 PRINT SERVER NAME OR ADDRESS Field 65 15 7 PRINT SERVER Type 21 7 Print Sign on Log Option 3 27 Print task Option 19 5 Print Transport Global Option 23 12 Print Utility Option Multi Term Look Up MTLU 25 1 25 6 Example 25 8 Printer Controller Mode 18 15 Printers Slaved 18 15 18 16 Printing Loaded Transport Globals KIDS 23 12 To Devices 14 1 Printing Routines Routine Tools 26 6 Priority Interactive Users 3 5 PRIORITY AT RUN TIME Field 21 13 PRIORITY Field 3 8 Options 7 3 Server Options 11 3 Privileges Audit 5 8 Spooling 17 1 17 6 17 7 Processing
183. 907 456 possibilities for an 8 character password If you have forgotten your Verify code the site s Information Security Officer ISO should delete the existing code and then instruct you to sign on again At the Verify code prompt simply press the lt Enter gt key without making any other entries You will be prompted to enter a new Verify code and then re prompted to enter the same Verify code again as confirmation If you do not want to bother inventing a Verify code entering a question mark at the Verify code prompt displays a possible although cryptic choice e g DKM1 amp 493 Entering a question mark a second time displays another choice When you log off you re reminded to remember the new Verify code for use at your next signon LOGIN Menu Template You can execute a script of options on your first signon of the day by having a MENU template called LOGIN REF For more information please refer to the Menu Manager User Interface chapter in this manual 2 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security User Interface Signon Shortcuts In roll and scroll VistA to reach the primary menu in one step at the ACCESS CODES prompt you can enter the Access and Verify code as one string separated by a semicolon Figure 2 3 Entering the Access and Verify codes at the same time ACCESS CODES accesscode verifycode Good afternoon You last signed on today at 12 00 To ju
184. AME SPOOL NAME SPOOL AUTO DESPOOL AUTO DESPOOL 1 lt Enter gt YES Select DESPOOL DEVICES Generating Spool Document Names Spool devices can be set up to generate the name that will identify the spool document If this flag is set in the DEVICE file 3 5 users of that device will not be prompted to enter the spool document name Also if the flag is set any user or developer defined name in IO DOC is ignored The generated name consists of the first 15 characters of the spool device s name an underscore _ and the internal entry number IEN of the spool document in the SPOOL DOCUMENT file 3 51 Figure 17 19 Generating spool document name Sample user dialogue NAME SPOOL GENERATE SPL DOC NAME GENERATE SPL DOC NAME YES 17 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 18 Special Device Issues This chapter discusses the following special devices and device issues e Browser Device e Form Feeds e Hunt Groups e Magtape e Network Channel Device Support e Resources e SDP obsolete e Slaved Printers Browser Device User Interface VA FileMan s Browser allows you to view reports on your terminal screen letting you scroll backward and forward through the report and also letting you perform simple searches within the report In the past when you sent a report to the terminal screen you could only go in one direction forward by pressing the lt Enter gt key after
185. ASK HFS I O OPERATION NO FORM FEED BACK SPACE C 8 POST CLOSE EXECUTE D POST DDBRZLS SUBTYPE P BROWSER PRE OPEN EXECUTE I SSTEST DDBRT S ZISQUIT 1 W C 7 Browser not selectable from current terminal 18 4 I DDBR TXT ASK PARAMETERS NO QUEUING NOT ALLOWED ASK HOST FILE N MARGIN WIDTH 80 PAGE LENGTH 99999 OPEN PARAMETERS NEW DELETE TYPE HOST FILE SERVER Kernel Systems Management Guide Version 8 0 July 1995 Revised June 2008 Special Device Issues Form Feeds User Interface Most users would prefer to see their printouts without any extra blank pages before or after Most prefer to see their reports printed on a fresh page instead of starting in the middle of the previous printout The printing of labels should also be accomplished without unnecessary form feeds If a printer is generating extra pages you should contact IRM to remedy the problem July 1995 Kernel Systems Management Guide 18 5 Revised June 2008 Version 8 0 Special Device Issues System Management If a particular device does not need a form feed between reports IRM should set the SUPPRESS FORM FEED AT CLOSE field to YES in the device s DEVICE file 3 5 entry Label printers for example should have this flag set This procedure prevents the Device Handler from issuing a form feed Figure 18 5 Device Edit option Sample user dialogue Select Systems Manager Menu Option Device Handler Select Device Handler
186. Alert on the Fly 10 7 Managing 7 7 Map Pointer Relations 5 6 Mark Option Set Out Of Order 7 10 Menu Management 9 7 Menu Templates Option 6 8 Modify File Attributes 5 6 5 8 Monitor Taskman 21 13 22 7 22 36 Multi Term Lookup MTLU 25 1 25 5 Example 25 6 Multi Term Lookup MTLU Main Menu 25 3 Index Network Channel Device Edit Option 18 11 New Revised Help Frames 12 5 One time Option Queue 22 24 Operations Management 3 26 23 23 Option Access by User 7 6 Option Audit Display 7 4 Options in the Option File that are Out of Order 7 11 Options that Should Be Scheduled 7 12 Options to be Delegated 9 8 OUT OF ORDER MESSAGE Field 2 7 1 Out of Service Set Clear 15 12 Out Of Order Set Management 7 10 Output Routines 26 8 P1 Print 1 occurrence of each error for T 1 QUEUE 13 4 PARENT OF QUEUABLE OPTIONS 3 28 7 1 7 12 17 9 22 18 Patient Alert List for specified date 10 9 Permitted Devices 7 11 Place Taskman in a WAIT State 22 15 Post sign in Text Edit 3 7 Print 2 occurrences of errors on T 1 QUEUED 13 5 Print All Delegates and their Options 9 11 Print Alpha Beta Errors Date Site Num Rou Err 23 23 Print File Entries 5 6 Print Option File 7 5 Print Options Recommended for Queueing TaskMan 22 18 Print Options that are Scheduled to run 22 18 Print Sign on Log 3 27 Print task 19 5 Print Transport Global 23 12 Print Utility Multi Term Look Up M
187. All Keys a User Needs 8 3 All your tasks 22 3 Allocation of Security Keys 8 3 9 9 Alpha Beta Test Option Usage Menu 7 4 23 23 Application Utilities 25 3 Assign Editors 12 5 Audit Features 7 4 Audited Options Purge 7 4 Audits 7 4 Backup a Transport Global 23 15 Build a New Menu 9 4 9 11 Build File Print 24 2 Build Primary Menu Trees 7 13 Building 9 5 Index Calculate and Show Checksum Values Programmer Options Menu 27 3 Change my Division 2 8 Change user s allocated keys to delegated keys 8 3 Check Taskman s Environment Option 22 13 Choosing 6 1 Clean Error Log Over Range Of Dates 22 25 Clean Error Trap 13 5 Clean old Job Nodes in the XUTL 7 12 7 13 Clean Task File 22 17 Cleanup Task List 22 6 Clear all users at startup 3 4 3 8 3 27 Clear Electronic signature code 4 2 Common 2 3 3 19 6 3 6 4 6 5 6 6 6 7 6 8 7 1 7 7 7 8 8 1 8 5 10 1 17 3 17 7 19 2 Redefining 7 7 Compare local national checksums report 23 12 24 11 24 12 26 6 26 7 27 4 Compare Routines on Tape to Disk 26 7 Compare Transport Global to Current System 23 13 Compare Two Routines 26 7 Compare Merge File Entries 5 7 Continue 6 7 Convert Loaded Package for Redistribution 23 5 24 4 Copy Everything About an Option to a New Option 9 4 9 11 Copy One Users Menus and Keys to others 9 4 CPU Service User Device Stats 3 21 3 28 Create a Set of Options to Mark Out Of Ord
188. CHECK1 XTSUMBLD routine into the Calculate and Show Checksum Values option XTSUMBLD CHECK July 1995 Kernel Systems Management Guide 27 3 Revised June 2008 Version 8 0 Verification Tools The CHECKI XTSUMBLD API is more accurate than the old integrity checking utility CHECK XTSUMBLD CHECKI XTSUMBLD determines the current checksums for selected routine s the functionality of which 1s shown as follows e Any comment line with a single semi colon is presumed to be followed by comments and only the line tag will be included e Line 2 will be excluded from the count e The total value of the routine is determined excluding exceptions noted above by multiplying the ASCII value of each character by its position on the line and position of the line in the routine being checked The corresponding direct mode utility can be used in programmer mode gt D CHCKSUM XTSUMBLD i The integrity checking utility CHCKSUM XTSUMBLD supports the Compare local national checksums report option XU CHECKSUM REPORT as released with Kernel Patch XU 8 0 369 i The modification CHECK1 XTSUMBLD to the integrity checking utility CHCKSUM XTSUMBLD fixes the problem in which the old CheckSum output is the same CheckSum value even if some lines were swapped within a routine Error Processing Kernel Error Trapping and Reporting Technical personnel who have entered programmer mode with D XUP might choose to record an error encountered with D
189. CTIVE USER S PRIORITY The INTERACTIVE USER S PRIORITY parameter in the KERNEL SYSTEM PARAMETERS file 8989 3 should usually be left NULL A setting here affects the job priority of interactive users and could result in poor response time ASK DEVICE TYPE AT SIGN ON The ASK DEVICE TYPE AT SIGN ON parameter controls whether the user s current device at signon is queried for its display attributes DA Thus the correct terminal type can be identified without prompting the user It is recommended that ASK DEVICE TYPE AT SIGN ON be set to ASK so that Signon Security performs the DA query and allows the Device Handler to set up the correct terminal type attributes This has become more important with the advent of screen control VA FileMan s Screen Editor and Screen Manager for example will not function properly if the terminal type recorded by Kernel fails to match the actual terminal type being used As with other parameters the site default ASK DEVICE TYPE AT SIGN ON field in the KERNEL SYSTEM PARAMETERS file 8989 3 is overridden by a DON T ASK setting for the device like named field in the DEVICE file 3 5 which would similarly be overridden by a DON T ASK setting for the user like named field in the NEW PERSON file 200 A NULL value functions as ASK The user Override can be set by any user via the Edit User Characteristics option If the parameter is set to DON T ASK Signon Security does not perform the DA query and assumes t
190. Conversion After the conversion users may complain about not being able to add entries to files as they previously could This typically results from use of an option that navigates from one file to another To be able to add entries to the navigated to file the user needs LAYGO access to that file IRM can solve the problem by granting LAYGO access using the File Access Security menu options XUFILEACCESS Figure 5 3 If this form of security is implemented IRM will find that it provides a more accurate and precise knowledge of who has what level of access to which files When the conversion is run privileges are granted to existing users by making use of information stored in the VA FileMan record of file manipulation activity the DISV global The file access conversion grants each user READ access to files that the user had recently accessed as indicated in the DISV global IRM can grant file access privileges to new users by copying the profile of an existing user with similar duties e g a laboratory application coordinator or admissions clerk To be sure that appropriate levels of access have been allocated IRM staff should determine who has what level of access to which files Access to sensitive files e g the NEW PERSON file 200 should be reviewed and readjusted for individual users as appropriate All files on a system should be reviewed before and after running the File Access Security conversion Figure 5 9 shows ho
191. Current Routines option can be used whenever the developer would like a new snapshot of the routine The XTV ROUTINE CHANGES file 8991 holds each new snapshot as a new version This filing method does not however alter the actual version number of the routine itself Routine Compare Current with Previous Option The Routine Compare Current with Previous option XTVR COMPARE is used to compare one or more current routines to previous versions To use the routine compare utility copies of the selected routines must first be stored in the XTV ROUTINE CHANGES file 8991 stored in the XTV 8991 global This is achieved by use of the Update with Current Routines option XTVR UPDATE on the Verifier Tools Menu Routines can be specified one by one or as a group with the wildcard syntax e g XQ Any initialize routines are automatically excluded Differences between the current version and the indicated number of prior versions are noted The user is prompted for the number of previous versions from which to begin the listing An entire history or just a brief display of recent modifications can be obtained 27 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Verification Tools Miscellaneous Verification Tools Programmer Options Menu The Programmer Options menu XUPROG comprised of the following options Figure 27 2 Programmer Options menu options Toolkit verification tools SYSTEMS MANAGER ME
192. DCL Context 21 18 SCHEDULE File 20 6 22 27 Schedule List 22 9 Select another task Option 19 6 Sequences of Tasks 18 13 SPECIAL QUEUEING Field 22 22 Starting Up Pausing and Stopping Multiple Managers 21 11 Startup 21 11 States BALANCE 21 12 21 13 22 36 ERROR 22 36 Messages 22 36 PAUSE 21 7 22 37 RUN 22 37 WAIT 21 11 22 15 22 16 22 38 Status Codes 22 32 Stop Task Manager Option 22 16 Stopping 22 16 Tasks 19 4 Submanagers 20 1 20 3 SYNC flag file control Option 22 16 SYNC FLAGs 18 13 System Management Configuration 21 1 Operation 22 1 Overview 20 1 Task List 22 10 TASK PARAMETERS Field 22 21 Task Rejection Messages 22 35 Task Status Codes 22 32 Taskman Error Log 13 2 20 6 22 11 22 17 22 24 22 25 Menu 22 24 Node 22 27 TaskMan Management Menu 22 1 Taskman Management Utilities Menu 22 7 TaskMan s Reach 21 2 TASKS File 14 4 20 7 22 30 Terminology 20 7 Troubleshooting 22 9 22 12 22 27 22 36 User Interface 19 1 Background Jobs 19 1 Creating Tasks 19 1 Display Status of Tasks 19 4 Editing Tasks 19 5 Listing and Printing Tasks 19 5 Other Sources of Tasks 19 2 Queuing Output 19 1 Select another task Option 19 6 Selecting Tasks 19 3 Stopping Tasks 19 4 Summary 19 6 Tasks in the Task List 19 3 Working with Tasks 19 2 Working with Tasks 19 2 ZTMQ Security Key 20 8 TASKMAN ERROR File 22 11 Taskman Error Log 13 2 20 6 22 11 22 17 22 24 22 25 Add Erro
193. Display Option Help 6 2 One Question Mark to List Options 6 2 Three Question Marks to Display Option Descriptions 6 5 Two Question Marks to List Secondary and Common Options 6 3 Extended 12 2 Line Mode Editing 28 4 Online xxxv Question Marks xxxv 2 4 3 6 3 21 3 22 5 2 5 9 6 1 6 2 6 3 6 5 6 6 6 9 7 7 8 1 12 2 12 3 12 7 13 3 13 4 13 6 14 2 15 3 19 3 19 5 19 6 22 5 22 11 23 16 HELP FRAME Field 7 3 12 5 12 7 HELP FRAME File 9 2 12 4 12 6 Help Frames Creating 12 6 Deleting Help Frames 12 5 Disk Space Concerns 12 6 Display 12 1 Editing 12 6 Editors 12 5 Exported 12 6 Keywords 12 7 Layout Considerations 12 6 Linking Help to an Option or Menu 12 7 Menu System 12 2 Namespacing 12 6 XUSER COMPUTER ACCOUNT 3 10 Help Processor 12 1 Cross Reference Help Frames Option 12 5 Deleting Help Frames 12 5 Display Edit Help Frames Option 12 4 Editors 12 5 Fix Help Frame File Pointers Option 12 5 Index 16 Kernel Systems Management Guide Version 8 0 Help System Actions 12 2 Layout Considerations 12 6 Linking a Help Frame as Help for an Option or Menu 12 7 List Help Frames Option 12 4 Menu 12 4 Menu System 12 2 New Revised Help Frames Option 12 5 System Management 12 4 User Interface 12 1 HFS Device 15 6 HFS Devices 15 4 15 9 16 1 16 2 18 15 21 13 23 1 23 5 23 6 23 7 23 9 23 10 History Revisions to Documentation and Patches 111 Home Device 14 1 14 3 15 10
194. E Spooler Subtype DEVICE Spooler spool Document Name DEVICE Spooler Subtype Spool Document Name Retrieving Spooled Documents After a spool document has been created you can retrieve the output by using options on the Spooler Menu This menu is distributed as part of Kernel s Common menu a menu available to all users Specifically the Spooler Menu is in your User s Toolbox menu to quickly reach the Toolbox or any other option on the Common menu you can enter a quotation mark plus the menu text or synonym Figure 17 8 Spooler Menu options Select Primary Menu Option TBOX Select User s Toolbox Option Spooler Menu Select Spooler Menu Option Allow other users access to spool documents Browse a Spool Document Delete A Spool Document List Spool Documents Make spool document into a mail message Print A Spool Document The List Spool Documents option lists any documents that you have created Other users cannot read or print these documents unless you have authorized them to with the Allow other users access to spool documents option also on the Spooler menu To delete spool documents you can use the Delete A Spool Document option Since there is a limit on the amount of spool space that any one user can consume you may need to delete old spool documents to free up space for new ones If you attempt to create a new document when the space limits have been exceeded the spooler issues a message about the need to delet
195. E BLOCK TITLE OFFICE PHONE VOICE PAGER DIGITAL PAGER Applications can print some or all of these fields when printing an electronically signed document You should therefore ensure that the values entered in these fields are accurate July 1995 Kernel Systems Management Guide 4 Revised June 2008 Version 8 0 Electronic Signatures System Management Figure 4 2 User Edit menu options SYSTEMS MANAGER MENU EVE User Edit XUSER Electronic Signature Block Edit XUSESIG BLOCK Clear Electronic signature code lt locked KUMGR gt XUSESIG CLEAR Electronic signature codes are stored in the NEW PERSON 200 file The Electronic Signature Block Edit option XUSESIG BLOCK lets you edit the electronic signature code for any user on the system When you create an electronic signature code for a user the SIGNATURE BLOCK PRINTED NAME field is initially filled in by a cross reference on the NAME field 01 and will be overwritten 1f the NAME field 01 is changed Credentials e g M D can be added to customize the printed name As a security feature an input transform requires that the user s last name first comma piece of the NAME field 01 be included in the printed name This field cannot be edited through VA FileMan since it is WRITE protected with a caret The Clear Electronic signature code option XUSESIG CLEAR is another option available to IRM that allows the clearing deleting of an
196. EDITLPD MT Magtape Device Edit XUDEVEDITMT RES Resource Device Edit XUDEVEDITRES SPL Spool Device Edit XUDEVEDITSPL TRM TRM or VTRM Device Edit XUDEVEDITTRM VOLUME SET CPU Setting a value in a device s VOLUME SET CPU field is optional If the VOLUME SET CPU field is filled in the device is assumed to be accessible only from the specified CPU If the field is left blank the device is assumed to be accessible from any CPU NOTE In the Cach environment where cluster mounting is used and most devices are set up on all CPUs all such devices do not need a value for this field When the VOLUME SET CPU field is blank the Device Handler still maintains the CPU cross reference to support queuing and other activities The cross reference format involves use of periods as 15 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler System Management delimiters If the VOLUME SET CPU value were BBB the cross reference for the device with a I of 75 would be BBB 75 If the VOLUME SET CPU value were NULL then 75 would be the CPU cross reference TYPE There are twelve types of devices A device s type is set in the DEVICE file s 3 5 TYPE field The twelve types are Table 15 2 Device types in the TYPE Field in the DEVICE file 3 5 T Terminal devices e g most CRTs and printers should be associated with a corresponding device entry with a type of TRM O
197. ELETE 22 26 XUTM ERROR LOG CLEAN RANGE 22 25 XUTM ERROR PURGE TYPE 22 26 XUTM ERROR SCREEN ADD 13 3 XUTM ERROR SCREEN EDIT 13 3 XUTM ERROR SCREEN LIST 13 3 XUTM ERROR SCREEN REMOVE 13 4 XUTM ERROR SHOW 22 25 XUTM INQ 22 2 XUTM MGR 13 2 XUTM QCLEAN 21 8 22 17 22 24 22 30 XUTM REQ 20 8 22 5 22 33 XUTM RESTART 22 14 22 15 XUTM RUN 22 15 XUTM SCHEDULE 22 19 XUTM STOP 22 15 22 16 22 29 XUTM SYNC 22 16 XUTM TL CLEAN 22 6 XUTM UCI 21 8 XUTM USER 19 2 22 33 XUTM UTIL 13 2 22 7 XUTM VOLUME 21 5 XUTM WAIT 22 15 XUTM ZTMON 21 13 22 7 22 36 XUTMGER 22 1 XUTTEST 15 12 XUUSERDISP 2 11 XUUSERSTATUS 3 28 Index Your future tasks 22 3 ZTMQUEUABLE OPTIONS 3 25 7 1 17 9 22 17 22 18 Options in the Option File that are Out of Order Option 7 11 Options to be Delegated Option 9 8 Orientation For Kernel Systems Management Guide xxxiii Other Files TaskMan 20 7 Other Non TaskMan Mode 21 4 OTHER NON TASKMAN VOLUME SET Type 21 7 Other Sources of Tasks 19 2 OUT OF ORDER MESSAGE Field 2 7 10 7 11 7 14 11 1 11 3 11 8 Out of Service Set Clear Option 15 12 OUT OF SERVICE Field 21 7 Out Of Order Set Management Menu 7 10 OUT OF SERVICE DATE Field 3 2 Output Routines Option 26 8 Overflowing Spool Document Storage 17 6 Overview Multi Term Look Up MTLU 25 1 Routine Tools 26 1 Verification Tools 27 1 OVERWRITE 23 21 P P1 Print 1 occ
198. ERS file 14 7 entries for each satellite and adjust their TaskMan Job Limit to reflect each satellite s individual capacity Figure 21 5 VOLUME SET file 14 5 standardized VA Cach and GT M configuration VOLUME SET TYPE INHIBIT LOGONS LINK ACCESS OUT OF SERVICE REQUIRED VOLUME SET TASKMAN FILES UCI TASKMAN FILES VOLUME SET REPLACEMENT VOLUME SET DAYS TO KEEP OLD TASKS SIGNON PRODUCTION VOLUME SET You need one entry for ROU GENERAL PURPOSE VOLUME SET Blank Blank Blank Blank VAH Leave Leave Up to Yes or NO or NO or NO or NO this blank this blank you can leave blank Figure 21 6 UCI ASSOCIATION file 14 6 standardized VA Cach and GT M configuration FROM UCI FROM VOLUME SET TO VOLUME SET TO UCI NOTE Can leave this empty 1 entries ROU Blank Blank VAH Figure 21 7 TASKMAN SITE PARAMETERS file 14 7 standardized VA Cach and GT M configuration BOX VOLUME PAIR LOG TASKS DEFAULT TASK PRIORITY TASK PARTITION SIZE SUBMANAGER RETENTION TIME TASKMAN JOB LIMIT TASKMAN HANG BETWEEN NEW JOBS MODE OF TASKMAN ENVIRONMENT FOR DCL OUT OF SERVICE MIN SUBMANAGER CNT LOAD BALANCE ROUTINE Auto Delete Tasks Manager Startup Delay ROU FORFORUM1 Your answer should be the volume set name concatenated with the concatenated with the name of the Cache Configuration Blank or NO unless TaskMan is running in a DCL context in which case set to YES
199. ERTRP PRINT T 1 1 ERR 13 4 XUERTRP PRINT T 1 2 ERR 13 5 XUFILEACCESS 5 8 5 9 5 10 5 13 5 14 5 15 XUINDEX 26 2 XUKEYALL 8 3 XUKEYDEALL 8 3 XUKEYEDIT 8 4 XUOPTDISP 7 4 XUOPTPURGE 7 4 XUOPTUSER 3 26 XUOPTWHO 7 6 XUOUT 15 12 XUPR RTN EDIT 26 5 XUPR RTN PATCH 26 5 XUPRGL 28 1 XUPRINT 7 5 XUPROG 23 2 26 1 26 3 27 3 XUPROGMODE 7 16 XUPRROU 26 6 XUPR ROUTINE TOOLS 26 1 XUPR RTN TAPE CMP 26 7 XURESJOB 22 10 22 29 XUROUTINE IN 26 8 XUROUTINE OUT 26 8 XUSC LIST 3 27 XUSCZONK 3 28 XUSER 3 24 5 1 5 8 5 10 5 14 XUSER DIV CHG 2 8 XUSER KEY RE INDEX 8 5 XUSERAOLD 3 29 XUSERBLK 3 9 XUSER CLEAR ALL 3 8 XUSERDEACT 3 24 3 25 XUSEREDIT 3 17 XUSEREDITSELF 2 9 XUSERINQ 3 27 XUSERINT Option 3 1 XUSERLIST 3 27 XUSERNEW 3 9 XUSERPOST 3 7 XUSERPURGEATT 3 26 XUSERREACT 3 26 XUSERREL 3 27 XUSERTOOLS 2 7 XUSESIG 4 1 4 2 Index 30 Kernel Systems Management Guide July 1995 Revised June 2008 XUSESIG BLOCK 4 2 XUSESIG CLEAR 4 2 XUSITEMGER 3 26 23 23 XUSITEPARM 3 2 15 5 XU SPL MGR 17 7 XU SPL PURGE 17 8 XU SPL SITE 17 8 XU SPL USER 17 7 XUSTAT 3 21 3 28 XUTESTUSER 7 9 XUTIO 15 2 15 12 XUTLOOPBACK 15 12 XUTM BACKGROUND PRINT 22 18 XUTM BACKGROUND RECOMMENDED TaskMan 22 18 XUTM CHECK ENV 22 13 XUTM CLEAN 22 17 XUTM DEL 20 8 22 6 XUTM DQ 20 8 22 4 22 5 22 33 XUTM ERROR 13 2 22 24 XUTM ERROR D
200. ES INPUT TO WHAT FILE HELP FRAME lt Enter gt EDIT WHICH FIELD ALL TEXT lt Enter gt word processing Select HELP FRAME NAME ISC COMMPUTER ACCESS lt Enter gt Computer Access NAME ISC COMMPUTER ACCESS lt Enter gt HEADER Computer Access lt Enter gt TEAL suspension termination of access privileges I affirm with my signature that I have read understand and agree to fulfill the provisions of this User Access notice INDENT 5 WIDTH 75 NOWRAP Signature 20 2 29 RETURN THIS FORM TO IRMS NEW ACCTS xxx xxx Edit NO YES 3 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management Figure 3 10 Security Forms Sample user entries 2 of 4 WRAP INSERT lt TEXT gt lt PF1 gt H Help INDENT 5 WIDTH 70 NOWRAP CENTER USER ACCOUNT NOTIFICATION CENTER Department of Veterans Affairs CENTER SuperStar VAMC CENTER 123 Any Street CENTER Any Town ST 99999 Read through and edit entries specific XUVT 12 to your site information and save your 20 2 changes 29 29 1 5 OV Co WRAP A user account has been created in your name to enable you to access on line clinical and or administrative data required to perform your duties as an employee of the Department of Veterans Affairs Please rea
201. Enters Direct output to the current terminal home device The home device can also be selected by entering H h 0 or HOME To send output to a printer enter the name of the printer at the DEVICE prompt as shown below Figure 14 2 Choosing a printer device DEVICE DVNM5 Specify a device with the name DVNM5b To select the closest printer if one 1s defined unlikely you can simply enter P and press lt Enter gt as shown below Figure 14 3 Choosing the closest printer device DEVICE P Select the closest printer if one is defined July 1995 Kernel Systems Management Guide 14 1 Revised June 2008 Version 8 0 Device Handler User Interface You can enter a question mark to display help about the syntax of the response Figure 14 4 Device syntax help One question mark DEVICE Specify a device with optional parameters in the format Device Name Right Margin Page Length or Device Name Subtype Right Margin Page Length You can enter two question marks to display available printers and other devices connected to the current Volume Set or reachable from the current Volume Set You can also ask for a series of help frames under extended help Figure 14 5 Displaying devices help Two question marks DEVICE The following information is available All Printers Printers only on ROU Complete Device Listing Devices only on ROU Extended Help Select one A P C D or E
202. File Access Options Figure 5 3 File Access Security menu options SYSTEMS MANAGER MENU EVE User Management XUSER File Access Security XUFILEACCESS Grant Users Access to a Set of Files XUF LLEGRANT Copy One User s File Access to Others XUFILECOPY Single file add delete for a user XUFILESINGLEADD Inguiry to a User s File Access XUFILEINQUIRY List Access to Files by File number XUFILELIST Print Users Files XUFILEPRINT Delete Users Access to a Set of Files XUFILESETDELETE Remove All Access from a Single User XUFILEREMOVEALL Take away All access to a File XUFILEDELETE Assign Delete a File Range XUFTLERANGEASSIGN When using options on the File Access Security menu XUFILEACCESS you may have the following questions e What is the DUZ that appears next to the user s name e How is arange of file numbers specified e What are the queuing questions all about Understanding DUZ the User Number When listing the file accesses by user or by file the user s name is followed by a number in parentheses The heading indicates that this is the User which is the same as the DUZ DUZ is a local variable that identifies the user who has signed onto the system Once the user enters an Access and Verify code Kernel s Signon Security uses this variable to identify an entry in the NEW PERSON file 200 It must be unique so the user s name will not do Instead the internal entry num
203. Global Location 15 1 NAME Field 01 15 8 Naming Conventions 15 9 OPEN EXECUTE Field 14 7 15 8 18 16 18 17 PAGE LENGTH Field 15 8 RIGHT MARGIN Field 15 8 SELECTABLE AT SIGN ON Field 3 6 15 8 15 11 Terminating Users 3 24 TERMINATION DATE Field 3 10 3 22 3 24 3 25 3 26 11 4 Terminology KIDS 23 1 TaskMan 20 7 Test an option not in your menu Option 28 2 Testing User s Menus 7 9 XQSCHK Server Option 11 6 TEXT TERMINATOR Field 2 10 3 23 TIED ROUTINE Field 3 1 Time Option 6 7 TIME PERIOD Field 01 7 11 TIMED READ Field 3 7 3 21 Kernel Systems Management Guide Index 41 Version 8 0 Index TIMES DAYS PROHIBITED Field 3 91 Multiple 11 2 11 3 TITLE Field 3 18 TITLE File 3 1 3 18 TMP Global 7 12 7 13 TO UCI Field 21 9 TO VOLUME SET Field 21 9 Toggle Options Protocols On and Off Option 7 10 Tokenizing Routine 25 2 Toolbox Display User Characteristics Option 2 11 Electronic Signature code Option 4 1 Menu 2 3 2 6 2 7 2 8 2 9 2 11 4 1 4 2 6 7 6 8 17 3 19 2 Toolkit Queuable Options menu Errors Logged in Alpha Beta Test QUEUED Option 23 23 Transfer Entries Option 5 6 5 7 Transfer File Entries Option 5 7 5 7 Transfer Lines from Another Document Option 5 2 5 5 Transparent Print Mode 18 15 Transport a Distribution Option 23 5 24 5 TRANSPORT BUILD NUMBER Field 63 23 12 24 12 26 7 Transport Global 23 1 Backup 23 15 Compare 23 3 23 7 23 13 Componen
204. Guide July 1995 Version 8 0 Revised June 2008 Contents Purse Build or Install Files Opt On nsei nnc n E E 24 7 Rollup Patches mioa Buld OPON terenie E E TO A 24 9 Update Routine PICe ODUM nenacia A a atieseaaheueaaesiaes 24 10 VP ee U0 ODIO E A 24 10 Verily Package Inte stily ODUON sesi weet 24 11 2 Wiis O00 r eopreremereeneenereee rereroenne errr ier ure eneren A arene ee ene eer A nr een Tye VI 1 25 Wilt Teri Wook 2U 9 VETILW s5 5 4 sres vaicasionctaoseecncamesdicacacus tas borsaceensd auras Micacusnetiesoosuacdsae 25 1 CON CEVA Woes cer e dle il aedsd teal a eels tel ae daca s mivenl naval ia tateothaluncckahddenlamsuededs 25 1 Introduction to Multi Term Look Up MTLU i ccccccccccccceseseeeeeeeeeeeeaeeeseeeeeseeeeaaeenees 25 1 PRUMCHON al CSCi Ul OM mosean co dace bass gaereoeware a e E 25 1 Usare CONSIGSLATIONS eenn a a a a seams eee Gowstnenians titer ecasams 25 2 Useren AC Soares eG E A A 25 3 Multi Term Look Up Menu Options ssssssesseseeecceceeecceeceeaaaeeeseeseeeeeceeeeeeeeeeeaaaagas 25 3 Using the Multi Term Lookup MTLU Option ccccccssssseseeseeeeeeeceeeeeseeeeneaas 25 5 Usine the Prine Utility Oplossen a a eau 25 6 Usine the Utilities tor MTL OPON ijaviccts oe vvsicest rss cose n a a 25 8 Sy SLOTS Mando emen sashes asta stnaraacd sus seuaanonevonus ae casasieae tesountousy aco ahoesnseage emotes ieee ons 25 20 Implementation of Multi Term Look Up MTLU cc cccssssseesesseeeeeeee
205. INSTALL STARTED USPSA HZ XPD POSTINSTALL COMPLETED 07 52 21 INSTALL QUESTION PROMPT XPZ1 Want to DISABLE Scheduled Options Options and Protocols MESSAGES Install Started for Z2XG DEMO 1 0 Feb 07 2Z2004 07 52 14 Installing Routines Feb 07 2004 07 52 15 Running Pre Install Routine ZXGPRE Installing Data Dictionaries Feb 07 2004 07 52 16 Installing PACKAGE COMPONENTS Installing PRINT TEMPLATE Installing OPTION Feb 07 2004 072 52 21 Running Post Install Routine ZXGPOS Updating Routine file July 1995 Kernel Systems Management Guide Revised June 2008 Version 8 0 ANSWER NO 24 3 KIDS System Management Utilities Upodat rng KIDS ELISS ox ZXG DEMO 1 0 Installed Feb 07 2004 07 52 23 Convert Loaded Package for Redistribution Option Use the Convert Loaded Package for Redistribution option XPD CONVERT PACKAGE to add software to an existing distribution A KIDS distribution can transport one or more software applications What if you want to add additional software to an existing distribution For example suppose you have a distribution for a software application Further suppose that patches are transported as individual KIDS software and you want to add all existing patches to the software s distribution The Convert Loaded Package for Redistribution option XPD CONVERT PACKAGE lets you do this In Figure 24 4 and Figure 24 5 distributions for a software application i e Z
206. ION Field Multiple 3 6 3 21 Division of Labor TaskMan 20 1 DLAYGO Variable 5 3 5 5 Documentation History 111 Symbols xxxiv DOMAIN File 4 2 5 11 5 13 Double Quote Jump 6 8 Double Quote Shortcuts 6 8 DQ6 ZTLOAD API 22 33 DSM for OpenVMS Systems ENVIRONMENT FOR DCL Field 21 5 DTIME Variable 3 7 3 21 DUZ Description 5 9 Variable 5 9 DUZ AG Variable 3 6 DUZ AUTO Variable 3 6 DUZ 0 Variable 3 19 3 20 5 3 5 4 5 7 5 8 5 10 9 5 15 8 DUZ 2 Variable 3 6 E Edit a Build Option 24 9 Edit a User s Options Option 9 2 Example 9 3 Edit an Existing User ACCESS CODE 3 19 ALLOWED TO USE SPOOLER 3 22 ALWAYS SHOW SECONDARIES 3 22 ASK DEVICE TYPE AT SIGN ON 3 22 AUTO MENU 3 21 CAN MAKE INTO A MAIL MESSAGE 3 22 DISUSER 3 22 DIVISION Multiple 3 21 FILE MANAGER ACCESS CODE 3 3 19 FILE RANGE 3 22 INITIAL Field 41 3 17 MAIL CODE 3 18 MULTIPLE SIGN ON 3 21 NAME Field 01 3 17 NICK NAME 3 18 PAC Programmer Access Code 3 22 PREFERRED EDITOR 3 20 PRIMARY MENU OPTION 3 18 PROHIBITED TIMES FOR SIGN ON 3 22 SECONDARY MENU OPTIONS Field Multiple 3 19 SER VICE SECTION 3 21 SSN Field 9 NEW PERSON File 200 3 18 TERMINATION DATE 3 22 TIMED READ 3 21 Title 3 18 TY PE AHEAD 3 22 VERIFY CODE 3 19 Edit an Existing User Option 3 17 Edit Devices by Specific Types Option 18 10 Edit Error Screens Option 13 3 Edit File Option 5 11 EDIT HISTORY Multiple
207. ION PROCEDURE File 80 1 25 1 Identifying Locked Options 8 2 Idle Node 22 28 If the Option Invokes Non VistA Applications 7 4 If the Option Should Be Regularly Scheduled 7 4 Implementation Multi Term Look Up MTLU 25 20 INDEPENDENTLY INVOCABLE Field 7 8 Information Stored in the INSTALL File 9 7 KIDS 23 17 INHIBIT LOGONS Field 3 8 21 7 INIT Routines 23 1 23 5 INITIAL Field 1 NEW PERSON File 200 2 9 3 9 3 17 3 18 4 1 Input Routines Option 26 8 Inquire Option 7 6 Inquire to File Entries Option 5 6 5 8 Inspecting the Tasks in the Monitor s Lists 22 11 INSTALL ANSWERS Field Multiple 23 17 INSTALL File 9 7 23 4 23 5 23 7 23 9 23 17 23 19 23 20 23 21 24 3 24 7 24 9 Purging 24 7 Install File Print Option 23 17 23 19 24 3 Install Package s Option 23 7 23 16 23 17 INSTALL CHECK MESSAGE PackMan Option 23 7 23 9 Installation Menu 23 3 Installation Menu KIDS 23 8 23 16 July 1995 Revised June 2008 Index Installations Components 23 19 Finish 23 19 Global Distributions KIDS 23 21 KIDS 23 2 23 3 Menu KIDS 23 8 Progress KIDS 23 19 Restarting 23 20 Running KIDS 23 16 Scheduling KIDS 23 16 Sequence KIDS 23 7 Standard Distributions KIDS 23 7 Instances How Can the Number of Instances of a Server Option Be Controlled 11 2 INSTITUTION File 4 3 6 Intensity 14 6 Interactive Print of Error Messages Option
208. In turn ZTLOAD uses that information to create an entry in the TASKS file 14 4 A ZTLOAD then sets up a simple cross reference to the new task in the SCHEDULE file thereby finishing the queuing process After queuing the task ZTLOAD quits returning control back to the queuer and leaving the next step in the process to the Manager routines Option Scheduling through the OPTION SCHEDULING File 419 2 Another commonly used queuer is the OPTION SCHEDULING file 19 2 Menu Manager and TaskMan work together to allow certain options to be run as TaskMan tasks These special options can be scheduled to run just once or they can be set up to run over and over based on a rescheduling cycle Such cycles can even include running the task whenever the computer system boots up Manager For tasks to run at least one CPU in a configuration needs to run a Manager Only one Manager process needs to run per CPU the site determines how many CPUs should be configured to run a Manager The Manager s job is to route the tasks created by queuers It normally runs at all times in the manager UCIs It repeats the same loop of code all day long every 2 seconds it looks for overdue tasks every 15 seconds it checks the environment and performs some cleanup The environment check allows the system manager to control the Manager even at its busiest All of the commands to which the Manager responds described later take effect here between every task pro
209. K PARAMETERS YES SLAVED FROM DEVICE TRM LOCATION OF TERMINAL SLAVE DEVICE FOR LA5O MARGIN WIDTH 132 FORM FEED PAGE LENGTH 64 SUBTYPE P LA50O TYPE TERMINAL Figure 18 18 Slaved Printer example DEC LASO TERMINAL TYPE file 3 2 entry NAME P LA5O RIGHT MARGIN 132 FORM FEED PAGE LENGTH 64 OPEN EXECUTE W 27 4w CLOSE EXECUTES W 27T Owe DESCRIPTION LA50 132 COL 16 5 CPI Figure 18 19 Slaved Printer example Epson LQ870 DEVICE file 3 5 entry NAME SLAVELQ870 PEREN ASK DEVICE YES ASK PARAMETERS YES SLAVED FROM DEVICE TRM LOCATION OF TERMINAL SLAVE DEVICE FOR LQ870 MARGIN WIDTH 132 FORM FEED PAGE LENGTH 64 SUBTYPE PLO 70 TYPE TERMINAL Figure 18 20 Slaved Printer example Epson LQ870 TERMINAL TYPE file 3 2 entry NAME P LQ870 RIGHT MARGIN 132 FORM FEED PAGE LENGTH 64 OPEN EXECUTE W 15 CLOSE EXECUTE W 18 DESCRIPTION EPSON L0870 PRINTER CONDENSED Use of Slaved Printer Processing Steps The Device Handler manages output to slaved printers using the following steps 1 Execute the OPEN PRINTER PORT code of the home device s terminal type 2 Execute the OPEN EXECUTE code of the slaved printer s terminal type July 1995 Kernel Systems Management Guide 18 17 Revised June 2008 Version 8 0 Special Device Issues 3 When the application closes the device execute the CLOSE EXECUTE code of the slaved printer s terminal type 4 Execute the CLOSE PRINTE
210. LOCAL LOOKUP file 8984 4 e Routine Tools Routine Tools provide a set of generic tools to aid the VistA development community and IRM in analysis writing and testing of code These tools are used by VistA developers to support distinct tasks Routine Tools do the following Promote standard program interfaces Check adherence to programming standards and correct syntax with the XINDEX utility Provide standard error trapping storing and reporting Customize and tunes site parameters for local requirements Provide M function libraries Provide a portable routine and global editor Provide a Kermit file transfer utility Provide a Multi Term Look Up MTLU utility for enhanced VA FileMan lookups Provide software project management utilities e Verification Tools Verification Tools are a set of generic tools to aid the VistA development community and IRM in reviewing M code These tools are used by VistA developers to support distinct tasks Verification Tools provide the following Tools used for comparison of routines and data dictionaries A tool used to record routine text indicated in the file used to maintain changes in routines July 1995 Kernel Systems Management Guide VI 1 Revised June 2008 Version 8 0 Toolkit Where applicable each major area of Kernel Toolkit is described first in terms of its user interface then in terms of system management implications showing the menu
211. M KUPROG n XOO T 29y TAI XUTIO Device Hand er Me eee 134 on 20 n WOO 2p T XUSER User Edit M 1 53 4 n XOOT 297 TA KUCORE Core Applications L AMAA AAAA TOO es oy TAM ZTMMGR Task Manager M n 50 1 1XOOT 29 TAM XUSITEMGR Operations Managements M nnnnnnAnys ns s WRONG 297 TAT XUSPY System Security AMANA EAA ynn TRO 297 TAM XU SPL MGR Spool Management M 419 20 XUTL XQ0 29 VA FILEMAN 19 1 7 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Figure 7 24 Display Nodes for a secondary menu XUTL SAUTI SKUTE XUTL X00 VM UGE 20 15054927 30758 X00 U66 0 1 ZZTSTSM Secondary Menu lt 2 n X00 U66 SECONDARY MENU 580 1 KOO U66 580 ZZTSTSM Secondary Menus Mase ae Lao aL Jump Nodes Jump nodes are stored in XUTL XQO P _internal number where there is one P_ entry in AXUTL XQO for each primary menu that exists The jump nodes for each primary menu store the pathways to all options that can be jumped to The jump nodes are created in the XQ8 series of programs They are very similar to display nodes except that 1 They have a P concatenated on the front of the primary option s number in the second subscript
212. ME OF VERIFY CODE 90 DEFAULT INSTITUTION ISC SAN FRANCISCO AUTO GENERATE ACCESS CODES NO LOG RESOURCE USAGE YES Exit Save Next Page Refresh Enter a command or followed by a caption to jump to a specific field COMMAND Press lt PF1 gt H for help Insert Signon Attempts and Device Lock out Times The DEFAULT OF ATTEMPTS field in the KERNEL SYSTEM PARAMETERS file 8989 3 holds the default limit of the number of times a user can try to enter a valid Access and Verify code pair When the limit is reached Signon Security is unresponsive for the duration specified by the DEFAULT LOCK OUT TIME field The values for number of attempts and lock out time are overridden by any values for the current device specified by comparable fields in the DEVICE file 3 5 Device values are ignored however if the BYPASS DEVICE LOCK OUT site parameter in the KERNEL SYSTEM PARAMETERS file 8989 3 is set to YES In particular the fields that are bypassed are OUT OF SERVICE DATE SECURITY and PROHIBITED TIMES FOR SIGN ON Device values are put back into effect for the current device if the DEVICE file s PERFORM DEVICE CHECKING field is set to YES 3 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management MAX SIGNON ALLOWED One Kernel site parameter used in the initial signon screening is MAX SIGNON ALLOWED It is a field within the VOLUME SET field Multiple in the KERNEL SYSTEM PARAMETER
213. Man Edit File option REF For more information on the Edit File option please refer to the Utility Functions chapter in the VA FileMan User Manual Figure 25 22 VA FileMan Edit File option Sample user entries VAH MTL gt D QDI VA FileMan 20 0 Select OPTION UT lt Enter gt ILITY FUNCTIONS Select UTILITY OPTION ED lt Enter gt IT FILE MODIFY WHAT FILE ICD DIAGNOSIS lt Enter gt NAME ICD DIAGNOSIS lt Enter gt DESCRIPTION lt Enter gt 1 gt Contains all valid ICD diagnosis codes EDIT Option lt Enter gt Select APPLICATION GROUP lt Enter gt PROGRAMMER lt Enter gt VERSION 9 lt Enter gt DATA DICTIONARY ACCESS lt Enter gt READ ACCESS lt Enter gt WRITE ACCESS lt Enter gt DELETE ACCESS lt Enter gt LAYGO ACCESS lt Enter gt AUDIT ACCESS lt Enter gt DD AUDIT NO lt Enter gt ASK OK WHEN LOOKING UP AN ENTRY YES lt Enter gt YES POST SELECTION ACTION lt Enter gt LOOK UP PROGRAM XTLKDICL CROSS REFERENCE ROUTINE lt Enter gt Select UTILITY OPTION lt Enter gt NOTE The developer might elect to use MTLU only in selected instances This is accomplished by not adding the special lookup routine to the file s DD After the file has been added to the LOCAL LOOKUP file 8984 4 you can make a developer call to LKUP XTLKMGR REF Multi Term Look Up MTLU Application Programming Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Develo
214. Management Utilities i NOTE As of Kernel Patch XU 8 0 393 KIDS was modified to send a message to a server on FORUM when a KIDS build is sent to a Host File Server HFS device This message contains the checksums for the routines in the patch The server on FORUM matches the message with a patch if the sending domain is authorized on FORUM There is no longer a need for developers to manually include routine checksums either CHECK XTSUMBLD and or CHECK1 XTSUMBLD in the patch description The patch module will include the before and after CHECK1 XTSUMBLD values in the Routine Information section at the end of the patch document With changes in the National Patch Module NPM on FORUM when the patch is released the checksums for the routines are moved to the ROUTINE file 9 8 on FORUM The checksum before values will come from the FORUM ROUTINE file 9 8 and are considered the GOLD standard for released checksums The local site s Compare local national checksums report option XU CHECKSUM REPORT uses the FORUM ROUTINE file 9 8 as its source to create reports showing any routines that do not match This patch also modified the KIDS BUILD file 9 6 by adding the TRANSPORT BUILD NUMBER field 63 used to store a build number that is incremented each time a build is made This build number is added to the second line of each routine in the 7th 3 piece This makes it easy to tell if a site is running the current release during te
215. Manager menu EVE is the master menu for IRM The Common menu XUCOMMAND is linked through the display function of the menu system rather than the OPTION file 19 Kernel also exports a menu that is a miscellaneous collection of options that should not normally be invoked by the interactive user it is the PARENT OF QUEUABLE OPTIONS menu ZTMQUEUABLE OPTIONS Most of the options on this menu should be scheduled to run as TaskMan jobs Figure 7 1 Kernel menu tree roots SYSTEMS MANAGER MENU EVE SYSTEM COMMAND OPTIONS XUCOMMAND PARENT OF QUEUABLE OPTIONS ZITMQUEUABLE OPTIONS July 1995 Kernel Systems Management Guide 7 1 Revised June 2008 Version 8 0 Menu Manager System Management Creating Menus and Options Figure 7 2 Edit options option SYSTEMS MANAGER MENU EVE Menu Management XUMAINT Edit options XUEDITOPT One task IRM performs frequently is defining local primary menus that are appropriate for their users This task of menu creation is accomplished by grouping exported menus from various software application together on a new master menu You can use Edit options on the Menu Management menu to define a new menu if READ WRITE and LAYGO access to the OPTION file 19 has been granted either through the FILE MANAGER ACCESS CODE field 3 or through the File Access Security system if that is enabled Only a few fields need to be defined as shown below The new men
216. Menu Delegation 9 12 Kernel Systems Management Guide Version 8 0 July 1995 Revised June 2008 10 Alerts User Interface When you receive an alert something on the computer system is requesting your immediate attention A software application might issue an alert to one or more users when certain conditions are met e g depleted stock levels or abnormal lab test results The first time you reach a menu prompt after receiving a particular alert the alert s message is displayed to you by the menu system The alert message is displayed along with a standard notice to select the View Alerts VA option on the Common menu to process the alert see Figure 10 1 When you receive an alert you should find out what the alert is asking of you and attend to it This is called processing the alert Until you process all unprocessed alerts you receive you ll be reminded that you have pending alerts each time you re at a menu prompt You will not however see the alert message you only see that the first time you receive an alert and reach the menu prompt Figure 10 1 Alert Sample user message Dr You need to enter a progress note on KRNPATIENT ONE Enter VA VIEW ALERTS to review alerts Select Systems Manager Menu Option Processing Alerts To process alerts choose the View Alerts VA option from the Common menu The View Alerts VA option presents a list of all pending alerts numbered consecutively with the most re
217. Menu Trees 7 13 Restricting Option Usage 7 11 Rubber band Jump 6 6 Summary 6 9 System Management 7 1 Out Of Order Set Management Menu 7 10 Templates LOGIN Menu 6 9 Up arrow Jump 6 5 User Interface 6 1 Variables Troubleshooting 7 20 MENU TEMPLATE Field Multiple 6 9 Menu Templates Option 6 8 MENU TEXT Field 1 11 3 Menus ACTION 28 5 Alert Management 10 4 10 6 Alpha Beta Test Option Usage Menu 7 4 23 23 Altering Exported Menus 7 8 Application Utilities 25 3 Audit Features 7 4 Common 2 3 3 19 6 3 6 4 6 5 6 6 6 7 6 8 7 1 7 7 7 8 8 1 8 5 10 1 17 3 17 7 19 2 Redefining 7 7 Creating 7 2 Data Dictionary Utilities xxxv 5 6 Delegate s Menu Management 9 2 9 4 9 5 9 7 9 9 Device Management 15 2 15 12 DI DDU 5 6 Diagramming 7 5 Display Menus and Options 7 5 Displaying 7 5 DIUTILITY 5 6 Edit Line Editor 5 2 Edit option 3 20 Edit TaskMan Parameters 21 2 21 13 Edits and Distribution 23 2 Error Processing 13 4 EVE 7 1 7 17 7 18 9 10 13 2 23 2 Exported 7 2 7 8 File Access Security 5 8 5 9 5 10 5 13 5 14 5 15 Help Processor 12 4 Installation KIDS 23 3 23 8 23 16 July 1995 Kernel Systems Management Guide Index 21 Revised June 2008 Version 8 0 Index 22 Index Kernel 7 1 Kernel Installation amp Distribution System 23 2 Key Management 8 3 8 4 9 8 9 9 Managing 7 7 Menu Management 9 7 Menu Templates Option 6 8 Multi Term Lookup
218. NU EVE Programmer Options XUPROG gt Locked with XUPROG KIDS Kernel Installation amp Distribution System XPD MAIN gt Locked with XUPROG PG Programmer mode XUPROGMODE gt Locked with XUPROGMODE Calculate and Show Checksum Values XTSUMBLD CHECK Delete Unreferenced Options XO UNREF D OPTIONS Error Processing XUERRS General Parameter Tools XPAR MENU TOOLS Global Block Count XU BLOCK COUNT List Global XUPRGL gt Locked with XUPROGMODE Routine Tools XUPR ROUTINE TOOLS Test an option not in your menu XT OPTION TEST gt Locked with XUMGR Tools found on the Programmer Options menu that can be of use for verification purposes include e Calculate and Show Checksum Values XTSUMBLD CHECK e Error Processing XUERRS These options are described below Calculate and Show Checksum Values Option The Calculate and Show Checksum Values option XTSUMBLD CHECK gives developers the ability to check the value of a routine at any given time It does not regenerate NTEG routines and can safely be used anytime This option calls the CHCKSUM XTSUMBLD API to calculate and show the checksum value for one or more routines in the current account This value is referenced in the Patch Module description for routine patches i Kernel Toolkit Patch XT 7 3 94 deployed the CHECKI XTSUMBLD API and the new logic CheckSum 4ZOSFC RSUM1 Kernel Toolkit Patch XT 7 3 100 included the
219. Narrative contained no usable words The following word s was not used in this search word s Search was unsuccessful The selected code or description is displayed The system searches in the following order shortcut synonym then keyword If more than one entry is found they are displayed and you are prompted to select one If only one entry is found the following appears IEE XIF lt Enter gt to accept default Return to the menu July 1995 Kernel Systems Management Guide 25 5 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The following is an example of what might appear on your screen when using the Multi Term Lookup MTLU option Figure 25 4 Multi Term Lookup MTLU option Sample user entries Lookup on which file ICD DIAGNOSIS NARRATIVE DIABETES MELLITUS DIABETES DIABETIC MELLITUS The following 3 matches were found Us OU 250 00 DIABETES UNCOMPL ADULT NIDDM 2 200 40 250 40 DIAB RENAL MANIF ADULT NIDDM be ea 7150 INFANT DIABET MOTHER SYN Select 1 3 2 Using the Print Utility Option The Print Utility option XTLKPRTUTL is used to print a list of shortcuts keywords or synonyms from a specified reference file in the LOCAL LOOKUP file 8984 4 Both the shortcut and keyword lists can be sorted alphabetically by name or numerically by code The synonym list however only prints alphabetically Since these lists can be long and the generation time consuming it
220. ON file 19 has been modified since the menus were compiled in XUTL and the global is therefore locked until XQ8 can recompile the modified menus This error message can be generated by both user generated jumps and phantom jumps Figure 7 17 Menu jump error message 2 of 6 WARNING Illegal jump requested to option option s menu text Jump pathway locked at option flocked option s menu text This indicates that a locked option for which the user does not possess the security key has been encountered in the tree between the option where the jump was requested and the target option to which the jump was requested This error message can be generated by both user generated jumps and phantom jumps Figure 7 18 Menu jump error message 3 of 6 x WARNING Illegal jump was requested to option option menu text Jump path out of order from option s menu text with message out of order message This means that an option on the tree between the option where the phantom jump was requested and the target option has been marked as out of order OUT OF ORDER MESSAGE Field 2 of the OPTION file 19 This error message can be generated by both user generated jumps and phantom jumps 7 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Figure 7 19 Menu jump error message 4 of 6 WARNING Illegal jump was requested to option option menu t
221. OUT Kernel provides several options on the Device Management menu XUTIO to aid with troubleshooting device problems which are described in the topics that follow Loopback Test of Device Port Option Use the Loopback Test of Device Port option XUTLOOPBACK to test an RS 232 serial data line when using a loopback connection on the line First disconnect the data line from the device it is attached to Gf any Then tie pins 2 and 3 of the RS 232 serial data line together This is a loopback connection data sent down pin 2 transmit will loop back up pin 3 receive The Loopback Test of Device Port option sends the letters of the alphabet down the data line one at a time and attempts to READ them back If both lines are intact you should see ABCDEFGHIJKLMNOPOQRSTUVWX YZ print on the terminal from which you are testing the data line Send Test Pattern to Terminal Option Use the Send Test Pattern to Terminal option XUTTEST to send a simple test pattern to a device This is an easy way to verify whether a device is connected to the system It lets you choose how many lines of the test pattern to send and then sends that number of lines to the device You can confirm on the device end exactly how many lines of the test pattern you receive which can be useful when troubleshooting printer handshaking problems Out of Service Set Clear Option You can use the Out of Service Set Clear option XUOUT to set a device out of order I
222. Options 25 8 XTLKMODSH Option 25 2 25 13 XTLKMODSY 25 2 XTLKMODSY Option 25 17 XTLKMODUTL Option 25 2 25 8 25 12 XTLKPRTUTL Option 25 1 25 6 XTLKTOKN Routine 25 2 XTLKUSER2 Menu 25 3 XTLKUTILITIES 25 8 XTLKZMGER Security Key 25 1 25 8 25 9 XTMENU Menu 25 3 XTMP Global 7 10 7 12 7 13 23 7 23 9 23 20 XT OPTION TEST Option 28 2 XTRCMP Routine 26 7 XTRDEL Option 26 8 XTRGRPE Option 26 5 XT ROUTINE COMPARE Option 26 7 XTSPING Utility 11 6 Index 46 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 XTSUMBLD CHECK Option Programmer Options Menu 27 3 XTV MENU Menu 27 1 27 2 XTV ROUTINE CHANGES File 8991 27 2 XT VARIABLE CHANGER Option 26 5 XTVCHG Routine 26 5 XT VERSION NUMBER Option 26 6 XTVNUM Routine 26 6 XTVR COMPARE Option 27 2 XTVR UPDATE Option 27 2 XU BLOCK COUNT Option 28 1 XU CHECKSUM LOAD Option 26 8 XU CHECKSUM REPORT Option 23 12 24 11 24 12 26 6 26 7 27 4 XU DA EDIT Option 15 11 XU FINDUSER Option 3 27 XU OPTION QUEUE Option 22 24 XU SWITCH UCI Option 2 12 XU USER SIGN ON Extended Action 3 7 XU USER SIGN ON Option 3 7 XUAUDIT MENU 7 4 XUAUDIT Option 7 4 XUAUTHOR Security Key 12 5 12 6 XUAUTODEACTIVATE Option 3 25 XUCOMMAND Menu 7 1 7 7 7 8 XUDEVEDIT Option 18 10 XUDEVEDITCHAN Option 18 11 XUDEVEDITHES Option 15 6 16 2 XUDEVEDITRES Option 18 14 XUDEVEDITSPL Option 17 9 XUDEVEDITTRM Option 15
223. Options to be Delegated option branches you to the Key Management program and lets you allocate if you so wish the appropriate keys to the delegates you are creating However to assign security keys to users the delegate must be delegated the key To do that you need to use the Key Management menu option Delegate keys option XQKEYDEL This option allows you to delegate security keys to delegates by populating the DELEGATED KEYS field Multiple in their NEW PERSON file 200 entry Security keys entered in a delegate s DELEGATED KEYS Multiple allow them to allocate the entered keys to other users but not themselves 9 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Secure Menu Delegation When a delegate assigns options to a user they can assign the matching security keys as part of that process However as an enhancement to a delegate s ability to work with keys IRM can assign the delegate the following options from the Key Management menu e Allocation of Security Keys e De allocation of Security Keys e Show the Security Keys of a Particular User As long as the delegate does not hold the XUMGER security key which allows any key to be allocated the Key Management menu options only allow delegates to allocate and de allocate security keys they ve been delegated Kernel also follows key delegation levels with the Allocation of Security Keys and De allocation of Security Keys options NOTE Key m
224. PORT BUILD NUMBER field 63 used to store a build number that is incremented each time a build is made This build number is added to the second line of each routine in the 7th 3 piece This makes it easy to tell if a site is running the current release during testing and afterword The leading B found in the checksum tells the code what checksum API to use Compare Routines on Tape to Disk Option The Compare Routines on Tape to Disk option XUPR RTN TAPE CMP compares routines and displays the differences This option reads a standard Cach RO Host File Server HFS file and compares the routines on the HFS file with a routine with the same name 1n the current account The corresponding direct mode utility can be used in programmer mode as follows gt D TAPE XTRCMP NOTE While it is still called a TAPE compare it is actually comparing a routine in an Host File Server HFS file to an installed routine Compare Two Routines Option The Compare Two Routines option XT ROUTINE COMPARE is used to compare two routines with different names that are located in the same account and display print the differences using MailMan s PackMan compare utilities The corresponding direct mode utility can be used in programmer mode as follows gt D XTRCMP July 1995 Kernel Systems Management Guide 26 7 Revised June 2008 Version 8 0 Routine Tools Deleting Routines Delete Routines Option The Delete Routines option XTRDEL ca
225. PTIONS field in the NEW PERSON file 200 entry for each user Figure 7 23 Display Nodes for EVE example KUT X00 29 0 2 55046 38923 RUT XOO 29707 XUCORE Core Applications asa NOT AVAILABLE XUTIO Device Handler ca OOnN RM DLUSER VA FileMan n XMMGR Manage Mailman XUMAINT Menu Management p POOR XUPROG Programmer Options xXUPROG XUTL XQ0 29 0 2 XUSITEMGR Operations Management XKU SPL MGR Spool Management XKUSPY System Security OOPS S LIMMGR Task Manager 2 nR XUSER User BO gyr Aee XOO 29 CORE APPLICATIONS 401 XOO 29 DEVICE HANDLER 32 1 WXOO 29 VEM 1970 XQO 29 MANAGE MAILMAN 30 1 XQ0 29 MENU MANAGEMENT 9 1 XQ0O 29 OPERATIONS MANAGEMENT 174 1 XQO0O 29 PROGRAMMER OPTIONS 31 1 XOO 29 SPOOL MANAGEMENT 415 1 XOO 29 SYSTEM SECURITY 226 1 XOO 29 TASK MANAGER 83 1 X00 29 USER EDIT 391 op XUT XUTL XUTL XUTL XUTL XUTL XUTL XUTL XUTL XUTL XUTL XUIL gt KUTI XUTL XUTL XUTL XUTL KUT XUTL XUTL XUTL XUTL XQ0 29 9 XUMAINT Menu Management M 105 4n n n XOOT 29 TAM FM DIUSER VA FileMan M 4n 4n 1 XOOT 2 97 TAM XMMGR Manage Mailman M 299 54 4141 NOV yee XUPROG Programmer Options
226. PackMan Message 1 Using the Load a Distribution option the installer chooses the HFS file from which to load distributions If loading from a PackMan message choose the message and invoke the INSTALL CHECK MESSAGE PackMan option 2 For each transport global KIDS makes an entry in the INSTALL file 9 7 for the transport global 3 KIDS loads transport globals from distribution into XTMP 4 KIDS prompts the user to see if they want to run the environment check for each transport global if unsuccessful the process quits here the developer may or may not KILL INSTALL file 9 7 entries and transport globals from X TMP 5 The installer can print the contents of the transport global compare the contents to the current system and verify checksums of the transport global Phase 2 Answering Installation Questions for Transport Globals in a Distribution 1 Using the Install Package s option the installer selects a distribution to install by choosing an entry from the INSTALL file 9 7 2 KIDS runs the environment check for the first transport global the environment check can allow KIDS to install the transport global cancel installation of the transport global or cancel installation of all transport globals in the distribution The installer answers pre installation questions for the first transport global The installer answers standard KIDS questions for the first transport global The installer answers post inst
227. Patch XU 8 0 355 added the following routine for TaskMan load balancing in Cach M Implementation Kernel Load Balance Routine Cach CACHE2 com file logical name in ZTM6 If the com file value is set that com file will be run each time TaskMan gets the balance value The logical name defaults to VISTAS METRIC or uses the value entered The normal way would be to have CACHE2 in the field and use the following two scripts e GET_METRIC COM This script sets the logical VISTAS METRIC It can be run by TaskMan or from the TM lt node gt batch queue with the METRIC_SCHEDULE COM script e METRIC_SCHEDULE COM tThis script takes a parameter of the number of seconds to reschedule itself It defaults to 15 seconds and runs under the SYSTEM user NOTE These scripts are located in the same directory as the TaskMan in DCL files Use of TaskMan in DCL is optional It is all right to run multiple TaskMan Managers without using load balancing it is also all right if load balancing is set up and only one Manager is running that Manager automatically takes all jobs itself If one Manager s CPU has the LOAD BALANCE ROUTINE field filled in and another running Manager s CPU does not the Managers acts as if no load balancing is taking place In short the only ramification from various combinations of Managers with the LOAD BALANCE ROUTINE field filled in or not is that load balancing might not take place The load balancing routi
228. Purge Build or Install Files option in the Purge Build or Install Files topic in the KIDS System Management Utilities chapter in this manual July 1995 Kernel Systems Management Guide 23 21 Revised June 2008 Version 8 0 KIDS System Management Installations Figure 23 15 Installation of a global distribution Load a Distribution option Select Installation Option Load a Distribution Enter a Host File DMANAGER XGGLOBAL DAT KIDS Distribution save on Jan 26 2004 12 58 25 Comment GLOBAL PACKAGE THiS Distribution Contains the following Iransport globals GLOBAL PACKAGE 1 0 This is a Global Distribution It contains Global s that will update your system at this time The following Global s will be installed XGRON 1 Overwrite XGRON PX Replace XGRON TX Overwrite If you continue with the Load the Global s will be Installed at this time Want to Continue with Load YES lt Enter gt Loading Distribution Globals will now be installed OK YES lt Enter gt Installing Global s Jan 26 2004 13 04 16 GLOBAL PACKAGE 1 0 Installed Jan 26 2004 13 04 17 Select Installation Option 23 22 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations Alpha Beta Tracking Kernel provides a mechanism for tracking and monitoring installation and option usage during the alpha and beta testing phases of VistA software applic
229. QKQTL 28 3 Global Block Count Option 28 1 Global Distributions 23 6 23 7 GLOBAL LOCK Field 36 18 12 Globals AQIS 20 7 AMZLIS 1 15 1 AMLIS 2 15 1 A MLIS 3 22 15 1 PZISL 18 13 AXYZTER 13 2 13 5 AKL TSCH 20 2 20 5 20 7 21 8 21 11 22 19 22 27 22 32 AQTL TSK 20 2 20 5 21 8 21 11 22 2 22 17 22 30 22 32 AKLZUA 3 05 3 29 ADISV 3 25 5 10 5 11 5 13 5 15 KILLing 5 11 5 13 TMP 7 12 7 13 AUTILITY J 5 12 5 13 7 12 7 13 AXMB 17 6 AXMBS 17 6 AXTMP 7 10 7 12 7 13 23 7 23 9 23 20 SXUSEC 0 3 29 7 12 AXUTL 7 12 7 13 7 19 15 10 Display Nodes 7 17 Structure and Function 7 16 User Stacks 7 16 Installing Global Distributions 23 21 KIDS Transport Global 23 1 Backup 23 15 Compare 23 3 23 7 23 13 Create 23 2 23 5 24 10 24 11 Definition 23 1 Environment Check 23 7 Export 23 2 Install 23 3 Load from Distribution 23 3 23 7 23 9 Load from PackMan Messages 23 3 23 7 Print 23 3 23 7 23 12 Processing 23 16 Verify 24 10 Verifying Checksums 23 12 Purging 7 12 Scratch 18 3 XUTL 7 14 7 20 Kernel Systems Management Guide Index 15 Version 8 0 Index Glossary Home Page Web Address Glossary 6 Go home Jump 6 7 Grant Access by Profile Option 3 9 3 21 Granting File Access Purpose 5 4 Group Routine Edit Option 26 5 H Halt Option 6 7 HEADER Field 26 7 11 11 1 11 4 Header Page TaskMan 21 13 Help At Prompts xxxv Entering Option to
230. R PORT code of the home device s terminal type Queuing to Slaved Printers If queuing to a slaved device is desired then the SLAVE FROM DEVICE field of the DEVICE file 3 5 must be used This field is a pointer to the DEVICE file 3 5 Data must be entered in this field for the entry for the slaved printer This data should point to the home device entry unless the slaved printer is attached to a terminal on a Terminal Server 1 e a virtual terminal If queuing to a slaved device is being performed from a virtual terminal then a third device entry must be established that fully describes the home device with a type of TRM This device should be entered into the SLAVE FROM DEVICE field NOTE When queuing to a slaved device from a terminal on a Terminal Server the user must be fully logged off the computer system and logged off the port by the time the queued task is scheduled to run 18 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 IV TaskMan July 1995 Revised June 2008 Kernel Systems Management Guide Version 8 0 IV 1 TaskMan V 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 19 TaskMan User Interface The Kernel TaskMan TM software allows you to run tasks e g VA FileMan prints and sorts in the background and lets you continue working without interruption Creating Tasks VistA runs in a multiprocessing environment which means the computer can wor
231. RAMETERS file 14 7 6 Edit TaskMan Parameters Figure 21 15 Sample user dialogue to edit TaskMan parameters Select Edit Taskman Parameters Option SIT lt Enter gt e Parameters Edit Select TASKMAN SITE PARAMETERS BOX VOLUME PAIR ISC L ISOT Or CoA 2 ISC ISCISC6A2 namespace configname CHOOSE 1 2 1 lt Enter gt ISC ISCISC6A1 ota Have node name VAX ENVIROMENT FOR DCL ISC6A1 TaskMan call the script Balance Interval 30 lt Enter gt LOAD BALANCE ROUTINE S S CACHE2 Q DHCPSTASKMAN GET METRIC COM LOAD BALANCE ROUTINE CACHE2 Submit the METRIC_SCHEDULE COM file July 1995 Kernel Systems Management Guide 21 17 Revised June 2008 Version 8 0 TaskMan System Management Configuration How to Restart TaskMan when Running in a DCL Context To manually restart TaskMan when TaskMan is running in a DCL context you can either e Signin as OpenVMS user TASKMAN and DO RESTARTA ZTMB e Sign in from an OpenVMS account that has the OPER and SYSPRV privileges and DO RESTART ZTMB This submits the Manager to run under the username TASKMAN In either case however do not use the Restart TaskMan option in the Kernel menus it is not compatible with TaskMan in a DCL context Figure 21 16 ZTM2WDCL COM Command File Sil KERNEL or gt t Pi os the Cache contig that taskman should start ain S P2 is the namespace that taskman should start in Sl Po Muli to START and 1 6 RESTART on ol This fil
232. REF For a list of the code formats for the RESCHEDULE FREQUENCY field please refer to the SPECIAL QUEUEING topic that follows For the incremental scheduling frequencies every n seconds hours days or months the increment is added to the scheduled date and time in the QUEUED TO RUN AT WHAT TIME field to determine when the task should run next As of Kernel V 8 0 if the incremented time is in the past however TaskMan keeps adding the increment until a future time is reached only then does it reschedule the task TASK PARAMETERS The TASK PARAMETERS field provides a way to pass data to a scheduled option TASK PARAMETERS holds a string that is passed to scheduled jobs through the ZTQPARAM variable Ideally the developer of an option that uses the TASK PARAMETERS string should describe the format and meaning of the string in the option s DESCRIPTION field July 1995 Kernel Systems Management Guide 22 21 Revised June 2008 Version 8 0 TaskMan System Management Operation SPECIAL QUEUEING Use the SPECIAL QUEUEING field 9 in the OPTION SCHEDULING file 19 2 to designate which option is scheduled to be run by TaskMan NOTE In order to queue a task its SCHEDULING RECOMMENDED field 209 in the OPTION file 19 must be set to YES Valid values are Table 22 1 Special Queueing field settings Option Description STARTUP TaskMan will queue the job to run whenever the TaskMan computer is started i e at System Boot
233. REMOVE Option 13 4 XUTM ERROR SHOW Option 22 25 XUTM INQ Option 22 2 XUTM MGR Menu 13 2 XUTM QCLEAN Option 21 8 22 17 22 24 22 30 XUTM REQ Option 20 8 22 5 22 33 XUTM RESTART Option 22 14 22 15 XUTM RUN Option 22 15 XUTM SCHEDULE Option 22 19 XUTM STOP Option 22 15 22 16 22 29 XUTM SYNC Option 22 16 XUTM TaskMan Namespace 20 5 XUTM TL CLEAN Option 22 6 XUTM UCI Option 21 8 XUTM USER Option 19 2 22 33 XUTM UTIL Menu 13 2 22 7 XUTM VOLUME Option 21 5 XUTM WAIT Option 22 15 XUTM ZTMON Option 21 13 22 7 22 36 XUTMGR Menu 22 1 XUTTEST Option 15 12 XUUSERDISP Option 2 11 XUUSERSTATUS Option 3 28 XUXREF Option 7 5 XUXREF 2 Option 7 6 Y Your future tasks Option 22 3 Z Z Namespace 9 11 ZIS Global 20 7 ZIS Variable 18 9 ZIS 14 5 LOGON volume set Node 3 8 ZIS 1 Global 15 1 ZIS 2 Global 15 1 ZIS 3 22 Global 15 1 ZISL Global 18 13 ZISQUIT Variable 15 5 ZOSE Nodes 22 37 ZOSEF VOL Node 21 6 ZSTU Routine 21 11 ZTCPU Variable 21 15 ZTER Global 13 2 13 5 ZTER Routines 13 2 ZTLOAD API 18 13 20 2 22 34 ZTM TaskMan Namespace 20 5 ZTMGRSET Routine 28 3 ZTMOVE Utility Toolkit 22 34 ZTMQ Security Key 20 8 22 2 22 5 22 6 ZTMQUEUABLE OPTIONS Menu 3 25 7 1 17 9 22 17 22 18 ZTMSH Routine 21 13 ZTMSWDCL COM 21 19 ZTMWDCL COM 21 18 ZTQPARAM Variable 22 21 ZTSCH Global 20 2 20 5 20 7 21 8 21 11 22 19 22 27 22 32
234. RGIN 80 lt Enter gt Sample output Shortcuts of the CPT file sorted by Name NOV 23 1994 13 36 PAGE 1 FREQUENTLY USED NARRATIVE Using the Utilities for MTLU Option The following is a list of the options and their descriptions that comprise the Utilities for MTLU menu XTLKUTILITIES This option can only be accessed by holders of the XTLKZMGER security key e The Delete Entries From Look Up option XTLKMODPARK deletes entries from the LOCAL LOOKUP file 8984 4 In order to do this there cannot be any shortcuts synonyms or keywords associated with the file to be deleted This option should be used as an IRM developer utility and can only be accessed by holders of the XTLKZMGR security key e The Add Entries To Look Up File option XTLKMODPARS sets entries in the LOCAL LOOKUP file 8984 4 This option should be used as an IRM developer utility and can only be accessed by holders of the XTLKZMGER security key In order to add entries with this option DUZ O must be set to an at sign programmer access e The Add Modify Utility option XTLKMODUTL is used to make or edit entries in the LOCAL KEYWORD 8984 1 LOCAL SHORTCUT 8984 2 and LOCAL SYNONYM 8984 3 files Delete Entries from Look Up Option The Delete Entries From Look Up option XTLKMODPARK is used to delete a reference file from a site s LOCAL LOOKUP file 8984 4 25 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi
235. ROG gt PG Programmer mode lt locked with XUPROGMODE gt XUPROGMODE Calculate and Show Checksum Values XT SUMBLD CHECK Delete Unreferenced Options XO UNREF D OPTIONS Error Processing tes XUERRS General Parameter Tools XPAR MENU TOOLS Global Block Count XU BLOCK COUNT List Global lt locked with XUPROGMODE gt XUPRGL Routine Tools XUPR ROUTINE TOOLS Test an option not in your menu lt locked with XUMGR gt XT OPTION TEST Delete Unreferenced Options The Delete Unreferenced Options option XQ UNREF D OPTIONS is used to examine those options which are not on any menu are not used as primary or secondary options and are not tasked to run The user may then decide in each case whether to delete the unreferenced option Global Block Count Option The Global Block Count option XU BLOCK COUNT can be used to count the number of data blocks in a global Listing Globals Option The List Global option XUPRGL is found on the Programmer Options menu locked with the XUPROG key This option is also locked with the XUPROGMODE key as an extra level of security It can be used to list the contents of a global to the screen It makes use of operating system specific utilities such as G the global lister The option is locked with the XUPROGMODE security key The corresponding direct mode utility can be used in programmer mode For example gt D OS specific July 1995 Kernel Systems Management Guide
236. ROUND PRINT The Print Options Recommended for Queueing option XUTM BACKGROUND RECOMMENDED displays all options in the OPTION SCHEDULING file 19 2 that are recommended for scheduling by the option s developer The Print Options that are Scheduled to run option XUTM BACKGROUND PRINT lists all currently scheduled options on your system By comparing these two reports you can see if any options recommended for scheduling are not scheduled on your system and vice versa 22 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Schedule Unschedule Options Figure 22 22 Schedule Unschedule Options option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Schedule Unschedule Options XUTM SCHEDULE The Schedule Unschedule Options option XUTM SCHEDULE is a straightforward VA ScreenMan edit option and allows you to schedule and unschedule options After you select the option to schedule you are prompted for information about the task you want to set up You can edit the following fields in the OPTION SCHEDULING file 19 2 e QUEUED TO RUN AT WHAT TIME e DEVICE FOR QUEUED JOB OUTPUT e QUEUED TO RUN ON VOLUME SET e RESCHEDULE FREQUENCY e TASK PARAMETERS e SPECIAL QUEUEING The cross references on these fields make calls to TaskMan s API to update the TASKS file 414 4 and AJMZTSCH NOTE In order to queue a task its SCHEDULING
237. RS 26 8 LTER 13 2 ZTRDEL 26 8 A ZTMSH 21 13 AXTLKDICL 25 2 25 22 AXTLKWIC 25 20 AZU 3 8 Component Editing 24 10 Cross references 12 5 Verification Tools 27 2 27 3 DIC 5 3 DIE 5 3 Index 34 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 DIP 7 20 INIT 23 1 23 5 Load 26 8 NVSTNSET 15 7 Save 26 8 XTER 13 2 XTLATSET Routine 15 7 XTLKTOKN 25 2 XTRCMP 26 7 XTVCHG 26 5 XTVNUM 26 6 XUINCON 5 14 XUSCLEAN 7 12 ZSTU 21 11 ZTMGRSET 28 3 Routines by Patch Number Option 26 5 RPC Broker Documentation Web Address 2 1 Rubber band Jump 6 6 6 9 RUN Node 20 6 22 8 22 9 22 14 22 29 RUN State TaskMan 22 37 Running File Access Security Conversion 5 10 Advance Preparation 5 10 Advantages 5 10 Sequences of Tasks 18 13 TaskMan with a DCL Context 21 14 Running tasks Option 22 4 S SAC xxxvi 7 8 22 17 Save Routines 26 8 SCHEDULE File 20 1 20 2 20 5 20 6 20 7 21 1 21 2 21 4 22 7 22 11 22 30 22 32 22 33 22 34 22 36 TaskMan 22 27 Schedule List 20 6 22 9 Node 22 27 Schedule Unschedule Options Option 7 4 22 17 22 19 22 23 Scheduling Installations KIDS 23 16 Options 7 4 TaskMan 22 18 SCHEDULING RECOMMENDED Field 209 7 4 22 19 22 22 Scratch Global 18 3 Screen Editor VA FileMan 2 6 3 5 3 20 3 21 Scripts Index GET_METRIC COM 21 12 METRIC_SCHEDULE COM 21 12 SDP Devices 18 15 SE TIMEOUT ON
238. RT 18 16 18 17 OpenVMS Specific DEVICE Fields DEVICE File 3 5 15 7 OUT OF ORDER MESSAGE 2 7 10 7 11 7 14 11 1 11 3 11 8 OUT OF SERVICE 21 7 OUT OF SERVICE DATE 3 2 PAC Programmer Access Code 3 22 PAGE LENGTH TERMINAL TYPE File 3 2 15 8 18 10 18 11 PASSWORD 15 7 15 8 PATCH APPLICATION HISTORY Multiple 23 5 Index PERFORM DEVICE CHECKING 3 2 PERMITTED DEVICES Multiple 7 11 PERSON LOOKUP 8 4 PHONE 3 3 22 PHONE 4 3 22 PHONE HOMB 2 9 3 22 3 23 POST SIGN IN MESSAGE 3 7 POST CLOSE EXECUTE DEVICE File 3 5 15 2 15 4 18 3 PREFERRED EDITOR 2 10 3 20 3 21 PRE OPEN EXECUTE DEVICE File 3 5 15 2 15 4 15 5 PRIMARY MENU OPTION 3 1 3 8 3 18 3 19 3 26 9 3 9 4 PRINT SERVER NAME OR ADDRESS 65 15 7 PRIORITY 3 8 Options 7 3 Server Options 11 3 PRIORITY AT RUN TIME 21 13 PROHIBITED TIMES FOR SIGN ON 3 2 3 3 3 22 QUEUVED TO RUN AT WHAT TIME 22 19 22 20 22 21 22 23 QUEUED TO RUN ON VOLUME SET 22 19 22 20 22 22 QUEUING DEVICE File 3 5 15 4 QUEUING REQUIRED Multiple 7 11 REMOTE PRINTER NAME 67 15 7 REPLACEMENT VOLUME SET 21 8 Required Fields NEW PERSON File 200 3 9 REQUIRED VOLUME SET 21 7 RESCHEDULE FREQUENCY 22 19 22 21 22 23 22 24 RESCHEDULING FREQUENCY 6 22 22 RESOURCE SLOTS 18 13 RESOURCE SLOTS 35 11 2 11 5 RESTRICT DEVICES 7 11 REVERSE NEGATIVE LOCK 8 5 RIGHT MARGIN TERMINAL TYPE File 3 2 15 8 ROUTINE
239. Redistribution Select INSTALL NAME ZXG 1 0 lt Enter gt Loaded from Distribution This distribution was loaded on Feb 28 2004 08 15 05 with header of It consisted of the following Install s ZXG 1 0 Want to make the Transport Globals Permanent NO YES Want to continue with the conversion of the package s NO YES DONE Select Utilities Option Then we would convert the patch distribution ZXG 1 0 1 into a form ready to re distribute Figure 24 5 Convert Loaded Package for Redistribution Sample user dialogue 2 of 2 Select Utilities Option Convert Loaded Package for Redistribution Select INSTALL NAME ZXG 1 0 1 lt Enter gt Loaded from Distribution This distribution was loaded on Feb 28 2004 08 15 35 with header of It consisted of the following Install s FRG Fe OL Want to make the Transport Globals Permanent NO YES Want to continue with the conversion of the package s NO YES DONE 3 Create the new distribution with the Transport a Distribution option Select each build from the original distributions that you want to be part of the new distribution For each build that you select you should be told that the transport global already exists and be asked 1f you want to use this transport global Answer YES in each case to use the current transport global Once you have selected all of the builds for the new distribution go ahead and create the new distribution July 1995 Kernel Systems Manag
240. Roos a a e a 9 1 User Interace Acting asa Deletie aea N A 9 2 Derai e Me Mirea a a gn ere te Sree 9 2 PUE OS UISEl SO OG i E A os biseaanudineaceintaalahet 9 2 Build a New Ment O pton cisveciinct toca eee hatte ede verti a a habagin sen a 9 4 Copy Everything About an Option to a New Option Option ccccecccssseeseeeeeeeeeeeeeeeees 9 4 Copy One Users Menus and Keys to others Option sssessssseerssssssssseersssssssseeressssssseerres 9 4 Limited File Manager Options Build Option cceccccccccessssseeeeceeceeeeeeseeceeeeeeeaaeeeseeees 9 5 system Management Managing Dele cates coe a E 9 7 Delegating Options Select Options to be Delegated Option nnnessessssseeesssssssseerrsssssse 9 7 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Contents Replicate or Replace a Delegate Option cc ceseeceseccececeeeeeeeeecceececaaeeeeeeceseeeeaeeeenes 9 10 Remove Options Previously Delegated Option cccccccccsssseseececeeeeeseeseeecceeeeenaeeseeeees 9 10 Specify Allowable New Menu Prefix Option ccccccssecsscccccecceeesseeecceeeeeeaeeseeeeeeeeeeaeeees 9 11 RDO Seesaw soap ences as E uecuaremianeeeentcosatad 9 11 tO AlE a a cack sata teamad eee anek oe caaten tone taualale teesiartn eiacaceeteteen 10 1 EES a Wa aa Belem pe E erm E E A A E Some E Cn EE E E ORES Seg 10 1 Proce me AT aa A E TA 10 1 Delenn A ler e a a a aa 10 3 Forvardine ACTS a a A howe aacanusbii
241. S file 8989 3 Its value sets an upper limit for number of M processes interactive background and system that can run concurrently on the specified Volume Set or CPU The TASKMAN JOB LIMIT a field in the TASKMAN SITE PARAMETERS file 14 7 should be set to a number slightly lower than MAX SIGNON ALLOWED to leave room for a few interactive logons when TaskMan is busiest For OpenVMS sites the OpenVMS interactive logins parameter set by the DCL command SET LOGINS INTERACTIVE should be set to a number less than the Kernel MAX SIGNON ALLOWED to conserve system resources If the OpenVMS limit is set too high in relation to the Kernel limit users will try to access Kernel only to be rejected when reaching Signon Security That means that they would waste system resources by creating a new OpenVMS process and activating a Cach image all to no avail PROHIBITED TIMES FOR SIGN ON Time periods can be specified during which interval signons can be barred by device or by user This is controlled by the PROHIBITED TIMES FOR SIGN ON field in the DEVICE file 3 5 and a comparable field in the NEW PERSON file 200 July 1995 Kernel Systems Management Guide 3 3 Revised June 2008 Version 8 0 Signon Security System Management Figure 3 4 Signon flow chart Display Introductory Text Get system parameters from KERNEL SYSTEM PARAMETERS File Update system parameters from DEVICE File 1 Number of bad attempts allowed 2 Lockout time
242. SPF200 security key or if another default set of New Person Identifiers has been defined July 1995 Kernel Systems Management Guide 3 9 Revised June 2008 Version 8 0 Signon Security System Management Access is assigned according to an existing user profile Characteristics of the new user are cloned from the existing one Rather than copying the characteristics from an actual user creating several dummy users with profiles of typical positions can be worthwhile A user e g PHARMACY TECH or RESIDENT SURGERY could be created with the appropriate user attributes including menu options keys and service section codes Several steps are involved in copying access to new or existing users First you enter the name of the user account to clone from Then optionally you can specify a TERMINATION DATE Next you enter the names of the new users to create The system will pause for each new user as it verifies identifiers checks for duplicates and updates the NEW PERSON file 200 You must enter a device upon which to print the computer account notification letters You can either run the access assignment immediately or queue it for a later time Security Forms Figure 3 8 Reprint Access agreement letter option SYSTEMS MANAGER MENU EVE User Management XUSER Reprint Access agreement letter XUSERREPRINT Two security forms are printed for each new user 1 The Computer Account Notification Includes the user
243. Sample user dialogue cccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 18 6 Figure 18 6 Terminal Type Edit option Sample user dialogue ccccceeseeeeeeceeecceeeeeeeeeeeeeeeeeeeeees 18 6 Figure 18 7 Hunt groups Sample hunt group device NaMe ccccceeesssseesseseeeeeececeeeeeeeeeeneaeeeeeeeeeeees 18 7 Figure 18 8 Hunt Group Manager Menu Options ecs r A A E AA 18 8 Figure 18 9 Edit Devices by Specific Types option sive nice cadens aii ees 18 10 Figure 18 10 Network Channel Device Edit Option 2 0 0 0 cceccsccccccceeseseeeccecceeeeeeseeeeceeeeeaeaeseeeeeeeenes 18 11 Figure 18 11 Network Channel Device Edit option Sample output cc cceeecssecceeeeeeeeeeeeeeeeeees 18 12 Figure 18 12 Resource Device Edit OpUO Miinan saiscandetacstinciacscaddenseheinte a AE E 18 14 Figure 18 13 Resource device Sample output cccccccccccccsssseseeeccceceeaeesseeececeeessaeeeeeeeeeesessaeaeeneeess 18 14 Figure 18 14 Slaved Printer Sample user dialogue cccccccccceeeeeeeeseesseeeeeeeeecceeeeeeeeeeeaaaaeeeeeeees 18 15 Figure 18 15 Home Device example VT320 DEVICE file 3 5 entry ccccccccsssseeeeeeeeeeees 18 16 Figure 18 16 Home Device example VT320 TERMINAL TYPE file 8 2 entry 00 0 18 17 Figure 18 17 Slaved Printer example DEC LASO DEVICE file 3 5 entry 2 0 0 0 eeeeeeeeeeeeees 18 17 Figure 18 18 Slaved Printer example DEC LASO TERMINAL TYPE file 8 2
244. Server on which it is running and does not process the Device Waiting List or the Job List The Volume Set next run time task and device lO are stored here AZT SCH DEV This node stores the Device Allocation List This list is used by TaskMan to coordinate its allocation of devices to tasks The presence of a node indicates that TaskMan has already allocated this device to a specific task that has not yet gained ownership of it It tells TaskMan not to give the device to another task When the task for whom the allocation node was established gains ownership of the device or fails due to possession by some interactive job the node is KILLed off The H value is used in case the task fails to remove its own node for some reason after two minutes TaskMan KILLs the node on its next idle loop A ZTSCH ER This node stores the Taskman Error Log July 1995 Kernel Systems Management Guide 22 27 Revised June 2008 Version 8 0 TaskMan System Management Operation A ZTSCH ES This node stores the Error Screens A LTSCH IDLE This node is used to ensure that the Manager s idle loop activities are spaced out correctly in case multiple Managers are being run in the same environment A LTSCH I1O This node stores the Device Waiting List The device IO value is the value for the task s device and should not be the IO of a spool or host file device The run time subscript the total number of seconds contained in the run ti
245. Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues SDP Obsolete Though the Sequential Disk Processors SDP SDP entry is still found in the DEVICE file 3 5 it is obsolete and users should now use Host File Server HFS devices REF For more information on HFS devices please refer to the Host Files chapter in this manual Slaved Printers User Interface If your terminal has an auxiliary printer port with a printer directly attached you can send output normally destined for the CRT terminal directly to a printer Output for the terminal is redirected from the host computer through the terminal s auxiliary port to the printer Such printers are commonly called slaved printers or slaved devices If slaved printing is available from your terminal you can send a printed report to your slaved printer by entering the device name that corresponds to your slaved printer like this Figure 18 14 Slaved Printer Sample user dialogue DEVICE SLAVELA5O You can consult your local IRM to find out if slaved printing devices are available System Management There are two modes of slaved printing e Auto Print Mode a k a Copy Print Mode When Auto Print Mode is toggled on output is displayed on the terminal as well as printed on the printer Special escape sequences and control characters such as those that are normally used to adjust fonts pitches are not passed to the printer however t
246. TE QUEUING SUPPRESS FORM FEED OpenVMS Specific DEVICE Fields The DEVICE file 3 5 can store operating system specific information Several fields are included for example in the DEVICE file 3 5 to configure terminals and ports on Terminal Servers as part of an OpenVMS start up command file These are e LAT SERVER NODE 61 e LAT SERVER PORT 62 e VMS DEVICE TYPE 63 e LAT PORT SPEED 64 e PRINT SERVER NAME OR ADDRESS 65 e TELNET PORT 66 e REMOTE PRINTER NAME 67 Kernel Toolkit software distributes the XTLATSET and NVSTNSET routines that makes use of these fields NOTE These fields are used by VMS and not Cach Device Security To regulate who can use a particular device you can use the PASSWORD and SECURITY fields July 1995 Kernel Systems Management Guide 15 7 Revised June 2008 Version 8 0 Device Handler System Management The SECURITY field 1f populated should contain a string of characters to compare with a user s FILE MANAGER ACCESS CODE field 3 DUZ O when the device is selected Access is denied to anyone whose DUZ Q does not contain one of the specified characters As with other uses of DUZ Q the at sign programmer access will override this restriction The PASSWORD field if populated forces all users trying to log on to the device to be prompted for the matching password before entering their Access code TERMINAL TYPE File 3 2 The TERMINAL TYPE file
247. TLU 25 1 25 6 Example 25 8 Programmer mode 3 22 8 2 Programmer Options 8 2 23 2 26 1 26 3 27 3 28 1 Prohibited Times 7 11 Protocols Marked Out of Order in Protocol File Option 7 11 Purge Alerts for a User 10 7 Purge Build or Install Files 24 7 Purge Data Audits 5 5 Purge DD Audits 5 5 Purge Error Log Of Type Of Error 22 26 Name 6 3 Purge Inactive Users Attributes Utility 3 26 July 1995 Kernel Systems Management Guide Index 27 Revised June 2008 Version 8 0 Index Purge Log of Old Access and Verify Codes Option 3 29 Purge old spool documents 17 8 Queuable Task Log Clean Up 22 17 Reactivate a User 3 26 Recover Deleted Option Set 7 10 Reindex the users Key s 8 5 Reindexing All Users Security Keys 8 5 Release user 3 27 Remove Error Screens 13 4 Remove Options Previously Delegated 9 10 Remove Out Of Order Messages from a Set of Options 7 10 7 11 Remove Taskman from WAIT State 22 15 Replace a Delegate 9 9 Replicate or Replace a Delegate 9 7 9 10 Report Menu for Alerts 10 8 Reprint Access Agreement Letter 3 17 Requeue Tasks 11 2 20 8 22 5 22 33 Resource Device Edit 18 14 Restart Install Of Package s 23 20 Restart Session 6 7 Restart Task Manager Option 22 14 Restart TaskMan 21 18 Restrict Availability of Options 7 11 Restricting Usage 7 11 Rollup Patches into a Build 24 9 Routine Compare Current with Previous 27 2 Routine Edit 26 5 Rou
248. TO UCI Field 21 9 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TO VOLUME SET Field 21 9 VOLUME SET 14 5 3 8 20 5 20 7 21 1 21 5 21 9 22 17 22 35 22 37 DAYS TO KEEP OLD TASKS Field 21 8 INHIBIT LOGONS Field 21 7 LINK ACCESS Field 21 7 OUT OF SERVICE Field 21 7 REPLACEMENT VOLUME SET Field 21 8 REQUIRED VOLUME SET Field 21 7 Standardized VA Cach and GT M Configuration 21 10 TASKMAN FILES UCI Field 21 8 TASKMAN FILES VOLUME SET Field 21 8 TYPE Field 21 7 VOLUME SET Field 21 6 Who Needs File Access 5 4 XTV ROUTINE CHANGES 8991 27 2 XTV ROUTINE CHANGES File 8991 27 2 Find a User Option 3 27 Fix Help Frame File Pointers Option 12 5 Fix Option File Pointers Option 7 9 Flow Chart Entire Routine Option 26 4 Flow Chart from Entry Point Option 26 5 FORM FEED Field TERMINAL TYPE File 3 2 15 8 18 10 18 11 Form Feeds 18 5 SUPPRESS FORM FEED AT CLOSE Field 18 6 System Management 18 6 User Interface 18 5 Forms Security 3 9 3 10 FORUM ROUTINE File 9 8 23 12 24 12 26 7 Forwarding Alerts 10 4 FROM UCI Field 21 9 FROM VOLUME SET Field 21 9 FUNCTION File 5 3 20 Functional Description Multi Term Look Up MTLU 25 1 Further Delegation 9 9 Future tasks Option 22 4 G General Processor Mode 21 4 July 1995 Revised June 2008 Index GENERAL PURPOSE VOLUME SET Type 21 7 GET_METRIC COM Script 21 12 GETENV4 ZOSV API 21 3 Global A
249. TURE BLOCK TITLE Field 4 1 Signoff Error Handling 2 6 Normal 2 5 Signon 2 1 Audits 3 28 Devices 15 10 Enabling Disabling Logons 3 8 Flow Chart 3 3 Jump Start 2 5 Lock out Times 3 2 Parameters Checked 3 2 Process 3 1 Shortcuts 2 5 Statistics 3 28 Terminal Type Selection 15 11 SIGN ON LOG File 3 081 3 27 3 28 3 29 Purging 3 28 Signon Security Introductory Text 3 1 Summary 2 12 System Management 3 1 Add a New User to the System Option 3 9 Grant Access by Profile Option 3 9 User Interface 2 1 Change my Division Option 2 8 Edit User Characteristics Option 2 9 Switch UCI Option 2 12 July 1995 Revised June 2008 Index SIGN ON SYSTEM DEVICE Field DEVICE File 3 5 15 4 15 10 15 13 Site Parameters 3 1 21 2 Site Parameters Edit Option 21 13 SLAVE FROM DEVICE Field 18 18 Slaved Printers 18 15 18 16 Auto Print Mode 18 15 Copy Print Mode 18 15 Device and Terminal Type File Entries 18 16 Printer Controller Mode 18 15 Processing Steps 18 17 Queuing 18 18 System Management 18 15 Transparent Print Mode 18 15 User Interface 18 15 Software Components 20 5 23 4 24 9 24 11 Exported 23 1 23 4 23 12 KIDS Installations 23 8 SPAWN Command 20 2 21 5 Special Device Issues 18 1 Browser Device 18 1 Magtape 18 10 Network Channel Device Edit Option 18 11 Network Channel Devices 18 11 Resources 18 13 SDP 18 15 SPECIAL QUEUEING Field 22 19 SPECIAL QUEUEING Field 9 22 22 Spe
250. TaskMan screen reports whether the Manager is currently running on your machine and if so whether or not it is being delayed This is accomplished by comparing TaskMan s RUN Node to the M HOROLOG variable Under normal circumstances they should be within 15 seconds of each other though certain conditions can cause a difference of up to two minutes Any difference greater than that however is a sign that the Manager is being delayed typically by a problematic device or a recurring error Of course the Manager is also likely to fall behind if the system is saturated to the point where all of the jobs on the system are slow The last line of the first section evaluates the difference and guesses at the Manager s current condition The HOROLOG values are translated into an external format for your convenience in understanding the values Figure 22 9 Sample Monitor TaskMan screen Checking TaskMan Current H 54180 45147 MAY 04 1989 12 32 27 RUN NODE 54180 45145 MAY 04 1989 Q12 32 25 TaskMan is current Checking the Status List TaskMan job 4 status 54180 45145 RUN Main Loop There are 3 idle submanagers Checking the Schedule List TaskMan has 29 tasks in the Schedule List None of them are overdue Checking the TO Lists Last TM scan 54160 45146 TNA9995 Device _TNA9995 is not available and there are 7 tasks waiting Checking the Job List There are no tasks waiting for partitions For KDE ISCoV2 there are 2 tasks Not
251. Test an option not in your menu 28 2 Time 6 7 Toggle Options Protocols On and Off 7 10 Transfer Entries 5 6 Transfer Lines from Another Document 5 2 5 5 Transport a Distribution 23 5 24 5 TRM or VTRM Device Edit 15 6 Turn Data Audit On Off 5 5 UCI Association Table Edit 21 8 Unassign Editor 12 5 Unload a Distribution 23 20 23 21 Unreferenced 7 8 Unsuccessful tasks 22 4 Update Routine File 24 10 Update with Current Routines 27 2 User Alerts Count Report 10 9 User Inquiry 3 27 User Management 3 24 5 1 Index 28 Kernel Systems Management Guide July 1995 Revised June 2008 July 1995 Revised June 2008 User Management Menu 3 26 5 8 5 10 5 14 User Status Report 3 28 User s Toolbox 2 3 2 6 2 7 2 8 2 9 2 11 4 1 4 2 6 7 6 8 17 3 19 2 Utilities For MTLU 25 8 Utilities Menu KIDS 24 1 Utility Functions 5 6 VA FileMan 5 1 Variable Changer 26 5 Verifier Tools 27 1 Verifier Tools Menu 27 1 27 2 Verify a Build 24 10 Verify Checksums in Transport Global 23 12 Verify Package Integrity 24 11 Version Number Update 26 6 View Alerts VA 2 7 6 7 10 1 10 2 View data for Alert Tracking file entry 10 9 Volume Set Edit Option 21 5 Where am I 6 7 XPD BACKUP 23 15 XPD COMPARE TO SYSTEM 23 13 XPD CONVERT PACKAGE 24 4 XPD DISTRIBUTION MENU 23 2 XPD INSTALL BUILD 23 16 XPD INSTALLATION 23 8 XPD INSTALLATION MENU 23 3 XPD LOAD DISTRIBUTION 23 9
252. Typically it should be set to the same value as the MODE OF TASKMAN field for all BOX VOLUME PAIRs associated with this Volume Set in the TASKMAN SITE PARAMETERS file 14 7 This field must be filled in for all Volume Sets This field can have the following values e GENERAL PURPOSE VOLUME SET e PRINT SERVER e COMPUTE SERVER e OTHER NON TASKMAN VOLUME SET These values have the same meanings as the equivalent values for the MODE OF TASKMAN field in the TASKMAN SITE PARAMETERS file 14 7 as described previously in the Where Tasks Run topic in this chapter GENERAL PURPOSE VOLUME SET for Volume Sets is the rough equivalent of the MODE OF TASKMAN value GENERAL PROCESSOR for BOX VOLUME PAIRS The FILE SERVER value has been removed Volume Sets for File Servers should be set to a TYPE of OTHER NON TASKMAN VOLUME SET INHIBIT LOGONS Setting the INHIBIT LOGONS field to YES causes TaskMan to notify Signon that logons are now prohibited and to enter a PAUSE state stopping processing of tasks until logons are allowed again Under ordinary circumstances system managers should leave this field as NULL or NO LINK ACCESS The LINK ACCESS field should always be set to NULL or YES for the usual kinds of configurations used in VistA Answer NO to tell TaskMan that this Volume Set cannot be accessed by other Volume Sets using the local network links Tasks that request a Volume Set without link access are rejected by TaskMan Such Volume Sets are
253. U EVE User Management XUSER Edit an Existing User XUSEREDIT The attributes of an existing user can be edited with the Edit an Existing User option XUSEREDIT This option invokes a screen oriented display using ScreenMan It is impossible to exit the form and save changes unless all required fields e g the SERVICE SECTION field in the NEW PERSON file 200 are filled in Listed below are descriptions of each of the user attributes you can edit with the Edit an Existing User option NAME required The user s name should be entered in capital letters The syntax should be LAST FIRST MI with only a comma no spaces between the last and first name A middle initial can follow separated with a space and followed with a period It is not appropriate to add credentials e g M D since there are other ways to specify such additional information by the Title and the Signature Block Printed Name Furthermore the parsing algorithms commonly used in software applications only recognize two pieces before and after the comma rearranging them and using uppercase lowercase to generate First MI Last INITIAL The user s initials can be entered usually two or three capital letters with no spaces The NEW PERSON file 200 contains a lookup type cross reference by INITIAL C so if the INITIAL field is filled in the user can be found in the NEW PERSON file 200 by entering the initials For example just the initial
254. UNT View data for Alert Tracking file entry XOAL VIEW ALERT TRACKING ENTRY Critical Alerts Count Report Option The Critical Alerts Count Report option XQAL CRITICAL ALERT COUNT is used to generate a report of users who have more than a specified number of alerts containing the word critical or the words abnormal imaging between the specified start and end dates The report is presented in descending order for the number of critical abnormal imaging alerts present For each user who has the specified number of critical abnormal imaging alerts or more the report includes the following e User name e Section Service for the user e Number of alerts in the ALERT file 8992 e Last signon date e Number of Critical alerts or Abnormal Imaging alerts e Date of the oldest alert List Alerts for a user from a specified date Option The List Alerts for a user from a specified date option XQAL ALERT LIST FROM DATE is used to obtain an interactive list of alerts from the ALERT TRACKING file 8992 1 for a specified user starting from a specified date The listing includes the following e Internal Entry Number IEN for the alert in the ALERT TRACKING file 8992 1 e Date and time the alert was generated e Message text of the alert e Information about any option or routine to be executed for processing the alert 10 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Alerts Patient Alert List
255. UPROG on the Kernel Systems Manager Menu EVE as shown below Figure 23 1 KIDS menu options Select Systems Manager Menu Option Programmer Options KIDS Kernel Installation amp Distribution System XPD MAIN xx gt Locked with XUPROG PG Programmer mode XUPROGMODE gt Locked with XUPROGMODE Delete Unreferenced Options XO UNREF D OPTIONS Error Processing asa XUERRS General Parameter Tools XPAR MENU TOOLS Global Block Count XU BLOCK COUNT List Global XUPRGL xx gt Locked with XUPROGMODE Routine Tools XUPR ROUTINE TOOLS Test an option not in your menu XT OPTION TEST x gt Locked with XUMGR Select Programmer Options Option kids lt Enter gt Kernel Installation amp Distribution System Edits and Distribution XPD DISTRIBUTION MENU Utilities XPD UTILITY Installation XPD INSTALLATION MENU xx gt Locked with XUPROGMODE Patch Monitor Main Menu XTPM PATCH MONITOR MAIN MENU Patchman XPD AUTOMATIC PATCHING MENU As indicated by its name i e KIDS Kernel Installation and Distribution System KIDS supports two major functions e Distribution e Installation discussed in this chapter REF In addition KIDS also provides other utilities For more information on KIDS utilities please refer to the KIDS System Management Utilities chapter in this manual Distributions The distribution related options are located on the Edits and Distrib
256. UTE XUTL AKIPI XUTL XO 941065826 TIOS II 158 TROT 7p SE LUGS626 1055 24 NRO 94069026 LOSE CHV TLOOn GH TKO Do CO G40 LOSE CO T FA UXOUP OSI OS 6267 101 VIRM KO poe LOG S820 LOX W SCO Tror DYIP SC 59 1 Der Se 12 XO 54065626 TEN UXO 041005626 XOM PUT ECE XO p SAG S826 VIONT LAT DEVICE 3 29 XQT Nodes MENU Templates The XQT nodes are used to create a stack of options similar to the XQ stack when a MENU template is invoked These nodes are translated from the V A 200 DUZ 19 8 Multiple when a user precedes an option selection with a left square bracket character much like a PRINT template is invoked in VA FileMan For example 1f the user has defined a MENU template named DOIT using the Menu Template options of the User s Tool Box typing DOIT will load that sequence of options into the XQT nodes and begin executing them When a MENU template is requested by the user the option tree of that template is loaded into the XQT nodes and remains loaded as long as the user is logged on Further requests for DOIT will use that same stack Display Nodes Display nodes are stored in XUTL XQO internal number The first example below Figure 7 23 shows the display nodes for EVE the System Manager s Menu The internal number of EVE in this particular OPTION file 19 is 29 In the first part of the exam
257. UTPUT QUEUED NO YES REQUESTED TIME TO PRINT NOW 1T 18 00 lt Enter gt JUL 11 2004 18 00 REQUEST QUEUED Task number 856109 Whether you request queuing before or after naming a device Device Handler then asks you to specify a time for the queued job to run You can accept the default NOW or indicate a later time in the usual format Queuing sends output to TaskMan for scheduling Meanwhile you can continue working on the computer system without a delay Figure 14 9 Queuing a print job Sample user dialogue REQUESTED TIME TO PRINT NOW 1T 18 00 lt Enter gt JUL 11 2004 18 00 REQUEST QUEUED Task number 856109 REF For more information about queuing output please refer to the TaskMan User Interface chapter in this manual Specifying a Special Subtype There is an exception to using numbers in the second semicolon piece to indicate a right margin setting If instead of a number you use a letter and then a hyphen in a device specification e g P DEC the second semicolon piece specifies a terminal type entry from the TERMINAL TYPE file 3 2 to use for the output A terminal type entry specifies information about what commands to use with specific printers e g escape codes Figure 14 10 Terminal type device entry Without pauses If the home device is a video terminal output would be formatted DEVICE P DEC with page breaks and it would scroll without waiting for the user to press the Ent
258. Update Node 22 29 Update Routine File Option 24 10 Update with Current Routines Option 27 2 URLs Acronyms Home Page Web Address Glossary 6 Adobe Home Page Web Address xxxvii Glossary Home Page Web Address Glossary 6 Health Systems Design and Development Home Page Web Address xxxvi KAAJEE Documentation Web Address 2 2 Kernel Home Page Web Address xxxvi July 1995 Revised June 2008 RPC Broker Documentation Web Address 2 1 VA FileMan Documentation Web Address 3 20 5 1 5 5 VHA Software Document Library VDL Home Page Web Address xxxvii Usage Considerations Multi Term Look Up MTLU 25 2 USE AS LINK FOR MENU ITEMS Action 23 8 23 16 USE Command 20 3 Use of Slaved Printer Processing Steps 18 17 USE PARAMETERS Field DEVICE File 3 5 15 4 Use this Manual How to xxxiii User Alerts Count Report Option 10 9 USER CHARACTERISTICS TEMPLATE Field 3 23 User Inquiry Option 3 27 User Interface 1 2 Z Editor 28 3 Alerts 10 1 Browser Device 18 1 Device Handler 14 1 Electronic Signatures 4 1 Error Processing 13 1 File Access Security 5 1 Form Feeds 18 5 Help Processor 12 1 Host Files 16 1 Hunt Groups 18 7 Menu Manager 6 1 Miscellaneous Programmer Tools 28 1 Multi Term Look Up MTLU 25 3 Routine Tools 26 2 Secure Menu Delegation Acting as a Delegate 9 2 Security Keys 8 1 Signon Security 2 1 Slaved Printers 18 15 Spooling 17 1 TaskMan 19 1 Verification Tools 27 1 User Management Men
259. Update Routine File option Sample user dialogue Select Utilities Option Update Routine File Routine Namespace XU Routine Namespace XUI Routine Namespace lt Enter gt NAMESPACE INCLUDE EXCLUDE OK to continue YES lt Enter gt Want me to clean up the Routine File before updating YES lt Enter gt SORRY THIS MAY TAKE A FEW MOMENTS cnc Done Verify a Build Option The Verify a Build option XPD VERIFY BUILD checks whether a build entry s listed components actually exist on the current system This is useful for developers who are preparing to create a transport global They can check that there are actual components on the system matching the components requested in the build entry in advance of trying to create a transport global Therefore developers should use the Verify a Build option before creating transport globals from build entries 24 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Utilities For any component in the build entry that does not actually exist on the system the option outputs a one line message identifying the missing component with the appellation NOT FOUND The developer is also prompted with Do you want to remove the missing Files NO This allows you to verify if the missing component should in fact be removed from the build If the missing component is required the developer should create the missing component for th
260. VI 1 25 1 25 2 25 3 25 8 25 9 25 12 LOCAL LOOKUP 8984 4 VI 1 25 1 25 2 25 5 25 6 25 8 25 9 25 12 25 22 LOCAL SHORTCUT 8984 2 VI 1 25 1 25 2 25 3 25 5 25 8 25 9 LOCAL SYNONYM 8984 3 VI 1 25 1 25 2 25 3 25 8 25 12 NEW PERSON 200 2 3 2 8 2 9 2 12 3 1 3 3 3 4 3 5 3 6 3 7 3 8 3 9 3 10 3 17 3 18 3 20 3 24 3 25 3 29 3 30 4 2 5 1 5 2 5 3 5 8 5 9 5 10 5 12 5 13 5 15 6 9 7 7 7 18 8 2 8 4 8 5 8 6 9 8 9 9 11 9 15 10 17 7 22 3 Required Fields 3 9 NEW PERSON file 200 3 19 OLD ACCESS AND VERIFY CODES 200 XREF 3 29 OPTION 19 7 4 22 19 22 22 OPTION 19 3 20 6 3 6 5 6 9 7 1 7 2 7 3 7 4 7 8 7 9 7 14 7 15 7 16 7 17 7 18 7 19 8 2 9 2 9 10 11 1 11 2 11 6 11 8 11 9 12 6 12 7 28 2 Dangling Pointers 7 9 12 5 OPTION SCHEDULING 19 2 7 13 10 7 20 1 20 2 20 7 22 17 22 18 22 19 22 20 22 22 Other TaskMan Files 20 7 PACKAGE 9 4 5 6 23 1 23 4 23 5 23 6 24 7 PARAMETER DEFINITION 8989 51 10 10 PARAMETERS 8989 5 10 10 VI 2 PATIENT 2 5 8 Purpose of Granting Access 5 4 RESOURCE 3 54 18 13 ROUTINE 9 8 23 12 24 10 24 12 26 6 26 7 26 8 28 3 SCHEDULE 20 1 20 2 20 5 20 6 20 7 21 1 21 2 21 4 22 7 22 11 22 30 22 32 22 33 22 34 22 36 SECURITY KEY 19 1 8 2 8 4 8 5 12 6 SERVICE SECTION 49 3 17 3 21 SIGN ON LOG 3 081 3 27 3 28 3 29 Purging 3
261. XG 1 0 and a patch 1 e ZXG 1 0 1 are both loaded The Convert Loaded Package for Redistribution option is used to build a new distribution combining both original distributions Follow these steps to create a new distribution from existing distributions 1 Load the original distributions there is no need to install them however In this example we would load the distributions for ZXG 1 0 and ZXG 1 0 1 but we would not install them 2 Use the Convert Loaded Package for Redistribution option It lets you choose loaded transport globals and transfers them into a format ready for export Also it creates build entries for each software application contained in the distributions This allows you to create a new distribution containing the transport globals from the existing distributions Patch XU 8 0 44 added the Want to make the Transport Globals Permanent NO prompt answering YES to this prompt flags the global so that it is not deleted after the transportation This provides a Gold account or library of software and patches that are included in a Transport Global 24 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Utilities In this example we would first convert the loaded distribution ZXG 1 0 into a form ready to re distribute Figure 24 4 Convert Loaded Package for Redistribution Sample user dialogue 1 of 2 Select Utilities Option Convert Loaded Package for
262. XQHELP DEASSIGN Option 12 5 XQHELP DISPLAY Option 12 4 XQHELPFIX Option 12 5 XQHELP LIST Option 12 4 XQHELP MENU Menu 12 4 XQHELP UPDATE Option 12 5 XQHELP XREF Option 12 5 XQKEY ALTODEL Option 8 3 XQKEYDEL Option 8 3 9 8 XQLOCK1 Option 8 3 XQLOCK2 Option 8 3 XQMM J Variable 7 15 XQOOFF Option 7 10 XQOOMAIN Menu 7 10 XQOOMAKE Option 7 10 XQOON Option 7 10 7 11 XQOOREDO Option 7 10 XQOOSHOFIL Option 7 11 XQOOSHOPRO Option 7 11 XQOOSHOW Option 7 11 XQOOTOG Option 7 10 XQOPTFIX Option 7 9 XQPSM Variable 7 20 XQRESTRICT Option 7 11 XQSCHK Server Option Errors and Warnings 11 8 Testing 11 6 XQSERVER Bulletin 11 4 11 8 XQSMD ADD Option 9 9 XQSMD BUILD MENU Option 9 4 XQSMD COPY USER Option 9 4 XQSMD EDIT OPTIONS Option 9 2 Example 9 3 XQSMD LIMITED FM OPTIONS Option 9 5 Example 9 6 XQSMD MGR Menu 9 7 9 9 XQSMD REPLICATE Option 9 9 9 10 XQSMD SET PREFIX Option 9 5 XQSMD USER MENU 9 2 9 4 9 5 9 7 9 9 XQSMDFM Security Key 9 5 XQSPING Utility 11 5 XQSRV Namespace 11 5 XQT Nodes MENU Templates 7 17 XQT Variable 7 20 XQUIT Variable 7 15 11 3 XQUR Variable 7 20 XQUSER Variable 7 21 XQXFLG Variable 7 21 XQY Variable 7 21 XQYO Variable 7 21 XTER Routines 13 2 XTEFCE 26 5 XTFCR Option 26 4 XTLATSET Routine 15 7 XTLKLKUP Option 25 1 25 5 XTLKMODKY Option 25 2 25 16 XTLKMODPARK Option 25 1 25 8 XTLKMODPARS Option 25 1 25 9 XTLKMODPARS
263. XTLKUSER2 25 3 XTLKUTILITIES 25 8 XTMENU 25 3 XTV MENU Menu 27 1 27 2 XUAUDIT MENU 7 4 XUCOMMAND 7 1 7 7 7 8 XUERRS 13 4 XUFILEACCESS 5 8 5 9 5 10 5 13 5 14 5 15 XUOPTUSER 3 26 XUPROG 23 2 26 1 26 3 27 3 XUPR ROUTINE TOOLS 26 1 XUSER 3 24 5 1 5 8 5 10 5 14 XUSERTOOLS 2 7 XUSITEMGR 3 26 23 23 XU SPL MGR 17 7 XUTIO 15 2 15 12 XUTM ERROR 13 2 22 24 XUTM MGR 13 2 XUTM UTIL 13 2 22 7 XUTMGR 22 1 ZTMQUEUABLE OPTIONS 3 25 7 1 17 9 22 17 22 18 Messages Answerback 3 5 PackMan 23 3 23 6 23 7 23 9 TaskMan Rejection Messages 22 35 TaskMan States 22 36 MESSAGES Field 23 17 23 20 METRIC_SCHEDULE COM Script 21 12 Miscellaneous Programmer Tools 28 1 Z Editor 28 3 Delete Unreferenced Options Option 28 1 Global Block Count Option 28 1 List Global Option 28 1 Test an option not in your menu Option 28 2 User Interface 28 1 Missing Components 24 11 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Mixed OS Environment Fields DEVICE File 3 5 15 5 MNEMONIC Field 15 12 MODE OF TASKMAN Field 21 4 21 7 21 11 Modes Auto Print 18 15 Compute Server 21 4 Copy Print 18 15 General Processor 21 4 Other Non TaskMan 21 4 Print Server 21 4 Printer Controller 18 15 Transparent Print 18 15 Modify File Attributes Option 5 6 5 8 Monitor TaskMan Inspecting the Tasks in the Monitor s Lists 22 11 Monitor Taskman Option 21 13 22 7 22 36 Action Promp
264. XUSERAOLD Option 3 29 XUSERBLK Option 3 9 XUSER CLEAR ALL Option 3 8 XUSERDEACT Option 3 24 3 25 XUSEREDIT Option 3 17 XUSEREDITSELF Option 2 9 XUSERINQ Option 3 27 XUSERINT Option 3 1 XUSERLIST Option 3 27 XUSERNEW Option 3 9 XUSERPOST Option 3 7 XUSERPURGEATT Option 3 26 XUSERREACT Option 3 26 XUSERREL Option 3 27 XUSERTOOLS Menu 2 7 XUSESIG BLOCK Option 4 2 XUSESIG CLEAR Option 4 2 XUSESIG Option 4 1 4 2 XUSITEMGR Menu 3 26 23 23 Kernel Systems Management Guide Index 47 Version 8 0 Index XUSITEPARM Option 3 2 15 5 XUSPF200 Security Key 3 9 3 18 XU SPL MGR Menu 17 7 XU SPL PURGE Option 17 8 XU SPL SITE Option 17 8 XU SPL USER Option 17 7 XUSTAT Option 3 21 3 28 XUTESTUSER Option 7 9 XUTIO Menu 15 2 15 12 XUTL Global 7 12 7 13 7 14 7 20 15 10 Display Nodes 7 17 Jump Nodes 7 19 Structure and Function 7 16 User Stacks 7 16 XUTL XQ J T Node 7 16 XUTL XQ J XQM Node 7 16 XUTLOOPBACK Option 15 12 XUTM BACKGROUND PRINT Option 22 18 XUTM BACKGROUND RECOMMENDED Option TaskMan 22 18 XUTM CHECK ENV Option 22 13 XUTM CLEAN Option 22 17 XUTM DEL Option 20 8 22 6 XUTM DQ Option 20 8 22 4 22 5 22 33 XUTM ERROR DELETE Option 22 26 XUTM ERROR LOG CLEAN RANGE Option 22 25 XUTM ERROR Menu 13 2 22 24 XUTM ERROR PURGE TYPE Option 22 26 XUTM ERROR SCREEN ADD Option 13 3 XUTM ERROR SCREEN EDIT Option 13 3 XUTM ERROR SCREEN LIST Option 13 3 XUTM ERROR SCREEN
265. XUSERINT an option specially designed for this purpose Figure 3 1 Introductory text edit option SYSTEMS MANAGER MENU EVE Operations Management XUSITEMGR Introductory text edit XUSERINT July 1995 Kernel Systems Management Guide 3 1 Revised June 2008 Version 8 0 Signon Security System Management Parameters Checked during Signon Various parameters are checked as an initial step in the signon process The KERNEL SYSTEM PARAMETERS file 8989 3 stores the default values for most of the parameters Values for critical fields should be defined by IRM when Kernel is installed The values in the KERNEL SYSTEM PARAMETERS file 8989 3 can be edited any time though with the Enter Edit Kernel Site Parameters option XUSITEPARM Figure 3 2 Enter Edit Kernel Site Parameters option SYSTEMS MANAGER MENU EVE Operations Management XUSITEMGR Kernel Management Menu XUKERNEL Enter Edit Kernel Site Parameters XUSITEPARM Figure 3 3 Enter Edit Kernel Site Parameters option ScreenMan form Kernel Site Parameter edit DOMAIN FO OAKLAND MED VA GOV DEFAULT OF ATTEMPTS 5 AGENCY CODE DEFAULT LOCK OUT TIME 600 DEFAULT MULTIPLE SIGN ON Only one MULTIPLE SIGN ON LIMIT DEFAULT AUTO MENU YES DEFAULT AUTO SIGN ON DEFAULT LANGUAGE DEFAULT TYPE AHEAD YES DEFAULT TIMED READ SECONDS 999 BROKER TIMEOUT 180 BYPASS DEVICE LOCK OUT YES ASK DEVICE TYPE AT SIGN ON NO LIFETI
266. XUTM and located on the Taskman Error Log menu XUTM ERROR located under the Taskman Management Utilities menu XUTM UTIL located under the Taskman Management menu XUTM MGR which are all located under the Systems Manager Menu EVE 13 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Error Processing List Error Screens Figure 13 1 List Error Screens option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR List Error Screens XUTM ERROR SCREEN LIST The List Error Screens option XUTM ERROR SCREEN LIST lists in a simple table the screens you have established and the number of errors that have been screened out by each Add Error Screens Option Figure 13 2 Add Error Screens option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Add Error Screens XUTM ERROR SCREEN ADD With the Add Error Screens option XUTM ERROR SCREEN ADD you can enter a screen and specify whether the errors should be counted If there are already similar screens in place e g entering SYN when SYNTAX is already established you will be so informed shown the similar screens and prompted for confirmation before being asked about the count Entering two question marks at the Enter Screen To Apply pro
267. YES all incoming options and protocols are disabled You are also prompted to add to or delete from the list of options and protocols to disable However KIDS does not disable options and protocols which have an Action of USE AS LINK FOR MENU ITEMS All scheduled options on the system are also disabled Finally you are asked a time period for installation Delay Install Minutes 0 60 O You can delay before starting the installation after disabling options and protocols from 0 to 60 minutes This is to allow users already in disabled options time to exit the options before the installation starts Scheduling Installations The final question you are asked when using the Install Package s option to load software is upon what device to run the installation Your choices at the DEVICE prompt are e Run the installation directly by selecting a device without queueing The installation runs immediately on the device you specify e Queue the installation e Abort the installation of the distribution by entering a caret 23 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations When the Installation is Queued If you queued the installation you can look up the installation task in TaskMan A KIDS installation task looks like Figure 23 11 Queued KIDS installation Sample installation task You can cancel a queued installation before it has started b
268. ZTSK Global 20 2 20 5 21 8 21 11 22 2 22 17 22 30 22 32 ZTSK task 0 Node 20 7 ZTSK task 3 Node 20 7 ZTSTOP Variable 22 33 ZU Routine 3 8 Index 48 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Index ZUA 3 05 Global 3 29 July 1995 Kernel Systems Management Guide Index 49 Revised June 2008 Version 8 0 Index Index 50 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008
269. a clean way to stop the Manager from within the menu system This option also asks if you want the Submanagers to shut down when they finish what they are doing NOTE The WAIT state takes precedence While the Manager is in a WAIT state not even XUTM STOP affects it until after you invoke XUTM RUN to release it from the WAIT state after it is released it shuts down This option should always be used to shut down TaskMan rather than simply KILLing the TaskMan process which can leave the TaskMan globals in an improper state and even lose tasks SYNC flag file control Option Figure 22 19 SYNC flag file control option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUIM UTIL SYNC flag rile control XUTM SYNC With the SYNC flag file control option XUTM SYNC for any SYNC FLAG entry you can remove it from the file and delete all waiting tasks with the same SYNC FLAG You can also choose START NEXT which resumes running the series of tasks associated with that SYNC FLAG This is useful when one task in a series of tasks that is synchronized with SYNC FLAG fails 22 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Clean Task File Option The TASKS file 14 4 grows every time a new task is queued While the SAC requires applications to delete their tasks entries when they complete it is possible t
270. a number of NEW PERSON file 200 field values that you can edit with the Edit User Characteristics option e INITIAL You can enter your initials which can serve as an alternate way for users to specify your account e g when sending mail to you e NICK NAME You can enter a nick name which can serve as an alternate way for users to specify your account e g when sending mail to you e Telephone Contact Information You can enter phone numbers in the following fields PHONE HOME OFFICE PHONE VOICE PAGER DIGITAL PAGER e ASK DEVICE TYPE AT SIGN ON This field controls whether Kernel should determine what kind of terminal you are using when you sign on If this is set to DON T ASK Kernel assumes you are using the same kind of terminal you used the last time you signed on This can cause July 1995 Kernel Systems Management Guide 2 9 Revised June 2008 Version 8 0 Signon Security User Interface problems if you are using a different kind of terminal screen displays may not work properly so this should normally be set to ASK AUTO MENU The setting of AUTO MENU determines whether in the menu system a list of items on the current menu is displayed with the menu prompt Beginning users should usually set AUTO MENU to YES so that they can see menu items for each menu Experienced users who are familiar with their menus may prefer to set this field to NO which makes menu displays speedier since individual items
271. a terminology based on that of DSM 11 that includes the following terms Table 20 1 TaskMan system configuration terminology UCI User Class Identifier This is roughly equivalent to a directory or an account A UCI refers to the environment limited to a particular set of routines and globals In Cache terms this is a namespace Manager UCI Roughly equivalent to a system UCI or a library UCI This is where the vendor s system management routines are kept and where all namespaced routines and globals reside Currently all Kernel routines and globals are mapped back to the production account Volume Set On current systems we just set this to the string ROU This is the critical definition since this is what affects how TaskMan starts background jobs CPU Also known as a node or computer this designates a source of computing power and partitions It is used both for controlling TaskMan s behavior with parameters and for sending tasks to specific CPUs Mounted Volume Set Obsolete no longer used The TaskMan chapters that follow make use of this terminology TaskMan Security Key The TaskMan module comes with one security key ZTMQ The ZTMQ security key does not completely lock any options Instead it affects the behavior of the following three options e Dequeue Tasks XUTM DQ e Requeue Tasks XUTM REQ e Delete Tasks XUTM DEL Those who use these options without holding this security key can manipu
272. aaaadtent aGeaaes 4 2 PIC ACCESS S CCU eaae E E O sues tasectch Sn eet ech taaeois 5 1 User Imer ICO ira ahatepobadcvemsi aula boscactanet abewbmotedvarn aenleboocactentemeatecccatonete 5 1 Sy Ste Mie Manase meN cc caraacwaseucciaetnagaceaatescughaonsacieasleestee Waspacuaadescagh dascoducaseuediotaggeamiatnbaphanccadacaiaus 5 3 Whenis File Access security Checked isisisi i S 5 3 What in VA FileMan is Still Protected by the File Manager Access Code 00 5 4 Purpose tor Gratitine Pile ACCESS eonenni E E ENA 5 4 Who Needs Pe ACCOSS o mataa r E msg eemne een 5 4 levels ot IE ACOS SCC CUNY eir E a 5 5 Adit ACCESS 10 RIES aa a a eestadevaaedeleDaeees 5 8 Howto Grant Pile ACCESS eai O EA 5 8 Usine the File Access POIs eisirean a aa 5 9 Running the File Access Security Conversion eessssssseeeressssssecerrssssssscerressssssssecerressssseeeee 5 10 NON AVILA OS casas asen se aaalerases ner poseacdsasuctaanteo seca Jesu caee Govmad ac uad sas geueaneedsaresundecaadeorsded sanieuaecnaee 5 10 Advance Preparation for the Conversion cerniere e e a Eai 5 10 X Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Contents Summary of How the File Access Security Conversion Works ccccccccsssssssseeeeeeeeeees 5 12 File Access Security Conversion IMnstructions cccccccccsssesssseccccceceeeesssecccceesaeessseess 5 13 Atere CON VC Oeser an ARA O A A 5 15 Th Menu Wanater iinic aa II 1 6 Me
273. add a new number gt 0 LAYGO lt value gt record to the file Examples of the VA FileMan options that this property controls are as follows e Enter or Edit File Entries DIEDIT NOTE You must have LAYGO and WRITE access to a file to add new entries In addition you must have WRITE access at the field level for all required identifier fields READ RD The READ security property controls who ADIC lt file number gt 0 RD lt value gt has access to read data contained within a file Examples of the VA FileMan options that this property controls are as follows Print File Entries DIPRINT search File Entries DISEARCH DELETE DEL Inquire to File Entries DIINQUIRE Statistics DISTATISTICS List File Attributes DILIST Transfer Entries DITRANSFER To transfer text the user needs READ access to the file from which 5 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security Access Security Property Description Property Location Classic VA FileMan text is being transferred Similarly WRITE access is needed for the file to which entries are being transferred with this option Transfer File Entries transfer to file NOTE READ access is also required to use some of the Filegram and Audit options The WRITE security property controls who DIC lt file number gt 0 WR lt value gt can alter data in an existing record that
274. ade available online in Microsoft Word format and in Adobe Acrobat Portable Document Format PDF The PDF documents must be read using the Adobe Acrobat Reader 1 e ACROREAD EXE which is freely distributed by Adobe Systems Incorporated at the following Web address http www adobe com VistA documentation can be downloaded from the VHA Software Document Library VDL Web site http www va gov vdl VistA documentation and software can also be downloaded from the Enterprise Product Support EPS anonymous directories e Preferred Method download vista med va gov This method transmits the files from the first available FTP server e Albany OIFO ftp fo albany med va gov e Hines OIFO ftp fo hines med va gov e Salt Lake City OIFO _ ftp fo slc med va gov DISCLAIMER The appearance of external hyperlink references in this manual does not constitute endorsement by the Department of Veterans Affairs VA of this Web site or the information products or services contained therein The VA does not exercise any editorial control over the information you may find at these locations Such links are provided and are consistent with the stated purpose of this VA Intranet Service July 1995 Kernel Systems Management Guide XXXVI Revised June 2008 Version 8 0 Orientation XXXVI Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Introduction This manual provides descriptive information about Kernel for use by Informat
275. ager s influence spans all of those UCIs When the environment spans Volume Sets ZTSCH and ZTSK are translated across the Volume Sets included They are never replicated because TaskMan updates them so frequently The ZTSK global is mostly defined by VA FileMan beginning with Kernel V 8 0 but the ZTSCH is not Historically these globals were not VA FileMan compatible Now the inquire search and print capabilities of VA FileMan can be used to study the TASKS file 14 4 At present all edit access to these globals is restricted to the TaskMan options that edit the tasks in various ways REF For a description of the structure of ZTSCH and ZTSK please refer to the Troubleshooting topic in the TaskMan System Management Operation chapter in this manual July 1995 Kernel Systems Management Guide 20 5 Revised June 2008 Version 8 0 TaskMan System Management Overview SCHEDULE File The SCHEDULE file holds all of the lists and nodes that TaskMan uses to manage itself and to schedule tasks Some of these lists are e Schedule List or Time Queue e Waiting List or IO Queue e Job List e Compute Server Job List or C List e Link List e Status List e Run Node e Taskman Error Log e Error Screens The SCHEDULE file s function is split between identifying the status of active tasks and of TaskMan itself REF For more information on these lists please refer to the TaskMan System Management Operation
276. all be required to clear a locked account Where around the clock system administration service is not available accounts shall remained locked out for at least ten minutes NOTE These rules are taken from the VA Account and Password Management Interim Policy document All of these restrictions are enforced whenever Access or Verify codes are created or changed These changes were made to meet VHA DIRECTIVE 6210 available at the following Web address http vawwl va gov vhapublications ViewPublication asp pub_ID 54 REF For more tips and general advice regarding Access and Verify codes and security in general please refer to the Kernel Security Tools Manual Why Longer Passwords Passwords used to access VA systems must be at least 8 characters long because longer passwords are stronger and thus harder to guess than shorter ones The more tries it takes a hacker or a program to guess a password the more secure the system is Adding just one character to the length of a password greatly increases the difficulty of guessing the password For an 8 character password made up of letters and numbers assuming you can repeat characters and that there are no restrictions such as requiring the first character to be a letter there are 36 possibilities for the first position 36 possibilities for the second position 36 possibilities for the third position and so on Thus there are 36 x 36 x 36 x 36 x 36 x 36 x 36 x 36 2 821 109
277. allation questions for the first transport global a ge The installer repeats Steps 2 5 for the remaining transport globals if there are any more transport globals to process July 1995 Kernel Systems Management Guide 23 7 Revised June 2008 Version 8 0 KIDS System Management Installations 7 The installer chooses a device for the installation to run on The installer can queue the installation or run it directly entering a caret aborts the installation Phase 3 KIDS Installation of Software l Por P a ae KIDS disables any options and protocols the site has asked to be disabled for this install However KIDS does not disable options and protocols which have an Action of USE AS LINK FOR MENU ITEMS KIDS waits for the time period from 0 to 60 minutes the site specifies if they chose to disable options and protocols KIDS suspends the running of queued options by TaskMan for this install if the site chooses to do so The pre install routine is run for the first transport global All components are installed for the first transport global The post install routine is run for the first transport global KIDS repeats Steps 4 6 for any remaining transport globals to install in the distribution Options and protocols that were disabled for this install Gf any are re enabled Queued options are removed from suspense if the site chose to suspend queued options Installation Menu The KIDS Installation Menu
278. am Interfaces APIs are documented in the XGF Function Library Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml 29 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Glossary ALPHA TESTING AUTO MENU BETA TESTING CAPACITY MANAGEMENT CHECKSUM CIPHER COMMON MENU COMPILED MENU SYSTEM AXUTL GLOBAL COMPUTED FIELD DEVICE HANDLER DIFROM July 1995 Revised June 2008 In VA terminology Alpha testing is when a VistA test software application is running in a site s account An indication to Menu Manager that the current user s menu items should be displayed automatically When AUTO MENU is not in effect the user must enter a question mark at the menu s select prompt to see the list of menu items In VA terminology Beta testing is when a VistA test software application is running in a Production account The process of assessing a system s capacity and evaluating its efficiency relative to workload in an attempt to optimize system performance Kernel provides several utilities A numeric value that is the result of a mathematical computation involving the characters of a routine or file A system that arbitrarily represents each character as one or more other characters See also ENCRYPTION Options that are available to al
279. anagement options must be separately assigned they are not a part of the Delegate s Menu Management menu XQSMD USER MENU Delegation Level Options and Keys DELEGATION LEVEL is a field in the NEW PERSON file 200 specifying the number of steps that a person is from the original delegation of options by the Site Manager whose Delegation Level is 0 Starting with Kernel V 8 0 the delegation level is also maintained for DELEGATED KEYS For instance if the Site Manager delegates all laboratory options to the Lab ADP Application Coordinator ADPAC then the Lab ADPAC would have a Delegation Level of 1 Should the Lab ADPAC further delegate a set of those options to the Chief of Chemistry the Chief would have a level of 2 and so on The use of levels insures that supervision is not compromised such that the lower level user could alter menus or remove security keys of the higher level person No attempt is made to determine who actually works for whom since that information is not available to the software Delegation chains should therefore be constructed with some care To modify the set of options and accompanying security keys delegated to a particular person you must have a Delegation Level equal to or less than the person you are trying to modify If you create a new delegate by delegating some or all of the options delegated to you that person will have a Delegation Level equal to your level 1 It may be necessary to modif
280. anager opens the device making it unavailable July 1995 Kernel Systems Management Guide 22 9 Revised June 2008 Version 8 0 TaskMan System Management Operation Understanding how the IO List works can make this particular check very useful Submanagers handle the Device IO Lists Unusual behavior in these lists usually points to device or Submanager problems There are three fundamental things to look for with this check e When a device becomes available The Submanagers should notice and start a task running on that device If the Submanagers do not do this it is probably time to start looking for problems with the Submanagers e When a device is allocated A Submanager should quickly make it unavailable If this fails to occur the Submanagers may be having problems There can be extenuating circumstances e g the system being very slow that explain these occurrences e When many tasks are backed up waiting for the same device Sometimes it is just because that device is busy However sometimes the device is off line or out of paper Job List The Job List is where tasks wait for partitions so if many tasks are backed up here you know the Submanagers are not picking them up This can be caused by any of the following e A slow system e TaskMan reaching its job limit e TaskMan assigning tasks a priority that is too low for them to run Systems that are too busy will back up in this list not the Schedule List The Co
281. and and agree to fulfill the provisions of this User Access notice The name of the user and location is displayed here Signature ACCESS REQUEST Superstar VAMC RETURN THIS FORM TO IRMS NEW ACCTS XXX XXX 3 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management VA FileMan word processing windows are used to retrieve the user s name service section and service section coordinator s name To be effective the SER VICE SECTION field in the NEW PERSON file 200 must be filled in for the new user The COORDINATOR IRM field a field in the SER VICE SECTION file 49 must also be filled in and updated when necessary Word processing windows are also used for formatting like TOPI to separate the two forms When using the File Access Security system READ access to the SERVICE SECTION file 49 is needed to retrieve the Coordinator s name within the window command REF For more information on using word processing windows the File Access Security system and navigation please refer to the VA FileMan Getting Started Manual The Reprint Access Agreement Letter option allows you to reprint the computer access agreement letter in case there was a problem printing the first form e g the first form is jammed in the printer It does not reprint the Access code on the letter however Editing an Existing User Option SYSTEMS MANAGER MEN
282. and restart Scroll when the user wishes to continue July 1995 Revised June 2008 Kernel Systems Management Guide Version 8 0 SECONDARY MENU OPTIONS SECURE MENU DELEGATION SMD SERVER OPTION SIGNON SECURITY SPECIAL QUEUEING SPOOLER SYNONYM TASKMAN TIMED READ UP ARROW JUMP XINDEX July 1995 Revised June 2008 Glossary Options assigned to individual users to tailor their menu choices If a user needs a few options in addition to those available on the primary menu the options can be assigned as secondary options To facilitate menu jumping secondary menus should be specific activities not elaborate and deep menu trees A controlled system whereby menus and security keys can be allocated by people other than IRM staff e g application coordinators who have been so authorized SMD is a part of Menu Manager An entry in the OPTION file 19 An automated mail protocol that is activated by sending a message to the server with the S server syntax A server option s activity is specified in the OPTION file 19 and can be the running of a routine or the placement of data into a file The Kernel module that regulates access to the menu system It performs a number of checks to determine whether access can be permitted at a particular time A log of signons is maintained An option attribute indicating that TaskMan should automatically run the option whenever the system reboots An entry in the
283. andard distributions is used to only export globals You still use the Load a Distribution option to install global distributions Unlike loading a standard distribution however KIDS installs global distributions immediately from the Load a Distribution option Also there is no queueing of the installation A global distribution can only contain one transport global and the transport global can only export globals You know that the distribution you re installing is a global distribution rather than a standard distribution because when you load it with the Load a Distribution option KIDS will indicate the following Figure 23 14 KIDS Global distribution Sample message The Load a Distribution option lists each global that will be installed from the distribution Each global in the list is marked OVERWRITE or REPLACE e OVERWRITE Load the global without purging the site s version of the global beforehand e REPLACE Purge the site s version of the global first and then load the global You are given two chances to abort the installation of the global distribution If you answer YES to both questions the globals in the global distribution are installed immediately Purging the BUILD and INSTALL Files Each KIDS installation adds one entry to the BUILD 9 6 and INSTALL 9 7 files for every transport global installed from the distribution REF For information about purging these files please refer to the discussion of the
284. ange their Verify codes at periodic intervals IRM should set the LIFETIME OF VERIFY CODE parameter in the KERNEL SYSTEM PARAMETERS file 8989 3 to a certain number of days The maximum number is 90 days and the minimum number is day Thus sites can choose any number from 1 90 days before requiring users to change their Verify code At the end of that period e g every 90 days users must then change their Verify codes Signon Security checks whether the Verify code needs to be changed and if so prompts the user at signon to enter a new Verify code AUTO GENERATE ACCESS CODES When assigning Access codes the security officer or IRM staff can invent an alphanumeric string or can ask Kernel to generate one If the AUTO GENERATE ACCESS CODES site parameter in the KERNEL SYSTEM PARAMETERS file 8989 3 is set to YES only generated cryptic codes can be assigned It is not necessary to pick the first one presented others can be generated for selection DEFAULT INSTITUTION and AGENCY The institution running Kernel software is defined during the Kernel installation when prompted for the DEFAULT INSTITUTION in the KERNEL SYSTEM PARAMETERS file 8989 3 This field is a pointer to the INSTITUTION file 4 One or more institutional affiliations can also be associated with a user e g a VA Outpatient Clinic and an Army Medical Center This data is stored in the DIVISION field Multiple in the NEW PERSON file 200 If a user 1s associated with
285. as been reached the signon attempt will fail If the current device is tied to a routine as specified in the TIED ROUTINE field of the DEVICE file 3 5 that routine is executed and the session is halted If not the user is prompted for Access and Verify codes After a successful signon attributes for that user are then retrieved from the NEW PERSON file 200 Signon Security then sends the user to Menu Manager If a primary menu is associated with the device PRIMARY MENU OPTION field in the DEVICE file 3 5 that menu is presented Otherwise the user s primary menu is presented If the user does not have a primary menu the PRIMARY MENU OPTION field in the NEW PERSON file 200 is NULL the session is halted The signon flow chart in this topic see Figure 3 4 illustrates the procedural steps taken by Kernel s Signon Security system to determine whether to permit signons and if so how to create an appropriate computing environment Typically after site parameters and device characteristics are checked the user is prompted for Access and Verify codes user attributes are collected and a primary menu prompt is presented Introductory Text Before gathering system parameters or prompting for Access and Verify codes Signon Security displays contents of the INTRO TEXT field in the KERNEL SYSTEM PARAMETERS file 8989 3 The text can be edited with the Enter Edit Kernel Site Parameters option or with the Introductory text edit option
286. askMan makes sure all tasks that need this device start on the designated Volume Set TYPE Any tasks that must wait for HFS or SPL type devices are rescheduled for ten minutes in the future instead of being placed in a list of waiting tasks This is because these lists are checked through repeated opens which may contaminate the output of these two special types of devices PRIORITY AT RUN TIME The PRIORITY AT RUN TIME field overrides the default priority that system managers can establish for tasks using the Site Parameters Edit option on the Edit TaskMan Parameters menu TASKMAN PRINT A HEADER PAGE If the TASKMAN PRINT A HEADER PAGE field is set to YES for the device being opened by the Submanager a header page is printed The header page distributed with TaskMan is very simple and system managers can substitute their own locally written header pages To do this you must rename your header page routine as ZTMSH the name of the one distributed with TaskMan Whenever you install new versions of Kernel it overwrites ZTMSH with the default copy so you should maintain your local version by doing the following e Keep your local header page routine saved somewhere under a local name e After each Kernel install re save the locally named copy as ZTMSH July 1995 Kernel Systems Management Guide 21 13 Revised June 2008 Version 8 0 TaskMan System Management Configuration The following example shows an alternative to th
287. ations This tool is primarily intended for application developers to use in monitoring the testing process at local test sites NOTE In VA terminology Alpha and Beta testing are defined as follows e Alpha Testing VistA test software application is running in a site s Test account e Beta Testing VistA test software application is running in a site s Production account Alpha Beta Tracking provides the following services to both developers and IRM personnel e Notification when a new alpha or beta software version is installed at a site e Periodic option usage reports for alpha or beta options being tracked e Periodic listings of errors in the software s namespace that are currently in alpha or beta test at the site The following options are provided on the Alpha Beta Test Option Usage Menu XQAB MENU which is located on the Operations Management menu XUSITEMGR These options allow developers and IRM personnel to monitor Alpha Beta Tracking at a site e Errors Logged in Alpha Beta Test QUEUED option XQAB ERROR LOG XMIT e Actual Usage of Alpha Beta Test Options option XQAB ACTUAL OPTION USAGE e Low Usage of Alpha Beta Test Options option XQAB LIST LOW USAGE OPTS e Print Alpha Beta Errors Date Site Num Rou Err option XQAB ERR DATE SITE NUM ROU ERR e Send Alpha Beta Usage to Programmers option XQAB AUTO SEND i REF For more detailed information about and description of the Alpha Beta Tracking functionali
288. aus or TaS Ksenia e a dlaadiasenannsens saaeaeuassedeveeds 19 4 SOPPA TI KS sacmnck santa aceiuseeace sande ans uesenet cae tace ma tiase sang scaeduasnnnecanssaeaseneeaceennes 19 4 PC PAG RG Sree Sant lene nnt a id ennt net GeuutiedteostestGaactian T setantaus 19 5 PtSi arid Pata PASTS n A tl eusmbod tasaseciedeatibenoatne 19 5 ELC CUINS ANONSE TaS K nine ttrastcet ccna antnatl a ran detiar mel 19 6 20 TaskMan System Management Overview ccccccccccccccccceceeaeeeeeeeeeeeeeeeeeeceeceeeeeeeeeeeaaqaeas 20 1 PAS KIVA SGV IS POMsO AON sieatoe fee ceuts Seteaihineceat iraheas neces nena nace aaa caer ean 20 1 CC IST sessed sere ts tan talc uses edn ena lo einen eons as a Salon ae eens 20 1 IVT AC Eas sce Sagecris tants ccmsg encanta snee E eae 20 2 SUDMIANG GELS sa cias Si cacecoesn coterie ats Renee entero waco ned ntco scan hein co eee ceo eeneees 20 3 MAGNUS SE LNCS ashe sc ariapicee natntnct a r e r 20 5 PaskMan Globals 7oZ ISCH and WZ ISK oeiee E EE 20 5 SCHEDULE clic mee etme TAE mene E E OR en Mere are Mere Serer 20 6 TASKS PIEGA A eaa a a tals ceaasessearasboscueneee 20 7 OMOT EC oa a res tee ere Ser rere tenn Ce eee Tee CECT et er ert Tae ate ene 20 7 System Conieuration Terminalo y sreske a a 20 7 TERMIN SEC R Vna E a E A 20 8 21 TaskMan System Management Configuration cccccccccccccsssssssseseseseeeececeeeeeeeeeeaaaaeeeeeeees 21 1 Definme TaskMan Environments oseraies E A E aadi 21 1 Cono ime Task Mian e
289. authorized sender of any mail groups e Revokes the user s status as a surrogate e Revokes the user s status as a Secure Menu Delegation delegate e Deletes the user s Access code Verify code Electronic Signature code VA FileMan Access code 1 e FILE MANAGER ACCESS CODE field 3 and Programmer Access code e Deletes the user s menu templates 3 24 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management e Deletes the user s delegated options e Purges the DISV global on that CPU for that user You can also decide whether all mail messages and all security keys for the account will be deleted on the TERMINATION DATE with the final two fields in the Deactivate a User option XUSERDEACT DELETE ALL MAIL ACCESS and DELETE KEYS AT TERMINATION If the user is expected to return to the facility and will need to have the user account reopened security keys and mail could be retained REF For more information on cleaning up user access and privileges at termination please refer to the XU USER TERMINATE Option topic in the Signon Security Developer Tools chapter in the Kernel Developer s Guide DELETE ALL MAIL ACCESS Setting the DELETE ALL MAIL ACCESS field causes all mail messages for the user to be deleted when their account is terminated on the TERMINATION DATE DELETE KEYS AT TERMINATION Setting the DELETE KEYS AT TERMINATION field causes all security keys for t
290. ave access to a user s entire secondary menu instead only those options on the secondary menu that are also delegated to you 9 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Secure Menu Delegation If when you edit a user s secondary menu you choose an option that is already on a user s secondary menu you are asked if you want to delete it from their secondary menu Otherwise you are asked if you want to add the option to their secondary menu If you are assigning an option that is locked with a security key the delegation process checks whether you have been delegated the key as well If you have the key is automatically assigned to the user along with the option If you have not been delegated the key you get an error message saying that you have not been delegated the needed security key the option is assigned to the user but they will not have the key to unlock the option If you delete an option that is locked with a security key and that key is delegated to you and you are at a higher key delegation level than the option holder the key is deleted along with the option unless the user holds another option locked by the same security key Example In this example the menu option LRZ MAIN is added to the user s secondary menu LRZ MAIN is locked with a security key and that key is automatically assigned when the option is assigned Figure 9 2 Edit a User s Options Sample user dialogue Sele
291. ay be also returned For example if you want diagnostic information about a server option named ZZSERVER and the option resides on the system at the Oakland OIFO you should create a message containing the text ZZSERVER and send it to Se XOSCHRELSC SFE5VA CGOV 11 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Server Options The XQSCHK server option at Oakland will unload the name of the server option in this example ZZSERVER see Figure 11 2 Assuming such a server option exists you would expect to receive a reply in a MailMan message as shown below Figure 11 2 XQSCHK server option Sample MailMan return message MailMan message for KRNUSER ONE COMPUTER SPECIALIST Subj Server Request Reply from SF ISC VA GOV From Postmaster in IN basket NOVa Zop L992 22455 PM Sender KRNUSER ONE Option name ZZSERVER Subject TESTING XQSCHK Message 999 This is a reply from ISC SF VA GOV Checking Server Option ZZSERVER Fields 220 to 225 in the Option File 220 No bulletin selected will use default XQOSERVER CAR The server action code is Run Immediately 222 The mail group ZZGROUP is pointed to 223 Auditing is turned off 224 The server s bulletin is not suppressed Leo Reply mail is sent when an error is trapped July 1995 Kernel Systems Management Guide 11 7 Revised June 2008 Version 8 0 Server Options Errors and Warnings from the XQSCHK Server Option The following table lis
292. ber IEN is used That is what becomes the value of DUZ Some users have low numbers while others have high ones This simply indicates the order their names were entered into the NEW PERSON file 200 Users with low numbers are often people who began using the system some years ago while users with high numbers tend to be recent entries in the file Using Ranges of File Numbers Can files be specified by number ranges Yes it is useful to do this when granting several files at once First find out the number of the files Typing a question mark at the to Files prompt will display the number and name of the files Note the numbers and then put them together on one line You can use dashes to indicate a consecutive range and commas to separate the single numbers and dashed groups as follows 2 3 4 6 7 8 125 236 799 July 1995 Kernel Systems Management Guide 5 9 Revised June 2008 Version 8 0 File Access Security OR 2 4 6 8 125 236 799 File numbers are also used when printing a group of consecutive files The prompt asks for a place to start with a default file name presented To print just this one file respond to the next prompt by simply pressing the lt Enter gt key thereby accepting the default of ending after printing that one file To print a consecutive range of files the lowest number is entered as the starting point and the highest number as the ending point All files that fall in this range will be printed
293. ble device setting File 3 5 which will in turn override the site parameter default File 8989 3 Users can edit the setting with the Edit User Characteristics option TY PE AHEAD If TYPE AHEAD is disabled any keystrokes that the user enters while computer system processes previously issued instructions will not register If TYPE AHEAD is enabled keystrokes entered in advance of processing will be stored in the TYPE AHEAD buffer and will be interpreted when the earlier process is finished New users may experience unwanted results if TYPE AHEAD is enabled and they had not anticipated the effect Experienced users may prefer TYPE AHEAD for efficiency The user setting overrides the device setting which in turn overrides the site parameter setting Users can edit the setting with the Edit User Characteristics option TIMED READ The value for the TIMED READ parameter is stored in the local variable DTIME and is used to calculate how long Kernel should wait before terminating a READ If for example a user does not respond to a menu prompt in the number of seconds defined by the TIMED READ Kernel will take steps towards signoff and without subsequent user response will halt the user session The user setting overrides the device setting which as usual will override the site default POST SIGN IN MESSAGE The POST SIGN IN MESSAGE is similar to introductory text 1 e INTRO TEXT field in File 8989 3 except that Kernel displays it only
294. bleshooting topic in this chapter Schedule List The Schedule List always shows the number of tasks currently scheduled to run and checks the times for which they are scheduled to determine whether any of them should already have started When many tasks are queued to run at the same time it is not unusual for the Manager to be a little late in sending off the last few When most of the tasks on the Schedule List are overdue however the Manager is probably having problems keeping up This is not a normal condition If the problem is not a recurring error or a difficult output device the most likely culprit is your default setup in the TASKMAN SITE PARAMETERS file 14 7 Another possible problem is that TaskMan is trapping many errors or trying to access a very slow link between Volume Sets If the problem is error trapping the Status List should regularly show the Manager in an Error state Also remember that if the machine is saturated all of the jobs on the system including the Manager will run slowly IO List The IO List first shows the last time H a Submanager checked the list and the last device checked The check generally shows how many tasks are waiting for each device in the IO List The occasional remark Allocated means that a Submanager has already noticed that the device is available and has allocated the device to a task using the Device Allocation List Devices should only be allocated for a short time before the Subm
295. bmenu on the Taskman Management menu called TaskMan Management Utilities menu XUTM UTIL provides several options to set up monitor and modify the TaskMan environment The Taskman Management Utilities menu contains the following options Monitor Taskman Check Taskman s Environment Edit Taskman Parameters Restart Task Manager Place Taskman in a WAIT State Remove Taskman from WAIT State Stop Task Manager Taskman Error Log Clean Task File SYNC flag file control These options are discussed in the topics that follow Monitor Taskman Option Figure 22 8 Monitor Taskman option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Monitor Taskman XUTM ZTMON The Monitor Taskman option XUTM ZTMON gives you a screen of information about the current state of TaskMan and offers you several ways to get more information The monitor focuses on the current state of the Manager itself and on the contents of the SCHEDULE file As you use this option you will acquire an intuitive understanding of how these lists should look and behave when your system is healthy Spending the time using this option to get that intuition will save you troubleshooting time by helping you to notice problems sooner July 1995 Kernel Systems Management Guide 22 7 Revised June 2008 Version 8 0 TaskMan System Management Operation RUN Node The first section of the Monitor
296. by a KIDS patch This option is under the July 1995 Kernel Systems Management Guide 23 15 Revised June 2008 Version 8 0 KIDS System Management Installations Installation menu of the KIDS menu It works on a patch that has been loaded on your system but not installed Running Installations Once you ve loaded the transport global s from a standard distribution you can install them Do this using the Install Package s option XPD INSTALL BUILD When you load a distribution KIDS tells you which transport global name to use to install the distribution e g Use PACKAGE 1 0 to install this Distribution This will always be the first transport global to successfully load from the distribution When you use the Install Package s option XPD INSTALL BUILD select the transport global name reported when you loaded the original distribution Once you ve done that you can answer the installation questions for each transport global in the distribution Processing Each Transport Global When you select a distribution to install the Install Package s option processes the installation questions for each transport global in the distribution For each transport global you re asked e Pre Install questions e Standard KIDS Questions e Post Install Questions e Whether to disable any options or protocols By typing three question marks at this prompt KIDS will list all of the options and protocols it will disable If you answer
297. ce all output from the installation is also stored in the INSTALL file 9 7 in the MESSAGES word processing type field The installation questions and your answers to them are stored in the INSTALL ANSWERS field Multiple of the INSTALL file 9 7 You can print entries from the INSTALL file 9 7 with the Install File Print option July 1995 Kernel Systems Management Guide 23 17 Revised June 2008 Version 8 0 KIDS System Management Installations Answering Installation Questions for a Distribution Figure 23 12 Answering installation questions for a distribution Flowchart Select a distribution to install by choosing INSTALL File entry for the first transport global in the distribution KIDS starts processing first transport global Answer pre install Answer Data Answer post install questions if Dictionary DD questions if Any more developer needs and Data question developer needs any transport any answers for if developer is answers for globals to pre install phase of exporting DDs or post install phase of process installation data installation Edit select set of options and protocols Yes to disable during install If you select anything to disable TaskMan will also be suspended from running scheduled options only during install Question Disable option and protocols Yes Select CPUs to install routines on Question Move routines to other CPUs No Queue j
298. cent alerts listed first Information only alerts are displayed with the letter I in front of the alert message When you process information only alerts all that happens is that they are removed from the pending alerts list Their only purpose was to send you the one line alert message When you process alerts that are not information only processing the alert may send you to a particular option or program Afterwards you are returned to the View Alerts screen if more alerts need processing or back to the menu prompt if no pending alerts remain July 1995 Kernel Systems Management Guide 10 1 Revised June 2008 Version 8 0 Alerts There are various methods for processing alerts from the View Alerts screen You can enter any of the following alert process codes listed alphabetically Table 10 1 Alert processing codes Process all alerts in the order shown Delete specific alerts Some alerts can not be deleted Only listed if one or more INFORMATION ONLY alerts have been listed If unable to delete an alert users will see Unable to delete alerts which require action n n n Forward one or more specific alerts Forwarding may be sent as an alert to a specific user s and or mail group s a mail message or sent to a specific printer Process all INFORMATION ONLY alerts Only listed if one or more INFORMATION ONLY alerts have been listed Add or remove a surrogate to receive alerts for you An optional start and end date
299. cessed The Manager looks for overdue tasks in the schedule list comparing the current time to the start time of the tasks listed If an overdue task is found the Manager removes it from the schedule list and inspects it If the task is defined with a complete task record the Manager places it in a list of tasks ready to run The Manager places a task on one of several different lists depending on whether the task needs ownership of a currently unavailable I O device As its final step in processing each overdue task the Manager checks the number of Submanagers available to process tasks and starts up new submanagers if needed The Manager uses the JOB command or SPAWN if the Manager is running in a DCL context on a Cach system The only variation on this scheme happens when the Manager finds a task bound for a different Volume Set Depending on the system configuration such tasks may need to be run by the Manager running on that other Volume Set In this case the current Volume Set s Manager copies the task over to the Volume Set on which the task should run and marks it as moved in the current TASKS file 14 4 In this 20 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Overview process the task is assigned a new task number and the Manager on that other Volume Set handles the task from there If during this process the Manager discovers that the link between the two Volume Sets
300. ciated processors CPUs in the local area network The global locations of the device related files are Table 15 1 Device related files global locations Device related File Name Global Location DEVICE 8 5 AMLIS 1 TERMINAL TYPE 3 2 ZIS 2 DA RETURN CODES 3 22 ZIS 3 22 The SUBTYPE field of the DEVICE file 3 5 points to the TERMINAL TYPE file 3 2 to retrieve a standard set of characteristics that have been defined for vendor devices e g Laser printers or VT320 CRTs July 1995 Kernel Systems Management Guide 15 1 Revised June 2008 Version 8 0 Device Handler System Management DEVICE File Fields DEVICE file 3 5 The most essential fields to populate or consider populating for DEVICE entries are e NAME e I e VOLUME SET CPU e TYPE e SUBTYPE The following two fields were introduced with Kernel V 8 0 e PRE OPEN EXECUTE e POST CLOSE EXECUTE The DEVICE file 3 5 has many more fields where additional specific information for particular devices can be entered Kernel provides a number of options to facilitate creating and editing device types on the Device Management menu XUTIO Figure 15 1 Device edit options Device Management XUTIO Device Edit XUDEV Edit Devices by Specific Types XUDEVEDIT ALL Edit All Device Fields XUDEVEDITALL CHAN Network Channel Device Edit XUDEVEDITCHAN HFS Host File Server Device Edit XUDEVEDITHFS LPD LPD VMS Device Edit XUDEV
301. cifications are used as the I value Figure 17 16 Spool Device for Cach and GT M SPOOL VALS SPOOLER SPOOL P OTHER Spool Device Edit Option The Spool Device Edit option XUDEVEDITSPL lets you edit Spool device attributes using a ScreenMan form Figure 17 17 Spool Device Edit option Device Management XUTIO Edit Devices by Specific Types XUDEVEDIT Spool Device Edit XUDEVEDITSPL NOTE The type of data entered in the I and OPEN PARAMETERS fields depends on the type of M system you are using and the mode of access REF For further details please refer to your M system manuals REF Examples are provided in the Defining Spool Device Types topic Auto despooling For convenience spool devices can be defined to ensure that despooling takes place automatically without user interaction If the AUTO DESPOOL flag is set one copy of the spooled output is sent to each device named in the DESPOOL DEVICES field Multiple Having the output automatically July 1995 Kernel Systems Management Guide 17 9 Revised June 2008 Version 8 0 Spooling despooled saves users the time and trouble of logging on and printing a spool document that may have been created the previous evening Documents are not deleted upon despooling they remain available to the user for subsequent printing Figure 17 18 Device Edit option Sample user dialogue Select Device Handler Option Device Edit Select DEVICE N
302. cify Allowable New Menu Prefix Option 9 5 9 11 Specifying Right Margin and Page Length 14 2 Special Subtype 14 4 SPOOL DATA File 3 519 17 6 Spool Device Edit Option 17 9 SPOOL DOCUMENT File 3 51 14 6 15 9 17 6 17 10 Spool Documents Making into Mail Messages 3 22 Name 14 6 15 9 17 2 17 10 Name An Exception 14 6 Spool Management Menu 17 7 SPOOLER Device 17 1 Spooler Menu 17 3 Spooler Site Parameters Edit Option 17 8 Spooling 17 1 Attributes 17 1 Auto despooling 17 9 Document Name Prompt 17 2 Document Names Generated 17 10 Kernel Systems Management Guide Index 37 Version 8 0 Index Generating Names 17 10 Granting Privileges 17 7 Making Into Mail Messages 17 4 Managing Spool Documents 17 7 Printing spool documents 17 4 Privileges 3 22 Privileges 17 1 Privileges 17 1 Privileges 17 6 Privileges 17 7 Purge old Spool documents Option 17 8 Retrieving Spool Documents 17 3 Sending Output to the Spooler 17 1 Spool Device Edit Option 17 9 Spool Device Types 17 9 Spool Document Name 14 6 15 9 Spool Document Storage 17 6 Overflowing 17 6 Spool Management Menu 17 7 Spooler Menu 17 3 Storage Overflows 17 6 System Defaults 17 8 User Interface 17 1 Viewing spool documents 17 4 SSN Field PATIENT File 2 5 8 SSN Field 9 NEW PERSON File 200 3 9 3 18 STACK Variable 13 4 Standard Device Chart Multi Term Look Up MTLU 25 4 Standard Distributions 23 6 23 7 START
303. cribed below This option can be run either directly or as a queued job You can specify a retention period other than the 14 day default when you queue the option only by using the TASK PARAMETERS field of the 10 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Alerts OPTION SCHEDULING file 19 2 If you put a numeric value in the TASK PARAMETERS field this value replaces the default alert retention value of 14 days The Delete Old gt 14 d Alerts option also purges the ALERT TRACKING file 8992 1 It purges all entries in the ALERT TRACKING file 8992 1 that are more than 30 days old The only exception is 1f when an alert is created the call to create the alert specified a retention period different than 30 days in this case the different period is used Finally this option forwards unprocessed alerts to supervisors and surrogates if this was requested when the alert was created However if the period to wait before forwarding exceeds the purging retention period used by this option the alerts will be purged rather than forwarded Due to the number of tasks performed by this option it should be queued through TaskMan on a regular basis The suggested scheduling frequency is once every day Make an Alert on the Fly Option The Make an Alert on the Fly option XQALERT MAKE allows you to generate an alert on the fly It interactively asks you for the alert message recipients and alert action if
304. ct Delegate s Menu Management Option Edit a User s Options Select NEW PERSON NAME KRNUSER FIVE PRIMARY MENU OPTION XMUSER lt Enter gt MailMan Menu No keys needed to delete No keys needed to give SECONDARY MENU OPTION LRZ MAIN lt Enter gt Lab User Menu ZZURMAIN key also given SECONDARY MENU OPTION lt Enter gt Select NEW PERSON NAME Unlike secondary menus you are only able to edit a user s PRIMARY MENU OPTION if their current primary menu is an option that has been delegated to you Otherwise you are not allowed to change that user s PRIMARY MENU OPTION NOTE You cannot add or subtract options on a user s primary menu you can only replace the user s entire PRIMARY MENU OPTION with another one July 1995 Kernel Systems Management Guide 9 3 Revised June 2008 Version 8 0 Secure Menu Delegation Build a New Menu Option Using the Build a New Menu option XQSMD BUILD MENU located on the Delegate s Menu Management menu XQSMD USER MENU you can create new menus with menu items chosen from your delegated options First you need to provide an option name for the new menu you are creating The menu option name must begin with a namespace assigned to you by IRM Once you provide a name for the menu you are asked e Text for the menu e Description for the menu e Items for the menu choose from your delegated options Once you have created a new menu you can assign it to your users just as 1f it were
305. ct Display Menus and Options Option Inquire Which OPTIONS item to display XT KERMIT MENU lt Enter gt Kermit menu NAME XI KERMIT MENU MENU TEXT Kermit menu TYPE menu CREATOR POSTMASTER PACKAGE KERNEL E ACTION PRESENT YES X ACTION PRESENT YES DESCRIP TION This is the top level menu for kermit functions It gives access to the send receive and edit options ITEM XT KERMIT RECEIVE SYNONYM R ITEM XT KERMIT SEND SYNONYM S ITEM XT KERMIT EDIT SYNONYM E EXIT ACTION D CLEAN XTKERM4 ENTRY ACTION D INIT XTKERM4 UPPERCASE MENU TEXT KERMIT MENU Option Access by User Option Figure 7 7 Option Access by User option Menu Management XUMAINT Show Users with Selected Primary Menu XUXREF 2 Option Access By User XUOPTWHO Use the Show Users with Selected Primary Menu option XUXREF 2 to show which users have been assigned a particular option as a primary or secondary menu The Option Access by User option XUOPTWHO is another cross referencing tool 7 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Managing Menus and Options Managing Primary Menus When IRM receives new software applications existing primary menus should be modified to include the new menus It is not wise to create a new primary menu for every new or unusual circumstance This would lead to a tremendous variety of menus that would be difficult to sort out and use
306. cut however it can also be associated with multiple terms and multiple keywords can be associated with the same term 25 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU The term SMOKER can be used as a synonym or keyword As a keyword one can associate it with a few specific diseases AS a Synonym properly selected tokens might result in a display of all smoking related diseases Recall that MALIG results in 447 matches If this were used as a shortcut to a single entry MTLU would display only that entry and the remaining 446 would never be displayed These files add some control over the behavior of certain lookups However developers should use extreme caution when placing entries in these files to ensure that results are predictable and appropriate for both users and other VistA software developers The decision to populate them for a given lookup file depends on whether or not a commonly used word or phrase results in any matches during a lookup If not it is a candidate The LOCAL KEYWORD 8984 1 LOCAL SHORTCUT 8984 2 and LOCAL SYNONYM 8984 3 files should only be populated with common words or phrases In the event that a search produces no matches MTLU continues with a standard FileMan search User Interface Multi Term Look Up Menu Options The following is a description of the Multi Term Lookup Main Menu XTLKUSER2 which can be selected from the Application Ut
307. d Select RELATED FRAME KEYWORD lt Enter gt Want to LOAD KEYWORDS Y N N Select INVOKED BY ROUTINE lt Enter gt Select EDITOR lt Enter gt Select OBJECT lt Enter gt ENTRY EXECUTE STATEMENT lt Enter gt EXIT EXECUTE STATEMENT lt Enter gt Select HELP FRAME NAME lt Enter gt Enter or Edit File Entries Print File Entries Search File Entries Modify File Attributes Inquire to File Entries Utility Functions Data Dictionary Utilities Transfer Entries Other Options Select VA FileMan Option ENTER OR EDIT FILE ENTRIES INPUT TO WHAT FILE HELP FRAME 8989 2 lt Enter gt KERNEL PARAMETERS 6 entries EDIT WHICH FIELD ALL lt Enter gt Select KERNEL PARAMETERS NAME XUSER COMPUTER ACCOUNT NAME XUSER COMPUTER ACCOUNT Replace lt Enter gt TYPE lt Enter gt DEFAULT lt Enter gt REPLACEMENT ISC COMPUTER ACCESS July 1995 Kernel Systems Management Guide 3 13 Revised June 2008 Version 8 0 Signon Security System Management Select KERNEL PARAMETERS NAME lt Enter gt Enter or Edit File Entries Print File Entries Search File Entries Modify File Attributes Inquire to File Entries Utility Functions Data Dictionary Utilities Transfer Entries Other Options Select VA FileMan Option lt Enter gt FM VA FileMan Core Applications Device Management Information Security Officer Menu Manage Mailman Menu Management Operations Management Programmer Options Spool Management Taskman
308. d 21 3 MODE OF TASKMAN Field 21 4 Standardized VA Cach and GT M Configuration 21 10 SUBMANAGER RETENTION TIME Field 21 3 21 4 TASK PARTITION SIZE Field 21 3 TASKMAN HANG BETWEEN NEW JOBS Field 21 4 TASKMAN JOB LIMIT Field 21 3 TaskMan User Option 19 2 19 3 19 4 22 33 Display Status of Tasks 19 4 Editing Tasks 19 5 Listing and Printing Tasks 19 5 Stopping Tasks 19 4 Summary 19 6 Tasks in the Task List 19 3 Working with Tasks 19 2 Tasks Editing 19 5 In the Task List 19 3 KILL 22 10 Waiting for a Volume Set 20 3 Waiting to Start on a Compute Server 20 6 TASKS File 14 4 19 4 20 1 20 2 20 3 20 5 20 7 21 1 21 2 21 4 22 2 22 3 22 4 22 6 22 17 22 19 22 24 22 25 22 27 22 29 22 30 22 31 22 34 22 36 July 1995 Revised June 2008 Index Tasks waiting for a device Option 22 4 TELNET PORT Field 66 15 7 Templates IRM Setup to Enable Building Options from Templates 9 5 LOGIN Menu 2 4 6 9 XUEDIT CHARACTERISTICS 3 23 Terminal Type Attributes 3 5 15 9 15 10 Entries 14 4 15 11 18 16 Identity 2 5 Information Retained by User 15 10 Naming Conventions 15 9 P BROWSER 18 3 Prompt 2 6 3 5 Query 2 5 2 6 Selection at Signon 15 11 Setup 3 5 3 23 Specifications 14 6 TERMINAL TYPE File 3 2 3 5 3 6 14 4 15 1 15 8 15 9 15 11 18 6 18 16 BACK SPACE Field 15 8 18 10 18 11 CLOSE EXECUTE Field 14 7 15 8 18 6 18 16 18 18 FORM FEED Field 15 8 18 10 18 11
309. d RESOURCE SLOTS that determines how many jobs can simultaneously own it as a resource Device Handler and TaskMan work together to provide resource device functionality The RESOURCE file 3 54 stored in the translated ZISL global regulates processing and is for internal use only The NAME field 01 holds the I of the resource device Other fields hold information on jobs currently using the resource information that is cleared when the resource 1s closed The RESOURCE file 3 54 supports processing by maintaining a count of the number of available slots The ability to open and close resources is accomplished by decrementing and incrementing this count Limiting Simultaneous Running of a Particular Task Resources make it possible for you to control the number of a particular kind of non I O task that runs at any one time If you have a particular job and you want no more than three running versions of it at any one time you can queue the job through the ZTLOAD interface to a resource that had a RESOURCE SLOTS setting of 3 Running Sequences of Tasks Resources also make it possible to run non I O tasks in sequential order Non I O tasks ordinarily can run simultaneously because they do not compete for the ownership of I O devices If you instead queue such tasks to the same resource and the resource has a RESOURCE SLOT setting of 1 TaskMan will run the tasks one at a time and in the order queued In this way the result
310. d a file to a user s ACCESSIBLE FILE Multiple field 32 in the NEW PERSON file 200 The conversion uses the FILE MANAGER ACCESS CODE field 3 DUZ O string to assign file access according to the characters in the string If a file is protected with a particular character that matches one in the user s code that file is entered into the user s ACCESSIBLE FILE Multiple field 32 Levels of access are granted according to the file s original security field level security continues to function the same by checking the FILE MANAGER ACCESS CODE field 3 5 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security NOTE Users with programmer level access FILE MANAGER ACCESS CODE field 3 will not need to have any files in their ACCESSIBLE FILE Multiple field 32 since they will be able to access all files without restriction DISV Global The File Access Security conversion process makes use of the DISV global to identify which files have recently been accessed by which users The conversion adds all files that the user has been able to access select from to the user s ACCESSIBLE FILE Multiple field 32 list It grants READ access to these files Using the DISV global to grant file access has the benefit of permitting option usage as usual the day after the conversion is run KILLing the DISV global just before the conversion is not advised since many users will
311. d indicate normal intensity The quality settings are Q Q1 and Q2 Your IRM needs to confirm that the appropriate code to set the specified printer attributes 1s set up for the device that you are using Then when the Device Handler closes the device IRM needs to be sure that appropriate reset code is in the CLOSE EXECUTE field so that the characteristics do not stay in effect If for example someone requests a small pitch subsequent reports will also use the small pitch unless reset in the CLOSE EXECUTE statement for that device or altered by the OPEN EXECUTE statement of the next device called Summary The Device Handler is a common interface used by all VistA applications to send output to devices usually printers Once you become familiar with the Device Handler you can enhance your productivity by making use of some of the Device Handler s special features including queuing selecting a specific right margin or page length and selecting a special subtype July 1995 Kernel Systems Management Guide 14 7 Revised June 2008 Version 8 0 Device Handler User Interface 14 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 15 Device Handler System Management The Device Handler makes use of two primary Files e DEVICE File 3 5 e TERMINAL TYPE File 3 2 Together these two files control most of the characteristics of devices in Kernel DEVICE File 3 5 Kernel s DEVICE file 3 5 stores inf
312. date the Kernel Systems Management Guide As time allows we will be updating this reformatted manual with all released patch information that affects its content Because of the chapter numbering scheme future additions can be made with minimal disruption to the entire July 1995 Kernel Systems Management Guide 1 Revised June 2008 Version 8 0 Revision History Date Revision Description Author E 7 manual page flow Thanks for your patience Software Version 8 0 Reviewed document and edited for the Data Scrubbing and the PDF 508 Compliance projects Data Scrubbing Changed all patient user TEST data to conform to Ol amp T standards and conventions as indicated below e The first three digits prefix of any Social Security Numbers SSN start with 000 or 666 Patient or user names are formatted as follows XUPATIENT N or XUUSER N respectively where the Nis a number written out and incremented with each new entry e g XUPATIENT ONE XUPATIENT TWO etc Other personal demographic related data e g addresses phones IP addresses etc were also changed to be generic PDF 508 Compliance The final PDF document was recreated and now supports the minimum requirements to be 508 compliant i e accessibility tags language selection alternate text for all images icons fully functional Web links successfully passed Adobe Acrobat Quick Check Software Version 8 0 Updates e R
313. dates the ROUTINE file 9 8 to match the routine set stored on the current system Ideally the ROUTINE file 9 8 would contain an entry for every routine on the current system However the ROUTINE file 9 8 does not get updated automatically when routines are added to or deleted from the system But KIDS needs the ROUTINE file 9 8 so that it can store the list of routines in a software application as pointers to the ROUTINE file 9 8 rather than relying on namespace alone Developers should use this option to update the ROUTINE file 9 8 before editing the routine component in a build entry to ensure that all the routines they want to include in a software application can be selected by the routines matching entries in the ROUTINE file 9 8 If you answer YES to the question Want me to clean up the Routine file before updating the option goes through the ROUTINE file 9 8 and deletes any entries across all namespaces that have no matches with an actual routine on the current system As of Kernel Patch XU 8 0 393 however any routine that has been marked in the CHECKSUM REPORT field 6 in the ROUTINE file 9 8 as National will not be deleted during the clean up the Routine File phase of the update Then the Update Routine File option re populates the ROUTINE file 9 8 with all routines currently on the system for the namespaces you enter you can exclude parts of a namespace if you want as well Figure 24 10
314. de as follows gt D XTRGRPE Routine Edit Option The Routine Edit option XUPR RTN EDIT invokes the Z editor The Z editor can be used to edit a group of routines with the Group Routine Edit option This allows developers at an external site e g on the site manager s staff to edit M routines This option is locked with the XUPROGMODE security key The corresponding direct mode utility can be used in programmer mode as follows gt X SZ REF For more information on the Z Editor please refer to the Z Editor topic in Chapter 0 Error Not a valid result for table in this manual Routines by Patch Number Option The Routines by Patch Number option XUPR RTN PATCH allows users to print routines associated with a patch When prompted enter a list of routines The output is sorted by patch number Variable Changer Option The Variable Changer option XT VARIABLE CHANGER runs the XTVCHG routine which changes all occurrences of one variable to another This option is locked with the XUPROGMODE security key July 1995 Kernel Systems Management Guide 26 5 Revised June 2008 Version 8 0 Routine Tools CAUTION This option changes DOs and GOTOs also but it does not change the target of the DOs and GOTOs For example if you request to change all occurrences of TAG to TAGS DO TAG would be changed to DO TAGS However the actual Line Label called TAG would not be changed The corresponding direc
315. decide how a server request is to be treated see Table 11 1 SERVER MAIL GROUP 222 This field is a pointer to another mail group the first is pointed to by XQSERVER and or the bulletin in Field 220 to which server request notifications are to be sent The software will notify all legitimate users in all mail groups pointed to It is recommended that this field be left blank and a mail group be assigned the chosen bulletin instead N CAUTION Server options will not work unless there is a local active user associated with the specified mail group SERVER AUDIT 223 This field causes the server request to be audited in the AUDIT LOG FOR OPTIONS file 19 081 The default is YES The information stored for an audited server option includes Option name User always PostMaster Device Job number Date Time CPU Message number Return address of sender Subject of the message 11 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Server Options e Error message A server option can also be audited using the normal option auditing software Auditing the PostMaster or the namespace XQSRV will capture all server requests SUPPRESS BULLETIN 224 If set to Y YES it prevents a bulletin from being sent under normal conditions If there is an error or a possible security breach a bulletin will still be fired If the field is not filled in it takes the default of N which means tha
316. dentity completing the VistA Kernel authentication process Asterisks only are displayed when you enter your Access and Verify codes so that the actual characters are not displayed echoed back on the screen Codes are encrypted after they are entered and compared with the encrypted stored values for a match REF For a description of valid and strong Access and Verify codes please refer to the Defining a Strong Verify Code topic that follows in this chapter Figure 2 1 Signing on to VistA Sample roll and scroll user authentication dialogue ACCESS CODE lt Enter gt VERIFY CODE xxxxxx x lt Enter gt Device _TNA8628 An invalid Access and Verify Not a valid ACCESS CODE VERIFY CODE pair code pair produces an error ACCESS CODES lt Enter gt VERIFY CODES lt Enter gt Good evening FRIEND You last Signed on Apr 21 1992 at 07257 There was 1 unsuccessful attempt since you last signed on You were last executing the MailMan Menu menu option Do you wish to resume YES Entering a valid Access and Verify code combination completes the signon authentication process and takes you beyond Signon Security into Kernel s Menu Manager or other security role based access keys used to authorize your appropriate level of access to data and or application functionality If you have not been assigned a primary menu Kernel displays a message indicating that access is not allowed and signs you out from th
317. described in the Advance Preparation for the Conversion topic described earlier For example the DOMAIN file 4 2 may need to be protected so that it will be granted to users having a FILE MANAGER ACCESS CODE field 3 containing the assigned symbol character NOTE In previous documentation and data dictionaries it has been implied that the pound sign symbol character was reserved for File Access Security for IRM however this is not true It has merely been used as a convention 2 Review the FILE MANAGER ACCESS CODE fields 3 of VA FileMan users The codes should contain symbols characters matching those used to protect the files that these individuals use Since the conversion will automatically grant files to users according to previous privileges as indicated by the FILE MANAGER ACCESS CODE field 3 add any additional symbols characters to their FILE MANAGER ACCESS CODE fields 3 to take advantage of the conversion s automated file assignment according to levels of access 3 Be ready to use the File Access Security menu XUFILEACCESS Figure 5 3 to review and grant file access privileges after the conversion July 1995 Kernel Systems Management Guide 5 13 Revised June 2008 Version 8 0 File Access Security 4 Inthe production account enable File Access Security system features and options with ENABLE XUFILE3 as illustrated below Figure 5 6 Enabling File Access Security Sample user dialogue In VAH
318. device assigned at signon users also need a terminal type As described in the Signon Security System Management chapter in this manual Kernel can usually determine the correct subtype without needing to prompt the user by querying the terminal and matching the returned string if any with return codes for terminals stored in the DA RETURN CODES file 3 22 If the user is prompted to enter a terminal type they will need to choose one The list of terminal types from which they can choose is screened by the SELECTABLE AT SIGN ON field in the TERMINAL TYPE file 3 2 Users can only choose from entries with this field set to YES This stops users from choosing inappropriate terminal types The setting of this field does not prevent terminal types from being chosen by the DA return code method however Make sure that all terminal types appropriate for signon have SELECTABLE AT SIGN ON set to YES If the Signon Security system cannot supply even a default the Device Handler makes a selection according to the signon device s subtype Managing Display Attributes DA Return Codes Figure 15 7 DA Return Code Edit option Device Management XUT DA Return Code Edit XU DA EDIT The DA RETURN CODES file 3 22 stores entries for the codes returned by different terminals after Kernel asks for their display attributes at signon This file then maps Kernel terminal types to terminal s return codes This mapping allows sites to
319. dit TaskMan Parameters menu one to edit each of the three configuration files Because the TASKMAN SITE PARAMETERS 14 7 allows you to define parameters e g TaskMan Job Limit separately for each CPU on your system you are able to optimize TaskMan s behavior individually for each CPU You no longer need to stop and then restart TaskMan in order to change the TASKMAN JOB LIMIT ona CPU Cross references on the relevant fields locate every TaskMan on your system and inform them that they need to update their TaskMan parameter information Thus within a minute or so of making the changes TaskMan on that CPU should be operating with the new value TaskMan s Reach The key issue that defines TaskMan s configuration is its reach those places where TaskMan can start background jobs TaskMan s reach extends to e All UCIs a Submanager can access directly after using Kernel s UCI switching facilities e All other Managers to whose TASKS 14 4 and SCHEDULE files a given Manager can WRITE using extended global reference e All UCIs on Print Servers with link access to the current Volume Set TaskMan s reach does not include other sites on a wide area network because they cannot be accessed through either UCI switching or through extended global reference There are ways to simulate such a reach through the use of server options however For purposes of TaskMan configuration we generally think in terms of the reach of a single Manager which
320. ditor you should press lt PF1 gt E to exit 2 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security User Interface Alerts After signing on you could be presented with an alert notice just before the menu prompt If so you need to pick the View Alerts VA option XQALERT for viewing alerts to take care of urgent pending matters REF For more information about alerts please refer to the Alerts chapter in the Menu Manager section in this manual Figure 2 6 System commands View Alerts VA option SYSTEM COMMAND OPTIONS XUCOMMAND View Alerts VA XQALERT User s Toolbox Menu The User s Toolbox menu XUSERTOOLS is available from any menu prompt by entering the toolbox synonym e g TBOX or User s Toolbox It makes available from one menu some of the most frequently used Kernel options Figure 2 7 User s Toolbox menu options Select User s Toolbox Option Change my Division XUSER DIV CHG Display User Characteristics XUUSERDISP Edit User Characteristics XUSEREDITSELF Electronic Signature code Edit XUSESIG Menu Templates XOTUSER Spooler Menu XU SPL MENU gt Locked with XUMGR Switch UCL XU SWITCH UCI TaskMan User XUTM USER User Help XUUSERHELP July 1995 Kernel Systems Management Guide 2 7 Revised June 2008 Version 8 0 Signon Security User Interface The following table lists the options contai
321. document on the VDL Mendoza Roger Deleted Default Task Priority MBEAN OKIP OTMSBY l and Ba Tran topic from this manual Moved the Error Screens topic ee ete from Chapter 22 TaskMan System Management Operation to Chapter 13 Error Processing Updated the Alpha Beta Tracking topic in Chapter 23 Merged information from the Kernel Systems Management Guide this manual into the Kernel Developer s Guide in order to avoid duplication and confusion with instructions procedures Updated VA OI amp T organization changes and the document properties e g Title Author Creation Dates Keywords etc Updated references to the VDL Removed all references to HSD amp D Updated Alert options in Figure 10 3 and added the missing descriptions for those Alert related options Completed updates to remove obsolete references to MSM PDP 486 VAX Alpha etc and updated vi Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Revision History references to DSM for OpenVMS to Cach where appropriate Updated content references to checksum compares based on Kernel Patch XU 8 0 393 Changed references from INDEX to XINDEX where appropriate Updated Section Ill Device Handler chapters Deleted Kermit section Updated SPECIAL QUEUEING topic in Chapter 22 Added Table 22 1 Updated Security Forms section in Chapter 3 Signon Security System Management Software Version
322. e Security and Other Common Services S amp OCS products projyects g Broker Components Kernel VA FileMan MailMan Toolkit Mail Groups ISC STAFF Public KERNEL PROGRAMMERS Public July 1995 Kernel Systems Management Guide 2 11 Revised June 2008 Version 8 0 Signon Security User Interface Switch UCI Option The Switch UCI option XU SWITCH UCI allows users to select from a list of UCIs if any stored for that user in the NEW PERSON file 200 Summary VistA s Kernel s Signon System Security module provides the means for signing into Kernel with a unique identity Once you complete the signon process you are sent to Kernel s menu system where you can run any option your system manager has placed in your menus When you finish a computer session always be sure to sign off this protects your account from misuse by someone else 2 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 3 Signon Security System Management This chapter describes the system management tools for Kernel s Signon Security module Signon Process If signons are enabled as shown in the Signon Flow Chart that follows the signon process begins with a gathering of information from the KERNEL SYSTEM PARAMETERS file 8989 3 and then from the DEVICE file 3 5 to determine whether to allow signon for this session and if so how to create an appropriate environment If for example the MAX SIGNON ALLOWED limit h
323. e Multi Term Lookup MTLU option it recognizes all the codes and descriptions associated with MALIGNANCY LEUKEMIA and CARCINOMA NOTE A synonym replaces the original word in the lookup process therefore to retain the original word in the search it must be matched to itself as well as to other synonyms Words used as a shortcut should never be repeated as synonyms or keywords Since the system searches for shortcuts first and stops when one is found it cannot find duplicated words in the LOCAL SYNONYM 8984 3 or LOCAL KEYWORD 8984 1 files Since searching all files for each word is time consuming the search is done in this order so as to speedup the search process 25 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU Since the add modify functions for Shortcuts Keywords and Synonyms are considered separate options a process chart for each is provided The charts on the following pages show the prompts and steps involved in using the following options Figure 25 11 Add Modify Utility menu options Select Add Modify Utility Option SH Shortcuts XTLKMODSH KE Keywords XTLKMODKY SY Synonyms XTLKMODSY The Shortcuts option XTLKMODSH one of the three selections within the Add Modify Utility option is described below July 1995 Kernel Systems Management Guide 25 13 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The following process char
324. e aks s bmitted to the queue to run and it oS builds and runs the TMP pid files ga SL Build the file to run can t pass arguments with RUN gt pid F GETJPI PID infile TMP_ pid ZTM S Out ae EMP ae pid t Tulog S SAY write output 3 S entry START S if p3 veg 1 then entry RESTART S S open and build the input file S OPEN write output infile S SAY S Taskman temp file to run the Manager GAY TOT Delere this Tile If 1t Ss not opens gt SAY S Set verity amp iAY Vs esesci on MEDLARE Saw a hp 2 we TO Veni Se EMO art TOA TE esq S Close Ourput 3 ml det a Log Tile 26 needed change NLA tOo ourti te S name ZTMS_ pid S run sys system loginout exe inp t infile output _NLAO detach process name on S Wait for loginout to run it then delete the file S wait 00 01 gt del TMP_ ZTM 1 gt exe 21 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration Figure 21 17 ZTMS2WDCL COM Command File ZLIMS2WDCL COM Cache Start Submanager with a DCL Context KERNEL 8 pl is the Cache config name p2 is the namespace to start p3 is NOT used VOL for DSM This file is submitted to the queue to run and it builds and runs the TMP_pid file Sa S Build the file to run can t pass arguments with RUN 2 pid ESGETJPI TT TPID infile TMP_ pid ZTMS S Out tite TMP
325. e assigning Help Frame Editors An existing help frame can be edited through the Help Processor options by the following people e The help frame author e Any holder of the XUAUTHOR security key e Anyone who has been assigned as an editor to that help frame To assign an editor to a given help frame use the Assign Editors option XQHELP ASSIGN or to de assign an editor to a given help frame use the Unassign Editor option XQHELP DEASSIGN July 1995 Kernel Systems Management Guide 12 5 Revised June 2008 Version 8 0 Help Processor Disk Space Concerns Help frames consume disk space The amount can be considerable if numerous frames are exported with a software application You can estimate the size of the HELP FRAME file 9 2 by Kernel s Block Count utility Figure 12 8 Estimating the size of the HELP FRAME file 9 2 using Kernel s Block Count utility Select Systems Manager Menu Option Prog lt Enter gt rammer Options Select Programmer Options Option Global lt Enter gt Block Count Block Count for Global DIC 9 2 Creating and Editing Help Frames One way to edit help frames from the HELP FRAME file 9 2 is to use the Display Edit Help Frames option to display the help frame in question Then at the Select Help System Action prompt you can enter E to edit the help frame if you have edit access to the help frame You have edit access if e You are the help frame s author e You are assigned as an editor f
326. e build entry before creating a transport global Figure 24 11 Verify a Build option Sample user dialogue Select Utilities Option Verify a Build Select BUILD NAME XU 8 0 11 lt Enter gt KERNEL File 3995 NOT FOUND Do you want to remove the missing Files NO lt Enter gt DONE Select Utilities Option Verify Package Integrity Option You can use the Verify Package Integrity option XPD VERIFY INTEGRITY to compare checksums of software components on the system against the checksums of the components when they were originally transported Any discrepancies are reported Currently routines are the only components that are checked but checksums will be extended to other software components in the future The checksums of components for the currently installed software are verified against checksums stored in the BUILD file 9 6 entry for the software If the most recent version of the BUILD file 9 6 entry for a software application has been purged the Verify Package Integrity option will no longer be able to verify checksums for the loaded software Because of this in most cases you should not purge the most recent build entry for a software application NOTE As of Kernel Patch XU 8 0 369 the integrity checking CHECK1 XTSUMBLD API supports the Compare local national checksums report option XU CHECKSUM REPORT July 1995 Kernel Systems Management Guide 24 11 Revised June 2008 Version 8 0 KIDS System
327. e computer system Similarly if your primary menu has been marked as out of order an option attribute Kernel also denies you access see Figure 2 2 REF For more information on primary menus please refer to the Menu Manager section in this manual 2 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security User Interface Figure 2 2 Access denied due to no primary menu or menu out of order message ACCESS CODES xx x lt Enter gt VERLEY CODED VARTE lt BnEeGr gt Device _TNA8628 lt Enter gt No access allowed for this user Defining a Strong Verify Code While Access codes are a unique identifier 1 e username for your user record in Kernel s NEW PERSON file 200 Verify codes are secret passwords assuring that the person signing on is the one for whom the user record was established You rarely need to be issued a new Access code but you must change your Verify code if you suspect that someone else has used it to gain access to the system or when your Verify code has expired 1 e every 90 days or less You can change your Verify code with the Edit User Characteristics option is available from the Common menu User s Toolbox menu As of Kernel Patch XU 8 0 180 Strong Access and Verify codes must adhere to the following criteria July 1995 Access and Verify codes cannot be identical Verify codes 1 e passwords must be at least 8 characters in length Strong pa
328. e default header page distributed with Kernel Figure 21 8 Customized Header Page routine SZZTMSH SEA RDS Local Sample Header Page 3 9 92 11 17 eee deg eO Caer s Print The Local Header Page build text lines X1 SP G VA 200 DUZ 0 U I X1 S X1 name unknown X2 SP SG VA 200 DUZ 5 U 2 I X2 5 X2 unlisted mail stop X3 SP SG VA 200 DUZ 13 U 2 I X3 S X3 unlisted phone number AZINE SSPORMAT i _X1_ _X2_ X3_ IOM ZZLINK2 SSFORMAT _ZTDESC_ IOM ZZLINE3 FORMAT TON HTE XLFDT H _ IOM W ZZ2LINEZ2 1 ZZLINE3 FORMAT ZZTEXT ZZIOM local extrinsic function input text to be formatted and margin width output text filled out to margin width 3 with characters LA ly ZZFILLED 2A l Z2TOM 3 L ZZTEXTI 2 SP ZZFILLED ZZ1 24 1 SP CAGE La lag AN 7A i Pea al EXI SL ZZFILLED 3 ZZI0M S ZZFILLED ZZFILLED_ LZE LT LLED Figure 21 9 Customized Header Page KKKKKKKKKKKK XUUSER ONE OLFO ETS 555 5555 KKKKKKKKKKKK KKKKKKKKKKKK XUUSER ONE OIFO FTS 555 5555 KKKKKKKKKKKK KKKKKKKKKKKK XUUSER ONE OLFO ETS 555 5555 KAKKKKKKKKKKK KKKKKKKKKKKKKKKKKKKKKK SAMPLE TASK KKKKKKKKKKKKKKKKKKKKKKEK KKKKKKKKKKKKKKKKKKKKKK SAMPLE TASK KKKKKKKKKKKKKKKKKKKKKKEK KAKKKKKKKKKKKKKKKKKKKKK SAMPLE TASK KKKKKKKKKKKKKKKKKKKKKKEK kkk AKO LAT DEVICE Jun 30 1992 14 34 01 kee RR RH Kk AAO LAT DEVICE Jun 30 1992 14 34 01 eke RRR RH kkk AC LAT DEVICE Jun 30 1992 1
329. e if they want to run the environment check for each transport global If a transport global does not pass its environment check KIDS may purge it from X TMP otherwise the transport global stays in XTMP KIDS tells you the result of each environment check e Checks the version number of the incoming software against any existing software of the same name at the site If the incoming version number is not greater than the existing version KIDS aborts the installation for the transport global in question e Echoes the name of the first transport global to pass environment check 1 e Use transport global name to install this Distribution The name of the first transport global to pass its environment check is the name you use to install the distribution in the next phase Loading a distribution is the first of three phases to install VistA software The second phase is answering installation questions including scheduling the installation the third and final phase is the actual running of the installation When loading from a PackMan message load the distribution using the INSTALL CHECK MESSAGE PackMan option in MailMan For KIDS PackMan messages this option through MailMan is equivalent to the Load a Distribution option XPD LOAD DISTRIBUTION July 1995 Kernel Systems Management Guide 23 9 Revised June 2008 Version 8 0 KIDS System Management Installations Figure 23 6 Load a Distribution option Sample user dialogue Selec
330. e of distribution contains one transport global only and that transport global can export M globals only The transport globals in both types of distributions also contain the corresponding build entry and if linked to a PACKAGE file 9 4 entry the corresponding PACKAGE file 9 4 entry However a patch sent with KIDS does not transport the entire PACKAGE file 9 4 entry It only sends the information that is needed to update the PACKAGE file 9 4 What Happens to DIFROM Developers should no longer use the DIFROM entry point to export software Developers should use KIDS The DIFROM method is still supported but only for the support of sites that use standalone VA FileMan VA FileMan without Kernel REF For more information on using DIFROM please refer to the VA FileMan Programmer Manual 23 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations Installing Standard Distributions As noted previously KIDS supports two types of distributions e Standard e Global This topic describes how KIDS installations work when installing standard distributions Installation Sequence KIDS installs standard distributions in three phases 1 Loading transport globals from the distribution 2 Answering installation questions for each transport global 3 Installing each transport global in the distribution Phase 1 Loading Transport Globals from a Distribution or
331. e some documents Old documents are deleted automatically on a schedule as determined by IRM The life span of a spool document is a site parameter that IRM controls IRM should inform you of the life span of spooled documents so that you are not surprised when old documents are purged July 1995 Kernel Systems Management Guide 17 3 Revised June 2008 Version 8 0 Spooling Browsing a Spool Document With the Browse a Spool Document option you can view spool documents with VA FileMan s Browser The Browser allows you to view spool documents on your terminal screen letting you scroll backward and forward through the report and also letting you perform simple searches within the report In the past when you sent a report to the terminal screen you could only go in one direction forward by pressing lt Enter gt after each screen of text REF For more information on using the Browser please refer to the VA FileMan Getting Started Manual Printing Spool Documents You can print spool documents with the Print A Spool Document option Before selecting an output device you are prompted for the number of copies to print If you have been granted the ability to print to multiple devices you can send your output to several devices for simultaneous printing If this privilege has been granted to you the device prompt is displayed again after you choose the first printer Entering a NULL response to the second device prompt tells the spool
332. e to support the ordering of medical tests and other activities Kernel includes several protocol type options for enhanced menu displays within the OE RR software Requesting that a job be processed in the background rather than in the foreground within the current session Kernel s TaskMan module handles the queuing of tasks An option attribute that specifies that the option must be processed by TaskMan the option can only be queued The option can be invoked and the job prepared for processing but the output can only be generated during the specified time periods A method that enables sequential processing of tasks The processing is accomplished with a RES device type designed by the application developer and implemented by IRM The process is controlled via the RESOURCE file 3 54 A menu jump used to go out to an option and then return in a bouncing motion The syntax of the jump is two carets uppercase 6 on most keyboards followed by an option s menu text or synonym e g Print Option File If the two carets are not followed by an option specification the user is returned to the primary menu See also GO HOME JUMP A way of ordering TaskMan to run an option at a designated time with a specified rescheduling frequency e g once per week The Scroll No Scroll button also called Hold Screen allows the user to stop No Scroll the terminal screen when large amounts of data are displayed too fast to read
333. e used to format the error report Error Screens At times you may not want to trap a certain type of error but merely to count them because you are already aware of the error and can do nothing to prevent it At other times you may not even want to count the error because it is inevitable or harmless An error screen is a string of characters that is compared with the error message of every error trapped Any trapped error whose message contains the screen is screened out You decide for each screen whether the error is counted or completely ignored In either case the error is not recorded in either the Kernel ERROR LOG file 3 075 or the Taskman Error Log In TaskMan if a running task encounters a screened error the Submanager still notes the error in the record for that task Kernel gives you four options with which to manage your error screens e List Error Screens XUTM ERROR SCREEN LIST e Add Error Screens XUTM ERROR SCREEN ADD e Edit Error Screens XUTM ERROR SCREEN EDIT e Remove Error Screens XUTM ERROR SCREEN REMOVE NOTE These error screen options are described in the topics that follow in this chapter Error Processing Previously these options were described in Chapter 22 TaskMan System Management Operation Because these error screen options apply to all errors and not just TaskMan specific errors they were moved to this chapter For historical purposes however these four option names are still prefixed with
334. e when you know for sure that it has failed you can invoke XUTM STOP to prove to XUTM RESTART that the Manager really has stopped Then you will be able to restart it Place Taskman in a WAIT State Option Figure 22 16 Place Taskman in a WAIT State option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Place Taskman in a WAIT State XUTM WAIT The WAIT state as described in the Troubleshooting topic in this chapter is a condition in which the Manager does nothing but wait for you to release it Putting a stop to the Manager s activities without actually shutting down the Manager can often be very useful For example with the Manager in a WAIT state you can look at the tasks after they are queued but before the Manager has a chance to validate them This can help you isolate problems caused by the queuing process from those caused by the validation process Another time you may want to create a WAIT state is before restarting a manager that has stopped This prevents the Manager from processing any tasks when it first starts up the Manager will check out its environment and then WAIT for your command to continue The Place Taskman in a WAIT State option XUTM WAIT gives you a way to switch the Manager s activities on and off without having to completely shut down and restart the Manager When you select the XUTM WAIT option you are also prompted with the question Sh
335. each CPU BOX VOLUME pair entry should process tasks You can set it to one of four values e General Processor G The G type should be selected when the TASKS 414 4 and SCHEDULE files are seen by only one Volume Set For example VA s Alpha clusters have several CPUs but each of them runs on the same Volume Set The Manager on a G type runs tasks created on the same Volume Set and tasks from any other Volume Set that explicitly requests the G type s Volume Set The G type sends tasks from another Volume Set that did not explicitly request its Volume Set back to the originating Volume Set however To transfer tasks to a G type TaskMan uses extended global references to copy the task to the destination TASKS 14 4 and SCHEDULE files and then removes the task from its own side Submanagers started on a G type processor process tasks in the Partition Waiting List and the Busy Device Waiting List e Print Server P The P type should be selected when multiple Volume Sets map to the same TASKS 414 4 and SCHEDULE files and you want to run the Manager on the Volume Set CPU in question Like the G type the Manager on a P type runs tasks created on the same Volume Set and tasks from any other Volume Set CPU that explicitly request the P type s Volume Set CPU Unlike the G type however the P type also runs tasks from other Volume Sets that did not make an explicit Volume Set request Tasks are transferred to a P type in the same way as
336. each screen of text If the Browser has been installed at your site and set up as a device you can now use the Browser to view any report that asks you for an output device To send a report to the BROWSER device at any device prompt enter BROWSER as the device You may not want to send huge reports to the BROWSER however since the report must complete before you can view its output in the Browser REF For information on using the Browser and on Browser commands please refer to the VA FileMan Getting Started Manual July 1995 Kernel Systems Management Guide 18 1 Revised June 2008 Version 8 0 Special Device Issues Figure 18 1 Print File Entries option Sample user dialogue when sending a report to the Browser device Select VA FileMan Option Print File Entries OUTPUT FROM WHAT FILE DOMAIN SORT BY NAME lt Enter gt START WITH NAME FIRST lt Enter gt FIRST PRINT FIELD NAME THEN PRINT FIELD lt Enter gt HEADING DOMAIN LIST lt Enter gt DEVICE HOME BROWSER lt Enter gt HFS CRT One moment Figure 18 2 Report displayed in Browser device Domain List sample output DOMAIN LIST JAN 24 1995 15 12 PAGE 1 ALBANY VA GOV ALBUQUERQUE VA GOV ALEXANDRIA VA GOV ALLEN PARK VA GOV ALTOONA VA GOV AMARILLO VA GOV ANCHORAGE VA GOV ANN ARBOR VA GOV ASHEVILLE VA GOV ATLANTA VA GOV AUGUSTA VA GOV BALTIMORE VA GOV BATAVIA VA GOV BATH VA GOV BATTLE CREEK VA GOV BAY PINES VA GOV BDC VA
337. eaeeeeeseeeeseeeeeeeees 17 7 Freure 17 13 Spool Management menu Options mesier i teens anes E es eee 17 7 Figure 7 14 Spooler Site Parameters Optom vescdic sacvacosatastadeaies teenslattsamcbaaesdic cies sdesaentetedeh tines baaestespeltaaruetys 17 8 Figure 17 15 Purge old spool documents option cccccccccccecceeceeeceeeaaeeeessseeeeeeeeeeeeeeeeeeeeeaasaaeseseseeees 17 8 Figure 17 16 Spool Device for Cach and GT M 0 0 ceccceeceeeeeeeeeeeeeeeeeeeeeeeeeseseeeeeeeeeeeeeeeeeeeeeeeeeeeeeas 17 9 Fiore L 17 Spool Device EG Op iOnn itor Ges concen e E moss ne laurent ncumdateneetic 17 9 Figure 17 18 Device Edit option Sample user dialogue cccccccsseessseeecceccceeeeeseseceeeeeeaaaeeeeeeeeeenes 17 10 Figure 17 19 Generating spool document name Samople user dialogue ccccccceeeeeeeeeeeeeeees 17 10 Figure 18 1 Print File Entries option Sample user dialogue when sending a report to the Browser CNA E EOE ELE AE EE ETA T oh EEE TE EEE PEE O TEELE ET ET EET 18 2 Figure 18 2 Report displayed in Browser device Domain List sample output seeeeesessssssssssseeereeeee 18 2 Figure 18 3 Cach and GT M Browser Device TERMINAL TYPE file 3 2 entry 0 0 a 18 4 Figure 18 4 Cach and GT M Browser Device DEVICE file 3 5 Entry cc ccccsssssssesssseeeeeeeees 18 4 July 1995 Kernel Systems Management Guide XXV Revised June 2008 Version 8 0 Figures and Tables Figure 18 5 Device Edit option
338. edattmasbiecnedenetseesar 7 13 Error Messages Donne Menu Jumping esii a a a 7 14 AKUTE Gopal Struct re and Pun C UOM E a aatensee caeeetaetenee 7 16 UR So L E E EE E A E S T A E E A S E T A EE E E 7 16 XOT Nodes MENU Templates enpresari ro ir na E E uatinel Saaceahoncaiun 7 17 PEDS NO S E RUneren opeeent mentee UT re ene nteeerT 7 17 JOP NOIES ees tans Aa chet Mansi lt ialae tite R ia cdakss hut Giasla Silantch tt iats said a cata ddantchiheat 7 19 Menu Manager Variables Troubleshooting ccccccesseesseeccccceeeeeeeeeeeeeeeeaaeeseeeeeeeeeeeaaenenes 7 20 SECU KC VS rai acicte saat a detain Raa hd nd Miansadtabaa ns debe yea bees whe acaea au neaaaes 8 1 User IME ACS cass tase ihat toca a r 8 1 SV Stemi ANAS emeni ernia N uuanedaasassas ad tenets 8 2 Identiti yine Locked Options aici see orca te soe teehed ia a a a a a 8 2 key Via CI C10 a sssesaca sit canscsetaicacomcaivanieseussacsnceeanseneucencascebaaua deena sons stcadsueanhaoeeentsanseeaanesnciane 8 2 Allocatins and De allocatine Security Keysin a 8 3 Dele cating Securty Key Setna a a Mual nee latter 8 3 Creating and Edine Security Keys csscorinin a a aus uastiadictons 8 4 Delete Security K Ey S aa a Geis ees ene eiatactans 8 5 Reindexing All Users Security Keys Option cccccccccccsssseeeeceeecceaeeeseeeeceeeeseeeeesseeees 8 5 Usme Security KReys with Reverse LOCkiaroriisn ne a e E etnias 8 5 Security Key Dele salon Leve luscre e 8 6 SECME Meni Dele s AON saxciesacesanenns
339. eeeeeeeeaaas 25 20 ZO TROUUIME OOS i tid saat steed ne ce hie ante sasat ot ohis cam siect et boaeeerase set ashes ed seetiaanct eabecnd oneeegiedateaasexhotadinwet tec erae 26 1 OD CEN OW caer eer E nad dae ot coc ce isc oa aide Nae nation w E sea aes E E 26 1 WS Ser TS ACS os bac os cedseeenias a a A A E 26 2 PRIVY Zl Oo OVEN C aar cas iuec mut eae ceakonacredteesankeleacwen thins cat wecwald A eeatoceeats 26 2 Editino T OUl CL Sai oi st ge ie h a ateaeiae tae eaae Wanve eat inca aan Siete 26 5 Panone ROUE iesca a tnoad iacechan eet scniane 26 6 Comparine TR OUTINES sescca scuien teen ebes to oie bensned ates eenenateonieeneaen tee tenance 26 6 Delete ROUTES sete sec sdoses rinciesedn densa a O 26 8 Load and Save ROUNE Sosna a E a 26 8 Dr CPE CACM EO eera a E E E eee nee 27 1 CON CIVIC W oia a a aa canta echt Ribak RSA achadte da ttecn hohe teat riacs 27 1 WY Sei Li iA CC patos ce set on anes iene oastue acm sae sass ened acne peta anata connect eet stan areata eatecacceminccene 27 1 Merer OOS MOn aaah sige et aa atest tart Si oduct aetna acuta eat ona Duca aes aca eaee 27 1 FOCE C OND Komen ee erencanee E teen red ar eee tere ree ee eretr 27 2 Miscellaneous Verification Tools iii iisssieiciaesssnsbeckaclaheisdacseciatlencdeledapsiielabeledaeendeaiene 27 3 265 Mascellaneous Prosrammer Tolsassa a a a 28 1 Prorrammer Opuons Ment ersero a 28 1 July 1995 Kernel Systems Management Guide XiX Revised June 2008 Version 8 0 Contents User IMET
340. eformatted document to the latest SOP and Style Guidelines Updated files routines options APIs security keys etc Software Version 8 0 Updates e Made minor formatting updates throughout Changed the original Other Tools section to become the new Kernel Systems Management Guide Version 8 0 Technical Writer Thom Blom Oakland OIFO Oakland CA OIFO ISS Maintenance Team Oakland CA OIFO e Maintenance Project Manager Jack Schram Developers Alan July 1995 Revised June 2008 Toolkit section see note below Added Multi Term Look Up MTLU and Tools chapters from the original Toolkit User Manual V 7 3 see note below Removed the Response Time Measures topic from the original Capacity Management chapter in the Toolkit User Manual V 7 3 see note below Kernel Toolkit Patch X1T 7 3 102 removed all Response Time Log Option menu options XURTL NOTE All Kernel Toolkit content currently in the Kernel Toolkit User Manual and Kernel Toolkit Technical Manual is being absorbed by the Kernel Systems Management Guide Kernel Developer s Guide and Kernel Technical Manual Other Toolkit content has been replaced by other manual sets including e Duplicate Record Merge Patient Merge Resource Usage Monitor RUM Statistical Analysis of Global Growth SAGG Capacity Management CM Tools Software Version 8 0 02 08 07 5 0 Security amp Other Common Servic
341. eing temporarily disabled the user will not be able to jump to reach the option Microsurgery is triggered in the following situations e The option Edit options is used e An Out of Order option set is enabled or disabled e A sufficiently large number of changes have been made to a menu tree It is also recommended to rebuild all primary menu trees every other day during non peak hours using the XQBUILDTREEQUE option If separate copies of XUTL are maintained on different CPUs separate entries should be made in the OPTION SCHEDULING file 19 2 for each CPU so that a separate job will rebuild each CPU s XUTL global Primary menu trees can also be built repaired immediately using the Build Primary Menu Trees option In particular if menu jumping has stopped working and microsurgery is not fixing the menus use the Build Primary Menu Trees option to force a menu rebuild to fix the problem July 1995 Kernel Systems Management Guide 7 13 Revised June 2008 Version 8 0 Menu Manager System Management Error Messages During Menu Jumping There are some conditions under which a menu jump may not be completed In these cases the user will see one of the following error messages Figure 7 16 Menu jump error message 1 of 6 I NEED TO REBUILD MENUS QUICK ACCESS IS TEMPORARILY DISABLED Please proceed to target option s menu text This means that the time stamps on the OPTION file 19 and the XUTL global indicate that the OPTI
342. eld is an option attribute that will be presented when using Edit options When first assigning a number for the display order you may want to use 10 20 and 30 rather than 1 2 and 3 to permit easier modification in the future if another item needs to be inserted PRIORITY You can set an option s PRIORITY field to set a run priority for an option Experimentation will be needed to determine the effect of priority settings HELP FRAME You can specify a help frame for an option The help frame is displayed if at the Select menu prompt the user enters OPTION where OPTION is the name of an option DISPLAY OPTION If AUTO MENU 1s in effect for a user the items on that user s current menu are always displayed A problem can arise when if an option displays output and then quits AUTO MENU s automatic display of menu options scrolls the output off the screen Since the AUTO MENU display usually scrolls the option s output off the screen faster than the user can read the output it can effectively render the option unusable You can avoid this problem by setting the option s DISPLAY OPTION field to YES If set to YES and the user has AUTO MENU turned on Menu Manager will ask Press RETURN to continue after the option completes but before displaying the list of menu options The user will then have a chance to review the output before returning to their menu REF For information on other fields in the OPTION file 19 including how t
343. ement Guide 24 5 Revised June 2008 Version 8 0 KIDS System Management Utilities In this example we create a new distribution containing both ZXG 1 0 the original software application and ZXG 1 0 1 an added software application Figure 24 6 Transport a Distribution Sample user dialogue Select Edits and Distribution Option Transport a Distribution Enter the Package Names to be transported The order in which they are entered will be the order in which they are installed First Package Name ZXG 1 0 lt Enter gt Transport Global exists Use this Transport Global YES Another Package Name ZXG 1 0 1 lt Enter gt Transport Global exists Use this Transport Global YES Another Package Name lt Enter gt Order 1 ZXG 1 0 will use current Transport Global Za ARG Lele i will use current Transport Global OK to continue NO YES Enter a Host File ZXG1 KID Header Comment PATCHED DISTRIBUTION ZXG 1 0 BAG dims wee AAOS Lg Teas Package Transported Successfully NOTE Changing a distribution s build entries before redistributing 1s not recommended 24 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Utilities Display Patches for a Package Option The Display Patches for a Package option XPD PRINT PACKAGE PATCHES prints all patches installed for a software application It displays the Date Installed and who installed the patches It optionally
344. empt to fire off 30 server option processes you can control the maximum number of simultaneous processes that actually run Additional server options will be able to run when resource slots are freed up from the resource device 11 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Server Options Setting Up a Server Option A server option has many fields in common with other option types and is set up using the Menu Management option Edit options This option calls the FileMan edit template option XUEDITOPT which prompts for data to be entered in the following fields listed in field number order Table 11 2 OPTION file 19 field values when setting up a server option NAME 01 This should be a namespaced set of 3 to 30 uppercase letters MENU TEXT 1 Since there is never a menu prompt for a server option this field should instead contain an accurate description of what this server option does as it is used by the server request in error messages bulletins and MailMan replies It should be 3 to 50 characters in length OUT OF ORDER MESSAGE 2 If this field contains between 1 and 80 characters of text the server option is placed out of order and will not be activated by a server request The message itself is included in bulletins or MailMan replies that report the failure LOCK 8 Since server options have no online user associated with them the existence of a lock in this field prevents t
345. en granted full file access privileges for a particular file a further restriction can be placed at the file or field level to prohibit modification of the definition or entry of data Files have top level restrictions of READ WRITE or DELETE access as do fields and templates e If the file field or template is protected with the at sign programmer access the user must also have the at sign in the FILE MANAGER ACCESS CODE field 3 in the NEW PERSON file 200 The Device Handler also checks the FILE MANAGER ACCESS CODE of the user if the SECURITY field in the DEVICE file 3 5 has been defined with a character string The user would not be able to select the device unless at least one of the characters in the user s code matched at least one character in the device code The most important FILE MANAGER ACCESS CODE field 3 character is the at sign programmer access It has special meaning and overrides other file access restrictions or other FILE MANAGER ACCESS CODE field 3 characters It is not recommended that the at sign be allocated unless absolutely needed Allocation is in part restricted by the fact that only those few users who have developer access to the system can give other users the at sign NOTE A SET statement from programmer mode can be used to temporarily assign DUZ 0 without storing the code in the NEW PERSON file 200 which would give permanent programmer access Use of the at sign pr
346. end on the standardized encoding of diagnoses and procedures for reports searches and statistics The ICD DIAGNOSIS 80 ICD OPERATION PROCEDURE 80 1 and CPT 81 files are among some of the more critical files The Multi Term Look Up utility increases the accessibility of the information in these files by associating user supplied words or phrases with terms found in a more descriptive free text field Multi Term Look Up allows e Local setup of virtually any reference file e Modification of the behavior of the special lookup by defining shortcuts synonyms or keywords MTLU integrates with any software that uses a reference file that has been entered into a site s LOCAL LOOKUP file 8984 4 Functional Description The Multi Term Look Up MTLU utility provides a method of enhancing the lookup capabilities of associated software applications This utility is comprised of the following options e The Multi Term Lookup MTLU option XTLKLKUP is used to test ICD diagnosis and procedure codes CPT codes and other commonly used references that have been entered in the LOCAL LOOKUP file 8984 4 Optionally terms or phrases may be entered into the LOCAL KEYWORD 8984 1 LOCAL SHORTCUT 8984 2 or LOCAL SYNONYM 8984 3 files e The Print Utility option XTLKPRTUTL is used to print a list of shortcuts keywords or synonyms from a specified reference file in the LOCAL LOOKUP file 8984 4 This list can be sorted alphab
347. ent To display the results of the audit your DUZ O must equal the at sign programmer access Then you can query the AUDIT file 1 1 in the usual way with VA FileMan s Inquire to File Entries option DIINQUIRE How to Grant File Access IRM specifies the particular files and levels of access for users The File Access Security menu XUFILEACCESS on the User Management menu XUSER provides options to grant file access security These options edit the ACCESSIBLE FILE Multiple field 32 in the NEW PERSON file 200 The options for granting file access privileges fall into three functional categories e EDITING To assign file access to an individual user or a group of users One user s profile can also be duplicated or copied to another user or group of users To simplify adding files number ranges can be specified e LISTING To display one user s profile a name sorted list of all user s profiles or a file or range of files with associated users and the access levels of each e RESTRICTING To entirely limit access by user or by file or to delete a range of files for a user or group of users The options are designed to facilitate queries by user or by file You can add or delete file access for one user or for many users Or you can begin with the file and list users with access or restrict access 5 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security Using the
348. entry 18 17 Figure 18 19 Slaved Printer example Epson LQ870 DEVICE file 3 5 entry cc cceeeeeeeeeeeeees 18 17 Figure 18 20 Slaved Printer example Epson LQ870 TERMINAL TYPE file 3 2 entry 18 17 Figure 19 1 Queuing output Sample user dialOQue cc eeeccescccccccceeseeeeecceceeeaeeseeeceeeeesaaeeeseeeeeeeees 19 1 Ficar 19 2 Task Min U Ser ODAO Monein a E 19 2 Figure 19 3 TaskMan User option Sample user dialogue ssoeeessssssssoerrssssssseerrsssssssecerrssssssseeeees 19 3 Figure 19 4 Edit Task option Sample user dialogue eneseessssoeeesssssssseerrssssssseerrssssssseeressssssseeresess 19 5 Figure 20 1 TaskMan Manager and Submanager process flow diagram eesssssseessssssssoeerssssssssseeee 20 4 Figure 21 1 Site Paramete Edit oponse asin aula caste Le eae eae a estate chin nee 21 2 Fiure 24 2 Volume Set EGiv Option caiassoeatehaoSicsccesereatindsaiesse es atleast iascdes et adeeb iccsaneneen tel 21 5 Z 3 ample Volume Set Setup on FORUM ix isistecccckco hacen he tae a eee e 21 6 Figure 21 4 UCI Association Table Edit Option cccceccccccccccceccecceneeeesesseeeeeeeccceeceeeeeeeeeeeeaaaaaaaaesees 21 8 Figure 21 5 VOLUME SET file 414 5 standardized VA Cach and GT M configuration 21 10 Figure 21 6 UCI ASSOCIATION file 14 6 standardized VA Cach and GT M configuration 21 10 Figure 21 7 TASKMAN SITE PARAMETERS file
349. enu PROHIBITED TIMES FOR SIGN ON As discussed with other signon parameters PROHIBITED TIMES FOR SIGN ON can be used to regulate when the user can sign on The user setting takes precedence over any corresponding device setting PHONE HOME OFFICE PHONE PHONE 3 PHONE 4 COMMERCIAL PHONE FAX NUMBER Set up phone numbers for the user in these fields 3 22 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management VOICE PAGER DIGITAL PAGER Set up pager numbers for the user in these fields LANGUAGE Overrides the setting of the DEFAULT LANGUAGE field in the KERNEL SYSTEM PARAMETERS file 8989 3 Both of these are used to set the DUZ LANG flag for each user VA FileMan uses this setting to enable the display of language specific dates and times numeric formats and dialogues Additional Attributes Editable by Users Some but not all of the user attribute fields can be edited by users using the Edit User Characteristics option The only field the user can edit that is not part of the system manager s Edit an Existing User form is the TEXT TERMINATOR field REF For a description of the fields users can edit using the default Edit User Characteristics form and template please refer to the Signon Security User Interface chapter in this manual Edit User Characteristics Form and Template Kernel exports a ScreenMan form and a template to be used in the Edit User Characte
350. enu 5 1 Screen Editor 2 6 3 5 3 20 3 21 What Happened to DIFROM 23 6 VA FileMan Documentation Web Address 3 20 5 1 5 5 VA Programming Standards and Conventions SAC 26 2 Variable Changer Option 26 5 Variables HOROLOG 22 8 22 9 22 29 STACK 13 4 LISQUIT 15 5 AZZIS 18 9 DIDEL 5 3 5 5 DLAYGO 5 3 5 5 DTIME 3 7 3 21 DUZ 5 9 DUZ AG 3 6 DUZ AUTO 3 6 DUZ 0 3 19 3 20 5 3 5 4 5 7 5 8 5 10 9 5 15 8 DUZ 2 3 6 IO 7 4 IONOFF 18 6 Menu Manager Troubleshooting 7 20 XQABTST 7 20 XQACNDEL 10 3 XQDIC 7 20 XQMM J 7 15 XQPSM 7 20 XQT 7 20 XQUIT 7 15 11 3 XQUR 7 20 XQUSER 7 21 XQXFLG 7 21 XQY 7 21 XQYO 7 21 ZTCPU 21 15 ZTQPARAM 22 21 ZTSTOP 22 33 Verification Tools 27 1 Calculate and Show Checksum Values Option Programmer Options Menu 27 3 Overview 27 1 Routine Compare 27 2 27 3 Routine Compare Current with Previous option 27 2 Update with Current Routines option 27 2 Index 44 Kernel Systems Management Guide Version 8 0 Update with Current Routines Option 27 2 User Interface 27 1 Verifier Tools Menu 27 1 27 2 Verify a Build Option 24 10 Verify Checksums in Transport Global Option 23 12 VERIFY CODE Field 2 10 3 19 Verify Codes 1 1 2 1 2 2 2 3 2 4 2 5 2 10 3 1 3 2 3 6 3 9 3 18 3 19 3 24 3 28 3 29 3 30 5 9 11 4 11 9 Defining 2 3 Log 3 29 Old 3 29 Purging 3 29 Verify Package Integrity Option 24 11
351. er 7 10 Creating 7 2 Critical Alerts Count Report 10 8 Cross Reference Help Frames 12 5 Cross references 12 5 DA Return Code Edit 3 5 15 11 Data Dictionaries Being Audited 5 5 Data Dictionary Utilities xxxv 5 6 Deactivate a User 3 24 3 25 De allocation of Security Keys 8 3 9 9 Delegate keys 8 3 9 8 Delegate s Menu Management 9 2 9 4 9 5 9 7 9 9 Delegating 8 3 9 7 9 9 Delete Entries From Look Up 25 8 Example 25 9 Multi Term Look Up MTLU 25 1 Kernel Systems Management Guide Index 25 Version 8 0 Index 26 Index Delete Error Log 22 26 Delete Old gt 14 d Alerts 10 6 10 7 Delete Routines 26 8 Delete Tasks 20 8 22 6 Delete Unreferenced Options 7 8 28 1 Dequeue Tasks 20 8 22 4 22 5 22 6 22 33 Descriptions 7 5 Device Management 15 2 15 12 DI DDU 5 6 Diagram Menus 8 2 8 5 Diagramming 7 5 DIAUDIT DD 5 5 DIAUDIT PURGE DATA 5 5 DIAUDIT PURGE DD 5 5 DIAUDIT TURN ON OFF 5 5 DIAUDITED FIELDS 5 5 DIEDFILE 5 11 DIEDIT 5 4 5 6 5 7 DIINQUIRE 5 6 5 8 DILIST 5 6 DIMODIFY 5 6 5 8 DIPRINT 5 6 DISEARCH 5 6 Display 7 5 7 6 Description 6 5 Help 6 2 Order 7 3 Display Menus and Options 7 5 Display Patches for a Package 24 7 Display status 19 4 Display User Characteristics 2 11 8 1 Display Edit Help Frames 12 4 12 6 DISTATISTICS 5 6 DITRANSFER 5 6 5 7 DIUTILITY 5 6 Edit a Build 24 9 Edit a User s Options 9 2 Example 9 3 Edit an Existing User
352. er a bulletin send a MailMan reply and or initiate an audit of itself Developers and local IRM staff can also customize the bulletins or MailMan replies Can Server Requests Be Denied Only server type options can be activated by mail messages The following must be true for a server request to be processed e The server option must be set to type s in the TYPE field 4 of the OPTION file 19 If the type is not s and a request is received it results in an error that by default is recorded in the AUDIT LOG FOR OPTIONS file 19 081 e The server option name must be complete and exact when a server request is made or the request will be denied e The server option must not be disabled it can be disabled for all requests by setting its LOCK 3 and or OUT OF ORDER MESSAGE fields July 1995 Kernel Systems Management Guide 11 1 Revised June 2008 Version 8 0 Server Options As long as the conditions listed above are satisfied the only mechanism a site has for security for server requests is the setting of the server option s SERVER ACTION field 221 This field has the following settings Table 11 1 SERVER ACTION field 221 security values for server requests Run immediately This code causes the server request to be honored in real time as soon as it is received from MailMan run immediately provided it is not prevented by a setting in the TIMES DAYS PROHIBITED field 3 91 Queue server This code causes
353. er key after a screen display 14 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler User Interface One form of the subtype request made possible by VA FileMan s print routines is the use of the word SINGLE along with P or PK Appending SINGLE indicates that a pause should occur after the display of each page If using a slaved device to print the screen display for example the next page is displayed only after the user has pressed lt Enter gt Figure 14 11 Terminal type device entry With pauses If the home device is a video terminal output would be DEVICE P DEC SINGLE presented one single page at a time the next page being displayed after the user presses the Enter key If you re not sure which subtype to use you can enter a partial specification of the subtype in the second piece and the Device Handler will let you choose from all matching subtypes For example if a dozen subtypes begin with P LASER you can list them by entering only the beginning of the subtype name e g P LASER Figure 14 12 Partial Device specification Unknown subtype DEVICE LASER P LASER All subtypes beginning with P LASER are listed you can then choose a subtype from this list When using a subtype as the second semicolon piece of a device specification you can still specify a right margin and page length to use but you then do so with the 3rd and 4th semicolon pieces Figu
354. er not to use any more additional printers To save users the time and trouble of despooling their documents IRM can set up a spool device for auto despooling If you invoke such a spool device the spool document is sent to one or more printers when the spooling process has completed After automatic printing the spool document remains available for reprinting as necessary it is not automatically deleted upon despooling Making Spool Documents into Mail Messages You can also be granted the ability to make spool documents into mail messages If so the corresponding option on the Spooler Menu will be available You can use it to make documents into regular mail messages that can then be edited copied or forwarded just like other messages After the text has been moved into a mail message the spool document is deleted The deletion is to allow space for new spool documents 17 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Spooling If you plan to make a document into a message you should do the original output to the spool device with an appropriate margin and page length for a MailMan message Since MailMan breaks incoming text lines at about the 75th character a right margin of 75 may be desirable Indicating that page breaks should not be inserted during the spooling process may also be desirable Otherwise the VA FileMan window command ITOPI is inserted into the text at the beginning of each page While th
355. ere are three fields in an HFS device entry that act as flags for what a user must enter when they use an HFS device The fields are e ASK PARAMETERS TIf this field is set to YES the user must enter the correct M open parameters to open the device This should be set it to NO if the device is accessible to non IRM users If it is set to YES the default value is the current value of the OPEN PARAMETERS field e ASK HES I O OPERATION If this field is set to YES the user can choose what mode the file should be opened in for example READ or WRITE If it is set to NO files are opened in WRITE mode This should be set to NO if the device is accessible to non IRM users assuming that all such users would only need to WRITE host files e ASK HOST FILE When this field is set to YES the user can choose what file will be opened If it is set to NO the default file name built into the device entry is always used This should be set to NO in most cases if the HFS device is accessible to non IRM users since host files can proliferate if many users are able to create many files and also because an HFS device opens up access to the host operating system and the potential for overwriting vital files Host File Server Device Edit Option Figure 16 2 Host File Server Device Edit option Device Management Ex Edit Devices by Specific Types XUDEVEDIT Host File Server Device Edit XUDEVEDITHES The Host File Server Device
356. ermine where the task should run If ZOSF UCICHECK rejects the UCI TaskMan rejects the task If the task is bound for a different Volume Set and that Volume Set s link is down and its REPLACEMENT VOLUME SET is the current Volume Set TaskMan rejects the task BAD DESTINATION VOLUME SET Every task s destination Volume Set must be listed in the VOLUME SET file 14 5 BAD IO DEVICE lt l gt If a port goes bad while many tasks wait for it in the Busy Device Waiting list TaskMan traps an error whenever the port is tested for availability When the Submanager traps such an error it rejects every task waiting for that device INVALID OUTPUT DEVICE The Manager performs a lookup on the devices that tasks request If the ZIS call indicates that the device does not exist then TaskMan rejects the task INVALID ROUTINE NAME If a task s entry point is in a routine the Manager tests for that routine s existence in the library UCI If the routine does not exist there TaskMan rejects the task NO DESTINATION UCI When older applications bypassed the Program Interface they sometimes scheduled tasks without specifying the destination UCI The Manager rejects all such tasks NO LINK ACCESS TO VOLUME SET If the VOLUME SET file 14 5 entry for a task s destination Volume Set indicates there is no link access to that Volume Set the task is rejected NO ROUTINE AT DESTINATION If a task s entry point is in a non routine then the
357. erms for PROCEDURE MODIFIERS entries PREFIX M lt Enter gt lt REMINDER gt Using Edit File set the lookup routine XTLKDICL in PROCEDURE MODIFIERS DD Select LOCAL LOOKUP NAME lt Enter gt Add Modify Utility Option The Add Modify Utility option XTLKMODUTL is used to enter new or edit existing shortcuts keywords or synonyms to the LOCAL LOOKUP file 8984 4 A shortcut is a word or phrase which recognizes one specific code or procedure If you are adding a shortcut whose text duplicates the first part of an existing entry you must enclose the new shortcut word or phrase in double quotes to prevent the system from matching it to existing terms A keyword is a word or phrase which corresponds to several related codes or procedures Keywords are typically terms commonly used to describe a clinical entity Entering a series of keywords separated by single spaces results in all of the keywords being added to the specified code A synonym is a word entered to expand the lookup capability of an existing term or terms in the LOCAL LOOKUP file 8984 4 Synonyms would be used in cases where several words within the text of codes or procedures have the same diagnostic meaning e g CANCER and MALIGNANCY A synonym can be entered for an existing keyword or for a word in the diagnostic description or procedure e g the term CANCER might be matched to the synonyms MALIGNANCY LEUKEMIA and CARCINOMA When CANCER is referenced in th
358. es S amp OCS is combining the Kernel Toolkit documentation set with the Kernel documentation set All Kernel Toolkit content will be moved to the appropriate Kernel manual section and chapter In the Kernel Systems Management Guide the following Kernel Toolkit chapters have been added to the new Toolkit Section VI Multi Term Look Up MTLU Routine Tools Verification Tools July 1995 Kernel Systems Management Guide Revised June 2008 Version 8 0 Revision History Chan Wally Fort and Joel Ivey Technical Writer Thom Blom Oakland CA OIFO Maintenance Project Manager Jack Schram Developers Alan Chan Wally Fort Jose Garcia Joel Ivey Mike Meighan Raul Mendoza Roger Metcalf Skip Ormsby and Ba Tran Technical Writer Thom Blom Revision History Date Revision Description Author Also Changed Kernel document title references to e Kernel Developer s Guide previously known as the Kernel Programmer Manual Kernel Systems Management Guide previously known as the Kernel Systems Manual Software Version 8 0 06 10 08 5 1 Updates Oakland CA OIFO e Updated the Defining a Strong e Maintenance Project Verify Code topic Manager Jack Updated Chapter 5 File Access oon security based on the newly Developers Gary created VA FileMan Version 22 Beuschel Alan Chan and Kernel Version 8 0 File Wally Fort Jose Access Security supplemental Garcia Joel Ivey Raul
359. es and files associated with the following menus and options e VPM VAX ALPHA Capacity Management e Move Host File to Mailman e Response Time Log Options The following namespace options and routines are also removed e XUCM e XUCS e XURTL e XTCM DISK2MAIL option e XTCMXTCMFILN routine Data dictionaries and data have been deleted for the following VA FileMan compatible files e Global XUCM CM DAILY STATISTICS 8986 6 CM DISK DRIVE RAW DATA 8986 5 CM METRICS 8986 4 CM NODENAME RAW DATA 8986 5 1 CM SITE DISKDRIVES 8986 35 CM SITE NODENAMES 8986 3 CM SITE PARAMETERS 8986 095 VPM RESPONSE TIME DATA 8986 098 e Global ZRTL RESPONSE TIME 3 091 RT DATE_UCI VOL 3 092 RT RAWDATA 3 094 Data has been deleted for the following non VA FileMan compatible global e A ZRTL 3 e ZRTL RTH NOTE to System Managers The XUCM and ZRTL globals can be removed from your database after installation of this patch however please make sure no local routines access these globals before doing so VI 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 25 Multi Term Look Up MTLU Overview This chapter contains an introduction and functional description site implementation instructions for Multi Term Look Up MTLU and the option documentation Introduction to Multi Term Look Up MTLU Many medical information systems dep
360. es in the patch The server on FORUM matches the message with a patch if the sending domain is authorized on FORUM There is no longer a need for developers to manually include routine checksums either CHECK XTSUMBLD and or CHECK1 XTSUMBLD in the patch description The patch module will include the before and after CHECK1 XTSUMBLD values in the Routine Information section at the end of the patch document With changes in the National Patch Module NPM on FORUM when the patch is released the checksums for the routines are moved to the ROUTINE file 9 8 on FORUM The checksum before values will come from the FORUM ROUTINE file 9 8 and are considered the GOLD standard for released checksums The local site s Compare local national checksums report option XU CHECKSUM REPORT uses the FORUM ROUTINE file 9 8 as its source to create reports showing any routines that do not match This patch also modified the KIDS BUILD file 9 6 by adding the TRANSPORT BUILD NUMBER field 63 used to store a build number that is incremented each time a build is made This build number is added to the second line of each routine in the 7th 3 piece This makes it easy to tell if a site is running the current release during testing and afterword The leading B found in the checksum tells the code what checksum API to use Printing Loaded Transport Globals Once you have loaded transport globals from a standard distribution onto your system you can pri
361. ese LAYGO and DELETE access checks using the following variables e DLAYGO e DIDEL respectively July 1995 Kernel Systems Management Guide 5 3 Revised June 2008 Version 8 0 File Access Security When accessing data through software options File Access Security is also checked when a file is navigated to from another file 1 e READ WRITE DELETE and LAYGO access Currently there is no way for developers to override access checks when navigating to a file from another file so explicit access to files navigated to from an application option must be granted by IRM What in VA FileMan is Still Protected by the File Manager Access Code When the File Access Security system is enabled access to templates e g INPUT PRINT SORT etc is denied when using VA FileMan options if the user s DUZ Q string does not contain a matching character Similarly when editing fields via VA FileMan s Enter or Edit File Entries option DIEDIT the DUZ O matching process is invoked to permit or deny editing for protected fields The DUZ Q value is also checked by some non VA FileMan applications Finally if a user s DUZ Q is they are allowed complete access to all files Purpose for Granting File Access IRM is responsible for granting file access The needs of each user must be determined and an appropriate degree of access authority assigned Too much access may risk the security of your system while too little may inhibit productive acti
362. ess XUFPURGE XUAUDIT SHOW Attempts XUFDEV Users User Failed Access Attempts XUFDISP OLD ACCESS AND VA 200 Predefined N A Always done Purge Log of VERIFY CODES Old Access 200 XREF and Verify Codes XUSERAOLD Purge Old Access and Verify Codes Figure 3 19 Purge Log of Old Access and Verify Codes option SYSTEMS MANAGER MENU EVE User Management XUSER Purge Log of Old Access and Verify Codes XUSERAOLD The Purge Log of Old Access and Verify Codes option XUSERAOLD purges all inactive Access and Verify codes which allows for the recycling of codes Old Access and Verify codes are stored so that users cannot pick a previously used code when required to choose a new code If old codes are stored indefinitely though it may become difficult for users to invent new codes When you use this option interactively you can purge codes older than a retention period you specify from 7 to 90 days When scheduled the retention period defaults to 90 days but can be changed to anything from 30 to 90 days by putting the number of days in the TASK PARAMETERS field The log of Access codes is stored in the whole file AOLD cross reference of the NEW PERSON file 200 The log of Verify codes is stored per user in the VOLD cross reference of the NEW PERSON file July 1995 Kernel Systems Management Guide 3 29 Revised June 2008 Version 8 0 Signon Security System Management 200 not a whole file
363. et of options You are asked to enter the message used to place all options in the set out of order The option then places the message in each option s OUT OF ORDER MESSAGE field 2 Use the Remove Out Of Order Messages from a Set of Options option XQOON to enable access to an option set To toggle the status of an individual option only use the Toggle Options Protocols On and Off option XQOOTOG Out of Order Option sets are stored in the X TMP global with a purge date set for seven days in the future If you place a set of options out of order but the option set is purged from XTMP before you enable access to it you can rebuild the out of order option set using the Recover Deleted Option Set option XQOOREDO It asks you to specify the exact text of the message used to place the set of options out of order it then recreates an out of order option set containing all options currently placed out of order with the specified message NOTE Make sure the message you specify is unique to the set of options you are re enabling 7 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management You can then enable access to the rebuilt option set with the Remove Out Of Order Messages from a Set of Options option XQOON To see what sets of options have been grouped in sets on the system use the List the Defined Options Sets option XQOOSHOW To show all options and protocols currentl
364. etically by name or numerically by code e The Delete Entries from Look Up option XTLKMODPARKIis used to delete a reference file from a site s LOCAL LOOKUP file 8984 4 This option should be used as an IRM developer utility and can only be accessed by holders of the XTLKZMGR security key e The Add Entries To Look Up File option XTLKMODPARS lis used to add reference files to a site s LOCAL LOOKUP file 8984 4 This option should be used as an IRM developer utility and can only be accessed by holders of the XTLKZMGER security key In order to add entries with this option DUZ O must be set to an at sign programmer access July 1995 Kernel Systems Management Guide 25 1 Revised June 2008 Version 8 0 Multi Term Look Up MTLU e The Add Modify Utility option XTLKMODUTL is used to enter new or edit existing shortcuts keywords or synonyms to the LOCAL LOOKUP file 8984 4 as described below The Shortcuts option XTLKMODSH is used to enter new or edit existing shortcuts to the LOCAL LOOKUP file 8984 4 The Keywords option XTLKMODKY is used to enter new or edit existing keywords to the LOCAL LOOKUP file 8984 4 The Synonyms option XTLKMODSY is used to enter new or edit existing synonyms to the LOCAL LOOKUP file 8984 4 Usage Considerations MTLU provides users and developers with the ability to perform specialized lookups on database files using standard VA FileMan calls These files typically co
365. every version of a software application that a developer exports Also a software application s build entry is sent to installing sites as part of the software after an installation the site can examine the build entry to see the software definition Figure 23 4 KIDS file diagram PACKAGE file 9 4 INSTALL file 9 7 INSTALL File 9 7 The INSTALL file 9 7 stores a record of each installation a site performs The INSTALL file 9 7 allows KIDS to store a separate installation entry for each installation A new version of software no 23 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations longer overwrites the installation information of a previous version and developers installation history no longer overwrites the sites installation history The national PACKAGE file 9 4 is now static at its top level The three main items recorded in the INSTALL file 9 7 for each installation are the installing site s answers to installation questions any installation output and the installation s timing information Changes in the Role of the PACKAGE File 9 4 The PACKAGE file 9 4 still plays a role in installations with KIDS albeit a diminished one KIDS provides a link from the build entry of a package to the PACKAGE file so that developers can link a package to a PACKAGE file 9 4 entry The top level of a PACKAGE file 9 4 entry for a
366. ext Variable XQUIT encountered at option option name This means that the jump logic has encountered the variable XQUIT detected with a DATA statement This variable is usually set by an Entry Action Field 20 of the OPTION file 19 and causes the menu system to refuse to run or jump past that option This error message can be generated by both user generated jumps and phantom jumps Figure 7 20 Menu jump error message 5 of 6 x WARNING Background jump requested to option value in XQOMM J but this option does not exist on your system A VA FileMan lookup was attempted for the option set in the variable XQMM J but no such option was found in the OPTION file 19 This error message can only be generated from a phantom jump Figure 7 21 Menu jump error message 6 of 6 x WARNING Background jump requested to option option s menu text but you do not have access to this option See your computer representative This means that the target option requested by XQMM J is not in the tree of options to which this user has access that 1s the target option was neither in the user s primary menu tree nor specifically listed as a secondary menu for that user This error message can only be generated from a phantom jump REF For more information on phantom jumps please refer to the Menu Manger Developer Tools chapter in the Kernel Developer s Guide July 1995 Kernel Systems Management Gu
367. fault set of fields is required at a minimum This set is defined by the NEW PERSON IDENTIFIERS field in the KERNEL SYSTEM PARAMETERS file 8989 3 If it is NULL the default set of required fields for the NEW PERSON file 200 entries is e INITIAL 1 SEX 4 e SSN 9 If given local site policy a different set should be used IRM can use this field to specify other identifiers NOTE SSN is not required if the person entering accounts holds the XUSPF200 security key Grant Access by Profile Option The Grant Access by Profile option XUSERBLK includes features unavailable in the Add a New User to the System option XUSERNEW With the Grant Access by Profile option you can grant access to one or more people based on a typical user profile All characteristics of the typical user including menus keys and service section are copied to the new user or replace the characteristics of an existing user For new users access security forms are generated as part of the process These forms can be delivered to the service section coordinator by inter office mail and can be distributed to the new users The Grant Access by Profile option is locked with the XUMGR security key and is strictly limited for use by IRM It must be restricted because any user profile even that of a developer can be copied to another user As with the Add a New User option the SSN field 9 is required when adding new records except by holders of the XU
368. for specified date Option The Patient Alert List for specified date option XQAL PATIENT ALERT LIST is used to obtain a list of alerts for a specified patient from the ALERT TRACKING file 8992 1 for a selected date A prompt is provided to obtain a quick scan listing of dates with at least some alerts for the patient on it based on OR and DVB alerts other patient related alerts need to be identified by looking at each alert s message text and are included in the full list but not the quick scan The listing includes the following e Internal Entry Number IEN for the alert in the ALERT TRACKING file 8992 1 e Date and time the alert was generated e Message text of the alert e Information about any option or routine to be executed for processing the alert User Alerts Count Report Option The User Alerts Count Report option XQAL USER ALERTS COUNT is used to generate a report on users who have more than a specified number of alerts in the ALERT file 8992 The report covers a specified range of dates and can be sorted by any of the following data e User name e Number of alerts e Service Section In addition the report in each of these formats may be generated by Divisions if desired For each user who has the specified number of alerts or more the report includes the following e User name e Section Service for the user e Number of alerts in the ALERT file 8992 e Last signon date e Number of Critical alerts or Abnorma
369. from the Taskman Error Log all entries for an error of a specific type In fact this option uses the M contains operator therefore it removes every error whose message contains your input as a substring For example you can remove every error that occurred in a certain routine or even every error whose message contains a Q After performing the purge the option shows you how many entries were removed This option is the best way to keep the log clean As you resolve certain kinds of errors and prevent them from happening again you can remove all errors of that kind from the log This leaves behind only those errors you have not resolved helping you focus on the problems that remain Delete Error Log Option Figure 22 27 Delete Error Log option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Delete Error Log XUTM ERROR DELETE The Delete Error Log option XUTM ERROR DELETE completely deletes all errors in the Taskman Error Log If the error log is cleaned and purged as described above you will rarely need to use this option 22 26 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Troubleshooting The information given in this topic cannot be used by application developers in their code It is provided to help site managers troubleshoot problems with tas
370. from WAIT State Option sssssssoeeeessssssssoeresssssssoeersssssssseeressssssseereee 22 15 stop Task Manas cr Optom sese A ESEN E 22 16 SY NC Alas file Contre Opio iscs a e aaa sensi 22 16 Clean Task Bile OPIO ieron E 22 17 Oueviable Task Loe Clean Up Opt Omn niccisccass siete ticees e shasta 22 17 SCHEGUMINS Ol ONS eosa sevensievaealatasen Lid nakite sienna tes 22 18 WV VC Opon 10 QU IE er tastead ac tauteae dasseanedsaehaes Masi acdoa taahenedlaawaceasaoeactuestiacea 22 18 Taskman Error LoS Ment sison A 22 24 SNOW Error LO O PON see N E went 22 25 Clean Error Log Over Range Of Dates Option ececccccccccccssseeeeceeeeeeaaeeneeeeeeeeeaaaaas 22 25 Purse Error Lot Or Type Of Emor Optom srera aumseseviadeddsss 22 26 DERE al rine ol EO OPIO aasi A E A 22 26 TOUDICSHOOUNS eean E 22 2 SCHEDULE TIC ace o E E 22 27 TASKS Pilo Adhere akinesia aia as sane aoe 22 30 Task Stalls Code sxc silanes ahcnccii stacey E A EA 22 32 asic RejeEChOn MESSAGES 5 fain asec Aira tatens E E Winco els ceuce letineece ven Made netieetes 22 35 TaskMan ate WICSS ACCS assests sascha theta lee hoo ca aiecnttaerabcetncentetaalvalcn nmr tnanbedie enchant 22 36 Mo KIDS eaiwaieiiarniinen iad iain aca a V 1 23 KIDS System Management Installations cccccecceccssssseseeceeeeeeaeeeeseeceeceeauaeeseseeeeseseeaaees 23 1 July 1995 Kernel Systems Management Guide xvii Revised June 2008 Version 8 0 Contents KAD SO PtloOn cianie a sda ssoaiete evins
371. fter a crash which can cause numerous abnormal exits To prevent this problem from occurring IRM can use the Clear all users at startup option XUSER CLEAR ALL Kernel recommends this option be scheduled to run at system startup Although this option can be invoked interactively without ill effects it was designed as a background process thus it is placed along with other tasked options on the PARENT OF QUEUABLE OPTIONS menu REF For information on how to release a single user please refer to the Release User option in the User Management Options in the Operations Menu topic in this chapter Enabling and Disabling Logons IRM has full control over whether logons are enabled Access to a particular Volume Set can be disabled by setting the INHIBIT LOGONS flag in the VOLUME SET file 14 5 Setting the flag to YES sets the ZIS 14 5 LOGON volume set node whose presence disallows user logons That is logons through Signon Security invoking the ZU routine will fail terminals for user access are usually linked to ZU within the operating system setup Some special terminals like the console are untied The AMLZIS 14 5 LOGON volume set node is also checked after each cycle through the menu system signed on users will be logged off as soon as they return to a menu prompt Adding New Users Creating a new user account involves adding a record to the NEW PERSON file 200 assigning an Access code and assignin
372. ftware version number to decide which entries are the most recent When there are multiple entries for the same version number for example alpha or beta installs took place the following order of precedence is used 1 Released Version is the most recent version number contains no letters such as 8 0 2 Beta Test Version version number contains V such as 8 0V 10 3 Alpha Test Version version number contains T such as 8 0T10 Selecting Software Names for Purging After versions to retain the next prompt is Package Name You can enter a partial or full software application name You will continue to be prompted for additional software names until you simply press the lt Enter gt key without making any further entries at the Package Name prompt e Packages Software To select software entries for purging at the Package Name prompt enter a partial or full software application name You can optionally enter partial or full version numbers The list of candidates for purging will contain all entries excluding patch entries whose first characters match all characters in the software name that you specify If you enter ALL all software but not patches will be selected for purging e Patches Patches are a special case To select patch entries for purging you must enter the full namespace of the patch the full version number and an asterisk You can optionally add a partial or full patch number after the asterisk The li
373. g a primary menu You need the XUMGER security key to assign primary menu options Even the at sign programmer access is insufficient as checked by the PRIMARY MENU OPTION field s input transform Figure 3 7 User Management menu options Associated menu options when adding a new user SYSTEMS MANAGER MENU EVE User Management XUSER Add a New User to the System XUSERNEW Grant Access by Profile lt locked XUMGR gt XUSERBLK User Inquiry XUSERINQ 3 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management Add a New User to the System Option You can use the Add a New User to the System option XUSERNEW to set up user accounts one by one The option presents a standard scrolling mode editing sequence for user attributes When using this option entry of a social security number in the SSN field 9 is usually required While SSN is not required in the NEW PERSON file 200 data dictionary it is a required field when using this option If the option is used by someone who holds the XUSPF200 security key however entry of an SSN is not required You can also print security forms for the new user with this option When signing on for the first time the new user should simply press lt Enter gt at the Verify code prompt which then lets them enter their own secret Verify code NEW PERSON File 200 Required Fields When adding new users a de
374. general information including references to additional reading material CAUTION DISCLAIMER Used to caution the reader to take special notice of critical information e Descriptive text 1s presented in a proportional font as represented by this font e Conventions for displaying TEST data in this document are as follows The first three digits prefix of any Social Security Numbers SSN will begin with either 000 or 666 Patient and user names will be formatted as follows Application Name PATIENT N and Application Name USER N respectively where Application Name is defined in the Approved Application Abbreviations document and N represents the first name as a number spelled out and incremented with each new entry For example in Kernel KRN test patient and user names would be documented as follows KRNPATIENT ONE KRNPATIENT TWO KRNPATIENT THREE etc e Sample HL7 messages snapshots of computer online displays 1 e character based screen captures dialogues and computer source code are shown in a non proportional font and enclosed within a box Also included are Graphical User Interface GUI Microsoft Windows images 1 e dialogues or forms User s responses to online prompts will be boldface References to lt Enter gt within these snapshots indicate that the user should press the Enter key on the keyboard Other special keys are represented within lt gt angle brackets For example
375. gers 21 11 Standardized VA Cach and GT M 21 10 DCL Context 21 14 Batch Queues 21 20 Cache VMS 21 15 Restarting 21 18 TASKMAN Account 21 20 TASKMAN Queue 21 20 ZTMSWDCL COM 21 19 ZTMWDCL COM 21 18 Defining Environments 21 1 Delete Tasks Option 22 6 Dequeue Tasks Option 22 4 DESCRIPTION Field 22 21 DEVICE FOR QUEUED JOB OUTPUT Field 22 20 Division of Labor 20 1 Error Screens 20 6 Files 20 5 Header Page 21 13 Inspecting the Tasks in the Monitor s Lists 22 11 IO List 22 9 22 10 Job Limit 21 3 Job List 22 10 List Tasks Option 22 2 Load Balancing 21 11 Manager 20 1 20 2 Startup 21 11 Monitor Action Prompt 22 11 Multiple Managers and Load Balancing 21 11 Option Scheduling 22 18 List Background Options 22 18 One time Option Queue Option 22 24 PARENT OF QUEUABLE OPTIONS Menu 22 18 Problems 22 23 Queuing an option 22 19 Schedule Unschedule Options Option 22 19 Through the OPTION SCHEDULING File 19 2 20 2 July 1995 Kernel Systems Management Guide Index 39 Revised June 2008 Index 40 Index Which Options to Queue 22 18 Other Files 20 7 QUEUVED TO RUN AT WHAT TIME Field 22 19 22 20 22 21 QUEUED TO RUN ON VOLUME SET Field 22 20 22 22 Queuers 20 1 Queuing an Option 22 19 Queuing Output 19 1 Rejection Messages 22 35 Remove Taskman from WAIT State Option 22 15 Requeue Tasks Option 22 5 RESCHEDULE FREQUENCY Field 22 21 Restart Task Manager Option 22 14 Restarting
376. gt D ENABLE XUFILE3 gt 5 In the production account begin the conversion with XUINCON Figure 5 7 XUINCON conversion routine Sample user dialogue In VAH gt D XUINCON Version 7 of the Kernel defined a new multiple valued field in the New Person File called Accessible File This conversion will store file access in this multiple in the following manner Those Users who have a FileMan Access Code DUZ 0 which is not null i e contains some character string will have their access string matched to the protection currently on your files For each match between the file and the user the file will be listed in the user s Accessible File multiple as will the type of access dictionary delete laygo read write audit NOTE Files with no protection will NOT be assigned to any user Would you like to run the conversion now NO 6 If you are ready to run the conversion answer YES Figure 5 8 Running a conversion Sample user dialogue Would you like to run the conversion now NO YES 5602377360965 Build Table Convert Users Give access from DISV file X ref Done56237 36565 gt 7 Review the newly assigned access settings Use the File Access Security menu XUFILEACCESS Figure 5 3 located on the User Management Menu XUSER to display file access by user and by file 5 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security After the
377. gue enesssssoeeesssssssoeerrssssssseerrsssssscerrssssssseeressss 6 9 Pisure 7 1 kermel meni fee TOUS neien a E eee 7 1 Freour F Edr OPUS OPU Oese S S 7 2 Figure 7 3 Defining local primary menus IRM Sample user dialogue 2 0 0 0 ecccceeeeeeeeeeeeeeeeeees 7 2 Ficure 7 4 Auditine Menu OPlOMs ssis a adhiaacasend EE 7 4 Preure 7 5 Display Menus and Options Menu sssassaaesausesvaadsatesidauassacdasueaenaveandaataediaavanwacoadaaebentaccecas aiaa 7 5 Figure 7 6 Inquire option Sample user dialof cisn innsin EEEE 7 6 Figure 7 7 Option ACCESS Dy USE1 OpllOn si a o a a e a EES 7 6 Pieute 7 8 Delete Unrererenced Options OPO irera AS 7 8 Heure 7 9 Pix Option Pile Fonnes Opio at beabeaunecehvalmncaaeuacesyest 7 9 Figure 7 10 Fix Option File Pointers option Sample user dialOQue ccccccccccssseseseecceeeeeaeeeeeeeeeeeeees 7 9 Figure Pehle Switch IGemeities Opon sssini a N ected eaten 7 9 Figure 7 12 Out Of Order Set Management menu OPTIONS ccccceesssseeeceeeeceeeeeeseeeceeceeaseeeeeeeeeeeeeaas 7 10 Figure 7 13 Restrict Availability of Options option ssssssssssssssssseseeeeerressssssssssssssseceeereressssssssssssssseees 7 11 Pieure 7 14 Ckm old Job Nodes ti XU Tiesto nsec ce nat ca tanan och cecutdeaacaninavennthcuGosagsed cance oe usnesminasennueeegeanahense 7 12 Figtre 7215 Building primary Menu Tees OPO osise tise tered eva E yates nice od Goad deen inteass 7 13 xxii Kernel Systems Management
378. gure 8 2 Display User Characteristics option Sample output KEYS HELD XUPROG XUPROGMODE XUAUTHOR The security keys you need to carry out computing activities should be assigned by IRM when your computer account is first added to the system Other keys can be allocated at a later time by IRM or by an IRM designee e g an application coordinator with the use of the Secure Menu Delegation menu utilities July 1995 Kernel Systems Management Guide 8 1 Revised June 2008 Version 8 0 Security Keys System Management Identifying Locked Options IRM can list which security keys lock what options by using Menu Management s Diagram Menus option The following example Figure 8 3 shows that the Programmer Options menu is locked with the XUPROG security key It also shows that one of its options Programmer mode is locked with the XUPROGMODE security key Figure 8 3 Diagram Menus option Sample user dialogue Select Menu Management Option Diagram Menus Select USER U xXxXxxx or OPTION O xxXxxx name O XUPROG Programmer Options XUPROG LOCKED XUPROG PG Programmer mode XUPROGMODE x LOCKED XUPROGMODE Security keys are stored in the SECURITY KEY file 19 1 Security keys given to users are stored in the users NEW PERSON file 200 entries in the KEYS field Multiple Options are locked by a given security key when the name of that key is entered into the LOCK field 3 of the OPTION file 19 If an opt
379. hat older applications may not do this Other tasks abort with errors still others are rejected The result is that ZTSK is always growing Options are available that clean up the ZTSK global Figure 22 20 Clean Task File option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Clean Task File XUTM CLEAN In unusual circumstances you may need to clean the ZTSK global manually Kernel provides the called Queuable Task Log Clean Up option to regularly clean up the TASKS file 14 4 in the background Only rarely will you not be able to rely on the queued cleanup to perform this function However when necessary you can use the interactive Clean Task File option XUTM CLEAN First XUTM CLEAN asks you if you are sure you want to clean out the old entries from the TASKS file 14 4 If you respond that you are the option asks you how far back you want to keep old entries The default is to keep old entries going back a week and to delete the older ones After you provide this value the option queues a task to do the cleanup XUTM CLEAN cannot be queued Queuable Task Log Clean Up Option The Queuable Task Log Clean Up option XUTM QCLEAN resides on the ZTMQUEUABLE OPTIONS menu This option allows you to purge all of the entries for tasks that are no longer queued for whatever reason and to purge the Taskman Error Log It is very useful to be able to queue the
380. he user s last terminal type is still appropriate Although the difference in resource consumption is negligible the user can appreciate a split second s savings in time Thus bypassing the DA query can be acceptable if the same terminal type is always being used But if the user should sign onto another terminal type problems can occur with the presentation of screen oriented displays unless the user knows how to change the terminal type to match the actual current one If the device is non ANSI standard Signon Security may not find a DA but will continue to determine the terminal s identity by querying its answerback message All known non ANSI devices e g Qume 102 terminal should have their answerback messages programmed This is accomplished by using the terminal type setup mechanism and entering C QUME as the Qume 102 s answerback message The name must match an entry in Kernel s TERMINAL TYPE file 3 2 to take effect If the answerback message contains additional characters e g a serial number the message will not match an entry in the TERMINAL TYPE file 43 2 and will be useless for signon purposes If the terminal s DA return code does not match an entry in the DA RETURN CODES file 3 22 or if the terminal is non ANSI and cannot be programmed with an appropriate answerback message Signon Security prompts the user to identify the terminal type if the user s ASK DEVICE TYPE AT SIGN ON setting is set to ASK This is the only case
381. he Hunt Group Using a device as if it was not a member of a hunt group is possible with the use of the D flag in the Device Handler input variable ZIS REF For more information please refer to the documentation for the ZIS API in the Device Handler Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml July 1995 Kernel Systems Management Guide 18 9 Revised June 2008 Version 8 0 Special Device Issues Magtape System Management Figure 18 9 Edit Devices by Specific Types option Device Management XUTIO Edit Devices by Specific Types XUDEVEDIT Magtape Device Edit XUDEVEDITMT The Edit Devices by Specific Types option XUDEVEDIT lets you edit specific types of devices using ScreenMan Values entered in a Magtape device s SUBTYPE FORM FEED BACK SPACE MARGIN WIDTH and PAGE LENGTH fields may not be significant to a given application The value of the data entered may be arbitrary On the other hand if the application plans to copy the output to a printer the characteristics may need to be similar to that of the printer If an application intends to use these fields be cautious about the type of data that is entered When sent to the tape unit some control codes will initiate tape movement or cause tape markers to be written to the mounted tape
382. he Kernel Technical Manual Information about managing computer security which includes a detailed description of techniques that can be used to monitor and audit computing activity is presented in the Kernel Security Tools Manual Instructions for installing Kernel are provided in the Kernel Installation Guide This guide also includes information about software application management e g recommended settings for site parameters and scheduling time frames for tasked options This manual is further organized within each section of Kernel in the following order 1 User Interface Information of relevance to the general end user 2 System Management Information of relevance to system managers July 1995 Kernel Systems Management Guide XXXII Revised June 2008 Version 8 0 Orientation When a subject is large enough e g Signon Security separate chapters are devoted to the User Interface and System Management topics In other cases where the subject matter is smaller e g the discussion of the Browser device the two divisions of audience are contained entirely within a chapter or sub chapter This manual uses several methods to highlight different aspects of the material e Various symbols are used throughout the documentation to alert the reader to special information The following table gives a description of each of these symbols Table ii Documentation symbol descriptions NOTE REF Used to inform the reader of
383. he Manager starts submanagers with the JOB command instead LOAD BALANCE ROUTINE If you are running multiple Managers one per node use this field to set up load balancing between the Managers on each node It should be set to the name of an extrinsic function that returns a load rating for the node REF For more information on load balancing please refer to the Multiple TaskMan Managers and Load Balancing topic in this chapter VOLUME SET File 14 5 Figure 21 2 Volume Set Edit option SYSTEMS MANAGER MENU EVE Task Manager XUTM MGR Taskman Management Utilities XUTM UTIL Edit Taskman Parameters XUTM PARAMETER EDIT Volume Set Edit XUTM VOLUME TaskMan knows about a system s configuration from the values entered into the VOLUME SET file 14 5 using the Volume Set Edit option XUTM VOLUME The information stored in this file strongly affects TaskMan s behavior If you inaccurately describe your system you will usually notice very quickly as TaskMan begins processing tasks in a consistently incorrect way July 1995 Kernel Systems Management Guide 21 5 Revised June 2008 Version 8 0 TaskMan System Management Configuration You need to make one entry in this file for each Volume Set that tasks can be queued to or from These entries are only used when e A Manager is running on the Volume Set and must look up information about its own environment e The Volume Set is a required volume
384. he execution of a server option much like an OUT OF ORDER MESSAGE The user for all server options is the PostMaster The originator of a server request is recorded however in the return address variable DESCRIPTION 3 5 This word processing field should contain an extensive description of the server option intended for the local Site Manager and IRM staff The description should include an exact description of what the server option does and the resources it requires PRIORITY 3 8 This field determines the priority at which the server option runs TIMES DAYS PROHIBITED This multiple allows the local IRM staff to control the days and 3 91 times during which the server request is honored If data is entered that prevents the server option from being honored immediately the software determines the next available time slice that is not prohibited and queues the request for that time Server options that are marked R for Run Immediately in the SERVER ACTION field are instead queued to run at the next non prohibited time period TYPE 4 This field must always contain the code s for server type option or the request will be denied and an error will result EXIT ACTION 15 The M code stored in this field is executed just before the server option exits ENTRY ACTION 20 The M code in this field is executed if the server request is honored If as with other options the variable XQUIT exists after the Entry Actio
385. he primary data structures that TaskMan uses to schedule and run tasks TASKS File 14 4 The TASKS file 14 4 unlike the SCHEDULE file contains the tasks themselves Every task run by TaskMan is described by an entry in the TASKS file 414 4 Each entry is subscripted by a unique internal number and ZTSK 1 always equals the number of the most recently created task The lists and nodes in ZTSCH store the tasks numbers that are scheduled to run Each task s entry consists of a ZTSK task 0 node that contains most of the essential information about the task several decimal nodes 1 2 25 and 26 that store the remainder of the critical information and a number of storage nodes under ZTSK task 3 that store the names and values of parameters that TaskMan creates for the task Left unchecked this file tends to grow REF For a description of the various means of controlling this growth please refer to the TaskMan System Management Operation chapter in this manual Other Files The TASKS 14 4 and SCHEDULE files taken together describe all the information about tasks on the system A few more files are needed however to describe everything about how tasks are managed on the system The following three files are stored in ZIS e The VOLUME SET file 14 5 Describes the computer system s Volume Sets and how they are configured into TaskMan environments e The UCI ASSOCIATION file 14 6 Lists all
386. he user to be deleted at termination except security keys marked KEEP AT TERMINATE As discussed in the Security Keys chapter in this manual the application developer can export a security key with the KEEP AT TERMINATE field set to YES in such a situation The Provider security key included with Kernel has the flag set to YES for this purpose Although a user may have been deactivated it could be important to continue a processing activity that the user had authorized based on privileges associated with a security key A medical order could continue to hold an approved status for example even though the authorizing provider had been deactivated Automatically Deactivating Users Kernel s XUAUTODEACTIVATE option finds all users in the NEW PERSON file 200 with a TERMINATION DATE in the past but who still have an Access code Any such users are users that had been scheduled for termination but who were not terminated usually because the task that should have terminated them did not run XUVAUTODEACTIVATE terminates any users it finds in this category It acts as a Safety net to ensure that all users who were scheduled for termination are in fact terminated It should be regularly scheduled REF For recommended frequency of scheduling please refer to the Kernel Installation Guide Because this option is not intended for interactive use it is placed on the ZTMQUEUABLE OPTIONS menu July 1995 Kernel Systems Management Guide 3
387. her device that happens to be a member of a hunt group the Device Handler attempts to open the device If unsuccessful the Device Handler identifies the name of the associated hunt group device from the AHG whole file cross reference and proceeds as described above Hunt Group Device on Another CPU If the user sends output to a device that 1s a member of a hunt group and is located on another CPU the hunt group search will not succeed since the Device Handler only attempts to open devices that are on the local CPU If the user has queued to the device however TaskMan would have the Device Handler begin searching for a device on the local CPU If the Device Handler was unsuccessful TaskMan would send the job to the other CPU s task global to be scheduled for processing and the effort would eventually succeed Queuing to a Hunt Group Device If the user had queued to a hunt group member on the local CPU TaskMan again calls the Device Handler to search the local CPU and if the Device Handler is unable to open a device returns the job to TaskMan for processing on the local CPU The Device Handler returns POP with a non zero value IO and IO CPU destination CPU 18 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Special Device Issues NOTE At this point the job would be placed into the IO queue and thereafter be processed as if it was not a hunt group member Using a Hunt Group Device Without Using t
388. his is so that it can be distinguished from a device subtype in a call to the Device Handler Confusion could arise since either can be used as the second piece of the device specification The SPOOL DOCUMENT file 3 51 has an input transform pattern match that guards against creation of document names in the format of device subtypes How Shared Device and Terminal Type Attributes are Used The DEVICE 3 5 and TERMINAL TYPE 3 2 files share attribute fields for RIGHT MARGIN and PAGE LENGTH If a value is entered for RIGHT MARGIN or PAGE LENGTH in the DEVICE file 3 5 it will override the value from the TERMINAL TYPE file 3 2 When a user selects a device by responding to the device prompt with only the first required piece of information the device identification Device Handler retrieves parameters to characterize the device e g RIGHT MARGIN from the DEVICE file 3 5 Furthermore the Device Handler checks the ASK PARAMETERS flag for the selected device and if the flag is set prompts the user for associated parameters presenting DEVICE file 3 5 characteristics as the default For terminals and virtual terminals types TRM and VTRM respectively the user is prompted for the right margin For magtape MT Sequential Disk Processor SDP obsolete and Host File Server HFS devices they can be prompted for address parameters with the value of the OPEN PARAMETERS field in the DEVICE file 3 5 as the default REF For mo
389. his option lets you monitor or manipulate one task at a time 19 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan User Interface Selecting Tasks When you choose the TaskMan User option it first asks you to select a task with which to work TaskMan displays the Select TASK prompt If you enter a single question mark you get some general help about the option if you enter two question marks you can get a list of every task that you have queued to run Typically you would enter two question marks at this prompt so that you can get a listing of your individual tasks listed by task number You then choose a task from the list of tasks to work with Using the TaskMan User option looks like the following Figure 19 3 TaskMan User option Sample user dialogue Select User s Toolbox Option TaskMan User Select TASK 2 Please wait while I find your tasks searching finished Task 161325 ZTSK2 XMA02 Queued print for KRNUSER TWELVE Device VERSLW KRN KDE From TODAY at 14 22 By you Scheduled for TODAY at 20 00 Task 161776 ZATSK DIP4 DEVICE LIST Device VERSLW KRN KDE From TODAY at 14 22 By you Scheduled for TODAY at 22 00 End of listing Press RETURN to continue lt Enter gt Select TASK 161776 lt Enter gt DEVICE LIST Taskman User Option Display status Stop task Edit task Print task List own tasks Select another task Select Action Task 161776
390. hole entities If dissection appears necessary the Internal Relations section of the software documentation should be consulted before rearranging any of the items Delete Unreferenced Options Option Figure 7 8 Delete Unreferenced Options option Programmer Options lt locked KUPROG gt XUPROG Delete Unreferenced Options XO UNREF D OPTIONS All options for interactive use not designed exclusively as queuable tasks should normally be tied to a menu that is used as a primary menu or at least as a secondary menu Standalone options that have no parents and are not menu type options should be reviewed They may be obsolete software options or local test options and could be candidates for deletion Use the Delete Unreferenced Options option XQ UNREF D OPTIONS to delete unreferenced options It can be used to cycle through the entire OPTION file 19 and delete non menu options that are not referenced by other options Deletion should obviously be done with care Use of this option is limited to those who hold the XUPROG security key 7 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Fix Option File Pointers Option Figure 7 9 Fix Option File Pointers option Menu Management XUMAINT Fix Option File Pointers XOOPTFIX After performing maintenance work on the OPTION file 19 e g deleting obsolete options that may have been items on a
391. hose used for actions like carriage return line feed and form feed are passed on to the printer e Printer Controller Mode a k a Transparent Print Mode When Printer Controller Mode is on output is only printed on the printer nothing is displayed on the terminal All escape sequences and control characters are passed to the printer This mode is preferable to Auto Print Mode especially when compressed mode printing is desired July 1995 Kernel Systems Management Guide 18 15 Revised June 2008 Version 8 0 Special Device Issues The following are the escape sequences used to toggle the slaved printing modes for DEC VT220 VT320 terminals Table 18 1 Escape sequences used to toggle the slaved printing modes for DEC VT220 V1T320 terminals Auto print mode on ESC 5i Auto print mode off ESC 4i Printer controller mode on ESC 5i Printer controller mode off ESC 4i Device and Terminal Type File Entries To use a slaved printer through the Device Handler two DEVICE file 3 5 entries along with corresponding TERMINAL TYPE file 3 2 entries must be made for the following e Home Device e Slaved Printer One pair of DEVICE TERMINAL TYPE entries is needed to describe the home 1 e CRT terminal attributes including the codes to open and close the printer port The OPEN PRINTER PORT and CLOSE PRINTER PORT fields of the TERMINAL TYPE file 3 2 can be used to store the appropriate codes Another pair of DEVICE TERMINAL
392. hould be set to Local report NOTE As of Kernel Patch XU 8 0 369 the integrity checking CHECK1 XTSUMBLD API supports the Compare local national checksums report option XU CHECKSUM REPORT 26 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Routine Tools NOTE As of Kernel Patch XU 8 0 393 KIDS was modified to send a message to a server on FORUM when a KIDS build is sent to a Host File Server HFS device This message contains the checksums for the routines in the patch The server on FORUM matches the message with a patch if the sending domain is authorized on FORUM There is no longer a need for developers to manually include routine checksums either CHECK XTSUMBLD and or CHECK1 XTSUMBLD in the patch description The patch module will include the before and after CHECK1 XTSUMBLD values in the Routine Information section at the end of the patch document With changes in the National Patch Module NPM on FORUM when the patch is released the checksums for the routines are moved to the ROUTINE file 9 8 on FORUM The checksum before values will come from the FORUM ROUTINE file 9 8 and are considered the GOLD standard for released checksums The local site s Compare local national checksums report option XU CHECKSUM REPORT uses the FORUM ROUTINE file 9 8 as its source to create reports showing any routines that do not match This patch also modified the KIDS BUILD file 9 6 by adding the TRANS
393. ication data server configuration As of Kernel Patch XU 8 0 440 support was added to allow the Device Handler to work in this mixed operating system OS environment The following fields were added to the KERNEL SYSTEM PARAMETERS file 8989 3 to provide this support e MIXED OS field 05 Makes OpenVMS the primary system and a non VMS system the secondary system e SECONDARY HFS DIRECTORY 320 2 Kernel Patch XU 8 0 440 updated the Enter Edit Kernel Site Parameters option XUSITEPARM screen 3 shows these added fields 15 2 Support added to allow the Device Handler to work in a mixed operating system OS environment updating the MIXED OS 05 and SECONDARY HFS DIRECTORY 320 2 fields Kernel Site Parameter edit DOMAIN NXT KERNEL FO OAKLAND MED VA GOV MAX SPOOL LINES PER USER 99999 MAX SPOOL DOCUMENTS PER USER 99 MAX SPOOL DOCUMENT LIFE SPAN 60 MIXED OS VMS Linux DEFAULT DIRECTORY FOR HFS USERS TEMP SECONDARY HFS DIRECTORY var tmp DNS Le 10 3 909 10 10 9421 4 NEW PERSON IDENTIFIERS July 1995 Kernel Systems Management Guide 15 5 Revised June 2008 Version 8 0 Device Handler System Management Kernel Patch XU 8 0 440 also included the addition of the SECONDARY I field 52 in the DEVICE file 3 5 The following example shows an HFS device using the Host File Server Device Edit option XUDEVEDITHEFS to update Field 52 15 3 Sample user dialogue updating the SECONDARY I field 52
394. ide 7 15 Revised June 2008 Version 8 0 Menu Manager System Management AXUTL Global Structure and Function The XUTL global is an account specific global It should exist in each production account on your system This global is created primarily from information in the OPTION file DIC 19 and is therefore sometimes referred to as the compiled menu system SX UTL is divided into three main sections e User Stacks AUTAT ed XUTL XQT J MENU templates only e Display Nodes AXUTL XQO ien e Jump Nodes AXUTL XQO P _ien User Stacks User stacks are stored in nodes in XUTL XQ J and XUTL XQT J The example illustrated in Figure 7 22 shows a typical user stack In this case the J is 541065826 The XQ nodes can be divided into meaningful sets according to what is contained in the third subscript The numeric third subscripts begin with the zero node which is set to the date and time in VA FileMan format by the program XUS1 when the user logs on or XUCI when the user is changing UCIs The other numeric third subscripts in this case the numbers to 3 reflect the user s progression through the menu system Each time a new option is invoked a new node is created which contains the option number concatenated with a P the number of the option whose compiled menu tree contains the current option a caret and the zero node of the OPTION file 19 for that option A different format is
395. ie mstalaions ses sue sii vhs ctl tavesieuh telah Mahe tcctle Svartih det tee duad 23 16 W hen the Installation 16 OUCUCG say cuctsviay atraciovins aati ascioust a a Aa 23 17 Re answering Installation Questions sssseeessessssooeeessssssseerrssssssseceeresssssecerrssssssseeeeeess 23 17 Information Stored in the INSTALL File 9 7 eseesseseeseeeseseresreresesseesserereseeseseseees 23 17 Answering Installation Questions for a Distribution 0 0 0 0 eee ceccceccceeeeseeeeeeeeeeeeeeeeeeeees 23 18 Instala non PrO chs meee necretee E en nan E eens Use en Aire ee enone 23 19 Once the Tnstall aun FImisMes sses a 23 19 Restartins Aborted Installations seinien e R en ieee Eiaa E 23 20 Recovering from an Aborted Distribution Load cc cccccccssssscsssseeseseeeeeeeeeeeeeeeeeaaas 23 20 Installing Global DistrilbWUOns Aaecnir a akcnnte teases a a ie neeusaetacseaeaceom 23 21 P re me the B UWE Dean INSTALL FIle Sini ea a e rs 23 21 el VAY Cla CAC INO goer shout a E E a 23 23 24 KIDS System Management Utilittes 00 0 ccccccccccccesnsseeseececceecaeeesseeceeceeseaeeseeceeseeeeeeees 24 1 Bele PD ODIO ayanettat hoatica tee ectetadia T beatea nena ade hame date 24 2 stahl Pie Partin OOM eenean E 24 3 Convert Loaded Package for Redistribution Option ccccssssseeececceeeeeeeeeeeeeaaasaeeeseeseeees 24 4 Display Patches Tor a Package ptlom ss acc satvecdsataasacaveawscdeaseceasd a E 24 7 xviii Kernel Systems Management
396. ieren ek Src cinch sisal cee Sel nea uiah aed a 22 2 Figure 22 2 List Tasks option submenu OPTIONS ccccccccesseeseececccceeaeeseeececeeeeasaeseeeceeeessaaaaeseeeeeeeaeas 22 2 Figure 22 3 All your tasks suboption Sample of TaskMan tasks running cc eeeeeeeeeeeeeeeeeeeeees 22 3 Fissure 22 4 Dequeue Tasks Optoma tceiaccoctesaseniusiecsniteanaes a O 22 4 Poore 22 NCCC Ue Tasks OPUIOM i in5 55545 saab dasavahbdaayoal inaceatt A tanh osaceadoasasaatecsaceatiaceernte 22 5 Pisure2 7 0 Delete Pasks Op louie i cisssccasteeasaes E eet ae ee acae ee aaa 22 6 Frente 22 7 Cleqnup ask Is Optom axcte sneha scahacercche iastacnsatentede cia a ane Naecene Saasease elt 22 6 Figure 22 8 Monitor Taskinan Opon eenean a che eet aaelidooeactiaeted vena che eon hoon aie 22 7 Figure 22 9 Sample Monitor TaskMan screen cccccceeeececccccccceceneaaeeeeeseeeeeeceeceeeeeeeeeeeaeaaaeeeeeeeeeees 22 8 Piore 22 10 Task Man iOmirOr da ChOns ares sencincgntaiaess noedeattlasehcnriocuetiaacee hs score are soem Medan 22 11 Figure 22 11 Options for inspecting tasks in the TaskMan Monitor s Lists ccccessesseeeeeeeeeeeeeeees 22 11 Figure 22 12 Check Taskman s Environment options sisena a AE EE AEA 22 13 Figure 22 13 Check TaskMan s Environment option First SCTeeM ccccceeeeececceeeeeeeeeeeeeeseeeeeees 22 13 Figure 22 14 Check TaskMan s Environment option Second screen cceeeeeeeceeceeeeeeeeeeeeeeeeeeee
397. if the depth of the secondary menu trees is confined ALWAYS SHOW SECONDARIES Field You can set the ALWAYS SHOW SECONDARIES field in a user s NEW PERSON file 200 entry If set to YES for a user that user will always have their secondary and common options listed when options on their primary menu are listed which occurs either by the user entering two question marks at the Select menu prompt or when AUTO MENU is turned on Redefining the Common Menu All users automatically have access to the options on the Common menu XUCOMMAND by virtue of the menu system s design As described earlier entering two question marks at any select prompt will display the Common menu The only way to deny access to a particular user is to lock the Common menu option with a reverse key and then allocate the security key to the same user July 1995 Kernel Systems Management Guide 7 7 Revised June 2008 Version 8 0 Menu Manager System Management REF For more information on security keys please refer to the Security Keys chapter in this manual The items on the Common menu can be left as they are distributed by Kernel or modified locally as desired For example an item can be added to display online help about local computer access policies This is accomplished by using Edit options to edit the XUCOMMAND menu option The Item multiple lists the existing menu choices other locally namespaced options can be added If options
398. ific Direct Mode Utility 28 1 A4 RR Direct Mode Utility 26 8 A RS Direct Mode Utility 26 8 A Z Direct Mode Utility 26 5 A Z Editor 26 5 28 3 28 5 User Interface 28 3 Z Global 28 3 A ZTER Direct Mode Utility 27 4 A oZTPP Direct Mode Utility 26 6 A ZTRDEL Direct Mode Utility 26 8 XINDEX Direct Mode Utility 26 3 XTER Direct Mode Utility 13 6 27 4 XTERPUR 27 4 XTERPUR Direct Mode Utility 13 5 27 4 XTFCE Direct Mode Utility 26 5 XTFCR Direct Mode Utility 26 5 SXTLKDICL Routine 25 2 25 22 XTLKWIC Routine 25 20 XTRCMP Direct Mode Utility 26 7 XTRGRPE Direct Mode Utility 26 5 XTVCHG Direct Mode Utility 26 6 AXTVNUM Direct Mode Utility 26 6 XUP Direct Mode Utility 27 4 NZTEDIT Direct Mode Utility 28 3 ZTMON Direct Mode Utility 22 11 A Abnormal Signoff and Error Handling 2 6 Abort KIDS Installations 23 20 Recovering From KIDS Installations 23 20 Restarting Aborted KIDS Installations 23 20 ACCESS CODE Field 3 19 Access Codes 1 1 2 1 2 2 2 3 2 4 2 5 2 6 3 1 3 2 3 6 3 10 3 17 3 18 3 19 3 24 3 25 3 26 3 28 3 29 3 30 5 9 5 13 11 9 15 8 Assigning 3 8 Log 3 29 Old 3 29 Purging 3 29 ACCESSIBLE FILE Multiple Field 32 5 1 5 3 5 8 5 10 5 11 5 12 5 13 Acronyms Home Page Web Address Glossary 6 Acting as a Delegate User Interface 9 2 ACTION Menu 28 5 Action Prompt Monitor Taskman 22 11 Actions USE AS LINK FOR MENU ITEMS 23 8
399. ify code These codes identify you to the computer system and as these codes are private to you serve to prevent unauthorized access to your account You are shielded from most steps in the signon process In the background Kernel s Signon Security establishes the proper environment records and monitors the signon event and takes you to Menu Manager Menu Manager presents a list of menu options that let you interact with other parts of Kernel and software applications When you complete a session on the computer system you sign out to exit Signing On To authenticate yourself to VistA Kernel s front door you need to sign onto the system by entering your Access and Verify codes The user signon authentication interface varies based on the type of Vista application software being run e Character User Interface CHUI based applications tThis includes M based roll and scroll applications used to access Kernel on the VistA M Server e g Laboratory Pharmacy With this type of authentication interface users are first prompted with an ACCESS CODE prompt Entering an Access code and pressing the lt Enter gt key brings up the VERIFY CODE prompt REF For a sample of the roll and scroll signon prompts please see Figure 2 1 below e Graphical User GUI client server applications This includes rich client and or client server applications used to access Kernel on the VistA M Server via RPC Broker Delphi Pascal or VistALi
400. ilities menu XTMENU The options are described in the same order as they appear on the screen Figure 25 1 Multi Term Lookup Main Menu options Application VisshteTes sas XTMENU Multi Term Lookup Main Menu XTLKUSER2 Multi Term Lookup MTLU XTLKLKUP Pate UCLELCY XTLKPRTUTL Utilities for MTLU lt Locked with XTLKZMGR gt XT LRKUTILITIES Delete Entries From Look up lt Locked with XTLKZMGR gt XTLKMODPARK ST Add Entries To Look Up File lt Locked with XTLKZMGR gt XTLKMODPARS Add Modify Utility XTLKMODUTL Most MTLU options are described using the following methods e Introduction A detailed description of the option is given The introduction usually contains any necessary special instructions e Process Chart The step by step flow of the option is illustrated showing the various choices allowed at each prompt e Examples In most cases there is an example of what might appear on the screen when using the particular option If the option produces a hardcopy output an example of the output is usually given The phrase You will be prompted for a device at this step appears in the process chart when a device is asked for A Standard Device Chart is shown on the next page It provides assistance in answering prompts related to device selection July 1995 Kernel Systems Management Guide 25 3 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The MTLU Process Charts do not co
401. ility to edit the ACCESS CODE field as well FILE MANAGER ACCESS CODE The FILE MANAGER ACCESS CODE e FILE MANAGER ACCESS CODE field 3 in the NEW PERSON file 200 is stored in the local variable DUZ O If DUZ 0 the user is a developer with the highest level of programmer access authority Other non reserved symbols can be assigned for File Access Security depending on the user s needs Software applications will indicate which symbols are needed for site specific File Access Security NOTE In previous documentation and data dictionaries it has been implied that the pound sign symbol character was reserved for File Access Security for IRM however this is not true It has merely been used as a convention If the File Access Security conversion has been run the FILE MANAGER ACCESS CODE 1s not used to control file level access security as it was before the conversion The File Access Security system formerly known as Part 3 of the Kernel installation permits the association of a user with a file whereby explicit access can be granted While the conversion process is somewhat involved the benefits resulting from implementing the File Access Security system are worthwhile July 1995 Kernel Systems Management Guide 3 19 Revised June 2008 Version 8 0 Signon Security System Management Even after running the file access conversion the FILE MANAGER ACCESS CODE field continues to serve several functions e Ifa user has be
402. in X TMP at subscript namespace lacking a header node at namespace Q or with a purge date in the header node less than the purge date determined by the purge routine is KILLed Finally the purge routine goes through the signon nodes stored at XUSEC 0 CUR DUZ DATE Any nodes older than the purge date are KILLed The XQ XUTL J NODES option should be queued to run on a regular basis If separate copies of SXUTL are maintained on different CPUs separate entries should be made in the OPTION SCHEDULING file for each CPU so that a separate job will purge each CPU s XUTL global Because this option deletes any user stacks that are time stamped with a date earlier than the purge date determined by this option seven days you need to take care how frequently you schedule it in the unusual event of a seven day long job this option should obviously not be run Rebuilding Primary Menu Trees Figure 7 15 Building primary menu trees options PARENT OF QUBRUABLE OPTIONS ZTMQUEUABLE OPTIONS Non interactive Build Primary Menu Trees XOBUILLDTREEQUE Menu Management XUMAINT Build Primary Menu Trees XOBUILDTREE The menu system uses local menu trees to process requests When changes are made to the menu structure the local menu trees are rebuilt a process also known as microsurgery If a user attempts an Up arrow Jump when the local trees need to be rebuilt or are being rebuilt a message is issued about quick access b
403. in which the terminal type prompt is asked during signon The last terminal type used will be presented as the default it is stored in the NEW PERSON file 200 If ASK DEVICE TYPE AT SIGN ON is set to DON T ASK Signon Security assumes that the last terminal type is appropriate and does not prompt the user for validation Display Attributes DA Return Codes The DA RETURN CODES file 3 22 is used to equate DA return codes to entries in the TERMINAL TYPE file 3 2 You can use the DA Return Code Edit option to automate the population of the DA RETURN CODES file 43 22 July 1995 Kernel Systems Management Guide 3 5 Revised June 2008 Version 8 0 Signon Security System Management REF For more information please refer to the Display Attributes DA Return Codes topic in the Device Handler System Management chapter in this manual SELECTABLE AT SIGNON IRM can also control which devices can be selected at signon with a field in the TERMINAL TYPE file 3 2 The SELECTABLE AT SIGN ON flag should be set to YES for all devices commonly used for sign on Ordinarily it should not be set for printers e g P terminal types P DEC or P OTHER To allow the loading of ScreenMan forms and proper functioning of other screen oriented displays the flag should also not be set for PK types that is printers with keyboards This is not an actual restriction however but a recommendation LIFETIME OF VERIFY CODE To insure that users ch
404. ing Submanagers until the number of processes falls back below this number This number should be slightly lower than the MAX SIGNON ALLOWED field of the VOLUME SET field Multiple in the KERNEL SYSTEM PARAMETERS file 8989 3 so that the system manager still has room to sign on when TaskMan is using its greatest number of partitions July 1995 Kernel Systems Management Guide 21 3 Revised June 2008 Version 8 0 TaskMan System Management Configuration TASKMAN HANG BETWEEN NEW JOBS The TASKMAN HANG BETWEEN NEW JOBS field sets a delay between the creation of new submanagers in seconds It is useful as a throttle For systems this delay spaces out the use of the JOB command to avoid slowing users response time when the Manager needs to JOB off many new processes in rapid succession For systems that create new processes cheaply this delay is unnecessary This delay also becomes less important when a high Submanager retention time is used since higher retention times reduce the likelihood that TaskMan will need to create new processes Be sure not to combine a high TASKMAN HANG BETWEEN NEW JOBS value with a low SUBMANAGER RETENTION TIME value since that increases the number of jobs per day TaskMan has to start and can cause busy systems to fall behind The number should be the lowest value that prevents the problem and can be left blank for systems with efficient JOB commands MODE OF TASKMAN The MODE OF TASKMAN field determines how
405. ing Project RM OTH MT SDP SPL BAR HFS V HG RES Hunt Groups are groups of devices that share a purpose for printing common reports Printers in the same Hunt Group are usually expected to be in the same general proximity Reports can be directed to a Hunt Group or to one of its members If a member is not This listing of the device type descriptions can also be obtained by entering two question marks at the TYPE field while editing a device July 1995 Kernel Systems Management Guide 15 3 Revised June 2008 Version 8 0 Device Handler System Management SUBTYPE Use this field to select a default terminal type for the device REF For a discussion of the TERMINAL TYPE file 3 2 please refer to the TERMINAL TYPE File 3 2 topic in this chapter SIGN ON SYSTEM DEVICE If set to YES this field identifies that this entry is the primary device among those device entries that have the same I with the same VOLUME SET CPU Among those device entries that have a common I and CPU only one of these entries can have this field set to YES If none of the common device entries is set to YES the default device will be identified by the first device on the CPU cross reference The default device is used when the Device Handler is invoked with I as the device to be selected QUEUING You can control the degree of queuing allowed for a device with the QUEUING field The following settings control queuing for a device
406. ing signon devices on a specific CPU Sample user dialogue Select DEVICE NAME SYS BBB To display all signon devices whose I begins with _TNA you could do Figure 15 10 Displaying signon devices with a specific I Sample user dialogue Select DEVICE NAME SYS _TNA The following global listing shows the cross references for a device with a I value of 99 and an internal entry number IEN of 251 It is a Sign On System Device and has a VOLUME SET CPU value of AAA Figure 15 11 Global listing for device cross references I value 99 and IEN 251 ASTUS ly GNP SYS ARAL 99 251 Sn NETS Ly CP TAAA OO OO SN ie Ti or alee Se a 2 ke we July 1995 Kernel Systems Management Guide 15 13 Revised June 2008 Version 8 0 Device Handler System Management If this device is a virtual terminal with a I of _TNA and established as a Sign On System Device but not given a VOLUME SET CPU value the cross reference structure would be as follows Figure 15 12 Global listing for virtual terminal device cross references I value TNA and IEN 251 Me TS Tg Met May St a NAYS DOL a OBZ TS Lg CPU Ns Ns SINAN 251 ee DG Te loge Gg _TNA 251 H 15 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 16 Host Files User Interface Host File Server HFS devices allow you to send output to a file maintained by your computer s operating system rather than to a printer You can send your
407. inked to a user who has an Access and Verify code and is not terminated This server option has no routine associated with it in the ROUTINE field of the remote site s OPTION file 19 The routine routine name is not on the The routine that is named in the ROUTINE field of There is no server action code for this option the OPTION file 19 is not found on the system It has been removed or is in another UCI The required server option action code in field 221 of the OPTION file 19 is blank July 1995 Kernel Systems Management Guide 11 9 Revised June 2008 Version 8 0 Server Options 11 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 12 Help Processor User Interface Kernel s Help Processor is a utility for displaying help frames A help frame is a screen of text that explains some part of a software application Each individual help frame can have keyword links to other help frames Using these keywords you can navigate through a series of related help frames to learn more about each help frame topic Some places where you may encounter help frames are e When requesting help on options in the menu system e When requesting help on a menu in the menu system e Asa standalone option describing some part of a software application Figure 12 1 Help frame example USING THE Help Processor OPTION The Help processor is a frame oriented display system which allows users and
408. int job Sample user dialogue 1 of 2 08 14 3 Figure 14 8 Specifying a device and queuing a print job Sample user dialogue 2 of 2 00 14 4 Figure 14 9 Queuing a print job Sample user dialogue ccc cccccccceesssesseccceeceeeeeeeeeceeseeeaueeeeeeeeeeeenes 14 4 Figure 14 10 Terminal type device entry Without pauses ccccccccssseeeeececeeceaaeeeeeeeceeeesaaeseeseeeeseeenes 14 4 Figure 14 11 Terminal type device entry With pauses cccccccccccccccsssesseeceeecesaeeeseeceeeeeeaaeeseeeeeeeeeas 14 5 Figure 14 12 Partial Device specification Unknown SubtyPe cc ceeeesescccccceeeeeseseeeceeeseesaeeeeeeeeeess 14 5 Figure 14 13 Device specification Four semicolon piece Sample ccceeeeeeeeeeeeeeeeeeeeeeeeeeeeens 14 5 Figure 14 14 Device specification Four semicolon piece SyNtaXx ccccceeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeees 14 5 Figure 14 15 Device syntax Specifying a spool document name Sample formats 1 of 2 14 6 Figure 14 16 Device syntax Specifying a spool document name Sample formats 2 of 2 8 14 6 Figure 14 17 Specifying a device Using alternate SyMtax cc eesessssesseseeeeceeceeceeeeeeeeeeeeaaeeeeeseeeeeees 14 7 Brie k TS V1 CSSA b Op UO Gass ce Seat wa gS sa a acai sa cee wave rs ea a a cen Reese 15 2 15 2 Support added to allow the Device Handler to work in a mixed operating system OS env
409. ion 22 0 Enter or Edit File Entries Print File Entries Search File Entries Modify File Attributes Inquire to File Entries Utility Functions Data Dictionary Utilities Transfer Entries Other Options Select VA FileMan Option TRANSFER ENTRIES Select TRANSFER OPTION TRANSFER FILE ENTRIES INPUT TO WHAT FILE HELP FRAME HELP FRAME lt Enter gt 562 entries TRANSFER FROM FILE HELP FRAME lt Enter gt TRANSFER DATA INTO WHICH HELP FRAME ISC COMMPUTER ACCESS Not a known package or a local namespace No Y Yes HELP FRAME NUMBER 742 lt Enter gt HELP FRAME HEADER Computer Access TRANSFER FROM HELP FRAME XUSER COMPUTER ACCOUNT lt Enter gt Batch user access document Are you adding ISC COMMPUTER ACCESS as a new HELP FRAME the 563RD July 1995 Kernel Systems Management Guide Revised June 2008 Version 8 0 Signon Security System Management WANT TO DELETE THIS ENTRY AFTER IT S TRANSFERRED No lt Enter gt No SORRY LET ME THINK ABOUT THAT A MOMENT SINCE THE TRANSFERRED ENTRY MAY HAVE BEEN POINTED TO BY ENTRIES IN THE HELP FRAME FELE ECs y DO YOU WANT THOSE POINTERS UPDATED WHICH COULD TAKE QUITE A WHILE No lt Enter gt No Enter or Edit File Entries Print File Entries Search File Entries Modify File Attributes Inquire to File Entries Util Cy Puncrions Data Dictionary Utilities Transfer Entries Other Options Select VA FileMan Option ENTER OR EDIT FILE ENTRI
410. ion Resource Management IRM staff end users Automated Data Processing Application Coordinators ADPACs and application developers This manual assumes that the reader is familiar with the computing environment of the VA s Veterans Health Information Systems and Technology Architecture VistA and understands VA FileMan data structures and terminology Some understanding of the M programming language is helpful for some parts of the manual No attempt is made to explain how the overall VistA programming system is integrated and maintained such methods and procedures are documented elsewhere This manual does however provide an explanation of Kernel utilities describing how they can be used to establish a standard user interface monitor and manage the computer system customize the environment according to local site needs and define new areas of computing activities for users Kernel is a vendor independent applications development environment as well as a run time environment providing standard vendor independent services to applications software It is not an operating system but a set of utilities and associated files that are executed in an M environment Kernel is central to VA VistA software strategy in that it permits any VistA software application to run without modification on any hardware software platform that supports American National Standards Institute ANSI Standard M All operating system specific M implementation specific
411. ion is locked users need to be given the security key in order to invoke the option Key Management Keys are defined and allocated to users with options on the Key Management menu Figure 8 4 Key Management menu options SYSTEMS MANAGER MENU EVE Menu Management XUMAINT Key Management XUKEYMGMT Allocation of Security Keys XUKEYALL De allocation of Security Keys XUKEYDEALL Enter Edit of Security Keys XUKEYEDIT All keys a user needs XQLOCK1 Change user s allocated keys to delegated keys XQKEYALTODEL Keys for a given menu tree XQLOCK2 Delegate keys XQKEYDEL List users holding a certain key XOSHOKEY Remove delegated Keys XOKEYRDEL Show the keys of a particular user XOLESTKEY 8 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Security Keys Allocating and De allocating Security Keys The main option to assign security keys to a user or users is the Allocation of Security Keys option XUKEY ALL Allocating a security key to a user lets them invoke options that are locked with the key For options with reverse locks allocating the security key locks the user out from the option In either case allocating the key to a user does not allow the user to give the key to anyone else To remove a security key from a user use the De allocation of Security Keys option XUKEYDEALL Unless you have been delegated a security key the only way you can allocate or de allocate key
412. ion of Kernel and the functionality contained in Kernel V 8 0 However no attempt is made to explain how the overall VistA programming system is integrated and maintained Such methods and procedures are documented elsewhere We suggest you look at the various VA Internet and Intranet Web pages for a general orientation to VistA For example go to the Veterans Health Administration VHA Office of Information and Technology OI amp T Veteran Health Information Technology VHIT Portfolio VistA Development Home Page at the following Intranet Web address http vista med va gov Reference Materials Readers who wish to learn more about Kernel should consult the following Kernel Release Notes Kernel Installation Guide Kernel Systems Management Guide this manual Kernel Developer s Guide Kernel Technical Manual Kernel Security Tools Manual Kernel Home Page at the following Web address http vista med va gov kernel index asp This site contains other information and provides links to additional documentation If the reader is not already familiar with VA FileMan or MailMan the respective user developer and technical manuals for each should be obtained and reviewed Other source documents describing overall VistA policy are XXXVI VA Programming Standards and Conventions SAC MIRMO OIFO Operations Document Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Orientation VistA documentation is m
413. ions The Merge Shell was originally developed by Indian Health Service IHS to support their Multi Facility Integration Project i REF The Duplicate Record Merge Patient Merge documentation is made available online in both Microsoft Word DOC and Adobe Acrobat PDF formats It can be downloaded from the VHA Software Document Library VDL at the following Web address http www va gov vdl application asp appid 2 e Capacity Management The Kernel Toolkit Capacity Management documentation is superseded by the following software documentation Capacity Management CM Tools Version 2 0 Resource Usage Monitor RUM Version 2 0 Statistical Analysis of Global Growth SAGG Version 1 8 VI 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Toolkit REF The Capacity Management related documentation is made available online in both Microsoft Word DOC and Adobe Acrobat PDF formats It can be downloaded from the VHA Software Document Library VDL at the following Web address e Capacity Management CM Tools http www va gov vdl application asp appid 129 e Resource Usage Monitor RUM http www va gov vdl application asp appid 130 e Statistical Analysis of Global Growth SAGG http www va gov vdl application asp appid 1 15 July 1995 Kernel Systems Management Guide VI 3 Revised June 2008 Version 8 0 Toolkit i NOTE Kernel Toolkit Patch XT 7 3 102 removed all options routin
414. ironment updating the MIXED OS 05 and SECONDARY HFS DIRECTORY 320 2 fields 15 5 15 3 Sample user dialogue updating the SECONDARY I field 52 HES device ccccccceeeees 15 6 15 4 Sample user dialogue updating the SECONDARY I field 452 NULL device c ceee 15 6 HFS oes yi 8 eu a o 24 EEE E pene peteeeeT nn E ENE E SEA 15 7 XXIV Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Figures and Tables Figure 15 6 Terminal type edit Options sisari a a teas aa tale ects teeny 15 8 Freure 1527 DA Return Code Edit OptiOm scans pcs seers a aaa aa ii oases 15 11 Figure 15 8 Device management Troubleshooting Options ssseeseeseeeeeeeeeeeeeeeeeaaaeaeaaaeeeeeeeeeees 15 12 Figure 15 9 Displaying signon devices on a specific CPU Sample user dialogue 000000 15 13 Figure 15 10 Displaying signon devices with a specific I Sample user dialogue cccceceeee 15 13 Figure 15 11 Global listing for device cross references I value 99 and IEN 251 eee 15 13 Figure 15 12 Global listing for vitural terminal device cross references I value _TNA and ENEZ ge aera eed E ee 15 14 Figure 16 1 Choosing a Host File Server HFS device Sample user dialogue ceeeeeeeeeeeeeeeees 16 1 Figure 16 2 Host File Server Device Edit Option sucses urnan e a aaia 16 2 Figure 16 3 Host File Server device for Cach and GT M Sample
415. is also a good way to store the results of a time consuming calculation e g a complex VA FileMan report By queuing to the spooler a report involving intensive processing can be done at night when the system is relatively free Output can then be printed during the day when the printer can be attended Finally when using the spooler report processing can run to completion without printer problems interfering Sending Output to the Spooler If you have been given the authority to spool you can send output to the spooler by responding to the DEVICE prompt with the name of the spool device Devices used for spooling are commonly named SPOOL or SPOOLER If you do not have spooling privileges and you try to use the spool device the spooler issues a message that authority has not been granted as below Figure 17 1 Unable to send output to a spool device Sample message DEVICE SPOOL You aren t an authorized SPOOLER user To send output to the spooler with a customized right margin of 96 and page length of 66 you can use the following syntax Figure 17 2 Specifying spooled output margin and length DEVICE SPOOL 96 66 July 1995 Kernel Systems Management Guide 17 1 Revised June 2008 Version 8 0 Spooling After requesting the spool device you are usually prompted for a spool document name as shown below Figure 17 3 The prompt is not issued however if the spool device has been set up to generate the spool document
416. is automatic formatting is an advantage when printing spool documents it is a disadvantage when creating a mail message Page breaks will not be inserted when indicating a page length of 99999 lines or a number greater than the document s total So when you know your spool document will end up as a MailMan message a suitable margin and page length request might be Figure 17 9 Formatting Sending a document to a spool device to print as a MailMan message Sample user dialogue DEVICE SPOOL 75 99999 To turn the spool document into a MailMan message once your spool document completes go to the Spooler Menu and select the appropriate option as illustrated below Figure 17 10 Make spool document into a mail message option Select Primary Menu Option Spooler Menu Select Spooler Menu Option Make spool document into a mail message If the number of lines in the document exceeds 500 you are asked whether the transfer process should be queued This prompt is provided for the your convenience since queuing of a time consuming process 1s usually preferred After using the option you can find your messages by reviewing recently delivered mail in your IN basket July 1995 Kernel Systems Management Guide 17 5 Revised June 2008 Version 8 0 Spooling System Management Spool Document Storage Spool document identification is stored in the SPOOL DOCUMENT file 3 51 in the XMB global This file is for internal use by Kernel s spo
417. is represents a UCI from which tasks are being transferred in order to reach their I O device Enter only the UCI name e g VAH Do not include the Volume Set name e g WAH ROU FROM VOLUME SET The FROM VOLUME SET field should be set to the name of the Volume Set that holds the UCI identified in the entry s FROM UCI field For four field entries this represents the Volume Set from which tasks are being transferred in order to reach their I O device Every Volume Set listed in this field should be described in the VOLUME SET file 14 5 TO VOLUME SET The TO VOLUME SET field is only used for entries that build a UCI Association Table For such entries it should be the name of the Volume Set to which tasks are being transferred in order to reach their I O devices TO UCI As with TO VOLUME SET the TO UCI field is only used for entries that build a UCI Association Table For such entries it should be the name of the UCI to which tasks will be transferred whenever they must be moved from the UCI on the first Volume Set to the second Volume Set in order to reach their I O devices As with the From UCI field the Volume Set name should not be included July 1995 Kernel Systems Management Guide 21 9 Revised June 2008 Version 8 0 TaskMan System Management Configuration Sample Configuration Standardized VA Cach and GT M Configuration Sites that run Managers on their satellites should make the appropriate TASKMAN SITE PARAMET
418. is suggested you queue the report to a device during off hours 25 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU The following process chart shows the prompts and steps involved in using the Print Utility option Figure 25 5 Print Utility option process chart IF USER STEP AT THIS PROMPT ANSWERS L Select one of the following SH SpHOre CUS KE Keyword SY Synonyms Print which file SH for KE for SY for Select one of the following A Alphabetic C Code A lphabetic Print Shorveucs Keywords O Synonyms for which file Name of entry in LOCAL LOOKUP file 8984 4 lt gt Tor List Of entries lt Enter gt or up arrow lt gt You will be prompted for a device at this step Return to the menu July 1995 Kernel Systems Management Guide 25 7 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The following is an example of what might appear on your screen when using the Print Utility option an example of the output generated by this option is provided following the computer dialogue Figure 25 6 Print Utility option Sample user entries and sample output Select one of the following Shortcuts Keywords Synonyms Print which file SH lt Enter gt Shortcuts Select one of the following A Alphabetic C Code Sort By A lt Enter gt lphabetic Print Shortcuts for which file CPT DEVICE HOME lt Enter gt RIGHT MA
419. ision 6 System Surrogate for which Users Option The Surrogate for which Users option XQAL SURROGATE FOR WHICH USERS provides a view of which users have specified a selected user as surrogates for themselves 10 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 11 Server Options System Management What is a Server Option A server option is a special type of option stored in the OPTION file 19 that can be triggered by mail messages Addressing a mail message to a server option is termed a server request A server request awakens the option and causes it to execute the following e Any M code in the server option s ENTRY ACTION field 20 e Any M code in the HEADER field 26 e The routine indicated in the ROUTINE field 25 e Any M code in the EXIT ACTION field 15 A server type option is similar to a run routine type option The difference is that a server option is activated by a mail message while a run routine option is activated by a user choosing that option from a menu on a screen Server options should only be invoked by mail messages never directly by a user The form of the mail message that activates the server option is identical to any other mail message except that it is addressed to S lt option name gt The S like the G form for sending to mail groups routes the message to the server request software What Can Server Options Do A server request might trigg
420. isplay Option Descriptions 6 5 Two Question Marks to List Secondary and Common Options 6 3 ENTRY ACTION Field 20 7 11 11 1 11 3 Environment Check 20 2 23 7 23 9 ENVIRONMENT FOR DCL Field 21 5 21 15 EPS Anonymous Directories xxxvii ERR ZU API 13 2 Error Log 27 4 Error Log 13 7 Purge 13 5 ERROR LOG File 3 075 13 2 13 5 22 24 Error Log Node 22 27 Error Messages During Menu Jumping 7 14 ERROR MESSAGES File 3 076 13 5 Error Processing 2 6 13 1 XTER 13 6 XTERPUR Direct Mode Utility 13 5 Add Error Screens Option 13 3 Clean Error Trap Option 13 5 Edit Error Screens Option 13 3 Enhanced 13 4 Error Screens 13 2 Error Trap Display Option 13 6 Interactive Print of Error Messages option 13 7 List Error Screens Option 13 3 P1 Print 1 occurrence of each error for T 1 QUEUE Option 13 4 P2 Print 2 occurrences of errors for T 1 QUEUE 13 5 Remove Error Screens Option 13 4 System Management 13 2 Index User Interface 13 1 Error Processing Menu 13 4 Error Screens Node 22 28 TaskMan 20 6 ERROR State TaskMan 22 36 Error Trap Purging 13 5 Error Trap Auto Clean Option 13 5 Error Trap Display Option 13 6 Errors Cross references 22 25 Error Messages During Menu Jumping 7 14 Error Screens Error Processing 13 2 Log 27 4 Processing Kernel Error Trapping and Reporting 27 4 Reporting 27 4 Trapping 27 4 Errors Logged in Alpha Beta Test QUEUED Option 23 23 Escaping from a Jumb
421. it falls short of for example deleting a field protected with the at sign programmer access The same applies to templates If the template is protected the user who has access to the file will not have access to the template from VA FileMan options unless there is a match in the DUZ O character string July 1995 Kernel Systems Management Guide 5 7 Revised June 2008 Version 8 0 File Access Security Audit Access to Files Audit privileges might be granted to advanced VA FileMan users who are interested in developing new audit capabilities With AUDIT access which must be accompanied by DD access VA FileMan s Modify File Attributes option DIMODIFY can be used to set an audit flag for a particular field within a file This access does not include setting audit conditions with M code which is reserved for users with a FILE MANAGER ACCESS CODE field 3 containing The data values for attribute fields can be recorded in the AUDIT file 1 1 by setting an audit flag in the data dictionary DD for that field For example the SSN field in the PATIENT file 2 could be audited There are two choices for the audit in the AUDIT file 1 1 e An entry can be made when a value is entered or changed e Anentry can be made only when the value is changed 1 e edited or deleted The second method may be all that s needed In the SSN example you would monitor just the circumstances of the change not of the initial SSN assignm
422. k it remains in the TASKS file 14 4 until you edit it to run again or until TaskMan purges it from the Task list 19 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan User Interface Editing Tasks The Edit task option E lets you edit a task s output device description and run time The task must be unscheduled before it can be edited The Edit task option asks if it s OK to unschedule the task To edit the task answer YES But once the task is unscheduled it will not run unless you reschedule it by finishing each step of editing the task NOTE You cannot edit a task that is already running Once the task is unscheduled you can update the following task settings e When the task should start e Which device it should use and whether a device is needed e What the description of the task should be Once you ve had a chance to modify these three settings you re asked whether the task should be rescheduled as shown see Figure 19 4 If you answer YES the task is updated to reflect the changes you specified If you answer NO however no settings are changed but the task remains unscheduled and will not run until you use Edit Task to reschedule it Figure 19 4 Edit Task option Sample user dialogue Before you edit the task I ll make sure it s not scheduled okay YES lt Enter gt Task ready for editing Currently this task requests output device VERSLW Do you want to cha
423. k on more than one job at a time Each job the computer works on consumes a part of the computer s resources Initially you have only one job your interactive terminal session with which to do your work TaskMan however allows you to claim more of the computer s resources by allowing you to schedule additional jobs to run in the background Background Jobs You can queue additional tasks to run through TaskMan Once started these additional tasks called background tasks can run at the same time as the foreground jobs and without further dialogue with the people who started them Appropriate use of background tasks can cut your frustration by reducing the amount of time you must wait for the computer to do lengthy repetitious work that does not need human intervention Every task queued to run in the background reduces time spent waiting and also uses the computer s resources more efficiently Queuing Output Most users use TaskMan by queuing reports labels and other kinds of output Because output involves no dialogue once it has begun and because it requires you to wait while it prints it makes an ideal candidate for queuing You can queue most output when the computer asks you to select a device to which the output should be sent The series of prompts and responses to queue a job to a device usually looks something like this Figure 19 1 Queuing output Sample user dialogue DEVICE QUEUE TO PRINT ON Answer with name of the output
424. kit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml 26 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 2 Verification Tools Overview Kernel Toolkit provides an Application Programming Interface API that includes developer utilities for working with routines and globals This chapter describes the verification tools exported with Kernel Toolkit that are useful to Information Resource Management IRM staff and developers for reviewing Veterans Health Information Systems and Technology Architecture VistA software Kernel Toolkit Application Programming Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml Verification tools can be accessed through one of three methods e Programmer Options menu e Operations Management menu e Direct Mode utilities User Interface Verifier Tools Menu The Verifier Tools Menu contains options which are available as tools for verification during program development These options are located on the Verifier Tools Menu XTV MENU which is located on the Systems Manager Menu These tools are useful for developers to e Record the text of the routines indicated in the file used to maintain changes in routines
425. kly than if only one CPU runs a Manager An added bonus with multiple Managers is that if one CPU running a Manager becomes unavailable Manager s will still run on the other CPU s with no further re configuration required Configuration for Multiple Managers Each node that runs a TaskMan Manager must have its own entry BOX VOLUME PAIR in the TASKMAN SITE PARAMETERS file 14 7 Each CPU must share access to a common ZTSK and ZTSCH global and have access to the same devices Because of this all CPUs must run the same M implementation Starting Up Pausing and Stopping Multiple Managers You will need to start a Manager on each CPU where a Manager should run Whatever steps you follow to start a single Manager you will need to repeat for any additional nodes on which you want to run additional Managers The options that place TaskMan in a WAIT state and stop TaskMan are not CPU specific they will affect all running Managers across the system July 1995 Kernel Systems Management Guide 21 11 Revised June 2008 Version 8 0 TaskMan System Management Configuration Load Balancing The LOAD BALANCE ROUTINE field in the TASKMAN SITE PARAMETERS file 14 7 holds the name of a function that returns a CPU s load rating This field is only useful if you are running multiple TaskMan Managers To use load balancing enter a routine name in the LOAD BALANCE ROUTINE field for each participating CPU s BOX VOLUME PAIR entry Kernel
426. ks and TaskMan Consider this topic a reference to TaskMan s global structure and messages SCHEDULE File A ZVSCH holds the non VA FileMan compatible SCHEDULE file which consists of independent lists and nodes This is where TaskMan processes tasks This structure is not supported for use by application software All task manipulation must be done through approved options and entry points These structures must be free to change from version to version to easily adapt and meet the changing needs of VistA On the following pages is an example of a global that contains one of each type of node used by TaskMan The initial node was used to create ZTSCH before TaskMan was active so that the global type and protection could be assigned Table 22 5 ZTSCH SCHEDULE File nodes A ZTSCH next run time task This node stores the Schedule List The task corresponds to an entry in the TASKS file 14 4 and the next run time is computed from the value in the sixth piece of the entry s 0 node and is the total number of seconds contained in the next run time s H translation If the Schedule List entry equals a device name the entry was not created through the Program Interface A LTSCH C This node stores the Compute Server Job List C list This list holds tasks that are ready to be run by Submanagers on specific Compute Servers A Submanager cross Volume Set jobbed to a Compute Server only runs tasks under this list for the Compute
427. l Imaging alerts e Date of the oldest alert View data for Alert Tracking file entry Option The View data for Alert Tracking file entry option XQAL VIEW ALERT TRACKING ENTRY can be used to view data for one or more entries in the ALERT TRACKING file 8992 1 in captioned format The internal entry numbers for the entries to be displayed must be entered individually July 1995 Kernel Systems Management Guide 10 9 Revised June 2008 Version 8 0 Alerts Set Backup Reviewer for Alerts Option The Set Backup Reviewer for Alerts option XQAL SET BACKUP REVIEWER was added with Kernel Patch XU 8 0 174 This option provides a mechanism for a user to set entries into the PARAMETERS file 8989 5 that will assign an individual as the Backup Reviewer for Unprocessed Alerts which is the DISPLAY TEXT Field 02 for the XQAL BACKUP REVIEWER entry in the NAME field 01 in the PARAMETER DEFINITION file 8989 51 if there is a date specified in the DAYS FOR BACKUP REVIEWER field 15 in the ALERT DATE TIME Multiple field 4 01 in the ALERT file 8992 for that alert If this is the case an alert that remains unread for the specified number of days will be forwarded to the Backup Reviewer for Unprocessed Alerts indicated at the lowest level found for processing for the user in the PARAMETERS file 8989 5 The following is the processing order listed lowest to highest level 1 User OERR Team Team 2 3 4 Service 5 Div
428. l users Entering two question marks 2 at the menu s select prompt will display any SECONDARY MENU OPTIONS available to the signed on user along with the common options available to all users Job specific information that is kept on each CPU so that it is readily available during the user s session It is stored in the XUTL global which is maintained by the menu system to hold commonly referenced information The user s place within the menu trees is stored for example to enable navigation via menu jumping This field takes data from other fields and performs a predetermined mathematical function e g adding two columns together You will not however see the results of the mathematical function on the screen Only when you are printing or displaying information on the screen will you see the results for this type of field The Kernel module that provides a mechanism for accessing peripherals and using them in controlled ways e g user access to printers or other output devices VA FileMan utility that gathers all software components and changes them into routines namespacel routines so that they can be exported and installed in another VA FileMan environment Kernel Systems Management Guide Glossary 1 Version 8 0 Glossary DOUBLE QUOTE DR STRING DUZ O ENCRYPTION FILE ACCESS SECURITY SYSTEM FORCED QUEUING GO HOME JUMP HELP PROCESSOR HOST FILE SERVER HFS HUNT GROUP INIT 2 Glos
429. late only their own tasks Only the holder of the ZTMQ security key can use these options to manipulate any task on the system 20 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 21 TaskMan System Management Configuration This chapter discusses the many issues surrounding the configuration of TaskMan Defining TaskMan Environments The part of configuring TaskMan for a system that requires the most creativity is deciding how to divide the system s UCIs Volume Sets and CPUs into TaskMan environments A TaskMan environment is the collection of UCIs from which entries can be made directly into a given Manager s TASKS 14 4 and SCHEDULE files and that are within that Manager s reach This requires looking at the system in terms of queuing and starting tasks There are a number of options available Many different configurations are possible One type of configuration has CPUs sharing the same Volume Set Since this type of environment shares a single Volume Set among multiple CPUs they also share a single TASKS 14 4 and SCHEDULE file However the reach of Managers cannot span CPUs Therefore you must decide which CPUs in that environment run Managers or whether some of them should rely on the other CPUs to run their tasks for them Alpha clusters in VA are typically configured with Managers on only one or a few CPUs A different configuration allows you to limit the number of places TaskMan runs In this scena
430. le on the current branch of your menu tree The Secondary menu and the Common menu contain options that you can select at any location in the menu system Options on the Secondary menu are typically created by your system manager Options on the Common menu are standard Kernel options available from anywhere in the menu system Options on the current menu on the other hand can only be directly selected while that menu is the current menu The two question mark display shows the option s synonym a short abbreviation if one exists You can select an option by its synonym as well as by its full name On the same line it lists the option s full name followed by the formal option name in capital letters enclosed in square brackets The name is the 01 field of the OPTION file 19 It also shows any option restrictions such as e QOut of Order e Locked e Prohibited times July 1995 Kernel Systems Management Guide 6 3 Revised June 2008 Version 8 0 Menu Manager User Interface Figure 6 3 Two question marks help Listing Primary Secondary and Common menu options Select Systems Manager Menu Option FM VA FileMan Core Applications Device Management gt Locked with XUPROG Information Security Officer Menu Manage Mailman Menu Management Operations Management Programmer Options gt Locked with XUPROG Spool Management Taskman Management User Management You can also select a secondary option OUT Equipmen
431. lect TIMES PROHIBITED lt Enter gt 7 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Select TIME PERIOD lt Enter gt RESTRICT DEVICES lt Enter gt Select PERMITTED DEVICE lt Enter gt Option Name and Menu Text By convention the formal option name is usually entered in all capital letters According to namespacing conventions it must begin with a namespace that identifies the associated software It is the NAME field 01 of the OPTION file 19 The menu text is what is displayed to the user at the select prompt Like the words of a heading or title initial capitalization is used for all words except prepositions and articles all of which are presented in lowercase To minimize the number of keystrokes needed to select an option different first letters should be used for the text of each menu item Menus should be limited to about seven items so they will all appear together on one screen The most frequently used items should be presented first Synonyms and Display Order By default the items on the menu are displayed in alphabetical order by menu text If any of the items is assigned a synonym those items will be displayed before others lacking synonyms To facilitate menu jumping synonyms should ideally be unique numbers are not good choices for synonyms To customize the order of the display each item on the menu can be assigned a Display Order This fi
432. led Screen 2 6 Establish System Audit Parameters Option 7 4 EVE Menu 7 1 7 17 7 18 9 10 13 2 23 2 EXIT ACTION Field 15 7 4 7 11 11 1 11 3 Exploding Key 8 4 Exported Components 23 12 Files 3 18 Frames 12 6 Keys 8 5 Menus 7 2 7 8 Options 7 1 Software 23 1 23 4 23 12 Extended Help 12 2 F Failed Access Attempts Audit 3 28 FAILED ACCESS ATTEMPTS LOG File 3 05 3 28 3 29 FAX NUMBER Field 3 22 Fields I DEVICE File 3 5 15 1 15 2 15 3 15 4 15 10 15 12 15 13 16 2 17 9 18 10 18 13 18 14 22 33 22 35 IDEVICE File 3 5 18 16 July 1995 Kernel Systems Management Guide Index 9 Revised June 2008 Version 8 0 Index 10 Index ACCESS CODE 3 19 ACCESSIBLE FILE Multiple 32 5 1 5 3 5 8 5 10 5 11 5 12 5 13 AGENCY 3 6 ALERT DATE TIME Multiple 01 10 10 ALLOWED TO USE SPOOLER 3 22 ALWAYS SHOW SECONDARIES 3 22 7 7 ASK DEVICE TYPE AT SIGN ON 2 6 2 9 35 329 ASK HFS I O OPERATION DEVICE File 3 5 16 2 ASK HOST FILE DEVICE File 3 5 16 2 ASK PARAMETERS DEVICE File 3 5 15 4 15 9 16 2 AUTO DESPOOL 17 9 AUTO MENU 2 10 3 6 3 7 3 21 6 2 7 3 AUTO GENERATE ACCESS CODES 3 6 BACK SPACE TERMINAL TYPE File 3 2 15 8 18 10 18 11 BOX VOLUME PAIR 21 3 21 4 21 11 21 12 BYPASS DEVICE LOCK OUT 3 2 CAN DELETE WITHOUT PROCESSING 1 10 7 CAN MAKE INTO A MAIL MESSAGE 3 22 CHECKSUM REPORT 26 6 CHECKSUM REPORT 6 24 10 CHECKSUM VALUE
433. lti Term Look Up MTLU 25 2 25 17 System Configuration TaskMan Terminology 20 7 System Management Index 38 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Alerts 10 5 Browser Device 18 3 Device Handler 15 1 Electronic Signatures 4 2 Error Processing 13 2 File Access Security 5 3 Form Feeds 18 6 Help Processor 12 4 Host Files 16 2 Hunt Groups 18 8 KIDS Installations 23 1 Utilities 24 1 Magtape Devices 18 10 Managing Delegates 9 7 Menu Manager 7 1 Network Channel Devices 18 11 Resources 18 13 Secure Menu Delegation 9 7 Security Keys 8 2 Server Options 11 1 Signon Security 3 1 Slaved Printers 18 15 TaskMan Configuration 21 1 Operation 22 1 Overview 20 1 XGF Function Library 29 1 System Manager Introduction 1 2 System Parameters 3 1 Systems Management Multi Term Look Up MTLU 25 20 Systems Manager Menu 7 1 23 2 27 1 T Table of Contents 1x Tables xxx TAPE XTRCMP Direct Mode Utility 26 7 Task File Cleanup 22 17 Task List 20 6 22 10 Node 22 29 TASK PARAMETERS Field 3 29 10 6 10 7 13 6 22 19 22 21 TASK PARTITION SIZE Field 21 3 Task Rejection Messages TaskMan 22 35 Task Status Codes TaskMan 22 32 TaskMan 19 1 Index ZTSCH Global 20 5 ZTSK Global 20 5 API 20 1 20 2 Check Taskman s Environment Option 22 13 Clean Task File Option 22 17 Cleanup Task List Option 22 6 Configuration 21 1 DEVICE File 3 5 21 13 Multiple Mana
434. ly authorized because the user held the key SUBORDINATE KEY Exploding Keys If a security key has any associated subordinate keys entries in this multiple the subordinate keys are automatically assigned along with the overall key A security key with this feature is called an exploding key since it and its subordinates are assigned all at once NOTE If entries in the SUBORDINATE KEY Field Multiple are edited dynamic updating of the security keys already assigned to users does not occur 8 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Security Keys Exploding security keys cannot be exported with software although there may be support for this functionality in the future They are intended to be created by IRM as a timesaving method in the key allocation process Deleting Security Keys Keys should not be deleted from the SECURITY KEY file 419 1 Kernel has made the NAME field 01 of the SECURITY KEY file 419 1 uneditable to prevent deletion of security keys through VA FileMan IRM should not attempt to edit the key global directly to remove a key since associated pointing relationships will be left to cause errors The one mechanism Kernel does provide for deletion of security keys is through the Kernel Installation and Distribution System KIDS REF For more information please refer to the KIDS section in this manual and the KIDS Developer Tools chapter in the Kernel Developer s Guide
435. marked in the remote OPTION file 19 as a server type option but some other kind of option returned in type such as a print type option The OUT OF ORDER MESSAGE field for that option has been filled in with the text that is returned in message There is no information for this option in fields 220 through 225 The 220 node of the OPTION file 19 is missing or blank There is no bulletin pointed to by Field 220 of this option in the OPTION file 19 and the default XQSERVER bulletin has been removed from the system Server options will not run without an associated bulletin even if it is suppressed WARNING there is an invalid pointer in Field 220 of the OPTION file 19 that points to a nonexistent bulletin The default bulletin XQSERVER will be used WARNING there is an invalid pointer in Field 222 of the OPTION file 19 indicating a mail group that should receive the bulletin in addition to the mail group pointed to by the BULLETIN file The bulletin returned in bulletin name does not have a mail group associated with it in the BULLETIN file 3 6 Version 8 0 July 1995 Revised June 2008 Server Options There is no active user associated with the bulletin bulletin name There is no routine in field 25 of the Option File for this option When following the pointers from the bulletin to the mail group to the NEW PERSON file 200 an active user was not found Each server option must be l
436. me s H translation prioritizes the tasks that should have started the longest time ago The Submanagers use the top node to space out access to the list and the last device so that only one Submanager at a time is checking the list and so that checks that find all devices still busy are followed by a short waiting period before the list is checked again A LTSCH JOB This node stores the Job List This list holds tasks that are ready to be run by Submanagers The run time is the total number of seconds contained in the run time s H translation and task and device IO are what you would expect A LZTSCH LINK This node stores the Link Lists The LINK node itself is only present when a link is down It is used to time the checks that occur every fifteen minutes The second level nodes should always be present with the current information on each of the CPUs and Volume Sets A ZTSCH LOAD load rating This node is used to balance the CPU load among the various Managers that work out of the current TASKS and Schedule files It identifies the CPU that most recently checked its rating and decided to run Managers more loaded a lower rating than this one wait to allow this Manager to pick up more of its share of the load A ZTSCH LOADA This node stores the Load List This list records the ratings for all the CPUs with Managers processing this TASKS file The first piece which flags the Managers that decide to wait to balance
437. ment Delete A Spool Document Option name XU SPL DELETE x gt Extended help available Type Delete to see it Delete a spool document from the spool document file and delete the associated message if they are still linked List Spool Documents Option name XU SPL LIST x gt Extended help available Type List to see it This option lists entries in the spool document file Make spool document into a mail message Option name XU SPL MATL x gt Extended help available Type Make to see it This option will take a spool document and post it as a mailman message to the user s IN basket This doesn t move the data at all but does decrease the number of lines charged to the user wk Press RETURN CO Continue TT Co stop of Option text for More help lt Enter gt Print A Spool Document Option name XU SPL PRINT x gt Extended help available Type Print to see it This allows the printing of a document that has been spooled Shall I show you your secondary menus too No lt Enter gt Would you like to see the Common Options No lt Enter gt Select Spooler Menu Option You should be ready to use three question marks to learn more about unfamiliar options e g options distributed in a new software release Jumping to Options Up arrow Jump The pathways of the primary secondary and Common menus have tree like structures You can step up or down the pathways to reach your destination
438. ment Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU Using the Multi Term Lookup MTLU Option The Multi Term Lookup MTLU option XTLKLKUP is used to test the ICD diagnosis and procedure codes CPT codes and other commonly used references that have been entered in the LOCAL LOOKUP file 8984 4 and have been associated with a shortcut synonym or keyword The system searches for entries in the following order shortcut synonym then keyword If you are entering a multi term narrative phrase you can enter double spaces between each term to avoid a search of the LOCAL SHORTCUT file 8984 2 When searching for a keyword phrase the system searches for each word in the phrase and then displays all common entries For example 1f the keyword is FRACTURE FEMUR the system searches for FRACTURE and then FEMUR and displays only those codes with a diagnosis containing both keywords or synonyms of those words The following process chart shows the prompts and steps involved in using the Multi Term Lookup MTLU option Figure 25 3 Multi Term Lookup MTLU option process chart IF USER AT THIS PROMPT ANSWERS WITH Lookup on which file Name of entry in LOCAL LOOKUP file 8984 4 lt gt for list of entries lt Enter gt or up arrow lt gt NARRATIVE HxESELng SNOrCEUL synonym or keyword If a word phrase or symbol is entered that the system cannot identify the following appears
439. mes Option The List Help Frames option XQHELP LIST can be used to print a series of frames with a table of contents and page numbering to resemble a hard copy manual Figure 12 7 List Help Frames option Sample user dialogue Select Help Processor Option List Help Frames Select primary HELP FRAME from which to list XUDOC NEW 12 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Help Processor New Revised Help Frames Option The New Revised Help Frames option XQHELP UPDATE produces a VA FileMan generated print of all help frames that have been updated during a specified time period Cross Reference Help Frames Option The Cross Reference Help Frames option XQHELP XREF lists any of the following cross references to a specified set of help frames e Parents other help frames that call the specified help frame e Options options whose HELP FRAME field references the specified help frame e Routines if a developer has entered the routine in the specified help frame s INVOKED BY ROUTINE field Fix Help Frame File Pointers Option Deleting Help Frames There is no Kernel utility to delete help frames but the menu system does not generate errors if a pointed to help frame is missing If a site chooses to delete help frames using VA FileMan they should use the Fix Help Frame File Pointers option XQHELPFIX afterwards to delete dangling pointers from the OPTION file s HELP FRAME field Assigning D
440. meters option XUAUDIT which is in the Audit Features XUAUDIT MENU menu tree Simply enter a time to initiate audit and a time to terminate audit Then enter the specific options you want to audit you can also choose all options Each time a user uses an audited option an entry is made in the AUDIT LOG FOR OPTIONS file 19 081 You can display these entries using the Option Audit Display option XUOPTDISP You can purge the AUDIT LOG FOR OPTIONS file 419 081 with the Audited Options Purge option XUOPTPURGE If Kernel Toolkit is installed at your site you can also use its Alpha Beta Test Option Usage menu to count the number of times an option is invoked REF For more information please refer to the Kernel Toolkit documentation and the Kernel Security Tools Manual 7 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager System Management Display Menus and Options Menu Figure 7 5 Display Menus and Options menu SYSTEMS MANAGER MENU EVE Menu Management XUMAINT List Options by Parents and Use XUXREF Display Menus and Options XODISPLAY OPTIONS Abbreviated Menu Diagrams XUUSERACC2 Diagram Menus XUUSERACC Inguire XUINQUIRE Menu Diagrams with Entry Exit Actions XUUSERACC1 Print Option File XUPRINT Kernel provides a number of options to display and diagram menus and options on the Display Menus and Options menu XQDISPLAY OPTIONS Diagram
441. ming Options To discover the menu tree roots of other software applications and how options and suboptions are related you can use the following menu diagramming options Table 7 1 Menu diagramming options to discover tree roots and relationships between options suboptions Menu Description S Abbreviated Menu Diagrams Outlines the menu tree Diagram Menus Outlines the menu tree and shows option attributes e g locks and prohibited times Menu Diagrams with Entry Exit Actions Outlines the menu tree shows option attributes and shows entry exit and header actions as well Also the List Options by Parents and Use option XUXREF identifies which options have no parents and thus are standalone roots It also indicates whether options are used as primary menus secondary menus and or as regularly scheduled tasks Option Descriptions To learn more about the options included in a software application you can use the Print Option File option XUPRINT from the Display Menus and Options menu XQDISPLAY OPTIONS to print the option description type and other information This listing can be sorted by namespace For example to print all the VA FileMan options you can sort from DD to DI July 1995 Kernel Systems Management Guide 7 5 Revised June 2008 Version 8 0 Menu Manager System Management Displaying Options To display an option use the Inquire option Figure 7 6 Inquire option Sample user dialogue Sele
442. mp start directly to a particular option you can specify the name of an option after another semicolon Figure 2 4 Entering the Access and Verify codes at the same time and jumping directly to a specified option ACCESS CODES accesscode verifycode Intro Good afternoon You last signed on today at 12 00 INTROductory text edit To force the Kernel query of the terminal type identity you can include a colon anywhere in the string REF If you want to avoid the terminal type query please refer to Terminal Type Prompt topic that follows Normal Signoff When you complete a session on the computer system you should sign off the system so that no one can come along and use the computer system under your identity There are several ways you can sign off of the system Figure 2 5 System commands Menu options for signoff SYSTEM COMMAND OPTIONS XUCOMMAND Halt XUHALT Continue XUCONTINUE Restart Session XURELOG One way to sign off is to enter halt at any menu prompt When you sign off using halt at next signon after entering Access and Verify codes your normal primary menu will be your first menu Or to sign off you can enter continue At your next signon after entering Access and Verify codes your last used menu when you signed off will be your first menu for that session July 1995 Kernel Systems Management Guide 2 5 Revised June 2008 Version 8 0 Signon Security User Interface If remotel
443. mplate to function Any user can define user specific MENU templates via the corresponding Common option The menu system s hierarchical tree like structures that can be traversed or navigated like pathways to give users easy access to various options Programmer Access Code An optional user attribute that can function as a second level password into programmer mode See FILE ACCESS SECURITY SYSTEM A preset formula used to test strings of data Refer to your system s M Language Manuals for information on Pattern Match operations Kernel Systems Management Guide Version 8 0 Glossary 3 Glossary PHANTOM JUMP PRIMARY MENUS PROGRAMMER ACCESS PROTOCOL QUEUING QUEUING REQUIRED RESOURCE RUBBER BAND JUMP SCHEDULING OPTIONS SCROLL NO SCROLL 4 Glossary Menu jumping in the background Used by the menu system to check menu pathway restrictions The list of options presented at signon Each user must have a PRIMARY MENU OPTION in order to sign on and reach Menu Manager Users are given primary menus by IRM This menu should include most of the computing activities the user will need Privilege to become a developer on the system and work outside many of the security controls of Kernel Accessing programmer mode from Kernel s menus requires having the at sign security code which sets the variable DUZ 0 An entry in the PROTOCOL file 101 Used by the Order Entry Results Reporting OE RR softwar
444. mplate will be executed on your first signon of the day So if you have a series of options you execute on your first signon every day an easy way to execute them is to create a MENU template store the series of options in the template and name the template LOGIN Summary Once you learn how to navigate Kernel s menu tree you can use some of Menu Manager s additional features to help increase your productivity in the VistA computer system These features include the Up arrow Jump the Rubber band Jump using three question marks to obtain online option help and using MENU templates as scripts July 1995 Kernel Systems Management Guide 6 9 Revised June 2008 Version 8 0 Menu Manager User Interface 6 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 7 Menu Manager System Management Menu Manager is built around options which are entries in the OPTION file 19 There are several types of options One type of option Menus has subentries in the MENU item field Multiple a multiple that points back to the OPTION file 19 itself Other types of options are designed as items that plug into the MENU item field Multiple of a menu type option Kernel provides a number of tools to create and manage menus and options Kernel Menus Most of the options exported with software are tied to a parent option or master menu as a collection point Kernel exports three menu tree roots The Systems
445. mprise a number or term in the 01 field and a longer description or definition in some other field In the simplest application of MTLU a special lookup routine XTLKDICL is defined in the file s data dictionary DD then a MUMPS cross reference is applied to the description definition field Options are available to fully configure a file for use with MTLU FileMan is used to create build the cross reference To set the cross reference text from the selected field is passed to a tokenizing routine XTLKTOKN Trivial words are filtered by an expanded Key Word In Context K WIC then each remaining token is added to the cross reference To request a lookup users and developers can pass in words or phrases Their input is similarly tokenized However only terms associated with all tokens entered are found Input can be generalized using partial words or fewer words as well as lexical variants For example using the FileMan Inquire to File Entries option on the ICD DIAGNOSIS file 80 one could first enter MALIG MTLU informs the user which terms apply to the search MALIG MALIGNANT and that 447 matches are found To be more specific the user might enter MALIG LIP to request all malignancies associated with the lip In this case only 12 matches are found The user can further screen searches by using the Not Sign before a word or phrase To request all malignancies of the lip except those of the lower lip one could enter MALIG LIP
446. mpt displays the list of error screens Edit Error Screens Option Figure 13 3 Edit Error Screens option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Edit Error Screens XUTM ERROR SCREEN EDIT Use the Edit Error Screens option XUTM ERROR SCREEN EDIT if you want to reset the counter on a screen or change your mind about whether or not the screen counts its errors You must type in the exact screen you wish to edit Again entering two questions marks displays the list of error screens currently in place July 1995 Kernel Systems Management Guide 13 3 Revised June 2008 Version 8 0 Error Processing Remove Error Screens Option Figure 13 4 Remove Error Screens option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Taskman Error Log XUTM ERROR Remove Error Screens XUTM ERROR SCREEN REMOVE When you type in a screen at the prompt for this option the screen is removed for you If there are any similar screens the Remove Error Screens option XUTM ERROR SCREEN REMOVE asks whether you wish to remove them also Again entering two question marks displays the list of error screens Enhanced Error Processing Enhanced error processing for Cach sites is supported Kernel s error trap captures variables in their state at the time errors
447. mpute Server Job List is checked here and will let you know about tasks waiting to run on other CPUs and if the Submanagers are not starting Task List The Task List is where TaskMan keeps track of the tasks it has started running Entries are set into this list when the Submanagers start their tasks and are cleared when the tasks quit or cause errors to be trapped KILLing a task by forcing its process to exit in the middle of execution using such vendor specific tools as RJD RESJOB FORCEX KILLJOB etc does not give the Submanager a chance to clear the task from the Task list so the Task List can become inaccurate If you frequently KILL jobs but want to keep your Task List accurate you will need to manually remove the obsolete entries The exit action of the KILL off a users job option XURESJOB will help you identify and remove from the list of running tasks those you have forcibly exited 22 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Monitor Action Prompt After summarizing the status of the Manager and the principal lists of the SCHEDULE file the monitor offers you a choice of actions They are displayed if you enter a single question mark at the Enter monitor action prompt Figure 22 10 TaskMan monitor actions Enter lt RET gt to update the monitor screen Enter to exit the monitor Enter E to inspect the TaskMan Error File Enter S t
448. ms simply enter a question mark as shown below Figure 6 1 One question mark help Sample user dialogue Select Any Level Menu Option First Item Second Item Third Item of Menu Choices Fourth Item Enter for more options for brief descriptions OPTION for help text Select Any Level Menu Option Entering Option to Display Option Help To obtain a lengthier description of an individual option enter a single question mark and the first few letters of the option name If there is an extended description of the option or a help frame describing the option they are displayed Figure 6 2 Using Option to get help on a named option Sample user dialogue Select User s Toolbox Option Display User Characteristics Fdit User Characteristics Electronic Signature Code Edit Menu Templates Spooler Menu TaskMan User User Help Select User s Toolbox Option DISPLAY Display User Characteristics Option name XUUSERDISP Display the user s name location and characteristics x gt Press RETURN to continue St to stop lt Enter gt Select User s Toolbox Option 6 2 Kernel Systems Management Guide Version 8 0 July 1995 Revised June 2008 Menu Manager User Interface Entering Two Question Marks to List Secondary and Common Options At any select prompt you can enter two question marks to see options on the Secondary and Common menus as well as options availab
449. n Library useful The XGF Function Library provides the following functionality e Text mode overlapping windows e Text mode cursor positioning by screen coordinate e Text mode video attribute control bold blink etc e Keyboard reader using M escape processing thereby making use of keystrokes like lt UP ARROW 1 lt DOWN ARROW lt PREV gt lt NEXT gt gt etc The XGF Function Library may not be appropriate if you need e A full graphical user interface GUI front end for your application e Support for non ANSI VT compatible display devices To use the XGF Function Library your system must use an M implementation that complies with the 1995 ANSI M standard At a minimum the M implementation must support the following features to use the XGF Function Library Table 29 1 Minimum M implementation features required for the XGF Function Library SET into EXTRACT S xXeUthis 1s a string sh Oy 1 4 that Reverse ORDER Sx 50 IME T S Two argument GET K Y S X SG Y DEFAULT Skipping parameters D TAG ROUTINE P2 P4 NAME W NA TMP J i This XGF Function Library supports terminals that are ANSI compatible and at least VT100 compatible As a result this software does not support QUME QVT102 QVT102A terminals July 1995 Kernel Systems Management Guide 29 1 Revised June 2008 Version 8 0 XGF Function Library System Management The XGF Function Library Application Progr
450. n Program Interfaces APIs please refer to the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml Information on recommended system configuration and setting Kernel s site parameters as well as lists of files routines options and other components are documented in the Kernel Technical Manual Information about managing computer security which includes a detailed description of techniques that can be used to monitor and audit computing activity is presented in the Kernel Security Tools Manual Instructions for installing Kernel are provided in the Kernel Installation Guide This guide also includes information about software application management e g recommended settings for site parameters and scheduling time frames for tasked options July 1995 Kernel Systems Management Guide 1 3 Revised June 2008 Version 8 0 Introduction 1 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security July 1995 Revised June 2008 Kernel Systems Management Guide Version 8 0 I 1 Signon Security Kernel Systems Management Guide Version 8 0 July 1995 Revised June 2008 2 Signon Security User Interface The first step you take each time you access the computer system is called signing on When you sign on to the VistA computer system you are required to enter an Access and Ver
451. n be used to delete one or more routine s The wildcard syntax can be used to delete a set such as ABC to delete all those routines beginning with the letters ABC This option is locked with the XUPROGMODE security key The corresponding direct mode utility can be used in programmer mode as follows gt D ZTRDEL Load and Save Routines The Input Routines and Output Routines options can be used to move routines from one UCI to another These make use of operating system specific utilities such as RR for routine restore and RS for routine save Input Routines Option The Input Routines option XUROUTINE IN loads routines from an external device This option is locked with the XUPROG security key The corresponding direct mode utility can be used in programmer mode as follows gt D SRR OS specific Output Routines Option The Output Routines option XUROUTINE OUT outputs routines to an external device such as a host file The corresponding direct mode utility can be used in programmer mode as follows gt D SRS OS specific Load refresh checksum values into ROUTINE file Option The Load refresh checksum values into ROUTINE file option XU CHECKSUM LOAD can be used to update the ROUTINE file 9 8 with the latest checksum values from FORUM i REF Kernel Toolkit Application Programming Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Tool
452. n is executed the request is terminated at that point and an error is generated ROUTINE 25 lf there is a routine name in this field in the forms ROUTINE July 1995 Kernel Systems Management Guide 11 3 Revised June 2008 Version 8 0 Server Options iediName PF AROUTINE or TAG ROUTINE the routine is run HEADER 26 This field of M code is executed if it exists SERVER BULLETIN 220 This field is a pointer to the BULLETIN file 3 6 it indicates the bulletin to use to notify the local mail group of a server request on their system If there is no bulletin entered in this field the default bulletin XQSERVER is used Unless there are pressing reasons to do otherwise it is recommended that the default bulletin XQSERVER be used by leaving the SERVER BULLETIN field blank If the mail group s pointed to by XQSERVER or the bulletin pointed to in this field does not contain an active user i e a user possessing a Verify code and no effective TERMINATION DATE the software turns on auditing i e SERVER AUDIT described below and sends a MailMan message to the local PostMaster CAUTION The most common reason for server A options not functioning is that there is no active user associated with the bulletin specified For security reasons server options will not run without a locally defined active user associated with the chosen bulletin SERVER ACTION 221 This SET OF CODES field allows the local IRM staff to
453. ncluding whether capacity management testing is active July 1995 Kernel Systems Management Guide 7 21 Revised June 2008 Version 8 0 Menu Manager System Management 7 22 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 8 Security Keys User Interface Security keys are primarily used to allow access to specially protected options If a software application exports a menu that has one or two options that require a secured level of access they can use security keys to lock those special options When an option is locked you can only use the locked option if you hold the security key matching the key with which the option was locked Entering two question marks at the menu system s select prompt displays the current options If any of the options are locked that fact is listed also along with the names of any associated security keys In the following example the option Programmer Options is locked with a security key named XUPROG Figure 8 1 Sample locked menu options showing required security key Entering two question marks Select Systems Manager Menu Option Device Handler XUTIO Menu Management XUMAINT Programmer Options XUPROG xx gt Locked with XUPROG You can list which security keys you currently hold by using the Display User Characteristics option on the Common menu It displays a list of all security keys you hold similar to the following Fi
454. nctionality that Kernel V 8 0 provides for the Veterans Health Information Systems and Technology Architecture VistA management and end users For example site parameters are discussed in various topics throughout this manual CAUTION To protect the security of VistA systems distribution of this software for use A on any other computer system by VistA sites is prohibited All requests for copies of Kernel for non VistA use should be referred to the VistA site s local Office of Information Field Office OIFO Otherwise there are no special legal requirements involved in the use of Kernel The Kernel Systems Management Guide is divided into six major sections based on the following functional divisions within Kernel I Signon Security e g techniques for granting user access and monitoring computing activity II Menu Manager e g techniques for managing menus Ul Device Handler IV TaskMan V Kernel Installation and Distribution System KIDS VI Toolkit REF For information on developer tools e g Direct Mode Utilities and Application Program Interfaces APIs please refer to the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml Information on recommended system configuration and setting Kernel s site parameters as well as lists of files routines options and other components are documented in t
455. nd according to the VA Programming Standards and Conventions SAC XINDEX reports any errors that it finds The reported error codes error flags are as follows e S Standards violation according to VA Standards e W Warning violation according to VA Conventions e F Fatal M error hard MUMPS error The XINDEX utility creates a cross referenced list of global references and routines invoked by a selected list of routines a build or a package While XINDEX will show all routines that are called it will not identify all global references in the routines After running XINDEX use the RFIND utility to find entries that were missed by XINDEX XINDEX can also be used to verify parts of a software application that contain M code Compiled templates can be included The M code used in data dictionaries functions and options can also be reviewed When using XINDEX to review an entire software application it is best to queue the report for an off peak time since processing is intensive 26 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Routine Tools The XINDEX utility can be called directly 1 e gt D XINDEXFigure 26 2 or via an option on the Programmer Options menu XUPROG Figure 26 2 XINDEX oIndex of Routines option direct mode utilities sample user entries gt D XINDEX Mig Pie Re Oe 35 soe ARS EI eae E IN a eR Shae UCI NXT CPU NXT JU 06 ZOO6CGLS 1412 All Routines No gt
456. nd jobs 3 Submanagers Each background job request is picked up by a TaskMan process called the Submanager The Submanager is the job that actually runs each task Submanagers handle contention for partitions and I O devices by running the waiting tasks in order first the oldest tasks and then the more recent ones Queuers Tasks run by TaskMan begin with code in an software application that decides to perform some work in the background This code is a queuer Most applications in VistA respond to a user s request to queue some output but other decisions may be involved Two commonly used queuers are programs that create report output by using the TaskMan API and options that are scheduled through the OPTION SCHEDULING file 19 2 July 1995 Kernel Systems Management Guide 20 1 Revised June 2008 Version 8 0 TaskMan System Management Overview Programs that Use the TaskMan API One commonly used queuer is an application s call to the TaskMan API to queue tasks In this process the queuer defines the task and its environment Applications are not allowed to do direct manipulation of the A ZTSCH and ZTSK globals The TaskMan API consists of entry points that allow developers to create manipulate and inquire about tasks The most widely used entry point ZTLOAD lets developers queue tasks which involves creating and scheduling them First an application sets the variables that 7ZTLOAD needs to define the desired task
457. ne 7 20 DIPRINT Option 5 6 Direct Mode Utilities A G OS specific 28 1 AZTEDIT 28 3 Error Processing XTER 13 6 XTERPUR 13 5 Miscellaneous Programmer AYZTER 27 4 XUP 27 4 Routine Tools A RR OS specific 26 8 A RS OS specific 26 8 Index Z 26 5 A Z TPP 26 6 A LZTRDEL 26 8 XINDEX 26 3 XTFCE 26 5 AXTFCR 26 5 AXTRCMP 26 7 XTRGRPE 26 5 AXTVCHG 26 6 AXTVNUM 26 6 TAPE XTRCMP 26 7 TaskMan AZTMON 22 11 RESTART ZTMB 21 18 Verification Tools ANZTER 27 4 AXTER 27 4 AXTERPUR 27 4 AXTTER 27 4 CHCKSUM XTSUMBLD 27 4 DISABLE USER Field 3 24 DISEARCH 5 6 Disk Space Concerns 12 6 Display Attributes 3 5 Delegated Options 9 11 Help Frames 12 1 Nodes 7 16 7 17 Options 7 6 Description 6 5 Help 6 2 Order 7 3 Status of Tasks 19 4 Display Menus and Options Menu 7 5 DISPLAY OPTION Field 7 3 7 7 Display Patches for a Package Option 24 7 Display status Option 19 4 DISPLAY TEXT field 02 10 10 Display User Characteristics Option 2 11 8 1 Display Edit Help Frames Option 12 4 12 6 DISTATISTICS Option 5 6 Distributions Definition 23 1 Global 23 6 23 7 KIDS 23 2 23 6 Standard 23 6 23 7 Transport Mechanism 23 5 DISUSER Field 3 22 3 24 3 26 DISV Global 3 25 5 10 5 11 5 13 5 15 KILLing 5 11 5 13 DITRANSFER Option 5 6 5 7 July 1995 Kernel Systems Management Guide Index 7 Revised June 2008 Version 8 0 Index DIUTILITY Menu 5 6 DIVIS
458. ne must be an extrinsic function that returns a positive value The CPU with the highest value is the one that will run new tasks Cache Algorithms e Cache2 s Returns the TCPIP metric e Cachel Returns the Available jobs Each CPU performing load balancing compares its current CPU capacity with that of the other nodes running Managers If the current CPU has a lower rating than the other CPUs it puts itself in a BALANCE state and waits to let the other CPUs take up the load before running more jobs itself Submanagers will try and wait until there node is running before testing if they should exit 21 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration Monitor Taskman Option On a system where multiple managers are running the Monitor Taskman option XUTM ZTMON shows a combined view of the operation of multiple managers If the current node the one where you are running the Monitor Taskman option has a lower rating than other nodes Monitor TaskMan will show that the current node is ina BALANCE state Device Handler s Influence on TaskMan Certain DEVICE file 3 5 fields strongly affect TaskMan s behavior System managers should keep these effects in mind as they configure their systems devices VOLUME SET CPU If the VOLUME SET CPU field is not filled in TaskMan considers this device to be available from all Volume Sets If it is filled in T
459. ned in the User s Toolbox menu and the chapters in this manual where each option is described Electronic Signature code Edit XUSESIG Menu Templates XU SPL MENU Spooler Menu XU SPL MENU locked with XUMGR security key TaskMan User XUTM USER User Help KUUSERHELP accesses online help Table 2 1 User s Toolbox menu options and documentation references Change my Division Option The Change my Division option XUSER DIV CHG allows users to select from a list of divisions if any stored for that user in the NEW PERSON file 200 2 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security User Interface Edit User Characteristics Option The Edit User Characteristics option XKUSEREDITSELF is one of the options available from the User s Toolbox menu It allows you define some characteristics of your online environment via ScreenMan as shown below Figure 2 8 Edit User Characteristics ScreenMan form EDIT USER CHARACTERISTICS NAME XUUSER ONE PAGE 1 OF 1 INITIAL PHONES Jabok Doamna NICK NAME OFFICE PHONE VOICE PAGER DIGITAL PAGER ASK DEVICE TYPE AT SIGN ON DON T ASK AUTO MENU YES MENUS GENERATED TYPE AHEAD ALLOWED TEXT TERMINATOR PREFERRED EDITOR SCREEN EDITOR VA FILEMAN Want to edit VERIFY CODE Y N EXit Save Refresh VANSE Enter a command or followed by a caption to jump to a specific field Press lt PF1 gt H for help There are
460. nedasadetincs sation saesat a otisaitauacbuetausbintea 23 2 PIS EPIOUUILONS ses seciesncetiadane cen T are see en E T T nasa 23 2 Insta laiton 25525553 ssnesndetsheeatascanans sages aaa stionn des cnmeaceactpes dna A 23 3 Bild Enties and the BUILD HIES HI O ic veck inccsiiiias cabiincdaad EAA 23 4 Da ho O S ai Te AO T eee eee T etre een terry earnest 23 4 Changes in the Role of the PACKAGE File 49 4 ccc cccccsssssssseeeeeeeceeeeeeeeeeeaaeseeeessesseseees 23 5 Transport Mechanism Distributions scseericronoena n A 23 5 Two kinds OF DiS HOU ONS reni R E cae sakes 23 6 What Happens to DIFEROM Saioen cncanscreeec ne E E E EE 23 6 lostaline Standard DIS TIDUUON Sirsi E A E 23 7 E CANT AGIOM OCMC E EE E E A EE E E E E E A 23 7 Tasalli onr Ment eesse ddaet nae hace tune teh atone delet hashes ata fohiaten i ddaneree el 23 8 L a dins a Standard 1S ri DU OM asss tans lanaaiesdattecosatentededat tina tiaeeahenaetasnsane 23 9 Loading Transport Globals from a Distribution ccccccssssseseeeeeseeeeceeeeeeeeeeeaaaaags 23 11 Verifying Checksums in a Transport Global 20 0 cceccccccccessseeeeeeeeeeeeaeeseeeceeeeeeeeaeeeeees 23 12 Printing Loaded Transport Globals secre vs netearontitgoeh inci acnaetinncievaccen cane GM EE 23 12 Comparing Loaded Transport Globals to the Current System ceeeeeeeeeeeeeeeeeeeees 23 13 Backing Up Transport Globals sodacxcescasasensiciscanadaoxaetSecnantesseandanedchodaadswasaetth dveadesaacsehoadheas 23 15 Ronn
461. nensessandanseubmusaneneaes 10 4 S mosates AG AlS asa E a E e a a 10 4 Sy Ste ta M aia e E eaaa e E AA E E A 10 5 Aler Manas cement Men s masisi a a a e a 10 6 EE SNCT ODON aa eee ta teen en E E TEE E T 11 1 System Mands menl caera ca venas Seareaatnceceams wise netmna aasiecacenceases 11 1 Wiat 18 2 Server OPIO esie a A N 11 1 Whare anr Serve OpUonS DO seneese a bess valhtontas wasp weedeat tie 11 1 Can Server Requests Be Denied ecirar a A 11 1 How Can the Number of Instances of a Server Option Be Controlled eee 11 2 Soine Upa Serner OPIO aise Mi abielushlsd suited vad erlaasccesiuin Ab tse uansiaesencaousedansedeaieg 11 3 Testing if a Site is Reachable XQSPING Server Option cceccccccccccceesseeeeeeeeeeeeeaeeees 11 5 Testing a Server Optom X OSCH Kerana nr a a r 11 6 Errors and Warnings from the XQSCHK Server Option ccccccccccccccesseeeeeeceeeeeeeeeeeees 11 8 12 FCI PROCESSOR stescian tet etaeotihl aceena tues sal inti aa ees aun ue hatin sash deco ceanddnnl ea cess 12 1 User Toter dC eana a a a 12 1 Heip Frames ain tie Meri Sy eiere A A AA 12 2 Systemi Mana emen ensia a a a a S 12 4 Display edit Help Frames OPUOM euriari ea 12 4 kist Help Frames Opuohessnnanaa a a E A 12 4 NewReyised Help Frames QU Oi seisena a ra 12 5 Cross Reference Help Fraimes Optom ics tania chacaapitcoy sss Shag E a 12 5 Fix Help Frame File Pointers Option Deleting Help Frames ceeeeceeeeeeeeeeeeeeees
462. ng These listings use the same format as that of the List Tasks option and show you the contents of the lists at the time you look at them The One Waiting List listing prompts you to select a device and the help for that prompt lets you see those devices that have tasks waiting Many of these lists change very quickly July 1995 Kernel Systems Management Guide 22 11 Revised June 2008 Version 8 0 TaskMan System Management Operation Thus it is not unusual to enter the help with the intention of seeing the task that was shown by the main screen to be in the Job List only to be informed by the help software that the Job List is now empty These kinds of experiences are simply part of troubleshooting TaskMan While these monitor actions are useful there are still times when you must leave the monitor to follow up on information you saw there For example you may want to check the list of unsuccessful tasks or to list a specific task both these actions require using the List Tasks option Taken as a whole the checks that make up the monitor can save you a lot of time in trying to evaluate TaskMan s status The example shown in Figure 22 9 is of a healthy and not very busy Manager Monitors at sites usually show considerably more activity especially in the Waiting Lists 22 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Check Taskman s Environment Option Figu
463. ng requirements is selected for further processing e Users not terminated e Users with an Access code e Users with a VA FileMan Access code 1 e FILE MANAGER ACCESS CODE field 3 in the NEW PERSON file 200 e Users with a FILE MANAGER ACCESS CODE field 3 in the NEW PERSON file 200 not equal to The user s FILE MANAGER ACCESS CODE field 3 in the NEW PERSON file 200 is parsed Each symbol character is compared with the list of files in the SUTILITY J global All files that have a protection code matching this symbol character are added to the user s ACCESSIBLE FILE Multiple field 32 in the NEW PERSON file 200 If the symbol character is used as the file s DATA DICTIONARY DD file security the user is granted DD access if it is used as LAYGO the user is granted LAYGO access and so on 3 Files accessed by the user through options since the last time the DISV global was KILLed are added to the user s ACCESSIBLE FILE Multiple field 32 by the processing of the DISV global Entries in DISV that meet both of the following requirements will be added to the ACCESSIBLE FILE Multiple field 32 with READ access e The file must not be in VA FileMan s file number range 1 e file number must be equal to or greater than 2 e The user does not already have access to this file File Access Security Conversion Instructions 1 Identify unprotected files and assign protection codes as desired as
464. ng System File a manager account global distributed with Kernel to provide an interface between VistA software and the underlying operating system This global is built during Kernel installation when running the manager setup routine ZTMGRSET The nodes of the global are filled in with operating system specific code to enable interaction with the operating system Nodes in the ZOSF global can be referenced by VistA application developers so that separate versions of the software need not be written for each operating system REF For a comprehensive list of commonly used infrastructure and security related terms and definitions please visit the Glossary Web page at the following Web address http vaww vista med va gov iss glossary asp For a comprehensive list of acronyms please visit the Acronyms Web site at the following Web address http vaww vista med va gov iss acronyms index asp 6 Glossary Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Index Cache2 Algorithm 21 12 S STEST DDBRT API 18 3 S HOROLOG Variable 22 8 22 9 22 29 I Field DEVICE File 3 5 15 1 15 2 15 3 15 4 15 10 15 12 15 13 16 2 17 9 18 10 18 13 18 14 18 16 22 33 22 35 STACK Variable 13 4 ZC Calls 13 6 G Utility 28 1 Index of Routines Option 26 2 RFIND Utility 26 2 RR Routine 26 8 RS Routine 26 8 ZTPP Utility 26 6 ZTRDEL Routine 26 8 A A G OS spec
465. ng these codes to anyone including family friends fellow workers supervisor s and subordinates for ANY reason T understand that I may be held accountable for all entries changes made to any government AIS using my passwords I am aware of the regulations and facility AIS security policies designed to ensure the confidentiality of all sensitive information I am aware that information about patients or employees is confidential and protected from unauthorized disclosure by law I understand that my obligation to protect VA information does not end with either the termination of my access to this facility s systems or with the termination of my government employment I will exercise common sense and good judgment in the use of electronic mail I understand that electronic mail is not inherently confidential and I have no expectation of privacy in using it I understand that technical or administrative problems may create situations which requires viewing of my messages I also understand that facility management officials may authorize access to my electronic mail messages whenever there is a legitimate purpose for such access I understand that a violation of this notice constitutes disregard of a local and or VHA policy and will result in appropriate disciplinary action as defined in VA employee conduct Regulations VAR 820 b as well as suspension termination of access privileges I affirm with my signature that I have read underst
466. ng to press the lt Enter gt key at page breaks Queuing At the DEVICE prompt if you enter a device s name the output goes directly to that device If the output you re sending is for example a long report this ties your terminal up until the report finishes printing to that device You can print output and yet keep your terminal free for other processing by queuing your jobs rather than running them directly As described in the TaskMan User Interface chapter you can queue output by entering Q at the Device prompt The device prompt is then presented a second time so that you can specify the output device Figure 14 7 Specifying a device and queuing a print job Sample user dialogue 1 of 2 DEVICE Q DEVICE DVNM5 REQUESTED TIME TO PRINT NOW lt Enter gt REQUEST QUEVED Task number 856103 July 1995 Kernel Systems Management Guide 14 3 Revised June 2008 Version 8 0 Device Handler User Interface Alternatively you can still specify the device first The Device Handler checks to see if the device is available and if so asks you if you want to queue your output If the device cannot be reached at the current time Device Handler indicates that the device is busy or unavailable You can avoid the preliminary availability check by entering Q at the first prompt see Figure 14 7 Figure 14 8 Specifying a device and queuing a print job Sample user dialogue 2 of 2 DEVICE DVNM5 DO YOU WANT YOUR O
467. nge the output device for this task NO Y Select Task s Output Device for none P236 When should this task run AUG 16 2004 22 00 lt Enter gt Task s purpose DEVICE LIST lt Enter gt 161776 DEVICE LIST P236 Next run time AUG 16 2004 22 00 Shall I reschedule this task as shown YES lt Enter gt Task rescheduled Listing and Printing Tasks You can use the List own tasks option L to review your tasks This option displays the same list as that given when you enter two question marks at the Select Task prompt The Print task option lets you print out the description of the task that you have currently selected July 1995 Kernel Systems Management Guide 19 5 Revised June 2008 Version 8 0 TaskMan User Interface Selecting Another Task Once in the TaskMan User option you can choose to work with a different task by using the Select another task option SE Enter another task number to work with a different task If you re not sure what task you want to work with you can get a list of all of your tasks by entering two question marks PI Summary Most output in VistA is performed by creating tasks that run in the background Once you become familiar with TaskMan s queuing system you can increase productivity by using some of TaskMan s special features including listing your future tasks displaying a task s status stopping a running task and editing a future task s run time and output de
468. nk Java based components e g Computerized Patient Record System CPRS or Care Management With this type of authentication interface users are presented with a GUI signon dialogue box Users can click in or tab to the Access and Verify code entry fields and press an OK button REF For a sample of the RPC Broker signon dialogue box and more information on RPC Broker please refer to the RPC Broker documentation located on the VHA Software Document Library VDL at the following Web address http www va gov vdl application asp appid 23 July 1995 Kernel Systems Management Guide 2 1 Revised June 2008 Version 8 0 Signon Security User Interface e Web based applications This includes Web based applications that use a client Web browser and Kernel Authentication and Authorization Java 2 Enterprise Edition KAAJEE to access Kernel on the VistA M Server e g Blind Rehab With this type of authentication interface users are presented with a GUI signon dialogue Web page Users can click in or tab to the Access and Verify code entry fields and press an Login button REF For a sample of the KAAJEE signon dialogue Web page and more information on KAAJEE please refer to the KAAJEE documentation located on the VHA Software Document Library VDL at the following Web address http www va gov vdl application asp appid 151 Your Access code establishes your unique identity to Kernel Your matching Verify code corroborates your i
469. nk to the Oakland OIFO is working properly you could address a message to SKXUGPINGUISC SF VA GOV July 1995 Kernel Systems Management Guide 11 5 Revised June 2008 Version 8 0 Server Options If the text of the message and the subject are simply the line Testing you should get the following message in return Figure 11 1 Sample message received when pinging a domain address MailMan message for User2 JOHN COMPUTER SPECIALIST Subj PING reply toi TESTING F999 20 Nov 92 2317 T Line From PING SERVER in IN basket Testing The XTSPING utility copies the message addressed to it and returns it to the person who sent it Testing a Server Option XQSCHK You can use the XQSCHK server option to return information about a server option on a remote system You should list the server option you want to test in the text of the message addressed to XQSCHK The subject of the message sent to the XQSCHK server option is not important However the body of the text must contain the name of the server option to be checked When you specify the server option to be checked do not precede the server option name with an S instead list the server option s name exactly as it appears in the OPTION file s 01 field The XQSCHK server option returns Fields 220 to 225 from the OPTION file 19 to show how the option has been set up In addition several other things about the option are investigated and error or warning messages m
470. nna a Gated aba Mates a tid alates 22 22 Table 22 2 Option Scheduling frequency Code fOrmal cseessseccccccccesesssecccccecaeeeeseececceesaaeeesseeeess 22222 Table 22 3 Day codes used in Option Scheduling frequency code formats cccccccccssesseeeeeeeeeeees 22 23 Table 22 4 Examples of Option Scheduling frequency code formats ccccccecessseeeeeeeeeceeeaeeeeeeeees 22 23 Lable 22 5 o7 LS CE ASCHEDULE Pile MOGGS cs jartect cabinet a anes eae iaenert 22 27 Table 22 6 Task Mati ask Stalls COUES sans spsuesasasauransesnussanasiQeacasiebens op sacasdasctbaaceaeass casement eecasaceberaeenxe 22 32 Table 22 7 Task Mant e eCHOm Me SSA GCS aa a chad eased cadssiness 22 35 Table 2226 Paskivian PAUSE States isa tate ascertain a ahaa eae ete cu basecaes 22 37 XXX Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Figures and Tables able 2 229 TaskM am RUN Sta ES scan dts vapesinc N RN 22 37 Table 23 1 KIDS related terms and Ge mmntitionss sensira ie isso oleae WA Sao 23 1 Table 29 1 Minimum M implementation features required for the XGF Function Library 29 1 July 1995 Kernel Systems Management Guide XXXI Revised June 2008 Version 8 0 Figures and Tables XXXI Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Orientation How to Use this Manual Throughout this manual advice and instruction are offered about the numerous tools and fu
471. nning the Conversion 5 10 System Management 5 3 User Interface 5 1 When is File Access Security Checked 5 3 Who Needs File Access 5 4 WRITE 5 1 5 4 5 7 7 2 WRITE Access 3 20 FILE MANAGER ACCESS CODE Field 3 3 19 3 20 3 24 3 26 5 2 5 3 5 4 5 7 5 8 5 10 5 11 5 12 5 13 7 2 8 3 9 5 15 8 FILE RANGE Field 3 22 FILE SERVER Type Obsolete 21 7 FileMan Browser Device 18 1 Limited File manger Options Build Option 9 5 Line Editor 2 10 3 20 3 21 5 2 5 5 Menu 5 1 Screen Editor 2 6 3 5 3 20 3 21 What Happened to DIFROM 23 6 FileMan edit template Option 11 3 FileMan Inquire to File Entries Option 25 2 Files Adding Explicit File Access for IRM 5 11 AGENCY 4 11 3 6 ALERT 8992 10 5 10 6 10 7 10 8 10 9 10 10 ALERT TRACKING 8992 1 10 3 10 5 10 6 10 7 10 8 10 9 ALTERNATE EDITOR 1 2 3 20 AUDIT 1 1 5 8 Audit Access 5 8 AUDIT LOG FOR OPTIONS 19 081 7 4 11 1 11 4 BUILD 9 6 23 1 23 4 23 12 23 17 23 21 24 7 24 9 24 11 24 12 26 7 BULLETIN 3 6 11 4 11 8 CPT 81 25 1 DA RETURN CODES 3 22 3 5 15 11 Global Location 15 1 DCL Command 21 5 21 15 DEVICE 3 5 1 2 3 1 3 2 3 3 3 4 3 5 3 20 11 2 11 5 15 1 15 2 15 6 15 7 15 8 15 9 15 10 17 9 17 10 18 3 18 6 18 8 18 13 18 14 18 15 18 16 18 18 20 7 21 13 22 20 Index I Field 15 1 15 2 15 3 15 4 15 10 15 12 15 13 16 2 17 9 18
472. nssacaiewinacd Meenas satenignceeanaebeeceaanetens 22 26 Pisure 22525 A SC Ei Galo Dal SNC e a a ceased hinateatGlanbaamohaniennlaeasrerdaasans 22 30 July 1995 Kernel Systems Management Guide XXVIl Revised June 2008 Version 8 0 Figures and Tables Figure 22 29 TASKS File 4714 4 nodes 1 Of 2 ai i OA 22 31 Fieure 22 30 TASKS Pile 144 nodes 2 OF 2 suse soisspasssvatulisiouea aos vsceeen ilaa waa vacates debates ncntbeen doeameaenke 22 31 Fisure 2521 gt KMS MenusO proms eae A a sed aeiadaneanennaogneenesseoeneasowons 23 2 Figure 23 2 Edits and Distribution Menu Options cccccccccccccecceeeeeeeeeeeeeeeeeeeeeceeeeeceeeeeeeaeaaaeeeeeeeeeees 23 3 Pisure 25 5 nstallationemenu Won ci shes cocacateckie E te ska ae weno we Sasa sace cee nea ee aads 23 3 Figure 2 5 4 KIDS tle Gia a sericea sassadawelssameban nace cient acesaiastasedatsansbancoaledag saasaiastedecah tianoelemensbicjeicasea ts 23 4 Figure 23 5 KIDS Installation menu Option cccceeeeeeeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 23 8 Figure 23 6 Load a Distribution option Sample user dialogue cc ceeeccccccccceeeeeeseeeeeeeeeaaeeeeeeeeees 23 10 Figure 23 7 Loading transport globals from a distributton FIOWchalt cccccccceceeeeeeeeeseeeeeeeseeees 23 11 Figure 23 8 Print Transport Global option Sample printed transport global cc ceeeseeeeeeeeeeeees 23 13 Figure 23 9 Compare Transport Gl
473. nt Guide 28 3 Revised June 2008 Version 8 0 Miscellaneous Programmer Tools When editing a question mark can be entered to provide help The dot commands are listed first They provide the usual break join insert and remove functions The n method of selecting lines to edit is also noted The line tag can be used along with a number e g TAG 3 to reach a particular line A mom minus sign will back up lines And the asterisk can be entered to reach the last line Figure 28 4 Z Editor Listing edit commands gt X SZ Edit ACTION menu BREAK line CHANGE every FILE routine INSERT after JOIN lines MOVE lines REMOVE lines SSEARGH TOr TERMinal type XY change to from replace with TO EXIT THE EDITOR n Absolute line n n To advance n lines n To backup n Lines use to get last line NAME to edit a GLOBAL node NAME to edit a LOCAL variable MUMPS command line mumps command lt space gt or Z command lt space gt Help displays information about editing in line mode A complete line is displayed and various keys can be used to navigate The lt Spacebar gt moves forward by words the period moves forward by characters and the lt CTRL H gt command key sequence moves backwards by characters Upon reaching the desired location the lt Delete gt key can be used to remove characters To enter characters the character E must first be entered as an insert delete toggle Pre
474. nt out the definitions of the transport globals using the Print Transport Global option XPD PRINT INSTALL This way you can see every component exported in each transport global before you install them 23 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations Figure 23 8 Print Transport Global option Sample printed transport global PACKAGE ZXG DEMO 1 0 NATIONAL PACKAGE DESCRIPTION ENVIRONMENT CHECK ZXGENV PRE INIT ROUTINE ZXGPRE POST INIT ROUTINE AXGPOS ROUTINE ZXGCO0O0 ZXGCOL ZXGCOZ2 ZXGCMOVE ZXGCTEST ZXGCTW1 ZXGCWE ZXGCXMP 1 ZXGCXMPL ZXGDEMO ZXGKC ZXGLMSG ZXGLOAD ZXGTIMP INSTALL QUESTIONS SUBSCRIPT PREL DIR 0 YA DIR A Do you want to run the pre install conversion DIR B YES DIR Answer YES to run the pre install conversion NO to skip it Comparing Loaded Transport Globals to the Current System When you have loaded transport global s from a standard distribution onto your system you can also compare a transport global to the matching software already installed on your system if any using the Compare Transport Global to Current System option XPD COMPARE TO SYSTEM This way you can compare the software you are about to install with the current version of the software on your system When this option finds differences it notes the change by displaying the differences between the current software and
475. ntain documentation of the system s response to erroneous input In certain instances in order to preserve the integrity of previously entered data the system does not allow the entry of a caret sometimes referred to as an up arrow This might not be documented The following chart provides assistance in answering prompts related to device selection Standard Device Chart STEP Figure 25 2 Standard Device Chart IF USER AT THIS PROMPT ANSWERS WITH 1 25 4 DEVICE Device name number from your DEVICE tile 3 9 for report CO print on Q UEUE to have report queued to print at a Later date time lt Enter gt for report to Print on your screen Up arrow lt gt DEVICE Device name number from your DEVICE FILS 3 25 for report to print on Up arrow lt gt RIGHT MARGIN 132 lt Enter gt to accept default different RIGHT MARGIN Value or up arrow lt gt The next step depends on what you entered in Step 1 Device name number lt Enter gt screen WANT TO FREE UP THIS TERMINAL NO lt Enter gt to accept default Y ES to free up terminal during report processing and to exit from the system Up arrow lt gt REQUESTED TIME TO PRINT x lt Enter gt to accept default NOW Later date time for report process to begin Up arrow lt gt Tf lt Enter gt or later date time is entered the following message appears REQUEST QUEUED Return to the menu Kernel Systems Manage
476. nting File Access 5 4 Q Quality 14 6 Question Mark Help xxxv 2 4 3 6 3 21 3 22 5 2 5 9 6 1 6 2 6 3 6 5 6 6 6 9 7 7 8 1 12 2 12 3 12 7 13 3 13 4 13 6 14 2 15 3 19 3 19 5 19 6 22 5 22 11 23 16 Queuable Task Log Clean Up Option 22 17 QUEVED TO RUN AT WHAT TIME Field 22 19 22 20 22 21 22 23 QUEUED TO RUN ON VOLUME SET Field 22 19 22 20 22 22 Queuers TaskMan 20 1 Queuing Device Handler 14 3 Index File Access Specifications 5 10 Forced Queuing 15 4 KIDS Installations 23 17 Options 22 19 Output TaskMan User Interface 19 1 To a Hunt Group Device 18 8 To Slaved Printers 18 18 To the Spooler 17 1 QUEUING Field DEVICE File 3 5 15 4 QUEUING REQUIRED Field Multiple 7 11 R Reactivate a User Option 3 26 Reactivating Users 3 24 3 26 READ Access 3 20 5 1 5 4 5 6 5 7 5 11 5 15 7 2 Reader Assumptions About the xxxvi Re answering Installation Questions KIDS 23 17 Reasons to Retain BUILD and INSTALL File Entries KIDS 24 9 Rebuilding Primary Menu Trees 7 13 Recover Deleted Option Set Option 7 10 Recovering from an Aborted Distribution Load KIDS 23 20 Redefining Common Menu 7 7 Reference Materials xxxvi Reindex the users key s Option 8 5 Reindexing All Users Security Keys Option 8 5 Rejection Messages TaskMan 22 35 Release user Option 3 27 REMOTE PRINTER NAME Field 67 15 7 Remove Error Screens Option 13 4 Remo
477. nu Manacer User MENICE cecen a aia nsa eto haa eel la naa wea 6 1 Navicatine Kernel S Menis rensie e A E 6 1 CHOO me OPUON cerce ease nce augue cen aneo che yensactsarauseeeanaanawetees 6 1 Entering One Question Mark to List Options sseseessssssssoeerssssssseerrsssssssererssssssseeressssssss 6 2 Entering Option to Display Option Help cc ecccccccccccceesseeeeceeeceeaeeessececeeeeeaaeeeeeceees 6 2 Entering Two Question Marks to List Secondary and Common Options ccseeeeeeees 6 3 Entering Three Question Marks to Display Option Descriptions cccccccceceeeeseeeeeeees 6 5 Jumpine to Options C Uparrow Jamp Jesrea hs cicevassaeavacbatheesdstucecten tideeend eeaas tiated 6 5 KUDDE Dand Jomp eosi errr ter nent re nt mn O 6 6 COMON a toot nguiaciaseo ches asseaceane geen tesaacetaney eeeanaarameees 6 7 Men Templates pion sigs sicpet sb aanes siete a aah nia S E 6 8 7 Menu Manager System Management coy sciicccoact co teases i E a a 7 1 Ferne INC i Sosa sh sche set sCas wan cecectat aa a aa a a a 7 1 Creatine Menus anid OPHONS 6 sc5 c lt cnsit con testrdcca nents E a E a 7 2 If the Option Invokes Non VistA Applications cccccccccccccesseseeeccceceeaeeesseeceeeeeeaeaseeeees 7 4 If the Option Should Be Regularly Scheduled cccccsecccnssssssssssseeeeeeeeeeeeeeeeaaas 7 4 AUT OPU OmU Se carta tsi A en tacce ese tina aaa ante iis T ees acute 7 4 Display Mienus and Options lem ssr makens E E A
478. ny user s tasks and start by prompting the holder for the user whose tasks should be shown Other than that they are identical to the selections used by normal users 22 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Operation Although each submenu option choice shows a different set of tasks the format for the output is the same Here is a sample display from the All your tasks suboption Figure 22 3 All your tasks suboption Sample of TaskMan tasks running All tasks that you created 2572 ALIVE XINDEX XINDEX of 1 routine Device OMS 17P VAH KXX From TODAY at 10 55 By you Scheduled for TODAY at 12 05 End of listing Press RETURN to continue In the upper left hand corner of each entry is the task number What follows the task number is either an option name e g XUTM QCLEAN or a routine entry point e g ERROR ZTMZT depending on whether the task was a queued routine or a queued option This is generally followed by a description of the task The device to which the task was queued if any along with the account in which the task was is scheduled to run complete the first line The next line contains the time the task was created followed by an identification of the creator In the case of tasks that requeue themselves this date and time represents when the task was last requeued When the creator s DUZ number is not listed in the NEW PERSON file 200 the
479. o go home to the menu that is displayed at signon and is called the Go home Jump is no attempt to protect variables that can be SET or KILLed via Entry or Exit Actions as you jump through the menu tree Thus the Rubber band Jump can be inappropriate under certain circumstances since it could cause significant alteration of your environment N CAUTION It is important to note that when you invoke the Rubber band Jump there Common Menu The Common menu is designed as a collection of options that are available to all users The standard Common menu items are e User s Toolbox As described in the User s Toolbox Menu topic in the Signon Security User Interface chapter the User s Toolbox is a menu containing options that allow users to control some aspects of their computing environment e Halt Continue Restart Session As described in the Signon Security User Interface chapter in this manual these options are three different ways to log out of the system e View Alerts As described in the Alerts and Signon Security User Interface chapters in this manual View Alerts is an option that lets you process Alerts e Time The Time option simply displays the date and time e Where am I This option lists information identifying what computer system you are signed into e g UCI Volume Set Node and Device July 1995 Kernel Systems Management Guide 6 7 Revised June 2008 Version 8 0 Menu Manager User Interface
480. o create INPUT SORT or PRINT templates can create menu options for their users that directly call these templates Characteristics of Intended Users The Limited File Manager Options Build option XQSMD LIMITED FM OPTIONS is designed for delegates such as some application coordinators who have VA FileMan access to a set of files and can create INPUT SORT or PRINT templates These delegates may have the VA FileMan options for editing or printing without the ability to modify data dictionaries They may also have explicit file access to a specified set of files via the File Access Management system Typically they would be working without the special FILE MANAGER ACCESS CODE field 3 DUZ O IRM Setup to Enable Building Options from Templates To allow a user to create menu options from VA FileMan templates IRM must first assign to the user e Delegate s Menu Management menu XQSMD USER MENU e XQSMDFM Security Key e A namespace in which to create options Do this with the Secure Menu Delegation option Specify Allowable New Menu Prefix XQSMD SET PREFIX This forces any options created by the user to be namespaced with the assigned namespace appended with a Z appended with an option name Building Options The tool for building options with VA FileMan templates is called the Limited File Manager Options Build option XQSMD LIMITED FM OPTIONS It is part of the Delegate s Menu Management menu under the Secure Menu Management men
481. o create options of a type other than Menu please refer to the Menu Manager Developer Tools chapter in the Kernel Developer s Guide July 1995 Kernel Systems Management Guide 7 3 Revised June 2008 Version 8 0 Menu Manager System Management If the Option Invokes Non VistA Applications If you create an option that invokes non VistA applications e g WordMan or CalcMan include a call to the Device Handler with the code D HOME ZIS in the EXIT ACTION field of the OPTION file 19 so that the required IO variables will be present when leaving these options Do the same for any other utility that is known to KILL IO variables upon exit If the Option Should Be Regularly Scheduled If an option should be regularly scheduled to run through TaskMan you must set its SCHEDULING RECOMMENDED field 209 in the OPTION file 19 to YES You will not be able to use Schedule Unschedule Options to schedule an option unless this field is set to YES for the option Auditing Option Use Figure 7 4 Auditing menu options SYSTEM MANAGER MENU EVE System Security XUSPY Audit Features XUAUDIT MENU Maintain System Audit Options XUAUDIT MAINT Establish System Audit Parameters XUAUDIT Audited Options Purge XUOPTPURGE Audit Display 2x XUADISP Option Audit Display XUOPTDISP You can establish an audit on options to record every time an option is used You can do this with the Establish System Audit Para
482. o see a system status listing Enter to see this message Enter to inspect the tasks in the monitor s lists These actions see Figure 22 10 attempt to bring together those utilities used most often in response to seeing a monitor screen Updating is the most commonly used choice since you often want to watch how the lists change over time The TASKMAN ERROR file needs to be easily accessible not only in case the Manager enters an Error state but also if a task that should take a long time to run leaves the Job List but never shows up in the Task List This usually means the task hit an error and quit which can be confirmed or disproved by a quick glance at the Taskman Error Log The System Status Report can be used to verify that tasks Submanagers and the Manager are indeed running as the monitor suggests Some actions at the Monitor Action prompt are not accessible when monitoring TaskMan from the manager s account using the direct mode utility D ZTMON Inspecting the Tasks in the Monitor s Lists If you are in a non library account you can directly inspect the contents of the various lists Do this by entering two question marks at the Enter monitor action prompt You get the following list of choices Figure 22 11 Options for inspecting tasks in the TaskMan Monitor s Lists Help For Monitor Taskman Option Schedule List Waiting Lists One Waiting List Job List Task List Link Lists Select Type Of Listi
483. ob Installation task created at time you specify Abort Up arrow Installation out Run job Installation runs KIDS removes directly immediately using transport global s the current device from XTMP 23 18 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Question Device for Installation KIDS System Management Installations Installation Progress If the device selected for output is a VT100 compatible or higher terminal KIDS displays the installation output in a virtual window on the terminal Below the virtual window a progress bar graphically illustrates the percentage complete that the current part of the installation has reached KIDS is able to report progress for the installation of files and for all components PRINT templates forms help frames routines options etc KIDS lists those compiled cross references INPUT templates and PRINT templates that were created during the install process KIDS does not show progress for installing data nor for pre and post install tasks On all other devices progress is reported using dots Figure 23 13 Installation progress Sample output TEOT aa Installing Routines Oct 077 20048015400702 Installing PACKAGE COMPONENTS Installing PRINT TEMPLATE Oct 07 2004 15 00 04 Updating Routine file The following Routines were created during this install ZZR4 Updating KIDS files TEST 1 1 Installed Oct 07p 20040T5400
484. obal to Current System option Sample comparison output 23 14 Figure 23 10 Compare Transport Global to Current System option Sample comparison output in COUA TORMA Foar er A E a 23 15 Figure 23 11 Queued KIDS installation Sample installation task 00sssseeeeeeneeeeeeessesssssssssssseerreeee 23 17 Figure 23 12 Answering installation questions for a distribution Flowchartt s seeseeeeeeeeeeeeeeeerreeen 23 18 Figure 23 13 Installation progress Sample Output ssseeeeessssssoereerrssssssscerrsssssssceressssssseeeresssssseeeee 23 19 Figure 23 14 KIDS Global distribution Sample message ccceseeessccccccecceeeeeseeececceeeaeeeeeeeceeeeees 23 21 Figure 23 15 Installation of a global distribution Load a Distribution option ceeeeeeeeeeees 23 22 Freure 24 1 KIDS Utilities menu plons ois visti nn Sota oad easels Svea eis ws eens Sean sseale Saale as Ren Rae nei 24 1 Figure 24 2 Build File Print option Sample Output cecccccccccccccceeeseeeecceceeeaeeeseeecceseesauaeeeeeceeeeeas 24 2 Figure 24 3 Install File Print option Sample Output siessen a rA r AA EE 24 3 Figure 24 4 Convert Loaded Package for Redistribution Sample user dialogue 1 of 2 24 5 Figure 24 5 Convert Loaded Package for Redistribution Sample user dialogue 2 of 2 00 24 5 Figure 24 6 Transport a Distribution Sample user dialogue ccccccececccccccececceeeeeeeeeseseeeeeeeeeeeeeees 24 6
485. ocesses This chapter introduces KIDS and describes some of the changes to the software export process The following definitions apply throughout the KIDS documentation Table 23 1 KIDS related terms and definitions Transport Global An exported software application stored in a global KIDS exports software i e package based on its definition in a build entry The transport global also contains the build entry and the PACKAGE file 9 4 entry if any for a given software application Build Entry An entry in the BUILD file 9 6 that defines the parts of a software application to export Also known as a build Component An element of one of the following types template PRINT SORT and INPUT form function bulletin help frame routine option security key and protocol Distribution A Host File Server HFS file containing transport global s If a distribution contains multiple transport globals KIDS treats them as a single installation when installing from the distribution Package A cohesive set of files data and components that together form a set of computing activities related to a functional area i e software July 1995 Kernel Systems Management Guide 23 1 Revised June 2008 Version 8 0 KIDS System Management Installations KIDS Options To get to the KIDS Kernel Installation amp Distribution System menu XPD MAIN locked with the XUPROG security key choose the Programmer Options menu option X
486. ogrammer access 1s less common now than in the past since alternative security measures have been developed It is still required for several critically sensitive checks however such as entering M code into VA FileMan files e g OPTION 19 and FUNCTION 5 files REF For more information on File Access Security please refer to Chapter 5 File Access Security in this manual and the VA FileMan Version 22 0 and Kernel Version 8 0 File Access Security supplemental documentation located on the VHA Software Document Library VDL at the following Web address http www va gov vdl application asp appid 5 PREFERRED EDITOR If a user s PREFERRED EDITOR field is NULL Kernel uses VA FileMan s Line Editor to edit word processing fields If the PREFERRED EDITOR is set to another entry in the ALTERNATE EDITOR file 1 2 like VA FileMan s Screen Editor Kernel uses that editor when the user edits word processing fields As described in VA FileMan s documentation users can switch from the Line Editor to another editor by using the Utility sub option on the Edit option menu 3 20 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management Figure 3 14 VA FileMan Line Editor Sample user dialogue Enter one space character on Line 1 and then press the 1 gt _ lt Enter gt lt Enter gt key at Line 2 2 gt lt Enter gt EDIT Option Utilities in Word Processing UTILITY Option Edito
487. old Job Nodes in the XUTL Option 7 12 7 13 Clean Old Job Nodes in XUTL 7 12 Clean Task File Option 22 17 Cleanup Task List Option 22 6 Clear all users at startup Option 3 4 3 8 3 27 Clear Electronic signature code Option 4 2 CLOSE EXECUTE Field TERMINAL TYPE File 3 2 14 7 15 8 18 6 18 16 18 18 CLOSE PRINTER PORT Field 18 16 18 18 Codes Access 1 1 2 1 2 2 2 3 2 4 2 5 2 6 3 1 3 2 3 6 3 10 3 17 3 18 3 19 3 24 3 25 3 26 3 28 3 29 3 30 5 9 5 13 11 9 15 8 Assigning 3 8 Log 3 29 Old 3 29 Purging 3 29 Verify 1 1 2 1 2 2 2 3 2 4 2 5 2 10 3 1 3 2 3 6 3 9 3 18 3 19 3 24 3 28 3 29 3 30 5 9 11 4 11 9 Defining 2 3 Log 3 29 Old 3 29 Purging 3 29 Commands SPAWN 20 2 21 5 JOB 20 2 21 3 21 4 21 5 22 29 USE 20 3 COMMERCIAL PHONE Field 3 22 Common Menu 2 3 3 19 6 3 6 4 6 5 6 6 6 7 6 8 7 1 7 7 7 8 8 1 8 5 10 1 17 3 17 7 19 2 Redefining 7 7 Compare local national checksums report Option 23 12 24 11 24 12 26 6 26 7 27 4 Compare Routines on Tape to Disk Option 26 7 Compare Transport Global to Current System Option 23 13 Compare Two Routines Option 26 7 Compare Merge File Entries Option 5 7 Comparing Loaded Transport Globals to the Current System KIDS 23 13 Comparing Routines Routine Tools 26 6 Components Build Entry 24 10 Definition 23 1 Exported 23 12 Installations 23 19 KIDS 23 12 Missing 24 11 Routine 24 10 Software 20
488. oler and should not be directly manipulated by IRM It holds identifying information such as the name of the spool document and the line count totals The document s text is stored in another file the SPOOL DATA file 3 519 in the XMBS global If the spool document is made into a mail message the text is moved into the MESSAGE file 3 9 the XMB global and the corresponding entry in the SPOOL DOCUMENT file 3 51 is deleted When initially creating a spooled document output is sent to the operating system s spooling area as defined in the spool device Kernel s spooler moves the output into XMBS when the operating system s spooling process is complete The status of the document a field in the SPOOL DOCUMENT file 3 51 is then changed from Active to Ready and the document can be accessed by the user Thus except during spooling the operating system s spool area should be empty Overflowing Spool Document Storage When the output is moved from the operating system s spool area into the XMBS global the lines are counted If during the count the user s maximum line limit is reached the transfer process is halted and a notification message is appended to the transferred text The entry in the SPOOL DOCUMENT file 3 51 is also marked as incomplete Thus the XMBS global is protected from growth expansion that could overflow the disk storage area The Kernel spooler cannot however count the lines of output as they are sent to
489. oler at the device prompt is controlled by one flag Another flag can enable the use of more than one device when despooling A third flag permits the conversion of a spool document into a mail message These three flags are user specific and are stored in the NEW PERSON file 200 As mentioned earlier the user oriented spooler options are distributed as part of the Common menu a menu available to all users If IRM has chosen to lock the Spooler Menu or remove it from the Common menu access to the options will need to be re established for users who are allowed to spool via the Edit User s Spooler Access option XU SPL USER as shown below Figure 17 12 Edit User s Spooler Access Sample user dialogue Select Spool Management Option Edit User s Spooler Access Select NEW PERSON NAME KRNUSER SIX ALLOWED TO USE SPOOLER YES lt Enter gt MULTI DEVICE DESPOOLING YES lt Enter gt CAN MAKE INTO A MAIL MESSAGE YES lt Enter gt Managing Spool Documents The remaining options on the Spool Management menu XU SPL MGR are also found on the user oriented Spooler Menu They are provided on the Spool Management menu simply for convenience to IRM to access any spool document on the system The only provision for access to all spool documents is holding the XUMGER security key Together these options along with the XUMGR security key permit IRM to view print or delete anyone s documents Figure 17 13 Spool Management menu options
490. on Recovering from an Aborted Distribution Load If you encounter an error while loading a distribution using the KIDS option to load a distribution from the export medium into the XTMP global you will be unable to re load the distribution until you clear out what was stored during the aborted load attempt To clear out the previously loaded distribution use the Unload a Distribution option XPD UNLOAD DISTRIBUTION To unload a distribution enter the name of the first transport global that was loaded when you loaded the distribution The entries in the INSTALL file 9 7 for all transport globals in the distribution will be removed and the transport globals themselves will be purged from the X TMP global Once you delete entries in the INSTALL file 9 7 and entries in the X TMP global with the Unload a Distribution option XPD UNLOAD DISTRIBUTION you should be able to reload the distribution in question If the install was already started and you choose to unload the distribution you first must edit 23 20 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations the INSTALL file 9 7 and set the STATUS field to Load From Distribution i e 0 prior to using the Unload a Distribution option XPD UNLOAD DISTRIBUTION Installing Global Distributions The second type of distribution supported by KIDS is called a global distribution This type of distribution unlike st
491. on Sample user entries cccccececeeeeeeeeeeseeeeeeeeeees 25 9 Figure 25 8 Add Entries To Look Up File option process chart 1 Of 2 ecceccccceeeeeeeeeeeeeeeeeees 25 10 Figure 25 9 Add Entries To Look Up File option process chart 2 Of 2 ccceeeeeeeeeeeeeeeeeeeeeeeeeeens 25 11 Figure 25 10 Add Entries To Look Up File option Sample user entries ccceeeeeeeeeeeeeeeeeeees 25 12 Figure 25 11 Add Modify Utility menu oOptions cccccceeeeccccccccecsesssseseeeeeeeceeeeecceceeesseseseess 25 13 Figure 25 12 Add Modify Utility option Shortcuts process chart 1 Of 2 cc ecceeeeeeeeeeeeeeeeeeeeeees 25 14 Figure 25 13 Add Modify Utility option Shortcuts process chart 2 Of 2 0 ceccccccccscssssseeeeeeeeeeees 25 15 Figure 25 14 Add Modify Utility option Keywords process chart ccccccccceeeeeeeeeeeeeeeseeessseeeeees 25 16 Figure 25 15 Add Modify Utility option Adding or editing a synonym process chart 1 of 2 25 17 Figure 25 16 Add Modify Utility option Adding or editing a synonym process chart 2 of 2 25 18 Figure 25 17 Shortcut option Samipleuser entries renens ranr E R SES 25 18 Figure 25 18 Keyword option Sample user entries ccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeens 25 19 Figure 25 19 Synonym option Sample user entries ccccccccccecececeeeaeeesesseseseeeceeeeeeeeeeeeeeaaaaeeeeesees
492. on 12 5 Assigning Access Codes 3 6 3 8 Display Order 7 3 File Number Ranges 3 22 Help Frame Editors 12 5 Options 9 3 Secondary Menus 7 7 Assumptions About the Reader xxxvi Attributes Editable by Users 3 23 Users 3 1 3 9 3 10 3 17 AUDIT Access 5 1 5 4 5 5 5 7 5 8 July 1995 Revised June 2008 Audit Features Menu 7 4 AUDIT File 1 1 5 8 AUDIT LOG FOR OPTIONS File 19 081 7 4 11 1 11 4 Audited Options Purge Option 7 4 Audits Failed Access Attempts 3 28 Option Use 7 4 Signon 3 28 AUTO DESPOOL Field 17 9 AUTO MENU Field 2 10 3 6 3 7 3 21 6 2 7 3 Auto Print Mode 18 15 Auto despooling 17 4 17 9 AUTO GENERATE ACCESS CODES Field 3 6 Automatically Deactivating Users 3 25 B B Cross references 18 8 22 30 BACK SPACE Field TERMINAL TYPE File 3 2 15 8 18 10 18 11 Background Jobs TaskMan User Interface 19 1 Backing Up Transport Globals KIDS 23 15 Backup a Transport Global Option 23 15 Backup Reviewer for Unprocessed Alerts 10 10 BALANCE State 21 12 21 13 TaskMan 22 36 Block Count Utility 12 6 BOX VOLUME PAIR Field 21 3 21 4 21 11 21 12 Browser Device 18 1 Storing Host Files in a Specific Directory 18 3 System Management 18 3 User Interface 18 1 BROWSER Device 18 1 BROWSER Type 18 3 Build a New Menu Option 9 4 9 11 Build Entries and the BUILD File 9 6 23 4 Build Entry Components 24 10 Definition 23 1 BUILD File 9 6 23 1 23 4 23 1
493. on 13 4 Show Error Log Option 22 25 SIGN ON LOG File 3 081 3 27 3 28 3 29 Purging 3 28 Taskman Error Log 13 2 20 6 22 11 22 17 22 24 22 25 July 1995 Revised June 2008 Menu 22 24 XUSCZONK Option Purging File 3 081 3 28 XUTM QCLEAN Option 22 24 Lookup type Cross reference 3 17 3 18 Loopback Test of Device Port Option 15 12 Low Usage of Alpha Beta Test Options Option 23 23 Magtape Devices 18 10 System Management 18 10 Mail Purging 3 26 MAIL CODE Field 3 18 Make an Alert on the Fly Option 10 7 Manager Startup TaskMan 21 11 TaskMan 20 1 20 2 UCI Definition 20 8 Managing Delegates 9 7 System Management 9 7 Display Attributes DA Return Codes 15 11 Menus and Options 7 7 Out Of Order Option Sets 7 10 Primary Menus 7 7 Spool Documents 17 7 Map Pointer Relations Option 5 6 MARGIN WIDTH Field 18 10 18 11 Mark Option Set Out Of Order Option 7 10 MAX SIGNON ALLOWED Field 3 1 3 3 21 3 MAX SPOOL DOCUMENT LIFE SPAN Field 17 8 MAX SPOOL DOCUMENTS PER USER Field 17 8 MAX SPOOL LINES PER USER Field 17 8 MENU item Field Multiple 7 1 Menu Management Menu 9 7 Menu Manager AUTO MENU 6 2 Diagramming Options 7 5 Display Options 7 6 Double Quote Jump 6 8 Fixing Option File Pointers 7 9 Go home Jump 6 7 Local modifications 7 8 LOGIN Menu Template 2 4 Menu jumping 6 6 Index Menu Tree Rebuilding 7 13 Options that Should Be Scheduled 7 12 Primary Menu 6 2 Rebuilding
494. on XUSERDEACT lets you temporarily or permanently disable access for users You can schedule termination of a user for a future date The Deactivate a User option loads a ScreenMan form with four fields described below DISABLE USER Setting the DISABLE USER field to YES prevents a user from signing on but leaves all of their menus keys and other attributes essentially the user s entire account still enabled It sets a field in the user s NEW PERSON file 200 entry called DISUSER You might want to use the Disable User feature to prevent access to your system by an external support person except during pre approved times where you may want to monitor their actions Setting DISUSER to YES prevents them from logging on to the system until you clear the field If you set Disable User to YES do not set any other fields in the Deactivate a User form they only apply to terminating a user Then to re enable access use the Reactivate a User option REF For a description of the Reactivate a User option please refer to the Reactivating Users topic that follows TERMINATION DATE Terminating a user is the way to formally deactivate a user as opposed to temporarily disabling their account Setting a TERMINATION DATE effectively terminates that user s account effective from the TERMINATION DATE forward The Deactivate a User option automatically performs the following steps when you deactivate a user e Revokes the user s status as an
495. on online will be indicated where applicable under the appropriate topic REF Please refer to the Kernel Technical Manual for further information Help at Prompts VistA M Server based software provides online help and commonly used system default prompts Users are encouraged to enter question marks at any response prompt At the end of the help display you are immediately returned to the point from which you started This is an easy way to learn about any aspect of VistA M Server based software Obtaining Data Dictionary Listings Technical information about VistA M Server based files and the fields in files is stored in data dictionaries DD You can use the List File Attributes option on the Data Dictionary Utilities submenu in VA FileMan to print formatted data dictionaries REF For details about obtaining data dictionaries and about the formats available please refer to the List File Attributes chapter in the File Management section of the VA FileMan Advanced User Manual July 1995 Kernel Systems Management Guide XXXV Revised June 2008 Version 8 0 Orientation Assumptions About the Reader This manual is written with the assumption that the reader is familiar with the following VistA computing environment Kernel VistA M Server software VA FileMan data structures and terminology VistA M Server software Microsoft Windows environment M programming language This manual provides an overall explanat
496. onment The following steps show you how to set up TaskMan to run in a DCL context in Cache VMS see Kernel Patch XU 8 0 355 NOTE The following is just an example an will have to be modified for your site You will need to adjust the UIC 100 20 to match your system and indicate the location of the TaskMan directory 1 Create TASKMAN that runs the TaskMan jobs Figure 21 10 Create TASKMAN ADD TASKMAN OWNER SYSTEM MANAGER ACCOUNT CACHE PRIV NETMBX TMPMBX DEFPRIV NETMBX TMPMBX DEVICE USERS DIR TASKMAN LGICMD LOGIN COM FLAGS DisCtlY DisWelcome DisReport DisForce_Pwd_Change DisPwdDic DisPwdHis PASS TASKSMAN UIC 100 20 2 Create the TASKMAN directory Figure 21 11 Create the TASKMAN directory Define SYSTEM DHCPSTASKMAN USERS TASKMAN July 1995 Kernel Systems Management Guide 21 15 Revised June 2008 Version 8 0 TaskMan System Management Configuration 3 Create the system logical name for the directory with the COM files NOTE Be sure to also add to the STARTUP LOGICALS COM file Figure 21 12 Create system logical name for the directory with the COM files Define SYSTEM DHCPSTASKMAN USERS TASKMAN 4 Create the queues as explained in this manual NOTE Be sure to also add to the STARTUP DEFINE_QUEUES COM file TaskMan will submit jobs to the queue TM lt node gt Because we use run loginout to detach the execution we do not need a large JOB limit here
497. or User Option 10 6 Algorithms Cache2 21 12 Parsing 3 17 All Keys a User Needs Option 8 3 All your tasks Option 22 3 Allocating Security Keys 8 3 Allocation of Security Keys Option 8 3 9 9 ALLOWED TO USE SPOOLER Field 3 22 Alpha Beta Test Option Usage Menu 7 4 23 23 Alpha Beta Tracking Sending a Summary Message 23 23 Alpha Beta Tracking KIDS 23 23 Altering Exported Menus 7 8 ALTERNATE EDITOR File 1 2 3 20 Alternate Syntax for Device Specification 14 6 Index 2 Kernel Systems Management Guide Version 8 0 ALWAYS SHOW SECONDARIES Field 3 22 7 7 Analyzing Routines Routine Tools 26 2 Answerback Message 3 5 Answering Installation Questions for Transport Globals in a Distribution KIDS 23 7 AOLD Cross reference 3 29 APIs TESTADDBRT 18 3 AYZTLOAD 20 2 22 34 A ZTLOAD API 18 13 ADIE 5 4 XUP 18 3 CHCK1AXTSUMBLD 27 3 27 4 CHCKSUM XTSUMBLD 27 3 27 4 CHECKIAXTSUMBLD 23 12 24 11 26 6 CHECKSUM XTSUMBLD 27 4 DIC 5 5 DIE 5 5 DQO ZTLOAD 22 33 ENABLE XUFILE3 Routine 5 14 ERR ZU 13 2 GETENV ZOSV API 21 3 LKUP XTLKMGR 25 22 PATIENT XQALERT 10 5 REQS ZTLOAD 22 33 TaskMan 20 1 20 2 USER XQALERT 10 5 Application Utilities Menu 25 3 ASK DEVICE TYPE AT SIGN ON Field 2 6 2 9 3 5 3 22 ASK HFS I O OPERATION Field DEVICE File 3 5 16 2 ASK HOST FILE Field DEVICE File 3 5 16 2 ASK PARAMETERS Field DEVICE File 3 5 15 4 15 9 16 2 Assign Editors Opti
498. or specific ZE text Stopped by user The Manager or the Submanager gives a task this status if wnen TaskMan removes the task from the SCHEDULE file for processing it finds that the user has asked the task to stop The Submanager also assigns this status if just before starting the task it finds the stop request has been made Finally the Submanager gives a task this status if the task uses the ZTSTOP output variable to report that it stopped in response to a user s request REF For an explanation of ZTSTOP please refer to the description of S ZTLOAD API in the TaskMan Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml Interrupted while running At startup the Manager gives this status to any task listed in the Task list of the SCHEDULE file as still running Unscheduled by lt user name or you gt The Dequeue Tasks KUTM DQ and TaskMan User KUTM USER options and the DQ ZTLOAD entry point use this status for tasks they unschedule Waiting for the link to lt volume set name gt to be restored The Manager uses this status for tasks that would have been transferred to a different TaskMan environment and deleted from this one if the local area network link to the remote environment were functioning properly If the task fails or errors out and TaskMan cannot
499. or the help frame e You are a holder of the XUAUTHOR security key Another handy way to edit help frames is within the help frame system as invoked from a software application For example if the help frames are tied to a software s options you can use the software invoke the help frame for each field or option and then edit that help frame on the spot To edit a help frame in this manner enter E at the help frame action prompt To do this however you must have edit access to the help frame as described above Namespacing of Help Frames Like entries in the OPTION 19 or SECURITY KEY 19 1 files entries in the HELP FRAME file 9 2 must be namespaced to avoid overwriting problems Help Frame Layout Considerations When entering the text of help frames you should keep each line to fewer than 80 characters for proper screen display NOTE The text is displayed as it stands and is not processed by VA FileMan s text formatter That is the text is not wrapped and word processing windows are not evaluated Frames are usually 22 lines in length although an end of page READ is issued to allow a pause 1f the frame exceeds 22 lines 12 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Help Processor If there are only a few lines of text the Help Processor displays a table at the bottom of the screen of all related frames those frames that the current frame has keyword links to The table show
500. ormation about devices on the system All connected volume Sets CPUs should make use of a single DEVICE file 3 5 Then all information concerning a particular device is stored in just one place which facilitates device management Sometimes a CPU will have an attachment point to which a device can be connected for example physical ports The I field in the DEVICE file 3 5 entry identifies this attachment point Most devices e g printers are connected to the network and I points to the name used by the underlying OS to point to the device When using such a device Kernel s Device Handler allows the creation and use of multiple DEVICE file 3 5 entries for the same physical device Each DEVICE file 3 5 entry can contain different specifications font margin page length etc to format output Each entry in the DEVICE file 3 5 then uniquely identifies a set of instructions to send to a particular device on the network Each device that Kernel Device Handler needs to communicate with should be set up as an entry in the DEVICE file 3 5 The DEVICE file 3 5 supports a variety of devices including video display terminals VDTs commonly called cathode ray tube devices CRTs printers tape drives and operating system files e g HFS devices The DEVICE file 3 5 is located in the Manager s account for common reference from all associated accounts With TaskMan s help this information is also available to all asso
501. other PCs e Select the Load a Distribution option Do not run the Environment Check routine e Under the Utilities Menu select the Convert Loaded Package for Redistribution option e Under the Edits and Distribution Menu select the Transport a Distribution option e When you are prompted to Enter a Host File enter the floppy drive and file name For example Enter a Host File A KRN8 KID One advantage to using distributions over INIT routines is that there is no limit to the size of a software application you can export Another advantage is that during installations you no longer have to overwrite a software application s existing routines with the new routines before running the installation July 1995 Kernel Systems Management Guide 23 5 Revised June 2008 Version 8 0 KIDS System Management Installations Alternatively a KIDS distribution can be sent via a PackMan message in MailMan But transporting software as host files especially large ones avoids slowing down MailMan Two Kinds of Distributions KIDS supports two kinds of distributions e Standard Distribution This type of distribution contains transport globals for what are traditionally thought of as software applications including files data and all components A standard distribution can contain one or more transport globals If there is more than one transport global KIDS treats each one as a single installation unit e Global Distribution This typ
502. ould active submanagers shut down after finishing their current tasks If you answer YES the Submanagers on the current Volume Set CPU will quit when they finish a task instead of recycling If you answer NO the Manager enters a WAIT state and the Submanagers continue with their business If you also want to keep the Submanagers from searching the Waiting List and the Job List for tasks you need to explicitly say so at this prompt This inhibition of the Submanagers recycling remains in effect either until you remove the WAIT state or until a new Manager starts or restarts whichever comes first Remove Taskman from WAIT State Option Figure 22 17 Remove Taskman from WAIT State option SYS LEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Remove Taskman from WAIT State XUTM RUN The Remove Taskman from WAIT State option XUTM RUN simply undoes the effects of XUTM WAIT allowing the Manager to process tasks and allowing the Submanagers to recycle 1f recycling had been inhibited July 1995 Kernel Systems Management Guide 22 15 Revised June 2008 Version 8 0 TaskMan System Management Operation Stop Task Manager Option Figure 22 18 Stop Task Manager option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Stop Task Manager XUTM STOP The Stop Task Manager option XUTM STOP gives you
503. ove to OpenVMS however the I of the user was dynamic with many thousands of I values possible The Virtual Terminal device type was created as a way to have one device entry be used for signon for multiple incoming I values The Device Handler still checks to see if it can assign a device to an incoming process based on an exact match of I values If there is no direct match however Device Handler checks to see if the first part of the user s I value matches the I value of a virtual device entry This way a virtual device with a I value of _TNA can service all incoming processes whose I values start with the string TNA Virtual devices do not need a value in the VOLUME SET CPU field they should have SIGN ON SYSTEM DEVICE field set to YES however to speed up the signon device selection process Common device prefixes on VMS systems that could be used for virtual terminal device entries include e TNA Telnet devices e RTA Remote processes using the SET HOST command e FTA Secure Shell devices Processes on VMS systems that use Telnet usually have I values beginning with the prefix TNA concatenated with an integer value and a colon e g TNA8456 A single virtual terminal device entry whose I value is TNA will service all such processes 15 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler System Management Terminal Type Selection at Signon Besides needing a
504. p from one menu option to another menu option without having to respond to all the prompts in between To jump type a caret and then type the name of the field or option you wish to jump to See also GO HOME JUMP PHANTOM JUMP RUBBER BAND JUMP or UP ARROW JUMP A logon procedure whereby the user enters the Access code Verify code option to go immediately to the target option indicated by its menu text or synonym The jump syntax can be used to reach an option within the menu trees by entering accesscode verifycode option A standard file transfer protocol It is supported by Kernel and can be set up as an alternate editor A UCI that holds vendor shared routines The process of first visiting a menu option by picking it from a menu s list of choices and then returning to the menu s select prompt Menu Manager keeps track of information e g the user s place in the menu trees according to the completion of a cycle through the menu system The Kernel module that controls the presentation of user activities e g menu choices or options Information about each user s menu choices is stored in the Compiled Menu System the XUTL global for easy and efficient access The overall Menu Manager logic as it functions within the Kernel framework An association of options as pathway specifications to reach one or more final destination options The final options must be executable activities and not merely menus for the te
505. per s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml 25 22 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 26 Routine Tools Overview Kernel Toolkit provides an Application Programming Interface API that includes developer utilities for working with routines and globals This chapter describes routine tools exported with Kernel Toolkit These tools are useful to IRM staff and VistA software developers REF Kernel Toolkit Application Programming Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml Most of the tools are available as options on the Routine Tools menu XUPR ROUTINE TOOLS located on the Programmer Options menu XUPROG which is locked with the XUPROG security key Some subordinate menu options are locked with the XUPROGMODE and or XUPROG security keys as an extra level of security Routines can be edited analyzed by flow charting printed compared deleted and moved by using an option or its corresponding direct mode utility REF Kernel Toolkit APIs and direct mode utilities are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide The Routine Tools menu is
506. phrase USER followed by the DUZ is substituted Finally the status of the task is shown REF For a list and description of the status messages please refer to the Troubleshooting topic in this chapter Each of these submenu options are described in the topics that follow All your tasks Option The All your tasks option see Figure 22 3 displays every task in the TASKS file 414 4 on the current Volume Set CPU that you created If you have no tasks scheduled the option gives you the message You have no tasks in this Volume Set s TASKS file Your future tasks Option The Your future tasks option displays those tasks you created that are currently scheduled to run If there are none the option tells you Every task lists every task in the TASKS file 14 4 List of tasks Option The List of tasks option allows you to list one or more tasks by task number You can specify individual tasks separated by commas along with ranges of tasks using a hyphen July 1995 Kernel Systems Management Guide 22 3 Revised June 2008 Version 8 0 TaskMan System Management Operation Unsuccessful tasks Option The Unsuccessful tasks option lists three kinds of tasks e Rejected by the Manager s validation process e Encountered an error while they were running e Unscheduled through the Dequeue Tasks option Future tasks Option The Future tasks option shows all tasks that are in the Schedule List or the Waiting List It does no
507. ple the option names and menu texts along with a limited number of fields for that option compiled from the OPTION file 19 are concatenated together It is from this part that XQ2 the menu display program gets the information it needs In the second part all the menu texts and synonyms are listed in order in uppercase It is here that XQ tries to match what the user entered at the terminal with the correct option The third part of the example the Oth node of the options is listed by number and provides the remaining information that the Menu July 1995 Kernel Systems Management Guide 7 17 Revised June 2008 Version 8 0 Menu Manager System Management System may need to make the option work To understand what the various pieces mean look at a VA FileMan global format data dictionary listing of the OPTION file 19 Illustrated in the second example Figure 7 24 is the display node for the SECONDARY MENU OPTIONS of a user whose DUZ is equal to 66 Here the user has only a single secondary menu called Secondary Menu with an internal number of 580 in the OPTION file 19 The various parts of this example are identical to those of the Display Nodes for the EVE menu example above NOTE The second subscript instead of pointing to a menu in the OPTION file 19 is a U concatenated with the user s DUZ which points to the NEW PERSON file 200 entry This is because secondary menu options are stored in the SECONDARY MENU O
508. pressing the PF1 key can be represented as pressing lt PF1 gt Author s comments are displayed in italics or as callout boxes NOTE Callout boxes refer to labels or descriptions usually enclosed within a box which point to specific areas of a displayed image e This manual refers in many places to the M programming language Under the 1995 American National Standards Institute ANSI standard M is the primary name of the MUMPS XXXIV Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Orientation programming language and MUMPS will be considered an alternate name This manual uses the name M e Descriptions of direct mode utilities are prefaced with the standard M gt prompt to emphasize that the call is to be used only in direct mode They also include the M command used to invoke the utility The following is an example gt D XUP e All uppercase is reserved for the representation of M code variable names or the formal name of options field file names and security keys e g the XUPROGMODE security key NOTE Other software code e g Delphi Pascal and Java variable names and file folder names can be written in lower or mixed case How to Obtain Technical Information Online Exported VistA M Server based software file routine and global documentation can be generated through the use of Kernel MailMan and VA FileMan utilities NOTE Methods of obtaining specific technical informati
509. programmers to access and manage help text The system is driven off of the HAASE 7 ORR Qa e There are severa fines which will cause the help text to be displayed to the user The system is interactive and the user may select which topic he she wishes further information on The Help Frame Processor Menu contains the following options DISPLAY EDIT Displays the text of a help frame and allows for the edit of the name header text or related frames Oi Oe HHO Tists all the help frames for a specified package showing parent help frames linked to menu option and invoking routine LIST Lists the help Frames 11 several dit ferent Lormats 1 54 hs LO FS Select HELP SYSTEM action or lt return gt At the bottom of every displayed help frame is a Select HELP SYSTEM action prompt You have several choices at this prompt To back your way out of the help frame system you can simply press the lt Enter gt key This backs you up one level or exits you if you are at the top level of a help frame tree If you want to exit quickly from help frames you can enter Q to quit immediately without having to back all of the way out July 1995 Kernel Systems Management Guide 12 1 Revised June 2008 Version 8 0 Help Processor You can list other choices at the Select HELP SYSTEM action prompt by entering a question mark 2 The full list of choices 1s Table 12 1 Help system command actions Respon
510. ption 23 12 XPD PRINT PACKAGE PATCHES Option 24 7 XPD PURGE FILE Option 24 7 XPD RESTART INSTALL Option 23 20 XPD ROLLUP PATCHES Option 24 9 XPD ROUTINE UPDATE Option 24 10 XPD UNLOAD DISTRIBUTION Option 23 20 23 21 XPD UTILITY Menu 24 1 XPD VERIFY BUILD Option 24 10 XPD VERIFY INTEGRITY Option 24 11 XQ Nodes 7 16 XQ UNREF D OPTIONS Option 7 8 28 1 XQ XUTL J NODES Option 7 12 7 13 XQAB ACTUAL OPTION USAGE Option 23 23 XQAB AUTO SEND Option 23 23 XQAB ERR DATE SITE NUM ROU ERR Option 23 23 XQAB ERROR LOG XMIT Option 23 23 XQAB LIST LOW USAGE OPTS Option 23 23 XQAB MENU Menu 23 23 XQABTST Variable 7 20 XQACNDEL Variable 10 3 XQAL ALERT LIST FROM DATE Option 10 8 Kernel Systems Management Guide Index 45 Version 8 0 Index XQAL BACKUP REVIEWER 10 10 XQAL CRITICAL ALERT COUNT Option 10 8 XQAL PATIENT ALERT LIST Option 10 9 XQAL REPORTS MENU Menu 10 8 XQAL SET BACKUP REVIEWER Option 10 10 XQAL SURROGATE FOR WHICH USERS Option 10 10 XQAL USER ALERTS COUNT Option 10 9 XQAL VIEW ALERT TRACKING ENTRY Option 10 9 XQAL DELETE Security Key 10 7 XQALERT BY USER DELETE Option 10 7 XQALERT DELETE OLD Option 10 6 XQALERT MAKE Option 10 7 XQALERT MGR Menu 10 6 XQALERT Option 2 7 XQALERT SURROGATE SET REMOVE Option 10 4 10 6 XQBUILDTREEQUE Option 7 13 XQCOPYOP Option 9 4 XQDIC Variable 7 20 XQDISPLAY OPTIONS Menu 7 5 XQHELP ASSIGN Option 12 5
511. quivalent in features to the current one since tasks that would normally run on the current one will be running on the REPLACEMENT VOLUME SET instead For many Volume Sets no other Volume Set is equivalent and tasks should wait for the link to be restored rather than run elsewhere If tasks that need this Volume Set should wait leave the field blank DAYS TO KEEP OLD TASKS This number stored in the DAYS TO KEEP OLD TASKS field is used by the XUTM QCLEAN option to decide which tasks to delete The decision only affects inactive tasks as explained in the discussion of the XUTM QCLEAN option Values in this field cannot inadvertently cause TaskMan to delete scheduled or running tasks If the field contains no value XUTM QCLEAN keeps the last seven days tasks A value of 0 here keeps your file very clean UCI ASSOCIATION File 14 6 Figure 21 4 UCI Association Table Edit option SYSTEMS MANAGER MENU EVE Task Manager XUTM MGR Taskman Management Utilities XUTM UTIL Edit Taskman Parameters XUTM PARAMETER EDIT UCI Association Table Edit XUTM UCI There are two different kinds of entries made into the UCI ASSOCIATION file 14 6 using the UCI Association Table Edit option XUTM UCI 21 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration Entries with only the first two fields FROM UCI and FROM VOLUME SET filled in identify the valid
512. r Select ALTERNATE EDITOR SCREEN EDITOR VA FILEMAN If the PREFERRED EDITOR is the Screen Editor it is also possible to switch to another editor like the Line Editor to take advantage of line editor features such as File Transfer from Foreign CPU NOTE Other editors e g WordMan or VA LetterMan do not support switching to the Line Editor which may be a limitation in some circumstances This field is also included in Edit User Characteristics and MailMan s Edit User Options so that all users can define a PREFERRED EDITOR if they so choose DIVISION The DIVISION field Multiple has a corresponding site parameter the Default Institution that sets users DUZ 2 if this field is not filled in A user setting however takes precedence over the site parameter This is a multiple field and if the user is associated with more than one institution the user is prompted at signon to pick the one corresponding to the computing activities to be carried out in that session SERVICE SECTION required This field points to the SERVICE SECTION file 49 distributed with Kernel s virgin installation No data is included It is a required field since applications have begun to use it in various utilities Kernel s CPU Service User Device Stats option XUSTAT for example can summarize signon information for all users in the same Service Section The Grant Access by Profile option also makes use of this field to specify the Service Section Coo
513. r Screens Option 13 3 Clean Error Log Over Range Of Dates Option 22 25 Delete Error Log Option 22 26 Edit Error Screens Option 13 3 List Error Screens Option 13 3 Menu 22 24 Node 22 27 Purge Error Log Of Type Of Error Option 22 26 Remove Error Screens Option 13 4 Show Error Log Option 22 25 Taskman Error Log Menu 13 2 TASKMAN FILES UCI Field 21 8 TASKMAN FILES VOLUME SET Field 21 8 TASKMAN HANG BETWEEN NEW JOBS Field 21 4 TASKMAN JOB LIMIT Field 3 3 21 2 21 3 Taskman Management Menu 13 2 Cleanup Task List Option 22 6 Delete Tasks Option 22 6 Dequeue Tasks Option 22 4 List Tasks Option 22 2 Requeue Tasks Option 22 5 TaskMan Management Menu 22 1 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Taskman Management Utilities Check Taskman s Environment Option 22 13 Clean Task File Option 22 17 Menu 22 7 Monitor Taskman 22 7 Place Taskman in a WAIT State Option 22 15 Queuable Task Log Clean Up Option 22 17 Remove Taskman from a WAIT State Option 22 15 Restart Task Manager Option 22 14 Stop Task Manager Option 22 16 SYNC flag file control Option 22 16 Taskman Management Utilities Menu 13 2 TASKMAN PRINT A HEADER PAGE Field 21 13 TASKMAN SITE PARAMETERS File 14 7 3 3 20 5 20 7 21 1 21 2 21 7 21 10 21 11 21 12 21 17 22 9 BOX VOLUME PAIR Field 21 3 ENVIRONMENT FOR DCL Field 21 5 Load Balance Routine 21 12 LOAD BALANCE ROUTINE Field 21 5 LOG TASKS Fiel
514. rdinator to whom the access forms of the new users should be delivered TIMED READ As discussed with other site parameters earlier in this chapter TIMED READ defines the length of time Kernel should wait for a user response to a READ A setting for the user attribute overrides the site default It is used to define the local variable DTIME MULTIPLE SIGN ON As discussed with other site parameters MULTIPLE SIGN ON controls whether the user will be permitted to have two or more concurrent signon sessions The user setting takes precedence AUTO MENU As discussed with other site parameters AUTO MENU controls whether the entire list of menu options is automatically presented or whether the user needs to enter a question mark to invoke the display The user setting takes precedence July 1995 Kernel Systems Management Guide 3 21 Revised June 2008 Version 8 0 Signon Security System Management ASK DEVICE TYPE AT SIGN ON As discussed with other site parameters the ASK DEVICE TYPE AT SIGN ON field controls whether the device being used at signon will be queried for its terminal type The user setting takes precedence TYPE AHEAD This field controls whether the user can enter text faster than the computer can read it If set to YES the computer buffers input from the user If set to NO keystrokes from the user are lost if they are typed faster than the computer can process them ALLOWED TO USE SPOOLER This field controls whether a
515. re 14 13 Device specification Four semicolon piece Sample DEVICE LASER P LASER NEW 132 100 The syntax for the four semicolon piece form of the device specification is Figure 14 14 Device specification Four semicolon piece Syntax DEVICE Device Name Subtype Right Margin Page Length July 1995 Kernel Systems Management Guide 14 5 Revised June 2008 Version 8 0 Device Handler User Interface Spool Document Names An Exception When you request the spool device at the device prompt you can use the following formats to specify the spool document name Figure 14 15 Device syntax Specifying a spool document name Sample formats 1 of 2 DEVICE Spooler Spool Document Name Right Margin Page Length Figure 14 16 Device syntax Specifying a spool document name Sample formats 2 of 2 DEVICE Spooler Subtype Spool Document Name Although neither right margin nor page length can be specified when including a subtype as the second piece and spool document name as the third no functionality is lost The explanation is simple the spooler only responds to these two terminal type specifications In other words identifying a subtype for the spooler does no more than define a margin and page length Spool document entries in the SPOOL DOCUMENT file 3 51 cannot have names beginning with P PK C etc 1 e one or two letters followed by a hyphen Because this syntax is the required naming convention for
516. re 22 12 Check Taskman s Environment option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Taskman Management Utilities XUTM UTIL Check Taskman s Environment XUTM CHECK ENV The Check Taskman s Environment option XUTM CHECK ENV presents two screens of information about TaskMan s environment on the current CPU The first screen see Figure 22 13 performs all of the checks that the Manager does whenever it starts restarts or encounters an error The second screen see Figure 22 14 shows what values the Manager is using for its definition variables This information can be very useful in pinpointing startup problems in verifying that the Manager is using the information you want it to use and in getting a general feel for how you have defined your system s task management Figure 22 13 Check TaskMan s Environment option First screen Checking Task Manager s Environment Checking TaskMan s globals ZTSCH is defined ZTSK is defined SZTSK 0O is defined g zZIS 14 5 0 is defined g zZIS 14 6 0 is defined Seto cas Te OO is defined Checking the SZOSF nodes required by TaskMan All SZOSF nodes required by TaskMan are der nedi 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 This first screen see Figure 22 13 goes through
517. re information on MT devices please refer to the Special Device Issues chapter in this manual For more information on HFS devices please refer to the Host Files chapter in this manual July 1995 Kernel Systems Management Guide 15 9 Revised June 2008 Version 8 0 Device Handler System Management Terminal Type Information Retained by User User can change some terminal type attributes of their signon device by doing either of the following 1 Changing the terminal type during the session with Edit User Characteristics 2 Selecting a device for direct output Kernel uses the XUTL global to hold information about changes made to device characteristics of the home device during a session REF For more information the XUTL global please refer to the Menu Manager System Management chapter in this manual The terminal type established for users at each signon is stored according in their NEW PERSON file 200 entries so that if necessary it can be used as a default for the next signon Devices and Signon Device Selection at Signon and Virtual Terminal Devices Every interactive user must be associated with a device by the Device Handler when they sign on to the VistA system The association of device is done by matching the incoming user s I value with the I value of an entry in the DEVICE file 3 5 Historically it was practical to set up one device entry with a matching I for each physical port With the m
518. recommended that the Site Manager Information Security Officer using VA FileMan add any locally sensitive options to this list It is the responsibility of each site to insure that the security of the system is not violated Replicate or Replace a Delegate Option You can copy the Delegated Options of a delegate to another user Use the Replicate or Replace a Delegate option XQSMD REPLICATE to do this The options that you transfer to another user do not replace any options the user has been previously delegated They will be added to those options if any Like the Select Options to be Delegated option this option also can branch you to the security key allocation program for the new delegate You are also asked if the delegated options should be removed from the original delegate If you say NO N the original delegate remains a delegate If you say YES Y all Delegated Options are removed from the original delegate who will no longer be an active delegate In order to remove the options from a delegate however you must have a Delegation Level lower than they do Remove Options Previously Delegated Option To simply remove an option from a delegate s list of delegable options use the Remove Options Previously Delegated option 1 Enter the name or names of the delegate s from which you want to remove options 2 Enter the option or options you want to remove from the specified set of delegates You re given a chance to review
519. ributes stored in the SECURITY KEY file 19 1 can be used for special purposes Attributes of the Provider key are shown in the following example Figure 8 5 Attributes for the Provider security key Sample user dialogue Select SECURITY KEY NAME PROVIDER No editin NAME PROVIDER lt Enter gt g DESCRIPTIVE NAME Provider lt Enter gt PERSON LOOKUP LOOKUP lt Enter gt KEEP AT TERMINATE YES lt Enter gt DESCRIPTION 1 gt This KEY is given to all entries in the New Person file that need 2 gt to be looked up as a Provider Those entries that hold this key 3 gt are considered to be providers It was given to all active 4 gt Providers in file 6 at the time of the Kernel 7 install EDIT Option lt Enter gt Select SUBORDINATE KEY lt Enter gt GRANTING CONDITION lt Enter gt PERSON LOOKUP As described in the Security Keys Developer Tools chapter in the Kernel Developer s Guide a special AK cross reference on the NEW PERSON file 200 is maintained automatically for anyone who 1s granted a security key that is flagged for Person Lookup This cross reference has been introduced to facilitate identification of user groups like providers KEEP AT TERMINATE As described in the Signon Security section concerning user deactivation security keys that are marked as KEEP AT TERMINATE will not be removed as a user attribute of terminated users This allows the continued processing of activities that had been previous
520. rio you pick certain CPUs to run TaskMan and give them Managers and files to do the job To have background processing support the remaining Volume Sets need to be able to queue to one of the Managers on the system This entails translating the TASKS 14 4 and SCHEDULE files of that Manager so they are visible to the unsupported Volume Set To tell TaskMan that the one Volume Set runs no tasks but is instead supported by the other you must configure the VOLUME SET file 14 5 as described later in this topic Another possible configuration is to allow tasks to run everywhere which requires that you place Managers within reach of every UCI and that you define your TaskMan environments accordingly Under this configuration every CPU needs its own Manager and its own TASKS 14 4 and SCHEDULE files One other configuration to keep in mind of course is to have a standalone environment disconnected from the rest of the computer system Such environments make excellent test areas for developers They are configured the same regardless of the configuration of the main system Configuring TaskMan TaskMan s three configuration files must be setup to properly reflect your system s layout The three files are e TASKMAN SITE PARAMETERS 14 7 e VOLUME SET 14 5 e UCI ASSOCIATION 14 6 July 1995 Kernel Systems Management Guide 21 1 Revised June 2008 Version 8 0 TaskMan System Management Configuration There are three options on the E
521. ristics option Both are called XUEDIT CHARACTERISTICS The INPUT template by the same name is invoked if the ScreenMan form cannot be loaded on the current terminal type IRM can substitute a locally developed template by entering its name in the USER CHARACTERISTICS TEMPLATE field in the KERNEL PARAMETERS file 8989 2 IRM can also design a customized form with the same name as the local INPUT template that will be displayed instead terminal type setup permitting In other words to invoke a locally modified display an INPUT template must exist If a ScreenMan form by the same name also exists an attempt will be made to display the form before defaulting to the INPUT template REF For more information on creating a local Edit User Characteristics form and template please refer to the Kernel Installation Guide July 1995 Kernel Systems Management Guide 3 23 Revised June 2008 Version 8 0 Signon Security System Management Deactivating and Reactivating Users Kernel provides options to deactivate and reactivate users on the User Management menu XUSER When users no longer need access privileges IRM can partially or entirely close access to their account Figure 3 15 User Management menu options SYSTEMS MANAGER MENU EVE User Management XUSER Deactivate a User XUSERDEACT Purge Inactive Users Attributes XUSERPURGEATT Reactivate a User XUSERREACT Deactivating Users The Deactivate a User opti
522. routine to another To copy lines to another routine first save the lines then load and edit the other routine and restore the lines When patching a routine the ACTION menu can be used to calculate checksums Before filing changes the new checksum can be displayed and compared with the patch report for verification of editing The following figure shows how to reach the ACTION menu with dot A A Figure 28 7 ACTION menu Sample user entries Edit A ACEO 2 Bytes in routine Checksum Restore lines Save lines Version Action C Checksum is 4971725 Action lt Enter gt Edit lt Enter gt Global nodes and local variables may also be edited with the Z editor Editing occurs directly so the idea of filing does not apply The editor must then be exited with a dot not with a dot file since filing should not take place July 1995 Kernel Systems Management Guide 28 5 Revised June 2008 Version 8 0 Miscellaneous Programmer Tools 28 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 29 XGF Function Library System Management The XGF Function Library supports developers designing text based applications The functions in this library support cursor positioning overlapping text windows video attribute control and keyboard escape processing all in a text mode environment If you intend to make simple interface enhancements for an existing text mode application then you may find the XGF Functio
523. rror trap To Remove ALL entries except the last N days simply enter the number N at the prompt OTHERWISE enter return at the first prompt and a DATE at the second prompt If no ending date is entered at the third prompt then only the date specified will be deleted If an ending date is entered that range of dates INCLUSIVE will be deleted from the error log Number of days to leave in error trap 50 DONE If you just press lt Enter gt instead of entering a number of days to retain you are then prompted for a start date and end date between which to remove errors Errors in the period you specify will then be purged immediately Figure 13 7 Choosing a start and end date range to delete errors from the error trap Starting Date to DELETE ERRORS from 1 1 lt Enter gt JAN 01 2004 Ending Date to DELETE ERRORS from 1 31 lt Enter gt JAN 31 2004 The queuable version of this option Error Trap Auto Clean can be scheduled to run in the background By default it cleans up errors recorded more than 7 days in the past You can specify a different interval July 1995 Kernel Systems Management Guide 13 5 Revised June 2008 Version 8 0 Error Processing by placing a numeric value representing the number of days beyond which to purge in this option s TASK PARAMETERS field Error Trap Display Option The Error Trap Display option XUERTRAP displays errors that have been trapped on the system The messages for these errors are
524. rs Alternatively IRM can use the Delegate keys option XQKEYDEL to populate the DELEGATED KEYS field Multiple one by one A user who has been delegated a security key can allocate that key to others in two ways e Through the Allocation of Security Keys option XUKEY ALL if it is on their menu e By delegating an option locked by the security key in question the key will be allocated along with the option The key recipients excepting holders of the XUMGER security key or a FILE MANAGER ACCESS CODE field 3 of cannot assign the security key to others however even if they have access to the Allocation option because the key does not exist in their DELEGATED KEYS field Multiple One example of key delegation is an IRM designee delegated the Provider key who allocates that key to incoming medical residents July 1995 Kernel Systems Management Guide 8 3 Revised June 2008 Version 8 0 Security Keys For security reasons users who have a key in their DELEGATED KEYS field Multiple cannot allocate that key to themselves That key must be awarded by another user who has been delegated the key or by an IRM staff member who holds the XUMGR system security key Creating and Editing Security Keys Keys can be created using the Enter Edit of Security Keys option XUKEYEDIT on the Key Management menu If a security key has already been defined its name cannot be edited It also cannot be deleted as discussed below Other key att
525. s and the environment pre install and post install routines Figure 24 2 Build File Print option Sample output PACKAGE ZXG DEMO 1 0 NATIONAL PACKAGE DESCRIPTION Package containing demonstration of ZXG functions ENVIRONMENT CHECK ZXGENV PRE INIT ROUTINE AXGPRE POST INIT ROUTINE ZXGPOS DATA USER COMES SITE RSLV OVER W FILE DATA PTS 662105 ZXG DEMO PRINT TEMPLATE ZXG PRINT FILE 662105 ROUTINE ZXGC0O0 ZXGCO1 LRECOZ ZXGCO3 ZXGCO04 ZXGCO5 ZXGCO06 ZXGCO7 ZXGCO08 OPTION AXG TEST INSTALL QUESTIONS 24 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Install File Print Option The Install File Print option XPD PRINT INSTALL FILE prints out the results of an installation as KIDS System Management Utilities stored in the INSTALL file 9 7 Use this option to check on the status of an installation in progress or to print out the results of a completed installation Figure 24 3 Install File Print option Sample output PACKAGE ZXG DEMO 1 0 BLAPS FEB 07 20048007 PAGE 1 ED 51 59 09 01 SOL 03 02 COMPLETED STATUS Install Completed DATE LOADED NATIONAL PACKAGE INSTALL STARTED FEB 07 2004 07 52 14 07 52 23 ROUTINES UP 25225 PRE INIT CHECK POINTS XPD PREINSTALL STARTED Oy oe gt XPD PREINSTALL COMPLETED OW eee li FILES ZXG DEMO 07 52 16 PRINT TEMPLATE OTa Sz OPTION 07 52 21 POST INIT CHECK POINTS XPD POST
526. s 22 14 Preure 22 15 Restart Task Manager Option nierscer i a cis enter eeenteees 22 14 Figure 22 16 Place Taskman in a WAIT State Option eeesesssssssssssssseeereeeseesssssssssseeeerereeeeeeeesesssssssssses 22 15 Figure 22 17 Remove Taskman from WAIT State option essseeeeeessesssssssssssssssserererererssssssssssseeees 22 15 Fisure 22 16 St0p Task Manager OptOliiicsitestsatcnctncetinesnaep neiaianctestansaareadaseeeinacs O 22 16 Picure 22219 5 YNC Ade Tle COnIrO OpMON sin Soa iescpaibieasaakshuccaatl bee saat dia A E AN 22 16 Risure 22 20 lean Task Pile Opti ciate cceectchs tial a S Dacia cient baschsee 22 17 Figure 22 21 Print Options Recommended for Queueing and Print Options that are Scheduled to run ODO ere ene nr Dera en ene nee tet baer eon ne rer ae Ree erat Om Seer tet ene nt ne enn yr enent Teen trnT Mp TER tOr nn ne rer Terrence no araeer 22 18 Figure 22 22 Schedule Unschedule Options Option ccccccseessseccccccceeeeseeecceceeeasseeseseeeeseeeeaeaseseees 22 19 Figure 22 25 One time O ptron Queue Opo semineri aeri i a i 22 24 Pieure 22 24 Show Error Loe opHlons esnean E E ob Svan tgeheews odes apenas 22 25 Figure 22 25 Clean Error Log Over Range Of Dates 2 0 0 cccccccscsnsnssesssssseeeeeceeceeeeeeeeseeaaaeeessesses 22 25 Figure 22 26 Purge Error Log Of Type Of Error Option ccccccssessseeesessssseeeceeeeeeececceesscecesssesseees 22 26 Fieure 22 7 7 Delete Error 108 OPU Onori Mecaceasticansaba
527. s O pl Ol sigiicah oaks hic cenit ites S 13 3 Pioure I5 5 Edt Error Screens Optio i isis cicia a se Sess as Sacer este Sree aes Sansa aoe aneee eased 13 3 Figure 5 4 Remove Error S CRECUs OptlOn N zegg bieoeiiaaets 13 4 Ficure 325 Error processing Option Soise a a aa a aia 13 4 Figure 13 6 Choosing the number of days to leave errors in the error trap ssseeseeeeeeeesssssssssssssssee 13 5 Figure 13 7 Choosing a start and end date range to delete errors from the error trap 0000000ee 13 5 Figure 13 8 Error trap display option Sample user dialogue ccccccccecceceeeeeeeeeeeceeeeeeeeeeeeeeeeeeeeeeees 13 6 Pisure 5 9 Mocalesyimbol tale Mel x0 sassciesakibccteab bees A 13 7 Figure 13 10 Choosing to examine the operating system s error log Sample user dialogue 13 7 Prenre 14 1 Choon tne NOME UEV CE ccs t snd iacceatia att acnsaiaetadecint tana E 14 1 Figure 14 2 GC nOosine a PEniterGe vCash ils a a a a a 14 1 Figure 14 3 Choosing the closest printer device sssssssoeeeerssssssseeerrssssssseerrssssssscerrssssssseeerressssseseeeee 14 1 Figure 14 4 Device syntax help One question mark ssessssssssseerssssssssseerssssssseerrssssssseeereeressssseeeee 14 2 Figure 14 5 Displaying devices help Two question marks 7 cccssssssssssssseeeecceeeeeeeeeeeeaaeeeeeseeseeees 14 2 Froore Tep Sampe pner SUIS ar E A AA 14 2 Figure 14 7 Specifying a device and queuing a pr
528. s can be used at the Select NEW PERSON Name prompt or when addressing mail messages or for other lookup purposes Users can edit their initials at any time since this field is included in the common option Edit User Characteristics July 1995 Kernel Systems Management Guide 3 17 Revised June 2008 Version 8 0 Signon Security System Management TITLE The TITLE field points to the TITLE file 3 1 a file exported with Kernel but without data records The User Management options to add or edit a user s record allow LAYGO into the TITLE file 3 1 so titles can be added via the NEW PERSON file 200 Although not required it may be wise to assign appropriate titles to users so this field can be referenced by other software applications MailMan for example displays titles in message headers if the user who is reading mail has so indicated with a flag in MailMan s Edit User Options called Show Titles NICK NAME Like INITIAL NICK NAME has a lookup type cross reference D in the NEW PERSON file 200 so that lookups will succeed simply by using the NICK NAME This field is also included in Edit User Characteristics Figure 3 13 Screen 1 of Edit an Existing User option EDIT AN EXISTING USER NAME USER8 ANTONY PAGE 1 OF 3 KRNUSER EIGHT INITIAL EK HISTORIAN NICK NAME EIG 000888888 MAIL CODE PRIMARY MENU OPTION XMUSER Select SECONDARY MENU OPTIONS ZZ MAIN Want to edit ACCESS CODE Y N FILE MANAGER ACCESS CODE
529. s is if you hold the XUMGER security key or have a FILE MANAGER ACCESS CODE field 3 of REF For more information on delegating security keys please refer to the Delegating Security Keys topic that follows All of the security keys that a new user needs to use their assigned options can be determined by using the All Keys a User Needs option on the Key Management menu XQLOCK1 This produces a list of the primary and secondary menus for that user and compiles a list of the keys for that menu tree This list can then be assigned or delegated It can also be edited before the keys are given to the user Similarly the Keys For a Given Menu Tree option XQLOCK2 examines a menu and lists all of the security keys associated with all sibling options Delegating Security Keys Delegating keys allows you to give a user the ability to assign specific security keys to other users as opposed to the XUMGER security key and VA FileMan Access code 1 e FILE MANAGER ACCESS CODE field 3 which allow all keys to be assigned One way to delegate security keys is to use the Change user s allocated keys to delegated keys option XQKEYALTODEL This option delegates to a user all of the security keys that are currently allocated to that user Any entries in their KEYS field Multiple are entered in the DELEGATED KEYS field Multiple as well They can now use the Allocation of Security Keys option XUKEY ALL to give the security keys to othe
530. s of one process can be used by another This sequential processing might be appropriate for example for the processing of physician orders or other nested tasks involving code execution An additional enhancement to resource devices called SYNC FLAGs allows TaskMan to run the next task waiting for a resource only if the previous task using that resource has completed successfully You can use SYNC FLAGs to ensure that subsequent jobs run only if previous jobs have completed successfully July 1995 Kernel Systems Management Guide 18 13 Revised June 2008 Version 8 0 Special Device Issues Creating Resource Devices Figure 18 12 Resource Device Edit option SYSTEMS MANAGER MENU EVE Device Management XUTIO Resource Device Edit XUDEVEDITRES The Resource Device Edit option XUDEVEDITRES provides a facility for editing resource devices Software that uses a resource should include in its installation instructions the way the new resource should be defined in the DEVICE file 3 5 IRM can then create one or more resource type RES entries Figure 18 13 Resource device Sample output NAME ZZRES STe ZZRES LOCATION OF TERMINAL NA RESOURCE SLOTS di TYPE RESOURCE The installation instructions should indicate the number of resource slots Sequential processing should use a value of 1 The name and I should probably use the same value and be namespaced according to VistA conventions 18 14 Kernel
531. s the choices of other frames so the user need not enter the keywords in the text You can force the table of related frames out of the display by entering enough blank lines so that the frame s length is 20 lines assuming the display has a page length of 24 lines For the Help Processor to identify and highlight keywords the keywords are entered in the text of the help frame enclosed in square brackets By convention keywords in help frames are usually in all capital letters A square bracket character can be displayed as part of the frame s text by entering two of the characters e g or If the frames are to be printed using the List Help Frames option the resulting help manual will have an organized outline if the frames are linked in a top down tree structure without any circular connections among the branches Linking a Help Frame as Help for an Option or Menu Once a help frame or a series of help frames has been created you can associate it them with options by entering the name of the top level help frame in the HELP FRAME field of the OPTION file 19 You can use Menu Manager s option Edit options to do this That way when a user enters a single question mark in conjunction with the option name Menu Manager will invoke the associated help frame Figure 12 9 Linking help frames to an option Sample user dialogue Select Systems Manager Menu Option Menu lt Enter gt Management Select Menu Management Option
532. s waiting for the same device Is there a task waiting to run Run the task Yes NO Yes Is it time to quit yet check Retention time Yes 20 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Overview TaskMan s Files The two central files that facilitate task processing are e TASKS file 414 4 e SCHEDULE file not VA FileMan compatible TaskMan is configured by three configuration Files e VOLUME SET 14 5 e UCI ASSOCIATION 14 6 e TASKMAN SITE PARAMETERS 14 7 These files and the TaskMan routines fall within TaskMan s namespace ZTM and numberspace TaskMan user interface routines have been moved to the XUTM namespace beginning with Kernel V 8 0 they were previously in the ZTM namespace TaskMan also relies upon software components outside of its direct control As an integral part of Kernel TaskMan accesses several files controlled by other Kernel modules and calls many software entry points as a whole TaskMan s main external relation however is with VistA software applications through the queuers and the tasks they use TaskMan Globals ZTSCH and ZTSK A LZVSCH holds the SCHEDULE file and ZTSK the TASKS file 14 4 Every environment controlled by a single Manager needs each of these globals in its library UCI globals are used to make these files accessible to all the UCIs in that environment so a single Man
533. sage is displayed 4 0Ok will now setup KEYWORD and SHORTCUT file DD s to allow terms for reference file name entries PREFIX M Letter s to be used to identify a variable The following reminder message is displayed lt REMINDER gt Using Edit File set the lookup routine XTLKDICL reference file name DD The selected file is displayed OK YESS lt Enter gt LOCAL LOOKUP NAME reference file name lt Enter gt to accept default Correct file name LOCAL LOOKUP DISPLAY PROTOCOL protocol lt Enter gt to accept default Correct entry point for routine to set display lt Enter gt no default accept the internal Default display format INDEX index lt Enter gt to accept default correct cross reference to be used to create new Keywords Return to the menu Required field July 1995 Kernel Systems Management Guide 25 11 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The following is an example of what might appear on your screen when using the Add Entries To Look Up File option Figure 25 10 Add Entries To Look Up File option Sample user entries Select LOCAL LOOKUP NAME PROCEDURE MODIFIERS ARE YOU ADDING PROCEDURE MODIFIERS AS A NEW LOCAL LOOKUP THE 4th Y lt Enter gt YES LOCAL LOOKUP NAME PROCEDURE MODIFIERS lt Enter gt LOCAL LOOKUP DISPLAY PROTOCOL lt Enter gt INDEX AIHS Ok will now setup KEYWORD and SHORTCUT file DD s to allow t
534. sary A symbol used in front of a Common option s menu text or synonym to select it from the Common menu For example the five character string TBOX lt selects the User s Toolbox Common option The set of characters used to define the DR variable when calling VA FileMan Since a series of parameters may be included within quotes as a literal string the variable s definition is often called the DR string To define the fields within an edit sequence for example the developer may specify the fields using a DR string rather than an INPUT template A local variable that holds the FILE MANAGER ACCESS CODE field 3 of the signed on user Scrambling data or messages with a cipher or code so that they are unreadable without a secret key In some cases encryption algorithms are one directional that is they only encode and the resulting data cannot be unscrambled e g Access and Verify codes Formerly known as Part 3 of the Kernel Inits If the File Access Security conversion has been run file level security for VA FileMan files is controlled by Kernel s File Access Security system not by VA FileMan Access codes i e FILE MANAGER ACCESS CODE field 3 in the NEW PERSON file 200 A device attribute indicating that the device can only accept queued tasks If a job is sent for foreground processing the device will reject it and prompt the user to queue the task instead A menu jump that returns the user to the primary menu presen
535. se Action Jump to help frame associated with Keyword Quit to previous help frame exit if no previous How you got to this frame On off switch for bracketing reverse video of keywords Edit this frame only if authorized as editor of frame Keywords in a help frame are displayed by the help processor in reverse video If you enter the first few letters of a keyword and press the lt Enter gt key the help processor will jump to the help frame linked to the entered keyword Help Frames in the Menu System If a menu option has associated help frames you can display them by entering a question mark followed by an option s menu text or synonym at a menu prompt 1 e 0ption For example Figure 12 2 Display a help frame for an option Entering one question mark and option name Select Office Menu Option MAILMAN Entering three question marks at the menu prompt indicates which options have associated extended help help frames Figure 12 3 Display a help frame for an option Entering three question marks Select Office Menu Option 27 12 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Help Processor If a menu itself has an associated help frame entering four question marks at the menus Select action prompt displays the help frame associated with that menu if one exists Figure 12 4 Display a help frame for an option Entering four question marks
536. se as primary or secondary options along with their security keys to users who fall under their administrative jurisdiction For example the Site Manager might delegate the management of the Laboratory software options to the Lab Application Coordinator LAC and the LAC could then allocate or remove options from everybody in the Laboratory software The system is set up in such a way that the LAC could also delegate with the Site Manager s permission and manager s menu the management of all the chemistry menus to the head of the Chemistry Section and so on creating another level of delegation There are two divisions in Secure Menu Delegation e The menu to create and manage delegates e The menu for the delegates themselves to assign options to end users July 1995 Kernel Systems Management Guide 9 1 Revised June 2008 Version 8 0 Secure Menu Delegation User Interface Acting as a Delegate As a delegate you have been delegated options usually by IRM If you have been delegated options you can assign these options to computer users on the computer system As a delegate you can assign the following options to your users e Options that have been delegated to you e Menus that you have created from options delegated to you e Options you have created from VA FileMan templates As a delegate you need to understand the basic structure of the OPTION file 19 which is a file that points back to itself That is a menu is an
537. security in this case is managed by controlling the availability of the option REF For exceptions please refer to the When is File Access Security Checked topic in this chapter If a user s DUZ O is set to the at sign programmer access VA FileMan options allow complete file access If it is set to anything else except the caret VA FileMan options use the ACCESSIBLE FILE Multiple field 32 specifications in the NEW PERSON file 200 to grant varying levels of file access NOTE The caret overrides the at sign programmer access This higher degree of control over a user s file access comes at a price because it requires more management on IRM s part to provide each user access to the files to which they need access However the payoff in using the File Access Security system is in enhanced control and security for VA FileMan files When is File Access Security Checked When using VA FileMan options access to files through the File Access Security system is checked When initially accessing data in a file through software options e g options using VA FileMan Application Program Interfaces APIs File Access Security is not checked File Access Security is checked however when calling the following APIs e DIC calls Adding an entry to the top level of a file 1 e LAYGO access e DIE calls Deleting an entry at the top level of a file 1 e DELETE access Developers can bypass th
538. sena anne e a E A anaes 21 1 TaS KMS RE a yss vanes eeotaaseussaassoueine caseestiansueatansnee 21 2 TASKMAN SITE PARAMETERS File 14 T cicania 21 2 VOLUME SET Ple HIA S eisie a eatin G dua tads netic dashes tied deus 21 5 UCEASSOCIA TION File Gil 6 aprirne a maine 21 8 Sample Configuration Standardized VA Cach and GT M Configuration 21 10 Manager SCAT Pitosedos saan nidanz eE 21 11 Multiple TaskMan Managers and Load Balancing ccecccccccccccssseeseeeeeeeeeeeeeeeeceeeeeeaneeees 21 11 xvi Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Contents Device Handler s Influence on TaskMan w cc ccccssssssesseeseeeecceceeccceeeeaaaaaeaseseeeeeeeeeeeeeees 21 13 Runnimne Task Man witha IC TC Onto rasni a E A E 21 14 22 TaskMan System Management Operation iios a aa a aaa i 22 1 Task Man Manaceme nt Memi siensia nnan E 22 1 List TASKS CU Onnen a a e a a E eres 22 2 Degoes Task OPIO staren a laa A at canea daa acme Racueerae 22 4 INS GUC US Task ODIOM a T 22 5 Delete Tasks OPHON saii a chcatontanwiaiebeaceuasiasahenedcawents 22 6 Cleantip Fask Mist Option snena e N A 22 6 Taskman Manasement Utilities sci aussscieoc casas is a E e A e aE Oa 22 7 Monitor Taskman OPU O soscas n O ER 22 7 Check Taskman s Environment Options sisssssnceeii i i an a i 22 13 Restart Fask Mamaser OPUOM enic E a veaed eataedict 22 14 Place Taskman ima WAIT State OPUON soio rise e A S 22 15 Remove Taskman
539. ses a checkpoint system to keep track of how many phases of an installation it completed When an installation aborts for some reason you can restart the installation using the Restart Install of Package s option XPD RESTART INSTALL KIDS does not automatically re run the entire installation from the beginning instead it re runs the installation only from the last completed checkpoint As well as some standard checkpoints built into KIDS e g completion of pre install completion of each component type and completion of post install KIDS lets developers create checkpoints for use within their pre and post install routines So depending on how the developer has designed a pre or post install it is possible that when re started the pre or post install does not have to be re run in its entirety either if the error occurred there Instead KIDS only re runs the pre or post install from the last completed developer checkpoint if any within the pre or post install Before restarting an installation you should try to determine what caused the installation to abort If an error occurred any error messages will be in the INSTALL file 9 7 entry in the MESSAGES word processing type field Once you ve fixed the problem you can use the Restart Install Of Package s option XPD RESTART INSTALL to continue with the installation KIDS also allows you to restart an install if the install 1s queued and you get an error during the installati
540. settings ccccccsssseeeeeeeeeeeees 16 3 Figure 17 1 Unable to send output to a spool device Sample Message ccsesssseeeceeeeeeeeeeeeeeeeeeeees 17 1 Figure 17 2 Specifying spooled output margin and length eee eeccseeeeeccccccceceeeceeeeenaaaeeeeeseeeeeeeeeees 17 1 Figure 17 3 Spool document name Promipt vocc ccc sacicssaces es ioa ced cea E E E 17 2 Figure 17 4 Specifying the spool device and document name ccceeeeeeeeeeeeeeeeeeeeeeeeeessesseeeeeeeeeens 17 2 Figure 17 5 Spooling output to a spool device on the same CPU 0 0 0 0 eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeens 17 2 Figure 17 6 Queuing Output to a spool device eesesssssseeeerssssssscerrsssssssseerssssssseceesssssssseeresssssseeeeeeees 17 2 Figure 17 7 Spooler Parameters at the Device prompt SUMMATLY cccccccccessseeeeeceeceeeaeeeeeeeeeeeeeeaas 17 3 Fis re 7 8 5 pooler Menu Options ss sciccals co ea sas atin e van id nich e M asia ean 17 3 Figure 17 9 Formatting Sending a document to a spool device to print as a MailMan message Sample user dialo GUC rnn E e A 17 5 Figure 17 10 Make spool document into a mail message option sesseesssssssssssssssseeerrrreeessssessssssssssses 17 5 Fisure 17 11Fdit Users Spooler ACCESS ODUM seissadccesnsea ueiacaactioasensiaesacssstwensed deeacenstionsnadinesncsdatesancdenest 17 7 Figure 17 12 Edit User s Spooler Access Sample user dialogue ccccecccccccccccccee
541. shown in menu cycle e First date and time selected for processing e Date and time processing completed if any e Date and time alert was deleted e Forwarding information If alert was forwarded user who forwarded it and date and time of forwarding e Surrogate information If a surrogate was added for alerts user who was the surrogate and date and time of the surrogate The PATIENT XQALERT and USER XQALERT functions provide access to information in the ALERT TRACKING file 8992 1 REF For a description of the XQALERT and other alert related APIs please refer to the Alerts Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml July 1995 Kernel Systems Management Guide 10 5 Revised June 2008 Version 8 0 Alerts Alert Management Menu The Alert Management menu XQALERT MGR contains the following options described below Figure 10 3 Alert Management menu options SYSTEMS MANAGER MENU EVE Operations Management XUSITEMGR Alert Management XQALERT MGR SURO Alerts Set Remove Surrogate for User XQALERT SURROGATE SET REMOVE Delete Old gt 14 d Alerts XQALERT DELETE OLD Make an Alert on the fly XOALERT MAKE Purge Alerts for a User XOALERT BY USER DELETE k gt Locked with XQAL DELETE Report Menu for Alerts XOAL REPORTS MENU Set Backup
542. sing first build KIDS starts processing next build Check version Greater than current No Any more builds to process Question Run the Environment check No Yes KIDS restores environment check routine for build and runs it Package s No environment check OK KIDS removes build s install data from XTMP install global KIDS creates INSTALL File entry for build it also links Yes INSTALL entry to other Exit packages if distribution contains multiple builds July 1995 Kernel Systems Management Guide 23 11 Revised June 2008 Version 8 0 KIDS System Management Installations Verifying Checksums in a Transport Global You can verify the checksums for a loaded transport global in advance of installing from it using the Verify Checksums in Transport Global option XPD PRINT CHECKSUM This option verifies all checksums of routines in the transport global reporting any discrepancies In the future the ability to verify checksums will be extended to other KIDS components besides routines NOTE As of Kernel Patch XU 8 0 369 the integrity checking CHECK1 XTSUMBLD API supports the Compare local national checksums report option XU CHECKSUM REPORT NOTE As of Kernel Patch XU 8 0 393 KIDS was modified to send a message to a server on FORUM when a KIDS build is sent to a Host File Server HFS device This message contains the checksums for the routin
543. sion 8 0 Revised June 2008 Contents User Titer AG icon te aes E a ste sawanisacatecsniachecdndes car heints tates nada ec snisched dnd ee can bainta tiecneataeennes 17 1 Sendia Output do the SHOO Eae atecsaetigg a bealeabincn E E 17 1 Rettevin Spooled Documents sessen a ds eons ds iuchaceseeeennetueest 17 3 BOW SING a opoo lL Docume a iisoeatd cna cssh i ioalousolieceatidncsenel A A 17 4 Prnans SPOOlDOCUMCINS coecssinien e E dabdclinladeels 17 4 Making Spool Documents into Mail Messages cccccccssssssseeeecececeeeeeeeseceeeeeeeaaeeseeees 17 4 Syse Mma Emen aine a tanseeteusa eaeaneaene neu tase e herent enemas 17 6 Spool Docume ne SUOLA GC sorga cinsnedo sedating satin sesansaiees cds andaveeenndl a teenie 17 6 Overmlowing Spool Document Stora Enea a E 17 6 Granon SPOONNe PAVESE Ssi Miva aT rere en easiness nee Mien enraene 17 7 Marae line SPO D OCUIMCN IS an Ar A A 17 7 spooler Site Parameters Edit Option 2 ccicccccsstiasseccieccenstiacssactacdanaatbassasccdaaseestandsasecanceeane 17 8 Purge old Spool documents Option scasiicnscie vactacesataesideces tannin sane viastaansdauntdeuinitaancanettsaesanes 17 8 Detinne Spool Device Types cen sisiccx tech teinds aa a A 17 9 Spool De Vice EdiCODHOM rrena rn ra a r 17 9 PAUORCES POON earran A E E E O eae 17 9 Generating Spool Document Name Seeiiensneeria ii A E E E E 17 10 lS Speca DC VICE TS ie Syse a iaentheseetiensaie 18 1 Browser DOVII Oore e E ae 18 1 TS iS a o E A N es ee ea ne
544. sked to confirm the new VERIFY CODE by entering it a second time if you confirm it the new VERIFY CODE will take effect immediately Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security User Interface Display User Characteristics Option The Display User Characteristics option XUUSERDISP like Edit User Characteristics is an option in the User s Toolbox menu It prints out a description of many of the characteristics of your current computing environment including some of the characteristics that can be set through the Edit User Characteristics option Figure 2 9 Display User Characteristics option Sample output and user dialogue KOSINUSI HANO 79999 DEVICE DEVICE INHAN Si TNA7304 JOB PERNE mice ENVIRONMENT ATTRIBUTES OAKLAND Type ahead KRN KDE Time out Signed on 08 48 Fileman code s Terminal type C VT100 Person Class Physicians M D and D03 Physician Osteopath Pathology Anatomic KEYS HELD XUP ROG XUPROGMODE SYSTEM COMMAND OPTIONS XUCOMMAND User s Toolbox XUSERTOOLS Display User Characteristics XUUSERDISP TA I to escape lt CR gt to view Mailman user info lt Enter gt Current Banner S amp OCS Technical Writer Last used MailMan 07 12 06 15 09 NEW messages 274 274 in the IN basket Office phone DOO O00 Fax DIS ODO Add l phone Ores eo SO Add l phone 39975 Tncroduct ron My name is One Xmuser and I am one of the Technical Writers for th
545. specific alerts Forwarding may be as an ALERT to specific user s and or mail group s or as a MAIL MESSAGE or to a specific PRINTER to delete specific alerts some alerts may not be deleted to print a copy of the pending alerts on a printer to receive a MailMan message containing a copy of these pending alerts to Redisplay the available alerts to exit or RETURN to see additional pending ALERTS Select from 1 to 3 OF enter A ily E S P M R Or to exit or RETURN to continue Deleting Alerts As of Kernel Patch XU 8 0 114 you can delete alerts by using the D alert processing code when viewing alerts The user can if desired delete specific alerts without viewing and or processing them This option provides the ability to delete INFORMATION ONLY alerts Alerts that require processing can not currently be deleted However if alerts requiring processing are created with the XQACNDEL variable set to 1 they too would be able to be deleted 1 e the developer of the code that creates the alert can specify if it must be processed or can be deleted Any alerts that were selected for deletion but could not be deleted will be noted for the user The ability for the user to delete alerts other than INFORMATION ONLY will require that the developers within a software application decide that specific alerts which would normally invoke processing via an option or routine can be deleted specifically by the user without processing They
546. ssescceceesaeeesees 10 6 Report Menu ior Alerts ment OpUlOMs iiic cess seein tee ce van cd ccna a incl echentdeee ease 10 8 Sample message received when pinging a domain address cccccecceeessseeeeeeeeeeeeeeees 11 6 XQSCHK server option Sample MailMan return Message ccceeeesseccceeeeeeesseeeeeeeees 11 7 FIG Pian Cx AIDC sh es consti ha aslee s deactth a sh dala Sates ea vacates eaakth dautt a latikt 12 1 Display a help frame for an option Entering one question mark and option name 12 2 Display a help frame for an option Entering three question marks 7 ccceeeeeeeeeeeees 12 2 Display a help frame for an option Entering four question marks 7 eceeeeeeeeeeees 12 3 Help Processor Ment OpGONs ossia ges su ct aenaatinasesntgciecee cane GM aemsen cusses 12 4 Display Edit Help Frames option Displaying help using the option syntax 6 12 4 List Help Frames option Sample user dialoQue cccccccccccccsssesseeceeecceeaeeseseeceeeeeeaeeneees 12 4 Kernel Systems Management Guide xxiii Revised June 2008 Version 8 0 Figures and Tables Figure 12 8 Estimating the size of the HELP FRAME file 9 2 using Kernel s Block Count utility 12 6 Figure 12 9 Linking help frames to an option Sample user dialogue cc eeeeccccccccceeeeeeeeeeeeeeeeeeeees 12 7 Fisure 5s Acist Brror Screens OPtOMsicess acesnsasGetaceistesas T T E AS 13 3 igure 3 2 Add Biron SCreen
547. ssing the lt Enter gt key reverses the toggle and allows navigation Pressing the lt Enter gt key again moves back to the beginning of the line Figure 28 5 Z Editor Line mode help information In the line mode Spacebar moves to the next space or comma Dot to the next char gt To move forward 80 char or to end of line Backspace to back up one char E to enter new char s at the cursor CR to exit enter mode return to start of line or EDIT prompt D to delete from the cursor to the next space or comma Delete Rub to delete the char under the cursor CTRL R to restore line and start back at the beginning Replace mode editing can be invoked by entering dot XY at the edit prompt This method allows easy string substitution as in the VA FileMan line editor Entering a question mark at the next edit prompt displays the following help Figure 28 6 Z Editor Replace mode editing help information In the replace with mode SPECIAL lt REPLACE gt STRINGS END to add to the END of a line t replace a line Awe B C specify a String that begins with A and ends with TR Pe seis to specify a string that begins with A to the end of the line CTRL R to restore line 28 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Miscellaneous Programmer Tools The ACTION menu provides additional functions Save and restore lines can be used to move lines within one routine or from one
548. sssees 11 8 Table 12 1 Help system command acHonS srna aa E E E ad 12 2 Table 14 1 Sample semicolon delimited pieces at the DEVICE prompt cccccccccccceeseeseeeeeeeees 14 3 Pable 14 2 A ltermatede vice atte COMES sccainncctasanesvonanseussanaseusannanenseasanctuesonsussaaaseueanaadenecatancebenanenteas 14 7 Table 15 1 Device telated files slobal lOCani onsSonendseinane a Minoan oe ee 15 1 Table 15 2 Device types in the TYPE Field in the DEVICE file 43 5 eeeeeeeeeeseeseeeeeeeeeeenens 15 3 Palle P93 OU Cum Se GN Siea aa e wads Sica Ada euecin dead a S 15 4 Table 15 4 Terminal type naming conventions ssseeeeessseeeececceeeeceeeceaasaeseeseeseeeeeeeeeeeeeeeeeeaaaaaaaeeaas 15 9 Table 15 5 Sample period delimited pieces used for device lookup ccccccccececeeeeeeeeeeeaeeseeseeseeees 15 13 Table 16 1 HFS input output modes of Operation ccceccecccccsssssseseeeccececeaeeceeeccceeeeaaeeseeeceeeeessaeeeeeees 16 1 Table 16 2 HFS I O operation modes for Cach and GTM cccccccccccccsssssseecececeeeeeeesseeceeeeeueaaensseeeeees 16 2 Table I is Spoolersite parameter el GS wisssct iota cahheatas disses a a aah hineeaeeaniensadioaade 17 8 Table 18 1 Escape sequences used to toggle the slaved printing modes for DEC VT220 VT320 MOTE AS ors soos sed ETE OE ETE OTE TET A E TE E OA EE E EE A E 18 16 Table 20 1 TaskMan system configuration terminology yei a a 20 8 Table 22 1 Special Queene feld Setting So
549. sswords in general contain at least three of the following four character types Uppercase letters Lowercase letters Numbers Special characters symbols that are neither letters nor numbers e g _ amp NOTE Some non VistA based systems restrict certain special characters symbols used as part of a username and or password Because VistA is case insensitive VistA only has three sets of characters from which to build a strong Verify code 1 e password Letters of any case Numbers Special characters symbols that are neither letters nor numbers e g _ amp NOTE Some non VistA based systems restrict certain special characters symbols used as part of a username and or password Verify codes must be changed at least every 90 days or less You must change your Verify code at periodic intervals as specified by IRM Information systems shall not permit re assignment of the last three passwords used When required you will be prompted during signon to pick a new Verify code Accounts that have been inactive for 90 days shall be disabled Kernel Systems Management Guide 2 3 Revised June 2008 Version 8 0 Signon Security User Interface e To preclude password guessing an intruder lockout feature shall suspend accounts after five invalid attempts to log on Where around the clock system administration service is available system administrator intervention sh
550. st be set to an at sign programmer access July 1995 Kernel Systems Management Guide 25 9 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The process chart below shows the prompts and steps involved in using the Add Entries To Look Up File option Figure 25 8 Add Entries To Look Up File option process chart 1 of 2 AT THIS PROMPT IF USER ANSWERS WITH Select LOCAL LOOKUP NAME ARE YOU ADDING reference file name AS A NEW LOCAL LOOKUP THE nTH LOCAL LOOKUP NAME reference file name LOCAL LOOKUP DISPLAY PROTOCOL Name of new reference file you wish to enter in LOCAL LOOKUP file 8984 4 lt 2 gt FOE file LLST Name of existing file lt Enter gt or up arrow lt gt lt Enter gt to accept default Other file name Entry DONE for routine to determine the display lt Enter gt to accept the internal default display format If the entry made at this step is not the same as the cross reference in the description field of the file the software still functions keywords entered in the LOCAL LOOKUP file Required field 25 10 Kernel Systems Management Guide Version 8 0 but it only uses the 8984 4 July 1995 Revised June 2008 Multi Term Look Up MTLU Figure 25 9 Add Entries To Look Up File option process chart 2 of 2 IF USER AT THIS PROMPT ANSWERS WITH Cross reference to be used to create new key NOTE The following mes
551. st before it starts the task at its entry point If the task fails or errors out and TaskMan cannot trap the error this status has a different meaning Started running lt date amp time gt and stopped irregularly Completed lt date and time gt The Submanager gives a task this status after the task quits 22 32 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Waiting for a partition When the Manager places a task in the Job list of the SCHEDULE file it gives the task this code If the task fails or errors out and TaskMan cannot trap the error this status has a different meaning Stopped irregularly while waiting for a partition TaskMan System Management Operation Status Code Waiting for device lt device name or l gt or hunt group lt hunt group name gt The Manager or the Submanager gives a task this status when it places the task in the Busy Device Waiting list If the task fails or errors out and TaskMan cannot trap the error this status has a different meaning Stopped irregularly while waiting for a device Rejected lt rejection message gt The Manager or the Submanager gives a task this status if it fails one of the basic validation tests The rejection messages are contained in the next topic Error lt date and time gt lt error message gt The Submanager gives a task this status if it traps an error after starting the task The error message records the vend
552. st of candidates for purging will contain all entries whose first characters match all characters in the string you specify Figure 24 8 Purge or Install Files option Sample user dialogue Select Utilities Option Purge or Install Files Select one of the following B Build I Install Purge from what file B Versions to Retain 0 100 1 0 Package Name ALL ZXG Another Package Name lt Enter gt in Build file Don t retain any versions OK to DELETE these entries NO YES Select Utilities Option 24 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Utilities Purging Selected Entries Based on the software name you enter and the number of entries you ask to retain the option lists the software it finds to purge If you answer YES to the OK to DELETE these entries NO prompt the option purges the listed entries Reasons to Retain BUILD and INSTALL File Entries e BUILD file Entries in the BUILD file 9 6 are created by the software developers and identify every component in the software BUILD file 9 6 entries also contain the checksums for a software application s components You may want to retain the build entry for the most recent versions of installed software so that you can verify the checksums of the loaded software against its original checksums e INSTALL file Each entry in the INSTALL file 9 7 contains a record of the installation for
553. stallation menu options Select Kernel Installation amp Distribution System Option Installation Load a Distribution Verify Checksums in Transport Global Print Transport Global Compare Transport Global to Current System Backup a Transport Global Install Package s Restart Install of Package s Unload a Distribution Select Installation Option July 1995 Kernel Systems Management Guide 23 3 Revised June 2008 Version 8 0 KIDS System Management Installations KIDS introduced two files into Kernel e BUILD file 9 6 e INSTALL file 9 7 KIDS also makes use of the existing PACKAGE file 9 4 but its role in exporting and installing software is diminished Build Entries and the BUILD File 9 6 Build entries stored in the BUILD file 9 6 are where developers define a software application This build entry defines the set of files data components installation questions national software information pre and post install routines and other settings that comprise the exported software Software components are no longer tied to namespace as they were previously with DIFROM and the PACKAGE file 9 4 Developers can select any components available on the current system and include them in their build entries as software components The format of the NAME field 01 of a build entry must be the software name concatenated with a space and then a version number This means that there is a separate entry for
554. sting and afterword The leading B found in the checksum tells the code what checksum API to use 24 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 VI Toolkit This section provides descriptive information about the set of software utilities furnished by Kernel Version 8 0 and Kernel Toolkit Version 7 3 a k a Toolkit describing how these tools can be used for the management and definition of development projects The major areas of the Kernel Toolkit described in this section are listed below e Multi Term Look Up MTLU Multi Term Look Up MTLU utilities provide a method of enhancing the lookup capabilities of associated VA FileMan files Multi Term Look Up MTLU is an adaptation of a tool developed by the Indian Health Service IHS which was originally made generic by the Albany Office of Information Field Office OIFO MTLU does the following Tests ICD diagnosis and procedure codes CPT codes and other commonly used references that have been entered in the LOCAL LOOKUP file 8984 4 Optionally terms or phrases can be entered into the LOCAL KEYWORD 8984 1 LOCAL SHORTCUT 8984 2 or LOCAL SYNONYM 8984 3 files Prints a list of shortcuts keywords or synonyms from a specified reference file in the LOCAL LOOKUP file 8984 4 Adds or deletes a reference file from a site s LOCAL LOOKUP file 8984 4 Enters new or edit existing shortcuts keywords or synonyms to the L
555. subtypes you are allowed to specify the document name and the subtype in any order REF For more information about Spool Devices please refer to the Spooling chapter in this manual Alternate Syntax for Device Specification An alternate syntax is available for specifying right margin and page length when responding to the device prompt Using the alternate format you can specify pitch intensity and quality The success of specifying these additional attributes however depends on whether the corresponding fields have been defined by IRM at your site The syntax requires the use of a slash after the last semicolon see Figure 14 17 14 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler User Interface You can use the following codes to specify special device attributes in any order without separating punctuation to delimit the pieces Table 14 2 Alternate device attribute codes Boldface Page length Quality can be Q Q1 or Q2 e mwn S o o E o For example you could specify Figure 14 17 Specifying a device Using alternate syntax DEVICE LASER P LASER LANDSCAPE M132L100P16BQ2 In this example Figure 14 17 the margin M is set to 132 1 e M132 the page length L is set to 100 lines G e L100 the pitch P is set to 16 P16 the intensity to boldface B and the quality Q set to letter quality 1 e Q2 An absence of the B woul
556. suffer inappropriate access restrictions and will need special attention by IRM just after the conversion KILLing the DISV global a week or two before the conversion however may be worthwhile as a way of purging obsolete user data In multi CPU environments where each CPU has its own copy of the DISV global you should choose the busiest user node upon which to run the conversion in order to pick up the most comprehensive information from that node s DISV Cach sites should run the conversion from their busiest user node It is assumed that DISV is not translated so K DISV on the CPU where the conversion will be run Do this about two weeks before you perform the conversion as advance preparation DISV will be reset as soon as a user responds to a Select prompt Figure 5 4 KILLing DISV Sample code K Keay Do this only on the CPU where the conversion will run about two weeks beforehand as advance preparation Adding Explicit File Access for IRM If there are any files that are neither protected nor accessed by users e g the DOMAIN file 4 2 the conversion will not list them in any user s ACCESSIBLE FILE Multiple field 32 Before the conversion these types of files are accessible to everyone while after the conversion these files will only be accessible to users with programmer level access Therefore before the conversion assign a unique symbol character to otherwise unprotected files This will en
557. sure that at least those users with that unique symbol e g IRM staff will be granted access VA FileMan s Edit File option DIEDFILE can be used to edit the codes NOTE In previous documentation and data dictionaries it has been implied that the pound sign symbol character was reserved for File Access Security for IRM however this is not true It has merely been used as a convention July 1995 Kernel Systems Management Guide 5 11 Revised June 2008 Version 8 0 File Access Security Figure 5 5 Updating file access settings before conversion Select OPTION UTILITY FUNCTIONS Select UTILITY OPTION EDIT FILE MODIFY WHAT FILE USER DOMAIN lt Enter gt 227 entries Do you want to use the screen mode version YES n lt Enter gt NO NAME DOMAIN lt Enter gt DESCRIPTION No existing text Enter a unique symbol character for Edit NO lt Enter gt each level of access so that those Select APPLICATION GROUP lt Enter gt DEVELOPER lt Enter gt unprotected files will be assigned to DATA DICTIONARY ACCESS lt Enter gt IRM staff READ ACCESS lt Enter gt WRITE ACCESS lt Enter gt DELETE ACCESS lt Enter gt LAYGO ACCESS lt Enter gt AUDIT ACCESS lt Enter gt Summary of How the File Access Security Conversion Works The File Access Security conversion prepares the NEW PERSON file 200 for VA FileMan s method of file access lookup into a user s record for file access VA FileMan s abili
558. t Operation The option first prompts you for the task number Entering one question mark gets you a short explanatory message but entering two question marks puts you in the List Tasks option to find the task you are interested in dequeuing When you leave the List Tasks option you automatically return to the task number prompt If you enter the number of a nonexistent task List Tasks tells you and then prompts you for another task number If you enter the number of a task that does exist the option displays the task and asks you if you are sure Answering NO returns you to the task number prompt whereas a YES dequeues the task and then returns you to the task number prompt You can also enter a list of tasks to be dequeued The list can include single tasks separated by commas and ranges of tasks consisting of two numbers separated by a hyphen After you enter the list you are asked if you want to know the actual number of tasks in the list You are then asked if you want a display of the actual tasks that are about to be dequeued Only holders of the ZTMQ security key can dequeue any task Others can only dequeue their own tasks as identified by their DUZ Requeue Tasks Option Figure 22 5 Requeue Tasks option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Requeue Tasks XUTM REQ A benefit of the Dequeue Tasks option is that it is completely non destructive If you dequeue a task and
559. t 22 11 IO List 22 9 22 10 Job List 22 10 RUN Node 22 8 Schedule List 22 9 Status List 22 8 Task List 22 10 Mounted Volume Sets Definition 20 8 Multiple Copies Spooling 17 1 Multiple Managers and Load Balancing 21 11 MULTIPLE SIGN ON Field 3 21 Multi Term Look Up MTLU 25 1 Add Entries To Look Up File Option 25 1 25 8 25 9 Example 25 12 Add Modify Utility Keywords Option 25 12 Shortcuts Option 25 12 Synonyms Option 25 12 Add Modify Utility Option 25 2 25 8 25 12 Examples 25 18 Synonyms 25 17 Delete Entries From Look Up Option 25 1 25 8 Example 25 9 Functional Description 25 1 Implementation 25 20 Introduction 25 1 Keyword Option Example 25 19 Keywords 25 1 25 12 Index Associated with a Single Term and Multiple Terms 25 2 Keywords Option 25 2 25 16 Lexical Variants 25 2 LOCAL KEYWORD File 8984 1 25 1 25 2 25 3 25 8 25 9 25 12 LOCAL LOOKUP file 8984 4 25 22 LOCAL LOOKUP File 8984 4 25 1 25 2 25 5 25 6 25 8 25 9 25 12 LOCAL SHORTCUT File 8984 2 25 1 25 2 25 3 25 5 25 8 25 9 LOCAL SYNONYM File 8984 3 25 1 25 2 25 3 25 8 25 12 Look Up How to Request 25 2 Lookups on Database Files 25 2 Multi Term Lookup MTLU Main Menu 25 3 Multi Term Lookup MTLU Option 25 5 Example 25 6 Overview 25 1 Print Utility Option 25 1 25 6 Example 25 8 Shortcuts 25 1 25 12 Point to a Single Word or Phrase 25 2 Shortcuts Option 25 2 25 13 Example 2
560. t Keywords Additions Modifications to Keywords in which file CPT Which code in the CPT file 11044 lt Enter gt CLEANSING TISSUE MUSCLE BONE Select LOCAL KEYWORD NAME TISSUE SKIN ARE YOU ADDING TISSUE SKIN AS A NEW LOCAL KEYWORD Y lt Enter gt YES LOCAL KEYWORD NAME TISSUE SKIN lt Enter gt Example 3 Illustration of editing an existing Synonym entry Figure 25 19 Synonym option Sample user entries SH Shortcuts KE Keywords SY Synonyms Select Add Modify Utility Option SY lt Enter gt Synonyms Additions Modifications to Synonyms in which file CPT Select LOCAL SYNONYM TERM SLEEP TERM SLEEP lt Enter gt Select SYNONYM DREAM NIGHT July 1995 Kernel Systems Management Guide 25 19 Revised June 2008 Version 8 0 Multi Term Look Up MTLU Systems Management Implementation of Multi Term Look Up MTLU This is how a user would configure a new file to be used with MTLU The file you select would typically contain a free text field that more completely describes the record entry Users would then use a cross reference on this text field to perform lookups MTLU is distinguished from FileMan in that users can enter a narrative or phrase rather than a single term The cross reference can be either a VA FileMan Key Word In Context K WIC cross reference or you can create a custom MUMPS cross reference that calls the routine XTLKWIC shown below The ICD DIAGNOSIS file 80 is used as an example
561. t Checked Out to Myself PAID SIGN INTO MARTINEZ VIA TELNET TYPE DUSER RUM Capacity Planning ISC OFFICE MENU OPTIONS Or a Common Option DIUSER XUCORE XUTIO XUSPY XMMGR XUMAINT XUSITEMGR XUPROG XU SPL MGR XUTM MGR XUSER A6A EQUIP USER A6A USE PAID XTCM MAIN ISCSTAFF SS ee ee ee KNF Kernel New Features Help XUVERSIONEW HELP Halt XUHALT Continue XUCONTINUE Restart Session XURELOG MM MailMan Menu XMUSER NPI PROVIDER NPI SELF ENTRY XUS NPI PROVIDER SELF ENTRY TBOX User s Toolbox XUSERTOOLS VA View Alerts XQALERT Time XUTIME Where am I XUSERWHERE 6 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager User Interface Entering Three Question Marks to Display Option Descriptions Entering three question marks at any select prompt displays option descriptions from a word processing type field in the OPTION file 19 If entered at the select prompt for a menu within the primary tree the top level options are described then you are prompted whether you want to see descriptions for secondary or Common options Figure 6 4 Three question marks help Sample user dialogue Select Spooler Menu Option Allow other users access to spool documents Option name XU SPL ALLOW This option edits the OTHER AUTHORIZED USERS field of the SPOOL DOCUMENT file to allow other users access to a spool docu
562. t Enter gt to accept default LOCAL SHORTCUT FREQUENTLY USED NARRATIVE shortcut lt Enter gt to accept default Correct shortcut term LOCAL SHORTCUT ENTRY code lt Enter gt to accept default Correct The selected code is displayed OK YES lt Enter gt Return to the menu July 1995 Kernel Systems Management Guide 25 15 Revised June 2008 Version 8 0 Multi Term Look Up MTLU The Keywords option XTLKMODKY one of the three selections within the Add Modify Utility option is described below The following process chart shows the prompts and steps involved in using the Add Modify Utility option when adding or editing a keyword Figure 25 14 Add Modify Utility option Keywords process chart IF USER AT THIS PROMPT ANSWERS WITH SH Shortcuts KE Keywords SY Synonyms Select Add Modify YETI Tey Ob hens KE for Keywords lt Enter gt or up arrow lt gt Additions Modifications to Keywords in which file Name of entry in local reference file lt gt for list of entries lt Enter gt Which code in the file name file Code for which you wish to enter a keyword Select LOCAL KEYWORD NAME New text you wish to use as a keyword Existing keyword term lt Enter gt ARE YOU ADDING text AS A NEW LOCAL KEYWORD An at sign entered at this step deletes the entire entry LOCAL KEYWORD NAME keyword lt Enter gt to accept default Correct keyword term Return to
563. t Installation Option Load a Distribution Enter a Host File ZXG_EXPT DAT Distribution saved on Oct 13 2004009 29 08 Comment TEST PKGS This Distribution contains Transport Globals for the following Package s TEST Zel Want to Continue with Load YES lt Enter gt Loading Distribution a Want to RUN the Environment Check Routine YES lt Enter gt TEST 2 1 Use INSTALL NAME TEST 2 1 to install this Distribution Select Installation Option When the Distribution is Split Across Diskettes Distributions can come in a single host file see Figure 23 6 alternatively they can come on diskettes with the host file split up among the diskettes If you are installing from a distribution that is spread across diskettes the Load a Distribution option XPD LOAD DISTRIBUTION will ask you for subsequent diskettes e g Insert the next diskette 2 and Press the return key etc Insert the appropriate disk and press the lt Enter gt key and continue until the distribution is loaded 23 10 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations Loading Transport Globals from a Distribution Figure 23 7 Loading transport globals from a distribution Flowchart Select a distribution to load choose an HFS file KIDS lists build s exported in distribution Question continue with No Yes KIDS loads builds into XTMP KIDS starts proces
564. t Names 1 List Namespaces XUZ NAMESPACES 2 List Namespaces ZZ NAMESPACE LIST Type to stop or choose a number from 1 to 2 IRM should assign shallow secondary menus to facilitate menu jumping When a jump is requested the menu system searches all the way through the primary as well as the secondary looking for a match Users will be inconvenienced and system resources will be consumed if secondary menus are deep in terms of their hierarchical tree like structure You may occasionally find jumping disabled when you try to jump you may get a message that quick access is temporarily disabled Jumping will stay disabled until the needed menu trees are rebuilt Rubber band Jump The menu system s jump feature includes the ability to jump out to a destination option and then back again something like the motion of a rubber band The syntax for the Rubber band Jump request is the use of a double caret followed by the usual option specification For example Figure 6 7 Rubber band jump Sample user dialogue Select Systems Manager Menu Option TASKMAN USER 6 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager User Interface As with the single Up arrow Jump restrictions along the menu pathways are checked If you enter two carets without a following option specification name you are returned to the primary menu This technique is a quick way for you t
565. t asks you the date on which to put the device out of order From that date forward the Device Handler will not allow any jobs to use the device users will get a message that the device is out of order To clear the out of order status use this option again and delete the out of order date Device Identification and Cross references Devices can be selected in several ways from the DEVICE prompt Besides the NAME field 01 three other attributes MNEMONIC LOCAL SYNONYM and I can also be used to select devices When LOCAL SYNONYM is used the Device Handler searches the local CPU for a match Thus the same LOCAL SYNONYM value e g PRINTER can be used to identify several devices one per CPU 15 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Device Handler System Management When editing devices through VA FileMan two additional fields can be used for lookup VOLUME SET CPU and SIGN ON SYSTEM DEVICE You can separate these values with a period delimiter as follows Table 15 5 Sample period delimited pieces used for device lookup Period delimited Piece Description CPU All devices matching CPU CPU l All devices matching the CPU and I SYS All SIGN ON DEVICES SYS I All SIGN ON DEVICES matching 1 SYS CPU All SIGN ON DEVICES matching CPU SYS CPU I All SIGN ON devices matching CPU and I For example to display all signon devices on CPU BBB you could do Figure 15 9 Display
566. t given in the VOLUME SET file 14 5 the Manager July 1995 Kernel Systems Management Guide 22 37 Revised June 2008 Version 8 0 TaskMan System Management Operation FRUNState Description O O OO O Reached can continue to process the Schedule list but cannot start any new Submanagers WAIT State While in the WAIT state the Manager does not react to changes in its environment It does not process tasks enter PAUSE states or even stop after the Stop TaskMan option has been used You have two options described above that let you create or undo the WAIT state TaskMan cannot enter this state on its own it can only be initiated manually This is essentially a tool for you to tightly control the processing of tasks on your machines The description for this state always reads TaskMan Waiting 22 38 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 V KIDS July 1995 Revised June 2008 Kernel Systems Management Guide Version 8 0 KIDS Kernel Systems Management Guide Version 8 0 July 1995 Revised June 2008 23 KIDS System Management Installations Kernel Installation and Distribution System KIDS was introduced with Kernel V 8 0 Previously software was exported using a utility called DIFROM and installed by running INIT routines that the DIFROM utility created KIDS is the replacement for DIFROM and introduces significant revisions to the software distribution and installation pr
567. t group with the same effect Figure 18 7 Hunt groups Sample hunt group device name DEVICE PRTGROUP The Device Handler indicates which hunt group device was selected so the user knows where to look for the output If all members of the hunt group are busy Device Handler displays a message with this information July 1995 Kernel Systems Management Guide 18 7 Revised June 2008 Version 8 0 Special Device Issues System Management Hunt group devices can be created and managed with options on the Device Handler menu The hunt group device type HG type makes use of a multiple field that holds the names of printers and other devices that can be used interchangeably Figure 18 8 Hunt Group Manager menu options Select Systems Manager Menu Option Device Handler Select Device Handler Option Hunt Group Manager Select Hunt Group Manager Option Edit Hunt Groups Delete Hunt Groups List Hunt Groups Print Hunt Groups and Associated Devices If the user attempts to select a hunt group device HG type the Device Handler uses the B cross reference of the multiple field to find the device with the lowest internal entry number IEN in the DEVICE file 3 5 If this device cannot be opened the Device Handler finds the hunt group member with the next higher internal number and tries again The Device Handler discontinues the search after all hunt group members have been tried If the user attempts to select a printer or ot
568. t mode utility can be used in programmer mode as follows gt D XTVCHG Version Number Update Option The Version Number Update option XT VERSION NUMBER is used to update version numbers of one or more routines This option runs the XTVNUM routine to update or set the version number into a set of routines This option is locked with the XUPROGMODE security key The corresponding direct mode utility can be used in programmer mode as follows gt D XTVNUM Printing Routines List Routines Option The List Routines option XUPRROU uses the ZTPP utility to print a listing of entire routines The corresponding direct mode utility can be used in programmer mode as follows gt D ZTPP Comparing Routines Compare local national checksums report Option The Compare local national checksums report option XU CHECKSUM REPORT compares checksums for routines to the values in the ROUTINE file 9 8 It produces a report listing routines that differ by the following criteria e Patch or version where the version or patch may be correct but checksums are off e Local routines being tracked e Information is not on record for a patch e g test patches Nationally released routine checksums are sent by Master File Updates to the local ROUTINE file 9 8 automatically Local sites may also record checksums in the CHECKSUM VALUE field in the ROUTINE file 9 8 To compare local routines that are being tracked the CHECKSUM REPORT field s
569. t show the tasks that are in the Job List In other words it shows all tasks that are scheduled to run but not those that are currently being run or those that are ready to be run Future Tasks is not offered by the List Tasks option if the Schedule List and Waiting List are empty an unlikely occurrence at most sites Tasks waiting for a device Option The Tasks waiting for a device option shows just the Waiting List which can be a useful way of isolating problem printers If there are no tasks currently waiting for output devices to become available the List Tasks option will not show this choice Running tasks Option The Running tasks option shows tasks that are currently running REF For a discussion of how TaskMan knows a task is running please refer to the Troubleshooting topic in this chapter Dequeue Tasks Option Figure 22 4 Dequeue Tasks option SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Dequeue Tasks XUTM DQ The Dequeue Tasks option XUTM DQ allows you to unschedule a task so that the task still exists in the TASKS file 14 4 but is no longer in the Schedule Waiting or Job List The process of unscheduling a task is called dequeuing This option allows you to dequeue any one task or range of tasks A task that you dequeue has a status of NOT QUEUED in a List Tasks display 22 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Managemen
570. t shows the prompts and steps involved in using the Add Modify Utility option when adding or editing a shortcut Figure 25 12 Add Modify Utility option Shortcuts process chart 1 of 2 IF USER AT THIS PROMPT ANSWERS WITH SH Shortcuts KE Keywords SY Synonyms Select Add Modify UELI CY Openers SH TOF Shortcuts lt ENter gt or uUp arrow lt gt Additions Modifications to ShoOrtcucs LA whieh tale Name of entry in local reference file lt gt for list of entries lt Enter gt Select LOCAL SHORTCUT FREQUENTLY USED NARRATIVE New text you wish to use as a shortcut Existing shortcut term lt Enter gt ARE YOU ADDING text AS A NEW LOCAL SHORTCUT N O or lt Enter gt An at sign entered at this step deletes the entire entry LOCAL SHORTCUT FREQUENTLY USED NARRATIVE shortcut lt Enter gt to accept default Other text LOCAL SHORTCUT ENTRY Name or number of entry in LOCAL LOOKUP file 8984 4 you wish your shortcut to reference 25 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU Figure 25 13 Add Modify Utility option Shortcuts process chart 2 of 2 IF USER THEN AT THIS PROMPT ANSWERS WITH STEP If the selected number name corresponds to more than one entry they are shown and you are prompted to choose one If there is only one corresponding entry it is displayed and the following appears Taen OR r YEO 7 l
571. t the sending of bulletins is not suppressed SERVER REPLY 225 This SET OF CODES controls the MailMan reply to a server request The reply is a message returned to the user who has sent the server request and should not be confused with the local user to whom the bulletin is addressed If a reply is requested the software uses the return address of the sender as supplied by MailMan to send a local or network reply REF For an example of a server type option return message please refer to the Figure 11 2 The possible codes are No reply is sent the default A reply is sent to the return address of the sender only in the event of an error A reply is always sent SERVER DEVICE 227 Optionally use this field and the SERVER ACTION field 221 set to Q Queue server to control the number of server requests for this server option that can be processed at any one time Enter the name of a device of type RESOURCES in the DEVICE file 3 5 The number of instances of this server option that can run at any one time is limited to the number of resource slots in the selected resource device i e RESOURCE SLOTS field 35 in the DEVICE file 3 5 Testing if a Site is Reachable XQSPING Server Option You can use the XQSPING server option to invoke the Kernel XTSPING utility at a site This utility tests to see if the domain to which a message is addressed is reachable For example 1f you want to see 1f the network li
572. table from the current terminal Also in order for the check TEST DDBRT to work properly the user must already be in the Kernel menu system or must have set up developer variables through the XUP entry point Otherwise the test will always fail Storing Host Files in a Specific Directory By default the temporary host files created by the Browser device are stored in the current default directory You can optionally specify a path to a specific directory to store the temporary host files Make sure the directory you specify exists on all nodes CPUs where users can sign on On DOS systems do not specify the root directory since there is a limit on the number of files a DOS root directory can hold Finally make sure you change both the OPEN PARAMETERS and POST CLOSE EXECUTE fields in the Browser DEVICE file 3 5 entry to specify the directory replace DD with for example D BROW DD July 1995 Kernel Systems Management Guide 18 3 Revised June 2008 Version 8 0 Special Device Issues Figure 18 3 Cach and GT M Browser Device TERMINAL TYPE file 3 2 entry NAME P BROWSER RIGHT MARGIN 80 PAGE LENGTH 99999 SELECTABLE AT SIGN ON NO FORM FEED BACK SPACE SC 8 OPEN EXECUTE D OPEN DDBRZIS CLOSE EXECUTE D Chosk DDBRALS DESCRIPTION Browser Device Figure 18 4 Cach and GT M Browser Device DEVICE file 3 5 Entry NAME BROWSER ASK DEVICE YES SIGN ON SYSTEM DEVICE NO LOCATION OF TERMINAL HFS CRT
573. ted at signon It is specified by entering two carets at the menu s select prompt It resembles the Rubber band Jump but without an option specification name following the carets A Kernel module that provides a system for creating and displaying online documentation It is integrated within the menu system so that help frames associated with options can be displayed with a standard query at the menu s select prompt A procedure available on layered systems whereby a file on the host system can be identified to receive output It is implemented by the Device Handler s HFS device type An attribute of an entry in the DEVICE file 3 5 that allows several devices to be used interchangeably useful for sending network mail or printing reports If the first hunt group member is busy another member can stand in as a substitute Initialization of an software application INIT routines are built by VA FileMan s DIFROM and when run recreate a set of files and other software components July 1995 Revised June 2008 Kernel Systems Management Guide Version 8 0 JUMP JUMP START KERMIT MANAGER ACCOUNT MENU CYCLE MENU MANAGER MENU SYSTEM MENU TEMPLATE MENU TREES PAC PART 3 OF THE KERNEL INIT PATTERN MATCH July 1995 Revised June 2008 Glossary In VistA applications the Jump command allows you to go from a particular field within an option to another field within that same option You can also Jum
574. that can be used to accomplish the task at hand i REF Kernel and Kernel Toolkit Application Program Interfaces APIs are documented in the Toolkit Developer Tools chapter in the Kernel Developer s Guide Kernel and Kernel Toolkit APIs are also available in HTML format at the following Web address http vista med va gov kernel apis index shtml NOTE The Parameter Tools Supplement to Patch Description Patch XT 7 3 26 explains the functions available with the use of the Parameter Tools provides information on the Kernel PARAMETERS file 8989 5 and describes the associated Application Program Interfaces APIs REF This documentation can be downloaded from the VHA Software Document Library VDL Web site at http www va gov vdl application asp appID 12 The following Kernel Toolkit chapters were removed from the Toolkit section of this manual because they are superseded by subsequent software and documentation e Duplicate Record Merge The Kernel Toolkit Duplicate Record Merge documentation is superseded by the Duplicate Record Merge Patient Merge software documentation 1 e Kernel Toolkit Patch XT 7 3 23 The Duplicate Record Merge functionality provides a developer Merge Shell with options that allow users to check data files for duplicate entries and merge those entries if any are found These options provide functionality to combine duplicate records based on conditions established in customized applicat
575. the UCIs on the system and which Volume Sets they belong to In more complicated systems it is also used to describe how the UCIs in different environments correspond with one another e The TASKMAN SITE PARAMETERS file 14 7 Lets the system manager divide up the environments by both CPU and Volume Set This allows a fine degree of control over such parameters as priority partition size and retention time Taken together these files give IRM precise and powerful control over TaskMan s behavior Other minor pieces of information are scattered throughout other Kernel files especially the DEVICE 3 5 and OPTION SCHEDULING 19 2 files System Configuration Terminology TaskMan operates close to the level of the system architecture It must be capable of starting tasks in all the environments within a computer system This means it must know about those environments consequently the options routines files and documentation somehow must refer to that architecture July 1995 Kernel Systems Management Guide 20 7 Revised June 2008 Version 8 0 TaskMan System Management Overview One problem presented by system configuration is terminology Such system architecture features as UCIs directories Volume Sets and namespaces are not part of the ANSI M standard so different vendors use different terminology Although it would be ideal for Kernel to use a universal terminology none exists For historical reasons Kernel has settled on
576. the menu 25 16 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Multi Term Look Up MTLU The Synonyms option XTLKMODSY one of the three selections within the Add Modify Utility option is described below The following process chart shows the prompts and steps involved in using the Add Modify Utility option when adding or editing a synonym Figure 25 15 Add Modify Utility option Adding or editing a synonym process chart 1 of 2 IF USER STEP AT THIS PROMPT ANSWERS WITH 1 SH Shortcuts KE Keywords SY Synonyms Select Add Modify Utility Option SY for Synonyms lt Enter gt or up arrow lt gt Additione Modriiveations to Synonyms in which file Name of entry in local reference file lt gt for list of entries lt Enter gt The entry made at this step must be in all upper case letters Select LOCAL SYNONYM TERM New text you wish to use as a synonym Existing synonym term lt Enter gt ARE YOU ADDING text AS A NEW LOCAL SYNONYM An at sign entered at this step deletes the entire entry LOCAL SYNONYM TERM synonym lt Enter gt to accept default Other text LOCAL SYNONYM Select SYNONYM Existing term in LOCAL LOOKUP file 8984 4 for which you are entering a synonym July 1995 Kernel Systems Management Guide 25 17 Revised June 2008 Version 8 0 Multi Term Look Up MTLU Figure 25 16 Add Modify Utility option Adding or editing a synonym
577. the server request to be honored queued as soon as permitted by the TIMES DAYS PROHIBITED field 3 91 Notify local authorities This code causes the server request to create a TaskMan entry but does not schedule it to run A local mail group is notified along with the task number so that it can be approved locally and then scheduled to run using TaskMan s Requeue Tasks option Ignore any server requests This code causes the software to ignore all requests for this server option A bulletin or MailMan message can still be sent however When a server request is received the server option itself is executed similarly to the way a normal option is executed That is 1f a server request causes a server option to be run or queued the server option along with its associated entry action code header code routine and exit action code does not run until the option as a whole runs as scheduled by TaskMan How Can the Number of Instances of a Server Option Be Controlled To tie a server option to a device of type RESOURCES use the SERVER DEVICE field 227 and set the SERVER ACTION field 221 to Q Queue server in the OPTION file 19 This allows you to control how many instances of the server option can run at any one time Only as many server option processes can run at any one time as are set up in the associated device s RESOURCE SLOTS field 35 in the DEVICE file 3 5 So if 30 mail messages come in at the same time and att
578. the system Questions about access should be referred to the AIS Application Coordinator in Your service your facility Information Security Officer ISO or your IRM Service The names and Your Computer Access Coordinator 1s contact XUUSER ONE information 1223X specific to your 510 555 9999 site will be Your Facility Information Security Ofricer displayed here Two Xuser Your Alternate Information Security Officer Three Xuser NT Domain NT Username VHA NT Password VistA Access Code VistA Verify Code July 1995 Kernel Systems Management Guide 3 15 Revised June 2008 Version 8 0 Signon Security System Management Figure 3 12 Security Forms Sample Computer Account Access Policy form 4 of 4 COMPUTER ACCOUNT ACCESS POLICY Department of Veterans Affairs superstar VAMC The name of the user and location is displayed here For this example the user s name is Access Request at the Superstar VAMC ACCESS REQUEST SuperStar VAMC As an authorized user of VHA automated information systems AISs and having access to data stored in them I will be given sufficient access to perform my assigned duties I will use this access ONLY for its intended purpose and understand the following policies that apply to VA data and computer systems I agree to safeguard all passwords e g Access Verify codes electronic Signature codes assigned to me and am strictly prohibited from disclosi
579. the transport global on two lines one line labeled OLD and the other NEW NOTE Pointers are converted to FREE TEXT when exporting VA FileMan entries so these converted free pointers show up as differences when using the compare feature July 1995 Kernel Systems Management Guide 23 13 Revised June 2008 Version 8 0 KIDS System Management Installations Figure 23 9 Compare Transport Global to Current System option Sample comparison output Compare ZXP 1 0 to current site Routine ZUVXD File 3 2 Data Dictionary File 3 2 Data x OLD SZIS 2 9 8 SCZ ANT RO A N IBT Oe Ary Pee ECAT aR eC Ta NEW ETO 23946 SOHO See C7 1 BAS 7 CEA SCD 7 pe AS X OLD AGALS 2744513 8SC 26 AnA T 2 SC 27 93r SXF 2X NEW MEV GAD OA Sy SSCL D6 Anes x OLD SZIS 2 60 8 PCA ZTT LA OCIA he SE AT EE TS G A a LD ee SA G ZT ANES NEW SEATS 6048 SO I AY OSC oO BASOEI Ta OAS 7 E ADD POTN C O OS le Se HELP FRAME BULLETIN 23 14 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations This option was updated with Kernel Patch XU 8 0 393 to add a side by side comparison in columnar format which only works if Kernel Toolkit Patch XT 7 3 93 has also been installed as shown below Figure 23 10 Compare Transport Global to Current System option Sample comparison output in columnar format Select Kernel Installation amp Distrib
580. ther devices that do not fit a particular category should be given a type of OTH Magtape devices should have a type of MT Obsolete Sequential Disk Processor is a predefined allocated disk space used for sequential processing use HFS Spool device is a predefined allocated disk space similar to SDP However access to the spool device can be achieved from multiple users simultaneously Bar code reader This type identifies the device as a barcode reader This type and the associated functionality provides the vehicle to READ and WRITE to host level files Instead of directing reports to a printer the results could be placed into an OpenVMS or UNIX Linux file This would allow a non M based statistical software application or spreadsheet to use data produced by the M based application by simply extracting data from the host file port identification l A generic device entry with a device type of VTRM can be established TRM Virtual Terminal Server devices are those that are associated with a dynamically created M for users who log into the system through Terminal Servers or other network protocols available the next available device in the Hunt Group is selected Resources is a type used for special sequencing of tasks that do not require a particular device CHAN Network Channels are high speed devices that use network protocols e g TCP IP IMPC Imaging work station device reserved for future use for VistA Imag
581. tine Tools 26 1 Routines by Patch Number 26 5 Running tasks 22 4 Schedule Unschedule Options 7 4 22 17 22 19 22 23 Scheduling 7 4 Search File Entries 5 6 Secure Menu Delegation 9 7 9 9 Secure Menu Management 9 2 9 5 Select another task 19 6 Select Options to be Delegated 9 7 9 9 9 10 Send Alpha Beta Usage to Programmers 23 23 Send Test Pattern to Terminal 15 12 Server type 11 1 Set Backup Reviewer for Alerts 10 10 Shortcuts Multi Term Look Up MTLU 25 2 25 13 Example 25 18 Show a Delegate s Options 9 11 Show Error Log 22 25 Show the Security Keys of a Particular User 9 9 Show Users with Selected Primary Menu 7 6 Site Parameters Edit 21 13 Specify Allowable New Menu Prefix 9 5 9 1 Spool Device Edit 17 9 Spool Management 17 7 Spooler Menu 17 3 Spooler Site Parameters Edit 17 8 Statistics 5 6 Stop task 19 4 Stop Task Manager 22 16 Stop TaskMan 22 38 Surrogate for which Users 10 10 Switch Identities 7 9 Switch UCI 2 12 SYNC flag file control Option 22 16 Synonym Multi Term Look Up MTLU Example 25 19 Synonyms 6 1 6 3 6 5 6 6 7 3 7 19 12 2 Multi Term Look Up MTLU 25 2 25 17 Systems Manager Menu 7 1 23 2 27 1 Taskman Error Log 13 2 Taskman Error Log Menu 22 24 Taskman Management 13 2 TaskMan Management Menu 22 1 Taskman Management Utilities 13 2 22 7 TaskMan User 19 2 19 3 19 4 22 33 Tasks waiting for a device 22 4
582. tiple copies of the TaskMan globals you must use Schedule Unschedule Options on the same Volume Set CPU where your task originated when you requeue the a task Otherwise the existing future task in the TASKS file will not be found and deleted when you enter a new time in the QUEUED TO RUN AT WHAT TIME field DEVICE FOR QUEUED JOB OUTPUT This field is where you can give the task an output device For print Report type options this is obviously mandatory for run or action types you need to consider if the option needs an output device Modifying this value for an already scheduled task merely causes a direct change to the currently scheduled task Tasks with an output device are assigned a process name of Task where is the task number tasks with no output device are assigned a process name of BTask with B meaning background QUEUED TO RUN ON VOLUME SET This field lets you designate a Volume Set or CPU for the task other than your current one This field is only useful for options that do not have a device selected because most devices are tied to a CPU and thus the task must run on the CPU that has that device Modifying this value for an already scheduled task merely causes a direct change to the currently scheduled task Running a task on each CPU for a given option may at times be useful consider XQBUILDTREEQUE In such cases make multiple entries in the OPTION SCHEDULING file 19 2 and use the QUEUED
583. to a G type and Submanagers behave the same e Compute Server C The C type should be selected when multiple Volume Sets map to the same TASKS 14 4 and SCHEDULE files as with the P type but when the Volume Set CPU in question runs users not tasks The Manager will not start on a C type Tasks that explicitly request to run on a C type are transferred to it by being placed in the Link Waiting List a Submanager is then jobbed across to the C type Volume Set CPU Submanagers started on a C type only process tasks in the Link Waiting List for their Volume Set e Other Non TaskMan O Neither the Manager nor the Submanager will run on O types Tasks sent from or to an O type are rejected 21 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 TaskMan System Management Configuration Because of the field s crucial role in guiding TaskMan s behavior the field is required ENVIRONMENT FOR DCL The ENVIRONMENT FOR DCL field only has meaning to DSM for OpenVMS and Cach systems It is set to the OpenVMS username of the DSM environment manager account Setting it to this username causes the Manager to use M7SPAWN to SUBMIT Submanagers to run This method requires that certain DCL command files exist along with a TASKMAN OpenVMS user account and directory REF For descriptions of the needed setups please refer to the Running TaskMan with a DCL Context topic in this chapter If the field is empty t
584. ts 23 8 Create 23 2 23 5 24 10 24 11 Definition 23 1 Environment Check 23 7 Export 23 2 Install 23 3 Load from Distribution 23 3 23 7 23 9 Load from PackMan Messages 23 3 23 7 Print 23 3 23 7 23 12 Processing 23 16 Verify 24 10 Verifying Checksums 23 12 Transport Mechanism Distributions 23 5 TRM or VTRM Device Edit Option 15 6 TRM Type 18 18 Troubleshooting Device Handler 15 12 Menu Manager Variables 7 20 TaskMan 22 9 22 12 22 27 22 36 Turn Data Audit On Off Option 5 5 TYPE Field Index 42 Kernel Systems Management Guide Version 8 0 DEVICE File 3 5 15 2 15 3 21 13 VOLUME SET File 14 5 21 7 TYPE Field 4 OPTION File 19 11 1 11 3 TY PE AHEAD Field 2 10 3 7 3 22 Types BROWSER 18 3 COMPUTE SERVER 21 7 FILE SERVER Obsolete 21 7 GENERAL PURPOSE VOLUME SET 21 7 OTHER NON TASKMAN VOLUME SET 21 7 P BROWSER 18 3 PRINT SERVER 21 7 RESOURCES 11 2 TRM 18 18 U UCI Definition 20 8 Switching 7 12 21 2 UCI ASSOCIATION File 14 6 20 5 20 7 21 1 21 8 22 35 FROM UCI Field 21 9 FROM VOLUME SET Field 21 9 Standardized VA Cach and GT M Configuration 21 10 TO UCI Field 21 9 TO VOLUME SET Field 21 9 UCI Association Table Edit Option 21 8 UCI ASSOCIATION TABLE Field 21 9 Unassign Editor Option 12 5 Understanding DUZ the User Number 5 9 Unload a Distribution Option 23 20 23 21 Unsuccessful tasks Option 22 4 Up arrow Jump 6 1 6 5 6 7 6 8 6 9 7 13
585. ts the errors or warnings that might be included in the return message from the XQSCHK server option along with an explanation of each Table 11 3 XQSCHK server option Error Warning messages Can t unload name of server from message message subject The option option name is not in the Option File Option option name is not shown as a server type option but a type Option name is marked as Out Of Order with the message message The expected data in DIC 19 option number 220 is missing No bulletin associated with this option default XQSERVER is missing from system Option option name points to a bulletin not in the bulletin file Option option name points to a mail group not in the Mail Group File There are no mail groups associated with the bulletin bulletin name Kernel Systems Management Guide The name of the server option to be tested could not be unloaded from the text of the message sent to waken the XQSCHK server option The message should contain just the name of the server option to be tested and nothing more XQSCHK ignores blank lines up to 4 and any lines of text that follow the line where it finds the options name There is no option in the remote site s OPTION file 19 that matches the name of the server option that was unloaded from the text of the message The string it is using to search the OPTION file 19 is returned in option name The option is not
586. ty 21 18 Restarting Aborted Installations KIDS 23 20 Restrict Availability of Options Option 7 11 RESTRICT DEVICES Field 7 11 Retrieving Spool Documents 17 3 Reverse Locks 8 3 8 5 REVERSE NEGATIVE LOCK Field 8 5 Revision History 111 Documentation 111 Patches vii RIGHT MARGIN Field TERMINAL TYPE File 3 2 15 8 Rollup Patches into a Build Option 24 9 Routine Compare Routine Compare Current with Previous Option 27 2 Routine Edit Option 26 5 Routine Editor 28 3 28 5 ROUTINE Field 25 11 1 11 3 11 9 ROUTINE File 9 8 23 12 24 10 24 12 26 6 26 7 26 8 28 3 Routine Tools 26 1 Analyzing Routines 26 2 Compare local national checksums report Option 23 12 24 11 24 12 26 6 26 7 Compare Routines on Tape to Disk Option 26 7 Compare Two Routines Option 26 7 Comparing Routines 26 6 Delete Routines Option 26 8 Deleting Routines 26 8 Flow Chart Entire Routine Option 26 4 Flow Chart from Entry Point Option 26 5 Group Routine Edit Option 26 5 Input Routines Option 26 8 List Routines option 26 6 Load Routines 26 8 Load refresh checksum values into ROUTINE file Option 26 8 Output Routines Option 26 8 Overview 26 1 Printing Routines 26 6 Routine Edit Option 26 5 Routine Tools Editing Routines 26 5 Routines by Patch Number Option 26 5 Save Routines 26 8 User Interface 26 2 Variable Changer Option 26 5 Version Number Update Option 26 6 Routine Tools Menu 26 1 Routines RR 26 8 P
587. ty e g starting stopping and monitoring options please refer to the Alpha Beta Tracking topic in Chapter 14 KIDS Developer Tools in the Kernel Developer s Guide July 1995 Kernel Systems Management Guide 23 23 Revised June 2008 Version 8 0 KIDS System Management Installations 23 24 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 24 KIDS System Management utilities KIDS provides the following utility options Figure 24 1 KIDS Utilities menu options Kernel Installation and Distribution System XPD MAIN Utilities XPD UTILITY Build File Print XPD PRINT BUILD Install File Print XPD PRINT INSTALL FILE Convert Loaded Package for Redistribution XPD CONVERT PACKAGE Display Patches for a Package XPD PRINT PACKAGE PATCHES Purge Build or Install Files XPD PURGE FILE Rollup Patches into a Build XPD ROLLUP PATCHES Update Routine File XPD ROUTINE UPDATE Verify a Build XPD VERIFY BUILD Verify Package Integrity XPD VERIFY INTEGRITY These utilities can be used both by developers and by sites who install software created by KIDS July 1995 Kernel Systems Management Guide 24 1 Revised June 2008 Version 8 0 KIDS System Management Utilities Build File Print Option The Build File Print option XPD PRINT BUILD prints out the build entry for a software application It lists the complete definition of the software including all files components install question
588. ty to protect data within files on fields and templates remains the same The steps that occur when the conversion is run are outlined below 1 The structure for implementing the file access method is set up via the following a Placing the data dictionary DD for the ACCESSIBLE FILE Multiple field 32 in the NEW PERSON file 200 This multiple will be permanently put in place by running the File Access Security conversion b Installing menu options help frames and templates used for maintaining the user file access method i e entries with the XUFI namespace 2 Each user s FILE MANAGER ACCESS CODE field 3 is used to add entries in the ACCESSIBLE FILE Multiple field 32 by a Creating a list of files to be processed by examining each file s protection codes Files that meet both of the following requirements are temporarily stored in the UTILITY J global e Files that have protection defined e Files with protection not equal to NOTE Files that lack any protection will be bypassed Such unprotected files will not later be listed in anyone s ACCESSIBLE FILE Multiple field 32 Protection should therefore be applied before running the conversion so that at least some users e g IRM Staff will be granted access 5 12 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security b Examining each user in the NEW PERSON file 200 Each user meeting all of the followi
589. u 3 24 3 26 5 1 5 8 5 10 5 14 User Management Options on the Operations Menu 3 26 User Stacks 7 12 7 13 7 16 Nodes 7 16 User Status Report Option 3 28 July 1995 Revised June 2008 Index USER XQALERT API 10 5 Users Adding New 3 8 Attributes 3 1 3 9 3 10 3 17 Deactivating 3 24 Deactivating Automatically 3 25 Introduction 1 1 Reactivating 3 26 Terminating 3 24 User s Toolbox Menu 2 3 2 6 2 7 2 8 2 9 2 11 4 1 4 2 6 7 6 8 17 3 19 2 Display User Characteristics Option 2 11 Electronic Signature code Option 4 1 Using File Access Options 5 9 Hunt Group Device Without Using the Hunt Group 18 9 Multi Term Lookup MTLU Option 25 5 Print Utility Option 25 6 Ranges of File Numbers 5 9 Security Keys with Reverse Locks 8 5 Utilities for MTLU Option 25 8 Utilities G 28 1 RFIND 26 2 ZTPP 26 6 A ZTMOVE Toolkit 22 34 Block Count 12 6 DIFROM 23 1 23 4 23 6 PackMan Compare 26 7 Secure Menu Delegation Menu 8 1 XINDEX 26 2 26 3 Error Codes 26 2 26 4 XQSCHK Server Option 11 6 XQSPING 11 5 XTSPING 11 6 Utilities For MTLU Menu 25 8 Utilities Menu KIDS 24 1 Utility Functions Menu 5 6 UTILITY J Global 5 12 5 13 7 12 7 13 Purging 7 12 V VA FileMan Browser Device 18 1 File Access Security Properties 5 5 Kernel Systems Management Guide Index 43 Version 8 0 Index Limited File manger Options Build Option 9 5 Line Editor 2 10 3 20 3 21 5 2 5 5 M
590. u and is locked with the XQSMDFM security key First you must have created a SORT PRINT or INPUT template for a VA FileMan file Once you have created a template you can make this template available as an option to your users by turning it into an option You can create three types of options e kdit type option from an EDIT template e Print type option from PRINT and SORT templates e Inquire type option from either a PRINT template or a file name Once you have turned the template into an option you can assign that option to your users as you deem necessary Then when a user uses the option they execute the PRINT SORT or INPUT template from which the option was created July 1995 Kernel Systems Management Guide 9 5 Revised June 2008 Version 8 0 Secure Menu Delegation Example Suppose you have created a PRINT template called LRZ REFERRAL PRINT for the Lab s REFERRAL file To turn this PRINT template into an Inquire option use the Limited File Manager Options Build option as shown below Figure 9 3 Limited File Manager Options Build Sample user dialogue Select Delegate s Menu Management Option Limited File Manager Options Build The menu options you build or edit must begin with the namespace LRZ The option types that may be built are P rint E dit and I nquire and you must have a template or templates ready to be included in the option Or enter D elete to DELETE an option Select Option Type
591. u can then be assigned to a user as described in the Signon Security User Interface chapter with one of several options on the User Edit menu Figure 7 3 Defining local primary menus IRM Sample user dialogue Select OPTION to edit ZZSTAFF MENU Located in the Z Local namespace ARE YOU ADDING ZZSTAFF MENU AS A NEW OPTION THE 721ST Y lt Enter gt YES OPTION MENU TEXT Staff Menu NAME ZZSTAFF MENU lt Enter gt MENU TEXT Staff Menu lt Enter gt PACKAGE lt Enter gt OUT OF ORDER MESSAGE lt Enter gt LOCK lt Enter gt REVERSE NEGATIVE LOCK lt Enter gt DESCRIPTION 1 gt This is the primary menu for staff members 2 gt lt Enter gt EDIT Option lt Enter gt TYPE menu Select ITEM XUCORE lt Enter gt Core Applications ARE YOU ADDING XUCORE AS A NEW MENU THE 1ST FOR THIS OPTION Y lt Enter gt YES MENU SYNONYM lt Enter gt SYNONYM lt Enter gt DISPLAY ORDER 10 Select ITEM XUSPY lt Enter gt System Security ARE YOU ADDING XUSPY AS A NEW MENU THE 2ND FOR THIS OPTION Y lt Enter gt YES MENU SYNONYM lt Enter gt SYNONYM lt Enter gt DISPLAY ORDER 20 Select ITEM XT KERMIT MENU lt Enter gt Kermit menu ARE YOU ADDING XT KERMIT MENU AS A NEW MENU THE 3RD FOR THIS OPTION YES lt Enter gt YES MENU SYNONYM lt Enter gt SYNONYM lt Enter gt DISPLAY ORDER 30 Select ITEM lt Enter gt CREATOR SITE MANAGER lt Enter gt HELP FRAME lt Enter gt PRIORITY lt Enter gt Se
592. u reactivate a user you are asked whether to deny access to old mail messages If the reactivated user account is a less privileged account than previously it may be appropriate to deny the user access to messages that were received in the user s prior capacity Even if that user s mailbox was deleted at termination once the user is reactivated an old message would be delivered if responded to by another recipient User Management Options on the Operations Menu Kernel provides a set of options for IRM to monitor and support users logged onto the system These options are on the User Management Menu XUOPTUSER under the Operations Management menu XUSITEMGR as shown below Figure 3 16 User Management Menu options SYSTEMS MANAGER MENU EVE Operations Management XUSITEMGR User Management Menu XUOPTUSER Find a user XU FINDUSER List users XUSERLIST Print bono OG XUSC LIST Release user XUSERREL User Inquiry XUSERINQ User Status Report XUUSERSTATUS 3 26 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Signon Security System Management Find a User Option You can use the Find a User option XU FINDUSER to find a user who is currently signed on to the system in this UCI group If you are on the same CPU as the user this option will also show the menu path of the user The option finds users based on the CUR cross reference of the SIGN ON LOG file 3 081
593. ue Wed Thu Fri Sat oun LOGI Pats LO NOVH L992 T4112 20 NOV 1992 10 44 Byte lim 64000 Poyt lm 0 JTquota 4096 WSdef 2048 WSquo 4096 WSextent 16384 Porlquo 100000 non Figure 21 19 Example of OpenVMS TASKMAN Queue ISC6A1S SH QUE FULL TMSISC6A1 Batch queue TMSISC6AI1 available on ISC6Al1 BASE_PRIORITY 4 JOB_LIMIT 50 OWNER DEV TASKMAN PROTECTION S E 0 D G R W W LSCOALS 21 20 Kernel Systems Management Guide Version 8 0 DEV TASKMAN July 1995 Revised June 2008 22 TaskMan System Management Operation This chapter describes how to operate TaskMan This chapter discusses the following TaskMan Management Menu Taskman Management Utilities Scheduling Options Taskman Error Log Menu Troubleshooting TaskMan Management Menu The Taskman Management menu XUTMGR is the main point of entry into the TaskMan options It contains the following options Schedule Unschedule Options One time Option Queue Taskman Management Utilities List Tasks Dequeue Tasks Requeue Tasks Delete Tasks Print Options that are Scheduled to run Cleanup Task List Print Options Recommended for Queueing The TaskMan Management Utilities submenu and the scheduling related options are discussed later in this chapter The options for listing dequeuing requeuing deleting and cleaning up tasks are discussed first July 1995 Kernel Systems Management Guide 22 1 Revised
594. uide July 1995 Version 8 0 Revised June 2008 Il Menu Manager July 1995 Revised June 2008 Kernel Systems Management Guide Version 8 0 II 1 Menu Manager I 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 6 Menu Manager User Interface Kernel s menu system presents menu options within VistA software in a standard fashion Once you become familiar with using the menu system in one application using other applications will be easier since the same rules apply Navigating Kernel s Menus When you successfully sign into the computer system Menu Manager presents your primary menu options Your primary menu is the top level menu assigned to you by IRM Most options that are available to you are available from your primary menu or from a sub menu attached to your primary menu The menu system prompts you with a Select menu name Option prompt For example in a menu named Billing Menu Manager would prompt you with Select Billing Option You can navigate through the menu system by responding to this prompt in different ways which are described in this chapter You can enter question marks to see option choices and obtain online help You can enter an option s synonym or the first few letters of its menu text using upper or lowercase to select the option Or you can enter a caret along with the option specification option menu text or synonym to jump to the destination option rather then tra
595. up after the task e Closes the output device e Performs any commands left for it by the task etc Running completely without user interaction each task performs the work it was created to do and then quits returning control to the Submanager that started it The task may leave instructions for its Submanager such as to requeue the task so that it runs again later or to delete the task s entry from the TASKS file 14 4 but the task itself finishes before the Submanager continues After Submanagers have run all available tasks they wait an interval before quitting This period called Submanager retention time allows the Submanager to keep its partition open for new tasks for a while so that the Manager need not start a new Submanager Every time a new task shows up during the retention time the Submanager starts its main loop over again returning to retention again only after all new tasks have been run When the Submanagers eventually reach the end of their retention time they quit July 1995 Kernel Systems Management Guide 20 3 Revised June 2008 Version 8 0 TaskMan System Management Overview Figure 20 1 TaskMan Manager and Submanager process flow diagram Manager Loop Job off a new Submanager No Yes Are there enough Submanagers Does the task Place task need a device on Job List Is there an overdue task Place task on I O List for device Submanager Loop Are any other task
596. urrence of each error for T 1 QUEUE Option 13 4 PAC Programmer Access Code Field 3 22 Package Definition 23 1 PACKAGE File 9 4 5 6 23 1 23 4 23 5 23 6 24 7 PackMan Compare Utilities 26 7 PackMan Messages 23 3 23 6 23 7 23 9 PAGE LENGTH Field TERMINAL TYPE File 3 2 15 8 18 10 18 11 PARAMETER DEFINITION File 8989 51 10 10 Parameters Checked during Signon 3 2 OpenVMS Interactive Logins 3 3 PARAMETERS File 8989 5 10 10 VI 2 PARENT OF QUEUABLE OPTIONS Menu 3 28 7 1 7 12 17 9 22 18 XUXREF 7 5 XUXREF 2 7 6 Parents Cross reference 12 5 July 1995 Kernel Systems Management Guide Index 31 Revised June 2008 Version 8 0 Index Parsing Algorithms 3 17 Part 3 of the Kernel Installation See File Access Security 3 19 5 1 Partition Size 21 3 PASSWORD Field 15 7 15 8 Passwords Defining 2 3 PATCH APPLICATION HISTORY Field Multiple 23 5 Patches History vii KIDS 23 5 23 6 23 15 24 9 Patient Alert List for specified date Option 10 9 PATIENT File 2 5 8 PATIENTSXQALERT API 10 5 PAUSE State 21 7 22 37 P BROWSER Type 18 3 PERFORM DEVICE CHECKING Field 3 2 Permitted Devices Options 7 11 PERMITTED DEVICES Field Multiple 7 11 PERSON LOOKUP Field 8 4 Phantom Jumps 7 14 7 15 PHONE 3 Field 3 22 PHONE 4 Field 3 22 PHONE HOME Field 2 9 3 22 Pitch 14 6 Place Taskman in a WAIT State Option 22 15 POST SIGN IN MESSAGE Field 3 7 Post sign in Text Edit Option 3
597. urth piece of Y Since the Volume Set and CPU are identified the TaskMan site parameters can be tuned for each specific Volume Set and CPU affected Systems running Managers on more than one CPU need one entry for each CPU where a manager is running LOG TASKS Set the LOG TASKS field to YES to make tasks log in and out through the signon log the way interactive users do How to set this is up to the individual site it does consume space and resources TASK PARTITION SIZE The TASK PARTITION SIZE field is used to assign partition sizes for tasks The value from this field is plugged directly into the JOB command used to create new submanagers If this field is left blank all tasks receive the operating system s current default value This field should only be used by system managers who thoroughly understand how their vendor s version of M handles partition sizes with the JOB command SUBMANAGER RETENTION TIME The SUBMANAGER RETENTION TIME number determines how many seconds submanagers should wait while looking for new tasks The purpose of this field is to reduce the number of JOB commands needed to process a site s tasks By keeping old Submanagers around to run new tasks new process creation is significantly reduced TASKMAN JOB LIMIT If there are more active processes on the system than the number stored in the TASKMAN JOB LIMIT field TaskMan will not create new submanagers to handle tasks Task processing will be left to exist
598. user can pick the spool device at the device prompt to send output to the spooler PAC Programmer Access Code For users who have been granted the Programmer Mode option along with the XUPROG and XUPROGMODE security keys a Programmer Access Code can be assigned as additional security If a PAC is defined Kernel prompts for the PAC just before allowing a user to enter programmer mode If this field is NULL a PAC is not asked CAN MAKE INTO A MAIL MESSAGE This field controls whether a spooled document can be transformed into a regular mail message for use within MailMan DISUSER If set to YES disables access to the system for this user without terminating the user s account FILE RANGE Users who have VA FileMan privileges to create files can be given a numeric range of numbers to use as file numbers Assigning number ranges acts as a safeguard to keep users from picking a number within a range that is nationally reserved for VistA software applications It can also serve local database administration needs of segmenting local development by number ranges TERMINATION DATE As mentioned in the topic about terminating users the TERMINATION DATE indicates when a user s access privileges should be revoked ALWAYS SHOW SECONDARIES If set to YES contents of a user s SECONDARY MENU OPTIONS are shown when the user enters one question mark at a menu prompt Otherwise the user must enter two question marks to see their secondary m
599. ust not involve user input There is nothing to prevent you from queuing an option of the wrong type or from queuing one that prompts the user for input but doing so results in a failed task You must be conscious of the nature of the task when you consider creating one that performs an option If the option itself will not run in the background then queuing it 1s pointless Even options that themselves queue tasks probably cannot be queued because most of these ask the user for an output device or a run time Software applications can make recommendations for scheduling of options This is a great help to site managers REF Recommendations for scheduling Kernel options can be found in the Kernel Installation Guide and the Kernel Technical Manual PARENT OF QUEUABLE OPTIONS Menu Some options that are intended to be queued are not intended to be run interactively so placing such options on a user menu could cause problems The PARENT OF QUEUABLE OPTIONS menu ZTMQUEUABLE OPTIONS a menu type option has no parent in the menu tree and is intended to be used as the parent of all such options Printing Options Recommended to Run and Scheduled to Run Figure 22 21 Print Options Recommended for Queueing and Print Options that are Scheduled to run options SYSTEMS MANAGER MENU EVE Taskman Management XUTM MGR Print Options Recommended for Queueing XUTM BACKGROUND RECOMMENDED Print Options that are Scheduled to run XUTM BACKG
600. usually PC workstations linked into the larger network They can access the core computers but cannot be accessed themselves Some system managers may wish to have a completely isolated computer for testing They can cut it off from the rest of the world by making entries for all the other Volume Sets and setting this field to NO for each of them This explicitly tells TaskMan it cannot reach the other Volume Sets OUT OF SERVICE Obsolete This field is obsolete and should only be set to NULL use the TYPE field REQUIRED VOLUME SET Obsolete This field is obsolete and should only be set to NULL July 1995 Kernel Systems Management Guide 21 7 Revised June 2008 Version 8 0 TaskMan System Management Configuration TASKMAN FILES UCI The TASKMAN FILES UCI field should be set to the name of the UCI that holds the ZTSCH and ZTSK globals usually the manager UCI The answer should not contain a comma and Volume Set name e g WAH PSA just the UCI name e g VAH This field is required TASKMAN FILES VOLUME SET The TASKMAN FILES VOLUME SET field should be set to the name of the Volume Set that holds AYZTSCH and ZTSK A NULL value means this Volume Set holds its own TaskMan files which is usually the case REPLACEMENT VOLUME SET The REPLACEMENT VOLUME SET field should be set to the name of a Volume Set to which tasks can be sent if this Volume Set is unavailable A REPLACEMENT VOLUME SET should be essentially e
601. ution System Option LOad4 Dist ri bucion Verify Checksums in Transport Global Print Transport Global Compare Transport Global to Current System Backup a Transport Global Install Package s Restart Install of Package s Unload a Distribution Select Installation Option 4 lt Enter gt Compare Transport Global to Current System Select INSTALL NAME XU 8 0 381 lt Enter gt Loaded from Distribution Loaded from Distribution 9 14 06C125392 52 gt DEMO COMPARE Created on Sep 14 2006 12 39 17 This Distribution was loaded on Sep 14 2006 12 39 52 with header of DEMO COMPARE Created on Sep 14 2006 12 39 17 Lie COnsiSstedor the following Instar ts KU e 0 33e Select one of the following Full Comparison Second line of Routines only Routines only Columnar Routine compare Type of Compare 4 lt Enter gt Columnar Routine compare DEVICE HOME lt Enter gt Telnet terminal Compare XU 8 0 381 to current site Routines Only of routines from KIDS XU 8 0 381 and disk Routine XU8P381 not on disk Routine 1 XUTMTP SEA RDS TaskMan ToolKit 1 XUTMTP SEA RDS TaskMan ToolKit ta Printy Part 1 204718720060 681 9 lt 5 Printy Part 1 0472472003 1206 2e FOO RERNE L O20 OO O04 ae yo OLEFA fom O RE RN Pes 20 oO Loo wae eee UT Backing Up Transport Globals The Backup a Transport Global option XPD BACKUP creates a MailMan message that will back up all current routines on your system that would be replaced
602. ution menu XPD DISTRIBUTION MENU see Figure 23 2 The distribution portion of KIDS allows developers to e Define the contents of a software application in a build entry e Create transport globals from build entries e Export transport globals by creating distributions 23 2 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 KIDS System Management Installations Figure 23 2 Edits and Distribution menu options Select Kernel Installation amp Distribution System Option Edits and Distribution Create a Build Using Namespace Copy Build to Build Edit a Build Transport a Distribution Old Checksum Update from Build Old Checksum Edit Routine Summary List Version Number Update Select Edits and Distribution Option REF For a description on how application developers use the KIDS build and distribution options please refer to the KIDS Developer Tools chapter in the Kernel Developer s Guide Installations The installation related options are located on the Installation menu XPD INSTALLATION MENU see Figure 23 3 The installation portion of KIDS allows sites to e Load transport globals from KIDS distributions e Load transport globals from KIDS PackMan messages e Print out the contents of loaded transport globals before installing them e Compare the contents of loaded transport globals to the current system before installing them e Install loaded transport globals Figure 23 3 In
603. ve Options Previously Delegated Option 9 10 Remove Out Of Order Messages from a Set of Options Option 7 10 7 11 Remove Taskman from WAIT State Option 22 15 REPLACE 23 21 Replace a Delegate Option 9 9 REPLACEMENT VOLUME SET Field 21 8 Replicate or Replace a Delegate Option 9 7 9 10 Report Menu for Alerts Menu 10 8 July 1995 Kernel Systems Management Guide Index 33 Revised June 2008 Version 8 0 Index Reports Alerts 10 8 10 9 10 10 First Occurrence of Each Error 13 4 First Two Occurrences of Each Error 13 5 Secure Menu Delegation 9 11 Reprint Access Agreement Letter Option 3 17 REQ S ZTLOAD API 22 33 Requeue Tasks Option 11 2 20 8 22 5 22 33 REQUIRED VOLUME SET Field 21 7 RESCHEDULE FREQUENCY Field 22 19 22 21 22 23 22 24 RESCHEDULING FREQUENCY Field 6 22 22 Resource Device Edit Option 18 14 Resource Devices Editing 18 14 RESOURCE File 3 54 18 13 RESOURCE SLOTS Field 18 13 RESOURCE SLOTS Field 35 11 2 11 5 Resources Creating Resource Devices 18 14 Devices RESOURCE File 3 54 18 13 Limiting Simultaneous Running of a Particular Task 18 13 Running Sequences of Tasks 18 13 Special Device Issues 18 13 SYNC FLAGs 18 13 System Management 18 13 RESOURCES Device Type 11 2 Response Time 3 5 21 4 Restart Install Of Package s Option 23 20 Restart Session Option 6 7 Restart Task Manager Option 22 14 Restart TaskMan Option 21 18 RESTART 4ZTMB Direct Mode Utili
604. ve until another surrogate is specified or the user removes the surrogate A message is sent to the surrogate to indicate that he has been designated as a surrogate and a message is sent when the surrogate is removed If the user has no alerts and selects the alert option he will be asked if he wants to add or remove a surrogate The XQALERT SURROGATE SET REMOVE option is also provided It can be used by IRM or ADPAC staff to add or remove a surrogate for a selected user This option is located on the Alert Management menu 10 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Alerts System Management An alert notifies one or more users of a matter requiring immediate attention Thus alerts function as brief notices that are distinct from mail messages or triggered bulletins Starting with Kernel V 8 0 alerts are stored in the ALERT file 8992 stored in XTV 8992 Also the ALERT TRACKING file 8992 1 stored in XTV 8992 1 provides a means to track alerts and users responses to alerts For each user to whom an alert is sent the ALERT TRACKING file 8992 1 stores the following data e Alert name e Date created e Software identifier of alert e User who generated the alert e Message text of the alert e Action associated with the alert e Data associated with the alert For each recipient of the alert the ALERT TRACKING file 8992 1 stores the following data e First date and time observed
605. versing the menu pathways step by step Choosing Options You can choose an option from your current menu at the select prompt Choosing the option launches the computer application associated with the option To choose an option type in the first few letters of the option as it is displayed and press the lt Enter gt key If the option is another menu indicated by trailing ellipses 1t will become the current menu and so on down the menu pathway To come back up the menu pathway press lt Enter gt at the select prompt Each time you press lt Enter gt Menu Manager will return you to the next higher menu level until you reach your highest menu the primary menu If you press lt Enter gt at the primary menu Menu Manager asks if you want to halt If you answer YES your Kernel session will be ended July 1995 Kernel Systems Management Guide 6 1 Revised June 2008 Version 8 0 Menu Manager User Interface Entering One Question Mark to List Options When you enter a menu the items may or may not be displayed automatically based on whether you have AUTO MENU turned on The AUTO MENU feature as described in the Signon Security User Interface chapter in this manual is a flag that controls the menu display If you do not have a setting specified for AUTO MENU the site parameter default will be used Often to save system resources the site parameter can be set to disable automatic display In this case to display your menu s ite
606. vice 19 6 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 20 TaskMan System Management Overview Kernel s TaskMan module provides a standardized system for initiating and managing background processing Since TaskMan handles all background processes system managers have a unified set of controls that apply to all background processes on their systems Most of TaskMan s processing does not involve interaction with users rendering its operation virtually invisible The explanations that follow provide information about the operation of TaskMan TaskMan s Division of Labor TaskMan uses a three step system to start and manage background processing 1 Queuers Foreground jobs cannot directly start any background jobs Instead they call the TaskMan Application Program Interface API to file requests in the TASKS 14 4 and SCHEDULE files The program code calling the TaskMan API is called a Queuer The TASKS file 14 4 is VA FileMan compatible The SCHEDULE file is not VA FileMan compatible REF For a description of the TASKS 14 4 and SCHEDULE file structure please refer to the Troubleshooting topic in the TaskMan System Management Operation chapter in this manual 2 Manager A TaskMan program called the Manager runs at all times in the background The Manager monitors the SCHEDULE file As needed it initiates background jobs called Submanagers to perform the work requested by the foregrou
607. vity What is the purpose of File Access Security Why bother specifying who has access to which files The answer is threefold e To monitor the use of VA FileMan e To regulate the extent of VA FileMan access from among six levels of security that allow AUDIT DATA DICTIONARY DD DELETE DEL LAYGO READ RD or WRITE WR access REF These File Access Security level properties are described in Table 5 1 e To reserve DUZ 0 the FILE MANAGER ACCESS CODE field 3 as a security measure to protect just templates and fields not files from VA FileMan options With file access security it is possible to know who has access to which files and what kind of access they have This information can also be retrieved by user or by file In addition privileges can also be entirely restricted for an individual user or for a single file that may contain sensitive information Who Needs File Access You need to grant File Access Security in the following cases e A user needs to access files directly through VA FileMan options e Within an application option VA FileMan is used to navigate from one file to another e Within an application option that calls the DIE API to edit a file entry a user is unable to add or delete entries in a pointed to file 5 4 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 File Access Security e Within an application option that calls the DIE or DIC APIs to edit
608. w to create a PRINT template to display a report on the current file access security Figure 5 9 Creating a PRINT template to display file access security Sample user dialogue Select OPTION PRINT FILE ENTRIES OUTPUT FROM WHAT FILE FILE Enter the starting and ending SORT BY NAME NUMBER file numbers START WITH NUMBER FIRST 3 GO TO NUMBER LAST 4 WITHIN NUMBER SORT BY lt Enter gt FIRST PRINT ATTRIBUTE NUMBER L8 S FIRST PRINT ATTRIBUTE NAME L25 THEN PRINT ATTRIBUTE DD ACCESS R6 THEN PRINT ATTRIBUTE RD ACCESS R6 THEN PRINT ATTRIBUTE WR ACCESS R6 Store in a local template for THEN PRINT ATTRIBUTE DEL ACCESS R6 later use e g ZZFILE THEN PRINT ATTRIBUTE LAYGO ACCESS R6 SECURITY THEN PRINT ATTRIBUTE AUDIT ACCESS R6 THEN PRINT ATTRIBUTE lt Enter gt HEADING FILE LIST FILE SECURITY STORE PRINT LOGIC IN TEMPLATE ZZFILE SECURITY Once the conversion has been run you can use the File Access Security menu XUFILEACCESS Figure 5 3 to print the accessible files for individual users Thus you can establish profiles that would be typical of groups of users e g Nursing Pharmacy or other services Then when establishing an account for a new user or reactivating the access of a previously terminated user the profile will be available for copying to the new user July 1995 Kernel Systems Management Guide 5 15 Revised June 2008 Version 8 0 File Access Security 5 16 Kernel Systems Management G
609. would then set the XQACNDEL variable to a value of 1 one prior to calling SET XQALERT to set up the alert Deletion of an alert by the user or by IRM or ADPAC staff using the existing option is noted within the ALERT TRACKING file 8992 1 as deletion by a user with the user ID without processing of the alert July 1995 Kernel Systems Management Guide 10 3 Revised June 2008 Version 8 0 Alerts Forwarding Alerts Beginning with Kernel V 8 0 you can forward alerts by using the F alert processing code when viewing alerts You can choose one or more alerts and forward them in the following ways e Forward as alert s to a specific user on the computer system e Forward as alert s to a mail group on the system e Copy alert s into mail message s and send to users and mail groups on the system e Print to an output device on the system e g a printer Surrogates and Alerts Beginning with Kernel Patch XU 8 0 114 you can designate and or remove a surrogate for alerts by using the S alert processing code when viewing alerts The user can if desired specify a start date time and or an end date time for the surrogate to be effective If a start date time is not specified the surrogate becomes active immediately If an end date time is specified the surrogate will be removed automatically effective with the first alert sent to the user after the end date time has passed If an end date time is not specified the surrogate is acti
610. xvii Glossary Home Page Web Address Glossary 6 Health Systems Design and Development Home Page Web Address xxxvi KAAJEE Documentation 2 2 Kernel Home Page Web Address xxxvi RPC Broker Documentation 2 1 VA FileMan Documentation 3 20 5 1 5 5 VHA Software Document Library VDL Home Page Web Address xxxvii VI 2 VI 3 What Can Server Options Do 11 1 What Happened to DIFROM 23 6 What in VA FileMan is Still Protected by the File Manager Access Code 5 4 What is a Server Option 11 1 When is File Access Security Checked 5 3 When the Distribution is Split Across Diskettes KIDS 23 10 When the KIDS Installation is Queued 23 17 Where am I Option 6 7 Which Options to Queue TaskMan 22 18 Who Needs File Access 5 4 Why Longer Passwords 2 4 Working with Tasks 19 2 WRITE Access 3 20 5 1 5 4 5 7 7 2 July 1995 Revised June 2008 Index X XGF Function Library System Management 29 1 System Requirements 29 1 XINDEX Utility 26 2 26 3 Error Codes 26 2 26 4 XMB Global 17 6 XMBS Global 17 6 XMNOPRIV Security Key 8 5 XPD BACKUP Option 23 15 XPD COMPARE TO SYSTEM Option 23 13 XPD CONVERT PACKAGE Option 24 4 XPD DISTRIBUTION MENU 23 2 XPD INSTALL BUILD Option 23 16 XPD INSTALLATION MENU Menu 23 3 23 8 XPD LOAD DISTRIBUTION Option 23 9 23 10 XPD MAIN Menu 23 2 XPD PRINT BUILD Option 24 2 XPD PRINT CHECKSUM Option 23 12 XPD PRINT INSTALL FILE Option 24 3 XPD PRINT INSTALL O
611. y Delegation Levels using the VA FileMan as the organization s structure changes over time Further Delegation The only way a delegate can delegate rather than simply assign options to someone else is if the delegate has access to the Select Options to be Delegated option XQSMD ADD or the Replicate or Replace a Delegate option XQSMD REPLICATE These options should only be on the Secure Menu Delegation menu XQSMD MGR You should carefully evaluate whether to give this menu to delegates which gives them the right to further delegate July 1995 Kernel Systems Management Guide 9 9 Revised June 2008 Version 8 0 Secure Menu Delegation Options Too Sensitive to Delegate Certain options e g Programmer related options are considered too sensitive or powerful to be delegated They are marked as not delegable in the OPTION file 19 and the Secure MenuMan Delegation software will not delegate these options The traditional methods of assigning these menu options must be employed by the Site Manager It should be noted that a higher level option such as EVE would still give the delegate access to lower level options such as XUMAINT even though XUMAINT is itself marked in the OPTION file 19 as non delegable The Delegation software does not follow the option trees down to insure that options of options are not delegable ISO or IRM Chief review the options marked as too sensitive to be delegated and N CAUTION It is highly
612. y connected via modem or other network device you can enter restart to sign out of Kernel without dropping the communication line Finally you can sign off without using any of these shortcuts simply by pressing lt Enter gt at each menu prompt to step back up the menu pathway and finally exit REF For more information on menus and menu prompts please refer to the Menu Management section in this manual Abnormal Signoff and Error Handling If you encounter an error while using the VistA computer system Kernel will trap it issue the message Sorry bout that and attempt to return you to your primary menu Kernel can recover from most error conditions and given a suitable environment will permit you to continue Some error conditions however cause an abnormal exit such that you are immediately logged off the computer system When this happens you can sign on again if you still need to use the computer system Terminal Type Prompt When signing on you may be prompted to enter a terminal type You should not see this prompt very often however since Kernel usually can identify your terminal type without needing to prompt you to enter one If you are prompted you should enter the name of the actual terminal type to use e g C V7T220 The entered terminal type tells Kernel how to support screen oriented and other enhanced displays If unusual circumstances arise and the wrong terminal type is in effect you can redefine it by
613. y deleting the task KIDS also allows you to restart an install if the install 1s queued and you get an error during the installation Re answering Installation Questions If you queued an installation you can re answer installation questions if you so choose using the Install Package s option To be able to re answer the questions however you need to locate the task that was queued for the installation and delete it first Once you delete the installation s queued task you can re answer the install questions When you re answer questions your answers from the previous time come up as default responses Also if you abort an installation after answering its installation questions i e by entering a caret your responses will again be used as the defaults the next time you try to install Information Stored in the INSTALL File 9 7 KIDS exports the definition of a software application in the BUILD file 9 6 KIDS records installations of software in the INSTALL file 9 7 The installation records in the INSTALL file 9 7 provide a record of the start time timing for each checkpoint and completion time if any for an installation When an installation aborts the contents of the INSTALL file 9 7 determine where the install will start up again when you use the Restart Install of Package s option checkpoint information is stored in the INSTALL file 9 7 As well as being sent to the installation s principal devi
614. y marked out of order use the Options in the Option File that are Out of Order option XQOOSHOFIL and the Protocols Marked Out of Order in Protocol File option XQOOSHOPRO Restricting Option Usage Figure 7 13 Restrict Availability of Options option Menu Management XUMAINT Restrict Availability of Options XORESTRICT Options can be restricted in terms of when users can select them and when devices can be used to invoke them Many of the option restrictions are included in the Restrict Availability of Options option XQRESTRICT OUT OF ORDER MESSAGE To completely restrict access you can mark an option to be out of order Do this by entering text in an option s OUT OF ORDER MESSAGE field If a user attempts to invoke the option the Out of Order Message will be displayed Locks Both the normal lock and also the Reverse Negative lock can be associated with options as described in the Security Keys chapter Also M code can be entered in the HEADER ENTRY ACTION or EXIT ACTION fields to restrict the use of an option given certain conditions Prohibited Times You can prohibit the use of an option at certain times during the day by assigning a set of prohibited time periods at the Select TIMES PROHIBITED prompt Permitted Devices If the RESTRICT DEVICES flag is set to YES the option can only be invoked on one of the devices listed in the PERMITTED DEVICES field Multiple Thus the running of an option
615. you have selected each executable option to be part of the template enter a plus sign to store the sequence of options You will be asked to confirm the sequence of options in the template and then to give the template a name 6 8 Kernel Systems Management Guide July 1995 Version 8 0 Revised June 2008 Menu Manager User Interface To invoke the template simply enter a left square bracket followed by the template name Figure 6 10 Invoking a template Sample user dialogue Select Option mytemplate Loading MYTEMPLATE The template will then execute each option that is part of the template in the same order as the options were selected for the template MENU templates are stored in the MENU TEMPLATE field Multiple of the NEW PERSON file 200 so you can use any name for MENU templates If your MENU template points to options that are subsequently removed from the OPTION file 19 you receive a message that the MENU template will no longer function properly and needs to be deleted and or rebuilt Use menu jumping 1 e the Up arrow Jump when you want to jump immediately to an option Use MENU templates when you have a series of options that you will need run in the same order repeatedly over a period of time LOGIN Menu Template Beginning with Kernel V 8 0 you can have a MENU template execute automatically on your first signon of the day If you have a MENU template named LOGIN all uppercase the MENU te

KERNEL SYSTEMS MANAGEMENT GUIDE Version 8.0

Contents

Download Pdf Manuals

Related Search

Related Contents