A fix is available
APAR status
Closed as program error.
Error description
A typo in CICS start up JCL resulted in an outstanding reply: DFHSI1579D applid Module DFHSIPLT PLT program xxxxxxxx not found. Reply GO or CANCEL. . Subsequently, when the MAS region(s) was, cancelled the following messages occurred: . EYUCL0009I applid ESSS ICT entered for Detach from <masname> EYUTS0002E applid Topology Connect for <masname> Failed ... EYUPM0107E applid Install of RTADEF (xxxxxxxx) for RTASPEC xxxxxx in Context(xxxxxxxx) Scope(xxxxxxxx) failed. . The EYUPM0107E message is issued out of PMDI (RTAMRM Definition Install) within the TDPATH_DOINST routine where it creates the RTAMRMs RDEF descriptor blocks and adds all the active RDEF list elements. . The following exception trace entries are issued: xxxxx PECD PRCD XLST RTA EXCP. 15 EXCEPT CPSM CMAS xxxxx PRCD PMDI XLST RTA EXCP. 2 EXCEPT CPSM CMAS xxxxx PMDI PMAT XLST RTA EXCP. 13 ANLZCDEF CPSM CMAS . where: Function EVALCRE PMPI_LOCMAS_XCPT 15 Locate MAS failed Function ANLZCRE PMPI_EVALCRE_XCPT 2 Create ANLZ_DESC failed Function DEFINSTL PMPI_CRERDEF2_XCPT 13 RTAANLZ Create RDEF . We are trying to create a resource definition and failing trying to locate the MAS region which is currently shut down. It appears the notification was not generated correctly so the RTA event was not cancelled. . . . Additional Symptom(s) Search Keyword(s): KIXREVxxx
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: All users of CPSM V5R4M0 and V5R5M0. * **************************************************************** * PROBLEM DESCRIPTION: When a MAS region is cancelled during * * the topology connection phase, message * * EYUTS0002E might be issued. * * * * EYUTS0002E applid Topology Connect * * for <masname> Failed * * * * If there are any RTA rules associated * * with the MAS region, message EYUPM0107E * * might be issued as well. * * * * EYUPM0107E applid Install of RTADEF * * (xxxxxxxx) for RTASPEC xxxxxx in * * Context(xxxxxxxx) Scope(xxxxxxxx) * * failed. * * * * If there are any Monitor rules * * associated with the MAS region, message * * EYUPM0107E might be issued as well. * * * * EYUMM0601E applid Monitoring * * Specification (xxxxxxxx) failed * * to install for Context(xxxxxxxx). * * * * If the MAS region is part of workload, * * you might be able to see it from * * WLMAWTOR or WLMAWAOR view. * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves * * PH04765, all CMASes must be recycled to pick * * up the new code. Note that the restarts do * * not need to occur at the same time. * **************************************************************** During MAS initialization, method EYU0TSSC (TSSC - Topology CICS System Start Event Method Receiver) is driven on the connected CMAS to perform the topology connect process for the MAS region, including automatic resource installation and topology resource map creation. During the topology resource map creation, method EYU0TSRA (TSRA - Resource Topology Map Add) is called to construct the Resource Topology Map Lists. An EMASSTRT notification event is generated, and delivered to other components which have registered for this event. Finally TSRA calls EYU0TSCI (TSCI - Topology Autoinstall Resources) to perform bundle normalization. While TSCI waits for the PLT process to complete in the MAS, the MAS region is cancelled by the operator. The CICS PLT process is terminated. The topology connect process fails with EYUTS0002E message issued, and due to a program logic error, topology disconnect process is not driven properly. As a result, the resources created for the MAS region are not released properly. No EMASSTOP notification event is generated.
Problem conclusion
Modules EYU0TSSC and EYU0TSSE have been updated to make sure all the resources are released properly (including issuing an EMASSTOP notification event) in the case where a MAS region is cancelled during the PLT initialisation process.
Temporary fix
Comments
APAR Information
APAR number
PH04765
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
2018-11-02
Closed date
2019-06-02
Last modified date
2019-07-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI63370 UI63371
Modules/Macros
EYU0TSSC EYU0TSSE EYU9TSP3 EYU9TSP4 EYU9TSPU EYU9TSR3 EYU9TSR4 EYU9TSRU
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 July 2019