Date:         Tue, 29 May 2001 09:56:28 -0400
Reply-To:     "Schechter, Robert S" <robert.schechter@ASTRAZENECA.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         "Schechter, Robert S" <robert.schechter@ASTRAZENECA.COM>
Subject:      Re: Optimal use of work space
Comments: To: Peter Crawford <peter.crawford@DB.COM>
Comments: cc: "agordon@scoteq.co.uk" <agordon@scoteq.co.uk>
Content-Type: text/plain; charset="iso-8859-1"

Just my 2 cents on this thread.

Know your data.

Is the data used in this analysis typical? For instance, does it contain
year-to-date records, growing over the year? Better, IMHO, to use "way too
much" of temporary space than have it abend, and need to be re-run on a
mission critical program. Usually disk space is cheaper than CPU.

I hate to have my assumptions second quessed by someone reviewing my
programs in a vacuum, not knowing why I did what I did.

The big thing is to know the data, and not make snap judgments on a single
review.

-----Original Message-----
From: Peter Crawford [mailto:peter.crawford@DB.COM]
Sent: Tuesday, May 29, 2001 10:17 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Optimal use of work space


add a proc contents data=work._all_ nods; run; at the end of the
SAS job. Examining the results you should find the info you need

from this sample of proc contents output....
Total Library Blocks:    50040
Total Used Blocks:       706
Total Free Blocks:       49334
Highest Used Block:      706

you can see that only 706 blocks of the 50040 allocated have been used.
This shows that the work allocation is  "way too much"
The Highest Used Block is the inportant statistic to examine.
The usage of the work library may be very small at the end of an
efficient process, particularly if work data sets are deleted when no
longer required. But I think the HighestUsed info indicates the max
usage of the allocation.

good luck



Datum:         29/05/2001 13:57
An:            SAS-L@listserv.uga.edu




Antwort an:    agordon@scoteq.co.uk

Betreff:       Optimal use of work space
Nachrichtentext:


I have been asked to review a suite of SAS batch jobs that run daily on our
OS390 TSO/MVS environment.  Some of these are large jobs, both in terms of
time
and data input/output.

So, say, if the JCL for job1 reserves 49000 tracks for workspace how can I
determine in an easy and straight-forward fashion (if this is possible) if
that is way too much, just right, or n% larger than is needed ?

Many thanks.





--

Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.