Examples for the generation of a client/server combination

The following examples show how to connect a UPIC client which is running on a Windows PC to a UTM application on BS2000 and on a Unix or Linux system.

Example 1: Connecting a UPIC client to openUTM on BS2000 systems

The UTM server application is located on a host with the name BS2HOST1, the client program is running on a PC with the computer name PCCLT002. The transport connection is to be established via TCP/IP (address format RFC1006).

• UTM generation under the BS2000 system

  *** Define BCAM application name for the UTM server application:***
  BCAMAPPL SERVER, T-PROT=RFC1006

  *** Generate client:***
  PTERM UPICPT, PTYPE=UPIC-R, LTERM=UPICLT, BCAMAPPL=SERVER, -
        PRONAM=PCCLT002
  LTERM UPICLT

  *** Define TAC for the client:***
  TAC TAC1, PROGRAM=SERVICE

  The statement LTERM UPICLT means that openUTM implicitly uses a connection user ID called UPICLT.

• Entries in the side information file (upicfile) of the UTM client

  * UTM application under the BS2000 system
  SDsamplaw SERVER.BS2HOST1 TAC1
  * or, if you require automatic conversion of user data 
  * from ASCII to EBCDIC and vice versa
  HDsamplaw SERVER.BS2HOST1 TAC1

• Specification in the client program

  Enable_UTM-UPIC "UPICPT"
  Initialize_Conversation "samplaw" 

Example 2: Connecting a UPIC client to openUTM on Unix, Linux or Windows systems

This example describes the TCP/IP RFC1006 connection of a UPIC client to a UTM application on a Unix, Linux or Windows system. The example shows the coordination of the generation for both communication partners.

The UTM application is running on a computer with the name UXHOST01. The client is located on a Windows system for which the name PCCLT001 has been generated in the KDCDEF. The UTM application receives the local port number 1230.

• Generating the UTM server on the Unix, Linux or Windows system

  BCAMAPPL UTMUPICR,LISTENER-PORT=1230,T-PROT=RFC1006,TSEL-FORMAT=T

  PTERM UPICPT,PTYPE=UPIC-R,LTERM=UPICLT,BCAMAPPL=UTMUPICR,PRONAM=PCCLT001, \
              T-PROT=RFC1006,TSEL-FORMAT=T
  LTERM UPICLT 
  

  The statement LTERM UPICLT means that openUTM implicitly uses a connection user ID called UPICLT.

• Entries in the side information file of the client computer

  * Local application
  LNUPICTTY UPICPT PORT=1240

  * UTM application on Unix/Linux/Windows system with port 1230, 
  * TCP/IP host name=UXHOST01
  SDsampladm UTMUPICR.UXHOST01 TAC1 PORT=1230

• Specification in the client program

  Enable_UTM_UPIC "UPICPT"
Initialize_Conversation "sampladm"    

Example 3: Connecting an OpenCPIC client

An OpenCPIC client is running on a Unix or Linux system with the host name UNIXPRO1. The client connects itself via RFC1006 to a UTM application on BS2000 system and to a UTM application on Unix, Linux or Windows system. The following is to apply:

• In the UTM application on the BS2000 system, the client calls the transaction code TRAVEL02 and in the UTM application on Unix, Linux or Windows system it calls the transaction code STATIST1.

• It is to be possible to have up to 10 parallel connections to the BS2000 system, and up to 2 parallel logical connections to Unix, Linux or Windows system.

• The UTM application on the BS2000 system uses the local port number 102. The UTM application on Unix, Linux or Windows system uses the local port number 12000.

• The OpenCPIC client uses the local port number 13000.

• UTM generation on BS2000 system

  UTMD APT = (2, 7, 16, 2)

  ACCESS-POINT SERVER,
     T-PROT = RFC1006,
     P-SEL = *NONE,
     S-SEL = *NONE,
     T-SEL = C'UTMSERV1',
     AEQ = 1

  OSI-CON CONNECTB,
     LOCAL-ACCESS-POINT = SERVER,
     P-SEL = *NONE,
     S-SEL = *NONE,
     T-SEL = C'CPICCLT1',
     N-SEL = C'UNIXPRO1',
     LISTENER-PORT = 13000,
     OSI-LPAP = OSILPAPB

  OSI-LPAP OSILPAPB,
     APT = (2, 7, 16, 4),
     APPLICATION-CONTEXT = UDTSEC,
     AEQ = 1,
     ASS-NAMES=CPIC,
     ASSOCIATIONS=10,
     CONTWIN=0
  TAC TRAVEL02 ...
  

• UTM generation on Unix, Linux or Windows system

  UTMD APT = (2, 7, 16, 3)

  ACCESS-POINT STATSERV,
     T-PROT = RFC1006,
     P-SEL = *NONE,
     S-SEL = *NONE,
     T-SEL = C'UTMSERV2',
     LISTENER-PORT = 12000,
     T-PROT = RFC1006,
     T-SEL-FORMAT = T,
     AEQ = 1

  OSI-CON CONNECTX,
     LOCAL-ACCESS-POINT = STATSERV,
     P-SEL = *NONE,
     S-SEL = *NONE,
     T-SEL = C'CPICCLT1',
     N-SEL = C'UNIXPRO1',
     LISTENER-PORT = 13000,
     T-PROT = RFC1006,
     T-SEL-FORMAT = T,
     OSI-LPAP = OSILPAPX

  OSI-LPAP OSILPAPX,
     APT = (2, 7, 16, 4),
     APPLICATION-CONTEXT = UDTSEC,
     AEQ = 1,
     ASS-NAMES=CPIC,
     ASSOCIATIONS=2,
     CONTWIN=0

  TAC STATIST1 ...

• OpenCPIC generation

  *** Entry for the local application
  LOCAPPL OPENCPIC,
     APT = (2, 7, 16, 4),
     AEQ = 1

  *** Connection to UTM application on BS2000 system
  PARTAPPL UTMSBS20,
     APT = (2, 7, 16, 2),
     APPLICATION-CONTEXT = utm-secu,
     AEQ = 1,
     ASSOCIATIONS = 10,
     CONTWIN = (10,10),
     CONNECT = 10*** 

  *** TAC in the UTM application on BS2000 system
  SYMDEST TRAVEL,
     PARTNER-APPL = UTMSBS20,
     PARTNR-APRO = TRAVEL02

  *** Connection to UTM application on Unix, Linux or Windows system
  PARTAPPL UTMSUNIX,
     APT = (2, 7, 16, 3),
     APPLICATION-CONTEXT = utm-secu,
     AEQ = 1,
     ASSOCIATIONS = 2,
     CONTWIN = (2,2),
     CONNECT = 2 

  *** TAC in the UTM  application on Unix, Linux or Windows system
  SYMDEST STATIST,
     PARTNER-APPL = UTMSUNIX,
     PARTNR-APRO = STATIST1 

• TNS entries in the OpenCPIC client computer (tnsxfrm format)

  OPENCPIC\
     PSEL V''
     SSEL V''
     TSEL RFC1006 T'CPICCLT1'
     TSEL LANINET A'13000'

  UTMSBS20\
     PSEL V''
     SSEL V''  
     TA RFC1006  ip-address-bs2  PORT 102 T'UTMSERV1'    

  UTMSUNIX\
     PSEL V''
     SSEL V''
     TA RFC1006  ip-address-unix  PORT 12000 T'UTMSERV2'