Re: Dataset space information

[Ted MacNEIL]

VTOCIX is the index -- required for SMS, along with the VVDS. The VTOC is 
unnamed.

-teD
  Original Message  
From: michelbutz
Sent: Tuesday, May 3, 2016 11:29
To: IBM-MAIN@LISTSERV.UA.EDU
Reply To: IBM Mainframe Discussion List
Subject: Dataset space information

Hi

I need to obtain dataset space information 

I have been looking at the DFSMS advanced services and there seems like a few 
away of going about this 

The OBTAIN and camlist seems like the easiest 
As all it needs is a dataset name and volser

The CVAF macros seems like the must current
But I would need to get (if I am using for instance)
CVAFDIR the DEB of the VTOC


BTW is the VTOC dataset name SYS1.VTOCIX. (Volser) ?

I guess that would mean allocating and opening it

Any suggestions ?

Sent from my iPhone
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[John Eells]

Without getting buried in the details of the F1DSCB (the format of 
which, as far as I know, matches the book's layout precisely and has for 
decades), *what* are you trying to find out *about* a data set?


- What size it is and the units used for allocation?
- How many extents it's in?
- Other stuff?

There very well might be far easier ways to get that information than by 
writing HLASM code to read the VTOC.  Things like, say, the DSINFO ISPF 
service...or LISTDSI in REXX...


michelbutz wrote:

I would assume a layout of DSCB format 1 didn't quite match up to the 
documentation
Specifically the volser followed the DSN followed by a '1' I assume for format 
1 DSCB for by the volser again

Sent from my iPhone


On May 10, 2016, at 2:52 PM, John Eells  wrote:

What information are you trying to get, exactly?

michelbutz wrote:

Hi

I need to obtain dataset space information





--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[John McKown]

On Tue, May 10, 2016 at 2:02 PM, michelbutz  wrote:

> I would assume a layout of DSCB format 1 didn't quite match up to the
> documentation
> Specifically the volser followed the DSN followed by a '1' I assume for
> format 1 DSCB for by the volser again
>

​Where did you get that doc? The DSN is a 44 byte hardware key. It should
be the first field, followed by a x'F1', followed by the CL6'volser'
This is mapped in SYS1.MODGEN(IECSDSL1)​



>
> Sent from my iPhone
>
> > On May 10, 2016, at 2:52 PM, John Eells  wrote:
> >
> > What information are you trying to get, exactly?
> >
> > michelbutz wrote:
> >> Hi
> >>
> >> I need to obtain dataset space information
> > 
> >
> > --
> > John Eells
> > IBM Poughkeepsie
> > ee...@us.ibm.com
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>



-- 
The unfacts, did we have them, are too imprecisely few to warrant our
certitude.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

I would assume a layout of DSCB format 1 didn't quite match up to the 
documentation 
Specifically the volser followed the DSN followed by a '1' I assume for format 
1 DSCB for by the volser again 

Sent from my iPhone

> On May 10, 2016, at 2:52 PM, John Eells  wrote:
> 
> What information are you trying to get, exactly?
> 
> michelbutz wrote:
>> Hi
>> 
>> I need to obtain dataset space information
> 
> 
> -- 
> John Eells
> IBM Poughkeepsie
> ee...@us.ibm.com
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[John Eells]

What information are you trying to get, exactly?

michelbutz wrote:

Hi

I need to obtain dataset space information



--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[Mike Shaw]

On 5/3/2016 7:42 PM, michelbutz wrote:

For CVAF I need the DEB of the VTOC

>

Michael:

If you use the technique I mentioned previously, the address of the DEB 
for the VTOC is available in the DCB after you OPEN the VTOC, but by 
then you are all set up to read the VTOC sequentially without using CVAF.


Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[Willy Jensen]

I would recommend the VTOC program from CBTTAPE.ORG file 112. It can provide a 
lot of information, including the CCHHR of the dataset. You can filter by 
datasetname and volser.

Willy

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[retired mainframer]

If all you want to know is how the dataset is allocated on the DASD, the TSO 
LISTDS command with the LABEL operand will display the DSCB including the 
extents.  The display is in a pseudo-dump format and the DFSMSdfp Advanced 
Services manual shows the internal structure.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of michelbutz
> Sent: Tuesday, May 03, 2016 1:23 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dataset space information
> 
> This all started by me trying to find out how space was taken by a dataset 
> DSCB info which
> led me to CVAFDIR
> It needed the DEB of the VTOC
> Maybe I should of used OBTAIN/CAMLIST

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

For CVAF I need the DEB of the VTOC 

Sent from my iPhone

> On May 3, 2016, at 7:24 PM, Mike Shaw  wrote:
> 
>> On 5/3/2016 11:29 AM, michelbutz wrote:
>> Hi
>> ..
> 
> Michael, since you said "...what is the VTOC..." it looks like you have a 
> long row to hoe..
> 
> To read the VTOC of a DASD volume you can issue a RDJFCB for a DDNAME that is 
> allocated to the volume, set the DSN in that JFCB to all x'04' characters, 
> then use OPEN TYPE=J to open the VTOC with that JFCB.
> 
> You can then read the entire with EXCP or BSAM to get the DSCBs and 
> interrogate each one in turn.
> 
> If you just want space info for one DS, maybe CVAF is better.
> 
> We have tried CVAF, BSAM, and EXCP; EXCP with a chained channel program is 
> fastest. If you don't care about speed, then use CVAF.
> 
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[Edward Finnell]

IIRC there's one already coded up on cbttape.org  file182 with PDS  command.
 
 
In a message dated 5/3/2016 6:25:11 P.M. Central Daylight Time,  
techsupp...@quickref.com writes:

If you  just want space info for one DS, maybe CVAF is better.

We have tried  CVAF, BSAM, and EXCP; EXCP with a chained channel program 
is fastest. If  you don't care about speed, then use  CVAF.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[Mike Shaw]

