gtpm4m1gMessages (System Error and Offline)

CBLD-CRA0

CBLD0000ILOAD MODULE BUILD JCL PRODUCED

Explanation: The C load module build tool has successfully completed building JCL to link the load module. Note that this message only means the JCL was created successfully. There may have been errors that will cause the JCL to create an incorrect load module.

System Action: None.

User Response: Check the return code. A return code of 8 means there were errors that may have affected the JCL that was created.

CBLD0400Wlinenumber: UNRECOGNIZED RUN-TIME OPTION option IS IGNORED

Where:

linenumber
The number of the line within the build script that contains the error.

option
The text of the unrecognized runtime option.

Explanation: The C load module build tool runtime option list includes text beyond the expected type and module.

System Action: The unrecognized option text is ignored by the C load module build tool.

User Response: Correct the C load module build tool runtime option list so that it does not include extraneous information.

CBLD0401Wlinenumber: THERE IS ONLY ONE VALID RUN-TIME OPTION - DEFAULTING TO JCL

Where:

linenumber
The number of the line within the build script that contains the error.

Explanation: The C load module build tool runtime option list includes an incorrect option.

System Action: The default value for the runtime option is assumed by the C load module build tool.

User Response: Correct the C load module build tool runtime option list.

CBLD0402Wlinenumber: SPECIFIED VERSION CODE code IS NOT VALID - DEFAULT TO 40

Where:

linenumber
The number of the line in the build script that contains the error.

code
The version code in error.

Explanation: The C load module build tool encountered a line of input in the build script where the version code is not valid. The version code must be 2 alphanumeric characters.

System Action: The default value 40 is assumed by the C load module build tool.

User Response: Do the following:

  1. Correct the version code.
  2. Run the C load module build tool again.

CBLD0410Wlinenumber: MORE THAN TYPE AND MODULE SPECIFIED

Where:

linenumber
The number of the line within the build script that contains the error.

Explanation: The C load module build tool found a line of input in the build script whose format is in error. If this line was intended to specify an object module to be linked into the C load module, it will not be included because the input line is ignored.

System Action: The input line is ignored and processing continues.

User Response: Check the build script. If the line in error cannot be ignored, then correct the build script and run the C load module build tool again.

CBLD0411IONE OR MORE OBJECT FILE NAMES ARE 1 OR 2 CHARACTERS LONG. BLANKS USED FOR VERSION CODE.

Explanation: The C load module build tool (CBLD) detected that one or more object files included in a build script have names that are only 1 or 2 characters long. Blanks are used for the 2-character version code.

System Action: None.

User Response: None.

See TPF Application Programming for more information about CBLD.

CBLD0412IONE OR MORE OBJECT FILE NAMES ARE 3 TO 5 CHARACTERS LONG. LAST 2 CHARACTERS USED FOR VERSION CODE.

Explanation: The C load module build tool (CBLD) detected that one or more object files included in a build script have names that are 3 to 5 characters long. The last 2 characters in the object file name are used as the 2-character version code.

System Action: None.

User Response: None.

See TPF Application Programming for more information about CBLD.

CBLD0801Elinenumber: MORE THAN ONE OBJECT NAME SPECIFIED

Where:

linenumber
The number of the line within the build script that contains the error.

Explanation: The C load module build tool found a line of input in the build script that contains more than 1 object module name before any comments.

System Action: The input line is ignored and processing continues.

User Response: Check the build script. If the line in error cannot be ignored, then correct the build script and run the C load module build tool again.

CBLD0803ENO OBJECT FILE SPECIFIED IN BUILD SCRIPT

Explanation: The C load module build tool (CBLD) created the job control language (JCL) to link the startup code for the C load module but there is no object file being included.

System Action: None.

User Response: Check the build script to ensure that no object file needs to be specified.

See TPF Application Programming for more information about CBLD.

CBLD0804Elinenumber: OBJECT FILE NAME EXCEEDS 8 CHARACTERS.

Where:

linenumber
The number of the line in the build script that contains the error.

Explanation: The C load module build tool detected that the object file included in a build script has a name that is more than 8 characters long.

System Action: The input line containing the object file name in error is ignored and processing continues.

User Response: Do the following:

  1. Check the format of the build script.
  2. Correct any errors.
  3. Run CBLD again.

See TPF Application Programming for more information about CBLD.

CBLD0805EIMPORTDS STATEMENT SHOULD PRECEDE OBJECT

