Search found 39 matches
- Sun Jun 11, 2006 10:50 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sequence - Restartability - Warnings - Status
- Replies: 4
- Views: 1648
No, not that I've seen yet... you need the job to Abort so the checkpointing can restart at that point. And your issue with 'applying the limits for warning messages to 1 does not help since the server is unable to respond in time' has been discussed here before and seems to be unique to PX jobs. P...
- Sun Jun 11, 2006 5:32 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Sequence - Restartability - Warnings - Status
- Replies: 4
- Views: 1648
Sequence - Restartability - Warnings - Status
Hi We have a rather unique problem: The design of our restartable suquence is such that if any one of the jobs finishes with a status other than "OK" control branches to a routineactivity (that updates the control table for the sequece) and then a terminator activity aborting the sequence....
- Fri May 26, 2006 3:53 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: where is the PATH variable value will be set in DataStage
- Replies: 10
- Views: 5789
where is the PATH variable value will be set in DataStage
When i'm invoking a unix script from Before job sub-routine and attempting to connect to Db2 , it fails.
But when path variable is been set properly it works fine.
Currently the issue is our dsenv file do not export PATH variable.
So i want to know how does the DataStage gets these values ?
But when path variable is been set properly it works fine.
Currently the issue is our dsenv file do not export PATH variable.
So i want to know how does the DataStage gets these values ?
- Thu May 25, 2006 8:40 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: DataStage 7.5.1 vs. DB2 UDB 8.2 in 64bit-mode
- Replies: 6
- Views: 7256
db2 connection error when pre-job subroutine script
The DB2 guys suggested: - Installing a 32-bit DB2 instance, and remotely use the 64-bit instance. We didn't really want to do that, so for now we've gone with the "kludge" in the called unix script that changes the LIBPATH and PATH to point to the 64-bit directories, just prior to running...
- Tue Apr 25, 2006 6:18 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: QUERY UNIVERSE DATABASE
- Replies: 18
- Views: 9401
Hi We're trying to create a dependancy table - where a user inputs a list of tablenames and the output displays a list of jobs where the table is being used... we could use the usage analysis tool - but for each table this would take allot of time I tried using the export method(as advised in this f...
- Fri Apr 21, 2006 5:39 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: QUERY UNIVERSE DATABASE
- Replies: 18
- Views: 9401
- Wed Apr 12, 2006 5:39 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: error while executing OPENSEQ
- Replies: 6
- Views: 2113
Re: error while executing OPENSEQ
Hi all, i am getting a strange error while using OPENSEQ Command in one routine. OPENSEQ '\home\dsa\a.txt' TO FILE ELSE ABORT. Even thought the file is existing it is going to Else part of it and aborting it. Did anyone got this error before? The above abort is intern raising the following error &q...
- Wed Apr 12, 2006 5:27 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: error while executing OPENSEQ
- Replies: 6
- Views: 2113
An OPENSEQ will take the ELSE clause if the file doesn't exist (this is normal behaviour and the file is opened) or if there is no ON ERROR clause and an error occurs. You should add error handling and also display the value of STATUS() to find out what is going wrong. Perhaps you don't have r ead ...
- Wed Apr 12, 2006 4:22 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: error while executing OPENSEQ
- Replies: 6
- Views: 2113
error while executing OPENSEQ
Hi all, i am getting a strange error while using OPENSEQ Command in one routine. OPENSEQ '\home\dsa\a.txt' TO FILE ELSE ABORT. Even thought the file is existing it is going to Else part of it and aborting it. Did anyone got this error before? The above abort is intern raising the following error &qu...