DSXchange

DSExecute has four arguments, the second being the command to execute. If you look at the original post I made, I constructed the unix command first in a variable and then used the variable as th second argument. Your usage is not correct. The UnixCmd line you posted is irrelevant if you are constru...

Jobs are compiled as subroutines, called by a "stub" program DSD.RUN executing from a DS Engine shell program (currently called uvsh. There is no separating jobs from the DS Engine. Furthermore, you'd lose all of the engine bin stuff, which is kind of needed. Furthermore, the projects must exist 'ca...

Licenses are held in a table/file server side. Your issue is that you must have at least 20 sessions logged in right now, or at least have that many defunct logins with active sessions. Consider doing a "ps -ef |grep dsapi" to get a look at current attached clients. Consider using kill to knock them...

Either a Director client somewhere is viewing the log, or there may be a lock on the log file itself. To verify, find out the internal job number and then list the current locks (search the forum for DS.TOOLS or the actual command list_readu). If you see RT_LOGnnn where nnn is the job number, then y...

That's because the * is being interpreted at the command line, and not passed as an argument. Try quoting the argument when passing in.

Look at your tnsnames.ora file, use the short name of the SID or the longer name, sometimes it looks like "xxxxx.world" or "xxxxx.abc.net". Look at the service_name value and try that.

Do whatever you want. Once a job calls a script there's no way to stop the job (without a kill) until the script exits. If your script does the checks and returns a status value, then your job could do the loop. Either Batch or Sequence has the ability to loop.

Your database ODBC driver (just a guess since you didn't tell us the stage) wants NULL as the derivation, not blank.

Using DS Director, from menu Tools --> Batches --> New. In the blank job control canvas, type in this: UnixCmd="hostname" CALL DSExecute("UNIX", UnixCmd, ScreenOutput, ReturnCode) CALL DSLogInfo("The UnixCmd shows this to the screen -->":ScreenOutput, "Test") CALL DSLogInfo("The UnixCmd had this exi...

So, write a shell script and call it from a DS Sequence job command stage or write a Batch job to loop and use CALL DSExecute to periodically run the same shell script.

If you absolutely wish the mainframe processes to initiate the load, and avoid a scheduler, then you simply need to start the jobstream using the command line program dsjob on the unix server. You can invoke this using any means your mainframe has for running remote programs on other machines. In un...

The easiest way is to write the hashed file to a sequential file and then use a PX job to read that sequental file into any of the lookup mechanisms available in PX. Consider using a container on the hashed to sequential portion and embed inside the PX job. You want to make sure the data is moved in...

See the other post you made for my response.

Keep in mind that DataStage uses a code branch of the Universe product, so it's not 100% compatible. Access is done use the BCI connectivity. All you need to do is setup the odbc.ini file and the uvodbc.config file to gain access. Everything is documented under your Start Menu-->Ascential DataStage-...

One job can contain so many stages that it completely overwhelms the hardware and operating system, so it's not a measure of the number of jobs but the number of processes. You post in the Server forum, but designated parallel, so I'm giving you a generic answer that works for both. In parallel desi...