Toolkit 7.3 03/01/2018 7.3 Tech Edits: Updated Section 2, “Signon/Security: User Interface” and Section 3.4.2, “Automatically Deactivating Users,” with regard to “smart card (aka PIV card) signons. Updated Section 2.1.1, “Defining a Strong Verify Code,” to include references to other section regarding Verify code expiration and option to reset. Updated Section 3.1, “Signon Process.” Updated Figure 31 and added Table 6 in Section 3.5.4, “Print Sign-on Log Option,” based on updates made with Kernel Patch XU*8.0*630. Updated Section 1; Kernel (and soon all of VistA) is no longer vendor-independent. Much of the new work being done in Kernel and other namespaces relies on Cache ObjectScript. Added the “Parameter Tools” section taking content from the Parameter Tools Supplement to Patch Description: Patch XT*7.3*26 document (ktk7_3p26sp.pdf). Updated Sections 1.1, 2, 2.1, 2.1.1, 3.1.2.16, and 3.5.8 to add or clarify references to 2-Factor Authentication (2FA) vs. use of the Access and Verify codes. Updated styles and formatting throughout. Updated all TOCs, lists, etc. Software Versions: Kernel 8.0 Toolkit 7.3 Developer: J.G. Technical Writer: T.B. 08/10/2016 7.2 Tech Edits: Updated Section 15.1.3.2 and Developer: H.W. Technical Writer: T.B.
(#3.5) file. Sites had to remove any HUNT GROUP devices before installing this patch using VA FileMan to find any existing Hunt Groups. “Hunt Groups” section was deleted from this manual. Also, any references to “Hunt Groups” were removed. Added blue font highlighting and underline to signify internal links to figures, tables, or sections for ease of use, similar to what one sees to hyperlinks on a Web page. Updated document for Section 508 conformance using word’s built-in Accessibility check: Added table bookmarks. Added screen tips for all URL links. Changed all floating callout boxes to in-line, causing reformatting of numerous dialogue screen captures. Software Versions: Kernel 8.0 Toolkit 7.3 06/06/2012 6.0 Updates: Added the “XU USER START-UP Option” section. The XU USER START-UP option was added with Kernel patch XU*8.0*593. Added Section 15.6.4 “Verify HFS and NULL Device Setup (required),” in the “Troubleshooting” section in “Device Handler: System Management.” Updated all VA organizational references. Revised all version numbers in the “Revision History” section. Updated the “” section. Updated the overall document for current national documentation standards and style guides. For Office of Information Field Office (OIFO): Maintenance Development Manager—J. Sch. Developers—G.B., R.D., J.I., R.Men., R.Met., B.T., and H.W. Technical Writer—T.B.
example: Changed all Heading n styles to use Arial font. Changed all Heading n styles to be left justified. Software Versions: Kernel 8.0 Toolkit 7.3 03/22/2010 5.3 Updates: Added Section 24.3, “Edit Install Status Option released with Kernel patch XU*8.0*539. Added Figure 244 Edit Install Status option—Sample user dialogue. Software Versions: Kernel 8.0 Toolkit 7.3 Office of Information Field Office (OIFO): Maintenance Development Manager—J.Sch. Developers—G.B., A.C., R.D., W.F., J.G., J I., R.Men., R.Met., and B.T. Technical and S.S. 11/16/2009 5.2 Updates: Updated references to the CHCKSUM^XTSUMBLD direct mode utility throughout. Updated organizational references. Minor format updates (e.g., reordered document revision history table to display latest to earliest, added outline numbering). Other minor format updates to correspond with the latest standards and style guides. Updated the “Automatically Deactivating Users” section in “Signon/Security: System Management” for Kernel patch XU*8.0*514. Re-ordered and edited all topics in the “Device Handler: System Management” section. Also, added updates to the Device handler based on Kernel patch XU*8.0*440. Moved the following section content from the Kernel 8.0 & Kernel Toolkit OIFO: Maintenance Development Manager—J.Sch. Developers—G. B., A.C., R.D., W.F., J.G., J.I., R.Men., R.Met., and B.T. Technical and S.S.
you. Kernel’s menu system is what is used to make VistA applications (e.g., Scheduling, Nursing, and Personnel) available to users. 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 8.0 & Kernel Toolkit 7.3 Systems Management Guide and concentrate on the user interface chapters and particularly issues concerning every Kernel user (e.g., signon process and menu navigation). System Managers 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: Alerts provide an integrated notification system. Device Handler provides a common device interface. Electronic Signature Codes provide a secure electronic approval system. File Access Security system manages access to VA FileMan files. Kernel Installation and Distribution System (KIDS) provides an application distribution and installation system. Menu Manager provides a common menu management system. Signon/Security organizes users and allows secure logons. TaskMan provides a common job queuing system.
As of Kernel patch XU*8.0*180, strong Access and Verify codes must adhere to the following criteria: Access and Verify codes cannot be identical. Verify codes (i.e., passwords) must be at least 8 characters in length. A minimum of 15 characters is recommended, and may be enforced at a later date. Strong passwords 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., -, _, #, &, $, *, @) NOTE: The caret (^) is a reserved symbol and cannot be used as part of a Verify code. Also, some non-VistA-based systems restrict certain special characters/symbols used as part of a username or password. Because VistA is case-insensitive, VistA only has three sets of characters from which to build a strong Verify code (i.e., password): Letters (of any case) Numbers Special characters/symbols that are neither letters nor numbers (e.g., -, _, #, &, $, *, @) NOTE: Some non-VistA-based systems restrict certain special characters/symbols used as part of a username 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 the system administrators. Information systems shall not permit re-assignment of the last three passwords used. When required, you are prompted during signon to pick a new Verify code. REF: For more information on Verify code expiration dates, see Section 3.1.2.9, LIFETIME OF VERIFY CODE.” Accounts that have been inactive for 90 days shall be disabled. 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 shall be required to clear a locked account. Where around-the-clock system administration service is not available, accounts shall remain locked out for at least ten minutes. NOTE: These rules are taken from the VA Account and Password Management Interim Policy document.
Possible categorizations for whether accounts are reported as “Compliant w/3-year Service Account Mandate?” are: YES (account is compliant). *** NO <---- MUST FIX *** (date created and date verify code last changed > 3 years in the past). No, but user not active. UNABLE TO DETERMINE (until patch XU*8.0*574, date verify code last changed for Connector Proxy accounts was incorrectly recorded as 4/10/2005) Unable to determine but not active. If an account’s Date Verify Code Last Changed is listed as “(changed but date not recorded)”, that means the “fake” 4/10/2005” date is present, and unless the account was created within the last 3 years, it is impossible to determine if the account is in compliance with the 3-year mandate. Also, if there is a value in the XUS LOGON ATTEMPT COUNT field, that value is displayed, as it could indicate a remote system attempting to connect and failing with an invalid Verify code. If the option to “Check/display connector proxy fields?” is selected, the following checks are performed: Warnings: (any field listed in the warning section should not be populated. However, before changing, consult the National Help Desk or Customer Support as some applications may (currently) be depending (incorrectly) on a misconfigured connector configuration.) Values for other fields allowed/expected: (field normally populated for connector proxies). Other Fields Populated (not expected fields, but not problematic either). Other Multiples Populated (not expected, but not problematic either). If the option to “Scan sign-on log for connector proxy activity?” is selected, the report scans the sign-on log for all signon activity associated with the account. Any activity found is displayed, organized by client IP address, and within IP address, by date of signon. The purpose of this report section is to help sites determine which accounts are active, and which external systems (by IP address) are logging onto the site with the specified account. This helps determine which remote applications a change to the account (e.g., Verify code change) might impact, and also helps a site determine whether too many remote applications/data centers are using the same account (which could result in a more widespread service disruption if an account must be changed). NOTE: This option can be scheduled.
To enable restrictions, authorized site personnel must set the XU SIG BLOCK DISABLE general parameter to a value of ON (1). The parameter definition is stored in the PARAMETER DEFINITION (#8989.51) file, and the parameter data is stored in the PARAMETER (#8989.5) file: If the XU SIG BLOCK DISABLE parameter is set to ON and the user has the XUSIG security key assigned in the NEW PERSON (#200) file, then access to the restricted fields is allowed. If the XU SIG BLOCK DISABLE parameter is set to ON, but the user does not have the XUSIG security key assigned, then access to the restricted fields is not allowed. If the site leaves the XU SIG BLOCK DISABLE parameter set to OFF (0), then access to all electronic signature fields is allowed. To set the XU SIG BLOCK DISABLE parameter to ON: Log into VistA with programmer access. At the “Select OPTION NAME:” prompt, enter XPAR MENU TOOLS. At the “Select General Parameter Tools Option:” prompt, enter EP. At the “Select PARAMETER DEFINITION NAME:” prompt, enter XU SIG BLOCK DISABLE. At the “Sig Block Disable:” prompt, enter YES. System Management Figure : User Edit Menu Options SYSTEMS MANAGER MENU ... [EVE] User Edit ... [XUSER] Electronic Signature Block Edit [XUSESIG BLOCK] Clear Electronic signature code <locked: XUMGR> [XUSESIG CLEAR] Electronic Signature Block Edit Option The Electronic Signature Block Edit [XUSESIG BLOCK] option 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 in the NEW PERSON (#200) file is initially filled in by a cross-reference on the NAME (#.01) field (and is overwritten if the NAME [#.01] field 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 (#.01) field) be included in the printed name. (This field cannot be edited through VA FileMan, since it is WRITE-protected with a caret [^].)
General Parameter Tools Menu Use the General Tools [XPAR MENU TOOLS] menu, located under the CPRS Configuration (IRM) [OR PARAM IRM MENU] menu, to update the XUEPCS REPORT DEVICE parameter. To edit the DEA ePCS Utility parameter, perform the following procedure: From the CPRS Manager Menu [ORMGR], select the IR—CPRS Configuration (IRM) [OR PARAM IRM MENU] option. At the “Select CPRS Configuration (IRM) Option:” prompt, select the XX—General Tools [XPAR MENU TOOLS]option. At the “Select General Tools Option:” prompt, select the EP—Edit Values [XPAR EDIT PARAMETER] option. At the “Select PARAMETER DEFINITION NAME:” prompt, enter XUEPCS REPORT DEVICE. At the “Select device for ePCS reports: XXXXXXXX//” prompt, enter the printer device appropriate for your system.
Figure : DEA ePCS: XPAREDIT Routine—Editing DEA ePCS Site Parameter: Test Account >D ^XPAREDIT --- Edit Parameter Values --- Select PARAMETER DEFINITION NAME: XUEPCS REPORT DEVICE <Enter> ePCS Device Definition for Reports ---- Setting XUEPCS REPORT DEVICE for System: ABC.FO-SITE.MED.VA.GOV ---- Select device for ePCS reports: SDD DUPLEX P10 <Enter> SDD DUPLEX PRINTER next to One, Xuuser USER$:[TEMP]SDD_DN2$PRT.TXT ------------------------------------------------------------------------------ Select PARAMETER DEFINITION NAME: Add DEA ePCS Utility Users There are three steps to give a user access to the DEA ePCS Utility: Assign the XUEPCSEDIT Security Key. Assign the XU EPCS EDIT DATA Option. Assign the XUSSPKI UPN SET Option. Assign the XUEPCSEDIT Security Key To assign the XUEPCSEDIT security key, perform the following procedure: From the Systems Manager Menu [EVE], select the Menu Management [XUMAINT] menu. At the “Select Menu Management Option:” prompt, select the Key Management [XUKEYMGMT] menu. At the “Select Key Management Option:” prompt, select the Allocation of Security Keys [XUKEYALL] option. At the “Allocate key:” prompt, enter XUEPCSEDIT security key. At the “Another key:” prompt, press Enter to complete your entries. At the “Holder of key:” prompt, enter the user’s name. At the “Another holder:” prompt, enter any additional user names that need access to the DEA ePCS Utility. When complete, press Enter. At the “You are allocating keys. Do you wish to proceed? YES//” prompt, press Enter to accept the YES default response.
Figure : DEA ePCS: Assigning the XU EPCS EDIT DATA Option—Sample User Entries (1 of 2) Select Systems Manager Menu Option: USER <Enter> 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 OAA Trainee Registration Menu ... Electronic Signature Block Edit Manage User File ... Person Class Edit Reprint Access agreement letter Select User Management Option: EDIT <Enter> an Existing User Select NEW PERSON NAME: XUUSER <Enter> XUUSER,ONE OX TECHNICAL WRITER Edit an Existing User NAME: XUUSER,ONE Page 1 of 5 ____________________________________________________________________________ NAME... XUUSER,ONE INITIAL: OX TITLE: TECHNICAL WRITER NICK NAME: ONE SSN: 000123456 DOB: DEGREE: MAIL CODE: DISUSER: TERMINATION DATE: Termination Reason: PRIMARY MENU OPTION: EVE Select SECONDARY MENU OPTIONS: XU EPCS EDIT DATA Want to edit ACCESS CODE (Y/N): FILE MANAGER ACCESS CODE: @ Want to edit VERIFY CODE (Y/N): Select DIVISION: SAN FRANCISCO SERVICE/SECTION: OIFO Field Office ____________________________________________________________________________ COMMAND: Press <PF1>H for help Insert
DEA EXPIRATION DATE XU EPCS DISUSER XDATE EXPIRES (See Section 6.4.5.) Print DISUSER DEA Expiration Date Expires 30 days This option prints all DISUSERed users with DEA # and where the DEA EXPIRATION DATE expires within 30 days. This option prints the following data: NAME DEA# DEA EXPIRATION DATE XU EPCS PRIVS (See Section 6.4.6.) Print Prescribers with Privileges This option prints all active users who have privileges to any of the SCHEDULEs II through V and who have a DEA# or VA#. This option prints the following data: NAME DUZ DEA# VA# SCHEDULESs XU EPCS DISUSER PRIVS (See Section 6.4.7.) Print DISUSER Prescribers with Privileges This option prints all DISUSERed users who have privileges to any of the SCHEDULEs II through V and who have a DEA# or VA#. This option prints the following data: NAME DUZ DEA# TERMINATION DATE VA# SCHEDULESs XU EPCS PSDRPH (See Section 6.4.8.) Print PSDRPH Key Holders This option prints all active users holding the PSDRPH security key. This report sorts by Division, and within DIVISION, it sorts by NAME. This option prints the following data: NAME DUZ GIVEN BY (Person Who Assigned Key) DATE GIVEN (Date Assigned)
To schedule the option to run daily using TaskMan, perform the following procedure: From the Systems Manager Menu [EVE], select the Taskman Management [XUTM MGR] option. At the “Select Taskman Management Option:” prompt, select the Schedule/Unschedule Options [XUTM SCHEDULE] option. At the “Select OPTION to schedule or reschedule:” prompt, enter XU EPCS LOGICAL ACCESS. At the “...OK? Yes//” prompt, enter YES. A ScreenMan dialogue is displayed. Tab down to the following fields and enter the values shown: QUEUED TO RUN AT WHAT TIME: T+1@001 (which means start running it tomorrow at 12:01) RESCHEDULING FREQUENCY: 1D (which means run it daily) At the “COMMAND:” prompt, enter Save. At the “COMMAND:” prompt, enter Exit.
Displaying Option Descriptions Entering three question marks (???) at any select prompt displays option descriptions (from a word-processing-type field in the OPTION [#19] file). 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 : 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 document. ‘Delete A Spool Document’ Option name: XU-SPL-DELETE **> 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 **> 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-MAIL **> 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. **> Press ‘RETURN’ to continue, ‘^’ to stop, or ‘?[option text]’ for more help: <Enter> ‘Print A Spool Document’ Option name: XU-SPL-PRINT **> 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// <Enter> Would you like to see the Common Options? No// <Enter> 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).
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 following: Job Number Username IO value Date/Time UCI/Volume Set Error Type Last Global Reference 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 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 : Local Symbol Table Help Which symbol? > ? Enter: ^Q to EXIT ‘^’ to return to the last question Leading character(s) of symbol(s) you wish to examine $ to get a display of the $ system variables ^L to obtain a list of 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 error log. Figure : 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 [XUERTRP PRINT ERRS] option provides for an interactive print of the first “n” of occurrences of an error (where “n” is user selectable) over a specified date range.
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: All UCIs a submanager can access directly after using Kernel’s UCI switching facilities. All other managers TASKS (#14.4) and SCHEDULE files to which a given manager can WRITE using extended global reference. 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 can only run tasks in the UCIs it can reach. TASKMAN SITE PARAMETERS (#14.7) File Figure : 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 (#14.7) file 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.
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 rejects 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 : TaskMan Rejection Messages TaskMan Rejection Message Description BAD DESTINATION UCI The Manager rejects a task for this reason under three different conditions: 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 ^%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 (#14.6) file 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 determine 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 (#14.5) file. BAD IO DEVICE <$I> 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, 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.
Kernel Installation and Distribution System KIDS: System Management—Installations Kernel Installation and Distribution System (KIDS) was introduced with Kernel 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; it introduces significant revisions to the software distribution and installation processes. This chapter introduces KIDS, and describes some of the changes to the software export process. Table 51 lists the definitions that apply throughout the KIDS documentation: Table : KIDS-related Terms and Definitions Term Definition 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 (#9.4) file entry (if any) for a given software application. Build Entry An entry in the BUILD (#9.6) file 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 globals. 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).
KIDS: System Management—Utilities KIDS provides the following Utilities [XPD UTILITY] menu options shown in Figure 296: Figure : 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] Edit Install Status [XPD EDIT INSTALL] 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.
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 VA FileMan Edit File [DIEDFILE] option. REF: For more information on the Edit File [DIEDFILE] option, see the “File Utilities” section in the VA FileMan Advanced User Manual. Figure : VA FileMan Edit File Option—Sample User Entries VAH,MTL>D Q^DI VA FileMan 20.0 Select OPTION: UT <Enter> ILITY FUNCTIONS Select UTILITY OPTION: ED <Enter> IT FILE MODIFY WHAT FILE: ICD DIAGNOSIS// <Enter> NAME: ICD DIAGNOSIS// <Enter> DESCRIPTION: <Enter> 1>Contains all valid ICD diagnosis codes. EDIT Option: <Enter> Select APPLICATION GROUP: <Enter> PROGRAMMER: <Enter> VERSION: 9// <Enter> DATA DICTIONARY ACCESS: <Enter> READ ACCESS: <Enter> WRITE ACCESS: <Enter> DELETE ACCESS: <Enter> LAYGO ACCESS: <Enter> AUDIT ACCESS: <Enter> DD AUDIT? NO// <Enter> ASK ‘OK’ WHEN LOOKING UP AN ENTRY? YES// <Enter> (YES) POST-SELECTION ACTION: <Enter> LOOK-UP PROGRAM: XTLKDICL CROSS-REFERENCE ROUTINE: <Enter> Select UTILITY OPTION: <Enter> 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 (#8984.4) file, 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 8.0 & Kernel Toolkit 7.3 Developer’s Guide. Kernel and Kernel Toolkit APIs are also available in HTML format at a VA Intranet Website.
Missing, 379 Routine, 378 Software, 281, 350, 377, 379 Transport Global, 353 Compute Server Job List, 282, 318, 342 Node, 334 Mode, 291 COMPUTE SERVER Type, 293 Computer Access Policy, 29 Computer Account Notification, 29 Configuration DEA ePCS Utility, 89 Multiple Managers TaskMan, 299 TaskMan, 287 Caché and GT.M, 298 CONNECTOR PROXY, 51, 54, 55, 56 Contents, xvi Continue Option, 138 Control How Can the Number of Instances of a Server Option Be Controlled?, 197 Conversion After File Access Security, 78 File Access Security, 73 Convert Loaded Package for Redistribution Option, 351, 372, 373 COORDINATOR (IRM) Field, 37 Copy Everything About an Option to a New Option Option, 171, 178 Copy One Users Menus and Keys to others Option, 171 Copy Print Mode, 267 CPRS Configuration (IRM) Menu, 89 CPRS Manager Menu, 89 CPT (#81) File, 385 CPU Cross-references, 225, 287 Definition, 284 CPU/Service/User/Device Stats Option, 41, 57 Create a Set of Options to Mark Option, 150 Creating Another Level of Delegation, 168 Delegates, 173 Device Types, 229 Distributions, 348 Help Frames, 209 Menus and Options, 141 New User Account, 28 Options and Menus, 141 Resource Devices, 266 Security Keys, 165 Several Dummy Users, 29 Spooled Document, 252 Tasks, 265 TaskMan User Interface, 271 Terminal Types, 237 Transport Globals, 379 Critical Alerts, 179 Critical Alerts Count Report Option, 181, 188, 189 Cross Reference Help Frames Option, 208 Cross-references ^XUSEC, 166 AK, 165 AOLD, 59 B, 339 CPU, 225, 287 CUR, 51 Devices, 242, 243 Errors, 333 Lookup-type, 38 Options, 208 Parents, 208 Routines, 208 VOLD, 59 CUR Cross-reference, 51 D DA Return Code Edit Option, 23, 239 DA RETURN CODES (#3.22) File, 23, 239 Global Location, 224 DA RETURN CODES File(#3.22), 224 Dangling Pointers OPTION (#19) File, 149 Data Dictionaries Being Audited Option, 64 Data Dictionary Data Dictionary Utilities Menu, l Listings, l
Spool Document Formats, 221 Subtypes, 220 Summary, 223 System Management, 224 Terminal Type Information Retained by User, 238 Test Pattern, 240 Troubleshooting, 240 User Interface, 217 Virtual Terminals, 238 Device Lock-out Times, 19 Device Management Menu, 229, 240 Device Waiting List Node, 335 Devices BROWSER, 233, 258, 260 Cross-references, 242, 243 Editing, 242 File Entries, 268 HFS, 226, 230, 237, 244, 245, 267, 301, 347, 351, 352, 354, 355 Home, 217, 219, 238, 268, 269, 270 Identification, 242 IO List, 318 Magtape, 263 Network Channel, 264 NULL, 232 P-MESSAGE, 233 Printing, 217 RESOURCES Type, 197 SDP, 267 Security, 236 Selection at Signon, 238 Sequential Disk Processor (SDP), 237, 267 Signon, 238 Slaved, 267 Special Devices, 258 SPOOLER, 247 Synonyms, 242 TELNET, 233 VMS Systems Virtual Devices, 239 DI DDMAP Option, 64 DI DDU Menu, l, 64 Diagram Menus Option, 163, 167 Diagramming Options, 145 DIALOG (#.84) File, 69 DIAUDIT DD Option, 64 DIAUDIT PURGE DATA Option, 64 DIAUDIT PURGE DD Option, 64 DIAUDIT TURN ON/OFF Option, 64 DIAUDITED FIELDS Option, 64 DIC API, 63 DIC Routine, 62 DIDEL Variable, 62, 63 DIE API, 63 DIE Routine, 62 DIEDFILE Option, 74, 407 DIEDIT Option, 62, 65, 66 DIFROM Utility, 347, 350, 352 Digital Certificate Smart Card, 4 DIGITAL PAGER (#.138) Field, 13, 43, 80 DIINQUIRE Option, 65, 67, 386 DILIST Option, l, 65 DIMODIFY Option, 64, 67 DIP Routine, 161 DIPRINT Option, 65 Direct Mode Utilities Error Processing ^XTER, 215 ^XTERPUR, 214 TaskMan ^ZTMON, 319 RESTART^ZTMB, 306 DISABLE USER Field, 47 Disclaimers Documentation, xlvii Software, xlvi DISEARCH, 65 Disk Space Concerns, 208 Display Attributes, 22 Return Codes, 23 Delegated Options, 178 Help Frames, 205 Nodes, 155, 157 Options, 146 Description, 136 Help, 133 Order, 143
Switch UCI Option, 16 Switching UCIs, 152, 288 Symbols Found in the Documentation, xlvii SYNC FLAG Field, 324 SYNC flag file control Option, 324 SYNC FLAGs, 266, 324 Synonym Options, 134 Synonym Option Multi-Term Look-Up (MTLU) Example, 404 Synonyms Devices, 242 Multi-Term Look-Up (MTLU), 385, 397 Associated with Multiple Terms, 387 Multiple Tokens, 387 Options, 132, 134, 137, 143, 159, 206 Synonyms Option Multi-Term Look-Up (MTLU), 386, 402 System Administrator Setup to Enable Building Options from Templates, 172 SYSTEM COMMAND OPTIONS Menu, 6, 39, 134, 135, 137, 138, 139, 147, 148, 162, 167, 179, 249, 253, 272 System Configuration TaskMan Terminology, 284 System Management Alerts, 185 Browser Device, 260 Device Handler, 224 Electronic Signatures, 81 Error Processing, 211 File Access Security, 61 Form Feeds, 262 Help Processor, 207 Host Files, 245 KIDS Installations, 347 Utilities, 369 Magtape Devices, 263 Managing Delegates, 173 Menu Manager, 141 Network Channel Devices, 264 Resources, 265 Secure Menu Delegation, 173 Security Keys, 163 Server Options, 196 Signon/Security, 18 Slaved Printers, 267 TaskMan Configuration, 286 Operation, 310 Overview, 277 System Manager Introduction, 2 System Parameters, 18 Systems Management Multi-Term Look-Up (MTLU), 404 Systems Manager Menu, 57, 91, 93, 96, 118, 121, 177, 211, 348 T Table of Contents, xvi Task Allocation Audit of PSDRPH Key Report Option, 102, 121, 124 Task Changes to DEA Prescribing Privileges Report Option, 102, 117 Task File Cleanup, 324 Task List, 282, 318 Node, 337 TASK PARAMETERS (#15) Field, 326, 329 TASK PARAMETERS Field, 59, 186, 215 TASK PARTITION SIZE (#4) Field, 289 Task Rejection Messages TaskMan, 343 Task Status Codes TaskMan, 340 TaskMan, 271 ^%ZTSCH Global, 281 ^%ZTSK Global, 281 API, 277 Check Taskman’s Environment Option, 320 Clean Task File Option, 324 Cleanup Task List Option, 314 Configuration, 287 DEVICE (#3.5) File, 301 Multiple Managers, 299 Standardized VA Caché and GT.M, 298
DCL Context, 303 Cache/VMS, 303 OpenVMS User TASKMAN on ALPHA AXP Systems, 309 Restarting, 306 ZTMS2WDCL.COM, 308 ZTMWDCL.COM, 306 Defining Environments, 286 Delete Tasks Option, 314 Dequeue Tasks Option, 313 DESCRIPTION Field, 329 DEVICE FOR QUEUED JOB OUTPUT (#3) Field, 326, 327, 328 Division of Labor, 277 Error Screens, 282 Files, 281 Header Page, 301 Inspecting the Tasks in the Monitor’s Lists, 319 IO List, 318 Job Limit, 290 Job List, 318 List Tasks Option, 310 Load Balancing, 299 Manager, 277, 278 Startup, 299 Monitor Action Prompt, 319 Multiple Managers and Load Balancing, 299 OpenVMS TASKMAN Queue, 309 Option Scheduling, 325 List Background Options, 326 One-time Option Queue Option, 331 PARENT OF QUEUABLE OPTIONS Menu, 325 Problems, 331 Queuing an option, 327 Schedule/Unschedule Options Option, 326 Through the OPTION SCHEDULING (#19.2) File, 278 Which Options to Queue, 325 Other Files, 283 QUEUED TO RUN AT WHAT TIM E (#2) Field, 331 QUEUED TO RUN AT WHAT TIME (#2) Field, 326, 327, 328 QUEUED TO RUN VOLUME SET (#5) Field, 326, 328, 329 Queuers, 277 Queuing an Option, 327 Queuing Output, 271 Rejection Messages, 343 Remove Taskman from WAIT State Option, 323 Requeue Tasks Option, 313 RESCHEDULE FREQUENCY (#6) Field, 326, 328 RESCHEDULING FREQUENCY (#6) Field, 329, 331 Restart Task Manager Option, 322 Restarting DCL Context, 306 SCHEDULE File, 282 ^%ZTSCH Global, 334 Schedule List, 317 Select another task Option, 275 Sequences of Tasks, 266 SPECIAL QUEUEING (#9) Field, 326 Starting Up, Pausing, and Stopping Multiple Managers, 299 Startup, 299 States BALANCE, 300, 301, 344 ERROR, 344 Messages, 344 PAUSE, 294, 345 RUN, 345 WAIT, 299, 322, 323, 346 Status Codes, 340 Stop Task Manager Option, 323 Stopping, 323 Tasks, 274 Submanagers, 277, 279 SYNC flag file control Option, 324 SYNC FLAGs, 266 System Management Configuration, 286 Operation, 310 Overview, 277 Task List, 318