Version 6.0
Document Number GC34-6044-00
CT0ZLIE
Note |
---|
Before using this information and the product it supports, be sure to read the general information under Appendix H, Notices. |
First Edition (February 2002)
This book is based on the previous edition, LANDP Family Installation and Customization Version 5.0, GC34-5530-00, which remains applicable and current for users of LANDP(R) Version 5.0.
This edition applies to LANDP Family Version 6 (Program number 5724-B16) and to all subsequent releases and modifications, until otherwise indicated in new editions. Make sure you are using the correct edition for the level of product.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the addresses given below.
At the back of this publication is a page titled "Sending your comments to IBM". If you want to make comments, but the methods described are not available to you, please address them to:
IBM United Kingdom Laboratories, User Technologies,
Mail Point 095, Hursley Park, Winchester, Hampshire, England, SO21 2JN.
When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
(C) Copyright International Business Machines Corporation 1992, 2002. All rights reserved.
U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Utilities and Performance Tuning
This book provides information about the following IBM(R) LAN Distributed Platform (LANDP(R)) Family products:
The information provided in this book is intended to help you install the LANDP family, customize it to your own requirements, and make it operational. The book also contains information about how to customize PC/Integrator and PC/Integrator/2.
This book is written for system analysts, system programmers, and application programmers. The book, LANDP Introduction and Planning, GC34-6043, is a prerequisite.
Individuals responsible for host computer systems and host computer applications can find useful information on how to include LANDP workstations in wide area networks.
You should be familiar with the operating systems that support your LANDP environment and the programming language you are using.
If you are involved in wide area communications, you should be familiar with Transmission Control Protocol/Internet Protocol (TCP/IP), System Network Architecture (SNA) protocols and Synchronous Data Link Control (SDLC), X.25 1 Data Link Control, or Token-Ring Data Link Control.
If you are involved in LANDP internal communications, you should be familiar with NetBIOS, or with the TCP/IP implementations of the systems where you are going to use the LANDP family.
A graphic, like the one shown here, appears in the margin at the beginning
of each major section.
This graphic shows the component or components of the LANDP family to which the section relates. This example shows that the paragraph relates to LANDP for DOS and LANDP for OS/2 only. This does not necessarily imply that the item being described runs on each platform shown, but it does indicate that it affects LANDP on each platform.
Icons such as the following might appear in individual paragaphs of the
book:
This example shows that the paragraph relates to LANDP for DOS only.
In this book, all references to DB2(R) or DB2/2 apply to IBM DB2 for OS/2 and to IBM DB2 Universal Database(R).
In this book, all references to Windows apply to Microsoft Windows NT, Microsoft Windows 2000, and Microsoft Windows XP Professional, unless indicated otherwise.
In this book, all references to Linux apply to RedHat, Caldera, SuSE and TurboLinux distributions of Linux, unless indicated otherwise.
File names in Linux will usually be lower-case versions of those shown in this book. In addition, for executable Linux files (for example, the LANDP servers), there are no filename extensions. For example, the LANDP for Windows TCP/IP wide area communication server is EHCTCP.EXE and the LANDP for Linux TCP/IP wide area communication server is ehctcp.
The LANDP family is supported by the following books. In this book, references to other LANDP books use the shortened titles shown here. For the full titles, order numbers of these publications, and a comprehensive list of LANDP-related literature, refer to Appendix J, Bibliography.
For more information about LANDP, please visit our web site at:
http://www.ibm.com/software/landp/
This manual has been updated to reflect enhancements made to LANDP in Version 6. The major changes in this version are:
This part introduces the installation and customization process.
It contains the following chapter:
Introduction | "Introduction" |
|
This book contains information enabling you to install the IBM LANDP(R) licensed programs family in your organization, to customize your LANDP workgroup so that it meets your specific needs, and to produce and distribute the workgroup information. Planning your configurations and their hardware and software requirements
must be done before you start the installation and customization
process. This is covered in the LANDP Introduction and
Planning book.
|
The complete installation and customization cycle includes the following steps:
The first step is to install the LANDP family on the workstations that will be used for customization purposes. These workstations are called customization workstations. Refer to Installation for further information.
Customization is done by editing customization vectors. Vectors can be created from scratch (as described in Customization), or by migrating from FBSS (the predecessor product to LANDP) or an earlier release of LANDP (as described in Migrating and generating customization data).
When all the vectors are defined according to your configuration plans, they contain all the operational and configurational characteristics for the workstations in the workgroup.
If you want to add your own user servers, refer to Appendix B, User servers.
After installing and customizing, the run-time files for all workstations are ready to be distributed.
These files are located in the specified paths of the workstations that will be used to distribute the files to the individual workstations. These workstations are called distribution workstations.
Refer to Distribution for further information.
Figure 1 summarizes the installation, customization, and distribution process and shows where to find more information.
The remainder of the book shows how to prepare the various LANDP platforms for LANDP, utilities you can use as part of the installation and customization process, hints on performance tuning, and appendixes providing detailed customization information.
Figure 1. LANDP Installation, Customization, and Distribution Process
This part describes how to install LANDP on your customization workstation.
It contains the following chapter:
Installing the LANDP family | "Installing the LANDP family" |
There are four stages required for installation:
You should read the LANDP Introduction and Planning book for detailed information about planning considerations for your own environment.
You should consider installing LANDP on:
This is useful if the production sites are unlikely to have LANDP skills.
This is useful if the workgroups often change, or are unique to the production sites.
You can install LANDP for DOS, LANDP for OS/2, LANDP for Windows, LANDP for Linux, and the LANDP online books on the customization workstation. If your network contains DOS, OS/2, Windows, and Linux workstations, you need to install all four components in the same location on the customization machine. The order does not matter. If your network includes workstations which are running FBSS, you will need to install FBSS too.
You can run the customization process on an OS/2 or Windows customization workstation. Your choice of customization workstation is independent of the mix of workstation types in the target workgroup.
You can install LANDP Version 6.0 on top of:
You can also install:
Notes:
If you plan to use the following products, you need to have the corresponding installation diskettes to copy the required files to the required paths.
For information on copying and customizing these files, refer to the manuals of the corresponding products. See Appendix J, Bibliography. See also Installing FBSI family and 47xx banking products.
For user-written servers you need to have the server program and all the files required by the server.
The operating system in the workstation where LANDP is to be installed can be:
The installation process uses Java. If a suitable version of Java is not available on the customization machine, a Java virtual machine is installed as part of the LANDP installation. On Windows, Java Virtual Machine (JVM) 1.3 is used; on OS/2, Java Virtual Machine 1.1.8 is used.
The product registration invoked during the installation process, requires either Netscape 4.04 or later, or Microsoft Internet Explorer 4.0 or later.
The Graphical Customization Editor that is described in Graphical Customization Editor is a Java-based program and requires a Java Virtual Machine (JVM), Version 1.3 or higher.
If your customization workstation is running Windows, and JVM 1.3 is not already present, it is installed as part of the LANDP installation.
If your customization workstation is running OS/2, IBM JVM 1.3 for OS/2 can be installed from the installation CD by clicking on the 'Java Installation' icon that is in the LANDP folder. To use the Graphical Customization Editor on OS/2 you must have JVM 1.3 available on your PATH.
64MB of disk space is required for a complete installation of the LANDP family. An additional 20MB of temporary disk space is required for the installation process. The disk storage required for any other products that you need, for example those described in the previous section, must be added to the storage that is needed by LANDP.
If you are running Windows, and JVM 1.3 is not already present on your system, an additional 23MB of disk space is required for its installation.
If you are running OS/2, and JVM 1.1.8 is not already present on your system, an additional 10MB of disk space is required for its installation.
You install LANDP from the product CD.
On Windows platforms, the installation process should start automatically when the product CD is inserted into the CD drive. If installation does not start automatically, start the installation either from the command line or by using the Run option of the Start Menu.
To start the installation from the command line, enter:
x:\setupW32 where x: is the address of the CD drive
On OS/2, the installation process has to be started manually. Either use the drives icon to select setupos2 from the CD drive, or, from the command line, enter:
x:\setupos2 where x: is the address of the CD drive
The installation may take a few seconds to be initialized. The time depends on the specification of your customization workstation, and also on whether Java needs to be installed.
When the Welcome Panel is displayed, you are ready to start the installation. Use the Next and Back buttons to navigate through the installation process.
There are two setup types, Typical and Custom. If you choose Typical, all LANDP components are selected for installation. If you choose Custom, you can select only those LANDP components that you want to install.
After accepting the license agreement, you are given the opportunity of specifying the directory where you want to install LANDP. The target directory for installation must be of the form D:\xxxxxxxx, where D: is the drive and xxxxxxxx (maximum 8 characters with no spaces) is the pathname. If the directory that you specify does not exist, it is created during the installation process.
During installation, a log file ehcmst.log, containing status messages showing the progress of your installation, is built. It is placed in the installation directory.
When the installation finishes, a desktop folder, called IBM LANDP is created. See Figure 2.
Figure 2. IBM LANDP desktop folder on Windows
This folder contains useful shortcuts for invoking LANDP programs and utilities.
To get the latest LANDP device drivers, contact your IBM representative who will send you the ones that are listed in the LANDP V6 announcement letter.
Copy the following files to the EHCO600 directory:
MAGCALLS.DLL
FIOxxx.MSG and FIOxxxH.MSG message files, renamed to FIO.MSG and FIOH.MSG files. Note that xxx stands for the language identifier.
If the server supports a 4717 MSR/E, or is mouse attached, copy the FIOAUXDD.SYS file from the 4700 OS/2 Device Drivers diskette to the EHCO600 directory.
If the server supports a 4777 MSR/E or a 4778 MSR, copy the FIOSERDD.SYS file to the EHCO600 directory.
Copy the following files to the EHCO600 directory:
PINCALLS.DLL
FIOxxx.MSG and FIOxxxH.MSG message files, renamed to FIO.MSG and FIOH.MSG files. Note that xxx stands for the language identifier.
If the server supports a 4718 PIN pad, and a magnetic stripe reader/encoder server will not be loaded in the workstation, copy the FIOAUXDD.SYS file from the 4700 OS/2 Device Drivers diskette to the EHCO600 directory.
If the server supports a 4778 PIN pad:
If the server supports a 4778 PIN pad, and a magnetic stripe reader/encoder server will be loaded in the workstation, copy the PINMSR.DLL file to the EHCO600 directory.
If only the parallel port is used, no device driver is required.
If serial ports are used and 4009, 4712, 4722, 4772, 9055-002, or 9068-S01 printers are supported, copy the following files from the 4700 OS/2 Device Drivers diskette to the EHCO600 directory:
You also have to copy the FIOxxx.MSG and FIOxxxH.MSG message files, renamed to FIO.MSG and FIOH.MSG files. Note that xxx stands for the language identifier; select the files according to the language of your choice.
Copy the COM.SYS file to the EHCO600 directory. The COM.SYS file is provided with OS/2. For IBM PS/55 Models 5560 and 5580, copy the COMDMA.SYS file.
The 4748 Printer Server also provides support for the 9055-001 printer, which supersedes the 4748 printer and can be set to emulate the 4748. (The 9055-002 printer is supported by the 47X2 server.) The 9055 Printer provides more function, such as Reader/Encoder Magnetic Stripe (REMS) support, but needs its own device driver if the extra function is to be used under OS/2.
Whichever printer you are using, you should copy its dynamic link library
files from the diskette supplied with it to the EHCO600 directory as shown
below.
Table 1. 4748 Printer Server Device Driver Files under OS/2
Printer | 4748 emulation mode? (No REMS) | DLL |
---|---|---|
4748 | Not relevant | PBPCALLS.DLL |
9055 Model 1 | Yes | SCPCALLS.DLL or PBPCALLS.DLL |
9055 Model 1 | No | SCPCALLS.DLL |
9068-D01 | Yes | SCPCALLS.DLL or PBPCALLS.DLL |
9068-D01 | No | SCPCALLS.DLL |
If you are using a 4733 teller assist unit, you must copy the TCD3862.SYS device driver to the EHCO600 directory.
You have now finished the installation process for LANDP for OS/2.
To get the latest LANDP device drivers, contact your IBM representative who will send you the ones that are listed in the LANDP V6 announcement letter.
Copy the following files to the EHCN600 directory:
Copy the following files to the EHCN600 directory:
If only the parallel port is used, no device driver is required.
If serial ports are used and 4712, 4722, 4772, 9055-002, 9069, 9068-A01, 9068-A03, or 9068-S01 printers are supported, copy the following files from the Device Drivers diskette to the EHCN600 directory:
Copy the file WNTDFPRT.DLL to the EHCN600 directory.
Under Windows, the 4748 printer server does not support the 4748 printer itself, but supports a 9055-001 or 9068-D01 printer when its ID byte is set to 1E(hexadecimal).
You have now finished the installation process for LANDP for Windows.
Copy the following files to the EHCL600 directory:
Copy the following files to the EHCL600 directory:
If only the parallel port is used, no device driver is required.
If serial ports are used and 4712, 4722, 4772, 9055-002, 9069, 9068-A01, 9068-A03, or 9068-S01 printers are supported, copy the following files from the Device Drivers diskette to the EHCL600 directory:
You have now finished the installation process for LANDP for Linux.
If the server supports a 4717 MSR/E, copy the MSRE2DD.SYS device driver from the 4700 Device Drivers diskette to the EHCD600 directory.
If the server supports a 4777 MSR/E or a 4778 MSR:
If the server supports a 4718 PIN pad, copy the PIN2DD.SYS device driver from the 4700 Device Drivers diskette to the EHCD600 directory.
If the server supports a 4778 PIN pad:
If 4778 MSR capabilities are used, copy the IBM4777.SYS device driver to the EHCD600 directory.
If only the parallel port is used, no device driver is required.
If serial ports are used, and either 4712 printers or 4722 printers are supported, you must customize the printer device drivers by using the device driver customization program supplied with the 4700 Device Drivers diskette.
Version 3.0 (or later) of the device drivers is required to support the 4722 model 3 printer with the Read and Encode Magnetic Stripe (REMS) facility.
The same device drivers as those for the 4722 printer are used to support the 9055 model 2 and 9068-S01 printers.
The device driver customization program prompts you to enter a driver file
name and a driver device name. Refer to Table 2 and assign driver file names depending on the port number
and model number, as well as on whether the REMS facility is present.
Driver device names depend only on the port number to which the printer will
be connected.
Table 2. 4712 and 4722 Printer Device Driver Customization
Model | Port | Driver File Name | Driver Device Name |
---|---|---|---|
4712 | 1 | FPRT121.SYS | FPRTDD1 |
4722 | 1 | FPRT221.SYS | FPRTDD1 |
4722 REMS | 1 | FPRT221R.SYS | FPRTDD1 |
4712 | 2 | FPRT122.SYS | FPRTDD2 |
4722 | 2 | FPRT222.SYS | FPRTDD2 |
4722 REMS | 2 | FPRT222R.SYS | FPRTDD2 |
4712 | 3 | FPRT123.SYS | FPRTDD3 |
4722 | 3 | FPRT223.SYS | FPRTDD3 |
4722 REMS | 3 | FPRT223R.SYS | FPRTDD3 |
4712 | 4 | FPRT124.SYS | FPRTDD4 |
4722 | 4 | FPRT224.SYS | FPRTDD4 |
4722 REMS | 4 | FPRT224R.SYS | FPRTDD4 |
If 4772 printers are supported, the required device driver is 4772SS.SYS.
The customized device drivers must be copied to the EHCD600 directory.
You must customize the 4748 printer device drivers by using the device driver customization program supplied with the 4748 printer device drivers diskette.
The 4748 Printer Server also provides support for the 9055 Model 1 printer, which supersedes the 4748 printer and can be set to emulate the 4748. (The 9055 Model 2 printer is supported by the 47X2 server.) The 9055 Printer provides more function, such as Reader/Encoder Magnetic Stripe (REMS) support, but needs its own device driver if the extra function is to be used under DOS.
Whichever printer you are using, you should copy its device driver files
from the diskette supplied with it to the EHCD600 directory as shown
below.
Table 3. 4748 Printer Server Device Driver Files under DOS
Printer | 4748 emulation mode? (No REMS) | Driver File Name |
---|---|---|
4748 | Not relevant | FPRT48x.SYS |
9055 Model 1 | Yes | FPRTSCPx.SYS or FPRT48x.SYS |
9055 Model 1 | No | FPRTSCPx.SYS |
9068-S01 | No | FPRTSCPx.SYS |
|
The device driver customization program prompts you to enter a driver file
name and a driver device name. Refer to Table 4 and assign driver file names depending on the port
number. Driver device names depend only on the port number to which the
printer will be connected.
Table 4. 4748 Printer Device Driver Customization
Model | Port | Driver File Name | Driver Device Name |
---|---|---|---|
4748 | 1 | FPRT481.SYS | FPRTDD1 |
4748 | 2 | FPRT482.SYS | FPRTDD2 |
9055 Model 1 | 1 | FPRTSCP1.SYS | FPRTDD1 |
9055 Model 1 | 2 | FPRTSCP2.SYS | FPRTDD2 |
9068-D01 | 1 | FPRTSCP1.SYS | FPRTDD1 |
9068-D01 | 2 | FPRTSCP2.SYS | FPRTDD2 |
If you are using a 4733 teller assist unit, you need to copy the TCD386D.SYS device driver to the EHCD600 directory.
If you select NetBIOS as the transport protocol, LANDP customization assumes that you are using the IBM LAN Support Program for a non-Network Driver Interface Specifications (NDIS) device driver.
Copy the following device drivers from the LAN Support Program installation diskette to the EHCD600 directory:
If the LAN Support Program version that you are using provides the message files DXMMSG.xxx, copy also the appropriate file as DXM.MSG.
If you are using IBM LAN Client, or if there are programs other than the LANDP NetBIOS transport using NetBIOS, you must install and configure the NetBIOS directly (see Installation requirements for NetBIOS transport protocol).
If you are using IBM PC X.25 Communications Adapter, copy the following files from the installation diskette of IBM PC X.25 Communication Support Version 1.11 to the EHCD600 directory:
If you are using IBM X.25 Co-Processor/2, create the FBSSC2X directory in the installation path.
Copy the following file from the IBM X.25 Co-Processor/2 option diskette to the FBSSC2X directory:
Copy the following files from the installation diskette of IBM X.25 Co-Processor/2 Support Program to the FBSSC2X directory:
Copy the following files from the installation diskette of IBM Realtime Interface Co-Processor DOS Support to the FBSSC2X directory:
Finally, you must customize the IBM X.25 Co-Processor/2 in order to create the profiles to be used. For information about this process, refer to the corresponding manuals.
You have now finished the installation process for LANDP for DOS.
If you have developed a server, the server program, the device driver it might require, and other needed files, should all be copied to the directory specified in the SUBDIR keyword of the DEFSERV vector and, if it applies, of the DISTRIB vector. See Appendix B, User servers.
If you have developed a server that runs under LANDP for DOS, LANDP for OS/2, LANDP for Windows, or LANDP for Linux, you must copy the files to the directories specified for each of these LANDP components. Note that LANDP for DOS, LANDP for OS/2, LANDP for Windows, or LANDP for Linux, must already be installed.
After installing LANDP, you can install the following products using the procedures provided for each of them.
If you installed LANDP to remote fixed disks, run the procedures making sure that you use the same drive and path as for LANDP installation.
PC/Integrator and PC Integrator/2
When LANDP has been installed:
INSTFBSI
Complete the installation process using the PC/Integrator or PC Integrator/2 manuals. See Appendix J, Bibliography.
To use BIWP or LDA7 in an OS/2 VDM, copy the BIWP.EXE file distributed with PC/Integrator to the EHCO600 directory, and rename it VBIWP.EXE.
Similarly, to use BIWP or LDA7 in a Windows VDM, copy BIWP.EXE into the EHCN600 directory, and rename it VBIWP.EXE.
To use BPP in a Windows VDM, copy the BPP.EXE file distributed with PC/Integrator into the EHCN600 directory, and rename it VBPP.EXE
47XX Banking Products
To install the software required for:
refer to the corresponding manuals. See Appendix J, Bibliography.
To start the customization process for the banking machines software, from the EHCCUS directory enter:
FBSSBDV
Complete the customization process by following the information in the Personal Banking Machines manuals.
The LANDP V6 books are on the product CD-ROM as PDF files, for viewing and printing under Adobe Acrobat. A PDF file that contains a Master Index to the LANDP V6 books is also on the product CD-ROM.
The Adobe Acrobat Reader is available on Windows, DOS, OS/2, and Linux.
Get a free copy of the Adobe Acrobat Reader for your platform from the Internet by following the instructions given on Adobe's home page:
http://www.adobe.com
Put the online book files on a shared drive, or distribute them to the machine of each user who will need them. Don't forget to tell your users that the online books are available for them to use.
Indexing is available, but to use indexing, you need to register the index with the Adobe Acrobat Reader.
This part describes how to customize your LANDP installation to satisfy the requirements of your organization.
It contains the following chapters:
|
After you have installed LANDP for DOS, LANDP for OS/2, LANDP for Windows, or
LANDP for Linux, you design a data processing network to meet your
organization's requirements. This is called
customizing.
LANDP customization files are automatically installed when you install LANDP for DOS, LANDP for OS/2, LANDP for Windows, or LANDP for Linux. The complete customization process involves the following steps:
|
If you have customization data that has been generated earlier by the FBSS customization program, you can use the migration utility. This utility migrates all the previously defined data to your LANDP workgroup, and adds the information to the internal repository. This process is described in Migrating customization data from FBSS and in Migrating and generating customization data.
You can see and perform the customization steps by following the examples described in Appendix A, An example. These examples are also provided on the product CD-ROM and might be useful if you want to get a hands-on feeling for the customization procedures.
A graphical Customization Editor is provided to help you prepare the data to customize your system and run the related utilities. Graphical Customization Editor provides a tuturial that describes how to use the graphical editor.
Notes:
You can start your MS-DOS window using the Windows command prompt cmd.exe. Alternatively, you can start your MS-DOS window using command.com /E:2048, with CONFIG.NT specifying DOSONLY.
Before starting the customization process, it is necessary to understand some fundamental concepts involved in the process.
The customization data is specified in vector format. A vector is a set of statements defining configuration items. You define a series of vectors that are stored in files. These files are processed to generate an internal repository for retrieval purposes.
You define and process the customization data in different vector groups. Each vector group is included in a separate LANDP specification (SPC) file:
Common data vectors are common for all or for several workstations or workgroups. These include defaults, tables, record definitions, and profiles.
The vectors that contain common data must be grouped in the COMMON.SPC file located in the EHCCUS directory, created by the installation program.
Workgroup configuration data vectors are specific for each workgroup.
The vectors that contain workgroup configuration data must be grouped in a LANCONF.SPC file located in a directory created for the workgroup. For more information, refer to Customization directory structure.
The objective of modeling is to avoid specifying customization data more than once, when defining similar workgroup configurations.
A model configuration is a pattern designed only for reference purposes. Once you have defined a model configuration, you can use that model in a workgroup configuration by just referencing its name.
Models can be defined on three levels:
Thus you specify the more general information only once in the model, and make workgroup specific changes only in the respective workgroup configuration definitions.
Specific changes to a workstation model are made on the workgroup level where this model is referenced.
Another useful way of using models is nesting models.
Within a workgroup model configuration, you can refer to a workstation model when specifying the configurations of similar workstations in the workgroup. You can also reference a server model.
On workstation level, you can refer to a particular server model, either from a workstation configuration, or from a workstation model.
The vectors that contain model configuration data must be grouped in the MODELS.SPC file in the EHCCUS directory that was created by the installation program.
To locate LANDP information, the installation program creates a set of directories.
To locate customization information, you have to create some directories at workgroup level. The customization directory structure must be located in the first level subdirectory you define during installation.
The base directory for customization must be of the form D:\xxxxxxxx, where D: is the drive, and xxxxxxxx (maximum 8 characters with no spaces) is the path name.
The following figure shows the customization directory structure. The .SPC files are also included.
Figure 3. Customization Directory Structure
The COMMON.SPC and MODELS.SPC files must be located in the EHCCUS directory created by the installation program.
To locate the LANCONF.SPC files, containing workgroup configuration data, create a directory for each file.
These directories can be located in either the EHCCUS directory or any directory you create at the same level as the EHCCUS directory. You can also create a directory for each group of workgroup configurations to be defined.
If you use the EDITSPC procedure provided by the customization program to edit .SPC files, you do not need to create those directories. The procedure creates them for you.
Here are some more points you will need to know before you start to customize LANDP.
Remote customization, the process of customizing from a machine other than a designated customization workstation (for example, a LAN server), is supported. However, customization from two remote workstations at the same time is not allowed. If you try to customize, and customization is already taking place, an error message is displayed on the screen.
Notes:
The objective of embedding files is to avoid working with large .SPC files.
Instead of storing all the common or model configuration data in the COMMON.SPC or MODELS.SPC file, some data can be stored in separate files. Later, these files can be embedded in the COMMON.SPC file or in the MODELS.SPC file, using INCLUDE statements.
The format of the INCLUDE statements is:
INCLUDE=D:\xxxxxxxx\yyyyyyyy\nnnnnnnn.eee
where
The number of directory levels is limited only by the operating system.
The INCLUDE keyword must start in the first position. No blanks are allowed between the INCLUDE keyword, the = sign, and the full file path.
When you retrieve customization data from the internal repository, only a single COMMON.SPC file and a single MODELS.SPC file are created, regardless of whether you embedded files to define the customization data.
The objective of creating partial .SPC files is to avoid processing the whole COMMON.SPC or MODELS.SPC files to update the internal repository.
When processing a COMMON.SPC file or MODELS.SPC file, the common data or model configuration data in the internal repository is not deleted. The result is that some of the data remains as it is, some of the data changes according to the data in the .SPC file, and some of the data is added to the repository.
This feature enables you to use either a new profile (common data) without processing the whole COMMON.SPC file, or a new model of workstation (model configuration data) without processing the whole MODELS.SPC file.
Figure 4 shows an overview of the customization steps.
Figure 4. The Customization Steps
The boxes in Figure 4 represent the procedures you will be running during customization. Depending on your work environment, you will have to run all or just some of them.
The following sections describe, briefly, the start state for each procedure, the task being performed, and where to find more information.
The graphical customization editor can be used to complete all the steps shown, either as an alternative to, or in conjunction with, the utilities described in this chapter. The graphical customization editor can be used to load, edit, and save the customization files, and to run the validation and distribution processes. See Graphical Customization Editor for more information.
You can migrate customization data from an earlier version of FBSS to LANDP. Figure 5 shows how the MIGRATE procedure fits into the customization process.
Figure 5. Migrating customization data from FBSS
Following the MIGRATE procedure, the customization process follows the same steps as for a new LANDP workgroup.
For more information see Migrating.
|
The CREATE utility program is used to generate common data default
definitions, held as vectors in the COMMON.SPC file.
Whether you need to specify common vectors depends on the servers in your workgroup. For a reference list of which vectors you have to specify at the common level, see Vectors - a quick reference. If you do not need to specify common vectors, you can omit the CREATE step. The CREATE utility runs only in OS/2 or Windows, but the common data definitions can apply to all platforms.
|
You can display online information about the CREATE procedure. From the EHCCUS directory, enter:
CREATE ?
To start the CREATE procedure, from the EHCCUS directory, enter:
CREATE
The common data default definitions are created in the internal repository, and are held as vectors on the COMMON.SPC file.
|
This chapter explains how to perform the vector generation step. It
shows how to start the generation procedure, and describes the data generated
by the procedure.
The generation procedure reads data in the internal repository, created either by the CREATE procedure, the migration procedure, or by the validation procedure, and generates vectors in the .SPC files. When LANDP is first installed, it is advisable to run CREATE followed by GENSPEC to create a COMMON.SPC file containing the source for all the default tables. This is useful if you later want to create or change items such as keyboard definitions and translation tables. If a .SPC file already exists with the same name and in the same path, the procedure creates a backup of the existing .SPC file, with the same file name but with extension BAK. If a .BAK file corresponding to the .SPC file already exists, the procedure erases the existing .BAK file. If a .SPC file is lost, you can recover it by running the generation procedure and using the current data in the internal repository. The GENSPEC utility runs only in OS/2 or Windows. The vectors generated can apply to all platforms.
|
You can display online information about the GENSPEC procedure. From the EHCCUS directory, enter:
GENSPEC ?
To start the generation procedure, from the EHCCUS directory, enter:
GENSPEC [parm1] [parm2] [parm3] [parm4]
The default is LAN.
If the parameter is used, only the workgroup configuration specified will be processed, whatever the contents of the LANLIMIT.SPC file.
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The default is 1. For further information, refer to Return codes.
If the parameter is specified, the customization data processed is automatically removed from the internal repository. Thus, after running the generation program, the data is stored only on the .SPC files.
If the parameter is not specified, the customization data processed also remains stored in the internal repository.
The parameters can be specified in any order. Return codes generated by the generation procedure are displayed on the screen.
To avoid lengthy processing, it is strongly recommended that you run the validation procedure specifying first the COMMON parameter value. Then, if it applies, run the procedure specifying the MODELS parameter value. Finally, run the validation procedure again specifying the LAN parameter value.
In addition, when processing workgroup configuration data, you can select the workgroup configurations affected by the process. See Selecting workgroup configurations.
After generation of .SPC files, the customization data is stored in vector format in those files. The common data is stored in the COMMON.SPC file, in the EHCCUS directory.
The workgroup configuration data is stored in the LANCONF.SPC files, in the yyyyyyyy\xxxxxxxx directories, where:
The vectors in a LANCONF.SPC file are:
The model configuration data is stored in the MODELS.SPC file, in the EHCCUS directory. The vectors in that file are:
Customization vectors can be created or edited with any text editor which adheres to the specifications below. Most commonly used editors already comply with the following standards:
The EDITSPC customization program provides a procedure that, if the .SPC file or the path does not exist, creates the necessary path and opens the new .SPC file for input.
The file EDITSPC.CMD is provided in the EHCCUS directory. The EDITSPC command calls the OS/2 Enhanced Editor (EPM.EXE). If you want to use your own personal editor, you must modify the EDITSPC.CMD file accordingly.
To have the OS/2 Enhanced Editor available, you must install that option from the OS/2 installation diskettes.
The EDITSPC command also enables the LANDP customization editing tool and adds the LANDP choice to the action bar of the editor window. For information about that tool, select the View doc option in the pull-down that appears when you choose LANDP.
A graphical customization editor is provided to help the preparation of customization data. A tutorial that describes how to use the editor is included in Graphical Customization Editor.
When creating or editing customization vectors in the COMMON.SPC, LANCONF.SPC, and MODELS.SPC files, you must keep to the following syntax rules:
This rule does not apply when text is enclosed within single quotes (').
Note that the generating program transforms vectors into upper case if the target workstation is running DOS, OS/2 or Windows. However, if the target workstation is running Linux, the generating program transforms all file names into lower case.
/* VECTOR1 defines the xx server properties */
You can also use these characters to comment out vector lines.
/* VECTOR1 defines the xx server properties */ VECTOR1
The keyword is followed by an equal sign (=) and by its parameter specifications. For example:
/* VECTOR1 defines the xx server properties */ VECTOR1 KEYWORD1=PAR1
You can have one or more blank separation characters before and after the equal sign.
A comma followed by a blank skips the rest of the line. For example:
/* VECTOR1 defines the xx server properties */ VECTOR1 KEYWORD1=PAR1, KEYWORD2=PAR2, KEYWORD3=PAR3, KEYWORD4=PAR4
Any text that you put in the same line after a comma followed by a blank is disregarded.
Special characters are blanks, commas (,), single and double quotes (' and "), and parentheses (()). For example:
/* VECTOR1 defines the xx server properties */ VECTOR1 KEYWORD1=PAR1, KEYWORD2=PAR2, KEYWORD3=PAR3, KEYWORD4=PAR4, KEYWORD5='field description'
/* VECTOR1 defines the xx server properties */ VECTOR1 KEYWORD1=PAR1, KEYWORD2=PAR2, KEYWORD3=PAR3, KEYWORD4=PAR4, KEYWORD5='field description', KEYWORD6=(PAR6a,PAR6b), KEYWORD7=(PAR7a,PAR7b, PAR7c,PAR7d, PAR7e,PAR7f)
Note that no blanks are allowed within parentheses.
/* VECTOR1 defines the xx server properties */ VECTOR1 KEYWORD1=PAR1, KEYWORD2=PAR2, KEYWORD3=PAR3, KEYWORD4=PAR4, KEYWORD5='field description', KEYWORD6=(PAR6a,PAR6b), KEYWORD7=(PAR7a,PAR7b, PAR7c,PAR7d, PAR7e,PAR7f), KEYWORD8=(PAR8a,,PAR8c,,,PAR8f)
However, if the last parameter values of a keyword are defaulted, KEYWORDx=(a,b,,,), they can be omitted. The format will then be KEYWORDx=(a,b).
The use of vectors is generally related to specific servers and functional areas.
The following is a list of LANDP functional areas and the vectors which have to be specified for each of them, both on common and on workgroup level. If you are using models, you must also specify the WSMODEL or the SVRMODEL vectors. They are not mentioned in the list.
Note that, depending on your own configuration, you might have to specify other vectors as well. This list is intended to give a quick overview only. For detailed information, see Appendix C, Editing common data and Appendix D, Editing configuration data.
Some LANDP functional areas in the list have a special mark:
Functional Area | On common level | Go to page: | On workgroup level | Go to page: |
---|---|---|---|---|
ASCII-EBCDIC translation server
(EHCDBTR) | XLAT2TBL | "XLAT2TBL vector" | LWSCONF
| "LWSCONF vector" |
(**) Banking Interactive Workstation Program
(BIWP) |
DEFAULTS DISPLATT KBDBIWP KSCCBIWP KSTRBIWP LUPOOL MSRINTBL MSROUTBL PINPTBL XLATETBL |
"DEFAULTS vector" "DISPLATT vector" "KBDBIWP vector" "KSCCBIWP vector" "KSTRBIWP vector" "LUPOOL vector" "MSRINTBL vector" "MSROUTBL vector" "PINPTBL vector" "XLATETBL vector" | LWSCONF
| "LWSCONF vector" |
Banking Printer Program
(BPP) |
BPPPARM DEFAULTS FORM4710 FORM4720 LUPOOL XLATETBL |
"BPPPARM vector" "DEFAULTS vector" "FORM4710 vector" "FORM4720 vector" "LUPOOL vector" "XLATETBL vector" | LWSCONF
| "LWSCONF vector" |
Batch Machine Loader Server
(BMLS) | LWSCONF
| "LWSCONF vector" | ||
Batch Machine Operator
(BMOP) | LWSCONF
| "LWSCONF vector" | ||
CICS interface server
(EHCTRAN) | LWSCONF
LWSCONF
| "LWSCONF vector"
| ||
Compression Server
(EHCCOMP) | LWSCONF
LWSCONF
| "LWSCONF vector"
| ||
DDE Access Server
(EHCLAD) | LWSCONF
LWSCONF
| "LWSCONF vector"
| ||
(*) Device Cluster Attachment DLC
(DCADLC) |
|
| LWSCONF
| "LWSCONF vector" |
Electronic journal server
(ELECJO##) |
EJOUPRF EJOUREC RECDEF RECFIELD |
"EJOUPRF vector" "EJOUREC vector" "RECDEF vector" "RECFIELD vector" | LWSCONF
LWSCONF
| "LWSCONF vector"
|
Financial printer server
(PR47X2##) | FORM47X2 | "FORM47X2 vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
Forwarding server
(FORWARD) |
FORWPRF FORWDS LUPOOL XLATETBL |
"FORWPRF vector" "FORWDS vector" "LUPOOL vector" "XLATETBL vector" | LWSCONF
| "LWSCONF vector" |
IBM 4731, 8, 9 Personal Banking Machine
(SS#####) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector"
|
IBM 4733 Teller Assist Unit
(DTAU4733) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
IBM 4737 Self-Service Transaction Station
(SS######) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Java file distribution
(JAVA) |
|
| LWSCONF
| "LWSCONF vector" |
LANDP Link server
(EHCLINK) |
|
| LWSCONF
| "LWSCONF vector" |
Local resource manager server
(EHCLRMGR) |
|
| LWSCONF
| "LWSCONF vector" |
(**) Logical device address (LDA) 7 program
(LDA7) | LUPOOL | "LUPOOL vector" | LWSCONF
| "LWSCONF vector" |
Magnetic stripe reader/encoder server
(MSRE47##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
MQSeries Link server
(EHCMQ##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Multiple Virtual DOS Machine Relay
(EHCVDMGR) |
|
| LWSCONF
| "LWSCONF vector" |
Native X.25
(X25NAT##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Object Post Box Server
(OPBS) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
ODBC Query Server
(EHCODB##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Operator Interface
(OPER) |
|
| LWSCONF
| "LWSCONF vector" |
PIN pad server
(PINP47##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Print manager server
(PRTMGR) |
|
| LWSCONF
| "LWSCONF vector" |
Program-to-program communication (PPC) server (LU 6.2)
|
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Query server
(EHCSQL##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Remote Change Management Services
(RMCS) | LUPOOL RCMSLNF XLATETBL |
"LUPOOL vector" "RCMSLNF vector" "XLATETBL vector" | LWSCONF
| "LWSCONF vector" |
Searcher for electronic journal server and store-for-forwarding server
(SFQUERY) |
|
| LWSCONF
| "LWSCONF vector" |
Service Availability Manager.
(EHCSAM) |
|
| LWSCONF
| "LWSCONF vector" |
Shared DOS Directory
(SHRDIR) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
Shared-file distributor
(EHCSFD##) | LWSCONF
LWSCONF
| "LWSCONF vector" | ||
Shared-file replicator
(EHCSFR##) | LWSCONF
LWSCONF
| "LWSCONF vector" | ||
Shared-file server
(SHFILE##) |
COLSQTBL SHFLDBD SHFLPCB RECDEF RECFIELD SHFLSGM |
"COLSQTBL vector" "SHFLDBD vector" "SHFLPCB vector" "RECDEF vector" "RECFIELD vector" "SHFLSGM vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
SNA server
(SNA##) |
LUPOOL X25DIR |
"LUPOOL vector" "X25DIR vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
Store-for-forwarding server
(SFORFORW) |
SFORWPRF SFORWREC RECDEF RECFIELD |
"SFORWPRF vector" "SFORWREC vector" "RECDEF vector" "RECFIELD vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
Synchronous data link control server
(SDLC) | LUPOOL | "LUPOOL vector" | LWSCONF
| "LWSCONF vector" |
System manager
(SMGR) |
SMGRPRF SMGRUSER RECDEF RECFIELD |
"SMGRPRF vector" "SMGRUSER vector" "RECDEF vector" "RECFIELD vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
System manager operator
(SMOP) |
|
| LWSCONF
| "LWSCONF vector" |
Distribution
(SOFTPACK) | SOFTPACK | "SOFTPACK vector" | LWSCONF
| "LWSCONF vector" |
TCP/IP wide area communication server
(EHCTCP) |
|
| LWSCONF
| "LWSCONF vector" "LWSCONF vector" |
Token-ring data link control server
(TRDLC) | LUPOOL | "LUPOOL vector" | LWSCONF
| "LWSCONF vector" |
Trace tools
For LANDP for DOS (DDT) |
|
| LWSCONF
| "LWSCONF vector" |
Trace tools
For LANDP for OS/2 and LANDP for Windows(EHCTRACW) |
|
| LWSCONF
| "LWSCONF vector" |
X.25 data link control server
For IBM X.25 Co-Processor Adapters (X25DLC) |
|
| LWSCONF
| "LWSCONF vector" |
X.25 data link control server
For IBM X.25 Interface Co-Processor/2 (X25DLC2) |
|
| LWSCONF
| "LWSCONF vector" |
3270 Emulator
(EMU3270) |
DEFAULTS DISPLATT KBD3270 LUPOOL XLATETBL |
"DEFAULTS vector" "DISPLATT vector" "KBD3270 vector" "LUPOOL vector" "XLATETBL vector" | LWSCONF
| "LWSCONF vector" |
3287 Printer emulator
(EMU3287) |
DEFAULTS LUPOOL P3287ATT XLATETBL |
"DEFAULTS vector" "LUPOOL vector" "P3287ATT vector" "XLATETBL vector" | LWSCONF
| "LWSCONF vector" |
(*) 4700 Virtual file support
(VFILE) | LUPOOL | "LUPOOL vector" | LWSCONF
| "LWSCONF vector" |
(*) 4700 Virtual volume support
(RDVVOLS) | LUPOOL | "LUPOOL vector" | LWSCONF
| "LWSCONF vector" |
4721 Printer integrator
(PT4721) | LUPOOL | "LUPOOL vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
4721 Self service printer server
(SP4721##) |
|
| LWSCONF
LWSCONF
| "LWSCONF vector" |
4748 printer server
(PR4748##) | FORM4748 | "FORM4748 vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
4770 printer server
(PR4770##) | FORM4770 | "FORM4770 vector" | LWSCONF
LWSCONF
| "LWSCONF vector" |
The following defines the prerequisites for a workstation in order to load
a server or a functional area.
Server | Workstation Requirements |
---|---|
BIWP |
|
BMOP |
|
BPP |
|
BMLS |
|
EHCSFD## |
|
EHCSFR## |
|
EHCTCP |
|
ELECJO## |
|
EMU3270 |
|
EMU3287 |
|
FORWARD |
|
LDA7 |
|
OPBS |
|
PBMS |
|
PT4721 |
|
RCMS |
|
RDVVOLS |
|
SDLC |
|
SFORFORW |
|
SMOP |
|
SNA## |
|
TRDLC |
|
VFILE |
|
Online help, including an example, is available for each LANDP functional area.
You can use any text editor to call this online help. In the EHCHELP subdirectory of the EHCCUS directory, open with your editor:
xxxxxxxx
where xxxxxxxx stands for the name of the functional area.
A list of the names follows:
BIWP | BMLS | BMOP | BPP |
DCADLC | DTAU4733 | EHCLAD | EHCLINK |
EHCLRMGR | EHCMQ## | EHCODB## | EHCSAM |
EHCSFD## | EHCSFR## | EHCSQL## | EHCTCP |
EHCTRAN | EHCVDMGR | ELECJO## | EMU3270 |
EMU3287 | FORWARD | JAVA | LDA7 |
MSRE47## | OPBS | OPER | PBMS |
PINP47## | PPC | PR47X2## | PR4748## |
PR4770## | PRTMGR | PT4721 | RCMS |
RDVVOLS | SDLC | SFORFORW | SFQUERY |
SHFILE## | SHRDIR | SMGR | SMOP |
SNA## | SP4721## | SS##### | SS###### |
TRDLC | VFILE | X25DLC | X25DLC2 |
X25NAT## |
|
You have to run the validation procedure, VALSPEC, to validate customization
data. This procedure reads customization data from the .SPC
files, and checks the consistency of the data. The validation procedure
generates data in the internal repository.
Although the VALSPEC utility runs only in OS/2 or Windows, the data that is validated can apply to all platforms.
|
This section applies when you want to process more than one workgroup configuration at the same time.
The LANLIMIT.SPC file is located in the EHCCUS directory. You can edit the LANLIMIT.SPC file using any text editor, and specify the workgroup configurations to be processed.
INCLUDE = langroup\lanname
OMIT = langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
You cannot use both INCLUDE and OMIT statements at the same time.
Comments must start with /* and end with */.
The LANLIMIT.SPC file provided with the customization program has the following contents, and specifies that all the workgroup configurations will be processed.
INCLUDE = *
You can modify the LANLIMIT.SPC file to meet your requirements.
Example 1:
/* LANLIMIT.SPC Example 1*/ INCLUDE = GROUP2\* INCLUDE = GROUP4\CONF47
Only the workgroup configurations located in the GROUP2 directory, and the workgroup configuration named CONF47 and located in the GROUP4 directory, will be processed.
Example 2:
/* LANLIMIT.SPC Example 2 */ OMIT = GROUP6\*
All the workgroup configurations, except for those located in the GROUP6 directory, will be processed.
Example 3:
/* LANLIMIT.SPC Example 3*/ INCLUDE = GROUP8\* INCLUDE = \CONF13
Only the workgroup configurations located in the GROUP8 directory, and the workgroup configuration named CONF13 and located in the EHCCUS directory, will be processed.
The return codes generated by the validation procedure are classified into four types. The following list shows the types of return codes, starting with the least severe; an identifier for each type appears in parenthesis.
The identifier of the type of return code is displayed as the last character of the return code. For example, the following might be displayed on the screen:
01159 I Host identification default for session not defined.
This means that the validation procedure has ended with an informative return code.
When running the validation procedure, you can specify the highest severity allowed.
You can display online information about the VALSPEC procedure.
From the EHCCUS directory, enter:
VALSPEC ?
To start the validation procedure, from the EHCCUS directory, enter:
VALSPEC [parm1] [parm2] [parm3]where:
When you specify LAN or MODELS, if there is no common data in the internal repository, COMMON is also assumed. If a COMMON.SPC file is available, this file is processed to generate common data. If a COMMON.SPC file is not available, a COMMON.SPC file, containing only the DEFAULT vector with no keyword, is generated and processed.
If the parameter is used, only the workgroup configuration specified is processed, regardless of the LANLIMIT.SPC file contents.
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The default is 1. For further information, refer to Return codes.
The parameters can be specified in any order. The CUSPARM.LST file, which is generated in the EHCCUS subdirectory, contains the vectors and pointers to any problems that might arise.
If you use the OS/2 Enhanced Editor with the LANDP customization editing tool, you can also start the validation procedure using that tool.
Select the LANDP choice from the action bar in the editor window, and the Validate option in the pull-down that appears when you choose LANDP.
For further information, select the View doc option in that pull-down.
To avoid long processing, it is strongly recommended to run the validation procedure specifying first the COMMON parameter value. Then, if it applies, run the procedure specifying the MODELS parameter value. Finally, run the validation procedure again, specifying the LAN parameter value.
In addition, when processing workgroup configuration data, you can select the workgroup configurations affected by the process. See Selecting workgroup configurations.
Example
VALSPEC LAN \Sample1
This command validates the Sample1 workgroup configuration on the EHCCUS directory. Only informative return codes are allowed; higher severity return codes result in execution ending.
This part describes how to distribute your LANDP configuration software to
the workstations in your LANDP workgroup. It contains the following
chapters:
The diagram on the next page shows the stages of the distribution process.
Figure 6. LANDP Distribution Process
|
The customization process creates software to be distributed to the production workstations. This chapter describes how to obtain that software and copy it to the distribution workstation. When the software is ready for distribution:
|
To obtain the software needed by the workstations:
This step is always required, and is performed using the GENRUN procedure on the customization workstation.
The GENRUN procedure reads data in the internal repository, created either by the migration procedure or the validation procedure, and generates run-time files. For each defined workstation, it generates a GETTING.SPC file that contains information about the software to be installed. The file is located in a directory where the directory name is the workstation ID.
For information on how to run the procedure, refer to Starting the run-time generation procedure--GENRUN.
This step is optional, and can be skipped if the customization workstation will be used for distribution purposes.
If you have carried out the customization process on a unique customization workstation located in the development site, you need to copy the run-time files to the distribution workstation using the GETGLOB procedure on the customization workstation.
The GETGLOB procedure creates, on a specified drive, an image of the customization directory structure corresponding to a specified workgroup configuration. Only one copy is made of the run-time files needed by the workgroup.
If the distribution workstation cannot be accessed remotely, you can specify a diskette drive and create a diskette set with the customization image.
For information on how to run the procedure, refer to Starting the procedure for getting customization data--GETGLOB.
Although the GENRUN and GETGLOB utilities run only in OS/2 or Windows, the software generated can be distributed to all platforms.
This section applies when you want to process more than one workgroup configuration at the same time.
The LANLIMIT.SPC file is located in the EHCCUS directory. You can edit the LANLIMIT.SPC file using any text editor, and specify the workgroup configurations to be processed.
INCLUDE = langroup\lanname
OMIT = langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
You cannot use both INCLUDE and OMIT statements at the same time.
Comments must start with /* and end with */.
The LANLIMIT.SPC file provided with the customization program has the following contents, and specifies that all the workgroup configurations will be processed:
INCLUDE = *
You can modify the LANLIMIT.SPC file to meet your requirements.
Example 1:
/* LANLIMIT.SPC Example 1*/ INCLUDE = GROUP2\* INCLUDE = GROUP4\CONF47
Only the workgroup configurations located in the GROUP2 directory, and the workgroup configuration named CONF47 and located in the GROUP4 directory, will be processed.
Example 2:
/* LANLIMIT.SPC Example 2 */ OMIT = GROUP6\*
All the workgroup configurations, except for those located in the GROUP6 directory, will be processed.
Example 3:
/* LANLIMIT.SPC Example 3*/ INCLUDE = GROUP8\* INCLUDE = \CONF13
Only the workgroup configurations located in the GROUP8 directory, and the workgroup configuration named CONF13 and located in the EHCCUS directory, will be processed.
The return codes generated by both the run-time generation procedure and the getting procedure are classified into four types. The following list shows the types of return codes, starting with the least severe; an identifier for each type appears in parenthesis.
The identifier of the type of return code is displayed as the last character of the return code. For example, the following is displayed on the screen:
00011 S COMMON specifications must be processed before RUN TIME generation
This means that the run-time generation procedure has ended with a severe return code.
When running both the run-time generation and getting procedure, you can specify the highest severity allowed.
You can display online information about the GENRUN procedure.
From the EHCCUS directory, enter:
GENRUN ?
To start the run-time generation procedure, from the EHCCUS directory, enter:
GENRUN [parm1] [parm2] [parm3]
where:
The default is LAN.
When you change existing data, or add new data, to the COMMON.SPC file, you have to reprocess the workgroup configurations affected by the modifications.
If this parameter is used, only the workgroup configuration specified will be processed, no matter what the LANLIMIT.SPC file contains.
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The default is 1. For further information, refer to Return codes.
To process data created by the validation procedure or the migration procedure, with return code 2 or 3, you have to specify parm3 with a parameter value equal to, or higher than, the return code obtained.
To avoid lengthy processing, it is strongly recommended that you run the run-time generation procedure twice. Specify the COMMON parameter value on the first run and the LAN parameter value on the second run.
In addition, when processing workgroup configuration data, you can select the workgroup configurations affected by the process. See Selecting workgroup configurations.
Example
GENRUN \Sample1
This command generates the distributable workgroup configuration data files for the Sample1 workgroup on the EHCCUS directory. Only informative return codes are allowed; higher severity return codes result in execution ending.
You can display online information about the GETGLOB procedure. From the EHCCUS directory, enter:
GETGLOB ?
To start the procedure for getting customization data, from the EHCCUS directory, enter:
GETGLOB parm1 [parm2] [parm3]
where:
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The default is 1. For further information, refer to Return codes.
path
Replace path with the required path, for example D:. The default path is A:.
The GETGLOB procedure creates on the specified drive an image of the directory structure generated during customization.
Example
GETGLOB \Sample1
This command gets the customization data for the Sample1 workgroup configuration on the EHCCUS directory, and copies it to the A: drive. Only informative return codes are allowed; higher severity return codes result in execution ending.
You can accomplish this task in three ways:
This procedure reads information from the GETTING.SPC files created by the run-time generation procedure, and copies the software for each workstation to the diskette drive or path specified.
For information on how to run the procedure, refer to Starting the getting procedure--GETTING.
If the software is copied to diskettes, you should format the diskettes before writing to them. The customization program does not erase the contents of a diskette before writing on it.
For LANDP for DOS workstations that need only one diskette, you can format the diskette with the system files included, in order to perform the IPL from that diskette. Including the system files enables you to use the diskette for testing, or as backup.
If the drive on the distribution workstation that contains the customization data is shared by the production OS/2 or Windows workstations, you can run the GETTING procedure from each individual workstation. The procedure can be run simultaneously on all the workstations, using a specific parameter.
Notes:
This option requires that the distribution workstation must be integrated in the workgroup.
If you plan to use the shared DOS directory server for distribution purposes, see Using the shared DOS directory server for distribution.
To meet your requirements, the software might need to be modified. For details of a utility program to modify files, see Modifying file contents.
For information on how to set up the LANDP workstations in your workgroups, refer to:
This option uses a common disk (such as a LAN drive) shared between the distribution workstation and the individual workstation. See Distributing software using a distribution server for more information.
To distribute software to a Linux workstation, you should first distribute to a temporary directory on the target workstation, and then run the ehcsetup utility program to complete the distribution. For further details, refer to Preparing Linux workstations.
The return codes generated by both the run-time generation procedure and the getting procedure are classified into four types. The following list shows the types of return codes, starting with the least severe; an identifier for each type appears in parenthesis.
The identifier of the type of return code is displayed as the last character of the return code. For example, the following might be displayed on the screen:
00042I A file is missing. Correct the error and run GETTING again.
This means that the GETTING procedure has ended with an informative return code.
When running both the run-time generation and the GETTING procedure, you can specify the highest severity allowed.
You can display online information about the GETTING procedure. From the EHCCUS directory, enter:
GETTING ?
To start the getting procedure, from the EHCCUS directory, enter:
GETTING parm1 [WS=parm2] [parm3] [parm4] [/W:parm5] [/S]
where:
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The parameter format is:
workstation name
Replace workstation name with the name of your workstation, for example AA.
The default is all workstations (WS=ALL).
The default is 1. For further information, refer to Return codes.
Note that the only check that the GETTING program does is to ensure that all the software that is being copied to the specified path is available.
If the target drive is demountable, and WS=ALL is specified (or defaulted) the copy must be targeted at the root directory, for example:
getting \sample ws=all 1 a:\
When running GETTING on Windows, the length of each directory name must be 8 characters or less.
If, in the path you specify, a directory already exists with the workstation ID as the directory name, and the directory is not empty, the program can overwrite the contents before copying the run-time files to that directory.
The parameter is required, if you run the GETTING procedure on different workstations simultaneously.
The parameter format is:
drive:[\directory\]
Replace drive with the required drive name. Replace directory with any required directory name. Always include the final \ after the directory name.
The /S parameter is used only for workstations that act as SBC servers. The files should be copied to the read-only directory (on the SBC server) that contains the files to be shared by the SBC clients. Refer to Appendix G, "LANDP using Server Based Computing" for more information about SBC servers.
The GETTING program builds a GETTING.SPC file for each workstation. This file contains the names of all the files that are to be distributed to that workstation.
The GETTING.SPC files are built for all SBC workstations, whether or not they are SBC servers or SBC clients. In addition, for an SBC server workstation, the GETTING program builds a GETWSVR.SPC file that contains the names of all the files that are to be distributed to that server workstation. It is this file that is used to determine which files are distributed to the SBC server when /S is specified.
Example
GETTING \Sample1 WS=AA 1 A:\
This command reads the information from the GETTING.SPC files created by the GENRUN procedure in the EHCCUS directory. This information is held in the Sample1 workgroup configuration. The files for workstation AA are copied to the A: drive, home directory.
Only information return codes are allowed. Higher severity return codes result in execution ending.
To distribute the files from the distribution workstation to the individual workstations in the workgroup, you can use the shared DOS directory server.
Because this is a DOS process, all workstations involved must run DOS. This means that you must boot OS/2 and Windows workstations to DOS. The required version of the operating system is IBM DOS Version 7.1.
The process is as follows:
You must run the procedure to create diskettes (EHCDISTR) on the customization workstation. If you have installed only LANDP for OS/2 on your customization workstation, copy the LAN Support Program device drivers to the EHCCUS\EHCD600 directory before running the EHCDISTR procedure.
If you plan to boot from the diskette, you must format the diskette with the system files included, by using the /S option on the FORMAT command. This can be done only from a DOS workstation.
To create the diskette, from the EHCCUS directory, enter:
EHCDISTR parm1 WS=parm2 [parm3] [parm4] [parm5] [parm6] [parm7]
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The parameter format is:
workstation name
Replace workstation name with the name of your workstation, for example, AA.
The default is 1. For further information, refer to Return codes.
The default is REQ.
path
Replace path with the path you require. The default is A:.
The parameter applies only when you create the diskette for the distribution workstation. In this case, it is required.
The parameter value must be the path on the distribution workstation where LANDP is installed. The parameter format is:
/S:path
Replace path with the path you require.
The parameter format is:
/W:path
Replace path with the path you require. The default is the current directory.
Example
EHCDISTR \Sample1 WS=AA
This command creates the distribution diskettes for the Sample1 workgroup configuration. Workstation AA will become the server workstation.
Only informative return codes are allowed; higher severity return codes result in execution ending.
To distribute software to each workstation in the workgroup, insert the created diskette in the server or requester workstation and, if it applies, boot from that diskette.
Then, on the server workstation, run the AUTOFBSS.BAT procedure.
Finally, on the server and requester workstations, from the diskette drive, enter:
GETDATA parm1 parm2
The parameter format is:
workstation name
Replace workstation name with the name of your workstation, for example AA. It must be specified in upper case.
path
Replace path with the path you require.
Example
GETDATA CC D:\LANDP
This command is run on workstation CC. It gets the workstation configuration data from a distribution diskette, and places it on the LANDP directory on the D: drive. The remaining files are copied from the server.
To meet your own requirements, you might need to modify some files created by the customization program, or files such as CONFIG.SYS on the production workstation.
Use the EHCADD utility program to add a new statement.
EHCADD path\nnnnnnnn.eee 'statement'
where:
The statement is added at the end of the file. If the file does not exist, the utility program creates it.
Example
EHCADD C:\CONFIG.SYS 'REM updated'
Use the EHCAPPEN utility program to append a new path to an existing statement.
EHCAPPEN path\nnnnnnnn.eee 'identifier' 'entry'
where:
If the path specified as the entry parameter already exists in the statement, the command is ignored. If the statement specified in the identifier parameter does not exist, the utility program creates it.
Example
EHCAPPEN C:\CONFIG.SYS 'PATH' '.'
You can create a CMD file that contains EHCADD and EHCAPPEN statements. The EHCADD and EHCAPPEN utility programs are located in the EHCO000 directory.
To move a file from one directory to another, you can also include COPY statements, which copy files from one directory to another, and DEL statements, which delete files from a directory.
To start the getting procedure with the BAT file or the CMD file, you must include a GETTING statement as shown in the following example:
GETTING WS=%1 %2 COPY %2\PGM1.EXE X:\aaa\PGM1.EXE DEL %2\PGM1.EXE EHCADD C:\CONFIG.SYS 'LASTDRIVE=G' EHCAPPEN C:\CONFIG.SYS 'LIBPATH' 'C:\aaa\xxx;'
The task of distributing using CID is accomplished in two steps:
This step is performed using the EHCIMAGE procedure on the distribution workstation. The distribution workstation must be running OS/2 to perform this step.
The EHCIMAGE procedure uses the run-time files generated by GENRUN, copies all the necessary files onto the shared disk, and generates response files for each individual workstation.
For more information on GENRUN, see Starting the run-time generation procedure--GENRUN.
This step is performed using the EHCCINST procedure and can run on DOS, OS/2, or Windows workstations.
The EHCCINST procedure reads the response file for the workstation and copies the files for the individual workstation from the shared disk.
Note that the above process does not support the distribution of Server Based Computing (SBC) server software.
This section applies when you want to process more than one workgroup configuration at the same time.
The LANLIMIT.SPC file is located in the EHCCUS directory. You can edit the LANLIMIT.SPC file using any text editor, and specify the workgroup configurations to be processed.
INCLUDE = langroup\lanname
OMIT = langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
You cannot use both INCLUDE and OMIT statements at the same time.
Comments must start with /* and end with */.
The LANLIMIT.SPC file provided with the customization program has the following contents, and specifies that all the workgroup configurations will be processed.
INCLUDE = *
You can modify the LANLIMIT.SPC file to meet your requirements.
Example 1:
/* LANLIMIT.SPC Example 1*/ INCLUDE = GROUP2\* INCLUDE = GROUP4\CONF47
Only the workgroup configurations located in the GROUP2 directory, and the workgroup configuration named CONF47 and located in the GROUP4 directory, will be processed.
Example 2:
/* LANLIMIT.SPC Example 2 */ OMIT = GROUP6\*
All the workgroup configurations, except for those located in the GROUP6 directory, will be processed.
Example 3:
/* LANLIMIT.SPC Example 3*/ INCLUDE = GROUP8\* INCLUDE = \CONF13
Only the workgroup configurations located in the GROUP8 directory, and the workgroup configuration named CONF13 and located in the EHCCUS directory, will be processed.
You can display online information about the EHCIMAGE procedure. From the EHCCUS directory enter:
EHCIMAGE ?
To start copying the run-time files onto the shared disk, from the EHCCUS directory, enter:
EHCIMAGE [parm1] parm2 parm3
where:
If the parameter is used, only the workgroup specified will be copied, regardless of the contents of the LANLIMIT.SPC file.
The parameter format is:
langroup\lanname
Replace langroup with the name of the directory on which the workgroup configuration resides. If you omit langroup, EHCCUS is assumed.
Replace lanname with the name of the workgroup configuration.
The names of the response files created include the NetView/DM workstation name, as specified by the WSID keyword on the LWSCONF vector for the workstation. The default value for this name comprises the first six characters of the workgroup name and the two character workstation name.
Example
EHCIMAGE \DJV W:\DJV\IMG\EHC W:\DJV\RSP\EHC
This command copies files from the LANDP installation directory to a directory tree that is similar to:
W:\DJV\IMG\EHC - Root directory for this CID directory tree W:\DJV\IMG\EHC\EHCCUS - Customization root directory W:\DJV\IMG\EHC\EHCCUS\DJV - Root directory for the DJV workgroup W:\DJV\IMG\EHC\EHCCUS\DJV\AA - Information for the AA workstation W:\DJV\IMG\EHC\EHCCUS\DJV\BB - Information for the BB workstation W:\DJV\IMG\EHC\EHCCUS\DJV\CC - Information for the CC workstation W:\DJV\IMG\EHC\EHCCUS\EHCD100 - Customization files for DOS W:\DJV\IMG\EHC\EHCCUS\EHCO100 - Customization files for OS/2 W:\DJV\IMG\EHC\EHCD600 - Common files for LANDP for DOS W:\DJV\IMG\EHC\EHCO600 - Common files for LANDP for OS/2 W:\DJV\IMG\EHC\EHCN600 - Common files for LANDP for Windows W:\DJV\IMG\EHC\EHCL600 - Common files for LANDP for Linux
This might create response files with the following names:
W:\DJV\RSP\EHC\DJVAA.RSP - Response file for workstation AA W:\DJV\RSP\EHC\DJVBB.RSP - Response file for workstation BB W:\DJV\RSP\EHC\MYFILE.RSP - Response file for workstation CC ('MYFILE' specified on the WSID on the LWSCONF vector for this workstation)
EHCIMAGE checks that all the response files that are generated have unique names before performing the copy operation.
It is recommended that you use only the default response file names created by EHCIMAGE, because this reduces user error situations where the same WSID is specified by different workgroups.
If you specify the WSID vector in a LANCONF.SPC, it overrides the default name created by EHCIMAGE only for that workstation.
You can display online information about the EHCCINST procedure. From the EHCCUS directory, enter:
EHCCINST ?
To start the EHCCINST procedure, from the distribution directory, enter:
EHCCINST [/S:parm1] /T:parm2 /R:parm3 /L1:parm4 /L2:parm5
where:
Example
EHCCINST /S:X:\DJV\IMG\EHC /T:D:\EHC /R:X:\DJV\RSP\EHC\MYFILE.RSP /L1:W:\ERRS\MYFILE.ERR /L2:W:\HIST
This command installs from the CID image directory X:\DJV\IMG\EHC, using the response file X:\DJV\RSP\EHC\MYFILE.RSP. The error log file is W:\ERRS\MYFILE.ERR and the history log file is W:\HIST\MYFILE.L2.
EHCCINST does not update any system files (such as CONFIG.SYS) on the individual workstation. If such an update is required, you can update the response file for the workstation to invoke a user exit program.
Although response files are generated by EHCIMAGE, you might want to perform additional tasks before or after EHCCINST transfers the LANDP files to the individual workstations. This can be done by enhancing the response file provided by EHCIMAGE.
The response file read by EHCCINST can contain records which use the following keywords. They are processed in the order they are encountered.
The file specifications used by the COPY, INCLUDE, and USEREXIT keywords can start with one of the following substitution variables:
Example
USEREXIT=$(Sourcedir)\EXITS\PREPWS.CMD
Together with a user exit program, you can use user-written response files to update the CONFIG.SYS file for individual workstations. To do this, create new response files for each workstation of the form:
USEREXIT=W:\USEREXIT\PREPWS.CMD INCLUDE=W:\DJV\RSP\EHC\DJVAA.RSP USEREXIT=W:\USEREXIT\FINISHWS.CMD REBOOT=YES
The first user exit prepares the workstation for run-time files by ensuring that a copy of the workstation's original CONFIG.SYS has been saved.
The include statement then includes the response file created by EHCIMAGE. This allows EHCIMAGE to be rerun at a later date without losing the new responses that specify the user exits.
The final user exit then appends the CONFIG.ADD file created for the workstation to the original CONFIG.SYS and saves that as the workstation's new CONFIG.SYS.
An example of the first user exit program, PREPWS.CMD, is:
@MKDIR C:\ORIGINAL @IF NOT EXIST C:\ORIGINAL\CONFIG.SYS COPY C:\CONFIG.SYS C:\ORIGINAL
An example of the second user exit program, FINISHWS.CMD, is:
/* In REXX, since we need to be able to give a return code */ /* Create the CONFIG.SYS from the original file and */ /* the additions from LANDP */ "@COPY C:\ORIGINAL\CONFIG.SYS+%1\CONFIG.ADD C:\CONFIG.SYS" /* Return to EHCCINST indicating that a reboot is required. */ exit x2d("FE 00")
A sample change file profile for NetView DM Change Distribution Manager (CDM) is shown below:
TargetDir = D:\EHC Section Catalog Begin GlobalName = LANDP2.DISTRIBUTION.REF.5.0 ObjectType = SOFTWARE Description = 'LANDP Version 5.0 Distribution files' End Section Install Begin Program = $(SourceDir)\EHCCINST.EXE Parms = /S:$(SourceDir) /T:$(TargetDir) /R:$(ResponseFile) /L1:$(LogFile1) /L2:$(LogFile2) SourceDir = SA:\IMG\EHC WorkingDir = $(TargetDir) ResponseFile = SA:\RSP\EHC\$(WorkStatName).RSP GeneralResponsePath = SA:\RSP\EHC\$(WorkStatName).RSP Logfile1 = SB:\ERRS\$(WorkStatName).ERR Logfile2 = SB:\HIST\ End
It is best to use variables as much as possible, as this allows you to have just one change profile for all workstations in your workgroup. The $(WorkStatName) is the NetView DM workstation name, and might not be the same as your LANDP workstation name.
It is helpful to create your NetView DM workstations with the same name as your LANDP workstation names, remembering to prefix the name with the workgroup name.
LANDP can run on the following platforms:
This part describes how to prepare these platforms for the installation of
LANDP. It contains the following chapters:
|
The first part of the chapter, Installing and configuring IBM OS/2 workstations, describes the requirements for installing the LANDP for
OS/2 run-time files onto the OS/2 workstations. Some requirements
relate to a specific server.
The second part of the chapter, Modifying run-time files, describes the process of modifying the run-time files created by the customization program, according to your needs. The third part of the chapter, Installing run-time files, describes how to check for a correct installation of the run-time files. Appendix G, LANDP using Server Based Computing gives additional information about implementing LANDP for
OS/2 on Workspace on Demand.
|
The workstation files, which might typically be kept on diskettes, created for the OS/2 workstations do not contain any OS/2 system files. Therefore, before installing the LANDP for OS/2 operational files onto your OS/2 workstation, make sure that OS/2 is installed according to the existing recommendations.
The LAN adapter and protocol support (LAPS) can be provided by one of the following products, or later versions:
When working in DBCS mode, the operating system can be one of the following,
or later versions, depending on your national language:
Language | Operating system | Supported codepage |
---|---|---|
Traditional Chinese | IBM OS/2 T4.0 | 938, 950 (no defaults) |
Korean | IBM OS/2 H4.0 | 949 |
Simplified Chinese | IBM OS/2 P4.0 | 1381, 1386 (no defaults) |
This section applies to LANDP for OS/2 workstations integrated in a LANDP
workgroup that uses NetBIOS as the transport protocol.
Table 5. Maximum Requirements for LANDP for OS/2 Workstations in a LANDP Workgroup
Sessions | nn |
Commands | MIN(nn+2, 70) |
Names | 1 |
Where nn is the number of workstations in the LANDP workgroup minus 1. This value corresponds to the case when every workstation in the workgroup needs a NetBIOS session to all the workstations in the LANDP workgroup.
To optimize the resources, for each workstation you can specify a lower value, which depends on the workstation requirements. This value refers to the number of workstations the workstation is related to - those to which it provides services, or from which it receives services.
The resources have to be specified in the current PROTOCOL.INI file that is used by LAPS. You should take into consideration the requirements of other programs installed in the same workstation. If OS/2 LAN Server or LAN Requester is installed, take into account the resources assigned through the IBMLAN.INI file.
Check the following statements in the PROTOCOL.INI file:
[NETBEUI] . . . SESSIONS = nn + (number of sessions used by other NetBIOS programs) NCBS = nn+2 + (number of commands used by other NetBIOS programs) NAMES = 1 + (number of names used by other NetBIOS programs) . . .
In addition, check for the DEVICE statements that correspond to the following LAPS modules in the CONFIG.SYS file:
Finally, add the DEVICE statement corresponding to the adapter used in the workstation, and any other DEVICE statement to meet your own requirements.
For information on those statements, refer to the manuals of the corresponding products. See Appendix J, Bibliography.
This section applies to LANDP for OS/2 workstations integrated in a LANDP workgroup that uses TCP/IP as the transport protocol.
To use TCP/IP as an internal communications protocol for a LANDP workgroup, OS/2 TCP/IP must be installed and configured in those workstations defined to use this transport protocol.
For detailed information, refer to the TCP/IP manuals. See Appendix J, Bibliography.
For more information about the TCP/IP transport protocol, see Appendix E, Using TCP/IP for internal communication.
If you plan to use TCP/IP X.25 support for LANDP workstations internal communications, consider the limit of X.25 switched circuits supported by OS/2 TCP/IP, and the characteristics of this support.
It is recommended that for each workstation-to-workstation session a circuit is always available when there is data exchange. Otherwise, the response time and session lost conditions might increase dramatically.
It is possible to use both the NetBIOS and the TCP/IP transports within the same workgroup. Workstations can be configured to use either NetBIOS, or TCP/IP, or both. However, each workstation must use the same protocols as the other workstations that they need to communicate with (related workstations).
For example, if a workgroup has a SNA gateway with some clients configured to use the TCP/IP transport and some other clients configured to use the NetBIOS transport, the SNA gateway workstation must be configured to use both NetBIOS and TCP/IP transports.
When a workstation is configured to use both transport protocols the required NetBIOS resources can be reduced to be sufficient for only the number of related workstations using the NetBIOS protocol.
The LANDP for OS/2 SNA server uses the LUA interface that is provided by one of the following SNA communications providers:
The workstation containing the SNA server must be defined in the appropriate SNA communications provider as the workstation connected to the host. All logical units types 0, 1, and 2 receiving services from the LANDP SNA server must be defined in the appropriate SNA communications provider of the workstation in which the SNA server is loaded; that is, the workstation that is connected to the host computer.
In the configuration files of the appropriate SNA communications provider, you define the workstation profile and the SNA profiles. Within the SNA profiles you update the following sections:
If you do not use LU pooling support, you have to define as many LUA profiles as SNA sessions.
If you plan to use LU pooling support, you have to group LUA profiles in LU pools. In this case, the number of LUA profiles depends on your configuration requirements.
The profile name is a string of eight characters, which must comply with the following conventions:
EHCxxnn
where:
If the workstation ID has only one character followed by a blank, the profile name you have to define is EHCx@nn .
The variable nn takes the following values.
For the 3270 emulator:
You can have five sessions running simultaneously in each workstation, with the identifiers numbered from 51 (for the first session) through 55 (for the fifth session). That is, the value for nn for the 3270 emulator ranges from 51 to 55.
For the 3287 printer emulator:
You can have five sessions running simultaneously in each workstation, with the identifiers numbered from 76 (for the first session) through 80 (for the fifth session). That is, the value for nn for the 3287 printer emulator ranges from 76 to 80.
For RCMS:
The value for the variable nn for RCMS is 33.
For Forwarding:
You can have three sessions running simultaneously, with the identifiers numbered from 37 (for the first session) through 39 (for the third session).
For applications:
For DOS applications, the variable nn can take the values of 1 through 15. For DOS user servers, it can take the values of 16 through 30.
For OS/2 or Windows applications or user servers, the variable nn can take the values of 1 through 30. However, a modified SNA interface that allows for more than 30 user sessions per workstation is available when the SNA services are provided from an OS/2 or Windows workstation. When using this interface, the session identifier can be any two ASCII characters. The SNA session identifier part of the LUA profile name (defined under the appropriate SNA communications provider) can now be any two ASCII characters instead of just two decimal digits.
For 4731 and 4737:
The variable nn can take the values 34 and 35 for the 4731 Personal Banking Machine (PBM), and the value 34 only for the 4737 PBM.
When the PC/Integrator version is running in an OS/2 VDM, the variable nn takes the value 63. For the PC Integrator/2 version running in OS/2 native, the variable nn takes the value 61.
For the LDA 7 Program:
When the PC/Integrator version is running in an OS/2 VDM, the variable nn takes the value 64. For the PC Integrator/2 version running in OS/2 native, the variable nn takes the value 62.
Following is an example of communications provider definition of the SNA LUA profile names for a given workgroup, for which LU pooling is not used:
Figure 7. Example of SNA LUA profile names in a workgroup (OS/2)
These are the expected profile names in the communications provider for workstation XX (gateway):
Then you specify the following profile parameters:
The LANDP for OS/2 SNA server provides the define connection (DC) and query connection (QC) functions.
These functions require that the communications provider is installed in the workstation where the SNA server is loaded.
To use the DC and QC functions, the communications provider requires further configuration:
The following sample shows the most relevant fields in a X.25 directory entry definition:
Directory Entry Name ENTRY01 Directory Entry Remote Directory Type SNA Virtual Circuit Type SVC Link Name PHYSLINK Link Station Role Secondary Remote DTE Address 111111111
The following sample shows the most relevant fields in a SNA connection definition:
Link Name LINK0002 X25 Directory Entry ENTRY04 Node ID 05D 80002
The following sample shows the most relevant fields in a LU (LUA) definition:
LU Name EHCAA01 Host Link Name LINK0002 (to X25 SNA Connection) NAU Address 001
All the subscriber numbers that become parameter values for the DC function must be defined as X.25 directory entries. These X.25 directory entries must not be referenced by any other SNA connection.
The LANDP for OS/2 SNA server can manage cryptography.
If cryptography is managed by the SNA server, copy the following files to the D:\CMLIB\DLL path, where D is the drive where the communications provider is installed.
To run the native X.25 server, you have to provide some definitions for the communications provider configuration.
You should provide the following definitions. The given values are mandatory.
For the X.25 feature profiles:
You must create this profile.
You must create this table for incoming calls expected to be received.
To ensure that all the communications provider files needed for X.25 management are located in the \CMLIB directory, reinstall the communications provider using a correctly defined configuration file.
To run the PPC server, you have to provide some definitions for the communications provider configuration.
The definitions that can be involved are shown in this section. However, you do not need to specify all the definitions in all the cases, due to the communications provider dynamic configuration.
Most definitions and the resulting configuration should be regarded as a pattern to define your own configuration.
For the workstation profile and automatic start options:
The parameter value can be, for example, FBSSNET.
The parameter value can be, for example, LAN1WS01.
The default is End Node - No Network Node Server.
The parameter is important when communicating to a subarea host computer via switched connection.
It is recommended that you specify the same value as that specified as the name of the machine.
Specify the parameter value that meets your requirements.
The default assumed by the PPC server is FBSSTPNA.
Specify the path according to your configuration.
This value corresponds to the only operation type to be used with LANDP. It allows for multiple occurrences of the same program to run concurrently, and no PID control is made by APPC. This enables the PPC server to issue calls for conversations remotely allocated, because APPC does not control the PID of the started TP file specification (for example, PPCRATP.EXE) and regards the server as the program previously started.
The parameter value is the OS/2 path and directory where the Attach Manager should search for programs called in attach requests and not defined in the Transaction Program Definitions.
The parameter value can be, for example, FBSSNET.CICS2.
The default assumed by the PPC server is FBSSLUPA.
Specify the parameter value according to your configuration.
The default assumed by the PPC server is FBSSLULO.
The parameter value can be 00, for independent LUs, or HH for host computer dependent LUs.
Specify the parameter value according to your choice.
The default assumed by the PPC server is FBSSMODE.
The parameter value can be 1, for dependent LUs, or the value required for independent LUs (for example, 3).
The parameter value can be 0, for dependent LUs, or a higher value for independent LUs. It is recommended that the number of minimum contention winners is sufficiently high to enable all the expected Open Send requests to allocate a session.
It is recommended to specify 0, unless pacing is needed.
The parameter value can be, for example, 1920.
Specify the parameter value according to your configuration.
The parameter value is a name that identifies the connection.
The parameter value can be, for example, FBSSNET.
The parameter value can be, for example, FBSSHOST.
LANDP for OS/2 workstations configured to use the TCP/IP wide area communications server must have OS/2 TCP/IP installed and configured.
There must also be an EHCTCP.INI file to provide the information required to map LANDP sessions with SNA and PPC servers to TCP/IP protocols, ports and internet addresses. The file can be created with any text editor, but it is best practice to use the file as generated by LANDP customization. See SES&TCP on page *** for a description of the file contents.
Workstations that are configured to use the LANDP link server must have TCP/IP installed and configured.
A significant amount of planning and configuration is required for each MQSeries Queue Manager. For more details on MQSeries administration please refer to the MQSeries documentation. For book numbers and titles, refer to Appendix J, Bibliography.
You can use the CRTMQM utility to define queue managers for use with the MQSeries Link server. When defining the queue manager, you should ensure that the queue manager has the same name as specified for the MQSeries Link server during customization.
In addition to MQSeries naming requirements, the MQSeries Link server can only accept MQSeries names that comply with the following.
The LANDP customizing process also imposes some restrictions on the naming of the MQSeries queue manager. For details, see the MQM_name parameter of the LOADER EHCMQ## statement in MQSeries Link server.
A default queue manager can be defined on the MQSeries server when CRTMQM is run, by using the -q flag.
It is suggested that the MQSeries Queue Manager is defined to have a maximum message length similar to the LANDP MQ Server. This can be achieved by use of the MQSeries attribute MaxMessageLength.
The MQSeries Link server must be installed on an MQSeries Server so that the MQSeries Queue Manager is on the same workstation as the MQSeries Link server.
For security control the MQSeries Link server relies on the services of the Object Authority Manager (OAM). If access to MQSeries entities is to be controlled, the access policies for the OAM have to be defined. This should be planned as part of the configuration of the MQSeries Queue Manager.
Data conversion of messages has been enabled in the LANDP API with the GQ option EHCGQ_CONVERT. When requested, conversion is attempted by the MQSeries Queue Manager.
Queues used by the MQSeries Link server should be predefined. Some sample queue definition files have been provided to aid application development. They can be found in \EHC\EHCO600\SAMPLES.
You can use the IBM DB2 Universal Database Control Center to create and customize a database for the LANDP for OS/2 query server. The control center is part of the IBM DB2 Universal Database program suite. For information on creating and customizing a new database, refer to the IBM DB2 Universal Database User's Guide.
When defining the parameters for the new database, consider the following:
As specified during database creation by using the control center.
The name of the new database must be the same as specified for the LANDP for OS/2 query server during customization.
As customized using the configuration database panel of the control center.
This value should be greater than or equal to the number of processes customized in LANDP for OS/2 query server.
As customized using the configuration database panel of the control center.
This value should be set to 600000 milliseconds, which is the maximum number permitted by the database manager
For enhanced performance and performance tuning information, see Tuning the LANDP for OS/2 query server.
If you are migrating data definitions or Shared File data from a LANDP for DOS SHFILE## environment, refer to LANDP Programming Reference.
If Microsoft Windows 3.1 support was specified at customization time, the EHCWIN.DLL file is distributed to the workstation.
In addition, the multiple virtual DOS machine relay (EHCVDMGR) is required in the workstation.
The LANDP Java support on OS/2 can be found in the following files located in the EHCO600 directory:
To support the running of Java user servers, applications, applets or servlets on a LANDP workstation, these files should be copied to the directory on the workstation containing the LANDP files. For more details, refer to LANDP Programming Guide.
These files can be distributed automatically with the LANDP files by specifying SERVER=JAVA in the LWSCONF definition for this workstation. However, note that this method of distribution does not distribute the documentation file ldpjdocs.zip, which is located in the EHCO600 directory.
Once copied, edit CONFIG.SYS and make the following changes:
<landp dir>\ldpjava.jar
where landp dir is the directory that contains the LANDP files.
<landp dir>\ldp4722.jar
The main areas of modification are:
For a utility program to modify files, see Modifying file contents.
Depending on which applications and servers you have developed, and which devices you have installed, you might need to copy additional files.
When the shared-file server starts up, it creates the necessary shared-file directories if they do not already exist. This removes the need (which existed in some earlier LANDP releases) to call CREADB.CMD to create these directories.
The customization program creates a CONFIG.ADD file for each workstation that requires it. You should compare the CONFIG.ADD file with the CONFIG.SYS file in your workstation, and make the necessary modifications to merge them into one.
You should specify the paths for the new device drivers and other files needed.
You should take into account that the default LIBPATH statement created during OS/2 installation is:
SET LIBPATH=.;C:\OS2\DLL
and DLLs in the current directory can be accessed.
If you plan to load this server, the following statements are typical of those required in the CONFIG.SYS file. Full details of the statements can be found in the LANDP/DOS and LANDP/2 Support for Financial Magnetic stripe Readers/Encoders, SG24-4530.
If the server supports a 4717 MSR/E:
DEVICE=FIOAUXDD.SYS /M /P
where /P should be specified only if a PIN pad server will also be loaded in the workstation.
If the server supports a 4777 MSR/E:
DEVICE=FIOSERDD.SYS /Cp /M /P
where /P should be specified only if a PIN pad server will also be loaded in the workstation. The p parameter value corresponds to the COM port where the 4777 MSR/E will be attached.
If the server supports a 4778 MSR:
DEVICE=FIOSERDD.SYS /Cp /P /S
where /P should be specified only if a PIN pad server will also be loaded in the workstation. The p parameter value corresponds to the COM port where the 4778 PIN pad MSR will be attached.
If a 4777 or 4778 device is mouse attached:
DEVICE=FIOAUXDD.SYS /M
If you plan to load this server, the following statements are required in the CONFIG.SYS file.
If the server supports a 4718 PIN pad, and a magnetic stripe reader/encoder server will not be loaded in the workstation:
DEVICE=FIOAUXDD.SYS /P
If the server supports a 4778 PIN pad, and a magnetic stripe reader/encoder server will not be loaded in the workstation:
DEVICE=FIOSERDD.SYS /Cp /P
The p parameter value corresponds to the COM port where the 4778 PIN pad MSR will be attached.
If a 4778 device is mouse attached:
DEVICE=FIOAUXDD.SYS /P
If you plan to load this server, the following statement is required in the CONFIG.SYS file:
DEVICE=<drive> <path> EHCVDMVD.SYS
where:
If you plan to load this server, the following statement is required in the CONFIG.SYS file:
DEVICE=<drive> <path> OS2PRT.SYS /Dd /Bnm /Cnp
where:
The parameter value ranges from 1 to 8. The default is 1.
Valid values for both n and p range from 1 to 8, with a default of 1.
The parameter value for n ranges from 1 to 8, with a default of 1.
The parameter value for m is the baud rate of the device, in bits per second. Its value can be 9600, 4800, 2400, 1200, 600, 300, and 150. The default is 9600.
IBM 4712 and 4722 printers use the 4772PDD.SYS device driver (for more information see 4772 or 9068-S01 printer).
If you plan to load this server, the following statement is required in the CONFIG.SYS file.
DEVICE=<drive> <path> COS2PRT.SYS /D:d /B:nm
where:
The parameter value ranges from 1 to 8. The default is 1.
Valid values for both n and p range from 1 to 8, with a default of 1.
The parameter value for n ranges from 1 to 8, with a default of 1.
The parameter value for m is the baud rate of the device, in bits per second. Its value can be 9600, 4800, 2400, 1200, 600, 300, and 150. The default is 9600.
The 4772PDD.SYS driver must be loaded if you plan to use a 4772, 9068-S01, 9068-A01, or 9068-A03 printer. The 4772PDD.SYS driver can also be loaded for 4712 and 4722 printers.
The following statement is required in the CONFIG.SYS file:
DEVICE=<drive> <path> 4772PDD.SYS [/Dd] [/Bnm] [/Cnp]
where:
The parameter value ranges from 1 to 3. The default is 1.
The parameter value can be 9600, 4800, 2400, 1200, or 600. The default is 9600.
The driver has to be customized if a 4770 device, and a 47X2 or a 9068-S01 printer, is to be included. The customization program 4772OCUS.EXE is on the 4772 device driver diskette, along with a detailed description in its READ.ME file, describing how and why the customization is done.
The following statement is required in the CONFIG.SYS file if you plan to load this server for each 4748, 9055-001, or 9068-D01 printer connected to an RS-232 port:
DEVICE=<drive> <path>COM.SYS
where:
If you plan to use the 9055-001 or 9068-D01 printer, you can use the same device driver as for the 4748 printer (but it provides support only for 4748 emulation mode).
If the extra features of these printers are to be used (for example, REMS), change the device driver name in your CONFIG.SYS file to:
DEVICE=<drive> <path>FPRTSCPx.SYS [/B:bbbb] [/X]
If you plan to use a 4733 teller assist unit, you must specify the following statement in your CONFIG.SYS file:
DEVICE=TCD3862.SYS
The AUTOFBSS.CMD file contains the loading statements of the supervisor and the servers that are to reside on the workstation. The first program loaded is the supervisor.
Ensure that any modification of this file does not cause a server to be loaded before the supervisor. Application loading statements should be placed at the end of the server loading statements.
The following is an example of a AUTOFBSS.CMD file for a workstation that contains the SNA server. The name of the workstation is AB.
LOADER SPV.EXE /AB IF ERRORLEVEL 1 GOTO END LOADER LAN.EXE IF ERRORLEVEL 1 GOTO END LOADER SNA##.EXE IF ERRORLEVEL 1 GOTO END GOTO OK :END EHCFREE SPV /F EXIT :OK
If the workstation is in a LANDP workgroup that uses TCP/IP as transport protocol, specify EHCLIP.EXE instead of LAN.EXE.
If the LANDP workgroup uses mixed transport protocols, and the workstation needs to use both transport protocols, include LOADER statements for both LAN.EXE (for NetBIOS) and EHCLIP.EXE (for TCP/IP).
You can specify the EXIT command to close the OS/2 session, and leave LANDP for OS/2 running in the background. After the :OK label, you can specify an OS/2 command to invoke a LANDP for OS/2 application.
In order to get an information window about LANDP for OS/2 status, and a LANDP for OS/2 icon, you should invoke the EHCINFO utility program. EHCINFO is a LANDP utility program; it is described in LANDP Servers and System Management. Alternatively, a command line version, EHCCINFO, is available.
Most loading statements explained in this section are automatically created by the customization program, using the parameters you provided. The following commands appear in the AUTOFBSS.CMD provided by customization. Manual modifications can be done if need be. The LOADER command is used to run the servers and the supervisor, in the background. You can use any OS/2 command (such as DETACH or START) to run these programs since they are regular OS/2 programs. Note that using the LOADER command displays the return codes corresponding to the initialization process.
The LOADER program provides the optional parameter T to specify the timeout for a specific server load:
LOADER [/T:xxxx] servername serverparms
The timeout value xxxx can be up to four characters long. The minimum is 1, the maximum 3600 seconds. If a timeout is not specified, the default used when loading the server is 30 seconds.
If the initialization works without errors, the server performs initialization, then goes into a wait state until it receives a request from an application. If an initialization error occurs, it is logged in the error log file. This file is named EHCLOGxx.DAT, where xx stands for the workstation ID.
To check the type of errors, use IF ERRORLEVEL statements. If a LANDP error occurs, the corresponding return code is provided. If an OS/2 error occurs, the value 1 is provided.
For return codes during loading, refer to LANDP Problem Determination.
The following commands are used when you load the LANDP for OS/2 functional areas.
The banking printer program (BPP), part of the IBM Financial Branch System Integrator/2 program, provides financial printer support that enables IBM 4700 application programs to use IBM 4712 and IBM 4722 printers (or IBM 9068 and 9069 printers in 4722 or 4712 emulator mode respectively) that are attached to the workstation.
The loading statements for BPP are described in IBM Financial Branch System Integrator/2 Programmer's Reference. LANDP for OS/2 provides an extra parameter for BPP that allows printer sharing between the 4700 and local applications, as described below.
[/Y:nnn]
where:
nnn must be in the range 001 to 255. All three digits must be specified. A value of 000 means that BPP holds the device indefinitely (as is the case without this new parameter). BPP reacquires the device automatically when a print request is received from the 4700 application.
The PRTMON.EXE utility must be installed to enable OS/2 printing to a serial-attached printer. This utility is shipped with the IBM printer drivers.
LOADER BMLS.EXE /N:bmlname /P:progname [/D:workdir] [/T:yyy]
where:
The default is 3.
START BMOP [/U:userid] [/P:password] [/J:jobname]
where:
LOADER EHCTRAN.EXE
START EHCLAD.EXE
LOADER ELECJO##.EXE [/K:y]
where:
The size of the buffer must be large enough to hold the maximum:
LOADER FORWARD.EXE /O:vvvvvvvv.vvv [/T:wwww] [/S:xxxxxxxx.xxx] [/K:y] [/H:z] [/Z:nnnn]
where:
It can range from 1 to 6000. The default is 20 (about 1 second).
The parameter value must be the value assigned in the loading statement of the store-for-forwarding server.
LOADER LAN.EXE [/N:n[,n,...]] [/I:x] [/S:y] [/U:s[,s,...]]
where:
The parameter value can range from 0 to 3. The default is 0.
You can specify a series of up to four adapter numbers. This enables you to configure a server which provides services to workstations on two or more otherwise unconnected LANs. For example, /N:0,1,2,3, tells LAN.EXE to use all four adapters.
The parameter value can be 0 or in the range 5 through 3000. The default is 20 seconds. If a value of 0 is specified, only one attempt is made to establish each session, at startup, or after a session has been lost.
The parameter value can be 0 or in the range 10 through 127. The default is 10 seconds. A value of 0 implies no timeout.
The parameter values can range from 0 to 254, provided sufficient sessions have been defined during NetBIOS configuration. If the parameter is omitted, or specified as 0, then enough sessions for all the related workstations are used. The total number of sessions specified must be not less than the number of related workstations.
The LAN server is needed only when more than one workstation is present in a LAN. It is included during the process of creating diskettes for distribution.
LOADER EHCLIP.EXE [/N:n] [/Y] [/T] [/C[:ws-id]] [/O:o[filename]] [/J]
where:
The parameter value ranges from 1024 to 65535. The default is 52699.
Note that the screen is the usual output, and requires that LANDP Internet Protocol is loaded in the foreground, with the DETACH or START command.
LOADER EHCLINK.EXE [/T] [/E:eeeeeeee[,eeeeeeee...]] [/I:iiiiiiii[,iiiiiiii...] /L:llllllll [/A:aaaaaaaa [,aaaaaaaa...]] [/R:rrrr]] [/P:ppppp]
where:
The LANDP link server can act as both an exporter and an importer of services. It can do both at the same time, if required.
There can be any number of exporters and importers in a workgroup and in a workstation, but only one exporter on each workstation can use each TCP/IP port number.
LOADER MSRE47##.EXE
LOADER EHCMQ## [/Q:MQM_name] [/L:lllll] [/M:m] [/P:[d:[path]]] [/T:tt] [/S:ss]
where:
This parameter specifies the name of the queue manager to which the server is to connect. The parameter can be a string that conforms to the rules defined for MQSeries object naming.
Alternatively, the parameter can define an environment variable, for example, '%MQMNAME%', which is resolved when the AUTOFBSS file is processed. The special characters '%' and '/' should not be used in the queue manager name.
If this parameter is omitted or entered as spaces, EHCMQ## connects to the default MQSeries queue manager.
A log file is created for each workstation that initiates a session. The log file is named as XXhhmmss.ddd, where
The maximum length of the combined /P arguments, d and path, must not exceed 128 bytes
This parameter specifies the maximum number of different sessions that the server can process at the same time. The parameter is optional, and can be in the range 1 to 64. The default is 32.
LOADER X25NAT##.EXE
LOADER OPBS.EXE
LOADER PINP47##.EXE /M
where /M indicates that 4778 magnetic stripe reader capabilities are to be used.
LOADER PPC.EXE [/FA] [/FS] [/D:nn]
where:
When the application sends data to the partner application program, the data is stored in buffers that are automatically flushed, and is immediately sent to the partner application. Note that this option might affect the workstations and the network performance.
LOADER EHCSQL##.EXE [/C:s] [/P:y] [/S:z] [/T:x] [/F] [/W:q] [/EL]
where:
x should be slightly larger than y The defaults of 5 and 4 are suitable in most installations. If you are using Distributed Database Connection Services/2(R) (DDCS/2) to communicate with a remote DB2(R) database (for example, DB2 on a mainframe), it is advisable to increase the /T and /P parameters. Suggested values are 8 and 7.
If you use Query Server in Shared File mode, set the /W parameter high enough for a call to complete before it is timed out. When increasing this parameter, keep it less than the LAN timeout value. If the LAN times out first, the result of the query call is lost.
At load time it is not necessary to have Database Management Services started, but if the selected database is protected with a logon password, a logon procedure must have been run previously. This can be done interactively by accessing User Profile Management, or by using the LOGON command. For example:
LOGON USERID /P=PASSWORD.
An attempt to load this server before you have logged on, will not be successful, and you will get a return code of RC=152.
For information on enhanced performance and performance tuning, see Tuning the LANDP for OS/2 query server.
LOADER RCMS.EXE /I:xxx /O:yyy [/T:ttt] [/L:n] [/P:q] [/C:x] [/R:r] [/Z:nnnn]
where:
/T:1, /T:2, or /T:55
Attention: If an EHCRCMS.LOG file with n1 lines exists already, and you choose a value for the L parameter that is different from n1, your old file is destroyed and a new one is created. If you want to keep the old file, rename it or copy it to somewhere else before running the LOADER program.
The default is E.
LOADER SFQUERY.EXE [/K:y]
where y is the size, in KBs, of the buffer used to read the electronic journal and store-for-forwarding records. It ranges from 1 to 4. The default is 1.
The parameter value must be the highest of the values assigned in the loading statements of the electronic journal and store-for-forwarding servers.
This loading statement does not correspond to a separate functional area. The SFQUERY.EXE program is required by the electronic journal and the store-for-forwarding servers.
This loading statement does not correspond to a separate functional area. The EHCSAM.EXE program is required by shared-file servers when using the XLR (external logging replicator) facility. For details, see LANDP Servers and System Management.
LOADER EHCSAM.EXE
LOADER EHCSFD##.EXE [/T:nnn] [/E]
where:
The parameter is optional. The parameter value can range from 1 to 252. The default is 2.
LOADER EHCSFR##.EXE /C:confname [/T:nnn] [/E]
where:
The parameter is optional. The parameter value ranges from 1 to 252. The default is 2.
(Note In this statement, the last parameter uses the letter O, not the digit 0.)
LOADER SHFILE##.EXE [/C:confname] [/B:nnn] [/E] [/R] [/S:xxx] [/D] [/L:y] [/F:zz] [/X:ss] [/A:ttt] [/O]
where:
Another factor that must be considered is that the more buffers you have, the greater is the probability of losing index file data when the shared file server is abnormally ended. Thus, if many index buffers are allocated, and the server workstation is switched off with a transaction still in process, or if no RF function has been called, an automatic index rebuild is issued the next time the server is loaded.
This number plus the number of workstations that receive services must not be higher than 243.
The default is 0.
The parameter value can range from 10 to 245.
Range: 0-999
During XLR server initialization, LANDP:
If a majority vote of at least two SAMs cannot be achieved, LANDP issues the following messages, where xlr can be SH or BK.
EHC0587: Waiting for XLR state confirmation (Last XLR state on WS N1: xlrFILE01). EHC0588: Start other XLR WS, or use /O parameter on SHFILE## to override.
If one of the XLR workstations is permanently unavailable and no other SAM is active, the server cannot complete initialization. If you are sure that the state given in the first message is correct, and that the issuing server has up-to-date copies of the databases, you can force confirmation by restarting SHFILE## with the /O parameter. Do not use this parameter in any other circumstances.
Consider the following scenario:
Workstation X1 Workstation N1 Start as Active Start as Backup Process transactions Track transactions Machine failure Take over as new Active Repair..... Process transactions .....machine Normal shutdown Start as ???
In the last step, it is not safe for the XLR server on X1 to initialize. With /O specified, X1 would erroneously assume that it is still the active and use out-of-date data. The only thing to do is to get workstation N1 running as soon as possible. Meanwhile:
In the above scenario, you must wait until workstation N1 is initialized. The following is a scenario in which it is safe to use the /O parameter:
Workstation X1 Workstation N1 Start as Active Start as Backup Process transactions Track transactions Machine failure Take over as new Active Repair..... Process transactions ..... Normal shutdown ..... Start as Active with /O parameter
In this case, N1 has up-to-date databases and can safely be started as the active, so the use of the /O parameter is valid. When X1 or another XLR server again becomes available, it automatically becomes the backup, bringing its log and databases up-to-date by communication with N1.
LOADER SNA##.EXE [/S:nnn] [/W:x] [/C:kkkkkkk] [/R:r]
where:
The parameter is optional. The parameter value ranges from 1 to 255. The default is 1.
The parameter is optional. The parameter value can be:
The default is N.
To have cryptography managed by the SNA server, and use the default master key, specify /C.
Omit the parameter if you do not wish to have cryptography managed by the SNA server.
The value must be an integer in the range 0 (do not retry) to 8. It is advisable to specify a low value, for example 1; if the connection does not succeed after one retry, there is likely to be a problem in the communications network which needs to be resolved before the connection can succeed.
LOADER SFORFORW.EXE [/K:y]
where:
The size of the buffer must be large enough to hold the maximum:
LOADER SPV.EXE /pc-id [/CL:n] [/PRIOR:pp]
where:
This parameter is optional. It enables you to change the priority class of the SPV.EXE and all the LANDP servers. The value n has the same meaning and rules as the OS/2 system function DosSetPrty for the field Priority Class.
This parameter is optional. It enables you to change the priority level of the SPV.EXE and all the LANDP servers. The value pp has the same meaning and rules as the OS/2 system function DosSetPrty for the field Priority Delta.
LOADER SMGR.EXE /D:x /O:yyyyyyyy [/Z:nnnn]
where:
START SMOP.EXE
LOADER EHCTCP.EXE [/M:aaaaaaaa[,aaaaaaaa]] [/T]
Where:
LOADER EHCTRACW [/R:rrrr][/B:bbb][/T:xxx][/MT:mmm][/ML:mmm][/LT:lll][/LL:lll] [/PT:[d:][path]filename][/PL:[d:][path]filename]
where:
The variable rrrr can take values between 64 and 1024 + 64. The default is 394.
The variable bbb can take values greater than 1. The minimum is 2, and the default is 162.
Note that the maximum number of bbb is calculated using the formula:
[(64 ×( 1024 - 64)) ÷ (record length rrrr)]
The default is MEMORY. This parameter does not affect the log file, because a log error file is always provided by the server.
You must erase the existing Trace or Log files when you are creating new ones, otherwise the new parameters do not take effect.
Note that you must specify /T:FILE in the loading statement when you create a new Trace file.
The default for Trace is 394. The default for Log is 150.
If EHCTRACW is loaded while the supervisor is still in the loading process, the workstation ID value xx in the filenames EHCTRCxx and EHCLOGxx are sometimes given the value [!!]. This might happen if you load with the DETACH or START command. To avoid this, you can either use the LOADER command, or rename the xx value for the files afterwards.
LOADER EHCVDMGR.EXE [path\name]
where:
The configuration file is optional. The default is EHCBOXS.CFG, if it exists.
LOADER PR47X2##.EXE [/K:n]
where:
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
LOADER PR4748##.EXE [/K:n]
where:
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
To change the baud rate of the device, you can issue a MODE OS/2 command before loading the server. Specify 9600, 4800, 2400, 1200, 600, 300, or 150. The default is 1200 bits per second.
LOADER PR4770##.EXE [/K:n]
where:
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
If you select VDM relay during customization, and define the emulators to be loaded in an OS/2 VDM, the customization program creates an AUTOFBSS.BAT file with the emulator loading statements. The LSI command is used to run the emulators in the OS/2 VDM.
When you install more than one emulator, they must be run in separate OS/2 VDMs. A separate AUTOFBSS.BAT file is required for each VDM, containing the loading statements for the emulators that run in that particular VDM. To create those files, copy only the required loading statements.
FBSS (DOS) and LANDP for DOS clients (not servers) can also be run in an OS/2 VDM.
LSI VBIWP.EXE /C:atr /K:kbd /D:dis /T:at1 /P:pin /M:msi /N:mso /I:n /F:nnn
where:
nnn is the interval, in seconds, for which BIWP holds the device after its window has lost the focus. The value specified must be in the range 001 to 255. All 3 digits must be specified. A value of 000 means that BIWP holds the device indefinitely (as is the case without this parameter). BIWP reacquires the device automatically when it regains the focus.
A user server, WINFOCUS.EXE, must be installed under OS/2. The server is shipped with LANDP for OS/2 but the following steps are necessary to install it:
SERVER=WINFOCUS,
DEFSERV NAME=WINFOCUS, TYPE=OS/2, SCOPE=BOTH, DESCRIPTION='Check Window Focus', OBJECT=WINFOCUS.EXE, SUBDIR=EHCO000, LOADER=LOADER, PRIORITY=3, LANUNIQ=N, ALLCLI=N
The version of the BIWP server must be 10026 or later.
LSI EMU3270.EXE /C:atr /K:kbd /D:dis /I:n [/H:hh] [/W:www] [/B:y] [/S:xxxxxxxx] [/Z:nnnn] [/P:a] [/L:l] [/T:tt]
where:
Use this parameter, in conjunction with /W, to make the emulated alternate screen look like one of the following 3270 models:
Alternate Alternate 3270 model screen height screen width 2 24 80 3 32 80 4 43 80 5 27 132
If this parameter is omitted, the default is 24.
If this parameter is omitted, the default is 80.
If this parameter is omitted, the default is N.
If this parameter is omitted, the default is a name of eight blanks.
If this parameter is omitted, the default is 2048.
If this parameter is omitted, the default is Y.
LSI EMU3287.EXE /x /E:prt [/T:nn] [/P:HP] [/N:n]
where:
The parameter value ranges from 1 to 60. The default is 15.
If the parameter is not specified, the emulator uses the number of parallel printer ports physically installed on the workstation.
LANDP for OS/2 provides a utility program to load the LANDP emulators supported by the multiple virtual DOS machine relay and the EXFS user server support (for the LANDP 3287 printer emulator) in virtual DOS machines of OS/2.
The load servers inline (LSI) utility program can also load the FBSI banking interactive workstation program (BIWP), if the FBSI is installed. The LSI program is called as follows:
LSI [/K:m] [/X] [/N:n] [/P:zz] servername serverparms
where:
Use the following command to unload LSI and the emulators from memory:
LSI /U
See the LANDP Programming Reference book for more information about the EXFS user-written server support for 3287 printer emulation.
The EHCFREE.EXE utility is provided to unload LANDP for OS/2. You can also unload LANDP for OS/2 by issuing a supervisor function call from an application program. For more information on supervisor function calls, see LANDP Programming Reference.
The LANDP for OS/2 utility, EHCFREE.EXE, is called as follows:
d:\path\EHCFREE SPV [/p]
where:
This is the default value, and requires that the supervisor function unload LANDP for OS/2 (ES) is issued to the LANDP components.
For information on supervisor function calls, refer to the LANDP Programming Reference.
This requires that LANDP for OS/2 unloads the LANDP components through the system functions provided to cancel an OS/2 process.
The EHCFREE.EXE program errors are detected by the LAN server or the supervisor. For information on the corresponding return codes, refer to the LANDP Problem Determination manual.
The EHCFREE.EXE utility program is used to dynamically unload a LANDP for OS/2 server at LANDP run time. The command must be entered in the workstation where the specific LANDP for OS/2 server to be unloaded is located.
Note that the EHCFREE.EXE program can also be used to unload the entire LANDP for OS/2 program.
The EHCFREE.EXE program is called as follows:
d:\path\EHCFREE servername [/p]
where:
This is the default value, and requires that the supervisor function unload LANDP for OS/2 (ES) is issued to the server specified.
For information on supervisor function calls, refer to the LANDP Programming Reference.
This requires that LANDP for OS/2 ends the servers specified, through the system functions provided to cancel an OS/2 process.
The EHCFREE.EXE program errors are detected by the LAN server or the supervisor. For information on the corresponding return codes, refer to the LANDP Problem Determination manual.
The LANDP family provides a utility program to check the path where the run-time files are located. See Installing and validating system files for more information about this program.
For other utility programs also provided to be used at run-time, refer to Run-time utility programs.
The customization program creates the EHC.MSG message file, which follows the OS/2 rules. The file is provided only for the workstations with:
The EHC.MSG file must be located in the current path, or in a path specified using a DPATH statement in the CONFIG.SYS file. Note that, for device drivers, the current path is the root directory.
|
The first part of the chapter, Installing and configuring Windows workstations, describes the requirements to install the LANDP for Windows
run-time files on the Windows workstations. Some requirements are
related to a specific server.
The second part of the chapter, Modifying run-time files, describes the process of modifying the run-time files created by the customization program, according to your needs. The third part of the chapter, Loading statements for LANDP for Windows servers, describes how to check that the files have been correctly
installed.
|
The workstation files, which might typically be kept on diskettes, created for the Windows workstations do not contain any Windows system files. Therefore, before installing the LANDP for Windows operational files into your Windows workstation, make sure that Windows is installed according to the existing recommendations.
The TCP/IP support that LANDP for Windows requires is provided as part of Microsoft Windows NT Version 4.0, Windows 2000, or Windows XP Professional.
The NetBIOS support that LANDP for Windows requires is provided as part of Microsoft Windows NT Version 4.0 or Windows 2000.
The SNA support that LANDP for Windows may require is provided as part of one of the following products:
When working in DBCS mode, the operating system can be one of the following
depending on your national language:
Language | Operating system | Supported codepage |
---|---|---|
Traditional Chinese | Microsoft Windows NT V4 (Traditional Chinese) | 950 (no defaults) |
Simplified Chinese | Microsoft Windows NT V4 (Simplified Chinese) | 1386 (no defaults) |
This section applies to LANDP for Windows workstations integrated in a LANDP workgroup that uses NetBIOS as the transport protocol.
Important |
---|
The NetBIOS interface might not be available on some versions of Windows. Check your operating system documentation to confirm whether or not it is available. The NetBIOS interface must be installed and it is recommended that you configure it so that Lana (LAN adapter) Number 0 is assigned to the Network route starting with Nbf-> because LANDP uses adapter number 0 by default. The NetBIOS interface can be configured by selecting the appropriate items within the Network function of the Windows Control Panel. Alternatively, you can choose to use the ADAPTNUM keyword in LANCONF.SPC (see LWSCONF vector) or the /N parameter on loading LAN.EXE (see LAN server) to specify the Lana (LAN adapter) Number of the route starting with Nbf->. LAN adapter numbers for Windows 2000 A change to the Windows 2000 GUI has resulted in the logical adapter numbers used by the LAN.EXE program no longer being displayed to the administrator. This might cause LANDP configuration problems, because you cannot tell what the Logical Adapter Number parameter on the LOADER statement for LAN.EXE should be. Microsoft have provided a Windows 2000 utility LANACFG.EXE that enumerates the Logical Adapter Numbers as in Windows NT. If you have difficulty connecting LANDP using NetBIOS, get a copy of the LANACFG.EXE utility from the Microsoft web site. |
In a workgroup with OS/2 or DOS machines as well as Windows machines, you should change the default NETBIOS timing parameters, which are different to those provided by IBM's NetBios support. The T1, T2 and TI values should be the same on all machines. On Windows machines, these values are in the registry under the following subkey:
HKEY_LOCAL_MACHINE\SYSTEM\Services\NBF\Parameters
This section applies to LANDP for Windows workstations integrated in a LANDP workgroup that uses TCP/IP as a transport protocol.
TCP/IP must be configured in those workstations defined to use this transport protocol, so that you can use TCP/IP as an internal communications protocol for a LANDP workgroup.
For detailed information, refer to the TCP/IP information in the Microsoft Windows online documentation.
For more information about the TCP/IP transport protocol, see Appendix E, Using TCP/IP for internal communication.
It is possible to use both the NetBIOS and the TCP/IP transports within the same workgroup. Workstations can be configured to use either NetBIOS, or TCP/IP, or both. However, each workstation must use the same protocols as the other workstations that they need to communicate with (related workstations).
For example, if a workgroup has a SNA gateway with some clients configured to use the TCP/IP transport and some other clients configured to use the NetBIOS transport, the SNA gateway workstation must be configured to use both NetBIOS and TCP/IP transports.
When a workstation is configured to use both transport protocols the required NetBIOS resources can be reduced to be sufficient for only the number of related workstations using the NetBIOS protocol.
The LANDP for Windows SNA server uses the LUA interface that is provided by one of the following products:
The workstation configured to run the SNA server must be the one that is connected to the host computer. All logical units types 0, 1, and 2 receiving services from the LANDP SNA server must be defined in the SNA provider of the workstation that is connected to the host computer.
You define the workstation profile and the SNA profiles in the configuration files of the SNA provider, as follows:
Select and add appropriate information in:
If you do not use LU pooling support, you have to define as many LUA profiles as SNA sessions.
If you plan to use LU pooling support, you have to group LUA profiles in LU pools. In this case, the number of LUA profiles depends on your configuration requirements.
The profile name is a string of eight characters, which must comply with the following conventions:
EHCxxnnb
where:
If the workstation ID has only one character followed by a blank, the profile name you have to define is EHCx@nn .
The variable nn takes the following values.
For the 3270 emulator:
You can have five sessions running simultaneously in each workstation, with the identifiers numbered from 51 (for the first session) through 55 (for the fifth session). That is, the value for nn for the 3270 emulator ranges from 51 to 55.
For the 3287 printer emulator:
You can have five sessions running simultaneously in each workstation, with the identifiers numbered from 76 (for the first session) through 80 (for the fifth session). That is, the value for nn for the 3287 printer emulator ranges from 76 to 80.
For RCMS:
The value for the variable nn for RCMS is 33.
For Forwarding:
You can have three sessions running simultaneously, with the identifiers numbered from 37 (for the first session) through 39 (for the third session).
For applications:
For DOS applications, the variable nn can take the values of 1 through 15. For DOS user servers, it can take the values of 16 through 30.
For OS/2 or Windows applications or user servers, it can take the values 1 through 30. However, a modified SNA interface that allows for more than 30 user sessions per workstation is available when the SNA services are provided from an OS/2 or Windows workstation. When using this interface, the session identifier may be any two ASCII characters. The SNA session identifier part of the LUA profile name (LU0 through LU3) (defined under the appropriate SNA communications provider) may now be any two ASCII characters instead of just two decimal digits.
For 4731 and 4737:
The variable nn can take the values 34 and 35 for the 4731 Personal Banking Machine (PBM), and the value 34 only for the 4737 PBM.
When the PC/Integrator version is running in a Windows VDM, the variable nn takes the value 61 or 63.
For the LDA 7 Program:
When the PC/Integrator version is running in a Windows VDM, the variable nn takes the value 62 or 64.
For the BPP emulator:
When the PC/Integrator version is running in a Windows VDM, the variable nn takes the value 71 or 72.
Following is an example definition of the SNA LUA profile names for a given workgroup, for which LU pooling is not used:
Figure 8. Example of SNA LUA profile names in a workgroup (Windows)
These are the expected profile names in the SNA provider for workstation XX (gateway):
You then specify the following profile parameters:
LANDP for Windows workstations, configured to use the TCP/IP wide area communications server, must have Windows TCP/IP installed and configured.
There must also be an EHCTCP.INI file to provide the information required to map LANDP sessions with SNA and PPC servers to TCP/IP protocols, ports and internet addresses. The file can be created with any text editor, but it is best practice to use the file as generated by LANDP customization. See SES&TCP on page *** for a description of the file contents.
Workstations that are configured to use the LANDP link server, must have TCP/IP installed and configured.
To run the PPC server, one of the following products must be installed, configured and running:
The following information must be configured:
Refer to the documentation for your communications provider for more details, and for information about how to configure transaction programs to be started automatically.
A significant amount of planning and configuration is required for each MQSeries Queue Manager. For more details on MQSeries administration please refer to the MQSeries documentation. Book numbers and titles can be found in Appendix J, Bibliography.
You can use the CRTMQM utility to define queue managers for use with the MQSeries Link server. When defining the queue manager, you should ensure that the queue manager has the same name as specified for the MQSeries Link server during customization.
A default queue manager can be defined on the MQSeries server when CRTMQM is run, by using the -q flag.
It is suggested that the MQSeries Queue Manager is defined to have a maximum message length similar to the LANDP MQ Server. This can be achieved by use of the MQSeries attribute MaxMessageLength.
The MQSeries Link server must be installed on an MQSeries Server so that the MQSeries Queue Manager is on the same workstation as the MQSeries Link server.
In addition to MQSeries naming requirements, the MQSeries Link server can only accept MQSeries names that comply with the following.
For security control the MQSeries Link server relies on the services of the Object Authority Manager (OAM). If access to MQSeries entities is to be controlled, the access policies for the OAM have to be defined. This should be planned as part of the configuration of the MQSeries Queue Manager.
Data conversion of messages has been enabled in the LANDP API with the GQ option EHCGQ_CONVERT. When requested conversion will be attempted by the MQSeries Queue Manager.
Queues used by the MQSeries Link server should be predefined. Some sample queue definition files have been provided to aid application development. These files can be found in \EHC\EHCN600\SAMPLE.
If you are migrating data definitions or Shared File data from a LANDP for DOS SHFILE## environment, refer to LANDP Programming Reference.
The workstation must have the Windows ODBC Driver Manager and an ODBC Device Driver installed. The ODBC Device Driver must:
For instructions on installing the ODBC Driver Manager, refer to the Microsoft Windows documentation. For instructions on installing the ODBC Device Driver, refer to the vendor's instructions.
On a machine that needs to use Microsoft Visual Basic, take the following steps to install the OCX.
c:\winnt\system32\regsvr32 Landp.OCX (on Windows NT or Windows 2000) or c:\windows\system32\regsvr32 Landp.OCX (on Windows XP)
Alternatively you can run regsvr32 from anywhere as long as you specify the fully qualified path name of where you placed the OCX. For example:
x:\regsvr32 c:\directory1\directory2\Landp.OCX
An error code of 7e usually indicates that the OCX cannot be found. Check that the path name been specified fully and correctly, and that the OCX is in the current directory.
The LANDP Java support on Windows can be found in the following files located in the EHCN600 directory:
To support the running of Java user servers, applications, applets or servlets on a LANDP workstation these files should be copied to the directory on the workstation containing the LANDP files. For more details, refer to LANDP Programming Guide.
These files can be distributed automatically with the LANDP files by specifying SERVER=JAVA in the LWSCONF definition for this workstation. However, note that this method of distribution does not distribute the documentation file ldpjdocs.zip, which is located in the EHCN600 directory.
Once copied, two system environment variables need to be updated. This can be done from the Control Panel System icon.
<landp dir>\ldpjava.jar
where landp dir is the directory that contains the LANDP files.
<landp dir>\ldp4722.jar
The VDM Relay DOS stub (EHCVDSPV.COM) must be loaded in any VDM that will run LANDP/DOS applications. This can be achieved in a number of ways, some of which are covered here. The most appropriate way depends on the way the workstation is used and the applications that will be used.
Firstly, an understanding of the Windows MS-DOS command window is required.
When an MS-DOS window is first opened, it runs the CMD.EXE command interpreter. This allows the invocation of Windows programs, OS/2 16 bit programs and DOS programs. When a DOS program is detected, a new process is created and COMMAND.COM is used to start the program. Before running the DOS program, CONFIG.NT and AUTOEXEC.NT from the SYSTEM32 subdirectory of the Windows directory (usually WINNT) are processed. When the DOS program ends, CMD.EXE regains control. Subsequent programs run under either CMD or COMMAND, depending on their type.
CONFIG.NT and AUTOEXEC.NT are the default files used for MS-DOS windows and WOW (Win16 On Win32) applications. However, different files may be specified using a PIF (Program Information File). Refer to Windows documentation for details.
This ability to have different start-up files can be used in a number of ways to implement a VDM relay.
If the workstation will only be used for specific LANDP for DOS applications, it may be appropriate to invoke EHCVDSPV in-line with the application using a batch file as in the following example:
STARTAPP.BAT LOADHIGH EHCVDSPV.COM LANDPAPP EXIT
In this case the VDM DOS stub is loaded into high memory and LANDP for DOS is started. The window is closed on termination of the application. No changes to CONFIG.NT or AUTOEXEC.NT are required.
If 16-bit Windows applications are to be run and/or all MS-DOS prompts have the capability to run LANDP for DOS applications, the following should be added to AUTOEXEC.NT:
D: CD \LANDPV6 EHCVDSPV
(Assumes the LANDP runtime is in D:\LANDPV6)
In some circumstances it may be necessary to create a PIF for LANDP for DOS command prompts because of disruptions to the EHCVDSPV TSR caused by non-DOS programs. In the following example the PIF file for a shortcut to COMMAND.COM called "LANDPDOS" is modified to use CONFIG.LDP and AUTOEXEC.LDP. These files are copies of CONFIG.NT and AUTOEXEC.NT respectively, with the following additions:
Appended to CONFIG.LDP DOSONLY Appended to AUTOEXEC.LDP D: CD \LANDPV5 EHCVDSPV
Note that only DOS programs will be able to run in this window.
Loadhigh can be used to load EHCVDSPV. Refer to the Windows help for details.
EHCWINNT.DLL is the dynamic link library that contains the LANDP interface routines RMTREQ, GETRPLY, SRVINIT, GETREQ, RMTRPLY, and RMTAREQ.
EHCWINNT.DLL is loaded in the supervisor and in every other LANDP process. LANDP for Windows expects EHCWINNT.DLL to be mapped to the same virtual address in every process that uses it. If the supervisor attempts to load EHCWINNT.DLL at an address that another process has already used, the load fails. To prevent this problem arising:
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\LANDP\4.0 value= SharedMemAddress (DWORD)
Figure 9 illustrates the problem and the solution.
Figure 9. EHCWINNT loading problem and solution Possible situation without Situation with HKEY_LOCAL_MACHINE\SOFTWARE\IBM\LANDP\4.0
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\LANDP\4.0 registry entry.
EHCWINNT.DLL loaded at different virtual addresses in the supervisor
and application. This causes a failure.
registry entry. EHCWINNT.DLL always loaded at same virtual
address in the supervisor and all applications, provided supervisor is started
first.
16-bit Windows LANDP applications developed for Windows 3.x may be run on Windows NT, Windows 2000, or Windows XP Professional.
AUTOEXEC.NT must be modified as in the previous section and EHCWIN.DLL must be present in the LANDP runtime directory.
Only one LANDP/DOS application can be run in any one WOW (Win16 on Win32) VDM. However, multiple applications can be run, if they are run in a separate VDM (See Windows documentation).
SVPCPRBW may be used to verify correct installation of Win16 support.
Under Windows, programs are normally run by, and associated with, one or more users. If the user logs off, the program is terminated. As this is not desirable in some environments, there is a facility to run programs as services. By default, LANDP Servers run as services. This imposes some restrictions:
The main areas of modification are:
Depending on the applications and servers you have developed, and the devices you have installed, additional files might need to be copied.
When the shared-file server starts up, it creates the necessary shared-file directories if they do not already exist. This removes the need (which existed in earlier LANDP releases) to call CREADB.BAT to create these directories.
LANDP for Windows adds entries to the Windows registry so that LANDP servers can be run as Windows services. See also Loading statements for LANDP for Windows servers.
The AUTOFBSS.BAT file contains the loading statements of the supervisor and the servers that are to reside on the workstation. The first program loaded is the supervisor.
Ensure that any modification of this file does not cause a server to be loaded before the supervisor. Application loading statements should be placed at the end of the server loading statements.
The following is an example of an AUTOFBSS.BAT file for a workstation that contains the SNA server. The name of the workstation is AB.
LOADER %1 SPV.EXE /AB IF ERRORLEVEL 1 GOTO END LOADER %1 LAN.EXE IF ERRORLEVEL 1 GOTO END LOADER %1 SNA##.EXE IF ERRORLEVEL 1 GOTO END GOTO OK :END EHCFREE SPV /F EXIT :OK
AUTOFBSS.BAT can be invoked with one positional parameter that will be passed to the loader. Any valid loader parameters can be used. For example:
AUTOFBSS /R:
This will remove all servers referenced in AUTOFBSS.BAT from the registry. See page *** for a description of LOADER parameters.
EHCLIP.EXE should be specified instead of LAN.EXE if the workstation is integrated in a LANDP workgroup that uses TCP/IP as a transport protocol.
If the LANDP workgroup uses mixed transport protocols, and the workstation needs to use both transport protocols, include LOADER statements for both LAN.EXE (NetBIOS) and EHCLIP.EXE (TCP/IP).
You can specify the EXIT command to close the Windows session, and leave LANDP for Windows running in background. After the :OK label, you can specify a Windows command to invoke a LANDP for Windows application.
You should invoke the EHCINFO utility program to get an information window about LANDP for Windows status. EHCINFO is a LANDP utility program; it is described in LANDP Servers and System Management.
Under normal circumstances, AUTOFBSS.BAT can only be invoked by a logged on user with the necessary authority. As this may not be convenient in some environments, EHCAUTO.EXE is provided to automate LANDP startup when Windows is booted.
To automate the LANDP startup, after the LANDP installation has been verified, issue EHCAUTO from the command prompt in the LANDP runtime directory. You must have administrator authority. This registers EHCAUTO as a Windows service that will be started automatically at Windows startup. Subsequent reboots of Windows will now run EHCAUTO. In turn, EHCAUTO will invoke AUTOFBSS.BAT. Note that only servers which can run as services are supported and any other programs run from AUTOFBSS must not attempt to interact with the user. By default, EHCAUTO runs under the Local System Account (LSA) and inherits the LSA access authority (refer to Windows documentation).
Syntax:
EHCAUTO [/D:|/R:|/S:]
Parameters of EHCAUTO are:
If no parameters are given, automated startup is enabled. Administrator authority is required.
Most loading statements explained in this section are automatically created by the customization program, using the parameters you provided. The following commands appear in the AUTOFBSS.BAT file provided by customization. Manual modifications can be done if need be. The LOADER command is used to run the servers and the supervisor.
You can use any Windows command, such as the START command, to run these programs because they are regular Windows programs. Note that using the LOADER command displays the return codes corresponding to the initialization process.
The following syntax is used when servers are to be started as Windows services:
LOADER [/P:] [/T:nnn] server_name[.exe] [server_options]
The first time LOADER is run for any given server, the server will be registered as a Windows service. This registration can be done only by users with Administrators authority. When the service has been registered, any user can start the service (see the /P: parameter, below).
The LOADER options are:
The following form of the LOADER statement can be used to manage LANDP servers that are run as services:
LOADER {/D:|/R:|/S:} server_name[.exe]
A %1 parameter is generated within the LOADER statements in AUTOFBSS.BAT during customization. This is to facilitate the addition of a common option to each LOADER request. For example, a /D: loader request would display the status of all LANDP servers contained within AUTOFBSS.BAT, by entering the command:
AUTOFBSS /D:
When servers are to be run as normal applications, the format is:
LOADER [/T:nnn] /N: server[.exe] serverparms
The LOADER options are:
See Unloading LANDP for Windows servers for details of how to stop LANDP for Windows servers.
If the initialization works without errors, the server performs initialization, then goes into a wait state until it receives a request from an application. If an initialization error occurs, it is logged in the error log file.
Use IF ERRORLEVEL statements to check the type of errors. If a LANDP error occurs, the corresponding return code is provided.
For return codes during loading, refer to LANDP Problem Determination.
Errors detected by LOADER are logged to the Application section of the Windows event log. System and Security Event Log messages can also be generated by system functions invoked by LOADER. Server initialization messages may also be logged in EHCLOGxx.DAT.
The following commands are used when you load the LANDP for Windows functional areas.
LOADER ELECJO##.EXE [/K:y]
where:
The size of the buffer must be large enough to hold the maximum:
LOADER FORWARD.EXE /O:vvvvvvvv.vvv [/T:wwww] [/S:xxxxxxxx.xxx] [/K:y] [/H:z] [/Z:nnnn]
where:
It can range from 1 to 6000. The default is 20 (about 1 second).
The parameter value must be the value assigned in the loading statement of the store-for-forwarding server.
LOADER LAN.EXE [/N:n[,n,...]] [/I:x] [/S:y] [/U:s[,s,...]]
where:
The parameter value can range from 0 to 255. The default is 0.
You can specify a series of up to four adapter numbers. This enables you to configure a server which provides services to workstations on two or more otherwise unconnected LANs. For example:
/N:0,1,2,3
tells LAN.EXE to use all four adapters.
The parameter value can be 0 or in the range 5 through 3000. The default is 20 seconds. If a value of 0 is specified, only one attempt is made to establish each session, at startup, or after a session has been lost.
The parameter value can be 0 or in the range 10 through 127. The default is 10 seconds. A value of 0 implies no timeout.
The parameter values can range from 0 to 254, provided sufficient sessions have been defined during NetBIOS configuration. If the parameter is omitted, or specified as 0, then enough sessions for all the related workstations are used. The total number of sessions specified must be not less than the number of related workstations.
The LAN server is needed only when more than one workstation is present in a LAN. It is included during the process of creating diskettes for distribution.
LOADER EHCLIP.EXE [/N:n] [/Y] [/T] [/C[:ws-id]] [/O:o[filename]] [/J]
where:
The parameter value ranges from 1024 to 65535. The default is 52699.
LOADER EHCLINK.EXE [/T] [/E:eeeeeeee[,eeeeeeee...]] [/I:iiiiiiii[,iiiiiiii...] /L:llllllll [/A:aaaaaaaa[,aaaaaaaa...]] [/R:rrrr]] [/P:ppppp]
where:
The LANDP link server can act as both an exporter and an importer of services. It can do both at the same time, if required.
There can be any number of exporters and importers in a workgroup and in a workstation, but only one exporter on each workstation can use each TCP/IP port number.
LOADER MSRE47##.EXE [/C:x] [/D:n] [/O:e]
where:
The parameter is optional. The value can be specified in the range 1 through 8. The default is 1.
The parameter is optional; if used, the value specified must be 1.
The parameter is optional. The value specified can be 0 or 1. The default value 0 disables redirected device requests. The value 1 enables the requests.
LOADER EHCMQ## [/Q:MQM_name][/L::lllll] [/M:m] [/P:[d:[path]]] [/T:tt] [/S:ss]
where:
This parameter specifies the name of the queue manager to which the server is to connect. The parameter can be a string that conforms to the rules defined for MQSeries object naming.
Alternatively, the parameter can define an environment variable, for example, '%MQMNAME%', which is resolved when the AUTOFBSS file is processed. The special characters '%' and '/' should not be used in the queue manager name.
If this parameter is omitted or entered as spaces, EHCMQ## connects to the default MQSeries queue manager.
A log file is created for each workstation that initiates a session. The log file is named as XXhhmmss.ddd, where
The maximum length of the combined /P arguments, d and path, must not exceed 128 bytes .
This parameter specifies the maximum number of different sessions that the server can process at the same time. The parameter is optional and can be in the range from 1 to 64. The default is 32.
LOADER PINP47##.EXE [/M] [/C:x]
where:
The parameter is optional.
The parameter is optional. The value that can be specified is in the range 1 to 8. The default is 1.
LOADER EHCODB##.EXE [/C:datasource] [/T:tt] [/MT:mm] [/S:ss] [/W:zz] [/EL] [/A]
where:
LOADER PPC.EXE [/FA] [/FS] [/D:nn]
where:
When the application sends data to the partner application program, the data is stored in buffers that are automatically flushed, and is immediately sent to the partner application. Note that this option may affect the workstations and the network performance.
LOADER RCMS.EXE /I:xxx /O:yyy [/T:ttt] [/L:n] [/P:q] [/C:x] [/R:r] [/Z:nnnn]
where:
/T:1, /T:2, or /T:55
Attention: If an EHCRCMS.LOG file with n1 lines exists already, and you choose a value for the L parameter that is different from n1, your old file will be destroyed and a new one created. If you want to keep the old file, rename it or copy it to somewhere else before running the LOADER program.
The default is E.
LOADER SFQUERY.EXE [/K:y]
where y is the size, in KBs, of the buffer used to read the electronic journal and store-for-forwarding records. It ranges from 1 to 4. The default is 1.
The parameter value must be the highest of the values assigned in the loading statements of the electronic journal and store-for-forwarding servers.
This loading statement does not correspond to a separate functional area. The SFQUERY.EXE program is required by the electronic journal and the store-for-forwarding servers.
This loading statement does not correspond to a separate functional area. The EHCSAM.EXE program is required by shared-file servers when using the XLR (external logging replicator) facility. For details, see LANDP Servers and System Management.
LOADER EHCSAM.EXE
(Note In this statement, the last parameter uses the letter O, not the digit 0.)
LOADER SHFILE##.EXE [/C:confname] [/B:nnn] [/E] [/R] [/S:xxx] [/L:y] [/F:zz] [/X:ss] [/A:ttt] /O
where:
Another factor that must be considered is that the more buffers you have, the greater is the probability of losing index file data when the shared file server is abnormally ended. Thus, if many index buffers are allocated, and the server workstation is switched off with a transaction still in process, or if no RF function has been called, an automatic index rebuild is issued the next time the server is loaded.
This number plus the number of workstations that receive services must not be higher than 243.
The default is 0.
The parameter value can range from 10 to 245.
Range: 0-999
During XLR server initialization, LANDP:
If a majority vote of at least two SAMs cannot be achieved, LANDP issues the following messages, where xlr can be SH or BK.
EHC0587: Waiting for XLR state confirmation (Last XLR state on WS N1: xlrFILE01). EHC0588: Start other XLR WS, or use /O parameter on SHFILE## to override.
If one of the XLR workstations is permanently unavailable and no other SAM is active, the server cannot complete initialization. If you are sure that the state given in the first message is correct, and that the issuing server has up-to-date copies of the databases, you can force confirmation by restarting SHFILE## with the /O parameter. Do not use this parameter in any other circumstances.
Consider the following scenario:
Workstation X1 Workstation N1 Start as Active Start as Backup Process transactions Track transactions Machine failure Take over as new Active Repair..... Process transactions .....machine Normal shutdown Start as ???
In the last step, it is not safe for the XLR server on X1 to initialize. With /O specified, X1 would erroneously assume that it is still the active and use out-of-date data. The only thing to do is to get workstation N1 running as soon as possible. Meanwhile:
In the above scenario, you must wait until workstation N1 is initialized. The following is a scenario in which it is safe to use the /O parameter:
Workstation X1 Workstation N1 Start as Active Start as Backup Process transactions Track transactions Machine failure Take over as new Active Repair..... Process transactions ..... Normal shutdown ..... Start as Active with /O parameter
In this case, N1 has up-to-date databases and can safely be started as the active, so the use of the /O parameter is valid. When X1 or another EHCSAM server again becomes available, it automatically becomes the backup, bringing its log and databases up-to-date by communication with N1.
LOADER SNA##.EXE [/R:r]
where:
The value must be an integer in the range 0 (do not retry) to 8. It is advisable to specify a low value, for example 1; if the connection does not succeed after one retry, there is likely to be a problem in the communications network which needs to be resolved before the connection can succeed.
LOADER SFORFORW.EXE [/K:y]
where:
The size of the buffer must be large enough to hold the maximum:
LOADER SPV.EXE /pc-id
where:
LOADER SMGR.EXE /D:x /O:yyyyyyyy [/Z:nnnn]
where:
LOADER EHCTCP.EXE [/M:aaaaaaaa[,aaaaaaaa]] [/T]
Where:
LOADER EHCTRACW [/R:rrrr] [/B::bbb] [/T:xxx] [/MT:mmm] [/ML:mmm] [/LT:lll] [/LL:lll] [/PT:[d:][path]filename] [/PL:[d:][path]filename]
where:
The variable rrrr can take values between 64 and 1024 + 64. The default is 394.
The variable bbb can take values greater than 1. The minimum is 2, and the default is 162.
Note that the maximum number of bbb is calculated using the formula:
[(64 × (1024 - 64)) ÷ (record length rrrr)]
The default is MEMORY. This parameter does not affect the log file, because a log error file is always provided by the server.
You must erase the existing Trace or Log files when you are creating new ones, otherwise the new parameters will not take effect.
Note that you must specify /T:FILE in the loading statement when you create a new Trace file.
The default for Trace is 394. The default for Log is 150.
If EHCTRACW is loaded while the supervisor is still in the loading process, the workstation ID value xx in the filenames EHCTRCxx and EHCLOGxx will sometimes be given the value [!!]. This may happen if you load with the DETACH command. To avoid this, you can either use the LOADER command, or rename the xx value for the files afterwards.
LOADER EHCVDMGR.EXE [path\name]
where:
The configuration file is optional. The default is EHCBOXS.CFG, if it exists.
LOADER PR47X2##.EXE [/K:n] [/T] [/N] [/R]
where:
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
The parameter is optional.
In LANDP for Windows only, the WR (Write to Printer) request allows the DEFAULT Parallel Attached printers to be accessed.
Use two new load-time parameters:
Running with /N but without /R, the server allows normal PROPRINTER escape sequences to be passed through to the printer. With /R, Postscript or PCL data streams pass through without change.
While running as a service, LANDP does not have any knowledge of who is, or is not, logged on. To allow it to find a default printer, the printer server needs an identity. To do this, allow the server to log on as a particular user. Do this after the servers have been registered (that is, AUTOFBSS has run at least once).
In control panel,
Select the account name and password that the printer server is supposed to use.
Selecting as above in the services panel enables the server to find the default printer. There is no default way to do this, even if a user is logged on. This also allows a different user to be logged on when LANDP is running in the background.
If you run AUTOFBSS /R:, you totally unregister LANDP. If you then want to access DEFAULT parallel attached printers, you must:
LOADER PR4748##.EXE [/K:n]
where:
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
If you select VDM (virtual DOS machine) relay during customization, and define the emulators to be loaded in a Windows VDM, the customization program creates an AUTO_VDM.BAT file with the emulator loading statements. The LSI command is used to run the emulators in the Windows VDM.
When you install more than one emulator, they can run in different Windows VDMs. A separate AUTO_VDM.BAT file is required for each VDM, containing the loading statements for the emulators that run in that particular VDM. To create those files, copy only the required loading statements.
FBSS (DOS) and LANDP for DOS clients (not servers) can also be run in a Windows VDM. If the VDM relay is not working on your Windows system, check the following.
If you are loading EHCVDSPV from AUTOEXEC.NT, all 16-bit Windows (WOW or Win16-on-Win32) lock EHCVDVXD.DLL, so it cannot be replaced. To overcome this either:
LSI VBIWP.EXE /C:atr /K:kbd /D:dis /T:at1 /P:pin /M:msi /N:mso /I:n
where:
LSI VBPP.EXE /E:e2a /H:ses /L:pses /M|S /I:n
where:
LSI EMU3270.EXE /C:atr /K:kbd /D:dis /I:n [/H:hh] [/W:ww] [/B:y] [/S:xxxxxxxx] [/Z:nnnn] [/P:a] [/L:l] [/T:tt]
where:
Use this parameter, in conjunction with /W, to make the emulated alternate screen look like one of the following 3270 models:
Alternate Alternate 3270 model screen height screen width 2 24 80 3 32 80 4 43 80
If this parameter is omitted, the default is 24.
If this parameter is omitted, the default is 80.
If this parameter is omitted, the default is N.
If this parameter is omitted, the default is a name of eight blanks.
If this parameter is omitted, the default is 2048.
If this parameter is omitted, the default is Y.
LSI EMU3287.EXE /x /E:prt [/T:nn] [/P:HP] [/N:n]
where:
The parameter value ranges from 1 to 60. The default is 15.
If the parameter is not specified, the emulator uses the number of parallel printer ports physically installed on the workstation.
The EHCFREE.EXE utility is provided to unload LANDP for Windows. You can also unload LANDP for Windows by issuing a supervisor function call from an application program. For more information on supervisor function calls, see LANDP Programming Reference.
The LANDP utility, EHCFREE.EXE, is called as follows:
d:\path\EHCFREE SPV [/p]
where:
This is the default value, and will send ES to the loaded LANDP components.
For information on supervisor function calls, refer to the LANDP Programming Reference.
This requires that LANDP for Windows unloads the LANDP components through the system functions provided to cancel a Windows process.
The EHCFREE.EXE program errors are detected by the LAN server or the supervisor. For information on the corresponding return codes, refer to the LANDP Problem Determination manual.
The EHCFREE.EXE utility program is used to dynamically unload a LANDP for Windows server at LANDP run time. The command must be entered in the workstation where the specific LANDP for Windows server to be unloaded is located.
Note that the EHCFREE.EXE program can also be used to unload the entire LANDP for Windows program.
The EHCFREE.EXE program is called as follows:
d:\path\EHCFREE servername [/p]
where:
This is the default value, and requires that the supervisor function unload LANDP for Windows (ES) is issued to the server specified.
For information on supervisor function calls, refer to the LANDP Programming Reference.
This requires that LANDP for Windows ends the servers specified, through the system functions provided to cancel a Windows process.
The EHCFREE.EXE program errors are detected by the LAN server or the supervisor. For information on the corresponding return codes, refer to the LANDP Problem Determination manual.
The LANDP family provides a utility program to check the path where the run-time files are located. See Installing and validating system files for more information about this program.
For other utility programs also provided to be used at run-time, refer to Run-time utility programs.
The LANDP customization process creates the EHCMSG.DLL file, which must be located in the current path or in a path specified using a PATH statement in the registry table.
|
The first part of this chapter, Installing and configuring Linux workstations, describes the requirements to install the LANDP for Linux
run-time files on the Linux workstations. Some requirements are related
to a specific server.
The second part of the chapter, Linux workstation setup, describes the final step of workstation distribution. The third part of the chapter, Modifying run-time files, describes the process of modifying the run-time files created by the customization program, according to your needs. The fourth part of the chapter, Loading statements for LANDP for Linux servers, describes how to check that the files have been correctly
installed.
|
The LANDP workstation files, which might typically be kept on diskettes, created for the Linux workstations do not contain any Linux system files. Therefore, before installing the LANDP for Linux operational files into your Linux workstation, make sure that a conforming version of Linux is installed.
The conforming versions supported by LANDP must contain the following kernel and glibc versions:
LANDP has been verified against the conforming versions of the following distributions of Linux for Intel-based platforms (x86 32-bit architecture):
The TCP/IP support that LANDP for Linux requires is typically provided as part of the Linux distribution that you have chosen.
After you have distributed the files from your customization workstation to a distribution directory that is accessible to the Linux workstations, you must run the ehcsetup utility program. Refer to "Linux workstation setup" for more details.
When working in DBCS mode, the operating system can be one of the following
depending on your national language:
Language | Linux Codeset | PC codepage | Linux Locale |
---|---|---|---|
Traditional Chinese | BIG5 | 950 (no defaults) | zn_TW.BIG5 |
Simplified Chinese | GBK | 1386 (no defaults) | zn_CN.GBK |
Notes:
LANDP for Linux workstations can only communicate in a LANDP workgroup by using TCP/IP as the transport protocol. TCP/IP must be configured for all the workstations that are to communicate to a Linux workstation. For detailed information, refer to the TCP/IP information in the Linux documentation. For more information about the TCP/IP transport protocol, see Appendix E, Using TCP/IP for internal communication.
LANDP for Linux workstations that are configured to use the TCP/IP wide area communications server, must have Linux TCP/IP installed and configured.
There must also be an ehctcp.ini file to provide the information required to map LANDP sessions configured with SNA and PPC servers to TCP/IP protocols, ports and internet addresses. The file can be created with any text editor, but it is best practice to use the file as generated by LANDP customization. See SES&TCP on page *** for a description of the file contents.
Workstations that are configured to use the LANDP link server, must have TCP/IP installed and configured.
If you are migrating data definitions or Shared File data from a SHFILE## environment on another LANDP environment, refer to LANDP Programming Reference.
The LANDP Java support on Linux is provided by the following files located in the EHCL600 directory:
To support the running of Java user servers, applications, applets or servlets on a LANDP workstation, copy these files to the directory on the workstation containing the LANDP files.
There are two alternative methods of distribution of the Java files:
You can copy the LANDP Java support files listed from the EHCL600 directory on the customization workstation to the required location on your Linux workstation.
LANDP Java support requires that the PATH and CLASSPATH environment variables are updated in your Linux profile:
<landp dir>\ldpjava.jar
where landp dir is the directory that contains the LANDP files.
<landp dir>\ldp4722.jar
Through customization, the LANDP Java support files can be distributed automatically with the LANDP files by specifying SERVER=JAVA in the LWSCONF vector for this workstation.
After distribution, the Linux workstation setup program, ehcsetup, automatically sets the required PATH and CLASSPATH environment variables in the .ehc_profile which should be run before starting autofbss.
Additionally, you can copy the documentation file, ldpjdocs.zip, from the EHCL600 directory located in the customization workstation.
After you have distributed the files from your customization workstation to a distribution directory that is accessible to the Linux workstations, you must perform some post-customization tasks before LANDP can be run.
These tasks include:
The LANDP utility program ehcsetup performs these tasks.
Another LANDP utility program, ehcremove, can be used to delete components of an existing LANDP setup.
All LANDP directories and files belong to the same Linux group, landp, and are owned by the LANDP Manager Account, ldpmgr. If ehcsetup detects that either the landp group or the LANDP Manager Account is not present, they will be created, using either default or user-prompted values, depending on the options specified on the command line invocation of ehcsetup.
LANDP user accounts can be created or modified using the ehcsetup utility program. If the account is a new account, the account is created, made part of the landp group, and the password for the account is stored in the LANDP password file, .landp_passwords, in the root home directory, if requested. A user home directory will be created.
If the account name already exists, the account will simply be added to the landp group.
The password for the account is not recorded in a readable form anywhere, except in the LANDP password file. Therefore if ehcsetup is run without --add_password, make sure that passwords are assigned to any user accounts that are created.
Because these accounts belong to the landp group, they can access all the LANDP files and data, but with restricted capabilities (for example, user accounts might not have the authority to delete LANDP objects).
Under normal circumstances, LANDP runs under a user account, not under the LANDP Manager Account, and definitely not under a root account. If landp is not the primary group of the user account, the command newgrp landp should be run immediately before .ehc_profile. See LANDP Environment Variables.
The utility program ehcsetup generates a log, .landp_log, in the administrator home directory. This log contains details of the processing that was done during the setup run. If any errors are detected during the setup, an error message is issued and the setup is terminated.
To help diagnose the error, the log also records any system-generated error codes associated with the error. Once the problem has been corrected, the setup can be rerun. However, any processing done before the error condition might not have been undone. Therefore, the ehcsetup parameters might need to be modified, or the incomplete setup removed and a new setup performed.
The utility program ehcsetup generates the files that contain the LANDP environment variables. The values of these variables should be created using information extracted during the setup run. They are not built as part of customization.
All workstation-specific environment variables are generated in the file, .ehc_profile, which is stored in the workstation directory. This file should be run as part of the user environment (ideally, it should be included in the user .profile file) to correctly build the LANDP process space.
Because many of the functions performed by the ehcsetup utility program require administrator privileges, ehcsetup can be run only by the root user. The utility will check that this is the case before continuing with the setup.
All messages and prompts produced by ehcsetup are catalog-based. To have messages and prompts displayed correctly during the workstation setup process, the ehcsetup message catalog (ehcsetup.msg), the ehcsetup message processor (ehcsmesg), and the ehcsetup script message defaults (shellmsg), must be present in the current working directory.
Ehcsetup can be run in one of three modes:
All the ehcsetup command line options are detailed below.
ehcsetup [--landp_release REL] * [--workstation_directory WSID] * [--distribution_directory DIR] * [--workstation_path WDPATH] * [--no_user] * [--default_manager] * [--default_group] * [--ws_dir_exist cancel|clear|replace] [--release_exist cancel|clear|replace] [--add_password] [--prompt full|brief|none] [--quiet] [--ignore_parameter_file] [--check_parameters]
ehcsetup [--prompt full|brief|none] [--quiet] --remove
ehcsetup [--prompt full|brief] [--add_password] [--quiet] [--check_parameters] --create_user
ehcsetup [--prompt full|brief] [--default_manager] [--quiet] [--check_parameters] --create_manager
ehcsetup [--prompt full|brief] [--default_group] [--quiet] [--check_parameters] --create_group
ehcsetup --help
where:
A full functional description of each option, with an example of its use, is detailed below. The short form of the command line option is shown in brackets. Short and long forms of the commands can be mixed on the same command line.
This defines the LANDP release code, related to the distribution being set up on this workstation. The parameter value REL is used as the directory name under which the LANDP components are installed.
There is no default value for REL. The parameter value REL can be any valid Linux directory name. See also the section Resolving Parameter Values for further details of how to define the parameter value during the running of ehcsetup.
Example: --landp_release L60
Example: -rl L60
This defines the name of the LANDP workstation directory. The parameter value WSID is the directory name under which all the LANDP workstation files are stored.
There is no default value for WSID. The parameter value WSID can be any valid Linux directory name. See also the section Resolving Parameter Values for further details of how to define the parameter value during the running of ehcsetup.
Example: --workstation_directory AC
Example: -wd AC
This is the name of the directory that currently holds all the LANDP files that are to be distributed on this workstation. These are the workstation files generated by LANDP customization, and put into the directory after the GETTING process. The directory DIR can be either local or network attached. Ehcsetup examines each file in the directory, makes a decision based on the file type about where the file should be placed, and then copies the file to the appropriate LANDP directory. Ehcsetup makes no changes to the contents of the files in the distribution directory, but some files and file types might be modified while being copied to their destination directories.
There is no default value for DIR. The parameter value DIR can be any valid, locally-accessible Linux directory name. See also the section Resolving Parameter Values for further details of how to define the parameter value during the running of ehcsetup.
Example: --distribution_directory /tmp/landp
Example: -dd /tmp/landp
This defines the local path to the workstation directory. The workstation path combined with the workstation directory defines the absolute location of the LANDP workstation files. If the path does not exist, ehcsetup will create it.
There is no default value for WDPATH. The parameter value WDPATH can be any valid, locally-accessible Linux path name. See also the section Resolving Parameter Values for further details of how to define the parameter value during the running of ehcsetup.
Example: --workstation_path /data/landp/workstations
Example: -wp /data/landp/workstations
This specifies the action to be taken by ehcsetup if the workstation directory, as defined by the workstation path and the workstation directory name, already exists. The default for ACTION is cancel, which specifies that ehcsetup will terminate with an error message.
The parameter ACTION can take either of the following values:
Example: ws_dir_exist replace
Example: -wx replace
This specifies the action to be taken by ehcsetup if the LANDP release directory already exists. The default for ACTION is cancel, which specifies that ehcsetup will terminate with an error message.
The parameter ACTION can take the following values:
Example: --release_exist clear
Example: -rx clear
This specifies that no user accounts should be created or modified during the present ehcsetup run. By default, ehcsetup prompts for the optional modification or creation of user accounts as part of the setup processing. For further information on user accounts, see the section LANDP User Accounts, Groups and Passwords.
Example: --no_user
Example: -nu
This specifies that ehcsetup should create a LANDP manager account using defaults, if it detects that a LANDP manager account is not present on the local workstation. By default, if there is no LANDP manager account, ehcsetup prompts the user for the name of the manager account. For further information on the LANDP manager account, see the section LANDP User Accounts, Groups and Passwords.
Example: --default_manager
Example: -dm
This specifies that ehcsetup should create the LANDP group using the next available group number, if it detects that a LANDP group has not been setup on the local workstation. By default, if there is no LANDP group, ehcsetup prompts the user to supply a group identifier number. For further information on the LANDP group, see the section LANDP User Accounts, Groups and Passwords.
Example: --default_group
Example: -dg
When ehcsetup creates a new user account, it also generates a user password. This parameter specifies that the new password should be appended to the LANDP account password file .landp_passwords in the home directory of the root user. Only the root user can write or read the LANDP password file.
The LANDP password file is only a record of the passwords generated for each new user; it has no other function, security or otherwise.
Example: --add_password
Example: -ap
This specifies the detail level of the prompts that are displayed to the user when ehcsetup requires input. The default for TYPE is full, which specifies that any formal prompts are preceded by a detailed explanation of the prompt and the input requirements, and a list of possible replies and examples of use.
The parameter TYPE can also take the following values:
brief - only the prompt itself is displayed; this is an expert mode
none - no prompts are displayed.
If ehcsetup is unable to resolve any required parameters, it terminates with an error message. This mode is used when ehcsetup is to run unattended.
Example: --prompt brief
Example: -pr none
This specifies that ehcsetup should run in quiet mode. By default, ehcsetup provides the user with a scrolled commentary that lists the tasks that it performs. In quiet mode, this commentary is not displayed, although it is still generated in the LANDP log file. For further information on the LANDP log file, see the section Installation Log and Error Logging.
Example: --quiet
Example: -qt
At the completion of every successful run, ehcsetup stores in a file, .landp_parameters, the parameters that were used. This file is held in the home directory of the root user. By default, this parameter file provides parameter values to ehcsetup on subsequent runs. See the section Resolving Parameter Values for details regarding which parameters can be supplied by the parameter file, and under what circumstances the parameter file will supply these parameters to ehcsetup. This parameter specifies that the parameter file should not be used to resolve any missing values.
Example: --ignore_parameter_file
Example: -ip
When specified, this parameter causes ehcsetup to display a list of all the proposed parameter values that are to be used in the present run, including all internally resolved parameters. No processing, except parameter checking, is performed.
Example: --check_parameters
Example: -cp
When specified, and if the LANDP group, landp, is not present on the local workstation, ehcsetup only performs LANDP group create processing. The user is prompted to input a group number for the new LANDP. For further details about the LANDP group, see the section LANDP User Accounts, Groups and Passwords.
Example: --create_group
Example: -cg
When specified, ehcsetup only performs user account processing on the local workstation. The user is prompted for the names of user accounts that are to be either created or modified. The use of this parameter implies parameter --create_group. For further details about user accounts, see the section LANDP User Accounts, Groups and Passwords.
Example: --create_user
Example: -cu
When specified, ehcsetup creates a LANDP manager account, if this account is not present on the local workstation. The user is prompted for the name of the account to be created. The use of this parameter implies the parameter --create_group. For further details about user accounts, see the section LANDP User Accounts, Groups and Passwords.
Example: --create_manager
Example: -cm
When specified, ehcsetup allows the user to remove various LANDP components from the local workstation, based on the release and/or workstation id that were specified during a previous ehcsetup. Because the user will not be able to subsequently recover any components that are removed, the user is prompted to confirm each removal before ehcsetup continues. At completion, all directories based upon the chosen LANDP release and/or workstation ID will have been removed.
Example: --remove
Example: -rm
When specified, a summary of all the command line parameters is displayed.
Example: --help
Example: -hp
The parameter values for the LANDP release, workstation directory name, distribution directory and workstation path are resolved in the following order:
Using the --check_parameters on the command line provides users with feedback about which parameter values will be used on a live run. This check is particularly useful when prompting is turned off, and when there might be different parameter values specified in the LANDP parameter and AUTOFBSS files.
Running ehcremove allows the user to delete LANDP components from the local workstation. The utility ehcremove can only be run by the root user. The utility will check that this is the case before continuing with the process. The components deleted are based on the landp release and/or the workstation id as specified during a previous ehcsetup. Because the user cannot subsequently recover components deleted during ehcremove, prompting occurs at several points to confirm the deletion before continuing. At completion, all directories based upon the chosen LANDP release and/or workstation id will have been removed.
Warning - the use of ehcremove might cause LANDP to become unavailable on the workstation. In this case, ehcsetup must be used to redistribute LANDP to this workstation.
DOS is supported on Linux using DOSEMU. This can be obtained from the www.dosemu.org website. You are responsible for correctly installing this, and the LANDP plug-in, on your Linux system. For more information refer to Chapter 24 of the LANDP Programming Reference.
The DOS-box Relay DOS stub (EHCVDSPV.COM) must be loaded in a DOS-box that will run LANDP/DOS applications. This can be achieved in a number of ways, some of which are covered here. The most appropriate way depends on the way the workstation is used.
If the workstation will only be used for specific LANDP for DOS applications, it might be appropriate to invoke EHCVDSPV in-line with the application using a batch file as in the following example:
STARTAPP.BAT LOADHIGH EHCVDSPV.COM LANDPAPP EXIT
In this case the DOS-box Relay DOS stub is loaded into high memory and the LANDP for DOS application is started. The window is closed on termination of the application. No changes to AUTOEXEC.BAT are required.
If all MS-DOS prompts have the capability to run LANDP for DOS applications, the following should be added to AUTOEXEC.BAT:
D: CD \LANDPV6 EHCVDSPV
This example assumes that the LANDP runtime exec is in D:\LANDPV6.
Loadhigh can be used to load EHCVDSPV. Refer to the Linux help information for details.
libehclnx.so is a shared object (similar to a dynamic link library) that contains the LANDP interface routines RMTREQ, GETRPLY, SRVINIT, GETREQ, RMTRPLY, and RMTAREQ.
libehclnx.so is loaded in the supervisor and in every other LANDP process. LANDP for Linux expects libehclnx.so to be mapped to the same virtual address in every process that uses it. If the supervisor attempts to load libehclnx.so at an address that another process has already used, the load fails. To prevent this problem arising:
$export EHC_MAP_LOC=value 9000000
where value is the virtual address where libehclnx.so. The default virtual address is 9000000.
Figure 10 illustrates the problem and the solution.
Figure 10. libehclnx.so loading problem and solution Possible situation without EHC_MAP_LOC environment variable Possible situation with EHC_MAP_LOC environment variable
defined. libehclnx.so is loaded at different virtual addresses
in the supervisor and application. This causes a failure.
defined. libehclnx.so is always loaded at the same virtual
address in the supervisor and all applications, provided the supervisor is
started first.
On Linux systems, signals are sent to processes to indicate that a particular event has occurred. These signals might be sent from the hardware, from other software, or from other processes. The signals are detected and handled by programs in a similar way to exceptions.
The ability to catch and handle an exception is necessary to keep a system stable. But in Linux, not all signals can be caught. SIGKILL and SIGSTOP will end a process without performing any signal-handling. This means that some resources held by that process might not be released back to the operating system or shared libraries.
The ehcrstml utility program is called by autofbss before the supervisor is loaded. This utility restarts the shared library libehcmap.so by removing all allocated semaphores and queues. The utility can only run if the supervisor is not loaded. Therefore, LANDP should be unloaded before running this utility.
If a LANDP process is sent a SIGKILL or a SIGSTOP, the workstation should be unloaded and ehcrstml should be run before reloading LANDP.
ehcrstml has no parameters.
You might need to modify the contents of the autofbss file.
Depending on the applications and servers that you have developed, and the devices that you have installed, additional files might also need to be copied.
The autofbss file contains the loading statements of the supervisor and the servers that are to reside on the workstation. The first program loaded is the supervisor.
Ensure that any modification of this file does not cause a server to be loaded before the supervisor. Application loading statements should be placed at the end of the server loading statements.
Linux provides two uncatchable signals, SIGKILL and SIGSTOP, that will force a process to end. Because system resources are not freed when you use SIGKILL or SIGSTOP to end a process, this way of ending a process is not recommended. If a LANDP process has been ended in this way, you must release its system resources using the utility ehcrstml to ensure that LANDP behaves normally.
The following is an example of an autofbss file for a workstation that contains the shared file server. The name of the workstation is AB.
#!/bin/bash # # Exit routine in case of any loader error doexit () { ehcfree spv exit 1 } # # Echo commands to user set -x # # Ensure clean system before LANDP startup ehcrstml if [ $? -ne 0 ] ; then exit 1 fi varparm if [ $? -ne 0 ] ; then doexit fi # # Load the LANDP supervisor loader spv -AB if [ $? -ne 0 ] ; then doexit fi # prodlvl=l60 # # Load the TCP/IP workgroup transport protocol loader ehclip if [ $? -ne 0 ] ; then doexit fi newcfg if [ $? -ne 0 ] ; then doexit fi # # Load the shared file server loader shfile## -C:SFSEDUC -B:3 -E -S:10 -L:0 -F:10 if [ $? -ne 0 ] ; then doexit fi # end of file
You should invoke the ehccinfo utility program from a command prompt to get information about LANDP for Linux status. ehccinfo is a LANDP utility program; it is described in the LANDP Servers and System Management book.
Most loading statements explained in this section are automatically created by the customization program, using the parameters that you provided. The following commands appear in the autofbss file provided by customization. Manual modifications can be done if required. The loader command is used to run the servers and the supervisor, in the background.
These are regular Linux programs that can be started from the shell prompt, either as a foreground or background task. Note that using the loader command displays the return codes corresponding to the initialization process.
The loader program provides an optional parameter t to specify the timeout for a specific server load:
loader [-t:xxxx] servername serverparms
The timeout value xxxx can be up to four characters long. The minimum timeout is 1 second and the maximum timeout is 3600 seconds. If a timeout is not specified, the default that is used when loading the server is 30 seconds.
serverparms are qualified by a hyphen, '-', and are of the form -<param>:<value>.
If the initialization completes without error, the server goes into a wait state until it receives a request from an application. If an error occurs during initialization, the error is logged in the Linux system log.
To check the type of error, use if [ $? -ne 0 ] statements. If a LANDP error occurs, the corresponding error code is returned.
Error codes returning during loading are listed in the LANDP Problem Determination book.
The following commands are used when you load the LANDP for Linux functional areas.
loader elecjo## [-K:y]
where:
The size of the buffer must be large enough to hold the maximum:
loader forward -O:vvvvvvvv.vvv [-T:wwww] [-S:xxxxxxxx.xxx] [-K:y] [-H:z] [-Z:nnnn]
where:
It can range from 1 to 6000. The default is 20 (about 1 second).
The parameter value must be the value assigned in the loading statement of the store-for-forwarding server.
loader ehclip [-N:n] [-Y] [-T] [-C[:ws-id]] [-O:o[filename]] [-J]
where:
The parameter value ranges from 1024 to 65535. The default is 52699.
loader ehclink [-T] [-E:eeeeeeee[,eeeeeeee...]] [-I:iiiiiiii[,iiiiiiii...] -L:llllllll [-A:aaaaaaaa[,aaaaaaaa...]] [-R:rrrr]] [-P:ppppp]
where:
The LANDP link server can act as both an exporter and an importer of services. It can do both at the same time, if required.
There can be any number of exporters and importers in a workgroup and in a workstation, but only one exporter on each workstation can use each TCP/IP port number.
loader msre47## [-C:x] [-D:n] [-O:e]
where:
The parameter is optional. The value that can be specified is in the range 1 to 8. The default is 1.
The parameter is optional; if used, the value specified must be 1.
The parameter is optional. The value specified can be 0 or 1. The value 0 (the default) disables redirected device requests. The value 1 enables the requests.
loader pinp47## [-M] [-C:x]
where:
The parameter is optional.
The parameter is optional. The value that can be specified is in the range 1 to 8. The default is 1.
loader ehcsam
This loading statement does not correspond to a separate functional area. The ehcsam program is required by shared-file servers when using the XLR (external logging replicator) facility. For details, see LANDP Servers and System Management.
loader shfile## [-C:confname] [-B:nnn] [-E] [-R] [-S:xxx] [-L:y] [-F:zz] [-X:ss] [-A:ttt] -O
where:
Another factor that must be considered is that the more buffers you have, the greater is the probability of losing index file data when the shared file server is abnormally ended. Thus, if many index buffers are allocated, and the server workstation is switched off with a transaction still in process, or if no RF function has been called, an automatic index rebuild is issued the next time the server is loaded.
This number plus the number of workstations that receive services must not be higher than 243.
The default is 0.
The parameter value can range from 10 to 245.
Range: 0-999
During XLR server initialization, LANDP:
If a majority vote of at least two SAMs cannot be achieved, LANDP issues the following messages, where xlr can be SH or BK.
EHC0587: Waiting for XLR state confirmation (Last XLR state on WS N1: xlrFILE01). EHC0588: Start other XLR WS, or use -O parameter on SHFILE## to override.
If one of the XLR workstations is permanently unavailable and no other SAM is active, the server cannot complete initialization. If you are sure that the state given in the first message is correct, and that the issuing server has up-to-date copies of the databases, you can force confirmation by restarting SHFILE## with the -O parameter. Do not use this parameter in any other circumstances.
Consider the following scenario:
Workstation X1 Workstation N1 Start as Active Start as Backup Process transactions Track transactions Machine failure Take over as new Active Repair..... Process transactions .....machine Normal shutdown Start as ???
In the last step, it is not safe for the XLR server on X1 to initialize. With -O specified, X1 would erroneously assume that it is still the active and use out-of-date data. The only thing to do is to get workstation N1 running as soon as possible. Meanwhile:
In the above scenario, you must wait until workstation N1 is initialized. The following is a scenario in which it is safe to use the -O parameter:
Workstation X1 Workstation N1 Start as Active Start as Backup Process transactions Track transactions Machine failure Take over as new Active Repair..... Process transactions ..... Normal shutdown ..... Start as Active with /O parameter
In this case, N1 has up-to-date databases and can safely be started as the active, so the use of the -O parameter is valid. When X1 or another ehcsam server again becomes available, it automatically becomes the backup, bringing its log and databases up-to-date by communication with N1.
loader sforforw [-K:y]
where:
The size of the buffer must be large enough to hold the maximum:
loader spv -pc-id
where:
loader smgr -D:path -O:yyyyyyyy [-Z:nnnn] [-r:cc]
where:
loader ehctcp [-M:aaaaaaaa[,aaaaaaaa]] [-T]
Where:
loader ehctracw [-R:rrrr] [-B::bbb] [-T:xxx] [-MT:mmm] [-ML:mmm] [-LT:lll] [-LL:lll] [-PT:[d:][path]filename] [-PL:[d:][path]filename]
where:
The variable rrrr can take values between 64 and 1024 + 64. The default is 394.
The variable bbb can take values greater than 1. The minimum is 2, and the default is 162.
Note that the maximum number of bbb is calculated using the formula:
[(64 × (1024 - 64)) ÷ (record length rrrr)]
The default is MEMORY. This parameter does not affect the log file, because a log error file is always provided by the server.
You must erase the existing Trace or Log files when you are creating new ones, otherwise the new parameters will not take effect.
Note that you must specify -T:FILE in the loading statement when you create a new Trace file.
The default for Trace is 394. The default for Log is 150.
If EHCTRACW is loaded while the supervisor is still in the loading process, the workstation ID value xx in the filenames ehctrcxx and ehclogxx will sometimes be given the value [!!]. To avoid this, you can either use the loader command, or rename the xx value for the files afterwards.
loader ehcvdmgr [path/name]
where:
The configuration file is optional. The default is ehcboxs, if it exists.
loader pr47x2## [-K:n] [-T] [-N] [-R]
where:
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
The parameter is optional.
The ehcfree utility program is provided to unload LANDP for Linux. You can also unload LANDP for Linux by issuing a supervisor function call from an application program. For more information on supervisor function calls, see LANDP Programming Reference.
The LANDP utility program, ehcfree, is called as follows:
ehcfree spv [-p]
where:
This is the default value, and will send ES to the loaded LANDP components.
For information on supervisor function calls, refer to the LANDP Programming Reference.
This requires that LANDP for Linux unloads the LANDP components through the system functions provided to cancel a Linux process.
The ehcfree program errors are detected by the LAN server or the supervisor. For information on the corresponding return codes, refer to the LANDP Problem Determination manual.
The ehcfree utility program is used to dynamically unload a LANDP for Linux server at LANDP run time. The command must be entered in the workstation where the specific LANDP for Linux server to be unloaded is located.
Note that the ehcfree program can also be used to unload the entire LANDP for Linux program.
The ehcfree program is called as follows:
ehcfree servername [-p] [-q]
where:
This is the default value, and requires that the supervisor function unload LANDP for Linux (ES) is issued to the server specified.
For information on supervisor function calls, refer to the LANDP Programming Reference.
This requires that LANDP for Linux ends the servers specified, through the system functions provided to cancel a Linux process.
The ehcfree program errors are detected by the LAN server or the supervisor. For information on the corresponding return codes, refer to the LANDP Problem Determination manual.
The LANDP family provides a utility program to check the path where the run-time files are located. See Installing and validating system files for more information about this program.
For other utility programs also provided to be used at run-time, refer to Run-time utility programs.
The LANDP customization process creates the ehc.msg file, whose location is specified by the environment variable NLSPATH. This variable is set during the workstation setup.
|
The first part of the chapter, Installing and configuring IBM DOS workstations, describes the requirements to install the LANDP for DOS
run-time files on the DOS workstations. Some requirements are related
to a specific server.
The second part of the chapter, Modifying run-time files, describes the process of modifying the run-time files created by the customization program, according to your needs. The third part of the chapter, Installing run-time files, describes how to check for the correct installation of the
run-time files.
|
If the workstation files, which might typically be held on diskettes, created for the DOS workstations do not contain the DOS system files, make sure that IBM DOS V7.1 is installed according to the existing recommendations, before installing the LANDP for DOS operational files into your DOS workstation.
When working in DBCS mode, the operating system can be one of the following,
or later versions, depending on your national language:
Language | Operating system | Supported codepage |
---|---|---|
Traditional Chinese | IBM DOS T2000 | 938, 950 |
Korean | IBM DOS H2000 | 949 |
Simplified Chinese | IBM DOS P2000 | 1381 |
This section applies to LANDP for DOS workstations integrated in a LANDP workgroup that uses NetBIOS as the transport protocol.
To use NetBIOS as the internal communications protocol for a LANDP workgroup, a NetBIOS implementation must be installed and configured in all the workstations. This can be the IBM LAN Support Program, IBM LAN Client, or another compatible implementation.
If you select NetBIOS as the transport protocol, LANDP customization assumes that you are using the IBM LAN Support Program for a non-Network Driver Interface Specifications (NDIS) device driver. It generates a CONFIG.SYS file containing statements to load the NetBIOS device drivers. The software distribution procedure (GETTING) copies these device drivers to the distribution media. However, if you are not using the IBM LAN Support Program for a non-NDIS device driver, or if there are programs other than the LANDP NetBIOS transport using NetBIOS, you will have to configure the NetBIOS support directly.
Before configuring some NetBIOS implementations you need to know what NetBIOS resources will be required. The NetBIOS resources to note are NAMES, SESSIONS, and COMMANDS. Each program that uses NetBIOS will require a number of these. Find out the programs that use NetBIOS and the resource that they require and add these resource requirements together to find the total number of NAMES, SESSIONS, and COMMANDS required for each workstation in the workgroup.
You should take into account:
When using non-NDIS adapters the statements in the generated CONFIG.SYS file are usually adequate. If n1 NAMES, n2 SESSIONS and n3 COMMANDS are required, the DXMT0MOD line should be:
DEVICE=DXMT0MOD N=n1 ST=n2 S=n2 C=n3
When using an NDIS adapter there is a choice of drivers depending upon whether the IEEE 802.2 interface is required in addition to the NetBIOS interface. The LANDP TRDLC server requires the IEEE 802.2 interface.
DEVICE=DXMA0MOD DEVICE=DXME0MOD DEVICE=DXMT0MOD N=n1 ST=n2 S=n2 C=n3 O=N
DEVICE=DXMA0MOD DEVICE=DXMJ0MOD
It has no parameters as NetBIOS resource information is contained in the PROTOCOL.INI file. For more information, see PROTOCOL.INI contents.
For either of these device drivers LANDP customization will not generate the correct software distribution statements in the GETTING.SPC files. You can either alter these or install and configure the IBM LAN Support Program separately on each workstation.
When using the device drivers for PC Network Adapters (DXMGnMOD) or NDIS adapters (DXME0MOD) the workspace might not be large enough if there are a large number of sessions or a large volume of data traffic. A message might be generated, the adapter might fail to open, or the workstation might simply hang at start-up. The workspace is the second positional parameter for these drivers. For example, to set it to the maximum of 64K, change the DXMG0MOD line to:
DEVICE=DXMG0MOD ,64
See the IBM LAN Support Program User's Guide for more details.
LANDP customization will not generate the correct software distribution statements in the GETTING.SPC files. You can either alter these or install and configure the IBM LAN Client separately on each workstation.
Discard the IBM LAN Support Program configuration statements in the generated CONFIG.SYS file and install IBM LAN Client in the required workstations. There is no requirement to enter NetBIOS resources.
This section applies to LANDP for DOS workstations integrated in a LANDP workgroup that uses TCP/IP as transport protocol.
To use TCP/IP as the internal communications protocol for a LANDP workgroup, TCP/IP must be installed and configured in all the workstations.
LANDP operates with either IBM TCP/IP for DOS version 2.1.1.4 or with PC/TCP(R) Network Software version 5.0 from NetManage Inc.(R).
The datagram length used by LANDP must not exceed the PC/TCP maximum segment size (MSS). The MSS values for different types of network are listed in the PC/TCP Advanced Users Guide. The datagram length used by LANDP can be set by the /D parameter of the LANDP Internet Protocol (LIP) LOADER statement described in LANDP Internet Protocol.
When large volumes of data are being transmitted, the PC/TCP kernel might require additional packet buffers for optimal performance. See the PC/TCP Advanced Users Guide for instructions on adjusting the number of packet buffers.
For more information about the PC/TCP transport protocol, see Appendix E, Using TCP/IP for internal communication.
The default configuration of PC/TCP has 4 TCP connections and 2 UDP connections. This might not be sufficient when using the TCP/IP wide area communications server. The connections required are:
udp-connections=3
to the [PCTCP KERNEL] section of the PCTCP.INI file.
To change the number of TCP connections add:
tcp-connections=number
to the [PCTCP KERNEL] section of the PCTCP.INI file.
When the TCP/IP wide area communications server is being used for MPTN (AnyNet) sessions, it is necessary to set the TCP window size parameter of PC/TCP to a value of at least 254 bytes more than the maximum RU size sent by the primary LU. The PC/TCP documentation recommends setting this parameter to a multiple of the maximum segment size of the network interface.
To set the TCP window size, where value is the required size, add:
window=value
to the [PCTCP KERNEL] section of the PCTCP.INI file.
To prepare TCP/IP software for coexisting with LANDP, update the IntExclude parameter in the TCPDOS.INI file, located in the ETC subdirectory in the path where TCP/IP is installed. The default specifies:
IntExclude = 61-63, 67
That means that TCP/IP will not use interrupts 61, 62, 63, and 67. Because interrupt 64 is used by LANDP, to avoid unpredictable results, specify also 64:
IntExclude = 61-64, 67
For detailed information, refer to the TCP/IP manuals. See Appendix J, Bibliography.
For more information about the TCP/IP transport protocol, see Appendix E, Using TCP/IP for internal communication.
LANDP for DOS workstations configured to use the TCP/IP wide area communications server must have PC/TCP installed. For more information, refer to Installation requirements for TCP/IP transport protocol.
There must also be an EHCTCP.INI file to provide the information required to map LANDP sessions with SNA and PPC servers to TCP/IP protocols, ports and internet addresses. This file can be created with any text editor, but it is best practice to use the file as generated by LANDP customization. See SES&TCP on page *** for a description of the file contents.
When using the TCP/IP wide area communications server the dependent LU names must have a common alphanumeric prefix and a numeric suffix with a constant difference between the suffix and the LOCADDR. For example:
IYCKT300 LU LOCADDR=2 IYCKT301 LU LOCADDR=3 IYCKT327 LU LOCADDR=29 IYCKT481 LU LOCADDR=183
This section applies to LANDP for DOS workstations configured to use the TRDLC server for SNA communications.
To use the TRDLC server on a workstation an IEEE 802.2 interface to the LAN adapter must be installed and configured on the workstation. This can be provided by IBM LAN Support Program, IBM LAN Client, or another compatible implementation.
If you select NetBIOS as the transport protocol and specify the TRDLC server, LANDP customization assumes that you are using IBM LAN Support Program for a non-NDIS device driver. It generates a CONFIG.SYS file containing statements to load the IEEE 802.2 device drivers. The software distribution procedure (GETTING) copies these device drivers to the distribution media. However, if you're not using IBM LAN Support Program for a non-NDIS device driver, then you will have to configure the NetBIOS support directly.
When using non-NDIS adapters the statements in the generated CONFIG.SYS file should be correct. For example:
DEVICE=DXMA0MOD DEVICE=DXMC0MOD 4000xxxxxxxx DEVICE=DXMT0MOD N=n1 ST=n2 S=n2 C=n3 ES=1 EST=1 DS=600
where 4000xxxxxxxx is the locally administered address for the adapter and 'ES=1 EST=1 DS=600' are additional required parameters for the NetBIOS driver when using the IEEE 802.2 interface.
When using an NDIS adapter simply change DXMC0MOD to DXME0MOD in the customization generated CONFIG.SYS file. In addition, O=N must be specified on the DXMT0MOD line, giving the following CONFIG.SYS file lines:
DEVICE=DXMA0MOD DEVICE=DXME0MOD 4000xxxxxxxx DEVICE=DXMT0MOD N=n1 ST=n2 S=n2 C=n3 O=N ES=1 EST=1 DS=600
Discard the IBM LAN Support Program configuration statements in the generated CONFIG.SYS file.
During IBM LAN Client installation make sure that the IEEE 802.2 interface is configured and that the locally administered address is set to the required value.
LANDP customization will not permit the configuration of the TCP/IP transport together with the TRDLC server because it is not possible to run them both through the same non-NDIS adapter with IBM LAN Support program. However, with multiple adapters or with an NDIS adapter it is possible to use them together. To get around the customization restriction, customize LANDP to use the NetBIOS transport. Substitute EHCLIP.EXE for LAN.EXE in the distributed files and in the loading statement in AUTOFBSS.BAT. To arrive at the correct adapter driver configuration see the IBM TCP/IP Version 2.1.1.4 for DOS Installation and Administration manual.
The main areas of modification are:
For a utility program to modify files, see Modifying file contents.
Depending on the applications and servers you have developed and the devices you have installed, additional files might need to be copied.
There are some considerations for the CONFIG.SYS and AUTOFBSS.BAT files for the emulators.
In accordance with the keyboard and display code page selected at emulator customization time, additions might be needed in the CONFIG.SYS and AUTOFBSS.BAT files. If these are not included, you might get unexpected results.
To CONFIG.SYS, add the following DOS commands for the 3270 emulator:
COUNTRY=xxx,yyy,COUNTRY.SYS DEVICE=DISPLAY.SYS CON:=(EGA,yyy,1)
To CONFIG.SYS, add the following DOS commands for the 3287 printer emulator:
COUNTRY=xxx,yyy,COUNTRY.SYS DEVICE=PRINTER.SYS LPT1:=(4201,yyy,1)
To AUTOFBSS.BAT, add the following DOS commands for the 3270 emulator:
NLSFUNC KEYB zz,yyy,KEYBOARD.SYS MODE CON: CP PREP=((yyy) EGA.CPI) CHCP 850 or MODE CON CP SELECT=yyy
To AUTOFBSS.BAT, add the following DOS commands for the 3287 printer emulator:
NLSFUNC KEYB zz,yyy,KEYBOARD.SYS MODE LPT1: CP PREP=((yyy) 4201.CPI) CHCP 850 or MODE CON CP SELECT=yyy
where:
For more information about these commands, refer to the DOS Reference Guide.
If Microsoft Windows 3.1 or 3.11 support was specified at customization time, the following files will be distributed to the workstation:
The EHCPREV.BAT procedure should be run before starting Windows 3.1 or 3.11.
The first statement in the file must be:
EHCWGMDI /L:xx
where xx is an optional parameter to specify the maximum storage, in KB, required by Windows parameters and user data. The parameter value ranges from 4 to 56. The default is 4.
If the following servers were specified at customization time, the corresponding loading statements will appear after the EHCWGMDI statement:
For information on those loading statements, refer to Loading statements for LANDP for DOS servers.
The WINSTART.BAT file contains the following statement:
EHCWVDMI
EHCWVDMI is accessed by the Windows 3.1/3.11 applications.
The EHCDOSVM.BAT procedure should be run under Windows 3.1/3.11 in a virtual machine.
The EHCDOSVM.BAT file contains the loading statements of the supervisor and the servers that are to reside on the workstation, except for those whose loading statement should be placed in the EHCPREV.BAT file.
Ensure that any modification of this file does not cause a server to be loaded after the supervisor. For information on the loading statements, refer to Loading statements for LANDP for DOS servers.
The EHCAPLVM.BAT procedure should be run under Windows 3.1/3.11 in the virtual machine where the LANDP application will be loaded. The default contents are:
EHCWVDMI AUTOUSER
The SYSTEM.ADD file should be added to the SYSTEM.INI Windows 3.1/3.11 setting file. The default contents are:
[386Enh] DEVICE=EHCVMSD.386
The EHCDOSVM.PIF file can be edited with the Windows 3.1/3.11 PIF editor. You can modify the contents according to the settings to be assigned to the virtual machines where LANDP or LANDP applications run.
You should compare the CONFIG.SYS file created by the customization program with the CONFIG.SYS file in your workstation, and make the necessary modifications to merge them into one.
You should specify the paths for the new device drivers and other needed files.
You should also take into account the following:
An approximate value is already set for the FILES parameter.
You must use the SHARE program. The default parameters might not be sufficient. In this case, load the SHARE program with the CONFIG.SYS file, by adding the following statement:
INSTALL d:\path\share.exe /F:xxxx
where xxxx is the value, in bytes, you need for file sharing. The default is 2048.
The SHARE program is mandatory to have file locking available.
You should add a CACHE program. In the workstations where you use a data management server such as the shared-file server, set lazy writes off, unless your system is equipped with an Uninterruptible Power Supply (UPS).
When the shared-file server starts up, it creates the necessary shared-file directories if they do not already exist. This removes the need (which existed in previous releases) to call CREADB.BAT to create these directories.
You do not require the LAN Support Program (LSP) drivers, DXMA0MOD, DXMC0MOD, and DXMT0MOD, in your CONFIG.SYS file if you are running under Windows for Workgroups 3.11. They are required for Windows 3.1.
The following is an example of a CONFIG.SYS file for a workstation that contains the SNA server with X.25 data link control, the shared-file server, and a 3270 emulator. The workstation is integrated in a LANDP workgroup that uses NetBIOS as transport protocol.
BUFFERS=20 FILES=40 SHELL = \COMMAND.COM /E:256 /P REM The environment parameter above might REM need to be increased based on other REM than LANDP for DOS program requirements. DEVICE=DXMAOMOD.SYS DEVICE=DXMCOMOD.SYS DEVICE=DXMTOMOD.SYS ST=26 S=26 C=30 DEVICE=X251.SYS
If you plan to load this server, the following statements are required in the CONFIG.SYS file.
If the server supports a 4717 MSR/E:
DEVICE=MSRE2DD.SYS /X
If the server supports a 4777 MSR/E:
DEVICE=IBM4777.SYS /X /Cp
The p parameter value corresponds to the COM port where the 4777 MSR/E will be attached.
If the server supports a 4778 MSR:
DEVICE=IBM4777.SYS /X /Cp /M
The p parameter value corresponds to the COM port where the 4778 PIN Pad MSR will be attached.
If a 4778 device is mouse attached:
DEVICE=MSRE2DD.SYS /M
If a 4777 device is mouse attached:
DEVICE=MSRE2DD.SYS
If you plan to load this server, the following statements are required in the CONFIG.SYS file.
If the server supports a 4718 PIN pad:
DEVICE=PIN2DD.SYS /X
If the server supports a 4778 PIN pad:
DEVICE=IBM4778P.SYS /X /Cp
The p parameter value corresponds to the COM port where the 4778 PIN Pad MSR will be attached. The second statement should be specified only if MSR capabilities will be used.
If a 4778 device is mouse attached:
DEVICE=PIN2DD.SYS
If you plan to load this server, refer to Installation requirements for TRDLC server.
If you plan to load this server, the following statement is required in the CONFIG.SYS file:
DEVICE=<drive> <path> xxxxxx.SYS
where:
If you plan to load this server, the following statement is required in the CONFIG.SYS file for each printer connected to an RS-232 port :
DEVICE=<drive> <path> FPRTxxxx.SYS [/B:bbbb][/A:a] [/R:rrr] [/X] [/M]
where:
The default value is Asynchronous connector 1.
All combinations 000 through 111 are valid. The default value is 000.
The same device drivers as those for the 4722 printer are used if you plan to use the 9055 Model 2 or 9068-S01 printers.
If you plan to load this server, the following statement is required in the CONFIG.SYS file for each 4748 printer connected to an RS-232 port:
DEVICE=<drive> <path>FPRTxxxx.SYS [/B:bbbb] [/A:a] [/X]
where:
The default value is Asynchronous connector 1.
If you plan to use the 9055 Model 1 or 9068-D01 printer, you can use the same device driver as for the 4748 printer (but it will provide support only for 4748 emulation mode). If the extra features of these printers are to be used (for example, REMS), change the device driver name in your CONFIG.SYS file to:
DEVICE=<drive> <path>FPRTSCPx.SYS [/B:bbbb] [/X]
If you plan to use a 4733 teller assist unit, you must specify the following statement in your CONFIG.SYS file:
DEVICE=TCD386D.SYS
If your workstation is using LAN Support Program device driver DXMJ0MOD.SYS, which requires LAN Support Program Version 1.38 or later, you need to update your PROTOCOL.INI file to include details that the LANDP configuration added to the CONFIG.SYS file. These include:
LANDP Customization will have added a sessions parameter to the DXMT0MOD.SYS device driver. You should use this value to set the SESSIONS and DATAGRAMPACKETS keywords in the DXMJ0MOD_MOD section of PROTOCOL.INI.
LANDP Customization will have added a commands parameter to the DXMT0MOD.SYS device driver. You should use this value to set the NCBS keyword in the DXMJ0MOD_MOD section of PROTOCOL.INI.
For example, LANDP customization might have generated a CONFIG.SYS file that includes the lines:
DEVICE=DXMC0MOD.SYS DEVICE=DXMT0MOD.SYS O=N ST=3 S=3 C=6
If, for example, you are using the IBMTOK.DOS MAC driver, PROTOCOL.INI would look something like this:
[DXMJ0MOD_NIF] Driver Name=NETBEUI$ Bindings=... NCBS=6 SESSIONS=3 DATAGRAMPACKETS=6
·
·
·
The AUTOFBSS.BAT file contains the loading statements of the supervisor and the servers that are to reside on the workstation. The last program loaded is the supervisor.
Ensure that any modification of this file does not cause a server to be loaded after the supervisor. Application loading statements should not be placed in the AUTOFBSS.BAT file but in the AUTOUSER.BAT file.
If DOSKEY is used as well as LANDP, execute DOSKEY before AUTOFBSS to ensure that the settings are saved.
The following is an example of a AUTOFBSS.BAT file for a workstation that contains the SNA server with X.25 data link control, the shared-file server, and a 3270 emulator. The workstation is integrated in a LANDP workgroup that uses NetBIOS as transport protocol.
NEWCFG IF ERRORLEVEL 1 GOTO END VARDAT IF ERRORLEVEL 1 GOTO END LOADER SHFILE##.EXE /C:SFILE1 /B:12 /E /S:3 /L:2 /F:50 IF ERRORLEVEL 1 GOTO END LOADER SNA##.EXE IF ERRORLEVEL 1 GOTO END XL.EXE IF ERRORLEVEL 1 GOTO END LOADER X25DLC.EXE IF ERRORLEVEL 1 GOTO END LOADER EMU3270.EXE /C:ATR/K:KBD/D:DIS/I:1 IF ERRORLEVEL 1 GOTO END LOADER DDT.EXE IF ERRORLEVEL 1 GOTO END LOADER LAN.EXE/AB IF ERRORLEVEL 1 GOTO END LOADER SPV.EXE/AB /K:20 IF ERRORLEVEL 1 GOTO END AUTOUSER :END FREE
If the workstation is integrated in a LANDP workgroup that uses TCP/IP as transport protocol, EHCLIP.EXE should be specified instead of LAN.EXE.
In order to get an information window about LANDP for DOS status, you should invoke the EHCCINFO utility program.
You should modify the AUTOUSER.BAT file to meet the requirements of your applications. They can be started with AUTOUSER.BAT.
If you plan to use DOS PRINT together with this server and either the 3287 printer emulator, or the financial printer server, or your own printer server, the following statement is required in the AUTOFBSS.BAT file:
FBSSP <path>\PRINT<parameters>
where FBSSP is the loading command. You should provide the path and parameters.
Most loading statements explained in this section are automatically created by the customization program, using the parameters you provided. LOADER is used by LANDP for DOS to load the functional areas into workstation memory.
For return codes during loading, refer to LANDP Problem Determination.
After loading LANDP, the functional areas become an extension of DOS. Control is transferred to the servers when loading is completed. Each server performs initialization, then goes into a wait state. Invocation is subsequently done by the supervisor as needed.
Some functional areas can be loaded into expanded memory, thus not occupying space in conventional memory. The loading command then is changed to LOADERE.
Both loading commands, LOADER and LOADERE, provide two optional parameters, w:e and &:e. These parameters can be included in the loading statements of some user servers, as follows:
LOADER (or LOADERE) [/w:e] [servername]
where servername is the name of the server being loaded.
The w:e parameter applies to user servers that do not call DOS functions at run-time, and therefore do not need specific internal storage for that purpose.
If the parameter is specified, the LOADER(E) program uses less memory. If specified, but the server uses DOS functions, the results are unpredictable.
LOADER (or LOADERE) [/&:e] [servername]
where servername is the name of the server being loaded.
The &:e parameter applies to user servers that do not process connection functions ("&&") and disconnection functions ("**") corresponding to a specific process, and therefore do not need to be involved in the general process for that purpose. Both parameters, w:e and &:e, can be included in the same loading statement.
If the &:e parameter is specified in the loading statement of the supervisor, the applications calling the Wait for Asynchronous Events (WM) supervisor function do not receive "&&" and "**" events.
LANDP for DOS functional areas can be loaded into high memory. Add the LOADHIGH command to the loading statement, in front of LOADER or LOADERE:
LOADHIGH LOADER (or LOADERE) [servername]
where servername is the name of the server being loaded.
The following commands can be used when you load the LANDP for DOS functional areas.
LOADER EHCDBTR.EXE
LOADER EHCCOMP.EXE
LOADER ELECJO##.EXE [/K:y]
where:
The size of the buffer must be large enough to hold the maximum of:
LOADER FORWARD.EXE /O:vvvvvvvv.vvv [/T:wwww] [/S:xxxxxxxx.xxx] [/K:y] [/H:z]
where:
Values can range from 1 to 6000. The default is 20 (about 1 second).
The parameter value must be the value assigned in the loading statement of the store-for-forwarding server.
LOADER LAN.EXE /pc-id [/N:n] [/B:bb] [/I:x] [/S:y]
where:
The parameter value can be 0 or 1. The default is 0, or the value specified at workgroup level.
The parameter value can range from 1 to 56. The default is 4, or the value specified at workgroup level.
If an incoming message size is bigger than the buffer size, performance degrades.
The parameter value can be 0 or in the range 5 through 3000. The default is 20 seconds. If a value of 0 is specified, only one attempt is made to establish each session, at startup, or after a session has been lost.
The parameter value can be 0 or in the range 10 through 127. The default is 10 seconds. A value of 0 implies no timeout.
The LAN server is needed only when more than one workstation is present in a workgroup that uses NetBIOS as transport protocol. It is included during the process of creating diskettes for distribution.
LOADER EHCLIP.EXE /pc-id [/N:n] [/Y] [/R:r] [/C[:ws-id]] [/P:p] [/J] [/D:d]
where:
The parameter value can range from 1024 to 65535. The default is 52699.
This table is used by LANDP Internet Protocol to save information about datagrams sent, in case they should be retransmitted.
The parameter value ranges from 256 to 65000. The default value is calculated using the following formula:
910 * ((N * 40) / (N + 34))
where N is the number of related workstations.
The parameter value can range from 3 to 70. The default value is 3.
LOADER EHCLRMGR.EXE
LOADER MSRE47##.EXE
LOADER X25NAT##.EXE
LOADER OPER.EXE
LOADER PINP47##.EXE /M
where /M indicates that 4778 magnetic stripe reader capabilities are to be used.
LOADER PRTMGR.EXE
The loader statement for the printer manager server will be included automatically during the process of creating diskettes for distribution if the 3287 printer emulator or the financial printer server is using the parallel port.
LOADER RCMS.EXE /I:xxx /O:yyy [/T:ttt] [/A:mmm] [/L:n] [/P:q] [/C:x] [/R:r]
where:
Attention: If an EHCRCMS.LOG file with n1 lines exists already, and you choose a value for the L parameter that is different from n1, your old file will be destroyed and a new one created. If you want to keep the old file, rename it or copy it to somewhere else before running the LOADER program.
The default is E.
LOADER SFQUERY.EXE [/K:y]
where:
The parameter value must be the highest of the values assigned in the loading statements of the electronic journal and store-for-forwarding servers.
This program is required by the electronic journal and the store-for-forwarding servers.
LOADER SHRDIR.EXE /E:nn
where:
In the client workstations that have IBM DOS 7.1 or higher installed, the customization program includes the following statement in the AUTOFBSS.BAT file:
SHRDIRDD /K:mm
where:
LOADER SHFILE##.EXE [/C:confname] [/B:nnn] [/E] [/S:xxx] [/L:y] [/F:zz]
where:
Another factor that must be considered is that the more buffers you have, the greater is the probability of losing index data when the shared file server is abnormally ended. Thus, if many index buffers are allocated, and the server workstation is switched off with a transaction still in process, or if no RF function has been called, an automatic index rebuild is issued the next time the server is loaded.
This number plus the number of workstations that receive services must not be higher than 245.
The default is 0.
The parameter value can be in the range 10 to 245.
LOADER SNA##.EXE /P:nn
where:
The parameter value can range from 3 to 70. The default is 3.
LOADER SFORFORW.EXE [/K:y]
where:
The size of the buffer must be large enough to hold the maximum of:
LOADER SPV.EXE /pc-id [/S] [/D:yy] [/L:zz] /K:mmm
where:
The parameter value ranges from 7 to 512. It can be specified during customization through the POOLSIZE keyword in the LWSCONF vector.
The default calculated by the customization program is [1.25 x N], where N is the number of workstations that receive services from the workstation you are defining, or provide services to it.
The value is limited by the available memory. In addition, a low value might result in a poor performance. Thus, it is highly recommended to adjust this value accurately. On the panels of the trace tools you can obtain information about the percentage of buffer pool being used.
If the size of the buffer pool is not big enough, the requester might receive status X'01004C46' (no free space in the buffer pool), X'01004C47' (no free space in the remote buffer pool), or X'01004C48' (timeout, due to the fact that a reply is not possible because no free space is available). On the Routines Trace panel of the trace tools you can see the number of times that a requester received these statuses.
For workstations that provide or receive shared DOS directory services, the customization program recalculates the default accordingly.
Increasing the value of mmm will resolve the error.
If you are using the shared DOS directory, a situation might occur where there are insufficient Supervisor buffers. This might result in the following symptoms:
If the /S parameter is omitted, the SI function returns a list of loaded processes. If the /S parameter is specified, the SI function returns loaded and configured processes.
LOADER SDLC.COM /C:x /T:nn /I:yy
where:
The default is N.
The parameter value can range from 10 to 65. The default is 65.
The parameter value can be:
The default is 34.
The parameter values must match the jumper settings on the adapter card.
LOADER SMGR.EXE /D:x /O:yyyyyyyy
where:
LOADER SMOP.EXE
LOADER xxx.EXE [/S:nn] [/T]
where:
LOADER TRDLC.EXE
LOADER DDT.EXE /I:x /R:y /P:nn
where:
The default is I. For application debugging purposes, choose the E parameter value.
The default is I. For application debugging purposes, choose the E parameter value.
The parameter value can range from 3 to 40. The default is 3.
LOADER X25DLC.EXE
LOADER X25DLC2.EXE [/T]
If the X25DLC2 server is used, it is renamed to X25DLC.EXE and loaded accordingly.
If option /T is added to the loading statement, the X.25 trace will be started from the beginning.
LOADER EMU3270.EXE /C:atr /K:kbd /D:dis /I:n [/H:hh] [/W:www] [/B:y] [/S:xxxxxxxx] [/Z:nnnn] [/P:a] [/L:l] [/T:tt]
where:
Use this parameter, in conjunction with /W, to make the emulated alternate screen look like one of the following 3270 models:
Alternate Alternate 3270 model screen height screen width 2 24 80 3 32 80 4 43 80 5 27 132
If this parameter is omitted, the default is 24.
If this parameter is omitted, the default is 80.
If this parameter is omitted, the default is N.
If this parameter is omitted, the default is a name of eight blanks.
The parameter value specified must match the RU size detailed in the bind session.
If this parameter is omitted, the default is 2048.
If this parameter is omitted, the default is Y.
LOADER EMU3287.EXE /x /E:prt [/T:nn] /P:HP [/N:n]
where:
The parameter value ranges from 1 to 60. The default is 15.
Specifies the range of logical printer numbers that can be used. The parameter value can be in the range 1 through 3. Specify:
If the parameter is not specified, the emulator uses the number of parallel printer ports physically installed on the workstation.
LOADER PR47X2##.EXE [/K:n]
where:
The parameter is optional. The parameter value can range from 1 to 4. The default is 1.
LOADER PR4748##.EXE [/K:n] [/H] [/N] [/A:xxxx]
where:
The parameter is optional. The parameter value can range from 1 to 4. The default is 1.
The FREE.EXE utility is provided to unload LANDP for DOS. You can also unload LANDP for DOS by issuing a supervisor function call from an application program. For more information on supervisor function calls, see LANDP Programming Reference. The FREE.EXE, is called as follows:
d:\path\FREE
where:
Notes:
To unload LANDP for DOS, the FREE program must be run from the application VDM after EHCWVDMI. The FREE program unloads only the LANDP modules loaded after Microsoft Windows 3.1 or 3.11.
To unload EHCWGMDI and the servers that were loaded before Windows 3.1/3.11, you must exit Microsoft Windows and then enter:
FREE /W:1
The maximum amount of conventional memory (640 KB) is sometimes not enough for large programs or groups of programs. Lotus Development Corporation, Intel Corporation, and Microsoft Corporation created the Lotus/Intel/Microsoft (LIM) Expanded Memory Specification to enable programs to be loaded into expanded memory.
The LIM Expanded Memory Specification defines the software interface between the Expanded Memory Manager (EMM), a device driver that controls and manages expanded memory, and programs that use expanded memory.
To use the LIM Expanded Memory Specification for loading servers into expanded memory, a special loader program called LOADERE is included in the LANDP for DOS distribution package.
To load a server into expanded memory, you have to select expanded memory for the server during customization. The customization program places the correct statements in the CONFIG.SYS and AUTOFBSS.BAT files, depending on the version of DOS chosen, and the LOADERE program loads the servers into expanded memory. The LOADERE program itself is always loaded in conventional memory.
The following LANDP for DOS functional areas can be loaded in expanded
memory. The user servers that conform to the rules listed in Rules for user servers in expanded memory can also be loaded in expanded memory. Note that the
corresponding definitions are provided during customization through the
DEFSERV vectors.
ASCII-EBCDIC translation server | EHCDBTR.EXE |
3270 emulator | EMU3270.EXE |
3287 printer emulator | EMU3287.EXE |
PIN pad server | PINP47##.EXE |
Electronic Journal | ELECJO##.EXE |
Store-for-Forwarding | SFORFORW.EXE |
Searcher | SFQUERY.EXE |
Forwarding | FORWARD.EXE |
MSR/E server | MSRE47##.EXE |
Financial printer server | PR47X2##.EXE |
4748 printer server | PR4748##.EXE |
Trace | DDT.EXE |
SNA server | SNA##.EXE |
Shared file server | SHFILE##.EXE |
X.25 Co-Processor | X25DLC.EXE |
Operator interface | OPER.EXE |
System manager operator | SMOP.EXE |
System manager | SMGR.EXE |
Local resource manager server | EHCLRMGR.EXE |
Remote Change Management Services | RCMS.EXE |
LANDP Internet Protocol | EHCLIP.EXE |
Notes:
The following PC/Integrator software can also be loaded into expanded
memory:
Banking interactive workstation program | BIWP.EXE |
Banking printer program | BPP.EXE |
Depending on the DOS version selected during customization, your CONFIG.SYS file is updated differently.
If you select DOS, the following statements are added to your CONFIG.SYS file:
DEVICE=HIMEM.SYS DEVICE=EMM386.EXE [parameters]
The second statement is valid only for personal computer systems with a processor higher than 80286. If your systems have processors lower than 80386, you must change your CONFIG.SYS file and use the XMA2EMS.SYS device driver or another specific device driver related to your memory adapter.
Note that the FRAME value must range from C000 to E000, in increments of 400h.
For more information, refer to the DOS library.
LOADERE checks for the largest frame that is available consisting of contiguous pages.
Following is an example of a configuration for a PS/2 Model 70 (80386) with Token-Ring (16Mb (bits) per second), X.25 Co-Processor, and DOS installed. The italicized lines show a possible memory address distribution:
Slot 1 - Token Ring Network 16/4 Adapter/A
Primary or Alternate Adapter........[Primary ]
Adapter Data Rate...................[16 Mps]
ROM Address Range...................[DE000 - DFFFF]
RAM Size and Address Range..........[16 KB / DA000 - DDFFF]
Interrupt Level.....................[Interrupt 2]
Slot 2 - IBM Realtime Interface Co-Processor Multiport/2
Physical Card number...........[Physical Card 0; 02A0H - 02A7H]
Shared Storage Window Location
and Size.......................[D8000 - D9FFF (8 KB Window)]
Interrupt Level.....................[Interrupt Level]
Port 0 Transmit Clock Source...[DCE Sourced Clocking]
Port 0 Receive Clock Source....[DCE Sourced Remote Clocking]
Port 1 Transmit Clock Source...[DCE Sourced Clocking]
Port 1 Receive Clock Source....[DCE Sourced Remote Clocking]
Possible CONFIG.SYS entries could be:
BUFFERS=20
FILES=40
DOS=HIGH,UMB
DEVICE=HIMEM.SYS
DEVICE=EMM386.EXE RAM FRAME=C000 /X=D800-DFFF
DEVICEHIGH=DXMAOMOD.SYS
DEVICEHIGH=DXMCOMOD.SYS
DEVICEHIGH=DXMTOMOD.SYS ST=26 S=26 c=30
LIM EMS involves some restrictions related to loading servers in expanded memory. Besides, user servers to be loaded in expanded memory must conform to the following rules:
To use high memory (between 640K and 1MB), Upper Memory Block (UMB) support is required. Set the CONFIG.SYS file to enable UMB support, following the standard DOS rules.
Because IBM TCP/IP uses UMB support, it is recommended not to load LANDP for DOS functional areas into high memory in IBM TCP/IP environments.
When you install the run-time files on a DOS workstation, take the following into account:
If you load such programs after the servers or the supervisor, unpredictable results might occur.
Assign to the parameters SES and CMD values larger than those needed for the PC LAN Program.
The LANDP family provides a utility program to check the path where the run-time files are located. See Installing and validating system files for more information about this program.
For other utility programs also provided to be used at run time, refer to Run-time utility programs.
This part describes some utilities that you can use when installing and customizing LANDP. It also describes how to tune some of your LANDP servers to obtain better performance.
It contains the following chapters:
The characteristics of the file are as follows:
The records must have the formats shown in Table Table 6. Create only the records that apply to the
communication devices affected by the update. If the record contains
optional fields, include only those that contain changed information.
Table 6. Variable data record formats for VARDAT utility
Definitions for Form column (field format):
The Value of the fields must adhere to the following rules, depending on the DLC. The field format is validated according to these rules.
Notes:
The old subscriber address in the record must exist in the model configuration file and be unique, as only one physical unit is allowed per subscriber address for incoming circuits and for outgoing circuits. After updating, all the subscriber addresses of each type must be different. The only part of this record that is considered variable data is the new subscriber address and the identification number.
DEVICE=DXMC0MOD.SYS address
where address is the PC local administration address.
The program VARDAT.EXE is copied by the customization utility program onto the operational diskettes for the gateway workstations in the branches and loaded before any server. VARDAT.EXE searches for a file called VARDAT.CFG, which is the file that contains the communication variable data. VARDAT.EXE performs the following steps:
If errors are found, the program generates a return code. See LANDP Problem Determination.
If no errors are found, the program updates the communication configuration files and deletes the variable communication data file VARDAT.CFG.
You can create the VARPARM.SPC file using any text editor. The file has the following format:
LANCONFG NAME = newwgid, SUFFIX = newsuffix, ID4721 = new4721id
where:
The VARPARM.SPC file is renamed to VARPARM.OLD at the end of the process, so that it is not processed each time you run AUTOFBSS.
If the VARPARM.SPC file is not available, the VARPARM.EXE program ends with no error and no change is made. If errors are found in the VARPARM.SPC file, the VARPARM.EXE program generates a return code. See LANDP Problem Determination.
On Windows, a native Windows 32-bit version, VARPARMW.EXE, provides equivalent function.
The 16-bit version, VARPARM.EXE, can be run under DOS in a VDM.
|
This section describes the utility programs provided to check record formats,
profiles and parameters, and installation paths.
|
Changes in the record definitions or in the electronic journal, store-for-forwarding, forwarding, or shared file server profiles can cause unpredictable errors at run-time. Make sure that the values specified in the new profiles are compatible with the existing shared files.
To prevent this, the customization program creates all the configuration
files related to these definitions with a file name extension that is
different from the one used at run-time:
Server profiles | From Customization | At Run-Time |
---|---|---|
Shared file profile |
.DBN .PCN |
.DBD .PCB |
Electronic journal profile | EJOU.PRN | EJOU.PRO |
Store-for-forwarding profile | STOR.PRN | STOR.PRO |
Forwarding profile | FORW.PRN | FORW.PRO |
In the run-time environment, when AUTOFBSS is running, the program NEWCFG.EXE is loaded. If any of the configuration files created by a new customization are found, the program NEWCFG.EXE checks to see if the same configuration file also exists with the different run-time name.
You can then choose to delete either:
Note, however, that the configuration file for the Service Availability Manager (EHCSAM) is handled separately. The program SAMCFG.EXE performs a similar function to NEWCFG.EXE, but specifically processes the configuration file for EHCSAM. SAMCFG.EXE must be invoked prior to loading EHCSAM in AUTOFBSS.
The following is a list of files that must be in the paths specified during the software building process.
The installation and validation utility program EHCVAL.EXE checks the customized paths in the FBSSPATH.DAT file against the servers being loaded. EHCVAL validates whether the path exists, and if it does not, enables the creation of the path. The program also validates the existence of all system files needed, and copies or updates all files required by the servers to be in the path. The copied files are erased from the original directory. In the run-time environment, when AUTOFBSS is running, the program EHCVAL.EXE is loaded.
Error messages, information messages, and prompts that require a response may be displayed. The messages are contained in the EHC.MSG file, or in the EHCMSG.DLL file for LANDP for Windows; see the LANDP Problem Determination book.
This chapter contains instructions for:
You can migrate customization data provided for:
Customization data provided for PC/Integrator, and PC Integrator/2 can also be migrated.
This section applies when you want to process more than one workgroup configuration at the same time.
The LANLIMIT.SPC file is located in the EHCCUS directory. You can edit the LANLIMIT.SPC file using any text editor, and specify the workgroup configurations to be processed.
INCLUDE = langroup\lanname
OMIT = langroup\lanname
Note that if langroup is omitted, EHCCUS is assumed.
You cannot use both INCLUDE and OMIT statements at the same time. Comments must start with /* and end with */.
The LANLIMIT.SPC file provided with the customization program has the following contents, and specifies that all the workgroup configurations will be processed.
INCLUDE = *
You can modify the LANLIMIT.SPC file to meet your requirements. Three examples follow.
Example 1:
Only the workgroup configurations located in the GROUP2 directory, and the workgroup configuration named CONF47 and located in the GROUP4 directory, will be processed.
/* LANLIMIT.SPC Example 1*/ INCLUDE = GROUP2\* INCLUDE = GROUP4\CONF47
Example 2:
All the workgroup configurations, except for those located in the GROUP6 directory, will be processed.
/* LANLIMIT.SPC Example 2 */ OMIT = GROUP6\*
Example 3:
Only the workgroup configurations located in the GROUP8 directory, and the workgroup configuration named CONF13 and located in the EHCCUS director, will be processed.
/* LANLIMIT.SPC Example 3*/ INCLUDE = GROUP8\* INCLUDE = \CONF13
The return codes generated by both the migration and the generation procedures are classified into four types. The following list shows the types of return codes, starting with the least severe. An identifier for each type appears in parentheses.
The identifier of the type of return code is displayed as the last character of the return code. For example, the following is displayed on the screen:
00039W This is an attention or warning return code. It ends with a 'W'.
When running the migration or the generation procedure, you can specify the highest severity allowed.
This section explains how to perform the migration step. It shows the data used by the migration procedure, and how to start that procedure.
The migration procedure reads data from the directories that contain FBSS customization data. Then, using that information, the procedure generates data in the internal repository.
The migration procedure uses the customization information that the FBSS customization program generated in the directories in the following list. They are located either in the root directory or in a first level subdirectory. The list also shows the contents of the directories.
Note that DIFFERENT stands for the name of any directory you created during customization to locate your workgroup configurations.
The directories containing the information for each workgroup configuration are located under the FBSSCUS and DIFFERENT directories. In turn, the directories containing information for each workstation are located under the workgroup configuration directories.
If you used the automatic building option of the FBSS customization program, the migration procedure uses the automatic building file created during the building process.
If some customization data cannot be obtained from existing FBSS customization data, or if the automatic building file does not exist, the migration procedure provides defaults, when possible, or generates ? symbols. When ? symbols are generated, the migration procedure ends with a non-zero return code.
When it is displayed on the screen, you should:
When you have finished updating the LANCONF.SPC files, run the validation procedure.
To convert an FBSS/2 workstation configuration to a LANDP for OS/2 workstation configuration, that is to migrate to a workstation running IBM OS/2 Warp V4.0, or higher, you have to:
When you have finished updating the LANCONF.SPC file, run the validation procedure.
To convert all the FBSS/2 workstation configurations to LANDP for OS/2 workstation configurations, the migration procedure provides a parameter to specify it.
You can display online information about the MIGRATE procedure. From the EHCCUS directory, enter:
MIGRATE ?
To start the migration procedure, from the EHCCUS directory, enter:
MIGRATE [parm1] [parm2] [parm3] [parm4] [parm5] [parm6]
If you specify LAN, but there is no common data in the internal repository, COMMON is also assumed. If the parameter is omitted, and there is no common data in the internal repository, both common and workgroup data are processed.
If the parameter is used, only the workgroup configuration specified will be processed, no matter the LANLIMIT.SPC file contents.
The parameter format is:
lanpath\lanname
If lanpath is omitted, FBSSCUS is assumed as the directory where the source workgroup configuration data is located. The migrated workgroup configuration data is located in the current path, that is, in the EHCCUS directory.
The default is 1. For further information, refer to Return codes.
d:\dirname\
where d is the drive identifier and dirname is the name of the directory. The default is the current first level subdirectory.
The parameter value must be NEWOS.
The parameter value must be NEWDOS.
The parameters can be specified in any order. You will get the CUSPARM.LST file in the EHCCUS subdirectory, containing pointers to any problems that arise.
To avoid long processing, it is strongly recommended to run the migration procedure specifying first the COMMON parameter value. Then, run the procedure specifying the LAN parameter value.
In addition, when processing workgroup configuration data, you can select the workgroup configurations affected by the process. See Selecting workgroup configurations.
This section explains how to perform the generation step. It shows how to start the generation procedure, and the data generated by that procedure.
The generation procedure reads data in the internal repository, created either by the migration procedure or by the validation procedure, and generates vectors in the .SPC files.
If an .SPC file with the same name and in the same path already exists, the procedure creates a backup of the existing .SPC file, with the same filename and extension BAK. If a .BAK file corresponding to the .SPC file already exists, the procedure erases the existing .BAK file.
If an .SPC file is lost, you can recover it running the generation procedure and using the current data in the internal repository.
You can display online information about the GENSPEC procedure. From the EHCCUS directory, enter:
GENSPEC ?
To start the generation procedure, from the EHCCUS directory, enter:
GENSPEC [parm1] [parm2] [parm3] [parm4]
The default is LAN.
If the parameter is used, only the workgroup configuration specified will be processed, no matter the LANLIMIT.SPC file contents.
The parameter format is:
langroup\lanname
If langroup is omitted, EHCCUS is assumed.
The default is 1. For further information, refer to Return codes.
If the parameter is specified, the customization data processed is automatically removed from the internal repository. Thus, after running the generation program, the data is stored only on the .SPC files.
If the parameter is not specified, the customization data processed also remains stored in the internal repository.
The parameters can be specified in any order. Return codes generated by the generation procedure are displayed on the screen.
To avoid long processing, it is strongly recommended to run the validation procedure specifying first the COMMON parameter value. Then, if it applies, run the procedure specifying the MODELS parameter value. Finally, run the validation procedure again specifying the LAN parameter value.
In addition, when processing workgroup configuration data, you can select the workgroup configurations affected by the process. See Selecting workgroup configurations.
After generation of .SPC files, the customization data is stored in vector format in those files. The common data is stored in the COMMON.SPC file, in the EHCCUS directory.
The workgroup configuration data is stored in the LANCONF.SPC files, in the yyyyyyyy\xxxxxxxx directories, where:
The vectors in a LANCONF.SPC file are:
The model configuration data is stored in the MODELS.SPC file, in the EHCCUS directory. The vectors in that file are:
Because the model concept has been introduced with the LANDP customization, no data exists in the FBSS customization files to generate the model configuration vectors. These vectors are generated only if you have already created a MODELS.SPC file, and run the validation procedure specifying the MODELS parameter value.
This chapter explains the following utility programs, which enable you to list customization data in different formats:
The LISTRTOC program is provided to generate the internal repository table of contents. The table of contents is generated on a file named CUSPARM.LST.
You can display online information about the LISTRTOC procedure. From the EHCCUS directory, enter:
LISTRTOC ?
To start the procedure, from the EHCCUS directory in your customization workstation, enter:
LISTRTOC [parm1]
where:
The default is LAN.
The EHCLIST program is provided to list and view the structure of your workgroup configurations. You can use this program after you have defined at least one workgroup. Two types of listings can be obtained: one oriented towards servers and the other towards services.
You can display online information about the EHCLIST procedure. From the EHCCUS directory, enter:
EHCLIST ?
To start the procedure, from the EHCCUS directory in your customization workstation, enter:
EHCLIST parm1 parm2 parm3 parm4 parm5
where:
The parameter has two possible values:
You can print the report or store it on a file. To print the report, enter the device name of the printer port to be used: LPT1, LPT2, or LPT3.
To store the report on a file, enter the name of the file. The file will be placed under the EHCCUS subdirectory.
The parameter has two possible values:
The following is an example of a servers listing for a workgroup
configuration that contains an OS/2 workstation with an SNA server, MQSeries
Link server, and a user-defined server, and a Windows workstation with an ODBC
query server, shared-file server and a 47x2 financial printer server.
Servers | Server PCs | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
GW OS/2 |
S1 NT |
|
|
|
|
|
|
|
| |
EHCMQ## | * |
|
|
|
|
|
|
|
|
|
EHCODB01 |
| * |
|
|
|
|
|
|
|
|
PR47X2## |
| * |
|
|
|
|
|
|
|
|
SHFILEBA |
| * |
|
|
|
|
|
|
|
|
SNA## | * |
|
|
|
|
|
|
|
|
|
USERSVR1 | * |
|
|
|
|
|
|
|
|
|
In this listing you can see all the servers installed in the workgroup and the workstations in which they are installed.
The services listing provides a complete picture of your workgroup configuration and the connections between the server workstations and the client workstations. For a complete listing of all the configurations, make sure you define, under communication configuration customization, all the communication parameters. If you have not defined the communication parameters, the listing will show question marks where services need to be defined.
Following is an example of a services listing for the same workgroup
configuration model as above:
Served PCs and Services |
| Server PCs | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
|
GW OS/2 |
S1 NT |
|
|
|
|
|
|
|
| |
S1 NT |
|
|
|
|
|
|
|
|
|
|
|
PR47X2PP |
|
| * |
|
|
|
|
|
|
|
|
W1 OS/2 |
|
|
|
|
|
|
|
|
|
|
|
USERSVR1 |
| * |
|
|
|
|
|
|
|
|
|
EHCODB01 |
|
| * |
|
|
|
|
|
|
|
|
PR47X2## |
|
| * |
|
|
|
|
|
|
|
|
SHFILEBA |
|
| * |
|
|
|
|
|
|
|
|
W2 DOS |
|
|
|
|
|
|
|
|
|
|
|
SNA |
|
|
|
|
|
|
|
|
|
|
|
EMU32701 |
| * |
|
|
|
|
|
|
|
|
|
EMU32702 |
| * |
|
|
|
|
|
|
|
|
|
EHCMQ01 |
| * |
|
|
|
|
|
|
|
|
|
SHFILEBA |
|
| * |
|
|
|
|
|
|
|
|
W3 NT |
|
|
|
|
|
|
|
|
|
|
|
EHCMQ01 |
| * |
|
|
|
|
|
|
|
|
|
EHCMQ02 |
| * |
|
|
|
|
|
|
|
|
|
EHCODB01 |
|
| * |
|
|
|
|
|
|
|
|
PR47X202 |
|
| * |
|
|
|
|
|
|
|
|
SHFILEBA |
|
| * |
|
|
|
|
|
|
|
|
The server workstations are shown horizontally at the top of the listing. On the left side, shown vertically, are the client workstations and the services they receive. For example:
This chapter contains information on how to tune the performance of some LANDP components. The following list shows what these specific components are, and where to find the related information:
You can also tune the server loading time parameter /B:nnn (number of index buffers) in order to improve the performance, if there is enough memory available in the system. The value nnn specifies the number of additional (above 10) 1KB index buffers to be allocated. More index buffers increase system throughput, but also reduce the amount of free storage available for the server workstation. A rule of thumb is that the number of buffers should be 10 per workstation using the shared-file server simultaneously. A practical limit is approximately 100, depending on available storage size. The maximum value for nnn is 484.
Another factor that must be considered is that the more buffers you have, the more likely you are to lose index data when the shared-file server is abnormally closed. Thus, if many index buffers are allocated, and the server workstation is switched off with a transaction still in process, or if no RF function has been called, an automatic index rebuild is performed the next time the server is loaded.
Note that these considerations are especially important when you specify a small number of simultaneously open files with the /F loading parameter.
You should write applications that access the query server in a way such that they can work properly with this isolation level.
The server loading parameters /P, /T, and /F affect considerably the throughput of the server. The number of processes, /P, and the number of threads, /T are related to the number of workstations that are accessing the server at the same time. In order to improve performance, fast cursor operation, /F, is recommended for applications that make extensive use of the functions GN, GP, GU, and GW, or for applications that access large data tables.
To achieve optimum performance, the buffer pool size of the server workstation should be large enough so as to allocate all incoming requests, which are received from all the client workstations. However, this solution could lead to a shortage of memory in the server workstation, therefore you should find a compromise between performance (that is, buffer size of the shared DOS directory client workstations) and memory requirements (buffer pool size of the shared DOS directory server workstation). This consideration is especially critical when you are going to make copies of large remote files.
Sizing the client workstation buffer and the server workstation buffer pool must meet the specific requirements of every LANDP workgroup.
Start the VERSION utility program from the EHCMAINT directory on the OS/2 or Windows customization workstation, or from the directories that contain the LANDP product components on the production site workstation.
To start the program, do the following:
VERSION [path1] [/o:path2]
where:
If you do not specify this parameter, the VERSION utility program searches only the current directory and the LANDP reserved subdirectories.
If you do not specify this parameter, the VERSION program places VERSION.TXT in the current directory.
The VERSION utility program generates the following output when it runs successfully, and all information is available:
ID=ssssssss VL=vrmxx nnnnnnn ffffffff.fff
vr is a variable that identifies which LANDP Version 6 components use a program:
For the FBSS products, PC/Integrator, and PC Integrator/2, v is the version and r is the release.
m is the modification level.
xx is a sequence number that corresponds to the number of modifications that have been applied to the LANDP program.
For information and procedures for installing program fixes, see Applying program fixes--APPLYFIX.
Before starting the version utility, make sure that you are running from a shell with the current LANDP environment set up.
To run version, issue the following command:
version [-o output] where output is the name of the output file. The default is version.txt.
For more information about the version utility, refer to the LANDP Problem Determination.
| The IBM Support Center uses the following naming convention for program
fix files:
filename.ext where:
|
An example of a program fix file name might be:
HC52249.D60
You must install program fix files on the workstation that is used for customization. To install program fixes, refer to the information that relates to the LANDP product components you are updating.
Use the APPLYFIX utility program if you are installing program fixes for a LANDP product component.
The APPLYFIX utility program performs the following functions:
| To start the apply-fix process, do the following:
Notes:
|
APPLYFIX A:\HC52249.D60
APPLYFIX A:\*.* /all
APPLYFIX A:\HC52249.D60 /?
If you do not specify the /all option, the APPLYFIX utility program displays a screen containing information about the program fixes. From this screen, you can do the following:
The APPLYFIX utility program checks the component ID, the release, the version level, and the directory where the program fix is to be installed. It then installs the fix and replaces product component files, as required.
The APPLYFIX utility program updates two history files by recording the changes made when program fixes were installed. The history files are named LANDP.HST and TOTS.HST. Both files reside in the EHCMAINT directory.
LANDP.HST and TOTS.HST are text files. You can view or print the files using the TYPE or PRINT commands from a command prompt.
After you install program fixes, the updated product components can be copied to diskette or other media for transfer to the workstations in your workgroups.
When the APPLYFIX utility program replaces a file, it saves a backup copy of the replaced file in a directory named FIXSTORE. The file is saved with its program name and its version level number as the extension.
SPV.Dxx
SPV.Oxx
SPV.Nxx
SPV.Lxx
SPV.Axx
SPV.Pxx
SPV.Bxx
SPV.Sxx
In the above list xx is a numeric value identifying the version of the backed-up program.
You can retrieve files in the FIXSTORE directory by running the APPLYFIX utility program. You would start the APPLYFIX program, specifying the backup directory and program file that you want to retrieve. For example:
APPLYFIX ..\FIXSTORE\SPV.AXX
Part 1 of the tutorial shows you how to navigate through the editor, how to add new common parameters, workstations, servers and clients, and how to edit their properties and parameters.
The tutorial explains how to customize a basic workgroup with four workstations, with an SNA server and a system management server.
To run the LANDP customization editor you must have one of the following operating systems installed on your computer:
You also need to have the Java Runtime Environment (JRE) Version 1.3, or later, installed.
To run LANDP customization, double-click on the "LANDP customization editor" icon that is in a directory display window on the screen. The main editor window appears with the title 'LANDP customization editor' as a heading.
The main editor window (see Figure 11) has three main areas:
The central tabbed pane contains two panes for editing common parameters and workgroup parameters:
Click on each of the tabs to view the different parameter definition areas. If objects disappear off the bottom of a list, a scroll-bar appears at the right of the list. Use this to scroll through the entire list.
Now click on the workgroup parameters pane, and then click on the 'Add Workgroup' button. A new window should appear with a title at the top: [LANDP customization - New workgroup]. This window is where the properties for each new workgroup are created, and is the first of the new workgroup guide.
The guide is split into four pages:
The guide pages always contain four buttons at the bottom righthand side of the page:
When the guide closes, a new workgroup icon appears in the tree on the left of the tabbed pane, and the parameter pane for the workgroup is displayed with the parameters entered for the workgroup displayed in their respective fields.
The workgroup parameter window is split into two panes, one for general parameters and one for advanced parameters.
We have already used the button bar to add a new workgroup. The other functions available from the button bar, from left to right, are:
The first two buttons allow you to open and save common parameter files (COMMON.SPC files) and workgroup parameter files (LANCONF.SPC files).
Three buttons are supplied to cut, copy and paste data. Data selected in a tree can be copied or cut, and then pasted to a tree that has data in the same format. For example, common vectors can only be pasted to a common vector list.
The other buttons allow new data to be added using guides.
The button bar can also be separated from the editor window by selecting it and dragging it. It then appears in a window of its own. To place it back on the editor window, select the 'X' button in the top right hand corner.
Now click on the 'Add a new workstation' button. A new window appears with a title 'LANDP customization - New Workstation.'
The guide is split into three pages:
This guide contains the same control buttons as the 'New Workgroup' guide.
Click on the 'Finish' button to add the workstation. The window should close, and you should see a new icon in the workgroup parameters tree representing the new workstation. The name of the workstation name is displayed next to the icon.
Now try adding some more workstations with the following names and operating systems:
Once you have added these, you should have four icons representing workstations in the workgroup tree view with the four names of the workstations.
Select workstation 'AA' in the list, and its properties page should be displayed. The workstation properties window is similar to the workgroup properties window in that it is split into two panes, one showing the general properties, and the other showing the advanced properties.
Now click on the 'Add server' button.
Click on the 'Add Server' button on the button bar. The server editing guide now opens. There are just two pages.
The first page contains the workgroup and workstation fields, as well as the name field. Type in 'SNA' in the name field, which is a combo-box. The server can also be selected from the drop-down list. The other two fields should be filled in automatically with 'SAMPLE1' and 'AA' respectively. Select the 'Next' button. The second page is displayed.
The second page contains fields for selecting a model, expanded memory selection and loading parameters. Ignore these and select 'Finish'. A server icon appears in the tree under Workstation AA. The server parameter window is also displayed to the right.
Some servers have extra parameters that can be specified. These are displayed in the advanced pane. There can be from two to thirty fields that can be edited. Click on the 'Advanced' tab to display these parameters. For details see Appendix D, Editing configuration data.
At the bottom of the window are two buttons, 'Cancel' and 'OK'. Selecting 'Cancel' restores the parameters to their values before they were edited. Selecting 'OK' saves the changes made.
Figure 11 shows that the name of the field is shown, followed by the range of permissible values, and whether that parameter is required or optional.
Two types of field are used.
The first is the standard text entry box. Simply click a mouse button when the cursor is over the field, and the caret (a thin blinking line) appears in the box.
The second type of field is a choice box. When you click on the arrow at the right hand side of the choice box, a list appears showing the values that can be selected. Click on one of these values and it appears in the choice box.
Experiment with these data entry methods, and then click on 'OK' to save the parameters. Now return to the general server properties editing window by selecting the 'General' tab. Try adding another server with name 'TRDLC' and experiment with the advanced parameter editing window.
To add clients, follow the procedure for adding servers described in Adding a New Server, but click on the 'Add Client' button on the button bar. The guide is slightly different.
The first page contains the fields for specifying which workgroup and client workstation to add the client to. It also allows selection for which workstation is providing the resources, or the servers.
The second page allows client selection, from a list of available clients from the workstation providing resources. In this case, it should only contain 'SNA##' because this is the only resource from workstation AA that can have a client.
With any resource that ends with a '#' or a '##', a session ID or suffix is needed. Enter '01' in the suffix field. This uniquely identifies the client on the workstation it is added to. An alias parameter can also be supplied. This parameter is optional and is not needed now.
Add two new clients with names 'SNA01 and 'SNA02'. To edit the parameters, follow the same procedure as for servers. The clients, when added, should appear in the tree view.
Editing clients and servers and their parameters forms the main part of creating or editing a LANDP customization file. Therefore, familiarization with these procedures is essential for using the software effectively. The specific details about each parameter are listed in Appendix D, Editing configuration data.
Saving
To save the workgroup details, either select the save icon from the button bar, or use the drop down menu from the top of the screen and click on the 'File' menu.
A menu appears. Click on the 'Save' menu item and a new window opens with a title 'Save'. This is a standard file menu. Enter the name of the workgroup list as 'LANCONF.SPC' in the file name field, and click on the 'OK' button to save it in the currently selected directory. Click on the 'Cancel' button to exit the save window without saving.
Opening
To open a new workgroup list, select the 'Open' menu item from the file menu on the workgroup list window. From this file window, locate the directory where the files are stored, and double-click on the file that you want to open. Alternatively, type in the path name of the directory in the file name field.
When you have experimented with adding workstations, clients and servers, and editing their parameters, save your file as 'LANCONF.SPC.
Well done. You have now finished the first part of the tutorial.
This section of the tutorial covers the editing of common parameters. It is very similar to the editing of workgroup parameters, but there are a few differences.
First, select the common parameters tab on the main editor window. The tree on the left should display a common vector list with a list of vectors. These are the default vectors for LANDP customization, and is the equivalent to running the 'CREATE' command (see The CREATE utility program).
Selecting one of the vectors in the tree displays the parameters for that vector in the panel on the right of the editor. Try selecting some of the different vectors. Selecting any of the 'XLATETBL' vectors displays a list of parameters. This is the only type of parameter that is unique to common vectors. Now click on the 'Add Vector' button.
A new window should appear with a title at the top: [LANDP customization - New Common Vector]. This window is the first page for the new vector guide, which has two pages:
Some vectors can be appropriate for more than one server. This is not a problem, since whatever vector you define is available to the other servers once LANDP has been customized. When you click 'Finish', the guide disappears and a new vector icon is displayed in the common vector list. The parameters for that vector are displayed in the main editor to the right of the tree view.
Try adding the following vectors for a new shared file record:
Saving
To save the common vector list, either select the save icon from the button bar, or use the drop down menu from the top of the screen and click on the 'File' menu.
A menu appears. Click on the 'Save' menu item and a new window opens with a title 'Save'. This is a standard file menu. Enter the name of the vector list as 'COMMON.SPC' in the file name field, and click on the 'OK' button to save it in the currently selected directory.
LANDP only uses one common vector list when running the customization process (see Tutorial Part 3: Validating and distributing) which is located in the customization root directory (EHC/EHCCUS). Click on the 'Cancel' button to exit the save window without saving.
Opening
To open a new common vector list, select the 'Open' menu item from the file menu on the workgroup list window.
From this file window, locate the directory where the files are stored, and double-click on the file you want to open. It is called 'COMMON.SPC'.
Alternatively, type in the path name of the directory in the file name field.
When you have experimented with adding common vectors, and editing their parameters, save the file as 'COMMON.SPC.'
An example of a common vector file is in the LANDP install directory, EHC\EHCCUS\SAMPLE2.
This section of the tutorial covers the validation and distribution of customization data. Validation is a process which checks the customization files for errors. Distribution is the process whereby the customization files are used to generate the lists of files needed for each LANDP workstation, and then send them to the required paths.
There are three different types of customization files:
The COMMON.SPC and MODELS.SPC files must be located in the EHCCUS directory created by the installation program. Each LANCONF.SPC file should be contained in a separate directory. These directories can be located either in the EHCCUS directory or in any directory that you create at the same level as the EHCCUS directory. You can also create a directory for each group of workgroup configurations to be defined.
Start validation either by selecting the 'Validate' button from the button bar or from the 'Tools' menu.
A new window appears that displays the validation guide. This is split into two pages:
To specify just one configuration, enter its file path into the field 'workgroup configuration to be processed'.
To specify more than one configuration, select the 'Add' button to add the file path to the list.
To remove a file path, select it and then select the 'Delete' button.
This list of file paths can be opened or saved as a file called 'LANLIMIT.SPC' in the LANDP customization directory (EHC/EHCCUS), using the open and save buttons provided.
A check box also allows the selected file paths to be either included in the validation process or omitted. If the file paths are to be included (check box not selected) then these are the only file paths to be customized. This is the default setting. If the check box is selected, then all relevant file paths found in the customization path (EHC/EHCCUS), except for the file paths listed, are validated. The default is that all file paths are processed.
Enter 'SAMPLE1' into the field 'workgroup configuration to be processed'.
A separate list is provided for specifying the highest severity of return codes. Leave this as 'Admit only informative return codes'.
Selecting the 'Finish' button starts the validation process.
The guide window is replaced by a status window that shows the progress of the validation process.
If the validation is successful, a message appears to indicate this. If you then select 'OK' the status window is closed.
If an error occurs, the incorrect data is displayed in the status window, together with an indication of where the error is, and how to fix it. Once the file has been edited to fix the problem, the file can be saved, and the validation process can be restarted. This process might need to be repeated several times if a large number of files are being processed.
Start distribution either by selecting the 'Distribute' button from the button bar or from the 'Tools' menu.
A new window appears that displays the distribution guide. This is split into four pages:
To specify just one configuration, enter its file path into the field 'workgroup configuration to be processed'.
To specify more than one configuration, select the 'Add' button to add the file path to the list.
To remove a file path, select it and then select the 'Delete' button.
This list of file paths can be opened or saved as a file called 'LANLIMIT.SPC' in the LANDP customization directory (EHC/EHCCUS), using the open and save buttons provided.
A check box also allows the selected file paths to be included in the validation process or omitted.
If the file paths are to be included (check box not selected) then these are the only file paths to be customized. This is the default setting.
If the check box is selected, then all relevant file paths found in the customization path (EHC/EHCCUS) are validated, except for the file paths listed. The default is that all file paths are processed.
Enter 'SAMPLE1' into the field 'workgroup configuration to be processed'.
Select 'Workgroup Data' from this list. A separate list is provided for specifying the highest severity of return codes. Leave this as 'Admit only informative return codes'.
A button 'Generate files' starts the generation process for creating runtime files. A check box labelled 'alternative path' also permits an alternative path to be specified if selected. The path field and button are made operational, and the generated files are copied to this path.
Selecting the 'Generate files' button produces a separate status window demonstrating the generation process. If it completes successfully, a message appears to indicate that validation has completed successfully. If you then select 'OK', the status window is closed.
Select 'next' on the guide page to continue once processing has completed, or to skip this step.
If an error occurs, the incorrect data is displayed in the status window, together with an indication of where the error is, and how to fix it. Once the file has been edited to fix the problem, the file can be saved. Selecting 'Generate files' again restarts the generation process. This process might need to be repeated several times if a large number of files are being processed.
All the workstations for the specified workgroup which require distributing are displayed in a list. By default, the entire workgroup is selected.
Selecting the path button next to the path field opens a file window where a path, for distributing files to, can be specified. Alternatively, individual workstations can be selected from the list with an associated path. This list of path names can be saved and reloaded to prevent having to specify different path names each time.
Selecting the 'Save' button opens a file window where the file 'DISTRIB.LST' can be saved. Selecting the 'Open' button opens a file window where a list can be opened.
Finally, selecting the 'Finish' button starts the distribution process.
The guide window is replaced by a status window that shows the progress of the distribution process.
If the distribution process completes successfully, a message appears to indicate this. If you then select 'OK' the status window is closed.
If an error occurs, the incorrect data is displayed in the status window, together with an indication of where the error is, and how to fix it. Once the file has been edited to fix the problem, the file can be saved, and the 'Continue' button can be selected from the guide window to continue distribution. This process might need to be repeated several times if a large number of files are being processed.
By now you should have quite a good working knowledge of the LANDP customization editor. However, there are still some essential functions that haven't been touched upon yet.
Some of the functions in the LANDP customization editor haven't been mentioned yet, and you should know where to find them.
File
This covers functions affecting the whole workgroup list, such as saving and loading.
Edit
View
Tools
Help
There are some things that can't be done with the LANDP customization editor.
Creating Dynamic Workgroups
Once you have specified workgroup details, and the software has been distributed to all the workstations, it is likely that in the future changes might need to be made. For example, an extra workstation might need to be added.
However, the workgroup can not simply be edited to add or modify data once the software has all been distributed. For example, once the workgroup is up and running, a new workstation can not be added simply by reloading the workgroup file, adding the new workstation and distributing the files to that new workstation.
This is because each workstation in the workgroup needs to know about every other workstation in the workgroup for the client/server relationships to operate successfully. This means that all the software needs to be redistributed to all workstations whenever a workgroup is changed.
Selecting and copying multiple objects
Within the customization editor, only one object in a tree view can be copied at the same time.
Re-sizing the editor screen
The customization editor uses a fixed screen size which can be viewed at a minimum resolution of 800 x 600. This cannot be re-sized.
Online help is available by selecting the Help menu.
Selecting 'Help Topics' opens the main help window with a list of topics providing further assistance.
'Books Online' directs you to the LANDP website that gives information about the latest support and any fixes that might be needed.
The 'About Box' gives information about the current version of the Customization Editor. This information is required if you request any assistance directly.
Error messages in the LANDP customization editor appear when you run the validation and distribution commands on a particular workgroup customization file. The error is displayed in the status window. See Tutorial Part 3: Validating and distributing for more details.
I cannot close the windows.
Most windows have 'OK' and 'Cancel' buttons on them, often at the bottom of the window. The bottom of the window might have moved off the bottom of the screen. Click on the title bar of the window and drag it towards the top of the screen. If there are no obvious buttons, use the 'X' button in the top right corner of the window. No data is lost if you do this.
Clicking on the graphical icons does not select them.
To select a workstation on the workgroup window, or a client or server on the workstation window, click on the object with the left mouse button.
I cannot see all the workstations/servers/clients in the tree view.
In the workgroup parameters pane, scroll down using the scroll bar at the right of the tree view. Alternatively, adjust the screen resolution to a higher resolution.
I cannot find all the parameters for the server or client objects.
Click on the 'Advanced' tab on the workgroup parameter editing window to view the separate parameter editing pane.
I cannot see all the vectors in the tree view. In the common parameters pane, scroll down using the scroll bar at the right of the tree view. Alternatively, adjust the screen resolution to a higher resolution.
The data that I entered has been lost.
When you have finished entering data for a vector, select the OK button in the bottom right of the main panel to save the new values.
Clients are shown on the workgroup parameter pane as nodes on the tree view, each with an icon and the client name. Each workstation must have at least one client or server connected to it.
The parameters for each client are displayed in the 'General' properties pane on the main editor window. Each client has a name, as well as an alias name, which is used by applications when requesting services. Some clients have extra parameters which can be edited by clicking on the 'Advanced' button to open the advanced properties pane.
Adding a client To add a new client, click on the 'New Client' button on the button bar or 'Edit' menu. The 'new client' guide opens. Enter the name of the client, and the name of the workstation providing the services. Enter other parameters if required. Select the 'Finish' button to store the details.
Removing a client Select the clients icon in the tree view on the workgroup parameter pane and press the right mouse button to display the pop-up menu from the list. Select the 'Delete' option, and the chosen client is removed.
Common vectors define data that is common to all workstations and workgroups. They consist of defaults, tables, record definitions and profiles. The list of currently defined vectors is displayed in a tree view, and can be viewed by selecting the 'Common Parameters' tab on the main editor window. To edit a vector, simply select it and its parameters appear to the right of the tree view.
Adding a common vector To add a new common vector, either select the 'New Common Vector' button from the button bar on the main editor window, or select it from the 'Edit' menu. The 'New Common Vector' guide opens. Select the server and type of common vector that is required, select 'Finish' and the guide closes. The newly created vector is added to the common vector list, and its parameters are displayed on the right hand side of the editor window.
Removing a common vector To remove a common vector, select it and press the right mouse button. A pop-up menu is displayed. Select the 'Delete' option, and the common vector is removed.
Distribution is the process which generates the lists of files needed for each LANDP workstation, and then sends them to the required paths. Start the distribution process by selecting 'Distribute' from the button bar or 'Tools' menu. The distribution guide opens. Select the customization directories that require distributing, and which types of data. Selecting 'Generate' starts the file generation process for each workstation. The final page of the guide provides the ability to distribute the files to either a single path for the entire workgroup, or individual paths for each workstation.
Errors If an error occurs during distribution, some information about the problem is displayed in the status window together with an indication of where the error is, and how to fix it. Once this has been edited to fix the problem, the file can be saved, and the 'Continue' button can be selected from the status window to continue distribution. This process might need to be repeated several times if a large number of files are being processed.
The whole aim of the LANDP customization editor is to enable easy editing of the LANDP configuration data files. These files contain data for defining LANDP workgroups.
There are three different files used in LANDP customization:
For more information about these files, see Preparation of customization data.
OpeningTo open new configuration files, select the 'Open Workgroup List' option from the 'File' menu on the Workgroup List menu. Then use the filer window to locate the folder that contains the files you want to open, select the file and then click on the 'OK' button to open the file.
SavingTo save the workgroup files, select the 'Save Workgroup List' option on the 'File' menu on the workstation list window. Use the filer window to select the folder where you want to save the data, and click on the 'OK' button.
To search for a particular object (for example, Workstation) enter the name in the search field above a tree view in the main editor window. If more than one search term is found, select the search button again to proceed to the next match.
Servers are shown on the workgroup parameter pane as nodes on the tree view, each with an icon and the server name. Each workstation must have at least one server or server connected to it. The parameters for each server are displayed in the 'General' properties pane on the main editor window. Each server has a name, as well as some optional parameters which can be defined. Some servers have extra parameters which can be edited by clicking on the 'Advanced' button to open the advanced properties pane.
Adding a server To add a new server, click on the 'New Server' button on the button bar or 'Edit' menu. The 'new server' guide opens. Enter the name of the server, and any other parameters if required. Select the 'Finish' button to store the details.
Removing a server Select the servers icon in the tree view on the workgroup parameter pane and press the right mouse button to display the pop-up menu from the list. Select the 'Delete' option, and the server is removed.
Validation is a process which checks the customization files for errors and inconsistencies. Start the validation process by selecting 'Validate' from the button bar or 'Tools' menu. The validation guide opens. Select the customization directories that require validation, and which types of data. Select 'Finish'. This closes the guide and opens a status window that displays the progress of the validation.
Errors If an error occurs during validation, some information about the error is displayed in the status window, together with an indication of where the error is, and what you need to do to fix it. Once this has been edited to fix the problem, the file can be saved, and the 'Continue' button can be selected from the status window to continue validation. This process might need to be repeated several times if a large number of files are being processed.
A workgroup is used in LANDP to describe a group of workstations that are connected together and share common resources. The workgroup parameter pane shows a list of all the workgroups currently loaded and all the workstations contained in the workgroups in the tree view. The workgroup properties editing pane is displayed when a workgroup icon is selected in the tree view.
Editing workgroups Workgroups contain workstations. The buttons on the button bar and 'Edit' menu allow addition of workstations. Workstations can be removed by selecting the workstation in the tree view, selecting the right mouse button to open the pop-up window and selecting 'Delete'. Workgroup properties can be edited from the workgroup properties window.
Adding workgroups Workgroups can be added from the workgroup parameters pane. Select the 'Add Workgroup Button' or select 'Add Workgroup' from the 'Edit' menu. See the tutorial section for more details on adding a workgroup.
Removing workgroups Workgroups can be removed from the current workgroup list. Select the workgroup from the workgroup list in the tree view, select the right mouse button and select 'Delete' from the pop-up menu.
The workgroup list contains all the workgroups currently loaded. These are displayed on the workgroup list window. To open an existing workgroup list, use the 'Open Workgroup List' option from the 'File' menu. To create a new workgroup list, select the 'New Workgroup List' option from the 'File' menu. To save a workgroup list click on the 'Save Workgroup List' option on the 'File' menu.
Workstations are the core objects in LANDP customization. A group of workstations constitutes a workgroup, and workstations can share services provided by other workstations using the client/server architecture.
Editing Workstations A workstation can be edited by selecting it from the list in the tree view of the workgroup parameters pane. The workstation parameters are displayed. Double-clicking on the icon in the tree view expands and collapses the list of clients and servers which are connected to the workstation. Clients and servers can be edited, removed or added from a workstation.
Adding Workstations Workstations can be added to a workgroup by clicking on the 'Add Workstation' button on the button bar. Selecting 'Add Workstation' from the 'Edit' menu has the same effect. For more information on adding workstations, see the tutorial section.
Removing Workstations Workstations can be removed from the current workgroup list. Select the workstation from the list in the tree view, select the right mouse button and select 'Delete' from the pop-up menu.
This part includes various appendixes, showing a hands-on example and providing detailed vector descriptions for user servers, common data, and configuration data.
To help you get a feeling for various LANDP configurations, some samples are provided on the LANDP CD-ROM. After installing LANDP, you will find them in path
...\EHCCUS\SAMPLEn\
This appendix describes SAMPLE1, which shows the steps to customize a basic workgroup of three workstations. It provides a guide through the customization process, with basic modifications to the configuration.
SAMPLE1 is located in path
...\EHCCUS\SAMPLE1\
If you wish to modify or test this example, or find out more information about how it was written and configured, please refer to the individual chapters of this manual.
SAMPLE1 shows all the steps and procedures needed to customize and obtain software for distribution to the work sites.
The example involves the following steps:
The workgroup in the example looks like this:
All workstations use SNA sessions to communicate with the host applications, and have the following requirements:
It contains the token-ring DLC server (TRDLC) and the SNA server (SNA##).
It uses two sessions of the SNA server in workstation AA, and receives services from the 3270 emulator.
It uses two sessions of the SNA server in workstation AA.
Because the example is a mixed workgroup with both DOS and OS/2 workstations, you must have LANDP for DOS and LANDP for OS/2 installed in your customization workstation.
Example 1 assumes that you have installed LANDP in directory C:\LANDP The common and models customization files will be put in subdirectory EHCCUS, which is created by the installation program. All procedures will be called from the same subdirectory: C:\LANDP\EHCCUS.
Some servers in your workgroup may need common data specifications. For a reference list of which vectors you have to specify, refer to Vectors - a quick reference. If you do not need to specify common vectors, go directly to Step 5. Editing workgroup vectors.
In the example, defaults are required at common level. Therefore, you will create the common data default definitions.
To create the default definitions, start from the EHCCUS subdirectory (C:\LANDP\EHCCUS) and enter the following command:
CREATE
The common data default definitions are created in the internal repository, and contain all the default values for your common data.
To generate the common vectors, enter:
GENSPEC COMMON
You may leave the default data and continue with defining workgroup vectors. If you want to see the data you have created, or want to make modifications to them, go to the next step.
You created the common data default definitions in Step 2. This also created a COMMON.SPC file in the EHCCUS subdirectory. This file can be edited by entering the following command from the same subdirectory:
EDITSPC COMMON
Your COMMON.SPC file is now open and you can start editing.
In the example, you want to add an additional key definition for the 3270 emulator keyboard table. The key definition will be: SCAN/ASCII 6D/00/END EMULATION.
To add the key definition, take the default KBD3270 vector (with keyword EXTEN=KBD) and add one keyword:
KEY=(6D,00,'END EMULATION')
When you have specified the common vectors, you can check that they are correct. To call the validation program, enter from the same EHCCUS subdirectory:
VALSPEC COMMON
The definitions of the COMMON.SPC file are validated, with a maximum allowed return code of 0.
If there are errors, attention items, or informative messages, the CUSPARM.LST file is created in the same subdirectory. This file contains the vectors and pointers to the messages or errors. Correct the data, and run the validation program again.
Once the common data definitions have been edited and validated, you can go on to define your workgroup specifications.
All the data for setting up workgroup definitions have to be defined for each workgroup customization.
The subdirectory where the workgroup definitions for this example will reside, is called SAMPLE1. Again, start from the EHCCUS subdirectory, and enter:
EDITSPC SAMPLE1 LAN
The LANCONF.SPC file is now open and ready to be edited. It is located in path C:\LANDP\EHCCUS\SAMPLE1.
If the path does not exist, or if you specify a different group and workgroup identification, the program asks if you want to create it. Enter Y, and the file LANCONF.SPC is created in the directory you specified.
All the vectors containing workgroup definitions for SAMPLE1 have to be written in this file. The LANCONF.SPC file is now open and you can start editing.
The workgroup vectors for the example are described below:
This is an example of a LANCONF vector, which specifies the configuration for the workgroup:
LANCONF GROUP=EHCCUS, NAME=SAMPLE1, WSNAMES=(AA,BB,CC)
After defining the LANCONF vector, the next step is to add the vectors for the individual workstation definitions.
This is the vector for workstation AA:
LWSCONF NAME=AA, TYPE=DOS, SERVER=(TRDLC), PAR&TKR=(48,04,04,00000001,00000099,017,00000), SERVER=(SNA##) PAR&SNA=(ANY,SRV)
The parameter values for this vector are:
Keyword | Parameter Values |
---|---|
NAME |
|
TYPE |
|
SERVER |
|
PAR&TKR |
|
SERVER |
|
PAR&SNA |
|
This is the vector for workstation BB:
LWSCONF NAME=BB, TYPE=DOS, CLIENT=(SNA01,AA), SES&SNA=(AA,01,31), CLIENT=(SNA02,AA), SES&SNA=(AA,02,32), SERVER=(EMU32701), PAR&3270;=(Y,N), SES&3270;=(AA,1,33,TKR,ATR,DIS,KBD,SESSION1)
The parameter values for this vector are:
Keyword | Parameter Values |
---|---|
NAME |
|
TYPE |
|
CLIENT |
|
SES&SNA |
|
CLIENT |
|
SES&SNA |
|
SERVER |
|
PAR&3270 |
|
SES&3270 |
|
This is the vector for workstation CC:
LWSCONF NAME=CC, TYPE=OS/2, CLIENT=(SNA01,AA), SES&SNA=(AA,01,11), CLIENT=(SNA02,AA), SES&SNA=(AA,02,12)
The parameter values for this vector are:
Keyword | Parameter Values |
---|---|
NAME |
|
TYPE |
|
CLIENT |
|
SES&SNA |
|
CLIENT |
|
SES&SNA |
|
You may wish to check whether the workgroup vectors are correct, especially if you have made any modifications to the example file. To call the validation program, from the same subdirectory enter:
VALSPEC LAN \SAMPLE1
The definitions of the LANCONF.SPC file for SAMPLE1 are validated, with a maximum allowed return code of 0.
If there are errors, attention items, or information messages, the CUSPARM.LST file is created in the same subdirectory. This file contains the vectors and pointers to the messages or errors. Correct the data, and run the validation program again.
When the workgroup data definitions have been edited and validated, you can go on to obtain the diskettes for distribution to your work sites.
Obtaining software for distribution is a two-stage process:
GENRUN LAN \SAMPLE1
The run-time files and a file containing a list of software required for each workstation (GETTING.SPC) have now been created. In the example, these files are created in path: C:\LANDP\EHCCUS\SAMPLE1\ws-name.
GETTING \SAMPLE1 WS=ALL 1 A:
This command copies all the configuration files for all workstations in SAMPLE1 to diskettes in drive A. Make sure you have a formatted disk inserted in drive A.
Each diskette produced in Step 7. Obtaining software for distribution contains the files for one workstation in the LANDP workgroup.
To distribute the software to a workstation in the workgroup, you need to take the appropriate diskette to the workstation, then copy the files to the workstation. For example, you might use the following commands:
MD C:\EHC XCOPY A:*.* C:\EHC
When the LANDP software is installed, and the necessary changes have been made to the CONFIG.SYS file, you can run LANDP using the AUTOFBSS command.
This section provides information about each user server vector.
Defines a user server and its corresponding characteristics. Define one DEFSERV vector for each server you are going to develop and use.
Vector Position | None |
List of keywords |
NAME, TYPE, SCOPE, DESCRIP, OBJECT, OBJPAR, SUBDIR, LOADER, LOADPAR,
PRIORITY, EXPMEM, INSTANCE, LANUNIQ, ALLCLI, FIRSTLVL, LASTLVL
|
Vector relates to | Second level vectors PREVLOAD, POSTLOAD, DEVICE, SVRREQS, and DISTRIB |
Vector format |
DEFSERV NAME=xxxxxxxx, [TYPE=xxxxxx,] [SCOPE=xxxxxx,] [DESCRIP=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx,] [OBJECT=xxxxxxxx.yyy,] [OBJPAR=' ',] [SUBDIR=xxxxxxxx,,] [LOADER=xxxxxx,,] [LOADPAR=' ',] [PRIORITY=x,] [EXPMEM=x,] [INSTANCE=1|N,] [LANUNIQ=Y|N,] [ALLCLI=Y|N,] [FIRSTLVL=F31|F11|L10|L20|L30|L40|L50|L60] [LASTLVL=F31|F11|L10|L20|L30|L40|L50|L60] |
NAME, TYPE, and SCOPE define the user server.
OBJECT and the other keywords up to and including EXPMEM specify parameters related to AUTOFBSS.BAT and AUTOFBSS.CMD.
The parameter value is a string of up to eight alphanumeric characters, starting with an alphabetical character. It must be unique among the server names.
The parameter value can be:
The default is DOS.
The parameter value can be:
The default is BOTH.
The parameter value is a string of up to 40 characters. It must be enclosed within quotes.
For DOS, OS/2, and Windows servers, the parameter has the following format:
xxxxxxxx.yyy
The name must be the name of the server, which you specified in the NAME keyword, and the extension can be:
The default is the server name specified in the NAME keyword, and the EXE extension.
For Linux servers, the parameter does not include a file extension. The name must be the name of the server that you specified in the NAME keyword.
The parameter value is a string of up to 40 characters, and the contents will appear in the loading statement in the same format as specified. It must be enclosed between quotes.
If &WSID appears in the string, it will be converted to workstation identification.
The parameter value is a string of up to eight characters. The defaults are:
If you specify EHCD, EHCO, EHCN, or EHCL for DOS type servers, OS/2 type servers, Windows type servers, or Linux type servers respectively, the customization program converts the values to those corresponding to the current release; for example, to the EHCD600 or EHCO600 values, if you are running LANDP for DOS or LANDP for OS/2.
It is not recommended that you specify these values or use these directories; instead, you should locate the user servers in a separate directory. Thus, the path of the user servers does not depend on the product release.
The parameter value can be:
The default is LOADER.
For Windows servers, the only parameter values supported are LOADER and NO. LOADER defaults to starting the server as a Windows service.
For Linux servers, the only parameter values supported are LOADER, NO, and START. START results in a statement being added to autofbss to start the server in a detached command shell. This will result in a statement of the form 'servername params&'.
For DOS servers, the parameter value LOADER will be changed to LOADERE, if overridden with other specifications.
The parameter value is a string of up to 40 characters. It must be enclosed between quotes.
The parameter value ranges from 1 to 9. The value 1 involves the highest priority; the value 9 involves the lowest priority. The default is 3.
All the loading statements with the same priority will be generated before the loading statements with lower priority. For example, all the statements with priority 1 will be processed before any statement with priority 2 is processed.
The parameter value can be Y or N. The default is N.
The parameter value can be:
The default is F11. If you omit the FIRSTLVL keyword, all levels of LANDP can run the server (unless qualified by the value specified in LASTLVL).
The parameter value can be:
The default is L60. If you omit the LASTLVL keyword, all levels of LANDP can run the server (unless qualified by the value specified in FIRSTLVL).
Defines a statement to be added to the CONFIG.SYS or CONFIG.ADD file, when the user server is selected for the corresponding workstation.
Define one DEVICE vector for each statement required by the server. The statements will be added in the order you define them.
Vector Position | Follows DEFSERV vector, or any of its second level vectors |
List of keywords | UNIQUEID, TEXT |
Vector relates to | None |
Vector format |
DEVICE [UNIQUEID=xxxxxxxx,] TEXT='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' |
The parameter value is a string of up to eight alphanumeric characters.
The parameter value is a string of up to 64 alphanumeric characters, and must be enclosed between quotes.
Specifies a file to be copied to the workstation where the user server is loaded.
Define one DISTRIB vector for each file to be copied. Server executable files and device drivers do not require DISTRIB vectors.
Vector Position | Follows DEFSERV vector, or any of its second level vectors |
List of keywords | FILENAME, SUBDIR, UNIQUEID, NEWNAME |
Vector relates to | LANCONF vector (LANGUAGE keyword) |
Vector format |
DISTRIB [FILENAME=xxxxxxxx.yyy,] [SUBDIR=xxxxxxxx,] [UNIQUEID=xxxxxxxx,] [NEWNAME=xxxxxxxx.yyy] |
The parameter has the following format:
xxxxxxxx.yyy
If the alphanumeric field contains the &NLS string, this string will be replaced by the parameter value assigned in the LANGUAGE keyword of the LANCONF value. You can specify &NLS as the extension, because once it is replaced by the language identifier, it will become a three-character string.
When the target workstation is of type Linux, this parameter can have the format:
xxxxxxxx
The parameter value is a string of up to eight characters. The defaults are:
The parameter value is a string of up to eight alphanumeric characters.
The parameter has the following format:
xxxxxxxx.yyy
When the target workstation is of type Linux, the file name and extension can be lower-case. The parameter can have the format:
xxxxxxxx
Specifies the parallel ports used by the user server. You can specify up to three ports.
Vector Position | Follows DEFSERV vector, or any of its second level vectors |
List of keywords | PORT1, PORT2, PORT3 |
Vector relates to | None |
Vector format |
PARPORT PORT1=xxxx, [PORT2=xxxx,] [PORT3=xxxx] |
The parameter value can be:
The parameter value can be:
It cannot be the same as the value specified in the PORT1 keyword.
The parameter value can be:
It cannot be the same as the value specified in the PORT1 or PORT2 keywords.
Defines statements that will be generated in the AUTOFBSS file, following the user server loading statement.
Vector Position | Follows DEFSERV vector, or any of its second level vectors |
List of keywords | UNIQUEID, CONDID, TEXT |
Vector relates to | None |
Vector format |
POSTLOAD [UNIQUEID=xxxxxxxx,] [CONDID=xxxxxxxx,] TEXT='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' |
The parameter value is a string of up to eight alphanumeric characters.
The parameter value is a string of up to eight alphanumeric characters, and must match a UNIQUEID keyword in another specified vector.
The parameter value is a string of up to 64 alphanumeric characters, and must be enclosed between quotes.
Defines statements that will be generated in the AUTOFBSS file, before the user server loading statement.
Vector Position | Follows DEFSERV vector, or any of its second level vectors |
List of keywords | UNIQUEID, CONDID, TEXT |
Vector relates to | None |
Vector format |
PREVLOAD [UNIQUEID=xxxxxxxx,] [CONDID=xxxxxxxx,] TEXT='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' |
The parameter value is a string of up to eight alphanumeric characters.
The parameter value is a string of up to eight alphanumeric characters, and must match a UNIQUEID keyword in another specified vector.
The parameter value is a string of up to 64 alphanumeric characters, and must be enclosed between quotes.
Specifies LANDP prerequisite server for the user server.
Define one SVRREQS vector for each prerequisite to be specified.
Vector Position | Follows DEFSERV vector, or any of its second level vectors |
List of keywords | COND, TYPE, SVRNAME |
Vector relates to | None |
Vector format |
SVRREQS [COND=x,] [TYPE=x,] SVRNAME=xxxxxxxx |
The parameter value can be:
The default is S.
The parameter value can be:
The default is C.
The parameter value is a string of up to eight alphanumeric characters.
/* Vector DEFSERV USERSVR1 server definition */ DEFSERV NAME=USERSVR1, OBJECT=USERSVR1.EXE, OBJPAR='/TBL /&WSID', LOADPAR='/w:e /&:e', EXPMEM=Y DEVICE UNIQUEID=ID1, TEXT='DEVICE=DRIVER1.SYS /a /b /c' DEVICE UNIQUEID=ID2, TEXT='DEVICE=DRIVER2.SYS /a /b /c' DISTRIB FILENAME=PGM.EXE, UNIQUEID=ID3, NEWNAME=USERPGM.EXE DISTRIB FILENAME=FILE002.&NLS, UNIQUEID=ID4, NEWNAME=FILE.MSG PARPORT PORT1=LPT1 POSTLOAD UNIQUEID=ID5, TEXT='echo on Server loaded successfully' PREVLOAD UNIQUEID=ID6, TEXT='USERPGM.EXE /1' SVRREQS SVRNAME=SNA## /* Vector DEFSERV. USERSVR2 server definition */ DEFSERV NAME=USERSVR2, PRIORITY=4, OBJECT=USERSVR2.EXE, OBJPAR=('/123'), LOADPAR='/&:e' DEVICE UNIQUEID=ID1, TEXT='DEVICE=DRIVER1.SYS /a /b /c' POSTLOAD TEXT='echo on Server loaded successfully' PREVLOAD UNIQUEID=ID7, CONDID=ID1, TEXT='Pause Please, check the printer' PREVLOAD UNIQUEID=ID8, CONDID=ID9, TEXT='Pause Please, Power off the printer'
For the example server definitions, the CONFIG.SYS file contains the following statements:
DEVICE=DRIVER1.SYS /a /b /c DEVICE=DRIVER2.SYS /a /b /c
For the example server definitions, the AUTOFBSS.BAT file contains the following statements (assuming ws = AA)
Pause Please check the printer LOADER /&:e USERSVR2.EXE /123 echo on Server loaded successfully USERPGM.EXE /1 LOADERE /w:e /&:e USERSVR1.EXE /TBL /AA echo on Server loaded successfully
In addition, the file FILE.MSG will be in the distribution diskette.
|
This appendix provides information about data that is common for all or for
several workstations or workgroups. This is called common data, and is
specified and stored in vector format in the COMMON.SPC file, located
in the EHCCUS directory.
Common vectors contain defaults, tables, record definitions, and profiles. They also contain definitions for user servers. Data for user servers is stored and processed together with other common data in the COMMON.SPC file. For information on how to define user servers, refer to Appendix B, User servers. For information on how to store customization data in specification files,
refer to Customization data structure, especially if you plan to use embedded files
(see page "Embedded specification files") or partial files (see page "Partial specification files").
|
Before you start creating and editing common vectors, consider the following:
The EDITSPC program is used to edit specification files.
You can apply this procedure to the COMMON.SPC file, and display and modify the common vectors.
If you want to display online information about this procedure, from the EHCCUS directory, enter:
EDITSPC ?
To start the procedure, from the EHCCUS directory, enter:
EDITSPC COMMON
If you use the OS/2 Enhanced Editor with the LANDP customization editing tool, the LANDP choice is listed in the action bar of the editor window. For information about that tool, select the View doc option in the pull-down that appears when you choose LANDP.
The EDITSPC program is included here only for compatibility with previous LANDP releases. The same function can be achieved by using the new graphical Customization Editor which, in addition to being easier to use, also provides improved functionality.
The graphical Customization Editor allows you to edit specification files. See Graphical Customization Editor for more information.
The graphical Customization editor can also be used to invoke the CREATE and GENSPEC procedures that are described in the following paragraphs.
The default common data is created in the internal repository. If the COMMON.SPC file already exists, the procedure also processes that file.
To start the procedure, from the EHCCUS directory, enter:
CREATE
The common vectors are generated in the COMMON.SPC file, located in the EHCCUS directory. The order in which the vectors appear in the file is not relevant.
To start the procedure, from the EHCCUS directory, enter:
GENSPEC COMMON
For further information on that procedure, refer to Generating data.
Common vectors contain the following information.
User servers are part of common data. They must be created and
processed in the COMMON.SPC file. If you want to define and add
your own user servers, refer to Appendix B, User servers.
Vector Name | Defines: | Is valid for: | Go to page: |
---|---|---|---|
BPPPARM | Optional identifications for printer device parameters | Banking printer program server | "BPPPARM vector" |
COLSQTBL | Alternate Collating Sequence Table | Shared-file server | "COLSQTBL vector" |
DEFAULTS | Hotkeys and session identifications | 3270 emulator, 3287 Printer Emulator, Banking Printer Program | "DEFAULTS vector" |
DISPLATT | Display attribute tables | 3270 Emulator, Banking Interactive Workstation Program | "DISPLATT vector" |
EJOUPRF | Electronic journal profile | Electronic journal server | "EJOUPRF vector" |
EJOUREC | Record names to be used as electronic journal records | Electronic journal server | "EJOUREC vector" |
FORM4710 | 4710 printer device parameters (document and journal formats) | Banking printer program server | "FORM4710 vector" |
FORM4720 | 4720 printer device parameters (document, journal, passbook, and REMS formats) | Banking printer program server | "FORM4720 vector" |
FORM47X2 | Financial printer device parameters (document, journal, passbook, and REMS formats) | Financial printer server | "FORM47X2 vector" |
FORM4748 | 4748 printer device parameters (document and passbook formats) | 4748 printer server | "FORM4748 vector" |
FORM4770 | 4770 printer device parameters (document and journal formats) | 4770 printer server | "FORM4770 vector" |
FORWDS | Forwarding data set inside a forwarding profile | Forwarding server | "FORWDS vector" |
FORWPRF | Forwarding profile | Forwarding server | "FORWPRF vector" |
KBD3270 | Keyboard table definitions | 3270 Emulator | "KBD3270 vector" |
KBD3270X | Extended keyboard table definitions | 3270 Emulator | "KBD3270X vector" |
KBDBIWP | Keyboard table definitions | Banking Interactive Workstation Program | "KBDBIWP vector" |
KSCCBIWP | Scan code translation table | Banking Interactive Workstation Program | "KSCCBIWP vector" |
KSTRBIWP | Key stroke translation table | Banking Interactive Workstation Program | "KSTRBIWP vector" |
LUPOOL | LUs and LU logical groups | SNA server and functional areas that use SNA services | "LUPOOL vector" |
MSRINTBL | MSR/E input conversion table | Banking Interactive Workstation Program for MSR/E server | "MSRINTBL vector" |
MSROUTBL | MSR/E output conversion table | Banking Interactive Workstation Program for MSR/E server | "MSROUTBL vector" |
P3287ATT | Time-out and common parameters | 3287 printer emulator | "P3287ATT vector" |
PINPTBL | PIN pad conversion table | Banking Interactive Workstation Program for PIN pad server | "PINPTBL vector" |
RCMSLNF | RCMS logical names file | RCMS server | "RCMSLNF vector" |
RECDEF | Record definitions | Electronic journal server, Store-for-forwarding server, Shared-file server, System manager server | "RECDEF vector" |
RECFIELD | Field definitions inside a record definition | Electronic journal server, Store-for-forwarding server, Shared-file server, System manager server | "RECFIELD vector" |
SFORWPRF | Store-for-forwarding profile | Store-for-forwarding server | "SFORWPRF vector" |
SFORWREC | Record names to be used as store-for-forwarding records | Store-for-forwarding server | "SFORWREC vector" |
SHFLDBD | Shared-file database description (DBD) inside a shared-file profile | Shared-file server | "SHFLDBD vector" |
SHFLPCB | Program control block (PCB) to access the previously defined DBDs | Shared-file server | "SHFLPCB vector" |
SHFLSGM | Segmented keys | Shared-file server | "SHFLSGM vector" |
SMGRPRF | System manager profile | System manager server | "SMGRPRF vector" |
SMGRUSER | System manager user profile | System manager server | "SMGRUSER vector" |
SOFTPACK | Non-LANDP files to be distributed with the GETTING utility | Not applicable | "SOFTPACK vector" |
XLAT2TBL | ASCII/EBCDIC and EBCDIC to ASCII translation tables | Applications using XLATE | "XLAT2TBL vector" |
XLATETBL | Translation tables | 3270 emulator, 3287 printer emulator, Banking Interactive Workstation Program, Remote Change Management Services, Forwarding server | "XLATETBL vector" |
X25DIR | X.25 directory tables | SNA server | "X25DIR vector" |
This section provides information about each common vector, including examples.
The products for which the vectors apply are shown in boxes at the beginning of each vector description. These include PC/Integrator and PC Integrator/2 where FBSS data is involved.
Defines DEVPARM defaults used by the banker printing program.
This vector is optional. If it is not specified, a default vector will be created. It can only be specified once.
For examples of default (DUMMY*) FORM4710, FORM4720, and FORM47X2 vectors, see the respective vector sections.
Vector position | None |
List of keywords | PAR4710, PAR4720, PAR4712, PAR4722, CHSTRID |
Keywords relate to |
|
Vector format |
BPPPARM [PAR4710=xxxxxxxx,] [PAR4720=xxxxxxxx,] [PAR4712=xxxxxxxx,] [PAR4722=xxxxxxxx,] [CHSTRID=( ),] [CHSTRID=( )] |
The parameter value is string of up to eight alphanumeric characters. The default is DUMMYDOC.
The parameter value is a string of up to eight alphanumeric characters. The default is DUMMYDOC.
The parameter value is a string of up to eight alphanumeric characters. The default is DUMMYJOU.
The parameter value is a string of up to eight alphanumeric characters. The default is DUMMYDOC.
You can specify one keyword for each character string table you want to define.
The keyword has two parameters:
/* Vector BPPPARM Default Example */ BPPPARM PAR4710=DUMMYDOC, PAR4720=DUMMYDOC, PAR4712=DUMMYJOU, PAR4722=DUMMYDOC, CHSTRID=(017,11)
Defines an alternate collating sequence table for the shared-file server.
Define one COLSQTBL vector for each alternate collating sequence table you want to use in your workgroups. If this vector is not specified, a default vector will be created.
Vector position | None |
List of keywords | NAME, SUBEXT, DATA0X to DATAFX |
Keywords relate to |
|
Vector format |
COLSQTBL NAME=xxxxxxxx, [SUBEXT=x,] DATA0X=( ), DATA1X=( ), : DATAFX=( ) |
The parameter value is a string of up to eight characters, which must adhere to DOS specifications for file names. It must be unique among all COLSQTBL vectors.
The parameter value can be any hexadecimal character, except for 0. The default is Q.
The extension becomes SEx, where x is the specified value. Thus, the default extension is SEQ.
When working under OS/2, only the alternate collating sequence table with extension SEQ can be substituted by the Default Country Collating Table.
DATA0X must contain the alternate collating sequence characters corresponding to ASCII characters '00' to '0F', DATA1X to ASCII '10' to '1F', and so on.
/* Vector COLSQTBL Default Example */ COLSQTBL NAME=CONFIGUR, SUBEXT=1, DATA0X=(00,01,02,03,04,05,06,07,08,09,0A,0B,0C,0D,0E,0F), DATA1X=(10,11,12,13,14,15,16,17,18,19,1A,1B,1C,1D,1E,1F), DATA2X=(20,21,22,23,24,25,26,27,28,29,2A,2B,2C,2D,2E,2F), DATA3X=(30,31,32,33,34,35,36,37,38,39,3A,3B,3C,3D,3E,3F), DATA4X=(40,41,42,43,44,45,46,47,48,49,4A,4B,4C,4D,4E,4F), DATA5X=(50,51,52,53,54,55,56,57,58,59,5A,5B,5C,5D,5E,5F), DATA6X=(60,61,62,63,64,65,66,67,68,69,6A,6B,6C,6D,6E,6F), DATA7X=(70,71,72,73,74,75,76,77,78,79,7A,7B,7C,7D,7E,7F), DATA8X=(80,81,82,83,84,85,86,87,88,89,8A,8B,8C,8D,8E,8F), DATA9X=(90,91,92,93,94,95,96,97,98,99,9A,9B,9C,9D,9E,9F), DATAAX=(A0,A1,A2,A3,A4,A5,A6,A7,A8,A9,AA,AB,AC,AD,AE,AF), DATABX=(B0,B1,B2,B3,B4,B5,B6,B7,B8,B9,BA,BB,BC,BD,BE,BF), DATACX=(C0,C1,C2,C3,C4,C5,C6,C7,C8,C9,CA,CB,CC,CD,CE,CF), DATADX=(D0,D1,D2,D3,D4,D5,D6,D7,D8,D9,DA,DB,DC,DD,DE,DF), DATAEX=(E0,E1,E2,E3,E4,E5,E6,E7,E8,E9,EA,EB,EC,ED,EE,EF), DATAFX=(F0,F1,F2,F3,F4,F5,F6,F7,F8,F9,FA,FB,FC,FD,FE,FF)
Defines required parameters for the supervisor and emulators.
Define as many DEFAULTS vectors as are required in your installation. If this vector is omitted, a default vector will be created.
The DEFAULTS vectors will be referenced on workgroup level in the keyword DEFAULTS of the LANMODEL or LANCONF vectors.
The parameters that you define in the DEFAULTS vector are:
There is a help facility for calling the scan and ASCII codes for each key on your keyboard. From the EHCCUS subdirectory, enter:
EHCSC
and you will get an interactive help panel where you can enter any key to find out the specified values.
For the hotkeys you define the scan code of the key that, when pressed with the Alt key, will transfer control to the corresponding LANDP for DOS server.
The following scan codes cannot be chosen:
If you define a scan code of 00, the corresponding hotkey will not be defined.
Vector position | None |
List of keywords | NAME, DEBUGHK, OPERHK, SMOPHK, TMR0SCC, TMR0ASC, TIMEOUT, E3270HK1 to E3270HK5, E3287SI1 to E3287SI5, BPPSI1 to BPPSI4, DBCSCTRY, DBCSPATH, PROCNAME |
Keywords relate to |
|
Vector format |
DEFAULTS [NAME=xxxxxxxx,] [DEBUGHK=xx,] [OPERHK=xx,] [SMOPHK=xx,] [TMR0SCC=xx,] [TMR0ASC=xx,] [TIMEOUT=xxxx,] [E3270HK1=( ),] [E3270HK2=( ),] [E3270HK3=( ),] [E3270HK4=( ),] [E3270HK5=( ),] [E3287SI1=xxxxxxxx,] [E3287SI2=xxxxxxxx,] [E3287SI3=xxxxxxxx,] [E3287SI4=xxxxxxxx,] [E3287SI5=xxxxxxxx,] [BPPSI1=xxxxxxxx,] [BPPSI2=xxxxxxxx,] [BPPSI3=xxxxxxxx,] [BPPSI4=xxxxxxxx,] [DBCSCTRY=( ),] [DBCSPATH=path,] [PROCNAME=xxxxxxxx] |
The parameter value is a field with up to eight alphanumeric characters, and must be unique among the DEFAULTS vectors defined. The default is GENERAL.
The parameter value is a 1-byte field. The default is 45 (NumLock).
The parameter value is a 1-byte field. The default is 44 (F10).
The parameter value is a 1-byte field. The default is 3E (F4).
LANDP for OS/2: The keyword can be set to any extended ASCII character.
LANDP for Windows: The keyword can be set to the extended ASCII characters Alt F1-F10 and Ctrl F1-F10.
The parameter value is a 1-byte field. The default is 01 (Esc), which is returned when timer 0 elapses if TMR0SCC is not coded or is set to a value other than those specified above.
The parameter value is a 1-byte field. The default is 1B (Esc).
The parameter value is a field with up to four digits, and can range from 1 to 3600. The default is 30 seconds.
A maximum of five 3270 emulator programs can be installed in one workstation.
Each keyword has two parameters in the format (xx,yyyyyyyy), where:
By default, the host/application identification is blank.
The defaults for the respective scan codes (examples, page ***) are:
Multiple Emulators | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The hotkeys can be defined so that the workstation operator activates the
next successive emulator as the previous one is ended. This is referred
to as chaining emulators.To chain four emulators so that the
next emulator is activated when the preceding emulator is ended, ensure that
the hotkey to enter an emulator is the same as at least one of the the hotkeys
used to exit the emulator. Exit hotkeys are defined in the KBD3270
vector.
Table 7. Chained Emulators: Example 1
The first time ALT+F2 is pressed, Emulator 1 is activated:
Pressing ALT+F10 exits the emulation mode. Notice that if ALT+F2 is pressed when the workstation is not in emulation mode, Emulator 1 is always activated. Using this configuration, it is not possible to directly activate any emulator other than Emulator 1 when the workstation is not in emulation mode. To be able to activate a specific emulator, define a unique entry hotkey
for each emulator.
Table 8. Chained Emulators: Example 2
Whether the workstation is in emulation mode or not:
Pressing ALT+F10 exits the emulation mode. |
A maximum of five 3287 printer emulator sessions can be installed in one workstation. Define the sessions you need in any order.
The parameter value is a field of up to eight alphanumeric characters. By default, all five host/application identifications are blank.
A maximum of four banking printer programs can be installed in one workstation for LANDP for DOS, three for LANDP for OS/2, and one for LANDP for Windows (supported in the DOS-box). Define the sessions you need in any order.
The parameter value is a field of up to eight alphanumeric characters. By default, all four programs are blank.
The parameter value can be:
The default is NO.
The keyword has two parameters in the format (xxx,yyyy), where:
If Korea (082) is specified, a second subparameter must also be specified designating the code page used in the LANDP workgroup. The supported code page is 949.
If People's Republic of China (086) is specified, a second subparameter must also be specified designating the code page used in the LANDP workgroup. The supported code pages are 1381 and 1386. For Linux workstations, for Linux codeset GBK, you should specify 1386.
If Taiwan (088) is specified, a second subparameter must also be specified. In this case, the supported code pages are 938 and 950. For example to specify Taiwan as the DBCSCTRY using code page 950, you would specify:
DBCSCTRY=(088,950)
For Linux workstations, for Linux codeset BIG5, you should specify 950.
Additionally, for People's Republic of China (086), a third subparameter may be specified designating the code page of the host computer. The supported code pages are 935 and 1388. For example, to specify PRC as the DBCSCTRY using LANDP workgroup code page 1386 and host code page 1388, you would specify
DBCSCTRY=(086,1386,1388)
The parameter value is a string of up to 30 alphanumeric characters. The format must be:
d:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path. The default is C:\.
The parameter value is a field with up to eight alphanumeric characters. The default is AUTOFBSS.
/* Vector DEFAULTS Default Example */ DEFAULTS NAME=GENERAL, DEBUGHK=45, OPERHK=44, SMOPHK=3E, TMR0SCC=01, TMR0ASC=1B, TIMEOUT=30, E3270HK1=(3F), E3270HK2=(40), E3270HK3=(41), E3270HK4=(42), E3270HK5=(43)
Defines color display attribute tables for the 3270 emulator or the banking interactive workstation program. These are the colors that you want to appear on your workstation display for each field attribute. You may want to assign a different color set for each 3270 or banking interactive workstation program in a workstation.
Specify one vector for each table you want to use in your workgroups.
Table 9 shows the display colors that can be used.
Color code | Color |
---|---|
0 | Black |
1 | Blue |
2 | Green |
3 | Cyan |
4 | Red |
5 | Magenta |
6 | Brown |
7 | Light Grey |
8 | Dark Grey |
9 | Light Blue |
A | Light Green |
B | Light Cyan |
C | Light Red |
D | Light Magenta |
E | Yellow |
F | White |
Vector position | None |
List of keywords | TYPE, EXTEN, DEFCOLRS, BACKGRD, HIGHPROT, NORMPROT, HIGHUNPR, NORMUNPR, STATUS, BLUE, RED, PINK, GREEN, TURQUOIS, YELLOW, WHITE, HIGHDFLT, NORMDFLT |
Keywords relate to |
|
Vector format |
DISPLATT TYPE=xxxx, EXTEN=xxx, [DEFCOLRS=xxxxx,] [BACKGRD=x,] [HIGHPROT=x,] [NORMPROT=x,] [HIGHUNPR=x,] [NORMUNPR=x,] [BLUE=x,] [RED=x,] [PINK=x,] [GREEN=x,] [TURQUOIS=x,] [YELLOW=x,] [WHITE=x,] [HIGHDFLT=x,] [NORMDFLT=x,] [STATUS=xx] |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all DISPLATT vectors.
The attribute values for the three default color schemes are as follows:
Keyword DEFCOLRS=MONO DEFCOLRS=DARK DEFCOLRS=LIGHT ------- ------------- ------------- ------------- BACKGRD 0 (Black) 0 (Black) 0 (Black) HIGHPROT F (White) 7 (Light grey) F (White) NORMPROT 7 (Light grey) 1 (Dark blue) 9 (Light blue) HIGHUNPR F (White) 4 (Dark red) C (Light red) NORMUNPR 7 (Light grey) 2 (Dark green) A (Light green) STATUS 7 (Light grey) 2 (Dark green) A (Light green) (background) STATUS 0 (Black) 0 (Black) 0 (Black) (foreground) BLUE 7 (Light grey) 1 (Dark blue) 9 (Light blue) RED 7 (Light grey) 4 (Dark red) C (Light red) PINK F (White) 5 (Dark magenta) D (Light magenta) GREEN 7 (Light grey) 2 (Dark green) A (Light green) TURQUOIS F (White) 3 (Dark cyan) B (Light cyan) YELLOW F (White) 6 (Brown) E (Yellow) WHITE F (White) 7 (Light grey) F (White) HIGHDFLT F (White) 7 (Light grey) F (White) NORMDFLT 7 (Light grey) 2 (Dark green) A (Light green)
If you have changed your BACKGRD color to white or light grey, you will receive message EHC02204 to tell you that the background and foreground colors for the attribute you have chosen should not be the same (because that data will not be visible). You can ignore this message if you do not intend to use extended color on this display.
If you want to use extended color, you should specify DEFCOLRS=DARK or DEFCOLRS=LIGHT and then specify any variations from the default scheme that you want.
If you do not want to use extended color, you might want to do this anyway, to suppress the messages.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter value is a 1-hexadecimal digit. The default is the value derived from the DEFCOLRS keyword.
The parameter is a value of two digits, with the first one specifying the background, and the second one the foreground color.
The parameter value is a 2-hexadecimal digit. The default is the values derived from the DEFCOLRS keyword.
The keyword does not apply to DBCS mode. When working in DBCS mode, the value used by the 3270 emulator is 07, which is black foreground on a light grey background.
/* Vector DISPLATT (TYPE=3270): Example */ DISPLATT TYPE=3270, EXTEN=ATR, DEFCOLRS=LIGHT, BLUE=3 /* Change blue to dark cyan */
Defines an electronic journal server profile. Define one EJOUPRF vector for each electronic journal profile you want to specify.
This vector must be followed by as many EJOUREC vectors as different records will be used in this electronic journal profile.
You can choose among two electronic journal server environments: physical or logical. In the physical environment, each file is accessed through a physical journal name that is assigned by the application. In the logical environment, you can have up to 99 logical journals that the application can access by name within each physical journal.
Vector position | None. Is followed by at least one EJOUREC vector. |
List of keywords | NAME, DATASETS, MAXNUML, SEPSESS, MAXACC, SHFLPRF, DBDPATH, DBDPATH6, SPLIT, KEY02 to KEY15 |
Keywords relate to |
|
Vector format |
EJOUPRF NAME=xxxxxxxx, [DATASETS=xx,] [MAXNUML=xx,] [SEPSESS=x,] [MAXACC=xxxxx,] SHFLPRF=xxxxxxxx, DBDPATH=path, DBDPATH6=path, SPLIT=length, [KEY02=xxxxxxxx,] : [KEY15=xxxxxxxx] |
The parameter value is a field of up to eight alphanumeric characters plus the special characters $, %, #, and @. It must be unique among all EJOUPRF vectors.
The parameter value is a field with up to two numeric characters, ranging from 1 to 70. The default is 3.
The parameter value is a field with up to two numeric characters, ranging from 0 to 99. The default is 0. When you select 0, only the physical journal environment is used.
Specify Y (Yes) if you want session integrity to be handled by the electronic journal server, independently of your own shared-file session. The default is N (No).
The parameter value is a field with up to five numeric characters and it can range from 1 to 32767. The default is 200.
You can use the name of a shared-file profile already defined in the keyword SHFLPRF of the SHFLDBD vector, or a new name. If you provide a new profile name, the corresponding shared-file profile will be created by the customization program.
In any case, the customization will add the DBD and PCB definitions required for this electronic journal profile to the shared-file profile.
The same shared-file profile can only be used by one electronic journal profile.
If you use the electronic journal server and the store-for-forwarding in the same workstation, you must use the same shared-file profile for both of them.
The parameter value is a field with up to eight alphanumeric characters. It must be unique among the EJOUPRF vectors.
The parameter value is the complete path (drive plus subdirectories). The number of subdirectories must not exceed four, and has to end with a back slash (\). It must at least contain three characters.
The parameter value is the complete path including the subdirectories. It must not exceed 56 characters, and must be enclosed within single quotes ('). Each subdirectory name included in the path must have one character at least, and 30 characters at most. A backslash ('\') must not be present after the last subdirectory name.
As with the DBDPATH keyword, the path must exist prior to running the LANDP family programs in a workstation with the shared file server.
Parameter values range from 62 to 4096 minus the size of the header that is appended. The header is the length of all the defined keys (including the electronic journal hidden key EJHIDKEY which is 8 bytes long) plus 36.
Fields in a record can be selected as electronic journal keys only if they are in character, unsigned ASCII numeric, or hexadecimal, and their length is fixed and less than 50 bytes.
If fields specified as keys are defined in more than one record, the characteristics of the field must match.
The keys must be specified sequentially; for example, KEY05 cannot be specified if KEY04 was omitted. The first key (KEY01) is not defined because it is the electronic journal hidden key.
/* Vectors EJOUPRF and EJOUREC Examples */ EJOUPRF NAME=EJPRF01, DATASETS=10, MAXNUML=5, SEPSESS=N, MAXACC=200, SHFLPRF=SFPROF01, DBDPATH=C:\TELLER\EJOU\, SPLIT=1024, KEY02=REC1FL01, KEY03=REC2FL03, KEY04=REC1FL02, KEY05=REC2FL01 EJOUREC RECNAME=RECORD01
Defines the names of the record structures defined with the RECDEF vector which will be used as electronic journal records.
At least one EJOUREC vector must be specified following an EJOUPRF vector.
Vector position | Follows EJOUPRF vector |
List of keywords | RECNAME |
Keywords relate to |
|
Vector format |
EJOUREC RECNAME=xxxxxxxx |
The parameter value is a field with up to eight alphanumeric characters, and must match the name given in keyword NAME of a RECDEF vector. Records that have fields with names AND or OR cannot be used as electronic journal records.
/* Vectors EJOUPRF and EJOUREC Examples */ EJOUPRF NAME=EJPRF01, DATASETS=10, MAXNUML=5, SEPSESS=N, MAXACC=200, SHFLPRF=SFPROF01, DBDPATH=C:\TELLER\EJOU\, SPLIT=1024, KEY02=REC1FL01, KEY03=REC2FL03, KEY04=REC1FL02, KEY05=REC2FL01 EJOUREC RECNAME=RECORD01
Defines default parameters (DEVPARM) for banking printer program when emulating a 4710 printer.
The following figure shows the layout of the document pages for a 4710 printer:
Figure 18. Document dimensions for IBM 4710 printer customization
Vector position | None |
List of keywords | See keyword TYPE |
Keywords relate to |
|
Vector format |
FORM4710 TYPE=xxxx, NAME=xxxxxxxx, [AUTONL=x,] [CPI=xx,] [LINELEN=xx,] [VRTOFFSL=x,] [PAGESIZE=x,] [STARTKEY=x,] [WRNLINE=x] |
Depending on the type you selected, you define a different set of keywords:
The default is Y.
The default is the maximum value for the CPI specified.
The value specified for VRTOFFSL plus the one for PAGESIZE must not be greater than 4. If WRNLINE is greater than 0, VRTOFFSL must not be greater than WRNLINE. The default is 0.
Permits the journal to be split up in logical pages by defining the number of print lines per page. When the end of the page is reached, the application receives a message and the journal is placed in line 1, column 1 of the next page. Allowed values are 0 to 63. Value 0 means continuous listing. The default is 0.
Allowed values are 1 to 4. The default is 4.
The default is N.
Notes:
/* Vector FORM4710 (Journal) Example */ FORM4710 TYPE=JOUR, NAME=JOURNAL1, CPI=10, LINELEN=40, PAGESIZE=60, WRNLINE=58 /* Vector FORM4710 (Document) Defaults Example */ FORM4710 TYPE=DOCU, NAME=DUMMYDOC, PAGESIZE=1, WRNLINE=0, LINELEN=40, CPI=10, VRTOFFSL=4, AUTONL=Y, STARTKEY=Y
Defines default parameters (DEVPARM) for banker printing program when emulating a 4720 printer.
The following figure shows the layout of the passbook pages for a 4720 printer:
Figure 19. Passbook Dimensions for IBM 4720 Printer Customization
Vector position | None |
List of keywords | See keyword TYPE |
Keywords relate to |
|
Vector format |
FORM4720 TYPE=xxxx, NAME=xxxxxxxx, [AUTONL=x,] [BKWIDTH=xxx,] [CPI=xx,] [DISPLACE=x,] [DBLREC=x,] [FOLDBEG=xx,] [FOLDSKIP=x,] [FOLDTYPE=x,] [HRZOFFS=x,] [JOURADV=x,] [LINELEN=xx,] [LPI=x,] [MAXSKEW=x,] [REMSMODE=x,] [NEWDOC=x,] [VRTOFFSL=x,] [VRTOFFSS=x,] [PAGESIZE=xx,] [QUALITY=x,] [STARTKEY=x,] [WRNLINE=x] |
Depending on the type you selected, you define a different set of keywords:
Use the keywords only with their corresponding types. Otherwise, you will get an error.
The default is Y.
Allowed values are 10, 12, or 16. The default is 10.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is Y.
For horizontal fold passbooks, the maximum value must not be greater than the specified PAGESIZE value.
For vertical fold passbooks, the maximum value must not be greater than the specified LINELEN value.
For both types of center fold, the default is 10.
The center fold skip can be any value provided that, when added to the page size (PAGESIZE for horizontal fold passbooks) or to the line length (LINELEN for vertical fold passbooks), the sum is less than or equal to the maximum logical page size or the maximum printer line length respectively.
For vertical passbooks, the default is 4.
The maximum values depend on the value defined for character density CPI. They are:
If 0 is specified, the maximum value is assumed. The default is 80.
The parameter values are 5 or 6 lines per inch. The default is 5.
The parameter values are:
The default is 1.
The default is N.
The maximum number of lines depends on the line density (LPI) chosen and, in horizontal fold passbooks, the center fold skip.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed.
Maximum values are:
If 0 is specified, the maximum value is assumed. The default is 60.
If 0 is specified, no end of page checking is performed, and the journal is treated as a continuous list. The default is 0.
If 0 is specified, the maximum value is assumed. The default is 0.
The parameter value can be either Y (Yes) or N (No). The default is N.
The default is D.
The default is N.
(See dimension 'C' in Figure 19.)
The value specified for VRTOFFSL plus the values for PAGESIZE and VRTOFFSS (and FOLDSKIP for horizontal passbook) must not be greater than the maximum page size.
The default is 0.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed.
Maximum values are:
The default is 0.
Notes:
/* Vector FORM4720 (Passbook) Example */ FORM4720 TYPE=PASS, NAME=PASS001, LPI=5, CPI=10, MAXSKEW=1, FOLDTYPE=V, LINELEN=70, PAGESIZE=38, FOLDBEG=30, FOLDSKIP=1, VRTOFFSS=0, VRTOFFSL=0, HRZOFFS=10, AUTONL=Y, STARTKEY=N
/* Vector FORM4720 (Document) Default Example */ FORM4720 TYPE=DOCU, NAME=DUMMYDOC, PAGESIZE=1, WRNLINE=0, LINELEN=82, STARTKEY=Y, AUTONL=Y, LPI=5, CPI=10, VRTOFFSL=0, VRTOFFSS=0, JOURADV=N, QUALITY=N
Defines financial printer device parameters for documents, journals, passbooks, and REMS objects.
Define one FORM47X2 vector for each financial printer object you want to use in your workgroups (documents, journals, passbooks, or REMS).
The following figure shows the layout of the 4772 and 9068 passbook pages:
Figure 20. Passbook Dimensions for IBM 4772 and 9068 Printer Customization
The following figure shows the layout of the document pages:
Figure 21. Document Dimensions for IBM 4009, 4712, 4722, 4772, 9068 and 9069 Printer Customization
Vector position | None |
List of keywords | See keyword TYPE |
Keywords relate to |
|
Vector format |
FORM47X2 TYPE=xxxx, NAME=xxxxxxxx, [AUTONL=x,] [BKWIDTH=xxx,] [BOTTVAL=xxx,] [CPI=xx,] [DBLLINE=x,] [DBLREC=x,] [DBLSTRK=x,] [DISPLACE=x,] [EMPHASIZ=x,] [FOLDBEG=xx,] [FOLDSKIP=x,] [FOLDTYPE=x,] [HIGHCHR=x,] [HRZOFFS=x,] [LINELEN=xx,] [LPI=x,] [MAXSKEW=x,] [NEWDOC=x,] [PAGESIZE=xx,] [QUALITY=x,] [REMSMODE=x,] [SHARED=x,] [STARTKEY=x,] [VRTOFFSI=x,] [VRTOFFSL=x,] [VRTOFFSS=x,] [WIDECHR=x,] [WRNLINE=x] |
Use the keywords only with their corresponding types. Otherwise, you will get an error.
The default is Y.
The maximum size for the printable area of a document to be checked is 2 inches.
The default is OFF.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter applies only to the 4772 printer. The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is Y.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
For horizontal fold passbooks, the minimum value is 1, and the maximum must not be greater than the specified PAGESIZE value.
For vertical fold passbooks, the minimum value is 1, and the maximum must not be greater than the specified LINELEN value.
If 0 is specified, the fold skip is considered to be in the page center for horizontal fold passbooks, and in the line center for vertical fold passbooks. The default is 10.
The center fold skip can be any value such that, when added to the page size (PAGESIZE for horizontal fold passbooks) or to the line length (LINELEN for vertical fold passbooks), the sum is less than or equal to the maximum logical page size or the maximum printer line length respectively.
The default is 4.
The parameter applies only to the 4772 printer, and when double line feed is selected through the DBLLINE keyword. The parameter value can be either Y (Yes) or N (No). The default is N.
The value, when added to the line length and center fold skip in a vertical fold passbook, must be less than or equal to the maximum line length. The default for PASS type objects is 0, and for DOCU type objects 1.
See parameter LINELEN (maximum line length) for reference.
The parameter values depend on the value defined for CPI, and on the printer supported by the financial printer server. The allowed values range from 0 to the following CPI values:
The default is 80.
The default is 80.
The default is 41.
The default is 82.
The default is 40.
The default is 80.
The maximum value will be assumed if you specify 0 in any object type.
The parameter values depend on the object type:
The default is 5.
The default is 6.
The default is 5.
If the allowed skew is exceeded, the document is rejected, and must be reinserted. The maximum skew depends on the initial vertical offset chosen.
The parameter values are:
1 for 1.37 mm
2 for 2.05 mm
3 for 2.74 mm
4 for 3.42 mm
The default is 1.
The parameter value can be either Y (Yes) or N (No). The default is N.
The maximum number of lines depends on the line density (LPI) chosen and, in horizontal fold passbooks, the center fold skip. It also depends on the printer supported by the financial printer server.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed.
Maximum values are:
If 0 is specified, the default (4) will be taken.
If 0 is specified, the maximum value is assumed. The default is 60.
If 0 is specified, the maximum value is assumed. The default is 82.
If 0 is specified, the maximum value is assumed. The default is 165.
Permits the journal to be split up in logical pages by defining the number of print lines per page. When the end of the page is reached, the application receives a message and the journal is placed in line 1, column 1 of the next page.
If 0 is specified, no end of page checking will be performed, and the journal is treated as a continuous list. The default is 0.
If 0 is specified, the maximum value is assumed. The default is 30.
The parameter value can be either Y (Yes) or N (No). The default is N.
The default is D.
The parameter value can be either Y (Yes) or N (No). The default is N.
If you select Y for this keyword, you also have to select Y for keyword STARTKEY.
The default is N.
If you have selected Y for keyword SHARED, you also have to select Y here.
The value specified for VRTOFFSL plus the values for PAGESIZE and VRTOFFSS (and FOLDSKIP for horizontal passbook) must not be greater than maximum page size. The default is 0.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed.
Maximum values are:
The default is 0.
The parameter applies only to the 4772 printer. The parameter value can be either Y (Yes) or N (No). The default is N.
/* Vector FORM47X2 (Passbook) Example */ FORM47X2 TYPE=PASS, NAME=PASS001, LPI=5, CPI=10, MAXSKEW=1, FOLDTYPE=V, LINELEN=70, PAGESIZE=38, FOLDBEG=30, FOLDSKIP=1, VRTOFFSS=0, VRTOFFSL=0, HRZOFFS=10, AUTONL=Y, STARTKEY=N, SHARED=N
/* Vector FORM47X2 (REMS) Example */ FORM47X2 TYPE=REMS, NAME=REMS01, REMSMODE=D, DISPLACE=Y, NEWDOC=N, DBLREC=N, BKWIDTH=135
/* Vector FORM47X2 (Document) Default Example */ FORM47X2 TYPE=DOCU, NAME=DUMMYDOC, PAGESIZE=0, WRNLINE=0, VRTOFFSS=0, VRTOFFSL=0, LINELEN=0, SHARED=N, STARTKEY=Y, AUTONL=Y, CPI=10, LPI=5, QUALITY=N, DBLSTRK=N, EMPHASIZ=N, MAXSKEW=1, BOTTVAL=OFF, VRTOFFSI=1 /* Vector FORM47X2 (Journal) Default Example */ FORM47X2 TYPE=JOUR, NAME=DUMMYJOU, PAGESIZE=0, WRNLINE=0, LINELEN=0, QUALITY=N, DBLSTRK=N, EMPHASIZ=N, LPI=6, CPI=10, SHARED=N
Defines 4748 printer device parameters for documents and passbooks objects.
Define one FORM4748 vector for each 4748 printer object you want to use in your workgroups (documents or passbooks).
The following figure shows the layout of the document pages:
Figure 22. Document Dimensions for IBM 4748 Printer Customization
The following figure shows the layout of the passbook pages:
Figure 23. Passbook Dimensions for IBM 4748 Printer Customization
Vector position | None |
List of keywords | See keyword TYPE |
Keywords relate to |
|
Vector format |
FORM4748 TYPE=xxxx, NAME=xxxxxxxx, [AUTONL=x,] [BKWIDTH=xxx,] [BOTTVAL=xxx,] [CPI=xx,] [DBLREC=x,] [DBLSTRK=x,] [DISPLACE=x,] [EMPHASIZ=x,] [FOLDADDS=xx,] [FOLDBEG=xx,] [FOLDSKIP=x,] [FOLDTYPE=x,] [FONT=x,] [HISPEED=x,] [HRZOFFS=x,] [INITPOS=xxxxx,] [LINELEN=xx,] [LPI=x,] [MAXSKEW=x,] [NEWDOC=x,] [PAGESIZE=xx,] [REMSMODE=x,] [SHARED=x,] [STARTKEY=x,] [VRTOFFSL=x,] [VRTOFFSS=x,] [WRNLINE=x] |
Use the keywords only with their corresponding types. Otherwise, you will get an error.
The default is Y.
The maximum size for the printable area of a document to be checked is 2 inches.
The default is OFF.
Value 12 cannot be specified if you assign value 1, 3, or 5 to FONT keyword; value 13 or 15 cannot be specified if you assign value 1, 2, 3, or 5 to FONT keyword. The default is 10.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The default is 0.
The maximum number of xx for horizontal folds is:
The maximum number of xx for vertical folds is:
For horizontal fold passbooks, the minimum value is 1, and the maximum must not be greater than the specified PAGESIZE value.
For vertical fold passbooks, the minimum value is 1, and the maximum must not be greater than the specified LINELEN value.
If 0 is specified, the fold skip is considered to be in the page center for horizontal fold passbooks, and in the line center for vertical fold passbooks. The default is 10.
The center fold skip can be any value such that, when added to the page size (PAGESIZE for horizontal fold passbooks) or to the line length (LINELEN for vertical fold passbooks), the sum is less than or equal to the maximum logical page size or the maximum printer line length respectively.
The default is 4.
The default is 0.
The parameter value can be either Y (Yes) or N (No). The default is N.
The value, when added to the line length and center fold skip in a vertical fold passbook, must be less than or equal to the maximum line length. The default for PASS type objects is 0, and for DOCU type objects 1.
See parameter LINELEN (maximum line length) for reference.
The parameter value can be either FIRST or REMS. The default is FIRST.
The parameter values depend on the value defined for CPI. The allowed values range from 0 to the following CPI values:
If you specify 0, the maximum value will be assumed. The default is 80.
The parameter values depend on the object type. They are::
The default is 5.
The default is 5.
The parameter values are:
The default is 1.
The default is 1.
The parameter value can be either Y (Yes) or N (No). The default is N.
The maximum number of lines depends on the line density (LPI) chosen and, in horizontal fold passbooks, the center fold skip.
The parameter values are a numeric field with up to three digits, ranging from 0 to the maximum value allowed.
Maximum values are:
If you specify 0, the maximum value will be assumed. The default is 60.
If you specify 0, the maximum value will be assumed. The default is 30.
The parameter values are:
The default is D.
The parameter value can be either Y (Yes) or N (No). The default is N.
If you select Y for this keyword, you also have to select Y for keyword STARTKEY.
The default is N.
If you have selected Y for keyword SHARED, you also have to select Y here.
The value specified for VRTOFFSL plus the values for PAGESIZE and VRTOFFSS (and FOLDSKIP for horizontal passbook) must not be greater than maximum page size. The default is 0.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed.
Maximum values are:
The default is 0.
/* Vector FORM4748 (Document) Example */ FORM4748 TYPE=DOCU, NAME=DOC01, LPI=5, CPI=10, MAXSKEW=1, LINELEN=80, PAGESIZE=60, WRNLINE=0, DBLSTRK=N, EMPHASIZ=N, VRTOFFSS=0, VRTOFFSL=0, HRZOFFS=1, AUTONL=Y, STARTKEY=N, SHARED=N, BOTTVAL=OFF, HISPEED=N, FONT=4
Defines 4770 printer device parameters for documents and journals objects.
Define one FORM4770 vector for each 4770 printer object you want to use in your workgroups (documents or journals).
The following figure shows the layout of the document pages:
Figure 24. Document Dimensions for IBM 4770 Printer Customization
Vector position | None |
List of keywords | See keyword TYPE |
Keywords relate to | |
Vector format |
FORM4770 TYPE=xxxx, NAME=xxxxxxxx, [AUTONL=x,] [FONT=x,] [HRZOFFS=xx,] [LINELEN=xx,] [PAGESIZE=x,] [SPACING=x,] [UPSDOWN=x,] [VRTOFFSL=x,] [VRTOFFSS=xx,] [WIDECHR=x,] [WRNLINE=x] |
Use the keywords only with their corresponding types. Otherwise, you will get an error.
The default is Y.
The default is S.
The value, when added to the line length, must be less than or equal to the maximum line length. The default is 0.
See parameter LINELEN (maximum line length) for reference.
The value, when added to the horizontal character offset, must be less than or equal to the maximum line length. The default is 0.
The maximum line length is:
The value, when added to the value specified in the VRTOFFSL keyword, must be less than or equal to the maximum page length.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed. The default is 0.
The maximum page length is:
The parameter value can be either T (text) or L (logo). The default is T.
The parameter value can be Y, to use inverted printing, or N, not to use it. The default is N.
The value, when added to the value specified in the PAGESIZE keyword, must be less than or equal to the maximum page length. The default is 0.
The parameter values are a numeric field with up to two digits, ranging from 0 to the maximum value allowed. The default is 0.
Maximum values are:
The parameter value can be either Y (Yes) or N (No). The default is N.
/* Vector FORM4770 (Document) Example */ FORM4770 TYPE=DOCU, NAME=DOCU01, AUTONL=Y, FONT=S, HRZOFSS=0, LINELEN=48, PAGESIZE=6, SPACING=T, UPSDOWN=N, VRTOFFSL=0, VRTOFFSS=0, WIDECHR=N, WRNLINE=0 /* Vector FORM4770 (Journal) Example */ FORM47X2 TYPE=JOUR, NAME=JOUR01, AUTONL=Y, FONT=S, SPACING=T, UPSDOWN=N, WIDECHR=N
Defines parameters for forwarding a data set, that is, sending a data set to the host. Up to 64 FORWDS vectors can be defined in a forwarding server profile. The number of FORWDS vectors must match the number of data sets defined in the store-for-forwarding profile used.
Vector position | Follows FORWPRF vector. This vector can exist up to 64 times for each FORWPRF vector. |
List of keywords | SESSION, TRANSACT, PRTY, EBCDICXL, AUTTRANS |
Keywords relate to |
|
Vector format |
FORWDS SESSION=x, TRANSACT=xxxxxxxx, [PRTY=xx,] [EBCDICXL=x,] [AUTTRANS=x] |
The parameter value is a number from 1 to 3, depending on the number of sessions defined in the forwarding profile, and cannot be omitted.
If the host session (SxTYPE in the FORWPRF vector) was IMS, this parameter is an alphanumeric field of up to eight characters. If the host session was CICS, the field has up to four characters. You can include blanks if the transaction code does not fill the field.
This keyword is required, if DSPRTY=Y was specified in the FORWPRF vector. If not, it must be omitted.
The parameter value can be any number from 0 to 99, where 0 means no priority and 99 corresponds to the highest priority. The default is 0. Two data sets cannot have the same priority in the same session.
In DBCS mode those fields defined as pure DBCS or mixed, SBCS and DBCS, are also translated.
The parameter value can be either Y (Yes) or N (No). The default is Y.
The parameter value can be either Y (Yes) or N (No). The default is Y.
If automatic transmission is selected, the forwarding server periodically checks if there is data to be transmitted and automatically starts up. New transactions can be stored while the forwarding is in process. If transmission is stopped by an application, the transaction must be explicitly restarted by the application.
If AUTTRANS=N, the application is responsible for starting and stopping transmissions.
/* Vectors FORWPRF and FORWDS Examples */ FORWPRF NAME=FORWPRF1, BLKFAC=1, DSPRTY=Y, ALTSESS=Y, S1TYPE=CICS, S1MAXCHR=256, S1RESTO=30, S1RETTO=300, S1TYPDLC=SDLC, S1APPNAM=C1C3C4F1, S2TYPE=IMS, S2MAXCHR=256, S2RESTO=30, S2RETTO=300, S2TYPDLC=SDLC, S2APPNAM=C1C3C2F2 FORWDS SESSION=1, TRANSACT=TR01, PRTY=03, EBCDICXL=Y, AUTTRANS=Y FORWDS SESSION=2, TRANSACT=TR02, PRTY=02, EBCDICXL=N, AUTTRANS=Y
Defines a forwarding server profile. One vector has to be specified for each profile you are going to use in your workgroups. You can define up to three forwarding sessions in each profile. It may be necessary to define more than one profile, in order to:
This vector must be followed by as many FORWDS vectors as store-for-forwarding data sets have been defined in the SFORWPRF vector that will be used with this profile.
Vector position | None. Can be followed by up to 64 FORWDS vectors. |
List of keywords | NAME, BLKFAC, DSPRTY, ALTSESS, S1TYPE, S1MAXCHR, S1RESTO, S1RETTO, S1TYPDLC, S1APPNAM, S1INITS1, S1INITS2, S2TYPE, S2MAXCHR, S2RESTO, S2RETTO, S2TYPDLC, S2APPNAM, S2INITS1, S2INITS2, S3TYPE, S3MAXCHR, S3RESTO, S3RETTO, S3TYPDLC, S3APPNAM, S3INITS1, S3INITS2 |
Keywords relate to |
|
Vector format |
FORWPRF NAME=xxxxxxxx, [BLKFAC=xx,] [DSPRTY=x,] [ALTSESS=x,] S1TYPE=xxxx, [S2TYPE=xxxx,] [S3TYPE=xxxx,] [S1MAXCHR=xxx,] [S2MAXCHR=xxx,] [S3MAXCHR=xxx,] [S1RESTO=xxxx,] [S2RESTO=xxxx,] [S3RESTO=xxxx,] [S1RETTO=xxxx,] [S2RETTO=xxxx,] [S3RETTO=xxxx,] S1TYPDLC=xxxxx, [S2TYPDLC=xxxxx,] [S3TYPDLC=xxxxx,] S1APPNAM=xxxxxxxx, [S2APPNAM=xxxxxxxx,] [S3APPNAM=xxxxxxxx,] S1INITS1=xxxxx, [S2INITS1=xxxxx,] [S3INITS1=xxxxx,] S1INITS2=xxxxx, [S2INITS2=xxxxx,] [S3INITS2=xxxxx] |
The parameter value must be a numeric field from 1 to 99. The default is 1.
If a number other than 1 is specified, the forwarding server automatically blocks the data. A block can contain the records from one store-for-forwarding server data set only. The blocking of records is limited by the available buffer space for building the blocks.
If the number of records to be transmitted is less than the blocking factor, a short block is sent. If records or blocks are longer than 4096 bytes or exceed the maximum size of the chain element specified, the records are sent as a SNA chained message. The host application that receives the forwarded data must be able to receive chained messages and to recover the individual records.
For more information about the block transmission, refer to the LANDP Severs and System Management book.
The parameter value can be either Y (Yes) or N (No). The default is Y.
In the following keywords, S1 means session 1, S2 session 2, and S3 session 3.
If S2TYPE is N/A, it deletes the definition of session 2. In this case, you cannot define session 3. The default is N/A.
If S3TYPE is N/A, it deletes the definition of session 3. The default is N/A.
The parameter value is a numeric field from 1 to 4096 bytes. If this keyword is omitted, the default is 256.
This keyword cannot be specified, if the respective session was N/A.
The parameter value is a numeric field from 1 to 1500. If this keyword is omitted, the default is 30 seconds.
This keyword cannot be specified, if the respective session was N/A.
The parameter value is a numeric field from 1 to 1500. If this keyword is omitted, the default is 300 seconds.
This keyword cannot be specified, if the respective session was N/A.
Parameter values are SDLC (synchronous), TRDLC (token ring), DCADLC (device cluster adapter), or X25DLC.
This keyword is required for each session that is NOT N/A.
The parameter values are fields with a length from 8 to 16 hexadecimal characters.
The SNA server builds the complete INITSELF string using this name. If this keyword is specified for a session, SxINITSx keyword must be omitted.
Any session that is not N/A requires either APPNAM or SxINITS1 (and SxINITS2). The INITSELF string must be specified using either one or the other.
This keyword cannot be specified, if the respective session was N/A.
Up to 48 hexadecimal digits can be specified as part 1 of the INITSELF string.
If these keywords are specified for the respective session, SxAPPNAM keywords must be omitted.
This keyword cannot be specified, if the respective session was N/A.
If these keywords are specified for the session, SxAPPNAM keyword must be omitted.
This keyword cannot be specified, if the respective session was N/A.
/* Vectors FORWPRF and FORWDS Examples */ FORWPRF NAME=FORWPRF1, BLKFAC=1, DSPRTY=Y, ALTSESS=Y, S1TYPE=CICS, S1MAXCHR=256, S1RESTO=30, S1RETTO=300, S1TYPDLC=SDLC, S1APPNAM=C1C3C4F1, S2TYPE=IMS, S2MAXCHR=256, S2RESTO=30, S2RETTO=300, S2TYPDLC=SDLC, S2APPNAM=C1C3C2F2 FORWDS SESSION=1, TRANSACT=TR01, PRTY=03, EBCDICXL=Y, AUTTRANS=Y FORWDS SESSION=2, TRANSACT=TR02, PRTY=02, EBCDICXL=N, AUTTRANS=Y
Defines a keyboard table for the 3270 Emulator. Specify one vector for each 3270 keyboard table you want to use in your workgroups.
The 3270 keyboard table allows you to associate function codes or data with the SCAN/ASCII code combination generated by every key on the keyboard.
There is a help facility for calling the scan and ASCII codes for each key on your keyboard. From the EHCCUS subdirectory, enter:
EHCSC
and you will get an interactive help panel where you can enter any key to find out the specified values.
The KBD3270 vector relates to the vector that defines the translation table generated by the keyboard ASCII codes with the EBCDIC host translation, XLATETBL TYPE=AE3270. You associate the two vectors by defining the same value for keyword EXTEN.
There is a limit on the number of keys that can be defined by using the KBD3270 vector. This limit depends on the size of the data strings associated with the keys and is, typically, about 80 or 90 key definitions. If you need to define more keys than this, use the KBD3270X vector to provide the extra definitions.
The following figure contains the scan and ASCII codes for the default key
assignments for the 3270 Emulator program functions, when using an English
keyboard.
This is the default KBD3270 vector (KBD3270 vector with EXTEN=KBD), the source
for which can be generated using GENSPEC after a CREATE. You can then
change or add values.
Scan code | ASCII code | Keyboard key | Function |
---|---|---|---|
01 | 00 | Alt+Esc | End emulation |
01 | 1B | Esc | Reset |
0E | 08 | Backspace | Cursor left and delete |
0F | 00 | SHIFT+TAB | Backtab |
0F | 09 | Tab | Tab |
10 | 00 | Alt+Q | Alternate cursor |
1C | 0D | Enter | New line |
1E | 00 | Alt+A | Attention |
1F | 00 | Alt+S | System request |
20 | 00 | Alt+D | Dup |
21 | 00 | Alt+F | Field mark |
2E | 00 | Alt+C | Cursor selection |
3B | 00 | F1 | PF1 |
3C | 00 | F2 | PF2 |
3D | 00 | F3 | PF3 |
3E | 00 | F4 | PF4 |
3F | 00 | F5 | PF5 |
40 | 00 | F6 | PF6 |
41 | 00 | F7 | PF7 |
42 | 00 | F8 | PF8 |
43 | 00 | F9 | PF9 |
44 | 00 | F10 | PF10 |
47 | 00 | HOME (numeric pad) | Home |
47 | E0 | HOME | Home |
48 | 00 | ^ (numeric pad) | Cursor up |
48 | E0 | ^ | Cursor up |
4A | 2D | - | Clear |
4B | 00 | < (numeric pad) | Cursor left |
4B | E0 | < | Cursor left |
4D | 00 | > (numeric pad) | Cursor right |
4D | E0 | > | Cursor right |
4E | 2B | + | Enter |
4F | 00 | End (numeric pad) | Erase EOF |
4F | E0 | End | Erase EOF |
50 | 00 | V (numeric pad) | Cursor down |
50 | E0 | V | Cursor down |
52 | 00 | Insert (numeric pad) | Toggle insert |
52 | E0 | Insert | Toggle insert |
53 | 00 | Del (numeric pad) | Delete |
53 | E0 | Del | Delete |
54 | 00 | SHIFT+F1 | PF13 |
55 | 00 | SHIFT+F2 | PF14 |
56 | 00 | SHIFT+F3 | PF15 |
57 | 00 | SHIFT+F4 | PF16 |
58 | 00 | SHIFT+F5 | PF17 |
59 | 00 | SHIFT+F6 | PF18 |
5A | 00 | SHIFT+F7 | PF19 |
5B | 00 | SHIFT+F8 | PF20 |
5C | 00 | SHIFT+F9 | PF21 |
5D | 00 | SHIFT+F10 | PF22 |
68 | 00 | Alt+F1 | PA1 |
69 | 00 | Alt+F2 | PA2 |
6C | 00 | Alt+F5 | End emulation |
85 | 00 | F11 | PF11 |
86 | 00 | F12 | PF12 |
87 | 00 | SHIFT+F11 | PF23 |
88 | 00 | SHIFT+F12 | PF24 |
E0 | 0D | Enter (numeric pad) | Enter |
You can edit the KBD3270 vector to use the following scan code values for
additional emulated 3270 keyboard keys.
Table 11. Emulated Keyboard Key Codes
Scan code | ASCII code | Keyboard key |
---|---|---|
01 | FF | Left CTRL |
02 | FF | Left ALT |
04 | FF | Right CTRL |
08 | FF | Right ALT |
10 | FF | Scroll Lock |
20 | FF | Num Lock |
40 | FF | Caps Lock |
80 | FF | Sys Req |
You can combine these by OR-ing the values together. For example:
Left CTRL + Scroll Lock = 11,FF
Vector position | None |
List of keywords | EXTEN, KEY |
Keywords relate to |
|
Vector format |
KBD3270 EXTEN=xxx, KEY=( ) |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all KBD3270 vectors.
When defining a 3270 emulator, parameter 7 of the SES&3270 keyword is a pointer to this identification.
This keyword has three parameters:
Mixing function and data strings is allowed when linking them with a plus (+) sign. The whole parameter is defined between single quotes ('). Data strings must be defined between double quotes ("). Function codes can match functions as described in Table 10. The following can also be specified:
For example:
'HOME+"data string"+PF4'
If single or double quotes are part of a data string, they must be doubled.
/* Vector KBD3270 Default Example */ KBD3270 EXTEN=KBD, KEY=(48,E0,'CURSOR UP'), KEY=(50,E0,'CURSOR DOWN'), KEY=(4B,E0,'CURSOR LEFT'), KEY=(4D,E0,'CURSOR RIGHT'), KEY=(52,E0,'TOGGLE INSERT'), KEY=(53,E0,'DELETE'), KEY=(47,E0,'HOME'), KEY=(4F,E0,'ERASE EOF'), KEY=(48,00,'CURSOR UP'), KEY=(50,00,'CURSOR DOWN'), KEY=(4B,00,'CURSOR LEFT'), KEY=(4D,00,'CURSOR RIGHT'), KEY=(52,00,'TOGGLE INSERT'), KEY=(53,00,'DELETE'), KEY=(47,00,'HOME'), KEY=(4F,00,'ERASE EOF'), KEY=(1C,0D,'NEW LINE'), KEY=(E0,0D,'ENTER'), KEY=(4E,2B,'ENTER'), KEY=(4A,2D,'CLEAR'), KEY=(01,1B,'RESET'), KEY=(01,00,'END EMULATION'), KEY=(6C,00,'END EMULATION'), KEY=(0F,09,'TAB'), KEY=(0F,00,'BACKTAB'), KEY=(0E,08,'CURSOR LEFT+DELETE'), KEY=(3B,00,'PF1'), KEY=(3C,00,'PF2'), KEY=(3D,00,'PF3'), KEY=(3E,00,'PF4'), KEY=(3F,00,'PF5'), KEY=(40,00,'PF6'), KEY=(41,00,'PF7'), KEY=(42,00,'PF8'), KEY=(43,00,'PF9'), KEY=(44,00,'PF10'), KEY=(85,00,'PF11'), KEY=(86,00,'PF12'), KEY=(55,00,'PF14'), KEY=(56,00,'PF15'), KEY=(57,00,'PF16'), KEY=(58,00,'PF17'), KEY=(59,00,'PF18'), KEY=(5A,00,'PF19'), KEY=(5B,00,'PF20'), KEY=(5C,00,'PF21'), KEY=(5D,00,'PF22'), KEY=(87,00,'PF23'), KEY=(88,00,'PF24'), KEY=(68,00,'PA1'), KEY=(69,00,'PA2'), KEY=(20,00,'DUP'), KEY=(21,00,'FIELD MARK'), KEY=(10,00,'ALTERNATE CURSOR'), KEY=(2E,00,'CURSOR SELECTION'), KEY=(1F,00,'SYSTEM REQUEST'), KEY=(54,00,'PF13'), KEY=(1E,00,'ATTENTION')
Defines additional keys for a keyboard table for the 3270 emulator. Specify one vector for each of your 3270 keyboard tables that need more key definitions.
When you need more key definitions for a keyboard table, specify a KBD3270X vector with the same value for its EXTEN keyword as you gave to the table that requires the additional keys.
Vector position | None |
List of keywords | EXTEN, KEY |
Keywords relate to |
|
Vector format |
KBD3270X EXTEN=xxx, KEY=( ) |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must match the EXTEN value of a KBD3270 vector.
When defining a 3270 emulator, parameter 7 of the SES&3270 keyword is a pointer to this identification.
This keyword has three parameters:
Mixing function and data strings is allowed when linking them with a plus (+) sign. The whole parameter is defined between single quotes ('). Data strings must be defined between double quotes ("). Function codes can match functions as described in Table 10. The following can also be specified:
For example:
'HOME+"data string"+PF4'
If single or double quotes are part of a data string, they must be doubled.
/* Vector KBD3270X Example */ KBD3270X EXTEN=KBD, KEY=(1E,00,'HOME+"HOST1"+ENTER'), KEY=(3E,00,'HOME+"HOST2"+ENTER')
Defines a keyboard table for the Banking Interactive Workstation Program (BIWP). Specify one vector for each BIWP keyboard table you want to use in your workgroups.
The BIWP keyboard table allows you to associate function codes or data with the SCAN/ASCII code combination generated by every key on the keyboard.
There is a help facility for calling the scan and ASCII codes for each key on your keyboard. From the EHCCUS subdirectory, enter:
EHCSC
and you will get an interactive help panel where you can enter any key to find out the specified values.
The keyboard definition vector is associated with three other vectors. The first two are optional, the third is required.
You associate the four vectors by defining the same value for the keyword EXTEN.
The keyboard table used by the BIWP can be changed from the 4700 application with the SWAPTT instructions. When the active keyboard table is changed, the active tables for all the group of vectors with the same EXTEN keyword will also be changed accordingly.
The following figure shows the defaults provided for the default keyboard
table.
You can change or add values.
Table 12. Keyboard Key Defaults
Function | Scan/ASCII Codes | Keyboard key |
---|---|---|
JUMP (see notes below the table) | 01 00 (see notes below the table) | [Alt] + [Esc] |
RESET | 01 1B | [Esc] |
BACKSPACE + SEG DELETE | 0E 08 | [Backspace] |
MSR/E CANCEL | 12 00 | [Alt] + [E] |
PIN pad CANCEL | 19 00 | [Alt] + [P] |
EOM, X'FF' | 1C 0D | [Return] |
CANCEL | 2E 00 | [Alt] + [C] |
MONITOR | 32 00 | [Alt] + [M] |
BACKSPACE | 4B 00 | [Left arrow] |
BACKSPACE | 4B E0 (see notes below the table) | [Left arrow] |
ADVANCE | 4D 00 | [Right arrow] |
ADVANCE | 4D E0 (see notes below the table) | [Right arrow] |
EOM, X'FF' | 4E 2B | [+] |
END OF INPUT | 4F 00 | [End] |
END OF INPUT | 4F E0 (see notes below the table) | [End] |
TOG.SEG. INSERT | 52 00 | [Ins] |
TOG.SEG. INSERT | 52 E0 (see notes below the table) | [Ins] |
SEGMENT DELETE | 53 00 | [Del] |
SEGMENT DELETE | 53 E0 (see notes below the table) | [Del] |
JUMP (see notes below the table) | 6C 00 | [Alt] + [F5] |
JUMP (see notes below the table) | 6D 00 | [Alt] + [F6] |
JUMP (see notes below the table) | 6E 00 | [Alt] + [F7] |
JUMP (see notes below the table) | 6F 00 | [Alt] + [F8] |
JUMP (see notes below the table) | 70 00 | [Alt] + [F9] |
ERASE END OF SEG. | 75 E0 (see notes below the table) | [Ctrl] + [End] |
EOM, X'FF' | E0 0D (see notes below the table) | [Enter] |
Notes:
Vector position | None |
List of keywords | EXTEN, APPLIC, EAEXTEN, KEY |
Keywords relate to |
|
Vector format |
KBDBIWP EXTEN=xxx, [APPLIC=xxxxxxxx,] [EAEXTEN=xxx,] KEY=( ) |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all KBDBIWP vectors.
The parameter value cannot be UNI, since it is a reserved name.
When defining a BIWP emulator, parameter 18 of the SES&BIWP keyword is a pointer to this identification.
The parameter value can have a maximum of eight alphanumeric characters, plus the special characters $, %, #, and @. It must be unique among all KBDBIWP vectors.
It will be translated to EBCDIC using the international code pages 850 and 500.
If you want to change this table, you must define it.
The parameter value is a 3-character string and must adhere to DOS specifications for file extensions. It must match the parameter of the EXTEN keyword in a XLATETBL vector (TYPE=EABIWP).
This keyword has three parameters:
The whole parameter is defined between single quotes ('). Mixing function code and data is allowed when linking them by using a plus (+) sign.
ASCII data strings are defined between double quotes ("). Hexadecimal or EBCDIC data strings are defined between double quotes and are preceded by a colon (:). They will be a group of hexadecimal pairs with the EBCDIC values.
Function codes can match functions as described in Table 12.
The following can also be specified:
If singlequotes, double quotes, or colons are part of a data string, they must be doubled.
When defining the function codes for the functions
the function code must be followed by a plus (+) sign and two hexadecimal digits corresponding to the EOM mask.
Note that when defining the function code for the EOM, EID function, you can specify only one byte. As SMSEID is a 1-byte field, the customization program requires that you enter a 1-byte character string before assigning the EOM, EID function to a key. This 1-byte character string is placed in SMSEID. To generate more than one character, you must define two concatenated character strings: one with the byte to be placed in SMSEID, and one with the rest of the characters.
For example, to define an EOM, EID key that generates EBCDIC C2 in the SMSEID field and EBCDIC C1 in the user segment, with the EOM mask being FF, the value for the third parameter must be:
'":C1"+":C2". +'EOM,EID+FF'
/* Vector KBDBIWP Default Example */ KBDBIWP EXTEN=KBD, APPLIC=DEFAULT, EAEXTEN=DIS, KEY=(01,1B,'RESET'), KEY=(70,00,'JUMP'), KEY=(2E,00,'CANCEL'), KEY=(32,00,'MONITOR'), KEY=(E0,0D,'EOM+FF'), KEY=(1C,0D,'EOM+FF'), KEY=(4B,00,'BACKSPACE'), KEY=(4D,00,'ADVANCE'), KEY=(4D,E0,'ADVANCE'), KEY=(4B,E0,'BACKSPACE'), KEY=(53,00,'SEG. DELETE'), KEY=(52,00,'TOG.SEG. INSERT'), KEY=(53,E0,'SEG. DELETE'), KEY=(52,E0,'TOG.SEG. INSERT'), KEY=(0E,08,'BACKSPACE+SEG. DELETE'), KEY=(19,00,'PIN PAD CANCEL'), KEY=(12,00,'MSR/E CANCEL'), KEY=(4F,E0,'END OF INPUT'), KEY=(75,E0,'ERASE END OF SEG'), KEY=(4E,2B,'EOM+FF'), KEY=(4F,00,'END OF INPUT'), KEY=(01,00,'JUMP'), KEY=(6C,00,'JUMP'), KEY=(6D,00,'JUMP'), KEY=(6E,00,'JUMP'), KEY=(6F,00,'JUMP')
Defines an issue-keyboard-scan code translation table for the Banking Interactive Workstation Program.
This vector is used to match scan codes and their associated shift states, which are used by the application when using the BIWP issue-keyboard-scan code function with the keyboard definition vector (KBDBIWP). You associate a KSCCBIWP vector with a KBDBIWP vector by defining the same value for the keyword EXTEN in both vectors.
Define as many KSCCBIWP vectors as different BIWP keyboard definition vectors you are going to use through the issue-keyboard-scan code function.
If this vector is omitted, an empty table will be created.
Vector position | None |
List of keywords | EXTEN, KEY |
Keywords relate to |
|
Vector format |
KSCCBIWP EXTEN=xxx, KEY=( ) |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be the same as defined in the associated KBDBIWP vector.
The keyword has four parameters.
The first and second parameters define the shift state and scan code values that will be used by the application when using the BIWP issue-keyboard-scan code function. The shift state/scan code combination must be unique in the table.
The third and fourth parameters define the SCAN and ASCII codes of a key defined in the associated KBDBIWP vector.
/* Vector KSCCBIWP Example */ KSCCBIWP EXTEN=KBD, KEY=(S,06,4D,E0), KEY=(U,32,4B,00), KEY=(U,33,E0,0D), KEY=(U,34,1C,0D)
Defines a present-keystroke translation table for Banking Interactive Workstation Program.
This vector is used to define how the keystrokes, used by the application when using the present-keystroke function, match with the keyboard definition vector (KBDBIWP). You associate a KSTRBIWP vector with a KBDBIWP vector by defining the same value for the keyword EXTEN in both vectors. Specify one vector for each BIWP keyboard definition vector you are going to use through the present-keystroke function.
If the KSTRBIWP vector is omitted, an empty table will be generated.
The following figure shows the values defined in the default KSTRBIWP
vector (KSTRBIWP vector with keyword EXTEN=KBD).
Table 13. Present-keystroke defaults
Function | Scan/ASCII Codes | Keystroke Values |
---|---|---|
EOM, FF | 1C 0D | 0D |
RESET | 01 1B | 00 |
BACKSPACE | 4B 00 | 03 |
ADVANCE | 4D 00 | 04 |
BACKSPACE + SEGMENT DELETE | 0E 08 | 08 |
Vector position | None |
List of keywords | EXTEN, KEY |
Keywords relate to |
|
Vector format |
KSTRBIWP EXTEN=xxx, KEY=( ) |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be the same as defined in the associated KBDBIWP vector, in the EXTEN keyword.
The keyword has three parameters:
/* Vector KSTRBIWP Default Example */ KSTRBIWP EXTEN=KBD, KEY=(0D,1C,0D), KEY=(03,4B,00), KEY=(04,4D,00), KEY=(08,0E,08), KEY=(00,01,1B)
Defines LUs for host communication using the SNA server with LU pooling on a DOS workstation. One vector is required for each LU to be pooled. All the LUs to be used by the SNA server must be in the same LUPOOL table - in other words, they must have the same NAME parameter value.
Vector position | None |
List of keywords | NAME, GROUPID, DLC, LUNUMBER |
Keywords relate to |
|
Vector format |
LUPOOL NAME=xxxxxxxx, GROUPID=xx, DLC=xxx, LUNUMBER=xxx |
The parameter value is a string of up to eight alphanumeric characters and may contain the special characters #, _, %, or @.
The parameter value is a string of two characters: the first character must be alphabetical, and the second one numerical.
For DLCs other than X.25, the parameter value can be:
For X.25 DLCs, the parameter value ranges from 1 to 999, and corresponds to the virtual circuit definition identification.
The parameter value ranges from 1 to 254, and must be unique for the data link control (DLC) or virtual circuit.
/* Vector LUPOOL Example */ LUPOOL NAME=LUPOOL1, GROUPID=P1, DLC=SDL, LUNUMBER=1
Defines an input translation table for the Banking Interactive Workstation Program when reading the MSR/E. Define one MSRINTBL vector for every MSR/E input table that you want to use in your workgroups.
Vector position | None |
List of keywords | EXTEN, TRKOPER, DELAY, TR2CHR0 to TR2CHRF, TR3CHR0 to TR3CHRF |
Keywords relate to |
|
Vector format |
MSRINTBL EXTEN=xxx, [TRKOPER=( ),] [DELAY=xx,] [TR2CHR0=( ),] [TR3CHR0=( )] |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all MSRINTBL vectors.
When defining a BIWP server, one of the parameters of the PAR&BIWP keyword is a pointer to this identification.
The keyword has two parameters:
The default is 2.
The parameter value ranges from 1 to 60. The default is 5.
Each keyword has two parameters:
The default is no defined character.
The default is NONE.
/* Vector MSRINTBL Default Example */ MSRINTBL EXTEN=MSR, TRKOPER=(2,Y), TR2CHR0=(":F0",NONE), TR2CHR1=(":F1",NONE), TR2CHR2=(":F2",NONE), TR2CHR3=(":F3",NONE), TR2CHR4=(":F4",NONE), TR2CHR5=(":F5",NONE), TR2CHR6=(":F6",NONE), TR2CHR7=(":F7",NONE), TR2CHR8=(":F8",NONE), TR2CHR9=(":F9",NONE), TR2CHRC=(":7C",EOM), TR2CHRD=(":7D",NONE), TR2CHRE=(":7E",NONE), TR3CHR0=(":F0",NONE), TR3CHR1=(":F1",NONE), TR3CHR2=(":F2",NONE), TR3CHR3=(":F3",NONE), TR3CHR4=(":F4",NONE), TR3CHR5=(":F5",NONE), TR3CHR6=(":F6",NONE), TR3CHR7=(":F7",NONE), TR3CHR8=(":F8",NONE), TR3CHR9=(":F9",NONE), TR3CHRA=(":FA",NONE), TR3CHRC=(":7C",NONE), TR3CHRE=(":7E",NONE)
Defines an output translation table for the Banking Interactive Workstation Program when writing to the MSR/E. Define one MSROUTBL vector for every MSR/E output table that you want to use in your workgroups.
Vector position | None |
List of keywords | EXTEN, OPTIONS, OUTCHR0 to OUTCHRF |
Keywords relate to |
|
Vector format |
MSROUTBL EXTEN=xxx, [OPTIONS=( ),] [OUTCHR0=( )] |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all MSROUTBL vectors.
When defining a BIWP, one of the parameters of the PAR&BIWP keyword is a pointer to this identification.
The parameter value can be either Y (Yes) or N (No). The default is N.
You must write the corresponding OUTCHRx for every character you want to be written to the MSR/E. If the keyword is omitted for a character, it will not be written. Each keyword has three parameters:
/* Vector MSROUTBL Default Example */ MSROUTBL EXTEN=MSR, OPTIONS=(IBM,2,N), OUTCHR0=(F0,Y,N), OUTCHR1=(F1,Y,N), OUTCHR2=(F2,Y,N), OUTCHR3=(F3,Y,N), OUTCHR4=(F4,Y,N), OUTCHR5=(F5,Y,N), OUTCHR6=(F6,Y,N), OUTCHR7=(F7,Y,N), OUTCHR8=(F8,Y,N), OUTCHR9=(F9,Y,N), OUTCHRA=(00,N,N), OUTCHRB=(00,N,N), OUTCHRC=(7C,Y,Y), OUTCHRD=(7D,Y,N), OUTCHRE=(7E,Y,N), OUTCHRF=(00,N,N)
Defines an attribute table for the 3287 emulator.
One vector has to be specified for each 3287 emulator attribute table that you want to use in your workgroups.
Vector position | None |
List of keywords | EXTEN, TIMEOUT, LSTDELIM, DEFCCHR, RESET |
Keywords relate to |
|
Vector format |
P3287ATT EXTEN=xxx, [TIMEOUT=xxxx,] [LSTDELIM=xxxxxxxx,] [DEFCCHR=xx,] [RESET=( )] |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all P3287ATT vectors.
When defining a 3287 printer emulator, one of the parameters of the PAR&3287 keyword is a pointer to this identification.
The parameter value is a field with up to four characters and can take the values between 0 and 3600. The default is 15 seconds.
The parameter value is a string of up to eight alphanumeric characters.
The application sends a LISTL (LISTL=xxxxxxxx) that identifies the beginning of the identified listing. The emulator program considers the listing to be finished when the corresponding ENDL (ENDL=xxxxxxxx) is received. Normally, the application sends a form feed control character following the ENDL. If the ENDL is not received, the following happens:
The parameter value is a field of up to 45 hexadecimal bytes. The hexadecimal bytes must be separated with a comma (,).
You only need to define this keyword if you use a printer that uses different reset control characters from those for the printers explicitly supported by the 3287 emulator.
/* Vector P3287ATT Default Example */ P3287ATT EXTEN=TAB, TIMEOUT=15, DEFCCHR=00
Defines an input translation table to be used by BIWP when reading the PIN pad. Define one PINPTBL vector for every PIN pad input table that you want to use in your workgroups.
Vector position | None |
List of keywords | EXTEN, FILLER, KEY0 to KEY9, KEYSCP, KEYSEP, KEYENDP |
Keywords relate to |
|
Vector format |
PINPTBL EXTEN=xxx, [FILLER=x,] [KEY0=( ),] [KEYSCP=( ),] [KEYSEP=( ),] [KEYENDP=( )] |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all MSROUTBL vectors.
When defining a BIWP, one of the parameters of the PAR&BIWP keyword is a pointer to this identification.
The parameter value is one ASCII character. Special characters have to be put between single quotes (''). The default is an asterisk (*).
You must write the corresponding KEYx for every character in PIN pad for which you want to generate data or EOM indicator. If the keyword is omitted for a character, no data will be sent to the 4700 when this character is read. Each keyword has three parameters:
The value must be a 2-byte digit and must be unique in the vector.
If the keyword is omitted, the defaults will be assumed.
The keyword has three parameters:
The value must be a 2-byte digit and must be unique in the vector.
The default is 7F.
If the keyword is omitted, the defaults will be assumed.
The keyword has three parameters:
The value must be a 2-byte digit and must be unique in the vector.
The default is 7E.
If the keyword is omitted, the defaults will be assumed.
The keyword has three parameters:
The value must be a 2-byte digit and must be unique in the vector.
The default is 7F.
/* Vector PINPTBL Default Example */ PINPTBL EXTEN=PIN, FILLER=*, KEY0=(F0,H,N), KEY1=(F1,H,N), KEY2=(F2,H,N), KEY3=(F3,H,N), KEY4=(F4,H,N), KEY5=(F5,H,N), KEY6=(F6,H,N), KEY7=(F7,H,N), KEY8=(F8,H,N), KEY9=(F9,H,N), KEYSCP=(7F,H,N), KEYSEP=(7E,H,N), KEYENDP=(7F,H,N)
Vector position | None |
List of keywords | NAME, PATH |
Vector format |
RCMSLNF NAME=xxxxxxxx, PATH=path |
The parameter value is a string of up to eight characters starting with an alphabetical character. It must be unique among all RCMS logical names.
The parameter value is a string of up to 64 characters and must adhere to DOS specifications for path and file names. It must be unique among all RCMLNF vectors.
/* Vector RCMSLNF Example */ RCMSLNF NAME=NAME001, PATH=C:\LEVEL1\LEVEL2\LEVEL3\
For more information on RCMS see LANDP Servers and System Management.
Defines a record structure. Every record you define has a name and can contain several fields. Every field in the record has a name and associated parameters to enable validation when the data is updated. Up to 92 fields can be defined in the RECFIELD vector.
Up to 250 RECDEF statements can be defined.
The record definition facility supports the following record formats:
The record definition facility defines the record structures used by the following LANDP family servers:
The validate record (VR) function of the System Manager server can be used to validate data against the record structure defined by the RECDEF vector.
The applications and the user servers can also use the record structures defined with this vector.
Vector position | None. Can be followed by up to 92 RECFIELD vectors. |
List of keywords | NAME, DELIMIT, DECSEP |
Keywords relate to |
|
Vector format |
RECDEF NAME=xxxxxxxx, [DELIMIT=x,] [DECSEP=x] |
The parameter value is a string with up to eight alphanumeric characters. It must be unique for all the RECDEF vectors.
This name can be referenced by the electronic journal server (EJOUREC vector), the shared-file server (SHFLDBD vector), or the store-for-forwarding server (SFORWREC vector).
Parameter values are the special characters \, /, $, @, &, and %. They must be enclosed between single quotes. The default is '/'.
If you specify pure DBCS or mixed, SBCS and DBCS, field format in an associate RECFIELD vector, characters \ and @ are not supported as delimiters.
The parameter value can either be the period (.) or the comma (,). They must be enclosed between single quotes. The default is the comma (,).
/* Vectors RECDEF and RECFIELD Examples */ /* RECORD1 Definition */ RECDEF NAME=RECORD1, DELIMIT='/', DECSEP=',' RECFIELD NAME=REC1FL01, LENGTH=4, FORMAT=C, DESCRIPT='TRANSACTION' RECFIELD NAME=FILLER1, LENGTH=2, FORMAT=C, DESCRIPT='2 BYTE FILLER' RECFIELD NAME=REC1FL02, LENGTH=10, FORMAT=N, DECIMALS=2, DESCRIPT='AMOUNT' RECFIELD NAME=REC1FL03, LENGTH=8, FORMAT=N, DECIMALS=0, DESCRIPT='CLIENT NUMBER' /* RECORD2 Definition */ RECDEF NAME=RECORD2, DELIMIT='/', DECSEP=',' RECFIELD NAME=REC2FL01, LENGTH=10, FORMAT=N, DECIMALS=2, DESCRIPT='BALANCE' RECFIELD NAME=REC2FL02, LENGTH=4, FORMAT=P, DECIMALS=0, DESCRIPT='CHECK TOTAL'
RECFIELD NAME=REC2FL03, LENGTH=4, FORMAT=P, DECIMALS=0, DESCRIPT='CASH TOTAL'
Defines a field inside a record structure.
At least one RECFIELD vector must be specified following a RECDEF vector. Up to 92 RECFIELD vectors can follow a RECDEF vector.
Vector position | Follows RECDEF vector. This vector can exist up to 92 times after a RECDEF vector. |
List of keywords | NAME, DECIMALS, DESCRIPT, FORMAT, LENGTH |
Keywords relate to |
|
Vector format |
RECFIELD NAME=xxxxxxxx, [DECIMALS=x,] [DESCRIPT=' ',] [FORMAT=xx,] LENGTH=xxxx |
The parameter value is a string of up to eight alphanumeric characters plus the special characters $, %, #, and @. It must start with an alphanumeric character and must be unique within one RECDEF vector, but can be repeated in different RECDEF vectors.
The parameter value can be a number from 0 to 9, and must not be greater than the field length. The default is 0.
The parameter value is a string with up to 30 alphanumeric characters. As this field may contain blanks or special characters, it must be enclosed between quotes. If quotes are part of the description, they must be doubled.
The parameter values are:
Values CD and CM apply only to DBCS mode. The default is C.
The parameter values are numeric characters from 0 to 4096. The allowed length depends on the field format:
Variable fields in a record will be considered length 1. At run time, the sum of all lengths in a record cannot exceed 4096 bytes.
/* Vectors RECDEF and RECFIELD Examples */ /* RECORD1 Definition */ RECDEF NAME=RECORD1, DELIMIT='/', DECSEP=',' RECFIELD NAME=REC1FL01, LENGTH=4, FORMAT=C, DESCRIPT='TRANSACTION' RECFIELD NAME=FILLER1, LENGTH=2, FORMAT=C, DESCRIPT='2 BYTE FILLER' RECFIELD NAME=REC1FL02, LENGTH=10, FORMAT=N, DECIMALS=2, DESCRIPT='AMOUNT' RECFIELD NAME=REC1FL03, LENGTH=8, FORMAT=N, DECIMALS=0, DESCRIPT='CLIENT NUMBER' /* RECORD2 Definition */ RECDEF NAME=RECORD2, DELIMIT='/', DECSEP=',' RECFIELD NAME=REC2FL01, LENGTH=10, FORMAT=N, DECIMALS=2, DESCRIPT='BALANCE' RECFIELD NAME=REC2FL02, LENGTH=4, FORMAT=P, DECIMALS=0, DESCRIPT='CHECK TOTAL'
RECFIELD NAME=REC2FL03, LENGTH=4, FORMAT=P, DECIMALS=0, DESCRIPT='CASH TOTAL'
Defines a store-for-forwarding server profile. Define one SFORWPRF vector for each store-for-forwarding profile you want to specify.
You must define as many records as you need in vectors RECDEF and RECFIELD.
Vector position | None. Can be followed by at least one SFORWREC vector. |
List of keywords | NAME, DATASETS, SEPSESS, MAXACC, SHFLPRF, DBDPATH, DBDPATH6, SPLIT, KEY02 to KEY15 |
Keywords relate to |
|
Vector format |
SFORWPRF NAME=xxxxxxxx, [DATASETS=xx,] [SEPSESS=x,] [MAXACC=xxxxx,] SHFLPRF=xxxxxxxx, DBDPATH=path, DBDPATH6=path, SPLIT=length, [KEY02=xxxxxxxx,] : [KEY15=xxxxxxxx] |
The parameter value is a field with up to two characters, ranging from 1 to 64. The default is 3.
If you are using the forwarding server, this value must be greater than or equal to the number of FORWDS vectors defined for the forwarding profile that will be used together with this profile. The other data sets will not be forwarded and can be accessed by the applications.
Specify Y (Yes) if you want session integrity to be handled by the store-for-forwarding server, independently of your own shared-file server session. The default is N (No).
The parameter value is a string of up to 5 numeric characters, which can range from 1 to 32767. The default is 200.
In any case, the customization adds to the shared-file profile the DBD and PCB definitions required for this store-for-forwarding profile.
The same shared-file profile can only be used by one store-for-forwarding profile. If you have the store-for-forwarding server and the electronic journal server in the same workstation, you must use the same shared-file profile for both of them.
The parameter value is a field with up to eight alphanumeric characters. It must be unique among the SFORWPRF vectors.
The parameter value is the complete path (drive plus subdirectories). The number of subdirectories must not exceed four, and has to end with a back slash (\). It must at least contain three characters.
The parameter value is the complete path including the subdirectories. It must not exceed 56 characters, and must be enclosed within single quotes ('). Each subdirectory name included in the path must have one character at least, and 30 characters at most. A backslash ('\') must not be present after the last subdirectory name.
As with the DBDPATH keyword, the path must exist prior to running the LANDP family programs in a workstation with the shared file server.
Parameter values range from 62 to 4096 minus the size of the header that is appended. The header length is the length of all the defined keys (including the store-for-forwarding hidden key SFHIDKEY which is 8 bytes long), plus 36.
If the record size exceeds the number specified, it will be split into two or more segments.
Fields in a record can be selected as store-for-forwarding keys only if they are in character, unsigned ASCII numeric, or hexadecimal, and their length is fixed and less than 50 bytes.
The keys must be specified sequentially; for example, KEY05 cannot be specified if KEY04 was omitted. The first key (KEY01) is not defined. It is always the store-for-forwarding hidden key SFHIDKEY.
/* Vectors SFORWPRF and SFORWREC Examples */ SFORWPRF NAME=SFFPRF01, DATASETS=10, SEPSESS=N, MAXACC=200, SHFLPRF=SFPROF01, DBDPATH=C:\TELLER\SFORW\, SPLIT=1024, KEY02=REC1FL03, KEY03=REC2FL02 SFORWREC RECNAME=RECORD1 SFORWREC RECNAME=RECORD2
Defines the names of the records defined with the RECDEF vector which will be used as store-for-forwarding records.
At least one SFORWREC vector must be specified following a SFORWPRF vector.
Vector position | Follows SFORWPRF vector |
List of keywords | RECNAME |
Keywords relate to |
|
Vector format |
SFORWREC RECNAME=xxxxxxxx |
The parameter value is a field with up to eight alphanumeric characters, and must match the name given in keyword NAME of RECDEF vector.
If a record has a field with name AND or OR, the record cannot be selected as store-for-forwarding record.
/* Vectors SFORWPRF and SFORWREC Examples */ SFORWPRF NAME=SFFPRF01, DATASETS=10, SEPSESS=N, MAXACC=200, SHFLPRF=SFPROF01, DBDPATH=C:\TELLER\SFORW\, SPLIT=1024, KEY02=REC1FL03, KEY03=REC2FL02 SFORWREC RECNAME=RECORD1 SFORWREC RECNAME=RECORD2
Defines a shared-file database description (DBD) for the shared-file server. You can define up to 2048 DBDs.
For each shared-file server you create:
A shared-file profile is made up of all the SHFLDBD vectors which have the same identification in keyword SHFLPRF.
Define one SHFLDBD vector for each shared-file database that you want to use in a shared-file profile. A shared-file profile is defined or referenced in the SHFLPRF keyword of this vector.
Vector position | None. Can be followed by as many SHFLPCB vectors as needed. |
List of keywords | SHFLPRF, DBDNAME, RECNAME, COLLKEYS, PHYSREC, RECLEN, DBDPATH, DBDPATH6, DBFLNAME, KEY01 to KEY15 |
Keywords relate to |
|
Vector format |
SHFLDBD SHFLPRF=xxxxxxxx, DBDNAME=xxxxxxxx, [RECNAME=xxxxxxxx,] [COLLKEYS=x,] [PHYSREC=xxxxx,] [RECLEN=xxxxx,] DBDPATH=path, DBDPATH6=path, DBFLNAME=xxxxxxxx, [KEY01=( )], . . [KEY15=( )], [MINLOCKS=xxxxx,], [TLOCKS=xxxxx,] |
If you specify to use an alternate collating sequence table, you can define the table and reference the SHFLPRF name in the keyword NAME of the COLSQTBL vector.
Do not use names starting with FBEJ, since they are reserved for electronic journal DBDs. Those starting with FBSF are reserved for store-for-forwarding DBDs.
Applications refer to a DBD by using one of the related program control blocks (SHFLPCB vectors).
If specified, it must match the name given in a RECDEF vector, keyword NAME.
If no record structure is referenced, the characteristics of each key field must be defined (KEY01 to KEY15). Records with variable length fields cannot be used as a pattern.
The parameter values are:
The default is N.
This definition is valid for the third parameter of the key definitions (keywords KEYxx). If you select Y, you can define for each key whether the alternate collating sequence table will be used or not. If you use the default, the keys must also be defaulted to N.
The parameter value can be between 44 (minimum length) and the data record length specified in the RECLEN keyword.
Each physical record contains 5 control bytes. Thus, the number of user data bytes in a physical record will be the parameter value you specify in the PHYSREC keyword minus 5.
If you have specified to use a previously defined record structure (keyword RECNAME), the keyword does not apply.
If you have not specified it, the keyword is required. The parameter value can be between 44 (minimum length) and 26624 (maximum length).
The parameter value is the complete path (drive plus subdirectories). It must not exceed 56 characters, and contain at least 3 characters. Always include the final \ (backslash) after the last directory.
The path must exist prior to running the LANDP family programs in a workstation with the shared-file server.
The parameter value is the complete path including the subdirectories. It must not exceed 56 characters, and must be enclosed within single quotes ('). Each subdirectory name included in the path must have one character at least, and 30 characters at most. A backslash ('\') must not be present after the last subdirectory name.
As with the DBDPATH keyword, the path must exist prior to running the LANDP family programs in a workstation with the shared file server.
The parameter value is a field with up to eight characters for the file name. The file extension must be omitted. They will be DAT for data, or IXn (or Inn for those nn greater than or equal to 10) for key index files.
The keys must be specified sequentially; for example, KEY05 cannot be specified if KEY04 was omitted.
If keyword KEY01 is omitted, only direct or sequential access will be allowed for this DBD.
If you have not defined a record name in keyword RECNAME, all key parameters have to be specified. If RECNAME has been defined, the name, key class, and the use of alternate collating sequence table parameters must be specified. Key length and key offset, however, must not be specified.
If you have selected the default (N) for an alternate collating sequence table (keyword COLLKEYS), do not specify the third parameter of these keywords.
Each keyword has five parameters:
The parameter value is an alphanumeric field with up to eight characters.
The default is S.
The parameter does not apply to segmented keys. The parameter value S applies only to DBCS mode. The default is N.
If you plan to define a segmented key, specify value 0. To specify a non-segmented key field length, the parameter value can be between 1 and 255.
The parameter does not apply to segmented keys. The parameter value can be between 0 and 26623. The offset specified for a key plus the key length must not exceed the data record length.
/* Vectors SHFLDBD, SHFLPCB, and SHFLSGM Examples */ SHFLDBD SHFLPRF=SAMPLE1, DBDNAME=SAMP1DBD, COLLKEYS=N, RECLEN=100, DBDPATH=D:\, DBDPATH6='/var/opt/landp/acc', DBFLNAME=SAMP1FIL, KEY01=(F1P,P,,0), KEY02=(F1S,S,N,15,5) SHFLPCB PCBNAME=PCBS1 SHFLPCB PCBNAME=PCBSF1P, KEYFIELD=F1P SHFLPCB PCBNAME=PCBSF1S, KEYFIELD=F1S SHFLSGM SGMKEY=1, SGM01=(YEAR,D,2,34), SGM02=(MONTH,D,2,32), SGM03=(DAY,D,2,30)
/* Segmented keys using RECNAME */ RECDEF NAME=RECORDX, DELIMIT='\', DECSEP=',' RECFIELD NAME=REC1FL01, LENGTH=4, FORMAT=C, DESCRIPT='Transaction' RECFIELD NAME=FILLER1, LENGTH=2, FORMAT=C, DESCRIPT='2-byte filler' RECFIELD NAME=REC1FL02, LENGTH=10, FORMAT=N, DECIMALS=2, DESCRIPT='Amount' RECFIELD NAME=REC1FL03, LENGTH=8, FORMAT=N, DECIMALS=0 DESCRIPT='Client number' SHFLDBD SHFLPRF=SFSPRF, DBDNAME=DBD1, RECNAME=RECORDX, DBDPATH=E:\LANDP\DATA\, DBFLNAME=SAMP1FIL, KEY01=(SGMKEY,P,,0) SHFLPCB PCBNAME=PCBS1, KEYFIELD=SGMKEY SHFLSGM SGMKEY=1, SGM01=(REC1FL03,D), SGM02=(REC1FL01,D), SGM03=(REC1FL02,D)
Defines a program control block (PCB) to access a previously defined DBD. You can define up to 2048 PCBs.
At least one SHFLPCB vector has to be specified for each access to a key field you are going to define.
Vector position | Follows SHFLDBD vector |
List of keywords | PCBNAME, KEYFIELD |
Keywords relate to |
|
Vector format |
SHFLPCB PCBNAME=xxxxxxxx, [KEYFIELD=xxxxxxxx] |
The parameter value is an alphanumeric field with up to eight characters. It must be unique among the SHFLPCB vectors for this profile.
The parameter value is the name given in the first parameter of the KEYxx keyword in the SHFLDBD vector.
All key fields defined in the DBD must have a corresponding PCB, if you want the record to be accessed through this key.
If the key name is omitted, the PCB is used for sequential or direct access (not indexed).
Defines a segmented key. Specify one SHFLSGM vector for each segmented key specified through the KEYxx keywords in the SHFLDBD vector.
Vector position | Follows SHFLPCB vectors |
List of keywords | SGMKEY, SGM01 to SGM32 |
Keywords relate to |
|
Vector format |
SHFLSGM SGMKEY=xx, SGM01=( ), [SGM02=( ),] . . [SGM32=( )] |
The parameter value is an integer, in the range 1 through 15, that is equivalent to the last two digits of the KEYxx keyword of the SHFLDBD vector. A leading zero must not be present (for example, if KEY01 is a segmented key, the corresponding SGMKEY value is 1).
The total length of all the segments of a segmented key cannot exceed 255.
Each keyword has six parameters:
The parameter value is an alphanumeric field with up to eight characters.
The default is D.
If RECNAME was specified in the SHFLDBD vector, the parameter does not apply. The parameter value can be between 1 and 255.
If RECNAME was specified in the SHFLDBD vector, the parameter does not apply. The parameter value can be between 0 and 26623.
The offset specified for a segment plus the segment length must not exceed the data record length (RECLEN keyword in SHFLDBD vector).
The parameter value S applies only to DBCS mode. The default is N.
The parameter does not apply to data or indicator segments, and is required for locally or globally nullable segments. The parameter value is a string of two hexadecimal digits.
Defines a system manager server profile. One vector has to be defined for each system manager server profile you want to use.
There are two conditions that determine if record structures (defined in vector RECDEF) are used by the system manager server:
If the system manager server is to validate the LAN common data, the customization creates the LAN common data, based on the record structure of record FBSSGLUS. This record must be created before defining a system manager server profile.
If the system manager server is to validate the application data, a record structure named FBSSUSPR must exist and is used to build the application data. You must create this record structure before you define a system manager server profile.
The records FBSSGLUS and FBSSUSPR can have up to 1024 bytes and cannot contain variable length fields.
Vector position | None. If you define that system security will be used (SECLVL=Y), this vector must be followed by SMGRUSER vectors that define the authorization level of each user. |
List of keywords | NAME, LANID, LOGSUPP, SECLVL, AUTSYNC, COMDTVAL, APPDTVAL, LOGFSIZE, LOGRECL, LEVELS, LEVELF, LEVELR, LEVELOA, LEVELM, MSGOPRCV, ALRHNDLR |
Keywords relate to |
|
Vector format |
SMGRPRF NAME=xxxxxxxx, [LANID=xxxxxxxx,] [LOGSUPP=x,] [SECLVL=x,] [AUTSYNC=x,] [COMDTVAL=x,] [APPDTVAL=x,] [LOGFSIZE=xxx,] [LOGRECL=xxxx,] [LEVELS=x,] [LEVELF=x,] [LEVELR=x,] [LEVELOA=x,] [LEVELM=x,] [MSGOPRCV=x,] [ALRHNDLR=x] |
The parameter value is a string with up to eight alphanumeric characters plus the special characters $, %, #, and @. It must start with an alphabetical character, and must be unique among all SMGRPRF vectors.
The parameter value is a string with up to eight alphanumeric characters plus the special characters $, %, #, and @. The default is LANID.
It is strongly recommended that the value matches the PU name defined in VTAM for the workstation providing SNA services for alerts. For OS/2 and Windows NT workstations, it is also recommended that the value matches SNA local node name (control point alias) defined in the communications provider configuration file, so that the RUNCMD files sent from the host computer can reach the LANDP workgroup.
The LOG file is created and maintained by the LANDP System Manager server. It can only be deleted when the LANDP program is not running.
If you select Y for this keyword, LOGFSIZE and LOGRECL keywords must be specified, or the default values will be taken. If you select N, these keywords do not apply.
The parameter value can be either Y (Yes) or N (No). The default is Y.
If you select Y for this keyword, you must choose which authorization levels you want the system manager to control. You do this by using the LEVELx keywords of the same vector. You must also have a user assigned as system manager administrator, so the keyword LEVELOA must be Y.
If you select N, no LEVELx=Y can be specified.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter values range from 10 to 500KB. The default is 100.
The parameter values range from 128 to 1024 bytes of memory (that is 960 bytes of data). The default is 128.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
If you have defined your workgroup to use LEVELF security, a user must be signed on with LEVELF authority to use any applications from a LANDP workstation.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
If you select Y for this keyword, at least one LEVELA=Y user must be specified in the SMGRUSER vector.
The parameter value can be either Y (Yes) or N (No). The default is N.
Select Y if you want to designate one or more users of the applications to have access to the administrator and operator functions.
The parameter value is a string of up to eight alphanumeric characters.
If only one LEVELO=Y has been specified in the SMGRUSER vector, or if LOGSUPP=N has been defined, this keyword can be omitted. Otherwise, it must be specified.
The parameter value is a string of up to eight alphanumeric characters. The default is EHCALRH.
/* Vectors SMGRPRF and SMGRUSER Examples */ SMGRPRF NAME=SMGRPRF1, LANID=MYLAN, LOGSUPP=Y, SECLVL=Y, AUTSYNC=Y, COMDTVAL=Y, APPDTVAL=Y, LOGFSIZE=200, LOGRECL=512, LEVELS=Y, LEVELF=Y, LEVELR=N, LEVELOA=Y, LEVELM=Y, MSGOPRCV=BOBSM
SMGRUSER USERID=BOBSM, PASSWORD=BOBSMITH, NAME='Bob Smith', LANGUAGE=33, LEVELS=Y, LEVELR=N, LEVELF=Y, LEVELO=Y, LEVELA=Y, LEVELM=N, APPLVL='12345ABCDE'
Defines a system manager user profile inside a system manager server profile. One SMGRUSER vector has to be defined for each system manager user profile you want to specify.
If you have defined your workgroup to use LEVELF security, a user must be signed on with LEVELF authority to use any applications from a LANDP workstation.
If no SMGRUSER vector is specified when keyword SECLVL=Y in SMGRPRF vector, the defaults will be USERID=SYSTEM and PASSWORD=MANAGER.
Vector position | Follows SMGRPRF vector |
List of keywords | USERID, PASSWORD, PSWCRYPT, NAME, LANGUAGE, LEVELS, LEVELR, LEVELF, LEVELO, LEVELA, LEVELM, APPLVL |
Keywords relate to |
|
Vector format |
SMGRUSER USERID=xxxxxxxx, PASSWORD=xxxxxxxx, [PSWCRYPT=password encrypted,] [NAME=' ',] [LANGUAGE=xx,] [LEVELS=x,] [LEVELR=x,] [LEVELF=x,] [LEVELO=x,] [LEVELA=x,] [LEVELM=x,] [APPLVL=' '] |
The parameter value is a string with up to eight alphanumeric characters plus the special characters $, %, #, and @. It must be unique within a system manager profile.
The parameter value is a string with four to eight alphanumeric characters plus the special characters $, %, #, and @.
This is a security provision. No changes can be made to the encrypted password. In order to change an user password in an already generated profile, you have to substitute the PSWCRYPT keyword by a PASSWORD keyword with the new information.
The parameter value is an alphanumeric field with a maximum of 30 characters. Since blanks are allowed in this field, it must be enclosed within quotes. If quotes are part of the name, they must be doubled.
The parameter value is a numeric field with two characters, or blanks. For example, you can define language code 01 for Italian and assign this code to various users.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value can be either Y (Yes) or N (No). The default is N.
If you want an user to receive the operator messages, you must define at least one user with authorization level O.
The parameter value can be either Y (Yes) or N (No). The default is Y.
The parameter value can be either Y (Yes) or N (No). The default is N.
The parameter value is a field of up to 10 characters.
/* Vectors SMGRPRF and SMGRUSER Examples */ SMGRPRF NAME=SMGRPRF1, LANID=MYLAN, LOGSUPP=Y, SECLVL=Y, AUTSYNC=Y, COMDTVAL=Y, APPDTVAL=Y, LOGFSIZE=200, LOGRECL=512, LEVELS=Y, LEVELF=Y, LEVELR=N, LEVELOA=Y, LEVELM=Y, MSGOPRCV=BOBSM SMGRUSER USERID=BOBSM, PASSWORD=BOBSMITH, NAME='Bob Smith', LANGUAGE=33, LEVELS=Y, LEVELR=N, LEVELF=Y, LEVELO=Y, LEVELA=Y, LEVELM=N, APPLVL='12345ABCDE'
Defines a list of non-LANDP files that are to be distributed with the LANDP runtime files. These files can be application programs, additional device drivers, bitmaps, or any other files required in the LANDP workstation.
This vector can define two types of pack:
Vector position | None |
List of keywords | PACKNAME, FILENAME, FILEPATH |
Keywords relate to | |
Vector format |
SOFTPACK PACKNAME=xxxxxxxx, FILENAME=xxxxxxxx[.xxx], [FILEPATH=path] |
If FILENAME specifies a predefined pack of files, this keyword must be omitted.
/* Sample of packs of files */ SOFTPACK PACKNAME=PACKO1, FILENAME=FILE101.EXE, FILEPATH=C:\SUBDIR1\SUBDIR2\ SOFTPACK PACKNAME=PACKO1, FILENAME=FILE102.EXE, FILEPATH=C:\SUBDIR1\SUBDIR2\ SOFTPACK PACKNAME=PACKO2, FILENAME=FILE201.EXE, FILEPATH=C:\SUBDIR1\SUBDIR2\ SOFTPACK PACKNAME=PACKO2, FILENAME=FILE202.EXE, FILEPATH=C:\SUBDIR1\SUBDIR2\ /* Sample of pack of packs */ SOFTPACK PACKNAME=GPACKO1, FILENAME=PACK01 SOFTPACK PACKNAME=GPACKO1, FILENAME=PACK02
Defines an ASCII to EBCDIC or an EBCDIC to ASCII translation table. One separate vector has to be specified for each table you are going to define.
For each type of table, a default table will be created by CREATE. The vectors for these default tables can be generated using GENSPEC.
Vector position | None |
List of keywords | TYPE, EXTEN, DATA0X to DATAFX |
Keywords relate to |
|
Vector format |
XLATETBL TYPE=xxxx, EXTEN=xxx, DATA0X=( ), : DATAFX=( ) |
The parameter values can be one of the following:
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all translation tables of the same type.
DATA0X must contain the translation information for digits '00' to '0F', DATA1X for '10' to '1F', and so on.
For translation tables with the type EA3270, EA47X2, EA3287, and EABIWP, the keywords DATA0X, DATA1X, DATA2X, and DATA3X must not be specified.
/* Vector XLATETBL (TYPE=AE3270) Default Example */ XLATETBL TYPE=AE3270, EXTEN=KBD, DATA0X=(00,01,02,03,04,05,06,07,08,09,0A,0B,0C,0D,0E,0F), DATA1X=(10,11,12,13,14,15,16,17,18,19,1A,1B,1C,1D,1E,1F), DATA2X=(40,4F,7F,7B,5B,6C,50,7D,4D,5D,5C,4E,6B,60,4B,61), DATA3X=(F0,F1,F2,F3,F4,F5,F6,F7,F8,F9,7A,5E,4C,7E,6E,6F), DATA4X=(7C,C1,C2,C3,C4,C5,C6,C7,C8,C9,D1,D2,D3,D4,D5,D6), DATA5X=(D7,D8,D9,E2,E3,E4,E5,E6,E7,E8,E9,4A,E0,5A,5F,6D), DATA6X=(79,81,82,83,84,85,86,87,88,89,91,92,93,94,95,96), DATA7X=(97,98,99,A2,A3,A4,A5,A6,A7,A8,A9,C0,BB,D0,A1,41), DATA8X=(68,DC,51,42,43,44,47,48,52,53,54,57,56,58,63,67), DATA9X=(71,9C,9E,CB,CC,CD,DB,DD,DF,EC,FC,70,B1,80,41,B4), DATAAX=(45,55,CE,DE,49,69,9A,9B,AB,AF,BA,B8,B7,AA,8A,8B), DATABX=(41,41,41,41,41,65,62,64,41,41,41,41,41,B0,B2,41), DATACX=(41,41,41,41,41,41,46,66,41,41,41,41,41,41,41,9F), DATADX=(8C,AC,72,73,74,9F,75,76,77,41,41,41,41,6A,78,41), DATAEX=(EE,59,EB,ED,CF,EF,A0,AE,8E,FE,FB,FD,8D,AD,BC,BE), DATAFX=(CA,8F,BF,89,B6,B5,41,9D,90,BD,B3,41,FA,EA,41,41)
Defines an ASCII to EBCDIC and an EBCDIC to ASCII translation table for the XLATE function of the PC/Integrator.
One vector has to be specified for each table you want to use in your workgroups. All the parameters for this vector have to be specified, there is no default for them.
Vector position | None |
List of keywords | EXTEN, EADATA0X to EADATAFX, AEDATA0X to AEDATAFX |
Keywords relate to |
|
Vector format |
XLAT2TBL EXTEN=xxx, EADATA0X=( ), : EADATAFX=( ), AEDATA0X=( ), : AEDATAFX=( ) |
The parameter value is a 3-character alphanumeric string, and may contain the special characters #, $, %, and @. It must be unique among all translation tables.
EADATA0X must contain the translation information for digit '00' to '0F', EADATA1X for '10' to '1F', and so on.
AEDATA0X must contain the translation information for digit '00' to '0F', AEDATA1X for '10' to '1F', and so on.
/* Vector XLAT2TBL Example */ XLAT2TBL EXTEN=TB1, EADATA0X=(00,01,02,03,37,2D,2E,2F,16,05,25,0B,0C,0D,0E,0F), EADATA1X=(10,11,12,13,3C,3D,32,26,18,19,3F,27,1C,1D,1E,1F), EADATA2X=(40,4F,7F,7B,5B,6C,50,7D,4D,5D,5C,4E,6B,60,4B,61), EADATA3X=(F0,F1,F2,F3,F4,F5,F6,F7,F8,F9,7A,5E,4C,7E,6E,6F), EADATA4X=(7C,C1,C2,C3,C4,C5,C6,C7,C8,C9,D1,D2,D3,D4,D5,D6), EADATA5X=(D7,D8,D9,E2,E3,E4,E5,E6,E7,E8,E9,4A,E0,5A,5F,6D), EADATA6X=(79,81,82,83,84,85,86,87,88,89,91,92,93,94,95,96), EADATA7X=(97,98,99,A2,A3,A4,A5,A6,A7,A8,A9,C0,6A,D0,A1,07), EADATA8X=(20,21,22,23,24,15,06,17,28,29,2A,2B,2C,09,0A,1B), EADATA9X=(30,31,1A,33,34,35,36,08,38,39,3A,3B,04,14,3E,E1), EADATAAX=(41,42,43,44,45,46,47,48,49,51,52,53,54,55,56,57), EADATABX=(58,59,62,63,64,65,66,67,68,69,70,71,72,73,74,75), EADATACX=(76,77,78,80,8A,8B,8C,8D,8E,8F,90,9A,9B,9C,9D,9E), EADATADX=(9F,A0,AA,AB,AC,AD,AE,AF,B0,B1,B2,B3,B4,B5,B6,B7), EADATAEX=(B8,B9,BA,BB,BC,BD,BE,BF,CA,CB,CC,CD,CE,CF,DA,DB), EADATAFX=(DC,DD,DE,DF,EA,EB,EC,ED,EE,EF,FA,FB,FC,FD,FE,FF), AEDATA0X=(00,01,02,03,9C,09,86,7F,97,8D,8E,0B,0C,0D,0E,0F), AEDATA1X=(10,11,12,13,9D,85,08,87,18,19,92,8F,1C,1D,1E,1F), AEDATA2X=(80,81,82,83,84,0A,17,1B,88,89,8A,8B,8C,05,06,07), AEDATA3X=(90,91,16,93,94,95,96,04,98,99,9A,9B,14,15,9E,1A), AEDATA4X=(20,A0,A1,A2,A3,A4,A5,A6,A7,A8,5B,2E,3C,28,2B,21), AEDATA5X=(26,A9,AA,AB,AC,AD,AE,AF,B0,B1,5D,24,2A,29,3B,5E), AEDATA6X=(2D,2F,B2,B3,B4,B5,B6,B7,B8,B9,7C,2C,25,5F,3E,3F), AEDATA7X=(BA,BB,BC,BD,BE,BF,C0,C1,C2,60,3A,23,40,27,3D,22), AEDATA8X=(C3,61,62,63,64,65,66,67,68,69,C4,C5,C6,C7,C8,C9), AEDATA9X=(CA,6A,6B,6C,6D,6E,6F,70,71,72,CB,CC,CD,CE,CF,D0), AEDATAAX=(D1,7E,73,74,75,76,77,78,79,7A,D2,D3,D4,D5,D6,D7), AEDATABX=(D8,D9,DA,DB,DC,DD,DE,DF,E0,E1,E2,E3,E4,E5,E6,E7), AEDATACX=(7B,41,42,43,44,45,46,47,48,49,E8,E9,EA,EB,EC,ED), AEDATADX=(7D,4A,4B,4C,4D,4E,4F,50,51,52,EE,EF,F0,F1,F2,F3), AEDATAEX=(5C,9F,53,54,55,56,57,58,59,5A,F4,F5,F6,F7,F8,F9), AEDATAFX=(30,31,32,33,34,35,36,37,38,39,FA,FB,FC,FD,FE,FF)
Defines an entry in a X.25 directory table. These tables contain communications provider directories and their associated X.25 subscriber numbers. A table can contain up to 100 entries.
The customization program creates an ASCII run-time file, named SNAX25D.CFG, which contains that information.
One vector has to be specified for each entry in the table. All the parameters for this vector have to be specified. There is no default for them.
Vector position | None |
List of keywords | TBLNAME, DIRNAME, SUBSNUMB |
Keywords relate to |
|
Vector format |
X25DIR TBLNAME=xxxxxxxx, DIRNAME=xxxxxxxx, SUBSNUMB=xxxxxxxxxxxxxxx |
The parameter value is a string of up to eight alphanumeric characters, and must be unique among all X.25 directory tables.
The parameter value is a string of up to eight alphanumeric characters, and must be unique among all the entries in the X.25 directory table.
The parameter value is a string of up to 15 digits, and must be unique among all the entries in the X.25 directory table.
/* Vector X25DIR Example */ X25DIR TBLNAME=X25TBL01, DIRNAME=PARTNER1, SUBSNUMB=123456789012345
|
This appendix provides information about:
|
For information on how to store customization data in specification files, refer to Customization data structure, especially if you plan to use embedded files (see page "Embedded specification files") or partial files (see page "Partial specification files").
The appendix also explains how to use models to define your workgroup configurations.
The following graphic shows the vectors in the .SPC files, and the references that can be specified to use the model configurations. The references are specified at keyword level.
Before you start creating and editing configuration vectors, consider the following:
The EDITSPEC program is used to edit specification files.
You can apply this procedure to the LANCONF.SPC or MODELS.SPC files, and display and modify the configuration vectors.
If you want to display online information about this procedure, from the EHCCUS directory, enter:
EDITSPC ?
To start the procedure for a workgroup configuration file (LANCONF.SPC), from the EHCCUS directory enter:
EDITSPC xxxxxxxx LAN
where xxxxxxxx is the name of the subdirectory in the EHCCUS directory where the LANCONF.SPC file is located.
If the file does not exist, the procedure creates a subdirectory with the name you provide, and an empty file named LANCONF.SPC located in that subdirectory.
If the subdirectory where the LANCONF.SPC file is located is not in the EHCCUS directory, but in an other directory at the same level, you have to specify also this directory. In this case, the command to enter is:
EDITSPC yyyyyyyy xxxxxxxx LAN
where yyyyyyyy is the name of a directory at the same level as EHCCUS.
If the file or the directories do not exist, the procedure creates the directories with the names you provide, and an empty file named LANCONF.SPC located in that path.
To start the procedure for the model configuration file (MODELS.SPC), from the EHCCUS directory, enter:
EDITSPC MODELS
If you use the OS/2 Enhanced Editor with the LANDP customization editing tool, the LANDP choice is listed in the action bar of the editor window. For information about that tool, select the View doc option in the pull-down that appears when you choose LANDP.
The configuration vectors are generated either in the LANCONF.SPC files, or in the MODELS.SPC file, located in the EHCCUS directory. The order in which the vectors appear in the files is not relevant.
To start the procedure for the workgroup configuration vectors, from the EHCCUS directory, enter:
GENSPEC LAN
To start the procedure for the model configuration vectors, from the EHCCUS directory, enter:
GENSPEC MODELS
For further information on that procedure, refer to Generating data.
To edit workgroup configuration data:
The LANCONF vector can contain actual definitions, and a reference to a LANMODEL vector.
The LWSCONF vector can contain actual definitions, a reference to a WSMODEL vector, and some references to SVRMODEL vectors.
When editing a configuration vector, if you refer to a model configuration vector, the definitions in the model configuration vector become the default parameter values for the configuration vector you are editing. To change some values, include the corresponding keywords in the vector and assign to them the new parameter values. Note that you can include keywords that are not included in the model configuration vector.
When defining a workgroup configuration and referring to a workgroup model
configuration, you may have to do some of the tasks in the following
table. The table shows the tasks and the actions you have to
take.
Task | Action |
---|---|
Delete a workstation from a workgroup model configuration |
|
Add a workstation to a workgroup model configuration |
|
Delete a server from a workstation model configuration |
|
Add a server to a workstation model configuration |
|
Delete access to the services provided by a functional area from a workstation model configuration |
|
Delete access to the services provided by a functional area to a workstation model configuration |
|
When you generate the LANCONF.SPC file through the generation procedure, using the customization data stored in the internal repository, the order in which the vectors appear in the file may be different from the order in which you wrote them.
This section provides information about each workgroup configuration vector, including examples.
Contains workgroup information, and must be the first vector in the workgroup configuration file. An example for this vector is provided under LANCONF vector examples.
Vector position | First vector in the LANCONF.SPC file. It can be followed by up to 250 LWSCONF vectors. |
List of keywords |
GROUP, NAME MODEL DEFAULTS, LANADAPT, LANGUAGE, RPLOAD, SUFFIX, XPORT, TCPPORT, ADAPTNUM,
NETBUFF, WSNAMES, PARLIP, NWSIDDUP
|
Keywords relate to |
|
Vector format |
LANCONF [GROUP=xxxxxxxx,] NAME=xxxxxxxx, [MODEL=xxxxxxxx,] [DEFAULTS=xxxxxxxx,] [LANADAPT=x,] [LANGUAGE=xxx,] [RPLOAD=x,] [SUFFIX=x,] [XPORT=x,] [TCPPORT=xxxxx,] [ADAPTNUM=xxx,] [NETBUFF=xx,] [NWSIDDUP=x,] [PARLIP=x,] WSNAMES=( ) |
The keywords in the first line in the list identify the workgroup configuration. The MODEL keyword refers to a workgroup model configuration. Other keywords define the workgroup configuration.
The combination of the name assigned in the GROUP keyword and the name assigned in the NAME keyword must be unique for the whole installation.
The parameter value is a name of up to 8 alphanumeric characters. The default is EHCCUS.
The combination of the name assigned in the GROUP keyword and the name assigned in the NAME keyword must be unique for the whole installation.
The parameter value is a name of up to 8 alphanumeric characters.
The parameter value must match the value assigned in the MODNAME keyword in a LANMODEL vector.
The parameter value must match the value assigned in the NAME keyword in a DEFAULTS vector. The default is GENERAL.
The parameter value can be:
The default is T. LANDP always uses the primary adapter, not the alternate one.
The parameter value can be:
The default is 001. When working in DBCS mode, only English and Simplified Chinese are supported. Note that you can only specify 086 if the DBCSCTRY entry on the DEFAULTS vector is also set to 086.
The parameter value can be Y, to use virtual volume remote program load, or N, not to use it. The default is N.
If the suffix is to be used, the workgroup name must be unique for each LANDP workgroup in the same network.
The suffix enables you to have workstations with the same name in different LANDP workgroups, which belong to the same network. This suffix can be changed at run-time using the LAN variable run-time parameters program (VARPARM.EXE).
The parameter value can be Y, to add the suffix, or N, not to add it. The default is N.
You can also specify the transport protocol at workstation level using the XPORT keyword in the LWSCONF vector. The value specified at the workstation level overrides the value specified at workgroup level.
The parameter value can be:
The default is N.
For a DOS workstation:
For non-DOS workstations, P and T values both have the same effect as T for a DOS workstation.
The parameter value can be in the range 1024 through 65535. The default is 52699.
You can also specify the adapter number at workstation level, through the ADAPTNUM keyword in the LWSCONF vector. The value specified at workstation level overrides the value specified at workgroup level.
The parameter value ranges from 0 to 255. The default is provided at workstation level.
For OS/2 and Windows workstations, you can also specify parameter values in the form: (x,x...), where x can range from 0 to 255, but where no number is repeated. This enables you to specify a range of adapters, thus supporting up to four adapters in a single workstation.
You can also specify the size of the NetBIOS buffer at workstation level, through the NETBUFF keyword in the LWSCONF vector. The value specified at workstation level overrides the value specified at workgroup level.
The parameter value ranges from 1 to 56. The default is provided at workstation level.
Each parameter is the name of a workstation in the workgroup configuration. The parameter value is a name of up to 2 alphanumeric characters. The value must match the value assigned in the NAME keyword in the LWSCONF vector that contains information about the workstation.
The parameter values are Y (to suppress duplicate WSID return codes) and N (to display these return codes). The default is N.
All WSIDs across all workgroups must be unique if you distribute your LANDP software by using NetView/DM. In this case, you must take action on the return codes issued by VALSPEC which indicate that a duplicate WSID has been issued. The first six characters of each workgroup name (NAME) must be unique. The two-character workstation name (WSNAME) is appended to create the eight-character WSID. Avoid the return codes by ensuring that the first six characters of all workgroup names are unique.
If you do not distribute your LANDP software by using NetView/DM, you can suppress return codes by setting the appropriate VALSPEC parameter. Be aware, however, that this also suppresses other return codes that you might need to respond to. Alternatively, set the NWSIDDUP parameter to Y to suppress return codes for duplicate WSIDs.
You can also specify these parameters at workstation level, through the PARLIP keyword in the LWSCONF vector. The value specified at workstation level overrides the value specified at workgroup level.
You can specify up to 3 parameters:
This parameter specifies whether availability probe datagrams will be sent at regular intervals when a session has no normal traffic.
The parameter value can be Y, to send availability probe datagrams, or N, not to send them. The default is Y.
This parameter specifies the storage, in bytes, to be allocated for the retransmission table.
This table is used by the LANDP Internet Protocol to save information about datagrams sent, in case they should be retransmitted. The information is deleted when the receiver acknowledges reception.
The parameter applies only to DOS workstations. The parameter value ranges from 256 to 65000.
The default is defined using the following formula:
Default value = 910 * ((n * 40) / (n + 34))
where n is the number of related workstations.
This parameter specifies whether checking for related workstations with undefined IP addresses will be carried out.
The parameter value can be Y or N. Y checks that all LANDP Internet Protocol addresses are defined; processing stops if any undefined addresses are found. N allows some addresses to be undefined at this time; processing continues. The default is Y.
/* Following is the EXAMPLE 1, which corresponds to keyword */ /* specifications for a workgroup that uses NetBIOS as transport */ /* protocol. */ LANCONF GROUP=EHCCUS, NAME=LAN1, WSNAMES=(AA,BB,CC)
/* Following is the EXAMPLE 2, which corresponds to keyword */ /* specifications for a workgroup that uses TCP/IP as transport */ /* protocol. */ LANCONF GROUP=EHCCUS, NAME=TCPIP1, WSNAMES=(AA,BB), DEFAULTS=GENERAL, /* Transport protocol through workgroup is TCP/IP */ XPORT=T, /* TCP/IP port used by LANDP is port 52699 */ TCPPORT=52699, SUFFIX=Y
Contains information about a particular workstation in the workgroup configuration, including functional area definitions. The keywords that define the functional areas are explained in the corresponding sections. Those sections provide examples of the keyword definitions that can be included in the LWSCONF vectors for the respective functional areas.
Vector position | None. Follows a LANCONF vector. There can be up to 250 LWSCONF vectors in the same LANCONF.SPC file. |
List of keywords |
NAME WSID, MODEL TYPE, SYSLVL, PRODLVL, SOFTPACK, FRAME, RPLOAD, POOLSIZE, XPORT, PARLIP,
PARLIPEX, LANDPDCE, ADAPTNUM, NETBUFF, DBCSXLAT, PARWIN, SBC, SERVER, CLIENT,
PARxxxxx, SESxxxxx
|
Keywords relate to |
|
Vector format |
LWSCONF NAME=xx, [WSID=xxxxxxxx,] [MODEL=xxxxxxxx,] [TYPE=( ),] [SYSLVL=x,] [PRODLVL=xxx,] [SOFTPACK=xxxxxxxx,] [FRAME=xxxx,] [RPLOAD=x,] [POOLSIZE=xxx,] [XPORT=x,] [PARLIP=( ),] [PARLIPEX=( ),] [LANDPDCE=x,] [ADAPTNUM=xxx,] [NETBUFF=xx,] [DBCSXLAT=x,] [PARWIN=xx,] [SBC=( ),] [SERVER=( ),] [CLIENT=( ),] [PARxxxxx=( ),] [SESxxxxx=( )] |
The NAME keyword identifies the workstation in the workgroup configuration. The MODEL keyword refers to a workstation model configuration.
Next keywords define the workstation in the workgroup configuration. The PARxxxxx and SESxxxxxx keywords specify the parameters used to define some functional areas.
The parameter value is a name of up to 2 alphanumeric characters. The value is used as the name of the workstation when you need to specify that name in other keywords, for example, because the services provided by this workstation are required in the configuration you are defining.
See the NWSIDDUP parameter of LANCONF for details of how to avoid receiving return codes about duplicate workstation identifiers.
The parameter value is a name of up to 8 alphanumeric characters, and should be unique across all workstations and workgroups. The default is the first 6 characters of the workgroup name, concatenated with the workstation name.
To point to a workstation model configuration, the parameter value must match the value assigned in the MODNAME keyword in a WSMODEL vector. To delete a workstation from a workgroup model configuration, the parameter value must be DELETE.
You can specify up to 2 parameters:
The parameter value can be:
The default is DOS.
This parameter specifies whether Windows 3.1/3.11 support is to be used. It applies only to DOS or OS/2 workstations.
To use Windows 3.1 support, the parameter value must be WIN. To use Windows for Workgroups support, the parameter value must be WFW. This specifies that no additional LAN support needs to be added for this workstation.
The parameter is optional. It is not supported for TYPE=NT (Windows) and TYPE=LINUX.
If it is specified, the parameter value must be 7, meaning DOS V.7.x.
The parameter value can be:
LANDP Version 6.0 for OS/2, if you define a TYPE=OS/2 workstation.
LANDP Version 6.0 for Windows, if you define a TYPE=NT workstation.
LANDP Version 6.0 for Linux, if you define a TYPE=LINUX workstation.
LANDP Version 5.0 for OS/2, if you define a TYPE=OS/2 workstation.
LANDP Version 5.0 for Windows NT, if you define a TYPE=NT workstation.
LANDP Version 4.0 for OS/2, if you define a TYPE=OS/2 workstation.
LANDP Version 4.0 for Windows NT, if you define a TYPE=NT workstation.
LANDP Version 3.0 for OS/2, if you define a TYPE=OS/2 workstation.
LANDP Version 2.0 for OS/2, if you define a TYPE=OS/2 workstation.
LANDP Version 1.0 for OS/2, if you define a TYPE=OS/2 workstation.
The default is the latest LANDP product version for the operating system installed in the workstation you define.
The parameter value ranges from C000 to E000, in increments of 400(hex). The default is C000.
The parameter value can be Y, to use virtual volume remote program load, or N, not to use it. The default is N.
The parameter value ranges from 7 to 512. The value is limited by the available memory.
The default is [1.25 x n], where n is the number of workstations that receive services from the workstation you are defining, or provide services to it.
For workstations that provide or receive shared DOS directory services, the customization program recalculates the default accordingly.
You can also specify the transport protocol at workgroup level using the XPORT keyword in the LANCONF vector. The value specified at the workstation level overrides the value specified at workgroup level.
The parameter values can be:
The default is the value specified on the XPORT keyword of the LANCONF vector.
Related workstations, where one is configured as a client of the other, must have at least one transport in common.
You can specify up to 3 parameters:
This parameter specifies whether availability probe datagrams will be sent at regular intervals when a session has no normal traffic.
The parameter value can be Y, to send availability probe datagrams, or N, not to send them. The default is Y.
This parameter specifies the storage, in bytes, to be allocated for the retransmission table.
This table is used by the LANDP Internet Protocol to save information about datagrams sent, in case they should be retransmitted. The information is deleted when the receiver acknowledges reception.
The parameter applies only to DOS workstations. The parameter value ranges from 256 to 65000.
The default is defined using the following formula:
Default value = 910 * ((n * 40) / (n + 34))
where n is the number of related workstations.
This parameter specifies whether checking for related workstations with undefined IP addresses will be carried out.
The parameter value can be Y or N. Y checks that all LANDP Internet Protocol addresses are defined; processing stops if any undefined addresses are found. N allows some addresses to be undefined at this time; processing continues. The default is Y.
You can specify one parameter:
This keyword applies only if the defaulted or specified value of the transport protocol in the XPORT keyword is NetBIOS.
You can also specify the adapter number at workgroup level, through the ADAPTNUM keyword in the LANCONF vector. The value specified at workstation level overrides the value specified at workgroup level.
The parameter value ranges from 0 to 255. The default is 0, or the value specified at workgroup level.
For OS/2 and Windows workstations, you can also specify parameter values in the form: (x,x...), where x can range from 0 to 255, but where no number is repeated. This enables you to specify a range of adapters, thus supporting up to four adapters in a single workstation.
You can also specify the size of the NetBIOS buffer at workgroup level, through the NETBUFF keywork in the LANCONF vector. The value specified at workstation level overrides the value specified at workgroup level.
The parameter value ranges from 1 to 56. The default is 4, or the value specified at workgroup level.
The parameter value can be:
The default is N.
The parameter value ranges from 4 to 56. The customization data provides no default.
Use of this keyword facilitates the generation of the appropriate lists of files for the SBC server directories. See also Distributing software.
A workgroup might include one or more SBC server workstations.
All workstations in an SBC server/client group must be running on the same operating system (either all OS/2 or all Windows). Also, all workstations in an SBC server/client group must be running on the same version of LANDP. This avoids the possibility of incompatible versions of files being grouped on the SBC server.
You can specify up to two parameters:
You can specify up to 4 parameters:
The parameter is required. The parameter value is a string of up to 8 alphanumeric characters.
Refer to the table in Vectors - a quick reference for the values (string in parenthesis) corresponding to the functional areas.
The following servers require that the server suffix (##) is substituted by the corresponding value to completely identify the server:
The following servers require a suffix to identify the session to be used:
Note that BIWP and LDA 7 program need the suffix only when they are installed in a DOS workstation.
If the following servers are to be run in either an OS/2 or a Windows VDM, the server names to be specified are:
where x is a suffix that identifies the session.
To specify user servers, the parameter value must be the value specified in the NAME keyword of the DEFSERV vector. Those vectors are located in the COMMON.SPC file. See Appendix B, User servers.
The parameter is optional. The parameter value is a string of up to 8 alphanumeric characters, and must match the value assigned in the MODNAME keyword in a SVRMODEL vector.
To delete a server from a workstation model, the parameter value must be DELETE.
The parameter applies only to DOS workstations. It is optional. The parameter value can be:
The default is N.
This parameter specifies a string that will be added to the loading statement of the server.
The parameter is optional. The parameter value is a string of up to 40 characters, enclosed between quotes.
You can specify up to 3 parameters:
The following resources are always local, and do not require this parameter:
In any other case, the parameter is required. The parameter value is a string of up to 8 alphanumeric characters.
Refer to the table in Vectors - a quick reference for the values (string in parenthesis) corresponding to the functional areas.
The following servers require that the server suffix (##) is substituted by the corresponding value to completely identify the server:
In the following resources, the suffix identifies the session used by the server:
To specify user servers, the parameter value must be the value specified in the NAME keyword of the DEFSERV vector. Those vectors are located in the COMMON.SPC file. See Appendix B, User servers.
A modified SNA interface that allows for more than 30 user sessions per workstation is available when the SNA services are provided from an OS/2 or Windows workstation. When using this interface, the session identifier may be any two ASCII characters. To customize for the modified interface, use a server name of just SNA, instead of SNA followed by the session identifier, in the CLIENT keyword of the LWSCONF vector. Only one CLIENT=(SNA,xx) keyword is required, no matter how many sessions are to be used
The parameter is required. The parameter value must match the value assigned in the NAME keyword in the LWSCONF vector corresponding to the workstation where the server is loaded.
When you define a workstation model configuration, and some services are locally provided, you can specify &W as the name of the workstation where the corresponding server is loaded. When you assign the &W value in the CLIENT keyword in a WSMODEL vector, the customization program substitutes the value &W for the name of the workstation that uses the model.
The parameter applies only to LANDP for OS/2, LANDP for Windows, and LANDP for Linux workstations. The parameter is optional. The parameter value is a string of up to 8 alphanumeric characters. It can be neither the name of a resource nor the alias of another resource used in the workstation.
This parameter is also used to delete a client from a workstation model. The parameter value must be DELETE, and is applicable to any type of workstation in this case.
The PARxxxxxx keywords are used to specify all the parameters for those servers that are loaded only once in the workstation, and handle a single resource. For servers that are loaded more than once in the workstation or handle multiple resources, the PARxxxxx keywords only specify the common information. In this case, the information specific for each particular server or resource is specified using the SESxxxxxx keywords.
The PARxxxxx and SESxxxxx keywords corresponding to all the functional areas are explained in the following sections.
/* Following is EXAMPLE 1, which corresponds to keyword */ /* specifications for a workstation that runs DOS. */ LWSCONF NAME=D1, TYPE=DOS, PRODLVL=L60, SOFTPACK=SHDIRC, FRAME=C000, SERVER=DDT, SERVER=(EMU32701,,Y), PAR&3270=(N,N), SES&3270=(D1,1,P1,,AT1,DI1,KBD), SERVER=(EMU32702,,Y), SES&3270=(D1,2,P1,,AT1,DIS,KBD,HOST2,43,80), SERVER=(EMU32703,,Y), SES&3270=(O1,3,P1,,ATR,DIS,KBD,HOST3,27,132), SERVER=(EMU32704,,Y), SES&3270=(O1,4,P2,,ATR,DIS,KBD,HOST4), SERVER=(OPER,,Y), SERVER=SDLC, PAR&SDLC=(20,01,N,Y,N,03D,01234,TURN,65,C1C1C1C1C1), SERVER=(SNA##,,Y), PAR&SNA=(APPL,SRV,,,LUPOOL1,Y) /* Following is EXAMPLE 2, which corresponds to keyword */ /* specifications for a workstation that runs OS/2. */ LWSCONF NAME=O1, TYPE=(OS/2), PRODLVL=L60, SERVER=SNA##, PAR&SNA=(APPL,SRV), SERVER=(EHCVDMGR,,N), SERVER=EMU32701, PAR&3270=(N,Y), SES&3270=(O1,1,,,ATR,DIS,KBD,HOST1), SERVER=EMU32702, SES&3270=(O1,2,,,ATR,DIS,KBD,HOST2)
The Banking Interactive Workstation Program (BIWP) requires one PAR&BIWP keyword.
If BIWP will run in an OS/2 or a Windows VDM, the name of the server in the SERVER keyword must be VBIWPx instead of BIWPx. Additionally, the keyword to be included in the LWSCONF, WSMODEL, or SVRMODEL vector, must be PAR&VBIW instead of PAR&BIWP. The parameters you can specify in a PAR&VBIW keyword are the same as those that can be specified in a PAR&BIWP keyword.
You can specify up to 19 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
When BIWP is installed in a DOS workstation or is used in an OS/2 or Windows VDM, the parameter is required. The parameter value ranges from 1 to 5, and must be unique for the workstation where BIWP is installed.
The parameter must be omitted when BIWP is installed in a OS/2 workstation. The parameter value is defaulted to 1.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only.
The parameter value can be:
This parameter defines how the cursor will work on the screen.
The parameter is optional. The parameter value can be:
The default is R.
This parameter defines how a read operation will be posted when the input segment is full and a character is typed.
The parameter is optional. The parameter value can be Y, to post the read operation complete without status, or N, to post it with a wrong length status. The default is Y.
The parameter is optional. The parameter value is a hexadecimal number of two digits. The default is FF.
The parameter is optional. The parameter value can be Y, to make the alarm sound when the indicator 1 of the BIWP display is turned on, or N, not to make it sound. The default is N.
The parameter is optional. The parameter value can be Y, to make the alarm sound when the indicator 2 of the BIWP display is turned on, or N, not to make it sound. The default is N.
The parameter is optional. The parameter value can be Y, to make the alarm sound when the indicator 3 of the BIWP display is turned on, or N, not to make it sound. The default is N.
The parameter is optional. The parameter value can be Y, to make the alarm sound when the SYSTEM indicator of the BIWP display is turned on, or N, not to make it sound. The default is N.
The parameter applies only when BIWP uses IBM 4717 MSR/E. It is optional.
The parameter value can be Y, to make the alarm sound when MSR/E is ready to encode, or N, not to make it sound. The default is N.
This parameter identifies the color attributes table used for the workstation display.
The parameter value is a string of three alphanumeric characters, which is the identifier of the color attributes table. It must match the value assigned in the EXTEN keyword in a DISPLATT vector with TYPE = BIWP.
This parameter identifies the table that is used to translate from 4700 system EBCDIC to personal computer system ASCII, when receiving from the 4700 system.
The parameter value is a string of three alphanumeric characters, which is the identifier of the translation table. It must match the value assigned in the EXTEN keyword in a XLATETBL vector with TYPE = EABIWP.
This parameter identifies the translation table used for the workstation keyboard.
The parameter value is a string of three alphanumeric characters, which is the identifier of the translation table. It must match the value assigned in the EXTEN keyword in a KBDBIWP vector.
This parameter identifies the table used by BIWP to read the input provided through the PIN pad.
The parameter applies only when BIWP uses IBM 4718 PIN Pad. The parameter value is a string of three alphanumeric characters, which is the identifier of the PIN pad input table. It must match the value assigned in the EXTEN keyword in a PINPTBL vector.
This parameter identifies the table used by BIWP to read the input provided through the MSR/E.
The parameter applies only when BIWP uses IBM 4717 MSR/E. The parameter value is a string of three alphanumeric characters, which is the identifier of the MSR/E input table. It must match the value assigned in the EXTEN keyword in a MSRINTBL vector.
This parameter identifies the table used by BIWP to encode data to the MSR/E.
The parameter applies only when BIWP uses IBM 4717 MSR/E. The parameter value is a string of three alphanumeric characters, which is the identifier of the MSR/E output table. It must match the value assigned in the EXTEN keyword in a MSROUTBL vector.
This parameter identifies the session that is used for the application program.
The parameter is optional. If specified, it overrides the value assigned in the E3270HKx keyword in the DEFAULTS vector. The parameter value is a string of up to 8 alphanumeric characters.
LWSCONF NAME=AA, TYPE=DOS, PRODLVL=L60, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* Banking Interactive Workstation Program DOS server definition. Example. */ SERVER=(BIWP1), PAR&BIWP=(AA,1,013,TKR,R,Y,FF, N,N,N,N,N,ATR,DIS,KBD) LWSCONF NAME=BB, TYPE=OS2, PRODLVL=L60, /* Banking Interactive Workstation Program server OS/2 definition. Example. */ SERVER=(BIWP1), PAR&BIWP=(AA,1,014,TKR,R,Y,FF, N,N,N,N,N,ATR,DIS,KBD) LWSCONF NAME=CC, TYPE=NT, PRODLVL=L60, /* Banking Interactive Workstation Program Windows NT VDM server definition. Example. */ SERVER=EHCVDMGR, SERVER=VBIWP1, PAR&VBIW=(AA,1,,,Y,Y,FF,N,N,N,Y,Y,ATR,DIS,KBD,,,,), SERVER=VLDA71, PAR&VLDA=(AA,1)
The banking printer program (BPP) requires one SES&BPP keyword per session.
If BPP will run in a Windows VDM, the name of the server in the SERVER keyword must be VBPPx instead of BPPx. Additionally, the keyword that is included in the LWSCONF, WSMODEL, or SVRMODEL vector, must be SES&VBPP instead of SES&BPP. The parameters that you can specify in a SES&VBPP keyword are the same as those that can be specified in a SES&BPP keyword.
You can specify up to 7 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
When BPP is installed in a DOS workstation, or in a Windows VDM, the parameter value ranges from 1 to 4. When BPP is installed in a OS/2 workstation, the parameter value ranges from 1 to 3.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only.
The parameter value can be:
This parameter identifies the table that is used to translate from 4700 system EBCDIC to ASCII, when transmitting to the printer.
The parameter value is the extension of the file containing the EBCDIC to ASCII translation table. It must match the value assigned in the EXTEN keyword in the XLATETBL vector.
The parameter is optional. The parameter value can be Y, to use this capability, or N, not to use it. The default is N.
The parameter is optional. If specified, it overrides the value assigned in the BPPSIx keyword in the DEFAULTS vector. The parameter value is a string of up to 8 alphanumeric characters.
LWSCONF NAME=AA, TYPE=DOS, PRODLVL=L60, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), SERVER=(PR47X2##), PAR&47X2=(N,C,9600,4722,N,C,9600,4722,Y), /* Banking Printer Program DOS server definition. Example. */ SERVER=(BPP1), SES&BPP=(AA,1,019,TKR,017,N)
LWSCONF NAME=BB, TYPE=OS/2, PRODLVL=L60, SERVER=(PR47X2##), PAR&47X2=(N,C,9600,4722,N,C,9600,4722,Y), /* Banking Printer Program OS/2 server definition. Example. */ SERVER=(BPP1), SES&BPP=(AA,1,020,TKR,017,N)
LWSCONF NAME=CC, TYPE=NT, PRODLVL=L60, /* Banking Printer Program NT VDM server definition. Example. */ SERVER=EHCVDMGR, SERVER=VBIWP1, PAR&VBIW=(AA,1,,,Y,Y,FF,N,N,N,Y,Y,ATR,DIS,KBD,,,,), SERVER=VLDA71, PAR&VLDA=(AA,1), SERVER=VBPP1, SES&VBPP=(AA,1,,,017,N)
The batch machine loader server requires one PAR&BMLS keyword.
You can specify up to 3 parameters:
This parameter specifies the name of the program called by the batch machine loader server when a message is pending in the message queue.
The parameter is required. The parameter value has the following format:
nnnnnnnn.eee
where:
The parameter is optional. The parameter value is a string of up to 8 alphanumeric characters. The default is the filename of the client program (parameter 1).
This parameter specifies the path where the client program runs.
The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
LWSCONF NAME=AA, TYPE=OS/2, SERVER=SMGR, PAR&SMGR=(,,,SMGRPRF,C:\SMGR\,C:\SMGR\,C:\SMGR\,C:\SMGR\), /* Batch machine loader server definition. Example */ SERVER=BMLS, PAR&BMLS=(MESSAGP.EXE,MESSAGEP,C:\PATHM\), /* Object post box client definition. Example */ CLIENT=(OPBS,BB) LWSCONF NAME=BB, TYPE=OS/2, SERVER=SHFILE01, PAR&SHFL=(PROFSFS,3,8,Y,0), /* Object post box server definition. Example */ SERVER=OPBS, PAR&OPBS=(C:\OPBSDB\), CLIENT=(SHFILE01,BB)
The DCADLC server requires one PAR&DCA keyword.
You can specify up to 3 parameters:
The parameter is optional. The parameter value ranges from 10 to 100. (1 buffer = 272 bytes in memory, 256 bytes of data.) The default is 64.
This parameter specifies the number of retries after negative responses that are admitted before resetting the DCA card.
The parameter is optional. The parameter value ranges from 1 to 100. The default is 10.
This parameter specifies the seconds after a non-answered request, that are admitted before resetting the DCA card.
The parameter is optional. The parameter value ranges from 1 to 60. The default is 30.
LWSCONF NAME=AA, TYPE=OS/2, PRODLVL=L60, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), CLIENT=(SNA01,AA), SES&SNA=(AA,01,010,DCA), /* DCA server definition. Example. */ SERVER=(DCADLC), PAR&DCA=(64,10,30)
LWSCONF NAME=AA, TYPE=OS/2, SERVER=SMGR, PAR&SMGR=(,,,SMGRPRF,C:\SMGR\,C:\SMGR\,C:\SMGR\,C:\SMGR\), SERVER=(SHFILEBA), PAR&SHFL=(PROFSFS,10,3,Y), SERVER=(SFQUERY), CLIENT=(SHFILEBA,AA), /* Electronic journal server definition. Example. */ SERVER=(ELECJO01), PAR&EJOU=(PROFEJOU,1) LWSCONF NAME=BB, TYPE=DOS, /* Electronic journal client definition. Example. */ CLIENT=(ELECJO01,AA)
|
The forwarding server requires one PAR&FORW keyword, and as many
SES&FORW keywords as forwarding sessions are defined in the profile
used.
|
You can specify up to 3 parameters:
If only one forwarding server profile is defined, the parameter is optional. The parameter value is a string of up to 8 alphanumeric characters, and must match the value assigned in the NAME keyword in the FORWPRF vector.
This parameter identifies the table that is used to translate from personal computer system ASCII to host computer EBCDIC, when transmitting from the workstation to the host computer.
The parameter does not apply to DBCS mode. It is optional, if only one translation table is defined. The parameter value is the name of the translation table. It must match the value assigned in a XLATETBL vector with TYPE = AEFORW.
The parameter is optional. The parameter value ranges from 1 to 4, meaning the size in KBs. The default is 1.
You can specify up to 5 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
The parameter is required. The parameter value ranges from 1 to 3, and must match the value assigned in the SESSION keyword in the FORWDS vector.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only that is not X.25.
For workstations with more than one DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
This parameter specifies the name of the device on the AS/400 that is used for communication purposes.
The parameter applies only when the SNA services are provided by a OS/400 system.
The parameter is optional. The parameter value is a string of up to 10 alphanumeric characters.
The default is QCFBZZFORx. Note that x is the forwarding session number, ranging from 1 to 3, specified in the second parameter.
LWSCONF NAME=AA, TYPE=OS/2, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(SHFILEBA), PAR&SHFL=(PROFSFS,10,3,Y), CLIENT=(SHFILEBA,AA), SERVER=SMGR, PAR&SMGR=(,,,SMGRPRF,C:\SMGR\,C:\SMGR\,C:\SMGR\,C:\SMGR\), SERVER=(SFQUERY), SERVER=(SFORFORW), PAR&SFOR=(PROFSTOR,1), CLIENT=(SFORFORW,AA), /* Forwarding server definition. Example. */ SERVER=(FORWARD), PAR&FORW=(PROFFORW,OUT,1), SES&FORW=(AA,1)
You can specify up to 5 parameters:
This parameter is optional. The parameter value can be:
This parameter specifies the number of dispatcher processes that are created for immediate use by the Java Manager. The parameter value can be in the range 1 through 32. The default value is 4.This parameter is ignored if parameter 1 is N.
This parameter is optional. Its value can be Y to distribute the file, or N to not distribute the file. The default value is N.
This parameter is optional. Its value can be Y to distribute the file, or N to not distribute the file. The default value is N.
This parameter is optional. Its value can be Y to distribute the file, or N to not distribute the file. The default value is N.
/* Java distribution definition. Example. */ LWSCONF NAME=AA, TYPE=LINUX, SERVER=JAVA, PAR&JAVA=(Y,6,N,N,Y)
|
The LANDP link server requires one optional PAR&LINK keyword, and can have
from 1 to 10 SES&LINK keywords.
|
Range 1024 through 65535, default 52699.
To make a connection, the exporting LANDP link server and the importing LANDP link server must use the same TCP/IP port.
Range 0 through 3276. A value of 0 means no retry. The default retry interval is 30 seconds.
This parameter is only permitted when the SES&LINK import keyword is also specified.
The TCP/IP network name or the IP address of the workstation running the exporting LANDP link server. Network names can be up to 35 characters, and must be resolvable to IP addresses by the domain name server or local HOSTS file. IP addresses must be in dotted decimal notation.
This parameter must be present when, and only when, the SES&LINK import keyword is also specified.
You can specify either two or three parameters:
This parameter is required. The parameter value can be:
This parameter is required, and its value is the name of the service to be imported or exported. The same name cannot appear more than once in the list of services to be imported. The same name cannot appear more than once in the list of services to be exported.
The following LANDP service names cannot be imported or exported: SPV, LAN, EHCLIP, SMGR, EHCSAM, EHCTRACW.
When defining a service to be imported, the value of this optional parameter is an alias name for the service. If an alias is specified, the imported service will be made available with the corresponding alias name. If the alias parameter is absent, the imported service will be made available without name change.
No two services can be imported with the same name. If an import name has trailing '#' characters, then the corresponding alias name must have the same trailing '#' characters.
When defining a service to be exported, the value of this required parameter is the name of the workstation providing the service.
Note that, if a service is imported with a name or alias that is not the name of a LANDP-supplied service, a server definition (DEFSERV) statement for it must appear in COMMON.SPC.
This example imports the SHFILE01 service into workstation AA in workgroup WG1, and exports it from workstation BB in workgroup WG2:
LANCONF NAME=WG1, WSNAMES=(AA,AB) LWSCONF NAME=AA, /* Workstation AA in workgroup WG1 */ SERVER=(EHCLINK,,N), PAR&LINK=(,,BB.HURSLEY.IBM.COM), SES&LINK=(I,SHFILE01) LWSCONF NAME=AB, /* Workstation AB in workgroup WG1 */ CLIENT=(SHFILE01,AA) LANCONF NAME=WG2, WSNAMES=(BB) LWSCONF NAME=BB, /* Workstation BB in workgroup WG2 */ SERVER=(SHFILE01,,N), PAR&SHFL=(PRF1,10,3,N,0,100,,N1,10), SERVER=(EHCLINK,,N), PAR&LINK=(), SES&LINK(E,SHFILE01,BB)
The logical device address (LDA) 7 program requires one PAR&LDA7 keyword.
If the LDA 7 program will run in an OS/2 or a Windows VDM, the name of the server in the SERVER keyword must be VLDA7x instead of LDA7x. Additionally, the keyword to be included in the LWSCONF, WSMODEL, or SVRMODEL vector must be PAR&VLDA instead of PAR&LDA7. The parameters you can specify in a PAR&VLDA keyword are the same as those that can be specified in a PAR&LDA7 keyword.
You can specify up to 4 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
When the LDA 7 program is installed in a DOS workstation, or is used in OS/2 VDM or Windows, this parameter is required.
The parameter value ranges from 1 to 5, and must be unique for the workstation where BIWP and the LDA 7 program are installed. It must match the value assigned as the BIWP emulated session number (parameter 2) in the PAR&BIWP keyword.
When the LDA 7 program is installed in a OS/2 workstation, the parameter must be omitted. The default is 1.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only.
The parameter value can be:
LWSCONF NAME=AA, TYPE=DOS, PRODLVL=L60, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), SERVER=(BIWP3), PAR&BIWP=(AA,3,013,TKR,R,Y,FF, N,N,N,N,N,ATR,DIS,KBD), /* Logical Device Address 7 Program DOS server definition. Example. */ SERVER=(LDA73), PAR&LDA7=(AA,3,011,TKR) LWSCONF NAME=BB, TYPE=DOS, PRODLVL=L60, SERVER=(BIWP3), PAR&BIWP=(AA,3,014,TKR,R,Y,FF, N,N,N,N,N,ATR,DIS,KBD), /* Logical Device Address 7 Program OS/2 server definition. Example. */ SERVER=(LDA73), PAR&LDA7=(AA,3,012,TKR) LWSCONF NAME=CC, TYPE=NT, PRODLVL=L60, /* Logical Device Address 7 Program Windows NT VDM server definition. Example. */ SERVER=EHCVDMGR, SERVER=VBIWP1, PAR&VBIW=(AA,1,,,Y,Y,FF,N,N,N,Y,Y,ATR,DIS,KBD,,,,), SERVER=VLDA71, PAR&VLDA=(AA,1)
|
The LANDP MQSeries Link server requires one PAR&MQ keyword.
|
You can specify up to 6 parameters:
This parameter specifies the name of the queue manager to which the server is to connect. The parameter is a string of up to 24 bytes. All alphabetic characters are processed as upper case. Special characters '_' and '.' can be used in the name. Alternatively, this parameter can define an environment variable, for example, '%MQMNAME%'. If this parameter is omitted, EHCMQ## connects to the MQSeries default queue manager.
This parameter specifies the maximum message length permitted by the MQSeries Link server. This is used to restrict the maximum message length to something less than or equal to the default of 57000 bytes. It can have a value between 1000 and 57000.
This parameter specifies the message detail level to be written to the log file. If this parameter is omitted, the default is for logging to be off. The values E|W|I can be specified where E=error level, W=warning level and I=information level. I includes levels W and E, W includes level E.
This data string specifies the log file path, which can include a drive identifier if required. The log file is where the session log files are created.
The data string must be less than 30 bytes in length.
If the data string is omitted, default values are used. The drive defaults to the drive of the current working directory for the EHCMQ## process. If a drive is specified, a path should also be defined. When the path is omitted it defaults to 'EHCMQLOG'. If both drive and path are omitted 'EHCMQLOG' is created as a subdirectory of the current working directory for the EHCMQ## process.
A log file is created for each session. The log file is named as XXhhmmss.ddd where:
This parameter specifies the maximum number of different sessions the server can process at the same time. The parameter, which is optional, can be given a value in the range from 1 to 64. The default is 32.
This parameter specifies the number of MQ connections that should be made at startup. Every session requires a MQ connection, which can be made at startup or as session requests are received. The parameter value can be in the range 0 to the total number of permitted sessions. The parameter is optional with a default value of 0. When this option is non-zero, the LOADER server's timeout probably needs to be increased. Refer to Loading statements for LANDP for OS/2 servers or Loading statements for LANDP for Windows servers.
MQSeries Link server example LWSCONF NAME=AA, TYPE=OS/2, /* MQSeries Link server definition. Example. */ SERVER=(EHCMQ##), PAR&MQ=(EHC_QM,32000,W,D:\EHC_QM\,64,4) LWSCONF NAME=BB, TYPE=DOS, /* LANDP link server client definition. Example, two sessions */ CLIENT=(EHCMQ01,AA), CLIENT=(EHCMQ02,AA)
|
When the magnetic stripe reader/encoder (MSR/E) server is loaded in a LANDP
workstation, it requires a PAR&MSRE keyword for the workstation that
provides services.
|
You can specify up to 2 parameters:
This parameter specifies the product attached to the workstation that provides the MSR/E device to be supported by the server.
The parameter is required. The parameter value can be:
This parameter specifies the COM port where the product that provides the MSR/E device will be attached.
The parameter applies only if value 4777 or 4778 was specified in parameter 1.
On LANDP for DOS and LANDP for OS/2, the parameter value can be in the range 1 through 4, or M. If the mouse port is to be used, specify M.
On LANDP for Windows and LANDP for Linux, the parameter value can be in the range 1 through 8. The mouse port attachment is not supported.
The default is 1.
If 4778 PIN pad capabilities are to be used, the value must match that specified in the PAR&PINP keyword.
LWSCONF NAME=AA, TYPE=NT, PRODLVL=L60, /* Magnetic Stripe Reader/Encoder server definition. Example */ SERVER=(MSRE4701), PAR&MSRE=(4777,1)
You can specify up to 4 parameters:
The parameter is optional. The parameter value can be Y, to include your telephone number in the packet call, or N, not to include it. The default is N.
The parameter is optional. The parameter value is a number of three digits. Valid values for your country can be obtained from the telecommunications company. The default is 000.
The parameter is optional. The parameter value ranges from 0 to 9. Valid values for your country can be obtained from the telecommunications company. The default is 0.
The parameter is required, if you have assigned the Y value to the first parameter (telephone number selection). If not, the parameter is optional.
The parameter value is a number of up to 11 digits.
You can specify up to 9 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
The parameter is required. The parameter value ranges from 1 to 15, and must be unique for each client workstation. This includes all the circuits: native X.25, SNA, or user communication server.
The parameter is optional. The parameter value can be:
It must match the value assigned in the PAR&X25D keyword, or on the X.25 profile. The default is OUTG.
The parameter is required for incoming virtual circuits, and optional for outgoing circuits. The parameter value is a string of up to 8 alphanumeric characters.
This parameter specifies the subscriber address of the partner you want to communicate with. For international calls, the subscriber number must be preceded by the country identification and the country subcode.
The parameter is optional for incoming virtual circuits, and required for outgoing circuits. The parameter value is a string of up to 15 digits.
The parameter is optional. The parameter value is a string of up to 4 bytes (eight hexadecimal characters).
Facility code |
---|
Parameters 7, 8, and 9 define the transmission facilities. The information is optional and made up of up to 63 bytes (126 hexadecimal characters). Refer to the X.25 Codification Facilities Rules from your X.25 Network provider. |
The parameter is optional. The parameter value is a string of up to 21 bytes (42 hexadecimal characters).
To specify this code, facility code (part 1) must be completely filled.
The parameter is optional. The parameter value is a string of up to 21 bytes (42 hexadecimal characters).
To specify this code, facility code (part 1) and facility code (part 2) must be completely filled.
The parameter is optional. The parameter value is a string of up to 21 bytes (42 hexadecimal characters).
LWSCONF NAME=AA, TYPE=DOS, SERVER=(X25DLC2), PAR&X252=(20,Y,7,3,PROFILE,214,1,231020107), /* Native X.25 server definition (using the IBM X.25 Interface Coprocessor/2). Example */ SERVER=(X25NAT##), CLIENT=(X25NAT01,AA), SES&NSVC=(AA,01,OUTG,INBB,203456988) LWSCONF NAME=BB, TYPE=DOS, /* Native X.25 client definition. Example */ CLIENT=(X25NAT01,AA), SES&NSVC=(AA,01,OUTG,INBB,203456988)
The object post box server requires one PAR&OPBS keyword.
You can specify one parameter:
This parameter specifies the path where the object post box server databases are located.
The parameter is required. The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
LWSCONF NAME=AA, TYPE=OS/2, /* Object post box server definition. Example */ SERVER=(OPBS), PAR&OPBS=(C:\OPBSDB\) LWSCONF NAME=BB, TYPE=DOS, /* Object post box client definition. Example */ CLIENT=(OPBS,AA)
The ODBC query server requires one PAR&ODB keyword.
You can specify up to 5 parameters:
This parameter specifies the default Data Source name as defined in the ODBC Driver Manager.
The parameter is optional. The parameter value is a string of up to 20 alphanumeric characters. The default is CONFIGUR.
The number of worker threads grows depending on the amount of throughput. This parameter represents the number of worker threads to be started at initialization.
The parameter is optional. The parameter value is in the range from 1 through 128, but must be less than or equal to parameter 3. The default is 5.
If system resources are scarce, this parameter puts a lower threshold on the number of worker threads EHCODB## can start after initialization.
This parameter is optional. The parameter value is in the range from 1 through 128, but must be greater than or equal to parameter 2. The default is 128.
This parameter specifies the maximum number of sessions that can be concurrently open on a workstation.
This parameter is optional. The parameter value is in the range from 1 through 64. The default is 10.
This parameter specifies the time, in seconds, that the ODBC query server waits for a reply from the data source before giving a time-out response.
The parameter is optional. The parameter value ranges from 10 to 32767. The default is 15.
LWSCONF NAME=AA, TYPE=NT, /* ODBC query server definition. Example */ SERVER=(EHCODB01), PAR&ODB=(BASEMIX,4,14,10,30) LWSCONF NAME=AB, TYPE=NT, /* ODBC query server client definition. Example */ CLIENT=(EHCODB01,AA)
|
When the PIN pad server is loaded in a LANDP workstation, it requires one
PAR&PINP keyword for the workstation that provides services.
|
You can specify up to 3 parameters:
This parameter specifies the product attached to the workstation that provides the PIN pad device to be supported by the server.
The parameter is required. The parameter value can be:
This parameter specifies the COM port where the product that provides the PIN pad device will be attached.
The parameter applies only if value 4778 was specified in parameter 1. On LANDP for DOS and LANDP for OS/2, the parameter value can be in the range 1 through 4, or M. If the mouse port is to be used, specify M.
On LANDP for Windows and LANDP for Linux, the parameter value can be in the range 1 through 8. The mouse port attachment is not supported.
The default is 1.
If 4778 magnetic stripe reader capabilities are to be used, the value must match that specified in the PAR&MSRE keyword.
This parameter specifies whether 4778 magnetic stripe reader capabilities are to be used, or not.
The parameter applies only if value 4778 was specified in parameter 1. It is optional. The parameter value can be Y, to use 4778 magnetic stripe reader capabilities, or N, not to use them. The default is Y.
LWSCONF NAME=BB, TYPE=OS/2, PRODLVL=L60, /* PIN pad server definition. Example */ SERVER=(PINP4702), PAR&PINP=(4778,2,Y)
The query server requires one PAR&SQL keyword.
You can specify up to 11 parameters:
This parameter specifies the Database Manager database name.
The parameter is optional. The parameter value is a string of up to 8 alphanumeric characters. The default is CONFIGUR.
This parameter specifies the maximum number of requests the server can process at the same time.
The parameter is optional. The parameter value ranges from 1 to 128. The default is 5.
This parameter specifies the maximum number of requests from different sessions the server processes at the same time.
The parameter is optional. The parameter value ranges from 1 to 128. The default is 4.
This parameter specifies the maximum number of applications running EHCSQL## sessions plus the number of extra sessions per workstation using the Open Session (OS) function.
The parameter is optional. The parameter value ranges from 1 to 64. The default is 10.
The parameter is optional. The parameter value can be Y, to get uniform response time, or N, not to specify it. The default is Y.
This parameter specifies the time, in seconds, the query server waits for a reply from SQL before giving a time-out response.
The parameter is optional. The parameter value ranges from 10 to 32767. The default is 15.
This parameter, if set to Y, indicates that the ODBC query server EHCODB## is to be invoked rather than the query server EHCSQL##. Valid values are Y and N. The default is N.
On a Windows workstation, only Y is valid. On an OS/2 workstation, only N is valid.
LWSCONF NAME=AA, TYPE=OS/2, /* Query server definition. Example. */ SERVER=(EHCSQL01), PAR&SQL=(CONFIGUR,5,4,10,Y,15) LWSCONF NAME=BB, TYPE=DOS, /* Query client definition. Example. */ CLIENT=(EHCSQL01,AA)
|
The remote change management services (RCMS) require one PAR&RCMS
keyword.
|
You can specify up to 9 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only if the SNA services are provided by a DOS workstation. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
This parameter specifies the name of the device on the AS/400 that is used for communication purposes.
The parameter applies only when the SNA services are provided by an OS/400 system.
The parameter is optional. The parameter value is a string of up to 10 alphanumeric characters. The default is QCFBZZRCMS.
This parameter specifies the directory where the logical names file (RCMS.LNF), the RCMS.ACK file, and the EBCDIC-to-ASCII and ASCII-to-EBCDIC translation tables are located in the production workstation at run-time.
The parameter is required. The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
This parameter specifies the directory where RCMS is to store the events occurring during the process, as well as the message file, and log file.
The parameter is required. The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
If only one table is defined, the parameter is optional. The parameter value is a string of three alphanumeric characters, which is the identifier of the translation table. It must match the value assigned in the EXTEN keyword in a XLATETBL vector with TYPE=AERCMS.
In DBCS mode the parameter specifies the translation mode. The parameter value can be:
If only one table is defined, the parameter is optional. The parameter value is a string of three alphanumeric characters, which is the identifier of the translation table. It must match the value assigned in the EXTEN keyword in a XLATETBL vector with TYPE=EARCMS.
In DBCS mode the parameter does not apply.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* Remote Change Management Services server definition. Example. */ SERVER=(RCMS), PAR&RCMS=(AA,021,TKR,,C:\RCMSYS\, C:\RCMPRO\,,OUT,INP)
The shared DOS directory server requires one PAR&SHDR keyword. You can also specify one SES&SHDR keyword for each client workstation.
You can specify one parameter:
You can specify two parameters:
The parameter is required, if you specify the keyword. The parameter value is a string of up to 2 alphanumeric characters.
This parameter specifies the size of the data area, in K.
The parameter is required, if you specify the keyword. The parameter value ranges from 1 to 56. The default is 4.
LWSCONF NAME=AA, TYPE=DOS, /* Shared DOS directory server definition. Example. */ SERVER=(SHRDIR), PAR&SHDR=(10) LWSCONF NAME=BB, TYPE=DOS, /* Shared DOS directory client definition. Example. */ CLIENT=(SHRDIR,AA), SES&SHDR=(AA,10)
The shared-file distributor requires one PAR&SFD keyword.
You can specify up to 2 parameters:
The parameter is optional. The parameter value can be Y, to create a file to collect statistics, or N not to create the file. The default is N.
This parameter specifies the number of threads to attend and process requests in parallel.
The parameter is optional. The parameter value ranges from 1 to 252. The default is 2.
LWSCONF NAME=M1, TYPE=OS/2, PRODLVL=L60, /* Shared-file distributor definition. Example. */ SERVER=EHCSFD01, PAR&SFD=(Y,2), /* Shared-file server definition. Example. */ SERVER=SHFILE01, PAR&SHFL=(BASEDB11,5,10,Y,3,,EHCSFD01), /* Shared-file distributor client definition. */ CLIENT=(EHCSFD01,M1), /* Shared-file server client definitions. */ CLIENT=(SHFILE01,M1), CLIENT=(SHFILE02,M2), CLIENT=(SHFILE03,M3) LWSCONF NAME=M2, TYPE=OS/2, PRODLVL=L60, /* Shared-file server definition. Example. */ SERVER=SHFILE02, PAR&SHFL=(BASEDB12,5,10,Y,3,,EHCSFD01), /* Shared-file distributor client definition. */ CLIENT=(EHCSFD01,M1), /* Shared-file server client definitions. */ CLIENT=(SHFILE01,M1), CLIENT=(SHFILE02,M2), CLIENT=(SHFILE03,M3) LWSCONF NAME=M3, TYPE=OS/2, PRODLVL=L60, /* Shared-file server definition. Example. */ SERVER=SHFILE03, PAR&SHFL=(BASEDB13,5,10,Y,3,,EHCSFD01), /* Shared-file distributor client definition. */ CLIENT=(EHCSFD01,M1), /* Shared-file server client definitions. */ CLIENT=(SHFILE01,M1), CLIENT=(SHFILE02,M2), CLIENT=(SHFILE03,M3)
The shared-file replicator requires one PAR&SFR keyword.
You can specify up to 4 parameters:
The parameter is optional. The parameter value can be Y, to create a file to collect statistics, or N not to create the file. The default is N.
This parameter specifies the number of threads to attend and process requests in parallel.
The parameter is optional. The parameter value ranges from 1 to 252. The default is 2.
This parameter specifies the full name of the owner of the shared-file replicator.
The parameter value can be:
This parameter specifies the filename of a file with extension PCN, which will contain the list of PCBs to be accessed by the shared-file replicator.
The parameter is optional. The parameter value is a string with up to 8 alphanumeric characters. The default is EHCSFRPC.
LWSCONF NAME=M1, TYPE=OS/2, PRODLVL=L60, /* Shared-file replicator definition. Example. */ SERVER=EHCSFR01, PAR&SFR=(Y,2,,BASEDB11), /* Shared-file server definition. Example. */ SERVER=SHFILE01, PAR&SHFL=(BASEDB11,5,10,Y,3,,EHCSFR01), /* Shared-file replicator client definition. */ CLIENT=(EHCSFR01,M1), /* Shared-file server client definitions. */ CLIENT=(SHFILE01,M1), CLIENT=(SHFILE02,M2), CLIENT=(SHFILE03,M3) LWSCONF NAME=M2, TYPE=OS/2, PRODLVL=L60, /* Shared-file server definition. Example. */ SERVER=SHFILE02, PAR&SHFL=(BASEDB11,5,10,Y,3,,EHCSFR01), /* Shared-file replicator client definition. */ CLIENT=(EHCSFR01,M1), /* Shared-file server client definitions. */ CLIENT=(SHFILE01,M1), CLIENT=(SHFILE02,M2), CLIENT=(SHFILE03,M3) LWSCONF NAME=M3, TYPE=OS/2, PRODLVL=L60, /* Shared-file server definition. Example. */ SERVER=SHFILE03, PAR&SHFL=(BASEDB11,5,10,Y,3,,EHCSFR01), /* Shared-file replicator client definition. */ CLIENT=(EHCSFR01,M1), /* Shared-file server client definitions. */ CLIENT=(SHFILE01,M1), CLIENT=(SHFILE02,M2), CLIENT=(SHFILE03,M3)
|
The shared-file server requires one PAR&SHFL keyword.
|
You can specify up to 9 parameters:
This parameter specifies the name of the shared-file server profile to be used.
If only one shared-file server profile is specified in all the SHFLDBD vectors you define, the parameter is optional. The parameter value is a string of up to 8 alphanumeric characters, and must match the value assigned in the SHFLPRF keyword in a SHFLDBD vector.
If shared-file replicator is to be used, all shared-file servers owned by the same shared-file replicator must use the same profile.
Each additional buffer requires 1KB of memory.
The parameter is optional. The parameter value ranges from 0 to 484. The default is 0.
The electronic journal, store-for-forwarding, and forwarding servers require an extra session. If those servers are loaded, the parameter is required.
If the application obtains additional sessions with the Open Session (OS) function, or if a separate session is defined for the electronic journal or the store-for-forwarding server, you must add those sessions.
The object post box server also requires an extra session.
The parameter value ranges from 0 through 243 (OS/2, Windows, and Linux), or from 0 through 245 (DOS). The value plus the number of client workstations must not be higher than 243 (OS/2, Windows, and Linux), or 245 (DOS). The default is 0.
The parameter is optional. The parameter value can be Y, to create a file to collect statistics, or N not to create the file. The default is N.
The parameter is optional. The parameter value can be:
The default is 0.
The parameter is optional. The parameter value ranges from 10 to 245.
This parameter specifies the full name of the owner of the shared-file server.
The parameter applies only to OS/2 workstations. However, it does not apply if the shared-file server is used by:
The parameter is optional. The parameter value can be:
Active and backup workstations can be OS/2, Windows, or Linux. Each XLR workstation must run the Service Availability Manager.
The parameter is optional.
The parameter is optional.
Range 0-999. Default 0 (no automatic takeover).
LWSCONF NAME=AA, TYPE=OS/2, /* Shared file server definition. Example. */ SERVER=(SHFILEBA), PAR&SHFL=(PROFSFS,10,3,Y,0,60) LWSCONF NAME=BB, TYPE=OS/2, /* Shared file client definition. Example. */ CLIENT=(SHFILEBA,AA)
In the following example, the active server (SHFILE01) is configured on the workstation O1, with a backup on N1. A takeover by the backup occurs 10 seconds after detection of a failure by the active. EHCSAM must run on both these workstations. EHCSAM is also configured to run on workstation O2. The purpose of EHCSAM on O2 is to maintain state information, which is useful if either XLR workstation is not available during the startup of the workgroup EHCCUS.
LANCONF GROUP=EHCCUS, /* Workgroup Definition */ NAME=XLR, SUFFIX=Y, WSNAMES=(O1,O2,O3,N1) LWSCONF NAME=O1, /* Workstation definition O1 */ PRODLVL=L60, TYPE=OS/2, SERVER=EHCSAM, /* Service Availability Manager */ SERVER=(EHCVDMGR), /* Multiple virtual DOS machine relay definition */ SERVER=(SHFILE01), /* Shared-file server definition */ PAR&SHFL=(SHFLPRF1,10,3,N,0,100,,N1,10), CLIENT=(SHFILE01,O1) /* Client definitions */ LWSCONF NAME=O2, /* Workstation definition O2 */ PRODLVL=L60, TYPE=OS/2, SERVER=EHCSAM, /* Service Availability Manager */ SERVER=(EHCVDMGR), /* Multiple virtual DOS machine relay definition */
CLIENT=(SHFILE01,O1) /* Client definitions */ LWSCONF NAME=O3, /* Workstation definition O3 */ PRODLVL=L60, TYPE=OS/2, SERVER=(EHCVDMGR), /* Multiple virtual DOS machine relay definition */ CLIENT=(SHFILE01,O1) /* Client definition */ LWSCONF NAME=N1, /* Workstation definition N1 */ PRODLVL=L60, TYPE=NT, SERVER=EHCSAM, /* Service Availability Manager */ SERVER=(EHCVDMGR), /* Multiple virtual DOS machine relay definition */ CLIENT=(SHFILE01,O1)
You can specify up to 7 parameters (on LANDP for Windows, only parameters 1 and 2 can be used).
This parameter specifies who initializes the session.
The parameter is optional. The parameter value can be:
The default is APPL.
This parameter specifies who manages the BID command.
The parameter is optional. The parameter value can be:
The default is SRV.
The parameter applies only to OS/2 workstations. The parameter value ranges from 1 to 255.
The parameter applies only to OS/2 workstations. The parameter value can be:
The default is N.
The parameter applies only to DOS workstations. The parameter value must match the value specified in the NAME keyword of a LUPOOL vector.
The parameter applies only to OS/2 workstations. The parameter value can be:
The default is N.
Server-managed cryptography uses the communications provider exits, ACSRENCR.DLL and ACSRDECR.DLL, which are supplied with LANDP, and the TSS SECY server.
The parameter applies only to OS/2 workstations, and is only valid if server-managed cryptography has been specified (if parameter 6 = Y).
If specified, this parameter must be a string of 1 to 16 alphanumeric characters. If it is not specified, the key defaults to TMKssww where ss is the session ID and ww is the workstation ID.
The keyword is required when the SNA services are provided from an OS/2 or Windows workstation that uses LU pool support.
You can specify up to 5 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
This number is used by a server or application to identify the SNA session.
The parameter is required. The parameter value ranges from 01 to 30, and must be unique for the client workstation. It must contain two digits.
A modified SNA interface that allows for more than 30 user sessions per workstation is available when the SNA services are provided from an OS/2 or Windows workstation. When using this interface, the session identifier may be any two ASCII characters. If LU pooling support is required, provide an SES&SNA keyword for each session to be pooled. If CLIENT=(SNA,xx) has been specified in LWSCONF, the SNA session identifier in the SES&SNA keyword may be any two ASCII characters.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only when the SNA services are provided from a DOS workstation, and the session does not use pooling support. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value must match the value assigned as the virtual circuit definition identification (parameter 1) in a SES&SPVC keyword or SES&SSVC keyword.
This parameter specifies the name of the device on the AS/400 that is used for communication purposes.
The parameter applies only when the SNA services are provided by an OS/400 system. The parameter value is a string of up to 10 alphanumeric characters.
You can specify up to 4 parameters:
This parameter identifies the virtual circuit, and is used for reference purposes when defining the SNA session that will use it.
The parameter is required. The parameter value ranges from 1 to 999. The value must be unique for all the circuits, permanent and virtual, that are used through the SNA server.
The parameter is required. The parameter value ranges from 1 to the number of permanent virtual circuits defined either in the PAR&X25D keyword or in the X.25 profile. It must be unique for the SES&SPVC keywords.
The parameter is optional. The parameter value is a hexadecimal number of three digits. The value must match the information in the host computer.
The parameter is optional. The parameter value is a hexadecimal number of five digits. The value must match the information in the host computer.
The combination of the constant X'0200', the identification block, and the identification number results in the exchange identifier (XID), which is only used for switched connections. For permanent SNA circuits, the XID is optional.
The number of SES&SSVC keywords included can be greater than the number of switched virtual calls defined either in the PAR&X25D keyword or in the X.25 profile. However, at run-time the number of switched virtual calls working simultaneously is limited by the number of switched virtual circuits defined.
You can specify up to 10 parameters:
This parameter identifies the virtual circuit, and is used for reference purposes when defining the SNA session that will use it.
The parameter is required. The parameter value ranges from 1 to 999. The value must be unique for all the circuits, permanent and virtual, that are used through the SNA server.
This parameter specifies the subscriber address of the partner you want to communicate with. For international calls, the subscriber number must be preceded by the country identification and the country subcode.
The parameter is required. The parameter value is a string of up to 15 digits.
The parameter is required. The parameter value is a hexadecimal number of three digits. The value must match the information in the host computer.
The parameter is required. The parameter value is a hexadecimal number of five digits. The value must match the information in the host computer.
The combination of the constant X'0200', the identification block, and the identification number results in the exchange identifier (XID).
The type of connection selected must match those defined during the customization of the X.25 communications adapter card, and the values assigned either in the PAR&X25D keyword, or in the X.25 profile.
To assign a circuit as incoming, you must have selected at least one incoming or one both-way call during configuration of the adapter.
To assign a circuit as outgoing, you must have selected at least one outgoing or one both-way call during configuration of the adapter.
The parameter is optional. The parameter value can be:
The default is OUTG.
The parameter is optional. The parameter value is a string of 8 bytes (16 hexadecimal characters) and must match the host computer definitions.
This is information of your own that is sent across the communication line every time a call is made.
The parameter is optional. The parameter value is a string of up to 4 bytes (eight hexadecimal characters).
Facility code |
---|
Parameters 8, 9, and 10 define the transmission facilities. The information is optional and made up by up to 63 bytes (126 hexadecimal characters). Refer to the X.25 Codification Facilities Rules from your X.25 Network provider. |
The parameter value is a string of up to 21 bytes (42 hexadecimal characters).
To specify this code, facility code (part 1) must be completely filled. The parameter value is a string of up to 21 bytes (42 hexadecimal characters).
To specify this code, facility code (part 1) and facility code (part 2) must be completely filled. The parameter value is a string of up to 21 bytes (42 hexadecimal characters).
The parameter value must match the value assigned to the TBLNAME keyword of a X25DIR vector.
Example 1 LWSCONF NAME=AA, TYPE=DOS, SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* SNA server definition. Example. */ SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV) LWSCONF NAME=BB, TYPE=OS/2, /* or TYPE=NT, */ /* SNA client definition. Example. */ CLIENT=(SNA01,AA), SES&SNA=(AA,01,018,TKR) Example 2 LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(X25DLC2), PAR&X252=(20,Y,7,3,PROFILE,214,1,231020107), /* SNA server definition (using the IBM X.25 Interface Coprocessor/2) for permanent circuits. Example */ SES&SPVC=(001,1) LWSCONF NAME=BB, TYPE=DOS, /* SNA client definition (using the IBM X.25 Interface Coprocessor/2) for permanent circuits. Example */ CLIENT=(SNA02,AA), SES&SNA=(AA,02,019,001) Example 3 LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(X25DLC2), PAR&X252=(20,Y,7,3,PROFILE,214,1,231020107), /* SNA server definition (using the IBM X.25 Interface Coprocessor/2) for virtual circuits. Example */ SES&SSVC=(002,231020107,017,80011,BOTH) LWSCONF NAME=BB, TYPE=DOS, /* SNA client definition (using the IBM X.25 Interface Coprocessor/2) for virtual circuits. Example */ CLIENT=(SNA02,AA), SES&SNA=(AA,02,019,002)
The store-for-forwarding server requires one PAR&SFOR keyword.
You can specify up to 2 parameters:
If only one store-for-forwarding server profile is defined, the parameter is optional. The parameter value is a string of up to 8 alphanumeric characters, and must match the value assigned in the NAME keyword in the SFORWPRF vector.
The parameter is optional. The parameter value ranges from 1 to 4, meaning the size in KBs. If that keyword is not specified, the default is 1.
LWSCONF NAME=AA, TYPE=OS/2, SERVER=SMGR, PAR&SMGR=(,,,SMGRPRF,C:\SMGR\,C:\SMGR\,C:\SMGR\,C:\SMGR\), SERVER=(SHFILEBA), PAR&SHFL=(PROFSFS,10,3,Y), CLIENT=(SHFILEBA,AA), SERVER=(SFQUERY), /* Store for forwarding server definition. Example. */ SERVER=(SFORFORW), PAR&SFOR=(PROFSTOR,1) LWSCONF NAME=BB, TYPE=DOS, /* Store for forwarding client definition. Example. */ CLIENT=(SFORFORW,AA)
The SDLC server requires one PAR&SDLC keyword.
You can specify up to 25 parameters:
The parameter is optional. The parameter value ranges from 8 to 999 (1 buffer = 290 bytes in memory, 256 bytes of data). The default is 8.
The parameter is required. The parameter value is a hexadecimal number of two digits.
The parameter is optional. The parameter value can be Y, to use NRZI, or N, not to use NRZI. The default is N.
The parameter is optional. The parameter value can be Y, when using a switched line, or N, when using a point-to-point line. The default is Y.
The parameter is optional. The parameter value can be:
The default is N.
When working with point-to-point lines, the parameter is optional. The parameter value is a hexadecimal number of three digits.
When working with point-to-point lines, the parameter is optional. The parameter value is a hexadecimal number of five digits.
The value must match the information in the host computer. The combination of the constant X'0200', the identification block, and the identification number results in the exchange identifier (XID), which is only used for switched connections.
The parameter is optional. The parameter value can be TURN, for turnaround required, or CRTS, for constant request to send. When using a two-wire line, you must select TURN; when using a four-wire line, you can select any of the values. The default is TURN.
This parameter specifies the time-out in seconds.
The parameter value ranges from 10 to 65. The default is 65.
The parameter is optional. The parameter value is a hexadecimal number of ten digits.
If specified, the SNA server validates the SSCP name that receives in the ACTPU (activate physical unit) command.
11-25. System Service Control Point (SSCP) name. See information for parameter 10.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), CLIENT=(SNA01,AA), SES&SNA=(AA,01,006,SDL), /* SDLC server definition. Example. */ SERVER=(SDLC), PAR&SDLC=(58,AA,N,Y,Y,017,00067,TURN)
The system manager operator requires one PAR&SMOP keyword.
You can specify up to 3 parameters:
The audio signal notifies the operator of a pending message.
The parameter is optional. The parameter value can be Y, to use the audio signal, or N, not to use it. The default is N.
The video signal notifies the operator of a pending message.
The parameter is optional. The parameter value can be Y, to use the video signal, or N, not to use it. The default is N.
This parameter specifies the directory where the system manager operator files are located in the production workstation at run-time.
The parameter is required and applies only to DOS workstations. The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
LWSCONF NAME=AA, TYPE=DOS, SERVER=SMGR, PAR&SMGR=(,,,SMGRPRF,C:\SMGR\,C:\SMGR\,C:\SMGR\,C:\SMGR\), /* System manager operator server definition. Example. */ SERVER=(SMOP), PAR&SMOP=(Y,Y,C:\SMOP\FILES\)
|
The system manager server requires one PAR&SMGR keyword.
|
You can specify up to 10 parameters:
The parameter applies only when using alerts. In this case, it is required. The parameter value is a string of up to 2 alphanumeric characters.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
This parameter specifies the directory where the file to temporary store alerts is located in the production workstation at run-time. The file is automatically created by the system manager server at run-time, in the path you specify.
The parameter value is a string of up to 30 alphanumeric characters.
On LANDP for OS/2, LANDP for Windows, LANDP for DOS, the format must be:
D:\[directory1\[directory2\[directory3\]]]
On LANDP for Linux, the parameter value is the complete path, including subdirectories. It must not exceed 30 characters, and must be enclosed in single quotation marks. A backslash character must be present after the last subdirectory name. The format must be:
/directory1/[directory2/[directory3/]]
A maximum of three levels is permitted for the path.
If only one system manager server profile is defined, the parameter is optional. The parameter value is a string of up to 8 alphanumeric characters, and must match the value assigned in the NAME keyword in the SMGRPRF vector.
This parameter specifies the directory where the user profiles are located in the production workstation at run-time.
If you have defined user profiles, the parameter is required. The parameter value is a string of up to 30 alphanumeric characters. On LANDP for OS/2, LANDP for Windows, LANDP for DOS, the format must be:
D:\[directory1\[directory2\[directory3\]]]
On LANDP for Linux, the parameter value is the complete path, including subdirectories. It must not exceed 30 characters, and must be enclosed in single quotation marks. A backslash character must be present after the last subdirectory name. The format must be:
/directory1/[directory2/[directory3/]]
A maximum of three levels is permitted for the path.
This parameter specifies the directory where the common data is located in the production workstation at run-time.
The parameter is required. The parameter value is a string of up to 30 alphanumeric characters. On LANDP for OS/2, LANDP for Windows, LANDP for DOS, the format must be:
D:\[directory1\[directory2\[directory3\]]]
On LANDP for Linux, the parameter value is the complete path, including subdirectories. It must not exceed 30 characters, and must be enclosed in single quotation marks. A backslash character must be present after the last subdirectory name. The format must be:
/directory1/[directory2/[directory3/]]
A maximum of three levels is permitted for the path.
This parameter specifies the directory where the log file is located in the production workstation at run-time.
If log support is used, the parameter is required. The parameter value is a string of up to 30 alphanumeric characters. On LANDP for OS/2, LANDP for Windows, LANDP for DOS, the format must be:
D:\[directory1\[directory2\[directory3\]]]
On LANDP for Linux, the parameter value is the complete path, including subdirectories. It must not exceed 30 characters, and must be enclosed in single quotation marks. A backslash character must be present after the last subdirectory name. The format must be:
/directory1/[directory2/[directory3/]]
A maximum of three levels is permitted for the path.
This parameter specifies the directory where the file containing the record definitions is located in the production workstation at run-time.
The parameter is required if you have specified COMDTVAL = Y or APPDTVAL = Y in the SMGRPRF vector, or if the system manager server will perform record validation.
The parameter value is a string of up to 30 alphanumeric characters.On LANDP for OS/2, LANDP for Windows, LANDP for DOS, the format must be:
D:\[directory1\[directory2\[directory3\]]]
On LANDP for Linux, the parameter value is the complete path, including subdirectories. It must not exceed 30 characters, and must be enclosed in single quotation marks. A backslash character must be present after the last subdirectory name. The format must be:
/directory1/[directory2/[directory3/]]
A maximum of three levels is permitted for the path.
The parameter specifies the drive where the FBSS#GDT backup is located in the production workstation at run-time.
The parameter is optional. The parameter value is an alphabetic character. The customization program provides no default for this parameter.
This parameter is not supported on Linux. If required, the value should be entered on the -D loader parameter (see "System manager server").
This parameter specifies the Netview operator ID that receives messages at the host computer.
The parameter is optional. The parameter value is a string of up to 8 ASCII characters. The customization program provides no default for this parameter.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(SDLC), PAR&SDLC=(58,AA,N,Y,Y,017,00067,TURN), /* System manager server definition. Example. */ SERVER=(SMGR), PAR&SMGR=(AA,SDL,C:\SMGR\ALERTS\,PROFSMGR, C:\SMGR\USERS\,C:\SMGR\COMMON\, C:\SMGR\LOG\,C:\SMGR\RECORDS\)
|
The TCP/IP wide area communications server requires one PAR&TCP keyword
for the workstation that provides services, and one SES&TCP keyword for
each line of the EHCTCP.INI file. This file is used to map LANDP
sessions with SNA and PPC servers to TCP/IP protocols, ports and internet
addresses.
|
You can specify up to 3 parameters.
The parameter applies only to DOS workstations. The parameter value can range from 5 through 2048. The default is 5. The number of sessions required is one for each user session, plus two for each Dependent LU Server (DLUS).
The parameter value can be:
The default is N.
The parameter value can be:
The default is N.
You can specify 3 or 4 parameters:
This parameter is required. It is a string of up to 8 characters. One or more characters can be replaced with '#' to indicate that this definition applies to names with any character in that position. The last character can be '*' to indicate that this definition applies to names with any suffix in place of the '*'. See below, for some examples of the parameter's use.
This parameter is required. See below, for some examples of the parameter's use.
This parameter is required. See below, for some examples of the parameter's use.
An optional comment of up to 30 characters enclosed in quotes.
These generate a line in the EHCTCP.INI file of the form:
Name= Type: Value ;Comment
The purpose of the EHCTCP.INI file is to provide the information required to map LANDP sessions with SNA and PPC servers to TCP/IP protocols, services, ports and internet addresses. Supported protocols include TELNET tn3270, MPTN(AnyNet), and TCP/IP sockets. IP addresses can be in dotted notation, or can be names that are to be resolved by the domain name server or HOSTS file.
SNA server sessions are identified by 'SNA', followed by the workstation ID, followed by the session ID. For example: SNAGW12 is session 12 on workstation GW.
PPC server sessions are identified by the local and partner LU aliases.
Starting from the beginning of the file, the first match to the session identifier is used. '#' represents any character and '*' represents any suffix. For example, SNAGW12 will match SNA##12 and SNAGW*, whichever is first.
Some of the following examples have been formatted for ease of readability. In SES&TCP statements, all blanks separating parameters must be removed. The last three examples show valid formatting.
To aid clarity, a mixture of uppercase characters, lowercase characters, and blanks, is allowed in the EHCTCP.INI file. However, the file is treated as uppercase in use, because all network names must be uppercase.
This example shows how to map EMU3270 server sessions (SNA sessions 51 through 55) from all workstations in the workgroup to the TELNET tn3270 protocol and service on a host called winmvs20.
SES&TCP=(SNA##5#, Telnet, winmvs20, 'All EMU3270 -> winmvs20 TELNET'),
The TCP/IP port number associated with the telnet service in the local TCP/IP SERVICES file is used. If no such association exists, port 23 is used.
This example shows the definitions required to map a PPC server session to MPTN (AnyNet) protocol. The local LU alias is IYAET000, the partner LU alias is IYCKSPP1 and the mode is CICSISC0.
The first line maps the partner LU alias to the port and IP address to be used. The IP address is in dotted notation just to demonstrate the range of possibilities.
The second line maps the local LU alias to the fully qualified SNA network name of the LU.
The third line maps the partner LU alias to the fully qualified SNA network name of the LU.
The last line defines the LU6.2 conversation mode. The value parameter must be two or three numbers separated by a period. The first is the total number of sessions (in the range 1 through 32767), the second is the number of contention winner sessions (in the range 0 through number of sessions), and the third is the maximum RU size (in the range 256 through 65536). If the third number is omitted, or is set to 0, an implementation-defined default will be used for the maximum RU size.
SES&TCP=(IYCKSPP1,MPTN, 9.20.101.41, 'TCP/IP service and IP address'), SES&TCP=(IYAET000, LocalLU, GBIBMIYA.IYAET000, 'Local LU fully qualified name'), SES&TCP=(IYCKSPP1, RemoteLU, GBIBMIYA.IYCKSPP1, 'Partner LU fully qualified name'), SES&TCP=(CICSISC0, MODE, 10.5.4096, '10 sessions, 5 winners, 4K RU'),
The TCP/IP port number associated with the MPTN service in the local TCP/IP SERVICES file is used. If no such association exists, port 397 is used.
Note that, on Linux, port numbers below 1024 can only be used by programs with root permissions. You can either run EHCTCP with root permissions, or configure it and the partner host to use an alternative port number. You can override the assignment of port number to service with the line below:
SES&TCP=(Mptn, Service, Port50397, 'Alternative MPTN port'),
This example shows the definitions that are required to map SNA server sessions to MPTN (AnyNet) protocol. This requires a dependent LU server (DLUS) on the host computer for which we have used a local alias of DLUS1 (DLUS is a required prefix for this name).
The first line maps all remaining SNA sessions (that is, not the EMU3270 sessions mapped earlier) to a pool of 8 LU numbers (2 through 9) on a dependent LU server with local alias DLUS1. DLUS is a required prefix for this name. The value parameter can be a single LU number in the range 2 through 255, or a pair of numbers that define an LU pool. In the latter case, the first number defines the lowest LU number in the pool and the second number defines the size of the pool. This line could be replaced by many lines, each mapping only one session to an LU number, or some combination of individual and pooled LU numbers.
The second and third lines define the local and host fully qualified SNA network names that should be used for communication with the DLUS.
The fourth line gives the protocol and IP address to be used.
The fifth and sixth lines define the XID and the PU name that are required for communication with the DLUS.
SES&TCP=(SNA*, DLUS1, 2.8, 'Map to pool of LU numbers 2-9'), SES&TCP=(DLUS1, LocalLU, GBIBMIYA.IYCUT310, 'Local node fully qualified name'), SES&TCP=(DLUS1, RemoteLU, GBIBMIYA.IYCUCDRM, 'Host node fully qualified name'), SES&TCP=(DLUS1, Mptn, winmvs2a, 'TCP/IP service and IP address'), SES&TCP=(DLUS1, XID, 05DE3001, 'XID'), SES&TCP=(DLUS1, PUname, IYCUR301, 'PU name'),
Note that, when using the TCP/IP wide area communications server, the depenent LU names configured in VTAM must have a common alphanumeric prefix and a numeric suffix with a constant difference between the suffix and the LOCADDR.
For example:
IYCKT300 LU LOCADDR=2 IYCKT301 LU LOCADDR=3 IYCKT327 LU LOCADDR=29 IYCKT481 LU LOCADDR=183
This example shows the definition that is required to allow the connection of incoming TCP/IP sessions. This is required for PPC server 'contention-loser' sessions and for SNA-dependent LU sessions (see the example above).
The value is the number of connections that can be in the process of connecting at any one time (not the number of connections). A value of at least 2 is required for MPTN sessions. Increase the value if you find that incoming (contention-loser) PPC sessions fail to connect.
SES&TCP=(Listen, Mptn, 2, 'Listen for 2 MPTN sessions'),
The PPC server OP request has a complex data field. However, it can be left completely blank if the default values are defined in the EHCTCP.INI file. The use of defaults is particularly appropriate when mapping PPC server sessions to TCP/IP sockets, because the only information that is needed is the TCP/IP address of the partner, and the port number to use.
The following definitions are required for a 'contention-winner' session :
SES&TCP=(FBSSLUPA, Port54321, testpc21), SES&TCP=(FBSSLULO, LocalLU, Dummy), SES&TCP=(FBSSLUPA, RemoteLU, Dummy), SES&TCP=(FBSSMODE, Mode, 1.0),
The corresponding 'contention-loser' session requires the following INI file definition:
SES&TCP=(Listen, Port54321, 1),
LWSCONF NAME=AB, TYPE=OS/2, PRODLVL=L60, /* PPC server over TCP/IP */ SERVER=(PPC,,N), /* TCP/IP wide area communications server */ SERVER=(EHCTCP,,N), PAR&TCP=(,,Y), SES&TCP=(Listen,Mptn,2,'Listen for MPTN sessions'), SES&TCP=(IYAET000,LocalLU,GBIBMIYA.IYAET000,'Local LU alias'), SES&TCP=(IYCKSPP1,RemoteLU,GBIBMIYA.IYCKSPP1,'Partner LU alias'), SES&TCP=(IYCKSPP1,Mptn,winmvs20.ibm.com,'Port and IP address'), SES&TCP=(CICSISC0,MODE,2.1,'2 sessions, 1 winner'), /* PPC client */ CLIENT=(PPC,AB)
LWSCONF NAME=AA, TYPE=DOS, PRODLVL=L60, /* SNA server over TCP/IP */ SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), /* TCP/IP wide area communications server */ SERVER=(EHCTCP,,N), PAR&TCP=(5,Y,), SES&TCP=(SNA##5#,Telnet,winmvs20,'Emulator session TELNET'), /* Emulator */ SERVER=(EMU32701), PAR&3270=(N,N), SES&3270=(AA,1,,,ATR,DIS,KBD)
LWSCONF NAME=AC, TYPE=OS/2, PRODLVL=L60, /* SNA server over TCP/IP */ SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), /* TCP/IP wide area communications server */ SERVER=(EHCTCP,,N), PAR&TCP=(,Y,), SES&TCP=(Listen,Mptn,1,'Listen for MPTN sessions'), SES&TCP=(SNA####,DLUS1,2.20,'Map all sessions to pool of 20'), SES&TCP=(DLUS1,LocalLU,GBIBMIYA.IYCUT310,'Local LU alias'), SES&TCP=(DLUS1,RemoteLU,GBIBMIYA.IYCUCDRM,'Partner LU alias'), SES&TCP=(DLUS1,Mptn,winmvs20.ibm.com,'Port and IP address'), SES&TCP=(DLUS1,XID,05DE3001,'XID'), SES&TCP=(DLUS1,PUname,IYCUR301'PU name'), /* SNA client */ CLIENT=(SNA01,AC), SES&SNA=(AC,01,,,)
The TRDLC server requires one PAR&TKR keyword.
You can specify up to 23 parameters:
The parameter is optional. The parameter value ranges from 16 to 216 (1 buffer = 272 bytes in memory, 256 bytes of data). The default is 48.
The parameter is optional. The parameter value is a hexadecimal number of two digits:
The value 00 is not valid. The default is 04, which is the default SAP used by SNA nodes and identifies the path control as the data link user.
The parameter is optional. The parameter value is a hexadecimal number of two digits:
The value 00 is not valid. The default is 04, which is the default SAP used by SNA nodes and identifies the path control as the data link user.
This parameter specifies the locally administered address for the workstation.
The parameter is required. The parameter value is a hexadecimal number of eight digits. It ranges from 00000000 to 7FFFFFFF.
The address becomes a hexadecimal number of twelve digits:
Note that the workstation address must not be the same as the host address.
This parameter specifies the locally administered address for the host.
The parameter is required. The parameter value is a hexadecimal number of eight digits. It ranges from 00000000 to 7FFFFFFF. The address becomes a hexadecimal number with twelve digits:
Note that the specified address must not be the same as the address of the workstation.
The parameter is optional. The parameter value is a hexadecimal number of three digits, and must match the information in the host computer. The default is 017.
The parameter is optional. The parameter value is a hexadecimal number of five digits, and must match the information in the host computer. The default is 00000.
The combination of the constant X'0200', the block number, and the identification number results in the SNA exchange identifier (XID).
The parameter is optional. The parameter value is a hexadecimal number of ten digits.
If specified, the SNA server validates the SSCP name that receives in the ACTPU (activate physical unit) command.
9 to 23. System Service Control Point (SSCP) name. See information for parameter 8.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), /* Token-Ring server definition. Example. */ SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), CLIENT=(SNA01,AA), SES&SNA=(AA,01,001,TKR)
The virtual file support requires one PAR&VFIL keyword.
You can specify up to 4 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only.
The parameter value can be:
The parameter is required. This parameter specifies the virtual drive assigned to the virtual file support in the workstation.
The parameter value ranges from C to Z.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* Virtual File Support server definition. Example. */ SERVER=(VFILE), PAR&VFIL=(AA,016,TKR,V) LWSCONF NAME=BB, TYPE=DOS, /* Virtual File Support server definition. Example. */ SERVER=(VFILE), PAR&VFIL=(AA,017,TKR,V)
The virtual volume support requires one PAR&VVOL keyword.
You can specify up to 27 parameters:
The parameter is required, unless the workstation is directly attached to the 4700 system via DCADLC, and is the same workstation where the virtual volume support installed. The parameter value is a string of up to 2 alphanumeric characters.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only.
The parameter value can be:
The parameter is optional. The parameter value can be Y, to select PUBLIC1 virtual volume, or N, tonot to select it. The default is N.
Public virtual volume n selection (n = 2, 3, ... , 24).
These parameters are optional. The parameter value can be Y, to select PUBLICn virtual volume, or N, to not select it. The default is N.
At least one public virtual volume (n = 1, 2, ... ,24) must be selected.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* Virtual Volume Support server definition. Example. */ SERVER=(RDVVOLS), PAR&VVOL=(AA,013,TKR,Y,Y,Y,N) LWSCONF NAME=BB, TYPE=DOS, /* Virtual Volume Support server definition. Example. */ SERVER=(RDVVOLS), PAR&VVOL=(AA,014,TKR,Y,Y,Y,N)
The X25DLC server, which supports the IBM PC X.25 Communications Adapter, requires one PAR&X25D keyword.
The X25DLC2 server, which supports the IBM X.25 Interface Coprocessor/2, requires one PAR&X252 keyword. To use the IBM X.25 Interface Coprocessor/2, it is required to run the customization program provided with the IBM X.25 Interface Coprocessor/2 support program. For information, refer to the User's Guide and the Programmer's Reference manuals of that product.
To use the X.25 support through the native X.25 server, it is necessary to specify one SES&NSVC keyword for each switched virtual circuit used by the client workstation. See Native X.25 server definitions.
To use the X25DLC support through the SNA server, it is necessary to specify one SES&SPVC keyword for each permanent circuit, and one SES&SSVC keyword for each switched circuit, managed by the SNA server. See SNA server definitions.
You can specify up to 16 parameters:
The parameter is optional. The parameter value ranges from 20 to 2000 (1 buffer = 144 bytes in memory, 128 bytes of data). The default is 20.
The parameter is optional. The parameter value can be Y, to include your telephone number in the packet call, or N, not to include it. The default is Y.
Number of virtual circuits and calls |
---|
Parameters 3, 4, 5, and 6 specify, respectively, the number of:
The sum of the permanent virtual circuits, incoming virtual calls, both-way virtual calls, and outgoing virtual calls, must be between 1 and 20. Note that you cannot assign 0 to the four parameters, but at least one of them must be assigned a non-zero value. |
The parameter is optional. The parameter value ranges from 0 to 20.
The parameter is optional. The parameter value ranges from 0 to 20.
The parameter is optional. The parameter value ranges from 0 to 20.
The parameter is optional. The parameter value ranges from 0 to 20.
Logical channel identification |
---|
Parameters 7, 8, and 9 specify, respectively, the logical channel identification for: They are assigned in ascending order with the lowest being permanent virtual circuits:
The circuit IDs are assigned consecutively, starting with the logical channel ID specified for the first circuit of each type. Therefore, if you had three permanent virtual circuits, the logical channel ID of the first incoming virtual call must be at least 4. Logical channel IDs cannot overlap. The maximum number of circuits is 20.
|
If the number of incoming virtual calls is different from zero, the parameter is required. The parameter value ranges from 1 to 4095.
If the number of both-way virtual calls is different from zero, the parameter is required. The parameter value ranges from 1 to 4095.
If the number of outgoing virtual calls is different from zero, the parameter is required. The parameter value ranges from 1 to 4095.
This parameter specifies the maximum number of messages that the workstation can send to the network before receiving an answer at frame level.
The parameter is optional. The parameter value ranges from 1 to 7. The default is 7.
This parameter specifies the number of frame retransmission attempts after an error occurs.
The parameter is optional. The parameter value ranges from 1 to 20. The default is 3.
This parameter specifies the amount of time, in hundredths of seconds, the system waits for an answer before retrying the transmission.
The parameter is optional. The parameter value ranges from 100 to 500. The default is 150.
This parameter specifies the interrupt number selected on the X.25 communications adapter card when it was installed in the workstation.
The parameter is optional. The parameter value ranges from 2 to 4. The default is 3.
The parameter is required. The parameter value is a number of three digits. Valid values for your country can be obtained from the telecommunications company.
The parameter is required. The parameter value ranges from 0 to 9. Valid values for your country can be obtained from the telecommunications company.
The parameter is required. The parameter value is a number of up to 11 digits.
You can specify up to 8 parameters:
The parameter is optional. The parameter value ranges from 20 to 2000 (1 buffer = 144 bytes in memory, 128 bytes of data). The default is 20.
The parameter is optional. The parameter value can be Y, to include your telephone number in the packet call, or N, not to include it. The default is Y.
This parameter specifies the amount of memory, in KB, reserved for the IBM X.25 Co-Processor Support program.
The parameter is optional. The parameter value ranges from 7 to 99.
The recommended value is: 6KB + (n ÷. 2)KB, where n is the number of virtual circuits. If you specify a value that is too low, unpredictable errors can occur. The default is 7.
The parameter is optional. The parameter value ranges from 0 to 7. The default is 0.
IBM X.25 and other IBM Realtime Interface Co-Processor adapters are numbered sequentially, starting with 0, according to the physical slots into which they are plugged in the workstation. Empty slots and slots used by other adapters are not counted.
This parameter specifies a profile created with the customization program provided with the X.25 Co-Processor Support program.
If only one X25DLC2 server profile is defined, the parameter is optional. The parameter value is a string of up to 8 alphanumeric characters.
The parameter is optional. The parameter value is a number of three digits. Valid values for your country can be obtained from the telecommunications company. The default is 000.
The parameter is optional. The parameter value ranges from 0 to 9. Valid values for your country can be obtained from the telecommunications company. The default is 0.
The parameter is required. The parameter value is a number of up to 11 digits.
/* Following is Example 1, which corresponds to keyword */ /* specifications for the X25DLC server. */ LWSCONF NAME=AA, TYPE=DOS, SERVER=(X25NAT##), CLIENT=(X25NAT01,AA), SES&NSVC=(AA,01,OUTG,INXB,111111111), /* Definition using the IBM PC X.25 Communications Adapter. */ SERVER=(X25DLC), PAR&X25D=(20,Y,1,2,4,4,2,4,8,7,3,150,3,214,1, 231020107)
/* Following is Example 2, which corresponds to keyword */ /* specifications for the X25DLC server. */ LWSCONF NAME=AA, TYPE=DOS, SERVER=(X25NAT##), CLIENT=(X25NAT01,AA), SES&NSVC=(AA,01,OUTG,INXB,111111111), /* Definition using the IBM X.25 Interface Coprocessor/2. */ SERVER=(X25DLC2), PAR&X252=(20,Y,7,3,PROFILE,214,1,231020107)
You can specify up to 2 parameters:
The parameter value can be Y, to use HLLAPI, or N, not to use HLLAPI. The default is N.
The parameter does not apply to DBCS mode. It is optional. The parameter value can be Y, to use the cryptographic support, or N, not to use it. The default is N.
You can specify up to 13 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
The parameter is required. The parameter value ranges from 1 to 5, and must be unique for the workstation where the 3270 emulator will be installed. The value must match the 3270 emulator suffix, which identifies the session to be used (x value in EMU3270x servername).
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
This parameter identifies the color attributes table used for the workstation display.
The parameter value is a string of three alphanumeric characters, which is the identifier of the color attributes table. It must match the value assigned in the EXTEN keyword in a DISPLATT vector with TYPE = 3270. Specify ATR to use the default table.
This parameter identifies the table that is used to translate from host computer EBCDIC to personal computer system ASCII, when receiving from the host computer.
The parameter value is a string of three alphanumeric characters, which is the identifier of the translation table. It must match the value assigned in the EXTEN keyword in a XLATETBL vector with TYPE = EA3270. Specify DIS to use the default table.
In DBCS mode, this parameter applies only to single-byte characters (SBCS). DBCS characters are translated by the DBTR server.
This parameter identifies the translation table used for the workstation keyboard. The parameter value is a string of three alphanumeric characters, which is the identifier of the translation table. It must match the value assigned in the EXTEN keyword in a KBD3270 vector. Specify KBD to use the default table.
There must also be an XLATETBL vector of type AE3270 and a KBD3270X vector with keyword EXTEN.
This parameter identifies the session that is used for the application program in the host computer. The parameter is optional. If specified, it overrides the value assigned in the E3270HKx keyword in the DEFAULTS vector. The parameter value is a string of up to 8 alphanumeric characters.
This parameter specifies the height (number of rows) of the 3270 alternate screen to be emulated. The value can be in the range 24 through 49. This should not include the operator information area line at the bottom of the screen. The default is 24.
This parameter specifies the width (number of columns) of the 3270 alternate screen to be emulated. The value can be 80 or 132. The default is 80. For LANDP for Windows workstations, only 80 is supported.
This parameter indicates whether blinking text is supported. The parameter value can be Y (use blinking) or N (no blinking). The default is N.
This parameter indicates whether the 3270 emulator should handle the Print Screen key. The parameter value can be Y or N. The default is Y.
This parameter specifies the buffer size to be used for communication with the host computer. The parameter value can be in the range 2048 through 4096. The default is 2048. The parameter value specified must match the RU size detailed in the bind session.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* 3270 emulator server definition. Example. */ SERVER=(EMU32701), PAR&3270=(N,N), SES&3270=(AA,1,011,TKR,ATR,DIS,KBD,,27,132,Y,N,4096) LWSCONF NAME=BB, TYPE=DOS, /* 3270 emulator server definition. Example. */ SERVER=(EMU32701), PAR&3270=(N,N), SES&3270=(AA,1,012,TKR,ATR,DIS,KBD,,,,,,)
You can specify up to 5 parameters:
This parameter specifies the printer to be used for output.
The parameter is optional. The parameter value can be:
The default is 1.
The parameter value is a string of three alphanumeric characters, which is the identifier of the EBCDIC to ASCII translation table. It must match the value assigned in the EXTEN keyword in a XLATETBL vector with TYPE = EA3287.
In DBCS mode the parameter does not apply. It is optional. The default is PRT.
The parameter value is the extension of the file containing the printer 3287 attributes table. It must match the value assigned in the EXTEN keyword in the P3287ATT vector.
It is optional. The default is TAB.
This parameter specifies the amount of time, in seconds, the 3287 printer emulator waits before checking for a file to be printed.
The time interval you specify is used only when the 3287 printer emulator is idle. However, when there is no file to be printed, a short interval deteriorates performance.
The parameter is optional. The parameter value ranges from 1 to 60. The default is 15.
The parameter is optional. The parameter value ranges from 1 to 3. Specify:
The default is the number of parallel ports available on the workstation.
You can specify up to 9 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
The parameter is required. The parameter value ranges from 1 to 5, and must be unique for the workstation where the 3287 printer emulator will be installed.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only when the SNA services are provided from a DOS workstation. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
The parameter is optional. The parameter value can be:
The default is 1.
This parameter specifies the default characters density, in characters per inch (CPI), for the 3287 printer emulator. The density can be modified at run-time using the CM command of the operator interface, or the local resource manager server.
The parameter is optional. The parameter value can be:
The default is 17.
When working with IBM 5575 Printer or IBM 5577 Printer, condensed density means 15 CPI.
This parameter must match the length, in inches, of the paper page to be used, and the switch settings in the printer attached to the workstation.
The parameter is optional. The parameter value can be 11 or 12.
The default is 11.
The parameter is optional. The parameter value can be Y, to perform a form feed before every listing, or N, not to perform it. The default is N.
This parameter identifies the session that is used for the application program in the host computer.
The parameter is optional. If specified, it overrides the value assigned in the E3287SIx keyword in the DEFAULTS vector. The parameter value is a string of up to 8 alphanumeric characters.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* 3287 printer emulator server definition. Example. */ SERVER=(EMU3287), PAR&3287=(1,PRT,TAB), SES&3287=(AA,1,017,TKR,1,17,11,N) LWSCONF NAME=BB, TYPE=DOS, /* 3287 printer emulator server definition. Example. */ SERVER=(EMU3287), PAR&3287=(1,PRT,TAB), SES&3287=(AA,1,018,TKR,1,17,11,N)
You can specify up to 17 parameters:
The parameter is optional. The parameter value can be:
The default is N.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the printer device driver sends data to the port when it receives data to be printed.
Select a lower baud rate, if necessary, based on the cable length and the working environment.
The parameter applies only when using port 1. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is 4722.
The parameter applies only when using port 1. It is optional. The parameter value can be Y, to specify that REMS is installed, or N, to specify that REMS is not installed. The default is N.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the printer device driver sends data to the port when it receives data to be printed.
Select a lower baud rate, if necessary, based on the cable length and the working environment.
The parameter applies only when using port 2. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is 4722.
The parameter applies only when using port 2. It is optional. The parameter value can be Y, to specify that REMS is installed, or N, to specify that REMS is not installed. The default is N.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the printer device driver sends data to the port when it receives data to be printed.
Select a lower baud rate, if necessary, based on the cable length and the working environment.
The parameter applies only when using port 3. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is 4722.
The parameter applies only when using port 3. It is optional. The parameter value can be Y, to specify that REMS is installed, or N, to specify that REMS is not installed. The default is N.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the 4712 or 4722 printer device driver sends data to the port when it receives data to be printed.
Select a lower baud rate, if necessary, based on the cable length and the working environment.
The parameter applies only when using port 4. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is 4722.
The parameter applies only when using port 4. It is optional. The parameter value can be Y, to specify that REMS is installed, or N, to specify that REMS is not installed. The default is N.
You can specify up to 6 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
This value is used by a server or application to identify the printer session.
The parameter is required. The parameter value is a string of two alphanumeric characters. For each workstation, it must be unique for this service, and must match the ## value of the financial printer server in the CLIENT keyword.
The parameter is required. The parameter value can be:
The value must match the port usage in the PAR&47X2 keyword for the server workstation.
The parameter is required. The parameter value can be:
The value must match the port usage in the PAR&47X2 keyword for the server workstation, provided it runs DOS, OS/2, or Windows. If the parallel port is used, only value C can be specified.
This parameter specifies the maximum number of KB to be printed at a time.
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
The value to be used for each printer is the maximum value specified for all the sessions defined for that printer.
This parameter specifies where the device is attached.
The parameter is required for Linux workstations. If the financial printer services are provided from a DOS, OS/2, or Windows workstation, the parameter does not apply.
If a TTY device is specified, the parameter value can be the following, within quotes:
\dev\tty\string
where string is a string of up to 18 characters, without blanks.
LWSCONF NAME=AA, TYPE=DOS, /* 4712/22 printer server definition. Example. */ SERVER=(PR47X2##), PAR&47X2=(N,C,9600,4722,N,C,9600,4722,Y) LWSCONF NAME=BB, TYPE=OS/2, /* 4712/22 printer client definition. Example. */ CLIENT=(PR47X2JO,AA), SES&47X2=(AA,JO,1,C)
The 4721 printer requires one PAR&SP21 keyword to define the printer server parameters, and one PAR&PT21 keyword to define the printer integrator parameters.
You can specify two parameters:
This parameter specifies how many 4721 printers are managed by the server. The parameter value ranges from 1 to 3. The default is 1.
This parameter specifies the first two characters of the 4721 terminal address that is used for the connection between the 4721 printer server and the served 4721 printers.
The parameter is optional. The parameter value must be unique in the network, for each 4721 printer server and the served 4721 printers. This enables you to configure several LANDP workgroups in the same network where every workstation with the 4721 printer server has the same ID.
The parameter value is a string of two alphanumeric characters. The default is the name of the workstation (workstation ID) where the 4721 printer server is installed.
The customization program creates an ASCII run-time file, named DEVSP47.TAB, which contains the information.
You can specify up to 8 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
This parameter identifies the 4721 printer to be used.
The parameter is required. The parameter value ranges from 1 to 3, and must take into account the value assigned in the PAR&SP21 keyword.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
If you do not wish to use the session, omit the parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with more than one X.25DLC, to specify the particular X.25DLC used, the parameter value ranges from 1 to 999 and must match the virtual circuit definition defined for the SNA server in the SES&SPVC or SES&SSVC keyword.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
If you do not wish to use the session, omit the parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with more than one X.25DLC, to specify the particular X.25DLC used, the parameter value ranges from 1 to 999 and must match the virtual circuit definition defined for the SNA server in the SES&SPVC or SES&SSVC keyword.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
If you do not wish to use the session, omit the parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with more than one X.25DLC, to specify the particular X.25DLC used, the parameter value ranges from 1 to 999 and must match the virtual circuit definition defined for the SNA server in the SES&SPVC or SES&SSVC keyword.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,N), PAR&SNA=(APPL,SRV), SERVER=(TRDLC), PAR&TKR=(48,04,04,00999999,00111111,017,00000), /* 4721 self-Service Document printer server definition. Example. */ SERVER=(SP4721##), PAR&SP21=(1), CLIENT=(SP4721##,AA), SERVER=(PT4721), PAR&PT21=(AA,1,005,TKR)
|
The IBM 4731, 4738, 4739 Personal Banking Machine (PBM) requires one
PAR&4731 keyword to define the PBM server.
|
You can specify up to 6 parameters:
The parameter is optional. It is required, if SNA services will be used.
The parameter value is a string of up to 2 alphanumeric characters.
This parameter specifies the directory where the IBM 4731, 4738, 4739 PBM files are located in the production workstation at run-time.
The parameter is required. The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
If you do not wish to use the session, omit the parameter.
The parameter applies only to DOS workstations. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
If you not wish to use the session, omit this parameter.
The parameter applies only when the SNA services are provided from a DOS workstation. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,Y), PAR&SNA=(ANY,SRV), SERVER=(SDLC,,N), PAR&SDLC=(8,C1,Y,N,N,03D,12345,CRTS), /* 4731, 4738, 4739 Personal Banking Machine server definition. Example. */ SERVER=(SS#####,,N), PAR&4731=(AA,C:\PROD\FBSS\WORK\,002,SDL,001,SDL) LWSCONF NAME=BB, TYPE=DOS, /* 4731, 4738, 4739 Personal Banking Machine client definition. Example. */ CLIENT=(SS#####,AA)
|
The IBM 4733 Teller Assist Unit requires one PAR&4733 keyword.
|
You can specify up to 2 parameters:
LWSCONF NAME=AA, TYPE=DOS, /* 4733 Teller Assist Unit server definition. Example. */ SERVER=(DTAU4733), PAR&4733=(9600,2) LWSCONF NAME=BB, TYPE=DOS, /* 4733 Teller Assist Unit client definition. Example. */ CLIENT=(DTAU4733,AA)
|
The IBM 4737 Self-Service Transaction Station requires one PAR&4737
keyword, and one PAR&PBMS keyword to define the PBM support.
|
You can specify one parameter:
This parameter specifies the directory where the IBM 4737 files are located in the production workstation at run-time.
The parameter is required. The parameter value is a string of up to 30 alphanumeric characters. The format must be:
D:\[directory1\[directory2\[directory3\]]]
A maximum of three levels is permitted for the path.
You can specify up to 3 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
When SNA services are provided by the SNA server from a DOS workstation without LU pooling, use this parameter to specify the LU number. The parameter value must be in the range 1 through 254, and must be unique for the data link control (DLC) or virtual circuit.
When SNA services are provided by the SNA server with LU pooling, use this parameter to the specify the ID of the LU pool. The parameter value must be two characters, the first being alphabetic and the second alphanumeric.
When SNA services are provided by the TCP/IP server, or by a non-DOS SNA server without LU pooling, omit this parameter.
The parameter applies only if the SNA services are provided by a DOS workstation. In this case, it is required except for workstations that have one DLC only, which is not X.25.
For workstations with DLC other than X.25, to specify the type of DLC used, the parameter value can be:
For workstations with DLC being X.25, the parameter value is the number you have assigned as the virtual circuit definition identification in a SES&SPVC keyword or SES&SSVC keyword.
LWSCONF NAME=AA, TYPE=DOS, SERVER=(SNA##,,Y), PAR&SNA=(ANY,SRV), SERVER=(SDLC,,N), PAR&SDLC=(8,C1,Y,N,N,,,CRTS), /* 4737 Self-Service Transaction Station server definition. Example. */ SERVER=(SS######,,N), PAR&4737=C:\4737PBM\, SERVER=(PBMS,,N), PAR&PBMS=(AA,002,SDL), CLIENT=(SS######,AA) LWSCONF NAME=BB, TYPE=DOS, /* 4737 Self-Service Transaction Station client definition. Example. */ CLIENT=(SS######,AA)
You can specify up to 12 parameters:
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the printer device driver sends to the port when it receives data to be printed.
Select a lower baud rate, if necessary, based on the cable length and the working environment.
The parameter applies only when using port 1. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is 4748.
The parameter is optional, and applies only when the printer for port 1 is 9055. The parameter value can be Y, to specify that REMS is installed, or N, to specify that REMS is not installed. The default is N.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the printer device driver sends to the port when it receives data to be printed.
Select a lower baud rate, if necessary, based on the cable length and the working environment.
The parameter applies only when using port 2. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is 4748.
The parameter is optional, and applies only when the printer for port 2 is 9055. The parameter value can be Y, to specify that REMS is installed, or N, to specify that REMS is not installed. The default is N.
This parameter specifies the printer device driver.
The parameter applies only to OS/2 workstations. It is optional. The parameter format is xxxxxxxx.yyy. The default is COMDMA.SYS.
This parameter specifies whether alerts are required. It is optional. The parameter value can be Y, to specify that alerts are required, or N, to specify that alerts are not required. The default is N.
This parameter specifies whether code conversion is supported. It is optional. The parameter value can be:
The default is Y.
This parameter specifies the UDC file name. It is optional. The parameter format is xxxxxxxx.yyy. The default is PR4748.UDC.
You can specify up to 5 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
This value is used by a server or application to identify the printer session.
The parameter is required. The parameter value is a string of two alphanumeric characters. For each workstation, it must be unique for this service.
The parameter is required. The parameter value can be:
The value must match the port usage in the PAR&4748 keyword for the server workstation.
The parameter is required. The parameter value can be:
The value must match the port usage in the PAR&4748 keyword for the server workstation.
This parameter specifies the maximum number of KB to be printed at a time.
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
The value to be used for each printer is the maximum value specified for all the sessions defined for that printer.
LWSCONF NAME=AA, TYPE=DOS, /* 4748 printer server definition. Example. */ SERVER=(PR4748##,,Y), PAR&4748=(C,9600) LWSCONF NAME=BB, TYPE=OS/2, /* 4748 printer client definition. Example. */ CLIENT=(PR474801,AA), SES&4748=(AA,01,1,C)
The 4770 printer server requires one PAR&4770 keyword, and as many SES&4770 keywords as printer server sessions are to be defined in the client workstation.
You can specify up to 7 parameters:
The parameter is optional. The parameter value can be:
The default is N.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the 4770 printer device driver sends data to the port when it receives data to be printed.
The parameter applies only when using port 1. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the 4770 printer device driver sends data to the port when it receives data to be printed.
The parameter applies only when using port 2. It is optional. The parameter value can be:
The default is 9600.
The parameter is optional. The parameter value can be:
The default is N.
This parameter specifies the number of bits per second the 4770 printer device driver sends data to the port when it receives data to be printed.
The parameter applies only when using port 3. It is optional. The parameter value can be:
The default is 9600.
You can specify up to 4 parameters:
The parameter is required. The parameter value is a string of up to 2 alphanumeric characters.
This value is used by a server or application to identify the printer session.
The parameter is required. The parameter value is a string of two alphanumeric characters. For each workstation, it has to be unique for this service and must match the ## value of the 4770 printer server in the CLIENT keyword.
The parameter is required. The parameter value can be:
The value must match the port usage in the PAR&4770 keyword for the server workstation.
This parameter specifies the maximum number of KB to be printed at a time.
The parameter is optional. The parameter value ranges from 1 to 4. The default is 1.
The value to be used for each printer is the maximum value specified for all the sessions defined for that printer.
LWSCONF NAME=AA, TYPE=OS/2, /* 4770 printer server definition. Example. */ SERVER=(PR4770##), PAR&4770=(N,C,9600) LWSCONF NAME=BB, TYPE=OS/2, /* 4770 printer client definition. Example. */ CLIENT=(PR477001,AA), SES&4770=(AA,01,1)
Before editing model configuration data, identify your requirements:
If the workstations are similar, you can define WSMODEL vectors for those workstations. Likewise, if the workstations use similar servers, you can define SVRMODEL vectors for those servers.
The customization process provides two alternative procedures to prepare and process model specification files.
To edit model configuration data using EDITSPC:
or
The EDITSPC procedure is provided to edit .SPC files.
Write the model configuration vectors on that file:
The LWSCONF vector can contain a reference to a WSMODEL vector, some references to SVRMODEL vectors, and actual definitions.
The WSMODEL vector can contain some references to SVRMODEL vectors, and actual definitions.
The following sections explain the vectors, their keywords, and the parameters corresponding to the keywords.
When you generate the MODELS.SPC file through the generation procedure, using the customization data stored in the internal repository, the order in which the vectors appear in the file may be different from the order in which you wrote them.
Information about each particular vector, including an example, follows.
Contains workgroup information, and must be placed in the MODELS.SPC file.
Vector position | None. It can be followed by up to 250 LWSCONF vectors. |
List of keywords |
MODNAME DEFAULTS, LANADAPT, LANGUAGE, SUFFIX, XPORT, TCPPORT, ADAPTNUM, NETBUFF,
WSNAMES, NWSIDDUP, PARLIP
|
Vector relates to | LWSCONF (NAME keyword), LANCONF (MODEL keyword), DEFAULTS |
Vector format |
LANMODEL MODNAME=xxxxxxxx, [DEFAULTS=xxxxxxxx,] [LANADAPT=x,] [LANGUAGE=xxx,] [SUFFIX=x,] [XPORT=x,] [TCPPORT=xxxxx,] [ADAPTNUM=xxx,] [NETBUFF=xx,] [NWSIDDUP=x,] [PARLIP=x,] WSNAMES=( ) |
The keywords in the first line in the list identify the workgroup model configuration.
Other keywords define the workgroup model configuration. For information on these keywords, refer to LANCONF vector.
The parameter value is a model name of up to 8 alphanumeric characters. The value is assigned in the MODEL keyword in the LANCONF vector to refer to the workgroup model configuration.
Each parameter is the name of a workstation in the workgroup model configuration. The parameter value is a string of up to 2 alphanumeric characters. The value is assigned in the NAME keyword in the LWSCONF vector that contains information about the workstation.
Each workstation specified in the WSNAMES keyword requires one LWSCONF vector to define that particular workstation in the workgroup model configuration. For information on this vector, refer to LWSCONF vector.
LANMODEL MODNAME=MODEL01, WSNAMES=(AA,BB,CC), LANGUAGE=001 LWSCONF NAME=AA, TYPE=OS/2, PRODLVL=L60, SERVER=(EHCSQL01), PAR&SQL=(CONFIGUR,5,4,10,Y,15) LWSCONF NAME=BB, TYPE=OS/2, PRODLVL=L60, CLIENT=(EHCSQL01,AA) LWSCONF NAME=CC, TYPE=OS/2, PRODLVL=L60, CLIENT=(EHCSQL01,AA)
Contains information about a workstation model configuration.
Vector position | None |
List of keywords |
MODNAME TYPE, SYSLVL, PRODLVL, SOFTPACK, FRAME, RPLOAD, POOLSIZE, XPORT, PARLIP, PARLIPEX, LANDPDCE, ADAPTNUM, NETBUFF, DBCSXLAT, PARWIN, SBC, SERVER, CLIENT PARxxxxx, SESxxxxx
|
Vector relates to | SVRMODEL vector |
Vector format |
WSMODEL MODNAME=xxxxxxx, [TYPE=( ),] [SYSLVL=x,] [PRODLVL=xxx,] [SOFTPACK=xxxxxxxx,] [FRAME=xxxx,] [RPLOAD=x,] [POOLSIZE=xxx,] [XPORT=x,] [PARLIP=( ),] [PARLIPEX=( ),] [LANDPDCE=x,] [ADAPTNUM=x,] [NETBUFF=xx,] [DBCSXLAT=x,] [PARWIN=xx,] [SBC=( ),] [SERVER=( ),] [CLIENT=( ),] [PARxxxxx=( ),] [SESxxxxx=( )] |
The MODNAME keyword identifies the workstation model configuration.
The keywords in the second line in the list define the workstation model configuration. The keywords in the third line define the servers related to that workstation. For information on all these keywords, refer to LWSCONF vector.
The parameter value can be any model name, of up to 8 alphanumeric characters.
WSMODEL MODNAME=MODEL02, TYPE=OS/2, PRODLVL=L60, SERVER=(PR47X2##,MODEL03), CLIENT=(EHCSQL01,AA), CLIENT=(SNA02,AA), SES&SNA=(AA,02,019,001)
Contains information about a server model configuration.
Vector position | None |
List of keywords |
MODNAME SVRNAME, EXPMEM, SERVPARM PARxxxxx, SESxxxxx
|
Vector relates to | None |
Vector format |
SVRMODEL MODNAME=xxxxxxx, SVRNAME=xxxxxxxx, [EXPMEM=x,] [SERVPARM=( ),] [PARxxxxx=( ),] [SESxxxxx=( )] |
The MODNAME keyword identifies the server model configuration. The SVRNAME and the EXPMEM keywords identifies the server.
The other keywords define the server model configuration. For information on those keywords, refer to LWSCONF vector.
The parameter value can be any model name, of up to 8 alphanumeric characters.
Refer to the table in Vectors - a quick reference for the names corresponding to the functional areas (string in parenthesis).
The following servers require that the server suffix (##) is substituted by the corresponding value to completely identify the server:
The following servers require a suffix to identify the session to be used:
Note that BIWP and LDA 7 program need the suffix only when they are installed in a DOS workstation.
If the following servers are to be run in either an OS/2 or a Windows VDM, the server names to be specified are:
where x is the suffix to identify the session.
The parameter value can be:
The default is N.
The parameter value is a string of up to 40 characters, enclosed between quotes.
SVRMODEL MODNAME=MODEL03, SVRNAME=PR47X2##, PAR&47X2=(N,C,9600,4722,,C,9600,4722)
Note for DOS users |
---|
For DOS users, the statements in this appendix about TCP/IP apply equally to PC/TCP. |
LANDP uses the standard TCP/IP user datagram protocol (UDP). LANDP adds extensions to this protocol to ensure reliable communication. The resulting protocol (and the LANDP server that implements it) is referred to as the LANDP Internet Protocol (LIP).
The following sections describe the LIP, and provide configuration information.
LIP refers to each workstation in the workgroup by its LIP name. The LIP name of a workstation consists of the prefix 'LIP-' followed by the workstation id and optionally followed by the workgroup name if SUFFIX=Y is specified in the LANCONF configuration vector.
For example: the LIP name of workstation 'S1' in workgroup 'BRANCH3' would be 'LIP-S1BRANCH3' if SUFFIX=Y were specified and 'LIP-S1' otherwise.
The LIP names are used as TCP/IP host names or host alias names for the workstations.
Within a LANDP workgroup the workstations that need to communicate with any particular workstation are called its related workstations. These are the workstations to which it provides services, or from which it receives services.
LIP uses TCP/IP to resolve the LIP name of every related workstation into an IP address. This requires the LIP names and corresponding IP addresses to be defined to a TCP/IP names server or in a local HOSTS file, but see Unresolved workstation IDs.
A sample of a HOSTS file follows:
214.1.1.51 basement LIP-AAWHAREHS 214.1.1.55 bossdesk LIP-BBWHAREHS 214.1.1.67 firstfloor LIP-CCWHAREHS
This sample corresponds to a LANDP workgroup with the following characteristics:
Before attempting to use LANDP for the first time, you should verify TCP/IP communications and definitions with the PING TCP/IP program. On each workstation, after TCP/IP has been started, issue the PING command with each related workstation ID.
For example, on a workstation AA belonging to a LANDP workgroup with the name WHAREHS, and related to LANDP workstations with the IDs BB and CC, you must issue:
PING LIP-AAWHAREHS PING LIP-BBWHAREHS PING LIP-CCWHAREHS
PING should report successful contact with every workstation. If it does not, either the network or the TCP/IP definitions are not ready.
For detailed information on the PING program, refer to the TCP/IP manuals. See Appendix J, Bibliography.
You can also perform this verification at production time when two workstations are unable to contact each other.
Unresolved workstation IDs can occur when not all workstations in the workgroup are in existence, or when DHCP (Dynamic Host Configuration Protocol) is being used to dynamically assign IP addresses.
In normal operation if any LIP name cannot be resolved then LANDP loading terminates. However when LIP address checking is turned off (with the PARLIP keyword or the /J parameter of EHCLIP) then unresolved LIP names are logged but LANDP loading continues.
Turning off LIP address checking is useful when not all workstations in the workgroup are in existence, or when DHCP (Dynamic Host Configuration Protocol) is being used to dynamically assign IP addresses. When LIP names cannot be resolved there will not, initially, be any attempt at communication with the workstations with unresolved LIP names. However, if any of these workstations make contact then communications will resume.
In an environment where DHCP is being used there are some alternative configurations to choose from:
The LIP uses one UDP port for communication in each workstation. The port number must be the same for all the workstations in a LANDP workgroup. If the default port number conflicts with other application requirements it can be changed during customization or at loading time.
The LIP establishes and maintains a session with each related LANDP workstation in the workgroup as defined at customization.
When the session is established, workstations identify themselves to each other to verify the LANDP configuration. If a mismatch is detected in the workstation identification or the corresponding INET addresses, the session is not established and an error message is logged.
Data is exchanged by sending and receiving datagrams. Datagrams are acknowledged by the destination workstation. Datagrams that are not acknowledged are retransmitted until they are acknowledged or until the LIP detects that contact is lost. If this happens, the session is reset, an attention message is logged, and the procedure to re-establish contact is started.
Both ends of a session can send data simultaneously at any time.
Depending on the message size, messages exchanged during a session are sent in one or more datagrams. The LIP stores information about each datagram in a retransmission table that is used if the datagram has to be retransmitted.
In LANDP for DOS, the size of this table is defined at customization or with a LIP loading parameter. If there is no space left in the retransmission table, the datagram cannot be sent and the process has to be retried later.
The default datagram length used by the LIP is 1472 bytes on DOS and 4272 bytes on other operating systems. The maximum datagram lengths are 32711 and 32767 respectively. To support messages longer than the datagram length, a segmentation mechanism divides them into segments and sends each segment as a datagram. The segments are reassembled at the receiving end. This process consumes time and resources. Therefore, the overall performance can be affected.
The LIP can detect whether a session partner is available during the periods of time when there is no traffic over the network. The LIP sends short availability probe datagrams at regular intervals to the related workstations. If these datagrams are not acknowledged, the LIP starts the session reset and re-establishment procedures.
You can disable this feature with a LIP parameter. However, this is not recommended in environments where clients can lock server resources. If a client locks a resource and then becomes unavailable, the resources would remain locked since the server would not be able to detect the lost session.
LANDP provides trace tools to diagnose errors and track problems. These tools use trace servers to log information about internal and external errors, and provide statistics.
For more information about these tools, see LANDP Problem Determination.
This appendix contains information for a possible host setup that you will need when working with LANDP. You must modify these examples for your own host system.
Three examples are provided that correspond to LANDP SNA/SDLC, SNA/X.25, and SNA/TRDLC configurations.
The access method configuration must match the LANDP SNA/SDLC configuration set up during customization. Following is an example for ACF/VTAM(R).
WPCGR20 GROUP LNCTL=SDLC,
DIAL=NO,
TYPE=NCP,
ANS=CONTINUE,
DATRATE=LOW,
DISCNT=NO,
DUPLEX=FULL,
IRETRY=NO,
ISTATUS=INACTIVE,
MAXDATA=265,
MAXOUT=2,
NEWSYNC=NO,
NRZI=NO,
PASSLIM=254,
PUTYPE=2,
PUDR=NO,
REPLYTO=2.0,
RETRIES=(3,15,40),
SERVLIM=10,
SPDSEL=NO,
TEXTTO=1.0
WL1PC LINE ADDRESS=001,
SPEED=9600,
CLOCKNG=EXT
WSRV1 SERVICE ORDER=(WP1AA,WP1AC)
WP1AA PU ADDR=AA
FU1AA01 LU LOCADDR=01,
MODETAB=TABPCLU,
SSCPFM=FSS,
DLOGMOD=ENTRYF,
PACING=0,
VPACING=0
FU1AA41 LU LOCADDR=41,
MODETAB=TABPCLU,
SSCPFM=FSS,
LOGAPPL=CICS2,
DLOGMOD=ENTRYP,
PACING=1,
VPACING=0
FU1AA37 LU LOCADDR=37,
MODETAB=TABPCLU,
SSCPFM=FSS,
DLOGMOD=ENTRYF,
PACING=0,
VPACING=0
FU1AA81 LU LOCADDR=81,
MODETAB=TABPCLU,
SSCPFM=USSSCS,
USSTAB=ROBTAB,
DLOGMOD=ENTRYZ,
PACING=0,
VPACING=0
WP1AC PU ADDR=AC,
MAXOUT=7,
PACING=7,
PASSLIM=7,
VPACING=7
FU1AC01 LU LOCADDR=01,
MODETAB=MODCRYP,
DLOGMOD=TABDSX11,
SSCPFM=USSSCS
The access method configuration must match the LANDP SNA/X.25 configuration setup during customization. Following is an example for ACF/VTAM.
SWPCX25 VBUILD TYPE=SWNET,
MAXGRP=10,
MAXNO=50
SPF01 PU ADDR=AA,
IDBLK=017,
IDNUM=80001,
ISTATUS=ACTIVE,
DISCNT=(YES,F),
MAXDATA=265,
MAXPATH=8,
PUTYPE=2,
SSCPFM=USSSCS,
VPACING=2
PATH DIALNO=C3231020108,PID=1,
GRPNM=XF1SNET
SUF0101 LU LOCADDR=01,
MODETAB=TABPCLU,
SSCPFM=FSS,
DLOGMOD=ENTRYF,
PACING=0,
VPACING=0
SUF0141 LU LOCADDR=41,
MODETAB=TABPCLU,
SSCPFM=FSS,
LOGAPPL=CICS2,
DLOGMOD=ENTRYP,
PACING=1,
VPACING=0
SUF0137 LU LOCADDR=37,
MODETAB=TABPCLU,
SSCPFM=FSS,
DLOGMOD=ENTRYK,
ENCR=REQD,
PACING=0,
VPACING=0
SUF0181 LU LOCADDR=81,
MODETAB=TABPCLU,
SSCPFM=USSSCS,
USSTAB=ROBTAB,
DLOGMOD=ENTRYZ,
PACING=0,
VPACING=0
The access method configuration must match the LANDP SNA/TRDLC configuration set up during customization. Following is an example for ACF/VTAM.
SWPCTOKE VBUILD TYPE=SWNET,
MAXGRP=2,
MAXNO=25
SPT11 PU ADDR=1,
IDBLK=05D,
IDNUM=11111,
PUTYPE=2,
MODETAB=TABPCLU,
MAXPATH=2
SDT1120 PATH DIALNO=0104400011111111,
GRPNM=GTL120
SDT1145 PATH DIALNO=0104400011111111,
GRPNM=GTL145
SUT111 LU LOCADDR=1,
USSTAB=ROBTAB,
DLOGMOD=ENTRYF
SUT1137 LU LOCADDR=37,
USSTAB=ROBTAB,
DLOGMOD=ENTRYF
SUT1235 LU LOCADDR=35,
USSTAB=ROBTAB,
MODETAB=MODCRYP,
DLOGMOD=TABDSX11
SUT1500 LU LOCADDR=0,
DLOGMOD=FBSSMODE,
SPAN=(450),
RESSCB=2
SUT1590 LU LOCADDR=90,
DLOGMOD=FBSSMODE,
SPAN=(450)
SUT1141 LU LOCADDR=41,
USSTAB=ROBTAB,
DLOGMOD=ENTRYP
SUT1181 LU LOCADDR=81,
USSTAB=ROBTAB,
DLOGMOD=ENTRYZ
When using the TCP/IP wide area communications server the dependent LU names must have a common alphanumeric prefix and a numeric suffix with a constant difference between the suffix and the LOCADDR. For example:
IYCKT300 LU LOCADDR=2 IYCKT301 LU LOCADDR=3 IYCKT327 LU LOCADDR=29 IYCKT481 LU LOCADDR=183
Following is an example of VTAM MODETAB for the previous definitions.
MODFBSS MODETAB
ENTRYF MODEENT LOGMODE=ENTRYF,
FMPROF=X'04',
TSPROF=X'04',
PRIPROT=X'B1',
SECPROT=X'B1',
COMPROT=X'7080',
RUSIZES=X'8787'
ENTRYP MODEENT LOGMODE=ENTRYP,
TSPROF=X'03',
FMPROF=X'03',
PRIPROT=X'B1',
SECPROT=X'B0',
COMPROT=X'3080',
PSERVIC=X'010000F90000000000000000',
RUSIZES=X'8585',
PSNDPAC=X'01',
SRCVPAC=X'01'
LDPDBCS MODEENT LOGMODE=LDPDBCS,
TSPROF=X'03',
FMPROF=X'03',
PRIPROT=X'B1',
SECPROT=X'B0',
COMPROT=X'3080',
PSERVIC=X'028000000000000000000300',
RUSIZES=X'8585'
ENTRYZ MODEENT LOGMODE=ENTRYZ,
TSPROF=X'03',
FMPROF=X'03',
PRIPROT=X'B1',
SECPROT=X'90',
COMPROT=X'3080',
PSERVIC=X'028000000000185000007E00',
RUSIZES=X'87C7'
The LANDP V5 emulator rejects the bind image if any of the following is true:
It is recommended that you set on the queryable flag in the VTAM MODEENT LOGMODE statement. This provides greater flexibility and allows the use of the extended color and highlighting support.
ENTDSX11 MODEENT LOGMODE=ENTDSX11,
FMPROF=X'03',
TSPROF=X'04',
PRIPROT=X'B0',
SECPROT=X'A0',
COMPROT=X'4000',
RUSIZES=X'8585'
This is an example for dependent LU:
SNASVCMG MODEENT LOGMODE=SNASVCMG,
TYPE=0,
FMPROF=X'13',
TSPROF=X'07',
PRIPROT=X'B0',
SECPROT=X'B0',
COMPROT=X'D0B1',
SSNDPAC=X'00',
SRCVPAC=X'00',
RUSIZES=X'8585',
PSNDPAC=X'00',
PSERVIC=X'060200000000000000000300'
This is an example for peer-to-peer LU:
FBSSMODE MODEENT LOGMODE=FBSSMODE,
TYPE=0,
FMPROF=X'13',
TSPROF=X'07',
PRIPROT=X'B0',
SECPROT=X'B0',
COMPROT=X'D0B1',
SSNDPAC=X'00',
SRCVPAC=X'00',
RUSIZES=X'F7F7',
PSNDPAC=X'00',
PSERVIC=X'060200000000000000002C00'
ENTRYF MODEENT LOGMODE=ENTRTF,
FMPROF=X'04',
TSPROF=X'04',
PRIPROT=X'B1',
SECPROT=X'B0',
COMPROT=X'7080',
RUSIZES='8787'
TYPETERM = ALU0M2
TERM = L711
TYPETERM(LDPSCSP) GROUP(LANDP) DESCRIPTION()
CICS/ESA(R) RDO OFF-LINE UTILITY PROGRAM
RESOURCE-TYPE
DEVICE(SCSPRINT) TERMMODEL() SESSIONTYPE()
LDCLIST() SHIPPABLE(NO)
MAPPING-PROPERTIES
PAGESIZE(24,80) ALTPAGE(0,0) ALTSUFFIX()
FMHPARM(NO) OBOPERID(NO)
PAGING-PROPERTIES
AUTOPAGE(YES)
DEVICE-PROPERTIES
DEFSCREEN(0,0) ALTSCREEN( , ) APLKYBD(NO)
APLTEXT(NO) AUDIBLEALARM(NO) COLOR(NO)
COPY(NO) DUALCASEKYBD(NO) EXTENDEDDS(NO)
HILIGHT(NO) KATAKANA(NO) LIGHTPEN(NO)
MSRCONTROL(NO) OBFORMAT(NO) PARTITIONS(NO)
PRINTADAPTER(NO) PROGSYMBOLS(NO) VALIDATION(NO)
FORMFEED(NO) HORIZFORM(NO) VERTICALFORM(NO)
TEXTKYBD(NO) TEXTPRINT(NO) QUERY(NO)
OUTLINE(NO) SOSI(NO) BACKTRANS(NO)
CGCSGID(0,0)
SESSION-PROPERTIES
ASCII(NO) SENDSIZE(256) RECEIVESIZE(256)
BRACKET(YES) LOGMODE()
DIAGNOSTIC-DISPLAY
ERRLASTLINE(NO) ERRINTENSIFY(NO) ERRCOLOR(NO)
ERRHILIGHT(NO)
OPERATIONAL-PROPERTIES
AUTOCONNECT(NO) ATI(YES) TTI(YES)
CREATESESS(NO) RELREQ(YES) DISCREQ(YES)
NEPCLASS(0) SIGNOFF(YES) XRFSIGNOFF(NOFORCE)
MESSAGE-RECEIVING-PROPERTIES
ROUTEDMSGS(ALL) LOGONMSG(NO)
APPLICATION-FEATURES
BUILDCHAIN(NO) USERAREALEN(40) IOAREALEN(512,0)
UCTRAN(NO)
RECOVERY
RECOVOPTION(SYSDEFAULT)
RECOVNOTIFY(NONE)
TYPETERM(A360001F) GROUP(TCTHURS) DESCRIPTION()
CICS/ESA RDO OFF-LINE UTILITY PROGRAM
RESOURCE-TYPE
DEVICE(3600) TERMMODEL() SESSIONTYPE()
LDCLIST() SHIPPABLE(NO)
MAPPING-PROPERTIES
PAGESIZE(1,40) ALTPAGE(0,0) ALTSUFFIX()
FMHPARM(NO) OBOPERID(NO)
PAGING-PROPERTIES
AUTOPAGE(YES)
DEVICE-PROPERTIES
DEFSCREEN(0,0) ALTSCREEN( , ) APLKYBD(NO)
APLTEXT(NO) AUDIBLEALARM(NO) COLOR(NO)
COPY(NO) DUALCASEKYBD(NO) EXTENDEDDS(NO)
HILIGHT(NO) KATAKANA(NO) LIGHTPEN(NO)
MSRCONTROL(NO) OBFORMAT(NO) PARTITIONS(NO)
PRINTADAPTER(NO) PROGSYMBOLS(NO) VALIDATION(NO)
FORMFEED(YES) HORIZFORM(NO) VERTICALFORM(NO)
TEXTKYBD(NO) TEXTPRINT(NO) QUERY(NO)
OUTLINE(NO) SOSI(NO) BACKTRANS(NO)
CGCSGID(0,0)
SESSION-PROPERTIES
ASCII(NO) SENDSIZE(30270) RECEIVESIZE(30720)
BRACKET(YES) LOGMODE(0)
DIAGNOSTIC-DISPLAY
ERRLASTLINE(NO) ERRINTENSIFY(NO) ERRCOLOR(NO)
ERRHILIGHT(NO)
OPERATIONAL-PROPERTIES
AUTOCONNECT(NO) ATI(YES) TTI(YES)
CREATESESS(YES) RELREQ(YES) DISCREQ(YES)
NEPCLASS(0) SIGNOFF(YES) XRFSIGNOFF(NOFORCE)
MESSAGE-RECEIVING-PROPERTIES
ROUTEDMSGS(ALL) LOGONMSG(NO)
APPLICATION-FEATURES
BUILDCHAIN(YES) USERAREALEN(40) IOAREALEN(1024,32767)
UCTRAN(NO)
RECOVERY
RECOVOPTION(SYSDEFAULT)
RECOVNOTIFY(NONE)
The CICS-supplied TYPETERM definition DFHLU2C2 in group DFHTYPE corresponds to the VTAM logmode ENTRYZ shown.
For an LU_2 with extended data streams, TYPETERM DFHLU2 in group DFHTYPE is suitable.
TYPE UNITYPE=SLUTYPEP
TERMINAL NAME=DCDSZU00,
OUTBUF=1024,
OPTIONS=(TRANRESP, PAGDEL, ACK, NOBID)
TYPE UNITYPE=SLUTYPE1
TERMINAL NAME=DCDPZU02
COMPT1=(PRINTER1,MFS=SCS1),
OPTIONS=(OPNDST, SHARE, RELRQ),
OUTBUF=256
TYPE UNITYPE=SLUTYPE2
TERMINAL NAME=LUFBS2,
TYPE=3270-A02,
SIZE=(24,80),
Communication between an AS/400 system and a LANDP workstation can use SNA LU_2 protocols. The following parameters must be defined in the AS/400 computer:
The Station Address must be the same as the PU address defined in LANDP customization for SNA Communication server.
The Station Address must be the same as the PU address defined in LANDP customization for SNA Communication server.
The Local Address must be the same as the LU defined for the emulator session during LANDP customization.
The following parameters must be defined in the AS/400 system for communications between AS/400 system and LANDP workstations using SNA LU_0 protocol:
The Station Address must be the same as the one defined in FBSS Customization for SNA Communication.
The Local Address must be the same as the LU defined in LANDP customization for the LU_0 Session.
There is no need to configure the LANDP controller as a 3174 because AS/400 also supports attachment of 3270 devices to 4700 controllers.
WorkSpace On-Demand (WSoD) and Windows Terminal Server (WTS) are known generically as Server Based Computing (SBC) products. This appendix describes how workstations within a LANDP workgroup can run within an SBC environment.
|
WorkSpace On-Demand (WSoD), a component of OS/2 Warp Server for e-Business,
provides server-managed client support. The following describes how
LANDP can be integrated into the WSoD client environment.
WorkSpace On-Demand Road Map gives a detailed walkthrough of how
to install an application onto a WSoD server. Figure 25 (based on page 59 of WorkSpace On-Demand Handbook
(Release 2)) shows how an application like LANDP is integrated into the
WSoD directory structure for remote IPL.
|
Figure 25. Integrating LANDP into WorkSpace On-Demand directory structure
The application (LANDP) directory structure is as follows:
To aid the implementation of LANDP in a workgroup comprising Server Based Computing systems, LANDP Customization generates the lists of files for the above SBC directories. Using GETTING, the sets of files can be suitably distributed. For more information, look at the descriptions of the SBC keyword of LWSCONF at ***, and of GETTING /S at ***.
Following customization, the LANDP files distributed by GETTING are machine-specific. They are for a specific workstation, although they include many files that might be shared across other workstations. There are no user-specific files. The following is an analysis of how the LANDP files might be distributed into the WSoD directory structure.
The following LANDP files can be shared across multiple machines, and are read-only (that is, suitable for inclusion in directory A):
All other files should be placed into a machine-unique directory. The following files might be machine-unique (read/write or read/only). Included are files that are targeted to a specific machine and that may be modified by selected servers. The following are suitable for inclusion in directory C:
There are many other miscellaneous files that can be distributed to each workstation dependent upon the servers selected, and that convey machine-configured information specific to a workstation.
These should similarly be placed into a machine-unique directory.
The CONFIG.ADD file includes modifications to CONFIG.SYS that are required for a given WSoD client (for example to include support for additional device drivers). This is identical to the process for a non-WSoD workstation. CONFIG.SYS is usually in RPL\MACHINES\client_name\CONFIG.SYS. Typical statements that could be added include:
LIBPATH=Z:\LANDP DPATH=Z:\LANDP DEVICE=Z:\LANDP\EHCVDMVD.SYS DEVICE=Z:\LANDP\4772PDD.SYS /D1 /C11 /B19600 SET EHC_WSID=id (where id is the workstation identifier)
This implementation is a machine-specific application. It does not follow the user around and always stays with that machine.
The following entries need to be added to the machine's file index table (FIT file). The FIT file entries are dependent upon which LANDP servers are assigned to the WSoD client. The following is an example of the relevant LANDP section of a FIT file used for a WSoD client on which Shared-File server and System Manager will run.
One possible suggestion is to add these entries to the machine classes that LANDP will be running on. This can be done either by modifying the machine FIT file \IBMLAN\RPL\FITS\DFBB20xx.FIT (where xx is the country code) before creating those machines, or by modifying the individual machine FIT files.
LANDP Support Z:\LANDP LANDP Z:\LANDP\*.CFG \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\*.LOG \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\*.BAT \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\*.DAT \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\*.DBD \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\*.PCB \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\*.SEQ \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\EHCLOG*.DAT \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\EHCTRC*.BAT \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\FBSS#* \\rplservername\WRKFILES\client_name\LANDP Z:\LANDP\AUTOFBSS.CMD \\rplservername\WRKFILES\client_name\LANDP\AUTOFBSS.CMD
If you wish to have more than one LANDP workgroup in a single WSOD server machine, one option is to define an additional instance of LANDP. For example, if two workgroups have different LANCONF LANGUAGE values, two sets of FIT file entries (as above) could be defined:
;LANDP Support (English) Z:\LANDPENG LANDPENG Z:\LANDPENG\*.CFG \\rplservername\WRKFILES\client_name\LANDPENG ...
;LANDPESP Support (Spanish) Z:\LANDPESP LANDPESP Z:\LANDPESP\*.CFG \\rplservername\WRKFILES\client_name\LANDPESP ...
The assigned drive location on the WSoD server on which the client system and application files reside defaults to Z:. This is the client user's boot drive. The rest of LANDP would have to be on the same drive and configured that way. For example, the target drive for location of the files used by RCMS server (PAR&RCMS parameters 5 and 6) and System Manager server (PAR&SMGR parameters 5, 6, 7, 8) for the production workstation would need to conform to this default, Z:. (These files are subsequently copied to their target directories by EHCVAL).
For example:
/* RCMS */ SERVER=RCMS, PAR&RCMS=(AB,,,,Z:\LANDP\,Z:\LANDP\,,,), /* System Manager */ SERVER=(SMGR,,N), PAR&SMGR=(AB,,Z:\LANDP\,SMGRPRF1,Z:\LANDP\, Z:\LANDP\,Z:\LANDP\,Z:\LANDP\,Z,USER1)
Generally, LANDP facilities run on a WSoD client as they do on an OS/2 workstation. Servers that have been tested include Shared_File server, Financial Printer server with the financial printer attached to the WSoD client, System Manager and System Manager Operator, and 3270 emulator running in a VDM.
Careful attention needs to be given to planning the use of Shared File (SF) server, specifically when using XLR or Replicator support. The underlying purpose of XLR or Replicator support is to provide immediate database recovery from a backup server in case of machine or system failure on the workstation on which SF server resides. Clearly it is inappropriate to have both the SF server and its backup residing on the same WSoD server.
To support the LANDP Java Manager in a WSoD environment, the environment variable EHC_WSID must be defined with the workstation ID and should be included in the machine-unique CONFIG.SYS file.
By default, WSoD does not allow anything to be written to a disk on a WSoD client workstation (it may be a media-less workstation). Any I/O requests are read/written to the disk on the WSoD server, for example, shared-file access or any attempt to write trace or logging information.
In the WTS environment, the installation and customization of LANDP can be done in the same way as usual for LANDP for Windows. There is no need to use the program wizard that is supplied with WTS to install and remove applications.
However, when distributing a workgroup, care must be taken to ensure that the LANDP files are segregated correctly.
One benefit of WTS is that only one version of an application program needs to be present on the server machine. These applications must be kept in a read-only directory. However, because LANDP files are distributed on a machine-specific basis, some changes to the normal distribution process are required.
Normally, after LANDP customization, the GETTING utility is used to distribute the files for a given workstation to the same directory destination. In a WTS environment, shared read-only files should be placed in a workstation-specific directory.
The following describes how the LANDP files might be distributed in a WTS environment.
The following LANDP files can be shared across multiple machines, and are suitable for inclusion in the read-only directory:
All other files should be placed into a machine-unique read-write directory. The following files might be machine-unique (read/write or read/only). The list includes files that are targeted to a specific machine and that can be modified by selected servers.
There are many other miscellaneous files that can be distributed to each workstation, and that contain information specific to that workstation.
These should also be placed into a machine-unique read-write directory.
LANDP customization creates configurations for the LANDP servers. In some cases, these configurations contain file names and file paths. These file attributes must be chosen carefully when LANDP is to run in a WTS environment. In a normal Windows environment, a LANDP workstation does not share its disk with another LANDP workstation, because each workstation is on a separate machine. However, under WTS, all LANDP workstations are on the same machine. Therefore, it is vital that these separate workstations are not allowed to interfere with each other.
For example, the SHFLDBD vector contains two keywords: DBDPATH and DBFLNAME. These keywords describe the name and path of the shared file. If two Shared File Servers exist within the same workgroup and therefore are going to run on the same server machine, these keywords must not conflict. Each shared file server profile must have have its own unique file name and path.
Devices that are attached to the client machine can be used by applications that run within that client's session. WTS provides the ability to access client-attached devices by mapping them through the LPT or COM ports. WTS only maps devices that have been installed using the printer wizard install utility provided by the operating system. It does not allow the mapping of client drives, although network drives can be mapped.
The common LANDP devices are magnetic stripe readers (MSRs), PIN pads, and printers. You might not be able to install these using the Windows printer wizard.
There are third-party software solutions (for example, Citrix MetaFrame) that extend the functionality of client-attached device mapping.
Some LANDP servers require the port number to which the device is attached. In the WTS environment, LANDP uses the port number that is defined on the terminal server, not the client. For example, if an MSRE is attached to the client's COM 1 port and mapped to the terminal server's COM 4 port, the /C: parameter for MSRE47## needs to be 4, not 1.
LANDP can access the local machine's disk when mapped through either MetaFrame or the 'net use' command. MetaFrame defines the drive-mapping convention that will be used for each client session, and when using the local drives mapped in the client sessions, no authorization is needed. However, the 'net use' method requires authorization before accessing a network drive. If client drives are to be used, the corrected path names must be supplied in your LANDP Customization data.
When running LANDP in a WTS environment, it is important to make sure that
each server does not interfere with other servers. This can usually be
done through careful planning at the customization stage. However, in
some cases, action is required at run time.
|
Shared File Server The Shared File Server has two types of local files, the log file and the locks file, which are unique to that instance of the Shared File Server. By default, these files are placed in the root directory of the C drive. In the WTS environment, if two or more Shared File Servers exist within the same workgroup, these local files will conflict. LANDP provides a mechanism to enable users to select their own paths for these files. This mechanism should be used within the WTS environment, so that each Shared File Server has its own instances of the log and locks files. To use the mechanism, set the environment variables LOGPATH, LOGPATH2, and LOCKSPATH in the AUTOFBSS.BAT file for each Shared File Server within the workgroup. Java manager When running LANDP Java applications in a WTS environment, the variable EHC_WSID must be defined. EHC_WSID should be set to be the ID of the LANDP workstation, and must be available to the process that is running the LANDP Java application and to the LANDP Java Manager. If the LANDP Java manager is started using the AUTOFBSS.BAT file,
add the SET EHC_WSID statement to the AUTOFBSS.BAT file.
Otherwise, set the EHC_WSID variable from the command-line prompt before
starting the LANDP Java Manager. Because LANDP Java applications are
not started by AUTOFBSS, EHC_WSID should be set at the command line prompt
before the Java application is started.
|
Because Windows NT Services can only have one instance invoked, each LANDP workstation should be loaded in application mode. To do this, use the parameter /N when invoking the LOADER utility program. In addition, use the /W parameter to specify a unique directory path for this Shared File Server. If no /W parameter is specified, the current working directory is used.
For example:
LOADER /N: /W:C:\LANDP\SPV.EXE /01
You should also add the read-only directory name to the 'path' statement. This tells Windows NT where the LANDP read-only files are, and also enables the user to invoke LANDP.
The following describes a simple workgroup configuration for a WTS environment. Figure 26 shows a simple LANDP workgroup in a normal Windows NT environment.
Figure 26. A Simple LANDP Workgroup
Figure 27. A Simple LANDP Workgroup in a WTS Environment
Under the WTS environment the associated COMMON.SPC and LANCONF.SPC files are described below.
COMMON.SPC (extract):
SHFLDBD SHFLPRF=SEF01234, DBDNAME=F1DBD, COLLKEYS=N, RECLEN=62, DBDPATH=D:\client1\SFSDATA, DBDFLNAME=F1, KEY01=(F1P,P,N,5,0) SHFLPCB PCBNAME=PCBF1, KEYFIELD=F1P SHFLDBD SHFLPRF=PERDATA, DBDNAME=PERDATA, COLLKEYS=N, RECLEN=100, DBDPATH=D:\client2\SFSDATA, DBDFLNAME=F1, KEY01=(PERNO,P,N,5,0) SHFLPCB PCBNAME=PERSNO, KEYFIELD=PERNO
LANCONF.SPC (extract):
LWSCONF NAME=01, TYPE=NT, SERVER=(SHFILE01), PAR&SHFL=(SEF01234,3,8,Y,0,,,,0,), CLIENT=(SHFILE01,01), CLIENT=(MSRE4702,02) LWSCONF NAME=02, TYPE=NT, SERVER=(SHFILE02), PAR&SHFL=(PERDATA,3,8,Y,0,,,,0,), SERVER=(EHCODB2), PAR&ODB=(DBNAME,4,14,10,), SERVER=(MSRE4702), PAR&MSRE=(4777,1), CLIENT=(SHFILE01,01), CLIENT=(MSRE4702,02), CLIENT=(SHFILE02,02), CLIENT=(EHCODB02,01)
The LANCONF vector definitions are exactly the same as for a normal Windows environment.
The following shows how the files that have been created by customization should be distributed if no LANDP servers are to be run as Windows services:
E:\LANDP is the shared read-only directory that contains all the read-only files ( for example, EXE files, DLL files, HLP files, MSG files).
E:\CLIENT1\01\contains the files that are specific to workstation 01 ( for example, SEF01234.*, AUTOFBSS.BAT, *.cfg).
E:\CLIENT2\02\contains the files that are specific to workstation 02 ( for example, PERDATA.*, AUTOFBSS.BAT, *.cfg).
Use the following statement to update the PATH variable to include the shared read-only file directory:
SET PATH=E:\LANDP;%PATH%
Before running LANDP, you must also change the AUTOFBSS.BAT files to set the correct environment variables to avoid conflicts between the two shared-file servers.
Add the following statements to the AUTOFBSS.BAT file in the directory containing read-write file for workstation 01:
SET LOGPATH=E:\CLIENT1\01
SET LOCKSPATH=E:\CLIENT1
Add the following statements to the AUTOFBSS.BAT file in the directory containing read-write file for workstation 02:
SET LOGPATH=E:\CLIENT2\02
SET LOCKSPATH=E:\CLIENT2
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this information in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to:
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS " WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice.
Any references in this information to non-IBM documentation or non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those documents or Web sites. The materials for those documents or Web sites are not part of the materials for this IBM product and use of those documents or Web sites is at your own risk.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or any equivalent agreement between us.
The following terms are trademarks of the IBM Corporation in the United
States or other countries, or both:
Table 14. Trademarks and service marks
|
|
Lotus is a registered trademark of Lotus Development Corporation in the United States and other countries.
Tivoli and NetView are registered trademarks of Tivoli Systems Inc. in the United States and other countries. In Denmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc in the United States and other countries.
Microsoft, Windows, Windows NT, Windows 2000, and the Windows logo, are registered trademarks of Microsoft Corporation.
UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited.
Intel is a registered trademark of Intel.
PC/TCP and NetManage are registered trademarks of NetManage Inc.
Red Hat is a registered trademark of Red Hat, Inc.
SuSE and its logo are registered trademarks of SuSE AG.
Caldera Systems, the C-logo, and OpenLinux are either registered trademarks or trademarks of Caldera Systems, Inc.
TurboLinux is a registered trademark of TurboLinux, Inc.
Other company, product, and service names may be trademarks or service marks of others.
This glossary includes abbreviations, terms, and definitions used in the IBM LANDP Licensed Programs Family publications. It does not include all terms previously established for IBM networks, programs, operating systems, or other IBM products.
If you do not find the term you are looking for, refer to the IBM Dictionary of Computing.
This glossary includes terms and definitions from the following sources:
Definitions that are specific to IBM products are so labeled, for example, "In LANDP," or "In SNA."
CALL "RMTREQ" USING BY REFERENCE EHC-CPRB BY VALUE EHC-RESERVED retcode = GETREQ(&mycprb, EHC_RESERVED);
Notes:
The term thin client usually refers to a system that runs on a resource-constrained machine or that runs on a small operating system. This clients do not require local system administration, and they execute Java applications delivered over the network.
Notes:
This bibliography includes publications cited in this book and other publications on related topics. Where a shortened title is used in the text, the short title is listed after the full title.
This bibliography also includes books which might now be obsolete.
IBM LANDP Family: Introduction and Planning, GC34-6043. Short title: LANDP Introduction and Planning.
IBM LANDP Family: Installation and Customization, GC34-6044.Short title: LANDP Installation and Customization.
IBM LANDP Family:Programming Guide, SC34-6048.Short title: LANDP Programming Guide.
IBM LANDP Family: Programming Reference, SC34-6045. Short title: LANDP Programming Reference.
IBM LANDP Family: Servers and System Management, SC34-6046. Short title: LANDP Servers and System Management.
IBM LANDP Family: Problem Determination, GC34-6047. Short title: LANDP Problem Determination.
IBM FBSS Licensed Programs Family General Information. GC19-5172.
IBM FBSS Licensed Programs Family Installation and Customization. SC19-5173.
IBM FBSS Licensed Programs Family Program Description. SC19-5176.
IBM FBSS Licensed Programs Family Version 2 Programmer's Reference. GA19-5450.
IBM FBSS Licensed Programs Family Version 2 Application Programming. SC19-5174.
Financial Branch System Integrator and Financial Branch System Integrator/2 General Information. GC19-5187.
Financial Branch System Integrator Programmer's Reference Manual. GA19-5452.
Financial Branch System Integrator/2 Programmer's Reference Manual. SC19-5188.
IBM Transaction Security System: General Information Manual and Planning Guide. GA34-2137.
IBM Transaction Security System: Programming Guide and Reference. SC31-2934.
IBM 4721 Self-Service Document Printer Programmer's Reference. GA19-5342.
IBM 4731/38/39 Personal Banking Machines P-Models Software Customization and Programming Reference. GA19-5462.
IBM 4733 Teller Assist Unit Programmer's Reference. GA19-5425.
IBM 4737 Self-Service Transaction Station Programmer's Reference. GA19-5408.
IBM Financial Application Development Toolkit Version 2 Program Description and Operation. SB11-8461.
PC DOS 7 Technical Update. GG24-4459.
PC DOS 7 User Guide. S83G-9260.
PC DOS 7 Command Reference. S83G-9309.
PC DOS 7 Keyboard and Code Pages. S83G-9310.
IBM TCP/IP Version 2.1.1 for DOS: Installation and Administration. SC31-7047.
IBM TCP/IP Version 2.1.1 for DOS: User's Guide. SC31-7045.
IBM TCP/IP Version 2.1.1 for DOS: Programmer's Reference. SC31-7046.
OS/2 Warp Version 4 Up and Running!. S84H-3098.
OS/2 Warp Server for e-Business. SG24-5393.
OS/2 Warp, PM Programming Reference Vol I. G25H-7190.
OS/2 Warp PM Programming Reference Vol II. G25H-7191.
OS/2 2.0 Application Design Guide. S10G-6260.
OS/2 2.0 Virtual Device Driver Reference. S10G-6310.
DB2/2 Guide. S62G-3663.
OS/2 LAN Server Network Administration Reference Volume 1: Planning, Installation and Configuration. S10H-9680.
OS/2 LAN Server Network Administrator Reference Volume 2: Performance Tuning. S10H-9681.
OS/2 LAN Server Network Administrator Reference Volume 3: Network Administrator Tasks. S10H-9682.
IBM Systems Application Architecture Common Programming Interface Dialog Reference. SC26-4356.
IBM Systems Application Architecture Common Programming Interface Presentation Reference. SC26-4359.
IBM OS/2 Programming Tools and Information V1.3 Programming Guide. S91F-9259.
TCP/IP for OS/2 Warp Programming Reference, SC31-8407.
IBM Network SignON Coordinator/2 Getting Started. S96F-8629.
IBM Token-Ring Network: Introduction and Planning Guide. GA27-3677.
IBM Token-Ring Network: Problem Determination Guide. SX27-3710.
Local Area Network: Administrator's Guide. GA27-3748.
IBM PC Network: Technical Reference.
IBM Personal Computer LAN Support Program.
IBM Personal Computer Baseband and Broadband.
IBM Cabling System Planning and Installation Guide. GA27-3361.
Using the IBM Cabling System with Communication Products. GA27-3620.
IBM Token-Ring Network Architecture Reference. SC30-3374.
IBM Local Area Network Technical Reference. SC30-3587.
IBM Local Area Network Support Program User's Guide. SC21-8288.
IBM 3270 Personal Computer Control Program Programming Guide. SC23-0165.
IBM 3270 Information Display System Character Set Reference. GA27-2837.
IBM PC 3270 Emulation Program, Entry Level V2.0 Programmer's Guide. S91F-8583.
IBM 3270 PC High Level Language API Programming Reference. SC23-2473.
Personal Communications Version 4.3 Emulator Programming, SC31-8478.
SNA Primary Custom Feature Description. GC31-2509.
Advanced Function for Communications: System Summary. GA27-3099.
System Network Architecture (SNA) Technical Overview. GC30-3073.
System Network Architecture (SNA) Format and Protocol Reference Manual. SC30-3112.
System Network Architecture (SNA) Formats. GA27-3136.
System Network Architecture (SNA) Format and Protocol Reference Manual: Management Services. SC30-3346.
System Network Architecture (SNA) Sessions between Logical Units. GC20-1868.
CCITT X.25 Recommendations, Interface between Data Terminal Equipment (DTE) and Data Circuit Terminating Equipment (DCE) for Terminals Operating in the Packet Mode on Public Data Networks. Vol. VIII. Fascicle VIII.5. This document is useful when writing X.25 applications.
RT PC X.25 Communication Support User's Guide. SC33-0630.
X.25 Interface for Attaching SNA Nodes to Packet-Switched Data Network General Information Manual. GA27-3345.
RT PC X.25 Communications Support Programmer's Reference. SC33-0631.
IBM Cryptographic Subsystem Concepts and Facilities. GC22-9063.
IBM X.25 Co-Processor Support Program User's Guide. X07F-8915.
IBM X.25 Co-Processor Support Program Programmer's Reference. X07F-8916.
IBM X.25 Interface Co-Processor/2 Technical Reference. S16F-1879.
SNA Advanced Peer-to-Peer Networking Dependent LU Requester Architecture Reference. SV40-1010.
Multiprotocol Transport Networking (MPTN) Architecture: Formats. GC31-7074.
Multiprotocol Transport Networking (MPTN) Architecture: Technical Overview. GC31-7073.
Telnet Protocol Specification, STD 8, RFC 854, USC/Information Sciences Institute. J. Postel and J. Reynolds .
To view this book, use the keyword RFC 854 with an internet search engine.
Printed copies of RFCs are available for a fee from:
SRI International, Room EJ291
333 Ravenswood Avenue
Menlo Park, CA 94025
(415) 859-3695
(415) 859-6387
FAX (415) 859-6028
NetView Distribution Manager: General Information V1.6. GH19-6792.
NetView Distribution Manager: Planning. SH19-6589.
NetView Distribution Manager Release 6: Installation and Customization. SH19-6794.
NetView Distribution Manager: Operation. SH19-6592.
NetView Distribution Manager: User's Guide V1.6. SH19-6795.
NetView Distribution Manager: Diagnosis R5. LY19-6374.
NetView Distribution Manager: Messages and Codes V1.6. SH19-6798.
IBM 4009 Operator's manual. GA19-5650.
IBM 4009 Service manual/Parts catalogue. SY19-6392.
IBM 4009 Quick Reference Card. GX11-6316.
IBM 4009 Customer Setup. GA19-5651.
IBM 4009 Safety Instructions. GA19-5651.
IBM 4009 Product and Programming Description (PPD) DOS. SH19-4015.
IBM 4009 Product and Programming Description (PPD) OS/2. SH19-4038.
IBM 4700 Finance Communication System Summary. GC31-2016.
IBM 4700 Financial I/O Planning Guide. GC31-3762.
IBM 4700 Financial I/O Devices Programming Guide. GC31-3770.
IBM 4700 Financial I/O Devices Programming Guide for OS/2. GC31-2661.
IBM 4700 Finance Communication System, Controller Programming Library, Volume 5, Cryptographic Programming. GC31-2070.
IBM 4700 Financial I/O Devices Operating Guide. SC31-3763.
IBM 4712 Transaction Printer Models 1, 2, and 3 Reference Card. SC31-3765.
IBM 4722 Document Printer Model 3 Programming Addendum. GC31-2928.
IBM 4722 Document Printer Models 1, 2, and 3 Reference Card. SC31-3767.
IBM 4748 Document Printer Programming Guide. SA34-2090.
IBM 4748 Document Printer Operating Guide. SA34-2068.
IBM 4748 Document Printer Service Guide. SA34-2091.
IBM 4770 Ink Jet Transaction Printer Product Profile. G571-0276.
IBM 4772 Universal Financial Printer Model 1 Programming Guide. SA34-2199.
IBM 4772 Universal Financial Printer Model 1 and 2 Installation and Operating Guide. GA34-2192.
IBM 4772 Universal Financial Printer Model 1 and 2 Reference Card. GX31-2077.
IBM 4772 Universal Financial Printer Model 1 and 2 Service Guide. SA34-2193.
IBM 4777 Magnetic Stripe Unit Installation and Operating Guide. GA34-2189.
IBM 4777 Magnetic Stripe Unit: Programming Guide for OS/2. SA34-2194.
IBM 4777 Magnetic Stripe Unit: Programming Guide for DOS. SA34-2195.
IBM 4778 PIN-Pad Magnetic Stripe Reader Installation and Operating Guide. GA34-2190.
IBM 4778 PIN-Pad Magnetic Stripe Reader: Programming Guide for OS/2. SA34-2196.
IBM 4778 PIN-Pad Magnetic Stripe Reader: Programming Guide for DOS. SA34-2197.
IBM 4777 Magnetic Stripe Unit and 4778 PIN-Pad Magnetic Stripe Reader AIX Programming Guide. SA34-2358.
IBM 9055-001 Document Printer: Planning and Programming Guide. SA18-7496.
IBM 9055-002 Document Printer: Planning and Programming Guide. SA18-7489.
IBM 9068-A01/A03 Multi-Purpose Passbook Printer Operating Guide. GA18-7719.
IBM 9068-A01/A03 Multi-Purpose Passbook Printer Planning and Programming Guide. GA18-7721.
IBM 9068 Multi-Purpose Passbook Printer Model D01 Planning and Programming Guide. SA18-7505.
IBM 9068 Multi-Purpose Passbook Printer Model S01 Planning and Programming Guide. SA18-7506.
IBM 9068-S01 Multi-Purpose Passbook Printer Operating Guide. SA18-7507.
IBM 9069 Printer Planning and Programming Guide, SA18-7525.
IBM 9069 Operating Guide, SA18-7524.
IBM Cryptographic Subsystem Concepts and Facilities. GC22-9063.
IBM 4700 Finance Communication System, Controller Programming Library, Volume 5, Cryptographic Programming. GC31-2070.
IBM Transaction Security System Workstation Security Services: Installation and Operating Guide. SA34-2141.
IBM Transaction Security System Concepts and Programming Guide: Volume 1, Access Controls and DES Cryptography. GC31-3937.
Product web site:
http://www.ibm.com/software/ad/vacpp/
Product web site:
http://www.ibm.com/software/ad/visgen/
IBM Redbook:
VisualAge Generator Version 3.1 System Development Guide, SG24-4230-02
Product web site:
http://www.ibm.com/software/ad/smalltalk/
IBM Redbooks:
VisualAge for Smalltalk Handbook - Volume 1: Fundamentals, SG24-4828-00
VisualAge for Smalltalk Handbook - Volume 2: Features, SG24-2219-00
IBM Java web site:
http://www.ibm.com/software/java/
IBM VisualAge for Java product web site:
http://www.ibm.com/software/ad/vajava/
IBM developerworks web site:
http://www.ibm.com/software/developer/java/
IBM VisualAge Developers Domain web site:
http://www.ibm.com/software/vadd/
IBM Redbooks:
Programming with VisualAge for Java Version 2, SG24-5624
Application Development with VisualAge for Java Enterprise, SG24-5081
Personal Communications AS/400 and 3270 for OS/2 Up and Running, SC31-8258.
Personal Communications AS/400 and 3270 for Windows NT Up and Running, GC31-8314.
Personal Communications/3270 Programmer's Guide for DOS (Entry Level), S20H-1774.
Personal Communications/3270 Programmer's Guide for OS/2, S85G-8681.
Personal Communications/3270 Reference Guide for OS/2, S85G-8721.
Personal Communications Version 4.3 for Windows 98 and Windows NT Reference, Volumes 1 and 2 , SC31-8682, SC31-8680.
Personal Communications Windows NT Quick Beginnings, GC31-8679.
IBM Communications Server for OS/2 Warp Quick Beginnings, GC31-8189.
IBM Communications Server for Windows NT Quick Beginnings, GC31-8424.
eIBM Network Communications Server for OS/2 Guide to AnyNet, GC31-8193, GC31-8320
WorkSpace On-Demand Road Map Release 2.0, SG24-5117
WorkSpace On-Demand Handbook Release 2.0, SG24-5117
WorkSpace On-Demand Handbook (Release 1), SG24-2028
WorkSpace On-Demand Early Customer Experiences, SG24-5107
IBM Up and Running! OS/2 Warp Server, S25H-8004
WorkSpace On-Demand Administrator's Guide.,, on the web at www.ibm.com/software/network/workspace/library
MQSeries for Windows NT and Windows 2000 Quick Beginnings, GC34-5389
MQSeries for OS/Warp Quick Beginnings, GC33-1868
MQSeries Planning Guide, GC33-1349
MQSeries Intercommunication, SC33-1872
MQSeries Clients, GC33-1632
MQSeries System Administration, SC33-1873
MQSeries Command Reference, SC33-1369
MQSeries Programmable System Management, SC33-1482
MQSeries Messages, GC33-1876
MQSeries Application Programming Guide, SC33-0807
MQSeries Application Programming Reference, SC33-1673
MQSeries Using C++, SC33-1877
If you especially like or dislike anything about this book, please use one of the methods listed below to send your comments to IBM(R).
Feel free to comment on what you regard as specific errors or omissions, and on the accuracy, organization, subject matter, or completeness of this book.
Please limit your comments to the information in this book and the way in which the information is presented.
To make comments about the functions of IBM products or systems, talk to your IBM representative or to your IBM authorized remarketer.
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate, without incurring any obligation to you.
You can send your comments to IBM in any of the following ways:
Whichever method you use, ensure that you include: