Date:         Thu, 6 Jun 1996 12:29:27 GMT
Reply-To:     Bosco Ho <bosco.ho@FMR.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Bosco Ho <bosco.ho@FMR.COM>
Organization: Fidelity Investments
Subject:      Re: MVS Space Question

TWB2%Rates%FAR@GO50.COMP.PGE.COM wrote:
>If a job fails with a B37-04 on the work library, does anyone know a way to
>discover how much space the job actually received?  It is my impression that
>our OS (is it OS390 yet? MVS/ESA V4.3.0 - DFSMS V1.2 ) will allocate up to
>five separate pieces of disk to meet the "primary" allocation, and count this
>as the primary and four of the secondaries, and that if this is still less
>than the primary request, tough.  I am considering running PROC DATASETS
>LIBRARY=WORK; throughout the job, but that will not tell me how much space I
>had when the job went down.  Right now, I do not even get a code which tells
>me whether I went through all 16 extents (so I need to increase my secondary
>size) or I filled all available space on the disk (so I need to increase my
>primary size to force a different disk).
>
>Any suggestions?
>
>Tim Berryhill - Contract Programmer and General Wizard
>TWB2@PGE.COM
>Frequently at Pacific Gas & Electric Co., San Francisco
>The correlation coefficient between their views and
>my postings is slightly less than 0
 
since the WORK library stores all your temporary SAS datasets, it
depends on how many of the DATA steps the session has. The
problem is that regular WORK library is confined to a single
PACK, so UNIT=(SYSALLDA,3) in the JCL override will not work.
There is utility out there that will allow U to alloc multiple
PACKS and fool SAS into thinking it is a single entity, but
without going into this elaborate extreme (now back to the
original problem :-),) U can manage your work area by execute the
PROC DATASETS and delete the unwanted SAS datasets. A lot of time
one may create DATA A and B for merging purposes, but once the
merge (into DATA C) is done, there is no reason for A and B to
hang around
 
if U r really into statistics tracking, which is your question
but will not resolve B37, U can try FILESTAT or FULLSTATS under
the Session options
 
BTW, recently i ve experimented with COMPRESS=YES, but it may b
less desireable than one would think
 
hope this help
 
regards
 
bh
--
+===================================================+
| Std disclaimers apply: Any comments or stmts made |
| are not necessarily those of Fidelity Investments,|
| its subsidiaries, or affiliates. Plz address all  |
| personal emails to wboscoho@usa.pipeline.com  Thx |
+=================== """"""""""""""""""""""""" -----+