The storage is in subpool 231, which is a CSA/ECSA subpool. This subpool is owned by the system, and it is not freed by task or address space termination.

--

Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507

On 2013-05-24 12:15, Scott Ford wrote:
Guys and Gals:

I just received a problem from a customer and its odd. I will try to explain.

1. Customer is on z/OS 1.13 ..Put ( i dont know we have asked)
2. We have a STC that does this:
      a. We issue a Storage Obtain like below
      b. STC passed amount desired ...we call an assembler module which is 
snippeted below..
          <obviously we are a vendor - i can show it all - and i am sorry about 
that>

           LM    R9,R11,4(R1)       LOAD ADDRESS STG AMT, ADR & RC
          L     R9,0(R9)           STG AMT - S/B 4K MULTIPLE
          MODESET KEY=ZERO,MODE=SUP GO INTO SUPERVISOR MODE
          STORAGE OBTAIN,LENGTH=(9),SP=231,                             X
                LOC=31,COND=YES,CHECKZERO=YES
          ST    R1,0(R10)          RETURN ADDR, IF ANY
          ST    R15,0(R11)         RETURN CODE, OK IF ZERO
          MODESET KEY=NZERO,MODE=PROB BACK TO MORTALITY

     c. STC shutdowns via a Modify command...
         we call an asembler routine that issues the release

           LM    R9,R11,4(R1)       LOAD ADDRESS STG ADR, SIZE & RC
          L     R9,0(R9)           STG ADR
          L     R10,0(R10)         STG SIZE
          MODESET KEY=ZERO,MODE=SUP GO INTO SUPERVISOR MODE
          STORAGE RELEASE,LENGTH=(10),SP=231,ADDR=(9),KEY=0
          ST    R15,0(R11)         RETURN CODE, OK IF ZERO
          MODESET KEY=NZERO,MODE=PROB BACK TO MORTALITY
*-------------------------------------------------------------
          L     R13,4(R13)          CALLER SAVE AREA
          RETURN (14,12),RC=(15)

The problem is according to the customer we are not seeing a storage release 
....we ran a GFS trace and I am looking at it.
This code basically hasnt been changed since 2002 ...and i know is running in a 
lot of our customer environments..
The only difference is there is a separate job to perform the allocation of 
storage, then the STC ...then a separate job after the STC shutdowns to release 
the storage.  This is working fine. Can someone enlighten me ...? Does storage 
linger after a STC shutdowns ?
I thought VSM cleans up ..

Confused in NJ....

Regards,
Scott J Ford
Software Engineer
http://www.identityforge.com/

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to