By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,610 Members | 1,672 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,610 IT Pros & Developers. It's quick & easy.

Urgent - OS scripts fails in Task Center with fixpack 10

P: n/a
After applying fixpack 10 on DB2 UDB ESE 8.1 (on Windows) all of our OS
scripts fails. The command which fails is:

db2 -svtf scriptfile.udb -z scriptfile.log

The error message is 'DB21061E Command line environment not initialized.'

We have a lot of scripts using this syntax and it is very urgent for us to
have this solved.....
Regards
Odd Bjorn Andersen
ErgoGroup As,
Oslo, Norway
Nov 12 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
start db2cmd, may be windows lost link to this file.

Nov 12 '05 #2

P: n/a
There is no problem starting db2cmd. And running db2 commands from command
window also works fine.

:-) Odd Bjorn

"bughunter@ru" <a.********@gmail.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...
start db2cmd, may be windows lost link to this file.

Nov 12 '05 #3

P: n/a
"Odd Bjørn Andersen" <od**********@ergo.no> wrote in message
news:11***************@makrell.interpost.no...
After applying fixpack 10 on DB2 UDB ESE 8.1 (on Windows) all of our OS
scripts fails. The command which fails is:

db2 -svtf scriptfile.udb -z scriptfile.log

The error message is 'DB21061E Command line environment not initialized.'

We have a lot of scripts using this syntax and it is very urgent for us to
have this solved.....
Regards
Odd Bjorn Andersen
ErgoGroup As,
Oslo, Norway

Try it without the "-s" and see if it works. If the "-s" is the problem,
then open a problem with IBM support and report it here.
Nov 12 '05 #4

P: n/a
Sounds suspiciously like this error is DOS based and not from a CLP
window.

Nov 12 '05 #5

P: n/a
Running db2 from the command line without first initializing the
environment will produce that error. The command window sets up the
environment itself, and can be seen by looking at the shortcut in the
start menu. Ultimately, it runs db2cmd which sets up the enviroment,
and then runs the other commands. Though, the command can be on the
same line.

db2cmd db2

Or the way it does it: db2cmd "db2clpsetcp db2"

B.

Nov 12 '05 #6

P: n/a
This is scripts that worked ok with db2 udb ese v 8.2.2, but when applying
fixpack this started to fail. There have been no changes to the scripts.

Regards
Odd Bjørn

"Brian Tkatch" <Ma***********@ThePentagon.com> wrote in message
news:11**********************@g49g2000cwa.googlegr oups.com...
Running db2 from the command line without first initializing the
environment will produce that error. The command window sets up the
environment itself, and can be seen by looking at the shortcut in the
start menu. Ultimately, it runs db2cmd which sets up the enviroment,
and then runs the other commands. Though, the command can be on the
same line.

db2cmd db2

Or the way it does it: db2cmd "db2clpsetcp db2"

B.

Nov 12 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.