Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Mon, 01 Nov 2004 @ 17:02:08 GMT


     
  <Prev Next>   <<First <Prev
Next>
Last>>
 


Subj:   Re: Problem with Named Pipe AXSMOD
 
From:   Prescott, Kyle R

For Windows platform, make sure the load utility creates the pipe and pauses for data prior to launching FEXP. This is a difference with UNIX as the utilities can be launched together with a proceeding mknod command to create the pipe.

For Windows the pipe name must have the following construct in order for the access module (np_AXSMOD) to create the pipe:

     <\\servername\pipe\mypipename>

Where the server name can be any server (including local server denoted as <\\.\>). Important: The path of pipe must be present for the access module to create the virtual pipe file vs. looking for a physical file named mypipename in the specified path. Mypipename can by any name.

Windows Example:

TPUMP/MLOAD/FLOD (Input data file - np_AXSMOD creates pipe file named edwpipe and pauses for data to arrive)

     File=\\.\pipe\edwpipe;

or

     file=\\myservername\pipe\edwpipe;

FEXP (write to pipe name created by load utility)

     OUTFILE <\\.\pipe\edwpipe>;

Or

     OUTFILE <\\myservername\pipe\edwpipe>;

Kyle Prescott
UnumProvident Corporation



     
  <Prev Next>   <<First <Prev
Next>
Last>>
 
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023