Hi Folks,

When you're making a new system or new catalogs, isn't it nice to generate DEFINE statements for most of the stuff that's in there? Especially if it is a new system and a new master catalog. OR, are you cleaning up the master catalog to make sure there's no junk that got cataloged in there and was never removed?

Well, most of us remember (or still use) the MCNVTCAT program that IBM used to distribute with the CBIPO's and CBPDO's. With MCNVTCAT, you get the DEFINE statements for all NONVSAM entries in a catalog, and also you get an indication of the VSAM stuff cataloged in there as well. BUT, IBM stopped distributing MCNVTCAT. What were we to do?

One person, Alastair Gray, did a lot. Alastair wrote a REXX program called RCNVTCAT which does everything that MCNVTCAT did, but was easier to use. RCNVTCAT is a public domain program, and is on File 542 of the CBT Tape.

BUT, RCNVTCAT stopped working when SWA is above the line, for TSU's (set in JOBCLASS(TSU) of JES2PARM if you have JES2).

So, Lionel Dyck fixed RCNVTCAT to work (as a TSO command written in REXX) so it works for SWA above the line. Also, Lionel's version allocates the output pds (which contains the information) permanently, instead of the temporary pds which the original RCNVTCAT generated.

However, RCNVTCAT had a UNIX component with it, and we didn't know if it worked or not.

SO, John McKown did an extensive rework of the UNIX component in RCNVTCAT, and now it works fine there too.

How do you get all this fixed-up stuff? It is on CBT Tape File 542 on the UPDATES page of www.cbttape.org. Lionel's version is called RCNVTCAT, and John's souped up version is member SCNVTCAT. SCNVTCAT can work under TSO giving the same results as RCNVTCAT. And SCNVTCAT also has John's extended UNIX support.

    Cool.  Use them in good health!

Sincerely,    Sam

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to