Re: New web query

[CRPence <crp@xxxxxxxxxxxxxxxxxxxx>]

  Having no idea, but from some cloudy recollection of similarly nasty 
localhost problems in an HTTP based feature, try specifying either the 
fully qualified system naming or not; i.e. the opposite of what is 
currently failing, between either of mysystem.xxx.yyy.zzz:11331 or 
mysystem:11331  ;; also review the CHGTCPDMN HOSTNAME() and DMNNAME() as 
compared to those names.

  If that does not help, then maybe... From a recent inquiry on an 
'obscure environment variable' and the apparent WAS plugin interference 
that one might infer from this posting, since the DB2 Web Query does not 
use WAS, I will offer this WAG as suggestion to try before stop/restart 
of the DB2 Web Query:
  Try to set the *SYS EnvVar SKIPWASPLUGIN = '1' by
   ADDENVVAR ENVVAR(SKIPWASPLUGIN) VALUE('1')

  A PMR sounds like a better approach regardless, or at least in 
addition, so IBM service can document the problem and outcome in a KB 
article.

Regards, Chuck