This section describes the messages generated in the course of Expand Includes Utility processing, along with possible causes and corrective actions to take in error situations.
Batch expand include syntax.
Action:
None.
Reason:
This message indicates the termination of the utility.
Action:
None.
Reason:
An invalid execution parameter was specified. The parameter in error printed out after this message.
Action:
Correct the error and resubmit.
Reason:
See message ENBX003E.
Action:
Correct the error and resubmit.
Reason:
The member name specification via ENXSCLIN overrides the JCL member name execution parameter specification.
Action:
None.
Reason:
A member name must be specified either via ENXSCLIN syntax or via the JCL execution parameter.
Action:
Specify the member name and resubmit.
Reason:
An initialization error occurred.
Action:
See associated error messages.
Reason:
A processing error occurred during syntax validation.
Action:
See associated error messages.
Reason:
Neither CA Panvalet nor CA Librarian include statement syntax was specified in the C1DEFLTS table.
Action:
Update the C1DEFLTS with the appropriate specification.
Reason:
There are no DD statements beginning with ENXINCnn found allocated to include libraries.
Action:
Correct the JCL and resubmit.
Reason:
The library identified in the message does not have DCB information consistent for include members.
Action:
Verify that the data set name identified is correct.
Reason:
The data set name identified in the message cannot be found in the catalog.
Action:
Make sure that the data set name in the specification is correct.
Reason:
The ddname specified in the message was found to be allocated.
Action:
Correct the JCL and resubmit.
Reason:
See message ENBX011E.
Reason:
The LRECL of the target data set is smaller than the source data set.
Action:
Check the LRECL specification to make sure it is correct.
Reason:
A dynamic allocation error occurred for the named data set. See IBM Publication Application Development Guide Authorized Assembler Language Programs for a definition of the return and reason codes.
Action:
Refer to the action.
Reason:
The source/destination data set, dsname, has invalid data set attributes.
Action:
Verify that you have specified the correct source and destination data sets.
Reason:
The data set pointed to by the ENXIN DD statement is a library but no member names were specified.
Action:
Specify a member name and resubmit.
Reason:
Validation failed for DD ddname, data set dsname.
Action:
Verify that the specified dsname is correct.
Reason:
See message ENBX025E.
Action:
Verify that you have specified the correct source and destination data sets.
Reason:
The specified member name is not found in the specified library name.
Action:
Correct the member name and resubmit.
Reason:
The indicated member has been selected and expanded.
Action:
None.
Reason:
This message indicates the name of the input data set.
Action:
None.
Reason:
This message indicates the name of the output data set.
Action:
None.
Reason:
This message indicates the number of members that were successfully expanded and the number of members that had an error.
Action:
None.
Reason:
The indicated member already exists in the named data set.
Action:
Check the specification of the member and resubmit.
Reason:
The indicated member already exists in the named data set.
Action:
Check the specification of the member and resubmit.
Reason:
EXPAND INCLUDE processing completed with the indicated return code.
Action:
None.
Reason:
This message indicates that sequential input has been processed resulting in the number of include members with the number of lines expanded.
Action:
None.
Reason:
This message indicates that the destination data set does not include an output member name.
Action:
Specify an output member name and resubmit.
Reason:
This message indicates that no matches were found for the member in the data set named.
Action:
Verify that the data set name is correct.
Reason:
The indicated member was not found in the named data set.
Action:
Verify the member name and the data set name.
Reason:
A circular reference where A includes B and B includes A has been caused by the include member reference.
Action:
Correct the include members.
Reason:
The named include member could not be located.
Action:
Verify that the data set name's include libraries are correct.
Reason:
The source member name is missing.
Action:
Specify a source member.
Reason:
The size of the named internal table has been exceeded.
Action:
Call CA Technical Support.
Reason:
The expansion of a line has exceeded the internal workarea.
Action:
Call CA Technical Support.
Reason:
See message ENBX046E.
Action:
Call CA Technical Support.
Reason:
The named abend has occurred.
Action:
Correct the condition that caused the abend.
Reason:
A storage failure has occurred in the named routine of the named module program.
Action:
Call CA Technical Support.
Reason:
This message indicates that control statement parsing has begun.
Action:
None.
Reason:
This message indicates that control statement parsing has completed with no errors.
Action:
None.
Reason:
This message indicates that control statement parsing has completed with errors.
Action:
Check the corresponding error messages.
Reason:
This message indicates that the FROM DDNAME or DSNAME clause is missing.
Action:
Specify a FROM DDNAME or DSNAME clause.
Reason:
This message indicates that the TO DDNAME or DSNAME clause is missing.
Action:
Specify a TO DDNAME or DSNAME clause.
Reason:
The named ddname is invalid.
Action:
Correct the ddname specification and resubmit.
Reason:
The named member is invalid.
Action:
Correct the member specification and resubmit.
Reason:
Either the TO MEMBER contains an asterisk (*) or the FROM MEMBER is wildcarded.
Action:
Verify both the TO MEMBER and FROM MEMBER specifications.
Reason:
The FROM DSNAME clause and the FROM DDNAME clause are mutually exclusive.
Action:
Check the FROM DSNAME and FROM DDNAME specifications.
Reason:
The TO DSNAME and the TO DDNAME clause are mutually exclusive.
Action:
Check the TO DSNAME and TO DDNAME specifications.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|