IBM Support

II14553: IEC331I 042-006(04280039) SCRT IGG0CLH0 DADSM SCRATCH ERROR DELETING PS DATA SETS USING PASS FOR JCL DISPOSITION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • INTRAN

Error description

  • STEP1 - creates sms-managed dataset with non-zero DVC
    STEP2 - runs TSO in the background (IKJEFT01)
         allocates data set SHR to a batch DD statement
            DISP=(SHR,PASS)
         runs a REXX exec which
         a. allocates the data set SHR
         b. writes to and extends the data set to another volume
         c. unallocates the data set
    
    STEP3 - runs IEFBR14 with a DD specifying the data set with
            DISP=(SHR,DELETE,DELETE)
    
    The above job setup results in the following error messages for
    STEP3 :
    IEC331I 042-006(04280039)
    IEC331I VOL,PRDS82,NAME,VPRDMIS.O.MISVBL38
    IGD17040I ERROR IN DADSM PROCESSING FOR DATA SET ....
    HISTORIC RETURN CODE IS 4 DIAGNOSTIC INFORMATION IS 04280039
    IGD306I UNEXPECTED ERROR DURING IGGDAS02 PROCESSING
    RETURN CODE 4 REASON CODE 57
    THE MODULE THAT DETECTED THE ERROR IS IGDVTSDA
    SMS MODULE TRACE BACK - VTSDA VTSCU VTSCT VTSDL DSP00 N/A
    SYMPTOM RECORD CREATED, PROBLEM ID IS ...
    
    The Dadsm Scratch error diagnostic error code 04280039 is
    described from the DFSMSdfp Diagnosis manual :
    
    |---------------------------------------------------------------
    |         DADSM SCRATCH Diagnostic Information (Register 0)
    |---------|----------|----------|----------|--------------------
    | Byte 0  | Byte 1   | Byte 2   | Byte 3   | Description
    |---------|----------|----------|----------|
    | DADSM   | Subfunc- | Subfunc- | Subfunc- |
    | Error   | tion     | tion     | tion     |
    | Code    | Identi-  | Return   | Reason   |
    |         | fier     | Code     | Code     |
    |---------|----------|----------|----------|--------------------
    | X'04'   | X'28'    | x'00'    | x'39'    | Locate volume to be
    |         |          |          |          | processed; volume
    |         |          |          |          | not mounted on any
    |         |          |          |          | online, shareable
    |         |          |          |          | DASD unit.
    |---------------------------------------------------------------
    
    The scratch error occurs because the JFCB for the data set in
    STEP3 only contains the first volser; not the second volser on
    which the data set was extended to.  This is caused by the PASS
    disposition used on the DD statement which allocates the dataset
    on STEP2.  The dynamic allocation done on behalf of the REXX
    program will create an entirely separate SIOT/JFCB pair.
    
    
    Thus when the data set is extended, the volser(s) get placed
    in this JFCB and not the one associated with the batch allocated
    DD statement.  At the end of STEP2 the batch allocated DD is
    PASSed, allowing its information to be available for later steps
    to reference.
    
    When STEP3 runs, its reference to the data set matches the
    data set name which was passed, and the SIOT/JFCB information
    from the passed data set is copied to the SIOT/JFCB for the DD
    in STEP3.  The end result is STEP3 having a JFCB with only the
    first volume in it.
    

Local fix

  • Change DISP=(SHR,PASS) to DISP=SHR in STEP2 .
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II14553

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-02

  • Closed date

  • Last modified date

    2012-08-30

  • 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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","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":"001","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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
30 August 2012