Lizette,

I'm certainly not anything resembling a DB2 expert, but perhaps there is some 
"version" information stored in the DBRM side file that is created / updated 
when the user application is bound to DB2?  Perhaps that could tell you what 
version of DB2 was used for the BIND operation and therefore what version you 
need to set up?

I would also go ask this question on the DB2 list if I were you.

Peter

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
Lizette Koehler
Sent: Wednesday, January 29, 2020 12:27 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: How to set up UNIX to switch between DB2 versions and .profiles

I am not very experienced in USS in z/OS

I have to set up a script that could dynamically determine

1.      What level of DB2 the user will be using (V10-V12)
2.      What level of Java they will need for that version of DB2

So when their app starts in USS, I need to setup steplib and a few other paths 
so that the invoke the correct level of DB2 and Java

So far everything I found says it needs to be in the .profile

That is too late in the process. 

So it needs to work like this

UserA executes myjava.exe (( not perfect but just to demonstrate the logic) 
which if it is on DB2 subsystem DB2A then DSNALOAD or DB2B then DB2BLOAD

The process needs to know if they will be using DB2 V10 or V11 (for example), 
then setup the STEPLIB for DSNV10 or DSNV11 load libs.  Along with the correct 
version of Java for that DB2.

I cannot prompt the user for this information.

Is there any way to do this easily or is this something that will be a 
challenge to do

Thank you 

Lizette
----------------------------------------------------------------------

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to