Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 30 Nov 2010 @ 09:57:07 GMT


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


Subj:   How can I expand (resolve) UNIX Variable from
 
From:   DAUGHERITY, RALPH C

To avoid adding a line to each of thousands of scripts across multiple UNIX systems, I am looking for a way to create a customized SET QUERY_BAND statement by just adding code to my existing .logon files.

The customized SET QUERY_BAND statement must have current values taken from several UNIX Environment variables.

Here I show just one for simplicity.

The following works from within an in-line bteq (network-attached) invoked in a ksh environment, but FAILS when I put it inside of a .RUN FILE file:

     SET QUERY_BAND = 'UNISON_SCHED=${UNISON_SCHED};' FOR session;

1. Does anyone know how to make this work correctly (pick up the actual value from the UNIX Variable $UNISON_SCHED) when I embed it in a file named abcfile, and issue the BTEQ command:

     .RUN FILE abcfile

2. The other requirement is that MULTIPLE bteqs must be able to do this SIMULTANEOUSLY without interfering with each other, since the VALUE for the UNIX Variable will be different.

Please reply only with tested ideas which satisfy BOTH requirements #1 and #2, since I already know a lot of ways that will not work. ;>}


Ralph



     
  <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: 27 Dec 2016