DSXchange

Can you close the monitor and recompile the job? If the recompile fails then there is at least one process still running which is preventing the monitor from detecting that the job has ended. Does the job do anything out of the ordinary? Are there before- or after-job routines being called?

Now we are a step further. You have DataStage job sequences that you wish to test.

Job sequences usually are used to call DataStage jobs. Do you want to test how the job sequences handle job aborts?

I am uncertain of how SQL-Queries play a role here.

Multiple compile won't solve your problem. You have hardcoded an APT_CONFIG_FILE in those jobs and will need to correct that by either adding config files or modifying the jobs.

No, without further information nobody will be able to assist you. DataStage is not the "front-end" and thus it is unlikely that the tool will be used for front-end testing. If you think about what you are asking you'll see how difficult it is to get any answer at all, it is similar to say...

Look into your director log for an entry starting "Environment variable settings..." and in the details for that entry see which APT_CONFIG file was actually used for the run - is it the 2-node you expected? I suspect not.

I'll assume that "/data/etldata/etl_parameter" exists and that access rights are sufficient to open the file (that includes access to "/data" and "/data/etldata"). There is little that can be done now if the problem is no longer reproduceable.

I suggest you post the complete error message as it might contain hints as to the actual cause. Also, if the path or filename to the sequential file are parameterized you need to ensure that they are as expected.

Work at the problem from the other end - who or what would try to login as "kprasad"?

Setting APT_DEFAULT_TRANSPORT_BLOCK_SIZE does not change your APT_MAX_TRANSPORT_BLOCK_SIZE

synsog - you recent posts are all "what is the difference between stage A and stage B" questions. Since the answers are evident by reading the documentation supplied with DataStage and also in the on-line help, it would seem that you prefer to have other people answer your questions instea...

I wonder if it might be an implicit string conversion in the transform stage. If you use the value "-12-30-30" for your time component, is your output correct or still 00:00:00?

Use the "Constraints" in your transform stage to direct output down a link when the constraint condition is met.

That was it, Ray.

dssiddu:
The DS_LICENSE file is either corrupted or you cannot write to it. If your user has "rw" access to the file then you will need to repair this file.

Let's see, you set the maximum block size to a value of 3,002,368 and are wondering why you get an error on a block size of 4,147,970? Since we don't know the maximum block size your application can create, we cannot answer your question as to what size you need to set your $APT_MAX_TRANSPORT_BLOCK_...

The posted APT_CONFIG file has no bearing on your db2 connectivity.

Can you, from the DataStage server machine at a shell command line, successfully do a "DB2 CONNECT TO DEV1 USER YourUserName USING YourPassword"?