DSXchange

You will need to establish the file name before the job runs. You do not have access to the output of the before-job subroutine in the way you wish. If you write the result to a file then, of course, you could read that in an after-job subroutine to change the name of the actual (generic) file name ...

It's nothing to do with the Data Set. Your connection to Oracle is dead. You need to investigate that.

You're not changing the dot characters in the source time portion to colons for the target. Iconv/Oconv do not handle fractional seconds. Updtime = in.Timestamp[12,15] Updtime = Oconv(Iconv(Field(Updtime,".",1,3),"MT."),"MTS") : "." : Field(Updtime,".&quo...

Can you compile other jobs with Transformer stages?

Perhaps you need to escape the intermediate underscore?

Iconv and Oconv do not work on timestamps. As you noted, you need to separate the date and time components. Given that "-" separates your date and time components you can use substrings (as you did) but you missed the fact that the time portion begins in position 12 (the "-" is i...

No stage should re-order columns unless you design them so. If this is happening and you have not thus designed it, you have uncovered a bug, which needs to be reported through your official support provider.

The easiest non-warning way is a routine that uses the DSGetJobInfo() function. One of the returnable values is a true/false indicating whether or not the job is multi-instance capable.

Make sure that the value of APT_CONFIG_FILE currently active when executing the orchadmin command is the same as that in use when the Data Set was written.

Get on very friendly terms with your DBA. You will need to ask for a REDO (rollback) segment large enough to handle a transaction of this size.

You don't need to but, if you don't, you're going to have to write some pretty fancy script to search through the output.

If you are working in BASIC, then the syntax is upper case; LIST.READU INTERNAL.

You can process all countries using Multinational Name Set (MNS) or Worldwide Address Verification (WAVES). Read about these in the manual. in version 8.x you use the AVI stage for address verification.

There is an additional charge for WAVES.

The CLS file should be understandable (if you understand Japanese). It is a list with four columns: a token (word) that might appear in your data the standard form of that token a letter designating the class of that token within the rule set (optional) an uncertainty threshold number, such as 850 T...

Are you running version 7 or version 8? The answer was for version 7. That's what you get for hijacking threads unthinkingly.

That is correct. You have a complete installation of the PXEngine. I presume, from this post, that you do not have an Enterprise Edition licence - only a Server Edition licence.