Datastage job monitor problems

Problem scene:

 

In datastage ctor, the extraction stream status is not displayed. All are ready!

 

Problem Analysis:

 

The jobmonapp service of datastage is not started or is not started correctly;

 

Solution:

 

1. Start and Stop the service manually. Run the following command to the directory:/datastage/pxengine/Java/:./jobmoninit start

 

View the log at the same time: jobmonapp. Log

 

2. If this cannot be solved, another reason is that the total number of files in/etc/hosts is missing the line 127.0.0.1 localhost!

 

Backup: participate

 

Problem (Abstract) Datastage job run statistics (I. e. rows per second processed) do not update in datastage designer or director clients.

Diagnosing the problem

This section contains a quick series of diagnosis steps for those familiar with datastage and job monitor. if more detail is needed for any step, please refer to the more detailed instructions in the "resolving the problem" section: If customer has checked and verified that the following: Confirm the jobmonapp process is up and running: PS-Ef | grep jobmonapp Confirm default ports 13400 and 13401 are listening: Netstat-an | grep 134 Check job Monitor log file for errors: CAT/IBM/informationserver/Server/pxengine/Java/jobmonapp. Log Confirm job monitor is setup to use ports 13400 and 13401 CAT/IBM/informationserver/Server/pxengine/etc/jobmon_ports If Job Monitor log shows no errors but job log reports "failed to connect to jobmonapp on port 13401" then update jobmon_ports file to use 2 new ports which are not already in use. this will require restart of datastage. If problem still occurs, confirm that/etc/hosts file contains the following entry 127.0.0.1 localhost Without a localhost entry, job monitor will be unable to use the ports correctly.

Resolving the problem

Datastage jobs generate statistics (such as rows per second processed) which can be displayed on each link when a job is run via designer. however, these statistics only update when the job monitor application, jobmonapp, is running. Jobmonapp is started with command jobmoninit script located in directory: .../IBM/informationserver/Server/pxengine/Java Verify that jobmonapp is running On UNIX systems, you can enter the following command to confirm if jobmonapp process is running: PS-Ef | grep jobmonapp To confirm if the job monitor is running. on Windows systems, you can enter "KSh" command first to obtain a command shell prompt (if installed) from where you can enter the ps command. if the job monitor is running, you shocould see a process entry with long description including the command string which started it and the 2 active ports requested. you will see a second entry also which is from the "grep" command itself, so you shoshould see at least 2 matches if the job monitor is running, I. e.: $ PS-Ef | grep jobmonapp System 4964 4044 0 09:22:27 con C:/IBM/informationserver/asbnode/apps/JRE/bin/Java-xrs-classpath C: /IBM/informationserver/Server/pxengine/Java/jobmonapp. jar; C:/IBM/informationserver/Server/pxengine/Java/xerces/xmlparserapis. jar; C:/IBM/informationserver/Server/pxengine/Java/xerces/xercesimpl. jar jobmonapp 13400 13401-Debug Dsadm 7788 4136 0 16:48:50 con grep jobmonapp However, on some platforms such as Solaris, the PS output may be truncated, and since jobmonapp appears at the end of string, the above command may not find a match even though the job is running. in this situation, you can instead look in. jobmonpid file, located in same directory as jobmoninit. the. jobmonpid file contains the process ID last used for jobmonapp. you can then query that process ID to see if it is running, I. e. if. jobmonpid file contains 3174, then enter command: $ PS-Ef | grep 3174 If jobmonapp is not running, then run the "jobmoninit" command script to restart it. Check for errors in jobmonapp. Log If jobmonapp is running, but your jobs do not update statistics, then the next place to check for an error is the jobmonapp. log file written to the above directory. historical logs are also saved in the same directory. during a normal startup, jobmonapp requires that is 2 defined ports be available, not used by other programs. one port is used to communicate with the job, while the other port is used to communicate with the datastage engine. both ports must be available, so if startup message indicates one port available and one has conflict, then job monitor will not function correctly. A normal startup log will appear as follows: Welcome to the job mon application. Tue Jun thirty 09:22:28 PDT 2009 Using ports: 13400 and 13401 A startup with port conflict will instead contain: Tue May 19 13:48:19 CDT 2009 Using ports: 13400 and 13401 Cocould not listen on port: 13400 address already in use Additionally, if the failing port is used to communicate with the running job, it may cause an additional error to appear in the job log: Failed to connect to jobmonapp on port 13401 Resolving port conflicts for jobmonapp To resolve port conflict issues for jobmonapp, use the following command to determine current usage for each port used by job monitor, I. e .: Netstat-A | grep 134 Confirm that the output shows both ports 13400 and 13401. If the ports are found, they shoshould have a status of "listening ". if the status is close_wait or something else, it cocould indicate that an older instance of datastage or jobmonapp did not successfully release the port. while some operating systems have commands to force the release of the port or to kill an application holding the port, in some cases it may take a system restart to free the port. If this port conflict continues even after a system restart, then multiple applications may have been setup to use this port. if you are running multiple datastage instances on one server, you should check the/etc/services file to confirm your ports have not been allocated to multiple applications. then look at the following file: .../IBM/informationserver/Server/pxengine/etc/jobmon_ports This file contains 2 variables that define the ports used by jobmonapp: Apt_jobmon_port1 = 13400 Apt_jobmon_port2 = 13401 For systems with multiple instances of datastage running, ensure that each instance is using a separate set of ports for the job monitor application. If two datastage instances are using the same job monitor ports, you will need to update this file for one instance. when the above 2 values are changed, both datastage and jobmonapp will need to be stopped and restarted before the change takes effect. Also confirm that your/etc/hosts file on datastage server machine contains the following entry: 127.0.0.1 localhost Without a localhost definition, the job monitor may not be able to communicate correctly on the above ports. If no port conflict exists, and no port errors are found in the jobmonapp. log File, but the log does contain other errors, it may be necessary to contact information server technical support if the error message does not give a clear cause of the problem. Running jobmonapp with debug output If no errors appear in log file, or if more detailed error messages are needed, you can run jobmonapp in debug mode. to enable debug output you will modify jobmoninit, so first create a backup copy of jobmoninit. next, edit jobmoninit and find the section of script for your current operating system, and then locate a line similar: Nohup $ apt_orchhome/Java/JRE/bin/Java-classpath $ classpath jobmonapp $ jobmon_port1 $ jobmon_port2> $ logfile 2> & 1 & Add the option "-Debug" after second port, I. e .: Nohup $ apt_orchhome/Java/JRE/bin/Java-classpath $ classpath jobmonapp $ jobmon_port1 $ jobmon_port2-Debug> $ logfile 2> & 1 & Some platforms will have 2 commands listed, one with-xrs option and one. in that situation you can update both lines. after making this change, stop and restart the job monitor application. additional debug output shoshould now appear in the log file which may provide more insight into cause of jobmonapp problems. Contacting Technical Support for job monitor problems When contacting technical support with a job monitor issue, provide the following files and details: OS platform/release info Problem symptoms/errors Version. xml Jobmonapp. Log Jobmon_ports File /Etc/services file Output of command: PS-Ef | grep jobmonapp Output of command: netstat-