gtpm4m1rMessages (System Error and Offline)

SALO-SYN0

SALO0001WTWO INPUT PARAMETERS REQUIRED. SALO ASSUMING 2147483650 PROGRAM RECORDS AND A BSS GENERATION

Explanation: The system allocator (SALO) expects at least:

System Action: None.

User Response: Run SALO again if the default values are not acceptable.

SALO0002WTOO MANY INPUT PARAMETERS. IGNORING ADDITIONAL PARAMETERS.

Explanation: The system allocator (SALO) expects a maximum of five input parameters, each separated by one or more spaces.

System Action: None.

User Response: Run SALO again if the parameters being passed to it are not correct.

SALO0003WNUMBER OF PROGRAM RECORDS CODED EVALUATES TO 0. PROCESSING CONTINUES ASSUMING 2147483650 PROGRAM RECORDS.

Explanation: The value passed in the PROG parameter to SALO was not numeric or was zero.

System Action: None.

User Response: Run SALO again if the default value is not correct.

SALO0004WSUBSYSTEM NAME MISSING FROM INPUT PARAMETERS. DEFAULTING TO BSS.

Explanation: The SS parameter was coded without a parameter specified.

System Action: None.

User Response: Do the following:

  1. Code the SS parameter with a valid subsystem name.
  2. Run SALO again if the default values are not correct.

SALO0005TUNABLE TO OPEN SAL TABLE OUTPUT FILE.

Explanation: The were was an error in opening the system allocator table (SAL) output file (SALOUT).

System Action: Processing is ended.

User Response: Ensure that the output data set exists and its LRECL is 12 bytes.

SALO0006TUNABLE TO OPEN PAT OUTPUT FILE

Explanation: There was an error in opening the program allocation table (PAT) output file (PATOUT).

System Action: Processing is ended.

User Response: Ensure that the output data set exists and its LRECL is 80 bytes.

SALO0007TUNABLE TO OPEN INPUT DECK(S)

Explanation: There was an error in opening one or more of the input decks (INFILE).

System Action: Processing is ended.

User Response: Ensure that the input deck exists and that the LRECL of the input data set is 80 bytes.

SALO0008TNOT ENOUGH PROGRAM RECORDS ALLOCATED

Explanation: The value passed to the system allocator (SALO) through the PROG parameter was smaller than the number of programs to be allocated in the input deck.

System Action: Processing is ended.

