z/OS DFSMS DFM Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Using the APPC/MVS LUADD Definition

z/OS DFSMS DFM Guide and Reference
SC23-6848-00

Use the APPC/MVS LUADD definition to define the start parameters in APPCPMxx. With LUADD parameters, you can add, modify, and delete LU information. You can also change the defined names for both the TP profile and the side information data sets.

Figure 1 is an example of the basic LUADD definition that should be included in APPCPMxx. This example can be found in system SAMPLIB member GDEAPPC (for example, SYS1.SAMPLIB(GDEAPPC)), or see GDEAPPC. Also see system SAMPLIB members APPCPMRX and APPCPMXX for more details.

Figure 1. Basic LUADD Definition
  LUADD
     ACBNAME(MVSLUO1 )             ◄─── LU name
     BASE
     TPDATA(SYS1.APPCTP)           ◄─── APPC/MVS VSAM TP data set
     SIDEINFO DATASET(SYS1.APPCSI) ◄─── APPC/MVS VSAM SI data set
The parameters in Figure 1 do the following:
ACBNAME(MVSLU01 )
Defines the name of the LU as MVSLU01. The name specified must be the same as the LU name specified to VTAM®.
BASE
Indicates that the LU specified for ACBNAME (MVSLU01 in this case) is the base LU for APPC/MVS. The base LU is associated with the APPC/MVS transaction scheduler. APPC LU 6.2 conversations take place across the base LU.
TPDATA(SYS1.APPCTP)
Defines the name of the TP profile data set as SYS1.APPCTP. The name specified must match the name of the APPC/MVS TP profile data set.
SIDEINFO DATASET(SYS1.APPCSI)
Defines the name of the VSAM KSDS side information data set as SYS1.APPCSI. The name specified must match the name of the APPC/MVS side information data set.

The LUADD SCHED parameter (omitted in the above example) specifies the name of the APPC/MVS transaction scheduler. If omitted, it defaults to the value SCHED(ASCH).

For more information on using the LUADD definition, see z/OS MVS Planning: APPC/MVS Management.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014