installation and configuration manual for unix

8/11/2019 Installation and Configuration Manual for UNIX

1/54

0102-66-02-OUNX6600

____________________

Inter.Pel 6.6

____________________

Installation & Configuration Manual for UNIX

____________________


2/54

Inter.Pel 6.6 SOPRA.

The information contained in this document is subject to revision without prior notice and shallnot be regarded as binding on SOPRA. The rights relative to the use of the software describedin this document are granted as part of the licensing contract and the software shall be used

only in accordance with the terms of that contract. Any reproduction or transmission in anyform or by any process whatever (electronic or mechanical, photocopy and recording included)and for any purposes other than the personal use of the purchaser without the writtenauthorization of SOPRA is strictly prohibited.

Copyright 2003 SOPRA.All rights reserved. All trademarks registered.November 2003.


3/54

Contents Installation & Configuration Manual for UNIX Page iii__________________________________________________________________________________________________


CONTENTS

1. ABOUT THIS MANUAL 1

1.1. Abstract 1

1.2. Reading guidelines 1

2. INTER.PEL DOCUMENTATION 2

3. PRE-REQUISITES 3

3.1. Disk space 3

3.2. Software protection key 3

3.3. Other information 3

4. DOWNLOADING 4

4.1. Delivery support 4

4.2. Downloading Inter.Pel 4

4.3. File descriptions 54.3.1. Directory layout 54.3.2. Directory contents 6

5. INTER.PEL CONFIGURATION 8

5.1. Configuration procedure 85.1.1 Using pelsetup menu interface 85.1.2 Using pelconf line command 85.1.3 Stage of Inter.Pel configuration 8

5.2. Configuration files 9

5.3. Network configuration in Inter.Pel 95.3.1. TCP/IP 95.3.2. X25 105.3.3. SNA LU6.2 10

5.4. Address configuration for Inter.Pel partners 105.4.1. TCP/IP 105.4.2. X25 115.4.3. SNA LU6.2 11

6. START/STOP PROCEDURE 12


4/54

Contents Installation & Configuration Manual for UNIX Page iv__________________________________________________________________________________________________


6.1. Checking Before starting 126.1.1. For TCP/IP subsystem 126.1.2. For X25 subsystem 126.1.3. For SNA LU6.2 subsystem 12

6.2. Initialize Inter.Pel monitor 12

6.3. Start/Stop Inter.Pel monitor 12

6.4. Start/Stop graphical user interface server 13

6.5. Start/Stop internet user interface server 13

6.6. Checking Inter.Pel processes 136.6.1. Checking after starting Inter.Pel monitor 146.6.2. Checking after stopping Inter.Pel monitor 15

6.6.3. Checking status process in trace files 15

7. APPENDIX FOR AIX 17

7.1. Operating system versions 17

7.2. Available option 17

7.3. TCP/IP network interface 177.3.1. Hardware and software prerequisites 177.3.2. TCP/IP configuration 17

7.4. X25 network interface for Bull/AIX 187.4.1. Configuring Inter.Pel for XTI/XX25 187.4.2. Configuring Inter.Pel for MAD/MAX3 X25 18

7.5. X25 network interface for IBM/AIX 197.5.1. Configuring Inter.Pel for NPI/X25 197.5.2. Configuring Inter.Pel for COMIO/X25 19

7.6. LU62 network interface 207.6.1. Hardware and software Prerequisites 207.6.2 Configuring Inter.Pel for CS5 20

7.6.2.1 Configuring the SNA connectivity 207.6.2.2. Configuring APPC/CPIC resources 237.6.2.3. Summary of SNA installation for Inter.Pel 28

7.6.3. LU62 Configuration with SNA server 6000 297.6.3.1. CPI - C side information profile 297.6.3.2. CPI-C transaction 30

7.6.4. LU62 Configuration with SNA services 327.6.4.1. CPI side information. 327.6.4.2. CPI transaction 32

8. APPENDIX FOR HPUX9000 34


5/54

Contents Installation & Configuration Manual for UNIX Page v__________________________________________________________________________________________________



8.2. Available option 34


8.4. X25 network interface for HPUX 358.4.1. Hardware and software prerequisites 358.4.2. X25 configuration 35

8.5. LU62 network interface 368.5.1. Hardware and software prerequisites 368.5.2. LU62 configuration 36

8.5.2.1. Configuring the SNA connectivity 36

8.5.2.2. Configuring APPC/CPIC resources 398.5.2.3. Summary of SNA installation for Inter.Pel 44

9. APPENDIX FOR SOLARIS 45


9.2. Available options 45

9.3. TCP/IP network interface 459.3.1. Hardware and software prerequisites 45

9.3.2. TCP/IP configuration 45

9.4. X25 network interface 469.4.1. Configuring Inter.Pel for X25 SOCKET interface. 46

9.5. LU6.2 network interface 46

10. APPENDIX FOR LINUX 47


10.2. Available options 47



6/54

Contents Installation & Configuration Manual for UNIX Page vi__________________________________________________________________________________________________



7/54

1. About this manual Installation & Configuration Manual for UNIX Page 1__________________________________________________________________________________________________

Inter.Pel .6 SOPRA.

1. About this manual

1.1. Abstract

This guide is intended for those responsible for UNIX platform management.

It describes how to download, install, and configure Inter.Pel product on UNIXplatforms.

1.2. Reading guidelines

To read this document, you must have basic knowledge of UNIX platform, ofTCP/IP, X25, and SNA networks.

Before using this manual, you must have a basic understanding of Inter.Pel .5.1

product presented in ProductOverviewpublication.


8/54

2. Inter.Pel documentation Installation & Configuration Manual for UNIX Page 2__________________________________________________________________________________________________

Inter.Pel .6 SOPRA.

2. Inter.Pel documentation

The Inter.Pel documentation contains two categories of technical publications:

- Generic manuals: they are designed for all platforms running Inter.Pel- Specific manuals containing platform dependent features. Each platform

is provided with its own set of specific manuals

Title Type Function

Product Overview Overview Presentation

User's Guide Services How To Use

On-line commands Manual Utilities Operations & Mgmt

Protocols Guide How it works Understanding & Using transfer protocols

Messages & Codes Description Interpreting Information and errors messages

C programming Manual

COBOL programming Manual

Programming Integration of user applications

Installation & Configuration Guide(1) Install & Config Install & Config

Platform Specific Document (1) Specific supplement OS specific features

Getting Started (1) Running a transfer Quick User's Guide

PELISF Manual (2) Utilities Script mode operator's interface

I.H.M. Manual (2) Utilities Graphical operator's interface

PELOP Manual (2) Utilities Character mode operator's interface

(1): Specific manual: one document for each platform.(2): Document provided when the related interface is supplied for the platform.


9/54


10/54

4. Downloading Installation & Configuration Manual for UNIX Page 4__________________________________________________________________________________________________

Inter.Pel .6 SOPRA.

4. Downloading

4.1. Delivery support

The monitor is delivered on a CD-ROM. For other types of installation medium,contact the SOPRA delivery department.

The CD-ROM may contain others products from SOPRA.

4.2. Downloading Inter.Pel

Depending on your platform, you must use an iso9660 or a cd_9660 file systemtype for mounting the CD-ROM. As a precaution, enter the following commandfor more information:

$ man mount

If you cant automatically load the CD-ROM, you must use the mountcommand.

Example for an AIX platform:

$ mount t cdrfs /dev/cd0 /cdrom

To find your Inter.Pel product files, you must go to INTERPEL/V651 directory.Finally, choose the directory corresponding to the platform you want to install (ex:AIX, SUN, HPUX, etc..).

The directory contains the following two files:

- an Inter.Pel product file with the suffix .tar.Z,- a descriptive file with the suffix .txt.

The *.tar.z file contains the applicable files to use Inter.Pel Monitor.The descriptive file gives pre-requisites and options delivered with the productfiles.

The pathname of this file is of the following pattern:

PPP-IPEL-DDDDDD-651-P-X-X.tar.Z

PPP : identifies the target UNIX platform (ex: AIX, SUN,etc..).IPEL : is an abstract for Inter.Pel product name.DDDDDD : is a time-stamp that identifies the master used to create

the installation material, for example: 000122.651 : is the Inter.Pel version.

P-X-X : is an internal number identifying the technical state.


11/54


Inter.Pel .6 SOPRA.

To install your monitor, you must choose a home directory for Inter.Pel and runthe following command (example for AIX):

$ compress -d < /cdrom/INTERPEL/V650/AIX-IPEL-000105-651-P-2-3.tar.Z |tar xvf -

This command extracts Inter.Pel product files and copies them into your currentdirectory, creating sub-directories as needed, according to the directory layoutdescribed hereafter .

It is recommended that you download Inter.Pel files under the account that will beused at product startup and stopping.

You can run Inter.Pel either under a normal user account or under the rootaccount. It is not recommended that you run Inter.Pel under the root account,unless absolutely necessary.

Application programs that submit transfer requests must ensure that the Inter.Pelaccount is granted with suitable rights for accessing the files to transmit. If it isnot, Inter.Pel processes will not be permitted to open the corresponding files andthe file transfers will not be carried out.

4.3. File descriptions

4.3.1. Directory layout

Inter.Pel files are stored in directories with the following layout:

bin

incnlt

frenchpelopsetup

englishpelopsetup

objrun_time

arcdata

etcscriptstemplateresolved

tmpsrc

cobolexitclntexituserisfuseritpuexsamples


12/54


Inter.Pel .6 SOPRA.

4.3.2. Directory contents

The paths are named from the installation directory.

./machine

Identifies the operating System on which Inter.Pel is running.

./userprof.sh

Inter.Pel script used to set up session environment variables prior tocompilation of programs using API or exits functions.

./pelsetup (English)./pelsetup_fr (French)

Program used to configure Inter.Pel Monitor.

/bin

Executable program files.

./inc

Header files (*.h) for EXIT and C API programming.

./nlt/french

French messages and screen forms.

./nlt/french/pelop

French forms, menus ,and help files for the operator interface in charactermode.

./nlt/french/setup

French forms, menus, and help files for the configurator interface incharacter mode.

./nlt/english

English messages and screen forms.

./nlt/english/pelop

English forms, menus and help files for the operator interface in charactermode.

./nlt/english/setup

English forms, menus, and help files for the configurator interface incharacter mode.


13/54


Inter.Pel .6 SOPRA.

./obj

Object files and libraries for editions of user program links.

./run_time/arc

Archived log files and transfer purge operation reports.

./run_time/data

Software data files specific to the Inter.Pel product: sites, applications,mailbox ... (*.dat).

./run_time/etc

Shell profile scripts (profile, csprofile), conffile and miscellaneous files.

./run_time/scripts/template

User scripts template files.

./run_time/scripts/resolved

Resolved user scripts.

./run_time/tmp

Execution report file (*.out, *.err).

./src/cobol

Cobol API definitions files and sample sources.

./src/exituser

Inter.Pel internal USER EXIT's programming examples.

./src/exitclnt

Inter.Pel client logging USER EXIT's programming examples.

./src/isfuser

Inter.Pel USER functions executed by interpreter PELISF.

./src/itpuex

Sample source files for external user exits.

./src/samples

Inter.Pel C API's programming example.


14/54

5. Inter.Pel configuration Installation & Configuration Manual for UNIX Page 8__________________________________________________________________________________________________

Inter.Pel .6 SOPRA.

5. Inter.Pel configuration

5.1. Configuration procedure

5.1.1 Using pelsetup menu interface

An installation program, named pelsetup, is provided. This tool is an interactiveoperator interface of Inter.Pel version 6.6 that configures Inter.Pel Monitor. Thisoperators interface appears in the form of screens containing options or namedfiles.

The pelsetupcommand operates in English by default. To start the interface inFrench, enter command pelsetup_fr.

This interface also provides help screens in the fields of each object. They are

displayed either by pressing the Ctrl orE keys.Note that pelsetupprogram configures both the monitor and the server part forClient Graphical User Interface or Client Internet User Interface (if selected).

5.1.2 Using pelconf line command

The pelconfon-line command must not be used to configure the product underUNIX. You muse use either pelsetupor pelsetup_frcommands instead.

5.1.3 Stage of Inter.Pel configuration

Inter.Pel configuration consists of the following steps:

1. Run pelsetupprogram and configure all Inter.Pel services you need foryour application.

2. If the network security has been selected, the corresponding securityfiles for IP network and X25 network may have to be filled up asneeded.

3. Initialize Inter.Pel resources, notably the Mailbox file by executing thecommand pelinit.

4. Start Inter.Pel using the pelstartcommand.

5. Define all other objects (Sites, Applications, ...) needed by yourapplication, using user tools supplied with Inter.Pel. You can use thepeladmshell commands, the pelop character mode Interface ,or theClient GUI interface.


15/54


Inter.Pel .6 SOPRA.

5.2. Configuration files

The pelsetupprogram creates configuration files under

/run_time/etcdirectory, which are text files containingparameters used by Inter.Pel at start-up.

The following configuration files are created for all UNIX platforms:

conffile : Global resources configuration parametersprofile : Environment variables

csconfig.ini : Server configuration file for graphical user interfacescsprofile : Server environment variables for graphical interfaces

If the network security feature of Inter.Pel has been selected, the followingadditional configuration files are created in /run_time/datadirectory:

tableip.adr : Security file for TCP/IPtablex25.adr : Security file for X25 access

See Inter.Pel User's Guide: "Using Network Security.

Specific additional configuration files may be produced, depending on the UNIXplatform. For example, an X25 configuration file is created during Inter.Pelconfiguration for SINIX machines.

5.3. Network configuration in Inter.Pel

5.3.1. TCP/IP

TCP/IP transport is supported by Inter.Pel for FTP, ODETTE, PEL and PeSITfamily of protocols. For Inter.Pel to use TCP/IP transport for a protocol, you mustindicate the hostname (or IP address) and the port number that is to be used toroute incoming calls to that protocol.

Each Inter.Pel protocol configured for TCP/IP must be assigned a different portnumber. You also must ensure that port numbers assigned to Inter.Pel protocolsare not already used by other applications running on your system.

It is recommended to select port numbers within the range 5000..32760. Eachvalue must be used once on the system. If you are using an X11 graphic display orintend to do so on your system, you must not select port number 6000 since it isthe port number used by the X Server to listen to X client connections.

See the Appendix on your platform for more details.


16/54


Inter.Pel .6 SOPRA.

5.3.2. X25

The actual X25 configuration parameters to enter at the installation step depend on

the X25 interface and/or on your UNIX systems. Basically, Inter.Pel must haveknowledge of parameters to use for selecting incoming connections from theNetwork. The information that is most commonly used to route X25 incomingcalls is the user-data field or the first 4 byte set of this field which is named

protocol-id. Some X25 interfaces also allow the routing of incoming connectionsby address fields. See the appendix corresponding to your platform for detailedinformation on these features.

Depending on the X25 interface type, Inter.Pel may require that it be providedwith information that addresses a specific X25 interface or line.

5.3.3. SNA LU6.2

Inter.Pel supports for LU6.2 communications are not available on all UNIXplatforms. See the appendix corresponding to your platform for detailedinformation on supported features.

Each LU6.2 session is handled by a separate Inter.Pel process. Processes that dealwith requestor sessions are started by Inter.Pel. For server sessions, transaction

programs (TP) must be defined in the LU6.2 sub-system. That sub-system isresponsible for starting an Inter.Pel LU6.2 server process on each incomingconnection.

5.4. Address configuration for Inter.Pel partners

5.4.1. TCP/IP

To create a destination SITE using TCP/IP, you must supply the remote machinename (if using a name server) or its dotted IP address (such as 193.56.234.50), andthe port number on which the remote FT protocol is listening.

Example:

The command

peladm create_site -pr PEL -a REMOTE_PEL_TCP -pi RPT0-ct TCP-dest_address 193.56.234.50/22200

creates a destination SITE based on protocol PEL (-pr PEL), whose alias name is"REMOTE_PEL_TCP" (-a REMOTE_PEL_TCP) and protocol ident "RPT0" (-piRPT0). To reach this site, Inter.Pel will use TCP/IP network (-ct TCP) and willcall the IP address 193.56.234.50 and the port number 22200. Note that the partnerapplication must be running in a platform with this IP address, and listening to this

port number.


17/54


Inter.Pel .6 SOPRA.

5.4.2. X25

To create a remote site reachable with X25, you have to define the remote X25

address, and user data and/or facilities if needed.

Example:

The command

peladm create_site -pr PEL -a REMOTE_PEL_X25-pi RPX0 -ct X25-dest_address-ud C9 -opt FB0012

creates a destination SITE based on protocol PEL (-pr PEL), whose alias name is"REMOTE_PEL_X25" (-a REMOTE_PEL_X25) and protocol ident "RPX0" (-piRPX0). To reach this site, Inter.Pel will use X25 network (-ct X25) to call requestwith "FB0012" facilities and user data "C9". Note that the partner application must

be running in a platform connected to X25 line.

5.4.3. SNA LU6.2

To create a destination SITE using SNA LU62, you have to specify a Networktype'lu62'. The field Machine nameis used to define the 'CPI-C SideInformation (also termedCPIC symbolic destination). The field Local LUcontains the 'local LU'.

Example for PEL protocol:

peladm create_site -pr PEL -a REMOTE_LU -pi RPX0-ct LU62-dest_address TOMVS@IPASOPL1@0

creates a destination site based on protocol PEL (-pr PEL), whose alias name is"REMOTE_LU" (-a REMOTE_LU) and protocol identity is "RPX0" (-pi RPX0).To reach this site, Inter.Pel will use SNA network (-ct LU62) and will call theaddress TOMVS@[email protected] corresponding and related SNA configuration parameters must have beendefined in the SNA configuration database of your system prior to creating

Inter.Pel Sites that utilize these parameters.On most UNIX systems, it is possible to define CPI-C side information profilesthat gather values for all SNA parameters needed to perform connections to theremote Site.


18/54

6. Start/Stop procedure Installation & Configuration Manual for UNIX Page 12__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

6. Start/Stop procedure

6.1. Checking Before starting

Before starting the Inter.Pel monitor, it is recommended to check the networkresources needed for communication between Inter.Pel and its remote sites.

6.1.1. For TCP/IP subsystem

You can check that a remote system can be reached by using the standard UNIXpingcommand with the hostname or IP address as an argument. See the pingdocumentation supplied with your UNIX system for detailed information.

6.1.2. For X25 subsystem

Most X25 subsystems are supplied with tools that allow the establishment ofconnections and the monitoring and tracing of X25 activity. You must refer to thedocumentation of your X25 sub-system and perform the recommended checks andtests.

6.1.3. For SNA LU6.2 subsystem

Check the SNA configuration, by activating each LU6.2 connection used byInter.Pel.

If sessions LU-LU can not be activated, check LU6.2 local and remote parameters.

If sessions LU-LU are activated, and the session establishment failed at filetransfer time, check if the remote site is active and the mode and the transactionname requested in 'CPI symbolic destination' are defined in the remote site.

If the problem remains, activate the audit function and the SNA trace and checkthe traced elements.

6.2. Initialize Inter.Pel monitor

Before starting your Inter.Pel, you must initialize your mailbox by the followingcommand:

pelinit

6.3. Start/Stop Inter.Pel monitor

Inter.Pel delivery supplies two utility programs named pelstart andpelstop whichare used to start or to stop the monitor.

Prior to any use of Inter.Pel program files, you must set the product environmentfor your UNIX session, by executing the Shell script named profile (it is createdunder /run_time/etc directory by the configuration utility):

$ . /run_time/etc/profile


19/54


20/54


Inter.Pel .1 SOPRA.

6.6.1. Checking after starting Inter.Pel monitor

When Inter.Pel is started, the pscommand must display at least the Inter.Pelsupervisor process (p_sup) and the Inter.Pel system process (p_sys).

Other processes are launched according to network resources and configuredprotocols.

For TCP/IP Network:

p_fpelsock (Use TCP/IP Network with PEL protocol)p_fsitsock (Use TCP/IP Network with PeSIT protocol)p_fodtsock (Use TCP/IP Network with ODETTE protocol)p_ftpsock (Use TCP/IP Network with FTP protocol)

For X25 Network:

p_x25.xxx with xxx: X25 Interface name

A p_x25.xxxprocess is launched for each protocol configured for X25. Then, ifseveral protocols are used with the X25 Network, you must count as manypx25.xxxprocesses as protocols that are used.

A protocol process is also launched if this protocol is not used with a TCP/IPNetwork. The list of the protocol processes is the following:

p_fpel (PEL protocol)p_fsit (PeSIT protocol)p_fodt (ODETTE protocol)p_ftp (FTP protocol)

For TCP/IP Network, protocol processes directly call the sub-system TCP/IP inorder to increase the performance of the transfer.

Note:when both PeSIT version E and PeSIT version D are configured, two processesexecuting either p_fsitsockor p_fsitimage must exist (one for each protocolversion).

If SSL/TLS has been configured for any protocol on either TCP or X25, theadditional process p_secs is also launched.

Example:On an AIX machine, using PeSIT protocol for TCP/IP and XTI Networkinterfaces and ODETTE protocol for XTI Network interface, the list of the

processes displayed by the command psis the following:

p_fsitsockp_x25.xtip_x25.xtip_fodt


21/54


Inter.Pel .1 SOPRA.

For SNA Network:

p_fpel62 (Use SNA Network with PEL protocol)

p_fsit62 (Use SNA Network with PeSIT protocol)

Only the protocols PEL and PeSIT are carried for SNA.

The SNA processes are not launched at the starting of Inter.Pel. They start only ifone connection takes place. Therefore, they are called dynamic processes.

Several processes for the same protocol can be displayed if several connectionsare taking place at the same time. These processes stop when the connections arereleased.

Message queues:

Inter.Pel uses message queues. With the ipcs command, you can check if themessage queues have been created.

$ ipcs q | grep

6.6.2. Checking after stopping Inter.Pel monitor

When Inter.Pel is stopped, no Inter.Pel process should be active.Use the command:ps -e | grep p_

6.6.3. Checking status process in trace files

When an Inter.Pel process detects a severe error condition, it writes a message toits standard output or error stream. These streams are redirected to files located inthe $p_home_dir/run_time/tmp/directory and each process writes to a differentfile, as follows:

SUP.out (SUPEVISOR traces)SYS.out (SYSTEM traces)SECS.out (SSL/TLS ancillary process traces)FT_PEL.out (Traces for PEL protocol)FT_PHSD.out (Traces for PeSIT D protocol)FT_PHSE.out (Traces for PeSIT E protocol)FT_ODT.out (Traces for ODETTE protocol)

FT_FTP.out (Traces for FTP protocol)TCP_PEL.out (TCP traces with PEL protocol)TCP_PHSD.out (TCP traces with PeSIT D protocol)TCP_PHSE.out (TCP traces with PeSIT E protocol)TCP_ODT.out (TCP traces with ODETTE protocol)TCP_FTP.out (TCP traces with FTP protocol)X25_PEL.out (X25 traces with PEL protocol)X25_PHSD.out (X25 traces with PHSD protocol)X25_PHSE.out (X25 traces with PHSE protocol)X25_ODT.out (X25 traces with ODT protocol)X25_FTP.out (X25 traces with FTP protocol)PELCPICR.XX.out (SNA traces for outgoing call with PEL protocol)PELCPICI.XX.out (SNA traces for incoming call with PEL protocol)


22/54


Inter.Pel .1 SOPRA.

PHDCPICR.XX.out (SNA traces for outgoing call with PHSD protocol)PHDCPICI.XX.out (SNA traces for incoming call with PHSD protocol)PHECPICR.XX.out (SNA traces for outgoing call with PHSE protocol)

PHECPICI.XX.out (SNA traces for incoming call with PHSE protocol)

In case of an Inter.Pel process that fails to start or exists abnormally, a messagerelated to the cause of the problem may have been written to one of these files.Checking the contents of these files can help diagnose problems preventingInter.Pel processes from operating properly.

Remark:

XX: PID of the process.


23/54

7. Appendix for AIX Installation & Configuration Manual for UNIX Page 17__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

7. Appendix for AIX

7.1. Operating system versions

- AIXV4.2,- AIXV4.3.

7.2. Available option

Interpel.Pel for AIX provides the following optional facility:

COBOL Application Program InterfaceThis API allows user application programs to submit transfer requests and toaccess the Inter.Pel mailbox while Inter.Pel is running. User Cobol programs must

be linked with the Microfocus Cobol run-time libraries.USER EXITS written in Cobol language are not supported.

7.3. TCP/IP network interface

7.3.1. Hardware and software prerequisites

Inter.Pel uses the BSD socket library services when it is configured for TCP/IPnetworking. These services are available as a standard feature under the AIXOperating System.For Inter.Pel to operate with TCP/IP, you must ensure that these services are

properly configured on your machines. You must refer to AIX manuals for the

configuration procedures of the system hardware and system software that addressTCP/IP services.

7.3.2. TCP/IP configuration

The following information is to be supplied to Inter.Pel for it to operate withTCP/IP:

- the local port numbers that are used by Inter.Pel in order to receiveincoming connections. A different port number must be assigned to eachconfigured File Transfer protocol. This information must be configured

prior to Inter.Pel startup and must not be changed while Inter.Pel is

running. You also must ensure that these port numbers are not currentlyin use and will not be attempted to be used by any other application onthe system. It is advised to choose port numbers in the range 5000-65000.

- either a host name or dotted IP address may be supplied to Inter.Pel asauthoritative host for incoming connections. You may use, the hostname of the local machine, the looped address (localhost or 127.0.0.1), oran empty address for this purpose.


24/54


Inter.Pel .1 SOPRA.

Inter.Pel parameters that apply to outgoing connections are gathered in Siteobjects. For each remote machine and each configured transfer protocol, a Siteobject must be created and supplied with the TCP/IP address and port number

expected by the remote machine for that protocol. This information must beentered using an Inter.Pel administration tool while Inter.Pel is running. TheWindows GUI Interface, the pelopscreen interface, or the peladmline-modecommand can be used to create Inter.Pel Sites.

The following is an example of Site creation using the peladmcreate_sitecommand for a site in PELprotocol at dotted IP address 193.56.234.50and portnumber 22001.

peladm create_site -pr PEL-a SITE1 -pi SITE1 -da 193.56.234.50/22001

Either the host name(when using DNS facilities), or the IP dotted address(suchas 193.56.234.50, for example) can be specified as IP destination addressfieldfor Sites intended to be connected to by Inter.Pel over TCP/IP.

