APAR= II09525  
NETSOFT NS/ROUTER V2.00I DATA COLLECTION

ERROR DESCRIPTION:
*** Last Updated 7/15/97 ***
 This informational APAR Documents the type of information
 required for troubleshooting NetSoft NS/Router problems
 as well as the documentation required for an APAR.

IMPORTANT: Before submitting a PTR and files to NetSoft, verify
that testing is done with the current level modules.  An attempt
should be made to recreate the problem on a PC other than the
one where the problem was discovered.  Results of this should
be provided and a step-by-step written description given on
on recreating the problem.

PLEASE PROVIDE ALL REQUESTED INFORMATION.  SUBMIT THIS
CHECKLIST IN ITS ENTIRETY (DO NOT EDIT).  PTRs WILL NOT BE
ACCEPTED IF THIS IS INCOMPLETE.

Client Access build:______ If upgrade, from what build level?___
Client Access Service Pack ________

Operating System: Windows 95____  Windows NT____
NT Checked Build? (Y/N) ________
Operating System Service Pack:________

Link Type:
___Anynet             TCP/IP Stack _________________
___Async
___AutoSync
___Netware for SAA    IPX____  TCP/IP____
___SDLC
___Twinax
___802.2  TR____  Ethernet____

If Gateway, what is the link between the Gateway and the AS400?
 __________

PLEASE SEND THE FOLLOWING TO NETSOFT ALONG WITH THE PTR REPORT:

Note:ON MOD2, USE THE ONE STEP DIAGNOSTICS TO GATHER INFORMATION
INTO AN .NSD FILE.  This automatically gathers the modules
report, workspace export, event log and trace file into a single
file that you can send.

FOR ALL PROBLEMS:

____One step diagnostics file (.NSD)
____Controller and line descriptions
____Modules Report (Module Viewer)
____Capture screen shot details for GUI problems--NOT PAGE
    FAULTS (TRAPS)
____Event Log File (.EVT) (M2 or later will be part of .NSD)
____Export of Workspace (M2 or later will be part of .NSD)
____WINSTART.BAT (If applicable)
____AUTOEXEC.BAT (If applicable)
____CONFIG.SYS (If applicable)

ALL PROBLEMS REPORTING PAGE FAULTS:

____Cut and paste PAGE FAULT (TRAP) details into text file
    (please do not send screen shots)
____WINICE for Windows 95 & NT

LINK SPECIFIC ITEMS TO BE SUBMITTED WITH THE PTR:

ANYNET
____Describe client hardware (class, processor speed, config)
____Describe network configuration (bridges, gateways)
____5250 router trace (no status dump)
____AS/400 line trace

Make sure the router trace and AS/400 line trace are started
and stopped at the same time.

ASYNC, AUTOSYNC, SDLC, TWINAX, 802.2
____AutoSync Mode (I/II)
____Modem/Card type ___________________
____5250 router trace
____Internal API trace

NETWARE FOR SAA
____Internal API trace
____PBTRACE from the gateway

Hardcopies can be faxed to (714) 753-0810, Attn: Kevin Huang.
Write the PTR number on it to aid in tracking.
Softcopies should be sent to BUBBERS@RCHVMP2 to put on
Netsoft's server.

Problem Description:

Application (step by step, what is being done when getting
the error):


HOW TO COLLECT DOCUMENTATION FOR M2

With Mod 2, collecting documentation for Netsoft is much
easier.  Their "single-click" diagnostics will collect all
information in just a few easy steps.

1.  Go to Netsoft "Diagnostics"
2.  Click on the "Start All Traces" icon on the toolbar
3.  Recreate problem
4.  Click on the "Stop all Traces" icon on the toolbar
5.  A message will be displayed stating that information
    is being collected.  This could potentially take 10
    minutes or more.  When finished it will state the name
    of the file created (will be DIAG00x.NSD)
6.  Send in this file.


HOW TO COLLECT DOCUMENTATION FOR M0 and M1

