Deliver - Sending report directly to tape instead of disk

Products

• Deliver

Issue/Introduction

We have a large monthly report and when it is written to the VIEW database, the database gets full.

When the report is not there, the database will be 30% full.

1) Is there a way to write that report directly to tape instead of disk database first ?

2) The report size is around 577 million lines. How can we estimate how much View disk layer space will be used?

Environment

Release : 14.0

Component : View

Resolution

A report that is processed pre-spool in Deliver and written directly to View (ARCHn=DIRECT[/...]) will not use any JES spool, yet it will use View disk layer space. 

A report that is processed pre-spool in Deliver and written to the JES spool for View to process to disk (ARCHn=c/d/f/D), will use both JES spool and View disk layer space. 

A report that is processed pre-spool in Deliver and is written to View tape (ARCHn=c/d/f/T) will use JES spool, but will not use View disk layer space. 

A report that is processed post-spool in Deliver and written directly to View (ARCHn=DIRECT[/...]) will use both JES spool and View disk layer space. 

A report that is processed post-spool in Deliver and is written to View tape (ARCHn=c/d/f/T) will use JES spool, but will not use View disk layer space. 

In this instance, the client was more concerned about using JES spool, and opted to expand the View disk layer space, so no SARDBI23 messages are received when the View disk layer starts becoming full. 

Note: With the use of ARCHn=c/d/f/T, there is no need to define any corresponding class in SARINIT CLSL or TAPECLSL. 

Note 2: Regarding a report of any size, it's difficult to determine how much View disk layer space is used, as it would also depend on what BLKSIZE is being used for the View data extents, plus the personality of the report needs to be taken into consideration. 

Please see article:

https://knowledge.broadcom.com/external/article?articleId=124300