Thank you. Sounds very promising.
Jon
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag
von John Eells
Gesendet: Donnerstag, 26. April 2007 22:40
An: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: AW: Renaming ADRDSSU
Jon Renton wrote:
> We want to
-Mensagem original-
De: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Em nome
de Jon Renton
Enviada em: quinta-feira, 26 de abril de 2007 16:07
Para: IBM-MAIN@BAMA.UA.EDU
Assunto: AW: Renaming ADRDSSU
We want to use the DFDSS user exit. In order to so the ADRDSSU call must
be changed
: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: Renaming ADRDSSU
- Original Message -
From: "Jon Renton" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
Sent: Thursday, April 26, 2007 12:07 PM
Subject: Renaming ADRDSSU
> Hello,
>
> we are experimenting with getting con
Surely you're not serious! Is "getting control" an intent to prevent some
users from using ADRDSSU?
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Jon Renton
Sent: Thursday, April 26, 2007 11:07 AM
To: IBM-MAIN@BAMA.UA.EDU
Su
internal methods.
Regards
Jon
On Thu, 26 Apr 2007 18:07:02 +0200, Jon Renton wrote:
>Hello,
>
>we are experimenting with getting control of all ADRDSSU calls (the IBM DSS
>user interface). To achieve this, we are thinking about renaming ADRDSSU
and
>supplying our own ADRDSSU
Hello,
we are experimenting with getting control of all ADRDSSU calls (the IBM DSS
user interface). To achieve this, we are thinking about renaming ADRDSSU and
supplying our own ADRDSSU frontend which will later call the real IBM
module.
Now my question - has anyone ever renamed modul ADRDSSU? Do
Gil,
I agree - my aim is not to restrict access to data - just log the use!
Regards
Jon
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag
von Paul Gilmartin
Gesendet: Montag, 29. Januar 2007 22:55
An: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: Getti
onents. If required via a subsystem or IMHO I think this is the
cleanest architectural way to solve the problem. Unfortunately the technical
solution does not seem to be that straight forward - shame!
I am wondering how products like Softaudit and PDSMan solved the problem?
Regards
Jon Rent
Circumnavigation could be a problem - especially in areas such as SOX
compliance. Certain actions must be logged without exception. This is where
I need to go! That means calls from JCL, Programs, REXX, Clists, ...
must all be captured. One risk can of course never be fully controlled - a
highl
pack or steplibs, but that sounds overly-complicated to me.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Jon Renton
Sent: Monday, January 29, 2007 6:40 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: AW: Getting control
John,
a "relink&qu
ssion List [mailto:[EMAIL PROTECTED] Im Auftrag
von McKown, John
Gesendet: Montag, 29. Januar 2007 15:21
An: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: Getting control
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Jon Renton
> Sent: Mond
Hello,
I am looking for a way to prevent users calling certain load modules
directly. Instead I would like my module to get control. This module can
then perform certain tasks before passing control to the user requested
processing module.
Here as a simple flow:
- User calls module "A"
- My m
Hello,
I am getting the follwoing abend:
IEC212I
414-08,IGG0201B,DBM05310,DFDSS,XRSDLOG,687C,SYSS45,SSUXRSP.XRS999.XRSLOG01
The IBM documentation is not very descriptive. Can anyone help me to
understand/solve the problem?
TIA
Regards
Jon
Hello,
I am getting the follwoing abend:
IEC212I
414-08,IGG0201B,DBM05310,DFDSS,XRSDLOG,687C,SYSS45,SSUXRSP.XRS999.XRSLOG01
The IBM documentation is not very descriptive. Can anyone help me to
understand/solve the problem?
TIA
Regards
Jon
--
No virus found in this outgoing message.
Checked
Many thanks to all of you for the suggestions.
I shall have to assess the various aspects and decide on how to continue.
The only solution that is not acceptable is the "open" method.
Jon
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag
John,
basically the calling programs process various generic dataset templates.
Dataset lists are built and the contents need to be checked against RACF
using certain given userids. The subroutine is called per dataset with the
required user. Upon return the rc, status and access (read, update, al
; [mailto:[EMAIL PROTECTED] On Behalf Of Paul Gilmartin
> Sent: Tuesday, June 14, 2005 3:03 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Re: Calling authorised modules from non-authorised
> environments
>
>
> In a recent note, Jon Renton said:
>
> > Date: Tue,
Juni 2005 21:44
An: IBM-MAIN@BAMA.UA.EDU
Betreff: Re: Calling authorised modules from non-authorised environments
In a recent note, Jon Renton said:
> Date: Tue, 14 Jun 2005 21:02:38 +0200
>
> Now my routine needs to be called from programs not running under TSO.
> The problem
Hello,
I have an assembler routine that checks the authorisation for given datasets
for specific users (using SAF/RACF). Not only the callers authorisation may
be checked but that of any given userid. I need to be authorised in order to
perform the authorisation check for other users.
Up to now
I have now also seen, that CA-MIM uses a VSAM dataset to coordinate
resources across multiple Sysplexes.
Jon
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag
von Ted MacNEIL
Gesendet: Montag, 23. Mai 2005 02:00
An: IBM-MAIN@BAMA.UA.EDU
Bet
Are there still situations where GRS is missing functionality contained
within CA-MIM?
At one time (if I am not mistaken) GRS was not able to coordinate resources
across multiple Sysplexes, where as CA-MIM could.
Jon
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List [mailto
I was hoping to use base MVS services / control blocks to find the
information rather than relying on USS commands!
Jon
-Ursprüngliche Nachricht-
Von: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Im Auftrag
von Big Iron
Gesendet: Mittwoch, 18. Mai 2005 12:27
An: IBM-MAIN@BAMA.U
22 matches
Mail list logo