DSXchange

Sorry, I meant within winexe.

Sounds like you don't have write access to the QS_TEMP or Quality folders on your client machine.

Can you use CMD /C rather than winexe?

... and have you checked the server logs (primarily SystemOut.log) and, if so, did they reveal anything pertinent?

FILENAME = @NULL is invalid. You can use either ISNULL(FILENAME) or FILENAME = @NULL.STR

Using REMOVE rather than DCOUNT and a FOR loop would be more efficient.

Have you used a different configuration file at some point, or has someone deleted one or more segment files from your resource disk? Ultimately the error message is informing you that a segment (data) file cannot be found. There may be more than one. Use the Data Set Management utility to confirm t...

You're missing the THEN clause of the first IF.

The BASIC Call Interface emulates ODBC API and does not support other protocols (such as OCI). You'd be easier to create the statement and invoke it via sqlplus called through the DSExecute subroutine.

I'd envisage a double-nested If..Then..Else as the right way to solve this one.

If the source and reference data have a common key, then you can build a temporary table of the source data keys, and extract the reference data from that joined to the actual reference data, thereby processing only the reference records that are actually needed.

Did you increase the memory using the Sort stage?

Read the Planning, Installation and Configuration Guide for version 9.1, which comes with your installation software or which is accessible in the IBM Information Center

You might also engage the IBM Concierge Service to help you with the planning - this is a free service from IBM Engineering.

You could avoid splitting the file by using the "multiple readers per node" capability. Use Sort stage to sort the individual partitions (partition by the first sort key so that results are correct), and perhaps allocate more than the default amount of memory per node to reduce spillage to...

It's probably a timing issue between the two jobs. Place them in a sequence with a dependency on job1 completing successfully before job2 is triggered. Make sure, too, that both jobs refer to the same Data Set descriptor file.

Have you tried double quotes around the name of the SMTP server?