Explanation: The C load module build tool (CBLD) detected that an @IMPORTDS statement was out of sequence in the build script. The @IMPORTDS statement must precede all included object file names in the dynamic load module (DLM), which is a DLL application, or in the dynamic link library (DLL).

System Action: The C load module build tool (CBLD) stops running and no job control language (JCL) is produced.

User Response: Move the @IMPORTDS statement to the correct position in the build script.

See TPF Application Programming for more information about the C load module build tool (CBLD).

CBLD1202Tline: LOAD MODULE NAME name NOT VALID

Where:

line
The input line containing the incorrect load module name.

name
The incorrect load module name found in the build script.

Explanation: An incorrect program name was found.

System Action: The C load module build tool (CBLD) stops running.

User Response: Correct the input line by updating the line with a valid 6-character program name (this includes the 2-character version code) or comment.

See TPF Application Programming for more information about CBLD.

CBLD1208TUNABLE TO DETERMINE LOAD MODULE TYPE

Explanation: The first non-comment line in the build script does not specify a valid C load module type (DLM, DLMvv, LIBRARY, or LIBRARYvv, where vv is the version code).

System Action: The C load module build tool stops running.

User Response: Do the following:

  1. Check the format of the build script.
  2. Correct any errors.
  3. Run the C load module build tool again.

CBLD1211TWRITE ERROR ON STDOUT

Explanation: An error occurred when attempting to write to STDOUT. Additional diagnostics may precede this message.

System Action: The C load module build tool stops running.

User Response: Determine why SYSOUT could not be written.

CBLD1222Tline: EITHER TYPE OR NAME NOT SPECIFIED

Where:

line
The input line containing the error.

Explanation: The first non-comment line in the build script does not specify the C load module name, or does not specify both the name and type (either DLM or LIBRARY).

System Action: The C load module build tool stops running.

User Response: Do the following:

  1. Check the format of the build script.
  2. Correct any errors.
  3. Run the C load module build tool again.

CCP001xxxx RESTART LEVEL LESS THAN SHUTDOWN LEVEL - DEFAULTS TAKEN

Where:

xxxx
The parameter for the CCPPOL macro.

Severity: 0

Explanation: The restart level for the parameter referenced in the message for the CCPPOL macro was specified as a smaller value than the shutdown level. Default values were assigned for both the shutdown and restart levels.

System Action: None.

User Response: If the assigned default values are not acceptable, do the following:

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

CHQI0001WADD STATEMENT BEGINNING IN LINE linenumber ENDS WITHOUT SPECIFYING LU

Where:

linenumber
The line number.

Explanation: An ADD statement was completed (by coding another verb or ending the input file) without specifying the LU parameter.

The ADD verb that begins the flagged statement is located at the line number referenced in the message.

System Action: The logical unit (LU) value is set to NULL.

User Response: Do one of the following:

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC). See the TPF C/C++ Language Support User's Guide for more information about mapped characteristics and TPF/APPC mapped conversation functions.

CHQI0002WADD STATEMENT BEGINNING IN LINE linenumber ENDS WITHOUT SPECIFYING MODE

Where:

linenumber
The line number.

Explanation: An ADD statement was completed (by coding another verb or ending the input file) without specifying the MODE parameter. The ADD verb that begins the flagged statement is located at the line number referenced in the message.

System Action: The MODE value is set to NULL.

User Response: Do one of the following:

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC). See the TPF C/C++ Language Support User's Guide for more information about mapped characteristics and TPF/APPC mapped conversation functions.

CHQI0003WADD STATEMENT BEGINNING IN LINE linenumber ENDS WITHOUT SPECIFYING TP

Where:

linenumber
The line number.

Explanation: An ADD statement was completed (by coding another verb or ending the input file) without specifying the TP parameter. The ADD verb that begins the flagged statement is located at the line number referenced in the message.

System Action: The TP value is set to NULL.

User Response: Do one of the following:

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC). See the TPF C/C++ Language Support User's Guide for more information about mapped characteristics and TPF/APPC mapped conversation functions.

CHQI0004WLU PARAMETER IS IGNORED IN REMOVE STATEMENT

Explanation: An LU parameter is specified in a REMOVE statement.

System Action: The LU parameter is ignored.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0005WMODE PARAMETER IS IGNORED IN REMOVE STATEMENT

Explanation: A MODE parameter is specified in a REMOVE statement.

System Action: The MODE parameter is ignored.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0006WTP PARAMETER IS IGNORED IN REMOVE STATEMENT

Explanation: A TP parameter is specified in a REMOVE statement.

System Action: The TP parameter is ignored.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0007EADD STATEMENT BEGINNING IN LINE linenumber ENDS WITHOUT SPECIFYING NAME

Where:

linenumber
The line number.

Explanation: An ADD statement was completed (by coding another verb or ending the input file) without specifying the NAME parameter. The ADD verb that begins the flagged statement is located in in the line number referenced in the message.

System Action: None.

User Response: Code the NAME parameter on the ADD statement.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0008EINVALID ADD PARAMETER

Explanation: A keyword parameter other than LU, MODE, NAME, or TP is coded as part of an ADD statement.

System Action: None.

User Response: Recode the ADD statement with the correct parameters.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0009EINVALID LOAD PARAMETER

Explanation: A keyword parameter other than SS is coded as part of a LOAD statement.

System Action: None.

User Response: Recode the LOAD statement with only the SS parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0011EINVALID PARAMETER SYNTAX

Explanation: A dash (-) or an equal sign (=) is coded that does not immediately follow a keyword parameter. A dash or equal sign is used only to delimit a keyword parameter and its value.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Correct the syntax.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0012EINVALID REMOVE PARAMETER

Explanation: A keyword parameter other than LU, MODE, NAME, or TP is coded as part of a REMOVE statement.

System Action: None.

User Response: Recode the REMOVE statement with the NAME parameter. The LU, MODE, and TP parameters are not required and are ignored. Any other parameter results in this error.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0013EINVALID VERB

Explanation: A verb other than ADD, DESCR, LOAD, or REMOVE is coded.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0014ELOAD MUST BE THE FIRST STATEMENT

Explanation: A LOAD statement is coded after the first statement in the input file.

System Action: None.

User Response: Move the LOAD statement to the top of the input file. The only type of input allowed in front of a LOAD statement are comments and blank lines.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0015ELOAD STATEMENT BEGINNING IN LINE linenumber ENDS WITHOUT SPECIFYING SS

Where:

linenumber
The line number.

Explanation: A LOAD statement was completed (by coding another verb or ending the input file) without specifying the SS parameter. The LOAD verb that begins the flagged statement is located in the line number referenced in the message.

System Action: None.

User Response: Recode the LOAD statement with the SS parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0016ELU IS ALREADY DEFINED FOR THIS STATEMENT

Explanation: At least one LU parameter was defined previously within the current ADD statement.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Remove the extraneous LU parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0017ELU NAME CONTAINS INVALID CHARACTER

Explanation: The logical unit (LU) name portion of an LU parameter value contains a character that is not an uppercase letter (A through Z) or a numeral (0 through 9).

System Action: None.

User Response: Recode the LU parameter value. Both the network ID (if any) and the logical unit (LU) name must be from 1 to 8 characters long, must contain only capital letters (A through Z) and numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0018ELU NAME IS LONGER THAN 8 CHARACTERS

Explanation: The logical unit (LU) name portion of an LU parameter value is more than 8 characters long.

System Action: None.

User Response: Recode the LU parameter value. Both the network ID (if any) and the logical unit (LU) name must be from 1 to 8 characters long, must contain only capital letters (A through Z) and numerals (O through 9), and must being with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0019ELU NAME MUST BEGIN WITH AN UPPERCASE LETTER

Explanation: The logical unit (LU) name portion of an LU parameter value begins with a character other than an uppercase letter (A through Z).

System Action: None.

User Response: Recode the LU parameter value. Both the network ID (if any) and the logical unit (LU) name must be from 1 to 8 characters long, must contain only capital letters (A through Z) and numerals (0 through 9) and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0020ELUNAME IS MISSING FROM NETID.LUNAME

Explanation: A value of the form netid is coded as an LU parameter value but there is no value for the LU name.

System Action: None.

User Response: Recode the LU parameter value. If the network ID is included, it must precede the LU name and be separated from it by a period.

If only the LU name is included, there should be no period. (For consistency with TPF commands, LU parameters specified as .luname, that is, no network ID but a leading period before the LU name, are accepted.).

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0021EMODE CONTAINS INVALID CHARACTER

Explanation: A MODE parameter value contains a character that is not an uppercase letter (A through Z) or a numeral (0 through 9).

System Action: None.

User Response: Recode the MODE parameter value. The value must be from 1 to 8 characters long, must contain only capital letters (A through Z), numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0022EMODE IS ALREADY DEFINED FOR THIS STATEMENT

