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 13:50:28 +0000, Mark Jacobs <markjac...@protonmail.com> 
wrote:

>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&search=markjac...@protonmail.com
>
>
>------- Original Message -------
>On Monday, March 27th, 2023 at 9:46 AM, Bill Giannelli 
><billgianne...@gmail.com> wrote:
>
>
>> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to