On 5/3/2016 11:29 AM, michelbutz wrote:

Hi
..



Michael, since you said "...what is the VTOC..." it looks like you have 
a long row to hoe..


To read the VTOC of a DASD volume you can issue a RDJFCB for a DDNAME 
that is allocated to the volume, set the DSN in that JFCB to all x'04' 
characters, then use OPEN TYPE=J to open the VTOC with that JFCB.


You can then read the entire with EXCP or BSAM to get the DSCBs and 
interrogate each one in turn.


If you just want space info for one DS, maybe CVAF is better.

We have tried CVAF, BSAM, and EXCP; EXCP with a chained channel program 
is fastest. If you don't care about speed, then use CVAF.


Mike Shaw
MVS/QuickRef Support Group
Chicago-Soft, Ltd.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michealbutz]

thanks that maybe a lot easier 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rob Scott
Sent: Tuesday, May 3, 2016 4:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset space information

If you need to find the space info for a single dataset - use CAMLST SEARCH to 
get the F1-DSCB and then CAMLST SEEK to process the F3-DSCBs.

For PDS/Es - you need to use FAMS (not a public interface).

For VSAM you can also use IGGCSI00

For bulk dataset info requests - you can use the DCOLLECT output and 
post-process it.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of michelbutz
Sent: Tuesday, May 3, 2016 9:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset space information

This all started by me trying to find out how space was taken by a dataset DSCB 
info which led me to CVAFDIR It needed the DEB of the VTOC Maybe I should of 
used OBTAIN/CAMLIST

Sent from my iPhone

> On May 3, 2016, at 4:09 PM, J R  wrote:
>
> The RDJFCB doesn't care too much about the DCB other than for the DDNAME and 
> where to put the copy of the JFCB.
>
> I'm not really sure what you're trying to do.  Unless you actually want to 
> access your dataset rather than its DSCB, why do you want to access the VTOC?
>
> Back in the '60s, this sort of thing was in the System Programmer's Guide.  
> It may be in Using Datasets or something similar now.
>
> However , you've lost me now.  I don't know why you need the DEB.  But you 
> should be able to get to it from the DCB.
>
> Sent from my iPhone
>
>> On May 3, 2016, at 15:54, michelbutz  wrote:
>>
>> Okay then the DCB on the open type=j is for the VTOC how about the 
>> DCB for the RDJFCB The original DCB in my program was for VB Dataset 
>> I hate bothering everybody is this documented anywhere i.e how to get 
>> the deb of the VTOC
>>
>>
>> Sent from my iPhone
>>
>>> On May 3, 2016, at 3:44 PM, J R  wrote:
>>>
>>> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
>>> it's been a long time). Then read until you see your damage in the key 
>>> area. Or, if you are more adventurous, you could use BDAM and search 
>>> directly for the key you are interested in.
>>>
>>> Sent from my iPhone
>>>
>>>> On May 3, 2016, at 15:11, michelbutz  wrote:
>>>>
>>>> Something strange is bombed on the open Message IEC141I the dataset 
>>>> it in the message is sys1.vtoc The DCB whose DSCB I am trying to 
>>>> access is a VB have that  DCB on the open type=j
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On May 3, 2016, at 2:35 PM, J R  wrote:
>>>>>
>>>>> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM.
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On May 3, 2016, at 14:30, michelbutz  wrote:
>>>>>>
>>>>>> I am still getting return code 4 in R15 CVSTAT is 8
>>>>>>
>>>>>> I first move 44X'04' to JFCBDSNM
>>>>>> I then do a READJFCB FILE
>>>>>> Everything is okay I get R15 = 0
>>>>>> I then do OPEN FILE,TYPE=J
>>>>>> R15 = 0
>>>>>> I then do ICM. R11,B'0111',DCBDEBA XC 
>>>>>> BUFLIST(BFLHLN+BFLELN),BUFLIST OI  BFLHFL,BFLHDSCB MVI. BFLHNOE,1 
>>>>>> LA. R6,DS1FMTID ST. R6,BFLEBUF OI.  BFLEFL,BFLECHR MVI.
>>>>>> BFLELTH,DSCBLTH
>>>>>>
>>>>>> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
>>>>>>
>>>>>> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>> On May 3, 2016, at 1:56 PM, J R  wrote:
>>>>>>>
>>>>>>> Nope.
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>>> On May 3, 2016, at 13:55, Staller, Allan  
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> ITYM 44x'40'
>>>>>>>>
>>>>>>>> 
>>>>>>>>
>>>>>>>> So, as I posted before:
>>>>>>>>
>>>>>>>> VTOC DSN is 44X'4'
>>>>>>>>
>>>>>

Re: Dataset space information

[J R]

I agree.  For a single dataset, OBTAIN/CAMLST would be much simpler. 

Sent from my iPhone

