EYUWMnnnn messages

EYUWM0400I
Workload type (name) has been successfully installed for Context (plexname) - initiated by CMAS (cmasname)
Explanation:

Workload information was received from the specified CMAS and installed in the specified CICSplex, where:

type
Identifies the type of workload information that was installed as one of the following:
  • Specification
  • Definition
  • Group
name
Is the user-defined name for that information.
System action:

Workload processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMWB, EYU0WMWI

EYUWM0401E
Workload type (name) failed to install for Context (plexname) - direction (objectname)
Explanation:

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:

type
Identifies the type of workload information that could not be installed as one of the following:
  • Specification
  • Definition
  • Group
name
Is the user-defined name for that information.
direction
Indicates what role the specified CMAS was playing in the exchange:
initiated by join of TOR
A query could not be sent to the specified CMAS.
received from
An analysis of information received by the specified CMAS could not be completed.

There may be other related messages further detailing the reasons for the failure.

System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMWB EYU0WMWI EYU0WMWU EYU0WMWC

EYUWM0402E
Workload type (name) reason for Context (plexname)
Explanation:

The specified workload information could not be installed for the specified reason, where:

type
Identifies the type of workload information that could not be installed as one of the following:
  • Specification
  • Definition
  • Transaction Group
name
Is the user-defined name for that information.
reason
Explains why the workload information could not be installed:
is not defined
No record exists in the data repository for the specification, definition or transaction group.
has an invalid scope specification
The AOR scope for the specification or definition is invalid.
has no transaction links
There are no transactions associated with the transaction group.
System action:

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.

User response:

Depending on the reason given, do one of the following:

is not defined
Make sure the specification, definition or transaction group name was specified correctly. If so, then the record has been removed from the data repository.
has an invalid scope specification
Make sure the AOR name in the specification or definition was specified correctly and that the AOR itself still exists.
has no transaction links
Make sure the transaction group name was specified correctly. If so, use the DTRINGRP view to determine what transactions are associated with the group.
Destination:

Console, job log, EYULOG

Module:

EYU0WMWC, EYU0WMBD

EYUWM0403E
Workload Manager Task has reported an error processing event (event_name) for entity_type (entity_name)
Explanation:

The Workload Manager (WLM) long running task experienced an internal error while attempting to process the specified event, where:

event_name
Identifies the event as one of the following:
  • CICSChg
  • CMASConn
  • CMASDisc
  • CMASExit
  • CMASJoin
  • Connect
  • DupWrkLd
  • EmStatus
  • ENetDisc
  • LambInterval
  • LogOff
  • MasJoin
  • MasSick
  • MasStart
  • MasStop
  • MasWell
  • PIInterval
  • PlexChg
  • PlexCnfg
  • RTAEvent
  • SignOff
  • SysGroup
entity_type
Identifies the entity the event is being processed for as one of the following:
  • CICS Group
  • CICSplex
  • CMAS
  • MAS
  • Workload
entity_name
Identifies the name of the entity.
System action:

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

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMEV

EYUWM0404E
Workload Manager Task has encountered an unknown event notification (nn) event ignored
Explanation:

The Workload Manager (WLM) long running task received an unsolicited event record, where:

nn
Is the event notification ID that was not recognized by WLM. Given the event notification ID, it is possible to determine which CICSPlex® SM method the event.
System action:

WLM ignores the event record and continues processing. The invalid event record is written to the CICS trace data set.

User response:

Collect the trace records and any related messages and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0WMEV

EYUWM0405W
Workload Manager Task has encountered an invalid netname while processing connection (conname) for routing region (rtrgn)
Explanation:

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:

conname
Identifies the connection name.
rtrgn
Identifies the name of the routing region.
System action:

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

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMTU

EYUWM0410I
Workload type (name) has been removed from Context (plexname)
Explanation:

The specified workload information is no longer installed for use by the specified CICSplex, where:

type
Identifies the type of workload information that was removed as one of the following:
  • Specification
  • Definition
name
Is the user-defined name for that information.
System action:

Workload processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMDF, EYU0WMWT

EYUWM0420I
TOR (sysname) has been joined to Workload (name)
Explanation:

The specified TOR has been connected to the specified workload. The TOR is now available for use by WLM.

System action:

Workload processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMTJ

EYUWM0421I
TOR (sysname) has been removed from Workload (name)
Explanation:

The connection between the specified TOR and the specified workload has been removed. The TOR is no longer available for use by WLM.

System action:

Workload processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMTT

EYUWM0422E
Routing System (sysname) already active in Workload (name)
Explanation:

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.

System action:

Creation of the new workload fails. The Routing System continues to be managed by the specified workload.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMWC

EYUWM0423I
AOR (sysname) has been quiesced for Context (plexname)
Explanation:

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.

System action:

The AOR is marked as quiesced and is no longer available to WLM for routing. Workload processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMQA

EYUWM0424I
AOR (sysname) has been activated for Workload (name)
Explanation:

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.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMAA

EYUWM0425I
AOR (sysname) has been terminated for Workload (name)
Explanation:

Start of changeThe 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.End of change

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMAT

EYUWM0426I
type (name) already installed in Workload (name) - parameter ignored
Explanation:

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:

type
Indicates what was already installed:
Definition
The definition is already installed.
Transaction
The transaction is already installed as part of another transaction group.
Group
The definition of the transaction group is different from one that is already installed under the same name; the existing one remains in effect.
name
Identifies the specific transaction or transaction group and the workload in which it is installed.

The indicated parameter is not reinstalled.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMWI

EYUWM0427I
Parameters have been ignored during the installation of Workload definition|group (def name|group name) for context (context)-received from (cmas name)
Explanation:

During installation of the indicated WLM definition or group, duplicate parameters were encountered and subsequently ignored.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMWI

EYUWM0428I
WLMDEF (wlmdefname1) already installed in Workload (workloadname) as (wlmdefname2) - parameter ignored
Explanation:

While attempting to install the specified WLM definition, it was found to match all the parameters of a previously installed definition.

System action:

The definition is not installed.

User response:

None.

Destination:

EYULOG

Module:

EYU0WMWI

EYUWM0429E
WLMDEFs (defname1) and (defname2) for Workload (workloadid) contain conflicting parameters. WLMDEF (defname3) is ignored
Explanation:

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:

System action:

The indicated workload definition is not installed.

User response:

Do one of the following:

Destination:

fonsole, job log, EYULOG

Module:

EYU0WMBD, EYU0WMWI, EYU0WMBP

EYUWM0430I
Workload workloadid transition to type: sysname at sysplex reason
Explanation:

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:

workloadid
Identifies the workload that is affected by the change.
type
Identifies the algorithm to which the workload is changing as either GOAL or QUEUE.
sysname
Is the name of the AOR or TOR that caused the change.
sysplex
Is the name of the MVS™ sysplex where the CICS system is running.
reason
Indicates the reason for the change as one of the following:
Initializing
The specified CICS system is initializing.
Terminating
The specified CICS system is terminating.
Changing status
The sysplex changed its MVS/WLM status.

This message appears only when the CICSPlex SM workload specification (WLMSPEC) identifies GOAL as the algorithm type.

System action:

The routing algorithm for all TORs in the workload changes to the type specified in this message.

User response:

None.

Destination:

EYULOG

Module:

EYU0WSUA

EYUWM0432E
WLMDEF (wlmdefname) in Workload (workloadname) cannot be processed due to a CICS BTS Processtype specification
Explanation:

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.

System action:

The WLMDEF install will fail.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMBD

EYUWM0433E
TRANGRP (trangrpname) in Workload (workloadname) cannot be processed due to a CICS BTS Affinity specification
Explanation:

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.

System action:

The WLMDEF install will fail.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMBD

Start of change
EYUWM0434W
Multiple connections are installed from routing region (torname) to target region (aorname) WLM will use connection (conn)
Explanation:

During activation of a routing region or target region, multiple connections were discovered between the routing region and the target region, where:

torname
is the name of the routing region.
aorname
is the name of the target region.
conn
is the name of the connection that WLM will use to route from the routing region to the target.
System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMAA, EYU0WMTJ

End of change
Start of change
EYUWM0435EW
An additional connection has been installed from routing region (torname) to target region (aorname) WLM will now use connection (newc) instead of (oldc)
Explanation:

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:

torname
is the name of the routing region.
aorname
is the name of the target region.
newc
is the name of the newly installed connection from the routing region to the target.
oldc
is the name of the existing connection from the routing region to the target.
System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0WMTU

End of change
Start of change
EYUWM0436I
Target region (sysname) has been reactivated for Context (plexname)
Explanation:

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.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0WAUO

End of change
Start of change
EYUWM0437I
Target region (sysname) quiesced due to CSYSDEF settings for context (plexname)
Explanation:

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.

System action:

The target region is marked as quiesced and is no longer available to WLM for routing. Workload processing continues.

User response:

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 :

Destination:

EYULOG

Module:

EYU0WMAA

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