Hello,

Tough one to explain, but here it is in detail:

When I use a Job/Task control to "Run Job"

I select the Job I want to run from the local server

and I pick Job Variables, and a "current Job variable"
and then set the value to {JOB(Active,Variable,var)}

When the job is run, the Job variable is set to string "{JOB(Active,Variable,var)}" versus the actual value.

Thank you,

Drew

Hmm..why do you set it to {JOB(Active,Variable,var)} when the Variable is {JOB(Active,Variable)} - do you want to include a comma in Variable name or?

---

I figured out why I would include the comma Henrik!

The variable browser gives it to me in that format.

See attachment.

Thanks,

Drew

Quick follow-up,

With the job control set to pass {JOB(Active,de_organization_id)} into the job it is calling, the string "{JOB(Active,de_organization_id)}" is set and not the value that variable contains.

thanks,

Drew

Yes, you are right, the Job Variables window is diplaying the wrong format. It should be like you describe: {JOB(Active,keyName)}

About passing the value we discovered one issue which we have fixed in latest version 7 beta build. Could you try that version?

http://www.visualcron.co....aspx?g=posts&t=3175 

---

Thank you Henrik, I wont be able to test a beta version in this environment.

Drew

Yes, you are right, the Job Variables window is diplaying the wrong format. It should be like you describe: {JOB(Active,keyName)}

About passing the value we discovered one issue which we have fixed in latest version 7 beta build. Could you try that version?

http://www.visualcron.co....aspx?g=posts&t=3175 

Continue to have issues with job variables, see attachments where now that i've converted to the format you indicated other jobs are not working.

My SQL query task fails with the error in the second screen shot if I use the format without "variable"

Thanks,

Drew

You *must* use the format with Variable. As mentioned the format is wrong when displayed in the Job Variables window but right in the Variables window.

---

It should be like you describe: {JOB(Active,keyName)}

I've read this a few times and feel like in one post you said it should be {JOB(Active,keyName)}

and now you are saying it should be

{JOB(Active,Variable,keyName)}

It is one way in one area and another format in other places?

---

Another thing that is causing an issue is that when I clone a job and update the variable in the clone window that comes up, the variable in the job I cloned FROM is updating also.

Yes, I was wrong about {JOB(Active,keyName)}. There is a bug in 6.2.2. which tells in the Job Variables window that it should be in this format while it should really be: {JOB(Active,Variable,keyName)}.

I verified that I could clone correctly in version 7.

It should be like you describe: {JOB(Active,keyName)}

I've read this a few times and feel like in one post you said it should be {JOB(Active,keyName)}

and now you are saying it should be

{JOB(Active,Variable,keyName)}

It is one way in one area and another format in other places?

---

Another thing that is causing an issue is that when I clone a job and update the variable in the clone window that comes up, the variable in the job I cloned FROM is updating also.

---