Explanation: At least one MODE parameter was previously defined within the current ADD statement.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Remove the extraneous MODE parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0023EMODE IS LONGER THAN 8 CHARACTERS

Explanation: A MODE parameter value is more than eight characters long.

System Action: None.

User Response: Recode the MODE parameter value. The value must be from 1 to 8 characters long, must contain only capital letters (A through Z), numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0024EMODE MUST BEGIN WITH AN UPPERCASE LETTER

Explanation: A MODE parameter value begins with a character other than an uppercase letter (A through Z).

System Action: None.

User Response: Recode the MODE parameter value. The value must be from 1 to 8 characters long, must contain only capital letters (A through Z), numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0025ENAME IS ALREADY DEFINED FOR THIS STATEMENT

Explanation: At least one NAME parameter was defined previously within the current ADD or REMOVE statement.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Remove the extraneous NAME parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0026ENETWORK ID CONTAINS INVALID CHARACTER

Explanation: The network ID portion of an LU parameter value contains a character that is not an uppercase letter (A through Z) or a numeral (0 through 9).

System Action: None.

User Response: Recode the LU parameter value. Both the network ID (if any) and the logical unit (LU) name must be from 1 to 8 characters long, must contain only capital letters (A through Z), numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0027ENETWORK ID IS LONGER THAN 8 CHARACTERS

Explanation: The network ID portion of an LU parameter value is more than 8 characters long.

System Action: None.

User Response: Recode the LU parameter value. Both the network ID (if any) and the logical unit (LU) name must be from 1 to 8 characters long, must contain only capital letters (A through Z), numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0028ENETWORK ID MUST BEGIN WITH AN UPPERCASE LETTER

Explanation: The network ID portion of an LU parameter value begins with a character other than an uppercase letter (A through Z).

System Action: None.

User Response: Recode the LU parameter value. Both the network ID (if any) and the logical name (LU) name must be from 1 to 8 characters long, must contain only capital letters (A through Z), numerals (0 through 9), and must begin with a capital letter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0029ENO VALUE WAS SPECIFIED FOR PARAMETER KEYWORD

Explanation: No value follows a parameter keyword before the next logical end of record.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Correct the syntax. Each parameter must be completed in the same record that it begins. That is, a keyword and its associated value must be on the same line.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0030ENO VERB WAS SPECIFIED FOR THIS PARAMETER

Explanation: A keyword parameter is coded without a preceding verb; for example, at the beginning of the file, following a DESCR statement or following a verb that is not valid.

System Action: None.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0031EPARAMETER KEYWORD FOLLOWED BY PARAMETER KEYWORD

Explanation: A parameter keyword immediately follows another parameter keyword.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Correct the syntax. A parameter keyword must be followed by a dash or an equal sign and then followed by the appropriate parameter value.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0032EREMOVE STATEMENT BEGINNING IN LINE linenumber ENDS WITHOUT SPECIFYING NAME

Where:

linenumber
The line number.

Explanation: A REMOVE statement was completed (by coding another verb or ending the input file) without specifying the NAME parameter. The REMOVE verb that begins the flagged statement is located in the line number referenced in the message.

System Action: None.

User Response: Recode the REMOVE statement with the NAME parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0033ESS IS ALREADY DEFINED FOR THIS STATEMENT

Explanation: At least one SS parameter was defined previously within the current LOAD statement.

System Action: None.

User Response: Do the following:

  1. Check the statement.
  2. Remove the extraneous SS parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0034ESS NAME IS LONGER THAN 4 CHARACTERS

Explanation: An SS parameter value is more than four characters long.

System Action: None.

User Response: Recode the SS parameter. The value must be from one to four characters long.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0035ESYMBOLIC DESTINATION NAME IS LONGER THAN 8 CHARACTERS

Explanation: A NAME parameter value (that is, the symbolic destination name) is more than eight characters long.

System Action: None.

User Response: Recode the NAME parameter. The value must be from one to eight characters long.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0036ETP IS ALREADY DEFINED FOR THIS STATEMENT

Explanation: At least one TP parameter or concatenated set of TP parameters was defined previously within the current ADD statement. This message is issued when a parameter other than TP comes between two TP parameters. When there are no parameters interpolated among a set of TP parameters, the TP parameters are concatenated to form a single TP value in the generated side information entry.

System Action: None.

