DSXchange

Is the database on the same machine as the DataStage server? Is the machine paging or maximizing I/O or at 100% CPU?

In server jobs, non-key columns in hashed file cannot be looked up. Nonkey columns in database stage can used for lookups. The reasons are based on the underlying access methods. When using SQL you can select on non-key columns but the database might have to go and do a full table scan. Hashed files...

Talk to your DBA; this symptom is common when you have indices on the table. Have the DBA monitor what is going on inside the database. If you make a copy of your job and write to a sequential file instead of to the table(s) {make the file /dev/null for real speed} you will see that the job will mos...

ThilSe - that doesn't look like C++ code to me

There is an audit trail loaded into the DataStage hashed file called DS_AUDIT; this does store information including which user saved a given job or container but it doesn't contain any details on what changes were made.

I'm afraid I currently don't have any examples of this to give to you, but perhaps someone else here might wish to post code.

If the files and the tables have different structures then you will need 10 jobs to do this, or perhaps you could combine what you now have in 10 jobs into 1 job and skip using the job sequence {but that doesn't change much}.

You cannot do this directly in a transform stage. When a row is processed through a transformer it cannot know that it is the last record, since the file is processed sequentially and the EOF has not been reached.

There are many posts that go into detail on this subject that you can search for in DSXchange. The secondary keys are used to speed up access times on certain columns for certain control hashed files in DataStage. The view of jobs in the director is the result of one such query using secondary keys ...

If you know that the job is in the category but it doesn't show up in the director, you will need to run reindex from the DS.TOOLS menu. This is the typical symptom.

What about page 144 of the Advanced Programmer's Guide?

What happens when you try to view the log in the director - does it seem to "hang"? Does it only happen for this one job? Is it a PX job with thousands upon thousand of log entries?

If you declare the APT_... as parameters to your job you can pass specific values, otherwise those seen and defined in the administrator are used.

I can't recall, but I'm sure it is in the documentation somewhere. I don't have any pdf's available on this pc, but if it isn't in the advanced programmer's guide then it might be found in the original orchestrate documentation.

The default separator for the dump option of orchadmin is space, if you wish another character such as the semicolon, you need to add -delim ';'