Cisco Cisco Workload Automation 6.3 Guida Utente
21
Cisco Systems, Inc.
www.cisco.com
4
Using the OpenVMS Agent
Overview
Once you have completed the configuration of the OVMS agent, you can create, run and monitor OVMS jobs from CWA.
Every OVMS job that is created is assigned a unique ID number by CWA. This number is called the Job Number and is
assigned as soon as CWA includes an OVMS job in the schedule.
Every OVMS job that is created is assigned a unique ID number by CWA. This number is called the Job Number and is
assigned as soon as CWA includes an OVMS job in the schedule.
Note:
This identification number differs from the job number that OVMS assigns to each job.
The OVMS job number is called the External ID in CWA and is displayed in the
Ext ID
column of the
Job Activity
pane.
The Job Number is also displayed in the
Job Activity
pane under the
Job No.
column.
This chapter covers these topics:
Defining a Job
Defining OVMS jobs in CWA is very similar to creating other jobs in CWA. There is a specific menu option in the
Job
pane
context menu that pertains to OVMS. In the context menu, select
Add Job>OVMS Job
.
There are three types of OVMS executables that can run as CWA jobs:
Command files
(xxx.com) – similar to shell scripts in UNIX or .bat files in Windows
Compiled files
(xxx.exe) – binary executable files that have been compiled/assembled
Commands
– system type of commands like “show time” or “show system”
The three types of CWA OVMS jobs–Batch(JobQ), job, and command jobs–relate to specific executable types and how
they are presented to OVMS to run:
they are presented to OVMS to run:
—.com files and .exe fils can run as ‘Batch(JobQ)’ jobs.
—.com files and .exe files can run as ‘job’ jobs.
—system commands and .com files can run as ‘command’ jobs.
The job definition dialogs for these three types of OVMS jobs may share some of the same or similar text fields but each
type has its own definition to define the unique characteristics of each type and control how it is presented to OVMS for
execution.
type has its own definition to define the unique characteristics of each type and control how it is presented to OVMS for
execution.