Not quite; SYSCALL is no longer the current (i.e., implicit) environment but it
is still available as an explicit environment:
address TSO
address SYSCALL foo
/* TSO is still the current envirenment */
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List [[email protected]] on behalf of
Paul Gilmartin [[email protected]]
Sent: Tuesday, June 28, 2022 7:04 PM
To: [email protected]
Subject: Re: Some questions on SYSCALL
On Tue, 28 Jun 2022 15:55:20 -0700, Ed Jaffe wrote:
>On 6/28/2022 3:50 PM, Charles Mills wrote:
>> And another question: what makes ADDRESS SYSCALL "go away"?
>
>Years ago on MVS-OE we were advised by Bill Schoen not to attempt
>SYSCALLS("OFF").
>
>Once you turn it on, leave it on...
>
Good memory, but wrong question.
address TSO /* makes ADDRESS SYSCALL "go away". */
--
gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
