SHP Messages

The SHP messages result from API Package Ship processing. The following list of CA Endevor SCM SHP messages includes possible causes and corrective actions to take in error situations.

SHP0001S

UNABLE TO ALLOCATE THE TEMPORARY JCL FILE

Reason:

CA Endevor SCM is unable to allocate a temporary JCL file required to build the JCL to execute the PROC statement.

Action:

View the job log for additional clues.

SHP0002E

UNABLE TO READ THE APIHJC JOBCARD FILE

Reason:

CA Endevor SCM is unable to read the skeleton host jobcard.

Action:

Verify that the APIHJC DD statement points to the jobcard file and that this sequential file exists.

SHP0003E

ERROR DETECTED WRITING TO THE TEMPORARY JCL FILE

Reason:

CA Endevor SCM is unable to write to the temporary JCL file it is building containing the JOBCARD, EXEC PROC statement and SCL statement.

Action:

Contact your administrator.

SHP0004E

UNSUPPORTED SCL STATEMENT

Reason:

A keyword was found at the beginning of a statement that is not the keyword SHIP, EOF, EOJ, or a comment.

Action:

Correct the SCL statement.

SHP0005E

SHIP STATEMENT NOT FOUND

Reason:

CA Endevor SCM parsed the SCL statements and did not locate the SHIP statement.

Action:

Ensure that the SHIP statement is included in the SCL.

SHP0006E

UNABLE TO LOCATE THE "TO" KEYWORD IN THE SHIP STATEMENT

Reason:

CA Endevor SCM is unable to locate the “TO“ keyword on the SHIP statement.

Action:

Ensure that the TO keyword is included in the SHIP statement.

SHP0007E

UNABLE TO LOCATE THE "DESTINATION" KEYWORD ON THE SHIP STATEMENT

Reason:

CA Endevor SCM is unable to locate the “DESTINATION“ keyword on the SHIP statement following the TO keyword.

Action:

Ensure that the DESTINATION keyword is included in the SHIP statement after the TO keyword.

SHP0008E

UNABLE TO LOCATE THE DESTINATION ID VALUE ON THE SHIP STATEMENT

Reason:

CA Endevor SCM is unable to locate the destination ID on the SHIP statement following the destination keyword.

Action:

Ensure that the destination ID is included in the SHIP statement following the destination keyword.

SHP0009E

THE @20CY VALUE MUST BE S-BDT1, B-BDT2, M-CONN, L-LOCL, F-NVFT OR X-XCOM. @1CY IS INVLD

Reason:

The six transmission methods supported by the API ship facility are S (BDT1), B (BDT2), M (CONN), L (LOCL), F (NVFT) and X (XCOM). The transmission method is determined by the destination ID specified on the SHIP statement.

Action:

Ensure that a valid transmission method is associated with the specified destination ID.

SHP0010E

ONLY 1 SHIP STATEMENT IS ALLOWED PER REQUEST. MULTIPLE SHIP STATEMENTS WERE DETECTED

Reason:

More than one SHIP statements were found within the SCL. Only one SHIP statement is allowed per request.

Action:

Ensure that the SCL statement includes only one SHIP statement.

SHIP011E

UNABLE TO OBTAIN AND CONVERT THE CURRENT DATE AND TIME

Reason:

The current date and time are obtained from the operating system and converted into a display format. This is an internal error.

Action:

Contact your administrator.