eTrust CA-Top Secret Security for z/OS and OS ... - SupportConnect

Tracing UNIX System Services (OMVS)GID(value)—Specifies the UNIX System Services MVS GroupID for which youintend to collect security information. Acceptable numeric values range fromzero to 2,147,483,647. This field is not maskable.USER(acid)—Specifies the acid for which you want UNIX System Services MVSsecurity information collected. This field is not maskable.GROUP(acid)—Specifies the group for which you want UNIX System ServicesMVS security information collected. This field is not maskable.SERVICE(service)—Specifies the name of the SAF callable service for which youwant security information collected.TSSOERPT Output DescriptionTSSOERPT formats and reports security events occurring in the UNIX SystemServices environment. The output is extracted from the System ManagementFacility (SMF) data sets.The following is a sample of the output of TSSOERPT with DETAIL specified inthe job. TSSOERPT shows the logging of security events in an UNIX SystemServices MVS environment:02/02/98 98.033 11.54.44 — OMVS LOGGING REPORT — PAGE 1SERVICE USERID GROUP UID GID SAF RC RSNDATE TIME JOBNAME SOURCE SYSID CPUINIT_USP STRTE01 OMVSGRP 0 2 0 0 002/02/98 98.033 11:52:50 STRTE01 XE14 XE14Home : /U/STRTE01CHECK_ACCESS STRTE01 OMVSGRP 0 2 0 0 002/02/98 98.033 11:52:51 STRTE01 XE14 XE14Requested Access: SearchFunction: chdirUser Type: Security Defined Local UserPathname: /U/STRTE01Filename: /ROOTVolume : SMS001 Owner: rwx Group: --- Other: ---File Identifier: 000107000000000003Owning UID: 0 Owning GID: 0User Audit Options : Read Failure Write Failure Exec/Search FailureAuditor Audit Options: Read Failure Write Failure Exec/Search FailureDELETE_USP STRTE01 OMVSGRP 0 0 0 0 002/02/98 98.033 11:52:52 STRTE01 XE14 XE14This sample output shows one log entry for a INIT_USP request, one entry for aCHECK_ACCESS request, and one entry for a DELETE_USP request.In this example, the services of INIT_USP and DELETE_USP result in two-linelog entries consisting of field information. The CHECK_ACCESS request resultsin log entries that consist of two lines plus additional lines of information aboutthe request. This happens because different information is logged for differenttypes of requests.Implementing eTrust CA-Top Secret in a z/OS or OS/390 Environment 1–23