C1Y messages are generated during processing. The following list of C1Y messages includes possible causes and corrective actions to take in error situations.
Reason:
An I/O error occurred when attempting to perform some activity against the DDNAME shown in the message.
Action:
Make sure the DDNAME is correctly specified. Correct the action and retry.
Reason:
The file containing archived or transferred Elements does not contain a logical end-of-file.
Action:
Make sure the input specified to the RESTORE or TRANSFER action contains CA Endevor SCM information. If the file contains Elements, contact your administrator.
Reason:
The file containing archived or transferred Elements contains archived information that is not in the proper sequence as required by the RESTORE or TRANSFER action.
Action:
Make sure that the input specified to the RESTORE or TRANSFER action contains CA Endevor SCM information. If the file contains Elements, contact your administrator.
Reason:
See the previous message.
Action:
Act on the previous message.
Reason:
The output record length exceeds the output buffer size.
Action:
Increase the LRECL and block size specifications for the data set.
Reason:
The minimum LRECL should be the greater of three times the maximum MCF-record length or the TYPE-LENGTH plus (+) 14.
Action:
Increase the LRECL size specifications for the data set.
Reason:
There was no input to perform any of the actions requested. Either an invalid library name was specified, or there is an invalid member name within a data set.
Action:
Make sure the data set specified on the BSTIPT01 DD statement contains SCL syntax. Correct the JCL and resubmit the job. If the job is being submitted from the background panels, make sure that the JCL found in ISPSLIB associated with CA Endevor SCM contains the BSTIPT01 DD statement.
Reason:
A syntax error was encountered by the SCL parser. This message appears after all input is parsed.
Action:
Review the syntax and messages that precede this message. Correct any errors and resubmit the job.
Reason:
A syntax error was encountered by the SCL parser. This message appears after all input is parsed.
Action:
Review the syntax and messages that precede this message. Correct any errors and resubmit the job.
Reason:
The CA Endevor SCM syntax parser is beginning to parse the request cards.
Action:
None.
Reason:
Informational message. This message indicates that the syntax cards were successfully parsed.
Action:
None.
Reason:
Warning message. This message indicates that an incorrect option was specified.
Action:
Correct the SCL to avoid future warning messages.
Reason:
A COPY or LIST function is directed to an existing member name, and the REPLACE option was not specified.
Action:
Specify REPLACE, or choose a different target member name.
Reason:
Informational message. This message indicates that the member name was copied to the target Restore data set.
Action:
None.
Reason:
A COPY action failed. This message is preceded by an error message indicating the reason.
Action:
Review other messages in the log to determine the cause of the problem.
Reason:
The processor group you specified does not include a GENERATE processor, therefore the BYPASS GENERATE PROCESSOR option will be ignored.
Action:
Make sure that you specified the correct processor group.
Reason:
Two or more WHERE clauses in this job are mutually exclusive.
Action:
Make sure that all the WHERE clauses are compatible.
Reason:
The maximum record length of the input file is 80. The attributes of the input file indicate the record length is greater than 80.
Action:
Make sure the name of the input file is correct. If so, reallocate with a record length of 80.
Reason:
You have specified WHERE CCID OF as part of a LIST or TRANSFER request from an archive file. This syntax is invalid.
Action:
Respecify the request using WHERE CCID.
Reason:
This message is issued when AUTOGEN is in effect. It indicates that both the AUTOGEN and bypass generate processor options were specified on the same request. These two options are mutually exclusive.
Action:
Review the options and remove the option you do not need.
Reason:
This message indicates the end of the execution log. The highest return code encountered by the RESTORE program was return code.
Action:
None.
Reason:
A temporary file as indicated by the DDNAME encountered an I/O error. The file that encountered the error may have been too small and may need to be increased to hold a large Element.
Action:
Verify that the template JCL associated with the RESTORE, COPY, or LIST action properly defines all temporary files. The template JCL is described in the Installation Guide.
Reason:
An I/O was detected while writing to the data set identified in the message.
Action:
Review other messages in the log to determine the cause of the problem.
Reason:
This Element already exists at this Stage.
Action:
A request to RESTORE an Element into an Environment, Stage, System, Subsystem, and type was made. This message indicates that an Element of same name already exists.
Action:
Delete the Element in target Stage, or RESTORE the Element to a different CA Endevor SCM location.
Reason:
A request to RESTORE was made when this Element already exists at the target location or further up the map from the location specified in the message.
Action:
Delete the Element.
Reason:
The component list base in the archive file is corrupted.
Action:
The Element is restored correctly, but the component list cannot be restored from the archive. Re-generate the Element to create a component list.
Reason:
The ARCHIVE, LIST, or TRANSFER actions encountered an error processing an external data set. The error is described in a message that follows message C1Y0053E.
Action:
For the appropriate corrective action, see the message that follows C1Y0053E.
Reason:
The Element and component base and delta records are being copied from an archive file and merged into a file. The merge failed.
Action:
Contact your administrator.
Reason:
BSTIPT01 or the DDNAME override specified in the first character string of the C1BM3000 execution parameter is not allocated.
Action:
Provide a BSTIPT01 DD card or a DD card for the parameter override.
Reason:
The C1BM3000 execution parameter was incorrect. The parameter can contain up to four parameters separated by commas. The first parameter is the override to the SCL DDNAME (defaults to BSTIPT01) and can be up to any eight characters which constitute a valid DDNAME; the second is the override to the message file DDNAME (defaults to CONMSGS1); the third is the Package ID; and the fourth is the override to the message summary DDNAME (defaults to CONMSGS2).
This message is WTOd since it may be the message DDNAME which cannot be allocated. In this case, nothing can be written to the messages data set.
Action:
Correct the parameter.
Reason:
The primary message data set, usually C1MSGS1, is not allocated. The System, therefore, is not able to write any messages.
This message is WTOd since it may be the message DDNAME which cannot be allocated; in this case, nothing can be written to the messages data set.
Action:
Correct the parameter.
Reason:
CA Endevor SCM turned off the RETAINAPI parameter, because it would cause an ABEND in this setup. The BC1PCSV0 utility is attached and not linked or branched to.
Action:
Remove the RETAINAPI parameter or change the way the BC1PCSV0 utility is executed.
Reason:
CA Endevor SCM cannot find the type definition named in the message.
Action:
Verify that the type name was specified correctly. Define the type if necessary.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|