How does the other computer recognize Blueworx Voice Response?

Communications Server for AIX manages only the pSeries computer. Other components on the network may require additional information before they can communicate with Blueworx Voice Response. For example, when the network connects the pSeries computer to a remote computer through a communication controller, both the remote computer and the controller need to be made aware that the pSeries computer is part of the network. When the connection is to an IBM System/370 processor, the VTAM definition file needs to include the pSeries computer.

Configuring host communication for Blueworx Voice Response

You must define to VTAM a physical unit (PU) with at least one logical unit (LU) for communication to the pSeries computer. Define the PU with a MAXDATA parameter of at least 256 and PUTYPE=2. All other parameters are dependent on the connection type to the host. Define at least one LU for 3270 emulation. Define the 3270 emulation LU with the following parameters:

Nonnegotiable bind 
FM Profile (FMPROF)=3 
TS Profile (TSPROF)=3 
FM usage-Primary LU protocols (PRIPROT)=x'11',x'21',x'31',x'91',x'A1',
                                                            or x'B1'
FM usage-Secondary LU protocols (SECPROT)=x'B0',x'90', or x'A0' for
displays, also x'10',x'20',x'30' for printers.
FM usage-Common LU Protocols (COMPROT)=x'3080',x'7080' for LU1 printers.
Pacing=none required 
LU type=LU2 (PSERVIC = x'028000000000000000000200') 
or 
LU type=LU3 (PSERVIC = x'038000000000648400007E00') 
or 
LU type=LU1 (PSERVIC = x'01000000E100000000000000')

The values specified for the PSERVIC fields are not the only valid values that can be entered. The PSERVIC field controls the LU type and screen or print buffer options and sizes. Other valid 3270 settings can be used in this field.

Configuring the mainframe computer for connection over TCP/IP

Use this procedure to help you configure your mainframe computer to communicate with Blueworx Voice Response over a TCP/IP network. For complete instructions see Communications Server for AIX: Administration Guide. Additional information is provided in the IBM Redbook Migrating Subarea Networks to an IP Infrastructure Using Enterprise Extender.

  1. Configure a VIPA address in the TCP/IP stack that Enterprise Extender will use.
  2. Set up an Enterprise Extender connection. The connections are defined to VTAM as shown in the following example:
    AP24XCAE VBUILD TYPE=XCA
    IYCOZXP1 PORT  MEDIUM=HPRIP,
                   IPTOS=(20,40,80,C0)
                   LIVTIME=10,
                   SAPADDR=8,
                   SRQRETRY=3
                   SRQTIME=15
    IYCOZXG1 GROUP DIAL=YES,CALL=INOUT,
                   DYNPUPFX=IY,
                   DYNPU=YES,
                   AUTOGEN=(24,EEL,EEP)
    Switched XCA major node
    Switched major node configuration
    AP24SMNX VBUILD TYPE=SWNET
    IYCOR000  PU   PUTYPE=2,
                   CPNAME=NETLEY,
                   ADDR=01,
                   ASDP=YES,
                   NETID=GBIBMIYA,
                   CPCP=YES,
                   CONNTYPE=APPN,
                   TGN=3,                  USE 3 FOR ENTERPRISE EXTENDER
                   HPR=YES,
                   DWACT=NO,
                   XID=YES,
                   TGP=TRING16M,           USE THIS TG PROFILE IN IBMTGPS
                   ISTATUS=ACTIVE
    *
    IYCOP000  PATH IPADDR=0.00.00.00,      IP ADDR OF WORK STATION
                   GRPNM=IYCOZXG1          REFERS TO GROUP NAME IN XCA MAJNODE
  3. Configure a DLUR connection. Use the following example as a guide:
    AP24SMNY VBUILD TYPE=SWNET
    IYCOR00A  PU   PUTYPE=2,
                   IDBLK=071,
                   IDNUM=1111A,
                   MODETAB=SNATERM#,
                   LOGTAB=LOGTAB00,
                   USSTAB=UTCPPTOK,
                   SSCPFM=USSSCS,
                   VPACING=0,PACING=0,
                   ISTATUS=ACTIVE
    *
    IYCOT042 LU    LOCADDR=2,ISTATUS=ACTIVE
    IYCOT043 LU    LOCADDR=3,ISTATUS=ACTIVE
    IYCOT044 LU    LOCADDR=4,ISTATUS=ACTIVE
    IYCOT045 LU    LOCADDR=5,ISTATUS=ACTIVE
    etc to
    IYCOT743 LU    LOCADDR=255,ISTATUS=ACTIVE
    *
    * Example of an additional DLUR connection
    IYCOR005  PU   PUTYPE=2,
                   IDBLK=071,
                   IDNUM=11115,
                   MODETAB=SNATERM#,
                   LOGTAB=LOGTAB00,    INTERPRET TABLE IN SYS2.VTAMLIB
                   USSTAB=UTM24TOK,
                   SSCPFM=USSSCS,
                   VPACING=0,PACING=0,
                   ISTATUS=ACTIVE
    *
    IYCOT051 LU    LOCADDR=1,ISTATUS=ACTIVE
    IYCOT052 LU    LOCADDR=2,ISTATUS=ACTIVE
    IYCOT053 LU    LOCADDR=3,ISTATUS=ACTIVE
    IYCOT054 LU    LOCADDR=4,ISTATUS=ACTIVE
    IYCOT055 LU    LOCADDR=5,ISTATUS=ACTIVE
    IYCOT056 LU    LOCADDR=6,ISTATUS=ACTIVE