| Author |
Message |
Don Macary
Joined: 13 Aug 2003
Posts: 51
|
|
 Asynchronous Option Greyed Out |
 |
I'm trying to change some existing jobs to be asynchronous. I can't change it because that option
is greyed out (ie. disabled).
Can anyone tell me why and what I need to do to fix this?
|
|
| Tue Jan 29, 2008 12:29 pm |
  |
 |
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7949
|
|
| |
|
This is likely a program type job and you are looking in a wrong place to change this option. This option should be enabled on the 3rd step in the Wizard.
|
|
| Tue Jan 29, 2008 1:18 pm |
|
|
Don Macary
Joined: 13 Aug 2003
Posts: 51
|
|
| Asynchronous Option Greyed Out |
|
Yes, its a program type job.
The Asynchronous option is Greyed out on both places that it is shown on the wizard.
Why would it be greyed out? It seems this way for this one customer only. I have several others that use
24x7 and I haven't seen this problem.
|
|
| Thu Jan 31, 2008 10:09 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7949
|
|
| |
|
There must be a reason for the disabled option. Somehow the Job Wizard "thinks" that the async. job option isn't applicable to this job. Please tell us more about the job setup. Is that a local/remote? attached/detached? How is it scheduled? Are there any job dependencies for it?
|
|
| Thu Jan 31, 2008 11:13 am |
|
|
Don Macary
Joined: 13 Aug 2003
Posts: 51
|
|
| Asynchronous Option Greyed Out |
|
version is 3.4.26
its running a batch file.
its local
its detached (althought there are undetached jobs with the same problems).
there are no job dependencies
the job is run by the semaphore file method.
I have the exact same setup on my server and async is active.
|
|
| Thu Jan 31, 2008 11:28 am |
|
|
Don Macary
Joined: 13 Aug 2003
Posts: 51
|
|
| Asynchronous Option Greyed Out |
|
more info
it uses a queue other than the <default> one.
and that queue is 1M in size (the default is 4M).
I tried the following and it enabled async:
1) changed the queue back to the default
2) exited out of the wizard
3) came back into the wizard and async was enabled.
could it be the queue size? Why are jobs that are scheduled to something other than the
non default queue not allow async?
thanks for your help.
|
|
| Thu Jan 31, 2008 11:34 am |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7949
|
|
| |
|
That reminds me about an old bug that was fixed quite a while ago. In simple words, the wizard doesn't allow changing the async. property if the queue property is not set to [default]. Changing queue property value to it [default], settings the async. property and then changing the queue property back to the required value can be used as a workaround. Yet, I suggest upgrading to a more recent version where this bug has been fixed so you don't need to monkey around with the queue property in order to change other stuff.
|
|
| Thu Jan 31, 2008 11:46 am |
|
|
|
