MustGather: System management for synchronization failures
 Technote (troubleshooting)
 
Problem(Abstract)
MustGather for problems with IBM® WebSphere® Application Server System Management synchronization problems. Gathering the information before calling IBM support helps familiarize you with the troubleshooting process and saves you time.
 
Resolving the problem

System Management synchronization specific MustGather information:
If you already contacted support, continue to the component-specific MustGather information. Otherwise, click: MustGather: Read first for WebSphere Application Server for z/OS®

Do the following to test and collect the correct information for understanding synchronization problems:
  1. Make sure that the File Transfer enterprise application is running on the Deployment Manager (dmgr).

  2. Try to do a full resynchronization of the problem node. This double-checks if synchronization is initialized. The following are two ways to perform a full resynchronization:

    • Using the administrative console:
      1. Expand the System Administration section and select Nodes.
      2. Check the box next to the nodes that are not synchronized.
      3. Click Full Resynchronize.
    • From the USS shell if security is enabled:
      1. Log on to TSO using a TSO userid ID that is connected to the WASKeyring that contains your SSL certificates.

      2. Add the -userid yourid and -password yourpassword parameters on your syncode command.

      3. Go to your bin directory for WebSphere root for the node you want to synchronize, for example: /WebSphere/V5R1M0/AppServer/bin, then run syncNode.sh; for example, the command contains: syncNode.sh dmgr_hostname SOAP_port

      4. Use -userid and -password keywords if security is enabled.

  3. Trace the synchronization process using one of the following two methods:
    • Add the -trace keyword on the syncNode.sh command under the built From the USS shell. The trace is written to the nodes log directory,

      For example:

      /WebSphere/V5R0M0/AppServer/logs.

    • Issue the following MVS modify commands to enable tracing:
      1. F Dmgr_control_region_name,tracejava='Sync=all=enabled'

      2. F nodeagent_name, tracejava='Sync=all=enabled'

        If issuing commands from SDSF, use the extended command line, otherwise characters are folded to uppercase, which might prevent trace from being set as successful.

  4. FTP the entire JOBLOGs for dmgr and nodeagent. FTP the syncNode.log output if run.

Refer to Submitting Diagnostic Information to IBM for FTP instructions.

For a listing of all technotes, downloads, and educational materials search the WebSphere Application Serve for z/OS support site.
 
Related information
Submitting Informaton to IBM support
Steps to Get support
MustGather: Read first
 
 
 


Document Information


Current web document: swg21181899.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > System Management/Repository
Operating system(s): z/OS
Software version: 5.1
Software edition:
Reference #: 1181899
IBM Group: Software Group
Modified date: Dec 28, 2004