IBM Support

OA68759: IGD306 RC08 RSN12011 FOLLOWED BY S0F4 WHEN COMMENTING A LINE IN THE SEPARATION PROFILE DATASET

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Separation profile data set was defined with a line comment
    without a continuation character:
    SEP(VOL) -
      TYPE(PREF) -
      DSN(dsname1,-
          dsname2,-
          *  COMMENT -*
          dsname3,-
          dsname4);
    
    In the IPL, during SMS initialization, customer received the
    following messages:
    IGD306I UNEXPECTED ERROR DURING IGDMCSCM PROCESSING RETURN CODE
    8 REASON CODE 12011
    THE MODULE THAT DETECTED THE ERROR IS IGDMCSCM
    SMS MODULE TRACE BACK - MCSCM OPST2 OPST1
    .
    IGD300I AN ABEND OCCURRED DURING SMS PROCESSING   ABEND SYSTEM
    CODE=0F4 ASID=0025
     COMPONENT NAME=SMS COMPONENT ID=DF101
     ACTIVE LOAD MODULE NAME=IGDZILLA ADDRESS=06211000
    
     CSECT IN ERROR  DESCRIPTION=MAIN BUILD MSG RTN
                     NAME=IGDMCSCM
    
    ADDITIONAL SYMPTOMS:
    MSGIGD306I RC08 RSN12011
    ABEND0F4 in IGDERDAC
    

Local fix

  • BYPASS/CIRCUMVENTION:
    Delete the comment line or add the comment in a valid line:
    SEP(VOL) -
      TYPE(PREF) -
      DSN(dsname1,-
          dsname2,-  *  COMMENT -*
          dsname3,-
          dsname4);
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: HDZ3310 Users and above                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    SUMMARY:
    During parsing a comment block for the data set separation
    profile syntax, the logic used the wrong flag and did not
    detect the comment block end, which caused the next keyword not
    to be recognized.
    Additionally, before building an error message for the data set
    separation profile processing, the message pointer is not
    initialized, which caused the reason code 12011, and ABEND0F4
    occurred.
    

Problem conclusion

Temporary fix

Comments

  • CONTROL NUMBER: ZSMS-622
    This APAR is being closed FIN with concurrence from the
    submitting customer. This means that a solution to this APAR
    is expected to be delivered from IBM in a release (if any)
    to be available within the next 36 Months.
    

APAR Information

  • APAR number

    OA68759

  • Reported component name

    STORAGE MGMT SU

  • Reported component ID

    5695DF101

  • Reported release

    310

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-11-12

  • Closed date

    2026-03-30

  • Last modified date

    2026-04-01

  • 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":"BU029","label":"Software"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"310"}]

Document Information

Modified date:
01 April 2026