> On May 3, 2016, at 16:38, michealbutz  wrote:
> 
> thanks that maybe a lot easier 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Rob Scott
> Sent: Tuesday, May 3, 2016 4:36 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dataset space information
> 
> If you need to find the space info for a single dataset - use CAMLST SEARCH 
> to get the F1-DSCB and then CAMLST SEEK to process the F3-DSCBs.
> 
> For PDS/Es - you need to use FAMS (not a public interface).
> 
> For VSAM you can also use IGGCSI00
> 
> For bulk dataset info requests - you can use the DCOLLECT output and 
> post-process it.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of michelbutz
> Sent: Tuesday, May 3, 2016 9:23 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dataset space information
> 
> This all started by me trying to find out how space was taken by a dataset 
> DSCB info which led me to CVAFDIR It needed the DEB of the VTOC Maybe I 
> should of used OBTAIN/CAMLIST
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 4:09 PM, J R  wrote:
>> 
>> The RDJFCB doesn't care too much about the DCB other than for the DDNAME and 
>> where to put the copy of the JFCB.
>> 
>> I'm not really sure what you're trying to do.  Unless you actually want to 
>> access your dataset rather than its DSCB, why do you want to access the VTOC?
>> 
>> Back in the '60s, this sort of thing was in the System Programmer's Guide.  
>> It may be in Using Datasets or something similar now.
>> 
>> However , you've lost me now.  I don't know why you need the DEB.  But you 
>> should be able to get to it from the DCB.
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 15:54, michelbutz  wrote:
>>> 
>>> Okay then the DCB on the open type=j is for the VTOC how about the 
>>> DCB for the RDJFCB The original DCB in my program was for VB Dataset 
>>> I hate bothering everybody is this documented anywhere i.e how to get 
>>> the deb of the VTOC
>>> 
>>> 
>>> Sent from my iPhone
>>> 
>>>> On May 3, 2016, at 3:44 PM, J R  wrote:
>>>> 
>>>> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
>>>> it's been a long time). Then read until you see your damage in the key 
>>>> area. Or, if you are more adventurous, you could use BDAM and search 
>>>> directly for the key you are interested in.
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On May 3, 2016, at 15:11, michelbutz  wrote:
>>>>> 
>>>>> Something strange is bombed on the open Message IEC141I the dataset 
>>>>> it in the message is sys1.vtoc The DCB whose DSCB I am trying to 
>>>>> access is a VB have that  DCB on the open type=j
>>>>> 
>>>>> Sent from my iPhone
>>>>> 
>>>>>> On May 3, 2016, at 2:35 PM, J R  wrote:
>>>>>> 
>>>>>> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM.
>>>>>> 
>>>>>> Sent from my iPhone
>>>>>> 
>>>>>>> On May 3, 2016, at 14:30, michelbutz  wrote:
>>>>>>> 
>>>>>>> I am still getting return code 4 in R15 CVSTAT is 8
>>>>>>> 
>>>>>>> I first move 44X'04' to JFCBDSNM
>>>>>>> I then do a READJFCB FILE
>>>>>>> Everything is okay I get R15 = 0
>>>>>>> I then do OPEN FILE,TYPE=J
>>>>>>> R15 = 0
>>>>>>> I then do ICM. R11,B'0111',DCBDEBA XC 
>>>>>>> BUFLIST(BFLHLN+BFLELN),BUFLIST OI  BFLHFL,BFLHDSCB MVI. BFLHNOE,1 
>>>>>>> LA. R6,DS1FMTID ST. R6,BFLEBUF OI.  BFLEFL,BFLECHR MVI.
>>>>>>> BFLELTH,DSCBLTH
>>>>>>> 
>>>>>>> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
>>>>>>> 
>>>>>>> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
>>>>>>> 
>>>>>>> Sent from my iPhone
>>>>>>> 
>>>>>>>> On May 3, 2016, at 1:56 PM, J R  wrote:
>>>>>>>> 
>>>>>>>> Nope.
&g

Re: Dataset space information

[Rob Scott]

If you need to find the space info for a single dataset - use CAMLST SEARCH to 
get the F1-DSCB and then CAMLST SEEK to process the F3-DSCBs.

For PDS/Es - you need to use FAMS (not a public interface).

For VSAM you can also use IGGCSI00

For bulk dataset info requests - you can use the DCOLLECT output and 
post-process it.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of michelbutz
Sent: Tuesday, May 3, 2016 9:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dataset space information

This all started by me trying to find out how space was taken by a dataset DSCB 
info which led me to CVAFDIR It needed the DEB of the VTOC Maybe I should of 
used OBTAIN/CAMLIST

Sent from my iPhone

> On May 3, 2016, at 4:09 PM, J R  wrote:
>
> The RDJFCB doesn't care too much about the DCB other than for the DDNAME and 
> where to put the copy of the JFCB.
>
> I'm not really sure what you're trying to do.  Unless you actually want to 
> access your dataset rather than its DSCB, why do you want to access the VTOC?
>
> Back in the '60s, this sort of thing was in the System Programmer's Guide.  
> It may be in Using Datasets or something similar now.
>
> However , you've lost me now.  I don't know why you need the DEB.  But you 
> should be able to get to it from the DCB.
>
> Sent from my iPhone
>
>> On May 3, 2016, at 15:54, michelbutz  wrote:
>>
>> Okay then the DCB on the open type=j is for the VTOC how about the
>> DCB for the RDJFCB The original DCB in my program was for VB Dataset
>> I hate bothering everybody is this documented anywhere i.e how to get
>> the deb of the VTOC
>>
>>
>> Sent from my iPhone
>>
>>> On May 3, 2016, at 3:44 PM, J R  wrote:
>>>
>>> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
>>> it's been a long time). Then read until you see your damage in the key 
>>> area. Or, if you are more adventurous, you could use BDAM and search 
>>> directly for the key you are interested in.
>>>
>>> Sent from my iPhone
>>>
>>>> On May 3, 2016, at 15:11, michelbutz  wrote:
>>>>
>>>> Something strange is bombed on the open Message IEC141I the dataset
>>>> it in the message is sys1.vtoc The DCB whose DSCB I am trying to
>>>> access is a VB have that  DCB on the open type=j
>>>>
>>>> Sent from my iPhone
>>>>
>>>>> On May 3, 2016, at 2:35 PM, J R  wrote:
>>>>>
>>>>> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM.
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>>> On May 3, 2016, at 14:30, michelbutz  wrote:
>>>>>>
>>>>>> I am still getting return code 4 in R15 CVSTAT is 8
>>>>>>
>>>>>> I first move 44X'04' to JFCBDSNM
>>>>>> I then do a READJFCB FILE
>>>>>> Everything is okay I get R15 = 0
>>>>>> I then do OPEN FILE,TYPE=J
>>>>>> R15 = 0
>>>>>> I then do ICM. R11,B'0111',DCBDEBA XC
>>>>>> BUFLIST(BFLHLN+BFLELN),BUFLIST OI  BFLHFL,BFLHDSCB MVI. BFLHNOE,1
>>>>>> LA. R6,DS1FMTID ST. R6,BFLEBUF OI.  BFLEFL,BFLECHR MVI.
>>>>>> BFLELTH,DSCBLTH
>>>>>>
>>>>>> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
>>>>>>
>>>>>> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>>> On May 3, 2016, at 1:56 PM, J R  wrote:
>>>>>>>
>>>>>>> Nope.
>>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>>
>>>>>>>> On May 3, 2016, at 13:55, Staller, Allan  
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>> ITYM 44x'40'
>>>>>>>>
>>>>>>>> 
>>>>>>>>
>>>>>>>> So, as I posted before:
>>>>>>>>
>>>>>>>> VTOC DSN is 44X'4'
>>>>>>>>
>>>>>>>> This email   including attachments   may contain confidential 
>>>>>>>> information. If you are not the intended recipient, do not copy, 
>>>>>>>> distribute or act on

