rvs Version Operator Manual

Transcription

1 rvs Version Operator Manual

2 Operator Manual The products listed in this manual are protected by copyright. rvs Version Operator Manual 2000 by gedas Pascalstraße Berlin This manual is protected by copyright. All rights reserved. No part of this book may be used or reproduced in any form or by any means including photocopies, microfilm or any other means or stored in a database or retrieval system without obtaining prior permission from gedas. Rights are also reserved as far as lectures, radio and television is concerned. We reserve the right to make changes to the content of this manual without giving prior notice. gedas is not liable for technical or printing errors or defects in this manual. Moreover, gedas shall not be liable for damage which is directly or indirectly caused by delivery, performance and use of this material. 2

3 Contents Contents I. Introduction Short Description of the System Target Group Structure of this Manual Representation means General Hints for Operators II. Windows NT Configuration of Windows NT Customizing Stationtable and Related Tables for Windows NT Customizing Stationtable ST Customizing ODETTE Parameter OP Customizing NeighbourNodes NK Customizing Routing Table RT Customizing SNA-LU6.2 Parameter LU Customizing TCP/IP Communikation TC Customizing X.25/ISDN Parameter Changing a Partner Station SNA LU6.2 receiption TCP/IP Receiption ISDN/X.25 Receiption User table modification Log file Administration Customizing environment variables License key modification Function Test rvs Monitor for Windows NT Start rvs Monitor Stop rvs Monitor Customizing the Monitor Parameters for Windows NT III. AS/ Configuration of AS/400 Systems Customizing Stationtable and Related Tables for AS/ Identification of rvs Nodes for AS/ StationTable ST for AS/ RoutingTable RT for AS/ Neighbour Node (NachbarKnoten) NK for AS/ ODETTE Parameters OP for AS/ LU 6.2 parameters LU for AS/ X.25 native Communications XP for AS/ TCP/IP parameters TC for AS/ Defining X.25 Communication Prerequisites Customising the Station Table Defining an X.25 Line Activating an X.25 receiver task Configuration Example X Defining ISDN Communication Requirements Defining a connection list and inserting new entries Definition of an ISDN network interface Definition of X.25 lines via ISDN Customising the Station Table Activating an ISDN receiver task Configuration Example for ISDN Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 3

4 Operator Manual 4.4 Defining LU6.2 Communication General overview Generating a line description Generating a Controller Generating an unit description Generating a mode description Adding an ICF entry Customising the Station Table Configuration Example SNA LU6.2 via X.25 to IBM Host Configuration Example SNA LU6.2 via Token Ring to AS/ Examples Configuration Worksheets Defining TCP/IP Communication Requirements Customising the Station Table Activating a TCP/IP receiver task Get a license for AS/ Application examples Routing Provision of files (mailbox mode) The STATISTICS Parameter rvs Monitor for AS/ Start rvs400 Monitor Stop rvs400 Monitor Monitor Initial File for AS/ IV. UNIX Configuration of UNIX Systems Customizing Stationtable and Related Tables for UNIX Identification of rvs Nodes StationTable ST RoutingTable RT Neighbour Node (NachbarKnoten) NK ODETTE Parameters OP LU 6.2 parameters LU (only AIX, HP-UX and SINIX) X.25 native Communications XP TCP/IP parameters TC Choosing Privileges for rvsx Running rvs high-privileged Running rvs low-privileged Defining the TCP/IP Connection rvsx Configuration for TCP/IP Problem Solving for TCP/IP Defining the ISDN Network for BRICK Router BRICK Router Installation rvsx Configuration for BRICK Router Problem Diagnosis for BRICK Router Defining the ISDN Network for netisdn Base Software (only AIX Systems) Adapter Installation for AIX rvsx Configuration for AIX Diagnosis for AIX Defining the ISDN Network for internal ISDN board (only SINIX Systems) Configuring TNS for SINIX Configuring rvsx (SINIX) rdstat.dat for ISDN communication Defining the X.25 Network for AIX Adapter Installation for AIX

5 Contents rvsx Configuration for AIX X.25 Problem Diagnosis for AIX X.25 Routing Information for AIX Defining the X.25 Network for SINIX rvsx Configuration for SINIX Tracing X.25 packet level for SINIX Defining the X.25 Network for HP-UX Configuration of HP-UX for X rvsx Configuration for HP-UX Defining the SNA Network for HP-UX Defining the SNA Network for AIX and SINIX Host Definition for AIX and SINIX SNA Server/6000 Definition for AIX SINIX TRANSIT Definition Specify System Environment Get a License for UNIX Defining your Error Handling rvs Monitor for UNIX Start rvs Monitor (rvsstart) Stop rvs Monitor (rvsstop) Stop MasterTransmitter Kill rvs Programms (rvskill) only for UNIX Use non default Database Set rvs Parameters at Start Time Monitor Initial File For UNIX Command Line Arguments Return Codes V. Operator Reference Operator Console and Commands Work with Individual rvs Commands List information about one command List Command Numbers Hold, Free or Delete an rvs command Suspend Traffic to Neighbor Activate Neighbor Work with Stationtable Entries Work With rvs Parameters Patterns Command Descriptions rvs Parameters rvs Parameter Values Savety, Resource Consumption and Performance Limit Number of Concurrent Senders Limit Number of Concurrent X.25 or ISDN Receivers TCP/IP Receiver SNA Transaction Program for Windows NT Optional Features Internal Parameters Database Maintenance for Windows NT Cleanup Backup Saving the stationtable Saving the user table and follow-on processing Saving the rvs Database Restore Restoring the stationtable Restoring the user table and the follow-on processing Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 5

6 Operator Manual Restoring the rvs Database New database Database Maintenance for UNIX Cleanup Backup Recovery Create new Database (rvsidb) Delete rvs Database (rvsdbdel) Dump rvs Database (rvsddb) Write rvs Database (rvswdb) Dump rvs User and Resident Receive Entries (rvsdru) Utilities List of all utilities Convert U or T File to pseudo F or V Format (rvsut2fv) Active Panel (rvsap) Recover Isam Index (rvsrii) rvs Information Entry (rvsie) Backup of the rvs data (rvsbackup) Restore of the rvs data (rvsrestore) rvs End-to-End Response (rvseerp) Send a Data set (rvssend) only for UNIX VI. Technical Overview Functional Elements Monitor Monitor Basic Characteristics Processing of a Send Order Handling Incoming Data MasterTransmitter Communication Modules LogWriter ActivePanel Operator Console Dialog Interface Batch and Call Interface Database Protocol Layers in rvs Communication Network Linedriver OFTP Communication Program LU 6.2 Basic Concepts Why LU 6.2 Communications? LU 6.2 Basic Functionality Mapped or Basic Conversation Security Dependent and Independent Lus Effects of LU 6.2 on rvs Design X.25 Native Communication Connection Establishment Effects of X.25 on rvs Design TCP/IP and rvs TCP/IP Application Interface TCP/IP Addressing Establishing a Connection with rvs Glossary Index

7 Introduction I. Introduction 1.1 Short Description of the System What rvs is The abbreviation rvs stands for the German word RechnerVerbundSystem. The rvs computer communication system is a well established base service for electronic data interchange, EDI. Task of the system is, to guarantee transmisssion of electronic data between heterogenious computer platforms using different network protocols. To do so, rvs realizes a universal network model which can be configured by you within each network node. It provides an efficient and reliable transport service for both standardized EDI message types and files of any format or content. You can get only data files which have been provided explicitly by rvs.this means that rvs does not provide an unauthorized access to remote data files. The system was originally developed by Volkswagen AG and has been used in the German and European automobile industries for a number of years. rvs uses the OFTP protocol. The Volkswagen AG has been developed an extansion to the standard OFTP: SNA LU6.2. rvs has become one of the most successful protagonists of EDI. This "portable" version of rvs has been developed in order to complement the classical rvs product line which is based on MVS and VSE mainframes for use on midrange, mini systems and personal computing. Though the design and make of this product line differs considerably from the mainframe versions, the functional spectrum is almost exactly the same as that of rvs MVS. This version of rvs is written in the language C and has been developed under the principles of modern design and the use of CASE-Tools. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 7

8 Operator Manual What rvs is not rvs is not an online system. It neither supports direct terminal-like access to other sites, nor does it provide a communication pipe from application to application on a data record level to the end user. You cannot directly execute transfers in your own application, you rather can place send orders in the rvs database which will be handled asynchronously. rvs is not a job scheduling system. rvs does not care about the contents of the data sets it is transporting. It only acts as a transparent transport medium and performs no semantical interpretation of the data it carries. rvs is not a EDI converter. But additional components for converting between specific message formats (e.g. VDA, ODETTE, EDIFACT) can be purchased via gedas deutschland GmbH. rvs is not a network control or monitoring tool. Supported Platforms The following versions of portable rvs are currently available: rvsx for SINIX using LU 6.2, X.25, ISDN and TCP/IP rvsx for AIX using LU 6.2, X.25, ISDN and TCP/IP rvsx for HP 9000 using LU 6.2, X.25, ISDN and TCP/IP rvsx for IRIX using ISDN and TCP/IP rvsx for Linux using ISDN and TCP/IP rvsx for SCO using ISDN and TCP/IP rvsx for Solaris using ISDN and TCP/IP rvs400 for IBM AS/400 systems using LU 6.2, X.25, ISDN and TCP/IP rvsnt for MS Windows NT using LU 6.2, X.25, ISDN and TCP/IP Basic Functional Characteristics The main function of rvs is the reliable transfer of files. rvs is suitable both for the transfer of large files and for the transfer of many small files. rvs supports many networks with many stations which are based on different platforms. Various data formats are supported thereby. 8

9 Introduction The key characteristics of portable rvs are: The Monitor, the central component of rvs, controls as a kind of local agent all work to be done. rvs works asynchronously, i.e. its processing is not under your direct control. You just places a send order in the rvs database by means of a menu controlled user interface or out of a batch file or program. The rvs processes the send orders as soon as possible. The advantage is, that you or your application program does not need to wait for completion of a file transfer. The connection to the communication partner is automatically established when necessary. The automatic submission of jobs after reception of a data set is supported by means of resident receive entries. Wildcarding of data set names, user IDs, and station IDs is supported. The file transfer is possible for the following record formats: U Unstructured, T Text file, F Fixed, V Variable. Extensive security and authorization checking is performed. rvs automatically repeats the transmission after an unsuccessful connection attempt or disruption of a connection. In the event of disruption rvs only transmits the parts of a file which have not yet been transmitted. Therefore it is suited particularly to transmit large quantities of data even under difficult conditions. The compression of data during transfer increases transmission line throughput. It is possible to create alternative routes (e.g for backup purposes). The user interface is a menu controlled interface. Besides a menue controlled interface a single command line interface is provided. That means that you can call rvs within batch or command files. A program call interface allows you to call rvs services out of a user application program. The ODETTE File Transfer Protocol, OFTP, is used. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 9

10 Operator Manual The X.25 native communication (interfacing directly to ISO-OSI protocol Level 3) is the communication protocol for `open' communication. rvs is designed to operate on the basis of Switched Virtual Circuits (SVCs). The ISDN communication is supported (via internal or external ISDN adapter). The SNA LU 6.2 communication (VW-modification of OFTP) is supported. This allows the use of the following physical SNA networks: X.25 SDLC Token-Ring The TCP/IP communication (According RFC 2204) is supported. rvs is designed to run parallel transmissions on parallel TCP/IP connections. A forward recovery of rvs database can be carried out from last database backup using the database LOG file. Message LOG files are provided for revision purposes. Tracing capabilities are provided on line I/O and/or OFTP level. rvs supports multiple languages in messages, operator (console) and user interfaces (presently English and German). The data conversion, if wanted, can be carried out. Text files are automatically converted to the code (EBCDIC or ASCII) used on the target partner system. The earliest date/time of a transmission can be defined for each file to be transferred. A serialization facility allows the transfer of files in a sequence which you can define. 10

11 Introduction rvs Network Architecture A rvs node (station) represents a 'peer' in a logical point-to-point connection. The connection is part of a logical network which consists of other rvs installations. rvs always requires the presence of communication partners 'talking' the same high-level File Transfer Protocol. Therefore the partner must be another rvs system or a compatible one. In a logical network of rvs nodes, the physical network can be quite inhomogeneous. That means that the kind of physical connection between two neigboring rvs nodes is of bilateral interest only. rvs thus supports data transfer through an inhomogeneous Station B Station C UNIX TCP/IP FTP Station D W95, W NT X.25 Station E rvsx Station F ISDN Station A rvswin SNA 3270 rvsmvs Station X TCP/IP rvsmvs Station G Station 1 rvsx Station 2 rvs400 Station Y Station 3 SNA LU6.0 rvs400 rvsnt rvsx Station I SNA LU6.2 SNA LU6.2 Station 4 rvsvse physical network. rvsx Station H Station 5 rvsx rvs2 Picture 1 A rvs Station Net Example with Different Platforms and Network Access Methods This picture shows a logical network of rvs stations. The nodes of this network are different computer platforms connected by different network access methods. Any number of stations can be connected in such a network. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 11

12 Operator Manual This example shows the following relationships between the partners: The rvsmvs station X is connected with a rvsx station H via LU6.2, but with a rvs400 station G via TCP/IP. Another rvsmvs station (station F) is also connected via TCP/IP. Other partners can be reached via SNA or X.25. rvs offers store and forward file transfer using gateway functionality, i.e. station H sends data to station G via Station X, even though there is no direct connection between the two stations. In doing so, rvs routes the file between different network protocols (to station X via SNA LU6.2 and to station G via TCP/IP) to its final destination. In the same way the station X could send data to the station Target Group This manual is intended as a reference for persons who are assigned to install and configure rvs running in the day-to-day business. It is intended to serve as general information for persons who want to understand the basic functionality and to get background knowledge of rvs. rvs is basically designed to run without operator control. However, there are always some duties left requiring hand-work. There is for example the very important task of maintaining the database. This requires regular cleanups and backups. The following skills are required to be able to use rvs : good knowledge of the current operating system knowledge of the communications technics in use SNA LU 6.2 PU 2.1 X.25 native communications and/or ISDN native communications TCP/IP understanding of the basic functions of rvs. knowledge of the current rvs configuration Before starting to work it is advisable to have read this book. 12

13 Introduction 1.3 Structure of this Manual rvs consists of the following manuals: Installation Manual The Installation Manual describes the installation of the rvs software on different platforms. The new installation procedure and the update installation procedure will be explained step by step. User Manual The User Manual describes how to transfer files to partners and vice versa. The three (basic) interface methods interactive, batch and API are described. Operator Manual The Operator Manual describes how you can work with rvs using the console. It contains tips how to maintain your data and a description of the utilities as well as how to configure rvs after the installation. Furthermore, this manual contains information on the technical background of rvs. The available manual is the Operator Manual. Messages und Return Codes Manual This manual describes all messages and error codes which will be displayed on the rvs Monitor and in the log file. The Installation Manual, the User Manual and the Operator Manual are available as printed and as electronic documents. The electronic document is available in Portable Document Format (PDF). The "Messages and Return Codes Manual" is only available as electronic document. We have planned to create tutorials for the operator and the user. These manuals will contain all important steps how to work with rvs. An explanation will be given step by step and in the correct order. That will help you to optimize your work with rvs. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 13

14 Operator Manual 1.4 Representation means This chapter contains the description of the indications which are used in this manual and the explanation of the expressions which are marked. Indications courier BOLD and IN CAPITAL LETTERS "quotation mark" bold commands, menu commands, file names, path names, programs, examples, scripts, qualifiers, data sets, fields, options, modes, window names, dialog boxes and statuses parameters, environment variables, variables links to other manuals, sections and chapters, literature important, names of operating systems, proper names, buttons, function keys Expressions rvsx is the synonym of rvs for UNIX systems. rvsnt is the synonym of rvs for Windows NT systems. rvs400 is the synonym of rvs for AS/400 systems. Directories As user directories are found on different locations for the different operating systems we use the variable $RVSPATH in this manual. Default values are: /home/rvs/ for AIX, Solaris, IRIX, Linux and SCO /users/rvs/ for HP-UX /defpath/rvs/ for SINIX c:\rvs for Windows NT Substitute the variable with your correct path. Generally, the file names on OS/400 systems are always written in capital letters. 14

15 Introduction 1.5 General Hints for Operators This chapter describes how you can avoid the cancel of rvs, how you can handle log files and database files. Avoid to Power Off Your System or Cancel rvs It is strongly recommended not to power off your system and/or to stop the subsystem QRVS (important for AS/400 systems) while any rvs tasks are active. Also, do not cancel any rvs task without need. Each rvs task potentially updates the rvs database. An uncontrolled shut down or cancel could collide or coincide with such a database update which could result in a logically inconsistent and thus destroyed database. Therefore, always make sure that rvs is completely down before shutting down your system. If system shut-downs or restarts are sheduled, especially if regular automatic boot procedures take place during night, rvs utility RVSSTOP should be used to initiate a programmed termination of rvs at an appropriate time and date. Handling LOG files It is the rvs administrator's or operator's responsibility to create regular backup copies of LOG files and keep them in a safe place for revision purposes. LOG files can get pretty large and, after a backup copy has been created, must be deleted if necessary. The handling of the database LOG file is described in chapter "12.2 Backup". Handling Database Files It is the rvs administrator's or operator's responsibility to create regular backup copies of the database and its LOG file and keep them in a safe place. The handling of the database is described in detail in chapter "Database Maintenance for Windows NT". Never try to modify a database file by hand - it will get damaged. The reason is, that database files contain control sequences that cannot be edited. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 15

16 Operator Manual Functions of the rvs Monitor The rvs400 Monitor is the central component of the file transfer via rvs400. The information, which tasks are to be executed by the Monitor and how, is stored in the rvs400 database. The Monitor executes the following tasks: Executing of operator commands Searching the database for send orders to be processed Activating transmissions Re-initialising of failed transmisions Creating state messages Ausgabe von Statusmeldungen Delivering incoming information to the final destination Starting additional processes after Send/Receive processes Generating of user notifications Writing statistic records The Monitor is controlled via an operator console task. Periodically the Monitor scans the database for processable commands. If the Monitor finds one or several processable commands, it converts them to internal rvs400 commands and assignes priorities to them. The further processing of each command depends on its priority. The most important rvs400 commands are: SE SK QS QE IE IZ OK EC RE JS send order entry send command send receipt received receipt information entry (about incoming information) informtion delivery (to the recipient) operator command end command (clean up) command for Resident Receive Entries (ResidenterEmpfangseintrag) command for Job Start after Send Attempt (JobStarteintrag) Processing a command may require several steps. Depending on the stages of processing they are assigned different states. 16

17 Introduction The possible states are: q f a i p e d h s queued (awaiting processing by rvs Monitor) forwardable (awaiting transmission) active (processing by rvs Monitor underway) in transit (processing by MasterTransmitter underway) Pending (final termination not reached) ended deleted (logically deleted from rvs database) held (by system or operator) suspended (all traffic to destination has been suspended, SK or QS) Handling Send Requests When a send order is compiled, a send entry (SE) is compiled in the database with the status queued. The rvs monitor analyses this entry, generates a send command (SK) - also with the status queued - and transforms the SE into the status pending. At the time to send (usually immediately) the SK is given the status forwardable and at the same time the MasterTransmitter, which coordinates the transmission, is activated. This starts a send process and the SK now has the status in transit. If the transmission was not successful, the monitor must arrange for a restart of SK and this is again - depending on the cause of the error - queued or forwardable. If the transmission was successful, the SK is transformed into the status pending and in this connection the SE remains in this status. As soon as acknowledgement in accordance with OFTP (End-to-End- Response) is received by the sender from the receiving partner station, SK and SE change to the status ended. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 17

18 Operator Manual Handling Receive Data The beginning of the reception of a file is noted in the database as an information entry (IE) with the status pending. The end of the reception is noted in the database by transforming the IE into the status queued. The files received are held in the buffer on a temporary basis to begin with. The monitor registers the IE and initiates the data transfer by creating an information assignment (IZ). The IE is then given the status pending. Processing the IZ consists of copying the temporary file received into the user data directory or starting a resident receive entry (RE) (if applicable). When this has been successfully performed, the IZ receives the status ended. Then an acknowledgement send entry (QS) is generated for the successful file transfer (OFTP: End-to-End- Response) and the IE is also transformed into the status ended. Processing the QS is effected similar to the processing of a SK. Once processing/assignment of the QS has been completed, it is given the status ended. 18

19 Configuration of Windows NT II. Windows NT In this part of the manual the configuration process under Windows NT systems as well as the rvs Monitor for Windos NT is described. After you have installed the rvsnt system, you must adapt rvsnt to your request. Which possibilities of the configuration are available and how you can execute these, is explained in the following chapters. 2 Configuration of Windows NT This section describes how to configure your Windows NT system. 2.1 Customizing Stationtable and Related Tables for Windows NT Before you can communicate with a partner station, you have to set up the partner station and your local station. The same also applies to your partner. In order to do so, open the Stations Table in the rvsnt Administrator using the View Stations menu command. The window Stationtable for administering the partner stations then opens. The table contains four sample stations after rvsnt has been installed: LOC is the local station. If you have selected your own station ID for your local station during user-defined installation of rvsnt, then the station ID which you have selected will appear here. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 19

20 Operator Manual If you use rvs version or higher you can rename the local SID. For further versions: ever delete the local station. If the name of the local station is to be changed, the rvs database must be deleted and set up again with the new name for the local station. In the standard installation further stations have been entered as examples of the various communications modes: RSL is a partner station for communication with SNA-LU6.2, RST is a partner station for communication with TCP/IP and RSX is a partner station for communication with X.25/ISDN. Use the examples in order to set up your stations. By double-clicking the station (or with the menu command Edit / Edit (or Add) you can cause the dialog window Properties of station to open and the tab ST Station is shown to you to begin with. You can display and edit the station properties by selecting the tabs ST-Station, OP-Odette Parameters, NK-Line Type, RT- Routing, LU-SNA LU6.2, XP-X.25/ISDN and TC-TCP/IP. 20

21 Configuration of Windows NT These abbreviations stand for: ST-Station OP-Odette parameters NK-Line Type RT-Routing The parameters that identify a station locally on your computer Parameters which rvsnt needs for the ODETTE transfer Connection type by which the station is reachable Parameters you need if you want to send files to an indirectly reachable station via your neighbour node. LU-SNA LU6.2 Details for the respective connection mode selected in the NK-Line Type tab XP-X.25/ISDN TC-TCP/IP Use the key combination CTRL+TAB or the mouse to click on the other tabs and enter the remaining parameters of the new stations. For more information refer to the following chapter "6.1.2 StationTable ST". Confirm the entries by pressing OK. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 21

22 Operator Manual Customizing Stationtable ST The ST tab uses three parameters to identify a station: Parameter Station ID Meaning tab ST-Station Partner station identity marker consisting of up to 16 characters. Station name Station name (optional). Enter a descriptive name for the station so that the station will be easily recognized by the user. Phone (Optional) telephone number for the contact person at the partner station. Database parameter SID STATNAME PHONE 22

23 Configuration of Windows NT NOTE: After confirmation with OK you are no longer in a position to change the station ID. In order to assign a new station ID you have to set up a new station. Station name and telephone number for the contact person are optional. Do not enter the telephone connection for communication here but - depending on connection mode - in one of the tabs LU, TC or XP Customizing ODETTE Parameter OP The OP-Odette Parameters tab contains information which is required by rvsnt for ODETTE File Transfer. If you access the partner station via a neighbouring station (connection type = Routing) you do not have to enter the parameters for passwords. This information has already been entered at the neighbouring station. In this case, rvsnt ignores the existing entries during the communication process. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 23

24 Operator Manual Parameter Odette Id Password: Send Password: Receive Meaning tab OP-Odette Parameters In contrast to the station ID, which only has to be unique on your computer, the ODETTE ID is a worldwide, unequivocal identification of the partner or your own station, if ODETTE File Transfer Protocol is used. The ODETTE ID consists of 25 characters including the letter "O", the 18-character organization ID and the 6- character computer address within the respective organization. The computer address may be freely determined by the organization and must be unique. Send password: rvsnt sends this password to the partner station as access authorization. Receive password: rvsnt permits the partner station to have access with this password. Database parameter ODETTEID PSWTO PSWFROM The fields for the passwords have been masked out on the local station, since no access authorization is required for communication with yourself. For a partner station the passwords for sending and/or receiving must have been agreed upon with the partner. The same passwords must be entered, interchanged, for receive and/or send. Non-compliance results in an error message and prevents communication (see following illustration). Station 1 Station 2. Password: Send: Receive: Password: Send: Receive: 24

25 Configuration of Windows NT NOTE: You may submit an application for your own ODETTE organization code to your national ODETTE organization. In Germany this is the Association of the German Automotive Industry (VDA). Telephone: / Fax: / rvsnt carries out transmission using standard values for ODETTE File Transfer Protocol (OFTP). If you would like to view the standard values or want to change them, click the button Advanced... The Odette-Parameter (Advanced) window will open with advanced configuration options: Allowed characters for file names: Parameter Exchange Buffer Size Meaning tab OP-Odette Parameters (Advanced) Maximum transmission buffer size Standard: 0, i.e. OEXBUF from parameter table applies. Database parameter OEXBUF Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 25

26 Operator Manual Exchange Buffer Credit Code Translation Input Code Code Translation Output code Allowed characters Maximum number of blocks sent without acknowledgement expected. Standard: 0, i.e. OCREVAL from parameter table applies. Input encoding of the file which is to be sent, prior to conversion for the partner station. Values: ASCII: The files which are to be sent are in ASCII format. EBCDIC: The files which are to be sent are in EBCDIC format. Standard: ASCII Target encoding of the files for send transmission. ASCII: During transmission rvsnt converts the files which are to be sent from input code format into ASCII format. EBCDIC: During transmission rvsnt converts the files which are to be sent from input code format into EBCDIC format. Standard:ASCII Stipulates which characters are permitted for ODETTE-FTP: ALL: no limitations OFTPUNIX: all capital letters, digits and special characters ".-" OCREVAL CODEIN CODEOUT VDSNCHAR 26

27 Configuration of Windows NT Transmit Blocks: Receive Transmit Blocks: Send UNIX: all letters and figures and the special characters "#_-+." ODETTE: all capital letters, figures and special characters "()-./&" and blanks CHECK_RE: as with ALL and in addition a RE must be included Number of blocks received between two restarting positions for error correction. ) Standard: 0, i.e. RECVBLOCKS from parameter table applies. Number of blocks sent between two restarting positions for error correction. ) Standard: 0, i.e. SENDBLOCKS from parameter table applies. RECVBLOCKS SENDBLOCKS ) Tip: The greater the number, the more improbable the data transmission will be interrupted for entry of the restarting positions, but the greater will be the quantity of data to be transmitted again in the event of error. Select large values for reliable data lines in order to use the line quality for greater transmission speeds. Select small values for poor line quality in order to minimize the time required for repeated data transmission. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 27

28 Operator Manual Parameter Meaning tab OP-Odette Parameters (Advanced) EERP IN Send transmission (EERP = "End-to-End-Response") acknowledgement; Values: NEVER: Partner does not send EERP, file dispatch ends with successful transmission. Do not wait for acknowledgement. NORMAL: Wait for acknowledgement by partner after successful file transmission. File dispatch ends with receipt of EERP. Standard: NORMAL Database parameter EERP_IN 28

29 Configuration of Windows NT EERP OUT Receive transmission (EERP) acknowledgement; Values: NEVER: Partner does not expect EERP. File reception ends with successful transmission. Do not acknowledge reception. IMMEDIATE: Prepare acknowledgement after successful file reception. Establish connection if there is no connection to the partner and send EERP to the partner. NORMAL: Prepare acknowledgement after successful reception of a file; send EERP only if a connection to the partner still exists, otherwise at next connection. Standard: IMMEDIATE EERP_OUT Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 29

30 Operator Manual Customizing NeighbourNodes NK The NK-Line Type tab contains information about the path via which the partner station is to be reached. For the local station it is possible to specify additional parameters. Parameter File Transfer Protocol Meaning tab NK-Line Type Transmission protocol for data transmission; ODETTE FTP is the only protocol at present. Database parameter FTP 30

31 Configuration of Windows NT Connection Type The connection type with which the station is to be reached; Values: LU6.2: he partner station is reached via SNA-LU6.2 line. Enter the connection parameters in tab LU. TCP/IP: The partner station is reached via a network with the TCP/IP protocol. Enter the connection parameters in tab TC. X.25/ISDN: The partner station is reached via an X.25 or ISDN line. Enter the connection parameters in tab XP. Routing: The partner station uses a different partner station as a routing station. Enter the routing station ID in tab RT-Routing. The connection type and parameter of the routing station are then important for the connection itself. Further information is contained in the chapter "6.1.3 RoutingTable RT". Standard: no default. PROTOCOL Values: L T X R = LU6.2 = TCP/IP = X.25/ISDN = Routing Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 31

32 Operator Manual Active Connection Setup Selftest via Receiver Delay Parallel Sessions Priority Specifies the send behaviour for a pending send order; Values: : Sender should automatically start as soon as a file is ready for dispatch. : Pending send orders do not trigger a send action. Standard: May only be selected at the local station: Line by which transmission is to be made if the self-test is performed when your own station is activated May only be selected at the local station: Receivers which have been configured and/or are still to be configured Time (in seconds) to wait after receiving a file before a "Change Direction" (CD) is initiated Maximum number of active simultaneous connections via this line Standard: "-1" - unlimited The priority number is planned for rvsnt updates. It is reserved for future use. AUTODIAL Values: Y = N = PROTOCOL No parameter CDWAIT PSESSIONS PRIORITY 32

33 Configuration of Windows NT Establishment of an active connection It is occasionally necessary for files to be made only available and not to be sent immediately. On the contrary, the partner station is to establish the connection and fetch the available files as and when required. In this case, rvs functions like a mailbox that is emptied as and when needed. The partner bears the costs for the connection. Active connection setup must be switched off for this case Customizing Routing Table RT If you have selected the Routing connection type on the NK- Line Type tab (your partner station is not a direct neighbour node of yours), you can edit the routing table. The routing table contain the neighbour station information by means of which the station selected (= target station) is to be reached. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 33

34 Operator Manual Parameter Meaning tab RT-Routing Database parameter Neighbour node Priority Station ID of partner station (= neighbour station) which knows the path to the target station. The station ID has to be in the stationtable. Priority number of neighbour station. It determines the data transmission route. The integer value is between 1 and 100. The neighbour station with the lowest value is used. The priority at the time when the send command is prepared is decisive. SIDNEIGHB PRIORITY The forwarding of files throughout several OFTP systems is referred to as "routing". If you would like to send a file via several systems, then the send order only has to be directed to the recipient. rvsnt then sends the file to the next OFTP system, the neighbour node which, in turn, then forwards the file onward. Information on the intermediate station connections is contained in the databases of the respective stations. When the file has arrived at the end system, it sends an acknowledgement (EERP="End-to-End-Response") back to the original sender. The send order is only completed as soon as the sender has received this acknowledgement. 34

35 Configuration of Windows NT Data flow with and/or without routing is depicted in the following illustrations: Without routing: File Station 1 Station 2 EERP With routing: File Station 1 Station 2 File Station 3 EERP EERP You have to define 2 stations in the stationtable for routing: the neighbour station (neighbour node), through which the end recipient is reached and the target station for the end recipient. Select Routing as the connection type on the NK-Line Type tab for this station and on the RT-Routing tab select the station ID for the neighbour station. You may define the neighbour station itself like any normal station with connection type LU6.2, TCP/IP or X.25/ISDN. For example: Setting up of a recipient station is shown in the following screenshots. The destination MAR is reached with routing via RST. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 35

36 Operator Manual Station name ODETTE ID of destination 36

37 Configuration of Windows NT Connection type Routing station Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 37

38 Operator Manual Customizing SNA-LU6.2 Parameter LU If you have selected line protocol LU6.2 on the NK-Line Type tab, you can edit the parameters for the SNA-LU6.2 connection on the LU-SNA LU6.2 tab. Parameter LU Name TP Name Meaning tab LU-SNA LU6.2 LU name for the partner station. Under Windows NT it is the LU name, which you have defined during configuration of the SNA server. Name of the transaction program (TP) that is started at the partner station. This is the RVSRCV program on the local station. Enter RVSOFTP for an rvsmvs host, and RVSRCV for rvs2, rvsx and rvs400. Database parameter LUNAME TPNAME 38

39 Configuration of Windows NT Security Determines whether the partner station expects the user ID and a password; Values: : Partner station expects user ID and password. : Partner station does not expect user ID and password. SECURITY Values: 0 = 1 = User Password Network ID Mode Standard: User ID which the USERID transaction program uses at the partner station. Standard: Password which is required PASSWORD to start the TP at the partner station. Standard: Unique identification within NETID SNA network (SNA network ID). Name for the SNA session mode which you have defined during configuration of the SNA server. Some implementations of LU6.2 require names having at least 8 characters. Thus, the mode should be at least 8 characters long. Standard: one blank space; value required MODE Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 39

40 Operator Manual Synchronization Conversation type APPC synchronization level; values: NONE: Partner station does not expect confirmation CONFIRM: Partner station expects confirmation Standard: NONE APPC conversation type; values: BASIC: Basic conversation (not supported at present). MAPPED: Mapped conversation. Standard: MAPPED SYNCLEVEL TYPE Customizing TCP/IP Communikation TC If you have selected line protocol TCP/IP on the NK-Line Type tab, you can edit the line parameters for the network connection on the TC -TCP/IP tab with TCP/IP protocol. 40

41 Configuration of Windows NT Local Station rvsnt supports multiple TCP/IP reception under various Internet addresses at the same time. When you edit the TC parameters for your local station (LOC), the TC-TCP/IP tab will also display the push buttons Add and Remove, with which you may either add other data records to the TC parameters or delete the currently displayed record. If you add a new record, then rvsnt will automatically assign a number for the receiving channel. NOTE: If the configured recipient is to be automatically active after the rvs Monitor has been started and is to wait for incoming calls, the parameter TCPIPRCV must be set. For further details, read the chapter entitled "rvs Parameters". Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 41

42 Operator Manual Partner Station The TCP/IP address has to be unique for a send transmission to a partner station. Thus you may only indicate one Internet address. The Recipient number is "0" and may not be changed. Parameter Number IP address Port Maximum sessions Meaning tab TC-TCP/IP May only be selected at the local station: Number for differentiating the various receiving channels through which the local station can be reached. Each number has one set of TC parameters. Standard: 0 Internet addresses have the form " " If you have not specified a value for the local station, you permit automatic definition of the Internet address. If your own station has only one Internet address, this field should be left empty. Standard: " " Port address Standard: 3305 May only be selected at the local station: Maximum number of simultaneously running receiving processes on this channel Standard: 1 Database parameter N INADDR PORT MAX_IN 42

43 Configuration of Windows NT Customizing X.25/ISDN Parameter If you have selected line protocol X.25/ISDN on the NK-Line Type tab, you can edit the parameters for X.25 / ISDN connection on the XP-X25/ISDN tab. You may be ready-to-receive for a partner station via several ISDN numbers or X.25 address at the same time. To begin with you must stipulate the parameters with which the connection to ISDN and/or the X.25 card is made. This information is passed on by the parameter LINK. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 43

44 Operator Manual Local Station rvsnt supports multiple X.25/ISDN reception through various receiving channels (call numbers) at the same time. When you edit the XP parameters for your local station (LOC), the tab will also display the push buttons Add and Remove, with which you may either add other data records to the XP parameters or delete the currently displayed record. If you add a new record, then rvsnt will automatically assign a number for the recipient. NOTE: If the configured recipient is to be automatically active after the rvs Monitor has been started and should wait for incoming calls, the parameter MAXX25RCV must be set. For further details, refer to the chapter entitled "ISDN/X.25 Receiption". 44

45 Configuration of Windows NT Partner Stations The call number has to be unique for a send transmission to a partner station. Thus you may only indicate one set of parameters. Parameter Number Card type Port Card number ISDN standard Meaning tab XP-X25 May only be selected at the local station: Number for differentiating the various recipients through which the local station can be reached. Each number has one set of XP parameters. Standard: 0 Specifies which hardware is to be used for the connection. Influences the parameter LINK. May only be selected if the card type is an X.25 card: Specifies the X.25 port. Influences the parameter LINK. Standard: 1 Only applies for X.25 Teccom - and ISDN cards: Specifies the number of the card in the PC. Influences the parameter LINK. Standard: 0 May only be selected for ISDN cards: Specifies which ISDN standard is used. 1TR6 German national standard E-DSS1 EURO-ISDN Standard: E-DSS1 Database parameter N ISDN_PROT Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 45

46 Operator Manual Link Link name; determines the type of connection within your computer. Is determined by the port, card type and card number values and cannot be directly changed. The values have different forms for ISDN and X.25 connections. For ISDN connection: CAPI2mn for ISDN cards Values for m and n: m: A = no Diehl/Eicon card 0 = Diehl/Eicon card n: Number of the ISDN/X.25 card installed in the computer, beginning with "0" Example: CAPI200 = "Diehl/Eicon card" number "0" For X.25 connection: EICONn for X.25-Eicon cards n: Port number of the configured X.25 port, beginning with "1" Example: EICON1 NETX25mn for TECCOM cards Values for m and n: m: Number of the X.25 card installed in the computer, beginning with "0" n: Port number of the configured X.25 port, beginning with "0" Example: NETX2500 = card no. "0" with port no "0" Standard: CAPI200 46

47 Configuration of Windows NT Further Parameters Not all parameters are shown on the tab. Click the button Next >>. The other parameters are now shown on the tab. Change the parameters accordingly and Click << Back if you want to change the parameters for LINK or the ISDN standard again. Parameters: Parameter Meaning tab XP Database parameter X.25 Address 15-digit X.25 DTE address of the partner station. Specification is optional for an ISDN connection, It is however advisable for an ISDN connection to enter the ISDN number here, as many partners expect an X.25 address. XADDRESS Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 47

48 Operator Manual ISDN number / (End Selection Number) TEI TimeOut Rcv Timeout Parallel sessions X.25 UserData X.25 Facilities ISDN Facilities ISDN UserData dependend Recv. An ISDN number under which the partner station may be reached. Not specified for an X.25 connection. For the ISDN standard 1TR6 the single-digit end selection number is (ESN) allocated for the local station. Standard: " " Only required for X.31: Terminal End Identification. Standard: 0 no TEI is allocated Cancellation time in seconds, after which the communication program aborts the connection if the partner station or CAPI does not reply. Standard: 30 Only valid for the local station: Cancellation time in seconds, after which the receiver interrupts the waiting for incoming calls and reconnects to the card driver. Maximum number of parallel active connections. The following applies for reception: As soon as a call has been accepted, the master transmitter starts a new receiver until the maximum number is reached. User data for an X.25 transmission; see the information of the X.25 service in use. Special information or facilities for an X.25 transmission; see the information of the X.25 service in use. Special information or facilities of the ISDN transmission User data for an ISDN transmission Only applies to partner station entries: Specifies from which ISDNNO ISDN_TEI TIMEOUT RCVTIMEOUT SESSIONS USERDATA FACILITIES ISDN_FAC ISDN_USRDT RCV_N 48

49 Configuration of Windows NT Dbit configured receiver the parameters for your own station (e.g. own ISDN number or X.25 address) are taken. Specifies whether every X.25 data packet is to be confirmed. Values: Yes, No. Standard: No, do not confirm every data packet DBIT Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 49

50 Operator Manual Changing a Partner Station If you want to change an existing partner station: In order to do so, open the Stations Table in the rvsnt Administrator using the View Stations menu command. Select the station to be changed in the window Stationtable. Execute the menu command Edit Edit. The dialog window Properties of station will open. You may now edit all the station parameters with the exception of the station ID. For further information read the chapter entitled "Customizing Stationtable ST". Confirm the entries by pressing OK. NOTE: In order to assign a new station ID you have to set up a new station. Set status You may activate, stop or set a station working. This is how to change the status of a partner station: Select the station to be changed in the window Stationtable. Activate In order to activate the station execute the menu command Edit Activate. NOTE: The station must already be Enabled before you can activate the station. rvsnt establishes the connection to the partner station and transmits the currently pending files. Activating a station means establishing an OFTP connection to this station. As soon as the connection has been established, each side has the opportunity to send any files that may possibly be available. If no file is ready to be sent, the connection is closed. 50

51 Configuration of Windows NT Set working In order to set the station working execute the menu command Edit Release. rvsnt is now ready for communication with the partner station. The status is Enabled. This is the standard setting for a station. A connection is established to this station as soon as data is available to be sent to this station. Stop working In order to stop the station working execute the menu command Edit Stop. rvsnt performs no send orders to the partner station but keeps them in the queue until you set the station working again. The status is Disabled. Save When you set up or change a station, save the changed parameters by pressing OK. When Windows NT is restarted, rvsnt continues to work with these parameters. However, if you delete the rvsnt database or reinstall rvsnt, you also delete the newly set up stations. Subsequent initializing of the database only provides the specified standard configuration of the stationtable. In order to avoid losing your entries, you may save the stationtable in a separate file and restore it later. For further information please see the chapter entitled "Database Maintenance for Windows NT". This section describes how the network configuration and other basic configuration issues can be defined as well as which privileges you can choose for rvs. The rvsnt administrator is used for configuring, administering and operating rvsnt. In order to carry out these activities the rvsnt Administrator is equipped with several detail windows. The configuration assumes administrator user rights at the system level and in the rvsnt environment. Start the program rvsnt Administrator by invocation in the rvs file or by means of Start Programs rvs rvs Administrator. The rvsnt Administrator then opens with the Monitor Log window which displays the current rvs Monitor activities. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 51

52 Operator Manual 2.2 SNA LU6.2 receiption When using SNA LU6.2 communications technology with rvsnt the calling station initiates a communications program at the receiving station. In order for the rvs communications program to start automatically when a partner station connects to your computer, the SNA LU6.2 has to recognize the communications program as a transaction program (TP). Communications program registration By using the RVSTPSET.EXE program you can enter all of the values required into the Windows NT registration database. To do so follow these steps: Select the Windows NT menu command Start Execute. Enter c:\rvs\system\rvstpset or use Search to find the file in the rvs system directory. Confirm the entry by pressing the button OK. The TP Setup dialog box will open. In the Command line field you will see the start command for the communications program which is to operate as a transaction program. In the Local LU Alias field enter the local LU name which you defined during configuration of the SNA server. Confirm the entry by pressing the button OK. 52

53 Configuration of Windows NT The RVSTPSET.EXE program then registers the communications program in the Windows NT registration database. Restart Windows NT in order for the new entries to take effect. Activate transaction mode In order to have the program start as a transaction program you have to carry out the following steps: Execute the View Parameters menu command in the rvsnt Administrator. The rvsnt - Parameter dialog window for editing the parameters then opens. In order for the transaction to start automatically you have to set the value of the rvs parameter SNARCV to 1: Double click SNARCV to select the parameter in the parameter list. Enter the desired value 1 into the input field. Confirm your entry with Apply. Use Close to exit the parameter list. Activate the parameter by stopping and starting the rvs Monitor. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 53

54 Operator Manual 2.3 TCP/IP Receiption If you want to be ready-to-receive via TCP/IP, rvsnt must start a TCP/IP receiver that waits for incoming calls. This is how you set the rvsnt to receive calls automatically via TCP/IP: Execute the View Parameters menu command in the rvsnt Administrator. The rvsnt - Parameter dialog window for editing the parameters then opens. In order for the TCP/IP receiver to start automatically start when the rvs Monitor starts, you have to set the value of the rvs parameter TCPIPRCV to 1: Double click TCPIPRCV to select the parameter in the parameter list. Enter the desired value 1 into the input field. Confirm your entry with Apply. Use Close to exit the parameter list. Activate the parameter by stopping and starting the Monitor. A message of the type I: <TCPIP_READY> : TCP/IP Receiver ready to accept incoming calls Port:3305 indicates your readiness to accept calls. 54

55 Configuration of Windows NT 2.4 ISDN/X.25 Receiption If you want to be ready-to-receive via X.25/ISDN, rvsnt must start a receiver that waits for incoming calls on the X.25/ISDN line. This is how you set the rvsnt to receive calls automatically via X.25/ISDN: Execute the View Parameters menu command in the rvsnt Administrator. The rvsnt - Parameter dialog window for editing the parameters then opens. In order for X.25/ISDN reception to start automatically when the Monitor starts, you have to set the value of the rvs parameter MAXX25RCV to 1: Double click MAXX25RCV to select the parameter in the parameter list. Enter the desired value 1 into the input field. Confirm your entry with Apply. Use Close to exit the parameter list. Activate the parameter by stopping and starting the Monitor. A message of the type I: <ISDN_READY> : ISDN Receiver ready to accept incoming calls No = indicates your readiness to accept incoming calls. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 55

56 Operator Manual 2.5 User table modification Only those users may work with rvsnt who are registered in the rvsnt database. In order to display or modify user data: Open the User Table in the rvsnt Administrator by using the View User menu command. The user table contains at least the table entry for your own data. Sort You can sort the table according to any column by using the mouse to click the column header. New user If you would like to set up a new user: Execute the menu command Edit Add. The User dialog window then opens and displays the User Table parameters. 56

57 Configuration of Windows NT Enter the user identification. Enter the user name. Select the language for screen dialog. Use the mouse to click on the user access authorization. Confirm the entries by pressing OK. NOTE: A basic user may use the program rvsnt to send and receive files. A user with administrator rights may in addition to this use the program rvsnt Administrator to configure the rvs system. An Operator has the same rights as an User. This type of user is reserved for future use. User Modification If you would like to modify an existing user: Select the user to be modified in the User window. Execute the menu command Edit Edit. The User dialog box will open. You can now edit all of the user data parameters. You can select German or English in the language field. rvsnt will then display all the menus and messages in the selected language. NOTE: If you want to modify your own user data then the entries will only take effect after restarting the rvsnt Administrator. Confirm the entries by pressing OK. Save If you set up or modify a user, use OK in order to save the modified parameters. If you delete the rvsnt database or reinstall rvsnt you will also delete all users. Subsequent initializing of the database only retains the administrator who has set up rvsnt. In order to avoid losing your entries you can save the users and the job start entries or even the entire rvs database and restore them later. If you choose to do so you can find more information in the chapter "Database Maintenance for Windows NT". Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 57

58 Operator Manual 2.6 Log file Administration Several log files are written during rvsnt operation. Their size and number can be controlled by means of rvs Monitor parameters. The Monitor Log file rlco.log Monitor Log shows the file c:\rvs\temp\rlco.log. It is regenerated with every new start of the rvs Monitor. Its maximum size is restricted by means of the rvs Monitor parameter RLCOMAXSIZE. Only those message classes specified in the rvs Monitor parameter CNSMSGS are written to this file. The permanent Monitor Log file rlog.log All rvs log messages - regardless of parameter CNSMSGS - are written to the file c:\rvs\db\rlog.log. Their existence is not restricted by a new start of the rvs Monitor. Their maximum size is restricted by the parameter RLOGMAXSIZE. When the file reaches this size, it is renamed by replacing the file extension by an active counter. Then a new file c:\rvs\db\rlog.log is generated and updated. The maximum number of generations can be restricted by the monitor parameter NUMRLOGS. The statistics file rlstat.log Statistical information is written to the file c:\rvs\db\rlstat.log. Its contents can be shown by means of View Statistics. Its maximum size is restricted by the parameter RLSTATMAXSI. When this size is reached, the file is renamed by assigning an active counter as a file extension and creating a new file c:\rvs\db\rlstat.log. The maximum number of generation files created in this way can be restricted by the parameter NUMRLSTATS. 58

59 Configuration of Windows NT 2.7 Customizing environment variables You can adapt the rvs environment to meet your requirements, e.g. modification of the directory in which the Monitor stores the received files. Carry out the following steps if you would like to modify the rvs system environment: Execute the menu command Edit Environment. The rvsnt - Environment dialog window then opens and displays the current environment settings: Confirm your changes / entries by pressing OK. NOTE: Any changes will only take effect after the rvs Monitor is restarted. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 59

60 Operator Manual Meaning of the environment variables Designation PATH SYSTEM Meaning of the environment variable Main directory of rvsnt and location of environment file rvsenv.dat System directory rvsnt with allprograms Help files, batch files and libraries Standard value c:\rvs c:\rvs\system DB rvs database directory rvsnt c:\rvs\db USRDAT TEMP INIT SAMPLES SERVER PORT ARCDIR AP_DISPL AY_INTER VAL Directory for user files received Temporary directory for the log book Directory for the initialization files, e.g. rdmini.dat for the monitor parameters Directory for files for the programming interface with examples Internet address of the server for messages of the line status Port number of the server for messages of the line status Directory for backup files Interval in milliseconds, in which the display for active lines is updated c:\rvs\usrdat c:\rvs\temp c:\rvs\init c:\rvs\samples IP address of the local PC 2956 c:\rvs\arcdir

61 Configuration of Windows NT DBLOG Disabled Language Write entries to the rvs database: Yes/No If you activate this check box rvs will write all database operations to the c:\rvs\db\rldb.log file and you are able to restore all the entries made since the last database backup. CAUTION: This will influence the performance of rvs extremely Disable access to the rvs database: Yes/No. You can use this control box to block access to the rvs database. Example: SNA processes should not modify the data bank during a backup. Language for message displays No No German 2.8 License key modification After initial installation rvsnt can be operated for test purposes without a license for a limited period of time. If you are satisfied with rvsnt and would like to continue working with it contact your sales representative or rvs Support (Tel.: 030 / ; FAX: 030 / , rvs-service@gedas.de). There you may obtain the desired license. Update license key Start the Get Machine ID program in the rvs file. The program now displays a three- or four- character machine identification number on the screen. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 61

62 Operator Manual Inform your sales partner of the machine identification number and he will send you a license key by fax or - preferably - by e- mail. The license key is used to modify the RDKEY.DAT file in the c:\rvs\init directory. Make a backup copy of the c:\rvs\init\rdkey.dat in order to be able to restore the original file status. In case you receive the license key by fax: Open the c:\rvs\init\rdkey.dat file using an ASCII text editor (e.g. MS DOS edit command). Edit the file precisely in accordance with the license key which you received from your sales representative to match your machine identification number. Note: The character entries have to be complete and absolutely identical with the license key model. Save the file and close the text editor. If you have received the license key by Save it as RDKEY.DAT file in the init directory. The license key has now been adapted. 2.9 Function Test The function test is used to make sure that rvsnt accepts and processes orders without error. To this end you should send a file to yourself from your workstation environment. To begin with you do not need a functioning network connection in this respect because when sending a file to yourself the rvs Monitor copies the individual data records internally. You can execute a line test by activating the local station. Sending a file to yourself If you want to test the function of rvsnt, execute these steps: Start the rvsnt Administrator program in the rvs file. Start the rvs Monitor if it has not already been started. Start the rvsnt program in the rvs file. The rvsnt window then opens and displays the list of files which have not yet been sent. 62

63 Configuration of Windows NT Create a new send entry with New Send Entry. The Choose file to be sent dialog box will open. Select any file and confirm your selection with Open. Example: c:\rvs\system\readme.txt The New Send Entry dialog window then opens and displays the file name selected in the File field. Enter the station code for your station in the Station ID field. or: Use Select... to open the Select Station window and select the station code. Example: LOC LOC is the standard setting. If you want to send the file under a different name, then enter the new file name into the New File Name field. Confirm the entries by pressing OK. The send entry for transmission of the file is thus entered into the rvs Database. The order to send the readme.txt file to your station has been made. rvsnt displays the order in the list of files which have not yet been sent. Go to the rvsnt Administrator. The Monitor Log window displays the rvs Monitor activities. The rvs Monitor reads the send order and executes it: Through the station code LOC the rvs Monitor recognizes its own station as the target and copies the file into the c:\rvs\usrdat directory. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 63

64 Operator Manual Check the output in Monitor Log for error messages. In order to eliminate any errors see manual "Messages and Codes". NOTE: Error messages begin with E: and are written in red. Activating the local station If you want to test the function of the line components, execute these steps: To ensure the function of the network line follow the instructions in the "Installation Manual" and in the below chapters of this manual. Open the stationtable with the menu command View Stations. The Stationtable window to administer the partner stations opens. Select the local station. Execute the menu command Edit Activate. The rvs Monitor reads the operator command and executes it. The window Monitor Log shows the activities of the rvs Monitor. The message O:<CONNECT > Sender: Connection established with station 'LOC' with credit=10, Odette buffer=2048. is shown. Check the output in Monitor Log for error messages. Eliminate any errors that occur in accordance with the advices in the "Messages and Codes" manual. NOTE: With the menu command Edit Activate you can also test the connection with other stations. 64

65 rvs Monitor for Windows NT 3 rvs Monitor for Windows NT This section describes how to start and stop the rvs Monitor as well as how to customize the Monitor Parameter for Windows NT. Usually the rvs Monitor works as a system service. In order to install the rvs Monitor as a system service, it is necessary that you belong to the Windows NT Administrator group. Services are managed about the dialog box Services within the Control Panel folder. Use this dialog box to start, stop, pause or continue the rvs Monitor service. 3.1 Start rvs Monitor You can start the rvs Monitor at the level of the operating system or from the rvsnt Administrator. This is the tool for operation of rvsnt. Operation of rvsnt requires administrator user rights at the system level and in the rvsnt environment. At first the status of the rvs Monitor service is stopped (represented by a blank entry in the status column). To start the service activate the row with the entry rvs Monitor and click at the Start button. The startup type for this service is Manual that means that the service can be started by the user. If you want to start rvs Monitor every time the system starts, you can set the startup type to Automatic by clicking the Startup... button and then changing the startup type to Automatic. Carry out the following steps if you want to start the rvs Monitor at the system level: Execute the Windows NT menu command Start Settings Control Panel. Start the Services program. Note: The term Service means a program that can be started from the operating system and works in the background. Search the list of services for rvs Monitor and select the service by clicking the appropriate line. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 65

66 Operator Manual Press the Start button. Windows NT will now try to start the service. If the attempt is successful the rvs Monitor status will change to started. The entry is Carry out the following steps if you want to start the rvs Monitor from within the rvsnt program environment while it is in operation: Start the rvsnt Administrator program in the rvs file. Execute the menu command Monitor Start. The rvs Monitor then starts. The rvs Monitor has been started if the stop symbol is active on the tool bar. 66

67 rvs Monitor for Windows NT 3.2 Stop rvs Monitor You can stop the rvs Monitor at the level of the operating system or from the rvsnt Administrator. This is the tool for operation of rvsnt. Operation of rvsnt requires administrator user rights at the system level and in the rvsnt environment. Carry out the following steps if you want to stop the rvs Monitor at the system level: Execute the Windows NT menu command Start Settings Control Panel. Start the Services program. Note: The term Service means a program that can be started from the operating system and works in the background. Search the list of services for rvs Monitor and select the service by clicking the appropriate line. Press the button Stop. Windows NT will now try to end the service. If the attempt is successful the rvs Monitor status will change to (not started). Carry out the following steps if you want to stop the rvs Monitor from within the rvsnt program environment while it is in operation: Start the rvsnt Administrator program in the rvs file. Execute the menu command Monitor Stop, or Start the Stop rvs Monitor program in the rvs file. The rvs Monitor then stops. It has been stopped if the stop symbol is not active on the tool bar. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 67

68 Operator Manual 3.3 Customizing the Monitor Parameters for Windows NT The Monitor parameters determine the operational mode of the rvs Monitor, the main component of the rvsnt system. By customizing the Monitor parameters you can modify the rvs Monitor in accordance with your system environment and your own requirements. You should customize the Monitor parameters in order to minimize the load on your system and in order to enhance the performance (parameters OCREVAL, OEXBUF, RECVBLOCKS and SENDBLOCKS; for more information please see "rvs Parameters" control the Monitor Log Book display make optimal use of data line quality monitor communication processes with other stations. administer the size and number of the log files. The rvs database, which works as a central information source, provides the rvs Monitor with allf the information required for the tasks to be executed. When the rvs database is initialized the initialization program first creates a parameter table for the Monitor parameters with standard values which determine the standard behaviour of the rvs Monitor. You can modify these values by editing the file c:\rvs\init\rdmini.dat, which is the source for modification of the parameter table in the rvs Monitor start phase. If you modify the file while the rvs Monitor is in operation the changes will only take effect when the Monitor is started again. Dynamic modification of the monitor parameters cannot be achieved in this way. 68

69 rvs Monitor for Windows NT Dynamic modification With the rvsnt Administrator you can dynamically modify the parameters during Monitor operation. In order to do so you have to enter individual operator commands. Carry out the following steps if you want to modify a parameter for rvs Monitor operation: Execute the View Parameters menu command in the rvsnt Administrator. The rvsnt - Parameter dialog window for editing the parameters will open. Double click the parameter that you want to modify. Enter the desired value parameter value into the input field. A complete list and description of all of the monitor parameters can be found in chapter "rvs Parameters". Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 69

70 Operator Manual Example: Parameter MAXSENDERS 2 With this example you indicate that a maximum of 2 senders transmit data at the same time. Confirm your entry with Apply. Use Close to exit the parameter list. This operation transfers the command into the rvs database. The Monitor will then read this command the next time it is started and then use the modified parameter. Static modification You can also customize the monitor parameters by making entries into the file rdmini.dat. It is read every time the rvs Monitor is restarted and the rvs orders and commands it contains are executed. Carry out the following steps if you want to permanently modify one or more monitor parameters: Open the file c:\rvs\init\rdmini.dat. Click the Monitor Parameter icon in the rvs file. The file contains the predefined operator commands which the rvs Monitor executes at each new start. Commands for modifying the rvs monitor parameters begin with setparm. Comment lines begin with *. Edit the file in accordance with your requirements. A complete list and description of all the monitor parameters can be found in "rvs Parameters". Save the file and close the text editor. Display the Monitor Log window in the rvsnt Administrator by using the View Monitor Log menu command. Stop and start the rvs Monitor. Read the action messages: They begin with A: Each setparm command in the initialization file triggers a parameter modification when the rvs Monitor is restarted. NOTE: Statically modify only those parameters which permanently differ from the rvsnt standard setting. 70

71 rvs Monitor for Windows NT Example: You want to monitor a transmission line temporarily in order to trace errors. In order to do so, modify the LITRACELEVL parameter by using the View Parameters menu command and reset it again using this command after you are done with monitoring. Please refer to chapter "Operator Console and Commands" for more detailed information, in particular on additional operator commands and optimizing rvsnt. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 71

72 Operator Manual III. AS/400 In this part of the manual the configuration process under AS/400 systems as well as the rvs Monitor for AS/400 is described. After you have installed the rvs400 system, you must adapt rvs400 to your request. Which possibilities of the configuration are available and how you can execute these, is explained in the following chapters. 4 Configuration of AS/400 Systems This section describes how to customize stationtable and related tables and how to configure the X.25, ISDN, LU6.2 and TCP/IP communication as well as how to get a license for AS/400. The last chapter of this section contains examples. 4.1 Customizing Stationtable and Related Tables for AS/400 You need an rvs entry in the Station table for each partner station you want to communicate with. The file RVS_INIT/DAT(RDSTAT) contains a sample definition file for the stationtable and its related database tables that define the characteristics of the local station and of the other nodes you want to communicate with. Change this file according to your needs using an editor. This file will be used as default stationtable input file when the rvs database is created. After you have installed rvs you will find a Station table containing sample entries for X.25/ISDN, TCP/IP and LU 6.2 communication. Lines starting with (*) are interpreted as comments. In general, the fields are case sensitive. When rdstat.dat is read, all field names and all those value fields that are not enclosed in simple quotes ( ) or double quotes (" ") are converted to upper case; e.g. 72

73 Configuration of AS/400 Systems LUNAME=MYSTAT and luname=mystat are equivalent and different from both LUNAME="Mystat" and LUNAME='mystat'. Stations are identified and managed by Station IDs (SID) consisting of three characters. Each entry in the Station table begins with a two characters table name. Line continuations are signalled by (+).The significance of the system tables is described in the following sections. Next you are presented with a sample Station table: ******************************************************** **************** * Define STATION-TABLE (ST), ROUTING-TABLE (RT), NACHBARKNOTEN (NK), * * ODETTE-PARAMETERS (OP), APPC/LU62-PARAMETERS (LU) * * X.25/ISDN-PARAMETERS (XP) * ******************************************************** **************** * * local station ST SID=LOC NETID=??LOC?? STATNAME="local station" RT SIDDEST=LOC SIDNEIGHB=LOC PRIORITY=1 NK SID=LOC FTP=O PROTOCOL=X PRIORITY=10 OP SID=LOC ODETTEID='my Odette ID' LU SID=LOC LUNAME=XVWGGU01 NETID=VWAG TPNAME=RVSRCV USERID="" + PASSWORD="" MODE=VWG6RV10 SECURITY=0 + SYNCLEVEL=NONE TYPE=MAPPED XP SID=LOC N=1 LINK=RVSLINEIN XADDRESS= TIMEOUT=30 XP SID=LOC N=2 LINK=X25LINE XADDRESS= TIMEOUT=300 TC SID=LOC N=1 INADDR= PORT=3305 MAX_IN=5 TC SID=LOC N=2 INADDR= PORT=2110 MAX_IN=10 * Partner Station - X.25 native communication sample ST SID=RSX NETID=??RSX?? STATNAME='remote station 1' RT SIDDEST=RSX SIDNEIGHB=RSX PRIORITY=1 NK SID=RSX FTP=O PROTOCOL=X PRIORITY=10 OP SID=RSX ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX XP SID=RSX LINK=X25LINE XADDRESS= TIMEOUT=300 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 73

74 Operator Manual * Partner Station - ISDN communication sample ST SID=RSI NETID=??RSI?? STATNAME='remote station 2' RT SIDDEST=RSI SIDNEIGHB=RSI PRIORITY=1 NK SID=RSI FTP=O PROTOCOL=X PRIORITY=10 OP SID=RSI ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX XP SID=RSI LINK=RVSLINERSI XADDRESS= TIMEOUT=30 * Partner Station - SNA-LU6.2 communication sample ST SID=RSL NETID=??RSL?? STATNAME='remote station 3' RT SIDDEST=RSL SIDNEIGHB=RSL PRIORITY=1 NK SID=RSL FTP=O PROTOCOL=L PRIORITY=10 OP SID=RSL ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX LU SID=RSL LUNAME=LU62RSL NETID=VWAG TPNAME=RVSRCV USERID="" + PASSWORD="" MODE=VWG6RV10 SECURITY=0 + SYNCLEVEL=NONE TYPE=MAPPED * Partner Station - TCP/IP communication sample ST SID=RST NETID=??RST?? STATNAME='remote station 2' RT SIDDEST=RST SIDNEIGHB=RSTPRIORITY=1 NK SID=RST FTP=O PROTOCOL=T PRIORITY=10 OP SID=RST ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX TC SID=RST INADDR= PORT=3305 * ROU (Routing sample: send file to station ROU via station RSX) * ("via station" is defined in SIDNEIGB) * (RSX must have a partner with Odette-ID of ROU) * ST SID=ROU NETID=?ROU? STATNAME='example for routing via RSX' RT SIDDEST=ROU SIDNEIGHB=RSX PRIORITY=1 OP SID=ROU ODETTEID='OROU' PSWFROM=aaa PSWTO=aaa The different operation systems use the same Station tables, differentiated only by the parameter LINK, which depends on the operation system. This parameter specifies the name of the used line definition for AS/400. For Windows NT and UNIX the parameter is pre-set in rvs. For further information on the LINK parameter see section "X.25 native Communications XP" and "X.25 native Communications XP for AS/400". The Station table is read automatically, when the database is initialised. Later changes in the Station table become effective only after deleting or re-initialising the rvs database. Alternatively, you can type the command modst in the operator interface (see section "Operator Console and Commands"). Note: Please observe, that the modst command adds new stations or changes the present ones. 74

75 Configuration of AS/400 Systems If you want to delete stations, you can use the command delst sid=... The related tables contain the information listed in the following sections Identification of rvs Nodes for AS/400 In the stationtables, there are several parameters that identify rvs nodes: SID This is a locally unique station ID which must consist of up to sixteen characters. This is a strictly local definition; remote stations do not have access to these names; they only know the ODETTE-IDs. When choosing station IDs, keep in mind that these IDs will have to be used in all SendEntries (SE) and ResidentEntries (RE) to identify the target and the source of the transmission, respectively. ST.NETID This parameter is not used in current version! NETID in database table ST is the unique identification of a table within the entire rvs network to which the station belongs. It is used to identify recipients in distribution lists. OP.ODETTEID ODETTE ID in database table OP is a worldwide unique identification of all nodes that use the ODETTE File Transfer Protocol (OFTP). This 25 character name consists of the letter O, an 18 character organization identifier that is provided by the ODETTE codification group, and a 6 character computer subaddress that is administrated by each organization. If you communicate within your own closed network only, the ODETTE ID may be freely chosen as long as it remains unique in your network. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 75

76 Operator Manual In Germany, to apply for a ODETTE ID please contact : Verband der Automobilindustrie e.v. ( VDA ) Abt. Logistik Postfach Frankfurt Tel.: Get the complete description of OFTP from StationTable ST for AS/400 This system table contains information about your own station as well as information about all nodes that can be reached from the local station (either directly or indirectly, including the local station itself). Table ST: SID NETID STATNAME PHONE Station ID; this name is unique within the local installation, only. Unique ID in the entire rvs network (see section 6.1.1"Identification of rvs Nodes" above) Descriptive name of station This text will be displayed when a list of stations is requested in the rvs dialog interface. Phone number of contact person at SID. This entry is a comment (optional). 76

77 Configuration of AS/400 Systems RoutingTable RT for AS/400 This system table defines for each rvs station through which neighbor(s) it can be reached. If more than one neighbor could be used, the routes should have different priorities; the one with the highest priority at the time the SK command is created will be used. It is the responsibility of network administration to avoid cycles that do not include the intended destination. Be especially careful when defining alternate paths to direct neighbors because others may think you are the proper transit station, since you are directly connected to it! The routing table must include an entry for your local station. Normally, the local station will be its own neighbor. Table RT: SIDDEST SIDNEIGHB PRIORITY Station ID of destination Station ID of neighbor that offers a path to the destination Determines which path is selected (the smaller the numerical value, the higher the priority, i. e. PR_HIGH < pr < PR_LOW). Not yet supported. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 77

78 Operator Manual Neighbour Node (NachbarKnoten) NK for AS/400 This system table contains detailed information how (and when) other nodes can be reached. Table NK: SID PROTOCOL FTP AUTODIAL DELAY Station ID of neighbor Line protocol Possible values: T TCP/IP ( ODETTE Standard ) X X.25 native / X.25 over ISDN (ODETTE Standard) L LU 6.2 R TCP/IP (rvs internal only for UNIX) Default: T File Transfer Protocol: O ODETTE Default: O Determines whether rvs automatically dials out if a data set is to be sent. Y a sender task will be started, as soon as a send request is available. N no sender task will be initiated, even when a send request is available. The queued data sets will be sent as soon as the partner establishes the connection, or an activate sid=xxx command for this partner is submitted from rvs Console. Default: Y Time (in seconds) that rvs should wait between connection attempts to this station. Default: 0 78

79 Configuration of AS/400 Systems PSESSIONS PRIORITY Maximum parallel sessions to be started to this partner. A value of -1 uses the global parameter MAXSESSIONS. Default: -1, use the global value from parameter MAXSENDERS. The overall number of parallel sessions is limited by MAXSESSIONS. Determines which combination of FTP and PROTOCOL is selected (the smaller the numerical value, the higher the priority, i. e. PR_HIGH pr PR_LOW) ODETTE Parameters OP for AS/400 This system table contains ODETTE related information about all nodes (not just the neighboring ones!) that can be reached from the local station using this File Transfer Protocol. Valid passwords are needed for neighboring nodes only. Table OP: SID ODETTEID PSWFROM Station ID As defined by ODETTE protocol (see section 6.1.1) Password that we are expecting this neighbor to send to us PSWTO Password that we are sending to this neighbor These ODETTE passwords are always exchanged and checked for neighboring nodes, independent of definitions for communication security as defined for LU 6.2. SENDBLOCKS Number of blocks to be sent before a checkpoint is reached. Use high values for "noiseless" connections to increase performance and low values for "noisy" connections. Default: 0, use the value from global parameter SENDBLOCKS Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 79

80 Operator Manual RECVBLOCKS Number of blocks to be received before a checkpoint is reached. Use high values for "noiseless" connections to increase performance and low values for "noisy" connections. Default: 0, use the value from global parameter RECVBLOCKS OEXBUF ODETTE exchange buffer size in bytes Default: 0, use the value from global parameter OEXBUF OCREVAL CODEIN CODEOUT USERFIELD RETRY ODETTE FTP windowsize, number of buffers to be sent before waiting for a response Default: 0, use the value from global parameter OCREVAL For codetranslation code of the local host (not yet implemented) For codetranslation code of the remote host (not yet implemented) SPECLOG: Force OFTP special logic. NOT necessary under normal conditions; if a partner requests special logic, rvs as a responder always answers with special logic. If USERFIELD is set to SPECLOG, rvs as an initiator tries to establish the OFTP special logic. That means the OFTP packet SSID contains SSIDSPEC=Y. If the partner (responder) answers with SSIDSPEC=Y, the following packets are transmitted and received with a leading STX character, a block sequence character, the data and two trailing checksum characters. (Not yet implemented) 80

81 Configuration of AS/400 Systems VDSNCHAR EERP_IN EERP_OUT Range of allowable charactersto be transferred within an ODETTE transmission: ALL: no restrictions OFTPUNIX: all capital letters, digits and the special characters. - UNIX: all letters, digits and the special characters # _ - +. ODETTE: all capital letters, digits and the special characters () -. / & CHECK_RE: same as ALL, but it is necessary that a RE exists default: ALL Wait for a receipt from the partner NEVER partner does not send EERP, so a send request ends with the correct transmission without waiting for the receipt NORMAL wait for receipt, end send request when receiving receipt Default: NORMAL Handling for sending a receipt NEVER partner does not expect EERP, so don't create a receipt IMMEDIATE create a receipt and start a session, if no session is available NORMAL create a receipt, but wait for a session to transmit (suggested) Default: IMMEDIATE Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 81

82 Operator Manual LU 6.2 parameters LU for AS/400 This system table contains LU 6.2 related information about the own local node or all neighboring nodes that can be reached from the local station using this protocol. Table LU: SID LUNAME TPNAME USERID PASSWORD Station ID; this name must be unique in the local installation. This is a required parameter. LU name of remote host. Default: no default Name of remote transaction processing program. This is a required parameter. For your local station, this name must match the invocable TP name that the remote stations are calling (with RVSRCV as default). rvs on an MVS-host (rvsmvs), uses RVSOFTP instead as its local TP name. If you intend to communicate with an rvsmvs make sure the host is calling you with TP name RVSRCV and you call it with RVSOFTP. User ID to be used with remote program Default: one blank Password needed to start remote program Default: one blank The required values for USERID and PASSWORD depend upon your communication partner's system and whether or not secure communication has been agreed upon. 82

83 Configuration of AS/400 Systems If your communication partner is another UNIX node, turn communication security off on both sides when defining a Partner LU Profile. Sending: USERID and PASSWORD from your LU entry for the remote node are those that your neighbor defined in his list of User Profiles (outside of the Communication Manager). Receiving: Your neighbor must enter those values for USERID and PASSWORD in his LU entry for your station that you defined in your list of User Profiles (outside of the Communication Manager). If your communication partner is an AS/400 node, turn communication security on when defining a Partner LU Profile. Sending: USERID and PASSWORD should be set to empty strings USERID="" PASSWORD=""and the respective device at the AS/400 should be defined, so that it will start the receiver under a default user name and does not require a password. Receiving: Your neighbor must enter those values for USERID and PASSWORD in his LU entry for your station that you defined in your list of Dialog Security Profiles (within the Communication Manager). Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 83

84 Operator Manual MODE SECURITY SNA session mode (one priority only) Default: one blank For communication with rvsmvs, this is the name of the VTAM Modetable Entry defined in the NCP LU Macro, with the DLOGMODE parameter. We strongly suggest you select a mode name that is min. eight characters long, because some implementations of LU 6.2 do not pad shorter names properly! If this happens, the remote side may not recognize the mode name and refuse to establish a session. specifies, whether password and user ID are expected: 0 (none) no user ID/password exchanged. This is the required value, if you communicate with rvsmvs. 1 (user security) userid/password must be specified explicitly Default: 0 SYNCLEVEL APPC synchronisation level NONE no confirmation CONFIRM confirmation may be requested Default: NONE TYPE APPC conversation type BASIC basic conversation (not supported, at this time) MAPPED mapped conversation Default: MAPPED 84

85 Configuration of AS/400 Systems X.25 native Communications XP for AS/400 XP contains data of X.25-native communications. Table XP: SID Station ID, defining local or remote station for which this entry is defined. N Key, to distinguish between different XP Blocks (e.g. to accept calls from different interfaces). Only supported for incoming calls. Use numbers beginning with 1. XADDRESS DTE address, character string of maximum 15 decimal digits. For the local station, this is the own X.25 DTE address; for a remote station, it is the remote DTE address. Default: empty string TIMEOUT LINK Time period in seconds after which a connection is automatically terminated, if the partner station does not answer. Default: 60 (seconds) Link name, string of characters. Link name for AS/400. Name of the used X.25 line description If ISDN router BinTec BRICK is used: The link name for BRICK routers must be RCAPI1 (1 stands for the control field in the ISDN request CAPI2_CONNECT_REQ and can be changed, e.g. to vary the BRICK board number). See Chapter "" for more information. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 85

86 Operator Manual USERDATA ALIAS RECV_ALIAS Call user data, string of maximum 256 hex characters (128 bytes); optional; default: empty string (no data) Call user data are appended to the outgoing call packet and might be used by the remote installation as control information, especially for routing to the target application. The first byte of the call user data field is commonly interpreted as "Protocol Identifier", PID, where some values are reserved, for example: X'C3' for SNA QLLC, X'C4' for SNA ELLC, X'EE' for TCP/IP. Therefore, care must be taken when using call user data and there must be a mutual agreement with your partner station. Under normal circumstances, the call user data field is not required. For incoming calls you can specify which protocol ID you want to accept with rvs, e.g. to distinguish between different partners. You can define 1 PID for each XP-Block. USERDATA is represented in hex, so for "RVS" you have to code "525653". Optional IP address for ISDN router BinTec BRICK, format "nnn.nnn.nnn.nnn". When rvs connects to a station with LINK=RCAPI1 ISDNNO=nnn ALIAS=nnn.nnn.nnn.nnn, it establishes a TCP/IP connection to this IP address. If ALIAS is empty, rvs reads the IP address from the UNIX environment variable CAPI_HOST. So, if you leave ALIAS empty, then define the variable CAPI_HOST in the rvs profile (e.g. $RVSPATH/.profile, see chapter "Representation means" for the detailed description of $RVSPATH). Defining ALIAS is especially useful if incoming calls originate from more than one BRICK router. string of characters. Provides a logical link for the rvs receiver. The default is IBMSAMP. Sometimes another application uses the entry IBMSAMP, so you have to define another entry. 86

87 Configuration of AS/400 Systems Receiving via X.25 and ISDN: If you want to be able to receive files from more than one partner at the same time, you have to prestart an X.25 receiver programs for each channel: 1. Edit the monitor initialisation file (RVS_INIT/DAT(RDMINI)) and set the rvs parameter MAXX25RCV to the number of receivers; 2. Edit the stationtable file (RVS_INIT/DAT (RDSTAT)) and add an X.25-parameter block ("XP") for each receiver to the local entry. Example for the local station definition (Receiving via ISDN BRICK router, listening on both ISDN channels, listen only for calls to our ISDN number with last digit=7): XP SID=LOC N=1 LINK="RCAPI1" ISDNNO="7" XP SID=LOC N=2 LINK="RCAPI1" ISDNNO="7" Example for the remote station definition (call via BRICK ISDN router to ISDN no. 4711, optional X.25 address 20): XP SID=R11 LINK="RCAPI1" ISDNNO=4711 XADDRESS=20 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 87

88 Operator Manual TCP/IP parameters TC for AS/400 This system table contains TCP/IP related information about the own local node or all neighboring nodes that can be reached from the local station using the protocols T (ODETTE standard) and R (rvs internal TCP/IP). For installation, please refer to chapter "Defining TCP/IP Communication". Table TC: SID N PROTOCOL INADDR PORT MAX_IN MAX_OUT Station ID; this name is unique in the local installation, only. This is a required parameter. Key which distinguishes between different TC blocks (e.g. to accept calls from different ports). For OFTP using TCP/IP, set: N=1 If you want to use the old rvs internal TCP/IP, set: local station:n=0 remote station:n=0 Line protocol R TCP/IP (for rvsx only - old rvs internal TCP/IP) T TCP/IP (ODETTE standard) Internet address / IP address or hostname Format or rvsas1.gedas.de Port to connect to (for OFTP is suggested to use 3305) Max. number of concurrent incoming transfers using the same port (relevant only for the local station). Max. number of concurrent outgoing transfers using the same port (not yet implemented). 88

89 Configuration of AS/400 Systems Example for the local station definition: TC SID=LOC PROTOCOL=T N=1 INADDR="" PORT=3305 Example for the remote station definition: TC SID=ABC PROTOCOL=T N=0 INADDR=xxx.xxx.xxx.xxx PORT= Defining X.25 Communication This section describes the prerequisites for X.25 communication, the definition of a X.25 line. It also informs you how to customise the station table and to activate a X.25 receiver task Prerequisites The prerequisites for the configuration with X.25 communication are: a X.25 main attachement with min. 2 in/out SVCs (switched virtual circuits) a free V.24 or X.21 interface installed on your system a connection to the X.25 network access (modem) Please note, that the connection to your modem must have a full 1:1 wiring of all pins. Use only prepared wired cables and observe the requirements specific for your country. You must not use null modem cable (crossed pin connection)! Customising the Station Table rvs/400 needs a station table entry RVS_INIT/DAT(RDSTAT)for every station you want to communicate with. Note, that for all stations you want to communicate with via X.25, you have to set the parameter PROTOCOL=X in the NK block. You have to write the required X.25 connection definition under LINK=... and the X.25 address of your communication partner under XADDRESS=..., both situated in the XP block. For further information see chapter "X.25 native Communications XP for AS/400". Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 89

90 Operator Manual Defining an X.25 Line Before being able to execute an rvs/400 data transfer via X.25 you need an X.25 line definition. The following example shows you how to create a line definition with 2 incoming / outgoing SVCs at the the LIN012 resource and the local X.25 address Example: CRTLINX25 LIND(X25LINE) RSRCNAME(LIN021) + LGLCHLE((001 *SVCBOTH) (002 *SVCBOTH)) + NETADR( ) DFTWDWSIZE(2) + TEXT( X.25 Leitung für rvs400 ) Next, you can attach the line by the following command: VRYCFG CFGOBJ(X25LINE) CFGTYPE(*LIN) STATUS(*ON) + RANGE(*NET) VRYWAIT(*CFGOBJ) RESET(*NO) Activating an X.25 receiver task In order to use X.25 communication, rvs/400 has to start a receiver task, which listens on the X.25 line for incoming calls. Modify the rvs parameter MAXX25RCV. (The default value is '0', because there is no need for an X.25 receiver task when using SNA-LU6.2 and TCP/IP communication.) Set MAXX25RCV=1 in order to activate a receiver task, when the Monitor will be started. Please refer to sections "Start rvs400 Monitor" and "Operator Console and Commands" for more information. Example: ==> SETPARM MAXX25RCV=1 The value of the parameter does not change after the end or restart of the rvs Monitor, because it is defined in the rvs database. Upon restart of the rvs Monitor you will see a message from the receiver task: Example: I: <X25_READY> : X.25 Receiver ready to accept incoming calls on line X25LINE. 90

91 Configuration of AS/400 Systems Configuration Example X.25 /* Definition of an X.25 line */ CRTLINX25 LIND(X25LINE) RSRCNAME(CMN02) + LGLCHLE((001 *SVCBOTH) (002 *SVCBOTH)) + NETADR( ) CNNINIT(*LOCAL) ONLINE(*NO) + EXCHID( ) DFTPKTSIZE(128) MAXPKTSIZE(128) + MODULUS(8) DFTWDWSIZE(2) TEXT( X25 line for rvs ) 4.3 Defining ISDN Communication This chapter describes the prerequisites required to run rvs with ISDN communication. Next, a description is presented how to define a connection list and how to add new entries to this list. Additionally, the definition of an ISDN network interface and of an X.25 line via ISDN are given. The last section describes how to customise the Station table and how to start an ISDN receiver task. General description A lower-cost alternative to an X.25 main connection is an ISDN connection. The ODETTE File Transfer Protocol (OFTP VDA recommendation 4914/2 ) is based on the native X.25 protocol, so it must be permuted to ISDN. You can choose between 2 alternatives: The VDA recommendation 4914/2, supplement "Nutzung des ISDN für 4914/2" describes the use of X.25/ISDN adapters, realising a relay function according to X.31 CCITT. If you need more information about the application of such X.25/ISDN adapters, please contact your distributor, because we don't pay further attention to it in this manual. Using of an X.25 protocol by means of an integrated ISDN communication adapter. We will discuss this possibility in the following. For further information see "OS/400 ISDN Support" Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 91

92 Operator Manual Requirements Requirements for the configuration with ISDN communication are: an ISDN S 0 connection (with to B-channels) an ISDN adapter (e.g. IBM 2605) installed on your system a connection to the ISDN network access Note, use only prepared wired cables and observe the requirements specific for your country Defining a connection list and inserting new entries In order to establish an X.25 connection via ISDN you need to specify a connection list of the ISDN communication which stores the ISDN call numbers. The following example describes the definition of a connection list named RVS and designed for one 1TR6-ISDN connection. Example: CRTCNNL CNNL(RVS) NETTYPE(*DBP1TR6) + TEXT( Connection list for rvs400 ) You have to add to this list an entry receiving the incoming calls. Example: ADDCNNLE CNNL(RVS) ENTRY(ANY) RMTNBR(*ANY) + RMTNBRTYPE(*UNKNOWN) RMTNBRPLAN(*ISDN) + LCLNBRPLAN(*ISDN) TEXT( accept any incoming call ) For each ISDN communication partner you have to add a separate entry. Tip: Use the station ID as the name for the connection list entry. Example: ADDCNNLE CNNL(RVS) ENTRY(VWG) RMTNBR( ) + RMTNBRTYPE(*UNKNOWN) RMTNBRPLAN(*ISDN) + LCLNBRPLAN(*ISDN) TEXT( gedas ) Definition of an ISDN network interface First, you have to install the integrated ISDN communication adapter in order to access it later. 92

93 Configuration of AS/400 Systems The following example is the definition of an adapter with an 1TR6-ISDN connection, 2 B-channels and a call number (installed) on the Resource CMN02. Example: CRTNWIISDN NWID(ISDNNWI) RSRCNAME(CMN02) + NETTYPE(*DBP1TR6) CHLENTRY((1 *SWT) (2 *SWT))+ PCLENTRY((*X25 *LOAD *MAX)) + LCLNBR( ) + TEXT( ISDN network interface ) Definition of X.25 lines via ISDN You have to create an X.25 line description for each communication partner which refers to a specified connection list entry and a specified ISDN network interface. To be able to receive calls via ISDN you need an additional X.25 line description. Tip: Use for the name of the line description a syntax which clearly identifies the usage of the line. Next you see a definition example of an X.25 line accessing the ISDN network interface ISDNNWI in order to communicate with the station VWG. You must have generated a connection list entry VWG in the connection list RVS before as a prerequisite (the local ISDN number is taken to be ). Example: CRTLINX25 LIND(RVSLINEVWG) RSRCNAME(*NWID) + LGLCHLE((001 *SVCBOTH) (002 *SVCBOTH)) + NETADR( ) CNNINIT(*LOCAL) ONLINE(*NO) + INTERFACE(*X31) CNN(*SWTPP) + SWTNWILST((ISDNNWI *B)) X25DCE(*NO) + LINESPEED(*CALC) CNNLSTOUT(RVS) + CNNLSTOUTE(VWG) CNNLSTIN(RVS) CALLIMMED(*NO) + LINKSPEED(64000) CMNRCYLMT(0 3) + TEXT( Line for VWG ) The next example presents a definition of an X.25 line receiving incoming calls. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 93

94 Operator Manual Example: CRTLINX25 LIND(RVSLINEIN) RSRCNAME(*NWID) + LGLCHLE((001 *SVCBOTH) (002 *SVCBOTH)) + NETADR( ) CNNINIT(*LOCAL) ONLINE(*NO) + INTERFACE(*X31) CNN(*SWTPP) + SWTNWILST((ISDNNWI *B)) X25DCE(*NO) + LINESPEED(*CALC) CNNLSTOUT(RVS) + CNNLSTOUTE(LOC) CNNLSTIN(RVS) CALLIMMED(*NO) + LINKSPEED(64000) CMNRCYLMT(0 3) + TEXT( Line for VWG ) Customising the Station Table For every station you want to communicate with rvs400 needs an entry in the station table RVS_INIT/DAT(RDSTAT). Observe, that for all stations you want to communicate with via ISDN, you have to set the parameter PROTOCOL=X in the NK block. You have to place the required X.25 line description under LINK=... and the ISDN call number of your communication partner under XADDRESS=... in the XP block. For further information see chapter "X.25 native Communications XP for AS/400". In the description of the XP block you have to specify the name of the line for incoming calls as the link name of your local station. Example: ST SID=LOC NETID=??LOC?? STATNAME= lokale Station... XP SID=LOC N=1 XADDRESS= Your call number + LINK=RVSLINEIN TIMEOUT=30 In the description of the XP block you have to specify as link name for each station the name of the line to be used. Example: ST SID=VWG NETID=??VWG?? STATNAME= VW-GEDAS... XP SID=VWG N=1 XADDRESS= LINK=RVSLINEVWG TIMEOUT=30 94

95 Configuration of AS/400 Systems Activating an ISDN receiver task The same statements and recommendations for the activation of an X.25 receiver task are valid for the activation of an ISDN receiver task. (see section "Activating an X.25 receiver task") Configuration Example for ISDN /* Definition of a network interface */ CRTNWIISDN NWID(ISDNNWI) RSRCNAME(CMN02) ONLINE(*NO) + VRYWAIT(*NOWAIT) NETTYPE(*DBP1TR6) CALLCTL(*FIRST) + CHLENTRY((1 *SWT) (2 *SWT)) + PCLENTRY((*X25 *LOAD *MAX)()) + LCLNBR(' ') LCLNBRTYPE(*UNKNOWN) + LCLNBRPLAN(*UNKNOWN) LCLNBRPSN(*ALLOW) + RMVCHR((' ') ('(')(')') ('/') ('-') ('+') ('.')) + LCLSUBADR(*CNNL) TEID(*AUTO) SPID(() ()) + X31NFYCLS(*NONE) SETUPDIF(*NONE) PRCDIF(*NONE) + X31DIF(*NONE) ACTTMR(100) REACTTMR(10) + THRESHOLD(*MED) CMNRCYLMT(2 5) + TEXT('ISDN-Networkinterface on resource CMN02') /* Definition of connection list RVS */ CRTCNNL CNNL(RVS) NETTYPE(*DBP1TR6) + RMVCHR(' ' '(' ')' '/' '-' '+' '.') + TEXT('Connectionlist for rvs400') /* Entry to accept any incoming call */ ADDCNNLE CNNL(RVS) ENTRY(ANY) RMTNBR(*ANY) + TEXT('Accept any incoming call') RMTNBRTYPE(*UNKNOWN) + RMTNBRPLAN(*ISDN) RMTSUBADR(*ANY) RMTSUBTYPE(*USER) + LCLNBR(*ANY) LCLNBRTYPE(*UNKNOWN) LCLNBRPLAN(*ISDN) + LCLNBRPSN(*ALLOW) LCLSUBADR(*ANY) LCLSUBTYPE(*USER) + NETSPFINF(*ALLANY) TRSNETSEL(*NONE) + INFTRFTYPE(*UNRESTRICTED) CNN(*CIRCUIT) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 95

96 Operator Manual /* Entry for station VWG */ ADDCNNLE CNNL(RVS) ENTRY(VWG) RMTNBR(' ') + TEXT('VW-GEDAS') RMTNBRTYPE(*UNKNOWN) + RMTNBRPLAN(*ISDN) RMTSUBADR(*ANY) RMTSUBTYPE(*USER) + LCLNBR(*ANY) LCLNBRTYPE(*UNKNOWN) LCLNBRPLAN(*ISDN) + LCLNBRPSN(*NONE) LCLSUBADR(*ANY) LCLSUBTYPE(*USER) + NETSPFINF(*ALLANY) TRSNETSEL(*NONE) + INFTRFTYPE(*UNRESTRICTED) CNN(*CIRCUIT) /* Line for incoming calls */ CRTLINX25 LIND(RVSLINEIN) RSRCNAME(*NWID) + LGLCHLE((001 *SVCBOTH)(002 *SVCBOTH)) + NETADR( ) EXNNETADR(*NO) + CNNINIT(*LOCAL) ONLINE(*NO) INTERFACE(*X31) + CNN(*SWTPP) X25DCE(*YES) VRYWAIT(*NOWAIT) + LINESPEED(*CALC) PKTMODE(*NO) EXCHID(056C0001) + MAXFRAME(1024) DFTPKTSIZE(128 *TRANSMIT) + MAXPKTSIZE(*DFTPKTSIZE *TRANSMIT) MODULUS(8) + DFTWDWSIZE(2 *TRANSMIT) ADRINSERT(*YES) IDLTMR(40) + FRAMERTY(7) THRESHOLD(*OFF) SWTCNN(*BOTH) + CNNLSTOUT(RVS) CNNLSTOUTE(LOC) CNNLSTIN(RVS) + CALLIMMED(*NO) SWTDSC(*YES) SWTDSCTMR(170 0) + LINKSPEED(64000) SWTNWISLCT(*FIRST) + COSTCNN(128) COSTBYTE(128) SECURITY(*PKTSWTNET) + PRPDLY(*PKTSWTNET) USRDFN1(128) USRDFN2(128) + USRDFN3(128) CMNRCYLMT(3 0) + TEXT( Line for incoming calls ) /* Line for outgoing calls to VWG */ CRTLINX25 LIND(RVSLINEVWG) RSRCNAME(*NWID) + LGLCHLE((001 *SVCBOTH)(002 *SVCBOTH)) + NETADR( ) EXNNETADR(*NO) + CNNINIT(*LOCAL) ONLINE(*NO) INTERFACE(*X31) + CNN(*SWTPP) X25DCE(*YES) VRYWAIT(*NOWAIT) + LINESPEED(*CALC) PKTMODE(*NO) EXCHID(056C0001) + MAXFRAME(1024) DFTPKTSIZE(128 *TRANSMIT) + MAXPKTSIZE(*DFTPKTSIZE *TRANSMIT) MODULUS(8) + DFTWDWSIZE(2 *TRANSMIT) ADRINSERT(*YES) IDLTMR(40) + 96

97 Configuration of AS/400 Systems FRAMERTY(7) THRESHOLD(*OFF) SWTCNN(*BOTH) + CNNLSTOUT(RVS) CNNLSTOUTE(VWG) CNNLSTIN(RVS) + CALLIMMED(*NO) SWTDSC(*YES) SWTDSCTMR(170 0) + LINKSPEED(64000) SWTNWISLCT(*FIRST) + COSTCNN(128) COSTBYTE(128) SECURITY(*PKTSWTNET) + PRPDLY(*PKTSWTNET) USRDFN1(128) USRDFN2(128) + USRDFN3(128) CMNRCYLMT(3 0) + TEXT( Line for outgoing calls to VWG ) 4.4 Defining LU6.2 Communication This section explains how to generate a line description, a controller and a unit and mode description. It also explains how to customise the station table and how to add a new ICF entry General overview With rvs400 you can also use the SNA-LU6.2 protocol. Explanatory note: The OFTP-SNA-LU6.2 communication is an extension of the standard OFTP. You can only use it, if your partner uses rvs, too. Advantages of SNA-LU6.2 are: Almost complete independence from the physical transmission type Better security by means of password exchange and encrypting Parallel data transfer using the same line To install an LU 6.2 connection several steps have to be done. You have to co-ordinate several parameters with your communication partners before installing LU 6.2. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 97

98 Operator Manual Explanatory note: You can find examples and worksheets which can prove useful for establishing your SNA LU6.2 connections and documentation in the following sections: " Configuration Example SNA LU6.2 via X.25 to IBM Host", "Configuration Example SNA LU6.2 via Token Ring to AS/400" and "Examples Configuration Worksheets" Generating a line description The first step is the definition of a line description by means of the CRTLIN xxx command. 'xxx' determines the line type (e.g. X25, TRN, SDLC). You can find the important parameters in the worksheet, which you have completed before. (see also chapter "Examples Configuration Worksheets") Generating a Controller The next step is to generate a controller. Depending on the type of your partner system you generate the controller using the command CRTCTLAPPC or CRTCTLHOST. In this case you can also find the important parameters in the worksheet, which you have completed before. Set as parameter determining the line (LINE) the newly generated line description (see also chapter "Examples Configuration Worksheets") Generating an unit description After you have created a controller you have to generate an APPC unit description. Use the command CRTDEVAPPC. In this case you can also find the important parameters in the worksheet, which you have completed before. Set as parameter determining the applied controller the just generated controller (see also chapter "Examples Configuration Worksheets"). 98

99 Configuration of AS/400 Systems Explanatory note: All names needed to describe the units in the rvs400 communication via SNA LU 6.2 should start with RVS... because there are routing entries already defined in the QRVS subsystem (see also chapter " Configuration Example SNA LU6.2 via X.25 to IBM Host" and "Configuration Example SNA LU6.2 via Token Ring to AS/400") Generating a mode description The next step is the generation of a mode description using the CRTMODD command. Explanatory note: The name of the mode must be 8 characters long, because some SNA LU 6.2 implementations are not able to handle shorter names (see also chapter " Configuration Example SNA LU6.2 via X.25 to IBM Host" and "Configuration Example SNA LU6.2 via Token Ring to AS/400") Adding an ICF entry rvs400 handles the SNA LU 6.2 communication via an ICF file, therefor you have to specify an entry for each LU6.2 communication partner in the RVS_INIT/ICF_RVS00 file (generated during the installation process). Use the ADDICFDEVE command and set the station ID of the particular station as the program device parameter (PGMDEV) (see also chapter " Configuration Example SNA LU6.2 via X.25 to IBM Host" and "Configuration Example SNA LU6.2 via Token Ring to AS/400") Customising the Station Table For every station you want to communicate with rvs400 needs an entry in the station table RVS_INIT/DAT(RDSTAT). Observe, that for all stations you want to communicate with via SNA LU 6.2 you have to set the parameter PROTOCOL=L in the NK block. You have to place the corresponding values for your partner(s) in the LU block. For further information see chapter "LU 6.2 parameters LU for AS/400". Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 99

100 Operator Manual Configuration Example SNA LU6.2 via X.25 to IBM Host /* Mode description */ CRTMODD MODD(VWG6RV10) COS(#CONNECT) MAXSSN(8) MAXCNV(8) + LCLCTLSSN(4) PREESTSSN(0) MAXINPAC(*CALC) INPACING(7) + OUTPACING(7) MAXLENRU(*CALC) DTACPR(*NETATR) + INDTACPR(*RLE) OUTDTACPR(*RLE) /* Line description */ CRTLINX25 LIND(X25LINE) RSRCNAME(CMN02) + LGLCHLE((001 *SVCBOTH) (002 *SVCBOTH)) + NETADR( ) CNNINIT(*LOCAL) ONLINE(*NO) + EXCHID( ) DFTPKTSIZE(128) MAXPKTSIZE(128) + MODULUS(8) DFTWDWSIZE(2) TEXT( X25 Leitung für rvs ) /* Controller unit description */ CRTCTLHOST CTLD(X25HOST) LINKTYPE(*X25) ONLINE(*YES) + SWITCHED(*YES) APPN(*NO) SWTLINLST(X25LINE) + CODE(*EBCDIC) + MAXFRAME(1024) RMTNETID(VWAG) LCLEXCHID(*LIND) + INLCNN(*DIAL) DIALINIT(*LINKTYPE) + CNNNBR(' ') ANSNBR(*CNNNBR) SWTDSC(*NO) + NETLVL(1980) LINKPCL(*QLLC) + DFTPKTSIZE(*LIND *LIND) DFTWDWSIZE(*LIND *LIND) + RVSCRG(*NONE) X25FRMRTY(7) X25RSPTMR(300) + X25') CMNRCYLMT(2 5) TEXT('PU Typ 2 for rvs via /* Unit description */ CRTDEVAPPC DEVD(RVSDEVR11) LOCADR(00) RMTLOCNAME(AVBR11L) + ONLINE(*YES) LCLLOCNAME(XVWGGU01) RMTNETID(VWAG) + CTL(X25HOST) MODE(VWG6RV10) MSGQ(*LIBL/QSYSOPR) + APPN(*NO) SNGSSN(*NO) SECURELOC(*NO) 100

101 Configuration of AS/400 Systems /* Adding an ICF entry for station HST */ ADDICFDEVE FILE(RVS_INIT/ICF_RVS00) PGMDEV(HST) + RMTLOCNAME(AVBR11L) LCLLOCNAME(XVWGGU01) + DEV(RVSDEVR11) MODE(VWG6RV10) RMTNETID(VWAG) Configuration Example SNA LU6.2 via Token Ring to AS/400 /* Mode description */ CRTMODD MODD(VWG6RV10) COS(#CONNECT) MAXSSN(8) MAXCNV(8) + LCLCTLSSN(4) PREESTSSN(0) MAXINPAC(*CALC) INPACING(7) + OUTPACING(7) MAXLENRU(*CALC) DTACPR(*NETATR) + INDTACPR(*RLE) OUTDTACPR(*RLE) /* Line description */ CRTLINTRN LIND(TRNLINE) RSRCNAME(CMN03) ONLINE(*YES) + VRYWAIT(*NOWAIT) MAXCTL(40) LINESPEED(4M) + MAXFRAME(1994) TRNLOGLVL(*OFF) TRNMGRMODE(*OBSERVING) + LOGCFGCHG(*NOLOG) TRNINFBCN(*NO) ADPTADR(*ADPT) + EXCHID(056C0001) + SSAP((04 *MAXFRAME *SNA)(12 *MAXFRAME *NONSNA) + (AA *MAXFRAME *NONSNA)(C8 *MAXFRAME *HPR)) + THRESHOLD(*OFF) LINKSPEED(4M) COSTCNN(0) COSTBYTE(0) + SECURITY(*NONSECURE)PRPDLY(*LAN) + USRDFN1(128) USRDFN2(128) USRDFN3(128) + AUTOCRTCTL(*YES) AUTODLTCTL(1440) CMNRCYLMT(2 5) + TEXT( Token Ring Line ) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 101

102 Operator Manual /* Controller unit description */ CRTCTLAPPC CTLD(RVSAS400) LINKTYPE(*LAN) ONLINE(*YES) + APPN(*YES) LINE(TRNLINE) + CODE(*EBCDIC) MAXFRAME(16393) RMTNETID(VWAG) + RMTCPNAME(AAS4) EXCHID(056C0971) INLCNN(*DIAL) + DIALINIT(*LINKTYPE) SWTDSC(*YES) DSCTMR(170 30) + ROLE(*NEG) ADPTADR(10005A594D62) DSAP(04) SSAP(04) + LANFRMRTY(*CALC) LANCNNRTY(*CALC) LANRSPTMR(*CALC) + LANCNNTMR(*CALC) LANACKTMR(*CALC) LANINACTMR(*CALC) + LANACKFRQ(*CALC) LANMAXOUT(*CALC) LANACCPTY(*CALC) + LANWDWSTP(*NONE) CPSSN(*YES) NODETYPE(*ENDNODE) + HPR(*YES) + TMSGRPNBR(1) MINSWTSTS(*VRYONPND) AUTOCRTDEV(*ALL) + AUTODLTDEV(1440) USRDFN1(*LIND) USRDFN2(*LIND) + USRDFN3(*LIND) CMNRCYLMT(2 5) MDLCTL(*NO) + TEXT(Controller for rvs via TRN to AS/400 ) /* Unit description */ CRTDEVAPPC DEVD(RVSAS400) LOCADR(00) RMTLOCNAME(AAS4) + ONLINE(*NO) LCLLOCNAME(S44R0540) RMTNETID(VWAG) + CTL(RVSAS400) MODE(VWG6RV10) MSGQ(*LIBL/QSYSOPR) + APPN(*YES)SNGSSN(*NO) + TEXT('automatically created with QLUS') /* Adding an ICF entry for station AS4 */ ADDICFDEVE FILE(RVS_INIT/ICF_RVS00) PGMDEV(AS4) + RMTLOCNAME(AAS4) LCLLOCNAME(S44R0540) + DEV(RVSAS400) MODE(VWG6RV10) RMTNETID(VWAG) 102

103 Configuration of AS/400 Systems Examples Configuration Worksheets Local Station Partner Station Station ID (SID) Odette ID Password from (PSWFROM) Password to (PSWTO) Line type local address (not with SDLC) Remote address (not with SDLC) Local LU (LCLLOCNAME) Remote LU (RMTLOCNAME) Exchange ID (EXCHID) Mode (MODE) Synchronisation level (SYNCLEVEL) Conversation type (TYPE) TPNAME Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 103

104 Operator Manual Line Controller Device Mode ICF entry Station table Line Controller Device Mode local LU remote LU LIND local address NETADR / ADPTADR remote address LINE NETCTL CTLD CTL DEV DEVD DEV CNNNBR / ADPTADR Exchange ID EXCHID LCLEXCHID Station ID ODETTE ID Password from Password to Sync.level Conv.Typ TPNAME MODE MODD MODE MODE LCLLOCNAME 4.5 Defining TCP/IP Communication LCLLOCNAME RMTLOCNME RMTLOCNAME LUNAME PGMDEV SID ODETTEID PSWFROM PSWTO SYNCLEVEL TYPE TPNAME This section describes the requirements for TCP/IP communication, the customising of the station table to fit TCP/IP communication and the activating of a TCP/IP receiver task. General Overview You can use also the TCP/IP protocol with rvs400. The advantages using TCP/IP are: Almost complete independence from the physical transfer type Transfer in heterogeneous networks Parallel data transfer using the same line To configure TCP/IP please refer to the recommended OS/400 system documentation "TCP/IP Configuration and Reference" (Document Number SC ) and/or "TCP/IP Fastpath Setup" (Document-Number SC ). 104

105 Configuration of AS/400 Systems Requirements Requirements to the configuration with TCP/IP communication are: TCP/IP a connection to LAN / WAN Customising the Station Table For every station you want to communicate with rvs400 needs an entry in the station table RVS_INIT/DAT(RDSTAT). Observe, that for all stations you want to communicate with via TCP/IP you have to set the parameter PROTOCOL=T in the NK block. In the TC block you have to define the IP-address or Alias in the INADDR field and the receiver port of your partner in the PORT field. For further information see chapter "TCP/IP parameters TC for AS/400" Activating a TCP/IP receiver task In order to use TCP/IP communication, rvs/400 has to start a receiver task, which listens on appropriate port for incoming calls. Modify the rvs parameter TCPIPRCV. (The default value is '0', because there is no need of an receiver task when using SNA- LU6.2 and TCP/IP communication.) Set TCPIPRCV=1 in order to activate one receiver task, always when the Monitor is started. Please refer to sections "Start rvs400 Monitor" and "Operator Console and Commands" for more information. Example: ==> SETPARM TCPIPRCV=1 The value of the parameter does not change after the end or restart of the Monitor, because it is defined in the rvs data base. Upon restart of the Monitor you will see a message from the receiver task: Example: I: <TCPIP_READY> : TCP/IP Receiver empfangsbereit auf Port: 3305 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 105

106 Operator Manual 4.6 Get a license for AS/400 You have to modify the Member RDKEY in file RVS_INIT/DAT by means of the license key. Please make a backup copy of the original file, which you can use if any failures should occur. Edit the Member RDKEY according to the license key (e.g. STRSEU RVS_INIT/DAT RDSTAT), matching the cases exactly. You can save the file RVS_INIT/DAT after checking, whether all cases of Member RDKEY indeed exactly correspond to the cases in your license key. 4.7 Application examples In addition to the dialog system RVSDIA you can work with rvs via the batch interface and the C programme interface (or the interface based on it RVSEXEC). The following examples describe how to use the batch interface Routing It is possible to send files via a net of rvs stations determining the exact route of the file from station table to station table. For example, you can send a file via an ISDN net to a rvs station which forwards it using a SNA net. There is a sample ROU station in the station table (RVS_INIT/DAT(RDSTAT)). Files sent to ROU are forwarded to the neighbour node RSX (SIDNEIGHB=RSX). There must be a station entry for the ROU station in the station table of RSX Provision of files (mailbox mode) For some applications it is required, that files are not immediately sent, but are kept ready to be called. On demand, the partner station establishes a connection and calls the prepared files. In this case rvs functions like a mailbox emptied on demand. The partner pays the connection fees. Running rvs in mailbox mode is indispensable, when the partner cannot be called due to security measures. The mailbox mode requires, that the rvs parameter is set to MAXSENDERS=0 (no send tasks are started). Change the parameter via the operator console, end and restart the monitor. If afterwards you want to send a prepared file, you can use the ACTIVATE command as an operator or a batch command. 106

107 Configuration of AS/400 Systems There is the option to define the just described mailbox mode for particular stations. This is the case, when you need the mailbox mode for some partners, but active communication with other partners. In order to realise this option, set AUTODIAL=N in the station table entry of the particular station. Example: NK SID=RSX FTP=O PROTOCOL=X PRIORITY=10 AUTODIAL=N Although the value of MAXSENDERS is higher than 0, no connection to station RSX can be established actively. rvs interprets this definition, as if MAXSENDERS=0, but only for this station The STATISTICS Parameter For the case that you need a quick overview of the completed transfers you can use the standard LOG file, which rvs generates for all successful transferred files. You can handle the output in this file by means of the STATISTICS parameter. The Statistics LOG file is situated in the RVS_DB/LOG file and is called RLSTAT. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 107

108 Operator Manual 5 rvs Monitor for AS/400 This chapter contains the description how to start and stop the rvs Monitor for AS/400 systems as well as how to set parameters and how to use rvs Monitor commands. 5.1 Start rvs400 Monitor Please read chapter "Get a license for AS/400" carefully before starting the rvs Monitor. After the rvs database has been successfully initialised, start the subsystem QRVS. STRSBS SBSD(QGPL/QRVS) All background processes run in the subsystem QRVS. You must start the subsystem QRVS before starting the Monitor, because the job queue is connected to QRVS. When the subsystem has started, call the main menu (WRKRVS) of rvs400. Choose option 4 rvs monitor. That is the way to go to the start menu of the monitor. Confirm by Y, to induce the execution of commands already defined in the Monitor initialisation file at the start of the Monitor (see also chapter "Monitor Initial File for AS/400"). The rvs400 Monitor starts. Even if you leave the menu and log out of the system, the Monitor continues to run. It starts other processes. Note: WRKACTJOB SBS(QRVS) displays the processes in the subsystem QRVS. It is necessary to stop the Monitor (see section "Stop rvs400 Monitor"), before ending the QRVS subsystem or executing PWRDWNSYS on your machine. Otherwise you may face irreversible damages of the rvs database. 108

109 rvs Monitor for AS/ Stop rvs400 Monitor Call the programme RVSSTOP to stop the rvs400 Monitor: CALL RVS_SYSTEM/RVSSTOP. Another possibility ist to use the rvs400 Operator Console. Enter ==> STOP in the command line prompt (see also section "Operator Console and Commands") 5.3 Monitor Initial File for AS/400 The member RDMINI in the file RVS_INIT/DAT (Monitor initialising file) contains definitions for the initialising of the Monitor, which are automatically executed at the start of the Monitor. They are not executed, if the Monitor is called via the /i0 option, or if you have set the N option in the Monitor start menu (see also section "Start rvs400 Monitor"). You can edit this file according to your needs. You can aplly there all operator commands. For further information see section "Operator Console and Commands". Use any editor to generate the initialization file. Please, follow these rules, when creating an initialization file: Any operator command may be specified. Each command must be contained in a separate, single line. Empty lines are ignored (so you can optically separate groups of commands). Lines starting with an asterisk (*) in column 1 are ignored (so feel free to enter comments or sample commands). Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 109

110 Operator Manual Sample Initialization File A file that directs the Monitor to clean up the database by deleting all entries that completed more than three days ago; and makes sure that all line tracing is turned off, might look like this: *Sample Monitor initialization file *(this is another comment line, followed by an empty line) cleanup days=3 ss=yes *turn all line tracing off setparm sp odtracelvl=0 litracelvl=0 By default, the installation process stores a sample initialisation file with a commented description of all commands and parameters in the Member RDMINI of the file RVS_INIT/DAT. 110

111 Configuration of UNIX Systems IV. UNIX In this part of the manual the configuration process under UNIX systems as well as the rvs Monitor for UNIX is described. Which UNIX systems are supported, is described in paragraph "Short Description of the System". The differences with the configuration, which due to the different UNIX systems result, are explicitly characterized. After you have installed the rvsx system, you must adapt rvsx to your request. Which possibilities of the configuration are available and how you can execute these, is explained in the following chapters. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 111

112 Operator Manual 6 Configuration of UNIX Systems This section describes how to customize stationtable and related tables for UNIX as well as which privileges you can choose for rvs and how the network configuration and other basic configuration issues can be defined. 6.1 Customizing Stationtable and Related Tables for UNIX You need an rvs entry in the Station table for each partner station you want to communicate with. The file $RVSPATH 1 /rdstat.dat for UNIX contains a sample definition file for the stationtable and its related database tables that define the characteristics of the local station and of the other nodes you want to communicate with. Change this file according to your needs using an editor. This file will be used as default stationtable input file when the rvs database is created. After you have installed rvs you will find a Station table containing sample entries for X.25/ISDN, TCP/IP and LU 6.2 communication. Lines starting with (*) are interpreted as comments. In general, the fields are case sensitive. When rdstat.dat is read, all field names and all those value fields that are not enclosed in simple quotes ( ) or double quotes (" ") are converted to upper case; e.g. LUNAME=MYSTAT and luname=mystat are equivalent and different from both LUNAME="Mystat" and LUNAME='mystat'. 1 see chapter "Representation means" for the detailed description of $RVSPATH 112

113 Configuration of UNIX Systems Stations are identified and managed by Station IDs (SID) consisting of three characters. Each entry in the Station table begins with a two characters table name. Line continuations are signalled by (+).The significance of the system tables is described in the following sections. Next you are presented with a sample Station table: ******************************************************** **************** * Define STATION-TABLE (ST), ROUTING-TABLE (RT), NACHBARKNOTEN (NK), * * ODETTE-PARAMETERS (OP), APPC/LU62-PARAMETERS (LU) * * X.25/ISDN-PARAMETERS (XP) * ******************************************************** **************** * * local station ST SID=LOC NETID=??LOC?? STATNAME="local station" RT SIDDEST=LOC SIDNEIGHB=LOC PRIORITY=1 NK SID=LOC FTP=O PROTOCOL=X PRIORITY=10 OP SID=LOC ODETTEID='my Odette ID' LU SID=LOC LUNAME=XVWGGU01 NETID=VWAG TPNAME=RVSRCV USERID="" + PASSWORD="" MODE=VWG6RV10 SECURITY=0 + SYNCLEVEL=NONE TYPE=MAPPED XP SID=LOC N=1 LINK=RVSLINEIN XADDRESS= TIMEOUT=30 XP SID=LOC N=2 LINK=X25LINE XADDRESS= TIMEOUT=300 TC SID=LOC N=1 INADDR= PORT=3305 MAX_IN=5 TC SID=LOC N=2 INADDR= PORT=2110 MAX_IN=10 * Partner Station - X.25 native communication sample ST SID=RSX NETID=??RSX?? STATNAME='remote station 1' RT SIDDEST=RSX SIDNEIGHB=RSX PRIORITY=1 NK SID=RSX FTP=O PROTOCOL=X PRIORITY=10 OP SID=RSX ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX XP SID=RSX LINK=X25LINE XADDRESS= TIMEOUT=300 * Partner Station - ISDN communication sample ST SID=RSI NETID=??RSI?? STATNAME='remote station 2' RT SIDDEST=RSI SIDNEIGHB=RSI PRIORITY=1 NK SID=RSI FTP=O PROTOCOL=X PRIORITY=10 OP SID=RSI ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX XP SID=RSI LINK=RVSLINERSI XADDRESS= TIMEOUT=30 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 113

114 Operator Manual * Partner Station - SNA-LU6.2 communication sample ST SID=RSL NETID=??RSL?? STATNAME='remote station 3' RT SIDDEST=RSL SIDNEIGHB=RSL PRIORITY=1 NK SID=RSL FTP=O PROTOCOL=L PRIORITY=10 OP SID=RSL ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX LU SID=RSL LUNAME=LU62RSL NETID=VWAG TPNAME=RVSRCV USERID="" + PASSWORD="" MODE=VWG6RV10 SECURITY=0 + SYNCLEVEL=NONE TYPE=MAPPED * Partner Station - TCP/IP communication sample ST SID=RST NETID=??RST?? STATNAME='remote station 2' RT SIDDEST=RST SIDNEIGHB=RSTPRIORITY=1 NK SID=RST FTP=O PROTOCOL=T PRIORITY=10 OP SID=RST ODETTEID='my partners Odette ID' PSWFROM=XXX PSWTO=XXX TC SID=RST INADDR= PORT=3305 * ROU (Routing sample: send file to station ROU via station RSX) * ("via station" is defined in SIDNEIGB) * (RSX must have a partner with Odette-ID of ROU) * ST SID=ROU NETID=?ROU? STATNAME='example for routing via RSX' RT SIDDEST=ROU SIDNEIGHB=RSX PRIORITY=1 OP SID=ROU ODETTEID='OROU' PSWFROM=aaa PSWTO=aaa The different operation systems use the same Station tables, differentiated only by the parameter LINK, which depends on the operation system. This parameter specifies the name of the used line definition for AS/400. For Windows NT and UNIX the parameter is pre-set in rvs. For further information on the LINK parameter see section "X.25 native Communications XP". The Station table is read automatically, when the database is initialised. Later changes in the Station table become effective only after deleting or re-initialising the rvs database. Alternatively, you can type the command modst in the operator interface (see section "Operator Console and Commands"). Note: Please observe, that the modst command adds new stations or changes the present ones. If you want to delete stations, you can use the command delst sid=... The related tables contain the information listed in the following sections. 114

115 Configuration of UNIX Systems Identification of rvs Nodes In the stationtables, there are several parameters that identify rvs nodes: SID This is a locally unique station ID which must consist of up to sixteen characters. This is a strictly local definition; remote stations do not have access to these names; they only know the ODETTE-IDs. When choosing station IDs, keep in mind that these IDs will have to be used in all SendEntries (SE) and ResidentEntries (RE) to identify the target and the source of the transmission, respectively. ST.NETID This parameter is not used in current version! NETID in database table ST is the unique identification of a table within the entire rvs network to which the station belongs. It is used to identify recipients in distribution lists. OP.ODETTEID ODETTE ID in database table OP is a worldwide unique identification of all nodes that use the ODETTE File Transfer Protocol (OFTP). This 25 character name consists of the letter O, an 18 character organization identifier that is provided by the ODETTE codification group, and a 6 character computer subaddress that is administrated by each organization. If you communicate within your own closed network only, the ODETTE ID may be freely chosen as long as it remains unique in your network. In Germany, to apply for a ODETTE ID please contact : Verband der Automobilindustrie e.v. ( VDA ) Abt. Logistik Postfach Frankfurt Tel.: Get the complete description of OFTP from Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 115

116 Operator Manual StationTable ST This system table contains information about your own station as well as information about all nodes that can be reached from the local station (either directly or indirectly, including the local station itself). Table ST: SID NETID STATNAME PHONE Station ID; this name is unique within the local installation, only. Unique ID in the entire rvs network (see section 6.1.1"Identification of rvs Nodes" above) Descriptive name of station This text will be displayed when a list of stations is requested in the rvs dialog interface. Phone number of contact person at SID. This entry is a comment (optional) RoutingTable RT This system table defines for each rvs station through which neighbor(s) it can be reached. If more than one neighbor could be used, the routes should have different priorities; the one with the highest priority at the time the SK command is created will be used. It is the responsibility of network administration to avoid cycles that do not include the intended destination. Be especially careful when defining alternate paths to direct neighbors because others may think you are the proper transit station, since you are directly connected to it! The routing table must include an entry for your local station. Normally, the local station will be its own neighbor. Table RT: SIDDEST SIDNEIGHB PRIORITY Station ID of destination Station ID of neighbor that offers a path to the destination Determines which path is selected (the smaller the numerical value, the higher the priority, i. e. PR_HIGH < pr < PR_LOW). Not yet supported. 116

117 Configuration of UNIX Systems Neighbour Node (NachbarKnoten) NK This system table contains detailed information how (and when) other nodes can be reached. Table NK: SID PROTOCOL FTP AUTODIAL DELAY PSESSIONS Station ID of neighbor Line protocol Possible values: T TCP/IP ( ODETTE Standard ) X X.25 native / X.25 over ISDN (ODETTE Standard) L LU 6.2 R TCP/IP (rvs internal only for UNIX) Default: T File Transfer Protocol: O ODETTE Default: O Determines whether rvs automatically dials out if a data set is to be sent. Y a sender task will be started, as soon as a send request is available. N no sender task will be initiated, even when a send request is available. The queued data sets will be sent as soon as the partner establishes the connection, or an activate sid=xxx command for this partner is submitted from rvs Console. Default: Y Time (in seconds) that rvs should wait between connection attempts to this station. Default: 0 Maximum parallel sessions to be started to this partner. A value of -1 uses the global parameter MAXSESSIONS. Default: -1, use the global value from parameter MAXSENDERS. The overall number of parallel sessions is limited by MAXSESSIONS. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 117

118 Operator Manual PRIORITY Determines which combination of FTP and PROTOCOL is selected (the smaller the numerical value, the higher the priority, i. e. PR_HIGH pr PR_LOW) ODETTE Parameters OP This system table contains ODETTE related information about all nodes (not just the neighboring ones!) that can be reached from the local station using this File Transfer Protocol. Valid passwords are needed for neighboring nodes only. Table OP: SID ODETTEID PSWFROM Station ID As defined by ODETTE protocol (see section 6.1.1) Password that we are expecting this neighbor to send to us PSWTO Password that we are sending to this neighbor These ODETTE passwords are always exchanged and checked for neighboring nodes, independent of definitions for communication security as defined for LU 6.2. SENDBLOCKS Number of blocks to be sent before a checkpoint is reached. Use high values for "noiseless" connections to increase performance and low values for "noisy" connections. Default: 0, use the value from global parameter SENDBLOCKS 118

119 Configuration of UNIX Systems RECVBLOCKS Number of blocks to be received before a checkpoint is reached. Use high values for "noiseless" connections to increase performance and low values for "noisy" connections. Default: 0, use the value from global parameter RECVBLOCKS OEXBUF ODETTE exchange buffer size in bytes Default: 0, use the value from global parameter OEXBUF OCREVAL CODEIN CODEOUT USERFIELD RETRY ODETTE FTP windowsize, number of buffers to be sent before waiting for a response Default: 0, use the value from global parameter OCREVAL For codetranslation code of the local host (not yet implemented) For codetranslation code of the remote host (not yet implemented) SPECLOG: Force OFTP special logic. NOT necessary under normal conditions; if a partner requests special logic, rvs as a responder always answers with special logic. If USERFIELD is set to SPECLOG, rvs as an initiator tries to establish the OFTP special logic. That means the OFTP packet SSID contains SSIDSPEC=Y. If the partner (responder) answers with SSIDSPEC=Y, the following packets are transmitted and received with a leading STX character, a block sequence character, the data and two trailing checksum characters. (Not yet implemented) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 119

120 Operator Manual VDSNCHAR EERP_IN EERP_OUT Range of allowable charactersto be transferred within an ODETTE transmission: ALL: no restrictions OFTPUNIX: all capital letters, digits and the special characters. - UNIX: all letters, digits and the special characters # _ - +. ODETTE: all capital letters, digits and the special characters () -. / & CHECK_RE: same as ALL, but it is necessary that a RE exists default: ALL Wait for a receipt from the partner NEVER partner does not send EERP, so a send request ends with the correct transmission without waiting for the receipt NORMAL wait for receipt, end send request when receiving receipt Default: NORMAL Handling for sending a receipt NEVER partner does not expect EERP, so don't create a receipt IMMEDIATE create a receipt and start a session, if no session is available NORMAL create a receipt, but wait for a session to transmit (suggested) Default: IMMEDIATE 120

121 Configuration of UNIX Systems LU 6.2 parameters LU (only AIX, HP-UX and SINIX) This system table contains LU 6.2 related information about the own local node or all neighboring nodes that can be reached from the local station using this protocol. Table LU: SID PROFILE (only AIX) LUNAME Station ID; this name must be unique in the local installation. This is a required parameter. LU 6.2 Partner Profile name. This is a required parameter. This is the name of the LU6.2 Partner Profile and LU6.2 Side Information Profile in the SNA/6000 database. The name rvscp is default in the sample stationtable and in the sample LU6.2 profile (file s_server.lis). LU name of remote host. Default: one blank. AIX: This field has no effect and is only for your documentation. It can be left empty. The LU name has to be defined in the SNA/6000 profile. SINIX: For communication with rvsmvs, this is the VTAM APPL Macro definition for the XRLU defined in TRANSIT. HP-UX: This is a required parameter which can be defined in rvs. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 121

122 Operator Manual TPNAME Name of remote transaction processing program. AIX: This is an optional parameter. If this field is left empty, SNA/6000 uses the first name of the Remote Transaction Program List (RTPN list). Otherwise, the TPNAME must match the TP name of your partner station. For HP-UX and SINIX is this a required parameter. For your local station, this name must match the invocable TP name that the remote stations are calling (with RVSRCV as default). rvs on an MVS-host (rvsmvs), uses RVSOFTP instead as its local TP name. If you intend to communicate with an rvsmvs make sure the host is calling you with TP name RVSRCV and you call it with RVSOFTP. The following parameters are relevant only for HP-UX and SINIX systems USERID User ID to be used with remote program Default: one blank 122

123 Configuration of UNIX Systems PASSWORD Password needed to start remote program Default: one blank The required values for USERID and PASSWORD depend upon your communication partner's system and whether or not secure communication has been agreed upon. If your communication partner is another UNIX node, turn communication security off on both sides when defining a Partner LU Profile. Sending: USERID and PASSWORD from your LU entry for the remote node are those that your neighbor defined in his list of User Profiles (outside of the Communication Manager). Receiving: Your neighbor must enter those values for USERID and PASSWORD in his LU entry for your station that you defined in your list of User Profiles (outside of the Communication Manager). If your communication partner is an AS/400 node, turn communication security on when defining a Partner LU Profile. Sending: USERID and PASSWORD should be set to empty strings USERID="" PASSWORD=""and the respective device at the AS/400 should be defined, so that it will start the receiver under a default user name and does not require a password. Receiving: Your neighbor must enter those values for USERID and PASSWORD in his LU entry for your station that you defined in your list of Dialog Security Profiles (within the Communication Manager). Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 123

124 Operator Manual MODE SECURITY SNA session mode (one priority only) Default: one blank For communication with rvsmvs, this is the name of the VTAM Modetable Entry defined in the NCP LU Macro, with the DLOGMODE parameter. We strongly suggest you select a mode name that is min. eight characters long, because some implementations of LU 6.2 do not pad shorter names properly! If this happens, the remote side may not recognize the mode name and refuse to establish a session. specifies, whether password and user ID are expected: 2 (none) no user ID/password exchanged. This is the required value, if you communicate with rvsmvs. 3 (user security) userid/password must be specified explicitly Default: 0 SYNCLEVEL APPC synchronisation level NONE no confirmation CONFIRM confirmation may be requested Default: NONE TYPE APPC conversation type BASIC basic conversation (not supported, at this time) MAPPED mapped conversation Default: MAPPED 124

125 Configuration of UNIX Systems Only SINIX systems require additional SNA related information. These parameters are stored in system table LX (for LU 6.2 extensions). Table LX: SID PUNAME Station ID; this name is unique in the local installation, only. This is a required parameter. PU name of your physical unit as specified in VTAM/NCP PU statement and TRANSIT XPUconfiguration. See also section 6.3. This is a required parameter X.25 native Communications XP XP contains data of X.25-native communications. Table XP: SID Station ID, defining local or remote station for which this entry is defined. N Key, to distinguish between different XP Blocks (e.g. to accept calls from different interfaces). Only supported for incoming calls. Use numbers beginning with 1. XADDRESS DTE address, character string of maximum 15 decimal digits. For the local station, this is the own X.25 DTE address; for a remote station, it is the remote DTE address. Default: empty string TIMEOUT Time period in seconds after which a connection is automatically terminated, if the partner station does not answer. Default: 60 (seconds) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 125

126 Operator Manual LINK ISDNNO FACILITIES Link name, string of characters. X.25 adapter name. Standard for AIX is x25s0 (IBM X.25 Coprocessor). Check your adapter name with lsdev -C -H -t x25* If ISDN router BinTec BRICK is used: The link name for BRICK routers must be RCAPI1 (1 stands for the control field in the ISDN request CAPI2_CONNECT_REQ and can be changed, e.g. to vary the BRICK board number). See Chapter "" for more information. Only AIX: If an ISDN board "diehl SCOM/2" is used together with "netisdn" software, the link name must be NETISDN0. If more than one ISDN board is used, a XP block for every board is required for the local stationtable entry. The second XP block must contain NETISDN1 etc. ISDN number of partner, string of characters. Required if ISDN connection is used (LINK=NETISDN0 or RCAPI1). The sender will setup the ISDN connection to this partner, and then establish the X.25 protocol on this connection. X.28 PAD profile string: If FACILITIES contains a string beginning with PAD, then the contents of this environment variable will be read and sent as a X.28 PAD profile string before OFTP SSRM packet. Example: If FACILITIES=PADSTRING1 and the environment variable PADSTRING1 contains D, then this 4 bytes will be sent as a PAD profile string before SSRM is sent. 126

127 Configuration of UNIX Systems USERDATA (only HP-UX and SINIX) Call user data, string of maximum 256 hex characters (128 bytes); optional; default: empty string (no data) Call user data are appended to the outgoing call packet and might be used by the remote installation as control information, especially for routing to the target application. The first byte of the call user data field is commonly interpreted as "Protocol Identifier", PID, where some values are reserved, for example: X'C3' for SNA QLLC, X'C4' for SNA ELLC, X'EE' for TCP/IP. Therefore, care must be taken when using call user data and there must be a mutual agreement with your partner station. Under normal circumstances, the call user data field is not required. For incoming calls you can specify which protocol ID you want to accept with rvs, e.g. to distinguish between different partners. You can define 1 PID for each XP-Block. USERDATA is represented in hex, so for "RVS" you have to code "525653". Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 127

128 Operator Manual ALIAS RECV_ALIAS Optional IP address for ISDN router BinTec BRICK, format "nnn.nnn.nnn.nnn". When rvs connects to a station with LINK=RCAPI1 ISDNNO=nnn ALIAS=nnn.nnn.nnn.nnn, it establishes a TCP/IP connection to this IP address. If ALIAS is empty, rvs reads the IP address from the UNIX environment variable CAPI_HOST. So, if you leave ALIAS empty, then define the variable CAPI_HOST in the rvs profile (e.g. $RVSPATH/.profile, see chapter "Representation means" for the detailed description of $RVSPATH). Defining ALIAS is especially useful if incoming calls originate from more than one BRICK router. Additional for SINIX: string of characters. Provides a logical link to the CMX/CCP-WAN- X25 services. For the local (own) station, this name must match with entry "name part[5]" in the TSNX definition for a local end system (Suggestion: X25_RVS_LOC). For the remote station, this name must match with entry "name part[5]" in the TSNX definition for a remote end system (Suggestion: X25_RVS_RMT). string of characters. Provides a logical link for the rvs receiver. Additional for AIX: It is only necessary for the local (own) station. This name has to match with an entry in the AIX X.25 routing table (see AIX program "xroute"). The default is IBMSAMP. Sometimes another application uses the entry IBMSAMP, so you have to define another entry. Additional for SINIX: It is only necessary for the local (own) station. This name must match with entry "name part[5]" in the TSNX definition for a local end system (Suggestion: X25_RVS_RCV). See also CCP-WAN definitions. 128

129 Configuration of UNIX Systems Receiving via X.25 and ISDN: If you want to be able to receive files from more than one partner at the same time, you have to prestart an X.25 receiver programs for each channel: 1. Edit the monitor initialisation file ($RVSPATH/rdmini.dat) and set the rvs parameter MAXX25RCV to the number of receivers; 2. Edit the stationtable file ($RVSPATH/rdstat.dat) and add an X.25-parameter block ("XP") for each receiver to the local entry. Only for AIX: Each receiver must have a different RECV_ALIAS name. See " Defining the X.25 Network for AIX" for more information. 3. Only for AIX: use program xroute to add routing entries. Example for the local station definition (Receiving via ISDN BRICK router, listening on both ISDN channels, listen only for calls to our ISDN number with last digit=7): XP SID=LOC N=1 LINK="RCAPI1" ISDNNO="7" XP SID=LOC N=2 LINK="RCAPI1" ISDNNO="7" Example for the remote station definition (call via BRICK ISDN router to ISDN no. 4711, optional X.25 address 20): XP SID=R11 LINK="RCAPI1" ISDNNO=4711 XADDRESS=20 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 129

130 Operator Manual TCP/IP parameters TC This system table contains TCP/IP related information about the own local node or all neighboring nodes that can be reached from the local station using the protocols T (ODETTE standard) and R (rvs internal TCP/IP). For installation, please refer to chapter "Defining the TCP/IP Connection". Table TC: SID N PROTOCOL INADDR PORT MAX_IN MAX_OUT Station ID; this name is unique in the local installation, only. This is a required parameter. Key which distinguishes between different TC blocks (e.g. to accept calls from different ports). For OFTP using TCP/IP, set: N=1 If you want to use the old rvs internal TCP/IP, set: local station:n=0 remote station:n=0 Line protocol R TCP/IP (for rvsx only - old rvs internal TCP/IP) T TCP/IP (ODETTE standard) Internet address / IP address or hostname Format or rvsas1.gedas.de Port to connect to (for OFTP is suggested to use 3305) Max. number of concurrent incoming transfers using the same port (relevant only for the local station). Max. number of concurrent outgoing transfers using the same port (not yet implemented). 130

131 Configuration of UNIX Systems Example for the local station definition: TC SID=LOC PROTOCOL=T N=1 INADDR="" PORT=3305 Example for the remote station definition: TC SID=ABC PROTOCOL=T N=0 INADDR=xxx.xxx.xxx.xxx PORT=3305 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 131

132 Operator Manual 6.2 Choosing Privileges for rvsx In order to exploit the full functionality of rvs, it is necessary that the Monitor can read all user data to be transferred; the Monitor can write received data into a user s directory, if required; the user can read data from the directory $RVSPATH/usrdat/ (see chapter "Representation means" for the detailed description of $RVSPATH) where all files are stored that are not explicitly directed elsewhere by means of resident receive entries; the Monitor can execute user jobs on behalf of a user because of a resident receive entry; the user or application can place orders into the rvs database by means of the dialog, batch, or call interface. On the other hand, the security control under UNIX allows to define privileges and access rules only on a rather crude level. The two basic possibilities to run rvs, between which the customer has to choose, are described below Running rvs high-privileged The simplest way with respect to delivery of maximum functionality is to execute the rvs Monitor under a user ID with root privileges. There will be no problem for the Monitor to read and write files and to execute user jobs out of a resident receive entry. The disadvantage is the potential abuse of the root privilege by rvs users or the operator Running rvs low-privileged Using this mode, abuse of privileges is not possible. The disadvantage is that each rvs user explicitely has to grant reading access to files to be transmitted and jobs to be executed out of a resident receive entry. If the group permission level is not applicable, there is only the world level left, which then allows access by everyone. 132

133 Configuration of UNIX Systems 6.3 Defining the TCP/IP Connection rvsx supports OFTP communication via TCP/IP. OFTP TCP/IP can be used for highspeed LAN connections as well as for internet connections. The protocol OFTP TCP/IP is described in the internet documentation "RFC 2204". The recommended TCP/IP port is rvsx Configuration for TCP/IP Configure your rvsx: Customize your stationtable (edit the file $RVSPATH/init/rdstat.dat) and your monitor initialisation file ($RVSPATH/init/rdmini.dat): See Representation means" for the detailed description of $RVSPATH. Edit file rdstat.dat: Edit your own local station entry (in the default file, this is the station LOC). The TC line defines the TCP/IP receiver task. By default, leave the parameter INADDR empty. If you want to force rvsx to bind the TCP/IP listen socket on another IP address, you can set INADDR to this IP address. By default, rvsx listens on port 3305 (rvsx is able to handle multiple TCP/IP connections over the same port). Then define a partner STATION with a TC line and an IP address. Set INADDR to the IP address of your partner. Set PORT to the OFTP-TCP/IP port number of your partner (default: 3305). Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 133

134 Operator Manual Sample: ******************************************************************************************* *LOC (Definition of own local station) * (LINK=RCAPI1 ISDNNO="" means we accept all calls from BRICK) * ST SID=LOC NETID=LOC STATNAME='local rvs station' RT SIDDEST=LOC SIDNEIGHB=LOC PRIORITY=1 NK SID=LOC FTP=O PROTOCOL=T PRIORITY=10 OP SID=LOC ODETTEID='O my ODETTE ID' + PSWFROM=AAA PSWTO=AAA TC SID=LOC PROTOCOL=T N=1 INADDR="" PORT=3305 ******************************************************************************************* *R11 (Definition of a partner station) * ST SID=R11 NETID=R11 STATNAME= 'OFTP-TCPIP partner' RT SIDDEST=R11 SIDNEIGHB=R11 PRIORITY=1 NK SID=R11 FTP=O PROTOCOL=X PRIORITY=10 OP SID=R11 ODETTEID='O VW R11' PSWFROM=AAA PSWTO=AAA TC SID=R11 PROTOCOL=T N=0 INADDR= xxx.xxx.xxx.xx x PORT=3305 ******************************************************************************************* 134

135 Configuration of UNIX Systems E.g., edit /home/rvs/init/rdmini.dat. Change: setparm TCPIPRCV=1 This will start one TCP/IP receiver task. If you want to listen to more then one port, add additional TC lines to your local station definition and increase the parameter TCPIPRCV. Then modify the rvsx database. Start the Operator Console (rvscns), and type modst The Operator Console should display the line " I: <OK_CMD_DONE> [RVSCNS] 'modst' done. ". Now you should be able to activate your partner with the operator command "ACT SID=xxx", for example: act sid=r11 The Operator Console should display the line I: <OK_ACTIVATE> connect to station R11... I: <CONNECTED> Connection to station R11 established Problem Solving for TCP/IP First, test the connection to your partner. A ping command should be successful: ping xxx.xxx.xxx.xxx Next, ensure that your partner station is listening on the defined TCP/IP port. For example, type telnet xxx.xxx.xxx.xxx 3305 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 135

136 Operator Manual The partner should answer with the string "IODETTE FTP READY". Next, ensure that your own station is listening on the defined TCP/IP port. For example, type telnet own-ip-address 3305 Your rvs should answer with the string "IODETTE FTP READY". Next, you can check the rvsx TCP/IP listen socket with the command netstat -a You have to find a line like this: tcp 0 0 hostname LISTEN Be sure your partner connects to this hostname and port number. 136

137 Configuration of UNIX Systems 6.4 Defining the ISDN Network for BRICK Router rvsx supports OFTP ISDN Communication via an external ISDN router (BinTec BRICK). BRICK has a "Remote CAPI" interface. That means, any computer in your LAN addresses the BRICK router as if it is an internal ISDN board. A TCP/IP-based driver "tunnels" the ISDN packets to the BRICK router. The rvsx OFTP software module addresses a BRICK router anywhere in the LAN/WAN of your company. That means: 1. The OFTP system does not need an internal ISDN board 2. Several OFTP systems (and other ISDN applications) can share the same BRICK router 3. Several routers in your WAN can provide multiple dial-in ports (fail-safe configurations) BRICK is available for S0 (2-channel) or S2M (30-channel) ISDN. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 137

138 Operator Manual BRICK Router Installation Install the BinTec BRICK Router in your LAN as described in the BRICK manual. For more information, visit the BinTec WWW homepage at Login on BRICK (telnet) und and choose "setup". The following mask appears: BIANCA/BRICK-XS Setup Tool Licenses System LAN Interface: WAN Interface: IP ISDN Partner Configuration Management Exit CM-BNC/TP, Ethernet CM-1BRI, ISDN S0 Choose "IP", "Routing". Your UNIX system must be inserted in the routing table. Choose "License". Insert your BinTec BRICK license key. Choose "ISDN", "Incoming Call Answering". Be sure that the local ISDN numbers which are used here, are NOT used for rvs (Otherwise the BRICK may catch incoming calls which were intended for rvs ). 138

139 Configuration of UNIX Systems rvsx Configuration for BRICK Router Configure your rvsx: Define UNIX environment variables: Edit /etc/profile or $RVSPATH/.profile (see Representation means" for the detailed description of $RVSPATH). Insert your IP address: CAPI_HOST=xxx.xxx.xxx.xxx; export CAPI_HOST TRACE_HOST=xxx.xxx.xxx.xxx; export TRACE_HOST Now login again to activate settings. On your rvs system, type the UNIX command ping $CAPI_HOST It must be successful. Customize your stationtable (edit the file $RVSPATH/init/rdstat.dat) and your monitor initialisation file ($RVSPATH/init/rdmini.dat). Then create the rvs database and start rvsx: Edit file rdstat.dat. Edit your own local station entry (in the default file, this is the station LOC). The 2 XP lines in the sample define 2 receiver tasks for "Remote-CAPI" (RCAPI) access. The fields ISDNNO in your local XP lines define a "filter" for incoming calls. Incoming calls will be accepted only if the last digits of the calling address match this number (e.g. if you want to receive OFTP calls on number "123" and FAX calls on number "124", then set ISDNNO=3). Then define a partner station with a XP line and an ISDN number. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 139

140 Operator Manual Sample: ************************************************* *LOC * * (Definition of own local station) (LINK=RCAPI1 ISDNNO="" means we accept all calls from BRICK) ST SID=LOC NETID= LOC RT SIDDEST=LOC SIDNEIGHB= LOC STATNAME='local rvs station' PRIORITY=1 NK SID=LOC FTP=O PROTOCOL=X PRIORITY=10 OP SID=LOC ODETTEID='O my ODETTE ID' + PSWFROM=AAA PSWTO=AAA XP SID=LOC N=1 LINK=RCAPI1 ISDNNO="" XP SID=LOC N=2 LINK=RCAPI1 ISDNNO="" *********************************************************** *ZZZ * * (Definition of a partner station) (if you insert your ISDN number and your ODETTE ID, you can do a "loop test") ST SID=ZZZ NETID=ZZZ STATNAME= 'looptest via BRICK' RT SIDDEST=Z SIDNEIGHB=ZZZ PRIORITY=1 ZZ NK SID=ZZZ FTP=O PROTOCOL=X PRIORITY=10 OP SID=ZZZ ODETTEID='O my ODETTE ID' + PSWFROM=AAA PSWTO=AAA XP SID=ZZZ LINK= RCAPI1 ISDNNO= *********************************************************** 140

141 Configuration of UNIX Systems (You can define an additional X.25 call address or X.25 userdata field which may be needed by some partners; for example, define: ISDNNO=123 XADDRESS=20 USERDATA=C0). Edit $RVSPATH/init/rdmini.dat. Change: setparm MAXX25RCV=2 This will start 2 X.25/ISDN receiver tasks which will wait for incoming ISDN calls. (A basic-rate ISDN line has 2 B-channels). Then modify the rvs (rvscns), and type database. Start the Operator Console modst The Operator Console should display the line " I: <OK_CMD_DONE> [RVSCNS] 'modst' done. ". Now you should be able to activate your partner with the operator command act sid=zzz The Operator Console should display the line I: <OK_ACTIVATE> connect to station ZZZ... I: <CONNECTED> Connection to station ZZZ established. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 141

142 Operator Manual Problem Diagnosis for BRICK Router First, test the connection to BRICK. A ping command should be successful. CAPI_HOST You can analyse problems with the programs bricktrace and capitrace, which produce a linetrace output. BinTec also supplies a Windows95 based trace tool called "BRICKware DIME tools". A simple tool to test your ISDN port is the program rcapitest. Just type for example rcapitest receive $CAPI_HOST & rcapitest send $CAPI_HOST isdnno where "isdnno" means the BRICK ISDN number. The "send" task will then communicate with the "receive" task. Next, you can create rvs (rvscns), type log files. In the Operator Console setparm LITRACELVL=4 act sid=xxx rvs will now create log files (rltr.log) in the temp directory which log the BRICK connection commands. 142

143 Configuration of UNIX Systems 6.5 Defining the ISDN Network for netisdn Base Software (only AIX Systems) This chapter describes the configuration required to run rvs with a diehl SCOM/2 board and netisdn software (from netcs GmbH). It is also possible to use the diehl S 2M ISDN board Adapter Installation for AIX Preparation (as described in "netcs netisdn Installation Manual, Software Installation IBM AIX"): 1. Power off, insert SCOM/2 board in any slot, insert ISDN cable 2. Power on, login as root 3. Install the netisdn software from diskette rvsx Configuration for AIX Install rvsx as described. During the installation process, you will be asked: Do you use network CAPI (e.g. BinTec Brick) for ISDN communication? Type Y (Yes). Customize your stationtable (edit the file /home/rvs/init/rdstat.dat) and your monitor initialisation file (/home/rvs/init/rdmini.dat). Then create the rvsx database and start rvsx: Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 143

144 Operator Manual Edit /home/rvs/init/rdstat.dat. The first entry describes your own local station with the Station ID (SID), default value is LOC. Change 2 parameters: OP SID=LOC ODETTEID='your_ODETTE_ID' + XP SID=LOC N=1 LINK="NETISDN0" ISDNNO=your_isdn_number Then change the entry of your partner (for example, SID "R40"): NK SID=R40 FTP=O PROTOCOL=X PRIORITY=10 OP SID=R40 ODETTEID='ODETTE_ID_of_partner' + PSWFROM=partner_password PSWTO=your_password XP SID=R40 LINK="NETISDN0" ISDNNO=partner_isdn_number Edit /home/rvs/init/rdmini.dat. Change: setparm MAXX25RCV=1 This will start 1 X.25/ISDN receiver task which waits for incoming ISDN calls. For one ISDN adapter, you can start up to 2 receiver tasks (because one ISDN line has 2 B channels). For one S 2M ISDN adapter you can start up to 30 receivers. Then modify the rvsx database. Start the operator console (rvscns), and type modst dsn="/home/rvs/init/rdstat.dat" The Operator Console should display the line " I: <OK_CMD_DONE> [RVSCNS] 'modst' done. ". Now you should be able to activate your partner with the operator command act sid=r40 144

145 Configuration of UNIX Systems The Operator Console should display the line I: <OK_ACTIVATE> connect to station R40... I: <CONNECTED> Connection to station R40 established. If an ISDN error occurs, read the next section. If nothing happens, probably a library is not properly installed (/usr/lib/libsna.a and /usr/lib/libx25s.a). To check this, leave rvscns and type rvscom /a R40. This may result in the message Could not load library libsna.a. You either can install the AIX SNA and/or X.25 package or use a different version of the rvscom Diagnosis for AIX If an ISDN error occurs, first test the ISDN board installation with the program rvsnetisdn. Log in as root and type: rvsnetisdn You will see this menue: RVS netisdn utilities 1. Start netisdn 2. Stop netisdn 3. Show netisdn status 4. Show netisdn statistics 5. Start monitoring ISDN line 6. Show ISDN monitor output Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 145

146 Operator Manual 7. Call myself (ISDN loop test) 8. Allow remote login 9. Allow remote copy 10. Remote login 11. Remote copy q. Quit First, check the status of netisdn (topic 3). The status must be "RUNNING". Otherwise, start netisdn (topic 1). If you use EuroISDN (ETSI), the message has to be Loading <TE_ETSI.SY>... netisdn started... To test the ISDN connection, call your own number (topic 7). The program will send data via one ISDN B channel and will get it back via the second B channel. The test must end with the message "ISDNTEST: OK!". With this topic, you can test the connection to any other OFTP ISDN partner, too. Just type in the ISDN number of your partner. The topic "8 Allow remote login" is useful to let your rvsx supporter log into your system. The topic "11 Remote copy" is a simple filecopy function via ISDN, but it only works on systems with netisdn (UNIX) or "acopy" servers (MS DOS). 146

147 Configuration of UNIX Systems 6.6 Defining the ISDN Network for internal ISDN board (only SINIX Systems) The configuration required to run rvs with the internal ISDN communication controller is described in the "Communications Manager SINIX V5.1 (CMX) Operation and Administration (SINIX, Reliant UNIX)": To use OFTP over ISDN for the internal ISDN communication controller you have to do the following steps: 1. Configure the ISDN configuration (KOGS) in CCP / CMX 2. Configure TNS to use X.25 over ISDN 3. Configure FSS 4. Configure rvsx (SINIX) Configuring TNS for SINIX To configure the connection between rvsx (SINIX) and the ISDN communication controller you have to define the following TNS entrys : 1. RVS_LOCAL for your local identification 2. For each partner RVS "partnerid" The definitions for TNS must match the definitions in rvsx (SINIX) and your FSS configuration. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 147

148 Operator Manual Configuring rvsx (SINIX) rdstat.dat for ISDN communication Customize stationtables, as described in chapter 6 on page 112. For your own station you must add a XP definition as followed: XP SID="own SID" N=1 XADDRESS="own ISDN no" RECV_ALIAS=ISDN_RCV ALIAS=RVS_LOCAL For each partner you must add a XP definition as followed : XP SID="partner SID" N=1 XADDRESS=USE_TNS RECV_ALIAS=RVS"partners SID"_ALIAS=RVS"partners SID" use command modst from rvs console to update your rvs station configuration. use act "partner SID" from rvs console to test connectivity. 148

149 Configuration of UNIX Systems 6.7 Defining the X.25 Network for AIX This chapter describes the configuration required to run rvs with X.25 native communication. OFTP allows connections via a X.25 network like Datex-P or TRANSPAC Adapter Installation for AIX Preparation: 1. Read the "AIXLink/X.25 Guide and Reference" 2. Install X.25 coprocessor board 3. Login as root 4. Install AIXLink/X.25 system software 5. With "smit" change network parameters (such as Network User Address) 6. Connect system and X.25 modem/router rvsx Configuration for AIX Customize your stationtable (edit the file $RVSPATH/init/rdstat.dat) and your monitor initialisation file ($RVSPATH/init/rdmini.dat): See chapter "Representation means" for the detailed description of $RVSPATH. Edit file rdstat.dat The first entry describes your own local station with the Station ID (SID) "LOC". The "XP" line defines the X.25 receiver task. The parameter RECV_ALIAS defines the entry for the AIX X.25 routing table (see below). The parameter XADDRESS defines your own X.25 network address. Then define a partner station with a "XP" line, the XADDRESS of your partner, and an optional USERDATA field. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 149

150 Operator Manual Sample: ************************************************************* * LOC (Definition of own local station) * ST SID=LOC NETID=LOC STATNAME='local rvs station' RT SIDDEST=LOC SIDNEIGHB=LOC PRIORITY=1 NK SID=LOC FTP=O PROTOCOL=X PRIORITY=10 OP SID=LOC ODETTEID='O my ODETTE ID' + PSWFROM=AAA PSWTO=AAA XP SID=LOC N=1 LINK="sx25a0" RECV_ALIAS=IBMSAMP XADDRESS=" " ************************************************************* * R11 (Definition of a partner station) * ST SID=R11 NETID=R11 STATNAME='OFTP X.25 partner' RT SIDDEST=R11 SIDNEIGHB=R11 PRIORITY=1 NK SID=R11 FTP=O PROTOCOL=X PRIORITY=10 OP SID=R11 ODETTEID='O VW R11' + PSWFROM=AAA PSWTO=AAA XP SID=R11 LINK="sx25a0" XADDRESS= ************************************************* Edit $RVSPATH/init/rdmini.dat Change: setparm MAXX25RCV=1 This will start one X.25 receiver task. If you want to listen on more then one X.25 SVC, add additional XP lines to your local station definition and increase the parameter MAXX25RCV. Then modify the rvs (rvscns), and type database. Start the Operator Console modst The Operator Console should display the line " I: <OK_CMD_DONE> [RVSCNS] 'modst' done. ". 150

151 Configuration of UNIX Systems X.25 Problem Diagnosis for AIX Before investigating any problem, ensure that X.25 communications are set up correctly. Read the "AIXLink/X.25 Guide and Reference". Use program lsx25 to list the X.25 configuration. Use xtalk for a simple send and/or receive test. Use xmon to view X.25 packets X.25 Routing Information for AIX For every incoming call, the operating system knows which application has to receive the call, because it holds a "routing table". The routing table contains "X.25 user data" filters, priorities and so on. You can change the routing table by using the program xroute. rvs uses the routing name IBMSAMP by default, so you don't have to change anything in the routing table. But, if you want to prestart more than one rvs receiver (to be able to get more than one data set at the same time), you need additional routing entries. For example, to prestart 3 receivers: 1. edit the monitor initialisation file ($RVSPATH/rdmini.dat and change the parameter MAXX25RCV to edit the stationtable file ($RVSPATH/rdstat.dat) and add 2 X.25-parameter blocks ("XP") to your local station entry (each RECV_ALIAS name must be different). 3. run program xroute and add 2 routing entries. Example: XP SID=LOC N=1 LINK="sx25a0" RECV_ALIAS=RVSA XADDRESS="394710" XP SID=LOC N=2 LINK="sx25a0" RECV_ALIAS=RVSB XADDRESS="394710" XP SID=LOC N=3 LINK="sx25a1" RECV_ALIAS=RVSC XADDRESS="394711" Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 151

152 Operator Manual 6.8 Defining the X.25 Network for SINIX The X.25 Network Definition for SINIX is described in the "Communications Manager SINIX V5.1 (CMX) Operation and Administration (SINIX, Reliant UNIX)", section "Configuration in expert mode" manual. You find this manual in the internet: rvsx Configuration for SINIX Customize your stationtable (edit the file $RVSPATH/init/rdstat.dat) and your monitor initialisation file ($RVSPATH/init/rdmini.dat). See chapter "Representation means" for the detailed description of $RVSPATH. Edit file rdstat.dat: By default the first entry describes your own local station with the Station ID (SID) "LOC". The following sample refers to your own station. Then modify the rvs (rvscns), and type database. Start the Operator Console modst The Operator Console should display the line " I: <OK_CMD_DONE> [RVSCNS] 'modst' done. " Tracing X.25 packet level for SINIX Under CMX, you can diagnose the connection in case of errors. You need good knowledge of X.25 packet structures. For complete information on CMX diagnostics, see "Communications Manager SINIX V5.1 (CMX) Operation and Administration (SINIX, Reliant UNIX)": 152

153 Configuration of UNIX Systems 6.9 Defining the X.25 Network for HP-UX This chapter describes a sample configuration with the necessary definitions required to run rvsx (HP-UX) with X.25 native communication Configuration of HP-UX for X.25 To run rvsx (HP-UX) with X.25, you must have installed X.25/9000 as described in "HP-UX Installing and Administering X.25/9000" In case of errors please refer to: "HP-UX Troubleshooting X.25/9000". Configure your own DTE the name of the interface (link) other parameters Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 153

154 Operator Manual A sample configuration is shown below. Please adopt this example to your own needs. # # X.25 Initialization File Created: Thu Aug 22 14:45: # # # Global Parameters # x.121 <own DTE Addr> x.121_packetaddr <own DTE Addr> device x25_0 name x25pgmaccess # # Level 2 Parameters # t t framesize 149 n2 20 l2window 7 # # Level 3 Parameters # networktype DTE_84 # # Circuit Table Definition # # LCI TYPE HOW MANY lci 1 svc 17 # # Flow Control, Throughput Class, Fast Select and Reverse Charge Settings # flowcontrol off thruputclass off fast_select_accept disabled reverse_charge disabled def_inpacketsize 128 def_outpacketsize 128 def_inwindow 2 def_outwindow 2 def_inthruputclass 11 def_outthruputclass 11 # # IP Parameters # ipaddress???.???.???.??? idletimer 600 holdtimer 300 mtu

155 Configuration of UNIX Systems rvsx Configuration for HP-UX Customize your stationtable (edit the file $RVSPATH/init/rdstat.dat) and your monitor initialisation file ($RVSPATH/init/rdmini.dat). See chapter "Representation means" for the detailed description of $RVSPATH. Edit file rdstat.dat: By default the first entry describes your own local station with the Station ID (SID) "LOC". The following sample refers to your own station. Then modify the rvs (rvscns), and type database. Start the Operator Console modst The Operator Console should display the line " I: <OK_CMD_DONE> [RVSCNS] 'modst' done. ". The "XP" line defines the X.25 receiver task. Sample : XP SID=LOC N=1 XADDRESS="*" USERDATA="" LINK="" Use XADDRESS LINK USERDATA for defining addressing options for the OFTP server. Refer to "Addressing options for servers" in the "HP-UX X.25/9000 Programmers Guide" to define addressing options. XADDRESS match X.121 Adress LINK match X.25/9000 Interface name USERDATA match Protocol ID Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 155

156 Operator Manual If you define USERDATA notice to use HEX codes. Edit $RVSPATH/init/rdmini.dat. Change: setparm MAXX25RCV=1 This will start the X.25 server task. Then define a partner station with a "XP" line as described below. Sample: XP SID=XXX N=1 XADDRESS=xxx USERDATA="" FACILITIES="" LINK="" Use XADDRESS LINK USERDATA FACILITIES for defining addressing options for your communication client. Refer to "Addressing options for clients" in the "HP-UX X.25/9000 Programmers Guide" to define addressing options. XADDRESS match X.121 Adress LINK match X.25/9000 Interface name USERDATA match Protocol ID FACILITIES match optional facilities If you define USERDATA or FACILITIES notice to use HEX codes. 156

157 Configuration of UNIX Systems 6.10 Defining the SNA Network for HP-UX This chapter describes a sample configuration with the necessary definitions. To run rvsx (HP-UX) with LU6.2, you must have installed SNAplus as described in "HP-UX SNAplus Installation Guide". Configure the SNAplusLink as described in "HP-UX SNAplusLink Administrator's Guide". Configure mode local LU remote LU local TP remote TP as described in "HP-UX SNAplusAPI Administrator's Guide". A example shows a running configuration. Please adapt this example to your own needs. ; ************************************************************************** ; SNAplus Binary to Text Configuration Utility ; Copyright (C) 1993 Hewlett-Packard Company ; Binary Configuration = /usr/lib/sna/com.cfg ; Security File = /usr/lib/sna/com.sec ; File version = ; ************************************************************************** Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 157

158 Operator Manual ; ************************************************************************** ; Diagnostics Record (Mandatory) ; ************************************************************************** [DIAGNOSTICS] connection = "" ; Name of network mgt connection UCF_user = "" ; User ID for UCF commands error_log = "/usr/lib/sna/sna.err" ; Error log file audit_log = "/usr/lib/sna/sna.aud" ; Audit log file audit_level = 10 ; Significant system events send_overfl = No ; Send RTM when response counter max send_end = No ; Send RTM at end of session stop_timer = screen ; Data first reaches the screen boundary_1 = 0.5 ; RTM histogram time boundaries boundary_2 = 1.0 boundary_3 = 2.0 boundary_4 = 5.0 pc_error_log = "sna.err" ; PC client error log file pc_audit_log = "sna.aud" ; PC client audit log file 158

159 Configuration of UNIX Systems ; ************************************************************************** ; Local Node Record ; ************************************************************************** [NODE] name = "GEDANODE" ; Local Node Name description = "NODE fuer Testinst." ; Description of Local Node network = "" ; Node Network Name ; ************************************************************************* APPC Local LU Record ; ************************************************************************** [APPC_LOCAL_LU] alias = "GEDASA01" ; LU Alias node = "GEDANODE" ; Local Node description = "Locale LU ; Text description of LU independent" net_name = "NETZ" ; LU Network Name LU_name = "GEDASA01" ; Name of LU LU_number = 0 ; LU Number session_lim = 40 ; Session Limit default_lu = No ; LU in pool of Default LUs local_use = No ; LU can be used locally partner_lu = "RVSCICST, 2" ; List of Partner LUs and Modes partner_lu = "RVSRVS6, 2" partner_lu = "RVSRVSG2, 2" partner_lu = "RVSR11L, 2" Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 159

160 Operator Manual ; ************************************************************************* ; SDLC Connection Record ; ************************************************************************** [SDLC_CONN] name = "GEDACONN" ; Name of connection node = "GEDANODE" ; Name of node description = "Connection fuer ; Description BZO-Wolfs" remote_end = host ; Remote end is host activation = initially ; Initially active XID_type = 3 ; Format 3 XID node_send = " " ; Node ID to send node_rcv = "" ; Node ID to receive control_point = "" ; Fully qualified control point name encoding = aaaa ; Encoding is aaaa full_duplex = No ; Full duplex data_rate = high; Data rate is high standby = Yes ; Standby dial_data = "" ; Dial data poll_address = 00 ; Poll address switch_timeout = 00 ; Time to dial number link = "GEDASDLC" ; link 160

161 Configuration of UNIX Systems ; ************************************************************************** ; APPC Mode Record ; ************************************************************************** [APPC_MODE] name = "GEDASV10" ; Mode name mode_id = 2 ; Unique Mode ID description = "APPC/LU6.2 ; Description parallel Sess." connection = "GEDACONN" ; Connection used by this mode priority = low ; Mode is Low Priority session_limit = 10 ; Mode Session Limit MCW = 5 ; Min Conwinner Sessions partner_mcw = 5 ; Partner Min Conwinner Sessions auto_act = 0 ; Auto activated sessions min_sendru = 256 ; Min Send RU size max_sendru = 2048 ; Max Send RU size send_pace = 16 ; Send Pacing count min_rcvru = 256 ; Min Receive RU size max_rcvru = 2048 ; Max Receive RU size rcv_pace = 16 ; Receive Pacing count Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 161

162 Operator Manual ; ************************************************************************** ; APPC Remote LU Record ; ************************************************************************** [APPC_REMOTE_LU] alias = "RVSCICST" ; LU Alias description = "CICS-Test ; Text description of LU DB/2" net_name = "NETZ" ; LU Network Name LU_name = "RVSCICST" ; Name of LU SSCP_Alias = "RVSCICST" ; SSCP LU Alias parallel_sess = Yes ; Parallel Sessions supported conv_sec = No ; LU uses conversation level security session_sec = none ; No Session Level Security ; ************************************************************************** ; APPC Remote LU Record ; ************************************************************************** [APPC_REMOTE_LU] alias = "RVSRVS6" ; LU Alias description = "rvs_mvs ; Text description of LU Test" net_name = "NETZ" ; LU Network Name LU_name = "RVSRVS6" ; Name of LU SSCP_Alias = "RVSRVS6" ; SSCP LU Alias parallel_sess = Yes ; Parallel Sessions supported conv_sec = No ; LU uses conversation level security session_sec = none ; No Session Level Security ; ************************************************************************** 162

163 Configuration of UNIX Systems ; APPC Remote LU Record ; ************************************************************************** [APPC_REMOTE_LU] alias = "RVSRVSG2" ; LU Alias description = "rvs_mvs ; Text description of LU Test2" net_name = "NETZ" ; LU Network Name LU_name = "RVSRVSG2" ; Name of LU SSCP_Alias = "RVSRVSG2" ; SSCP LU Alias parallel_sess = Yes ; Parallel Sessions supported conv_sec = No ; LU uses conversation level security session_sec = none ; No Session Level Security ; ************************************************************************** ; APPC Remote LU Record ; ************************************************************************** [APPC_REMOTE_LU] alias = "RVSR11L" ; LU Alias description = "R11 rvs- ; Text description of LU Produktion" net_name = "NETZ" ; LU Network Name LU_name = "RVSR11L" ; Name of LU SSCP_Alias = "RVSR11L" ; SSCP LU Alias parallel_sess = Yes ; Parallel Sessions supported conv_sec = No ; LU uses conversation level security session_sec = none ; No Session Level Security Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 163

164 Operator Manual ; ************************************************************************** ; 3270 Pool Record ; ************************************************************************** [3270_POOL] name = "gedas1" ; Pool name description = "gedas1-lu- ; Text description of pool Pool" model = 2 ; Model 2 (24*80) override = No ; User can change screen model ; ************************************************************************** ; SDLC Link Record ; ************************************************************************** [SDLC_LINK] name = "GEDASDLC" ; Name of SDLC link description = "SDLC-Link der ; Description Testinstallation" device_name = "sna_sdlc" ; Name of device file for link port_number = 0 ; Adapter port line_type = leased ; Leased const_carrier = Yes ; Full duplex modem support 164

165 Configuration of UNIX Systems ; ************************************************************************** ; Invocable Transaction Program Record ; ************************************************************************** [INVOCABLE_TP] alias = "ORACTEST" ; TP Alias description = "Oracle test" ; Text description of TP load_method = Q_auto ; TP is queued, dynamically loaded conv_sec = No ; TP needs user ID and password TP_type = APPC ; TP is an APPC TP file = "/users/test/orac" ; Executable file name TP_nametype = char ; TP name in characters TP_name = "ORATEST" ; Full name of TP parameters = "" ; Invocation parameters environment = "" ; Invocation environment target = "" ; Machine to load TP on load_time = 60 ; Timeout for loading TP service_time = 60 ; Timeout for servicing TP Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 165

166 Operator Manual ; ************************************************************************** ; Invocable Transaction Program Record ; ************************************************************************** [INVOCABLE_TP] alias = "RVSRCV" ; TP Alias description = "rvs Receiver ; Text description of TP LU6.2" load_method = auto ; TP is non-queued, dynamically loaded conv_sec = No ; TP needs user ID and password TP_type = APPC ; TP is an APPC TP file = "/users/rvs/system/r vscom" ; Executable file name TP_nametype = char ; TP name in characters TP_name = "RVSRCV" ; Full name of TP parameters = "/e/users/rvs/rvsenv.dat" ; Invocation parameters environment = "" ; Invocation environment target = "" ; Machine to load TP on load_time = 90 ; Timeout for loading TP service_time = 60 ; Timeout for servicing TP 166

167 Configuration of UNIX Systems ; ************************************************************************** ; SDLC Link Usage Record ; ************************************************************************** [SDLC_USAGE] node = "GEDANODE" ; Node name link = "GEDASDLC" ; Link name incoming = No ; Incoming calls accepted encoding = nrz ; Data encoding is nrz ; ************************************************************************** ; RJE FCB Record ; ************************************************************************** [RJE_FCB] name = ".STDFCB" ; Name of RJE Form description = "Default FCB" ; Text Description page_length = 66 ; Length of page (lines) first_line = 1 ; First line output last_line = 66 ; Last line output channel_2 = 0 ; Vertical Tab 2 channel_3 = 0 ; Vertical Tab 3 channel_4 = 0 ; Vertical Tab 4 channel_5 = 0 ; Vertical Tab 5 channel_6 = 0 ; Vertical Tab 6 channel_7 = 0 ; Vertical Tab 7 channel_8 = 0 ; Vertical Tab 8 channel_9 = 0 ; Vertical Tab 9 channel_10 = 0 ; Vertical Tab 10 channel_11 = 0 ; Vertical Tab 11 channel_12 = 0 ; Vertical Tab 12 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 167

168 Operator Manual 6.11 Defining the SNA Network for AIX and SINIX This chapter describes the Host Definition for AIX and SINIX, the SNA Server/6000 Definition for AIX and TRANSIT Definition for SINIX as well as the TRANSIT Support of Change Number of Sessions Verbs Host Definition for AIX and SINIX In the following chapter an overview on how to code VTAM and NCP parameters is given. There is no guarantee for completeness and correctness. However, the coding examples given below originate from a functioning environment. For data security reasons, sensitive parameters like names, dialnumbers etc. have been changed. Please choose your own names for LUs, PUs, mode tables, log modes etc. and insert your own values for DIALNO, IDBLK, IDNUM and other parameters APPL Macro The APPL Macro defines the HOST RVS as Major Node. VBUILD RVSAPPL APPL TYPE=APPL AUTH=(ACQ,PASS),PARSESS=YES,SPAN=(S P11), VPACING=7,MODETAB=LMTRVS,DLOGMOD=MT ERV10,ACBNAME=RVSAPPL, APPC=YES Mode Table Definitions The mode table defines the BIND parameters for LU 6.2. LMTRVS MODETAB MTERV10 ODEENT LOGMODE=MTERV10, BIND-Image for LU6.2 COS=BATCH1,TYPE=X'00', FMPROF=X'13',TSPROF=X'07 PRIPROT=X'B0',SECPROT=X'B0',COMPROT =X'DOB1', RUSIZES=X'8686',PSERVIC=X' ' 168

169 Configuration of UNIX Systems NCP BUILD Macro The build macro has to include some parameters in order to support LU 6.2 PU type 2.1 connections. NCPRVS01 BUILD ADDSESS=100, AUXADDR=50, BFRS=128, BRANCH=100, CA=(TYPE5,...), CANETID=(YXZ,...), CATRACE=(YES,128), COSTAB=ISTSDCOS, CWALL=32, DELAY=(.2,...), DR3270=NO, DSABLTO=3, ENABLTO=20, ERLIMIT=16, HSBPOOL=500, ITEXTTO=NONE, LOADLIB=NCPLOAD, LTRACE=4, MAXSESS=20, MAXSSCP=6, MAXSUBA=63, MODEL=3725, NAMTAB=200, NCPCA=(AVTIVE,...), NETID=XYXYXY, NETLIM=300, NEWNAME=XXXXX, NPA=(YES,DR), NUMHSAS=60, OLT=YES, PATHEXT=100, PRTGEN=GEN, LU 6.2! LU 6.2! LU 6.2 LU 6.2 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 169

170 Operator Manual PWROFF=NO, SESSLIM=255, SLODOWN=12, SUBAREA=33, TGBXTRA=20, TIMEOUT=(420,...), TRACE=(YES,256), TRANSFER=32, TYPGEN=NCP, TYPSYS=MVS, UCHAN=NO, VERSION=V4R3.1, VRPOOL=250, X25.MWINDOW=7, X25.IDNUMH=03, X25.MAXPIU=4000, X25.MCHCNT=1 170

171 Configuration of UNIX Systems SDLC Leased Line Attachement The line statement in NCP specifies the physical link for the attached units. LNRVS00 LINE ADRRESS=(nnn,HALF), CLOCKING=EXT, DATRATE=HIGH, DUPLEX=FULL, HISPEED=NO, MAXPU=1, NEWSYNC=NO, NPACOLL=YES, NRZI=YES, OWNER=SAnn, PAUSE=0.1, RETRIES=(7,0,0), SERVLIM=10, SPAN=(SP11), SPDSEL=NO, SPEED=9600, ISTATUS=ACTIVE All necessary line configurations are depending on the physical line and modems, where the control unit (3174) is connected to the network controller (37xx / NCP). You can get these informations from the NCP systems administrator. The PU statement specifies the physical control unit (3174). PURVS00 PU ADDR=C1, MAXDATA=265, MAXOUT=7, NPACOLL=YES, PASSLIM=7, PUTYPE=2, SPAN=(SP11), XID=YES, ISTATUS=ACTIVE (!) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 171

172 Operator Manual (!) The parameter XID=YES must be included for SNA-NODE 2.1 and Leased Lines! All other parameters for SNA-NODE 2.1 & LU6.2 must be included in the BUILD Macro Definitions for the NCP. The LU statement specifies the Independent Logical Unit (LU) with parallel sessions. LURVS00 LU LOCADDR=00, DLOGMOD=MTERV10, MODETAB=LMTRVS, NPACOLL=YES, PACING=2, RESSCB=5, SSCPFM=FSS, SPAN=(SP11), VPACING=3, ISTATUS=ACTIVE (!) (!) The LOCADDR=00 defines, that an Independent LU with parallel session Support is being used X.25 or Tokenring connections X.25 or Tokenring are switched connections requiring definitions of a switched major node besides the Multichannel and Switched Line definitions for the physical attachement. Given below is a coding example for a switched major node for LU 6.2 PU 2.1 Attachement of rvs. 172

173 Configuration of UNIX Systems VBUILD PURVS00 PU PATH LURVS00 LU TYPE=SWNET,MAXGRP=1, MAXNO=1 ADDR=C1, DISCNT=(YES,F), IDBLK=xxx, IDNUM=xxxxx, IRETRY=NO, MAXDATA=261, MAXOUT=7, MAXPATH=1, PASSLIM=7, PUTYPE=2, SPAN=(SP11), ISTATUS=ACTIVE DIALNO= , GRPNM=xxxxxxx LOCADDR=00, DLOGMOD=MTERV10, MODETAB=LMTRVS, PACING=1, SSCPFM=FSS, SPAN=(SP11), VPACING=1, ISTATUS=ACTIVE (change!) (change!) (for X.25 dial-out) (!!) (!) These parameters are used to localize the corresponding PU/LU upon dial-in. IDBLK is depending on the type of device attached. For example, an AS/400 system requires IDBLK=056, an OS/2 system requires IDBLK=05D. The IDNUM parameter may be chosen according to your local policy. (!!) The LOCADDR=00 defines, that an Independent LU with parallel session support is being used. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 173

174 Operator Manual HOST Software Releases The following Software Releases on an IBM Mainframe must be available to Support VTAM APPC and NCP with SNA 2.1 Definition : VTAM Version 3.2 with PTF-Level NCP Version with PTF-Level NCP Version 5.3 (FEP 3745) SNA Server/6000 Definition for AIX LU6.2 connections are controlled by the subsystem SNA Server/6000. First, make sure that SNA Server/6000 is running on your system: 1. Check status of SNA server: smit. 2. Configure a session with: smit sna. We recommend to use the name rvscp for the LU6.2 Side Information Profile and LU6.2 Partner LU Profile so that this name corresponds with the rvs stationtable entry PROFILE=rvscp. One of the rvs partner stations must be an appn_network_node. If your rvs partner station is a MVS system, you can define your UNIX SNA system as an appn_end_node. You find a sample configuration in the file /home/rvs/system/s_server.lis. 3. Activate the link station. 4. Activate the session. 5. Check the Session: lssrc -l -s sna. The output should be like this: Link station Adjacent CP name Node type Device name State Number of XXXXXX XX XXXXXX.A BCD EN ent0 ent0 Starting Active

175 Configuration of UNIX Systems 6. Check rvs connection: rvscom /l rvscp. The rvs communication module rvscom tries to open the LU6.2 connection, allocates the remote transaction program (RVSOFTP) and waits for an OFTP Ready Message. If this test is successful, you can transfer files via rvs. If it fails, use smit sna - Diagnose. Here is a sample SNA/6000 profile. You can import it from $RVSPATH/samples/sserver.lis with smit sna - Configure - Import (see chapter "Representation means" for the detailed description of $RVSPATH). You have to change the marked parameters. Then verify with smit sna - Configure - Verify. sna: prof_name max_sessions max_conversations restart_action rrm_enabled dynamic_inbound_partner_ lu_definitions_allowed standard_output_device standard_error_device nmvt_action_when_no_ nmvt_process comments = "sna" = 200 = 200 = once = no = yes = "/dev/console" = "/var/sna/sna.stderr" = reject = "" Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 175

176 Operator Manual Control_pt: prof_name xid_node_id network_name control_pt_name_alias control_pt_name control_pt_node_type max_cached_trees max_nodes_in_topology_ database route_addition_resistance comments = "node_cp" = 0x071f0002 change! = "DEIBMD1" change! = "RVS2" change! = "RVS2" change! = appn_network_node = 500 = 500 = 128 = "" local_lu_lu6.2: prof_name local_lu_name local_lu_alias local_lu_dependent local_lu_address sscp_id link_station_prof_name conversation_security_li st_profile_name comments = "rvs" = "LURVS002" change! = "LURVS002" change! = no = = * = "LINKRVS1" = "" = "" 176

177 Configuration of UNIX Systems partner_lu6.2: prof_name fq_partner_lu_name partner_lu_alias session_security_supp parallel_session_supp conversation_security_ level comments = "rvscp" (rdstat.dat) = "DEIBMD1.LURVS001" = "LURVS001" change! = no = yes = none = "" side_info: prof_name local_lu_or_control_pt _alias partner_lu_alias fq_partner_lu_name mode_name remote_tp_name_in_hex remote_tp_name comments = "rvscp" (rdstat.dat) = "LURVS002" change! = "LURVS001" change! = "" = "RVSMODE0" = no = "RVSOFTP" = "" Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 177

178 Operator Manual local_tp: prof_name tp_name tp_name_in_hex pip_data_present pip_data_subfields_ number conversation_type sync_level resource_security_level resource_access_list_ profile_name full_path_tp_exe multiple_instances user_id server_synonym_name restart_action communication_type ipc_queue_key standard_input_device standard_output_device standard_error_device comments = "rvs" = "RVSOFTP" = no = no = 0 = mapped = none = none = "" = "/home/rvs/system/ rvscom" change! = Yes = 100 = "" = once = signals = 0 = "/dev/console" = "/tmp/rvssna.out" = "/tmp/rvssna.err" = "" 178

179 Configuration of UNIX Systems link_station_ethernet: prof_name use_control_pt_xid xid_node_id sna_dlc_profile_name stop_on_inactivity time_out_value LU_registration_ supported LU_registration_profile_ name link_tracing trace_format access_routing_type remote_link_name remote_link_address remote_sap verify_adjacent_node net_id_of_adjacent_node cp_name_of_adjacent_node xid_node_id_of_adjacent_ node node_type_of_adjacent_ node solicit_sscp_sessions call_out_on_activation activate_link_during_ system_init activate_link_on_demand cp_cp_sessions_supported cp_cp_session_support_ required adjacent_node_is_ preferred_server initial_tg_number = "LINKRVS1" = no = 0x071f0001 change! = "rvs2" = no = 10 = no = "" = no = long = link_name = "RVS1" change! = 0x = 0x04 = yes = "" = "RVS1" change! = 0x071f0001 change! = learn = yes = yes = no = no = yes = no = no = 0 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 179

180 Operator Manual restart_on_normal_ deactivation restart_on_abnormal_ deactivation restart_on_activation TG_effective_capacity TG_connect_cost_per_time TG_cost_per_byte TG_security TG_propagation_delay TG_user_defined_1 TG_user_defined_2 TG_user_defined_3 comments = no = no = = 0 = 0 = nonsecure = lan = 128 = 128 = 128 = "" sna_dlc_ethernet: prof_name datalink_device_name force_timeout user_defined_max_i_field max_i_field_length max_active_link_stations num_reserved_inbound_ activation num_reserved_outbound_ activation dlc_protocol transmit_window_count retransmit_count receive_window_count inact_timeout response_timeout acknowledgement_timeout link_name local_sap retry_interval = "rvs2" = "ent0" = 120 = no = = 100 = 0 = 0 = standard = 16 = 8 = 16 = 48 = 4 = 1 = "RVS2" change! = 0x04 =

181 Configuration of UNIX Systems retry_limit dynamic_link_station_ supported trace_base_listen_link_ station trace_base_listen_link_ station_format dynamic_lnk_solicit_ sscp_sessions dynamic_lnk_cp_cp_ sessions_supported dynamic_lnk_cp_cp_ session_support_required dynamic_lnk_tg_ effective_capacity dynamic_lnk_tg_connect_ cost_per_time dynamic_lnk_tg_cost_per_ byte dynamic_lnk_tg_security dynamic_lnk_tg_ propagation_delay dynamic_lnk_tg_user_ defined_1 dynamic_lnk_tg_user_ defined_2 dynamic_lnk_tg_user_ defined_3 comments = 20 = yes = no = long = yes = yes = no = = 0 = 0 = nonsecure = lan = 128 = 128 = 128 = "" Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 181

182 Operator Manual mode: prof_name mode_name max_sessions min_conwinner_sessions min_conloser_sessions auto_activate_limit max_adaptive_receive_ pacing_window receive_pacing_window max_ru_size min_ru_size class_of_service_name comments = "rvs" = "RVSMODE0" = 10 = 5 = 5 = 2 = 16 = 7 = 1024 = 256 = "#CONNECT" = "" SINIX TRANSIT Definition The SINIX TRANSIT definition is described in the "Communications Manager SINIX V5.1 (CMX) Operation and Administration (SINIX, Reliant UNIX)" manual and in the "TRANSIT (UNIX) Documentation". You find these manuals in the internet: and 182

183 Configuration of UNIX Systems 6.12 Specify System Environment rvs derives the information where its various data sets are stored from a data set describing the local environment. The standard environment data set is found in $RVSPATH/rvsenv.dat which was created during the installation process of rvs. The name of the path depends on the user which installed rvs. This data set is pointed to by environment variable RVSENV which can be set in system file /etc/environment for AIX /etc/profile for HP-UX, SINIX, Solaris, IRIX, Linux and SCO by means of the statement RVSENV = $RVSPATH/rvsenv.dat; export RVSENV Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 183

184 Operator Manual The environment variable RVSENV can also be set in the local environment files of the user who has been installed rvs. See chapter "Representation means" for the detailed description of $RVSPATH. This data set can be edited by the rvs administrator and contains a set of parameters, which, besides other information, describe the directory structure of rvs. More than one environment data set can exist. If for some reason you choose to run in another environment, you must call every rvs main program with the '/e' flag immediately followed by the name of the environment data set containing the actually wanted definitions. This facility allows for maximum flexibility in the storage of rvs data sets. This is convenient for example, if you want to install or test a new version of rvs without disturbing operations of the productive rvs. The environment data set contains parameters in the name=value syntax. Comment lines have to start with an asterisk (*) in column 1. Strings containing blanks, brackets, lowercase characters, and quotes have to be delimited by quotes or double quotes. Single quotes inside a string have to be doubled. The environment parameters are: MODE LANGUAGE DBLOG The execution mode. Valid values are MODE=n for 'normal' execution or MODE=d for 'disabled'. The latter can be useful during database recovery. Default is N. The language to be used if database is not available. Valid values are D for german and E for english dialog. Default is E for English. specifies wether a database log file will be written during rvs database accesses. If you specify Yes (Y), you can debug the rvs database access. If you specify No (N), much disk space will be saved and performance is increased. Default: DBLOG=N 184

185 Configuration of UNIX Systems PATH DB INIT SYSTEM TEMP The common default path for all rvs files. This specification can be overridden by the directory path definition decribed below. Default: $RVSPATH $RVSPATH depends on the system and can have different values: /home/rvs/ for AIX, IRIX, Solaris, Linux and SCO /users/rvs/ for HP-UX /defpath/rvs/ for SINIX If you choose to define a value for PATH other than the default value, all default directory names described below change accordingly. is the directory that contains all rvs database and related files. Default: DB=$RVSPATH/db/ is the directory containing all files that may be modified by the user like the stationtable or the initialization file for the Monitor. Default: INIT=$RVSPATH/init/ is the directory which contains all rvs system files like programs, messages, help files and masks. Default: SYSTEM=$RVSPATH/system/ is the directory which will be used to store all temporary data sets. For example, incoming data will be stored in this directory during reception and will be deleted after successful delivery (copy) to the end user. Default: TEMP=$RVSPATH/temp/ USRDAT is the directory where the received data sets are copied to after sucessful transmission. Default: USRDAT=$RVSPATH/usrdat/ SAMPLES is the directory which contains shell scripts an C- Sources. See file header for explanation, and User Manual for a description of Batch and Call- Interface. This directory also contains a SNA-LU6.2 sample profile. Default: SAMPLES=$RVSPATH/samples/ Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 185

186 Operator Manual DFTAUT describes the default access rights to received files 6.13 Get a License for UNIX During installation, an authorisation key data set rdkey.dat is copied to $RVSPATH/init/ If you install a full version of rvs, you get an authorisation file (see chapter "Representation means" for the detailed description of $RVSPATH) which contains no expiration date - that means there is no time limit build in. If you install a demo or test version, the file may contain an expiration date. Also, whenever you receive a new license key for rvs, edit or replace $RVSPATH/init/rdkey.dat Structure of the license key data ! Customer Number X! Product ! Release LTX! Included Components TESTINSTALLATIO N TESTVERSION! Customer Name (Part one)! Customer Name (Part two) ! reserved ! reserved ! reserved ! reserved ! reserved ! Computer Model ! PHYSICAL CPU IDENTIFICATION 186

187 Configuration of UNIX Systems 94211! Expiration Date CA580BE F9 77AD D0D7F 18FAB129 53B14EA F *******************(C) gedas GmbH * make a success of rvs ************************************** Included Components may contain two or more feature codes: L T X LU 6.2 communications TCP/IP communications X.25 native / ISDN communications Not all features are available on all platforms at this time. Expiration Date is designated YYTTT where YY means the year, TTT the day-of-year of expiration. Note: Do not modify any of the fields in the license key file unless explicitly asked to do so by gedas GmbH. However, if you are asked to make modifications, please note that the fields are sensitive to upper and lower case characters. Do not use "tabs" or the comments starting in column 37 might leak over into sensitive fields. Invalid or inconsistent entries will prevent rvs from working properly. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 187

188 Operator Manual 6.14 Defining your Error Handling Under rvs, you are able to specify the actions in case of errors. If an error occurs (for example, a transmit error because of dropped connections), a log message will appear on the operator console. In addition, the shell script $RVSPATH/system/rvserr (see chapter "Representation means" for the detailed description of $RVSPATH) will be executed, which may post the message as unix mail. So you don't have to look constantly for console messages to notice any problems. If you don't want to get error mails, or if you want to specify your own error handling, you can edit the unix shell script rvserr located in path $RVSPATH/system/ You can also write a C program with that name. See shell script rvserr for a description of parameters. 188

189 rvs Monitor for UNIX 7 rvs Monitor for UNIX This chapter contains the description how to start and stop the rvs Monitor for UNIX and Windows NT systems as well as how to set parameters and how to use rvs Monitor commands. 7.1 Start rvs Monitor (rvsstart) In this text, we assume that the Monitor is located in directory $RVSPATH/system/. Please, ask your system administrator, whether this is true for your installation and see chapter "Representation means" for the detailed description of $RVSPATH. rvsstart lets you start the rvs process: rvsstart Monitor as a background This starts the Monitor with the command nohup rvsmon&. If there is a Monitor already running, an error message appears. Switch to the proper directory, e.g. to $RVSPATH/system/. To start the monitor, simply say nohup rvsmon& or rvsstart and the Monitor starts running in background. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 189

190 Operator Manual If $RVSPATH is not part of your default access path as defined in the PATH system variable, switch to the proper directory be entering these two commands: c: cd $RVSPATH To start the operator console, simply say rvscns and the Operator Console should start running. To stop the operator console hit the F3 key. On the command input line you can enter additional inquiries, modify the way the Monitor executes or simply look what is going on. 7.2 Stop rvs Monitor (rvsstop) To stop the rvs system enter stop at the console input promt [RVSCNS] when using Operator Console (rvscns) or just use the command rvsstop rvsstop places a Monitor stop command into the rvs database for either immediate or for delayed execution. Note, however, that the stop command will only take affect, if Monitor is currently active (because a starting Monitor removes all `old' operator commands from the database). Therefore, it is better to include opcmd cmd=stop time=1 in the Monitor initialization file to stop rvs around 1 a.m. 190

191 rvs Monitor for UNIX Having stopped the monitor does not mean that rvs is completely down, because sender and receiver tasks still can be active and even new receiver tasks could be started-up from remote. Also application programs using the batch interface or the dialog interface could still be active. If you want rvs completely to shut down, close down any open dialog interface and rvs using application, then disable external communication by shutdown any rvs related communication deamon, e.g. the LU6.2 deamon. check that no rvs task is running with command ps -e grep rvs TPStart program by closing that program icon in case of LU6.2 communication. Then check that no rvs task is running. If rvs tasks are still running, the rvs database may be destroyed or deleted, when you start backup or maintanace functions, so wait until all task has been ended. Usage rvsstop [/ervsenv] [/lx] [/t] [/zhh[:mm[:ss]]] [/F] [/?] All parameters are optional: /ervsenv specifies rvs environment data set RVSENV. /lx uses language x for prompts and messages. /t stops Monitor executing in test mode. /z.. specifies time, when Monitor is supposed to stop; if that time has passed already today, the command will be scheduled for tomorrow. /F stops Monitor immediately; all active senders and receivers are interrupted. /? requests help information. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 191

192 Operator Manual Example rvsstop /e/home/sfr/rvstest/rvsenv.dat /ld /z3 Stop Monitor that uses rvs database defined in environment data set /home/sfr/rvstest/rvsenv.dat; use German language for user communications. The Monitor is to stop at 3 a.m. Use stop xmt=force to terminate Monitor, MasterTransmitter and all active Senders and Receivers immediatly. Active Senders will be interrupted abnormely. Exactly the same happens if you use the command rvsstop /F 7.3 Stop MasterTransmitter MasterTransmitter rvsxmt controls the number of concurrently active Senders, depending on parameter MAXSENDERS the number of prestarted "listening" receivers for X.25 native or ISDN communication, waiting to accept incoming calls, depending on parameter MAXX25RCV (provided your rvs version is able to support X.25 native or ISDN). the number of prestarted "listening" receivers for TCP/IP communication, waiting to accept incoming calls, depending on parameter TCPIPRCV (provided your rvs version is able to support TCP/IP). MasterTransmitter is started automatically during the Monitor's initialization phase. When the Monitor is terminated with stop or stop rvs=end, the MasterTransmitter waits until all active senders has been ended, and then ends. Use stop xmt or stop xmt=end to terminate MasterTransmitter after it stops all active Senders when rvsxmt receives such a stop command. 192

193 rvs Monitor for UNIX Use stop xmt=force to terminate Monitor, MasterTransmitter and all active Senders and Receivers immediatly. Active Senders will be interrupted abnormely. Exactly the same happens if you use the command rvsstop /F Upon closedown of rvsxmt all prestarted "listening" X.25 native, ISDN and TCP/IP Receivers will closedown too. 7.4 Kill rvs Programms (rvskill) only for UNIX rvskill lets you stop ("kill -9") the UNIX processes of rvs : rvskill Then you will be asked which process of rvs you want to stop. rvskill should be used ONLY if rvsstop does not work anymore (e.g. if the database is deleted or destroyed). If you are forced to use rvskill command call rvsrii afterwards (see chapter "Recover Isam Index (rvsrii)"). If the database is damaged you should delete it (see "Create new Database (rvsidb)"). 7.5 Use non default Database Sometimes, it may be desirable to use a database other than the default one for rvs operations. The path to the non-default database can be specified via an alternate environment data set specified as command line argument when the rvs Monitor is started (the same is true for the other rvs utilities like rvsdia or rvsbat, by the way). The environment data set, which by default is found as $RVSPATH/system/rvsenv.dat, contains all the nessesary information for rvs where to find the data sets and modules it needs for execution (see chapter "Representation means" for the detailed description of $RVSPATH). But before this can happen, you have to create an alternate copy of the environment data set and edit it. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 193

194 Operator Manual Let us assume that you want to start the Monitor with the database located in $RVSPATH/system/DBnew/ to test some new line definitions without disturbing the production rvs. Let us assume further, that the alternate environment data set is $RVSPATH/system/testenv.dat. This alternate environment data set has to contain the following statement: DB=$RVSPATH/rvs/system/DBnew/ To start the rvs Monitor with the alternate environment, say nohup rvsmon& /e/defpath/rvs/system/testenv.dat Note, that there must not be any blanks between the option indicator /e and the start of the environment data set name. Note further, that this specification will not be remembered across sessions. 194

195 rvs Monitor for UNIX 7.6 Set rvs Parameters at Start Time Many characteristics of rvs operation can be customized through rvs parameters. Chapter "9 rvs Parameters" contains a list of all parameter names and a brief description of their purposes. Chapter "10 rvs Parameter Values" discusses some considerations how to choose rvs parameter values. Parameter values can be changed when the Monitor is started 1. Note, that these changes are permanent and will be remembered across sessions. Requests to set parameter values are entered as NAME=VALUE command line arguments; the number of these requests is only limited by the length of the command string that the system will accept. Let us assume that you want to increase the priority of operator commands to 5 (the default is 10) and change the rvs Monitor suspension time 2 to 1 minute (default is 30 seconds). To accomplish this, start the rvs Monitor with nohup rvsmon okprio=5 sleep=60 & 1 Parameters may also be changed with the operator command setparm or in the Monitor initial command data set. 2 The Monitor suspension time is the period of time (in seconds) that the Monitor waits before looking for a new command when currently there is nothing to do for it. Longer periods decrease system overhead but make the Monitor less responsive to newly entered commands. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 195

