OA41102: INTERMITTENT SAPI GET REQUESTS USING SSS2CTKN FAIL WITH SSS2REAS OF SSS2RENM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• External Symptoms:
  The second of two successive SAPI GET requests using
  a valid client token (SSS2CTKN) as a filter for the same
  data set returns a SSS2REAS of x'F0' (SSS2RENM)
  indicating that there is no matching output when output exists.
  
  Impact to Customer:
  SAPI application is unable to retrieve requested output
  
  Additional Keywords: SSS2SCTK
  
  Analysis:
   On a SAPI PUTGET request, if the requested data set does
  not precede the previously returned data set in the job's
  OSE structure, IATOSSO begins looking for the requested data
  set with the next data set section.  Since two consecutive
  requests using the same token were made, the search on the
  second call began with the data set section following the
  one requested.  As a result, the data set was not found and
  SSS2RENM was returned in SSS2REAS.
  
  Verification steps:
  1) SAPI request acquires token
  2) SAPI GET request using token just acquired
     fails with :
     SSOBRETN =x'04' (No output found to process)
     SSS2REAS has a value of x'F0' (SSS2RENM),
      which indicates no matching output exists.
  3) The JCL will define multiple datasets with the
     same characteristics as the dataset with the token
  4) At least one additional dataset section in OSE variable
     section follows the dataset section found by the token
  
  The projected closing code is PER for HJS7770 and HJS7780.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of HJS7770 and HJS7780.            *
  ****************************************************************
  * PROBLEM DESCRIPTION: Successive SAPI PUTGET requests using   *
  *                      the same token fail with RC04 and       *
  *                      RSNF0 (no matching output).             *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  An application program obtained a client token for a SYSOUT
  data set and saved it.  Later, the application made two
  consecutive SAPI PUTGET requests using the saved token.  The
  first was successful.  Module IATOSSO was called to process
  the second request.  Using the checkpointed position of the
  previously returned data set, IATOSSO checks if the new request
  precedes the checkpointed location and resets its position
  before looking for the requested data set.  These checks
  neither account for identical data set locations nor include
  the data set section offset.  As a result, the new request
  did not result in repositioning before processing, and the
  requested data set was not found.
  

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 IATOSSO was changed to use the data set section offset
  and account for identical data set locations when making the
  checks related to repositioning.
  
  
  APAR OA41102 prereq's (and sup's) for FMID HJS7770:
  Pre's: * NONE *
  
  APAR OA41102 prereq's (and sup's) for FMID HJS7780:
  Pre's: * NONE *
  

Temporary fix

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

Comments

• ž**** PE13/12/10 FIX IN ERROR. SEE APAR OA44052  FOR DESCRIPTION
  

APAR Information

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

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

  UA68159 UA68160

Modules/Macros

• IATOSSO
  

Fix information

• Fixed component name

  JES3

• Fixed component ID

  5752SC1BA

Applicable component levels

• R770 PSY UA68159

     UP13/03/20 P F303

• R780 PSY UA68160

     UP13/03/20 P F303

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.