![]() |
![]() |
You can use this section as a reference when configuring MVS and the TSM server for APPC communications. It also provides scenarios for configuring the following clients for APPC communications:
This section also provides help in diagnosing initial client/server connection failures.
The following configurations were done in a cross-domain environment. All the workstations are generated to the 3745 in the DEIBMFD network with the SSCPNAME as FDW. The 3745 is channel-attached to an MVS host machine in the DEIBMA4 network. This MVS machine is connected to another MVS host machine where the TSM server application, named A4V, is running.
The following VTAM definitions must be made on the adjacent SSCP. The MVS host machine is channel-attached to the 3745 in this environment.
TITLE '#BATCH' #BATCH MODEENT LOGMODE=#BATCH, X ENCR=B'0000',SSNDPAC=8, X SRCVPAC=8,PSNDPAC=8,TYPE=0 |
If desired, you can create a new mode for performance tuning after the APPC connection is established. To do this, create it in your current logon mode table, compile it, and then link-edit the member into a VTAM library.
Since the RU size is negotiated between VTAM and the workstations, we recommend that you define a dummy mode table entry (see below). However, if you are going to specify an RU size, you should use a block size of at least 4KB.
+--------------------------------------------------------------------------------+ |TSMAPPC MODEENT LOGMODE=TSMAPPC | +--------------------------------------------------------------------------------+
*------------* * SWITCHED MAJOR NODE * *------------* * VBUILD TYPE=SWNET,MAXGRP=1, X MAXNO=1 * F13833B PU ADDR=C5, X IDBLK=05D,IDNUM=F333B, <==== see explanation below X ISTATUS=ACTIVE, X PUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, X VPACING=8,PACING=8,DISCNT=NO, X USSTAB=USSSNAM,SSCPFM=USSSCS, X MODETAB=MTD1SERH,DLOGMOD=QUERY X F13833B0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, X VPACING=8,PACING=8 F13833B1 LU LOCADDR=2 F13833B2 LU LOCADDR=3 F13833B3 LU LOCADDR=4 F13833B4 LU LOCADDR=5 F13833B5 LU LOCADDR=6,MODETAB=WI3820,PACING=0,VPACING=0, X DLOGMOD=IBM3820T * F13833C PU ADDR=C5, X IDBLK=05D,IDNUM=F333C, X ISTATUS=ACTIVE, X PUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, X VPACING=8,PACING=8,DISCNT=NO, X USSTAB=USSSNAM,SSCPFM=USSSCS, X MODETAB=MTD1SERH,DLOGMOD=QUERY X F13833C0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, X VPACING=8,PACING=8 * F13833D PU ADDR=C5, X IDBLK=05D,IDNUM=F333D, X ISTATUS=ACTIVE, X PUTYPE=2,MAXOUT=8,MAXDATA=4105,MAXPATH=1, X VPACING=8,PACING=8,DISCNT=NO, X USSTAB=USSSNAM,SSCPFM=USSSCS, X MODETAB=MTD1SERH,DLOGMOD=QUERY X F13833D0 LU LOCADDR=0,MODETAB=ISTINCLM,DLOGMOD=#BATCH, X VPACING=8,PACING=8 |
This makes it much easier to implement Advanced Peer-to-Peer Network (APPN(R)). The CPNAME has to be the same as the independent LU name. In the above example, use CPNAME=F13833B0 instead of IDBLK and IDNUM.
The following steps must be completed on an MVS host machine where the server application is executed. In this environment, the MVS host machine name is A4V.
Figure 13. Sample APPL Statement
A4VBTSM VBUILD TYPE=APPL A4VTSM2 APPL ACBNAME=A4VTSM2,EAS=30,AUTH=(ACQ,PASS,VPACE), X HAVAIL=YES,APPC=YES,PARSESS=YES,SONSCIP=YES, X VPACING=5,MODETAB=ISTINCLM,DLOGMOD=#BATCH,DSESLIM=4 |
In this example, the ACBNAME parameter, known as the LU name by the TSM server, is the partner LU that the clients see. MODETAB is the logon mode table entry name. DLOGMOD is the default logon mode entry name.
The DSESLIM parameter has been coded to handle two concurrent sessions from each LU; for example, when you run the administrative client and the backup client from the same workstation. You can increase this value if necessary.
+--------------------------------------------------------------------------------+ |luname A4VTSM2 | +--------------------------------------------------------------------------------+
The steps in Configuring an MVS Server in a Cross-Domain Network can be applied to the single network environment. A single network ID is used throughout all of the clients' configuration files.
Depending on where the control unit is attached, the setup for the server can be simplified. In the example environment, the control unit is not channel-attached to the same host machine where TSM is running. Therefore, you have two VTAMs to deal with. The log mode that you defined on the NCP must also exist on the second host machine where the application is running. However, define the independent LUs only on the host machine where the control unit is attached. The host machine is the owning SSCP.
In the case where the control unit is attached to the same application host machine, you only deal with one VTAM.
Configuration of the 3172 control unit environment is similar to the configuration of the 3745 control unit environment except for the single domain network. In most cases, the control unit is channel-attached to the same host machine that TSM is running on.
Figure 14 contains sample 3174 PU and LU definitions for use with TSM.
Figure 14. VTAM Definition for 3174 Token Ring LAN Gateway
DSM3174 VBUILD TYPE=LOCAL * PU3174 PU CUADDR=2A0, X DISCNT=NO, X DELAY=0, X ISTATUS=ACTIVE, X MAXBFRU=9, X PACING=7, X PUTYPE=2, X VPACING=7, X XID=YES, X SECNET=NO * INDEPENDENT LUS PS21ILU LU LOCADDR=0,ISTATUS=ACTIVE BORNEO LU LOCADDR=0,ISTATUS=ACTIVE IMAGOS2I LU LOCADDR=0,ISTATUS=ACTIVE IMAGNOVI LU LOCADDR=0,ISTATUS=ACTIVE |
The following is a list of recommendations and requirements from the 3174 support group:
For more information on configuring the 3174 for APPN connectivity see manuals: 3174 APPN Implementation Guide (GG24-3702) and IBM 3174 Establishment Controller Installation Guide (GG24-3061).