Accessing bridge facility properties

The user transaction can retrieve information about its principal facility (the bridge facility) from the EIB or by using INQUIRE and ASSIGN commands, in exactly the same way that it does when running normally, where the principal facility is a real 3270.

For example, the TERMID can be obtained from EIBTERMID or from an ASSIGN FACILITY, INQUIRE TASK FACILITY or INQUIRE NETNAME command, and the NETNAME can be obtained with ASSIGN NETNAME or INQUIRE TERMINAL.

You can use the INQUIRE BRFACILITY command to obtain information about any bridge facility, identified by its facilitytoken, but all other INQUIRE commands return only information about the bridge facility that is the principal facility of the transaction issuing the command. To other transactions, a transaction running in a bridged environment appears to be a non-terminal transaction, and an INQUIRE TERMID against a bridge facility TERMID issued by another transaction will result in TERMIDERR. INQUIRE NETNAME and INQUIRE TASK behave similarly.

Bridge facilities do not appear in response to INQUIRE TERMINAL browses.

All keywords of ASSIGN and INQUIRE are supported and return the values that have been set for the bridge facility from the FACILITYLIKE terminal definition, or that have been set during the execution of the transaction.

Some keywords return values fixed by CICS® for the bridge environment. These are:

Table 1. INQUIRE TERMINAL values
Keyword
Returned value
ACQSTATUS
ACQUIRED
ACCESSMETHOD
VTAM
CORRELID
blanks
EXITTRACING
NOTAPPLIC
LINKSYSTEM
blanks
MODENAME
blanks
REMOTENAME
blanks
REMOTESYSTEM
blanks
REMOTESYSNET
blanks
SERVSTATUS  
INSERVICE
TCAMCONTROL
X'FF'
TERMSTATUS
ACQUIRED
TTISTATUS
YES
ZCPTRACING
NOZCPTRACE
Note: VTAM® is now the z/OS® Communications Server.
Table 2. INQUIRE TASK values
Keyword
Returned value
FACILITY
the bridge facility name
FACILITYTYPE
TERM or TASK
STARTCODE
S,SD,TO,TP