Hi Scott,
Pardon my Monday morning eyes that have not been stimulated with enough
caffeine, but...
After the trace record for the STORAGE OBTAIN for the Storage
address=2BDC1000, Length=204800, you mentioned that there is a STORAGE
RELEASE for 2BDC1000 in the trace but I don't see it! In the unseen
trace record, the "return address" should be usable to identify the
issuer of the STORAGE RELEASE.
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2013-05-24 16:44, Scott Ford wrote:
Gord:
Name X ASID Start Length SP Key Date Time Storage
Header
-------------------------------------------------------------------------------
VOYAGERT* 259 2BD5F000
204800 231 0 5/24/2013 8:40:39 *....ALTXA555480 *
VOYAGERT* 259 2BDC1000 204800 231 0
5/24/2013 8:38:29 *....ALTXR1641 *
VOYAGERT* 259 2BD2D000 204800 231 0 5/24/2013 8:42:43 *....ALTXU244026
*
GMT-05/24/2013 13:38:30.602148 LOC-05/24/2013
08:38:30.602148
USRDA F65 ASCB
00F7F100 JOBN VOYAGERT
Storage Obtain Cond=Yes
CheckZero=Yes AllZero
Loc=(31,31) Bndry=Dblwd
Owner=Home
Return address=3541A2EA
Amode=31 Asid=0103 Jobname=VOYAGERT
Subpool=231 Key=0
Asid=0103 Jobname=VOYAGERT TCB=00000000 Retcode=0
Storage address=2BDC1000Length=204800
X'32000'
GPR
Values
0-3 00032000
0000003C 35401544 356B7250
4-7 356B9F68
35400544 35F4F250 356B72B0
8-11 000127FC
00032000 356B9F20 B56B72B0
12-15 3541A2A0
356B9F68 0000030B 0800E770
NO
STORAGE RELEASE for 2BDC1000 in trace, as well as other 2 addresses
above
Here is a Getmain and a
storage release for 16 bytes, that does work, involving TOP Secret and
VOYAGERT
USRDA F65 ASCB
00FC3880 JOBN TSSZOS
Getmain SVC(120) Cond=Yes
CheckZero=No
Loc=(31,31) Bndry=Dblwd
Owner=Home
Return address=3545C414
Amode=31 Asid=0021 Jobname=TSSZOS
Subpool=231 Key=3
Asid=0021 Jobname=TSSZOS TCB=007CC580 Retcode=0
Storage address=344EC078
Length=16 X'10'
GPR
Values
0-3 0000000C
00000000 00000000 0000000C
4-7 006FC840
3389EDF0 007D2FC8 00D15300
8-11 00D5D000
007B8F00 007B7700 3545C3CE
12-15 3544CCC0
007B77A8 B54564FC 0000E700
GMT-05/24/2013 13:38:30.688425 LOC-05/24/2013
08:38:30.688425
USRDA F65 ASCB
00F7F100 JOBN VOYAGERT
Storage Release Cond=No
CheckZero=No
Return address=33F7B7A8
Amode=31 Asid=0103 Jobname=VOYAGERT
Subpool=231 Key=3
Asid=0021 Jobname=TSSZOS TCB=00000000 Retcode=0
Storage address=344EC078
Length=16 X'10'
GPR
Values
0-3 0000000C
344EC078 00000004 007FC810
4-7 00000040
344EC078 7F73FD30 00D5D000
8-11 7F740DD0
7F741200 7F73F000 33F7CFAA
12-15 33F7B3E0
7F740A20 00000311 0030E703
Scott J Ford
Software Engineer
http://www.identityforge.com/
________________________________
From: Gord Tomlin <[email protected]>
To: [email protected]
Sent: Friday, May 24, 2013 1:40 PM
Subject: Re: ECSA
Are you looking at system trace to see that STORAGE RELEASE? The ASID,
work unit address, and PSW for the STORAGE RELEASE should reveal who
issued it. Can you post the relevant lines from system trace (assuming
that is where you are looking)?
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2013-05-24 13:24, Scott Ford wrote:
Huh.....i see a good RC from a Storage Release....can you explain that one to me
Scott J Ford
Software Engineer
http://www.identityforge.com/
________________________________
From: Gord Tomlin <[email protected]>
To: [email protected]
Sent: Friday, May 24, 2013 12:48 PM
Subject: Re: ECSA
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
----------------------------------------------------------------------
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
----------------------------------------------------------------------
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
