--------------------------<snip>-------------------
Following extracted from the CICS/TS RACF Security Guide:
"2.7.6.2 Checking which transactions to offer a user
You can use the QUERY SECURITY command to check whether a user is
authorized to use a particular transaction before displaying the
transaction code as part of an introductory menu. When you use the
command for this purpose, you will probably want to avoid logging the
checks for users who are not allowed to use certain transactions. To do
this, use the NOLOG option."
...and the QUERY SECURITY command invokes a RACROUTE to perform this
function. So CICS is documenting use of preemptive RACROUTE requests as
reasonable design in presenting usable options on a user's menu.
--------------------------<unsnip>-------------------
IIRC, under this particular set of circumstances, RACROUTE will do the
equivalent of a FRACHECK, which does no logging. Has to do with the
resource definitions for CICS transactions.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
