Local Redirector Plug-in specific MustGather Information:
If you experience Local Redirector Plug-in problems in version V4.0.1
and if you have not contacted IBM click: MustGather: Read first for WebSphere Application Server
for z/OS
For WebSphere Application Server Local Redirector
Plug-in problems that are
re-creatable, perform the following
steps:
(1) Turn on -vv tracing in the HTTP
Server
(2) If you are able to isolate the
failing request (i.e., eliminate additional
request workload, add the following
lines to your was.conf file:
appserver.loglevel=INFO
appserver.logdirectory=< some HFS
path >
appserver.tracelevel=*=all=enabled
service.plugin.tracelevel=MOST
*NONE or ALL are also valid, ALL
includes ICONV traces
If you unable to isolate the failing
request, add the
previous lines but change the
appserver.tracelevel=*=all=enabled
to
appserver.tracelevel=*=debug=enabled.
(3) Restart your HTTP Server with your
new trace settings, and
re-run your until your problematic
scenario re-creates.
Then, send in the following
documentation (preferably zipped as
an attachment):
(1) Configuration files: was.conf,
httpd.conf, and httpd.envvars files
(2) The ncf.log file from the
appserver.logdirectory specified.
(3) The corresponding JOBLOG containing
the -vv tracing.
For those problems that are not
re-creatable, send in the aforementioned
files as they exist on your
system.
Follow instructions in this link for FTP information:
Submitting diagnostic information to IBM
For a listing of all technotes, downloads, and educational materials
search the
WebSphere Application Serve for z/OS support site
|