MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: Writer keeps on ending and needs to be restarted NUMEROUS times during the day



fixed

Alan,

When you start the writer, do you have *YES as the default value in the
AUTOEND parameter?

On Tue, Jan 8, 2013 at 1:04 PM, Alan Shore <ashore@xxxxxxxx> wrote:

We have a writer that ALWAYS seems to end after printing every spool file
and needs to be started again for the next one

Here is a joblog and it seems to be code 20.
But what does it mean, and more importantly, how is it rectified?
We are on V5r4
Additional Message Information

Message ID . . . . . . : CPF1164 Severity . . . . . . . : 00
Message type . . . . . : Completion
Date sent . . . . . . : 01/08/13 Time sent . . . . . . :
12:52:37

Message . . . . : Job 057272/QSPLJOB/WPVPICK1 ended on 01/08/13 at
12:52:37;
8 seconds used; end code 20 .
Cause . . . . . : Job 057272/QSPLJOB/WPVPICK1 completed on 01/08/13 at
12:52:37 after it used 8 seconds processing unit time. The job had
ending
code 20. The job ended after 1 routing steps with a secondary ending
code of
0. The job ending codes and their meanings are as follows:
0 - The job completed normally.
10 - The job completed normally during controlled ending or controlled
subsystem ending.
20 - The job exceeded end severity (ENDSEV job attribute).
30 - The job ended abnormally.
40 - The job ended before becoming active.

More...
Press Enter to continue.

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


Disclaimer: This message contains confidential information and is intended
only for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secure or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of e-mail
transmission. If verification is required please request a hard-copy
version. Any views or opinions presented are solely those of the author and
do not necessarily represent those of the company.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact