PK96224: CHANGING A FILE FROM LSR TO NSR, THE BUFFER PARAMETER IS NOT HONORED. THE NUMBER OF BUFFERS IS DETERMINED BY STRING NUMBER

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have a file that is switched from LSR to NSR in order to
  facilitate fast loading.  You have the file defined to use LSR
  POOL 5 and you also have DataBuf and IndexBuf defined, with a
  STRings defined as 10.
  You have an application that closes and disables the file,
  then changes the LSrpoolid from 5 to 0 (zero).  This makes the
  file NSR and the 200 plus data and index buffers are used to
  load the file.  You close and disable the file, resetting
  the LSR pool to 5 and reopen it.
  When you encounter a problem and have to reload the file, you
  go through the same process, but the load takes an extremely
  long time.
  When you check the file definition, you find that you have 11
  data buffers and 11 index buffers (STRINO+1).
  When you switched from NSR back to LSR, the data and index
  buffers were set to zero.  On the second load of the file as
  an NSR file, the buffers were determined by the number of
  strings defined.
  Additional Symptom(s) Search Keyword(s):
  KIXREVPAD
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Attempts to switch a file between NSR   *
  *                      and LSR results in the set values for   *
  *                      DATABUFFERS and INDEXBUFFERS being      *
  *                      lost.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A file is defined using CEDA. As regards to this problem there
  are three fields of interest. The first is the LSRPOOLID, this
  can have the value of 1-8 or 0. If it is a value of 1-8 then
  this says that the file is to use the LSR pool (ie share
  resources with other files). If it is 0 then this file is NSR,
  and will use the number of strings and index/data buffers that
  have been specified in the CEDA define. The second and third
  fields of interest are the defined index and data buffers, which
  as discussed above are used with NSR files.
  
  If the file is closed, disabled, then it can have the LSRPOOLID
  value changed. For this problem the file was first defined as
  NSR with data and index buffers (lsrpoolid=0), then the file was
  updated using CECI to be LSR (lsrpoolid =1-8). However, in doing
  so the defined values for index and data buffers are zeroed. If
  the file is reopened as an NSR file, CICS uses default values
  for these fields. These default values for index buffers and
  data buffers are set to the value of the STRINGS field and the
  value of the STRINGS field value plus one.
  

Problem conclusion

• The file control code has been amended such that when
  switching a file from NSR to LSR the defined values
  for DATABUFFERS and INDEXBUFFERS are kept as defined.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PK92138

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

  UK52017

Modules/Macros

• DFHFCMT  DFHFCST
  

Fix information

• Fixed component name

  CICS TS Z/OS V4

• Fixed component ID

  5655S9700

Applicable component levels

• R600 PSY UK52017

     UP09/11/24 P F911

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.