DSXchange

You need to be aware of your DB/2 settings in the output stage as well as your array size and transaction size settings.

I don't think DS.TOOLS will find these orphaned files, as they have been removed from your VOC file (but it might discover other errors, so it worth running in any case). Since the VOC pointers to these files are gone, you can delete the dynamic file directory RT_LOG123 from UNIX with a rm command. ...

If you follow the instructions and make sure that no other users are logged it then the operation is safe. If other users are logged in then you might have unusable indices, but you won't lose any jobs or data. Perhaps you could contact your support provider to get further assistance and let them ma...

If you go to the Administrator command or go into TCL in a terminal session and enter DS.TOOLS the menu will have an option to reindex the files. This might fix your error. What about your UNIX access rights to all files in the directory?

When you change the name, do you do it as a "rename" from the Director/Manager/Designer lefthand screen? This keeps the original entry in DS_JOBS file. If you do a "save as" then delete the original and then rename the copy to the original's name it might work. If this is the case, I would do a REIN...

Ray - I'll keep that in mind; I've never experimented with the PX transform speed, I think that the long copmile times led me to believe it would also execute slowly

Ray - in this case it's a scripting .BAT problem in that the telnet command isn't taking the password from the script. I did check around a bit more and found a couple of potential solutions using google but they involved using 2 or even 3 .BAT scripts. I recall having had the same type of problems ...

Yakiku,

I think the problem was inside the Oracle database and the way the tables were created - some of them were created by the DBA with a different NLS_LANG setting. It's been a while and I'm not at that site anymore so I can't recall the details.

It would seem that your project might be corrupted. When you did the DS.REINDEX did you check to see if any error messages were listed? You might also try running the TCL command DS.CHECKER when no users are logged into the project and look at the output carefully to see if any errors are shown. Is ...

Release 7.5.1r2 and the auto-purge settings are for 5 days and the logs are being purged correctly. I just logged in to the production and checked one of these multi-instance jobs to make sure and the auto-purge seems to be working.

Kris,

the time isn't being interpreted correctly, try using

Ken,

I've been monitoring the log files here and some of the jobs run with 64 parallel instances more than once a day and the auto-purge settings of 3 days do work. These jobs do run without warnings or errors, so I've never seen any effects of non-deletion.

Correct, just as server functions can't be used in PX transform stages.

Just to narrow down if the error is in the calling sequence or elsewhere, what if you copied your sequence and stripped out everthing except the call to the job - does it work then?