ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

TSS9405E ignored by TSSSIM

book

Article ID: 226160

calendar_today

Updated On:

Products

Top Secret

Issue/Introduction

  A  DB2 WLM stored procedure  calls TSSSIM. Despite receiving the following message the simulation runs successfully:

12.30.39 STC25748  TSS9405E NO AUTHORITY FOR INTERNAL SECURITY FUNCTION (? )

 TSSUTIL Report shows:
15.09.21  12:30:39  ODVB  SCA#SIM   DD1GWRMX  DB2DIST   FAIL  01  DSNX9WLS                     *04*-1F  PGM  S025748

 1F = NO AUTHORITY FOR INTERNAL SECURITY FUNCTION (  )

Error message explanation:
TSS9405E
NO AUTHORITY FOR INTERNAL SECURITY FUNCTION ( )
Reason: A RACROUTE request requiring APF authorization was issued in a non-APR state.

The libraries in the STEPLIB concatenation do not have APF authority.
This is intended because the
 WLM procedure needs to have a non-APF Library in the Steplib concatenation; otherwise, the REXX call in the procedure fails with RC(-3).  

Why is the TSSSIM call successful even though the TSS9405E error message is issued?
Which request is causing the TSS9405E error (the function in the message is '?') .

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

TSSSIM tries to determine if you are authorized to run the utility. First it tries to check if the user (SCA#SIM) has MISC1 administrative authority.
It does this through a RACROUTE REQUEST=AUTH call for an internal class identified by the ?.  Since the process is not APF authorized, the RACROUTE call is failed with an error code of x'1F'. This results in the records you see in the TSSUTIL report.  If TSSSIM can not determine if the user has MISC1 authority for TSSSIM, it then checks if the user is authorized for CASECAUT resource TSSUTILITY.TSSSIM.  Since the user SCA#SIM has a permit for the resource, TSSSIM will continue processing. 

Test fix LT03421 will eliminate the TSS 9405E messages.
Contact Support to receive the fix.