PH63396: ABEND SB37 ON PSDFTPRB PROCESSING TAPE ARCHIVE FILES

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer is creating an ARCHIVE allocated to TAPE.
  While the ARCHIVE process completes successfully, the report
  step of the process abends with ABEND SB37 on DDNAME PSDFTPRB.
  The abend is not being correctly reported.
  
  In other scenarios, involving TAPE EXTRACT or ARCHIVE files,
  Optim may abort processing without issuing meaningful messages.
  

Local fix

• Pre-allocate a temporary data set in FOPMAIN step in the
  generated Optim JCL.
  The simplest DD statement which my be specified to allocate/
  override the DDNAME PSDFTPRB file  may be:
  
  
  //PSDFTPRB DD UNIT=SYSDA,DSN=&&TEMP,SPACE=(TRK,n)
  where n can be estimated by computing the value of expected
  number of rows in the XF/AF file * 6bytes
  
  Data set should be a BASIC SEQUENTIAL, with any other optional
  allocation parameters, except DCB. We also do not recommend
  specifying LRECL/BLKSIZE/RECFM values as these will be
  determined internally by Optim.
  
  Processes, which may require 2 ARCHIVE/EXTRACT allocations when
  TAPEs are being used, may also need to allocate DDNAME PSDFT2RB,
  Same rules.
  
  The UNIT value of the temporary data set allocated internally by
  Optim is controlled by the site option:
  
  Temp DASD Unit, Primary    ===> VIO    Valid Primary Unit Name
  Temp DASD Unit, Secondary  ===> SYSDA  Valid Secondary Unit Name
  
  Normally, we would see SMS accepting VIO when allowed by the
  SPACE values but switching over to secondary unit of SYSDA when
  SPACE values exceed VIO allocation rules. This does not seem to
  be the case in customer's environment. Note that we compute the
  exact required SPACE values based on the data in the EXTRACT/
  ARCHIVE TAPE files to be processed.
  
  
  Customer may want to change their Site Option for
  "Temp DASD Unit, Primary    ===> SYSDA Valid Primary Unit Name"
  to avoid using VIO.
  Or pre-allocate the temporary files and forcing the UNIT to
  SYSDA.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Optim ARCHIVE users processing TAPE Extract  *
  *                 or Archive files.                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: See Error Description.                  *
  ****************************************************************
  Optim allocates a temporary data set of proper size to
  accommodate the RBA values of the rows stored on the TAPE.
  In some customer environments these allocations may
  result in SPACE values which cause the data set to be
  under-allocated and unable to extend to secondary extents.
  This may cause S*37 abends which in turn are not being
  properly handled by Optim code.
  

Problem conclusion

• Optim processing will be corrected. The following messages
  will now be produced in Optim SUMMARY and/or PROCESS reports:
  
  *** ERROR *** TEMP RBA (PSDFTPRB) File is Full, pre-allocate or
  increase allocation
  
  The following additional messages have been issued:
  ---------------------------------------------------------------
  TEMP RBA (PSDFTPRB) File is Full, pre-allocate or increase
  allocation
  Estimated size: nnn blocks of nnnnn bytes
  ---------------------------------------------------------------
  
  Note that Optim allocates the temporary data set at the expected
  size and can not control any limitations placed upon the size of
  temporary data set imposed by the customer's environment.
  When such are present,a DD statement allocating the temporary
  data set, with the DDNAME and SPACE referenced in the message,
  will need to be added manually to the Optim's processing step in
  JCL.
  

Temporary fix

Comments

APAR Information

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

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

Modules/Macros

• FOPCFPMN FOPK09   FOPK10   FOPMARCN FOPMCBMN FOPMCMMN FOPMCOFN
  FOPMDBMN FOPMDMAI FOPMDPRC FOPMDXTR FOPMECMN FOPMMCMR FOPMMJBS
  FOPMMUTL FOPRS10  FOPRS3   FOPRS4   FOPRS7   FOPRS9   FOPTCV10
  FOPUMCBT FOPZFMMN
  

Fix information

• Fixed component name

  OPTIM MOVE FOR

• Fixed component ID

  5655V0700

Applicable component levels

• RB70 PSY UI98882

     UP24/10/29 P F410

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.