7.4. X25 network interface for Bull/AIX

Inter.Pel supports both the MAD/MAX3 X25 and the XTI/XX25 access methodsunder Bull machines supplied with the AIX Operating System.The XTI/XX25 access method is recommended when fast X25 links are used.The system software that provides X25 services must have been installed andmust be operational prior to configuring Inter.Pel for X25.

7.4.1. Configuring Inter.Pel for XTI/XX25

The following parameters are required for Inter.Pel to operate with XTI/XX25:

- The device name associated with the XTI/XX25 interface.Inter.Pel uses /dev/dat/xpi_xd as default device. This device shouldexist if the XTI/XX25 software has been properly installed andconfigured.

- A call user data must be supplied for each protocol configured for X25incoming connections. A one to one relationship must be maintained

between protocols and call user data values. In other words, differentprotocols must be configured with different call used data.

7.4.2. Configuring Inter.Pel for MAD/MAX3 X25

The following parameters are required for Inter.Pel to operate with MAD/MAX3X25:

- the device name associated with the MAD kernel interface.Inter.Pel uses /dev/mad/000 as a default device. This device shouldexist if the MAD/MAX3 X25 software has been properly installed andconfigured,

- the local address of the X25 physical interface. This address mustmatch the local address values that have been configured in the systemfor that interface,


25/54


Inter.Pel .1 SOPRA.

- for each protocol Inter.Pel may have to receive incoming connectionsfrom, a call user datahexadecimal string must be supplied. A one to onerelationship must be maintained between protocols and call user data

values. In other words, different protocols must be configured withdifferent call user data.

7.5. X25 network interface for IBM/AIX

Inter.Pel supports both the COMIO/X25 and the NPI/X25 access methods. Thelatter access method (e.g. NPI/X25) is recommended when fast X25 links areused.The system software that provides X25 services must have been installed andmust be operational prior to configuring Inter.Pel for X25.

7.5.1. Configuring Inter.Pel for NPI/X25

The following parameters are required for Inter.Pel to operate with NPI/X25:

- a token that identifies the X25 hardware interface and the kernel deviceinterface. This token is of the following pattern, where # is a digit thatdesignates the X25 line number: sx25# x25pkt.

Inter.Pel uses sx25a0 x25pkt as a default value. This valuecorresponds to X25 line number zero.

- for each protocol Inter.Pel may have to receive incoming connectionsfrom, a call user datahexadecimal string must be supplied. A one to onerelationship must be maintained between protocols and call user data

values. In other words, different protocols must be configured withdifferent call user data.

7.5.2. Configuring Inter.Pel for COMIO/X25

The following parameters are required for Inter.Pel to operate with COMIO/X25:

- a token that identifies the X25 hardware interface. This token is of thefollowing pattern, where character # designates the X25 line number:x25s #.

by default Inter.Pel uses x25s0that corresponds to X25 line numberzero.

- for each protocol Inter.Pel may have to receive incoming connectionsfrom, a xrouteentry must be supplied at Inter.Pel installation. Whenconfiguring those xrouteentries, the user must make sure that

parameters do not conflict in a way that may affect proper routing ofincoming connections to Inter.Pel File Transfer protocols. You must refer toAIX manuals for the description of the xroutecommand.


26/54


Inter.Pel .1 SOPRA.

7.6. LU62 network interface

7.6.1. Hardware and software Prerequisites

Inter.Pel can communicate over LU62 conversations using either SNA SERVERversion 3 or COMMUNICATION SERVER version 5 SNA sub-system.

7.6.2 Configuring Inter.Pel for CS5

Inter.Pel requires AIX Operating System 4.3 or a later version for the support ofCOMMUNICATION SERVER 5.

7.6.2.1 Configuring the SNA connectivity

This operation may highly vary depending on the actual topology of the SNAnetwork. You may use the X-motif GUI interface xsnaadminto configure theSNA connectivity on your system.

In brief, SNA connectivity configuration consists in defining the following SNAconfiguration items:

- the characteristics of the local node,- a portfor each hardware interface,- a link station for each adjacent host.

Follow respectively the below menu items under xsnaadminto achieve thisconfiguration:

local node

Services Connectivity Node Parameters

Port

Services Connectivity New Port

link station

Services Connectivity Link Station

The above configuration parameters are stored in the /etc/sna/sna_domn.cfgfile.To understand the parameters that address SNA connectivity, you must refer to therelated AIX Communication Server 5 documentation. Below are given someexcerpts of a sample sna_domn.cfgfile that illustrates some of the parametersinvolved in the SNA connectivity configuration data..

Example of local node configuration

[define_node]cp_alias = PXRS10description = ""fqcp_name = SOPRA.PXRS10

node_type = NETWORK_NODE


27/54


Inter.Pel .1 SOPRA.

mode_to_cos_map_supp = NOmds_supported = YESnode_id =

max_locates = 1500dir_cache_size = 255max_dir_entries = 0locate_timeout = 0reg_with_nn = YESreg_with_cds = YESmds_send_alert_q_size = 100cos_cache_size = 24tree_cache_size = 40tree_cache_use_limit = 40max_tdm_nodes = 0max_tdm_tgs = 0max_isr_sessions = 1000

isr_sessions_upper_threshold = 900isr_sessions_lower_threshold = 800isr_max_ru_size = 16384isr_rcv_pac_window = 8store_endpt_rscvs = NOstore_isr_rscvs = NOstore_dlur_rscvs = NOdlur_support = YESpu_conc_support = YESnn_rar = 128max_ls_exception_events = 0ms_support = NORMAL

queue_nmvts = YESptf_flags = NONE

Example of port defintion (X25)

[define_qllc_dlc]dlc_name = QLLC0description = ""neg_ls_supp = YESinitially_active = NOadapter_number = 0max_saps = 1support_level = 1984

[define_qllc_port]port_name = QLLCP0description = ""dlc_name = QLLC0port_number = 0address = ""initially_active = NOimplicit_hpr_support = NOmax_rcv_btu_size = 265tot_link_act_lim = 255inb_link_act_lim = 0out_link_act_lim = 0ls_role = LS_NEG


28/54


Inter.Pel .1 SOPRA.

implicit_dspu_services = NONEimplicit_dspu_template = ""implicit_ls_limit = 0

act_xid_exchange_limit = 9nonact_xid_exchange_limit = 5ls_xmit_rcv_cap = LS_TWSmax_ifrm_rcvd = 7target_pacing_count = 7max_send_btu_size = 265implicit_cp_cp_sess_support = YESimplicit_limited_resource = NOimplicit_deact_timer = 30effect_cap = 9600connect_cost = 0byte_cost = 0security = SEC_PUBLIC_SWITCHED_NETWORK

prop_delay = PROP_DELAY_PKT_SWITCHED_NETuser_def_parm_1 = 128user_def_parm_2 = 128user_def_parm_3 = 128loc_wsize = 0retry_limit = 2retry_timeout = 8idle_timeout = 48rx_thruput_class = DEFAULTtx_thruput_class = DEFAULT

Example of link station definition

[define_qllc_ls]ls_name = LYRS04description = ""port_name = QLLCP0adj_cp_name = SOPRA.RS04adj_cp_type = NETWORK_NODEdspu_services = NONEdspu_name = dlus_name = bkup_dlus_name = local_node_id = adj_node_id =

vc_type = SVCaddress = 9690002pvc_id = 1max_send_btu_size = 265ls_attributes = SNAcp_cp_sess_support = YESdefault_nn_server = YEShpr_supported = NOauto_act_supp = NOtg_number = 0limited_resource = NOsolicit_sscp_sessions = NOpu_name =

disable_remote_act = NO


29/54


Inter.Pel .1 SOPRA.

link_deact_timer = 30use_default_tg_chars = YESeffect_cap = 9600

connect_cost = 0byte_cost = 0security = SEC_PUBLIC_SWITCHED_NETWORKprop_delay = PROP_DELAY_PKT_SWITCHED_NETuser_def_parm_1 = 128user_def_parm_2 = 128user_def_parm_3 = 128target_pacing_count = 7ls_role = USE_PORT_DEFAULTSmax_ifrm_rcvd = 0dlus_retry_timeout = 0dlus_retry_limit = 0need_vrfy_fixup = NO

initially_active = NOreact_timer = 30react_timer_retry = 65535req_rev_charge = NOloc_wsize = 0rem_wsize = 0retry_limit = 2retry_timeout = 8loc_packet = DEFAULTrem_packet = DEFAULTidle_timeout = 48cud =

rx_thruput_class = DEFAULTtx_thruput_class = DEFAULTcugo = NOcug = NOcug_index = 0nuid =

7.6.2.2. Configuring APPC/CPIC resources

Inter.Pel uses the CPIC programming Interface to communicate over SNAnetworks. In CS5, this API is based on the APPC interface. Therefore , APPCresources must be defined for Inter.Pel to operate with SNA.

These resources are of the following type:

- local LU,- partner LU (on remote node),- mode,- remote node (if needed),- transaction programs,- CPIC Side Info.

