Log collection from Common Services Message Service Server (MSS) for MOI metric data flow interruption

Products

• Mainframe Operational Intelligence

Issue/Introduction

An interruption is reported with the flow of metric data to a MOI appliance.   In order to investigate the cause, the logs for the Common Services Message Service Server should be collected and provided via a Broadcom Support Case to MOI Engineering for initial problem investigation. 

Environment

Release : 2.0 

Component : MF OPERATIONAL INTELLIGENCE

Resolution

The Common Services Message Service Server STC (installation default name ZMSSTART) is used to collect metric data and then send it to a MOI appliance.   When there is a possible issue with the MSS, please collect the following MSS Troubleshooting doc for problem analysis:

1)  Capture the default ZMSSTART ( or the name of the MSS STC that was chosen during MSS installation)  STC job output from SYSVIEW and upload it to the Broadcom Support Case opened for your issue.  

2)   Zip up the USS messageService directory and its subdirectories using the zip command below for the Message Service Server and upload it to the Broadcom Support Case opened for your issue.  

 

         Command:  zip -r <output_file> <folder>

 

                   zip -r   message_service_logs.zip    <INSTALL HOME>/deploy/cfgb/instance/messageService             

 

                           where <INSTALL HOME>/deploy/cfgb/instance/messageService (captures entire folder contents of 'brokerData', 'config', 'database', and 'logs'). 

                           The path name for the deploy/cfgb/instance file name in USS can be found in the ZMSSTART job output by doing a find in the ZMSSTART job output on ‘INSTALL_HOME’.