IBM Support

PI98554: SDSFAUX ABEND S0C4 WHEN SDSFAUX IS STARTED MANUALLY.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When SDSFAUX is started manually and the SDSF server is active,
    the SDSFAUX server will end without an obvious message because
    it takes a silent abend. In the joblog there will be a series of
    HSF009I messages indicating the abend such as:
    HSF0091I - ABCC 840C4000
    A better indication needs to be presented so the user
    understands why the SDSFAUX server did not start.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of SDSF V2R3.                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * SDSFAUX ABEND S0C4 WHEN SDSFAUX IS                           *
    * STARTED MANUALLY.                                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The SDSF server automatically starts SDSFAUX and should not be
    started
    manually using an MVS START command.
    
    
    
    When SDSFAUX is started manually using an MVS START command and
    the SDSF address space is active, an abend S0C4 in SDSFAUX will
    occur and HSF0091I - ABCC 840C4000 will be issued.
    
    
    When SDSFAUX is started manually and the SDSF server is not
    active, an abend U0301 reason code xxxx0C04 occurs but this
    abend code is not documented.
    

Problem conclusion

  • SDSFAUX has been changed to abend with code U0201 reason code
    xxxx040C when SDSFAUX is not started by the SDSF address space.
    
    
    In addition, when the SDSFAUX server is started and SDSF server
    
    is not active SDSFAUX will ABEND U0201 with reason code
    xxxx0C04.
    
    
    
    Help panel ISFJCDE is updated to describe both the xxxx040C
    and xxxx0C04 reason codes.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI98554

  • Reported component name

    SDSF

  • Reported component ID

    566548801

  • Reported release

    7B0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-05-30

  • Closed date

    2018-06-26

  • Last modified date

    2018-08-02

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

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

    UI56842

Modules/Macros

  • HSFSRVSA HSFSRV00 ISFJCDE
    

Publications Referenced
SA232274    

Fix information

  • Fixed component name

    SDSF

  • Fixed component ID

    566548801

Applicable component levels

  • R7B0 PSY UI56842

       UP18/07/11 P F807

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 August 2018