DSXchange

Peter, what 7.x version do you have? 7.1 introduced the DRS or Dynamic Relational Stage. It is an database 'agnostic' stage and it is like a combination of most of the 'native' stages plus ODBC, with the database type passed in as a parameter! It is meant to be used for exactly the situation you lis...

Christina Lim wrote:the datastage user is different from the sybase database user.

Shouldn't have anything to do with it. Sybase won't really have a clue what your 'DataStage user' is, everything is driven by the userid specified in the ODBC / Sybase OC stage.

The table has to be referenced with DB name & the owner name when the table used in the SQL query in DataStage. This will apply for all Databases. Actually, no - it doesn't. It is definitely a Good Practice and may actually be required in Sybase, for all I know. However, for a query where the owner...

Upgrade to 7.5 and enjoy the benefits of the Stored Procedure Stage. As long as you are on Oracle, that is. Support for other databases 'coming soon'.

Kind of funny... I ended up sitting through the Tips & Tricks Part 2 webinar this morning and while I'd never heard of it until it was mentioned in this thread, the presenter made an off-hand comment about their methodology - something called 'Iterations'. Err... sorry. ITERATIONS. I'd be interested...

ariear wrote:There you'll find a utility called something like HFR.

HFC - the very useful but 'unsupported' Hash File Calculator utility, written by our dear friend Mr Wurlod. As noted, it will generate the create statement needed based on your input parameters.

Documentation for the various plugin stages should have been automatically installed on your pc when the client was installed. Look for a CFFStage.pdf in the Docs directory under your DataStage installation folder. If it's not there, you'll need to pull it off of your Server installation cdrom. I'm ...

Or on stages with the older 'grid style' available (like OCI) right-click, select 'Grid Style' and then you get an 'Insert Job Parameter' helper. No typing involved.

The name of your Job Parameter surrounded by pound signs, like 'normal'. It will be a little wierd because you won't be able to see it, but try using View Data and make sure it prompts you for the Parameter so you know it's ok.

denzilsyb wrote:It seems then the devil was in the detail

It usually is! Correct display lengths are very critical to making something like this work. Just be glad there were no 'REDEFINES' in there.

Glad you got it straightened out in spite of my minimal helpage.

Technically, under 'Type' you select 'Encrypted'. But other than that, as noted, it's just basically another Job Parameter.

While you could write a routine to do this, there's no reason to do so. All you need is one transformer, so the job will still be 'compact'. Simply use a single transformer, two hash file lookup stages and two reference links back to that single transformer. Use the same field in both key fields and...

I need a couple of things resolved for my understanding (knowing that my mainframe knowledge is next to zero) Thre isn't really alot of mainframe knowledge needed here, more like COBOL knowledge. You are seeing 'binary' because of the packed decimal - COMP-3 - fields, and also the one wee COMP one ...

Take a look here and see if that helps.

Is there a question in here somewhere? You haven't given us any clues about your source data, only (apparently) what you need to do with it. Do you need help with "line splitup" or a different part or ?? Off the cuff... * You can probably use the Row Splitter stage to help tell the difference betwee...