User Response: Recode the statement so that there are no parameters other than TP between the other TP parameters.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0037ETP NAME CONTAINS '$' NOT FOLLOWED BY SECOND '$' OR HEX DIGIT

Explanation: A TP parameter value contains a dollar sign that is interpreted as beginning a hexadecimal substring but that is followed by a character other than a hexadecimal digit (0 through 9, A through F) or a second dollar sign.

System Action: None.

User Response: Recode the TP parameter. The dollar sign is used to delimit substrings of TP parameter values that are to be interpreted as hexadecimal values, according to the following rules:

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0038ETP NAME CONTAINS AN EMBEDDED SPACE CHARACTER

Explanation: A hexadecimal substring containing the byte value X'40' (the EBCDIC space character) is included in a TP parameter value.

System Action: None.

User Response: Recode the TP parameter. See the user response for the CHQI0037E message for a list of the syntax rules for this parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0039ETP NAME CONTAINS HEX SUBSTRING WITH ODD NUMBER OF DIGITS

Explanation: A TP parameter value contains a hexadecimal substring (delimited by dollar signs) where the number of hexadecimal digit characters is not a multiple of two.

System Action: None.

User Response: Recode the TP parameter. See the user response for the CHQI0037E message for a list of the syntax rules for this parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0040ETP NAME CONTAINS INVALID CHARACTER IN HEX SUBSTRING

Explanation: A TP parameter value contains a hexadecimal substring (delimited by dollar signs) that includes a character other than a hexadecimal digit (0 through 9, A through F).

System Action: None.

User Response: Recode the TP parameter. See the user response for the CHQI0037E message for a list of the syntax rules for this parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0041ETP NAME ENDS WITH INCOMPLETE HEX SUBSTRING

Explanation: A TP parameter value ends with a hexadecimal substring that has no terminating dollar sign.

System Action: None.

User Response: Recode the TP parameter. See the user response for the CHQI0037E message for a list of the syntax rules for this parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0042ETP NAME IS LONGER THAN 64 BYTES

Explanation: The total length of all converted and concatenated TP parameter values making up a single transaction program name is greater than 64 bytes.

System Action: None.

User Response: Recode the TP parameter. See the user response for the CHQI0037E message for a list of the syntax rules for this parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0043EINPUT DATA SET OPEN FAILURE

Explanation: The user input data set could not be opened.

System Action: Summary information is written to the listing file and processing is ended immediately with return code 12.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0044EOUTPUT DATA SET OPEN FAILURE

Explanation: The SIDOUT output data set could not be opened.

System Action: Summary information is written to the listing file and processing is ended immediately with return code 16.

User Response: None.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0045ENAME MAY NOT CONTAIN LOWER CASE LETTERS

Explanation: The NAME parameter value contains one or more characters that are lowercase letters (a through z).

System Action: None.

User Response: Recode the NAME parameter.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CHQI0046ENO STATEMENTS IN INPUT FILE

Explanation: The input file is either empty or contains only blank lines and comments.

System Action: The output data set is empty.

User Response: Do the following:

  1. Create the input file again with valid entries.
  2. Run CHQI again.

See TPF ACF/SNA Data Communications Reference for more information about TPF Advanced Program-to-Program Communications (TPF/APPC).

CON004PROCESSOR SERIAL NUMBER (xxxx) WAS USED BY BOTH PROCy AND PROCz.

Where:

xxxx
The serial number of the processor.

y
The parameter in error.

z
The parameter in error.

Severity: 5

Explanation: Both PROCy and PROCz defined the same processor serial number, as referenced in the message. A loosely coupled environment requires that the concatenation of the serial and model number be unique.

System Action: None.

User Response: Do the following:

  1. Correct the duplicate identification number (the processor serial number).
  2. Rerun SIP stage I.

CON005AT LEAST ONE (PROCX=) MUST BE CODED.

Severity: 5

Explanation: When more than one ID is specified on the SYSID parameter, system initialization program (SIP) assumes that a loosely coupled environment exists. Loosely coupled environments required that at least one of the PROCx parameters is coded.

System Action: None.

User Response: Do one of the following:

Then, after making the appropriate changes, rerun SIP stage I.

CON006THE NUMBER OF SUBPARAMETERS SPECIFIED FOR PROCx EXCEEDS TEN.

Severity: 0

Explanation: Only the first 10 subparameters have meaning. The first subparameter is the processor serial number, the second subparameter is the model number, and the remaining subparameters are the SSA encodings. Any additional subparameters are extraneous and are ignored.

