DSXchange

Probably, you'd need to check with whomever setup the share.

Replace the Sequential stage with an External Source stage that just passes in the full XML file path and let the XML Input stage consume the file directly via the "URL/File path" option.

No, that's literally what I did as well and it allows the field to import as text with the 'E' in the string intact - isn't that what you mean by "without exponent"? What version of Excel do you have?

Huh, it actually worked for me when I tested it. As long as you didn't mind the 'extra' character in the field, that is. [shrug] The conversion mentioned was manual, as noted there doesn't seem to be any automated solution out there. Or did you want to convert it from scientific notation to... not s...

Your Sequence job must abort and be in an Aborted/Restartable status in order for the checkpoints to work... was it?

You need to "source" the dsenv file first to setup the environment properly:

Later when i run through a sequencer by deleting the already existing record, error occurs. keymgtgetnext value doesnt work. What exactly does this mean? There shouldn't be any need to delete from that hashed file. You can certainly use the routine anywhere a routine can be used - Server job, Seque...

Specifically, it's an account-based hashed file which live in their associated "account" which is the Project by default. You can import its metadata and view the contents via a hashed file stage, if you like, but it really isn't all that exciting.

D'oh, me typie too slow.

There is a hashed file where the current value is stored and which each call to the routine increments. You can double-click on the routine in the Manager if you want to find out the hashed file's name. "All the generated numbers" would be stored wherever you are using the values, typically a surrog...

It usually helps to explain what "not working" means.

Exactly. Your script can make no assumptions about where it is or what environment variables are available. Source your dsenv file in the script or do something to set the proper variables up.

Only if you post your sql, or at the very least the details of your job design and Oracle stage settings.

OCI != ODBC, use the Plug-in OCI metadata method to import. If you are using custom / user-defined SQL in the stage, post it.

There is at least one IBM Redbook here, perhaps more out there:

http://www.redbooks.ibm.com/abstracts/sg247576.html