DSXchange

The technical answer to the original question is yes. The architecture permits routine arguments to be (dimensioned) arrays. And how this can be accomplished is to be found in the DataStage BASIC manual. However, neither the editing controls for routines nor the calling mechanisms within DataStage a...

Welcome aboard! :D Since this is a server job, you really should have posted it on the server job forum. The most obvious approach would be to load the contents of the text file into a hashed file with two key columns and no non-key columns. The job to isolate the differences then extracts rows from...

DS routines don't apply to parallel jobs.

The closest you can get are operators (buildops and custom ops).

Read about these in Chapter 55 of the Parallel Job Developer's Guide (chapter number is correct for version 7).

You can create a DataStage job that retrieves the log information using the metadata I supplied to retrieve using either a UV stage or a hashed file stage. If you use a hashed file stage, the key column should be called AT.ID rather than @ID. Either stage type can constraint on any column, in the us...

If DataStage had been restarted, all locks are released. If your server has the DataStage deadlock daemon (dsdlockd) running, it will clean up locks held by defunct processes. An Administrator might also have released the lock that was held on the routine in order to perform an export of the project.

Hashed file is a method of implementing database tables in DataStage, UniVerse, UniData and other databases. Columns in the log files are: @ID Numeric event identifier (or "//..." for control records) TYPE Enumerated severity level of message WAVE.NO Internal number to identify run...

Read the chapter on the Lookup Stage in the Parallel Job Developer's Guide and you will learn about how vital it is that some key is specified for the Lookup Stage to use.

As many as you can dream up CHECK, UNIQUE, FOREIGN KEY (and other) constraints for in the target table!

Since the job sequence is a DataStage job in its own right it, too, has job parameters, which you edit in the usual way in the usual location. Having done that, when filling in the parameters for a job (or job sequence) specified in a Job Activity you can click on "Insert Job Parameter" to be presen...

Use generated SQL. Edit the derivation column in the grid of column definitions so that it contains the requisite MAX function. View the SQL to ensure that the result is what you desire (you may also need to add a GROUP BY clause on the Selection tab's Other Clauses field).

The server process (qsserv) are geared for automatic startup, so are forked by the init process (pid 1), which runs as root. Chances are that the root umask is being propagated. Need to investigate where qsserv or qsadm umask can be changed. The ipe.env.sh file in the $QSHOME/Projects/projname direc...

I normally use /tmp/ignore_me (just in case) but it never gets written to.

You can of course use a directory in the Filter command, for example and you can use whatever wildcard is relevant to your particular purpose, not just "*".

Enter dssh in the $DSHOME directory. Then SELECT * FROM UV.ACCOUNT; This will report where the DataStage Engine believes your DataStage projects to be. If this is incorrect, update the PATH column in this table. But that's not all you have to do. Next SELECT * FROM UV_SCHEMA; This will report where ...

A Sequencer (which is a component in a job sequence) can, and usually does, have multiple inputs. Its output fires depending on the Sequencer's Any/All properties when its input triggers have fired. It is permissible to have multiple output triggers from a Sequencer. However all are governed by the ...

I believe you are seeing exit status of dsjob , or exit status of osh (since you're running parallel jobs). The exit codes in JOBCONTROL.H were originally intended for server jobs. There is an expanded list of error codes in chapter 57 of the Parallel Job Developer's Guide but it does not include th...