Communications Server

Network Administration Guide


Chapter 14. Configuring Host Connectivity

You can connect workstations running Communications Server to System/390 (including System/370) or AS/400 hosts. Many of the values you specify for Communications Server configuration are also used when you configure the host. This chapter describes the mapping between the configuration parameters you specify during Communications Server configuration and the parameters you specify on the hosts. This chapter also contains tables that list the parameters that can be used to eliminate the common parameters on each macro to be issued between Communications Server and the host.
Note:Many NCP parameters issued from the LINE, PU, and LU macros can be specified in the GROUP macro for readability and ease of coding. This matching of parameters eliminates the need to include common parameters on each subsequent macro and still allows the capability to override when appropriate.


NCP Token Ring (NTRI) with VTAM and Communications Server

Table 7 compares host parameters to Communications Server parameters for IBM Token-Ring Network connections.

Table 7. Host/PC Parameters Cross-Reference: IBM Token-Ring Network NTRI Definition
NTRI/NCP Communications Server Profile/Parameters Remarks
GROUP ECLTYPE = PHY DLC Type: LAN
LINE LOCADDR
Configure Connections
  LAN
    Destination address

The value set for this parameter under Communications Server must be the address of the IBM Token-Ring Network adapter in the host controller.


Token Ring with VTAM Switched Network and Communications Server

Table 8 compares host parameters to Communications Server parameters for IBM Token-Ring Network connections using a VTAM switched network.

Table 8. Host/PC Parameters Cross-Reference: IBM Token-Ring Network VTAM Switched Net
VTAM Communications Server Profile/Parameters Remarks
IDBLK=
Configure Node
  Local node ID
    Block ID

The host IDBLK must match the first 3 hexadecimal characters of the Local node ID, which defaults to X'05D' for Communications Server. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
IDNUM=
Configure Node
  Local Node ID
    Physical Unit ID

The host IDNUM must match the last 5 hexadecimal characters of the Local node ID. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
CPNAME=
Node Definition
  Configure Node
    Fully qualified CP
    name
    (second field)

Specify this parameter when using switched lines, or omit when using IDBLK= and IDNUM=.
LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.

MAXDATA
Configure LAN Device
  Maximum PIU size
  (265-65535)

These values do not have to match.
MAXOUT
Configure LAN Device
  Receive buffer count
  (2-64)

The Receive buffer count in Communications Server should be equal to the MAXOUT parameter on the host.


9370 IBM Token-Ring Network Adapter and Communications Server

Table 9 compares 9370 host parameters to Communications Server parameters for IBM Token-Ring Network connections.

Table 9. Host/PC Parameters Cross-Reference: IBM Token-Ring Network 9370 VTAM LAN
VTAM Communications Server Profile/Parameters Remarks
VBUILD TYPE = LAN DLC Type: LAN  
PORT MACADDR=
Configure Connection
  LAN
    Destination address

The destination address specified in the Communications Server customization must be the address of the 9370 IBM Token-Ring adapter.
PORT SAPADDR=04
Configure Connection
  LAN
    Remote SAP

These values must match.
ADDR=04 (outgoing only)
Configure Connection
  LAN
    Local SAP

These values must match.


3174 Controller and Communications Server

Table 10 compares 3174 controller parameters to Communications Server for IBM Token-Ring connections.

Table 10. Parameter Matching between a 3174 Token Ring and Communications Server
3174 Communications Server Profile/Parameters Remarks
Upper limit address greater than 104: CUA DLC Type: LAN
Token-Ring address for gateway
Configure Connections
  LAN
    Destination address

These values must match.
Ring transmission definition.
W= window max out,
F=0, W = 1-7,
F=1, W = 1-7,
F=2, W = 1-4,
F=3, W = 1-2

Configure Devices
  LAN
    Receive buffer count
    (1-8)

The Communications Server receive buffer count should be equal to 3174 W.


3174 Controller VTAM PU and Communications Server

Table 11 compares 3174 controller VTAM PU parameters to Communications Server for IBM Token-Ring connections.

Table 11. Host/PC Parameters Cross-Reference: IBM Token-Ring Network 3174 Controller VTAM PU and Communications Server
VTAM Communications Server Profile/Parameters Remarks
CUADDR (local) or ADDR (remote) (none) Mapped by 3174 controller to IBM Token-Ring address
MAXDATA (remote only)
Configure Devices
  LAN
    Maximum PIU size
    (99-65535)

