Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
För Itschak Mugzach
Skickat: den 26 oktober 2012 14:22
Till: IBM-MAIN@LISTSERV.UA.EDU
Ämne: Re: Disabling interrupt and trace for Rexx execs
I don't care that the user will look at the program logic. He is not
authorized to execute some
I don't care that the user will look at the program logic. He is not
authorized to execute some of the commands in the program. The thing is
that I do not want the user to get control when the program run as they can
see run-time results of the program or even exit from the program.
I tried Russ
Itschak Mugzach imugz...@gmail.com wrote:
I don't care that the user will look at the program logic. He is not
authorized to execute some of the commands in the program. The thing is
that I do not want the user to get control when the program run as they can
see run-time results of the program or
In 5089dd6d.8050...@valley.net, on 10/25/2012
at 08:46 PM, Gerhard Postpischil gerh...@valley.net said:
FSVO decades.
Decades meaning prior to 1979. My recollection is that SMC=SYSTEM was
dropped in the transition from OS/VS2 R1 (SVS) to OS/VS2 R2 (MVS), but
IAC see below.
It's in OS/390;
On 10/26/2012 12:31 PM, Shmuel Metz (Seymour J.) wrote:
Decades meaning prior to 1979. My recollection is that SMC=SYSTEM was
dropped in the transition from OS/VS2 R1 (SVS) to OS/VS2 R2 (MVS), but
IAC see below.
We ran SVS long after 1979, and jumped to MVS/SP; somehow I
overlooked or forgot
In 5087f360.2060...@valley.net, on 10/24/2012
at 09:55 AM, Gerhard Postpischil gerh...@valley.net said:
If you want to prevent interruptions, the stand way is to issue an
ENQ with the (authorized) System Must Complete (SMC) option.
Hasn't that been dead for decades? Certainly the current
In
7519195663602734.wa.elardus.engelbrechtsita.co...@listserv.ua.edu,
on 10/24/2012
at 09:23 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za
said:
Try this in REXX: ISPEXEC CONTROL DISPLAY LOCK
Only if he's running under ISPF.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
On 24 Oct 2012 05:01:57 -0700, in bit.listserv.ibm-main
(Message-ID:CAOdPEgS8iox=fbnffUY0s76c1DFkaRo9B=kwt3k_xtrm810...@mail.gmail.com)
imugz...@gmail.com (Itschak Mugzach) wrote:
We have a rexx exec that performs functionality we don't
want to be
interrupted or traced in any way.
I infer
On 10/25/2012 4:17 PM, Arthur T. wrote:
I infer from your desire not to be traced that you'd like to
keep the actual code hidden from the users. Unless you've
compiled your REXX code, all they need to do is look directly at
the code. Even if that isn't the reason, if your code isn't
compiled a
On Thu, 25 Oct 2012 17:28:45 -0400, Dave Salt wrote:
Unless IBM has made changes recently, a compiled REXX program
retains all the source. This is used to run at installations
that don't license the compiler, but only the interpreter.
Gerhard Postpischil
That's true, but REXX can be
From: paulgboul...@aim.com
Compiled in such a way that it can't run at installations that don't
license the compiler? Or encrypted, where only the interpreter has the key?
Even though the source code isn't visible, it's still there and can still be
executed at sites that don't license the
On 10/25/2012 10:28 AM, Shmuel Metz (Seymour J.) wrote:
Hasn't that been dead for decades? Certainly the current version of
ENQ only accpets SMC=NONE and SMC=STEP.
FSVO decades. It's in OS/390; I haven't had a chance to try it
under z/OS. And there is always the possibility that they kept
We have a rexx exec that performs functionality we don't want to be
interrupted or traced in any way. this mean that we need to disable the
functions keys that might return control to the user, such as the
Attention, PA1, PA2 keys. We play to write a small program that will call
the TSO macros
On 10/24/2012 8:01 AM, Itschak Mugzach wrote:
We have a rexx exec that performs functionality we don't want to be
interrupted or traced in any way. this mean that we need to disable the
functions keys that might return control to the user, such as the
Attention, PA1, PA2 keys. We play to write a
I don't care for serialization, but wish to lock the keyboard until the end
of the rexx execution. I know doing this with TSO macros, but just checking
if Rexx can do this as well. If the keyboard is locked, the user can't
enter debug mode (msg
ITschak
On Wed, Oct 24, 2012 at 3:55 PM, Gerhard
Itschak Mugzach wrote:
I don't care for serialization, but wish to lock the keyboard until the end of
the rexx execution. I know doing this with TSO macros, but just checking if
Rexx can do this as well. If the keyboard is locked, the user can't enter
debug mode (msg
Try this in REXX: ISPEXEC
*/
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Elardus Engelbrecht
Sent: Wednesday, October 24, 2012 10:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Disabling interrupt and trace for Rexx execs
Itschak Mugzach wrote:
I don't care
17 matches
Mail list logo
