IBM Support

OA56295: ABENDS0A03 ABENDA03 BPXBATCH BPXBATSL BPXMBATC ALREADYDUBBED LOCAL SPAWN 18/10/08 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer issuing this command from the shell receives abendA03
    after activation of PTF for APAR OA54829.
    
    
    />tso -t "bpxbatsl pgm /bin/echo"
    bpxbatsl pgm /bin/echo
    
    FOMF0142I Command abended: code=SA03 rsn=FFFFFFFF
    
    
    PE Information:
    Users Affected: Users at release HBB77A0/HBB77B0 with
    APAR OA54829 installed; affected PTFs are listed below.
    
    z/OS 2.3 UA95901
    z/OS 2.2 UA95906
    
    OA54829 fixed a problem in BPXBATCH - a dubbed job was calling
    BPXBATCH and on return from the call, BPXBATCH was incorrectly
    cleaning up UNIX resources. However, it introduced a new problem
    where a local spawned child (subtask) may not end before the
    parent, leading to the abendA03. IBM recommends leaving OA54829
    installed, as the problem it fixes is of greater impact.
    
    User Impact: Customer may receive a dump for the abendA03.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    *  All users of z/OS UNIX System Services for                  *
    *                 HBB77A0 and HBB77B0                          *
    *                 with PTFs for APAR OA54829 applied           *
    *                  HBB77A0 PTF UA95906                         *
    *                  HBB77B0 PTF UA95901                         *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    *  ABENDA03 in moudle BPXMBATC can occur                       *
    *                      if BPXBATCH is invoked from the shell   *
    *                      command 'tso -t'                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The shell command tso was used to invoke BPXBATSL:
      tso -t "bpxbatsl pgm /usr/pgm"
    
    When the shell command 'TSO -t' is issued, the shell creates a
    new address space to run the tso -t command.  The new address
    space is dubbed.  A task is then attached to run the BPXBATSL
    command - this task (Task A) is not dubbed at first.
    BPXBATSL processing continues:
     - USS syscalls are issued, causing Task A to become dubbed
     - Task A issues a local spawn(), resulting in a new task in the
       address space (Task B) which is also a new process.
     - Task A waits for Task B to execute the pgm
     - the pgm completes and Task A is notified.
     - Since Task A was in an address space that was dubbed on
       entry to BPXBATSL, no clean-up is done for Task A (BPX1MPC
       is not called).
     - Task A and Task B are both ending.
    - Task A can end first.  When it does end, an ABENDA03 is
      issued since Task B has not yet ended.
    

Problem conclusion

  • When BPXBATCH is entered, it will check to see of the calling
    task is dubbed or not.  When BPXBATCH completes processing, if
    the calling task (Task A) was not dubbed on entry, then a
    BPX1MPC call will be issued to undub the task.
    .
    Since this task is the parent task of Task B, the BPX1MPC call
    will clean-up Task B before ending, avoiding the ABENDA03.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA56295

  • Reported component name

    OPENMVS SYS SRV

  • Reported component ID

    5695SCPX1

  • Reported release

    7B0

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-08

  • Closed date

    2019-03-01

  • Last modified date

    2019-04-02

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

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

    UA98703 UA98704

Modules/Macros

  • BPXMBATC
    

Fix information

  • Fixed component name

    OPENMVS SYS SRV

  • Fixed component ID

    5695SCPX1

Applicable component levels

  • R7A0 PSY UA98704

       UP19/03/13 P F903 {

  • R7B0 PSY UA98703

       UP19/03/13 P F903 {

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":"7B0","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":"7B0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2019