DSXchange

Just because you have ftp access to a system doesn't mean you have telnet or any kind of command line access. From what I recall, they'd need to open up their system permissions for you and they may not be willing to do that.

What is "StageVarn"? Realize that after stage (or after job) all you'll have access to are job parameters, anything else is out of scope. If you need to pass out processing or derived data, you'll need to go back to a transform function inside a Transformer.

SQL*Loader-522: lfiopn failed for file (name)

Cause: LFI failed to open the file.

Action: Check for any possible operating system errors and/or potential memory problems.

Space? Permissions?

For one used in a field derivation, yes. For use before/after use you must create it as such... and it doesn't need to "return" anything other than success, it just needs to put a value in USERSTATUS. Also realize that it uses a hashed structure to store it, so it can only store one value ...

You mean other than what's already in the installation and configuration guide?

If you have created it as a 'before/after' routine, it will show up in the drop down.

Advise you post any error message in full, unedited. It also sounds like your hash keys aren't appropriate.

You'll also have the Guide to Migrating to IBM InfoSphere Information Server pdf that comes with the product.

So what you posted was not the "actual" script? Your posted version has no credential mechanism that I see, nor any kind of an error check, hence my comment.

Looks like you picked certain parts from Kim's backup script and for some reason left out the important bits like checking to see if commands fail and passing credentials.

All view data working means is it can read the table, the fact that all lookups fail (and are thus rejected) means your key values are not matching... hence Ray's query.

Can you explain your cleaner way, please?

Seems to me you'd have to read the record first to get the value in the field to make this decision on. :? Regardless, to answer your generic question, yes - entire records are read and then decisions on how the parse different layouts can be made after that in subsequent stages. As an 'additional i...

I don't have the time to fully absorb what you need here, but this caught my eye: We did use a transformer to hardcode the XML namespace as a text and later convert it in XML stage by specifying the DATA ELEMENT as "XML". Just want to point out that using that data element does not convert...

It can all be done at once: Column Derivation Trim((If Trim(Col1) = '' Then 'Col1 is empty' Else If Len(Trim(Col1)) > 20 Then 'Col1 length is > 20' else '' ) : (If Trim(Col2) = '' Then ',Col2 is empty ' Else If Len(Trim(Col2)) > 10 Then ',Col2 length is > 10 ' else '' ),",","B") ...