Yeah, very sorry, doing too many thing at once.
SYSCALLS("ON") fails with a -3. I don't know that there is much relevant
context. It is about the third line of executable Rexx. Yes, with an "S".
So therefore subsequent SYSCALL "whatever" fails. (No "S".)
The key question: Is this to be expected in a "legacy" batch environment? If
not, what should I look for?
ADDRESS SYSCALL "some syscall command" works. That's what I am using,
successfully.
Charles
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Steve Smith
Sent: Tuesday, June 28, 2022 1:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Some questions on SYSCALL
One-line snippets, typically with typing errors, aren't going to be enough
for someone to diagnose your problem.
For a SWAG, are you clear that the function name is syscalls (with an 's'),
and command environment name is SYSCALL (no 's')?
sas
On Tue, Jun 28, 2022 at 3:45 PM Charles Mills <charl...@mcn.org> wrote:
> I was not super clear, was I? Per
> https://www.ibm.com/docs/en/zos/2.1.0?topic=environment-establishing-syscall
> I coded
>
> SYSCALLS("ON")
>
> And got a -3. Subsequent SYSCALL "whatever" commands failed.
>
> ADDRESS SYSCALL "whatever" works; SYSCALL("ON") did not.
>
> Charles
>
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
