Configuration of CM/2

For connection of R/2 Workstation Software under OS/2, you have to configure the Communications Manager for LU6.2 connections. Communications Manager CM/2 Version 1.0/1.1/1.11 can be used both under the OS/2 2.x operating system and OS/2 Warp 3.0.

The configuration example below is for communication with an IBM-3174 control unit as the LAN gateway.

This configuration example is available in the following subdirectory (after installation of the R/2 Workstation Software):
/SAP_WS/COMMSUB/TR_CM2.* (4 files in total)

In the same subdirectory, you will also find a configuration example for an SDLC connection to the host. It is under the name SDLC_CM2.* (4 files in total).

You configure other communication paths (Ethernet, X.25,..) in the same way as the model profiles. The IBM documentation may offer help on special adjustments.

General parameter definitions (on the host side; VTAM, CICS, IMS) are identical to the example specifications in the section MVS/VSE Host Systems. These parameter definitions are shown in the configuration data as follows: [Parameter value].

To configure the workstation-host connection correctly, you have to perform the following actions:

  1. Select the symbol "CM/2" on the PM interface
  2. Select the symbol "Communications Manager-Setup"
  3. Choose the option "SETUP"
  4. Select the profile to be edited (e.g. TR_CM2)
  5. (The configuration example can be found in the COMMSUB subdirectory. It must first be copied to the /CMLIB directory.))

  6. You will be prompted whether the CM/2 configuration is used on the workstation; Respond accordingly
  7. The following parameter setting is required only up to Version 1.040 of the R/2 Workstation Software:
  8. – Select "OPTIONS" in the menu bar of the CM/2 Configuration Definition

    – Select the function CHANGE WORKSTATION INFORMATION

    – Enter the file name ACSGSAP.DAT in the field "ASCII/EBCDIC translation table file name", and confirm

    – Do not make any changes under the option "DEFINITION SELECTION". This selection screen does NOT appear with CM/2 Version 1.0.

  9. Under "WORKSTATION CONNECTION TYPE", select the relevant connection type "TOKEN-RING OR OTHER LAN TYPES" is the connection type defined for the SAP example TR_CM2.
  10. It is a good idea if you first activate an IBM 3270 terminal emulation session (LU2). You can then be certain that you have a physical (and logical) connection with the host (display of terminal emulation screen). Now you can begin to set up an LU6.2 session. If you are not implementing 3270 terminal emulation, you can skip point 8.

  11. Under "FEATURE OR APPLICATION", select "3270-Emulation" and activate with the option "Configure"
  12. Comments
    3270 Emulation
    - Destination address: [40003174FFFF] Address 3174 Gateway
    (e.g. IBM control unit)
    - Number of terminal: [1 ] Number of 3270 terminal-
    emulation sessions

    – Activate the option "ADVANCED..."

    – From the "Communications Manager Profile List", select the function "REQUIRED 3270-EMULATION" and activate with the option "CONFIGURE"

    – In the 3270 Emulation Window, position the mouse pointer on "HOST" and double-click.

    Corresponding parameter update:

    - Presentation Space : 25x80 3278/79 Model 2

    - LU local/NAU address: [03] VTAM Address (LOGADDR)

    - Session ID : [A ]

    - Alarm : Screen Update [OFF] no beep

    SAP CONNECTION USER:
    If you intend to work with the product SAP Connection for OS/2, set an IBM 3278/79 Mod 2. Communication is implemented with an HLLAPI interface of the Communication Manager. Screen Update OFF stops the output of beeps when changing screens at the terminal.

    – Go back as far as the "Communications Manager Profile List" window.
    Continue with point 10.

  13. Under "FEATURE OR APPLICATION", select "APPC APIs" and activate with the option "Configure". Skip the "APPC APIs" window by activating the option "ADVANCED".
  14. From "Communications Manager Profile List", select the function "DLC-TOKEN-RING OR OTHER LAN TYPES" and activate with the option "CONFIGURE".

