z/OS MVS Planning: APPC/MVS Management
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Creating Side Information

z/OS MVS Planning: APPC/MVS Management
SA23-1388-00

Side information contains the translation of a symbolic destination name that can be used on outbound allocate requests, or by APPC/MVS servers, when registering to receive inbound conversations. Programs specify a symbolic destination name that represents the TP name, logon mode, and partner LU on the Allocate or Register_for_Allocates call.

Side information consists of the following sections:

Figure 1. Side Information Key
Symbolic Destination Name ──────→ DESTNAME(sym_dest_name)
Figure 2. Side Information Data
TP Name ────────────────────────→ TPNAME(name)
Logon Mode Name ────────────────→ MODENAME(mode)
Partner LU Name ────────────────→ PARTNER_LU(name)
DESTNAME(sym_dest_name)
Identifies the 1- through 8-character symbolic destination name for the partner TP.
TPNAME(name)
Indicates one of the following:
  • 1- through 64-character name of the transaction program. Valid characters are those from the 00640 character set and the Type A character set. For descriptions of these character sets, see Character Sets. If the name will be used in the APPC/MVS administration dialog or in DISPLAY commands, do not use an asterisk (*) in the name.
  • 2- to 4-character name of the transaction program (if the transaction program is an SNA service TP). Although the names can be 2 to 4 characters, they are normally 4 characters in length. To specify the SNA service TPNAME in the APPC/MVS administration utility, you must map the 2- to 4-character SNA TPNAME into the following 7- to 9-character format:
       ¬X'nn'yyy
    where:
    nn
    is two digits that represent hex characters from 00 through 3F, excluding 0E and 0F. These two digits correspond to the first character in the SNA TP name.
    yyy
    is 1 to 3 Type A characters. A listing of Type A characters is in Character Sets. These 1 to 3 characters correspond to the last 1 to 3 characters of the SNA TPNAME.

Figure 3 shows how the 4-character SNA TPNAME 37,C1,C2,C3 maps into the APPC/MVS administration utility TPNAME ¬X'37'ABC. Because the last 3 characters of the SNA TPNAME, C1,C2,C3, are TYPE A characters, you can convert them using the listing in Character Sets. The first character in the SNA TPNAME,37, is nondisplayable, however, so you must map the first character into the fourth and fifth characters shown in Figure 3.

Figure 3. Mapping an SNA TPNAME into an Administration Utility TPNAME
Mapping an SNA TPNAME into an Administration Utility TPNAME
MODENAME(mode)
Names the logon mode for the SNA session connecting the local LU with the partner LU. If no mode name is specified, a default mode name might be available. For information about when defaults are available, see Specifying a Logon Mode for a Conversation.
PARTNER_LU(name)
Identifies the 1- through 17-character name of the partner LU where the partner TP resides. If no partner LU name is specified, APPC/MVS assumes the TP resides in the local LU.
This value can be one of the following:
  • Network LU name only (1-8 byte Type A character string)
  • A VTAM® generic resource name (1-8 byte Type A character string). This value should not be a generic resource name if any APPC/MVS servers use the LU value from a side information entry for a Register_for_Allocates call. Register_for_Allocates accepts only a specific LU name.
  • Combined network_ID and network LU name (two 1-8 byte Type A character strings, concatenated by a period): network_ID.network_LUname. The network LU name can be a VTAM generic resource name.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014