Unable to Run iDash Commands in Autosys Job
search cancel

Unable to Run iDash Commands in Autosys Job

book

Article ID: 74351

calendar_today

Updated On:

Products

iDash Workload Automation

Issue/Introduction

We are trying to use the iDash CLI commands in our Autosys jobs to create reports. When we run the job, the job fails.

insert_job: TestBatchJobs_iDash_Run_Report  job_type: CMD
command: idgenxls –t run.report –n TestBatchJobs –f job_run_report.xls –u rpt_creator
machine: redhat-1136sp6
owner: [email protected]
permission:
date_conditions: 1
days_of_week: all
start_mins: 59
std_out_file: "/tmp/TestBatchJobs_iDash_Run_Report.out"
std_err_file: "/tmp/TestBatchJobs_iDash_Run_Report.err"
alarm_if_fail: 1
 

Environment

Workload Automation AE r11.3.6+
Workload Automation iDash r12.0+

Cause

There are various errors that can appear in your std_err_file. Below outlines the cause of the error and what the error looks like:

1. The CLI has not been enabled.
CLI disabled

2. The job owner doesn’t have permission to logon to the server where the CLI utilities are installed.
com.ca.idash.core.exception.IdashException: Invalid CLI User:root

3. The user specified in the -u parameter is not a valid iDash user.
Not authorized to use -u option:rpt_creator
 

Resolution

1. The CLI has not been enabled.
  • In the Admin Tool -> Security -> CLI Authentication tab, make sure the CLI Enabled checkbox is checked off. In the IP/Domain/Host tabs, make sure the AE server is included in all three lists (wildcards are acceptable).

2. The job owner doesn’t have permission to logon to the server where the CLI utilities are installed.

  • Make sure the job owner is a user that can logon to the server where the command will be executed. Autosys does not sudo to any user accounts - it assumes the job owner has direct logon permissions.
  • If the job owner cannot logon to the iDash server to run the command, install and configure an iDash client on the Autosys server.

3. The user specified in the -u parameter is not a valid iDash user.

  • The iDash user specified in the -u parameter needs to exist in the appropriate authenticating repository.

    • If you are using iDash to authenticate users, then the user should be added in the Admin Tool.
    • If you are using EEM to authenticate users, then the user should be added to EEM.
    • If you are using Active Directory to authenticate users, then the user should be added to AD.