PM80291: UNLOAD UTILITY EXECUTED VIA DSNUTILS , AFTER GETTING AN ABENDD37 ON THE OUTPUT DATASET, THE DATASET IS NOT DEALLOCATED

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Unload from table executed via DSNUTILS, if we have a failure
    When Unload from table is executed via DSNUTILS, if there is a
    failure on the output data set (i.i. ABENDD37), this one is
    not deallocated after utility termination, but it is kept until
    the WLM address space is either refreshed or cancelled.
    

Local fix

  • Refresh the WLM application environment after terminating the
    utility.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS       *
    *                 utility users of the DSNUTILU or DSNUTILS    *
    *                 utility stored procedure                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Data sets that are dynamically          *
    *                      allocated by utilities being executed   *
    *                      from either the DSNUTILU or DSNUTILS    *
    *                      stored procedure are not being          *
    *                      deallocated when the utility abnormally *
    *                      terminates.                             *
    ****************************************************************
    * RECOMMENDATION: Apply corrective PTF when available          *
    ****************************************************************
    The UNLOAD utility was invoked from a utility stored procedure
    and abnormally terminated because the dynamically allocated
    output data set (SYSREC) was too small.  The recovery routine
    failed to deallocate the SYSREC data set resulting in the WLM
    address space needing to be either refreshed or cancelled
    to deallocate it.
    

Problem conclusion

  • The utility recovery routine is fixed to dynamically deallocate
    any files that were dynamically allocated by the utility when
    the utility is called by a stored procedure.
    
    However, with this change, the utility needs to ensure that it
    is the only task running in the WLM-managed address space.
    
    DB2 for z/OS documents this requirement as NUMTCB=1 when
    running in a WLM-managed address space.
    
    PM80291 introduces the following new message when the utility
    detects that the WLM managed address space had been started
    with NUMTCB<>1:
    
    DSNU022I
    csect-name -  A UTILITY RUNNING UNDER A STORED PROCEDURE
    REQUIRES A WLM ENVIRONMENT WITH NUMTCB=1. UTILID utility-ID IS
    RUNNING WITH NUMTCB = tcb-number.
    
    Explanation
    When the utility stored procedure invoked a utility, the stored
    procedure was running in a stored procedure address space that
    was started with NUMTCB>1. The stored procedure address space in
    which the utility stored procedure runs must be started with
    NUMTCB=1 be started with NUMTCB=1.
    
    csect-name
    The name of the control section that issued the message.
    
    utility-ID
    The utility identifier or the UID parameter that was used in the
    job step.
    
    tcb-number
    The NUMTCB parameter of the job that started the WLM-managed
    stored procedure address space. The NUMTCB value represents the
    maximum number of task control blocks (TCBs) that can run
    concurrently in an address space that is initiated by the WLM
    environment.
    
    System action
    Execution of the utility is stopped.
    
    System programmer response
    Change the PROCLIB member that was used to start the WLM-managed
    stored procedure address space to specify NUMTCB=1. Then,
    refresh the WLM environment and run the utility again.
    
    Severity
    8 (error)
    
    Information about this new message, DSNU022I, will be
    included in the Information Management Software for z/OS
    Solutions Information Center
    (http://publib.boulder.ibm.com/infocenter/imzic) at a later
    date.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM80291

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-10

  • Closed date

    2013-03-22

  • Last modified date

    2013-05-03

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

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

    UK92851 UK92852

Modules/Macros

  •    DSN@TILS DSN@TILU DSNUGBAC DSNUTILS DSNUTILU
    

Publications Referenced
GC18984914 GC19297907      

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK92851

       UP13/04/10 P F304

  • R910 PSY UK92852

       UP13/04/10 P F304

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM80291

Modified date:

2013-05-03

Translate my page

Machine Translation

Content navigation