gtpm4m1vMessages (System Error and Offline)

ZZZ0

ZZZ001PROG OR MAC OPERAND INVALID

Severity: 7

Explanation: The PROG or MAC operands of the SPUPD macro were:

The SPUPD call occurred in the GENSIP macro.

System Action: None.

User Response: Do the following:

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

ZZZ002PARM=xxxx OPERAND INVALID FOR yyyy MACRO. DEFAULT zzzz USED

Where:

xxxx
The parameter name.

yyyy
The macro name.

zzzz
The default value.

Severity: 0

Explanation: The macro referenced in the message was called by the GENSIP macro with a parameter that is not valid. A default value was provided. This MNOTE indicates an error in the GENSIP macro.

System Action: None.

User Response: Do the following:

  1. In the GENSIP macro, locate the macro call that is not valid.
  2. Update the GENSIP macro source code to correct the parameter that is in error, if the default value provided is not correct. Then, continue with step 3.

    If the default value is acceptable, no further action is required.

  3. Rerun SIP stage I.

ZZZ003DSN OPERAND OF SPUPD MACRO INVALID

Severity: 7

Explanation: The name as specified in the DSN operand of SPUPD macro contained less than 2 or more than 8 characters. The SPUPD call occurred in the GENSIP macro.

System Action: None.

User Response: Do the following:

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

ZZZ004FIRST POSITIONAL PARAMETER OF SPUPD NOT JCL

Severity: 7

Explanation: This parameter may only contain JCL, if present. The error occurred in a SPUPD macro call in the GENSIP macro.

System Action: None.

User Response: Do the following:

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

ZZZ005PROG OPERAND OMITTED

Severity: 7

Explanation: The PROG operand in a SPASM macro call was omitted. This error occurred in the GENSIP macro.

System Action: None.

User Response: Do the following:

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

ZZZ006RELEASE LEVEL xxxx INVALID IN PLIB OPERAND

Where:

xxxx
The release level.

Severity: 7

Explanation: The error occurred in a SPASM macro call of the GENSIP macro. The release level for the specified program in the PLIB operand was not valid.

System Action: None.

User Response: Do the following:

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

ZZZ010PROGRAM TYPE xxxx INVALID

Where:

xxxx
The program type.

Severity: 7

Explanation: The program type, as specified in a SPPBLD macro call, is not a valid type.

System Action: None.

User Response: Do the following:

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

ZZZ011yyyy PROGRAM NAME xxxx INVALID

Where:

yyyy
The keypoint or real-time program name.

xxxx
The program name.

Severity: 7

Explanation: The program that is not valid was specified in a SPPBLD macro call. A real-time or keypoint program name must be 6 characters in length.

System Action: None.

User Response: Do one of the following:

ZZZ012xxxx PGM LIST OVERFLOW, INCREASE DIMENSION yyyy AND SET zzzz to THAT VALUE

Where:

xxxx
The program type.

yyyy
The global variable symbol.

zzzz
The value of the global variable.

Severity: 7

Explanation: The error occurred in the SPPBLD macro calls of SPPGML. Table space was exhausted for the program types referenced in the message.

System Action: None.

User Response: Do the following:

  1. Increase the dimension of the global variable symbol in the SPGLB macro.
  2. Set the variable symbol in the SPTABS macro to the global variable symbol dimension.
  3. Rerun the pre-SIP assembly.

ZZZ015TYPE xxxx INVALID

Where:

xxxx
The TYPE parameter that is not valid. Valid types are DEVxP and DEVxN (where x = (A, B, C, or D).

Severity: 7

Explanation: The RANGE macro was called by the DDCCAP macro and contained a TYPE parameter that is not valid. This is a system error requiring a correction to the DDCCAP macro.

System Action: None.

User Response: Do the following:

  1. Locate the RANGE macro instruction in the DDCCAP macro, which contains the error.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

ZZZ016LIST OPERAND xxxx CONTAINS MORE THAN 6 SUBOPERANDS

Where:

xxxx
The operand.

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Locate the RANGE macro instruction in the DDCCAP macro.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

ZZZ017LIST OPERAND MISSING

Severity: 7

Explanation: The RANGE macro called by the DDCCAP macro did not contain a LIST operand that is required.

System Action: None.

User Response: Do the following:

  1. Locate the RANGE macro in the DDCCAP macro.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

ZZZ018FLD AND/OR TYPE PARAMETER MISSING OR INVALID IN SPRANG MACRO

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Locate the SPRANG macro instruction.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

ZZZ019INVALID TYPE (.xxxx) SPECIFIED IN SPASM/SPASMS MACRO

Where:

xxxx
The type that is not valid.

Severity: 7

Explanation: None.

System Action: None.

User Response: Do the following:

  1. Locate the SPASM/SPASMS macro.
  2. Make the necessary corrections.
  3. Rerun SIP stage I.

ZZZ020SKIP-SWITCH TABLE CAPACITY EXCEEDED

Severity: 7

Explanation: The &XBSKIP table deals with the EXPRS parameter of the GENSIP macro. A value greater than the length of this table is being referenced.

System Action: None.

User Response: Do the following:

  1. Update the size of the table.
  2. Rerun SIP stage I.

ZZZ021PARAMETER xxxx IS NOT VALID FOR yyyyyy MACRO WHEN TYPE zzz IS USED. PARAMETER IS IGNORED.

Where:

xxxx
The parameter name.

yyyyyy
The macro name.

zzz
The type of program that was coded on the macro.

Severity: 0

Explanation: The program type that you coded on the macro is not compatible with the parameter that was coded.

System Action: The parameter is ignored.

User Response: Do one of the following:

  1. Correct the program type.
  2. Remove the parameter.