IBM Support

PH10634: ACBGEN WITH IMS CATALOG POPULATE TAPE ERROR ON IEFRDER IECTMS3 IS NOT SCRTCH (64) AND IEFTMS50 7XX- 04 ISSUED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer was testing running the IMS ACBGEN with Catalog
    Populate utility (DFS3UACB) in DL/I mode and received the
    following tape error on the DL/I logs:
    
    IECTMS3 1A1F,116682,IS NOT SCRTCH (64)
    IEFTMS50 7XX- 04 @OOACBAF,ACB$CAT ,IEFRDER ,1A1F,116682,
    00001,AF.D19064.T115854
    
    The RC64 on the IECTMS3 is indicating the tape is not scratch
    although the tape was mounted OK. According to the messages,
    the mount request was for PRIVAT:
    11.59.11 J0542353  IEF233A M 1A1F,PRIVAT,SL,@OOACBAF,ACB$CAT,
                       TSTOO.#IMS.SPLXB.CLP.@OOACBAF.D19064.T115854
    .
    A note on the IECTMS3 message also states:
          "Note: A double OPEN causes a NOT SCRATCH 60 or 64."
     Additional comment from customer:
    "I believe this is what's going on....
    It looks like from the Job Log that IMS is actually invoked
    twice during the ACBGEN w/Populate process.
    You can't do this with tape because our environment does NOT
    allow non-scratch tapes to be overwritten.
    
    This is not an issue with DASD logs because the dataset can
    be overwritten without any issues or problems.
    
    We need to write the logs to tape to avoid the possibility
    of getting an out-of-space abend during the Catalog Update
    which then would require us to have to mess around with
    Batch Backout.
    
    I don't think that IMS is actually updating anything with the
    first invocation so the logs are not really needed.
    It seems like IBM needs a way dynamically not to use the
    logs on the first invocation of IMS."
    
    This problem has been recreated by IMS Development at SVL.
    Initial findings reveal when GSAM is involved, we are using the
    same log data set for two 'utilities' and the second writes over
    the data of the first.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IMS V15 Managed ACBs Catalog Populate utility using GSAM     *
    * resources                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The Catalog Populate utility, DFS3PU00, runs with            *
    * MANAGEDACBS=STAGE or MANAGEDACBS=UPDATE mode either natively *
    * or as DFS3UACB utility fails because IEFRDER batch log using *
    * tape data set is not a scratch data set and the customer's   *
    * shop does not allow writing to non-scratch tape log data     *
    * sets                                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * INSTALL CORRECTIVE SERVICE FOR APAR/PTF                      *
    ****************************************************************
    The Catalog Populate utility, DFS3PU00, running as one or more
    tasks in sequence using PSB DFSCP001 in DLI mode uses the same
    batch log specified in DDNAME IEFRDER.  Since there is only one
    IEFRDER batch log data set, one or more DFS3PU00 tasks write to
    the same batch log data set.  Subsequent task that requires
    logging writes over log records written by the previous task.
    -----
    When DFS3PU00 runs in update mode, MANAGEDACBS=STAGE or
    MANAGEDACBS=UPDATE, it runs either as a single task or multiple
    tasks depending on whether GSAM resources are included.  When
    GSAM resources are included, DFS3PU00 update mode reuses the
    IEFRDER batch log data set.
    - If no GSAM resources, DFS3PU00 update mode runs as a single
    task and uses the IEFRDER batch log data set.
    - If GSAM resources, DFS3PU00 update mode runs as multiple tasks
    in sequence and the tasks share the same IEFRDER batch log data
    set.
    
    Additional Keywords: IMSMGDACBS/K
    

Problem conclusion

  • The Catalog Populate utility has been modified to address the
    reported problem when DFS3PU00 utility is run in update mode
    MANAGEDACBS=STAGE or MANAGEDACBS=UPDATE with GSAM resources
    using PSB DFSCP001 in DLI mode.
    -----
    New parameter GSAMPCB is added to the
    MANAGEDACBS=(STAGE|UPDATE,LATEST|UNCOND,GSAMPCB) control
    statement to show GSAM resources are  included.  In addition,
    APAR PI96542  adds new parameter GSAM=gsamdbd to the
    MANAGEDACBS=(STAGE|UPDATE,GSAM=gsamdbd) control statement for
    GSAM database resource to be added or changed without rebuilding
    its corresponding PSBs.   Both parameters GSAMPCB and
    GSAM=gsamdbd specified in the MANAGEDACBS= control statement for
    STAGE or UPDATE indicate GSAM resources.  In this case, the
    catalog members information gather task does not use the IEFRDER
    batch log data set.  After ACBGEN for GSAM resources task
    completion,  the catalog update task writes to the IEFRDER batch
    log data set for catalog database  changes.  The GSAMPCB
    parameter bypasses logging for the catalog members information
    gather task and logging is only done by the catalog update task.
    -----
    The following modules and macro have been changed:
    DFS3PU00:
    - Add GSAMPCB parameter for
    MANAGEDACBS=(STAGE|UPDATE,LATEST|UNCOND,GSAMPCB) to DLI mode.
    - If GSAMPCB or GSAM=gsamdbd specified in update mode, the
    catalog members information gather task is created without batch
    logging.
    - If GSAM resources is not found, issue new message DFS4899W and
    the Catalog Populate utilty continues without batch logging.
    DFSPCC30:
    - If the catalog populate no batch log request, set flag
    RCATNLOG to be examined at batch log initialization.
    DFSXLGI0:
    - If catalog populate no batch log request, bypass batch log
    initialization.
    PARMBLK:
    - New flag RCATNLOG to indicate catalog populate no batch log.
    -----
    A request for publication change to Release Planning (
    GC27679400 ), System Utilities ( SC27679800 ) and Messages and
    Codes, Volume 1, DFS Messages (GC27678900):
    
    GC27679400 Release Planning
    - Add Catalog Populate utility batch logging enhancement for
    GSAM resources.
    SC27679800 System Utilities under Catalog Populate utility
    - Add new parameter GSAMPCB to
    MANAGEDACBS=(STAGE|UPDATE,LATEST|UNCOND,GSAMPCB).
    GC27678900 Messages and Codes, Volume 1, DFS Messages
    - Add new message DFS4899W GSAMPCB SPECIFIED ON THE MANAGEDACBS
    CONTROL STATEMENT BUT NO GSAM RESOURCES FOUND.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH10634

  • Reported component name

    IMS V15

  • Reported component ID

    5635A0600

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-04

  • Closed date

    2020-05-19

  • Last modified date

    2020-06-01

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

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

    UI69598

Modules/Macros

  • DFS3PU00 DFSPCC30 PARMBLK  DFSXLGI0
    

Publications Referenced
GC27679400SC27679800GC27678900  

Fix information

  • Fixed component name

    IMS V15

  • Fixed component ID

    5635A0600

Applicable component levels

  • R500 PSY UI69598

       UP20/05/20 P F005

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPH2","label":"IMS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"15","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
22 December 2023