At least one resource of each type must be defined (except possibly Remote Node)for Inter.Pel to operate in both initiator and responder roles.


30/54


Inter.Pel .1 SOPRA.

A CPIC Side Info is to be defined for Inter.Pel to initiate connections to a remotemachine.

For each configured Inter.Pel protocol, a transaction Program, dedicated to thatprotocol, must be defined for the SNA sub-system to start the appropriate Interpelprogram on incoming conversations.The following menu entries may be used from xsnaadminto configure theseitems:

Local LU

Services APPC New Independant Local LU

Remote Node

Services APPC New Remote Node

Partner LU

Services APPC New Partner LU Partner LU on Remote Node

Modes

Services APPC Modes

Transaction Programs

Services APPC Transaction Programs

CPIC Side Info

Services APPC CPIC

Local LU, Partner LUs and Modes definitions are stored in the file/etc/sna/sna_node.cfg.Transaction Programs definitions are stored in /etc/sna/sna_tps.CPIC Side Info profiles are stored in /etc/sna/sna_domn.cfg.

Local LU definition

Although Inter.Pel is able to use a single Local LU for all configured file transferprotocols and both outgoing and incoming conversations, such a configuration isnot recommended. You may, instead, configure either a different Local LU foreach file transfer protocol, or several different Local LUs for each protocol.For instance, sets of Local LUs for Inter.Pel may be defined as below:

either

LPEL: local LU for PEL protocol and both incoming and ougoing conversions.LPHE: same for PESIT E protocol


31/54


Inter.Pel .1 SOPRA.

or

LPELI: local LU for PEL protocol and incoming conversations.

LPELO:local LU for PEL protocol and outgoing conversations.LPHEI: local LU for PESIT E protocol and incoming conversations.LPHEO:local LU for PESIT E protocol and outgoing conversations.

Example of Local LU definition

(excerpt from /etc/sna/sna_node.cfg)

[define_local_lu]lu_alias = PELI

list_name = ""description = ""lu_name = PELIlu_session_limit = 0pu_name = nau_address = 0default_pool = NOsyncpt_support = NOlu_attributes = NONEsscp_id = 0disable = NOsys_name = ""timeout = 60

back_level = NO

Partner LU definition

A partner LU must be defined for each Inter.Pel remote site. A CPIC side infoprofile that points to that partner LU must also be created if Inter.Pel is expectedto be able to connect to that site. CPIC side info profile creation is discussed in thefollowing sections of this document. When creating a partner LU name, the fullyqualified partner LU name must be supplied.

Example of partner LU definition


[define_partner_lu]plu_alias = RS04description = ""fqplu_name = SOPRA.RS04plu_un_name = RS04parallel_sess_supp = YESappcip_routing_preference = NATIVEmax_mc_ll_send_size = 0conv_security_ver = NO


32/54


Inter.Pel .1 SOPRA.

Mode definition

All modes used for LU6.2 conversations must be defined on all nodes intended to

communicate over LU6.2 (local and remote nodes as seen from the localmachine). A simple LU6.2 configuration for Inter.Pel that uses the same mode forall LU6.2 conversations is possible, but not required. When a single set of mode

parameters is not suitable for all LU6.2 conversations, several modes can becreated.

Example of mode definition


[define_mode]mode_name = PELMODEdescription = ""

max_neg_sess_lim = 32767plu_mode_session_limit = 2min_conwin_src = 1min_conloser_src = 0auto_act = 0receive_pacing_win = 4max_receive_pacing_win = 0default_ru_size = YESmax_ru_size_upp = 1024max_ru_size_low = 0cos_name = #CONNECT

CPIC side info definition

A CPIC side info profile must be created for each Inter.Pel remote site to whichInter.Pel may initiate LU6.2 conversations. Apart from the CPIC side info profile,the corresponding Inter.Pel site object must also be created. These objects can becreated in any order, but the CPIC side info profile that addresses a given remotesite must exist when Inter.Pel attempts to connect to this site.

The CPIC side info profile gathers all information needed by a CPIC applicationto initiate a LU6.2 conversation. Inter.Pel uses the CPIC side info profile name asan objet that fully addresses and qualifies the remote application.

For this reason, the following information must be supplied in each CPIC side infoprofile dedicated to Inter.Pel use:

- local LU alias,- partner LU name,- mode name,- TP (transaction program) name.

Example of CPIC side info definition

(excerpt from /etc/sna/sna_domn.cfg)

[define_cpic_side_info]

sym_dest_name = PELCPICI


33/54


Inter.Pel .1 SOPRA.

description = ""lu_alias = PELIpartner_lu_name = PELR

mode_name = PELMODEtp_name_type = APPLICATION_TPtp_name = PELCPICRconversation_security_type = NONEsecurity_user_id = ""security_password = ""

TP (Transaction Program) definition

For each incoming conversation intended to Inter.Pel, the SNA sub-system isexpected to start the appropriate Inter.Pel application program. For that to beachieved, a Transaction Program profile must have been created for eachconfigured file transfer protocol. The actual PATH field of the transaction

program that is to be supplied depends on the file transfer protocol that isaddressed, as follows:

- Protocol File path relative to Inter.Pel home installation- PEL bin/PELCPICR- PESIT D bin/PHDCPICR- PESIT E bin/PHECPICR

Inter.Pel expects Transaction Program profiles to be defined as follows:

- the USERID and GROUP fields must match the actual user-id andgroup-id used to install and start Inter.Pel,

- the TYPE field must be set to NON-QUEUED,- the PATH field must be filled with the absolute path of the Inter.Pel

application program corresponding to the targetted file transfer protocol(see above),

- the ENVIRONMENT field must set APPCTPN to the correspondingTP name,if for example, the TP name is PHECPICR, this field must containAPPCTPN=PHECPICR.

Example of Transaction Program definition

(excerpt from /etc/sna/sna_tps)

[PELCPICR]LUALIAS = ""DESCRIPTION = ""USERID = portpelGROUP = interpelTIMEOUT = 0TYPE = NON-QUEUEDSTYLE = EXTENDEDPATH = /portage_interpel/users/portpel/T6342/bin/PELCPICRENV = APPCTPN=PELCPICR


34/54


Inter.Pel .1 SOPRA.

7.6.2.3. Summary of SNA installation for Inter.Pel

Configuring and checking the SNA system resources

The SNA configuration procedure using the xsnaadminGUI can be summarizedas follows:

1. Configure the SNA connectivity on the local machine :

- the NODE,- a PORT for each hardware interface used for SNAn- a link station per remote machine.

2. Check that all links can be successfully activated. If some dont, checkthe SNA log and trace files and fix the problem. The cause may be dueto a misconfiguration on a remote machine.

3. Configure the Local, Partner LUs and possibly remote NODEs that willbe used by Inter.Pel.

4. Try to manually establish LU-LU sessions (using the appropriatexsnaadmin command). Fix any problem on the local and remotemachines that may prevent LU-LU sessions from being established.

5. Create all other configuration objects needed by Inter.Pel (i.e. Modes,CPIC Side Information Profile, Transaction Programs).

Configuring and checking Inter.Pel resources for SNA

- each file transfer protocol intended to communicate over SNA/LU6.2must be have this feature enabled. This can be achieved the first timeInter.Pel is set up by selecting the corresponding option, or change laterusing the pelconfcommand,

- start Inter.Pel using the appropriate command (usually: pelstart),

- for each remote system expected to accept SNA conversations initiatedby the local Inter.Pel instance, a remote site that contains thecorresponding CPIC side info profile name as destination addressfieldmust be created. This can be achieved using the GUI interface, the pelop

screen interface or the peladmline command,- check each remote site configured for SNA/LU6.2 by submitting a file

transfer request addressed to that site. If a problem occurs that preventsthe actual file transfer from being processed normally, enabling the tracemodefor that site and setting up tracesand loggingfacility in the SNAsub-system will produce outputs thatgenerally help track the problem.


35/54


Inter.Pel .1 SOPRA.

7.6.3. LU62 Configuration with SNA server 6000

SNA SERVER 6000 (v2.1) SNA SERVICES 6000 software must be installedand configured before using LU6.2 services on AIX V3.2.5.

SNA resources are defined via the system utility SMIT.

The following IBM documents provide extended information for SNAconfiguration on AIX.

On SNA Server 6000:

- AIX SNA Server/6000: Configuration Reference- AIX SNA Server/6000: Transaction Program Reference

On SNA Services 6000:

- SC31-7002 : Using AIX SNA services- SC31-7014 : AIX SNA services/6000 references

Required information:

- control point profiles,- SNA Node profile,- link station profiles:

- X25 (Example):

- X25 link station profile,- X25 optional facilities profiles,- X25 SNA DLC profiles,

- LU6.2 profiles:

- local LU profiles,- partner LU profiles,- mode profiles (session characteristics),- TPN (Transation Program Name) profiles,- partner LU 6.2 location profiles.

- LU6.2 CPI side information profiles

7.6.3.1. CPI - C side information profile

In the list of resources listed above, only "CPI - C Side Information" is directlyused by the Inter.Pel monitor.

One entry in "CPI - C Symbolic Destination" must be defined for each remote siteusing LU6.2 connection. The name of this entry is referenced in the site definitionin the field "machine name". The LOCAL LU field in the Inter.Pel site definitionhas to match the LU local parameter of the SNA configuration.


36/54


Inter.Pel .1 SOPRA.

All the other resources must be configured according to the network environment.Here are two examples of definitions. The values given are imposed by the remotesite.

This next example is the content of the screen when the CPI-C Side Information isdefined with SMIT.

Profile name PXMVSALocal LU or Control Point Alias MYLOCLLUPartner LU alias PXMVSC2Fully Qualified partner LU nameMode Name PELICANRemote Transaction Program Name (RTPN) PELCPICRRTPN in hexadecimal No

This next example is an extract of the result, when we make an export of the SNAconfiguration in a text file with SMIT(Export Configuration Profiles).

side_info:

prof_name "PXMVSA"local_lu_or_control_pt_alias "MYLOCLLU"partner_lu_alias "PXMVSC2"fq_partner_lu_name ""mode_name "PELICAN"remote_tp_name_in_hex noremote_tp_name "PELCPICR"

comments ""

"Partner LU name" corresponds to the remote LU name (ACB parameter of theVTAM APPL macro). The "Partner TP name" defines the remote transaction toactivate. The "mode name" defines the session to use and it has to be defined inthe remote and the local systems.

7.6.3.2. CPI-C transaction

For transfers in transmitter mode, the definition must be the same in the remotesite.

For transfers in receiver mode, Inter.Pel/AIX provides the following transactions:

PELCPICR : For transfers in PEL protocolPHDCPICR : For transfers in PeSIT HS DPHECPICR : For transfers in PeSIT HS E

These script shells are found in /bin.

In order to enable the access of these transactions from the remote site, you mustdefine one local transaction profile for each of them.


37/54


Inter.Pel .1 SOPRA.

Here are two examples of definitions.

This next example is the content of the screen when the CPI Transaction is

defined with SMIT.

Profile name PELCPICRTransaction program name (TPN) PELCPICRTransaction program name (TPN) is in hexadecimal? noPIP data ? noConversation type eitherSync level none/confirmResource security level noneFull path to TP executable /home/PELIUNIX/bin/PELCPICRMultiple instances supported? yes

This next example is an extract of the result, when we make an export of the SNAconfiguration in a text file with SMIT (Export Configuration Profiles).

local_tp:

prof_name "PHDCPICR"tp_name "PHDCPICR"tp_name_in_hex nopip_data_present nopip_data_subfields_number 0conversation_type eithersync_level none/confirmresource_security_level none

resource_access_list_profile_name ""full_path_tp_exe "/home/PELIUNIX/bin/PHDCPICR"multiple_instances yesuser_id 211server_synonym_name ""restart_action oncecommunication_type signalsipc_queue_key 0standard_input_device "/tmp/PHDCPCIR"standard_output_device "/tmp/PHDCPICR"standard_error_device "/tmp/PHDCPICR"comments ""

Environment variables APPCTPN and APPCLLU are mandatory. They have tocorrespond to the TP name called and to the alias of the LU used for theconversation.

As indicated in the script shell, the standard output is redirected to a directory/run_time/tmp. Redirection can be suppressed if traces are not used.


38/54


Inter.Pel .1 SOPRA.

7.6.4. LU62 Configuration with SNA services

Here is the list of elements required:

- control point profiles,- physical link profiles,- logical link profiles,- physical units attachment profiles,- LU6.2 profiles,- LU6.2 connection profiles,- mode list and mode profiles,- local transaction list and transaction place profiles,- remote transaction list and remote transaction profiles,- LU6.2 CPI side information profiles.

7.6.4.1. CPI side information.

In the list of resources listed above ,only "CPI side information profiles" is directlyused by the Inter.Pel monitor.

There must be a "CPI side information" entry for each remote site that uses anLU6.2 attachment. The name of this entry must be referenced in the site definitionin the field "network address".

All the other resources have to be configured according to the networkenvironment.

Here is an example of a definition. The values given are imposed by the remotesite:

Current profile names : PXMVSAPartner READ name : PXMVSC2Remote transaction program : PELCPICRService transaction program : NOMode name : PELICAN

"Partner LU name" corresponds to a "logical connection profile" where parametersare defined for an attachment LU-LU. The "remote transaction program" definesthe distant transaction to activate. The "mode name" determines the session to use

which has to be defined in the distant and the local system.

7.6.4.2. CPI transaction

For transfers in transmitter mode, the definition must be the same on the remotesite.

For transfers in receiver mode, Inter.Pel/AIX6000 provides the followingtransactions:

PELCPICR: For the transfers in PEL protocolPHDCPICR: For the transfers in PeSIT HS DPHECPICR: For the transfers in PeSIT HS E


39/54


Inter.Pel .1 SOPRA.

These shell scripts are located in /bin.

In order to enable the access of these transactions from the remote site, you must

define one local transaction profile for each of them.

Here are two examples of definitions:

Current profiles name : PELCPICRTransaction program name : PELCPICRPIP dated : NOTypical transaction : basicRecovery level : no reconnectSyn level : confirmFull path to TPN executable :/home/PELIUNIX/bin/PELCPICRMultiple instance : YESTo use ID : 111Server synonym name :Restart action : onceCommunication type : signalsStandard INPUT file/device : /dev/nullStandard OUTPUT file/device : /dev/nullStandard ERROR file/device : /dev/nullSecurity required : noneCurrent profiles name : PHDCPICRTransaction program name : PHDCPICRPIP data : NOTransaction type : basicRecovery level : no reconnect

Syn level : confirmFull path to TPN executable : PELIUNIX/bin/PHDCPICRMultiple instances : YESUser ID : 111Server synonym name :Restart action : onceCommunication type : signalsStandard INPUT file/device : /dev/nullStandard OUTPUT file/device : /dev/nullStandard ERROR file/device : /dev/nullSecurity required : none

The "user ID" must be the user number of Inter.Pel.As indicated in the shell script, the standard output is redirected to a directory/run_time/tmp. Redirection can be suppressed if traces are not used.


40/54

8. Appendix for HPUX9000 Installation & Configuration Manual for UNIX Page 34__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

8. Appendix for HPUX9000


HPUX9000 V10.20 or above.

8.2. Available option

Interpel.Pel for HPUX provides the following optional facility:

COBOL Application Program Interface

This API allows user application programs to submit transfer requests and toaccess the Inter.Pel mailbox while Inter.Pel is running. User Cobol programs must

be linked with the Microfocus Cobol run-time libraries.USER EXITS written in Cobol language are not supported.



Inter.Pel uses the BSD socket library services when it is configured for TCP/IPnetworking. These services are available as a standard feature under the HPUXOperating System.For Inter.Pel to operate with TCP/IP, you must ensure that these services are

properly configured on your machines. Your must refer to HPUX manuals for the

configuration procedures of the system hardware and system software that addressTCP/IP services.



- the local port numbers that are to be used by Inter.Pel in order toreceive incoming connections. A different port number must beassigned to each configured File Transfer protocol. This informationmust be made available to Inter.Pel prior to its starting and must not be

changed while Inter.Pel is running. You also must ensure that these portnumbers are not currently in use and will not be attempted to be used byany other application on the system.It is advised to choose port numbers in the range 5000-65000,

- either a host name or a dotted IP address may be supplied to Inter.Pel asauthoritative host for incoming connections. You may use the hostname of the local machine, the looped address (localhost or 127.0.0.1), oran empty address for this purpose.


41/54


Inter.Pel .1 SOPRA.

Inter.Pel parameters that apply to outgoing connections are gathered in siteobjects. For each remote machine and each configured transfer protocol, a siteobject must be created and supplied with the TCP/IP address and port number

expected by the remote machine for that protocol. This information must beentered using an Inter.Pel administration tool while Inter.Pel is running. TheWindows GUI Interface, the pelopscreen interface, or the peladmline-modecommand can be used to create Inter.Pel sites.

The following is an example of site creation using peladmcreate_sitecommandfor a site in PELprotocol at dotted IP address 193.56.234.50and port number22001.


Either the host name(when using DNS facilities), or the IP dotted address(suchas 193.56.234.50, for example) can be specified as IP destination addressfieldfor sites intended to be connected to by Inter.Pel over TCP/IP.

8.4. X25 network interface for HPUX


Inter.Pel supports the X25/9000 product. So, your hardware must provideX25/9000 service interfaces.The system software that provides X25 services must have been installed andmust be operational prior to configuring Inter.Pel for X25.

8.4.2. X25 configuration

The following parameters are required for Inter.Pel to operate with X25/9000:

- a protocol-idmust be supplied for each protocol configured for X25incoming connections. A one to one relationship must be maintained

between protocols and protocol-id values. In other words, differentprotocols must be configured with different protocol-ids,

