gtpm4m1jMessages (System Error and Offline)

GEF0-GTSZ

GEF003CYLINDER 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:

  1. Recode the macro.
  2. Rerun SIP stage I.

GEN001xxxx xxxx OPTION WAS SELECTED BUT A RAMFIL WAS NOT CODED FOR RECORD TYPE yyyy

Where:

xxxx
The option.

yyyy
The record type.

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:

  1. Code a RAMFIL statement if the record type is required.
  2. Rerun the FACE table generator (FCTBG).
  3. Rerun SIP stage I.

GEN002xxxx RECORD TYPE IS REQUIRED BUT A RAMFIL WAS NOT CODED

Where:

xxxx
The record type.

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:

  1. Make the necessary corrections.
  2. Rerun the FACE table generator (FCTBG).
  3. Rerun SIP stage I.

GEN005xxxx SPECIFIED IS INCORRECT FOR RECORD TYPE yyyy

Where:

xxxx
The parameter name.

yyyy
The record type.

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:

  1. Make the necessary corrections.
  2. Rerun the FACE table generator (FCTBG).
  3. Rerun SIP stage I.

GEN006AN INSUFFICIENT NUMBER OF RECORDS HAVE BEEN SPECIFIED FOR RECORD TYPE xxxx - THE MINIMUM NUMBER OF RECORDS REQUIRED IS yyyy

Where:

xxxx
The record type.

yyyy
The number of records.

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:

  1. Correct the appropriate RAMFIL macro statements for the record type to specify the minimum number of records.
  2. Rerun the FACE table generator (FCTBG).
  3. Rerun SIP stage I.

GEN010EDITOR NAME FOR RESIDENT APPLIC. xxxx WAS NOT SPECIFIED ON MSGRTA MACRO. DEFAULT OF yyyy ASSIGNED

Where:

xxxx
The application program name.

yyyy
The default application program name.

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:

GEN013BSNCT 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.

GEN018SIP PROGRAM TABLE (xxxx) IS EMPTY

Where:

xxxx
The program table that was empty (OL, CP, RT, CRT, ICL, ISA, ISC, or KP).

Severity: 7

Explanation: SIP stage I requires entries to the system initialization program (SIP) program tables.

System Action: None.

User Response: Do the following:

  1. Correct the SPPBLD macro in the SPPGML member for the table referenced in the message.
  2. Rerun SIP stage I.

GEN023SSU 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:

  1. Make the number of subsystem users match the number of subsystem user global definitions in the GLOBAL macro or make the number of subsystem user global definitions in the GLOBAL macro match the number of subsystem users.
  2. Rerun SIP stage I.

GEN028SUBSYSTEM 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:

  1. Correct the GLOBAL macro by ensuring that the number of input parameters specified on the subsystem parameters are equal.
  2. Rerun SIP stage I.

GEN030SUBSYSTEM USER ID (USER=) DEFINED IN xxxxxx DOES NOT APPEAR IN SSUID PARAMETER OF SSDEF

Where:

xxxxxx
The location of the subsystem user ID (SSUID) definition.

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:

  1. Correct the USER parameter involved or add the subsystem user ID (SSUID) to the SSUID parameter in SSDEF.
  2. Rerun SIP stage I.

GEN033xxxx PROGRAM MISSING FROM SIP PROGRAM TABLES (yyyy)

Where:

xxxx
The program name.

yyyy
The library name.

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:

GEN034GF KEYPOINT xxxxGv MISSING FROM SIP PROGRAM TABLES (KP)

Where:

xxxx
The general file keypoint.

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:

  1. Add the general file keypoint to the SIP program table (SPPGML), specifically in the KP table.
  2. Rerun SIP stage I.

GEN051xxxx SUPPORT REQUESTED in yyyy MACRO BUT NOT SUPPORTED IN A zzzz ENVIRONMENT

Where:

xxxx
The program support requested through a SIP option.

yyyy
The SIP user macros that contains the program support.

zzzz
Indicates a programming environment that is not compatible with the program support.

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.

GEN053xxxx MACRO MUST BE CODED WHEN A yyyy ENVIRONMENT EXISTS

Where:

xxxx
A user macro.

yyyy
Indicates a programming environment.

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.

GEN054PROGRAM xxxx DEFINED IN UTPROT MACRO NOT ALLOCATED IN SYSTEM

Where:

xxxx
The program defined in the UTPROT macro.

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.

GEN055xxxx MACRO CODED BUT A yyyy ENVIRONMENT DOES NOT EXIST

Severity: 7

Where:

xxxx
A user macro.

yyyy
A programming environment.

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.

