If you have not contacted support, click MustGather: Read first for WebSphere Application Server
for z/OS
Administrative Interface (wsadmin) specific MustGather information:
Use the following checklist to test and collect the correct information
to understand your wsadmin problems:
- Do you see the following error when starting wsadmin?
WASX7023E: Error creating "SOAP" connection to host "<name>";
If yes then:
- The server wsadmin is attempting to connect to is not running.
- The port/hostname that wsadmin is using is incorrect.
- wsadmin is not supposed to connect to a running server and must start
with option "-conntype NONE".
- If your wsadmin script (Java™ Command Language (JACL), JavaScript or
JPython) fails to work:
- Determine the exact command that fails in your script, then create a
simple script example.
- Enable tracing in wsadmin.
- Modify the wsadmin.properties file located in the
$Install_Root/properties directory.
- Uncomment the following line:
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
- Recreate your problem by rerunning the script file.
- Open a problem management record (PMR), if you have not already, and
forward the following files to IBM® Support:
- Install_Root/config/cells
- Install_Root/logs/wsadmin.traceout file
- Install_Root/properties/wsadmin.properites
file
- Exact Command used to execute script
- Joblogs for all servers involved
- If your wsadmin specific command fails to work:
- Enable tracing in wsadmin.
- Modify the wsadmin.properties file located in the
Install_Root/properties directory.
- Uncomment the following line:
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
- Recreate the problem.
- Forward the following files to IBM Support:
- Install_Root/config/cells
- Install_Root/logs/wsadmin.traceout file
- Install_Root/properties/wsadmin.properties
file
- Joblogs for all servers involved
- If wsadmin hangs:
- Enable tracing in wsadmin.
- Modify the wsadmin.properties file located in the
Install_Root/properties directory.
- Uncomment the following line:
com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
- Recreate your problem.
Refer to the Information Center V5.0 section: "Problems
starting or using the wsadmin command" for additional information.
There is also a White paper you can reference: Basic WebSphere Application Server V5 wsadmin Programmers
Guide.
For additional information regarding sending in documentation to IBM,
refer to Submitting Diagnostic Information to IBM link.
For a listing of all technotes, search the WebSphere Application Server for z/OS support
page. |