Which userid did CICS supply for the authorization check?

Check to see if the user reporting the problem has signed on to CICS.

If the user has not signed on to CICS, one of the following could be occurring:
  • If you are using preset-terminal security, the authorization could be related to that terminal's userid.
  • The user could be trying to operate as the CICS default user (without signing on to CICS).
  • If the transaction was initiated by a START command, the userid could be inherited from the transaction issuing the START, or specified on the START command itself.
  • If the transaction was initiated as the trigger transaction associated with a transient data queue, the userid could have been specified in the transient data destination definition for the queue.
  • If the program is running as a PLTPI program, the userid could be specified in the PLTPIUSR system initialization parameter.
Note: RACF message ICH408I identifies the userid, as supplied by CICS to RACF, for which the authorization failed.

For help in identifying the user, see CICS users.



dfht5b00108.html | Timestamp icon Last updated: Monday, 5 June 2017