XE500 SYSTEM LOAD UTILITY RELEASE B3.00.03/U.S.A. RELEASE TECHNICAL NOTES COPYRIGHT (C) 1980 CONVERGENT TECHNOLOGIES, INC. ALL RIGHTS RESERVED COPYRIGHT (C) 1984 BURROUGHS CORPORATION DETROIT, MICHIGAN 48232 THE WITHIN SPECIFICATION IS NOT INTENDED TO BE, NOR SHOULD SUCH BE CONSTRUED AS AN AFFIRMATION OF FACT, REPRESENTATION OR WARRANTY, BY BURROUGHS CORPORATION OF ANY TYPE, KIND, OR CHARACTER. THE WITHIN INFORMATION, AND RELATED MATERIALS ARE FURNISHED PURSUANT AND SUBJECT TO THE TERMS AND CONDITIONS OF A DULY EXECUTED LICENSE AGREEMENT. THE ONLY WARRANTIES MADE BY BURROUGHS WTIH RESPECT TO THE PRODUCTS DESCRIBED IN THIS MATERIAL ARE SET FORTH IN THE ABOVE MENTIONED AGREEMENT. BURROUGHS CORPORATION DETROIT, MICHIGAN 48232 TABLE OF CONTENTS SECTION DESCRIPTION PAGE ------- ---------------------------------- ---- 1.0 INTRODUCTION 3 2.0 DOCUMENTATION 4 3.0 SOFTWARE INSTALLATION PROCEDURE 5 4.0 REQUIRED FILES FOR INSTALLATION 9 5.0 SYSTEM LOAD UTILITY OUTPUT 14 6.0 LIMITATIONS 16 7.0 FCF REPORTING PROCEDURE 18 8.0 KNOWN PROBLEMS 20 9.0 SOFTWARE INDEX 21 XE500 SYSTEM LOAD UTILITY PAGE 3 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 1.0 INTRODUCTION The System Load Utility installs software distributed on release media to the XE500 system. The System Load Utility accepts the keyswitch position as input and displays light patterns to the front panel lights. The front panel lights are used to indicate the progress of software installation as well as to prompt the operator for specific actions. Release software may be distributed on a set of cartridges or it may be distributed on a single cartridge and a set of tapes. Loading software from a set of cartridges and loading software from tape differ somewhat in operation. Each method of software installation requires a cartridge that will boot the system and initiate the System Load Utility. Both the 'Master Operating System' release letter (CENTIX and/or BTOS) and this entire release letter should be read before proceeding to software installation. After software installation, a copy of this release letter can be found in the directory on [D1] labeled: Releasenotes.SYSLOAD.2. XE500 SYSTEM LOAD UTILITY PAGE 4 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 2.0 DOCUMENTATION 1166311 - XE520 System Administrator's Guide 1166329 - XE520 System Administrator's Handbook 1173192 - XE550 System Administrator's Guide 1173234 - XE550 System Administrator's Handbook XE500 SYSTEM LOAD UTILITY PAGE 5 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 3.0 INSTALLING SOFTWARE NOTE 1: Before attempting to use a 5 megabyte cartridge or tape drive, please refer to the 'System Administrator's Guide' for instructions on its use. NOTE 2: If a system disk is initialized manually prior to an update, instead of by the System Load Utility, then a SysImage size of at least 470 must be specified. Not doing so will result in the System Load Utility receiving a "219 - access denied" when attempting to copy SysImage.sys to disk D1. NOTE 3: Installing software: if the keyswitch is in the 'REMOTE' position, SysLoad will always initialize disk 1 (d1). If an Application Processor (AP) is in any enclosure, SysLoad will initialize disk 1 and disk 2 (D1 & D2). If disk 2 (D2) is not present but an SMD enclosure is, SysLoad will initialize disk 0 (S0) of the SMD enclosure. If an AP is present, either D2 or S0 must be online or SysLoad will fail displaying a '92' on the front panel display. If any customized files are present on either of the above disks, it is suggested that they be backed up prior to initiating software installation. (Reference the 'Master Operating System' release letter.) NOTE 4: If your software was distributed on cartridges instead of tape, the first cartridge, labeled 'Bootable Cartridge', is NOT part of software installation. Start software installation with the cartridge labeled 2 of n. 3.1 INSTALLING SOFTWARE FROM CARTRIDGES In order to begin software installation, the keyswitch should be turned to the 'STOP' position. Insert the release cartridge. If it is desirable to initialize the fixed disk before loading software, turn the keyswitch to the 'REMOTE' position, otherwise, turn the keyswitch to the 'NORMAL' position. The system will boot off of the cartridge displaying the normal sequence of lights (01 through 20). Once the utility begins to execute, the light pattern '80' will be displayed. If the keyswitch is in the 'REMOTE' position, SysLoad will display '81' and will pause, waiting for the operator to turn the keyswitch. If it is desirable to initialize the fixed disk(s) (D1 and possibly D2/S0), the keyswitch should be turned to the 'NORMAL' position. SysLoad will continue, displaying a front panel light display of '82' while initializing the disk(s). XE500 SYSTEM LOAD UTILITY PAGE 6 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 3.1 INSTALLING SOFTWARE FROM CARTRIDGES (CONT) CAUTION: DO NOT TURN THE KEYSWITCH TO THE 'STOP' POSITION WHILE AN '82' APPEARS ON THE FRONT PANEL LIGHTS (see Section 6.0, #8). Once the disk has been initialized, SysLoad will install software to the fixed disk, displaying light patterns in the range of '83' to '89'. SysLoad indicates completion by displaying a light pattern in the range of '90' to '99'. A '90' indicates that SysLoad has come to a successful completion. (For a more detailed description of front panel light displays, please see Section 5.1.) If the operator has turned the keyswitch to the 'REMOTE' position when the system was booted off of the cartridge, but has decided NOT to initialize the fixed disk, the operator may choose to terminate the current session of SysLoad. Prior to SysLoad initializing the fixed disk, a display of '81' will appear on the front panel display lights. At this point, t((he operator should turn the keyswitch to the 'MANUAL' position. This action will abort the current session of SysLoad and display a termination status of '92' on the front panel display lights. Once the termination status has been displayed, turn the keyswitch to the 'STOP' position and start again (with the same cartridge), this time turning the keyswitch to the 'NORMAL' position. If SUCCEEDING CARTRIDGES are to be loaded, with the keyswitch in the 'STOP' position insert each successive cartridge and turn the keyswitch to the 'NORMAL' position for each cartridge. The system will again boot off of each cartridge displaying light patterns in the range of 80, 83 - 90. After all cartridges have been loaded, remove the last cartridge and turn the keyswitch to the 'NORMAL' position and wait for the system to display a status of '20', normal operation. After logging in and before continuing, examine [D1]SysLoad.log for any installation failures which may have occured. A display of anything other than '90' during software installation indicates that an error has occurred and an error message has been logged in '[D1]SysLoad.log'. (An explanation of SysLoad.log can be found in Section 5.2 of this release letter.) After installation of software is complete, and your system is booted and ready for normal operation, please reference the 'Master Operating System' release letter for any additional steps that may be required to complete the installation procedure. Also, it is strongly recommended that the release media be duplicated and that the originals be placed in a safe place. For instructions on how to duplicate the release media, please reference the 'Master Operating System' release letter. XE500 SYSTEM LOAD UTILITY PAGE 7 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 3.2 INSTALLING SOFTWARE FROM TAPE In order to begin software installation, the keyswitch should be turned to the 'STOP' position. Insert the release cartridge. If it is desirable to initialize the fixed disk before loading software, turn the keyswitch to the 'REMOTE' position, otherwise, turn the keyswitch to the 'NORMAL' position. The system will boot off of the release cartridge displaying the normal sequence of lights (01 through 20). Once the utility begins to execute, the light pattern '80' will be displayed. If the keyswitch is in the 'REMOTE' position, SysLoad will display '81' and will pause waiting for the operator to turn the keyswitch. If it is desirable to initialize the fixed disk(s) (D1 and possibly D2/S0), the keyswitch should be turned to the 'NORMAL' position. SysLoad will continue, displaying a front panel light display of '82' while initializing the disk. WARNING: DO NOT TURN THE KEYSWITCH TO THE 'STOP' POSITION WHILE AN '82' APPEARS ON THE FRONT PANEL LIGHTS (see Section 6.0, #8). If the operator has turned the keyswitch to the 'REMOTE' position when the system was booted off the cartridge, but has decided NOT to initialize the fixed disk(s), the operator may choose to terminate the current session of SysLoad. Prior to SysLoad initializing the fixed disk, a display of '81' will appear on the front panel lights. At this point, the operator should turn the keyswitch to the 'MANUAL' position. This action will abort the current session of SysLoad, displaying a termination status of '92'. Once the termination status has been displayed, turn the keyswitch to the 'STOP' position and start again (with the same cartridge), this time turning the keyswitch to the 'NORMAL' position. Once the disk has been initialized (or the keyswitch has been turned to the 'NORMAL' position) SysLoad will pause, displaying an '84' to the front panel lights. This prompt indicates to the operator to load the first tape and ensure that the tape is on- line. SysLoad will load software from the tape until it encounters an end of tape mark. During this time, SysLoad will display light patterns in the range of '86' to '89'. Once SysLoad encounters the end of tape mark, SysLoad will automatically rewind and unload the tape. If a second tape is to be loaded, SysLoad will again display an '84' and will pause, waiting for the next sequential tape to become on-line. XE500 SYSTEM LOAD UTILITY PAGE 8 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 3.2 INSTALLING SOFTWARE FROM TAPE (CONT) If you load the second tape of a multi-reel tape load before the first, SysLoad will terminate displaying an '95' on the front panel lights. The error 'Multiple Tapes Out of Sequence' will be logged in Sysload.log. Once all tapes have been loaded, SysLoad will indicate completion by displaying a light pattern in the range of '90' to '99'. A '90' indicates that SysLoad has come to a successful completion. (For a more detailed description of front panel displays, please see section 5.1.) Turn the keyswitch to the 'STOP' position and remove the cartridge. Turn the keyswitch to the 'NORMAL' position and wait for the system to display a status of '20', normal operation status. After logging in and before continuing, examine [D1]SysLoad.log for any installation failures which may have occured. A display of anything other than '90' during installation indicates that an error has occurred and an error message has been logged in '[D1]SysLoad.log'. (An explanation of SysLoad.log can be found in Section 5.2 of this release letter.) After installation of software is complete, and your system is booted and ready for normal operation, please reference the 'Master Operating System' release letter for any additional steps that may be required to complete the installation procedure. Also, it is strongly recommended that the release media be duplicated and that the originals be placed in a safe place. For instructions on how to duplicate the release media, please reference the 'Master Operating System' release letter. XE500 SYSTEM LOAD UTILITY PAGE 9 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 4.0 REQUIRED FILES FOR SOFTWARE INSTALLATION 4.1.1 SYSCONTENT The SysContent file must be present on the release cartridge in order to install software. The format of an entry in this file is used to determine the type of media the release software will be loaded from. For software distributed on cartridges, an entry contains the product number followed by the product name. Each product listed has a directory containing all the files required for the product's installation. For software distributed on tape, the SysContent file contains the tape name and a list of product numbers that are present on the tape. The SysContent file must exist on a release cartridge in order to load software. If this file is not present, an error message will be logged in SysLoad.log and a '98' will be displayed on the front panel display. NOTE: The first 8 characters of an entry in the SysContent file are assumed to be the directory name of where the product resides. If you do not wish this product to be loaded, insert a special character (i.e. ":") at the beginning of the line. This causes the System Load Utility to search for a directory, with that special character, which is non-existent. For software distributed on tape, it is NOT possible to selectivly choose which products will be loaded. 4.2 PRODUCTCONTENT The ProductContent file is a required file for each product on a release cartridge. This file contains specific information in a structured format to allow the System Load Utility to successfully load the product. The format of the ProductContent file is as follows: XE500 SYSTEM LOAD UTILITY PAGE 10 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 4.2 PRODUCTCONTENT (CONT) :00:Product Name: :01:Product Number: :02:Version: :03:Language: :04:Dep((endency: :05:Create Directory: ,,, :06:File: :07:Append: :08:Submit: :09:Create File: , :10:Copyright Information: Each entry of the ProductContent file is delimited by an entry number enclosed between colons. An entry number must appear at the beginning of a line. The System Load Utility uses this number to determine the entry type. This is followed by a descriptive entry, also enclosed between colons, that describes the entry type. The descriptive entry is provided to enhance the readability of the file and is treated by the System Load Utility as comment text. Multiple line entries are considered to continue until the next entry number is encountered. Each entry is processed in the order encountered in the file. Any entry in the ProductContent file may include a comment. Text followed by the symbol '#', up to the end of a line, is considered to be comment text. Product Name, Product Number, Language, Version and Dependency entries are present for documentation purposes. Create Directory, Files, Append, Submit and Create File are all functions performed by the System Load Utility. XE500 SYSTEM LOAD UTILITY PAGE 11 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 4.2 PRODUCTCONTENT (CONT) The 'Create Directory' entry in the ProductContent file creates the specified directory, where is the directory to be created, is the protection level, is the maximun number of files and is the directory password. The System Load Utility does restrict the directory password to be the same as the volume password. This is indicated by entering '%1' for . All parameters specified, are optional and must be delimited by a comma. Where parameters are not specified, the default protection level will be 15, the default maximum number of files will be 45, and no directory password will be assigned. The 'File' entry in the ProductContent file is a list of all the files which constitute the product. It includes run files, text files and any other files that may be necessary. Each product file must begin an entry at the beginning of the line. Each entry is the full path and file name. The [volume] and portion of the filename specifies the destination of the file on the fixed disk. Some products, such as the System Load Utility, will not be loaded to the fixed disk, but only exist on the release cartridge. This is indicated to the System Load Utility by having the [volume] contain 'd0'. The 'Append' entry in the ProductContent file contains the name of the file on the fixed disk to which text will be added. The should be a full filename specification. An example of its use might be to add queue names to the Queue.Index file or to add a run statement to a jcl file. The is considered by the System Load Utility to be a single entry to be added to the file. This is necessary so that the System Load Utility is able to check for duplicate entries within the destination file. The 'Submit' entry in the ProductContent file contains BTOS commands that must be submitted to complete the installation of the product. This text will be appended to the file SysLoad.sub by the System Load Utility. The 'Create File' entry describes a file that needs to be created by the System Load Utility of a specific size. This entry may be used if a dump file is desired at software installation time. The filename and file size must be delimited by a comma. XE500 SYSTEM LOAD UTILITY PAGE 12 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 4.2 PRODUCTCONTENT (CONT) The last entry, 'CopyRight Information' is product specific information that is used when creating a release cartridge label. All entries in the ProductContent file must be numerically sequential and the range for keys are :00: to :11:. 4.3 SYSLOADPARAMS The SysLoadParams file is an optional file that contains parame- ters to be used when the fixed disk is initialized during software installation. The following example uses the default values passed to MIVolume by the System Load Utility to demonstrate the format of the SysLoadParams file: :01:MIVolume Parameters for !D1: Device,d1 Device Password,d1 Volume Name,disk1 Volume Password, Size of SysImage.sys,470 Size of LogFile,32 Size of Crash File,1600 Maximum Directories on Volume,520 Maximum Files in Volume,2000 Primary Headers only?,no Maximum Files in Sys Directory,1000 Password for Sys Directory Write protect Sys Directory Suppress format?,no Number of surface tests?,1 Debug LogFile Device Type Bad Spots,288/0/465/10 289/0/465/10 This file is input to the System Load Utility prior to the fixed disk's being initialized. The order of the entries must appear in the order described in the above example. The System Load Utility reads this file sequentially, taking the first parameter specified to be the device, the second parameter to the device password, the 18th parameter is to be device type, etc. If you wish to customize the SysLoadParams file for disk 1 in the SMD enclosure (S0), please read limitation #5 of Section 6. XE500 SYSTEM LOAD UTILITY PAGE 13 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 4.3 SYSLOADPARAMS (CONT) Each parameter to be input to the System Load Utility appears in the format , . Text up to the comma is considered comment text. The comma must appear in order for the parameter to input into the System Load Utility, otherwise, the default value for the parameter is assumed. The above example is for a volume that has a password that you want to remove. Removing the comma would maintain the current volume password. The bad spot entry in the SysLoadParams file will continue until an end of file or until a new key entry is encountered (an example of a key entry is :01:). The bad spot information contains as many bad spots that can fit into a 1024 byte array or approximately 60 bad spots, depending on the size of a bad spot entry. A comma must appear after the bad spot label in order for any bad spots to be input into the System Load Utility. All bad spots must be delimited by a single space, not a carridge return. XE500 SYSTEM LOAD UTILITY PAGE 14 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 5.0 SYSTEM LOAD UTILITY OUTPUT 5.1 FRONT PANEL DISPLAY LIGHTS The front panel display lights are used by the System Load Utility to indicate the progress of software installation. Below is a list of the light patterns displayed and the function the System Load Utility is performing: 80 Start of System Load Utility and Create SysLoad.log file. 81 Pause for MIVolume. User must turn the keyswitch to 'NORMAL' to initialize the fixed disk. 82 Initializing the fixed disk. 83 Creating the Master Configuration File. 84 Waiting for a tape to become ready. Waiting for the current tape to rewind and the next tape to become ready. 85 Unloading tape. 86 Creating the Directories listed in ProductContent. 87 Copying the system software from the release cart- ridge to the fixed disk. 88 Appending text to the appropriate file as listed in the ProductContent file. 89 Creating the files specified in ProductContent. The following displays are used to indicate that the SysLoad Utility has completed. A termination status ((of '90' indicates that software has been loaded successfully. A status light indication in the range '91' to '99' indicates that an error has occurred. The completion status lights have the following meanings, however, only the most recent error is reported in the front panel lights: 90 Successful completion. 91 Cannot create the log file. 92 MIVolume has failed. 93 Unable to create Master.cnf. 94 Cannot access open tape. 95 Tape sequence error. 96 Failed to create a directory. 97 Check the log file. One of the following errors may have occured: - a ProductContent file is missing - cannot create a specified file - cannot append BTOS commands to SysLoad.sub - a copy has failed 98 Cannot access SysContent. 99 Fatal error - keyswitch in MANUAL position. XE500 SYSTEM LOAD UTILITY PAGE 15 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 5.1 FRONT PANEL DISPLAY LIGHTS (CONT) CAUTION: If the system boots to a status of '30' with a removable cartridge in the drive, contact your local Burroughs Field Engineer. You may have a bad drive. CAUTION: If the system boots and immediately goes to a status of '99', there may be a faulty keyswitch. Retry the procedure. If you get the same failure contact you local Burroughs Field Engineer. 5.2 SYSLOAD.LOG The SysLoad.log is a file created on !D1 by the System Load Utility to report the status of software installation. If SysLoad.log is already present, then Sysload will append the current session to the end of the file. Sysload.log will also appear on the cartridge when a fixed disk is being initialized. This file contains entries that indicate the functions the System Load Utility has performed as well as log the output received from MIVolume. The purpose of this file is to report the success and failures of each software installation session. Once your software has been installed, SysLoad.log should be examined for any possible errors that might have occured during installtion. XE500 SYSTEM LOAD UTILITY PAGE 16 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 6.0 LIMITATIONS 1.) The System Load Utility only allows directory passwords that are the same as the volume password. 2.) The System Load Utility will not load software to a password protected !d2. 3.) The System Load Utility does not keep track of the amount of memory used by software placed in the Init.jcl files. Because of this the system may run out of memory on the FP or CP boards when loading excessive system services. For approximate memory requirements, please reference the 'Master Operating System' release letter. 4.) The System Load Utility requires that the MfAdminAgent and MSpoolerMgr entries must each be the last entry in whatever Init.jcl file they appear in. The Init.jcl that contains either of these entries is scanned for the strings: $run [sys]MfAdminAgent.run $run [sys]MSpoolerMgr.run Although capital and small letters are ignored, spaces are significant. Any manipulations of this entry must allow only a single space between run and [sys]. Also, if an attempt is made to append both the MfAdminAgent and MSpoolerMgr in a single Initxxyy.jcl file, the System Load Utility will not prevent the text from being added to the file. 5.) If a user wishes to initialize S0 and not D2, the SysLoadParams file must contain three (3) key entries: :01:MIVolume Parameters for !D1: . . :01:MIVolume Parameters for !d2: . . :01:MIVolume Parameters for !S0: . . XE500 SYSTEM LOAD UTILITY PAGE 17 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 6.0 LIMITATIONS (CONT) 6.) The front panel display only reflects the most recent SysLoad failure. Examine [!d1]SysLoad.log in all cases. 7.) Master.cnf is only built when software is installed (keyswitch = REMOTE). Also, the System Load Utility will not create multiple Ap entries (CENTIX systems). 8.) If MIVolume is interrupted while initializing a fixed disk (turning the keyswitch to the 'STOP' position while an '82' appears on the front panel display lights) then the badblk.sys file, which contains bad spot information, will be wiped off of the disk. If this occurs, you will need to contact your local Burroughs Support Personnel and they will inform you of the appropriate steps that need to be taken to correct the problem. XE500 SYSTEM LOAD UTILITY PAGE 18 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 7.0 FCF REPORTING PROCEDURE All software problems, software deficiencies, or suggestions for improvements should be reported by submitting a "Field Communication Form 3027057" (FCF), to your local Burroughs Support Personnel. The FCF should be reviewed for completeness and forwarded to the following address: Burroughs Corporation Product Assurance and Support PO Box 235 Downingtown, PA 19335 Attn: FCF Coordinator All information which would be helpful in understanding and analyzing the reported situation should be included with the FCF. This can be in the form of descriptions, computer listings, media containing programs and data, etc. Please include a listing of the file '[sys]Sys.Version' with ALL FCFs submitted. Certain problem situations are given below, together with appropriate information to be submitted for each. For a hang or crash condition: - a printout from MPLog or the logfile itself. - any observations of abnormal operation prior to the problem. - applicable crash files: FP - crashdump.sys, Cp - Cpxx.crash Workstation - Ws>crashdump.sys (where xx is the number of the board) - an indication of the front panel LED status code. - an indication of the LED's on the back of each board. For execution conditions: - any data necessary to demonstrate the problem. - a list of erroneous output with the errors indicated and cor- rections noted. XE500 SYSTEM LOAD UTILITY PAGE 19 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 7.0 FCF REPORTING PROCEDURE (CONT) For problems which reoccur but cannot be reproduced on demand: - a clear and detailed description of the situation. - a logfile (where applicable). - any data which may be available for this type of problem, in- cluding listings, etc. When completing the FCF, please keep the following points in mind: - Only one problem should be reported per FCF. - The FCF form is to be used for reporting system software problems, errors in documentation, or suggestions for new software features. Do not use it to ask questions or request information from Product Assurance and Support. - The information should be clear and legible as possible. - All attachments submitted with the FCF should be clearly marked with the FCF number. If you wish anything to be returned to you, including any media you may have submitted, you MUST indicate so on the FCF form and the piece of media. If you do not, your media will not be returned. XE500 SYSTEM LOAD UTILITY PAGE 20 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 8.0 KNOWN PROBLEMS 1.) During software installation, you may experience inter- mittent cycling when trying to boot from the cartridge (i.e. the front panel display lights cycle from 1 - 9 the(J n back to 1 and so on). If this occurs and upon reboot still occurs, you will need to contact your local Burroughs Support Personnel. 2.) If your system is utilizing the tape server within an SP/SC board combination, upon reboot you will receive a termination code of 33 when trying to access the tape, which means the tape server did not install. This is due to the System Load Utility not creating the appropriate InitDp00.jcl file. To correct this, edit the file [sys]InitDp00.jcl, add the following line to the file and reboot the system: $run [sys]MTapeInstall.run,8,10 XE500 SYSTEM LOAD UTILITY PAGE 21 LEVEL B3.00.03/U.S.A. - RELEASE TECHNICAL NOTES 9.0 SOFTWARE INDEX The following is a list of files which are contained on the release media and constitute the "XE500 System Load Utility" portion of the release: ProductContent [d0]Cli.run > [d0]MCreatePartition.run > [d0]MLoadPrimaryTask.run > Files from the XE520 [d0]MfAdminAgent.run > Standard BTOS portion [d0]MIVolume.run > of this release. [d0]MTapeInstall.run > [d0]MChgVolName.run > [d0]ivATASI46.cnf > [d0]ivMAXTOR53.cnf > [d0]ivMEMOREX166.cnf > [d0]SysImage.sys > [d0]CpBtos.sys > [d0]SpBtos.sys > [d0]DpBtos.sys > [d0]Centix.sys > [d0]Master.cnf > Files provided for in- [d0]Fp00.cnf > stalling this release [d0]Fp01.cnf > only. [d0]Fp02.cnf > [d0]Cp00.cnf > [d0]Cp01.cnf > [d0]Tp00.cnf > [d0]Dp00.cnf > [d0]TapeConfig.sys > [d0]InitFp00.jcl > [d0]InitSp00.jcl > [d0]InitDp00.jcl > [d0]SysLoad.run >