The Maximum PIU size value set on the Communications Server workstation must match the value set on the host.
MAXOUT (remote only)
Configure Devices
  LAN
    Receive buffer count
    (2-64)

The Communications Server Receive buffer count should be equal to MAXOUT.
LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.


Ethernet with VTAM Switched Network and Communications Server

Table 12 compares host parameters to Communications Server parameters for Ethernet Network connections using a VTAM switched network.

Table 12. Host/PC Parameters Cross-Reference: Ethernet Network VTAM Switched Network
VTAM Communications Server Profile/Parameters Remarks
IDBLK=
Configure Node
  Local node ID
    Block ID

The host IDBLK must match the first 3 hexadecimal characters of the Local node ID, which defaults to X'05D' for Communications Server. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
IDNUM=
Configure Node
  Local Node ID
    Physical Unit ID

The host IDNUM must match the last 5 hexadecimal characters of the Local node ID. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
CPNAME=
Node Definition
  Configure Node
    Fully qualified CP
    name
    (second field)

Specify this parameter when using switched lines, or omit when using IDBLK= and IDNUM=.
LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.

MAXDATA
Configure LAN Device
  Maximum PIU size
  (265-65535)

These values do not have to match.
MAXOUT
Configure LAN Device
  Receive buffer count
  (2-64)

The Receive buffer count in Communications Server should be equal to the MAXOUT parameter on the host.


VTAM/NCP and Communications Server (SDLC)

Table 13 compares VTAM/NCP host parameters to Communications Server parameters for SDLC connections.

Table 13. Host/PC Parameters Cross-Reference: SDLC
VTAM/NCP Communications Server Profile/Parameters Remarks
NETID=
Configure Node
  Fully qualified CP name
  (first field)

This parameter can be used for both leased and switched lines. This parameter identifies the SNA network you connect to using Communications Server.
NAME PU
Always use a NAME PU. This PU name should be a name that is not the same as the local CP name so you can define an LU for the control point.
IDBLK=
Configure Node
  Local node ID
    Block ID

The host IDBLK must match the first 3 hexadecimal characters of the Local node ID, which defaults to X'05D' for Communications Server. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
IDNUM=
Configure Node
  Local Node ID
    Physical Unit ID

The host IDNUM must match the last 5 hexadecimal characters of the Local node ID. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
CPNAME=
Node Definition
  Configure Node
    Fully qualified CP
    name
    (second field)

Specify this parameter when using switched lines, or omit when using IDBLK= and IDNUM=.
LNCTL=SDLC DLC Type: SDLC-WAC, SDLC-MPA, COM Port (depends on hardware used) SDLC must be selected here. This parameter is used for both leased and switched lines.
LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.

NRZI=YES/NO
Configure Connections
  SDLC-WAC, SDLC-MPA,
  COM Port
    NRZI encoding

Communications Server uses USE_NRZI_ENCODING=0 and USE_NRZI_ENCODING=1.

This parameter is found only on PCMs for Modem Type: Synchronous Switched, Synchronous NonSwitched, and AutoSync.

The encoding scheme, NRZI or NRZ, must be configured the same way at both ends of a connection. If the encoding schemes do not match, the modems will connect but data transfer will not succeed and the connection will be disconnected by Communications Server after a link-level timeout (typically 40 seconds).

We recommend the NRZ encoding scheme when you connect to an X.25 network using an IBM Wide Area Connector.

DUPLEX= FULL/HALF
Configure Connections
  SDLC-WAC and
  COM Port only
    Full-duplex
    communication

The values set on each side must be consistent with the modem type and configuration. This parameter is used for both leased and switched lines.
(TRANSFR * BFRS) -47
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Maximum PIU size
    (265-4105)

The Maximum I-field size value must be less than or equal to the (TRANSFR * BFRS) - 47 indicated on the host. This parameter is used for both leased and switched lines.
MAXDATA=
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Maximum PIU size
    (265-4105)

These values do not have to match. This parameter is used for both leased and switched lines. The lowest value will be used.
MAXOUT=
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Receive window count
    (1-30)

The Receive window count in Communications Server should be equal to the MAXOUT parameter on the host. This parameter is used for both leased and switched lines.
ADDR=
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Link station address
    (01-FE)

