A fix is available
APAR status
Closed as program error.
Error description
Normally, if an application is AVAILABLE at shutdown, it should be AVAILABLE again at startup time. But, in customer case, some applications do not become AVAILABLE on the next startup.
Local fix
NA
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: Following a restart of a CICS system, * * CICS Cloud applications deployed to * * that system are not recovered to the * * AVAILABLE state. * **************************************************************** A CICS Cloud Application includes a bundle which contains a reference to a PIPELINE as an Imported Resource. This means that the specified PIPELINE resource must be enabled in the CICS system before the bundle, and therefore the Application, can become ENABLED. The Application availability state is generally recovered across a CICS system restart. PIPELINE resources are enabled asynchronously, and may take some time after a system restart to reach the ENABLED state. When recovering a CICS Cloud Application, CICS will inspect the state of the Bundles included in that application, and so will also inspect the imported PIPELINE resource. If at this time, the PIPELINE is not yet ENABLED, for example if it is still ENABLING, then the bundle will be regarded as DISABLED. This will cause the attempt to recover the AVAILABLE state of the application to be terminated. Assuming the PIPELINE does reach the ENABLED state after this time then the Application will become ENABLED, but will not become AVAILABLE. CICS will issue message EYUBN0022W +EYUBN0022W applid CICS BUNDLE <bundle> failed to enable in time. Related application state might not be recovered. . Additional Keywords: msgEYUBN0022W BN0022W
Problem conclusion
DFHPIRL has been updated. If a PIPELINE has a state of ENABLING, then any BUNDLE which imports that PIPELINE resource will also be regarded as being in an ENABLING state (assuming no other errors cause it to become DISABLED).
Temporary fix
Comments
APAR Information
APAR number
PH08799
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-02-20
Closed date
2019-07-18
Last modified date
2019-08-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI64279 UI64280 UI64281
Modules/Macros
CJC0BNBE CJD0BNBE CJE0BNBE CJF0BNBE CJG0BNBE DFHPIRL EYU0BNBE
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R100 PSY UI64279
UP19/07/20 P F907
R10M PSY UI64280
UP19/07/20 P F907
R200 PSY UI64281
UP19/07/20 P F907
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 August 2019