DSXchange

So easy in the USA, where every phone number has the same format. Probably the most efficient, though least flexible, is substrings. Here are some variations on that theme. cust_phone[1,3] Left(cust_phone,3) cust_phone[5,3] cust_phone[9,4] cust_phone[4] Right(cust_phone,4) The Field ...

I think the point you're missing is that DataStage is client/server computing. Even though you are working on a PC, what you're actually doing while you're importing metadata, designing and so on is being stored on another computer, which may be UNIX or may be Windows. If you issue a Run request fro...

DB2's equivalent command is the eponymous db2. :D

I have a routine that does a search-and-replace on stage and link names, plus occurrences of the search token in job parameter default values and in annotations. This enables generic job designs to be cloned and rapidly made specific. Siva, is this the kind of thing you're after? I read that you're ...

Will have to get back on the exact platform requirements.

Certainly PX is running on a cluster of Linux machines in Ascential's Melbourne (Australia) office. Supported/certified or not, it seems to work.

Ah, an easy one.

Job parameter values can not be changed once the job has started.

. My question is, is there any way to assign the stage variable value into Job parameter inside the job?

So the answer is no.

The evaluation version IS the regular one, but with a license that expires after a certain amount of time - usually a month.

The only way you can get the regular one is in exchange for kilobucks !

Umm... why is this in the Parallel Extender forum?

Evaluation editions are not available for download.

Contact Ascential Software, who may be prepared to supply a time-limited evaluation copy if there's a likelihood of a sale.

If the source is a text file, pre-process it (use Filter in the Sequential File stage, or ExecSH as a before-stage or before-job subroutine). Sort the file then grab the final line. sort filename | tail -1

The mechanism by which DataStage transfers values from itself to your SQL is parameter markers. These are either "?" or of the form ":1", ":2" and so on, depending on the database. Look at the generated SQL, perhaps in a different job. It will look something like INSERT INTO Owner.Table(col1,col...

Try lying in yout column definition metadata for the link that writes to the bulk loader. At worst you'll get ONE metadata mismatch warning, but the job will go on.

Only my solution was more flexible and easier to implement than Red Brick's Not only does Red Brick automatically maintain its aggregates, it automatically rewrites SQL executed against the base table in order to use the precomputed results stored in the aggregates, where appropriate. Bet your "sol...

Some time back I posted a stored procedure for generating a GUID in SQL Server and returning it to DataStage. Perhaps you could adapt this.

Why do you always get the hard ones, Dae-Hwan? I think you will need to ask the owners of the mainframe, or the Unisys company, what "9 bit" actually means. It may, for example, be a proprietary scheme for encoding Korean characters. If you can obtain a list of character mappings, it may be possible...