No runs, no drips, no errors (Johnny Bench, Krylon spray paint commercial).
"Confidentially doc, I am the wabbit." Bugs Bunny Sent with Proton Mail secure email. On Thursday, August 14th, 2025 at 11:58 AM, Jousma, David <[email protected]> wrote: > I personally use the similar feature in FDRREPORT to generate the IDCAMs > statements. It generates for all datasets on the volume. I just run it as-is, > and those that already have an indirect catalog entry just get a RC 8 or 12, > and all the missing ones get created. No harm, no foul. > > > > > > > > > From: IBM Mainframe Discussion List [email protected] on behalf of > David Spiegel [email protected] > > Date: Thursday, August 14, 2025 at 11:29 AM > To: [email protected] [email protected] > > Subject: Re: Indirect cataloging comparing > > CAUTION EXTERNAL EMAIL > This message came from outside your organization. > DO NOT open attachments or click on links from unknown senders or unexpected > emails. > Report > Suspicioushttps://us-phishalarm-ewt.proofpoint.com/EWT/v1/MwwqYLOC6b6whF7V!odOEVDElgiBh_ko5LBkON29aNPXiyTA57thPo0O-yTU1FdH9K4t1h6VGOD1AgkPw2rlnXu43DSFxrN7YULJW17mIq3fgrAZj6Vc7F_f0RMXJlNuH5RfBud0QirtsmFAGev5eXg5gl4IFPA$ > > > > Hi Mike, > Does this list tell the user that e.g. SYS1.LINKLIB is already CATLGd, > but, SYS1.SGRBLNK is not? > > Regards, > David > > On 2025-08-14 10:49, Mike Shaw wrote: > > > I am late to this, but MVS/QuickRef supplies a Rexx function that can be > > used to extract a list of all the data sets on a DASD volume and store each > > DSN in a stem variable instance. > > > > You could invoke it like this: > > > > X =QWIKREXX(N=volser) > > > > and the stem variable 'qwilines.' would contain the DSNs, with qwilines.0 > > holding the count of the number of data sets names returned. > > > > Mike Shaw > > MVS/QuickRef Support Group > > Chicago-Soft, Ltd. > > > > On Wed, Aug 13, 2025, 11:29 PM David Spiegel < > > [email protected]> wrote: > > > > > Hi Jon, > > > It's a lot easier to use the VTOC Command Processor (CBT File 112) than > > > to do what you're describing. > > > > > > Regards, > > > David > > > > > > On 2025-08-13 15:55, Jon Perryman wrote: > > > > > > > On Wed, 13 Aug 2025 11:57:11 +0400, Jake Anderson < > > > > [email protected]> wrote: > > > > > > > > > Is it possible to compare two SYSRES volume dataset and generate > > > > > indirect > > > > > cataloging JCL for the new ones alone ? > > > > > If you use VTOCLIST, realize it might have duplicate DSN's for > > > > > multiple > > > > > extents. > > > > > ISPEXEC LMDxxx returns REXX compatible list of datasets on a volume or > > > > > dsn prefix similar to ISPF 3.4. You could LISTDSI or LISTDS for each > > > > > dataset to find the uncataloged datasets. > > > > > Alternatively, you could use ISPEXEC LMDxxx for old sysres and create > > > > > stem variables for the datasets (e.g. DSN.dataset-name) and LMDxxx > > > > > for the > > > > > new volume that checks if the stem variable exists. > > > > > Another possibility, you could use ISPF 3.4 (sort if necessary), save > > > > > the list for both volumes, edit the new sysres list, set bounds for > > > > > the > > > > > DSN, compare to old sysress and keep only new lines. > > > > > If ISPF 3.4 supports == line command, then you could create an exec > > > > > that > > > > > catalogs an uncataloged dataset. specify the exec name on the first > > > > > dataset, == on the second and == on the last. > > > > > ---------------------------------------------------------------------- > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > ---------------------------------------------------------------------- > > > > > For IBM-MAIN subscribe / signoff / archive access instructions, > > > > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > > > This e-mail transmission contains information that is confidential and may be > privileged. It is intended only for the addressee(s) named above. If you > receive this e-mail in error, please do not read, copy or disseminate it in > any manner. If you are not the intended recipient, any disclosure, copying, > distribution or use of the contents of this information is prohibited. Please > reply to the message immediately by informing the sender that the message was > misdirected. After replying, please erase it from your computer system. Your > assistance in correcting this error is appreciated. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
