This section describes how to configure APPC for a CM/2
workstation that is connected to a token-ring
Local Area Network (LAN) and the required workstation software.
- IBM OS/2 WARP Version 4.0 plus FixPak 5 or later
- Communications Manager/2 Version 1.11 or later
Below is a table of standard APPC terms and the equivalent CM/2 terms.
Standard Term
| CM/2 Term
|
Network Name
| Network Name
|
LU Name
| Local Node Name
|
Partner LU Name
| Partner Node Name
|
Local LAN Address
| Local MAC Address
|
Adjacent LAN Address
| LAN Destination Address
|
Use Table 1 to create a worksheet that defines
the listed symbols.
These symbols and their corresponding values are used to configure
CM/2 for communication with an APPC/MVS and/or CICS host.
The worksheet consists of two parts:
- Symbols that must be matched with a partner platform (for example,
MVS/APPC or CICS) are under the heading NETWORK VALUES.
- Symbols that are local to the workstation are under the heading
LOCAL VALUES.
Note: |
The values defined in Table 1
are compatible with an appropriately configured APPC/MVS or CICS host.
A workstation configured with these values supports
Remote Edit/Compile/Debug sessions with APPC/MVS and/or
Remote Debug sessions with APPC/MVS and/or CICS.
It also supports access to Remote VSAM using SdU via APPC/MVS
and access to IMS fully qualified databases using Remote DL/I.
In this configuration, it is assumed that CICS and APPC/MVS both reside
on the same MVS host. If this is not the case and you require
assistance, contact your IBM representative.
|
This example assumes that CM/2 configuration files already exist,
that is, you have already installed CM/2
and only require APPC configuration.
If this is not the case, install
CM/2 as described in CM/2 Installation and Configuration
Guide and resume at this point.
Prior to APPC configuration, it is recommended
that you copy your default CFG and NDF files
(usually located in the C:\CMLIB directory)
to another set of files that you can name to CVSCFG.
For example, assuming that your default configuration is named
BASIC, move to the C:\CMLIB directory and then enter on an OS/2
command line:
COPY BASIC.* CVSCFG.*
This creates a copy of the various files that comprise
your default configuration.
The steps below modify this file to contain APPC
definitions while leaving other existing definitions intact.
If you are modifying an existing configuration, as is the case
of the example that follows, some definitions from your worksheet
might already exist and need not be supplied by you.
Perform the following steps to modify the configuration CVSCFG:
- Double-click on the CM/2 icon.
- Double-click on the CM/2 Setup icon.
The Communications Manager Setup window appears,
as shown in Figure 1.
Note: The CM/2 windows shown in the examples are taken from
CM/2 Version 1.11.
If you are using a newer version of CM/2, the windows might have a
slightly different layout.
- Select the Setup push button.
The Open Configuration window appears, similar to
Figure 2.
- Select CVSCFG from the Configurations list.
- Select the OK push button.
- Select the Description as desired.
- When prompted, select the Yes push button
to confirm that CVSCFG will be used for this workstation.
- The Communications Manager Configuration Definition - CVSCFG window appears,
as shown in Figure 3.
Make sure that you have selected the Additional definitions
radio button;
otherwise, the window might appear different from the window in the figure.
Before the workstation can communicate within a network,
it must be recognized by that network.
This means that the
workstation must be properly defined in the Communications
Manager Local Node Characteristics window.
If the workstation has already been defined to the network, verify
that the definitions are complete and consistent with the
worksheet values.
Otherwise, perform the following steps to define these values:
- Select the option Token-ring or other LAN types.
- Select APPC APIs from the Feature or
Application list.
- After selecting APPC APIs,
the Communications Manager Configuration
Definition - CVSCFG window, shown in Figure 4,
changes as a result of your choice.
- Select the Configure push button.
- The APPC APIs through Token-ring window appears, as shown in
Figure 5.
- In the Network ID field, enter the NETWORK
value.
- In the Local node name field, enter the LUNAME
value.
- For the Local node type, select
End node - no network node server.
This allows you to configure directly to the token-ring at the
communications controller.
If you want to connect your host through an APPN network node,
select End node - to a network node server.
Our example does not address this form of connection.
- Select the Advanced push button.
- The Communications Manager Profile List window appears,
as shown in
Figure 6.
- Select SNA local node characteristics from the
Profile Name
list.
- Select the Configure push button.
- The Local Node Characteristics window, shown in
Figure 7,
appears.
- Confirm that the values you entered in the APPC APIs through
Token-ring window are what you need for Network ID,
Local node name, and Local node type.
- Enter the value of NODEID in the Local node ID
field to identify the workstation with NODEID
as opposed to CPNAME.
- Select the Options push button.
- The Local Node Options window appears,
as shown in Figure 8.
- In the Local node alias name field, enter the
LUALIAS value.
This can be the same as the local node name
(LUNAME).
- Select Activate Attach Manager at start up.
- Select the OK push button.
- The Local Node Characteristics window appears,
as shown in Figure 7.
- Select the OK push button.
- The Communications Manager Profile List window appears,
as shown in Figure 6.
Before the workstation can communicate with the host, a corresponding
connection must be defined.
If the connection is already defined, verify
that the definitions are complete and consistent with the worksheet
values by stepping through the following windows. If you are defining
a new connection, enter the field values as you move from one
window to the next.
- Select SNA connections from the Profile Name
list.
- Select the Configure push button.
- The Connections List window appears,
as shown in Figure 9.
- Select To host as the partner to which you are connecting,
as this example shows.
Alternatively, you can connect to a network node.
- If a connection to your host already exists,
select the connection corresponding to the value of LINKNAME.
In our example, LINKNAME is HOST0002.
- Assuming the connection to your
host is already defined for emulators, select the Change
push button.
If no such connection exists, select the Create push
button.
- The Adapter List window,
shown in Figure 10, appears.
- Since this example assumes a token-ring LAN, select
Token-ring or other LAN types.
- Select the Continue push button.
- Since you selected To host
in Figure 9, the Connection to a Host window
appears,as shown in
Figure 11.
- In the Link Name field, enter the LINKNAME
value.
- Check the Activate at startup box to initialize this
link when CM/2 is started.
- For the Local PU name field,
if
this is the only host connection defined and Use this host
connection as your focal point support (see step 8)
is selected, this field defaults to CPNAME.
Otherwise, enter the value of LOCALPU.
- Assuming that VTAM recognizes this station by NODEID
as opposed to CPNAME, specify its hexadecimal value here.
- In the LAN destination address field, enter the
LANADDRESS value.
For this type of connection, LANADDRESS refers to the
token ring at the communication controller.
- In the Partner network ID field, enter the
PARTNERNET value.
- In the Partner node name field, enter the
PARTNERCP value.
- If this is the only host connection defined from this
workstation, check the Use this host connection as your focal point
support box.
If other host connections exist, only one can be so designated.
To explore the alternative of not using host focal point services for a
connection, see the bibliography for this section.
You can define the partner LU and an alias for the MVS/APPC LU.
For example, you can specify that HOSTLU is an alias for
PARTNERNET.PARTNERLU.
Skip this step if you selected End node to network server
in the Local Node Characteristics window,
shown in Figure 7.
- From the Connection to a Host window,
shown in Figure 11, select the Define Partner LUs
push button.
- The Partner LUs window appears, similar to
Figure 12.
- In the Network ID field, enter
the value for PARTNERNET.
- In the LU name field, enter the
value for PARTNERLU.
- In the Alias field, enter
the value for PLUALIAS.
Note: An alias is case sensitive. HOSTLU is a different alias
than hostlu.
- Select the Add push button.
- Select the OK push button.
- From the Connection to a Host window,
shown in Figure 11, select the OK push button.
- The Connections List window appears,
as shown in Figure 9.
- Select Close.
- The Communications Manager Profile List window appears,
as shown in Figure 6.
- From the Communications Manager Profile List,
select SNA features.
- Select the Configure push button.
- The SNA Features List window appears.
To configure a server for the Remote Debugger:
- Select Transaction program definitions from the
Features list.
- Select the Create push button.
The Transaction Program Definition window appears, as shown in
Figure 13.
- Enter the Transaction program (TP) name using the
value of LOCALTP (COBVSDT).
- Using the value of TPPATH, enter the OS/2
Program path and file name as:
drive:\OS2\CMD.EXE
- Using the value of TPPARM, enter the program parameter
string as:
/C drive:\ibmcobol\BIN\CCX1APCD.CMD
- Select the Continue push button.
The Additional TP Parameters window appears, as shown in
Figure 14.
- For the Presentation type, select
VIO - windowable.
- For the Operation type,
select Non-queued, Attach Manager started.
- Select the OK push button.
- Select the Close push button on the SNA Features
List window.
- The Communications Manager Profile List window appears,
as shown in Figure 6.
- Select the Close push button and the
Communications Manager Configuration Definition - CVSCFG window appears,
as shown in
Figure 15.
- Select the Close push button, and
the Communication Manager - Checking Values window appears, as shown
in Figure 16.
A progress indicator will appear on top of this window to indicate that
CM/2 is verifying your APPC configuration.
If there are any errors in the APPC profile. you can identify
them by examining the First Failure Support Technology/2
log within the FFST/2 folder on your OS/2 desktop.
Make whatever corrections are necessary and repeat the
steps above to verify your configuration.
Your configuration can also be verified by issuing the following on
an OS/2 command line within the CMLIB directory:
CMVERIFY CVSCFG
- After your configuration has been verified,
stop and restart CM/2 with the newly modified configuration
file to activate your APPC configuration.