II01989: WHAT TO CONSIDER WHEN A CSA, SQA, OR A SUBPOOL STORAGE SHORTAGE OCCURS. VSAMINFO VSMDATA

APAR status

• Closed as canceled.

Error description

• *************************************************************
  *   APAR WAS CREATED ON 2/19/85 AND MAY BE MODIFIED IN      *
  *   FUTURE UPDATES.                                         *
  *************************************************************
   ****
   *   UPDATED 10/22/97   W.J. Williams   09/14/95 E.R. Brooks
   ****
     THE APAR WAS CREATED TO ASSIST IN RESOLVING CSA SHORTAGE
  SITUATIONS AND RELATED SQA SHORTAGES.  THIS INFORMATION IS
  VALID FOR ALL VSAM AND CATALOG RELEASES.               .
     WHEN SITUATIONS ARISE,  WHERE THE USER SUDDENLY
  FINDS HIMSELF WITH A CSA SHORTAGE CONDITION, ONE NEEDS TO
  EVALUATE THE CAUSE. AN ABEND80A, FOLLOWED BY MSGIEA705I WITH
  A RETURN CODE, CAN BE ONE RESULT THAT INDICATES THIS CONDITION.
     THE FOLLOWING STEPS DESCRIBE A WAY OF EVALUATING THE CSA
  STORAGE SHORTAGE:
  
  1) SEARCH ON CSA FRAGMENTATION OR CSA SP231 AND/OR SP241.
     ALSO SQA AND OR SP245.
  
   Releases affected: r330 hdp3330
                      r320 hdp3320 r240 hdp2240 r332 r321
                      566528451 566528452 566528418
  
  A search can yield several APARs closed RET, CAN or USE. Do not
  overlook or discount the information housed in these APARs.
  When developing a search, use keywords: CSA ECSA SQA ESQA.
  
  2) IF ONE FEELS THAT NONE OF THESE APPLY, THEN YOU WILL NEED TO
     MAP OUT CSA.  THERE ARE TWO UTILITY PROGRAMS IN DLL WHICH CAN
     BE OF GREAT ASSISTANCE:
     CSAMAP, IN DLL AS AZ93350.
  
  NOTE: THIS UTILITY CAN BE USED IN A DFP 370
        ENVIRONMENT ONLY. IN AN XA ENVIRONMENT ONE SHOULD
        USE THE PRINT DUMP (PRDMP) UTILITY WITH A CONTROL
        STATEMENT VSMDATA.
           FOR ESA, USE IPCS VERBX VSMDATA.  FOR ESA/430
        AND ESA/5xx, USE IPCS VERBX VSMDATA 'OWNCOMM'. (DIAG=01)
  
     ANOTHER UTILITY THAT CAN BE USED IN A NON XA
  ENVIRONMENT TO TRACE SVC120 GETMAIN / FREEMAIN (0A78), AND
  BRANCH ENTRIES BY SUBPOOL IS GM00V5 (IN DLL AS BZ93349), AND
  FOR XA USE GM00XAV7 (IN DLL AS AZ93349).  THESE INCLUDE
  A COMPLETE DESCRIPTION OF USAGE AND FUNCTIONS PROVIDED.
  
  THE GETMAIN FREEMAIN TRACE FOR MVS/ESA/430 IS NOW IN THE CODE,
  AND IS ONLY DESCRIBED IN APAR OY19890 AT THIS TIME.
     TO ENVOKE THE GFT, ONE SIMPLY NEEDS TO EDIT THE PARMLIB
  MEMBER  SYS1.PARMLIB(DIAG02), ADD THE WANTED OPTIONS, THEN,
  ENVOKE THE MEMBER VIA MVS CONSOLE COMMAND. HERE IS AN EXAMPLE:
  USER IS HAVING PRIVATE STORAGE SHORTAGES IN SUBPOOL 252 IN
  THE CATALOG (CAS) ADDRESS SPACE.  HE NEEDS TO RUN THE
  GETMAIN FREEMAIN TRACE TO FIND THE SOURCE OF THE SP252 FAILURE.
  THRU MVS COMMAND (D A,ALL) HE HAS DETERMINED THAT CAS = ASID(1A)
   (a) Go into ISPF/PDF edit mode.
   (b) Select the DIAG02 parmlib member, or, create a new member.
   (c) Add these options to the member:
          VSM TRACK CSA(ON) SQA(ON)
          VSM TRACE GETFREE (ON) SUBPOOL(252) ASID(1A)
   (d) Save the updated parmlib entry
   (e) Start GFT, we will be tracing USR F65 records
   (f) Envoke the updated parmlib member:  SET DIAG=02
   (g) Recreate error, then stop GTF and check the output
       Note: if you are to supply a corresponding SVCDUMP
             then take the dump before stopping GTF.
   (h) VSM infoapar OY19890 explains F65 record format.
       (BEWARE, data in the records is NOT on WORD boundaries)
  
  ALL GETMAIN/FREEMAIN TRACES REQUIRE GTF TO BE STARTED.
  (FOR ESA/430/5xx GFT CAN BE INVOKED THRU MVS CMD: SET DIAG=xx)
  See MVS/ESA Diagnosis: Tools and Service Aids  LY281845 chap11
  
  3) WHEN A USER INSTALLS THE CATALOG CVT TRAP, THIS INCLUDES THE
     INSTRUCTION '07FE' AT CVT + 10A,  AND DOES NOT RESET THE CVT
     TO THE ORIGINAL VALUE AFTER THE TRAP FOR CATALOG INFORMATION
     HAS BEEN GOTTEN, USER MAY FIND THAT CSA IS BEING FILLED UP.
  
  4) IN AN ICF CATALOG ENVIRONMENT THE NUMBER OF STRINGS USED
     AS PART OF THE CATALOG DEFINITION IS IMPORTANT. ONE SHOULD
     USE A VALUE OF 5-7. (STRNO)
  
  5) THE NUMBER OF CATALOGs OPEN AT THE TIME IS A FACTOR IN CSA
     USAGE. ALSO, THE CATALOG CISIZE, IF TOO LARGE, USES MORE CSA.
  
  6) IF CPA SEEMS TO BE A FACTOR THEN ONE NEEDS TO MAP THIS OUT.
     HE SHOULD START WITH THE CVT FIND THE AMCBS -->CAXWA CHAIN ->
     CATALOG ACB  --> AMBL--> AMB --> BUFCHDR --> BUFC--> CPA.
     EACH OPEN CATALOG WILL HAVE CPAs ASSOCIATED WITH IT.
        THE OTHER VSAM DATA AREAS NEED TO BE MAPPED OUT USING THE
     ASCBVGTT . THIS SHOULD POINT TO A VGTT AND THE VGTTPSB -->HEB
     WHICH ALSO DESCRIBE CPA STORAGE (CPA = Channel Program Area).
  
  7) IN AN HSM ENVIROMENT,  HSM MAY INDIRECTLY HAVE  VSAM
     CONSTRUCTED, CPA CONTROL BLOCKS.  FOR EVERY VSAM DATA SET
     OPENED, A CPA CAN BE BUILT.
  
  THE MEANING OF  VSRB  SEEMS TO CONFUSE MANY PEOPLE.
        (IDAVSRB = VSRB = VSAM SERVICE REQUEST BLOCK)
     A VSRB IS AN SRB AND THE START OF A GROUP OF CONTROL
  BLOCKS BUILT BY VSAM OPEN. (ALL BUILT IN SP245 SQA ESQA)
  ONCE YOU FIND THE VSRB EYECATCHER, OFFSET x'1C' POINTS TO
  AN IOSB. IOSB + x'20', IOSUSE, POINTS TO IOMB WHICH IS ALSO
  BUILT BY VSAM OPEN, BUT IN SP252.  TO VERIFY VSRBs ARE VALID,
  ONE NEEDS TO MAP OUT THE VSRBs, AND BASICALLY LOOK FOR THE
  FOLLOWING:
  
  1) THE VSRB + x'1C' (SRBPARM) -> IOSB; THE IOSB + x'20' (IOSUSE)
     -> IOMB; THE IOMB + x'10'(IOMAMB) -> AMB; THE AMB +x'30' BIT3
     (AMBOPEN) INDICATES THAT THE AMB IS OPEN.
  
  2) THE IOMB + x'C' -->IOMPLH, AND THE PLH ALSO CAN INDICATE
     IF IT IS ACTIVE (FF) OR NOT. PLH PLUS x'18' IS A POINTER TO
     THE ADDRESS OF AN ACB. THE ACB SHOWS IF IT IS OPEN, AND ALSO
     TELLS US IF LSR IS ACTIVE.  USING THE INFORMATION FOUND IN
     THESE CONTROL BLOCKS, THE USER CAN TELL IF THEY ARE ACTIVE.
     IF SHARED RESOURCES ARE A FACTOR, WE ALSO BUILD THE BUFFERS.
  
  3) THE IOSB CAN BE FOUND IN THE VSRB PLUS x'48'
     AN IOSB CAN BE IDENTIFIED WITH A 'C' AT OFFSET 00,
     AND POSSIBLY A  x'7F' OR 04 AT OFFSET 0D.
     IOSB + x'1C' POINTS BACK TO THE VSRB ADDRESS.
  
  4) WHEN USERS USE A LARGE STRING NUMBER (STRNO), WE BUILD AN
     RPL-PLH PAIR OF BLOCKS, AND THEIR ASSOCIATED CONTROL BLOCKS.
     MOST OF THESE USE SUBPOOL 245 (SQA ESQA).
     OTHER POINTERS ARE THE PLH + x'4C'---> IOMB
     IOMB + x'24' --> IOSB
  
     IN SHORT, AS LONG AS THERE IS A VALID CONNECTION TO AN AMB
  AND PLH, THE CONTROL BLOCKS ARE VALID. ALL THE CONTROL
  BLOCKS SHOULD BE RELEASED WHEN WE CLOSE THE DATASET, AND OR
  DO A DLVRP IF BLDVRP WAS USED.
  
     THERE ARE SEVERAL CONTROL BLOCKS BUILT AT OPEN,
  AND OR BLDVRP TIME. THEY ARE:
  
    IOMB    (SP252),    BUFC (SP250),   WAX (SP250)
    BUFFERS (SP250),    PLH  (SP250),   RPL (SP250),
    SRB     (SP245),    IOSB (SP245).
  
  OTHER CONTROL BLOCKS RELATED TO SQA STORAGE ARE:
    IQE, VSRT, PFL, VGTT, VDSAB, MMSB, MMSV = (SP245).
  
  AS THE SQA GROWS IT CAN OVERFLOW INTO THE CSA AND CAUSE
  COMMON STORAGE FRAGMENATION.
     SEE MVS/XA LOGIC LY263907 FOR A DISSERTATION ABOUT OPEN
  AND AN ADDITIONAL UNDERSTANDING OF CONTROL BLOCK USAGE.
  
  OTHER IMPORTANT FACTORS, PER THE NUMBER OF CONTROL BLOCKS
  BUILT, IS THE STRING NUMBER USED, DYNAMIC STRING ADDITION,
  NUMBER OF OPEN DATA SETS , AND OPEN CATALOGS.
  
  USING CICS 1.7 AND CODING THE  BASE = PARAMETER  IN
  THE DFHFCT MACRO, ALLOCATES A LARGE NUMBER OF BUFFERS
  FOR ALL THE FILES BELONGING TO THE BASE NAME USED.
  
  
  NOTE: WHETHER LSR OR NSR IS USED, ALL TASKS AND RESOURCES ARE
        TIED TO THE JOBSTEP TCB. CANCELING APPLICATION TASKS OR
        SUBTASKS DO NOT FREE UP THE RESOURCES. GLOBAL RESOURCES
        ARE FREED UP AT NORMAL CLOSE TIME, DELETVRP, OR JOBSTEP
        TERMINATION THRU IFG0TC0A, IDAOCEA2 AND MVS SERVICES.
  
  
  IF A USER DOES NOT HAVE DLL OR INFOSYS, AND NEEDS TO
  RUN THE GETMAIN FREEMAIN UTILITY BY SUBPOOL, THEN THE
  VSM COMPONENT (5752SC1CH) CAN BE CONTACTED FOR A COPY.
  
  NOTE: LOCAL IBM SUPPORT SHOULD BE USED AS AN AID FOR PSI.
            (read vsm infoapar II05506 first)
  
  SYMPTOMS: IDAHEB (HEB) using CSA or ECSA SP241 storage.
            ABEND878 ABEND80A (RC04 RSN4 RC08 RSN8)
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Sysroute II08940 Renee Brooks 09/25/95
  DB2INFO 5740XYR00
  

APAR Information

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

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

  II08940

Fix information

Applicable component levels