Re: Dataset space information

[michelbutz]

This all started by me trying to find out how space was taken by a dataset DSCB 
info which led me to CVAFDIR
It needed the DEB of the VTOC 
Maybe I should of used OBTAIN/CAMLIST

Sent from my iPhone

> On May 3, 2016, at 4:09 PM, J R  wrote:
> 
> The RDJFCB doesn't care too much about the DCB other than for the DDNAME and 
> where to put the copy of the JFCB.  
> 
> I'm not really sure what you're trying to do.  Unless you actually want to 
> access your dataset rather than its DSCB, why do you want to access the VTOC? 
>  
> 
> Back in the '60s, this sort of thing was in the System Programmer's Guide.  
> It may be in Using Datasets or something similar now. 
> 
> However , you've lost me now.  I don't know why you need the DEB.  But you 
> should be able to get to it from the DCB.  
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 15:54, michelbutz  wrote:
>> 
>> Okay then the DCB on the open type=j is for the VTOC how about the DCB for 
>> the RDJFCB 
>> The original DCB in my program was for VB
>> Dataset 
>> I hate bothering everybody is this documented anywhere i.e how to get the 
>> deb of the VTOC 
>> 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 3:44 PM, J R  wrote:
>>> 
>>> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
>>> it's been a long time). Then read until you see your damage in the key 
>>> area. Or, if you are more adventurous, you could use BDAM and search 
>>> directly for the key you are interested in. 
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 15:11, michelbutz  wrote:
 
 Something strange is bombed on the open 
 Message IEC141I the dataset it in the message is sys1.vtoc
 The DCB whose DSCB I am trying to access is a VB have that  DCB on the 
 open type=j 
 
 Sent from my iPhone
 
> On May 3, 2016, at 2:35 PM, J R  wrote:
> 
> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 14:30, michelbutz  wrote:
>> 
>> I am still getting return code 4 in R15 CVSTAT is 8
>> 
>> I first move 44X'04' to JFCBDSNM
>> I then do a READJFCB FILE
>> Everything is okay I get R15 = 0
>> I then do OPEN FILE,TYPE=J
>> R15 = 0
>> I then do ICM. R11,B'0111',DCBDEBA
>> XC BUFLIST(BFLHLN+BFLELN),BUFLIST
>> OI  BFLHFL,BFLHDSCB
>> MVI. BFLHNOE,1
>> LA. R6,DS1FMTID
>> ST. R6,BFLEBUF
>> OI.  BFLEFL,BFLECHR
>> MVI. BFLELTH,DSCBLTH
>> 
>> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
>> 
>> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 1:56 PM, J R  wrote:
>>> 
>>> Nope. 
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 13:55, Staller, Allan  
 wrote:
 
 ITYM 44x'40'
 
 
 
 So, as I posted before:  
 
 VTOC DSN is 44X'4'
 
 This email � including attachments � may contain confidential 
 information. If you are not the intended recipient, do not copy, 
 distribute or act on it. Instead, notify the sender immediately and 
 delete the message.
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / arc

Re: Dataset space information

[J R]

The RDJFCB doesn't care too much about the DCB other than for the DDNAME and 
where to put the copy of the JFCB.  

I'm not really sure what you're trying to do.  Unless you actually want to 
access your dataset rather than its DSCB, why do you want to access the VTOC?  

Back in the '60s, this sort of thing was in the System Programmer's Guide.  It 
may be in Using Datasets or something similar now. 

However , you've lost me now.  I don't know why you need the DEB.  But you 
should be able to get to it from the DCB.  

Sent from my iPhone

> On May 3, 2016, at 15:54, michelbutz  wrote:
> 
> Okay then the DCB on the open type=j is for the VTOC how about the DCB for 
> the RDJFCB 
> The original DCB in my program was for VB
> Dataset 
> I hate bothering everybody is this documented anywhere i.e how to get the deb 
> of the VTOC 
> 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 3:44 PM, J R  wrote:
>> 
>> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
>> it's been a long time). Then read until you see your damage in the key area. 
>> Or, if you are more adventurous, you could use BDAM and search directly for 
>> the key you are interested in. 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 15:11, michelbutz  wrote:
>>> 
>>> Something strange is bombed on the open 
>>> Message IEC141I the dataset it in the message is sys1.vtoc
>>> The DCB whose DSCB I am trying to access is a VB have that  DCB on the open 
>>> type=j 
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 2:35 PM, J R  wrote:
 
 Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 
 
 Sent from my iPhone
 
