LINELMT value and PKXTLMT processing flow and how to override LINELMT
search cancel

LINELMT value and PKXTLMT processing flow and how to override LINELMT

book

Article ID: 240885

calendar_today

Updated On:

Products

JMR

Issue/Introduction

I have LINELMT=50000 specified but need some jobs with more than 50000 lines to still be captured and LINELMT bypassed. However, all other jobs still should be processed and limited by the LINELMT value in OPTIONS. How can we accomplish this?

Environment

JMR 4.6

z/OS any level

JES2 only and any level

Resolution

The PKXTLMT only works in conjunction with the LINELMT option, i.e. the LINELMT setting takes precedence, as LINELMT=NONE effectively makes JMR bypass PKXTLMT altogether.
Accordingly, should one need to enforce some kind of specific LINELMT-related behavior, you should provide a LINELMT, and have the exit return an
 
RC of your choice:
  0   =  IGNORE LINE LIMIT
  4   =  EXIT HAS DONE ALL PROCESSING NECESSARY
  8   =  DELETE REMAINDER OF SYSOUT FILES FOR THIS JOB, BUT COLLECT THE FIRST "LINE LIMIT" NUMBER OF LINES INTO THE DAILY FILE.
12   =  DELETE THIS ENTIRE JOB.  NO SYSOUT FROM THIS JOB WILL BE COLLECTED INTO THE DAILY FILE
 
Thus, for the scenario you describe, you should keep the LINELMT=n setting, check for the job names of interest inside the exit, and return 0 (ignore LINELMT) or 4 (normal processing) in case of match/mismatch, respectively.