DSXchange

Workaround: You can reorder the input columns of a transformer stage. 1) Add a temporary transformer stage. 2) Move the output link of your sequential file to the transformer. 3) Use the transformer to reorder its input columns. 4) Move the link back to its original position. 5) Delete the temporary...

If they do not have a dataset descriptor file, then one of your inexperienced developers probably deleted the descriptor file improperly with a rm command. You can do the same for the orphaned dataset segment files. It sounds like you've done your due diligence in attempting to find the descriptor f...

I've had no problems with ODBC Connector/Sql Server/SCD stage in version 11.3. Have you used the SCD stage before? I think the first thing to check would be to make sure you don't have the output links backwards. That would probably cause the issue you're seeing. Then carefully review the purpose co...

My current client has created database views that we use to read RDM data using a database connector stage in our DataStage jobs.

As far as maintaining RDM data, that is all done within the RDM tooling.

Mike

It looks like you've assumed that the dataset descriptor file is in the same location as the dataset segment files. That could be a bad assumption.
Find the location of the descriptor file (ending in dot ds).

Mike

It sounds like you've got the Data Quality version of Information Server (if that still applies at version 11.5). I last worked on a Data Quality version at a 9.1 installation and you only got the DataStage core components, which didn't include server jobs, debugging stages, and a whole lot more of ...

There is a Version.xml file on each of the tier computers. Since a client install doesn't need to know anything about the other tiers, it's Version.xml won't have that information. If you have access to your engine tier computer, its Version.xml should at least have something in it about the service...

On your approach, doing it before a read operation makes little sense.

Best would be to do it immediately after an operation that significantly alters data content (load/insert/update/delete).

Next best would be to have a scheduled DBA task.

Mike

Do a search of the IBM Knowledge Center for the difference between out-of-band and in-band null representation.

Mike

To summarize, you need 1 input record to go through the entire pipeline before you allow the next input record to enter the pipeline in order to prevent your stored procedure from generating the same user id for similar inputs. I don't know if DataStage's wave concept can be applicable here, but it ...

It's been a while since I last used AVI, but I seem to recall the AVI stage itself having a property to point to a reference data location.

I'd check the stage properties in your developer's test job.

Mike

and sort&partitioned main input link by all the foreign key columns. It seems your understanding of how partitioning works is flawed. Besides $TMPDIR, please check for the settings of $TMP and $TEMP in your job log. If present, they will be listed in the second log entry. You can use 1 lookup s...

Seems like a UTF-8 file could come with an optional 3-byte BOM. But that is no guarantee that it is a UTF-8 file. I think if you're expecting a UTF-8 file, getting a us-ascii file should be no problem. If you're expecting a us-ascii file, getting a UTF-8 file with a BOM is going to be a problem even...

UTF-8 is a Unicode character set where characters are encoded from 1 to 4 bytes. ASCII characters are encoded in UTF-8 the same as they are in ASCII.

So us-ascii is essentially a subset of UTF-8.

Your us-ascii file is also a UTF-8 file.

Mike

IBM037 would have been my first guess too, but since it apparently didn't work out for you, I'd go with ibm-37-s390 (EBCDIC United States) as my second guess.

Mike