The CallAPIInterface de programmation pouvant être exécutée en direct ou à partir d'un autre programme, afin d'exécuter un Script dans le système AE. can be used to process scripts in the AE system from your own Cobol programs.
The delivery directory contains sample programs that provide a detailed description of how a scriptEgalement un type d'objet distinct dans l'Automation Engine. activation can be implemented.
General
Scripts are always activated with the following steps:
You can log on to several AE systems at the same time and process various scripts. In this case, a Dialog license is used for each connection.
Call
Call the CallAPI using the command CALL UCCALL3. Return code 0 is supplied if the action"Voir ""Action en cas de non-respect (AWI Service Orchestrator)""." was successful or a message number if an error occurred.
Description |
Call |
---|---|
Logging on to the AE system |
CALL UCCALL3 USING structure, login data, connection Format for login data: Format for connection data for the communication process: |
Activating a script |
CALL UCCALL3 USINGstructure, script |
Logging off the AE system |
CALL UCCALL3 USING structure |
Variables
The supplied sample program explains the structure AE-RECORD. It contains the following variables:
Data type |
Description |
|
---|---|---|
UC-OPERATION |
PIC X(4) |
Operation code This variable must be set if the universal function should be used. Allowed values: |
UC-ERROR-CODE |
PIC X |
The error code in cErrorCode is automatically set and can contain one of the following values: " " - no error occurred |
UC-INTERFACE-NR |
PIC X(3) |
The interface number must always contain the value 3. |
UC-SYSTEM-NAME |
PIC X(8) |
Name of the AE system to which the connection should be established |
UC-TIMEOUT |
PIC 9(4) COMP-4 |
Time in seconds during which the CallAPI waits for an AE system response |
UC-LANGUAGE |
PIC X |
Language in which messages are output |
FILLER |
PIC X(2) |
Not used |
UC-FLAG1 |
PIC X |
Depending on the specified value, this flag results in one of the processing options listed below: "CALL_FLAG1_INI_SERVER" - connection to communication process is retrieved from INI file |
FILLER |
PIC X(2) |
Not used |
UC-OUTPUT-LEN |
PIC 9(8) COMP-4 |
Not used |
UC-RUNNR |
PIC 9(8) COMP-4 |
|
UC-RETURN-CODE |
PIC 9(8) COMP-4 |
Return code of script execution |
UC-MESSAGE-TEXT |
PIC X(256) |
Variable message part explaining the return code's value |
UC-PRT-INI |
PIC S9(8) |
For internal CallAPI processing only |
UC-HND-LOG |
PIC S9(8) |
For internal CallAPI processing only |
UC-HND-TRC |
PIC S9(8) |
For internal CallAPI processing only |
UC-HND-HLP |
PIC S9(8) |
For internal CallAPI processing only |
UC-POINTER |
PIC S9(8) |
For internal CallAPI processing only |
FILLER |
PIC X(12) |
Not used |
UC-INIFILE |
PIC X(45) |
Path and name of INI file |
See also:
About the CallAPI