I've never used BPXWDYN, but I do know that the ancient practice of FREEing a file that is not currently allocated educes a message to that effect. On the other hand, ALLOCATing with REUSE works 'cleanly' whether or not the file is already allocated. I assume that BPXWDYN honors REUSE...
. . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Edward Jaffe <[email protected]> To: [email protected], Date: 01/14/2013 10:16 AM Subject: Re: Beware BPXWDYN (Was: Problem with REXX using OMVS stuff...) Sent by: IBM Mainframe Discussion List <[email protected]> On 1/14/2013 8:38 AM, Kirk Wolf wrote: > Right: It makes sense to me that BPXWDYN would have to dub if you had > MSG(2). > > Ed: is that what you had? The REXX consists of simple free statements (e.g.): rc = BPXWDYN("free dd(SYSPROC)") rc = BPXWDYN("free dd(SYSEXEC)") rc = BPXWDYN("free dd(ISPLLIB)") rc = BPXWDYN("free dd(ISPPLIB)") ... followed by simple alloc/concat statements: /* Allocate SYSPROC */ say "*** Allocating SYSPROC ***" rc=BPXWDYN("alloc dd(SYSPROC) shr reuse da('"clist"')") rc=BPXWDYN("alloc dd(CLIST2) shr reuse da('SYS2.CMDPROC')") rc=BPXWDYN("concat ddlist(SYSPROC,CLIST2)") rc=BPXWDYN("alloc dd(CLIST3) shr reuse da('USER.CLIST')") rc=BPXWDYN("concat ddlist(SYSPROC,CLIST3)") rc=BPXWDYN("alloc dd(CLIST4) shr reuse da('ADCD."adcdver".CLIST')") rc=BPXWDYN("concat ddlist(SYSPROC,CLIST4)") ... -- Edward E Jaffe Phoenix Software International, Inc 831 Parkview Drive North El Segundo, CA 90245 http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
