DSXchange

Try putting lib32 into LIBPATH ahead of lib in the dsenv script.

I've never been able to get "." to work with signed decimal numbers (those beginning with "S") which I've mainly used. That's why I thought that only "V" is valid.

S9(9).99 is not valid COBOL. It needs to be S9(9)V99 - as the examples that imported successfully show. Have "them" provide a correct copybook.

Good catch from Stuart. I'm working in an environment where most users have no access at all to the services tier.

Is the file system on which the file is located accessible to every machine in the grid that might be allocated as a compute node? (This is a requirement for success.)

If you use a BASIC Transformer stage the following expression will work. MatchField(InLink.TheString, "~0N0N0X", 2) This returns the first wholly numeric string in the original string. The tilde in the pattern is unrelated to tildes in the source string. The first part of the pattern (&quo...

Nothing I know of. There may be something like this in the new operational quality monitoring tool for 9.1.2, but I haven't played with that yet.

Contemplate also the following Modify stage functions (available in 9.1 - you'll need to check for earlier versions). compact_whitespace() strip_whitespace() trim_leading() trim_trailing() trimc() - this is the closest approximation to the Transformer Trim() function For ustring data type precede ea...

You may need to run the AppServerAdmin.sh script to re-synchronize. Your official support provider will take you through the process if you're unfamiliar with it.

Sometimes when working on a DSXchange question I want to spend more time on it than I currently have available. I'd like the ability to mark a post as unread, so I can easily return to it.

Some other way of flagging posts (apart from adding to Favorites) would be second choice.

Good catch. Your QS processing must populate columns in order for them to be visible in the Test Rule window. For example, if a name without a title is processed, then the NamePrefix column will not appear.

Database queries are asynchronous; they are submitted to the database server and results are awaited. There is nothing in DataStage that allows you manually to stop what the database server is doing (though its internal error handling can achieve this if a job aborts). You need to have a DBA termina...

If the columns are in the dictionary file, they should appear in the test window.

The UNIVERSE.INCLUDE location has been available since version 1.0.

You're missing one of the DataStage product roles and, if that's DataStage User, configuring that user's access to the project.