Re: How to assign length of generated instructions to macro variable?

Voltaire did say that the best is the enemy of the good. I do not recall his saying that the inadequate is a defensible substitute for the adequate. The ancient saw that time pressures preclude good or 'pretty' work is not finally an intellectual argument at all. It is a rationalization. Finall

Re: How to assign length of generated instructions to macro variable?

retired mainframer wrote When you find a macro construct that handles non-self-defining terms properly, let us know. It is not at all clear to me what this means. The macro language "handles" many kinds of entities that are not self-defining terms. If, however, it means what I suspect that it

Re: How to assign length of generated instructions to macro variable?

WARNING: ***MASSIVE KLUDGE*** If I really need to pass the value of a non-self defining term to a macro, I'll code: WorkArea DSECT WORD DSF FOO DSX BAR DSY WorkLen EQU *-WorkArea : &L SETA WorkLen MyMacro LENGTH=&L This assumes you can define

Re: SUBSCRIBE

You must already be subscribed or the listserv would not have accepted your message. > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > l...@listserv.uga.edu] On Behalf Of Ron.Wells > Sent: Monday, August 18, 2014 12:57 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU >

Re: How to assign length of generated instructions to macro variable?

When you find a macro construct that handles non-self-defining terms properly, let us know. > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > l...@listserv.uga.edu] On Behalf Of Peter Hunkeler > Sent: Monday, August 18, 2014 1:18 PM > To: ASSEMBLER-LIST@LISTSER

Re: How to assign length of generated instructions to macro variable?

Which of the currently available macro-language facilities support computations and comparisons on non-self-defining terms? > -Original Message- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > l...@listserv.uga.edu] On Behalf Of John Gilmore > Sent: Monday, August 18, 2014 11:31

Re: How to assign length of generated instructions to macro variable?

We use code of the form: WorkArea DSECT WORD DSF FOO DSX BAR DSY WorkLen EQU *-WorkArea DS(&WORKL-WorkLen)X If WorkLen exceeds &WORKL, the final DS will have a negative length and therefore generate an assembly time error. Thanks for all the answers

SUBSCRIBE

-- Email Disclaimer This E-mail contains confidential information belonging to the sender, which may be legally privileged information. This information is intended only for the use of the individual or entity addressed

Re: How to assign length of generated instructions to macro variable?

On Mon, 18 Aug 2014 15:43:45 -0400 rkueb...@tsys.com wrote: :>While Robert Ngan's examples are not pretty, they work. Sometimes pretty :>is beyond our time frame of action. Only if you live in a ivory tower with no considerations of reality and business needs. If ones test cases fit into a tin

Re: How to assign length of generated instructions to macro variable?

While Robert Ngan's examples are not pretty, they work. Sometimes pretty is beyond our time frame of action. The back and forth on this (and other) elists is often pretty. It is often informative. The perfect is often the enemy of the adequate. And obliquely, my one tagline is appropriate.

Re: How to assign length of generated instructions to macro variable?

Robert Ngan's examples are much like others already posted, and they suffer from the same defects. Implicit diagnosis by attempting to trigger an assembly error is indicative of something less than full competence in the use of the HLASM. Errors should be detected explicitly using the macro-langu

Re: How to assign length of generated instructions to macro variable?

Additionally, if you need an exact length match, code: WorkArea DSECT WORD DSF FOO DSX BAR DSY WorkLen EQU *-WorkArea DS(&WORKL-WorkLen)X DS(&WorkLen-&WORKL)X Robert Ngan CSC Financial Services Group IBM Mainframe Assembler List wrote on 2

Re: How to assign length of generated instructions to macro variable?

We use code of the form: WorkArea DSECT WORD DSF FOO DSX BAR DSY WorkLen EQU *-WorkArea DS(&WORKL-WorkLen)X If WorkLen exceeds &WORKL, the final DS will have a negative length and therefore generate an assembly time error. Robert Ngan CSC Financial Servi

Re: Can Someone Point Out My error Here

There has been far too much backing and filling in this thread. It is of course permissible, even desirable, to reduce the size of a code sample by pruning irrelevant features, but the resulting snippet must be complete in the sense that its independent execution exhibits the symptoms being compl

Re: How to assign length of generated instructions to macro variable?

On Sun, 17 Aug 2014 20:48:33 -0400 John Gilmore wrote: :>The value of LENGTH defrined by J R can be assigned to an arithmetic :>set symbol, give it the imaginative name/identifier &alength. Then, :>calling the arithmetic [set-symbol] value of the input-length :>parameter &ilength. :> :>|&el

Re: How to assign length of generated instructions to macro variable?

On Sun, 17 Aug 2014 17:25:34 -0600 Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote: :>On 2014-08-17, at 16:43, J R wrote: :>> Binyamin suggested an S-con 0S(expression) :>> which would contain a base and displacement :>> BDDD. By "absolute value" the base would be zero.