On Tue, May 5, 2015 at 9:28 AM, Scott Ford <[email protected]> wrote:
> All, > > Since I started this "question", so how is "one" to check for the existence > of datasets if we can't really trust IEFBR14 ? Yeah, I can write an > Assembler routine, by why, when BR14 is supposed to work...I have staging > datasets we use to build our product, my first step is the IEFBR14 , to > delete these datasets if they exist, if not fine give me a return code I > can test for and proceed on with the other steps. > > Regards, > > Scott > > ​Personally, I bypassed the HRECALL problem by simply using IDCAMS instead of IEFBR14. It has some drawbacks for general purposes. I.e. cannot change the HLQ of a DSN via a JCL symbolic. But it worked for me. Most of the programmers here get around the problem by making CA-11 the first step in their JCL, and let _it_ determine which DSNs need to be deleted. CA-11 uses IDCAMS to do the deletion and so does not suffer from the HRECALL delay. And it has the plus of always being up-to-date with any JCL changes, unlike an IDCAMS or IEFBR14 step. ​ -- If someone tell you that nothing is impossible: Ask him to dribble a football. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