GEN062GENSIP 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;

  1. Remove all but one GENSIP macro.
  2. Rerun SIP stage I.

GEN063xxxx MACRO WAS OMITTED FROM STAGE I

Where:

xxxx
The name of the macro.

Severity: 7

Explanation: The macro referenced in the message was not coded. This macro is required.

System Action: None.

User Response: Do the following:

  1. Code the macro.
  2. Include the macro in the SIP stage I input.
  3. Rerun SIP stage I.

GEN065REGN 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.

GEN066MACRO xxxxxx CANNOT BE INCLUDED IN A NONBASIC SUBSYSTEM GENERATION

Where:

xxxxxx
The SIP user macro.

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:

  1. Remove the macro call from the SIP stage I input.
  2. Rerun the SIP stage I assembly.

GEN068xxxx 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:

  1. Correct the LINES macro to specify a line type.
  2. Rerun SIP stage I.

GEN072SYNCLK 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:

  1. Correct the SLCAI parameter in the LINES macro or do not code the SYNCLK macro.
  2. Rerun SIP stage I.

GEN077SLC PSEUDO LINES SPECIFIED, BUT SLC LINKS WERE OMITTED

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Correct PSLNS in the LINES macro or correct NLINK in the SYNCLK macro.
  2. Rerun SIP stage I.

GEN078CRASTB ENTRY nn LINE NO. NOT IN LC RANGE

Where:

nn
The computer room agent set (CRAS) table entry.

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:

  1. Check the SIP report for the LC line numbers.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

GEN079xxxx yyyy > NO. OF xxxx LINES SPECIFIED

Where:

xxxx
The line type (SKN/PLN).

yyyy
The specification in the SYNCLK macro.

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:

  1. Correct the LINES or the SYNCLK macro.
  2. Rerun SIP stage I.

GEN080TOTAL 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:

  1. MAXAP is a parameter of the MSGRT macro.

  2. NLINK and N1LNK are parameters of the SYNCLK macro.

  3. SLCAI and PSLNS are parameters of the LINES macro.

GEN089GFENS OPERAND (RAM MACRO) INVALID, xxxx ASSUMED

Where:

xxxx
The assumed value.

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:

  1. Correct the GFENS operand.
  2. Rerun SIP stage I if the assumed value is not valid.

GEN090DUPLICATE 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:

  1. Correct the GENFIL macros.
  2. Rerun SIP stage I.

GEN102IN 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.

GEN106MAX 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.

GEN107FOR 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:

  1. Code the remaining capture and restore macros.
  2. Rerun SIP stage I.

GEN109CAPTURE PARAMETERS CODED FOR UNSUPPORTED DEVICE xxxx

Where:

xxxx
The storage device.

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:

  1. Correct the DDCCAP parameters.
  2. Rerun SIP stage I.

GEN110xxxx SUPPORTED, BUT NO CAPTURE PARAMETERS SPECIFIED

Where:

xxxx
The storage device.

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:

  1. Code additional storage devices if there is an error.
  2. Rerun SIP stage I.

GEN118MESSAGE ROUTER IS REQUIRED THEREFORE MSGRT AND MSGRTA MACROS MUST BE CODED

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Code the message router macros.
  2. Rerun SIP stage I.

GEN124MESSAGE ROUTER SUPPORT REQUIRED BUT GLOB3 NOT CODED IN GLOBAL MACRO

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN125PROCESSOR x SPECIFIED IN CRASTB IS NOT SPECIFIED IN MSGRTA OR CONFIG

Where:

x
The processor ID.

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:

  1. Correct the CRASTB macro, CONFIG macro, or MSGRTA macro.
  2. Rerun SIP stage I.

GEN128BSNCT MACRO WITH STANM OF xxxx HAS INVALID CPU ID OF 'y'

Where:

xxxx
The station name.

y
The CPU ID.

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:

  1. Correct the error (either the BSNCT or the MSGRTA macro).
  2. Rerun SIP stage I.

GEN129BSNCT STANO PARAM FOR STANM OF xxxx IS GREATER THAN NUMBER OF BBSAT MACROS

Where:

xxxx
The station name.

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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN130MSGSW 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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN131SLC 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:

  1. Correct the error.
  2. Rerun SIP stage I if the condition is not valid.

GEN137BSC MULTI POINT SUPPORT INCLUDED BUT NO BBSAT MACROS SPECIFIED

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN138BSC MULTI POINT SUPPORT NOT INCLUDED BUT BBSAT MACROS WERE SPECIFIED

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN139BSC LINE SUPPORT NOT INCLUDED BUT BSNCT MACRO WAS SPECIFIED FOR STANM xxxx

