On Fri, 15 May 2009 20:20:43 -0500, Mike Walter <mike.wal...@hewitt.com>
wrote: >I agree about numberless and undocumented messages. Except from my code, of course. > >How about determining what disks/filespaces are accessed by your server, then running a Pipe to read in every accessed executable file (MODULE, LOADLIB, EXEC, and XEDIT to start), run a LOCATE stage for that message string, and display the match with the matching file ID? I rather expect that message is issued from a repository containing something like "File &1 &2 not found" -- so you won't find "File CSLCALL TRACE not found". I did a Google search for +CSLCALL and found only: Web Server--Messages (print version)This message is displayed because bot h DEBUG CSLCALL ON and DEBUG ASYNC ON have ... VM:Webgateway displays this message because DEBUG CSLCALL ON or DEBUG ... maine.edu/VM:Webgateway/help/print/prtmsgs.html - 308k - Cached - Similar pages Web Server--Messages (print version)0000I REFERENCES TO VM:WEBGATEWAY MAY REFER TO THE VM:WEBGATEWAY (TM) PRODUCT. Cause: This message contains copyright information for Sterling Software, ... vnet.ibm.com/VM:Webgateway/help/print/prtmsgs.html - Similar pages Plus some Japanese and some irrelevant ones. Are you running VM:WebGateway? Alan Ackerman alan.acker...@bankofamerica.com