System Action: None.

User Response: Do one of the following:

CON007THE SERIAL NUMBER FOR PROCx IS NOT A HEXADECIMAL VALUE.

Severity: 5

Explanation: The serial number specified is not a hexadecimal value. Because this parameter must correspond to bits 12 through 31 of the results of a STIDP instruction, the value specified in the SIP stage I deck must be incorrect.

System Action: None.

User Response: Do the following:

  1. Recode the serial number with the proper hexadecimal value.
  2. Rerun SIP stage I.

CON008THE SERIAL NUMBER SPECIFIED FOR PROCx IS LONGER THAN 5 HEXADECIMAL DIGITS.

Where:

x
The parameter that is in error.

Severity: 5

Explanation: IBM processors use exactly six digits for the processor serial number. Since the TPF system forces the high-order digit to zero, only the remaining five need be coded.

System Action: None.

User Response: Do the following:

  1. Recode the serial number with no more than five digits.
  2. Rerun SIP stage I.

If fewer that five digits are coded, then the system initialization program (SIP) right justifies the serial number and writes zeros into the unused high-ordered digits.

CON009THE MODEL NUMBER SPECIFIED FOR PROCx DOES NOT CONTAIN FOUR CHARACTERS.

Where:

x
The parameter that is in error.

Severity: 5

Explanation: IBM hardware limits model numbers to four digits.

System Action: None.

User Response: Do the following:

  1. Recode the model number with exactly four characters.
  2. Rerun SIP stage I.

CON010PROCx DEFINED SSA y WHICH HAS ALREADY BEEN USED.

Severity: 5

Where:

x
The particular PROC parameter that is in error.

y
The duplicated SSA value.

Explanation: Each of the PROC parameters requires a unique set of SSA values.

System Action: None.

User Response: Do the following:

  1. Recode the PROCx parameter with a unique set of SSA values.
  2. Rerun SIP stage I.

CON011PROCx DEFINED y, WHICH IS OUTSIDE THE VALID SSA RANGE.

Where:

x
The particular PROC parameter that is in error.

y
The erroneous SSA value.

Severity: 5

Explanation: The SSA value corresponds to the hardware addresses on the TOD RPQ. The valid SSA values range from 0 to 7.

System Action: None.

User Response: Do the following:

  1. Recode the SSA value using a value from 0 to 7.
  2. Rerun SIP stage I.

COR001THE SUM OF APSIZ24 AND APSIZ31 MUST BE 1000 OR GREATER

Severity: 5

Explanation: The sum of the values coded for APSIZ24 and APSIZ31 is less than 1000.

System Action: None.

User Response: Do the following:

  1. Change the values coded for APSIZ24 or APSIZ31 so that their sum totals 1000 or more.
  2. Run SIP stage I again.

CRA001PRIME CRAS ADDRESS EQUALS xxxx CRAS ADDRESS

Where:

xxxx
The address of the prime computer room agent set (CRAS) console.

Severity: 5

Explanation: The addresses of the prime CRAS consoles referenced in the message cannot be the same as the address specified for the prime CRAS console.

System Action: None.

User Response:

  1. Correct one or both of the addresses.
  2. Rerun SIP stage I.

CRA002TERMINAL ADDRESS xxxx NOT VALID FOR yyyy

Where:

xxxx
The terminal address that is not valid for the device type.

yyyy
The device type.

Severity: 5

Explanation: The terminal address referenced in the message is not valid for the device type referenced in the message.

System Action: None.

User Response: Do the following:

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

CRA003NO CRASTB OPERANDS SPECIFIED

Severity: 5

Explanation: There are no default values. These operands must be specified.

System Action: None.

User Response: Do the following:

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

CRA0041977 SPECIFIED AS ROCRS DEVICE

Severity: 0

Explanation: The receive-only (RO) computer room agent set (CRAS) console is specified as a 1977, which is not a receive-only console.

System Action: None.

User Response: Do the following:

  1. Correct the operand if it is not valid.
  2. Rerun SIP stage I.

CRA005xxxx OPERAND IGNORED -VALID ONLY IF yyyy=NO

Where:

xxxx
The keyword that was ignored.

yyyy
The keyword that must be coded for xxxx to be valid.

Severity: 0

Explanation: The keyword referenced in the message is ignored because it is not valid. This keyword should only be coded when yyyy=NO is specified.

System Action: None.

User Response: Do one of the following: