PELV7.3 Installation and Implementation Guide

XFB. Inter.Pel V7.
3
Installation
and Implementation Guide
Copyright
The information contained in this document is subject to revision without prior
notice and shall not be regarded as binding on Axway Software. 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 Axway Software is strictly prohibited.
Axway Software, 2003.

All rights reserved. All trademarks registered.
Table of Contents
1. GENERAL PRESENTATION ........................................................................... 1-1
1.1 OVERVIEW .................................................................................................................................... 1-1
1.2 Inter.Pel ENVIRONMENT............................................................................................................ 1-2
1.3 DEFINITIONS ................................................................................................................................ 1-3

1.3.1 TRANSFER TYPES .................................................................................................................... 1-3
1.3.2 ROUTING CONCEPT................................................................................................................. 1-3
1.3.3 ACKNOWLEDGEMENTS ......................................................................................................... 1-4
1.3.4 PELICANIZATION..................................................................................................................... 1-4
1.3.5 DEPELICANIZATION................................................................................................................ 1-4
1.4 FILE NAME MANAGEMENT BY INTER.PEL ........................................................................ 1-4
1.5 DISK SPACE MANAGEMENT.................................................................................................... 1-5
1.6 MAILBOX....................................................................................................................................... 1-5
1.7 ACCESS SECURITY ..................................................................................................................... 1-6
1.8 SERVICES....................................................................................................................................... 1-6

1.8.1 INTER.PEL SERVICES .............................................................................................................. 1-6
1.8.2 USER SERVICES (EXITS)......................................................................................................... 1-7
1.9 GENERAL STRUCTURE.............................................................................................................. 1-8

1.9.1 MULTIPLE ADDRESS SPACES................................................................................................ 1-8
1.9.2 DIAGRAM OF THE VARIOUS ADDRESS SPACES ............................................................. 1-10
1.9.3 MULTIPLE TASKS .................................................................................................................. 1-10
1.9.4 DIAGRAM OF THE VARIOUS TRANSFER MONITOR TASKS ......................................... 1-11
1.9.5 TABLES..................................................................................................................................... 1-12
1.10 DOCUMENTATION.................................................................................................................... 1-12
2. INSTALLATION ............................................................................................... 2-1
2.1 RESOURCES REQUIRED ............................................................................................................ 2-1
2.2 INSTALLATION PRINCIPLES ................................................................................................... 2-2
2.3 RESTORING THE FILES ............................................................................................................. 2-3

2.3.1 RESTORING THE FILES FROM TAPE .................................................................................... 2-3
2.3.2 RESTORING THE FILES FROM CD ........................................................................................ 2-4
2.3.2.1 Content of the distribution CD............................................................................................ 2-4
2.3.2.2 Installation of Inter.Pel from the CD................................................................................... 2-4
2.4 CUSTOMIZING THE CNTL AND SAMPLIB FILES ............................................................... 2-7
2.5 CREATING THE TABLES ........................................................................................................... 2-7
2.6 CREATING THE UNIT TABLE................................................................................................... 2-7
Installation and Implementation Guide Table of Contents iii

2.7 CREATING THE FILES AND ALIASES .................................................................................... 2-8
2.7.1 LIST OF FILES TO BE CREATED ............................................................................................ 2-8
2.7.2 LIST OF ALIASES TO BE CREATED ...................................................................................... 2-8
2.7.3 MAILBOX FILE.......................................................................................................................... 2-8
2.7.4 LOG FILES .................................................................................................................................. 2-9
2.7.5 AUDIT FILES............................................................................................................................ 2-10
2.7.6 ACTION REPORT FILES......................................................................................................... 2-10
2.7.7 STATISTICS FILES .................................................................................................................. 2-11
2.7.8 CONTROL FILE........................................................................................................................ 2-11
2.7.8.1 CONTROL FILE FOR A VSAM MAILBOX.................................................................. 2-11
2.7.8.2 CONTROL FILE FOR A DB2 MAILBOX...................................................................... 2-12
2.8 COMMUNICATION SVC........................................................................................................... 2-13

2.8.1 INSTALLING THE COMMUNICATION SVC ....................................................................... 2-13
2.9 XCF DEFINITIONS ..................................................................................................................... 2-14

2.9.1 SAMPLE COUPLE FILE DEFINITION................................................................................... 2-15
2.10 VTAM DEFINITIONS ................................................................................................................. 2-15

2.10.1 OBJECTS TO BE DEFINED................................................................................................ 2-15
2.10.2 SAMPLE VTAM DEFINITIONS......................................................................................... 2-16
2.11 AUTOMATIC JCL EXECUTION.............................................................................................. 2-17
2.12 INTER.PEL EXECUTION .......................................................................................................... 2-30

2.12.1 RUNNING THE REQUEST SERVER................................................................................. 2-30
2.12.2 RUNNING THE MAILBOX SERVER ................................................................................ 2-31
2.12.3 RUNNING THE TRANSFER MONITOR ........................................................................... 2-32
2.12.4 STARTING UP THE ADDRESS SPACES.......................................................................... 2-33
2.13 INITIALIZATION TRANSACTIONS ....................................................................................... 2-34
2.14 MIGRATING FROM VERSION 7.1 .......................................................................................... 2-34
3. PARAMETER SETTING .................................................................................. 3-1
3.1 GENERAL PRINCIPLES .............................................................................................................. 3-1

3.1.1 Inter.Pel TABLES ........................................................................................................................ 3-1
3.1.2 INSTALLING THE TABLES ..................................................................................................... 3-2
3.1.2.1 DESCRIPTION .................................................................................................................. 3-2
3.1.2.1.1 Definitions Loaded by the Request Server ..................................................................... 3-2
3.1.2.1.2 Definitions Loaded by the MAILBOX Server ............................................................. 3-10
3.1.2.1.3 Definitions Loaded by the Transfer Monitor................................................................ 3-15
3.1.2.1.4 Definitions Loaded in BATCH Mode.......................................................................... 3-19
3.1.2.2 DYNAMIC MODIFICATIONS ....................................................................................... 3-19
3.1.3 TABLES CREATED DYNAMICALLY ................................................................................... 3-20
3.1.3.1 PRINCIPLES.................................................................................................................... 3-20
3.1.3.2 DEPOSITING TRANSFER REQUESTS ........................................................................ 3-21
3.1.3.3 ROUTING TOWARDS SITES DYNAMICALLY CREATED. ..................................... 3-22
3.1.3.4 TRANSACTIONS ON SITES CREATED DYNAMICALLY ........................................ 3-22
3.2 CREATING THE ENVIRONMENT TABLE............................................................................ 3-23

3.2.1 GENBIND - CREATING A VTAM BIND ............................................................................... 3-23
3.2.2 GENCENT - DEFINING HOSTS ............................................................................................. 3-24
3.2.3 GENDEB - CREATING THE BEGINNING OF THE PARAMETER TABLE....................... 3-25
3.2.4 GENDSN - DEFINING A RECEIVE FILE NAME .................................................................. 3-35
3.2.5 GENEND - CREATING THE END OF THE ENVIRONMENT TABLE ............................... 3-38
Installation and Implementation Guide Table of Contents iv

3.2.6 GENFILE- DEFINING AN APPLICATION ............................................................................ 3-39
3.2.7 GENLIGN - CREATING A LINE HANDLER- CONTROL BLOCK...................................... 3-46
3.2.8 GENLOGON - CREATING A LOGON.................................................................................... 3-49
3.2.9 GENLU - CREATING A HOMOGENEOUS MVS-MVS LINK.............................................. 3-50
3.2.10 GENMGER - CREATING A SESSION MANAGER CONTROL BLOCK ........................ 3-52
3.2.11 GENPFK - CREATING A FUNCTION KEY TABLE ........................................................ 3-53
3.2.12 GENPOINT - POINTING TO GENLIGN OR GENMGER................................................. 3-54
3.2.13 GENSAF - DEFINING AN EXTERNAL SECURITY PROFILE........................................ 3-55
3.2.14 GENSITE - CREATING A SITE DEFINITION CONTROL BLOCK ............................... 3-60
3.2.15 GENSSLDN Creating a distinguished name alias .............................................................. 3-70
3.2.16 GENSSLP Create an SSL security profile.......................................................................... 3-71
3.2.17 GENTER - CREATING A TERMINAL CONTROL BLOCK............................................. 3-74
3.2.18 GENTRAN - CREATING THE TRANSACTION TABLE ................................................. 3-83
3.2.19 ASSIGNING GENTER ENTRIES AUTOMATICALLY .................................................... 3-84
3.2.20 ORDER OF THE MACRO-INSTRUCTIONS ..................................................................... 3-85
3.2.21 SAMPLE ENVIRONMENT TABLE ................................................................................... 3-86
3.3 CREATING THE ROUTING TABLE...................................................................................... 3-103

3.3.1 GENDST0 - CREATING THE ROUTING TABLE ............................................................... 3-103
3.3.2 GENDST1 - DEFINING APPLICATIONS............................................................................. 3-104
3.3.3 GENDST2 - DEFINING REMOTE SITES ............................................................................. 3-105
3.3.4 GENDST3 - DEFINING THE LOCAL SITE.......................................................................... 3-106
3.3.5 ORDER OF THE MACRO-INSTRUCTIONS ........................................................................ 3-107
3.3.6 SAMPLE ROUTING TABLE ................................................................................................. 3-107
3.4 BROADCAST LIST TABLE ..................................................................................................... 3-109

3.4.1 DESCRIPTION........................................................................................................................ 3-109
3.4.2 BROADCAST LIST TABLE................................................................................................... 3-110
3.4.3 SAMPLE BROADCAST LIST TABLE .................................................................................. 3-111
3.5 MANAGING X.25 ACCESSES ................................................................................................. 3-112

3.5.1 DESCRIPTION........................................................................................................................ 3-112
3.5.2 X25TABLE .............................................................................................................................. 3-113
3.5.3 SAMPLE X25TABLE ............................................................................................................. 3-116
3.6 MANAGING TCP/IP ACCESSES ............................................................................................ 3-118

3.6.1 DESCRIPTION........................................................................................................................ 3-118
3.6.2 IPTABLE ................................................................................................................................. 3-118
3.6.3 SAMPLE IPTABLE................................................................................................................. 3-122
3.7 MANAGING MODELS ............................................................................................................. 3-123

3.7.1 DESCRIPTION........................................................................................................................ 3-123
3.7.2 GENMODEL: CREATING A MODEL-TYPE ENTRY......................................................... 3-124
3.7.3 GENETB12: CREATING AN ETEBAC1/2 ENTRY ............................................................. 3-134
3.7.4 GENETEB3: CREATING AN ETEBAC3 ENTRY ................................................................ 3-137
3.7.5 GENETEB5: CREATING AN ETEBAC5 ENTRY ................................................................ 3-141
3.7.6 GENFTP: CREATING A FTP ENTRY .................................................................................. 3-146
3.7.7 GENODET: CREATING AN ODETTE ENTRY ................................................................... 3-150
3.7.8 GENPEL: CREATING A PEL ENTRY .................................................................................. 3-154
3.7.9 GENPEL2: CREATING A PEL2 ENTRY .............................................................................. 3-158
3.7.10 GENSIT: CREATING A PeSIT SIT ENTRY..................................................................... 3-162
3.7.11 GENSITH: CREATING A PeSIT HORS SIT ENTRY ...................................................... 3-165
3.7.12 SAMPLE MODEL TABLE ................................................................................................ 3-170
3.8 USER MESSAGES ..................................................................................................................... 3-173

3.8.1 DESCRIPTION........................................................................................................................ 3-173
3.8.1.1 Parameters Passed........................................................................................................... 3-174
3.8.2 USER MESSAGE TABLE ...................................................................................................... 3-175
Installation and Implementation Guide Table of Contents v

3.8.3 SAMPLE USER MESSAGE TABLE...................................................................................... 3-178
3.9 INTER-TABLE CORRELATION ............................................................................................ 3-179

3.9.1 ENVIRONMENT AND ROUTING TABLE NAMES............................................................ 3-179
3.9.2 ADDING A NEW APPLICATION ......................................................................................... 3-179
3.9.3 ADDING A NEW DESTINATION OR SOURCE.................................................................. 3-179
3.9.4 DEFINING AN X.25 ACCESS ............................................................................................... 3-179
3.10 UNIT TABLE .............................................................................................................................. 3-180
3.11 DEFINING Inter.Pel-CICS CONNECTIONS.......................................................................... 3-182

3.11.1 OVERVIEW........................................................................................................................ 3-182
3.11.2 ARCHITECTURE............................................................................................................... 3-183
3.11.2.1 TRANSMISSION REQUEST ........................................................................................ 3-183
3.11.2.2 FILE RECEPTION......................................................................................................... 3-185
3.11.3 CICS DEFINITIONS .......................................................................................................... 3-186
3.11.3.1 TRANSFERRING FILES FROM Inter.Pel TO CICS (FILE RECEPTION) ................. 3-186
3.11.3.1.1 Macro-instruction definitions ................................................................................... 3-186
3.11.3.1.2 RDO definitions ....................................................................................................... 3-187
3.11.3.2 TRANSFERRING FILES FROM CICS TO Inter.Pel (FILE TRANSMISSION)........ 3-190
3.11.3.2.1 Macro-instruction definitions ................................................................................... 3-190
3.11.3.2.2 RDO definitions ....................................................................................................... 3-191
3.11.4 SETTING Inter.Pel PARAMETERS .................................................................................. 3-198
3.11.4.1 TRANSFERRING FILES FROM Inter.Pel TO CICS (FILE RECEPTION) ................. 3-198
3.11.4.2 TRANSFERRING FILES FROM CICS TO Inter.Pel (FILE TRANSMISSION)........ 3-198
3.11.5 SPECIFIC TABLES............................................................................................................ 3-199
3.11.5.1 LIST OF PEL TRANSFERS TO BE ROUTED TO CICS: PELTABAP ...................... 3-199
3.11.5.2 LIST OF PeSIT SIT TRANSFERS TO BE ROUTED TO CICS: PELSITTB .............. 3-201
3.11.5.3 CICS TRANSACTION AND TERMINAL TABLE: PELCITER ................................. 3-203
3.12 COUPLINGS............................................................................................................................... 3-206

3.12.1 PRINCIPLES....................................................................................................................... 3-206
3.12.2 IMPLEMENTING COUPLING IN Inter.Pel...................................................................... 3-209
3.12.2.1 CREATING AND INITIALIZING THE MESSAGE FILE........................................... 3-209
3.12.2.2 MODIFYING THE Inter.Pel STARTUP JCL................................................................ 3-210
3.12.2.3 UPDATING THE ENVIRONMENT TABLE ............................................................... 3-210
3.12.2.4 STARTING THE COMMUNICATION TASK............................................................. 3-212
3.12.3 Inter.Set DEFINITIONS...................................................................................................... 3-212
3.12.4 CICS DEFINITIONS .......................................................................................................... 3-214
3.12.5 MQSeries DEFINITIONS ................................................................................................... 3-218
3.12.6 VTAM DEFINITION.......................................................................................................... 3-219
APPENDIX A USING THE X25 NPSI PCNE FUNCTION ................................. A-1

A.1 INTRODUCTION.......................................................................................................................... A-1
A.2 MAJOR SWITCHED NODE TABLE ......................................................................................... A-2
A.3 MAJOR SWITCHED NODE DEFINITION EXAMPLE.......................................................... A-3
A.4 SEQUENCE OF OPERATIONS .................................................................................................. A-4
A.5 SUMMARY DIAGRAM ............................................................................................................... A-5
Installation and Implementation Guide Table of Contents vi

APPENDIX B USING THE X25 NPSI GATE FUNCTION ................................. B-1
B.1 X25NPSI GENERATION...............................................................................................................B-1
B.2 MAJOR SWITCHED NODE.........................................................................................................B-1
APPENDIX C USING SMS................................................................................ C-1
C.1 SETTING INTER.PEL PARAMETERS ..................................................................................... C-1
C.2 CONSTRAINTS............................................................................................................................. C-1
APPENDIX D USING LU 6.2............................................................................. D-1
D.1 INTRODUCTION.......................................................................................................................... D-1
D.2 VTAM DEFINITIONS .................................................................................................................. D-3
D.3 INTER.PEL DEFINITIONS ......................................................................................................... D-7
D.4 INTER.PEL TRACES IN LU 6.2 MODE .................................................................................... D-9
APPENDIX E USING TCP/IP................................................................................ E-1
E.1 INTRODUCTION...........................................................................................................................E-1
E.2 INTER. PEL PARAMETERS FOR TCP/IP ................................................................................E-2

E.2.1 SPECIFIC PARAMETERS ......................................................................................................... E-2
E.2.1.1 GENLIGN .......................................................................................................................... E-2
E.2.1.2 GENTER ............................................................................................................................ E-2
E.2.2 IPTABLE (Common INTERLINK and IBM parameters) ........................................................... E-4
E.2.3 SAMPLE IPTABLE..................................................................................................................... E-7
E.3 INTERLINK/IBM TCP/IP SPECIFIC PARAMETERS AND REQUIREMENTS..................E-8

E.3.1 INTERLINK SNS/TCPACCESS PARAMETERS...................................................................... E-8
E.3.2 IBM SPECIFIC PARAMETERS AND REQUIREMENTS........................................................ E-8
E.3.2.2 PORT DEFINITIONS ........................................................................................................ E-8
E.3.2.3 DEFINITIONS USING SYMBOLIC NAMES .................................................................. E-9
E.4 SAMPLE INTER.PEL DEFINITIONS FOR INTERLINK AND IBM TCP/IP .....................E-12
E.4.1 SAMPLE INTER.PEL DEFINITIONS FOR INTERLINK....................................................... E-12
E.4.2 SAMPLE INTER.PEL DEFINITIONS FOR IBM TCP/IP ....................................................... E-13
E.4.3 SAMPLE INTER.PEL DEFINITIONS COMMON TO INTERLINK/IBM TCP/IP ................ E-13
E.4.4 SAMPLE INTER.PEL DEFINITIONS COMMON TO INTERLINK/IBM TCP/IP ............... E-14
E.5 EXITS.............................................................................................................................................E-16
E.5.1 MANAGING INCOMING TCP/IP CONNECTIONS: EXIPIN ............................................... E-16
E.5.2 MANAGING OUTGOING TCP/IP CONNECTIONS: EXIPOUT........................................... E-19
E.6 INITIALIZING THE IPTABLE..................................................................................................E-22
E.7 DISPLAYING AND MODIFYING IPTABLE ENTRIES .......................................................E-22
Installation and Implementation Guide Table of Contents vii

E.8 TCP/IP TRACES ..........................................................................................................................E-22
E.8.1 TCP/IP TRACES IN AN INTERLINK SNS/TCPACCESS ENVIRONMENT........................ E-22
APPENDIX F USING HSI ..................................................................................... F-1
F.1 INTRODUCTION...........................................................................................................................F-1
F.1.1 Authentication .............................................................................................................................. F-1
F.1.2 Encryption .................................................................................................................................... F-2
F.1.3 Sealing.......................................................................................................................................... F-2
F.1.4 X.509 Certificates......................................................................................................................... F-2
F.2 PRINCIPLES OF INTEGRATION IN Inter.Pel .........................................................................F-3

Inter.Pel Operation Diagram....................................................................................................................... F-4
F.3 PROCESSING IN THE X.509 ELEMENT FILES ......................................................................F-5

F.3.1 File Element Processing Procedure .............................................................................................. F-5
F.3.2 X.509 Element Retrieval Program................................................................................................ F-6
F.3.3 Utility Populating the Inter.Pel Files with the X.509 Elements .................................................... F-6
F.3.4 File Formats.................................................................................................................................. F-7
F.3.4.1 Temporary File ................................................................................................................... F-7
F.3.4.2 X.509 Certificate and Private Key File............................................................................... F-7
F.3.4.3 Authority File...................................................................................................................... F-7
F.3.5 SAMPLE RUN-TIME JCL .......................................................................................................... F-8
F.3.6 RETURN CODES........................................................................................................................ F-8
F.4 DEFINITIONS IN INTER.PEL................................................................................................... F-9
F.4.1 GENDEB Macro ..................................................................................................................... F-9
F.4.2 GENTER Macro...................................................................................................................... F-9
F.5 RESTRICTIONS........................................................................................................................ F-11
APPENDIX G XFB.SCOPE AGENT..................................................................G-1
G.1 INTRODUCTION.......................................................................................................................... G-1
G.2 Prerequisites ................................................................................................................................... G-2
G.3 Installing XFB.Scope ...................................................................................................................... G-3

G.3.1 Adapting the Installation JCLs to the Production Environment ...................................................G-3
G.3.2 Customizing the XFB.Scope Agent Installation Files (NT00CUST) ............................................G-3
G.3.3 LINK EDITING the Agent Modules (NT10LTCP) .....................................................................G-5
G.3.4 Creating the Message File (NT20MSG).......................................................................................G-6
G.3.5 Creating an Agent Configuration (NT30INST)............................................................................G-6
G.3.5.1 Return Codes ....................................................................................................................G-10
G.3.6 Defining the Buffering File (NT40DEF) ....................................................................................G-10
G.4 Configuration ............................................................................................................................... G-12

G.4.1 Updating the Inter.Pel Configuration .........................................................................................G-12
G.4.2 Updating the Message Table ......................................................................................................G-12
G.4.3 selecting tracker level.................................................................................................................G-13
G.5 Operations .................................................................................................................................... G-14

G.5.1 Starting Up the Agent.................................................................................................................G-14
G.5.1.1 Sample JCL.......................................................................................................................G-15
G.5.1.2 Log Files ...........................................................................................................................G-16
G.5.1.3 Other Output Files ............................................................................................................G-16
G.5.2 Commands..................................................................................................................................G-16
G.5.2.1 Current Status: NTFQLT ACT .........................................................................................G-16
G.5.2.2 Activating the Log: NTFQLT LOGACT ..........................................................................G-16
Installation and Implementation Guide Table of Contents viii

G.5.2.3 Deactivating the Log: NTFQLT LOGINACT ..................................................................G-17
G.5.2.4 Log Swapping: LOG SWAP.............................................................................................G-17
G.5.3 Shutting Down the Agent ...........................................................................................................G-17
G.6 Return Codes................................................................................................................................ G-18
APPENDIX H IUI API SERVER......................................................................... H-1
H.1 INTRODUCTION.......................................................................................................................... H-1
H.2 Prerequisites ................................................................................................................................... H-2
H.3 Installing the IUI API server......................................................................................................... H-3

H.3.1 Adapting the Installation JCLs to the Production Environment ...................................................H-3
H.3.2 Customizing the XFB.IUI API Server Installation Files (IU00CUST) .........................................H-4
H.3.3 LINK-EDITING the API Server Modules (IU10LINK) ..............................................................H-6
H.4 Configuration ................................................................................................................................. H-7
H.5 Operations ...................................................................................................................................... H-8

H.5.1 Starting Up the API Server...........................................................................................................H-8
H.5.1.1 Sample JCL.........................................................................................................................H-9
H.5.1.2 TRACE Files ....................................................................................................................H-10
H.5.2 Shutting Down the API Server ...................................................................................................H-10
H.6 Return Codes................................................................................................................................ H-11
APPENDIX I SENTINEL....................................................................................... I-1
I.1 INTRODUCTION ................................................................................................................................I-1
I.2 PrErequisites .........................................................................................................................................I-2
I.3 Configuration ........................................................................................................................................I-3

I.3.1 UPDATING Inter.Pel GENERAL PARAMETERS ..................................................................... I-4
I.3.2 MESSAGE TABLE INTEGRATION .......................................................................................... I-5
I.3.3 PARTICIPATION OF SITES OR APPLICATIONS IN Sentinel TRACKING........................... I-5
I.3.4 CONFIGURING THE AGENT AND THE EVENT ROUTER ................................................... I-5
I.4 OpErationS............................................................................................................................................I-6
I.4.1 PARAMETERS CONCERNING REQUESTS ............................................................................ I-6
I.4.2 SUPPLYING TRACKING ELEMENTS...................................................................................... I-7
I.4.3 TRACKING STOP AND START COMMANDS ........................................................................ I-7
I.4.4 USING THE LOGGER OF THE UNIVERSAL AGENT ............................................................ I-8
I.4.5 OTHER OUTPUT FILES ............................................................................................................. I-8
Installation and Implementation Guide Table of Contents ix

1. GENERAL PRESENTATION
1.1 OVERVIEW
The Inter.Pel software is designed to control and manage file exchanges in a distributed
system environment based on a homogeneous or heterogeneous architecture.
It performs direct-type transfers, so that the file transmitted is restored in the receiving
system's environment as if it were a newly created file and it can be used immediately; the
transfer operations are managed and controlled automatically by the Inter.Pel transfer monitor
and may be monitored from screens connected to Inter.Pel or from the system console.
In HOMOGENEOUS environments when exchanges take place between two MVS systems,
Inter.Pel takes charge of, and manages the transfer of all types of file.
In HETEROGENEOUS environments when exchanges take place between two systems
(using the same or different platforms) belonging to different environments, Inter.Pel only
processes and manages sequential or HFS file transfers except for PeSIT Hors-SIT version E
protocol which also accepts PDS, VSAM ESDS, KSDS and RRDS files.
The term Inter.Pel refers to the software developed for the MVS operating system; this
software is described in the following chapters.
Installation and Implementation Guide General Presentation 1-1

1.2 Inter.Pel ENVIRONMENT
MVS
Inter.Pel
BSAM
BPSAM MAILBOX Request

Transfer
server server
VSAM
QSAM
VTAM/BTAM/TCP-IP
NCP
X.25 GATE/PCNE PAD
The Inter.Pel monitoring and control functions are performed from:
- The operating system console

- Any 3270 terminal directly connected to the site or from other sites, themselves
connected to the site
- A batch utility
They can also be performed from external products associated to Inter.Pel:
- Sentinel.
- XFB.IUI (Internet User Interface).

1.3 DEFINITIONS
1.3.1 TRANSFER TYPES
The term transfer type refers to the procedure used to reach a given destination.
Heterogeneous or type 1 transfers
These transfers are performed between two Inter.Pel transfer monitors (or between an Inter.Pel
transfer monitor and another file transfer monitor) belonging to different environments.
They use either the internal Inter.Pel protocol (PEL) or a public domain protocol, such as
ETEBAC, ODETTE, PeSIT or FTP.
The communication systems supported are SNA, SNI, BSC, TCP/IP (Interlink or IBM
product) or X.25 (X25NPSI software in the PCNE, PAD or GATE mode).
The files transferred are sequential or HFS type files except for transfers using PeSIT Hors-
SIT version E protocol which also accepts VSAM ESDS, KSDS and RRDS files as well as
PDS files between two Inter.Pel MVS (1).
Homogeneous MVS-MVS or type 2 transfers
These transfers are performed between two Inter.Pel transfer monitors working in an
IBM/MVS environment.
They use the internal Inter.Pel protocol.
The communication systems supported are SNA or SNI in the CROSS-DOMAIN mode.
Using this mechanism, all types of files may be exchanged (1), irrespective of their sizes and
formats, and without the need to first define them in the transfer monitor.
(1) Except for:
FIXED LENGTH files where LRECL exceeds 32 756
UNDEFINED files where BLKSIZE exceeds 32 756
VARIABLE LENGTH files where LRECL exceeds 32 767
Files result of an IEBCOPY on a PDS whose LRECL exceeds 32724
1.3.2 ROUTING CONCEPT
Routing is the mechanism whereby Inter.Pel automatically forwards on to a new destination

any file received that is not addressed to it.

1.3.3 ACKNOWLEDGEMENTS
When using specific protocols (ODETTE or PeSIT Hors-SIT version E), Inter.Pel is also able
to manage file transfer acknowledgements. ODETTE protocol only supports positive
acknowledgements to notify that the file was successfully received at the final destination.
PeSIT Hors-SIT protocol accepts both positive and negative acknowledgements. It can also
notify that either the file was successfully received at the final destination, or that the
transferred file was successfully processed by the user application on this site.
1.3.4 PELICANIZATION
This operation is required to transfer a non-sequential file: it converts any file into a sequential
file called a Type 2 transfer file. This operation is performed automatically by Inter.Pel and
will:
- Call a utility (IEBCOPY or IDCAMS)

- Compact and compress the file
- Create a transfer file of the following type:
DSORG=PS,RECFM=U,BLKSIZE=(1024 by default)
1.3.5 DEPELICANIZATION
This operation must be performed after receiving a Type 2 transfer file so that it can be used.
It is performed automatically by Inter.Pel to convert the transfer file into a file with the same
properties as those of the source file.
This action will:
- Decompact and decompress the file

- Call a utility (IEBCOPY or IDCAMS)
1.4 FILE NAME MANAGEMENT BY INTER.PEL
The names of the files transmitted by Inter.Pel are:
- The source file name for type 1 transfers

- The pelicanized file name for type 2 transfers
The names of the files received by Inter.Pel are:
- A name created in line with protocol constraints guaranteeing unique file names or a
name defined by a user GENDSN macro, for type 1 transfers. When a GENDSN is
associated with a PeSIT Hors-SIT version E transfer, the target file can also be a PDS
member or an HFS file.
- The name specified by the sender or a name created in line with protocol constraints
guaranteeing unique file names, for type 2 transfers
All these files are dynamically allocated by Inter.Pel.

1.5 DISK SPACE MANAGEMENT
Inter.Pel can allocate files to volumes or unit names that are pre-defined at generation time or
provided by user exits called each time a file is allocated. Disk space management can be
entirely offloaded to SMS, if available.
1.6 MAILBOX
The MAILBOX file is a VSAM-KSDS file in the standard version of Inter.Pel. Optionally, a
DB2 table can be used for the MAILBOX.
There are two types of data in the MAILBOX.
Transfer data
This data relates to transfer requests, such as:
- File name
- Transfer source site
- File destination site
- Transfer status
This data can be accessed via the transaction monitor or the programmable interfaces supplied
with the product.
Control data
This data is of two types:
- Inter.Pel operator management data

- Transfer monitor management data
Some of this data can be accessed by authorized users via the transaction monitor.
MAILBOX management is performed exclusively in a dedicated address space (MAILBOX

SERVER) that receives all requests (read, update, add or delete) via XCF, performs the
requested operations and returns any response, as well as a return code to the calling address
space.
This address space must be initialized prior to any access to the MAILBOX. For performance
reasons, all MAILBOX records are loaded into memory locations above the 16 Mbytes
boundary at the start of this address space.
If the MAILBOX is a VSAM file, an AUDIT file system is used to rebuild it, should it
become corrupted. AUDIT file swaps and MAILBOX backup and maintenance operations are
performed by an internal system used to keep this address space active at all times. When used
with a DB2 MAILBOX, this function is offloaded to the standard DB2 save/restore system.

1.7 ACCESS SECURITY
Inter.Pel has its own security management system based on the data stored in the MAILBOX
and the generation parameters.
However, Inter.Pel can interface directly with user-specific security software or security
products installed on the site (RACF, TOP-SECRET, ACF2 and so on).
Inter.Pel may protect the sensitive data from any access, modification or deletion by
unauthorized users by using modifiable security routines called each time an access requires
checking.
These routines can be used to perform the checks or request that Inter.Pel perform them. The
routines can communicate with each other via an anchor point provided by Inter.Pel.
1.8 SERVICES
1.8.1 INTER.PEL SERVICES
Inter.Pel uses three files to monitor and control operations.
- The LOG file contains a trace of all events relating to transfer monitor activities and
to the transfers performed. This file is read via the request server monitor (option
4.5).
- The STAT or statistics file contains a trace of all elements relating to each transfer.
Utilities supplied with the product allow statistics to be printed by transfer and by
destination.
- The CPTR or action report file contains a trace of all elements relating to each
transfer. This file can be accessed via the request server monitor using selection
criteria.

1.8.2 USER SERVICES (EXITS)
So that each Inter.Pel operating site can be customized in-situ, a number of user exits are
available.
General exits
- Operator connection......................................................................................... EXLOG001

- Writing to the statistics file ............................................................................ EXFAC001
- Writing to the LOG file .................................................................................. USER
Security exits
- Controlling Inter.Pel users

Controlling access to the transfer monitor
- User LOGON exit ................................................................. EXLOG002
- User LOGOFF exit................................................................ EXLOGF02
Controlling access to files
- File access exit ...................................................................... EXSEC001
- MAILBOX access exit ......................................................... EXMLB001
Controlling command or transaction execution
- Transaction exit..................................................................... EXSEC004
- Controlling transfers
Controlling the transfer request parameter settings
- Transfer request exit.............................................................. EXSEC003
- BATCH request deposit exit ................................................. EXSEC005
Controlling file allocations in receive mode
- Receive check exit................................................................. EXSEC002
Controlling file availability
- Utility submit exit ................................................................. EXRAC001
Heterogeneous file transfer exits

- VTAM send/receive USER
- Start of transmission..............................................................................EXEMI0.S
- End of transmission ...............................................................................EXEMI00.
- End of broadcast list transmission ........................................................EXEMILDF
- File allocation in receive mode..............................................................EXVOLPL1
- File read/write........................................................................................USER
- End of reception ....................................................................................EXRCV00.
- Compression/compacting ......................................................................USER
- Incoming X.25 call packet management ...............................................EXX25IN
- Outgoing X.25 call packet management................................................EXX25OUT
- Incoming TCP/IP call management.......................................................EXIPIN
- Outgoing TCP/IP call management.......................................................EXIPOUT
- Exits specific to the PeSIT, ETEBAC5, ETEBAC3, FTP and ODETTE protocols

Homogeneous MVS-MVS transfer exits
- Allocation of utility files in transmit mode .......................................... EXVOLUTL

- Allocation of pelicanized files.............................................................. EXVOLPEL
- End of transmission .............................................................................. EXEMI001
- Allocation of pelicanized files in receive mode ................................... EXVOLDPL
- Allocation of depelicanized files in receive mode ............................... EXVOLRES
- Scratch of pelicanized files in receive mode ........................................ EXDPLEND
- End of reception .................................................................................. EXRCV001
- Allocation of the SYSIN file for the receive mode utility.................... EXVOLUTB
A primitive (PELSUBX or PELSJCLX) can be used in these exits to read, modify and submit
(and/or save) JCL skeletons.
1.9 GENERAL STRUCTURE
The general architecture of Inter.Pel is defined by:
- A multiple address space structure

- In each address space, a multiple task structure
- Tables
- Tasks
- Management modules
- Transfer modules
- Transaction modules used to monitor and control transfer monitor activities
1.9.1 MULTIPLE ADDRESS SPACES

To ensure independence between the main software functions, a kind of address space is
assigned to each function.
- One address space manages the MAILBOX and centralizes all read, update, add or
delete requests on this mailbox. It also manages the logging and maintenance
procedures for this file. It is structured so that it may remain active at all times. This
address space is called the MAILBOX SERVER.
- One address space receives all transfer requests and analyzes and records them. This
address space is also where the various tables required by Inter.Pel are stored. They are
installed from the standard definitions and then the appropriate definitions are
forwarded to the other address spaces. This address space is called the REQUEST
SERVER. This address-space also manage services files (STAT, CPTR, LOG).
- Up to ten address spaces perform the transfers. They arecalled TRANSFER
MONITOR or TRANSFER SERVER.
The various address spaces communicate via XCF to allow SYSPLEX operations.
Together, thoseaddress spaces are called a CLUSTER.

1.9.2 DIAGRAM OF THE VARIOUS ADDRESS SPACES
MLBX Trigger the

transfer
Tables Tables
MAILBOX Request Transfer
server Transfers
server managers
MLBX
Query Submit the request Submit the request

Update
BATCH CICS
When a site is specifically assigned to a transfer manager through the environment table, all
outgoing transfers towards this site will be processed by this manager. When several managers
are associated with a site, a load management function is performed to select the manager that
will process every transfer.
1.9.3 MULTIPLE TASKS
To ensure complete independence between the various functions in each address space
(operator, transfer and link management), an OS task is assigned to each function.
A specific OS task supervises the execution of the other tasks. It detects aborts and performs
RECOVERIES.
The tasks are synchronized using the MVS POST and WAIT macros.
A communication system informs each task of the status of the resources available in
Inter.Pel.

1.9.4 DIAGRAM OF THE VARIOUS TRANSFER MONITOR TASKS
Inter.Pel
Inter.Pel COMMON Inter.Pel
NUCLEUS STORAGE TABLES
AREA
SERVICE TYPE2 MNGT TYPE1

TASKS TASKS TASKS TASKS
LOG SESSION DEPEL. LOG
STATS MANAGER TIMERS STATS
MODIFY OPERATOR MODIFY
... ... ...
RECEPTION TRANSMISSION
Transfer Receive NETWORK NETWORK

Selection Any Interface Interface
Tasks Tasks
Tasks Tasks
Transfer Protocol Protocol

Task Tasks Tasks

1.9.5 TABLES
Inter.Pel uses two main tables: the environment table and the routing table.
The environment table mainly contains the transfer monitor's general execution parameters,
the list of remote sites along with their specific characteristics (protocol used, associated
network resources, and so on) and the list of logical names (applications) referenced during
the transfers.
The routing table contains elements relating to file routing (in the transmit or receive modes)
as well as the path used to reach a remote site (adjacent site concept).
These tables are submitted to Inter.Pel in the form of a PARMLIB that is resolved on
initialization. Modifications may be accepted dynamically during the request server session.
1.10 DOCUMENTATION
Inter.Pel documentation comprises the following manuals:
- Installation and Implementation Guide

- System Programmer's Reference Manual
- Messages & Codes Manual
- User Guide
- Protocol Guide
- Security Guide

2. INSTALLATION
2.1 RESOURCES REQUIRED
- Operating system
MVS, Version 5 and above.
- Network access mode

VTAM, V1.R3 and above.
- Communications controller
37XX or compatible.
- Network software
NCP, V2 and above.
NPSI, R3 and above.
- Disk space
50 3390 cylinders.
- System resources
One authorized library.
- Heterogeneous connections
SNS/TCPaccess, Version 2 and above, if TCP/IP is used with the Interlink
product.
The IBM TCP/IP product, V2R2.1 and above, if it is used as the TCP/IP file
exchange communication system.
A TRANSPAC access accepting reverse charging (RC) if files are to be

exchanged with PCs running the PELIPC/PAD software.
This access is defined in the NPSI X25MCH macro-instruction:
* Either in the GATE mode, with the following parameters:
X25MCH ..., GATE = GENERAL, SUBADDRESS = YES, LLCLIST =

(...,LLC4,...),...
(See Appendix B).
Installation and Implementation Guide Installation 2-1

* Or in the PCNE mode, with the following parameters:
...,LLCLIST=(LLC0,...),...
(See Appendix A).
In this case, if files are to be exchanged with PCs running the PELIPC/PAD
software, the TRAN=NO parameter must also be set.
2.2 INSTALLATION PRINCIPLES
The Inter.Pel software can be delivered either on tape or on CD support. In both cases it is
installed using the following procedure.
1 - Restore the files from the installation tape.
2 - Customize the CNTL file (IPOUPDTC).

Customize the SAMPLIB file (IPOUPDTS).
3 - Create the:
- Environment table (ENVTAB).
- Routing table (RTGTAB).
- X.25 dial number table, if X25NPSI-GATE is used (X25TAB) .
- TCP/IP dial number table (IPTB), if used.
- Models table, if models are used.
- Broadcast list table, if broadcast lists are used.
- User message table, if required.
4 - Build the FLAGDYN module (FLAGDYN).
5 - Create the required files and aliases (CREFICH).
6 - Enter the VTAM definitions (VTAPPL, VTSW, NPSISRC).
7 - Prepare the JCLs that are to be submitted automatically.
8 - Start up the Inter.Pel address spaces.
9 - Perform the initialization transactions (if the Inter.Pel internal security mechanism is
used):
- Assign USERIDs/PASSWORDs (option 6.1).
- Assign remote access rights (option 6.2) for type 2 transfers
If necessary, customize the exits.

2.3 RESTORING THE FILES
The Inter.Pel software can be delivered either on tape or on CD support. The only step that
changes between these two supports is the file restoration method. All subsequent steps are
the same for both supports. When installing Inter.Pel from a tape, you restore the files directly
to the MVS machine. When installing Inter.Pel from a CD, you first download the files to a
local workstation (e.g. Windows), then you send them to MVS using FTP. Finally, you format
them on the MVS machine.
2.3.1 RESTORING THE FILES FROM TAPE
The Inter.Pel tape contains eight files created by the IEBCOPY utility.
These files contain:
1 - SOP$PEL.DIST.INST: JCL required to download the Inter.Pel libraries.

2 - SOP$PEL.DIST.CNTL: sample Inter.Pel installation and execution JCLs.
3 - SOP$PEL.DIST.DBRM: DBRMs required to implement the DB2 MAILBOX
option.
4 - SOP$PEL.DIST.MAC: macro-instructions required to build the exits and tables.
5 - SOP$PEL.DIST.OBJ: object modules required for the link-edits.
6 - SOP$PEL.DIST.LOAD: Inter.Pel load-modules (RECFM = U, BLKSIZE = 32760);
this library must be authorized.
7 - SOP$PEL.DIST.SAMPLIB: sample tables or programs.
8 - SOP$PEL.DIST.SCR: XFB.SCOPE message file.
9.- SOP$PEL.DIST.CERT: file containing sample X509 certificates to be used with
SSL.
10 - SOP$PEL.DIST.READ description of fixes and enhancements available on the
tape.
The eighth file has to be unloaded only if the XFB.SCOPE agent has to be installed.
The ninth file has to be unloaded only if the SSL option has to be installed.
The first file on the tape contains the JCL required to download the Inter.Pel libraries. It can
be obtained by running the following JOB.
//PEL JOB
//LOAD EXEC PGM=IEBCOPY
//SYSPRINT DD SYSOUT=*
//INSTALL DD DISP=(,KEEP),DSN=SOP$PEL.DIST.INST,
// LABEL=(1,SL),UNIT=TTTT,
// VOL=(,RETAIN,SER=SOPxxx)
//USER DD DISP=OLD,DSN=...
//SYSIN DD *
C I=((INSTALL,R)),O=USER
/*

2.3.2 RESTORING THE FILES FROM CD
2.3.2.1 Content of the distribution CD
The delivered CD contains the complete Inter.Pel documentation set as well as the following
distribution files:
interpel.bin : All the Inter.Pel libraries (compressed and EBCDIC coded).

jclinst.txt : JCL used to install the previous file on MVS (text file ASCII coded)
upload.bat : MS-DOS command executed on the PC to transfer files to MVS.
upload.ftp : FTP script used by the upload.bat command.
2.3.2.2 Installation of Inter.Pel from the CD
1. Copy files UPLOAD.BAT and UPLOAD.FTP on the hard disk.
2. Customize the UPLOAD.FTP file:
open xxx.xxx.xxx.xxx
USERTSO
PSWDTSO
quote site recfm=fb lrecl=80
quote site volume=vvvvvv
quote site cyl
quote site primary=120
quote site secondary=15
quote site directory=10
mkdir 'IIIIIIII.interpel.uplib'
ascii
put D:jclinst.txt 'IIIIIIII.interpel.uplib(jclinst)'
quote mode c
quote type e
put D:interpel.bin 'IIIIIIII.interpel.uplib(interpel)'
quit
- line 1 (open) :
replace "xxx.xxx.xxx.xxx" with the MVS IP address.
- line 2 :
replace "USERTSO" with the TSO user name.
- line 3 :
replace "PSWDTSO" with the TSO password.
- line 5 :
replace "vvvvvv" with the destination volume name or delete
the line to allow SMS to choose the volume.
- lines 12 and 15 : replace "D" with the letter associated with the CD reader.
- lines 10, 12 and 15 : replace "IIIIIIII" with the Inter.Pel files major name.

3. Transfer file to MVS.
Execute the UPLOAD command in the MS-DOS window (file UPLOAD.BAT) :
ftp -s:upload.ftp
Le FTP script upload.ftp customized in the previous step contains the FTP commands used to
transfer files to MVS.
When this command is completed, a new file, IIIIIIII.INTERPEL.UPLIB, is created on MVS.

This PDS contains two members:
- JCLINST JCL used to install libraries (must be customized).
- INTERPEL All the Inter.Pel libraries (compressed and EBCDIC coded).
4. Customize the JCLINST member in the IIIIIIII.INTERPEL.UPLIB library:
//PEL1 ...
//PEL2 ...
//*********************************************************************
//* RESTORE INTER.PEL LIBRARIES
//*
//* IIIIIIII.INTERPEL.UPLOAD - BINARY COPY OF CD INTER.PEL FILE
//* IT MUST BE : RECFM=FB,LREC=80,BLKSIZE=3120
//*
//* IIIIIIII - INTER.PEL DSN PREFIX
//* VVVVVV - VOLUME NAME
//* SSSSSSSS - STORAGE CLASS
//*
//*********************************************************************
//*
//RSTEP01 EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
RECEIVE INDATASET('IIIIIIII.INTERPEL.UPLIB(INTERPEL)')
VOLUME(VVVVVV) DATASET('IIIIIIII.INTERPEL.ADRDFILE')
/*
//*
//*********************************************************************
//*
//RSTEP02 EXEC PGM=ADRDSSU
//ADRDFILE DD DISP=OLD,DSN=IIIIIIII.INTERPEL.ADRDFILE
//SYSIN DD *
RESTORE DATASET (INCLUDE(**)) -
INDD (ADRDFILE) -
RENAMEUNC (IIIIIIII) -
STORCLAS (SSSSSSSSS) -
CATALOG -
TOLERATE (ENQFAILURE)
/*
//*

//*
//*********************************************************************
//*
//RSTEP03 EXEC PGM=IDCAMS
//*
//SYSIN DD *
DEL IIIIIIII.INTERPEL.ADRDFILE
/*
//
- Create the JOB card.

- Replace all occurrences of "IIIIIIII" with the Inter.Pel files major name.
- Replace "VVVVVV" with the volume name to use (when needed).
- Replace "SSSSSSSS" with the storage class (when needed).
- The volume name in the RECEIVE command can be omitted when SMS is used.
- The STORCLAS parameter can be omitted if the SMS policies forces it.
5. Submit the JOB from the JCLINST member customized in the previous step
This JOB creates the following Inter.Pel libraries:
1. SOP$PEL.DIST.CNTL: sample Inter.Pel installation and execution JCLs.

2. SOP$PEL.DIST.DBRM: DBRMs required to implement the DB2 MAILBOX option.
3. SOP$PEL.DIST.MAC: macro-instructions required to build the exits and tables.
4. SOP$PEL.DIST.OBJ: object modules required for the link-edits.
5. SOP$PEL.DIST.LOAD: Inter.Pel load-modules (RECFM = U, BLKSIZE = 32760);
this library must be authorized.
6. SOP$PEL.DIST.SAMPLIB: sample tables or programs.
7. SOP$PEL.DIST.SCR: XFB.SCOPE message file.
8. SOP$PEL.DIST.CERT: file containing sample X509 certificates to be used with SSL.
9. SOP$PEL.DIST.READ description of fixes and enhancements available on the CD.
The seventh file (SCR) can be deleted if the XFB.Scope agent has not to be installed.
The eighth file (CERT) can be deleted if the SSL option has not to be installed.
This JCL creates a temporary file IIIIIIII.INTERPEL.ADRDFILE. This file is deleted at the
end of the JOB.
The IIIIIIII.INTERPEL.UPLIB library can also be deleted as it is no longer of any use to
Inter.Pel.

2.4 CUSTOMIZING THE CNTL AND SAMPLIB FILES
Two members in the CNTL library are used to modify the various examples. They are:
- IPOUPDTC for the CNTL library.

- IPOUPDTS for the SAMPLIB library.
They call the IPOUPDTE utility to replace some of the keywords with actual site values.
Note: to ensure that the IPOUPDTS member is not changed before it can be used, it is
recommended that this member be run before the IPOUPDTC member.
2.5 CREATING THE TABLES
The next stage involves creating the Inter.Pel definition tables. Two tables are mandatory:
- Environment table.
- Routing table.
and some tables are optional:
- X.25 dial number table.

- TCP/IP dial number table.
- Broadcast list table.
- Models table.
- User message table.
See the chapter entitled PARAMETER SETTING for instructions on how to create these
tables.
2.6 CREATING THE UNIT TABLE
Inter.Pel can allocate files to volume or unit names. The volumes are defined in the
environment table (PELPARMS VOL parameter) and the unit names are defined in a unit
table (FLAGDYN).
This table is used to modify the dynamic allocation flags.
See the chapter entitled PARAMETER SETTING for details of how to create this table.
See the chapter on exit customization in the System Programmer's Reference Manual for
further information on how to use this table.

2.7 CREATING THE FILES AND ALIASES
2.7.1 LIST OF FILES TO BE CREATED
FILE DSORG RECFM LRECL BLKSZ NAME
MAILBOX VSAM KSDS 400/4000 4080 IIIIIIII.INTERPEL.MAILBOX

PLOG VSAM RRDS 133 133 IIIIIIII.INTERPEL.PLOG
SLOG VSAM RRDS 133 133 IIIIIIII.INTERPEL.SLOG
AUDIT(P) PS VB 4020 4024 IIIIIIII.INTERPEL.AUDITB
AUDIT(S) PS VB 4020 4024 IIIIIIII.INTERPEL.AUDITP
PELFACT PS VB 500 504 IIIIIIII.INTERPEL.FACT
PELFACTB PS VB 500 504 IIIIIIII.INTERPEL.FACTB
PELFACTC PS VB 500 504 IIIIIIII.INTERPEL.FACTCUM
LOGTRANS PS F 1000 1000 IIIIIIII.INTERPEL.LOGTRANS
LOGTRANB PS F 1000 1000 IIIIIIII.INTERPEL.LOGTRANB
ARCHTRAN PS FB 1000 1000 IIIIIIII.INTERPEL.ARCHTRAN
MAILBOX Mailbox file.

PLOG Transfer monitor primary log.
SLOG Transfer monitor secondary log.
AUDIT Primary (P), secondary (S) and Inter.Pel (P) audit files for the MAILBOX
server (optional if DB2 is used).
LOGTRANS Transfer monitor primary action report output file.
LOGTRANB Transfer monitor secondary action report output file (optional).
ARCHTRAN Action report archive file (optional).
PELFACT Primary statistics file.
PELFACTB Secondary statistics file (optional).
PELFACTC Statistics archive file (optional).
PRINT1D Completed transfer action report file (type 1 transfers).
An allocation JCL can be found in the CREFICH member of the CNTL library.
2.7.2 LIST OF ALIASES TO BE CREATED
Create the alias defined in the environment table (GENDEB macro-instruction INDXR
parameter and PELPARMS file TEMPXR parameter).
2.7.3 MAILBOX FILE
The MAILBOX file is used only in the MAILBOX server. The MAILBOX DSN is provided
in the CNTRL control file (PELPARMS file FICNTRL parameter) associated with the
MAILBOX server.
There are two types of data in the MAILBOX.

Transfer data
This data relates to transfer requests, such as:
- File name.
- Transfer source site.
- File destination site.
- Transfer status.
This data can be accessed via the transaction monitor or the programmable interfaces supplied
with the product.
Control data
This data is of two types:
- Inter.Pel operator management data.

- Transfer monitor management data.
Some of this data can be accessed by authorized users via the transaction monitor.
Inter.Pel has three MAILBOX files: MAILBOX1, MAILBOX2 and MAILBOX3, which are
used exclusively by the MAILBOX server address space. The first two files are used in flip-
flop mode and are swapped when the Audit file full event occurs. The third file is a backup
copy. All mailbox accesses transit via the MAILBOX server job. For performance reasons, the
entire MAILBOX is loaded into memory when the server is started up.
The MAILBOX2 and MAILBOX3 files are created and initialized when the MAILBOX
server is first started up. A task triggered by the Audit file full event reorganizes the
MAILBOX file and calls the IDCAMS program to back it up in the MAILBOX3 file.
2.7.4 LOG FILES
The LOG files are used in the request server address space.
All events generated in the three address spaces (request server, MAILBOX server and
transfer monitor) are recorded in two files used in flip-flop mode.
These two files, PLOG and SLOG, are formatted and then used in UPDATE mode.
INITIALIZATION:
The last parameter in the Inter.Pel EXEC PARM field specifies the LOG FILE operation
mode.
- COLD: Format the LOG files. This parameter can be omitted when starting up with
empty log files. It is only mandatory to format existing files. However, for
performance reasons, you are advised to delete and to redefine before start-up.
This parameter should then never be used.
- WARM: Append after the last record.
FILE FULL:
When one of the files is full, Inter.Pel continues LOGGING in the other file and the JCL in
the member specified by the PELPARMS file MBRLOG parameter in the environment table
is submitted automatically. The name of the file that is full is passed as a parameter (a sample
JCL can be found in the PRTLOG member of the CNTL library).

Caution: the three address spaces write to the same LOG file (controlled in the address space
of the request server). If the LOG is queried via the request server operator interface (option
4.5) without applying a filter based on selection criteria, ALL entries in the LOG file
generated by the THREE address spaces are displayed. Each LOG entry written to the file
ends with the send address space identifier (eight characters corresponding to the ID
parameter in the PELPARMS file). The activities in a specific address space can be queried by
entering selection criteria. Origin address-space can also be recognized by the color of the line
on the display screen : yellow for the MAILBOX server, green for the request server and blue
for the transfer monitor.
2.7.5 AUDIT FILES
When the MAILBOX is a KSDS VSAM file, Inter.Pel uses two AUDIT files to rebuild it,
should it become corrupted.
These files are used exclusively by the MAILBOX server address space in flip-flop mode.
When the current AUDIT file is full (S/X37), the other file takes its place. This event triggers
a MAILBOX reorganization and backup process that can be run without shutting down the
MAILBOX server.
When the MAILBOX is a DB2 table, an AUDIT file may also be defined. This file will only
be used between execution of the FREEMLB and ATTMLB commands to store updates on
the mailbox while the table is being reorganized. These modifications will be applied to the
MAILBOX as soon as the ATTMLB command is entered.
2.7.6 ACTION REPORT FILES
The action report files are used in the request server address space.
The action report file contains information about each transfer performed. Two files,
LOGTRANS and LOGTRANB, can be used in flip-flop mode, or the same file can be used on
a permanent basis.
When the request server address space is started up, the availability of these files is checked:
- If neither file is present, the action report file function is disabled.
- If only one of the files is present, that file is used (DISP=MOD).
- If both files are present, the file that was used during the last Inter.Pel session is
reopened (DISP=MOD).
When one of the files is full:
- If only one file is being used, this file is reopened after a possible WTOR (see the
WAITCPT parameter in the PELPARMS file), and the data it contained is lost.
- If both files are available, Inter.Pel reinitializes the second file and continues to write
action reports to it, the JCL in the FIPROC MBRCPT member being automatically
submitted (see the MBRCPT and FIPROC parameters definition of the PELPARMS
file); the name of the file that is full is passed as a parameter (a sample JCL can be
found in the PRTCPT member of the CNTL library).

2.7.7 STATISTICS FILES
The statistics files are used in the request server address space.
The statistics file receives data relating to Inter.Pel activities. Two files, PELFACT and
PELFACTB, can be used in flip-flop mode, or the same file can be used on a permanent basis.
When the request server address space is started up, the availability of these files is checked.
- If neither file is present, the statistics function is disabled.
- If only one of the files is present, that file is used (DISP=MOD).
- If both files are present, the file that was used during the last Inter.Pel session is
reopened (DISP=MOD).
When one of the files is full:
- If only one file is being used, this file is reopened after a possible WTOR (see the
WAITFAC parameter in the PELPARMS file), and the data it contained is lost.
- If both files are available, Inter.Pel reinitializes the second file and continues to write
statistics to it, the JCL in the FIPROC MBRFAC member being automatically
submitted (see the MBRFAC and FIPROC parameters definition of the PELPARMS
file); the name of the file that is full is passed as a parameter.
(A sample customizable JCL can be found in the PRTFAC member of the CNTL
library).
2.7.8 CONTROL FILE
2.7.8.1 CONTROL FILE FOR A VSAM MAILBOX.
The MAILBOX server collects data relating to the MAILBOX and AUDIT files in a control
file, which is updated each time MAILBOX and AUDIT files are swapped. The name of this
file is set in the PELPARMS file FICNTRL parameter for the MAILBOX server. This file is
initialized by the PELMLGEN program. The JCL executing this program can be found in both
the CREFICH and CTRLGEN members of the CNTL library.
//PEL1 JOB
//PEL2 JOB
//*
//******************************************************************
//* INIT CONTROL FILE *
//* ================= *
//******************************************************************
//CTRLGEN EXEC PGM=PELMLGEN
//*********************************************************************
//STEPLIB DD DISP=SHR,DSN=IIIIIIII.INTERPEL.LOAD
//PELCTRFL DD DSN=IIIIIIII.INTERPEL.CTRL,VOL=SER=VVVVVV,
// DISP=(,CATLG),SPACE=(TRK,1),UNIT=UUUU,
// DCB=(LRECL=304,RECFM=FB,BLKSIZE=304)
//*********************************************************************

//SYSIN DD *
IIIIIIII.INTERPEL.MAILBOX1 MAILBOX1 FILE NAME
V11111 MAILBOX1 VOLSER
IIIIIIII.INTERPEL.PAUDIT PAUDIT FILE NAME
IIIIIIII.INTERPEL.SAUDIT SAUDIT FILE NAME
SIZE=(TRK,75,5) MAILBOX SIZE
//SYSUDUMP DD SYSOUT=*
//*********************************************************************
//ZZZZZZZZ EXEC PGM=IEFBR14
The following parameters are passed to the program via the SYSIN file:
- MAILBOX1 file name.

- MAILBOX1 volume (this volume name may be omitted when SMS is used).
- Name of the first AUDIT file.
- Name of the second AUDIT file.
- [SIZE=({CYL|TRK|REC},prim,sec)] (size used to create the MAILBOX during
automatic reorganization):
{CYL|TRK|REC} - space unit (cylinder, track, number of records).
prim - primary quantity (in above unit).
sec - secondary quantity (in above unit).
If this parameter is omitted, the mailbox will be created in a record unit, using the
high water mark of number of records in the active mailbox.
You are strongly advised to locate the MAILBOX files on different volumes.
The control file can be rebuilt by the PELREGE4 program. The sample JCL used to restore
the control file can be found in the CTRLREC member of the CNTL library.
2.7.8.2 CONTROL FILE FOR A DB2 MAILBOX.
When the MAILBOX server uses the DB2 access method, the CONTROL file is optional. It
can be used to release the MAILBOX table temporarily without stopping the monitor
(FREEMLB and ATTMLB commands). IF these commands are used, an AUDIT file has to be
created to store updates on the mailbox while the table is released and the CONTROL file
must be initialized using the PELMLGEN utility to define this AUDIT file. The JCL
executing this program can be found in the CTRLGEND member of the CNTL library:
//PEL1 JOB
//PEL2 JOB
//*
//******************************************************************
//* INIT CONTROL FILE FOR DB2 MAILBOX *
//* CREATE AUDIT FILE FOR DB2 MAILBOX *
//* ================================= *
//******************************************************************
//CTRLGEN EXEC PGM=PELMLGEN

//*********************************************************************
//PELPARMS DD DISP=SHR,DSN=IIIIIIII.INTERPEL.PARMLIB(ZPARMSRQ)
//PELCTRFL DD DSN=IIIIIIII.INTERPEL.CTRL,VOL=SER=VVVVVV,
//AUDLOGP DD DSN=IIIIIIII.INTERPEL.PAUDIT,VOL=SER=VVVVVV,
//********************************************************************
//SYSIN DD *
DB2 TELL : WE ARE USING DB2 MAILBOX
IIIIIIII.INTERPEL.AUDITP PAUDIT FILE NAME
//********************************************************************
//ZZZZZZZZ EXEC PGM=IEFBR14
The following parameters are passed to the program via the SYSIN file:
- DB2 to notify the use of a DB2 MAILBOX.

- Name of the AUDIT file. This name must be the same as the dsname referenced in
the AUDLOGP DD statement.
2.8 COMMUNICATION SVC
A communication SVC has been created to allow transfer requests to be submitted from batch
applications using concatenated unauthorized load-module libraries. This SVC uses the ESR
(Extended SVC Routines) mechanism. Use of the communication SVC is transparent for
these applications.
To prevent unauthorized access to this SVC, it is protected by an internal Inter.Pel algorithm
when it is called.
Note: The communication SVC was not modified for Inter.Pel version 7.3. The SVC installed
for version 7.1 or version 7.2 is still valid and does not have to be reinstalled during
migration to version 7.3.
2.8.1 INSTALLING THE COMMUNICATION SVC
Check that SVC 200 is not already being used on the system.
If it is, find a free number between 201 and 255 and rename the IGX00200 module as
IGX00nnn (where nnn is the SVC number chosen). In this case, you must set the
COMSVC=nnn parameter in the PELPARMS file to be used by the batch applications.
The IGX00nnn module (where nnn is the communication SVC number selected) must be link-
edit in the LPALIB using the LNKSVC JCL from the CNTL library. Follows instruction in
the header of this sample to customize it.
Remark : IGX00nnn program is invoked via the SVC 109 (which receive the IGX00nnn
name as a parameter). If an error occurs during installation of this module, this will cause an
abort S16D with R15=8 and R2=number of the used SVC.

Sample procedure used to link-edit IGX00nnn into LPALIB :
000001 //JOBNAME JOB (1),'SVC CREATE ',

000002 // CLASS=E,MSGCLASS=E,NOTIFY=&SYSUID,COND=(0,NE)
000003 //*
000004
//*********************************************************************
000005 //*
000006 //* SVC DE COMMUNICATION
000007 //*
000008 //* MODIFY USING "CHANGE ALL"
000009 //* SVC NUMBER : NNN WITH THE NUMBER OF THE COMSVC
000010 //* PARAMETER IN PELPARMS
000011 //* LIBRARY PEL730: PELSYS.PELICAN.OBJ730
000012 //* LIBRARY LPA : SYS1.USERLPA
000013 //*
000014
//*********************************************************************
000015 //*
000016 //LKED EXEC PGM=IEWL,
000017// PARM='XREF,LET,LIST,XCAL,AC=1,RENT,REUS,AMODE=31,RMODE=ANY'
000018 //*
000019 //SYSPRINT DD SYSOUT=*
000020 //SYSUT1 DD DSN=&&SYSUT1,UNIT=SYSDA,SPACE=(1024,(50,20))
000021 //*
000022 //SYSLIB DD DISP=SHR,DSN=PELSYS.PELICAN.OBJ7300
000023 //SYSLMOD DD DISP=SHR,DSN=SYS1.USERLPA
000024 //*
000025 //SYSLIN DD *
000026 CHANGE PELIXSVC(IGX00NNN)
000027 INCLUDE SYSLIB(PELIXSVC)
000028 NAME IGX00NNN(R)
000029 //*
000030 //BR14 EXEC PGM=IEFBR14
000031 //
Please contact the system administrator if you have any problems installing the
communication SVC.
2.9 XCF DEFINITIONS
Inter.Pel uses six XCF groups to control communications between its different address spaces
(transfer monitor, request server and MAILBOX server). The XCF configuration, particularly
the COUPLE file generation parameter, must reflect this situation.
Note: Inter.Pel uses the USERID associated with its address space to establish XCF
communications XCF. Each address space (JOB or STC) must thus have an associated USER.

2.9.1 SAMPLE COUPLE FILE DEFINITION
//PEL1 JOB
//****************************************************************
******
//* SAMPLE JCL TO FORMAT THE PRIMARY AND/OR ALTERNATE COUPLE
DATA
//* SETS USED BY THE XCF COMPONENT OF MVS
//*
//* CHANGE-ACTIVITY =
//* $L0=COUPLXLK,HBB4410,880120,PDFR: CROSS-SYSTEM COUPLING
FACILITY
//* $P1=PE02890,HBB4410,891204,PDDS: CHANGING DSNS
//****************************************************************
******
//STEP1 EXEC PGM=IXCL1DSU
//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR
//SYSIN DD *
DEFINEDS DSN(SYS1.XCF.CDS01) VOLSER(VVVVVV) SYSPLEX(PLEX114)
MAXMEMBER(100) MAXGROUP(20) CATALOG
DEFINEDS DSN(SYS1.XCF.CDS02) VOLSER(VVVVVV) SYSPLEX(PLEX114)
MAXMEMBER(100) MAXGROUP(20) CATALOG
//
2.10 VTAM DEFINITIONS
2.10.1 OBJECTS TO BE DEFINED
The applications and CDRSCs, the names of which are specified in the environment table,
must be defined in the VTAMLST.
1 - Operator applications with the parameter:

AUTH=(ACQ,SPO) (see VTAPPL in the SAMPLIB library).
2 - Transfer applications with the parameters:

AUTH=ACQ,PARSESS=YES (see VTAPPL in the SAMPLIB library).
Do not set the VPACING option; Inter.Pel uses SNA responses to control the data
flow.
If LU 6.2 is used, the ACB definition is modified (see below).
3 - CDRSCs for the SNA CROSS-DOMAIN links.
4 - Major switched node for the X.25 links (see VTSW in the SAMPLIB library).

2.10.2 SAMPLE VTAM DEFINITIONS
NTSS site definitions:
Major node applications:
VBUILD TYPE=APPL
*
APPNTSS APPL AUTH=ACQ,PARSESS=YES MVS-MVS HOMEGENEOUS ACB
APPOPER APPL AUTH=(ACQ,SPO) Monitor OPERATORS ACB
APPOPERQ APPL AUTH=(ACQ,SPO) SRQ OPERATORS ACB
APPOPERM APPL AUTH=(ACQ,SPO) MAILBOX server OPERATORS ACB
ACBPCNE APPL AUTH=ACQ,PARSESS=YES PEL - X25 PCNE
ACBPCNES APPL AUTH=ACQ,PARSESS=YES PEL SERVER - X25 PCNE
ACBPCNED APPL AUTH=ACQ,PARSESS=YES PEL REQUESTER - X25 PCNE
ACBPELHV APPL AUTH=ACQ,PARSESS=YES PEL-HV - SNA
ACBPCSNA APPL AUTH=ACQ,PARSESS=YES PEL SERVER - PELIPC SNA
ACBPCPAD APPL AUTH=ACQ,PARSESS=YES PEL SERVER - PELIPC PAD
ACBTBACE APPL AUTH=ACQ,PARSESS=YES ETEBAC3 REQUESTER - X25 PCNE
ACBSIT APPL AUTH=ACQ,PARSESS=YES PESIT HORS-SIT - SNA
ACBMCH01 APPL AUTH=ACQ,PARSESS=YES GATE ACCESS LUMCH01
ACBMCH02 APPL AUTH=ACQ,PARSESS=YES GATE ACCESS LUMCH02
ACBLU62 APPL AUTH=(ACQ,PASS,SPO),PARSESS=YES LU 6.2
*
Major switched node:
PELISW VBUILD TYPE=SWNET,MAXGRP=1,MAXNO=10

*
*---- PU/LU USED BY Inter.Pel FOR OUTGOING CALL TO SITE001
SWPU01 PU ADDR=C1,IDBLK=003,IDNUM=AAAAA,PUTYPE=1,MAXPATH=1,
ISTATUS=ACTIVE,MAXDATA=2540,DISCNT=YES
PATH DIALNO=.........0....*AAAAA,GRPNM=.....,GID=1,PID=1
SWLU01 LU LOCADDR=0,PACING=(1,1),SSCPFM=FSS
*---- PU/LU USED BY Inter.Pel FOR INCOMING CALL FROM SITE001
SWPU02 PU ADDR=C1,IDBLK=003,IDNUM=BBBBB,PUTYPE=1,MAXPATH=1,
SWPU03 PU ADDR=C1,IDBLK=003,IDNUM=CCCCC,PUTYPE=1,MAXPATH=1,
PATH DIALNO=.........0....*CCCCC,GRPNM=.....,GID=1,PID=1
SWPU04 PU ADDR=C1,IDBLK=003,IDNUM=DDDDD,PUTYPE=1,MAXPATH=1,
SWPU05 PU ADDR=C1,IDBLK=003,IDNUM=EEEEE,PUTYPE=1,MAXPATH=1,
SWPU06 PU ADDR=C1,IDBLK=003,IDNUM=FFFFF,PUTYPE=1,MAXPATH=1,
PATH DIALNO=.........0....*FFFFF,GRPNM=.....,GID=1,PID=1
SWPU07 PU ADDR=C1,IDBLK=003,IDNUM=GGGGG,PUTYPE=1,MAXPATH=1,
PATH DIALNO=.........0....*GGGGG,GRPNM=.....,GID=1,PID=1
SWPU08 PU ADDR=C1,IDBLK=003,IDNUM=HHHHH,PUTYPE=1,MAXPATH=1,
PATH DIALNO=.........0....*HHHHH,GRPNM=.....,GID=1,PID=1

2.11 AUTOMATIC JCL EXECUTION
Inter.Pel can resolve and submit a JCL skeleton member automatically. This facility is
implemented in all Inter.Pel end of transmission and end of reception routines, which can
generally be used without any modification. The sources are, however, provided, should
customization be required (see the System Programmer's Reference Manual).
This mechanism uses the GENFILE macro-instruction SUBJCL parameter (see the
description of the GENFILE macro-instruction).
It is only activated if the value of the GROUP parameter in the GENFILE macro-instruction
set for the transmitted or received application is the same as the value of the GROUP
parameter in the GENSITE or GENLU macro-instruction (heterogeneous or homogeneous
MVS-MVS links respectively) defining the remote site.
It enables processing to be sequenced automatically without developing specific exits.
The following exits already support this facility:
(The sources for these exits can be found in the SAMPLIB library.)
EXEMI001, called when a file has been transmitted via the homogeneous MVS-MVS
protocol
(EXEMI01 member).
EXEMI002, called when a file has been transmitted via the PEL, ETEBAC or ODETTE
protocols
(EXEMI02 member).
EXEMI003, called when a file has been transmitted via the PeSIT SIT protocol
(EXEMI03 member).
EXEMI004, called when a file has been transmitted via the PeSIT Hors SIT or FTP
protocols
(EXEMI04 member).
EXEMI005, called when a file has been transmitted via the ETEBAC5 protocol
(EXEMI05 member).
EXRCV001, called when a file has been received via the homogeneous MVS-MVS
protocol
(EXRCV01 member).
EXRCV002, called when a file has been received via the PEL, ETEBAC or ODETTE
protocols
(EXRCV02 member).
EXRCV003, called when a file has been received via the PeSIT SIT protocol
(EXRCV03 member).
EXRCV004, called when a file has been received via the PeSIT Hors SIT or FTP protocols
(EXRCV04 member).

EXRCV005, called when a file has been received via the ETEBAC5 protocol
(EXRCV05 member).
You can modify or make additions to the exits, if necessary.
Use of the exits
When the exits are called, they check that the SUBJCL parameter is set in the GENFILE
macro-instruction for the group specified by the GENSITE or GENLU macro-instructions
(heterogeneous or homogeneous MVS-MVS links respectively) defining the destination
site in transmission mode, or the source site in reception mode.
For the PeSIT Hors SIT and ETEBAC5 protocols, the name of the application to be located
corresponds to the first eight characters of the PeSIT file name (PI 12).
The name of the member to be resolved and submitted automatically consists of:
PPPPPP = Prefix
Value of the GENFILE macro-instruction SUBJCL parameter.
X = Transfer direction
E=Transmission / R=Reception
I = Skeleton index
Transfer status in the MAILBOX.
The exit searches for the PPPPPPXI member in the library specified by the PELPARMS
file FICJCL parameter. If this member exists, the exit resolves and submits it. If it does not
exist, the exit searches for the PPPPPPX member. If the PPPPPPX member exists, the
exit resolves and submits it. Otherwise, no submission is made.
The exits set key transfer information using variables that are resolved automatically,
depending on the transfer protocol used.
The &SUBSTR function allows the use of only part of a variable. This function is coded the
following way:
&SUBSTR(p:l,&variable)
with p = start position in the &variable variable

and l = length to use.
Example:
&SUBSTR(2 :10,&MSG1) with &MSG1 = ABCDEFGHIJKLMNOPQRST is translated in
BCDEFGHIJK
&variable can be a concatenation of several variables, constants or other &SUBSTR

functions. In any case, the first element cannot be a constant.
These variables are listed on the following pages.

Homogeneous MVS-MVS links (type 2):
&APPL Application name

LENGTH = 8 characters
&BYTES Total number of bytes in the file

LENGTH = 12 digits
&CLEMLBX MAILBOX key for the file

&DATE Transfer date

LENGTH = 5 digits
FORMAT = YYDDD
&DCB Transfer information

FORMAT = AAAAAA BB CC
AAAAAA = Abend code or s00000
BB = Inter.Pel function
CC = Inter.Pel function return code
&DESTF Source site (S) / destination site (R)

&MSG2 Accompanying message

&NBREC Total number of records in the file

LENGTH = 9 digits
&NOTIFY NOTIFY TSO

&PELDSN Dsname of the source file

&PELDSNR Dsname of the destination file, if specified

&PELDSN1 Dsname of the pelicanized file

&PELIJOB JOBNAME of the resolved JCL

&PSRANG Transfer priority

LENGTH = 3 digits
&PSVMAX Number of bytes transferred after compression

LENGTH = 12 digits
&RANG Rank assigned to the transfer


&REQ Request deposit date
FORMAT = YYDDD HHMMSS
YYDDD = Transfer request deposit date
HHMMSS = Transfer request deposit time
&RETRY Number of retries

LENGTH = 2 digits
&SCRATCH Scratch flag

LENGTH = 1 character
&SITE Destination site (S) / source site (R)

&STATUS Transfer status in the MAILBOX

&TRACKER XFB.SCOPE or Sentinel tracking activation.

Y = Transfer registered to Sentinel
N = Transfer not registered to Sentinel
S = Transfer partially registered to Sentinel
&TRKCID Cycle ID used to register this transfer to Sentinel.

&TRKOBJ Object used to register this transfer to Sentinel.

&USRDATA User information

&UTILITY Utility if specified

&XREQE Transfer end date and time

YYDDD = Transfer end date
HHMMSS = Transfer end time
&XREQS Transfer start date and time

YYDDD = Transfer start date
HHMMSS = Transfer start time

PEL, ODETTE or ETEBAC protocol:
&APPL Application name


LENGTH = 12 digits
&COMP Compression type

&DATE Transfer date

LENGTH = 5 digits
FORMAT = YYDDD
&DCB File format

FORMAT = RRR LLLLL BBBBB
RRR = File RECFM
LLLLL = File LRECL
BBBBB = File BLKSIZE

&MSG Accompanying message 1

&MSG2 Accompanying message 2


LENGTH = 9 digits
&NOTIFY NOTIFY TSO

&PELDSN Sent file (S) / received file (R)


&PSVMAX Amount, if specified

LENGTH = 12 digits



LENGTH = 2 digits






&USRDATA Number of bytes transferred after compression

LENGTH = 12 digits
&UTILITY Transfer priority

LENGTH = 1 digit



PeSIT SIT protocol:
&APPL SIT application name


LENGTH = 12 digits

&DATE Transfer date

LENGTH = 5 digits
FORMAT = YYDDD
&DCB File format

RRR = File RECFM
LLLLL = File LRECL

&MSG Accompanying message


LENGTH = 9 digits
&NOTIFY NOTIFY TSO



&PSDIAG PeSIT diagnostics

FORMAT = EEEEE RRRRR
EEEEEE = PeSIT diagnostic transmitted by Inter.Pel
RRRRRR = PeSIT diagnostic received by Inter.Pel
&PSNAME SIT file name

&PSSIGN SIT signature

FORMAT = T SS.........SS
T = SIT signature type
SS..SS = SIT signature

&PSVMAX SIT validity data
FORMAT = T YYDDD HHMM
T = Validity data type
YYDDD = Validity expiry date
HHMM = Validity expiry time



LENGTH = 2 digits







LENGTH = 1 digit



PeSIT Hors SIT protocol:
&APPL SIT application name


LENGTH = 12 digits

&DATE Transfer date

LENGTH = 5 digits
FORMAT = YYDDD
&DCB File format

RRR = File RECFM
LLLLL = File LRECL

&LABEL Label (PI 37) associated with this transfer

&MSG 1st accompanying message

&MSG2 2nd accompanying message


LENGTH = 9 digits
&NOTIFY NOTIFY TSO



&PSDIAG PeSIT diagnostics

EEEEEE = PeSIT diagnostic transmitted by Inter.Pel
RRRRRR = PeSIT diagnostic received by Inter.Pel

&PSNAME Hors SIT file name
&PSRANG Rank assigned to the transfer

LENGTH = 8 digits


LENGTH = 2 digits







LENGTH = 12 digits

LENGTH = 1 digit



ETEBAC5 protocol:
&APPL ETEBAC5 application name (PI 11)


LENGTH = 12 digits

&DATE Transfer date

LENGTH = 5 digits
FORMAT = YYDDD
&DCB File format

RRR = File RECFM
LLLLL = File LRECL

&MSG 1st accompanying message

&MSG2 2nd accompanying message


LENGTH = 9 digits
&NOTIFY NOTIFY TSO



&PSDIAG ETEBAC5 diagnostics

EEEEEE = ETEBAC5 diagnostic transmitted by Inter.Pel
RRRRRR = ETEBAC5 diagnostic received by Inter.Pel
&PSNAME ETEBAC5 file name


&PSRANG Rank assigned to the transfer
LENGTH = 8 digits


LENGTH = 2 digits







LENGTH = 12 digits

LENGTH = 1 digit



Several system variables are also available in the JCL :
Name Contents Length

&XCLUST Cluster name 7
&XDAY Current day 2
&XHH Current time 2
&XID Address space ID 8
&XMM Current minute 2
&XMONTH Current month 2
&XQQQ Current day in the year 3
&XSTATE Monitor state: 1
I = initializing
N = normal processing
T = terminating
&XTYP Type of address space (MON/SRQ/MLB) 3
&XYEAR Current year 4
Some parts of the skeleton may be conditionally excluded from the resulting JCL using )SEL
and )ENDSEL cards.
The )SEL sets an inclusion condition till the next balanced )ENDSEL
This card is coded in the following manner:
)SEL argument1 op argument2
with:
argument = constant, variable (&xxx), &SUBSTR function or concatenation
op = condition oprator
= : equal to
> : greater than
< : less than
>= : greater than or equal to
<= : less than or equal to
<> : different from
At least one space must separate arguments from the operator.
The test is always executed on the length of the first argument. This allows generic argument
comparison.
Up to 32 )SELs mayoverlap.
Examples of )SEL :
)SEL &DESTF = SITE1 : includes the following cards if the value of the
DESTF parameter is equal to SITE1,
)SEL AG = &DESTF : includes the following cards if the value of
DESTF parameter starts with AG,
)SEL &XHH&XMM > 1230 : includes the following cards if the value of the
concatenation of XHH and XMM is greater than
1230,

)SEL AG <> &SITE : includes the following cards if the value of
inclusion of the SITE parameter does not start
with AG,
)SEL &SUBSTR(2 :3,&MSG1) = DSN : includes the following cards if the MSG1
parameter contains DSN at position 2.
The )ENDSEL card has no argument.
At the end of JCL, Inter.Pel assumes as many )ENDSELs as needed to terminate all the active
)SELs.
2.12 INTER.PEL EXECUTION
2.12.1 RUNNING THE REQUEST SERVER
The run-time JCL consists of two phases:

- Starting up the request server.
- Listing and reinitializing the LOG files.
The run-time JCL can be found in the EXSRQSRV member of the CNTL library.
//PEL JOB
//*
//*-- PARAMETRES D'EXECUTION SRQ:
//*-- PARM='STAE,WARM'
//*
//STEP01 EXEC PGM=PL6SRQ,TIME=1440,REGION=3000K,
// PARM=(STAENO,COLD),
// DYNAMNBR=50
//*
//MAILBOX DD DUMMY
//AUDLOG DD DUMMY
//PELFACT DD DISP=MOD,DSN=IIIIIIII.INTERPEL.FACTA
//PELFACTB DD DISP=MOD,DSN=IIIIIIII.INTERPEL.FACTB
//PLOG DD DISP=SHR,DSN=IIIIIIII.INTERPEL.PLOG
//SLOG DD DISP=SHR,DSN=IIIIIIII.INTERPEL.SLOG
//PELPARMS DD DISP=SHR,DSN=IIIIIIII.INTERPEL.SAMPLIB(EXSRQSRV)
//LOGTRANS DD DISP=MOD,DSN=IIIIIIII.INTERPEL.LOGTRNA
//LOGTRANB DD DISP=MOD,DSN=IIIIIIII.INTERPEL.LOGTRNB
//ARCHTRAN DD DISP=SHR,DSN=IIIIIIII.INTERPEL.ARCHTRAN
//VERSION DD DUMMY
//PRINT1D DD SYSOUT=*,DCB=(RECFM=FA,BLKSIZE=121,LRECL=121)
//MEMLST DD SYSOUT=*
//VSMLIST DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SYSIN DD *
EXEC .... .... .... ....
//*
//******************************************************************
//*
//* IMPRESSION ET CLEAR DES FICHIERS LOG
//*
//******************************************************************
//*
//STEP02 EXEC PGM=PELVPRTC,PARM='PLOG,SLOG'
//*

//PLOG DD DISP=SHR,DSN=IIIIIIII.INTERPEL.LOG
//SLOG DD DISP=SHR,DSN=IIIIIIII.INTERPEL.LOG
//SYSIN DD DUMMY
During the request server start-up phase, the PARM parameter providing the following run-
time options is interpreted.
- STAE/NOSTAE: abend processed by the request server; this option prevents the request
server from terminating, should an error occur in the main task.
By default, an STAE is active for the main program.
- LOGGING:
- COLD : Format the LOG files.
- WARM : Append the LOG files.
The SYSIN file contains the Inter.Pel authorization keys in the following format:
BYTES 01-04 : EXEC - Inter.Pel execution authorization

: PSNA - Number of authorized SNA PELIPCs
: PPAD - Number of authorized PAD PELIPCs
BYTES 06-09 : 4 digits
- Seven keys of each type can be specified in SYSIN.
The request server protection key is the same as the one used for the associated transfer
monitor.
THESE KEYS ARE PROVIDED BY CUSTOMER SERVICES.
2.12.2 RUNNING THE MAILBOX SERVER

The run-time JCL consists of a single phase:
- Starting up the MAILBOX server.
The run-time JCL can be found in the EXMLBSRV member of the CNTL library.

//PEL JOB
//*
//*-- PARAMETRE D'EXECUTION du serveur MAILBOX:
//*-- PARM='STAE'
//*
//STEP01 EXEC PGM=PL6SERV,TIME=1440,REGION=3000K,
// PARM=(STAENO),
// DYNAMNBR=50
//*
//SYSIVER DD DISP=SHR,DSN=IIIIIIII.INTERPEL.CNTL($VRFMLBX)
//PELPARMS DD DISP=SHR,DSN=IIIIIIII.INTERPEL.SAMPLIB(EXMLBSRV)
//ARCHTRAN DD DUMMY
//SYSPVER DD DUMMY
//SYSIVER DD DUMMY
//VERSION DD DUMMY
//MLBSYSP DD SYSOUT=*
//MLBSYSP DD SYSOUT=*
//SYSIN DD *
EXEC .... .... .... ....
//*
During the MAILBOX server start-up phase, the PARM parameter providing the following
run-time option is interpreted.
- STAE/NOSTAE: abend processed by the MAILBOX server; this option prevents the
MAILBOX server from terminating, should an error occur in the main task.

The MAILBOX server protection key is the same as the one used for the associated
transfer monitor.
2.12.3 RUNNING THE TRANSFER MONITOR
The Inter.Pel run-time JCL consists of a single phase:
- Starting up Inter.Pel.

The Inter.Pel run-time JCL can be found in the EXTRNSRV member of the CNTL library.
//PEL JOB
//*
//*-- PARAMETRE D'EXECUTION Inter.Pel :
//*-- PARM='STAE'
//*
//STEP01 EXEC PGM=PL6MAIN,TIME=1440,REGION=3000K,
// PARM=(STAENO),
// DYNAMNBR=50
//*
//PELPARMS DD DISP=SHR,DSN=IIIIIIII.INTERPEL.SAMPLIB(EXTRNSRV)
//ARCHTRAN DD DUMMY
//VERSION DD DUMMY
//SYSIN DD *
EXEC .... .... .... ....
//*
During the Inter.Pel transfer monitor start-up phase, the PARM parameter providing the
following run-time option is interpreted.
- STAE/NOSTAE: abend processed by Inter.Pel; this option prevents Inter.Pel from

terminating, should an error occur in the main task.
When several transfer manager monitors are used, the JCL is the same for each one, except,
for the PELPARMS member which must be different.

2.12.4 STARTING UP THE ADDRESS SPACES
The three procedures are started up by the START command or by submitting the JCL.
The JOBs may be started up in any order, as they are automatically synchronized when they
are initialized.

2.13 INITIALIZATION TRANSACTIONS
These transactions define the:
1 - Inter.Pel operators (menu 6.1) on each address space.

2 - Authorizations (menu 6.2) on transfer monitor only.
Use of these first transactions
- WITHOUT AN EXTERNAL SECURITY MECHANISM.
If the external security call option is not set on the site, you must log on to Inter.Pel when the
installation procedure is complete using MASTER as your USERID and PELICAN as your
PASSWORD. This will allow you to define the users authorized to access Inter.Pel.
The MASTER/PELICAN user can subsequently be deleted in the EXLOG001 LOGON exit.
- WITH AN EXTERNAL SECURITY MECHANISM.
If the external security call option is set on the site, Inter.Pel authorizes all logons until the
EXLOG002 logon exit is run (see the System Programmer's Reference Manual).
See the description of these transactions in the User Guide.
These transactions must be executed for each address space.
2.14 MIGRATING FROM VERSION 7.1
The format of the MAILBOX file has been changed in Version 7.2:
- The record length is now variable, up to 4000 bytes.

- The ETEBAC5 record format has also been changed to support version 2 of this
protocol.
- Each key field containing a two byte year is now coded in binary rather than in
EBCDIC.
A special utility converts records from the old to the new format. A sample call to this utility
can be found in the CNTL library:
CNVVS712 member for a VSAM MAILBOX.

CNVDB712 member for a DB2 MAILBOX.
Sample procedures describing how to downgrade to a previous version from Version 7.3 are
also available in the same library:
CNVVS721 member for a VSAM MAILBOX.

CNVDB721 member for a DB2 MAILBOX.
The PELC7172 mailbox is used to migrate the mailbox from Version 7.1x to make it compatible with
Version 7.2 or 7.3.

Run-time JCL format:
//PEL1 JOB
//PEL2 JOB
//*********************************************************************
//* CONVERSION MAILBOX FORMAT
//* =========================
//* V7.1 / V7.2
//* ===========
//*
//* STEP01 : REPRO MAILBOX V7.1 INTO SEQUENTIAL FILE (IDCAMS)
//* STEP02 : MIGRATION MAILBOX (PELC7172)
//* STEP03 : SORT SEQUENTIAL FILE (SORT)
//* STEP04 : CREATION MAILBOX AND RELOAD (IDCAMS)
//*
//* CUSTOMIZATION :
//* ---------------
//* - IIIIIIII : INTERPEL LIBRARIES AND FILES MAJOR INDEX
//* - VVVVVV : INTERPEL FILES VOLSER FOR MAILBOX
//* - UUUU : VVVVVV UNIT TYPE
//*
//*--------------------------------------------------------------------
//* UNLOAD VSAM MAILBOX
//*--------------------------------------------------------------------
//*
//STEP01 EXEC PGM=IDCAMS
//MAILBOXO DD DISP=SHR,DSN=IIIIIIII.INTERPEL.MAILBOX.OLD
//FILESEQ DD DSN=&&PELI,UNIT=SYSDA,DISP=(,PASS),
// DCB=(RECFM=VB,BLKSIZE=27998,LRECL=2000),
// SPACE=(TRK,(75,5))
//SYSIN DD *
REPRO INFILE(MAILBOXO) OFILE(FILESEQ)
//*
//*-------------------------------------------------------------------
//* DATA MIGRATION
//*-------------------------------------------------------------------
//*
//STEP02 EXEC PGM=PELC7172
//SEQINP DD DISP=(SHR,DELETE),DSN=&&PELI
//SEQOUT DD DSN=&&PELO,UNIT=SYSDA,DISP=(,PASS),
// DCB=(RECFM=VB,BLKSIZE=27998,LRECL=4000),
// SPACE=(TRK,(75,5))
//*
//*--------------------------------------------------------------------
//* SORT MIGRATED DATA
//*--------------------------------------------------------------------
//*
//STEP03 EXEC PGM=SORT
//SYSOUT DD SYSOUT=*
//SORTIN DD DISP=SHR,DSN=&&PELO
//SORTOUT DD DISP=(SHR,PASS),DSN=&&PELO
//SORTWK01 DD UNIT=SYSDA,SPACE=(CYL,(4,1))

//SYSIN DD *
SORT FIELDS=(5,41,CH,A)
//*
//*--------------------------------------------------------------------
//* MAILBOX FILE CREATION (VSAM KSDS)
//*--------------------------------------------------------------------
//*
//MAILBOX DD UNIT=UUUU,VOL=SER=VVVVVV,DISP=SHR
//SEQOUT DD DISP=(SHR,DELETE),DSN=&&PELO
//SYSIN DD *
DEFINE CLUSTER (NAME(IIIIIIII.INTERPEL.MAILBOX) -
FILE(MAILBOX) -
VOL(VVVVVV) -
KEYS(41 0) -
RECSZ(2000 4000) -
TRK(75,5) -
FSPC(50,50) -
SHR(2 3) -
UNIQUE ) -
DATA (NAME(IIIIIIII.INTERPEL.MAILBOX.DATA) -
CISZ(4096)) -
INDEX (NAME(IIIIIIII.INTERPEL.MAILBOX.INDEX) -
CISZ(1024))
REPRO INFILE(SEQOUT) OUTDATASET(IIIIIIII.INTERPEL.MAILBOX)
//*
DD cards to be specified:
SEQIN : Mailbox file to upgrade.

SEQOUT : Output mailbox file. This file must be completely empty when the utility is
executed.
Program return codes:
0 : Correct execution.
4 : Correct execution but some records in the input file were already in a version 7.2
format.

3. PARAMETER SETTING
3.1 GENERAL PRINCIPLES
3.1.1 Inter.Pel TABLES
Inter.Pel uses seven tables, two of which are mandatory:
- Environment table
- Routing table
The third is used only with the NPSI GATE function:
- X.25 dial number table (X25TABLE)

The fourth is used only with TCP/IP:
- TCP/IP address table (IPTABLE)
The fifth can be used for transfer submission requests:
- Models table
The sixth can be used to define broadcast lists:
- Broadcast list table
The seventh can be used to customize message management:
- User message table
These tables are systematically passed to Inter.Pel as PDS members containing the source
definitions (PARMLIB). This solution allows the tables to be updated dynamically during an
Inter.Pel session. They are controlled and loaded into memory by the request server (at
startup). The definitions are then sent to the transfer monitor and the MAILBOX server when
they are started up to be loaded in these address spaces. In some specific cases, those tables
are also transmitted to batch programs.
Reminder: the server sites do not have to be defined in the environment and routing tables, as
Inter.Pel can create them dynamically from the associated call receive models.
Installation and Implementation Guide Parameter Setting 3-1

3.1.2 INSTALLING THE TABLES
3.1.2.1 DESCRIPTION
3.1.2.1.1 Definitions Loaded by the Request Server
The tables are created dynamically from the sources when the request server job is started up
or user jobs invoking Inter.Pel are executed. They can be updated during the request server
session and are then automatically loaded in the address space of the transfer monitor (if it is
running; otherwise, they are applied when it is next started up).
The request server uses two DD cards:
- PELPARMS, which provides the parameters required to install the dynamic tables; this
sequential file (or PDS member) is mandatory in the JCL
- PELDFNDS, which specifies a PDS or PDS concatenation containing the definitions to

be installed; if this file is not present in the JCL, it can be allocated dynamically from
data in PELPARMS
Column 1 of the PELPARMS file contains two sets of keyword parameters:
1 Keywords identifying the tables used (ENV, RTG, X.25, and so on)
2 Keywords specific to the configuration of the current job
Note: only the request server job processes the keywords for the tables to be used. The other
jobs (MAILBOX server and transfer monitors) use only configuration-type keywords.
The keywords used to load the tables are:
DYNDFN={YES}
YES - The request server uses the tables installed dynamically.
Note: at present, this is the only possible value.
DFNDS=aaaaaaaa.bbbbbbbb.cccccccc.....
DSNAME of a file (PDS) allocated dynamically to create PELDFNDS.
These files are concatenated in the order in which they are specified. They
contain the definitions to be installed.
These parameters are not used if the PELDFNDS card is declared in the
JCL.
Up to 16 DFNDS can be given.
ENVLIST=xx
Suffix for the list of members in the environment table.
The PELDFNDS PELENVxx member then contains the list of members to
be installed to create the environment table.
RTGLIST=xx
Suffix for the list of members in the routing table.
The PELDFNDS PELRTGxx member then contains the list of members to
be installed to create the routing table.

LDFLIST={xx|NO}
xx - Suffix for the list of members in the broadcast list table.
The PELDFNDS PELLDFxx member then contains the list of
members to be installed to create the broadcast list table.
NO - The broadcast list table is not installed when Inter.Pel is started up.
MODLIST={xx|NO}
xx - Suffix for the list of members in the models table.
The PELDFNDS PELMODxx member then contains the list of
members to be installed to create the models table.
NO - The models table is not installed when Inter.Pel is started up.
MSGLIST={xx|NO}
xx - Suffix for the list of members in the user message table.
The PELDFNDS PELMSGxx member then contains the list of
members to be installed to create the user message table.
NO - The user message table is not installed when Inter.Pel is started up.
TCPLIST={xx|NO}
xx - Suffix for the list of members in the TCP/IP address table.
The PELDFNDS PELTCPxx member then contains the list of
members to be installed to create the TCP/IP address table.
NO - Inter.Pel does not use the TCP/IP address table.
X25LIST={xx|NO}
xx - Suffix for the list of members in the X.25 dial number table.
The PELDFNDS PELX25xx member then contains the list of
members to be installed to create the X.25 dial number table.
NO - Inter.Pel does not use the X.25 dial number table.
The configuration keywords are as follows.
ACB3270=
Name of the operator ACB associated with the request server.
Default: none.
ARM={YES|NO}
YES - Register to ARM when the address space starts up.
NO - Do not register to ARM when the address space starts up.
When Inter.Pel registers to ARM, the element name used in the IXCARM
macro is built as follows:
X constant,
the cluster name(CLUSTER parameter), up to 7 characters,
the address space name (ID parameter), up to 8 characters.
The blank characters contained in the element name are automatically
replaced by an underscore.
Default: NO
CHKDSN={YES|NO}
Default value of the CHKDSN parameter in the transfer requests:
YES - Check if the file exists while creating the transfer request.
NO - No check while creating the request. The check is run at transfer time (in
this case, the value of the GETCAR parameter is forced to N (get
physical characteristics of the file at transfer time).
Default: YES

CLUSTER=
Identifier (maximum of seven characters) common to the all address spaces
(request server, MAILBOX server and transfer monitors) within this cluster.
This identifier is used by Inter.Pel as a prefix to build the XCF group names.
This identifier has to be unique in a SYSPLEX.
Default: none.
COMSVC={nnn|200}
Number of the communication SVC.
Minimum: 200.
Maximum: 255.
Default: 200.
DISP330={YES|NO}
Display (YES or NO) PEL330 warning message during table installation.
This message is issued for all the sites whose first eight characters cannot be
used to create reception file names.
Default: YES.
FIJCL='dsname'
Name of the library containing the JCL skeletons used to transmit action
reports, call utilities or to submit the requested JCLs from the user message
table(GENUMSG). It is also the default value for the FICJCLI parameter in
the PELSUBX or PELSBJCLX macros.
The name must be between quotes.
Default: none; mandatory parameter.
FIPROC='dsname'
Name of the library containing the initialization command member and the
file swap JCLs. It also contains procedures started by the PROC transaction
in the monitor or defined in the user message table (GENUMSG).
GETCAR={YES|NO}
Default value of the GETCAR parameter in the transfer requests:
YES - Get physical parameters of this file (DCB, number of records) when
creating the transfer request.
NO - Get physical parameters at transfer time.
If the value of the CHKDSN is set to N, the value of the GETCAR parameter is
also set to N.
Default: YES
ID=name
Eight characters identifying the Inter.Pel monitor for the operator terminals.
It must be different for each of the address spaces within a cluster.
Default: first eight characters of the LOCNAME parameter.
LANG={FRAN|ENGL}
ENGL - Messages and screens in English.
FRAN - Messages and screens in French.
Default: FRAN.
LOCNAME=name
Name of the physical site. This value must be the same for each address-
space of the cluster.

MBRCPT={name|PRTCPT}
Name of the FIPROC member containing the skeleton of the JCL to be
submitted when one of the action report files (LOGTRANA/LOGTRANB)
is full.
Default: PRTCPT.
MBRFAC={name|PRTFAC}
submitted when one of the statistics files (FACTA/FACTB) is full.
Default: PRTFAC.
MBRLOG={name|PRTLOG}
submitted when one of the LOG files (PLOG/SLOG) is full.
Default: PRTLOG.
NOSERV=(mm,{ABEND|STOP|WTOR})
Defines the action performed by Inter.Pel batch utilities when the servers
(request server or mailbox server) are unavailable:
mm - Maximum wait time (minutes) when a server is unavailable
before the action defined by the second parameter is executed.
ABEND - Terminate the JOB with abend code U4095 (X'FFF')
STOP - Terminate the function and return a code 47 to the caller.
WTOR - Issue a PELS084 WTOR to the system console to determine
the action.
Default: (0,STOP)
PARM=si
s: Severity level determining when a message is displayed in the system log.
This value is compared with the severity level of each message generated.
If the message severity level is less than this value, the message is not
displayed in the system log.
i : Severity level determining when a message is displayed in the Inter.Pel
log. This value is compared with the severity level of each message
generated. If the message severity level is less than this value, the
message is not displayed in the Inter.Pel log.
Minimum: 0 (systematically displayed).
Maximum: 9.
Default: 55.
PROCI=name
Name of the FIPROC member containing the Inter.Pel initialization
commands. The commands contained in this member will be executed at the
end of the SRQ initialization. This member must not contain commands
executed in the transfer monitor address space (see the User Manuel to
check the address space in which the commands are executed).
Default: no initialization procedure.
REPLY={Y|N}
Y - Permanent REPLY on the MASTER CONSOLE.
N - No permanent REPLY.
Default: N.

TRACKER={YES|NO|SUM}
Enables tracking by XFB.Scope or Sentinel
YES - All changes of mailbox recording status are sent to the tracking
server.
NO - No information is sent to the tracking server.
SUM - Only the change of a status to 2, 4, 5, 6, 7, 9, A, C, I, N as well
as the messages in the message table are sent to the tracking server.
This parameter is used during the creation of the transfer request.
Default: YES if SCOPNAME is entered, otherwise NO.
SCOPCF='dsname'[,member]
Name of the Sentinel configuration file, if Sentinel is used with Inter.Pel.
Enter the name between quotation marks.
Optionally, enter the second sub-parameter to specify the name of the
member if the configuration file is contained in a PDS member.
Default: None, the parameter is mandatory if you are using Sentinel.
SCOPNAME=name
Name of the server waiting for the XFB.Scope or Sentinel (Axway products
tracking Inter.Pel activities) tracking/log messages generated by Inter.Pel
Default: none.
SCOPVERS={V1|V2}
The tracking server used with Inter.Pel:
V1: Tracking by XFB.Scope.
V2: Tracking by Sentinel.
Default: none.
TDATCLS=name
Name of the DATA CLASS used by SMS to create temporary files.
Default: none.
TEMPXR={index}
First level index for the temporary files allocated dynamically by Inter.Pel or
the utilities.
Maximum length: eight characters.
Default: none, mandatory parameter.
TMGTCLS=name
Name of the MANAGEMENT CLASS used by SMS to create temporary
files.
Default: none.
Enables tracking by XFB.Scope or Sentinel.
server.
TSTRCLS=name
Name of the STORAGE CLASS used by SMS to create temporary files.
Default: none.

VOL=(VOL1[,VOL2]....)
Names of the volumes used to generate the volume table. These volumes are
used by Inter.Pel to allocate the files received or the work files.
Up to sixteen volumes can be defined.
This parameter can be omitted if SMS is used (set in FLAGDYN).
Default: SMS is used.
WAITCPT={YES|NO}
Keyword used if the LOGTRANB file is not defined.
YES - Issue a WTOR and wait for the reply before reopening the action
report file after an X37.
NO - Reopen the action report file immediately after an X37. The data is
lost.
Default: YES.
WAITFAC={YES|NO}
Keyword used if the PELFACTB file is not defined.
YES - Issue a WTOR and wait for the reply before reopening the statistics
file after an X.37.
NO - Reopen the statistics file immediately after an X37. The data is lost.
Default: YES.
XTMOUT=mm
Time out value (minutes) for the batch XCF connections.
Caution: this value may in some cases be increased automatically by
Inter.Pel.
Default: 7.
XTMOUTI=mm
Time out value (minutes) for the XCF connections between Inter.Pel address
spaces.
You are advised to set XTMOUT (batch) and XTMOUTI values so that
XTMOUT>=(XTMOUTI*2)+1.
Default : 3
Comment cards may also be added ('*' in column 1).
A PELPARMS DD statement must be present in each Inter.Pel JCL address space as well as
each JCL batch using Inter.Pel. It can be the concatenation of two members; one containing
the common definition used by every address space; one containing specific definitions for the
current address space.

Sample PELPARMS file (see the SAMPLIB library ZPARMSRQ member)
*----------------------------------------------------------------------*
* DYNAMIC TABLES DEFINITIONS *
*----------------------------------------------------------------------*
DYNDFN=YES DYNAMIC TABLES USED
ENVLIST=TE ENVIRONMENT TABLE SUFFIX
RTGLIST=TE ROUTING TABLE SUFFIX
LDFLIST=00 DIFFUSION LIST TABLE SUFFIX
MODLIST=00 MODEL TABLE SUFFIX
MSGLIST=00 MESSAGE TABLE SUFFIX
TCPLIST=00 TCP/IP TABLE SUFFIX
X25LIST=00 X25 TABLE SUFFIX
DFNDS=IIIIIIII.INTERPEL.SAMPLIB PARMLIB 1ST DATASET
*----------------------------------------------------------------------*
* DYNAMIC CONFIG DEFINITIONS *
*----------------------------------------------------------------------*
ACB3270=APPOPERQ 3270 ACB
CHKDSN=YES CHECK DSN AT REQUEST TIME
CLUSTER=SOPR1 CLUSTER NAME (MAX. 7 CHAR)
COMSVC=200 COMMUNICATION SVC NUMBER
FIJCL='IIIIIIII.INTERPEL.JCL730' JCL SKELETON LIBRARY
FIPROC='IIIIIIII.INTERPEL.JCL730' PROC SKELETON LIBRARY
GETCAR=YES GET FILE ATTRIBUTES AT REQUEST TIME
ID=SOPR1RQ ADDRESS SPACE ID (MAX. 7 CHAR)
LANG=FRAN MSG AND SCREEN IN FRENCH
LOCNAME=SOPRA1 LOCAL NAME
MBRCPT=PRTCV7R FULL CPTR JCL MEMBER NAME
MBRFAC=PRTFV7R FULL STAT JCL MEMBER NAME
MBRLOG=PRTLV7R FULL LOG JCL MEMBER NAME
NOSERV=(0,STOP) DO NOT WAIT SERVERS
PROCI=OSOPR1Q INITIAL PROCEDURE
SCOPCF='IIIIIIII.SENTINEL.CONFILE' SENTINEL CONFIGURATION FILE
SCOPNAME=SCOPSOP XFB-SCOPE NAME
SCOPVERS=V2 USE SENTINEL
TEMPXR=TNSYT20 TEMPORARY FILES INDEX
TRACKER=YES START TRACKER TASK
VOL=(VOL001,VOL002) VOLUME LIST
WAITCPT=N WAIT BEFORE CPTR OPEN (X37)
WAITFAC=N WAIT BEFORE STAT OPEN (X37)
XTMOUT=7 WAIT 3MN BEFORE BATCH TIME OUT
XTMOUTI=3 WAIT 3MN BEFORE SERVER TIME OUT
The lists of members in a table are located in the PELDFNDS PELENVxx, PELRTGxx,
PELX25xx, PELTCPxx, PELMODxx, PELLDFxx and PELMSGxx members. They contain a
series of member names, beginning in column 1. The names of several members can be
declared on the same line and separated by commas. Comment cards may be used ('*' in
column 1).

Sample environment table list
*****************************************************************
*** MEMBER LIST USED TO CREATE ENVIRONMENT TABLE **
*****************************************************************
ENVDEB GENDEB
ENVLIGN GENLIGN
ENVSITE1 GENSITE
ENVLYON DEFINITIONS CONNECTION LYON
ENVSITE2 END OF GENSITES
ENVFILE,ENVTRAN,RESTE END OF DEFINITIONS
ENVEND GENEND
Refer to the PELENVTE, PELRTGTE, PELX25TE, PELTCPTE, PELMODTE, PELLDFTE

and PELMSGTE members in the SAMPLIB library.
See also the ZENVxxx, ZRTGxxx, ZTCPxxx, ZX25xxx, ZMODxxx, ZLDFxxx and
ZMSGxxx members for sample dynamic definitions.
Definitions are created using macro-instructions according to the syntax rules listed below.
- Continuation characters are not required: the cards are processed from columns 1 to
71; the end of a line is indicated by a space and the end of the macro-instruction by a
space that is not preceded by a comma.
- Null lines are treated as comments.
- It is not mandatory for continuations to start in column 16, as spaces at the beginning
of a line are ignored. This means that a parameter between quotes cannot be split
between two lines where there is a space.
- Definitions are not necessarily contiguous (GENTRAN, GENFILE, and so on).
- The GENTER and GENLU macro-instructions must respectively always follow the
GENLIGN and GENMGER macro-instructions with which they are associated.
However, additions or modifications may be made using a new GENPOINT macro-
instruction used to point to the corresponding entry.
- The GENPEL, GENPEL2, GENETEB5, GENETEB3, GENETB12, GENODET,

GENSIT, GENSITH and GENFTP macro-instructions must always follow the
GENMODEL macro-instruction with which they are associated.
- The first parameter in a macro-instruction must always be on the same line as the
macro-instruction itself.
- If an item (SITE, FILE, LIGN, and so on) is defined more than once, only the last
definition is used.
- The macro-instructions must always be in the following order.
- The GENDEB macro-instruction must always be the first macro-instruction

in the first definition member of the environment table.
- The GENEND macro-instruction must always be the last macro-instruction
in the last definition member of the environment table.

- The GENTER macro-instructions must always follow the GENLIGN
macro-instruction to which they are attached or a GENPOINT macro-
instruction used to point to this entry.
- The GENPEL, GENPEL2, GENETEB5, GENETEB3, GENETB12,
GENODET, GENSIT, GENSITH and GENFTP macro-instructions must
always follow the GENMODEL macro-instruction with which they are
associated.
- The GENLU macro-instructions must always follow the GENMGER
macro-instruction to which they are attached or a GENPOINT macro-
instruction used to point to this entry.
- The GENDST0 macro-instruction must always be the first macro in the first
definition member of the routing table.
- The GENDST3 macro-instruction must always be the last macro in the last
definition member of the routing table.
- The GENMODEL macro-instruction must always be the first macro in each
definition member of the model table.
3.1.2.1.2 Definitions Loaded by the MAILBOX Server
The MAILBOX server uses a mandatory DD card:
- PELPARMS, which provides the parameters required to install the configuration

parameters specifically used to run the MAILBOX server; this sequential file (or PDS
member) is mandatory in the JCL
Column 1 of the PELPARMS file contains the following set of keyword parameters:
ACB3270=
Name of the operator ACB associated with the MAILBOX server. This
parameter is optional since all the transactions can be entered from the
request server.
Default: none.
ACCMETH={DB2|VSAM}
VSAM - The Inter.Pel mailbox is managed by the VSAM access method.
DB2 - The Inter.Pel MAILBOX is managed by the DB2 RDBMS.
Default: VSAM.
ARM={YES|NO}
X constant,
Default: NO

CLUSTER=
Identifier (maximum of seven characters) common to all address spaces
(request server, MAILBOX server and transfer monitors) within this cluster.
Default: none.
COMSVC={nnn|200}
Minimum: 200.
Maximum: 255.
Default: 200.
DB2ID=name
SYSTEM-ID of the DB2 Inter.Pel MAILBOX manager.
This parameter is ignored if ACCMETH = VSAM.
Default: none; mandatory if ACCMETH = DB2.
DB2MAX={nn|10}
Maximum number of threads to be used by Inter.Pel.
It must be between 1 and 255 and less than the number defined in DB2.
Default: 10.
DB2PLAN=name
Plan used to open a thread with DB2.
Default: PELDB2Mx, where x is the DB2TAB parameter value.
DB2TAB={n|1}
Number of the MAILBOX used (see the DB2TB member in the CNTL
library).
It must be between 1 and 9 and different for all Inter.Pels with the same
DB2ID.
Default: 1.
DISP330={YES|NO}
used to create reception file names.
Default: YES.
FICNTRL=dsname
Name of the MAILBOX server control file.
FIJCL='dsname'
reports, call utilities or to submit requested JCLs from the user message

FIPROC='dsname'
ID=name
It must be different for each of the address spaces within a cluster.
LANG={FRAN|ENGL}
Default: FRAN.
LOCNAME=name
MLBROSRV=nn
Number of tasks started to manage read functions on this server. This
parameter then defines the parallelism rate for the read access to the
mailbox. For integrity reasons, updates are always serialized.
Minimum : 1.
Maximum : 10
Default: 3
PARM=si
i : Severity level determining when a message is displayed in the Inter.Pel
Maximum: 9.
Default: 55.
PROCI=name
commands. The commands contained in this member will be executed at the
end of the mailbox server initialization. This member must not contain
commands executed in the transfer monitor address space (see the User
Manuel to check the address space in which the commands are executed).

REPLY={Y|N}
Default: N.
SCOPNAME=name
Name of the server waiting for the Sentinel or XFB.SCOPE (Axway
products tracking Inter.Pel activities) tracking/log messages generated by
Inter.Pel
Default: none.
SCOPVERS={V1|V2}
Default: none.
TDATCLS=name
Default: none.
TEMPXR={index}
the utilities.
TMGTCLS=name
files.
Default: none.
server.
TSTRCLS=name
Default: none.

XTMOUT=mm
Inter.Pel.
Default: 7.
XTMOUTI=mm
spaces.
You are advised to set XTMOUT (batch) and XTMOUTI values so that
Default : 3
A PELPARMS DD statement must be present in each Inter.Pel JCL address space as well as
each JCL batch using Inter.Pel. It may be the concatenation of two members; one containing
the common definition used by every address space; one containing specific definitions for the

Sample PELPARMS file (see the SAMPLIB library ZPARMSMB member)
*----------------------------------------------------------------------*
* SPECIFIC CONFIGURATION MAILBOX SERVER *
*----------------------------------------------------------------------*
ACB3270=MLBACB 3270 ACB
ACCMETH=VSAM MAILBOX ACCESS METHOD
DB2ID=DB2T DB2 SSID
DB2MAX=16 DB2 MAX THREADS
DB2TAB=2 DB2 MAILBOX TABLE INDEX
FICNTRL=IIIIIIII.INTERPEL.CTRL CONTROL FILE
FIJCL='IIIIIIII.INTERPEL.JCL' JCL SKELETON LIBRARY
FIPROC='IIIIIIII.INTERPEL.PROC' PROC SKELETON LIBRARY
ID=SOPR1MX ADDRESS SPACE ID (MAX. 7 CHAR)
MLBROSRV=2 2 MAILBOX READS IN PARALLEL
PROCI=OSOPR1X INITIAL PROCEDURE
TRACKER=YES START TRACKER TASK
VOL=(VOL001,VOL002) VOLUME LIST
3.1.2.1.3 Definitions Loaded by the Transfer Monitor
The transfer monitor uses a mandatory DD card:
- PELPARMS, which provides the parameters required to install the configuration

parameters specifically used to run the transfer monitor; this sequential file (or PDS
member) is mandatory in the JCL.
Column 1 of the PELPARMS file contains the following set of keyword parameters.
ACB3270={xxxxxxxx}
Name of the operator ACB associated with the transfer monitor. This
parameter is optional since all the transactions can be entered from the
request server.
Default: none.

ARM={YES|NO}
X constant,
Default: NO
CLUSTER=
Identifier (maximum of seven characters) common to all address spaces
(request server, MAILBOX server and transfer monitors) within a cluster.
Default: none.
COMSVC={nnn|200}
Minimum: 200.
Maximum: 255.
Default: 200.
DISP330={YES|NO}
used to create reception file name.
Default: YES.
FIJCL='dsname'
reports, call utilities or to submit requested JCLs from the user message
FIPROC='dsname'
ID=name
It must be different for each of the address spaces within a cluster. If
Inter.Set coupling, Sentinel or XFB.Scope is used, the first seven
characters in the ID parameter must be different for all Inter.Pels on
the same site.

LANG={FRAN|ENGL}
Default: FRAN.
LOCNAME=name
PARM=si
i: Severity level determining when a message is displayed in the Inter.Pel
Maximum: 9.
Default: 55.
PROCI=name
commands.
REPLY={Y|N}
Default: N.
SCOPNAME=name
Name of the server waiting for the Sentinel or XFB.Scope (Axway products
tracking Inter.Pel activities) tracking/log messages generated by Inter.Pel
Default: none.
SCOPVERS={V1|V2}
Default: none.
TDATCLS=name
Default: none.

TEMPXR={index}
the utilities.
TMGTCLS=name
files.
Default: none.
server.
TSTRCLS=name
Default: none.
WLMNETID=name
NETWORK-ID used to register to WLM.
The name used to register is created as LOCATION.NETWORK-
ID.LUNAME where:
LOCATION = Value of the GENDEB WLMGROUP parameter,
NETWORK-ID = Value of this parameter.
LUNAME = Value of the ID parameter.
Default: None.
XTMOUT=mm
Inter.Pel.
Default: 7.
XTMOUTI=mm
spaces.
You are advised to set XTMOUT (batch) and XTMOUTI value so that
Default : 3

A PELPARMS DD statement must be present in each Inter.Pel JCL address spaces as well as
each JCL batch using Inter.Pel. It may be the concatenation of two members, one containing
the common definition used by every address space, one containing specific definitions for the
Sample PELPARMS file (see the SAMPLIB library ZPELPARM member)
*----------------------------------------------------------------------*
* SPECIFIC CONFIGURATION FOR V730 MONITOR *
*----------------------------------------------------------------------*
ACB3270=ACBPEL 3270 ACB
FIJCL='IIIIIIII.INTERPEL.JCL' JCL SKELETON LIBRARY
FIPROC='IIIIIIII.INTERPEL.PROC' PROC SKELETON LIBRARY
ID=SOPR1TF ADDRESS SPACE ID (MAX. 7 CHAR)
PROCI=OSOPR1 INITIAL PROCEDURE
TRACKER=YES STRART TRACKER TASK
3.1.2.1.4 Definitions Loaded in BATCH Mode
BATCH programs use only the PELPARMS configuration parameters. When one of these
programs needs a specific entry, it read it in the request server. However, in some cases, all
the Inter.Pel tables are loaded before any processing can be carried out.
The request server PELPARMS member is therefore recommended for BATCH jobs using
Inter.Pel.
3.1.2.2 DYNAMIC MODIFICATIONS
Dynamic modifications are carried out (from the request server only) via a member ADD or
REPLACE command affecting the contents of the member rather than the member name (a
member can be replaced even if it has never been installed, provided that it contains existing
definitions).
The ADD function is used to add new definitions. If a definition already exists when the ADD
function is used, the new definition is not installed, except for X25 or TCP les tables X25. For
these tables, the ADD function always installs the entry as the first in the table. This allows
you to reinstall an entry which was previously overridden by a temporary definition.
Therefore, for these tables, you are advised to only install modified entries grouped in a
temporary member to make sure that this update is effective, and to avoid memory problems
when installing the complete table.

The REPLACE function is used to modify existing definitions. If a definition does not exist, it
is added. Caution: some values cannot be modified by a dynamic update (see the description
of the various parameters).
A dynamic modification can be made in two ways:
- Via menu 6.6 of the request server monitor
- By entering the following command on the MVS console, or via the request server
native menu (option C):
ALTER {ADD|REP},{ENV|RTG|X25|TCP|MOD|MSG|LDF},member'
Each correctly installed definition is sent to the transfer monitor by the request server and is
immediately loaded into the transfer monitor address space. If any definitions are updated
dynamically while the transfer monitor is not running, the transfer monitor updates all
definitions from the request server memory when it is next started up.
The update will not be permanent until the definition has been added to a member in the
request server startup list.
A line-handler must be stopped to replace the GENLIGN macro that describes it or a

GENTER macro associated with it.
A session manager must stopped to replace the GENMGER macro that describes it or a
GENLU macro associated with it.
3.1.3 TABLES CREATED DYNAMICALLY
3.1.3.1 PRINCIPLES
From Version 5.4.0 onwards, it is no longer mandatory for the remote sites for which Inter.Pel
is the server to be defined in the environment table (the remote site systematically initiates the
connection). If the site is not defined in the environment table, it is also optional in the routing
table.
When using PeSIT Hors-SIT protocol, these definitions are not mandatory neither for
requester sites if the remote site is not an adjacent site and thus transfer involves routing. In
this case, Inter.Pel may also creates dynamically the site, using the adjacent site as the model.
The outgoing transfers toward this site will be sent directly to the adjacent site.
When in server mode, this function can be implemented in two ways, depending on the
network protocol used.
- For X.25 GATE or TCP/IP connections
When a call is received, an Inter.Pel module determines the name of the remote site by
looking for the caller number in the X.25 or TCP/IP table. A parameter in the GENX25NB or
GENIPNB macro-instruction used to define the entries in each of the tables authorizes the site
to be created dynamically. If this PROFILE parameter is set, it indicates that site creation has
been authorized and gives the name of the site to be used as a model when generating the new
site in the environment table. For protocols supporting dynamic site allocation, this creation
will have to be validated by the EXODETLG exit during the protocol connection phase.

If required, a GENDST2 entry is also created without any routing possibilities.
- For other types of connections via the PEL, PeSIT Hors-SIT, FTP or ETEBAC3
protocols
When a call is received, the connection is established on a physical site defined in the tables
(generally the dummy site). This site allows the first protocol-level exchanges to take place,
until the actual site to which the transfer is to be made is determined (in the parameter card for
ETEBAC3, the ACCEPTED command for PEL, in the preconnection message, the connect
FPDU, the CREATE FPDU or the SELECT FPDU for PeSIT Hors-SIT protocol, in the
USER/PASSWORD message in FTP).
If this logical site is not defined in the tables, Inter.Pel can create it automatically. A
GENSITE entry is then created using the same properties as those of the physical site with
which the connection was established. If necessary, a GENDST2 entry is also created without
any routing possibilities.
For security purposes, these sites can only be created if the operation is accepted by specific
exits:
EXODETLG for PEL protocol,

EXODETLG, EXPHS001 or EXPHS002 for PeSIT Hors-SIT protocol,
EXODETLG for FTP protocol,
USRETBCS for ETEBAC3 protocol.
These exits can also change the group (GENSITE macro-instruction GROUP parameter) to
which the newly-created site is attached.
If GENSAF macros are defined to use the external security functions for the connection, those
exits are no longer mandatory. The dynamic site allocation can be accepted through the
parameters of the GENSAF macro associated with the physical site that receives the
connection.
At the end of the connection, the site is automatically deleted, if it is not used by another
connection.
For the PeSIT Hors-SIT version E or FTP protocols, the site can be dynamically created, only
in requester mode, if the PROFILE parameter of the request gives the references for a
requester site (see paragraph depositing transfer requests). The request created that way is
automatically attached to the PROFILE site. To route the file to the final destination, referred
in the DEST parameter which is dynamically created, the PROFILE site must be the adjacent
site. This facility is also available when receiving files that must be routed to an unknown
destination. The final destination must not be an adjacent site in this case. The adjacent site to
which the transfer will be routed is retrieved from callers definitions.
3.1.3.2 DEPOSITING TRANSFER REQUESTS
To enable the remote site to receive files on server sites, the PEL PeSIT Hors-SIT, FTP and
ETEBAC3 protocols can be used to submit requests for transfers to sites not defined in the
Inter.Pel tables. In the PeSIT Hors-SIT protocol, this functionality allows deposits of files
towards requester sites not defined but whose transfers are routed through defined adjacent
sites.

These requests can be submitted via either the PELICA2 utility or the INTBAL interface. This
feature is not available for requests deposited via the transfer monitor user interface.
When a request is submitted, the PROFILE parameter can specify the site to be used as a
model when creating the request. In the PeSIT Hors-SIT protocol, if the site referenced in the
PROFILE parameter accepts outgoing calls (STOSR=B or STOSR=R), Inter.Pel will add the
request to the queue attached to this site and will automatically create the GENSITE and
GENDST2 (including routing via the PROFILE SITE) entries for the final destination site
when the key is selected for transfer.
3.1.3.3 ROUTING TOWARDS SITES DYNAMICALLY CREATED
When Inter.Pel MVS is an intermediate site with PeSIT Hors-SIT E or FTP protocols, it is not
mandatory to define the final destination of a transfer in the environment and the routing table.
This is only possible if the final destination is not the next site for the routing. The name of
the adjacent site to which the transfer will be routed is retrieved from the GENSITE macro
describing the caller site. The final destination will be dynamically created when routing the
file to the adjacent site.
The BLNDRTG parameter in the GENSITE describing the caller allows the use of this
facility.
This parameter accepts two sub-parameters:

The fisrt sub-parameter defines action to take when the final destination is
unknown:
A - Transfer is accepted and must be routed toward the adjacent site provided
in the second sub-parameter.
L - Transfer is accepted but it is processed locally without any routing.
R - Transfer is rejected.
The second sub-parameter provides the name of the adjacent site if the first
sub- parameter is et to A, else it is ignored. This adjacent site must be
defined in the Inter.Pel tables.
3.1.3.4 TRANSACTIONS ON SITES CREATED DYNAMICALLY
The STARTX, STOPX, TRACE and Q transactions are available for sites created
dynamically, even if they do not exist when the transaction is executed.
If the site exists when the transaction is executed, these commands are run in the same way as
for standard sites.
If the sites do not exist, or when a site created dynamically is deleted after being used, the
trace status, the active/inactive status and transfers pending for this site are saved in the
Inter.Pel queues. They will be reset when the site is next created.

3.2 CREATING THE ENVIRONMENT TABLE
A sample table definition can be found in the SAMPLIB library ENVTAB member.
The syntax of the macro-instructions used to set up the table is indicated below.
The macro-instruction descriptions use the default parameters.
3.2.1 GENBIND - CREATING A VTAM BIND
This macro-instruction is designed to generate a VTAM BIND, the name of which is specified
by the BIND parameter in the GENTER macro-instruction.
It is required to enable a specific BIND to be used (such as SYSTEM 38 connections).
NAME OPERATION OPERAND(S)
GENBIND NAME=nnnnnnnn (1)

,VALUE='xxxxxxxx'
(1) Key used for a dynamic REPLACE.
NAME=nnnnnnnn
Name of the BIND specified by the BIND parameter in the GENTER
macro-instruction.
Key used for a dynamic REPLACE.
VALUE='xxxxxxxx'
Hexadecimal value of the BIND.
Maximum length: 80 bytes.

3.2.2 GENCENT - DEFINING HOSTS
This macro-instruction is designed to list the sites attached to a remote site. Only files
originating from that site, or from sites specified in the macro-instruction, can be transferred
to Inter.Pel by the remote site.
If the macro-instruction is not declared, Inter.Pel only checks whether the source site is
defined in the environment table (GENSITE macro-instruction ).
In the FTP protocol, this macro-instruction is used to define all the IP addresses that may be
used by outgoing DATA type connections for an incoming IP address. The outgoing address is
received in the PORT command and may be changed in the EXFTP005 exit routine. If the
address returned by this exit has been changed, it has to be defined in the GENCENT macro,
if not, the PORT command is rejected.
GENCENT NAME=nnnnnnnn (1)

,SITE=(site1[,site2]....)
NAME=nnnnnnnn
Name of the remote site (must be defined in a GENSITE macro-instruction
with the CENTRAL=YES parameter).
In the FTP PROTOCOL, the incoming IP address as nnn.nnn.nnn.nnn
SITE=(site1[,site2]....)
List of the sites attached to this remote site (must be defined in a GENSITE
macro-instruction with the CENTRAL =NO parameter).
In the FTP protocol, the list of authorized outgoing DATA type addresses.
Maximum: 16 sites.

3.2.3 GENDEB - CREATING THE BEGINNING OF THE PARAMETER TABLE
This macro-instruction is mandatory.

It must be the first macro-instruction in the first member in the dynamic table list.
Option 6.7 can be used to modify some of its parameters directly.
label GENDEB [,AMOD31={Y|N}]

[,AUTOLABL={Y|N}]
[,BCOMP={Y|N}]
[,BUF1SP={nnn|1000}]
[,CONFIRM={Y|N}]
[,CPTE3S={Y|N}]
[,CPTRC={Y|N}]
[,DDSYSIN={name|SYSIN}]
[,DEFJBN={name|PELCPTR}]
[,DATCLS=name]
[,DEFNTF={name|PELICAN}]
[,DISP330={Y|N}]
[,DSNETEB3=name]
[,DSNETEB5=name]
[,DSNFTP=name]
[,DSNODET=name]
[,DSNPEL=name]
[,DSNSITH=name]
[,ET5DSN1='dsname']
[,ET5DSN2='dsname']
[,ET6DSN1='dsname']
[,ET6DSN2='dsname']
[,EXLOG={name|DUMMY}]
[,EXTSEC={Y|N}]
[,FTPFP1=port]
[,FTPFP2=port]
[,FTPFP3=port]
[,FTPFP4=port]
[,FTPLP1=port]
[,FTPLP2=port]
[,FTPLP3=port]
[,FTPLP4=port]
[,HSIDSNCA='dsname']
[,HSIDSNUS='dsname']
[,INDXR={index|PELFICH}]
[,KCENT={Y|N}]
[,LDSN={nn|44}]
[,LSITE={nn|8}]
[,MAXPRIM=nnnnnnnn]
[,MAXTRAN={nnnnn|512}]
[,MBRJBR={name|USERTSO}]
[,MBRUTIL={name|MBRUTIL}]
[,MENUSER=name]
[,MGTCLS=name]
[,MSUPPER={Y|N}]
[,ODTLV={n|1}]
[,PROTECT={Y|N}]
[,RAMAX={n|5}]
[,REPORT={Y|N}]
[,RKC9={Y|N}]
[,RMINDEX={Y|N}]
[,ROUTCDE=r
[,SCRATCH={Y|N}]
[,SPACE=nnnn]
[,SSLDSNCA='dsname']
[,SSLDSNUS='dsname']
[,STAT={Y|N}]
[,STRCLS=name]
[,SUBJBR={Y|N}]

[,TABROUT={name|TABROUT}]
[,TIMER={nn|10}]
[,USRXTAB={name|PELODTS1}]
[,WLMALG={R|BS|BM]}
[,WLMGROUP=name}
AMOD31={Y|N}
Y - The transfer buffers are allocated above the 16 Mbytes boundary
if the MVS Release is 4.3.0 or later.
N - The transfer buffers are always allocated below the 16 Mbytes
boundary.
Default: Y.
AUTOLABL={Y|N}
Y - When PI 37 (label) is not provided in the transfer request
(PeSIT Hors-SIT E protocol), Inter.Pel must complete it with
the local DSNAME of the transmitted file.
N - When PI 37 (label) is not provided in the transfer request
(PeSIT Hors-SIT E protocol), Inter.Pel must not transmit it.
Default: Y.
BCOMP={Y|N}
Y - The spaces in the messages are compressed.
N - The spaces in the messages are not compressed.
This value can be changed for a specific message in the user message table.
Default: N.
BUF1SP={nnn|1000}
Size in Kbytes reserved for Inter.Pel inter-task communications.
Default: 1000.

CONFIRM={Y|N}
Y - Inter.Pel asks for confirmation of all interactive change requests and all
transfer requests.
N - Inter.Pel does not ask for confirmation.
Default: N.
List of screens requiring confirmation:
1.1 : PF2, PF4, PF7, PF9, PF11 and PF12 function keys on the
Transfer Detail screen
1.2 : PF2, PF4, PF6, PF7, PF9, PF11 and PF12 function keys on the
Transfer Detail screen
1.3 : PF7, PF9, PF11 and PF12 function keys on the Transfer Detail
screen
1.4 : PF9, PF11 and PF12 function keys on the Transfer Detail screen
1.5 : PF7, PF9, PF11 and PF12 function keys on the Transfer Detail
screen
3.1 : PF6, PF7, PF9 and PF12 function keys on the PEL2 Destination
Management screen
3.2 : PEL2 Transfer Cancellation screen
5.7 : PF9 function key on the Dual Dataset Control screen
6.6 : Dynamic Definition Installation screen
6.7 : Inter.Pel Parameter Modification screen
7.2 : PF9 function key on the X25TABLE Entry Display screen
7.3 : PF9 function key on the GENSITE Entry Display screen
7.6 : PF9 function key on the GENLIGN Entry Display screen
7.7 : PF9 function key on the IPTABLE Entry Display screen
8.1 : PEL, ODETTE, or ETEBAC Transfer Request screen
8.2 : Homogeneous MVS-MVS Transfer Request screen
8.3 : PeSIT Hors SIT Transfer Request screen
8.4 : PeSIT SIT Transfer Request screen
8.5 : ETEBAC3 Reception Request screen
8.6 : PEL-D or ODETTE Reception Request screen
8.7 : PeSIT Hors SIT Reception Request screen
8.8 : ETEBAC5 Transfer Request screen
8.9 : ETEBAC5 Reception Request screen
8.M : PeSIT HORS SIT Message Transfer Request screen
CPTE3S={Y|N}
Y - ETEBAC3 transfers write transfer action reports at the bank end.
N - ETEBAC3 transfers do not write transfer action reports at the bank
end.
Default: N.
CPTRC={Y|N}
Y - The transfer action reports are written to the PRINT1D file.
N - The transfer action reports are not written to the PRINT1D file.
Used for type 1 transfers only.
Default: Y.
DATCLS=name
Name of the DATA CLASS used as a default by SMS to create reception
files. This value may be overridden by the GENFILE DATCLS parameter.
Default: none.
DDSYSIN={name|SYSIN}
DDNAME of the SYSIN file containing the CPU authorization key(s).
Default: SYSIN.

DEFJBN={name|PELCPTR}
Default JOBNAME used to submit the transfer action report jobs each time
an action report is received from the remote receiver site (type 2 transfers).
Default: PELCPTR.
DEFNTF={name|PELICAN}
Default NOTIFY used to submit transfer action report jobs each time an
action report is received from the remote receiver site (type 2 transfers).
Default: PELICAN.
DISP330={YES|NO}
used to create reception file name.
Default: YES.
DSNETEB3=name
Name of the default GENDSN associated with ETEBAC 3 transfers. This
macro will force the dsname of all the files received through this protocol.
This value can be overridden by the RDSN value of the GENFILE.
When a value is provided, all the ETEBAC 3 transfers will use a GENDSN,
it will not be possible to use the standard Inter.Pel name.
Default: No GENDSN for this protocol.
DSNETEB5=name
Name of the default GENDSN associated with ETEBAC 5 transfers. This
When this value is provided, all the ETEBAC 5 transfers will use a
GENDSN, it will not be possible to use the standard Inter.Pel name.
DSNFTP=name
Name of the default GENDSN associated with FTP transfers. This macro
will force the dsname of all the files received through this protocol. This
value can be overridden by the RDSN value of the GENFILE.
When this value is provided, all the FTP transfers will use a GENDSN, it
will not be possible to use the standard Inter.Pel name.
DSNODET=name
Name of the default GENDSN associated with ODETTE transfers. This
When this value is provided, all the ODETTE transfers will use a GENDSN,
it will not be possible to use the standard Inter.Pel name.
DSNPEL=name
Name of the default GENDSN associated with PEL transfers. This macro
will force the dsname of all the files received through this protocol. This
value can be overridden by the RDSN value of the GENFILE.
When this value is provided, all the PEL transfers will use a GENDSN, it
will not be possible to use the standard Inter.Pel name.

DSNSITH=name
Name of the default GENDSN associated with PeSIT Hors-SIT transfers.
This macro will force the dsname of all the files received through this
protocol. This value can be overridden by the RDSN value of the GENFILE.
When this value is provided, all the PeSIT Hors-SIT transfers will use a
GENDSN, it will not be possible to use the standard Inter.Pel name.
ET5DSN1='dsname'
Name of the file containing the ETEBAC5 version 1 secure keys.
This file is create by the PELET5CD utility.
Default: none.
ET5DSN2='dsname'
Name of the file containing the random encryption codes for the ETEBAC5
version 1 security elements. If this second file is not specified, Inter.Pel
considers that the first file contains all the required data.
This file is created by the PELET5CD utility.
Default: none.
ET6DSN1='dsname'
Name of the file containing the ETEBAC5 version 2 secure keys.
Default: none.
ET6DSN2='dsname'
Name of the file containing the random encryption codes for the ETEBAC5
version 2 security elements. If this second file is not specified, Inter.Pel
considers that the first file contains all the required data.
Default: none.
EXLOG={name|DUMMY}
Name of the exit activated each time an entry is written to the LOG file (see
the System Programmer's Reference Manual).
Default: DUMMY (no exit).
EXTSEC={Y|N}
Y - Inter.Pel calls the external security exits (see the System Programmer's
Reference Manual).
N - Inter.Pel guarantees security.
When coded to Y, this parameter will force depelicanization of sequential
files in PEL2 protocol to be performed by an IEBGENER in a batch JOB.
The PROTECT parameter is ignored.
Default: N.
FTPFP1=port
Port number that defined the beginning of the first range of ports that may
be used as DATA type ports in the FTP protocol (PASV command)
Default: none.
FTPFP2=port
Port number that defined the beginning of the second range of ports that may
Default: none.

FTPFP3=port
Port number that defined the beginning of the third range of ports that may
Default: none.
FTPFP4=port
Port number that defined the beginning of the fourth range of ports that may
be used as DATA type ports in FTP protocol (PASV command)
Default: none.
FTPLP1=port
Port number that defined the end of the first range of ports that may be used
as DATA type ports in the FTP protocol (PASV command)
Default: none.
FTPLP2=port
Port number that defined the end of the second range of ports that may be
used as DATA type ports in the FTP protocol (PASV command)
Default: none.
FTPLP3=port
Port number that defined the end of the third range of ports that may be used
as DATA type ports in the FTP protocol (PASV command)
Default: none.
FTPLP4=port
Port number that defined the end of the fourth range of ports that may be
used as DATA type ports in the FTP protocol (PASV command)
Default: none.
HSIDSNCA='dsname'
Name of the file containing X509 authority certificates used by HSI.
This file is created by the PELGX509 utility.
Default: none.
HSIDSNUS='dsname'
Name of the file containing X509 user certificates and the associated private
keys used by HSI.
This file is created by the PELGX509 utility.
Default: none.
INDXR={index|PELFICH}
First level index for permanent files allocated dynamically.
Maximum length: seven characters.
Default: PELFICH.
KCENT={Y|N}
Y - Requests towards a type 0 destination are authorized. This request will
create central type records in the mailbox.
N - Requests toward a type 0 destination are not authorized. No central
type records in the mailbox.
Default: N.

label =
Name of the environment table.
Must be equal to the value of the ENVIR parameter in the GENDST3
macro.
LDSN={nn|44}
Length of the file names in the messages.
Minimum: 20.
Maximum: 44.
Default: 44.
LSITE={nn|8}
Length of the site names in the messages.
Minimum: 8.
Maximum: 20.
Default: 8.
MAXPRIM={nnnnnnnn}
Maximum number of megabytes used as primary space when allocating
reception files.
Default : None, no limit.
MAXTRAN={nnnnn|512}
Maximum number of GENTRAN macro-instructions that can be declared.
Default: 512.
MBRJBR={name|USERTSO}
submitted if SUBJBR=Y (type 2 transfers).
Default: USERTSO.
MBRUTIL={name|MBRUTIL}
Name of the FIJCL member containing the skeleton of the JCL to be
submitted to call a reception utility (type 2 transfers).
Default: MBRUTIL.
MENUSER=name
Name of the user menu associated with option "U" on the Inter.Pel primary
option menu.
Default: no user menu.
MGTCLS=name
Name of the MANAGEMENT CLASS used as a default by SMS to create
reception files. This value may be overridden by the GENFILE MGTCLS
parameter.
Default: none.
MSUPPER={Y|N}
Y - The messages are displayed in upper-case characters.
N - The messages are displayed in lower-case characters.
This value can be changed for a specific message in the user message table
(UPPER parameter).
Default: N.

ODTLV={n|1}
ODETTE protocol: version of the ODETTE protocol supported by the local
site.
Default: 1.
PROTECT={Y|N}
This parameter is only used when sequential files are received for type 2
transfers. It determines whether the received file is to be depelicanized
directly in the file specified by the DSNDEST parameter for the transfer.
Y - The file is depelicanized in a temporary file and then copied to the
DSNDEST file via a batch IEBGENER external to Inter.Pel. The
EXRAC001 security exit is also called before the utility is submitted.
N - The file is depelicanized directly in the DSNDEST file. No utility
submit is required.
CAUTION: this parameter is not used if the EXTSEC parameter is set to
YES.
Default: N.
RAMAX={n|5}
Maximum number of standard receive tasks initialized by Inter.Pel for all
type 2 transfers.
Default: 5.
REPORT={Y|N|X}
Y - When a transfer request is executed, an action report is generated in the
format defined for Version 5.2.0 and above.
N - When a transfer request is executed, no action report is generated.
X - When a transfer request is executed, an action report is generated in the
format defined in versions prior to 5.2.0.
Default: Y.
RKC9={Y|N}
Y - When a file is received for a type 0 destination, a central-type record
must be created in the MAILBOX.
N - When a file is received for a type 0 destination, no central-type record
is created in the MAILBOX.
Default: N.
RMINDEX={Y|N}
Y - The major indexes of the destination files are checked (see menu 6.2).
N - The major indexes of the destination files are not checked.
This parameter is only used for type 2 transfers.
Default: Y.
ROUTCDE=c
Value (1 to 16) of the ROUTE CODE used for the WTO issued by
Inter.Pel.
Default: 2.
SCRATCH={Y|N}
Y - Received files that have been rerouted are deleted after being routed.
N - Received files that have been rerouted are retained after being routed.
Default: Y.

SPACE=nnnn
Number of Kbytes allocated for reception files in FTP protocols. This value
can be overridden by the GENFILE SPACE parameter, the ALLO command
or the EXFTP003 exit routine.
Default: 100.
SSLDSNCA = dsname
Name of the file containing X509 authority certificates used by SSL.
Maximum length: 44 characters.
Default: none (SSL is not used).
SSLDSNUS = dsname
Name of the file containing X509 user certificates and the associated private
keys used by SSL.
Default: none (SSL is not used).
STAT={Y|N}
Parameter specifying use of the statistics function.
Default: Y.
STRCLS=name
Name of the STORAGE CLASS used as a default by SMS to create
reception files. This value may be overridden by the GENFILE STRCLS
parameter.
Default: none.
SUBJBR={Y|N}
Parameter controlling submission of the JCL in the member specified by the
MBRJBR parameter, designed to send a transfer action report each time a
transfer is acknowledged by the remote receiver site (type 2 transfers).
Default: Y.
TABROUT={name|TABROUT}
Name of the routing table.
This parameter must be equal to the value of the GENDST0 NAME
parameter.
Default: TABROUT.
TIMER={nn|10}
Period of time used by the type 2 transfer selectors to reactivate the sessions
that would have been closed; two digits must be specified.
Default: 10 minutes.
USRXTAB={name|PELODTS1}
Name of the ASCII/EBCDIC conversion table to be used for the transfers.
The default PELODTS1 table and the conversion table definition procedure
are described in the System Programmer's Reference Manual.
Caution: when this table is defined, all the protocol components are
converted accordingly.
Default: PELODTS1.

WLMALG={R|BM|BS}
Algorithm used to dispatch requestor transfers on the transfer monitors.
R- Rotate, a transfer to one destination will performed on the next
eligible active monitor.
BM - Best Monitor, request server keeps the number of active transfers for
each monitor. A new requestor transfer will be started on the least
loaded monitor. When several monitors have the same number of
active transfers, the rotate algorithm is used between those monitors.
BS - Best System, this algorithm can be used if the monitors are running
on different systems within a SYSPLEX. To select the monitor that
will execute a transfer, Inter.Pel will query WLM to determine the
least loaded system. The transfer will be run on this system. When
several systems have the same activity, or if several monitors are
running on the same system, the Best Monitor algorithm is used
between those monitors.
Default: R.
WLMGROUP=name
LOCATION used to register to WLM.
The name used to register is created as LOCATION.NETWORK-
ID.LUNAME where:
LOCATION = Value of this parameter.
NETWORK-ID = Value of the PELPARMS WLMNETID parameter.
LUNAME = Value of the PELPARMS ID parameter.
Default: None.

3.2.4 GENDSN - DEFINING A RECEIVE FILE NAME
This macro-instruction is designed to generate a physical file name (DSN) in receive mode
instead of the name generated automatically by Inter.Pel, and consequently to avoid using the
RENAME functions. It is used if its name is referenced by the GENFILE macro-instruction
RDSN parameter associated with the transfer.
Caution: the name generated by this macro must be unique.
Note: this table is loaded above the 16 Mbytes boundary.
GENDSN NAME=name (1)

,DSN=dsn
[,ACT={DELETE|ERASE|VERIFY|REPMB|NREPMB}]
[,DISP={NEW|OLD|BOTH}]
[,CONTIG={Y|N}
[,DSNDAT=dsname]
[,DSNIDX=dsname]
[,MEMBER=member]
(1): Key used for a dynamic REPLACE.
ACT={DELETE|ERASE|VERIFY|REPMB|NREPMB }
Action on the existing file prior to reception:
DELETE - the file must be created by Inter.Pel; the file is deleted if it
already exists
ERASE - erases the file
VERIFY - checks that the file is empty
REPMB - when receiving one or several PDS members, replace a
member that already exists in the PDS.
NREPMB- when receiving one or several PDS members, do not replace a
member that already exists in the PDS. The transfer continues
with the next member if several members must be received, or
is rejected when only one member must be received.
Default = VERIFY.
CONTIG={Y|N}
Contiguous allocation option:
Y - allocates the file contiguously
N - does not allocate the file contiguously
You are advised, whenever possible, to request contiguous allocation to
ensure that Inter.Pel has enough space available at the beginning of the
transfer to receive the whole file.
Default = Y.
DISP={NEW|OLD|BOTH}
Receive file check indicator:
NEW - the file must be created by Inter.Pel; the transfer is refused if the
file already exists
OLD - the file must already exist; the transfer is refused if the file does
not exist
BOTH - the file is created if it does not already exist
Default = BOTH.

DSN=dsn
Character string used to generate the file name. This string can contain one
or more symbolic variables. Each symbolic variable must have the "&"
prefix. The variables are resolved at the start of the transfer.
If alphanumeric data is to be concatenated with symbolic variables, periods
are required after the symbolic variables. The periods are deleted when the
variables are resolved. If symbolic variables are to be concatenated, a period
is not required after the variables.
The file name generated can be a GDG file name. In this case, the string
must be terminated by (+1) (the next generation is created) or (0) (the
existing generation is reused).
For PeSIT Hors-SIT version E protocol only, if the file name start with a /,
reception will be done in an HFS file.
The predefined symbolic variables that can be used in the dsn string are:
&APPL name of the application used in receive mode

maximum length: 8 bytes
&DD day of the month
length: 2 bytes
&DEST name of the destination site
&HH current hour
length: 2 bytes
&INDXR first level index of the permanent files allocated dynamically
(GENDEB INDXR parameter)
&MIN current minute
length: 2 bytes
&MM month
length: 2 bytes
&MSG accompanying message (concatenation of MSG1 and MSG2)
maximum length: 80 bytes.
&ORIG name of the remote site
&PSNAME protocol-level name of the file (PI12) in PeSIT protocol only
&PSTYPE file type (PI11) in PeSIT protocol only
length: 5 bytes
&QQQ day in the year
length: 3 bytes
&RANK transfer rank
&SS current second
length: 2 bytes
&TIME current time in the hhmmss format
length: 6 bytes
&YY two-digit year
length: 2 bytes
&YYYY four digit-year
length: 4 bytes

You can include only a substring of a variable by using the SUBSTR
function. This function is coded as follows:
&SUBSTR(s:l,&variable)
where "s" = start position in the &variable variable

and "l" = length to be used
Example:
&SUBSTR(2:10,&MSG1)
with &MSG1 = ABCDEFGHIJKLMNOPQRST
results in BCDEFGHIJK
The &variable field can itself be the concatenation of several variables,

constants or other &SUBSTR functions. However, the first element must
never be a constant.
If the string contains parentheses (use of GDG or the SUBSTR function), it

must be between quotes.
The file name resulting from the resolved variables must not exceed
44 characters.

NAME=name
Name of the macro-instruction referenced by the RDSN parameter in the
GENFILE macro-instruction.
DSNDAT=dsn
Character string used to generate the DATA component name for VSAM
file reception (see DSN parameter).
Default: DSN suffixed with .D.
DSNIDX=dsn
Character string used to generate the INDEX component name for VSAM
KSDS file reception (see DSN parameter).
Default: DSN suffixed with .I.
MEMBER=member
Member name in the DSN PDS in which the file has to be received. A
sequential file can thus be received in a PDS member. As for DSN
parameters, this member name can be built from variables resolved at
transfer time.
This facility is only available for PeSIT Hors-SIT version E protocol.
Default: none, reception in a sequential file.

3.2.5 GENEND - CREATING THE END OF THE ENVIRONMENT TABLE
This macro-instruction marks the end of the environment table. It is the last macro-instruction
in environment table.
It cannot be replaced or added dynamically.
NAME OPERATION OPERAND (S)
GENEND

3.2.6 GENFILE- DEFINING AN APPLICATION
Note : this table is loaded above the 16M line.
[label] GENFILE APPL=name (1)

,BLKSIZE={nnnnn|AUTO}
,GROUP=group (1)
,LRECL=nnnnn
[,CODMONT={nn|04}]
[,COMP={TYPEC0|TYPEC1|TYPEC2|TYPEC3|TYPEC4|TYPECU}]
[,DATCLS=name]
[,DIR=nnn]
[,DSORG={AUTO|PDS|PDSE|ESDS|KSDS|RRDS|SEQ}]
[,EMPTY={Y|N}]
[,EXT2={Y|N}]
[,HFSTEXT={Y|N}]
[,LENMONT={nn|12}]
[,MEMFILE={YES|NO}]
[,MGTCLS=name]
[,POSMONT={n|0}]
[,RDSN=dsn]
[,RECFM={format|FB}]
[,RMODEL=model]
[,RUPSEQ={nn|01}]
[,SITCDE={nnnnn|65535}]
[,SPACE=nnnn]
[,STRCLS=name]
[,SUBJCL=name]
[,TEXT={Y|N}]
[,TRACKER={YES|NO|SUM}]
[,TYPID=type]
[,TYPINF=type]
[,TYPMONT=E]
[,TYPSYNT=type]
[,TYPXFER=type]
[,USRCOMP=name]
[,USRRW=name]
[,USRXTAB={DUMMY|name|STANDARD}]
[,VERMONT={YES|NO}]
[,VERSEQ={YES|NO}]
[,VSAVGLR=length]
[,VSCISZD=size]
[,VSCISZI=size]
[,VSKEY=(length,offset)]
[,VSSHR=(s1,s2)]
APPL=name
Application name (one to eight characters).

BLKSIZE={nnnnn|AUTO}
AUTO - Inter.Pel automatically calculates the optimum block size
according to the type of volume on which the file is to be
allocated. When SMS is fully used on Inter.Pel (no VOL
parameter in the PELPARMS file), the optimum block size is
computed by SMS.
nnnnn - Physical block size of the associated files, even if SMS is used.
For the PEL1 application, this value is of no immediate
significance, but a value other than AUTO allows the BLKSIZE
used on the remote site to be propagated.
NOTE: a zero value is the equivalent of AUTO.
CODMONT={nn|04}
Only used when VERMONT=YES.
This code is located in the first two positions of the logical record. The
checksum is calculated on the fields defined by POSMONT and
LENMONT. The records concerned are identified by this code. If several
checksums are required, they must be defined as shown below (maximum of
eight codes): CODMONT=0407 indicates that the codes to be selected are
"04" and "07".
Default: 4.
COMP={TYPEC0|TYPEC1|TYPEC2|TYPEC3|TYPEC4|TYPECU}
TYPEC0 - No compression ( C0 )
TYPEC1 - Reduced horizontal compression ( C1 )
TYPEC2 - Full horizontal compression ( C2 )
TYPEC3 - Data compacting ( C3 )
Compacting for fixed-length sequential files with records
containing identical fields
TYPEC4 - Compacting and compression ( C4 )
TYPECU - User compression ( CU )
The name of the routine is provided by the USRCOMP
parameter in the GENFILE macro-instruction
Overrides the compression mode specified in the GENSITE macro-
instruction.
Default: not used.
DATCLS=name
Name of the DATA CLASS used by SMS to create reception files.
Default: Value of the GENDEB DATCLS parameter.
DIR=nnn
For PDS reception with PeSIT Hors-SIT version E protocol, number of
directory blocks of the reception file.
Default : Value received from the remote site.

DSORG={AUTO|PDS|PDSE|ESDS|KSDS|RRDS|SEQ}
Reception dataset organization.
This parameter is only valid with PeSIT Hors-SIT version E protocol, which
is the only protocol able to receive non-sequential files.
AUTO - Use organization received from the remote site,
PDS - Receive in a partitioned file,
PDSE - Receive in an extended partitioned file (PDS-E),
ESDS - Receive in a VSAM ESDS file,
KSDS - Receive in a VSAM KSDS file,
RRDS - Receive in a VSAM RRDS file,
SEQ - Receive in a sequential file.
Default: AUTO.
EMPTY={Y|N}
Used by the PEL protocol.
N - Empty files are rejected in receive mode.
Y - Empty files are accepted in receive mode.
Default: N.
EXT2={Y|N}
N - No secondary allocation for receive files.
Y - Secondary allocation for receive files.
Default: Y.
GROUP=group
Group name. This parameter must also be present in the GENSITE macro-
instruction GROUP option. All sites belonging to the same group use the
same file profiles.
HFSTEXT={Y|N}
N - Transmitted or received HFS file is a binary file, no need to manage
CRLF.
Y - Transmitted or received HFS file is a text file, system has to manage
CRLF.
Default: Y.
LENMONT={nn|12}
Length of the amount field in the logical record expressed in bytes.
Default: 12.
LRECL=nnnnn
Length of the logical record expressed in bytes.
MEMFILE={YES|NO}
Flag indicating whether Inter.Pel is to create the file on disk.
YES - Inter.Pel loads the file received into the memory.
NO - Inter.Pel creates the file on disk.
Default: NO.
MGTCLS=name
Name of the MANAGEMENT CLASS used by SMS to create reception
files.
Default: Value of the GENDEB MGTCLS parameter.

POSMONT={n|0}
Offset pointing to the amount field in the logical record. It is used with
LENMONT and CODMONT.
Default: 0.
RDSN=dsn
Name of the GENDSN macro used to create the dsname of the reception
files.
Default: None.
RECFM={format|FB}
Format of the logical record (any format).
Default: FB.
RMODEL=model
Name of the model used for routing.
Default: none.
RUPSEQ={nn|01}
Sequence break code in the first two bytes of the logical record. This
parameter is ignored when VERSEQ=NO.
Default: 01.
SITCDE={nnnnn|65535}
SIT application code.
Used by the PeSIT protocol.
If the requested application is declared in the Inter.Pel tables when a request
is submitted, the corresponding SITCDE is used as the PI 11 in the protocol;
otherwise, the application parameter is used directly as the PI 11.
When the transfer takes place (in transmit or receive mode) with the
SITCDE as the sent or received PI 11, the file properties are taken from the
application, and the values transmitted in receive mode are ignored.
Default: 65535.
SPACE=nnnn
Number of Kbytes allocated for reception files in FTP protocols. This value
can be overridden by the ALLO command or the EXFTP003 exit routine.
Default: None.
STRCLS=name
Name of the STORAGE CLASS used by SMS to create reception files.
Default: Value of the GENDEB STRCLS parameter.
SUBJCL=name
Prefix for the skeleton members used by the automatic JCL triggering
function (see Section 2.11 of this guide).
Maximum of six characters.
Default: SUBJCL value of the GENSITE describing the remote site.

TEXT={Y|N}
ODETTE protocol: text file indication.
Y - ODETTE text file.
N - Other file type.
Default: N.
Y - Mailbox records describing transfers using this application are sent to
the tracker every time their status changes.
N - Nothing is sent to the tracker for this application.
S - Mailbox records describing transfers using this application are sent to
the tracker only when their status changes to 2, 4, 5, 6, 7, 9, A, C, I,
N.
This parameter is set when creating the mailbox record.
Default: value of this parameter in the GENSITE macro.
TYPID=type
Type of ETEBAC5 identifier (first byte in the PI 11).
Used by the ETEBAC5 protocol.
If the requested application exists in the Inter.Pel tables when a request is
submitted, the corresponding TYPID, TYPSYNT, TYPINF and TYPXFER
parameters are concatenated in the PI 11 for the protocol. Otherwise, the
application parameter is used directly as the PI 11.
When the transfer takes place (in the transmit or receive mode) with the
concatenation of the TYPID, TYPSYNT, TYPINF and TYPXFER
parameters as the sent or received PI 11, the file properties are taken from
the application, ignoring the values transmitted in receive mode.
One character.
Default: none.
TYPINF=type
Type of ETEBAC5 data (bytes 3 to 7 in the PI 11).
Five characters.
Default: none.
TYPMONT=E
Amount representation mode.
E - Extended decimal (only mode supported).
Default: E.

TYPSYNT=type
Type of ETEBAC5 syntax (second byte in the PI 11).
One character.
Default: none.
TYPXFER=type
Type of ETEBAC5 transfer (eighth byte in the PI 11).
One character.
Default: none.
USRCOMP=name
Name of the user compacting routine.
(See the System Programmer's Reference Manual).
Default: not used.
USRRW=name
Name of the user routine activated for each file read/write operation. (See
Default: not used.
USRXTAB={DUMMY|name|STANDARD}
ODETTE, PeSIT Hors SIT and ETEBAC5 protocols: name of the
conversion table used when this type of file is transferred (maximum of
eight characters). The table used converts the contents of the file only; the
protocol components are converted using the table defined in the GENDEB
macro-instruction.
STANDARD - Value of the GENSITE USRXTAB parameter.
DUMMY - No conversion.
name - Name of the user conversion table.
Default: STANDARD.
VERMONT={YES|NO}
Checksum flag.
Default: NO.

VERSEQ={YES|NO}
Logical record sequence check flag. The sequence is in position 3 of the
record and is six bytes long.
Default: NO.
VSAVGLR=length
Average record length when receiving VSAM files with PeSIT Hors-SIT
version E protocol.
Default: value received from the remote site.
VSCISZD=size
DATA CI size when receiving VSAM files with PeSIT Hors-SIT version E
protocol.
VSCISZI=size
INDEX CI size when receiving VSAM KSDS files with PeSIT Hors-SIT
version E protocol.
VSKEY=(length,offset)
Length and position of the key when receiving VSAM KSDS files with
PeSIT Hors-SIT version E protocol.
VSSHR=(s1,s2)
SHR option when receiving VSAM files with PeSIT Hors-SIT version E
protocol.

3.2.7 GENLIGN - CREATING A LINE HANDLER- CONTROL BLOCK
This macro-instruction is used to generate a connection manager.
The line-handler must be stopped before replacing a GENLIGN macro.
label (1) GENLIGN TYPE={CONSOLE|STAT|DYN|MCH|LU62

|IPITL|IPIBM|IPIB3} (2)
[,ACBNAME=(acb1[,[m1]][,acb2,m2])]]
[,CVCNB={nn|20}]
[,EXTATT={BIND|NO|QUERY}]
[,IPADO=address]
[,ISTATUS={ACT|INACT}]
[,MSESSOU={nn|10}]
[,PORT=(p1,[,[m1]][,p2,m2])]
[,PORTOUT=number]
[,PORTOUT2=number]
[,SUBSID=(id1[,[m1]][,id2,m2])]

(2) Cannot be changed via a dynamic REPLACE.
ACBNAME=(acb1[,[m1]][,acb2,m2])
TYPE=CONSOLE: not used (replaced by the value of the PELPARMS
ACB3270 parameter.
TYPE=MCH: name(s) of the VTAM ACB(s) used to monitor X.25
accesses.
TYPE=DYN|LU62: name(s) of the VTAM ACB(s) used for resource
management.
This parameter accepts a list of acb/monitor pairs to assign different ACBs
to all the monitors.
It accepts as many ACBs as the number of monitors in the cluster. Those
ACBs can be generic if no monitor is dedicated to an ACB. Inter.Pel will
then use the first free ACB for a monitor starting this line. Those ACBs can
also be dedicated to one monitor if a monitor name (ID) is associated with
the ACB. Inter.Pel will then use this ACB when this monitor starts this line.
Both solutions can be mixed, some ACBs are dedicated to monitors and the
others are generic creating a pool.
Default: none.
CVCNB={nn|20}
Used when TYPE=MCH|IPITL|IPIBM|IPIB3.
nn Maximum number of SVCs to be managed in the X.25 access or
maximum number of accesses controlled by the TCP/IP manager.
Default: 20.

EXTATT={BIND|NO|QUERY}
Used when TYPE=CONSOLE. This parameter determines whether
extended attributes are used on the terminals.
BIND - Extended attributes are used if they are defined in the BIND for
this logon.
NO - Extended attributes are not used.
QUERY - A QUERY is forced on the terminal at LOGON.
This option may block the keyboard on terminals that do not support the
QUERY function.
Default: BIND.
IPADO=address
Caller address provided to the remote site in outgoing calls.
Default: address provided by the system.
ISTATUS={ACT|INACT}
Initial site status.
ACT - The line is active and the line-handler starts when Inter.Pel is
started up.
INACT - The line is inactive. A STALINE or STARTMCH command is
required to activate the line.
Default: ACT.
label =
TYPE=MCH: name of the MCH LU associated with the X.25 access.
TYPE=IPITL or IPIB3: name of the LUOUT to be contacted when calling
a site.
Mandatory parameter.
MSESSOU={nn|10}
nn: Maximum number of simultaneous outgoing connections requested by
Inter.Pel for terminals defined in the GENTER macro-instructions
associated with this GENLIGN definition. It is used only for DYN, STAT or
LU62 type GENLIGN definitions.
Default: 10.
PORT=number
listening port numbers used by the TCP/IP manager. Mandatory when
TYPE=IPITL or IPIB3:
This parameter accepts a list of port/monitor pairs to assign different ports to
all the monitors.
It accepts as many ports as the number of monitors in the cluster. Those
ports can be generic if no monitor is dedicated to a port. Inter.Pel will then
use the first free port for a monitor starting this line. Those ports can also be
dedicated to one monitor if a monitor name (ID) is associated with the port
number. Inter.Pel will then use this port when this monitor starts this line.
Both solutions can be mixed, some ports are dedicated to monitors and the
Default: none.

PORTOUT=number
Port number used to establish DATA outgoing connections with FTP
protocol (PASV mode) if PORTOUT2 parameter is omitted.
Beginning of the port number range used to establish DATA outgoing
connections with FTP protocol (PASV mode) if PORTOUT2 parameter is
provided.
This parameter is only effective if the GENTER FPORT parameter is set to
Y.
Default: none.
PORTOUT2=number
End of the port number range used to establish DATA outgoing connections
with FTP protocol (PASV mode). The full range includes all the
portsbetween PORTOUT and PORTOUT2.
This parameter is only effective if the GENTER FPORT parameter is set to
Y.
Default: none.
SUBSID={ACSS/TCPIP|name}
TYPE=IPITL: name of the SNS/TCPaccess subsystem.
TYPE=IPIB3: name of the IBM product JOB or STC.
It consists of four characters if the Interlink product is used; otherwise, it has
eight characters.
It is optional and set by default to ACSS for SNS/TCPaccess or to default
TCP value (retrieved from the SYSTCPD file or forced toTCPIP) for the
IBM product.
This parameter accepts a list of id/monitor pairs to assign different ids to all
the monitors.
It accepts as many ids as the number of monitors in the cluster. A single id
can be used if only one value is provided. Inter.Pel will then use this id for
all the monitors starting this line. Those ids can also be dedicated to one
monitor if a monitor name (ID) is associated with the TCP id. Inter.Pel will
then use this id when this monitor starts this line. Both solutions can be
mixed, some ids are dedicated to monitors and another one is used for the
others monitors.
Default: ACSS or IBM TCPIP default.
TYPE={CONSOLE|STAT|DYN|MCH|LU62|IPITL|IPIBM|IPIB3}
Type of LINE HANDLER.
- CONSOLE - Inter.Pel terminal management
- STAT - Static heterogeneous transfer management
- DYN - Dynamic heterogeneous transfer management
- MCH - X.25 access management (no associated GENTER
definition)
- LU62 - Dynamic heterogeneous transfer management in LU 6.2
mode
- IPITL - TCP/IP access management with the Interlink
SNS/TCPaccess product (no associated GENTER
definition)
- IPIBM - TCP/IP access management with the IBM product (no
associated GENTER definition). Equivalent to IPIB3
- IPIB3 - TCP/IP access management with the IBM product (no
associated GENTER definition)
Cannot be changed via a dynamic REPLACE.

3.2.8 GENLOGON - CREATING A LOGON
This macro-instruction is used to send a LOGON of variable format (see the LOGONS
parameter in the GENTER macro-instruction), particularly when connecting to non-IBM
systems. This macro-instruction is only used for type 1 transfers.
GENLOGON NAME=name (1)

,VALUE={X'hex value'|C'char value'}
NAME=name
Name of the LOGON to be specified in the GENTER definition.
VALUE={X'hex value'|C'char value'}

LOGON value.
Hexadecimal - VALUE=X'010101'
Character - VALUE=C'TEST1'

3.2.9 GENLU - CREATING A HOMOGENEOUS MVS-MVS LINK
This macro-instruction must immediately follow the GENMGER macro-instruction to which

it is attached, or follow a GENPOINT macro-instruction pointing to the required GENMGER
definition.
The session manager (GENMGER) to which a GENLU is attached must be stopped to

dynamically replace this GENLU.
GENLU DEST=name (1)

,LUNAME=name
[,ACQ={N|A}]
[,BLOCK={nnnn|1024}] (2)
[,BUFNO={nn|15}] (2)
[,GROUP=name]
[,HCOMP={Y|N|R}] (2)
[,HSO={Y|N}]
[,LOGMODE={name|NO|0}]
[,NUMFILE={n|3}]
[,RTME={n|5}]
[,VTAMARL={nnnn|1024}] (2)

(2) Cannot be changed via a dynamic REPLACE.
ACQ={N|A}
N - LUNAME corresponds to a SECONDARY LU.
A - LUNAME corresponds to a PRIMARY LU (initializing the session).
Sites wishing to exchange files must have opposite definitions (on
PRIMARY LU and SECONDARY LU).
Default: N.
BLOCK={nnnn|1024}
Size of the pelicanized file blocks.
- It must be numeric and =< 30720.
- It must have the same value as the VTAMARL parameter.
- It must be equal to 1024 for Inter.Pel versions prior to Version 4.1.0.
- It must be consistent with the remote site definitions.
It cannot be changed via a dynamic REPLACE.
Default: 1024.
BUFNO={nn|15}
Number of buffers allocated to these files.
This number must be numeric and =< 255.
(See S.P.L Data Management: BUFNO parameter in the DCB macro-
instruction).
Default: 15.
DEST=name
Name of the destination.

GROUP=name
Group name. This parameter must also appear in the GROUP option of the
GENFILE macro-instruction. This parameter is only used by the automatic
JCL triggering function (see Chapter 2, INSTALLATION).
Default: not used.
HCOMP={Y|N|R}
Y - Extended compression is applied in the transmit and receive modes,
assuming that the Inter.Pels likely to receive type 2 transfers use
version 5.3.0 or later and has his HCOMP parameter coded to Y or R.
This compression can be used for any application (including LOAD).
N - No extended compression is applied in the transmit or receive modes.
R - No files are transmitted with extended compression.
Files can be received using this new type of compression, or the
previous type.
Cannot be changed via a dynamic REPLACE.
Default: R.
HSO={Y|N}
Y - HIGH SPEED OPTION. This option allows the windowing to be used
in live with the value of the RTME parameter during file
transmissions.
N - No HIGH SPEED OPTION.
It must be consistent with the remote site definitions.
Default: N.
LOGMODE={name|NO|0}
0 - The BIND is supplied by Inter.Pel.
name - LOGMODE to be used.
NO - Inter.Pel supplies neither the BIND nor the LOGMODE.
Default: 0.
LUNAME=name
Name of the VTAM destination LU (eight characters).
NUMFILE={n|3}
Maximum number of files transferred simultaneously (maximum: 10).
Default: 3.
RTME={n|5}
Must only be used when HSO=Y.
HSO window (2 to 20).
Default: 5.
VTAMARL={nnnn|1024}
Maximum VTAM RECEIVE ANY buffer size.
- It must be numeric and =< 30720.
- It must be less than the MAXDATA network parameter.
- It must be equal to the value specified in the BLOCK parameter of
the GENLU macro-instruction.
- It must be equal to 1024 for Inter.Pel versions prior to Version 4.1.0.
- It must be consistent with the remote site definitions.
Default: 1024.

3.2.10 GENMGER - CREATING A SESSION MANAGER CONTROL BLOCK
Homogeneous MVS-MVS links
At least one GENMGER NAME=PELICAN2 entry must be declared to define PEL2 protocol
support.
The session manager must be stopped to dynamically replace a GENMGER.
GENMGER ACBNAME=name
,NAME=name (1)
[,SELMON=mon]
ACBNAME=name
Name of the ACB used for type 2 transfers.
NAME=name
Name of the main type 2 transfer task. Currently, this name is always
PELICAN2.
SELMON=mon
Monitor on which PEL2 can be started.
If this parameter is specified when the START2 command is run, Inter.Pel
checks that the monitor where this command is passed is indeed the
authorized monitor and does not execute the command if this is not the case.
If this parameter is not specified, the first monitor executing a START2
command starts the protocol. All subsequent START2 commands are then
ignored for as long as the PEL2 remains active on this monitor.
Default: none.

3.2.11 GENPFK - CREATING A FUNCTION KEY TABLE
This macro-instruction is designed to generate a 3270 function key table. These function keys
can be used on the Inter.Pel READY screen (C option on the primary option menu).
GENPFK NAME=name (1)

[,AP1=transaction]
[,AP2=transaction]
[,ENTER=transaction]
[,RAB=transaction]
[,PF1=transaction]
.........
[,PF12=transaction]
NAME =
Name of the function key table specified by the TABPFK parameter in the
GENTER macro-instruction.
AP1=transaction
Name of the transaction called by the function key.
(PF1 to PF12 generate PF13 to PF24 automatically.)
Default: no associated transaction.
NOTE: the transaction list can be found in the sample environment table in SAMPLIB
library ENVTAB member.

3.2.12 GENPOINT - POINTING TO GENLIGN OR GENMGER
This macro-instruction is designed to point to a GENLIGN or GENMGER definition when

adding or modifying GENTER or GENLU entries.
GENPOINT {LIGN=linename|MGER=manager}
LIGN=linename
Name of the LIGN to which you wish to point.
Default: none.
MGER=manager
Name of the MGER to which you wish to point.
Default: none.

3.2.13 GENSAF - DEFINING AN EXTERNAL SECURITY PROFILE
The GENSAF macro is used to define the security measures to be taken by Inter.Pel for each
possible checkpoint during connection with a requester external site. These checks are
performed using standard SAF macros and therefore involve the use of an external security
tool (RACF, TSS, ACF2).
Note: this table is loaded above the 16 Mbytes boundary.
GENSAF NAME=name (1)

[,ACCES1={A|C|R|U}]
[,ACCES2={A|C|R|U}]
[,ACCES3={A|C|R|U}]
[,ACCES4={A|C|R|U}]
[,CLASS1=class]
[,CLASS2=class]
[,CLASS3=class]
[,CLASS4=class]
[,DSA1={Y|N}]
[,DSA2={Y|N}]
[,DSA3={Y|N}]
[,EXIT1={Y|N}]
[,RSRC1=resource]
[,RSRC2=resource]
[,RSRC3=resource]
[,RSRC4=resource]
[,SAF1={Y|N}]
[,SAF2={Y|N}]
[,SAF3={Y|N}]
[,SAF4={Y|N}]
[,TCBSEC={N,1,2,3}]
ACCES1={A|C|R|U}
Type of access to be tested on the RSRC1 resource:
- A : Alter
- C : Control
- R : Read
- U : Update
Default: R.

ACCES2={A|C|R|U}
- A : Alter
- C : Control
- R : Read
- U : Update
Default: R.
ACCES3={A|C|R|U}
- A : Alter
- C : Control
- R : Read
- U : Update
Default: R.
ACCES4={A|C|R|U}
Type of access to be tested on the RSRC4 resource. This parameter is
processed only if the PHYGET/PHYPUT parameter in the corresponding
GENSITE macro is set to SAF.
- A : Alter
- C : Control
- R : Read
- U : Update
Default: R.
CLASS1=class
Class of the RSRC1 resource.
Default: none.
CLASS2=class
Default: none.
CLASS3=class
Default: none.
CLASS4=class
Class of the RSRC4 resource. This parameter is processed only if the
PHYGET/PHYPUT parameter in the corresponding GENSITE macro is set
to SAF.
Default: none.
DSA1={Y|N}
Dynamic site creation at checkpoint 1:
- Y : automatic site creation authorized
- N : automatic site creation not authorized
The site created dynamically depends on the protocol used:
PeSIT Hors-SIT : name in the preconnection message
ETEBAC 5 : name in the preconnection message
PEL : name in *ACCEPTE
ODETTE : name in the SSID
FTP : name in the SIGNON
Default: N.

DSA2={Y|N}
PeSIT Hors-SIT : PI 03 in the CONNECT
ETEBAC 5 : PI 03 in the CONNECT
PEL : not used
ODETTE : not used
FTP : not used
Default: N.
DSA3={Y|N}
PeSIT Hors-SIT : PI 61 in the SELECT/CREATE if defined;
otherwise, PI 03 in the SELECT/CREATE
ETEBAC 5 : PI 61 in the SELECT/CREATE
PEL : site in ?TRANS
ODETTE : name in the SFID
FTP : name in the SITE P_ORG command
Default: N.
EXIT1={Y|N}
EXODETLG exit called (Y or N).
Default: N.
NAME=name
Name of the security profile.
This name is defined in the GENTER SAFPROF parameter for the
associated communication profile.
RSRC1=resource
Resource for which the access authorization must be controlled at
checkpoint 1 if SAF1=Y. If this resource is not specified and the SAF1
check is requested, only the user and password are checked.
Default: none.
RSRC2=resource
check is requested, only the user and password are checked.
Default: none.
RSRC3=resource
check is requested, only the user is checked.
Default: none.

RSRC4=resource
check is requested, only the user and password are checked against the user
name and password received at the FTP login. This parameter is processed
only if the PHYGET/PHYPUT parameter in the corresponding GENSITE
macro is set to SAF.
Default: none.
SAF1={Y|N}
SAF security check at point 1 (current point at which EXODETLG is called)
PeSIT Hors-SIT : when the preconnection message is received
ETEBAC 5 : when the preconnection message is received
PEL : when the ACCEPTE command is received
ODETTE : when the SSID is received
FTP : when the USER/PASSWORD is received
Default: N.
SAF2={Y|N}
SAF security check at point 2 (remote site connection)
PeSIT Hors-SIT : when the CONNECT is received
ETEBAC 5 : when the CONNECT is received
PEL : not used
ODETTE : not used
FTP : not used
Default: N.
SAF3={Y|N}
SAF security check at point 3 (routing elements received)
PeSIT Hors-SIT : when the CREATE or SELECT is received
ETEBAC 5 : when the CREATE or SELECT is received
PEL : when the TRANS command is received
ODETTE : when the SFID is received
FTP : when a SITE P_ORG command is received
Default: N.
SAF4={Y|N}
SAF security check at point 4 (FTP RETR/STOR commands with the
physical file name). This parameter is processed only if the
PHYGET/PHYPUT parameter in the corresponding GENSITE macro is set
to SAF.
PeSIT Hors-SIT : not used
ETEBAC 5 : not used
PEL : not used
ODETTE : not used
FTP : when a RETR or STOR command is received with
a request for a physical name (file name beginning
with a quote)
Default: N.

TCBSEC={N|1|2|3}
Indicates the ACEE that will be linked to the TCB on which the transfer
takes place. This allows the security tool to manage automatically all
accesses to the resources during this transfer and in the jobs submitted by
this TCB:
- N : maintain Inter.Pel authority
- 1 : perform security controls at the first checkpoint
- 2 : perform security controls at the second checkpoint
- 3 : perform security controls at the third checkpoint
Default: N.

3.2.14 GENSITE - CREATING A SITE DEFINITION CONTROL BLOCK
[label] GENSITE NAME=name (1)

,GROUP=name
[,ACQ={nn|00}]
[,ALTLOCN={name|NO}]
[,ALTPATH=name]
[,BLNDRTG=[(]{A|L|R}[,dest)]]
[,BUFSIZE={nnnn|0}]
[,CENTRAL={YES|NO}]
[,CMDLOT={L|S}]
[,COMPACT={YES|NO|YESN}]
[,EARLMSG={Y|N}]
[,ET5CID=id]
[,ET5GEST={n|2}]
[,ET5PST=name]
[,ET5TID=id]
[,FILESIZ={E|R}]
[,ISTATUS={ACT|INACT}]
[,LINGRP=name]
[,{LOGONF=llll|LOGONU=llll|LOGONS=llll}]
[,LUIN=name]
[,LUOUT=name]
[,MANU={Y|N}]
[,MAXCON={n|1}]
[,MSGLEN={nn|4}]
[,ODTEE={F|I}]
[,RETRY=(m,n)]
[,PHYGET={YES|NO|SAF}]
[,PHYPUT={YES|NO|SAF}]
[,PSCD={M|N|Y}]
[,PSCDINT=(tt,mmm)]
[,PSNACK={Y|N}]
[,PSWID={name|NO}]
[,SCNMLBX={n|3}]
[,SECAUTH={NO|1|2|U}]
[,SECCIPH={NO|RSA|1|3|U}]
[,SECSEAL={NO|P|RSA|C|M|S|U}]
[,SECSIGN={NO|1|2|U}]
[,SELMON=({E|I},mon1[,mon2)]]
[,SITLNAME=name]
[,SITTYP={CTE|CTR|IE|IR}]
[,SITNUM={nnnnn|65535}]
[,SSLPROF=name]
[,STOCSA=cccc]
[,STOICD=c]
[,STOOID=cccc]
[,STOORGC=cccccccccccccc]
[,STOPRFX={Y|N}]
[,STOSPC={Y|N}]
[,STOSR={S|R|B}]
[,STOXST={Y|N}]
[,SUBJCL=name]
[,TPNAME=name]
[,TRACKER={Y|N|S}]
[,TRAILER={xx|Y|N}]
[,USRXTAB=name]
[,XUSER={Y|N}]

ACQ={nn|00}
PEL protocol : Indicates the number of blocks transmitted before
acknowledgment.
ODETTE protocol : Credit value.
Default: 00.
ALTLOCN=name
PEL protocol : Used when LINGRP is set. Local Inter.Pel
name for the remote site (see the same
parameter in the GENTER macro-instruction).
PeSIT Hors SIT protocol : Site name used during the preconnect phase.
This name and its associated passwords must
be defined via option 6.5 in the Inter.Pel menu.
ETEBAC 5 protocol : Site name used during the preconnect phase.
This name and its associated passwords must
be defined via option 6.5 in the Inter.Pel menu.
NO generates a preconnect message without
either a site name or password.
Default: not used.
ALTPATH=name
Name of the resource to be used if the LU of the MCH specified in the
LUOUT parameter cannot be contacted after the number of retries requested
(see the RETRY parameter).
Default: not used.
BLNDRTG=[(]{A|L|R}[,dest)]
Allows routing towards unknown sites in PeSIT Hors-SIT version E or FTP
protocols.
The fisrt sub-parameter defines action to take when the final destination is
unknown:
A - Transfer is accepted and must be routed towards the adjacent site
provided in the second sub-parameter,
L - Transfer is accepted but it is processed locally without any routing,
R - Transfer is rejected.
The second sub-parameter provides the name of the adjacent site if the first
sub-parameter is set to A, otherwise it is ignored. This adjacent site must be
defined in the Inter.Pel tables.
Default: R.
BUFSIZE={nnnn|0}
Size of the data blocks exchanged during transfers.
It must be consistent with the remote site definition.
Mandatory.
Default: 0.
CENTRAL={YES|NO}
Indicates whether the site is CENTRAL.
YES - The site is CENTRAL. A GENCENT macro-instruction must have
been declared for this site.
Default: NO.

CMDLOT={L|S}
Length of the application name in the PEL protocol DDL (start of batch) and
LL (batch list) commands.
S - Short, four-character application name.
L - Long, eight-character application name.
Default: S.
COMPACT={YES|NO|YESN}
Flag specifying whether the data transferred to this site must be compressed.
PEL protocol:
NO - No compression.
YES - Type C1 compression.
YESN - Type C2 compression.
ODETTE protocol:
NO - No compression.
YES - Compression.
ETEBAC5 V2 Protocol:
NO - Compression is performed after encryption (meaning no
compression)
YES - Compression is performed before encryption (if the remote site
supports this facility).
Default: NO.
EARLMSG={Y|N}
Used in the PEL protocol.
Flag Indicating whether the accompanying messages are transferred at the
beginning of the protocol-level exchange (so that they are available in the
EXVOLPL1 exit).
This function can only be used if it is supported by the remote site.
N - Messages are transferred normally during the protocol-level
exchange.
Y - Messages are transferred at the start of the exchange.
Default: N.
ET5CID=id
ETEBAC5 identifier. This field, which is concatenated after the ET5TID
field, is used as an identifier in PI 3, 4, 61 or 62.
21 characters.
Default: none.
ET5GEST={n|2}
Sequence number of the dual key for the manager. This is the number in the
ETEBAC5 card. It is used to determine the certificates to be used on the
requester site.
1 : Test card.
2 : Live card.
Default: 2.
ET5PST=name
Inter.Pel name of the site used as the service provider during a transfer. The
CONNECT PI 3 or 4 is then created from the ET5CID and ET5TID
parameters for this site. This site must also be defined in the routing table as
the adjacent site.
20 characters.
Default: none.

ET5TID=id
Type of ETEBAC5 identifier. This field, which is concatenated before the
ET5CID field, is used as an identifier in PI 3, 4, 61 or 62.
3 characters.
Default: none.
FILESIZ={E|R}
E - When a transfer request is submitted, Inter.Pel estimates the size of the
file to be transferred according to the file allocation.
R - When a transfer request is submitted, Inter.Pel reads the file to be
transferred in order to calculate its exact size.
Default: E.
GROUP=name
Generic name allowing applications to be collected by site or group of sites
(see the GENFILE macro-instruction).
ISTATUS={ACT|INACT}
Initial site status.
(Valid when the LINGRP parameter is set).
ACT - The site is active when Inter.Pel is started up.
INACT - A STARTX command is required to activate the site.
Default: INACT.
LINGRP=name
Name of the associated GENLIGN.
(See the section entitled Assigning GENTER Entries Automatically)
Default: not used.
{LOGONF=llll|LOGONU=llll|LOGONS=llll}
Valid if the LINGRP parameter is set.
LOGONF - Formatted LOGON. When the physical connection has been
established, the LOGON APPLID(llll) message is generated.
LOGONU - Unformatted LOGON. When the physical connection has
been established, the llll message is generated.
LOGONS - Specific LOGON. When the physical connection has been
established, the message associated with the GENLOGON
macro-instruction specified is generated.
If no LOGON is specified, no message is generated.
This parameter is only used on DYN or STAT lines.
Default: not used.
LUIN=name
Name of the associated calling LU.
(Valid if the LINGRP parameter is set).
Default: not used.
LUOUT=name
Name of the associated outgoing LU, name of the label for the GENLIGN
defining the associated MCH or TCP/IP manager (valid if the LINGRP
parameter is set).
Default: not used.

MANU={Y|N}
PEL protocol:
N - The transfer switches to status "5" in transmit mode and "7" in
receive mode, even if a checksum error occurs.
Y - The transfer switches to status "W" (requiring manual
validation), if a checksum error occurs.
PESITHSE protocol:
N - When a routed file is received, a receive acknowledgment
message is automatically sent to the source site.
Y - No message is sent when a routed file is received.
Default: N.
MAXCON={n|1}
Used when the LINGRP parameter is set. Maximum number of
simultaneous outgoing connections (must be set to 1 in the NPSI PCNE
mode).
NOTE: if the maximum number of connections is reached, Inter.Pel creates
an additional connection when a 0 priority transfer request is
submitted.
Default: 1.
MSGLEN={nn|4}
Used for PeSIT Hors SIT E.
Maximum length in Kbytes of the messages (PI 91) that can be transmitted
or received by this site.
Default: 4.
NAME=name
Site name (maximum of 20 characters).
Mandatory parameter.
The name must correspond to a type 0 site in the routing table, or to the
value of the GENDEB macro-instruction LOCNAME parameter in the
tables of the corresponding remote site.
ODETTE protocol: ODETTE ORGANIZATION CODE and ODETTE
COMPUTER SUB-ADDRESS for the site.
ODTEE={F|I}
ODETTE protocol: EERP management.
F - GALIA version, French mode.
I - International mode.
Default: F.
PHYGET={YES|NO|SAF}
Accept FTP RETR (GET) commands with physical file name (DSN):
YES : accept these commands,
NO : reject these commands,
SAF : check authorization depending on fourth level of GENSAF
macro.
Default: NO

PHYPUT={YES|NO|SAF}
Accept FTP STOR (PUT) commands with physical file name (DSN):
YES : accept these commands,
NO : reject these commands,
SAF : check authorization depending on fourth level of GENSAF
macro.
Default: NO
PSCD={M|N|Y}
This parameter is used to indicate whether or not the Change Direction
functionality must be used with this site, and, if so, with what restrictions:
Y the feature is fully implemented
M the feature is limited to message transmission
N the feature is not activated
Default: N
PSCDINT=(tt,mmm)
Change Direction polling:
- the first sub-parameter indicates the number of minutes between two
automatic calls
- the second sub-parameter indicates the maximum number of active
connections beyond which a new connection is not activated when the
first sub-parameter deadline falls
Default : no polling, no connection limit.
PSNACK={Y|N}
Negative Acknowledgement support:
Y the feature is supported by the adjacent site
N the feature is not supported
Default: N
PSWID={psw|NO}
Site used to retrieve the protocol password sent in the PI 05 in PeSIT Hors-
SIT version E protocol. On connection, Inter.Pel will complete the PI 05
with the password associated with the site defined in this PSWID parameter
in option 6.5 of the monitor. New password feature is still not supported,
second half of PI 05 is always set to the same value as the first half.
NO means that PI 05 must not be transmitted (no password)
Default: NO.
RETRY=(m,n)
Valid when the LINGRP parameter is set.
Outgoing calls:
m: Number of retries. If no transfer has taken place after "m" attempts and
the ALTPATH parameter is not set, the site is disabled (m= 0: the
number of retries is unlimited).
n: Interval between two retries (expressed in minutes).
Incoming calls in PAD mode:
m: Number of consecutive errors after which the PEL480 message is sent
to the log.
n: Number of consecutive errors after which the connection is aborted.
Default: value of the RETRY parameter in the GENTER definition
associated with the GENLIGN entry to which the LINGRP parameter points.

SCNMLBX={n|3}
Number of minutes between two MAILBOX scans, if the ISC=N parameter
is set in the GENDEB macro-instruction.
Default: 3.
SECAUTH={NO|1|2|U}
Parameter used in ETEBAC5 protocol.
Authentication level requested for the site.
NO : No authentication.
1 : One-way authentication.
2 : Two-way authentication.
U : Server: all types of authentication are accepted.
Requester: no authentication.
Default: U.
SECCIPH={NO|RSA|1|3|U}
Encryption requested for the site.
NO : No encryption.
RSA/1 : Server : encryption is required
Requester : DES encryption with transmission of RSA
encrypted elements and use of a sequester.
3 : Server : encryption is required.
Requester : Triple DES encryptionwith transmission of RSA
encrypted elements and use of a sequester.
U : Server : the received encryptionis accepted.
Requester : no encryption.
Default: U.
SECSEAL={NO|RSA|U}
Sealing is requested for this site:
NO : No sealing.
P : Server : sealing is requested.
Requester : DES CBC sealing with transmission of RSA
encrypted elements and partial seals.
RSA/C : Server : sealing is requested.
Requester: DES CBC sealing with transmission of RSA
encrypted elements but no partial seals.
M : Server : sealing is requested.
Requester : DES MDC sealing, no transmission of elements and
no partial seals.
S : Server : sealing is requested.
Requester : SHA-1 sealing, no transmission of elements and no
partial seals.
U : Server : the received sealing is accepted.
Requester : no sealing.
Default: U.

SECSIGN={NO|1|2|U}
Signature requested for the site.
NO : No signature.
1 : Single signature.
2 : Double signature.
U : Server: the received signature is accepted.
Requester: no signature.
Default: U.
SELMON=({E|I},mon1[,mon2)]
Allocates sites to the transfer monitors within a cluster.
The first sub-parameter defines the function to apply on the following
monitors list.
E : Exclude this site on the following transfer monitors.
I : Include this site in the following monitors.
The following parameters are the list of sites on which the function is
applied. The name of the monitor is the ID parameter in their PELPARMS
file.
Default: Site included in all the transfer monitors.
SITLNAM=name
Used by PeSIT Hors SIT level E.
PeSIT name of the local site used for the connection. When
STORE&FORWARD is used with this site, this parameter is mandatory to
retrieve the local name of Inter.Pel during connections with the adjacent site.
When STORE & FORWARD is not used, this name will always replace the
LOCAL parameter from the transfer request.
Default: not used.
SITTYP={CTE|CTR|IE|IR}
Type of SIT station.
CTE - Transmit host.
CTR - Receive host.
IE - Transmit station.
IR - Receive station.
Default: not used.
SITNUM={nnnnn|65535}
Number associated with the type of station.
Numeric value between 1 and 65535.
Default: 65535.
SSLPROF=name
Name of the SSL security profile (GENSSLP) associated with this site.
Default: None (SSL is not used).
STOCSA=cccc
ODETTE protocol: ODETTE COMPUTER SUB-ADDRESS
Maximum of six characters between quotes.
Default: not used.

STOICD=c
ODETTE protocol: ODETTE INTERNATIONAL CODE DESIGNATOR
for the site.
Maximum of four characters.
Default: not used.
STOOID=cccc
ODETTE protocol: ODETTE IDENTIFIER constant for the site
Set to "O" for Release 1 of the protocol.
Default: not used.
STOORGC=cccccccccccccc
ODETTE protocol: ODETTE ORGANIZATION CODE for the site.
Maximum of fourteen characters between quotes.
Default: not used.
STOPRFX={Y|N}
ODETTE protocol Support of: the standard ODETTE prefix.
N - The remote site does not support the standard prefix.
Y - The remote site supports the standard prefix.
Default: Y.
STOSPC={Y|N}
ODETTE protocol: Support of ODETTE special logic.
N - The remote site does not support special logic.
Y - The remote site supports special logic.
Default: N.
STOSR={S|R|B}
ODETTE protocol: ODETTE mode for the site.
S - SENDER mode only
R - RECEIVER mode only.
B - BOTH mode.
PeSIT Hors SIT or ETEBAC5 protocol:
R - REQUESTER mode (the local site always initiates the connection).
S - SERVER mode (the remote site always initiates the connection).
B - Mixed mode (both sites are authorized to establish the connection).
Default: B.
STOXST={Y|N}
ODETTE protocol: support of the RESTART function.
N - The site does not support the RESTART function.
Y - The site supports the RESTART function.
Default: Y.
SUBJCL=name
Prefix for the skeleton members used by the automatic JCL triggering
function for this site (see Section 2.11 of this guide).
This parameter can be overridden by the value of the same parameter in the
GENFILE macro.
Maximum length: six characters.
Default: no automatic JCL triggering.

TPNAME=name
In LU 6.2: transaction to be started when the site connection is established.
This parameter is mandatory if the remote site is not an IBM host.
The value has to be defined according to the remote site. If the remote
monitor is an Inter.Pel V6.x, three values are normalized:
PELCPICR for PEL protocol transfers.
PHDCPICR for PeSIT Hors-SIT D protocol transfers.
PHECPICR for PeSIT Hors-SIT E protocols transfers.
Maximum of 50 characters.
Default: not used.
YES - Mailbox records describing transfers with this site are sent to the
tracker every time their status changes.
NO - Nothing is sent to the tracker with this site.
SUM - Mailbox records describing transfers with this site are sent to the
tracker only when their status changes to 2, 4, 5, 6, 7, 9, A, C, I, N.
Default: value of this parameter in the PELPARMS file.
TRAILER={xx|Y|N}
Value of the character added by Inter.Pel to the end of each block transferred
over the network.
N - No trailer.
Y - Standard trailer (X'25').
XX - Specific trailer (two hexadecimal digits).
Default: N.
USRXTAB={DUMMY|name|STANDARD}
ODETTE, PeSIT Hors SIT and ETEBAC5 protocols: name of the
conversion table used with this site (maximum of eight characters). The
table used converts the contents of the file only; the protocol components are
converted using the table defined in the GENDEB macro-instruction.
This parameter can be overridden by the value of the same parameter in the
GENFILE macro.
STANDARD - Value of the GENDEB USRXTAB parameter.
DUMMY - No conversion.
name - Name of the user conversion table.
Default: STANDARD.
XUSER={Y|N}
Used in PEL protocol with PEL1 application only.
Transmit the identification of the user that created the request to the remote
site:
N - Do not transmit the identification.
Y - Transmit the identification.
Default: Y.

3.2.15 GENSSLDN CREATING A DISTINGUISHED NAME ALIAS
This macro is used to define aliases to retrieve distinguished names. This alias will then be
used in the ACAUTH, RCACERT, RUSCERT and USCERT parameters of the GENSSLP
macro. The NAME parameter of the GENSSLDN macro is used to define these parameters.
Note: this table is loaded above the 16M line.
GENSSLDN NAME=name (1)

,DN1=nnn
,TDN1=n
[,DN2=nnn]
[,DN3=nnn]
[,DN4=nnn]
[,DN5=nnn]
[,DN6=nnn]
[,DN7=nnn]
[,DN8=nnn]
[,DN9=nnn]
[,DN10=nnn]
[,DN11=nnn]
[,DN12=nnn]
[,DN13=nnn]
[,DN14=nnn]
[,DN15=nnn]
[,DN16=nnn]
[,DN2=t]
[,DN3=t]
[,DN4=t]
[,DN5=t]
[,DN6=t]
[,DN7=t]
[,DN8=t]
[,DN9=t]
[,DN10=t]
[,DN11=t]
[,DN12=t]
[,DN13=t]
[,DN14=t]
[,DN15=t]
[,DN16=t]
NAME=name
Distinguished name Id (alias).

DNx=nnn
Description of an element of the distinguished name. The type of this element
(1 to 7) is provided in the corresponding TDNx parameter.
Default: none.
TDNx=t
Type of the distinguished name element provided in the corresponding DNx
parameter. This type must correspond to the number used in the certificate.
Maximum length: one character (value between 1 and 7).
Default: none.
Note : common types of distinguished name elements are:

1 - symbol of the country.
2 - name of the city.
3 - region code.
4 - name of the company that owns this certificate.
5 - name of the division in the company that owns this certificate.
6 - name of the employee in the company that owns this certificate.
7 - e-mail address of the employee in the company that owns this
certificate.
Note: fields DN1 to DN7 are case-sensitive. They must be defined as they really are in the
distinguished name of the certificate. It is recommended that you define these macros in
separate members to keep other members CAPS ON
3.2.16 GENSSLP CREATE AN SSL SECURITY PROFILE
This macro is used to define an SSL security profile. This profile is linked to a site through the
GENSITE SSLPROF parameter that must refer to the NAME parameter of the associated
GENSSLP macro.
Note: this table is loaded above the 16M line.
GENSSLP NAME=name (1)

,AUTPOLC={1|2|3}
,AUTPOLS={1|2|3}
,CFSUITE=(cf1[,cf2])
,SSLALIAS=name
[,ACAUTH=(dn1[,dn2])]
[,CCHENAB={Y|N}]
[,EXTPKI={Y|N}]
[,PROTVERS={300|301}]
[,RCACERT=(dn1[,dn2])]
[,RUSCERT=(dn1[,dn2])]
[,USCERT=name]
[,USERDATA=nnnn]
NAME=name
Profile name.
Must be equal to the SSLPROF parameter of the associated GENSITEs.

ACAUTH=(dn1[,dn2])
List of authorities accepted by this security profile. This list refers to the
distinguished name defined in GENSSLDN macros. This parameter is not used
for client sites.
Maximum: eight names.
Default: none, mandatory parameter for server sites.
AUTPOLC={1|2|3}
Client authentication rule. Three possible values:
1 - anonymous client,
2 - client may be authenticated on server request,
3 - client must be authenticated.
Default: 1.
AUTPOLS={1|2|3}
Server authentication rule. Three possible values:
1 - anonymous server,
2 - server may be authenticated on client request,
3 - server must be authenticated.
Default: 2.
Authorized AUTPOLC et AUTPOLS configurations:

On client site: AUTPOLC=1, AUTPOLS=2
AUTPOLC=1, AUTPOLS=3
On server site: AUTPOLC=1, AUTPOLS=1
CCHENAB={Y|N}
Use cache session.
Cache keeps security parameters in memory and then avoids multiple execution
of handshake protocol when opening multiple session.
Inter.Pel only uses cache with FTP protocol.
Default: N.

CFSUITE=(cf1[,cf2])
List of supported cipher suites by decreasing encryption method preference.
Accepted values are:
1 - RSA authentication, no encryption, MD5 hashing
2 - RSA authentication, no encryption, SHA hashing
3 - RSA authentication, RC4 encryption, MD5 hashing
4 - RSA authentication, RC4 encryption, SHA hashing
5 - RSA authentication, DES encryption, SHA hashing
6 - RSA authentication, triple DES encryption, SHA hashing
7 - RSA authentication, AES encryption, SHA hashing
11 - RSA internal authentication, no encryption, MD5 hashing
12 - RSA internal authentication, no encryption, SHA hashing
13 - RSA internal authentication, RC4 encryption, MD5 hashing
14 - RSA internal authentication, RC4 encryption, SHA hashing
15 - RSA internal authentication, DES encryption, SHA hashing
16 - RSA internal authentication, triple DES encryption, SHA hashing
17 - RSA internal authentication, AES encryption, SHA hashing
The internal authentication mode allows processing of privacy and integrity
functions, without authentication and thus without X509 certificates. When this
mode is activated, an Inter.Pel internal private /public key pair is used to
process RSA encryption. The public key is transmitted to the remote site
without any certificate.
Parentheses may be omitted when only one cipher suite is defined.
Maximum: eight cipher suites.
EXTPKI={Y|N}
Activate external PKI. When set to YES, all the EXPKI*** exits are called.
Default: N, use Internal PKI.
PROTVERS={300|301}
SSL protocol version to be used.
Default: 301 (Version 3.01).
RCACERT=(ce1[,ce2])
List of authorities accepted in the certificate list received from the remote site.
This list refers to distinguished names defined in GENSSLDN macros.
Maximum: eight certificates.
Default: none, all the certificates contained in the local base are accepted.
RUSCERT=(ce1[,ce2])
List of user certificates accepted in the certificate list received from the remote
site. This list refers to distinguished names defined in GENSSLDN macros.
Maximum: eight certificates.
Default: none, all the user certificates contained in the local base are accepted.
SSLALIAS=name
Id of the X509 user certificate for this profile.
This Id is provided when creating the entry in the user certificate file
(GENDEB SSLDSNUS parameter).
Default: none.

USCERT=name
Name of the GENSSLDN macro describing the distinguished name of the
certificate associated with this profile (additional criteria used with SSLALIAS
parameter).
Default: none.
USERDATA=nnnn
Free user area. The value contained in this parameter area will be provided as
an input parameter at each call to an external PKI exit (EXPKI***).
Default: none.
3.2.17 GENTER - CREATING A TERMINAL CONTROL BLOCK
The GENTER macro-instruction defines a connection type.

It must immediately follow the GENLIGN macro-instruction to which it is attached or it must
immediately follow a GENPOINT macro-instruction pointing to the required GENLIGN
definition.
The line-handler (GENLIGN) to which a GENTER is attached must be stopped to

dynamically replace this GENTER.
NAME OPERATION OPERAND (S)
[label] GENTER [ACBIN=name]

[,ACBOUT=name]
[,ALTLOCN=name]
[,ALTPATH=name]
[,BIND=name]
[,CDH={Y|N}]
[,CHNASSY={Y|N}]
[,CRC={Y|N}]
[,DEFRESP={xx|NO|0}]
[,FPORT={Y|N}]]
[,HSIALIAS=xxxxxxxxxxxxxxxxxxxxxxxx]
[,HSIPROFI={D0,D1,D3,R0,R1,R3|NO}]
[,HSIPROFM={D0,D1,D3,R0,R1,R3|NO}]
[,HSIPROFO={D0,D1,D3,R0,R1,R3|NO}]
[,HSIPWDL=xxxxxxxx]
[,HSIPWDR=xxxxxxxx]
[,LOGMODE={name|NO|0}]
[,{LOGONF=llll|LOGONU=llll|LOGONS=llll}]
[,MULTI={Y|N}]
[,NUMBER=n]
[,PRIO=({h|0},{l|9})]
[,PROT={prot|PEL}]
[,PROTVERS={n|1]
[,PSWCHCK={(Y|N},{Y|N})]
[,RETRY=({m|10},{n|5})]
[,RTYMAX={n|0}]
[,SAFPROF=name]
[,SEG={Y|N}]
[,SESSON={n|0}]
[,SITNAME=name] (1)
[,SITSYN={n|0}]
[,SITNWD={n|0}]
[,SNGALT={Y|N}]
[,STYPE=type]

[,TABPFK=name]
[,TIMEOUT={nn|5}]
[,TRANS={YES|NO}]
[,TYPE={E|G|P|T|U}]
[,USERSR=name]
(1) Key used for a dynamic REPLACE, if static.
ACBIN=name
Only used if the previous GENLIGN definition type is STAT.
Name of the ACB used to receive calls from remote sites.
Not used if TYPE=G.
Default: not used.
ACBOUT=name
Name of the ACB used to call the remote sites.
Not used if TYPE=G.
Not used if PROT=PEL-S, FTP, ETEBAC3S or ODETTE-R.
Default: not used.
ALTLOCN=name
Local Inter.Pel name for the remote site.
PeSIT or ETEBAC5 protocols: site name used in the preconnect phase.
Default: GENDEB macro-instruction LOCNAME parameter.
ALTPATH=name
List of the LUs to be used if the LU specified in the label is not contacted
after the number of retries indicated in the RETRY parameter.
Three names can be given, for example: ALTPATH=(LU2,LU3,LU4)
(successive attempts will be made to contact LU-label, LU2, LU3, LU4, LU-
label, and so on).
Default: not used.
BIND=name
Name of the BIND transmitted by Inter.Pel. It is defined in a GENBIND
macro-instruction. Inter.Pel uses a default BIND if no BIND or LOGMODE
is specified.
Default: not used.
CDH={Y|N}
For SNA links: SNA CHANGE DIRECTION management.
Y - The SNA CHANGE DIRECTION is rigorously controlled. Exchanges
take place only in HALF-DUPLEX mode. This setting is mandatory
for AS400 connections and X.25 links via the X.25 ISA product.
Warning: if this setting is used with a PeSIT Hors SIT or ETEBAC5
protocol, the windows value for the synchronization points must be set
to 1 for a HALF-DUPLEX exchange.
N - Exchanges take place in FULL-DUPLEX mode.
For the TCP/IP access (STYPE=ITL, IIBM or IIB3), this parameter defines
how the length of the internal TCP/IP blocks is coded. This length is stored
in the two binary bytes with one of the following formats:
Y - (low order, high order), used by UNIX systems
N - (high order, low order), used by MVS systems
Default: N.

CHNASSY={Y|N}
Y - SNA chaining is accepted in receive mode.
N - SNA chaining is ignored in receive mode.
Default: N.
CRC={Y|N}
Y - A CRC is added to the end of the network block when transfers take
place. This function is only supported by the PESITHSE protocol and
some PEL connections.
N - No CRC is added to the end of the network block.
Default: N.
DEFRESP={xx|NO|0}
Number of blocks transmitted over the network before an SNA
DEFINITE-RESPONSE is requested.
0 - A DEFINITE-RESPONSE is requested for each block.
YES - A DEFINITE-RESPONSE is requested for each block.
NO - No DEFINITE-RESPONSE.
FF - No DEFINITE-RESPONSE.
xx - A DEFINITE-RESPONSE is requested after xx blocks.
Default: 0.
HSIALIAS={xxxxxx}
Ident (up to 24 characters) of the user X509 certificate used by the local site
for HSI exchanges with this line-handler.
Default: not used.
FPORT={Y|N}
Y - Use values defined in the GENLIGN PORTOUT and PORTOUT2
parameters to set the caller address in the FTP outgoing DATA
connections (PASV mode).
N - Let the system set the caller address in the FTP outgoing DATA
connections (PASV mode).
Default: N
HSIPROFI={D0,D1,D3,R0,R1,R3|NO}
Maximum HSI security level for incoming calls
D0 - Internal authentication, SHA integrity, no confidentiality.
D1 - Internal authentication, SHA integrity, DES confidentiality.
D3 - Internal authentication, SHA integrity, triple DES confidentiality.
R0 - Authentication using X509 certificates, SHA integrity, no
confidentiality.
R1 - Authentication using X509 certificates, SHA integrity, DES
confidentiality.
R3 - Authentication using X509 certificates, SHA integrity, triple DES
confidentiality.
NO - No security.
Default: NO.

HSIPROFM={D0,D1,D3,R0,R1,R3|NO}
Minimum HSI security level for incoming calls
confidentiality.
confidentiality.
confidentiality.
NO - No security.
Default: NO.
HSIPROFO={D0,D1,D3,R0,R1,R3|NO}
HSI security level used for outgoing calls
confidentiality.
confidentiality.
confidentiality.
NO - No security.
Default: NO.
HSIPWDL={xxx.xxx}
HSI password (up to 64 characters) used by the local site.
Default: no password used.
HSIPWDR={xxx.xxx}
HSI password (up to 64 characters) used by the remote site.
Default: no password used.
label =
Label specifying the LU associated with the remote site with which Inter.Pel
requests an outgoing connection.
If TYPE=G, label is the name of the MCH LU to be used.
If PROT=IPIS, this label indicates the ddname of the DD card in the
Inter.Pel startup JCL defining the message file associated with this link.
LOGMODE={name|NO|0}
Name of the LOGMODE to be used for the connection.
0 : Inter.Pel supplies the BIND.
NO : Inter.Pel does not supply the BIND or the LOGMODE.
Mandatory for LU 6.2.
Default: not used.

{LOGONF=llll|LOGONU=llll|LOGONS=llll}
LOGONF - Formatted LOGON. When the physical connection has been
established, the LOGON APPLID(llll) message is generated.
LOGONU - Unformatted LOGON. When the physical connection has
been established, the llll message is generated
LOGONS - Specific LOGON. When the physical connection has been
established, the message associated with the GENLOGON
macro-instruction specified is generated.
If no LOGON is specified, no message is generated.
This parameter is only used for STAT or DYN lines.
Default: not used.
MULTI={Y|N}
Y - The remote site supports multi-record FPDUs.
N - The remote site does not support multi- record FPDUs.
Used by the PeSIT Hors SIT and ETEBAC5 protocols.
Default: N.
NUMBER=n
When the previous GENLIGN definition type is CONSOLE, it represents
the maximum number of Inter.Pel consoles that can be activated at the same
time.
When the previous GENLIGN definition type is DYN, it represents the
number of transfers (transmit and receive) that can be activated at the same
time.
Default: none; mandatory if TYPE=DYN or CONSOLE.
PRIO=({h|0},{l|9})
H - 0 to 9 indicating the highest transfer priority level accepted by this
type of link
L - 0 to 9 indicating the lowest transfer priority level accepted by this type
of link
The priority is set in a transfer request parameter.
Default: (0,9).

PROT={prot|PEL}
Protocol used:
ETEBAC2N - BSC ETEBAC1/2 protocol
ETEBAC3E - ETEBAC3 sender protocol (the local site always
initiates the connection)
ETEBAC3S - ETEBAC3 server protocol (the remote site always
ETEBAC5 - ETEBAC5 protocol
FTP - FTP protocol
IPCICS - CICS coupling
IPIS - Inter.Set coupling
IPMQS - MQSeries (IBM) coupling
ISCMDTP - Subsystem to Inter.Pel interface
ISXFER - Inter.Pel to subsystem interface
ODETTE - ODETTE INITIATOR and RESPONDER protocol
ODETTE-I - ODETTE INITIATOR protocol (the local site always
ODETTE-R - ODETTE RESPONDER protocol (the remote site
always initiates the connection)
PEL - PEL server/requester protocol
PEL-D - PEL requester protocol (the local site always initiates
the connection)
PEL-HV - High-Value PEL protocol
PEL-S - PEL server protocol (the remote site always initiates the
connection)
PESITF - PeSIT SIT protocol
PESITHS - PeSIT Hors SIT protocol level D
PESITHSE - PeSIT Hors SIT protocol level E
LU 6.2 supports only the PEL, PEL-S, PEL-D, PEL-HV, PESITHS and
PEHITHSE protocols.
Default: PEL.
PROTVERS={n|1}
ETEBAC5 version associated at all the sites managed by this GENTER:
1 - ETEBAC5 version 1.3 protocol.
2 - ETEBAC5 version 2.1 protocol.
Default: 1.
PSWCHCK={(Y|N},{Y|N})
Used by the PEL protocol.
P1 = Y - The caller's password is checked (see menu 6.5).
N - The password is not checked.
P2 = Y - A password is supplied when Inter.Pel establishes a
connection with the site (see menu 6.5).
N - No password is supplied.
This parameter is ignored if the GENSAF parameter is coded for this
GENTER.
Default: (N,N).

RETRY=({m|10},{n|5})
Outgoing calls:
m: Number of retries. If no transfer has taken place after "m" attempts
and the ALTPATH parameter is not set, the site is disabled (m= 0: the
number of retries is unlimited).
n: Interval between two retries (expressed in minutes).
Incoming calls in PAD mode:
m: Number of consecutive errors after which the PEL480 message is sent
to the log.
n: Number of consecutive errors after which the connection is aborted.
Default: (10,5).
RTYMAX={n|0}
Number of automatic retries attempted by Inter.Pel after an abend.
Default: 0.
SAFPROF=name
Name of the security profile SAF (external security control) used for the
incoming calls. If this parameter is filled, Inter.Pel will automatically
execute access security controls defined in the GENSAF macro referenced
by this parameter using standard RACROUTE macro.
Default: No automatic control.
SEG={Y|N}
Y - The remote site supports record segmentation.
N - The remote site does not support record segmentation.
Used by the PESITHS and PESITHSE protocols.
Default: N.
SESSON={n|0}
Time-out, in minutes, before an inactive connection is released.
0 - Immediate release.
255 - No release.
In LU 6.2 mode, this parameter is not used in the PESITHS protocol.
Default: 0.
SITNAME=name
Used if the previous GENLIGN definition type is DYN, LU62 or STAT
Name of the remote site if the associated GENLIGN definition type is
STAT.
Name of the DUMMY site if the associated GENLIGN definition type is
DYN.
Key used for a dynamic REPLACE if TYPE = STAT.
Default: not used.
SITSYN={n|0}
Interval between synchronization points in Kbytes.
Used by the PESITF, PESITHS, and PESITHSE and ETEBAC5 protocols.
Default: 0 (no synchronization points).
SITWND={n|0}
Acknowledgment window for the synchronization points.
Used by the PESITF, PESITHS, and PESITHSE and ETEBAC5 protocols.
Must be between 0 and 5.
This parameter must be set to 0 or 1 in LU 6.2 mode.
Default: 0 (synchronization points are not acknowledged).

SNGALT={Y|N}
Y - once Inter.Pel switches to the ALTPATH, it returns to a systematic
retry phase for the LUOUT, that is, one time in two it will make a retry
to the primary LU before using the secondary LU if the former is still
not available. As a result, the line manager will automatically detect
the reactivation of the LUOUT and will therefore use it in priority as
soon as possible.
N - when the primary LU defined by the LUOUT parameter reaches its
maximum RETRY number, this LU is deactivated and Inter.Pel
switches definitively to the secondary LU defined by the ALTPATH
parameter. The only way to return to LUOUT is then to reinstall the
site in 6.6.
This feature is not available in native TCP/IP Interlink.
Default: N
STYPE=type
SUB-TYPE: AS400 - SNA link with an AS400
DPSGP - Link with a PAD handler DPS function
DPSHS - Link with a DPS7
E3270 - Link with an SNA PELIPC
PAD - Link with a PAD PELIPC, Version 1
PCPAD - Link with a PAD PELIPC, Version 2 and
later
S38EX - Link with a PELI38 (IBM SYSTEM 38)
ITL - Link with TCP/IP via the Interlink
SNS/TCPaccess product
IIBM - Link with TCP/IP via the IBM TCP/IP
product (Equivalent to IIB3)
IIB3 - Link with TCP/IP via the IBM TCP/IP
product,
Default: not used.
TABPFK=name
Only used if the previous GENLIGN definition type is CONSOLE.
Name of the reference table for the function keys defined in a GENPFK
macro-instruction.
Default: not used.
TIMEOUT={nn|5}
Time, in minutes, before a TIME-OUT is detected at network level.
For 3270 terminals (GENLIGN TYPE CONSOLE): maximum duration of
inactivity on a terminal. At the end of this maximum delay, if no data has
been received from the keyboard in Inter.Pel, the terminal manager ends the
session.
Default: 5 for transfer terminals, no time out for 3270 terminals.
TRANS={YES|NO}
Call to a CICS or IMS transaction at the end of a transfer (see the PEL -
PeSIT SIT Protocol Guide).
Default: NO.

TYPE={E|G|P|T|U}
Type of link.
E - Inter.Pel console.
G - GATE: uses the X25NPSI-GATE interface.
P - Non-GATE X.25 connections.
T - TCP/IP connections.
U - SNA connection.
Default: P.
USERSR=name
Name of the user routine that is activated for each VTAM send/receive (see
Default: not used.
Dynamic addition and replacement of GENTER definitions attached to a non-static

GENLIGN entry:
- ADD adds a number of terminals specified by the NUMBER parameter, the terminals
being identical to those already defined, without taking the other parameters into
account.
- REP replaces all terminals with the new parameters. The new number of terminals is the
value of the NUMBER parameter in the macro-instruction used in the REP command,
irrespective of the original number of terminals.

3.2.18 GENTRAN - CREATING THE TRANSACTION TABLE
This macro-instruction is designed to assign a security class to a transaction.
The maximum number of transactions that can be defined is specified in the GENDEB
MAXTRAN parameter.
label GENTRAN TRAN=name (1)

[,CLASS={n|1}]
CLASS={n|1}
Security class (1 to 9, in ascending order).
Default: 1.
TRAN=name
Name of an Inter.Pel transaction.
NOTE: the transaction list can be found in the sample environment table in the SAMPLIB
library ENVTAB member.

3.2.19 ASSIGNING GENTER ENTRIES AUTOMATICALLY
To simplify environment table definitions, pools of identical GENTER entries can be created,
with Inter.Pel using these entries according to the transfer requirements.
The GENTER macro-instruction NUMBER parameter indicates the number of GENTER

entries in the pool plus one (the GENTER profile is not used for transfers).
Each site (GENSITE) is associated with a GENLIGN entry, which controls a GENTER pool.
This association is created by the GENSITE macro-instruction LINGRP parameter.
The LUOUT parameter indicates the name of the network resource associated with the remote
site for sites initializing connections. If the NPSI GATE interface is used, the LUOUT
parameter indicates the name of the MCH to be used. If the TCP/IP interface is used, the
LUOUT parameter indicates the name of the TCP/IP manager to be used.
When incoming connections are requested, the remote site can be recognized in four ways:
- Via the GENSITE macro-instruction LUIN parameter
- Via X25TABLE for X.25 calls using the NPSI GATE
- Via IPTABLE for TCP/IP calls
- Via the protocol: in this case, the GENTER pool SITNAME parameter must begin
with DUMMYxx, and a GENSITE macro-instruction in which the SITNAME is
DUMMYxx must exist to give Inter.Pel the logical properties of the calling site
(GENTER and GENSITE profiles)
The number of GENTER entries in the pool may be less than the number of sites attached to it.

3.2.20 ORDER OF THE MACRO-INSTRUCTIONS
- The GENDEB macro-instruction must always be the first macro-instruction in the first
definition member.
- The GENEND macro-instruction must always be the last macro-instruction in the last
definition member.
- The GENTER macro-instructions must follow the GENLIGN macro-instruction to
which they are attached or a GENPOINT macro-instruction pointing to this entry.
- The GENLU macro-instructions must follow the GENMGER macro-instruction to
which they are attached or a GENPOINT macro-instruction pointing to this entry.

3.2.21 SAMPLE ENVIRONMENT TABLE
NOTE: the sample table can be found in the SAMPLIB library ENVTAB member.
TITLE '**** ENVIRONMENT TABLE ****'

PRINT NOGEN
*----------------------------------------------------------------------
* ENVIRONMENT TABLE SAMPLE :
* ==========================
*
* LOCAL SITE NAME : NTSS
*
* REMOTE SITES LIST :
*
*----------------------------------------------------------------------
* NAME * TYPE * NETWORK * PROTOCOL * REMOTE PRODUCT TYPE
*----------------------------------------------------------------------
* NICE * HOMOGEN. * SNA * PRIVATE * INTERPEL MVS
* NICE1 * HETEROG. * SNA * PEL-HV * INTERPEL MVS
* METZ * HOMOGEN. * SNA * PRIVATE * INTERPEL MVS
* METZ1 * HETEROG. * SNA * PEL-HV * INTERPEL MVS
* SITE001 * HETEROG. * X25-PCNE * PEL * PELIPC X25
* SITE005 * HETEROG. * X25-PCNE * PEL * PELIVAX
* SITE010 * HETEROG. * X25-PCNE * PEL-S * PELI88 (BULL DPS8 AX25)
* SITE015 * HETEROG. * X25-PCNE * PEL-D * PELIPC X25
* SITE020 * HETEROG. * X25-PCNE * PEL-D * INTERPEL MVS
* SITE025 * HETEROG. * X25-GATE * PEL * PELIVSE
* SITE030 * HETEROG. * X25-GATE * PEL * PELI77 (BULL DPS7 AX25)
* SITE031 * HETEROG. * X25-GATE * PEL * PELIBUR (BURR. CP9500)
* SITE035 * HETEROG. * X25-GATE * PEL-S * PELIPC X25
* SITE040 * HETEROG. * X25-GATE * PEL-D * PELIPC X25
* SITE045 * HETEROG. * X25-GATE * PEL-D * PELIPC X25
* SITE050 * HETEROG. * SNA LU2 * PEL-S * PELIPC SNA
* SITE065 * HETEROG. * X25-PCNE * PEL-S * PELIPC PAD
* SITE085 * HETEROG. * X25-PCNE * ETEBAC3E * ANY
* SITE090 * HETEROG. * X25-GATE * ETEBAC3E * ANY
* SITE095 * HETEROG. * X25-GATE * ETEBAC3S * ANY
* SITE100 * HETEROG. * X25-GATE * ETEBAC3S * ANY
* SITE105 * HETEROG. * X25-GATE * PESITHS * ANY
* SITE110 * HETEROG. * X25-GATE * PESITHS * ANY
* SITE115 * HETEROG. * SNA/SNI * PESITHS * ANY
* SITE120 * HETEROG. * X25-GATE * PESITF * SIT STATION
* SITE125 * HETEROG. * X25-GATE * PESITF * SIT STATION
* SITE130 * HETEROG. * X25-GATE * PESITF * LOCAL LOGICAL SITE
* SITE135 * HETEROG. * X25-GATE * PESITF * LOCAL LOGICAL SITE
* ODETTE1 * HETEROG. * X25-GATE * ODETTE * ANY
* ODETTE2 HETEROG. * X25-GATE * ODETTE-R * ANY
* SITE140 * HETEROG. * BSC2 * ETEBAC2N * ANY
* SITE185 * HETEROG. * SNA LU2 * PEL-S * PELI38 ( IBM S38 )
* SITE190 * HETEROG. * SNA LU2 * PEL-S * PELI38 ( IBM S38 )

* SITE195 * HETEROG. * X25-GATE * PEL-S * PELI77 (BULL DPS7 QMON)
* SITE206 * HETEROG. * X25-GATE * PEL-S * ANY CONNECT. TO SITE205
* SITE207 * HETEROG. * X25-GATE * PEL-S * ANY CONNECT. TO SITE205
* LDIFF1 * LISTE DE DIFFUSION 1
* LDIFF2 * LISTE DE DIFFUSION 2
*
*----------------------------------------------------------------------
*
ENVTAB GENDEB DEFJBN=PELCPTR,
DEFNTF=NNNN, TSU NOTIFIE (PEL2) CP. RENDUS
INDXR=INDXR, MAXIMUM 7 CARACTERES
LANG=ENGL,
MBRJBR=RPTPEL2,
MBRUTIL=PEL2UTI,
ODTLV=1,
REPLY=Y,
STAT=Y,
SUBJBR=Y,
TABROUT=RTGTAB,
TASKNUM=20,
TIMER=10
*----------------------------------------------------------------------
* HOMOGENEOUS MVS-MVS CONNECTIONS
*----------------------------------------------------------------------
GENMGER NAME=PELICAN2,ACBNAME=APPNTSS
GENLU LUNAME=APPLNICE,ACQ=A,NUMFILE=2,DEST=NICE,
BLOCK=3500,VTAMARL=3500,HSO=Y,RTME=10
GENLU LUNAME=APPLMETZ,ACQ=A,NUMFILE=2,DEST=METZ,
BLOCK=3500,VTAMARL=3500,HSO=Y,RTME=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL PROTOCOL, X25-PCNE
* 8 SIMULTANEOUS TRANSFERS MAXIMUM.
*----------------------------------------------------------------------
STARTER1 GENLIGN TYPE=DYN,ACBNAME=ACBPCNE
*
GENTER TYPE=P,SITNAME=DUMMYPCNE,
RETRY=(10,3),PROT=PEL,NUMBER=8
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL SERVER PROTOCOL, X25-PCNE
*----------------------------------------------------------------------
STARTER2 GENLIGN TYPE=DYN,ACBNAME=ACBPCNES
*
PROT=PEL-S,NUMBER=6
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL REQUESTER PROTOCOL, X25-PCNE
*----------------------------------------------------------------------
STARTER3 GENLIGN TYPE=DYN,ACBNAME=ACBPCNED
*
RETRY=(10,3),PROT=PEL-D,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL PROTOCOL, X25-GATE

*----------------------------------------------------------------------
STARTER4 GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYGATE,
RETRY=(10,3),PROT=PEL,NUMBER=8
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL SERVER PROTOCOL, X25-GATE
*----------------------------------------------------------------------
*
PROT=PEL-S,NUMBER=6
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL REQUESTER PROTOCOL, X25-GATE
*----------------------------------------------------------------------
*
RETRY=(10,3),PROT=PEL-D,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL-HV PROTOCOL, SNA
*----------------------------------------------------------------------
STARTER7 GENLIGN TYPE=DYN,ACBNAME=ACBPELHV,LOCK=Y
*
GENTER TYPE=U,SITNAME=DUMMYHV,
RETRY=(10,3),PROT=PEL-HV,DEFRESP=NO,BIND=BIND3850,
CHNASSY=YES,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL-S PROTOCOL, PELIPC SNA
*----------------------------------------------------------------------
STARTER8 GENLIGN TYPE=DYN,ACBNAME=ACBPCSNA
*
GENTER TYPE=U,SITNAME=DUMMYSNA,
STYPE=E3270,PROT=PEL-S,LOGMODE=D4C32782,DEFRESP=NO,
NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL-S PROTOCOL, PELIPC PAD
* ( X25-PCNE )
*----------------------------------------------------------------------
STARTER9 GENLIGN TYPE=DYN,ACBNAME=ACBPCPAD
*
GENTER TYPE=P,SITNAME=DUMMYPAD,
STYPE=PCPAD,PROT=PEL-S,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH ETEBAC3E PROTOCOL, X25-PCNE
*----------------------------------------------------------------------
STARTERA GENLIGN TYPE=DYN,ACBNAME=ACBTBACE
*
GENTER TYPE=P,SITNAME=DUMMYTBE,
RETRY=(10,3),PROT=ETEBAC3E,NUMBER=10
*----------------------------------------------------------------------

* HETEROGENEOUS CONNECTIONS WITH ETEBAC3E PROTOCOL, X25-GATE
*----------------------------------------------------------------------
STARTERB GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYTBE,
RETRY=(10,3),PROT=ETEBAC3E,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH ETEBAC3S PROTOCOL, X25-GATE
*----------------------------------------------------------------------
STARTERC GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYTBS,
PROT=ETEBAC3S,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PESITHS PROTOCOL, X25-GATE
*----------------------------------------------------------------------
STARTERD GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYHS,
PROT=PESITHS,RETRY=(10,3),
SEG=Y,MULTI=Y,SITSYN=100,SITWND=4,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PESITHS PROTOCOL, SNA
*----------------------------------------------------------------------
STARTERE GENLIGN TYPE=DYN,ACBNAME=ACBSIT
*
GENTER TYPE=P,SITNAME=DUMMYHS,
PROT=PESITHS,RETRY=(10,3),
SEG=Y,MULTI=Y,SITSYN=100,SITWND=4,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PESITF PROTOCOL, X25-GATE
*----------------------------------------------------------------------
STARTERF GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYSIT,
PROT=PESITF,RETRY=(10,3),
SITSYN=100,SITWND=4,NUMBER=10
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH FULL ODETTE PROTOCOL, X25-GATE
*----------------------------------------------------------------------
STARTERG GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYO,
PROT=ODETTE,RETRY=(10,3),NUMBER=16
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH ODETTE-R PROTOCOL, X25-GATE
*----------------------------------------------------------------------
STARTERH GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYO,
PROT=ODETTE-R,NUMBER=6

*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH ETEBAC2N PROTOCOL, BSC
*----------------------------------------------------------------------
STARTERI GENLIGN TYPE=STAT
*
LINE01 GENTER TYPE=P,SITNAME=DUMMYT2,
PROT=ETEBAC2N
LINE02 GENTER TYPE=P,SITNAME=DUMMYT3,
PROT=ETEBAC2N
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL-S PROTOCOL, SNA LU2 FOR
* PELI38 ( IBM S38 ), 6 SIMULTANEOUS TRANSFERS MAXIMUM.
*----------------------------------------------------------------------
STARTERK GENLIGN TYPE=DYN
*
GENTER TYPE=U,SITNAME=DUMMYS38,
PROT=PEL-S,STYPE=S38EX,
DEFRESP=10,BIND=BINDS38,NUMBER=6
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL-S PROTOCOL, X25-GATE FOR
* PELI77 ( BULL DPS7 QMON ), 6 SIMULTANEOUS TRANSFERS MAXIMUM.
*----------------------------------------------------------------------
STARTERL GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYP77,
PROT=PEL-S,STYPE=DPSHS,RETRY=(10,3),NUMBER=6
*----------------------------------------------------------------------
* HETEROGENEOUS CONNECTIONS WITH PEL-S PROTOCOL, X25-GATE FOR
* PELI88 ( BULL DPS8 QMON ), 6 SIMULTANEOUS TRANSFERS MAXIMUM.
*----------------------------------------------------------------------
STARTERM GENLIGN TYPE=DYN
*
GENTER TYPE=G,SITNAME=DUMMYP88,
PROT=PEL-S,STYPE=DPSGP,RETRY=(10,3),NUMBER=6
*----------------------------------------------------------------------
* ETEBAC5 CONNECTIONS, X25-GATE ; 6 SIMULTANEOUS TRANSFER MAXIMUM
* WAIT 2 MINUTES BEFORE RELEASING PROTOCOL CONNECTION
* SYNC POINT EVERY 20 KBYTES, ACQ EVERY 2 SYNC POINTS
* SEGMENTATION AND MULTIPLE ITEMS SUPPORTED
*----------------------------------------------------------------------
STARTERN GENLIGN TYPE=DYN,LOCK=O
GENTER TYPE=G,SITENAME=DUMMYHE5,
PROT=ETEBAC5,NUMBER=8,SESSON=2,
SITSYN=20,SITWND=2,DEFRESP=NO,SEG=Y,MULTI=Y
*----------------------------------------------------------------------
* MCH DEFINITION : LUMCH01, 20 CVC'S MAX
*----------------------------------------------------------------------
LUMCH01 GENLIGN TYPE=MCH,ACBNAME=ACBMCH1,CVCNB=20
*----------------------------------------------------------------------
* MCH DEFINITION : LUMCH02, 10 CVC'S MAX
*----------------------------------------------------------------------
LUMCH02 GENLIGN TYPE=MCH,ACBNAME=ACBMCH2,CVCNB=10
*----------------------------------------------------------------------
* DEFINITION FOR INTERPEL CONSOLES HANDLING (15 MAXIMUM)
*----------------------------------------------------------------------
LIGN3270 GENLIGN TYPE=CONSOLE,ACBNAME=ACBOPER
GENTER TYPE=E,NUMBER=15,TABPFK=TAB3270

*----------------------------------------------------------------------
* DEFINITION OF PFK TABLE FOR INTERPEL CONSOLES.
*----------------------------------------------------------------------
GENPFK PF1=PELMXDOP, OPERATORS COMMANDS HELP
PF2=PELMXLSI, REMOTE SITES LIST
PF3=PELM1, INTERPEL 'PRIMARY OPTION MENU'
PF4=PELMXSCM, 'VTAM COMMANDS' MENU
PF5=PELM122, 'TRANSFERS MONITORING' MENU
PF6=PELM145, 'LOG FILES DISPLAY' MENU
AP2=PELMXDOP,AP1=PELM1,NAME=TAB3270
*----------------------------------------------------------------------
* BINDS DEFINITIONS
*----------------------------------------------------------------------
*-------- NETWORK MAXDATA 512 BYTES
GENBIND NAME=BINDS38,
VALUE='010303B19030800001C8C8010001000000E1'
*-------- NETWORK MAXDATA 4K BYTES
GENBIND NAME=BIND3850,
VALUE='010303B1B130800107898901070000000000'
*----------------------------------------------------------------------
* LOGON DEFINITIONS
*----------------------------------------------------------------------
*-------- LOGON USED WITH PELIBUR ( BURROUGHT CP9000 )
GENLOGON NAME=LOGBUR,VALUE=X'FE524E2050454C49'
*-------- LOGON USED WITH PELI77 OR PELI88
GENLOGON NAME=LDPS7,VALUE=X'E2E2D3C24040404025'
*----------------------------------------------------------------------
* REMOTE SITES DEFINITIONS
*
* SITES USING PEL PROTOCOL WITH X25-PCNE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYPCNE,GROUP=GROUPE1,BUFSIZE=2540,ISTATUS=ACT
GENSITE NAME=SITE001,GROUP=GROUPE1,BUFSIZE=2540,FILESIZ=R,
LINGRP=STARTER1,LUIN=SWLU02,LUOUT=SWLU01,ISTATUS=ACT,
TRAILER=N,COMPACT=YESN
GENSITE NAME=SITE005,GROUP=GROUPE1,BUFSIZE=2540,ISTATUS=ACT,
LINGRP=STARTER1,LUIN=SWLU04,LUOUT=SWLU03,
*----------------------------------------------------------------------
* SITES USING PEL SERVER PROTOCOL WITH X25-PCNE
*----------------------------------------------------------------------
LINGRP=STARTER2,LUIN=SWLU05,
*----------------------------------------------------------------------
* SITES USING PEL REQUESTER PROTOCOL WITH X25-PCNE
*----------------------------------------------------------------------
LINGRP=STARTER3,LUOUT=SWLU06,
LINGRP=STARTER3,LUOUT=SWLU07,
*----------------------------------------------------------------------
* SITES USING PEL PROTOCOL WITH X25-GATE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYGATE,GROUP=GROUPE1,BUFSIZE=2540,ISTATUS=ACT
GENSITE NAME=SITE025,GROUP=GROUPE1,BUFSIZE=3000,

ISTATUS=ACT,LOGONF=ACBR001,
LINGRP=STARTER4,LUOUT=MCH01,ALTPATH=MCH02,
ISTATUS=ACT,LOGONS=LDPS7,
LINGRP=STARTER4,LUOUT=MCH02,
ISTATUS=ACT,LOGONS=LOGBUR,ACQ=05,
*----------------------------------------------------------------------
* SITES USING PEL SERVER PROTOCOL WITH X25-GATE
*----------------------------------------------------------------------
LINGRP=STARTER5,TRAILER=N,COMPACT=YESN
*----------------------------------------------------------------------
* SITES USING PEL REQUESTER PROTOCOL WITH X25-GATE
*----------------------------------------------------------------------
LINGRP=STARTER6,LUOUT=MCH02,ALTPATH=MCH01,RETRY=(2,3),
*----------------------------------------------------------------------
* SITES USING PEL-HV PROTOCOL WITH SNA
*----------------------------------------------------------------------
GENSITE NAME=DUMMYHV,GROUP=GROUPEN,BUFSIZE=16384,ISTATUS=ACT,
GENSITE NAME=NTSS1,GROUP=GROUPEN
GENSITE NAME=NICE,GROUP=GROUPEN
GENSITE NAME=NICE1,GROUP=GROUPEN,BUFSIZE=16384,ISTATUS=ACT,
LINGRP=STARTER7,LUOUT=ACBNICE1,LUIN=ACBNICE1,
TRAILER=N,COMPACT=NO,MAXCON=3
GENSITE NAME=METZ,GROUP=GROUPEN
GENSITE NAME=METZ1,GROUP=GROUPEN,BUFSIZE=16384,ISTATUS=ACT,
LINGRP=STARTER7,LUOUT=ACBMETZ1,LUIN=ACBMETZ1,
TRAILER=N,COMPACT=NO,MAXCON=4
*----------------------------------------------------------------------
* SITES USING PELIPC-SNA AND PEL-S PROTOCOL WITH SNA
*----------------------------------------------------------------------
GENSITE NAME=DUMMYSNA,GROUP=GROUPE4,BUFSIZE=2540,
ISTATUS=ACT,LINGRP=STARTER8
ISTATUS=ACT,LINGRP=STARTER8,COMPACT=YESN
*----------------------------------------------------------------------
* SITES USING PELIPC-PAD AND PEL-S PROTOCOL WITH X25-PCNE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYPAD,GROUP=GROUPE4,BUFSIZE=2000,
ISTATUS=ACT,LINGRP=STARTER9

*----------------------------------------------------------------------
* SITES USING ETEBAC3 REQUESTER PROTOCOL WITH X25-PCNE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYTBE,GROUP=GROUPE4,BUFSIZE=1000,ISTATUS=ACT
ISTATUS=ACT,LINGRP=STARTERA,RETRY=(5,3),
LUOUT=SWLU08,TRAILER=N
*----------------------------------------------------------------------
* SITES USING ETEBAC3 REQUESTER PROTOCOL WITH X25-GATE
*----------------------------------------------------------------------
ISTATUS=ACT,LINGRP=STARTERB,RETRY=(5,3),
LUOUT=MCH01,TRAILER=N
*----------------------------------------------------------------------
* SITES USING ETEBAC3 SERVER PROTOCOL WITH X25-GATE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYTBS,GROUP=GROUPE4,BUFSIZE=1000,ISTATUS=ACT
ISTATUS=ACT,LINGRP=STARTERC,TRAILER=N
ISTATUS=ACT,LINGRP=STARTERC,TRAILER=N
*----------------------------------------------------------------------
* SITES USING PESIT 'HORS SIT' PROTOCOL WITH X25-GATE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYHS,GROUP=GROUPE5,BUFSIZE=3000,ISTATUS=ACT
ISTATUS=ACT,LINGRP=STARTERD,TRAILER=N,MAXCON=3,
LUOUT=MCH01,ALTPATH=MCH02,FILESIZ=R,ALTLOCN=TEST1,
RETRY=(10,5)
ISTATUS=ACT,LINGRP=STARTERD,TRAILER=N,MAXCON=3,
LUOUT=MCH01,ALTPATH=MCH02,FILESIZ=R,ALTLOCN=TEST1
*----------------------------------------------------------------------
* SITES USING PESIT 'HORS SIT' PROTOCOL WITH SNA
*----------------------------------------------------------------------
ISTATUS=ACT,LINGRP=STARTERE,TRAILER=N,MAXCON=3,
ALTLOCN=TEST1,RETRY=(10,5),
LUOUT=ASITE23,LUIN=ASITE23
* SITE LOGIQUE LOCAL
GENSITE NAME=TEST1,GROUP=GROUPE5,BUFSIZE=3000,
ISTATUS=ACT,LINGRP=STARTERE,TRAILER=N
*----------------------------------------------------------------------
* SITES USING PESIT 'SIT' PROTOCOL WITH X25 GATE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYSIT,GROUP=GROUPE5,BUFSIZE=3000,
ISTATUS=ACT,LINGRP=STARTERF
*------- SIT STATION IDENTIFICATION
ISTATUS=ACT,LINGRP=STARTERF,TRAILER=N,ALTPATH=MCH02,
LUOUT=MCH03,MAXCON=3,SITTYP=IR,SITNUM=02,RETRY=(10,5)
ISTATUS=ACT,LINGRP=STARTERF,TRAILER=N,ALTPATH=MCH02,
LUOUT=MCH03,MAXCON=3,SITTYP=IE,SITNUM=03,RETRY=(10,5)
*------- INTERPEL IDENTIFICATION FOR THE STATION

ISTATUS=ACT,LINGRP=STARTERF,TRAILER=N,
SITTYP=CTE,SITNUM=53
ISTATUS=ACT,LINGRP=STARTERF,TRAILER=N,
SITTYP=CTR,SITNUM=53
*----------------------------------------------------------------------
* SITES USING ODETTE INITIATOR / RESPONDER PROTOCOL WITH X25 GATE
*----------------------------------------------------------------------
GENSITE NAME=DUMMYO,GROUP=GROUPE6,TRAILER=N,BUFSIZE=2800,
ISTATUS=ACT
GENSITE NAME=ODETTE,GROUP=GROUPE6,TRAILER=N,BUFSIZE=2800,
ISTATUS=ACT,STOOID=O,
STOICD=0931,STOORGC='ODETTE-FTP',STOCSA='FTP001'
GENSITE NAME=ODETTE1,GROUP=GROUPE6,TRAILER=N,BUFSIZE=2800,
LINGRP=STARTERG,ISTATUS=ACT,ACQ=07,COMPACT=YES,
LUOUT=MCH01,MAXCON=3,ALTLOCN=ODETTE,FILESIZ=R,
STOOID=O,STOICD=0111,STOORGC='552139305',STOCSA='ODT111'
*----------------------------------------------------------------------
* SITES USING ODETTE RESPONDER PROTOCOL WITH X25 GATE
*----------------------------------------------------------------------
GENSITE NAME=ODETTE2,GROUP=GROUPE6,TRAILER=N,BUFSIZE=3000,
LINGRP=STARTERG,ISTATUS=ACT,ACQ=10,COMPACT=YES,
ALTLOCN=ODETTE,FILESIZ=R,
STOOID=O,STOICD=0222,STOORGC='662139305',STOCSA='ODT222'
*----------------------------------------------------------------------
* SITES USING ETEBAC1/2 BSC PROTOCOL
*----------------------------------------------------------------------
GENSITE NAME=DUMMYT1,GROUP=GROUPE6,TRAILER=N,BUFSIZE=2800,
ISTATUS=ACT
ISTATUS=ACT
ISTATUS=ACT
GENSITE NAME=SITE140,GROUP=GROUPE6,TRAILER=N,BUFSIZE=3000,
ISTATUS=ACT
ISTATUS=ACT
ISTATUS=ACT
*----------------------------------------------------------------------
* SITES USING PEL SERVER PROTOCOL WITH SNA LU2 ( S38 )
*----------------------------------------------------------------------
GENSITE NAME=DUMMYS38,GROUP=GROUPE7,TRAILER=N,BUFSIZE=4000,
ISTATUS=ACT,LINGRP=STARTERK
ISTATUS=ACT,LINGRP=STARTERK,FILESIZ=R
ISTATUS=ACT,LINGRP=STARTERK,FILESIZ=R
*----------------------------------------------------------------------
* SITES USING PEL SERVER PROTOCOL WITH X25-GATE ( PELI77 QMON )
*----------------------------------------------------------------------
GENSITE NAME=DUMMYP77,GROUP=GROUPE1,BUFSIZE=2540,
ISTATUS=ACT,LINGRP=STARTERL
ISTATUS=ACT,LINGRP=STARTERL,FILESIZ=R
*----------------------------------------------------------------------

* SITES USING PEL SERVER PROTOCOL WITH X25-GATE ( PELI88 QMON )
*----------------------------------------------------------------------
GENSITE NAME=DUMMYP88,GROUP=GROUPE1,BUFSIZE=2540,
ISTATUS=ACT,LINGRP=STARTERL
*------- SITE SITE205 IS ALSO WORKING FOR SITE206, SITE207 AND SITE208
GENSITE NAME=SITE205,GROUP=GROUPE1,BUFSIZE=2540,CENTRAL=YES
*---------------------------------------------------------------------
* DUMMY SITE FOR ETEBAC5
*---------------------------------------------------------------------
GENSITE NAME=DUMMYHE5,GROUP=ETE5,
TRAILER=N,LINGRP=STARTER5,
ISTATUS=ACT,BUFSIZE=8192
*---------------------------------------------------------------------
* ETEBAC5 CUSTOMER SITE AS DEFINED IN BANK
*---------------------------------------------------------------------
GENSITE NAME=CLIENT1,GROUP=ETE5,BUFSIZE=8192,TRAILER=N,
LINGRP=STARTERN,MAXCON=4,ISTATUS=ACT,
LUOUT=LUXPCH,ALTLOCN=ID1,
STOSR=S,ET5TID=ZZZ,ET5CID=254829,
SECAUTH=1,
SECSEAL=U,
SECCIPH=U,
SECSIGN=U
*---------------------------------------------------------------------
* ETEBAC5 CUSTOMER USING PRESTATAIRE SITE AS DEFINED IN BANK
*---------------------------------------------------------------------
GENSITE NAME=CLIENT2,GROUP=ETE5,
TRAILER=N,BUFSIZE=2048,
LINGRP=STARTERN,MAXCON=4,
ISTATUS=ACT,LUOUT=LUXPCH,
ALTLOCN=ID2,STOSR=S,
ET5TID=ZZZ,ET5CID=437228,ET5PST=PRESTA1
SECAUTH=2,
SECSEAL=U,
SECCIPH=U,
SECSIGN=U
GENSITE NAME=PRESTA1,GROUP=ETE5,
LUOUT=LUXPCH,ALTLOCN=PST1,
STOSR=S,ET5TID=ZZZ,ET5CID=5178951
*---------------------------------------------------------------------
* ETEBAC5 BANK SITES DEFINED IN BANK
*---------------------------------------------------------------------
GENSITE NAME=BANK1,GROUP=ETE5,
ET5CID=951357,ET5TID=ZZZ,
ET5PST=ATELIER
GENSITE NAME=ATELIER,GROUP=ETE5,

ET5CID=852654,ET5TID=ZZZ
*---------------------------------------------------------------------
* ETEBAC5 BANK SITE AS DEFINED AT THE CUSTOMER
*---------------------------------------------------------------------
GENSITE NAME=BANQA,GROUP=ETE5,BUFSIZE=8192,TRAILER=N,
LUOUT=LUXPCH,ALTLOCN=B1,
STOSR=S,ET5TID=ZZZ,ET5CID=147254829,
SECAUTH=1,
SECSEAL=RSA,
SECCIPH=RSA,
SECSIGN=1
*---------------------------------------------------------------------
* ETEBAC5 BANK USING PRESTATAIRE SITE AS DEFINED AT THE CUSTOMER
*---------------------------------------------------------------------
GENSITE NAME=BANQB,GROUP=ETE5,BUFSIZE=2048,TRAILER=N,
LINGRP=STARTERN,MAXCON=4,
ISTATUS=ACT,LUOUT=LUXPCH,
ALTLOCN=ID2,STOSR=R,
ET5TID=ZZZ,ET5CID=65437228,ET5PST=ATELA
SECAUTH=2,
SECSEAL=RSA,
SECCIPH=NO,
SECSIGN=NO
GENSITE NAME=ATELA,GROUP=ETE5,BUFSIZE=2048,TRAILER=N,
LUOUT=LUXPCH,ALTLOCN=ATE1,
STOSR=R,ET5TID=ZZZ,ET5CID=5178951
*---------------------------------------------------------------------
* ETEBAC5 BANK SITES DEFINED IN BANK
*---------------------------------------------------------------------
GENSITE NAME=CLIENTA,GROUP=ETE5,BUFSIZE=2048,TRAILER=N,
ET5CID=951357,ET5TID=ZZZ,ET5PST=PRESTAA
GENSITE NAME=PRESTAA,GROUP=ETE5,BUFSIZE=2048,TRAILER=N,
ET5CID=852654,ET5TID=ZZZ
*---------------------------------------------------------------------
* DIFFUSION LIST DEFINITIONS
*---------------------------------------------------------------------
GENSITE NAME=LDIFF1,GROUP=GROUPE1
GENSITE NAME=LDIFF2,GROUP=GROUPE2
*---------------------------------------------------------------------
* 'CENTRAL' SITES DEFINITIONS
*---------------------------------------------------------------------
GENCENT NAME=SITE205,SITE=(SITE205,SITE206,SITE207,SITE208)
*---------------------------------------------------------------------
* APPLICATIONS DEFINITIONS OF GROUP : GROUPE1
*---------------------------------------------------------------------
GENFILE GROUP=GROUPE1,APPL=ODC,
LRECL=240,BLKSIZE=2400,RECFM=FB,
VERMONT=YES,POSMONT=228,LENMONT=12,TYPMONT=E,CODMONT=04,
VERSEQ=YES,COMP=TYPE2
GENFILE GROUP=GROUPE1,APPL=FB80,
LRECL=80,BLKSIZE=AUTO,RECFM=FB,RMODEL=MODEL1
GENFILE GROUP=GROUPE1,APPL=VS,
LRECL=1000,BLKSIZE=AUTO,RECFM=VB
*---------------------------------------------------------------------

*---------------------------------------------------------------------
GENFILE GROUP=GROUPE2,APPL=ODC,
LRECL=240,BLKSIZE=2400,RECFM=FB,
VERMONT=YES,POSMONT=228,LENMONT=12,TYPMONT=E,CODMONT=04,
VERSEQ=YES,COMP=TYPE2
GENFILE GROUP=GROUPE2,APPL=FBM,
LRECL=251,BLKSIZE=AUTO,RECFM=FB
GENFILE GROUP=GROUPE2,APPL=IMP,
LRECL=133,BLKSIZE=AUTO,RECFM=FBM
GENFILE GROUP=GROUPE2,APPL=FACT,
LRECL=80,BLKSIZE=AUTO,RECFM=FBA
GENFILE GROUP=GROUPE2,APPL=SARE,
*---------------------------------------------------------------------
*---------------------------------------------------------------------
GENFILE GROUP=GROUPE4,APPL=SAP,
*---------------------------------------------------------------------
*---------------------------------------------------------------------
*---------------------------------------------------------------------
*---------------------------------------------------------------------
GENFILE GROUP=GROUPE6,APPL=PRT,
USRXTAB=ODETAB1,
GENFILE GROUP=GROUPE6,APPL=VARB,
GENFILE GROUP=GROUPE6,APPL=TEXT,TEXT=Y,
LRECL=0,BLKSIZE=2052,RECFM=U
GENFILE GROUP=GROUPE6,APPL=UNDF,
LRECL=0,BLKSIZE=32760,RECFM=U
GENFILE GROUP=GROUPE6,APPL=XLOD,
USRXTAB=DUMMY,
LRECL=0,BLKSIZE=AUTO,RECFM=U
GENFILE GROUP=GROUPE6,APPL=PEL1,
*---------------------------------------------------------------------
*---------------------------------------------------------------------
*---------------------------------------------------------------------
* APPLICATIONS DEFINITIONS OF GROUP : GROUPEN
*---------------------------------------------------------------------
GENFILE GROUP=GROUPE7,APPL=PEL1,

*---------------------------------------------------------------------
* APPLICATIONS DEFINITIONS OF GROUP : SIT
*---------------------------------------------------------------------
GENFILE GROUP=SIT,APPL=PEL1,
*---------------------------------------------------------------------
* APPLICATIONS DEFINITIONS USING GENDSN FACILITY
*---------------------------------------------------------------------
GENFILE GROUP=GROUPE1,APPL=AIND,
LRECL=80,BLKSIZE=0,RECFM=FB,RDSN=INDX
GENFILE GROUP=GROUPE1,APPL=ASMS,
LRECL=80,BLKSIZE=0,RECFM=FB,RDSN=SMS
GENFILE GROUP=GROUPE1,APPL=AGDG,
LRECL=80,BLKSIZE=0,RECFM=FB,RDSN=GDG
GENFILE GROUP=GROUPE1,APPL=AMSG,
LRECL=80,BLKSIZE=0,RECFM=FB,RDSN=MSG
GENFILE GROUP=GROUPE1,APPL=AIND,
LRECL=80,BLKSIZE=0,RECFM=FB,RDSN=INDX
GENDSN NAME=INDX,DISP=BOTH,ACT=DELETE,
DSN=&INDXR..&ORIG..&DEST..&APPL
GENDSN NAME=SMS,
DSN=PELSMS.&APPL..&ORIG..T&HH..M&MIN..S&SS
GENDSN NAME=GDG,ACT=ERASE,
DSN='PELSYS.XFER.DSN.GDG1(+1)'
GENDSN NAME=MSG,ACT=ERASE,
DSN='&INDXR..&ORIG..&DEST..&SUBSTR(39:4,&MSG)'
*
TITLE '*** INTERPEL TRANSACTIONS AND MENUS ***'
*---------------------------------------------------------------------*
* *
* INTERPEL TRANSACTIONS SAMPLE TABLE *
* *
*---------------------------------------------------------------------*
* *
* SAMPLES CLASSES : *
* *
* 1 - PUBLIC *
* 2 - INTERPEL USERS *
* 3 - TRANSFERS CONTROLLERS *
* 4 - PRODUCTION CONTROLLERS *
* 5 - OPERATORS *
* 6 - SYSTEM OPERATORS *
* 7 - MASTER OPERATORS *
* 8 - SYSTEM ADMINISTRATORS *
* 9 - INTERPEL MASTER ADMINISTRATOR *
*----------------------------------------------------------------------
GENTRAN TRAN=PELMXAA,CLASS=5 HETER. ACTIVE SITES DISP.
GENTRAN TRAN=PELMXAB,CLASS=5 HETER. SPECIF. SITES DISP.
GENTRAN TRAN=PELMXACA,CLASS=5 HETER. LINKS ACTIVITY DISP
GENTRAN TRAN=PELMXACD,CLASS=5 DEPELIC. ACTIVITY DISP
GENTRAN TRAN=PELMXAC1,CLASS=5 HETER. DEFINED SITES DISP.
GENTRAN TRAN=PELMXAC2,CLASS=5 HOMOG. DEFINED SITES DISP.
GENTRAN TRAN=PELMXAFM,CLASS=1 DYNAMIC ALLOCATION
GENTRAN TRAN=PELMXALF,CLASS=1 DYNAMIC ALLOCATION
GENTRAN TRAN=PELMXALM,CLASS=1 DYNAMIC ALOCATION
GENTRAN TRAN=PELMXATH,CLASS=9 AUTHORIZED TERMINAL UPDATE
GENTRAN TRAN=PELMXAU1,CLASS=1 PRIORITY USE VERIFICATION
GENTRAN TRAN=PELMXAU2,CLASS=1 REMOTE INDEX USE VERIF.

GENTRAN TRAN=PELMXBLK,CLASS=8 INTERPEL CTL BLOCK DISPLAY
GENTRAN TRAN=PELMXBUF,CLASS=8 INTERPEL BUFFERS MAP
GENTRAN TRAN=PELMXCMD,CLASS=9 INTERPEL MASTER COMMANDS
GENTRAN TRAN=PELMXCMO,CLASS=9 XFER MODULE UPDATE
GENTRAN TRAN=PELMXCPU,CLASS=5 CPU TYPE DISPLAY
GENTRAN TRAN=PELMXCTR,CLASS=9 HETER. LINK NAME UPDATE
GENTRAN TRAN=PELMXDCB,CLASS=1 DATASET DCB DISPLAY
GENTRAN TRAN=PELMXDDN,CLASS=5 ALLOCATED DDNAMES DISPLAY
GENTRAN TRAN=PELMXDEA,CLASS=1 DYNAMIC DESALLOCATION
GENTRAN TRAN=PELMXDEL,CLASS=9 MODULE REFRESH
GENTRAN TRAN=PELMXDEM,CLASS=1 DYNAMIC DESALLOCATION
GENTRAN TRAN=PELMXDES,CLASS=1 DYNAMIC DESALLOCATION
GENTRAN TRAN=PELMXDIA,CLASS=1 HELP- PEL1 MLBX STATUS DSP.
GENTRAN TRAN=PELMXDI2,CLASS=1 HELP -PEL2 MLBX STATUS DSP.
GENTRAN TRAN=PELMXDLU,CLASS=5 MCH STATUS DISPLAY
GENTRAN TRAN=PELMXDMX,CLASS=1 HELP - MLBX KEY DISPLAY
GENTRAN TRAN=PELMXDOP,CLASS=1 HELP - OPERATOR COMMANDS
GENTRAN TRAN=PELMXDYN,CLASS=5 ALTER - TABLE MODIFICATION
GENTRAN TRAN=PELMXESS,CLASS=6 HETEROG. SESSION ABORT
GENTRAN TRAN=PELMXFLC,CLASS=9 UNIT-NAMES TABLE UPDATE
GENTRAN TRAN=PELMXFLL,CLASS=9 UNIT-NAMES TABLE LIST
GENTRAN TRAN=PELMXFSS,CLASS=9 HETEROG. MAX CONNECTION UPD.
GENTRAN TRAN=PELMXHSO,CLASS=9 HOMOG. HSO PACING UPDATE
GENTRAN TRAN=PELMXHT2,CLASS=9 HOMOG. LINKS SHUTDOWN
GENTRAN TRAN=PELMXIIS,CLASS=8 CROSS-MEMORY SERVICES START
GENTRAN TRAN=PELMXILI,CLASS=7 LINE-HANDLER START
GENTRAN TRAN=PELMXIMC,CLASS=7 X25 MCH MANAGEMENT START
GENTRAN TRAN=PELMXITB,CLASS=7 DEPELICANIZATION TASK START
GENTRAN TRAN=PELMXIT1,CLASS=6 HETEROGENEOUS LINK START
GENTRAN TRAN=PELMXIT2,CLASS=7 HOMOGENEOUS LINKS START
GENTRAN TRAN=PELMXKLI,CLASS=7 STARTER LINE CANCEL
GENTRAN TRAN=PELMXKTR,CLASS=6 HETEROG. TRANSFER CANCEL
GENTRAN TRAN=PELMXLIN,CLASS=1 LINE-HANDLER ADDRESS DISP.
GENTRAN TRAN=PELMXLIS,CLASS=1 DATASET LIST
GENTRAN TRAN=PELMXLOG,CLASS=6 TERMINAL LOGON TO INTERPEL
GENTRAN TRAN=PELMXLSI,CLASS=1 SITES LIST
GENTRAN TRAN=PELMXLTR,CLASS=5 LINKS STATUS LIST
GENTRAN TRAN=PELMXMOD,CLASS=8 INTERPEL STORAGE ZAP
GENTRAN TRAN=PELMXMXT,CLASS=9 HOMOG. PARALLEL XFERS UPDATE
GENTRAN TRAN=PELMXOGT,CLASS=7 DYNAMIC LINE-HANDLER STOP
GENTRAN TRAN=PELMXOIS,CLASS=8 CROSS-MEMORY SERVICES STOP
GENTRAN TRAN=PELMXOLI,CLASS=7 STATIC LINE-HANDLER STOP
GENTRAN TRAN=PELMXOMC,CLASS=7 X25 MCH MANAGEMENT STOP
GENTRAN TRAN=PELMXOTB,CLASS=7 DEPELICANIZATION TASK STOP
GENTRAN TRAN=PELMXOT1,CLASS=6 HETEROGENEOUS LINK STOP
GENTRAN TRAN=PELMXOT2,CLASS=7 HOMOGENEOUS LINKS STOP
GENTRAN TRAN=PELMXPOS,CLASS=9 POST - POST AN ECB
GENTRAN TRAN=PELMXPRM,CLASS=8 INTERPEL GENERAL TRACE UPDATE
GENTRAN TRAN=PELMXPRO,CLASS=7 INTERPEL CLIST EXECUTION
GENTRAN TRAN=PELMXPRT,CLASS=5 DATASET PRINT UTILITY SCS
GENTRAN TRAN=PELMXPUR,CLASS=6 PURGE OPERATOR TERMINAL
GENTRAN TRAN=PELMXP11,CLASS=5 ACTIVITY MONITORING
GENTRAN TRAN=PELMXQUE,CLASS=8 SITES BUFFERS QUEUE DISPLAY
GENTRAN TRAN=PELMXSCM,CLASS=7 VTAM OPERATOR INTERFACE
GENTRAN TRAN=PELMXSIT,CLASS=8 SITE BLOCK DISPLAY
GENTRAN TRAN=PELMXSLA,CLASS=5 MONITORING

GENTRAN TRAN=PELMXSL1,CLASS=5 MONITORING
GENTRAN TRAN=PELMXSPI,CLASS=7 SITE TRACE UPDATE
GENTRAN TRAN=PELMXSTA,CLASS=5 MONITORING
GENTRAN TRAN=PELMXSUD,CLASS=5 MONITORING
GENTRAN TRAN=PELMXSU1,CLASS=5 MONITORING
GENTRAN TRAN=PELMXSU2,CLASS=5 MONITORING
GENTRAN TRAN=PELMXSWF,CLASS=9 SWAP LOG, CPTR OR FACT
GENTRAN TRAN=PELMXSWL,CLASS=9 SWAP LANGUAGE BETWEEN E/F
GENTRAN TRAN=PELMXS1A,CLASS=5 MONITORING
GENTRAN TRAN=PELMXTAL,CLASS=1 DYNAMIC ALLOCATION
GENTRAN TRAN=PELMXTA2,CLASS=1 DYNAMIC ALLOCATION
GENTRAN TRAN=PELMXTCB,CLASS=9 TCB LIST
GENTRAN TRAN=PELMXTC2,CLASS=9 TCB DETAIL
GENTRAN TRAN=PELMXTER,CLASS=8 LINK BLOCK DISPLAY
GENTRAN TRAN=PELMXTIM,CLASS=9 HOMOG. LINKS TIMER UPDATE
GENTRAN TRAN=PELMXTMF,CLASS=3 RECEIVED DATASET BROWSE
GENTRAN TRAN=PELMXTRL,CLASS=7 LINE TRACE UPDATE
GENTRAN TRAN=PELMXTRQ,CLASS=9 QUEUE TRACE UPDATE
GENTRAN TRAN=PELMXTS2,CLASS=6 MVS-HOMOG. SESSION STOP
GENTRAN TRAN=PELMXVCP,CLASS=5 REPORTS FILE COPY
GENTRAN TRAN=PELMXVDS,CLASS=4 DATASET DUPLICATION
GENTRAN TRAN=PELMXVLO,CLASS=7 PLOG / SLOG FILE COPY
GENTRAN TRAN=PELMXVRP,CLASS=5 HOMOG. LINK PARTNER VERIFY
GENTRAN TRAN=PELMXVST,CLASS=7 STATISTICS FILE COPY
GENTRAN TRAN=PELMXWDT,CLASS=1 CURR.DATE & TIME-OF-DAY DISP
GENTRAN TRAN=PELMXXST,CLASS=6 RESTART 'Q' STATUS DEPELIC.
GENTRAN TRAN=PELMXX25,CLASS=7 REFRESH SITE X25 NUMBERS
GENTRAN TRAN=PELMXZPL,CLASS=7 INTERPEL SHUTDOWN COMMAND
**-------------------------------------------------------------------**
** INTERPEL MENUS **
**-------------------------------------------------------------------**
GENTRAN TRAN=PELM1,CLASS=1 INTERPEL PRIMARY OPTION MENU
*
*===============> OPTION '1'
*
GENTRAN TRAN=PELM11,CLASS=1 INTERPEL MAILBOX ACCESS MENU
GENTRAN TRAN=PELM111,CLASS=1 PEL/ETEBAC/ODETTE PROTOCOL XFERS
GENTRAN TRAN=PELM111A,CLASS=3 TRANSFER CANCELLATION
GENTRAN TRAN=PELM111K,CLASS=4 SCRATCH TRANSFER FILE
GENTRAN TRAN=PELM111L,CLASS=2 TRANSFERRED FILE BROWSING
GENTRAN TRAN=PELM111R,CLASS=3 TRANSFER ROUTING
GENTRAN TRAN=PELM111S,CLASS=4 TRANFERRED FILE SCRATCH
GENTRAN TRAN=PELM111U,CLASS=3 TAPE FILE UNLOAD
GENTRAN TRAN=PELM111W,CLASS=3 FILE RETRANSMISSION
GENTRAN TRAN=PELM111Z,CLASS=3 'W' STATUS MANUAL VALIDATION
GENTRAN TRAN=PELM1111,CLASS=1 PEL,ETEBAC OR ODETTE XFER DETAILS
GENTRAN TRAN=PELM112,CLASS=1 MVS-MVS HOMOGENEOUS XFERS
GENTRAN TRAN=PELM112A,CLASS=3 TRANSFER CANCELLATION
GENTRAN TRAN=PELM112D,CLASS=2 DESTIN. DATASET NAME ALTERATION
GENTRAN TRAN=PELM112J,CLASS=2 SUBMIT UTILITY
GENTRAN TRAN=PELM112L,CLASS=1 PELICANIZED FILE ATTRIB. DISPLAY
GENTRAN TRAN=PELM112P,CLASS=2 DEPELICANIZATION RESTART
GENTRAN TRAN=PELM112R,CLASS=3 REMOTE RETRANSMISSION
GENTRAN TRAN=PELM1121,CLASS=1 MVS-MVS HOMOGENEOUS XFERS DETAILS
GENTRAN TRAN=PELM113,CLASS=1 PESIT 'HORS-SIT' TRANSFERS
GENTRAN TRAN=PELM113M,CLASS=1 PESIT 'HORS-SIT' MESSAGE DISPLAY
GENTRAN TRAN=PELM1131,CLASS=1 PESIT 'HORS-SIT' TRANSFER DETAILS
GENTRAN TRAN=PELM114,CLASS=1 PESIT 'SIT' TRANSFERS

GENTRAN TRAN=PELM1141,CLASS=1 PESIT 'SIT' TRANSFER DETAILS
GENTRAN TRAN=PELM115,CLASS=1 ETEBAC5 TRANSFERS
GENTRAN TRAN=PELM115S,CLASS=4 ETEBAC5 SECURITY DETAILS 1
GENTRAN TRAN=PELM1151,CLASS=1 ETEBAC5 TRANSFER DETAILS
GENTRAN TRAN=PELM1152,CLASS=4 ETEBAC5 SECURITY DETAILS 2
GENTRAN TRAN=PELM116,CLASS=1 DIFFUSION LISTS TRANSFERS
*
*===============> OPTION '2'
*
GENTRAN TRAN=PELM12,CLASS=5 HETEROGENEOUS TRANMISSIONS MENU
GENTRAN TRAN=PELM121,CLASS=5 PC'S MANAGEMENT MENU
GENTRAN TRAN=PELM1211,CLASS=5 PC'S LIST
GENTRAN TRAN=PELM1212,CLASS=5 INACTIVE PC'S LIST
GENTRAN TRAN=PELM1213,CLASS=6 INACTIVE PC'S AUTOMATIC RESTART
GENTRAN TRAN=PELM122,CLASS=5 'IN XFER' SITES LIST
GENTRAN TRAN=PELM123,CLASS=5 CYCLIC 'IN XFER' SITES LIST
*
*===============> OPTION '3'
*
GENTRAN TRAN=PELM13,CLASS=5 MVS-MVS HOMOGENEOUS TRANSM. MENU
GENTRAN TRAN=PELM131,CLASS=5 MVS-MVS HOMOGENEOUS DEST. MANAG.
GENTRAN TRAN=PELM132,CLASS=6 MVS-MVS HOMOGENEOUS XFER CANCEL.
*
*===============> OPTION '4'
*
GENTRAN TRAN=PELM14,CLASS=1 FILE TRANSFERS SUPERVISION MENU
GENTRAN TRAN=PELM141,CLASS=5 TRANSFERS MONITORING
GENTRAN TRAN=PELM1411,CLASS=5 COMPLETE ACTIVITY
GENTRAN TRAN=PELM142,CLASS=5 TRANSFERS STATISTICS
GENTRAN TRAN=PELM143,CLASS=2 TRANSFER REPORT DETAILS
GENTRAN TRAN=PELM144,CLASS=2 ARCHIVED TRANSFERS REPORTS
GENTRAN TRAN=PELM144A,CLASS=2 ARCHIVED TRANSFERS REPORTS
GENTRAN TRAN=PELM145,CLASS=5 INTERPEL LOG FILES DISPLAY
GENTRAN TRAN=PELM146,CLASS=2 TRANSFERS REPORTS PRINT
*
*===============> OPTION '5'
*
GENTRAN TRAN=PELM15,CLASS=1 INTERPEL FACILITIES MENU
GENTRAN TRAN=PELM151,CLASS=6 DYNAMIC ALLOCATION MENU
GENTRAN TRAN=PELM151L,CLASS=7 DATASETS LIST
GENTRAN TRAN=PELM1511,CLASS=6 DATASET INFORMATIONS DISPLAY
GENTRAN TRAN=PELM1512,CLASS=1 SCRATCH CONFIRMATION
GENTRAN TRAN=PELM1513,CLASS=8 DYNAMIC FILE ALLOCATION
GENTRAN TRAN=PELM1514,CLASS=8 DYNAMIC FILE DESALLOCATION
GENTRAN TRAN=PELM1515,CLASS=4 DATASET SCRATCH
GENTRAN TRAN=PELM152,CLASS=7 FILE PRINT FACILITY
GENTRAN TRAN=PELM153,CLASS=6 TERMINALS MANAGEMENT
GENTRAN TRAN=PELM1531,CLASS=6 TERMINALS LIST
GENTRAN TRAN=PELM155,CLASS=9 GENERAL BROADCAST MSG UPDATE
GENTRAN TRAN=PELM156,CLASS=8 INTERPEL MAINTENANCE MENU
GENTRAN TRAN=PELM157,CLASS=9 DUAL DATASETS CONTROL
GENTRAN TRAN=PELM1561,CLASS=8 INTERPEL STORAGE DISPLAY
GENTRAN TRAN=PELM1562,CLASS=8 INTERPEL C.BLOCKS ADDRESS DISPLAY
*
*===============> OPTION '6'
*
GENTRAN TRAN=PELM16,CLASS=1 MONITOR ACCESS CONTROL MENU
GENTRAN TRAN=PELM161,CLASS=9 INTERPEL USERS MANAGEMENT

GENTRAN TRAN=PELM1611,CLASS=9 INTERPEL USERS LIST
GENTRAN TRAN=PELM162,CLASS=9 FILES AUTHORIZATION MANAGEMENT
GENTRAN TRAN=PELM163,CLASS=9 WORK VOLUMES MANAGEMENT
GENTRAN TRAN=PELM164,CLASS=1 USER PASSWORD UPDATE
GENTRAN TRAN=PELM165,CLASS=9 PROTOCOLS PASSWORDS MANAGEMENT
GENTRAN TRAN=PELM166,CLASS=5 TABLE MODIFICATIONS
GENTRAN TRAN=PELM167,CLASS=9 PARAMETERS MODIFICATION
*
*===============> OPTION '7'
*
GENTRAN TRAN=PELM17,CLASS=5 MONITOR ENVIRONMENT INF. MENU
GENTRAN TRAN=PELM171,CLASS=5 ROUTING INFORMATIONS
GENTRAN TRAN=PELM172,CLASS=5 X25 GATE INFORMATIONS
GENTRAN TRAN=PELM173,CLASS=5 SITES INFORMATIONS
GENTRAN TRAN=PELM174,CLASS=5 FILES INFORMATIONS
GENTRAN TRAN=PELM175,CLASS=5 LINKS INFORMATIONS
GENTRAN TRAN=PELM176,CLASS=5 LINE-HANDLERS INFORMATIONS
*
*===============> OPTION '8'
*
GENTRAN TRAN=PELM18,CLASS=1 FILE TRANSFER REQUEST MENU
GENTRAN TRAN=PELM180,CLASS=2 AUTO. PROTOCOL RESEARCH / REQUEST
GENTRAN TRAN=PELM18M,CLASS=2 PESIT MESSAGE XFER REQUEST
GENTRAN TRAN=PELM18M1,CLASS=2 PESIT MESSAGE
GENTRAN TRAN=PELM181,CLASS=2 PEL/ETEBAC/ODETTE XFER REQUEST
GENTRAN TRAN=PELM182,CLASS=2 MVS-MVS HOMOGENEOUS XFER REQUEST
GENTRAN TRAN=PELM1821,CLASS=2 MEMBERS SELECTION PANEL FOR PDS
GENTRAN TRAN=PELM183,CLASS=2 PESIT 'HORS-SIT' XFER REQUEST
GENTRAN TRAN=PELM184,CLASS=2 PESIT 'SIT' TRANSFER REQUEST
GENTRAN TRAN=PELM185,CLASS=2 ETEBAC RECEPTION REQUEST
GENTRAN TRAN=PELM186,CLASS=2 PEL-D/ODETTE RECEPTION REQUEST
GENTRAN TRAN=PELM187,CLASS=2 PESIT HORS SIT RECEPTION REQUEST
GENTRAN TRAN=PELM188,CLASS=2 ETEBAC5 TRANSFER REQUEST
GENTRAN TRAN=PELM189,CLASS=2 ETEBAC5 RECEPTION REQUEST
*
*===============> OPTION '9'
*
GENTRAN TRAN=PELM19,CLASS=2 FILE PROCESSING REQUEST MENU
GENTRAN TRAN=PELM191,CLASS=4 REQUEST EXECUTION
*
*===============> OPTION 'U'
*
GENTRAN TRAN=PELMUSR,CLASS=1 USER PRIMARY OPTION MENU
*
GENEND
END

3.3 CREATING THE ROUTING TABLE
A sample table definition can be found in the SAMPLIB library RTGTAB member.
The syntax of the macro-instructions used to define the table is given below.
The parameters shown in the macro-instruction descriptions are the default parameters.
3.3.1 GENDST0 - CREATING THE ROUTING TABLE
This macro-instruction cannot be replaced or added dynamically.
GENDST0 NAME=name
[,MAX1={nnnnn|1024}]
[,MAX2={nnnnn|1024}]
MAX1={nnnnn|1024}
Maximum number of GENDST1 entries that can be defined.
Default: 1024.
MAX2={nnnnn|1024}
Maximum number of GENDST2 entries that can be defined. The location
for this number of entries is systematically reserved.
Default: 1024.
NAME=name
Name of the routing table.

3.3.2 GENDST1 - DEFINING APPLICATIONS
GENDST1 APPL=name (1)

[,DESTL=name] (1)
[,DESTP=name]
APPL =name
Application name (defined by the GENFILE macro-instructions or specific
name for type 2 transfers: PEL2, JCL, LOAD).
It can be declared several times for different destinations.
DESTL =name
Logical destination.
Used when a transfer request is deposited to allow the file destination to be
changed, without altering the transfer request.
Used after a file has been received to allow files to be rerouted, without
affecting the remote site (application routing).
Default: DESTP value.
DESTP =name
Final physical destination of the file corresponding to the APPL/DESTL
pair. This is the actual destination specified in the transfer.
Default: none.

3.3.3 GENDST2 - DEFINING REMOTE SITES
GENDST2 DESTP=name (1)

,DESTTYP={0|1|2}
[,ADEST=name]
ADEST=name
Adjacent destination. Intermediate destination before the final physical
destination is reached (routing by destination).
It must be declared in the GENLU or GENSITE macro-instructions in the
environment table.
Default: none.
DESTP=name
Final physical destination.
It must be declared in the GENLU or GENSITE macro-instruction in the
environment table.
DESTTYP={0|1|2}
Type of transfer used to reach the final physical destination or the adjacent
destination.
0 - Logical destination attached to the local Inter.Pel.
1 - Heterogeneous link.
2 - Homogeneous MVS-MVS link.

3.3.4 GENDST3 - DEFINING THE LOCAL SITE
This must be the last macro-instruction in the routing table.

It cannot be replaced or added dynamically.
GENDST3 NAME=name
,ENVIR=name
ENVIR=name
Name of the environment table (LABEL in the GENDEB macro-instruction)
NAME=name
Name of the local site (LOCNAME in the GENDEB macro-instruction).

3.3.5 ORDER OF THE MACRO-INSTRUCTIONS
- The GENDST0 macro-instruction must always be the first macro-instruction in the first
definition member.
- The GENDST3 macro-instruction must always be the last macro-instruction in the last
definition member.
3.3.6 SAMPLE ROUTING TABLE
NOTE: the sample table can be found in the SAMPLIB library RTGTAB member.
GENDST0 NAME=RTGTAB
*
*----------------------------------------------------------------------
* APPLICATION ROUTING
*----------------------------------------------------------------------
*
GENDST1 APPL=FACT,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=FB80,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=FBM,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=IMP,DESTL=METZ,DESTP=NICE1
GENDST1 APPL=IMP,DESTL=NICE,DESTP=NICE1
GENDST1 APPL=IMP,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=ODC,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=PEL1,DESTL=METZ,DESTP=NICE1
GENDST1 APPL=PEL1,DESTL=NICE,DESTP=NICE1
GENDST1 APPL=PEL1,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=PRT,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=SAP,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=SARE,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=TEXT,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=UNDF,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=VARB,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=VS,DESTL=NTSS,DESTP=NTSS
GENDST1 APPL=LOAD
GENDST1 APPL=JCL
GENDST1 APPL=PEL2
*
*----------------------------------------------------------------------
* DESTINATIONS ROUTING
*----------------------------------------------------------------------
*
GENDST2 DESTP=SITE001,DESTTYP=1

GENDST2 DESTP=ODETTE1,DESTTYP=1
GENDST2 DESTP=ODETTE2,DESTTYP=1
GENDST2 DESTP=SITE206,ADEST=SITE205,DESTTYP=1
GENDST2 DESTP=NICE1,DESTTYP=1
GENDST2 DESTP=METZ1,DESTTYP=1
GENDST2 DESTP=NTSS0,DESTTYP=0
GENDST2 DESTP=NICE,DESTTYP=2
GENDST2 DESTP=METZ,DESTTYP=2
GENDST2 DESTP=BANK1,DESTTYP=0
GENDST2 DESTP=ATELIER,DESTTYP=0
GENDST2 DESTP=CLIENT1,DESTTYP=1
GENDST2 DESTP=PRESTA1,DESTTYP=1
GENDST2 DESTP=CLIENT2,DESTTYP=1,ADEST=PRESTA1
GENDST2 DESTP=CLIENTA,DESTTYP=0
GENDST2 DESTP=PRESTAA,DESTTYP=0
GENDST2 DESTP=BANQA,DESTTYP=1
GENDST2 DESTP=ATELA,DESTTYP=1
GENDST2 DESTP=BANQB,DESTTYP=1,ADEST=ATELA
*
*---------------------------------------------------
* DIFFUSION LISTS DECLARATIONS
*---------------------------------------------------
*
GENDST2 DESTP=LDIFF1,DESTTYP=1
GENDST2 DESTP=LDIFF2,DESTTYP=1
GENDST3 NAME=NTSS,ENVIR=ENVTAB
*
END

3.4 BROADCAST LIST TABLE
3.4.1 DESCRIPTION
Broadcast lists are used to submit or route a transfer request to several sites using a single
request. The sites on which these transfers are to be made can be defined using different
protocols.
The Logical Unit of Work (LUW) concept is used to ensure that all operations required by the
request deposit are performed correctly; this includes canceling requests that failed due to an
incident during the transfer request creation (BACKOUT) and validating all successful
transfers deposits (COMMIT).
Broadcast lists are defined using the GENLDF macro-instruction. This macro-instruction
associates a group of sites in a list with a logical list name. A list can also contain the name of
another broadcast list (broadcast list nesting). A generic name (suffixed with the "*"
character) may also be declared for the sites (but not for another list).
Each list must also be defined by a GENSITE macro-instruction and by the GENDST2 macro-
instruction using the DESTTYP=1 parameter.

3.4.2 BROADCAST LIST TABLE
GENLDF NAME=name (1)

,SITE=(site1[,site2]...)
[,MODEL=model]
NOM=name
Name of the broadcast list.
Maximum of 20 characters.
SITE=(site1[,site2]...)
List of sites or other broadcast lists attached to this broadcast list.
A site name can be generic (i.e. suffixed with *).
Maximum of 64 sites or lists.
MODEL=model
Name of the model used for routing purposes. When it is defined, it
overrides the RMODEL parameter in the GENFILE macro-instruction.
Maximum of eight characters.
Default: none.

3.4.3 SAMPLE BROADCAST LIST TABLE
NOTE: the sample table can be found in the SAMPLIB library LDFTAB member.
*----------------------------------------------------------------------
* DIFFUSION LISTS DEFINITIONS
*----------------------------------------------------------------------
*
GENLDF NAME=LDIFF1,SITE=(SITE001,SITE005,SITE01*,SITE02*)
GENLDF NAME=LDIFF2,SITE=(SITE03*),MODEL=MODEL2
GENLDF NAME=LDIFF3,SITE=(LDIFF1,LDIFF2),MODEL=MODEL2

3.5 MANAGING X.25 ACCESSES
3.5.1 DESCRIPTION
Inter.Pel can manage X.25 accesses via the X25NPSI GATE function (see Appendix B).
A table (X25TABLE) links the Inter.Pel resources (SITE) and the X.25 dial numbers. This
table is used to associate several outgoing dial numbers with each site and automatically
change the outgoing dial number, if attempts to establish a connection fail.
The X.25 PACKET SIZE and WINDOW SIZE parameters are defined for each site in the
X25TABLE.
Control of the REVERSE CHARGING parameter can be requested for outgoing and
incoming call packets.
An incoming call packet and a site can be associated via the caller X.25 number, the contents
of the call data, or both.
The EXX25IN user exit is called each time a call packet is received. This exit can return the
name of the calling site (see the System Programmer's Reference Manual).
The EXX25OUT user exit is called before an outgoing call packet is created. It can return the
outgoing call packet as it is to be sent over the X.25 network (see the System Programmer's
Reference Manual).
The X.25 accesses are activated when Inter.Pel is started up. If an access is temporarily out of
service, Inter.Pel tries periodically to reactivate it.

3.5.2 X25TABLE
This table is loaded when Inter.Pel is started up.

The GENX25NB macro-instruction is used to create this table.
A sample table definition can be found in the SAMPLIB library X25TAB member.
GENX25NB NAME=name (1)

[,INx=nnnnnnnnnn]
[,INFx=({RC|NORC},{CHCK|NOCHCK})]
[,INUx=({X,hex value|C,char value})]
[,MCHx=mmmmmmmm]
[,OUTx=(nnnnnnnnn,aaaaaaaa)]
[,OUTFx=vvvv]
[,OUTUx=({X,hex value|C,char value})]
[,PKSZx={nnn|128}]
[,PROFILE=name]
[,RETRYx={nn|8}]
[,TMOUT={nn|9}]
[,WDx={n|2}]
NOTE: the value of the "x" suffix at the end of the parameter name
can be between 1 and 4.
INx=nnnnnnnnnn
Value of the X.25 access caller number of the remote site.
This number can be generic. any * then replaces a group of characters, any
? replaces a single character.
Maximum length: 156 digits.
Examples: IN1=17503434.
IN1=1*03?8 (accepts any number starting with 1 and ending
with 03 followed by any number and then a 8, like
1756790348 or 179260318).
Default: none.
INFx=({RC|NORC},{CHCK|NOCHCK})
Call accept parameters.
RC - Reverse charge calls are accepted.
NORC - Reverse charge calls are not accepted.
CHCK - The caller number is checked.
NOCHCK - The caller number is not checked.
Default: (RC,CHCK).
INUx=({X,hex value|C,char value})

Value of the associated user field when the call is received.
This value can be in character or hexadecimal form.
Example: INU1=(C,PELICAN) in characters.
INU1=(X,C012345) in hexadecimal.
Default: none.

MCHx=mmmmmmmm
MCH associated with a number for outgoing calls.
If this parameter is set, the associated number (OUTx) can only be used if
the MCH requesting this outgoing call is the one specified in this parameter.
When combined with the ALTPATH parameter in the GENTER macro-
instruction, it is used to switch automatically to a backup MCH and its
associated number.
If this parameter is not specified, the X.25 number can be selected,
irrespective of which MCH is active.
Default: no associated MCH.
NAME=name
Site name.
OUTx=(nnnnnnnnn,aaaaaaaa)
nnnnnnnnn: X.25 number to be specified when calling the site.
aaaaaaaa: Caller number to be indicated in the call packet.
Maximum length: 2 x 156 digits.
Example: OUT1=1750304788.
OUT1=(1750000,918).
Default: none.
OUTFx=vvvv
Facilities field to be included in the outgoing call packet.
(The value must be hexadecimal.)
Example: OUTF1=1003.
Default: none.
OUTUx=({X,hex value|C,char value})

User data field to be included in the outgoing call packet. This value can be
in character or hexadecimal form.
Example: OUTU1=(C,PELICAN) in characters.
OUTU1=(X,C012345) in hexadecimal.
Default: none.
PKSZx={nnn|128}
Packet size.
Default: 128.
PROFILE=name
Site used as a model when creating another site dynamically. Site creation is
always authorized if this parameter is set until the real control is performed
by the EXODETLG exit, or the GENSAF macro.
Default: none; the site exists, or automatic creation is not authorized.
RETRYx={nn|8}
Number of retries after which the dial number is considered to be out of
service. Inter.Pel then uses the next number, if it is defined.
The CLX25NO command allows a temporarily disabled number to be
reactivated.
Default: 8.

TMOUT={nn|9}
Time after which the SVC will be released if no activity takes place.
It is expressed in minutes.
Caution: This value must always be greater than the timeout value defined
in the GENTER macro associated with this X25 number.
For no time-out, set the parameter to 0 (zero).
Default: 9.
WDx={n|3}
Packet window size.
Default: 3.

3.5.3 SAMPLE X25TABLE
NOTE: the sample table can be found in the SAMPLIB library X25TAB member.
GENX25NB NAME=SITE025,TMOUT=5, *
OUT1=175041739,OUTU1=(X,C0120010), *
OUT2=175002339,OUTU2=(X,C0120010), *
IN1=175041739, *
IN2=175002339
OUT1=(1220412584,21), *
IN1=122041258
OUT1=144047854, *
IN1=144047854
IN1=114589564, *
IN2=140000584
OUT1=125000158,OUTU1=(X,C0550010), *
OUT2=125000158,OUTU2=(X,C0550010)
OUT1=113580008,OUTU1=(X,C0124780)
OUT1=113580008, *
OUT2=113258888
IN1=136589564, *
IN2=136000588
IN1=186008965, *
IN2=186000064, *
IN3=186012588
OUT1=178047854, *
IN1=178047854
OUT1=168045789, *
IN1=168045789
*----- SIT
GENX25NB NAME=DUMMYSIT,TMOUT=40, *
IN1=34
OUT1=(34,11),PKSZ1=1024,WD1=1
OUT1=(34,11),PKSZ1=1024,WD1=1
*----- SIT END
GENX25NB NAME=552139305,TMOUT=5, *
OUT1=168045789, *
OUT2=168000984
GENX25NB NAME=662139305,TMOUT=5, *
IN1=155887000, *
IN2=155000879
IN1=172000888
IN1=149004589
IN1=179005689, *
IN2=179005890
IN1=133058963, *
IN2=179072591

GENX25NB NAME=CLIENT1,TMOUT=5,
IN1=14909209120,
OUT1=14909209120
GENX25NB NAME=PRESTA1,TMOUT=5,
IN1=14907348540,
OUT1=14907348540
GENX25NB NAME=BANQA,TMOUT=5,
IN1=14909209120,
OUT1=14909209120
GENX25NB NAME=ATELA,TMOUT=5,
IN1=14907348540,
OUT1=14907348540
END

3.6 MANAGING TCP/IP ACCESSES
3.6.1 DESCRIPTION
Inter.Pel uses the Interlink SNS/TCPaccess product and/or the IBM product to manage
TCP/IP accesses (see Appendix E).
A table (IPTABLE) links the Inter.Pel resources (SITE) and TCP/IP addresses. This table is
used to associate several outgoing IP addresses with each site and automatically change IP
addresses, if attempts to establish a connection fail.
An incoming IP address and a site can be associated via the IP address of the calling site and
the listening port number assigned to the local TCP/IP manager.
The EXIPIN user exit is called each time a call is received. This exit can return the name of
the calling site (see the System Programmer's Reference Manual).
The EXIPOUT user exit is called before the outgoing connection is requested. It can return the
outgoing IP address(see the System Programmer's Reference Manual).
The TCP/IP accesses are activated when Inter.Pel is started up. If an access is temporarily out
of service, Inter.Pel tries periodically to reactivate it.
3.6.2 IPTABLE

The GENIPNB macro-instruction is used to create this table.
A sample table definition can be found in the SAMPLIB library IPTB member.
GENIPNB NAME=name (1)

[,INx=nnnnnnnnnn]
[,NINx=hostname] (2)
[,NOUTx=hostname] (2)
[,OUTx=nnn.nnn.nnn.nnn]
[,PLCINx=vvvvv]
[,PLCOUTx=vvvvv]
[,PORTINx=vvvvv]
[,PORTOUTx=vvvvv]
[,PROFILE=name]
[,RETRYx={nn|8}]
[,TIMERx={nnnnn|0}]
[,TMOUT={nn|9}]

(2) Parameter available exclusively for the IBM product, Release 3.2 and above.

INx=nnn.nnn.nnn.nnn
nnn.nnn.nnn.nnn: IP address of the calling site.
The value * in the place of a group of three digits (one hexadecimal digit),
indicates that a check does not have to be run on this digit in the caller
address.
The value *.*.*.* indicate that no control must be performed on the caller
address but only on the port number as defined in the PCLINx parameter
(equivalent of NINx=*).
Note: since the caller address is not really reliable and since it may be
difficult to manage this address (automatic address selection or use of NAT),
you are advised to always use the generic site selection (INx=*.*.* or
NINx=*). PCLINX will then be used to select the protocol by assigning the
entry to the DUMMY site associated with the GENLIGN managing this
protocol. The real site will be retrieved later from the protocol parameters.
Maximum length: 15.
Example: IN1=127.0.0.1.
Default: none.
NAME=name
Site name.
NINx=hostname
Name used for incoming connections.
Maximum length: 74.
This name must not contain any spaces.
If this string does not contain any dots ('.'), TCP/IP concatenates it with the
domain name defined by the DOMAINORIGIN parameter (SYSTCPD DD
card in the Inter.Pel JCL).
When coded to *, indicates that a check does not have to be run on the
caller name but only on the port number as defined in the PCLINx
parameter.
If this parameter is set, it overrides the INx parameter.
Example: NIN1=HOST1.
Default: none.
NOUTx=hostname
Name used for outgoing connections.
Maximum length: 74.
If this parameter is set, it overrides the OUTx parameter.
Example: NOUT1=HOST1.
Default: none.

OUTx=nnn.nnn.nnn.nnn
nnn.nnn.nnn.nnn: IP address to be specified when calling the site.
Maximum length: 15.
Example: OUT1=127.0.0.1.
Default: none.
PLCINx=vvvvv
Local listening PORT for the local TCP/IP manager receiving the call from
the calling site. It provides an additional criterion to identify a calling site
when several TCP/IP managers are running.
(It must be a decimal number.)
Example: PLCIN1=3500.
Default: none.
PLCOUTx=vvvvv
Local listening PORT for the local TCP/IP manager calling the destination
site. It is not currently used.
Example: PLCOUT1=3500.
Default: none.
PORTINx=vvvvv
Calling site PORT. It is not currently used.
Example: PORTIN1=4310.
Default: none.
PORTOUTx=vvvvv
Listening PORT to be provided for the destination site to be reached.
(It must be decimal.)
Example: PORTOUT1=6210.
Default: none.
PROFILE=name
Site used as a model when creating another site dynamically. Automatic
creation is always authorized if this parameter is set until the real control is
performed by the EXODETLG exit or the GENSAF macro..
RETRYx={nn|8}
Number of retries after which the address is considered to be out of service.
Inter.Pel then uses the next number, if it is declared.
The CLIPNO command allows a temporarily disabled number to be
reactivated.
Default: 8.
TIMERx={nnnnn|0}
Data flow control timer in hundredths of a second.
Default: 0.

TMOUT={nn|9}
Period at the end of which the SVC table entry is released if no activity has
taken place.
Expressed in minutes.
in the GENTER macro associated with this IP address.
Default: 9.

3.6.3 SAMPLE IPTABLE
NOTE: the sample table can be found in the SAMPLIB library IPTAB member.
GENIPNB NAME=PELIUNX1,TMOUT=3,
OUT1=145.45.25.1,PORTOUT1=6210,
IN1=145.45.25.1,PLCIN1=3500
OUT1=145.45.25.2,PORTOUT1=6210,
IN1=145.45.25.2,PLCIN1=3500
OUT2=145.45.25.3,PORTOUT2=6210,
IN2=145.45.25.3,PLCIN2=3500
OUT3=145.45.25.4,PORTOUT3=6210,
IN3=145.45.25.4,PLCIN3=3500
END

3.7 MANAGING MODELS
3.7.1 DESCRIPTION
A model is a pre-defined set of parameters reflecting a transfer request to be deposited in the

MAILBOX. This facility is not currently available via:
- Request deposit screens in the transfer monitor (8.x)
Each model definition is based on the following principles:
- Creation of a model-type entry: this entry can contain the complete list of
parameters for one transfer request, irrespective of the protocol used
- Creation of n protocol-type entries: the parameters specific to each protocol can be
created under a model-type entry. Only one entry is authorized for each protocol
defined in a model
With the exception of the model name in the GENMODEL macro-instruction, no parameter is
mandatory. Parameters that are not set are not active, and no default value is used with the
model. The default value specified in the parameter definition is the value used when the
request is submitted, if the parameter is not set either in the model or in the request.
Operating rules:
All transfer requests specifying a model name trigger the following procedure.
1. The parameters in the MODEL-type entry with the name specified are retrieved.
2. The MODEL-type entry is searched for a protocol-type entry corresponding to the
protocol required by the site: if the entry is found, the parameters are applied (if
necessary, they override the parameters defined in the MODEL-type entry).
3. The pre-defined parameters can, if necessary, be overridden by the parameters in the
initial request.
NOTE: the use of models allows transfer requests to be deposited by setting only a limited
number of parameters, or just the name of the model.

3.7.2 GENMODEL: CREATING A MODEL-TYPE ENTRY
The GENMODEL macro-instruction is used to create a MODEL-type entry.
GENMODEL NAME=name
[,ACK=x]
[,APPL=xxxxxxxx]
[,CDATE=xxxxx]
[,CHKDSN={YES|NO}]
[,CIPH=x]
[,COMP=n]
[,CONTRAT=xxxxxxxxxxxxxxxxxxxxxx]
[,CTIME=nnnnnn]
[,CUMULMNT=x]
[,CYL=nnn]
[,DEST=xxxxxxxxxxxxxxxxxxx]
[,DSIGN={YES|NO}]
[,DSNDEST=xxxxxxxxxxx....xxxxxxx]
[,DSNORIG=xxxxxxx....xxxxxxx]
[,DUPFILE=x]
[,FDATE=nnnnn]
[,FILECODE=x]
[,FILESIZE=xxxxxxxx]
[,FMTMSG={YES|NO}]
[,GETCAR={YES|NO}]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,JOBR=xxxxxxxx]
[,LABEL=xxxxxxxx.......xxxxxx]
[,LOCAL=xxxxxxxxxxxxxxxxxx]
[,LRECL=nnnnn]
[,MBR=xxxxxxxx]
[,MBRLIST=xxxxx.......xxxxxx]
[,MESSAGE=xxxxxxx....xxxxxxx]
[,MODREQ=xxxxxxxx]
[,MSG1=xxxxxxxx.......xxxxxx]
[,N=xxxxxxx....xxxxxxx]
[,NOM=xxxxx]
[,NOME5=xxxxxxxxxxxxxx]
[,ORIGINE=xxxxxxxxxxxxxxxxxxxx]
[,PARAF={YES|NO}]
[,PERM=x]
[,PRIOR=n]
[,PROFILE=xxxxxxxxxxxxxxxxxxxx]
[,RANG=nnnnnnnn]
[,RECFM=x]
[,RELANCE=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,SEAL=x]
[,SIGN=x]
[,SUPPRESS=x]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
[,USERAREA=xxxxxx......xxxxxxx]
[,USERDATA=xxxxxxxxxxxxxxxxxxx]
[,USERNAME=xxxxxxxx]

[,UTIL=x]
ACK : Request for an acknowledgment message (Y/N) in response to a PeSIT

Hors SIT level E message.
Default: N.
Protocol(s): PeSIT Hors SIT E.
APPL : Name of one of the applications defined in the routing table or file type (PI
11) for PeSIT or ETEBAC5 transfers.
Default: none.
Protocol(s): all.
CDATE : File creation date (YYDDD).

Default: selection start date.
Protocol(s): all except PEL2.
CHKDSN : Check if the file exists.

Y - Check if the file exists while creating the transfer request.
N - No check while creating the request. The check is run at transfer
time (in this case, the value of the GETCAR parameter is forced
to N (get physical characteristics of the file at transfer time).
Default: Value of the CHKDSN parameter in the PELPARMS file.
Protocol(s): PEL, ODETTE, ETEBAC3, PeSIT Hors-SIT, FTP
CIPH : Encryptionrequested for this transfer.

N - No encryption.
R - DES encryptionwith transmission of RSA encrypted elements and
use of a sequester.
3 - Triple DES encryptionwith transmission of RSA encrypted elements
and use of a sequester.
U - No encryptionin requester mode.
Accepts the encryptionproposed by the remote site in server mode.
Default : SECCIPH parameter for the corresponding site.
Protocol(s) : ETEBAC5.
COMP : Compression.
PEL:
0 - No compression.
2 - Horizontal compression.
3 - Compacting (valid for sequential fixed format records; only those
characters that are different from the previous record are
transferred).
4 - Compacting (3) then compression (2).
PeSIT Hors SIT and ETEBAC5:
0 - No compression.
2 - Vertical compression.
3 - Mixed compression (horizontal + vertical).
Default: 2.
Protocol(s): PEL, PeSIT Hors SIT, ETEBAC5.
CONTRAT : Identification of the contract used for this transfer (PI 3bis).
Default: none.
Protocol(s): ETEBAC5.

CTIME : File creation time (HHMMSS).
Default: selection start time.
CUMULMNT : Checksum for bank-type files

Y - Inter.Pel calculates the checksum.
N - Inter.Pel does not calculate the checksum.
Default: N.
Protocol(s): PEL and PEL2.
CYL : Space allocated in cylinders on the sender site for the file generated by the
utility (for a partitioned or VSAM file, the unused space is not released) and
for the pelicanized file (for all file types, the unused space is released). The
value is between 1 and 999.
For sequential and partitioned files, no default value is used, as the size is
calculated automatically. This parameter must be set for VSAM files.
Default: None.
Protocol(s): PEL2.
DEST : Name of the transfer destination site. This site is defined in the routing
table.
Default: none.
Protocol(s): all.
DSIGN : Use of the ETEBAC 5 remote signature.

Y - Use the remote signature (transfer is created with status S and
will be released when the remote signature has been performed.)
N - Do not use remote signature.
Default : N.
Protocol(s) : ETEBAC5
DSNDEST : Name of the receiving file on the destination site. This keyword is required
if the UTIL=Y option is set and the file to be transmitted is not sequential.
When transmitting a sequential file, you can specify a GDG file along with
the required relative generation number; if (+1) is set in the generation
number, the current generation plus one is created on the receiver site. If the
file exits on the destination site, it is overwritten; otherwise, disk space is
allocated and the file is catalogued.
Default: none.
Protocol(s): PEL2.
DSNORIG : Name of the file to be transmitted.

Default: none.
Protocol(s): all.
DUPFILE : Source file transfer control.

Y - The source file is transferred as many times as necessary.
N - The transfer is refused if the source file name is already recorded in
the MAILBOX for the destination site.
Default: N.
Protocol(s): all except PeSIT SIT and ETEBAC5.
FDATE : End of selection date.

AAQQQ - Year and day.
+X - Current date plus X day(s), X being between 1 and 9.
Default: none.

FILECODE : File code.
A - Inter.Pel informs the remote site via the protocol that the file is in
the ASCII format.
AT - Inter.Pel informs the remote site via the protocol that the file is in
the ASCII format and converts it from the EBCDIC to ASCII format
during the transfer.
E - Inter.Pel informs the remote site via the protocol that the file is in
the EBCDIC format.
B - Inter.Pel informs the remote site via the protocol that the file is in
the binary format.
Default: E.
Protocol(s): PeSIT Hors SIT, FTP and ETEBAC5.
FILESIZE : Number of records in the file.

This parameter is mandatory for IN-STREAM files from CICS; otherwise, it
is ignored.
Default: none.
Protocol(s): all.
FMTMSG : Used for VSAM file transfers only.

Y - During the transfer, additional VSAM information is transmitted to
the remote site at the end of PI 99 (DATA CISIZE (5), INDEX
CISIZE (5), average LRECL (5) and SHR option (2)).
N - Additional information is not transmitted.
Default : N
Protocol(s) : PeSIT Hors-SIT E.
GETCAR : Get physical parameters of this file.

Y - Get physical parameters of this file (DCB, number of records)
when creating the transfer request.
N - Get physical parameters at transfer time.
If the value of the CHKDSN is set to N, the value of the GETCAR
parameter is also set to N.
Protocol(s): PEL, ODETTE, ETEBAC3, PeSIT Hors-SIT, FTP
HOLD : Transfer hold flag.

Y - The transfer is created with the H status. It can only be activated
after a release (press PF9 on the MAILBOX detail screen or set the
status to 9 via INTBAL or MLBTRDSN).
N - The transfer can be activated immediately (status 9).
Default: N.
Protocol(s): all.
HSDEB : Time after which a transfer can take place (HHMM).

With PEL protocol, during central request deposit, if this parameter is
provided, it will be used to complete the start-of-transmission time in the
mailbox record.
Default: the transfer can take place immediately.
Protocol(s): all.
HSFIN : Time after which a transfer can no longer take place (HHMM).
Default: none.
Protocol(s): all.

INTERVAL : Number of minutes between two retries. It must be between 0 and 99
minutes.
Default: 0 for transmission requests.
15 for reception requests.
Protocol(s): all except PEL2 and FTP.
JOBR : Name of the job to be submitted on the source site when the action report is
received.
Default: none.
Protocol(s): PEL2.
LABEL : LABEL (PI 37) that will be sent to the remote site in PeSIT Hors-SIT
version E protocol.
Default : None.
Protocol(s) : PeSIT Hors-SIT.
LOCAL : Name by which the local site is to be presented to the remote site via the
protocol. This name must be defined as type 0 in the routing table if it is not
the Inter.Pel name.
Default: Inter.Pel name.
LRECL : Logical record length.

This parameter is mandatory for IN-STREAM files from CICS if a PEL1
application is used for the transfer (LRECL not set in a GENFILE entry);
otherwise, it is ignored.
Default: none.
Protocol(s): all.
MBR : Member of a partitioned file to be transferred.

For the PEL2 protocol, up to 20 MBR parameters can be provided. In this
case, this list replaces the MBRLIST parameter.
Default: none.
Protocol(s): PEL, PEL2, FTP and PeSIT Hors SIT.
MBRLIST : List of the members in a partitioned file to be transferred. A maximum of

twenty members can be specified. If all the members in a file are to be
transferred, this parameter must be omitted.
Default: none.
Protocol(s): PEL2 and PeSIT Hors SIT E.
MESSAGE : Accompanying message describing the transfer.

Default: none.
Protocol(s): PEL2.

MODREQ : Inter.Pel mode used to process this request.
B - This request can be transmitted, whether Inter.Pel is the server or
the requester
R - This request can only be transmitted if Inter.Pel is the requester. It is
not presented if the remote site has established the connection and
reads the file
S - This request can only be transmitted if Inter.Pel is the server, when a
SELECT is received from the remote site that established the
connection and wishes to read the file (never if the local site
initiated the connection).
Default: B.
Protocol(s): PeSIT Hors SIT.
MSG1 : Accompanying message 1 describing the transfer.

Default: none.

Default: none.
Protocol(s): all except PEL2 and PeSIT SIT.
N : PeSIT Hors SIT file name (PI 12).

Default: none.
Protocol(s): PeSIT Hors SIT and FTP.
NAME : Model name.

Reference key when a model is used in a transfer request.
Default: none.
Protocol(s): all.
NOM : PeSIT SIT file name (PI 12).

Default: none.
Protocol(s): PeSIT SIT.
NOME5 : ETEBAC5 file name (PI 12).

Default: none.
ORIGINE : For reception requests, remote site on which the file is to be read (this
parameter overrides the DEST parameter).
Note: this parameter is maintained for compatibility reasons only. You are
advised to always use the DEST parameter to define the remote site, and the
LOCAL parameter to define the local site.
Default: none.
Protocol(s): ETEBAC3, PEL and ODETTE.
PARAF : Use of the ETEBAC 5 agreement.

Y - Use the remote signature agreement (transfer is created with status
S and will be released when the agreement has been
performed).
N - Do not use agreement.
Default : N.

PERM : Permanent request flag:
Y - The request is created as permanent, it will stay with status 9 after
each transmission (in server mode) to let it be selected at next
reception of a LIST or NLST command.
N - The request is nit created as permanent.
Default: N.
Protocol(s): FTP.
PRIOR : Transfer priority:

PEL : 0 to 9 (0 = top priority).
ODETTE : 0 to 9 (0 = top priority).
ETEBAC : 0 to 9 (0 = top priority).
PEL2 : Top-priority channel used (Y/N).
PeSIT : 1 to 3 (1 = top priority).
ETEBAC5 : 1 to 3 (1 = top priority).
Default: 1 in PeSIT and ETEBAC5, N in PEL2 otherwise, 5.
Protocol(s): all.
PROFILE : Site model to be used for a submission to a dynamically allocated site.

Caution: with the PeSIT Hors-SIT protocol, if this site accepts outgoing calls
(STOSR=B or STOSR=R), this site is considered as the adjacent site for routing.
The transfer is routed toward this PROFILE site with the site defined in the DEST
parameter as the final destination.
Default: none.
Protocol(s): PEL, ETEBAC3, PeSIT Hors-SIT et FTP.
RANG : Transfer rank.

Default: rank number generated by Inter.Pel.
Protocol(s): PEL and PeSIT SIT.
RECFM : Record format (F for a fixed format, V for a variable format).

application is used for the transfer (RECFM not set in a GENFILE entry);
Default: none.
Protocol(s): all.
RELANCE : Authorization to resume an existing SIT transfer. If the value is not blank or
a binary zero, the transfer is resumed.
Default: the transfer is not resumed.
Protocol(s): PeSIT SIT.
RETRY : Number of transfer retries to be performed. This number must be between 1

and 99.
Default: 10.
Protocol(s): all, except PEL2 and FTP.
SCRATCH : Source file scratch flag.

Y - The source file must be deleted when the request is deleted from the
MAILBOX.
N - The source file is not deleted.
Default: N.
Protocol(s): all.

SDATE : Earliest transfer date.
YYDDD - Year and day.
When provided for a central request in PEL protocol, this parameter will be
used to complete the start of-transmission date field in the mailbox.
Default: the transfer takes place immediately.
Protocol(s): all.
SEAL : Type of ETEBAC5 sealing used for this transfer.

N - No sealing.
P - DES CBC sealing with transmission of RSA encrypted elements
and partial seals.
R - DES CBC sealing with transmission of RSA encrypted elements but
no partial seals.
M - DES MDC sealing, no transmission of elements and no partial seals.
S - SHA-1 sealing, no transmission of elements and no partial seals.
U - No sealing in requester mode.
Accepts the sealing proposed by the remote site in server mode.
Default : Value of the SECSEAL parameter for the corresponding site.
SIGN : Type of ETEBAC5 signature used for this transfer.

N - No signature.
1 - Single signature.
2 - Double signature.
U - No signature in requester mode.
Accept the signature proposed by the remote site in server mode.
Default: value of the SECSIGN parameter for the corresponding site.
SUPPRESS : Procedure to be followed for this request when the number of retries is
reached.
Y - The request is deleted from the MAILBOX.
N - The request is canceled in the MAILBOX.
This parameter is only used for reception requests.
Default: N.
Protocol(s): all except PeSIT SIT, FTP and PEL2.

TRACKER : XFB.SCOPE or Sentinel tracking activation.
Y - Mailbox records are sent to the tracker every time their status
changes.
N - Nothing is sent to the tracker.
S - Mailbox records are sent to the tracker only when their status
changes to 2, 4, 5, 6, 7, 9, A, C, I, N. Messages selected in the
messages table are always sent.
Default : Value of the TRACKER parameter in the GENFILE associated
with this transfer.
Protocol(s) : All.
TRKCID : Cycle ID of the object to which this transfer will be linked in Sentinel.
Default : No link.
Protocol(s) : All.
TRKCIDX : Hexadecimal Cycle ID of the object to which this transfer will be linked in
Sentinel.
Default : No link.
Protocol(s) : All.
TRKOBJ : Type of the object to which this transfer will be linked in Sentinel
Default : No link.
Protocol(s) : All.
TYPEREQ : Type of request.

S - Standard: the catalogued file specified in the DSNORIG parameter
is transferred.
M - Message: the PeSIT Hors SIT level E message is transferred. This
type of transfer is the same as the "delayed" mode for files.
C - Call: a file reception request is created.
Caution: when a request is submitted by CICS, it is imperative for this
parameter to be set by the program; the model value must not be used.
Default: none.
Protocol(s): all.
USERAREA : MAILBOX user area. This data is stored only on the local site and never
transmitted to the remote site. When a reception request is submitted, this
area is copied to the MAILBOX record corresponding to each file received
as a result of that request.
Default: none.
Protocol(s): all.

USERDATA : User area transmitted to the remote site. When a VSAM file is transferred,
this area indicates the catalog on the destination site that will be used to
locate the file specified in the DSNDEST keyword.
Example of use consistent with the sample EXRCV001 exit provided in the
SAMPLIB library. This option specifies the name of a member containing
JCL cards with symbolic parameters. When the file is transferred, the JCL
referenced in this way is resolved and submitted in BATCH mode. In this
case, the data is coded as follows.
01,MBRI,MBRO, where:
MBRI refers to the name of a member containing a symbolic JCL
that can be found in a library on the destination site.
MBRO refers to the name of the member to which the resolved JCL
corresponding to the above-mentioned member is output. If
this name is omitted, Inter.Pel assigns a default name.
If a JCL is to be submitted when a file is received, the UTIL=N keyword
must be declared.
Default: none.
Protocol(s): PEL2.
USERNAME : Name of the user authorized to modify files on a specific site (see menu
1.5.B). The TSO USERID is also informed when the action report job has
been completed.
Default: none.
Protocol(s): PEL2.
UTIL : Request to activate a utility on the destination site.

Default: N.
Protocol(s): PEL2.
Note: Enclose the parameters in quotes if there are imbedded blanks.
A sample table definition can be found in the SAMPLIB library MOD001 member.

3.7.3 GENETB12: CREATING AN ETEBAC1/2 ENTRY
The GENETB12 macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the ETEBAC1 and ETEBAC2 protocols.
GENETB12 APPL=xxxxxxxx
[,CDATE=xxxxx]
[,CTIME=nnnnnn]
[,DUPFILE=x]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LRECL=nnnnn]
[,PRIOR=n]
[,RECFM=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,USERAREA=xxxxxxx......xxxxxxx]
APPL : Name of one of the applications defined in the routing table.

Default: none.

CTIME : File creation time (HHMMSS).

table.
Default: none.

Default: none.

Y - The source file is transferred as many times as necessary
Default: N.

is ignored.
Default: none.

Default: N.

Default: none.

minutes.
the Inter.Pel name.

Default: none.

Default: none.

Default: none.
PRIOR : Transfer priority.

0 to 9 (0 = top priority).
Default: 5.

Default: none.

and 99.
Default: 10.

MAILBOX.
Default: N.


changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
TRKOBJ : Type of the object to which this transfer will be linked in Sentinel.
Default : No link.
Default: none.

3.7.4 GENETEB3: CREATING AN ETEBAC3 ENTRY
The GENETEB3 macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the ETEBAC3 protocol.
GENETEB3 APPL=xxxxxxxx
[,CDATE=xxxxx]
[,CHKDSN={YES|NO}]
[,CTIME=nnnnnn]
[,DUPFILE=x]
[,GETCAR={YES|NO}]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LRECL=nnnnn]
[,PRIOR=n]
[,RECFM=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,SUPPRESS=x]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
[,USERAREA=xxxxxxx.......xxxxxxx]

Default: none.


CTIME : File creation time (HHMMSS)..


table.
Default: none.

Default: none.

Default: N.

is ignored.
Default: none.


Default: N.

Default: none.

minutes.
the Inter.Pel name.

Default: none.

Default: none.

Default: none.
Default: none.

Default: 5.

Default: none.

Default: none.

and 99.
Default: 10.
SCRATCH : Source file scratch flag..

MAILBOX.
Default: N.

reached.
Default: N.

changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.

S - Standard: the catalogued file specified in the DSNORIG parameter, is
transmitted.
Caution: when a request is submitted by CICS, this parameter must be
set by the program; the model value must not be used.
Default: none.
Default: none.

3.7.5 GENETEB5: CREATING AN ETEBAC5 ENTRY
The GENETEB5 macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the ETEBAC5 protocol.
GENETEB5 [,APPL=xxxxxxxx]
[,CDATE=xxxxx]
[,CIPH=x]
[,COMP=n]
[,CONTRAT=xxxxxxxxxxxxxxxxxxxxxx]
[,CTIME=nnnnnn]
[,DSIGN={YES|NO}]
[,FDATE=nnnnn]
[,FILECODE=x]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LRECL=nnnnn]
[,NOME5=xxxxxxxxxxxxxx]
[,PARAF={YES|NO}]
[,PRIOR=n]
[,RECFM=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,SEAL=x]
[,SIGN=x]
[,SUPPRESS=x]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
[,USERAREA=xxxxxx......xxxxxx]
11).
Default: none.


CIPH : Encryptionrequested for this transfer.
N - No encryption.
R - DES encryptionwith transmission of RSA encrypted elements and
use of a sequester.
3 - Triple DES encryptionwith transmission of RSA encrypted elements
and use of a sequester.
U - No encryptionin requester mode.
Accept the encryptionproposed by the remote site in server mode.
Default : SECCIPH parameter for the corresponding site.
COMP : Compression.
0 - No compression.
Default: 2.
CONTRAT : Identification of the contract used for this transfer (PI 3bis).
Default: none.

table.
Default: none.
DSIGN : Use of the ETEBAC 5 remote signature.

Y - Use the remote signature (transfer is created with status S and
will be released when the remote signature has been performed).
N - Do not use remote signature.
Default : N.

Default: none.
FDATE : End of selection date.

Default: none.

the ASCII format.
the ASCII format and converts it from EBCDIC to ASCII at
transmission time.
the EBCDIC format.
the binary format.
Default: E.

is ignored.
Default: none.

Default: N.

Default: none.

minutes.
the Inter.Pel name.

Default: none.

Default: none.

Default: none.
NOME5 : ETEBAC5 file name (PI 12).

Default: none.
PARAF : Use of the ETEBAC 5 agreement.

Y - Use the remote signature agreement (transfer is created with status
S and will be released when the agreement has been
performed).
N - Do not use agreement.
Default : N.

Default: 1.

Default: none.

and 99.
Default: 10.

MAILBOX.
Default: N.

SEAL : Type of ETEBAC5 sealing used for this transfer.

N - No sealing.
P - DES CBC sealing with transmission of RSA encrypted elements
and partial seals.
R - DES CBC sealing with transmission of RSA encrypted elements but
no partial seals.
M - DES MDC sealing, no transmission of elements and no partial seals.
S - SHA-1 sealing, no transmission of elements and no partial seals.
U - No sealing in requester mode.
Accept the sealing proposed by the remote site in server mode.
Default : Value of the SECSEAL parameter for the corresponding site.
SIGN : Type of ETEBAC5 signature used for this transfer.

N - No signature.
1 - Single signature.
2 - Double signature.
U - No signature in requester mode.
Accept the signature proposed by the remote site in server mode.
Default: value of the SECSIGN parameter for the corresponding site.
reached.
Default: N.

changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.

S - Standard: the catalogued file specified in the DSNORIG parameter,
is transferred.
Default: none
Default: none.

3.7.6 GENFTP: CREATING A FTP ENTRY
The GENFTP macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the FTP protocol.

NAME OPERATION OPERANDE(S)
GENFTP [,APPL=xxxxxxxx]
[,CDATE=xxxxx]
[,CHKDSN={YES|NO}]
[,CTIME=nnnnnn]
[,FILECODE=x]
[,GETCAR={YES|NO}]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,LRECL=nnnnn]
[,MBR=xxxxxxxx]
[,PERM=n]
[,PRIOR=n]
[,RECFM=x]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
APPL : Name of one of the applications defined in the routing table or file type.
Default: none.



table.
Default: none.

Default: none.

the ASCII format.
the ASCII format and converts it from the EBCDIC to ASCII format
during the transfer.
the EBCDIC format.
the binary format.
Default: E.

is ignored.
Default: none.


Default: N.

Default: none.
the Inter.Pel name.

Default: none.

Default: none.

Default: none.

Default: none.
N : Logical file name (PI 12).

Default: none.
PERM : Permanent request flag:

Y - The request is created as permanent, it will stay with status 9 after
each transmission (in server mode) to let it be selected at next
reception of a LIST or NLST command.
N - The request is nit created as permanent.
Default: N.
PRIOR : Transfer priority:

Default: 1.

Default: none.

Default: none.

MAILBOX.
Default: N.


changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.

is transferred.
Caution: when a request is submitted by CICS, it is imperative for this
parameter to be set by the program; the model value must not be used.
Default: none.
Default: none.

3.7.7 GENODET: CREATING AN ODETTE ENTRY
The GENODET macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the ODETTE protocol.
GENODET APPL=xxxxxxxx
[,CDATE=xxxxx]
[,CHKDSN={YES|NO}]
[,CTIME=nnnnnn]
[,DUPFILE=x]
[,GETCAR={YES|NO}]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LRECL=nnnnn]
[,PRIOR=n]
[,RECFM=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,SUPPRESS=x]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
[,USERAREA=xxxxxx.......xxxxx]

Default: none.


Y - Check if the file exists while creating the transfer quest.

DEST : Name of the transfer destination site. This site is defined in the routing table
Default: none.

Default: none.

N - The transfer is refused if the source file name is already
recorded in the MAILBOX for the destination site.
Default: N.

is ignored.
Default: none.


Default: N.

Default: none.

minutes.
the Inter.Pel name.

Default: none.

Default: none.

Default: none.
Default: none.

Default: 5.

Default: none.
RETRY : Number of transfer retries to be performed.

This number must be between 1 and 99.
Default: 10.

MAILBOX.
Default: N.

reached.
Default: N.

changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.

is transmitted.
Default: none.
Default: none.

3.7.8 GENPEL: CREATING A PEL ENTRY
The GENPEL macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the PEL protocol.
GENPEL [,APPL=xxxxxxxx]
[,CDATE=xxxxx]
[,CHKDSN={YES|NO}]
[,COMP=n]
[,CTIME=nnnnnn]
[,CUMULMNT=x]
[,DUPFILE=x]
[,GETCAR={YES|NO}]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LRECL=nnnnn]
[,MBR=xxxxxxxx]
[,PRIOR=n]
[,RANG=nnnnnnnn]
[,RECFM=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,SUPPRESS=x]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
[,USERAREA=xxxxx......xxxxx]

Default: none.



COMP : Compression.
0 - No compression.
3 - Compacting (valid for sequential fixed-length records; only
characters that are different from those in the previous record are
transmitted).
4 - Compacting (3) followed by compression (2).
Default: 2.

CUMULMNT : Checksum for bank-type files

N - Inter.Pel does not calculate the checksum.
Default: N.
table.
Default: none.

Default: none.

Y - The source file istransferred as many times as necessary.
Default: N.

is ignored.
Default: none.


Default: N.

During central request deposit, if this parameter is provided, it will be used
to complete the start-of-transmission time in the mailbox record.
Default: none.

minutes.
the Inter.Pel name.

Default: none.

Default: none.

Default: none.

Default: none.
Default: none.

Default: 5.

Default: none.
RANG : Rank assigned to the transfer.


Default: none.

and 99.
Default: 10.

MAILBOX.
Default: N.

When provided for a central request this parameter will be used to complete
the start-of-transmission date field in the mailbox.
reached.
Default: N.

changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.

is transmitted
Default: none.
Default: none.


3.7.9 GENPEL2: CREATING A PEL2 ENTRY
The GENPEL2 macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the PEL2 protocol.
GENPEL2 [,APPL=xxxxxxxx]
[,CUMULMNT=x]
[,CYL=nnn]
[,DSNDEST=xxxxxxxxxxx....xxxxxxx]
[,DUPFILE=x]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,JOBR=xxxxxxxx]
[,LRECL=nnnnn]
[,MBR=xxxxxxxx]
[,MESSAGE=xxxxxxx....xxxxxxx]
[,PRIOR=n]
[,RECFM=x]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,USERAREA=xxxxxx......xxxxxxx]
[,USERDATA=xxxxxxxxxxxxxxxxxxx]
[,USERNAME=xxxxxxxx]
[,UTIL=x]

Default: none.
CUMULMNT : Checksum for bank-type files.

N Inter.Pel does not calculate the checksum.
Default: N.
CYL : Space allocated in cylinders on the sender site for the file generated by the
utility (for a partitioned or VSAM file, the unused space is not released) and
for the pelicanized file (for all types of files, the unused space is released).
The value is between 1 and 999.
For sequential and partitioned files, there is no default value, as the size is
calculated automatically. This parameter must be set for VSAM files.
Default: None.
table.
Default: none.

DSNDEST : Name of the receiver file on the destination site. This keyword is required if
the UTIL=Y option is set and the file to be transmitted is not sequential.
When a sequential file is transmitted, you can specify a GDG file along with
the relative generation number required; if (+1) is set in the generation
number, the current generation plus one is created on the receiver site. If the
file exists on the destination site, it is overwritten; otherwise, disk space is
allocated and the file is catalogued.
Default: none.

Default: none.

N - The transfer is refused if the source file name is already
Default: N.

is ignored.
Default: none.

Default: N.

Default: none.
JOBR : Name of the job to be submitted on the source site when the action report is
received.
Default: none.

Default: none.

Up to 20 MBR parameters can be provided. In this case, this list replaces the
MBRLIST parameter.
Default: none.
MBRLIST : List of the members in a partitioned file to be transferred. A maximum of 20

members can be specified. If all members in a file are to be transferred, this
parameter must be omitted. If the list contains fewer than 20 members, it
must be padded with spaces.
Default: none.

MESSAGE : Accompanying message describing the transfer.
Default: none.

Use the priority channel (Y/N).
Default: N.

Default: none.

MAILBOX.
Default: N.


changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.
Default: none.

USERDATA : User area transmitted to the remote site. When a VSAM file is transmitted,
this area indicates the catalog on the destination site that will be used to
locate the file specified in the DSNDEST keyword.
Example of use consistent with the sample EXRCV001 exit provided in the
SAMPLIB library. This option specifies the name of a member containing
JCL cards with symbolic parameters. When the file is transmitted, the JCL
referenced in this way is resolved and submitted in BATCH mode. In this
case, the data is coded as follows.
01,MBRI,MBRO, where:
MBRI refers to the name of a member containing a symbolic JCL
that can be found in a library on the destination site.
MBRO refers to the name of the member to which the resolved JCL
corresponding to the above-mentioned member is output. If
this name is omitted, Inter.Pel assigns a default name.
If a JCL is to be submitted when a file is received, the UTIL=N keyword
must be declared.
Default: none.
USERNAME : Name of the user authorized to modify files on a specific site (see menu
1.5.B). The TSO USERID is also informed when the action report job has
been completed.
Default: none.
UTIL : Request to activate a utility on the destination site.

Default: N.

3.7.10 GENSIT: CREATING A PeSIT SIT ENTRY
The GENSIT macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the PeSIT SIT protocol.
GENSIT APPL=xxxxxxxx
[,CDATE=xxxxx]
[,CTIME=nnnnnn]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LRECL=nnnnn]
[,NOM=xxxxx]
[,PRIOR=n]
[,RANG=nnnnnnnn]
[,RECFM=x]
[,RELANCE=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,USERAREA=xxxxxxx.......xxxxxx]
APPL : Name of one of the applications defined in the routing table or file type.
Default: none.


table.
Default: none.

Default: none.

is ignored.
Default: none.

HOLD : Transfer hold indicator.
Default: N.

Default: none.

minutes.
the Inter.Pel name.

Default: none.

Default: none.
NOM : PeSIT SIT file name (PI 12).

Default: none.

Default: 1.
RANG : Rank assigned to the transfer.


Default: none.
RELANCE : Authorization to resume an existing SIT transfer. If the value is not a blank
or a binary zero, the transfer is resumed.
Default: the transfer is not resumed.

and 99.
Default: 10.

MAILBOX.
Default: N.


changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.
Default: none.

3.7.11 GENSITH: CREATING A PeSIT HORS SIT ENTRY
The GENSITH macro-instruction is used to create a PROTOCOL-type entry defining the

parameters to be used for the PeSIT Hors SIT protocol.
GENSITH [,ACK=x]
[,APPL=xxxxxxxx]
[,CDATE=xxxxx]
[,CHKDSN={YES|NO}]
[,COMP=n]
[,CTIME=nnnnnn]
[,DUPFILE=x]
[,FILECODE=x]
[,FMTMSG={YES|NO}]
[,GETCAR={YES|NO}]
[,HOLD=x]
[,HSDEB=nnnn]
[,HSFIN=nnnn]
[,INTERVAL=nn]
[,LABEL=xxxxxxxx.......xxxxxx]
[,LRECL=nnnnn]
[,MBR=xxxxxxxx]
[,MODREQ=xxxxxxxx]
[,PRIOR=n]
[,RECFM=x]
[,RETRY=nn]
[,SCRATCH=x]
[,SDATE=nnnnn]
[,SUPPRESS=x]
[,TRACKER={Y|N|S}]
[,TRKCID=id]
[,TRKCIDx=idx]
[,TRKOBJ=object]
[,TYPEREQ=x]
ACK : Request for an acknowledgment message (Y/N) in response to a PeSIT

Hors SIT E message.
Default: N.
11).
Default: none.


COMP : Compression.
0 - No compression.
Default: 2.

table.
Default: none.

Default: none.

N - The transfer is rejected if the source file name is already
Default: N.

the ASCII format.
the ASCII format and converts it from EBCDIC to ASCII at
transmission time.
the EBCDIC format.
the binary format.
Default: E.

is ignored.
Default: none.
FMTMSG : Used for VSAM file transfers only.

Y - During the transfer, additional VSAM information is transmitted to
the remote site at the end of PI 99 (DATA CISIZE (5), INDEX
CISIZE (5), average LRECL (5) and SHR option (2)).
N - Additional information is not transmitted.
Default : N

HOLD : Transfer hold indicator.

Default: N.

Default: none.

minutes.
LABEL : LABEL (PI 37) that will be sent to the remote site in PeSIT Hors-SIT
version E protocol.
Default : None.
the Inter.Pel name.

Default: none.

Default: none.
MBRLIST : List of members in a partitioned file to be transferred. A maximum of 20

member names can be specified. If all members of a file are to be
transferred, this parameter must be omitted.
Default : None.

MODREQ : Inter.Pel mode used to process this request.
B - This request can be transmitted, whether Inter.Pel is the server or
the requester.
R - This request can only be transmitted if Inter.Pel is the requester. It is
not presented if the remote site established the connection and
wishes to read the file.
S - This request can only be transmitted if Inter.Pel is the server, when a
SELECT is received from the remote site that established the
connection and wishes to read the file (never if the connection was
initiated by the local site).
Default: B.

Default: none.

Default: none.
N : PeSIT Hors SIT file name (PI 12).

Default: none.

Default: 1.

Caution: If this site accepts outgoing calls (STOSR=B or STOSR=R), it is
considered as the adjacent site for routing. The transfer will be routed toward this
PROFILE site with the site defined in the DEST parameter as the final destination.
Default: none.
RECFM : Record format (F for a fixed format, V for a variable format)

Default: none.

and 99.
Default: 10.

MAILBOX.
Default: N.


reached.
Default: N.

changes.
with this transfer.
Default : No link.
Sentinel.
Default : No link.
Default : No link.

is transmitted.
M - Message: the PeSIT Hors SIT E message is transmitted. This type of
transfer is the same as the "delayed" mode for files.
Default: none.
Default: none.

3.7.12 SAMPLE MODEL TABLE
NOTE: the sample table can be found in the SAMPLIB library MOD001 member.
*
* EXEMPLE DE CREATION D'UN MODELE COMPRENANT :
*
* 1- UNE ENTREE DE TYPE MODELE AVEC TOUS LES PARAMETRES
* D'UNE DEMANDE DE TRANSFERT (TOUS PROTOCOLES CONFONDUS)
* 2- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE PEL
* 3- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE ETEBAC5
* 4- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE ETEBAC3
* 5- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LES PROTOCOLES
* ETEBAC1 ET ETEBAC2
* 6- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE ODETTE
* 7- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE PESIT
* SIT
* 8- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE PESIT
* HORS-SIT
* 9- UNE ENTREE DE TYPE PROTOCOLE CONCERNANT LE PROTOCOLE PEL2
*
GENMODEL NAME=MODEL01,
CIPH=N,
COMP=0,
CONTRAT=ZZZ951357,
CUMULMNT=N,
DUPFILE=O,
FILECODE=E,
MESSAGE='TRANSFERT PAR MODELE MODEL01'
MSG1=MSG1,
MSG2=MSG2,
NBENR=NBENR,
NOME5=NOME5,
NOM=NOMXX,
ORIGINE=ORIGINE,
PRIOR=9,
RANG=WWWWWWWW,
RECFM=9,
RELANCE=9,
RETRY=XX,
SCRATCH=8,
SDATE=99999,
SEAL=X,
SIGN=X,
SIGNATUR=SIGNATURE,
SUPPRESS=9,
TYPEREQ=7,
VALMAX=1234567890
*
* PEL :
* DEMANDE D'EMISSION VERS LE SITE PARIS D'UN FICHIER
* ASSOCIE A L'APPLICATION FB80, LE TRANSFERT DEVANT
* S'EFFECTUER A PARTIR DE 14H00.
*
GENPEL APPL=FB80,
COMP=3,
CUMULMNT=N,

DEST=PARIS,
DSNORIG=IIIIIIII.FB80.XFER,
HSDEB=1400,
MSG1='STOCK DU 080190',
MSG2=MSG2,
*
* ETEBAC5 :
*
* DEPOT D'UNE DEMANDE DE TRANSFERT D'UN FICHIER DE TYPE 10200120
* DONT LE NOM EST 10F33333333333 VERS LE SITE BANQ1
* LE SITE LOCAL EST CLIENT1
* LA DEMANDE DOIT ETRE EXECUTEE A PARTIR DE 12H30 EN PRIORITE 2
* ET EN COMPRESSION 3
*
GENETEB5 APPL=10200120,
COMP=3,
DEST=BANQ1,
DSNORIG=FICHIER.A.TRANS,
FDATE=FDATE,
HSDEB=1230,
LOCAL=CLIENT1,
NOME5=10F33333333333,
PRIOR=2
*
* ETEBAC3 :
*
* DEMANDE DE TRANSFERT VERS LE SITE SITE1 POUR L'APPLICATION
* CLI1
*
*
GENETEB3 APPL=CLI1,
COMP=0,
DEST=SITE1,
DSNORIG=FICHIER.A.TRANSF,
MSG1=TEST
*
* ETEBAC1/2 :
*
* DEMANDE DE TRANSFERT SENS R VERS LE SITE SITE1 POUR
* L'APPLICATION CLI1, LA DEMANDE DEVANT ETRE EXECUTEE
* IMMEDIATEMENT
*
GENETB12 APPL=CLI1,
COMP=0,
DEST=SITE1,
DSNORIG=FICHIER.A.TRANSFERER,
MSG1=MSG1
*
* ODETTE :
*
* DEMANDE DE TRANSFERT POUR UN NOM-FICHIER ODETTE
* 'CARTE 80C' CORRESPONDANT A UNE APPLICATION INTER.PEL
* FB80. LA ZONE USERDATA DU SSID DEVRA CONTENIR LA
* VALEUR 'SSIDUSER' CELLE DU SFID 'SFIDUSER', LA DEMANDE
* DOIT ETRE EXECUTEE A PARTIR DE 12H30.
*
*
GENODET APPL=FB80,

DEST=RENAULT,
DSNORIG=FIC.DSNAME,
HSDEB=1230,
MSG1='CARTE 80C',
MSG2=SSIDUSER-SFIDUSER
ORIGINE=PARIS
*
* PESIT SIT :
* DEMANDE DE TRANSFERT D'UN FICHIER DE TYPE 023 DONT LE
* NUMERO SIT EST 123 VERS LA STATION IE22, A PARTIR DU
* CTE11, LA DEMANDE DOIT ETRE EXECUTEE A PARTIR DE 12H30
*
GENSIT APPL=023,
DEST=IE22,
HSDEB=1230,
MSG1=TESTS,
N=123,
PRIOR=2
*
* PESIT HORS SIT :
* DEMANDE DE TRANSFERT D'UN FICHIER DE TYPE 023 DONT LE
* NOM EST 'FACTURE' VERS LE SITE NICE,
* LA DEMANDE DOIT ETRE EXECUTEE A PARTIR DE 12H30
*
GENSITH APPL=023,
DEST=NICE,
HSDEB=1230,
MSG1=TESTS,
N=FACTURE,
PRIOR=2,
COMP=3
*
* PEL2 :
* DEMANDE DE TRANSFERT D'UN FICHIER EN PEL2 DONT LE
* MESSAGE EST 'FACTURE' VERS LE SITE CANNES,
* LA DEMANDE DOIT ETRE EXECUTEE A PARTIR DE 12H30
*
*
GENPEL2 APPL=PEL2,
DEST=CANNES,
HSDEB=1330,
MESSAGE=FACTURE

3.8 USER MESSAGES
3.8.1 DESCRIPTION
The user message table is used to change the parameters of an Inter.Pel message (severity,
space compression) and to trigger user-defined processing when this message is generated.
The severity (displayed or not) is set independently for the system log (SWTO parameter) and
Inter.Pel log (SLOG parameter).
Whenever a message is detected, you can trigger one of the following actions:
- Submit a JCL
- Run a user program
- Execute an Inter.Pel procedure
If a JCL is submitted or an Inter.Pel procedure is executed, the JCL or procedure is resolved

before being called with the message parameters.
When procedures are triggered, conditional execution instructions (IF, THEN, ELSE) can be
included to adapt the processing to the conditions in which the message is generated (see the
System Programmer's Reference Manual).
If a JCL is submitted, conditional execution cards ()SEL and )ENDSEL) can be included
to adapt the processing to the conditions in which the message is generated (see the System
Programmer's Reference Manual).
The actions are triggered in asynchronous mode by an Inter.Pel task.
The parameters set for an Inter.Pel message can be used in the JCL or a procedure (P1, P2,
and so on) with the prefix defined in the DELIM parameter.

3.8.1.1 Parameters Passed
The following parameters can be resolved.
Name Contents Length

&P1 First message parameter Message-dependent
&P2 Second message parameter Message-dependent
&P3 Third message parameter Message-dependent
&P4 Fourth message parameter Message-dependent
&P5 Fifth message parameter Message-dependent
&P6 Sixth message parameter Message-dependent
&P7 Seventh message parameter Message-dependent
&P8 Eighth message parameter Message-dependent
&P9 Ninth message parameter Message-dependent
&P10 Tenth message parameter Message-dependent
&XCLUST Cluster name 7
&XDAY Current day 2
&XHH Current hour 2
&XID Address space ID 8
&XMM Current minute 2
&XMONTH Current month 2
&XMSGID Message number 8
&XQQQ Current day in the year 3
&XSTATE Monitor state: 1
I = initializing
N = normal session in progress
T = terminating
&XTYP Type of address space (MON/SRQ/MLB) 3
&XYEAR Current year 4

3.8.2 USER MESSAGE TABLE
This table is loaded when Inter.Pel is started up and can be modified dynamically during a
session (transfer monitor option 6.6 or ALTER command).
The GENUMSG macro-instruction is used to create this table.
GENUMSG MSGID=name (1)

[,ALERT={YES|NO}]
[,BCOMP={YES|NO}]
[,DELIM=c]
[,JCL=name]
[,PROC=name]
[,PROG=name]
[,ROUTCDE=c]
[,SCOPE={NO|I|W|E}
[,SLOG=n]
[,SWTO=n]
[,UPPER={YES|NO}]
ALERT={YES/NO}
YES - The message generates an alert in XFB.Scope or Sentinel.
NO - No alert in XFB.Scope or Sentinel.
If the value of the SCOPE parameter is set to NO, the ALERT
parameter is ignored.
Default: NO.
BCOMP={YES/NO}
YES - The spaces in the messages are compressed.
NO - The spaces in the messages are not compressed.
Default: value of the BCOMP parameter in the GENDEB macro-instruction.
DELIM=c
Prefix for the Inter.Pel message parameters in a JCL to be submitted or in a
procedure to be executed.
Field length: 1 digit.
Example: DELIM=.
Default: &.
JCL=name
Name of the FIJCL member containing the skeleton of the JCL to be
submitted when this message is displayed.
Example: JCL=USERJCL.
Default: none.
MSGID=name
Name of the Inter.Pel message.
Example: MSGID=PEL104.

PROC=name
Name of the FIPROC member containing the skeleton of a procedure to be
executed when this message is displayed.
Example: JCL=USERPROC.
Default: none.
PROG=name
Name of the user program to be run when this message is displayed.
Example: PROG=USERPROG.
Default: none.
ROUTCDE=c
Value (1 to 16) of the ROUTE CODE used for the WTO sending this
message.
Default: value of the ROUTCDE parameter in GENDEB.
SCOPE={NO|I|W|E}
Severity level for call to XFB.Scope or Sentinel:
NO - Do not call XFB.Scope nor Sentinel
I - Information message
W - Warning message
E - Error message
EX : SCOPE=W
Default: NO.
SLOG=n
Severity level determining whether this message is displayed in the Inter.Pel
log (0 - the message is not displayed). This value is compared with the
second digit in the PARM parameter of the PELPARMS file. If it is less, the
Maximum length: 1 digit.
Example: SLOG=7.
Default: value set in the Inter.Pel message table (see Messages & Codes).
SWTO=n
Severity level determining whether this message is displayed in the system
log (0 - the message is not displayed). This value is compared with the first
digit in the PARM parameter of the PELPARMS file. If it is less, the
message is not displayed in the system log.
Maximum length: 1 digit.
Example: SWTO=7.
Default: value set in the Inter.Pel message table (see Messages & Codes).
UPPER={YES/NO}
Y - The messages are displayed in upper-case characters.
N - The messages are displayed in lower-case characters.
Default: value of the GENDEB MSUPPER parameter.
Caution:
The procedures triggered for Inter.Pel startup/shutdown messages must not
include remote commands executed in another address space as it may not
be available (shutdown in progress or completed). See the User Manuel to
check the address space in which the commands are executed.

Note:
Sample tables can be found in the SAMPLIB library UMSG and
ZMSGTAB members. The JCL and the PROC associated with the PEL115
message in the ZMSGTAB sample are provided in the CNTL library
(UMSGL115 and UPROC115 members).

3.8.3 SAMPLE USER MESSAGE TABLE.
A sample user message table can be found in the SAMPLIB library UMSG member.
***********************************************************************
* MESSAGE PELEX01 WILL BE SENT ONLY TO THE SYSTEM LOG *
***********************************************************************
*
GENUMSG MSGID=PELEX01,SWTO=9,SLOG=0
*
***********************************************************************
* MESSAGE PELEX02 WILL BE SENT TO THE SYSTEM LOG AND INTER.PEL LOG *
* THE USER PROGRAM "USRPGM" WILL BE INVOKED *
***********************************************************************
*
GENUMSG MSGID=PELEX02,SWTO=9,SLOG=9,PROG=USRPGM
*
***********************************************************************
* MESSAGE PELEX03 WILL NOT BE SENT TO ANY LOG, *
* BUT THE USER DEFINED JCL "USRJCL" WILL BE SUBMITTED *
***********************************************************************
*
GENUMSG MSGID=PELEX03,SWTO=0,SLOG=0,JCL=USRJCL
*
***********************************************************************
* MESSAGE PELEX04 WILL BE SENT TO DEFAULT LOG, *
* THE BLANK COMPRESSION WILL BE PERFORMED *
* THE USER DEFINED PROCEDURE "USERPROC" WILL BE EXECUTED *
***********************************************************************
*
GENUMSG MSGID=PELEX04,BCOMP=Y,PROC=USRPROC

3.9 INTER-TABLE CORRELATION
3.9.1 ENVIRONMENT AND ROUTING TABLE NAMES
The GENDEB macro-instruction TABROUT parameter in the environment table must

correspond to the NAME parameter in the routing table GENDST0 macro-instruction.
The ENVIR parameter in the routing table GENDST3 macro-instruction must correspond to
the LABEL of the environment table GENDEB macro-instruction.
3.9.2 ADDING A NEW APPLICATION
Add the following macro-instructions:
- GENDST1 Routing table

- GENFILE Environment table
The APPL parameters in these two macro-instructions must be the same.
3.9.3 ADDING A NEW DESTINATION OR SOURCE
- GENDST2 Routing table
For heterogeneous links:
- GENSITE Environment table

- GENTER (If GENTER is not assigned automatically)
The DESTP parameter in the GENDST2 definition must be the same as the NAME parameter
in the GENSITE definition and the SITNAME parameter in the GENTER definition, if
applicable.
For homogeneous MVS-MVS links:
- GENLU Environment table
The DESTP parameter in the GENDST2 definition must be the same as the DEST parameter
in the GENLU definition.
3.9.4 DEFINING AN X.25 ACCESS
A GENLIGN macro-instruction is used in the environment table to define an X.25 access (see
the GENLIGN macro-instruction).
Example:
MCH3651 GENLIGN TYPE=MCH,ACBNAME=ACB01,CVCNB=10

- MCH3651 Name of the MCH LU associated with the X.25 access (X25MCH
macro-instruction LUNAME parameter used in stage 1 of X25NPSI
generation for the access)
- ACB01 Name of the VTAM ACB used for all the connections on the X.25
access
- CVCNB=10 Inter.Pel will control ten switched virtual circuits on this X.25
access. This parameter is used, for example, to limit the number of
simultaneous transfers on the access
3.10 UNIT TABLE
Inter.Pel can allocate files to volumes or units. The volumes are defined in the environment
table (PELPARMS VOL parameter) and the units are declared in a unit table (FLAGDYN).
This table is used to modify the dynamic allocation flags.
It contains the:
* Dynamic allocation flags:
- FLAG1 (2 bytes)
First byte:
X'80' : Only use an existing allocation that has the convertible

attribute to satisfy the request.
X'40' : Do not use an existing allocation to satisfy this request.
X'20' : Do not mount volumes or consider off-line devices. (This bit
overrides S99MOUNT and S99OFFLN in FLAGS2.) If this bit
is one and the request causes a private catalog to be allocated,
mounting will not be allowed for that catalog.
X'10' : Not used by Inter.Pel.
X'08' : Issue a conditional ENQ on the TIOT resource. If the TIOT is
not available, an error code is returned to the user.
Second byte: Reserved.
- FLAG2 (4 bytes)
First byte:
X'80' : Wait for volumes.

X'40' : Wait for DSNAME.
X'20' : Do not reserve (serialize) data sets.
X'10' : Wait for unit.
X'08' : Exclusive TIOT ENQ already performed.
X'04' : Set the special catalog datasets indicator.
X'02' : Volumes may be mounted. The system ignores this bit if
S99NOMNT in FLAGS1 is on. For a batch user, or if a time-
sharing user has the mount attribute in the UADS entry, the
system proceeds as if this bit were on, regardless of the setting.
This setting overrides the NOMOUNT option from the TSO
user attribute data set (UADS).

X'01' : Unitname parameter for DALUNIT is a device type. If you are
using the output from the DEVTYPE macro, be sure the shared
DASD bits are turned off.
Second byte:
X'80' : Allocate a private catalog.
Third byte : Reserved.
Fourth byte : Reserved.
See the System Macros and Facilities Guide for a full description of the
dynamic allocation flags.
* One or more unit name entries

- UNIT NAME (8 bytes)
- VOLUME TYPE (6 bytes)

or
- CL6'SMS '
Each unit name must have a corresponding volume type of the same DEVICE
TYPE as the volumes that can be selected for this unit.
If the volume in the first entry in the table is set to SMS, the files used are controlled
by SMS.
* This table is delimited by an 8X'FF' entry.
This table must be assembled and link-edited with the name FLAGDYN using the REUSE
NORENT options (CNTL library ASMLREUS member).
If the first unit name in the FLAGDYN table contains binary zeros, Inter.Pel does not allocate
a file to a unit name.
If the volume in the first entry is set to SMS, this entry must be the only one in the table, and
all the files used must be controlled by SMS.
A sample table definition can be found in the SAMPLIB library FLAGDYN member.
See the Customizing Exits chapter in the System Programmer's Reference Manual for further
details on how to use this table.

3.11 DEFINING Inter.Pel-CICS CONNECTIONS
3.11.1 OVERVIEW
Inter.Pel can communicate with the CICS transaction subsystem in synchronous mode.
This communication mode is used to deposit a transfer request (transmit or receive) in
Inter.Pel, or, conversely, to receive a file from a remote site directly in CICS, without any
intermediate storage in Inter.Pel.
- Transfer request deposit: a transaction can request that a file be transmitted to Inter.Pel via
a standardized interface. The parameters submitted to this interface are the same as those
used for the other transfer request features (INTBAL, PELICA2) and the type of transfer
request required can also be specified. There are three types of requests.
- Transfer request specifying a catalogued file: the DSNAME of the file to be

transmitted is submitted to the interface by the transaction. Inter.Pel writes
this request directly to the MAILBOX and then triggers the transfer.
- In-stream transfer request with allocation: the data to be transmitted to the

remote site is submitted directly to the interface by the transaction in the
form of a memory address or TS QUEUE. When this data is received,
Inter.Pel creates a sequential file and deposits a request in the MAILBOX
for the file created.
- Synchronous in-stream transfer request: the data to be transmitted to the

remote site is submitted directly to the interface by the transaction in the
form of a memory address or TS QUEUE. When this data is received,
Inter.Pel establishes a physical connection with the remote site, then sends
the records in the "file" to this site in synchronous mode, without any
intermediate storage on the site.
Inter.Pel does not create a file or MAILBOX record for this type of transfer.
It is simply the relay between CICS and the remote site.
This type of request is only available for file transmissions with the
PeSIT SIT and PEL protocols.
In each of these three cases, Inter.Pel sends CICS an action report on the transfer
containing:
- A return code
- An information or error message
- The MAILBOX key created for this transfer
- The parameters set when the request was made
This action report can be sent:

- In synchronous mode; the transaction waits for the action report before
continuing execution
- In asynchronous mode; the transaction continues execution and another
transaction defined in the PELCITER table is triggered when required
This action report is sent at the end of the transfer in the case of a synchronous in-stream
request, and in the other cases, after the request has been written to the MAILBOX.

- Synchronous file reception: for some applications from remote sites, Inter.Pel can be asked
to store the file received in memory. Before acknowledging reception via the protocol,
Inter.Pel triggers a CICS transaction (defined in a table) and transmits the file received to
CICS, in compliance with an internal protocol. If the transaction accepts the file, Inter.Pel
acknowledges the transfer for the remote site via the protocol. This type of reception does
not create a file or write a record to the MAILBOX.
The applications implementing this function, and the characteristics of the transaction
(CICS called, transaction called, message passed to this transaction and so on), are defined
in the Inter.Pel PELTABAP table for the PEL protocol and the PELSITTB table for the
PeSIT SIT protocol (see the Installation and Implementation Guide).
This type of reception is only available for the PeSIT SIT and PEL protocols.
3.11.2 ARCHITECTURE
3.11.2.1 TRANSMISSION REQUEST
To ensure maximum flexibility and ease of implementation, the call to the interface takes
place in the user transaction via a link to the Inter.Pel PELCICSA program that selects a free
link with Inter.Pel and starts a transaction to control the dialog with the monitor (PELCICSB
program). In the case of a request with a synchronous action report, the transaction waits for
the transfer action report, before returning control to the user transaction.
The pool of terminals used to communicate with Inter.Pel and the name of the transaction to
be started are defined in the PELCITER table loaded in CICS.
The PELCICSB program establishes the connection and controls the dialog with Inter.Pel on
the CICS side.

USER
TRANSACTION
LINK PELCICSA PELCICSA
PELCICSB
PELCICSB
START ... PELCICSB
Inter.PEL

3.11.2.2 FILE RECEPTION
If a received file is to be transmitted to CICS, Inter.Pel stores it until the transfer is complete.
Before acknowledging the transfer via the protocol, Inter.Pel selects a terminal connected to
CICS and triggers the transaction associated with the transfer in the PELTABAP (PEL
protocol) or PELSITTB (PeSIT SIT) table. It then establishes a session with CICS to enable
the data to be transferred to the transaction. This dialog is described in the Inter.Pel-CICS
EXCHANGE PROTOCOL section of the User Manuel. At the end of the session, if the
transfer has been accepted by CICS, Inter.Pel acknowledges the transfer for the remote site via
the protocol; if the transfer has not been accepted, Inter.Pel rejects it.
When the file is received, the user transaction takes full control of the dialog.
USER
TRANSACTION
Inter.Pel

3.11.3 CICS DEFINITIONS
3.11.3.1 TRANSFERRING FILES FROM Inter.Pel TO CICS (FILE RECEPTION)
3.11.3.1.1 Macro-instruction definitions
- TCT definition:
R121 DFHTCT TYPE=TERMINAL,

ACCMETH=VTAM,
CHNASSY=YES,
BMSFEAT=(NOROUTE,NOROUTEALL),
BRACKET=YES,
BUFFER=2000,
RUSIZE=1024,
NETNAME=PELOUT01, ================> ACBNAME (Inter.Pel)
GMMSG=NO,
TRMIDNT=R121, ================> 'USER'
TRMMODL=2,
TRMPRTY=255,
TRMSTAT=(TRANSCEIVE),
TRMTYPE=LUTYPE2,
TIOAL=(2400,4000)
- PCT definition for an "NR50" file reception transaction:
DFHPCT TYPE=ENTRY,
PROGRAM=NR50PGM,
TRANSID=NR50,
TPURGE=YES,
SPURGE=YES,
RSL=PUBLIC
- PPT definition for the program attached to the transaction:
DFHPPT TYPE=ENTRY,
PGMLANG=COBOL,
PROGRAM=NR50PGM,
RSL=PUBLIC

3.11.3.1.2 RDO definitions
- TCT definition:
OBJECT CHARACTERISTICS
CEDA View
TYpeterm : PELOLU2
Group : GRPPEL
RESOURCE TYPE
DEVice : LUTYPE2
TERmmodel : 2
SESsiontype :
LDclist :
SHippable : No No ! Yes
MAPPING PROPERTIES
PAGesize : 024 , 080 0-999
ALTPage : 000 , 000 0-999
ALTSUffix :
FMhparm : No No ! Yes
OBOperid : No No ! Yes
PAGING PROPERTIES
AUTOPage : No No ! Yes
DEVICE PROPERTIES
DEFscreen : 024 , 080 0-999
ALTSCreen : 000 , 000 0-999
APLKybd : No No ! Yes
APLText : No No ! Yes
AUDiblealarm : No No ! Yes
COLor : No No ! Yes
COPy : No No ! Yes
DUalcasekybd : Yes No ! Yes
EXtendedds : No No ! Yes
HIlight : No No ! Yes
Katakana : No No ! Yes
LIghtpen : No No ! Yes
Msrcontrol : No No ! Yes
OBFormat : No No ! Yes
PARtitions : No No ! Yes
PRIntadapter : No No ! Yes
PROgsymbols : No No ! Yes
VAlidation : No No ! Yes
FOrmfeed : No No ! Yes
HOrizform : No No ! Yes
VErticalform : No No ! Yes
TEXTKybd : No No ! Yes
TEXTPrint : No No ! Yes
Query : No No ! Cold ! All
OUtline : No No ! Yes
SOsi : No No ! Yes
BAcktrans : No No ! Yes
CGcsgid : 00000 , 00000 0-65535
SESSION PROPERTIES
AScii : No No ! 7 ! 8
SENdsize : 02000 0-30720
RECEivesize : 01024 0-30720
BRacket : Yes Yes ! No
LOGMode :
DIAGNOSTIC DISPLAY
ERRLastline : No No ! Yes
ERRIntensify : No No ! Yes
ERRColor : NO NO ! Blue ! Red ! Pink ! Green !
Turquoise ! Yellow ! NEutral
ERRHilight : No No ! Blink ! Reverse ! Underline
OPERATIONAL PROPERTIES
AUTOConnect : No No ! Yes ! All
ATi : Yes No ! Yes
TTi : Yes Yes ! No
CReatesess : Yes No ! Yes
RELreq : Yes No ! Yes

DIscreq : Yes Yes ! No
Nepclass : 000 0-255
SIgnoff : Yes Yes ! No ! Logoff
MESSAGE RECEIVING PROPERTIES
ROutedmsgs : None All ! None ! Specific
LOGOnmsg : No No ! Yes
APPLICATION FEATURES
BUildchain : Yes No ! Yes
USerarealen : 000 0-255
Ioarealen : 02400 , 04000 0-32767
UCtran : Yes No ! Yes
RECOVERY
RECOVOption : Sysdefault Sysdefault ! Clearconv ! releasesess !
Uncondrel ! None
RECOVNotify : None None ! Message ! Transaction
CEDA View
TErminal : R121
Group : GRPPEL
AUTINSTModel : No No ! Yes ! Only
AUTINSTName :
TERMINAL IDENTIFIERS
TYpeterm : PELOLU2
Netname : PELOUT01
Console : No No ! 0-99
REMOTESystem :
REMOTEName :
Modename :
ASSOCIATED PRINTERS
PRINTER :
PRINTERCopy : No No ! Yes
ALTPRINTEr :
ALTPRINTCopy : No No ! Yes
PIPELINE PROPERTIES
POol :
TAsklimit : No No ! 1-32767
OPERATOR DEFAULTS
OPERId :
OPERPriority : 000 0-255
OPERRsl : 0 0-24,.
OPERSecurity : 1 1-64,.
Userid :
TERMINAL USAGES
TRansaction :
TErmpriority : 255 0-255
Inservice : Yes Yes ! No
PRINTER DATA
SESSION SECURITY
Securityname :
ATtachsec : Local Local ! Identify ! Verify
Bindpassword : PASSWORD NOT SPECIFIED

- PCT definition for an "NR50" file reception transaction:
CEDA View
TRansaction : NR50
Group : GRPPEL
PROGram : NR50PGM
TWasize : 00000 0-32767
PROFile : DFHCICST
PArtitionset :
STatus : Enabled Enabled ! Disabled
PRIMedsize : 00000 0-65520
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
TRProf :
Localq : No ! Yes
SCHEDULING
PRIOrity : 001 0-255
TClass : No No ! 1-10
ALIASES
TAskreq :
Xtranid :
RECOVERY
DTimout : No No ! 1-6800
Indoubt : Backout Backout ! Commit ! Wait
REStart : No No ! Yes
SPurge : Yes No ! Yes
TPurge : Yes No ! Yes
DUmp : Yes Yes ! No
TRACe : Yes Yes ! No
SECURITY
Extsec : No No ! Yes
TRANsec : 01 1-64
RSL : Public 0-24 ! Public
RSLC : No No ! Yes ! External
- PPT definition for the program attached to the transaction:
CEDA View
PROGram : NR50PGM
Group : GRPPEL
Language : Cobol Cobol ! Assembler ! Pli ! Rpg
RELoad : No No ! Yes
RESident : No No ! Yes
RSl : Public 0-24 ! Public
Status : Enabled Enabled ! Disabled

3.11.3.2 TRANSFERRING FILES FROM CICS TO Inter.Pel
(FILE TRANSMISSION)
3.11.3.2.1 Macro-instruction definitions
- TCT definitions:

ACCMETH=VTAM,
CHNASSY=YES,
BRACKET=YES,
BUFFER=30760,
RUSIZE=1024,
NETNAME=PELIN001, ================> ACBNAME (Inter.Pel)
GMMSG=NO,
TRMIDNT=R122, ================> 'USER'
TRMMODL=2,
TRMPRTY=255,
TRMTYPE=LUTYPE2,
TIOAL=(2400,4000)

ACCMETH=VTAM,
CHNASSY=YES,
BRACKET=YES,
BUFFER=30760,
RUSIZE=1024,
NETNAME=PELIN002, ================> ACBNAME (Inter.Pel)
GMMSG=NO,
TRMIDNT=R123, ================> 'USER'
TRMMODL=2,
TRMPRTY=255,
TRMTYPE=LUTYPE2,
TIOAL=(2400,4000)
- PCT definitions for the US01 transaction preparing a transfer request, the US02
transaction receiving the asynchronous action reports and the PEL2 transaction running
on the terminal (R122) associated with Inter.Pel
DFHPCT TYPE=ENTRY,
PROGRAM=PEL1PGM1,
TRANSID=US01,
TPURGE=YES,
SPURGE=YES,
RSL=PUBLIC

DFHPCT TYPE=ENTRY,
PROGRAM=PEL1PGM2,
TRANSID=US02,
TPURGE=YES,
SPURGE=YES,
RSL=PUBLIC
DFHPCT TYPE=ENTRY,
PROGRAM=PELCICSB,
TRANSID=PEL2,
TPURGE=YES,
SPURGE=YES,
RSL=PUBLIC
- PPT definition for the programs attached to the transactions:
DFHPPT TYPE=ENTRY,PGMLANG=COBOL,PROGRAM=PEL1PGM1,RSL=PUBLIC
DFHPPT TYPE=ENTRY,PGMLANG=COBOL,PROGRAM=PEL1PGM2,RSL=PUBLIC
DFHPPT TYPE=ENTRY,PGMLANG=ASM,PROGRAM=PELCICSA,RSL=PUBLIC
DFHPPT TYPE=ENTRY,PGMLANG=ASM,PROGRAM=PELCICSB,RSL=PUBLIC
DFHPPT TYPE=ENTRY,PGMLANG=ASM,PROGRAM=PELCITER,RSL=PUBLIC
3.11.3.2.2 RDO definitions
- TCT definitions:
CEDA View
TYpeterm : PELILU2
Group : GRPPEL
RESOURCE TYPE
DEVice : LUTYPE2
TERmmodel : 2
SESsiontype :
LDclist :
MAPPING PROPERTIES
PAGesize : 024 , 080 0-999
ALTPage : 000 , 000 0-999
ALTSUffix :
PAGING PROPERTIES
DEVICE PROPERTIES
DEFscreen : 024 , 080 0-999
ALTSCreen : 000 , 000 0-999
COLor : No No ! Yes
COPy : No No ! Yes
DUalcasekybd : Yes No ! Yes
PROgsymbols : No No ! Yes

OUtline : No No ! Yes
SOsi : No No ! Yes
CGcsgid : 00000 , 00000 0-65535
SESSION PROPERTIES
SENdsize : 30720 0-30720
LOGMode :
DIAGNOSTIC DISPLAY
AUTOConnect : No No ! Yes ! All
ATi : Yes No ! Yes
TTi : Yes Yes ! No
SIgnoff : Yes Yes ! No ! Logoff
ROutedmsgs : None All ! None ! Specific
Ioarealen : 02400 , 04000 0-32767
UCtran : Yes No ! Yes
RECOVERY
RECOVOption : Sysdefault Sysdefault ! Clearconv ! releasesess !
Uncondrel ! None

CEDA View
TErminal : R122
Group : GRPPEL
AUTINSTName :
TYpeterm : PELILU2
Netname : PELIN001
REMOTESystem :
REMOTEName :
Modename :
ASSOCIATED PRINTERS
PRINTER :
ALTPRINTEr :
PIPELINE PROPERTIES
POol :
OPERATOR DEFAULTS
OPERId :
OPERRsl : 0 0-24,.
Userid :
TERMINAL USAGES
TRansaction :
PRINTER DATA
SESSION SECURITY
Securityname :

CEDA View
TErminal : R123
Group : GRPPEL
AUTINSTName :
TYpeterm : PELILU2
Netname : PELIN002
REMOTESystem :
REMOTEName :
Modename :
ASSOCIATED PRINTERS
PRINTER :
ALTPRINTEr :
PIPELINE PROPERTIES
POol :
OPERATOR DEFAULTS
OPERId :
OPERRsl : 0 0-24,.
Userid :
TERMINAL USAGES
TRansaction :
PRINTER DATA
SESSION SECURITY
Securityname :
- PCT definitions for the US01 transaction preparing a transfer request, the US02
transaction receiving the asynchronous action reports and the PEL2 transaction running
on the terminal (R122) associated with Inter.Pel
CEDA View
TRansaction : US01
Group : GRPPEL
PROGram : PEL1PGM1
TWasize : 00000 0-32767
PROFile : DFHCICST
PArtitionset :
PRIMedsize : 00000 0-65520
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
TRProf :
Localq : No ! Yes
SCHEDULING
ALIASES
TAskreq :
Xtranid :
RECOVERY

DUmp : Yes Yes ! No
SECURITY
TRANsec : 01 1-64
CEDA View
TRansaction : US02
Group : GRPPEL
PROGram : PEL1PGM2
TWasize : 00000 0-32767
PROFile : DFHCICST
PArtitionset :
PRIMedsize : 00000 0-65520
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
TRProf :
Localq : No ! Yes
SCHEDULING
ALIASES
TAskreq :
Xtranid :
RECOVERY
DUmp : Yes Yes ! No
SECURITY
TRANsec : 01 1-64

CEDA View
TRansaction : PEL2
Group : GRPPEL
PROGram : PELCICSB
TWasize : 00000 0-32767
PROFile : DFHCICST
PArtitionset :
PRIMedsize : 00000 0-65520
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
TRProf :
Localq : No ! Yes
SCHEDULING
ALIASES
TAskreq :
Xtranid :
RECOVERY
DUmp : Yes Yes ! No
SECURITY
TRANsec : 01 1-64
- PPT definition for the program attached to the transactions:
CEDA View
PROGram : PEL1PGM1
Group : GRPPEL
CEDA View
PROGram : PEL1PGM2
Group : GRPPEL

CEDA View
PROGram : PELCICSA
Group : GRPPEL
Language : Assembler Cobol ! Assembler ! Pli ! Rpg
CEDA View
PROGram : PELCICSB
Group : GRPPEL
CEDA View
PROGram : PELCITER
Group : GRPPEL
NOTE : if MRO transaction routing is used, it is imperative for the user transaction
(calling PELCICSA), the Inter.Pel transaction (PELCICSB) and the
terminals establishing the connection with Inter.Pel to be defined in the
same CICS.

3.11.4 SETTING Inter.Pel PARAMETERS
3.11.4.1 TRANSFERRING FILES FROM Inter.Pel TO CICS (FILE RECEPTION)
- STARTER definition in the environment table
STARTERS GENLIGN TYPE=STAT

ACBCICS GENTER TYPE=U,SITNAME=CICSO,PROT=ISXFER,
ACBIN=PELOUT01,DEFRESP=1
- Site definition in the environment table

GENSITE NAME=CICSO,GROUP=GROUPEC,TRAILER=N,BUFSIZE=2540
- Routing table definition

GENDST2 DESTP=CICSO,DESTTYP=1
- Note 1 : the number of Inter.Pel-CICS connections is unlimited.
- Note 2 : remember to specify MEMFILE=YES in the GENFILE macro-

instructions using CICS receive connections.
3.11.4.2 TRANSFERRING FILES FROM CICS TO Inter.Pel

(FILE TRANSMISSION)
- STARTER definition in the environment table

STARTERR GENLIGN TYPE=STAT
ACBCICS GENTER TYPE=U,SITNAME=CICSI,PROT=ISCMDTP,
ACBIN=PELIN001,DEFRESP=1
- Site definition in the environment table

GENSITE NAME=CICSI,GROUP=GROUPEC,TRAILER=N,BUFSIZE=30000
- Routing table definition

GENDST2 DESTP=CICSI,DESTTYP=1
- Note 1 : the number of Inter.Pel-CICS connections is unlimited.
- Note 2 : the size of the buffer (BUFSIZE parameter in the GENSITE macro-
instruction) must be the same as the one defined for this connection in
the PELCITER table.

3.11.5 SPECIFIC TABLES
3.11.5.1 LIST OF PEL TRANSFERS TO BE ROUTED TO CICS: PELTABAP
This table lists the applications and sites for which Inter.Pel must route the files received via
the PEL protocol to CICS.
It must be assembled and link-edited as re-entrant.
It is defined using the GENMAPP macro-instruction.
GENMAPP APPL=
DEST=
GROUP=
TRAN=
[,ACCEPT={E|N|Y}]
[,LISTEND={NO|YES}]
[,SIZE={sssss|0}]
ACCEPT =
Procedure to be followed if the connection with CICS is not active.
- N: The transfer is rejected and the connection is aborted.
- Y: A disk file and a MAILBOX record are created.
- E: A memory file is created, but an end-of-transfer time-out may occur.
Default: N.
APPL =
Application name
DEST =
Inter.Pel logical name for the connection with CICS. This connection is
defined in the environment table by a GENTER and GENSITE macro-
instruction.
GROUP =
Name of the group of applications to which the remote site belongs (GROUP
parameter in the GENSITE macro-instruction associated with the remote site).
LISTEND=
YES - Last entry in the table.
Default: NO.
SIZE =
Maximum size in Kbytes of the file that can be stored in memory. If a larger
file is received, Inter.Pel processes it in the usual way.
Caution: the memory area allocated to receive a file is always of this size,
irrespective of the actual file size.
Default: 0.

TRAN =
Transaction code associated with the transfer. This code is sent to CICS to
activate the transaction and transfer the file. It can be of any length. If it
contains spaces, it must be between quotes (for example: 'FIL1 stock').
Default: none.
Sample PELTABAP table definition:
GENMAPP APPL=FB80,DEST=CICSO,GROUP=GROUPEC,
SIZE=1000,ACCEPT=Y,TRAN='NR50PELICAN TO CICS',
LISTEND=YES

3.11.5.2 LIST OF PeSIT SIT TRANSFERS TO BE ROUTED TO CICS: PELSITTB
This table must be assembled and link-edited as reentrant.

It uses the GENSITAP macro-instruction to specify the particular processing required for
certain types of files received (PI 11).
It is defined using the GENSITAP macro-instruction.
GENSITAP TYPE=nnnnn
TRAN={tran|'tran'}
[,ACCEPT={Y|N|E}]
[,DEST=name]
[,LISTEND={YES|NO}]
[,RECFB={F|V}]
[,SIZE={nnn|0}]
ACCEPT = {Y|N|E}
Procedure to be followed if the connection with the subsystem is not active.
- N: The transfer is rejected and a 2/201 abort is sent to the station.
- Y: A disk file and a MAILBOX entry are created.
- E: A memory file is created, but an end-of-transfer time-out may occur.
Default: N.
DEST =name
Logical name of the associated subsystem. This subsystem is defined in the
environment table by a GENTER macro-instruction.
If the link with the subsystem is not active, Inter.Pel processes the file in the usual
way.
Default: no associated subsystem.
LISTEND ={YES|NO}
YES - Last entry in the table.
Default: NO.
RECFB ={F|V}
Procedure to be followed for a fixed format file.
- F : The file is allocated as a fixed format file.
- V : The file is allocated as a variable format file.
Default: F.
SIZE ={nnn|0}
Maximum size in Kbytes of the file that can be stored in memory. If a larger file
is received, Inter.Pel processes it in the usual way.
Caution: the memory area allocated to receive a file is always of this size,
irrespective of the actual file size.
Default: 0.
TYPE =nnnnn
Type of file, numeric, 0 to 65535.

TRAN ={tran|'tran'}
Transaction code associated with the type of file. This code is sent to the
subsystem, before the file is transferred.
This code can be of any length. If it contains spaces, it must be between quotes
(for example: 'FIL1 SIT').
Default: no transaction code.
Sample PELSITTB table definition:
GENSITAP TYPE=00010,DEST=CICSO,
SIZE=1000,ACCEPT=Y,TRAN='NR51PELICAN TO CICS',
LISTEND=YES

3.11.5.3 CICS TRANSACTION AND TERMINAL TABLE: PELCITER
In the CICS to Inter.Pel direction, the PELCITER table provides the Inter.Pel modules in
CICS (PELCICSA and PELCICSB) with the parameters required to run. They are the:
- Terminals used to connect to Inter.Pel

- Transactions to be used
- Size of the communication buffer
- Language in which the messages are written
- Timer values
This table is defined using the GENCICS macro-instruction.
GENCICS TYPE={BEG,TER,END}
[,ASYTERM={term|NONE|SAME}]
[,ASYTRAN={tran|NONE|SAME}]
[,BUFSIZE={nnnnn|2540}]
[,LGE={FR,UK}]
,STARTDL=nnnnn
,TERM=term
,TRAN=tran
,TRANSDL=nnnnn
TYPE = {BEG|TER|END}
Type of macro-instruction.
BEG : First macro-instruction in the table; it defines the general parameters.
It contains the ASYTERM, ASYTRAN, STARTDL and TRANSDL
parameters and, optionally, the BUFSIZE parameter.
TER : Description of a terminal that can be used to establish a connection
between CICS and Inter.Pel. It contains the TRAN and TERM
parameters, and, optionally, the BUFSIZE parameter.
END : Last macro-instruction in the table; it defines the general parameters
and contains the LGE parameter.
Default : none; mandatory parameter.
ASYTERM = {term|NONE|SAME}
Name of the terminal on which the transaction processing the action report is
triggered, if the asynchronous mode is used for a transfer request.
term : Name of a terminal defined in CICS.
NONE : A blind transaction not attached to a terminal is started.
SAME : A transaction is started on the terminal that submitted the request.
Default : NONE.
ASYTRAN = {tran|NONE|SAME}
Name of the transaction that will be triggered to manage the action report, if the
asynchronous mode is used for a transfer request.
tran: Name of a transaction defined in CICS.
NONE: No transaction is triggered.
SAME: The transaction that submitted the request is triggered.
Default : NONE.

BUFSIZE = {nnnnn|2540}
Size of the communication buffer used between CICS and Inter.Pel. This
parameter may appear in the BEG type macro-instruction, where it is the default
size for the other entries, or in the TER-type macro-instructions, where the size is
terminal-specific. The value of this parameter must be from 1200 to 32000.
It must be the same as the value of the BUFSIZE parameter in the GENSITE
macro-instruction defining this connection in Inter.Pel.
Default : 2540.
LGE = {FR|UK}
Language in which the interface messages are to be generated.
UK: The messages are generated in English.
FR: The messages are generated in French.
Default : UK.
STARTDL = nnnn
Maximum period of time, in seconds, during which the PELCICSA program waits
for the transaction establishing communication with Inter.Pel to start. If the
transaction has not started when this period has expired, or if no terminal is
available, the transfer is aborted and the user program is notified.
Default : none; mandatory parameter when TYPE=BEG; otherwise, it must be
omitted.
TERM = term
CICS name of a terminal that can be used to establish a connection with Inter.Pel.
The PELCICSA program selects the first available terminal in the pool defined in
PELCITER to execute the transfer request.
Default: none, mandatory parameter when TYPE=TER; otherwise, it must be
omitted.
TRAN = tran
Name of the CICS transaction that will be triggered on the terminal defined in the
corresponding TYPE=TER entry to set up the connection with Inter.Pel. This
transaction must call the PELCICSB program.
Default : none, mandatory parameter when TYPE=TER; otherwise it must be
omitted.
TRANSDL = nnnn
Maximum wait time, in seconds, for an action report transferred in synchronous
mode. When this period has expired, the user program is informed that the action
report has not been received. The action report is then processed in asynchronous
mode by triggering the transaction defined by the ASYTRAN parameter (if it is
not NONE) on the terminal defined by the ASYTERM parameter. This parameter
can be modified during the transfer request.
A 0 indicates an asynchronous transfer request and the user program is reactivated
when the transaction controlling the transfer has been started.
Default : none, mandatory parameter when TYPE=BEG; otherwise, it must be
omitted.
The PELCITER table therefore comprises:
- One GENCICS TYPE=BEG macro-instruction

- One to n GENCICS TYPE=TER macro-instruction(s) defining the links that can be
established with Inter.Pel
- One GENCICS TYPE=END macro-instruction

Sample PELCITER table:
GENCICS TYPE=BEG,STARTDL=60,TRANSDL=60,
ASYTERM=SAME,ASYTRAN=US02,BUFSIZE=30000
GENCICS TYPE=TER,TERM=R122,TRAN=PEL2,BUFSIZE=30000
GENCICS TYPE=TER,TERM=R123,TRAN=PEL2,BUFSIZE=30000
GENCICS TYPE=END,LGE=FR

3.12 COUPLINGS
3.12.1 PRINCIPLES
Purpose
The coupling services are designed to send messages from Inter.Pel exits to external
applications. The messages are made available via:
- The Inter.Set message transfer manager (SOPRA)

and/or
- The CICS transaction monitor (IBM)
and/or
- The MQSeries message transfer manager (IBM)
Note: Inter.Set, MQS or CICS must be running on the same platform as Inter.Pel. Later in this
document, these products are called the monitor.
Principles
A message transfer request is processed in two phases.
- The message is deposited in a buffer file via a macro-instruction (ISCOM) used

in the exits.
- The message is sent to the destination monitor via a dedicated communication
interface.
These two phases are independent. The message can be deposited, even if the transmission
function is not running.
Deposit function: all Inter.Pel exits can execute deposit functions by using the ISCOM macro-
instruction. The parameters associated with this function are:
- The name of the calling site to determine the request context
- The name of the destination monitor (defined as a site in Inter.Pel)
- The name of the queue defined in Inter.Set, MQS or the name of the target CICS
transaction
- The length and address of the message to be transferred
This function:
- Adds the message to a message file
- Notifies the dedicated communication interface of the transfer request
Message file: the message file contains all the messages to be sent to the destination monitor.
It ensures that the message deposit and transmission functions remain independent.
A message file is required for each connection defined in Inter.Pel.

Each message file is created with a fixed number of records during the installation procedure.
A utility initializes all the records. The size of the record is the size that was selected when the
file was created.
Caution: the size of the record (maximum 32761) determines the maximum size of the
messages that can be transmitted.
This file is used in the same way as a circular queue.
- The messages are added, then processed sequentially.

- When the end of the file is reached, processing is resumed from the beginning of
the file.
Messages for a given destination are sent in the order in which they were deposited. The
destination therefore receives all the messages in that same order, irrespective of the deposit
agent.
Transmission function: the transmission function is executed via a communication interface,

which reads the messages queued in the message file and then transfers them to the monitor
concerned.
This interface is a task that can be started either automatically when Inter.Pel is started up, or
manually (STARTX) when Inter.Pel is running. This task has three phases.
1. The interface is activated: a connection is established with the transfer monitor

and a session is opened.
2. A message is deposited in the message file: a unique identifier or Logical Unit of
Work (LUW) is assigned to the message and the message is sent.
3. The interface is deactivated: the transfer monitor session is closed.

General functional block diagram
Transfer communication
interface send
message
message
deposit file read/upd
message message
ack
Inter.Pel Inter.Set
CICS
MQS
GENERAL COUPLING BLOCK DIAGRAM

3.12.2 IMPLEMENTING COUPLING IN Inter.Pel
3.12.2.1 CREATING AND INITIALIZING THE MESSAGE FILE
An example of a JCL that can be customized can be found in the CNTL file (ISFLINI
member); it is used to create and initialize the message files.
This JCL uses IDCAMS to create the message file (RRDS VSAM without secondary
allocation). It then executes a program to format all the records in the file.
//PEL1 JOB
//PEL2 JOB
//*
//*
//*****************************************************************
//*
//* STEP01 : DELETE/DEFINE VSAM MESSAGE FILE
//*
//* - RECORD SIZE : NNNNN (MAXIMUN 32761)
//* - CI SIZE : SSSSS (MAXIMUN 32768)
//* FOR NUMBERED : CISZ = (N * (RECSZ+3)) + 4
//* N = NUMBER OF RECORDS
//* - FIXED RECORDS
//* - ORGANIZATION : RRDS (NUMBERED)
//* - RECORDS : RRRRR GIVE THE NUMBER OF RECORDS FOR PRIMARY ALLOC
//* (DEPEND OF THE ACTIVITY)
//* NO SECONDARY ALLOCATION
//*
//*****************************************************************
//*
//*
//*
//SYSIN DD *
DELETE (PELSYS.ISTEMP.SYSLAB) CL;
SET MAXCC = 0 ;
DEFINE CLUSTER (NAME(PELSYS.ISTEMP.SYSLAB) -
VOL(2NSY01) -
RECSZ(1000 10000) -
CISZ(32768) -
FSPC( 0 0 ) -
RECORDS( 10 0 ) -
SHR (4 3 ) -
NUMBERED ) ;
//*
//*********************************************************************
//*
//* STEP2 : PROGRAM ISFLINI : INITIALIZE ALL RECORDS OF THE MSG FILE
//* DETERMINE A LUW AAQQQHHMM FOR THE FIRST
//* SLOT AND ADD 1 FOR THE NEXTS
//* FILE ISTEMP : DDNAME OF THE MESSAGE FILE
//* PELPARMS : I.PEL PARAMETERS
//* STATS : JOB REPORT FILE (LRECL=80,RECFM=FB)
//*
//*

//*********************************************************************
//*
//STEP2 EXEC PGM=ISFLINI,REGION=3000K
//*
//STATS DD DISP=SHR,DSN=IIIIIIII.ISFLINI.SYSOUT
//ISTEMP DD DISP=SHR,DSN=IIIIIIII.INTERPEL.ISTEMP
//PELPARMS DD DISP=SHR,DSN=IIIIIIII.INTERPEL.PARM(SYSP01)
//*
3.12.2.2 MODIFYING THE Inter.Pel STARTUP JCL
During the PL6MAIN execution step, the load-module library must be concatenated in a
STEPLIB for each monitor connected (or added in the LNKLIST).
Note: as the Inter.Pel load library must be defined as APF, any new library concatenated in a
STEPLIB must also be defined as such.
For each message file, add the following to the JCL:

1. A first step calling the IDCAMS program to verify each message file
2. A DD card, during the PL6MAIN execution step, so that each message file
can be allocated; the DDNAME specified must correspond to the label in
the GENTER macro-instruction defining the site associated with the
monitor connected
3.12.2.3 UPDATING THE ENVIRONMENT TABLE
Inter.Set connection:
label GENLIGN TYPE=STAT

ddname GENTER TYPE=U,SITNAME=site,PROT=IPIS,
ACBIN=isetacb,ACBOUT=ouracb,
ALTPATH=table
GENSITE NAME=site,GROUP=XXX,TRAILER=N,
BUFSIZE=3000,
ISTATUS=ACT,

CICS connection:

ddname GENTER TYPE=U,SITNAME=site,PROT=IPCICS,
ACBIN=cicsacb,ACBOUT=ouracb
BUFSIZE=3000,
ISTATUS=ACT,
MQS connection:

ddname GENTER TYPE=U,SITNAME=site,PROT=IPMQS,
LOGONS=MQDEF
BUFSIZE=3000,
ISTATUS=ACT,
GENLOGON NAME=MQDEF,VALUE=C'nom.queue.manager/nom
.queue.suivi'
Notes:
_ GENLIGN macro-instruction: static-type starter definition
_ GENTER macro-instruction:
- The label in this macro-instruction (ddname) corresponds to the ddname of

the buffer file allocated in the Inter.Pel execution JCL
- The site name (site) must be defined in a GENSITE macro-instruction and
specifies the monitor connected. For Inter.Set coupling, the site name
corresponds to the application used during the connection.
- The IPIS protocol must be used for an Inter.Set connection, IPCICS for a
CICS connection, or IPMQS for an MQSeries connection.
- ACBIN= name of the ACB dedicated to the monitor.
- ACBOUT= name of the ACB used by Inter.Pel to connect to the monitor.
- LOGONS= (IPMQS protocol only). It identifies a GENLOGON definition
specifying the names of the queues used for the connection and the
exchange security option. This parameter is optional. If it is not set, the
default queue manager is used and the exchanges apply the single-phase
commit mode.
- ALTPATH= (IPIS protocol only). This parameter specifies the name of a
translation table used to convert the contents of messages received in
Inter.Set (for example, the EBCDIC/ASCII conversion table).
This table must be accessible in the remote Inter.Set.
This parameter is optional. If it is not set, the messages received are written
to the target queue without being converted.
_ GENSITE macro-instruction: the name of the site specifies the monitor defined
in the previous GENTER macro-instruction

_ GENLOGON macro-instruction: the names of two MQS queues separated by the
"/" character without spaces can be declared in the VALUE parameter; the first
name represents the queue manager used for the connection and the second the
backup queue used for secure exchanges (two-phase commit in the communication
process)
- The following formats are available.
VALUE=C'/': no values entered. The default queue manager is

used but no two-phase commit. This has the same
effect as not setting the LOGONS parameter in the
GENTER macro-instruction.
VALUE=C'queue.manager.name/backup.queue.name': both queue names are
entered. The connection is established with this
queue and the exchanges are protected by the
backup queue specified.
VALUE=C'/backup.queue.name': only the name of the backup queue is
specified. The connection is established with the
default queue manager and the two-phase commit
uses the queue specified.
VALUE=C'queue.manager.name/': only the name of the queue manager to be
used when the connection is established is specified.
There is no two-phase commit to protect the
exchanges.
3.12.2.4 STARTING THE COMMUNICATION TASK
Each communication task defined must be started after Inter.Pel is started up. The STARTX
startup command can be added in the initial procedure (PROCI).
Messages that have been deposited remain pending in the message files until the task has been
started.
Note: messages can be deposited in the corresponding buffer file, even if a task has not been
started.
3.12.3 Inter.Set DEFINITIONS
The communication interface in Inter.Pel uses the standard Inter.Set API. The BATCH
connection mode is used.
An ENG service (type=COUPLING) must be created (see the Inter.Set MVS - COUPLING
with Inter.Pel Technical Guide).
The coupling ENG service comprises a queue dedicated to the Inter.Pel communication
process connection within the scope of the PEL-SET coupling. This queue must be specified
when messages are deposited in the buffer file. The name of the destination message queue
must also be declared in Inter.Set.

Sample Inter.Set definition:
C330 2.5 ------------- EXTERNAL NETWORK GATE DETAILS --------------- V 3.4.1

DISPLAY Page 01
ENG Name : SYSLAB Version : 0009

ENG Type : COUPLAGE Status : A
Authorizer/Modifier : ITSUSE01
Description.......... couplage syslab pel

Auto Start........... Y
Communications Log... Y
Request Application.. PELSET

Response Application. PELSET
System Identification XYZLAB
Delivery Request QSet PELMSG

Delivery Done QSet... PELFIC
User Exit............ CCICPLEX
-----------------------------------------------------------------------------
PF1 HELP PF3 EXIT PF8 NEXT PAGE
C330 2.5 ------------- EXTERNAL NETWORK GATE DETAILS --------------- V 3.4.1

DISPLAY Page 02
ENG Name : SYSLAB Version : 0009

ENG Type : COUPLAGE Status : A
Authorizer/Modifier : ITSUSE01
Home Logical Unit.... A000IT01

Remote LU............ PELOUT01
-----------------------------------------------------------------------------
PF1 HELP PF3 EXIT PF7 PREVIOUS PAGE
Note: the coupling ENG service is defined as follows.
- "Response Application": queue used for the connection. This value must be
declared in the GENTER macro-instruction (SITE parameter) of the
Inter.Pel definition associated with Inter.Set.
- "System Identification": Inter.Pel identifier connected.
- "Home Logical Unit": VTAM LU used by Inter.Set in the communication.
This value must be declared in the GENTER macro-instruction (ACBIN
parameter) of the Inter.Pel definition associated with Inter.Set.
- "Remote LU": VTAM LU used by Inter.Pel for communications with
Inter.Set. This value must be declared in the GENTER macro-instruction
(ACBOUT parameter) of the Inter.Pel definition associated with Inter.Set.

3.12.4 CICS DEFINITIONS
The communication interface is connected to CICS (via VTAM) and sends the message in the
3270 format.
The connections between Inter.Pel and CICS are defined as a terminal in CICS.
- Macro-instruction definition:

ACCMETH=VTAM,
CHNASSY=YES,
BRACKET=YES,
BUFFER=0,
RUSIZE=5000,
NETNAME=A000ITC1, ================> ACBNAME (Inter.Pel)
COMPAT=NO,
GMMSG=NO,
PGESTAT=PAGE,
TRMIDNT=ITS1, ================> 'USER'
TRMMODL=2,
TRMPRTY=255,
TRMTYPE=LUTYPE2,
TIOAL=(2000,6000)
- RDO definition:
CEDA VIew
TErminal : ITS1
Group : GRPPEL
AUTINSTName :
TYpeterm : ITSTTER
Netname : A000ITC1
REMOTESystem :
REMOTEName :
Modename :
ASSOCIATED PRINTERS
PRINTER :
ALTPRINTEr :
PIPELINE PROPERTIES
POol :
OPERATOR DEFAULTS
OPERId :
OPERRsl : 0 0-24,...
OPERSecurity : 1 1-64,...

Userid :
TERMINAL USAGES
TRansaction :
PRINTER DATA
SESSION SECURITY
Securityname :
CEDA View
TYpeterm : ITSTTER
Group : GRPPEL
RESOURCE TYPE
DEVice : LUTYPE2
TERmmodel : 2
SESsiontype :
LDclist :
MAPPING PROPERTIES
PAGesize : 024 , 080 0-999
ALTPage : 000 , 000 0-999
ALTSUffix :
PAGING PROPERTIES
+ DEVICE PROPERTIES
DEFscreen : 024 , 080 0-999
ALTSCreen : 000 , 000 0-999
COLor : No No ! Yes
COPy : No No ! Yes
+ DUalcasekybd : Yes No ! Yes
+ PROgsymbols : No No ! Yes
+ OUtline : No No ! Yes

SOsi : No No ! Yes
CGcsgid : 00000 , 00000 0-65535
SESSION PROPERTIES
SENdsize : 00000 0-30720
LOGMode :
DIAGNOSTIC DISPLAY
+ AUTOConnect : No No ! Yes ! All
ATi : Yes No ! Yes
TTi : Yes Yes ! No
SIgnoff : No Yes ! No ! Logoff
+ ROutedmsgs : None All ! None ! Specific
Ioarealen : 02000 , 06000 0-32767
UCtran : No No ! Yes
RECOVERY
+ RECOVOption : Sysdefault Sysdefault ! Clearconv ! releasesess !
Uncondrel ! None

Sample definition of an RMSG message reception transaction:
DFHPCT TYPE=ENTRY,
PROGRAM=PELCIC1,
TRANSID=RMSG,
TPURGE=YES,
SPURGE=YES,
RSL=PUBLIC
- RDO definition:
CEDA View
TRansaction : RMSG
Group : GRPPEL
PROGram : PELCIC1
TWasize : 00000 0-32767
PROFile : DFHCICST
PArtitionset :
PRIMedsize : 00000 0-65520
REMOTE ATTRIBUTES
REMOTESystem :
REMOTEName :
TRProf :
Localq : No ! Yes
SCHEDULING
ALIASES
TAskreq :
Xtranid :
RECOVERY
DUmp : Yes Yes ! No
SECURITY
TRANsec : 01 1-64
Sample definition of the program attached to the transaction:
DFHPPT TYPE=ENTRY,
PGMLANG=COBOL,
PROGRAM=PELCIC1,
RSL=PUBLIC

- RDO definition:
CEDA View
PROGram : PELCIC1
Group : GRPPEL
3.12.5 MQSeries DEFINITIONS
The destination application queues specified in the ISCOM macro-instruction must exist.
If the queue manager and/or backup queue names are specified in a GENLOGON macro-
instruction, ensure that these permanent queues exist.
Queue name : SOPRDJ.CRE.EM1

Description : QUEUES RDJ
Def_Persistence : YES
Def_priority : 0
backout_QName :
Date Create : 1997-01-16 11.35.42
Initq Queue : SOPRDJ.TRIGAPPL
Process Name : SOPRDJ.PRDJEXP
Trigger Data :
Backout_TH : 0
Input_Option : 4
Definition_Type : 4
Harden_Get_Bk : 1
Max_Lng_Length : 33000
Max_Queue_Depth : 5000
Trigger Ctrl : TRIGGER
Trigger Depth : 10
Trigger Prio : 0
Trigger Type : DEPTH
Queue Usage : NORMAL
Input_Count : 0
Output_Count : 0
Queue_Depth : 0

3.12.6 VTAM DEFINITION
The following sample VTAM definition describes an ACB used by Inter.Pel for its outgoing
connections with the monitors.
*
* MAJOR APPLICATION NODE
*
VBUILD TYPE=APPL
PELIN002 APPL AUTH=ACQ,EAS=5

APPENDIX A USING THE X25NPSI PCNE FUNCTION
A.1 INTRODUCTION
The PCNE function is designed for data communication between an application program and
non-SNA equipment connected to the X.25 network. This equipment can be:
- A non-IBM terminal
- A non-IBM processor
- An IBM processor with a 37X5 running X25NPSI-PCNE
IBM IBM
N P P N
X.25
P C C P
Inter.Pel network Inter.Pel
S N N S
I E E I
X.25 Inter.Pel
interface interface
FIGURE A1: CONNECTIONS
ACF/VTAM sees the connected equipment as a PU type 1/LU type 1 pair.

Only one LU can be associated with the PU. This means that only one PU-LU pair can be
associated with a virtual circuit. The USER DATA field of the call packet from the X.25
equipment must contain:
- X'C0' representing the type of LLC (in this case PCNE)

- Followed by 5 digits representing the caller IDNUM
This IDNUM+1 must be found in one of the PUs of an active major switched node on the
called VTAM side (see the example below).
Installation and Implementation Guide Using the X25NPSI PCNE Function A-1
PVC
NCP PVC NCP

V SVC1 V
P P
T P P T
E X.25 E
A C SVC1 C A
L network L
M N N M
A E SVC2 E B
A B
SVC2
37x5 SVC3
37x5
Processor A Processor B
FIGURE A2: PCNE-PCNE CONNECTIONS
NOTES: VTAM A can open only three sessions (three SVCs); VTAM B can open only
two.
The two processors do not necessarily belong to the same SNA CROSS-
DOMAIN network.
A.2 MAJOR SWITCHED NODE TABLE
The switched node resource table contains the names and properties of the SNA entities
representing these resources.
Amongst these properties are the:
- PU and LU names
- IDNUM and IDBLK identifications
- X.25 dial number
- X.25 call facilities
A.3 MAJOR SWITCHED NODE DEFINITION EXAMPLE
The following example can be applied to the connection diagram in Figure A2.
COMPUTER A COMPUTER B
PU1 PU ... PUX PU ...

IDBLK=003 IDBLK=003
IDNUM=00001 IDNUM=00001
PATH1 PATH ... PATHX PATH ...
DIALNO=1750010010++++ DIALNO=1840020020++++
LU1 LU ... LUX LU ...
PU2 PU ... PUY PU ...
IDBLK=003 IDBLK=003
IDNUM=00002 IDNUM=00002
LU2 LU ... LUY LU ...
NOTES: IDBLK=003 is mandatory for PCNE resources.

The PATH declaration is optional.
Two PU-LU pairs must be defined: one to call and the other to be called.
The tables shown above illustrate the connection operation sequences.
The call facilities defined in the X.25 network are invoked via the ++++ bytes
in the dial number (closed user group for example).
A.4 SEQUENCE OF OPERATIONS
Example based on Figure A2:
1) Inter.Pel A sends VTAM an OPNDST ACQ LU=LU1 macro-instruction.
2) VTAM and NCP assign an SVC (the highest NVL, in this case, NCP A SVC3) to the
LU1 SNA resource.
3) The X.25 dial number in the PATH declaration associated with the PU1-LU1 pair is
used by VTAM and NCP to build the call packet. The C000002 digits (C0 followed
by IDNUM + 1) are located in the USER DATA field.
4) The receiver NCP analyzes the call packet and transmits the IDNUM to VTAM. In
the example, IDNUM 00002 identifies the SNA PUY-LUY resources.
5) The connection process on the X.25 and SNA levels is now complete. The following
SNA sessions are active:
- VTAM A <---------> PU1

- VTAM A <---------> LU1
- PELI.A <---------> LU1
- VTAM B <---------> PUY
- VTAM B <---------> LUY
6) Inter.Pel A then sends VTAM A a SEND macro-instruction containing a character

string representing the LOGON to Inter.Pel B.
7) VTAM B interprets the character string using a USSTAB and builds the standard
LOGON: LOGON APPLID(PELICANB) LOGMODE(..) DATA(.)
8) Inter.Pel B accepts the LOGON. All the sessions are now open, particularly:
- Inter.Pel B <---------> LUY

- Inter.Pel A <======> Inter.Pel B
A.5 SUMMARY DIAGRAM
I I
n PU PU n
t t
V V
e e
T X.25 T
r r
A A
. .
M M
P P
e LU LU e
l l
SNA sessions
Inter.Pel session
APPENDIX B USING THE X25NPSI GATE FUNCTION
B.1 X25NPSI GENERATION
The stage 1 parameters for X25NPSI generation must be defined before the NPSI GATE
function can be used.
..... X25MCH ADDRESS=...,

GATE=GENERAL,
SUBADDR=YES,
LLC0=0,LLC2=2,LLC3=3,LLC4=4,LLC5=5,
LLCLIST=(LLC0,LLC2,LLC3,LLC4,LLC5),
LUNAME=.......
NOTES: - LLC0 values are for information purposes only, to connect to the GATE
function, the caller must add a 4 to the X.25 dial number (LLC4=4 ).
- A full generation example can be found in the SAMPLIB library
NPSISRC member.
B.2 MAJOR SWITCHED NODE
Sample node associated with an X.25 GATE access
VBUILD MAXGRP=4,MAXNO=1,TYPE=SWNET
P...1 PU ADDR=01,PUTYPE=1,IDNUM=....2,IDBLK=003,DISCNT=YES,
MAXDATA=5000,ISTATUS=ACTIVE,PACING=(1,1)
L...1 LU LOCADDR=0,TERM=TWX
P...2 PU ADDR=01,PUTYPE=1,IDNUM=....4,IDBLK=003,DISCNT=YES,
MAXDATA=5000,ISTATUS=ACTIVE,PACING=(1,1)
L...2 LU LOCADDR=0,TERM=TWX
NOTE: - the IDNUM values depend on the installation.
Installation and Implementation Guide Using the X25NPSI Gate Function B-1
APPENDIX C USING SMS
C.1 SETTING INTER.PEL PARAMETERS
To allows files allocation without declaring volumes and units, FLAGDYN table must be
defined as follows.
It must have only one entry, the first volume of which must be set to SMS.
Sample FLAGDYN table:
FLAGDYN CSECT
DC X'0000' flag1
DC X'00000000' flag2
DC XL8'00' no unit name
DC CL6'SMS' no volume
DC 8X'FF' end of table
END
- PELPARMS VOL parameter:
This parameter is optional when SMS is enabled in the FLAGDYN table. If no volume is
specified, track balancing and BLKSIZE optimization are performed by SMS when files are
allocated; if at least one volume is specified, Inter.Pel performs these operations and applies
the properties of the first volume specified, before allocating any files.
Even when SMS if fully used (no VOL parameter), if the GENFILE BLKSIZE is different
from AUTO or 0, the SMS track balancing is not performed. The block size provided in the
GENFILE macro is used to create the reception file.
Caution: the default FLAGDYN table delivered with Inter.Pel indicates the use of SMS.
C.2 CONSTRAINTS
All files created by Inter.Pel must be controlled by SMS.
The security checks performed on the files must only applied to the first index level.
Installation and Implementation Guide Using SMS C-1

APPENDIX D USING LU 6.2
D.1 INTRODUCTION
Role of LU 6.2
The role of LU 6.2 can be understood by comparing it with the other types of LUs:
- Type 0: No FMD (session presentation services)

The profile depends on how it is implemented
- Type 1: For terminals operating in line mode and using the SNA character string (SCS)
- Type 2: For terminals operating in page mode and using the 3270 data stream
- Type 3: For printers using the 3270 data stream
- Type 4: For data or word processing using the SNA Character String (SCS)
- Type 6: For inter-program communication
- Type 7: For desktop terminals using the 5250 data stream
The various types of LUs do not have session presentation services (SPS) or a specific SPS
(SCS, DS 3270, DS 5250, and so on). LU 6.2 is designed for distributed processing and
program-to-program communication. For this type of LU, the SPS is determined dynamically.
LU 6.2 Autres LU's
Dynamic
SPS
SPS
DFC DFC
TC TC
FIGURE A3: LU architecture
Installation and Implementation Guide Using LU 6.2 D-1

SPS: Session Presentation Services.
SNA character string, directory code (such as EBCDIC, ASCII), FM header.
DFC: Data Flow Control.

Request/Response modes, half duplex, full duplex, and so on.
TC: Transmission Control.

RU size, pacing, cryptography options, and so on.
LU 6.2 has thus put an end to the proliferation of different LU types and achieved
convergence on the following points:
- A single LU architecture
- Architectured system services
- Any-to-any communication
- Flexible, open protocols
- A single API in the form of a pseudo language
LU 6.2 sessions
In the SNA environment, two LUs communicate on a session or logical connection

established when the BIND is sent by the primary LU (PLU) to the secondary LU (SLU).
In the LU 6.2 mode, this BIND can be negotiated and LU A can have several sessions with
LU B as PLU or SLU, depending on the session. When a session is opened, an ALLOCATE
command is used to start a conversation between two applications. A Begin Bracket command
is sent at SNA level, and in the event of contention, the contention winner beats the contention
loser.
Each session belongs to a mode name, which defines a BIND to establish particularly the
correspondence between the PLU and the contention winner/loser.
TP A TP B
ALLOCATE
Session 1
Session 2
LU 6.2 A LU 6.2 B
Sessions i: LU6.2 sessions opened with mode name i
LU 6.2 conversation
FIGURE A4: LU 6.2 connections

D.2 VTAM DEFINITIONS
Sample mode table definition
MPELLU62 MODETAB
LPELLU62 MODEENT LOGMODE=LPELLU62,TYPE=0,FMPROF=X'13', *
TSPROF=X'07',PRIPROT=X'B0',SECPROT=X'B0', *
COMPROT=X'D0B1',ENCR=B'0000', *
RUSIZES=X'C8C8', *
PSERVIC=X'060200000000000000002300', *
COS=.....
MODEEND
END
NOTE: TYPE=0 means that the BIND can be negotiated.

The logmode must be known to both the source and destination.
Sample ACB definition
PELLU62A APPL AUTH=(ACQ,,PASS),EAS=10,PARSESS=YES,APPC=YES, *

VPACING=3,AUTOSES=8,DSESLIM=11,DMINWNL=8, *
DMINWNR=3 [,LIMQSINT= ] [,ATNLOSS= ]
PELLU62B APPL AUTH=(ACQ,,PASS),EAS=10,PARSESS=YES,APPC=YES, *
VPACING=3,AUTOSES=5,DSESLIM=12,DMINWNL=8, *
DMINWNR=4 [,LIMQSINT= ] [,ATNLOSS= ]
NOTE:
DSESLIM = Total number of sessions opened for a mode name.
DMINWNL = Maximum number of contention winner sessions opened for the local
LU and for a mode name.
DMINWNR = Maximum number of contention winner sessions opened for a remote

LU 6.2 and for a mode name.
AUTOSES = Maximum number of contention winner sessions to be started up

automatically for the local LU 6.2 when a connection is established.
VPACING = Data flow control parameter.

LIMQSINT = Time-out value to close contention winner sessions not used by a
conversation (0 closes the sessions as soon as the conversation ends).
It is similar to the LIMRES parameter for a switched node PU.
ATNLOSS = LAST/ALL (LAST is the default setting); it records an end-of-session

message in the Inter.Pel log when the last session for a mode name is
closed (LAST value) or when each session for a mode name is closed
(ALL value).
When connections are established between two IBM main-frame systems (MVS, VM, VSE),
one must be defined PLU (DMINWNR=0) and the other one SLU (DMINWNL=0). If the
definitions do not match this rule, connection will never be established and will stay in a
Pending Notify Session state.
Sample major switched node definition
XSOPRA VBUILD TYPE=SWNET,MAXNO=1,MAXGRP=1
PUTRI1 PU ADDR=01, *
PUTYPE=2, *
IDBLK=..., *
IDNUM=....., *
LIMRES=NO, *
DISCNT=NO, *
XID=YES, *
SSCPFM=FSS, *
ISTATUS=ACTIVE, *
PACING=3, *
VPACING=3
LUTRI1 LU LOCADDR=0, *
MODETAB=MPELLU62, *
DLOGMOD=LPELLU62
NOTE:
LOCADDR=0 is mandatory.
LIMRES=YES is used to close LU 6.2 sessions when no conversation has been taking
place or, if the LIMQSINT parameter is set in the application ACB, when
the corresponding time-out has expired.
LIMRES=NO (default value) is used to maintain LU 6.2 sessions even if no
conversation is taking place.

Sample LU 6.2 session setup
Hypothesis:
Inter.Pel opens sessions between two LU 6.2s: LU A and LU B. The VTAM parameters are:
For LU A: DSESLIM=11,AUTOSES=8,
DMINWNL=8,DMINWNR=3
For LU B: DSESLIM=12,AUTOSES=5,
DMINWNL=8,DMINWNR=4
Negotiation:
When Inter.Pel opens a session, negotiation takes place as follows:

- w= smaller of (DSESLIM A, DSESLIM B)=11
w is the maximum number of sessions between A and B.
- x= larger of ([w/2], DMINWNR B)=5
x is an intermediate result used to calculate y.
- y= smaller of (x, DMINWNL A)=5
y is the number of contention winner sessions for A.
- z= smaller of (w-y, DMINWNL B)=6
z is the number of contention winner sessions for B.
Execution:
The parameters actually used during the session will therefore be:
For LU B: DSESLIM=11,AUTOSES=5
DMINWNL=6,DMINWNR=5
VTAM will open five contention winner sessions from B to A .
For LU A: DSESLIM=11,AUTOSES=8
DMINWNL=5,DMINWNR=6
VTAM will open five contention winner sessions from A to B.
In this example, DSESLIM (11) is equal to w obtained from the negotiation, DMINWNL (6)
is equal to z and DMINWNR (5) is equal to y.

Sample definition on a remote station
Local station name: EUROPE.LUTRI1 (in the NETID.LUNAME form)
NETID = Name of the network to which the switched node LU

defined on the HOST as LUNAME belongs (in this
example, LUTRI1 belongs to the EUROPE network).
LUNAME = Name of the switched node LU defined on the HOST

(LUTRI1 in this example).
Note: if several LUs are defined under the switched node
PU, one of the available LUs can be reserved.
Name of the partner LU: EUROPE.PELLU62A (in the NETID.ACBNAME form)
NETID = Name of the network to which the remote application

ACB on the HOST belongs (in this example, PELLU62A
belongs to the EUROPE network).
ACBNAME = Name of the ACB defined on the HOST (PELLU62A in

this example).
Note: two different stations, which therefore have two
different local LUs (for example LUTRI1 and LUTRI2),
can open LU 6.2 sessions simultaneously with the same
remote LU (PELLU62A in this example).
Local node identifier: field 1, field 2 (used in the XID)

For switched connections (QLLC or SNA)
Field1 = IDBLK (hexadecimal) set on the switched node PU.
Field2 = IDNUM set on the switched node PU.
LOGMODE: LPELLU62 (modename)

Modename = Name of the LOGMODE; it must be the same as the name
defined on the HOST (LPELLU62 in this example).
The parameters defining the number of sessions to be opened and the number of contention
winner and/or contention loser sessions must be consistent with the DSESLIM, DMINWNL
and DMINWNR parameters of the ACB identifying the remote LU. Thus, in the example of a
connection to PELLU62A, the total number of sessions must be 11, the number of contention
winner sessions must be 3 and the number of contention loser sessions must be 8 (see the LU
6.2 ACB definition example).

D.3 INTER.PEL DEFINITIONS
Sample environment table
STARTER3 GENLIGN TYPE=LU62,LOCK=Y,ACBNAME=PELLU62A

GENTER TYPE=U,SITNAME=DUMMYP,PROT=PEL,
NUMBER=30,SESSON=2,DEFRESP=NO,
LOGMODE=LPELLU62
GENSITE NAME=DUMMYP,GROUP=UNX,TRAILER=N,
BUFSIZE=3000,LINGRP=STARTER3,
ISTATUS=ACT,COMPACT=YESN
GENSITE NAME=PELIUNIX,GROUP=UNX,TRAILER=N,
ISTATUS=ACT,COMPACT=YESN,MAXCON=10,
LUIN=LUTRI1,LUOUT=LUTRI1,FILESIZ=E,
ALTLOCN=NETLU62A,TPNAME=PELCPICR
GENSITE NAME=NETLU62A,GROUP=UNX,TRAILER=N,
GENSITE NAME=NETLU62B,GROUP=UNX,TRAILER=N,
LUIN=PELLU62B,LUOUT=PELLU62B,FILESIZ=E,
ALTLOCN=NETLU62A
GENFILE GROUP=UNX,APPL=FB80,LRECL=80,RECFM=FB,
BLKSIZE=AUTO,EMPTY=Y
GENFILE GROUP=UNX,APPL=PEL1,LRECL=0,RECFM=U,
BLKSIZE=AUTO
NOTE:
- For LU 6.2, LOGMODE is a mandatory parameter of the GENTER macro-instruction.
It must be the same as the one defined on the remote site.
- TPNAME must be set in the GENSITE macro-instruction when the remote site is an
Inter.Pel station based on the V6.x Inter.Pel portable layer (such as Peliunix, Pelios2,
Peli-NT). The possible values are:
- PELCPICR for the PEL protocol
- PHECPICR for the PeSIT Hors SIT protocol, version E
- PHDCPICR for the PeSIT Hors SIT protocol, version D
- For PeSIT protocols, the GENTER SITWND parameter must always be coded to 1.

Sample routing table
GENDST2 DESTP=PELIUNIX,DESTTYP=1
GENDST2 DESTP=NETLU62B,DESTTYP=1
GENDST2 DESTP=NETLU62A,DESTTYP=0

D.4 INTER.PEL TRACES IN LU 6.2 MODE
Sample NET, SUM type site trace
This site trace is used for debugging purposes and traces the request buffers originating from
the protocol tasks. Its format is:
mmmmmmmm BUFFER TRACE AT:aaaaaaaa,LEN:llll,PT:cccccccc

0000 rq000000 bbbbbbbb 000000rc
where:
mmmmmmmm = Name of the presentation and service automaton module processing
the request
Example: SMAPS562 Request deposit module
SMAPS662 Processing module
aaaaaaaa = Address of the request buffer
llll = Buffer length
cccccccc = LU 6.2 conversation identifier
rq = Request identifier
01 Allocate
02 Send
03 Receive
05 Deallocate
07 Stop task
09 Initiate request
bbbbbbbb = Address of the LU 6.2 buffer
rc = Request return code
00 Request successful
04 Request failed
039 07:28:57 STALIGN/STARTER3

039 07:28:57 PEL678 LINE HANDLER : PELGTG62 NOM : STARTER3 LANCE, CTR=0006
039 07:28:57 STARTX/NETLU62A
039 07:28:57 PEL707 STARTER3 OUVERTURE ACB OK : PELLU62D
039 07:28:57 PEL770 STARTER3 INITIALISATION OK
039 07:28:57 STARTX/NETLU62B
039 07:28:58 TRACE/NETLU62A,ON,NET,SUM
039 07:28:58 TRACE POUR : NETLU62A - NETWORK : ON /SUM - PROTOCOL : OFF/SUM - F
039 07:29:58 PEL880 STARTER3 SESSION OK CID:01000003,PLU:PELLU62C,SLU:PELLU62D
039 07:29:59 PEL880 STARTER3 SESSION OK CID:01000009,PLU:PELLU62D,SLU:PELLU62C
039 07:29:59 PEL880 STARTER3 SESSION OK CID:0100000A,PLU:PELLU62D,SLU:PELLU62C
039 07:29:59 PEL880 STARTER3 SESSION OK CID:0100000B,PLU:PELLU62D,SLU:PELLU62C
039 07:29:59 PEL880 STARTER3 SESSION OK CID:0100000C,PLU:PELLU62D,SLU:PELLU62C
039 07:29:59 PEL880 STARTER3 SESSION OK CID:0100000D,PLU:PELLU62D,SLU:PELLU62C
039 07:29:59 PEL880 STARTER3 SESSION OK CID:0100000E,PLU:PELLU62C,SLU:PELLU62D
039 07:29:59 PEL880 STARTER3 SESSION OK CID:0100000F,PLU:PELLU62C,SLU:PELLU62D
039 07:30:00 PEL105 NETLU62A CONNEXION ETABLIE PAR PELLU62C/PELLU62D
039 07:30:00 PEL010 NETLU62A TACHE DE RECEPTION PRETE, ACB : PELLU62D
039 07:30:00 SMAPS162 BUFFER TRACE AT:00094C48, LEN:000C, PT:01000020
039 07:30:00 0000 09000000 00000000 00000000 ........ ->............ <-
039 07:30:05 SMAPS562 BUFFER TRACE AT:00094D00, LEN:000C, PT:01000020

039 07:30:05 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:05 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:05 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:05 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:05 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:06 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:06 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:07 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:09 NETLU62A ALLO 00006D10 00000001 00000050 FB 2NSY01 00001F90 00000
039 07:30:09 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:09 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:09 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:09 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:09 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:10 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:10 PEL101A NETLU62A R0337 DEBUT RECEPTION PELSYS.PEL1.NETLU62A.A1.J03
039 07:30:10 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:12 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:12 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:12 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:12 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:13 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:13 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:13 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:30:15 PEL103A NETLU62A R0337 FIN RECEPTION PELSYS.PEL1.NETLU62A.A1.J039.
039 07:30:15 EXRCV002 : NO JCL DEFINED FOR PEL1
039 07:30:16 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:32:16 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:32:16 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:32:17 0000 02000000 00094F40 00000000 ........ ->......! .... <-
039 07:32:19 0000 05000000 00000000 00000000 ........ ->............ <-
039 07:32:19 SMAPS462 BUFFER TRACE AT:00094CFE, LEN:000C, PT:00000000

039 07:32:19 0000 07000000 00000000 00000000 ........ ->............ <-
039 07:32:19 PEL879 NETLU62A FIN DE TACHE SESSION LU6.2
039 07:32:19 PEL106 NETLU62A FIN DE CONNEXION PELLU62C
039 07:32:19 PEL878 NETLU62A FIN DE TACHE PRESENTATION LU6.2
039 07:32:19 PEL775 STARTER3 TACHE XFER TERMINEE : NETLU62A, CODE : 00000000
039 07:35:21 PEL881 STARTER3 FIN SESSION(S) PELLU62D-PELLU62C,MODE:LPELU62 ,CI
039 07:35:21 PEL881 STARTER3 FIN SESSION(S) PELLU62D-PELLU62C,MODE:SNASVCMG,CI
039 07:36:07 STOPX/NETLU62A
039 07:36:07 STOPX/NETLU62B
039 07:36:08 STOPLIGN/STARTER3
039 07:36:08 PEL773 STARTER3 DEMANDE DE FIN
039 07:36:08 PEL779A STARTER3 CONNEXIONS ENTRANTES - TOTAL : 000001 - MAX : 000
039 07:36:08 PEL779B STARTER3 CONNEXIONS SORTANTES - TOTAL : 000000 - MAX : 000
039 07:36:08 PEL779C STARTER3 NOMBRE DE CONNEXIONS - TOTAL : 000001 - MAX : 000
039 07:36:08 PEL774 STARTER3 TERMINE, CODE : 00000000
039 07:36:09 PEL692 LINE HANDLER : STARTER3 TERMINE, CODE : 000000, CTR=0005
Sample NET, ALL type site trace
This site trace is used for debugging purposes and traces the request buffers originating from
the protocol tasks in the same way as the NET,SUM trace. It also traces automaton events in
the LU 6.2 session and presentation tasks. The format of the automaton trace is:
ID: cccccccc M: mmmmmmmm S: ssss E: eeee C: cccccccc A: aaaaaaaa
where:
cccccccc = LU 6.2 conversation identifier
mmmmmmmm = Name of the automaton module
ssss = Current automaton state
eeee = Event
cccccccc = Condition met
aaaaaaaa = Name of the module performing the action

039 07:28:38 PEL707 STARTER3 OUVERTURE ACB OK : PELLU62C
039 07:28:39 TRACE/NETLU62B,ON,NET,ALL
039 07:28:39 TRACE POUR : NETLU62B - NETWORK : ON /ALL - PROTOCOL : OFF/SUM - F
039 07:29:56 ID: 00000000 M: PELGPS62 S: 0002 E: 0001 C: A : SMAPS162
039 07:29:56 PEL104 NETLU62B DEMANDE DE CONNEXION PELLU62D
039 07:29:56 PEL011 NETLU62B TACHE D'EMISSION PRETE, ACB : PELLU62C
039 07:29:56 ID: 00000000 M: PELGAR62 S: 0002 E: 0001 C: A : SMAAR162
039 07:29:56 ID: 00000000 M: PELGAR62 S: 0002 E: 0006 C: SMCAR362 A : SMAAR262
039 07:29:57 PEL200 SELECTION DE LA CLE : XPEL1 NETLU62B E95039A
039 07:29:58 SMAPS562 BUFFER TRACE AT:001DFD00, LEN:000C, PT:00000000
039 07:29:58 0000 01000000 00000000 00000000 ........ ->............ <-
039 07:29:58 ID: 00000000 M: PELGAR62 S: 0002 E: 0004 C: A : SMAAR462
039 07:29:58 ID: 00000000 M: PELGRQ62 S: 0002 E: 0001 C: A : SMARQ162
039 07:29:58 ID: 00000000 M: PELFAR62 S: 0002 E: 0006 C: SMCAR162 A : SMAAR262
039 07:29:59 ID: 0100001F M: PELGOR62 S: 0002 E: 0002 C: A : SMAOR162
039 07:29:59 ID: 0100001F M: PELGAR62 S: 0002 E: 0006 C: SMCAR362 A : SMAAR262
039 07:29:59 ID: 0100001F M: PELGPS62 S: 0002 E: 0006 C: A : SMAPS662
039 07:29:59 SMAPS662 BUFFER TRACE AT:001DFD00, LEN:000C, PT:0100001F
039 07:29:59 0000 01000000 00000000 00000000 ........ ->............ <-
039 07:29:59 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:29:59 ID: 0100001F M: PELGAR62 S: 0002 E: 0004 C: A : SMAAR462
039 07:29:59 ID: 0100001F M: PELGRQ62 S: 0006 E: 0003 C: A : SMARQB62
039 07:30:00 ID: 0100001F M: PELFAR62 S: 0002 E: 0003 C: SMCAR162 A : SMAAR862
039 07:30:05 ID: 0100001F M: PELGOR62 S: 0005 E: 002F C: A : SMAOR262
039 07:30:05 0000 03000000 00000000 00000000 ........ ->............ <-

039 07:30:05 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:05 ID: 0100001F M: PELGRQ62 S: 0003 E: 0002 C: A : SMARQA62
039 07:30:06 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:06 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:06 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:06 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:07 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:07 0000 03000000 00000000 00000000 ........ ->............ <-

039 07:30:09 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:09 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:10 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:10 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:10 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:10 PEL100A NETLU62B R0337 DEBUT EMISSION PELSYS.XFER.FB80
039 07:30:11 0000 02000000 001DFF40 00000000 ........ ->....... .... <-

039 07:30:12 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:12 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:12 ID: 0100001F M: PELGRQ62 S: 0003 E: 0002 C: A : SMARQ962
039 07:30:12 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:12 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:13 ID: 0100001F M: PELGRQ62 S: 0003 E: 0002 C: A : SMARQ962
039 07:30:13 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:30:13 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:13 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:30:13 PEL102A NETLU62B R0337 FIN EMISSION PELSYS.XFER.FB80
039 07:32:16 0000 02000000 001DFF40 00000000 ........ ->....... .... <-

039 07:32:16 0000 02000000 001DFF40 00000000 ........ ->....... .... <-
039 07:32:16 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:32:17 0000 03000000 00000000 00000000 ........ ->............ <-
039 07:32:17 0000 05000000 00000000 00000000 ........ ->............ <-
039 07:32:17 ID: 0100001F M: PELGRQ62 S: 000A E: 0005 C: A : SMARQ562
039 07:32:17 ID: 0100001F M: PELGPS62 S: 0002 E: 0006 C: SMCPS462 A : SMAPS462
039 07:32:17 SMAPS462 BUFFER TRACE AT:001DFCFE, LEN:000C, PT:0100001F
039 07:32:17 0000 07000000 00000000 00000000 ........ ->............ <-
039 07:32:19 ID: 00000000 M: PELGAR62 S: 0004 E: 0002 C: SMCAR362 A : SMAAR562
039 07:32:19 PEL879 NETLU62B FIN DE TACHE SESSION LU6.2
039 07:32:19 ID: 00000000 M: PELGPS62 S: 0004 E: 0008 C: SMCPS262 A : SMAPS262
039 07:32:19 PEL108 NETLU62B FIN DE CONNEXION PELLU62D
039 07:32:19 PEL878 NETLU62B FIN DE TACHE PRESENTATION LU6.2
039 07:32:19 PEL775 STARTER3 TACHE XFER TERMINEE : NETLU62B, CODE : 00000000
039 07:35:19 STOPX/NETLU62A
039 07:35:20 STOPX/NETLU62B
039 07:35:20 STOPLIGN/STARTER3
039 07:35:20 PEL773 STARTER3 DEMANDE DE FIN
039 07:35:21 PEL779A STARTER3 CONNEXIONS ENTRANTES - TOTAL : 000000 - MAX : 000
039 07:35:21 PEL779B STARTER3 CONNEXIONS SORTANTES - TOTAL : 000001 - MAX : 000
039 07:35:21 PEL779C STARTER3 NOMBRE DE CONNEXIONS - TOTAL : 000001 - MAX : 000
039 07:35:21 PEL774 STARTER3 TERMINE, CODE : 00000000
039 07:35:21 PEL692 LINE HANDLER : STARTER3 TERMINE, CODE : 000000, CTR=0013

Sample PROT, SUM type site trace
In LU 6.2 mode, the protocol trace format does not change.

039 07:35:23 PEL707 STARTER3 OUVERTURE ACB OK : PELLU62C
039 07:35:24 TRACE/NETLU62B,ON,PROT,SUM
039 07:35:24 TRACE POUR : NETLU62B - NETWORK : OFF/SUM - PROTOCOL : ON /SUM - F
039 07:37:07 PEL104 NETLU62B DEMANDE DE CONNEXION PELLU62D
039 07:37:07 PEL011 NETLU62B TACHE D'EMISSION PRETE, ACB : PELLU62C
039 07:37:08 PEL200 SELECTION DE LA CLE : XPEL1 NETLU62B E95039A
039 07:37:10 PEL880 STARTER3 SESSION OK CID:0300000A,PLU:PELLU62C,SLU:PELLU62D
039 07:37:10 PEL880 STARTER3 SESSION OK CID:0300000B,PLU:PELLU62C,SLU:PELLU62D
039 07:37:10 PEL880 STARTER3 SESSION OK CID:0300000C,PLU:PELLU62C,SLU:PELLU62D
039 07:37:10 PEL880 STARTER3 SESSION OK CID:0300000E,PLU:PELLU62D,SLU:PELLU62C
039 07:37:15 Prot trace for:NETLU62B(158) req:Read dl:..108 prot:PEL
039 07:37:15 0000 6FC4C5C2 E4E340D5 C5E3D3E4 F6F2C240 ->?DEBUT NETLU62B <-
039 07:37:15 0010 40404040 40404040 40404040 00000000 -> ....<-
039 07:37:15 0020 00000000 00000000 00000000 00000000 ->................<-
039 07:37:15 0030 00000000 00000000 00000000 00000000 ->................<-
039 07:37:15 0040 00000000 00000000 00000000 00000000 ->................<-
039 07:37:15 0050 00000000 00000000 00000000 00000000 ->................<-
039 07:37:15 0060 00000000 00000000 00000000 ........ ->............ <-
039 07:37:15 Prot trace for:NETLU62B(158) req:Writ dl:...29 prot:PEL
039 07:37:15 0000 5CC1C3C3 C5D7E3C5 40D5C5E3 D3E4F6F2 ->*ACCEPTE NETLU62<-
039 07:37:15 0010 C1404040 40404040 40404040 40...... ->A <-
039 07:37:15 Prot trace for:NETLU62B(158) req:Read dl:....3 prot:PEL
039 07:37:15 0000 5CD6D2.. ........ ........ ........ ->*OK <-
039 07:37:15 Prot trace for:NETLU62B(158) req:Writ dl:..225 prot:PEL
039 07:37:15 0000 6FE3D9C1 D5E240D5 C5E3D3E4 F6F2C140 ->?TRANS NETLU62A <-
039 07:37:15 0010 40404040 40404040 40404040 E5C5D9E2 -> VERS<-
039 07:37:15 0020 40D5C5E3 D3E4F6F2 C2404040 40404040 -> NETLU62B <-
039 07:37:15 0030 40404040 4040D3D6 E340D7C5 D3F14040 -> LOT PEL1 <-
039 07:37:15 0040 404060F0 F3F960F0 F3F3F860 F0F0F0F1 -> -039-0338-0001<-
039 07:37:15 0050 F0F140C3 F040F0F0 F040F0F0 F0F0F0F0 ->01 C0 000 000000<-
039 07:37:15 0060 40404040 40404040 40404040 40404040 -> <-
039 07:37:15 0070 40404040 40404040 40404040 40404040 -> <-
039 07:37:15 0080 40404040 40404040 40404040 40404040 -> <-
039 07:37:16 0090 40404040 40404040 40404040 40404040 -> <-
039 07:37:16 00A0 40404040 40404040 40404040 40404040 -> <-
039 07:37:16 00B0 00500FA0 90D7C5D3 E2E8E24B E7C6C5D9 ->.&...PELSYS.XFER<-
039 07:37:16 00C0 4BC6C2F8 F0404040 40404040 40404040 ->.FB80 <-
039 07:37:16 00D0 40404040 40404040 40404040 40404040 -> <-
039 07:37:16 00E0 40...... ........ ........ ........ -> <-
039 07:37:18 0000 5CD6D2.. ........ ........ ........ ->*OK <-

039 07:37:18 0000 5CC4C4D3 40D7C5D3 F1404040 4060F0F3 ->*DDL PEL1 -03<-
039 07:37:18 0010 F960F0F3 F3F860F0 F0F0F1F0 F160D5C5 ->9-0338-000101-NE<-
039 07:37:18 0020 E3D3E4F6 F2C14040 40404040 40404040 ->TLU62A <-
039 07:37:18 0030 4040.... ........ ........ ........ -> <-
039 07:37:19 0000 5CD6D2.. ........ ........ ........ ->*OK <-
039 07:37:19 PEL100A NETLU62B R0338 DEBUT EMISSION PELSYS.XFER.FB80
039 07:37:19 Prot trace for:NETLU62B(158) req:Writ dl:.2960 prot:PEL
039 07:37:19 0000 5C606060 60606060 60606060 60606060 ->*---------------<-
039 07:37:19 0B80 60606060 60604040 F0F0F0F0 F3F7F0F0 ->------ 00003700<-
039 07:37:20 Prot trace for:NETLU62B(158) req:Writ dl:.1120 prot:PEL
039 07:37:20 0000 5C606060 60606060 60606060 60606060 ->*---------------<-
039 07:37:20 0450 40404040 40404040 F0F0F0F0 F5F1F0F0 -> 00005100<-
039 07:37:20 0000 5CC6C4D3 40F0F0F0 F0F0F0F0 F0F0F0F0 ->*FDL 00000000000<-
039 07:37:20 0010 F040F0F0 F0F0F5F1 ........ ........ ->0 000051 <-
039 07:37:32 0000 5CC1C4D3 ........ ........ ........ ->*ADL <-
039 07:37:32 PEL102A NETLU62B R0338 FIN EMISSION PELSYS.XFER.FB80
039 07:37:36 EXEMI002 : NO JCL DEFINED FOR PEL1
039 07:39:16 Prot trace for:NETLU62B(158) req:Writ dl:....4 prot:PEL
039 07:39:16 0000 6FC6C9D5 ........ ........ ........ ->?FIN <-
039 07:39:16 Prot trace for:NETLU62B(158) req:Read dl:...20 prot:PEL
039 07:39:16 0000 5CC6C9D5 40C140E5 D6E3D9C5 40C4C5D4 ->*FIN A VOTRE DEM<-
039 07:39:16 0010 C1D5C4C5 ........ ........ ........ ->ANDE <-
039 07:39:18 PEL879 NETLU62B FIN DE TACHE SESSION LU6.2
039 07:39:18 PEL108 NETLU62B FIN DE CONNEXION PELLU62D
039 07:39:18 PEL878 NETLU62B FIN DE TACHE PRESENTATION LU6.2
039 07:39:18 PEL775 STARTER3 TACHE XFER TERMINEE : NETLU62B, CODE : 00000000

Sample line trace
This line trace is used for debugging purposes and traces the request buffers sent to the line-
handler by the other tasks. It also traces line-handler management automaton events.
The format of the request buffer trace is:
mmmmmmmm BUFFER TRACE AT:aaaaaaaa,LEN:llll,PT:nnnnnnnn

0000 rq000000 xxxxxxxx xxxxxxxx xxxxxxxx
0010 xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx
.... ........ ........ ........ ........
llll xxxxxxxx xxxxxxxx ........ ........
where:
mmmmmmmm = Name of the automaton module managing the line-handler
aaaaaaaa = Address of the request buffer
llll = Buffer length
nnnnnnnn = Name of the line-handler
rq = Request identifier
00 Open ACB
01 TPEND exit routine
02 LOGON exit routine
04 Line-handler stop
06 SCIP exit routine
08 Transfer request
0A ATTN FMH5
0B Cancel task
0C ATTN CNOS
0D Time-out detected
0F ATTN LOSS scheduled
xxxxxxxx = Data, the format of which depends on the request
The format of the automaton trace is:
LN: llllllll M: mmmmmmmm S: ssss E: eeee C: cccccccc A: aaaaaaaa
where:
llllllll = Name of the line-handler
mmmmmmmm = Name of the automaton module
ssss = Current automaton state
eeee = Event
cccccccc = Condition met
aaaaaaaa = Name of the module performing the action

033 03:18:12 PEL678 LINE HANDLER : PELGTG62 NOM : STARTER3 LANCE, CTR=000D
033 03:18:13 TRACEL/STARTER3
033 03:18:13 TRACE POUR : STARTER3 ON
033 03:19:02 LN: STARTER3 M: PELGTG62 S: 0002 E: 0004 C: A : SMATG462
033 03:19:02 SMATG462 BUFFER TRACE AT:000DA388, LEN:0078, PT:STARTER3
033 03:19:02 0000 06000000 D7C5D3D3 E4F6F2C3 01000002 ->....PELLU62C....<-
033 03:19:02 0010 00000000 00000000 00080018 00000000 ->................<-
033 03:19:02 0020 00002600 0902E2D5 C1E2E5C3 D4C70903 ->......SNASVCMG..<-
033 03:19:02 0030 00DF3DF3 B59A2A1C 1004C2D7 F0F6F3C1 ->...3......BP063A<-
033 03:19:02 0040 4BD7C5D3 D3E4F6F2 C3000000 00000000 ->.PELLU62C.......<-
033 03:19:02 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:02 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:02 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:03 0000 0C000000 C3D5D6E2 D7C5D3D3 E4F6F2C3 ->....CNOSPELLU62C<-
033 03:19:03 0010 D3D7C5D3 E4F6F240 FFFFFFFF FFFFFFFF ->LPELU62 ........<-
033 03:19:03 0020 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF ->................<-
033 03:19:03 0070 FFFFFFFF FFFFFFFF ........ ........ ->........ <-
033 03:19:03 0000 02000000 D7C5D3D3 E4F6F2C3 01000003 ->....PELLU62C....<-
033 03:19:03 0010 18000033 001307B0 B0D0B100 07868687 ->.........}...ffg<-
033 03:19:03 0020 00060200 00000000 00000023 000008D7 ->...............P<-
033 03:19:03 0030 C5D3D3E4 F6F2C400 0E000000 003E0773 ->ELLU62D.........<-
033 03:19:03 0040 02000401 00000000 00000000 00000000 ->................<-
033 03:19:03 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:03 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:03 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:04 0000 02000000 D7C5D3D3 E4F6F2C3 01000004 ->....PELLU62C....<-
033 03:19:04 0010 18000033 001307B0 B0D0B100 07868687 ->.........}...ffg<-
033 03:19:04 0020 00060200 00000000 00000023 000008D7 ->...............P<-
033 03:19:04 0030 C5D3D3E4 F6F2C400 0E000000 003E0773 ->ELLU62D.........<-
033 03:19:04 0040 02000501 00000000 00000000 00000000 ->................<-
033 03:19:04 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:04 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:04 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:04 SMATG462 BUFFER TRACE AT:000DAB08, LEN:0078, PT:STARTER3
033 03:19:04 0000 02000000 D7C5D3D3 E4F6F2C3 01000005 ->....PELLU62C....<-

033 03:19:04 0010 18000033 001307B0 B0D0B100 07868687 ->.........}...ffg<-
033 03:19:04 0020 00060200 00000000 00000023 000008D7 ->...............P<-
033 03:19:04 0030 C5D3D3E4 F6F2C400 0E000000 003E0773 ->ELLU62D.........<-
033 03:19:04 0040 02000601 00000000 00000000 00000000 ->................<-
033 03:19:04 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:04 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:04 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:04 SMATG462 BUFFER TRACE AT:000DAB88, LEN:0078, PT:STARTER3
033 03:19:04 0000 02000000 D7C5D3D3 E4F6F2C3 01000006 ->....PELLU62C....<-
033 03:19:04 0010 18000033 001307B0 B0D0B100 07868687 ->.........}...ffg<-
033 03:19:05 0020 00060200 00000000 00000023 000008D7 ->...............P<-
033 03:19:05 0030 C5D3D3E4 F6F2C400 0E000000 003E0773 ->ELLU62D.........<-
033 03:19:05 0040 02000701 00000000 00000000 00000000 ->................<-
033 03:19:05 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:05 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:05 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:05 0000 02000000 D7C5D3D3 E4F6F2C3 01000007 ->....PELLU62C....<-
033 03:19:05 0010 18000033 001307B0 B0D0B100 07868687 ->.........}...ffg<-
033 03:19:05 0020 00060200 00000000 00000023 000008D7 ->...............P<-
033 03:19:05 0030 C5D3D3E4 F6F2C400 0E000000 003E0773 ->ELLU62D.........<-
033 03:19:05 0040 02000801 00000000 00000000 00000000 ->................<-
033 03:19:05 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:05 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:05 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:22 SMATG462 BUFFER TRACE AT:000DAC08, LEN:0078, PT:STARTER3
033 03:19:22 0000 06000000 D7C5D3D3 E4F6F2C3 0100000E ->....PELLU62C....<-
033 03:19:22 0010 00000000 00000000 00080018 00000000 ->................<-
033 03:19:22 0020 00002500 0802D3D7 C5D3E4F6 F2090300 ->......LPELU62...<-
033 03:19:22 0030 DF3DF3B5 9A2A2210 04C2D7F0 F6F3C14B ->..3......BP063A.<-
033 03:19:22 0040 D7C5D3D3 E4F6F2C3 00000000 00000000 ->PELLU62C........<-
033 03:19:22 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:22 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:22 0070 00000000 00000000 ........ ........ ->........ <-
033 03:19:22 LN: STARTER3 M: PELGTV62 S: 0004 E: 0002 C: A : SMATV362
033 03:19:22 0000 06000000 D7C5D3D3 E4F6F2C3 0100000F ->....PELLU62C....<-
033 03:19:22 0010 00000000 00000000 00080018 00000000 ->................<-
033 03:19:22 0020 00002500 0802D3D7 C5D3E4F6 F2090300 ->......LPELU62...<-
033 03:19:22 0030 DF3DF3B5 9A2A2310 04C2D7F0 F6F3C14B ->..3......BP063A.<-
033 03:19:22 0040 D7C5D3D3 E4F6F2C3 00000000 00000000 ->PELLU62C........<-
033 03:19:22 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:19:22 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:19:22 0070 00000000 00000000 ........ ........ ->........ <-
033 03:40:43 PEL678 LINE HANDLER : PELGTG62 NOM : STARTER3 LANCE, CTR=000D
033 03:40:43 SMATG462 BUFFER TRACE AT:000DAC88, LEN:0078, PT:STARTER3

033 03:40:43 0000 00000000 00034EE4 00034FA0 00000000 ->......+U..!.....<-
033 03:40:43 0010 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0020 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0030 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0040 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0070 00000000 00000000 ........ ........ ->........ <-
033 03:40:43 0000 08000000 000AC1E0 00000000 00000000 ->......A\........<-
033 03:40:43 0010 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0020 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0030 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0040 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:40:43 0070 00000000 00000000 ........ ........ ->........ <-
033 03:40:44 0000 08000000 000AC098 00000000 00000000 ->......{q........<-
033 03:40:44 0010 00000000 00000000 00000000 00000000 ->................<-
033 03:40:44 0020 00000000 00000000 00000000 00000000 ->................<-
033 03:40:44 0030 00000000 00000000 00000000 00000000 ->................<-
033 03:40:44 0040 00000000 00000000 00000000 00000000 ->................<-
033 03:40:44 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:40:44 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:40:44 0070 00000000 00000000 ........ ........ ->........ <-
033 03:41:27 0000 06000000 D7C5D3D3 E4F6F2C3 03000002 ->....PELLU62C....<-
033 03:41:27 0010 00000000 00000000 00080018 00000000 ->................<-
033 03:41:27 0020 00002600 0902E2D5 C1E2E5C3 D4C70903 ->......SNASVCMG..<-
033 03:41:27 0030 00DF3DF3 B59A306E 1004C2D7 F0F6F3C1 ->...3...>..BP063A<-
033 03:41:27 0040 4BD7C5D3 D3E4F6F2 C3000000 00000000 ->.PELLU62C.......<-
033 03:41:27 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:41:27 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:41:27 0070 00000000 00000000 ........ ........ ->........ <-
033 03:41:28 0000 0C000000 C3D5D6E2 D7C5D3D3 E4F6F2C3 ->....CNOSPELLU62C<-
033 03:41:28 0010 D3D7C5D3 E4F6F240 FFFFFFFF FFFFFFFF ->LPELU62 ........<-
033 03:41:28 0070 FFFFFFFF FFFFFFFF ........ ........ ->........ <-

033 03:41:28 SMATG462 BUFFER TRACE AT:000DAA88, LEN:0078, PT:STARTER3
033 03:41:28 0000 06000000 D7C5D3D3 E4F6F2C3 03000008 ->....PELLU62C....<-
033 03:41:28 0010 00000000 00000000 00080018 00000000 ->................<-
033 03:41:28 0020 00002500 0802D3D7 C5D3E4F6 F2090300 ->......LPELU62...<-
033 03:41:28 0030 DF3DF3B5 9A306F10 04C2D7F0 F6F3C14B ->..3...?..BP063A.<-
033 03:41:28 0040 D7C5D3D3 E4F6F2C3 00000000 00000000 ->PELLU62C........<-
033 03:41:28 0050 00000000 00000000 00000000 00000000 ->................<-
033 03:41:28 0060 00000000 00000000 00000000 00000000 ->................<-
033 03:41:28 0070 00000000 00000000 ........ ........ ->........ <-

APPENDIX E USING TCP/IP
E.1 INTRODUCTION
A TCP/IP network layer independent of the protocol used is built into the Inter.Pel product.
It can use Interlink SNS/TCPaccess and/or the IBM TCP/IP product.
This network layer is managed like X.25 in the GATE mode. There is a line-handler for each
TCP/IP listening port (the equivalent in the X.25 GATE mode is the MCH LU) and a new
IPTABLE contains all the IP addresses of the remote sites (X25TABLE for the X.25 GATE
mode). The two new EXIPIN and EXIPOUT connection exits can be used in the same way as
EXX25IN and EXX25OUT for the X.25 GATE mode.
From IBM TCP/IP Release 3.2 onwards, symbolic names (aliases) can be used to define an
outgoing or incoming connection. For each connection, the IP addresses are resolved in two
steps.
- A specialized name server is called. This server must be defined for the Inter.Pel address
space (IP address and port number). It returns the IP address (or list of IP addresses)
associated with the symbolic name.
- The prefix.HOSTS.SITEINFO and prefix.HOSTS.ADDRINFO files are queried to
determine the corresponding IP address(es). The prefix of these two files must be defined for
the Inter.Pel address space.
Inter.Pel invokes this service using the GETHOSTBYNAME and GETHOSTBYADDR

functions. TCP/IP first attempts to resolve the IP addresses via the name server.
If the name server cannot respond (or is not defined for the Inter.Pel address space, or is
temporarily not available, or the name requested is not defined in the server), TCP/IP uses the
prefix.HOSTS.SITEINFO and prefix.HOSTS.ADDRINFO files to determine the
corresponding IP address. The prefix of these files is defined by the DATASETPREFIX
parameter (SYSTCPD DD card in the Inter.Pel JCL).
In Inter.Pel, use of symbolic names is requested via the new NINx and NOUTx parameters in
the GENIPNB macro-instruction. These parameters override the INx and OUTx parameters.
This option can only be used if TYPE=IPIB3 in the GENLIGN macro-instruction and
STYPE=IIB3 in the GENTER macro-instruction.
Installation and Implementation Guide Using TCP/IP E-1

E.2 INTER. PEL PARAMETERS FOR TCP/IP
E.2.1 SPECIFIC PARAMETERS
E.2.1.1 GENLIGN
The following values and parameters have been added to the GENLIGN macro-instruction for
TCP/IP:
TYPE: - IPITL designates an Interlink TCP/IP line manager

- IPIBM designates an IBM TCP/IP line manager. Equivalent to IPIB3
- IPIB3 designates an IBM TCP/IP line manager
PORT: This parameter indicates the number of the listening port of the TCP/IP
manager.
This parameter accepts a list of port/monitor pairs to assign different ports to
all the monitors.
It accepts as many ports as the number of monitors in the cluster. Those
ports can be generic if no monitor is dedicated to a port. Inter.Pel will then
use the first free port for a monitor starting this line. Those ports can also be
dedicated to one monitor if a monitor name (ID) is associated with the port
number. Inter.Pel will then use this port when this monitor starts this line.
Both solutions can be mixed, some ports are dedicated to monitors and the
It is a decimal value with a maximum length of five digits.
It is mandatory and used by both Interlink and IBM.
SUBSID: This parameter indicates the name of the Interlink SNS/TCPaccess

subsystem or the name of the address space (JOB or STC) for IBM TCP/IP.
It contains four characters for the Interlink product, and eight characters for
IBM.
It is optional and set by default to ACSS for SNS/TCPaccess or to default
TCP value (retrieved from the SYSTCPD file or forced to TCPIP) for the
IBM product.
This parameter accepts a list of id/monitor pairs to assign different ids to all
the monitors.
It accepts as many ids as the number of monitors in the cluster. A single id
can be used if only one value is provided. Inter.Pel will then use this id for
all the monitors starting this line. Those ids can also be dedicated to one
monitor if a monitor name (ID) is associated with the TCP id. Inter.Pel will
then use this id when this monitor starts this line. Both solutions can be
mixed, some ids are dedicated to monitors and others are used for the other
monitors.
IPADO: Caller address provided to the remote site in outgoing calls.
E.2.1.2 GENTER
The following parameter values have been added to the GENTER macro-instruction for
TCP/IP:

TYPE: "T" designates a TCP/IP terminal.
STYPE: The following values designate an Interlink or IBM terminal:

- ITL for an Interlink TCP/IP terminal
- IIBM for an IBM TCP/IP terminal (equivalent to IIB3)
- IIB3 for an IBM TCP/IP terminal.
CDH={Y|N}
For the TCP/IP access (STYPE=ITL, IIBM or IIB3), this parameter defines
how the length of the internal TCP/IP blocks is coded. This length is stored
in the two binary bytes with one of the following formats:
Y - (low order, high order), used by UNIX systems
N - (high order, low order), used by MVS systems
Default: N.

E.2.2 IPTABLE (Common INTERLINK and IBM parameters)

The GENIPNB macro-instruction is used to create this table.
A sample table definition can be found in the SAMPLIB library IPTB member.
GENIPNB NAME=name (1)

[,INx=nnnnnnnnnn]
[,NINx=hostname] (2)
[,NOUTx=hostname] (2)
[,OUTx=nnn.nnn.nnn.nnn]
[,PLCINx=vvvvv]
[,PLCOUTx=vvvvv]
[,PORTINx=vvvvv]
[,PORTOUTx=vvvvv]
[,PROFILE=name]
[,RETRYx={nn|8}]
[,TIMERx={nnnnn|0}]
[,TMOUT={nn|9}]

(2) Parameter available exclusively for the IBM product, Release 3.2 and above.
INx=nnn.nnn.nnn.nnn
nnn.nnn.nnn.nnn: IP address of the calling site.
The value * in the place of a group of three digits (one hexadecimal digit),
indicates that a check does not have to be run on this digit in the caller
address.
The value *.*.*.* indicates that a check must not to be performed on the
caller address, but only on the port number as defined in the PCLINx
parameter (equivalent ot NINx=*).
Maximum length: 15.
Example: IN1=127.0.0.1.
Default: none.
NAME=name
Site name.

NINx=hostname
Name used for incoming connections.
Maximum length: 74.
The value * indicates that a check does not have to be run on the caller
name but only on the port number as defined in the PCLINx parameter.
If this parameter is set, it overrides the INx parameter.
Example: NIN1=HOST1.
Default: none.
NOUTx=hostname
Name used for outgoing connections.
Maximum length: 74.
If this parameter is set, it overrides the OUTx parameter.
Example: NOUT1=HOST1.
Default: none.
OUTx=nnn.nnn.nnn.nnn
nnn.nnn.nnn.nnn: IP address to be specified when calling the site.
Maximum length: 15.
Example: OUT1=127.0.0.1.
Default: none.
PLCINx=vvvvv
Local listening PORT for the local TCP/IP manager receiving the call from
the calling site. It provides an additional criterion to identify a calling site
when several TCP/IP managers are running.
Example: PLCIN1=3500.
Default: none.
PLCOUTx=vvvvv
Local listening PORT for the local TCP/IP manager calling the destination
site. It is not currently used.
Example: PLCOUT1=3500.
Default: none.

PORTINx=vvvvv
Calling site PORT. It is not currently used.
Example: PORTIN1=4310.
Default: none.
PORTOUTx=vvvvv
Listening PORT to be provided for the destination site to be reached.
(It must be decimal.)
Example: PORTOUT1=6210.
Default: none.
PROFILE=name
Site used as a model when creating another site dynamically. Automatic
creation is always authorized if this parameter is set until the real control is
performed by the EXODETLG exit or the GENSAF macro.
RETRYx={nn|8}
Number of retries after which the address is considered to be out of service.
Inter.Pel then uses the next number, if it is declared.
The CLIPNO command allows a temporarily disabled number to be
reactivated.
Default: 8.
TIMERx={nnnnn|0}
Data flow control timer in hundredths of a second.
Default: 0.
TMOUT={nn|9}
Period at the end of which the SVC table entry is released if no activity has
taken place.
Expressed in minutes.
in the GENTER macro associated with this IP address.
Default: 9.

E.2.3 SAMPLE IPTABLE
NOTE: The sample IPTABLE can be found in the SAMPLIB library IPTB member.
***********************************************************************
* INTERLINK / IBM (WITHOUT ALIAS NAMES) *
***********************************************************************
GENIPNB NAME=PELIUNX1,TMOUT=3, *
OUT1=145.45.21.1,PORTOUT1=6210, *
IN1=145.45.21.1,PLCIN1=3500
OUT1=145.45.21.2,PORTOUT1=6210, *
IN1=145.45.21.2,PLCIN1=3500, *
OUT1=145.45.21.3,PORTOUT1=6210, *
IN1=145.45.21.3,PLCIN1=3500, *
OUT1=145.45.21.4,PORTOUT1=6210, *
IN1=145.45.21.4,PLCIN1=3500, *
OUT1=145.45.21.5,PORTOUT1=6210, *
IN1=145.45.21.5,PLCIN1=3500
***********************************************************************
* IBM WITH ALIAS NAMES (FROM TCP/IP V3.2) *
***********************************************************************
NOUT1=HOST1,PORTOUT1=6210, *
NIN1=HOST1,PLCIN1=3500 *
NIN1=HOST2,PLCIN1=3500, *
NIN1=HOST5,PLCIN1=3500 *
END
In this example, the addresses for the PELUNX1 and PELUNX2 sites are defined explicitly.
The IP addresses for the PELUNX3 and PELUNX4 sites are defined using the HOST1,
HOST2, ... HOST5 symbolic names. The IP addresses are resolved when the connection is
established via the name server or the HOSTS.SITEINFO and HOSTS.ADDRINFO files.

E.3 INTERLINK/IBM TCP/IP SPECIFIC PARAMETERS AND REQUIREMENTS
E.3.1 INTERLINK SNS/TCPACCESS PARAMETERS
The Interlink product requires no specific parameters.
E.3.2 IBM SPECIFIC PARAMETERS AND REQUIREMENTS
E.3.2.2 PORT DEFINITIONS
The ports used by each Inter.Pel product (GENLIGN macro-instruction) must be reserved in
the PROFILE.TCPIP file as follows.
PORT
Port number TCP Inter.Pel jobname ;
Example (extract from the TCPPIBM member in the SAMPLIB library):
PORT
3500 TCP INTERPEL ; Inter.Pel
Note: the ports defined in this example correspond to those specified in the GENLIGN macro-
instructions.

E.3.2.3 DEFINITIONS USING SYMBOLIC NAMES
From IBM TCP/IP Release 3.2 onwards, symbolic names (aliases) can be used to define
outgoing or incoming connections. For each connection, the IP addresses are resolved in two
steps.
- A specialized name server is called. This server must be defined for the Inter.Pel
address space (IP address and port number). It returns the IP address (or list of IP
addresses) associated with the symbolic name.
- The prefix.HOSTS.SITEINFO and prefix.HOSTS.ADDRINFO files are queried to
determine the corresponding IP address(es). The prefix of these two files must be
defined for the Inter.Pel address space.
The HOSTS.SITEINFO and HOSTS.ADDRINFO files are generated by the MAKESITE

program from the HOSTS.LOCAL source file. The MAKESITE program can be run by
entering the TSO MAKESITE command or in batch mode.
A sample JCL using the MAKESITE program in batch mode can be found in the CNTL
library MAKESITE member.
//PEL1 JOB
//PEL2 JOB
//*
//********************************************************************
//* EXEMPLE OF "MAKESITE" JCL *
//* INPUT FILE : PREFIX.HOSTS.LOCAL *
//* OUTPUT FILE : PREFIX.HOSTS.SITEINFO *
//* OUTPUT FILE : PREFIX.HOSTS.ADDRINFO *
//********************************************************************
//*
//BATCH EXEC PGM=MAKESITE,REGION=8000K,
// PARM='VOLSER=VVVVVV,UNIT=SYSDA,HLQ=PREFIX,MGMT=M0001'
//*
//********************************************************************
//* TCP/IP LIBRARY *
//********************************************************************
//STEPLIB DD DISP=SHR,DSN=TCPIP.V3R2.SEZALINK
//*
//SYSPRINT DD SYSOUT=*,DCB=(LRECL=132,RECFM=FBA,BLKSIZE=3960)
The HLQ parameter defines the prefix for the following files: HOSTS.LOCAL (input file),
HOSTS.ADDRINFO and HOSTS.SITEINFO (output files).
The other parameters are used to create the output files dynamically and in most cases, can be
omitted. See the IBM TCP/IP documentation (Customization and Administration Guide) for
further information.
The HOSTS.LOCAL file is used to resolve IP addresses, if the name server is unavailable. It
allows the IP address(es) to be associated with a symbolic name or list of symbolic names. Its
structure is defined in the IBM TCP/IP documentation (Customization and Administration
Guide). This file is used as input to the MAKESITE program when generating the
HOSTS.SITEINFO and HOSTS.ADDRINFO files.
A sample HOSTS.LOCAL file can be found in the SAMPLIB library HLOCAL member.

; *******************************************************************
; * THIS IS EXAMPLE OF PREFIX.HOSTS.LOCAL FILE *
; *******************************************************************
;
; HOST1 HAS IP ADDRESS : 123.12.12.1
HOST : 123.12.12.1 : HOST1 ::::
;
; HOST2 HAS 2 IP ADDRESS : 123.12.12.2 AND 123.12.12.3
HOST : 123.12.12.2, 123.12.12.3 : HOST2 ::::
;
; HOST3 (WITH ALIAS NAME ANHOST3) HAS IP ADDRESS 123.12.12.4
HOST : 123.12.12.4 : HOST3,ANHOST3 ::::
;
; HOST4 (AN1HOST4,AN2HOST4) HAS IP ADDRESS 123.12.12.5 AND 123.12.12.6
HOST : 123.12.12.5, 123.12.12.6 : HOST4,AN1HOST4,AN2HOST4 ::::
This example defines four associations.
HOST1 is associated with IP address 123.12.12.1.
HOST2 is associated with IP addresses 123.12.12.2 and 123.12.12.3 (123.12.12.2 takes

precedence, but if the connection fails, the 123.12.12.3 secondary address is used).
The HOST3 and ANHOST3 names are associated with IP address 123.12.12.4.
The HOST4, AN1HOST4 and AN2HOST4 names are associated with IP addresses 123.12.12.5
and 123.12.12.6.
The IP address, port number and file prefix of the name server must be defined to enable the
name server and HOSTS.SITEINFO and HOSTS.ADDRINFO files to be used. This is why a
definition file must be added to the Inter.Pel startup JCL (SYSTCPD DD card).
A sample definition file can be found in the SAMPLIB library TCPDATA member.
; ********************************************************************
; * THIS IS EXEMPLE OF "TCPDATA" PARAMETER FILE *
; * THIS FILE SHOULD BE ADD INTO INTERPEL STARTUP JCL *
; * AS DD : "SYSTCPD" *
; * YOU SHOULD REPLACE : *
; * TCPIP BY THE NAME OF TCPIP JOB(STC) IF DIFFERENT FROM TCPIP *
; * DDDDDD BY YOUR DOMAIN NAME *
; * 123.123.123.123 BY YOUR NAME SERVER IP ADDRESS *
; * PREFIX BY PREFIX OF YOURS "HOSTS" FILES *
; * IF YOU WANT TO HAVE THE RESOLVER TRACE DELETE ";" IN TRACE LINE *
; ********************************************************************
TCPIPJOBNAME TCPIP
DOMAINORIGIN DDDDDD
NSINTERADDR 123.123.123.123
NSPORTADDR 53
RESOLVEVIA UDP
RESOLVERTIMEOUT 30
RESOLVERUDPRETRIES 1

DATASETPREFIX PREFIX
;TRACE RESOLVER
TCPIPJOBNAME Jobname of the TCPIP address space (STC) used to call the
name server. Default is TCPIP.
DOMAINORIGIN Name to be concatenated with the name in the IPTABLE for the
request to the name server. This parameter is not used to search
the HOSTS.SITEINFO and HOSTS.ADDRINFO files.
NSINTERADDR IP address of the name server.
NSPORTADDR Port number of the name server (default: 53).
RESOLVEVIA UDP/TCP method of communicating with the name server

(default: UDP).
RESOLVERTIMEOUT Name server connection time-out (default: 30 seconds).
RESOLVERUDPRETRIES Number of connection retries with the name server (default: 1,

no retry).
DATASETPREXIX Prefix of the HOSTS.SITEINFO and HOSTS.ADDRINFO files

(maximum length of 26 characters; must not terminate with a
dot).
TRACE Communication trace with the name server. The trace data is
written to the SYSPRINT (DD) file.
See the IBM TCP/IP documentation (Customization and Administration Guide) for further
information.

E.4 SAMPLE INTER.PEL DEFINITIONS FOR INTERLINK AND IBM TCP/IP
E.4.1 SAMPLE INTER.PEL DEFINITIONS FOR INTERLINK
ENVIRONMENT TABLE (SAMPLIB library TCPITL member)
TCPIP1 GENLIGN TYPE=IPITL,PORT=3500
STARTER3 GENLIGN TYPE=DYN,LOCK=Y

GENTER TYPE=T,STYPE=ITL,SITNAME=DUMMYP,PROT=PEL,
NUMBER=30,SESSON=2
GENSITE NAME=PELIUNX1,GROUP=UNX,TRAILER=N,
ISTATUS=ACT,LUOUT=TCPIP1
BLKSIZE=AUTO

E.4.2 SAMPLE INTER.PEL DEFINITIONS FOR IBM TCP/IP
ENVIRONMENT TABLE (SAMPLIB library TCPIBM member)
TCPIP1 GENLIGN TYPE=IPIB3,PORT=3500
STARTER3 GENLIGN TYPE=DYN,LOCK=Y

GENTER TYPE=T,STYPE=IIB3,SITNAME=DUMMYP,PROT=PEL,
NUMBER=30,SESSON=2
BLKSIZE=AUTO
E.4.3 SAMPLE INTER.PEL DEFINITIONS COMMON TO INTERLINK/IBM TCP/IP
ROUTING TABLE
GENDST2 DESTP=PELIUNX1,DESTYP=1
GENDST2 DESTP=PELIUNX2,DESTYP=1

E.4.4 SAMPLE INTER.PEL DEFINITIONS COMMON TO INTERLINK/IBM
TCP/IP
IPTABLE (SAMPLIB library IPTB member)
***********************************************************************
* INTERLINK / IBM (WITHOUT ALIAS NAMES) *
***********************************************************************
OUT1=145.45.21.1,PORTOUT1=6210, *
IN1=145.45.21.1,PLCIN1=3500
OUT1=145.45.21.2,PORTOUT1=6210, *
IN1=145.45.21.2,PLCIN1=3500, *
OUT1=145.45.21.3,PORTOUT1=6210, *
IN1=145.45.21.3,PLCIN1=3500, *
OUT1=145.45.21.4,PORTOUT1=6210, *
IN1=145.45.21.4,PLCIN1=3500, *
OUT1=145.45.21.5,PORTOUT1=6210, *
IN1=145.45.21.5,PLCIN1=3500
***********************************************************************
* IBM WITH ALIAS NAMES (FROM TCP/IP V3.2) *
***********************************************************************
NOUT1=HOST1,PORTOUT1=6210,
NIN1=HOST1,PLCIN1=3500
NIN1=HOST2,PLCIN1=3500,
NIN1=HOST5,PLCIN1=3500

HOSTS.LOCAL FILE (SAMPLIB library HLOCAL member)
; *******************************************************************
; * THIS IS EXAMPLE OF PREFIX.HOSTS.LOCAL FILE *
; *******************************************************************
;
; HOST1 HAS IP ADDRESS : 123.12.12.1
HOST : 123.12.12.1 : HOST1 ::::
;
; HOST2 HAS 2 IP ADDRESS : 123.12.12.2 AND 123.12.12.3
HOST : 123.12.12.2, 123.12.12.3 : HOST2 ::::
;
; HOST3 (WITH ALIAS NAME ANHOST3) HAS IP ADDRESS 123.12.12.4
HOST : 123.12.12.4 : HOST3,ANHOST3 ::::
;
; HOST4 (AN1HOST4,AN2HOST4) HAS IP ADDRESS 123.12.12.5 AND 123.12.12.6
HOST : 123.12.12.5, 123.12.12.6 : HOST4,AN1HOST4,AN2HOST4 ::::
NAME SERVER DEFINITIONS (SAMPLIB library TCPDATA member)
; ********************************************************************
; * THIS IS EXEMPLE OF "TCPDATA" PARAMETER FILE *
; * THIS FILE SHOULD BE ADD INTO INTERPEL STARTUP JCL *
; * AS DD : "SYSTCPD" *
; * YOU SHOULD REPLACE : *
; * DDDDDD BY YOUR DOMAIN NAME *
; * 123.123.123.123 BY YOUR NAME SERVER IP ADDRESS *
; * PREFIX BY PREFIX OF YOURS "HOSTS" FILES *
; * IF YOU WANT TO HAVE THE RESOLVER TRACE DELETE ";" IN TRACE LINE *
; ********************************************************************
DOMAINORIGIN DDDDDD
NSINTERADDR 123.123.123.123
NSPORTADDR 53
RESOLVEVIA UDP
RESOLVERTIMEOUT 30
RESOLVERUDPRETRIES 1
DATASETPREFIX PREFIX
;TRACE RESOLVER

E.5 EXITS
These exits are common to the IBM and Interlink TCP/IP products.
E.5.1 MANAGING INCOMING TCP/IP CONNECTIONS: EXIPIN
Inter.Pel calls this exit each time it receives a request for a TCP/IP connection on the listening
port of a TCP/IP line manager.
It is used to accept or reject a call, or to ask Inter.Pel to check the call against information in
the IPTABLE.
Input parameters:
- R9 points to the environment table

- R7 points to the PELLIBLK line block
- R1 points to a list of six words representing the:
Reserved address
Address of the field containing the caller number
Reserved address
Reserved address
Address of the caller site
Address of the TCP/IP connection parameters:
* Data flow control timer in hundredths of a second (two binary
bytes)
Default value: 0
* Reserved address (one binary byte)
* Time-out value in minutes (one binary byte)
Default value: 4
Possible action: The exit must store a return code in register 15 indicating the action
to be taken by Inter.Pel.
R15 = 0 : The connection is accepted and the exit loads the site
name in the field to which the fifth word in the
parameter list points.
R15 = 4 : To accept the connection, Inter.Pel must check the
contents of the call packet against the IPTABLE data.
R15 = 8 : Inter.Pel must reject the connection.
Default program: Ask Inter.Pel to check the call packet.

A sample incoming IP call management exit can be found in the SAMPLIB library EXIPIN
member.
TITLE 'EXIPIN : IP INCOMING CALL EXIT'

*************************************************************
*
* FUNCTION :
* - VERIFY INCOMING CALL AND ACCEPT OR REFUSE CONNECTION
* - FORCE SITE NAME OR LET Inter.Pel VERIFY AND PROVIDES
* SITE NAME FROM 'IPTABLE' ( FEATUR USE )
*
* INPUT :
* R1 CONTAINS A PARAMETER LIST ADDRESS
* 00 - RESERVED
* 04 - CALLING NUMBER FIELD ADDRESS
* 08 - RESERVED
* 12 - RESERVED
* 16 - SITE NAME ADDRESS
* 20 - PARAMETERS:
* TIMER (XL2)
* RESERVED (XL1)
* TIME OUT (XL1)
*
* OUTPUT :
* R15 :
* 0 - SITE NAME IS PROVIDED BY EXIT.
* SITE NAME IS A 25 BYTES EBCDIC FIELD LEFT JUSTIFIED
* 4 - Inter.Pel WILL VERIFY FROM IPTABLE
* 8 - CONNECTION MUST BE REJECTED
*
*************************************************************
*
* LINK-EDIT : NORENT
* LOAD MODULE : 'EXIPIN'
*
*************************************************************
SPACE 3
EXIPIN PELIDEB
L R2,4(R1) POINT TO CALLING NUMBER
MVC CALLN(LCALLN),0(R2)
L R2,16(R1) GET SITE ADDRESS
MVC 0(25,R2),=CL25'DUMMYP' FORCE SITE NAME
B RET0
RET0 EQU *
SR R15,R15 CALL ACCEPTED
B RETURN
RET4 EQU *
LA R15,4 CALL CHECKED BY INTER PEL
B RETURN
RET8 EQU *
LA R15,8 CALL REJECTED
B RETURN
*
RETURN EQU *

PELIRET
*
CALLN DS 0F CALLING NUMBER
DS AL1 LENGTH OF CALL NUMBER ALWAYS 06
DS AL2 PORT NUMBER
DS AL1(0,0,0,0) IP ADDRESS
LCALLN EQU *-CALLN
*
PELIEND
END

E.5.2 MANAGING OUTGOING TCP/IP CONNECTIONS: EXIPOUT
Inter.Pel calls this exit each time it sends a TCP/IP connection request to another site.
It is used to dial the IP number and port to be contacted directly, to ask Inter.Pel to do so using
the IPTABLE data, or to ask Inter.Pel to reject the call request.
Input parameters:
- R9 points to the environment table

- R7 points to the PELLIBLK line block
- R1 points to a list of four words representing the:
Address of the field containing the name of the site to be called

Address of the field in which the IP number and port to be called are
to be loaded
Address of the TCP/IP connection parameters:
* Data flow control timer in hundredths of a second (two binary
bytes)
Default value: 0
* Reserved address (one binary byte)
* Time-out value in minutes (one binary byte)
Default value: 4
Address of the field in which the port number (two binary bytes)
and the name of the host to be called (24 EBCDIC characters)
must be loaded; this parameter is valid if the IBM TCP/IP
interface (Release 3.2 or later) is used.
Possible actions: The exit must store a return code in register 15 indicating the action
to be taken by Inter.Pel.
R15 = 0 : The exit loads the IP number and port in the field to
which the second word in the parameter list points.
R15 = 4 : Inter.Pel must dial the IP number and port using the
IPTABLE data for this site. The exit can load the site
name in the field to which the first word in the
parameter list points.
R15 = 8 : Inter.Pel must not execute the call.
R15 =12 : Inter.Pel must use the port number and host name in
the field to which the fourth word in the parameter list
points for the external connection. Inter.Pel uses the
host name as an argument for the
GETHOSTBYNAME macro-instruction, which will
return the IP number to be called. This return code can
be set if the IBM TCP/IP interface (Release 3.2 and
onwards) is used.
Default program : Ask Inter.Pel to determine the call parameters.
A sample TCP/IP outgoing connection management exit can be found in the SAMPLIB
library EXIPOUT member.
TITLE 'EXIPOUT : TCP/IP OUTGOING CALL EXIT'

***********************************************************************
*
* FUNCTION :
* - VERIFY OUTGOING CALL
* - ACCEPT OR REFUSE CONNECTION

* - PROVIDE NUMBER OR HOST NAME (ALIAS) TO CALL
* OR LET Inter.Pel SET CALLED NUMBER FROM 'IPTABLE' TABLE.
*
* INPUT : R1 CONTAINS PARAMETER LIST ADDRESS :
* 00 - SITE NAME ADDRESS
* SITE NAME IS A 25 BYTES EBCDIC FIELD LEFT JUSTIFIED.
*
* 04 - AREA (COULD BE SET BY EXIT)
* LENGTH (XL1) (ALWAYS X'06')
* PORT NUMBER (XL2)
* IP ADDRESS (XL4)
*
* 08 - PARAMETERS : TIMER (XL2) IN HUNDRED OF SEC
* RESERVED (XL1)
* TIME OUT (XL1)
*
* 12 - AREA (COULD BE SET BY EXIT)
* PORT NUMBER (XL2)
* HOST NAME (ALIAS) (CL24)
* HOST NAME SHOULD BE A 24 BYTES EBCDIC FIELD
* LEFT JUSTIFIED.
*
*
* OUTPUT : R15 -- > 0 - THE PORT NUMBER AND ADDRESS IP TO CALL
* ARE SET BY EXIT
* R15 -- > 4 - Inter.Pel WILL SET CALLED NUMBER FROM
* 'IPTABLE' TABLE.
* R15 -- > 8 - CONNECTION REQUEST SHOULD BE REJECTED.
* R15 -- >12 - THE PORT NUMBER AND HOST NAME (ALIAS) TO CALL
* ARE SET BY EXIT
***********************************************************************
***********************************************************************
* LINK EDIT : NORENT
* LOAD MODULE 'EXIPOUT'
***********************************************************************
SPACE 3
EXIPOUT PELIDEB
*
B RET4 Inter.Pel SHOULD USE IPTABLE
*
*********************************************************************
* SEARCH IN INTERNAL TABLE (IPNOTAB) *
* IF SITE NAME FOUND, THEN R15=0 OR R15=12 DEPENDING ON *
* HOST NAME (BLANK OR NOT) *
* ELSE CALL WILL BE REJECTED (R15=8) *
*********************************************************************
*
L R2,0(R1) POINT TO SITE NAME
L R3,4(R1) POINT TO Inter.Pel NO AREA
L R4,12(R1)
*
LA R15,IPNOTAB
LOOP EQU *
CLC 0(25,R15),0(R2) SITE NAME MATCH
BE SITEF YES
LA R15,25+4(R15) POINT TO NEXT SITE ENTRY
CLI 0(R15),X'FF' END OF LIST
BNE LOOP

B RET8 SITE NAME IS NOT IN TABLE, SO REJECT
*
SITEF EQU *
ICM R14,15,25(R15) POINT TO FORMATTED IP ADDRESS
*
CLI 7(R14),C' ' HOST NAME = SPACES ?
BE SET_IPAD YES, SO SET IP ADDR
*
MVC 0(2,R4),1(R14) MOVE PORT NUMBER INTO OUTPUT AREA
MVC 2(24,R4),7(R14) MOVE HOST NAME INTO OUTPUT AREA
B RET12
*
SET_IPAD DS 0H
SR R15,R15
IC R15,0(R14) GET LENGTH OF NUMBER
EX R15,IPMVC MOVE NUMBER IN Inter.Pel AREA
B RET0 END
IPMVC MVC 0(0,R3),0(R14)
*
IPNOTAB EQU *
DC CL25'SITE1',AL4(ASITE1)
DC X'FF'
DS 0F
********************** PORT ****** IP ADRESS ** HOST NAME (ALIAS) ****
ASITE1 DC AL1(6),AL2(3501),AL1(127,0,0,1),CL24' '
ASITE2 DC AL1(6),AL2(3502),AL1(000,0,0,0),CL24'HOST2'
ASITE3 DC AL1(6),AL2(3503),AL1(000,0,0,0),CL24'HOST3'
**********************************************************************
DS 0F
RET0 EQU *
XR R15,R15 CALL ACCEPTED
B RETURN PORT NUMBER AND IP ADDR SET BY EXIT
RET4 EQU *
LA R15,4 CALL CHECKED BY Inter.Pel
B RETURN
RET8 EQU *
LA R15,8 CALL REJECTED
B RETURN
RET12 EQU *
LA R15,12 CALL ACCEPTED
B RETURN PORT NUMBER AND HOST NAME SET BY EXIT
RETURN EQU *
PELIRET
PELIEND
END

E.6 INITIALIZING THE IPTABLE
A new keyword has been added to the PELPARMS library startup member.
This keyword is TCPLIST=xx, where xx is the suffix of the PELTCPxx member in the
PELDFNDS library.
PELTCPxx contains the list of members in which the IP definitions are created (see Section
E.2.2).
E.7 DISPLAYING AND MODIFYING IPTABLE ENTRIES
The IPTABLE entries are displayed via menu 7.7 of the Inter.Pel monitor.
The IPTABLE is updated dynamically via menu 6.6 of the Inter.Pel monitor.
E.8 TCP/IP TRACES
E.8.1 TCP/IP TRACES IN AN INTERLINK SNS/TCPACCESS ENVIRONMENT
TCP/IP traces available with the Interlink product can be obtained by running the following
JCL.
//JOBNAME JOB ACCOUNT,'TSO PROC ',MSGCLASS=X,CLASS=A,

// NOTIFY=&SYSUID
//*
//* EXECUTION DE ACPEEP
//*
//S1 EXEC PGM=IKJEFT01,REGION=2M,DYNAMNBR=100
//STEPLIB DD DSN=SYS1.TCP200.LINK,DISP=SHR
//SYSTSIN DD *,BLKSIZE=80
ACPEEP nn.nn.nn.nn,Hostname / USER=User1 PASSWORD=xxx
/*
where:
nn.nn.nn.nn is the IP address of the remote site
Hostname is the name of the remote system
User1 is the TSO user
xxx is the User1 password

APPENDIX F USING HSI
F.1 INTRODUCTION
HSI (High level Security Interface) is a proprietary mechanism integrated into the XFB
monitors to perform the following security functions:
- Authentication
- Integrity
- Confidentiality
This mechanism is integrated at the monitor network layer level, and is therefore transparent
with respect to the file transfer protocols.
F.1.1 Authentication
Authentication can be performed either by transferring a password and encrypted elements

internally or via two-way authentication mechanisms based on the use of the RSA algorithm
and X.509 certificates.
If X.509 certificates are not used, HSI enables two-way authentication via an internal
algorithm, and guarantees a secure exchange of the key used for DES or triple DES
encryption.
Two-way authentication uses the R.S.A. algorithm.

This algorithm is of the asymmetrical key (or public) key type: two different keys are used for
encryption and decryption. A message encrypted with one of the keys can only be decrypted
with the other. One of the keys (the so-called private key) belongs to one of the participants
who never discloses it; the other (the so-called public key) is broadcast to the entire network.
This algorithm resolves the problem of key exchanges, since the only key to be broadcast is
public; however, the complexity of this algorithm prevents it from processing large volumes
for performance reasons.
HSI uses the keys provided by the X.509 certificates (Release 1, 2 or 3) to perform this
operation.
Installation and Implementation Guide Using HSI F-1

F.1.2 Encryption
Encryption ensures that the messages exchanged can only be read by the two entities involved
in the connection, guaranteeing exchange confidentiality. This is performed by using the DES
symmetric key encryption algorithm. To perform these operations, the issuer and receiver
have and use the same key for encryption and decryption purposes. The major downfall with
this type of algorithm is that the key must be exchanged between the two partners before any
operation can take place, which poses a significant risk of interception. The problem of
transferring the DES key is resolved by encrypting it in RSA mode and transmitting it during
the two-way authentication phase.
There are two DES levels: basic DES, which although no longer very reliable, is efficient, and
triple DES, which is much more secure. Both can be used in HSI to guarantee confidentiality.
F.1.3 Sealing
Sealing guarantees the integrity of the messages exchanged by ensuring that they are not
altered during the transfer between the two connected entities. Sealing involves associating
the generated data with a polynomial (message digest) calculated from the exchanged data.
The receiver can then recalculate the HASH with respect to the received data and compare it
with the sender's HASH to check that the message has not been corrupted. The HASH is sent
encrypted by HSI in triple D.E.S mode, using the encryption key exchanged during the two-
way authentication phase.
F.1.4 X.509 Certificates
An X.509 certificate consists of a set of information associated with a dual key that can be
used by a public key encryption algorithm (RSA for example). This information and the
public key are authenticated by the electronic signature of the authority that issued the
certificate. To check the validity of the certificate, the authority's public key contained in the
special certificate called the "authority certificate" is required.
The information provided consists of the user identifier, the public key associated with the
certificate, the certificate version, the certificate validity date, the name of the authority that
signed the certificate, the serial number, and so on.
The certificates exist in various formats that are often standardized (PEM or ASN1 formats
for example).
The "tools" used to manage and get these certificates are called the PKI (Public Key
Infrastructure).
Before you can use an X.509 certificate, you must therefore have:
- The user certificate

- The associated private (or secret) key
- The authority certificate to check its electronic signature

F.2 PRINCIPLES OF INTEGRATION IN Inter.Pel
Access to the security functions is directly integrated into the Inter.Pel network layers and
does not currently require user exits or external programs to be called during the transfer.
Integration into Inter.Pel is mainly via parameter settings. For each communication profile,
you must determine whether or not you want to implement HSI security, and if you do, the
security level required and the security elements to be used (password, certificate).
If you are using X.509 certificates, you must provide the monitor with the following elements
for each communication profile implementing this feature:
- X.509 certificate to be used

- Associated authority certificate
- Associated private key
These parameters are extracted from sequential files and stored in a table in memory, when
the monitor is started up. They are then queried during the transfer via an alias associated with
the communication profile. Two files are used, one for the authority certificates and the other
for the X.509 certificate/private key pairs.
A batch utility is used to add or update the various elements associated with the X.509
certificates in the files.
The associated private keys are stored encrypted in the file and can never be accessed by
the utility in clear form. They remain encrypted when the files are loaded into the
memory at monitor startup and are only decrypted when they are used during a
transfer.
A transaction is used on the monitor to recreate the X.509 element table in memory if it is
updated during a monitor session.
The names of the files to be used can be found in the general Inter.Pel parameters. The
certificate aliases are a communication profile parameter.

Inter.Pel Operation Diagram
Inter.Pel
Inter.Pel
TABLES
X .509 CE RTIFIC ATES /

P RIV ATE KE YS
L P
O R N
A O E
D T T
I O W
N C O
G O R
L K
AU TH O R ITY
CER TIFIC ATES
X .509
TABLES

F.3 PROCESSING IN THE X.509 ELEMENT FILES
The security elements are processed in two phases in Inter.Pel. During the first phase, the user
creates a file with a specific format containing the elements to be processed. If this file
contains a private key, it is encrypted in the triple DES CBC mode from a 16-character
password passed to the file creation utility. The user is responsible for developing this utility.
A utility (PELGX509) is then used to integrate the received elements into the files used by
Inter.Pel. It associates the X.509 certificates and private keys with the alias used to link them
with the communication profile. The password used to encrypt the private key is passed to this
utility as a parameter to decrypt the key and reencrypt it using the Inter.Pel internal algorithm.
You must create the files before the first elements are added. The file format is:
- RECFM=FB
- LRECL=5000
F.3.1 File Element Processing Procedure
Example processing a new certificate in the files:
ADMINISTRATION SYSTEM TARGET SYSTEM
Alias LOAD
USER UTILITY
PROGRAM password password X.509
CERTIFICATES
PRIVATE
KEYS
AUTHORITY
CERTIFICATES
WORK
FILE
WORK
FILE

F.3.2 X.509 Element Retrieval Program
The user is responsible for developing this program. It is designed to create a temporary file
containing the security elements in a format recognized by Inter.Pel. This file is then
broadcast, if necessary, to the target systems, to populate the files used by the monitors with
the security elements. This program must use an encryption function in the triple DES CBC
mode to protect the private key associated with an X.509 certificate during data transfer. The
key used for this encryption is supplied as a password when the utility is executed on the
target system for decryption purposes.
The format of the temporary file is described in the following paragraph.
F.3.3 Utility Populating the Inter.Pel Files with the X.509 Elements
This Inter.Pel utility is used to populate the "X.509 certificate/private key" and "authority
certificate" files with the elements received in the temporary client file.
This utility decrypts the private keys received in triple DES mode using a password set when
the temporary file was created. This password is one of the parameters passed to the utility.
If a user X.509 certificate and private key are received, it assigns an alias to link this pair with
a security profile in Inter.Pel. With the alias, this utility either adds or replaces an X.509
certificate/private key pair. If an entry does not exist when replacing the pair, the entry is
added. If an entry already exists when adding the pair, the utility terminates with an error
code. The private key and certificate are also checked for consistency.
In the case of an authority certificate, the certificate identifier is used for certificate
management purposes in the Inter.Pel files. With this key, the utility either adds or replaces an
entry. If an entry does not exist in replace mode, the entry is added. If an entry already exists
in add mode, the utility terminates with an error code.
The temporary file can contain n authority certificates and/or one X.509 certificate/private key
pair.
Parameters passed to the utility:
- Decryption password (if a private key is received)

- Alias to be associated with the X.509 certificate/private key pair
- ADD/REP function
Files used by the utility:
- Temporary file (containing the elements to be processed)

- Inter.Pel X.509 certificate and private key file
- Inter.Pel authority certificate file
- Inter.Pel parameter file (PELPARMS)
The format of these files is described in the following paragraph.

F.3.4 File Formats
F.3.4.1 Temporary File
Offset Length Parameter Notes

0 4 Record type KEY in ASCII = private key
USER in ASCII = X.509 certificate
AC in ASCII = authority certificate
4 2 Version Certificate version in ASCII:
10 for version 1, 30 for version 3
Not used for private keys
6 4 Certificate format PEM or ASN1 word (in ASCII)
Not used for private keys
10 2 Element length
12 Variable Element Private key encrypted in the triple DES
CBC mode
X.509 certificate
or authority certificate
A file can only contain one X.509 certificate/private key pair and/or n authority certificates.
F.3.4.2 X.509 Certificate and Private Key File

0 24 Alias
24 4 Certificate format ASN1
28 2 Certificate length
30 Variable Certificate
xx 2 Private key length
xx Variable Encrypted private key
F.3.4.3 Authority File

0 2 Name length
2 Variable Certificate name
xx 2 Certificate length
xx Variable Authority certificate

F.3.5 SAMPLE RUN-TIME JCL
The following JCL provides an example of how the MVS utility is executed to process the
temporary X.509 certificate files.
//PEL1
//PEL2
//STEP01 EXEC PGM=PELGX509,REGION=4M,
// PARM='ALIAS,0123456789ABCDEF,REP'
//STEPLIB DD DISP=SHR,DSN=INTERPEL.LOAD
// DD DISP=SHR,DSN=CEE.SCEERUN
//PELPARMS DD DSN=IIIIIIII.INTERPEL.PARMLIB(ZPARMSRQ),DISP=SHR
//SYSIN DD DSN=IIIIIIII.INTERPEL.X.509.INPUT,DISP=SHR
//CAFILE DD DSN=IIIIIIII.INTERPEL.X.509.CA,DISP=MOD
//USFILE DD DSN=IIIIIIII.INTERPEL.X.509.US,DISP=MOD
//LISTE DD SYSOUT=*
//ZZZZZZZ EXEC PGM=IEFBR14
where:
PARM: three parameters
- Alias (maximum of 24 characters) associated with the user key/private
key record
- Key (maximum of 16 characters) used on the client workstation to
encrypt the private key (triple DES CBC mode)
- Function (three characters): ADD (update not authorized) or REP
(update authorized, change to add mode if not found)
SYSIN: temporary file (containing the elements to be processed)
LISTE: report file (RECFM=FBA,LRECL=133)
USFILE: Inter.Pel X.509 certificate and private key file
(DISP=MOD, created with RECFM=FB/LRECL=5000)
CAFILE: Inter.Pel authority certificate file (DISP=MOD, created
with RECFM=FB/LRECL=5000)
PELPARMS : Inter.Pel parameter file
F.3.6 RETURN CODES
- 0: execution OK
- 8: error during execution, refer to the error messages in the job report

F.4 DEFINITIONS IN INTER.PEL
Six parameters are added to the communication profile definition (GENTER) and two to the
general parameters (GENDEB), to provide HSI with the necessary information.
F.4.1 GENDEB Macro
HSIDSNCA='dsname'
Name of the file containing the authority certificates. This file is updated by
the PELGX509 utility.
Default: none.
HSIDSNUS='dsname'
Name of the file containing the user certificates and their associated
encrypted private keys. This file is created by the PELGX509 utility.
Default: none.
F.4.2 GENTER Macro
HSIALIAS={xxx...xxx}
Identifier (maximum of 24 characters) of the X.509 user certificate used for
transfers by this line handler.
Default: not used.
HSIPROFI={D0,D1,D3,R0,R1,R3|NO}
Maximum HSI security level for incoming calls:
D0 - internal authentication, SHA integrity, no confidentiality
D1 - internal authentication, SHA integrity, basic DES confidentiality
D3 - internal authentication, SHA integrity, triple DES confidentiality
R0 - certificate-based authentication, SHA integrity, no confidentiality
R1 - certificate-based authentication, SHA integrity, basic DES
confidentiality
R3 - certificate-based authentication, SHA integrity, triple DES
confidentiality
NO - no security
Default: NO.
HSIPROFM={D0,D1,D3,R0,R1,R3|NO}
Minimum HSI security level for incoming calls:
confidentiality
confidentiality
NO - no security
Default: NO.

HSIPROFO={D0,D1,D3,R0,R1,R3|NO}
HSI security level used for outgoing calls.
confidentiality
confidentiality
NO - no security
Default: NO.
HSIPWDL={xxx....xxx}
HSI password (maximum of 64 characters) used by the local site.
Default: password not used.
HSIPWDR={xxx....xxx}
HSI password (maximum of 64 characters) used by the remote site.
Default: password not used.

F.5 RESTRICTIONS
HSI can only be used with the following file transfer protocols:
- PEL
- PeSIT Hors-SIT
- PeSIT SIT
- ODETTE
HSI cannot be used with the following communication protocols:
- LU 6.2
- PC PAD
- NETEX

APPENDIX G XFB.SCOPE AGENT
G.1 INTRODUCTION
XFB.Scope is an Axway product monitoring transfers executed by the XFB.Monitors. It

consists of a server installed on a UNIX or NT system and agents installed on the systems
running the XFB.Monitors. These agents route the messages sent by the monitors to the server.
This guide describes how to install and use the notification agent on MVS systems. It explains
how to:
- Install the agent

- Configure an agent
- Configure the XFB Monitor(s)
- Run the agent
The XNTF agent is integrated into a file transfer monitor. This monitor may be either Inter.Pel
or CFT from Axway's XFB (eXtended File Broker) range.
The agent generates messages from file transfer events. To transmit these messages to the
Scope server, it uses the QLT protocol. QLT (QueuerLess Transport) is a proprietary protocol
using the TCP/IP network.
Within the XFB.Scope package, the notification agent is called the XFB.Scope agent.
The agent and monitors communicate via the IBM XCF interface (Cross-system Coupling
Facility). This interface allows the agent to receive events from several monitors running in a
Sysplex environment.
All the components required to install the XFB.Scope agent on MVS systems can be found on
the Inter.Pel installation tape.
Installation and Implementation Guide XFB.Scope Agent G-1

G.2 PREREQUISITES
The XFB.Scope agent can be used in the following minimum environment:
- OS/390 Release 2.4
- For TCP/IP communications:
- eNETWORK Communications Services TCP/IP, OS/390

version
or
- Sterling Software SOLVE:TCPaccess (INTERLINK)
Release 5.2 CUM9907
- Run-time environment:
- Language environment

G.3 INSTALLING XFB.SCOPE
The files required by the XFB.Scope agent must be installed at the same time as the XFB
monitor files.
G.3.1 Adapting the Installation JCLs to the Production Environment
The following JCLs located in the CNTL library of the monitor are specific to the agent:
1. NT00CUST : customization of the installation JCLs and the agent

2. NT10LTCP : module link editing
3. NT20MSG : file message creation
4. NT30INST : agent configuration file creation
5. NT40DEF : agent buffering file allocation
These JCLs must be executed in the order indicated above.
The following paragraphs give a brief description of the JCL features for agent users.
G.3.2 Customizing the XFB.Scope Agent Installation Files (NT00CUST)
The NT00CUST member is used to customize the installation files. This JCL must only be run
if the JCLs were not customized when the monitor was installed.
//jopname JOB account,'NT00CUST',

// CLASS=class,MSGCLASS=msgclass,NOTIFY=userid
jobparm
//*
//* Issue a CHANGE 'NTFV1.' 'YOUR.DATASET.PREFIX.' ALL
//*
//* After 'submit', exit the edit to 'free' the file
//*
//CLIST EXEC PGM=IKJEFT01
//SYSPROC DD DISP=OLD,DSN=ntfv1.CNTL
//*
//SYSTSIN DD *
%NT01CUST ntfv1.CNTL NT01MEML
/*
//CFTIN DD DATA,DLM='@@'
jobname 'JOBPR'
userid '&SYSUID'
account '(XXXXXX)'
msgclass 'R'
class 'G'
jobparm '/*JOBPARM ROOM=A116'
sysout '*'
prdlib 'NTFV1
prdvol 'VOLUME'
prdunit '3390'
sysda VIO
le370 'CEE'

tcpibm 'TCPIP'
lang 'FR'
*
@@
//*
Important:
- The parameters in bold must be adapted to your environment.

- The keywords must be in lower-case characters.
- The value of each keyword must be delimited by quotes.
- The order of the keywords must not be changed.

The various keywords are explained in the following table.
Keyword Meaning
jobname Names of the jobs submitted during installation (maximum of eight
characters).
userid User name with which the installation JCLs will be submitted
(NOTIFY).
account Account Number with which the installation JCLs will be submitted.
msgclass Message output class.
class Installation JCL execution class.
jobparm Parameters related to the installation JCLs for JES2 ( //* if not used).
sysout Execution report output class.
prdlib Inter.Pel monitor file creation alias.
prdvol Name of the file creation volume.
prdunit Type of disk drive.
sysda Type of disk drive for work files (SYSUTx or SYSDA).
le370 LE/370 library alias.
tcpibm IBM TCP/IP or SOLVE TCPaccess library alias.
lang Language chosen (EG for English or Fr for French) for the generated
log messages
The names of the message files used consist of:
prdlib + "NTFMSG" + lang
G.3.3 LINK EDITING the Agent Modules (NT10LTCP)
The load modules can be found in the Inter.Pel load module library. The purpose of this phase
is to resolve any compatibility problems from one version to another (LE/370 or TCP/IP) or to
enable you to use SOLVE:TCPaccess.
This job edits the links for all the XNTF agent modules using an internal procedure.
If the agent is installed separately from the monitor, the object library used by the monitor
must be added at both stages in the procedure (XFBO DDNAME).

Using SOLVE:TCPaccess
Modify the procedure provided and customized for IBM IBM/IP as follows.
Description of the procedure:
1. Replace L=I with L=S.
2. Link edit phase, SYSLIB DDNAME: remove the comment for the reference to
the "&TCP..LOAD" PDS.
G.3.4 Creating the Message File (NT20MSG)
This phase creates the files containing the log messages used by the XFB.Scope utilities.
The choice of language is given when the internal job procedure is called.
The name of the sequential file created consists of:
prefix + ".NTFMSG" + language
The prefix and language are selected when the XNTF agent installation files are customized
(see the corresponding paragraph).
G.3.5 Creating an Agent Configuration (NT30INST)
An agent uses three types of information:
- A configuration
- The server communication parameters
- The buffering file definition parameters
The NTFINST utility is used to create PDS members containing this information.
Only the member containing the configuration is referenced in the agent run-time JCL.
The utility has three input files:
- INSTALL : product installation library

- CONFIG : library in which the generated PDS members are to be saved
- NTFPARM : parameter list
The utility creates three output members:
- NTFCONF : containing the configuration

- NTFPROF : containing the server access information
- NTFDEF : containing the declaration for the VSAM file to be defined

Sample agent creation JCL:
//jobname JOB account,'NT30INST',

jobparm
//* ---------------------------------------------------------------+
//* !
//* NT30INST : CREATION AGENT CONFIGURATION FILE !
//* !
//* AFTER 'SUBMIT', EXIT THE EDIT TO 'FREE' THE FILE !
//* !
//* ------------------------(C) COPYRIGHT Axway--------------------+
//*
//NTFCONF PROC OUT=sysout,
// QUAL=prdlib
//*
//INSTALL EXEC PGM=NTFINST,REGION=4000K
//*
//STEPLIB DD DISP=SHR,DSN=&QUAL..LOAD
//*
//INSTALL DD DISP=SHR,DSN=&QUAL..CNTL
//CONFIG DD DISP=OLD,DSN=&QUAL..CNTL
//*
//NTFPARM DD DUMMY
//SYSPRINT DD SYSOUT=&OUT
//SYSOUT DD SYSOUT=&OUT
//CEEDUMP DD SYSOUT=&OUT
//SYSUDUMP DD SYSOUT=&OUT
//*
// PEND
//*
//* EXECUTE THE PROC
//*
//GO EXEC NTFCONF
//INSTALL.NTFPARM DD *
*
svcnb '202' - SVC defined with XFB.Monitor
ntfqueue 'PELSCOPP' - XCF Communication
disctime '30' - Disconnect connection
arm 'NO' - ARM policy
*
qltport '44444' - Server Port Number
qltserver 'address' - Server Adress
qlttime '3' - Communication Timeout
*
ntffile 'prdlib.TAMPON' - Buffer file
ntfvol 'prdvol' - Volume
ntflen '2000' - Record Length
ntfnbr '10000' - Message Number
The parameters in bold are replaced during the customization phase.
Important:
- Keywords are not case-sensitive.
- Most of the parameters have a default value.
- The order of the keywords can be changed.
- In the JCL provided, the installation library will contain the generated files
(CONFIG DDNAME).
This library is referenced in the buffering file definition JCL (NT40DEF)
and the agent run-time JCL (NTFAGENT).

Keyword Explanation
svcnb Number of the SVC used to communicate with the Inter.Pel
monitors if the library is not "APF" authorized.
This SVC is installed for the Inter.Pel monitor and its number must
correspond to the monitor PELPARMS file COMSVC parameter.
Default: 0.
ntfqueue Name of the queue used to communicate with the monitors.
It must be equal to the PELPARMS file SCOPNAME parameter for
the monitor.
Mandatory.
disctime Time-out (in seconds) before the agent closes an open socket.
If the time-out is set to zero, the server must close the socket.
Default: 0.
arm Element name used to register with ARM, or NO if the address
space does not need to register with ARM.
qltport Port number of the XFB.Scope QLT server.
Default: 44444.
qltserver TCP/IP address or name of the QLT server.
Mandatory.
qlttime Time-out value in seconds for a message sent to the QLT server.
This value can be changed in agreement with the XFB support
service.
filter List of filters (see Filter Table).
Default: no filter.
If you modify one of the following parameters, the NT40DEF
JCL must be run to recreate the buffering file.
ntffile Name of the buffering file.
Mandatory.
ntflen Maximum message size.
Default: 2000.
ntfnbr Maximum number of messages to be stored in the buffering file.
Mandatory.
ntfvol Name of the volume on which the buffering file is to be created.
Mandatory.
You cannot change the following parameters without also
modifying the XFB.Scope server.
qlog Name of the target queue.
Default: +ELS.
qtrans Name of the target.
Default: +TCS.
The following parameters are only required if the declarations for
several agents are stored in the same library.

Keyword Explanation
config Name of the generated member containing the configuration.
Default: NTFCONF.
profile Name of the generated member containing the information required
to communicate with the server.
Default: NTFPROF.
deffile Name of the generated member containing the buffering file VSAM
declaration.
Default: NTFDEF.

G.3.5.1 Return Codes
Code Description
0 Normal shutdown, the installation is complete.
1 Configuration error.
A message indicates the incorrect parameter(s), specifying the type of
error (invalid value, missing parameter, and so on).
2 Utility initialization error.
A message indicates the cause of the error (such as a missing file).
4 Configuration file creation problem.
A message indicates the cause of the problem and the name of the
file.
99 Utility internal error.
Inform the XFB support service.
G.3.6 Defining the Buffering File (NT40DEF)
This JCL defines the buffering file, using the declaration generated during the previous phase.
Sample buffering file definition JCL:

//jobname JOB account,'NT40DEF',
jobparm
//* ---------------------------------------------------------------+
//* |
//* NT99CUST : CREATION AGENT CONFIGURATION FILE |
//* |
//* ------------------------(C) COPYRIGHT Axway--------------------+
//*
//NTFDEF PROC OUT=sysout,
// FILE=NTFDEF, DEFAULT FILE
// QUAL=prdlib
//*
//DEFINE EXEC PGM=IDCAMS
//SYSIN DD DISP=SHR,DSN=&QUAL..CNTL(&FILE)
//*
// PEND
//*
//* Execute the PROC
//*
//GO EXEC NTFDEF
//*
The parameters in bold will be replaced during the customization phase.

The file is declared during the agent installation phase. The member generated during this
phase is referenced by the FILE and QUAL internal procedure parameters. It is as follows:
//*-------------------------------------------------------------*/
//* DELETE FILE */
//*-------------------------------------------------------------*/
DELETE (name of tampon) CL;
SET MAXCC = 0 ;
//*-------------------------------------------------------------*/
//* DEFINE FILE */
//*-------------------------------------------------------------*/
DEFINE CLUSTER (NAME(name of tampon) -
VOL(volume) -
RECSZ(2000 2000) -
FSPC( 0 0 ) -
RECORDS(10000 1) -
SHR (2 3 ) -
NUMBERED );

G.4 CONFIGURATION
The monitor and agent communicate to notify all monitoring events, such as:
- MAILBOX activities corresponding to transfer monitoring (TCS, Track and

Control System); they are recorded via the MAILBOX write exit
- Inter.Pel log messages corresponding to logging activities (ELS, Event
Logging System); they are recorded via the message user table
The actions to be taken on the Inter.Pel clients to supply the agent are as follows:
- Update the configuration (PELPARMS)

- Update the message user table (ZMSGTAB member)
- Implement the MAILBOX write exit to monitor transfers
The examples described later in this appendix can be found in the SAMPLIB library.
G.4.1 Updating the Inter.Pel Configuration
The SCOPNAME parameter (maximum of eight characters) in the PELPARMS file must be
equal to the ntfqueue parameter given when the agent was installed; see Creating an Agent
Configuration (NT30INST). This parameter must be specified in the PELPARMS file for all
Inter.Pel address spaces, including the BATCH address spaces.
Use the SCOPVERS parameter in the PELPARMS file to select the tracking product. Set the
value to V1 to select XFB.Scope and to V2 to select Sentinel.
G.4.2 Updating the Message Table
Two parameters in the message user table generation macro (GENUMSG) are used to define
the messages to be sent to XFB.Scope, the severity associated with each of these messages,
and the messages that trigger an alert.
SCOPE={NO|I|W|E}
Severity level at which the XFB.Scope monitoring tool is called:
NO - XFB.Scope is not called
I - information message
W - warning message
E - error message
Example : SCOPE=W.
Default : NO.
ALERT={YES/NO}
YES - the message triggers an alert in the XFB.Scope monitoring tool.
NO - no alert is triggered in the XFB.Scope monitoring monitor.
If the SCOPE parameter is set to NO, the ALERT parameter is
ignored.
Default : NO.

A sample definition is given in the ZMSGNTF member of the CNTL library.
G.4.3 selecting tracker level
TRACKER parameter is available in:

- PELPARMS file
- GENSITE definitions
- GENFILE definitions
- transfer requests
This will allow you to select the desired tracking level for each transfer.
This parameter is coded as follows :
XFB.SCOPE or Sentinel tracking activation.
Y - Mailbox records are sent to the tracker every time their
status changes.
S - Mailbox records are sent to the tracker only when their
status changes to 2, 4, 5, 6, 7, 9, A, C, I, N. Messages
selected in the messages table are always sent.
Default: Yes if SCONAME parameter is filled.
The value used for a transfer is selected as follows:
- If the parameter is provided in the transfer request then this value is used.
- Else, if the parameter is set in the GENFILE macro then this value is used.
- Else, if the parameter is set in the GENSITE macro then this value is used.
- Else the value in the PELPARMS file (or its default value) is used.
It is then easy to select which transfers must be tracked or not, with the fewest parameters
possible.
Note: these parameters are used at deposit time, any later modification will not be effective on
transfers already created.

G.5 OPERATIONS
G.5.1 Starting Up the Agent
The XFB.Scope agent must be started up before the Inter.Pel monitor to allow the
monitor startup messages to be intercepted.
Only the following two input files are required to run the agent program; the other files
are declared in the configuration:
- Configuration file, referenced by the CONFIG DD statement- Message file,

referenced by the MSGTAB DD statement
The configuration file is the file generated during the agent installation phase.
The program run-time parameter is "NTFQLT SYS".
If the name of the IBM TCPIP address space is not TCPIP, or if DNS is to be used, a
SYSTCPD card must be added to the JCL to define the required TCP parameters.
This job or STC must be authorized in the Open Edition group segment as it opens a
TCP connection.

G.5.1.1 Sample JCL
The following sample can be found in the NTFAGENT member of the CNTL library. If
the agent is installed separately from the monitor, the monitor load library must be
added in a steplib instruction.
//NTFAGENT JOB account,'AGENT NTF',
jobparm
//*
//* ---------------------------------------------------------------+
//* |
//* NTFAGENT : EXECUTE XFB-SCOPE MVS AGENT |
//* APF is mandatory for this program |
//* |
//* (C) COPYRIGHT Axway |
//* ---------------------------------------------------------------+
//*
//NTFAGENT PROC OUT=sysout,
// QUAL=prdlib,
// CONFIG=NTFCONF, Default configuration
// LANG=lang
//*
//NTFRUN EXEC PGM=NTFSCOPE,REGION=4000K,
// PARM='NTFQLT SYS'
//*
//CONFIG DD DISP=SHR,DSN=&QUAL..CNTL(&CONFIG) Config
//MSGTAB DD DISP=SHR,DSN=&QUAL..NTFMSG&LANG Error Msg File
//*
//*
// PEND
//* Execute the PROC
//GO EXEC NTFAGENT
The member generated during the agent installation phase is referenced by the CONFIG
parameter in the internal JCL procedure.

G.5.1.2 Log Files
The agent writes LOG messages in the files referenced by the LOGA and LOGB
DDNAMEs.
If these DDNAMEs are not present in the JCL (example supplied), these files are
allocated dynamically to SYSOUT.
A command (LOG SWAP) allows you to switch from one file to another (if the files are
not allocated to SYSOUT).
If sequential files are used, the oldest file is used as the LOG file when the agent is
started up.
G.5.1.3 Other Output Files
The program starts up several subtasks. Each subtask has its own trace file allocated
dynamically to SYSOUT.
The DDNAME of each file is "TRACEnnn", where nnn is the number of the subtask.
These traces are activated at the request of the XFB support service.
The trace for the NTFSCOPE program is the standard SYSPRINT output.
It always contains the list of subtasks that have been started up and indicates any
subtasks that have been stopped.
In the event of an error (subtask or utility), one or more messages are logged in the trace
files and centralized in the SYSOUT error file.
G.5.2 Commands
Commands can be passed to the agent via the console interface.

The structure of the commands from the console is as follows:
F <jobname>,<command>
G.5.2.1 Current Status: NTFQLT ACT
The agent generates "230 XNTF" messages giving the number of sent and pending
messages.
G.5.2.2 Activating the Log: NTFQLT LOGACT
The agent sends log messages for each event deposited in the buffering file and each
send operation to the server.

G.5.2.3 Deactivating the Log: NTFQLT LOGINACT
The agent stops sending log messages for each event deposited and each send operation
to the server.
G.5.2.4 Log Swapping: LOG SWAP
The two log files (LOGA and LOGB) are swapped.
G.5.3 Shutting Down the Agent
The job is stopped via the console interface and the following commands:
P jobname
or
F jobname, STOP

G.6 RETURN CODES
All codes different from zero are explained by one or more messages in the LOG file
and/or SYSOUT and TRACE files.
Code Description
0 Normal end of job.
1 SCOPE program or one of its subtasks.
The processes cannot be started up, or they stop immediately, due to
configuration errors.
Sample errors:
- An error occurred when the configuration file was opened.
- A parameter was not set in the configuration.
2 An error occurred when the inter-process communication interface
was initialized.
5 A problem occurred when the file containing the communication
profiles was read.
6 A problem occurred when the buffering file was opened (or
formatted).
7 The QLT communication mode was not declared or is not supported.
8 A problem occurred when the communication interface was
initialized.
9 A problem occurred when the buffering file and the queuer were
synchronized.
10 An error occurred when the buffering file was updated
12
11 An error occurred during a commit with the queuer.
60 No memory was available to start the subtasks.
80 An internal problem occurred during memory allocation.
84 No memory was available to receive all the queries from the
monitors.
90 A error occurred when allocating a file dynamically or opening a file
allocated dynamically.
93 The queue defined for a process is already used by another job.
97 An error was detected when using a memory-type file
98 Inter-process communication with the XFB monitor(s) or another
process is not active.
99 One of the processes cannot complete its initialization, or does not
stop.
999 An internal problem occurred when the memory blocks were released.
Other Subtask abend code value.

APPENDIX H IUI API SERVER
H.1 INTRODUCTION
IUI (Internet User Interface) is a Axway product used to access information from an
XFB.Monitor via a browser. It is also used to deposit transfer requests for the PeSIT Hors-SIT
and PEL protocols.
Transfers using these protocols, can be either frozen (status set to C) or restarted (status set to
9) through this interface.
It consists of a Java applet loaded from a WEB server, and a API server installed on the
system on which XFB.Monitor is running. This API server routes the requests from the
browser to the monitor and returns the responses.
This guide describes how to install and use the IUI API server on MVS systems. It explains
how to:
- Install the product

- Configure an API server
For information about the other XFB.IUI components, refer to the manual for this product.
The IUI API server is integrated into a file transfer monitor. This monitor may be either
Inter.Pel or CFT from Axway's XFB (eXtended File Broker) range. An API server address
space is required for each Inter.Pel cluster to be interfaced.
The API server and the monitors communicate via the IBM XCF interface (Cross-system
Coupling Facility). This interface allows the API server to receive events from several
monitors running in a SYSPLEX environment.
All the components required to install the IUI API server on MVS systems can be found on
the Inter.Pel installation tape.
Installation and Implementation Guide IUI API Server H-1

H.2 PREREQUISITES
The IUI API server can be used in the following minimum environment:
- OS/390 Release 2.4
- For TCP/IP communications:
- eNETWORK Communications Services TCP/IP, OS/390

version
or
- Sterling Software SOLVE:TCPaccess (INTERLINK)
Release 5.2 CUM9907
- Run-time environment:
- Language environment

H.3 INSTALLING THE IUI API SERVER
The files required by the IUI API server are installed at the same time as the XFB monitor
files.
H.3.1 Adapting the Installation JCLs to the Production Environment
The following JCLs located in the monitor CNTL library are specific to the API server:
1. IU00CUST : customizes the installation JCLs and API server

2. IU10LINK : link edits the modules
These JCLs must be executed in the order indicated above.
The following paragraphs give a brief description of the JCL features for API server users.

H.3.2 Customizing the XFB.IUI API Server Installation Files (IU00CUST)
The IU00CUST member is used to customize the installation files. This JCL must only be run
if the JCLs were not customized when the monitor was installed.
//jobname JOB account,'NT00CUST',
jobparm
//*
//* ---------------------------------------------------------------+
//* !
//* IU00CUST : CUSTOMISATION OF PARAMETERS !
//* !
//* Issue a CHANGE 'NTFV1.' 'YOUR.DATASET.PREFIX.' ALL !
//* !
//* After 'submit', exit the edit to 'free' the file !
//* !
//* ------------------------(C) COPYRIGHT Axway--------------------!
//CLIST EXEC PGM=IKJEFT01
//SYSPROC DD DISP=OLD,DSN=ntfv1.CNTL
//SYSTSPRT DD SYSOUT=sysout
//SYSPRINT DD SYSOUT=sysout
//*
//SYSTSIN DD *
%NT01CUST ntfv1.CNTL IU01IUIL
/*
//CFTIN DD DATA,DLM=''
************************************************************************
* *
* XFB-IUI Installation customization *
* ------------------------------------ *
* *
* Replace the provided sample according to your installation. *
* ALL KEYWORDS MUST STAY IN LOWER CASE *
* ALL VALUES MUST BE ENCLOSED IN QUOTES *
* DO NOT CHANGE THE ORDER OF THE KEYWORDS *
* All lines beginning with '*' are treated as comments and removed *
* *
************************************************************************
*
* keyword value
*
jobname 'JOBNAME' - Job name
userid '&SYSUID' - User identifier (for notify)
account '(XXXXXX)' - Account number
msgclass 'R' - Message class
class 'G' - Execution class
jobparm '/*JOBPARM ROOM=A116' - Job parm (//* if none)
sysout '*' - Sysout class
prdlib 'NTFV1' - Monitor library prefix
sysda 'VIO' - SYSUTx UNIT= VIO or SYSDA
le370 'CEE' - Le/370 data set prefix
tcpibm 'TCPIP' - IBM tcp/ip library prefix
* 'SNSTCP' or INTERLINK tcp/ip library prefix
cluster 'CLUSTER' - XFB.INTERPEL Cluster ID
port '1971' - Port Number for listen
svcnb '202' - XFB.INTERPEL SVC
arm 'NO' - ARM policy
*

//
Important:
- The parameters in bold must be adapted to your environment.

- The keywords must remain in lower-case characters.

- The order of the keywords must not be changed.
Keyword Meaning
jobname Names of the jobs submitted during installation (maximum of eight
characters).
userid User name with which the installation JCLs will be submitted
(NOTIFY).
account Account Number with which the installation JCLs will be submitted.
msgclass Message output class.
class Installation JCL execution class.
jobparm Parameters related to the installation JCLs for JES2 ( //* if not used).
sysout Execution report output class.
prdlib Inter.Pel monitor file creation alias.
sysda Type of disk drive for work files (SYSUTx or SYSDA).
le370 LE/370 library alias.
tcpibm IBM TCP/IP or SOLVE TCPaccess library alias.
cluster Name of the Inter.Pel cluster addressed by this API server (Inter.Pel
PELPARMS file CLUSTER parameter).
port Number of the port listening to the IUI workstations.
svcnb Number of the XCF communication SVC to be used if the API server
libraries are not authorized (COMSVC parameter in the Inter.Pel
PELPARMS files).
arm Element name used to register with ARM, or NO if the address space
does not need to register with ARM.

H.3.3 LINK-EDITING the API Server Modules (IU10LINK)
The load modules can be found in the Inter.Pel load module library. The purpose of this phase
is to resolve any compatibility problems from one version to another (LE/370 or TCP/IP) or to
enable you to use SOLVE:TCPaccess.
This job edits the links for all the API server modules using an internal procedure.
If the API server is installed separately from the monitor, the object library used by the
monitor must be added to both stages in the procedure (XFBO DDNAME).
This stage must also be executed if you want to install a TCP patch or upgrade.
Using SOLVE:TCPaccess
Modify the procedure provided and customized for IBM IBM/IP as follows.
Description of the procedure:
1. Replace L=I with L=S.
2. Link edit phase, SYSLIB DDNAME: remove the comment for the reference to
the "&TCP..LOAD" PDS.

H.4 CONFIGURATION
The IUI API server is configured in the PROFILE file of the API server startup JCL. This file
is used to describe different execution profiles; the profile to be used at startup is specified by
the EXEC card -TPT parameter in the execution step.
The profile description format is as follows:
(name)
parm1=value1
parm2=value2
where name defines the name of the profile to be referenced in the EXEC card parameter
when the API server is started up.
The possible parameters are as follows.
PORT={nnnnn|0}
Number of the listening port (updated by the installation JCL).
Default: 0.
ADDR={aaa.bbb.ccc.ddd|name|ANYHOST}
TCP address or name of the authorized server.
Default: ANYHOST (accept all servers).
SERVERMAX=nnnn
Maximum number of concurrent logins.
Default: 46.
Maximum: 250.
TRACE=nnn
Number of the subtask to be traced. This parameter must only be set at the
request of the XFB support service.
Default: 0 (main task).
RECVTIMEOUT={nnnn|1000}
Time-out in seconds before a connection is closed.
Default: 1000.

H.5 OPERATIONS
H.5.1 Starting Up the API Server
Only one input file, the configuration file referenced by the PROFILE DDNAME, is
required to run the API server program. This file is customized when the API server is
configured.
A log file (XFBLOGA DDNAME) can also be defined in the JCL. In this case, it must
be defined with the following DCB:
RECFM=FBA,LRECL=121
If this file is not defined in the JCL, it is allocated to SYSOUT.
If the name of the IBM TCPIP address space is not TCPIP, or if DNS is to be used for
the PROFIL file ADDR parameter, a SYSTCPD card must be added to the JCL to
define the required TCP parameters.
The run-time parameters for the program are as follows.
-CL : name of the Inter.Pel cluster to which this API server is assigned (Inter.Pel
PELPARMS file CLUSTER parameter).
-SVC : number of the communication SVC to be used if the library is not APF
authorized (Inter.Pel PELPARMS file COMSVC parameter).
-TPT : name of the profile defined in the PROFIL file to be used for execution.
These three parameters are updated by the installation JCL.
This job or STC must be authorized in the Open Edition group segment, as it opens a
TCP connection.

H.5.1.1 Sample JCL
The following sample can be found in the IUIRUN member of the CNTL library. If the
API server is installed separately from the monitor, the load library used by the monitor
must be added as a STEPLIB instruction.
//IUIRUN JOB account,'IUI SERVER',
jobparm
//*
//* ---------------------------------------------------------------+
//* !
//* IUIRUN : EXECUTE SERVER IUI !
//* !
//* (C) COPYRIGHT Axway !
//* ---------------------------------------------------------------+
//*
//IUIRUN PROC OUT=sysout,
// CLUSTER=cluster,
// SVCNB=svcnb,
// QUAL=prdlib,
// PROF=IUIPROF COMMUNICATION PROFILE
//*
//IUIRUN EXEC PGM=XFBPDMN,REGION=4000K,
// PARM='-CL &CLUSTER -SVC &SVCNB -TPT SERVER'
//*
//PROFIL DD DISP=SHR,DSN=&QUAL..CNTL(&PROF)
//*
//*
//*
// PEND
//*
//* EXECUTE THE PROC
//*
//GO EXEC IUIRUN
//

H.5.1.2 TRACE Files
The program starts up several subtasks, each of which has its own trace file allocated
dynamically to SYSOUT.
The DDNAME of each file is "TRACEnnn", where nnn is the number of the subtask.
These traces are activated at the request of the XFB support service.
In the event of an error (subtask or utility), one or more messages are logged in the trace
files and centralized in the SYSOUT error file.
H.5.2 Shutting Down the API Server
The job is stopped via the console interface and the following command:
P jobname
or via one of the following MODIFY commands:
F jobname, STOP
F jobname, STOP,QUICK
F jobname, STOP,FAST
The STOP command prevents any new connection from being opened, and shuts down
the product as soon as all existing connections are closed.
The STOP, QUICK command prevents any new connection from being opened, and
orders the subtasks to close all existing connections. The API server shuts down as soon
as all connections are closed.
The STOP,FAST command stops the API server immediately. If any subtasks are still
running, they terminate with an ABEND SA03.

H.6 RETURN CODES
All codes different from zero are explained by one or more messages in the XFBLOG
file and/or SYSOUT and TRACE files.
Code Description
0 Normal end of job.
1 API server initialization error.
Sample errors:
- XFBLOG file opening error
- Invalid or missing parameter
- TCP/IP initialization error
2 Subtask initialization error.
3 TCP/IP communication problem.
88 MVS environment initialization error (insufficient memory, program
not found, and so on).
96 XCF interface shutdown error.
97 MODIFY interface shutdown error.
98 MODIFY interface startup error.
99 XCF environment initialization error.

APPENDIX I SENTINEL
I.1 INTRODUCTION
Sentinel is an Axway product that enables you to track the flow of application-specific events,
notably the transfers effected by the XFB.Monitor. Sentinel replaces the earlier generation of
Axway monitoring tools, XFB.Scope.
Sentinel is composed of a server hosted on a UNIX or Windows machine, and Event Routers.
the XFB.Monitor can be installed either on the same machine as the Event Router or on an
independent machine. Event Routers collect messages generated and emitted by one or more
XFB.Monitors. Event Routers then direct the messages to the Sentinel Server.
An XFB.Monitor can connect directly to the Sentinel Server, or alternatively, communicate

via an Event Router which acts as a relay and/or concentrator.
In both cases, communication is made possible by the use of the Universal Agent integrated in
the Monitor, which acts as the notification agent.
In the Sentinel product, the notification agent is called the Universal Agent (UA).
In the MVS environment it is preferable to communicate with the server via the Event
Rooter instead of connecting directly to the server.
This document describes the use of the Sentinel agent installed on an MVS host. It explains
how to configure the XFB transfer monitor(s) to enable transfer monitoring.
The Sentinel documentation set includes an Event Router installation guide for the MVS
environment.
To configure the UA and the Event Router, refer to the Sentinel online documentation.
The Sentinel notification agent integrates into the file transfer monitor. The monitor can be
either the Inter.Pel or CFT element of the Axway XFB (eXtended File Broker) product.
The Event Router generates messages from transfer event information sent by the Universal
Agent. The Event Router uses the QLT protocol to send these messages to the Sentinel Server.
QLT (QueueLess Transport) is an Axway proprietary protocol that runs over TCP/IP.
On MVS, the communication between the Event Router and the UA running on the monitor
uses the IBM XCF (Cross-system Coupling Facility) interface. This interface enables the
Event Router to receive event information origination from several monitors operating in a
Sysplex environment.
Installation and Implementation Guide Sentinel I-1

I.2 PREREQUISITES
The Event Router requires the following environment:
- OS/390 V2.7.
- For TCP/IP communication:
- eNETWORK Communications Services TCP/IP version

OS/390
or
- Sterling Software SOLVE: TCPaccess (INTERLINK) Version
5.2 CUM9907.
- Execution environment:
- Language environment.

I.3 CONFIGURATION
The monitor sends information about tracked events to the Event Router. This information can
include details of:
- MAILBOX activities: information about the tracking of transfers (Tracking

and Control System) recorded by the internal MAILBOX update process.
- the links between transfers to be sent and the targeted applications, in the
case where these linked elements were indicated in the transfer request.
- Inter.Pel log messages, these messages are daily activities logs (ELS, Event
and Log System) recorded from the message table definitions.
To activate the communication to the Event Router, in Inter.Pel:
- Update the configuration (PELPARMS).

- Update the message table (member ZMSGTABS).
- If necessary, update the site (GENSITE) definitions to enable/inhibit the
transfer tracking for each site.
- If necessary, update the application (GENFILE) definitions to
enable/inhibit the transfer tracking for each application.
- Supply the new parameters relating to transfer requests and exits.
Sample definitions are located in the SAMPLIB library.

I.3.1 UPDATING Inter.Pel GENERAL PARAMETERS
Inter.Pel enables you to create tracking messages valid for either the XFB.Scope server or the
Sentinel Server. You activate tracking by setting the TRACKER= parameter in the
PELPARMS file. You select the target server by entering a value for the SCOPVERS=
parameter in the PELPARMS file.
For tracking by the XFB.Scope server, see Appendix G for details.
For tracking by the Sentinel Server, enter values for the following PELPARMS file
parameters:
Enables tracking by XFB.Scope or Sentinel
server.
SUM - Only the change of a status to 2, 4, 5, 6, 7, 9, A, C, I, N is sent
to the tracking server.
For both YES and SUM values, the messages in the message table are
sent to the tracking server.
This parameter is used during the creation of the transfer request. Any
further change in definition has no effect on existing transfers.
SCOPCF=(dsname[,member])
Optionally enter the second sub-parameter to specify the name of the
An example of configuration file is delivered in the ZTRACKER member of
the SAMPLIB library.
SCOPNAME=name
Name of the server waiting for the Sentinel tracking/log messages generated
by Inter.Pel.
This parameter is for information only. You can enter any mnemonic value
to identify the Sentinel server that is used to track events for this Inter.Pel.
It does not have to match any parameter from the configuration file or
Sentinel. However it is mandatory that it exists, for internal reasons.
Default: None.
SCOPVERS={V1|V2}
Default: None.
Enter values for these parameters in the PELPARMS file for all Inter.Pel address spaces,
including BATCH address spaces.

I.3.2 MESSAGE TABLE INTEGRATION
The macro used for the generation of the message table (GENUMSG) provides two
parameters for messages to be transmitted to Sentinel. These parameters enable you to define
the severity associated with each message, and enable you to define the messages that trigger
an alert.
SCOPE={NO|I|W|E}
Severity level for call to Sentinel:
NO - Do not call Sentinel.
I - Information message.
W - Warning message.
E - Error message.
EX: SCOPE=W.
Default: NO.
ALERT={YES|NO}
YES - The message generates an alert in Sentinel.
NO - No alert in Sentinel.
If the value of the SCOPE parameter is set to NO, the ALERT
parameter is ignored.
Default: NO.
For an example of this definition, refer to the ZMSGTABS member.
I.3.3 PARTICIPATION OF SITES OR APPLICATIONS IN Sentinel TRACKING
Parameter for the site generation macro (GENSITE) and application generation macro
(GENFILE) enables you to define whether or not a site or an application participates in
Sentinel tracking. This parameter also enables you to specify the tracking scope.
YES - Send to Sentinel or XFB.Scope, all mailbox modifications that
relate to transfers using this application or this site.
NO - Dont send to Sentinel or XFB.Scope, all mailbox modifications
that relate to transfers using this application or this site.
SUM - Only sends to Sentinel or XFB.Scope, the principle modifications
of the mailbox status that relate to transfers that use the application
or the site.
This parameter is used during the creation of the transfer request. Any
further change in definition has no effect on existing transfers.
Default: See the rules for managing the use of the TRACKER parameters,
below.
I.3.4 CONFIGURING THE AGENT AND THE EVENT ROUTER
The Sentinel documentation set includes an installation guide for the MVS environment.
Refer to: Installation manual Sentinel Event routers V2.2 for MVS
To configure the UA and the Event Router, refer to the Sentinel online documentation.
For an example of an UA configuration file, refer to the ZTRACKER member of the

SAMPLIB library.

I.4 OPERATIONS
I.4.1 PARAMETERS CONCERNING REQUESTS
A Sentinel tracking function enables applications (sources or targets of transfers) to establish a

logical link with the reference application, in order to trace all steps of transfer handling.
To enable the processes of this CycleLink function, four request-related parameters are
available in the PELICA2 utility and in the INTBAL API.
TRACKER : Option for tracking of the transfer by Sentinel :

YES - Send all mailbox modifications relating to transfers using this
application (GENFILE) or this site (GENSITE) to Sentinel or
XFB.Scope.
NO - Do not send all mailbox modifications relating to transfers using
this application (GENFILE) or this site (GENSITE) to Sentinel
or XFB.Scope.
SUM - Only send principal mailbox state modifications for transfers
using this application (GENFILE) or this site (GENSITE) to
Sentinel or XFB.Scope (states 2, 4, 5, 6, 7, 9, A, C, I, N).
Default: See hierarchy of TRACKER parameters in the paragraph New
parameters concerning Requests.
Protocol(s): All.
TRKCID : Character identifying the Sentinel event to which the tranfer is linked. When
available, the transfer identifier is automatically linked to the event when the
request is received. This enables end-to-end inter-applicative tracking.
This event must have been created prior to this transfer request, either
through another Axway product or using the UA interface.
Maximum length 30 characters.
Default: None.
Protocol(s): All.
TRKCIDX : Hexadecimal identification of the Sentinel event to which the transfer is

linked. When available, the transfer identifier is automatically linked to the
event when the request is received. This enables end-to-end inter-applicative
tracking.
Maximum length 60 digits (30 bytes).
Default: None.
Protocol(s): All
TRKOBJ : Type of object associated with the Sentinel identifier to which the transfer is
attached. When available, the transfer identifier is automatically linked to
the event when the request is received. This enables end-to-end inter-
applicative tracking.
Maximum length 50 bytes.
Default: None.
Protocol(s): All
You cannot supply both the TRKCID and the TRKCIDX parameters. Choose a character or an
hexadecimal format.

If you enter the TRKOBJ and TRKCID (or TRKCIDX) parameters, you must also enter a Y or
S value for TRACKER parameter.
An example of the receipt of a request is provided in the REQTRK member of the CNTL
library.
Use TRACKER parameters according to the following rules:

- If the parameter is provided in the request message (or in the model), it is used.
- Otherwise, if the parameter is present in GENFILE, this value is used.
- Otherwise, if the parameter is present in GENSITE, this value is used.
- Otherwise, the value of PELPARMS is used.
I.4.2 SUPPLYING TRACKING ELEMENTS
The tracked elements created for each transfer and then written to the Mailbox record, are
available to the user in the end-of-transfer exits. They can be redirected to the operational JCL
via the PELSUBX or PELSJCLX macro.
The parameters are the following:
TRACKER = transfer tracking option: Y/S/N.

TRKCID = string (length 30 bytes) representing the CID of this transfer.
TRKOBJ = string (length 50 bytes), representing the name of the tracked object, in
this case: XFBTransfer.
I.4.3 TRACKING STOP AND START COMMANDS
If tracking is requested, it is automatically triggered on monitor startup.

It is possible to stop and restart the tracking process at any time. Use the following Inter.Pel
commands from the interface console.
These commands are general commands that apply to all monitor activities, transfers and log
messages.
STARTRK : Sentinel tracker startup for the entire cluster.

Parameter: [ALL|SUM]
ALL: startup of the entire tracking process.
SUM: startup of restricted tracking.
Type: 1, on the request server.
Trace: yes.
Associated program: PELMXITB.
STOPTRK : Stop Sentinel tracker for the entire cluster.

Parameters: None.
Type: 1, on the request server
Trace: yes.
Associated program: PELMXOTB.

I.4.4 USING THE LOGGER OF THE UNIVERSAL AGENT
In order to enable the interception of monitor startup messages, you are advised to start the
Sentinel Event Router before starting the Inter.Pel monitor. Otherwise, Inter.Pel will be able
to write messages into a logger file. You will then have to manage size of this file and specify
the action to take when this file is full.
See the Sentinel documentation for more details on how to configure and manage this logger
file.
I.4.5 OTHER OUTPUT FILES
The UA writes log messages to SYSOUT.
To trigger a trace of all UA activities, specify the trace option (TRKTRACE=) in the UA
configuration file. The trace file is dynamically allocated in SYSOUT.

PELV7.3 Installation and Implementation Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PELV7.3 Installation and Implementation Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

XFB. Inter.Pel V7.

Axway Software, 2003.

1. GENERAL PRESENTATION ........................................................................... 1-1

1.1 OVERVIEW .................................................................................................................................... 1-1

1.2 Inter.Pel ENVIRONMENT............................................................................................................ 1-2

1.3 DEFINITIONS ................................................................................................................................ 1-3

1.4 FILE NAME MANAGEMENT BY INTER.PEL ........................................................................ 1-4

1.5 DISK SPACE MANAGEMENT.................................................................................................... 1-5

1.6 MAILBOX....................................................................................................................................... 1-5

1.7 ACCESS SECURITY ..................................................................................................................... 1-6

1.8 SERVICES....................................................................................................................................... 1-6

1.9 GENERAL STRUCTURE.............................................................................................................. 1-8

1.10 DOCUMENTATION.................................................................................................................... 1-12

2. INSTALLATION ............................................................................................... 2-1

2.1 RESOURCES REQUIRED ............................................................................................................ 2-1

2.2 INSTALLATION PRINCIPLES ................................................................................................... 2-2

2.3 RESTORING THE FILES ............................................................................................................. 2-3

2.4 CUSTOMIZING THE CNTL AND SAMPLIB FILES ............................................................... 2-7

2.5 CREATING THE TABLES ........................................................................................................... 2-7

2.6 CREATING THE UNIT TABLE................................................................................................... 2-7

Installation and Implementation Guide Table of Contents iii

2.8 COMMUNICATION SVC........................................................................................................... 2-13

2.9 XCF DEFINITIONS ..................................................................................................................... 2-14

2.10 VTAM DEFINITIONS ................................................................................................................. 2-15

2.11 AUTOMATIC JCL EXECUTION.............................................................................................. 2-17

2.12 INTER.PEL EXECUTION .......................................................................................................... 2-30

2.13 INITIALIZATION TRANSACTIONS ....................................................................................... 2-34

2.14 MIGRATING FROM VERSION 7.1 .......................................................................................... 2-34

3. PARAMETER SETTING .................................................................................. 3-1

3.1 GENERAL PRINCIPLES .............................................................................................................. 3-1

3.2 CREATING THE ENVIRONMENT TABLE............................................................................ 3-23

Installation and Implementation Guide Table of Contents iv

3.3 CREATING THE ROUTING TABLE...................................................................................... 3-103

3.4 BROADCAST LIST TABLE ..................................................................................................... 3-109

3.5 MANAGING X.25 ACCESSES ................................................................................................. 3-112

3.6 MANAGING TCP/IP ACCESSES ............................................................................................ 3-118

3.7 MANAGING MODELS ............................................................................................................. 3-123

3.8 USER MESSAGES ..................................................................................................................... 3-173

Installation and Implementation Guide Table of Contents v

3.9 INTER-TABLE CORRELATION ............................................................................................ 3-179

3.10 UNIT TABLE .............................................................................................................................. 3-180

3.11 DEFINING Inter.Pel-CICS CONNECTIONS.......................................................................... 3-182

3.12 COUPLINGS............................................................................................................................... 3-206

APPENDIX A USING THE X25 NPSI PCNE FUNCTION ................................. A-1

A.2 MAJOR SWITCHED NODE TABLE ......................................................................................... A-2

A.3 MAJOR SWITCHED NODE DEFINITION EXAMPLE.......................................................... A-3

A.4 SEQUENCE OF OPERATIONS .................................................................................................. A-4

A.5 SUMMARY DIAGRAM ............................................................................................................... A-5

Installation and Implementation Guide Table of Contents vi

B.1 X25NPSI GENERATION...............................................................................................................B-1

B.2 MAJOR SWITCHED NODE.........................................................................................................B-1

APPENDIX C USING SMS................................................................................ C-1

C.1 SETTING INTER.PEL PARAMETERS ..................................................................................... C-1

C.2 CONSTRAINTS............................................................................................................................. C-1

APPENDIX D USING LU 6.2............................................................................. D-1

D.1 INTRODUCTION.......................................................................................................................... D-1

D.2 VTAM DEFINITIONS .................................................................................................................. D-3

D.3 INTER.PEL DEFINITIONS ......................................................................................................... D-7

D.4 INTER.PEL TRACES IN LU 6.2 MODE .................................................................................... D-9

APPENDIX E USING TCP/IP................................................................................ E-1

E.2 INTER. PEL PARAMETERS FOR TCP/IP ................................................................................E-2

E.3 INTERLINK/IBM TCP/IP SPECIFIC PARAMETERS AND REQUIREMENTS..................E-8

E.6 INITIALIZING THE IPTABLE..................................................................................................E-22

E.7 DISPLAYING AND MODIFYING IPTABLE ENTRIES .......................................................E-22