The client uses eJES with is an SDSF replacement. In eJES, the ST command is used to view your output. The command /ST also starts a SECTRACE. How is the SECTRACE protected with ACF2 from being started by mistake?
Release : 16.0
Component : CA ACF2 for z/OS
In the Protect Operator Commands section of the ACF2 manual, there is a section on protecting the SECTRACE commands.
Command/Keyword
|
SERVICE
|
Resource Name
|
SECTRACE DELETE
|
UPDATE
|
TRCE.SECTRACE.DELETE
|
SECTRACE DISABLE
|
UPDATE
|
TRCE.SECTRACE.DISABLE
|
SECTRACE DISPLAY
|
READ
|
TRCE.SECTRACE.DISPLAY
|
SECTRACE LOGERR
|
UPDATE
|
TRCE.SECTRACE.LOGERR
|
SECTRACE MODIFY
|
UPDATE
|
TRCE.SECTRACE.MODIFIED
|
SECTRACE NOLOGERR
|
UPDATE
|
TRCE.SECTRACE.NOLOGERR
|
SECTRACE SET
|
UPDATE
|
TRCE.SECTRACE.SET
|