EYUWInnnn messages

EYUWI0001I
Workload Manager Task Initialization Started
Explanation:

Initialization of the Workload Manager (WLM) long running task has begun.

System action:

WLM initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WINT

EYUWI0002I
Workload Manager Task Initialization Complete
Explanation:

The Workload Manager (WLM) long running task has been successfully initialized.

System action:

WLM initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMGR

EYUWI0003I
WLM Initialization Complete
Explanation:

The Workload Manager (WLM) component has been successfully initialized. WLM is now available for work.

System action:

CMAS initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WINT

EYUWI0010E
WLM Initialization Failed
Explanation:

The Workload Manager (WLM) component could not be initialized.

System action:

WLM is not available for work. A user trace record is written to the CICS® trace data set. CMAS initialization continues.

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:

EYU0WINT

EYUWI0080I
WLM workload action process for context (plexname) has been started - direction CMAS (cmasname)
Explanation:

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:

action
Identifies the action that WLM is performing as either:
query
One CMAS is requesting information from the other CMAS.
analysis
One CMAS is analyzing the information received from the other CMAS.
direction
Indicates what role the specified CMAS is playing in the exchange:
directed to CMAS
A query is being sent to the specified CMAS.
initiated by CMAS
An analysis of information received is being done by the specified CMAS.
System action:

Workload query process continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0WMQM EYU0WMQW

EYUWI0081I
WLM workload action process for context (plexname) has been completed - direction CMAS (cmasname)
Explanation:

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:

action
Identifies the action that WLM completed as either:
analysis
One CMAS has analyzed the information received from the other CMAS.
build
One CMAS has constructed the appropriate workload based on information received from the other CMAS.
direction
Indicates what role the specified CMAS is playing in the exchange:
directed to
A query is being sent to the specified CMAS.
initiated by
An analysis of information received is being done by the specified CMAS.
cmasname
Identifies the CMAS that initiated this stage of workload processing.
System action:

None.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0WMQB EYU0WMQW

EYUWI0082E
WLM Workload action failed for context (plexname) direction (cmasname)
Explanation:

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:

action
Identifies the action that WLM could not complete as either:
query
A request for information could not be completed.
analysis
An analysis of information could not be completed.
direction
Indicates what role the specified CMAS was playing in the exchange:
directed to CMAS
A query could not be sent to the specified CMAS.
initiated by CMAS
An analysis of information received by the specified CMAS could not be completed.
System action:

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.

User response:

Other messages should appear with detailed information about the failure.

Destination:

Console, job log, EYULOG

Module:

EYU0WMQM EYU0WMQW

EYUWI0083E
WLM Query Workload has encountered an unknown type during workload build process - nn (nn) ignored
Explanation:

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:

nn
Is the invalid command or object type identifier.
System action:

The invalid record is ignored. User trace records are written to the CICS trace data set. The workload build process continues.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0WMQB

EYUWI0084E
WLM Query Workload was unable to locate object (nn), key (type), update ignored
Explanation:

A request was made to update the specified Workload Manager (WLM) object, but the object could not be found.

System action:

The update record is ignored. User trace records are written to the CICS trace data set. The workload build process continues.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0WMQU

EYUWI0085E
WLM Query Workload has detected a Workload synchronization failure for Workload (name)
Explanation:

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.

System action:

The workloads are considered to be unique; they do not share any information. The workload query process continues.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMQW

EYUWI0086I
Workload Specification (specname) exists but cannot be imported -- Should Workload installation for routing region (masname) continue? (Y=Continue,N=Cancel, R=Retry)
Explanation:

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.

System action:

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.

User response:

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.

Notes:
  1. If you enter a Y response before a CMAS that has the workload installed becomes accessible to the local CMAS, a duplicate workload is created. If definitional changes had been made since the original workload was installed, this can result in the workloads routing with different rules. Additionally, affinity cannot be honored between the workloads. If you do not want a duplicate workload, ensure that a CMAS that has the workload installed becomes accessible to the local CMAS before replying Y.
  2. The EYUWI0086I message prompt expires 15 minutes after issue. At that time, a check is made to determine whether or not a CMAS that has the workload installed has become accessible. If one has, the workload is imported from that CMAS. If not, the EYUWI0086I message and prompt are reissued.
Destination:

Console, job log

Module:

EYU0WMQM

EYUWI0087I
Attempt to query workload (workname) for context (contname) by lower level CMAS (cmasname) is rejected
Explanation:

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.

System action:

Import is rejected.

User response:

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.

Destination:

Console

Module:

EYU0WMQW

EYUWI0088E
Attempting to import workload (workname) for context (contname)
Explanation:

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.

System action:

Continues.

User response:

None

Destination:

Console

Module:

EYU0WMQW

Start of change
EYUWI0089E
Invalid reply -- reenter
Explanation:

The reply to preceding message EYUWI0086I was not valid, that is. a character other than N or Y was entered.

System action:

Message EYUWI0086I is reissued.

User response:

Provide a valid reply to message EYUWI0086I.

Destination:

Console, job log, EYULOG

Module:

EYU0WMQW

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