IBM Support

PI73764: Z/OSMF CONFIGURATION WORKFLOW FAILS WITH "AN EXCEPTION OCCURRED WHILE ALLOCATE THE PARTITION DATA SET..." BPXWDYN FAILED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • "An exception occurred while allocate the partition data set
    XXXXX.YYYYY.ZZZZZ, on volume U.  BPXWDYN failed;
    S99ERROR/S99INFO = 0x218/0x0 RC=35127296 (0x2180000)"
     An exception occurred while allocate the partition data set
    XXXXX.YYYYY.ZZZZZ, on volume U.  BPXWDYN failed;
    S99ERROR/S99INFO = 0x218/0x0 RC=35127296 (0x2180000)
    
    The exact volume name and specific error text may differ. In the
    above case, the issue is due to the volume name U$XYZX. This
    error was intially discovered in Configuration Workflow step 2.1
    but may occur in other places due to similar circumstances.
    
    The issue is caused by the $ charecter. In REXX, the $ is not a
    special charecter, so it is substituted to the bpxwunix
    invocation without a problem. However, $ denotes the start of a
    variable substitution. So the $ and the rest of the charecters
    in the string are ignored.
    
    Specifically in this case, the string substitution isn't
    sanitized, so the variable subsitution is attempted, resulting
    in the error.
    

Local fix

  • Perform the workflow step using a volume with a $ in the name.
    The step work can also be done outside of workflows and the step
    marked as skipped. The steps for manually adding plugins are
    found in Appendix B of the V2R2 configuration guide or Appendix
    C of the V2R1 configuration guide.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM z/OSMF V2R2 and V2R1        *
    ****************************************************************
    * PROBLEM DESCRIPTION: An exception occurred in some steps     *
    *                      of z/OSMF Configuration Workflow when   *
    *                      allocate the partition data set on      *
    *                      the volume whose name contains $.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An exception occurred in some steps of z/OSMF Configuration
    Workflow when allocate the partition data set on the volume
    whose name contains $.
    This is due to z/OSMF Configuration Workflow couldn't process
    the variables which include $ character.
    
    This APAR provides the fix that checks all the variables which
    include $ to make sure them not be truncated, and can be run
    as expected.
    

Problem conclusion

Temporary fix

Comments

  • See Problem Description.
    

APAR Information

  • APAR number

    PI73764

  • Reported component name

    Z/OSMF CORE

  • Reported component ID

    5655S28SM

  • Reported release

    220

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-14

  • Closed date

    2017-03-23

  • Last modified date

    2017-05-01

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

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

    UI45795 UI45796

Modules/Macros

  • IZUGNAFT IZUGNAFY
    

Fix information

  • Fixed component name

    Z/OSMF CORE

  • Fixed component ID

    5655S28SM

Applicable component levels

  • R210 PSY UI45795

       UP17/04/12 P F704

  • R220 PSY UI45796

       UP17/04/12 P F704

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.

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

Document Information

Modified date:
01 May 2017