Re: Do Forever Loop

[Evan Harris <spanner@xxxxxxxxxx>]

Jim

I have created a few never ending programs and generally use a data queue 
to control them.  I guess the exact implementation you need is dependent on 
the type of processing you are undertaking.

Having said that, let me say this (as a famous Australian ex-prime minister 
reputedly said)

ANY (did you get that) ANY function intended to run like this should have 
an explicit end function.

I can't count the number of times that I have had jobs not end when the 
subsystem is ended and cause two problems:

- The subsystem won't restart properly
- Objects don't get saved properly

In my view it is the programmers responsibility to provide the operations 
people with the control necessary for them to do their jobs, whenever they 
do them. Therefore an end function is mandatory (there, I said it again)

I do a lot of this stuff for lights out type environments and there won't 
be an operator there to check that the jobs end properly, it will be 
done  in an automated fashion.

Just my particular take

Cheers
Evan Harris

>I have written a program that is to be add to the job scheduler
>that has a do forever loop (DoW 1=1).  I remember hearing some
>discussion that there was something you were supposed to do so
>programs could close gracefully if given an ENDJOB.
>
>Where do I even start to look for this?  This program does not
>require a graceful end, as it does a bit of processing then waits
>for a long time (usually 24 hours I would think) and there is a
>lot of idle time, so I doubt if they will hit the job with and
>end during processing, but you never know.
>
>Any pointers to the manual or how to do this would be appreciated.
>
>Regards,
>
>Jim Langston

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---