Run DB2CMD commands through PowerShell
in [DB2]
|
From: Jan M. Nelken on 10 Jul 2007 13:49 Mesan wrote: > You're a genius! I know that; you know that - problem is my boss doesn't know that... > I found some help on using environment variables in > powershell and it worked like a champ! Thanks - I just wonder why I > was unable to find that tip elsewhere - where did you learn that? One of the new features in V9 was to add this undocumented environment variable... Jan M. Nelken
From: Ian on 10 Jul 2007 18:42 Jan M. Nelken wrote: > One of the new features in V9 was to add this undocumented environment > variable... Is this restricted to PowerShell? Or will this work for the regular old cmd.exe ? (Sorry, don't have a Windows box handy with DB2 9). Thanks,
From: Jan M. Nelken on 10 Jul 2007 19:30 Ian wrote: > Jan M. Nelken wrote: > >> One of the new features in V9 was to add this undocumented environment >> variable... > > Is this restricted to PowerShell? Or will this work for the regular old > cmd.exe ? (Sorry, don't have a Windows box handy with DB2 9). > > > Thanks, No - it works with Windows command prompt and cygwin bash shell etc etc. What was changed in V9 is the way we can anchor db2 environment (for communication with db2bp.exe) - Unix devotess will recognize that $$ is expanded to PID of current shell. In V8 it was an obscure way to achieve the same way. Jan M. Nelken
From: gimme_this_gimme_that on 12 Jul 2007 17:10 Hi Jan, If you get around to posting the V8 solution I'd find it useful. Cheers.
From: Jan M. Nelken on 15 Jul 2007 21:28
gimme_this_gimme_that(a)yahoo.com wrote: > If you get around to posting the V8 solution I'd find it useful. For DB2 V8 follow those relatively simple 3 steps: 1. Find out process id (PID) if the shell process (CMD.EXE) - using Task Manager, pslist.exe from Sysinternals or similliar tools; 2. Get db2ntclp.exe from IBM DB2 Support - specify your db2level; Run db2ntclp command using PID of the CMD.EXE as argument; 3. Output of the db2ntclp command will tell you the value you should set environment variable DB2CLP in the *same* CMD.EXE session whose PID you used in step 1. Jan M. Nelken |