DSXchange

With a question buried in the middle of it, apparently:

sudhakar_viswa wrote:Hi,

where can i execute the following commands.And how can i specify these commands should work for specified job

They may have 4 Hyper-threaded or Dual Core CPUs on the box and going thru that particular bit of licensing fun.

If the former, you can turn that off in the BIOS from what I recall to get around the warning in every job that runs problem you've got now.

pmadhavi wrote:Pls clarify me whether all three people can work with the same ID at a time

Same ID - Yes. Same job - No.

I understand your requirements, they're not all that uncommon in a Sequence job. Two ways to do it. First is as mentioned with two links from JobActivity1 to Sequencer1. Set one to 'OK - (Conditional)' and the other to 'Warning - (Conditional)'. Set the Sequencer to 'Any' and then link it to JobActi...

Ok... then reinstall the Client software on the Citrix server.

Reinstall the Client software on the machines that are exhibiting this problem.

Reread my posts, I said to right-click on the Sequencer (blue goodie) that you need to add between your two Job Activity stages.

It's a property of the Sequencer object. By default it is set to All and you can tell that because of the three yellow 'lights' on it. If you right-click on the stage, one of the options will be to 'Set to Any'. This will cause two of the 'lights' to turn off so you can see the difference visually. ...

Well, one simple way is to use two triggers like you listed into a Sequencer set to Any that sits in front of the next job.

I'm not sure you can actually 'View Data' with a structure like that. What happens when you try and run the job?

Noted.

As noted - winner is #2.

You sure you're not thinking of the fact that they removed the warning for that PRINTER MEMORY SEGMENT REMOVED (or whatever) 'warning' message?

As noted in your other thread, it's no different - passive versus active, all works the same.

In all the years I've been doing this, I have yet to see a situation where I had to use a Stored Procedure. Maybe that's unusual, don't know. Looks like our foray into SOA land may require one real soon, however. Unless you are doing something that absolutely requires it, I would tend to avoid them...