You'll never be able to stop people from copying files to their A disk - and
making modifications - including removing any checks you make for an X disk,
etc. Users can do an EXECDROP or EXECLOAD on their own - there's not many
good ways to stop a determined user from shooting themselves in
Once it's loaded in memory -- what prevents that determined user from
reading it out of memory and creating a file? Might have to write your own
module.. but I'm just saying ;-)
Scott Rohling
On Fri, Oct 15, 2010 at 8:11 AM, David Boyes dbo...@sinenomine.net wrote:
You'll never be able to
If they're THAT good, hire them. 8-)
On Oct 15, 2010, at 10:53 AM, Scott Rohling
scott.rohl...@gmail.commailto:scott.rohl...@gmail.com wrote:
Once it's loaded in memory -- what prevents that determined user from reading
it out of memory and creating a file? Might have to write your own
On Fri, Oct 15, 2010 at 10:05 AM, David Boyes dbo...@sinenomine.netwrote:
If they're THAT good, hire them. 8-)
Yeah -- they shouldn't be an end user but running the system :-)
I'm wondering too about Sergio saying that users are taking the EXEC and
modifying it to their purposes.. I would
Subject:Re: REXX that verify what MINIDISK is a file
Years ago we used the alternative EXEC processor support to encrypt our execs
and make these the ones the users executed.
On 10/15/10 12:51 PM, gclo...@br.ibm.com gclo...@br.ibm.com wrote:
Hi,
A lot of years ago (VSE age), I saw a similar problem: how to protect an exec
that puts controlled
...@tampabay.rr.com
To:
IBMVM@LISTSERV.UARK.EDU
Date:
15/10/2010 02:07
Subject:
Re: REXX that verify what MINIDISK is a file
Sent by:
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
--
Sergio,
As Scott suggests, compiling is the first step to protect yourself
outname outtype outmode. Options include LIST, XREF and
REPLACE.
Peter
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Neale Ferguson
Sent: October 15, 2010 13:04
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: REXX that verify what
Subject:Re: REXX that verify what MINIDISK is a file
: Thursday, October 14, 2010 5:17 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: REXX that verify what MINIDISK is a file
Hello Mike,
Thanks very much from your good explanation.
We need that the user execute our EXEC from a public dasd (Maint 31a), because,
We try track who executed
Les,
Thanks very much from your opinion also.
Of course, I'm I'm learning a lot with this problem.
Best Regards,
Sergio
Date: Fri, 15 Oct 2010 01:14:24 -0400
From: vmr...@tampabay.rr.com
Subject: Re: REXX that verify what MINIDISK is a file
To: IBMVM@LISTSERV.UARK.EDU
Sergio
99
Thanks very much, Jim.
Best Regards,
Sergio
Date: Thu, 14 Oct 2010 17:33:36 -0400
From: jim.hug...@doit.nh.gov
Subject: Re: REXX that verify what MINIDISK is a file
You have to be careful with syntax like this:
Parse Source . 'EXEC' fm +1 .
The variable fm is assigned the value E, taken from the first letter
of
EXEC. You wanted it to be assigned the first character in the word
following EXEC.
How embarrassing!
I did a couple of quick tests in RexxTry, then proceeded to
cut-n-paste the wrong one.
Mea culpa.
That line should read:
Parse Source . 'EXEC' . +5 fm +1 .
or more succinctly (if less clear):
Parse Source 'EXEC' +5 fm +1
Sorry for the confusion.
-Chip-
On 10/15/10
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on X
acessed minidisk.
So, try with STATE command without succesfull and now try with LISTFILE
command.
If execute like this :
9 *-* 'LISTFILE cataa exec x (DATE STACK LIFO'
Of Sergio Lima
Sent: Thursday, October 14, 2010 3:19 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: REXX that verify what MINIDISK is a file
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on
X acessed minidisk.
So, try with STATE command without succesfull and now
@LISTSERV.UARK.EDU
Subject: REXX that verify what MINIDISK is a file
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on X
acessed minidisk.
So, try with STATE command without succesfull and now try with LISTFILE
command.
If execute like this :
9
Parse Source . . x1 x2 x3 .
If x3 'X' Then Do
Say 'You are not executing from the X disk!'
Exit 99
End
Scott Rohling
On Thu, Oct 14, 2010 at 1:19 PM, Sergio Lima sergiovm...@hotmail.comwrote:
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on X
/2010 03:20 PM
Subject:REXX that verify what MINIDISK is a file
Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on X
acessed minidisk.
So, try with STATE command without succesfull and now
Oops -- need to only look at the first letter of the filemode:
Parse Source . . x1 x2 x3 .
If left(x3,1) 'X' Then Do
Say 'You are not executing from the X disk!'
Exit 99
End
Scott Rohling
On Thu, Oct 14, 2010 at 1:34 PM, Scott Rohling scott.rohl...@gmail.comwrote:
Parse Source . . x1
to
The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
REXX that verify what MINIDISK is a file
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on X
acessed minidisk.
So, try with STATE command without succesfull
Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Scott Rohling
Sent: Thursday, October 14, 2010 2:34 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: REXX that verify what MINIDISK is a file
Parse Source . . x1 x2 x3 .
If x3 'X' Then Do
Say 'You are not executing from the X disk!'
Exit
: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Sergio Lima
Sent: Thursday, October 14, 2010 3:19 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: REXX that verify what MINIDISK is a file
Hello List,
We are changing a REXX here for that this EXEC execute only if reside on
X
Hello,
Excellent idea, we consider this as well,
Thanks
Sergio
Date: Thu, 14 Oct 2010 15:34:19 -0400
From: brene...@us.ibm.com
Subject: Re: REXX that verify what MINIDISK is a file
To: IBMVM@LISTSERV.UARK.EDU
You might consider using MAKEBUF and DROPBUF around your code. You
. CATAA CMS
11 *-* If x3 'X'
1
*-* Then
Any mistake here ?
Sergio
--
Date: Thu, 14 Oct 2010 13:34:28 -0600
From: scott.rohl...@gmail.com
Subject: Re: REXX that verify what MINIDISK is a file
To: IBMVM@LISTSERV.UARK.EDU
Parse
, and now, the people here, want
have a little control about what was compiled, and others thinks.
Thanks again, and Best Regards,
Sergio
Date: Thu, 14 Oct 2010 15:03:36 -0500
From: mike.wal...@hewitt.com
Subject: Re: REXX that verify what MINIDISK is a file
To: IBMVM@LISTSERV.UARK.EDU
Hello Jim,
Tested, run very well,
Thanks very much, and Best Regards,
Sergio
Date: Thu, 14 Oct 2010 16:05:42 -0400
From: jim.hug...@doit.nh.gov
Subject: Re: REXX that verify what MINIDISK is a file
To: IBMVM@LISTSERV.UARK.EDU
A better method would be to verify the EXEC
,
Thanks,
Sergio
--
Date: Thu, 14 Oct 2010 14:48:09 -0600
From: scott.rohl...@gmail.com
Subject: Re: REXX that verify what MINIDISK is a file
To: IBMVM@LISTSERV.UARK.EDU
Yes - I corrected this in another post - you only want the first character
of the filemode
: REXX that verify what MINIDISK is a file
Scott,
Sorry about disturb, but still don't run, look please :
The code :
trace r
'LISTFILE cataa exec * (DATE STACK LIFO'
Parse Source . . x1 x2 x3 .
If left(x3,1) 'X' Then Do
Say 'You are not executing from the X disk!'
Exit 99
into CP QUERY MDISK to verify that the disk accessed as X is MAINT 31A.
-Mike
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Sergio Lima
Sent: Thursday, October 14, 2010 5:17 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: REXX that verify what MINIDISK is a file
System IBMVM@LISTSERV.UARK.EDU
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: REXX that verify what MINIDISK is a file
Hello Mike,
Thanks very much from your good explanation.
We need that the user execute our EXEC from a public dasd (Maint 31a),
because, We try track who executed
5:17 PM
*To:* IBMVM@LISTSERV.UARK.EDU
*Subject:* Re: REXX that verify what MINIDISK is a file
Hello Mike,
Thanks very much from your good explanation.
We need that the user execute our EXEC from a public dasd (Maint 31a),
because, We try track who executed this, the date, the time
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: REXX that verify what MINIDISK is a file
Scott,
Sorry about disturb, but still don't run, look please :
The code :
trace r
'LISTFILE cataa exec * (DATE STACK LIFO
31A.
-Mike
*From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On
Behalf Of *Sergio Lima
*Sent:* Thursday, October 14, 2010 5:17 PM
*To:* IBMVM@LISTSERV.UARK.EDU
*Subject:* Re: REXX that verify what MINIDISK is a file
Hello Mike,
Thanks very much from your good
34 matches
Mail list logo
