ESP Report Server - Common Problem Diagnoses

Products

• ESP Workload Automation

Issue/Introduction

Common Problem Diagnoses for ESP Report Server: 

1. Can't start the Report Server and in ESP JESMSGLG:
   
   ESP3883E Unable to find password matching DB2USER,RSERVER,-,RC=4
   ESP6945I Report Server is now inactive
   
   
2. Report Server shows Active and Disconnected, and following shows in ESP JESMSGLG:
   
   ESP2215E Connect(2),->127.0.0.1:6170, Connection Refused
   ESP6933E Errror connecting to Report Server
   
   
3. Report Server can't be started, and its STDERR shows error:
   
   EspMessageInDbPassword: Cannot start DB Manager:EspExceptionSQLConnectionFailed: .jcc..t4..2057..11264..3.61.84. The application server rejected establishment of the connection.
   
   An attempt was made to access a database, DB2DB, which was either not found or does not support transactions. ERRORCODE=-4499, SQLSTATE=08004 SQLState=08004 ErrorCode=-4499 Method=EspDBManager.getConnection
   
   
4. "OPER RSERVER STATUS" shows error "ESP6937E Invalid message keyword ERROR received from Report Server".
   
   
5. Report Server failed with RC=0256 and error below in its log:
   *** Report Server starting... ***
    Exception in thread "main" java.lang.OutOfMemoryError
   
   
   

Environment

Release: ALL
Component: ESP Report Server

Resolution

#1 Use PASSWORD command to define user DB2USER with its password and TYPE SERVER.
#2 Check if the port on RSERVER START command is the same port defined on RServerPort.
#3 Correct the RServerDbName, it should be the LOCATION name for mainframe DB2.
#4 One Report Server can ONLY be used by one ESP system. If it's linked to one ESP system, then linked to another one; then it will not be linked to the first one any more. And message ESP6937E will be issued for the command "OPER RSERVER STATUS" from first ESP system.
#5 Set JCL MEMLIMIT=1G in Report Server STC. We recommend to control the memory limits for all ESP JOBs/STCs including Report server be made through rules in an SMFLIMxx PARMLIB member.

Additional Information

When there is a problem with Report Server:
- Set RServerLogLevel to 9 to capture debug data in Report Server STC;
- Related ESP Edition STC JESMSGLG should also be checked for any error messages.