DSXchange

You've elected to have a very limited time dimension table with day as its granularity. All you need to do is to generate a file with the base dates (in external or internal format), then run this through a Transformer stage to generate the key and the hierarchy (week, month, quarter, calendar year,...

There's no hierarchy. The ODBC/OCI stage (or any other SQL database stage types) selects a single column, derived as MAX(columnname), from the database table. This is loaded into a hashed file as not-the-key-column, the key column in the hashed file being the table name (probably a job parameter).

Depending on what you want to do, it may be sufficient to write to two files, then use the cat command to append the second to the first. On the other hand, if you want to append columns from one file to each row in the first file, then what you need is the Merge stage . The Merge stage performs var...

I can only see two DEPTNO tags in your XML. This might explain why there are only two output rows, since DeptNo is a column. Also, should the DNAME tag precede the closing /DEPT tag?

Eons ago I posted a function to calculate the interval between two timestamps. Search for it. If you can't find it I'll try to dig it out of my archives!

You can test your theory with the DS_CONNECT utility from the UV command prompt.

The Lookup stage is for parallel jobs.
The original poster specified server jobs, and the desire to view the value of environment variables from the UV command prompt.

To summarise thus far, your controlling job generated the error J0BlaSrc..JobControl (@J3BlaSrc): Controller problem: Error calling DSAttachJob(J3BlaSrc) (DSGetJobInfo) Failed to open RT_STATUS1886 file. (DSOpenJob) Cannot open job J3BlaSrc - not a runnable job We have eliminated the open dynamic ha...

Quick first thoughts are to monitor the system to see whether you are running out of some critical resource. For CPU monitor %Idle (very low is bad), for memory monitor PF/sec (high is bad), for physical disk I/O monitor IO/sec (high is bad). You could also check whether you're running out of slots ...

ENV is a TCL-level command that displays all currently-set environment variables. You can also use its long form, ENVIRONMENT . On Windows it is equivalent to the DOS /C set command while on UNIX it is equivalent to the SH -c set command. There is nothing in the operating system to distinguish whet...

Create a job that does anything (even just X = 0 in Job Control will suffice). Create a before-job subroutine using ExecTCL to execute the ENV command. The environment variables will appear in the job log. If you have a recent enough version of DataStage, you don't even need to do this. Each time yo...

Each batch can "see" the other's user status area. You could use this variable for communication. It persists even after the batch has finished.

Use DSSetUserStatus() function to assign a value to the user status area, and DSGetJobInfo(hJob, DSJ.USERSTATUS) to retrieve it.

You could create a DataStage job to dump the requisite contents from DataStage job logs into, for example, delimited text files. You could then create a job control routine to process a particular selection of jobs in the project (maybe all of them, maybe just the ones with a status of DSJS.RUNWARN,...

If you design a server job with a link joining two passive stages, compiling the job causes an invisible "identity Transformer" stage to be used. While this is not visible in Designer palette, you will get an "active stage finishing" message from it in the log. Active stages are the ones that issue ...

Having eliminated T30FILE as a contender, we now need to investigate whether there's really a problem with the status file RT_STATUS1885. Open a TCL prompt or Administrator client window into the project, and issue a query on it, for example COUNT RT_STATUS1886 or (if you prefer SQL) SELECT COUNT(*)...