Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Wed, 27 Jul 2005 @ 08:44:03 GMT


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


Subj:   Re: Using rexec/rsh from Windows client
 
From:   Victor Sokovin

Hi Simion,

  I'm wondering if anyone is executing multiload/fastload on a Teradata box using rexec/rsh from a windows client. Essentially what we have is a job residing on the unix box, with the source files on the unix box, but being kicked off from the windows client.  


As I don't see any response yet for your query I would venture a few comments although they are not based on exactly the same set-up as yours.

However, we are running quite a few daily jobs on Windows boxes, and those jobs trigger Unix jobs using rsh. I wouldn't claim that this was a solution adopted without hesitation. It was rather an inevitable thing because the client still have their main "control center" on Windows but have recently purchased the software some components of which only run on Unix. To integrate the requirements we are using Ab Initio and Cygwin Korn shell emulator for Windows which came with it.

This might sound as an eclectic and over-complicated solution, which perhaps it is to some extent, but having a few layers of *reliable* software in this area seems to be paying off. The other factor which helps a lot here is that our networks seem to be reliable as well. Also, we have made sure that only fast-running jobs are using this rsh construction. I don't think we have a job of this kind which takes more than 15 min to complete (this might be different for you, and you'll have to pay attention at the run times; I have seen unsuccessful implementations of this kind around Teradata backup solutions, for example). This minimizes the risk of nasty timeouts, which always seem to be a point of concern here. In addition to the Windows "control center", Unix jobs and networks are independently monitored, so there is a good chance that the support staff will be called out when something goes funny in the chain.

On the technical level, we typically use something like

     rsh ${UNIX_RSH_HOST} -l ${UNIX_RSH_USER} -n some_Unix_script.csh

to launch a job on a Unix box (Unix-y syntax because of the emulator).

Access rights are handled via the ~/.rhosts files on Unix boxes.


  I know rexec has problems in that the job can only be run interactively due to the requirement for a password, so rsh would seem to be a better option. Any ideas?  


We use rexec in other situations and did not have problems with submitting passwords (with the extra layers of software I mentioned above) but you are probably right about the rsh being the first choice here.


Regards,

Victor



     
  <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