II08094: INITIAL ESQA CONSIDERATIONS WHEN ADDING CONTROL UNITS TO A CONFIGURATION.

APAR status

• Closed as canceled.

Error description

• For all 3990 Model 3 or higher control units, storage is
  obtained from initial ESQA for DFSMS/DFP subsystem control blks.
  Thus, there exists the possibility that initial ESQA will be
  exhausted as more and more 3990 Model 3 or higher control units
  are added to the installation's configuration.  To prevent the
  possibility of an initial ESQA exhaustion condition, do the
  following.
     Whenever d/t3990 mod3 or higher control units are added to
  the installation's configuration, the constant found in IEAIPL04
  (NVESQA) may need to be incremented by one.  The current
  formula to use is:
  
     For every 30 3990 Model 3 or higher control units added to
     your configuration, increment the constant by one.  For
     example, if you add 20 3990 Model 3 control units to your
     configuration, you do not need to increment the constant;
     however, if at a later time you add 10 more 3990 Model 3
     control units to your configuration, you will need to
     increment the constant in IEAIPL04 (since the cumulative
     total of added control units is 30).
  
  Refer to MVS/ESA Initialization and Tuning Reference
  (GC28-1625 and SC28-1452) for instructions on changing the
  initial ESQA value in IEAIPL04. See  IEASYSxx SQA=(a,b)
  
  This zap is for HBB5520, HBB6601, HBB6603
  
    ++VER(Z038) FMID(HBB5520).
    ++ZAP(IEAIPL04).
      NAME IEAIPL04
      VER  0EF2  0010   NVESQA
      REP  0EF2  0011   increase ESQA by 1
  
    ++VER(Z038) FMID(HBB6605).
    ++ZAP(IEAIPL04).
      NAME IEAIPL04
      VER  0F02  0012   NVESQA
      REP  0F02  0013   increase ESQA by 1
    .
     The current offset within IEAIPL04 to access the half-word
  constant that indicates the number of 64K blocks that will
  be allocated for initial ESQA is given below for each MVS
  release.
     FMID(HBB4410) PRE(UY56582) -> OFFSET='0BD0'X
     FMID(HBB4420)              -> OFFSET='0BD0'X
     FMID(JBB4422)              -> OFFSET='0BD8'X
     FMID(HBB4430)              -> OFFSET='0EA6'X
     FMID(HBB5510)              -> OFFSET='0EF2'X
     FMID(HBB5520)              -> OFFSET='0EF2'X
     FMID(HBB5520) ptf UW42303  -> OFFSET='0F0A'X
     FMID(HBB6601)              -> OFFSET='0EF2'X
     FMID(HBB6601) ptf UW42304  -> OFFSET='0F02'X
     FMID(HBB6603)              -> OFFSET='0EF2'X
     FMID(HBB6603) ptf UW42305  -> OFFSET='0F02'X
     FMID(HBB6605)              -> OFFSET='0F02'X
     FMID(HBB6606)              -> OFFSET='0F32'X
  
  ADDITIONAL KEYWORDS:
  ABEND878 RC04 WAIT040 MSGIEA303W IEA303W IODF UCB RAMAC DB2INFO
  NOTE: ALSO SEE DFSMS APARS OW14713 and OW14938 FOR ADDITIONAL
        RELIEF! (Both apars are fixed by one ptf.)
  
  ADDITIONAL NOTE:
  Installation of RVA D/T9393 devices can cause exhaustion of
  ESQA in a similar manner.  There are PDDB items which address
  the specifics of this storage usage.  The zaps in this APAR
  may be used to increase the amount of initial ESQA necessitated
  by installation of RVA devices for OS/390 releases up to R2.5.
  In OS/390 R2.6 and beyond the initial ESQA can be increased
  using the INITSQA parameter of the LOADxx parmlib member.  See
  OW36793 for additional detail on this parameter.
  .
  For additional information on exhaustion of initial ESQA,
  please see apar OW27942.
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• close for Internet viewing
  

APAR Information

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

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

Fix information

Applicable component levels