DSXchange

But an enhancement request for password policies to be available in internal registry has already been submitted, so "watch this space".

Only the Endianness doesn't come into this issue, which is about bittage.

Google will help with the first part of the question. Once you have decided what specific kind of crosswalk table you're interested in, it may be easier to provide cogent advice.

Looks like it's already been achieved, based on your first post in this thread. Check everything about your Engine Credentials. I'd warrant that dsadm has been set as the default for users who don't have credentials and that no other users have credentials mapped.

If, unequivocally, each value of Party_ID will occur on one and only one partition when the data are partitioned by Partition_ID then the advice you have received is sound. If this condition can not be met, even for one row, then they are wrong, and you need to partition (and sort) by Party_ID ahead...

Pre-compilation of sequences can take a bit longer, because the existence of each of the referenced jobs and routines is checked, and connectivity to the client is also checked - part of sequence compilation actually occurs on the client.

Given the transient nature of hashed files in DataStage and the apparent preference for parallel jobs - even when server jobs would be way faster - I agree with them that there'd be no market.

The suffixes are important. ".pjb" is not just a job; it's a parallel job. Can you guess what ".mjb", ".qjb" and ".sjb" are?

I'd agree with that summation. Unfortunately I'm not on an 8.7 system this week, so can't check. Next week maybe.

Pre 8.x DataStage was a stand-alone product.

... or you can set up dsadm as the default Engine Credentials. The downside is that you lose auditability - all changes will be recorded as having been made by dsadm. Why not solve the permissions problem itself, rather than take this ill-advised route?

As noted, you don't need a loop. A single Index() function can check all possible values. Delimit them, and the search string, with some character (space will do). For example, the following function will return 0 if not found and some non-zero value if found. Index(" A B C D E F G H I J K L M ...

You still need to configure a System DSN to associated the DSN with the mdb file, since DataStage will use the DSN. You also need to "register" the DSN in a uvodbc.config file. Note: If you are using a 64-bit Windows operating system, use odbcad32.exe in %Windows%\SysWOW64 folder to config...

What if you make up a string of the characters you need to convert in a stage variable. For those you can't enter via the keyboard, concatenate a Char function; for example 0xFF is Char(255).

I don't think it's ever been documented. I think of precompilation as a sanity check, for example making sure that no mandatory properties have been missed, that all the stages are connected properly, etc. But with the relatively new Connector stage types, who knows? Maybe a lot more checking is don...