A fix is available
APAR status
Closed as program error.
Error description
In the CICS region the JVMServer was discarded. This caused the OSGi bundle parts to be set to a disabled state. Therefore, the bundle can never be enabled but is also not completely disabled (despite the external state being displayed as disabled). The bundle has to be set to a clean disabled state and then discarded and reinstalled. This situation is the same as when a bundle is installed and the required JVMSERVER is not installed. This APAR is to add new messages to say that the bundle is now in a failed state after the discard of the JVMSERVER. Setting the BUNDLE to a failed state and then needing to DISABLE, DISCARD and reinstall it is the way that bundles were designed to work when one of the individual bundle parts is now unusable.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS Users. * **************************************************************** * PROBLEM DESCRIPTION: After discarding a JVMSERVER, the * * bundles are in a failed state and the * * parts are left unusable but no message * * is issued to that fact. * **************************************************************** When a JVMSERVER is discarded, message DFHSJ0912 is issued to inform the user of the JVMSERVER being disabled. However, any bundles that will now be in a failed state, with its bundleparts unusable, do not have a message issued to advise of this fact and any required actions. When the JVMSERVER is re-installed, the bundle was attempted to be re-enabled but was found to be in the wrong state. Keyword: msgDFHSJ0912
Problem conclusion
New message DFHSJ1111 will be issued to identify the failed bundle and its parts. The message explanation in the Knowledge Center will inform the customer of the required actions. . DFHSJ1111 BUNDLE xxxxxxxx part name yyyyyyyyyyyyyyyy is now in an unusable state following the discard of JVMSERVER zzzzzzzz. Explanation JVM Server was discarded which left the BUNDLE bundlename in an unusable state. System Action bundlename is now in an unusable state. User response For the bundle to be used again the JVMSERVER jvmserver needs to be re-installed. Next, bundlename needs to be disabled and discarded and then re-installed. Module DFHSJBD
Temporary fix
Comments
APAR Information
APAR number
PH18062
Reported component name
CICS TS Z/OS V5
Reported component ID
5655Y0400
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-10-14
Closed date
2020-01-17
Last modified date
2020-02-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI67423
Modules/Macros
DFHAPJVM DFHAXIS2 DFHCDJNI DFHMESJC DFHMESJE DFHMESJK DFHSJBD DFHSJDM DFHSJDS DFHSJDUF DFHSJIN DFHSJIS DFHSJIX DFHSJJS DFHSJL DFHSJNA DFHSJNR DFHSJNT DFHSJRE DFHSJRL DFHSJRM DFHSJRT DFHSJSC DFHSJSM DFHSJST DFHSJTH DFHSJTRI DFHSJXM DFJ@H356 DFJ@H360 DFJ@H427 DFJ@H467 DFJ@H468 DFJDTCOE DFJOUTRE DFJWLPBP DFJWLPPL
Fix information
Fixed component name
CICS TS Z/OS V5
Fixed component ID
5655Y0400
Applicable component levels
R200 PSY UI67423
UP20/01/18 P F001
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.5","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.5","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
04 February 2020