XOS: Audit File Error 45 - Missing Sequence Numbers

XOS: Audit File Error 45 - Missing Sequence Numbers

If a disk file name is specified for the AUDIT and no disk file exists, the file is created with the default format of type E, rec 4000, block 4096, primary extent size 300 pages, secondary extent size 300 pages and maxextents set to 16.
 
When an audit file fills up, XOS will receive an error 45 when it attempts to write to it. At that point, the current file will be renamed using the first three characters of the current file?s name followed by a five digit sequence number. A new file will be created with the original name and format and processing will continue. The numbered audit files will continue to increment each time the audit file fills up and is rolled over.
The below example will send XOS audits to the file called XOSAUDIT in the subvolume $SECURE.XOSAUDIT.

It is not unusual to be missing sequential file numbers with the XOS product, since there are multiple processes writing to that audit trail. Two processes could both get error 45, and each performs a roll.
 
File AUD00000
Process 1: gets error 45
Process 2: gets error 45
Process 1: renames to AUD00001
Process 2: renames the file it has open, which the previous step renamed to AUD0001, TO AUD00002
Result:
AUD00000
<missing AUD00001>
AUD00002
 
Fixed in XAC 5.90 and XOS 2.50:
 
ITID 590-10655 Audit file naming scheme can switch from the default to the alternate/fallback naming scheme.
 
If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.




    • Related Articles

    • XAC: Error 580 opening audit file

      The maximum audit file size must be less than 4GB. Audit file sizes larger than 4GB create a File System Error 580 OPEN or FILE_OPEN error. If you are unable to locate the solution needed or need additional assistance please Click Here to open a case ...

    • How to resize XOS audit files

      TACL> VOLUME $<VOLUME>.<XYGATEOS INSTALLATION SUBVOLUME> TACL> RUN XOS INSTALL TACL> EDIT OSCONF Edit the line AUDIT <FILENAME> EXT(<PRIMARY>, <SECONDARY>, <MAX EXTENTS>) (size of an audit trail can be controlled with the EXT option) eg: TACL> AUDIT ...

    • XOS: Why am I seeing \UNKNOWN in the XOS Audit Report?

      Below are two possible reasons "\unknown" is seen in a XOS Audit Report for node name: A. When the EXPLICIT_NODES is OFF and you try to execute a FUP program on \one node to purge a file on another you see \UNKNOWN on the SUBJECT-SYSTEM field as ...

    • XOS: NORECORD IGNORED causing frequent audit rollover

      If you want to get rid of ?IGNORED?s, set the AUDIT-NORECORD keyword to OFF in the OSCONF. Additionally, depending on whether or not you want NORECORD audits for non-IGNORE entries, just setting AUDIT_NORECORD OFF wouldn't work. You would also need a ...

    • XOS: Disk that holds XOS audit is running out of space

      A. Create more disk space or change audit location in OSCONF to location with more space OR B. Decrease the extent size of the audit files (Modify OSCONF to set extents smaller) Steps to modify OSCONF and update configuration: 1. Set new parameters ...