AS400 Execution Agent Installation
Two AS/400 Execution Agents are available for installation.
1) The native AS/400 agent software is distributed in “Save File Format” (or SAVF) and can be restored using the RSTOBJ command into a library.
Once restored you can execute the ABATINST program to perform the actual agent installation.
For example:
CALL ABATINST to interactively install the agent
CALL ABATINST PARM(‘-s’ ‘-d NEWLIBRARY’) to perform a silent installation
Where:
‘-s’ is used to indicate a silent install
‘-d NEWLIBRARY’ is used to indicate the library to install the agent. If –d is omitted, ABATINST will create a library named ABATEMGR and install the agent there.
2) The other agent uses the PASE facility which allows a UNIX environment to be emulated within the AS/400 system. The installation of the PASE-based agent follows the same procedures outlines in the Unix/Linux Installation Section. The information below applies to the native AS/400 agent only.
Native AS/400 Commands
After installing the agent you can start it by invoking the ABATSTART program, as follows:
CALL ABATSTART to perform a normal startup OR
CALL ABATSTART PARM(-g’) to perform a verbose trace startup
When the agent starts you can see the process in the batch jobs list.
By default, the Native AS/400’s QBATCH Job Queue is set to have a maximum active number of jobs to run on a queue to 1. Abatemgr consumes one queue slot. In order to be able to run Jobs, the maximum active number of Jobs must be set to 2 or more.
The command to change the QBATCH Job Queue to allow multiple Jobs is as follows:
CHGJOBQE SBSD(QBATCH) JOBQ(QBATCH) MAXACT(2)
The above command changes the value to 2.
When running jobs using the native AS/400 agent, ActiveBatch jobs are executed using the same AS/400 batch jobs facility. So any jobs that run will appear in that list as well.
Normally the ActiveBatch Execution Agent is not stopped. However, if you do need to terminate it, the ABATKILL program can be used.
For example:
CALL ABATKILL
Wait until no jobs are executing on the target machine before invoking the command.
Finally to uninstall the native agent you can run the ABATUNINST program.