View - MAXLINES number has a fixed value irrespective of size of JCL.

Products

• View

Issue/Introduction

We observe the following lines in the SARSTC job log:

SAR MAXLINES EXCEEDED BY ABCDEFGH(JOB16011) - DATASET 000 SENT TO TAPE, 47479552
SAR MAXLINES EXCEEDED BY IJKLMNOPQ(JOB16011) - DATASET 000 SENT TO TAPE, 47479552

This database captures sysouts with a maximum line count of 47479552, which routes them to tape. 

With this, View is capturing the output for each and every step for the single job .

 

Environment

Release : 14.0

Component : View

Resolution

The client had a fully-modified SARSTCUX exit. 

It was suggested that the client ensure that their SARSTCUX user exit code is not JES-level vulnerable. 

The PDBRECCT and PDBDSKEY values being accessed are contained in the SPLLINES and SPLDSID field of the SPL which is main control block passed to the exit. These fields have been available since release 11.0 of View. 

To change the SARSTCUX user exit:

 . Remove or comment out all of the $ JES macros ($BUFFER, $MODULE, etc).

 . Comment out the PDB look up code "L     R4,SPLSSCM" 4 lines after label PMMAXCK through the "LR    R4,R8" instruction, just after "MODESET KEYADDR=(2) instruction.

 . After the commenting, add 3 instructions, before the "SR    R5,R5" and "A     R5,CUMLINES" instructions.

   These instructions are as follows:

L     R8,SPLDSID     LOAD DATA SET NUMBER

STH   R8,KEY     SAVE DATA SET NUMBER

L      R4,SPLLINES  LOAD LINE COUNT.

With those changes there will no longer be any JES-release level dependency.

Install the USERMOD for SARSTCUX, then recycle the View SARSTC started task, for the changes to take effect.