DSXchange

Clients connect under the process names of dscs and dsapi in the ps table. Using netstat is one of the 2 required steps to making sure there are no active process, ps is the other. That has always been true, the issue is the constant renaming of processes from uvcs to dscs; from uvapi to dsapi; unir...

Put all of your source data into a hash file and use the date as the key. Then, read the source again and reference the hash file four times. In each reference key expression, use your date value +1, +2, +3, and +4. Since most next business days will be the next day, on 5/7 attempts the +1 row will ...

You need to verify that your dsenv file does not contain errors. The startup script parses this file and you probably have errors that are preventing it from correctly parsing. I suggest you revert to your saved "before" copy and restart your services. By the way, the reason services don't start aga...

None. DS on unix uses the unix login to that server.

It works up to 7.1, haven't heard from anyone using 7.5 if it still works. The help text is one of 18-20, but I'm not sure. I did see from looking at the data that it looks to be associated from the fact that I saw delimiting multivalue marks on all of those attributes and assumed they're part of th...

Why use date? Could you use a fixed range of numbers, thereby reusing the instance? Since you're using hour, could jobname.hournumber suffice? You'll have 24 instances fixed in the status view, and can utilize the purging capabilities.

You may be running afoul of the "quotes inside quotes inside quotes" issue common to any language that has OS shells. You're best bet is to write a dynamic (temporary) shell script and execute that. By constructing it on the fly, then executing it, you avoid a lot of these hassles. Sorry, that's jus...

Sorry, I've confused myself. You're talking about getting rid of job invocations, not log entries. How to get rid of job invocations that have a date as the invocation id, meaning an infinite number of invocations. Craig's suggestion is to recompile the base job, which removes all invocations. You n...

When you use the APIs to access the log of an instance, it returns all messages across all instances of the root. You will have to discriminate the rows that pertain to the instance you have interest in. As far as Director is concerned, the only way to filter log messages on an instance is to change...

After each instance run extract the log rows for that instance run and tuck it away in your own repository table. Basically "roll your own". Set the purge to be daily and ignore DataStage's log completely.

Beat 'cha

You will have to put two links to the hash file, using 1 as the expression in the first link, and 2 as the expression in the second link. You'll double-tap the hash file, but that's your requirement. You will need to decide which takes precedence, the 1 row or the 2 row, because you may have both ro...

Reboot your server. Sorry, your locks are probably being held by Windoze, make sure you don't have any virus software running on the server.

Search the forum, we've covered this before. It's in the uvconfig file, so requires a uvregen and is a server wide setting, affecting all projects.

Leaving the field blank will default the job to creating/looking for the hash file in the project. By explicitly naming the account (project), you "lock" the hash file to that named project. Better to use a job parameter in this field. However, leaving it blank works the best since it doesn't care w...