DS Engine Problem

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Raftsman
Premium Member
Premium Member
Posts: 335
Joined: Thu May 26, 2005 8:56 am
Location: Ottawa, Canada

DS Engine Problem

Post by Raftsman »

We re-installed DataStage PX and cannot get any jobs to run. We get the following error (which is not much). Could someone please explain what the problem may be. Thanks

Starting Job IBQ_Create_Seq_TIAXSCT.
PASSWORD = ********
Attempting to Cleanup after ABORT raised in stage IBQ_Create_Seq_TIAXSCT.
Job IBQ_Create_Seq_TIAXSCT aborted.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

How about telling us what kind of a stage "IBQ_Create_Seq_TIAXSCT" is? Do server jobs run? Does a job without that kind of a stage run?
Raftsman
Premium Member
Premium Member
Posts: 335
Joined: Thu May 26, 2005 8:56 am
Location: Ottawa, Canada

Post by Raftsman »

The process reads a DB2 table and creates a dataset file. That all. When viewing the DB2 table, we can see the input. The transformer stage substrings the data and it passes the data for dataset creation. This job worked previously. We are currently re-install the software.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Do you get additional information in the log entry for "from previous run" when you reset the job? You did state in the first entry that you can't get any jobs to run - is that right? Perhaps you could try a server job that reads a sequential file and outputs to a sequential file (or even the same job in PX) - it might have something to do with your DB2 connection settings that changed during the re-install or even libraries or different paths in the dsenv file
Raftsman
Premium Member
Premium Member
Posts: 335
Joined: Thu May 26, 2005 8:56 am
Location: Ottawa, Canada

Post by Raftsman »

Cleanup and Re-installation of the product fixed the problem. We think it was corrupt files that cause the error.
Post Reply