This section details messages generated in the course of Batch Package Facility processing, along with possible causes and corrective actions to take in error situations.
Reason:
A fully specified Package ID was provided on the Batch Package Facility request but the Package ID was not defined or is not available. It is possible that the Package exists but the LIST BEFORE or AFTER exit has suppressed presenting the Package. It is also possible that the ID associated with the batch job is not an approver or that the Package is not sharable.
Action:
Verify that the correct Package ID was specified on the request. If the correct Package ID was specified, verify that you are authorized to access the Package. If you did not create the Package, the Package must be defined as a sharable Package. If the Package has one or more approver groups associated with it, you must be a member of one of the approver groups. If you are authorized to access the Package, contact your administrator to determine if the LIST BEFORE or AFTER exits are suppressing the Package.
Reason:
A fully specified DELETE PACKAGE action was provided on the Batch Package Facility request but the Package ID was not defined or is not available. It is possible that the Package exists but the LIST BEFORE or AFTER exit has suppressed presenting the Package. It is also possible that the ID associated with the batch job is not an approver or that the Package is not sharable.
Action:
Verify that the correct DELETE PACKAGE action was specified on the request. If the correct DELETE PACKAGE action was specified, verify that you are authorized to access the Package. If you did not create the Package, the Package must be defined as a sharable Package. If the Package has one or more approver groups associated with it, you must be a member of one of the approver groups. If you are authorized to access the Package, contact your administrator to determine if the LIST BEFORE or AFTER exits are suppressing the Package.
Reason:
A partially or fully wildcarded Package ID was specified on the Batch Package Facility request but there were not Packages that matched the mask specified. It is possible that one or more Packages exist but that the LIST BEFORE or AFTER exit suppressed presenting the Package. It is also possible that the ID associated with the batch job is not an approver or that the Package is non sharable. If the WHERE OLDER THAN clause was specified, it is possible that there are no Packages older than the number of days specified. If the WHERE PACKAGE STATUS clause was specified, it is possible that there are no Packages in the specified state.
Action:
Verify that the correct Package ID was specified on the request. If the correct Package ID was specified, verify that you are authorized to access the Packages that may match the wildcard. If you did not create the Packages, the Packages must be defined as a sharable Package. If the Packages have one or more approver groups associated with it, you must be a member of one of the approver groups. If you are authorized to access the Packages, contact your administrator to determine if the LIST BEFORE or AFTER exits are suppressing the Packages.
Reason:
The Batch Package Facility initialization routine encountered one or more errors. One or more error messages should precede message ENBP003E. The Batch Package Facility will terminate with a return code of 12.
Action:
Perform the corrective action associated with the error message that preceded message ENBP003E.
Reason:
The ENPSCLIN DD statement was not allocated to the session. The ENPSCLIN DD statement defines the Batch Package Facility control statements.
Action:
Add a valid ENPSCLIN DD statement to the execution JCL and resubmit the JCL.
Reason:
The data set that the ENPSCLIN DD statement refers to has the incorrect attributes. The data set must be either sequential or partitioned (with a member specification), it must contain either fixed or variable length records and the record length must be exactly 80 for RECFM=F and at least 84 for RECFM=V.
Action:
Add a valid ENPSCLIN DD statement to the execution JCL or reallocate the data set that was specified with the correct attributes. Resubmit the JCL.
Reason:
The ENPSCLIN data set did not contain any valid action SCL statements. Either the data set was empty or the data set contained syntactically invalid statements. Package action processing will terminate.
Action:
Change the ENPSCLIN DD statement to refer to a data set that contains valid Batch Package facility control statements. Resubmit the job.
Reason:
The Batch Package Facility initialization routine was unable to dynamically load the named program. The initialization routine will fail and the program will terminate.
Action:
Verify that the execution JCL contains the appropriate data sets in the CONLIB DD statement. Check the JES System log for the job for any System messages that may indicate a System error and, if any are present, take the corrective action for those errors. If the problem persists, contact CA Technical Support.
Reason:
The Package ID returned by the GENPKGID exit already exists in the Package file. The Package name returned by the GENPKGID exit must be unique.
Action:
Either specify a fully qualified Package ID or resubmit the request to redrive the GENPKGID exit. If the problem persists, contact the administrator to determine why the installation GENPKGID exit is generating a duplicate Package ID.
Reason:
The Batch Packages Facility program has completed execution. The program will terminate with the return code specified.
Action:
No action is necessary.
Reason:
This message appears in the Action Execution report to identify the current action number that is being processed. The statement number refers to the corresponding action in the Control Statement Summary report.
Action:
No action is necessary.
Reason:
The Batch Package Facility is passing control to the Package Application Interface to perform the action specified.
Action:
No action is necessary.
Reason:
The user is not authorized to access the Batch Package Facility.
Action:
Contact CA Technical Support to obtain the necessary authorization to execute the Batch Package Facility.
Reason:
The specified data set could not be dynamically allocated. The s99error and s99info fields identify the Dynamic Allocation error and information codes that were returned with the request.
Action:
See the IBM publication GC28-1852 Systems Programming Library: Application Development Guide (or the equivalent manual for your release of x/OS90) for the definition of the error and information codes. Correct the condition and resubmit the request. If the error persists, it may be necessary to contact your System administrator or CA Technical Support.
Reason:
The action identified has been successfully performed against the Package named. If the return code is greater than zero, one or more messages should precede message ENBP023I to indicate the reason for the non-zero return code.
Action:
No action is necessary.
Reason:
The DEFINE action has determined that a new Package is to be created but the DESCRIPTION clause was not specified on the DEFINE action. The DESCRIPTION clause is required when a new Package is being created.
Action:
Add the DESCRIPTION clause to the request and resubmit the request.
Reason:
The DEFINE PACKAGE control statements did not include an IMPORT SCL FROM, COPY PACKAGE, DESCRIPTION, or any OPTIONS clauses. The Package will not be updated because there is no information to be added to the Package.
Action:
Add the DESCRIPTION, IMPORT SCL FROM, or COPY PACKAGE FROM clause or one or more of the OPTION clauses to the request and resubmit the request.
Reason:
The data set specified on the DEFINE PACKAGE IMPORT SCL FROM DSNAME clause or the SUBMIT PACKAGES JOBCARD DSNAME clauses could not be located in the System catalogue.
Action:
Verify that the correct data set name was specified in the request and verify that the data set is catalogued. If the incorrect data set name was specified, correct and resubmit the request.
Reason:
The member name specified on the DEFINE PACKAGE IMPORT SCL FROM DSNAME MEMBER clause or the SUBMIT PACKAGE JOBCARD DSNAME MEMBER clause could not be found in the data set specified.
Action:
Change the MEMBER clause to refer to a member that exists in the data set or create the member in the data set. Resubmit the request.
Reason:
The DD statement specified on the DEFINE PACKAGE IMPORT SCL FROM DDNAME clause, the SUBMIT PACKAGE JOBCARD DDNAME clause, or the SUBMIT PACKAGE INTERNAL READER DDNAME clause is not allocated to the Batch Package Facility session.
Action:
Add the specified DD statement to the execution JCL. Resubmit the request.
Reason:
The Package specified on the DEFINE PACKAGE action COPY PACKAGE FROM clause could not be found.
Action:
Verify that the correct Package ID was specified on the COPY PACKAGE FROM clause. If the Package ID does not exist, change the clause to refer to a Package that does exist. Resubmit the request.
Reason:
The DEFINE Package action will create a new Package but SCL for the Package was not provided. In order to create a new Package, the IMPORT SCL FROM or COPY PACKAGE FROM clause must be specified. These clauses define the location of the Package SCL.
Action:
Specify the location of the SCL to be added to the Package by specifying either an IMPORT SCL FROM or a COPY PACKAGE FROM clause to the DEFINE action. Resubmit the request.
Reason:
The data set identified has invalid attributes for the Package action requested.
Action:
For the action to determine the appropriate characteristics for the data set that is invalid, see the SCL Reference Guide. Either refer to a data set with the correct attributes or reallocate the specified data set with the correct attributes. Resubmit the request.
Reason:
The INTERNAL READER DD statement does not have the correct attributes. The DD statement must specify a sequential data set that has fixed length, 80 byte records.
Action:
Verify that the data set that the INTERNAL READER DD statement refers is a sequential data set with fixed length records and a record length of 80. If the DD statement refers to a SYSOUT data set, it may be necessary to add the DCB=(LRECL=80,RECFM=F,BLKSIZE=80) statement to the DD statement. Resubmit the request.
Reason:
The request contained a wildcarded Package name. The wildcard expansion routine found at least one Package ID that matched the wildcarded Package ID that was specified. The Package or Packages were not selected for one or more of the following reasons:
Action:
If the action request contained an OPTIONS WHERE clause, change the clause to broaden the selection criteria. For example, change the WHERE OLDER THAN clause to a smaller value to enlarge the number of possible Packages selected. If the Package has one or more Approver Groups, verify that you are a member of one of the Approver Groups. Contact your administrator to be placed in the appropriate Approver Group, if necessary. If the Package is non-sharable, contact the owner of the Package and have the owner perform the desired action.
Reason:
The Package state associated with the Package identified contains an undefined value.
Action:
Use the ISPF dialog to verify the status of the Package. If the Package has a valid status, resubmit the request. If the Package status is invalid, contact your administrator.
Reason:
The indicated Package ID is not available for the indicated action.
Action:
Verify the Package ID and resubmit the action request.
Reason:
The member name specified on the EXPORT SCL TO DSNAME MEMBER clause already exists in the data set specified and the REPLACE clause was not specified. The REPLACE clause is required in order to overwrite an existing member.
Action:
Either specify the name of a member that does not exist or add the REPLACE keyword to the MEMBER clause. Resubmit the request.
Reason:
The TO DSNAME MEMBER clause was specified for a sequential data set. The action will ignore the MEMBER name specified.
Action:
No action is necessary.
Reason:
The IMPORT SCL FROM DSNAME MEMBER clause was specified for a sequential data set. The action will ignore the MEMBER name specified.
Action:
No action is necessary. To eliminate the message, either remove the MEMBER clause or specify a partitioned data set that contains the member specified in the MEMBER clause.
Reason:
The data set specified on the DEFINE action IMPORT SCL FROM DSNAME clause is a partitioned data set and the MEMBER clause was not specified. A member clause is required in order to identify the member to be used by the DEFINE action.
Action:
Either add a MEMBER clause to the IMPORT SCL FROM DSNAME clause or change the data set name specified on the IMPORT SCL FROM DSNAME clause to a sequential data set. Resubmit the request.
Reason:
The request specified the EXECUTION WINDOW FROM value but did not specify an EXECUTION WINDOW TO value. The EXECUTION WINDOW FROM value specified on the request is later than the EXECUTION WINDOW TO value that is already associated with an existing Package.
Action:
Either change the EXECUTION WINDOW FROM value to a date and time that is earlier than the existing EXECUTION WINDOW TO value or add an EXECUTION WINDOW TO clause to the request. Resubmit the request.
Reason:
The EXECUTE PACKAGE request specified the EXECUTION WINDOW clause but the EXECUTION WINDOW that is associated with the Package is still open; that is, the current date and time falls within the EXECUTION WINDOW FROM and TO time range. The EXECUTE PACKAGE action can only change the Execution Window if the Window is closed.
Action:
Either remove the EXECUTION WINDOW clause from the request or wait for the existing Execution Window to close. Resubmit the request.
Reason:
An unrecoverable ABEND occurred during Batch Package Facility execution. One or more messages should precede message ENBP081E to indicate the error that occurred. The Batch Package Facility will immediately terminate.
Action:
Resubmit the request. If the problem persists, contact CA Technical Support.
Reason:
The BACKOUT PACKAGE action cannot process the Package because the Package was not defined with the BACKOUT ENABLED option.
Action:
Verify that the correct Package ID was specified on the BACKIN PACKAGE request.
Reason:
The BACKIN PACKAGE action cannot process the Package specified because the Package has not been backed-out.
Action:
Verify that the correct Package ID has been specified on the BACKIN PACKAGE action.
Reason:
The specified function was unable to obtain the specified amount of storage. Processing will terminate with a return code of 16.
Action:
Increase the REGION= parameter on the JOB or EXEC JCL statement and resubmit the request. If the problem persists, reduce the number of actions that are specified by the ENPSCLIN DD statement.
Reason:
An internal logic error occurred in the function identified. The error text may provide an indication of the error.
Action:
Contact CA Technical Support.
Reason:
The specified function was unable to build a TDF. The Build TDF routine returned a NULL pointer. The field code value identifies the field code of the TDF to be built.
Action:
Contact CA Technical Support.
Reason:
The specified function was unable to build a TDF. The Build TDF routine returned a NULL pointer. The field code value identifies the field code of the TDF to be built.
Action:
Contact CA Technical Support.
Reason:
The specified function was unable to build a TDF. The Build TDF routine returned a NULL pointer. The field code value identifies the field code of the TDF to be built.
Action:
Contact CA Technical Support.
Reason:
A call to the Package Interface routine returned a non-zero return code or interface return code. The Error Text contains a formatted interpretation of the return code from the Package Application Interface.
Action:
Contact CA Technical Support.
Reason:
A call to the Package Interface routine returned a non-zero return code or interface return code. The Error Text contains a formatted interpretation of the return code from the Package Application Interface.
Action:
Contact CA Technical Support.
Reason:
A call to the Package Interface routine returned a non-zero return code or interface return code. The message contains the interface return and reason codes and the function return code. This message is issued if the return code and reason code cannot be converted into a message string.
Action:
Contact CA Technical Support.
Reason:
An internal error occurred while allocating a new I/O Object.
Action:
Contact CA Technical Support.
Reason:
The Batch Package Facility ABENDed with the code identified. The current action will terminate processing immediately and any remaining, unexecuted actions will not be executed.
Action:
Resubmit the request. If the problem persists, contact CA Technical Support. Before calling Technical Support, however, add the following card to the execution JCL and resubmit the request:
a //SYSABEND DD SYSOUT=_
This JCL statement will create a diagnostic dump when the ABEND occurs.
Reason:
The Batch Package Facility is beginning to parse the user supplied control statements.
Action:
No action is necessary.
Reason:
The Batch Package Facility has completed parsing the control statements and no errors were detected.
Action:
No action is necessary.
Reason:
The Batch Package Facility has completed parsing the control statements. One or more errors were detected in the control statements. None of the control statements will be executed.
Action:
Correct the errors identified by the parsing and validation routine and resubmit the JCL.
Reason:
The Package ID specified on the DEFINE, APPROVE, DENY, BACKOUT, BACKIN, RESE, or EXPORT action contained a wildcard character. These actions do not support wildcarded Package IDs.
Action:
Change the Package ID that was specified on the action so that it does not contain a wildcard character. Resubmit the JCL.
Reason:
The user set the Package Execution window with the same FROM/TO Date and Time.
Action:
Ensure that the Package Execution Window is at least one minute.
Reason:
The COMMIT or DELETE action specified a wildcarded Package ID but the WHERE OLDER THAN clause was not specified. The WHERE OLDER THAN clause is required when a wildcarded Package ID is specified.
Action:
Either add the appropriate WHERE OLDER clause to the request or specify a fully qualified Package ID. Resubmit the request.
Reason:
The date or time value specified on the EXECUTE WINDOW clause is syntactically invalid. The date value must be specified in the format DDMMMYY and the time value must be specified in the format HH:MM. For example, January 1, 1993 would be specified as 01JAN93 and 1:30 PM would be specified as 13:30.
Action:
Correct the EXECUTION WINDOW date or time value and resubmit the request.
Reason:
The EXECUTION WINDOW FROM date specified is greater than the TO date specified or the default EXECUTION WINDOW TO date.
Action:
Correct the EXECUTION WINDOW clause so that the FROM date and time is earlier than the TO date and time.
Reason:
The EXECUTION WINDOW TO date or time specified is earlier than the current System date and time. The EXECUTION WINDOW TO value must be later than the date and time that the action is being executed.
Action:
Correct the EXECUTION WINDOW TO clause so that the date and/or time specified is later than the current date and time. Resubmit the request.
Reason:
The EXPORT PACKAGE action specified both a TO DDNAME and a TO DSNAME clause. The clauses are mutually exclusive. Only one of the clauses can be specified.
Action:
Remove either the TO DDNAME or the TO DSNAME clause from the EXPORT PACKAGE action. Resubmit the JCL.
Reason:
The EXPORT PACKAGE action did not specify either a TO DDNAME or a TO DSNAME clause. One of the two clauses is required.
Action:
Add either the TO DDNAME or the TO DSNAME clause to the EXPORT PACKAGE action. If the TO DDNAME is added, also add the DD Name to the execution JCL. Resubmit the JCL.
Reason:
The COMMIT PACKAGE or DELETE PACKAGE action contained a fully specified Package ID and the WHERE OLDER THAN clause was also specified. The WHERE OLDER THAN clause is ignored when a fully specified Package ID is provided.
Action:
No action is necessary. To eliminate this message, remove the WHERE OLDER THAN clause from the COMMIT or DELETE PACKAGE action statement.
Reason:
The DEFINE PACKAGE action contained a COPY PACKAGE FROM clause but the Package ID specified was wildcarded. The Package ID must be fully specified.
Action:
Specify a fully qualified Package ID on the COPY PACKAGE FROM clause. Resubmit the request.
Reason:
The execution JCL contained the PARM=VALIDATE statement. The program will only syntax check the control statements. The control statements will not be executed.
Action:
No action is necessary. In order to execute the Batch Package Facility control statements, remove the VALIDATE parameter from the execution JCL.
Reason:
The execution JCL contained an unidentifiable parameter on the PARM statement. The program will terminate with a return code of 12.
Action:
See message ENBP926E for the invalid JCL PARM parameter. Correct the parameter and resubmit the request.
Reason:
The DEFINE action request contained both a FROM DDNAME and a FROM DSNAME clause. Only one of the clauses can be specified for a specific request.
Action:
Remove one of the two clauses from the request and resubmit the request.
Reason:
The value specified on the WHERE OLDER THAN clause was either less than one or greater than 999.
Action:
Specify a value between 1 and 999, inclusive, for the WHERE OLDER THAN clause. Resubmit the request.
Reason:
The SUBMIT PACKAGE clause specified both the JOBCARD DDNAME and the JOBCARD DSNAME clauses. Only one of the clauses can be specified.
Action:
Remove one of the two clauses from the request and resubmit the request.
Reason:
The DEFINE PACKAGE clause specified both the STANDARD PACKAGE and the EMERGENCY PACKAGE clauses. Only one of the clauses can be specified.
Action:
Remove one of the two clauses from the request and resubmit the request.
Reason:
The DEFINE PACKAGE clause specified both the SHARABLE PACKAGE and the NONSHARABLE PACKAGE clauses. Only one of the clauses can be specified.
Action:
Remove one of the two clauses from the request and resubmit the request.
Reason:
The EXECUTION WINDOW clause can only be specified with a fully qualified Package ID. The request contained a fully or partially wildcarded Package ID.
Action:
Either remove the EXECUTION WINDOW clause from the request or use a fully specified Package ID on the request. Resubmit the request.
Reason:
The DEFINE PACKAGE statement specified a blank Package name but the installation GENPKGID exit did not provide a replacement Package ID.
Action:
If the GENPKGID exit is not being used then supply a non-blank Package ID on the DEFINE PACKAGE action. If the GENPKGID exit is being used, contact CA Technical Support to determine why the exit did not provide a Package ID.
Reason:
The action specified a blank Package name. Only the DEFINE action supports a blank Package name.
Action:
Specify a valid, non blank Package ID on the request. Resubmit the request.
Reason:
This message identifies the current statement number of the SCL statement that is being parsed.
Action:
No action is necessary.
Reason:
The Package ID specified on the DEFINE PACKAGE action was blank and the call to the installation GENPKGID exit failed. For any error messages that the GENPKGID exit may have generated, see the SCL Reference Guide.
Action:
Determine why the installation GENPKGID exit failed and correct the situation. Resubmit the request.
Reason:
The GENPKGID exit passed back a return code that could not be handled by the Batch Package Facility.
Action:
Contact CA Technical Support to determine why the GENPKGID passed a non-standard return code. Resubmit the request after the situation has been corrected.
Reason:
This message is issued immediately after message ENBP914E. It identifies the invalid parameter that was passed to the Batch Package Facility.
Action:
See message ENBP914E.
Reason:
The OPTIONS NOTES clause contained more NOTE text lines than are currently supported. The maximum number of NOTE text lines that can be specified are eight (8).
Action:
Correct the DEFINE, CAST, APPROVE or DENY PACKAGE action so that at most eight (8) NOTE text lines are specified. Resubmit the request.
Reason:
The WHERE PACKAGE STATUS clause is valid only when the Package ID is wildcarded. It is ignored for fully qualified Package IDs.
Action:
No action is necessary. To eliminate the message, remove the WHERE PACKAGE STATUS clause from the request.
Reason:
The action specified a wildcarded Package ID but did not specify a WHERE PACKAGE STATUS clause.
Action:
Either add the WHERE PACKAGE STATUS clause to the request or provide a fully specified Package ID on the request. Resubmit the request.
Reason:
The CAST PACKAGE VALIDATE COMPONENTS clause is invalid if the C1DEFLTS table indicates that Component validation is mandatory (PKGCVAL=Y).
Action:
Remove the VALIDATE COMPONENTS clause from the CAST request and resubmit the request.
Reason:
The DEFINE PACKAGE action cannot specify both the COPY FROM PACKAGE and the IMPORT SCL FROM clauses. These two clauses are mutually exclusive.
Action:
Remove one of the two clauses from the DEFINE PACKAGE action. Resubmit the request.
Reason:
The final control statement did not contain a terminating period. All Batch Package Facility control statements must be terminated with a period.
Action:
Add a terminating period to the final control statement. Resubmit the request.
Reason:
The Package ID specified on the Package action or the COPY PACKAGE FROM clause contained one or more invalid characters. Only alphanumeric, blanks, and the national characters # and $ are allowed in a Package ID.
Action:
Correct the invalid Package ID. Resubmit the request.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|