The AE databaseA database is an organized collection of data including relevant data structures. 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 can be used to process Stored Procedures for MS SQL.
The statement RETURN can return a number. This return codeThe value that represents the result of tasks and script functions. can then be written to the jobAn Automation Engine object type for a process that runs on a target system. reportA report provides more detailed information about a task's execution or a component. (see example below). The name of the stored procedure is ANGTEST.
SQL_SET_STATEMENT_TERMINATOR TERM='!';
DECLARE @result int;
EXEC @result = ANGTEST;
select @result;!
A separator other than the semicolon is automatically used because this character has already been used within the statement.
The job ends normally regardless of its return code. If you intend to change a job's end statusThis represents the condition of a task (such as active, blocked, generating)., you can read the corresponding value in the job report and react to it using :MODIFY_STATE.
The statement PRINT facilitates the output of messages to a 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. (example: DBCC CHECKDB). These messages are also written to the job report. Job execution continues as usual.
Causes the job to be aborted. The error message is written to the activation report.
See also:
Form tab
Process tab
PREP_PROCESS_REPORT
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2016 Automic Software GmbH |