Utility Report Messages › TMSCONVR Messages

TMSCONVR Messages

** INVALID SYNTAX, NEAR COLUMN xx

Reason:

An attempt to parse the control statement failed at or near column xx.

Action:

Correct the control statement(s) and resubmit the job.

** 'xxxx' FIELD FOR 'yyyyyyy' IS INVALID

Reason:

One of the values for displacement, length, format, or type(xxxx) for keyword yyyyyyy is invalid.

Action:

Correct the control statement(s) and resubmit the job.

** 'xxxxxxx' KEYWORD ALREADY SPECIFIED

Reason:

Keyword xxxxxxx is only allowed to be used once in a control statement.

Action:

Correct the control statement(s) and resubmit the job.

** 'xxxxxxx' EXCEEDS TMC FIELD LENGTH

Reason:

The value for keyword xxxxxxx exceeds the maximum length allowed for the keyword.

Action:

Correct the control statement(s) and resubmit the job.

** INVALID RETURN CODE FROM USER-EXIT

Reason:

The only valid return code values from the user exit are 0, 4, and8.

Action:

Correct the user exit and resubmit the job.

** VOLUME-SERIAL-NUMBER MISSING

Reason:

The volser field is required to produce output records in the format requested.

Action:

Correct the control statement(s) or the input data and resubmit the job.

** FIELDS NECESSARY FOR TMSEXPDT OUTPUT NOT SPECIFIED

Reason:

The DSN and either EXPDT, RETPD, or WRETPD keywords are required to generate output for TMSEXPDT.

Action:

Correct the control statement(s) and resubmit the job.

** NO SYSIN CONTROL CARDS SPECIFIED

Reason:

Control statements are required to indicate the input fields and attributes for processing.

Action:

Correct the control statement(s) and resubmit the job.

** POSITION 1 CONTAINS A BLANK

Reason:

Control statements must begin in position 1.

Action:

Correct the control statement(s) and resubmit the job.

** DATEFMT, xxxxxxxxxx, IS INVALID
** RETCODE=xx, REASON=xx, FDBK=xx

Reason:

The DATEFMT value xxxxxxxxxx is invalid for the keyword.

Action:

Correct the control statements(s) and resubmit the job. See the TMMDATE macro return and reason codes in the Programming Guide.

** TMMDATE OPEN FAILED
** RETCODE=xx, REASON=xx, FDBK=xx

Reason:

CA 1 could not open the date processing routines.

Action:

Ensure that all CA 1 libraries are correctly specified in the link list or STEPLIB and resubmit the job. See the TMMDATE macro return and reason codes in the Programming Guide.

** TMMDATE SET_FORMAT FAILED. DATEFMT=xxxxxxxxxx

Reason:

This is an internal error.

Action:

For assistance, contact Technical Support athttp://ca.com/support.

** PASSWORD DATA FORMAT NOT ALLOWED

Reason:

Password format is not allowed to be used in the control statements.

Action:

Correct the control statement(s) and resubmit the job.

** HEX/BINARY DATES NOT ALLOWED

Reason:

Valid date fields in input data must be in packed decimal or character format.

Action:

Correct the control statement(s) or input data and resubmit the job.

** NUMBER OF ERRORS EXCEEDS MAXERR PARM **

Reason:

The number of errors encountered exceeds the value specified on the JCL parameter MAXERR or the default value of 50.

Action:

Correct the JCL and resubmit the job.

ABEND004 DUE TO PARAMETER ERROR

Reason:

An error has occurred in processing the parameter.

Action:

See previous error messages to correct the error and resubmit the job.

** ABEND006 DUE TO CONTROL/INPUT ERRORS **

Reason:

An error has occurred in processing the control statements or the input data.

Action:

See previous error messages to correct the error and resubmit the job.

RECORD xxxxxxx, '=' NOT FOUND DURING KEYWORD SEARCH - MASTER(ACTIVITY) RECORD IGNORED.

Reason:

An = was not found as expected during keyword processing for control statement xxxxxxx. The control statement has been skipped.

Action:

Correct the control statement(s) and resubmit the job.

** 'xxxxxxx' MUST BE yy CHARACTERS

Reason:

The keyword xxxxxxx must be yy characters in length.

Action:

Correct the control statement(s) and resubmit the job.

RECORD xxxxxxx, 'yyyyyyy' IS NOT A VALID KEYWORD - MASTER(ACTIVITY) RECORD IGNORED.

Reason:

An invalid keyword, yyyyyyy, was encountered in processing control statement xxxxxxx. The control statement has been skipped.

Action:

Correct the control statement(s) and resubmit the job.

RECORD xxxxxxx, INVALID VOLSER(yyyyyy) FROM TMSXITU - TMINPUT RECORD IGNORED.

Reason:

Volser yyyyyy in input data record xxxxxxx is not in the TMC or user exit TMSXITU is in error. The input data record has been skipped.

Action:

Correct the input data or user exit TMSXITU and resubmit the job.

RECORD xxxxxxx, INVALID VOLSER(yyyyyy) FROM TMSXITU - DEFAULT SRECORD IGNORED.

Reason:

Volser yyyyyy in control statement xxxxxxx is not in the TMC or user exit TMSXITU is in error. The control statement has been skipped.

Action:

Correct the control statement(s) or user exit TMSXITU and resubmit the job.

RECORD xxxxxxx, INVALID VOLSER(yyyyyy) FROM TMSXITU - MASTER(ACTIVITY) RECORD IGNORED.

Reason:

Volser yyyyyy in control statement xxxxxxx is not in the TMC or user exit TMSXITU is in error. The control statement has been skipped.

Action:

Correct the control statement or user exit TMSXITU and resubmit the job.

** DATEFMT NOT ALLOWED FOR THIS FIELD

Reason:

The DATEFMT keyword is not valid for this field.

Action:

Correct the control statement(s) and resubmit the job.

RECORD xxxxxxx, FIELD 'yyyyyyy' CONTAINS INVALID DATA OR DEFINEDWRONG - MASTER (ACTIVITY) RECORD IGNORED.

Reason:

Field yyyyyyy in input data record xxxxxxx contains invalid data or is not defined correctly in the control statement. The input data record is skipped.

Action:

Correct the control statement(s) or input data and resubmit the job.

RECORD xxxxxxx, FIELD 'yyyyyyy' CONTAINS INVALID DATA OR DEFINEDWRONG - DEFAULTS RECORD IGNORED.

Reason:

Field yyyyyyy in control statement xxxxxxx contains invalid data or is not defined correctly in the control statement. The control statement is skipped.

Action:

Correct the control statement(s) or input data and resubmit the job.

RECORD xxxxxxx, FIELD 'yyyyyyy' CONTAINS INVALID DATA OR DEFINEDWRONG - MASTER (ACTIVITY) RECORD IGNORED.

Reason:

Field yyyyyyy in control statement xxxxxxx contains invalid data or is not defined correctly in the control statement. The control statement is skipped.

Action:

Correct the control statement(s) or input data and resubmit the job.

VOLSER xxxxxx HAS DUPLICATE RECORDS - TMINPUT RECORD IGNORED.

Reason:

The same volser is not allowed more than once in the input data. The input data record is skipped.

Action:

Correct the input data and resubmit the job.

VOLSER xxxxxx AND DSN dsname HAS DUPLICATE RECORDS - MASTER(ACTIVITY) RECORD IGNORED.

Reason:

The same volser and data set name cannot be used more than once in the control statements. The control statement is skipped.

Action:

Correct the control statement(s) and resubmit the job.

DSN= dsname HAS DUPLICATE RECORDS - TMINPUT RECORD IGNORED.

Reason:

A data set name can only be used once in the input data. The input data record is skipped.

Action:

Correct the input data and resubmit the job.

DSN= dsname HAS DUPLICATE RECORDS - MASTER(ACTIVITY) RECORD IGNORED.

Reason:

A data set name can only be used once in the control statements. The control statement is skipped.

Action:

Correct the control statement(s) and resubmit the job.

DSN= dsname HAS DUPLICATE RECORDS - DEFAULTS RECORD IGNORED.

Reason:

A data set name can only be used once in the control statements. The control statement is skipped.

Action:

Correct the control statement(s) and resubmit the job.

** xxxxxxxx IS NOT A VALID KEYWORD

Reason:

Keyword xxxxxxxx is not a valid keyword.

Action:

Correct the control statement(s) and resubmit the job.

** xxxxxxxx IS NOT A VALID KEYWORD FOR OUTPUT

Reason:

Keyword xxxxxxxx is not valid for the output record format requested.

Action:

Correct the control statement(s) and resubmit the job.