COMMAND UTILITIES Release Level 12.1.2 This application consists of one runfile: CmdUtilities.Run with three command cases; 00, CC, and UC Product Name : Command Utilities Supported On : B24, B26, B27, B28, B38, B39, and all SuperGen hardware Supported OS : BTOS II, CTOS I, CTOS II, CTOS III Description : Command Utilities consists of three applications: /Compare /Commands, /List Commands, Update Command File. /Compare Commands is used to compare all or selected commands in two command files. /List Commands is used to list all or selected commands in a command file. /Update Command Files is used to make updates to currently existing commands. Directions/Use : The /Compare Commands application compares all or selected commands in two command files. The full command is printed if either a command is different or it does not exist in one of the command files. For commands which are different, the command name and the different parameters are preceded with '<>'. Commands or parameters missing in the compare command file, are preceded with '--' and if they are missing in the reference command file, they are preceded with '++'. Note that when comparing command descriptions, ending spaces are ignored (i.e. 'Quick list of files' and 'Quick list of files' are considered identical). This is not so for /UPDATE COMMAND FILE. /Compare Commands may be executed using the following mandatory and optional parameter fields: Compare command file This field is mandatory. Enter the name of the command file to be compared with the reference command file. [Reference command file] This field is optional. The default is the current command file. Enter the name of the command file to be used as a reference. [Command name(s)]: This field is optional. The default is all commands. If you only want to compare specific commands, enter the command names. If a command specification is abreviated or contains wildcards, all commands that match the command specification will be compared. The examples below show whether the command specification causes the 'SET TIME' command to be compared or not: Command specification Result s compared s t compared Set compared settime not compared Set Ti?e compared Set Ti? not compared time not compared *time compared [Print command names only?]: This field is optional. The default is 'No'. If you enter 'Yes', only the names of the commands that are different, are printed. [Print file]: This field is optional. The default is [Vid]. If you want the command output written to a log file, enter a file specification. If the file does not exist, it is created. [Check caps?] This field is optional. The default is 'No'. If you enter 'Yes', upper/lower case differences are not ignored when comparing two commands. If you enter 'No' or leave the field blank, upper/lower case differences are ignored. [Ignore additional commands?] This field is optional. The default is 'No'. If you enter 'Yes', commands which appear in the compare command file but not in the reference command file are ignored. [Ignore missing commands?] This field is optional. The default is 'No'. If you enter 'Yes', commands which appear in the reference command file but not in the compare command file are ignored. [Ignore '!'?]: This field is optional. The default is 'No'. If you enter 'Yes', '!' run file differences are ignored (i.e. [!sys]Exec.run and [Sys]Exec.run are considered to be the same). The /List Commands application lists all or selected commands in a command file. There are three modes: not detailed, semi-detailed and detailed. /List Commands may be executed using the following mandatory and optional parameter fields: [Command file]: This field is optional. The default is the current command file. Enter the name of the command file of which you want to list the commands. [Public command file?]: This field is optional. The default is 'No'. If you enter 'Yes', the commands in the public command file '[!sys]Cluster.cmds' are listed. Note that if you enter 'Yes', any entry that you may have made in the '[Command file]' field is ignored. [Command name(s)]: This field is optional. The default is all commands. If you only want to list specific commands, enter the command names. If a command specification is abreviated or contains wildcards, all commands that match the command specification will be listed. The examples below show whether the command specification causes the 'SET TIME' command to be listed or not: Command specification Result s listed s t listed Set listed settime not listed Set Ti?e listed Set Ti? not listed time not listed *time listed [Details?]: This field is optional. The default will print command name, description, run file and case value. If you enter 'No', only the command name is printed. If you leave the field blank, the command name, description, run file and case value are printed. If you enter 'Yes', the command parameters are also printed. [Print file] This field is optional. The default is to display only to [Vid]. If you want the command output written to a log file, enter a file specification. If the file does not exist, it is created. [Single column?] This field is optional. The default is to display/print to two columns. If you want the commands listed in only one column, enter a 'Yes'. This also suppresses the program header being written to the print file. The /Update Command File application compares all commands in an old command file with the same commands in a reference command file. For all commands that are different, the old command file is updated with the commands found in the reference command file. The difference between MERGE COMMAND FILES (Standard Software) and /UPDATE COMMAND FILE is that /Update Command File only updates existing commands. No commands are added to the old command file. /Update Command File may be executed using the following mandatory and optional parameter fields: Old Command file: This field is optional. Enter the name of the command file to be updated. [Reference command file]: This field is optional. The default is the current command file. Enter the name of the command file to be used as a reference command file. [Print file] This field is optional. The default is to [Vid] only. If you want the command output written to a log file, enter a file specification. If the file does not exist, it is created. [Show differences?] This field is optional. The default is 'No'. If you enter 'Yes', the command differences are shown before updating the old command file. [Confirm each?] This field is optional. The default is 'No'. If you enter 'Yes', you are prompted to press to confirm or to deny the update operation for each command that is different, or to terminate the command. If you enter 'No' or leave this field blank, all different commands are updated without user interaction. [Check caps?] This field is optional. The default is 'No'. If you enter 'Yes', upper/lower case differences are not ignored when comparing two commands. If you enter 'No' or leave the field blank, upper/lower case differences are ignored. [Ignore '!'?] This field is optional. If you enter 'Yes', '!' run file differences are ignored (i.e. [!sys]Exec.run and [Sys]Exec.run are considered to be the same). [Public commands?] This field is optional. This option allows you to update the PUBLIC command file [!sys]Cluster.cmds from a private command file, or vice-versa. If you leave the field blank, the run file specification in the updated commands will be the same as in the reference command file. If you enter 'No', the '!' will be suppressed in the run file specification of the updated commands. If you enter 'Yes', the '!' will be forced in the run file specification of the updated commands. ADDITIONAL INFO If the print file is a GPS device, video escape sequences are translated into GPS escape sequences (e.g. half-bright is printed as bold-italic). For non-GPS print files, they are suppressed. There is however one exception: if the print file is a disk file whose name ends with '.Vid', the video escape sequences are written to the print file. If you TYPE such a print file, the display is exactly the same as during the execution of the CmdUtilities command. If, when comparing two commands, the only difference is a difference in ending spaces for the command description (i.e. the two descriptions are the same except that one ends with a space and the other not) the difference is ignored and the commands are considered to be the same. /UPDATE COMMAND FILE, however, does not ignore this difference and updates the old command file. This is not a bug. If the [sys]KrivaboSoftMsg.bin file does exist, it is used instead of the English linked-in messages. COMMANDS /Compare Commands Compare command file [Reference command file] [Command name(s)] [Print command names only?] [Print file] [Check caps?] [Ignore additional commands?] [Ignore missing commands?] [Ignore '!'?] /List Commands [Command file] [Public command file?] [Command name(s)] [Details?] [Print file] [Single column?] /Update Command File Old command file [Reference command file] [Print file] [Show differences?] [Confirm each?] [Check caps?] [Ignore '!'?] [Public commands?]