|
Documentation Tabs |
Job |
Job - Includes |
|
Job - ExecutionThe script is processed in a specific way in the object type "Job". Depending on the JCL (Job Control Language) and the script elements, an executable job is generated for the respective target system and transmitted via file transfer.
The AE Script (if existing) and the JCL lines are processed and subsequently, the JCL is sent to the target system. AE Script is never sent to the target system.
On Windows the User Account Control (UAC) should be turned off to prevent errors because of missing permissions.
The databaseA database is an organized collection of data including relevant data structures. agent regularly attempts to establish a connection to the database if its first attempt was not successful. The administrator can define this interval in the INI-file parameter connect=. The job remains in status "Active" during these attempts to establis a connection.
The job also remains in status "Active" if the agent is not able to establish a connection because the login data specified in the Login object is incorrect. It must be canceled manually either in the Activity Window, using the script function CANCEL_UC_OBJECTor directly in the job by monitoring the maximum runtime.
Keep in mind that it is not possible to end commands the agent has been processing in the database at the moment job canceling is initiated. The JDBC interface does not provide this function. Jobs can only be canceled between two commands. Therefore, the agent waits until a command which is just being processed is finalized and cancels the job afterwards. Use the functions of your database Server to cancel ongoing commands.
The administrator can specify the parameter login_check=yes in the MPE agent's INI file. The passwordA secret combination of characters for a Automation Engine user. defined in the Login object is then checked. For reasons of security, Automic recommends using this setting. Login_check=no only checks the user nameName of the Automation Engine user..
The user specified in the Login object also owns the job and report file. The administrator can assign authorizations for both files using the agent's INI-file parameters JobFileMode= and ReportMode=.
TThe administrator can specify the parameter login_check=yes in the UNIX agent's INI file. The password defined in the Login object is then checked. For reasons of security, Automic recommends using this setting. The setting Login_check=no only checks the user name.