DSXchange

All marking a field as a "key" means is it is a value from the source that you need to pass to the lookup so that it can be included in (bound into) the where clause of your SQL statement. While normally yes, that would imply that it also exists as a Key field in the hashed file, in this i...

OK, that helps somewhat. So, what is the ultimate goal here? The creation of a single file with all of this combined, sorted by the common key and all of the variable record metadata (and record lengths) preserved? Key1 Claims data for Key1 Pharmacy data for Key1 Prescriber data for Key1 Patient dat...

Managed to get the one pesky ROOT record deleted and now it no longer says "Cannot find job TEST". Now I get "Cannot open executable job file RT_CONFIG1775". :roll: Even better, although I can see all of the normal structures for that job in the project: $ ls -ld *1775* drwxrwxr-...

Can you post some examples of the actual file contents and then what this merged and sorted output should look like for the sample data? I think that would go a long way towards helping us help you properly.

:?: In exploring this further, the interesting thing is that this behaviour is the same across both servers and all projects for me. Doesn't matter what project I check or if we're talking the dev/qa or production servers, they all dump this huge list when I run VERIFY.SQL SCHEMA on them. Every stin...

Just to clarify, that column does not need to be one in your outgoing XML stream. It can be one that simple exists to control the file switch and does not have an XPath Expression associated with it.

Not sure if that helps or not.

As I said, there are functions for that in the API. Go to your online help Index and type 'DSGet' and they'll all be there. DSGetJobInfo DSGetNewestLogId DSGetLogSummary DSGetLogEntry There are examples in the help and searches here for those function names would find other examples, I would think. ...

You'll have to perform the lookup on four keys (Year being the fourth) then add something like "AND ? BETWEEN BEGIN_YEAR AND END_YEAR". Now, if BETWEEN isn't supported you can add it exactly as you've posted with Year replaced by question marks, but with two more question marks (rather tha...

That's what the "Use trigger column" option under Output Mode is for. Every time that column changes value, a new file is switched to. Only 'issue' is you have no control (per se) over the filenames used but it's easy enough to rename them post-process if they offend you.

Well... it says right in the error that it is a (lack of) tablespace issue.

Take the problem to your DBA.

The drivers that ship with the product are not licensed for use outside of the product stages. Why not use whatever command line DB2 provides, like sqlplus for Oracle?

HFC is on the client CDROM under 'Utilities/Unsupported' or perhaps the other way 'round. As noted, it's all there.

Good Lord, why did you post this three times? Please go delete the two extraneous ones in the Server forum before some silly wabbit replies to them!

* Don't worry - I caught them and deleted them - Andy*

You can find the syntax in any job's log that creates one - the command is 'mkdbfile' and the syntax is also documented in the HFC or Hashed File Calculator utility on your client CDROM.

No, %report% is the token in the 'sendmail' script that gets generated, you need to pass an actual value there in your call. Build a 'body' string and reference it there.