Subject: Re: APPC Connection
Enabling the OS/2 Communications Manager/2 for ADSM           6/1/94


A VTAM independent LU definition must be added to the VTAM definition
for the OS/2 workstation on SYN.  This VTAM definition should look like:

   Exxxxx00 LU   LOCADDR=0,MODETAB=ZT5160,DLOGMOD=APPCMODE

where xxxxx is the VTAM workstation XID (IDNUM)

Get the XID from the customers workstation and contact VTAM Support
Remember that the VTAM major node S05xxxxx must be recycled for the new
definition to take effect.  The customer should be logged off when doing
the recycle.


The following procedure is applicable to the new OS/2 Version 2
Communications Manager/2 and to an OS/2 workstation that does not already
have APPC/LU6.2 enabled.  Minor variations are pointed out for
version 1.0.


From the OS/2 Desktop select the Communications Manager/2 icon.

1. Initiate CM Setup.

   CM setup is initiated by the following steps:

   a. Select the Communications Manager SetUp icon

   b. After the IBM logo flashes by select SETUP from the Communications
      Setup screen

   c. From the Open Configuration screen:

      1) Select OK

2. From the Communication Manager Configuration Definition screen:

   a. Select Token ring or other LAN types from the Workstation
      Connection Type column

   b. Select APPC APIs from the Feature or Application column

   c. Select the Configure button

3. From the Communication Manager Profile List screen:

   a. Select SNA local node characteristics

   b. Select the Configure button

      1) From the Local Node Characteristics screen:

         a) Enter BVNET for Network ID

         b) Enter Exxxxx00 for Local node name

         c) Select End node - no network node server for Node type
                   (middle of the three selections)

         If the version is 1.1 select Options

         d) Enter Exxxxx00 for Local node alias name

            For the above, xxxxx is the workstation XID (IDNUM)

         If the version is 1.1 select the OK button

         e) Select the OK button

4. From the Communications Manager Profile List screen:

   a. Select SNA connections

   b. Select the Configure button

      1) From the Connections List screen:

         a) Select the active link (usually HOST0001)

            Note that the Partner type should be To host

         b) Select the Change button

            i. From the Adapter List screen:

               i) Select Token ring or other LAN types

               ii) Select the Continue button

                   1. From the Connection to a Host screen:

                      a. Un-highlight APPN Support box if highlighted

                      b. Enter Dxxxxx for the Local PU name
                         (this will not be highlighted for version 1.1
                          so will not be set)

                      c. Enter 400000000004 for the LAN destination
                         address (hex)

                      d. Enter BVNET for the Partner network ID

                      e. Enter Dxxxxx for the Partner node name

                      g. Now select the Define Partner LUs button

                         1) From the Partners LUs screen:

                            a) Enter BVADSM04 for LU name

                            b) Enter BVADSM04 for the Alias

                            c) Enter "FOR MVS ADSM" for the Optional
                               Comment

                            d) Select the ADD button

                         2) Select the OK button

                   2. Select the OK button again

      2) From the Connection List screen:

         a) Select the Close button

5. From the Communications Manager Profile List screen:

   a. Select SNA features

   b. Select the Configure button

      1) From the SNA Features List screen:

         a) Select Modes

         b) Select the Create button

            i. From the Mode Definition screen:

               i) Enter APPCMODE for the Mode name

               ii) Select the OK button

      2) From the SNA Features List screen:

         a) Select CPI Communications side information

         b) Select the Create button

            i. From the CPI Communications Side Information screen

               i) Enter ADSMAPPC for the Symbolic destination name

               ii) Select Fully qualified name

               iii) Enter BVNET in the first field

               iv) Enter BVADSM04 in the second field

               v) Enter BVADSM04 for TP name

               vi) Select None for Security type

               vii) Enter APPCMODE for Mode name

               viii) Select the OK button

      3) Select the Close button from the SNA Features List screen

6. Again select the Close button from the Communications Manager Profile
   List

7. One more time select the Close button from the Communications Manager
   Configuration Definitin screen

8. For the question 'Would you like to dynamically update your SNA
   resources?' select the NO button.

9. Finally from the Communications Manager Setup screen, select the Close
   button

Reboot your workstation before by try to establish an ADSM APPC client/
server session.  If you've already rebooted from the ADSM software
install, then only Communications Manager must be restarted.





Enabling the OS/2 Version 2 Communications Manager for ADSM