> On May 3, 2016, at 14:30, michelbutz  wrote:
> 
> I am still getting return code 4 in R15 CVSTAT is 8
> 
> I first move 44X'04' to JFCBDSNM
> I then do a READJFCB FILE
> Everything is okay I get R15 = 0
> I then do OPEN FILE,TYPE=J
> R15 = 0
> I then do ICM. R11,B'0111',DCBDEBA
> XC BUFLIST(BFLHLN+BFLELN),BUFLIST
> OI  BFLHFL,BFLHDSCB
> MVI. BFLHNOE,1
> LA. R6,DS1FMTID
> ST. R6,BFLEBUF
> OI.  BFLEFL,BFLECHR
> MVI. BFLELTH,DSCBLTH
> 
> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
> 
> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 1:56 PM, J R  wrote:
>> 
>> Nope. 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 13:55, Staller, Allan  
>>> wrote:
>>> 
>>> ITYM 44x'40'
>>> 
>>> 
>>> 
>>> So, as I posted before:  
>>> 
>>> VTOC DSN is 44X'4'
>>> 
>>> This email � including attachments � may contain confidential 
>>> information. If you are not the intended recipient, do not copy, 
>>> distribute or act on it. Instead, notify the sender immediately and 
>>> delete the message.
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

Okay then the DCB on the open type=j is for the VTOC how about the DCB for the 
RDJFCB 
The original DCB in my program was for VB
Dataset 
I hate bothering everybody is this documented anywhere i.e how to get the deb 
of the VTOC 


Sent from my iPhone

> On May 3, 2016, at 3:44 PM, J R  wrote:
> 
> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
> it's been a long time). Then read until you see your damage in the key area. 
> Or, if you are more adventurous, you could use BDAM and search directly for 
> the key you are interested in. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 15:11, michelbutz  wrote:
>> 
>> Something strange is bombed on the open 
>> Message IEC141I the dataset it in the message is sys1.vtoc
>> The DCB whose DSCB I am trying to access is a VB have that  DCB on the open 
>> type=j 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 2:35 PM, J R  wrote:
>>> 
>>> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 14:30, michelbutz  wrote:
 
 I am still getting return code 4 in R15 CVSTAT is 8
 
 I first move 44X'04' to JFCBDSNM
 I then do a READJFCB FILE
 Everything is okay I get R15 = 0
 I then do OPEN FILE,TYPE=J
 R15 = 0
 I then do ICM. R11,B'0111',DCBDEBA
 XC BUFLIST(BFLHLN+BFLELN),BUFLIST
 OI  BFLHFL,BFLHDSCB
 MVI. BFLHNOE,1
 LA. R6,DS1FMTID
 ST. R6,BFLEBUF
 OI.  BFLEFL,BFLECHR
 MVI. BFLELTH,DSCBLTH
 
 CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
 
 I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
 
 Sent from my iPhone
 
> On May 3, 2016, at 1:56 PM, J R  wrote:
> 
> Nope. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 13:55, Staller, Allan  
>> wrote:
>> 
>> ITYM 44x'40'
>> 
>> 
>> 
>> So, as I posted before:  
>> 
>> VTOC DSN is 44X'4'
>> 
>> This email � including attachments � may contain confidential 
>> information. If you are not the intended recipient, do not copy, 
>> distribute or act on it. Instead, notify the sender immediately and 
>> delete the message.
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[J R]

dataset, not damage!  (Danged predictive text.)

Sent from my iPhone

> On May 3, 2016, at 15:45, J R  wrote:
> 
> You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, 
> it's been a long time). Then read until you see your damage in the key area. 
> Or, if you are more adventurous, you could use BDAM and search directly for 
> the key you are interested in. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 15:11, michelbutz  wrote:
>> 
>> Something strange is bombed on the open 
>> Message IEC141I the dataset it in the message is sys1.vtoc
>> The DCB whose DSCB I am trying to access is a VB have that  DCB on the open 
>> type=j 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 2:35 PM, J R  wrote:
>>> 
>>> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 14:30, michelbutz  wrote:
 
 I am still getting return code 4 in R15 CVSTAT is 8
 
 I first move 44X'04' to JFCBDSNM
 I then do a READJFCB FILE
 Everything is okay I get R15 = 0
 I then do OPEN FILE,TYPE=J
 R15 = 0
 I then do ICM. R11,B'0111',DCBDEBA
 XC BUFLIST(BFLHLN+BFLELN),BUFLIST
 OI  BFLHFL,BFLHDSCB
 MVI. BFLHNOE,1
 LA. R6,DS1FMTID
 ST. R6,BFLEBUF
 OI.  BFLEFL,BFLECHR
 MVI. BFLELTH,DSCBLTH
 
 CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
 
 I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
 
 Sent from my iPhone
 
> On May 3, 2016, at 1:56 PM, J R  wrote:
> 
> Nope. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 13:55, Staller, Allan  
>> wrote:
>> 
>> ITYM 44x'40'
>> 
>> 
>> 
>> So, as I posted before:  
>> 
>> VTOC DSN is 44X'4'
>> 
>> This email � including attachments � may contain confidential 
>> information. If you are not the intended recipient, do not copy, 
>> distribute or act on it. Instead, notify the sender immediately and 
>> delete the message.
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[J R]

You should use BSAM, ie. READ, not GET, KEYLEN=44, BLKSIZE=140? (Not sure, it's 
been a long time). Then read until you see your damage in the key area. Or, if 
you are more adventurous, you could use BDAM and search directly for the key 
you are interested in. 

Sent from my iPhone

> On May 3, 2016, at 15:11, michelbutz  wrote:
> 
> Something strange is bombed on the open 
> Message IEC141I the dataset it in the message is sys1.vtoc
> The DCB whose DSCB I am trying to access is a VB have that  DCB on the open 
> type=j 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 2:35 PM, J R  wrote:
>> 
>> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 14:30, michelbutz  wrote:
>>> 
>>> I am still getting return code 4 in R15 CVSTAT is 8
>>> 
>>> I first move 44X'04' to JFCBDSNM
>>> I then do a READJFCB FILE
>>> Everything is okay I get R15 = 0
>>> I then do OPEN FILE,TYPE=J
>>> R15 = 0
>>> I then do ICM. R11,B'0111',DCBDEBA
>>> XC BUFLIST(BFLHLN+BFLELN),BUFLIST
>>> OI  BFLHFL,BFLHDSCB
>>> MVI. BFLHNOE,1
>>> LA. R6,DS1FMTID
>>> ST. R6,BFLEBUF
>>> OI.  BFLEFL,BFLECHR
>>> MVI. BFLELTH,DSCBLTH
>>> 
>>> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
>>> 
>>> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 1:56 PM, J R  wrote:
 
 Nope. 
 
 Sent from my iPhone
 
