IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

How can amount of the Storage Usage be extracted ?


IBM Mainframe Forums -> CICS
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
esduman61

New User


Joined: 08 Mar 2016
Posts: 2
Location: türkiye

PostPosted: Wed Mar 09, 2016 1:19 pm
Reply with quote

There is a storage violation problem in our mainframe about one transaction which is consuming large amount of storage when it is running.

In that trx, many sub-programs are being called. We need to find amount of the storage usage in terms of the sub-programs being called in that trx (i.e. the root pgm of the trx is A , A is calling B , B is calling C etc. We need the storage usage of A , B and C respectively.

Could you please help us how can we extract these information ?

Thanks in advance

-Erkan
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7309
Location: Inside the Matrix

PostPosted: Wed Mar 09, 2016 2:34 pm
Reply with quote

Is it a CICS system? Have you asked your technical support what is available? Have you looked at the module sizes? Have you looked at the code?
Back to top
View user's profile Send private message
Bill O'Boyle

CICS Moderator


Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA

PostPosted: Wed Mar 09, 2016 5:13 pm
Reply with quote

Your CICS System Support group is where you should go. Do you have IBM's Fault Analyzer? When a SYSDUMP occurs, it will give you a total amount of storage used by a given task, regardless if the task is the culprit which caused the SV or not. Your programs should be allocating 31-Bit storage from the User/EDSA. Are your experiencing SOS conditions?

There are many ways to debug something like this so again, check with your Support group and/or your CICS System Programmer(s).

HTH....
Back to top
View user's profile Send private message
enrico-sorichetti

Superior Member


Joined: 14 Mar 2007
Posts: 10872
Location: italy

PostPosted: Wed Mar 09, 2016 5:25 pm
Reply with quote

Quote:
There is a storage violation problem in our mainframe about one transaction which is consuming large amount of storage when it is running.


there is no relation whatsoever between a storage violation and the amount of storage used
( as long as the storage is accessed properly )

remember ...

most often/almost always, in CICS the task abending because of the storage violation is not the one who caused it
Back to top
View user's profile Send private message
esduman61

New User


Joined: 08 Mar 2016
Posts: 2
Location: türkiye

PostPosted: Wed Mar 09, 2016 8:46 pm
Reply with quote

Thanks for all the replies.

Special thanks to "enrico-sorichetti" for his following comment : "most often/almost always, in CICS the task abending because of the storage violation is not the one who caused it". I strongly agree with this but unfortunately the owner of the abending task is always responsiple for replying or solving the problem.

We are using CICS and we have CICS support team. But we can't find any way to extract the storage usage in terms of the sub-programs of a task. We can see the total amount of usage by using "OMEGAVIEW " application. But as i indicate, we need storage usage of all of the sub-programs running in the task respectively.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 3048
Location: NYC,USA

PostPosted: Wed Mar 09, 2016 10:44 pm
Reply with quote

Check if this and also this helps.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Thu Mar 10, 2016 12:42 am
Reply with quote

Quote:
But as i indicate, we need storage usage of all of the sub-programs running in the task respectively.
No, you think you need to know this and you're probably not going to be able to get it. Depending on how the subprograms are invoked, it may not even be possible to get this data. A storage violation has absolutely NOTHING to do with subprogram storage usage and everything to do with storage overlay(s) -- that is, storage taking more bytes than it is supposed to. I've seen storage violations caused by programs calling subprograms with mis-matched parameter / argument lists, and table overflows, and copy book mis-matches, and communications buffer overflows.

As long as you are looking at the storage used by the subprograms, you are not looking at the trace and dump and figuring out where the REAL issue is. To find and fix a storage violation, you look at the trace and the dump to see what storage got overlaid and then -- if you are lucky -- you track it back to a particular program.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> CICS

 


Similar Topics
Topic Forum Replies
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts CICS vs LE: STORAGE option CICS 0
No new posts Insufficient Storage ABENDS & Debugging 7
No new posts STEM usage in REXX CLIST & REXX 14
No new posts Amount of days between two dates PL/I & Assembler 8
Search our Forums:

Back to Top