IBM Support

II08940: CSA SQA ECSA ESQA SUBPOOL SHORTAGE WHAT TO CONSIDER IF STORAGE SHORTAGE OCCURS. VSAMINFO VSMDATA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • ****
    *   UPDATED 10/29/97
     ****
    This APAR was created to assist in resolving CSA shortages
    and related SQA shortages.  This information is valid for
    DFSMS releases for VSAM and catalog.
    *****SEE II01989 FOR NON-DFSMS 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.
       HERE ARE A FEW KNOWN APARS:
    
        OW07911   IOS
        II00670
        OW05408 R1B0 ONLY
        OW14120
        OW15380
        OY66211 R110 ONLY
        OW12963
        OW13455
        OW12499
     Releases affected: R1C0 HDZ11C0 R1B0 HDZ11B0 R110 JDZ1110
                        5695DF106 5695DF105
    
       THERE MAY BE OTHER APARS WHICH I HAVE MISSED. A SEARCH
    CAN ALSO 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
    
             FOR ESA, USE IPCS VERBX VSMDATA.  FOR ESA/430
          AND ESA/5xx, USE IPCS VERBX VSMDATA 'OWNCOMM'. (DIAG=01)
    
       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
     (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)
    
    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).
    
       CONSTRUCTED, CPA CONTROL BLOCKS.  FOR EVERY VSAM DATA SET
       OPENED, A CPA CAN BE BUILT.
    *************************************************************
    *The size of VSRB control block starting at DFSMS R110 increased
    *to X'160' bytes or larger. It includes IOSB,IOD,CDTPL,DSNAME.
    *NOTE: The most common reason for CSA shortages due to many
    *VSRB's below the line is due to old programs that do not
    *specify RMODE31=CB or RMODE31=ALL.
    *************************************************************
          (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)
    SQA increase impacts IBM products that still use below
    16MB storage such as CICS, IMS, and other products that
    were designed pre-ESA.  There are also OEM products
    do not request that control blocks or buffers of vsam
    datasets are built above the 16mb line.
    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.
    
    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

  • VSAMINFO DB2INFO  Internet viewing
    

APAR Information

  • APAR number

    II08940

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1995-09-25

  • Closed date

    1999-11-19

  • Last modified date

    2001-01-19

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

    II01989

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
19 January 2001