Quote:
|
Originally Posted by grofaty
Why doesn't IBM eliminate the need of this db2cmd starting for each script on Windows?
|
Actually, it's not as bad as it seems: it suffices to set the environment variable DB2CLP to the same value as that from a running db2cmd window. From then on, you can do exactly the same as on unix (e.g., using a Cygwin bash window).
I guess this could be automated (i.e., scripted) in one way or the other, say by issuing db2cmd in the background and capturing the DB2CLP setting, but I did not yet bother to do so.