These parameters must have the same value. This is coded in hexadecimal for both Communications Server and VTAM/NCP. This parameter is used for both leased and switched lines.


VTAM and Communications Server (APPC)

Table 14 compares VTAM host parameters to Communications Server parameters for APPC connections.

Table 14. Host/PC Parameters Cross-Reference: APPC
VTAM Communications Server Profile/Parameters Remarks
LU NAME
Configure Host LU
  Local LU name
   or:
Configure Node
  Fully qualified CP name
  (second field)


LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.

NETID APPL
Configure Partner LU 6.2
  Partner LU name

 
VTAM Interpret Table
Configure Partner LU 6.2
  Partner LU name

This is for dependent LUs only.
LOGMODE Table LOGMODE=
Configure Mode
  Mode name

These parameters must match.
LOGMODE Table RUSIZES=
Configure Mode
  Maximum RU size
  (256-32767)

Final values are negotiated.


VTAM and Communications Server (MPC)

Table 15 and Table 16 compare IOCP/HCD and VTAM host parameters to Communications Server parameters for Multi-Path Channel (MPC) connections.

Table 15. IOCP/HCD Parameters Cross-Reference: MPC
IOCP/HCD Communications Server Profile/Parameters Remarks

IOCP
  IODEVICE
    UNIT=SCTC



DLC Type: IBM-MPC

HCD
  Device Type
    SCTC



DLC Type: IBM-MPC

Table 16. VTAM Parameters Cross-Reference: MPC
VTAM Definition Statement Operand Communications Server Profile/Parameters Remarks
VBUILD,TYPE=TRL LNCTL=MPC DLC Type: IBM-MPC
MPCLEVEL=HPDT
Communications Server IBM-MPC connections require HPR/HPDT
MAXBFRU
Configure MPC DLC
  Maximum PIU size

May affect performance and/or VTAM storage use
MAXREADS
Configure MPC DLC
  Receive Buffer Count

May affect performance and/or VTAM storage use
READ Configure MPC DLC The list of VTAM READ IODEVICE addresses must correspond to the Communications Server MPC DLC list of READ subchannels
WRITE Configure MPC DLC The list of VTAM WRITE IODEVICE addresses must correspond to the Communications Server MPC DLC list of WRITE subchannels
VBUILD,TYPE=LOCAL CONNTYPE=APPN
Configure Connections
  IBM-MPC
    APPN Support



Communications Server IBM-MPC connection requires APPN.
XID=YES
Configure Connections
  IBM-MPC
    APPN Support



Communications Server IBM-MPC connection requires PU2.1.
CPCP=YES
Configure Connections
  IBM-MPC
    APPN Support



Communications Server IBM-MPC connection requires APPN.
HPR=YES
Configure Connections
  IBM-MPC
    HPR Support



Communications Server IBM-MPC connection requires HPR.
NN
Configure Node
  Node type



VTAM PU node type must match Communications Server definition.
DELAY
May affect performance and/or VTAM CPU use


ES/9000 and Communications Server (SDLC)

Table 17 compares 9370 Information System parameters to Communications Server parameters for SDLC connections.

Table 17. Host/PC Parameters Cross-Reference: 9370 Information System via SDLC
9370/VTAM Communications Server Profile/Parameters Remarks
QFI: Non-return -to-zero inverted (microcode configuration)
Configure Connections
  SDLC-WAC, SDLC-MPA,
  COM Port
    NRZI encoding

These parameters must match. This parameter is used for both leased and switched lines.

Communications Server uses USE_NRZI_ENCODING=0 and USE_NRZI_ENCODING=1.

This is the synchronous data stream.

QFI: Protocol (microcode configuration) VTAM: GROUP LNCTL=SDLC
DLC Type
  SDLC-WAC, SDLC-MPA
  COM Port

The microcode and VTAM parameters must match. This parameter is used for both leased and switched lines.
MAXDATA
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Maximum PIU Size
    (265-4105)

These values do not have to match. This parameter is used for both leased and switched lines.
MAXBFRU * IOBUF size
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Maximum PIU Size
    (265-4105)

The Maximum I-field size value must be equal to or less than the MAXBFRU times IOBUF size indicated on the host. This parameter is used for both leased and switched lines.
MAXOUT=
Configure Devices
  Receive window count
  (1-30)

