LINES Parameter in JOB statement

senthilkumarse · New User Joined: 16 Sep 2005 Posts: 7

IN JCL JOB STATEMENTS WE R USING LINES=(1.CANCEL) FOR WHAT WE R MENTIONING LINES IN JOB STATEMENT, IS ANY DEFAULT IS THERE GIVE SOME GENERAL DETAILSIN THAT LINES

ksubbamanoz · New User Joined: 16 Sep 2005 Posts: 4

Hi senthil

I found this article about LINES parameter. This may clear your doubt.

*** The LINES Parameter ***

The LINES parameter is an optional parameter on the JOB statement
for use with ESA 4.2 and later releases. It indicates the maximum
amount of output, in thousands of lines, to be printed for the job's
sysout data sets. It can also be used to specify the action that
the system is to take if the maximum is exceeded.

If the LINES parameter is not specified, then the system uses an
installation-defined default value.

Syntax: LINES=nnnnnn
or
LINES=({nnnnnn{,CANCEL|DUMP|WARNING})

nnnnnn is a value between 0 and 999999 which indicates the maximum
printed output for the job, in thousands of lines. An nnnnnn
value of 300 represents 300,000 bytes. If a LINES parameter
is specified without an nnnnnn value, then the system uses an
installation-defined limit.

If nnnnnn is specified as 0:

In a JES2 system: produces an amount of output that is
based on the record blocking factor
and, when the 0 value is exceeded, one
of the following gets control:
-CANCEL, DUMP, or WARNING option
(if coded)
-the installation exit

In a JES3 system: no output is produced

CANCEL indicates that the system is to cancel the job (without
dumping storage) when the maximum output is exceeded.

DUMP indicates that the system is to cancel the job (and request
a storage dump) when the maximum output is exceeded.

WARNING indicates that the job is to continue (with a message sent
to the operator) when the maximum output is exceeded.
Subsequent warning messages are issued at an interval
defined by the installation.

If a LINES parameter is provided with neither CANCEL, DUMP, nor
WARNING specified, then the system uses an installation-defined
default option.

Specifying LINES on the JOB statement overrides:
-LINES on the JES2 /*JOBPARM statement
-the JES3 //*MAIN statement
-the installation-defined default

Examples:

//JOB10 JOB 1234,ME,LINES=(400,DUMP)

would cause JOB10 to be canceled with a dump when its
output exceeds 400,000 lines

//JOB20 JOB 1234,ME,LINES=60

would use the installation default, when JOB20 exceeds
60,000 lines of output, to determine if JOB20 is
cancelled (with or without a dump) or allowed to
continue with a warning message issued to the operator

khamarutheen · Active Member Joined: 23 Aug 2005 Posts: 677 Location: NJ

hi frnd,

syntax:

LINES={nnnnnn }
{([nnnnnn][,CANCEL]) }
{([nnnnnn][,DUMP]) }
{([nnnnnn][,WARNING])}

nnnnnn: 0 - 999999

Meaning:
Indicates the maximum
amount of output to be
printed for the job's
sysout data sets, in
thousands of lines, and
the action the system is
to take if the maximum
is exceeded.

ramangouda patil · New User Joined: 09 Apr 2008 Posts: 39 Location: India

Can we put in LINES=(999999,WARNING) and would the job still run fine if it exceeds 999,999,000 lines of ouput ?

Robert Sample · Posted: Thu Apr 16, 2009 9:10 pm

ramangouda patil · New User Joined: 09 Apr 2008 Posts: 39 Location: India

dbzTHEdinosauer · Posted: Thu Apr 16, 2009 9:55 pm

who actually looks at the output?

might try to determine if there is a need for the 'report'.

Terry Heinze · Posted: Thu Apr 16, 2009 10:04 pm

Instead of increasing your LINES parameter from 10,000 to 999,999 all in one fell swoop, I'd suggest increasing it gradually and keeping your support folks informed of the circumstances regarding the increased need. Before doing that though, follow Dick's suggestion.

ramangouda patil · New User Joined: 09 Apr 2008 Posts: 39 Location: India

There are users who need the report.So cannot do away with it.
Will kep in mind about gradually increasing and informing the support folks.
Thanks a lot for the help!

Robert Sample · Posted: Thu Apr 16, 2009 10:42 pm

Another thing to consider is sites use JES frequently to limit output by job class -- the job class you run in may be limited to 10K no matter what you set LINES= to; another reason to consult your site support group. If this is the case, they can tell you which job class you need to run in.

Tom Bowman · Posted: Thu Jun 18, 2009 7:30 pm

An easy way to deal with huge reports is to write them to a file - where users can browse it (most of the time any printing would be best as screen prints - paper is expensive, so is delivering it).

I'd consider a GDG, or perhaps an output handling system such as EOS (writes reports to VSAM and controls who can access what). Same can be done for Dumps, if they seem to be a problem (I do't really want a 'Hard Copy' dump anyway, can't Copy/Paste, etc.).