LIB/TSO Interface › LIBAUDIT Processing and LIB/TSO

LIBAUDIT Processing and LIB/TSO

The CA Librarian Auditing facility (LIBAUDIT) provides the following benefits:

• For archived modules, LIBAUDIT conserves master file space by retaining only the changed records of an updated module in the module instead of generating a complete copy of the module as a separate level.
• For non-archived modules, LIBAUDIT marks the changed records generated during an update with date stamps. Thus, updates can be identified through the date stamps.
• For LIB/TSO, LIBAUDIT notes the changes that were applied through a LIBGET/LIBSAVE sequence or the LIBEXP command. It then issues the appropriate CA Librarian control statements (-INS, -DEL, and -REP) to update the changed records only.

You can suppress LIB/TSO LIBAUDIT processing for individual command executions by specifying the NOAUDIT operand on the LIBSAVE or LIBEXP commands. NOAUDIT causes LIB/TSO to issue a -REP ALL,NOAUDIT control statement.

Note:

• The advantages of LIBAUDIT can be lost through careless handling of sequence numbers. If you change the location of your sequence numbers, LIBAUDIT views the records as updated, even if no other changes are made. This problem can be especially acute if editing COBOL data sets. Take great care to ensure that sequence numbers remain in the same location when modules are retrieved from or returned to the master file. In addition, avoid using ISPF AUTONUM if LIBAUDIT is in effect.
• Without LIBAUDIT, CA Librarian generates an entire copy of the module for every archiving level and CA Librarian does not date stamp the changed records of non-archived modules.