|
Sometimes the symptoms can be misread ... I have found sometimes that things are on JOBQ but they are ON HOLD ... how did they get that way ... well some sign-ons can get their defaults that way then those sign-ons launch things & forget or never realize this, or we have some mild crisis & put some tasks on hold & forget to unhold everything when the crisis is over. WRKUSRJOB F4 select *ALL users *BATCH jobs with status *JOBQ to see what all is in all JOBQs right now & something about the status of each of those jobs. If your security is appropriate, you can 5 work with DSPJOB on those JOBQ jobs then I think it is option 1 or 2 from main menu which will tell you when the job was placed in the system (on the jobq) as opposed to started running (off the JOBQ). You might GO CMDSCDE & WRK with them *ALL to see if the scenario is with respect to a particular job that someone has placed on hold & also what the record shows there for the last time anything was submitted & when is the next time it is scheduled to run. You might check what JOBQ the jobs are supposed to run in when the Job Scheduler submits them. This is something that can get changed. For example, if it launches on schedule, it can use different rules than if someone I think it is 10 launch right now using user defaults instead. We have some tasks on Job Scheduler which would not be harmful to 10 launch right now, such as some reports & message generators - you might do so with something like that to verify that the Job Scheduler appears to be functional. You might WRKJOBQ & notice what sub systems each JOBQ is in & put cursor on sub system column & F1 to be reminded that JOBQ has to be assigned to a Sub System for jobs in that Q to run. You might GO CMDSBSD & take the option to display subsystem you think this should be running in, then take option 6 to review settings for JOBQ that are in that SBS. Where I work we just have the plain vanilla IBM Job Scheduler, not the advanced one or Help Systems Robot Scheduler - you might want to verify we talking about the same animal. > From: mark.allen@fast-friends.com (Mark Allen) > > Submitting this for someone who does not have access to the list. > > > IBM Job Scheduler suddenly stopped submitting. I am having them check to > make sure the QJOBSCD subsystem is active, is there anything else that might > be causing? > > Mark Allen > Director of MIS > Fast Friends, Inc. > (601) 888-4392 ext. 13 > www.fast-friends.com MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) AS/400 Data Manager & Programmer for BPCS 405 CD Rel-02 mixed mode (twinax interactive & batch) @ http://www.cen-elec.com Central Industries of Indiana--->Quality manufacturer of wire harnesses and electrical sub-assemblies - fax # 812-424-6838 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.