John MACRF is quite different from your starting point, the DD-name. It was probably when I started trying to be flexible with some VTAM entity similar to your MACRF that I discovered that these macros were just not designed to be flexible enough to mimic "or"ing on bits or "and"ing them off in the primary control blocks such as, in my case, principally the RPL as - as I said before - I had always done in the past - up to 1982 or so - and as I have done ever since - always saving time and effort by totally ignoring those "weird and wonderful" macros!
Chris Mason ----- Original Message ----- From: "Bodoh John Robert" <[email protected]> To: <[email protected]> Sent: Thursday, March 08, 2012 1:05 AM Subject: Re: Non-Flexible VSAM macros That might be but I still need a meth of handling MACRF options as input. That I cannot figure out. If I had asked befor, please excuse my senior moments. John -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Tony Harminc Sent: Wednesday, March 07, 2012 5:32 PM To: [email protected] Subject: Re: Non-Flexible VSAM macros On 7 March 2012 16:05, Bodoh John Robert <[email protected]> wrote:
I have been trying to use the VSAM macros to generate and modify an ACB. One of the things I would like to modify is the DDNAME. The DDNAME actually comes into my program as a parameter so I would like to issue a MODCB ACB=...DDNAME=(R3) but I get an error because the DDNAME parameter is not a character string. How can I set the DDNAME in an ACB where the name is dynamic?
Did you not ask and have answered in great detail this very same question on Feb 9 of this year? Tony H.
