EYUXDnnnn messages

EYUXD0001I
Data Repository initialization complete
Explanation:

The Data Repository component has been successfully initialized.

System action:

CMAS initialization continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN, EYU3XDIN

EYUXD0002I
Start of changeaction CONTEXT(plexname) MAJOR_ID(deftype) MAJOR_NAME(defname) MAJOR_VER(defver) MINOR_ID(deftype) MINOR_NAME(defname) MINOR_VER(defver) By User(userid) System(sysname) Date(dddyy) Time(hh.mm.ss)End of change
Explanation:

A change was made to the data repository; this message serves as a record of the change, where:

action
The type of change that was made, as one of the following: ADD, UPDATE, DELETE, GENERIC DELETE, or INTERNAL DELETE.

A generic delete is one that used a generic name (including the characters + or *) to affect multiple instances of a definition. An internal delete is one that was made as a result of another delete to maintain the referential integrity of the data repository.

plexname
The name of the CICSplex that was affected by the change.
deftype
The type of definition that was changed, which corresponds to an administrative definition such as CPLXCMAS or MONDEF.
defname
The name of the definition that was changed.
Start of changedefverEnd of change
Start of changeThe version of the definition that was changed.End of change
userid
The ID of the user who made the change.
sysname
The name of the CICS® system where the change was made.
dddyy
The date on which the change was made, in Julian format.
hh.mm.ss
The time at which the change was made.
System action:

None.

User response:

If this message accurately reflects a change that was made by a user, no action is required. If, however, this message contains information that you consider invalid, contact your IBM® Support Center.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0XDCR

EYUXD0003I
Data Repository termination complete
Explanation:

The Data Repository component has been terminated.

System action:

CMAS termination continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDTM, EYU3XDTM

EYUXD0004I
Start of changeImport of PLEX(plexname) from (cmasid) successfulEnd of change
Start of change
Explanation:

A request was issued to add a CMAS to the management of a CICSplex, where:

plexname
Identifies the name of the CICSplex being imported.
cmasid
Identifies the maintenance point CMAS from which CICSplex information was being imported.
End of change
System action:

This message is written to the EYULOG of the CMAS that was being added. The definitions required to manage the specified CICSplex are added to the data repository; the CMAS can now participate in the management of the CICSplex.

User response:

No action is required.

Destination:

EYULOG

Module:

EYU0XDIP

EYUXD0005I
Managed Object Services initialization has started
Explanation:

The Managed Object Services subcomponent of the Data Repository component is being initialized.

System action:

Initialization of Managed Object Services continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDIN

EYUXD0006I
Managed Object Services initialization complete
Explanation:

The Managed Object Services subcomponent of the Data Repository component has been successfully initialized.

System action:

CMAS initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDMI

EYUXD0007I
Managed Object Services termination requested
Explanation:

The Managed Object Services subcomponent of the Data Repository component is being terminated.

System action:

Termination of Managed Object Services continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDMT

EYUXD0008I
Managed Object Services termination complete
Explanation:

The Managed Object Services subcomponent of the Data Repository component has been terminated.

System action:

CMAS termination continues.

User response:

None

Destination:

EYULOG

Module:

EYU0XDMT

EYUXD0009E
I/O error on repository for CMAS cmasid Offline Maintenance Required. CMAS will terminate.
Explanation:

An input/output error has occurred in the repository.

System action:

CMAS terminates.

User response:

Restore repository from backup.

Destination:

EYULOG

Module:

EYU0XDKL

EYUXD0010E
CICSPlex SM Version nnnn Does not Match Repository Version yyyy. CMAS Terminates.
Explanation:

During initialization of a version nnnn CMAS, CICSPlex® SM detected a version yyyy Data Repository.

System action:

CMAS initialization terminates.

User response:

Ensure that the correct Data Repository (EYUDREP) is being used with the CMAS. If the CMAS has been migrated to a later Version of CICSPlex SM, ensure that the Data Repository has been converted to the appropriate TARGETVER with EYU9XDUT. For details of EYU9XDUT, see the CICSPlex SM Setup manual.

Destination:

Console, Job Log, EYULOG

Module:

EYU0XDIN

EYUXD0011E
The Data Repository is full; all further modifications will fail. The repository must be expanded.
Explanation:

An attempt to update the Data Repository failed due to a NOSPACE condition.

System action:

The CMAS continues to run, but the process that initiated the Data Repository update terminates.

User response:

To successfully update the Data Repository, stop the CMAS and reorganize or expand the Data Repository.

Destination:

Console, job log, EYULOG

Module:

EYU0XDAI, EYU0XDCA, EYU0XDCR, EYU0XDIP, EYU0XDRS, EYU0XDUI

Start of change
EYUXD0012E
An error has occurred while performing special repository recovery for CICSplex (plexname). Special recovery processing is status.
Explanation:

During special repository update processing for, an error was detected while processing the records for a CICSplex, where plexname is the name of the CICSplex. Depending upon the type of error, the update process may continue or end, as indicated by status, which indicates the status of the special process as either:

System action:

CMAS repository update is terminated for the named CICSplex. Processing either continues with the update of the next CICSplex or terminates, returning to normal CMAS initialization.

User response:

The next time the CMAS is restarted, this processing will again be attempted. If error messages persist and the CMAS is not the maintenance point (MP) for the CICSplex, use the TSO End User Interface (EUI), with the CONTEXT set to the CICSplex's MP CMAS, to manually remove and re-add the CMAS from the CICSplex. If the CMAS is the MP for the CICSplex, collect the CMAS job output and auxtrace data set(s) and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDRR

End of change
EYUXD0013E
Error converting Repository for CMAS cmasname from non-recoverable to recoverable. CMAS Terminates.
Explanation:

During CICSplex add or remove processing, an error occurred while changing the status of the repository from non-recoverable to recoverable, where:

cmasname
is the name of the CMAS.
System action:

The CMAS is terminated.

User response:

Before attempting to restart the CMAS, collect the CMAS job output and auxtrace dataset(s). restart the CMAS with a COLD start. If the failure persists, contact your IBM Support Center., providing the job output and trace dataset(s).

Destination:

Console, job log, EYULOG

Module:

EYU0XDIP, EYU0XDDP

Start of change
EYUXD0014I
Special repository recovery processing has started.
Explanation:

During initialization of the data repository component in a CMAS, one or more CICSplexes defined to the CMAS's repository needed to be updated.

System action:

CMAS repository update is performed.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDRR

End of change
Start of change
EYUXD0015I
Special repository recovery processing has ended.
Explanation:

During initialization of the data repository component in a CMAS, one or more CICSplexes defined to the CMAS's repository needed to be updated.

System action:

CMAS initialization continues

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDRR

End of change
EYUXD0016W
CSD definition for file EYUDREPN is missing or not installed. CMAS initialization continues.
Explanation:

During CMAS initialization, Data Repository initialization detected that the alternate file definition for the Data Repository file, EYUDREPN, was not installed.

System action:

CMAS initialization continues without use of the EYUDREPN file definition. Start of changeThis has an adverse effect on the performance of CICSplex add and remove processing.End of change

User response:

Start of changeEnsure that the IBM-supplied CMAS CSD group EYU310G0 is installed on the CMAS.End of change

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0017E
The Data Repository records for CICSplex (cicsplex) appear to be corrupted. Resyncronization with the Maintenance Point CMAS (cmasname) is required.
Explanation:

While this CMAS was processing Data Repository updates for a CICSplex that were shipped from the maintenance point CMAS for the CICSplex, an unrecoverable error was encountered, where:

cicsplex
is the name of the CICSplex
cmasname
is the name of the maintenance point CMAS.
System action:

The error is noted internally, a dump is taken, and CMAS execution continues. However, no further updates to this CMAS's repository for this CICSplex is processed.

User response:

All MASs connected to this CMAS should be terminated, and the CMAS should then be restarted. This results in this CMAS performing repository syncronization with the maintenance point CMAS. Because the system has noted that this CMAS's repository is corrupted for this CICSplex, the CICSplex is removed from and then re-added to this CMAS's repository as part of the repository syncronization process.

Destination:

Console, job log, EYULOG

Module:

EYU0XDRS

Start of change
EYUXD0018I
Enhanced MOS initialization in progress.
Explanation:

The enhanced MOS initialization phase of CMAS initialization has started.

System action:

CMAS initialization continues.

User response:

No action is needed. The message is for information only.

Destination:

EYULOG

Module:

EYU0MOIT

End of change
Start of change
EYUXD0019I
Enhanced MOS initialization complete.
Explanation:

The enhanced MOS initialization phase of CMAS initialization completed successfully.

System action:

CMAS initialization continues.

User response:

No action is needed. The message is for information only.

Destination:

EYULOG

Module:

EYU0MOIT

End of change
Start of change
EYUXD0020E
Enhanced MOS initialization failed.
Explanation:

A failure occurred during the enhanced MOS initialization phase of CMAS initialization.

System action:

The system terminates.

User response:

Examine the job log for messages issued earlier which might indicate the reason for the failure. Examine any dumps and traces which have been produced. If no reason for the failure can be found, contact your IBM support centre.

Destination:

EYULOG

Module:

EYU0MOIT

End of change
Start of change
EYUXD0021I
Enhanced MOS termination in progress.
Explanation:

The enhanced MOS termination phase of CMAS termination has started.

System action:

CMAS termination continues.

User response:

No action is needed. The message is for information only.

Destination:

EYULOG

Module:

EYU0MOIT

End of change
Start of change
EYUXD0022I
Enhanced MOS termination complete.
Explanation:

The enhanced MOS termination phase of CMAS termination completed successfully.

System action:

CMAS termination continues.

User response:

No action is needed. The message is for information only.

Destination:

EYULOG

Module:

EYU0MOIT

End of change
Start of change
EYUXD0024E
Field (field) value (value) has been deleted from modification string.
Explanation:

A modification string contains a field which does not exist at the target end. This message can be issued by the CICSPlex SM API or the batched repository-update facility. This message can arise when a resource assignment is installed in multiple CMASs which are at different levels of CICSPlex SM and the field that is to be modified is unknown at the lower CICSPlex SM levels.

System action:

The modification string is installed with the fields removed that are unknown at this release.

User response:

Correct the error in the input string.

Destination:

EYULOG

Module:

EYU0MOSS

End of change
Start of change
EYUXD0025E
Field (fielda) requires field (fieldb) in MAL(mal).
Explanation:

This message is issued by the CICSPlex SM batched repository-update facility. Fields fielda and fieldb are both required for the creation of a base table. However the batched repository input contains only fielda.

System action:

The batched repository-update facility request fails.

User response:

Correct the error in the input and reissue the request.

Destination:

EYULOG

Module:

EYU0MOMB

End of change
Start of change
EYUXD0026E
Field (fielda) mutually exclusive with (fieldb) in MAL(mal).
Explanation:

This message is issued by the CICSPlex SM batched repository-update facility. Either fielda or fieldb may be specified for the creation of a base table but not both. However the batched repository input contains both fielda and fieldb.

System action:

The batched repository-update facility request fails.

User response:

Correct the error in the input and reissue the request.

Destination:

EYULOG

Module:

EYU0MOMB

End of change
Start of change
EYUXD0027E
MAL (mal )cannot be transformed. Metadata not available.
Explanation:

A transformation between two systems failed. This is a CICSPlex SM internal error.

System action:

A MAL is a request to run a program in another MAS or CMAS. The program request is sent to its destination without being transformed. If associated resource tables have changed, the program might fail.

User response:

Contact your IBM support centre.

Destination:

EYULOG

Module:

EYU0MOX2

