Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Temporary datasets: how much space are they using?

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
Perry

New User


Joined: 01 Apr 2010
Posts: 2
Location: UK

PostPosted: Tue Apr 06, 2010 3:31 pm    Post subject: Temporary datasets: how much space are they using?
Reply with quote

Greetings

My site makes heavy use of temporary dataseta in JCL/Procs etc.

We have frequent S*37 problems on them, the data they hold has frequent, difficult to predict spikes.

I would like to be able to monitor actual space useage of temporary ( eg &&foobar ) datasets, in order to get an insight into those which are going multi-extent, and allow for recoding on JCL prior to an actual S*37 occuring.

Are there any SMF records that would help me ( type 15 maybe?) or can anyone recommend an approach?
Back to top
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8617
Location: Back in jolly old England

PostPosted: Tue Apr 06, 2010 3:44 pm    Post subject:
Reply with quote

Type 15 may be of some use to you. I did do an analysis many years ago and might have the code somewhere.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8617
Location: Back in jolly old England

PostPosted: Tue Apr 06, 2010 3:50 pm    Post subject:
Reply with quote

This was written for z/OS 1.4 but hopefully the SMF records have not changed too much, if any, since the good old days.

I assume that you have SAS available icon_wink.gif
Code:
 IF RECTYPE = 15 THEN DO;                       
     INPUT   @003     SMFTIME    ??   SMFSTAMP.
             @011     SYSTEMID        $4.       
             @023     READER     ??   SMFSTAMP.
             @015     JOBNAME         $8.       
             @042     NUMBUCB         PIB1.     
             @053     DDNAME          $8.       
             @065     DATASET         $44.     
             @257     TRACKS3         PIB4.     
             @271     VOLSER          $6.       
             @282     EXTENTS         PIB1.     
             @285     EXCPCNT         PIB4.     
             @289     TRACKS1         PIB4.;   
                                               
     IF DATASET = '          ' THEN DELETE;     
                                               
     TRACKUSD = TRACKS1 - TRACKS3;             
                                               
     RUNDATE  = DATEPART(SMFTIME);             
     RUNTIME  = TIMEPART(SMFTIME);             
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Tue Apr 06, 2010 4:12 pm    Post subject:
Reply with quote

With my little knowledge, suggest, run the TSO command PARMLIB; if you are allowed, no operands but you must be allowed to execute it. Look at the value for 'VIO' . That's where the temporary output goes. The default is supposed to represent VIO, meaning that a memory-resident 'file' holds the data before being written to spool (or may be to a named output dataset.) On most tof the shops, they direct VIO to real DASD because a truly gigantic PDS can overload auxiliary storage and cause space abends. You might be using an esoteric for 'VIO' that has only a few volumes associated with it.
Back to top
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8617
Location: Back in jolly old England

PostPosted: Tue Apr 06, 2010 4:30 pm    Post subject:
Reply with quote

Anuj,

the VIO limit is usually set within the SMS subsystem, and is quite often quite a low threshold so that most && datasets do in fact get routed to DASD rather than VIO.

There could be a couple of things that may be causing the problem here, one being that the && datasets need to be adjusted to reflect the actual sizes being used, or that the storage group may just be over utilised at certain moments of the batch cycle.

Hopefully 'ye olde' SAS code from 1797 might still work icon_eek.gif
Back to top
View user's profile Send private message
Perry

New User


Joined: 01 Apr 2010
Posts: 2
Location: UK

PostPosted: Tue Apr 06, 2010 9:15 pm    Post subject:
Reply with quote

Thanks folks:

looks good, I'm sure I can use the 15s for what I need.

BTW, A colleague mentioned CA-MICS as a possible tool, has anyone done anything of this nature with it?
Back to top
View user's profile Send private message
PeterHolland

Global Moderator


Joined: 27 Oct 2009
Posts: 2445
Location: Netherlands, Amstelveen

PostPosted: Tue Apr 06, 2010 10:06 pm    Post subject:
Reply with quote

Record type 15 is for OUTPUT, UPDAT, INOUT, or OUTIN,
maybe you need also type 14 : INPUT or RDBACK.

MICS is terrible in case of reruns, thats why i kept far away from it.
We used MICS to see if OPC deadlines were kept or not, but nowadays
there are better tools (maybe homemade) to do that.
My experience is that MXG is a much nicer tool to work with, but then
you need SAS.
Back to top
View user's profile Send private message
Anuj Dhawan

Senior Member


Joined: 22 Apr 2006
Posts: 6258
Location: Mumbai, India

PostPosted: Wed Apr 07, 2010 8:28 pm    Post subject:
Reply with quote

Thank you expat - hopefully Perry gets his way to go...icon_smile.gif
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 445
Location: London

PostPosted: Thu Jun 10, 2010 10:16 pm    Post subject:
Reply with quote

Some places turn off SMF for TEMP's to reduce the size of the MANx files, in which case JCL library scans may be needed.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts File Tailoring -- Temporary dataset i... samzee71 CLIST & REXX 3 Fri Dec 01, 2017 3:12 am
No new posts The TS7720 is out of cache space. Rex Montemayor All Other Mainframe Topics 2 Mon Sep 25, 2017 7:18 am
No new posts REXX to get the all datasets name parasmalik20 CLIST & REXX 5 Tue Jul 18, 2017 9:10 pm
No new posts VSAM Space Allocation mrgnndhmk JCL & VSAM 7 Sat Apr 22, 2017 12:42 am
This topic is locked: you cannot edit posts or make replies. SDSF multiple spool datasets extracte... PJAlarcon CLIST & REXX 1 Fri Apr 21, 2017 10:50 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us