PK82214: PERSISTENT JVM IN MPP/BMP/IFP REGIONS.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This service provides the support for allowing a persistent JVM
  in IMS MPP, BMP, and IFP regions.
  
  DCR KA00075
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS V10 users who invoke Java            *
  *                 applications from COBOL or equivalent        *
  *                 applications running in MPP/BMP/IFP regions  *
  *                 and who would like to issue DB2 calls from   *
  *                 this Java application                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Support a persistent JVM in MPP/BMP/IFP *
  *                      regions and support DB2 calls from a    *
  *                      Java application invoked by an          *
  *                      MPP/BMP/IFP using ESAF                  *
  ****************************************************************
  * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
  ****************************************************************
  Currently, Enterprise COBOL is leveraged as the conduit between
  the COBOL appl and the Java appl.  However, Enterprise COBOL
  creates/destroys the JVM every time the Java appl is called
  from/returns to the COBOL appl.  This causes extremely poor
  performance.  The performance gain with this support is that IMS
  now manages the JVM and therefore the JVM is only created during
  dependent region init and is only destroyed when the MPP/BMP/IFP
  region terminates.
  
  Support two new JCL parms for MPPs, BMPs, IFPs (ENVIRON= and
  JVMOPMAS=) to allow the user to specify that IMS should
  create/manage the JVM in the region.  These JCL parms are the
  same parms as those supported for JMP/JBP regions currently.
  
  There is an associated DB2 SPE with this support that will allow
  the Java application (which is invoked from the COBOL or
  equivalent application in the MPP/BMP/IFP region) to issue DB2
  JDBC calls where DB2 will use the IMS ESAF instead of RRS. Thus,
  supporting code has also been added in IMS with this SPE to
  support this DB2 SPE.  This supporting code in IMS is called the
  DB2 callbacks.  These DB2 callbacks are required by the DB2 JDBC
  Universal Driver to know when to commit/rollback/reset
  resources.
  
  The following IMS requirement is satisfied with this SPE:
  MR0114086422
  
  This service has the following software dependencies:
  
  1. z/OS 1.9 (HBB7740) or above is required
  
  2. LE (Language Environment) APAR PK99010 is required
  
  3. LE (Language Environment) APAR PM00482 is required if
     running z/OS 1.11 or above
  
  4. DB2 APAR PK93123 is required if issuing DB2 calls from the
     Java application in this environment
  

Problem conclusion

Temporary fix

Comments

• Affected Modules/Macros:
  
  DFSECP   (Dep region environment control block)
  -----------------------------------------------
  Added the ECLJAVAC bit to indicate when the callbacks should be
  invoked
  
  
  DBFIFP   (Sysgen IFP JCL)
  MSGJCL   (Sysgen MPP/BMP JCL)
  -----------------------------------------------
  Added ENVIRON= and JVMOPMAS= parms
  
  
  PARMBLK  (Dependent region parameter block)
  -----------------------------------------------
  Added subfunction codes for DB2 callbacks and depdendent region
  codes to the parm list for DFSJVM00.  Added new field PCJVM00 to
  contain EPA of DFSJVM00 for DB2 callbacks.
  
  
  DFSJVM00 (JVM Processor)
  -----------------------------------------------
  Added function 2 for DB2 callbacks and added code to recognize
  MPP/BMP/IFP regions
  
  
  DFSPCC20 (MPP/BMP/IFP program controller)
  DFSRRC10 (MPP/IFP region controller)
  DFSRRC40 (BMP region controller)
  DFSRRA40 (Dep region parm analysis)
  -----------------------------------------------
  Added supporting code for ENVIRON= and JVMOPMAS= parm
  recognition to create the LE enclave/JVM environment in which to
  execute the COBOL or equivalent application
  
  
  DFSTMPR0 (non-IFP program request handler)
  DBFFPPR0 (IFP program request handler)
  -----------------------------------------------
  Added logic to issue the appropriate DB2 callback, either
  commit() or rollback(), depending on the IMS DLI call from the
  application (eg.  GU, CHKP, ROLB, etc)
  
  
  DFSPCJM0 (JMP program controller)
  -----------------------------------------------
  Removed the internal logic that destroyed the JVM every 256
  schedules
  
  
  DFSPCJB0 (JBP program controller)
  -----------------------------------------------
  Added code to zero field PCJVMBM for explicit LE enclave
  termination
  
  
  DFSRCJB0 (JBP region controller)
  DFSRCJM0 (JMP region controller)
  -----------------------------------------------
  Added logic to zero new field PCJVM00 in PXPARMS
  
  
  ********************** DOC CHANGES ***************************
  
  RPG, GC18971701
  
  Add the following text in a new topic in the Release planning
  Guide under "Overview of IMS Version 10 enhancements > IMS
  system (DB and enhancements)":
  
  Dependent region enhancements
  
  Prior to these enhancements, the Java Virtual Machine (JVM) used
  in BMP, IFP, and MPP regions is always managed by IBM Enterprise
  COBOL for z/OS and the JVM is created and destroyed the JVM
  every time the Java application is called from or returns to the
  COBOL application.
  
  IMS is now capable of managing the JVM for these regions.  IMS
  creates the JVM when the dependent region is inititialized and
  only destroys the JVM when the region terminates.
  
  To specify that IMS should create and manage the JVM in the
  region, use the new ENVIRON and JVMOPMAS parameters in the
  DFSMPR, IMSFP, or IMSBATCH procedures.  These JCL parms are the
  same parameters as those supported for JMP and JBP regions.
  
  There is an associated DB2 for z/OS enhancement with this
  support that allows the Java application (which is invoked from
  the COBOL or equivalent application in the MPP, BMP, or IFP
  region) to issue DB2 JDBC calls where DB2 will use the IMS ESAF
  instead of RRS.
  
  The IMS dependent region enhancements have the following
  software requirements:
  
   1. z/OS 1.9 (HBB7740) or above is required
  
   2. LE (Language Environment) APAR PK99010 is required
  
   3. LE (Language Environment) APAR PM00482 is required if
      running z/OS 1.11 or above
  
   4. DB2 for z/OS APAR PK93123 is required if issuing DB2 calls
      from the Java application in this environment
  
  
  System Definition Reference, GC18996600
  
    Section: Parameter descriptions for IMS procedures
  
    For JVMOPMAS and ENVIRON parms, indicate that these two parms
    can be specified for non-Java dependent regions (MPPs, BMPs,
    IFPs) as well in order to instruct IMS to create and manage
    the JVM in an MPP, BMP, IFP region.
  
  
    Sections: DFSMPR, IMSFP, IMSBATCH procedures
  
    Indicate JVMOPMAS and ENVIRON parms can be specified
  
  
  Messages and Codes Reference, Volume 3: IMS Abend Codes,
  GC18971401
  Chapter 4: 0101 abend
  
     Update the explanation to indicate that this abend can occur
     for non-Java dependent regions as well (MPP, BMP, IFP
     regions) . And, add DFSRRC10, DFSRRC40, and DFSPCC20 to the
     list of issuing modules.
  
     Add the following tables:
  
     For DFSRRC10, DFSRRC40
       This is a standard abend issued by DFSRRC10, DFSRRC40
       Key        Label           Description
       Reg15=X'4'                 Required JVMOPMAS=member not
                                  specified.
  
       Reg15=X'6'                 BPX1SDD failed.
       Reg3=BPX1SDD return code
       Reg4=BPX1SDD reason code
  
  
     For DFSPCC20
       This is a standard abend issued by DFSPCC20
       Key        Label           Description
       Reg15=X'1'                 Unable to create LE enclave
                                  (CEEPIPI error)
       Reg3=CEEPIPI return code
  
       Reg15=X'2'                 Unable to create JVM
       Reg3=possible CEEPIPI return code
  
       Reg15=X'3'                 JVM unable to invoke appl
                                  (CEEPIPI error)
       Reg3=possible CEEPIPI return code
  
       Reg15=X'5'                 Unable to add entry
                                  (CEEPIPI error)
       Reg3=possible CEEPIPI return code
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PM00360 UK58284

Modules/Macros

• DBFFPPR0 DBFIFP   DFSASK00 DFSDDEF1 DFSECP
  DFSECP10 DFSJVM00 DFSPCC20 DFSPCJB0 DFSPCJM0 DFSRCJB0 DFSRCJM0
  DFSRRA00 DFSRRA40 DFSRRC10 DFSRRC40 DFSSSOB  DFSTMPR0 MSGJCL
  PARMBLK
  

Fix information

• Fixed component name

  IMS V10

• Fixed component ID

  5635A0100

Applicable component levels

• R010 PSY UK58284

     UP10/07/24 P F007

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.