CA Harvest debugging features

Products

• CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

Collecting and enabling debug logging can assist in troubleshooting cases you may be having.

Environment

Release: SCMNCR99000-12.5-Harvest-Software Change Manager-Named User-Competitive Replacem
Component:

Resolution

Logging procedure is: 

1. Start server side logging. -See below, either from GUI or command line- 

2. Have Harvest user reproduce use case. 

3. After problem is reproduced, then stop server side logging in order to free the lock on the server logs, then provide the HBroker.log and all HServer.log logs for the period of the test. 

C:\Program Files\CA\SCM\Log 

 

HOW TO ENABLE DEBUGGING 

To generate server side log files for analysis: 

Customer can use the HLoginMon utility with the hdbgctrl interface to quickly start and stop server side logging or use the primitive hdbgctrl commandline to do same. 

 

GUI METHOD 

HLoginMon utility can be obtained free from here after logging into 

support.ca.com: https://communities.ca.com/thread/241745212 

The user's guide provided in the HLoginMon installation provides instruction on how to start/stop logging against a specific Harvest user. 

 

COMMAND LINE METHOD 

If prefered method is to enable debugging from command line: 

An example of using hdbgctrl commandline from the Harvest server box... 

hdbgctrl -b broker -usr harvestuser -pw passwd hserver:on:5:all:ClientMachineNameGoesHere (starts logging) 

reproduce your problem 

hdbgctrl -b broker -usr harvestuser -pw passwd hserver:off:5:all:ClientMachineNameGoesHere (stops logging)