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

A fix is available

Subscribe

You can track all active APARs for this component.

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.All of RDz users                          *
    *                 02.RDz system administrator                  *
    *                 03.CARMA administrators and CARMA RAM        *
    *                    developers.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: 01.Sometimes GC doesn't clean up        *
    *                         everything and it needs more runs.   *
    *                         It's useful for operator to run GC   *
    *                         manually to confirm if the heap can  *
    *                         be freed by more GCs.                *
    *                      02.enhancement to allow execution       *
    *                         of a user exit during CARMA server   *
    *                         startup                              *
    *                      03.Enhancement to pass client version   *
    *                         and user exit invocation information *
    *                         to CARMA startup and CARMA RAM.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    01.Sometimes GC doesn't clean up everything and it needs more
       runs. It's useful for operator to run GC manually to confirm
       if the heap can be released by more GCs.
    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.
    03.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.
    

Problem conclusion

  • 01.Now, a new operator command is supported to run GC: /F
       rsed,APPL=DEBUG GC,PID=process_id
    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.
    03.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.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM85959

  • Reported component name

    RD/Z HOST

  • Reported component ID

    5724T0723

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-29

  • Closed date

    2013-10-16

  • Last modified date

    2013-10-31

  • 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   FEKFMINE FEKFZOS
    

Fix information

  • Fixed component name

    RD/Z HOST

  • Fixed component ID

    5724T0723

Applicable component levels

  • R850 PSY UK98515

       UP13/10/31 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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Developer for System z

Software version:

8.5

Reference #:

PM85959

Modified date:

2013-10-31

Translate my page

Machine Translation

Content navigation