PM84654: THIS APAR ENABLES HPPR TO SUPPORT THE PIPEBLKSZ, PIPEDEPTH, AND PIPEWAIT KEYWORDS IN THE FABYIN CONTROL STATEMENT.

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• This APAR enables HPPR to support the PIPEBLKSZ, PIPEDEPTH, and
  PIPEWAIT keywords in the FABYIN control statement.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All IMS High Performance Prefix Resolution   *
  *                 for z/OS Version 3 Release 1 users           *
  *                 (FMID=H1IP310).                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: This APAR enables HPPR to support       *
  *                      new PIPE control statements.            *
  ****************************************************************
  * RECOMMENDATION: Apply the maintenance for this APAR.         *
  ****************************************************************
  IMS High Performance Prefix Resolution for z/OS has been
  modified so that it can support new PIPE keywords
  (PIPEBLKSZ,PIPEDEPTH,PIPEWAIT) in FABYIN control statements.
  

Problem conclusion

Temporary fix

Comments

• ========================
  = DOCUMENTATION CHANGE =
  ========================
  IMS High Performance Prefix Resolution for z/OS Version 3
  Release 1 User's Guide SC18-9230-03 ( SC18923003 ) should be
  changed as follows.
  ================================================================
  > 3.0 Running IMS High Performance Prefix Resolution
  >> 3.1 Stand-Alone Prefix Resolution
  >>> 3.1.3 Control statements for Stand-Alone Prefix Resolution
  Description of control statements
  PIPEBLKSZ
    PIPEBLKSZ specifies how many records can be moved to and from
  a HPPRPIPE at one time. It is recommended that you do not
  specify this control statement before you finish tuning other
  parameters. HPPRPIPE depends on a variety of factors, and this
  control statement can degrade performance.
    The block size specified in PIPEBLKSZ must include the data
  length (up to 32,756 bytes) plus 4 bytes for the internal block
  descriptor word (BDW).
    If you change the PIPEBLKSZ specification, you might need to
  change the value of the REGION parameter to avoid running out
  of virtual storage.
  _____________________________________________
  |                                            |
  |                 _32768___                  |
  | >>__PIPEBLKSZ=_|_________|_ _________ __>< |
  |                |         | |         |     |
  |                |_blksize_| |    _*_  |     |
  |                            |_,_|___|_|     |
  |                                |_1_|       |
  |                                |_2_|       |
  |                                |_3_|       |
  |                                |_4_|       |
  |____________________________________________|
    The first parameter blksize specifies the block size for the
  pipe identified by the second parameter, which specifies a pipe
  ID. For the valid pipe IDs, see "Notes on pipe ID".
    The default block size is 32768 for each pipe. If the blksize
  value is not specified, the default value is used for the
  specified pipe ID. If only the blksize value is specified, or
  the blksize value is specified with pipe ID *, it overrides the
  default block size. The maximum blksize value is 262144, and the
  minimum value is 1024. The minimum value must be larger than or
  equal to the maximum length of the records you are to transfer
  through the pipe, plus four.
  Notes on pipe ID:
    Pipe ID is a number that identifies a HPPRPIPE allocated
  between tasks running in an IMS HP Prefix Resolution job.
  The following pipes are allocated:
   -  The pipe between the INDX sort task and the LPLC sort task
     in the Prefix Resolution function. This pipe is allocated
     only when both INDX sort and LPLC sort are used for the
     Stand-Alone Prefix Resolution or Concurrent Prefix Update.
     It has pipe ID 1.
   -  The pipe to eliminate the intermediate Work File 2 (WF2)
     data set used in the Prefix Resolution function. This pipe
     will not be allocated when WF2 type data is not required.
     For example, the pipe will not be allocated for the
     Stand-Alone Prefix Update. It has pipe ID 2.
   -  The pipe to eliminate the intermediate Work File 3 (WF3)
     data set used between the Prefix Resolution function and the
     Prefix Update function. This pipe will not be allocated when
     WF3 type data is not required. For example, the pipe will
     not be allocated for the Stand-Alone Prefix Resolution or the
     Stand-Alone Prefix Update. It has pipe ID 3.
   -  The pipe used inside of the Prefix Update function. For
     example, the IMS DL/I buffer handler task to update OSAM data
     sets allocates this pipe. It has pipe ID 4.
    The default value of all pipes can be changed by using pipe
  ID *.
  PIPEDEPTH
    PIPEDEPTH specifies the number of blocks that can be in a
  HPPRPIPE at any given time before the pipe becomes "full." It is
  recommended that you do not specify this control statement
  before you finish tuning other parameters. HPPRPIPE depends on
  a variety of factors, and this control statement can degrade
  performance.
    The use of large values for PIPEDEPTH enables the HPPRPIPE
  service to accumulate more information in virtual storage. This
  can be helpful in smoothing out periodic wait periods during
  which the writing task is forced to wait because the pipe
  temporarily becomes full. The pipe becomes full because the
  reading task is temporarily delayed in reading data from the
  pipe.
    If you change the PIPEDEPTH specification, you might need to
  change the value of the REGION parameter to avoid running out
  of virtual storage.
  ___________________________________________
  |                                          |
  |                 _30____                  |
  | >>__PIPEDEPTH=_|_______|_ _________ __>< |
  |                |       | |         |     |
  |                |_depth_| |    _*_  |     |
  |                          |_,_|___|_|     |
  |                              |_1_|       |
  |                              |_2_|       |
  |                              |_3_|       |
  |                              |_4_|       |
  |__________________________________________|
    The first parameter depth specifies the number of blocks that
  can be held in the pipe, which is identified by the second
  parameter, at any given time before the pipe becomes "full." The
  second parameter specifies a pipe ID. For the valid pipe IDs,
  see "Notes on pipe ID".
  PIPEWAIT
    PIPEWAIT specifies the amount of time a writer or a reader of
  a HPPRPIPE can remain in a wait state before the HPPRPIPE
  service issues a message and abends.
  ________________________________________________________
  |                                                       |
  | >>__PIPEWAIT=_ ______ _ ________________________ __>< |
  |               |      | |                        |     |
  |               |_time_| |    _*_                 |     |
  |                        |_,_|___|_ ____________ _|     |
  |                            |_1_| |    _RDWR_  |       |
  |                            |_2_| |_,_|______|_|       |
  |                            |_3_|     |_OPEN_|         |
  |                            |_4_|                      |
  |_______________________________________________________|
    The first parameter time specifies the amount of time that a
  reader or a writer connecting to the pipe, which is identified
  by the second parameter, can remain in a wait state. The second
  parameter specifies a pipe ID. For the valid pipe IDs, see
  "Notes on pipe ID".
    The third parameter specifies the target to apply the wait
  state. The default value RDWR is used when the third parameter
  is not specified:
  RDWR
    Specifies to apply the wait state to the read and write wait
  state of the pipe. With RDWR, the first parameter time specifies
  how many of minutes, from 1 to 1440, a writer or a reader for
  the pipe can remain in a wait state.
    The default amount of time is 1440 (minutes) for pipe ID 1,
  and 15 (minutes) for pipe ID 2, 3, and 4. If the time value is
  specified with no pipe ID, or the time value is specified with
  pipe ID *, it overrides the default time value for all pipes.
  OPEN
    Specifies to apply the wait state to the open wait state of
  the pipe. With OPEN, the first parameter time specifies how
  many of seconds, from 1 to 1440, a writer or a reader for the
  pipe can remain in a wait state.
    The default time value is 30 (seconds) for each pipe. If the
  time value is specified with no pipe ID, or the time value is
  specified with pipe ID *, it overrides the default time value
  for all pipes.
  ================
  >> 3.2 Concurrent Prefix Update
  >>> 3.2.3 Control statements for Concurrent Prefix Update
  (Description about the new control statements, PIPEBLKSZ,
   PIPEDEPTH, and PIPEWAIT, are added as the same as
   "3.1.3 Control statements for Stand-Alone Prefix
   Resolution" above)
  ================
  >> 3.3 Stand-Alone Prefix Update
  >>> 3.3.3 Control statements for Stand-Alone Prefix Update
  (Description about the new control statements, PIPEBLKSZ,
   PIPEDEPTH, and PIPEWAIT, are added as the same as
   "3.1.3 Control statements for Stand-Alone Prefix
   Resolution" above)
  

APAR Information

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

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

  UK93992

Modules/Macros

• FABYINI0 FABYISI0 FABYPI00 FABYPMA0 FABYPMC0
  FABYPME0 FABYPMFT FABYPMF0 FABYPMGR FABYPMI0 FABYPMO0 FABYPMSG
  FABYPMT0 FABYPMX0 FABYTRM0
  

Fix information

• Fixed component name

  IMSPREFIXRESOLU

• Fixed component ID

  5655I1500

Applicable component levels

• R310 PSY UK93992

     UP13/05/08 P F305

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.