IBM Support

OA51143: HCD MIGRATION ACTIONS FOR IO PATH REPORT MISSING

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as documentation error.

Error description

  • With HCD 2.1 the behavior of the I/O Path report has changed
    compared to HCD 1.13. When TSA IO operations is not installed
    or
    working, HCD tries to exploit a new function Discovery and
    Autoconfiguration, which in turn needs specific authorization.
    Migration actions for this report are not described.
    
    External Symptoms:
    If TSA is not installed or running and the authorization
    necessary for harware activate is not given, the job will
    fail with RC 8.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All HCD users requesting an HCD I/O          *
    *                 Path report and migrating from z/OS          *
    *                 V1R13 or below to z/OS V2R1 or above         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Change of HCD behavior generating I/O   *
    *                       Path report.                           *
    *                                                              *
    *                      HCD allows you to check the             *
    *                       definitions in your IODF against the   *
    *                       actual configuration as sensed from    *
    *                       the active system. This function       *
    *                       is called "Verify  Configuration"      *
    *                       and provided as an I/O Path report.    *
    *                       It shows the sensed I/O paths of an    *
    *                       active system and compares this data   *
    *                       with the definitions in the IODF.      *
    *                                                              *
    *                      Prior to z/OS V2R1 (aka in HCD version  *
    *                       1), the I/O Operations component of    *
    *                       System Automation for z/OS (formerly   *
    *                       known as ESCON Manager) must be        *
    *                       installed and active for the "Verify   *
    *                       Configuration" functionality to        *
    *                       retrieve information from the active   *
    *                       system.                                *
    *                                                              *
    *                      If this requirement is not satisfied,   *
    *                       the error message CBDG133I is issued   *
    *                       in the HCDMLOG when generating the     *
    *                       I/O PATH REPORT and only the defined   *
    *                       data in the IODF is printed with *     *
    *                       indication in the column D.            *
    *                                                              *
    *                      MSGCBDG133I I/O Operations processing   *
    *                       completed unsuccessfully. Return code  *
    *                       = 20 and reason code = 300D0004.       *
    *                       IHVU029I I/O-OPS IS NOT OPERATIONAL    *
    *                                                              *
    *                      Beginning with z/OS V2R1 (aka in HCD    *
    *                       version 2), you can now verify the     *
    *                       active or target configuration by      *
    *                       means of z/OS discovery and I/O        *
    *                       Autoconfiguration (zDAC), if Tivoli    *
    *                       System Automation (TSA) I/O            *
    *                       operations is not installed or not     *
    *                       working. This is possible for          *
    *                       a processor after the z196 and z114    *
    *                       generations supporting zDAC and for a  *
    *                       system in the local sysplex, which is  *
    *                       capable for dynamic activates. The     *
    *                       verification is limited to FICON       *
    *                       attached storage devices.              *
    *                                                              *
    *                      With HCD 2.1, the behavior of the I/O   *
    *                       Path report has changed compared to    *
    *                       HCD 1.13. When TSA IO operations is    *
    *                       not installed or working, HCD tries    *
    *                       by default to exploit a new function   *
    *                       via  zDAC to generate the Sensed       *
    *                       data, which in turn needs specific     *
    *                       authorization.                         *
    *                      Only when the RACF OPERCMDS class is    *
    *                       activated and RACLISTed, the           *
    *                       MVS.ACTIVATE                           *
    *                       profile is defined, and the user who   *
    *                       generates I/O Path report has an       *
    *                       UPDATE access authority to the         *
    *                       profile, the                           *
    *                       "Verify Configuration" functionality   *
    *                       via zDAC will be successful.           *
    *                                                              *
    *                      Example of RACF definitions:            *
    *                                                              *
    *                       SETR CLASSACT(OPERCMDS)                *
    *                       RDEFINE OPERCMDS MVS.ACTIVATE          *
    *                       UACC(NONE)                             *
    *                       PERMIT MVS.ACTIVATE CL(OPERCMDS)       *
    *                       ID(user1) ACCESS(UPDATE)               *
    *                       SETR RACLIST(OPERCMDS) REFRESH         *
    *                                                              *
    *                      Replace user1 with the user name of     *
    *                       the person running the report.         *
    *                                                              *
    *                      Otherwise, the error messages           *
    *                       MSGIOS530I and MSGCBDG905I will be     *
    *                       displayed in the HCDMLOG:              *
    *                                                              *
    *                      IOS530I DISCOVERY AND AUTOCONFIG        *
    *                              PROCESSING WAS UNSUCCESSFUL     *
    *                              REASON=01E7,AUTHORIZATION       *
    *                              COULD NOT BE DETERMINED         *
    *                              DESCTEXT=RACROUTE RETURN        *
    *                              CODE: 04, REASON CODE           *
    *                              00000000 COMPID=SC1C3           *
    *                      CBDG905I Service invoked by module      *
    *                       CBDMGIAC was not successful. Return    *
    *                       code = 12, reason code = 0, error      *
    *                       information: 0, 0.                     *
    *                                                              *
    *                      Note: zDAC will temporarily change the  *
    *                       I/O configuration to do the "Verify    *
    *                       Configuration" functionality, so this  *
    *                       should require update access. If the   *
    *                       RACROUTE fails for any reason, the     *
    *                       request is rejected.                   *
    *                                                              *
    *                      The IO Path report contains two parts,  *
    *                       one containing the defined             *
    *                       configuration, the other containing    *
    *                       sensed information.                    *
    *                       If TSA is not installed or             *
    *                       working, HCD tries by default to use   *
    *                       discovery via zDAC to fill the sensed  *
    *                       information. If discovery fails (e.g.  *
    *                       because of missing authorization or    *
    *                       other                                  *
    *                       reasons), HCD returns with job step    *
    *                       condition code 8, but still writes     *
    *                       thereport describing the defined       *
    *                       configuration.                         *
    *                                                              *
    *                      For further details about job step      *
    *                       return handling, refer to APAR         *
    *                       OA51144 (APAROA51144).                 *
    ****************************************************************
    * RECOMMENDATION: Read the description and prepare for the     *
    *                 migration accordingly                        *
    ****************************************************************
    Change of HCD behavior generating I/O Path report. Missing
    information in z/OS Migration book.
    

Problem conclusion

  • Additional migration information provided using this APAR and
    close as DOC
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA51143

  • Reported component name

    MVS/HCD

  • Reported component ID

    5695SC1XL

  • Reported release

    790

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-08-24

  • Closed date

    2016-09-12

  • Last modified date

    2016-09-12

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

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

Publications Referenced
GA32088904    

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":"790","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"790","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 September 2016