IBM Support

PH12906: DOC GDPS GM 4.2 ENABLE(PPRCMT) IN DEVSUPXX IS REQUIRED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • After starting GDPS Global - GM 4.2 "z/OS Device Support for
    Multi Target is not ENABLED in system <sysname>" is seen when
    the customer is displaying a script. The script is not allowed
    to execute.
    
    Section 2.2.1 GDPS and Multi-target PPRC considerations of
    GDPS Global - GM V4R2 Installation and Customization Guide
    need to point out ENABLE(PPRCMT) is required instead of DISABLE.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * GDPS GM 4.2 users                                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * A documentation update is needed to indicate that            *
    * ENABLE(PPRCMT) in PARMLIB member DEVSUPxx is needed for GDPS *
    * Global - GM GM2SITE at level 4.2                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Updates to "GDPS Global - GM V4R2 Installation and Customization
    Guide", ZG24-6757
    
    1.5.1 Migration to GDPS Global - GM 4.2
    Addition:
    Enable PPRCMT in DEVSUPxx
    
    Specify ENABLE(PPRCMT) in your DEVSUPxx member of your PARMLIB
    on both GDPS GM controlling systems. You can dynamically
    activate it with SET DEVSUP=xx .
    
    Change the text for
    2.2.1 GDPS and Multi-target PPRC considerations
    to:
    GDPS GM from 4.2 need multi-target PPRC in the DEVSUPxx member
    to be enabled. If you plan to establish any multi-target
    relationships for devices that GDPS is managing you also need to
    specify topology GM2SITE suboption MTFO(YES) in GDPS options.
    Otherwise if you do establish any multi-target relationships for
    devices that GDPS is managing, GDPS will not function correctly.
    
    Addition:
    3.1.9 DEVSUPxx customization
    In order for GDPS to initialize you must specify ENABLE(PPRCMT)
    in the DEVSUPxx member of your PARMLIB on both GDPS GM
    controlling systems.
    
    Note this option must be enabled regardless of the hardware
    capability to support Multi Target.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH12906

  • Reported component name

    GDPS

  • Reported component ID

    694235B00

  • Reported release

    420

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-06-04

  • Closed date

    2019-12-18

  • Last modified date

    2019-12-23

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

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

Fix information

Applicable component levels

[{"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":"420","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
23 December 2019