The Receive window count in Communications Server should be equal to the MAXOUT parameter on the host. This parameter is used for both leased and switched lines.
ADDR=
Configure Devices
  Link station address
  (01-FE)

The values set for these parameters must match. This parameter is used for both leased and switched lines.
IDBLK=
Configure Node
  Local Node ID
    Block ID

The host IDBLK must match the first 3 hexadecimal characters of the Local node ID, which defaults to X'05D' for Communications Server. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
IDNUM=
Configure Node
  Local node ID
    Physical unit ID

The host IDNUM must match the last 5 hexadecimal characters of the Local node ID. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
CPNAME=
Configure Node
  Fully qualified CP name
  (second field)

Specify this parameter when using switched lines, or omit when using IDBLK= or IDNUM=.
LOCADDR
Configure Host LUs
    NAU address

LOCADDR and NAU parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide. This parameter is used for both leased and switched lines.


Host and Communications Server (DLUR)

Table 18 compares host and Communications Server parameters for VTAM connections over DLUR.

Table 18. VTAM Communications Server Parameter Cross-Reference: Using DLUR
VTAM Communications Server Remarks
IDBLK=
Configure DLUR PUs
  Block ID

The IDBLK must match the first 3 hexadecimal characters of the Node ID, that defaults to X'05D' for Communications Server Specify this parameter when NOT using CPNAME=.
IDNUM=
Configure DLUR PUs
  Physical unit ID

The IDBLK must match the last 5 hexadecimal characters of the Node ID. Specify this parameter when NOT using CPNAME=.
CPNAME=
Configure DLUR PUs
  PU name

The CPNAME must match the local PU name. Specify this parameter when NOT using IDNUM= and IDBLK=.

Table 19 lists the following parameters on the PATH statement that are used when establishing a connection from the host to the workstation.

Table 19. VTAM Communications Server DLUR Parameter Matching Connection from Host to Workstation
VTAM Communications Server Remarks
DLURNAME=
Configure Node
  Fully qualified CP name
  (second field)

The DLURNAME provides the name of the DLUR node that owns the DLUR PU. For Communications Server, this is the fully qualified CP name.

DLCADDR=
  (1,C,INTPU)


Required. This parameter tells the DLUR that the connection is for an internal PU.
DLCADDR=(2,X,zzzzzzzz)
Configure DLUR PUs
  Block ID and
  Physical unit ID

The zzzzzzzz in DLCADDR=(2,X,zzzzzzzzz) must match the Node ID. Specify this parameter when NOT using DLCADDR=(3,C,puname).

DLCADDR=
  (3,C,puname)


Configure DLUR PUs
  PU name

The PU name in DLCADDR=(3,C,puname) must match Local PU name. Specify this parameter when NOT using DLCADDR=(2,X,zzzzzzzz).


NPSI and Communications Server (X.25)

Communications Server X.25 support enables the transmission of SNA frames across an X.25 network. X.25 treats SNA frames as raw data and transmits them as data-within-data packets. The two network nodes are not directly connected, but both are connected to an intermediary called the packet-switching data network (PSDN). The X.25 network can comprise any of the X.25 connectivities.

The software that interacts with the PSDN and packages the SNA data into packets and extracts it intact is an integral part of Communications Server. On the S/370 host side, the X.25 functions are handled by a separate software product called X.25 Network Control Program Packet Switching Interface (NPSI). The NPSI definitions are generated along with the NCP and the NPSI software runs in harmony with the NCP in the same 3705, 3725, 3720, or 3745 controller.

The majority of the X.25 parameters specified in both Communications Server and NPSI take values that are agreed upon by you and the X.25 network provider rather than between the two nodes. For example, with an SDLC connection on a nonswitched line, the host controller (NCP) is configured to poll a particular secondary address. Communications Server is configured to respond to that address on a physical link between the Communications Server workstation and the host.


NPSI Connections over X.25

Table 20 compares host and Communications Server parameters for NPSI connections over X.25.

Table 20. Host/PC Parameter Cross-Reference: NPSI Connections over X.25
NPSI Communications Server Profile/Parameters Remarks
X25.LINE TYPE=
DLC Type
  X.25 COM Port,
  X.25-WAC

Specify TYPE=P for PVCs and TYPE=S for SVCs for NPSI X.25 line definition.
CALL= (only for type = S)
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Virtual circuit ranges

Virtual circuit ranges must match your X.25 network subscription.
MAXDATA=
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Maximum PIU size
    (256-4105)

These values do not have to match.
VWINDOW
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Window size
    (1-7)

The SVC/PVC window size must match the X.25 subscriptions.
MWINDOW
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Frame values
      Window size
      (1-7)


FRMLGTH
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Frame sequence
      Modulo

The host FRMLGTH value must be at least MAXPKT +3 when running Modulo 8 or MAXPKT +4 when running Modulo 128. The host and Communications Server Modulo size and the packet sizes must match your X.25 subscription.
MAXPKTL
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Packet size

The host SVC/PVC packet sizes must match the X.25 subscription value.


VTAM/NCP and Communications Server (X.25)

Table 21 compares host and Communications Server parameters for X.25 (VTAM/NCP).

Table 21. Host/PC Parameters Cross-Reference: X.25 (VTAM/NCP)
VTAM/NCP Communications Server Profile/Parameters Remarks
NETID=
Configure Node
  Fully qualified CP name
  (first field)

This identifies the SNA network you connect to using Communications Server.
PU NAME
Always use a PU name. This PU name should not be the same as the local CP name so you can define an LU for the control point.
IDBLK=
Configure Node
  Local node ID
    Block ID

First 3 hex digits of the Local node ID, which defaults to X'05D' for Communications Server. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
IDNUM=
Configure Node
  Local node ID
    Physical unit ID

The host IDNUM must match the last 5 hexadecimal characters of the Local node ID. Specify this parameter when using switched lines, or omit this parameter if you use CPNAME=.
CPNAME=
Configure Node
  Fully qualified CP name
  (second field)

Specify this parameter when using switched lines, or omit when using IDBLK= and IDNUM=.
(TRANSFR * BFRS) - 47
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Maximum PIU size
    (265-4105)

The Maximum PIU size must be equal to the value set on the host.
MAXDATA=
Configure Devices
  X.25 COM Port,
  X.25-WAC
    Maximum PIU size
    (265-4105)

These values do not have to match.
LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.


APPC over X.25

Table 22 matches the parameters for a Communications Server workstation running advanced program-to-program communications (APPC) connecting to a host by way of X.25.

Table 22. Host/PC Parameters Cross-Reference: APPC on an IBM Token-Ring Network Using X.25 to a Host
NCP Communications Server Profile/Parameters Remarks
LU NAME
Configure Local LU 6.2
  Local LU name
   or:
Configure Node
  Fully qualified CP name
  (second field)


LOCADDR
Configure Host LUs
    NAU address

These parameters must have the same value. For independent LUs, VTAM recommends creating a CDRSC definition or using the DYNLU operand instead of coding LOCADDR=0. For more information on coding CDRSC definitions for independent LUs, refer to the VTAM Network Implementation Guide

No host definitions are required for dependent LUs if SDDLU or dynamic definition is used for independent LUs on VTAM 3.4 or later.

NETID APPL
Configure Partner LU 6.2
  Partner LU name

 
VTAM Interpret Table
Configure Partner LU 6.2
  Partner LU name

This is for dependent LUs only.
LOGMODE Table LOGMODE=
Configure Mode
  Mode name

These parameters must match.
LOGMODE Table RUSIZES=
Configure Mode
  Maximum RU size
  (256-32767)

These values must match.


AS/400 Host Line Definitions

AS/400 host line definitions include matching OS/400 host program parameters with Communications Server parameters. Table 23 contains the SDLC line parameters.

Table 23. AS/400 Communications Server Parameters Cross-Reference: OS/400 Host Program Line Definition
OS/400 Communications Server Profile/Parameters Remarks
NRZI= Data Encoding
Configure Connections
  SDLC-WAC, SDLC-MPA,
  COM Port
    NRZI encoding

Communications Server uses USE_NRZI_ENCODING=0 and USE_NRZI_ENCODING=1.

This parameter is found only on PCMs for Modem Type: Synchronous Switched, Synchronous NonSwitched, and AutoSync.

Modem data rate select
Configure Devices
  COM Port only
    Configure modem

The parameters on both systems for modem connection types, asynchronous switched, must match.
Maximum frame size (MAXFRAME)
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Receive window count
    (1-30)

Asynchronous nonswitched values do not have to match.
Maximum outstanding frames (MAXOUT)
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Receive window count
    (1-30)

The Receive window count in Communications Server should be equal to the MAXOUT parameter on the AS/400 host.


AS/400 Host Controller Definitions

Defining the AS/400 host controller includes matching OS/400 host program parameters with Communications Server parameters.

Table 24 shows the OS/400 host program parameters.

Table 24. AS/400 Communications Server Parameters Cross-Reference: Controller Parameters
OS/400 Communications Server Profile/Parameters Remarks
Linktype: *SDLC
DLC Type
  SDLC-WAC, SDLC-MPA
  COM Port

Link type on both systems must match. This parameter is on the line description, but include for completeness.
Attached Nonswitched Line
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Switched line

This parameter is for nonswitched connections. This value must match a previously defined host line definition.
Switched Line List (none) This parameter is for switched connections. This value must match a previously defined host line definition.
Maximum frame size
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Maximum PIU size
    (265-4105)

These values do not have to match.
Remote network identifier
Configure Node
  Fully qualified CP name
  (first field)

These values must match.
Remote control point name
Configure Node
  Fully qualified CP name
  (second field)

These values must match.
Data link role:
Configure Connections
  SDLC-WAC, SDLC-MPA,
  COM Port
    Link station role

The parameters on both systems are complementary. If the host role is primary the Communications Server workstation must be configured as secondary or negotiable. Unless multipoint (*MP) is used, it is best to set the data link role to negotiable (*NEG).
Station address
Configure Devices
  SDLC-WAC, SDLC-MPA,
  COM Port
    Link station address
   (01-FE)

These values must match.
APPN CP session support: (Yes/No)
Configure Connections
  SDLC-WAC, SDLC-MPA,
  COM Port
    APPN Support

These must match if CP-CP sessions are desired.
APPN node type:
Configure Connections
  SDLC-WAC, SDLC-MPA,
  COM Port
    Adjacent CP type

These values must match.


AS/400 Host Device Definitions

The AS/400 host can create a device definition when Communications Server workstation connects without a previously defined device definition.

Table 25 contains the OS/400 host program device parameters.

Table 25. AS/400 Communications Server Parameters Cross-Reference: Device Parameters
OS/400 Communications Server Profile/Parameters Remarks
Remote location name
Configure Local LU 6.2
  Local LU name
   or:
Configure Node
  Fully qualified CP name
  (second field)

These values must match.
Attached controller (none) This parameter is for nonswitched connections. This value must match a previously defined host line definition.
Local location name   Use the default provided.
Remote network identifier
Configure Node
  Fully qualified CP name
  (first field)

Use the default provided.
Mode
Configure Mode
  Mode name

Use the default provided.


AS/400 Host Line Description and Communications Server

Table 26 contains the AS/400 host program line description.

Table 26. Host/PC Parameters Cross-Reference: Line Description
OS/400 Communications Server Profile/Parameters Remarks
Local adapter address:
Configure Connections
  LAN destination address

The two addresses must match to communicate.


AS/400 Host Controller Description and Communications Server

Table 27 contains the OS/400 host program controller description.

Table 27. Host/PC Parameters Cross-Reference: Controller Description
OS/400 Communications Server Profile/Parameters Remarks
Active switched line (none) This parameter is for nonswitched connections. This value must match a previously defined host line definition.
Remote control point
Configure Node
  Fully qualified CP name
  (second field)

The names must match.
Remote network identifier
Configure Node
  Fully qualified CP name
  (first field)

Use the default or match the parameters if different from the AS/400 local network ID.
Model controller description
This parameter must be YES if the AS/400 uses a connection network.
Connection network ID  and Connection network CP name
Configure Connection Networks
  Connection network name

These values must match for all nodes participating in a connection network.


AS/400 Twinaxial Descriptions

Table 28 contains the AS/400 twinaxial description.

Table 28. Host/PC Parameters Cross-Reference: Controller Description
AS/400 Communications Server Profile/Parameters Remarks
Attached nonswitched line (none) This parameter is for nonswitched connections. This value must match a previously defined host line definition.
Remote control point
Configure Node
  Fully qualified CP name
  (second field)

The names must match.
Remote network identifier
Configure Node
  Fully qualified CP name
  (first field)

Use the default or match the parameters if different from the AS/400 local network ID.
Data link role=*SEC:
Configure Connections
  SDLC-WAC, SDLC-MPA
  COM Port
    Link station role

