Information
Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

LOGON


This command establishes a session between an EXEC and a VTAM application and supplies the first screen output to the EXEC.

See Interacting-with-VTAM-applications-with-OSPI for more information about using this command and OSPI.

Command

Parameters

LOGON

[APPLID|ACB(applicationName)]

[DATA|USERDATA(userdata)]

[PREFIX(OSI|Prefix)]

[SESSION(sessionIdentifier)]

[REQACB(ACBName)]

[LOGMODE(D6327802|logmode)]

[DEBUG|NODEBUG]

[NORECEIVE]

The following table describes the parameters:

Parameter

Function

Notes

APPLID|ACB

ACB name of the application (to establish a session with) as it is specified in SYS1.VTAMLIST

Required if the SESSION parameter is not specified. 1-8 alphanumeric characters.

The application must be active and accepting LOGONs.

DATA| USERDATA

Any data passed to the application during logon processing

Maximum length is 80 characters.

PREFIX

OSPI variable name prefix

The prefix must be exactly 3 characters long. The first character must be an alpha character.

SESSION

Session identifier of a previously disconnected session

When specified, this parameter indicates that no new session should be established but an existing session reconnected.

REQACB

ACB to use to communicate with the application

Since the ACB name used will also represent the terminal name when connecting to an application, this parameter may be used for applications that allow access only from specific terminals. If this ACB is unavailable for whatever reason, the command will fail.

LOGMODE

logmode name to use when requesting a session

The logmode value determines the screen characteristics to emulate (in particular, the virtual screen size).

DEBUG|NODE- BUG

Controls whether or not execution of all activities against the resulting session will execute in DEBUG mode

When specified, many messages about internal activities are generated and buffer snaps are taken.

NORECEIVE

Used when logging on to an application that does not display an initial panel before allowing the terminal user to enter data

n/a

Condition codes are listed in the following table:

Value

Description

0

Command was executed successfully.

4

A LOGON with the SESSION parameter was issued but failed to reestablish the session.

8

Syntax error occurred or LOGON failed.

Example

This example command establishes a session to the application BTSO and passes the string SYSUSER to it. All control variables have the prefix TSO and no debugging messages are generated.

/* REXX */
"IMFEXEC LOGON APPLID(BTSO) DATA(SYSUSER) LOGMODE(D6327803) PREFIX(TSO)"
"IMFEXEC VGET TSOSESS LOCAL"

CLIST example:

IMFEXEC LOGON APPLID(BTSO) DATA(SYSUSER) LOGMODE(D6327803) PREFIX(TSO)
IMFEXEC VGET TSOSESS LOCAL

Following the successful execution of this LOGON command, the variable xxx SESS (where xxx represents the session prefix) must be retrieved from the local variable pool. If it is not retrieved, you cannot perform further commands against this session.

The token contained in this variable uniquely identifies the session. The default name for this variable is OSISESS. Refer to Interacting-with-VTAM-applications-with-OSPI for more information.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Automation 8.3