Where:

xxxx
The station name.

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:

  1. Correct the error.
  2. Rerun SIP stage I.

GEN142LINE NUMBER FOR SNCT ENTRY WITH STANM xxxx and STANO yy IS NOT A BSC LINE

Where:

xxxx
The station name.

yy
The station number.

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:

  1. Check the SIP report for the correct BSC line numbers.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

GEN143APPL xxxx FOR SNCT ENTRY WITH STANM yyyy IS NOT IN RCAT TABLE

Where:

xxxx
The application name.

yyyy
The station name.

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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN150PROGRAM xxxx LOADING VERSION yy AND ASSEMBLY IS VERSION zz

Where:

xxxx
The program name.

yy
The version number as listed in the SPPGML macro.

zz
The version number.

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:

  1. Change the SPPGML macro.
  2. Rerun SIP stage I if necessary.

GEN151SIP MACRO xxxx NOT CODED IN STAGE I INPUT, CALLED INTERNALLY TO SET DEFAULT VALUES

Where:

xxxx
The SIP user macro.

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.

GEN158THE 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.

Note:
The maximum value of 256 was set. If a lower value is required, you must redefine the MAXAP value on the MSGRT macro and then rerun SIP stage I.

GEN159THE 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:

  1. Reduce the number of MSGRTA statements by the overage count specified in the error message.
  2. Rerun SIP stage I.

GEN161PROGRAM NAME xxxx DEFINED IN BSNCT MACRO IS NOT DEFINED BY A MSGRTA MACRO

Where:

xxxx
The application program name.

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:

  1. Code a MSGRTA macro for the application program name referenced in the message and defined in the BSNCT macro.
  2. Rerun SIP stage I.

GEN162VOLSER RANGE OF xxxx OVERLAYS THE VOLSER RANGE OF yyyy

Where:

xxxx
The first device type (an online device type, the copy module, or the loader general file).

yyyy
The second device type (an online device type, the copy module, or the loader general file).

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:

  1. Recode VOLNOx, PERMx, and EXTRx of the ONLFIL macro so that the overlap is eliminated.
  2. Recode VOLNLGF of the GENSIP macro so that the overlap is eliminated.
  3. Rerun SIP stage I.

GEN163xxxx RELATIVE MOD NUMBER IN LOGCAP MACRO TOO LARGE DEFAULTED TO HIGHEST MOD

Where:

xxxx
The relative module number.

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:

GEN164xxxx RELATIVE MOD NUMBER IN DDCCAP MACRO TOO LARGE DEFAULTED TO HIGHEST MOD NUMBER

Where:

xxxx
The relative module number.

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:

GEN171xxxx DEVICE NAME USED MORE THAN ONCE

Where:

xxxx
The device type.

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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN173BSNCT MACROS FOR THIS CPU=xx > BSC DROPS DEFINED IN LINES MACRO WHICH TOTAL yy

Where:

xx
The CPU ID.

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:

  1. Increase the BSCDRPS parameter or remove the BSNCT macro definitions to equal the BSCDRPS count.
  2. Rerun SIP stage I.

GEN175COMPUTED NUMBER OF MODULES (xxxx) EXCEEDS MAXIMUM (yyyy) ALLOWED

Where:

xxxx
The number of online modules.

yyyy
The general file modules.

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:

  1. Reduce the PERMx or the EXTRx parameters on the ONLFIL macro on the RAM macro.
  2. Rerun SIP stage I.

GEN179xxxx SUPPORT REQUESTED BUT yyyy SUPPORT REQUIRED AND NOT REQUESTED IN zzzz MACRO

Where:

xxxx
The program support requested through a SIP option, for example, mapping support.

yyyy
The optional program support required to allow the programming feature defined xxxx to process properly, for example, 3270 support must be included for mapping.

zzzz
The SIP user macro that contains the yyyy programming support missing, for example, the NETWK macro contains the 3270 support option.

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.

GEN182NUMBER OF PROCESSORS(xx) DEFINED IN CONFIG DIFFERS FROM THE NUMBER OF PRIME CRAS ENTRIES(yy) DEFINED IN CRASTB

Where:

xx
The number of processors.

yy
The number of prime computer room agent set (CRAS) entries.

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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GEN190NUMBER OF PROCESSORS (x) SPECIFIED IN CONFIG CONFLICTS WITH THE NUMBER OF UAT ENTRIES SPECIFIED IN NETWK (y). DEFAULT (= 2 × x) TAKEN.

Where:

x
The number of processors.

y
The number of initialization table (UAT) entries specified in the NETWK macro.

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:

