LAN File Services/ESA VM FeatureIBM Program Directory LAN File Services/ESA VM Feature Version 1 Release 1 Modification Level 2 Program Number 5654-030 (as a Feature of VM/ESA Version

IBMProgram Directory

LAN File Services/ESA

VM Feature

Version 1 Release 1 Modification Level 2

Program Number 5654-030 (as a Feature of VM/ESA Version 2) or 5648-039

for Use withVM/ESA

Document Date: July 1999

GI10-8153-01

Note!

Before using this information and the product it supports, be sure to read the general information under “Notices” on page vi.

This program directory, dated July 1999, applies to LAN File Services/ESA Version 1 (LAN File Services/ESA) Release 1Modification Level 2 Service Level 1200, Program Number 5648-039 for the following:

A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM anonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Copyright International Business Machines Corporation 1993, 1999. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

COMPIDs Feature Numbers System Name

564803901 58105811581264895450545154526488

VM/ESA

564803902 58855825

OS/2

Contents

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTrademarks and Service Marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Program Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 Basic Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Optional Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.3.1 Basic Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3.2 Optional Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.4 Microfiche Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.5 Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.1 Preventive Service Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.2 Statement of Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.1 Program Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.2 Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.1 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5.1.1 OS/2 LAN Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.1.2 NFS Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.2 Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.2.1 OS/2 LAN Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.2.2 NFS Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5.3 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175.4 Program Considerations for Softcopy Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.5 System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.6 Special Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185.7 DASD Storage and User ID Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5.7.1 Considerations Of Installing LAN File Services/ESA Into A Shared FILE SYSTEM . . . . . . . 22

6.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1 Installation of LAN File Services/ESA with VMSES/E (VMFINS) . . . . . . . . . . . . . . . . . . . . 23

6.1.1 Plan Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.2 Allocate Resources for Installing LAN File Services/ESA . . . . . . . . . . . . . . . . . . . . . . 27

Copyright IBM Corp. 1993, 1999 iii

6.1.2.1 When installing on SFS: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.1.3 Install LAN File Services/ESA Using the VMFINS EXEC . . . . . . . . . . . . . . . . . . . . . . 326.1.4 Update Build Status Table for LAN File Services/ESA . . . . . . . . . . . . . . . . . . . . . . . 35

6.2 Place the New Product Into Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.3 Defining the LAN File Services/ESA user IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376.4 Tailoring the LAN File Services/ESA Host Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6.4.1 Customization of the Software License Monitor/VM . . . . . . . . . . . . . . . . . . . . . . . . . 476.4.1.1 Customization of LAN File Services/ESA to Exploit Software License Monitor . . . . . . . 476.4.1.2 Customize the LAN File Services/ESA server machine profiles . . . . . . . . . . . . . . . 49

6.5 Installing the LAN File Services/ESA FEP Drivers ( OS/2 LAN ) . . . . . . . . . . . . . . . . . . . . 506.5.1 Host to Front End Processor (FEP) Communications Considerations . . . . . . . . . . . . . . . 50

6.5.1.1 PWSCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506.5.1.2 CLAW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

6.5.2 Installing and Verifying the LAN File Services/ESA FEP Drivers . . . . . . . . . . . . . . . . . . 52

7.0 Service Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.1 VMSES/E Service Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537.2 Determining The Service Level For LAN File Services/ESA . . . . . . . . . . . . . . . . . . . . . . . 547.3 Servicing LAN File Services/ESA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.3.1 Prepare to Receive Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.3.2 Receive the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.3.3 Apply the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557.3.4 Update the New Status Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567.3.5 Build Serviced Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7.4 Place the New Service into Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.5 Installing Corrective Service on the Front End Processor. . . . . . . . . . . . . . . . . . . . . . . . . 58

8.0 Corrections to LAN File Services/ESA Guide & Reference (SH24-5264) . . . . . . . . . . . . . 598.1 Guide and Reference Additions and Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598.2 Message Additions and Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

9.0 IBM Software Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Appendix A. Overriding the VMSYS File Pool Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Reader's Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

iv LAN File Services/ESA Program Directory

Figures

1. Basic Material: Program Tape and Diskettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42. Basic Material: Japanese Program Tape and Diskettes . . . . . . . . . . . . . . . . . . . . . . . . 43. Optional Material: American English Program Diskettes . . . . . . . . . . . . . . . . . . . . . . . . 54. Optional Material: Japanese Program Diskettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55. Basic Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56. Optional Material:Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67. Related Publications For IBM Operating System/2 . . . . . . . . . . . . . . . . . . . . . . . . . . 68. Related Publications for IBM OS/2 LAN Server 3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . 69. Related Publications For VM/ESA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

10. Related Publications For VM PWSCF programming RPQ P81056: . . . . . . . . . . . . . . . . . 711. Related Publications For VM PWSCS: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712. Related Publications For IBM Workstation Data Save Facility/VM: . . . . . . . . . . . . . . . . . . 713. Related Publications For IBM TCP/IP Version 2.0 for VM: . . . . . . . . . . . . . . . . . . . . . . 814. Related Publications For IBM Personal System/2: . . . . . . . . . . . . . . . . . . . . . . . . . . . 815. Related Publications For IBM Software License Monitor: . . . . . . . . . . . . . . . . . . . . . . . 816. Related Publications For Customization, Installation & Distribution. . . . . . . . . . . . . . . . . . 817. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918. Component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919. VM Operating System Installation Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120. Software for the OS/2 LAN Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1221. Software for the OS/2 LAN Server Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1522. IBM BookManager Read level required to use softcopy pubs. . . . . . . . . . . . . . . . . . . . . 1823. Installation and Service Minidisks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1924. DASD Storage Requirements for Target Minidisks . . . . . . . . . . . . . . . . . . . . . . . . . . . 1925. Default Shared File Directory Names vs Minidisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2226. Sample LAN File Services/ESA server machine directory . . . . . . . . . . . . . . . . . . . . . . . 3927. I/O definition files by release of VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5128. Sample IOCP Deck for ESA Configuration of a Front End Processor on a Parallel Channel . . . 6129. Sample SFS Installation Override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figures v

Notices

When the abbreviation 'LFS/ESA' appears in this document it shall stand for the full name of the programproduct, 'LAN File Services/ESA '.

When the abbreviation 'FEP' appears in the document it refers to the LAN File Services/ESA front endprocessor.

When the abbreviation 'OLS' appears in the document it refers to the OS/2 LAN Server.

When the abbreviation 'SAA' appears in the document it refers to Systems Applications Architecture.

When the abbreviation 'IS' appears in the document it refers to Information Services.

When the abbreviation 'SNA' appears in the document it refers to Systems Network Architecture.

When the abbreviation 'DBCS' appears in the document it refers to Double Byte Character Set.

The term "System/390" is used to refer to both IBM System/370 and IBM System/390.

The term "CM/2 and CM2" is used to refer to Communications Manager 2.

The term "ES" is used to refer to Extended Services.

The term "ESCON" is used to refer to Enterprise systems connection.

This information was developed for products and services offered in the U.S.A. IBM may not offer theproducts, services, or features discussed in this document in other countries. Consult your local IBMrepresentative for information on the products and services currently available in your area. Any referenceto 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 notinfringe any IBM intellectual property right may be used instead. However, it is the user's responsibility toevaluate 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 document.The furnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 1�5�4-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

vi Copyright IBM Corp. 1993, 1999

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 1�6, Japan

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allowdisclaimer of express or implied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication. IBMmay make improvements and/or changes to the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not partof the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange 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:

IBM CorporationMail Station P3��522 South RoadPoughkeepsie, NY 126�1-54��U.S.A.Attention: Information Request

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 document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, theresults obtained in other operating environments may vary significantly. Some measurements may havebeen made on development-level systems and there is no guarantee that these measurements will be thesame on generally available systems. Furthermore, some measurement may have been estimated

Notices vii

through extrapolation. Actual results may vary. Users of this document should verify the applicable datafor their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.Questions on the capabilities on non-IBM products should be addressed to the suppliers of thoseproducts.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrates programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platform forwhich the sample programs are written. These examples have not been thoroughly tested under allconditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. You may copy, modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing application programs conforming toIBM's application programming interfaces.

Trademarks and Service Marks

The following terms are trademarks of the International Business Machines Corporation in the UnitedStates, or other countries, or both:

Microsoft is a registered trademark of Microsoft Corporation in the United States, other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.

ADSTAR AIX ES/9000IBM Operating System/2 OS/2AT PC/XT System/370System/390 VM/ESA ESCONC/370 FunctionPac IBMLinkExtended Services XT BookManager3090

viii LAN File Services/ESA Program Directory

1.0 Introduction

This program directory is intended for the system programmer responsible for program installation andmaintenance. It contains information concerning the material and procedures associated with theinstallation of LAN File Services/ESA. You should read all of this program directory before installing theprogram and then keep it for future reference.

The program directory contains the following sections:

4 2.0, “Program Materials” on page 4 identifies the basic and optional program materials anddocumentation for LAN File Services/ESA.

4 3.0, “Program Support” on page 9 describes the IBM support available for LAN File Services/ESA.

4 4.0, “Program and Service Level Information” on page 10 lists the APARs (program level) and PTFs(service level) incorporated into LAN File Services/ESA.

4 5.0, “Installation Requirements and Considerations” on page 11 identifies the resources andconsiderations for installing and using LAN File Services/ESA.

4 6.0, “Installation Instructions” on page 23 provides detailed installation instructions for LAN FileServices/ESA.

4 7.0, “Service Instructions” on page 53 provides detailed servicing instructions for LAN FileServices/ESA. It also describes the procedures for activating the functions of LAN File Services/ESA.

4 8.0, “Corrections to LAN File Services/ESA Guide & Reference (SH24-5264)” on page 59

Before installing LAN File Services/ESA, read 3.1, “Preventive Service Planning” on page 9. This sectiontells you how to find any updates to the information and procedures in this program directory.

1.1 Program Description

LAN File Services/ESA brings together computing environments that were previously separate "islands ofautomation."

Historically, Local Area Network (LAN) data and VM data have been stored as separate entities. LAN datahas been saved on PC-based LAN servers or on users' local disk drives, while VM data resided on largecapacity System/370 or System/390 DASD. Interaction between the two environments consisted ofoccasional uploads and downloads of files to and from the VM system, but even with this, separate copiesof data were still maintained. Additionally, users on different types of LANs and different types ofworkstations could not easily share data amongst themselves due to differences in protocols and dataformats.

With LAN File Services/ESA, many of the barriers between these environments are removed and thestrengths of each environment can complement those of the others. As a result, new function and capacityare added to all of these environments.

Copyright IBM Corp. 1993, 1999 1

LAN File Services/ESA:

4 uses VM DASD to provide file sharing services to LAN workstation users.

4 allows file sharing across multiple LANs.

4 provides its services transparently.

4 allows sharing between OS/2 LAN server requesters and Network File System (NFS) clients.

Some of the fundamental ideas in setting up and administering a LAN File Services/ESA system:

4 In an OS/2 LAN environment, LAN File Services/ESA acts as an extension of the OS/2 LAN Server.

4 In an TCP/IP environment, LAN File Services/ESA provides standard NFS Version 2 services.

4 LAN File Services/ESA uses configuration files (some on the VM system, and some on each OS/2LAN Server system that acts as a front end processor for LAN File Services/ESA). These files areread once each time LAN File Services/ESA is started. Every time LAN File Services/ESA is started ituses the current values in the configuration files.

4 Temporary changes (and some permanent ones) can be made via administrative commands to LANFile Services/ESA while LAN File Services/ESA is running. It is not always necessary to stop LAN FileServices/ESA to make important changes.

4 Almost all of the administration of LAN File Services/ESA is done from an administration virtualmachine other than the server virtual machine.

4 In an OS/2 environment LAN File Services/ESA can use two different connectivity methods: VMPWSCS and CLAW (Common Link Access to Workstations).

4 In a TCP/IP environment, communications are through the IBM TCP/IP for VM program product.

4 Setting up a LAN File Services/ESA system requires VM system programmer knowledge.

4 Administering a LAN File Services/ESA system, in general, does not require VM system programmerknowledge.

LAN File Services/ESA in an OS/2 environment has three parts:

4 A Server Message Block (SMB) protocol server on the VM system

4 An administration user ID on the VM system, and

4 A corresponding "client" in a PS/2 OS/2 running LAN Server that acts as a "front end processor" to theVM system.

OS/2 LAN Server environments use the Microsoft Server Message Block (SMB) server protocols overlower-layer NetBIOS communications protocols. LAN topologies supported in this environment includeToken-Ring and Ethernet. Physically, the VM system is attached to its front end processors via high-speedor LAN-attached connections.

LAN File Services/ESA in an NFS environment has two parts:

4 A LAN File Services/ESA server virtual machine which acts as a NFS stand alone server, and

2 LAN File Services/ESA Program Directory

4 An administration virtual machine on the VM system.

LAN File Services/ESA uses sockets over an IUCV connection to a TCP/IP machine to communicate withNFS clients. Workstations supported by this environment are any NFS clients connected by a TCP/IPnetwork.

NOTE!

For additional information refer to LAN File Services/ESA Guide & Reference (SH24-5264).

Introduction 3

2.0 Program Materials

An IBM program is identified by a program number and a feature number. The program number for LANFile Services/ESA is 5648-039.

LAN File Services/ESA is now offered as a no cost feature on VM/ESA 2.1.0. Ordering instructions are inthe announcement material for VM/ESA 2.1.0, customers who have ordered the feature on VM/ESA 2.1.0will receive the same materials as offered by the standalone product.

The program announcement material describes the features supported by LAN File Services/ESA. Askyour IBM marketing representative for this information if you have not already received a copy.

The following sections identify the basic and optional program materials available with this program.

2.1 Basic Machine-Readable Material

The distribution medium for this program is 9-track magnetic tape (written at either 1600 or 6250 BPI),3480 cartridge, 4MM DAT cartridge and optionally 3.5" 2.0 MB diskettes. The tape or cartridge containsall the programs and data needed for the host code installation. The diskette contains all the system filesfor the front end processor (FEP). Figure 1 describes the tape or cartridge and diskettes for AmericanEnglish installations. Figure 2 describes the tape or cartridge and diskettes for Japanese installations.

Figure 1. Basic Material: Program Tape and Diskettes

FeatureNumber Medium

PhysicalVolume Tape Content External Tape Label

5810 1600tape

1 of 1 Installation, System and Help files VM Host Feature

5811 6250tape

1 of 1 Installation, System, and Help files VM Host Feature

5812 3480cart


6489 4MMDAT


Figure 2 (Page 1 of 2). Basic Material: Japanese Program Tape and Diskettes



5450 1600tape

1 of 1 Japanese Installation, System, and Help files VM Japanese Feature

5451 6250tape


4 Copyright IBM Corp. 1993, 1999

2.2 Optional Machine-Readable Material

The distribution medium for the optional machine readable material is 3.5" 2.0 Mb diskette. The diskettecontains all of the programs and data needed for installation of the Front End Processor portion of LANFile Services/ESA .

2.3 Program Publications

The following sections identify the basic and optional publications for LAN File Services/ESA.

2.3.1 Basic Program Publications

Figure 2 (Page 2 of 2). Basic Material: Japanese Program Tape and Diskettes



5452 3480cart


6488 4MMDAT


Figure 3. Optional Material: American English Program Diskettes

Medium FeatureNumber

PhysicalVolume

External Label Identification

3.5" 2.0Mbdiskette

5885 1 of 1 OS/2 LS FEP

Figure 4. Optional Material: Japanese Program Diskettes

MediumFeatureNumber

PhysicalVolume External Label Identification

3.5" 2.0Mbdiskette

5825 1 of 1 OS/2 LS FEP-J

Figure 5 (Page 1 of 2). Basic Material

Publication Title Form Number

LAN File Services/ESA Licensed Program Specifications GH24-5260

LAN File Services/ESA General Information GH24-5259

LAN File Services/ESA Guide and Reference SH24-5264

Program Materials 5

2.3.2 Optional Program Publications

There is one optional publication for LAN File Services/ESA. This will be provided when the Front EndProcessor option is selected.

Figure 5 (Page 2 of 2). Basic Material


Discovering LAN File Services/ESA CDRom GK2T-5762

Figure 6. Optional Material:Publications


The LAN File Services/ESA Memo Appendices for FEP Installationand SNA Configuration

See note

Note

The LAN File Services/ESA MemoAppendices for FEP Installation and SNA Configurationis shipped with the product diskette, anddescribes how to perform the procedures describedin 6.5.2, “Installing and Verifying the LAN File Services/ESA FEP Drivers” on page 52.

2.4 Microfiche Support

There is no microfiche for LAN File Services/ESA.

2.5 Publications Useful During Installation

The publications listed in the following figures may be useful during the installation of LAN FileServices/ESA. To order copies, contact your IBM representative.

Figure 7. Related Publications For IBM Operating System/2


Information and Planning Guide G326-0160

Figure 8 (Page 1 of 2). Related Publications for IBM OS/2 LAN Server 3.0


Network Administrator's Reference Vol. 1 S96F-8428



Figure 8 (Page 2 of 2). Related Publications for IBM OS/2 LAN Server 3.0



Network Administrator's Supplement for OS/2 3.0 LAN Server S04G-1080

Commands Reference S96F-8439

Figure 9. Related Publications For VM/ESA


VM/ESA: CP Planning and Administration SC24-5521

VM/ESA: CP Planning and Administration for 370 SC24-5430

VM/ESA: CMS Command Reference SC24-5461

VM/ESA: CMS User's Guide SC24-5460

VM/ESA: CP Command and Utility Reference SC24-5519

VM/ESA: CP Programming Services SC24-5520

VM/ESA: Connectivity Planning, Administration, and Operation SC24-5448

VM/ESA: Installation SC24-5526

SAA Common Programming Interface Communications Reference SC26-4399

VM/ESA: VMSES/E Introduction and Reference SC24-5444

Figure 10. Related Publications For VM PWSCF programming RPQ P81056:


VM PWSCF Guide and Reference SC24-5593

Figure 11. Related Publications For VM PWSCS:


VM PWSCS Operating Guide and Reference SC24-5645

Figure 12. Related Publications For IBM Workstation Data Save Facility/VM:


Workstation Data Save Facility/VM General Information GH24-5232

Workstation Data Save Facility/VM Administrator's Guide and Reference SH24-5234

Workstation Data Save Facility/VM OS/2 User's Guide and Reference SH24-5237

Workstation Data Save Facility/VM AIX User's Guide and Reference SH24-5238

Program Materials 7

Figure 13. Related Publications For IBM TCP/IP Version 2.0 for VM:


TCP/IP Version 2 for VM: User's Guide SC31-6081

TCP/IP Version 2 for VM: Planning and Customization SC31-6082

TCP/IP Version 2 for VM: Programmers Reference SC31-6084

TCP/IP Version 2 for VM: Messages and Codes SC31-6151

Figure 14. Related Publications For IBM Personal System/2:


PS/2 MicroChannel to MainFrame Connection Hardware Maintenance Library G571-0239

Figure 15. Related Publications For IBM Software License Monitor:


IBM Software License Monitor/MVS and VM Guide and Reference SH24-5258

Figure 16. Related Publications For Customization, Installation & Distribution.


Workstation LAN Files Services/VM, LAN Resource Extension and Services/VM GG24-4073

Automated Installation for CID Enable ES, LAN Server V3.0 & NTS/2 GG24-3781


3.0 Program Support

This section describes the IBM support available for LAN File Services/ESA.

3.1 Preventive Service PlanningBefore installing LAN File Services/ESA, check with your IBM Support Center or use IBMLink (ServiceLink) to see whether there is additional Preventive Service Planning (PSP) information that you shouldknow. To obtain this information, specify the following UPGRADE and SUBSET values:

3.2 Statement of Support Procedures

Report any difficulties you have using this program to your IBM Support Center. In the U.S.A., if an APARis required, submit the data to the location identified in the Programming System General Informationmanual (PSGIM), G229-2228, as being responsible for the failing component.

Figure 18 identifies the component ID (COMPID), Retain Release and Field Engineering Service Number(FESN) for LAN File Services/ESA.

Figure 17. PSP Upgrade and Subset ID

Upgrade Subset Description

LFSVM LFSVM112SES VMSES/E version for AMENG

LFSVM LFSVM1J2SES VMSES/E version for JAPANESE

Figure 18. Component IDs

Retain

COMPID

FESNReleaseComponentName

564803901 112 Host Server ( VMSES/E ) 0468300

564803901 1J2 Japanese Host Server ( VMSES/E ) 0468300

564803902 112 OS/2 Front End Processor 0968301

564803902 1J2 Japanese OS/2 Front End Processor 0968301


4.0 Program and Service Level Information

This section identifies the program and any relevant service levels of LAN File Services/ESA. Theprogram level refers to the APAR fixes incorporated into the program. The service level refers to thePTFs integrated. Information about the cumulative service tape is also provided.

4.1 Program Level Information

The following APAR fixes against previous releases of Workstation LAN File Services have beenincorporated into this release:

PW00102PW00103PW00106

4.2 Service Level Information

This is LAN File Services/ESA 1.1.2 and there are no PTFs.

4.3 Cumulative Service Tape

There is no cumulative service tape or PUT tapes for LAN File Services/ESA.

10 Copyright IBM Corp. 1993, 1999

5.0 Installation Requirements and Considerations

The following sections identify the system requirements for installing and activating LAN FileServices/ESA.

5.1 Software Requirements

This section addresses the software requirements needed to set up LAN File Services/ESA for OS/2 LANserver and/or NFS.

For host code installation, the installation method is VMSES/E as shown in the following figure:

5.1.1 OS/2 LAN Server Environment

Software required for use with LAN File Services/ESA in an OS/2 LAN environment is:

Figure 19. VM Operating System Installation Method.

VM Operating System Installation Method Prerequisites

VM/ESA 2.0 or higher VMSES/E None

VM/ESA 1.1 VMSES/E SPE APAR VM54804

VM/ESA 1.5 370 Feature VMSES/E None

VM/ESA 1.0 370 Feature VMSES/E VMSES/E for LicensedPrograms Feature 7806

VM/ESA 2.1.0 VMSES/E None


Figure 20 (Page 1 of 3). Software for the OS/2 LAN Server Environment

Software Comments

VM Operating Systems For VM PWSCS connections, LAN File Services/ESA requires one of the following:

4 VM/ESA Release 2.0, or higher, with APAR VM559974 VM/ESA Release 1.1 or later, or VM/ESA Release 1.0 (370 Feature), supplemented

with the VM PWSCF PRPQ P81056 Release 1.2 with APAR VM55997

For CLAW connections, LAN File Services/ESA requires one of the following:

4 VM/ESA Release 2.0, or higher, with APAR VM559974 VM/ESA Release 1.1, or higher, with APAR VM559974 VM/ESA Release 1.0 (370 Feature), or higher, with APAR VM55997

Additional requirements are:

4 The IBM C/370 Library Version 2, program number 5688-188

| Just to Clarify: The IBM C/370 Library Version 2, program number 5688-188 IS| REQUIRED even though LFS/ESA ships integrated with VM/ESA 2.2.0 or higher along| with LE/370, i.e., LFS/ESA VM does not support LE and requires the C/370 runtime| library.

4 The IBM Software License Monitor Release 1.1.1, program number 5648-038 withAPAR PW00238.

4 The IBM Software License Monitor Release 1.1.1 is not required for VM/ESA 2.1.0customers. The pre-req has been disabled.

Either Workstation Data Save Facility/VM (WDSF/VM), program number 5684-122, orADSTAR Distributed Storage Manager Version 1 Release 1, program number 5648-020is required to use the backup and restore functions of LAN File Services/ESA. (LAN FileServices/ESA includes a built-in client to backup and restore LAN File Services/ESA data).



Software Comments

OS/2 LAN Server LAN File Services/ESA requires a front end processor consisting of a workstation runningone of the following:

4 OS/2 LAN Server Version 3.0/Advanced with OS/2 Version 2.0 or later.4 OS/2 LAN Server Version J3.0/Advanced with OS/2 Version J2.0, or later for DBCS

support (Japanese).4 OS/2 LAN Server Version H3.0/Advanced with OS/2 Version H2.0, or later for DBCS

support (Korean).4 OS/2 LAN Server Version T3.0/Advanced with OS/2 Version T2.0, or later for DBCS

support (Traditional Chinese).

Note:

1. Other levels of OS/2 LAN Servers can be used on a LAN with a front end processor,but they cannot act as a front end processor.

One of the following connectivity options is also required:

4 VM PWSCS Version 1 or higher

Note: VM PWSCS Version 1.2 is required for PWSCS communications using the IBMPS/2 MicroChannel to Mainframe Connection (MMC) card.

4 OS/2 CLAW device driver (which uses software that is shipped with LAN FileServices/ESA), provides a direct channel connection with the LAN File Services/ESAhost server using the IBM PS/2 MicroChannel to Mainframe Connection card. Thisdevice driver uses a proprietary channel protocol for communications.

4 OS/2 CLAW device driver (which uses software that is shipped with File Services),provides direct channel connection with the File Services host server using the anESCON adapter card. This device driver uses a proprietary channel protocol forcommunications.

Notes: 1. Either VM PWSCS Version 1.2 or the CLAW device driver can use the IBM PS/2

MMC card, but not both simultaneously.2. For further information on CLAW and MMC connectivity, refer to Planning for

LAN File Services/ESA in the LAN File Services/ESA Guide & Reference(SH24-5264).

3. When using PWSCS OS/2 gateway for SNA connectivity, you must installExtended Services 1.0 for OS/2 and apply ES (Extended Services) APARJR05162S.

4. For further information on SNA connectivity refer to the LFS Memo Appendices forFEP Installation and SNA Configuration.

Installation Requirements and Considerations 13

Note: Other levels of the OS/2 LAN Server can be used on the same LAN as the front end processor, butthey cannot act as a front end processor.


Software Comments

Workstation operatingsystems andrequesters

Workstations may use any of these operating systems with the requesters indicated:

4 OS/2 Version 1.3 or later with OS/2 LAN Server Version 2.0 or 3.0 LAN Requester4 OS/2 Extended Edition (includes OS/2 LAN Requester)4 DOS Version 3.3 or later, with DOS LAN Requester 2.0 or 3.0 (part of OS/2 LAN

Server Version 2.0 or 3.0)4 DOS Version 3.3 or later, with PC LAN Program (PCLP)

Workstations may use any LAN requester capable of interoperating with OS/2 LAN ServerVersion 3.0.

Note: The PCLP Version 1.3 Requester and the OS/2 Version 1.1 LAN Requestercontain some administrative incompatibilities with OS/2 LAN Server Version 1.2 andhigher. To use one of these requesters to access LAN File Services/ESA data, aworkstation user must first log on to an OS/2 Version 1.1 LAN Server domain and use theexisting cross-domain services to access resources in the OS/2 LAN Server Version 2.0and 3.0 system serving as the front end processor to LAN File Services/ESA. The usercan then communicate directly with the front end processor. Requests from the user donot pass through the OS/2 Version 1.1 LAN Server.

For DBCS support, workstations may use any of these operating systems with therequesters indicated:

4 OS/2 Verson J1.3 or later with OS/2 LAN Server Version J2.0 or J3.0 LAN Requester4 OS/2 Extended Edition (includes OS/2 LAN Requester)4 DOS Version J5.0 or J5.0/V, with DOS LAN Requester 2.0 or J3.0 (part of OS/2 LAN

Server Version J2.0 or J3.0)4 OS/2 Verson H2.0 with OS/2 LAN Server Version H2.0 or H3.0 LAN Requester4 DOS Version H5.0 or H5.0/V, with DOS LAN Requester 2.0 or H3.0 (part of OS/2 LAN

Server Version H2.0 or H3.0)4 OS/2 Verson T2.0 with OS/2 LAN Server Version T2.0 or T3.0 LAN Requester4 DOS Version T5.0 or T5.0/V, with DOS LAN Requester 2.0 or T3.0 (part of OS/2 LAN

Server Version T2.0 or T3.0)

For 3174 Peer Communications coax-attached DOS or OS/2 workstation support,workstation operating systems and software include:

For DOS:

4 DOS Release 3.3 and higher4 DOS Release 3.3 and higher with Microsoft Windows 3.0 in standard or enhanced

mode4 IBM 3174 Workstation Peer Communication Support Program4 DOS LAN Requester

For OS/2:

4 OS/2 Version 1.30.2 or later, with Extended Services or LAN Server.


5.1.2 NFS Environment

Software required for use with LAN File Services/ESA in an NFS environment are:

1. One of the following:

4 VM/ESA Release 1.0 (370 or ESA Feature)

4 VM/ESA Release 1.1

4 VM/ESA Release 2.0 or later

2. The IBM C/370 Library Version 2, program number 5688-188.

3. Transmission Control Program/Internet Protocol (TCP/IP) for VM Version 2 and above (5735-FAL) isrequired on the VM system when establishing TCP/IP communications with LAN File Services/ESAclients.

4. Workstations may use any operating systems capable of running a standard NFS Version 2 client.

5.2 Machine Requirements

This section addresses the hardware requirements needed to set up LAN File Services/ESA for OS/2 LANand NFS.

The installer user ID must have access to the appropriate tape device for the installation tape media.

5.2.1 OS/2 LAN Server Environment

Equipment recommended for use with LAN File Services/ESA in an OS/2 LAN environment:


Hardware Comments

VM processor VM processors supported by LAN File Services/ESA are any System/370 or System/390architecture machines that support a channel, an integrated Channel-to-Channel adapter,or an integrated Token-Ring adapter. Examples are the following IBM machines:

4 937x (model 12 and higher)4 4381-2x and 4381-9xE

4 3090-xxx 4 ES/9000

One of the following tape drives for installing LAN File Services/ESA on the host:

4 A 9-track/1600 bpi magnetic tape drive4 A 9-track/6250 bpi magnetic tape drive4 An 18-track/3480 cartridge tape drive



Hardware Comments

Front end processor A workstation acting as a front end processor to LAN File Services/ESA must be capableof running OS/2 LAN Server 3.0/Advanced and OS/2 Version 2.0 or later, or OS/2 LANServer J3.0/Advanced and OS/2 Version J2.0 or later.

The front end processor:

4 Must have at least 12MB of main memory (16MB or more is recommended for betterperformance)

4 Should have a hard disk of at least 80MB for OS/2, OS/2 LAN Server and LAN FileServices/ESA. The LAN File Services/ESA portion is about 1.4MB.

4 Should be based on the 80386 or later microprocessor.

Note: The LAN File Services/ESA front end processor code is memory intensive.Performance may vary depending on the number of other applications on the front endprocessor.

Connectivity equipment Connections between the VM processor and the front end processor can be made by:

4 A standard channel interface using an IBM PS/2 MicroChannel to MainframeConnection (MMC) card (Part number 95F1436). The MMC card can be used eitherwith the CLAW device driver (which uses software shipped with LAN FileServices/ESA) or with PWSCS Version 1.2.

4 An ESCON channel interface using an IBM 3712 interconnect Controller, Model 003(3712-3) with an IBM ESCON adapter card (feature number 2800). The ESCONadapter card is supported by the CLAW device driver (which uses software that isshipped with File Services).

4 Any device supported by the VM PWSCS OS/2 gateway to SNA resources4 Any device supported by CM/2 for SNA(LU6.2) connections.4 Any device supported by VM PWSCF and VM PWSCS, such as:

– 9370 Model 14 data exchange adapter– 9370 Integrated Token-Ring LAN adapter– IBM System/370 Channel Emulator/A card to an IBM 3088 Multisystem Channel

Communications Unit.– IBM System/370 Channel Emulator/A card to an integrated Channel-to-Channel

adapter on an IBM 4381 processor.

LAN media Token-Ring LANs or Ethernet LANs may be used for workstations; however, EthernetLANs are not supported as a front end processor to VM connection.

Workstations (DOS and OS/2) can optionally be coax-attached to a 3174 EstablishmentController running 3174 Peer Communications; they can access LAN File Services/ESAdata through an OS/2 LAN Server that is connected to the 3174 through a Token-Ringcard. Connectivity requirements for the workstation include one of the following:

4 IBM 3270 Connectivity Card4 IBM 3278/3279 Emulation Adapter


5.2.2 NFS Environment

Equipment recommended for use with LAN File Services/ESA in an NFS environment are:

1. VM processor

VM processors supported by LAN File Services/ESA are any System/370 or System/390 architecturemachines that support IBM TCP/IP Version 2 for VM. Refer to the TCP/IP Version 2 for VM: Planningand Customization manual for information on which VM processors are supported.

One of the following tape drives for installing LAN File Services/ESA on the host:

4 A 9-track/1600 bpi magnetic tape drive

4 A 9-track/6250 bpi magnetic tape drive

4 An 18-track/3480 cartridge tape drive

2. Connectivity Equipment

The only connectivity supported by the NFS portion of LAN File Services/ESA is through the TCP/IPvirtual machine provided by TCP/IP for VM. LAN File Services/ESA uses sockets over an IUCVconnection to the TCP/IP virtual machine to communicate with its NFS clients. Refer to the TCP/IPVersion 2 for VM: Planning an Customization manual for information on the types of connectivitysupported between the TCP/IP virtual machine and TCP/IP networks.

3. Workstations

Any programmable workstation capable of running a standard NFS Version 2 client and is capable ofconnecting to TCP/IP.

5.3 Programming Requirements

The Software License Monitor/VM is required for monitoring the licensed LAN File Services/ESA front endprocessors. Software License Monitor must be installed before you install LAN File Services/ESA. Refer to6.4.1, “Customization of the Software License Monitor/VM” on page 47 for directions on customizing theSoftware License Monitor/VM for LAN File Services/ESA.


Hardware Comments

Workstations Workstations supporting requester programs include:

4 IBM Personal Computer XT (PC/XT) family

4 IBM Personal Computer AT (PC/AT) family

4 IBM Personal System/2 (PS/2) family

4 IBM Personal System/55 (PS/55) family, for DBCS support


NOTE: Installation of Software License Monitor/VM requires a minimum level of SVM. If this level of SVMis not available, neither Software License Monitor/VM nor LAN File Services/ESA will function properly.Refer to the Software License Monitor/VM publications and program directory for further details.

A C compiler for utilities (optional, only for NFS or NFS-OLS sharing).

5.4 Program Considerations for Softcopy Publications

Refer to the following table to determine which level of IBM BookManager READ you require.

5.5 System Considerations

If you are using VMSES/E for installation:

4 Refer to the VMSES/E Introduction and Reference for additional information about VMSES/E and theVMFINS EXEC.

4 Ensure that the planner and installer user IDs have:

– read access to the MAINT 5E5 disk

– write access the MAINT 51D disk

5.6 Special Considerations

The following are special considerations for starting LAN File Services/ESA for NFS clients:

4 TCP/IP should be started.

4 VMNFS and any other NFS Version 2 server on the VM system should be disabled.

4 Portmapper virtual machine should be started.

5.7 DASD Storage and User ID Requirements

There is a default user ID and default minidisk addresses for the installation of LAN File Services/ESAdepending on the language ordered. There are also default user IDs for the LAN File Services/ESAserver and administrator virtual machines. The default user IDs are:

Figure 22. IBM BookManager Read level required to use softcopy pubs.

Operating system Level of IBM BookManager READ required

VM IBM BookManager READ/VM Release 2 (5684-062).

DOS workstation IBM BookManager READ/DOS 1.2 (5601-453)

OS/2 workstation IBM BookManager READ/2 Version 1.2.1 (5601-454)


P648039D Default installer user ID for American English

P648039E Default installer user ID for Japanese

LFSSERV Default user ID for LAN File Services/ESA server virtual machine

LFSADM Default user ID for LAN File Services/ESA administrator virtual machine

The default installer user ID will be referenced by P648039x, where you will substitute the appropriateletter for x, based on the language that you are choosing to install. The following lists the default minidiskaddresses and their descriptions:

The following table is provided here for the planning of your DASD storage requirements for installation ofLAN File Services/ESA The user ID's and minidisks will be created in the installation procedures.

Figure 23. Installation and Service Minidisks.

Minidisk Address Minidisk Usage Used By

2B2 Base system code disk VMSES/E

2C2 Sample/local disk VMSES/E

36F Production build disk VMSES/E

29D Help files VMSES/E

2DF Softcopy publications VMSES/E

2D2 Delta service disk VMSES/E

37F Test build disk VMSES/E

2A6 Alternate apply disk VMSES/E

2A2 Production apply disk VMSES/E

Figure 24 (Page 1 of 3). DASD Storage Requirements for Target Minidisks

Minidiskowner(user ID)

DefaultAddress

Storage inCylinders FB-512

BlocksSFS 4KBlocks UsageDASD CYLS

P648039x 2B2 93453390338033753350

2017203225

26400 3000 Contains all the base code shipped withLAN File Services/ESA

Note: Cylinder values defined in this table are based on a 4k block size. FB-512 block values are derived fromthe 3380 cylinder values in this table. For any Fixed Block Architecture (FBA) DASD (e.g. 3370, 9335, 9336, etc.)use the FB-512 values.




DefaultAddress



P648039x 2C2 93453390338033753350

55587

6600 450 Contains sample files and user localmodifications for LAN File Services/ESA

P648039x 2D2 93453390338033753350

2017203225

26400 3000 Contains serviced files andthe current level of service.

P648039x 2A6 93453390338033753350

11111

1320 150 Contains AUX files and version vectortable that represent your test level ofLAN File Services/ESA

P648039x 2A2 93453390338033753350

11111

1320 150 Contains AUX file and version vectortable that represent your productionlevel of LAN File Services/ESA

P648039x 36F 93453390338033753350

2219223528

29040 3300 Production build disk

P648039x 37F 93453390338033753350

2219223528

29040 3300 Test build disk

P648039x 29D 93453390338033753350

656108

10560 900 Help





DefaultAddress



P648039x 191 93453390338033753350

55587

6600 750 P648039 user ID's 191 minidisk

P648039x 2DF 93453390338033753350

8781310

10560 1200 Softcopy publications

LFSADM 191 93453390338033753350

55587

6600 750 LFSADM user ID's 191 minidisk

LFSSERV 191 93453390338033753350

55587

6600 750 LFSSERV user ID's 191 minidisk

LFSSERV 201 93453390338033753350

2017203225


LFSSERV 202 93453390338033753350

2017203225




Notes:

1. P648039E is the minidisk owner for Japanese installs.

2. The minidisks LFSSERV 201 and 202 are included here for the initial file repository. The user can addas many additional minidisks with whatever size they require in place of or in addition to theseminidisks. These minidisks must be formatted in 4096-byte blocks.

5.7.1 Considerations Of Installing LAN File Services/ESA Into AShared FILE SYSTEM

If you plan to install LAN File Services/ESA into a shared file system, please note the following:

4 If you are using a version of VMSES/E that allows you to choose the name for the shared file systeminstall, then where you see the name of VMSYS: you should substitute the name you have chosen.

4 For VMSES/E 2.1 and earlier, VMSES/E will install only into a shared file system with the name ofVMSYS:

4 For versions of VMSES/E that allow overriding the VMSYS: file pool name refer to Appendix A,“Overriding the VMSYS File Pool Name” on page 63.

4 The default user ids for the directories are P648039x, LFSSERV, LFSADM

4 You must create the shared file directories during the planning stage of the P648039 and LFSSERVuser ids.

4 When installing LAN File Services/ESA, remember to substitute the name of the shared file directoryfor any references to minidisks. The default correlation of minidisks to shared file is as follows:

Figure 25. Default Shared File Directory Names vs Minidisk

P648039x - 191 VMSYS:P648039x.

P648039x - 2B2 VMSYS:P648039x.BASE

P648039x - 2C2 VMSYS:P648039x.LOCALSAM

P648039x - 36F VMSYS:P648039x.BUILD

P648039x - 37F VMSYS:P648039x.TBUILD

P648039x - 2DF VMSYS:P648039x.PUBS

P648039x - 2D2 VMSYS:P648039x.DELTA

P648039x - 2A2 VMSYS:P648039x.PRDAPPLY

P648039x - 2A6 VMSYS:P648039x.ALTAPPLY

P648039x - 29D VMSYS:P648039x.HELP

LFSSERV - 191 VMSYS:LFSSERV.

LFSSERV - 201 Must Be A Minidisk

LFSSERV - 202 Must Be A Minidisk

LFSADM - 191 VMSYS:LFSADM.


6.0 Installation Instructions

This chapter describes the installation methods and the step-by-step procedures to install and activateLAN File Services/ESA.

The step-by-step procedures are in two column format. The steps to be performed are in bold largenumbers. Commands for these steps are on the left hand side of the page in bold print. Additionalinformation for a command may exist to the right of the command. For more information about the twocolumn format see 'Understanding Dialogs with the System' in the VM/ESA Installation Guide.

Note!

The sample console output presented throughout these instructions was produced on a VM/ESA 1.2.0system. If you're installing LAN File Services/ESA on a different VM/ESA system, the results obtainedfor some commands may differ from those depicted here.

6.1 Installation of LAN File Services/ESA with VMSES/E (VMFINS)

VMFINS will be used to install LAN File Services/ESA. VMFINS is an installation aid supplied as part ofVMSES/E to make installation of VM and Licensed Program Products (LPs) consistent. The "InstallScenarios" chapter illustrates how various VMFINS operands and options are used.

6.1.1 Plan Your Installation

The VMFINS command will be used to plan the installation. This is a two step process that will:

4 load the first tape file, containing VMSES/E control files

4 generate a 'PLANINFO' file listing

– all user ID/mdisks requirements

– required products

1 Log on as LAN File Services/ESA installer planner. This user ID can be anyID that has read access to MAINT's 5E5 minidisk and write access toMAINT's 51D minidisk.

logon MAINT

2 Mount the LAN File Services/ESA installation tape onto your tape drive.


3 Attach the physical tape drive and add it to the user ID at virtual address 181.The VMFINS EXEC requires the tape drive to be attached at virtual address181.

att nnn * 181 Note: "nnn" is the physical address of the tapedrive.

4 Establish read access to the VMSES/E code.

link maint 5e5 5e5 rraccess 5e5 b

Note: If installing on VM/ESA Release 1.0 370Feature link to SESELPS and access EE5.

5 Establish write access to the Software Inventory disk.

link maint 51d 51d mraccess 51d d

Note: If installing on VM/ESA Release 1.0 370Feature link to SESELPS.

6 Load the product memos.

vmfins install info (nomemo The NOMEMO option will load the memos from thetape but will not issue a prompt to send them tothe system printer. If you would like a prompt tosend the memos to the printer do not specifyNOMEMO.

This command will perform the following:

4 load Memo-to-Users

4 load the product control files (PPF andPRODPART)

4 create VMFINS PRODLIST on your A-disk.The VMFINS PRODLIST contains a list ofproducts on the installation tape.

5 6VMFINS276�I VMFINS processing startedVMFINS19�9I VMFINS PRODLIST created on your A-diskVMFINS276�I VMFINS processing completed successfully

; <

7 Obtain resource planning information for LAN File Services/ESA.


Notes:

a. The product will not be loaded by the VMFINS command at this time.

b. If this product is being installed on a VM/ESA Release 1.1 or VM/ESA Release 1.0 370 Feature(+ VMSES/E for Licensed Programs feature) you will need to use the PROD keyword instead ofthe PPF keyword IF you wish to have the opportunity to change the installation defaults.

vmfins install ppf 5648039x {LFS | LFSSFS} (plan nomemo

Use LFS if installing using minidisks or LFSSFS ifinstalling using SFS

The PLAN option indicates that you want VMFINSto perform requisite checking, plan systemresources, and provide an opportunity to overridethe defaults in the product parameter file. You canoverride the following:

4 the name of the product parameter file

4 the default user IDs

4 minidisk/directory definitions

Note:

4 If you change the PPF name, a default user ID, or other parameters via a PPF override, you'llneed to use your changed values instead of those indicated (when appropriate), throughout therest of the installation instructions, as well as those provide for servicing LAN FileServices/ESA.For example, you'll need to specify your PPF override file name instead of5648039x for certain VMSES/E commands. For more information about changing the VMSYSfile pool name see see Appendix A, “Overriding the VMSYS File Pool Name” on page 63

4 If you're not familiar with creating PPF overrides using VMFINS, you should review the 'Usingthe Make Override Panel' section in Chapter 3 of the VMSES/E Introduction and Referencebefore you continue.

5 6VMFINS276�I VMFINS processing startedVMFSIP25��E Requisite error, missing requisite 5688188 for PRODID 5648�39x%LFSVMFREQ28�6W The following requisites for product 5648�39x componentare not satisfied.VMFREQ28�6W Type Product Component PTF

------------- -------- ---------------- -------------VMFREQ28�6W Requisite 5688188Do you want to create an override for 5648�39xLAN File Services/ESA (prodid 5648�39x)?Enter � (No), 1 (Yes) or 2 (Exit)

; <

Installation Instructions 25

0 Enter a 0 to bypass creating an override, a 1 tocreate an override, or 2 to exit the VMFINS exec.

5 6VMFRMT276�I VMFRMT processing startedVMFRMT276�I VMFRMT processing completed successfullyVMFPLA19�9I 5648�39x PLANINFO created on your A-diskVMFINS276�I VMFINS processing completed successfullyReady;

; <

8 Using the command below, review the install message log ($VMFINS$MSGLOG). If necessary, correct any problems before going on. Forinformation about handling specific build messages, see VM/ESA: SystemMessages and Codes, or use on-line HELP.

vmfview install

VMFREQ2806W unsatisfied product requisites message

During VMFINS processing, you may receive the following message:

VMFREQ28�6W The following requisites for product 5648�39x LFS are not satisfied Type Product Component PTF ---------- ---------- ---------- ---------- 1. Requisite 5688188

This message indicates that 5688188 is a pre-requisite product for LAN File Services/ESA. Thismay be a result of 5688188 not being in VMSES/E format. If 5688188 is not in VMSES/E formatand it has been installed on your system you will need to update the system level softwareinventories by issuing the following commands:

Note: Complete this step only if you received message VMFREQ28�6W and the requisite product isnot in VMSES/E format.

vmfsim modify vm sysrecs d tdata :prodid 5688188 :ppf 5688188 notvmsese :stat received

vmfsim modify vm sysapps d tdata :prodid 5688188 :ppf 5688188 notvmsese :stat applied

where:

VM SYSRECS is the default name of the Receive Status table.

VM SYSAPPS is the default name of the Apply Status table.

End of VMFREQ2806W unsatisfied product requisites message


6.1.2 Allocate Resources for Installing LAN File Services/ESA

You will use the planning information in the 5648039x PLANINFO file, created in the PLAN step, to:

4 Create the P648039x user directory

4 Create the LFSADM user directory

4 Attach the appropriate minidisks to the userids

4 Place the new directories on-line

1 To create the P648039x directory (P648039x DIRECT), copy the 5648039xPLANINFO file.

copyfile 5648039x planinfo a P648039x direct a (lrecl 80 recfm f

The P648039x user directory entry information is located at the bottom of theP648039x DIRECT file you just created. It contains all of the necessary linksand privilege classes necessary for the P648039x user ID.

Edit the P648039x DIRECT file.

xedit P648039x direct

a. Remove all of the lines prior to and including the line REPLACE USER:P648039x.

b. Keep all of the lines that were indented under REPLACE USER:P648039x.

c. Modify the password in the USER statement.

d. If the default FILEPOOL VMSYS: was not used, then modify the IPLstatement in the direct file to refer to your filepool name.

2 If you are running VM/Directory Maintenance (DIRMAINT), and you wish tohave DIRMAINT automatically allocate minidisk space for userid P648039x,first add the P648039x directory to the user directory.

dirm add P648039x

Next, give the following command for each of the 10 minidisks to be ownedby P648039x, as listed in Figure 24 on page 19. Use the values in theFigure 24 on page 19 to fill in the userid, default minidisk address, andnumber of FB-512 blocks. See your DIRMAINT Administrator or check yourDIRMAINT control files for your system's groupname value. If you are not


using fixed block architecture (FBA) DASD, modify your DIRMAINTcommands accordingly.

dirm amd P648039x default_address fb-512 autog FB-512_Blocks groupname

3 If you do NOT wish to have DIRMAINT automatically allocate minidisk spacefor userid P648039x, add the MDISK statements to the directory entry forP648039x. Use Figure 24 on page 19 to obtain minidisk requirements forP648039x.

Next, add the P648039x directory to the user directory.

4 Place the new directory on-line using VM/Directory Maintenance (DIRMAINT)or an equivalent CP directory maintenance method. The DIRMAINTcommand is listed below.

dirm direct

5 Logoff of MAINT or switch to a new emulator session.

6 Logon to P648039x.

logon P648039x

7 Format all of the minidisks for userid P648039x.

format default_address access_letter

8 Switch back to the MAINT user ID.

9 To create the LFSADM directory (LFSADM DIRECT), copy the 5648039xPLANINFO file.

copyfile 5648039x planinfo a LFSADM direct a (lrecl 80 recfm f

The LFSADM user directory entry information is located in the middle of theLFSADM DIRECT file you just created. It contains all of the necessary linksand privilege classes necessary for the LFSADM user ID.

Edit the LFSADM DIRECT file.

xedit LFSADM direct


a. Remove all of the lines prior to and including the line REPLACE USER:LFSADM.

b. Keep all of the lines that were indented under REPLACE USER:LFSADM.

c. Remove any lines that occur after the indented section referred to in Part“b” above.

d. Modify the password in the USER statement.

10 If you are running VM/Directory Maintenance (DIRMAINT), and you wish tohave DIRMAINT automatically allocate minidisk space for userid LFSADM,first add the LFSADM directory to the user directory.

dirm add LFSADM

Next, give the following command for the one minidisk to be owned byLFSADM, as listed in Figure 24 on page 19 Use the values in Figure 24 onpage 19 to fill in the userid, default minidisk address, and number of FB-512blocks. See your DIRMAINT Administrator or check your DIRMAINT controlfiles for your system's groupname value. If you are not using Fixed BlockArchitecture(FBA) DASD, modify your DIRMAINT command accordingly.

dirm amd LFSADM 191 fb-512 autog FB-512_Blocks groupname

11 If you do NOT wish to have DIRMAINT automatically allocate minidisk spacefor userid LFSADM, add the MDISK statements to the directory entry forLFSADM. Use Figure 24 on page 19 to obtain minidisk requirements forLFSADM.

Next, add the LFSADM directory to the user directory.


dirm direct

13 Logoff of MAINT.

logoff MAINT

14 Logon to LFSADM.


logon LFSADM

15 Format the 191 minidisk for userid LFSADM.

format 191 access_letter

Note: You will create the LFSSERV directory in a later step in theinstallation process.

16 Logoff LFSADM.

logoff LFSADM

6.1.2.1 When installing on SFS:

1 Obtain the user directory from the 5648039x PLANINFO file.Note: The user directory entry is located at the bottom of the PLANINFO fileof the resource section; these entries will contain all of the links and privilegeclasses necessary for the P648039x user ID.

2 If you're installing LAN File Services/ESA on a VM/ESA 370 Feature system,the following directory entry changes must be made:

4 For the P648039x directory entry:

– Add an OPTION ECMODE statement prior to the CONSOLE statement.

– Modify the LINK statements for the MAINT 5E5 and 51D minidisks sothat the SESELPS EE5 and 51D minidisks are linked.

3 Add the P648039x directory to the system directory.

4 Change the passwords for P648039x from xxxxx to a valid password, inaccordance with your security guidelines.

5 Place the new directories on-line using VM/Directory Maintenance(DIRMAINT) or an equivalent CP directory maintenance method.

Note

All minidisks for the P648039x user ID must be formatted before installingLAN File Services/ESA.

6 To continue installing LAN File Services/ESA with SFS, you'll need to do thefollowing:


a Determine the number of 4k blocks that are required for SFS directoriesyou'll use by adding up the 4K blocks required for each SFS directoryyou plan to use.

If you intend to use all of the default LAN File Services/ESA SFSdirectories, the 4K block requirements for each LAN File Services/ESAare summarized in Figure 24 on page 19

This information will be used when enrolling the P648039x to theVMSYS filepool.

b Enroll user P648039x in the VMSYS filepool using the ENROLL USERcommand:

ENROLL USER P648039x VMSYS (BLOCKS blocks

where blocks is the number of 4k blocks that you calculated in theprevious step.

Note: This must be done from a user ID that is an administrator forVMSYS: filepool.

c Determine if there is enough blocks available in the filepool to installLAN File Services/ESA. This information can be obtained from theQUERY FILEPOOL STATUS command. Near the end of the outputfrom this command is a list of minidisks in the filepool and the numberof blocks free. If the number of blocks free is smaller than the total 4kblocks needed to install LAN File Services/ESA you will need to addspace to the filepool. See the VM/ESA SFS and CRR Planning,Administration, and Operation manual for information on adding spaceto a filepool.

d Create the necessary subdirectories listed in the 5648039x PLANINFOfile using the CREATE DIRECTORY command.

set filepool vmsys:create directory dirid

dirid is the name of the SFS directory you'recreating, such as:

create directory .LFScreate directory .LFSbase :

If necessary, see the VM/ESA CMS CommandReference manual for more information about theCREATE DIRECTORY command.

A complete list of default LFS SFS directories is provided in Figure 25on page 22.

Note: Subdirectories, when required, must be created from therespective user IDs.


e Give the MAINT user ID READ authority to the general-use test builddirectory, using the GRANT AUTHORITY command.

grant auth vmsys:P648039x.LFS.build to MAINT (read newread

If necessary, see the VM/ESA CMS CommandReference manual for more information about theGRANT AUTHORITY command.

f If you intend to use an SFS directory as the work space for theP648039x used ID, include the following IPL control statement in theP648039x directory entry:

IPL CMS PARM FILEPOOL VMSYS

This will cause CMS to automatically access the P648039x's topdirectory as file mode A.

6.1.3 Install LAN File Services/ESA Using the VMFINS EXEC1 Logon to the installation user ID P648039x.

logon P648039x

2 Create a PROFILE EXEC that will contain the access of MAINT's 5E5 and51D minidisks.

xedit profile exec a===> input /**/===> input 'access 5e5 b'===> input 'access 51d d'===> file

Note: If installing on VM/ESA Release 1.0 370Feature the first access should be for minidiskEE5.

3 Execute the profile to access MAINT's minidisks.

profile

4 Verify that the LAN File Services/ESA installation tape is mounted onto yourtape drive.

5 Disconnect from P648039x. Log on to the MAINT userid. Attach the physicaltape drive and add it to user ID P648039x at virtual address 181, and thenreturn to your P648039x session. The VMFINS EXEC requires the tape driveto be attached at virtual address 181.


disc

logon MAINT

att nnn P648039x 181 Note: "nnn" is the physical address of the tapedrive.

logoff MAINT

logon P648039x

6 Install LAN File Services/ESA from the P648039 userid.Note: If this product is being installed on VM/ESA Release 1.1 or VM/ESARelease 1.0 370 Feature (+ VMSES/E for Licensed Programs feature) youwill need to use the PROD keyword instead of the PPF keyword IF you wishto have the opportunity to change the installation defaults. This steprequires several minutes to run to completion.

vmfins install ppf 5648039x {LFS | LFSSFS} (nomemo nolink


The NOLINK option indicates that you don't wantVMFINS to link to the appropriate minidisks, onlyaccess them if not accessed. These are theminidisks defined in the :DCL section of the PPFfile.

If you have created a ppf override file during theplan stage, use the name of the override fileinstead of 5648039x.

Sample console output


VMFINS276�I VMFINS processing startedVMFREQ28�5I Product 5648�39x componentLFSINS passed requisitecheckingDo you want to create an override for 5648�39x LFS (prodid 5648�39x)?Enter � (No), 1 (Yes) or 2 (Exit)

0 Enter a 0 to bypass creating an override, a 1 tocreate an override, or 2 to exit the VMFINS exec.

VMFINST Processing StartedVMFLDP27�6I 5648�39x LFS (prodid 5648�39x) will be process as a PDI product.VMFSET276�I VMFSETUP processing startedVMFUTL22�5I Minidisk|Directory Assignments:

String Mode Stat Vdev Label/DirectoryVMFUTL22�5I LOCALSAM E R/W 2C2 P642C2VMFUTL22�5I APPLY F R/W 2A6 P642A6VMFUTL22�5I G R/W 2A2 P642A2VMFUTL22�5I DELTA H R/W 2D2 P642D2VMFUTL22�5I BUILD1 I R/W 37F P6437FVMFUTL22�5I BUILD3 J R/W 29D P6429DVMFUTL22�5I BASE K R/W 2B2 P642B2VMFUTL22�5I -------- A R/W 191 P64191VMFUTL22�5I -------- B R/O 5E5 MNT5E5VMFUTL22�5I -------- D R/W 51D MNT51DVMFUTL22�5I -------- S R/O 19� MNT19�VMFUTL22�5I -------- Y/S R/O 19E MNT19EVMFSET276�I VMFSETUP processing completed successfullyVMFREC276�I VMFREC processing startedVMFREC1852I Volume 1 of 1 of INS TAPE 94�� AXLVMFREC1851I (1 of 9) VMFRCAXL processing AXXLIST AXLVMFRCX2159I Loading � part(s) to DELTA 2D2 (H)VMFREC1851I (2 of 9) VMFRCPTF processing PARTLST CPTF

.

.

.VMFREC276�I VMFREC processing completed successfullyVMFINS276�I VMFINST processing completed successfullyVMFINS276�I VMFINS processing completed successfullyReady(��4);

End of Sample console output

7 Using the command below, review the install message log ($VMFINS$MSGLOG). If necessary, correct any problems before going on. For


information about handling specific build messages, see VM/ESA: SystemMessages and Codes, or use on-line HELP.

vmfview install

6.1.4 Update Build Status Table for LAN File Services/ESA1 From the P648039x user ID, update the VM SYSBLDS software inventory file

for LAN File Services/ESA.

vmfins build ppf 5648039x {LFS | LFSSFS} (serviced nolink


The SERVICED option will build any parts that areflagged as serviced on the install tape. Theseparts may consist of saved segments or other partswhich can not be shipped on a VMSES/Eformatted install tape.

If you have created a ppf override file during theplan stage, use the name of the override fileinstead of 5648039x.

Sample console output


VMFINS276�I VMFINS processing startedVMFREQ28�5I Product 5648�39 component LFS passed requisite checkingVMFSET276�I VMFSETUP processing startedVMFUTL22�5I Minidisk|Directory Assignments:

String Mode Stat Vdev Label/DirectoryVMFUTL22�5I LOCALSAM E R/W 2C2 P642C2VMFUTL22�5I APPLY F R/W 2A6 P642A6VMFUTL22�5I G R/W 2A2 P642A2VMFUTL22�5I DELTA H R/W 2D2 P642D2VMFUTL22�5I BUILD1 I R/W 37F P6437FVMFUTL22�5I BUILD3 J R/W 29D P6429DVMFUTL22�5I BASE K R/W 2B2 P642B2VMFUTL22�5I -------- A R/W 191 P64191VMFUTL22�5I -------- B R/O 5E5 MNT5E5VMFUTL22�5I -------- D R/W 51D MNT51DVMFUTL22�5I -------- S R/O 19� MNT19�VMFUTL22�5I -------- Y/S R/O 19E MNT19EVMFSET276�I VMFSETUP processing completed successfullyVMFBLD276�I VMFBLD processing startedVMFBLD1851I Reading build listsVMFBLD2182I Identifying new build requirementsVMFBLD2182I No new build requirements identifiedVMFBLD2179I There are no build requirements matching your request at this time.

No objects will be builtVMFBLD218�I There are � build requirements remainingVMFBLD276�I VMFBLD processing completed successfullyVMFINB26�3I Product builtVMFINB2173I No verification exec found for this productVMFINB2822I Product 5648�39x LFSbuilt successfullyVMFINS276�I VMFINS processing completed successfullyReady;

End of Sample console output

6.2 Place the New Product Into Production

1 Place LAN File Services/ESA into production.

access 37F eaccess 36F fvmfcopy * * e = = f (prodid 5648039x olddate replace

37F is the minidisk that the new code was loadedto during the installation step.

36F is the production build disk.


Note

If you installed into a shared file system remember to substitute the name of the correspondingdirectory for the 37F and 36F.

What's next?

You have now completed the installation of LAN File Services/ESA using VMSES/E. Continue with6.3, “Defining the LAN File Services/ESA user IDs” to create the LAN File Services/ESA user ID(s).

6.3 Defining the LAN File Services/ESA user IDsOne or more LAN File Services/ESA virtual server machines can be defined on agiven VM/ESA system. Each LAN File Services/ESA server machine will access theFile Services system disk (P648039D 36F) to obtain the LAN File Services/ESAMODULE and a default copy of the PROFILE LFS.

1 From the P648039D userid, access the LAN File Services/ESA sample disk.

access 2c2 f The sample disk contains a sample server machinedirectory. The installation user ID is P648039E forJapanese.

2 Create an LAN File Services/ESA server machine user ID

copyfile lfsserv direct f = = a Copy the sample directory to the A-disk so that itcan be modified.

3 Modify the LFSSERV DIRECT file.

xedit lfsserv direct a Figure 26 on page 39 is a sample of the directorythat you are now looking at. You should modifythe following where applicable:

4 the password

4 running in 370 mode or ESA mode.

4 the C/370 library link

4 the dedicate statements to request the systemaddresses for the CLAW connection.


For CLAW Connections - Please Note

This is the first of four places where you will be asked tospecify line addresses for the CLAW connections. The host side andthe PC side must identify the CLAW line address by the same number(s)or communication between the two sides will not occur.

In the LFSSERV DIRECT file, the DEDICATEstatements use both the even and the odd 4-digit line address.

In the LFS CONFIG file, the LINK statementuses only the even 4-digit line address.

In the PROFILE LFS file, the DETACH, VARY OFF,VARY ON, and ATTACH statements use both the even and theodd 4-digit line addresses.

On the SET CONFIGURATION panel of the FEP installationon the PS/2, the CHANNEL ADDRESS field uses the lasttwo digits of the even line address.


USER LFSSERV password 128M 256M BG* Use the following line if running in a 370 mode virtual machine* USER LFSSERV password 16M 64M BGMACHINE ESA* Use the following line if running in a 370 mode virtual machine* MACHINE 370IUCV ANYIUCV ALLOWIUCV *IDENT RESANY GLOBALOPTION ACCT DIAG98 MAXCONN 1024* Use the following line if running in a 370 mode virtual machine* OPTION ACCT DIAG98 ECMODE BMX MAXCONN 1024IPL CMSCONSOLE 009 3215 TSPOOL 00C 2540 READER ASPOOL 00D 2540 PUNCH ASPOOL 00E 1403 A*MDISK 191 dasd_type start_location end_location volid MR READ********* LFS/VM Repository *************MDISK 201 dasd_type start_location end_location volid MW*MDISK 202 dasd_type start_location end_location volid MW********* End of Repository ********************* Change the installer user ID if it is not P648039D *********LINK P648039D 36F 36F RRLINK P648039D 2C2 2C2 RRLINK P648039D 29D 29D RRLINK MAINT 190 190 RRLINK MAINT 19D 19D RRLINK MAINT 19E 19E RR*** The following LINK statement links the C/370 Library diskLINK MAINT nnn 120 RR*** The following DEDICATE statements show how to define CLAW devices.*** The xxxx is the even line address, and the yyyy*** is the next sequential odd line address.*DEDICATE xxxx xxxx*DEDICATE yyyy yyyy

Figure 26. Sample LAN File Services/ESA server machine directory

4 Send the LFSSERV DIRECT file to the MAINT userid.

sf LFSSERV direct a maint

5 Logoff the P648039x user ID or open a new emulator session.


6 Logon to MAINT. Receive the LFSSERV DIRECT file sent by the P648039xuser ID.

logon MAINT

rdrlist

receive

7 If you are running VM/Directory Maintenance (DIRMAINT), and you wish tohave DIRMAINT automatically allocate minidisk space for userid LFSSERV,add the LFSSERV directory to the user directory.

dirm add LFSSERV

Next, give the following command for each of the 3 minidisks to be owned byLFSSERV, as listed in Figure 24 on page 19. Use the values in Figure 24on page 19 to fill in the default minidisk address and number of FB-512blocks. See your DIRMAINT Administrator or check your DIRMAINT controlfiles for your system's groupname value. If you are not using Fixed BlockArchitecture(FBA) DASD, modify your DIRMAINT commands accordingly.

dirm amd LFSSERV default_address fb-512 autg FB-512_blocks groupname

8 If you do NOT wish to have DIRMAINT automatically allocate minidisk spacefor userid LFSSERV, edit the MDISK statements in the directory entry forLFSSERV. Use Figure 24 on page 19 to obtain minidisk requirements forLFSSERV.

Next, add the LFSSERV directory to the user directory.


dirm direct

10 Logoff the MAINT user ID, or open a new emulator session.

11 Logon to LFSSERV


logon LFSSERV

12 Format the 191, 201 and 202 minidisks for userid LFSSERV.

format 191 a

format 201 b (blksize 4k The PWS minidisks were defined in 6.3, “Definingthe LAN File Services/ESA user IDs” on page 37.The default addresses are 201 and 202.

format 202 b (blksize 4k BLOCKSIZE 4K is used to obtain the maximumperformance from the server machine. Additionallya blocksize of 4k is required to ensure that theFASTBUFS record in the LFS CONFIG willfunction properly. (Refer to the LAN FileServices/ESA Guide & Reference (SH24-5264).)

What's next?

You have now completed the creation of the LAN File Services/ESA server machine. Continue with6.4, “Tailoring the LAN File Services/ESA Host Software” to tailor the host software.

6.4 Tailoring the LAN File Services/ESA Host SoftwareThis section highlights the tailoring of the host software. The LAN FileServices/ESA contains a complete description of the files involved and how theyshould be tailored.

To tailor the LAN File Services/ESA server machine LFSSERV perform thefollowing steps:

1 Access the LAN File Services/ESA samples disk.access 2c2 d

2 Use the COPYSAMP EXEC to copy the configuration files from the LANFile Services/ESA samples disk to your A-disk.

copysamp


3 Create the LFS CONFIG for the server machine, selecting the appropriatefile from those described below as the source of the copy.

The LFS CONFIG contains fixed length (80 character) records that definethe general environment under which LAN File Services/ESA will run. Theserecords are restricted to columns 1 through 71, with no continuation.

copyfile fn ft a lfs config a fn ft is one of the following files depending on youroperating environment:

4 LFSOLS CONFIG. This file sets up the LANFile Services/ESA for OS/2 LAN serving. Usethis file if you will only be supporting OS/2 LANServer users.

4 LFSNFS CONFIG. This file sets up LAN FileServices/ESA for NFS serving. Use this file ifyou will only be supporting NFS Clients.

4 LFSALL CONFIG. This file sets up LAN FileServices/ESA for both environments. Use thisfile if you will be supporting both NFS andOS/2 LAN servers.

4 Modify the LFS CONFIG file:Below is an example of what you may need to modify: (Refer to the LAN FileServices/ESA Guide & Reference (SH24-5264))

4 The global resource id's are for the server. These must be modified ifmore than one LAN File Services/ESA virtual machine will be installed.

4 Authorizations for other virtual machines to connect to this LAN FileServices/ESA virtual machine's administrative feature.

4 Minidisks which are to be accessible to LAN File Services/ESA.

4 Virtual storage usage tuning parameters.

4 The host and workstation code pages (by using the CODEPAGE record),if using other than American English code pages.

4 If you are using Japanese, update the LANG record to Kanji.

4 If you are using CLAW, update the LINK statement at the top of the LFSCONFIG file, in the form LINK even_line_address fepname CLAW.


For CLAW Connections - Please Note

This is the second of four places where you will be asked tospecify line addresses for the CLAW connections. The host side andthe PC side must identif

Documents

LAN File Services/ESA VM FeatureIBM Program Directory LAN File Services/ESA VM Feature Version 1 Release 1 Modification Level 2 Program Number 5654-030 (as a Feature of VM/ESA Version