IMD 1.18: 15/11/2012 22:02:59 wicat systems mcs 4.0 s150ws 162-290-127 a vol 4 of 4  field, then start looking for another "stop" character. The third field begins immediately after this second "stop" character. SORT will then ignore "Ignoreleading=" characters at the beginning of this third field until the actual key is found. Miscellaneous Key Options: -Error indicates that the entire record should NOT be marked as erroneous even if this particular key is in error. The default is +Error. For more details, see the section on "Error Handling" below. Position descriptors are used to describe positions within records for key-items like "Before=" and "FRom=". Positions are given with numbers followed by an indication of units. The following units are recognized. Asciicharacters, BYtes, Characters equivalent to eight bits. This is the default if no units are specified with a number. Bcddigits equivalent to four bits. Bits equivalent to a sin-DIR 04JAN0006BAKBACKUPLOGÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿFCBSYSÿÿ¾%%¾%%3pãROOTDIRDIR ÿÿ¾%%¾%%0ò6?<%?<ÿÿN¹3`/9N¹2Jv3üL |#È/9/<ó?<?<?<ÿÿN¹3`/9/<Q09LÁü60@Ñü‚/?< N¹1B/<Q?<?<Q?<ÿÿN¹3`/9N¹2JRyLQËÿ€/<N¹2J |#È/9/<ö?<?< ?<ÿÿN¹3` |(#È/9/<out The contents of "file" are sorted in ascending ASCII order and the result is put in "out". sort file >out key=il=" " This sorts "file" into "out" in ascending ASCII order. Because of the "Ignoreleading=" field, the sort will ignore any leading blanks that appear at the beginning of each line. sort file key="fr=41,b=48,+des,+num" key="fr=0,b=30" "file" is sorted according to two keys. The first key is numeric; it begins after character 41 and ends at character 48 (the initial character of the record is charaOnly selects files created on or before the date and time specified. If a file is specified, then its date and time are used. :SINCE={DD/MM/YY_HH:MM | FILE_NAME} Only selects files created on or since the date and time specified. If a file is specified, then its date and time are used. :SINCE and :BEFORE can be used together to specify a time period. :MOD Causes date and time selection to be based on MODIFICATION rather than creation date and time. :ARC Causes date and time selection to be based on ARCHIVE rather than creation date and time. This switch is only valid for :E command. :GROUP=GID<,GID> Excludes files not matching one of the group ids. Hex numbers must begin with '$'. :OWNER=UID<,UID> Excludes files not matching one of the user ids. Hex numbers must begin with '$'. :EXCLUDE=FILE_SPEC<,FILES_SPEC> Excludes any files matching one of the FILE_SPECs. FILE_SPECs may include directory and name wild carding. Specs are seperat. Both directory and name wild carding are allowed for each spec listed. Multiple specs are seperated with commas, NOT spaces. COMMANDS : :I Insert. Files matching the FILE_SPECs will be inserted into an existing archive file, if one by the name given already exists, or the files will be inserted into a newly created archive file. :D Delete. Files matching the FILE_SPECs will be deleted from the archive file. :R Replace. Files matching the FILE_SPECs will be inserted into an existing archive file after any files already in the archive file having the same names are deleted. :E Extract. All files in the archive file whose names match the name portion of one of the FILE_SPECs will be extracted. The extracted file will be created in the directory specified in the matching FILE_SPEC. :L List. All files in the archive file whose names match the FILE_SPECs will be listed to the screen. SWITCHES : :BEFORE={DD/MM/YY_HH:MM | FILE_NAME}  criteria specified via the selection switches. Selection switches are based on such variables as creation or modification date, owner id, or group id. All of the switches are described below. If, during the execution of ARCH, another volume of media needs to be mounted, the user will be prompted to insert the next media into the device at the appropriate time. The user need only insert the media, ARCH will perform the logical mounting. The first volume must already have been mounted, and the desired path must already exist on that media. For additional volumes, the media need not be formatted. ARCH will prompt the user for format instructions. The path will be created on the new media by ARCH. PARAMETERS : COMFILE The name of a command file containing valid ARCH parameters and switches. ARCH_FILE The name of the archive file. It can be on any currently mounted device, and the path must exist already. FILE_SPEC The string representing the file(s) to be archivedhen the next four shortest, and so on. Appendix #5 -- Archive, Backup and Restore Utilities ----------- ------------------------------------- ------------------------------------------ COMMAND DESCRIPTION FOR THE "ARCH" COMMAND ------------------------------------------ SYNTAX : > ARCH ARCH_FILE FILE_SPEC<,FILE_SPEC> COMMAND > OR > ARCH @COMFILE DESCRIPTION : This utility will compact all files complying with the FILE_SPECs and SWITCH parameters in the archive file specified by ARCH_FILE. Files may come from any directory, but once a file is entered in an archive file, its original directory path is not retained. ARCH can be used to create libraries of linkable files or source files, or it can be used to backup a group of files into a single backup file. Included among the switches are qualifiers that restrict the number of files involved. These selection switches eliminate files that match the FILE_SPEC, but do not comply with one of the selectionated in the default directory called 'BACKUP.LOG'. This file records which files were copied into which backup files. After the last backup file is written, 'BACKUP.LOG' is copied to the backup media as the last file. If the backup session will result in multiple volumes of backup media, then the default device and directory MUST NOT be on the backup media. PARAMETERS : COMFILE The name of a command file containing valid BACKUP parameters and switches. BACKUP_DIR The full path spec to the directory where the backup files are to be located. The path must already exist on a currently mounted device. FILE_SPEC The string representing the file(s) to be archived. Both directory and name wild carding are allowed for each spec listed. Multiple specs are seperated with commas, NOT spaces. DSR The DSR for the destination device. SWITCHES : :BEFORE={DD/MM/YY_HH:MM | FILE_NAME} Only selects files created on or before the date and time specified. Ifching one of the FILE_SPECs. The files may be on any currently mounted disk. Directory and name wild carding are allowed. The backup files will be located on the device and in the directory specified by BACKUP_DIR. The backup device must already be mounted, and the directory must already exist. If multiple volumes of backup media are needed to hold all of the files, the user will be prompted at the appropriate time to switch the media. All logical dismounting and mounting will be performed by BACKUP. Any additional media need not be initialized, and the directory need not exist. The name of each backup container file will be created by concatenating a 2-byte string representing the day with a 3-byte string representing the month and a 4-byte string representing the number of the backup file created during this session. The name will always be exactly 9 bytes long, and the extension will always be 'BAK' with the general form 'DDMMMnnnn.BAK'. During the backup process, a log file is cre depending upon the size of the archive file, so the reservation of space may be worthwile. EXAMPLES : > ARCH MY.ARC /.*/* :I :EXCLUDE=*.EXE :SINCE=22/9/82_13:30 This command will insert all non-EXE files residing in and below the current default directory created on or since 1:30 p.m. September 22, 1982. > ARCH MY.ARC *.PAS,*.PRN :L :ARC :BEFORE=21/8/82_00:00 This commnad will list all files having a 'PAS' or 'PRN' extension that were archived on or prior to August 21, 1982. > ARCH MY.ARC .TEST/* :E :GROUP=$1001,$1002 :CONFIRM This command will copy all files with group ids of $1001 or $1002 to the subdirectory 'TEST' after allowing the users to confirm or reject each file. -------------------------------------------- COMMAND DESCRIPTION FOR THE "BACKUP" COMMAND -------------------------------------------- SYNTAX : > BACKUP BACKUP_DIR FILE_SPEC<,FILE_SPEC> DSR > OR > BACKUP @COMFILE DESCRIPTION : This utility will backup all files mated by commas, NOT spaces. :VERIFY Will verify that the files were entered properly in the archive file. If a file was not copied correctly, a warning is displayed to the log file. :LOG=FILE_SPEC By default, results are logged to SYS$OUTPUT. Through this switch, results may be written to some file. :DSR=DSR_SPEC If the archive file will need to span multiple volumes, the DSR of the destination device must be given via this switch. If the user fails to give the DSR, (s)he will be prompted for it when it is needed. :CONFIRM Displays files to be affected one at a time and allows the user to confirm or reject each file from the operation. :SPACE=n By default, space is reserved for the future addition of up to 48 files. This switch allows the user to reserve more or less space. If more than the reserved number of files are added to an archive file, the archive file will automatically extend itself. This extension process can take significant timeup via the BACKUP command. By default, files are restored to the current default device and directory. The user may optionally request that files be restored to their original device and directory using the ':ORIGINAL' switch, or to some other directory using the ':DEST=path' switch. 'ORIGINAL' and 'DEST=path' are mutually exclusive switches. Included among the switches are qualifiers that restrict the number of files involved. These selection switches eliminate files that match the FILE_SPEC, but do not comply with one of the selection criteria specified via the selection switches. Selection switches are based on such variables as creation or modification date, owner id, or group id. All of the switches are described below. If, during the execution of RESTORE, another volume of media needs to be mounted, the user will be prompted to insert the next media into the device at the appropriate time. The user need only insert the media, RESTORE will perform the logical mounting. The firstll be included in the backup. > BACKUP _DX0/ONE/ JIM.*/* MFLOP$150.DSR :RETRIES=5 :VERIFY This command will backup all files in all directories in and below the directory 'JIM' on the default device. Up to 5 retries will be made at copying files that do not verify or for which an error is detected during the copy. The backup files and log file will be located in directory '_DX0/ONE/'. > BACKUP _DF0/BKUP/ DI0/*/*,DI1/*/* FLOP$100.DSR :SINCE=TEST.PAS This command will backup all files in all directories of _DI0 and _DI1 that were created since the creation of file 'TEST.PAS' in the default directory. The backup files and log file will be located in directory '_DF0/BKUP/'. --------------------------------------------- COMMAND DESCRIPTION FOR THE "RESTORE" COMMAND --------------------------------------------- SYNTAX : > RESTORE BACK_FILE FILE_SPEC<,FILE_SPEC> DSR > OR > BACKUP @COMFILE DESCRIPTION : This utility will restore files that were backed e file. If a file does not verify, a warning is written to the backup log file. Retries are made on files that do not verify. :RETRIES=n If an error is detected in copying a file to one of the backup files, by default, up to three retries will be made at copying that file. Via this switch, the user may specify some other maximum number of retires. :LOG=FILE_SPEC By default a log file named 'BACKUP.LOG' is created in the default directory. The user may assign this log file a different name in a different directory using this switch. If this switch is used, the log file should not be assigned to the backup directory. EXAMPLES : > BACKUP _TP0/BKUP/ _DI0/*/* DEI$100.DSR :EXCLUDE=DI0/BOB.LIB/* This command will backup all files in all directories on _DI0. The backup files and log file will be located in _TP0/BKUP/. Files in directory 'DI0/BOB.LIB/' will be excluded from the backup. However, if there are any subdirectories below 'DI0/BOB.LIB/', they will sti a file is specified, then its date and time are used. :SINCE={DD/MM/YY_HH:MM | FILE_NAME} Only selects files created on or since the date and time specified. If a file is specified, then its date and time are used. :SINCE and :BEFORE can be used together to specify a time period. :MOD Causes date and time selection to be based on MODIFICATION rather than creation date and time. If this switch is used in conjunction with a file name, then this switch must preceed the :SINCE or :BEFORE switch. :GROUP=GID<,GID> Excludes files not matching one of the group ids. Hex numbers must begin with '$'. :OWNER=UID<,UID> Excludes files not matching one of the user ids. Hex numbers must begin with '$'. :EXCLUDE=FILE_SPEC<,FILES_SPEC> Excludes any files matching one of the FILE_SPECs. FILE_SPECs may include directory and name wild carding. Specs are seperated by commas, NOT spaces. :VERIFY Will verify that the files were entered properly in the archivto the current default directory. Appendix # 6 - TCOPY Utility ------------ ------------- ------------------------------------------ COMMAND DESCRIPTION OF THE "TCOPY" COMMAND ------------------------------------------ SYNTAX : > TCOPY FILE_1 FILE_2 BLK_SIZE DESCRIPTION : This command copies a tape file created on a foreign system, or copies to a tape file to be read by a foreign system. A file defined by file_1 is copied to a newly created file defined by file_2. Either file_1 or file_2 may be a tape drive. Wild cards are not permitted. The data should be in either ASCII or EBCDIC format, and it is recommended that no headers or labels be written on the tape. NOTE: TAPES READ OR WRITTEN ON A CIPHER DRIVE MUST BE NINE TRACK, 1600 BPI. PARAMETERS : FILE_1 - The source file specification. If the device is a tape then only the device name is recognized. FILE_2 - The destination file specification. If the device is a tape then only the device nspec, or to graft the original directory tree to some directory by specifying the directory followed by ".*". See example below. EXAMPLES : > RESTORE DF0/BKUP/22SEP0001.BAK BOB.LIB.*/* FLOP$100.DSR :DEST=JIM/ This command will restore files backed up to 'DFO/BKUP/' on September 22. The files all will be restored to directory 'BOB' on the default directory. > RESTORE DF0/BKUP/22SEP0001.BAK BOB.LIB.*/* FLOP$100.DSR :DEST=JIM.*/ The same as in the first example, only instead of restoring all of the files to directory 'BOB', the subtree from 'BOB.LIB' down will be grafted to the directory 'JIM'. > RESTORE DF0/BKUP/22SEP0001.BAK BOB.LIB.*/* FLOP$100.DSR :ORIGINAL The same as in the first example, only the files will be restored to their original path. > RESTORE DF0/B/01JUN0003.BAK /*/* FLOP$100.DSR :SINCE=26/5/82_18:30 This command will restore files backed up to 'DF0/B/' on June 1. Only files created on or since 6:30 p.m. May 5, 1982 will be restored. All files will be restored his switch is only valid for :E command. :GROUP=GID<,GID> Excludes files not matching one of the group ids. Hex numbers must begin with '$'. :OWNER=UID<,UID> Excludes files not matching one of the user ids. Hex numbers must begin with '$'. :EXCLUDE=FILE_SPEC<,FILE_SPEC> Excludes any files matching one of the FILE_SPECs. FILE_SPECs may include directory and name wild carding. Specs are seperated by commas, NOT spaces. :VERIFY Will verify that the files were entered properly in the archive file. If a file was not copied correctly, a warning is displayed to the log file, but no attempt will be made to retry the restoration of that file. :ORIGINAL This switch will cause files to be restored to their original device and directory. The device must be mounted, but RESTORE will create the path. :DEST={/dir_path/ | /dir_path.*/} This switch allows the user to either restore all of the files to some specified path by providing an exact directory  volume must already be mounted. PARAMETERS : COMFILE The name of a command file containing valid RESTORE parameters and switches. BACK_FILE The full file specification of the first backup file of interest. The device must already be mounted. FILE_SPEC The string representing the file(s) to be restored. Both directory and name wild carding are allowed for each spec listed. Multiple specs are seperated with commas, NOT spaces. DSR The dsr of the backup device. SWITCHES : :BEFORE=DD/MM/YY_HH:MM Only selects files created on or before the date and time specified. A file name cannot be used in RESTORE. :SINCE=DD/MM/YY_HH:MM Only selects files created on or since the date and time specified. A file name cannot be used in RESTORE. :MOD Causes date and time selection to be based on MODIFICATION rather than creation date and time. :ARC Causes date and time selection to be based on ARCHIVE rather than creation date and time. Tince no other parameters are specified, the appropriate defaults will apply. > TCOPY _TP0 ABC.DAT 512 :SKIPF=-2 :SWAP :CVRT=A :RECL=128 :TERM=TRIM,LF This command will cause the tape drive to rewind from wherever it is until it has encountered two file markers or the front of tape marker. A file named ABC.DAT will be created under the current default device and directory. Using a block size of 512 and a fixed record size of 128, each pair of bytes copied from _TP0 will be swapped, converted from EBCDIC to ASCII, have trailing blanks trimmed and each record terminated with a line feed character. ROOTDIR/BOOTDISK.150 13-Dec-82 3072 163493 ROOTDIR/DISK.150 13-Dec-82 14336 953181 ROOTDIR/KERNEL.150 13-Dec-82 20072 1475823 ROOTDIR/KERNELBUG.150 13-Dec-82 31648 2068127 ROOTDIR/MATH1010.150 13-Dec-82 2048 125938 ROOTDIR/OSINIT.150 13-Dec-82 4096 217440 ROOTDIR/STARTUP.150 13-Dec-82 4096 61240 ROOTDIR/TTY- NO Specifies whether the source file is to be converted from ASCII to EBCDIC or vice versa, depending on whether it contains an E/e or an A/a respectively. If the parameter is blank or if it contains an 'n' or 'N', then no conversion takes place. :DET - ERROR TERMINATION DEFAULT - YES When this switch is specified as NO, TCOPY will not terminate on minor errors; but will continue to copy until either a file marker is detected or a fatal error is encountered. :TPMRK - WRITE TAPE MARK DEFAULT - NO Specifies whether or not a tape mark should be written on the tape before copying the data to the tape. EXAMPLES : > TCOPY ABC.TXT _TP0 1024 :TERM=CR,LF This command will copy the file ABC.TXT from the current default device and directory to the tape using 1024 as the block size. The TERM option specifies that all carriage return characters in the file ABC.TXT will be replaced with a line feed before being written to the tape. Swould cause all trailing blanks to be trimmed from the source terminator. PAD is a destination terminator and specifies that records are to be blank filled out to the :RECL specified. PAD and TRIM are mutually exclusive. :SKIPF=n - SKIP N FILES DEFAULT - 0 Specifies the number of files to skip on the source device prior to executing the copy operation. N must be an integer, either positive or negative. If the parameter is negative, then the tape will wind backwards that number of files, otherwise the tape will wind forward that many files. :SKIPB=n - SKIP N BLOCKS DEFAULT - 0 Specifies the number of blocks to be skipped in the source file prior to the execution of the copy operation. N must be a positive integer. :SWAP - SWAP BYTES DEFAULT - NO Specifies whether or not the contents of each pair of bytes is to be swapped before being written to the destination file. :CVRT=A/E - CONVERT DEFAULT ame is recognized. BLK_SIZE - The size of each block in bytes. Must be an even integer. NOTE: THIS PARAMETER MUST NOT EXCEED 4096 BYTES. Options are identified by key-word rather than position as follows : :RECL=n :TERM=s :SKIPF=n :SKIPB=n :SWAP :CVRT=A/E :DET :TPMRK :RECL - FIXED RECORD LENGTH DEFAULT - 1 Specifies the number of bytes to a fixed length record. Must be a positive integer. If this option is specified, then BLK_SIZE must be a multiple of the value given. :TERM=s - SPECIFY RECORD TERMINATOR DEFAULT - NULL,NULL 'S' consists of a pair of parameters seperated by comma's specifying the record terminator in the source file and the terminator to replace it with in the destination file. Possible values are: CR, LF, CRLF, NULL, TRIM, and PAD. The first parameter specifies source record terminator and the second parameter specifies the destination record terminator. TRIM would be specified as the source terminator and /CIP.EXE 13-Dec-82 18432 1290073 SYSEXE/COPY.EXE 13-Dec-82 34816 2699142 SYSEXE/COUNT.EXE 13-Dec-82 15360 1039812 SYSEXE/CRD.EXE 13-Dec-82 9216 569488 SYSEXE/CREATE.EXE 13-Dec-82 10240 525971 SYSEXE/DEL.EXE 13-Dec-82 14336 1123596 SYSEXE/DEV.EXE 13-Dec-82 9216 395610 SYSEXE/DINIT.EXE 13-Dec-82 17408 793648 SYSEXE/DIR.EXE 13-Dec-82 24576 1958629 SYSEXE/DMNT.EXE 13-Dec-82 9216 403610 SYSEXE/DUMP.EXE 13-Dec-82 14336 1022141 SYSEXE/DUPDAT3.EXE 13-Dec-82 31744 2074915 SYSEXE/DWNLD.EXE 13-Dec-82 12288 579649 SYSEXE/DYMEM.EXE 13-Dec-82 17408 1220489 SYSEXE/ERR.EXE 13-Dec-82 8192 352577 SYSEXE/FIXSTACK.EXE .150 13-Dec-82 3072 190723 SYSDSR/CENT$150.DSR 13-Dec-82 2048 80856 SYSDSR/MFLOP$150.DSR 13-Dec-82 3072 204721 SYSDSR/MSC$150.DSR 13-Dec-82 3072 169670 SYSDSR/NULL.DSR 13-Dec-82 1024 18651 SYSDSR/PIP02$150.DSR 13-Dec-82 1024 53608 SYSDSR/PIP05$150.DSR 13-Dec-82 1024 53609 SYSDSR/PIP10$150.DSR 13-Dec-82 1024 53611 SYSDSR/RAVD$150.DSR 13-Dec-82 3072 133998 SYSDSR/RAVDP$150.DSR 13-Dec-82 8192 351415 SYSDSR/TTY$150.DSR 13-Dec-82 2048 117691 SYSEXE/ARCH.EXE 13-Dec-82 60416 4980228 SYSEXE/BACKUP.EXE 13-Dec-82 51200 4160448 SYSEXE/BTUP.EXE 13-Dec-82 16384 810498 SYSEXE/CATALOG.EXE 13-Dec-82 15360 956310 SYSEXE/CHECKSUM.EXE 13-Dec-82 21504 1650465 SYSEXE/CHKD.EXE 13-Dec-82 40960 2586018 SYSEXEFCBSYSÿÿ¾%%¾%%3pãROOTDIRDIR ÿÿ¾%%¾%%0ò6?<%?<ÿÿN¹3`/9N¹2Jv3üL |#È/9/<ó?<?<?<ÿÿN¹3`/9/<Q09LÁü60@Ñü‚/?< N¹1B/<Q?<?<Q?<ÿÿN¹3`/9N¹2JRyLQËÿ€/<N¹2J |#È/9/<ö?<?< ?<ÿÿN¹3` |(#È/9/<' is no longer required as the first character on a line in a command file. - Within the spawned CIP, SYS$INPUT is redefined to be the command file that the spawned CIP is using. Because of this, if you have any programs in the command file which request input from standard input, these have to be redefined to be the logical name SYS$PROMPT which is defined to be the station which initiated the command file. (e.g. to use the PROMPT command within a command file, you would use the following "PROMPT ENTER YOUR NAME XXX'LOG'YYY ) | | * CIP will allow translated command lines to be longer than 80 characters. | (The maximum is 100 characters.) | | * The help files for all the utilities have been rewritten. (In addition, | help files have been provided for all the new utilities.) 2.2 CIP UTILITIES All of the utilities were enhanced to accomodate the following changescified | will be in effect after returning to the parent CIP. | | * There is a new OPTION command built into CIP. It accepts either a :VERIFY | or a :NOVERIFY switch. The :VERIFY switch causes command lines from command | files to be displayed as they are executed. The :NOVERIFY switch supresses | the display of command lines from command files. Usually CIP is set to | NOVERIFY. | | * Logical name substitutions in assignment statements will be allowed. | For instance in the following statement, the logical name equivalent | of 'p1' will be substituted before the logical assignment is made. | The logical name to be substituted must be in single quotes and the | multi-word assignment must be in double quotes as in the following example: | | > aaa := "this is parm1 'p1'" | | Note that all multi-word assignments should be enclosed in double quotes | instead of the single quotes which were used in previous releases. | (sfile name, but also as many characters as possible from the name of the standard input file. This allows better recognition of which processes belong to which users. For instance the process name for a copy of VEW running on _TT3 would have the process name "VEW_TT3". * The new command "CMDST" is included in the CIP. It causes the display of the recently issued command list. The command list contains the 8 most recently entered commands. Pressing the CTRL/R key will retrieve commands from the top of the list as it appears on the screen. Pressing CTRL/P will retrieve commands from the bottom of the list as it appears on the screen. * The ability to fork a command file as a background process has been added to CIP. The syntax is: >&@filename parm1 parm2 ... | * The CD command built into CIP is enhanced to have a :PERM option when | it is used in a command file. If ':PERM' is present on a CD command | while executing a command file, the default device and directory spethe command name) is translated being replaced with either the original word or it's logical equivalent. If there is an ampersand (&) or at sign (@) in front of the command name, they are not included in the name that is translated. Then all entries on the command line which are enclosed in single quotes (') are translated being replaced by either the null string, or the logical equivalent. Not all words are translated. Also, entries can be substituted in the middle of strings, which was not possible before. This change allows the user to control which parts of the command line are translated and which are not. For example given the following logical name assignments: T :== TYPE FILE1 :== DX0/SYSLIB/MCS and the following command to the CIP: T 'FILE1'0310.RLS,FILE2.TXT the CIP would type the contents of DX0/SYSLIB/MCS0310.RLS and FILE2.TXT on the standard output. * When a new process is forked or spawned by CIP, the process name (displayed by the STAT command) contains not only the bad sectors checked during that run. | 3. User feedback will be written to the screen showing | the user the intermediate progress being made by the | program. This feedback will be of the form: | .........|.........|.........|.........|.........| | .........|.........|.........|.........|.........| | where each '.' indicates 1% of the sectors done, and | each '|' indicates 10% of the sectors done. If less | than 100 sectors are being checked, each '.' indicates | 1 sector done. | | 4. Two optional switches, :FULL and :LOG=filename, are | provided for your convenience. Their functions are as | follows: | | :FULL - if specified, will cause CHKD to subject all | unallocated sectors to the "Very Extensive Test". | This is particularly useful immediately following | initialization of the disk with DINIT, causing | practically the entire disk to be tested | rigorously before it is used. | *** NOTE *** Disks with a large number of | free sectors will require a great amoun to BTUP: | | :Usercache (maximum # of cache elements that can be used by | a single process at one time) | :Readahead (Y or N , Y means read ahead is to be done on that | disk) | :Ialloc (initial sector allocation) | :Alloc (extension sector allocation) 2.2.4 CHKD (Check disk for bad sectors) | This utility has been rewritten. The previous version | of CHKD followed the philosophy that any sector that could | possibly be used should be marked as good and made | available for use. This was found to be undesirable. The | utility has been changed and enhanced to do the following: | | 1. Any sector that is unreadable will be marked bad. Any | allocated sector that requires retries to be read will | be marked bad. Any unallocated sector that requires | retries to be read will be subjected to a "Very | Extensive Test" which it must pass without retries to | be allowed to remain good. | | 2. CHKD will report the name of any file that contains | ultiple volumes. (REF: Appendix #5 -- Archive, Backup and Restore Utilties) 2.2.2 BACKUP/RESTORE (Backup and Restore files) ***NEW COMMAND*** This pair of new utilities allow incremental backups and retrieval of files onto multiple volumes. Files can be grouped together into a library based on several selection criteria, including the file name, date last modified and/or the file owner. The names of all files backed up are logged in a log file. Both backup and restore have verify options which allow you to verify that files were entered into/copied from the backup archives. (REF: Appendix #5 -- Archive, Backup and Restore Utilities) | The following bugs were fixed in BACKUP: | | 1. It now uses the "forced write" edit mode so that errors will be | reported correctly. | 2. If an error occurs in writing a file, the last byte of the file | is written anyway to make the file size match the recorded size. 2.2.3 BTUP (Disk Boot Block Update) | The following switches have been added: * As CIP no longer converts the command lines to upper case, the utilities were made insensitive to case. * Some of the utilties depended on the fact that the null character was a line terminator. This dependancy was removed. Either a line feed or a null will be recognized as a line terminator. * The utilties were linked with the updated linker which reserves the high 4K bytes of memory for the floating point hardware. This is in preparation for the hardware floating point option to be released later. | * All of the utilities which do mounts or dismounts have been changed | to report any warnings returned. 2.2.1 ARCH (Archive) ***NEW COMMAND*** This new utility is added to provide a librarian function. Files can be grouped together into a library based on several selection criteria, including the file name, date last modified and/or the file owner. The archive file can be updated (added to, deleted from ... ). The archive file can grow indefinitely. An archive file may span mnsion sector allocation) | | A bug was fixed so that now when DINIT gets an error it dismounts | the device being initialized. 2.2.9 DIR (List files in a directory) This standard utility has been modified to support the new tape file label formats. To list files with the previous tape labels, use the utility DIR$1. It has also been modified to list the file sequence number in addition to the FCB number. | This utility has been changed to accomodate the larger file | capacity of SMD disk. 2.2.10 DM (Display Memory) ***NEW COMMAND*** This new utility will display on the terminal screen a map of memory usage on the system 100 or the multiuser system 150. It will not run on the single user (unmapped) system 150. Up to 960K bytes can be represented on the screen. The DM utility permits you to specify the frequency with which the map is updated. | Changes in DM (Display Memory) utility include: | | 1. In addition to the mandatory screen refresh interval parameter, | two optional parameteed as follows: FUJ76 - Fujitsu 84 megabyte unformatted (76 formatted) FUJ152 - Fujitsu 168 megabyte unformatted (152 formatted) FUJ421 - Fujitsu 474 megabyte unformatted (421 formatted) * PRI132 - Priam 144 megabyte unformatted (132 formatted) * PRI32 - Priam 35 megabyte unformatted (32 formatted) * AMP302 - Ampex 330.3 megabyte unformatted (302 formatted) * CDC152 - CDC 160 megabyte unformatted (152 formatted) * CDC29 - CDC 35 megabyte unformatted (29 formatted) * NEC76 - NEC 85 megabyte unformatted (76 formatted) * These are proposed and have been included in the driver but have not been tested and are not supported by Wicat Systems currently. | The following parameters have been added to DINIT: | | Usercache (maximum # of cache elements that can be used by a | single process at one time) | Readahead (Y or N , Y means read ahead is to be done on that | disk) | Ialloc (initial sector allocation) | Alloc (extee. | | 3. When the primary device driver is changed, the current disk | types from that driver are displayed. Formerly, changing the | primary device driver did not change the displayed disk types. 2.2.6 COPY (Copy files) This standard utility has been modified to support the new tape file label formats. To copy tape files with the previous tape labels, use the utility COPY$1. The new version of COPY allows copying to and from any TTY, TTYSPC, TAPE, DISK or PIPE class device. It also allows ":CONFIRM" AND ":CONCAT" switches. 2.2.7 CRD (Create directory file) | A bug was fixed so that a directory can now be created on other than | the default device by typing: | | CRD _DX0B/MYDIR/ | | rather than: | | CRD _DX0B/ROOTDIR.MYDIR/ | | as was previously necessary. 2.2.8 DINIT (Initialize disk) The standard DINIT utility has been updated to initialize the new large SMD disks. To incorporate these new drives, a set of new device types has been specifit of time | to run CHKD; as long as several hours. | | :LOG=filename - if specified, all screen output will | also be written to the specified file for later | scrutiny. This is useful when the user will not | be available to watch the screen to see which, | if any, files are found to contain bad sectors | or if the utility is forked to run in the back- | ground with SYS$OUTPUT redirected to the _NULL | device. | *** NOTE *** The specified log file CANNOT | reside on the disk being checked. | | *** NOTE *** CHKD must NOT be run on a disk on which other | *** NOTE *** processes are running. 2.2.5 CONFIG (Configure disk) | The configuration utility has been modified as follows: | | 1. The MSC$150.DSR driver for the old disk controller on the unmapped | system 150 is now configurable to handle the four types of disks | so this has been included in the CONFIG utility. | | 2. CONFIG now updates the sysconfig file only if changes have been | made to that fil, | therefore the part of the stack occupying space in the top page | is simply deleted. | | Since FIXSTACK safely handles non-image files and files whose | stacks are already correct, an entire disk can be updated (via | directory wildcarding) in one command: | | eg. FIXSTACK _DI1/*/*.* | | Files updated by FIXSTACK will still run under all older versions | of MCS. 2.2.13 GPRINT (Print the graphics screen) ***NEW COMMAND*** | This new utility transfers the contents of the graphics plane of | the MG8000 terminal to a printer. A scale parameter is supplied | to control the size and orientation of the image on the printer. 2.2.14 INCL (Include files) | A bug was fixed so that an empty destination file will no longer | result from being unable to open the source file, and making it | possible to specify the same file as both source and destination. | It has also been modified to output an "Included" message when | the file(s) to be merged with the source file is(are) opened, | to single| of user space (see the 8087 Floating Point Support section of | this document). It moves the stack down in any image file that | needs it. This utility would need to be run on all executable | files created prior to the release of MCS 4.0 and all executable | files created with versions of the Fortran or C loader which do | not automatically adjust the stack (also see 2.2.16). | Files to be updated can be listed on the command line, | separated by commas (directory and filename wildcarding are | allowed), otherwise a file specification is prompted for. The | name of each file specified is logged on the screen along with | a message indicating what action was taken on that file. The | possibilities are: 1) not an image file - nothing is done to the | file, 2) no stack adjustment necessary - nothing is done to the | file, 3) stack adjusted - the stack is shifted down out of the | top 4K page of user space, and 4) stack adjusted by forfeiting | top page - there is insufficient room to shift the stack downthe process displayed | r - page is allocated (resident) to the process displayed | p - page is write protected to the process displayed | s - page is shared with 2 or more processes | | 5. The process PID used to select which logical space to display in | megabytes 0 and 1 may be changed at run time. To select a new | PID strike the escape key. A prompt will appear on the | command line requesting a new PID. Enter the PID in hexidecimal | digits. The hexedecimal prefix character '$' is optional. | Terminate the PID string with a carraige return. A PID of zero | is interpreted as the PID of the current process (alias DM itself). 2.2.11 DUPDAT3 (Disk update to MCS 3.0.0 format) This standard utility has been modified to fill in the file type into the directory entry of each file. 2.2.12 FIXSTACK (Fix the program stack space) ***NEW COMMAND*** | This new utility is provided to handle the problem of updating | image files which have stack area allocated in the top 4K page rs have been added to the command line. | The first optional parameter is the megabyte of memory which will | be displayed at the time DM starts execution. If no value is | specified the default is 2. The second optional parameter is the | PID which will be used to identify the owner of the logical space | in megabytes 0 and 1. If no value is specified the PID of the | current process (alias DM itself) is assumed. | | 2. The DM display has been increased to show a complete megabyte of | memory on the screen. | | 3. The megabyte of memory may be changed at run time to display any | megabyte of memory from 0 to 9 inclusive by striking the 0 to 9 | keys on the keyboard. Megabytes 0 and 1 belong to a particular | process, whose name and PID will be displayed at the top of the | screen when megabytes 0 or 1 are being displayed. | | 4. The page information displayed with megabytes 0 and 1 have the | following meanings: | blank - page is not allocated | o - page is owned by  hysical sectors on the disk. The disk to be "patched" must be mounted so if the disk is not initialized or the boot block has been corrupted, you can specify "DISKSPC" instead of "DISK" for the device class in the MNT command. | This utility has been modified to accomodate the larger capacity | of the SMD disk, write the buffer to disk even when only the | checksum changes, and restrict ascii output to chr(32) through chr(127). 2.2.22 PRINT (Print file) | Changes in the PRINT utility include: | | 1. A :NOHEAD option has been added to allow files to be printed without | a header flag. The option must be specified at the time the file(s) | is/are queued for printing. | | 2. The parsing of switches has been improved to accept any unique and | legal abbreviation of up to 6 characters. | | 3. Communication among the processes used to implement the printer | queue has been improved. Faster response time to print queue requests | will be evident. | | 4. Exit handlers have been added to the (Refer to the Warnings section of this document | for a description of the "shouting match" problem.) 2.2.19 MEMTEST (Memory test) ***NEW COMMAND*** | This utility tests unallocated memory in the system. It unlinks any | bad pages it finds from the "free list", making these pages unavailable | to MCS. 2.2.20 MXFER (Diskette transfer) ***NEW COMMAND*** | This new utility allows for sector by sector floppy transfers | when only one floppy drive exists on the system. It copies | an "image" of the floppy onto the system disk, then produces | 0 or more copies of that diskette. There are four optional | switches available. They are :VERIFY (verifies that copies were | made correctly), :DELETE (deletes intermediate file when done), | :FORMAT (formats destination diskettes), and :COPIES (specifies | number of copies of source disk to be made - default is 1). 2.2.21 PATCH (Patch the disk directly) ***NEW COMMAND*** This new utility is a derivative of ZAP. It allows inspection and modification of pously. If needed, the interval between login polls and the interval between flushing disk buffers can be set to any desired value. NOTE: IF THE FLUSH FLAG IS TURNED OFF ON A DISK (INDICATING THAT BUFFERS ARE WRITTEN TO THE DISK BY LOGFLUSH ONCE EVERY 30 SECONDS), THAT DISK SHOULD BE DISMOUNTED PRIOR TO TURNING THE SYSTEM OFF. IF THE SYSTEM CRASHES DUE TO POWER FAILURE OR SOMETHING, THE RECOVER COMMAND SHOULD BE RUN IMMEDIATELY AFTER BOOTING THE SYSTEM AGAIN TO ENSURE THAT THE INTEGRITY OF THE DISK IS MAINTAINED. | NOTE: SEE SHUTDOWN COMMAND (SECTION 2.2.26) 2.2.18 LOGON (Log a user into the system) | The following changes were made to LOGON: | | 1. It will now look for the UAF.DAT file on SYS$DISK. | | 2. It will append the entire terminal device name onto the username | as the process name for the logon CIP. | | 3. "Username" is prompted for only if the "RETURN" key is pressed. | This was done to help prevent "shouting matches" with other | devices.-space rather than double-space sreen output, and to allow | spaces between the "%%" and the filename and after the filename. 2.2.15 KILL (Terminate a task) | This utility has been enhanced to allow more than one PID on the | command line. The PID's would be seperated by blanks on the command | line. 2.2.16 LINK (Link portions of program together) The link prgram has been modified to begin the user stack down 1 4K byte page from the top of the 2Mb address space. This reserves the top page for floating point hardware. It also insulates the Operating System from run-a-way I/O which could overwrite the Operating System. 2.2.17 LOGFLUSH (Replaces STARTLOG and FLUSH programs) The two programs STARTLOG and FLUSH have now been replaced by the single program LOGFLUSH. This program combines the two functions of polling terminals to initiate logging in sequences and flushing all modified buffers to any disk devices. This program is started up in background at system startup time and runs continu ically to do a warm boot following completion of the | shutdown procedure. 2.2.27 SKIP (Skip files on a tape) | The SKIP (skip files on tape) utility will be released on the 156 | (as well as the 100). 2.2.28 SORT (Sort records in file) ***NEW COMMAND*** | This new utility is a versatile sorting program. (REF: Appendix #4 -- | SORT Utility for complete documentation). 2.2.29 SSCOPY (System to system copy) | This utility has been fixed to better handle error conditions. | In addition, an "_" is no longer required on the port name. 2.2.30 TALKT (Talk to a TTY port) | Previously it was impossible to use more than one level of TALKT, | and break out of them in reverse order, because TALKT could not | send the terminator character (cntl-Z). (In fact, it could not send | any control characters.) TALKT has been changed to allow any level to | be terminated and any character to be sent through any number of | levels (maximum nesting level is 9). | | At the first level, to quit type: | | [cntl-Z] [0]| disk statistics at the end of the run). 2.2.24 SEND (Send message to other users) ***NEW COMMAND*** | This new utility allows the user to send a message to a list of | devices or all (TTY class) devices. 2.2.25 SERIAL (Print the system serial number) | This utility has been fixed so it can print the serial # on | unmapped System 150's. It has also been changed to print the | number both in hex and decimal. 2.2.26 SHUTDOWN (Shut down the system) ***NEW COMMAND*** | This new utility safely and quickly shuts down the system by | killing all processes and then dismounting all devices. Any devices | it can not successfully dismount will be reported and flushed. | The user must supply a delay of minutes:seconds to wait to begin | the shutdown procedure. The user may also specify a message to | be sent to all TTY class devices connected to the system (or, | in conjunction with a :NOBROADCAST switch, only to 'sys$output'.) | The user can also specify a :REBOOT switch which will cause the | system automatthey were queued. 2.2.23 RECOVER (Rebuild system files) This standard utility has been modified to fill in the file type into the directory entry of each file. | This standard utility has been modified to rebuild the FCBBITMAP in its | new form. If RECOVER is executed on a disk with the old style FCBBITMAP, | it will still operate correctly, generating a new style FCBBITMAP file. | | RECOVER was modified to allow it to be used on large disks. | | Improvements were made in the procedure used by RECOVER. It inspects | the FCB's fewer times, especially if shared sectors are found, thus | reducing the amount of time required to recover a disk. | | Optionally, disk statistics on file size, and extent usage | can be displayed at the end of the recover. | | The operator can no longer specify which part of the RECOVER | process to run. Rather, it always recovers everything. | | There are 2 switches that can be applied to RECOVER. Namely | :VERSION (displays a version banner) and :STATS (displays  print queue processes such that | they behave correctly under unexpected abort conditions. Interlocking | of pipe usage between PRINT and QMGR has been implemented. | | 5. Carriage returns are always written to the printer port after each | form feed encountered or generated by QPRT.EXE. | | 6. A form feed and carriage return is always written to the printer | port when QPRT.EXE terminates, whether the file queues completed | printing or not. | | 7. The name of the QMGR process associated with a print request is | derived by adding the last 5 characters of the (translated) logical | name PRINTER to QMGR. Previously, only the last character was added. | | 8. Multiple printer queues may be simultaneously assigned and in use. | | 9. Printer queues may be assigned to a file. Currently multiple versions | of the output file will be created. In future versions of the OS | only 1 file will be created and all files queued to the printer | file will be appended in the order in which   the utility TINIT$1. | The TINIT (initialize a tape) utility will be released on the 156 | (as well as the 100). 2.2.33 VEW (Virtual Edit Window) | The following changes were made to VEW: | | 1. Input (SYS$INPUT) can now be redirected to come from a disk file. | This allows a very limited batch editing capability. | Output (SYS$OUTPUT) must still be set to a valid TTY device. | | 2. VEW now has an exit handler which causes the previous terminal | characteristics to be restored when VEW is killed. 3. MCS OPERATING SYSTEM 3.1 DEVICE NAMING CONVENTIONS To accomodate the development of several non-uniform devices on the same controller, the device naming convention has been enhanced. It is upward compatible with the current naming scheme. The names are still restricted to up to 8 characters. The new device name is broken up into the following fields: _DX 0 A 0 --- - - - ------------ -------------- ------he would type [ctrl-Z] [1] [ctrl-Z]. | In other words, he would tell the talkt at level 1 to send a [ctrl-Z] | to the system it is connected to. Then the operator would tell the | talkt at level 1 to terminate by typing [ctrl-Z] [1] [ctrl-Q]. He | could then tell the talkt at level 0 to terminate by typing | [ctrl-Z] [ctrl-Q]. If you have difficulty remembering how to send a | command to a certain talkt in the chain, draw the configuration out as | above and it should be fairly simple from there on out. 2.2.31 TCOPY (Tape copy) ***NEW COMMAND*** This new utility is added to allow reading and writing foreign tapes. It provides standard conversion to and from ebcdic. It will block and deblock records. It will swap bytes and/or exchange line termination characters in text files at the users option. (See Appendix 6) 2.2.32 TINIT (Initialize tape) This standard utility has been modified to initialize a tape with the new tape label format. To initialize a tape with the previous tape labels, useown below: | | SYSTEM 150 SYSTEM 200 SYSTEM 150 | ---------- ----------------- ---------- | | |tt2 tt1a1| |tt3a1 tt3| | | | talkt -|---------------|- - - talkt - - -|---------------|-create | | | | | | | | | | ---------- ----------------- -----+---- | | | -------- | level 0 level 1 | disk | | ------- ------- | file | | -------- | | Now once the operator has typed in all of the data that is to be | entered into the disk file, he needs to send a [ctrl-Z] to the create | program to terminate it. To do this,  [cntl-Q] | -or- | [cntl-Z] [cntl-Q] | | to send a cntl-Z type: | | [cntl-Z] [0] [cntl-Z] | -or- | [cntl-Z] [cntl-Z] | At the second level, to quit type: | | [cntl-Z] [1] [cntl-Q] | | to send a cntl-Z type: | | [cntl-Z] [1] [cntl-Z] | | At the Nth level, to quit type: | | [ctrl-Z] [N] [ctrl-Q] | | to send a ctrl-Z type: | | [ctrl-Z] [N] [ctrl-Z] | | Where N is the number of levels of TALKT to pass the | command or character through. (N can not be more than one | digit.) | | To clarify this, an example follows. In this diagram, you have | three Wicat systems connected together. On the leftmost system, | the operator typed the command "TALKT _TT2" in order to enter commands | on the middle system. Once logged in on the middle system, the | operator typed "TALKT _TT3A1" to enter commands on the rightmost | system. Once logged in on the rightmost system, the operator types | the create command to create a file on the rightmost system's disk. | We end up with the configuration as sh s may have the same file read locked (write locked) as long as no one of them request read (write) access. If read access (write access) is requested, access is granted as long as the file is not already read locked (write locked). For example, if a user opens a file with read access and write lock, he or any one else can read the file but no one can modify its contents. Then, if another user opens the same file with read access and write lock, the system will grant his request and he can read the file as well. However, if a user tries to open the same file with write access, his request will be rejected. 3.4 SUPERVISOR CALLS (SVC's) |Several new SVC's were added. They are: | | 1. A new form of get status (trap 49), and | 2. A new form of set status (trap 50). | These use 128 byte status blocks. | Internally all the device drivers are using the 128 byte status | blocks. For compatibility the old traps return the same (old) | status blocks although these old traps will soon be phased only nulls but also line feeds to the carriage return line feed combination. This change was made to reflect that the line feed is the industry standard line termination character. At some later date (circa March 1983) the null character will no longer be recognized as a line terminator. 3.3 FILE LOCKING MECHANISM MCS has always had a file locking mechanism (the read lock and write lock mode bits set when a file is opened). Under previous releases, if a process requests read lock (or write lock) and the file is not already read locked (or write locked), access is granted. It does not check to see if other processes are already using the file. The file may be read locked (write locked) only one time by one process. If a process requests read access (or write access) and the file is not already read locked (write locked) access is granted. With 3.1.0, if a process requests read lock (or write lock) access is granted if no process has already been granted read access (write access). Multiple processeoller, and board 1). Defaults are assumed at the end of the name. For instance, _DX assumes drive 0, device type A and board 0. _DX1 assumes device type A and board 0. _DX1B assumes board 0. To help system 150 users to determine the correct name for the floppy, the following table is provided: Controller How to identify Device name ---------- --------------------------- ----------- WD3 Single multi-layered board. _DX0B0 WD2 Piggy-backed board (two boards _DX0 attached together). MSC4 Single board with large black _DX0 boxmounted near top center edge. Only used on unmapped single user system 150WS. The controller is mounted in the card rack slot closest to the front of the system 150. |To see examples of the device names that are available on the type of system |that you have, type "NAMES?" and they will be displayed. 3.2 LINE FEEDS The line feed character (ASCII 10) is now recognized in the file system edit modes as a line terminator. The write edit mode 3 will map not-- ------------ DRIVE/DEVICE DEVICE CONTROLLER CONTROLLER NUMBER TYPE NUMBER ------------ -------------- -------- ------------ _DX,_TT,_DI, (0 - 63) (A - Z) (0 - 9) etc. The first alpha characters identify the controller. (e.g. _DX, _TT, _DI, etc.) Following that comes the drive/device number (e.g. _DX0, _TT1, etc.) Next is the device type. There may be several device types on the same controller. For example, the Intelligent Port Expander (IPE) has several serial ports and a parallel port. The new Western Digital board has a winchester and a floppy. The device types are identified with a single letter (A-Z) (e.g. _DX0A, DI1A). Finally, there is the ability to reference additional boards. There may exist two or more similar controller boards in a system. These are identified by a single digit (0-9) (e.g. _DX2B1 means the controller _DX, drive 2, the Bth device on that contr ascal. | | * Due to the above, the KSAMLIB directory has been dispensed with and | the directory KSAM is set up with just the KSAMCONV utility program | to convert old KSAM files to the new format. | | * A new mode bit (6) was added to the _KREAD system call. When the bit | is set no data is actually read. This is used to specify the | direction for subsequent reads and writes. | | * Previously, if an attempt was made to lock a record that was already | locked, and the timeout expired, a timeout error was returned. Now | the error returned is "KSAM record locked". 3.6 8087 FLOATING POINT SUPPORT |The OS has been modified to provide support for the new 8087 |hardware floating point board. When a user process is initiated |(via create process) the highest 4K byte page of the user's logical |space is reserved. When during execution the process identifies |itself as a floating-point user, the dual port memory on the 8087 |board is mapped into that page (if hardware is present on the system). |This allows iems or with the VEW editor on 100 systems. If the above line is already in the sysconfig file but is preceeded by an exclamation (!), simply remove the exclamation to enable KSAM. You must reboot the system after changing the sysconfig file. Functionally, the KSAM option provided in the Operating System is nearly identical to the KSAM pascal run time routines which were shipped out to some customers previously. The main distinction concerns the multiuser capability, record locking, segmented keys, more key types and deadlock detection which were not available with the pascal run time. A utility program is provided to convert Pascal Run-time KSAM files to the new format. A full description of the capabilities of the KSAM file handler and how to make use of it is contained in the KSAM PROGRAMMER REFERENCE MANUAL. |Changes to the KSAM package with release 4.0 of MCS are as follows: | | * The runtime interface between KSAM and Pascal is not part of the | MCS release. It will be released shortly with P1 = hardware) | DC.W 26 | | (The stack is returned clean.) 3.5 KSAM (Keyed Sequential Access Method) KSAM is an optional Operating System module that can be configured in at boot time the same way that class handlers are currently configured. It allows a more sophisticated access method than the current random access. It provides: - Multiuser access to KSAM files - Record level locking - Deadlock detection - Multiple keys - Segmented keys KSAM files are maintained as two separate files, one which contains the keys and the second which contains the data. To add KSAM capability to your system, you must make sure that the system configuration file contains the line "KSAM.156" (mapped S150) or "KSAM.100" (S100/200) previous to the line with OSINIT.--- on it. The system configur- ation file is in ROOTDIR on the system disk and is named SYSCONFIG.156 for the mapped system 150 or SYSCONFIG.100 for the system 100 and 200. This can be done automatically with the CONFIG command on 150 syst out. | Complete information on the calling sequences and staus block | definitions is contained in the appendix to this document. | | 3. A "fast read complete" (trap 55). | This is to be used in conjunction with fast reads from the disk. | Because fastread is asynchronous, the user must be able to | determine when the transfer is complete. This trap waits for all | pending sectors to load before returning. It returns any errors | received on the image load. The calling sequence is as follows: | | Push lun of file | Push address of status | TRAP 0 | DC.W 55 | | (The stack is returned clean.) | | 4. A "mathinit" (trap 26). | This identifies the calling process as a floating-point math user. | It returns a value indicating whether or not there is floating- | point hardware and maps the floating-point hardware, if present, | into the user's space. The calling sequence is as follows: | | Push address of return value (0 = no hardware, | TRAP 0  e other provided | as an argument) 3.7 SCHEDULER |The scheduler was modified to fix some long standing bugs and to |add some enhancements as follows: | | - The time slice value used in setting the interval timer | chip on the unmapped 150 and the multiuser 156 was incorrectly | set to a value 8 times less than it should have been. This | caused rescheduling of tasks on these systems to happen much | more frequently than it should have. This bug was fixed. | | - A bug existed such that if a process was hibernated within | the OS, it could lock up the system. This bug was fixed by not | hibernating a process until it exits the OS. | | - A bug existed such that if a process was in a timer wait state | and the system clock was set to some earlier value, the | process might not wake up for some period of time. This was | changed such that if a process specified a 'delta' time | to wait before being awakened, setting the system clock has | no effect on how long it waits. | | - The (or divide top of stack by value) | REM - provide remainder of top 2 stack elements or of top of | stack and a value | COMP - compare top 2 stack elements or compare value with top | of stack | TEST - compare top of stack to 0 | TRUNC - truncate the top of stack value | ROUND - round the top of stack | NEG - negate the top of stack | ABS - absolute value of top of stack | SIGN - signum of top of stack (-1, 0, 1) | INV - reciprocal of top of stack | SQRT - square root of top of stack | EXP - exponential of top of stack | LN - natural log of top of stack | LOG - log base 10 of top of stack | SIN - sine of top of stack | COS - cosine of top of stack | TAN - tangent of top of stack | ASIN - arcsine of top of stack | ACOS - arccosine of top of stack | ATAN - arctangent of top of stack | SINH - hyperbolic sine of top of stack | COSH - hyperbolic cosine of top of stack | TANH - hyperbolic tangent of top of stack | POW - raise a value to a power (base and power may be on | stack, or one on the stack and thties section of this | document for full description) run on them to assure that the | highest 4K byte page of user logical space is reserved. | |NOTE: The previous floating-point package (implemented with the | 1010 instruction trap) has been made into a class handler | called MATH1010.100 (.156, .150). Currently it must be | configured in at boot time in order for the utilities to | operate correctly. At a later date it will become optional. | |The following floating operations are supported: | PUSH - push a value onto the evaluation stack | POP - retrieve the value from the top of the evaluation stack | SWAP - exchange the top 2 stack elements | DUP - duplicate the top stack element | ADD - add top 2 stack elements, or add a value to the top of stack | SUB - subtract top 2 stack elements or subtract value from top | of stack (or top of stack from value) | MUL - multiply top 2 stack elements or multiply value by top | of stack | DIV - divide top 2 stack elements, or divide value by top of | stack t to be accessed by the floating point run time |routines. The floating point run time routines get linked with |the user process. The same routines will do either software |floating point emulation or, if hardware is available, will use |the 8087 floating point board. Support exists for single and |double precision IEEE format floating point and for signed and |unsigned 32 bit integers. | |NOTE: The floating point support is of little use to the end | user until the compilers are modified to use it. The | floating-point runtime routines are not part of the OS | release. They will be packaged and released with the | compilers. | |NOTE: Pascal users with files containing floating point values | will have to convert the data contained in those files | to the IEEE format. A sample conversion program will be | provided with the release of Pascal version 4.0.0 which | supports 8087 floating-point. | |NOTE: Image files created under versions of MCS earlier than 3.1 | must have the FIXSTACK utility (see Utili tained in the | appendix to this document. (Appendix #1 covers the changes to the | TTY class handler, Appendix #2 covers the changes to the disk class | handler, and Appendix #3 covers the changes to the tape class handler.) 4.2 CLASS HANDLER CHANGES 4.2.1 DISK CLASS HANDLER |The disk class handler was modified to fix some bugs and add some enhancements |as follows: | | - A bug existed such that if a directory file was renamed into itself, | the process requesting the rename would hang. It will now return an | error (number 186). | | - A bug existed such that if a file was renamed to the same name with | the same version number an error would be returned. This has been | corrected to no longer return an error. | | - Two bugs existed in the file system which could have caused shared | sectors between files. They have been fixed. | | - A bug existed such that when a read or write was requested through | the PHYSOPER SVC for n sectors it would assume a sector size of 1K, | regardless of the  issue a read-ahead request | for the next logical sector. | | - When a file is closed, it will automatically be truncated | to the physical size closest to the logical file size. This | makes possible setting the primary and secondary allocation | words such that when files are extended, they are extended | by amounts larger than one sector without wasting space. | | - File images are read in up to 4K byte requests and are placed | directly into the final memory location without having to | go through the disk cache, thus speeding image loading. | |NOTE: The changes to the interface between the disk class handler and | disk device drivers necessitate changes to any user-written disk | device drivers as well. Complete information on the changes are | provided in an addendum to this document. The same is true of the | tape class handler and tape device drivers and the tty class | handler and tty device drivers because corresponding changes were | made to them. Again, complete information is con | |NOTE: The user must run RECOVER on all winchester disk drives to | convert the FCBBITMAP to the new format. | |NOTE: This will not effect transferring floppies from systems running | 4.0 to systems running 3.0 or 3.1 as there is not enough space on | a floppy for the allocation portion of the FCBBITMAP to overlap | the bad sector portion. In transferring 3.0 or 3.1 floppies to a | 4.0 system, RECOVER should be run first to establish the bad | sector portion of the FCBBITMAP prior to using the diskette. 4. DEVICE HANDLERS AND DRIVERS 4.1 PERFORMANCE |The Disk Class handler was enhanced to improve disk performance. This |was done by making the following changes: | | - The interface between the disk class handler and the disk | device drivers was changed so the class handler can | access the disk asynchronously. | | - The disk cache management algorithm was improved to be | more efficient. | | - When the disk class handler detects that the user is reading | sequentially from the disk, it willscheduler uses 3 of the LED's on the CPU board to | represent status. | - The 1st LED blinks once per second to indicate that | the system is operational. | - The 2nd LED is lit each time a process is scheduled | and extinguished each time control is transferred back | to the scheduler. This will give some indication | of scheduling frequency. If the system is idle, the | light will be extinguished. | - The 3rd LED is lit each time the OS is entered via | TRAP 0 and extinguished each time TRAP 0 is exited. | It will give a coarse indication of how much time is | spent in the OS vs the user process. 3.8 FCBBITMAP RESTRUCTURE |The FCBBITMAP file was modified to have two parts; one for allocation, |and one for bad FCB's. It now resembles the BITMAP.SYS file in that |each record is one sector long and the sector is logically divided in |half with the 1st half representing which FCB's are currently in use |and which are available. The second half represents which FCB's are |bad.  | file will not be deleted. | | bit 3 - close forced write bit | Force any sectors written to this file onto the disk. | Any errors received are returned as warnings. | | - The edit modes for the READ and WRITE commands have been | modified. Previously the edit mode was the entire longword, | now the low word contains the edit mode number and the high | word contains the mode bits which are: | | bit 16 - reserved | | bit 17 - reserved | | bit 18 - | (On a READ command when the file was opened with the | fast-read-bit set) do not fast-read this request. | (On a WRITE command) force the write request to the media | and return any write errors immediately to the user. | Without this the user might not know whether a write | error occurred. (Note: forced write significantly increases | the amount of time it takes to write.) | | - Previously if a request was made to write more data to a disk than | there was free space available, an error was returned and no data | written. It has b| - The following OPEN mode bits have been added: | | bit 6 - fast read bit | Asynchronously read the requested data directly into | the user's memory, bypassing the cache. Restrictions: | the request must be such that all data is read into the | same 4K physical page and the destination address for the | read must be even. Only complete sectors can be read. To | insure that the read has completed, either close the file or | call trap 55 ("fast read complete" SVC - refer to SVC section | of this document for details). | | bit 7 - reserved | | bit 8 - no read ahead bit | Do not do readahead while accessing this file. | | bit 9 - no truncate file bit | Do not truncate this file back to its logical size when | the file is closed. | | - The following CLOSE mode bits have been added: | | bit 1 - no truncate file bit | Do not truncate this file back to its logical size when | the file is closed. | | bit 2 - close no delete bit | Override any delete file bits specified earlier, the  printed indicating that the cache is full of non-writeable | sectors. The message is: "WARNING -- Disk cache is full of | unwritable sectors." | 3. If a sector is unable to be written from the cache to the disk after | 128 tries, a message is printed stating that the sector is being | deleted. The message is: "WARNING -- Releasing unwritable sector | $XXXX from cache." | | - A write done by the PHYSOPER SVC will now write directly | through to the media, bypassing the cache, and returning any | errors immediately. | | - A software write-protect has been added to the disk class handler. | Currently it can be turned on and off using the new get and set | status SVC's (described in the SVC section of this document). | Coming shortly is a new DEVSTAT (device status) utility which | (among other things) allows the user to do this from CIP. Refer | to the addendum covering disk class handler changes (#2) for the | definition of the write-protect bit. | actual sector size, and transfer nK of data. This | has been fixed. | | - A bug existed such that if a user gave a read request for more data | than could fit in the space from the destination address to the top | of user space, the data read would spill over into the OS thus | overwriting it. A check has been made to prevent this from happening. | | - Warnings have been implemented in the file system. Warnings | are returned as negative status. They indicate a successful | operation, but with some kind of qualifying information which | must be returned to the user. Some warnings currently implemented | would be that the disk was improperly dismounted, device is write | protected, etc. | | - Three new diagnostic messages have been added which will appear | on the boot terminal. | | 1. Whenever an error occurs while writing out an FCB the message | "WARNING -- Mapping FCB $XXX to another FCB." will be printed. | 2. If the disk cache becomes unwriteable, a warning message is |  he TTY device drivers (TTY$100.DSR, TTY$156.DSR, and TTY$150.DSR) were |modified to allow the user to specify how many devices to poll. The number |of devices is specified by a longword at location $C. The defaults are |TTY$100.DSR = 8, TTY$156.DSR = 7, and TTY$150.DSR = 3. | |A bug existed in the TTY device drivers (TTY$100.DSR, TTY$156.DSR, and |TTY$150.DSR) such that the next tab after a form feed was given was not |expanding correctly. This has been fixed. | |Previously, bad UART's and non-existent UART's were not detected. Now they are. 4.3.3 CIPHER TAPE A cipher tape device driver was written to support the cipher tape drive on the system 100. |A bug in CIPH$100.DSR (cipher tape driver) was fixed to allow mounting |of a second cipher tape device. This was released as part of the 3.1.2 |update. 4.3.4 DEI TAPE The DEI cartridge tape device driver on the system 100 was rewritten to provide better reliability and to conform to the improved tape class handler. |The DEI1$100.DSR device driver for readinle results. This was fixed. | | 2. If a startup call to the device driver failed (example - | the device was mounted with a different name), the class | handler would call the shutdown driver command dismounting | the previously mounted device. This was fixed. 4.3 DEVICE DRIVER CHANGES 4.3.1 DISK DEVICE DRIVERS |All interrupt driven disk device drivers (for the MSC controller - |MSC$150.DSR, WD2 (piggyback) controller - WD2$150.DSR and WD2$156.DSR, |WD3 (WFC) controller - WD3$156.DSR, and the SMD controller - SMD$100.DSR) |were modified to return immediately after a request has been given. |The data will be transferred to and from the device asynchronously by |the device driver. | |The non-interrupt driven disk device drivers were modified to accomodate |the new interface between the disk class handler and drivers. The |drivers modified in this way are IMI$100.DSR, FLOP$100.DSR, MFLOP$150.DSR, |WDMF$156.DSR, MDSK$156.DSR, MDSK$100.DSR, and MRKS$100.DSR. 4.3.2 TTY DEVICE DRIVERS |Tnd labels were modified to be compatible with disk FCB's and volume labels. Tapes written with the previous tape class handler cannot be read with the new class handler. A copy of the old class handler (and device driver) is provided for reading older format tapes. To access tapes formatted under the old format, you need to modify the sysconfig file for your system so that TAPE.100 is changed to TAPE$1.100 and then reboot your system. You now have the ability to access the old format tape by using the commands with the "$1" extention (i.e. DIR$1, COPY$1, SKIP$1 and TINIT$1). To mount the tape, you use the standard MNT command but specify "DEI1$100.DSR" for the device driver. | - For the first time, a tape class handler will be released for the | 156 (TAPE.156). | | - The following bugs were fixed: | | 1. If a startup call to the device driver failed (example - | the device was already mounted), the class handler would | deallocate memory which was never allocated causing | unpredictabeen changed to write as many complete records as | fit and to return the number of records actually written. The out | of space error will occur on the next attempt to write. 4.2.2 TTY CLASS HANDLER | - A bug existed such that if a port was currently open read & write | locked and an attempt was made by another user to open that same | port read & write locked, the 2nd user would receive an error but | the port would cease to function for anyone. This has been fixed. | | - A bug existed such that if a process was waiting while reading from | or writing to a TTY device and another process tried to do a read or | write to that port with a timeout, the timeout count would not begin | until the first process had finished with the port (i.e. the process | could not timeout while waiting in the queue for the port). This has | been fixed so the timeout is in effect at all times. 4.2.3 TAPE CLASS HANDLER The tape class handler has been stream-lined. The WICAT standard file headers a econdary device, drive 0, device type A, controller 0). 5.2 ANY OPERATING SYSTEM BOOT A change has been made to the boot program so that it will not only boot the MCS operating system, but will also boot other operating systems (e.g. UNIX). This does not affect the operation of the boot program from the average users viewpoint but enables other operating systems to be run on the same system without having to alter the hardware configuration. 5.3 TAPE BOOT A tape boot program has been written for the system 100 to allow tape as the secondary boot device. This will allow booting from either a DEI cartridge tape with the new file format, or from the Cipher tape drive. 5.4 BOOTDISK PROGRAM | - The BOOTDISK program (BOOTDISK.100, BOOTDISK.156, and BOOTDISK.150) | has been modified so that the primary and secondary boot device | drivers no longer have to be the first two entries in the device | driver section of the SYSCONFIG file (SYSCONFIG.100, SYSCONFIG.156, | and SYSCONFIG.150). They may now beug existed in the Centronics driver (CENT$156.DSR and CENT$150.DSR) |such that it would not work correctly with the Prism printer (by IDS). |This has been fixed. | |There will no longer be a FLOP$150.DSR driver released for the 150. | |For the record - all disk device drivers move the heads to a "landing zone" |when the device is dismounted. The landing zone is defined differently for |each type of device. 5. BOOTS 5.1 SECONDARY BOOT DEVICE The boot program, resident in Read Only Memory, will now prompt for the name of a secondary boot device if the primary boot failed. This allows the opportunity to boot from a drive other than drive 0. There are still only 2 device drivers kept in the boot ROM's, but you can select any drive number on either device, including having it retry the primary device. To specify the appropriate device to boot from, you need to type S or P, to indicate secondary or primary device, followed by the drive number, device type, and controller number (e.g. S0A0 would boot from sb, 15Mb) at the same time on the same board. 4.3.7 MEMORY DISK A memory device driver has been written that responds like a fast disk. Files can be created and written to this device. Consider using the memory disk for temporary files, and for often used commands. To mount the memory disk, enter the command "MNT _FAST DISK MDSK$156.DSR" (or MDSK$100.DSR for system 100's). CAUTION: when the device is dismounted, or the machine is turned off, the files are lost. This driver works on either the system 100 (MDSK$100.DSR) or the multiuser (mapped) system 150 (MDSK$156.DSR). 4.3.8 IPE SUPPORT The standard terminal driver for the system 100 has been enhanced to support the IPE (Intelligent Port Expander) board. The convention for naming these extra terminal ports is _TT0A1 through _TT15A1. The Centronix Parallel port on the IPE board is referred to as device PP0B1 and uses the same driver as the TTY ports as the parallel logic is handled on the IPE board itself and not by the driver. 4.3.9 OTHERS |A bg in old format tapes had been |modified to be more robust and less subject to tape controller problems. | |There is now a device driver for the Alloy DEI tape drive on the 156 and the |system 100. The name of the driver is ADEI$156.DSR and ADEI$100.DSR |respectively. ========> NOTE: WHEN INITIALIZING AN ALLOY DEI TAPE WITH THE |UTILITY 'TINIT', YOU MUST SPECIFY A BLOCK SIZE OF 1022. <================== 4.3.5 STORAGE MODULE DRIVE CONTROLLER A driver has been provided to support interfacing to the large number of SMD compatible disk drives available. This gives the capability of adding large disk drives to the system 100 with storage capacities of 76, 152, and 414 megabytes. 4.3.6 WESTERN DIGITAL DISK CONTROLLER (multilayer) A driver is provided to support this new device which combines the winchester and floppy on the same controller. Note that the floppies on this device are device type B. (See the Device Naming Conventions described above). This driver will support multiple drive types (e.g. 10More the assignment takes place. | This problem fixed under MCS 4.0. See CIP ENHANCMENTS. * The recover program computes the size of each file and compares it with the size that is stored in the FCB. If the size does not match it prints a notice "correcting file size info for fcb ####" and corrects the size. If the file has extention FCB's, the last extention FCB will be messed up. | This problem fixed under MCS 4.0. * If you have a process that is CPU bound, it will sometimes grab all of the system resources tying up any other processes that are executing until it is done. | This problem fixed under MCS 4.0. * If a process is in a resource queue and becomes hibernated it can lock up the system as no other process can get at the queue. | This problem fixed under MCS 4.0. * Setting the system time of day clock to an earlier time after a process has initiated a timer wait SVC can cause that process to wait effectively forever as it will never be started back up again. | This probleem that has been experienced with shared sectors has been fixed. Several patches have been made to correct this but as it is a very complex problem, we are not positive that it has been corrected. | * The DIR$1 utility was changed to omit a long standing bug. After a | DIR, the tape was positioned after the logical end of tape mark. | This was changed to leave the tape just before the logical end of | tape. | | * The TCOPY utility had a number of bugs fixed. It should now work | correctly per the documentation included. 7.2 KNOWN BUGS * Changing the directory within a command file will not affect the default directory when the command file terminates. The default directory will revert to the default at the time the command file was initiated. | This problem fixed under MCS 4.0. See CIP ENHANCEMENTS. * Parameters cannot be used in logical name assignments within command files. (e.g. if you have an assignment in a command file of "ABC :== 'P1'/ROOTDIR", the 'P1' will not be translated befler.) 6.2 DISK CLASS HANDLER | Previously if a request was made to write more data to a disk than | there was free space available, an error was returned and no data | written. It has been changed to write as many complete records as | fit and to return the number of records actually written. The out | of space error will occur on the next attempt to write. 6.3 FLOATING POINT | Pascal users with files containing floating point values | will have to convert the data contained in those files | to the IEEE format. A sample conversion program will be | provided. | | Image files created under versions of MCS earlier than 3.1 | must have the FIXSTACK utility (see Utilities section of this | document for full description) run on them to assure that the | highest 4K byte page of user logical space is reserved. 6.4 FCBBITMAP | The user must run RECOVER on all winchester disk drives to | convert the FCBBITMAP to the new format. 7. NOTES 7.1 FIXES * It is believed that the probl preceeded by any number of | comment (!) lines. 5.5 SMD DISK |Boot ROMS will be supplied for the SMD disk. These were actually |supplied for the 3.1.2 update. 6. USER COMPATIBILITY PROBLEMS |(These problems have been previously discussed under their appropriate |categories and are repeated here only for ease of reference.) 6.1 PERFORMANCE | The changes to the interface between the disk class handler and | disk device drivers necessitate changes to any user-written | device drivers as well. Complete information on the changes are | prvided in an addendum to this document. The same is true of the | tape class handler and tape device drivers and the tty class | handler and tty device drivers because corresponding changes were | made to them. Again, complete information is contained in an | addendum to this document. (Addendum #1 covers the changes to the | TTY class handler, Addendum #2 covers the changes to the disk class | handler, and Addendum #3 covers the changes to the tape class hand from the factory. The following describes the procedures to be followed to back up the operating system to a secondary media (either magnetic tape or floppy) and how to re-install the operating system from the secondary media in the eventuality that your primary disk becomes corrupted or just needs to be rebuilt for some reason. 8.1 SYSTEM 100/200/160 (tape media) 8.1.1 Installation a. Insert the MCS 4.0 release tape into the tape drive and reset the system by pressing the reset button on the main CPU cabinet. b. After the system display's "booting..." on the screen, press the space bar a couple of times. c. When the system displays: Boot failed. Enter boot id (P/S, drive id): enter "S0A0" (that is S (zero) A (zero)) followed by the RETURN key. d. After the system has booted up from the tape, set the time: > STIM dd/mm/yy hh:mm:ss Where dd = the current day, mm the current month, yy the current year, hh the current hour, mm the current minute, ss the current seconcurrently | residing in cache will be lost. | | * "Shouting match": When a host system sends characters to another | system connected to one of the host's ports (as with the SEND command) | and there is no program reading those characters on the other system, | that non-host system's type-ahead buffer may fill up causing it to send | "bell" characters back to the host system. If there is no program | reading those characters on the host system, then its buffer may | fill up causing it to send "bell" characters to the non-host system, | resulting in a "shouting match" between the two systems. This can be | prevented by setting the host to HOSTSYNC and the non-host to | NOHOSTSYNC. | | * DUPDAT3: LOGFLUSH must be killed before running DUPDAT3. This is | because MCS 4.0 flushes not only disk cache, but all modified FCB's | as well. (It destroys the files DUPDAT3 asks you to delete.) 8. INSTALLATION/BACKUP INSTRUCTIONS In most cases, your system will come with the MCS 4.0 operating system already installeding physical EOT (end of tape) just as a file | is being closed. The problem shows up when the file at EOT is read. | | * COPY can not handle copying from a tape to a tape. 7.3 WARNINGS * Some of the operating system tables have changed so if you have any programs that make use of them, check the files in the directory SYSINCL.SYS to ensure that you are using the proper values. * The tape error codes have changed so if you make use of them in any of your existing programs check the file SYSINCL.SYS/SYSERR.ASM or SYSINCL.SYS/SYSERR.PAS for any changes. * Do not remove the &LOGFLUSH from the STARTUP.COM file in SYSLIB as when startup.com terminates, &LOGFLUSH must be running or else you will not be able to log on to the system. This applies to all systems, even the single user system 150. | * Write-protecting disks: Some disk drives (such as the Eagle) have | a hardware write-protect switch. This switch should not be set to | write-protect while the system is running because any data m fixed under MCS 4.0. | * Cipher controller board anomalies: | | a. The cipher controller board sometimes generates what appears to | be a spurious level four interrupt. More specifically, an | interrupt is generated and control is passed to the interrupt | routine but the interrupt pending bit in the status word is not | set (off). The interrrupt routine then assumes that it was not | its own interrupt and tries to pass control to the next interrupt | routine in the interrupt chain. | | b. On occasion a bus error is generated (DTACK did not come back). | This error occurs after a tape is mounted and some sort of tape | activity is initiated (reads or writes). | | c. On occasion the cipher drive will show an error condition in the | front panel lights and the process accessing the tape will hang | until the drive is turned off and on again at which point an error | is returned to the process. The only condition known to generate | this problem is detect 4.0 is contained on 1 BOOT diskette and 4 archive diskettes labelled VOL 1 through VOL 4. 8.2.1 Installation WARNING: When installing the MCS 4.0 backup diskettes on a system 150, all of the existing files in the directories SYSEXE, SYSLIB, SYSDSR, SYSHLP, and SYSINCL.SYS will be deleted. If you have any files in these directories that you wish to retain, you need to copy them to another directory prior to installing MCS 4.0 (e.g. LINKLIB.DEF, UAF.DAT). a. Insert the MCS 4.0 BOOT diskette into the diskette drive and reset the system by depressing the reset button under the lower right front corner of the system 150. b. After the system display's "booting..." on the screen, press the space bar a couple of times. c. When the system displays: Boot failed. Enter boot id (P/S, drive id): enter "S0A0" (that is S (zero) A (zero)) followed by the RETURN key (NOTE: IF YOU HAVE A WD3 CONTROLLER (SINGLE BOARD) THEN YOU SHOULD SPECIFY "S0B0" INSTEAD OF S0A0). d. When t the system files that are needed (see cautions/notes below), and run the RECOVER utility if you did not initialize the disk (step e above). > RECOVER k. Restart the system by typing the command: > SHUTDOWN 0 :REBOOT l. Log onto the system with the username SYSTEM. Delete the file MCSLOAD.COM in the root directory: > DEL ROOTDIR/TMCSLOAD.COM :Y m. To confirm that your MCS 4.0 installation was done correctly, type the verify report file: > TYPE SYSLIB/MCS0400.RPT NOTE: TO USE KSAM YOU MUST ALTER THE SYSTEM CONFIGURATION FILE. SEE SECTION 3.5 FOR DETAILS. 8.1.2 Backup a. Insert a blank tape to which the system is going to be backed up. Make sure it is not write protected. b. Execute the command file to backup the tape: > @SYSLIB/TMCSBKUP e.g. @SYSLIB/TMCSBKUP _TP0 CIPH$100.DSR c. Wait for the tape to completely rewind before removing from the tape drive. 8.2 SYSTEM 150/160 SERIES (diskette media) MCSi.e. FUJ121, IMI20, etc.) should be Y for an IMI drive and N for an SMD drive. is the name of the driver for your disk. The driver names would be as follows: IMI$100.DSR - IMI20 or IMI40 EAGLE.DSR - FUJ421 HAWK.DSR - FUJ152 SPARROW.DSR - FUJ76 e.g. DINIT _DI0 IMI20 MCS_4.0 Y Y 50 5000 10 Y 25 25 IMI$100.DSR f. Mount the disk with the command: > MNT DISK e.g. MNT _DI0 DISK IMI$100.DSR g. Change the default directory to the disk: > CD /ROOTDIR/ e.g. CD _DI0/ROOTDIR/ h. Copy the MCS load command file from the tape to the disk: > COPY _TP0/SYSLIB/TMCSLOAD.COM * NOTE: DEPRESS CTRL C AS SOON AS THE FILE IS COPIED AND THEN REWIND THE TAPE BY TYPING "REW _TP0" FOLLOWED BY PRESSING THE RETURN KEY. i. Execute the MCS load command file: > @TMCSLOAD e.g. @TMCSLOAD _DI0 _TP0 j. When the loading is complete, modify any ofd. NOTE: FROM THIS POINT ON, IF YOU MAKE A MISTAKE IN ENTERING A COMMAND AND GET AN ERROR MESSAGE, YOU MUST FIRST REWIND THE TAPE BY ENTERING "REW _TP0" FOLLOWED BY PRESSING THE RETURN KEY BEFORE RETRYING THE COMMAND. e. Determine whether or not you want to intialize the disk. When you initialize a disk, all files stored on the disk are DESTROYED. Make sure you have all the files you need backed up before you do the intialization. If you need help in determining whether or to initialize the disk, call Customer Software Support in Orem. If the disk needs to be initialized then enter the command: > DINIT MCS_4.0 Y 50 5000 10 Y 25 25 Where: is the name of the disk drive on your system. If you have an SMD Fujitsu drive then you would enter _DS0 otherwise if you have an IMI drive, you would enter _DI0. is the type of disk drive that you have in the system ( BECAUSE YOU MUST ALTER THE DISKETTE WITH THE CONFIG UTILITY WHEN YOU FIRST BEGIN THE MCS LOAD. IT IS SUGGESTED THAT AFTER YOU HAVE CONFIGURED THE BOOT DISKETTE TO YOUR SYSTEM AND COMPLETED THE LOAD PROCEDURE, YOU PUT A WRITE PROTECT TAB ON THE BOOT DISKETTE. l. When the loading is complete, modify any of the system files that are needed (see cautions/notes below), and run the RECOVER utility if you did not initialize the disk (step e above). > RECOVER m. Restart the system by typing the command: > SHUTDOWN 0 :REBOOT n. Log onto the system with the username SYSTEM. Delete the file MCSLOAD.COM in the root directory: > DEL ROOTDIR/MCSLOAD.COM :Y o. To confirm that the installation of MCS 4.0 was done correctly, type the verify report file: > TYPE SYSLIB/MCS0400.RPT 8.2.2 Backup There are two operations that are performed when backing up MCS on diskette. * Creating the BOOT diskette. * Creating the four archive volumes TO CREATEo the disk: > CD _DC0/ROOTDIR/ j. Copy the MCS load command file from the diskette to the disk: > COPY /SYSLIB/MCSLOAD.COM * Where: is DX0 or DX0B0. k. Execute the MCS load command file: > @MCSLOAD e.g. @MCSLOAD _DX0B0 WD3$156.DSR During the loading process, the command file will prompt for any other information needed. After loading the BOOT diskette, it will prompt you to load each volume of the archive diskettes. NOTE: AT THE BEGINNING OF THE LOAD PROCEDURE YOU WILL GET THE ERROR STATUS 133 WHEN THE SYSTEM TRIES TO FIND ERROR.TXT. THIS IS NORMAL - DO NOT BE CONCERNED ABOUT IT. NOTE: WHEN EACH VOLUME OF THE ARCHIVE DISKETTES IS MOUNTED, YOU WILL GET A WARNING MESSAGE SHOWING THE VALUE -269 IF THE DISKETTE IS WRITE PROTECTED. THIS WILL NOT INTERFERE WITH LOADING MCS. NOTE: THE BOOT DISKETTE SHOULD NOT BE WRITE PROTECTED WHEN INITIALLY USED. THIS IS =====> NOTE: IF YOU MADE CHANGES TO THE SYSTEM CONFIGURATION YOU MUST REBOOT FROM THE MCS 4.0 BOOT DISKETTE BEFORE PROCEEDING. TO REBOOT USE THE FOLLOWING PROCEDURE: 1. Dismount the floppy drive: DMNT 2. Follow steps b thru e (above) then proceed to step g, skipping step f. g. Determine whether or not you want to intialize the disk. When you initialize a disk, all files stored on the disk are DESTROYED. Make sure you have all the files you need backed up before you do the intialization. If you need help in determining whether or to initialize the disk, call Customer Software Support in Orem. If the disk needs to be initialized then enter the command: > DINIT _DC0 MCS_4.0 Y Y 40 3000 10 Y 25 25 e.g. DINIT _DC0 CMI10 MCS_4.0 Y Y 40 3000 10 Y 25 25 WD3$156.DSR h. Mount the disk with the command: > MNT _DC0 DISK e.g. MNT _DC0 DISK WD3$156.DSR i. Change the default directory the system displays "USER LOGGED OFF" log in by pressing the RETURN key. When the system prints "Username" type the following: Username: SYSTEM (return) e. After the system has booted up from the diskette, set the time: > STIM dd/mm/yy hh:mm:ss where: dd is the current day, mm is the current month, yy is the current year, hh is the current hour, mm is the current minute and ss is the current second. f. Execute the CONFIG utility to define to MCS the proper disk device driver name and the disk device size. Use the up and down arrows to position yourself to the various fields displayed on the screen. Strike the space bar to set the field to the desired value. Leave the KSAM field set to NO. This configuration sets up the diskette only. You will have the opportunity to config- ure your system winchester disk near the end of the load procedure. e.g. > CONFIG Where: is _DX0 or _DX0B0 SLIB. Under MCS 4.0, the user is always logged off after the STARTUP.COM file has finished executing (even on a single user 150) and so LOGFLUSH has to be running so that the user can log in. * In your command files: - Use :== for permanent assignments. - Redirect input to come from SYS$PROMPT on all commands that expect operator input. - Be aware that the "CD" command in a command file will change default only for commands in that command file. The system will revert to the previous default when the command is finished. | If you want the "CD" command to result in a permanent change, use | the :PERM switch on the CD command line. - Be aware that parameters on the command line will only be translated if they are enclosed in single quotes (with the exception of SYS$DISK, SYS$INPUT, etc. which are translated by the file management system, not CIP). * Ensure that the system is configured with the correct drivers and disk drive types using the CONFI of the first archive file with the command: > DIR /MCS0400/*0001.BAK e.g. > DIR _DX0B/MCS0400/*0001.BAK Given the archive file name, you can restore any file or files with the following command (all on one line): > RESTORE /MCS0400/ :DEST=_DC0/*/ Where: is _DX0 or _DX0B is the name of the file gotten from the DIR command above (eg. 05DEC0001.BAK) is the name of a file, a directory, or a list of files and directories you want to recover. (eg. SYSEXE/STAT.EXE, SYSEXE/*) is the name of the device driver for the diskette on your system (eg. WD3$156.DSR) e.g. > RESTORE _DX0B/MCS0400/05DEC0001.BAK SYSEXE/* WD3$156.DSR :DEST=_DC0/*/ The restore program will automatically prompt you to load additional volumes as neccessary to find the files. * Do not remove the &LOGFLUSH command from the STARTUP.COM file in SYKUP _DX0B WD3$156.DSR WD3 b. The command procedure will automatically prompt you to enter each diskette to be initialized and backed up. NOTE: The backup utility verifies the backed up files after each directory is dumped to diskette. When a single directory (e.g. SYSEXE) spans more than one diskette volume, backup will ask you to reinsert the previous volume (or volumes) for verification before proceeding to dump the next direc- tory. c. When the backup procedure is done, just remove the last diskette and you are finished. NOTE: ALWAYS KEEP THE ARCHIVE DISKETTES TOGETHER AS ONE UNIT. THE VOLUMES OF DIFFERENT ARCHIVE SETS ARE NOT INTERCHANGABLE. 8.3 CAUTIONS/NOTES * On a system 150, if when you type the MCS0400.RPT file and note that there are files that did not load from the diskettes properly, you can reload those files with the following procedure. First insert volume 1 of the archive diskettes and mount it with the "mf" command. List the name THE BOOT DISKETTE: ============================ a. Initiate the BOOT backup command file by typing: > @SYSLIB/MCSBOOT e.g. @SYSLIB/MCSBOOT _DX0B0 WD3$156.DSR b. After the initial files have been copied to the BOOT diskette, the configuration procedure will be started up to allow you to specify the configuration of the system that the floppies are going to be loaded on. Use the arrow keys to move around the screen and the space bar to change an entry. If there are no changes to be made then just press CTRL-A otherwise press the ESC key. c. When the backup procedure is done, remove the BOOT diskette from the floppy drive and proceed to create the archive volumes. TO CREATE THE ARCHIVE VOLUMES: ============================== a. Initiate the ARCHIVE command file by typing: > @SYSLIB/MCSBKUP Where is WD2, WD3 or MSC e.g. @SYSLIB/MCSBESS RETURN DINIT 'P1' MFLOPPY MCS_4.0_BOOT Y Y 10 20 4 Y 10 10 'P2' > MNT 'P1' DISK 'P2' > COPY SYS$DISK/ROOTDIR/*.150 'P1'/*/* > CRD 'P1'/SYSEXE/ > COPY SYS$DISK/SYSEXE/CHKD.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/CIP.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/CONFIG.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/COPY.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/CRD.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/DEL.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/DINIT.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/DIR.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/DMNT.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/DUPDAT3.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/LOGFLUSH.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/LOGON.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/MNT.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/PROMPT.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/RECOVER.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/RESTORE.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/SET.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/STIM.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/STTY.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/TIME.EXE 'P1'/*/* > COPY SYS$DISK/SYSEXE/ZAP.EXE OK, NOW ENTER THE THIRD DISK AND PRESS RETURN DINIT 'P1' MFLOPPY MCS~4.0~VOL3 Y Y 10 20 4 Y 10 10 'P2' > PROMPT OK, NOW ENTER THE FOURTH DISK AND PRESS RETURN DINIT 'P1' MFLOPPY MCS~4.0~VOL4 Y Y 10 20 4 Y 10 10 'P2' > PROMPT GOOD, REINSERT DISK 1 TO START COPY OPERATION MNT 'P1' DISK 'P2' > CRD 'P1'/MCS0400/ > BACKUP @BACK'P3' DMNT 'P1' > PROMPT MCS 4.0 DISK BUILD COMPLETE, PRESS RETURN OPTION :VERIFY !========================================================================= !MCSBOOT: Build MCS 4.0 boot diskette for unmapped system 150 !Format: @MCSBOOT !Example: @MCSBOOT _DX0B WD3$156.DSR !========================================================================= ! > OPTION :NOVERIFY > PROMPT ENTER BOOT DISKETTE AND PRe system configuration file must be altered. This file has the name SYSCONFIG.156 and resides in the ROOTDIR of the system disk. Using the VEW editor, remove the exclamation point (!) from in front of the line containing TAPE.156. Removing the exclamation point causes the tape class handler to be loaded at bootup time. The system must be rebooted after making the above change. > OPTION :VERIFY !========================================================================= !MCSBKUP: Build MCS 4.0 release diskette for unmapped system 150 !Format: @MCSBKUP !Example: @MCSBKUP _DX0 WD2$156.DSR WD2 !========================================================================= ! > OPTION :NOVERIFY > PROMPT ENTER FIRST DISK TO INITIALIZE AND PRESS RETURN DINIT 'P1' MFLOPPY MCS~4.0~VOL1 Y Y 10 20 4 Y 10 10 'P2' > PROMPT OK, NOW ENTER THE SECOND DISK AND PRESS RETURN DINIT 'P1' MFLOPPY MCS~4.0~VOL2 Y Y 10 20 4 Y 10 10 'P2' > PROMPTG program (SYSTEM 150 ONLY). Use VEW to modify ROOTDIR/SYSCONFIG.100 on a system 100. * On the mapped system 150, the system startup command file needs to be configured for a system 150-1, 150-3 or 150-6. The startup file is located in the directory SYSLIB and is named STARTUP.COM. You can change this file using the VEW editor. In the file there are three command lines that appear as follows: > !@SYS$DISK/SYSLIB/START$156 > !@SYS$DISK/SYSLIB/START$153 > !@SYS$DISK/SYSLIB/START$151 To configure the command file, remove the exclamation point (!) from in front of the line that is appropriate to your system type. * On a mapped system 150 with the old revision 2 Western Digital controller board (WD2), START$151, START$153 or START$156 needs to be modified so that MF and DF specify DX0 for the floppy drive name and WD2$156.DSR for the driver name. * NOTE: If you are using a DEU (device expansion unit) with a DEI tape unit as an accessory to your system 150, thYS$PROMPT ! !========================================================================= ! MCS V 4.0 diskette load complete !========================================================================= 24 Number of lines on the screen (line one) 80 Number of characters on a line (two) 255 Direct cursor-addressing sequence (three) YS 255 X or y first, and the displacement to add to each (four) 27 91 75 Sequence to erase to end of line (five) 27 91 74 Sequence to erase to end of screen (six) 27 77 Sequence to move text down from home position (seven) 27 Function terminator for VEW command line (eight) 20 Move cursor to top of file (nine) 5 Move cursor to end of file (ten) 16 Move cursor to next page  'P1'/SYSEXE/DIR.EXE SYS$DISK/*/* > COPY 'P1'/SYSEXE/PROMPT.EXE SYS$DISK/*/* > COPY 'P1'/SYSEXE/MNT.EXE SYS$DISK/*/* > COPY 'P1'/SYSEXE/DMNT.EXE SYS$DISK/*/* > CRD SYSDSR > DEL SYS$DISK/SYSDSR/*.*.* :Y >_NULL > COPY 'P1'/SYSDSR/'P2' SYS$DISK/SYSDSR/* > CRD SYSLIB > DEL SYS$DISK/SYSLIB/*.*.* :Y >_NULL > COPY 'P1'/SYSLIB/ERROR.TXT SYS$DISK/*/* >_NULL ^_NULL > DEL SYS$DISK/SYSHLP/*.*.* :Y >_NULL > DEL SYS$DISK/SYSINCL.SYS/*.*.* :Y >_NULL > DEL SYS$DISK/ROOTDIR/*.150 :Y >_NULL > DMNT 'P1' > PROMPT PLEASE ENTER VOLUME 1 AND PRESS RETURN MNT 'P1' DISK 'P2' > DIR 'P1'/MCS0400/*0001.BAK > PROMPT TYPE FIRST 5 CHARACTERS OF FILE NAME ABOVE P := " RESTORE 'P1'/MCS0400/'RESPONSE'0001.BAK * SYSDSR/'P2' :DEST=_DC0/*/'P' > PU SYSEXE :Y >_NULL > PU SYSLIB :Y >_NULL > PU SYSDSR :Y >_NULL > DMNT 'P1' > PROMPT PRESS RETURN TO CONFIGURE DISK CONFIG _DC0 VERIFY * SYSLIB/MCS0400.CKS SYSLIB/MCS0400.RPT > PROMPT MCS 4.0 DISK LOAD COMPLETE, PRESS RETURN OPTION :VERIFY !========================================================================= !MCSLOAD: Load MCS 4.0 from diskette for unmapped system 150 !Format: @MCSLOAD !Example: @MCSLOAD _DX0 MFLOP$156.DSR ! NOTE *** THIS COMMAND FILE WILL DELETE ALL EXISTING FILES IN THE ! FOLLOWING DIRECTORIES: SYSEXE, SYSLIB, SYSDSR, SYSHLP, ! SYSINCL.SYS, AND KSAM. IF YOU HAVE ANY FILES IN THESE ! DIRECTORIES THAT YOU WISH TO RETAIN, YOU NEED TO COPY THEM ! TO A TEMPORARY DIRECTORY. !========================================================================= ! > OPTION :NOVERIFY > P1/SYSEXE/PROMPT PRESS RETURN TO CONTINUE, CTRL-C TO ABORT CD _DC0/ROOTDIR/ > P1/SYSEXE/CRD SYSEXE > CD SYSEXE > P1/SYSEXE/DEL _DC0/SYSEXE/*.*.* :Y >_NULL > P1/SYSEXE/COPY 'P1'/SYSEXE/COPY.EXE _DC0/SYSEXE/* > SYS$DISK :== _DC0 > COPY 'P1'/SYSEXE/RESTORE.EXE SYS$DISK/*/* > COPY 'P1'/SYSEXE/CRD.EXE SYS$DISK/*/* > COPY 'P1'/SYSEXE/DEL.EXE SYS$DISK/*/* > COPY 'P1'/*/* > CRD 'P1'/SYSDSR/ > COPY SYS$DISK/SYSDSR/NULL.DSR 'P1'/*/* > COPY SYS$DISK/SYSDSR/TTY$150.DSR 'P1'/*/* > COPY SYS$DISK/SYSDSR/WD2$150.DSR 'P1'/*/* > COPY SYS$DISK/SYSDSR/MSC$150.DSR 'P1'/*/* > COPY SYS$DISK/SYSDSR/MFLOP$150.DSR 'P1'/*/* > CRD 'P1'/SYSLIB/ > COPY SYS$DISK/SYSLIB/LOGIN.COM 'P1'/*/* > COPY SYS$DISK/SYSLIB/MCSLOAD.COM 'P1'/*/* > COPY SYS$DISK/SYSLIB/SETUP252.SYS 'P1'/*/* > COPY SYS$DISK/SYSLIB/STARTUP.COM 'P1'/*/* > COPY SYS$DISK/SYSLIB/UAF.DAT 'P1'/*/* > COPY SYS$DISK/SYSLIB/USERUP.COM 'P1'/*/* > COPY SYS$DISK/SYSLIB/VEWMG8000.HLP 'P1'/*/* > PROMPT PRESS RETURN TO CONFIGURE DISKETTE CONFIG 'P1' PU 'P1'/ROOTDIR/SYSCONFIG.150 :Y >_NULL > REN 'P1'/ROOTDIR/SYSCONFIG.150.2 'P1'/ROOTDIR/SYSCONFIG.150.1 >_NULL > DMNT 'P1' > PROMPT MCS 4.0 BOOT DISK BUILD COMPLETE, PRESS RETURN !========================================================================= > ! Welcome to WICAT's Multi-user Control System (MCS). > ! > ! Turn to your MCS Introductory User Manual for tutorials that will > ! acquaint you with the capabilities of your system. > ! > ! Information on each command described in the Command Interpreter > ! Program (CIP) User Reference Manual can also be displayed on your > ! terminal screen. To find out how to do so, type HELP onto the CIP > ! command line. The CIP command line is the line at the bottom of > ! the screen where the cursor appears next to a right angle > ! bracket, >. Then type a question mark. > ! > ! However, "help displays" are intended for your use only after you > ! have read the MCS Introductory User Manual, and the CIP manual. > ! > ! Call a copy of the MCS release notice for your version of MC  ÒSYSTEM SYS$DISK/SYSLIB/ ÿÿ''SYS$INPUT SYS$OUTPUT SYS$ERROR @SYS$DISK/SYSLIB/LOGIN.COM SYS$DISK/SYSEXE/CIP.EXE [ä Ðð Àò ¢`@SYSTST ¾¹4倬 Ðí¦€¬K  ÒSYSTST SYS$DISK/SYSLIB/ ÿÿ''SYS$INPUT SYS$OUTPUT SYS$ERROR @SYS$DISK/SYSLIB/LOGIN.COM SYS$DISK/SYSEXE/CIP.EXE ======================================================== > @SYS$DISK/SYSLIB/START$150 > !===== INSERT LANGUAGE AND APPLICATION 'UP' COMMANDS BELOW THIS LINE ===== > ! > !===== INSERT LANGUAGE AND APPLICATION 'UP' COMMANDS ABOVE THIS LINE ===== > TIME > SET 0 3 > &LOGFLUSH > SEND ALL SYSTEM IS UP AND RUNNING. > LOG DEFAULT ÿÿÿÿWÈÿüJ9KgŒ |#È/9/<@Bg 9pÿ SYS$DISK/ROOTDIR/ ÿÿ'pSYS$INPUT SYS$OUTPUT SYS$ERROR @SYS$DISK/SYSLIB/LOGIN.COM SYS$DISK/SYSEXE/CIP.EXE ÓüÿÿÿZpPÙWÈÿüpÿ NÑüÿÿÿ«rPR@JWSYSTEM ÿÿÿÿ€¬ Ðí¦€¬K S$DISK/SYSLIB/VEW.HLP> !========================================================================= > ! The commands in START$150.COM make it possible for CIP > ! to communicate with the devices that constitute your > ! system. Use the VEW Command to change, or to add to, the > ! commands in this file. > !========================================================================= > MF :== 'MNT _DX0 DISK MFLOP$150.DSR' > DF :== 'DMNT _DX0' > RELEASE :== 'TYPE SYS$DISK/SYSLIB/MCS0400.RLS' > PRINTER :== _TT1 > SYS$PIPE :== SYS$DISK/SYSDSR/PIP02$150.DSR > MNT _TT1 TTYSPC SYS$DISK/SYSDSR/TTY$150.DSR > MNT _TT2 TTYSPC SYS$DISK/SYSDSR/TTY$150.DSR > STTY _TT0 TABS T7000 > STTY _TT1 TABS 1200BAUD > STTY _TT2 TABS T7000 > OPTION :VERIFY > !========================================================================= > ! STARTUP.COM is executed each time the system is booted. > ! Use the VEW Command to change, or to add to, the commands > ! in this file. > !=================ion [ESC] ab y (n cancels abortion) Save this copy of the file [ESC] sa Exit the buffer and save this copy of file [ESC] ex Rename this copy of the file [ESC] fn (then enter new file name) Insert control key function characters [ESC] ic VEW status report (toggle) [ESC] ss Insert/replace (toggle) [ESC] ir Uppercase/lowercase flag (toggle) [ESC] ul Create a CIP while you are in VEW [ESC] cp VEW Program Diagnostic Messages: The following numbers correspond to the portion of the diagnostic message that reads: ERROR NUMBER= 1 Error in reading terminal setup file 10 Line character limit exceeded 2 Error in opening source file 11 Unable to insert character 3 Unable to open .TMP files 12 Unable to create output file 4 Error in writing to MAINBEF.TMP 13 Unable to read help file 5 Error in writing to MAINAFT.TMP 14 Unable to create cut buffer, i.e., 6 Error m (use with the IC Function) Insert vertical tab, [CTRL] k (use only with the IC Function) Restore command line function [CTRL] \ Refresh screen [CTRL] - [ESC] rs Undo previous deletion [ESC] ud Cut line(s) for pasting [ESC] (n)cu (n is no. of lines) Paste line(s) [ESC] pa Move cursor up in same column Up-arrow [ESC] (-n)pl (n is no. of lines) Move cursor down in same col. Down-arrow [ESC] (n)pl (n is no. of lines) Decide and switch [ESC] (n, or -n)ds (n is a numeral) Find and switch [ESC] (n, or -n)fs (n is a numeral) Search [ESC] (n, or -n)sr (n is a numeral) Help display [ESC] he Set horizontal view [ESC] hv n (n is column number) Set page size [ESC] ps n (n is no. of lines) Abort the editing sessursor to next word [CTRL] f [ESC] (n)mw (n is no. of words) Move cursor to previous word [CTRL] r [ESC] (-n)mw (n is no. of words) Move cursor to next character Right-arrow [ESC] (n)mc (n is no. of char.) Move cursor to previous char. Left-arrow [ESC] (-n)mc (n is no. of char.) Delete line [CTRL] y [ESC] (n, or -n)dl (n is no. lines) Delete to front of line [CTRL] u [ESC] df Delete to end of line [CTRL] d [ESC] de Delete word [CTRL] s [ESC] (n)dw (n is no. of words) Delete previous word [CTRL] b [ESC] (-n)dw (n is no. of words) Delete character [CTRL] v [ESC] (n)dc (n is no. of chars) Delete previous character [DEL] [ESC] (-n)dc (n is no. of chars) Create blank line [CTRL] n [ESC] (n)ol (n is no. of lines) Insert line feed, [CTRL] j Insert form feed, [CTRL] l Insert carriage return, [CTRL]S to > ! the screen by typing RELEASE, and striking the return key, [RETURN]. > ! When the text of the notice appears on the screen, strike the no > ! scroll key, [NO SCRL], to stop temporarily the "scrolling," or > ! movement, of the text. Strike [NO SCRL] a second time to allow the > ! scrolling to continue. > !========================================================================= VEW Help Display Immediate Command Line Move cursor to top of file [CTRL] t [ESC] mt Move cursor to end of file [CTRL] e [ESC] me Move cursor to next page [CTRL] p [ESC] (n)mp (n is no. of pages) Move cursor to previous page [CTRL] q [ESC] (-n)mp (n is no. of pages) Move cursor to front of line [CTRL] a [ESC] fl Move cursor to end of line [CTRL] g [ESC] el Move cursor to next line [CTRL] o [ESC] (n)ml (n is no. of lines) Move cursor to previous line [CTRL] w [ESC] (-n)ml (n is no. of lines) Move cpage size [ESC] ps n (n is no. of lines) Abort the editing session [ESC] ab y (n cancels abortion) Save this copy of the file [ESC] sa Exit the buffer and save this copy of file [ESC] ex Rename this copy of the file [ESC] fn (then enter new file name) Insert control key function characters [ESC] ic VEW status report (toggle) [ESC] ss Insert/replace (toggle) [ESC] ir Uppercase/lowercase flag (toggle) [ESC] ul Create a CIP while you are in VEW [ESC] cp VEW Program Diagnostic Messages: The following numbers correspond to the portion of the diagnostic message that reads: ERROR NUMBER= 1 Error in reading terminal setup file 10 Line character limit exceeded 2 Error in opening source file 11 Unable to insert character 3 Unable to open .TMP files 12 Unable to create output file 4 Error in writing to MAINBEF.TMP 13 Unable to read  [CTRL] j Insert form feed, [CTRL] l Insert carriage return, [CTRL] m (use with the IC Function) Insert vertical tab, [CTRL] k (use only with the IC Function) Restore command line function [CTRL] \ Refresh screen [CTRL] - [ESC] rs Undo previous deletion [ESC] ud Cut line(s) for pasting [ESC] (n)cu (n is no. of lines) Paste line(s) [ESC] pa Move cursor up in same column Up-arrow [ESC] (-n)pl (n is no. of lines) Move cursor down in same col. Down-arrow [ESC] (n)pl (n is no. of lines) Decide and switch [ESC] (n, or -n)ds (n is a numeral) Find and switch [ESC] (n, or -n)fs (n is a numeral) Search [ESC] (n, or -n)sr (n is a numeral) Help display [ESC] he Set horizontal view [ESC] hv n (n is column number) Set . of lines) Move cursor to previous line [CTRL] w [ESC] (-n)ml (n is no. of lines) Move cursor to next word [CTRL] f [ESC] (n)mw (n is no. of words) Move cursor to previous word [CTRL] r [ESC] (-n)mw (n is no. of words) Move cursor to next character Right-arrow [ESC] (n)mc (n is no. of char.) Move cursor to previous char. Left-arrow [ESC] (-n)mc (n is no. of char.) Delete line [CTRL] y [ESC] (n, or -n)dl (n is no. lines) Delete to front of line [CTRL] u [ESC] df Delete to end of line [CTRL] d [ESC] de Delete word [CTRL] k [ESC] (n)dw (n is no. of words) Delete previous word [CTRL] b [ESC] (-n)dw (n is no. of words) Delete character [CTRL] v [ESC] (n)dc (n is no. of chars) Delete previous character [DEL] [ESC] (-n)dc (n is no. of chars) Create blank line [CTRL] n [ESC] (n)ol (n is no. of lines) Insert line feed,  in reading MAINBEF.TMP VEWCUTTXT.TMP, for the CU Function 7 Error in writing to MAINBEF.TMP after 15 Error in writing to VEWCUTTXT.TMP read 16 Error in reading VEWCUTTXT.TMP 8 Error in reading MAINAFT.TMP 17 Error in reading source file 9 Error in writing to MAINAFT.TMP after read Use the CP Function and the ERR Command to identify the MCS diagnostic message, i.e., the portion of the message that reads: STATUS=. VEW Help Display Immediate Command Line Move cursor to top of file [CTRL] t [ESC] mt Move cursor to end of file [CTRL] e [ESC] me Move cursor to next page [CTRL] p [ESC] (n)mp (n is no. of pages) Move cursor to previous page [CTRL] h [ESC] (-n)mp (n is no. of pages) Move cursor to front of line [CTRL] a [ESC] fl Move cursor to end of line [CTRL] g [ESC] el Move cursor to next line [CTRL] o [ESC] (n)ml (n is noTERED 26 KILL.EXE.1 ENTERED 27 LINK.EXE.1 ENTERED 28 LOGFLUSH.EXE.1 ENTERED 29 LOGON.EXE.1 ENTERED 30 MNT.EXE.1 ENTERED 31 MXFER.EXE.1 ENTERED 32 PATCH.EXE.1 ENTERED 33 PRELINK.EXE.1 ENTERED 34 PRINT.EXE.1 ENTERED 35 PROF.EXE.1 ENTERED 36 PROMPT.EXE.1 ENTERED 37 PROT.EXE.1 ENTERED 38 PU.EXE.1 ENTERED 39 QMGR.EXE.1 ENTERED 40 QPRT.EXE.1 ENTERED 41 RECOVER.EXE.1 ENTERED 42 REN.EXE.1 ENTERED 43 RESTORE.EXE.1 ENTERED 44 SCAN.EXE.1 ENTERED 45 SEND.EXE.1 ENTERED 46 SERIAL.EXE.1 ENTERED 47 SET.EXE.1 ENTERED 48 SETUPED.EXE.1 ENTERED 49 SHLOG.EXE.1 ENTERED 50 SHUTDOWN.EXE.1 ENTERED 51 SORT.EXE.1 ENTERED 52 SP.EXE.1 ENTERED 53 SSCOPY.EXE.1 ENTERED 54 STAT.EXE.1 ENTERED 55 STIM.EXE.1 ENTERED 56 STTY.EXE.1 ENTERED 57 SWAP.EXE.1 ENTERED 58 TALKT.EXE.1 ENTERED 59 TIME.EXE.1 ENTERED 60 TTY.EXE.1 ENTERED 61 TYPE.EXE.1 ENTERED 62 TYPEB.EXE.1 ENTERED 63 VERIFY.EXE.1 ENTERED 64 VEW.EXE.1 ENTERED 65 XFER.EXE.1 150.DSR.1 VERIFIED 3 MSC$150.DSR.1 VERIFIED 4 NULL.DSR.1 VERIFIED 5 PIP02$150.DSR.1 VERIFIED 6 PIP05$150.DSR.1 VERIFIED 7 PIP10$150.DSR.1 VERIFIED 8 RAVD$150.DSR.1 VERIFIED 9 RAVDP$150.DSR.1 VERIFIED 10 TTY$150.DSR.1 VERIFIED 11 WD2$150.DSR.1 VERIFIED _DC1/SYSEXE/ _DX0B/MCS0400/04JAN0003.BAK VOL # 1 1 ARCH.EXE.1 ENTERED 2 BACKUP.EXE.1 ENTERED 3 BTUP.EXE.1 ENTERED 4 CATALOG.EXE.1 ENTERED 5 CHECKSUM.EXE.1 ENTERED 6 CHKD.EXE.1 ENTERED 7 CIP.EXE.1 ENTERED 8 CONFIG.EXE.1 ENTERED 9 COPY.EXE.1 ENTERED 10 COUNT.EXE.1 ENTERED 11 CRD.EXE.1 ENTERED 12 CREATE.EXE.1 ENTERED 13 DEL.EXE.1 ENTERED 14 DEV.EXE.1 ENTERED 15 DINIT.EXE.1 ENTERED 16 DIR.EXE.1 ENTERED 17 DMNT.EXE.1 ENTERED 18 DUMP.EXE.1 ENTERED 19 DUPDAT3.EXE.1 ENTERED 20 DWNLD.EXE.1 ENTERED 21 DYMEM.EXE.1 ENTERED 22 ERR.EXE.1 ENTERED 23 FIXSTACK.EXE.1 ENTERED 24 GPRINT.EXE.1 ENTERED 25 INCL.EXE.1 EN _DC1/ROOTDIR/ _DX0B/MCS0400/04JAN0001.BAK VOL # 1 1 BOOTDISK.150.1 ENTERED 2 DISK.150.1 ENTERED 3 KERNEL.150.1 ENTERED 4 KERNELBUG.150.1 ENTERED 5 MATH1010.150.1 ENTERED 6 OSINIT.150.1 ENTERED 7 STARTUP.150.1 ENTERED 8 SYSCONFIG.150.1 ENTERED 9 TTY.150.1 ENTERED 1 BOOTDISK.150.1 VERIFIED 2 DISK.150.1 VERIFIED 3 KERNEL.150.1 VERIFIED 4 KERNELBUG.150.1 VERIFIED 5 MATH1010.150.1 VERIFIED 6 OSINIT.150.1 VERIFIED 7 STARTUP.150.1 VERIFIED 8 SYSCONFIG.150.1 VERIFIED 9 TTY.150.1 VERIFIED _DC1/SYSDSR/ _DX0B/MCS0400/04JAN0002.BAK VOL # 1 1 CENT$150.DSR.1 ENTERED 2 MFLOP$150.DSR.1 ENTERED 3 MSC$150.DSR.1 ENTERED 4 NULL.DSR.1 ENTERED 5 PIP02$150.DSR.1 ENTERED 6 PIP05$150.DSR.1 ENTERED 7 PIP10$150.DSR.1 ENTERED 8 RAVD$150.DSR.1 ENTERED 9 RAVDP$150.DSR.1 ENTERED 10 TTY$150.DSR.1 ENTERED 11 WD2$150.DSR.1 ENTERED 1 CENT$150.DSR.1 VERIFIED 2 MFLOP$help file 5 Error in writing to MAINAFT.TMP 14 Unable to create cut buffer, i.e., 6 Error in reading MAINBEF.TMP VEWCUTTXT.TMP, for the CU Function 7 Error in writing to MAINBEF.TMP after 15 Error in writing to VEWCUTTXT.TMP read 16 Error in reading VEWCUTTXT.TMP 8 Error in reading MAINAFT.TMP 17 Error in reading source file 9 Error in writing to MAINAFT.TMP after read Use the CP Function and the ERR Command to identify the MCS diagnostic message, i.e., the portion of the message that reads: STATUS=. ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿNTERED 34 LINK.HLP.1 ENTERED 35 LOG.HLP.1 ENTERED 36 LOGFLUSH.HLP.1 ENTERED 37 LOGON.HLP.1 ENTERED 38 MNT.HLP.1 ENTERED 39 MXFER.HLP.1 ENTERED 40 NAMES.HLP.1 ENTERED 41 OPTION.HLP.1 ENTERED 42 PATCH.HLP.1 ENTERED 43 PRELINK.HLP.1 ENTERED 44 PRINT.HLP.1 ENTERED 45 PROF.HLP.1 ENTERED 46 PROMPT.HLP.1 ENTERED 47 PROT.HLP.1 ENTERED 48 PU.HLP.1 ENTERED 49 RECOVER.HLP.1 ENTERED 50 REN.HLP.1 ENTERED 51 RESTORE.HLP.1 ENTERED 52 SCAN.HLP.1 ENTERED 53 SEND.HLP.1 ENTERED 54 SERIAL.HLP.1 ENTERED 55 SET.HLP.1 ENTERED 56 SETUPED.HLP.1 ENTERED 57 SHLOG.HLP.1 ENTERED 58 SHUTDOWN.HLP.1 ENTERED 59 SORT.HLP.1 ENTERED 60 SP.HLP.1 ENTERED 61 SSCOPY.HLP.1 ENTERED 62 STAT.HLP.1 ENTERED 63 STIM.HLP.1 ENTERED 64 STTY.HLP.1 ENTERED 65 SWAP.HLP.1 ENTERED 66 TALKT.HLP.1 ENTERED 67 TIME.HLP.1 ENTERED 68 TTY.HLP.1 ENTERED 69 TYPE.HLP.1 ENTERED 70 TYPEB.HLP.1 ENTERED 71 VERIFY.HLP.1 ENTERED 72 VERSION.HLP.1 ENTERED 73 VEW.ERIFIED 64 VEW.EXE.1 VERIFIED 65 XFER.EXE.1 VERIFIED 66 XMIT.EXE.1 VERIFIED 67 ZAP.EXE.1 VERIFIED _DC1/SYSHLP/ _DX0B/MCS0400/04JAN0004.BAK VOL # 3 1 ARCH.HLP.1 ENTERED 2 ASCII.HLP.1 ENTERED 3 ASSIGN.HLP.1 ENTERED 4 BACKUP.HLP.1 ENTERED 5 BTUP.HLP.1 ENTERED 6 CATALOG.HLP.1 ENTERED 7 CD.HLP.1 ENTERED 8 CHECKSUM.HLP.1 ENTERED 9 CHKD.HLP.1 ENTERED 10 CIP.HLP.1 ENTERED 11 CMD.HLP.1 ENTERED 12 CMDST.HLP.1 ENTERED 13 COPY.HLP.1 ENTERED 14 COUNT.HLP.1 ENTERED 15 CRD.HLP.1 ENTERED 16 CREATE.HLP.1 ENTERED 17 DEF.HLP.1 ENTERED 18 DEL.HLP.1 ENTERED 19 DEV.HLP.1 ENTERED 20 DINIT.HLP.1 ENTERED 21 DIR.HLP.1 ENTERED 22 DMNT.HLP.1 ENTERED 23 DUMP.HLP.1 ENTERED 24 DUPDAT3.HLP.1 ENTERED 25 DWNLD.HLP.1 ENTERED 26 DYMEM.HLP.1 ENTERED 27 ERR.HLP.1 ENTERED 28 FIXSTACK.HLP.1 ENTERED 29 FUNCTIONS.HLP.1 ENTERED 30 GPRINT.HLP.1 ENTERED 31 HELP.HLP.1 ENTERED 32 INCL.HLP.1 ENTERED 33 KILL.HLP.1 ER.EXE.1 VERIFIED 32 PATCH.EXE.1 VERIFIED 33 PRELINK.EXE.1 VERIFIED 34 PRINT.EXE.1 VERIFIED 35 PROF.EXE.1 VERIFIED 36 PROMPT.EXE.1 VERIFIED 37 PROT.EXE.1 VERIFIED 38 PU.EXE.1 VERIFIED 39 QMGR.EXE.1 VERIFIED 40 QPRT.EXE.1 VERIFIED 41 RECOVER.EXE.1 VERIFIED 42 REN.EXE.1 VERIFIED 43 RESTORE.EXE.1 VERIFIED 44 SCAN.EXE.1 VERIFIED 45 SEND.EXE.1 VERIFIED 46 SERIAL.EXE.1 VERIFIED 47 SET.EXE.1 VERIFIED 48 SETUPED.EXE.1 VERIFIED 49 SHLOG.EXE.1 VERIFIED 50 SHUTDOWN.EXE.1 VERIFIED 51 SORT.EXE.1 VERIFIED 52 SP.EXE.1 VERIFIED 53 SSCOPY.EXE.1 VERIFIED 54 STAT.EXE.1 VERIFIED 55 STIM.EXE.1 VERIFIED 56 STTY.EXE.1 VERIFIED 57 SWAP.EXE.1 VERIFIED 58 TALKT.EXE.1 VERIFIED 59 TIME.EXE.1 VERIFIED 60 TTY.EXE.1 VERIFIED 61 TYPE.EXE.1 VERIFIED 62 TYPEB.EXE.1 VERIFIED 63 VERIFY.EXE.1 VENTERED 66 XMIT.EXE.1 ENTERED 67 ZAP.EXE.1 ENTERED 1 ARCH.EXE.1 VERIFIED 2 BACKUP.EXE.1 VERIFIED 3 BTUP.EXE.1 VERIFIED 4 CATALOG.EXE.1 VERIFIED 5 CHECKSUM.EXE.1 VERIFIED 6 CHKD.EXE.1 VERIFIED 7 CIP.EXE.1 VERIFIED 8 CONFIG.EXE.1 VERIFIED 9 COPY.EXE.1 VERIFIED 10 COUNT.EXE.1 VERIFIED 11 CRD.EXE.1 VERIFIED 12 CREATE.EXE.1 VERIFIED 13 DEL.EXE.1 VERIFIED 14 DEV.EXE.1 VERIFIED 15 DINIT.EXE.1 VERIFIED 16 DIR.EXE.1 VERIFIED 17 DMNT.EXE.1 VERIFIED 18 DUMP.EXE.1 VERIFIED 19 DUPDAT3.EXE.1 VERIFIED 20 DWNLD.EXE.1 VERIFIED 21 DYMEM.EXE.1 VERIFIED 22 ERR.EXE.1 VERIFIED 23 FIXSTACK.EXE.1 VERIFIED 24 GPRINT.EXE.1 VERIFIED 25 INCL.EXE.1 VERIFIED 26 KILL.EXE.1 VERIFIED 27 LINK.EXE.1 VERIFIED 28 LOGFLUSH.EXE.1 VERIFIED 29 LOGON.EXE.1 VERIFIED 30 MNT.EXE.1 VERIFIED 31 MXFEERED 19 PFDDISP.ASM.1 ENTERED 20 PRCSDISP.ASM.1 ENTERED 21 PRCSDISP.PAS.1 ENTERED 22 SYNCEQU.ASM.1 ENTERED 23 SYSEQU.ASM.1 ENTERED 24 SYSERR.ASM.1 ENTERED 25 SYSERR.PAS.1 ENTERED 26 SYSTEM100.CND.1 ENTERED 27 SYSTEM150.CND.1 ENTERED 28 SYSTEM156.CND.1 ENTERED 29 TBOOTDISP.ASM.1 ENTERED 30 TFILEDISP.ASM.1 ENTERED 1 ANYOSBOOT.ASM.1 VERIFIED 2 BOOTDISP.ASM.1 VERIFIED 3 BOOTDISP.PAS.1 VERIFIED 4 CACHEDISP.ASM.1 VERIFIED 5 CLASSCMD.ASM.1 VERIFIED 6 CLOCKEQU.ASM.1 VERIFIED 7 CONTCMD.ASM.1 VERIFIED 8 DEVTDISP.ASM.1 VERIFIED 9 DEVTDISP.PAS.1 VERIFIED 10 DIRDISP.ASM.1 VERIFIED 11 DIRDISP.PAS.1 VERIFIED 12 DSTATDISP.ASM.1 VERIFIED 13 DSTATDISP.PAS.1 VERIFIED 14 FCBDISP.ASM.1 VERIFIED 15 FCBDISP.PAS.1 VERIFIED 16 FCBICDISP.ASM.1 VERIFIED 17 MATHDISP.ASM.1 VERIFIED 18 OFFSETDEF.ASM.1 VERIFIED 19 PFDDISP.ASM.1 VERIFIED 20  VERIFIED 63 STIM.HLP.1 VERIFIED 64 STTY.HLP.1 VERIFIED 65 SWAP.HLP.1 VERIFIED 66 TALKT.HLP.1 VERIFIED 67 TIME.HLP.1 VERIFIED 68 TTY.HLP.1 VERIFIED 69 TYPE.HLP.1 VERIFIED 70 TYPEB.HLP.1 VERIFIED 71 VERIFY.HLP.1 VERIFIED 72 VERSION.HLP.1 VERIFIED 73 VEW.HLP.1 VERIFIED 74 XFER.HLP.1 VERIFIED 75 XMIT.HLP.1 VERIFIED 76 ZAP.HLP.1 VERIFIED _DC1/SYSINCL.SYS/ _DX0B/MCS0400/04JAN0005.BAK VOL # 3 1 ANYOSBOOT.ASM.1 ENTERED 2 BOOTDISP.ASM.1 ENTERED 3 BOOTDISP.PAS.1 ENTERED 4 CACHEDISP.ASM.1 ENTERED 5 CLASSCMD.ASM.1 ENTERED 6 CLOCKEQU.ASM.1 ENTERED 7 CONTCMD.ASM.1 ENTERED 8 DEVTDISP.ASM.1 ENTERED 9 DEVTDISP.PAS.1 ENTERED 10 DIRDISP.ASM.1 ENTERED 11 DIRDISP.PAS.1 ENTERED 12 DSTATDISP.ASM.1 ENTERED 13 DSTATDISP.PAS.1 ENTERED 14 FCBDISP.ASM.1 ENTERED 15 FCBDISP.PAS.1 ENTERED 16 FCBICDISP.ASM.1 ENTERED 17 MATHDISP.ASM.1 ENTERED 18 OFFSETDEF.ASM.1 ENTHLP.1 VERIFIED 31 HELP.HLP.1 VERIFIED 32 INCL.HLP.1 VERIFIED 33 KILL.HLP.1 VERIFIED 34 LINK.HLP.1 VERIFIED 35 LOG.HLP.1 VERIFIED 36 LOGFLUSH.HLP.1 VERIFIED 37 LOGON.HLP.1 VERIFIED 38 MNT.HLP.1 VERIFIED 39 MXFER.HLP.1 VERIFIED 40 NAMES.HLP.1 VERIFIED 41 OPTION.HLP.1 VERIFIED 42 PATCH.HLP.1 VERIFIED 43 PRELINK.HLP.1 VERIFIED 44 PRINT.HLP.1 VERIFIED 45 PROF.HLP.1 VERIFIED 46 PROMPT.HLP.1 VERIFIED 47 PROT.HLP.1 VERIFIED 48 PU.HLP.1 VERIFIED 49 RECOVER.HLP.1 VERIFIED 50 REN.HLP.1 VERIFIED 51 RESTORE.HLP.1 VERIFIED 52 SCAN.HLP.1 VERIFIED 53 SEND.HLP.1 VERIFIED 54 SERIAL.HLP.1 VERIFIED 55 SET.HLP.1 VERIFIED 56 SETUPED.HLP.1 VERIFIED 57 SHLOG.HLP.1 VERIFIED 58 SHUTDOWN.HLP.1 VERIFIED 59 SORT.HLP.1 VERIFIED 60 SP.HLP.1 VERIFIED 61 SSCOPY.HLP.1 VERIFIED 62 STAT.HLP.1 HLP.1 ENTERED 74 XFER.HLP.1 ENTERED 75 XMIT.HLP.1 ENTERED 76 ZAP.HLP.1 ENTERED 1 ARCH.HLP.1 VERIFIED 2 ASCII.HLP.1 VERIFIED 3 ASSIGN.HLP.1 VERIFIED 4 BACKUP.HLP.1 VERIFIED 5 BTUP.HLP.1 VERIFIED 6 CATALOG.HLP.1 VERIFIED 7 CD.HLP.1 VERIFIED 8 CHECKSUM.HLP.1 VERIFIED 9 CHKD.HLP.1 VERIFIED 10 CIP.HLP.1 VERIFIED 11 CMD.HLP.1 VERIFIED 12 CMDST.HLP.1 VERIFIED 13 COPY.HLP.1 VERIFIED 14 COUNT.HLP.1 VERIFIED 15 CRD.HLP.1 VERIFIED 16 CREATE.HLP.1 VERIFIED 17 DEF.HLP.1 VERIFIED 18 DEL.HLP.1 VERIFIED 19 DEV.HLP.1 VERIFIED 20 DINIT.HLP.1 VERIFIED 21 DIR.HLP.1 VERIFIED 22 DMNT.HLP.1 VERIFIED 23 DUMP.HLP.1 VERIFIED 24 DUPDAT3.HLP.1 VERIFIED 25 DWNLD.HLP.1 VERIFIED 26 DYMEM.HLP.1 VERIFIED 27 ERR.HLP.1 VERIFIED 28 FIXSTACK.HLP.1 VERIFIED 29 FUNCTIONS.HLP.1 VERIFIED 30 GPRINT.ÿÿBACKWD2.COM.1 VERIFIED 3 ERROR.TXT.1 VERIFIED 4 LOGIN.COM.1 VERIFIED 5 MCS0400.APX.1 VERIFIED 6 MCS0400.CKS.1 VERIFIED 7 MCS0400.RLS.1 VERIFIED 8 MCSBKUP.COM.1 VERIFIED 9 MCSBOOT.COM.1 VERIFIED 10 MCSLOAD.COM.1 VERIFIED 11 SETUP252.SYS.1 VERIFIED 12 SETUP253.SYS.1 VERIFIED 13 SETUP254.SYS.1 VERIFIED 14 SETUP255.SYS.1 VERIFIED 15 START$150.COM.1 VERIFIED 16 STARTUP.COM.1 VERIFIED 17 UAF.DAT.1 VERIFIED 18 USERUP.COM.1 VERIFIED 19 VEW.HLP.1 VERIFIED 20 VEWMG8000.HLP.1 VERIFIED ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿPRCSDISP.ASM.1 VERIFIED 21 PRCSDISP.PAS.1 VERIFIED 22 SYNCEQU.ASM.1 VERIFIED 23 SYSEQU.ASM.1 VERIFIED 24 SYSERR.ASM.1 VERIFIED 25 SYSERR.PAS.1 VERIFIED 26 SYSTEM100.CND.1 VERIFIED 27 SYSTEM150.CND.1 VERIFIED 28 SYSTEM156.CND.1 VERIFIED 29 TBOOTDISP.ASM.1 VERIFIED 30 TFILEDISP.ASM.1 VERIFIED _DC1/SYSLIB/ _DX0B/MCS0400/04JAN0006.BAK VOL # 3 1 BACKMSC.COM.1 ENTERED 2 BACKWD2.COM.1 ENTERED 3 ERROR.TXT.1 ENTERED 4 LOGIN.COM.1 ENTERED 5 MCS0400.APX.1 ENTERED 6 MCS0400.CKS.1 ENTERED 7 MCS0400.RLS.1 ENTERED 8 MCSBKUP.COM.1 ENTERED 9 MCSBOOT.COM.1 ENTERED 10 MCSLOAD.COM.1 ENTERED 11 SETUP252.SYS.1 ENTERED 12 SETUP253.SYS.1 ENTERED 13 SETUP254.SYS.1 ENTERED 14 SETUP255.SYS.1 ENTERED 15 START$150.COM.1 ENTERED 16 STARTUP.COM.1 ENTERED 17 UAF.DAT.1 ENTERED 18 USERUP.COM.1 ENTERED 19 VEW.HLP.1 ENTERED 20 VEWMG8000.HLP.1 ENTERED 1 BACKMSC.COM.1 VERIFIED 2 ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿ ÿÿÿÿ!ÿÿÿÿ!ÿÿÿÿ"ÿÿÿÿ"ÿÿÿÿ#ÿÿÿÿ#ÿÿÿÿ$ÿÿÿÿ$ÿÿÿÿ%ÿÿÿÿ%ÿÿÿÿ&FCBSYSÿÿ¾%%¾%%3pãROOTDIRDIR ÿÿ¾%%¾%%0ò6FCBBITMAPSYSÿÿ¾%%¾%%2© BITMAPSYSÿÿ¾%%¾%%1h;Øþÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿüÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ-DIRFCBSYSROOTDIRDIRFCBBITMAPSYSBITMAPSYSMCS0400DIRÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ&ÿßÿÝÿÛÿÙ ÿç ÿåÿãÿáÿï ÿí ÿë ÿéMCS0400DIR ¾7¾7>u 04JAN0006BAK¾7/¾8 pni"O BACKUPLOG¾96(¾99b42x ¡ÃÄÿñ'ÿÿÿÿ'ÿÿÿÿ(ÿÿÿÿ(ÿÿÿÿ)ÿÿÿÿ)ÿÿÿÿ*ÿÿÿÿ*ÿÿÿÿ+ÿÿÿÿ+ÿÿÿÿ,ÿÿÿÿ,ÿÿÿÿ-ÿÿÿÿ-ÿÿÿÿ.ÿÿÿÿ.ÿÿÿÿ/ÿÿÿÿ/ÿÿÿÿ0ÿÿÿÿ0ÿÿÿÿ1ÿÿÿÿ1ÿÿÿÿ2ÿÿÿÿ2ÿÿÿÿ3ÿÿÿÿ3ÿÿÿÿ4ÿÿÿÿ4ÿÿÿÿ5ÿÿÿÿ5ÿÿÿÿ6ÿÿÿÿ6ÿÿÿÿ7ÿÿÿÿ7ÿÿÿÿ8ÿÿÿÿ8ÿÿÿÿ9ÿÿÿÿ9ÿÿÿÿ:ÿÿÿÿ:ÿÿÿÿ;ÿÿÿÿ;ÿÿÿÿ<ÿÿÿÿ<ÿÿÿÿ=ÿÿÿÿ=ÿÿÿÿ>ÿÿÿÿ>ÿÿÿÿ?ÿÿÿÿ?ÿÿÿÿ@ÿÿÿÿ@ÿÿÿÿAÿÿÿÿAÿÿÿÿBÿÿÿÿBÿÿÿÿCÿÿÿÿCÿÿÿÿDÿÿÿÿDÿÿÿÿEÿÿÿÿEÿÿÿÿFÿÿÿÿFÿÿÿÿGÿÿÿÿGÿÿÿÿHÿÿÿÿHÿÿÿÿIÿÿÿÿIÿÿÿÿJÿÿÿÿJÿÿÿÿKÿÿÿÿKÿÿÿÿLÿÿÿÿLÿÿÿÿ