There are some peculiarities that must be considered when you use file events with an OS/400 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.
You must start OS/400 agents of version 9.00A or later as a multi-threaded process in order to use the newfile eventAction that is triggered if particular conditions apply. It can be an Automation Engine object type or an entry in a Policy Orchestrator EventBase.. Doing so requires the agent's JOBD parameter ALWMLTTHD to be set to "YES".
The new file event is handled in threads which means that you can only use the following file systems:
IFS file system
IFS (Integrated File System) is a UNIX-based file system. IFS files must always be specified with an absolute path (starting from the root) and a final file name.
If the file specification includes a / character, the agent assumes that an IFS file is concerned.
For example:
/home/AE/test.txt
The wildcard charactersThese are placeholders for characters when you specify filters. ? stands for exactly one character, * for any number of characters. * and ? can be used to process partially qualified file events. They can be used as necessary within the path and/or file name.
In an individual file event, the path and file name are not case-sensitive. Therefore, the following two specifications are identical:
/home/AbC.txt
/HOME/ABC.txt
Wildcard file event paths are case-sensitive. The following two specifications differ from each other:
/home/AB*
/home/ab*
(Note: An exception is QOpenSys, here wildcard file event paths are not case-sensitive.)
See also:
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |