Greetings:

I posted a message on March 19 called "job creates many repeating jobs in queue". I tried all of the suggestions you made, but the only way I've been able to stop this from happening is to disable 'Retry on error'. On one job this morning, I enabled it again with a retry interval of 120 seconds and to only retry once. Upon the next job error (a telnet connecton error which is still plaguing me) the system waited the 120 seconds and then proceeded to place 8 instances of the job in the queue.

I realize I'm running v3.2.5 on a Pentium II - 233 MHz machine with 284MB RAM running Win2000Pro, therefore it could be considered a little underpowered. This would support your earlier theory that the system is too busy doing something else when it tries to reschedule the job. But I think that it does meet your 'Recommended Configuration' requirements in the users manual.

What do you recommend now? This problem seems to have been dismissed after the last posting on April 01.

Thanks!

Could you remind how often the job is scheduled to run?

Have you checked the telnet.log file to find out which operation(s) is resposible for the long connection type?

: Greetings: I posted a message on March 19 called "job creates many
: repeating jobs in queue". I tried all of the suggestions you made,
: but the only way I've been able to stop this from happening is to disable
: 'Retry on error'. On one job this morning, I enabled it again with a retry
: interval of 120 seconds and to only retry once. Upon the next job error (a
: telnet connecton error which is still plaguing me) the system waited the
: 120 seconds and then proceeded to place 8 instances of the job in the
: queue.

: I realize I'm running v3.2.5 on a Pentium II - 233 MHz machine with 284MB RAM
: running Win2000Pro, therefore it could be considered a little
: underpowered. This would support your earlier theory that the system is
: too busy doing something else when it tries to reschedule the job. But I
: think that it does meet your 'Recommended Configuration' requirements in
: the users manual.

: What do you recommend now? This problem seems to have been dismissed after
: the last posting on April 01.

: Thanks!

Anywhere from every ten minutes to monthly.
: Could you remind how often the job is scheduled to run?

Telnet.log on the scheduler PC or on the server?
: Have you checked the telnet.log file to find out which operation(s) is
: resposible for the long connection type?

: Anywhere from every ten minutes to monthly.

One of the solutions is not to use the automatic retry. You can change your script to do something like the following

// tell 24x7 to restart the job
OnErrorGoTo START

Dim tries_count, number, 3
Dim first_try, boolean

START:
isEqual tries_count, 3, first_try
Subtract tries_count, 1, tries_count
// if still have tries do the Telnet thing
IfThen tries_count, DO_TELNET
// no more tries, abort job
Exit

DO_TELNET:
if first_try, MAIN, WAIT

WAIT:
// wait 3 minutes before making new try
Wait 120

MAIN:
// your current script below

: Telnet.log on the scheduler PC or on the server?

Telnet.log on the PC in scheduler's directory. You need to have tracing enabled in order for 24x7 to write telnet trace info into that file