Initialization of the Workload Manager (WLM) long running task has begun.
WLM initialization continues.
None.
EYULOG
EYU0WINT
The Workload Manager (WLM) long running task has been successfully initialized.
WLM initialization continues.
None.
EYULOG
EYU0WMGR
The Workload Manager (WLM) component has been successfully initialized. WLM is now available for work.
CMAS initialization continues.
None.
EYULOG
EYU0WINT
The Workload Manager (WLM) component could not be initialized.
WLM is not available for work. A user trace record is written to the CICS® trace data set. CMAS initialization continues.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0WINT
As part of the connection process between two CMASs, Workload Manager (WLM) has been asked to exchange information about workloads in the specified CICSplex, where:
Workload query process continues.
None.
Console, job log, EYULOG
EYU0WMQM EYU0WMQW
During connection of a TOR to a CMAS, the Workload Manager determined that the required workload already existed in another CMAS and initiated an query request to that CMAS to retrieve all pertinent information about the workload. This message indicates the successful conclusion of that process and may be issued either by the CMAS initiating the request or by the CMAS receiving the request, where:
None.
None.
Console, job log, EYULOG
EYU0WMQB EYU0WMQW
During connection of a TOR to a CMAS, the Workload Manager (WLM) determined that the required workload already existed in another CMAS and initiated an query request to that CMAS to retrieve all pertinent information about the workload. This message indicates the failure of that process and may be issued either by the CMAS initiating the request or by the CMAS receiving the request, where:
If the reason for the failure of the workload query was that the CMAS to which it was directed was not accessible, an attempt is made to select a new targeet CMAS, and the workload query process is retried.
If the workload query failed for any other reason, the workload query process is not retried.
Other messages should appear with detailed information about the failure.
Console, job log, EYULOG
EYU0WMQM EYU0WMQW
During composition of a workload received from another CMAS, Workload Manager (WLM) encountered a record that contains an invalid command type or object type. The command or object type identifying number is inserted in the message, where:
The invalid record is ignored. User trace records are written to the CICS trace data set. The workload build process continues.
Collect the trace records and the job log and contact your IBM® Support Center.
Console, job log, EYULOG
EYU0WMQB
A request was made to update the specified Workload Manager (WLM) object, but the object could not be found.
The update record is ignored. User trace records are written to the CICS trace data set. The workload build process continues.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0WMQU
During workload analysis, a workload was found to be active on both the inquiring CMAS and the reporting CMAS. Because the workloads were initiated by different CMASs, they can not be synchronized to reflect the same workload characteristics.
This situation can occur when two unconnected CMASs are initialized with their respective MASs (acting as TORs and AORs) and the workload becomes active in both. When the two CMASs attempt to connect to each other, the workloads do not reflect the same information and can not be combined into a single workload. Note that this situation does not prevent a TOR that is using one of the workloads from routing to AORs connected to the other CMAS.
The workloads are considered to be unique; they do not share any information. The workload query process continues.
If you want to synchronize the two workloads, first shut down all of the TORs and AORs associated with one of the CMASs, and then shut down the CMAS itself. Then restart the CMAS and wait for it to establish a connection to the other CMAS. After the CMAS is fully initialized and connected, restart the TORs and AORs. The workload on each CMAS is synchronized and treated as a single workload.
Console, job log, EYULOG
EYU0WMQW
During connection of a TOR to a CMAS, the workload manager determined that the required workload already existed in another CMAS, however communications with that CMAS were not active. This prevents the import of the required workload.
The console is queried as to whether or not the workload should be installed from the repository records on the local CMAS (possibly creating a duplicate workload) or whether workload installation should be deferred until communications with a CMAS which knows of the workload is reestablished.
Should the operator defer installation of the workload, WLM must be restarted in the TOR using the MAS view after communications is reestablished.
Should the operator continue the installation of a local copy of the workload, it is possible that the newly created workload contains affinity relationships that conflict with those already established in the original workload.
WLM waits for a response. An exception trace is written to the CICS trace data set. The trace provides a list of CMASes where the workload already exists, but communication with these CMASes is not active.
Entering Y on the console causes the workload to be installed at that time. If a CMAS that already has the workload installed has become accessible, the workload is imported from that CMAS. Otherwise the workload is built from the local CMAS's data repository records.
Entering N on the console aborts installation of any workload
Entering R on the console causes the workload query to be repeated. If a CMAS that has the workload installed has become accessible, the workload is imported from that CMAS. Otherwise the workload will not be built from definitions in the data repository of the local CMAS, but message EYUWI0086 and the prompt to the operator is reissued.
Console, job log
EYU0WMQM
CMAS cmasname attempted to import workload workname for CICSPlex, but this import was failed because CICS BTS data was present, and CMAS cmasname is at an earlier release level.
Import is rejected.
If you intended to share the workload, you should either create a separate workload for the CICS BTS data, or remove the CICS BTS data from the workload.
Console
EYU0WMQW
CMAS cmasname is attempting to import workload workname for the context CICSPlex (because a routing region connected to CMAS cmasname is part of the workload, and it is the first such active region connected to that CMAS). Since that CMAS is at an earlier release, this CMAS must check that no CICS BTS data is present in the workload. If there is CICS BTS data present then the import will be rejected and message EYUWI0087E will be issued.
Continues.
None
Console
EYU0WMQW
The reply to preceding message EYUWI0086I was not valid, that is. a character other than N or Y was entered.
Message EYUWI0086I is reissued.
Provide a valid reply to message EYUWI0086I.
Console, job log, EYULOG
EYU0WMQW