User Response: Do the following:

  1. Increase the number of program records (through #PROG1) allocated in RAMFIL to contain the number of programs being allocated.
  2. Rerun the FACE table generator.
  3. Rerun SALO with the value specified on the PROG parameter equal to the number of #PROG1 records allocated.

SALO0009EINVALID PROGRAM NAME

Explanation: One of the following errors occurred:

System Action: The program is not allocated.

User Response: Code the program name correctly.

SALO0010EPROGRAM NAME ALREADY ALLOCATED

Explanation: The program name that is being allocated was already allocated.

System Action: The statement is ignored.

User Response: Do one of the following:

SALO0011EINVALID PROGRAM TYPE

Explanation: The program type coded was not one of the following:

System Action: The statement is ignored.

User Response: Code the program type as CR, FR, or TV.

SALO0012EEXTRANEOUS SPARE PROGRAM DATA

Explanation: Additional characters were found on the SPARE type statement. The SPARE type statement has no parameters.

System Action: The card is ignored.

User Response: Remove the additional characters.

SALO0013ENO TV PARENT PROGRAM NAME

Explanation: The transfer vector (TV) type statement did not have a parent program name coded.

System Action: The card is ignored.

User Response: Code the parent program name following the transfer vector (TV) characters.

SALO0014EINVALID TV PARENT PROGRAM NAME

Explanation: One of the following errors exists in the transfer vector (TV) parent program name:

System Action: The card is ignored.

User Response: Code the parent program name correctly.

SALO0015ETV PARENT PROGRAM NAME HAS NOT BEEN ALLOCATED

Explanation: The parent program name coded was not allocated.

System Action: The card is ignored.

User Response: Ensure that the parent program name is allocated before any transfer vectors (TVs) that point to that parent are allocated.

If the parent program allocation card was in error, this message will be issued for all TVs of the parent program.

SALO0016EINVALID CLASS

Explanation: The value coded for the CLASS parameter is not one of the following:

System Action: The card is ignored.

User Response: Ensure that the value coded for the CLASS parameter is one of the following:

SALO0017EINVALID CLASS FOR CR PROGRAM

Explanation: The value coded for the CLASS parameter of a core resident (CR) program is not SHARED or COMMON.

System Action: The card is ignored.

User Response: Ensure that the value coded for the CLASS parameter is SHARED or COMMON.

SALO0018EINVALID MODE

Explanation: The value coded for the MODE parameter is not 24BIT or 31BIT.

System Action: The card is ignored.

User Response: Ensure that the value coded for the MODE parameter is 24BIT or 31BIT.

SALO0019EINVALID OPTIONS

Explanation: One of the values coded for the OPTIONS parameter is not valid.

System Action: The card is ignored.

User Response: Ensure that the value coded for the OPTIONS parameter is valid or that the option coded exists in the users authorization list defined in c$idsalo.

SALO0020EINVALID SYMBOL DEFINITION NAME

Explanation: The symbol definition name does not have an alphabetic first character or the last two characters are not alphanumeric.

System Action: The card is ignored.

User Response: Code the name correctly.

SALO0021ESYMBOL DEFINITION NAME ALREADY DEFINED

Explanation: The symbol definition name is already defined.

System Action: The card is ignored.

User Response: Do one of the following:

SALO0022EINVALID SYMBOL DEFINITION TYPE

Explanation: The symbol definition type was not POOL.

System Action: The card is ignored.

User Response: Code the TYPE parameter with a symbol definition type of POOL.

SALO0024EVALUE PARAMETER MISSING FROM POOL DEFINITION STATEMENT

Explanation: The VALUE parameter on a POOL definition statement is required.

System Action: The card is ignored.

User Response: Code the VALUE parameter.

SALO0025EEXTRANEOUS POOL SYMBOL DEFINITION DATA

Explanation: Additional characters were found on the POOL symbol definition statement. Only the VALUE= parameter is valid.

System Action: The card is ignored.

User Response: Remove the additional characters.

SALO0026EINVALID PROGRAM OR SYMBOL DEFINITION NAME

Explanation: Only a four character program name, a three character symbol definition, or SPARE can begin a statement.

System Action: The card is ignored.

User Response: Code one of the following:

SALO0027ENO TV NUMBER

Explanation: No transfer vector (TV) number was specified in the statement. This is required right after the parent program name.

System Action: The card is ignored.

User Response: Code a valid TV number.

SALO0028EINVALID TV NUMBER

Explanation: The transfer vector (TV) number specified was not numeric.

System Action: The card is ignored.

User Response: Code a valid TV number.

SALO0029EINVALID PARAMETER SPECIFIED ON INPUT STATEMENT

Explanation: On a core resident (CR) or file resident (FR) program allocation statement, additional characters where found. The following are the only valid parameters:

System Action: The card is ignored.

User Response: Remove the characters that are not valid.

SALO0030EPOOL SYMBOL DEFINITION VALUE DATA MUST BE 6 CHARACTERS LONG

Explanation: The hexadecimal number coded on the VALUE parameter contains six characters.

System Action: The card is ignored.

User Response: Code a valid six character value.

SALO0031EEXTRANEOUS PARAMETER ON STATEMENT

Explanation: Extraneous characters where found on a TAPE symbol definition statement. Only the VALUE parameter is valid.

System Action: None.

User Response: Remove the additional characters.

SALO0032ETRANSFER VECTOR NUMBER OUT OF RANGE

Explanation: The transfer vector (TV) number specified was not in the range of 0 to 1023.

System Action: The card is ignored.

User Response: Code a valid TV number.

SALO0034ETRANSFER VECTOR PARENT CANNOT BE A TRANSFER VECTOR ITSELF

Explanation: The parent name coded for this statement is also a transfer vector.

System Action: The card is ignored.

User Response: The parents allocation is incorrect and should be changed or the parent name coded for the transfer vector is not correct.

SALO0035EINVALID POOL SYMBOL DEFINITION VALUE

Explanation: The value coded does not match one of the valid values.

System Action: The card is ignored.

User Response: None.

See TPF System Installation Support Reference for more information about valid values.

SALO0036EUNDEFINED FUNCTION SWITCH

Explanation: The value coded for the FUNC parameter does not exist.

System Action: The card is ignored.

User Response: Code a valid function switch name. The list of valid names is in c$idfunc.

SALO0037EINVALID MODE ON MODE STATEMENT

Explanation: The value coded for MODE on the MODE statement is not 24BIT or 31BIT.

System Action: The card is ignored.

User Response: Code a valid MODE value on the MODE statement.

SALO0038TERROR WRITING TO OUTPUT FILE

Explanation: An error occurred when writing the system allocator table (SAL) or the program allocation (PAT) table.

System Action: Processing is ended.

User Response: Verify that the output files exist and that there is enough space to contain the output.

SALO0039TERROR ALLOCATING STORAGE

Explanation: An error occurred when the system allocator (SALO) tried to get a piece of dynamic storage.

System Action: Processing is ended.

User Response: Increase the size of the region in which your program is running.

SALO0040EPREMATURE END OF FILE

Explanation: An end of file was reached in the middle of a continued line.

System Action: The card is ignored.

User Response: Check the last statement in the input file. The statement should not end with a continuation character.

SALO0041ICONTENTS OF SAL TABLE -- BEGIN

Explanation: The content of the system allocator table (SAL) is displayed.

System Action: None.

User Response: None.

SALO0042ICONTENTS OF SAL TABLE -- END

Explanation: The end of the system allocator table (SAL).

System Action: None.

User Response: None.

SALO0043ITHE FOLLOWING PARAMETERS WERE PASSED TO SALO list

Where:

list
The list of parameters.

Explanation: The list of parameters referenced in the message is picked up by the system allocator (SALO).

System Action: None.

User Response: None.

SALO0044Wxxx= PARAMETER CODED MORE THAN ONCE. ADDITIONAL CODINGS IGNORED

Where:

xxx
The name of the parameter.

Explanation: The parameter referenced in the message was coded more than once.

System Action: None.

User Response: Remove the extraneous parameters.

SALO0045Wxxx= PARAMETER INVALID. DEFAULTING TO yyyy.

Where:

xxx
The name of the parameter.

yyyy
The default.

Explanation: The parameter referenced in the message was coded with a value that is not valid. Therefore, the default referenced in the message was assumed.

System Action: None.

User Response: Code the parameter correctly.

SALO0046Wxxx= NOT CODED. DEFAULTING TO yyyy.

Where:

xxx
The name of the parameter.

yyyy
The default.

Explanation: The parameter referenced in the message was not coded. The default referenced in the message was assumed.

System Action: None.

User Response: Code the parameter again if the default is not acceptable.

SALO0047ECONTINUED LINE DIDN'T BEGIN WITH A SPACE

Explanation: Continued lines must begin with one or more spaces.

System Action: The statement is ignored.

User Response: Code the continued line starting with one or more spaces. If the line flagged in error is a new line, remove the continuation character from the previous line.

SALO0048EINVALID SUBSYSTEM NAME

Explanation: The subsystem name specified for the SS parameter is not valid.

System Action: The statement is ignored.

User Response: Specify a valid subsystem name for the SS parameter. The subsystem name can contain between one and four characters.

SALO0049EPRELOAD INCOMPATIBLE WITH FR

Explanation: The PRELOAD parameter is valid only for core resident programs.

System Action: The statement is ignored.

User Response: Do one of the following:

SALO0050TUNABLE TO OPEN SAL REPORT OUTPUT FILE

Explanation: There was an error in opening the system allocator table (SAL) report output file (SALRPT).

System Action: Processing is ended.

User Response: Ensure that the output DD name SALPRT is defined.

SALO0051TUNABLE TO WRITE TO OUTPUT FILE.

Explanation: There was an error in writing the:

System Action: Processing is ended.

User Response: Ensure that there is enough space in the output data sets to hold the output files.

SALO0052TUNABLE TO OPEN OUTPUT LISTING FILE

Explanation: There was an error in opening the output listing file (LSTFILE).

System Action: Processing is ended.

User Response: Ensure that the DD name LSTFILE is defined.

SALO0053WTHIS PROGRAM IS OVERWRITING A DUMMY ENTRY

Explanation: The program being allocated has the same name as a previous program that was allocated as a dummy program.

System Action: None.

User Response: If the warning is acceptable to you, there is nothing further to do.

Otherwise, you must change the current program name so that it is unique.

SSD001THE SUM OF THE SSUIDS CODED (xxx) EXCEEDS THE MAXIMUM ALLOWED (yyy)

Where:

xxx
The total number of subsystem user IDs (SSUIDs).

yyy
The maximum number of SSUIDs allowed.

Severity: 5

Explanation: The total number of subsystem user IDs defined and specified in the SSUID1 through the SSUID4 parameter exceeds the maximum allowed.

System Action: None.

User Response: Do the following:

  1. Correct the SSUID1, SSUID2, SSUID3, or SSUID4 parameter to ensure that the total number of names specified does not exceed the maximum allowed.
  2. Rerun SIP stage I.

SSD002xxx PARAMETER yyy DUPLICATE OF NAME PREVIOUSLY DEFINED, NOT ALLOWED

Where:

xxx
The parameter list.

yyy
The parameter name.

Severity: 5

Explanation: Only unique names may be specified for each subsystem user. The name specified by yyy in the parameter list of xxx is a duplicate of a previously defined name.

System Action: None.

User Response: Do the following:

  1. Correct the duplicate subsystem user name.
  2. Rerun SIP stage I.

SSD004THE SUM OF THE VALUES CODED FOR TOTSSU AND TOTSS EXCEEDS 128.

Severity: 5

Explanation: The number of subsystem users plus the number of subsystems must not exceed 128.

System Action: None.

User Response: Do the following:

  1. Correct one or both parameters in question.
  2. Rerun SIP stage I.

SSD005SSNAME PARAMETER (xxx) INVALID, NAME RESERVED FOR SYSTEM USE

Where:

xxx
The parameter name.

Severity: 5

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Correct the SSNAME parameter.
  2. Rerun SIP stage I.

SSD006BASIC SUBSYSTEM GENERATION INDICATED BUT SSNAME NOT 'BSS'. SSNAME SET TO 'BSS'.

Severity: 0

Explanation: The BSSGEN parameter is equal to YES indicating that a basic subsystem generation is required, but the subsystem name is not BSS as required. The system initialization program (SIP) reset the subsystem name to BSS.

System Action: None.

User Response: Do one of the following:

SSD007SSNAME=BSS BUT BSSGEN=NO CODED, RESET TO BSSGEN=YES

Severity: 0

Explanation: The subsystem name of BSS can only be used if the subsystem generation parameter is BSSGEN=YES. The system initialization program (SIP) reset BSSGEN=NO to BSSGEN=YES.

System Action: None.

User Response: Do one of the following:

STA001xxxx PARAMETER OF yyyy MACRO IS OMITTED OR INVALID

Where:

xxxx
The parameter name.

yyyy
The macro name.

Severity: 5

Explanation: The parameter of the macro referenced in the message was omitted or contains data that is not valid.

System Action: None.

User Response: Do the following:

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

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA002xxxx PARAMETER OF yyyy MACRO IS OMITTED OR INVALID. ASSUMED DEFAULT IS zzzz

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The assume default.

Severity: 0

Explanation: The parameter of the macro referenced in the message was omitted or contains data that is not valid. The assumed default is zzzz.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I if the assumption is not valid.

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA003xxxx PARAMETER OF yyyy MACRO IS OMITTED OR INVALID IN A zzzz ENVIRONMENT. ASSUMED DEFAULT IS jjjj

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The type of environment.

jjjj
The assumed default.

Severity: 0

Explanation: The parameter of the macro referenced in the message was omitted or contains data that is not valid in the environment indicated. The assumed default is jjjj.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I if the assumption is not valid.

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA004xxxx PARAMETER OF THE yyyy MACRO IS OMITTED OR INVALID IN A zzzz ENVIRONMENT.

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The type of environment.

Severity: 5

Explanation: None.

System Action: None.

User Response: None.

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA005xxxx PARAMETER OF THE yyyy MACRO IS EXTRANEOUS IN A zzzz ENVIRONMENT

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The type of environment.

Severity: 0

Explanation: When an environment such as the one referenced in the message exists, the functions or information provided by the parameter referenced in the message is not needed.

System Action: The parameter is ignored.

User Response: None.

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA006wwww IS OUTSIDE RANGE xxxx-yyyy IN MACRO zzzz

Where:

wwww
May be a single value or a range.

xxxx-yyyy
Defines the boundaries of a range that wwww is not within.

zzzz
The macro in which the error occurred.

Severity: 7

Explanation: The range is not valid for the macro.

System Action: None.

User Response: In general, recode the parameter or parameters that are at fault and rerun SIP stage I.

However, keep the following in mind:

STA007xxxx PARAMETER OF yyyy MACRO IS NOT zzzz.

Where:

xxxx
The name of the parameter.

yyyy
The name of the macro.

zzzz
A quality or a requirement.

Severity: 7

Explanation: The parameter of the macro referenced in the message is not the proper quality or requirement.

System Action: None.

User Response: Do the following:

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

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA008xxxx IS A DDNAME CODED ON THE yyyy PARAMETER: zzzz. HOWEVER, IT VIOLATES MVS DATASET NAMING CONVENTIONS.

Where:

xxxx
The DDNAME coded.

yyyy
The macro name.

zzzz
The parameter name.

Severity: 5

Explanation: xxxx was coded on the parameter of the macro referenced in the message. xxxx must be a valid IBM MVS data set name.

System Action: None.

User Response: Do the following:

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

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information.

STA009xxxx PARAMETER OF yyyy HAS AN EXCESSIVE NUMBER OF SUBPARAMETERS. THE MAXIMUM ALLOWED IS: zzzz

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The maximum subparameters allowed.

Severity: 5

Explanation: The parameter of the macro referenced in the message has too many subparameters. The maximum subparameters allowed is indicated in the message.

System Action: None.

User Response: Do the following:

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

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for more information about coding the parameter.

STA010xxxx PARAMETER OF yyyy MACRO CONTAINS MORE THAN zzzz CHARACTERS. THE PARAMETER HAS BEEN TRUNCATED AND IS rrrr

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The number of characters allowed.

rrrr
The value to which the parameter was truncated.

Severity: 0

Explanation: The parameter of the macro referenced in the message was coded with more than the indicated number of characters. Therefore, the parameter was truncated. If the truncation. is not acceptable, then the macro must be coded with no more than the number of characters referenced in the message.

System Action: None.

User Response: Do the following:

  1. Make the necessary corrections.
  2. Rerun SIP stage I if the truncation is not acceptable.

STA011xxxx PARAMETER OF yyyy MACRO MUST BE NUMERIC AND GREATER THAN ZERO.

Where:

xxxx
The parameter name.

yyyy
The macro name.

Severity: 5

Explanation: The parameter of the macro referenced in the message was coded as a 0 or contained non-numeric characters.

System Action: None.

User Response: Do the following:

  1. Code a non-zero value for the parameter.
  2. Rerun SIP stage I.

STA012xxxx PARAMETER OF yyyy MACRO FOR THE zzzz APPL IS NOT APPROPRIATE

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The application program name.

Severity: 5

Explanation: An inappropriate parameter for the application program referenced in the message was coded for the macro indicated.

System Action: None.

User Response: Do the following:

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

STA013VALUE xxxx CODED FOR PARAMETER yyyy OF MACRO zzzz IS INVALID

Where:

xxxx
The value coded for the macro.

yyyy
The parameter name.

zzzz
The macro name.

Severity: 5

Explanation: The value coded for the macro referenced in the message is not valid.

System Action: None.

User Response: Do the following:

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

See TPF System Macros or TPF General Macros (whichever book is appropriate for the macro referenced in the message) for a list of correct values.

STA014vvvv IS OUTSIDE RANGE wwww-xxxx IN MACRO yyyy. ASSUMED DEFAULT IS zz

Where:

vvvv
The parameter name.

wwww-xxxx
Defines the boundaries of a range that the parameter is not within.

yyyy
The macro where the error occurred.

zz
The assumed default.

Severity: 0

Explanation: The parameter referenced in the message is outside the acceptable range for the macro. Therefore, the value of the parameter was reset to the value indicated in the message.

System Action: None.

User Response: Do one of the following:

STPP0001EPERMANENT IO ERROR ON TAPE/SYNAD ENTERED

Explanation: An error occurred while reading the real-time (RTx) tape during post processing. The SYNAD error analysis function will be entered to analyze the error data. This message is sent to the printer only. The error data will be sent in message STPP0002T.

System Action: None.

User Response: None.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0002T 

Explanation: This message contains the tape read error information gathered by the SYNAD error analysis function. The information in this message varies based on the type of error that occurred. This message is sent to the printer only.

System Action: The STPP program is abended with a U2222 error.

User Response: None.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0003T*** RTL DUMP RECORD VALIDITY CHECK FAILED ***

Explanation: A DP record was encountered on the dump tape whose header contains a series of byte counts that, when added together, do not match the count of data bytes actually read. This indicates a problem with the online system (copy member CEDT of the CCCPSE CSECT). This message is sent to the printer only.

System Action: The STPP program is abended with a U2222 error.

User Response: The dump data cannot be postprocessed. Have your IBM service representative review the IBM MVS dump. Register 4 contains the sum of the byte counts extracted from the record header; register 8 contains the actual count of data bytes read, obtained from the RTL tape DCB and adjusted by the size of the record header and trailer. This information, along with the dump tape if possible, should be forwarded to your IBM service representative for problem determination and correction.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0004T*** NEXT TAPE VOLUME REQUIRED TO CONTINUE PROCESSING ***

Explanation: An end-of-file was unexpectedly encountered while postprocessing a dump. The remaining dump data is contained on succeeding tape volumes. This message is sent to the printer only.

System Action: The STPP program is abended with a U2999 error.

User Response: Do the following:

  1. If the remaining dump output is desired, modify the volser list on the SYS000 DD statement of the postprocessor JCL to include the missing tape volumes.
  2. Run the job again.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0005T*** INVALID TAPE -- NO DATA ON TAPE ***

Explanation: An end-of-file was unexpectedly encountered while postprocessing a tape, before any data records were read. This message is sent to the printer only.

System Action: The STPP program is abended with a U2999 error. The tape cannot be postprocessed.

User Response: None.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0006T*** TAPE VOLUME IS CONTINUATION FROM PREVIOUS -- FIRST VOLUME REQUIRED TO PROCESS ***

Explanation: The user requested one or more dumps from a dump tape but an end-of-file was encountered before a DX record was read. This indicates that no dumps begin on this volume. This message is sent to the printer only.

System Action: The STPP program is abended with a U2999 error.

User Response: Do the following:

  1. Locate the volume containing the first dump record for the desired dumps and add it to the volser list on the SYS000 DD statement of the postprocessor JCL.
  2. Run the job again.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0007T*** RTL DX RECORD VALIDITY CHECK FAILED ***

Explanation: The amount of dump label table data read from one or more DX records on the tape exceeds the actual size of the dump label table. This indicates a problem with the online system (copy member CEDT of the CCCPSE CSECT)). This message is sent to the printer only.

