Joined: 17 Dec 2007 Posts: 55 Location: Victoria, BC, Canada
I am a bit curious why you are listed as a "New User" on this list, having been resident here for more than 9 years.
An IMS DC "screen" is typically produced by an underlying IMS transaction code. It is the transaction code and associated PSB and program load modules, using database PCBs coded in the PSB that access IMS database segments and DB2 tables to produce the IMS DC "screen" output.
So you really want to protect the IMS transaction code.
Assuming your shop uses RACF for security, you will need to know what resource (transaction code) to define in what RACF Class to protect the transaction. Then you permit READ authority in RACF for the resource(transaction) in the RACF Class to give specific users the access they need to the transaction. READ is all that is needed, even if the transaction performs database updates.
How do you determine the RACF class?
You examine the startup messages from your IMS control region until you find this message:
DFS1929I * RCLASS = iprod
Whatever you see in the message where "iprod" is shown in the above message is your IMS RCLASS.
You concatenate a "T" in front of the RCLASS to obtain the RACF CLASS that protects transactions on this IMS region.
In my example, the RACF CLASS is "tiprod".
Once your RACF administrator has defined the transactions to RACF and permitted access to users, she will have to perform a refresh in RACF to activate the definitions, using the SETROPTS command, specifying the RACF CLASS.
Maida Snapper has written a number of presentations on this topic.
Here is one.