Re: VTOC reading

2019-06-17 Thread Seymour J Metz
m: IBM Mainframe Discussion List on behalf of Greg Price Sent: Monday, June 17, 2019 10:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: VTOC reading On 2019-06-14 7:58 AM, Mike Shaw wrote: > CVAF is much slower than BSAM, alphabetical order or not. EXCP with > chained CCWs is much faste

Re: VTOC reading

2019-06-17 Thread Greg Price
ad separately donated the code to the CBT tape in the 1980s. As TLCMz level 3 from 2008 until it went EOS in 2010, I was interested to see that they had used the same routine in their DASD scanner - the "Surveyor". So, XVTCREAD - the VTOC reading routine originally written around 1

Re: VTOC Reading

2019-06-15 Thread Binyamin Dissen
Have you tried: DSN='44 bytes of x'04'',DISP=SHR,UNIT=SYSDA,VOL=SER=volser Note that the DSNAME value is in quotes and is 44 repetitions of the unprintable x'04' On Fri, 14 Jun 2019 10:03:08 -0400 Bill Ogden wrote: :>Thank you all! My old memory seemed to recall something like :>DSN=VTOC.FO

Re: VTOC reading

2019-06-14 Thread Matthew Stitt
You are correct. I did mean to type 527 for the file number. 529 has several COBOL programs which can process various SMF data records. Matthew On Fri, 14 Jun 2019 20:38:54 +, David Spiegel wrote: >Hi Matthew, >I think that you meant File 527. > >Regar,s, >David > >On 2019-06-14 15:18,

Re: VTOC reading

2019-06-14 Thread David Spiegel
Hi Matthew, I think that you meant File 527. Regards, David On 2019-06-14 15:18, Matthew Stitt wrote: > If what you want is to find a dataset, then program DADSM on CBT file 529 > will do what you want. > > P.S. I have an updated version if you would like it. Let me know (privately > preferre

Re: VTOC reading

2019-06-14 Thread Matthew Stitt
If what you want is to find a dataset, then program DADSM on CBT file 529 will do what you want. P.S. I have an updated version if you would like it. Let me know (privately preferred). Matthew On Fri, 14 Jun 2019 08:41:35 -0700, Tom Brennan wrote: >On 6/14/2019 7:12 AM, Bill Ogden wrote:

Re: VTOC reading

2019-06-14 Thread Tom Brennan
On 6/14/2019 7:12 AM, Bill Ogden wrote: Wow. Everyone is being helpful. Yes! But only because nobody mentioned mainframe security or AMODE 32 :) I have to say when I saw that DSN=FORMAT4.DSCB post I said, "What???" and immediately went off to try it. Then I saw Skip's post about ZAP. -

Re: VTOC reading

2019-06-14 Thread Bill Ogden
Wow. Everyone is being helpful. I am making a temporary ("one shot") tool to help with a different problem that might involve dataset locations on DASD. Was thinking of reading the VTOC directly versus picking fields out of a IEHLIST DUMP listing. At the moment I am going with the IEHLIST l

Re: VTOC Reading

2019-06-14 Thread Bill Ogden
Thank you all! My old memory seemed to recall something like DSN=VTOC.FORMAT4 which, while on the right general track, obviously does not work. Never thought to look in Superzap for the information. Bill -- For IBM-MAI

Re: VTOC reading

2019-06-13 Thread Mike Shaw
On 6/13/2019 1:43 PM, Lennie Dymoke-Bradshaw wrote: Rather than do BSAM reads I think it is better to make use of the CVAF macros. These make use of the VTOC Index to assist processing. This will present you the data set names in alphabetical order. CVAF is much slower than BSAM, alphabetical

Re: VTOC reading

2019-06-13 Thread Seymour J Metz
x27;. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Bill Ogden Sent: Thursday, June 13, 2019 11:44 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: VTOC reading My old memory is failing in too many areas.

Re: VTOC reading

2019-06-13 Thread Edward Finnell
FILE182 is an awesome tool with references to other tools to help organize the windmills.* Member Original source Description (CP is command processor) * -|-|-- * BLKDISK | (CBT FILE 296) | Disk block size optimizing CP * COBANAL | (CB

Re: VTOC reading

2019-06-13 Thread Lizette Koehler
right process can be identified Lizette > -Original Message- > From: IBM Mainframe Discussion List On Behalf Of > Lennie Dymoke-Bradshaw > Sent: Thursday, June 13, 2019 10:43 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: VTOC reading > > Rather than do BSAM re

Re: VTOC reading

2019-06-13 Thread Lennie Dymoke-Bradshaw
ching. Encrypt like everyone is.' -Original Message- From: IBM Mainframe Discussion List On Behalf Of svet...@ameritech.net Sent: 13 June 2019 17:40 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] VTOC reading Are used to do it in programs a while ago. First do a dynami

Re: VTOC reading

2019-06-13 Thread svetter
Are used to do it in programs a while ago. First do a dynamic allocate Specifying a DS name of 44 characters of hex 04 for 44 characters and specify the valves there that you want. There is a mapping macro that describes each record that you can use. Do an open a read or a get as appropriate. T

Re: VTOC reading

2019-06-13 Thread Jesse 1 Robinson
Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tony Harminc Sent: Thursday, June 13, 2019 9:19 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: VTOC reading On Thu, 13 Jun 2019 at 11:48, John McKown wrote: > On Thu, Jun 13,

Re: VTOC reading

2019-06-13 Thread Tony Harminc
On Thu, 13 Jun 2019 at 11:48, John McKown wrote: > On Thu, Jun 13, 2019 at 10:44 AM Bill Ogden wrote: > > > My old memory is failing in too many areas. Long ago, I seem to recall, > > there was an easy way to read a VTOC with simple JCL using a "magic" > > DSNAME - obviously not 040404... f

Re: VTOC reading

2019-06-13 Thread David W Noon
On Thu, 13 Jun 2019 11:44:24 -0400, Bill Ogden wrote abour VTOC reading: > My old memory is failing in too many areas. Long ago, I seem to recall, > there was an easy way to read a VTOC with simple JCL using a "magic" > DSNAME - obviously not 040404... for JCL, but some

Re: VTOC reading

2019-06-13 Thread John McKown
On Thu, Jun 13, 2019 at 10:48 AM John McKown wrote: > On Thu, Jun 13, 2019 at 10:44 AM Bill Ogden wrote: > >> My old memory is failing in too many areas. Long ago, I seem to recall, >> there was an easy way to read a VTOC with simple JCL using a "magic" >> DSNAME - obviously not 040404... f

Re: VTOC reading

2019-06-13 Thread John McKown
On Thu, Jun 13, 2019 at 10:44 AM Bill Ogden wrote: > My old memory is failing in too many areas. Long ago, I seem to recall, > there was an easy way to read a VTOC with simple JCL using a "magic" > DSNAME - obviously not 040404... for JCL, but some other name. Is my > memory correct? What

VTOC reading

2019-06-13 Thread Bill Ogden
My old memory is failing in too many areas. Long ago, I seem to recall, there was an easy way to read a VTOC with simple JCL using a "magic" DSNAME - obviously not 040404... for JCL, but some other name. Is my memory correct? What is the DSNAME? While playing with google I cannot find a