GEN197NO VALID TAPE DRIVES WERE DEFINED BY IODEV

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Code the IODEV macros for the tape devices.
  2. Rerun SIP stage I.

GEN250MESSAGE 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:

  1. Remove the message router support.
  2. Rerun SIP stage I.

GEN255MACRO GLSYNC HAS COMMON=YES CODED FOR GLOBAL xxxx FOR AT LEAST ONE USER. xxxx COMMON CHANGED TO YES FOR PRIMARY USER (yyyy)

Where:

xxxx
The name of the global.

yyyy
The primary user.

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.

GEN256MACRO GLSYNC HAS COMMON=YES CODED FOR GLOBAL xxxx FOR AT LEAST ONE USER. xxxx ADDED TO PRIMARY SUBSYSTEM USER (yyyy)

Where:

xxxx
The global name.

yyyy
The primary user.

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.

GEN260RECORD xxxx MUST BE SPECIFIED FOR EACH USER. RECORD xxxx FOR USER yyyy WAS SPECIFIED INCORRECTLY AS COMMON

Where:

xxxx
The record.

yyyy
The user.

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:

  1. Specify the record for each user.
  2. Rerun SIP stage I.

GEN261RECORD xxxx WAS NOT FOUND, OR RECORD IS NOT 4K. DLU SUPPORT IS DISABLED.

Where:

xxxx
The file address compute program (FACE) type of the record.

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:

  1. Specify the FACE types and make sure they are defined as 4K in the SIP stage 1 deck.
  2. Run the FACE table generator (FCTGB) again.
  3. Run SIP stage 1 again.
Note:
See TPF Migration Guide: Program Update Tapes for more information about dynamic LU.

GEN270MACRO 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:

n
The value of the NFBACK parameter of the RAM macro. This defines the number of keypoint fallback extents in the #KEYPT record area.

p
The number of characters defining system IDs on the SYSID parameter of the CONFIG macro. This defines the number of processors that can be brought up in the loosely coupled complex that is being generated.

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.

GLO001PARAMETER xxxx EXCEEDS PARAMETER LIMIT OF 94

Where:

xxxx
The name of the parameter.

Severity: 5

Explanation: Only 94 items may be input in this parameter.

System Action: None.

User Response: Do the following:

  1. Correct the parameter by reducing the number of items in the parameter.
  2. Rerun SIP stage I.

GLO002xxxx OPERAND IGNORED-VALID ONLY IF yyyy=YES

Where:

xxxx
The keyword that was ignored.

yyyy
The name of the parameter.

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:

GLS001THE PARAMETER xxxx IS SPECIFIED AS yyyy. IT IS PREVIOUSLY SPECIFIED AS zzzz

Where:

xxxx
The parameter name.

yyyy
The form in which the parameter name is specified currently.

zzzz
The form in which the parameter name was specified previously.

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:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GLS002THE MAXIMUM NUMBER OF xxxx EXCEEDS yyyy

Where:

xxxx
Users, records, or fields.

yyyy
The maximum number of users, records, or fields.

Severity: 5

Explanation: The maximum yyyy for xxxx was exceeded.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I.

GLS003TYPE=FLD, BASE=x AND COMMON=y COMMON RESET TO z

Where:

x
The value for BASE (for example, Y or A).

y
The value for COMMON (for example, YES or NO).

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:

GLS004THE GLOBAL NAME xxxx IS RESERVED FOR SYSTEM USAGE

Where:

xxxx
The name of the global.

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:

  1. Change the global name or eliminate the GLSYNC statement.
  2. Rerun SIP stage I.

GTSZ0001TCANNOT OPEN OUTPUT FILE filename

Where:

filename
name of the output file

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.

GTSZ0002TCANNOT OPEN THE PDS DIRECTORY directory AS THE INPUT FILE.

Where:

directory
name of the PDS directory

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:

  1. Determine why the PDS cannot be opened.
  2. Take the necessary corrective action.
  3. Run GTSZ again.

See TPF System Generation for more information on GTSZ.

GTSZ0003TREADING THE PDS DIRECTORY FOR directory HAS FAILED.

Where:

directory
name of the PDS directory

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:

  1. Determine why the PDS cannot be read.
  2. Take the necessary corrective action.
  3. Run GTSZ again.

See TPF System Generation for more information on GTSZ.

GTSZ0004WTHE SIZE COULD NOT BE FOUND FOR member

Where:

member
The name of a member in a data set.

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:

  1. Check the version code on the input member name that could not be found.
  2. Run GTSZ again.

See TPF System Generation for more information on GTSZ.