We have numerous scheduled jobs which that are simular in function and product.
When setting up a scheduled job, some of the job's properties will not allow me to check off the asynchronous processing while others will.
I created a new job schedule and during the initial setup it would allow me to check off the asynchronous check box.
After exiting and saving job and returning to the properties of the job, the asynchronous check box is grey and I can not change it.

Some of these jobs are run all day with 2 or more start times while others are once a day.

I have the default queue and two other queues currently running.

Do you have any ideas?

I don't quite understand what is happening. Here are just some thoughts.

Program type Async jobs are like "kick them off and forget"
On the other hand, Sync. type jobs are like "kick them off, monitor them and wait for them to complete" before doing next job in the same queue.

So if you choose to check job exit code you must run that job as Sync job. The scheduler in that case reverts back to Sync. job run mode. Same thing could happen if you choose to link jobs and make some other job dependent on completion of this job.

Please note the difference between program type and other type jobs. First are run by the system (Windows) while others are run by the scheduler. In the latest case even if a job is set to run Async. the scheduler always knows when it is complete and can link other jobs to completion of failure event of that job.

: We have numerous scheduled jobs which that are simular in function and
: product.
: When setting up a scheduled job, some of the job's properties will not allow
: me to check off the asynchronous processing while others will.
: I created a new job schedule and during the initial setup it would allow me
: to check off the asynchronous check box.
: After exiting and saving job and returning to the properties of the job, the
: asynchronous check box is grey and I can not change it.

: Some of these jobs are run all day with 2 or more start times while others
: are once a day.

: I have the default queue and two other queues currently running.

: Do you have any ideas?

I do not have any exit codes identified.
I am using the Job Properties Wizard on Set 3 of 12 is where
the asynchronous check box is greyed out and I can not check it off.
Is there something that I am missing in the setup to allow a single
job to run asynchronous?

: I don't quite understand what is happening. Here are just some thoughts.

: Program type Async jobs are like "kick them off and forget"
: On the other hand, Sync. type jobs are like "kick them off, monitor them
: and wait for them to complete" before doing next job in the same
: queue.

: So if you choose to check job exit code you must run that job as Sync job.
: The scheduler in that case reverts back to Sync. job run mode. Same thing
: could happen if you choose to link jobs and make some other job dependent
: on completion of this job.

: Please note the difference between program type and other type jobs. First
: are run by the system (Windows) while others are run by the scheduler. In
: the latest case even if a job is set to run Async. the scheduler always
: knows when it is complete and can link other jobs to completion of failure
: event of that job.

There must be something selected on the following steps that makes asynchronous option unusable and as a result making the asynchronous check box grayed out. What do you have selected for job notification actions and events?
: I do not have any exit codes identified.
: I am using the Job Properties Wizard on Set 3 of 12 is where
: the asynchronous check box is greyed out and I can not check it off.
: Is there something that I am missing in the setup to allow a single
: job to run asynchronous?

: There must be something selected on the following steps that makes
: asynchronous option unusable and as a result making the asynchronous check
: box grayed out. What do you have selected for job notification actions and
: events?

Job notification is on error send and email.
All of the job have this and only this checked off.

By the way:
This last message that you posted had a server error on your end.

Just to be sure we are on the same page, are you taliking about async. option displayed on step 3 or step 5?

: Job notification is on error send and email.
: All of the job have this and only this checked off.

: By the way: This last message that you posted had a server error on your end.

: Just to be sure we are on the same page, are you taliking about async. option
: displayed on step 3 or step 5?

In my prior message that I sent you I indicated step 3.

In any event, both step 3 and 5 are greyed out.

: Just to be sure we are on the same page, are you taliking about async. option
: displayed on step 3 or step 5?

Sorry about the prior message. I had sent an email to
support@SoftTreeTech.com explaining the same and got a
bit confused as to which one I was respnding to.
I sent an attachment of the job properties to the
above email address.
Again, sorry.

I think you have this job entered first to run in a job queue that has been deleted lately. You don't see the deleted name in the wizard becasue the queue names list shows [default] as the assigned queue name as it is unable to show the deleted queue. You should be able to see the originial queue name on the job properties page.

Anyway, here is how you can get the async. option back. Change the job queue to something non-default (step 5) then change it back to [default]. Close and repopen the wizard and you should get the async. option enabled again.

: In my prior message that I sent you I indicated step 3.

: In any event, both step 3 and 5 are greyed out.

: I think you have this job entered first to run in a job queue that has been
: deleted lately. You don't see the deleted name in the wizard becasue the
: queue names list shows [default] as the assigned queue name as it is
: unable to show the deleted queue. You should be able to see the originial
: queue name on the job properties page.

: Anyway, here is how you can get the async. option back. Change the job queue
: to something non-default (step 5) then change it back to [default]. Close
: and repopen the wizard and you should get the async. option enabled again.

No, the job queue was not deleted.
I have a default, jobqueue2 and jobqueue3.
It looks like if I change the job to any queue other than
default, the asynchronous option goes away. When changed back
to default it appears. Even when assigning to newly created queue and
restarting the monitor this happens.
Possible a bug when assigned to a queue other than default?

I am unable to reproduce that. I will send this case to developers for further investigation. Which version are you running? Is that 24x7 Scheduler Windows or Java version?

As a workaround for now, please set the queue to [default] first, set the job async., and then set the queue back to whatever you want.

: No, the job queue was not deleted.
: I have a default, jobqueue2 and jobqueue3.
: It looks like if I change the job to any queue other than
: default, the asynchronous option goes away. When changed back
: to default it appears. Even when assigning to newly created queue and
: restarting the monitor this happens.
: Possible a bug when assigned to a queue other than default?

: I am unable to reproduce that. I will send this case to developers for
: further investigation. Which version are you running? Is that 24x7
: Scheduler Windows or Java version?

: As a workaround for now, please set the queue to [default] first, set the job
: async., and then set the queue back to whatever you want.

Windows version 3.4.25e

This could be a design concept because normally you would only run out of one
queue for asynchronous jobs. Otherwise the monitor could have
a very large number of jobs to track from multiple sources.
If it is a design concept, it should be documented to avoid
future misunderstandings.

I will set these jobs to the defualt queue.

Thanks

Talking about the concept: even if a job is set to run in the background it is still must be assigned to a queue, because the queue really controls when and how the job starts. After the job is launched it only then becomes a background job.

: No, the job queue was not deleted.
: I have a default, jobqueue2 and jobqueue3.
: It looks like if I change the job to any queue other than
: default, the asynchronous option goes away. When changed back
: to default it appears. Even when assigning to newly created queue and
: restarting the monitor this happens.
: Possible a bug when assigned to a queue other than default?