Copyright © Cloud Software Group, Inc. All Rights Reserved

PURGELOG_BATCH

Purges the audit log data from the TIBCO Object Service Broker audit log table and archives it to an external file. (CE)

Invocation

Do one of the following:

From the…	Move the cursor to the…	And…
Developer’s workbench	EX Execute Rule option	Type PURGELOG_BATCH <Enter>
	COMMAND prompt	Type EX PURGELOG_BATCH <Enter>
From a rule		Type CALL PURGELOG_BATCH (fromdate, todate, file)
From a batch file		Submit a batch file job that invokes the PURGELOG_BATCH tool.

Where:

 

fromdate	The start date of the range of audit log data to be purged (Specify in YYYYMMDD format, for example, 20000101.)
todate	The end date of the range of audit log data to be purged (Specify in YYYYMMDD format, for example, 20000131.)
file	The archive filename.

Prerequisites

Two external resource rules must be set up so that the user can specify the archive filename and purge the audit log.

See Also

TIBCO Object Service Broker Managing Security for more information on this tool.

Constraints

•	The Execution Environment must be in single user mode if used on z/OS.

•	The Data Object Broker must be authorized and be run using Cross Memory Services (XMS) if used on z/OS.

•	External security must be established.

•	Current (that is, today’s) audit logs cannot be purged.

Example

Assume an installation is externally secured using ACF2. An authorized user would define two resource rules, for example, ABCS6B.SPECFILE and ABC2S6B.PURGELOG. For each of these resource files, a list of user IDs who can perform the file specification and the purging of the audit log is created.

According to whatever schedule is appropriate to that site, a JCL job that does a SCHEDULE PURGELOG_BATCH is submitted by users authorized through the resource rules.

Copyright © Cloud Software Group, Inc. All Rights Reserved