Terminals can be created as sign-on capable or sign-on incapable, depending both on the API function that is used to create them and the type of CICS server on which they are installed. The sign-on capability of a terminal can be specified by one of the following methods.
Use CICS_EpiAddExTerminal and set the sign-on capability parameter in the CICS_EpiAttributes_t structure.
Set the sign-on capability parameter when constructing a CclTerminal class object.
Use the SetTermDefns method of the Terminal COM class.
Set the sign-on capability parameter when constructing an EPIRequest object via the addTerminal or addTerminalAsync method.
Create a Terminal object using the default Constructor, then use setSignonCapability, or create a Terminal object using the extended Constructor. If a terminal is in disconnected state (that is, has been disconnected, or never connected) calling setSignonCapability allows you to change the sign-on capability for the terminal and changes the terminal type to extended. When you connect, you connect an extended terminal with that sign-on capability. Setting the sign-on capability while a terminal is connected does not alter the connected setting; the setting is stored.
The sign-on capability of the installed terminal is returned in the terminal attributes. This will be set to SIGNON_UNKNOWN if the server does not return a sign-on capability parameter in the CTIN response.