The SASSHIS5 report includes new parameter options. A selection of literal date ranges is added to the existing date options. These literal date ranges enable easier history management.
Each date range literal indicates both a beginning date and an ending date for history records that are moving to archives. The ending date is used in the same way that the current YYDDD specified date is used. All records that are dated up to and including the ending date are moved to archives. The beginning date is used as a check to allow for a notification when records outside of the date range are moved into archives. If the history file contains only records that all fit within the literal date range, all records are moved to archives. If some records are dated before the beginning date, the check fails. A message is printed in the output report listing the earliest date found in the history file. The job ends with return code 4. This condition still moves records to archives.
For example, a job could be scheduled to run at the beginning of each month, using the literal date range LMNTH. This job moves all records from the previous calendar month to archives and creates another generation of the history file. This new generation contains only log records from the current month. The previous generation contains only records from the previous month. With the history generations aligned month to month in this way, locating required log records is accomplished easily.
Note: For more information about literals for date range record archival control and their meanings, see the Systems Programming Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|