I am not quite sure what you mean by TPTLOAD "named pipe" jobs.
I am assuming you mean that the job is sending the data through named pipes to the Load operator.
Since you also mentioned the Data Connector operator, then the job is doing one of 2 things. It is either trying to open/manage named pipes natively, or you must be using the Named Pipe Access Module.
If you are not using the Named Pipe Access Module, then you should. We do not recommend using native named pipes with TPT. Very hard to manage and they do not support restarts.
The NPAM supports restarts because it does create its own checkpoint (also called fallback) file to store data that it sends to the DC operator.
In any event, the DC operator will always create a checkpoint file because it has information of its own to keep track of while a job is running. the user should not concern itself about any temp files created under the covers.
I am not quite sure what you mean by TPTLOAD "named pipe" jobs.
I am assuming you mean that the job is sending the data through named pipes to the Load operator.
Since you also mentioned the Data Connector operator, then the job is doing one of 2 things. It is either trying to open/manage named pipes natively, or you must be using the Named Pipe Access Module.
If you are not using the Named Pipe Access Module, then you should. We do not recommend using native named pipes with TPT. Very hard to manage and they do not support restarts.
The NPAM supports restarts because it does create its own checkpoint (also called fallback) file to store data that it sends to the DC operator.
In any event, the DC operator will always create a checkpoint file because it has information of its own to keep track of while a job is running. the user should not concern itself about any temp files created under the covers.