Re: Help building a parameter list
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 Mar 24, 2020, at 9:19 AM, Peter Relson wrote: > > > 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 macro, invoke the CALL macro to do its thing > so that you don't have to write that part yourself. > > Peter Relson > z/OS Core Technology Design
Re: Help building a parameter list
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 macro, invoke the CALL macro to do its thing so that you don't have to write that part yourself. Peter Relson z/OS Core Technology Design
Re: Help building a parameter list
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 Relson wrote: > > Shmuel is of course correct. &DISP(R1) is an incorrect reference to the > "R1" element of &DISP which is not valid syntax, contrast with &DISP(1) > for example. > With the trailing period, &DISP.(R1) says to substitute &DISP and then > append (R1). > > But why write this macro at all? > In what was does the z/OS-provided CALL macro not do exactly what you're > trying to do? > > Peter Relson > z/OS Core Technology Design
Re: Help building a parameter list
Shmuel is of course correct. &DISP(R1) is an incorrect reference to the "R1" element of &DISP which is not valid syntax, contrast with &DISP(1) for example. With the trailing period, &DISP.(R1) says to substitute &DISP and then append (R1). But why write this macro at all? In what was does the z/OS-provided CALL macro not do exactly what you're trying to do? Peter Relson z/OS Core Technology Design
Re: Help building a parameter list
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: >
Re: Help building a parameter list
No, &DISP doesn't have to be a SETC symbol and there's no need to make a copy of &CTR3. Of course, the code would be more readable if you chose better names for the variables than &CTR*. Try putting a period at the end of the name ST R14,&CTR3.(R1) -- Shmuel (Seymour J.) Metz http://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 &PGM,&PARMLST,&PARM1..&PARMC LCLA &CTR1,&CTR2,&CTR3 LCLC &DISP &CTR1 SETAN'&SYSLIST &CTR2 SETA3 &CTR3 SETA 0 LA R1,&PARMLST .LOOP ANOP AIF(&CTR2 EQ CTR1).SETEND .* .* I Think the displacement has to be a SETC symbol not a SETA .* &DISP SETC '&CTR3' LA R14,&SYSLIST(&CTR3) ST R14,&DISP(R1) &CTR1 SETA &CTR1+1 &CTR3 SETA &CTR3+4 AGO .LOOP I am getting the following assembler error "STR14,&DISP(R1)" ** ASMA108E Inconsistent dimension on SET symbol reference; default=0, null, or Whether I was the above syntax Or ST R14,&CTR3(R1) Any guidance appreciated thanks
