TS_CONNECT
The TS_CONNECT activity is used to connect to an aXes terminal server and signon the 5250 session using the server identification and user credentials provided.
It is possible to use more than one aXes terminal server session at a time in your processing sequence. The value of the AXHANDLE output parameter identifies the session created by this instance of the TS_CONNECT activity. The same value must be specified as the AXHANDLE input parameter value for all subsequent aXes terminal server activities (such as TS_SETBYNAME or TS_SEND) that are to operate on the same terminal server session.
NOTE: The processing sequence containing the TS_CONNECT activity becomes ineligible to be restarted in the event of any failure for the duration of the aXes terminal server session - that is, until the TS_DISCONNECT activity is executed.
INPUT Parameters:
HOST : Required
This parameter must specify the host name or IP address of the machine hosting the aXes terminal server to which you wish to connect.
PORT : Optional
This parameter may specify the port number to be used to connect to the aXes terminal server. If not specified, a default value of 80 is assumed.
USER : Required
This keyword must specify the user name used to connect to the aXes terminal server. This must be the name of an authorised i/OS user profile.
PASSWORD : Required
This parameter must specify the password for the user name specified in the USER keyword.
AXPROJECT : Optional
This parameter may be used to set the aXes project to use for this session. A project contains user assigned definitions of screens and fields. For example, you can assign a name to a screen or a field, and later use that name to refer to the screen or the field in other aXes terminal server activities. Although aXes projects can either be stored in a file on the file system or on the aXes server, you may only specify here an aXes server-based project.
AXEXTENDEDTRACE : Optional
If you specify YES for this parameter, LANSA Composer will use additional LANSA Integrator aXesTerminalService tracing options that will create additional Java Service Manager (JSM) tracing. The additional tracing will include terminal session screen captures at appropriate points as well as creating an additional aXes-specific trace file in the JSM trace directory. The additional tracing may help in diagnosing interactions with the aXes terminal server and so may be useful in the design and testing stage of your LANSA Composer solution. However, there is additional processing overhead associated with the the extra tracing and you may wish NOT to use it in a performance-sensitive production environment. The effect of this parameter is subject to standard LANSA Composer logging and tracing system settings being in effect. The default for this parameter, if not specified, is NO.
OUTPUT Parameters:
AXHANDLE : Required
If successful, the value of this output parameter identifies the session created by this instance of the TS_CONNECT activity. The same value must be specified as the AXHANDLE input parameter value for all subsequent aXes terminal server activities that are to operate on the same terminal server session.
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 in the AXPROJECT parameter and a name was assigned to the screen. Otherwise the screen signature is returned.