The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact firstname.lastname@example.org.
Does the job actually get submitted or not?
Is there a job log?
Which user profile is the job submitted under? You may be able to look into that user's message queue to see of Job Scheduler sent a message to that user regarding the scheduled job.
My immediate thought is that perhaps the jobd used for the scheduled job has been deleted/moved/changed?
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jerry Adams
Sent: Thursday, February 23, 2023 6:41 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Job Scheduler Issue
I have a job in the standard Job Scheduler that is set to run every day at 0430. It has been there for many years. It usually takes about five (5) minutes. Starting this week it takes about one (1) second. I.e., it does not actually run.
The job is not *Held; otherwise, of course, it would not even be evoked.
And there are no problems in the CL. I run it from the command line by copying the scheduled command, and everything runs successfully.
Any suggestions what I can look for?
Jerry C. Adams
It isn't easy being me. Sometimes even I have a hard time doing it.
IBM i Programmer/Analyst
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
As an Amazon Associate we earn from qualifying purchases.