End of change
EYUXD0030W
The performance of the operation on the data repository records for CICSplex cicsplex may be degraded due to the recoverable attribute of EYUDREPN.
Explanation:

The EYUDREPN file has taken on the recoverable attribute of the data repository data set. The result is a degradation of performance (logging will occur) on the data repository records when adding or deleting a CICSplex.

EYUDREPN's recovery definition change from non-recoverable to recoverable could have occurred in one of two ways:

  1. The Backup While Open (BWO) option was specified for the data repository data set associated with EYUDREP in the ICF catalog via the IDCAMS DEFINE CLUSTER definition. IDCAMS marks the EYUDREP data set as recoverable. Thus, when the EYUDREPN file name is associated with the EYUDREP data set, EYUDREPN is marked as recoverable. The ICF catalog definition takes precedence over the EYUDREPN RDO definition.
  2. EYUDREPN RDO definition was copied to a user group and RECOVERY(NONE) was modified.
System action:

CICSPlex SM processing continues. However, because EYUDREPN was defined as recoverable, the operation on the data repository records may be degraded.

User response:

To make the data repository eligible for backup while open, you must change the default RDO EYUDREP definition by copying the RDO EYUDREP definition to a user group and specifying the following keywords:

where nn is a number between 1 and 99.

This definition change marks the file EYUDREP as recoverable and any data set, while associated with the EYUDREP file name, is marked as recoverable.

Requesting BWO for the CICSPlex SM data repository data set via the IDCAMS DEFINE CLUSTER definition within the ICF catalog is not supported.

You should not change the recovery options of the EYUDREPN FILE definition.

Destination:

job log, EYULOG

Module:

EYU0XDDP, EYU0XDIP

Start of change
EYUXD0031E
Capability mismatch(relationship) for table(rtnum/rtname) (Service=servlevel). Local=lver/lsub : Remote=rver/rsub.
Explanation:

The service and maintenance level of a resource table is incompatible with the partner system where:

relationship
is the relationship between the service and maintenance levels of the local and remote systems and can be::
HIGH
where the partner system is at a higher level than the local system.
LOW
where the partner system is at a lower level than the local system.
rtnum/rtname
is the number and name of the CICSPlex SM resource table.
servlevel
is the service and maintenance level of the resource table as defined in the local CMAS.
lver/lsub
is the local version and subversion of the resource table.
rver/rsub
is the remote version and subversion of the resource table.

The partner name is given in a later message, which is EYUCL0130E if the partner is a MAS, or EYUCP0022E if the partner is a CMAS.

System action:

Information about the system action is given in a later message, either EYUCL0130E or EYUCP0022E.

User response:

For CMAS-to-CMAS connections, the maintenance point CMAS must not be at a lower level than the non-maintenance point CMAS. Restart one of the CMASs with a version of the CICSPlex SM load libraries that is at a maintenance level compatible with the other CMAS.

For CMAS-to-MAS connections, the CMAS must not be at a lower level than the MAS. Restart either the MAS or the CMAS with a version of the CICSPlex SM load libraries that is at a maintenance level compatible with the other system.

Notes:
  1. This message can be issued even though both systems are using the same CICSPlex SM load libraries. This can occur if one system was started before maintenance was applied to the libraries, and the other system was started afterwards. In this case, the earlier of the two systems must be restarted.
  2. If a non-maintenance point CMAS is restarted with CICSPlex SM load libraries at a higher maintenance level, ensure that this will not cause the non-maintenance point CMAS to be at a higher maintenance level than its related maintenance point CMAS.
  3. If a MAS has failed to connect to the CMAS because of this error, and you restart the CMAS , the MAS agent must be restarted (for example by the COLM transaction).
Destination:

Console, job log, EYULOG

Module:

EYU0MOCS

End of change
Start of change
EYUXD0032E
Import of PLEX(plexname) from (cmasid) failed
Explanation:

A request was issued to add a CMAS to the management of a CICSplex, where:

plexname
Identifies the name of the CICSplex being imported.
cmasid
Identifies the maintenance point CMAS from which CICSplex information was being imported.
System action:

This message is written to the console and to the job log and EYULOG of the CMAS that was being added. If the add request was made through the TSO EUI, message EYUEI0558E will be received. If the add request was made through the WUI, messages EYUVC1231E and EYUVC1272I will be received.

User response:

If the cause of the problem cannot be determined by the messages displayed where the add was attempted, collect the complete job output and auxtrace data sets from both the maintenance point CMAS and the CMAS being added, and contact your IBM support center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIP

End of change
Start of change
EYUXD0034I
Special one time removal of Topology resource maps from the data repository for APAR (PM16527) has started.
Explanation:

The Topology resource maps removal process has started.

System action:

The Topology resource maps are removed from the data repository of the CMAS.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

End of change
Start of change
EYUXD0035I
Special one time removal of Topology resource maps from the data repository for APAR (PM16527) is being performed under file definition (<filedef>).
Explanation:

The Topology resource maps are removed when <filedef> indicates which data repository file definition is being used during the process. If EYUDREPN is specified, then the removal is performed without journaling, decreasing the removal processing time. If EYUDREP is specified, then EYUDREPN is not used during the removal process and journaling takes place.

System action:

The Topology resource maps are removed from the data repository of the CMAS.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

End of change
Start of change
EYUXD0036I
Special one time removal of Topology resource maps from the data repository for APAR (PM16527) has been completed.
Explanation:

The Topology resource maps removal process has completed successfully.

System action:

CMAS initialization continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

End of change
Start of change
EYUXD0037E
Special one time removal of Topology resource maps from the data repository for APAR (PM16527) has encountered errors switching back to file definition (EYUDREP). The CMAS is being terminated.
Explanation:

The Topology resource maps removal process has encountered an error switching back to the normal data repository file definition EYUDREP. The CMAS will terminate.

System action:

After issuing the message, the CMAS will request a system dump. The title of the dump will resemble the following example:

