Top Secret what needs to be done to correct the XACTION errors
search cancel

Top Secret what needs to be done to correct the XACTION errors

book

Article ID: 137202

calendar_today

Updated On:

Products

Top Secret

Issue/Introduction

Testing some new software on  a sandbox LPAR. getting *08*-88 LCF XACTION  Top Secret errors

 

Environment

Release : 16.0

Component : CA Top Secret for z/OS

Resolution

XACTION relates to LCF's (Limited Command Facility).

 

 There are 2 ways to define transactions to Top-Secret

 1. You can use OTRAN....

 2. You can use LCF.


TSS MODI FAC(CICSfacilityname) and check the attributes for XDEF or NOXDEF.

 XDEF turns on LCF protection by default, so if the transaction is not

 owned as an OTRAN, there will be an LCF check done. If the user doesn't

 have access to the LCF, a violation occurs.

 

 If your not using LCF security recommend set NOXDEF on the facility.

  

 OTRAN overrides LCFs. If the transaction is owned as an OTRAN, there

 will not be an LCF check: Either the user is allowed access to the OTRAN

 or not. With NOXDEF you should get a OTRAN violation not XACTION.