Session Management

The LISTE (and its synonym, LISTU) command will display the engines currently in use by the OpenEngine Server. The current engine used by the CTO will be designated by an asterisk ("*").

The WHO command will return information about the engine currently used by the CTO.

The VERSION command will return the current version number of the CTO.

The RESET.ENGINE and LOGOFF commands will allow administrative users to reset any engine that may be performing improperly or that you otherwise wish to shut down. Note that these commands can only be run by users with administrator privileges.

By default, the RESET.ENGINE command will operate only on "asynchronous" engines (i.e., those that are being used for web interaction). To reset other CTO sessions, you must specify the "U" option when invoking the command ("RESET.ENGINE (U"). You will be prompted for the name of the session to reset; press RETURN for all engines, or

the name of the application you wish to reset. You must also provide the supervisor password as defined for that OpenEngine Server (by default, this is REVSOFT).

The LOGOFF command will prompt the user for the name of the process to log off, and the OpenEngine Server supervisor password. It will terminate the CTO or asynchronous sessions that have the specified process name.

The LOGTO and LOGTOX commands will allow you, from TCL, to leave the current application and enter a different application. You may either specify LOGTO by itself, or use the following syntax:

LOGTO <application>{,<username>,<password>}

You will be prompted for any parameters you do not supply on the command line. Note that if you specify an application that doesn't exist, or you incorrectly enter your username or password, you will be in a "logged off" state, and must actually log off and reconnect to resume.

If the application, username, and password are the same, you may use the LOGTOX command. LOGTOX will automatically use the specified application name to fill in the username and password parameters. Use the following syntax:

LOGTOX<application>

For example, entering the command

LOGTO MYAPP,MYAPP,MYAPP

The LOGON command allows you to create a ‘background’ or ‘phantom’ process. You may either specify LOGON by itself, or use the following syntax:

LOGON <processed>{,<application>{,<username>{,<password>}}}

You will be prompted for any parameters you do not supply on the command line.

You must specify a “processID” so that you might uniquely identify the phantom process, and the name of the application and user you wish to invoke. There MUST be a “login process” associated with the application or user. The “phantom” process will run the login process, and any other procedures the login process may call. Once the login process has terminated, the ‘phantom’ process will be reset. Note that the phantom process CANNOT request any

input (unless that request is satisfied by DATA statements); any INPUT statement will cause the phantom process to terminate.

The OFF command indicates to the CTO that you are finished with the current application. You will be returned to the "login" screen of the revcmd program.

The QUIT command indicates to the CTO that you are finished with the current application and the CTO environment in general. The revcmd program will terminate.