EYU0XZPT Dump,<jobname>,<cmasname>,<lpar>,CMAS,XLEV,<tasknum>,
         TRAC,EYU0XDIN,<mm/dd/yy>,<hh:mm:ss>

After the dump is requested, the CMAS will terminate.

User response:

Collect the complete job output, auxtrace data sets, and the dump from the CMAS, and then restart the CMAS. If the subsequent start of the CMAS fails again, collect the same documentation from the restart and then contact your IBM support center, providing the collected documentation.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

End of change
EYUXD0101E
Data Repository initialization failed.
Explanation:

The Data Repository component could not be initialized.

System action:

CMAS initialization terminates. A user trace record is written to the CICS trace data set.

User response:

Check the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN, EYU3XDIN

EYUXD0103E
Data Repository termination failed.
Explanation:

An error occurred while attempting to terminate the Data Repository component.

System action:

CMAS termination continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XDTM, EYU3XDTM

EYUXD0104E
Data Repository initialization failed. Repository Not Defined.
Explanation:

The Data Repository component could not be initialized because the DD statement for EYUDREP was missing or invalid.

System action:

CMAS initialization terminates.

User response:

Make sure the DD statement for EYUDREP is properly specified in the CMAS startup JCL. Restart the CMAS.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0105E
Data Repository initialization failed. Cannot Open File.
Explanation:

The Data Repository component could not be initialized because the VSAM file could not be opened.

System action:

CMAS initialization terminates.

User response:

Make sure the VSAM file definition is properly specified in the CMAS startup JCL. Restart the CMAS.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0106E
Data Repository initialization failed. Invalid File Attributes.
Explanation:

The Data Repository component could not be initialized because the VSAM file attributes are invalid.

System action:

CMAS initialization terminates.

User response:

Make sure the file is a KSDS data set, with a key length of 64, a key position of 0, and attributes of ADD, UPDATE, DELETE, BROWSE, and READ.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0107E
Data Repository initialization failed. SYSID Mismatch, Repository SYSID=sysid1, CICS SYSID=sysid2.
Explanation:

The Data Repository component could not be initialized because the SYSID specified in the EYU9XDUT repository initialization program does not match the SYSID of the CMAS to which it is connecting.

System action:

CMAS initialization terminates.

User response:

Correct the SYSID parameter in either the EYU9XDUT program or the CMAS startup job, and then restart the CMAS.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0108E
Data Repository initialization failed. CMAS name cmasid not defined on repository.
Explanation:

The Data Repository component could not be initialized because the CMAS name does not match a CMAS specified in the EYU9XDUT repository initialization program.

System action:

CMAS initialization terminates.

User response:

Correct the CMAS name on the startup job, and then restart the CMAS.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0109E
Unable to load EYUTXDMD Module
Explanation:

The Managed Object Services initialization routine was unable to perform an OS LOAD for a required module, EYUTXDMD.

System action:

CMAS initialization terminates.

User response:

Verify that module EYUTXDMD exists in the STEPLIB for the CMAS startup job, then resubmit the job.

Destination:

Console, job log, EYULOG

Module:

EYU0XDMI

EYUXD0110E
Managed Object Service initialization failed
Explanation:

The Managed Object Services subcomponent of the Data Repository component could not be initialized.

System action:

CMAS initialization terminates.

User response:

Check the job log for EYUXD01nn messages issued before this one to determine the cause of the problem. If the problem persists, contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDMI

EYUXD0111E
Managed Object Service termination failed
Explanation:

The Managed Object Services subcomponent of the Data Repository component could not be properly terminated.

System action:

Data Repository termination continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XDMT

EYUXD0112I
API initialization has started
Explanation:

The application programming interface (API) subcomponent of the Data Repository component is being initialized.

System action:

Initialization of the API continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDIN

EYUXD0113E
Data repository initialization failed. System log must not be type dummy.
Explanation:

The data repository component could not be initialized because the CICS system log DFHLOG has been defined as being a dummy log. In order to maintain data integrity on the CICSPlex SM data repository a fully functioning CICS system log is required.

System action:

CMAS initialization terminates.

User response:

Follow the CICS procedures for setting up the system log DFHLOG.

Destination:

Console, job log, EYULOG

Module:

EYU0XDIN

EYUXD0601I
Successful CMASDEF CMASNAME=cmasid SYSID=sysid TIMEZ=x ZONEO=nn DAYLSV=option
Explanation:

A repository batch header record for the specified CMAS has been successfully formatted. The parameters are shown as they were specified in the EYU9XDUT repository initialization program, where:

cmasid
Identifies the CMAS for which the data repository was defined.
sysid
Is the CICS system ID of the CMAS.
x
Is a time zone code, from B - Z.
nn
Is a time zone offset in minutes, from 00 - 59.
option
Indicates whether daylight savings time is in effect, as Y or N.
System action:

The data repository (EYUDREP) is ready for CMAS initialization.

User response:

None.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0602E
SYSPRINT must be specified.
Explanation:

The SYSPRINT DD statement for the CMAS data repository was missing or invalid.

System action:

Data repository initialization terminates.

User response:

Make sure a valid SYSPRINT DD statement is included in the data repository initialization routine, and then resubmit the job.

Destination:

Console, job log, EYULOG

Module:

EYU9XDUT

EYUXD0603E
SYSPRINT could not be opened.
Explanation:

The SYSPRINT file specified in the data repository initialization routine could not be opened.

System action:

Data repository initialization terminates.

User response:

Make sure the specified printer is online and available, and then resubmit the job.

Destination:

Console, job log, EYULOG

Module:

EYU9XDUT

EYUXD0604E
EYUDREP VSAM file must be specified. CMASDEF Init terminated.
Explanation:

The EYUDREP DD statement for the CMAS data repository was missing or invalid.

System action:

Data repository initialization terminates.

User response:

Make sure a valid EYUDREP DD statement is included in the data repository initialization JCL.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0605E
Invalid parm length SYSID=status CMASNAME=status TIMEZONE=status ZONEOFFSET=status DAYLIGHT=status. CMASDEF Init terminated.
Explanation:

The length of one of the parameters specified for the EYU9XDUT repository initialization program was invalid, where:

status
Identifies the status of each parameter as:
ERR
The parameter was in error.
OK
The parameter was correctly specified.
System action:

Data repository initialization terminates.

User response:

Correct the length of the parameters in error, as follows:

SYSID=
1- to 4-characters.
CMASNAME=
1- to 8-characters.
TIMEZONE=
1-character.
ZONEOFFSET=
2-characters.
DAYLIGHT=
1-character.
Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0606E
Invalid parm data SYSID=status CMASNAME=status TIMEZONE=status ZONEOFFSET=status DAYLIGHT=status. CMASDEF Init terminated.
Explanation:

One of the parameters specified for the EYU9XDUT repository initialization program was invalid, where:

status
Identifies the status of each parameter as:
ERR
The parameter was in error.
OK
The parameter was correctly specified.
System action:

Data repository initialization terminates.

User response:

Correct the parameters in error, as follows:

SYSID=
1- to 4-character CICS system ID of the CMAS.
CMASNAME=
1- to 8-character name of the CMAS.
TIMEZONE=
1-character time zone code, from B--Z.
ZONEOFFSET=
2-character time zone offset in minutes, from 00--59.
DAYLIGHT=
Y or N, to indicate whether daylight savings time is in effect.
Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0607E
CMASNAME=cmasid 1st position invalid. CMASDEF Init terminated.
Explanation:

The first character of the CMASNAME= parameter as specified for EYU9XDUT was invalid. The first character must be one of the following: A-Z a-z @ $ or #.

System action:

Data repository initialization terminates.

User response:

Correct the parameter and then resubmit the job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0608E
EYUDREP contains at least one(1) record. CMASDEF Init terminated.
Explanation:

The data repository could not be initialized because it already contains at least one record.

System action:

Data repository initialization terminates.

User response:

Initialize EYUDREP with the IDCAMS utility, using ‘DELETE dataset name,PURGE,ERASE’ followed by the DEFINE CLUSTER parameters. Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0609E
EYUDREP Relative Key Position error. CMASDEF Init terminated.
Explanation:

The EYUDREP relative key position was invalid.

System action:

Data repository initialization terminates.

User response:

Initialize EYUDREP with the IDCAMS utility, using KEYS(64,0). Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0610E
EYUDREP KEYLEN must be (nn). CMASDEF Init terminated.
Explanation:

The EYUDREP relative key length was invalid.

System action:

Data repository initialization terminates.

User response:

Initialize EYUDREP with the IDCAMS utility, using KEYS(64,0). Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0611I
Error is terminating execution
Explanation:

An error is causing the data repository initialization routine to terminate. One or more EYUXDnnnn messages issued before this one describe the error.

System action:

Data repository initialization terminates.

User response:

Follow the instructions associated with the EYUXDnnnn messages issued to SYSOUT.

Destination:

Console, job log, EYULOG

Module:

EYU9XDUT

EYUXD0612E
VSAM Error Processing EYUDREP Return Code=code Feedback=chars MACRO=macro Mode=mode. CMASDEF Init terminated.
Explanation:

This message describes a VSAM error encountered during data repository processing.

System action:

Data repository initialization terminates.

User response:

Refer to the VSAM documentation for a description of the specified error and follow the instructions given there for correcting the problem. Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0613E
SYSID= cannot be binary zeroes. CMASDEF Init terminated.
Explanation:

The SYSID= parameter specified for EYU9XDUT was invalid; it contained binary zeroes.

System action:

Data repository initialization terminates.

User response:

Correct the SYSID= parameter by specifying the 1- to 4-character CICS system ID of the CMAS. Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0614E
Invalid KEYWORD SYSID=status CMASNAME=status TIMEZONE=status ZONEOFFSET=status DAYLIGHT=status. CMASDEF Init terminated.
Explanation:

One of the keywords specified for the EYU9XDUT repository initialization program was invalid, where status identifies the status of each keyword as:

ERR
The keyword was in error or was not specified.
OK
The keyword was correctly specified.
System action:

Data repository initialization terminates.

User response:

Correct the keywords in error, as follows:

Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0615E
NEWREP VSAM file must be specified. CMASDEF Init terminated.
Explanation:

The NEWREP DD statement for the CMAS data repository was missing or invalid.

System action:

Data repository initialization terminates.

User response:

Make sure a valid NEWREP DD statement is included in the data repository initialization JCL.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0700E
Invalid TARGETVER= value, must be numeric
Explanation:

The TARGETVER= parameter specified for the EYU9XDUT repository initialization program was invalid. The TARGETVER= value must be a numeric that represents a version of CICSPlex SM. For example, TARGETVER=0230 represents CICSPlex SM for CICS Transaction Server for z/OS, Version 3 Release 1.

System action:

The data repository is not converted.

User response:

Correct the TARGETVER= parameter and then resubmit the job.

Destination:

SYSOUT

Module:

EYU9XDUT

EYUXD0701E
VSAM Error Processing EYUDREP Return Code=code Feedback=chars MACRO=macro.
Explanation:

This message describes a VSAM error encountered during the data repository conversion process.

System action:

The data repository conversion process terminates.

User response:

Refer to the VSAM documentation for a description of the specified error and follow the instructions given there for correcting the problem. Then resubmit this job.

Destination:

SYSOUT

Module:

EYU9XDU1

EYUXD0702I
Repository successfully converted.
Explanation:

The EYU9XDUT repository initialization program successfully converted the data repository to the version of CICSPlex SM specified by the TARGETVER= parameter.

System action:

None.

User response:

None.

Destination:

SYSOUT

Module:

EYU9XDU1

EYUXD0703E
Internal conversion error.
Explanation:

The EYU9XDUT repository initialization program encountered a problem while attempting to convert the data repository to a new version of CICSPlex SM.

