MustGather: wsadmin problems in WebSphere Application Server V5.0
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with the IBM® WebSphere® Application Server for z/OS® Administrative Interface component (for example: the wsadmin tool) for all releases of V5.0. Gathering this information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
 
Resolving the problem
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:

  1. Do you see the following error when starting wsadmin?
    WASX7023E: Error creating "SOAP" connection to host "<name>";

    If yes then:
    1. The server wsadmin is attempting to connect to is not running.
    2. The port/hostname that wsadmin is using is incorrect.
    3. wsadmin is not supposed to connect to a running server and must start with option "-conntype NONE".

  2. If your wsadmin script (Java™ Command Language (JACL), JavaScript or JPython) fails to work:
    1. Determine the exact command that fails in your script, then create a simple script example.

    2. Enable tracing in wsadmin.
      1. Modify the wsadmin.properties file located in the $Install_Root/properties directory.
      2. Uncomment the following line: com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled

    3. Recreate your problem by rerunning the script file.

    4. 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

  3. If your wsadmin specific command fails to work:
    1. Enable tracing in wsadmin.

    2. Modify the wsadmin.properties file located in the Install_Root/properties directory.

    3. Uncomment the following line: com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled

    4. Recreate the problem.

    5. 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
  4. If wsadmin hangs:
    1. Enable tracing in wsadmin.

    2. Modify the wsadmin.properties file located in the Install_Root/properties directory.

    3. Uncomment the following line: com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled

    4. 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.
 
Related information
Submitting Information to IBM support
Steps to Get Support
MustGather:Read first
 
 
 


Document Information


Current web document: swg21178164.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Administrative Scripting Tools (for example: wsadmin or ANT)
Operating system(s): z/OS
Software version: 5.1
Software edition:
Reference #: 1178164
IBM Group: Software Group
Modified date: Dec 28, 2004