CA View - How to Limit the Number of Lines Being Collected for a Sysout

book

Article ID: 131146

calendar_today

Updated On:

Products

CA Deliver CA View

Issue/Introduction

The client collected a large report (400+ million lines), using SARSTC, causing their View database to become full.
Is there a way for View to limit how many lines it will archive of a report?

Environment

CA View - All Releases

Resolution

SARINIT parameter MAXLINES can be used to limit the number of lines that are collected, for a report, by the View SARSTC task: 

MAXLINES 

Syntax: 
MAXLINES=nnn,BYPASS | BYPASSDS,ddd 
The default is 0. 

Values are as follows: 
nnn - Specifies the maximum amount of lines to be archived to the database per SYSOUT group. 
Valid values are 1 to 16777216. A value of 0 indicates that there is no limit for the reports. 

BYPASS 
An optional parameter that specifies that any lines in excess of the number (nnn) in a SYSOUT group are deleted without archival. 
If left blank, the lines in excess of nnn are passed to the user exit SARSTCUX for processing. 

BYPASSDS 
An optional parameter that specifies that any lines in excess of the number (nnn) in a SYSOUT data set are deleted without archival. Subsequent data sets in the SYSOUT group are archived. 

ddd 
For the direct-to-CA View archival feature of CA Deliver, specifies the maximum number of lines to be archived per report. 
Valid values are 1 to 16777216. A value of 0 indicates that there is no limit for the reports. Records in excess of the specified limit are discarded. 
If the report is also designated for printing, the entire report is printed. 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 

Use of MAXLINES will interrogate the line count of every report collected to the database. 

Sometimes there can be "runaway" reports, mostly due to program loops, that can potentially fill a database. 

If a report in question is always large, it should be considered to have the report go straight to tape, bypassing the disk space use altogether. 

That would be with use of SARINIT TAPECLSL=x[xxxx], where the sysout class of the report is the class specified in the parameter. 
(Note: What is in TAPECLSL also needs to be in SARINIT CLSL.)