- when several X25 interfaces are installed on the machine, a device namecan be used to select an interface name. Otherwise, your systemautomatically chooses your default interface.

Inter.Pel parameters that apply to outgoing connections are gathered in siteobjects. For each remote machine and each configured transfer protocol, a siteobject must be created and supplied with the X25 address and the user dataexpected by the remote machine for that protocol. This information must beentered using an Inter.Pel administration tool while Inter.Pel is running. TheWindows GUI Interface, the pelopscreen interface ,or the peladmline-modecommand can be used to create Inter.Pel Sites.


42/54


Inter.Pel .1 SOPRA.

Example of Site creation using peladmcreate_sitecommand for a site in PELprotocol at X25 address 9920033linking on Band protocol-id c9.

peladm create_site ct X25-pr PEL-a SITE2 -pi SITE2 -da B.9920033ud c9

8.5. LU62 network interface


Inter.Pel can communicate over LU62 conversations using SNAPLUS2.The system software that provides LU62 services must have been installed andmust be operational prior to configuring Inter.Pel for SNA.

8.5.2. LU62 configuration

Inter.Pel requires HPUX Operating System 10.20 or later version for the supportof SNAPLUS2.

8.5.2.1. Configuring the SNA connectivity

This operation may highly vary depending on the actual topology of the SNAnetwork. You may use the X-motif GUI interface xsnapadminto configure theSNA connectivity on your system.

In brief, SNA connectivity configuration consists of defining the following SNAconfiguration items:

- the characteristics of the local node,

- a portfor each hardware interface,- a link station for each adjacent host.

You are expected to follow respectively the below menu items under xsnapadminto achieve this configuration:

local node

Services Configure Node Parameters

Port

Services Connectivity New Port

link station

Services Connectivity New Link Station

The above configuration parameters are stored in the /etc/opt/sna/sna_node.cfgfile.

To understand the parameters that address SNA connectivity, you must refer to therelated HPUX SNAPLUS2 documentation. Below are given some excerpts of asample sna_node.cfgfile that illustrate some of the parameters involved in theSNA connectivity configuration data.


43/54


Inter.Pel .1 SOPRA.

Example of local node configuration

[define_node]cp_alias = pxhpx3description = ""fqcp_name = SOPRA.PXHPX3node_type = LEN_NODEmode_to_cos_map_supp = NOmds_supported = YESnode_id = max_locates = 1500dir_cache_size = 255max_dir_entries = 0locate_timeout = 0reg_with_nn = YESreg_with_cds = YES

mds_send_alert_q_size = 100cos_cache_size = 24tree_cache_size = 40tree_cache_use_limit = 40max_tdm_nodes = 0max_tdm_tgs = 0max_isr_sessions = 1000isr_sessions_upper_threshold = 900isr_sessions_lower_threshold = 800isr_max_ru_size = 16384isr_rcv_pac_window = 8store_endpt_rscvs = NOstore_isr_rscvs = NOstore_dlur_rscvs = NOdlur_support = YESpu_conc_support = YESnn_rar = 128max_ls_exception_events = 0ms_support = NORMALqueue_nmvts = YESptf_flags = NONE

Example of port definition (X25)

[define_qllc_dlc]

dlc_name = QLLC0description = ""card_type = QLLC_NLIinitially_active = NO

[define_qllc_port]port_name = QLLCP0description = ""dlc_name = QLLC0port_number = 0address = ""initially_active = NOimplicit_hpr_support = NO

max_rcv_btu_size = 265


44/54


Inter.Pel .1 SOPRA.

tot_link_act_lim = 255inb_link_act_lim = 0out_link_act_lim = 0

ls_role = LS_NEGimplicit_dspu_services = NONEimplicit_dspu_template = ""implicit_ls_limit = 0act_xid_exchange_limit = 9nonact_xid_exchange_limit = 5ls_xmit_rcv_cap = LS_TWSmax_ifrm_rcvd = 7target_pacing_count = 7max_send_btu_size = 265implicit_cp_cp_sess_support = YESimplicit_limited_resource = NOimplicit_deact_timer = 30

effect_cap = 9600connect_cost = 0byte_cost = 0security = SEC_PUBLIC_SWITCHED_NETWORKprop_delay = PROP_DELAY_PKT_SWITCHED_NETuser_def_parm_1 = 128user_def_parm_2 = 128user_def_parm_3 = 128driver_name = cud_mode = IDENTITYcud_match = add_mode = DONTCARE

add_len = 0vc_type = SVCloc_packet = DEFAULTrem_packet = DEFAULTloc_wsize = 0rem_wsize = 0retry_limit = 2retry_timeout = 8idle_timeout = 48

Example of link station definition

[define_qllc_ls]

ls_name = QLLCL0description = ""port_name = QLLCP0adj_cp_name = BP063A.H000Aadj_cp_type = BACK_LEVEL_LEN_NODEdspu_services = NONEdspu_name = dlus_name = bkup_dlus_name = local_node_id = adj_node_id = vc_type = SVC

address = 17745971368pvc_id = 1


45/54


Inter.Pel .1 SOPRA.

max_send_btu_size = 265ls_attributes = SNAcp_cp_sess_support = YES

default_nn_server = YEShpr_supported = NOauto_act_supp = NOtg_number = 1limited_resource = NOsolicit_sscp_sessions = NOpu_name = QLLCL0disable_remote_act = NOlink_deact_timer = 30use_default_tg_chars = YESeffect_cap = 9600connect_cost = 0byte_cost = 0

security = SEC_PUBLIC_SWITCHED_NETWORKprop_delay = PROP_DELAY_PKT_SWITCHED_NETuser_def_parm_1 = 128user_def_parm_2 = 128user_def_parm_3 = 128target_pacing_count = 7ls_role = USE_PORT_DEFAULTSmax_ifrm_rcvd = 0dlus_retry_timeout = 0dlus_retry_limit = 0initially_active = NOreact_timer = 30

react_timer_retry = 65535req_rev_charge = NOloc_packet = DEFAULTrem_packet = DEFAULTloc_wsize = 0rem_wsize = 0fac = retry_limit = 5retry_timeout = 3idle_timeout = 30sn_id = 0cud =

8.5.2.2. Configuring APPC/CPIC resources

Inter.Pel uses the CPIC programming Interface to communicate over SNAnetworks. In SNAPLUS2, this API is based on the APPC interface. Therefore,APPC resources must be defined for Inter.Pel to operate with SNA.

These resources are of the following type:

- local LU,- partner LU (on remote node),- mode,


46/54


Inter.Pel .1 SOPRA.

- remote node (if needed),- transaction programs,- CPIC Side Info.

At least one resource of each type must be defined (except possibly Remote Node)for Inter.Pel to operate in both initiator and responder roles.

A CPIC Side Info is to be defined for Inter.Pel to initiate connections to a remotemachine.

For each configured Inter.Pel protocol, a transaction program, dedicated to thatprotocol, must be defined for the SNA sub-system to start the appropriate Inter.Pelprogram on incoming conversations.

The following menu entries may be used from xsnapadminto configure theseitems:

Local LU

Services APPC New Independent Local LU

Remote Node

Services APPC New Remote Node

Partner LU

Services APPC New Partner LUs Partner LU on Remote Node

Modes

Services APPC Modes

Transaction Programs

Services APPC Transaction Programs

CPIC Side Info

Services APPC CPIC

Local LU, Partner LU and Mode definitions are stored in the file/etc/opt/sna/sna_node.cfg. Transaction Program definitions are stored in/etc/opt/sna/sna_tps. CPIC Side Info profiles are stored in/etc/opt/sna/sna_domn.cfg.

Local LU definition

Although Inter.Pel is able to use a single Local LU for all configured file transferprotocols and both outgoing and incoming conversations, such a configuration isnot recommended. You may, instead, configure either a different Local LU foreach file transfer protocol, or several different Local LUs for each protocol.


47/54


Inter.Pel .1 SOPRA.

For instance, sets of Local LUs for Inter.Pel may be defined as below:

either

LPEL: local LU for PEL protocol and both incoming and ougoing conversions.LPHE: same for PESIT E protocol.

or

LPELI: local LU for PEL protocol and incoming conversations.LPELO:local LU for PEL protocol and outgoing conversations.LPHEI: local LU for PESIT E protocol and incoming conversations.LPHEO:local LU for PESIT E protocol and outgoing conversations.

Example of Local LU definition

(excerpt from /etc/opt/sna/sna_node.cfg)

[define_local_lu]lu_alias = PELIlist_name = ""description = ""lu_name = PELIlu_session_limit = 0pu_name = nau_address = 0default_pool = NO

syncpt_support = NOlu_attributes = NONEsscp_id = 0disable = NOsys_name = ""timeout = 60back_level = NO

Partner LU definition

A partner LU must be defined for each Inter.Pel remote site. A CPIC side infoprofile that points to that partner LU must also be created if Inter.Pel is expectedto be able to connect to that site. CPIC side info profile creation is discussed in thefollowing sections of this document. When creating a partner LU name, the fullyqualified partner LU name must be supplied.

