Installation and Configuration Manual For UNIX

0102-66-02-OUNX6600
____________________
Inter.Pel 6.6
____________________
Installation & Configuration Manual for UNIX
____________________

Inter.Pel 6.6 SOPRA.
The information contained in this document is subject to revision without prior notice and shall
not be regarded as binding on SOPRA. The rights relative to the use of the software described
in 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 any
form 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 written
authorization of SOPRA is strictly prohibited.

Copyright 2003 SOPRA.
All rights reserved. All trademarks registered.
November 2003.
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 5
4.3.1. Directory layout 5
4.3.2. Directory contents 6
5. INTER.PEL CONFIGURATION 8
5.1. Configuration procedure 8
5.1.1 Using pelsetup menu interface 8
5.1.2 Using pelconf line command 8
5.1.3 Stage of Inter.Pel configuration 8
5.2. Configuration files 9
5.3. Network configuration in Inter.Pel 9
5.3.1. TCP/IP 9
5.3.2. X25 10
5.3.3. SNA LU6.2 10
5.4. Address configuration for Inter.Pel partners 10
5.4.1. TCP/IP 10
5.4.2. X25 11
5.4.3. SNA LU6.2 11
6. START/STOP PROCEDURE 12
Contents Installation & Configuration Manual for UNIX Page iv
__________________________________________________________________________________________________
6.1. Checking Before starting 12
6.1.1. For TCP/IP subsystem 12
6.1.2. For X25 subsystem 12
6.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 13
6.6.1. Checking after starting Inter.Pel monitor 14
6.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 17
7.3.1. Hardware and software prerequisites 17
7.3.2. TCP/IP configuration 17
7.4. X25 network interface for Bull/AIX 18
7.4.1. Configuring Inter.Pel for XTI/XX25 18
7.4.2. Configuring Inter.Pel for MAD/MAX3 X25 18
7.5. X25 network interface for IBM/AIX 19
7.5.1. Configuring Inter.Pel for NPI/X25 19
7.5.2. Configuring Inter.Pel for COMIO/X25 19
7.6. LU62 network interface 20
7.6.1. Hardware and software Prerequisites 20
7.6.2 Configuring Inter.Pel for CS5 20
7.6.2.1 Configuring the SNA connectivity 20
7.6.2.2. Configuring APPC/CPIC resources 23
7.6.2.3. Summary of SNA installation for Inter.Pel 28
7.6.3. LU62 Configuration with SNA server 6000 29
7.6.3.1. CPI - C side information profile 29
7.6.3.2. CPI-C transaction 30
7.6.4. LU62 Configuration with SNA services 32
7.6.4.1. CPI side information. 32
7.6.4.2. CPI transaction 32
8. APPENDIX FOR HPUX9000 34
Contents Installation & Configuration Manual for UNIX Page v
__________________________________________________________________________________________________
8.2. Available option 34
8.4. X25 network interface for HPUX 35
8.4.2. X25 configuration 35
8.5. LU62 network interface 36
8.5.2. LU62 configuration 36
8.5.2.1. Configuring the SNA connectivity 36
8.5.2.2. Configuring APPC/CPIC resources 39
8.5.2.3. Summary of SNA installation for Inter.Pel 44
9. APPENDIX FOR SOLARIS 45
9.2. Available options 45
9.4. X25 network interface 46
9.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

Contents Installation & Configuration Manual for UNIX Page vi
__________________________________________________________________________________________________
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 UNIX
platforms.
1.2. Reading guidelines

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

Before using this manual, you must have a basic understanding of Inter.Pel .5.1
product presented in Product Overview publication.

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.

3. Pre-Requisites Installation & Configuration Manual for UNIX Page 3
__________________________________________________________________________________________________
Inter.Pel .6 SOPRA.
3. Pre-Requisites
3.1. Disk space

The disk space needed for the installation is approximately 80 MB.
Additional disk space is needed to operate the product.
3.2. Software protection key

A software protection key is checked by Inter.Pel on its starting. If Inter.Pel
encounters a wrong key value, the monitor will not start.

Contact SOPRA delivery department to receive your private protection key. This
information is requested during installation.
3.3. Other information

Following parameters are requested during installation, depending on the type of
network used and the platform running the monitor.

For TCP/IP network:

- IP address (or hostname) of UNIX platform,
- port numbers to be used by Inter.Pel for incoming connection requests,
each F.T. protocol uses its own listening port.

For X25 network:

- local address,
- user data or sub-address or both to be used by Inter.Pel to route
incoming connection requests. Each F.T. protocol is attached to its own
data,
- Board/Line/Link/Application identifier,
- Facilities.

For SNA/LU6.2 network:

- local LU name,
- CPI-C Symbolic Destination name.
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 system
type for mounting the CD-ROM. As a precaution, enter the following command
for more information:

$ man mount

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

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 product
files.

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.

__________________________________________________________________________________________________
Inter.Pel .6 SOPRA.
To install your monitor, you must choose a home directory for Inter.Pel and run
the 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 current
directory, creating sub-directories as needed, according to the directory layout
described hereafter .

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

