The EYUWRnnnn messages are issued by the user-modifiable program
called EYU9WRAM, which CICSPlex® SM distributes as part of its Workload Manager component.
The EYU9WRAM program can be modified to control the dynamic transaction
routing process used by CICSPlex SM. For more information about EYU9WRAM
and the CICSPlex SM Workload Manager, refer to
the CICSPlex System Manager Managing Workloads manual.
The text of these messages, like the program itself, can be modified.
If the EYU9WRAM program has been modified at your enterprise, the
text and meaning of these messages may vary.
The following variables are used in EYUWRnnnn messages, as distributed
by CICSPlex SM:
- fname
- The name of the EYU9WRAM function being processed, as one of
the following:
- SM_BALANCE
- Selects a target AOR from a list of candidates.
- SM_CREAFF
- Creates an affinity to an AOR.
- SM_DELAFF
- Deletes an affinity to an AOR.
- SM_ROUTE
- Routes a transaction to a named AOR, bypassing normal CICSPlex SM
processing.
- SM_SCOPE
- Returns a list of candidate AORs.
- fcode
- The numeric code of the EYU9WRAM function being processed, as
one of the following:
- 0
- Route Select
- 1
- Route Error
- 2
- Route Termination
- 3
- Transaction ABEND
- 4
- Route Notify
EYUWR0001E
Internal Error Raised in EYU9WRAM: Error is text
Explanation:
The EYU9WRAM program detected an unexpected error, where:
- text
- Identifies the error as one of the following:
- Nonzero return code from API: RC=code.
- A call to the WLM internal API returned a nonzero return
code. The return code from the WLM API should always be zero,
where:
- code
- Identifies the return code as a decimal value.
The WLM API function processor was not called.
- Invalid input COMMAREA size: Size=nnn.
- The size of the COMMAREA passed to EYU9WRAM was not as expected,
where:
- nnnn
- Is the size of the COMMAREA as a decimal value.
- Unknown Function in WCOM_CTYPE: Function=fcode.
- The specified function code is not known to the EYU9WRAM program
where fcode is as described in the
introduction to the EYUWRnnn messages.
- Unknown API Response from fname: RESPONSE=code.
- The API response code received from the specified EYU9WRAM
function is not known, where:
- code
- Identifies the response code as a decimal value.
- Unknown API Reason from fname: REASON=code.
- The API reason code received from the specified EYU9WRAM function
is not known, where:
- code
- Identifies the reason code as a decimal value.
System action:
The transaction that was using the EYU9WRAM program is not routed.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
The most likely causes of an internal error in EYU9WRAM are:
- An improper user modification to EYU9WRAM.
- Maintenance being applied to CICSPlex SM but not to the EYU9WRAM program.
Destination:
CICS® user terminal
EYUWR0002W
warning text
Explanation:
The EYU9WRAM program was invoked for a Route Error function after
having selected an AOR for routing. The selected AOR is not available
and there are no other AORs from which to select, where:
- warning text
- Identifies the problem as one of the following:
- The CICS link to the selected AOR (typeid) was not found.
- The CICS link to the selected AOR (typeid) is currently
out of service.
- No sessions are available for route to AOR (typeid).
- An allocation timeout occurred on the transaction route to AOR typeid.
- typeid
- Identifies the AOR that is not available by its:
- APPLID applid
- Eight-character application identifier, if available.
- SYSID sysid
- Four-character system identifier, if the APPLID is not available.
System action:
The transaction that was using the EYU9WRAM program is not routed.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0003W
The Affinity AOR (typeid) is not available because
the reason. text
Explanation:
The EYU9WRAM program was invoked for a Route Select or Route Error
function and call SM_SCOPE to obtain a scope list. The scope list
contained a single affinity AOR, which was not available, where:
- typeid
- Identifies the AOR that is not available by its:
- APPLID applid
- Eight-character application identifier, if available.
- SYSID sysid
- Four-character system identifier, if the APPLID is not available.
dt.reason dd.identifies the reason the AOR is not available,
as one of the following:
- AOR is down.
- The AOR is not active.
- CICS Link to the AOR is not available.
- The link to the AOR is either not defined or not in service.
- AOR job is different.
- The AOR is active but the Job terminated and restarted again
after the affinity was initially created.
- text
- describes the new state of the affinity
- The affinity remains.
- Neither the EYU9WRAM program nor CICSPlex SM deleted the affinity.
- The affinity is ended.
- Either EYU9WRAM or CICSPlex SM deleted the affinity.
System action:
The transaction that was using the EYU9WRAM program is not routed.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0101E
Invalid Request to CPSM: FUNCTION=fname, REASON=code.
Explanation:
The specified EYU9WRAM function returned an invalid request response
where:
- fname
- Is as described in the introduction to
the EYUWRnnn messages
- code
- Identifies the reason code as a decimal value.
System action:
The transaction that was using the EYU9WRAM program is not routed.
A user trace record is written to the CICS trace data set.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0102E
Parameter Error on call to CPSM: FUNCTION=fname,
REASON=code.
Explanation:
The specified EYU9WRAM function returned a parameter error response
where:
- fname
- Is as described in the introduction to
the EYUWRnnn messages
- code
- Identifies the reason code as a decimal value.
System action:
The transaction that was using the EYU9WRAM program is not routed.
A user trace record is written to the CICS trace data set.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0103E
Function Error on call to CPSM: FUNCTION=fname,
REASON=code.
Explanation:
The specified EYU9WRAM function returned a function error response
where:
- fname
- Is as described in the introduction to
the EYUWRnnn messages
- code
- Identifies the reason code as a decimal value.
System action:
The transaction that was using the EYU9WRAM program is not routed.
A user trace record is written to the CICS trace data set.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0104E
CPSM Reports an unexpected error on FUNCTION fname.
Explanation:
The specified EYU9WRAM function encountered an unexpected error
where fname is as described in the
introduction to the EYUWRnnn messages.
System action:
The transaction that was using the EYU9WRAM program is not routed.
A user trace record is written to the CICS trace data set.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0201W
The CICS link to the SM_ROUTE selected AOR (typeid)
is not available.
Explanation:
The SM_ROUTE function of the EYU9WRAM program determined that the
selected AOR is not available for routing, where typeid identifies
the AOR that is not available by its:
- APPLID applid
- Eight-character application identifier, if available.
- SYSID sysid
- Four-character system identifier, if the APPLID is not available.
System action:
The transaction that was using the EYU9WRAM program is not routed.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program. Note that the sample
EYU9WRAM program, as delivered with CICSPlex SM, does not use the SM_ROUTE
function.
Destination:
CICS user terminal
EYUWR0301W
The initial affinity transaction can not be routed because reason.
Explanation:
The SM_SCOPE function of the EYU9WRAM program determined that an
affinity to an AOR is required but can not be created, where reason identifies
the reason an affinity can not be created as one of the following:
- required CICSPlex SM services are not available.
- Either the CMAS to which the TOR is attached is not active,
or the workload that the TOR is using has been frozen. In the first
case, the WLMAWTOR view shows a value of YES in the Connection Lost
field. In the second case, the WLMAWORK view shows a status of FROZEN.
- no systems are available.
- There are no AORs available for routing. The WLMAWAOR view shows
the status of AORs defined as part of the workload.
System action:
The transaction that was using the EYU9WRAM program is not routed.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
EYUWR0501W
Affinity to AOR (typeid) was not created because
the reason.
Explanation:
The SM_CREAFF function of the EYU9WRAM program returned a warning
response, where:
- typeid
- Identifies the AOR by its:
- APPLID applid
- Eight-character application identifier, if available.
- SYSID sysid
- Four-character system identifier, if the APPLID is not available.
- reason
- Identifies the reason, as one of the following:
- AOR is quiesced
- The AOR is quiesced; no new affinities can be created to it.
- AOR is marked ignore
- The EYU9WRAM program previously marked the AOR to be ignored
by CICSPlex SM.
- transaction group is dormant
- The transaction group for the transaction is dormant.
- AOR is down
- The AOR is not active.
- Workload is not active
- The create affinity call was for a system or permanent lifetime
affinity, but the workload is not considered active.
System action:
The transaction that was using the EYU9WRAM program is not routed.
User response:
Report the problem to the person at your site who is responsible
for workload management and the EYU9WRAM program.
Destination:
CICS user terminal
[[