196 Operator Manual 7.7 Monitor Initial File For UNIX You may wish to have certain operator commands executed whenever the Monitor starts. This can be accomplished by storing those operator commands in file $RVSPATH/init/rdmini.dat, (see chapter "Representation means" for the detailed description of $RVSPATH) and setting flag /i in the start command: nohup rvsmon /i& (Since this flag is remembered across session, specifying /i actually is only necessary, after the flag has been turned off for some reason.) $RVSPATH/init/rdmini.dat contains a sample definition file for Monitor initialization commands, i.e. those commands, that are executed whenever the rvs Monitor is started (except if flag /i0 is in effect). The default values of all parameters are shown as comments, if you remove the comment sign you can change this parameter to your own choice. Edit this file according to your needs. Any operator command can be entered. See chapter "Operator Console and Commands" for more information on operator commands. Use any editor to generate the initialization file. Please, follow these rules, when creating an initialization file: Any operator command may be specified. Each command must be contained in a separate, single line. Empty lines are ignored (so you can optically separate groups of commands). Lines starting with an asterisk (*) in column 1 are ignored (so feel free to enter comments or sample commands). 196

197 rvs Monitor for UNIX Sample Initialization File A file that directs the Monitor to clean up the database by deleting all entries that completed more than three days ago; and makes sure that all line tracing is turned off, might look like this: *Sample Monitor initialization file *(this is another comment line, followed by an empty line) cleanup days=3 ss=yes *turn all line tracing off setparm sp odtracelvl=0 litracelvl=0 By default, the installation process stores a sample initialisation file with a commented description of all commands and parameters in the $RVSPATH/init/rdmini.dat. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 197

198 Operator Manual 7.8 Command Line Arguments When starting the Monitor, a number of optional command line arguments may be specified. They may be either 1. value parameters, 2. flags, or 3. assignment statements. Value parameters and flags start out with a minus sign ("-") or a slash ("/"); they are case independant. Note: All settings except the environment selection parameter /e and temporary flags are remembered across sessions! Value Parameters Value parameters expect a value to immediately (i. e. without intervening space) follow the parameter indicator. /e specify an alternate environment data set containing alternate path information for rvs standard data sets. The value specified here affects only the current run; permanent changes require the default environment data set located in $RVSPATH/system/rvsenv.dat to be edited according to your needs (see chapter "Representation means" for the detailed description of $RVSPATH). Nota bene. This must be the first command line argument; otherwise, it may be ignored. /l language for operator communication and LOG messages; default language for user communication. Must immediately be followed by language specification: D Deutsch E English 198

199 rvs Monitor for UNIX /w recreate database ("Wiederanlauf").The fully qualified name of the old database log must be specified (this name must be different from the data set name that rvs will be using for the current run). flags may be followed by 0 or 1 to turn the flag off or on, respectively; specifying the flag name, only, turns the flag on (e. g. /i1 is equivalent to /i). /i is the flag for reading initial commands. Assignment Statements Assignment statements are of the form PARM=VALUE, with no spaces allowed. parm can be the name of any valid rvs parameter. 7.9 Return Codes The Monitor might return to the operating system with one of the following return codes: 0 normal termination 4 forced termination requested by operator 5 rvs database is disabled 6 another Monitor is already active for the same database 99 sever internal error Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 199

200 Operator Manual V. Operator Reference This section gives an overview of the operator commands and how to them. Then the rvs parameters are listed. In the end the database maintenance and utilities are described. 8 Operator Console and Commands Operator Console The Operator Console is used to control the functions of rvs. The following section presents the rvs logbook and possibilities for control and parameter setting in the rvs through different commands. The Operator Console displays all messages created since the last start of the rvs Monitor. The entire logbook is generated in the following file: $RVSPATH/db/rlog.log for UNIX $RVSPATH\db\rlog.log for Windows NT RVS_DB/LOG (RLOG) for AS/400 and can be saved in an archive file for documentation purposes (see chapter "Representation means" for the detailed description of $RVSPATH). To start the Operator Console: UNIX: write $RVSPATH/system/rvscns Winows NT: choose the Short Cut rvsnt Administrator from the rvs programme groupe or write $RVSPATH\system\rvsmgr.exe AS/400: choose the die Option rvs Console from the rvs400 main menu 200

201 Operator Console and Commands To terminate the Operator Console: UNIX: press the esc button Winows NT: press ALT+F4 or choose File Close from the menu AS/400: press F3 in the rvs400 main menu To scroll in the Operator Console: UNIX: press < or > Winows NT: use the scroll bar AS/400: press buttons page up and page down in the rvs400 main menu To enter commands in the Operator Console: UNIX: you are automatically in the command mode; confirm your command by [ENTER] Winows NT: press [ENTER] or choose Edit Operator Command in the menu and confirm each command you write by [ENTER] AS/400: press [ENTER]in the rvs400 main menu and confirm each command you write by [ENTER] Operator Commands Most operator commands provide information about or influence contents of items in the area of individual rvs commands traffic to neighbors stationtable database rvs parameters Command syntax is specified in chapter "Patterns". The sections in this chapter provide a brief overview of the functionality of operator commands. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 201

202 Operator Manual Note the difference between operator commands and rvs commands: operator command rvs command is a command like listcmd, modst, or cleanup that you enter in the Operator Console for UNIX or execute the menu command Edit/OperatorCommand in rvsnt Administrator window for Windows NT in the rvs400 main menue for AS/400 to instigate some action by the rvs Monitor. is a database entry (like SE (send entry), SK (send command), or BB (user notification). These commands, representing a processable unit of work, are created internally by rvs and are used to organize the flow of work and information between its components. 8.1 Work with Individual rvs Commands When a user creates a send entry (rvs command SE), the user can hold it, delete it, or release it in the dialog interface rvsdia or rvsnt as long as the Monitor did not start processing it. Once one or more send commands (rvs command SK) have been created, command execution can only be modified through operator commands. 202

203 Operator Console and Commands List information about one command In the Operator Console use listcmd cn=n to display information about individual commands. `n' is the command number which uniquely identifies every rvs command. Command numbers are displayed at the Operator Console when the command is created and when certain actions are carried out. NEW_CMD_CREATED IZ(245) created from IE(242) tells you, for example, that an information delivery command (IZ) with command number 245 has been created from information entry (IE) with command number 242 (which in turn normally will have been created by the Receiver while accepting a data set from another rvs node). To learn more about the above information delivery, enter listcmd cn=245 If this operator command is entered after IZ terminated, the system response may look like this: R: KT(245): R: CMDTYPE = IZ R: PRIORITY = 70 R: DTCREATED = 1992/03/25 15:12:29 R: DTSCHEDULE = 1992/03/25 15:12:29 R: DTDONE = 1992/03/25 15:12:43 R: FLAGSERIAL = FALSE R: STATUS = en R: ERRORCODE = 0 R: IZ(245): R: CNIE = 242 R: DSNLOCAL = $RVSPATH/usrdat/AUTOSER1 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 203

204 Operator Manual KT (the part of the information that is stored in the command table) contains the same fields for all commands: CMDTYPE PRIORITY DTCREATED DTSCHEDULE DTDONE FLAGSERIAL STATUS ERRORCODE DSNLOCAL command type, in this case IZ (information delivery, from German InformationsZustellung) the priority with which the command is or was executed; the smaller this number, the higher the priority. These priorites are defined as rvs parameters BBPRIO, IEPRIO, IZPRIO, etc. date and time when the command was created date and time when the command will be available for execution (or in case of an ended command was scheduled to be executed). Very often, DTCREATED and DTSCHEDULE will be the same; command retry or user actions may be the reasons behind differing values. date and time when processing of this command terminated. indicates, whether the (SE) command (still) is in serialization hold; i.e. it is waiting for another rvs command to terminate before it will be eligible for processing. current status; see description of listcmd in chapter "8.1.2 List Command Numbers" for a list of first status letters. The second letter tells you, whether it is a `n'ormal or a `t'est command. _ In our example, `en' means that the `n'ormal command `e'nded. tells you whether the previous attempt to execute the command was successful or failed. In particular, if the status is `q'ueued and the ERRORCODE is not zero, error recovery will be performed, when the command will be selected for execution. The detailed description of $RVSPATH is explained in chapter "Representation means". 204

205 Operator Console and Commands This general information is followed by command-specific information. In our example, it tells you that the parent command (the IE) had command number 242 and in which file the received information was stored List Command Numbers To get a list of all commands that are in a certain status, use listcmd with parameter status. listcmd status=q will give you a list of all `q'ueued commands, for example. See description of listcmd in chapter 8.7 on page 209 for a list of status letters. The second part of the status (`n'ormal or `t'est) is always taken from your current execution mode and you will only see commands that belong to this mode Hold, Free or Delete an rvs command Use holdcmd cn=n freecmd cn=n delcmd cn=n to place command with command number n in operator hold, so that it will not be executed until explicitly freed; to free command with command number n previously placed in operator or user hold; and to delete command with command number n. If you want to delete a command, first you have to put it into the hold state. You will have to delete all commands, too, which are generated from the send entry (i.e. SE and SK). Otherwise, the database would be left in an inconsistent state. This applies to file reception,too (i.e. IE and IZ should be deleted). Note, that no prompting for confirmation has been implemented, yet! So, be careful that you do not mistype the command number when deleting a command. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 205

206 Operator Manual 8.2 Suspend Traffic to Neighbor holdcmd and freecmd may also be used to suspend all traffic to a particular neighboring node in the rvs network. When you know that communication lines to a neighbor will not be available for a while, suspending all traffic to that node will prevent unnecessary send attempts and is much easier than holding and freeing all queued commands for that neighbor, individually. Also, all newly created sends to that station will automatically be suspended. holdcmd sid=xxx suspends all traffic to station ID `xxx' (which must be a neighbor), while freecmd sid=xxx lifts the suspension and releases all suspended commands (commands that were placed in hold using holdcmd cn=n are not released). Use listst sid=xxx and check flag FLAGSUSPND in NK: listing to find out whether all traffic to `xxx' is suspended (FLAGSUSPND=TRUE) or not (FLAGSUSPND=FALSE). 8.3 Activate Neighbor activate can be used to test the connection or to get queued files from your partner. activate sid=xxx act sid=xxx activate starts a send process rvscom which establishes a connection to the neighbor station. Your neighbor is a partner station to which you have a direct connection (by TCP/IP, LU 6.2 or X.25/ISDN). If your rvs station has queued files for this partner, they will be send now. If your partner has queued files, they will be received. Otherwise, the connection ends. The partner can be called repeatedly, for example every 3 hours: opcmd cmd="act sid=xyz" repeat=03:00:00 Note, that you can't activate the target station, if you are sending a file via routing. 206

207 Operator Console and Commands 8.4 Work with Stationtable Entries Entries in stationtable ST and its related tables LU TC NK OP RT XP LU 6.2 (or APPC) parameters, TCP/IP parameter table, neighboring nodes (from German `NachbarKnoten'), ODETTE parameters, and routing table X.25 native and ISDN parameters are explained in chapter "Customizing Stationtable ST". Use listst sid=xxx to list all entries in these tables relating to station ID `xxx'. To modify entries, edit $RVSPATH/init/rdstat.dat (see chapter "Representation means" for the detailed description of $RVSPATH), the file that provides stationtable definitions when the database is generated by rvsidb. If you are using the default file $RVSPATH/init/rdstat.dat, use modst without parameters. Else create a separate file in directory $RVSPATH/init/ which contains only new and modified entries and set the filename parameter DSN (DataSetName) to the path name of your file. modst dsn="$rvspath/init/rdstat_new.dat" reads file $RVSPATH/init/rdstat_new.dat and replaces all database table rows with the input of this file. Therefore, specify all fields for each entry that you want to replace! The file name can be a single input file or a directory which contains several input files. delst sid=xxx removes all entries relating to station ID `xxx' from the stationtable and its related tables from the database (it does not search for open send requests to this station, however; if there are any, they will fail later on, when Monitor or Sender will try to execute them). Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 207

208 Operator Manual We recommend that you execute the command delst sid=xxx first and then modst, to avoid possible duplicate entries in the database. Note, that no prompting for confirmation has been implemented, yet! So, be careful that you do not mistype the station ID when deleting. 8.5 Work With rvs Parameters Parameters can be used to customize rvs operations. They are described in chapter "rvs Parameters" on page 213; tips how to choose rvs parameter values are given in chapter "rvs Parameter Values". Use listparm name to list one or more parameter values. NAME can be the name of a parameter to list this one value, a pattern to list all parameters whose names match this pattern (patterns are described in section 8.6 on page 209), or ALL to list all parameters. Parameter NAME can be modified with setparm name=value No plausibility check is made on the value you specify and results are unpredictable if you specify invalid values or wrong data types. 208

209 Operator Console and Commands 8.6 Patterns Some commands support patterns, which means that the values you specify for these parameters may include wildcards asterisk (*) and/or question mark (?) to select more than one value at a time: * matches any number of arbitrary characters,? matches exactly one arbitrary character pattern must be enclosed in single or double quotation marks. For example, to list the execution priorities of all commands, enter listparm "*prio" and the Monitor will list the values of BBPRIO, IEPRIO, IZPRIO, etc. Specifying listparm "q?prio" will list QEPRIO and QZPRIO. 8.7 Command Descriptions In the command descriptions, brackets ([ ]) indicate optional parameters, braces and bars({ }) list alternatives. activate SID=sid act is an alias of activate. Activate a partner station. A rvs communication program starts and establishes the connection. Queued data sets will be transmitted. cleanup [DAYS=n] [SS=YES] Physically delete commands from rvs database that ended at least n days ago (n x 24 hours, to be precise). cleanup DAYS=0 purges all ended and deleted commands. If SS=YES is specified, all old SendStatistics records are deleted. For AS/400: At first, the commands will be deleted logically. Only if database of the AS/400 system is reorganized, the commands will be deleted definitely. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 209

210 Operator Manual delcmd CN=cn Delete command with command number cn logically from database delst SID=sid Delete station sid from all station-table related database tables. freecmd [CN=cn] [SID=sid] Free command with command number cn from hold status or free all suspended transfers to neighbor sid. holdcmd [CN=cn] [SID=sid] Put command with command number cn in hold status or suspend all transfers to neighbor sid. listdbv list version and creation date of database. listcmd [CN=n] [STATUS=x] lc is an alias of listcmd. List details of command with number n or type and number of all commands whose status is x: a active: the command is being processed d deleted: this entry was (logically) deleted e ended: processing of the command ended f forwardable: ready to be sent (SK or QS) h held: command was put in hold status; it cannot be processed until freed (i.e. put into status q) i in transit: command is currently being sent (SK or QS) p pending: processing partially complete; command is waiting for some event (e.g. SE is in this status, after SKs have been created until all receipts are received; RE is always in this status, waiting for information that matches it to come in) q queued: ready to be processed s suspended: ready to be sent but suspended, because all traffic to neighbor has been stopped (SK or QS) listparm {name "pattern" ALL} 210

211 Operator Console and Commands lp listst ls modst opcmd is an alias of listparm List one, more, or all rvs parameters. SID=sid is an alias of listst list all stationtable entries involving station ID sid. DSN=dsn Modify stationtable ST and/or related tables by applying commands stored in DSN which must be fully qualified. Hinweis: Wenn Sie in der Stationstabelle Änderungen vorgenommen haben, müsen diese über den modst Befehl in die Datenbank übernommen werden, damit sie wirksam werden. modst can also be used without parameters; then the default rdstat.dat in the init directory is used as input. The parameter DSN (data set name) can be used to read another input file instead of rdstat.dat: the file name can be a single input file or a directory which contains several input files (see chapter "Representation means" for the detailed description of $RVSPATH): modst DSN="$RVSPATH/init/otherfile.dat" Default: $RVSPATH/init/rdstat.dat for UNIX $RVSPATH\init\rdstat.dat for Windows NT RVS_INIT/DAT(RDSTAT) for AS/400 [DSN=dsn] [CMD=cmd] [TIME=hh[:mm[:ss]]]] [REPEAT=hh[:mm[:ss]]]] read operator commands from external data set `dsn' which must be fully qualified; or execute operator command specified in cmd; if TIME is specified, the operation will be rescheduled for the specified time of day; if REPEAT is specified, the command will be executed immediately and repeated (indefinitely) after the given interval has expired. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 211

212 Operator Manual setparm name=value sp is an alias of setparm Modify one rvs parameter. start [XMT] [CID=console-id] Start MasterTransmitter or one console. stop [XMT][RVS={END FORCE}] XMT=END CID={console-id pattern}] Stop Monitor (normally or with FORCEDEND), MasterTransmitter, or one or more consoles. stop xmt and stop XMT=END are equivalent commands. stop---without parameters---stops the Monitor. system CMD="cmd" Pass command cmd to operating system for execution. 212

213 rvs Parameters 9 rvs Parameters The execution of the Monitor and its related components may be influenced by changing parameter values. ACTPCOUNT (only parameter for ActivePanel) AECCHECK BBCREATE BBPRIO CDWAIT CMDDELETE the interval after which the statistical information about the active lines will be updated; the units are percentage of the actual filesize default: 10 check authority to execute (Monitor internal) command default: 0 (turned off) creation of user notifications (BB command) default: 0 (turned off) priority of user notifications (BB command) default: 40 time before executing an OFTP change direction after receiving a file default: 0 (turned off) remove each command and its related entries from database as soon as command ends or is being deleted default: 1 (turned on) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 213

214 Operator Manual CNSMSGS IDs of LOG messages to be sent to operator console. The following message codes are defined: A action B security E error I information L linedriver O ODETTE R report S severe error W warning + long messages default: ABEILORSW+ 214

215 rvs Parameters DTCONNnn FORCEDEND IEPRIO INITCMDS IZPRIO wait periods until an unsuccessful connection attempt is repeated. nn is the number of unsuccessful attempts (CNTRETRY in SK). There need not be a parameter for all values of nn; if a particular one is not defined, the next smaller one that is found will be used. format: MM/DD/YY HH:MM:SS defaults: increasing time intervals, so that rvs will not be kept busy trying to reach a station that may be having hardware problems. For longer wait periods, minutes have been added to the defaults, so that retries will not occur at precisely the same time: DTCONN01 "00/00/00 00:01:00" DTCONN02 "00/00/00 00:02:00" DTCONN03 "00/00/00 00:03:00" DTCONN05 "00/00/00 00:05:00" DTCONN07 "00/00/00 00:07:00" DTCONN10 "00/00/00 00:10:00" DTCONN15 "00/00/00 00:15:00" DTCONN20 "00/00/00 00:20:00" In addition, DTCONN01 is the wait period for all other rvs commands. Halting of the Monitor with Monitor-Stop: Immediate cancellation, even if the transmitter and receiver are active. NOTE: If the parameter is set at "1" the Monitor will immediately stop. default: off priority of IE-commands default: 50 execute initialization commands default: 1 (turned on) priority of IZ commands default: 70 Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 215

216 Operator Manual KEEPDAYS LANGUAGE LDSNPRIO LID LITRACELVL LMPRIO MAXCMD MAXRECL MAXSENDERS number of days, after which deleted and ended commands and their related information may be discarded during database cleanup default: 7 language for operator communication and LOG messages: D Deutsch E English default: E send priority for long data sets default: 80 local station ID default: supplied during database initialization request line tracing (between OFTP and network): 2 no tracing 3 minimum tracing (linedriver events etc.) for station specified in parameter SIDTRACE 4 detailed tracing (incl. hex dump of data) for station specified in parameter SIDTRACE 5 detailed tracing for all stations. default: 0 priority for LOG messages as external LM commands default: 10 max external commands read once default: 10 maximum record length for data sets with record format F or V to be received default: 4096 maximum number of concurrent Senders. If MAXSENDERS=0, no sender will start; default: 5 216

217 rvs Parameters MAXX25RCV MSGPRIO NUMRLOGS NUMRLSTAT OCREVAL ODTRACELVL OEXBUF maximum number of concurrently active or prestarted "listening" receiver processes for X.25 native communication default: 0 send priority for operator to operator messages default: 20 number of generations of rlog.log files default: NOLIMIT number of generations of rlstat.log files default: NOLIMIT ODETTE credit value = window size of OFTP: Maximum number of sent blocks without confirmation default: 99 request line tracing (between sender and OFTP): 0 no tracing 1 minimum tracing (request names, only) for station specified in SIDTRACE. 2 detailed tracing (parameter values etc.) for station specified in SIDTRACE. 3 detailed tracing but for all stations. default: 0 maximum ODETTE exchange buffer size in bytes (1019 for UNIX and 2048 for AS/400 the largest ODETTE cmd (SFID); OKPRIO ORETRY priority for operator commands default: 10 indicates the ODETTE Errorgroup for which a retry will be initiated after a request has been interrupted default: Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 217

218 Operator Manual OTIMEOUT QEPRIO QSPRIO RECVBLOCKS RLCOMAXSIZE RLDBMAXSIZE RLOGMAXSIZE RSTATMAXSIZE SDSNMAX SDSNPRIO SENDBLOCKS SEPRIO ODETTE time-out value (in seconds) default: 600 priority of QE commands default: 50 priority of QS commands should lie between MSGPRIO and SDSNPRIO default: 40 number of buffers or records that the Receiver writes before closing temporary data set. default: maximum file size for consol messages rlco.log default: NOLIMIT maximum filesize for logging of database actions rldb.log default: maximum filesize for log messages rlog.log default: maximum filesize for statistical logs rlstat.log default: maximum size for a data set to be considered short (in units of 1024 bytes) default: 100 send priority for short data sets default: 60 number of buffers or records that the Sender sends before looking at FORCEDEND again. default: priority for new SEs should be at least as high as the highest priority of what can be trans mitted by a SE default: 20 (same as MSGPRIO) 218

219 rvs Parameters SIDTRACE SLEEP SNARCV SSCREATE ID of station that shall be traced (if LITRACELVL or ODTRACELVL are set min. to 1 or 2. default is " " (3 blanks). If you need to trace incoming data, SIDTRACE must be set equal to the local station ID, LID. Monitor suspension time in seconds when there is no work to do, the Monitor waits this period of time, before checking, whether a command awaits processing. default: 30 enable start of SNA Transaction Program automatically on incomming calls: 0 no Transaction Program will start 1 a Transaction Program starts default: 0 creation of a send statistics record for each transfer attempt default: 0 (turned off) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 219

220 Operator Manual STATISTICS TCPIPRCV TIMESTAMP TMAXCON TSTODPRCT creation of a send statistics record in the statistics log file (rlstat.log for UNIX and Windows NT and RVS_INIT/DAT(RLSTAT) for AS/400) 0 no statistics log file 1 short form 2 detailed form of statistics 3 short form of statistics inclusive routed transfers 4 detailed form of statistics inclusive routed transfers 5 new parameters such as fileformat, state of transmission, numer of dial tries 6 statistics about deleted entries (by the user), too 7 includes all of '6' inclusive routed transfers default: 2 (detailed statistics turned on) maximum number of (concurrently) prestarted "listening" processes for TCP/IP communication: 0 no TCP/IP receiver will be started n TCP/IP receiver will be started default: 0 creation of a timestamp to destinguish data sets with the same dsname (counter) 2 Thhmmss (Time) 3 Dyymmdd.Thhmmss (Date and Time) default: 2 ( only time ) TCP/IP maximum number of connections default: 16 percentage of non-error returns from ODETTE simulation program when rvs runs in testmode; -1 requests prompting for return values. default:

221 rvs Parameters VDSNCHAR VFTYP XMCREATE range of allowable charactersto be transferred within an ODETTE transmission: ALL: no restrictions OFTPUNIXS: all capital letters, digits and the special characters. - UNIX: all letters, digits and the special characters # _ - +. ODETTE: all capital letters, digits and the special characters () -. / & CHECK_RE: same as ALL, but it is necessary that a RE exists default: ALL kind of method how data sets (with a fixed or variable format) will be converted before they will be sent. V rvs internal format, only useful for rvs for variable and fixed formats S format of ft-sinix, useful also for ft-sinix T text format, each line is terminated by carriage return and line feed; each line is converted into one output record. The record length is defined in MAXRECL. default: V (rvs internal format) creation of LOG messages with detailed information about what was transferred from and to whom after each successfull data set send or receive default: 1 (turned on) Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 221

222 Operator Manual 10 rvs Parameter Values rvs contains a number of optional and security related features which you may not need (all the time) at your installation. When activated, these features consume computer resources (processor time and disk accesses) and thus may dramatically influence performance of rvs components. As an example, consider transmission of a large data set. To be able to resume transmission after a line failure without having to start at the beginning of the file all over again, the Receiver periodically closes the incoming data set, and both Sender and Receiver store the number of transmitted bytes or records in the database. The frequency of these actions is determined by parameters SENDBLOCKS and RECVBLOCKS. Reopening and positioning a large data set involves quite a number of disk access operations and therefore is very time consuming 1. So, if most of your communication lines are very stable, you will want to set these parameters to very large values effectively disabling the restart feature of rvs. If, on the other hands, most of your lines tend to break down every few minutes, you will want to make sure that whatever has been transmitted once, will not have to be transmitted again. Note, that a large value of SENDBLOCKS may also increase the time before Senders terminate after Monitor has been stopped with stop rvs=force. Defaults have been chosen, so that rvs will work securely and with most options enabled. $RVSPATH/system/rdmini.dat (see chapter "Representation means" for the detailed description of $RVSPATH) contains a list of rvs parameters and their default values, in the order in which they are mentioned in this chapter. Use this file to restore parameter values to their defaults any time the Monitor is running by entering the operator command. 1 Transmission time for a 4.5 MB data set between two OS/2 nodes was reduced by about a factor of 10 (from more than an hour to a few minutes) by changing the values of these parameters from `10' to `10000'. 222

223 rvs Parameter Values To ensure that the Monitor is always operating with your local set of parameters, copy rdmini.dat to $RVSPATH/init/defparms.dat, customize it, and add the line OPCMD DSN=$RVSPATH/init/defparms.dat to the list of Monitor initialization commands in $RVSPATH/init/rdmini.dat Savety, Resource Consumption and Performance Besides RECVBLOCKS and SENDBLOCKS which have been discussed above, there are several other parameters that influence the balance between safety, resource consumption, and performance. OCREVAL (recommended window size 99) and OEXBUF (recommended size 4096 bytes) influence the overhead incurred by the ODETTE protocol; the larger these values, the less overhead_but the more memory will be required for Sender and Receiver. These values may be negotiated down at the start of each transmission, so that unilateral changes may have no effect. What you really determine is the maximum amount of memory you are willing to allocate to ODETTE. Searching in a large database generally takes longer than looking for something in a small one; a larger database, however, retains more information on completed transmissions. KEEPDAYS determines the number of days you want to keep information about ended or deleted transmissions (unless you use cleanup days=n, explicitly specifying the retention period in the command itself). For CMDDELETE = 1, all related entries will be removed physically from the database when a commands ends or when it is (logically) deleted. This keeps the size of the database as small as possible. If you choose this option, you should leave XMCREATE at its default value (`1'), so that detailed LOG messages will be created after sending or receiving a data set and all users should have access to the log data set ($RVSPATH/db/rlog.log) to be able to look at these messages, because the dialog interface will be unable to display any information about completed transfers. Consider using this option for continuous unattended operations. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 223

224 Operator Manual The Monitor's reaction time to new events is determined by SLEEP; this may influence for example, how long it takes, before the Monitor starts acting on an operator command. SLEEP is the period of time (in seconds) that the Monitor is suspended when there is nothing to do for it and the longer you choose this period, the less it will interfere with your other applications, but the longer you may have to wait, before it starts processing your requests. The shorter you choose this period the higher is the unproductive overhead produced by scanning the database when there is nothing to do. The time until the Monitor restarts an unsuccessful or aborted transmission is determined by the DTCONNxx parameters. The smaller these values, the sooner the transmission will start after the line is up again but the more computer time may have been wasted on unsuccessful attempts until the line is restored Limit Number of Concurrent Senders If your system is very busy or when you know, that one or more of your neighbors cannot accept more than a few incoming calls at the same time, then you want to limit the number of Senders that rvs is allowed to execute at the same time. MAXSENDERS tells MasterTransmitter rvsxmt how many Senders may run concurrently. When this number has been reached, it waits until a Sender terminates before starting the next one. If MAXSENDERS is set to 0, no Sender will be started at all. This is useful if only the partner station should establish the connection and get the queued data sets. Use the operator command activate, to send data to a specific station even if MAXSENDERS is set to

225 rvs Parameter Values 10.3 Limit Number of Concurrent X.25 or ISDN Receivers You must specify the number of concurrently active X.25 and ISDN receivers. A small number is adequate for low traffic, a higher number is required if you must be able to receive data on several connections in parallel. However, there cannot be more X.25 receivers, than virtual channels are available on your X.25 multichannel or, in case of ISDN, there cannot be more receivers than B-channels are available. Because Senders also occupy virtual channels or B channels in ISDN repectively, the number of concurrent receivers should be limited to half the total number of channels. MAXX25RCV tells MasterTransmitter rvsxmt how many Receivers must run concurrently. It prestarts as many X.25 (ISDN) receivers as indicated. If a receiver terminates, MasterTransmitter will start a new receiver, which in turn will wait for incoming calls. MAXX25RCV, if set to zero, prevents any incoming X.25 or ISDN traffic. If only SNA-LU6.2 or TCP/IP is used, it must be set to zero. On product systems, if MAXX25RCV is greater than 1, you have to define additional entries in the X.25 routing table (see chapter "6.1.3 RoutingTable" TCP/IP Receiver If you want to communicate via TCP/IP, rvs has to start a TCP/IP receiver, wich waits on incoming calls. You must set the value of the parameter TCPIPRCV. If only LU6.2 or X.25/ISDN is used, it must be set to zero. If a TCP/IP receiver accepts an incoming call, MasterTransmitter will start a new receiver on the same port, which in turn will wait for incoming calls. So, on each port, you can accept as many calls as indicated by the values MAX_IN for your local station in your stationtable $RVSPATH/init/rdstat.dat (see chapter "Representation means" for the detailed description of $RVSPATH). Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 225

226 Operator Manual 10.5 SNA Transaction Program for Windows NT To make the rvs communication program start as Transaction Program, you have to set the value of the parameter SNARCV to 1. If only TCP/IP or X.25 is used, it should be set to zero. For further informations about SNA Transaction Programs see the "Installation Manual" Optional Features Providing these optional services takes time and uses up disk space; so, you may wish to turn them off, if you do not need them. AECCHECK is a flag which tells the Monitor, to check whether the originator of the command currently being processed has the authority to issue this particular command. In a (future) multiconsole environment, this could be used to prevent certain consoles from stopping the Monitor, for example. Currently, this feature is not fully supported, so AECCHECK should remain at 0 (turned off). If BBCREATE is turned on (BBCREATE=1), user notification messages are generated and passed to the user. The default action is to send this message as UNIX mail (type mail to read the message) prevents creation of user messages. For AS/400 systems the command SNDMSG is used to send user messages. With the command DSPMSGQ you can read these messages. Statistics records will be created for every attempted transfer when flag SSCREATE is turned on (SSCREATE=1). These records contain the station ID of the neighboring rvs node as well as time and completion code of the attempted (or completed) transfer. SSCREATE=0 prevents generation of these records. Currently, no utility to analyze these records is provided. XMCREATE (create xfer message) controls generation of detailed information about successful transfers in the system log ($RVSPATH/db/rlog.log, see chapter "Representation means" for the detailed description of $RVSPATH). If XMCREATE=1 (the default), a log message will be written, whenever a data set is successfully sent to a neighboring node (even before a receipt has been received), whenever a send entry completes (after receiving receipts from all recipients), and whenever a data set has been delivered to a local user. XMCREATE=0 suppresses generation of these LOG messages. When communication errors occur, helpful trace information can be found in the trace data sets, if LITRACELVL and 226

227 rvs Parameter Values ODTRACELVL are larger than zero. Tracing can dramatically reduce performance because a lot of data has to be analyzed, formatted and written into the trace file. For normal operations, tracing should be turned off, i.e. both parameters should be set to 0. CNSMSGS controls, which LOG messages are echoed to the operator console. All messages, whose code letter is included in the character string value of CNSMSGS are written to the console (all messages are always logged, independent of the value of CNSMSGS). The additional message types `O'(ODETTE), `L' (Linedriver) and + (for long messages) can now also be used. STATISTICS controls the creation of the statistic log file. STATISTICS=1 creates the file ($RVSPATH/db/rlstat.log). It contains a line for each sended or received file with name, date, time and sender/receiver sid. STATISTICS=2 creates the same file, but with extended information (e.g. the file name for the transmission (virtual file name), the file size and command nummbers for SE, SK or IE, IZ). STATISTICS=3 is the same as STATISTICS=1, but routed filetransfer will be logged, too (i.e. SID of destination station and SID of source station). STATISTICS=4 is the same as STATISTICS=2, but routed filetransfer will be logged too. STATISTICS=5 means a detailed output in ($RVSPATH/db/rlstat.log). with new parameters such as file format, state of transmission and number of dial tries. STATISTICS=6 produces a more detailed output about deleted entries (by the user) with the cause of deletion (if specified with delcmd). STATISTICS=7 includes all of 6 with information about routing. STATISTICS=0 prevents the creation of this file Internal Parameters Several parameters are used for the internal operation of the Monitor. You may list their values with listparm, but should never modify them with setparm! Internal parameters are FORCEDEND INITCMDS set by stop rvs=force, and set by /i-command line flag. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 227

228 Operator Manual 11 Database Maintenance for Windows NT The rvs Database is the memory of rvs, both as to what happened in the past and what still has to be done. If the rvs Database is damaged or contains inconsistent entries, files may be sent twice or not at all. This chapter describes how to maintain the rvs Windows NT. Database for 11.1 Cleanup The larger the rvs Database, the more time is required by the rvs Monitor and for user access. In order to get the best possible performance rvsnt operates with an automatic cleanup function which removes information on completed or deleted transmissions from the database after a certain retention period. Information about completed actions, e.g. transmissions, are deleted immediately from the database by default. It is controlled by parameter CMDDELETE. It has the value 1 by default. If you want to keep information about completed actions for some time, set this parameter to value 0. You can determine the information retention time by using the operator command "cleanup". The general command is: cleanup days=n ss=yes/no n represents the period in units of 24 hours; with yes or no you specify whether you want to delete the associated entries in the transmission statistics, as well. You may indicate the command as a single operator command or integrate it into the c:\rvs\init\rdmini.dat initialization file. We recommend that you edit the initialization file. As a standard the file contains the entry cleanup days=3 ss=yes. That means that the completed or deleted transmissions remain stored for 72 hours in the rvs database until the rvs Monitor deletes them along with the transmission statistics. 228

229 Database Maintenance for Windows NT Carry out the following steps if you want to modify the parameters: Open the file c:\rvs\init\rdmini.dat. Click the Monitor Parameter icon in the rvs folder. Search for the cleanup entry and modify it to meet your requirements. Save the file and close the text editor. Stop the rvs Monitor and then start it again in order to activate the modified settings Backup rvsnt supports several methods of securing data. With three independent backup procedures you can save the stationtable, the user table together with the tables for resident actions and the entire rvs Database Saving the stationtable In order to save the stationtable with all the parameters for partner stations: Start the rvsnt Monitor. Open the Stationtable window with the View Stations menu command. Execute the menu command Edit Export Stationtable. The Select Backup-File dialog window then opens and displays the files which have the specification "DAT" in the rvsnt arcdir directory. Enter the file name under which you want to save the stationtable. Confirm the entry by pressing Open. rvsnt then saves the stationtable and displays any errors in the rvsnt - dump Stationtable message window. Saving has been successfully completed if the message Done with 0 errors appears. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 229

230 Operator Manual Saving the user table and follow-on processing In order to save the user table and the follow-on processing: Stop the rvs Monitor. Execute the Database Export of Jobstart Entries and User menu command. The Select Backup-File dialog window then opens and displays the files which have the specification LOG in the rvsnt arcdir directory. Enter the file name under which you want to save the tables. Confirm the entry by pressing Open. rvsnt then saves the tables and displays any errors in the rvsnt - Dump Jobstart Entries and User message window. Saving has been successfully completed if the message END appears. Start the rvsnt Monitor Saving the rvs Database If you want to save the entire rvs Database: Stop the rvs Monitor. Execute the menu command Database Export. The Select Backup-File dialog window then opens and displays the files which have the specification LOG in the rvsnt arcdir directory. Enter the file name under which you want to save the rvs Database. Confirm the entry by pressing Open. rvsnt then saves the database and displays any errors in the rvsnt - Dump database message window. Saving has been successfully completed if the message End appears. Start the rvs Monitor. 230

231 Database Maintenance for Windows NT 11.3 Restore When you have performed a backup with one of the three backup procedures you can restore the stationtable, the user table together with the tables for resident actions or the entire database Restoring the stationtable This is how you restore data for a stationtable that has been saved: Start the rvsnt Monitor. Activate the Station Table window with the View Stations menu command. Execute the menu command Edit Import StationTable. The Select file with station definitions dialog window then opens and displays the files which have the suffix DAT in the rvsnt arcdir directory. Select the file which contains the stationtable which is to be restored. Confirm your selection by pressing Open. Restoration of the data has been successfully completed if the Monitor Log window contains the message I: <ok cmd done> [RVSCNS] modst ended Restoring the user table and the follow-on processing Carry out the following steps if you want restore data for the user table and follow-on processing: Stop the rvs Monitor. Execute the Database Import of Jobstart Entries and User menu command. The Select Backup-File dialog window then opens and displays the files which have the suffix LOG in the rvsnt arcdir directory. Select the file which contains the user table and resident actions which are to be restored. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 231

232 Operator Manual Confirm your selection by pressing Open. rvsnt then opens the DOS input request rvsnt - Restore Jobstart Entries and User and restores the saved entries for follow-on processing in the rvs database. Restoration of the data has been successfully completed if the DOS window closes without error. Start the rvs Monitor Restoring the rvs Database If you want to restore the data for the entire rvs database from a backup: Stop the rvs Monitor. Execute the menu command Database Import. The Select Backup-File dialog window then opens and displays the files which have the suffix LOG in the rvsnt arcdir directory. Select the file which contains the rvs Database which is to be restored. Confirm your selection by pressing Open. rvsnt then restores the rvs Database and displays any errors in the rvsnt - Restore Database dialog window. Restoration of the data has been successfully completed if the message 0 error(s) occurred appears. Start the rvsnt Monitor New database If you want to set up a new rvs Database, you have to delete the existing one first. CAUTION: If you delete the rvs Database you will irrevocably loose any incomplete data transmissions and all settings which you have entered in the rvs Administrator. If you are absolutely sure that you want to reinstall your database carry out the following steps: Make sure that all send and receive entries have been completed. Pay attention to the send orders and receive entries which make use of the serialization function. Save the tables which you would like to restore after initialization of the rvs database is complete. For precise instructions please read the chapter "11.2 Backup". 232

233 Database Maintenance for Windows NT Execute the menu command Monitor Stop. Use the preferred backup method to save the stationtables, users tables and the job start entries or the entire rvs Database. For precise instructions see chapter "11.2 Backup". Delete the rvs Database. To do so start the Delete Database program in the rvs program file. The DOS input request will open. You have to confirm each one of the individual steps for deletion. Prior to the delete operation you can save selected entries. Click the entries to be saved in the field Save entries. In this case you will be asked under what name the entries are to be saved. Depending on the type of entries two different file types are created. When saving User and Program start the specified file name is given the extension _job. The entries can be read-in again with the menu command Database Import and/or Database Import of Jobstart Entries and User after the rvs Database has been created again. Operator Manual rvs / Rev gedas deutschland GmbH / Competence Center EDI/rvs 233