Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
LINES Parameter in JOB statement

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
senthilkumarse
Warnings : 1

New User


Joined: 16 Sep 2005
Posts: 7

PostPosted: Fri Sep 16, 2005 2:41 pm    Post subject: LINES Parameter in JOB statement
Reply with quote

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
Back to top
View user's profile Send private message

ksubbamanoz

New User


Joined: 16 Sep 2005
Posts: 4

PostPosted: Fri Sep 16, 2005 3:30 pm    Post subject: Re: jcl doubt IN JOB STATEMENT
Reply with quote

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
Back to top
View user's profile Send private message
khamarutheen

Active Member


Joined: 23 Aug 2005
Posts: 680
Location: NJ

PostPosted: Thu Nov 17, 2005 6:46 pm    Post subject: Line
Reply with quote

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.
Back to top
View user's profile Send private message
ramangouda patil

New User


Joined: 09 Apr 2008
Posts: 39
Location: India

PostPosted: Thu Apr 16, 2009 8:29 pm    Post subject:
Reply with quote

Can we put in LINES=(999999,WARNING) and would the job still run fine if it exceeds 999,999,000 lines of ouput ?
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8152
Location: East Dubuque, Illinois, USA

PostPosted: Thu Apr 16, 2009 9:10 pm    Post subject:
Reply with quote

Quote:
Can we put in LINES=(999999,WARNING) and would the job still run fine if it exceeds 999,999,000 lines of ouput ?
Until the site support group killed you and hid your body .... icon_biggrin.gif

Seriously, you do not want to do this. Site limits are established after careful consideration of the ramifications and changing them may cause unexpected side effects. One example is that if you start writing millions of lines of output to the JES spool, sooner or later it fills up. When the JES spool fills up, JES stops submitting jobs (and sometimes jobs stop running) until the spool free space hits a certain percentage. Spool space is also needed to sign onto TSO so nobody can get into TSO until spool space is freed up ... and so forth. And no matter how big your shop is, they do not have 130 billion bytes of space allocated to the spool, so using this parameter is guaranteed to fill up spool space if your program starts looping or just writes a lot of debug data.
Back to top
View user's profile Send private message
ramangouda patil

New User


Joined: 09 Apr 2008
Posts: 39
Location: India

PostPosted: Thu Apr 16, 2009 9:47 pm    Post subject:
Reply with quote

Quote:
Until the site support group killed you and hid your body
icon_eek.gif
Didnt know I cud create so much of a trouble.. icon_lol.gif
On a serious note though, whats happened is, for one of our job has started abending lately due to spool constraints. Data handled by one of the steps has gradually increased(and will going forward). As of now we have the lines limit to 10,000 w/o any specific action for exceed. This has worked for now. But we expect it to cross this limit. So wondering if there is any other alternative.
Back to top
View user's profile Send private message
dbzTHEdinosauer

Global Moderator


Joined: 20 Oct 2006
Posts: 6968
Location: porcelain throne

PostPosted: Thu Apr 16, 2009 9:55 pm    Post subject:
Reply with quote

who actually looks at the output?

might try to determine if there is a need for the 'report'.
Back to top
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Thu Apr 16, 2009 10:04 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
ramangouda patil

New User


Joined: 09 Apr 2008
Posts: 39
Location: India

PostPosted: Thu Apr 16, 2009 10:15 pm    Post subject:
Reply with quote

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!
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8152
Location: East Dubuque, Illinois, USA

PostPosted: Thu Apr 16, 2009 10:42 pm    Post subject:
Reply with quote

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.
Back to top
View user's profile Send private message
Tom Bowman

New User


Joined: 15 Jun 2009
Posts: 3
Location: Minnesota, USA

PostPosted: Thu Jun 18, 2009 7:30 pm    Post subject:
Reply with quote

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.).
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Regarding time parameter shanthi gude JCL & VSAM 7 Mon Sep 04, 2017 2:31 pm
No new posts WER268A OUTREC STATEMENT : SYNTAX E... frozenblood87 SYNCSORT 12 Sat Aug 26, 2017 9:45 pm
No new posts Suppress value reported by BREAK in D... Learncoholic DFSORT/ICETOOL 3 Wed Aug 16, 2017 6:03 pm
No new posts Paasing symbolic parameter to instrea... Robert Sample JCL & VSAM 2 Thu Jul 27, 2017 1:22 pm
No new posts ON 2 AND EVERY 1 - Statement ??? UmeySan COBOL Programming 2 Tue Jul 25, 2017 1:20 pm

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us