RE: Exporting variables in QShell

Oops the first line wrapped, try again---

I do it like this for the AS/400:

# Set the Classpath 
CLASSPATH=${CLASSPATH}:/opt/appl/bin/ps400.jar;
CLASSPATH=${CLASSPATH}:/opt/appl/electric/lib/jsse.jar;
CLASSPATH=${CLASSPATH}:/opt/appl/electric/lib/GLUE-ALL.jar;
CLASSPATH=${CLASSPATH}:/opt/appl/bin/jt400Native.jar;
CLASSPATH=${CLASSPATH}:/opt/appl/bin/xerces.jar;
CLASSPATH=${CLASSPATH}:/opt/appl/bin/xmlParserAPIs.jar;
export CLASSPATH;
echo CLASSPATH: $CLASSPATH >> /opt/AVAps/logs/stdout.log 

Also remember to export your path...

Kristen



> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx
> [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Terry Perkins
> Sent: Friday, September 16, 2005 10:51 AM
> To: java400-l@xxxxxxxxxxxx
> Subject: Exporting variables in QShell
> 
> 
> Hello
> In conjunction with trying Hibernate and Spring, we have some
> very long classpaths.  
> We have tried to set up QShell scripts that we can run to set 
> the classpath for different situations.  
> 
> A script may consist of a single line like:
> export -s CLASSPATH='.:/java/lib/jt400.jar:java/lib/utility.jar'
> 
> If we enter the export command directly in QShell it works.
> If we run it in a script it does not work.  
> It acts like all variables are local to the script and can 
> not be exported.  
> 
> What are we doing wrong?
> Do you have suggestions for dynamically setting a classpath?  
> 
> 
> Terry
> 
> 
> --
> This is the Java Programming on and around the iSeries / 
> AS400 (JAVA400-L) mailing list To post a message email: 
> JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change 
> list options,
> visit: http://lists.midrange.com/mailman/listinfo/java400-l
> or email: JAVA400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/java400-l.
> 
> 
>