Redwood Documentation

Product Documentation

 

›Tracing and Debugging

RunMyJobsTroubleshooting

Getting Support

  • Contacting Redwood Support Services

SAP Connector

  • Troubleshooting Connections to SAP Systems
  • Enabling XMI Logging to Troubleshoot Issues
  • Tuning Redwood Server Database Queries

Application Servers

  • Troubleshooting Redwood Server
  • Troubleshooting Performance and Memory Problems
  • Troubleshooting Performance and Memory Problems with an HP JVM
  • Troubleshooting Common Errors on Application Servers
  • Common Redwood Platform-Related Errors

Tracing and Debugging

  • Inspecting Log Files in Redwood Platform
  • Tracing and Debugging Redwood Server
  • Platform agent and System Tools logging
  • Tracing AS/400 Connections
  • Troubleshooting Credential Lookup

Common Errors

  • Common LDAP Errors
  • Common Redwood Server Errors
  • Common SAP-Related Errors
  • Common SAP BAE Errors
  • SAP BusinessObjects
  • Common External Platform-Related Errors
  • Common OracleJob-Related Errors
  • Common AS/400-Related Errors

Reference

  • JCS Errors
  • Common Logging Categories
  • GenDatabaseIndexes
← Platform agent and System Tools loggingTroubleshooting Credential Lookup →

on-site-related topic Tracing AS/400 Connections

You want to debug your AS/400 connection. System_DynamicTrace only logs messages from Redwood Server, not the connection to the AS/400 system. Redwood Server uses the JTOpen library to connect to AS/400 systems and offers an AS/400-specific a trace.dynamic action to capture logging from the JTOpen library.

Create an AS/400 process definition with the following source:

[Action]
action=trace.dynamic
category.Conversion=true
category.Datastream=true
category.Diagnostic=true
category.Error=true
category.Information=true
category.JDBC=true
category.PCML=true
category.Proxy=true
category.Thread=true
category.Warning=true


This process will run until you kill it and allows you to trace connections to AS/400 connections.

tip

If you wish to have it run for a specific period of time, such as 5 minutes for example, you navigate to the Runtime Limits tab in the process definition editor and specify 5 minutes for Maximum, check Kill process to forcefully terminate the process once the limit has been reached.

See Also

IBM AS/400 Connector Architecture

onsiteTopic

← Platform agent and System Tools loggingTroubleshooting Credential Lookup →
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |