gtpm4m1j | Messages (System Error and Offline) |
GEF003 | CYLINDER 0 TRACK 0 INVALID |
Severity: 5
Explanation: Cylinder 0 track 0 is intended to hold other information, such as the VOLSER number.
System Action: None.
User Response: Do the following:
GEN001 | xxxx xxxx OPTION WAS SELECTED BUT A RAMFIL WAS NOT CODED FOR RECORD TYPE yyyy |
Where:
Severity: 0 or 7
Explanation: The option referenced in the message was coded in the SIP stage I deck to be included in the TPF system. This option may require the record type referenced in the message.
A RAMFIL macro was not coded for this record type. Severity 7 occurs when the record is required by the TPF code. Severity 0 occurs when the record is required because of the application program or optional support.
System Action: None.
User Response: Do the following:
GEN002 | xxxx RECORD TYPE IS REQUIRED BUT A RAMFIL WAS NOT CODED |
Where:
Severity: 0 or 7
Explanation: The record type referenced in the message is required but a RAMFIL was not coded.
Severity 7 occurs when the record is required by the TPF code. Severity 0 occurs when the record is required because of the application program or optional support.
User Response: Do the following:
GEN005 | xxxx SPECIFIED IS INCORRECT FOR RECORD TYPE yyyy |
Where:
Severity: 0
Explanation: The parameter referenced in the message is coded on the RAMFIL macro for the record type referenced in the message. This parameter is incorrect for this record type.
System Action: None.
User Response: Do the following:
GEN006 | AN INSUFFICIENT NUMBER OF RECORDS HAVE BEEN SPECIFIED FOR RECORD TYPE xxxx - THE MINIMUM NUMBER OF RECORDS REQUIRED IS yyyy |
Where:
Severity: 7
Explanation: The system initialization program (SIP) calculated that there are not enough records specified on the RAMFIL macros for the record type referenced in the message. The minimum number of records than can be specified for a user for this record type is shown in the message.
System Action: None.
User Response: Do the following:
GEN010 | EDITOR NAME FOR RESIDENT APPLIC. xxxx WAS NOT SPECIFIED ON MSGRTA MACRO. DEFAULT OF yyyy ASSIGNED |
Where:
Severity: 0
Explanation: The MSGRTA macro for the application program identified in the message did not specify the application editor program name through the EDIT parameter. A default program name, as referenced in the message, was assigned by system initialization program (SIP).
System Action: None.
User Response: Do one of the following:
GEN013 | BSNCT MACROS MUST BE CODED IF THERE ARE BISYNC LINES |
Severity: 7
Explanation: If the user generates BISYNC lines, then at least one BSNCT macro must be coded. BISYNC line support requires the CRSx segment, which system initialization program (SIP) generates when BSNCT macros are coded.
System Action: None.
User Response: When generating BISYNC lines provide at least one BSNCT macro.
GEN018 | SIP PROGRAM TABLE (xxxx) IS EMPTY |
Where:
Severity: 7
Explanation: SIP stage I requires entries to the system initialization program (SIP) program tables.
System Action: None.
User Response: Do the following:
GEN023 | SSU DEFINITIONS IN GLOBAL MACRO DO NOT MATCH SSUSERS DEFINED IN SSDEF MACRO |
Severity: 7
Explanation: The number of subsystem users defined in the SSDEF macro and the number of subsystem user global definitions in the GLOBAL macro do not match.
System Action: None.
User Response: Do the following:
GEN028 | SUBSYSTEM USER PARAMETERS ON GLOBAL MACRO DO NOT AGREE |
Severity: 7
Explanation: The number of input parameters specified in each subsystem user parameter of the GLOBAL macro (SSUGLO1, SSUGLO2, SSUGLO3, and SSULMOD) must be equal.
System Action: None.
User Response: Do the following:
GEN030 | SUBSYSTEM USER ID (USER=) DEFINED IN xxxxxx DOES NOT APPEAR IN SSUID PARAMETER OF SSDEF |
Where:
Severity: 7
Explanation: Every subsystem user ID (USER=) appearing in the MSGRTA, GLSYNC, or RAMFIL macros must be defined in the SSUID parameter of SSDEF. If SSDEF was not coded, then USER= must be allowed to default or be coded as the default.
System Action: None.
User Response: Do the following:
GEN033 | xxxx PROGRAM MISSING FROM SIP PROGRAM TABLES (yyyy) |
Where:
Severity: 0 or 7
Explanation: The program name referenced in the message was not found in the SIP program tables (SPPGML). The program name minus the version number was used as the search argument.
System Action: None.
User Response: Do one of the following:
GEN034 | GF KEYPOINT xxxxGv MISSING FROM SIP PROGRAM TABLES (KP) |
Where:
Severity: 7
Explanation: The general file keypoint (suffix Gv) was not found in the SIP program tables (SPPGML), specifically in the keypoint table (KP).
System Action: None.
User Response: Do the following:
GEN051 | xxxx SUPPORT REQUESTED in yyyy MACRO BUT NOT SUPPORTED IN A zzzz ENVIRONMENT |
Where:
Severity: 7
Explanation: The system initialization program (SIP) detected an incompatibility with a programming support parameter coded in the user macros.
System Action: None.
User Response: Do one of the following:
In either case, make the necessary corrections and rerun SIP stage I.
GEN053 | xxxx MACRO MUST BE CODED WHEN A yyyy ENVIRONMENT EXISTS |
Where:
Severity: 7
Explanation: The system initialization program (SIP) detected that the user macro referenced in the message was not coded but is required when the programming environment indicated in the message exists.
System Action: None.
User Response: Do one of the following:
In either case, make the necessary corrects and rerun SIP stage I.
GEN054 | PROGRAM xxxx DEFINED IN UTPROT MACRO NOT ALLOCATED IN SYSTEM |
Where:
Severity: 7
Explanation: The program defined in the UTPROT macro, which is referenced in the message, is not assigned for assembly or allocation in the TPF system. This error causes the Utility Interface Program Table not to be generated.
System Action: None.
User Response: Do one of the following:
In either case, make the necessary corrections and rerun SIP stage I.
GEN055 | xxxx MACRO CODED BUT A yyyy ENVIRONMENT DOES NOT EXIST |
Severity: 7
Where:
Severity: 7
Explanation: The system initialization program (SIP) detected that the user macro referenced in the message was coded but is not required when the programming environment indicated in the message does not exist.
System Action: None.
User Response: Do one of the following:
In either case, make the necessary corrections and rerun SIP stage I.
GEN062 | GENSIP MACRO SPECIFIED MORE THAN ONCE |
Severity: 7
Explanation: The GENSIP macro was specified more than once.
System Action: None.
User Response: Do one of the following;
GEN063 | xxxx MACRO WAS OMITTED FROM STAGE I |
Where:
Severity: 7
Explanation: The macro referenced in the message was not coded. This macro is required.
System Action: None.
User Response: Do the following:
GEN065 | REGN OPERAND LESS THAN DEFAULT, ASSUMED DEFAULT |
Severity: 0
Explanation: The REGN value must not be less than default regions. Defaults are minimum sizes for SIP Stage II assemblies.
System Action: The operand that was specified is ignored.
User Response: No action is necessary if the minimum core is available for SIP stage II assemblies.
GEN066 | MACRO xxxxxx CANNOT BE INCLUDED IN A NONBASIC SUBSYSTEM GENERATION |
Where:
Severity: 7
Explanation: Use of the SIP user macro referenced in the message is restricted to basic subsystem generation. This macro is not to be supplied for this process.
System Action: None.
User Response:
GEN068 | xxxx TCU SPECIFIED BUT LINES OMITTED, OR VICE VERSA |
Severity: 7
Explanation: One of the following errors occurred:
System Action: None.
User Response: Do the following:
GEN072 | SYNCLK SPECIFIED BUT SLC LINES OMITTED |
Severity: 7
Explanation: The SYNCLK macro was coded but no SLC lines were specified in LINES macro.
System Action: None.
User Response: Do the following:
GEN077 | SLC PSEUDO LINES SPECIFIED, BUT SLC LINKS WERE OMITTED |
Severity: 7
Explanation: None.
System Action: None.
User Response: Do the following:
GEN078 | CRASTB ENTRY nn LINE NO. NOT IN LC RANGE |
Where:
Severity: 7
Explanation: The CRAS table entry referenced in the message is in error. This entry is for a device on a local (LC) line but the line number is not in the LC line range.
System Action: None.
User Response: Do the following:
GEN079 | xxxx yyyy > NO. OF xxxx LINES SPECIFIED |
Where:
Severity: 7
Explanation: yyyy as specified in the SYNCLK macro exceeds the number of SKN/PLN lines that were specified in the LINES macro.
System Action: None.
User Response: Do the following:
GEN080 | TOTAL NUMBER OF SLC LINKS, SLC LINES, AND RCAT ENTRIES IS GREATER THAN FIFTY (50) |
Severity: 0
Explanation: Defining more than 50 SLC links, or SLC lines and RCAT entries may cause the Global 3 directory area to be overrun.
System Action: None.
User Response: If you are sure that Global Area 3 will not be overrun, then no action is required. Otherwise, adjust the following SIP macro parameters so that the sum of the SLC and RCAT entries will be less than or equal to 50:
((MAXAP) + (NLINK-N1LNK) + (SLCAI) + (PSLNS)) <= 50
Notes:
GEN089 | GFENS OPERAND (RAM MACRO) INVALID, xxxx ASSUMED |
Where:
Severity: 7
Explanation: The GFENS operand must be greater than the highest data set number in the GENFIL macros.
System Action: None.
User Response: Do the following:
GEN090 | DUPLICATE OR INVALID GENERAL FILE DATA SET NUMBERS SPECIFIED IN GENFIL MACROS |
Severity: 7
Explanation: The data set number was entered more than once or the data set number was out of the required range (0 to 59).
System Action: None.
User Response: Do the following:
GEN102 | IN BASE ONLY SYSTEM THE USER= PARM OF MSGRTA SHOULD NOT BE CODED |
Severity: 0
Explanation: The subsystem user (SSU) must be initialized to the basic subsystem (BSS) in GEND for a base only system. The USER parameter should only be coded by MSGTRA in a MASS environment.
System Action: None.
User Response: When in a base-only environment, you should not code any USER parameters in the MSGRTA macro.
GEN106 | MAX 3270 MSG LENGTH EXCEEDS 7268, POST PROCESSOR SORT/ MERGE FEATURE NOT AVAILABLE |
Severity: 0
Explanation: 7268 is the maximum variable length record.
System Action: None.
User Response: If the post processor sort/merge feature is required, specify a shorter 3270 message length.
GEN107 | FOR CAPTURE/RESTORE, DDCCAP, RESCAP AND LOGCAP MUST BE CODED |
Severity: 7
Explanation: At least one, but not all of the capture and restore macros were coded. If capture and restore is to be included in the TPF system, all three macros must be coded.
System Action: None.
User Response: Do the following:
GEN109 | CAPTURE PARAMETERS CODED FOR UNSUPPORTED DEVICE xxxx |
Where:
Severity: 7
Explanation: Parameters were coded in the DDCCAP macro for a storage device that was not specified in the ONLFIL macro.
System Action: None.
User Response: Do the following:
GEN110 | xxxx SUPPORTED, BUT NO CAPTURE PARAMETERS SPECIFIED |
Where:
Severity: 0
Explanation: No parameters were coded in the DDCCAP macro for a storage device that was specified in the ONLFIL macro.
System Action: None.
User Response: Do the following:
GEN118 | MESSAGE ROUTER IS REQUIRED THEREFORE MSGRT AND MSGRTA MACROS MUST BE CODED |
Severity: 7
Explanation: None.
System Action: None.
User Response: Do the following:
GEN124 | MESSAGE ROUTER SUPPORT REQUIRED BUT GLOB3 NOT CODED IN GLOBAL MACRO |
Severity: 7
Explanation: None.
System Action: None.
User Response: Do the following:
GEN125 | PROCESSOR x SPECIFIED IN CRASTB IS NOT SPECIFIED IN MSGRTA OR CONFIG |
Where:
Severity: 7
Explanation: Only the processors defined in the MSGRTA macro or the CONFIG macro should be in the CRASTB definition.
System Action: None.
User Response: Do the following:
GEN128 | BSNCT MACRO WITH STANM OF xxxx HAS INVALID CPU ID OF 'y' |
Where:
Severity: 7
Explanation: A CPU ID was specified on the BSNCT macro that was not defined by a MSGRTA macro.
System Action: None.
User Response: Do the following:
GEN129 | BSNCT STANO PARAM FOR STANM OF xxxx IS GREATER THAN NUMBER OF BBSAT MACROS |
Where:
Severity: 7
Explanation: The BSNCT macro for the station identified in the message contained a STANO value that was greater than the number of BBSAT macros coded.
System Action: None.
User Response: Do the following:
GEN130 | MSGSW SPECIFIED WITHOUT INCLUDING RES0 |
Severity: 7
Explanation: Message switching was requested through the MSGSW parameter of CONFIG macro but RES0 was not included by specifying RES in the CONFIG macro. Inclusion of message switching requires the RES0 application program.
System Action: None.
User Response: Do the following:
GEN131 | SLC OR NEF SHOULD BE SPECIFIED WITH MSGSW |
Severity: 7
Explanation: If MSGSW=YES is coded on the CONFIG macro, then NEF=YES must also be coded on the CONFIG macro or SLCAI must be coded as nonzero on the LINES macro.
System Action: None.
User Response: Do the following:
GEN137 | BSC MULTI POINT SUPPORT INCLUDED BUT NO BBSAT MACROS SPECIFIED |
Severity: 7
Explanation: None.
System Action: None.
User Response: Do the following:
GEN138 | BSC MULTI POINT SUPPORT NOT INCLUDED BUT BBSAT MACROS WERE SPECIFIED |
Severity: 7
Explanation: None.
System Action: None.
User Response: Do the following:
GEN139 | BSC LINE SUPPORT NOT INCLUDED BUT BSNCT MACRO WAS SPECIFIED FOR STANM xxxx |
Where:
Severity: 7
Explanation: A BSNCT macros with the STANM referenced in the message was coded for the system generation CPU but no BSC lines were defined for this CPU.
System Action: None.
User Response: Do the following:
GEN142 | LINE NUMBER FOR SNCT ENTRY WITH STANM xxxx and STANO yy IS NOT A BSC LINE |
Where:
Severity: 7
Explanation: The line number for the SNCT entry with the station name and station number referenced in the message is in error.
System Action: None.
User Response: Do the following:
GEN143 | APPL xxxx FOR SNCT ENTRY WITH STANM yyyy IS NOT IN RCAT TABLE |
Where:
Severity: 7
Explanation: The application for the SNCT entry with the station name referenced in the message is in error.
System Action: None.
User Response: Do the following:
GEN150 | PROGRAM xxxx LOADING VERSION yy AND ASSEMBLY IS VERSION zz |
Where:
Severity: 0
Explanation: The program identified in the message was assembled using the version number referenced in the message. The program is listed in the SPPGML macro with a different version number.
System Action: None.
User Response: Do the following:
GEN151 | SIP MACRO xxxx NOT CODED IN STAGE I INPUT, CALLED INTERNALLY TO SET DEFAULT VALUES |
Where:
Severity: 0
Explanation: The SIP user macro referenced in the message was not included in the user's stage I system generation input. The system initialization program (SIP) will call this macro from its internal structure to set the default values.
System Action: None.
User Response: If the assumption is not valid, correct the error and rerun SIP stage I.
GEN158 | THE MAXAP VALUE ON MSGRT MACRO EXCEEDED LIMIT AND HAS BEEN REDUCED BY &P1 |
Severity: 0
Explanation: The maximum number of application programs that can be defined by you is 256-M where M is the number of fixed application programs (for example, RES0 (&P1=OVERAGE COUNT).
System Action: None.
User Response: None.
GEN159 | THE NUMBER OF MSGRTA APPLICATION NAMES PLUS THE FIXED APPLIC'S EXCEED THE LIMIT BY &P1 |
Severity: 7
Explanation: The maximum number of user application programs that can be defined by the MSGRTA macro is 256-M where M is the number of fixed application programs defined in the user's system (for example, &P1=OVERAGE COUNT).
System Action: None.
User Response: Do the following:
GEN161 | PROGRAM NAME xxxx DEFINED IN BSNCT MACRO IS NOT DEFINED BY A MSGRTA MACRO |
Where:
Severity: 7
Explanation: While creating the SNCT table using the SIP skeleton SKSNCT, it was determined that the application program name referenced in the message does not have a corresponding MSGRTA definition.
System Action: None.
User Response: Do the folllwing:
GEN162 | VOLSER RANGE OF xxxx OVERLAYS THE VOLSER RANGE OF yyyy |
Where:
Severity: 7
Explanation: The calculated range for the first device type overlaps at least part of the volume serial numbers (VSNs) for the second device type. For the online modules, the starting VSN is the value specified for VOLNOx and the ending range is VOLNOx + PERMx + EXTRx - 1. Each DASD type must have a unique set of VSNs.
System Action: None.
User Response: Do the following:
GEN163 | xxxx RELATIVE MOD NUMBER IN LOGCAP MACRO TOO LARGE DEFAULTED TO HIGHEST MOD |
Where:
Severity: 0
Explanation: The relative module number specified in the LOGCAP macro exceeds the number of modules specified in ONLFIL macro.
System Action: None.
User Response: Do one of the following:
GEN164 | xxxx RELATIVE MOD NUMBER IN DDCCAP MACRO TOO LARGE DEFAULTED TO HIGHEST MOD NUMBER |
Where:
Severity: 0
Explanation: The relative module number specified in DDCCAP macro exceeds the number of modules specified in the ONLFIL macro.
System Action: None.
User Response: Check the capture and restore options in the SIP report and do one of the following, as appropriate:
GEN171 | xxxx DEVICE NAME USED MORE THAN ONCE |
Where:
Severity: 7
Explanation: The device name referenced in the message is for the online pool programs to know the device by. Therefore, each device must have a unique name.
In the ONLFIL macro, the parameter NAMDEVx (where x is the device type (for example, A would be used for device type A)) can be used to assign different names to the same device types.
System Action: None.
User Response: Do the following:
GEN173 | BSNCT MACROS FOR THIS CPU=xx > BSC DROPS DEFINED IN LINES MACRO WHICH TOTAL yy |
Where:
Severity: 7
Explanation: BSNCT macros were coded to define SNCT slots but there are not enough BSC drops defined in the TPF system.
System Action: None.
User Response: Do the following:
GEN175 | COMPUTED NUMBER OF MODULES (xxxx) EXCEEDS MAXIMUM (yyyy) ALLOWED |
Where:
Severity: 7
Explanation: The total number of modules is calculated by adding the number of online modules to the number of general file modules plus one. The number of online modules exceeds the maximum number of general file modules permitted in the TPF system.
System Action: None.
User Response: Do the following:
GEN179 | xxxx SUPPORT REQUESTED BUT yyyy SUPPORT REQUIRED AND NOT REQUESTED IN zzzz MACRO |
Where:
Severity: 7
Explanation: The system initialization program (SIP) detected an incompatibility with a programming support parameter coded in the user macros.
System Action: None.
User Response: Do one of the following:
In either case, make the necessary corrections and rerun SIP stage I.
GEN182 | NUMBER OF PROCESSORS(xx) DEFINED IN CONFIG DIFFERS FROM THE NUMBER OF PRIME CRAS ENTRIES(yy) DEFINED IN CRASTB |
Where:
Severity: 7
Explanation: The number of processor IDs (SYSID) specified in the CONFIG macro does not match the number of primary CRAS operator consoles (PRCRS) specified in CRASTB.
In non-native console systems, fallback consoles are specified with the ALTPC parameter.
In native console systems, fallback consoles are specified with additional entries on the PRCRS parameter.
Consequently, in non-native console systems, the number of consoles must exactly equal the number of processors being defined (through the SYSID parameter). In native console systems, the number of consoles may be greater than or equal to the number processors being defined.
System Action: None.
User Response: Do the following:
GEN190 | NUMBER OF PROCESSORS (x) SPECIFIED IN CONFIG CONFLICTS WITH THE NUMBER OF UAT ENTRIES SPECIFIED IN NETWK (y). DEFAULT (= 2 × x) TAKEN. |
Where:
Severity: 0
Explanation: The minimum number of line address, interchange address, and terminal address (LNIATAs) requiring an entry in the AAA initialization table (UAT) is two times the number of CPUs (2×x), only (y) number were specified.
System Action: None.
User Response: Do one of the following:
GEN197 | NO VALID TAPE DRIVES WERE DEFINED BY IODEV |
Severity: 7
Explanation: None.
System Action: None.
User Response: Do the following:
GEN250 | MESSAGE ROUTER, MSGRT, SHOULD ONLY BE PRESENT IN THE BASIC SUBSYSTEM OF A MASS SYSTEM |
Severity: 7
Explanation: The message router was coded in a TPF system where BSSGEN=NO.
System Action: None.
User Response: Do the following:
GEN255 | MACRO GLSYNC HAS COMMON=YES CODED FOR GLOBAL xxxx FOR AT LEAST ONE USER. xxxx COMMON CHANGED TO YES FOR PRIMARY USER (yyyy) |
Where:
Severity: 0
Explanation: If a synchronized global is coded as common for any user, the same global must be coded as COMMON=YES for the primary user. The primary user's global was changed to COMMON=YES.
System Action: None.
User Response: None, unless the global in error was coded incorrectly.
GEN256 | MACRO GLSYNC HAS COMMON=YES CODED FOR GLOBAL xxxx FOR AT LEAST ONE USER. xxxx ADDED TO PRIMARY SUBSYSTEM USER (yyyy) |
Where:
Severity: 0
Explanation: If a synchronized global is coded as common for any user, the same global must be coded for the primary subsystem user with COMMON=YES.
System Action: None.
User Response: None, unless the global in error was coded incorrectly.
GEN260 | RECORD xxxx MUST BE SPECIFIED FOR EACH USER. RECORD xxxx FOR USER yyyy WAS SPECIFIED INCORRECTLY AS COMMON |
Where:
Severity: 7
Explanation: The record referenced in the message must be coded for each user specifically. It must never be a common record.
System Action: None.
User Response: Do the following:
GEN261 | RECORD xxxx WAS NOT FOUND, OR RECORD IS NOT 4K. DLU SUPPORT IS DISABLED. |
Where:
Severity: 0
Explanation: The record referenced in the message was not found or it is not defined as 4K.
System Action: Dynamic LU support is disabled.
User Response: If you want dynamic LU support, do the following:
GEN270 | MACRO RAM HAS NFBACK=n AND MACRO CONFIG DEFINES p PROCESSORS. NFBACK IS SUPPORTED FOR COEXISTENCE WITH PRE 32 WAY LOOSELY COUPLED CODE ONLY. COEXISTENCE DOES NOT EXTEND BEYOND 8 PROCESSORS. |
Where:
Severity: 7
Explanation: When a loosely coupled complex is expanded to more than eight processors, all processors must be running 32-way loosely coupled processor support and the migration of the loosely coupled complex has been completed. Once migration to 32-way loosely coupled processor support has been completed, the fallback extents in the #KEYPT area defined by NFBACK can no longer be used. The fallback extents are controlled by the #KFBXn RAMFIL definitions in the FACE table (FCTB).
System Action: None.
User Response: When migration to 32-way loosely coupled processor support has been completed, change the value of NFBACK to 0.
See TPF Migration Guide: Program Update Tapes for more information about dynamic LU support.
GLO001 | PARAMETER xxxx EXCEEDS PARAMETER LIMIT OF 94 |
Where:
Severity: 5
Explanation: Only 94 items may be input in this parameter.
System Action: None.
User Response: Do the following:
GLO002 | xxxx OPERAND IGNORED-VALID ONLY IF yyyy=YES |
Where:
Severity: 0
Explanation: The keyword referenced in the message should only be coded if yyyy=YES was specified.
System Action: None.
User Response: Do one of the following:
GLS001 | THE PARAMETER xxxx IS SPECIFIED AS yyyy. IT IS PREVIOUSLY SPECIFIED AS zzzz |
Where:
Severity: 5
Explanation: This global name was specified previously with the parameter referenced in the message specified as zzzz. The parameter is now defined as yyyy.
System Action: None.
User Response: Do the following:
GLS002 | THE MAXIMUM NUMBER OF xxxx EXCEEDS yyyy |
Where:
Severity: 5
Explanation: The maximum yyyy for xxxx was exceeded.
System Action: None.
User Response: Do the following:
GLS003 | TYPE=FLD, BASE=x AND COMMON=y COMMON RESET TO z |
Where:
Severity: 0
Explanation: When TYPE=FLD and BASE=Y then COMMON must equal YES. When TYPE=FLD and BASE=A, then COMMON must equal NO.
System Action: The system initialization program (SIP) reset COMMON to the correct value.
User Response: Do one of the following:
GLS004 | THE GLOBAL NAME xxxx IS RESERVED FOR SYSTEM USAGE |
Where:
Severity: 5
Explanation: The global referenced in the message is a system value that is synchronized automatically by the system initialization program (SIP).
System Action: None.
User Response: Do the following:
GTSZ0001T | CANNOT OPEN OUTPUT FILE filename |
Where:
Explanation: GTSZ could not open the SKGTSZ output file for writing.
System Action: Processing is ended immediately.
User Response: Rerun GTSZ after the file can be opened for writing.
See TPF System Generation for more information on GTSZ.
GTSZ0002T | CANNOT OPEN THE PDS DIRECTORY directory AS THE INPUT FILE. |
Where:
Explanation: The PDS reference in the message could not be opened for input. GTSZ cannot determine file sizes unless it can open and read the directory.
System Action: Processing ends immediately.
User Response: Do the following:
See TPF System Generation for more information on GTSZ.
GTSZ0003T | READING THE PDS DIRECTORY FOR directory HAS FAILED. |
Where:
Explanation: The PDS referenced in the message could not be read from. GTSZ cannot determine file sizes unless it can read the PDS.
System Action: Processing ends immediately.
User Response: Do the following:
See TPF System Generation for more information on GTSZ.
GTSZ0004W | THE SIZE COULD NOT BE FOUND FOR member |
Where:
Explanation: A size could not be determined for the file name referenced in the message. The default size of 0 was used.
System Action: Processing continues normally.
User Response: Do the following:
See TPF System Generation for more information on GTSZ.