System action:

The data repository conversion process terminates with a 2048 abend. A system dump is produced.

User response:

Collect the dump output and contact your IBM Support Center.

Destination:

SYSOUT

Module:

EYU9XDU1

EYUXD0704E
DDNAME NEWREP key length incompatible with target version.
Explanation:

While attempting to convert the data repository, the EYU9XDUT utility determined that the target data repository specified in the NEWREP DD statement has a key length that is incompatible with the version of CICSPlex SM specified in the TARGETVER parameter.

System action:

The EYU9XDUT utility terminates.

User response:

Verify that the desired CICSPlex SM version is specified in the TARGETVER parameter. If it is, verify that the correct data set is specified on the NEWREP DD statement and that the data set is defined with the appropriate key length for the target version. Refer to the CICS Transaction Server for z/OS® Installation Guide manual for key length information.

Destination:

SYSOUT

Module:

EYU9XDU1

EYUXD0705E
DDNAME EYUDREP record nnnnn length incompatible with target repository.
Explanation:

While attempting to convert the data repository, the EYU9XDUT utility encountered a record whose length, after conversion, would exceed the maximum record length for the target data repository, where nnnnn is the number of the record.

System action:

The specified record is not updated or added to the target data repository. The EYU9XDUT utility continues processing.

User response:

Ensure that the attributes of the target data repository are correct for version of CICSPlex SM specified in the TARGETVER parameter. Refer to the CICS Transaction Server for z/OS Installation Guide manual for sample JCL containing the appropriate DEFINE CLUSTER information.

Destination:

SYSOUT

Module:

EYU9XDU1

Start of change
EYUXD0706W
DDNAME NEWREP nnnnn records were bypassed.
Explanation:

While attempting to convert the data repository, the EYU9XDUT utility encountered some records that will not be written to the new target data repository, where nnnnn is the number of the record(s) bypassed.

System action:

The bypassed record(s) are not added to the new target data repository. The EYU9XDUT utility continues processing with a return code of 4. The bypassed records are not correct for the version of CICSPlex SM specified in the TARGETVER parameter and have been printed to the //BYPASS DD statement.

User response:

This may not be a problem situation. If you suspect an error has occurred collect your EYUDREP and NEWREP data repositories, the job log output from the EYU9XDUT batch utility, and contact your IBM support center.

Note:
If you specify a TARGETVER that is less than the VERSION of your current EYUDREP, records may be bypassed because they are not supported on the lower level of CICSPlex SM as specified by the TARGETVER parameter. In this case the message is normal and can be expected. In other cases it is not and should be investigated.
Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0707E
BYPASS DD statement must be specified. TARGETVER BYPASS DD statement must be specified. TARGETVER init terminated.
Explanation:

The BYPASS DD statement for the CMAS data repository was missing or invalid.

System action:

Data repository initialization terminates.

User response:

Make sure a valid BYPASS DD statement is included in the data repository initialization JCL. It is required when PARM=('TARGETVER=xxxx') is specified as input.

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0708I
CRESxxxx resource table nnnnn records not converted.
Explanation:

CRESxxxx is a CICSPlex SM topology manager object that describes instances of a resource within a CICS system. They will not be converted by the EYU9XDUT batch utility. These object types will be recreated when a MAS joins to the CMAS. CRESxxxx resource descriptions can be found in the CICSPlex System Manager Resource Tables Reference

System action:

Data repository initialization continues.

User response:

None

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0709E
The TARGETVER value (xxxx) is greater than the CICSPlex SM version of EYU9XDUT (yyyy)
Explanation:

To ensure that the data repository conversion works properly, it is required that the value provided on the PARM=('TARGETVER=xxxx') statement cannot be greater than the version of EYU9XDUT being loaded from the SEYUAUTH dataset.

System action:

Data repository initialization terminates.

User response:

Ensure that your STEPLIB DD statement is referencing the correct SEYUAUTH dataset.

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0710E
The CICSPlex SM version of the EYUDREP (xxxx) is greater than the CICSPlex SM version of EYU9XDUT (yyyy)
Explanation:

To ensure that the data repository conversion works properly, it is required that the version of the EYUDREP (data repository) cannot be greater than the version of EYU9XDUT being loaded from the SEYUAUTH dataset.

System action:

Data repository initialization terminates.

User response:

Ensure that your STEPLIB and EYUDREP DD statements are correct.

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0711E
TARGETVER value (xxxx) is not a valid CICSPlex SM version.
Explanation:

An invalid value was entered on the TARGETVER=xxxx parameter. The value given is not a valid CICSPlex SM version.

System action:

Data repository initialization terminates.

User response:

Ensure that your PARM=(TARGETVER=xxxx) specifies a valid CICSPlex SM version.

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0712E
NEWREP contains at least one(1) record. Data Repository conversion terminated.
Explanation:

The NEWREP DD statement references a dataset that is not empty. This dataset must be empty before the EYUDREP can be migrated to it.

System action:

Data repository initialization terminates.

User response:

Ensure that your NEWREP DD statement references an empty dataset.

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
Start of change
EYUXD0714I
DDNAME NEWREP Switched to DIRECT update after nnnnn records were written.
Explanation:

During CPSM data repository conversion a record key was modified requiring a switch from SEQUENTIAL to DIRECT updating of the new data repository. This may result in an increase in the time required to complete the repository conversion.

System action:

Processing continues.

User response:

None.

Destination:

SYSOUT

Module:

EYU9XDU1

End of change
EYUXD0800I
API initialization complete
Explanation:

The application programming interface (API) subcomponent of the Data Repository component has been successfully initialized.

System action:

CMAS initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDJI

EYUXD0801E
API initialization has failed. API services are unavailable.
Explanation:

The application programming interface (API) subcomponent of the Data Repository component could not be initialized.

System action:

API initialization terminates. CMAS initialization continues, but the API is not available. A user trace record is written to the CICS trace data set.