System Action: The STPP program is abended with a U2222 error.

User Response: The tape cannot be postprocessed. Have your IBM service representative review the IBM MVS dump. Register 3 points to the header of the current DX record. Register 8 contains the amount of DX record data read so far. This information, along with the dump tape if possible, should be forwarded to your IBM service representative. for problem determination and correction.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STPP0008W*** VOLSER LIST OUT OF SEQUENCE ***

Explanation: The tape volumes that appear in the volser list on the SYS000 DD statement of the postprocessor JCL for multivolume postprocessing are not listed in the same order in which the TPF system wrote to them. This message is sent to the printer only.

System Action: The dump continues to be processed.

User Response: Do the following:

  1. Change the order of volume serial numbers in the volser list.
  2. Run the job again.

See TPF Program Development Support Reference for more information about the diagnostic output formatter.

STUB0001ICALL STUB CREATED FOR PROGRAM pgmn

Where:

pgmn
The program name.

Explanation: A call stub was successfully created for the program.

System Action: Processing continues.

User Response: None.

STUB0010WNO PROGRAM NAMES WERE INPUT

Explanation: There are no program names listed in the input file.

System Action: No stubs are created.

User Response: Include program names in the input file.

STUB0100EINVALID PGM NAME - inputline

Where:

inputline
The input line containing the program name that is not valid.

