C1X Messages

This section details messages generated in the course of processing, along with possible causes and corrective actions to take in error situations.

C1X0001I

The ASXBSENV and ASXBUSER values were forced from the alternate id to the user id at processor end

Reason:

The processor step included an OPEN of LGNT$$$I to force the ASXBSENV and ASXBUSER fields to those of the alternate id. However, the corresponding LGNT$$$O OPEN was not done. In this case, CA Endevor SCM reset the ASXBSENV and ASXBUSER fields back to their original values when the processor step ended.

Action:

None

C1X0003E

RC=severity code ERROR ACCESSING vsam ddname MASTER FILE

Reason:

An open request was issued against the Master Control File for the indicated Stage. An open error was encountered.

Action:

Make sure that the specified C1DEFLTS found in the files CONLIB and STEPLIB correctly define the Stage 1 Master Control File for which the action was requested. Verify that the VSAM file DSNAME exists and is available.

C1X0004E

RC=vsam error code VSAM ERROR ACCESSING dsname

Reason:

An error was encountered when attempting to open the VSAM master file.

Action:

See the appropriate IBM VSAM manual to determine the cause of the error.

C1X0005E

VSAM ERROR RC return code FDBK feedback DSN data set name

Reason:

An error was detected when attempting to read, write, or delete a record from a VSAM file. The name of the current data set is displayed.

Action:

Look up the VSAM return code and feedback to determine the cause of this condition.

C1X0006E

C1DEFLTS ELM CTLG NAME DIFFERENT THAN LAST ELM CTLGUSED: CTLGUSED: catalog data set name

Reason:

A Stage record was successfully read. The name of the catalog in the Stage record is different than the name of the catalog found in the defaults table.

Action:

Verify that you are picking up the correct C1DEFLTS table. If you are using the correct CIDEFLTS table, run BC1JXCNM to synchronize your catalog with the MCFs.

C1X0007E

CANNOT CONSTRUCT THE EINDEX NAME FROM THE CATALOG NAME. IT CANNOT BE GREATER THAN 37 CHARACTERS.

Reason:

The catalog name is too large.

Action:

Create a catalog name that is 37 characters or less.

C1X0008C

UNABLE TO LOCATE INCLUDE ELEMENT Element name REFERENCED BY Element name

Reason:

Unable to expand INCLUDEs found in the requested Element.

Action:

Verify that the INCLUDE library definitions specified in the Stage 1 and Stage 2 type definitions are correct and contain the INCLUDE members.

C1X0009E

RECURSIVE REFERENCE TO INCLUDE MEMBER member name DETECTED WHILE EXPANDING INCLUDE MEMBER member name

Reason:

A reference to a previously specified INCLUDE module would result in an endless loop.

Action:

Make sure that, when nesting INCLUDE modules, not to include a previously specified INCLUDE module (that is, remove all recursive calls to previously referenced INCLUDE modules).

C1X0010I

STEP step name PROGRAM program name COMPLETED, RC = return code

Reason:

This is an informational message which displays the highest return code associated with the indicated processor.

Action:

None. You should review these processor return codes to verify that the requested action successfully completed.

C1X0011S

STEP step name PROGRAM program name ABENDED, CODE = return code

Reason:

A processor has abended. The message indicates the abend code associated with the abended processor.

Action:

Review the messages displayed prior to this message and check the appropriate IBM Error Codes and Messages manual. If the abend code BADGU is displayed, it means the program named in this message is not supported in a processor.

C1X0012I

STEP step name INVOKING PROGRAM program name

Reason:

This is an informational message that indicates the name of the processor to be executed.

Action:

None. In the event that an error is encountered in a processor to follow, this message gives an indication of the Element name which was executed.

C1X0013I

PARM = parameter

Reason:

This is an informational message that indicates the parameter passed to the program as displayed in message C1X0012I. This is useful in verifying parameter values passed as input to a particular program. Substituted symbolics are displayed.

Action:

None. If an error is encountered during processor execution, information displayed in the PARM=VALUE may be useful to verify that the processor is executing against the correct System, Element, and so on.

