DSXchange

Hi Klaus, Can you try to compile a user-written routine from the GUI to see if you get a better error message. Or put a file in &PH& called "Test" with 1 line "X=1", then from the command line in that project do "BASIC &PH& Test" to see if a normal compi...

I would avoid the INLIST as that would require using a BASIC transform stage in your PX job. Are you 100% certain that the string is as you described (check the log for parameter values). You might also try using "'RED','BLUE','YELLOW'" for the parameter value to see if that makes a differ...

As Craig has already indicated, using a UNIX function such as "touch path/file/name" will create the file. Then you can test for existence from a call in a job sequence and branch accordingly.

One possible reason is physical memory. Large buffers used so much memory that the system began paging / swapping. This slowed user level processes down so much that your error occurred. This is only a guess, without additional data and your monitoring nobody can know for certain.

Recently with 8.x we built a HA set of systems for DS in a banking environment. All of the concepts worked on the assumption that jobs would abort and, after failover, would get restarted. The jobs in this case used MQ for messages and thus could guarantee that each message would be processed once a...

I stand corrected and am appropriately

If your values are in a string and formatted correctly for sql, just insert them into your custom SQL as a single value.

There are many ways to do this. First of all, you need to decide on a method to read your database flag. Here are just 2 options: a) DS job to read the DB and, if "Y", create a dummy file b) UNIX command line call to the DB which creates output which can be parsed for the flag Once you hav...

You can avoid using the sort stages by using "ORDER BY" in your queries. When using multiple partitions things get a bit trickier; you will then need to ensure that your partitioning algorithm puts like records down each stream, so that the subsequent merge will function correctly. Using t...

(1) and (2) Yes, there are limits. They are more of the type "I'd like to run 1000 jobs at the same time on my 1-CPU system; which is also running my database".

(3) No. Shared containers are loaded into the job at compile time.

Remember that CHAR fields aren't trimmed, a Char(5) string with "hi " is still "hi " after TRIMming.

If this problem occurs often, then temporarily turning off the virus scan, seeing if that is it, then re-activating it and turning off the firewall will help localize the cause. As the problem is sporadic I would tend to assume that the cause is elsewhere - perhaps a patch on the database which is d...

I'm afraid I'll have to pass, as I don't know what an "Identification Card" is with reference to DataStage. Could it be your UNIX server name?

At version 7 the documentation does not reflect the true behaviour of using multiple disks for a node. The system ends up looking at which partition is the largest (not which one has the most free space) and uses that first - thus circumventing the balancing. I believe this has been fixed at V8 but ...

I'm not at a DS installation to check, but I'm really not sure what that part num refers to. Could it be the project name that you are referring to? Did you assign this part num yourself during installation?