DSXchange

DSJ.STATUS is JOB status, not stage status. Job status is returned by DSGetJobInfo; stage status is returned by DSGetStageInfo.

Create a job sequence containing a job activity. Set the run property to "reset if required, then run". On the job properties window examine the code produced by compiling this job sequence. Emulate that code.

NEVER put OpenSeq inside a loop!

It's not a command, it's a function. You first need to have allocated an ODBC environment using SQLAllocEnv() and a connection using SQLAllocConnect(). You may then wish to set connection options using SQLSetConnectionOptions(). The syntax of SQLConnect() varies depending on exactly what you want to...

My guess is that UserId is used internally as a variable name therefore making it the name of a job parameter introduced ambiguity into usage of that particular variable.

The architecture is radically changed. UniVerse, technically, has not been the Repository database since version 5.2. Since then it's been DataStage (child of UniVerse). In version 8.0 this is no longer a choice; the choices are DB2 v9, Oracle v10g or SQL Server. However, DataStage Engine continues ...

No different effect on the running of the job from -jobstatus ; either option will cause the dsjob command. The difference is that -wait does not emit a job status report and emits the exit status of dsjob rather than the exit status of the job. From memory the -wait option emits the job status on f...

You don't want to, for the reasons I gave.

Use "Cleanup Resources" in Director to log out process(es) in a job, or the equivalent function from the DS.TOOLS menu. That's the safe way.

The unsafe way is to use Task Manager on the server machine. If you do, you're on your own.

You can only initialize the stage variable successfully by creating a routine that reads the file, and invoking that routine.

What is the job design of the shared container? What is it intended to do? Does it have any of its own parameters? Did you get any warning messages logged? If so, please post the text thereof.

It doesn't really matter; it has to be supplied

APT_CONFIG_FILE needs to point to a configuration file, by default $DSHOME/../Configurations/default.apt

APT_ORCHHOME needs to point to the parallel engine directory, by default $DSHOME/../PXEngine

APT_CONFIG_FILE needs to contain the pathname of a configuration file, for example $DSHOME/../Configurations/default.apt

APT_ORCHHOME needs to contain the location of the parallel engine directory, by default $DSHOME/../PXEngine

Create a job containing no table definitions ("metadata"). Save the job so that it gets a name. Go to the New menu and create a new template from that job. Once that's done, as many times as needed go back to the New menu and choose create job from template; name the job and load the requisite table...

The easiest way to get this right is as follows. Import the table definition for the sequential file. When on the Format tab, check the "fixed width" check box, then fill in the ten column widths as a comma separated list in the indicated field. Complete the import then load the table definition int...