C1X0014I

STEP step number (name) NOT EXECUTED BECAUSE OF CONDITION CODE(S)

Reason:

The step identified in the message was not executed because of the COND parameter specification on the EXEC statement.

Action:

None.

C1X0015I

STEP step number (name) NOT EXECUTED BECAUSE OF AN "EXECIF" CLAUSE

Reason:

The step identified in the message was not executed because it did not meet the conditions set in the EXECIF parameter.

Action:

None.

C1X0016E

ERROR IN processor name PROCESSOR DEFINITION - INVALID COND CLAUSE

Reason:

The COND parameter is specified incorrectly in the processor identified in the message.

Action:

Correct the COND parameter specification.

C1X0017E

ERROR IN processor name PROCESSOR DEFINITION - UNABLE TO RESOLVE STEP NAME IN COND PARM FOR STEP step number.

Reason:

The step name specified in the COND parameter is not defined in the processor identified in the message.

Action:

Correct the COND parameter specification.

C1X0018E

ERROR IN processor id PROCESSOR DEFINITION - NO OUTPUT DD STATEMENT WAS SPECIFIED IN THE CONWRITE STEP step

Reason:

The CONWRITE utility requires the specification of a DD statement that is used as output. CONWRITE writes the output to the first DD statement, after the EXEC statement that does not begin with the characters C1INCL. This statement is missing.

Action:

Add the DD statement to the processor.

C1X0019E

THIS PROCESSOR MUST BE REGENERATED — IT CONTAINS IF-THEN-ELSE STMTS FROM ENDEVOR RELEASE 3.72

Reason:

Indicates that a processor from a previous CA Endevor SCM release with IF-THEN-ELSE statements was encountered.

Action:

Regenerate the processor.

C1X0030E

ELM EXTENSION DEFINE FUNCTION CALLED WITH AN INVALID PATH AREA

Reason:

Internal error. The PATH area passed to this program contains an invalid length. This error was detected by the Element extension subroutine, BC1PEEXT.

Action:

Contact your administrator.

C1X0031E

VSAM I/O ERROR ON ELM EXTENSION CREATE/DELETE/UPDATE FUNCTION AGAINST DDNAME ddname, RC= return code, FEEDBK= feedback code

Reason:

A VSAM error was detected while attempting to create, delete, or update an Element extension record in the master control file.

Action:

Look up the VSAM return code and feedback code to determine the cause of this problem.

C1X0032E

ELM EXTENSION RCD NOT FOUND ON DDNAME ddname, KEY= record key DURING CREATE/DELETE/UPDATE RETRIEVE TO/ADD FROM FUNCTION

Reason:

An Element extension record was not found.

Action:

Contact your administrator.

C1X0033E

ELEMENT RCD DOES NOT CONTAIN A VALID EXTENSION KEY, KEY= record key

Reason:

Internal error. The key to access an extension record is stored in the Element record. The value found at this location is not a valid extension key.

Action:

Contact your administrator.

C1X0034E

ELEMENT EXTENSION "TO" LIBRARY DELETION FAILED, KEY= record key, ENV Environment name STG Stage ID

Reason:

Internal error. The delete of the Element extension "TO" library record failed. The key of the extension record and the Environment and Stage ID are displayed.

Action:

Contact your administrator.

C1X0100E

RC=return code message [INTERNAL FUNCTION] ERROR ATTEMPTING action FOR dsname (member name)

Reason:

See the following corrective Action.

Action:

For the error messages associated with the indicated error, see the appropriate library management documentation.

C1X0102E

LIBRARIAN utility return code ERROR: RC=return code - [READ ACCESS RETURN CODE]

Reason:

A CA Librarian error was encountered.

Action:

See the appropriate library management documentation for the error messages associated with the indicated error.

C1X0103C

ELEMENT WAS FOUND AT PHYSICAL PATH LOCATION ENV/Environment name SYS/System name SBS/Subsystem name STAGE/Stage ID

Reason:

