Knowledge Base > Automation Engine and Target Systems > OS/400 > Agent - Commands

Agent - Commands

The agentA program that enables the de-centralized execution of processes (such as deployments) on target systems (computers or business solutions) or a service that provides connectivity to a target system (such as for databases or middleware). An agent is also an object type in the Automation Engine. [Formerly called "Executor."] See also: host is supplied with additional programs and commands. They can be used to start or end the agent quickly and easily without creating a CL routine. A program for generating the message library is also supplied. It is helpful if an error occurs.

Note that you must use the latest agent of version 9.00A. The library that includes the program files must have been added to the system's library listShows entities in a grid view. See: Installation Guide of the OS/400 Agent.

Starting the Agent

Supplied objects:
Program: STRUCAGENT
Command: STRUCAGENT

Command for starting any AE agent without creating a CL routine. The library that includes the agent must be specified for this purpose. The agent's INI file must be specified either for the IFS or the QSYS file system. It replaces the UCEX_RUN routine.

Parameters:
LIB(library)
MBR(QSYS INI file) or PATH(IFS path and INI-file name)

Examples:

STRUCAGENT LIB(UC4) FILE(UC4/INI) MBR(UCXJO41)
Starts the agent from the UC4 library by using the INI file UC4/INI(UCXJO41).

STRUCAGENT LIB(UC4) PATH('/userIn the Automation Engine, a user is an instance of a User object, and generally the user is a specific person who works with Automic products. The User object is assigned a user ID and then a set of access rights to various parts of the Automation Engine system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and ARA web application object rights. You can manage all these centrally in the ECC user management functions. See also, Unified user management./uc4/ucxjo41.ini')
Starts the agent from the UC4 library by using the INI file ucxjo41.ini which is available in the IFS file path /user/uc4/.


Ending the Agent

Supplied objects:
Program: ENDUCAGENT
Command: ENDUCAGENT

Ends the agent that has been started from a particular library either immediately or in a controlled manner. You can use it instead of the UCEX_END routine.

Parameters:
LIB(library)
OPTION(end)

Examples:

ENDUCAGENT LIB(UC4) OPTION(*CNTRLD)
Ends the agent that has been started from the UC4 library in a controlled manner. This command has the effect that the agent obtains an end signal which is processed soon.

ENDUCAGENT LIB(UC4) OPTION(*IMMED)
Cancels the agent that has been started from the UC4 library. This command corresponds to the ENDJOB command. The specified agent is searched in the system and ends immediately.


Generating the Message Library

Supplied objects:
Program: MAKEMSL
Command: GENUCMSL

The command GENUCMSL can be used to convert an MSL file that is stored in the IFS file to a physical message library. The agent can then use the generated message library. This procedure is not necessary for installing the agent but it is helpful for updating or repairing the message library (if an error occurs).

Parameters:
PATH(IFS path and file name)
FILE(QSYS target file)

Examples:

GENUCMSL PATH('/tmp/uc.msl') FILE(UC4/MSL)

Converts the file uc.msl which is provided in the IFS path '/tmp/' to the file UC4/MSL. The number of imported message records is output:

Processing completed.
Lines processed '34579'.
Imported '11607' english messages.
Imported '11607' german messages.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2016 Automic Software GmbH