Collecting data for Remote System Explorer and LPEX Editor

If you think that Remote System Explorer and LPEX Editor might be the origin of a problem, collect diagnostic data that you or IBM® Software Support can use to diagnose and resolve the problem.

Collect the following diagnostic data for Remote System Explorer and LPEX Editor:

  1. Product version. (Click Help > About (Product name).)
  2. Workstation operating system version and user group.
  3. Host version.
  4. Is the problem reproducible? If so, collect a set of step-by-step reproduction instructions.
  5. A list of active antivirus or firewall applications on the workstation.
  6. Run the Verify Connection command from the Objects subsystem's context menu.
  7. Turn on additional logging:
    Note: Be sure to reset these settings to "Errors Only" when you have completed reproducing the problem and collecting the log. This will ensure that your system does not experience the performance cost of the more detailed logging.
    • Click Window > Preferences, and select Remote Systems > Logging.
    • Select Warnings, errors and information messages.
    • Data will be captured in the .metadata\.log file in your workspace directory.
    • The DDS parser's DdsModel%n.log file (where %n is replaced with 1, 2, 3, etc. as the log fills up one log file and creates another) is located by default in the C:\Documents and Settings\username directory. You can configure the amount and format of information logged as well as the log file location by editing the ddsLogging.properties file in the following directory (by default): C:\Program Files\IBM\SDPShared\plugins\com.ibm.etools.iseries.dds_version. To get detailed information about the DDS parser and model change the .level setting to FINEST from its default of SEVERE.
    • For the ILE RPG Outline view, additional information can be added to the .log file in your workspace directory for when the Update the Outline view when text is changed in the editor preference is selected. Create a file in you local drive (e.g. c:\temp\.options) with the following contents:
      • com.ibm.etools.iseries.rpgle.parser/debug=true
      • com.ibm.etools.iseries.rpgle.parser/debug/lextokens=true
      • com.ibm.etools.iseries.rpgle.parser/debug/parserules=true
      • com.ibm.etools.iseries.rpgle.parser/debug/parsestacks=true
      • com.ibm.etools.iseries.rpgle.parser/debug/parsetokens=true
      To activiate the additional logging, the product must be started with an additional command-line parameter of '-debug' specifying the file you created. e.g. -debug c:\temp\.options

Feedback