Explanation: A program name was found that is not valid.

System Action: The input line is skipped and no stub is generated.

User Response: Correct the input line; update the line with a valid 4-character program name or comment.

STUB0101EERROR GENERATING STUB - pgmn

Where:

pgmn
The 4-character stub name.

Explanation: An error was found while attempting to create the stub on file. There is a problem with the SYSOUT output file.

System Action: No stub is generated and processing continues.

User Response: Do the following:

  1. Determine the problem with the SYSOUT file.
  2. Correct the problem.

STUB1200TUNABLE TO OPEN OUTPUT FILE

Explanation: An error occurred while attempting to open the output file.

System Action: The program stops running after processing the remainder of the input file and no stubs are created.

User Response: Correct the DD specification used when invoking the DLM Stub Generator Tool.

STUB1202TUNABLE TO CLOSE OUTPUT FILE

Explanation: An error occurred while trying to close the output file. The partitioned data set (PDS) or the disk may be out of space.

System Action: The program stops running and no more dynamic load module (DLM) stubs are created.

User Response: Do the following:

  1. Correct the PDS or disk space problems.
  2. Run the DLM stub generator tool again.

SYN001FIELD yyyy IN ROUTING TABLE xxxx IS INVALID

Where:

yyyy
The field that is not valid.

xxxx
The name of the routing table.

