Workload information was received from the specified CMAS and installed in the specified CICSplex, where:
Workload processing continues.
None.
EYULOG
EYU0WMWB, EYU0WMWI
The indicated workload specification, definition or group has failed to install in the specified CICSplex. This workload specification, definition, or group was propagated throughout the CICSplex by the indicated CMAS, where:
There may be other related messages further detailing the reasons for the failure.
Workload processing continues, but the specified workload information is not available to the CICSplex. A user trace record is written to the CICS® trace data set.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem. If the problem can be identified and corrected, then try reinstalling the workload information. If the problem can not be corrected, then contact your IBM® Support Center.
Console, job log, EYULOG
EYU0WMWB EYU0WMWI EYU0WMWU EYU0WMWC
The specified workload information could not be installed for the specified reason, where:
Workload processing continues, but the specified workload information is not available to the CICSplex. A user trace record is written to the CICS trace data set.
Depending on the reason given, do one of the following:
Console, job log, EYULOG
EYU0WMWC, EYU0WMBD
The Workload Manager (WLM) long running task experienced an internal error while attempting to process the specified event, where:
Workload event processing continues. A user trace record is written to the CICS trace data set.
This message may be immediately preceded by message EYUWM0405W. If so, please refer to the user response for that message. If not, make a note of the event name, then collect the auxtrace data sets and complete job output from the CMAS and contact your IBM Support Center.
Console, job log, EYULOG
EYU0WMEV
The Workload Manager (WLM) long running task received an unsolicited event record, where:
WLM ignores the event record and continues processing. The invalid event record is written to the CICS trace data set.
Collect the trace records and any related messages and contact your IBM Support Center.
Console, job log, EYULOG
EYU0WMEV
The Workload Manager (WLM) long running task running in a CMAS encountered a null netname while processing the install of a connection in a routing region, where:
Workload event processing continues. A user trace record is written to the CICS trace data set.
Determine if the named connection is to a target region. If not, the message can be ignored. If the connection is to a target region, then collect the auxtrace data sets and complete job output from the CMAS, routing region, and target region, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0WMTU
The specified workload information is no longer installed for use by the specified CICSplex, where:
Workload processing continues.
None.
EYULOG
EYU0WMDF, EYU0WMWT
The specified TOR has been connected to the specified workload. The TOR is now available for use by WLM.
Workload processing continues.
None.
EYULOG
EYU0WMTJ
The connection between the specified TOR and the specified workload has been removed. The TOR is no longer available for use by WLM.
Workload processing continues.
None.
EYULOG
EYU0WMTT
An attempt was made to link the specified Routing System to a new workload, but Workload Manager (WLM) determined that the Routing System is already active and linked to the specified workload.
Creation of the new workload fails. The Routing System continues to be managed by the specified workload.
Use the WLMSCOPE view to review the links that are defined between Routing Systems and workloads. Then collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0WMWC
All Workload Manager (WLM) activity has been quiesced for the specified AOR in the specified CICSplex. When a request is made to quiesce an AOR for one workload, that AOR is quiesced for all workloads in the CICSplex. The fact that an AOR is quiesced only indicates that WLM no longer considers it for routing purposes.
The AOR is marked as quiesced and is no longer available to WLM for routing. Workload processing continues.
None.
EYULOG
EYU0WMQA
The indicated AOR has been activated for the indicated workload. This indicates that WLM may now route transactions to this AOR as it is available for work.
None.
None.
EYULOG
EYU0WMAA
The indicated AOR is no longer active in the indicated
workload. This means that the CMAS no longer has any connection to
this MAS and the MAS will not be available for transaction routine.
None.
None.
EYULOG
EYU0WMAT
A transaction or transaction group that was to be installed as part of a workload definition was found to already exist in an active workload, where:
The indicated parameter is not reinstalled.
None.
None.
EYULOG
EYU0WMWI
During installation of the indicated WLM definition or group, duplicate parameters were encountered and subsequently ignored.
None.
None.
EYULOG
EYU0WMWI
While attempting to install the specified WLM definition, it was found to match all the parameters of a previously installed definition.
The definition is not installed.
None.
EYULOG
EYU0WMWI
During installation of the specified workload, two workload definitions were found to have the same transaction group, LUname, and user ID values, but different AOR scopes. The conflicting AOR scopes would make routing decisions impossible, so one of the WLMDEFs is discarded, where:
The indicated workload definition is not installed.
Do one of the following:
fonsole, job log, EYULOG
EYU0WMBD, EYU0WMWI, EYU0WMBP
The routing algorithm for the specified workload is changing because an application-owning region (AOR) or terminal-owning region (TOR) named in the workload underwent a change in status, where:
This message appears only when the CICSPlex SM workload specification (WLMSPEC) identifies GOAL as the algorithm type.
The routing algorithm for all TORs in the workload changes to the type specified in this message.
None.
EYULOG
EYU0WSUA
Whilst installing a WLMDEF into an existing Workload that is shared with a / CICSPlex SM V1R2M0 or V1R3M0 TOR, a non-generic CICS BTS Processtype value was found.
The WLMDEF install will fail.
A Workload that is being used by a CICSPlex SM V1R2M0 or V1R3M0 TOR cannot contain any CICS BTS definitions or attributes. Either remove the candidate TOR from the Workload Scope, or separate the non-CICS BTS WLMDEFs into a different Workload, and include the candidate TOR in the installation scope for the new Workload.
Console, job log, EYULOG
EYU0WMBD
Whilst installing a WLMDEF into an existing Workload that is shared with a CICSPlex SM V1R2M0 or V1R3M0 TOR, a TRANGRP with a CICS BTS Affinity specification was found.
The WLMDEF install will fail.
A Workload that is being used by a CICSPlex SM V1R2M0 or V1R3M0 TOR cannot contain any CICS BTS definitions or attributes. Either remove the candidate TOR from the Workload Scope, or separate the non-CICS BTS TRANGRPs into a different Workload, and include the candidate TOR in the installation scope for the new Workload.
Console, job log, EYULOG
EYU0WMBD
During activation of a routing region or target region, multiple connections were discovered between the routing region and the target region, where:
This message and a trace record are issued. WLM attempts to route from the routing region to the target region using the connection indicated in the message. Note that if routing is not possible over this connection, WLM will not switch to any alternate connection between the routing region and the target region.
If you want routing over the connection indicated in the message, no response is necessary. If you want routing over a different connection, discard all the unwanted connections and restart the target region.
Console, job log, EYULOG
EYU0WMAA, EYU0WMTJ
While processing an ad-hoc install of a connection between an active routing region and an active target region, WLM determined that a previous connection was installed, where:
This message and a trace record are issued. WLM attempts to route from the routing region to the target region using the newly installed connection. Note that if routing is not possible over this connection, WLM will not switch to any alternate connection between the routing region and the target region.
If you want routing over the newly installed connection indicated in the message, no response is necessary. If you want routing over a different connection, discard all the unwanted connections and restart the target region.
Console, job log, EYULOG
EYU0WMTU
The indicated target region has been activated as a potential target of workloads in the specified CICSplex. This indicates that WLM may now route transactions to this target region as it is available for work.
None.
None.
EYULOG
EYU0WAUO
All Workload Manager (WLM) activity has been quiesced for the specified target region in the specified context because the CICS system is defined to CICSPlex SM as not being a target region at startup.
This definition is set by specifying NO in one of:
The target region is quiesced for all workloads in the CICSplex. The fact that a target region is quiesced only indicates that WLM no longer considers it for routing purposes.
The target region is marked as quiesced and is no longer available to WLM for routing. Workload processing continues.
Change the definition to YES, if the target region should be part of the workload at startup.
Alternatively, when the target region is ready to receive work use one of the following methods :
EYULOG
EYU0WMAA