A fix is available
APAR status
Closed as program error.
Error description
You have updated your RTA configuration and now when you bring up a CICS region, you see the following message in your CMAS EYULOG . EYUPM0107E Install of RTADEF (defname) for RTASPEC specname in Context(myplex) Scope(MASname) failed. . You no longer get RTA alerts issued. From initial analysis, this issue appears to be caused by having the same EVALDEF used in more than one RTADEF, associated with the same RTASPEC. Additionally, one of the EVALDEFs that had just previously installed successfully may have had a modification string ( OPRSTRING ) specified. . Additional details on the exact cause will be placed in the APAR closing text. . Additional Symptom(s) Search Keyword(s): KIXREVSVR
Local fix
use unique EVALDEF names
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM users. * **************************************************************** * PROBLEM DESCRIPTION: A CMAS issues message EYUPM0107E * * when connecting to a MAS, * * or installing an RTADEF into a MAS. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves * * APAR PH07143, all CMAS regions must be * * restarted to activate the new code. * * The restarts do not need to occur at * * the same time. * **************************************************************** A MAS region is started, and connects to a CMAS. That CMAS needs to install some RTA definitions into the MAS region. There is more than one RTADEF to install, EYU0PECD is called to install the evaluation definitions for an RTADEF. The first EVALDEF has not previously been installed for any other RTADEF, so a new one is created (and state established in PECD to indicate this). A subsequent EVALDEF being processed for this RTADEF has been previously installed for another RTADEF. A loop control error in EYU0PECD means that this EVALDEF is re-initialised as if it were a new element. An error caused by doing this means that the PEED control block representing this element is released, thereby allowing the storage where it resides to be reused. . The CMAS will issue msgEYUPM0107E +EYUPM0107E applid Install of RTADEF ( name ) for RTASPEC spec in Context( context ) Scope( scope ) failed. . Exception trace entries which may be seen include XSLU - EXCP 1,RESNTFND XSRU - EXCP 4,XSLUFAIL PECD - EXCP 21,EXCEPT PECD - EXCP 5,EXCEPT PRCD - EXCP 2,EXCEPT PMDI - EXCP 4,ANLZCDEF . Other symptoms may occur due to other processing attempting to read in the PEED control block after it has been freed. These include EYUXL0905E applid ASRA IN MOMS, OFFSET 00000A08 as a result of a 0E0 system completion code in EYU0MOMS when accessing storage addressed by PEED_MOS_MAL.
Problem conclusion
EYU0PECD has been update to ensure that each EVALDEF is processed correctly.
Temporary fix
Comments
APAR Information
APAR number
PH07143
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
10M
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-01-10
Closed date
2019-02-26
Last modified date
2019-03-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI61495 UI61496
Modules/Macros
EYU0PECD
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
01 March 2019