Well, suffice it to say, Easytrieve allows one to define a variable following the BPXWDYN non-REXX return variable structure and allows BPXWDYN to return a value for use in the Easytrieve program.
After playing with different options all day, I have successfully called Easytrieve with an INFO request, FREE request and ALLOC request. All of these requests following BPXWDYN's non-REXX calling requirements. Charles (Chuck) Hardee Senior Systems Engineer/Database Administration EAS Information Technology Thermo Fisher Scientific 300 Industry Drive | Pittsburgh, PA 15275 Phone +1 (724) 517-2633 | Mobile +1 (412) 877-2809 | FAX: +1 (412) 490-9230 chuck.har...@thermofisher.com | www.thermofisher.com WORLDWIDE CONFIDENTIALITY NOTE: Dissemination, distribution or copying of this e-mail or the information herein by anyone other than the intended recipient, or an employee or agent of a system responsible for delivering the message to the intended recipient, is prohibited. If you are not the intended recipient, please inform the sender and delete all copies. -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul Gilmartin Sent: Tuesday, January 31, 2017 7:24 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Calling bpxwdyn from CA-Easytrieve On 2017-01-31, at 17:04, Hardee, Chuck wrote: > In order to return a value from BPXWDYN to an Easytrieve caller, one must use > the variable definition as follows: > > VARFIELD DC Y(L'VARVALUE) > VARVALUE DC CLx('......') > > Where 'x' is large enough to contain the maximum value that can be returned. > For example, a dataset name's max length is 44 characters so in this example, > x would be 45. > > The keyword representing the value to be returned must start in position 1 of > VARVALUE and must include a SPACE at the end of the keyword. > For instance, if one wants the dataset name associated with an allocated > DDname, then the VARVALUE would be coded as 'INRTDSN '. > That describes (some of) BPXWDYN's requirements. It makes no presentation of whether Easytrieve supports return values in CALL arguments, which is an uncommon practice. I believe it is more commom to pass the address of a reply buffer rather than expecting the reply to replace the argument string itself. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
