Verify that on the host where the report will be executed that the user executing the report has the correct API environment defined with the Environment Service.
Environment Service

If using user/password to login, verify that the user can login with the Session Service.
Session Service

If using an API token to login, there is no need to use the Session Service to verify.

Verify that the report defined in Control-M Reports can be executed manually.
Example syntax:  ctm reporting report:: get REPORTNAME -o OUTPUTFILE
Example command for Unix/Linux:  ctm reporting report:: get My_Report -o /tmp/myreport.csv
 

To run the report from a Control-M job:

• Take the above command that worked manually and add it to an OS Job
• As desired, add a date and/or time stamp to the file name of the report.  The relevant Control-M System Variables can be used in the file name specified after the "-o" option in the Control-M job.
  • The Control-M System Variables, including those related to time and date are covered in the online documentation at the following link: https://documents.bmc.com/supportu/9.0.21.200/en-US/Documentation/Variables.htm

For example:

 
 
Verify that the Run As user is defined in the CCM or Web Configuration (when needed)

Linux/Unix:
Verify that the Run As user is either the Control-M/Agent user, or if another user that it has CLI installed.

Windows:
Verify that the Agent is configured with the "Login as User" parameter set to Y, and that this user can manually run the report



This information is summarized in the following video:


 

Additional Information:
Customers viewing this solution may find value in the following self-help Connect with Control-M video.