The call turns the last parameter high order
Bit on I am using the last parameters as as follows header
And starting and ending pairs of storage to dump Using LIST parameter on SNAP
Towards that it’s not the last parameter the I need x’80’ bit on but the one
before the last
Thanks
> On
In case of a bad return code I WTO r15 and r0 in ebcdic and then use the
wto message as a header as the first parameter when I build a parameter
list to call a program to snap relevant variables the variables in the
macro I use to build LIST= parm on the SNAP
So do that but, within your
In case of a bad return code I WTO r15 and r0 in ebcdic and then use the wto
message as a header as the first parameter when I build a parameter list to
call a program to snap relevant variables the variables in the macro I use to
build LIST= parm on the SNAP
On Mar 23, 2020, at 8:44 AM, Peter
Shmuel is of course correct. (R1) is an incorrect reference to the
"R1" element of which is not valid syntax, contrast with (1)
for example.
With the trailing period, (R1) says to substitute and then
append (R1).
But why write this macro at all?
In what was does the z/OS-provided CALL macro
Thanks
Joe Reichman
Lead Developer Sam Golob Systems Programming
71-28 163 rd st apt 1A
Fresh meadows NY 11365
> On Mar 22, 2020, at 11:24 AM, Seymour J Metz wrote:
>
://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Joe Reichman [reichman...@gmail.com]
Sent: Sunday, March 22, 2020 10:56 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Help building a parameter list
Hi
I have a macro which takes a variable number of parameters as parameters
to a called program best I give any example
CALLPGM ,,
LCLA ,,
LCLC
SETAN'
SETA3
SETA
