I noticed this benign cyst of codein the SNAPX macro. Obviously this has no effect on code generation but executing it a few million times per day could really chew up some cycles. YMMV
.CKLFORM ANOP AIF ('&MF' NE 'L').ARND AIF ('&STORAGE' EQ '').ARND .ARND ANOP Keven -------Original Message------- From: Joseph Reichman <reichman...@gmail.com> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Snap Macro Assembler error ? Here it is thanks Sent: Nov 04 '18 19:06 Here is it is Thanks SETRP RC=4,RETREGS=YES,RETADDR=(R4),FRESDWA=YES,DUMP=YES, X 306 RECORD=YES,RUB=(R3),DUMPOPX=SNAPL 307 SNAPL SNAPX DCB=*-*,PDATA=ALL,SDATA=LSQA,LIST=(R7),STRHDR=L1 CNOP 0,4 01-SNAPX The DCB is the last parameter so I guess SETRP will ignore it SNAPL BAL 1,IHB0010 BRANCH AROUND PARAM LIST DC AL1(0) ID NUMBER DC AL1(115) OPTION FLAGS DC AL1(133) OPTIONS FLAG 2 DC AL1(1) VERSION NUMBER DC AL1(32) SDATA FLAGS ONE DC AL1(0) SDATA FLAGS TWO DC AL1(191) PDATA FLAGS DC AL1(0) RESERVED DC A(*-*) DCB ADDRESS -----Original Message----- From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On Behalf Of Walt Farrell Sent: Sunday, November 4, 2018 7:33 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Snap Macro Assembler error ? On Sun, 4 Nov 2018 12:48:47 -0500, Joseph Reichman <reichman...@gmail.com <mailto:reichman...@gmail.com> > wrote: >I was using the DUMPOPT Parm of SETRP >Say parameter list form of snap >In the end I had to use standard form and include dcb coding DCB=*-* as it's the last parameter I am assuming setrp won't need it Could you show us your final code (both the SETRP and the SNAP) and how the macros expanded? -- Walt