IBM Support

OA38975: NEW FUNCTION - TOLERATION SUPPORT FOR FSSDEF PARAMETER IN JES3 V2R1

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • The projected closing code for this APAR is UR1 for releases
    HJS7750, HJS7760, HJS7770, HJS7780.
    FIXCAT:  ZOS0204C/K
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of HJS7750, HJS7760, HJS7770 and   *
    *                 HJS7780.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Provide Support for TERM=YES in JES3    *
    *                      auto-restart situations.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Support was added to JES3 V2R1 for the TERM=YES parameter on
    the FSSDEF statement.  Without this APAR, the FSS defined with
    the TERM=YES parameter will be cancelled during the JES3 global
    termination but it will not be restarted automatically.
    

Problem conclusion

  • KEYWORDS: ZOS0204C/K ZOS0202C/K ZOS0203C/K
    

Temporary fix

  • *** * TEMPORARY FIX MAY BE OBTAINED FROM DLL OR INFO/ACCESS ****
    ******************* OA38975  DECK AVAILABLE ********************
    

Comments

  • Installation On (All Processors)
                 Order (Any)
    Activation   Order (Any)
                 Type/JES3 restart (Hot,Local)
                 Type/IPL (Rolling/DynLPA)
                 CLPA (Yes)
    (See Apar II07968 for definitions)
    
    
    Code is added to module IATSI34 to recognize a cancel command
    issued during JES3 global auto-restart termination.  IATSI34
    will flag the MEM Entry (IATYMEM) so that during connect
    processing, the condition can be communicated to the JES3 global
    during a subsequent connect.  The global will then flag the FSS
    entry (IATYFSS) in the same manner as when a *RETURN command is
    issued.  As soon as the FSS is terminated, the FSS is restarted.
    
    Documentation Updates:
    ======================
    
    The information in the following JES3 manuals should appear as
    indicated below.  Updates will only be made to the manuals in
    future JES3 releases.
    
    SA22-7550-xx JES3 Initialization and Tuning Reference
    
      FSSDEF statement
    
      TERM=
        Specifies whether the FSS terminates if the JES3 global
    |   address space terminates.
    
      Section 2.22.4 Examples
    
      Example 1: The following example defines a C/I FSS named
      CIFSS1 that runs on processor SY3 when processor SY1 is the
      JES3 global processor. The maximum number of batch CI DSPs
      that can operate in the C/I FSS address space at any one time
      is 4, while the maximum number of demand select CI DSPs is 5.
      The C/I FSS will not be started automatically by JES3, nor
    | will it terminate if JES3 address space terminates.
    
      Example 2: The following example defines an output writer FSS
      named WTRFSS1 that runs on processor SY1. The procedure in the
      procedure library for starting the output writer FSS has a
      member name of WTR3800. The output writer FSS will terminate
    | if JES3 address space terminates.
    
      Example 3: The following example defines three AFP
      channel-attached printers that operate under the control of
      the same output writer FSS (FSSPRT2). The DYNAMIC=YES
      specification on the PRTAFP3 allows JES3 to dynamically start
      that printer.
    
      The output writer FSS runs on processor SY1. Messages
      concerning this FSS will be displayed at consoles defined to
      receive routing code 42 which is the routing code equivalent
      of message destination class JES. The procedure in the
      procedure library for starting the output writer FSS has a
      member name of MULTIPRT. If you enter a *RETURN command,
    | invoke DSI or JES3 global is automatically restarted, the
      output writer FSS terminates with JES3.
    
    GA22-7547-xx JES3 Diagnosis
    
      Chapter 7.9 Recovering from Output Writer Functional Subsystem
      Failures:
    
      If you perform a hot start, output writer FSSs continue
      running in their own address spaces unless you specified the
      TERM=YES keyword on the FSSDEF initialization statement or
      unless you IPL the main on which the FSSs were operating. (You
      use the TERM= keyword to specify whether you want JES3 to
    | terminate an FSS when you terminate the global).  If the
      output writer FSS runs out of work before the JES3 global
      address space restarts, the output writer FSS remains idle
      until the restart.  After the hot start, JES3 restarts the
      writer DSPs, both hot writers and dynamic writers, that were
      associated with output writer FSSs active before the hot
      start.  The writer DSPs reestablish contact with the output
      writer FSSs and work continues as before the hot start.  For
      information about the effects of a dynamic system interchange
      on output writer FSSs see Dynamic System Interchange.
    
      Chapter 7.13 Recovering from C/I Functional Subsystem Address
      Space Failures
    
      If the JES3 global address space abnormally ends, all C/I FSS
      address spaces continue operating until they run out of work.
      Then they are idle until the JES3 global address space
      restarts. If the FSSDEF statement for the C/I FSS address
    | space specifies TERM=YES, a JES3 global address space
    | termination ends the C/I FSS address space.
    

APAR Information

  • APAR number

    OA38975

  • Reported component name

    JES3

  • Reported component ID

    5752SC1BA

  • Reported release

    760

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-03-01

  • Closed date

    2013-03-19

  • Last modified date

    2019-04-03

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

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

    UA68382 UA68383 UA68384 UA68385

Modules/Macros

  • IATIPMEE IATMSR1  IATSI34  IATYMEM  IATYRSR
    

Publications Referenced
SA227550XXGA227547XX   

Fix information

  • Fixed component name

    JES3

  • Fixed component ID

    5752SC1BA

Applicable component levels

  • R770 PSY UA68384

       UP13/04/03 P F304

  • R780 PSY UA68385

       UP13/04/03 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.

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

Document Information

Modified date:
03 April 2019