II06752: VTAM STORAGE DIAGNOSIS - AN INTRODUCTION / OVERVIEW

APAR status

• Closed as canceled.

Error description

• ***************************************************************
  * PROLOG:                                                     *
  ***************************************************************
  
  This is one of the APARs in a series of INFO APARs created to
  assist you in the initial diagnosis of VTAM storage problems.
  There are currently six INFO APARs in this series and others
  may be added if needed.  The current APARs are as follows:
  
  II06752  VTAM Storage Diagnosis - An Introduction/Overview
  II04548  VTAM Storage Diagnosis - Documentation Requirements
  II07563  VTAM Storage Diagnosis - Private Storage Problems
  II07564  VTAM Storage Diagnosis - Common Storage (CSA) Problems
  II09086  VTAM Storage Diagnosis - ABEND0C4 in ISTORCFB
  II09095  VTAM Storage Diagnosis - MSGIST565I During Activation
  
  
  ***************************************************************
  * INTRODUCTION:                                               *
  ***************************************************************
  
  Storage is a resource that a lot of users monitor very closely.
  This can be accomplished by the use of storage monitors, such
  as OMEGAMON or by VTAM DISPLAY commands that are either issued
  manually or by NETVIEW CLISTs that are triggered at specific
  timed intervals.
  
  The commonly used VTAM commands are D NET,BFRUSE which gives
  VTAM buffer pool values and D NET,STORUSE which gives SPANC
  pool values.  In addition, both commands provide CURR and MAX
  storage usage values.
  
  If you already know which type of storage shortage you have
  (CSA or Private), you may want to go directly to the INFO APAR
  listed above for that storage type.  First, however, you
  should review INFO APAR II04548 to insure you have met the
  minimum documentation requirement to diagnose your type of
  storage problem.  Once you have the required dump loaded into
  IPCS, you are ready to begin.
  
  On the other hand, there may be no storage monitors or CLISTs
  in place.  All of a sudden you find a dump was taken and not
  much of a problem description is given to you.  It is now your
  task as a VTAM System Programmer or VTAM LVL2 Programmer to
  come up with a resolution and you have no idea of where to
  begin your diagnosis.
  
  If you are not sure, or have no idea what area of storage
  is experiencing the shortage, the following text should help
  you determine this.
  
  
  
  ***************************************************************
  * IS THE PROBLEM IN PRIVATE OR CSA STORAGE?                   *
  ***************************************************************
  
  VTAM will rarely ABEND in an out of storage situation because
  we issue conditional GETMAINs.  When our request for storage
  is rejected with a non-zero return code from GETMAIN, we will
  issue one or more diagnostic messages to reflect the error.
  If there is one thing you can count on in life, it is the fact
  thatVTAM will become very vocal on the console when there is
  a shortage of storage.
  
  Check the MVS or NETVIEW console log for any of the following
  messages and you will be able to determine if the shortage is
  occurring in the Private or CSA storage area.
  
  
  
  ***************************************************************
  * MESSAGES INDICATING A CSA PROBLEM:                          *
  ***************************************************************
  
  MSGIST154I indicates expansion failed for one of the fixed
  length buffer pools in ECSA SP231.  The message also has an
  error code which should be looked up in the VTAM Messages
  and Codes manual for a further description of the problem.
  
  MSGIST561I indicates that you have hit SLOWPT in one of the
  fixed length buffer pools in ECSA SP231.  If this message
  only occurs occasionally, it may just mean some tuning should
  be done in this area.  If the console is flooded with this
  message, the buffer pool named in the message could be the
  cause, or just a victim of the CSA problem.
  
  MSGIST562I indicates you have reached the limit you have set
  for CSA or CSA24.  If you issued the MODIFY CSALIMIT command
  to increase the limit and this message begins repeating again
  in a short period of time, further investigation into the
  contents of CSA will be required.
  
  MSGIST564I indicates a GETMAIN failed for the CSA subpool
  specified in the message.  The CSA problem could lie in this
  subpool, but it may just be a victim and the problem lies in
  one of the other CSA subpools.
  
  MSGIST930I indicates that 80% or more of the XPANLIM value set
  for the IOBUF pool definition has been reached.  The message
  text will indicate which two session partners are involved in
  a 'HOT I/O' condition that is rapidly expanding the size of the
  IOBUF pool in CSA.
  
  
  
  ***************************************************************
  * MESSAGES INDICATING A PRIVATE STORAGE PROBLEM:              *
  ***************************************************************
  
  MSGIST563I indicates the user specified MAXPVT value has been
  reached in SP229 of the address space for the application
  program reported in the message.  VTAM acquires this storage to
  queue up inbound data for the application when there are RPLs
  outstanding to receive the data.  This usually indicates a
  problem with an application program not receiving its inbound
  data and is not a VTAM problem.
  
  MSGIST565I indicates a GETMAIN failed for the VTAM Private
  area subpool indicated in the message.  This subpool may be
  the problem or just a victim.  Further investigation into the
  contents of all the Private storage subpools is necessary to
  to identify the subpool actually using up all of the storage.
  
  MSGIST566I is the same as MSGIST563I except MAXPVT was not
  specified on the APPL definition.  This message usually does
  not indicate a VTAM problem.
  
  MSGIST999E indicates VTAM attempted to issue a message and was
  not able to obtain storage to build the message.  Most of the
  time that message is MSGIST565I.  The contents of the Private
  storage subpools need to be investigated.
  
  
  
  ***************************************************************
  * CONCLUSION:                                                 *
  ***************************************************************
  
  At this point you should have been able to determine whether
  the storage problem is in Private or CSA storage by the above
  messages.  You are now ready to continue your diagnosis using
  the INFO APAR for your particular storage type.  They will
  guide you through the dump using the IPCS commands and VTAM
  CLISTs to determine what is filling storage.  Once that has
  been accomplished, it will be much easier to formulate search
  arguments that will hopefully locate a resolution in IBMLINK
  or RETAIN.
  
  Remember, you are always welcome to queue in to the VTAM LVL2
  Support Center at any time for any additional diagnostic help
  you may require now or as you move on to the next step.
  
  
  
  ***************************************************************
  * GO TO II07564 (CSA) OR II07563 (PVT) FOR FURTHER DIAGNOSIS. *
  ***************************************************************
  
  
  ***************************************************************
  SEARCHABILITY KEYWORDS:
  VTAMINFO TPINFO INFOV2LIB PERFORMANCE PERFM DEGRADATION
  HIGH CPU EXCESSIVE PAGING ISTORMAF ISTORMVA ISTORFBA
  566528001 R204 R214
  566528901 R303
  568508501 R301 R401 R431 R404
  569511701 R101 R201 R301
  MSGIEA911E MSGIST154I MSGIST561I MSGIST562I MSGIST563I
  MSGIST564I MSGIST565I MSGIST566I MSGIST999E
  IEA911E IST154I IST565I IST562I IST563I IST564I IST565I
  IST566I IST9999E
  EXTENDED PRIVATE PVT EPVT CSA ECSA CSA24 COMMON STORAGE
  SUBPOOL SP LSQA ELSQA
  1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
  25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
  46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66
  67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87
  88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106
  107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122
  123 124 125 126 127 128 229 230 250 227 228 231 241
  SP1 SP2 SP3 SP4 SP5 SP6 SP7 SP8 SP9 SP10 SP11 SP12 SP13 SP14
  SP15 SP16 SP17 SP18 SP19 SP20 SP21 SP22 SP23 SP24 SP25 SP26
  SP27 SP28 SP29 SP30 SP31 SP32 SP33 SP34 SP35 SP36 SP37 SP38
  SP39 SP40 SP41 SP42 SP43 SP44 SP45 SP46 SP47 SP48 SP49 SP50
  SP51 SP52 SP53 SP54 SP55 SP56 SP57 SP58 SP59 SP60 SP61 SP62
  SP63 SP64 SP65 SP66 SP67 SP68 SP69 SP70 SP71 SP72 SP73 SP74
  SP75 SP76 SP77 SP78 SP79 SP80 SP81 SP82 SP83 SP84 SP85 SP86
  SP87 SP88 SP89 SP90 SP91 SP92 SP93 SP94 SP95 SP96 SP97 SP98
  SP99 SP100 SP101 SP102 SP103 SP104 SP105 SP106 SP107 SP108
  SP109 SP110 SP111 SP112 SP113 SP114 SP115 SP116 SP117 SP118
  SP119 SP120 SP121 SP122 SP123 SP124 SP125 SP126 SP127 SP128
  SP229 SP230 SP250 SP227 SP228 SP231 SP241
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• closing cancel
  

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