EYUXUnnnn messages

EYUXUnnnn messages are issued by various utilities of the Kernel Linkage component, such as the online utility transaction (COLU) and the batched repository-update facility.

The COLU transaction is a diagnostic tool that should be used only at the request of customer support personnel; it is described in the CICSPlex® System Manager Problem Determination manual.

Note:
If the COLU transaction is issued from an MVS™ console, its messages (EYUXU0001-EYUXU0017) are returned to the console, rather than to a CICS® terminal.

The batched repository-update facility can be used to create and modify definitions in a CMAS data repository. Some of these messages describe problems with the batched repository input file, such as invalid commands or resource objects. For a description of the input file and its commands, see the CICSPlex System Manager Administration manual. For a list of valid resource objects and keywords, see CICSPlex System Manager Resource Tables Reference.

EYUXU0001I
command input
Explanation:

This message echoes the text of the command that was issued for the current COLU transaction.

System action:

COLU processing continues.

User response:

None.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0002I
Online Utility terminated with result.
Explanation:

The COLU transaction has completed processing, where:

result
Indicates the result of COLU processing, as one of the following:
no errors
The transaction completed successfully.
error(s)
The transaction encountered one or more error conditions.
System action:

The COLU transaction completes its processing.

User response:

If this message indicates there were errors, review any EYUXUnnnn messages issued before this one to determine the cause of the problem. Then correct the input to COLU and rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0003E
CICS command failed, RESP=respcode, RESP2=resp2code.
Explanation:

An EXEC CICS command returned an abnormal response, where:

command
Is the EXEC CICS command that caused the error, and is one of the following:
  • FREEMAIN
  • GETMAIN
  • SPOOLCLOSE
  • SPOOLOPEN
  • SPOOLWRITE
respcode
Is the EIBRESP code returned by CICS.
resp2code
Is the EIBRESP2 code returned by CICS.
System action:

The COLU transaction terminates.

User response:

Evaluate the RESP= and RESP2= values for the specified EXEC CICS command. Then correct the input to COLU, if possible, and rerun the transaction. If the problem persists, contact your IBM® Support Center with the text of this message.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUS

EYUXU0004E
No parmtype specified in the input stream.
Explanation:

A required parameter was missing from the input to COLU, where:

parmtype
Identifies the type of parameter that was missing as either a key word or data.
System action:

The COLU transaction terminates.

User response:

Review the syntax of the COLU transaction in the CICSPlex System Manager Problem Determination manual. Then correct the input to COLU and rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0005E
Invalid parmtype (parm) specified.
Explanation:

The COLU transaction was issued with an invalid parameter, where:

parmtype
Identifies the type of parameter that was invalid as either a component ID or a key word.
parm
Is the component ID or keyword parameter that was invalid.
System action:

The COLU transaction terminates.

User response:

Review the syntax of the COLU transaction in the CICSPlex System Manager Problem Determination manual. Then correct the input to COLU and rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0006E
cblock for compid is not available.
Explanation:

A control block that is required by COLU is not available for the specified component, where:

cblock
Identifies the required control block as either MODB or MOEB.
compid
Identifies the component that COLU was trying to access.

The component may not be initialized in the CMAS or MAS where COLU was issued.

System action:

The COLU transaction terminates.

User response:

Make sure the specified component is fully initialized and then rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0007E
Invalid number of keyword values for keyword parm.
Explanation:

An invalid number of values were specified with a keyword parameter on the COLU transaction, where:

parm
Is the keyword parameter that was invalid.
System action:

The COLU transaction terminates.

User response:

Review the syntax of the COLU transaction in the CICSPlex System Manager Problem Determination manual. Then correct the input to COLU and rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0009E
Invalid syntax in parameter parm.
Explanation:

A parameter was specified incorrectly on the COLU transaction, where:

parm
Is the parameter whose syntax was incorrect.
System action:

The COLU transaction terminates.

User response:

Review the syntax of the COLU transaction in the CICSPlex System Manager Problem Determination manual. Then correct the input to COLU and rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0010E
Missing keyword value in keyword parm.
Explanation:

A keyword parameter was specified on the COLU transaction without a required value, where:

parm
Is the keyword parameter that was missing a value.
System action:

The COLU transaction terminates.

User response:

Review the syntax of the COLU transaction in the CICSPlex System Manager Problem Determination manual. Then correct the input to COLU and rerun the transaction.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0011W
Requested service is not available from a addspace.
Explanation:

An option was requested on the COLU transaction that is not available from the type of address space where the transaction was issued, where:

addspace
Start of changeIdentifies the address space as a CMAS or a local MAS (LMAS),.End of change
System action:

The COLU transaction terminates.

User response:

Review the description of the COLU transaction in the CICSPlex System Manager Problem Determination manual for a list of options and the address spaces from which they are available.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0012E
An ABEND occurred.
Explanation:

An abend occurred during COLU transaction processing.

System action:

The COLU transaction terminates. User trace records are written to the CICS trace data set and a transaction dump is taken.

User response:

Collect the trace records and the transaction dump, and contact your IBM Support Center.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0013E
Options not supported for compid.
Explanation:

There are no COLU options available for the specified component of CICSPlex SM, where:

compid
Is the component ID that was specified.
System action:

The COLU transaction terminates.

User response:

Review the description of the COLU transaction in the CICSPlex System Manager Problem Determination manual for a list of options and the components for which they are available.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0014E
Utility processor for compid encountered an unexpected error.
Explanation:

A CICSPlex SM program that was called by the COLU transaction returned a Method Failure Response, where:

compid
Identifies the component that generated the error.
System action:

The COLU transaction terminates. User trace records are written to the CICS trace data set.

User response:

Collect the trace records and contact your IBM Support Center.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XLUT

EYUXU0015I
There are no allocated queue resources which satisfy your request
Explanation:

The COLU online utility transaction was issued with the QUE option and qualifying operands, but there are no allocated queues that match the specified criteria.

System action:

None.

User response:

None.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XL70

EYUXU0016E
Component and/or method ID are invalid
Explanation:

Either a component ID or a method ID was specified incorrectly on the COLU online utility transaction's QUE option.

System action:

None.

User response:

Reissue the COLU QUEUE transaction with a valid component or method ID.

For a list of valid CICSPlex SM component IDs, see the CICSPlex System Manager Problem Determination manual. Valid method IDs are supplied by customer support personnel, as needed.

Destination:

CICS terminal, SYSOUT

Module:

EYU0XL70

EYUXU0017E
Query queue environment method failed with a status of nn
Explanation:

The query queue environment method, which is used by the COLU online utility transaction's QUE option, failed, where:

nn
Is a numeric status code that identifies the problem.
System action:

A user trace record is written to the CICS trace data set. Additional messages relating to the problem might also be written to the job log.

User response:

Collect the following information and contact your IBM Support Center:

Destination:

CICS terminal, SYSOUT

Module:

EYU0XL70

EYUXU0200E
Failure action input file (dsname) - reason code (code)
Explanation:

A failure occurred during allocation processing of the specified batched repository input file, where:

action
Identifies the action being performed as either allocating or unallocating.
dsname
Is the name of the data set that was being processed.
code
Is the reason code returned from the MVS dynamic allocation call.
System action:

The batched repository run terminates.

User response:

Refer to the MVS Application Development Guide: Authorized Assembler Language Programs for an explanation of the reason code returned by dynamic allocation. Correct the problem and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBI

EYUXU0201E
Failure action input file (dsname) - return code (code)
Explanation:

A failure occurred during the input/output processing of the specified batched repository input file, where:

action
Identifies the action being performed as opening, reading, or closing.
dsname
Is the name of the data set that was being processed.
code
Is the return code from the MVS BSAM call.
Note:
A return code of zero (0) means an abend occurred during MVS input/output processing. When the batched repository-update facility intercepts an abend, a return code cannot be set.
System action:

The batched repository run terminates.

User response:

Check the job log of the appropriate CMAS for MVS messages related to the problem. Then refer to the MVS Messages and Codes manual for an explanation of those messages.

Correct the problem and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBI

EYUXU0202E
Insufficient storage to build type buffer
Explanation:

A buffer of the specified type, which is required for the batched repository facility, could not be created because of a GETMAIN failure, where:

type
Identifies the type of buffer that could not be created as either input or parser.
System action:

The batched repository run terminates.

User response:

Increase the region size of the CMAS under which the batched repository-update facility is running. The CMAS is indicated by the context of the BATCHREP view. Resubmit the job.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0203E
Method failure in (module) - response (respcode) - reason (rcode)
Explanation:

A failure occurred during execution of the specified CICSPlex SM module by the batched repository facility, where:

module
Is the name of the module that failed.
respcode
Is the response code returned by the module.
rcode
Is the reason code returned by the module.
System action:

The batched repository run terminates. User trace records are written to the CICS trace data set.

User response:

Collect the following information and contact your IBM Support Center:

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0204E
Utility parmtype (parmname) too long
Explanation:

The length of a parameter used as input to the batched repository facility was too long, where:

parmtype
Identifies the type of parameter as one of the following:
Type
Length
Command
7 characters or less
Object
8 characters or less
Keyword
12 characters or less
parmname
Is the name of the parameter that was too long.
System action:

If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Correct the input parameter and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0205E
Value clause missing following parameter (parmname)
Explanation:

No value was found for the specified parameter, where:

parmname
Is the name of the parameter for which no value was found.
System action:

If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Correct the parameter and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0206E
Invalid syntax following parameter (parmname)
Explanation:

In the batched repository input file, either a parameter was specified incorrectly, or there was no semicolon delimiter following the last parameter in a control statement.

parmname
Is the name of the parameter that was incorrect.
System action:

If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Correct the parameter and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0207E
Parser buffer error
Explanation:

The input stream exceeded the limits of the batched repository parser buffer. The most likely cause of this error is that a command was not properly delimited with a semicolon (;). The parser continues trying to build a command block until it encounters a command delimiter.

System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Check each line of command input for a delimiter. Correct any errors and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0208E
Invalid Context (context) for execution of (command)
Explanation:

The specified context is not appropriate for processing of the specified batched repository command, where:

context
Identifies the CMAS or CICSplex that was specified on the CONTEXT command. Note that if CONTEXT is used with no parameter, the local CMAS (that is, the CMAS under which the repository facility is running) is assumed.
command
Is the name of the command that could not be processed.
System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Check the last CONTEXT command before the command statement. Make sure it specifies an appropriate context (either the local CMAS or a CICSplex) for the command being processed. Correct any errors and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0209E
Maintenance point not active for Context (plexname)
Explanation:

The specified CICSplex was named as the context for subsequent commands. However, either the maintenance point CMAS for that CICSplex is not active, or the context does not name a CICSplex. Data repository records cannot be updated for a CMAS that is not active.

System action:

Processing of the current command terminates. Further processing is limited to syntax checking.

User response:

Make sure the CICSplex name was specified correctly on the CONTEXT command. If it was and you expected the maintenance point CMAS for that CICSplex to be active, investigate why it is not. Once the required CMAS is active, resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0210E
Invalid record attribute for batch input file (dsname)
Explanation:

Some attribute of the records in the specified batched repository input file is invalid, where:

attribute
Indicates whether it is the record length or the record format that is invalid. Input to the batched repository facility must be supplied as 80-byte records in a fixed blocked format.
dsname
Is the name of the data set that was being processed.
System action:

The batched repository run terminates.

User response:

Correct the input file and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBI

EYUXU0211E
Context (context name) not found
Explanation:

The context name specified on the CONTEXT command either is not the name of the local CMAS or is the name of a CICSplex that has not been defined to CICSPlex SM.

System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Make sure the specified context name is either the name of the local CMAS or the name of a CICSplex that has been defined to CICSPlex SM. Use the CPLEXDEF view to verify that the CICSplex has been defined to CICSPlex SM. Correct any errors and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0212E
Local CMAS is not Maintenance Point for Context (plexname)
Explanation:

The local CMAS (that is, the CMAS under which the repository facility is running) is not the maintenance point for the specified CICSplex.

System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Start of changeCorrect the parameter in error or connect to the appropriate CMAS and resubmit the batch stream for execution.End of change

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0213E
Invalid parmtype (parmname)
Explanation:

A parameter in the batched repository input file was specified incorrectly.

parmtype
Identifies the type of parameter as either command or object.
parmname
Is the name of the parameter that was invalid.
System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Correct the parameter and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBS

EYUXU0214E
Object (objname) may not be referenced by batch utility
Explanation:

The specified resource object is not one that can be processed by the batched repository facility, where objname identifies the resource object that was specified.

System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Remove all references to the specified object from the batched repository input file and resubmit the job. For a list of resource objects that can be processed by the batched repository facility, see the CICSPlex System Manager Administration manual.

Destination:

SYSOUT

Module:

EYU0XDBS

EYUXU0215E
Invalid value (parmvalue) following parameter (parmname)
Explanation:

A parameter value in the batched repository input file was specified incorrectly, where:

parmvalue
Is the value that was specified.
parmname
Is the name of the parameter for which the value is invalid.
System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Correct the parameter and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBS

EYUXU0216E
Required parameter (parmname) missing
Explanation:

A keyword parameter that is required by the batched repository facility was not supplied.

System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Refer to the CICSPlex System Manager Administration manual and the CICSPlex System Manager Resource Tables Reference. for a discussion of the parameters required by the batched repository facility. Then correct any errors and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBS

EYUXU0217E
Conflicting parameter (parmname) supplied
Explanation:

A parameter was specified in the batched repository input file that conflicts with another parameter, where: parmname is the name of the conflicting parameter.

System action:

Processing of the current command terminates. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Refer to the CICSPlex System Manager Administration manual and the CICSPlex System Manager Resource Tables Reference for a discussion of the parameters required by the batched repository facility. Remove the conflicting parameter from the batched repository input file, and resubmit the job.

Destination:

SYSOUT

Module:

EYU0XDBS

EYUXU0218I
Batch type request complete - Status (status) - Associated fields (fielda), (fieldb)
Explanation:

Processing of the specified batched repository request has been completed, where:

type
Identifies the type of request that was processed as one of the following: CREATE, UPDATE, LIST, DUMP, REMOVE, MAPLEFT, or MAPRIGHT.
status
Indicates the status of the request's completion.
fielda and fieldb
Start of changeAre fields which are in error when the staus is not OK. Additional fields are included in message EYUXU0240I which is a continuation of this message.End of change
System action:

Processing continues. However, a status which is not OK causes further processing to be limited to syntax checking.

User response:

If the status is OK, no action is required. Otherwise, correct the indicated condition and resubmit the batch stream for execution. Status codes other than OK depend on the resource table being manipulated and are self-explanatory. Please refer to the CICSPlex System Manager Resource Tables Reference manual for valid input.

Destination:

SYSOUT

Module:

EYU0XDBR

EYUXU0219E
Batch type request failed - Response (respcode) - Reason (rcode)
Explanation:

Processing of the specified batched repository request failed, where:

type
Identifies the type of request that failed as one of the following: CREATE, UPDATE, LIST, DUMP, or REMOVE.
respcode
Is the response code returned by the batched repository facility.
rcode
Is the reason code returned by the batched repository facility.
System action:

Further processing is limited to syntax checking. User trace records are written to the CICS trace data set.

User response:

Collect the following information and contact your IBM Support Center:

Destination:

SYSOUT

Module:

EYU0XDBR

EYUXU0220E
Invalid record key for update process
Explanation:

The requested repository record selected for UPDATE processing was not found on the data repository.

System action:

Further processing is limited to syntax checking.

User response:

Make sure the correct record was specified, and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBI

EYUXU0221E
Failure action Batch Utility Spool File - Reason (rcode)
Explanation:

A failure occurred while processing the batched repository output spool file, where:

action
Identifies the action being performed as either opening, writing, or closing.
rcode
Indicates the reason for the failure as one of the following:
  • Allocation Failure
  • Invalid Class Value
  • Invalid Output Record Length
  • Unidentified Node/User Combination
  • Storage GETMAIN Error
  • Storage FREEMAIN Error
  • Unsupported Language
  • Unsupported Function
  • UserId Missing
  • Node Missing
  • From Missing
  • Invalid Keep/Delete
  • Input/Output Missing
  • CICS SSI Already Enabled
  • No Subsystem Present
  • Interface Being Disabled
  • Interface Stopped
  • Data Set Not Open
  • Open Macro Failure
  • Internal Spool Error
  • VSAM SHOWCB Failure
  • JES Thread Unavailable
  • Spool In Use by Another Task
  • Spool In Use by Current Task
  • MVS Interface Failure
System action:

The batched repository run terminates.

User response:

Correct the condition indicated by rcode and resubmit the batched repository job.

Destination:

EYULOG

Module:

EYU0XDBO

EYUXU0222E
Parameter (parmname) invalid for cmd/obj (cmd/objname)
Explanation:

The indicated parameter is not valid for use during the current processing. If obj/cmd is 'object' the parameter is not valid with the resource table indicated by cmd/obj name. If obj/cmd is 'command' the parameter is valid for the resource table, but not valid during the command process indicated by cmd/objname.

System action:

If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Make sure the correct object or command was specified and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBS

EYUXU0223E
Command (cmdname) not valid for object (objname)
Explanation:

The indicated command is not valid for use when processing the indicated resource table.

System action:

If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Make sure the correct object or command was specified and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBF

EYUXU0224E
Unexpected end of file encountered
Explanation:

While processing the input stream, end-of-file was encountered before a command delimiter was detected.

System action:

Batch stream processing is terminated.

User response:

Make sure the last command is properly terminated, and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0225E
Duplicate parameter (parmname) encountered
Explanation:

While processing the input stream, a resource table parameter was encountered that had already been processed.

System action:

Processing of the current command is terminated. If the input file was being executed, further processing is limited to syntax checking. If the input file was being checked, the run continues.

User response:

Check for duplicate parameters in each command, and make sure all commands are properly terminated. Correct any errors and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0226E
A previous error has caused incomplete processing to occur.
Explanation:

An error which had occurred earlier in the input stream caused the batch utility to not fully process. This message is issued at end of process to insure users are aware of any error conditions which have occurred during execution run processing.

System action:

Processing terminates.

User response:

Examine output from batched repository job for prior messages indicating the cause of failure.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0227I
There is no data which satisfies your request.
Explanation:

A MAPLEFT or MAPRIGHT request was included in the batched repository input file, but the object that you asked to map does not exist. This message appears immediately after the MAPLEFT or MAPRIGHT statement in the batched repository output file.

System action:

Processing continues.

User response:

None.

Destination:

SYSOUT

Module:

EYU0XDBZ

EYUXU0228I
Invalid values encountered while formatting resource table
Explanation:

One or more invalid data values were encountered while processing a BATCHREP DUMP or LIST command.

System action:

Further processing is limited to syntax checking.

User response:

Invalid attribute values are formatted as "********". Correct any invalid values via the EUI, API, or BATCHREP UPDATE command, and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBR

EYUXU0229E
OUTPUT statement must be the first input to batched repository
Explanation:

If you include an OUTPUT control statement in the batched repository input stream, the OUTPUT statement must come first.

System action:

Start of changeThe batched repository run continues. Output will continue to be written to the original target.End of change

User response:

Place the OUTPUT statement at the beginning of the batched repository input stream.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0230E
OUTPUT must be followed by the keyword LISTING or DATASET
Explanation:

You specified a keyword other than LISTING or DATASET on the OUTPUT control statement. These are the only supported keywords.

System action:

The batched repository run terminates.

User response:

Correct the OUTPUT control statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0231E
OUTPUT DSNAME only supports parameters DSNAME and INQUOTES
Explanation:

You specified a parameter other than DSNAME or INQUOTES on an OUTPUT DSNAME control statement. These are the only valid parameters.

System action:

The batched repository run terminates.

User response:

Correct the OUTPUT control statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0232E
DSNAME does not specify a valid data set name
Explanation:

The DSNAME parameter did not specify a valid data set name. Data set names must not be more than 44 bytes long. They must consist of groups from 1 to 8 characters separated by full stops. DSNAME may include an optional member name placed following the data set name. The member name must be enclosed in parentheses and must not be more than 8 characters long. The data set name and member name of the batched repository output data set must not be the same as the data set name and member name of the batched repository input data set.

System action:

The batched repository run terminates.

User response:

Correct the DSNAME parameter of the OUTPUT statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0233E
INQUOTES must take the value YES or NO
Explanation:

You specified a value other than YES or NO as the value of the parameter INQUOTES.

System action:

The batched repository run terminates.

User response:

Correct the INQUOTES parameter on the OUTPUT control statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0234E
Failure action output file (dsname) - return code (code)
Explanation:

A failure occurred during the input/output processing of the specified batched repository output file, where:

action
Identifies the action being performed as opening, reading, or closing.
dsname
Is the name of the data set that was being processed.
code
Is the return code from the MVS BSAM call.
Note:
A return code of zero (0) means an abend occurred during MVS input/output processing. When the batched repository-update facility intercepts an abend, a return code cannot be set.
System action:

The batched repository run terminates.

User response:

Check the job log of the appropriate CMAS for MVS messages related to the problem. Then refer to the MVS Messages and Codes manual for an explanation of those messages.

Correct the problem and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBW

EYUXU0235E
Invalid record length nnn for batch output file
Explanation:

The record length (LRECL) for the output file used by the batched data repository is not 80 bytes.

System action:

The batched repository run terminates.

User response:

Use an output data set with 80 byte records.

Destination:

SYSOUT

Module:

EYU0XDBW

EYUXU0236E
Failure action output file (dsname) - reason code (code)
Explanation:

A failure occurred during allocation processing of the specified batched repository output file, where:

action
Identifies the action being performed as either allocating or unallocating.
dsname
Is the name of the data set that was being processed.
code
Is the reason code returned from the MVS dynamic allocation call.
System action:

The batched repository run terminates.

User response:

Refer to the MVS Application Development Guide: Authorized Assembler Language Programs for an explanation of the reason code returned by dynamic allocation. Correct the problem and resubmit the batched repository job.

Destination:

SYSOUT

Module:

EYU0XDBW

EYUXU0237E
Syntax error. Unbalanced quotes on BATCHREP statement
Explanation:

A batched repository parameter value began with a quote but did not end with a quote. If the first character (the one immediately following the left parenthesis) of a parameter value is a quote, then the last character (the one immediately preceding the right parenthesis) must also be a quote, and any imbedded quotes within the parameter value must occur in pairs.

System action:

The batched repository run terminates.

User response:

Correct the BATCHREP control statement

Destination:

SYSOUT

Module:

EYU0XDBP

EYUXU0238W
Invalid set-attributes have been ignored
Explanation:

The MP CMAS has shipped a Resource Assignment (RASGNDEF) to a CMAS running a lower level of CICSPlex SM, as part of repository synchronization. The RASGNDEF in question contains an Override string that identifies an attribute that is not applicable to the lower level CMAS.

System action:

The unknown attribute is ignored, but the lower level CMAS will issue an exception trace entry to identify the definition attribute that is being ignored. This message will be issued only once in the CMAS job step, regardless of the number of invalid set-attributes detected.

User response:

As the system is reporting an attribute that is not applicable to the lower level CMAS, then normally this message can be ignored. If there is any doubt as to the integrity of system resources after this message is issued, then collect the CMAS Auxiliary Trace Datasets and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU0XDOS

EYUXU0239W
Invalid filter-attributes have been modified
Explanation:

The MP CMAS has shipped a Resource Assignment (RASGNDEF) to a CMAS running a lower level of CICSPlex SM, as part of repository synchronization. The RASGNDEF in question contains a Filter string that identifies an attribute that is not applicable to the lower level CMAS.

System action:

The unknown attribute is modified internally to generate a FALSE condition in the lower level CMAS. An exception trace entry will be taken to identify the filter-attribute that has been changed. This message will be issued only once in the CMAS job step, regardless of the number of invalid filter-attributes detected.

User response:

The system is reporting an attribute test that is being modified to enable the filter to be executed. However, users should be aware that the modified test will be updated to produce an unconditional FALSE state. This means that resources that you would assume to be successfully installed may not now be defined at their target scopes - particularly if these invalid filter-attributes are part of a compound specification connected with the AND logical operator. If there is any doubt as to the integrity of system resources after this message is issued, then collect the CMAS Auxiliary Trace Datasets and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDOP

Start of change
EYUXU0240I
Additional associated fields (fielda), (fieldb), (fieldc), (fieldd).
Explanation:

This is an extension to message EYUXU0218I which gives up to two associated fields. This message can give up to four more associated fields. Refer to the explanation for EYUXU0218I for more information.

System action:

Refer to the explanation for EYUXU0218I for more information.

User response:

Refer to the explanation for EYUXU0218I for more information.

Destination:

SYSOUT

Module:

EYU0XDBR

End of change
EYUXU0241E
Invalid syntax for BATCHREP OPTION command.
Explanation:

A syntax error was encountered while parsing an OPTION command. The OPTION command has the following form:

OPTION type keyword ^keyword ...]

where:

OPTION
is the option type
keyword
are keywords whose form depends upon the option type being processed.
System action:

The batch repository run terminates.

User response:

Correct the BATCHREP control statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0242E
Invalid BATCHREP OPTION card type (type).
Explanation:

The OPTION command had an unrecognized type. The following option types are currently supported:

DUPREC
Sets processing option for duplicate record condition for the CREATE command.
System action:

The batch repository run terminates.

User response:

Correct the BATCHREP control statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0243E
Invalid keyword for OPTION (type) (keyword).
Explanation:

The OPTION command contained an invalid keyword , where

type
is the option card type
keyword
is the unrecognized keyword.
System action:

The batch repository run terminates.

User response:

Correct the BATCHREP control statement.

Destination:

SYSOUT

Module:

EYU0XDBM

EYUXU0244E
Generic keys are not allowed on remove.
Explanation:

A batched repository request was made to remove a record and a generic key was specified. That is, either a "+" or a "*" was specified in the key field. The request failed because remove acts only upon specific keys.

System action:

The batched repository-update request fails. Further processing is limited to syntax checking.

User response:

Correct and resubmit the batched repository request.

Destination:

SYSOUT

Module:

EYU0XDBX

Start of change
EYUXU0245E
Insufficient authority to access output file (dsname)
Explanation:

The issuer of the BATCHREP command stream is not authorized to write to the data set named in the OUTPUT command, where:

dsname
Is name of the output data set specified in the BATCHREP OUTPUT command.
System action:

The BATCHREP stream is aborted.

User response:

Update the OUTPUT command to specify the name of a data set that the user has the authority to write to.

Destination:

SYSOUT

Module:

EYU0XDBM

End of change [[ Contents Previous Page | Next Page Index ]]