Previous Topic: clean_sadmin-Remove Static Data and MIBs

Next Topic: install_agents-Install or Remove Agents or Services

exagent-Control the Agent Technology Example Agent

Valid on Windows, z/OS

exagent starts and controls the Agent Factory example agent.

Note: See the Installation Guide for a description of how to build the example agent.

Windows

install-path\agents\samples\exagent

z/OS JCL

&CAI.MFNSM.CAW0JCL(EXAGNT)

This command has the following format:

exagent start [--instance=instName] [-t topDirectory] [-i interval] [-l log_level] [-f logfile] [-s]

Sample z/OS JCL

This sample JCL requests the cmd /tmp instance of exagent to be started with /tmp as top directory under which all monitored directories must be found. It also requests a log level 4 with the log messages sent to the LOGFILE DD statement.

//stepname   EXEC PGM=EXAGENT,
 // PARM='/ debug --instance=/tmp -t /tmp -l 4 -f //DD:LOGFILE'
//LOGFILE  DD SYSOUT=*

Comments

If the --instance and -t parameters are not specified, then exagent will run without MIBMUX.

If you decide to run multiple instances of exagent, then specify the same names for the --instance and -t parameters in order to get consistent information displayed by the awservices status command and other commands such as orbctrl and agentctrl.

This command has the following options:

--instance=instName

Specifies the instance name as it will be known by awservices. This name will appear on the display of the awservices status command.

-t topDirectory

Specifies the top level directory under which all monitored directories must be found. This is the real instance name for the agent. It is used as instName parameter on the AWF_RegInstance function call.

-i interval

Specifies the interval for the main exagent task in seconds.

-f logfile

Specifies the name of the file where log messages are sent.

-l log_level

Specifies the message level for log messages.

-s

Uses the store instead of Register for Get Agent.