TS_EXECUTE
The TS_EXECUTE activity executes a specified routine in an aXes terminal operation script. Refer to the LANSA Composer guide for more information about aXes terminal operations scripts.
INPUT Parameters:
AXHANDLE : Required
This parameter must specify the connection handle value that identifies the aXes terminal server session upon which the aXes terminal operations script should operate. The connection handle value is returned by the TS_CONNECT activity.
AXSCRIPTFILE : Required
This parameter must specify the full path to a file that contains the aXes terminal operations script routine to be executed. The aXes terminal operations script must be in a comma-separated format as described in the LANSA Composer guide.
AXROUTINE : Optional
This parameter may specify the name of a routine in the aXes terminal operation script. If not specified, a blank routine name is assumed. If your script does not contain named routines you do not need to specify this parameter.
AXRELOAD : Optional
You may specify YES in this parameter to force the aXes terminal operations script to be re-loaded from the file specified in the AXSCRIPTFILE parameter. In normal operation, the activity loads an aXes terminal operations script file once and then uses the loaded copy if the same script is specified again in subsequent TS_EXECUTE activity executions. However, if your processing sequence "generates" the script file in response to other inputs (by using a Transformation Map, for example), then you may need to force the TS_EXECUTE activity to reload the script after your processing sequence has changed it. In that case you should specify YES for this parameter. If not specified, the default for this parameter is NO.
OUTPUT Parameters:
AXSCREEN :
Upon successful completion this parameter contains the resulting aXes 5250 screen name or signature. The screen name is the user-defined name if an aXes project name was specified on the TS_CONNECT activity and a name was assigned to the screen. Otherwise the screen signature is returned.