HOWTO - Configure Deliver to send sysouts to View for "DIRECT TO TAPE" archival
search cancel

HOWTO - Configure Deliver to send sysouts to View for "DIRECT TO TAPE" archival

book

Article ID: 281570

calendar_today

Updated On:

Products

OM View

Issue/Introduction

We have Deliver configured to PRE-SPOOL process ALL SYSOUT data on our system. We are already familiar with how to direct Deliver output over to View for DIRECT ARCHIVAL to the DISK layer of the View database.

Unfortunately, because of some very LARGE SYSOUTS that get created on our system, this direct to disk archival method sometimes causes our View database to temporarily fill up, until such time as the backup cycle is executed and the SYSOUT data gets moved from disk to tape. 

Instead, we would like to be able to direct LARGE SYSOUTS, that are PRE-SPOOL processed through Deliver, over to View for "DIRECT TO TAPE" archival rather than direct to DISK archival. 

Is this possible and if so, how would we have to configure things?

Environment

z/os, View, Deliver, direct, archive, archival, tape, 14.0, howto, configure, tapeclsl, parm, parameter, arch

Cause

Direct archival to disk causes the View database to fill up. Want to redirect the Deliver output to View for direct to TAPE archival functionality. 

Resolution

If you decide that you want to start sending large sysouts that are being PRE-SPOOL processed through Deliver over to View so that they can be archived DIRECT TO TAPE, you would need to make the following configuration changes:

- Establish a unique CLASS that you want to use for View DIRECT TO TAPE archival processing. (For our example, lets say CLASS=T).
- You will also need to know what your current SARINIT settings are for: CLSL, DEST and FORM. (For our example, lets say you have CLSL=X,DEST=DEST1,FORM=FORM1).

Configuration for View...

- Using you current View configuration of (CLSL=X, DEST=DEST1,FORM=FORM1), run a SARINIT to make the following modifications:
  a. ADD CLASS 'T' to your CLSL setting - (Example:  CLSL=XT).
  b. Set your TAPECLSL  parm to process class 'T' - (Example:  TAPECLSL=T).
  c. Recycle the View STC.

Configuration for Deliver...

- Decide which Deliver ARCNnn parameter you want to use to send the large sysouts out to the JES queue temporarily, so that they can then be picked up by View and archived DIRECT TO TAPE. (For our example, lets use ARCH10).

  a. Code your Deliver ARCH10 statement specifically as follows:  ARCH10 = T/DEST1/FORM1/T/  

     - (NOTE - The criteria specified on this statement MUST MATCH the TAPECLSL, DEST and FORM criteria of the View database that you want to archive these reports to.

     - (NOTE - The above ARCH10 statement will assign the appropriate sysout characteristics to the dataset so that when it arrives in JES, View will know that it needs to archive these reports DIRECT TO TAPE).

  b. Update the Deliver "Report Definition Attributes" screen for all of the large sysouts that you want to be DIRECTLY ARCHIVED TO TAPE,  by View,  and change the current  ARCH ===> ? setting to ARCH ===> 10 for these sysouts..

  c. Recycle the Deliver STC.

Additional Information

KEY points that may result from the above functionality change that you should also consider...

- Consult with your Storage Management folks and make sure you have enough JES SPOOL space allocated to temporarily hold these large sysouts until such time as View can get the data associated to them archived to tape.

- If you use EAS, there "may be" some impact to your users during the time that View is actively archiving this data.

- Understand that because the sysouts are now archived directly to tape, they will NOT be backed up again when the standard backup is executed.

- When archived "DIRECT TO DISK" - The standard BACKUP will honor any ERO TABLE statement that direct a sysout to a specific STORGRP. 

- When archived "DIRECT TO TAPE" - Sysouts are written from JES directly to the STORGRP0 tape ONLY. Consequently, if you need to move any of these direct to tape archived sysouts to a different STORGRP, you will need to execute the SARPAC utility against the STORGRP0 tape in order to move them. (The SARPAC program will also honor any ERO TABLE statement that direct a sysout to a specific STORGRP, just like the standard backup does). 

For more information on View/Deliver direct to tape configuration please refer to:

- View TAPECLSL Initialization Parameter

- Deliver ARCH parameter