> I've found that GIMSMP opens the datasets in UPDATE mode, so the user will
> still need UPDATE or higher access. READ access fails when the program
> starts.
That is not true for all SMP/E commands. LIST for example, or the REPORT
commands, and the ISPF Query dialog, definitely open the
That's disappointing. It's not being done now, but another good way to handle
that problem is to enhance the GIM.* Facility class profiles to include zone
support for commands. User can run certain zone altering SMP/e commands against
TZONE1, but not TZONE2. Something like that.
Mark Jacobs
I've found that GIMSMP opens the datasets in UPDATE mode, so the user will
still need UPDATE or higher access. READ access fails when the program starts.
I've growled that GIMSMP needs to open in READ mode, then close/open in the
desired UPDATE mode if needed.
Matthew
On Mon, 27 Mar 2023
If you have those zones in their own CSI datasets, you can use your security
system just to allow READ access.
Mark Jacobs
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
--- Original Message
Why not give them read-only access?
From: IBM Mainframe Discussion List on behalf of
Bill Giannelli
Sent: Monday, March 27, 2023 9:46 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMPe securing zones
I want to create another TARGET and DLIB zone for another
I want to create another TARGET and DLIB zone for another level of maintenance.
I am currently, showing "newbie" offshore folks our SMPe environment.
Is there a way to "secure" the newly created TARGET and DLIB zones so they are
not inadvertently updated?
thanks
Bill