User response:

If you need API services, stop and restart the CMAS and any local MASs that are attached to it. If the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDJI

EYUXD0802E
API initialization is unable to start name task
Explanation:

One of the long running tasks (LRTs) required by the API could not be initialized, where:

name
Identifies the LRT that could not be initialized as one of the following:
  • Notification
  • Connection
  • Disposition
  • Service
System action:

API initialization terminates. CMAS initialization continues, but the API is not available. A user trace record is written to the CICS trace data set.

User response:

If you need API services, stop and restart the CMAS and any local MASs that are attached to it. If the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDJI

EYUXD0803E
name task has failed. Task is being restarted.
Explanation:

One of the long running tasks (LRTs) required by the API experienced a problem from which it is attempting to recover, where:

name
Identifies the LRT that is being restarted as one of the following:
  • Notification
  • Connection
  • Disposition
  • Service
System action:

The CMAS attempts to restart the LRT. A user trace record is written to the CICS trace data set.

User response:

If the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDNC, EYU0XDND, EYU0XDNE, EYU0XDNS

EYUXD0804E
name task unable to recover from failure(s). Task being terminated.
Explanation:

The specified API long running task (LRT) was attempting to recover from a failure. However, the LRT determined that the number of recovery attempts it had made exceeded the maximum allowed, where:

name
Identifies the LRT that is being terminated as one of the following:
  • Notification
  • Connection
  • Disposition
  • Service
System action:

The LRT and the API service environment are terminated. CMAS processing continues, but the API is not available for use. A user trace record is written to the CICS trace data set.

User response:

If you need API services, stop and restart the CMAS and any local MASs that are attached to it. If the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDNC, EYU0XDND, EYU0XDNE, EYU0XDNS

EYUXD0805I
API name task terminated
Explanation:

The specified API long running task (LRT) has been terminated, where:

name
Identifies the LRT that was terminated as one of the following:
  • Notification
  • Connection
  • Disposition
  • Service
System action:

Additional EYUXD0805I messages are issued as the remaining API LRTs are terminated.

User response:

None.

Destination:

EYULOG

Module:

EYU0XDNC, EYU0XDND, EYU0XDNE, EYU0XDNS

EYUXD0806E
API ESSS action has failed. ESSS Response (code)
Explanation:

A CMAS attempt to communicate with the Environment Services System Services (ESSS) address space on behalf of the API failed, where:

action
Identifies the CMAS action as either CONNECTION or DISCONNECTION.
code
Is the hexadecimal return code.
System action:

The API service environment is terminated. CMAS processing continues, but the API is not available. A user trace record is written to the CICS trace data set.

User response:

Collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDF1

EYUXD0807I
API User(userid) has been successfully action
Explanation:

An application programming interface (API) user issued either an EXEC CPSM CONNECT or DISCONNECT command and the command completed successfully, where:

userid
Identifies the API user. This ID was either supplied by the user on a CONNECT command or determined by CICSPlex SM based on the operating environment.
action
Indicates that the user was either signed on or signed off, depending on which EXEC CPSM command was issued.
System action:

API processing continues.

User response:

None. This message may be suppressed by setting the CMAS CICSPlex SM system parameter APISIGNMSG(NO).

Destination:

EYULOG

Module:

EYU0XDF1, EYU0XDF2

EYUXD0808W
API User (userid) has failed to action
Explanation:

An application programming interface (API) user issued either an EXEC CPSM CONNECT or DISCONNECT command, but the command failed, where:

userid
Identifies the API user. This ID was either supplied by the user on a CONNECT command or determined by CICSPlex SM based on the operating environment.
action
Indicates that the user could not either sign on or sign off, depending on which EXEC CPSM command was issued.
System action:

API processing continues. A user trace record is written to the CICS trace data set.

User response:

Make sure the CONNECT or DISCONNECT command was correctly specified. If it was and the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDF1, EYU0XDF2

EYUXD0809W
CPSM resources will remain outstanding for API user(userid) due to resource release failures
Explanation:

As part of its disconnection process, the API attempted to release resources that had been allocated for its use. However, the attempt was not completely successful, where:

userid
Identifies the API user with which the resources were associated. This ID was either supplied by the user on a CONNECT command or determined by CICSPlex SM based on the operating environment.
System action:

The API user is signed off. However, some of the resources associated with that user's API thread remain allocated. A user trace record is written to the CICS trace data set.

User response:

Collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDF2

EYUXD0810E
CPSM API environment is damaged. API services are now unavailable
Explanation:

A problem has caused the API service environment to become damaged.

System action:

The API service environment is terminated. CMAS processing continues, but the API is not available. A user trace record is written to the CICS trace data set.

User response:

If you need API services, stop and restart the CMAS and any local MASs that are attached to it. If the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDNE

EYUXD0811W
CPSM API type resource shortage detected
Explanation:

The API has exhausted its supply of certain resources, where:

type
Identifies the type of resource as one of the following:
  • Thread Index
  • Thread Set
  • List Link
  • Command Free Queue
System action:

The API request that prompted the shortage fails.

User response:

If you need API services, stop and restart the CMAS and any local MASs that are attached to it. If the problem persists, collect the exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XDNE

Start of change
EYUXD0901E
SYSPRINT must be specified
Explanation:

The SYSPRINT DD statement for the batched repository update utility was missing or invalid.

System action:

The batched repository update utility terminates.

User response:

Correct the JCL for the batched repository update utility to include a valid SYSPRINT DD statement and resubmit the job.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0902E
SYSPRINT could not be opened
Explanation:

The SYSPRINT data set for the batched repository update utility could not be opened.

System action:

The batched repository update utility terminates.

User response:

Correct the JCL for the batched repository update utility to include a valid reference to a printer destination and resubmit the job.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0903E
SYSIN could not be opened
Explanation:

The SYSIN data set for the batched repository update utility could not be opened.

System action:

The batched repository update utility terminates.

User response:

Correct the JCL for the batched repository update utility to include a valid SYSIN DD statement and resubmit the job.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0904E
command command failed. Response=response Reason=reason
Explanation:

This message provides additional information on the cause of an error that occurred during a run of the batched repository update utility. The CICSPlex SM API command command returned a response value of response and a reason value of reason.

System action:

Start of changeThe batched repository update utility terminates.End of change

User response:

Refer to additional messages produced by the batched repository update utility. For an explanation of the response and reason values of the command refer to the CICSPlex System Manager Application Programming Reference

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0905E
An attempt to connect to CMAS cmasname failed
Explanation:

The batched repository update utility failed to connect to CMAS cmasname. The CMAS cmasname must be available for the batch repository update utility to connect and to submit batched repository updates.

System action:

The batched repository update utility terminates.

User response:

Ensure that CMAS cmasname is running so that it is available for the batch repository update utility to connect. Additional messages produced by the batched repository update utility provide further information.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0906E
An attempt to submit a batched repository update to run in CMAS cmasname failed.
Explanation:

The attempt to submit the batched repository update failed.

System action:

The batched repository update utility terminates.

User response:

Refer to additional messages produced by the batched repository update utility to determine why the attempt to submit a batch repository update failed.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0907E
Unable to interpret command response and reason. Response=response Reason=reason
Explanation:

The batched repository update utility received a response value of response and a reason value of reason which it was unable to interpret.

System action:

The batched repository update utility abnormally terminates.

User response:

Examine the job log for messages issued earlier which might indicate the reason for the failure. Also examine the job log for the CMAS. Examine any dumps and traces which have been produced, including those produced by the CMAS. If no reason for the failure can be found, collect the job log and trace for the CMAS, and the job log and dump for the batched repository update utility. Contact your IBM support center.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0908I
A batched repository update has been submitted to run in CMAS cmasname
Explanation:

The batched repository update utility has submitted a batched repository update to run in the specified CMAS.

System action:

A batched repository update runs in the specified CMAS.

User response:

Review the spooled output of the batched repository update that runs in the specified CMAS as appropriate.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0909I
CICSPlex SM Batched Repository Update Utility is terminating
Explanation:

The batched repository update utility is terminating.

System action:

The job ends.

User response:

None.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0910E
An attempt to obtain feedback information failed.
Explanation:

An attempt to obtain feedback information failed for a previous CICSPlex SM API command that also failed.

System action:

The batched repository update utility abnormally terminates.

User response:

Examine the job log for additional messages produced by the batched repository update utility which might indicate the reason for the failure. Also examine the job log for the CMAS. Examine any dumps and traces which have been produced, including those produced by the CMAS. If no reason for the failure can be found, collect the job log and trace for the CMAS, and the job log and dump for the batched repository update utility. Contact your IBM Support Center.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0911E
Feedback information did not contain an error code
Explanation:

The batch repository update utility issued a CICSPlex SM API command that failed. It then attempted to obtain further information describing the error by attempting to obtain error code feedback information but no error code was available.

System action:

Start of changeThe batched repository update utility terminates.End of change

User response:

See other messages issued by the batchrep repository update utility.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0912E
Error code nn supplied in feedback information not recognized
Explanation:

Feedback information supplied error code nn which was not recognized.

System action:

The batched repository update utility abnormally terminates.

User response:

Examine the job log for messages issued earlier which might indicate the reason for the failure. Also examine the job log for the CMAS. Examine any dumps and traces which have been produced, including those produced by the CMAS. If no reason for the failure can be found, collect the job log and trace for the CMAS, and the job log and dump for the batched repository update utility. Contact your IBM Support Center.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0913E
Feedback information contained error code nn - feedback text
Explanation:

An attempt by the batched repository update utility to submit a batched repository update in the CMAS failed. The reason for the failure is described by feedback text and is one of the following:

Duplicate request for this input data set and member
The batched repository update job could not be submitted because there was already a batched repository update in progress in the CMAS for the same input data set name and input data set member.
Failure to obtain storage for job
There was insufficient storage in the CMAS to run the batched repository update.
Failure during print processing
The batched repository update could not run because an error occurred during spooled print output processing in the CMAS.
Security violation with input data set
The batched repository update job could not run because the userid for the batched repository update utility was not authorized for access to the input data set.
Spool found to be not available
The batched repository update job could not run because spooled print output was not available in the CMAS.
Input data set not found
The batched repository update could not run in the CMAS because the input data set was not be found.
Security violation with output data set
The batched repository update job could not run because the userid for the batched repository update utility was not authorized for access to the output data set.
System action:

The batched repository update utility terminates.

User response:

Correct the cause of the error that prevents the batched repository update from being submitted and rerun the batched repository update utility.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0914E
Invalid input parameter
Explanation:

An invalid input parameter for the batched repository update utility was detected.

System action:

The batched repository update utility terminates without submitting a batched repository update to run in a CMAS.

User response:

Correct the input parameter and rerun the batched repository update utility. Consult the CICSPlex System Manager Administration manual for a description of the input parameters.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0915E
Required parameter parameter is not specified
Explanation:

The parameter input parameter for the batched repository update utility is required but has not been specified.

System action:

The batched repository update utility terminates without submitting a batched repository update to run in a CMAS.

User response:

Supply the correct input parameter and rerun the batch repository update utility. Consult the CICSPlex System Manager Administration manual for a description of the input parameters.

Destination:

Console, job log.

Module:

EYU9XDBC

End of change
Start of change
EYUXD0916E
Run type is not specified
Explanation:

A run type input parameter for the batched repository update utility is required but has not been specified.

System action:

The batched repository update utility terminates without submitting a batched repository update to run in a CMAS.

User response:

Supply the correct input parameter and rerun the batch repository update utility. Consult the CICSPlex System Manager Administration manual for a description of the input parameters.

Destination:

Console, job log.

Module:

EYU9XDBC

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