> On May 3, 2016, at 13:55, Staller, Allan  
> wrote:
> 
> ITYM 44x'40'
> 
> 
> 
> So, as I posted before:  
> 
> VTOC DSN is 44X'4'
> 
> This email � including attachments � may contain confidential 
> information. If you are not the intended recipient, do not copy, 
> distribute or act on it. Instead, notify the sender immediately and 
> delete the message.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

Something strange is bombed on the open 
Message IEC141I the dataset it in the message is sys1.vtoc
The DCB whose DSCB I am trying to access is a VB have that  DCB on the open 
type=j 

Sent from my iPhone

> On May 3, 2016, at 2:35 PM, J R  wrote:
> 
> Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 14:30, michelbutz  wrote:
>> 
>> I am still getting return code 4 in R15 CVSTAT is 8
>> 
>> I first move 44X'04' to JFCBDSNM
>> I then do a READJFCB FILE
>> Everything is okay I get R15 = 0
>> I then do OPEN FILE,TYPE=J
>> R15 = 0
>> I then do ICM. R11,B'0111',DCBDEBA
>> XC BUFLIST(BFLHLN+BFLELN),BUFLIST
>> OI  BFLHFL,BFLHDSCB
>> MVI. BFLHNOE,1
>> LA. R6,DS1FMTID
>> ST. R6,BFLEBUF
>> OI.  BFLEFL,BFLECHR
>> MVI. BFLELTH,DSCBLTH
>> 
>> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
>> 
>> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 1:56 PM, J R  wrote:
>>> 
>>> Nope. 
>>> 
>>> Sent from my iPhone
>>> 
 On May 3, 2016, at 13:55, Staller, Allan  
 wrote:
 
 ITYM 44x'40'
 
 
 
 So, as I posted before:  
 
 VTOC DSN is 44X'4'
 
 This email � including attachments � may contain confidential information. 
 If you are not the intended recipient, do not copy, distribute or act on 
 it. Instead, notify the sender immediately and delete the message.
 
 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[J R]

Do the RDJFCB first, *then* move the 44X'4' to JFCBDSNM. 

Sent from my iPhone

> On May 3, 2016, at 14:30, michelbutz  wrote:
> 
> I am still getting return code 4 in R15 CVSTAT is 8
> 
> I first move 44X'04' to JFCBDSNM
> I then do a READJFCB FILE
> Everything is okay I get R15 = 0
> I then do OPEN FILE,TYPE=J
> R15 = 0
> I then do ICM. R11,B'0111',DCBDEBA
> XC BUFLIST(BFLHLN+BFLELN),BUFLIST
> OI  BFLHFL,BFLHDSCB
> MVI. BFLHNOE,1
> LA. R6,DS1FMTID
> ST. R6,BFLEBUF
> OI.  BFLEFL,BFLECHR
> MVI. BFLELTH,DSCBLTH
> 
> CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)
> 
> I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 1:56 PM, J R  wrote:
>> 
>> Nope. 
>> 
>> Sent from my iPhone
>> 
>>> On May 3, 2016, at 13:55, Staller, Allan  
>>> wrote:
>>> 
>>> ITYM 44x'40'
>>> 
>>> 
>>> 
>>> So, as I posted before:  
>>> 
>>> VTOC DSN is 44X'4'
>>> 
>>> This email � including attachments � may contain confidential information. 
>>> If you are not the intended recipient, do not copy, distribute or act on 
>>> it. Instead, notify the sender immediately and delete the message.
>>> 
>>> --
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

I am still getting return code 4 in R15 CVSTAT is 8

I first move 44X'04' to JFCBDSNM
I then do a READJFCB FILE
Everything is okay I get R15 = 0
I then do OPEN FILE,TYPE=J
R15 = 0
I then do ICM. R11,B'0111',DCBDEBA
XC BUFLIST(BFLHLN+BFLELN),BUFLIST
OI  BFLHFL,BFLHDSCB
MVI. BFLHNOE,1
LA. R6,DS1FMTID
ST. R6,BFLEBUF
OI.  BFLEFL,BFLECHR
MVI. BFLELTH,DSCBLTH

CVAFDIR ACCESS=READ,DSN=DSN,BUFLIST=BUFLIST,DEB=(R11)

I get rerun code 4 in R15 and CVSTAT is 08 invalid DEB

Sent from my iPhone

> On May 3, 2016, at 1:56 PM, J R  wrote:
> 
> Nope. 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 13:55, Staller, Allan  wrote:
>> 
>> ITYM 44x'40'
>> 
>> 
>> 
>> So, as I posted before:  
>> 
>> VTOC DSN is 44X'4'
>> 
>> This email � including attachments � may contain confidential information. 
>> If you are not the intended recipient, do not copy, distribute or act on it. 
>> Instead, notify the sender immediately and delete the message.
>> 
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[J R]

Nope. 

Sent from my iPhone

> On May 3, 2016, at 13:55, Staller, Allan  wrote:
> 
> ITYM 44x'40'
> 
> 
> 
> So, as I posted before:  
> 
> VTOC DSN is 44X'4'
> 
> This email � including attachments � may contain confidential information. If 
> you are not the intended recipient, do not copy, distribute or act on it. 
> Instead, notify the sender immediately and delete the message.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[Staller, Allan]

ITYM 44x'40'



So, as I posted before:  

VTOC DSN is 44X'4'

This email � including attachments � may contain confidential information. If 
you are not the intended recipient, do not copy, distribute or act on it. 
Instead, notify the sender immediately and delete the message.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[J R]

So, as I posted before:  

VTOC DSN is 44X'4'

Sent from my iPhone

> On May 3, 2016, at 12:55, John McKown  wrote:
> 
>> On Tue, May 3, 2016 at 11:39 AM, michelbutz  wrote:
>> 
>> I have seen examples in the DFSMS advanced services using CVAFDIR one of
>> the parameters is the DEB of the VTOC is there a way to get that
>> Normally when you open a dataset its in the DCB
>> 
>> ​
> 
> The data extent block (DEB) can be obtained by opening a DCB for INPUT,
> using the RDJFCB and OPEN TYPE=J macros. (After issuing an OPEN TYPE=J
> macro, the DCB's DCBDEBA field contains the DEB's address.) The DCB's
> DDNAME must identify a DD statement allocated to the unit whose VTOC is to
> be accessed. Once your program issues the RDJFCB macro, it must initialize
> the JFCBDSNM field with the data set name of the format-4 DSCB: 44 bytes of
> X'04'. The RDJFCB macro is described under RDJFCB Macro Specification
> ;
> the OPEN macro is described under OPEN - Initialize Data Control Block for
> Processing the JFCB
> 
> . For an extended address volume the DCB macro must point to a DCBE where
> the EADSCB=OK keyword is specified. If you do not code this option, the
> OPEN function will issue ABEND 113-48 and message IEC142I.
> 
> ​
> 
> 
> 
> So you need to ​allocate the volume​, either with JCL or DYNALLOC, and
> specify both DISP=SHR and VOL=SER=aa. One convention is to use a data
> set name of FORMAT4.DSCB as the DSN, e.g.
> 
> //VTOC DD DISP=SHR,UNIT=SYSALLDA,VOL=SER=aa,DSN=FORMAT4.DSCB
> 
> You have a DCB with a DDNAME=VTOC. You do a RDJFCB on the DD. You then
> modify the data set name in the returned.
> 
> 
> 
> 
>   - Changing the data set name field or member field in the JFCB. See RDJFCB
>   Security
>   
> 
>and RDJFCB Use by Authorized Programs
>   
> .
>   You can open a VTOC by reading the JFCB, changing the data set name to 44
>   bytes of X'04' and then issuing the OPEN macro with TYPE=J. Use BSAM or
>   EXCP. If you use BSAM, also code RECFM=F, KEYLEN=44 and BLKSIZE=96 on the
>   DCB macro. For an extended address volume the DCB macro must point to a
>   DCBE where the EADSCB=OK keyword is specified. You'll find examples of
>   opening an EXCP DCB for a VTOC in Example of Using the CVAFFILT Macro
>   
> 
>andExample of using the CVAFSEQ macro to process a volume in physical
>   sequential order
>   
> 
>   .
> 
> 
> 
> 
> 
> -- 
> The unfacts, did we have them, are too imprecisely few to warrant our
> certitude.
> 
> Maranatha! <><
> John McKown
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[John McKown]

On Tue, May 3, 2016 at 11:39 AM, michelbutz  wrote:

> I have seen examples in the DFSMS advanced services using CVAFDIR one of
> the parameters is the DEB of the VTOC is there a way to get that
> Normally when you open a dataset its in the DCB
>
> ​

The data extent block (DEB) can be obtained by opening a DCB for INPUT,
using the RDJFCB and OPEN TYPE=J macros. (After issuing an OPEN TYPE=J
macro, the DCB's DCBDEBA field contains the DEB's address.) The DCB's
DDNAME must identify a DD statement allocated to the unit whose VTOC is to
be accessed. Once your program issues the RDJFCB macro, it must initialize
the JFCBDSNM field with the data set name of the format-4 DSCB: 44 bytes of
X'04'. The RDJFCB macro is described under RDJFCB Macro Specification
;
the OPEN macro is described under OPEN - Initialize Data Control Block for
Processing the JFCB

. For an extended address volume the DCB macro must point to a DCBE where
the EADSCB=OK keyword is specified. If you do not code this option, the
OPEN function will issue ABEND 113-48 and message IEC142I.

​



So you need to ​allocate the volume​, either with JCL or DYNALLOC, and
specify both DISP=SHR and VOL=SER=aa. One convention is to use a data
set name of FORMAT4.DSCB as the DSN, e.g.

//VTOC DD DISP=SHR,UNIT=SYSALLDA,VOL=SER=aa,DSN=FORMAT4.DSCB

You have a DCB with a DDNAME=VTOC. You do a RDJFCB on the DD. You then
modify the data set name in the returned.




   - Changing the data set name field or member field in the JFCB. See RDJFCB
   Security
   

and RDJFCB Use by Authorized Programs
   
.
   You can open a VTOC by reading the JFCB, changing the data set name to 44
   bytes of X'04' and then issuing the OPEN macro with TYPE=J. Use BSAM or
   EXCP. If you use BSAM, also code RECFM=F, KEYLEN=44 and BLKSIZE=96 on the
   DCB macro. For an extended address volume the DCB macro must point to a
   DCBE where the EADSCB=OK keyword is specified. You'll find examples of
   opening an EXCP DCB for a VTOC in Example of Using the CVAFFILT Macro
   

andExample of using the CVAFSEQ macro to process a volume in physical
   sequential order
   

   .





-- 
The unfacts, did we have them, are too imprecisely few to warrant our
certitude.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

I have seen examples in the DFSMS advanced services using CVAFDIR one of the 
parameters is the DEB of the VTOC is there a way to get that 
Normally when you open a dataset its in the DCB

Sent from my iPhone