Example of partner LU definition


[define_partner_lu]plu_alias = RS04description = ""fqplu_name = SOPRA.RS04plu_un_name = RS04

parallel_sess_supp = YES


48/54


Inter.Pel .1 SOPRA.

appcip_routing_preference = NATIVEmax_mc_ll_send_size = 0conv_security_ver = NO

Mode definition

All modes used for LU6.2 conversations must be defined on all nodes intended tocommunicate over LU6.2 (local and remote nodes as seen from the localmachine). A simple LU6.2 configuration for Inter.Pel that uses the same mode forall LU6.2 conversations is possible, but not required. When a single set of mode

parameters is not suitable for all LU6.2 conversations, several modes can becreated.

Example of mode definition


[define_mode]mode_name = PELMODEdescription = ""max_neg_sess_lim = 32767plu_mode_session_limit = 2min_conwin_src = 1min_conloser_src = 0auto_act = 0receive_pacing_win = 4max_receive_pacing_win = 0default_ru_size = YES

max_ru_size_upp = 1024max_ru_size_low = 0cos_name = #CONNECT

CPIC side info definition

A CPIC side info profile must be created for each Inter.Pel remote site to whichInter.Pel can initiate LU6.2 conversations. Apart from the CPIC side info profile,the corresponding Inter.Pel site object must also be created. These objects can becreated in any order, but the CPIC side info profile that addresses a given remotesite must exist when Inter.Pel attempts to connect to this site.

The CPIC side info profile gathers all information needed by a CPIC applicationto initiate a LU6.2 conversation. Inter.Pel uses the CPIC side info profile name asan object that fully addresses and qualifies the remote application.

For this reason, the following information must be supplied in each CPIC side infoprofile dedicated to Inter.Pel use:

- local LU alias,- partner LU name,- mode name,- TP (transaction program) name.


49/54


Inter.Pel .1 SOPRA.

Example of CPIC side info definition

(excerpt from /etc/opt/sna/sna_domn.cfg)

[define_cpic_side_info]sym_dest_name = PELCPICIdescription = ""lu_alias = PELIpartner_lu_name = PELRmode_name = PELMODEtp_name_type = APPLICATION_TPtp_name = PELCPICRconversation_security_type = NONEsecurity_user_id = ""security_password = ""

TP (Transaction Program) definition

For each incoming conversation intended for Inter.Pel, the SNA subsystem isexpected to start an appropriate Inter.Pel application program. For that to beachieved, a Transaction Program profile must have been created for eachconfigured file transfer protocol.

The actual PATH field of the transaction program that is to be supplied dependson the file transfer protocol that is addressed as follows:

Protocol File path relative to Inter.Pel home installationPEL bin/PELCPICR

PESIT D bin/PHDCPICRPESIT E bin/PHECPICR

Inter.Pel expects Transaction Program profiles to be defined as follows:

- the USERID and GROUP fields must match the actual user-id andgroup-id used to install and start Inter.Pel,

- the TYPE field must be set to NON-QUEUED,- the PATH field must be filled with the absolute path of the Inter.Pel

application program corresponding to the targeted file transfer protocol(see above),

- the ENVIRONMENT field must set APPCTPN to the correspondingTP name.If for example, the TP name is PHECPICR, this field must containAPPCTPN=PHECPICR.

Example of Transaction Program definition:

(excerpt from /etc/opt/sna/sna_tps)

[PELCPICR]LUALIAS = ""DESCRIPTION = ""USERID = portpelGROUP = interpel

TIMEOUT = 0


50/54


Inter.Pel .1 SOPRA.

TYPE = NON-QUEUEDPATH = /portage_interpel/users/portpel/T6342/bin/PELCPICR

ENV = APPCTPN=PELCPICR

8.5.2.3. Summary of SNA installation for Inter.Pel

Configuring and checking the SNA system resources

The SNA configuration procedure using the xsnapadminGUI can be summarizedas follows:

1. Configure the SNA connectivity on the local machine:

- the NODE,- a PORT for each hardware interface used for SNA,- a link station per remote machine.

2. Check that all links can be successfully activated. If some cant, checkthe SNA log and trace files and fix the problem. The cause may be dueto a misconfiguration on a remote machine.

3. Configure the Local, Partner LUs and possibly remote NODEs that willbe used by Inter.Pel.

4. Try to establish manually LU-LU sessions (using the appropriatexsnapadmincommand). Fix any problem on the local and remotemachines that may prevent LU-LU sessions from being established.

5. Create all other configuration objects needed by Inter.Pel (i.e. Modes,CPIC Side Information Profile, and Transaction Programs).

Configuring and checking Inter.Pel resources for SNA

- each file transfer protocol intended to communicate over SNA/LU6.2must have this feature enabled. This can be achieved the first timeInter.Pel is set up by selecting the corresponding option, or changed laterusing the pelconfcommand,

- start Inter.Pel using the appropriate command (usually: pelstart),

- for each remote system expected to accept SNA conversations initiatedby the local Inter.Pel instance, a remote site that contains thecorresponding CPIC side info profile name such as destination addressfield must be created. This can be achieved using the GUI interface, thepelopscreen interface, or the peladmline command,

- check each remote site configured for SNA/LU6.2 by submitting a filetransfer request addressed to that site. If a problem occurs that preventsthe actual file transfer from being processed normally, enabling thetrace modefor that site and setting up tracesand loggingfacility in theSNA sub-system will produce outputs that may help track the

problem.


51/54

9. Appendix for SOLARIS Installation & Configuration Manual for UNIX Page 45__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

9. Appendix for SOLARIS


SUN/SPARC SOLARIS 2.6 and above.

9.2. Available options

Interpel.Pel for Solaris supports the SNAPIX SNA/LU6.2 Services through theCPIC programming interface.



Inter.Pel 6.6 for Solaris 2.6 has been built using SUNWx25 version 9.1 andSNAP-IX version 6.06.



The local port numbers that are used by Inter.Pel in order to receive incomingconnections. A different port number must be assigned to each configured FileTransfer protocol. This information must be configured prior to Inter.Pel start-up

and must not be changed while the product is running. You also must ensure thatthese port numbers are not currently in use and will not be attempted to be used byany other application on the system. It is advised to choose port numbers in therange 5000-65000.

Either a host name or dotted IP address may be supplied to Inter.Pel ashost name for the binding to listen ports. You may use, either the hostname of the local machine, the looped address (localhost or 127.0.0.1) or an

empty address for this purpose.

Inter.Pel parameters that apply to outgoing connections are gathered in siteobjects. For each remote machine and each configured transfer protocol, a site

object must be created and supplied with the TCP/IP address and port numberexpected by the remote machine for that protocol. This information must beentered using an Inter.Pel administration tool while Inter.Pel is running. TheWindows GUI Interface, the pelopscreen interface, or the peladmline-modecommand can be used to create Inter.Pel sites.

Example of site creation using peladmcreate_sitecommand for a site in PELprotocol at dotted IP address 193.56.234.50and port number 22001.


Either the host name(when using DNS facilities), or the IP dotted address(suchas 193.56.234.50, for example) can be specified as IP destination addressfield

for sites intended to be connected to by Inter.Pel over TCP/IP.


52/54

9. Appendix for SOLARIS Installation & Configuration Manual for UNIX Page 46__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

9.4. X25 network interface

Inter.Pel supports the SOCKET X25 access methods under the SOLARIS O/S.

9.4.1. Configuring Inter.Pel for X25 SOCKET interface.

Call user data must be supplied for each protocol configured for X25 incomingconnections. A one to one relationship must be maintained between protocols andcall user data values. In other words, different protocols must be configured withdifferent call user data.

When more than one X25 interface is installed on the system, it is possible torestrict Inter.Pel connections to a specific X25 interface. This is achieved by

providing the link id. (number 09) of this interface as device name whenconfiguring the server side of protocols.

9.5. LU6.2 network interface

Inter.Pel supports the SNAP-IX product from Data-Connection under theSOLARIS operating system. This product originates from the SNAPS (SNA

portable software) from the same supplier as Communication Server on IBM AIXand SNAPLUS 2 on HP/UX. As a result, the sections of this documentation thatdescribe LU6.2 installation on either AIX or HPUX must be referred to for theconfiguration of LU6.2 services for Inter.Pel under SOLARIS.


53/54

10. Appendix for LINUX Installation & Configuration Manual for UNIX Page 47__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

10. Appendix for LINUX


RedHat 6.1/i386 and Operating Systems compatible with RedHat 6.1/i386.

10.2. Available options

Only TCP/IP communication services are supported.



There is no special additional pre-requisite for Inter.Pel for Linux, provided thatthe Operating System is compatible with RedHat/Linux 6.1/i386.


A different port number must be assigned to each configured File Transferprotocol. This information must be configured prior to Inter.Pel start-up and mustnot be changed while the product is running. You also must ensure that these portnumbers are not cur

installation and configuration manual for unix

Documents