A version of the Element was found at the named location, which is in a mapped Environment but is not on the current map route.

Action:

See message C1X0104E.

C1X0103W

ELEMENT WAS FOUND AT PHYSICAL PATH LOCATION ENV/Environment name SYS/System name SBS/Subsystem name STAGE/Stage ID

Reason:

A version of the Element was found at the named location, which is in a mapped Environment but is not on the current map route.

Action:

See message C1X0104E.

C1X0103I

ELEMENT WAS FOUND AT PHYSICAL PATH LOCATION ENV/Environment name SYS/System name SBS/Subsystem name STAGE/Stage ID

Reason:

A version of the Element was found at the named location, which is in a mapped Environment but is not on the current map route.

Action:

See message C1X0104E.

C1X0104E

JUMP OPTION IS REQUIRED FOR SYSTEM System name TO BYPASS THE ELEMENT IN THE PHYSICAL PATH

Reason:

The System named in the message requires that MOVE actions be specified with JUMP=Y when CA Endevor SCM encounters a version of the Element(s) to be moved in a mapped Environment, but not on the map.

Action:

Resubmit the MOVE request with JUMP=Y.

C1X0201E

STMT statement number INVALID--NAME OPERAND EXCEEDS 8 CHARACTERS

Reason:

The NAME operand in the statement identified in the message contains more than eight characters. Only eight characters are allowed.

Action:

Correct the statement and resubmit.

C1X0202E

STMT statement number INVALID ── statement

Reason:

A JCL error was encountered during the Scan 1 phase of JCL translation. Scan 1 errors are typically due to omitting a comma when attempting to continue a JCL statement to a second line.

Action:

Review the JCL statement in error, correct the problem, and reprocess the JCL.

C1X0203E

STMT statement number INVALID--REQUIRED PARAMETER "PGM" MUST BE THE FIRST PARAMETER ON THE EXECUTE STATEMENT

Reason:

The statement identified in the message is an EXECUTE statement, but does not have PGM as its first parameter.

Action:

Correct the statement and resubmit.

C1X0204E

STMT statement number INVALID--REFERBACK NOT SUPPORTED ON THE "PGM" PARAMETER

Reason:

A referback was specified for the PGM parameter.

Action:

Change the referback to an explicit specification.

C1X0205W

STMT statement number INVALID--KEYWORD keyword IS NOT SUPPORTED

Reason:

The keyword identified in the message is not supported as used in the statement identified in the message.

Action:

Correct the statement and resubmit.

C1X0206E

STMT statement number INVALID--KEYWORD keyword IS NOT SUPPORTED

Reason:

The keyword identified in the message is not supported as used in the statement identified in the message.

Action:

Correct the statement and resubmit.

C1X0207E

STMT statement number INVALID--CONTAINS UNBALANCED PARENTHESES

Reason:

Nesting specified in the indicated JCL statement is invalid.

Action:

Make sure that parentheses are properly balanced, correct the error, and resubmit the JCL.

C1X0208E

STMT statement number INVALID--CONTAINS UNBALANCED QUOTES

Reason:

Nesting specified in the indicated JCL statement is invalid.

Action:

Make sure that quotes are properly balanced, correct the error, and resubmit the JCL.

C1X0209E

STMT statement number INVALID--CONTAINS ILLEGAL FORMAT

Reason:

During scan 1 of JCL translation, the JCL statement that was indicated was invalid, probably due to improper continuation specification.

Action:

Make sure that the JCL statement was specified correctly, correct the error, and resubmit the job.

C1X0210E

STMT statement number INVALID--CONTAINS INVALID KEYWORD: keyword

Reason:

The JCL statement specified an unknown keyword that was flagged as an error.

Action:

Make sure that the keyword flagged is a valid JCL keyword as shown in the appropriate JCL reference book. Correct the keyword and resubmit the job.

C1X0211E

STMT statement number INVALID--COND PARAM VALUE LONGER THAN nnn CHARACTERS

Reason:

The COND= parameter was improperly specified.

Action:

For details about the COND=parameter, see the Extended Processors Guide. Correct the COND= parameter and resubmit the job.

C1X0212E

STMT statement number INVALID--IMPROPER EVEN/ONLY SPECIFICATION IN THE COND PARAMETER

Reason:

The COND parameter in the statement identified in the message contains improper coding of the EVEN/ONLY specification.

Action:

Correct the EVEN/ONLY syntax and resubmit.

C1X0213E

STMT statement number INVALID--FOOTPRINT PARAM CONTAINS INVALID VALUE

Reason:

The footprint parameter is improperly coded.

Action:

For a list of the valid values that can be specified for the FOOTPRINT= parameter, see the Extended Processors Guide.

C1X0214E

STMT statement number INVALID--DDNAME IS REQUIRED

Reason:

A DD statement was coded in the processor but no DDname was specified.

Action:

Correct the format of the DD statement.

C1X0215E

STMT statement number INVALID--NUMERIC VALUE EXPECTED IN FIELD field name

Reason:

The statement identified in the message allows other than a numeric value for the field identified in the message. However, the field requires numeric values.

Action:

Correct the statement and resubmit.

C1X0216E

STMT statement number INVALID--DLM SPECIFICATION IS IN ERROR

Reason:

The DLM parameter in the statement identified in the message was coded incorrectly.

Action:

Correct the statement and resubmit.

C1X0217E

STMT statement number INVALID--TOO MANY POSITIONAL PARAMETERS IN FIELD field name

Reason:

The field identified in the message was assigned too many positional parameters in the statement identified in the message.

Action:

Correct the statement and resubmit.

C1X0218E

STMT statement number INVALID--EXPECTING KEYWORD OPERAND

Reason:

1) The statement identified in the message contains a keyword that must be used with an operand, but the operand is missing.

2) If the error occurs on the first statement in the processor, the probable cause is an invalid symbol defined on the proc statement.

Action:

1) Correct the statement and resubmit.

2) Check all the variable names defined on the proc statment. Correct any that are nine or more characters in length and resubmit.

C1X0219E

STMT statement number INVALID--DLM IS ONLY VALID IN COMBINATION WITH A SYSIN DATASTREAM

Reason:

The DLM parameter in the statement identified in the message was not coded as part of a SYSIN statement. The DLM parameter is only valid when it is coded as part of a SYSIN statement.

Action:

Correct the statement and resubmit.

C1X0220E

STMT statement number INVALID--MUTUALLY EXCLUSIVE FIELDS field1 name AND field2 name SPECIFIED

Reason:

The two fields identified in the message cannot be coded in the same statement.

Action:

Correct the statement and resubmit.

C1X0221E

UNDEFINED SYMBOLIC PARAMETER - parameter

Reason:

There is a symbolic in this statement that is not a CA Endevor SCM symbolic and is not defined in the PROC statement.

Action:

Make sure that the symbolic is coded correctly. Include it in the PROC statement if necessary.

C1X0222E

STMT statement number INVALID--EXECIF PARAM VALUE LONGER THAN nnn CHARACTERS

Reason:

One or both of the values in the EXECIF statement of the statement identified in the message has more than 999 characters.

Action:

Correct the EXECIF statement and resubmit.

C1X0223E

STMT statement-number INVALID--FOOTPRNT, MONITOR AND DSN KEYWORDS NOT ALLOWED WITH PATH

Reason:

The PATH keyword was specified on the DD statement. The FOOTPRNT, MONITOR, and DSN keywords cannot be specified along with the PATH keyword.

Action:

If using a PATH, remove the FOOTPRNT and MONITOR keywords from the statement. If using a DSN, remove the PATH keyword from the statement.

C1X0224E

STMT statement number INVALID--INVALID OPERATOR IN parameter name PARAMETER - EQ,NE,GT,GE,LT,LE

Reason:

The operator coded in the parameter identified in the message is not one of the following: EQ, NE, GT, GE, LT, LE.

Action:

Correct the parameter specification and resubmit.

C1X0226E

STMT statement number INVALID--SYNTAX ERROR, TOO MANY SUBFIELDS IN parameter name PARAMETER

Reason:

The parameter identified in the message specifies more than the allowed number of subfields.

Action:

Correct the parameter specification and resubmit.

C1X0228E

STMT statement number INVALID--OPERATOR MISSING FROM parameter name PARAMETER

Reason:

The parameter identified in the message does not specify an operator.

Action:

Correct the parameter specification using one of the following operators: EQ, NE, GT, GE, LT, LE.

C1X0230E

STMT statement number INVALID--SYNTAX ERROR IN parameter name PARAMETER

Reason:

The parameter identified in the message was coded incorrectly.

Action:

Correct the parameter specification and resubmit.

C1X0231E

STMT statement number INVALID - EXPECTING CONTINUATION CARD

Reason:

A JCL statement was improperly continued.

Action:

Make sure that the JCL statement flagged in error is properly continued. For a description of continuing JCL statements, see the appropriate IBM JCL manual.

C1X0232E

STMT statement number INVALID--NON-JCL CARD ENCOUNTERED PRIOR TO FIRST STEP

Reason:

A non-JCL statement was encountered prior to the first EXEC statement.

Action:

Remove the non-JCL statement.

C1X0233E

STMT statement number INVALID--EXCESSIVE PARAMETER LENGTH (>nnn CHARS) FOR KEYWORD keyword

Reason:

The statement identified in the message contains an invalid length specification for the keyword identified in the message.

Action:

Recode the statement and resubmit.

C1X0234E

STMT statement number INVALID--EXPECTING CONTINUATION CARD, NULL CARD ENCOUNTERED

Reason:

The statement prior to the statement identified in the message was continued, however the statement identified in this message is a null (end-of-job) statement.

Action:

Correct the JCL.

C1X0236E

STMT statement number INVALID--EXPECTING CONTINUATION CARD, END OF FILE ENCOUNTERED

Reason:

The statement prior to the statement identified in the message was continued, however the statement identified in this message is not a valid continued JCL statement.

Action:

Correct the JCL.

C1X0237E

STMT statement number INVALID--IF-THEN-ELSE EXPRESSIONS MUST BE CONTAINED IN PARENTHESES

Reason:

The expression must be enclosed in parentheses.

Action:

Correct the syntax error in this statement.

C1X0238E

STMT statement number INVALID USE OF QUOTES

Reason:

The statement identified in the message contains quotes that are either used improperly or placed incorrectly.

Action:

Modify the statement as necessary, and then resubmit.

C1X0239E

STMT statement number INVALID USE OF PARENTHESIS

Reason:

The statement identified in the message contains parentheses that are either used improperly or placed incorrectly.

Action:

Modify the statement as necessary, and then resubmit.

C1X0240I

jcl statement and line number

Reason:

This is an informational message. The JCL statement and associated line number are shown. Use this information to aid in the debugging of any messages which will appear following the input JCL.

Action:

None.

C1X0241E

STMT statement number INVALID--PARM= VALUE EXPANDS TO GREATER THAN MAX ALLOWED (nnn CHARS)

Reason:

A PARM= value was greater than 100 characters.

Action:

Make sure that the PARM= value does not exceed 100 characters. For a description of coding the PARM= parameter, see the appropriate IBM JCL manual.

C1X0242E

STMT statement number INVALID--USER SYMBOLICS MAY NOT BEGIN WITH "C1", RESERVED FOR ENDEVOR USE

Reason:

One or more symbolics defined in the PROC statement begin with C1.

Action:

Correct the symbolic specification.

C1X0243E

STMT statement number INVALID--USER SYMBOLICS MAY NOT CONTAIN AMPERSANDS

Reason:

One or more symbolics defined in the PROC statement contain an ampersand.

Action:

Correct the symbolic specification.

C1X0244E

DUPLICATE KEYWORD FOUND - keyword

Reason:

The DCB subparameter duplicates an ESA keyword coded outside the DCB.

Action:

Change either the DCB information, or the external keyword.

C1X0245E

DSNAME MAY BE TRUNCATED: DEFINED LENGTH CAN BE UP TO nn BYTES, DEPENDING ON JOBNAME

Reason:

Internal error. The size of the data set name exceeds the maximum allowed. This could happen when a temporary data set name is generated by CA Endevor SCM.

Action:

Contact your administrator.

C1X0245W

DSNAME MAY BE TRUNCATED: DEFINED LENGTH CAN BE UP TO nn BYTES, DEPENDING ON JOBNAME

Reason:

The size of the data set name exceeds the maximum allowed. This could happen when a temporary data set name is generated by CA Endevor SCM.

Action:

Contact your administrator.

C1X0249E

STMT statement number INVALID--RIGHT COMPARATOR MISSING FROM EXECIF CLAUSE

Reason:

EXECIF clause syntax require the specification of two values for comparison. The EXECIF clause in this statement does not specify the second value.

Action:

Specify the second value and resubmit.

C1X0250W

ddname IS A RESERVED ENDEVOR DDNAME - ALLOCATION REQUEST NOT PERFORMED

Reason:

The DDNAME shown in the message is a DDNAME that CA Endevor SCM retains for its own use.

Action:

Specify a DDNAME other than the DDNAME shown in the message. If the DDNAME shown in the message cannot be changed, contact your administrator for assistance.

C1X0251E

INVALID PARAMETER SPECIFIED FOR keyword KEYWORD: parameter

Reason:

The format of syntax associated with this keyword is invalid. The parameter is invalid or missing.

Action:

For the proper syntax format of this keyword, see the SCL Reference Guide.

C1X0260W

REQUIRED THEN CLAUSE IS MISSING ON IF-THEN STATEMENT

Reason:

A THEN clause is missing on an IF-THEN statement.

Action:

Correct the syntax.

C1X0261E

INVALID EXPRESSION ELEMENT Element; TRUE OR FALSE EXPECTED

Reason:

During processing, the IF clause discovered an invalid Element.

Action:

Correct the syntax.

C1X0262E

INVALID REFERBACK. THE REFERENCED STEP stepname IS NOT IN PROCESSOR

Reason:

A referback to the indicated stepname is invalid because the stepname is not in the processor.

Action:

Correct the syntax.

C1X0263E

AN ERROR OCCURRED PARSING IF-THEN-ELSE, RC(return code), +

Reason:

Parsing an IF-THEN-ELSE caused an error.

Action:

Correct the syntax. If the error persists, note the return and reason code in the error message and contact CA Technical Support. The return code and reason code that appear is for use by CA Technical Support as an aid to help locate and debug IF-THEN-ELSE issues that cannot be resolved by correcting the syntax.

C1X0264E

INVALID EXPRESSION OPERATOR (operator)

Reason:

The indicated expression operator is invalid.

Action:

Correct the syntax. Valid operators are GT, LT, NG, NL, EQ, NE, GE, LE, NOT, AND, OR.

C1X0265E

RUN EXPRESSION REQUIRES STEP REFERBACK

Reason:

The RUN expression is specified in the IF-THEN-ELSE logic. This expression requires a refer back step name (IF RUN.stepname=TRUE).

Action:

Modify the syntax to include a refer back step name.

C1X0266E

INVALID REFERBACK VALUE referback step name

Reason:

The refer back step name does not exist.

Action:

Make sure the step name is spelled correctly.

C1X0270E

MISMATCHED IF-ENDIF PAIR: unmatched if statement| unmatched endif statement

Reason:

The number of IF and ENDIF statements do not match. The message text indicates if there are more IF or ENDIF statements.

Action:

Modify the processor syntax and make sure all the IF statements are paired with ENDIF statements.

C1X0500E

INVALID SYNTAX IN INPUT DATA

Reason:

The control statement read from SYSIN contained invalid syntax.

Action:

Correct the syntax.

C1X0501W

MEMBER member name NOT FOUND IN ANY INPUT LIBRARY

Reason:

The member identified in the message does not exist in the input library.

Action:

Make sure that the member name was specified correctly on the input control statement.

C1X0502I

MEMBER member name SUCCESSFULLY COPIED

Reason:

Informational message. The member identified in the message was successfully copied.

Action:

None.

C1X0503E

MEMBER member name RESIDES IN OUTPUT LIBRARY AND REPLACE NOT SPECIFIED

Reason:

The input control statement specifies a member that currently exists in the output library, however, REPLACE was not specified on the control statement.

Action:

Specify REPLACE on the control statement.

C1X0504E

COMPRESS NOT SUPPORTED: input ddname SAME AS output ddname

Reason:

A COMPRESS was requested, but BSTCOPY does not support the IEBCOPY COMPRESS function.

Action:

If a COMPRESS is desired, specify IEBCOPY instead of BSTCOPY.

C1X0505E

DSORG OF dsorg NOT SUPPORTED

Reason:

The data set organization specified in the message is not supported by BSTCOPY. BSTCOPY only supports an organization of PO.

Action:

Use IEBCOPY instead of BSTCOPY.

C1X0506E

ROOT MODULE member name NOT SELECTED WITH ALIAS member name

Reason:

One or more aliases were specified on the input control statement(s), however their root member was not specified.

Action:

Root members must be copied with aliases.

C1X0507E

THE BLKSIZE OF THE INPUT DATA SET IS > THE BLKSIZE OF THE OUTPUT DATA SET

Reason:

BSTCOPY has determined that the block size for the input data set is greater than the block size for the output data set. This condition cannot exist when RECFM=U.

Action:

Make sure that the block size is the same at the source and the target of BSTCOPY statements.

C1X0508E

SCATTERED OR OVERLAY NOT ALLOWED (member name)

Reason:

The member name identified in the message is in overlay or SCATTER format.

Action:

Use IEBCOPY instead of BSTCOPY.

C1X0509E

BEGINNING TTR EQUAL TO TEXT TTR

Reason:

BSTCOPY detected a load module that is invalid because the beginning TTR is equal to the text TTR.

Action:

Regenerate the Element associated with the load module.

C1X0510E

INVALID SELECT FORMAT FOR HEX MEMBER NAME SUPPORT

Reason:

When using BSTCOPY to copy a member with a non-standard name (non-alphanumeric characters) the following rules must be followed:

Only one member can be copied per SELECT statement.
The format of the statement must be one of the following: SELECT M=((member name)) SELECT M=((member name, member name))
In this example, the member name must be exactly eight characters long.

If the REPLACE option is desired, it must be coded as part of the INDD keyword of the COPY statement.

Action:

Correct the BSTCOPY request and resubmit.

C1X0511I

text

Reason:

The text in this message echoes BSTCOPY input statements, and displays input and output data set names used by BSTCOPY.

Action:

None.

C1X0512E

VALIDATION ERROR, RECFM INCOMPATIBLE: source ddname(recfm) — target ddname(recfm)

Reason:

The RECFM at the source location of a BSTCOPY statement is not the same as the RECFM at the target.

Action:

Make sure that the RECFM is the same at the source and the target of BSTCOPY statements.

C1X0513E

ERROR ACCESSING SYSIN FILE

Reason:

An error was encountered accessing the SYSIN file.

Action:

Make sure that the SYSIN file is present and pointing to the input stream.

C1X0514W

INPUT LIBRARY ddname CONTAINS NO MEMBERS

Reason:

The input library specified in the BSTCOPY processor step contains no members.

Action:

Make sure the library name is correct. If not, correct the processor and re-execute the action.

C1X0515E

< I/O operation 1 > IN SHIPPED PKG AND < I/O operation 2 > IN SUPERSEDING PKG INDICATE OUT OF SEQUENCE CONDITION

Reason:

An operation was performed on a member, after the Package that is being shipped was executed, and before the superseding Package was executed. The member may have been updated in another Package, but under a different Element type. Another possibility is that the member was updated under the same Element name and type, but outside of Package processing.

Action:

Investigate to find out what has happened to the member between the two Package executions. Recover the member as indicated by the situation.