View previous topic :: View next topic
|
Author |
Message |
maxsubrat
Active User
Joined: 27 Feb 2008 Posts: 110 Location: india
|
|
|
|
I have a requirement to restrict few users to edit any field in the Map.
For ex: suppose Ram is the user and city type as Mumbai, I want to stop this user to edit any field from the map.
I have a main program which has many activities on it and also all the users can able to read and edit the MAP in all the fields.
My requirement is to stop the user to edit any field whose name is Ram from Mumbai without affecting other users.
Here I just want to know how to stop that user to edit the entire map or put entire map to Ram as read only.
Thanks in advance. |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
For each named field in the map you have an attribute character.
After receiving the map for the 1st time, you check the user and the city.
Depending on the values entered, you set the other fields attributes to protected or non-protected, then send the map. |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3048 Location: NYC,USA
|
|
Back to top |
|
|
maxsubrat
Active User
Joined: 27 Feb 2008 Posts: 110 Location: india
|
|
|
|
You are saying to check all the fields one by one and put it as protected.
Instead of that I just want to protect all the fields in one go...
Is there any way to set like this? |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3048 Location: NYC,USA
|
|
|
|
Yes, as soon as you get Ram as a user and City is Mumbai then use PROT attribute from the above copybook for all the Attribute fields which are editable and then send that map, are you not asking for this? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Each field on a CICS 3270 screen is defined separately. If you allow fields to be individually editable, then there is no way that you can protect every field -- unless you move the protect attribute to each and every field attribute. If you have 97 fields on the screen you want to protect, you can use 97 MOVE statements (assuming you are using COBOL) or you can use 1 MOVE statement with 97 destination variables -- but any way you look at it, you've got to specify every field attribute you want protected. |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
Alternatively, the fields can be defined as protected by default.
Then if user is not Ram or if city is not Mumbai, you can UNPROT the fields.
Either way, there is no shortcut: each attribute of each field must be set. |
|
Back to top |
|
|
|