Hmm ... Good point!
However, since you raise the issue, I googled for LSPACE
and came up with
http://www-1.ibm.com/support/docview.wss?uid=isg1II02887
which, despite being 20 years old, still seems to apply and
was updated as recently as April. It says:
"LSPACE then causes an ENQ to be issued against each device."
So, whether it reads F5 DSCBs or not, there does appear
to be an ENQ against the "device". What actual resource
name is used it doesn't say.
> Date: Fri, 15 Aug 2008 14:23:04 -0500
> From: [EMAIL PROTECTED]
> Subject: Re: Checking Volume Capacity
> To: [email protected]
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[EMAIL PROTECTED] On Behalf Of J R
> > Sent: Friday, August 15, 2008 2:02 PM
> > To: [email protected]
> > Subject: Re: Checking Volume Capacity
> >
> > If you were doing it from ISPF Option 6, you were probably
> > using a home-grown, 3rd party or CBT TSO CP or CLIST.
> > There were several around. The one that comes to mind is
> > "LSPACE" which simply issued the LSPACE macro/SVC. It
> > returned a formatted line of text containing how much free
> > space was on the volume, how many extents, the largest, etc.
> >
> > Be aware that this reads the F5 dscbs and probably ENQs
> > SYSVTOC, so you wouldn't want to do it indiscriminately.
> >
>
> Are you sure it reads the F5's? If you have an indexed VTOC (and you
> should!), then the free space information is kept in the VTOCIX and,
> IIRC, DADSM no longer maintains the F5 DSCBs on that volume.
>
> --
> John McKown
_________________________________________________________________
See what people are saying about Windows Live. Check out featured posts.
http://www.windowslive.com/connect?ocid=TXT_TAGLM_WL_connect2_082008
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
