Re: Does the GET macro indicate EOF?

on behalf of Ed Jaffe <17285f33d197-dmarc-requ...@listserv.uga.edu> Sent: Friday, May 10, 2024 3:04 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Does the GET macro indicate EOF? On 5/9/2024 5:41 AM, Binyamin Dissen wrote: > Have your EODAD do > >

Re: Does the GET macro indicate EOF?

On 5/9/2024 5:41 AM, Binyamin Dissen wrote: Have your EODAD do LFI R1,c'EODA' BR R14 Or my favorite value: LFI R1,X'FE0D' Then you can DOEXIT CIJ,R1,LT,0 to exit the loop if negative... -- Phoenix Software International Edward E. Jaffe 831 Parkview

Re: Does the GET macro indicate EOF?

, 2024 6:35 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Does the GET macro indicate EOF? I hope someone can help me; my question pertains to the QSAM GET macro. Please consider this code snippet: OPEN SYSIN GETLOOP GET SYSIN,BUFFER MYEODAD DS0H B

Re: Does the GET macro indicate EOF?

From: IBM Mainframe Assembler List on behalf of Martin Trübner <1237eee49f7e-dmarc-requ...@listserv.uga.edu> Sent: Thursday, May 9, 2024 8:37 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Does the GET macro indicate EOF? set the bit as suggested in a separate EOF routine if y

Re: Does the GET macro indicate EOF?

Thank you so much, everyone; I now understand what I need to do (and I understand why I don't need to dig anything out of the DCB, etc). I hadn't realized (until reading these solutions) that R14 points to the instruction after the GET even when the EODAD routine is called. I'll clear R1 in

RES: Does the GET macro indicate EOF?

The simplest way is using “eodad=eof” De: Gary Weinhold Enviada em: quarta-feira, 8 de maio de 2024 20:21 Para: jb.regin...@gmail.com Assunto: Re: Does the GET macro indicate EOF? As Jose implies, there is no need for a flag to be set at EOF; your DCB specified that the you should enter

Re: Does the GET macro indicate EOF?

Have your EODAD do LFI R1,c'EODA' BR R14 That will not be a record address. On Thu, 9 May 2024 08:18:57 -0400 David Eisenberg wrote: :>>What are you trying to do?< :> :>I'm trying to overcome a limitation in ASMIDF involving single-stepping through code while

Re: Does the GET macro indicate EOF?

, May 8, 2024 7:14 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Does the GET macro indicate EOF? You can set up an EODAD routine that clears R1, and BR 14. You can then just check for R1 being 0 after the GET. I think that will work; I only use GL for QSAM. sas

Re: Does the GET macro indicate EOF?

set the bit as suggested in a separate EOF routine if you use the BR 14 to end your EOF handling, you have a bit to test after the GET. so it looks like this GET_LOOP  DS 0H    GET  DCB RESUME DS 0H    TM FLAG,BIT    JO  REAL_EOF SET_FLAG DS 0H    OI  FLAG,BIT    J   RESUME DCB

Re: Does the GET macro indicate EOF?

macro indicate EOF? >What are you trying to do?< I'm trying to overcome a limitation in ASMIDF involving single-stepping through code while debugging. That's the only reason I'm asking about this. As per the IBM documentation, ASMIDF's single-stepping process involves the automatic pla

Re: Does the GET macro indicate EOF?

>What are you trying to do?< I'm trying to overcome a limitation in ASMIDF involving single-stepping through code while debugging. That's the only reason I'm asking about this. As per the IBM documentation, ASMIDF's single-stepping process involves the automatic placement and removal of

Re: Does the GET macro indicate EOF?

If the manual doesn't state the content of R1, don't rely on it :-) The only thing you really need to sense EOF is to know that the branch to the specified EODAD has been taken, so (as you mention) I would normally keep MYEODAD DS 0H outside the loop. I'm not aware of any quirks of IDF, so I'll

Re: Does the GET macro indicate EOF?

Hi David, Have you acces to a DEB block ? there is the DEBEOF flag Just in case... René Le jeudi 9 mai 2024 à 04:18:29 UTC+2, David Eisenberg a écrit : Peter, Yes... I'm using ASMIDF. I can definitely set a manual breakpoint on the EOF label, and the breakpoint will be

Re: Does the GET macro indicate EOF?

Doctor, doctor, it hurts when I do this. Obviously you do not want to simply branch after the EOF returns after the GET, as you can simply set the EOF to there. You can alter the EODAD in the DCB if you wish to conditionally change where the EOF goes. What are you trying to do? On Wed, 8 May

Re: Does the GET macro indicate EOF?

zXDC? It allows one to step through code Just say 'n'. Steve Thompson On 5/8/2024 10:17 PM, David Eisenberg wrote: Peter, Yes... I'm using ASMIDF. I can definitely set a manual breakpoint on the EOF label, and the breakpoint will be honored... but that's not my problem. The issue

Re: Does the GET macro indicate EOF?

Peter, Yes... I'm using ASMIDF. I can definitely set a manual breakpoint on the EOF label, and the breakpoint will be honored... but that's not my problem. The issue pertains to single-stepping; in my case, using IDF's STMTSTEP command. The code doing the GET resides in an external subroutine

Re: Does the GET macro indicate EOF?

You can set up an EODAD routine that clears R1, and BR 14. You can then just check for R1 being 0 after the GET. I think that will work; I only use GL for QSAM. sas

Re: Does the GET macro indicate EOF?

single-stepping at GETLOOP? Assuming the DCB has EODFAD=EOF of course. Peter From: IBM Mainframe Assembler List On Behalf Of David Eisenberg Sent: Wednesday, May 8, 2024 6:35 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Does the GET macro indicate EOF? I hope someone can help me; my

RES: Does the GET macro indicate EOF?

the GET macro indicate EOF? I hope someone can help me; my question pertains to the QSAM GET macro. Please consider this code snippet: OPEN SYSIN GETLOOP GET SYSIN,BUFFER MYEODAD DS0H B GETLOOP EOF CLOSE SYSIN * SYSINDCB DDNAME=SYSIN,MACRF=GM

Does the GET macro indicate EOF?

I hope someone can help me; my question pertains to the QSAM GET macro. Please consider this code snippet: OPEN SYSIN GETLOOP GET SYSIN,BUFFER MYEODAD DS0H B GETLOOP EOF CLOSE SYSIN * SYSINDCB