Implementing and Managing APPC Protected Conversations

114 Implementing and Managing APPC Protected Conversations

Overview of installed components

When defining our systems for setting up an APPC protected conversation environment we

utilized existing installation verification procedures and available examples where

appropriate.

We used the basis of the DB2 and CICS IVP code to establish a connection and update

facility for the APPC protected conversation. This allows us to write records to DB2 and view

any updates that are committed to the database. We used SPUFI to interrogate DB2. This is

not mandatory but is widely available.

The setup was organized into four areas: general, CICS, IMS, and DB2 definitions. Where

required, we also provided the JCL, RDO definitions, SQL code, and source to aid you in

installing a complete environment.

General definitions

PL/I and COBOL Enterprise compilers

Access to the compilers is needed to allow the five APPC/IMS (PL/I) and one APPC/CICS

(COBOL) programs. The compiles are done via batch jobs so access to the PL/I and COBOL

compilers via ISPF foreground panels is not required.

a. Enterprise PL/1 V3.3.0 (includes the compiler, samples, and so forth.)

PL/I libraries established under HLQ: BMZ.EPLI.V3R3M0

IBMZ.EPLI.V3R3M0.SIBMZCMP (Load library)

IBMZ.EPLI.V3R3M0.SIBMZPRC (procs)

IBMZ.EPLI.V3R3M0.SIBMZSAMP (samples)

b. Enterprise COBOL Cobol v3.3.0 (includes the compiler)

Cobol can be found under HLQ: IGY.ECOBOL.V3R3M0

IGY.ECOBOL.V3R3M0.SIGYCLST

IGY.ECOBOL.V3R3M0.SIGYCOMP (Load library)

IGY.ECOBOL.V3R3M0.SIGYMAC

IGY.ECOBOL.V3R3M0.SIGYPROC (procs)

IGY.ECOBOL.V3R3M0.SIGYSAMP (samples)

Version 3.3.0 of PL/I and COBOL is used for the setup exercise.

Network components

Commonly you implement protected conversations in an existing environment. From a

network point of view, there are three components that must be addressed:

򐂰 General VTAM parameters

򐂰 CICS LUs parameters

򐂰 IMS LUs parameters

ACF/VTAM LOGMODE table entries

You must specify a Modetable and an entry within the table to be used for LU6.2

conversations. The VTAM APPL parameter MODETAB=LOGMODES indicates the Mode

Table. LOGMODES resides in SYSx.VTAMLIB. Table A-1 lists the entries for the Logmodes.

Appendix A. Installation definitions for Protected Conversation exploiters 115

Table A-1 Logmode Names

The VTAM APPL parameter DLOGMOD=APPCHOST indicates the entry (MODEENT) within

the Mode Table. The Logmode entry used by the IMS system and CICS systems needs to be

aligned.

For CICS-to-IMS links that are cross-domain, you must associate the IMS LOGMODE entry

with the CICS applid (the generic applid for XRF systems) using the DLOGMOD or

MODETAB parameters. Ensure the CICS Mode table entry contains a Logmode table entry

(MODEENT) which is the same as the Logmode table entry used by IMS when allocating the

conversation.

The Modetable LOGMODES and its associated APPCHOST Logmode is sourced from the

ATBLMODE member in SYS1.SAMPLIB.

Example A-1: SYSx.SAMPLIB Logmodes

SYSx.SAMPLIB contains the following samples;

ATBLJOB JCL, VTAM logmode table link edit job.

ATBLMODE VTAM logmode table for APPC.

Extract from the ATBLMODE member (VTAM logmode table for APPC).

Example A-2: Extract from the ATBLMODE

LOGMODES MODETAB

EJECT

**********************************************************************

TITLE 'SNASVCMG' *@R495812*

**********************************************************************

* LOGMODE TABLE ENTRY FOR RESOURCES CAPABLE OF ACTING *

* AS LU 6.2 DEVICES *

* REQUIRED FOR LU MANAGEMENT *

**********************************************************************

SNASVCMG MODEENT LOGMODE=SNASVCMG,FMPROF=X'13',TSPROF=X'07', *

PRIPROT=X'B0',SECPROT=X'B0',COMPROT=X'D0B1', *

RUSIZES=X'8585',ENCR=B'0000', *

PSERVIC=X'060200000000000000000300'

**********************************************************************

TITLE 'APPCPCLM'

**********************************************************************

* LOGMODE TABLE ENTRY FOR RESOURCES CAPABLE OF ACTING *

* AS LU 6.2 DEVICES *

* FOR PC TARGET *

* IN THIS EXAMPLE THE DEFAULT RU SIZE FOR OS/2 (1024) IS USED @01C*

**********************************************************************

APPCPCLM MODEENT LOGMODE=APPCPCLM, *

RUSIZES=X'8787', *

SRCVPAC=X'00', *

SSNDPAC=X'01'

Logmode Name Description

SNASVCMG Logmode table entry for resources capable of acting as LU 6.2

devices, required for LU management.

APPCPCLM Logmode table entry for resources capable of acting as LU 6.2

devices for PC target.

APPCHOST Logmode table entry for resources capable of acting as LU 6.2

devices for host target in this example RU size of 4096 is used.