![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
On an ongoing basis, the data in the audit log must be archived to an external file and deleted from the TIBCO Object Service Broker table. For security reasons, the only way to archive the data is to use either:
• PURGELOG_SCREEN, which is an interactive tool
• PURGELOG_BATCH, which is a batch toolTo run the PURGELOG tools, adequate security must be defined for TIBCO Object Service Broker to allow you to run the PURGELOG tools and/or specify the external file that is used to store the archive data. Refer to Task A, Enter the name of the file where the audit data is to be stored for information about the purge file.You must edit your secparm file, which is in the same directory as the crparm file, to specify the list of user IDs that are allowed to run these routines.
For users connecting to TIBCO Object Service Broker through an ostty session, specify the operating system user ID, not the TIBCO Object Service Broker user ID. It can be as long as 251 characters, but only the first 8 characters are used.For a user connecting through theTIBCO Object Service Broker UI or the SDK (Java), specify “CLI”. A logical value (Y/y or N/n) indicating whether the userid is allowed to specify the archive file for the audit log A logical value (Y/y or N/n) indicating whether the userid is allowed to purge the audit log
If userid is “3270” or “CLI”, any user of the specified session type can archive the audit log.
TIBCO Object Service Broker for z/OS Installing and Operating or TIBCO Object Service Broker for Open Systems Installing and Operating for details about the crparm file.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |