To debug an InfoHub from the shell, execute a command like:

$gtm_dist/mumps -run InfoHub --action=jobexam 

To debug an InfoHub from within GT.M, invoke the following entry point in the InfoHub API as an extrinsic function:



GTM>if $$status^InfoHub(7421,1)
InfoHub ID      |InfoHub Name   |State
7421            |DEMO           |Running
Process listing
   28981 InfoHub       /usr/lib/fis-gtm/V6.0-003_x86_64/mumps -direct InfoHub ^InfoHubMain 7421
   28987   NoInfo      /usr/lib/fis-gtm/V6.0-003_x86_64/mumps -direct InfoHub ^InfoHubNoInfo 7421 1998603323 1 /home/jdoe/infohub/InfoHub/InfoHub.gld
   28985   Publishers  /usr/lib/fis-gtm/V6.0-003_x86_64/mumps -direct InfoHub ^InfoHubPublisher 7421 321 1 /home/jdoe/infohub/InfoHub/InfoHub.gld
   29085    FileLine   /usr/lib/fis-gtm/V6.0-003_x86_64/mumps -direct InfoHub ^InfoHubFileLine 7421 321 1 123 /home/jdoe/infohub/InfoHub/InfoHub.gld
GTM>if $$jobexam^InfoHub(7421,"28981,28987")
PID [28981] has been notified
PID [28987] has been notified
$ $gtm_dist/mumps -r ^InfoHub --action=jobexam --pidlist=28981,28987
PID [28981] has been notified
PID [28987] has been notified

Both examples place the output of ZSHOW "*" in a file called infohub-<service>-<infohub id>[-<publisher | noinfo id>[-<xline id>]-<configuration sequence number>.ZSHOW_DMP_"_$JOB_"_"_<cntr> for PIDs 28981 and 28987.


The ZSHOW "*" output in the JOBEXAMINE files may contain confidential information gleaned from the monitored components that the process holds in local variables, and, possibly, in Intrinsic Special Variables (ISVs). If that is the case in your InfoHub deployment, ensure that the files produced by this command are appropriately secured.

loading table of contents...