Hi Michael
You can set the message logging parameters for the job itself with the
CHGJOB command, but that doesn't affect the FTP log.
The way I would handle it would be to clear the log prior to the FTP being
executed, and then after the FTP has completed analyse the log via a program
to identify whether or not it needs to be reviewed manually.
I have posted an example CL program on how I would do it at
http://code.midrange.com/index.php?id=7755381b74 which shows what I would
do.
The CL program that runs an FTP script every 30 minutes. The program can be
shut down cleanly by setting a data area with the value "*SHUTDOWN" which is
checked before the FTP script is processed. The FTP output log is cleared
down prior to the FTP request and the new log is checked after the FTP
completes and is saved if manual review is required (in which case an
operator is notified).
The job then waits 30 minutes (1800 seconds) before repeating.
All the best
Jonathan
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger
Sent: 19 September 2007 10:48
To: midrange-l@xxxxxxxxxxxx
Subject: Re: scheduled job to run every n minutes?
I want to thank all of you for the suggestions. My preference would be to
get the Advanced Scheduler but my boss does not want to spend the money on
it (yet). So it looks like the suggestion for the CL program that is
launched at the beginning of the day by the scheduler and then suspends
itself will be what I will try to do.
I do have one concern. How can I prevent the job log from this long running
job from growing to an enormous size? I need to see the output from the FTP
command each time in case of a failure. How should I handle this?
midrange.com
