\ENTRY=HELPMENU,INTRO,ENTRY,HELP,ADDON The following information is available on the Turbo Update process: Introduction to Turbo Update (INTRO) TUINSTAL Optional Entry Points (ENTRY) Using the Turbo Update HELP Facility. (HELP) Updating Add-on Products (ADDON) You can enter the following chapter names shown in brackets to skip directly to that chapter: Update Preparation (PREP) Running the TUINSTAL Program (TUINSTAL) Bringing up the System (STARTUP) Creating Diagnostics (DIAG) SRB - Software Release Bulletin (SRB) Appendix A - Purchased Products being Updated (APPENDIXA) Appendix B - Accounting Structures Used (APPENDIXB) Appendix C - Error Messages and Warnings (APPENDIXC) Appendix D - The TUCOPY Program (APPENDIXD) >>>>>>>>>> The name of this screen is HELPMENU. <<<<<<<<<< For more information, enter a KEYWORD. Enter 'EXIT' or 'E' to leave help. \ITEM=INTRO Introduction to the Turbo Update Process The Turbo Update process is a simplified and faster method to update your system. It replaces the segments in the SYSTEM SL and files that have changed for both MPE and purchased subsystems. The familiar process that uses Autoinst must still be used to add a new product onto an existing system or to install a new system. However, the Turbo Update process is a alternative to the Release Installation process for updating the software on a running HP3000 system. You will need the following storage media in order to complete the entire Turbo Update process: 1. The Turbo Update tape(s) or cartridge, supplied by Hewlett- Packard. 2. One blank 2400-foot tape or one 600-foot cartridge tape for the COLDLOAD tape. 3. One blank tape for the DUS (Diagnostic Utility System) tape. (Do not reuse a current DUS tape.) 4. An optional flexible disk and blank tape to create the FLD (Fault Locating diagnostic) if using a Series 64/68/70. NOTE: Use all 2400 foot reel tapes or 600 foot cartridge tapes throughout the installation. Although the Turbo Update tape is not available on DAT, you may use DAT as your SYSDUMP and COLDLOAD media. The Turbo Update process is a very simple process that includes the following steps: 1. System preparation work including renaming the SYSSTART file, removing some UDC's, and a number of other tasks. 2. Create the HPTUINST.SYS group and restore nine files from the Turbo Update Master Tape. 3. Mount the Turbo Update Master Tape. When the tape drive is ready, run the TUINSTAL.HPTUINST.SYS program. 4. When prompted, take the Turbo Update tape off of the tape drive and mount a blank tape. 5. After the SYSDUMP tape has been written and the job that created the tape has completed, shut down the system and perform an UPDATE operation. 6. Re-enable the SYSSTART file and UDCs and restart the Data Comm and Security Monitor and allow the users back onto the system. \ITEM=ENTRY Turbo Update Update Optional Entry Points There are two optional entry points that may be used when running the Turbo Update update program (TUINSTAL.HPTUINST.SYS). The first is the HELP entry point which allows the user to access the HELP file as described below. The second is the DIAG entry point, which allows the user to create the DUS (Diagnostic Utility System) tape for Stand-alone diagnostics and the FLD (Fault Locating Diagnostics) flexible disk for S6X/7X systems. Instructions for using these optional entry points is explained below. Just enter HELP or DIAG at the HELP facility prompt (>) to access further information on these entry points. \ITEM=HELP The Turbo Update Program HELP entry point The TUINSTAL program has two ways to get HELP information. One method is to run the TUINSTAL.HPTUINST.SYS program with the HELP entry point. To do this, log onto the system as MANAGER.SYS,HPTUINST and issue the following command: :RUN TUINSTAL,HELP The program will call the MPE HELP facility using the file containing information about the Turbo Update process. When the EXIT command is issued to exit from the HELP facility, the TUINSTAL program will terminate. The second method is to enter a question mark ? anywhere the TUINSTAL program prompts the user for information. When ? is entered, the TUINSTAL program will print a few lines of information to help the user determine the correct response to the prompt. Help is available using the ? key during the installation process or when using the DIAG entry point to create the Stand-alone diagnostic media. To receive the full help text, use the HELP entry point. \ITEM=ADDON Updating Add-On Products One thing the Turbo Update process cannot be used for is to add a newly purchased product onto the system. This is because the Turbo Update tape only contains the files that have changed since Release 2P. In general, the Turbo Update tape does not have all of the files needed to install a complete product. When you purchase another subsystem, you will be asked what version of MPE V you are currently running. The subsystem software will be sent to you on a separate tape which must be installed using the AUTOINST process. If you are running MPE V Release 3P or earlier, simply run the AUTOINST program using the SUBSYS entry point (:RUN AUTOINST,SUBSYS) as documented in the HP 3000 Software Add-On manual or the HP 3000 Software Add-On Using the HPIB CDROM Drive manual. Once you have completed the Turbo Update process to update your software, your base version will always be Release 3P. Therefore, if you purchase a subsystem after doing the Turbo Update process, always specify Release 3P as the base version for the new subsystem. Once you receive the subsystem tape that contains the add-on product, you will have to use the AUTOINST process to install the subsystem. Then, when the subsystem is installed, you must perform Turbo Update update process to get the updated files and system SL segments for that product. When perform the Turbo Update process, it will update everything again because the Turbo Update program will not know that you have just added a subsystem and will therefore, just update all the subsystems on the system. However, updating all of your software again should not cause any problems. NOTE: Always perform the Turbo Update update process after installing the purchased subsystem because many purchased products also require other "dependent" products, which are installed during the subsystem installation process. The only way to guarantee that all the software has been upgraded to the latest version and is therefore compatible is to make sure the Turbo Update process is performed after installing the purchased product or subsystem. \ENTRY=PREP,VERIFY,SETUP,PASSWORDS,UDC,SECURITY Preparing to Run the Turbo Update Program The following tasks must be performed before the Turbo Update update program can be completed successfully. These items are listed below along with details on how to accomplish these checks or tasks. To access this information, just press the Enter key to display the information about the next item or enter the item name as shown in the brackets: System Version Verification (VERIFY) System Setup (SETUP) Passwords (PASSWORDS) Disable UDCs (UDC) HP Security Monitor Preparation (SECURITY) \ITEM=VERIFY System Version Verification The Turbo Update process will only work on MPE V systems that are currently running the Release 2P or later version of MPE. If you do not know what version of MPE you are currently running, use the following procedure to obtain the "RELEASE" version and match this version number against the list of Turbo Update supported versions below: 1. Ensure that the system has been properly backed up before continuing. 2. Log on and enter: :HELLO MANAGER.SYS,PUB 3. Use the SHOWME command to verify the current version of the operating system: :SHOWME The system will display a message similar to the following: USER: #S1,MANAGER.SYS,PUB (NOT IN BREAK) RELEASE: G.3P.00 MPE V HP32033 G.12.00 USER VERSION: G.3P.00 CURRENT: WED, OCT 26, 1994, 1:20 PM LOGON: MON, OCT 26, 1994, 10:29 AM CPU SECONDS: 9 CONNECT MINUTES: 75 $STDIN LDEV: 20 $STDLIST LDEV: 20 4. Match the RELEASE version highlighted above against the following list. If the version does not appear in the list, contact the Hewlett-Packard Response Center for information about getting updated to one of the versions listed below. Release 2P G.2P.00 Release 30 G.30.00 Release 31 G.31.00 Release 3P G.3P.00 \ITEM=SETUP Update Preparation Advise users in advance of the planned system down time. If you have not done a full system backup and tape verification, do so now. The installation will take from 3/4 hour to 2 1/2 hours to complete, depending on the number of SUBSYS products purchased and the type of computer and peripherals being used. NOTE: If the system segmented library (system SL) contains non-HP software, the update process will NOT remove it from the system. System Setup 1. From the console log on and enter: :HELLO MANAGER.SYS,PUB :CONSOLE 20 :LIMIT 1,1 :JOBFENCE 7 :SHOWJOB 2. Issue a warning using the WARN@ command, asking users to log off. MANAGER.SYS should be the only session logged on the system. Abort any jobs or sessions still executing. :WARN@ PLEASE LOG OFF! :ABORTJOB #Jnnn ** for jobs ** :ABORTJOB #Snnn ** for sessions ** 3. The Turbo Update process will be using the group USL.SYS. If you have files in this group that you wish to save, store the files to tape and keep the tape for archival purposes. 4. If the file SYSSTART.PUB.SYS exists on the system, rename the file and record the new name: :RENAME SYSSTART,filename 5. Enter the following command to determine if user logging processes are running: :SHOWLOGSTATUS Record the logids shown for use in both stopping the user logging process in the next step and for use in starting the user logging process when bring the system up after completing the Turbo Update process. 6. If any User Logging processes are running, terminate them as follows: :LOG logid,STOP 7. Print out or STORE off system log files in PUB.SYS for future reference, then purge the files from the system. This frees up disk space that may be needed for the installation. Enter the following commands to locate the log files: :LISTF LOG#@ :LISTF NML?#@ If you are running Release 30 (G.30.00) or later of MPE V and want to use the wildcard feature of the purge command to delete the log files, use the following commands: :PURGE LOG#@ :PURGE NML?#@ If you are on a release earlier than Release 30, you will have to use the :PURGE command specifying each file name individually: :PURGE LOG##### where ##### is the five digit number from the file name. 8. Enter the following to determine if spool files are present: :SHOWOUT SP Print or store to tape any existing spool files, and delete the files from the system. If you are using Release 31 or later of MPE you can use the following MPE and SPOOK5 commands to store all of the spool files to tape and delete the files: :RUN SPOOK5 >O;;P If you are using Release 30 or earlier of MPE, you will need to use the following MPE and SPOOK5 commands to store all of the spool files to tape: :FILE SPOOKOUT;DEV=TAPE :RUN SPOOK5 >O@.@;*SPOOKOUT >D ### where ### is the spool file number. Issue this command once for each spool file on the system. NOTE: If spool files are not deleted from the system, the space they occupy will NOT be reallocated to free space when the system is updated after the SYSDUMP job completes. 9. Disable data communication products as applicable: :DSCONTROL ldev;SHUT :MRJECONTROL SIGNOFF;hostid :MPLINE ldev,SHUT,NOW :IMFCONTROL STOP imfconfigfile :NRJECONTROL STOP;WSID=wsidname :SNACONTROL STOP;NODE=nodename;TYPE=stoptype :NSCONTROL STOP :NETCONTROL STOP NOTE: If you have DS or NRJE subsystems installed, you must now shut down the system and perform a coolstart. Make sure that no commands that perform any networking operations are entered after the system is restarted (for example, DSCONTROL, NRJECONTROL, etc.). 10. Ensure Free Space on the System Disk Turbo Update can require up to 35,000 sectors of free space on the system disk to bring in the system files from the Turbo Update tape and complete the SYSDUMP operation. Follow the steps below to ensure there is enough free space. A. Build a dummy file of 35,000 sectors, as follows: :BUILD TAKESPAC;DEV=1;DISC=35000,1,1 If there is not enough free space on the system disk, store files to tape and purge them. Other alternatives are presented in Appendix B, "Error Messages and Warnings." B. Purge the dummy file: :PURGE TAKESPAC CAUTION: If you do not ensure that there is enough free disk space, the Turbo Update process will produce a warning message displaying the minimum amount of free space you must have. Failure to ensure you have the minimum disk space required may force you into a RELOAD. \ITEM=PASSWORDS Passwords The only time a password is needed is when the TUINSTAL program streams the TUSYSDMP job to do a SYSDUMP. \ITEM=UDC Disable UDCs for MANAGER.SYS If user, account, or system level UDCs are set, the UDCs could affect the work accomplished by the Turbo Update program To make sure this does not happen, issue the following commands: :SHOWCATALOG (Record the names of the files being used) :SETCATALOG;SYSTEM (Disables System level UDCs) :SETCATALOG;ACCOUNT (Disables Account level UDCs) :SETCATALOG (Disables User level UDCs) If you do not have the HP Security Monitor product, go to the next task of running the TUINSTAL program (TUINSTAL). \ITEM=SECURITY HP Security Monitor and Preparation If you have the HP Security Monitor product on your system, follow steps 1, 2, and 3 below to set the global options, and steps 4 and 5 to suspend command disabling. 1. If the USERPASS=REQ option has been used on any of the USERs shown on the worksheet, you must change it to OPT. Do this by entering the following command: :ALTUSER username;USERPASS=OPT Be sure to note on a piece of paper which USERs have had the REQ option removed. NOTE: To determine if passwords are required for a particular user use the LISTUSER command in the LISTDIR5.PUB.SYS program. 2. If the HP Security Monitor is installed, ensure the following settings are correct before running the Turbo Update program. :RUN SECCONF.PUB.SYS 3. Respond to the prompts in the dialog as shown: HP SECURITY MONITOR HP 30392A.nn.nn (C) HEWLETT-PACKARD CO., 1986 MAIN MENU 0. Exit 1. Global Security Options 2. Device Logging and Access 3. Command Logging and Access Please enter your choice (0-3): [Enter 1] GLOBAL SECURITY OPTIONS 0. Exit to Main Menu 1. Password Encryption 2. Minimum Length for Passwords 3. Maximum Invalid Logons per Device 4. Mandatory Password Prompt 5. Idle Session Timeout 6. Generic Logon Message Option 7. UDC Failure Termination Option 8. File Open Logging Option 9. Global User Password Expiration 10. Batch Submission Security Options 11. Assurance of Auditability Option 12. File Maximum Protection Option Please enter your choice (0-12): [Enter 10] STREAM MENU 0. Exit to Global Security Menu 1. Embedded Password Disallowed Option 2. Cross Streaming Restriction Option 3. Stream Privilege Option Please enter your choice (0-3): [Enter 1] You have just selected the function to configure whether embedded passwords in job card are allowable. When this option is ON, MPE will reject any !JOB command with passwords embedded in it. EMBEDDED PASSWORD DISALLOWED is currently OFF (disabled). Please specify your new choice (ON/OFF): [Enter OFF] EMBEDDED PASSWORD DISALLOWED is now DISABLEd STREAM MENU 0. Exit to Global Security 1. Embedded Password Disallowed Option 2. Cross Streaming Restriction Option 3. Stream Privilege Option Please enter your choice (0-3): [Enter 2] You have just configured whether streaming of other people's jobs is allowable. When this option is ON, a person will not be allowed to stream another person's job unless specifically authorized. Cross Streaming Restriction is currently OFF (cross streaming is allowed). Please specify your new choice (ON/OFF):[Enter OFF] CROSS STREAM RESTRICTION is now DISABLEd STREAM MENU 0. Exit to Global Security Menu 1. Embedded Password Disallowed Option 2. Cross Streaming Restriction Option 3. Stream Privilege Option Please enter your choice (0-3): [Enter 0] GLOBAL SECURITY OPTIONS 0. Exit to Main Menu 1. Password Encryption 2. Minimum Length for Passwords 3. Maximum Invalid Logons per Device 4. Mandatory Password Prompt 5. Idle Session Timeout 6. Generic Logon Message Option 7. UDC Failure Termination Option 8. File Open Logging Option 9. Global User Password Expiration 10. Batch Submission Security Options 11. Assurance of Auditibility Option 12. File Maximum Protection Option Please enter your choice (0-12): [Enter 12] You have just selected the function to configure whether a newly created file is to be maximally protected. When this option is ON, the default access for new files will be set as (R,W,X,L,A: CR) only. MAXIMUM PROTECTION is currently OFF (disabled). Please specify your new choice (ON/OFF): [Enter OFF] MAXIMUM PROTECTION is now DISABLEd GLOBAL SECURITY OPTIONS 0. Exit to Main Menu 1. Password Encryption 2. Minimum Length for Passwords 3. Maximum Invalid Logons per Device 4. Mandatory Password Prompt 5. Idle Session Timeout 6. Generic Logon Message Option 7. UDC Failure Termination Option 8. File Open Logging Option 9. Global User Password Expiration 10. Batch Submission Security Options 11. Assurance of Auditibility Option 12. File Maximum Protection Option Please enter your choice (0-12): [Enter 0] MAIN MENU 0. Exit 1. Global Security Options 2. Device Logging and Access 3. Command Logging and Access Please enter your choice (0-3): [Enter 0] Your security configuration changes will now take effect. Thank you for using the Security Configurator. 4. Run SECCONF to display the RESET menu for HP Security Monitor: :RUN SECCONF,RESET 5. Respond to the prompts in the dialog as shown: HP SECURITY MONITOR HP30392A.nn.nn (C) HEWLETT-PACKARD CO., 1986 RESET MENU 0. Exit 1. Hard Reset 2. Soft Reset - Reset Global Options 3. Soft Reset - Reset Command Options 4. Soft Reset - Reset Device Passwords 5. Suspend - Suspend Command Disabling Please enter your choice (0-5): [Enter 5] WARNING -- This option will temporarily suspend the command disabling feature. To re-enable the function either RUN SECCONF again or restart the system. Proceed with the SUSPEND (YES/NO)? [Enter YES] Suspend - Command Disabling now Suspended. Your security configuration changes will now take effect. Thank you for using the Security Configurator. END OF PROGRAM \ENTRY=TUINSTAL,HPTUINST,RESTORE,RUNNING,UPDATE,ERRORS Running the Turbo Update Program The Turbo Update program (TUINSTAL.HPTUINST.SYS) determines which purchased subsystems exist on your system and updates MPE V, all Fundamental Operating System (FOS) products or utilities, and all purchased products that are on the system as needed. The process of using the Turbo Update Master Tape and program is designed to be very simple, and keep the amount of time your system is not available for production work to a minimum. Running the Turbo Update program is the second step in the process and will accomplish the items listed here. To display the information about the next item, press the Enter key to display each item in turn, or enter the item name as shown in the brackets: Creating the HPTUINST.SYS Group (HPTUINST) Restoring the Files (RESTORE) Running the TUINSTAL Program (RUNNING) Updating the System with the COLDLOAD Tape (UPDATE) Handling Error Conditions (ERRORS) \ITEM=HPTUINST Creating the HPTUINST.SYS Group The TUINSTAL program and associated files use the group HPTUINST.SYS. This group must be created on the system. Log onto the system as MANAGER.SYS,PUB and create the new group as follows: :HELLO MANAGER.SYS,PUB :NEWGROUP HPTUINST;CAP=PH,DS,MR,PM,IA,BA \ITEM=RESTORE Restoring Files to the HPTUINST.SYS Group To RESTORE the TUINSTAL program and associated data files, do the following: 1. On the system console, log onto the system as follows: :HELLO MANAGER.SYS,HPTUINST 2. Mount the Turbo Update tape on the tape drive or insert the Turbo Update cartridge tape into the cartridge tape drive. 3. RESTORE the eight files from the Turbo Update tape as follows: For device class TAPE drives (reel tapes & DAT tapes): :RESTORE ;;SHOW For Cartridge tape drives: :FILE TU;DEV=CTAPE :RESTORE *TU;;SHOW Nine files should be restored from the tape. These files are: TUINSTAL (TUINSTAL Program file) TUCAT000 (TUINSTAL Message Catalog file) TUHELP (TUINSTAL HELP file) TUACCT (File of needed accounting structures) TUSUBSYS (File list of purchased subsystems that have changes) TUSLINFO (File of needed SYSDUMP System Program & SL changes) TUTAPE (Program file to handle the Turbo Update Tape) TUCOPY (Program to copy the Turbo Update Master Tape) TUCATSRC (Source for TUCAT000 for language localization) 4. When the tape finishes the rewind operation after restoring the files, remount the Turbo Update Master Tape and prepare the tape drive for the next step. \ITEM=RUNNING Running the TUINSTAL Program The TUINSTAL program will: 1. Enable disk caching on ldev 1 if the disk caching product is installed on the system and caching has NOT been enabled for ldev 1. 2. Verify that all of the data files are the correct version. 3. Verify that the program is being run from the system console and that it is being run from the HPTUINST.SYS group. 4. Check to determine what purchased subsystems you have on your system that have had changes. 5. Build a SYSDUMP job file on the HPTUINST.SYS group which will make all of the changes required to the system SL (SL.PUB.SYS) for MPE, FOS (Fundamental Operating System) products or utilities, and all purchased products that are on the system. 6. RESTORE all of the files needed to update MPE, FOS (Fundamental Operating System) products or utilities, and all purchased products that are on the system. 7. STREAM the job file TUSYSDMP.HPTUINST.SYS to perform the SYSDUMP operation. NOTE: The TUINSTAL program can only be run: 1. From the system console. 2. The user must be logged on as MANAGER.SYS,HPTUINST. 3. No jobs can be running. 4. Only one session can be logged onto the system. 5. All data communications lines must be shut down. To run the program, issue the following command: :RUN TUINSTAL When the TUINSTAL program starts, it will display the following msg: TUINSTAL is determining the products to install. This will take from 1-15 minutes depending on CPU speed and products installed. After determining the products to install, TUINSTAL will ask the following questions about the tape drive to be used: Enter the Ldev or Device Class of your tape device (? for help) >> Device "x" will be used to read the Turbo Update tape. SYSDUMP will write to Ldev number "x". New Ldev? (? for help) >> Enter the Ldev number for SYSDUMP to write to "x" (? for help) >> (Where "x" is the device number or class name you entered.) To find out more about any of the questions, enter a ?. The TUINSTAL program will display three to five lines of information about the question, and ask the question again, providing another chance to answer the question. TUINSTAL will also display the following informative message: Logical device number "x" will be used later in the TUSYSDMP job. (Where "x" is the device number or class name you entered.) Once the Turbo Update Master Tape has been rewound and put off line by the program, remove the tape and mount a 2400' scratch tape or a 600' cartridge tape as appropriate. The scratch tape will be used by the TUSYSDMP job to create a COLDLOAD tape to be able to update the system SL and appropriate system programs and drivers. Unless some kind of error is detected, the only other action that is required before shutting down the system is to answer the I/O request for the tape drive from the SYSDUMP job. Once the TUSYSDMP job has completed, look for a message on the system console stating whether the job successfully completed or had problems. If the SYSDUMP job completes successfully, it will issue the following message on the system console and the spool file will be deleted. SYSDUMP job completed successfully. Shut down the system and update the system with the created UPDATE tape. If a problem is detected by the SYSDUMP job, it will issue the following message on the system console and the spool file will be left on the system for troubleshooting purposes: SYSDUMP failed. Check spool file for errors. To check the spool file for errors, use the MPE SPOOK5 utility to look at the spool file. To do this, use the following steps to look at the spool file: 1. Use the following command to run the MPE SPOOK5 utility: :RUN SPOOK5.PUB.SYS 2. Obtain the spool file number by using the SPOOK5 SHOW command: >S There should only be one spool file listed because you should have saved off and deleted any other spool files as part of the setup items to be accomplished. If, however, there are multiple spool files, the correct spool file can be identified by the job number shown on the console when the SYSDUMP job logged onto the system. Using the spool file number, use the SPOOK5 TEXT command to be able to look at the file: >T #### (where #### is the spool file number) 3. Use the SPOOK5 LIST command to look at the end of the spool file: >L L-20/L,UNN 4. Look at the listing to see what error message was issued. After determining what corrective action to take, delete the spool file by using the SPOOK5 DELETE command: >D* 5. Exit the SPOOK5 utility by using the EXIT command: >E NOTE: If there was an error message, take the appropriate action as indicated by the error message and restart the SYSDUMP job by using the MPE STREAM command: :STREAM TUSYSDMP \ITEM=UPDATE Updating the System with the UPDATE Tape 1. MPE V Shutdown Shut down the system: CONTROL-A =SHUTDOWN If the system does not halt within 60 seconds, manually halt the system as follows: On a Series 37, MICRO 3000, or MICRO 3000/XE enter: CONTROL B On all other systems enter: CONTROL B ->HALT 2. Update from the UPDATE Tape created by the Turbo Update TUSYSDMP job. For all versions of MPE, update the operating system as follows: A. Mount the FOS tape and put the tape drive online. B. Enter: ->LOAD C. Respond to the dialog as shown below. (If the DRT number given by the system for LDEV 1 differs from the value displayed, use the value from the system I/O Configuration listing.) WHICH OPTION (COLDSTART/RELOAD/UPDATE)? [Enter UPDATE] SYSTEM DISC DRT = xx(MIN=8, MAX=127)? ** S/39, 4X, 58 ** or SYSTEM DISC DRT = xx(MIN=8, MAX=511)? ** S/37, 6X, 70 ** ANY CHANGES? N **WARNING** AFTER THIS POINT DO NOT INTERRUPT THE STARTUP PROCESS UNTIL AFTER THE MESSAGE " WELCOME " APPEARS DIRECTORY MAINTENANCE COMPLETED LOADING OF SYSTEM FILES IN PROGRESS LOADING OF SYSTEM FILES COMPLETED PART 1 OF 6 COMPLETED - MEMORY RESIDENT TABLES SET UP PART 2 OF 6 COMPLETED - SL BINDING PART 3 OF 6 COMPLETED - SYSTEM I/O PROCESS CREATION PART 4 OF 6 COMPLETED - DRIVER LOADING PART 5 OF 6 COMPLETED - DISC RESIDENT TABLES SET UP PART 6 OF 6 COMPLETED - SYSTEM PROCESS CREATION BANK 0 DEPENDENT MEMORY USED -xxxxx On a Series 37 or MICRO/3000 Series system: Respond to the date prompt as requested. (If you do not respond ``Y'' or ``N'' within 60 seconds, the system by default, assumes the displayed time and date is correct.) day,date,time? (Y/N) If ``N'', respond to the prompts as indicated (use 24 hour time). On all other systems: Respond to the date prompt as requested. DATE (M,D,Y)? (mm/dd/yy) TIME (H:M)? (hh:mm - ** 24 hour format) Confirm the date and time as prompted. The system has now been fully updated. The next task is to make the system fully operational for the users. NOTE: If you have any patches that need to be applied, please refer to your Patch Installation Instructions and install them at this time. \ITEM=ERRORS Handling Error Conditions Suggestions for handling error conditions are in Appendix C. To jump to Appendix C, enter APPENDXC (without a space) or to get the cause and action text, enter TUERRxx where "xx" is the error number. \ENTRY=STARTUP,CACHING,UDC,PASSWORDS,CATALOG,RECORD,SYSSTART,RESTART, \CONTINUE,SECURITY,LOGGING,DATACOMM Getting the System Started After the Update Once the system has been updated, you will need to set up the system for normal operations. This is almost the reverse of the steps done to get ready to do the Turbo Update process. To display the information about the next item in turn, just press the Enter key or enter the item name as shown in the brackets: Start Disk Caching (CACHING) Enabling UDCs (UDC) Replace Passwords (PASSWORDS) Re-modify System Catalog File (CATALOG) Record the Installation (RECORD) Re-enable the SYSSTART File (SYSSTART) Restart the System (RESTART) Restart the Security Monitor (SECURITY) Restart User Logging Processes (LOGGING) Open the Data Communication Lines (DATACOMM) Before you get started, log onto the system as follows: :HELLO MANAGER.SYS \ITEM=CACHING To Enable disk caching, issue the following command for each disk where software caching is applicable: :STARTCACHE ldev# \ITEM=UDC Enable UDCs To enable the SYSTEM, ACCOUNT, and USER level UDCs previously disabled, use the following commands, inserting the file names as appropriate: :SETCATALOG udcfilename,udcfilename;SYSTEM (SYSTEM Level UDCs) :SETCATALOG udcfilename,udcfilename;ACCOUNT (ACCOUNT Level UDCs) :SETCATALOG udcfilename,udcfilename (USER Level UDCs) \ITEM=PASSWORDS Replace any passwords that were previously removed. If Turbo Update changed the password, the new password will be recorded at the end of the file TUSYSDMP.HPTUINST.SYS. Hewlett-Packard recommends that you set passwords for the accounts and users listed below. These accounts and users could be created or modified during the Turbo Update process as required by the products on the tape regardless of whether or not the products were on your system. Some of these accounts may not contain files after you complete the update. * CONV * HPOFFICE * HPPL85 * HPPL87 * HPPL96 * HPPL89 * ITF3000 * RJE * SUPPORT * TELESUP The following users are created or modified to have OP and/or PM capabilities. We recommend that you set passwords for these users. * MGR.HPOFFICE * FIELD.HPPL85 * FIELD.HPPL87 * FIELD.HPPL89 * MGR.TELESUP Record the passwords and keep them in a secure place. \ITEM=CATALOG If any modifications were made to the old CATALOG.PUB.SYS file, re-enter the modifications in the new file. NOTE: If you make modifications to CATALOG.PUB.SYS, you will need to create a new coldload tape with the SYSDUMP program in order to save the changes. \ITEM=RECORD Record the installation in the system logbook. \ITEM=SYSSTART Reinstate the original filename of SYSSTART as follows: :RENAME filename,SYSSTART NOTE: The commands in your SYSSTART file will only be executed when you START (Warm or Cool) or LOAD (Update, Coldload or Reload) your system. \ITEM=RESTART Restart the System At this point, the system is set up so that in most cases, if the system was shutdown and restarted, the rest of the work listed below would be automatically accomplished. It is not a requirement that the system be restarted at this point, however most of the time it is the easiest way to get everything set to a known working state. If you do not feel comfortable with shutting down the system and doing a COOLSTART, then continue with the steps below to finish preparing the system for the users. \ITEM=SECURITY Restarting the Security Monitor If you have Security Monitor, re-enable your security configuration as follows: :RUN SECCONF The program will display the MAIN MENU. Select option 0 (zero), "EXIT". You will see: Your security configuration changes will now take effect. Thank you for using the Security Configurator. END OF PROGRAM If you have Security Monitor, add the USERPASS=REQ option to any USERs which have had the option removed (refer to the worksheet). Do so by entering the following: :ALTUSER username;USERPASS=REQ \ITEM=LOGGING Restart logging processes you previously stopped as follows: :LOG logid,START \ITEM=DATACOMM Open the applicable communication lines as follows: :LIMIT n,nn ** n=jobs, nn=sessions ** :STREAMS 10 :DSCONTROL ldev;OPEN :MRJECONTROL SIGNON :MPLINE ldev,OPEN :SNACONTROL START;NODE=nodename :IMFCONTROL START imfconfigfile :NRJECONTROL START;WSID=wsidname :NETCONTROL START :NSCONTROL START :OUTFENCE n :JOBFENCE n \ENTRY=DIAG,CART,DISK2647,DISK150,DUS,FLD,FLD2647,FLD150 Creating the Stand-alone Diagnostics There are two kinds of stand-alone diagnostics that might need to be created for your system. For all systems, there should be a DUS (Diagnostic Utility System) tape created and kept available for use by Hewlett-Packard Customer Engineers. For customers who have a S/67, S/68, or S/70 system with an HP150 or an HP2647F for a system console, there should also be a FLD (Fault Locating Diagnostic) flexible disk available. Either one or both of the diagnostics media can be created using the TUINSTAL program by specifying the DIAG entry point. However, this entry point can only be used if the system is on Release 30 or greater because the TUINSTAL program uses the MPE RUN command by using the COMMAND Intrinsic. Therefore, if you are not on MPE Release 30 or later, you must perform the Turbo Update update process before creating the stand-alone diagnostic media. When the DIAG entry point is used, the TUINSTAL program will not perform any of the work needed to update MPE or any of the subsystem products. To create the stand-alone diagnostics, log onto the system as MANAGER.SYS,HPTUINST and issue the following command: :RUN TUINSTAL,DIAG When the DIAG entry point is used, the program will ask if you wish to create the DUS tape. If you do, follow the procedure listed in "Create the DUS Tape" listed below. If you do not wish to create this tape or when the DUS tape has been successfully created, the program will test to see if you are using one of the system types that needs to create the FLD (S6X/7X). If you are using one of these system types, the program will ask you if you want to create an FLD flexible disk. To create the FLD flexible disk, follow the procedure listed in the "Create the FLD Disk" below. To access this information, just press the Enter key to display the information about the next item or enter the item name as shown in brackets: Format a Cartridge Tape (CART) Format a Flexible Disk for an HP2647F (DISK2647) Format a Flexible Disk for an HP150 (DISK150) Create the DUS Tape (DUS) Create the FLD Disk (FLD) Create the FLD Disk on an HP2647F console (FLD2647) Create the FLD Disk on an HP150 console (FLD150) \ITEM=CART How to Format a Cartridge Tape To format, scratch, or serialize a cartridge tape or to perform any combination of these items, use the VINIT utility. This utility is fully documented in the MPE V System Operation and Resource Management manual (P.N. 32033-90005). Listed below, however, is the information needed to make a cartridge tape ready to be used for a scratch tape for the SYSDUMP job streamed by the Turbo Update program and to use as a tape to create a DUS tape. This procedure is best done from the system console. 1. Load the cartridge tape in the tape drive making sure the tape is write-enabled. 2. When the tape has loaded, notice the LDEV number displayed in the message on the system console. 3. Do the following MPE command: :DOWN ldev (where ldev is the ldev number obtained in step 2.) 4. Run the VINIT utility by issuing the following command: :VINIT 5. Issue the VINIT command to format the cartridge tape: >FORMAT ldev (where ldev is the ldev number obtained in step 2.) 6. Issue the VINIT command to scratch the tape: >SCRATCH ldev (where ldev is the ldev number obtained in step 2.) 7. Issue the VINIT command to mark the tape as a serial tape: >SERIAL ldev (where ldev is the ldev number obtained in step 2.) 8. Exit the VINIT utility: >EXIT (Note that the command cannot be abbreviated.) 9. Issue the following MPE command to make the tape drive accessible from the TUINSTAL program: :UP ldev where ldev is the ldev number obtained in step 2. 10. The tape must be unloaded from the drive and loaded back into the drive before it can be used by the TUINSTAL program. \ITEM=DISK2647 How to Format a Flexible Disk on an HP2647F Console. Before you attempt to create the S64/68/70 FLD program on a flexible disk using an HP2647F console, you must format the disk as follows: 1. Ensure the disk is write-enabled and insert it in the drive. 2. When the red light stops flashing on the drive, press the command key on the console keyboard. 3. Press the f8, f1, and f3 keys in sequence. The following message will be displayed: FORMAT VOLUME ON DISC# 4. Enter: 1 5. Two messages will be displayed (the second message in inverse video): ** Disc FORMAT in progress ** ** Disc VERIFY in progress ** 6. When the prompt is displayed, press the COMMAND key to terminate the process. The flexible disk is now ready to be used by the TUINSTAL program to write the FLD test program. \ITEM=DISK150 How to Format a Flexible Disk on an HP 150 Console. Before you attempt to create the S64/68/70 FLD program on a flexible disk using an HP150 console, you must format the disk as follows: 1. Ensure the disk is write-enabled and insert it in the drive. 2. Select the FORMAT option on the Personal Applications Manager (PAM) menu. Press RETURN. 3. A menu will prompt you to select Drive A or B. Type B and press RETURN. 4. You will be prompted to supply DISC LABEL. If you wish, you can type a name (perhaps for archiving purposes). This is optional, and won't interfere with creating the diagnostics. If you do not need a label, simply press RETURN. 5. Notice that the function keys now show a new set of options, Select the START FORMAT option. A message is displayed when the disk format is complete. The flexible disk is now ready to be used by the TUINSTAL program to write the FLD test program. \ITEM=DUS Create the DUS Tape The procedure for creating the DUS tape is as follows: :HELLO MANAGER.SYS,HPTUINST :RUN TUINSTAL,DIAG Do you want to make a DUS tape (Y/[N])? [Enter Y] The following message and question will appear: DUS COPY ROUTINE REVISION 1.09 ENTER MEDIA TYPE (FLOPPY DISC, CARTRIDGE TAPE, MAG TAPE): [You can enter either CART or MAG as appropriate for your system.] The following messages will appear: INSTALL SCRATCH TAPE. Reply to 'MTAPE' on the system console. Mount the tape as requested, using either a 600', 1200' or 2400' tape, or a cartridge tape and place the drive online. On the system console, issue the command: =REPLY pin,ldev where "pin" is the process identification number from the I/O Request on the system console and "ldev" is the logical device number of the tape drive where the tape was mounted. The following messages will appear: BEGIN TRANSFER OF DATA. OPENED FILE: TAPEDUS.HP32231.SUPPORT (or CARTDUS.HP32231.SUPPORT) THE DUS DATECODE IS 3303 BEGIN VERIFICATION OF DATA. END OF PROGRAM When the DUS tape is created, label the tape DUS TAPE datecode Where the datecode is the one displayed in the datecode message. \ITEM=FLD Create the FLD Disk The procedures for creating the FLD differ, depending on which terminal you are using as the system console, the HP 2647F, or the HP 150. To start the process of creating the FLD, do the following steps (you will not do the :HELLO command if you have just created the DUS tape): :HELLO MANAGER.SYS,HPTUINST :RUN TUINSTAL,DIAG Do you want to make a DUS tape (Y/[N])? [Enter N] Do you want to make an FLD disk (Y/[N])? [Enter Y] \ITEM=FLD2647 Creating Diagnostics on the HP2647F The following are instructions for creating the FLD using an HP2647F terminal as a system console. If you want to skip these instructions and go the the instructions for an HP 150, enter HP150. If you are going to create the FLD on an HP2647F, you may want to read through the dialog of the FLDCOPY program shown below. The dialog gives specific instructions. The appropriate responses are shown, highlighted in full-bright inverse video. The program FLDCOPY.HP32342.SUPPORT will then be running to create the FLD disk. The output of this program will look as follows: This utility program is intended to make copies of Fault Locating Diagnostics (binary) to HP9164-0128 flexible disc media by using the HP2647F 3000/64 System Console. Successful operation of this utility requires that the MPE Console ( ldev#20 ) be temporarily moved to another appropriately configured terminal. Perform the following operations: 1. Press: BREAK key 2. Type: CONSOLE ldev# to move System Console 3. Type: RESUME 4. Type: GO to continue The console will be switched back to ldev#20 programmatically upon successful completion of the program. TYPE 'GO' TO CONTINUE GO Pressing control Y will transfer control to a trap procedure, which switches the Console back to device 20, sets terminal echo on, and terminates the program. It should be used to abort the program when- ever possible. However, during binary data transfer, control Y is regarded as data by the system. If it is necessary to abort the program during binary read or write and control Y seems to be ignored, do the following instead: 1. press BREAK key 2. press ESC & : keys (turn on terminal echo) 3. type ABORT, CR 4. type RUN CBON, CR (enable control B) 5. type CONSOLE 20, CR (switch System Console back) . . . Do you have a permanent file (saved from previous execution of this program) you want to copy the discs from? YES What is the name of the permanent file? S64FLDS Do you want instructions to prepare the TO disc for copying? NO Press RETURN when disc is ready and inserted Do not enter anything on the keyboard until you see "Do you want to make another copy?" The values given in the example below may differ from those on your display. BEGIN WRITE (approximately 15 minutes) 3 RECORDS RECORDED, FILE 1 7 RECORDS RECORDED, FILE 2 16 RECORDS RECORDED, FILE 3 15 RECORDS RECORDED, FILE 4 14 RECORDS RECORDED, FILE 5 6 RECORDS RECORDED, FILE 6 3 RECORDS RECORDED, FILE 7 90 RECORDS RECORDED, FILE 8 121 RECORDS RECORDED, FILE 9 97 RECORDS RECORDED, FILE 10 65 RECORDS RECORDED, FILE 11 146 RECORDS RECORDED, FILE 12 10 RECORDS RECORDED, FILE 13 170 RECORDS RECORDED, FILE 14 14 FILES COPIED. WRITE COMPLETED Do you want to make another copy? * To make another copy, reply YES You will be prompted: "Do you want the instructions to prepare the TO disc for copying?" If N, the following message will be displayed, and the program will terminate. CONSOLE HAS BEEN SWITCHED FROM LDEV 21 TO LDEV 20. END OF PROGRAM * Remove the disk from the drive and label it with "FLD", the date, and the v.uu.ff number. \ITEM=FLD150 Creating Diagnostics on the HP 150 The following are the instructions for creating the FLD using an HP2647F terminal as a system console. You may want to read through the dialog of the FLDCOPY program shown below. The dialog gives specific instructions. The appropriate responses are shown, highlighted in full-bright inverse video. * Go through the dialog as shown: Terminal= 150B, Ldev= 21, MPE Console Ldev= 20 This utility program is intended to make copies of Fault Locating Diagnostics (binary) to HP92190A flexible disc media by using the HP2647F or to HP92192A micro flexible disc media by using an HP150 running the HP3000 S68 DCU to HP150 Communication Program. TYPE 'GO' TO CONTINUE GO Pressing CTRL and Y will transfer control to a trap procedure, which sets terminal echo ON and terminates the program. The CTRL-Y trap should be used to abort the program whenever pos- sible. However, during binary data transfer, CTRL-Y is regarded as data by the system. If it is necessary to abort the program during binary read or write and CTRL-Y seems to be ignored, do the following instead: 1. press BREAK (break to MPE) 2. type ESC : (turn on terminal echo) 3. type ABORT Return (abort FLDCOPY) Do you have a permanent file (saved from previous execution of this program) you want to copy the discs from? YES What is the name of the permanent file? S64FLDS Do you want the instructions to prepare the TO disc for copying? NO Press Return when disc is ready and inserted. Do not enter anything on the keyboard until you see "Do you want to make another copy?" The values given in the example below may differ from those on your display. BEGIN WRITE (approximately 15 minutes) 3 RECORDS RECORDED, FILE 1 7 RECORDS RECORDED, FILE 2 16 RECORDS RECORDED, FILE 3 15 RECORDS RECORDED, FILE 4 14 RECORDS RECORDED, FILE 5 6 RECORDS RECORDED, FILE 6 3 RECORDS RECORDED, FILE 7 90 RECORDS RECORDED, FILE 8 121 RECORDS RECORDED, FILE 9 97 RECORDS RECORDED, FILE 10 65 RECORDS RECORDED, FILE 11 146 RECORDS RECORDED, FILE 12 10 RECORDS RECORDED, FILE 13 170 RECORDS RECORDED, FILE 14 14 FILES COPIED. WRITE COMPLETED Do you want to make another copy? * To make another copy, reply YES. You will be prompted: "Do you want the instructions to prepare the TO disc for copying?" If N, the following message will be displayed, and the program will terminate. CONSOLE HAS BEEN SWITCHED FROM LDEV 21 TO LDEV 20 . END OF PROGRAM * Remove the disk from the drive and label it with "FLD", the date, and the v.uu.ff number. \ENTRY=APPENDIXA Appendix A - Purchased Products that are being Updated The following purchased products have changes on this version of the Turbo Update tape. The Turbo Update process will only update the products that exist on your system. Also, you may not recognize some of the listed products as products that you have directly purchased. This is because some of the products are "Dependent Products". Dependent Products are products that two or more regularly purchased products depend on and therefore are handled by the Turbo Update process as separate products. This allows code or information sharing by two or more products without having to maintain separate copies of the code or information for each product. The Turbo Update program (TUINSTAL.HPTUINST.SYS) tells you what products are being updated. Do not be alarmed if you do not recognize some of the products since they are probably these dependent products. Also, as a record of what subsystems were updated by the Turbo Update process, look at the file TUSWINFO.HPTUINST.SYS or in the file HPSWINFO.PUB.SYS. Following is a list of the subsystems that have changed files or system SL segments on the Turbo Update tape. They are grouped according to the MPE V Release where the product was changed. Note that all of the changes are included in the Release 40 Turbo Update tape. All of the files which were changed on Release 2P have been changed in subsequent releases, therefore, there is no reference to Release 2P in this list. --------------------------------------- PRODUCTS CHANGED ON RELEASE 40 G.40.00 DATECODE : 3532 Product Name Product # V.UU.FF --------------------------------------- Bus.BasiC Assembly ASSYBBH A.01.03 Bus.BasiC Assembly ASSYBBT A.01.02 BSTORE DATABASE BSTORE G.40.00 CS/INP DOWNLOAD HP30131 A.55.50 MPE OPERATING SYST HP32002 G.13.00 MPE OPERATING SYS HP32033 G.13.00 MODCAL 'LIB HP32047 A.00.04 RPG HP32104 A.08.10 HP BUSINESS BASIC HP32115 A.02.12 FORTRAN 77 HP32116 A.02.09 OPT/3000 HP32238 A.00.33 RAPID/INFORM HP32246 A.10.00 RAPID/TRANSACT HP32247 A.10.02 Transact RAPID0 A.10.02 Transact RAPID1 A.10.02 --------------------------------------- PRODUCTS CHANGED ON RELEASE 3P G.3P.00 DATECODE : 3419 Product Name Product # V.UU.FF --------------------------------------- IMF/3000 SNA IMF DCSIMF A.53.13A DS COMMON MODULES DSCOMMON B.56.09B ERROR MSG. HELP EXPLAIN A.01.01 FORMATTER GROUP FMT A.01.23A HP SRC/V HP30234 A.01.20 DSN/SNA NRJE HP30245 A.70.06B SNA IMF HP30247 A.53.13A IMF/3000 HP30250 A.53.13 DS NETWORK SERVICE HP32185 B.56.09D X.25 NETWORK LINK HP32187 B.56.09B EDITOR HP32201 A.09.00 KSAM INTRINSICS HP32208 A.05.12B FCOPY HP32212 A.05.03 SORT/MERGE HP32214 C.05.11B HPIB DIAG.(DUS) HP32231 3303B ON LINE DIAGNOSTIC HP32340 2719B NETWORK TRANSPORT HP32343 A.01.23G NS/3000 HP32344 A.00.16A HP NETDELIVERY/V HP32346 A.02.06A NLS/3000 HP32414 A.03.09B HP BRW/V HP36070 A.02.83 HP GLANCE/V HP50733 B.01.02B HP PREDICTIVE HP51467 A.02.07 NODE MGMT.SERVICES NMS A.01.23 NS CORE NSC A.00.16A NSPAD SERVICE NSPAD A.00.16A HPDesk Components NWOMAIL A.04.00 RPM RPM A.00.16A VT ONLY VTO A.00.16A X.25 PROTOCOL MDL X25PM A.01.23B --------------------------------------- PRODUCTS CHANGED ON RELEASE 31 G.31.00 DATECODE : 3330 Product Name Product # V.UU.FF --------------------------------------- Information Access ACCESSV A.06.05 NWO (Access) B1726B A.06.05 Perf Collector V B1793B B.00.04 CCSY ACCESS SVR B3161A A.06.05 TurboSTORE HP30167 A.00.14 MPE SEGMENTER HP32050 A.03.11 BASIC HP32101 B.00.24A PASCAL HP32106 A.01.32 HPLISTKEEPER HP32132 A.03.23 ADCC HP32196 G.51.51 VPLUS/3000 HP32209 B.06.05 TURBO IMAGE HP32215 C.01.01 RAPID/PROCESSOR HP32249 A.09.02 HI-LI HP32424 A.00.11 HP BRW-DESK/V HP35365 A.00.03 HPSLATE HP36576 A.05.03 TDP HP36578 A.05.05 INP DOWNLOAD INPDLL A.02.42 INP DRIVER IOINP A.55.42 INP DRIVER IOINP1 A.55.42 LINK SUPPORT LSS B.02.23A RAPID2 RAPID2 A.09.02 --------------------------------------- PRODUCTS CHANGED ON RELEASE 30 G.30.00 DATECODE : 3248 Product Name Product # V.UU.FF --------------------------------------- HPDESKOMGATE HP27567 A.00.04 COMPILER LIB HP32211 D.01.11 QUERY HP32216 C.02.22 COBOL LIB HP32232 A.03.04 COBOL II HP32233 A.02.05 HP-COLOSSUS HP35074 A.00.06 DBCHANGE HP36020 A.01.03 \ENTRY=APPENDIXB Appendix B - Accounting Structures Used Following is a list of accounts and groups that may have been created on your systems, or if they already existed, the capabilities and/or access specifications may have been altered to HP specifications. These accounts and/or groups will be created and/or modified even though you do not have any products that use these accounting structures. ACCOUNT GROUP ------- -------- HPPL85 HP36576 HP36578 HPPL87 HP30245 HPPL89 HP32115 ITF3000 BRWEXEC BRWONLNE BRWSPEC SUPPORT HP32033 HP32231 HP32340 HP32342 SYS APPC CONVALL HPMMGR HPSRC NET NRJE PPC SCOPE USL TELESUP HP51467 HPSUP PRV \ENTRY=APPENDIXC Appendix C - Error Messages and Warnings This appendix contains the error messages that could be displayed by the TUINSTAL program along with the cause of the error along with a suggested course of action to be take in order to correct the problem. \ENTRY=TUERR1 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 1) \ENTRY=TUERR2 MESSAGE Error reading message catalog. TUINSTAL Terminating (TUERR 2) CAUSE An I/O error occurred while trying to read the message catalog (TUCAT000.HPTUINST.SYS) for the TUINSTAL program. ACTION Restore the file from the Turbo Update Master tape and try the TUINSTAL program again. \ENTRY=TUERR3 MESSAGE File TUCAT000 is not a GENCAT formatted file. (TUERR 3) CAUSE The file TUCAT000.HPTUINST.SYS has been replaced with a file that is not an NLS (Native Language Support) formatted message catalog file. ACTION Restore the file from the Turbo Update Master tape and try the TUINSTAL program again. \ENTRY=TUERR4 MESSAGE Cannot open localized TUINSTAL message catalog. (TUWARN 4) CAUSE An NLS (Native Language Support) language other than default (0) is configured on the system as the default language and a corresponding localized language message catalog file (TUCATxxx.HPTUINST.SYS where xxx = the default configured language) does not exist. ACTION No specific action is required. The TUINSTAL program will try to open the default message catalog file TUCAT000. \ENTRY=TUERR5 MESSAGE Cannot open TUCAT000, TUINSTAL terminating. (TUERR 5) CAUSE The TUINSTAL program message catalog file TUCAT000.HPTUINST. SYS does not exist. ACTION Restore the file from the Turbo Update Master tape and try the TUINSTAL program again. \ENTRY=TUWARN6 MESSAGE Open of localized catalog TUCATxxx failed. Opening TUCAT000. (TUWARN 6) CAUSE The TUINSTAL program tried to open an NLS (Native Language Support) localized message catalog file when the NLS configured language is a language other than default (0) and couldn't open the localized file. The TUINSTAL program then tries to open the default message catalog file TUCAT000. ACTION NONE - This is just an informative message in case the user expected to be using an NLS localized message catalog file. \ENTRY=TUERR7 MESSAGE Error writing to $STDLIST, TUINSTAL terminating. (TUERR 7) CAUSE An I/O error occurred while trying to write to the $STDLIST device specified for the TUINSTAL program. ACTION No specific action can be suggested here. If required, call your HP field service representative to help identify the problem and run the TUINSTAL program again. \ENTRY=TUERR8 MESSAGE Error closing message catalog. (TUERR 8) CAUSE An error occurred while trying to close the TUINSTAL program message catalog file (TUCAT000.HPTUINST.SYS or other NLS localized catalog file). ACTION Other file system information should have also been printed on the terminal. Analyze this information, take appropriate action, and run the TUINSTAL program again if there is any indication that the program did not end in a normal manner. \ENTRY=TUERR9 MESSAGE Unable to read from $STDINX - TUINSTAL Terminating (TUERR 9) CAUSE An I/O error occurred while trying to read from the $STDIN device for the TUINSTAL program. ACTION No specific action can be suggested here. If required, call your HP field service representative to help identify the problem and run the TUINSTAL program again. \ENTRY=TUWARN10 MESSAGE WARNING: Disk caching is installed but not enabled. TUINSTAL will run 20-40% slower without caching enabled. (TUWARN 10) CAUSE The TUINSTAL program has determined that disk caching is installed on your system, but was unable to start disk caching on LDEV 1. ACTION Manually enable disk caching on all disks before running TUINSTAL, by using the STARTCACHE MPE command. \ENTRY=TUWARN11 MESSAGE WARNING: This system does not have disc caching installed. TUINSTAL will run approximately 20-40% slower. (TUWARN 11) CAUSE The TUINSTAL program has determined that the disk caching product is not installed on your system. ACTION None. If you believe that the disk caching product (HP30539) should be installed, contact your HP Support Representative. \ENTRY=TUWARN12 MESSAGE CACHING STARTED ON LDEV 1. (TUWARN 12) CAUSE The TUINSTAL program has determined that the disk caching product is installed on your system, but caching was not enabled for logical device 1 (the system disk). The TUINSTAL program has started caching on logical device 1. NOTE: You may want to insure that disk caching is enabled on all of your disk drives before running TUINSTAL. ACTION NONE - This is just an informative message. \ENTRY=TUERR13 MESSAGE TUINSTAL was unable to START/STOP the SEGMENTER process SEGPROC.PUB.SYS. See TULOGFIL.HPTUINST.SYS for the error messages. (TUERR 13) CAUSE An error occurred when the TUINSTAL program attempted to START or STOP the SEGMENTER process. Additional error messages can be found in the file TULOGFIL.HPTUINST.SYS. ACTION Other file system information should have been logged in the file TULOGFIL.HPTUINST.SYS. Analyze this information, take appropriate action, and run the TUINSTAL program again. If required, call your HP field service representative to help identify the problem and run the TUINSTAL program again. \ENTRY=TUERR14 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 14) \ENTRY=TUERR15 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 15) \ENTRY=TUERR16 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 16) \ENTRY=TUERR17 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 17) \ENTRY=TUERR18 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 18) \ENTRY=TUERR19 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 19) \ENTRY=TUERR20 MESSAGE The following command could not be executed by MPE (TUERR 20) CAUSE The TUINSTAL program tried to issue an MPE command through the COMMAND Intrinsic and the command got an MPE error. ACTION TUERR 21 will be issued along with this message giving the CIERR number. Take appropriate corrective action according to the CIERR listed and run the TUINSTAL program again. \ENTRY=TUERR21 MESSAGE COMMAND ERROR #! OCCURRED (TUERR 21) CAUSE The TUINSTAL program tried to issue an MPE command through the COMMAND Intrinsic and the command got an MPE error. ACTION TUERR 20 will be issued along with this message Take appropriate corrective action according to the CIERR listed and run the TUINSTAL program again. \ENTRY=TUERR22 MESSAGE The DIAG entry point cannot be used on this version of MPE (TUERR 22) CAUSE The version of MPE you are currently running is Release 30 or earlier and does not support using the MPE RUN command through the COMMAND Intrinsic. ACTION Use the Turbo Update Master Tape to update the system to the latest released version of MPE and rerun the TUINSTAL program using the DIAG entry point. \ENTRY=TUWARN23 MESSAGE If using a cartridge tape, it must be formatted first. (TUWARN 23) CAUSE If you are using a cartridge tape, the tape must be formatted and serialized and marked as a scratch tape before it can be used by the TUINSTAL program. ACTION Use the VINIT subsystem to format, serialize, and scratch the cartridge tape. Instructions for formatting cartridge tapes are included in this HELP file or in the MPE Operation and Resource Management manual (P.N. 32033-90005). Enter the command DIAG for further information on formatting cartridge disks. \ENTRY=TUWARN24 MESSAGE If using an HP150/HP2647F, the flexible disk must be formatted first. (TUWARN 24) CAUSE If you are using a flexible disk, the disk must be formatted before it can be used by the TUINSTAL program. ACTION Instructions for formatting flexible disks are included in this HELP file. Enter the command DIAG for further information on formatting flexible disks. \ENTRY=TUERR25 MESSAGE Disk error accessing sysdump/initial Comm Record. (TUERR 25) CAUSE A disk error occurred while trying to access the SYSDUMP/ Initial Communications Record while trying to update the MPE VUF. ACTION There is a possibility that you will have to reload your system. If you did not back up your system before starting to accomplish the Turbo Update process, you should do so at this time. DO NOT SHUTDOWN YOUR SYSTEM. Call Hewlett-Packard to have your disks checked out as soon as possible. \ENTRY=TUERR26 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 26) \ENTRY=TUERR27 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 27) \ENTRY=TUERR28 MESSAGE The Turbo Update tape has NOT been successfully restored. Check the messages that were displayed during the retrieval of the Turbo Update files to determine the appropriate action to take. (TUERR 28) CAUSE The cause of this error should have been displayed on the system console. Other causes could include a power failure on either the system or tape drive. ACTION Examine the displayed error messages, take corrective action as appropriate, and restart the TUINSTAL program. \ENTRY=TUERR29 MESSAGE An error has occurred trying to open the tape file on ldev or class "!". Correct the error and run TUINSTAL again. (TUERR 29) CAUSE The cause of this error should have been displayed on the system console. Other causes could include a power failure on either the system or tape drive. ACTION Examine the displayed error messages, take corrective action as appropriate, and restart the TUINSTAL program. \ENTRY=TUERR30 MESSAGE The Turbo Update tape that was mounted on the tape drive does not match the version of the Turbo Update data files. (TUERR 30) CAUSE The Turbo Update Master Tape mounted is not the same version as the TUINSTAL program. This could be caused by the TUINSTAL program not being successfully restored from the front of the Turbo Update Master Tape. ACTION Restore the files from the front of the Turbo Update Master Tape again. Be sure to use the ';SHOW' option on the :RESTORE command and verify that all of the files are restored and rerun the TUINSTAL program. \ENTRY=TUERR31 MESSAGE The Turbo Update files must be restored into the HPTUINST.SYS group. (TUERR 31) CAUSE The files from the front of the Turbo Update Master Tape were not restore into the HPTUINST.SYS group. ACTION If the HPTUINST.SYS group does not exist with the proper capabilities, create the group using the NEWGROUP command, restore the files from the front of the Turbo Update Master Tape, and rerun the TUINSTAL program. \ENTRY=TUERR32 MESSAGE The tape mounted on the tape drive is not a Turbo Update format tape. Please mount the correct tape, and run TUINSTAL again. (TUERR 32) CAUSE A tape other than the Turbo Update Master Tape was mounted on the tape drive (perhaps a scratch tape in preparation of the sysdump operation). ACTION Remount the Turbo Update Master Tape and rerun the TUINSTAL program. \ENTRY=TUERR33 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 33) \ENTRY=TUERR34 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 34) \ENTRY=TUERR35 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 35) \ENTRY=TUERR36 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 36) \ENTRY=TUERR37 MESSAGE "!" is not a configured Device Class name. (TUERR 37) CAUSE The device class entered for the Turbo Update Master tape restore device OR for the TUSYSDMP job output does not exist in your system configuration. ACTION Enter a device class name that is configured for the tape device that you will use. \ENTRY=TUERR38 MESSAGE A : is an invalid response to Ldev or Class number. (TUERR 38) CAUSE A : was entered in response to a question asking for an Ldev number or a Class name, perhaps to try to issue an MPE command. The TUINSTAL program does not allow issuing MPE commands in response to a question. ACTION Enter the information requested. If you do need to issue an MPE command, the TUINSTAL program must be terminated. Since BREAK is disabled at this point, the program can be terminated by issuing the MPE command :EOD. To restart the Turbo Update process, rerun the TUINSTAL program. \ENTRY=TUERR39 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 39) \ENTRY=TUERR40 MESSAGE TUINSTAL logon must be MANAGER.SYS,HPTUINST. (TUERR 40) CAUSE The TUINSTAL program was run without the current logon being MANAGER.SYS,HPTUINST. ACTION Re-logon using the logon of MANAGER.SYS,HPTUINST. \ENTRY=TUERR41 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 41) \ENTRY=TUERR42 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 42) \ENTRY=TUERR43 MESSAGE TUINSTAL must be run from the system console. (TUERR 43) CAUSE The TUINSTAL program was run from a terminal that was not the system console. ACTION Rerun the TUINSTAL program from the system console. \ENTRY=TUERR44 MESSAGE *WARNING -- THIS SYSTEM DOES NOT HAVE ENOUGH DISK SPACE ON LDEV 1. FOR TUINSTAL TO CONTINUE "!" CONTIGUOUS SECTORS ARE REQUIRED ON LDEV 1. (TUERR 44) CAUSE Logical Device 1 does not have enough contiguous sectors of disk space to complete the SYSDUMP and UPDATE operation. ACTION Delete files residing on LDEV 1 or move them to other disk drives on the system then rerun the TUINSTAL program. \ENTRY=TUERR45 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 45) \ENTRY=TUERR46 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 46) \ENTRY=TUERR47 MESSAGE TUINSTAL cannot be be run in JOB mode. (TUERR 47) CAUSE A job was created that tried to run the TUINSTAL program. The TUINSTAL program can only be run from a session on the console logged onto MANAGER.SYS,HPTUINST. ACTION Run the TUINSTAL program from a session. \ENTRY=TUERR48 MESSAGE TUINSTAL requires 0 JOBS and 1 SESSION to be logged on. (TUERR 48) CAUSE Either one or more jobs or one or more sessions other than the one on the system console being used to run the TUINSTAL program is logged onto the system. If any jobs or sessions are logged onto the system while the TUINSTAL program is running, the program might not be able to do all operations correctly. ACTION Stop all jobs running using the MPE ABORTJOB command and take appropriate action to get all sessions logged off of the system. Then, rerun the TUINSTAL program. \ENTRY=TUERR49 MESSAGE TUINSTAL cannot be run on an MPE iX system. (TUERR 49) CAUSE The TUINSTAL program is being run on an MPE iX system. The TUINSTAL program is only intended to install software on MPE V systems running Release 2P or later. ACTION The TUINSTAL program cannot be run on MPE iX systems. \ENTRY=TUERR50 MESSAGE TUINSTAL requires a Series 37,4X,5X,6X,70 or Micro. (TUERR 50) CAUSE The TUINSTAL program is being run on an MPE IV system. The TUINSTAL program is only intended to install software on MPE V systems running Release 2P or later. ACTION The TUINSTAL program cannot be run on MPE IV systems (SII/III/30/33). \ENTRY=TUERR51 MESSAGE TUINSTAL requires MPE V version 2P or later. (TUERR 51) CAUSE The TUINSTAL program is being run on an MPE V system that is currently running a version of MPE V that is earlier than release 2P. ACTION Use the AUTOINST process to install a version of MPE V that is Release 2P, 30, 31, or 3P. Then, rerun the TUINSTAL program. \ENTRY=TUERR52 MESSAGE File system error attempting to open SL.PUB.SYS. (TUERR 52) CAUSE A file system error occurred while attempting to FOPEN the file SL.PUB.SYS. Other file information should be displayed on the system console along with this message helping to identify the specific error. ACTION Take appropriate action as indicated by the information on the system console and rerun the TUINSTAL program. \ENTRY=TUERR53 MESSAGE FGETINFO error on SL.PUB.SYS. (TUERR 53) CAUSE A problem occurred when the FGETINFO Intrinsic was called to get information about the size of the file SL.PUB.SYS. Other file information should be displayed on the system console along with this message helping to identify the specific error. ACTION Take appropriate action as indicated by the information on the system console and rerun the TUINSTAL program. \ENTRY=TUERR54 MESSAGE File System error closing SL.PUB.SYS. (TUERR 54) CAUSE A file system error occurred while attempting to FCLOSE the file SL.PUB.SYS. Other file information should be displayed on the system console along with this message helping to identify the specific error. ACTION Take appropriate action as indicated by the information on the system console and rerun the TUINSTAL program. \ENTRY=TUERR55 MESSAGE TUINSTAL was run as "!", but must be run as TUINSTAL.HPTUINST.SYS. (TUERR 55) CAUSE The program file TUINSTAL.HPTUINST.SYS has been renamed to some other name. ACTION Rename the file back to the name TUINSTAL.HPTUINST.SYS and rerun the TUINSTAL program. \ENTRY=TUERR56 MESSAGE This system does not have job streaming enabled. Please issue the STREAMS command and run TUINSTAL again. (TUERR 56) CAUSE The MPE STREAMS command has not been issued on the system console, so jobs cannot be streamed. ACTION Issue the MPE STREAMS command to enable the MPE input spooling facility and rerun the TUINSTAL program. \ENTRY=TUERR57 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 57) \ENTRY=TUERR58 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 58) \ENTRY=TUERR59 MESSAGE Creation of TUTAPE.HPTUINST.SYS failed. Create error = !. (TUERR 59) CAUSE An error occurred when the TUINSTAL program tried to create and activate the program TUTAPE.HPTUINST.SYS. The error number is displayed as part of the message. ACTION Take appropriate action as indicated by the error number displayed as part of the error message and rerun the TUINSTAL program. \ENTRY=TUERR60 MESSAGE This error message is reserved for future use and is not currently used. (TUERR 60) \ENTRY=TUERR61 MESSAGE Data file "!" is missing. (TUERR 61) CAUSE One of the data files from the front of the Turbo Update Master Tape did not get restored from the tape. The name of the file will be inserted as part of the message. ACTION Restore the files from the Turbo Update Master Tape using the ';SHOW' option of the RESTORE command an verify that the files are all restored from the tape. Then, rerun the TUINSTAL program. \ENTRY=TUERR62 MESSAGE TUINDIR could not be created due to invalid "!". (TUERR 62) CAUSE An error occurred while trying to create the file TUINDIR.HPTUINST.SYS. Additional information about the error is included as part of the message and could possibly appear as additional messages on the system console. ACTION Take appropriate action as indicated by the error message(s) and rerun the TUINSTAL program. \ENTRY=TUERR63 MESSAGE TUSYSDMP could not be created due to invalid "!". (TUERR 63) CAUSE An error occurred while trying to create the file TUSYSDMP.HPTUINST.SYS. Additional information about the error is included as part of the message and could possibly appear as additional messages on the system console. ACTION Take appropriate action as indicated by the error message(s) and rerun the TUINSTAL program. \ENTRY=TUERR64 MESSAGE TUSYSDMP could not be streamed due to CIERR !. (TUERR 64) CAUSE An error occurred when the TUINSTAL program tried to stream the job file TUSYSDMP.HPTUINST.SYS. The error number is displayed as part of the message. ACTION Take appropriate action as indicated by the error number displayed as part of the error message and using the MPE STREAM command, restream the job file TUSYSDMP.HPTUINST.SYS. \ENTRY=TUERR65 MESSAGE Data file "!" is invalid. (TUERR 65) CAUSE One or more of the files on the HPTUINST.SYS group are not the same version as the TUINSTAL program. This could be caused by one or more of the files not being restored from the front of the Turbo Update Master Tape. ACTION Restore the files from the front of the Turbo Update Master Tape. Be sure to use the ';SHOW' parameter with the RESTORE command and verify that the files are restored. Then, rerun the TUINSTAL program. \ENTRY=TUERR66 MESSAGE Subsystem search failed due to invalid data file "!". (TUERR 66) CAUSE One of the data files from the front of the Turbo Update Master Tape is not a correct file. The name of the file will be inserted as part of the message. ACTION Restore the files from the front of the Turbo Update Master Tape. Be sure to use the ';SHOW' parameter with the RESTORE command and verify that the files are restored. Then, rerun the TUINSTAL program. \ENTRY=TUERR67 MESSAGE Could not create TUSWINFO file. (TUERR 67) CAUSE An error occurred while trying to create the file TUSWINFO.HPTUINST.SYS. Additional information about the error is included as part of the message and could possibly appear as additional messages on the system console. ACTION Take appropriate action as indicated by the error message(s) and rerun the TUINSTAL program. \ENTRY=APPENDIXD,TUCOPY,LOCALIZE,CATALOG Appendix D - The TUCOPY Program The TUCOPY program copies the Turbo Update Master Tape. It does this by making a copy of the image of the tape to a large disk file on the system and then copying the tape image back to a tape. This allows copying the tape on a system that only has one tape drive or copying the tape to a tape media different than the type of media on which you received the Turbo Update Master Tape. The TUCOPY program has one special entry point called LOCALIZE which allows adding a localized message catalog to the front part of the Turbo Update Master Tape. Procedures for localizing the TUINSTAL message catalog and for using the entry point are in this appendix after the following procedures for using the TUCOPY program without the entry point. The TUCOPY program is a modified version of the "STORCOPY" utility. You will be prompted to select an INPUT file and an OUTPUT file. You may enter a carriage return at either prompt to select a tape file. If a Turbo Update tape has already been read into a disc file, you can supply the disc file name as the input file and carriage return as the output file to make a copy to tape. A file equation may be issued to override the default specifications, as follows: Note: You only need to issue a file equation to override the default specifications. For example, if you want to use a cartridge tape as the input file, you should issue a file equation with either the ldev number of the cartridge tape OR a device class name (such as CTAPE) that is configured for the cartridge tape drive that you would like to use. IF THE TAPE DEVICE YOU ARE COPYING To/FROM DOES NOT HAVE DEVICE CLASS NAME 'TAPE' CONFIGURED, YOU MUST ISSUE A FILE EQUATION. Input file default specifications: FILE INPUT;DEV=TAPE;REC=8192 or if a disc file name is entered at the SELECT INPUT FILE prompt, FILE INPUT=filename,(OLD or TEMP) NOTE: DO NOT ADD ANY PARAMETERS OTHER THAN FILENAME AND FILE DOMAIN TO A FILE EQUATION FOR A DISC FILE. Output file default specifications: FILE OUTPUT;DEV=TAPE;REC=8192 (or 4096 if 1600 BPI) or if a disc file name is entered FILE OUTPUT=filename,NEW;SAVE disc output To make a copy of an INPUT from a tape device, to an OUTPUT on disc, you would not need to issue a file equation, just enter the disc file name that you would like to use at the NOTE: DO NOT ADD ANY PARAMETERS OTHER THAN FILENAME AND FILE DOMAIN TO A FILE EQUATION FOR A DISC FILE. To access this information, just press the Enter key to display the information about the next item or enter the item name as shown in the brackets: Running the TUCOPY Program (TUCOPY) Installing the Localized Message Catalog (LOCALIZE) Localizing the TUINSTAL Message Catalog (CATALOG) \ITEM=TUCOPY Running the TUCOPY Program To make a copy of the Turbo Update Master Tape without adding a localized message catalog file, do the following: To make a disc copy of the Turbo Update Master Tape, or to do a copy from tape to tape: 1. Log onto MANAGER.SYS,HPTUINST. 2. Enter a file equation for the INPUT file. This is normally the Turbo Update Master Tape the first time the program is run. You would normally copy from the Turbo Update Master tape to a disc file, unless you have more than 1 tape device. If your input is from a device that does not have device class name 'TAPE' configured on it, or if it is a 9140/9144/9145 cartridge tape, issue a file equation for file INPUT. For example, if the INPUT is from a cartridge tape device with device class name CTAPE configured, you would issue the INPUT file equation as follows: :FILE INPUT;DEV=CTAPE You could also use the logical device number in place of the class name as follows: :FILE INPUT;DEV=7 If your input is from a previously created disc file, you do not need to issue a file equation. 3. Enter a file equation for the OUTPUT file. This would normally be a disc file name to copy the Turbo Update Master tape into. If you have more than 1 tape drive, you can copy from tape to tape. If you have 2 different types of tape drives (a cartridge tape and a 6250 BPI 1/2" reel tape, for example) you can still copy from tape to tape. If your output is to a device that does not have device class name 'TAPE' configured on it, or if it is a 9140/9144/9145 cartridge tape, issue a file equation for file OUTPUT. For example, if the OUTPUT is to a cartridge tape device with device class name 'CTAPE' configured, you would issue the OUTPUT file equation as follows: :FILE OUTPUT;DEV=CTAPE You could also use the logical device number in place of the class name as follows: :FILE INPUT;DEV=7 If your output is to a disc file that you are going to create, you do not need to issue a file equation. 4. Issue the following command to run the TUCOPY program: :RUN TUCOPY 5. If you select a disk file for output, and a disk file already exists with the name that you specified, the TUCOPY program will ask if you want to purge the OUTPUT file. If it is OK to purge the disk file, enter a Y. The TUCOPY program will purge the old disk file and create a new disk file with the name you specified. If you do NOT want to purge the old disk file, enter either a N or just a carriage return. The TUCOPY will prompt you for the OUTPUT file again. Enter a filename for the OUTPUT file that is not the same as an already existing disk file. 6. Answer the I/O request on the system console for INPUT and/or OUTPUT with the information requested. 7. If copying to a disc file, the Turbo Update Master tape will be read into the disc file name selected, and the TUCOPY program will complete with an END OF PROGRAM message. If a tape to tape copy was done, the TUCOPY program will terminate with an END OF PROGRAM message if no errors occurred. << TUCOPY will be changed to prompt multiple times in the next >> << build of the Turbo Update Tape >> 8. If a disc file was created, repeat steps 2 thru 7 above, but use the file name entered for the OUTPUT file as the INPUT file, and a carriage return for the OUTPUT file. (Be sure and issue a file equation for OUTPUT if the tape device does NOT have device class name 'TAPE' configured) (Note that step 9 will only occur on the FINAL BUILD of RELEASE 40) 9. After the copy is made, answer the question as to whether or not you want to make another copy. Enter either a N or just a carriage return will terminate the TUCOPY program. If you want to make another copy, answer the question with a Y. Then, repeat steps 7 through this step. \ITEM=LOCALIZE Installing the Localized Message Catalog To make a copy of the Turbo Update Master Tape and at the same time add a localized message catalog file (there is a limit of only one localized message catalog file that can be added), do the following: NOTE: You can only use the LOCALIZE entrypoint when copying from the original Turbo Update Master Tape. Your INPUT must be from the Turbo Update Master Tape. You can output to either a disc file or to another tape device. 1. Log onto MANAGER.SYS,HPTUINST. 2. Enter a file equation for the INPUT file. This is MUST be the Turbo Update Master Tape in order to use the localize entry point. If your input is from a device that does not have device class name 'TAPE' configured on it, or if it is a 9140/9144/9145 cartridge tape, issue a file equation for file INPUT. For example, if the INPUT is from a cartridge tape device with device class name CTAPE configured, you would issue the INPUT file equation as follows: :FILE INPUT;DEV=CTAPE You could also use the logical device number in place of the class name as follows: :FILE INPUT;DEV=7 3. Enter a file equation for the OUTPUT file. This would normally be a disc file name to copy the Turbo Update Master tape into. If you have more than 1 tape drive, you can copy from tape to tape. If you have 2 different types of tape drives (a cartridge tape and a 6250 BPI 1/2" reel tape, for example) you can still copy from tape to tape. If your output is to a device that does not have device class name 'TAPE' configured on it, or if it is a 9140/9144/9145 cartridge tape, issue a file equation for file OUTPUT. For example, if the OUTPUT is to a cartridge tape device with device class name 'CTAPE' configured, you would issue the OUTPUT file equation as follows: :FILE OUTPUT;DEV=CTAPE You could also use the logical device number in place of the class name as follows: :FILE INPUT;DEV=7 If your output is to a disc file that you are going to create, you do not need to issue a file equation. 4. Issue the following command to run the TUCOPY program: :RUN TUCOPY,LOCALIZE 5. The TUCOPY program will prompt you for the name of the already localized message catalog. It must start with 'TUCAT' followed by the 3 digit language number (for example TUCAT007 for a catalog localized in FRENCH). 5. If you select a disk file for output, and a disk file already exists with the name that you specified, the TUCOPY program will ask if you want to purge the OUTPUT file. If it is OK to purge the disk file, enter a Y. The TUCOPY program will purge the old disk file and create a new disk file with the name you specified. If you do NOT want to purge the old disk file, enter either a N or just a carriage return. The TUCOPY program will prompt you for the OUTPUT file again. Enter a filename for the OUTPUT file that is not the same as an already existing disk file. 6. Answer the I/O request on the system console for INPUT and/or OUTPUT with the information requested. 7. If copying to a disc file, the Turbo Update Master tape will be read into the disc file name selected, and the TUCOPY program will complete with an END OF PROGRAM message. If a tape to tape copy was done, the TUCOPY program will terminate with an END OF PROGRAM message if no errors occurred. << TUCOPY will be changed to prompt multiple times in the next >> << build of the Turbo Update Tape >> 8. If a disc file was created, repeat steps 2 thru 7 above, but use the file name entered for the OUTPUT file as the INPUT file, and a carriage return for the OUTPUT file. (Be sure and issue a file equation for OUTPUT if the tape device does NOT have device class name 'TAPE' configured) (Note that step 9 will only occur on the FINAL BUILD of RELEASE 40) 9. After the copy is made, answer the question as to whether or not you want to make another copy. Enter either a N or just a carriage return will terminate the TUCOPY program. If you want to make another copy, answer the question with a Y. Then, repeat steps 7 through this step. \ITEM=CATALOG Localizing the TUINSTAL Message Catalog The TUINSTAL message catalog is an NLS (Native Language Support) standard catalog file formatted using the NLS utility GENCAT.PUB.SYS. To localize the catalog file, follow the steps listed below: 1. Log onto the system using the logon MANAGER.SYS,HPTUINST. 2. If the files from the front of the Turbo Update Tape have not been restored, issue the following MPE commands: :NEWGROUP HPTUINST.SYS;CAP=IA,BA,PH,PM,MR,DS :FILE T;DEV=TAPE (or CTAPE if cartridge tape) Place the Turbo Update Master Tape on the tape drive. :RESTORE *T;@.HPTUINST.SYS;SHOW Reply to the console request. 9 files will be restored. The file TUCATSRC.HPTUINST.SYS is the source file for TUCAT000. 2. Using a text editor, text the file and modify the file as desired: :EDITOR HP32201A.09.00 EDIT/3000 FRI, JAN 27, 2023, 9:18 AM (C) HEWLETT-PACKARD CO. 1993 /S SHORT;T TUCATSRC FILE UNNUMBERED /L 11/15,UNN 20 The following command could not be executed by MPE (TUERR 20) 21 COMMAND ERROR #! OCCURRED (TUERR 21) 22 The DIAG entry point cannot be used on this version of & MPE (TUERR 22) 23 If using a cartridge tape, it must be formatted first.& 4. Using GENCAT.PUB.SYS again, format the catalog file into a file that follows the NLS standard naming convention of TUCATxxx where xxx is the NLS defined language number. Following is the sequence needed to accomplish this for a catalog converted to French (NLS defined language 7): :RUN GENCAT.PUB.SYS HP32414A.03.09 GENCAT/3000 (C) HEWLETT-PACKARD., 1983 ENTER INDEX OF DESIRED FUNCTION 0. EXIT 1. HELP 2. MODIFY SOURCE CATALOG 3. FORMAT SOURCE INTO FORMATTED CATALOG 4. EXPAND FORMATTED CATALOG INTO SOURCE >>3 ENTER NAME OF SOURCE FILE TO BE FORMATTED >>TUCATSRC FORMATTING.... ENTER NAME FOR NEW FORMATTED FILE >>TUCAT007 TOTAL NUMBER OF SETS FORMATTED = 2 TOTAL NUMBER OF MESSAGES FORMATTED = 65 FORMATTING SUCCESSFUL ENTER INDEX OF DESIRED FUNCTION 0. EXIT 1. HELP 2. MODIFY SOURCE CATALOG 3. FORMAT SOURCE INTO FORMATTED CATALOG 4. EXPAND FORMATTED CATALOG INTO SOURCE >>0 END OF PROGRAM If you do not know what the NLS defined language number is for the language desired, use the LANGINST.PUB.SYS utility to list the languages as follows: :RUN LANGINST.PUB.SYS HP32414A.03.09 LANGINST/3000 (C) HEWLETT-PACKARD CO., 1983 0. EXIT 1. ADD LANGUAGE TO LANGDEF 2. DELETE LANGUAGE FROM LANGDEF 3. MODIFY NATIVE FORMATS 4. LIST HP SUPPORTED LANGUAGES 5. MODIFY THE SYSTEM DEFAULT LANGUAGE 6. LIST LANGUAGES CURRENTLY CONFIGURED 7. DISPLAY TRANSLATION TABLES Enter selection number :4 Once the above procedure is accomplished and the new file is added to the front of the Turbo Update Master Tape using the procedures described at the front of Appendix D, the TUINSTAL program will use the localized message catalog as follows: When the TUINSTAL program starts running, it will query the operating system to find out the number of the NLS configured default language. The program will then append this number to the file name TUCAT to make the name of the localized message catalog. The program will then attempt to open this file on the .HPTUINST.SYS group. If the program cannot open this file, it will attempt to open the default Turbo Update message catalog file TUCAT000.HPTUINST.SYS. Upon the first successful open of a message catalog file, the program will continue working. If the program cannot successfully open any message catalog file, the program will terminate. \ENTRY=SRB,HP32115,HP32116,HP32246,HP32047,HP32238,HP32104,HP32247, \CONTINUE,HP30131,HP32033 Software Release Bulletin for MPE V Release 40 and all associated products. These are service requests (SRs) that have been fixed in this release of MPE V. To see a list of all of the SR numbers with the one line description for a particular product, enter the product number. To view the SR detail, at any help prompt you may enter the SR number preceded by the letters "SR". For example, service request 4701243071 for MPE V can be viewed by entering SR4701243071. If you enter the keyword SRBDETAIL, a list of each product and it's SRs (without the one line description) will be displayed. The SR detail can be viewed by entering the SR number preceded by the letters "SR". Product name Product number v.uu.ff -------------------|------------------|------------ MPE V/E HP32033 G.13.00 BUSINESS BASIC HP32115 A.02.12 FORTRAN 77/V HP32116 A.02.09 INFORM HP32246 A.10.00 MODCAL-CM-LIBRARY HP32047 A.00.04 OPT HP32238 A.00.33 RPG HP32104 A.08.10 TRANSACT HP32247 A.10.02 DSN/CS HP30131 A.55.50 \ITEM=HP32115 - BUSINESS BASIC - Product Number: 32115A Report JOINFORM sent to printer is missing last 2 lines of form 5000529891 IF statement with a complex string equality causes abort 5000561449 Enhancement request to modify warning message #2053 5000588012 Problems with OUTPUT,MARGIN= command; confusion byte vs word 1650155192 ABS(X<3) when X is negative causes abort in the compiler 5000553123 Stack underflow when print variable>500 chars with K format 1653056168 MOD function does not always return correct result D500167668 LIST * displays last line modified instead of executed D500168112 Control Y trapping in interpreter varies according to load D500168138 DMPT if PRINTER IS statmnt called from SUB if report active D500168161 Problems with CR/LF and PRINT functions at end of PRINT list D500166595 BBASIC truncates last byte of a file opened with CCTL D500172452 COPYQ followed by DEL causes a bounds violation 1650136358 HELP catalog needs to be clearer on SETOFLD,SETCFLD,SETIFLD 5000630467 \ITEM=HP32116 - FORTRAN 77/V - Product Number: 32116A I/O ERR 915 with BZ format 5000577387 Problems with A2 format and repeat factors 5000580258 Auto-open file doesn't always work, WRITE or FNUM fails 5003224170 HPEXTIN FORTRAN/V LIB routine does NOT error when passed '.' D500205781 HPINEXT returns "******" for short real -.9999995 with G12.6 D500205799 Arithmetic IF branching to a format statment is not detected D500205898 FSET will not allow Filenumbers > 254 (I/O error 975) D500205930 CANNOT OPEN FORTRAN 77 ERROR MESSAGE FILE FTNCAT.PUB.SYS D500205963 Illegal constant substring parms not flagged at compile time 5000201285 \ITEM=HP32246 - INFORM - Product Number: 32246A Inability to report on common element linked in flat files 5000180232 Wrong driving file when link item is not in the report 5000581033 User-defined field,P(11,0,6),too small to handle calculation 5003033977 References to DATA BASE should be DATABASE in msg catalog D500157255 Incorrect error message displayed when sort error occurs D500178111 INFORM aborts with BOUNDS VIOLATION when PASSWORD = ]]. D500199752 Selection criteria, field type Z or P results in no entries 9999034204 Using ^^ on two character fields does not work. 5000045138 INVALID REC NUMBER (KSAM 184)when NMKSAM used with FIRSTREC=1D500190108 Wildcard chars don't work with other than Native-3000 lang 1650047688 Wrong selection criteria for 8-byte intgr items and neg. vals5000614958 No records found when selection criteria is 12-byte integer D500187492 \ITEM=HP32047 - MODCAL-CM-LIBRARY Intgr ovrflw in M'CAN'ESCAPE+16 if PARM large on runtime err 1650160531 \ITEM=HP32238 - OPT - Product Number: 32238A OPT DOES NOT DISPLAY OPEN FILE DETAIL FOR SOME FILES ON 3P 1653122564 \ITEM=HP32104 - RPG - Product Number: 32104A Hangs if locking and with RECORD NUMBER ADJUST on flat file 5000434175 SIGEDIT forms file using unmerged NLS cat gets BOUND VIOLATI 4700946004 SIGEDIT Screen Corrupts after Adding 20 1-Position Fields 5000622050 Add fields SIGEDIT scrn result in field name 3, Seq No 2000 5000622068 SIGEDIT Convert S&D specs with >255 D-specs in form aborts 4701003004 SIGEDIT file w/signed numeric field show diff. length,A.08.055000662403 SIGEDIT will corrupt form name when deleting a form. 5003009670 Sigedit delete form causes corruption in form list. 1653056507 SIGEDIT forms file with msgs merged requires FILE CATALOG= 4700945998 RSI needs ability to open port with 4 digit LDEV 5003215012 SIGEDIT MERGE CATALOG fails if catalog created w/GENCAT. 5000442517 Convert S&D screen allows fileset, screen text says filename 5000480210 \ITEM=HP32247 - TRANSACT - Product Number: 32247A Product Number: 32247A Report # DISPLAY to a file uses blocking factor as first PAGE number. D500132399 REWIND KSAM file fails if first record marked for deletion. D500189811 Bad db reference (-11) if main prog uses > 32k bytes stack. D500155200 DISPLAY(FILE=xxx) command, close the spoolfile, get FSERR 0 5000705046 CURSOR= option on PUT/GET(FORM), error Cannot place cursor. 5000553842 No warning for Dict item names > 16 chrs, migration issue. 5000562496 No records found when selection criteria is 12-byte integer D500187245 NEED= doesn't work, if NEED group starts last line of page 1650017103 Row format of DISPLAY does not work if FILE=filename is used 1650159327 DISPLAY to screen & file, linecount errors, no CONTINUE(Y/N) D500132365 DISPLAY to a file uses blocking factor as first PAGE number. D500132399 Trailing "-" interpreted as hyphen,not as optional sign char 5003004382 TRANSACT V: Incorrect error using type X items in LET stmnt. 5000601179 RETURN(@) leads to infinite loop TRANSACT/V; works in TR/XL 5000534313 FORMAT verb's CCTL applied to prev item instead of current 5003071332 GET(CURRENT) doesn't retrieve last entry written to KSAM fil 5000268235 Partial key(generic)access doesn't retrieve expected records 5000225086 LET RESULT=SQRT(X) doesn't work when RESULT type 9 or X or Z 9999203042 LET zero from 9,I,J,K,P,R,E types into X,U results in blanks 5000462366 LET (positive-real)=(-1 or (Neg'Item'Value)) produces no err D500121905 Get INTEGER OVERFLOW when LET (I) = maximum negative integer D500168252 Continuous error message loop when INIT value > display lgth D500138578 Passwords are not passed correctly to sub-programs. D500160077 LIST item,PASSWORD in a subprogram may return garbage. D500186171 Match with wildcards not handled properly when condition <> D500183905 Incorrect matching for 8-byte intgr items and neg values D500186452 SORT= option on OUTPUT(SERIAL), results not in sorted order D500144121 Partial key(generic)access doesn't retrieve expected records 5000225086 PROMPT(SET) gives invalid data with CHECK= and carriage ret D500153809 REPLACE doesn't update KSAM records if item order not physic D500190389 Get INTEGER OVERFLOW when LET (I) = maximum negative integer D500168252 \ITEM=HP30131 - DSN/CS - Product Number: 30131A SHOWCOM command cannot be ALLOW'd in 3P 5003214494 \ITEM=HP32033 - MPE V/E - Product Number: 32033G MPE allows > 2 chars for yr in lbld tape exp date w/o err 4701240150 SPOOK allows delete of READY spoolfile while OUTPUT @.@ 5000423079 SPOOK DELETE cmd selects OPEN files - warning msg misleading 5003104992 SPOOK5 displays wrong date for two digit months in R31 5003162362 DELETEVAR - MISLEADING MSGs WHEN TRYING TO DELETE JCW 4701243071 MPE ERROR MSG CARET OFF ONE BYTE IF ERROR ON CMD AFTER REDO 4701257600 SPOOK5 produces corrupt tapes on OUTPUT command. 4701263004 SPOOK5 truncates records on 3P when COPY cmd used with CCTL 5003215277 SPOOK5 on 3P changed the prompting in batch mode. 5003227280 FREAD OF AN OPEN SPOOLFILE FAILS WITH FSERR 0 ON 3P 4701267831 SF16 or 59, 1st accessor of msgfile run w/ NOCB and ;COPY 4701222745 SF310 in SECURITYPROC in UTILITY2 due to integer overflow 4701249086 SPOOK should print SECURITY VIOLATION, not FILE NOT FOUND 4700102616 \ENTRY=SRBDETAIL Software Release Bulletin detail reports for Release 40 as of 07/18/95 Enter the SR number (preceded by SR) for an SR to see the text of the SR displayed. The SRs are listed here by product number. - MPE V/E - Product Number: 32033G 4700102616 4701222745 4701240150 4701243071 4701249086 4701257600 4701263004 4701267831 5000423079 5003104992 5003162362 5003215277 5003227280 - BUSINESS BASIC - Product Number: 32115A 1650136358 1650155192 1653056168 5000529891 5000553123 5000561449 5000588012 5000630467 D500166595 D500167668 D500168112 D500168138 - FORTRAN 77/V - Product Number: 32116A 5000201285 5000577387 5000580258 5003224170 D500205781 D500205799 D500205898 D500205930 D500205963 - INFORM - Product Number: 32246A 1650047688 5000045138 5000180232 5000581033 5000614958 5003033977 9999034204 D500157255 D500178111 D500187492 D500190108 D500199752 - MODCAL-CM-LIBRARY 1650160531 - OPT - Product Number: 32238A 1653122564 - RPG - Product Number: 32104A 1653056507 4700945998 4700946004 4701003004 5000434175 5000442517 5000480210 5000622050 5000622068 5000662403 5003009670 5003215012 - TRANSACT - Product Number: 32247A 1650017103 1650159327 5000225086 5000225086 5000268235 5000462366 5000534313 5000553842 5000562496 5000601179 5000705046 5003004382 5003071332 9999203042 D500121905 D500132365 D500132399 D500132399 D500138578 D500144121 D500153809 D500155200 D500160077 D500168252 D500168252 D500183905 D500186171 D500186452 D500187245 D500189811 D500190389 - DSN/CS - Product Number: 30131A 5003214494 \ENTRY=SR1650136358 _______________________________________________________________________ Number: 1650136358 Product: BUSINESS BASIC 32115A 02.0 Keywords: BOUNDS One-line description: COPYQ followed by DEL causes a bounds violation Problem: Editing large programs can abort the interpreter. For example, copying lines from one program unit to another may cause a subsequent delete to get a bounds violation. Cause: This problem is caused by the memory manager picking the wrong subunit to swap out of memory when the switching from one subunit to another. This may occur when the memory pool is not big enough to hold all the information for two of the subunits at once, but is big enough to hold everything but their variable tables. Temporary solution: To work around this problem, run the interpreter with a larger PARM value to edit the large program. You may need to break up some of the large subunits into smaller ones; the Program Analyst can help you do this. If the PARM value needed for editing is too large to allow RUN, save your program after it has been edited and then run the interpreter with a smaller PARM value. \ENTRY=SR1650155192 _______________________________________________________________________ Number: 1650155192 Product: BUSINESS BASIC 32115A 02.0 One-line description: Problems with the OUTPUT ,MARGIN= command; confusion byte vs word Problem: The record size of a file created by the SEND OUTPUT TO statement is not 80 bytes as specified in the manual. Instead, it is based on the value of the MARGIN option. In the following example, the record size of the file "file1" is 100 bytes (50 words). This can lead to confusion between the record size of the created file (positive indicates words, negative indicates bytes) and the meaning of the MARGIN value during output. MARGIN is always a byte count; negative values are essentially ignored, with the margin being set to the field width. 10 SEND OUTPUT TO "file1";MARGIN=50 ! creates file1 with recsize=100B Cause: The SEND OUTPUT TO routine is using the MARGIN value when creating the output file. It should always use 80 bytes for the record size. Temporary solution: To work around the problem, create the file with the desired record size before the SEND OUTPUT TO statement. \ENTRY=SR1653056168 _______________________________________________________________________ Number: 1653056168 Product: BUSINESS BASIC 32115A 02.1 One-line description: Stack underflow when print variable > 500 chars with K format Problem: HP Business BASIC aborts when a string of more than 500 characters is printed with a "K" format specifier in PRINT/DISP USING. For example: >10 DIM B$[512] >20 B$[1;512] = " " >30 DISP USING "K";B$ >run **** PROGRAM ERROR #29 :STACK UNDERFLOW Cause: The problem is caused by a fixed size buffer of 500 bytes used to hold the formatted item output. The code for handling the K specifier does not check for buffer overflow. Temporary solution: To work around the problem, break up the print of the string into 500 character chunks: 25 FOR I=1 TO LEN(B$)-500 STEP 500 30 DISP USING "#,K";B$[I,I+499] ! print next 500 chars, suppress cr/lf 35 NEXT I 36 DISP USING "K";B$[I,LEN(B$)] ! print remaining chars with cr/lf \ENTRY=SR5000529891 _______________________________________________________________________ Number: 5000529891 Product: BUSINESS BASIC 32115A 02.0 One-line description: JOINFORM sent to printer is missing last 2 lines of form Problem: JOINEDIT "Print Form" prints a line of blanks instead of the last line of the form if that line does not end with a carriage return. Cause: This problem was caused by JOINEDIT first detecting line wraparound and resetting the column index to one, before detecting the end of the form. When end of form is detected, the rest of the line is blanked, starting at the current column index, before the line is output. Since the current column index was already reset, the entire line was being blanked. \ENTRY=SR5000553123 _______________________________________________________________________ Number: 5000553123 Product: BUSINESS BASIC 32115A 02.0 One-line description: ABS(X<3) when X is negative causes an abort in the compiler Problem: Some numeric expressions containing boolean operands may cause compiled programs to abort. For example, 10 X = -4 20 PRINT ABS(X<3) Cause: This problem is caused by the compiler getting confused about the type of boolean expressions in some instances during compilation. It ends up leaving an extra word on the top of stack due to an incorrect type conversion. Temporary solution: To work around the problem, assign the boolean expression to a temporary, and use the temporary as the operand in the numeric expression. For example: 10 X = -4 15 Y = X<3 20 PRINT ABS(Y) \ENTRY=SR5000561449 _______________________________________________________________________ Number: 5000561449 Product: BUSINESS BASIC 32115A 02.0 One-line description: IF statement with a complex string equality condition causes abort Problem: Extremely complicated expressions can cause incorrect behavior in compiled programs. This is most likely to occur with expressions which require many dynamic temporaries, such as those involving substrings and/or string function calls. For example, the following program may cause a bounds violation, or may simply fail to branch when it should: 10 GLOBAL OPTION BASE 1,REAL 100 DIM B1$[215],B$[482] 200 B1$=RPT$(" ",215);B$=RPT$(" ",482) 300 Temp=0 400 IF Temp=1 THEN 410 PRINT "Programme has looped back and then stopped" 420 STOP 430 ENDIF 500 Temp=1 68500 IF B1$[6,8]+B1$[22,26]+B1$[47,203]=B$[44,46]+B$[6,10]+B$[171,& 184]+B$[47,65]+B$[191;2]+B$[188;2]+B$[185;2]+B$[128,153]+B$[78, 89]+B$[90,127]+B$[155,170]+B$[66,77]+B$[193,206] THEN 400 ! B ck if & no change 90000 PRINT "End of TEST programme" 99999 END Cause: This problem is caused by the code generator doing garbage collection on one of its internal data structures when it exceeds a limit. An old index is then used to index into the rearranged data structure, referencing garbage. This causes incorrect code to be generated. Temporary solution: To work around the problem, break up the complicated expression: ... 21 DIM X1$[215],X2$[215] ... 81 X1$=B1$[6,8]+B1$[22,26]+B1$[47,203] 82 X2$=B$[44,46]+B$[6,10]+B$[171,184]+B$[47,65]+B$[191;2]+B$[188;& 2]+B$[185;2]+B$[128,153]+B$[78,89]+B$[90,127]+B$[155,170]+B$[66 77]+B$[193,206] 90 IF X1$=X2$ THEN ... \ENTRY=SRD500166595 _______________________________________________________________________ Number: D500166595 Product: BUSINESS BASIC 32115A 02.1 One-line description: Problems with CR/LF and PRINT functions at the end of the PRINT list Problem: The SPA function as the last item in a PRINT list, and not followed by a trailing delimiter, generates an extra CR/LF. Also, if the TAB function is the last item in a PRINT list and the PRINT is going to an HP terminal, no CR/LF is generated. For example: >10 PRINT 1;SPA(5) >20 PRINT 2 >30 PRINT 1;TAB(5) >40 PRINT 2 >run 1 2 1 2 This should print: 1 2 1 2 Temporary solution: To work around the problem, you can add a trailing delimiter to the original PRINT statement, and add an empty PRINT afterwards. Or, simply delete the function. 10 PRINT 1;SPA(5); 11 PRINT 20 PRINT 2 30 PRINT 1;TAB(5); 31 PRINT 40 PRINT 2 \ENTRY=SRD500167668 _______________________________________________________________________ Number: D500167668 Product: BUSINESS BASIC 32115A 02.1 One-line description: MOD function does not always return correct result Problem: INTEGER MOD with large values does not always return the correct result. For example: 10 INTEGER X,Y 20 X=16777235 30 Y=7 40 PRINT X MOD Y This will print -1. It should print 6. Cause: The problem is caused by an intermediate calculation being done in single-precision arithmetic. This is not accurate enough to represent all integers, and this roundoff causes the incorrect result for MOD. Temporary solution: To work around the problem, force the MOD to be done in REAL or DECIMAL arithmetic: 5 REAL X 10 INTEGER Y 20 X=16777235 30 Y=7 40 PRINT X MOD Y ! REAL variable for one of the operands 50 PRINT 16777235 MOD 7.0 ! or floating point constant \ENTRY=SRD500168112 _______________________________________________________________________ Number: D500168112 Product: BUSINESS BASIC 32115A 02.1 One-line description: LIST * displays last line modified instead of executed Problem: LIST * displays the last line added or modified. It should list the last line executed. Cause: The "current" line number is being maintained separately from the information about the last executed line. When a line is added or modified, the current line number is set to the new line. LIST * is using the current line number, while other commands use the last executed line information. \ENTRY=SRD500168138 _______________________________________________________________________ Number: D500168138 Product: BUSINESS BASIC 32115A 02.1 One-line description: Control Y trapping inside interpreter varies according to load Problem: Business BASIC does not always respond to Control-Y if the statement which is the target of ON ERROR itself gets an error. For example, 10 ON ERROR GOTO 20 20 IF VAL("X") THEN 10 ! this statement gets an error 30 END Cause: This problem is caused by the ON ERROR condition taking precedence over Control-Y. While this may make sense when ON HALT is in effect, it should not override an attempt to interrupt the program when ON HALT is not in effect. Temporary solution: To work around the problem, make sure that the target of any ON ERROR statement does not itself cause an error. For example, 10 ON ERROR GOTO 19 19 Dummy=1 20 IF VAL("X") THEN 10 30 END \ENTRY=SRD500168161 _______________________________________________________________________ Number: D500168161 Product: BUSINESS BASIC 32115A 02.1 One-line description: DMPT when PRINTER IS statement is called from SUB if report is active Problem: A Data Memory Protection Trap occurs when a subprogram contains a SEND OUTPUT TO statement and a report is active in the main at the time the subprogram is called. If the subprogram is a compiled subroutine CALLed from an interpreted main, the interpreter aborts. The following example causes the trap: 10 BEGIN REPORT 100 ! report is now active 20 DETAIL LINE Jtest WITH 2 LINES ! start report output 40 CALL Xsub ! call the subroutine 50 END REPORT 60 END 100 REPORT HEADER WITH 3 LINES 110 PAGE HEADER WITH 1 LINES 130 REPORT TRAILER WITH 30 LINES 140 END REPORT DESCRIPTION 210 SUB Xsub 220 SEND OUTPUT TO "*printer" ! not legal after report 221 ! output has started 230 SUBEND Cause: This problem is caused by the check to see whether report output has started before performing the SEND OUTPUT TO. An uninitialized pointer is being referenced if a report is active whose BEGIN REPORT is in a different program unit. The trap may or may not occur dependin on the garbage contained in the pointer. Temporary solution: To work around the problem, move or remove the SEND OUTPUT TO statement which is illegal when output has started for a report. \ENTRY=SRD500172452 _______________________________________________________________________ Number: D500172452 Product: BUSINESS BASIC 32115A 02.1 One-line description: BBASIC truncates last byte of a file opened with CCTL Problem: Business BASIC treats records in files with CCTL as if they had 1 less byte than they actually have. This causes the last character in each record to be truncated when LINPUT into a Business BASIC program. For example: FILEX2 11B FAC 5 1023 25 48 1 * FILEX2 RECORD 0 (%0, #0) 0000: 2020 2020 2020 2020 2020 20 FILEX2 RECORD 1 (%1, #1) 0000: 0031 3233 3435 3637 3839 30 .1234567890 10 DIM A$[12] 20 ASSIGN #1 TO "filex2" 40 LINPUT #1,2;A$ 50 PRINT NUM(A$),A$ 100 ASSIGN * TO #1 This program prints 0 123456789 The trailing zero is not included in the data assigned to A$. Cause: This problem is caused by the Business BASIC library subtracting 1 from the record length when it opens a file that has CCTL, apparently in an attempt to adjust for the carriage control character. Temporary solution: To work around the problem, use fcopy to copy the file to a file with NOCCTL, or to a file with CCTL that has records which are 1 byte larger than those in the original file. \ENTRY=SR5000588012 _______________________________________________________________________ Number: 5000588012 Product: BUSINESS BASIC 32115A 02.0 One-line description: Enhancement request to modify warning message #2053 Enhancement text: Change warning 2053 to state that the runtime error will occur if the statement is executed. \ENTRY=SR5000630467 _______________________________________________________________________ Number: 5000630467 Product: BUSINESS BASIC 32115A 02.1 Keywords: HELP One-line description: Enhance the HELP catalog to be more clear on SETOFLD,SETCFLD,SETIFLD Problem: When doing a HELP interactively on the cursor-items { IFLD | OFLD | CFLD | SETIFLD | SETOFLD | SETCFLD } the text that comes up does not include any information about the fact that these functions can ONLY be called with the CURSOR verb. If you try to use the syntax as presented by HELP you will receive >SETCFLD(1) Setcfld(1) ^Error 68 Undefined variable or improperly used keyword. Enhancement text: The HELP text for the cursor functions (IFLD,OFLD,CFLD,SETIFLD,SETOFLD, SETCFLD) should be enhanced to clarify that these functions are only allowed in a CURSOR statement. \ENTRY=SR5000577387 _______________________________________________________________________ Number: 5000577387 Product: FORTRAN 77/V 32116A 02.0 One-line description: I/O ERR 915 with BZ format Problem: READ (1,10) FILENUMBER CHECKNUMBER CHECKFLAG (MF(I),D1(I),D2(I),I=1,70) 10 FORMAT (1X,A4,3X,A6,A2,70(BZ,I2,2I9)) is returning I/O ERR 915 READ UNEXPECTED CHARACTER intermittently at different points. Cause: The library code was looking one character too far when the BZ option was in effect when skipping blanks before a sign. Thus a garbage character was sometimes examined and therefore produced the error. \ENTRY=SR5000580258 _______________________________________________________________________ Number: 5000580258 Product: FORTRAN 77/V 32116A 02.0 One-line description: Problems with A2 format and repeat factors Problem: The A2 format does not appear to work correctly on output. Too many characters are emitted when an implied DO is used and the repetition factor on the A format does not match the DO factor. \ENTRY=SR5003224170 _______________________________________________________________________ Number: 5003224170 Product: FORTRAN 77/V 32116A 02.0 One-line description: Auto-open of file does not always work, WRITE or FNUM function fails Problem: The auto-open feature that allows files to be referenced without being explicitly OPENed does not work correctly for all cases. A WRITE or other simple function may fail unless the file is explicitly opened. The FNUM function will not properly return the file number for a unit that has not been opened. This may cause a program to fail when later attempting to use the referenced file number. Cause: The code changes for SR 5003-045310 were not fully copied for all the modules impacted by the change for auto-open. This should be fixed in the next patch release planned for late 1994. Temporary solution: As the auto-open feature is not working correctly, the program should explicitly open the unit prior to the call to FNUM or other file reference. \ENTRY=SRD500205781 _______________________________________________________________________ Number: D500205781 Product: FORTRAN 77/V 32116A 02.0 One-line description: HPEXTIN FORTRAN/V LIB routine does NOT error when passed "." Problem: HPEXTIN does NOT return an error when the input is only a period(.). Cause: It appears that a single period has always been allowed as a degenerate case of 0. or .0 thus ".". This has been corrected. \ENTRY=SRD500205799 _______________________________________________________________________ Number: D500205799 Product: FORTRAN 77/V 32116A 02.0 One-line description: HPINEXT returns "******" for short real -.9999995 with G12.6 Problem: A program that attempts to print a SHORT REAL number with the value of - 0.9999995 using HPEXTIN as G12.6 gets an error and prints ######## (pound or number signs). Cause: The problem is that a call to inext' with the value -0.9999995, format #3 (G), field width 12, and # decimal places = 6 results in a field overflow ("############"). The cause is that rounding of .9999995 to 1.0 is not properly handled by reducing the number of decimals to be printed by one. A similar problem occurs with the value .09999995 that rounds to .1 but is printed with the E format rather than the F format. The issue stems from the test for determining which format to use (E or F) and when rounding is to be applied. To be consistent with compatibility mode the code has been changed to check for the result of rounding near 0.1 and 1.0 before selecting the mode and number of decimals. Temporary solution: Increase the field width to 13 or reduce the number of decimals to 5 to avoid the problem. \ENTRY=SRD500205898 _______________________________________________________________________ Number: D500205898 Product: FORTRAN 77/V 32116A 02.0 One-line description: Arithmetic IF branching to a format statement is not detected. Problem: An Arithmetic IF branch to a FORMAT statement does not produce an error Cause: A generic routine could not check for the specific case if invalid label references for arithmetic IFs. Now a specialized version of the code will cause an error ILLEGAL USE OF LABEL (120) when the branch to a non-executable statement is seen. \ENTRY=SRD500205930 _______________________________________________________________________ Number: D500205930 Product: FORTRAN 77/V 32116A 02.0 One-line description: FSET will not allow Filenumbers greater than 254 (I/O error 975) Problem: FSET is getting the following error when the new file number parm is >= 255: FORTRAN I/O ERROR 975: ILLEGAL NEW FILE NUMBER REQUESTED IN FSET... Cause: The routines were using a constant 254 as a maximum file number. This used to be the maximum but is now larger for later MPE releases. For MPE/iX, 4.0 it should be 1023. Temporary solution: Close files so that no more than 254 are open at the same time. \ENTRY=SRD500205963 _______________________________________________________________________ Number: D500205963 Product: FORTRAN 77/V 32116A 02.0 One-line description: CANNOT OPEN FORTRAN 77 ERROR MESSAGE FILE FTNCAT.PUB.SYS Problem: Message "CANNOT OPEN FORTRAN 77 ERROR MESSAGE FILE FTNCAT.PUB.SYS" when attempting to print an error message. Cause: When the file system error of too many files opened has occurred, the error routine is unable to open the Error Catalog FTNCAT.PUB.SYS. This will be corrected by closing some files when the catalog is not opened successfully and then trying to open the catalog again. Previously, the error routine only tested for a specific condition of the FORTRAN IOSTAT value being equal to 908, before closing the files. \ENTRY=SR5000201285 _______________________________________________________________________ Number: 5000201285 Product: FORTRAN 77/V 32116A 00.0 Keywords: ERROR One-line description: Illegal constant substring parameters should be flagged at compile time Cause: The compiler has been enhanced to check for substring specifiers that are incorrect even if Range checking is not on. The error RANGE VIOLATION DETECTED AT COMPILATION TIME (504) will be produced. Temporary solution: The RANGE ON compiler option will detect the invalid substring specifier. Enhancement text: A compile time error should be generated on an incorrect character substring in a list-directed PRINT. \ENTRY=SR1650047688 _______________________________________________________________________ Number: 1650047688 Product: INFORM 32246A 03.0 Keywords: NLS One-line description: Wildcard characters do not work with other than Native-3000 language Problem: Wildcard characters are not recognized when using other than Native-300 language. Also, if the match condition is not "EQ" and the match field characters are "^"s and the match field length is less than the item length, then the record qualifies as a match when it should not. Cause: If the condition is not "EQ", then nlcollate is used to determine if th field is "LT" or "GT" for the match field, ignoring the wildcard characters. Temporary solution: There is no known workaround for this problem. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR5000045138 _______________________________________________________________________ Number: 5000045138 Product: INFORM 32246A 01.0 Keywords: INFORM One-line description: Using "^^" on two character fields does not work. Problem: When using the "^^" parameter to select records to be processed on data items of length less than three, the following message is given: INPUT FIELD IS LONGER THAN LENGTH OF FIELD. Thus "C^^" cannot be used to specify any fields containing "C" on a two character field. Cause: The algorithm is not correct when using "^^" on a field length that is less than the match length. Temporary solution: Use relational connector to select the items. For example: if you use "C^^" to try to select an item that is defined as X(2), this will NOT work. Use "C^ or ^C" as selection criteria. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR5000180232 _______________________________________________________________________ Number: 5000180232 Product: INFORM 32246A 02.0 One-line description: Inability to report on common element linked in flat files Problem: When there is no driver file and a link element (link value of 1) is used in a report along with other elements (all from flat files),INFORM cannot compile and produce the report. Cause: The algorithm for selecting a driving file is not correct. Instead of selecting the best driving file, it picked the first possible file. Temporary solution: By setting the required link item's link value to 0 and all of the other items link values to -1 to insure that they are not accessed at all, the correct data is retrieved. Also, adding a driver file will eliminate the problem. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR5000581033 _______________________________________________________________________ Number: 5000581033 Product: INFORM 32246A 05.0 One-line description: Wrong driving file when link item is not in the report Problem: INFORM is incorrectly choosing the driving file from an INFORM group when the link item is not included in the report. The INFORM group includes three datasets within 2 databases: BASE1 BASE2 -------------- --------------- Mast1 Mast2 link-item link-item item2 item3 Detl2 link-item item4 In the Dictionary, "link-item" in mast1 is the only element within the INFORM Group with a positive link value. INFORM should choose mast1 as the driving file, instead it is using "detl2." Cause: INFORM is not looking at the link item when it is not included in the report. This causes it to choose the wrong driving file. Temporary solution: The temporary workaround is to specify a secondary link item from the desired driving file that is included in the report. This will force INFORM to use the correct file as the driving file. Give the "real" link element a higher priority (i.e. 1) and the secondary link item a lower priority (i.e. 2). The secondary link item must be included in the report for the workaround to work. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR5000614958 _______________________________________________________________________ Number: 5000614958 Product: INFORM 32246A 06.0 Keywords: SELECTION One-line description: Incorrect selection criteria for 8-byte integer items and neg. values Problem: INFORM selects incorrect records when using an 8-byte negative integer for the selection criteria and the records contain negative values. Cause: The comparison was being done incorrectly for 8 byte negative integers. Temporary solution: There are no known workarounds for this problem. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR5003033977 _______________________________________________________________________ Number: 5003033977 Product: INFORM 32246A 07.0 One-line description: User-defined field, P(11,0,6), too small to handle calculation. Problem: DECIMAL OVERFLOW error when the results of a computed item needs more than 12 bytes of storage. For example, TO INCLUDE IN REPORT> + NEW DATA NAME> compute1 COMPUTATIONAL EXPRESSION> 400000 - 700000 * 915000 EDIT MASK> TO INCLUDE IN REPORT> 12 <> The report shows the following error message for COMPUTE1: *ERROR: DECIMAL OVERFLOW (PROG 47) and COMPUTE1 is 0 for every detail line. Cause: All computed items are defined as P(11,0,6), which may be too small in storage length for some calculations. Temporary solution: Verify that calculations do not need more than 11 bytes of storage. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR9999034204 _______________________________________________________________________ Number: 9999034204 Product: INFORM 32246A 00.0 Keywords: INFORM SELECT One-line description: Selection criteria with field type Z or P results in "no entries found" Problem: If a Z or P type item is a key of a data set and the data has been entered through Query, when selecting this item in the selection criteria, Inform will not find the item unless a '+' sign is used. Cause: Inform always overpunches the last character of a Z type item, while Query enters Z type data without the overpunch. Nonkey Z items work because Inform converts them to packed decimal before matching and so 321 and +321(represented by 32A internally) are the same. But key item are searched by calculated access, and 321 and 32A are different. Hence, the user must enter a '+' sign to select a key item if its value are entered thru Query. A P type item is kept in the database with its sign. Nonkey P items work correctly because they are converted prior to matching. P type items that are keys are searched by calculated access, 321 and +321 are different. Temporary solution: 1) Enter data by a TRANSACT DATA statement, or 2) Use '+' sign with the value at the selection prompt. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SRD500157255 _______________________________________________________________________ Number: D500157255 Product: INFORM 32246A 08.0 One-line description: References to "DATA BASE" should be changed to "DATABASE" in msg catalo Problem: The message catalog does not spell database as spelled in the TurboIMAGE manual. It is spelled "data base" currently in the message catalog. Temporary solution: Interpret "data base" as a reference to an TurboIMAGE database. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SRD500178111 _______________________________________________________________________ Number: D500178111 Product: INFORM 32246A 08.0 One-line description: Incorrect error message is displayed when a sort error occurs. Problem: The message WRITE FAILURE ON TRANSORT is misleading. INFORM does not use the file TRANSORT. Cause: The message catalog, RAPID000, was changed for Transact/V A.10.00. The message should be SORT FILE WRITE when running INFORM. Temporary solution: Modify the message in the RAPIDCAT catalog to be "SORT FILE WRITE". Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SRD500187492 _______________________________________________________________________ Number: D500187492 Product: INFORM 32246A 08.0 Keywords: TYPE INTEGER SELECTION One-line description: No records found when selection criteria is a 12-byte integer Problem: Inform selects no records when using a 12-byte integer for the selection criteria. Cause: The code is missing for 12-byte integer comparisons. Temporary solution: Use a different data type or an 8-byte integer. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A.10.00 \ENTRY=SRD500190108 _______________________________________________________________________ Number: D500190108 Product: INFORM 32246A 08.0 Keywords: SELECT KSAM One-line description: INVALID RECORD NUMBER (KSAM 184) when NM KSAM is used with FIRSTREC=1. Problem: Inform returns the following message when accessing KSAM/XL files where the first record is 1: "*ERROR: INVALID RECORD NUMBER (FFINDN INTRINSIC) (FSERR 184) Cause: KSAM/XL is not compatible with KSAM/V and KSAM/CM and Inform was designed to work with KSAM/V. More precisely, Inform performs an FPOINT to record 0 and expects a file system error 0 to occur if the KSAM file has been built with a first record of 1. KSAM/XL will return a file system error 184. Inform required changes to handle either product. Temporary solution: Temporary workaround is to rebuild the KSAM file with FIRSTREC=0 or to use compatibility mode KSAM. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SRD500199752 _______________________________________________________________________ Number: D500199752 Product: INFORM 32246A 08.0 Keywords: CALL REPORT INFORM One-line description: INFORM aborts with BOUNDS VIOLATION when PASSWORD = "]]". Problem: When calling REPORT or INFORM from Transact and responding "]]" to a REPORT or INFORM database prompt will result in a Bounds Violation. This only occurs in interactive mode, not in batch mode. In batch mode the user will receive the error message "ERROR: INVALID PASSWORD FOR DATA BASE: ". Cause: Transact aborts with a Bounds Violation when attempting to close the databases being accessed by REPORT or INFORM. Temporary solution: There is no temporary workaround for entering "]]" as a response to the password prompt of a called REPORT or INFORM program. Fix information: Fixed in Inform version A.10.00 and available on MPE V Release 40 and General Release patch INFDV79. Signed off 06/23/95 in release A10.00 \ENTRY=SR1650160531 _______________________________________________________________________ Number: 1650160531 Product: MODCAL-CM-LIBRARY 32047A 00.0 Keywords: OVERFLOW One-line description: Integer overflow in M'CAN'ESCAPE+16 if PARM is large on runtime error Problem: An integer overflow abort can occur for any type of Pascal runtime error if PARM is large, ~32K. Cause: The PARM word is stored in the stack in the same place as a DeltaQ. When the library is following stack markers in the case of an error it aborts when it subtracts the large PARM from Q. Temporary solution: Use the INFO string instead of PARM. Signed off 06/15/93 in release A00.04 \ENTRY=SR1653122564 _______________________________________________________________________ Number: 1653122564 Product: OPT 32238A 00.3 Keywords: OPT One-line description: [OPT DOES NOT DISPLAY OPEN FILE DETAIL FOR SOME FILES ON Platform 3P. Problem: Problem: In the Process display, open file detail is not displayed for certain files. the group and account are displayed as ******** ********. Cause: Cause: The problem is caused by a change that was made to Platform 3P of MPE V. Procedures GETFILENAME and FIND'DBU both validate that the FCB file being displayed is valid. One of the checks is to insure that (previously) UNUSED words in the FCB (File Control Block) are zero. The change to Platform 3P allocates the previously unused words in the FCB, so it is no longer zero. Temporary solution: There is no temporary work around. \ENTRY=SR1653056507 _______________________________________________________________________ Number: 1653056507 Product: RPG 32104A 08.0 One-line description: Sigedit delete form causes corruption in form list. Problem: Customer needs to modify a formfile using SIGEDIT (A.08.06). He has a formfile which resides in a runtime environment and is developing/modifying forms in his own formfile. He needs to replace some forms in the runtime formfile (delete form / copy form). The problem is the following: if customer tries to delete a form (whatever form in the formfile), SIGEDIT will delete the last form in the formfile and duplicate the first form. If SIGEDIT doesn't produce this strange result, it will fail in **** PROGRAM ERROR #18 :PROCESS QUIT .PARAM = 20305 ABORT: SIGEDIT.PUB.SYS NM SYS a.009d3180 dbg_abort_trace+$24 CM SYS % 213.7323 SWITCH'TO'NM'+%4 SUSER1 CM PROG % 0.340 CHK_FILE_ERROR+%70 SEG00 PROGRAM TERMINATED IN AN ERROR STATE. (CIERR 976) on file SIGSORT and the first form name will become 1*******. Cause: SIGEDIT keeps the forms in the forms-file in sorted order to improve the overall search speed when looking for a new form. When a form is deleted, a variable containing the number of forms is decremented, but for the sort process, the original number of forms should have been used. This could cause the sort to get out of sync, thus causing forms to be lost, or in some cases resulting in aborts. \ENTRY=SR4700945998 _______________________________________________________________________ Number: 4700945998 Product: RPG 32104A 08.0 One-line description: SIGEDIT forms file with messages merged still requires FILE CATALOG= Problem: If user messages (from either an MPE or NLS catalog) are merged into a forms file by SIGEDITOR, then it should not be necessary to issue a fil equation for the formal file name "CATALOG" for the forms file to be opened by an RPG program. But, the RPG program aborts with "RPG Error: Open of user messages CATALOG file failed." The program can be made to work by first equating file CATALOG to $NULL (or anything else that can be opened at runtime.) Related SR's are: 5000-442517 and 4700-946004. Cause: The run-time library routine used to open the message catalog failed to check a variable in the forms file that specified whether or not mess- ages had been merged. As a result, an attempt was always made to open the message catalog. Temporary solution: Issue the following file equation prior to running the RPG program: :FILE CATALOG=$NULL \ENTRY=SR4700946004 _______________________________________________________________________ Number: 4700946004 Product: RPG 32104A 08.0 One-line description: SIGEDIT forms file using unmerged NLS catalog gets BOUNDS VIOLATION Problem: When a SIGEDITOR forms file uses message fields, and a Native Language Support (NLS) catalog is referenced at runtime via a :FILE CATALOG= command, the RPG program aborts with a BOUNDS VIOLATION (at library offset %14440.) This occurs after the first screen is displayed (although all the mes- sage fields contains blanks!) and the user hits the F1 (Command) key. There is no problem when using an MPE catalog file instead of NLS. (Related SR's are: 5000-442517 and 4700-945998.) Cause: A parameter for the CATREAD intrinsic (used to access the NLS catalog) was not properly set. Temporary solution: Create the catalog file using the MPE MAKECAT utility, rather than the NLS GENCAT program, and reference the resulting file with FILE CATALOG= at runtime. \ENTRY=SR4701003004 _______________________________________________________________________ Number: 4701003004 Product: RPG 32104A 08.0 One-line description: SIGEDIT: Convert S & D specs with > 255 D-specs in form aborts w/hang. Problem: When converting an S & D file to an RPG forms file using SIGEDIT, if a form in the file contains more than 255 D-specs (fields and constants), SIGEDITOR aborts and may leave the terminal hung. It should issue an error message and exit gracefully. \ENTRY=SR5000434175 _______________________________________________________________________ Number: 5000434175 Product: RPG 32104A 07.0 One-line description: Hangs if locking and with the RECORD NUMBER ADJUST on flat file Problem: Customer has RPG version A.07.04, MPE version G.03.01. Experienced job and session hangs when RPG programs accessed files opened in LOCK and SHR mode. Application program was accessing an MPE direct-access files with the RECORD NUMBER ADJUST feature (column 22 of the H-spec) turned on. Additionally, he was doing a KLOCK on the file so that the file was locked immediately before it was read. Apparently, if the relative record number supplied to the direct-access file was equal to zero, the number would be adjusted to a -1. A chaine read of the file with record number -1 would result in a record not found and the file would remain locked. One workaround would be to add an UNLCK statement in the C-specs to unlock the file if this situation arises. \ENTRY=SR5000442517 _______________________________________________________________________ Number: 5000442517 Product: RPG 32104A 08.0 Keywords: CATALOG One-line description: SIGEDITOR: MERGE CATALOG fails if catalog created w/GENCAT. MAKECAT OK Problem: Sigedit will not MERGE CATALOG a form file with a catalog file created by GENCAT.PUB.SYS. It will only MERGE CATALOG with a catalog file created by MAKECAT.PUB.SYS. According to the documentation, it should merge with a catalog created by either program. If MERGE CATALOG is used with GENCAT, the message field of the SIGEDIT screen remains blank and the set and message fields of the field attributes are zeroed out. When PROCMON is run to PROMPT the formfile to appear, the optional parameters of the PROMPT command START and LENGTH are no longer optional if you want the message to appear in the message field. See also SR4700-945998 regarding the need for a file equation for the catalog file. Cause: The original design of SIGEDITOR only used the intrinsics for MAKECAT. The ability to use message files from GENCAT was never there. If the messages were not merged, and the message file was accessed from the RSI application, then either MAKECAT or GENCAT files would work OK. Temporary solution: Either do not merge messages into the forms file or do the merge from an MPE message file rather than NLS. \ENTRY=SR5000480210 _______________________________________________________________________ Number: 5000480210 Product: RPG 32104A 08.0 Keywords: SYNTAX One-line description: Convert S&D screen allows a "fileset" but the screen text says filename Problem: In SIGEDIT, the "convert S & D" screen allows you to enter a fileset, but the screen text says "file name". It should be made clear that filesets are also allowed. \ENTRY=SR5000622050 _______________________________________________________________________ Number: 5000622050 Product: RPG 32104A 08.0 One-line description: SIGEDIT Screen Corrupts after Adding 20 1-Position Fields Problem: SIGEDITOR (A.08.04) corrupts form when adding to a very large form. Corruption seen after adding 120th field to form. Corruption appears after the ENTER key is hit on the EDIT FORM screen. When ENTER key is hit, edits do not seem to be accepted. Cursor is moved to a different line and ENTER is pressed again. Form is accepted, but when the user returns to edit the screen again, the literal fields have shifted down one or more lines, thus corrupting the screen. Cause: A buffer used in the FREAD to get information on a modified line was not large enough to hold all the necessary characters. This placed a limit of about 19 fields on a given line. The buffer has now been expanded to allow up to 40 fields on a line. \ENTRY=SR5000622068 _______________________________________________________________________ Number: 5000622068 Product: RPG 32104A 08.0 One-line description: Adding fields to SIGEDIT screen result in field name of 3, Seq No 2000 Problem: SIGEDITOR (A.08.04) places a 3 in the fieldnumber of a field and gives it a sequence number of 2000. This occurs for 4 fields added to a very large SIGEDIT form. The form consisted of 112 fields. When user went back and added 6 new fields, the last 4 fields had the problem. Cause: SIGEDIT was incorrectly managing an internal buffer, causing valid entries to be overwritten with other data. This occurs only on very large forms. The problem was noted on a form containing 112 fields and 72 constants for a total of 184 items. Adding one more constant caused the problem. Since we allow a maximum of 256 entries, this should be allowable. The management of the internal buffer, however, relied on no. fields + 2*no. constants <= 256, which is not the case here (112 + 2*73 = 258). Hence the loss of data. \ENTRY=SR5000662403 _______________________________________________________________________ Number: 5000662403 Product: RPG 32104A 08.0 One-line description: SIGEDIT file with signed numeric fields shows diff. length on A.08.05 Problem: SIGEDIT forms file created under VD2 using signed numerics fields report different field lengths on version A.08.05 of MPE/XL 2.2 using PRINT SPECS and GEN I/O specs. GEN I/O SPECS is correct. \ENTRY=SR5003009670 _______________________________________________________________________ Number: 5003009670 Product: RPG 32104A 08.0 One-line description: SIGEDIT will corrupt form name when deleting a form. Problem: SIGEDIT corrupts form name to "1*****" under the following conditions: There are only two forms in the file. The first form is then deleted. Cause: SIGEDIT keeps forms in sorted order in order to rapidly access a given form. For the case of two forms in a forms-file, where the first form was deleted, leaving one form, it decided that for one form no sort was needed. This resulted in the loss of the 2nd form, with the first form renamed "1*******". This name is actually the 'flag' used by the sort routine for a form to be discarded. \ENTRY=SR500321501 _______________________________________________________________________ Number: 5003215012 Product: RPG 32104A 08.0 One-line description: RSI needs ability to open port with 4 digit LDEV Problem: RSI applications run on terminals with LDEV numbers greater than 999 will immediately terminate with no error or warning message. Cause: The FOPEN intrinsic originally designed for the classic HP3000 (using MPE/V) specifies the LDEV parameter to be a 3-digit numeric string. The RPG RSI interface was designed with this restriction, with the result that 4-digit (or more) LDEV numbers are truncated on the left. Since the FOPEN then cannot find an appropriate terminal, it simply forces the program to terminate. \ENTRY=SR1650017103 _______________________________________________________________________ Number: 1650017103 Product: TRANSACT 32247A 02.0 Keywords: NEED DISPLAY One-line description: NEED= does not work when NEED group starts on the last line on page Problem: The NEED= option of the FORMAT verb is not working when DISPLAY is printing the last line of data on a page. Cause: Transact does not check the NEED= value when printing the last line of a page. Temporary solution: There is no workaround. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR1650159327 _______________________________________________________________________ Number: 1650159327 Product: TRANSACT 32247A 08.0 Keywords: DISPLAY FILE ROW One-line description: Row format of DISPLAY does not work if FILE=filename is used. Problem: Doing a DISPLAY(FILE=filename) itemname,ROW=10 does not skip rows when writing to a file. This works correctly for Transact/XL NM. Transact/V & /CM work correctly if outputting to the terminal. Cause: The section of code that writes out the blank lines is being by-passed when writing to a file. Temporary solution: The LINE function can be used instead of the ROW function to accomplish the desired task. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000225086 _______________________________________________________________________ Number: 5000225086 Product: TRANSACT 32247A 03.0 Keywords: KSAM PARTIAL KEY One-line description: Partial key (generic) access does not retrieve the expected records Problem: Customer application is used to inquire into a KSAM file. The first value entered as the key is found. When a second value is entered, it finds the record after the value requested. When the full key value is used, the correct data is obtained. Partial keys locate the incorrect records. Cause: The find is using an exact match, and as a result, fails to find keys i which a portion of the key was specified as the argument. Temporary solution: There are two workarounds: 1. Define a child item of the full search key and use the child item for the SET(KEY) statement. For example, if the child item is X(3) and a search value of '110' is used, all the records having '110' in the first 3 bytes are retrieved. 2. Use SET(MATCH) with GE, LT or other options along with SET(KEY) of the full key. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000268235 _______________________________________________________________________ Number: 5000268235 Product: TRANSACT 32247A 03.0 Keywords: KSAM GET One-line description: GET(CURRENT) does not retrieve the last entry written to a KSAM file Problem: When using GET(CURRENT) after doing several PUTs and DELETEs to a KSAM file, sometimes the current record retrieved is not the correct one. Cause: The record pointer is positioned to the next record in key sequence whe a record is PUT to a KSAM file, rather than to the record just added. Temporary solution: There is no temporary workaround identified. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000462366 _______________________________________________________________________ Number: 5000462366 Product: TRANSACT 32247A 06.0 Keywords: LET One-line description: LET of zero from 9,I,J,K,P,R,E types into X,U types results in blanks. Problem: Using the LET verb to assign the value 0 from an item with the data type of 9,I,J,K,P,R, or E to an item with a data type of X or U will result in blanks instead of a single ascii zero. Cause: When assigning zero to a character field, the zero is considered a leading zero. The leading zero is stripped off and a blank assigned to it. Temporary solution: Use the MOVE verb to assign a numeric data type to a character data type. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000534313 _______________________________________________________________________ Number: 5000534313 Product: TRANSACT 32247A 07.0 Keywords: RETURN FIND One-line description: RETURN(@) leads to infinite loop in TRANSACT/V; no looping in TR/XL Problem: RETURN(@) in the PERFORM routine of a FIND(SERIAL) leads to an infinite loop in Transact/V. For example: Find(serial) flat1,list=(lll),perform=p1; exit; p1: display lll; return(@); end; In the above case Transact would be continuously reading the first record of file flat1. Cause: RETURN(@) in a FIND(SERIAL) prematurely closes the file and the next find starts at the beginning of the file again. Temporary solution: Use only RETURN when returning from one level of PERFORM. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000553842 _______________________________________________________________________ Number: 5000553842 Product: TRANSACT 32247A 07.0 Keywords: CURSOR GET One-line description: CURSOR= option on PUT/GET(FORM) displays error "Cannot place cursor". Problem: When a PUT(FORM) positions the cursor into a display only field, a subsequent call to GET(FORM) will return an error: "Cannot place cursor to display only fields (VPLUS 800,25,FORM)" Cause: Transact saves the last cursor position from a SET(FORM) verb so subsequent GET(FORM) or PUT(FORM) verbs place the cursor in the proper field. PUT(FORM) and SET(FORM) erroneously set the last cursor position, causing the error. Temporary solution: After doing the GET(FORM) or a PUT(FORM) with a CURSOR= option, do a SET(FORM) to clear the last cursor position. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000562496 _______________________________________________________________________ Number: 5000562496 Product: TRANSACT 32247A 08.0 Keywords: DEFINE DICTIONARY One-line description: No warning for Dictionary item names > 16 chars which migration issue. Problem: Transact/iX provides a warning when item names from the Dictionary are greater than 16 characters. Transact/V and Transact/CM provide no such warning. Cause: Transact/V and Transact/CM check item name lengths when parsing the DEFINE and LIST verbs. Unfortunately, this will not detect undefined items or unlisted items. When a customer migrates to Transact/iX, the Transact/iX compiler issues a name truncation warning to alert the programmer of the compatibility problem. Temporary solution: When an item name of greater than 16 characters causes a warning by the Transact/iX compiler, change the item name to 16 or less characters Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000601179 _______________________________________________________________________ Number: 5000601179 Product: TRANSACT 32247A 08.0 Keywords: ERROR MESSAGE LET One-line description: TRANSACT V: Incorrect error when using type X items in LET statement. Problem: TRANSACT/V gets "*ERROR: **** INVALID ERROR NUMBER - PLEASE REPORT " after an expected "INVALID ARITHMETIC FIELD FOR ITEM" error. For ex: define(item) name x(80): first x(80): small x(1)=first(1); list name: first; move (name) = "hello my name is "; move (small) = "s"; let (name) = (name) + (small); Cause: The problem is caused by the fix for SR 4700-829614 in which TRANSACT was altering the SOURCE item in a LET statement when it had an invalid number. For example, using "LET (num1) = 1+(str1);" with "str1" equal to "s", would change "str1" to 0. The fix for the above SR changed thi so that the source field (str1) was left alone. For the current SR, this means that after the LET, the item str1 still has "s". The code path for LET depended on str1 being cleared. Since it now is not, a trap occurs and the INVALID ERROR NUMBER is generated. Temporary solution: The temporary workaround is to use the ERROR= option on the LET which has the error. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5000705046 _______________________________________________________________________ Number: 5000705046 Product: TRANSACT 32247A 09.0 Keywords: DISPLAY CLOSE One-line description: DISPLAY(FILE=xxx) command, close the spoolfile, get FSERR 0 Problem: When the following conditions occur, a CLOSE will result in a file system error 0. * A file is not the first named file in the SYSTEM statement. * TRANLIST is redirected to a printer. * A display has been performed to the named file. Cause: The events named in the problem text cause the Transact processor incorrectly interpret the state of the MPE/KSAM file. Transact returns an error, and the file is not closed. Temporary solution: Do not redirect output to a printer while using a display to a file. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5003004382 _______________________________________________________________________ Number: 5003004382 Product: TRANSACT 32247A 09.0 Keywords: DISPLAY One-line description: Trailing "-" interpreted as hyphen, not as optional sign character. Problem: The fix to SR 5003-002303 for version A.08.05 causes the trailing "-" to work differently than the trailing "CR" for a "9" data type. The trailing "-" is now displayed for for all values. Cause: The fix for SR 5003-002303 causes the DISPLAY verb to edit items of a "9" data type as a character ("X" or "U") data. The items of a "9" data type should be edited as a numeric ("Z", "P" or "9") data. Temporary solution: Move the data to a "Z" type item before displaying the data. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5003071332 _______________________________________________________________________ Number: 5003071332 Product: TRANSACT 32247A 08.0 Keywords: FORMAT One-line description: FORMAT verb's CCTL is applied to previous item instead of current item. Problem: Given the following two statements: 1. FORMAT "Line-1": "Line-2",cctl=65: "Line-3",cctl=66; 2. DISPLAY(file=fname); The carriage control for "Line-2" will be erroneously applied to "Line-1", and the carriage control for "Line-3" will be erroneously applied to "Line-2". The literal "Line-3" will have no carriage control applied. Cause: The logic for applying the CCTL option of the FORMAT verb is off by one. Carriage control is applied to the item preceding the item with the CCTL option. Temporary solution: 1. Use the LINE= or the PAGE= option instead of the CCTL= option. 2. Add an empty CCTL= option in the format verb to adjust the CCTL specifications: This format statement: FORMAT "Original format specification",CCTL=0; becomes: FORMAT " ",CCTL=1: "Original format specification",CCTL=0; NOTE: If using workaround #2, you will need to change your program when this problem is fixed. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR9999203042 _______________________________________________________________________ Number: 9999203042 Product: TRANSACT 32247A 02.0 Keywords: LET SQRT One-line description: LET RESULT = SQRT(X) does not work when RESULT is type 9 or X or Z. Problem: Square root function works inappropriately when the destination item is type 9, Z, or X. Cause: While evaluating the expression "LET (Z-TYPE) = SQRT (Y);", conversion from the square root value of Y to Z (also X and 9) type is not done correctly. Temporary solution: Please continue using the temporary workaround as follows: 1. Initially, assign the square root value to R-Type. 2. Assign this R-Type to 9, Z, or X type. For an example, LET (R-Type) = SQRT (number); LET (Z-Type) = R-TYPE; Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500121905 _______________________________________________________________________ Number: D500121905 Product: TRANSACT 32247A 08.0 Keywords: LET One-line description: LET (positive-real) = (-1 or (Neg'Item'Value)) produces no error. Problem: For the LET verb, the value assigned to a positive only real (R+) is not checked to verify that it is a positive value. Some confusion may result by using the DISPLAY verb to test the positive real (R+) value. The DISPLAY verb will not print out an R+ value if it is negative. The negative value, however, is still there and usable in subsequent LET verbs. Cause: Transact/V has conversion routines for types "R" and "E" and conversion routines for all other data types. The conversion routines for "R" and "E" data types allow negative values to be loaded into a positive value only (R+, E+) item. Temporary solution: Programs may check for a value less than zero to enforce the positive only values in R+ and E+ items. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500132365 _______________________________________________________________________ Number: D500132365 Product: TRANSACT 32247A 08.0 Keywords: DISPLAY One-line description: DISPLAY to screen & file causes linecount errors and no CONTINUE (Y/N). Problem: Use of DISPLAY to a screen and DISPLAY to a file will cause erratic line counting, irregular page breaks, and missing CONTINUE Y/N? prompts Cause: When a page break occurs on the DISPLAY verb to a file, the line counter for the DISPLAY verb to a screen is also set to one. Temporary solution: No temporary workaround has been identified for this problem. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500132399 _______________________________________________________________________ Number: D500132399 Product: TRANSACT 32247A 08.0 Keywords: DISPLAY $PAGE TPRINT One-line description: DISPLAY to a file uses blocking factor as first PAGE number. Problem: If a blocking factor is specified for a file in the SYSTEM statement, then the file is used in a DISPLAY to a file, first page number will be equal to the blocking factor from the SYSTEM statement. Cause: The DISPLAY to a file and SYSTEM statement use the same memory location. The blocking factor left behind by the SYSTEM statement is not properly reset to 1. Temporary solution: Do not specify a blocking factor on a file which is to be used with the DISPLAY verb. If necessary, use an MPE file equate to specify the blocking factor externally. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500138578 _______________________________________________________________________ Number: D500138578 Product: TRANSACT 32247A 08.0 Keywords: LIST One-line description: Continuous error message loop when INIT value > display length. Problem: If a DEFINE verb with an INIT= has the correct number of display characters, but the number does not fit into the storage allocated, Transact/V and Transact/CM will print the error message "*ERROR: INPUT FIELD LONGER THAN " in a continuous loop until the Transact processor is aborted. The following lines will cause an infinite loop at runtime: DEFINE(ITEM) integer i(5,,2), init=32768; LIST integer; Cause: Transact does not properly distinguish between the LIST verb with an INIT= option and the PROMPT verb. Transact incorrectly attempts to re-prompt a user for a valid number, then INIT= always provides the sam invalid number. The cycle continues until Transact is aborted. Temporary solution: Correct the program statement which is in error. The error message provides the information necessary to correct the Transact program. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500144121 ________ ______________________________________________________________ Number: D500144121 Product: TRANSACT 32247A 09.0 Keywords: OUTPUT SORT One-line description: SORT= option on OUTPUT(SERIAL) is not displaying results in sorted orde Problem: The SORT option on OUTPUT(SERIAL) does not work if the sort item specified is defined more than once in the LIST register. Cause: The cause of the SORT on OUTPUT(SERIAL) not working correctly is that TRANSACT sorts on the first occurrence of the item in the LIST register, while the data is read into the latest occurrence of the item. It only affects programs where the sort item has been added to the LIST register multiple times. Temporary solution: Depending on the program the workarounds are: 1) Rename the sort item to a unique name 2) Use RESET(STACK) LIST to reset the LIST register prior to adding the sort item to the register Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500153809 _______________________________________________________________________ Number: D500153809 Product: TRANSACT 32247A 09.0 Keywords: PROMPT One-line description: PROMPT(SET) gives invalid data with CHECK= option and carriage return. Problem: When the "PROMPT(SET) ,CHECK= " verb, modifier, and option are used without the STATUS option, then incorrect data may be returned to the item after the PROMPT(SET) completes. Cause: When PROMPT(SET) is used, Transact/V will add the item to the list register. If a user replies with a carriage return, PROMPT(SET) will mismanage the list and data registers, causing data from the wrong item to be returned. Temporary solution: You may use one of the following workarounds: * Use the PROMPT verb without the SET modifier with the CHECK option. * Use the DATA(SET) verb when using the CHECK option. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500155200 _______________________________________________________________________ Number: D500155200 Product: TRANSACT 32247A 09.0 Keywords: CALL One-line description: Bad database reference (-11) if main program uses over 32k bytes stack. Problem: When a Transact program uses more than 32768 bytes of MPE/V stack space for the data register and the Transact/V program file, CALLed Transact subprograms will pass a blank (BASE) parameter for PROC verb until the associated database has been accessed by a Transact verb. Cause: When the main program data and code exceeds 32768 bytes, Transact/V and Transact/CM will open databases in CALLed subprograms when the database are first accessed by a Transact verb. This is why the (BASE) paramete to the PROC verb is invalid until the database is used by a Transact verb. Temporary solution: 1. Execute a Transact verb for the database within the subprogram before using the (BASE) construct of the PROC verb. 2. Reduce the program or data register size of the main program which calls the subprogram. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500160077 _______________________________________________________________________ Number: D500160077 Product: TRANSACT 32247A 09.0 Keywords: LIST PASSWORD One-line description: Passwords are not passed correctly to sub-programs. Problem: A problem exists when a variable is passed to a subprogram, and the subprogram is using the 'LIST x,PASSWORD' option where the passed password should be moved to 'x'. The correct password is not moved to 'x'. If a string is used in the CALL statement, the correct password IS moved to 'x'. Cause: The cause of the problem is that when a variable is passed as a password to a subprogram, it is passed as a structure, and not a string. In the subprogram it is treated as a string. Temporary solution: The only known workaround to this problem is to use a string instead of a variable in the calling program (CALL SUB("XX",.. instead of CALL SUB(x,..), if possible. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500168252 _______________________________________________________________________ Number: D500168252 Product: TRANSACT 32247A 09.0 Keywords: LET VALUE One-line description: Get INTEGER OVERFLOW when LET (I) = maximum negative integer. Problem: Get an integer overflow error if the source code assigns the maximum negative integer constant to an integer item of either 2 or 4 bytes. The program below shows 2 source statements that will cause this run-time error. SYSTEM OVERFL; DEFINE(ITEM) I2 I( 5,,2): I4 I(10,,4); LIST I2: I4; LET (I2) = -32768; << but OK if use -32767 >> LET (I4) = -2147483648; << but OK if use -2147483647 >> EXIT; Starting with version A.10.00, this problem also applies to the new VALUE function of the MOVE verb. Cause: A call is made to the BINARY intrinsic for a 2 byte integer and DBINARY for a 4 byte integer to convert the number. However, before the intrinsic is called, the minus sign is stripped so that the absolute value of the number is used. This creates a problem since BINARY works on -32768 to 32767, but not 32768. Similarly, DBINARY is valid for -2147483648 to 2147483647, but not 2147483648. Temporary solution: Avoid using the numbers -32768 for 2 byte integers and -2147483648 for 4 byte integers in your Transact/V source code. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500183905 _______________________________________________________________________ Number: D500183905 Product: TRANSACT 32247A 09.0 Keywords: MATCH One-line description: Match with wildcards is not handled properly when condition is not "EQ" Problem: If the match condition is not "EQ" and the match field characters are "^"s and the match field length is less than the item length, then the record qualifies as a match when it should not. Additionally, if using other than Native-3000 language, the wild card character is not recognized. It is merely collated along with the othe characters. Cause: If the condition is not "EQ" then nlcollate is used to determine if the field is "LT" or "GT" for the match field, ignoring the wild card characters. Temporary solution: There is no known workaround available. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500186171 _______________________________________________________________________ Number: D500186171 Product: TRANSACT 32247A 09.0 Keywords: LIST One-line description: LIST item,PASSWORD in a subprogram may return garbage. Problem: When a subprogram has the password provided as a CALL parameter, the LIST item,PASSWORD statement in the subprogram will return an uninitialized value. Cause: The area which contains the first password is not set to the correct value until a user is prompted for a password. Temporary solution: Use the PASSWORD initialization option only when the program prompts a user for the PASSWORD. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500186452 _______________________________________________________________________ Number: D500186452 Product: TRANSACT 32247A 10.0 Keywords: TYPE INTEGER MATCH One-line description: Incorrect matching criteria for 8-byte integer items and negative value Problem: Incorrect records are selected when using an 8-byte negative integer in SET(MATCH), DATA(MATCH), or PROMPT(MATCH) statements. The records matched against also contain negative values. For example: DEFINE(ITEM) aitem I(18,,8); PROMPT(MATCH) aitem; When running Transact, the user is prompted and enters selection criteria: AITEM> lt -200 The results are: And should be: AITEM: AITEM: -199 -300 Cause: The comparison was being done incorrectly for 8 byte negative integers. Temporary solution: There are no known workarounds for this problem. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500187245 _______________________________________________________________________ Number: D500187245 Product: TRANSACT 32247A 10.0 Keywords: MATCH FIND GET TYPE INTEGER OUTPUT DELETE One-line description: No records found when selection criteria is a 12-byte integer Problem: No records are found when retrieving data that is based on a 12 byte integer value in the match register. GET, FIND, OUTPUT, and DELETE statements will return 0 records erroneously. For example, prompt(match) item1; output(serial) tfile,list=(item1); exit; Results in, 0 RECORDS FOUND Cause: The code is missing for 12-byte integer comparisons. Temporary solution: Reset the match register and do the comparison within the retrieval loop. For example, data item-in; reset(option) match; find(serial) tfile,list=(item1:itemn),perform=compare; compare: if (item1) > (item-in) then display "greater"; return; Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500189811 _______________________________________________________________________ Number: D500189811 Product: TRANSACT 32247A 10.0 One-line description: REWIND of KSAM file fails if first record is marked for deletion. Problem: A KSAM file is not repositioned to the beginning when the automatic rewind for a SERIAL access command is performed by TRANSACT if the firs record is marked for deletion. For example, an OUTPUT(SERIAL) will only output the records from the last access position instead of rewinding to the beginning. Cause: The FPOINT done to position the file at the beginning fails if the firs record pointed to is marked for deletion. No error is returned and the pointers are not re-positioned. Temporary solution: No temporary workaround has been identified. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SRD500190389 _______________________________________________________________________ Number: D500190389 Product: TRANSACT 32247A 09.0 Keywords: REPLACE One-line description: REPLACE does not update KSAM records when item order not physical order Problem: When items are not specified in the order of the physical record, the REPLACE verb will not update the MPE or KSAM file with the data in the data register. Cause: When the list does not include all items in their order of occurrence in the physical record using an "@" list or a range list, Transact will buffer the record on file input and file output. Transact does not transfer the data from the data register into the input/output buffer during a REPLACE verb, so Transact updates the record with the original data read from disc. Data is transferred from the UPDATE register to the input/output buffer so using the UPDATE register works for all lists. Temporary solution: 1. Use the SET(UPDATE) statement in the PERFORM= routine to specify th item to be used for the update. 2. Use a range list with all items in the physical record order, or use the "@" list. Fix information: Fixed in Transact/V version A.10.02 and available on MPE V Release 40 and General Release patch TRVDV78. Signed off 06/23/95 in release A10.02 \ENTRY=SR5003214494 _______________________________________________________________________ Number: 5003214494 Product: DSN/CS 30131A 55.3 One-line description: SHOWCOM cannot be ALLOW'd in 3P, workaround available with SLPATCH Problem: Cannot :ALLOCATE the :SHOWCOM command. Cause: This problem was caused by a value being defined in the CS subsystem instead of allowing it to be defined in the INCLUDE file. This problem was introduced in Release 31 and also exists in Release 3P. Temporary solution: The SHOWCOM command is not executing even after an Allow from the master operator console. The SHOWALLOW indicates the command is available to the user. However, trying to executed the command results in a CIERR4307. This does not occur under MPE V/E R23. This problem is occurring on MPE V/E 3P. The workaround is to run a PRIV MODE program which sets all the capabilities on and, for obvious reasons, he'd like to not do that. Easy to duplicate: From the system console on ZEUS: (3P) :showcom 15 LDN - 15 MESSAGES SENT 5570 MESSAGES RECVD 2438758 LAST RECOVERABLE ERROR 0 LAST IRRECOVERABLE ERROR 0 LINE IS CONNECTED (more not shown) :ALLOW @.@;COMMANDS=SHOWCOM Now same showcom command from another session: SHOWCOM 15 OPERATOR REQUIRES PERMISSION VIA THE ALLOW OR ASSOCIATE COMMANDS. (CIERR 4307) :showallow #S300 MANAGER.SYS USER HAS THE FOLLOWING COMMANDS ALLOWED: LOG SHOWCOM It thinks it's there but you just can't do it. Tried to ASSOCIATE class LANIC to a vanilla account, mgr.pvs: :run asoctbl5 ASOCTBL5 G.03.07 (C) >lanic = mgr.pvs >exit Then from MGR.PVS: :showcom 15 EXECUTING THIS OPERATOR COMMAND BY OTHER THAN THE MASTER OPERATOR REQUIRES PERMISSION VIA THE ALLOW OR ASSOCIATE COMMANDS. (CIERR 4307) That doesn't work either.. Confirmed it works fine on Release 30. Temporary workaround is as follows: We can fix this code in COMSYS1 306.4250 021055 "- LDI 45 can be changed to: 306.4250 021050 "- LDI 40 RUN SLPATCH.PUB.SYS (as MANAGER.SYS) ?COMSYS1,D,4250,1 to display the value, it must be 21055. 021055 ?COMSYS1,M,4250,1 021055 _ 021050 Then make a COLDLOAD tape and boot from it. ?exit \ENTRY=SR4701212753 _______________________________________________________________________ Number: 4701212753 Product: MPE 32002C 00.0 One-line description: SEGMENT TABLE OVERFLOW (LOAD ERR 70) due to fragmentation of LST Problem: Several MPE/iX systems were consolidated onto a single 980-400. Up to 450 users were running a wide variety of CM programs. Eventually, some users got the following error messages when attempting to run CM progra files. SEGMENT TABLE OVERFLOW (LOAD ERR 70) UNABLE TO LOAD PROGRAM TO BE RUN. (CIERR 625) Cause: Garbage list management for the CM Loader Segment Table (CM LST) causes large free entries to be carved up into many small free entries. This is particularly true when a large variety of CM programs are being continually loaded and unloaded. Eventually, the CM LST becomes so fragmented that there are no entries large enough to load a CM program file -- even though the total free space is > 35% of the CM LST. Temporary solution: There is no workaround for this problem. Signed off 08/02/94 in release G12.00 \ENTRY=SR4700102616 _______________________________________________________________________ Number: 4700102616 Product: MPE V/E 32033G 0X.1 Keywords: SPOOK One-line description: SPOOK should print SECURITY VIOLATION, not FILE NOT FOUND Problem: For users with limited capabilities, SPOOK searches for spoolfiles by USER.ACCT. For example, if >S #O14 is entered, it would look for devic file ID 14 under USER.ACCT. If the spoolfile exists but belongs to som other user, it prints "The specified file was not found. (SPERR 31). Temporary solution: There is no temporary work around for this problem. \ENTRY=SR4701222745 _______________________________________________________________________ Number: 4701222745 Product: MPE V/E 32033G 11.0 Keywords: SF2559 One-line description: SF16 or 59 if 1st accessor of msgfile run w/ NOCB and uses ;COPY Problem: When a message file is opened with COPY and NOBUF mode by an applicatio running with NOCB, the exclusive access mode was not handled correctly. The second accessor could have the same message file open in the native mode. And if the first accessor closes the file prior to the second accessor, it causes system abort 2559 when the second accessor is tryin to FCLOSE that message file. Cause: When a message file is opened in copy mode, the FCB is normally created on a process stack. However, it is not true if an application is runnin with NOCB. In that case, it is created on a DST. Therefore, the second accessor bypassed the check which would normally fail if it has been accessed in copy mode. Temporary solution: Do not run programs that access message files with ;NOCB \ENTRY=SR4701240150 _______________________________________________________________________ Number: 4701240150 Product: MPE V/E 32033G 00.0 One-line description: MPE allows more than 2 chars for year in labeled tape exp date w/o err Problem: A four digit year in the label= parameter of a file equation is accepted by the FILE command, but is formatted incorrectly by LISTEQ. For example: :file t;dev=tape;label=foo,ans,05/16/1991 :listeq FILE T;DEV=TAPE;LABEL=foo,ANS,05/11991 Then, the STORE/RESTORE will fail with either an FSERR 116 or S/R 63 followed by S/R 6093. Cause: Under investigation. Temporary solution: Use 2 digit years. \ENTRY=SR4701243071 _______________________________________________________________________ Number: 4701243071 Product: MPE V/E 32033G 12.0 One-line description: DELETEVAR GIVES MISLEADING MSGs WHEN TRYING TO DELETE JCW or CIERROR Problem: The DELETEVAR command which was added to MPE V Release 31 gives a misleading error message when a user attempts to delete a system reserved JCW. The message indicates that the JCW has not been defined and is confusing, since a SHOWJCW will show that the JCW does exist. For instance, :DELETEVAR HPMINUTE will give the following error message on MPE V: THIS JCW HAS NOT BEEN DEFINED. (CIERR 1731) on MPE iX: VARIABLE IS NOT DELETABLE. (CIWARN 8170) Cause: The cause of the problem is that when the DELETEVAR command was added to Release 31 of MPE V, a new message was not added to the message catalog to cover the situation where a user attempts to deletevar a system reserved JCW. Temporary solution: There is no temporary work around. The user needs to understand that the message is misleading. \ENTRY=SR4701249086 _______________________________________________________________________ Number: 4701249086 Product: MPE V/E 32033G 12.0 Keywords: SF310 One-line description: SF310 in SECURITYPROC in UTILITY2 due to integer overflow Problem: SF 310 due to an Integer Overflow from the security monitor system process. See the Temporary work around for further details. Cause: This problem is caused by an integer overflow. Temporary solution: Decrease the value of the new device timeout interval (0 - 32766 seconds) found in item 3 (Maximum Invalid Logons per Device) of the 1.-Global menu of SECCONF to a value much less than 32766 so the system can up the terminal before an integer overflow can occur. A valu of 30000 ought to be fine. \ENTRY=SR4701257600 _______________________________________________________________________ Number: 4701257600 Product: MPE V/E 32033G 12.0 One-line description: THE MPE ERROR MSG CARET IS OFF ONE BYTE IF ERROR ON CMD AFTER REDO. Problem: The problem is that the procedure CIERR which calculates where the care should be printed assumes that there is a ":" as the first character on the user's screen and compensates for the colon. However, if the user was REDOing the command and made a mistake, the colon is not on the screen because the REDO command only print what the user typed and that does not include the colon. Cause: This problem was caused by an oversite in the routine that prints the carat that points to the place where a command is in error. Temporary solution: There is no temporary work-around for this problem. \ENTRY=SR4701263004 _______________________________________________________________________ Number: 4701263004 Product: MPE V/E 32033G 12.0 One-line description: SPOOK5 produces corrupt tapes on OUTPUT command. Problem: Customers cannot recover selective files from a SPOOK5 tape created using the MPE/V Release 3P version or if all files are restored, an error message (SPERR 53) saying that the tape is not a SPOOK tape is displayed after the files are restored. In fact, all of the files that should be on the tape are there. Refer to the Temporary Work Around section of this SR for recovery procedures. Cause: This problem only happens if the file set specified in the OUTPUT command would also include OPEN files (files still being created). For example, if the command "O@.@" was issued (notice that a back reference to tape is no longer required) and there were any OPEN files on the system, then the SPOOK5 output tape would not be correctly written thus creating this problem. What SPOOK5 has always done is to create the list of "possible" files to be stored on the tape and then written the directory on the tape. Then, when actually storing the dat for each file on the tape, it first writes a header (SPOOK file label) before writing the contents of the file to tape. If the spool file wa OPEN when it became time to write the contents of the file to tape, SPOOK5 would write a dummy header on the tape for use when trying to recover selective files. When trying to recover selective files, SPOOK5 would examine the directory and count how many files down the desired file is on the tape With this problem, the dummy header would not be written on the tape, s the SPOOK5 INPUT command could not find the correct file. Temporary solution: With this problem, the dummy header would not be written on the tape, s the SPOOK5 INPUT command could not find the correct file. With the Cause of the problem identified, there are a couple of work arounds that can be used. The first is to try not to create a bad tape by making sure that there will not be any OPEN spool files in the file set used to specify what files are to be written on tape. If, however you have a bad tape, the file(s) can be recovered by using the SPOOK5 INPUT command to input all files from the tape and then use the SPOOK5 wildcard DELETE command to get rid of any unwanted files leaving only the desired file(s) left on the system. This work around works because if the file specification says "recover all files from th tape" (use the command I@.@ for this) then SPOOK5 ignores the directory and recovers all files from the tape stepping over any dummy file headers if there are any on the tape. Since it is not counting files, SPOOK5 will not know that the dummy file headers are missing from the tape and the files can be recovered. There is a patched version of the SPOOK5.PUB.SYS program available. \ENTRY=SR4701267831 _______________________________________________________________________ Number: 4701267831 Product: MPE V/E 32033G 12.0 Keywords: FREAD FILESYS One-line description: FREAD OF AN OPEN SPOOLFILE FAILS WITH FSERR 0 ON 3P. FIX IS MPEDV95 A. Problem: A change to MPE V 3P was made to the MPE V file system that should have excluded spoolfiles. The code to exclude spoolfiles from an additional file type check was incorrect. This results in an FSERR 0 being returned if an FSOPEN is attempted on an already opened spoolfile. Cause: A change to MPE V 3P was made to the MPE V file system that should have excluded spoolfiles. The code to exclude spoolfiles from an additional file type check was incorrect. This results in an FSERR 0 being returned if an FSOPEN is attempted on an already opened spoolfile. Temporary solution: I have set up a fix for the next release of MPE, and have also created a binary patch for the problem. There is also a general release patch MPEDV95 R. The solution is to check the SPOOLF flag in FOPENDA instead of the ACBSPOOLED bit. This can be accomplished with a binary patch. The following are the SLPATCH.PUB.SYS commands -RUN SLPATCH.PUB.SYS SL.PUB.SYS FILESYS4'6,D,7000,3 FILESYS4'6,M,7000,3 041447 000000 000000 FILESYS4'6,D,7000,3 FILESYS4'6,D,12212,1 FILESYS4'6,M,12212,1 123563 FILESYS4'6,D,12212,1 EXIT The checksum of FILESYS4'6 changes from %147610 to %123563. FILESYS4'6 has 3 instructions changed at the following offsets (in FOPENDA at offset %2451): 7000 021447 #' LDXI 39 ------> 041447 C' LOAD Q+ 04 7001 047424 O. LOAD Q+ 024,I,X ------> 000000 .. NOP ,NOP 7002 026401 -. EXF (0:1) ------> 000000 .. NOP ,NOP 7003 021406 #. LDXI 6 7004 047424 O. LOAD Q+ 024,I,X 7005 026443 -# EXF (2:3) 7006 022004 $. CMPI 4 The checksum was then recalculated and changed from 147610 to 123563: /-Old checksum /-New checksum / / 0.12212 147610 .. BR Q- 010,I,X -----> 123563 .s DECM Q+163, RUN CHECKSUM.HPSUP.TELESUP to verify that the checksum of FILESYS4'6 matches the value 147610. :run checksum.hpsup.telesup ------------------------------------------------------------------ CHECKSUM (A.01.07) MPE V - HP3000 System Support Tool THU, JUN 22, 1995, 2:31 PM Copyright Hewlett - Packard Co. 1983 CHECKSUM is designed for use by Hewlett Packard Support personnel HP IS NOT LIABLE FOR DAMAGES RESULTING FROM UNAUTHORIZED USE ------------------------------------------------------------------ File name >> sl.pub.sys <<-----User Input Segment name >> filesys4'6 <<-----User Input FILESYS4'6 Computed: 147610 Retrieved: 147610 Segment name >> <> <<-----User Input File name >> <> <<-----User Input END OF PROGRAM NOTE: IF CHECKSUM IS NOT %147610 DO NOT SLPATCH SEGMENT FILESYS4'6! :RUN SLPATCH.PUB.SYS <<-----User Input SLPATCH G.03.07 (C) HEWLETT-PACKARD CO., 1976 SL FILE? SL.PUB.SYS <<-----User Input ?FILESYS4'6,D,7000,3 <<-----User Input 021447 047424 026401 WARNING: IF THE ABOVE 3 VALUES ARE NOT THE DISPLAYED VALUES, DO NOT USE THE NEXT COMMANDS TO MODIFY SEGMENT FILESYS4'6! ?FILESYS4'6,M,7000,3 <<-----User Input 021447 _ 41447 <<-----User Input 047424 _ 0 <<-----User Input 026401 _ 0 <<-----User Input ?FILESYS4'6,D,7000,3 <<-----User Input 041447 000000 000000 ?FILESYS4'6,D,12212,1 <<-----User Input 147610 ?FILESYS4'6,M,12212,1 <<-----User Input 147610 _ 123563 ?FILESYS4'6,D,12212,1 <<-----User Input 123563 ?exit <<-----User Input END OF PROGRAM :run checksum.hpsup.telesup ------------------------------------------------------------------ CHECKSUM (A.01.07) MPE V - HP3000 System Support Tool THU, JUN 22, 1995, 2:31 PM Copyright Hewlett - Packard Co. 1983 CHECKSUM is designed for use by Hewlett Packard Support personnel HP IS NOT LIABLE FOR DAMAGES RESULTING FROM UNAUTHORIZED USE ------------------------------------------------------------------ File name >> sl.pub.sys <<-----User Input Segment name >> filesys4'6 <<-----User Input FILESYS4'6 Computed: 123563 Retrieved: 123563 Segment name >> <> <<-----User Input File name >> <> <<-----User Input END OF PROGRAM The system must now be COOLSTARTED for the change to be activated. Also, a new COLDLOAD tape should be created to save the change. \ENTRY=SR5000423079 _______________________________________________________________________ Number: 5000423079 Product: MPE V/E 32033G 02.B One-line description: SPOOK allows delete of READY spoolfile while OUTPUT @.@ is being done Problem: SPOOK does not show the right error message for deleting READY spoolfil while OUTPUT @.@ is being done. Cause: The problem is caused by a bug in procedure OUTFILES. SPOOK does not display the right DFID for "FILE NOT FOUND". The problem is only in th error message displayed; the tape is correct. SPOOK does not lock spoolfiles between their selection and their output so it is possible for files to be deleted in between. Since SPOOK also writes a copy of the ODD (the spoolfile directory) at the beginnin of the tape, this means that the directory on tape contains a spoolfile entry for a file which is not actually on the tape. To prevent problem when using the directory to input files, SPOOK writes a special "no file" record for any deleted files. Temporary solution: There is not any work around for this problem. \ENTRY=SR5003104992 _______________________________________________________________________ Number: 5003104992 Product: MPE V/E 32033G 10.0 One-line description: SPOOK DELETE command selects OPEN files - warning message misleading... Problem: This error message is issued because SPOOK gets an error trying to purg the file. Since a spool file in the OPEN state means it is just now being created, the user may not even know someone else is creating it and probably did not intend to purge it. Therefore, the code will be changed to simply ignore the error and not issue an error message. Cause: This problem is caused by the fact that the code does not realize that the OPEN state means it is just being created and the user probably did not want to purge the file. The code will be changed to not issue the error message for OPEN files. Temporary solution: There is no temporary workaround for this problem. \ENTRY=SR5003162362 _______________________________________________________________________ Number: 5003162362 Product: MPE V/E 32033G 11.0 One-line description: SPOOK5 displays wrong date for two digit months in Release 31 Problem: Under certain conditions, the first digit of the month in the long version of the show command could be replaced with a "0" (zero) leading one to believe the spool file is much older than it really is. For example, a spool file created on 11/08/93 would show as having been created on 01/08/93. This will only happen to spool files created in month number 11 (November) of any year. Cause: This problem occurred when putting enhancements into SPOOK5 for Release 31 of MPE V/E. Temporary solution: There is no direct work around, but the code of the SPOOK5 program can be easily patched to work correctly as follows: Log onto MANAGER.SYS,PUB :RUN PATCH FILE=?SPOOK5 ?M,2.7530,1 <> 045414,041402 ?EXIT Refer to the MPE V Utilities manual for further information on the PATC utility. ************** Note that this temporary solution does not apply to G.3P.00. See MR text from 11/02/94 for offset to use for this version. ************** \ENTRY=SR5003215277 _______________________________________________________________________ Number: 5003215277 Product: MPE V/E 32033G 12.0 One-line description: SPOOK5 truncates records on 3P when COPY command is used with CCTL Problem: If using the SPOOK5 COPY command back referenced to a disk file with CCCTL, SPOOK5 drops the last byte of each record. Cause: This problem was caused by enhancements being put into SPOOK5 for the Release 31 of SPOOK5. Temporary solution: Either go back to an earlier version of SPOOK5 (Release 30 or earlier) or do not use the ;CCTL specification on the file equation. \ENTRY=SR5003227280 _______________________________________________________________________ Number: 5003227280 Product: MPE V/E 32033G 12.0 One-line description: SPOOK5 on 3P changed the prompting in batch mode. Problem: While enhancing SPOOK5, it was decided that the prompt would not be written to $stdlist if the program was being run in job mode. It turns out, however, that a customer depends on this prompt being written out. Cause: While enhancing SPOOK5, it was decided that the prompt would not be written to $stdlist if the program was being run in job mode. It turns out, however, that a customer depends on this prompt being written out. Temporary solution: There is no temporary work around for this problem other than go back t a previous version of SPOOK5 or request the patched version from the HP Response Center. \ALL