- Adapter : [ 1] Adapter number
- Maximum Link Stations : [ 4] or higher
- percent incoming calls: [ 0] no reservation
- Maximum I-field size : [1920] Adapter type dependent
(to be adjusted according to the RU size in MODE, as the headers are to be included for this parameter.)

- Window count Parameter xxx in VTAM

Send window count : [2]

Receive window count : [1]

- Network ID : [SNANETID] SNA network ID

- Local node name : [PTRJA0 ] VTAM PU name (PTRJA0=PUNAME)

- End Node - no Network Node [x] LEN, no APPN !

- Local node ID : [00000] IDNUM in VTAM

Continue by activating the OPTIONS field.

- Local node Alias : [PUALIAS ] PU Alias Name

- Activate Attach Mgr [x]

Partner Typ - to host

- Link name [LINK0001]

Back to window adapter list with Create or Change

Select adapter type/number (for example "Token-ring or other LAN types") and activate with the option CONTINUE ...

- Partner network ID : [SNANETID] SNA Network ID

- Partner node name : [CPNAME ] VTAM CP name
(not checked;
entry field is however
"REQUIRED")

- LAN destination address: [40003174FFFF] Address 3174 Gateway
(e.g. IBM control unit)

Continue by activating the option DEFINE PARTNER LUs...

- Define Partner LUs

Network ID : [SNANETID] SNA Network ID

LU name : [CICSPL ] CICS ACB name or
IMS LU6.1 Adapter
[APPCBRDG] (CICSPL=ACBNAME)

Alias : [MYCICS ] ==> Entry in table SIDEINFO

Define partner LU functionality

[DEPENDENT] or [INDEPENDENT]

For Independent, the parameter
"Uninterpreted name" has to be defined;
Parameter is identical to Parameter LU name

Uninterpreted name : [CICSPL ] CICSPL=ACBNAME

[ADD]

This is the only way that the partner LUs can be defined. If they are defined via "SNA features", then the Communications Manager functions incorrectly.

LU name : [LU00000 ] VTAM LU name
(LU00000=LUNAME1)
- Alias : [LU#01 ] ==> SIDEINFO
- NAU address

(x) Dependend LU : [01] VTAM address (LOGADDR)
- LU name : [LU00001 ] VTAM LU name
(LU00001=LUNAME2)
- Alias : [LU#02 ] ==> SIDEINFO
- NAU address

(x) Dependend LU : [02] VTAM Address (LOGADDR)

For Single Session Module, an LU address should be made available for each parallel connection.

Display only is possible here. Partner LUs must not be defined from this position ---> Error !!!

The partner LUs are already defined within the connection and assigned to LINK0001.

- Mode name : [LU62SAP1] VTAM Mode

- Class of service : #CONNECT

- Mode session limit : [1] Single Session

- Minimum con.winner : [1]

- Receive pacing : [0] 0=no pacing

- RU size

(x) Maximum RU size : [256] SAP recommended value

For local connections, there are Pacing and RU Size values, which are also indicative for LU6.2 performance:

Only has to be defined when the host is starting a program. For IMS customers, a program named IMSASYNC must always be entered here.

By copying the program GMUX_5x.EXE, you must create the program IMSASYNC.EXE from the GRAPHIC subdiretory.

- Transaction Program (TP) name : IMSASYNC
- OS/2 program path and file name : x:\SAP\GW\IMSASYNC.EXE
corresponding drive

- Presentation type : Presentation Manager
- Operation type : Non-queued. Attach Manager started

If you want to use the SAP configuration examples as a model, you must copy the files TR_CM2.* or SADLC_CM2 from the LW:\SAP\GW\COMMSUB directory to the directory of the Communications Manager (LW:/CMLIB).

The following files were copied:

\CMLIB\TR_CM2.CFG

\CMLIB\TR_CM2.CF2

\CMLIB\TR_CM2.SEC

\CMLIB\TR_CM2.NDF

or

\CMLIB\SDLC_CM2.CFG

\CMLIB\SDLC_CM2.CF2

\CMLIB\SDLC_CM2.SEC

\CMLIB\SDLC_CM2.NDF

The file TR_CM2.NDF (or SDLC_CM2.NDF) is a text file, in which the entries specified above (inter alia) can be found again. It is structured as follows:.

DEFINE_LOCAL_CP FQ_CP_NAME(SNANETID.PTRJA0 ) PTRJA0=PUNAME
DESCRIPTION(Created on 01.02.95 at 16.30)
CP_ALIAS(PUALIAS)
NAU_ADDRESS(INDEPENDENT_LU)
NODE_TYPE(EN)
NODE_ID(X'00000')
HOST_FP_SUPPORT(YES)
HOST_FP_LINK_NAME(LINK0001);

DEFINE_LOGICAL_LINK LINK_NAME(LINK0001)
FQ_ADJACENT_CP_NAME(SNANETID.SSCPNAME)
ADJACENT_NODE_TYPE(LEN)
DLC_NAME(IBMTRNET)
ADAPTER_NUMBER(0)
DESTINATION_ADDRESS(X'40003174FFFF')
CP_CP_SESSION_SUPPORT(NO)
ACTIVATE_AT_STARTUP(YES)
LIMITED_RESOURCE(USE_ADAPTER_DEFINITION)
LINK_STATION_ROLE(USE_ADAPTER_DEFINITION)
SOLICIT_SSCP_SESSION(YES)
EFFECTIVE_CAPACITY(USE_ADAPTER_DEFINITION)
COST_PER_CONNECT_TIME(USE_ADAPTER_DEFINITION)
COST_PER_BYTE(USE_ADAPTER_DEFINITION)
SECURITY(USE_ADAPTER_DEFINITION)
PROPAGATION_DELAY(USE_ADAPTER_DEFINITION)
USER_DEFINED_1(USE_ADAPTER_DEFINITION)
USER_DEFINED_2(USE_ADAPTER_DEFINITION)
USER_DEFINED_3(USE_ADAPTER_DEFINITION);

DEFINE_LOCAL_LU LU_NAME(LU00000) LU00000=LUNAME1
DESCRIPTION(Local LU #1 for LU6.2 sessions)
LU_ALIAS(LU#01 )
NAU_ADDRESS(1);

DEFINE_LOCAL_LU LU_NAME(LU00001) LU00001=LUNAME2
DESCRIPTION(Local LU #3 for LU6.2 sessions)
LU_ALIAS(LU#02 )
NAU_ADDRESS(2);

DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(SNANETID.CICSPL ) CICSPL=ACBNAME
DESCRIPTION(Partner LU is CICS running SAP R/2 System)
PARTNER_LU_ALIAS(MYCICS)
PARTNER_LU_UNINTERPRETED_NAME(CICSPL ) CICSPL=ACBNAME
MAX_MC_LL_SEND_SIZE(32767)
CONV_SECURITY_VERIFICATION(NO)
PARALLEL_SESSION_SUPPORT(NO);

Entry for LU6.2 connection with IMS. To be able to implement LU6.2, an LU6.1 Adapter is used here. You must enter the name of the LU6.1 Adapter for the entry ACBNAME of CICS when defining the partner LU. The standard definition of this name is as APPCBRDG.

DEFINE_PARTNER_LU FQ_PARTNER_LU_NAME(SNANETID.APPCBRDG)
DESCRIPTION(Partner LU is IMS LU6.1 Adapter for LU6.2 Applications)
PARTNER_LU_ALIAS(APPCBRDG)
PARTNER_LU_UNINTERPRETED_NAME(APPCBRDG)
MAX_MC_LL_SEND_SIZE(32767)
CONV_SECURITY_VERIFICATION(NO)
PARALLEL_SESSION_SUPPORT(NO);

DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(SNANETID.CICSPL) CICSPL=ACBNAME
DESCRIPTION(Partner LU is CICS running SAP R/2 System)
WILDCARD_ENTRY(NO)
FQ_OWNING_CP_NAME(SNANETID.CPNAME )
LOCAL_NODE_NN_SERVER(NO);

DEFINE_PARTNER_LU_LOCATION FQ_PARTNER_LU_NAME(SNANETID.APPCBRDG)
DESCRIPTION(Partner LU is IMS LU6.1 Adapter for LU6.2 Applications)
WILDCARD_ENTRY(NO)
FQ_OWNING_CP_NAME(SNANETID.CPNAME )
LOCAL_NODE_NN_SERVER(NO);

DEFINE_MODE MODE_NAME(LU62SAP1)
DESCRIPTION(Logmode used for LU6.2 single session support)
COS_NAME(#CONNECT)
DEFAULT_RU_SIZE(YES)
RECEIVE_PACING_WINDOW(0)
MAX_NEGOTIABLE_SESSION_LIMIT(32767)
PLU_MODE_SESSION_LIMIT(1)
MIN_CONWINNERS_SOURCE(1);

DEFINE_DEFAULTS IMPLICIT_INBOUND_PLU_SUPPORT(YES)
DESCRIPTION(Created on 01.02.95 at 16.30)
DEFAULT_MODE_NAME(BLANK)
MAX_MC_LL_SEND_SIZE(32767)
DIRECTORY_FOR_INBOUND_ATTACHES(*)
DEFAULT_TP_OPERATION(NONQUEUED_AM_STARTED)
DEFAULT_TP_PROGRAM_TYPE(BACKGROUND)
DEFAULT_TP_CONV_SECURITY_RQD(NO)
MAX_HELD_ALERTS(10);

An entry for transaction programs is only necessary if a host is activating a program on the workstation. This is the case, for example, with direct program-to-program communication. You only define the program IMSASYNC.EXE if you are using the LU6.1 Adapter.

DEFINE_TP TP_NAME(IMSASYNC)
DESCRIPTION(SAP's Graphics Multiplexer for IMS Requests)
FILESPEC(D:\SAP_WS\GRAPHIC\IMSASYNC.EXE)
CONVERSATION_TYPE(EITHER)
CONV_SECURITY_RQD(NO)
SYNC_LEVEL(EITHER)
TP_OPERATION(QUEUED_AM_STARTED)
PROGRAM_TYPE(PRESENTATION_MANAGER)
INCOMING_ALLOCATE_QUEUE_DEPTH(255)
INCOMING_ALLOCATE_TIMEOUT(INFINITE)
RECEIVE_ALLOCATE_TIMEOUT(INFINITE);

START_ATTACH_MANAGER;

The configuration file SDLC_CM2.NDF has the same structure; The only additional parameters for definition are some that are specific to dedicated or switched lines.

Explanation:

All "name or value" parameters refer to other examples in this guide.

You can assign any value to the parameter MYCICS; It only refers to the SIDEINFO table. For a better understanding, you should enter the ACB name here (that is, the same value as for parameter ACBNAME).

When using a "dependent" LU, the parameter "PARTNER_LU_UNINTERPRETED_NAME" must be the same as the ACBNAME for the partner definition.

If you want to define additional LUs, PLUs etc, this can also be done by copying the corresponding block in the .NDF file and then overwriting the old data with the current parameters. If the.NDF file was changed with an editor, you must then execute the program CMVERIFY.EXE in an OS/2 window. You start the program with the CMVERIFY command and the specification of the file to be checked (without extension).

Configuration File Upgrade

It is not the adapter address of the file to be updated that is copied, but the adapter address of the standard configuration file for starting the Communications Manager.

Table SIDEINFO for Configuration Example TR_CM2

You can assign any value to the DEST parameter, but it must match the SYSTEMID (or DESTINATION) entry in the CUA Interface called.

*--------------------
* SAP R/2 K50
*-------------------
DEST=K50 - Destination
PROTOCOL=C
LOCAL_LU=LU#01 - local LU
LU=MYCICS- Partner LU
TP=X1SA- Start transaction on the host

MODE_NAME=LU62SAP1- LogMode

CPIC_TRACE=3 - Environment variable (example)
KEEP_SESSION=1
- Environment variable (example)