PM85960: RDZ ENHANCEMENT: ALLOCATE DIFFERENT CARMA DATASETS BASED ON CLIENT VERSION

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A customer has various RDz client levels, and various host
  levels active on multiple machines.
  The customer is unable to apply the compatibilty fixes so that
  all clients and hosts can work with each other for the CARMA
  component of RDz.
  This enhancement allows the CARMA miner to determine the client
  version, and pass this info to the routine that starts the CARMA
  server, which in turn can allocate the datasets required for
  that client level.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: 01.CARMA administrators and CARMA RAM        *
  *                    developers.                               *
  *                 02.RDz system administrator                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: 01.Enhancement to pass client version   *
  *                         and user exit invocation information *
  *                         to CARMA startup and CARMA RAM.      *
  *                      02.enhancement to allow execution of a  *
  *                         user exit during CARMA server        *
  *                         startup                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  01.Enhancement to pass client version and user exit invocation
     information to CARMA startup and CARMA RAM. CARMA startup
     and configuration files are enhanced to accept up to 8
     arguments, of which currently 4 are used (port, timeout,
     user exit and client version). CARMA startup also places this
     data in a new DD, CRAPARM, to allow a RAM to access the data.
  02.enhancement to allow execution of a user exit during CARMA
     server startup.
     CRASRV.properties has a new directive to specify the
     exit: #user.exit = 'FEK.SFEKSAMP(CRAEXIT)'
  
     #user.exit
     Defines the user-exit invoked by the CRAALLOC / CRANDVRA
     allocation execs. A sample user-exit is provided as
     FEK.SFEKSAMP(CRAEXIT). Uncomment and specify the name of
     the user-exit. When not enclsoed in quotes, the client
     userid will be used as high level qualifier prefix.
  

Problem conclusion

• 01.Enhancement to pass client version and user exit invocation
     information to CARMA startup and CARMA RAM. CARMA startup
     and configuration files are enhanced to accept up to 8
     arguments, of which currently 4 are used (port, timeout,
     user exit and client version). CARMA startup also places this
     data in a new DD, CRAPARM, to allow a RAM to access the data.
  02.enhancement to allow execution of a user exit during CARMA
     server startup.
     CRASRV.properties has a new directive to specify the
     exit: #user.exit = 'FEK.SFEKSAMP(CRAEXIT)'
  
     #user.exit
     Defines the user-exit invoked by the CRAALLOC / CRANDVRA
     allocation execs. A sample user-exit is provided as
     FEK.SFEKSAMP(CRAEXIT). Uncomment and specify the name of
     the user-exit. When not enclsoed in quotes, the client
     userid will be used as high level qualifier prefix.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• CRAEXIT  CRAMAJAR CRANDVRA CRAREXX  CRASCFCA
  CRASCONF CRASRV   FEKFMAIN FEKFMAI6 FEKFMINE FEKFZOS
  

Fix information

• Fixed component name

  RD/Z HOST

• Fixed component ID

  5724T0723

Applicable component levels

• R801 PSY UK96308

     UP13/08/05 I 1000

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.