A VTAM independent LU definition must be added to the VTAM definition
for the OS/2 workstation on SYN.  This VTAM definition should look like:

  Exxxxx00 LU    LOCADDR=0,MODETAB=ZT5160,DLOGMOD=APPCMODE

  where xxxxx is the VTAM workstation XID (IDNUM)

Remember that the VTAM major node S05xxxxx must be recycled for the new
definition to take effect.  Verify this from SYN NetView by entering DP
Exxxxx00 again where xxxxx is the VTAM workstation XID.

The following procedure is only applicable to the standard OS/2 Version 2
communication manager (not the new communication manager) and to an OS/2
workstation that does not have APPC/LU6.2 enabled.


1. Initiate CM Setup

   CM setup is initiated by the following steps.
   a. Go to the CM Main Menu
   b. Select Advanced from the pull-down menu
   c. Select 4. Configuration from teh pull-down menu
   d. Use the name of your current configuration in the pop-up window
   e. Select 4. SNA feature profiles from the next window
   f. Select SNA network definitions
   g. Select 1. Create/Change from the pop-up menu

These steps lead to the SNA Network Definition Selection window from
where you continue with the following steps:

2. Set Up Local Node Characteristics

   In this step you set up the characteristics of your workstation.

   a. Select Local Node Characteristics
   b. Select the Configure button
      The Local Node Characteristics window should appear.  You should
      fill in:

      1) BVNET for the Network ID
      2) Exxxxx00 for the Local node name (where xxxxx is the workstation
         XID (IDNUM).  This is the VTAM independent LU name which was
         discussed at the beginning of the install procedures.
      3) Select End node - no network node server (middle of the three
         selections) for Node type
      4) Enter xxxxx for Local node ID (This is the workstation's XID
         (IDNUM)
      5) Enter Exxxxx00 for Local node alias name (This is the same as
         Local node name above).
      6) Select the Save and Return button

3. Set Up Mode

   In this step you will define the VTAM logon mode name.

   a. Select Additional SNA Features
   b. Select the Configure button
      This leads to the CM Addtional SNA Features window
   c. Select Modes
      The Creating a Mode Definition window will appear.  You should fill
      in:
      1) Enter APPCMODE for Mode name
      2) Enter #CONNECT for Class of service
      3) Use the defaults for the other selections
      4) Select the OK button

4. Set up side information

   The side information is used to group information needed for
   establishing and APPC session and to provide it with a label tag
   called the symbolic destination name.

   a. Select CPI Communications Side Information
      The Creating a Side Information window should appear.  You should
      fill in the following:

      1) Enter ADSMAPPC for the Symbolic destination name
      2) Select Fully qualified name and enter BVNET in the first field
         and BVADSM04 in the second field
      3) Enter BVADSM04 for the TP name
      4) Select None for the Security type
      5) Enter APPCMODE for the Mode name
      6) Select the OK button
      7) Select File from the action bar
      8) Select Save and Exit from the File pull-down menu

5. Set up Link to Host

   In this step a path will be set which will be used to establish a
   session to the host application.  From the SNA Network Definitions
   Selection window where the previous step should have led you:

   a. Select Connections
   b. Select the Configure button
   c. Select To Primary Host
   d. You have to choose a data link control (DLC) type and the
      appropriate adapter number.  Select DLC type IBMTRNET with adapter
      number 00
   e. Select the Continue button
      The Creating a Connection to a Primary Host window should appear.
      You must fill in:

      1) Use the system generated default name for Link name
      2) Enter BVNET for the Partner network ID
      3) Enter Dxxxxx (where xxxxx is the workstation XID (IDNUM)) for
         for the Partner node name  (This is the VTAM PU name for this
         workstation.)
      4) Enter 400000000004 for the LAN destination address
      5) Select the Define Partner LU's button
         The Creating Partner LUs window should appear.  You should fill
         in:
         a) Enter BVADSM04 for the LU name (This is the MVS VTAM APPL
            name.)
         b) Enter BVADSM04 for the Alias name
         c) Select the Add button
         d) Select the OK button
         e) Select the OK button
         f) Select File from the action bar
         g) Select Save and Exit from the File pull-down menu

6. Save your work

   Perform exit operaitons until you are back to the Communications
   Configuration Menu.  You should end with a message telling you that
   verification is required.

   For verification you have to:

   a. Select Verify from the action bar
   b. Select Run verify from the Verify pull-down menu
      Verification should end with no errors.

7. Reboot your workstation before you try to establish an ADSM APPC
   client/server session.  If you've already rebooted from the ADSM
   software install, then only Communications Manager must be restarted.