View - Query regarding SYSOUT archival with 18M lines
search cancel

View - Query regarding SYSOUT archival with 18M lines


Article ID: 253457


Updated On:




We have SARINIT setting of:


My understanding is that this MAXLINES parm allows a maximum of 100,000 lines to archive and excess lines (lines beyond 100,000 lines) will be discarded by the archival task.

We have one SARSTC, which produces around 18 million lines of output per week.

If we increase the MAXLINES value, then it allows all SYSOUTS to archive that much, possibly filling the database.

1) How can we archive these 18 million lines to View ?

2) If 18 million lines of SYSOUT fills most of the View database, to stop the database from getting full, can we migrate this SYSOUT from DISK to TAPE in one day and delete SYSOUT from database in 2-3 days?

Does this approach sound good?



Release : 14.0


Using SARINIT TAPECLSL=... View can write large reports directly to tape, skipping its being on the database disk layer, which will save disk space. 

For example, using the following SARINIT parameters:

 . In the above, sysout of class C would get written directly to tape.
 . Note: The class(es) used in TAPECLSL must also appear in CLSL.

When View writes reports directly to tape, there is no comparison of the report size to MAXLINES.

To collect reports that have a size in the 10s-of-millions of lines, there may be need to consider use of a modified SARSTCUX exit.

CVDEOPTN(SARSTCU9) can be used as source code to assemble to exit SARSTCUX, where certain Sysout IDs would be excluded from the MAXLINES checking before being written directly to tape.

With this exit, you can use a SARSTC //MAXLNTAB DD that defines a table reports that should be excluded from the MAXLINES checking. 

To assemble any of the SARSTCUX exits, you can use CVDEJCL(BRMSSTCX).

It is better to install this exit in a test environment first, so that it can be evaluated therein.

For more details, please look into SARSTCUX - Archival Task