+ BPXWDYN is easy to debug. You can print out the character string parm easy-peasy and see if it is right or wrong.
Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Thursday, August 8, 2019 3:41 PM To: [email protected] Subject: Re: ALLOC or BPXWDYN ? On Thu, 8 Aug 2019 14:19:06 -0500, Lionel B Dyck wrote: >Which is the most efficient in terms of processor resources? > >TSO ALLOC or BPXWDYN? > It probably depends on where you start from. From the TSO READY prompt, ALLOC may be more efficient that "CALL *(BXWDYN) 'arg-string'" because the latter must load a program object. (Is BPXWDYN in LPA?) >From Rexx, BPXWDYN() bypasses the TSO command environment and IKJPARS, a possible saving. Don't know. Efficiency aside, I use BPXWDYN in Rexx because: o I'm familiar with it. o It doesn't restrict my EXECs to running in a TSO environment. o It allows me to concatenate UNIX files and Classic data sets. o The RTDDN key allows me to retrieve temporary DDNAMEs. o ALLOC lacks the INFO key. I use ALLOC for a sort of bootstrapping to allocate SYSEXEC initially. -- gil ---------------------------------------------------------------------- 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
