DSXchange

gateleys wrote:Hey Jules...

Sorry, Jules has been dead for almost 100 years now.

Really seems to be dragging ass when posting... or is it just me? Don't think so as we're starting to seem some double-posts, first sign of slowness in my experience.

Hmm... nothing seems to be happening, let me click 'Submit' again.

Yes. Completely separate sequence jobs.

That's because it deleted and recreated the log file for the job. Your problem with the 'blink' error meant the job's original log was corrupted, more than likely because it had exceeded the 2GB boundary. There are other, simpler ways of solving that particular problem.

If by that you mean running a series of jobs via a Sequencer and you want individual jobs to have different 'Abort after' warnings levels - you can't. That kind of thing would require custom job control code.

That's fine... whatever Warning Limit is in effect for the 'parent' Sequence job itself will be passed to all 'child' jobs that it runs automatically.

The simplest way is via a Custom Routine that just takes a value in and calls DSSetUSerStatus using that value. You can then either decide to pass the input argument back as the 'answer' or pass back a '0', depending on exactly how you would use it. For example: Call DSSetUserStatus(Arg1) An...

Not asking for much, eh? Milliseconds and a timezone.

Check this post from our dear friend Arnd, it covers the milliseconds part and can probably be leveraged for both.

Well, there's always the 'Stop' button in the Director. Other than that there's the operating system which can be used to end any process your have the permissions to put down. On UNIX that would be the 'kill' command against the appropriate PID. Tell us what "i tried to kill the job but cudn succee...

Specifically, page 6-31 of the Designer's Guide (version 7.5.1A) is where you want to start reading. There is a section on the Start Loop Activity, End Loop Activity and User Variables Activity stages with examples of how they can be used in a job. Don't be afraid to experiment. Not everything is ex...

Search the forum or the online help for USERSTATUS. This can be set with a single value inside a Server job and then easily picked up in a Sequencer and passed in as a parameter to a downstream job.

There have been high availability sessions at the last two conferences. It centres around the RTI pack which can automatically allocate jobs to available servers. If one server goes down or is fully loaded it allocates the job to another server. It does come at an extra cost, though I have no idea ...

Just like that. What kind of actual problem are you having? You need to send in the columns to be used in the 'where' clause marked as Key fields. The fields to actually be updated by the generated SQL are the non-Key fields, send those in with the values you want to update them to. Lastly, based on...

Since the job name is unique in the Project, it doesn't really matter to the Sequence job what category they live in.

Outputs / Properties / Wildcard. That controls what file(s) are read. If you don't use a wildcard pattern there but use a 'normal' filename it will just read that file in. You can use a parameter there in either case.