OA47871: IAT6397 FCT DYNAL DISPATCHED CONTINUOUSLY, LOOP IN JES3 IATDYDR

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• External symptoms:
  JES3 monitor indicates an issue with the DYNAL FCT being
  dispatched repetitively
  
  Impact to customer:
    JES3 is looping in module IATDYDR until monitor messages
  IAT6410 is responded to
  
  Analysis:
    The DYNAL FCT is attempting to process a dynamic allocation
  request for a task.  The dataset in question is currently in use
  (busy return taken from MDSDSN DSN=DJSTDSNM call in routine
  DYALL030).  As a result we will attempt to search the DYNUN
  chain of staging areas for a matching unallocation request in
  routine DYDSTC20.  The logic incorrectly uses the allocation
  staging area to step through the chain of request instead of the
  unallocation chain, resulting in a loop.
  
  Verification steps:
  1)  MSGIAT6397 indicating DYNAL FCT is repetitively processing
  2)  ABENDDM134 (taken as a result of operator responding to
  IAT6410 message) shows R1 staging area on the ALLDYNAL queue
  (STAFUNC value x'95') instead of UNADYNAL (STAFUNC value of
  x'96') which is chained to the R4 staging area
  
  
  The projected closing code is PER for HJS7790 and HJS77A0.
  

Local fix

• none for loop; responding to monitor messages in a timely manner
  breaks loop and processing will continue
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of HJS7790 and HJS77A0.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Loop in module IATDYDR.                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  As part of processing a dynamic allocation request, module
  IATDYDR was called.  IATDYDR found that the requested resource
  was currently in use.  In this case, the requesting job was
  unable to wait for the resource.  As a result, subroutine
  DYALDSTC was called to look for a queued unallocation request.
  An error in this subroutine caused it to use the wrong staging
  area as the starting point for its scan and a loop resulted.
  

Problem conclusion

• Installation On (Global)
               Order (Any)
  Activation   Order (Any)
               Type/JES3 restart (Hot)
               Type/IPL (None)
               CLPA (No)
  (See Apar II07968 for definitions)
  
  Module IATDYDR's DYALDSTC subroutine was changed to use the
  correct staging area for starting its scan.
  
  APAR OA47871 prereq's (and sup's) for FMID HJS7790:
  Pre's: * NONE *
  
  APAR OA47871 prereq's (and sup's) for FMID HJS77A0:
  Pre's: * NONE *
  

Temporary fix

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

Comments

APAR Information

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

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

  UA78146 UA78147

Modules/Macros

• IATDYDR
  

Fix information

• Fixed component name

  JES3

• Fixed component ID

  5752SC1BA

Applicable component levels

• R7A0 PSY UA78146

     UP15/07/30 P F507

• R790 PSY UA78147

     UP15/07/30 P F507

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.