How dynamic linking works

Understanding how dynamic linking works, and the components involved, helps you use dynamic linking effectively.

Dynamic linking involves the following components:
  • A source workspace that provides the context (attribute values) for the link
  • A target workspace that contains a terminal emulator view associated with a query and a suitable connection and navigation script
  • A dynamic link from the source workspace to the target workspace that specifies the attribute values from the source workspace that are used for navigation to the appropriate screen.
  • A query that retrieves additional required values from the OMEGAMON® agent to be used by the script associated with the terminal adapter
  • A script that uses the values from the query and the link to connect to OMEGAMON for MVS session and navigate to the appropriate screen

When a dynamic link on a row in the source workspace is selected, the link picks up the values of the attributes specified in the link definition from the row and passes them to the target workspace. The query associated with the terminal view in the target workspace is executed to obtain connection information. The query is processed by the monitoring agent and discovered or configured information is passed back to the terminal emulator.

When a Tivoli Enterprise Portal user attempts to connect to a session, a TN3270 logon window prompts for a user ID and password. These credentials can be saved for the duration of the Tivoli Enterprise Portal session so they will not have to be prompted for again. They are lost when the Tivoli Enterprise Portal client is terminated. If the script associated with the session is modified to include the user ID and password for the OMEGAMON session, or if no user ID or password is required for the logon, the window can be dismissed without them.
Note: The stored user credentials are associated with the specific OMEGAMON session being linked to, as defined by its host name, port number, LU Group and APPLID. If the same terminal emulator (and workspace) is used to connect to a different classic instance, the user is prompted again for another user ID and password.

After a user clicks OK to close the prompt, the startup script file is run. The script file retrieves all the query values, link values, and any values modified during logon and uses this information to drive the 3270 interface to connect to the APPLID returned in the query and to navigate to the appropriate display in OMEGAMON for MVS.

The connection values for the OMEGAMON for MVS session (host name, port number, Logical Unit (LU) Group and APPLID) are discovered by the monitoring agent. However, these values can be overridden using PARMGEN. For more information about configuring OMEGAMON for MVS parameters, see the IBM Z OMEGAMON AI for z/OS: Parameter Reference. The host to which the TN3270 session connects must have an active TN3270 listener. By default, that host is assumed to be the LPAR on which the monitoring agent is located. If there is no active listener, the address of an LPAR that does have an active listener must be specified. The default port number for the Telnet listener is 23. This value can also be overridden. The Dynamicto 3270 (Classic) linking feature requires the VTAM® UNIX System Services screen to accept a LOGON APPLID() DATA() command. If the default Telnet UNIX System Services screen does not accept this command, the name of a Logical Unit (LU) group that does accept it must be provided. The TN3270 session will be joined to that LU group. The default values are overridden on the Add Runtime Environment (3 of 3) or Update Runtime Environment (3 of 3) panel.

The default values or the override values used for the session are displayed at the TN3270 logon and can be modified for an individual TN3270 session.

The terminal connection terminates after 5 minutes of inactivity or when you end this Tivoli® Enterprise Portal work session.