The parameters on both systems are complementary. If the host role is primary, the Communications Server workstation must be configured as secondary or negotiable. Unless multipoint (*MP) is used, it is best to set the data link role to negotiable (*NEG).


AS/400 Host Line Definitions (X.25)

AS/400 host line definitions include matching OS/400 host program parameters with Communications Server parameters. Table 29 contains the X.25 line parameters.

Table 29. AS/400 Communications Server Parameters Cross-Reference: OS/400 Host Program Line Definition (X.25)
OS/400 Communications Server Profile/Parameters Remarks
Local Network Address
Configure Devices
Local Address



Both addresses are usually determined by your network provider.
Connection Type
Configure Devices
X.25-COM Port
X.25-WAC
Switched Line



Connection Type on both systems must match.
X.25 DCE Support
N/A

Must be set to YES, if the connection between the two systems is point-to-point, without going through an X.25 network.
Maximum Frame Size
Configure Devices
X.25-COM Port
X.25-WAC
Maximum PIU Size



Maximum Frame Size on both systems must match.
Default Packet Size
Configure Devices
X.25-COM Port
X.25-WAC
Packet Size



This value is determined by your network provider, and is the same for Transmit and Receive.
Maximum Packet Size N/A This value is determined by your network provider.
Modulus
Configure Devices
X.25-COM Port
X.25-WAC
Sequencing



This value is determined by your network provider.

Default Window Size


Configure Devices
X.25-COM Port
X.25-WAC
Window Size



This value is determined by your network provider, and is the same for Transmit and Receive.
Insert Network Address
Configure Devices
X.25-COM Port
X.25-WAC

This value is determined by your network provider, and should be the same for both systems.

Logical Channel Entries


Configure Devices
X.25-COM Port
X.25-WAC
Virtual Circuit
Ranges

These values are determined by your network provider and your X.25 virtual circuit type.


AS/400 Host Controller Definitions (X.25 PVC)

Defining the AS/400 host controller includes matching OS/400 host program parameters with Communications Server parameters.

Table 30 shows the OS/400 host program parameters for X.25 PVC.

Table 30. AS/400 Communications Server X.25 PVC Parameters Cross-Reference: Controller Parameters
OS/400 Communications Server Profile/Parameters Remarks
X.25 logical channel ID
Configure Connections
  X.25 COM Port,
  X.25-WAC
    Logical Channel Number

These values are determined by your network provider.
Linktype: *X25 Configure Connections Link types on both systems must match.
Switched Connection: *NO
All PVCs are non-switched.
Maximum Frame Size
Configure Devices
X.25-COM Port
X.25-WAC
Maximum PIU Size



The Maximum Frame Size values do not need to match.
Data Link Role
Configure Devices
X.25-COM Port
X.25-WAC
Link Station Role



The parameters on both systems are complementary. If the host role is primary the Communications Server workstation must be configured as secondary or negotiable.
X.25 Network Level
Configure Devices
X.25-COM Port
X.25-WAC
CCITT Compliance



These values are determined by your network provider.
X.25 Link Level Protocol: *QLLC
This value must be QLLC.


AS/400 Host Controller Definitions (X.25 SVC)

Defining the AS/400 host controller includes matching OS/400 host program parameters with Communications Server parameters.

Table 31 shows the OS/400 host program parameters for X.25 SVC.

Table 31. AS/400 Communications Server X.25 SVC Parameters Cross-Reference: Controller Parameters
OS/400 Communications Server Profile/Parameters Remarks
Linktype: *X25 Configure Connections Link types on both systems must match.
Switched Connection: *YES
All SVCs are switched.
Maximum Frame Size
Configure Devices
X.25-COM Port
X.25-WAC
Maximum PIU Size



The Maximum Frame Size values do not need to match.
Connection Number
Configure Devices
X.25-COM Port
X.25-WAC
Local DTE address



This value is determined by your network provider.
Data Link Role
Configure Devices
X.25-COM Port
X.25-WAC
Link Station Role



The parameters on both systems are complimentary. If the host role is primary the Communications Server workstation must be configured as secondary or negotiable.
X.25 Network Level
Configure Devices
X.25-COM Port
X.25-WAC
CCITT Compliance



These values are determined by your network provider.
X.25 Link Level Protocol: *QLLC
This value must be QLLC.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]