Severity: 5

Explanation: The field in the routing table is not valid because it:

One of the following occurred:

System Action: None.

User Response: Do the following:

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

SYN002AILST EQUALS INPUT, AIRTE IGNORED

Severity: 0

Explanation: If AILST=INPUT, then AIRTE is not required.

System Action: None.

User Response: None.

SYN003NPOOL OPERAND xxxx NOT A MULTIPLE OF 8

Where:

xxxx
The value that is not valid in the operand.

Severity: 5

Explanation: None.

System Action: None.

User Response: Do the following:

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

SYN004NLRT VALUE xxxx LESS THAN NUMBER OF ROUTING TABLES

Where:

xxxx
The value assigned to NLRT.

Severity: 5

Explanation: The number of routing tables specified in this macro exceeds the value assigned to NLRT. The NLRT value may be greater than or equal to the number of routing tables.

System Action: None.

User Response: Do the following:

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

SYN005N1LNK AND NLINK CONFLICT

Severity: 5

Explanation: One of the following errors occurred:

System Action: None.

User Response: Do the following:

  1. Correct NLINK or N1LNK.
  2. Rerun SIP stage I.

SYN006NUMBER OF ROUTING TABLES EXCEED MAXIMUM OF 50

Severity: 5

Explanation: None.

System Action: None.

User Response: Do the following:

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

SYN007xxxx ROUTING TABLE FORMAT INVALID

Where:

xxxx
The routing table that is not valid.

Error Message: 5

Explanation: The routing table:

IND is the only optional field.

System Action: None.

User Response: Do the following:

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