DSXchange

Yes, if you are on version 8.5 or higher, then you can use the Loop Condition that's built into the parallel Transformer stage. Count the delimited fields in a stage variable. Iterate through the number of fields in the loop condition. Create a loop variable using the Field function. Create a constr...

It should handle that except that the version 11.3 connectivity guide for the Distributed Transaction stage indicates support equals Yes for DB2, Oracle, and MQ Connector stages and support equals No for ODBC and Teradata Connector stages. I haven't tested it myself. Sometimes the documentation is n...

First try Craig's suggestion and prove you get complete, correct output to a Sequential File stage instead of the ISD Output stage. You may be running into the 8.x bug where the ISD stage's buffer size setting is actually a hard limit (not the expected behavior). The default is 512 KB. Try doubling ...

I recall reading in the 9.1 docs that Windows servers can't run multiple servers. You could check the 11.3 docs to see if it has the same restriction.

For testing purposes pick any valid date as a default, but do check with your coworkers or the business on what they would want as a default. You may also want to look into using the NullToValue function to simplify the if then else statements.

In my case, I have encrypted parameters defined as parameters (not environment variables) within a parameter set. As they are not environment variables, they do not use $PROJDEF and DS Administrator does not come into play. In 8.7 I must recompile jobs that rely on the encrypted parameter, every tim...

If the data types are Timestamp then try to default the values to a valid timestamp. Zeros do not make for valid month or day numbers.

Or, if you really want all zeros then try using a string data type, such as Char or Varchar.

I have found that when using encrypted parameters, for passwords, that are defined within a parameter set, that it is necessary to recompile jobs that rely on the parameter set, every time after a password changes. I have not tested the same behavior when using a values file.

The Progress DataDirect ODBC drivers that come with DataStage include a few OpenEdge drivers out of the box: "Progress DataDirect OpenEdge Wire Protocol" and "Progress DataDirect OpenEdge." Have you tried either one of those to test the connectivity and performance?

I tried your syntax in 8.7 and got the same result. When I added the -sub option after -matches, then I got a good result. The wildcard on job name works using *part_of_job_name* syntax. Note that the part you match the job name on is case sensitive. Searching the knowledge center on "dssearch&...

We used to get a similar error which turned out to be caused by a firewall blockage between Information Server and the "server" that runs on the Client PC. The error is somewhat generic, so you may need to check and open firewalls, as Ernie mentioned above, "you need a clear connectio...

Great question. It's hard to name just one. I've been using DataStage from version 3.5 (Ardent) up through version 11.3. I had the good fortune of skipping versions 8.0 and 8.1. For me, the first would be the visual Designer GUI with drag 'n drop that the product was founded upon. With any job type,...

I have not used it, but only read about it here. It appears to be a design-time tool only. The document states that once the developer verifies the final output, "the job is ready to compile and run." The add-on has to be licensed in some way, however, the pricing model you described for t...

I'm not aware of any bugs in the stage. Maybe it has something to do with null handling behavior changes after version 8.1. If you are able to reproduce the difference and narrow it down further, please share the details.

Compress and Encode stages operate on data sets and as per the product manual, repartitioning is not allowed. Try them in conjunction with the Data Set stages.