This section covers the following topics:
Every time reports are archived to a tape, a data set is created on the tape volume containing all the archived reports. This is called an archive data set.
For each archive data set, an entry is made on the Entire Output Management archive catalog, which contains control information regarding each archive process. This information includes the date and time of the operation, the volser(s) on which the archive data set has been catalogued, and an indication of whether the data set still contains reports which must remain on archive.
When the reports contained in an archive data set are no longer required, a message is displayed to the right of the data set indicating that the volsers can be reused for other purposes.
For further information about archiving, see Automatic Archiving Defaults and Archiving Task.
To display the list of data sets which have been archived:
Enter 9 in the command line of the
Main Menu.
The Archive Data Sets screen is displayed:
17:31:17 **** ENTIRE OUTPUT MANAGEMENT **** 2015-04-30
User ID XYZ - Archive Data sets -
Cmd Data set NVol NumRp Created Msg
___ ______________________________ ___ ______ ______________ _________________
__ NOM.ARC221.NOM0402 1 1 03-03-03 09:00
__ NOM.ARC221.NOM0401 1 02-12-23 09:00 can be deleted
__ NOM.ARC221.NOM0400 1 02-12-18 14:17 can be deleted
__ NOM.ARC221.NOM0399 1 02-12-18 13:39 can be deleted
__ NOM.COND221.NOM0398 1 02-11-11 11:05 can be deleted
__ NOM.ARC221.NOM0397 1 02-11-11 09:00 can be deleted
__ NOM.ARC221.NOM0396 1 02-11-08 10:19 can be deleted
__ NOM.ARC221.NOM0393 1 02-11-05 11:05 can be deleted
__ UKSJU.NOMUDA.NOM0392 1 11 02-11-01 16:10
__ RDU.SJU.NOMUDA3.NOM0391 1 02-11-01 16:10 can be deleted
__ NOM.ARC221.NOM0390 1 02-11-01 16:10 can be deleted
__ NOM.ARC221.NOM0389 1 02-11-01 09:00 can be deleted
__ RDU.SJU.NOMUDA3.NOM0388 1 02-10-31 09:00 can be deleted
__ RDU.SJU.NOMUDA3.NOM0387 1 02-10-30 09:00 can be deleted
__ NOM.ARC221.NOM0386 1 02-10-02 09:00 can be deleted
Top Of Data
Command => ___________________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip - + < > Menu
|
The data sets are listed in alphabetical order.
The information displayed is spread over four screens. By repeatedly pressing PF11, you can display the information on the subsequent screens.
| Field | Explanation |
|---|---|
| First Screen: | |
| Dataset | The archived data set name. |
| NVol | The number of tape volumes the data set occupies. |
| NumRp | The number of archived reports contained on the data set. |
| Created | The date and time the data set was created. |
| Msg | When all reports archived on the data set are no longer required and have been purged, the message "Delete" is displayed, advising you that the data set can be uncataloged and the volsers reused. |
| Second Screen: | |
| LogExpD |
Logical Expiration Date. This is the date until which the data set is to be kept. This can differ from the Physical Expiration Date (see below), if the expiration date of one or more active reports is extended or shortened after archiving. If the Logical Expiration Date is later than the Physical Expiration Date, the line with the archive data set is highlighted. Run a condense to synchronize the two dates. |
| PhysExpD | Physical Expiration Date. This is the date until which the tape is to be kept and corresponds to the date supplied on the tape with the EXPDT parameter. |
| Third Screen: | |
| # Expired | The number of expired reports. This is calculated by subtracting the number of reports still active on this data set from the number of reports originally archived. This number will not be displayed for old archive data sets. |
| Cdns | This shows whether this archive is output from a condense or not. |
| Fourth Screen: | |
| Arc Type | Displays the archive type name, standard or user-defined. |
| Num | Internally allocated number for archive type. |
To condense an archive data set:
To mark an archive data set for condensing, enter the line command
CD on the Archive Data Sets
screen next to the data set(s) to be condensed.
The message "condense" is displayed in the Msg column of theArchive Data Sets screen.
To start the condense task, enter the direct command
START CONDENSE in the command line of any screen, or
select option 9 on the System Administration menu (see
Condense
Task).
Note:
The job skeleton used for condensing has to be saved in library
SYSNOMU and must be named JCDNSKEL.
This function renames the selected archive data set and updates all active reports contained on it so that they point to the new data set. Summary information on the results of this function is written to the monitor log.
To rename an archive data set:
On the Archive Data Sets screen, enter the line
command RN next to the data set you want to
rename.
The Rename Archive Data Set screen is displayed. It contains the following fields:
| Field | Explanation |
|---|---|
| From data set name | The old name of the data set. |
| To data set name | Specify the new name of the data set. |
| Log modifications of reports |
This field determines whether or not messages about changed reports of archive data set are written to the monitor log:
|
| Adabas calls between screen writes | The number of records to be updated between screen writes. The default value is 1000. |
| Adabas updates between End Transactions | The number of records to be updated between End-of-Transaction commands. The default value is 30. |
Enter the new data set name, and press PF5 to perform the update.
An archive data set can only be deleted when it contains no reports.
To delete an archive data set:
On the Archive Data Sets screen, enter the line
command DE next to the data set you want to
delete.
A window will be displayed in which you enter
DELETE to confirm the deletion, and in which you
also specify whether or not the data set is to be uncatalogued.
To list the VOLSERs spanned by an archive data set:
On the Archive Data Sets screen, enter the line
command VO next to the appropriate data set.
A list of the VOLSERs is displayed.
This function is used to change the VOLSER of an archive data set in and updates all active reports contained on it so that they point to the new VOLSER:
This function can only be used for single-volume data sets. For multi-volume data sets, you condense the archive data set to a new one; this which will also update the VOLSERs.
To modify the VOLSER of an archive data set:
On the Archive Data Sets screen, enter the line
command MV next to the desired data set.
A screen containing the following fields is displayed:
| Field | Explanation |
|---|---|
| Archive data set | The name of the data set whose VOLSER is to be modified. |
| Current VOLSER | The current VOLSER of the data set. |
| To volser | Here you specify the new VOLSER. |
| Log modifications of Reports |
This field determines whether or not messages about changed reports of archive data set are written to the monitor log:
|
| Adabas calls between screen writes | The number of records to be updated between screen writes. The default value is 1000. |
| Adabas calls between End Transactions | The number of records to be updated between End-of-Transaction commands. The default value is 30. |
Enter the new VOLSER, and press PF5.
To list the reports contained in an archive data set:
On the Archive Data Sets screen, enter the line
command RP next to the appropriate data set.
The Reports in Archive Data Set screen is diplayed.
The names of the reports deleted from active reports are marked with an asterisk (*).
With PF9 (Ext), you can toggle to short names display.
The screen contains the following information on each report:
|
Field
|
Explanation |
|---|---|
| Report | The name of the report archived. |
| Run-No | Unique number identifying the report. |
| ExpDate | Expiration date until which the report is to be kept. |
| OrigExp | Original expiration date until which the report was to be kept (if the original value of ExpDate has been modified or deleted). |
| Status | Report status. |
To modify the expiration data of a report in an archive data
set:
On the Reports in Archive Data Set screen,
enter the line command MO in the command line next
to the report in the data set you want to modify.
A window containing the following fields is displayed:
| Field | Explanation |
|---|---|
| Report | The report name. |
| Expiration Date | The current expiration date. This can differ from the original expiration date. |
| OrigExp Date | This is the first valid expiration date. If the original date has already been modified, the original date appears here and the current expiration date appears in the Expiration Date field. |
| New Expiration Date | Enter the new expiration date here. |
Enter a new value in the field New Expiration Date.
To reset the expiration date of a report in an archive data set:
On the Reports in Archive Data Set screen,
enter the line command RS in the command line next
to the data set to be reset.
The expiration date of the report is reset to the original expiration date.
To mark a report in an archive data set for deletion:
On the Reports in Archive Data Set screen,
enter the line command DE in the command line next
to the report to be deleted.
A "D" is displayed in the Status column of the report, and the report's expiration date (ExpDate) changes to the current date. Reports marked with "D" are automatically deleted on the following day.
If an archived report was deleted from active reports manually, but not deleted from the archive, the report is marked with a "D" on the Reports in Archive Data Set screen. Reports marked with "D" are automatically deleted on the following day.
To revive an archived report deleted from active reports:
Reset the report's expiration date with the line command
RS as described above.
On the Reports in Archive Data Set screen,
enter the line command RV in the command line
preceding the report name.
A window is displayed, in which you specify where the report is to be revived to:
the spool,
the Entire Output Management database,
Con-nect.
The report is marked accordingly for the next scheduled reviving (see Reviving Task).
In addition, you can specify the name of a bundle: when the report is revived, it is added to an open active bundle of that name. If there is no such open active bundle, one will be created from the bundle of the same name.