IBM Support

PI62018: IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING
    

Local fix

  • IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All VTF Mainframe Release 3.0.0 users.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: IGD306I UNEXPECTED ERROR DURING         *
    *                              CBRXLCS PROCESSING              *
    *                              RETURN CODE 12 REASON CODE 69   *
    ****************************************************************
    * RECOMMENDATION: Install the latest PTF associated with this  *
    *                 APAR.                                        *
    ****************************************************************
    IGD306I UNEXPECTED ERROR DURING CBRXLCS PROCESSING messages with
    various return and reason codes are issued by jobs whose one or
    more tape allocations have been reallocated by VTFM.
    
    Consider the following job:
    
       //S1       EXEC PGM=PROG1
       //UTILX    DD  DSN=DBD1.IMAGCOPY.SYSUTILX(+1),
       //             DISP=(NEW,CATLG,DELETE),
       //             UNIT=TAPE,
       //             VOL=(,RETAIN,,99),LABEL=(01,SL)
       //S2      EXEC PGM=PROG2
       //UTILX    DD  DSN=DBD1.IMAGCOPY.SYSUTILX(+1),
       //             DISP=(OLD,KEEP)
       //DBD01    DD  DSN=DBD1.IMAGCOPY.DBD01(+1),
       //             DISP=(NEW,CATLG,DELETE),
       //             UNIT=AFF=UTILX,
       //             VOL=(,RETAIN,,99,REF=*.S1.UTILX),
       //             LABEL=(02,SL)
    
    In addition, SMS assigns a Storage Class to S1.UTILX and the
    following RULE is in effect:
    
        RULE  INC,UNIT=TAPE
    
    S1.UTILX is reallocated due to the RULE and its SMS attributes
    removed accordingly.
    S2.DBD01 is REF-ed to the same tape as S1.UTILX that is
    reallocated and allocated on same device due to its affinity to
    S2.UTILX.
    However, although the SMS attributes are propagated from
    S1.UTILX to all associated DDnames, VTFM fails to remove them.
    That in turn lets SMS try and handle S2.DBD01 as an SMS-managed
    tape causing various allocations problems.
    
    The fix lets the dynamic reallocation remove all SMS indicators
    from related VOL=REF DDnames.
    

Problem conclusion

  • Additional keywords: VTFM/K
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI62018

  • Reported component name

    SYS STOR VTF MA

  • Reported component ID

    5655V4300

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-06

  • Closed date

    2016-05-08

  • Last modified date

    2016-06-02

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

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

    UI37632

Modules/Macros

  • HVTWTO
    

Fix information

  • Fixed component name

    SYS STOR VTF MA

  • Fixed component ID

    5655V4300

Applicable component levels

  • R300 PSY UI37632

       UP16/05/10 P F605

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"300","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 June 2016