This section details messages generated in the course of Batch Package processing, along with possible causes and corrective actions to take in error situations.
Reason:
An attempt was made to create a Package which already exists.
Action:
Choose a different Package ID or modify the Package specified.
Reason:
The named job is being submitted for the execution of one or more Packages.
Action:
No action is necessary.
Reason:
The data set containing the Package submission JOB card was either empty, could not be found or could not be opened.
Action:
Correct the jobcard DDNAME, DSNAME, or DSNAME/member on the "submit Package" statement.
Reason:
A Package request editor/executor received a request (create, modify, cast, execute, etc.) to operate on the Package. More messages follow.
Action:
No action required.
Reason:
A Package request (create, modify, cast, execute, etc.) completed successfully.
Action:
No action required.
Reason:
A Package request (create, modify, cast, execute, etc.) completed with a non-zero return code.
Action:
Check previous messages and the JES log for the reason for the failure.
Reason:
An "export" or "archive" action specified a data set name and member name. The member already exists and "replace" was not specified.
Action:
Specify "replace" or choose a member name which does not exist.
Reason:
The Package was marked non-sharable and the user requesting access to the Package is not the owner. Non-sharable was not overridden in the corresponding Package exit.
Action:
The creator of this Package must change it to sharable if others are to be allowed to modify it.
Reason:
Archive data sets must be RECFM=V or VB and have a minimum LRECL of 4096. The data set specified has an LRECL which is less than the minimum.
Action:
Choose or allocate a data set with the minimum LRECL and the correct RECFM.
Reason:
Archive data sets must be RECFM=V or VB and have a minimum LRECL of 4096. The data set specified has an invalid RECFM.
Action:
Choose or allocate a data set with a RECFM of V or VB.
Reason:
The C1DEFLTS that was loaded cannot be used for Package processing because PKGDSN was not coded.
Action:
Assemble the C1DEFLTS table with PKGDSN coded and link it into a library where it will be the one loaded.
Reason:
An attempt was made to Create_TFC or Create_TDF and it didn’t work. Possible storage error (format 1), old version of ENMC$TFO (format 2), or none zero return code (format 3).
Action:
If a storage error and the result is "NOSTG", increase the region size. If any of the other formats occur, check the data sets making up CONLIB and make sure that the concatenation doesn’t contain more than one release of CA Endevor SCM.
Reason:
The current status of the Package (in-edit, approved, in-approval, executed, etc.) makes it ineligible for the specified function (casting, execution, etc.).
Action:
For more information about Packages, see the Packages Guide.
Reason:
The Package has an illegal character in its name. Valid characters are A-Z (capitals only), 0- 9, $, @, #, and embedded spaces. Leading spaces are invalid.
Action:
Examine the Package ID and make the appropriate corrections.
Reason:
The data set or member was not found. The type can be "Import", "Export", or "Archive."
Action:
Correct the DDNAME, DSNAME, or DSNAME/member name on the Package SCL statement. If DDNAME was used, be sure that there is a DD card bearing that name in the JCL.
Reason:
A request to define (create or modify) a Package specified another Package ID which contains the SCL. The latter Package was not found.
Action:
Correct the COPY FROM Package ID.
Reason:
A Package was created or modified resulting in a Package without any SCL statements.
Action:
None. The Package has been created and can be updated later with the required SCL statements.
Reason:
A request to export PKG SCL was made, but the Package contained no SCL statements.
Action:
Ensure that the correct Package ID was specified. The target data set of the EXPORT has not been modified.
Reason:
An error was encountered in attempting to allocate the Package work data set or the Package report data set. The message contains the dynamic allocation return code.
Action:
See the appropriate IBM documentation to interpret the return code.
Reason:
An attempt was made to create a Package but no SCL was provided via the import or copy process.
Action:
Make sure that the import data set or COPY FROM Package is not empty.
Reason:
A Package INSPECT function was executed against a Package whose execution window has passed. The Package can no longer be executed.
Action:
None.
Reason:
Informational message. This message is generated by the PACKAGE INSPECT action. Packages that are In-approval, Approved, In-execution, or Exec-failed can be selected for the INSPECT action. This message is followed by message ENMP300W if the execution window is closed.
Action:
None.
Reason:
Warning message generated by the PACKAGE CAST/INSPECT actions. The date and time of the CAST/INSPECT actions does not fall within the specified execution window for the Package. The execution window is printed in the preceding ENMP300I message. Although the rest of the CAST/INSPECT actions may successfully complete, the Package will not execute unless the date and time fall within the execution window.
Action:
None.
Reason:
Informational message. This message is generated by the Package inspect action. The SCL associated with the Package was successfully extracted from the Package file. Parsing of the SCL follows this message.
Action:
None.
Reason:
Informational message. This message is generated by the Package inspect action. The Element and member validation part of the inspect action has been started. This message can be followed by error messages associated with security violations, signout conflicts, and/or source changes.
Action:
None.
Reason:
Informational message. This message is generated by the Package inspect action. The Element and member validation part of the inspect action has been successfully completed.
Action:
None.
Reason:
Informational message. This message is generated by the Package inspect action. The Element and member validation part of the inspect action has been completed. Non-zero return codes have been detected.
Action:
Check for other error messages accompanying this message.
Reason:
Informational message. This message indicates that a validation of a PKG action, whose statement number is xxxxx, issued a message. This message is always followed by ENMP306I.
Action:
None.
Reason:
This message indicates a validation (SRC-ELM, TGT-ELM, COMMENT, CCID, EXIT-2, SYNC, JUMP, or SIGNOUT) resulted in (NO, WARNING, CAUTION, or ERROR) messages. Another message is issued with the error reason.
Action:
None.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|