CA7 Log, History and Archive Data Set Management

Document ID : KB000024715
Last Modified Date : 14/02/2018
Show Technical Document Details


CA 7 logs various records that can be used in history reporting and for problem determination. The SASSHIS5 and SASSHIS6 utility programs are used to maintain the log, history and archive data. 


CA 7 writes many different log records to the CA 7 log files. Primary and secondary logs are defined in the CA 7 Initialization File (pointed to by the UCC7IN DD statement in the CA 7 online procedure) with the ALOG1 and ALOG2 statements. The CA 7 DBASE statement in the Initialization File JOB= keyword names a 7 character log dump job that will be automatically submitted by CA 7 when the log fills. A P or an S is appended to the 7 character job name to denote the primary (P) or secondary (S) file to be dumped. The default job names are CA07LOGP and CA07LOGS. These jobs execute program SASSHIS5 which writes the log records to a history file. The SASSHIS5 program can also be used to remove log records from the log history file and place them on the CA 7 log archives file so the log history file does not become too large. This transfer can occur either while the log records are being extracted from the log files or as a separate operation by making the DD for the log files a DD DUMMY and using the PARM operand on the EXEC statement. If you want to archive records from the history file as a separate operation, you would need to have a job (other than the CA07LOGP or CA07LOGS) set up to do so because the log dump jobs cannot be DEMANDed into CA 7 (they only automatically come into the queues when a log fills or you do the /SWAP command in CA 7). The PARM operand on the EXEC statement for the SASSHIS5 program has the following format:


where yyddd defines a Julian date specifying the ending date of the period to be placed onto the CA 7 log archives file. Five blanks cause no records to be archived. The value TODAY may be used to specify the current date. This parameter has no default. The nnnnnn defines a six-digit number, with leading zeros, representing the amount of memory available to the internal sort--it must be six blanks if not used. The maximum available memory is the default. When the SASSHIS5 program runs, a History Management report is written to the CNTLREPT DD. This report reflects the status of logged history or archive data which is stored as internal control data in the first record of the history file and gives information showing when the history data was written to the history file and when/if it was archived. The SASSHIS6 program is used to manage the size of the history and/or archive files. SASSHIS6 deletes unwanted CA 7 log records from the log history and log archives files while keeping the internal control data between the files synchronized. SASSHIS6 should run whenever the older CA 7 log records are no longer needed for analysis. These records are permanently deleted from the system and thereby prevent the log files from becoming too large. SASSHIS6 has a required PARM operand on the EXEC statement of PURGE= which identifies the from and through dates defining the period (or range) of records to be purged.

Additional Information:

See the CA 7 Systems Programmer Guide, topic SASSHIS6 for the various purge parameters. You can DEMAND or schedule the execution of the SASSHIS6 program.

Also see Technical Document TEC433609 for more information on the log dump process.

As always, please contact CA Technologies support for CA 7 if you have further questions.