DSXchange

Get the tablespace increased and/or made dynamic. There's nothing you can do in DataStage to overcome "tablespace full" in Oracle.

Is your temp filespace full? Is the "cannot open compile.tmp" error happening when compiling other jobs too? Does inspecting the generated OSH reveal anything useful about the job's structure? (You need to resolve the latest problem or you won't even get that far.) Replace the Transformer stage with...

But this is Mainframe edition. Surely there's a RND function in a standard COBOL library somewhere!

Welcome aboard. :D

Just use multiple links coming from the same hashed file (or other lookup source).

Can you be more precise about what you want to accomplish?

Do you have the requisite SELECT privilege on the DB2 system tables needed to check table and column definitions, to verify that the metadata in your job design matches them.

Call one from an after-stage subroutine, the other from an after-job subroutine.

"NULL" will not fit in Char(2)

If they are all in the one directory you could use a Sequential File stage with the filter command (so that all rows from all these files (stdout from the cat command) become a single stream of data into your DataStage job).

Only four posts back on this very thread:

Director: Tools / Options / Limits - set it there. Keep in mind that this is not a global setting, but is a per user setting.

But it's applicable to every job started by the user, so it's fairly close to global.

Lookups against what? That is, what stage types are feeding the reference input links? If Oracle, is the Oracle instance on the same machine as DataStage server, or remote from it?

You need to search earlier in the code to find a comment that shows the exact function to which PUT.Pin%%V0S75P2 is mapped. You can figure out that this is performing a"write" operation, and through which stage type. An access violation (attempt to access a memory address that you do not own) may be...

Most of what can be done in DS.TOOLS can also be done in Director client Tools > Cleanup Resources. This needs to have been enabled from the DataStage Administrator.

It remains the case that Windows XP is not a supported (certified) platform and that, therefore, IBM support are within their rights to be deaf to your pleas.

Why? They're all listed in JOBCONTROL.H (in the DSINCLUDE subdirectory in each project).

You should be able to stream 70 million rows in an hour or two. After that you can stream only the changed rows, if you have some way of detecting them.