> On May 3, 2016, at 12:15 PM, John McKown  wrote:
> 
>> On Tue, May 3, 2016 at 10:54 AM, michelbutz  wrote:
>> 
>> I am sorry dont understand what is the VTOC
>> Dataset name, there is another dataset on that volume sys1.vvds.v
>> concentrated to the volser
> 
> ​SYS1.VTOCIX.aa (aa is _normally_ the same as the volser, but need
> not necessarily be) is a _index_ into the actual VTOC itself. It does not
> contain the VTOC information.
> SYS1.VVDS.Vaa (aa, again, is _normally_ the same as the volser, but
> need not necessarily be) is a VSAM-like data set which contains SMS
> information for data sets in the VTOC.
> 
> The VTOC is the Volume Table Of Contents. IT IS NOT A DATA SET!!! It does
> _not_ show up in a VTOC listing of data sets on a volume. The VOL1 record
> on a volume contains a field which points to where the VTOC exists. The
> VTOC is "self described" in the type 4 VTOC record. The VTOC most closely
> resembles a keyed BDAM data set (remember, it's not a data set!) which has
> a 44 byte hardware key. The hardware key is the same as the DSN. For the
> VTOC, the hardware key is 44x'04', that is 44 repetitions of the hex value
> x'04'. When z/OS processes the VARY ONLINE command for a DASD device, it
> reads the VOL1 record. This validates the volume serial is unique and it
> then stores the address of the VTOC in the UCB for other users, such as
> DADSM allocation.​
> 
> ​I don't know what you want to do, but personally, I prefer using the
> output from the IDCAMS DCOLLECT command for data set information. Of
> course, it is not useful for a "one off" data set requirement. If you want
> a VTOC mapping of where data sets reside on a volume, for some reason, then
> using ADRDSSU with a PARM='TYPRUN=NORUN' and a DEFRAG command will get you
> a fairly nice listing.
> 
> You could also do a IEHLIST of the volume.
> 
> ​Oh, and I also use the REXX / TSO LISTDSI command for data set information
> retrieval.​
> 
> 
> -- 
> The unfacts, did we have them, are too imprecisely few to warrant our
> certitude.
> 
> Maranatha! <><
> John McKown
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[John McKown]

On Tue, May 3, 2016 at 10:54 AM, michelbutz  wrote:

> I am sorry dont understand what is the VTOC
> Dataset name, there is another dataset on that volume sys1.vvds.v
> concentrated to the volser
>

​SYS1.VTOCIX.aa (aa is _normally_ the same as the volser, but need
not necessarily be) is a _index_ into the actual VTOC itself. It does not
contain the VTOC information.
SYS1.VVDS.Vaa (aa, again, is _normally_ the same as the volser, but
need not necessarily be) is a VSAM-like data set which contains SMS
information for data sets in the VTOC.

The VTOC is the Volume Table Of Contents. IT IS NOT A DATA SET!!! It does
_not_ show up in a VTOC listing of data sets on a volume. The VOL1 record
on a volume contains a field which points to where the VTOC exists. The
VTOC is "self described" in the type 4 VTOC record. The VTOC most closely
resembles a keyed BDAM data set (remember, it's not a data set!) which has
a 44 byte hardware key. The hardware key is the same as the DSN. For the
VTOC, the hardware key is 44x'04', that is 44 repetitions of the hex value
x'04'. When z/OS processes the VARY ONLINE command for a DASD device, it
reads the VOL1 record. This validates the volume serial is unique and it
then stores the address of the VTOC in the UCB for other users, such as
DADSM allocation.​

​I don't know what you want to do, but personally, I prefer using the
output from the IDCAMS DCOLLECT command for data set information. Of
course, it is not useful for a "one off" data set requirement. If you want
a VTOC mapping of where data sets reside on a volume, for some reason, then
using ADRDSSU with a PARM='TYPRUN=NORUN' and a DEFRAG command will get you
a fairly nice listing.

You could also do a IEHLIST of the volume.

​Oh, and I also use the REXX / TSO LISTDSI command for data set information
retrieval.​


-- 
The unfacts, did we have them, are too imprecisely few to warrant our
certitude.

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[michelbutz]

I am sorry dont understand what is the VTOC 
Dataset name, there is another dataset on that volume sys1.vvds.v concentrated 
to the volser 

Sent from my iPhone

> On May 3, 2016, at 11:46 AM, J R  wrote:
> 
> VTOC DSN is 44X'4' 
> 
> Sent from my iPhone
> 
>> On May 3, 2016, at 11:30, michelbutz  wrote:
>> 
>> Hi
>> 
>> I need to obtain dataset space information 
>> 
>> I have been looking at the DFSMS advanced services and there seems like a 
>> few away of going about this 
>> 
>> The OBTAIN and camlist seems like the easiest 
>> As all it needs is a dataset name and volser
>> 
>> The CVAF macros seems like the must current
>> But I would need to get (if I am using for instance)
>> CVAFDIR the DEB of the VTOC
>> 
>> 
>> BTW is the VTOC dataset name SYS1.VTOCIX.  (Volser) ?
>> 
>> I guess that would mean allocating and opening it
>> 
>> Any suggestions ?
>> 
>> Sent from my iPhone
>> --
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dataset space information

[J R]

VTOC DSN is 44X'4' 

Sent from my iPhone

> On May 3, 2016, at 11:30, michelbutz  wrote:
> 
> Hi
> 
> I need to obtain dataset space information 
> 
> I have been looking at the DFSMS advanced services and there seems like a few 
> away of going about this 
> 
> The OBTAIN and camlist seems like the easiest 
> As all it needs is a dataset name and volser
> 
> The CVAF macros seems like the must current
> But I would need to get (if I am using for instance)
> CVAFDIR the DEB of the VTOC
> 
> 
> BTW is the VTOC dataset name SYS1.VTOCIX.  (Volser) ?
> 
> I guess that would mean allocating and opening it
> 
> Any suggestions ?
> 
> Sent from my iPhone
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN