Peter-Jacob
commented
1 year ago Which BREXX release are you running? Von meinem Huawei-Telefon gesendet-------- Ursprüngliche Nachricht --------Von: Vittimj @.>Datum: Mi., 21. Juni 2023, 15:37An: mvslovers/brexx370 @.>Cc: Subscribed @.**>Betreff: [mvslovers/brexx370] Multiple read Execio in a single script (Issue #106) On MVS3.8J (Turnkey MVS) I am trying to have a REXX session running in a loop that will accept commands from a PL/I (F) program and pass the results back. The commands will include things like does this dataset exist, is that member in the LNKLST concatenation, provide dataset information). I thought the simplest solution was to have the PL/I program write a request to a file, then BREXX/370 (in a wait, read, exec, wait) loop read and process the request, writing the results back. My initial testing shows that the second EXECIO causes a BREXX/370 abend, while the first one works perfectly well. I saw some debugging code you provided elsewhere and incorporated that, into the below: NOT_OK = 28 OK = 0 "EXECIO DISKR PLAN (STEM xxxrec. finis" If rc <> OK Then Do Say "EXECIO gave RC = "rc Exit NOT_OK End say xxxrec.0 "records read" do i = 1 to xxxrec.0 say xxxrec.i end say "next execio" "EXECIO DISKR PLAN (STEM xxxrec. finis" If xxxrec.0 = 0 Then Do Say 'XXX001E: NO DATA RECORDS READ' Return 16 End Exit 005 /===================================================================/ ohShit: /-------------------------------------------------------------------/ / Rexx Error routine. Called on Syntax error. Issue error details & / / terminate the script with the return code. / /-------------------------------------------------------------------*/ _errorrc = rc Parse source . . _exec . Say 'An error has been encountered in '||_exec Say 'Return code is: ' _errorrc Say 'The line of code in question is:' Sourceline(Sigl)'.' Say Errortext(_errorrc) Say ' ' Exit rc //EXEC.PLAN DD DSN=SYS3.EZRJCL.CONTROL(REXXPORT),DISP=SHR the input jobstream, output pdf result and a screen shots of the control file are attached. I get the abend even when I use different DDnames, such as PLAN, PLAN1, PLAN2 (etc). I could abandon this approach and have each script submit another version of its batch job (instead of having a wait loop), but this is a cleaner solution. Any advice or thoughts?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
Vittimj
On MVS3.8J (Turnkey MVS) I am trying to have a REXX session running in a loop that will accept commands from a PL/I (F) program and pass the results back.
The commands will include things like does this dataset exist, is that member in the LNKLST concatenation, provide dataset information).
I thought the simplest solution was to have the PL/I program write a request to a file, then BREXX/370 (in a wait, read, exec, wait) loop read and process the request, writing the results back.
My initial testing shows that the second EXECIO causes a BREXX/370 abend, while the first one works perfectly well. I saw some debugging code you provided elsewhere and incorporated that, into the below:
NOT_OK = 28
OK = 0
"EXECIO * DISKR PLAN (STEM xxxrec. finis"
If rc <> OK
Then Do
Say "EXECIO gave RC = "rc
Exit NOT_OK
End
say xxxrec.0 "records read" do i = 1 to xxxrec.0 say xxxrec.i end
say "next execio"
"EXECIO * DISKR PLAN (STEM xxxrec. finis"
If xxxrec.0 = 0
Then Do
Say 'XXX001E: NO DATA RECORDS READ'
Return 16
End
Exit 005
/===================================================================/ ohShit:
/-------------------------------------------------------------------/ / Rexx Error routine. Called on Syntax error. Issue error details & / / terminate the script with the return code. / /-------------------------------------------------------------------/ _errorrc = rc
Parse source . . _exec .
Say 'An error has been encountered in '||_exec Say 'Return code is: ' _errorrc
Say 'The line of code in question is:' Sourceline(Sigl)'.'
Say Errortext(_errorrc)
Say ' '
Exit rc //EXEC.PLAN DD DSN=SYS3.EZRJCL.CONTROL(REXXPORT),DISP=SHR
the input jobstream, output pdf result and a screen shots of the control file are attached.
I get the abend even when I use different DDnames, such as PLAN, PLAN1, PLAN2 (etc). I could abandon this approach and have each script submit another version of its batch job (instead of having a wait loop), but this is a cleaner solution.
Any advice or thoughts?