On Thu, Oct 19, 2017 at 2:55 PM, PINION, RICHARD W. < [email protected]> wrote:
> John your last assumption is correct. What I'm attempting to do is this. > We have utility A, which I want to replace with utility B without making > hundreds of JCL changes, and going through change control. > > I have an assembler program which invokes CLIST/REXX. I'll rename my > assembler program to the name of utility A. My program will invoke my > CLIST/REXX, which will parse the SYSIN statements that went into utility A, > and create the appropriate statements for utility B. Utility A used a tape > as output. Utility B will use that name as its control file name, and > perform its version of what utility A did, with its own output going to > another tape data set name. > Why use REXX at all? You can use RDJFCB in HLASM with a DCB to get the DSN on the JCL DD statement. You can then use either SVC 99 or BPXWDYN to easily free, then allocate a disk data set with the DSN gotten from the RDJFCB. If you never did an OPEN on the tape data set, then it will not be catalogued so there is no need to do any kind of "delete" processing on it. Tapes which are not OPEN'd are simply never catalogued because the physical tape was never written to. OPEN creates the HDR1/HDR2 records, not allocation. -- I just child proofed my house. But the kids still manage to get in. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
