IBM Support

PI20593: GCLMDA04E ALLOCATION FAILED WITH COPY-IF-NO-IMS-TARGET-DB(Y)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • We run database refresh (IMSDBREFRESH) for HIDAM database using
    COPY-IF-NO-IMS-TARGET DB(Y) to define elements for target
    database which is not defined. When processing to create MDA
    member for ICTDB1 database, "GCLMDA04E Allocation failed for
    dsn: IMS.V1110.SDFSMAC" was issued. MDA assembly processing
    needs SDFSMAC library and SYS1.MACLIB as SYSLIB, but the SDFSMAC
    library name is hard coded with IMS.V1110.SDFSMAC.
    Since our SDFSMAC library name is not IMS.V1110.SDFSMAC,
    "GCLMDA04E Allocation failed" was issued. I added SDFSMAC
    library to SYSLIB DD and rerun the job. Then, "GCLMDA06E MDA
    ASSEMBLY failed" was issued because MDA assembly processing also
    need SYS1.MACLIB, but SYS1.MACLIB was not concatenated to
    SYSLIB. Then, "GCLMDA05E ALLOCATION failed for DDname: SYSLIB"
    was issued. Finally, I added PROCLIB DD, but the result was
    same.
    

Local fix

  • When I changed our SDFSMAC library name to IMS.V1110.SDFSMAC,
    creating MDA member was completed successfully,  BUT it is not
    acceptable.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IMS Cloning Tool V1.2               *
    ****************************************************************
    * PROBLEM DESCRIPTION: GCLMDA04E  ALLOCATION FAILED WITH       *
    *                      COPY-IF-NO-IMS-TARGET-DB(Y)             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    User runs database refresh (IMSDBREFRESH) for HIDAM database
    using COPY-IF-NO-IMS-TARGET DB(Y) to define elements for target
    database which is not defined. When processing to create MDA
    member for ICTDB1 database, "GCLMDA04E Allocation failed for
    dsn: IMS.V1110.SDFSMAC" was issued. MDA assembly processing
    needs SDFSMAC library and SYS1.MACLIB as SYSLIB, but the SDFSMAC
    library name is hard coded with IMS.V1110.SDFSMAC.
    Since the SDFSMAC library name is not IMS.V1110.SDFSMAC,
    "GCLMDA04E Allocation failed" was issued. Added SDFSMAC
    library to SYSLIB DD and rerun the job. Then, "GCLMDA06E MDA
    ASSEMBLY failed" was issued because MDA assembly processing also
    need SYS1.MACLIB, but SYS1.MACLIB was not concatenated to
    SYSLIB. Then, "GCLMDA05E ALLOCATION failed for DDname: SYSLIB"
    was issued. Finally, added PROCLIB DD, but the result was
    same.
    

Problem conclusion

  • Code has been modified to correct the above issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI20593

  • Reported component name

    IMS CLONING TOO

  • Reported component ID

    5655U9100

  • Reported release

    120

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-23

  • Closed date

    2014-07-29

  • Last modified date

    2014-08-04

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

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

    UI20076

Modules/Macros

  •    GCLMDA   GCL00349
    

Publications Referenced
SC19247500    

Fix information

  • Fixed component name

    IMS CLONING TOO

  • Fixed component ID

    5655U9100

Applicable component levels

  • R120 PSY UI20076

       UP14/08/01 P F407

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCBTY5","label":"IMS Cloning Tool"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.2.0"}]

Document Information

Modified date:
21 October 2020