×
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 support@midrange.com.
I've seen something similar, don't remember the exact details.
I tried to do a recreate of your issue.
I put the jobq on hold.
7=Submitted a job immediately from AJS.
Cancelled the job in the jobq.
All was fine.
AJS allowed me to change the job.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Sunday, June 25, 2017 10:01 AM
To: Midrange Systems Technical Discussion
Subject: Advanced Job Scheduler - cannot change job
All,
I (stupidly) deleted an AJS job from the job queue. Now I cannot change that AJS job because it says it is on the job queue:
Message ID . . . . . . : IJS1112
Date sent . . . . . . : 06/25/17 Time sent . . . . . . :
09:57:42
Message . . . . : Job LOGFUPD cannot be changed. Reason is 01.
Cause . . . . . : An attempt to change job LOGFUPD for group *NONE
sequence
*N failed with reason code 01. Reasons are as follows:
01 - Job status indicates that it is on the job queue or in process.
02 - Jobs with schedule of *TEMP cannot be changed.
03 - The schedule code cannot be changed from *ALTERNATE if the job is
used as an alternate in other jobs.
04 - The schedule code cannot be changed to *ALTERNATE if the job is used
within a string of dependencies.
Recovery . . . : Use the reason code to locate the area to investigate
then
retry the change operation.
I tried a Release/reset but no joy.
Message ID . . . . . . : IJS1042
Date sent . . . . . . : 06/25/17 Time sent . . . . . . :
09:57:46
Message . . . . : Job LOGFUPD cannot be reset.
Cause . . . . . : An attempt to reset job LOGFUPD for group *NONE
sequence
*N failed because the job status indicates that it is on the job queue or in
process.
Recovery . . . : Allow the job to finish processing and try the request
again.
No other option seems appropriate and documentation is lacking.
So how do I clear this up?
Thanks.
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.