1.  The Event Log is used for posting messages from the
     NS/Router.
     Step 1.  Clear the event log.  The event log does not have
       to be cleared prior to recreating the error, but it is a
       good idea.
        a) Open the NS/Router folder from the Client Access
           folder.
        b) Double click on Diagnostic Tools.
        c) Double click on the Event Log viewer.
        d) Click on File, Click on 'Clear All Events'.
     Step 2.  Jump ahead to collecting Traces and Dumps
       and perform steps 1 and 2.
     Step 3.  Recreate the problem.
     Step 4.  Collect the Event Log.  From the Event Log
       Viewer, click on File and then 'Save As'.  Call the
       file NSLOG.EVT.

 2.  Traces and Dump.  Open the NS/Router folder (in the Client
     Access group) and then open the Diagnostic Tools folder.
     Click on Diagnostics.  Three trace and dump types are
     listed in the panel.

     Step 1.  Set the properties.  Double click on the first
       trace, 5250 Router, and enter a Trace title and a Dump
       title (Hint:  When naming the trace be sure to include
       the trace type in the title.  For example: '5250 Router
       8022 hang').   Click on OK.  Continue to set the
       properties for the Internal API and E32APPC API Trace
       types.  You do not need to name a Dump title for these
       two traces.

     Step 2.  Start the trace.  While still in the Diagnostics
       panel, select the 5250 Router trace and click on the
       green Start Trace button.  Do the same for the Internal
       API and E32APPC API traces.

     Step 3.  Recreate the problem.  The trace will begin as
       soon as the connection starts.

     Step 4.  Stop the trace.  After the problem has been
       recreated, return to the Diagnostics panel.  Select the
       5250 Router trace from the list and press the red Stop
       Trace button.  Then click on the button to the right of
       the red Stop Trace button.  This will perform the Status
       Dump.  Click the Stop Trace button for the Internal API
       and E32APPC API traces.  (Note:  If the trace is not
       stopped, the trace logs will continue to grow and may
       eventually impair system performance).  Close the
       Diagnostic viewer.

     Step 5.  Verify the trace data.  Open the Diagnostic
       Viewer program in the Diagnostic Tools folder.  In the
       left pane, you will see a tree view with Dump and Trace
       listed below Diagnostics.  If the trace and dump were
       successfully collected, you will see a plus sign in a
       box beside Dump and Trace.  There should be one dump and
       multiple traces (There is not always a one to one
       ratio of traces to files).  Click on the 5250 Router
       trace.  Check to make sure that there is data in this
       file.  If there is not any data in this file, then there
       is a good chance that the trace did not complete or
       there was no NS/Router information to trace.

     Step 6.  Export the trace data.  While still in the
       Diagnostic Viewer, click on file and Export (not the
       Export as ASCII or Export as Binary unless specifically
       asked to do so).  Name the file apropriately, keeping the
      .dgs file extension.  This file will include all of the
      traces and the dump.
 
     Step 7.  Clearing the Diagnostic Viewer.  Each subsequent
      set of traces collected will cause the list of dumps and
      traces to grow.  When a trace or dump is no longer needed
      its a good idea to delete them.  To do this, highlight
      a trace then click on Edit and delete.

3.  Module Viewer Report.  This is collected by running the
    NSMOD32.EXE program.  It will soon be accessible as an
    ICON in the NS/Router diagnostics tools folder.  If you
    do not have this icon, then it can be executed from a
    command prompt.  The Module Viewer Report should be
    collected immediately following the problem recreation.
 
    Step 1.  Click on START (on the Windows 95 task bar).

    Step 2.  Click on run.

    Step 3.  Enter the following:
      c: progra 1 ibm client 1 NSMOD32.EXE and press enter.
        = tilde character

    Step 4.   when the Module Viewer window appears, click on
      file and save it as MODULES.TXT.

4.  Registry Information.  If you believe that a problem was
    caused by putting on a service pack PTF, it is helpful to
    collect registry information from both before and after
    the Service Pack PTF install.  There are four registry
    entries needed:
                   HKEY_CURRENT_USER Software Netsoft
                   HKEY_CURRENT_USER Software IBM
                   HKEY_LOCAL_MACHINE Software Netsoft
                   HKEY_LOCAL_MACHINE Software IBM

    Step 1.  Click on START (on the Windows 95 task bar).

    Step 2.  Click on Run.

    Step 3.  Enter 'regedit' and press enter.

    Step 4.  Double click on HKEY_CURRENT_USER.

    Step 5.  Double click on Software.

    Step 6.  Single click on NetSoft (so its selected).

    Step 7.  Click on the 'Registry' pull down menu.

    Step 8.  Click on 'Export Registry File' and enter
      a file name such as USERNS1

    Step 9.  Repeat steps 4 through 8 for the other three
      registry files.

5.  DLC trace.  This trace would only be used for 802.2
    connections and will not be needed for all reported
    problems.  Information on collecting this trace will
    be added at a later date.