You can run Inter.Pel either under a normal user account or under the root
account. 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.Pel
account is granted with suitable rights for accessing the files to transmit. If it is
not, Inter.Pel processes will not be permitted to open the corresponding files and
the 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:

<home_directory>
bin
inc
nlt
french
pelop
setup
english
pelop
setup
obj
run_time
arc
data
etc
scripts
template
resolved
tmp
src
cobol
exitclnt
exituser
isfuser
itpuex
samples
__________________________________________________________________________________________________
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 to
compilation 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 character
mode.

./nlt/french/setup

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

./nlt/english

English messages and screen forms.

./nlt/english/pelop

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

./nlt/english/setup

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

__________________________________________________________________________________________________
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.

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 interactive
operator interface of Inter.Pel version 6.6 that configures Inter.Pel Monitor. This
operators interface appears in the form of screens containing options or named
files.

The pelsetup command operates in English by default. To start the interface in
French, 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 pelsetup program configures both the monitor and the server part for
Client Graphical User Interface or Client Internet User Interface (if selected).
5.1.2 Using pelconf line command

The pelconf on-line command must not be used to configure the product under
UNIX. You muse use either pelsetup or pelsetup_fr commands instead.

5.1.3 Stage of Inter.Pel configuration

Inter.Pel configuration consists of the following steps:

1. Run pelsetup program and configure all Inter.Pel services you need for
your application.

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

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

4. Start Inter.Pel using the pelstart command.

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

__________________________________________________________________________________________________
Inter.Pel .6 SOPRA.
5.2. Configuration files

The pelsetup program creates configuration files under
<Inter.Pel_home>/run_time/etc directory, which are text files containing
parameters used by Inter.Pel at start-up.

The following configuration files are created for all UNIX platforms:

conffile : Global resources configuration parameters
profile : Environment variables

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

If the network security feature of Inter.Pel has been selected, the following
additional configuration files are created in <Inter.Pel.home>/run_time/data
directory:

tableip.adr : Security file for TCP/IP
tablex25.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 UNIX
platform. For example, an X25 configuration file is created during Inter.Pel
configuration 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 PeSIT
family of protocols. For Inter.Pel to use TCP/IP transport for a protocol, you must
indicate the hostname (or IP address) and the port number that is to be used to
route incoming calls to that protocol.

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

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

See the Appendix on your platform for more details.

__________________________________________________________________________________________________
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 have
knowledge of parameters to use for selecting incoming connections from the
Network. The information that is most commonly used to route X25 incoming
calls 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 connections
by address fields. See the appendix corresponding to your platform for detailed
information on these features.

Depending on the X25 interface type, Inter.Pel may require that it be provided
with 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 UNIX
platforms. See the appendix corresponding to your platform for detailed
information on supported features.

Each LU6.2 session is handled by a separate Inter.Pel process. Processes that deal
with 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 is
responsible for starting an Inter.Pel LU6.2 server process on each incoming
connection.

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 machine
name (if using a name server) or its dotted IP address (such as 193.56.234.50), and
the 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" (-pi
RPT0). To reach this site, Inter.Pel will use TCP/IP network (-ct TCP) and will
call the IP address 193.56.234.50 and the port number 22200. Note that the partner
application must be running in a platform with this IP address, and listening to this
port number.
__________________________________________________________________________________________________
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" (-pi
RPX0). To reach this site, Inter.Pel will use X25 network (-ct X25) to call request
with "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 Network
type 'lu62'. The field Machine name is used to define the 'CPI-C Side
Information (also termedCPIC symbolic destination). The field Local LU
contains 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 the
address TOMVS@IPASOPL1@0.
The corresponding and related SNA configuration parameters must have been
defined 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 profiles
that gather values for all SNA parameters needed to perform connections to the
remote Site.

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 network
resources 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 UNIX
ping command with the hostname or IP address as an argument. See the ping
documentation 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 of
connections and the monitoring and tracing of X25 activity. You must refer to the
documentation of your X25 sub-system and perform the recommended checks and
tests.
6.1.3. For SNA LU6.2 subsystem

Check the SNA configuration, by activating each LU6.2 connection used by
Inter.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 file
transfer time, check if the remote site is active and the mode and the transaction
name requested in 'CPI symbolic destination' are defined in the remote site.

If the problem remains, activate the audit function and the SNA trace and check
the traced elements.
6.2. Initialize Inter.Pel monitor

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

pelinit

6.3. Start/Stop Inter.Pel monitor

Inter.Pel delivery supplies two utility programs named pelstart and pelstop which
are used to start or to stop the monitor.

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

$ . <Inter.Pel_directory>/run_time/etc/profile

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
To start or stop the monitor, enter the following command:

$ pelstart (starts Inter.Pel)

$ pelstop (stops Inter.Pel)

6.4. Start/Stop graphical user interface server

Inter.Pel installation program creates a Shell script named itpdmn that is used to
start or stop the server for client graphical user interfaces. Note that this program
also configure the GUI server.

Prior to any use of GUI server and related files (including itpdmn), you must set
the corresponding environment for your UNIX session, by executing the Shell
script named csprofile (it is created under <Inter.Pel_directory>/run_time/etc
directory by the configuration utility):

$ . <Inter.Pel_directory>/run_time/etc/csprofile

To start or stop the server, run itpdmn ipelapi with start or stop:

$ itpdmn ipelapi start (starts the server)

$ itpdmn ipelapi stop (stop the server)

6.5. Start/Stop internet user interface server

Inter.Pel installation program creates a Shell script named itpdmn that is used to
start or stop the server for client internet user interfaces. Note that this program
also configures the IUI server.

Prior to any use of IUI server and related files (including itpdmn), you must set
the corresponding environment for your UNIX session, by executing the Shell
script named csprofile (it is created under <Inter.Pel_directory>/run_time/etc
directory by the configuration utility):

$ . <Inter.Pel_directory>/run_time/etc/csprofile

To start or stop the server, run itpdmn xfbapi with start or stop:

$ itpdmn xfbapi start (starts the server)

$ itpdmn xfbapi stop (stops the server)
6.6. Checking Inter.Pel processes

When you enter the command pelstart or pelstop, you can check that your
Inter.Pel processes are correctly started or stopped by the following command:

$ ps e | grep p_
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
6.6.1. Checking after starting Inter.Pel monitor

When Inter.Pel is started, the ps command must display at least the Inter.Pel
supervisor process (p_sup) and the Inter.Pel system process (p_sys).

Other processes are launched according to network resources and configured
protocols.

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.xxx process is launched for each protocol configured for X25. Then, if
several protocols are used with the X25 Network, you must count as many
px25.xxx processes as protocols that are used.

A protocol process is also launched if this protocol is not used with a TCP/IP
Network. 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 in
order to increase the performance of the transfer.

Note:
when both PeSIT version E and PeSIT version D are configured, two processes
executing either p_fsitsock or p_fsit image must exist (one for each protocol
version).

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

Example:
On an AIX machine, using PeSIT protocol for TCP/IP and XTI Network
interfaces and ODETTE protocol for XTI Network interface, the list of the
processes displayed by the command ps is the following:

p_fsitsock
p_x25.xti
p_x25.xti
p_fodt

__________________________________________________________________________________________________

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 if
one connection takes place. Therefore, they are called dynamic processes.

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

Message queues:

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

$ ipcs q | grep <OWNER>
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 to
its standard output or error stream. These streams are redirected to files located in
the $p_home_dir/run_time/tmp/ directory and each process writes to a different
file, 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)
__________________________________________________________________________________________________

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 message
related 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 preventing
Inter.Pel processes from operating properly.

Remark:

XX: PID of the process.
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 Interface
This API allows user application programs to submit transfer requests and to
access 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/IP
networking. These services are available as a standard feature under the AIX
Operating 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 address
TCP/IP services.
7.3.2. TCP/IP configuration

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

- the local port numbers that are used by Inter.Pel in order to receive
incoming connections. A different port number must be assigned to each
configured 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 currently
in use and will not be attempted to be used by any other application on
the 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 as
authoritative host for incoming connections. You may use, the host
name of the local machine, the looped address (localhost or 127.0.0.1), or
an empty address for this purpose.

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
Inter.Pel parameters that apply to outgoing connections are gathered in Site
objects. For each remote machine and each configured transfer protocol, a Site
object must be created and supplied with the TCP/IP address and port number
expected by the remote machine for that protocol. This information must be
entered using an Inter.Pel administration tool while Inter.Pel is running. The
Windows GUI Interface, the pelop screen interface, or the peladm line-mode
command can be used to create Inter.Pel Sites.

The following is an example of Site creation using the peladm create_site
command for a site in PEL protocol at dotted IP address 193.56.234.50 and port
number 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 (such
as 193.56.234.50, for example) can be specified as IP destination address field
for 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 methods
under 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 and
must 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 should
exist if the XTI/XX25 software has been properly installed and
configured.

- A call user data must be supplied for each protocol configured for X25
incoming connections. A one to one relationship must be maintained
between protocols and call user data values. In other words, different
protocols 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/MAX3
X25:

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

- the local address of the X25 physical interface. This address must
match the local address values that have been configured in the system
for that interface,
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
- for each protocol Inter.Pel may have to receive incoming connections
from, a call user data hexadecimal string must be supplied. A one to one
relationship must be maintained between protocols and call user data
values. In other words, different protocols must be configured with
different call user data.
7.5. X25 network interface for IBM/AIX

Inter.Pel supports both the COMIO/X25 and the NPI/X25 access methods. The
latter access method (e.g. NPI/X25) is recommended when fast X25 links are
used.
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 device
interface. This token is of the following pattern, where # is a digit that
designates the X25 line number: sx25# x25pkt .

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

from, a call user data hexadecimal string must be supplied. A one to one
relationship must be maintained between protocols and call user data
values. In other words, different protocols must be configured with
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 the
following pattern, where character # designates the X25 line number:
x25s #.
by default Inter.Pel uses x25s0 that corresponds to X25 line number
zero.

from, a xroute entry must be supplied at Inter.Pel installation. When
configuring those xroute entries, the user must make sure that
parameters do not conflict in a way that may affect proper routing of
incoming connections to Inter.Pel File Transfer protocols. You must refer to
AIX manuals for the description of the xroute command.

__________________________________________________________________________________________________

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 SERVER
version 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 of
COMMUNICATION SERVER 5.
7.6.2.1 Configuring the SNA connectivity

This operation may highly vary depending on the actual topology of the SNA
network. You may use the X-motif GUI interface xsnaadmin to configure the
SNA connectivity on your system.

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

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

Follow respectively the below menu items under xsnaadmin to achieve this
configuration:

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.cfg file.
To understand the parameters that address SNA connectivity, you must refer to the
related AIX Communication Server 5 documentation. Below are given some
excerpts of a sample sna_domn.cfg file that illustrates some of the parameters
involved in the SNA connectivity configuration data..

Example of local node configuration
[define_node]
cp_alias = PXRS10
description = ""
fqcp_name = SOPRA.PXRS10
node_type = NETWORK_NODE
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
mode_to_cos_map_supp = NO
mds_supported = YES
node_id = <0710000f>
max_locates = 1500
dir_cache_size = 255
max_dir_entries = 0
locate_timeout = 0
reg_with_nn = YES
reg_with_cds = YES
mds_send_alert_q_size = 100
cos_cache_size = 24
tree_cache_size = 40
tree_cache_use_limit = 40
max_tdm_nodes = 0
max_tdm_tgs = 0
max_isr_sessions = 1000
isr_sessions_upper_threshold = 900
isr_sessions_lower_threshold = 800
isr_max_ru_size = 16384
isr_rcv_pac_window = 8
store_endpt_rscvs = NO
store_isr_rscvs = NO
store_dlur_rscvs = NO
dlur_support = YES
pu_conc_support = YES
nn_rar = 128
max_ls_exception_events = 0
ms_support = NORMAL
queue_nmvts = YES
ptf_flags = NONE

Example of port defintion (X25)
[define_qllc_dlc]
dlc_name = QLLC0
description = ""
neg_ls_supp = YES
initially_active = NO
adapter_number = 0
max_saps = 1
support_level = 1984
[define_qllc_port]
port_name = QLLCP0
description = ""
dlc_name = QLLC0
port_number = 0
address = ""
implicit_hpr_support = NO
max_rcv_btu_size = 265
tot_link_act_lim = 255
inb_link_act_lim = 0
out_link_act_lim = 0
ls_role = LS_NEG
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
implicit_dspu_services = NONE
implicit_dspu_template = ""
implicit_ls_limit = 0
act_xid_exchange_limit = 9
nonact_xid_exchange_limit = 5
ls_xmit_rcv_cap = LS_TWS
max_ifrm_rcvd = 7
target_pacing_count = 7
max_send_btu_size = 265
implicit_cp_cp_sess_support = YES
implicit_limited_resource = NO
implicit_deact_timer = 30
effect_cap = 9600
connect_cost = 0
byte_cost = 0
security = SEC_PUBLIC_SWITCHED_NETWORK
prop_delay = PROP_DELAY_PKT_SWITCHED_NET
user_def_parm_1 = 128
loc_wsize = 0
retry_limit = 2
retry_timeout = 8
idle_timeout = 48
rx_thruput_class = DEFAULT
tx_thruput_class = DEFAULT
Example of link station definition
[define_qllc_ls]
ls_name = LYRS04
description = ""
port_name = QLLCP0
adj_cp_name = SOPRA.RS04
adj_cp_type = NETWORK_NODE
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
local_node_id = <00000000>
adj_node_id = <00000000>
vc_type = SVC
address = 9690002
pvc_id = 1
ls_attributes = SNA
cp_cp_sess_support = YES
default_nn_server = YES
hpr_supported = NO
auto_act_supp = NO
tg_number = 0
limited_resource = NO
solicit_sscp_sessions = NO
pu_name = <0000000000000000>
disable_remote_act = NO
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
link_deact_timer = 30
use_default_tg_chars = YES
effect_cap = 9600
connect_cost = 0
byte_cost = 0
ls_role = USE_PORT_DEFAULTS
max_ifrm_rcvd = 0
dlus_retry_timeout = 0
dlus_retry_limit = 0
need_vrfy_fixup = NO
react_timer = 30
react_timer_retry = 65535
req_rev_charge = NO
loc_wsize = 0
rem_wsize = 0
retry_limit = 2
retry_timeout = 8
loc_packet = DEFAULT
rem_packet = DEFAULT
idle_timeout = 48
cud = <c3>
rx_thruput_class = DEFAULT
tx_thruput_class = DEFAULT
cugo = NO
cug = NO
cug_index = 0
nuid = <>
7.6.2.2. Configuring APPC/CPIC resources

Inter.Pel uses the CPIC programming Interface to communicate over SNA
networks. In CS5, 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,
- 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.

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
A CPIC Side Info is to be defined for Inter.Pel to initiate connections to a remote
machine.

For each configured Inter.Pel protocol, a transaction Program, dedicated to that
protocol, must be defined for the SNA sub-system to start the appropriate Interpel
program on incoming conversations.
The following menu entries may be used from xsnaadmin to configure these
items:

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 transfer
protocols and both outgoing and incoming conversations, such a configuration is
not recommended. You may, instead, configure either a different Local LU for
each 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

__________________________________________________________________________________________________

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 = PELI
lu_session_limit = 0
pu_name = <0000000000000000>
nau_address = 0
default_pool = NO
syncpt_support = NO
lu_attributes = NONE
sscp_id = 0
disable = NO
sys_name = ""
timeout = 60
back_level = NO
Partner LU definition

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

Example of partner LU definition


[define_partner_lu]
plu_alias = RS04
description = ""
fqplu_name = SOPRA.RS04
plu_un_name = RS04
parallel_sess_supp = YES
appcip_routing_preference = NATIVE
max_mc_ll_send_size = 0
conv_security_ver = NO
__________________________________________________________________________________________________

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 local
machine). A simple LU6.2 configuration for Inter.Pel that uses the same mode for
all 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 be
created.

Example of mode definition


[define_mode]
mode_name = PELMODE
description = ""
max_neg_sess_lim = 32767
plu_mode_session_limit = 2
min_conwin_src = 1
min_conloser_src = 0
auto_act = 0
receive_pacing_win = 4
max_receive_pacing_win = 0
default_ru_size = YES
max_ru_size_upp = 1024
max_ru_size_low = 0
cos_name = #CONNECT
CPIC side info definition

A CPIC side info profile must be created for each Inter.Pel remote site to which
Inter.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 be
created in any order, but the CPIC side info profile that addresses a given remote
site must exist when Inter.Pel attempts to connect to this site.

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

For this reason, the following information must be supplied in each CPIC side info
profile 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
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
description = ""
lu_alias = PELI
partner_lu_name = PELR
mode_name = PELMODE
tp_name_type = APPLICATION_TP
tp_name = PELCPICR
conversation_security_type = NONE
security_user_id = ""
security_password = ""
TP (Transaction Program) definition

For each incoming conversation intended to Inter.Pel, the SNA sub-system is
expected to start the appropriate Inter.Pel application program. For that to be
achieved, a Transaction Program profile must have been created for each
configured file transfer protocol. The actual PATH field of the transaction
program that is to be supplied depends on the file transfer protocol that is
addressed, 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 and
group-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 corresponding
TP name,
if for example, the TP name is PHECPICR, this field must contain
APPCTPN=PHECPICR.

Example of Transaction Program definition

(excerpt from /etc/sna/sna_tps)

[PELCPICR]
LUALIAS = ""
DESCRIPTION = ""
USERID = portpel
GROUP = interpel
TIMEOUT = 0
TYPE = NON-QUEUED
STYLE = EXTENDED
PATH = /portage_interpel/users/portpel/T6342/bin/PELCPICR
ENV = APPCTPN=PELCPICR
__________________________________________________________________________________________________

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 xsnaadmin GUI can be summarized
as 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, check
the SNA log and trace files and fix the problem. The cause may be due
to a misconfiguration on a remote machine.

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

4. Try to manually establish LU-LU sessions (using the appropriate
xsnaadmin command). Fix any problem on the local and remote
machines 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.2
must be have this feature enabled. This can be achieved the first time
Inter.Pel is set up by selecting the corresponding option, or change later
using the pelconf command,

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

- for each remote system expected to accept SNA conversations initiated
by the local Inter.Pel instance, a remote site that contains the
corresponding CPIC side info profile name as destination address field
must be created. This can be achieved using the GUI interface, the pelop
screen interface or the peladm line 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 prevents
the actual file transfer from being processed normally, enabling the trace
mode for that site and setting up traces and logging facility in the SNA
sub-system will produce outputs that generally help track the problem.

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
7.6.3. LU62 Configuration with SNA server 6000

SNA SERVER 6000 (v2.1) SNA SERVICES 6000 software must be installed
and 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 SNA
configuration 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 directly
used by the Inter.Pel monitor.

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

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 remote
site.

This next example is the content of the screen when the CPI-C Side Information is
defined with SMIT.
Profile name PXMVSA
Local LU or Control Point Alias MYLOCLLU
Partner LU alias PXMVSC2
Fully Qualified partner LU name
Mode Name PELICAN
Remote Transaction Program Name (RTPN) PELCPICR
RTPN in hexadecimal No
This next example is an extract of the result, when we make an export of the SNA
configuration 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 no
remote_tp_name "PELCPICR"
comments ""
"Partner LU name" corresponds to the remote LU name (ACB parameter of the
VTAM APPL macro). The "Partner TP name" defines the remote transaction to
activate. The "mode name" defines the session to use and it has to be defined in
the 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 remote
site.

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

PELCPICR : For transfers in PEL protocol
PHDCPICR : For transfers in PeSIT HS D
PHECPICR : For transfers in PeSIT HS E

These script shells are found in <product>/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.

__________________________________________________________________________________________________

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 PELCPICR
Transaction program name (TPN) PELCPICR
Transaction program name (TPN) is in hexadecimal? no
PIP data ? no
Conversation type either
Sync level none/confirm
Resource security level none
Full path to TP executable /home/PELIUNIX/bin/PELCPICR
Multiple instances supported? yes
This next example is an extract of the result, when we make an export of the SNA
configuration in a text file with SMIT (Export Configuration Profiles).

local_tp:
prof_name "PHDCPICR"
tp_name "PHDCPICR"
tp_name_in_hex no
pip_data_present no
pip_data_subfields_number 0
conversation_type either
sync_level none/confirm
resource_security_level none
resource_access_list_profile_name ""
full_path_tp_exe "/home/PELIUNIX/bin/PHDCPICR"
multiple_instances yes
user_id 211
server_synonym_name ""
restart_action once
communication_type signals
ipc_queue_key 0
standard_input_device "/tmp/PHDCPCIR"
standard_output_device "/tmp/PHDCPICR"
standard_error_device "/tmp/PHDCPICR"
comments ""

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

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

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 directly
used by the Inter.Pel monitor.

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

All the other resources have to be configured according to the network
environment.

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

Current profile names : PXMVSA
Partner READ name : PXMVSC2
Remote transaction program : PELCPICR
Service transaction program : NO
Mode name : PELICAN

"Partner LU name" corresponds to a "logical connection profile" where parameters
are defined for an attachment LU-LU. The "remote transaction program" defines
the 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 remote
site.

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

PELCPICR: For the transfers in PEL protocol
PHDCPICR: For the transfers in PeSIT HS D
PHECPICR: For the transfers in PeSIT HS E

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
These shell scripts are located in <software>/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 : PELCPICR
Transaction program name : PELCPICR
PIP dated : NO
Typical transaction : basic
Recovery level : no reconnect
Syn level : confirm
Full path to TPN executable :/home/PELIUNIX/bin/PELCPICR
Multiple instance : YES
To use ID : 111
Server synonym name :
Restart action : once
Communication type : signals
Standard INPUT file/device : /dev/null
Standard OUTPUT file/device : /dev/null
Standard ERROR file/device : /dev/null
Security required : none
Current profiles name : PHDCPICR
Transaction program name : PHDCPICR
PIP data : NO
Transaction type : basic
Recovery level : no reconnect
Syn level : confirm
Full path to TPN executable : PELIUNIX/bin/PHDCPICR
Multiple instances : YES
User ID : 111
Server synonym name :
Restart action : once
Communication type : signals
Standard INPUT file/device : /dev/null
Standard OUTPUT file/device : /dev/null
Standard ERROR file/device : /dev/null
Security 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
<software>/run_time/tmp. Redirection can be suppressed if traces are not used.

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 to
access 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/IP
networking. These services are available as a standard feature under the HPUX
Operating 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 address
TCP/IP services.

TCP/IP:

- the local port numbers that are to be used by Inter.Pel in order to
receive incoming connections. A different port number must be
assigned to each configured File Transfer protocol. This information
must 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 port
numbers are not currently in use and will not be attempted to be used by
any 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 as
authoritative host for incoming connections. You may use the host
name of the local machine, the looped address (localhost or 127.0.0.1), or
an empty address for this purpose.

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
Inter.Pel parameters that apply to outgoing connections are gathered in site
objects. For each remote machine and each configured transfer protocol, a site
command can be used to create Inter.Pel sites.

The following is an example of site creation using peladm create_site command
for a site in PEL protocol at dotted IP address 193.56.234.50 and port number
22001.


for 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 provide
X25/9000 service interfaces.
8.4.2. X25 configuration

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

- a protocol-id must be supplied for each protocol configured for X25
incoming connections. A one to one relationship must be maintained
between protocols and protocol-id values. In other words, different
protocols must be configured with different protocol-ids,

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

object must be created and supplied with the X25 address and the user data
Windows GUI Interface, the pelop screen interface ,or the peladm line-mode
command can be used to create Inter.Pel Sites.

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
Example of Site creation using peladm create_site command for a site in PEL
protocol at X25 address 9920033 linking on B and protocol-id c9.

peladm create_site ct X25-pr PEL -a SITE2 -pi SITE2 -da B.9920033 ud 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 and
must 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 support
of SNAPLUS2.
8.5.2.1. Configuring the SNA connectivity

This operation may highly vary depending on the actual topology of the SNA
network. You may use the X-motif GUI interface xsnapadmin to configure the
SNA connectivity on your system.

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

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

You are expected to follow respectively the below menu items under xsnapadmin
to 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.cfg
file.

To understand the parameters that address SNA connectivity, you must refer to the
related HPUX SNAPLUS2 documentation. Below are given some excerpts of a
sample sna_node.cfg file that illustrate some of the parameters involved in the
SNA connectivity configuration data.

__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
Example of local node configuration
[define_node]
cp_alias = pxhpx3
description = ""
fqcp_name = SOPRA.PXHPX3
node_type = LEN_NODE
mode_to_cos_map_supp = NO
mds_supported = YES
node_id = <05d0000f>
max_locates = 1500
dir_cache_size = 255
max_dir_entries = 0
locate_timeout = 0
reg_with_nn = YES
reg_with_cds = YES
mds_send_alert_q_size = 100
cos_cache_size = 24
tree_cache_size = 40
tree_cache_use_limit = 40
max_tdm_nodes = 0
max_tdm_tgs = 0
max_isr_sessions = 1000
isr_sessions_upper_threshold = 900
isr_sessions_lower_threshold = 800
isr_max_ru_size = 16384
isr_rcv_pac_window = 8
store_endpt_rscvs = NO
store_isr_rscvs = NO
store_dlur_rscvs = NO
dlur_support = YES
pu_conc_support = YES
nn_rar = 128
max_ls_exception_events = 0
ms_support = NORMAL
queue_nmvts = YES
ptf_flags = NONE
Example of port definition (X25)
[define_qllc_dlc]
dlc_name = QLLC0
description = ""
card_type = QLLC_NLI
[define_qllc_port]
port_name = QLLCP0
description = ""
dlc_name = QLLC0
port_number = 0
address = ""
implicit_hpr_support = NO
max_rcv_btu_size = 265
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
tot_link_act_lim = 255
inb_link_act_lim = 0
out_link_act_lim = 0
ls_role = LS_NEG
implicit_dspu_services = NONE
implicit_dspu_template = ""
implicit_ls_limit = 0
act_xid_exchange_limit = 9
nonact_xid_exchange_limit = 5
ls_xmit_rcv_cap = LS_TWS
max_ifrm_rcvd = 7
implicit_cp_cp_sess_support = YES
implicit_limited_resource = NO
implicit_deact_timer = 30
effect_cap = 9600
connect_cost = 0
byte_cost = 0
driver_name =
cud_mode = IDENTITY
cud_match = <>
add_mode = DONTCARE
add_len = 0
vc_type = SVC
loc_wsize = 0
rem_wsize = 0
retry_limit = 2
retry_timeout = 8
idle_timeout = 48

Example of link station definition
[define_qllc_ls]
ls_name = QLLCL0
description = ""
port_name = QLLCP0
adj_cp_name = BP063A.H000A
adj_cp_type = BACK_LEVEL_LEN_NODE
dspu_services = NONE
dspu_name = <0000000000000000>
dlus_name = <0000000000000000000000000000000000>
bkup_dlus_name = <0000000000000000000000000000000000>
local_node_id = <05d630c7>
adj_node_id = <00000000>
vc_type = SVC
address = 17745971368
pvc_id = 1
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
ls_attributes = SNA
cp_cp_sess_support = YES
default_nn_server = YES
hpr_supported = NO
auto_act_supp = NO
tg_number = 1
limited_resource = NO
solicit_sscp_sessions = NO
pu_name = QLLCL0
disable_remote_act = NO
link_deact_timer = 30
use_default_tg_chars = YES
effect_cap = 9600
connect_cost = 0
byte_cost = 0
ls_role = USE_PORT_DEFAULTS
max_ifrm_rcvd = 0
dlus_retry_timeout = 0
dlus_retry_limit = 0
react_timer = 30
react_timer_retry = 65535
req_rev_charge = NO
loc_wsize = 0
rem_wsize = 0
fac = <>
retry_limit = 5
retry_timeout = 3
idle_timeout = 30
sn_id = 0
cud = <c3>
8.5.2.2. Configuring APPC/CPIC resources

Inter.Pel uses the CPIC programming Interface to communicate over SNA
networks. 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,
__________________________________________________________________________________________________

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 remote
machine.

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

The following menu entries may be used from xsnapadmin to configure these
items:

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 transfer
protocols and both outgoing and incoming conversations, such a configuration is
not recommended. You may, instead, configure either a different Local LU for
each file transfer protocol, or several different Local LUs for each protocol.

__________________________________________________________________________________________________

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 = PELI
list_name = ""
description = ""
lu_name = PELI
lu_session_limit = 0
pu_name = <0000000000000000>
nau_address = 0
default_pool = NO
syncpt_support = NO
lu_attributes = NONE
sscp_id = 0
disable = NO
sys_name = ""
timeout = 60
back_level = NO
Partner LU definition

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

Example of partner LU definition


[define_partner_lu]
plu_alias = RS04
description = ""
fqplu_name = SOPRA.RS04
plu_un_name = RS04
parallel_sess_supp = YES
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
appcip_routing_preference = NATIVE
max_mc_ll_send_size = 0
conv_security_ver = NO
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 local
machine). A simple LU6.2 configuration for Inter.Pel that uses the same mode for
all 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 be
created.

Example of mode definition


[define_mode]
mode_name = PELMODE
description = ""
max_neg_sess_lim = 32767
plu_mode_session_limit = 2
min_conwin_src = 1
min_conloser_src = 0
auto_act = 0
receive_pacing_win = 4
max_receive_pacing_win = 0
default_ru_size = YES
max_ru_size_upp = 1024
max_ru_size_low = 0
cos_name = #CONNECT

CPIC side info definition

A CPIC side info profile must be created for each Inter.Pel remote site to which
Inter.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 be
created in any order, but the CPIC side info profile that addresses a given remote
site must exist when Inter.Pel attempts to connect to this site.

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

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

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

__________________________________________________________________________________________________

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 = PELCPICI
description = ""
lu_alias = PELI
partner_lu_name = PELR
mode_name = PELMODE
tp_name_type = APPLICATION_TP
tp_name = PELCPICR
conversation_security_type = NONE
security_user_id = ""
security_password = ""
TP (Transaction Program) definition

For each incoming conversation intended for Inter.Pel, the SNA subsystem is
expected to start an appropriate Inter.Pel application program. For that to be
achieved, a Transaction Program profile must have been created for each
configured file transfer protocol.

The actual PATH field of the transaction program that is to be supplied depends
on the file transfer protocol that is addressed 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 and
group-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 corresponding
TP name.
If for example, the TP name is PHECPICR, this field must contain
APPCTPN=PHECPICR.

Example of Transaction Program definition:

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

[PELCPICR]
LUALIAS = ""
DESCRIPTION = ""
USERID = portpel
GROUP = interpel
TIMEOUT = 0
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.
TYPE = NON-QUEUED
PATH = /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 xsnapadmin GUI can be summarized
as 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, check
the SNA log and trace files and fix the problem. The cause may be due
to a misconfiguration on a remote machine.

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

4. Try to establish manually LU-LU sessions (using the appropriate
xsnapadmin command). Fix any problem on the local and remote
machines 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.2
must have this feature enabled. This can be achieved the first time
Inter.Pel is set up by selecting the corresponding option, or changed later
using the pelconf command,

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

- for each remote system expected to accept SNA conversations initiated
by the local Inter.Pel instance, a remote site that contains the
corresponding CPIC side info profile name such as destination address
field must be created. This can be achieved using the GUI interface, the
pelop screen interface, or the peladm line 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 prevents
the actual file transfer from being processed normally, enabling the
trace mode for that site and setting up traces and logging facility in the
SNA sub-system will produce outputs that may help track the
problem.

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 the
CPIC programming interface.

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

TCP/IP:

The local port numbers that are used by Inter.Pel in order to receive incoming
connections. A different port number must be assigned to each configured File
Transfer 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 that
these port numbers are not currently in use and will not be attempted to be used by
any other application on the 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 as
host name for the binding to listen ports. You may use, either the host
name of the local machine, the looped address (localhost or 127.0.0.1) or an
empty address for this purpose.


Example of site creation using peladm create_site command for a site in PEL
protocol at dotted IP address 193.56.234.50 and port number 22001.


for sites intended to be connected to by Inter.Pel over TCP/IP.
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 incoming
connections. A one to one relationship must be maintained between protocols and
call user data values. In other words, different protocols must be configured with

When more than one X25 interface is installed on the system, it is possible to
restrict Inter.Pel connections to a specific X25 interface. This is achieved by
providing the link id. (number 09) of this interface as device name when
configuring the server side of protocols.
9.5. LU6.2 network interface

Inter.Pel supports the SNAP-IX product from Data-Connection under the
SOLARIS operating system. This product originates from the SNAPS (SNA
portable software) from the same supplier as Communication Server on IBM AIX
and SNAPLUS 2 on HP/UX. As a result, the sections of this documentation that
describe LU6.2 installation on either AIX or HPUX must be referred to for the
configuration of LU6.2 services for Inter.Pel under SOLARIS.
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 that
the Operating System is compatible with RedHat/Linux 6.1/i386.

A different port number must be assigned to each configured File Transfer
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 that these port
numbers are not currently in use and will not be attempted to be used by any 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 as
host name for the binding to listen ports. You may use the host name of the local
machine, the looped address (localhost or 127.0.0.1), or an empty address for this
purpose.


Example of site creation using peladm create_site command for a site in PEL
protocol at dotted IP address 193.56.234.50 and port number 22001.


as 193.56.234.50, for example) can be specified as the IP destination address
field for sites intended to be connected to by Inter.Pel over TCP/IP.
10. Appendix for LINUX Installation & Configuration Manual for UNIX Page 48
__________________________________________________________________________________________________

Inter.Pel .1 SOPRA.

Installation and Configuration Manual For UNIX

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation and Configuration Manual For UNIX

Uploaded by

Copyright:

Available Formats

0102-66-02-OUNX6600

You might also like