CA View - The SARINIT MAXLINES Parameter and Its Use for "Runaway" reports of Large Output
search cancel

CA View - The SARINIT MAXLINES Parameter and Its Use for "Runaway" reports of Large Output


Article ID: 201735


Updated On:


Deliver View


If there is a "runaway" report that quickly fills a View database in a short amount of time, how can the SARINIT MAXLINES parameter be used to instead have that report go directly to tape?

What happens to lines that are above MAXLINES?


Release : 14.0

Component : CA View


Use of SARINIT MAXLINES will interrogate the line count of every sysout dataset collected to the database.

There can sometimes 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 accomplished 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.)

In the SARSTC task, what can be used is DD "//MAXLNTAB DD DISP=SHR,DSN=....CVDEOPTN(MAXLNJOB)", where MAXLNJOB is a member containing statements that wildcard (J=A*) or specify (JOBNAME1) jobnames to be excluded from MAXLINES processing.

Similarly, CVDEOPTN(SARSTCU9) can be used as source code to assemble to a new exit SARSTCUX, where certain Sysout IDs would be excluded from the MAXLINES checking.

Use of source CVDEOPTN(SARSTCU3), to assemble to a new exit SARSTCUX, will have a report that exceeds MAXLINES go entirely to tape.
With use of the exit, the report lines will go either all to disk or all to tape, not a mix of the two, when collected.

Any output that exceeds MAXLINES, unless addressed in the exit, is ignored and goes to the "bit bucket".