----------------------------------------------------------------------------- QUICK HELP FOR INSTALLATION OF IBM OS/2 WARP SERVER (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- QUICK HELP FOR INSTALLATION OF IBM OS/2 WARP SERVER (C) COPYRIGHT IBM CORP. 1996 (C) COPYRIGHT IBM CORP. 1996 1.0 PURPOSE ____________ The purpose of this document is to describe the installation testing results of the IBM Enterprise LAN Integration Test (ELITE) laboratory. The informa- tion contained in the report is intended to assist customers in getting IBM OS/2 Warp Server installed and running as quickly and easily as possible. It is intended as a supplement to the product information and publications. The report assumes familiarity with the products involved. 1.1 OVERVIEW _____________ U.S. GA DATE 02/27/96 SYSLEVEL OS/2 WARP BASE OPERATING SYSTEM COMP ID: 5622-74700 VERSION: 3.01 CURRENT CSD LEVEL: XR03005 IBM OS/2 LAN SERVER COMP ID: 5622-88900 VERSION: 5.0 CURRENT CSD LEVEL: IP08200 IBM LAN ADAPTER AND PROTOCOL SUPPORT COMP ID: 5622-90900 VERSION: 5.0 CURRENT CSD LEVEL: WR08200 IBM LAN DISTANCE CONNECTION SERVER COMP ID: 5622-88600 VERSION: 5.0 CURRENT CSD LEVEL: LD08200 IBM SYSTEMVIEW FOR OS/2 COMP ID: 5622-88700 VERSION: 1.01 CURRENT CSD LEVEL: XR00005 IBM PRINT SERVICES FACILITY/2 COMP ID: 5622-88800 VERSION: 2.0 CURRENT CSD LEVEL: UR00000 IBM PERSONALLY SAFE AND SOUND COMP ID: 5622-88400 VERSION: 5.0 CURRENT CSD LEVEL: 3009010 IBM TCP/IP COMP ID: 5622-59100 VERSION: 3.1 Page 2 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 CURRENT CSD LEVEL: UN00002 ADD'L DOC IBM OS/2 Warp Server "Up and Running!" - Document number ______________________________________ S25H-8004 IBM OS/2 Warp Server "Easy Start" - Document number S25H-8003 _________________________________ -- Page 3 of 90 (C) COPYRIGHT IBM CORP. 1996 IBM OS/2 Warp Server includes the following IBM products: o OS/2 Warp with WINOS2 o LAN Server (includes LAN Adapter and Protocol Support) o LAN Distance Connection Server o SystemView for OS/2 o Network SignON Coordinator/2 o Personally Safe and Sound o Print Services Facility/2 o TCP/IP OS/2 Warp base operating system is an advanced 32-bit operating system that runs both 16-bit and 32-bit applications on systems. OS/2 Warp is a multi- tasking operating system that runs DOS, OS/2, and Windows applications. This version, OS/2 Warp Version 3.01, is easier to use and has better performance than previous versions of the OS/2 Warp operating system. IBM LAN Server provides File and Print Sharing Services that allow you to share directories, printers, and serial devices across a local area network (LAN). IBM LAN Server also provides the following services: o OS/2 File and Print Client (IBM LAN Requester) o Adapters and Protocol Services (Multi-Protocol Transport Services - MPTS) o LAN Server administration o LAN Support Program o Various LAN utility programs Warp Server also provides NetWare File and Print Gateway Service. When installed on a File and Print Sharing Server, the NetWare Gateway Service enables users at File and Print Sharing clients to access resources shared by NetWare servers. At the server, you are going to use as the gateway, you an log in to NetWare and map local device names to NetWare resources. Then you can share those device names with your LAN Server users. LAN Distance Connection Server provides remote access services for asynchro- nous, synchronous, ISDN and X.25 communications connections for remote LAN access environments. Remote Access Services allows multiple remote work- stations to dial in concurrently and access LAN Resources. The number of remote workstations supported is determined by your workstation's processing power, its communications adapters. Remote Access Services provides the ability to: o Answer incoming calls to establish connections o Route and filter data to bridge the Remote Access Client workstations to the LAN Page 4 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 o Helps prevent unauthorized access to provide security for LAN resources o Perform other administrative functions for the LAN Distance Wide Area Network (WAN) System Management Services provided by SystemView for OS/2 offers the admin- istrator a broad range of functions for managing individually managed systems and groups of managed systems on a LAN. System Management Services operates on a single logical LAN, which can consist of one NetBIOS, TCP/IP, or IPX LAN, or multiple LANs connected by routers or bridges. The configuration might include one or more SystemView Managers. System Management Services provides the ability to: o Keep track of hardware and software resources o Keep the workstations on the LAN running efficiently o Make software available to users at managed systems o Define groups of managed systems o Schedule these services to happen at a future date and time on selected groups Network SignON Coordinator/2 provides password coordination that gives the user a single-menu interface to log on, log off, or change passwords on mul- tiple user accounts simultaneously. Backup and Recovery Services provided by IBM Personally Safe and Sound allows you to safeguard your workstation against possible loss of information by making backups of your OS/2 files and folders. It has facilities to make backups of files automatically or manually and can restore these files selec- tively. Once you designate how your backups are restored, Backup and Recovery Services manages their backup and retrieval for you. The background execution of Backup and Recovery Services means that normal work can continue with minimal interruption. Backup and Recovery Services compresses files as they are backed up to conserve space on the media and finds data it has backed up using special index files, which are automatically saved by this service whenever it does a backup. Backup and Recovery Services provides you with the ability to: o Define which files and folders you want to back up as well as where and how you want to back them up o Schedule backups or instigate them manually o Keep track of which files PSnS has backed up o Decide whether to perform an incremental backup of the files or to back up all of the files IBM Print Services Facility allows you to print file formats that your printer typically does not support. Advanced Print Services automatically performs data stream transforms to convert the data in your document into the type of data required by the printer. For example, Advance Print Services can transform a PostScript document into an Advanced Function Presentation (AFP) document that can be printed on a high-speed IBM printer or transform an AFP document into a document that can be printed on an HP LaserJet printer. Advanced Print Services lets users send print jobs from work- stations running OS/2, Windows, DOS, or AIX. -- Page 5 of 90 (C) COPYRIGHT IBM CORP. 1996 Transmission Control Protocol/Internet Protocol (TCP/IP) is a set of proto- cols, or standards, that define how workstations can communicate with one another. A TCP/IP network, which can be established in any type of physical network (such as Ethernet or Token-Ring), is called an internet. You can use TCP/IP to establish your own internal internet and to connect to the global TCP/IP network known as the Internet. Using TCP/IP, users can: o Share data o Exchange electronic mail (e-mail) o Access programs and information on other computers o Access the collection of hypermedia information known as the World Wide Web The TCP/IP domain name system (DNS) is maintained by domain name servers located throughout the network. You can configure one or more name servers on your network to resolve the host names used on the network. Typically, IP addresses and host names on a network are maintained in relatively static tables at the name server. This can make it difficult and time-consuming to change a network's infrastructure or to support mobile clients (such as note- book computers) that might move to different locations on your network from time to time. Dynamic IP is the integration of the Dynamic Host Configura- tion Protocol (DHCP), which provides configuration information to IP hosts, and the Dynamic Domain Name System (DDNS), which provides dynamic host name-to-IP address (and IP address-to-host name) mapping for the Dynamic IP clients. You can use the OS/2 Warp Server installation program to install the DHCP server and the DDNS server. OS/2 Warp Server TCP/IP services can be installed on the client workstation to add DHCP and DDNS support. 1.2 INSTALLATION _________________ 1.2.1 GENERAL INSTALLATION RECOMMENDATIONS The Warp Server CD consists of the latest base Warp with WIN-OS/2 operating system and 7 networking products (hereafter referred to as services or compo- nents). Warp Server is not designed to be installed remotely and unattended by a Software Distribution Manager (SDM), although most components contained within Warp Server are CID enabled and CID installations can be accomplished via an SDM such as NetView DM/2. Warp Server does, however, include the ability for you to perform remote ATTENDED installation for the networking products for Warp Server clients. Please review the following documentation before installing IBM OS/2 Warp Server. o README.1ST located on root directory of the CD o Easy Start __________ o Up and Running Book ___________________ o README files for each component included in Warp Server o YELLOW book - OS/2 System Software Distribution & Installation Using ______________________________________________________ NetView DM/2 (GG66-3253-1) ____________ o Automated Installation for CID Enabled OS/2 V2.x (GG24-3783) ________________________________________________ Page 6 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 o Automated Installation for CID Enabled Extended Services, LAN Server ____________________________________________________________________ V3.0, and Network Transport Services/2 (GG24-3781-01) ______________________________________ o IBM Multi-Protocol Transport Services Redirected Installation and Config- _________________________________________________________________________ uration Guide (S19H-1344) _____________ In summary, remote unattended installation via NetView DM/2 is a viable install option if the components contained within Warp Server were treated individually. The following sections are the steps the Eagle Integration Test team took to perform CID installs of each individual component of Warp Server. 1.2.2 MANUAL INSTALLATION You must create two installation diskettes if you do not have the diskettes that were supplied with the OS/2 Warp Server package. These two diskettes are used to boot your workstation so that the OS/2 base operating system can be installed as well as the networking parts of OS/2 Warp Server. Use the following procedure to create installation diskettes. ----------------------------------------------------------------------------- Insert OS/2 Warp Server CD-ROM 1 in the CD-ROM drive. At an OS/2 command prompt, type the following and press Enter: d:CDINST where d is your CD-ROM drive. When prompted to do so, insert a blank formatted 1.44MB 3.5-inch diskette in drive A, then press Enter. When the copy is finished, remove the diskette from drive A and label it "OS/2 DISKETTE 1 for CD-ROM". Insert another blank formatted 1.44 MB 3.5-inch diskette in drive A and press Enter. When the copy is finished, remove the diskette from drive A and label it "INSTALLATION DISKETTE for CD-ROM". ----------------------------------------------------------------------------- Use the diskette labelled "INSTALLATION DISKETTE for CD-ROM" to boot off your workstation, and follow the instructions online to start the installation of Warp Server. Basically, there are 2 installation paths: 1. Easy Installation Path o Easy Installation lets you quickly install OS/2 Warp to drive C, plus the services you choose from the following list: -- Page 7 of 90 (C) COPYRIGHT IBM CORP. 1996 - File and Print Sharing Services (IBM LAN Server) - Remote Access Services (IBM LAN Distance Connection Server) - System Management Services (IBM SystemView for OS/2) - Backup and Recovery Services (IBM Personally Safe and Sound) - Advanced Print Services (IBM Print Services Facility/2) - TCP/IP Services (TCP/IP in Warp Server) 2. Advanced Installation Path o Advanced Installation allows you to customize your installation, install any or all of the services listed above in the Easy Installa- tion path, plus make detailed configuration selections for each. NOTE: If you are installing OS/2 Warp Server on a partition that already has OS/2 Warp (without WIN-OS/2), for example a partition with OS/2 for Windows already installed, you must use the Advanced Installation Path and select to format the partition during the installation. Formatting the partition during the Advanced installation will remove the previous version of OS/2 and all data on the boot partition. Make sure you back up any data on the boot partition before beginning the OS/2 Warp Server installation process. You do not have to format the partition if you are installing OS/2 Warp Server over OS/2 2.0, OS/2 2.1, OS/2 2.11, or OS/2 Warp (with WIN-OS/2). 1.2.2.1 Prerequisite Software needed for installation of Warp Server client: Unless specific exceptions are noted, the following operating systems are supported on clients in non-DBCS countries: o OS/2 clients - OS/2 Warp (with WIN-OS/2, without WIN-OS/2) - OS/2 Warp Connect o DOS and Windows clients - MS DOS 6.0, PC DOS 6.1, MS DOS 6.2, PC DOS 6.3 and PC DOS 7.0 - Windows 3.1 - Windows for Workgroups versions 3.1 and 3.11 - Windows 95 NOTE: OS/2 clients MUST have at least OS/2 Warp with WIN-OS/2 operating ____ system installed before using this remote lightly attended installation to install clients across the LAN. The remote OS/2 Warp Server client installa- tion will let you upgrade a previous version of OS/2 Warp with WIN-OS/2 to the version included in OS/2 Warp Server. Page 8 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.2.2 Additional Notes for OS/2 Warp pristine manual installation Please refer to the Easy Start and/or the Up and Running book provided with __________ ______________ the IBM OS/2 Warp Server for additional detailed instructions on manual installation via CD ROM. The Eagle Integration Test team noted the following special considerations for manual installation: o If you get a red screen with "Error 3" after using the boot diskettes to reboot your system, you might need to manually format your hard drive and restart the installation of OS/2 Warp Server. -- Page 9 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.3 REMOTE CID INSTALLATION USING NETVIEW DM/2 1.2.3.1 Installation of the Images onto the CC Server The CID code images for all components/products included in Warp Server have already been created and are on the Warp Server CD. If you choose to copy all product CID images included in Warp Server, you will need approximately 250MB of additional space. The Eagle Integration Test team used the syntax below to copy all product images from the CD onto our code server: ----------------------------------------------------------------------------- XCOPY cdrom_drive:\CID\CLIENT\*.* target_path /e/s XCOPY cdrom_drive:\CID\SERVER\*.* target_path /e/s XCOPY cdrom_drive:\OS2IMAGE\*.* target_path /e/s XCOPY cdrom_drive:\CID\EXE\OS2\*.* target_path /e/s XCOPY cdrom_drive:\WARPSRV\*.* target_path /e/s where target_path = the target path & directory to copy the code images ----------------------------------------------------------------------------- 1.2.4 PRISTINE-REMOTE INSTALLATION PROCEDURES This section is divided into several sub-sections, one for each product/component included in Warp Server. Page 10 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.5 OS/2 WARP WITH WIN-OS/2, LAPS AND NETVIEW DM/2 CC CLIENT NOTE: The Eagle Integration Test team used OS/2 Warp with WIN-OS2, but you can also build the boot diskettes using OS/2 Warp level which came with Warp Server. It is necessary to create and boot the pristine (brand new) workstation from the pristine boot diskettes. This will allow the workstation to establish contact with the NetView DM/2 CC Server. The pristine boot diskettes contain a minimal OS/2 system, a minimal LAPS for LAN transport code which allows the connection to the Server, and a minimal NetView DM/2 agent to accept commands from the CC Server to install various products. In our test, we built the pristine diskettes with LAPS 2.0 at CSD WR08000 and NetView DM/2 2.1 at CSD XR20466. o To create the two OS/2 WARP pristine boot diskettes, the following steps should be executed from the NetView DM/2 2.1 CSD XR20466 CC Server. 1. Insert a formatted diskette into the disk drive. 2. Apply the minimal OS/2 onto the diskettes by executing SEDISK which is located in the OS/2 CID Utility directory. (See 1.2.3.1, "Instal- lation of the Images onto the CC Server" on page 10 for information on the location of the CID Utility directory.) SEDISK will apply the minimal OS/2 onto the first diskette and prompt you to insert the second diskette for completion. The following is the SEDISK syntax: os2_cid_utility_dir\SEDISK /S:os2_image_dir /T:target_dir where os2_cid_utility_dir = The drive and path of the OS/2 CID Utility directory on the NetView DM/2 CC Server os2_image_dir = The drive and path of the OS/2 images on the NetView DM/2 CC Server target_dir = The drive and path of target directory For example, the Eagle Integration Test team used: SEDISK /S:I:\IMG\STABLE\OS230FP /T:A: 3. Keeping the second diskette in the disk drive, apply the minimal LAPS onto the second diskette by executing the THINLAPS utility. THINLAPS can be executed from the LAPS image directory on the NetView DM/2 CC Server. The following command syntax should be used: -- Page 11 of 90 (C) COPYRIGHT IBM CORP. 1996 laps_image_directory\THINLAPS laps_image_directory target_directory nif_file where laps_image_directory = The drive and path of the LAPS images on the NetView DM/2 CC Server target_directory = The drive and path of the target directory nif_file = the .NIF file you will use For example, the Eagle Integration Test team used: THINLAPS I:\IMG\STABLE\LA8000WS A: IBMTOK.NIF 4. Keeping the second diskette in the disk drive, apply the minimal NetView DM/2 agent using the NVDMBDSK utility. Execute NVDMBDSK from the BIN subdirectory within the NetView DM/2 product directory. NVDMBDSK is a presentation manager utility so, a window will be opened for you to fill in the required parameters. You should specify your Target Environment as OS/2, (rather than DOS), and it is recommended you leave the ? for the Client Name and Server Name, and _ change the Receive Timeout value from 15000 to -1. The "?" in this ___ case means that the set of boot diskettes is suitable for use on ANY ___ CC Client for installations, instead of being built with fixed Server Name and Client name. o Boot the workstation from the two diskettes. If when building the OS/2 pristine boot diskettes, you left the ? for the Client Name and the _ Server Name, you will be prompted to fill in these parameters. o You now have established connectivity to the NetView DM/2 CC server. To install OS/2, you must install the following 3 change files together as a COREQ group in the exact order as they appear below: 1. OS/2 pristine install profile - (OS230WB.PRO) - Using program SEINST with PARM=/B:bootdrive /T:A:\ - Response file with FormatPartition=1 (Yes) 2. LAPS pristine install profile - (LA8200WB.PRO) - Using program LAPS with PARM=/E:MAINT 3. NetView DM/2 pristine install profile - (NDM2466B.PRO) - Using program NVDMCLT - With PhaseEnd=Yes o After the successful completion, the workstation will be running with OS/2, LAPS and NetView DM/2 Client code. o Sample response files are located as follows: Page 12 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 - OS/2 WARP - "SAMPLE.RSP" is in the \OS2IMAGE directory on the Warp Server CD. - LAPS - "MPTS.RSP" sample response file is provided in the \CID\CLIENT\SYSVIEW2\CLIENT_2 directory on the Warp Server CD. - NetView DM/2 2.1 did not ship any sample response files, but the only required parameters are "CLIENTNAME=" and "SERVERNAME=" for a client. See Figure 6 on page 20 for the sample NetView DM/2 response file the Eagle Integration Test team used. o See section 1.2.5.1, "Sample OS/2 pristine install PROFILES" for the pro- files and 1.2.5.2, "Sample OS/2 pristine RESPONSE FILES" on page 15 for the response files used for pristine installation of OS/2. 1.2.5.1 Sample OS/2 pristine install PROFILES Below are the corresponding profiles presented in the same order that they must be installed as a COREQ group: o OS/2 WARP o LAPS o NetView DM/2 Client ----------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=IBM.OS2.BOOT.REF.30.FP.US.WARPSERVER Description="Warp Server Base OS/2 FullPak" End Section Install Begin Program = SA:\IMG\STABLE\OS230WS\SEINST.EXE Parms = /B:C: /T:A:\ /R:$(ResponseFile) /S:$(SourceDir) /L1:$(LogFile1) ResponseFile = SA:\RSP\OS230WS\$(WorkStatName).RSP SourceDir = SA:\IMG\STABLE\OS230WS LogFile1 = SB:\LOG\OS230WS\$(WorkStatName).LOG End ----------------------------------------------------------------------------- Figure 1. Sample OS/2 Pristine Install Profile (OS230WB.PRO) -- Page 13 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=IBM.LAPS.BOOT.REF.5.WR08200.US.WARPSERVER Description="LAPS MAINT Install" End Section Install Begin Program = SA:\IMG\STABLE\LA8200WS\MPTS.EXE Parms = /E:MAINT /R:$(ResponseFile) /T:$(TargetDir) /TU:C:\ /S:$(SourceDir) /L1:$(LogFile1) SourceDir = SA:IMG\STABLE\LA8200WS ResponseFile = SA:\RSP\LA8200WS\$(WorkStatName).RSP LogFile1 = SB:\LOG\LA8200WS\$(WorkStatName).LOG End ----------------------------------------------------------------------------- Figure 2. Sample LAPS Pristine Install Profile (LA8200WB.PRO) ----------------------------------------------------------------------------- TargetDir = C:\IBMNVDM2 Section Catalog Begin ObjectType=Software GlobalName=IBM.NVDM2.BOOT.REF.21.XR20466.US Description="NVDM/2 2.1 client install for boot environment" End Section Install Begin Program = SA:\IMG\STABLE\NVDM2466\NVDMCLT.EXE Parms = /B:C /R:$(ResponseFile) /T:$(TargetDir) /S:$(SourceDir) /L:$(LogFile1) SourceDir = SA:\IMG\STABLE\NVDM2466 ResponseFile = SB:\RSP\NVDM2466\$(WorkStatName).RSP LogFile1 = SB:\LOG\NVDM2466\$(WorkStatName).LOG PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 3. Sample NetView DM/2 Pristine Install Profile (NDM2466B.PRO) Page 14 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.5.2 Sample OS/2 pristine RESPONSE FILES The following response files were used for the remote installation of: o OS/2 WARP o LAPS o NetView DM/2 Client The comments were edited out of the OS/2 WARP response file for clarity. A copy of the actual response file used is in the PKZIP2 file (See 1.2.24, "PKZIP2 Samples" on page 87 for the location of the response file). This response file was used for formatting the C drive as HPFS during the install. The following response file keywords are noted: +-------------------------------------+-------------------------------------+ | RESPONSE FILE KEYWORD | REASON | +-------------------------------------+-------------------------------------+ | BaseFileSystem=1 | indicates HPFS format (DEFAULT) | +-------------------------------------+-------------------------------------+ | CDROM=1 | indicates AUTODETECT instead of the | | | default (0) | +-------------------------------------+-------------------------------------+ | ExitOnError=1 | indicates exit with a return code | | | instead of default (0) | +-------------------------------------+-------------------------------------+ | FormatPartition=1 | indicates format the partition | | | instead of default (0) | +-------------------------------------+-------------------------------------+ | MultimediaSupport=0 | indicates no multimedia support | | | instead of the default (1). | +-------------------------------------+-------------------------------------+ -- Page 15 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- AdditionalPrinters=2:228,3:344 BaseFileSystem=1 CDROM=1 CountryCode=001 CountryKeyboard=US DefaultPrinter=186 DiagnosticAids=1 DisplayAdapter=0 Documentation=1 DOSSupport=1 WIN-OS/2Support=1 DPMI=1 ExitOnError=1 Fonts=1 FormatPartition=1 MigrateConfigFiles=1 MoreBitmaps=1 Mouse=1 MousePort=0 OptionalFileSystem=1 OptionalSystemUtilities=1 OS2IniData=/AppName/KeyName/KeyValue/ PCMCIA=0 PCMCIAOptions=0 PrimaryCodePage=1 PrinterPort=1 ProcessEnvironment=1 ProgressIndication=1 RebootRequired=0 SCSI=1 SerialDeviceSupport=1 TargetDrive=C: ToolsAndGames=1 MultimediaSupport=0 *UserExit=MyProg Copy=F:\IBMRAID.ADD C:\ SeedConfigSysLine=BASEDEV=IBMRAID.ADD ----------------------------------------------------------------------------- Figure 4. Sample OS/2 WARP Pristine Install response file (CIDA124.RSP) Page 16 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- INST_SECTION = ( UPGRADE_LEVEL = SAME INSTALL = PRODUCT ) PROTOCOL = ( [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] IBMMPC_nif = IBMMPC.nif LANDD_nif = LANDD.NIF NETBEUI_nif = NETBEUI.NIF TCPIP_nif = TCPIP.nif [LANDD_nif] DriverName = LANDD$ Bindings = IBMMPC_nif NETADDRESS = "T40000C1DA124" ETHERAND_TYPE = "I" SYSTEM_KEY = 0x0 OPEN_OPTIONS = 0x2000 TRACE = 0x0 LINKS = 125 MAX_SAPS = 5 MAX_G_SAPS = 0 USERS = 5 TI_TICK_G1 = 255 T1_TICK_G1 = 15 T2_TICK_G1 = 3 TI_TICK_G2 = 255 T1_TICK_G2 = 25 T2_TICK_G2 = 10 IPACKETS = 200 UIPACKETS = 100 MAXTRANSMITS = 6 MINTRANSMITS = 2 TCBS = 64 GDTS = 30 ELEMENTS = 800 ----------------------------------------------------------------------------- Figure 5 (Part 1 of 3). Sample LAPS response file configured for Token Ring (CIDA124.RSP) -- Page 17 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- [NETBEUI_nif] DriverName = netbeui$ Bindings = IBMMPC_nif ETHERAND_TYPE = "I" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 240 NCBS = 240 NAMES = 75 SELECTORS = 30 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 30000 T1 = 500 T2 = 200 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 1000 NETBIOSRETRIES = 12 NAMECACHE = 0 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 2 PACKETS = 250 LOOPPACKETS = 1 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 5 [IBMMPC_nif] DriverName = IBMMPC$ MaxTransmits = 31 MaxTxFrameSize = 18000 MinRcvBuffs = 20 SizWorkBuf = 2048 MulticastNum = 16 EnableTxEofInt = "YES" Enet20UTP = "NO" EnableHiPriTx = "NO" HiPriTxAccess = 5 HiPriTxThresh = 4 LLCOnly = "NO" [TCPIP_nif] DriverName = TCPIP$ Bindings = IBMMPC_nif Page 18 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ) ----------------------------------------------------------------------------- Figure 5 (Part 2 of 3). Sample LAPS response file configured for Token Ring (CIDA124.RSP) ----------------------------------------------------------------------------- MPTS = ( [CONTROL] Local_IPC = YES INET_Access = YES NETBIOS_Access = NO [IFCONFIG] Interface = 0 Address = 9.67.142.124 Brdcast = Dest = Enable = UP Netmask = 255.255.255.0 Metric = 0 Mtu = 1500 Trailers = NO Arp = NO Bridge = NO Snap = NO Allrs = NO 802.3 = NO Icmpred = NO Canonical = NO [ROUTE] Type = default Action = add Dest = Router = 9.67.142.250 Metric = 1 ) RESOLV = ( NAME = domain raleigh.ibm.com NAME = nameserver 9.67.128.3 ) ----------------------------------------------------------------------------- Figure 5 (Part 3 of 3). Sample LAPS response file configured for Token Ring (CIDA124.RSP) -- Page 19 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- SERVERNAME=CIDA050 CLIENTNAME=CIDA124 ATTACHTIMEOUT=-1 RECEIVETIMEOUT=-1 ----------------------------------------------------------------------------- Figure 6. Sample NetView DM/2 Client response file (CIDA124.RSP) Page 20 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.5.3 Additional MPTS/LAPS Sample Response File The following LAPS sample response files were used for different types of adapter card: -- Page 21 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- INST_SECTION = ( UPGRADE_LEVEL = SAME INSTALL = PRODUCT ) PROTOCOL = ( [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] landd_nif = landd.nif netbeui_nif = netbeui.nif tcpip_nif = tcpip.nif SMCOS2P_nif = SMCOS2P.nif ibmtok_nif = ibmtok.nif [NETBIOS] DriverName = netbios$ ADAPTER0 = netbeui$,0 ADAPTER1 = netbeui$,1 [landd_nif] DriverName = LANDD$ Bindings = ibmtok_nif,SMCOS2P_nif NETADDRESS = "T40000C1DA112","T40000C1DE112" ETHERAND_TYPE = "I","D" SYSTEM_KEY = 0x0,0x0 OPEN_OPTIONS = 0x2000,0x2000 TRACE = 0x0,0x0 LINKS = 8,8 MAX_SAPS = 3,3 MAX_G_SAPS = 0,0 USERS = 3,3 TI_TICK_G1 = 255,255 T1_TICK_G1 = 15,15 T2_TICK_G1 = 3,3 TI_TICK_G2 = 255,255 T1_TICK_G2 = 25,25 T2_TICK_G2 = 10,10 IPACKETS = 250,250 UIPACKETS = 100,100 MAXTRANSMITS = 6,6 MINTRANSMITS = 2,2 TCBS = 64,64 GDTS = 30,30 ELEMENTS = 800,800 Page 22 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- Figure 7 (Part 1 of 3). Sample LAPS response file (Ethernet & Token Ring) (CIDA112.RSP) -- Page 23 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- [netbeui_nif] DriverName = netbeui$ Bindings = ibmtok_nif,SMCOS2P_nif ETHERAND_TYPE = "I" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 240 NCBS = 225 NAMES = 75 SELECTORS = 30 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 30000 T1 = 1000 T2 = 200 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 2000 NETBIOSRETRIES = 3 NAMECACHE = 1000 RNDOPTION = 1 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 10 PACKETS = 150 LOOPPACKETS = 8 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 10 FCPRIORITY = 5 NETFLAGS = 0x0 [tcpip_nif] DriverName = TCPIP$ Bindings = SMCOS2P_nif [SMCOS2P_nif] DriverName = DC21040$ [ibmtok_nif] DriverName = IBMTOK$ MAXTRANSMITS = 6 RECVBUFS = 2 RECVBUFSIZE = 256 XMITBUFS = 1 Page 24 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ) ----------------------------------------------------------------------------- Figure 7 (Part 2 of 3). Sample LAPS response file (Ethernet & Token Ring) (CIDA112.RSP) ----------------------------------------------------------------------------- MPTS = ( [CONTROL] Local_IPC = YES INET_Access = YES NETBIOS_Access = NO [IFCONFIG] Interface = 0 Address = 9.67.141.240 Brdcast = Dest = Enable = UP Netmask = 255.255.255.128 Metric = 0 Mtu = 1500 Trailers = NO Arp = NO Bridge = NO Snap = NO Allrs = NO 802.3 = NO Icmpred = NO Canonical = NO [ROUTE] Type = default Action = add Dest = Router = 9.67.141.250 Metric = 1 ) RESOLV = ( NAME = domain raleigh.ibm.com NAME = nameserver 9.67.128.3 NAME = nameserver 9.67.1.5 ) ----------------------------------------------------------------------------- Figure 7 (Part 3 of 3). Sample LAPS response file (Ethernet & Token Ring) (CIDA112.RSP) -- Page 25 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- INST_SECTION = ( UPGRADE_LEVEL = SAME INSTALL = PRODUCT ) PROTOCOL = ( [PROT_MAN] DriverName = PROTMAN$ [IBMLXCFG] landd_nif = landd.nif netbeui_nif = netbeui.nif tcpip_nif = tcpip.nif PRO1670O_nif = PRO1670O.nif [NETBIOS] DriverName = netbios$ ADAPTER0 = netbeui$,0 [landd_nif] DriverName = LANDD$ Bindings = PRO1670O_nif NETADDRESS = "T40000C1DE016" ETHERAND_TYPE = "D" SYSTEM_KEY = 0x0 OPEN_OPTIONS = 0x2000 TRACE = 0x0 LINKS = 100 MAX_SAPS = 3 MAX_G_SAPS = 0 USERS = 3 TI_TICK_G1 = 255 T1_TICK_G1 = 15 T2_TICK_G1 = 3 TI_TICK_G2 = 255 T1_TICK_G2 = 25 T2_TICK_G2 = 10 IPACKETS = 250 UIPACKETS = 100 MAXTRANSMITS = 6 MINTRANSMITS = 2 TCBS = 64 GDTS = 30 ELEMENTS = 800 [netbeui_nif] Page 26 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 DriverName = netbeui$ Bindings = PRO1670O_nif ETHERAND_TYPE = "D" USEADDRREV = "YES" OS2TRACEMASK = 0x0 SESSIONS = 240 NCBS = 240 NAMES = 75 SELECTORS = 30 USEMAXDATAGRAM = "NO" ADAPTRATE = 1000 WINDOWERRORS = 0 MAXDATARCV = 4168 TI = 30000 T1 = 1000 T2 = 200 MAXIN = 1 MAXOUT = 1 NETBIOSTIMEOUT = 2000 NETBIOSRETRIES = 3 NAMECACHE = 1000 RNDOPTION = 1 PIGGYBACKACKS = 1 DATAGRAMPACKETS = 10 PACKETS = 150 LOOPPACKETS = 8 PIPELINE = 5 MAXTRANSMITS = 6 MINTRANSMITS = 2 DLCRETRIES = 10 FCPRIORITY = 5 NETFLAGS = 0x0 [tcpip_nif] DriverName = TCPIP$ Bindings = PRO1670O_nif ----------------------------------------------------------------------------- Figure 8 (Part 1 of 2). Sample LAPS response file configured for Ethernet (CIDA016.RSP) -- Page 27 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- [PRO1670O_nif] DriverName = ETHPCI$ ) MPTS = ( [CONTROL] Local_IPC = YES INET_Access = YES NETBIOS_Access = NO [IFCONFIG] Interface = 0 Address = 9.67.142.16 Brdcast = Dest = Enable = UP Netmask = 255.255.255.0 Metric = 0 Mtu = 1500 Trailers = NO Arp = NO Bridge = NO Snap = NO Allrs = NO 802.3 = NO Icmpred = NO Canonical = NO [ROUTE] Type = default Action = add Dest = Router = 9.67.142.250 Metric = 1 ) RESOLV = ( NAME = domain raleigh.ibm.com NAME = nameserver 9.67.128.3 NAME = nameserver 9.67.1.5 ) ----------------------------------------------------------------------------- Figure 8 (Part 2 of 2). Sample LAPS response file configured for Ethernet (CIDA016.RSP) Page 28 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.6 REMOTE INSTALLATION OF MPTS/LAPS USING SYSTEMVIEW NOTE: SystemView does not support Pristine Installation at this time. Therefore, in this example, it is assumed LAPS is already installed on the target machine and you wish to upgrade to a new level. If you are not familiar with SystemView Software Distribution, then please refer to the SystemView Up and Running! book. You can view this book online __________________________ from the Warp Server CD. Change to the directory \CID\SERVER\BOOKS on the Warp Server CD Drive and enter the command "view ikoo0mst.inf". Now you will see the contents of the book. Expand the entry "Getting Started With SystemView" by clicking on the + sign next to the entry. Now expand the sub- topic "Getting Started with CID". Review this section for information on: o CID Software Distribution Environment. o Setting up a Code Server. o CID Software Preparation process and the use of Application Definition Files (ADF) for creating profiles and response files. For more detail on ADF files please see the SystemView Up and Running! book in the section __________________________ entitled "Application Definition File Considerations". o How to catalog and distribute software objects via SystemView. 1.2.6.1 MPTS ADF File and sample profiles and response files. The ADF file for MPTS is located on the WARP Server CD in \CID\SERVER\ADFRSP\MPTS.ADF. The Eagle Integration Test team used the ADF file as input to SystemView's CID SOFTWARE PREPARATION process to create a profile and response file. See Figure 9 on page 30 for the sample profile generated by SystemView. 1.2.6.1.1 SAMPLE PROFILE NOTE: The PARAMETERS section of the following profile has been edited to fit this document. Please refer to the actual sample profile included in the PKZIP2 file called ELITE042.ZIP that is shipped with this document. -- Page 29 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- GLOBAL NAME: IBM.MPTS50.MPTSWS.REF.050000.US_EN DESCRIPTION: WARP SERVER MPTS CHANGE FILE TYPE: OS2CID PREREQ COMMAND: cidmount IBMLS $(FREEDRIVE1) $(FREEDRIVE2) CIDA035S DDISK35 DDISK35 POSTREQ COMMAND: cidunmnt IBMLS $(FREEDRIVE1) $(FREEDRIVE2) INSTALL PROGRAM: PROGRAM NAME: $(FREEDRIVE1)\IMG\MPTSWS\MPTS.EXE PARAMETERS: /S:$(FREEDRIVE1)\IMG\MPTSWS /R:$(FREEDRIVE1)\RSP\MPTSWS\$(SYSTEMNAME).RSP /TU:$(BOOTDRIVE) /L1:$(FREEDRIVE2)\LOG\MPTSWS\$(SYSTEMNAME).L1 /L2:$(FREEDRIVE2)\LOG\MPTSWS\$(SYSTEMNAME).L2 /E:PROD ----------------------------------------------------------------------------- Figure 9. Sample MPTS profile generated by SystemView (MPTSWS.PRO) 1.2.6.1.2 SAMPLE RESPONSE FILE The Eagle Integration Test team tested the default MPTS response file created via the CID SOFTWARE PREPARATION process. The response file can be further tailored to work in your environment via the SOFTWARE CONFIGURATION utility (refer to the SystemView Up and Running! book in the section entitled __________________________ "Getting Started with CID") or, if you wish, you can use the same response file used for distributions from NetView DM/2 . Please refer to Figure 5 on page 17 for a sample response file that can be used for distributions from both NetView DM/2 and SystemView. Page 30 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.7 LAN SERVER VERSION 5.0 The scenarios described below use NetView DM/2 to install LAN Services (LS) Server and Requester functions. Procedures for installation of LAN Support Program (LSP) and DOS LAN Requester (DLR) are not covered. If you prefer to use SystemView to install LAN Server, please refer to section 1.2.8, "Remote Installation of LAN Server Advanced using SystemView" on page 41. The profile in Figure 10 on page 32 and response file in Figure 11 on page 34 were used to install the LS 5.0 Server code. Please note that the parameter /SRV is contained in the profile for Server installation. This is required to indicate that the Server function is to be installed. Requester code is installed automatically whenever Server code is installed. NOTE: The sample response file included here was used to install LAN Server with the role of an ADDITIONAL SERVER. _________________ NOTE: LANINSTR.EXE has the following syntax: ----------------------------------------------------------------------------- LANINSTR /SRV /R:resp_file /T:target /L1:logfile /SRV = denotes that this is a Server install /REQ = denotes that this is a Requester install resp_file = fully-qualified path & name of the response file target = (optional) target drive to install product. - can be overridden by response file - if not specified here or in response file, current boot drive is used logfile = where installation messages are to be written ----------------------------------------------------------------------------- -- Page 31 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.7.1 Sample LAN Server 5.0 Installation Profile ----------------------------------------------------------------------------- TargetDir=C:\ Section Catalog Begin ObjectType=Software Globalname=IBM.LS.REF.50.US.WARPSERVER.SRV Description="Warp Server LS server 5.0" End Section Install Begin Program=SA:\IMG\STABLE\LS50WS\LANINSTR.EXE Parms=/SRV /L1:$(LogFile1) /R:$(ResponseFile) ResponseFile= $(SA)\rsp\LS50WS\$(WorkStatName).rsp LogFile1= $(SB)\log\LS50WS\$(WorkStatName).l1 PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 10. Sample WARP LAN Server Profile (LSS50WS.PRO) Page 32 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.7.2 Sample LAN Server 5.0 Response File -- Page 33 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- DELETEIBMLAN = Networks< net2 = net3 = net4 = netlb = > UPDATEIBMLAN = Networks< net1 = NETBEUI$,*,LM10,*,75,* > UPDATEIBMLAN = Remoteboot< rpldir = Migrate rpluserdir = Migrate > DELETEIBMLAN = Requester< wrknets = NETLB,NET2,NET3,NET4 > UPDATEIBMLAN = Requester< Computername = CIDA124S Domain = q4it002 sesstimeout = 300 useallmem = Yes wrkheuristics = ***********000 > ADDIBMLAN = Requester< wrknets = NET1 > DELETEIBMLAN = Server< srvservices = DCDBREPL srvnets = NETLB,NET2,NET3,NET4 > UPDATEIBMLAN = Server< Page 34 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 autopath = Migrate srvheuristics = ***************2***** > ADDIBMLAN = Server< srvservices = LSSERVER srvnets = NET1 > ----------------------------------------------------------------------------- Figure 11 (Part 1 of 2). Sample LS 5.0 Server response file (CIDA124.RSP) -- Page 35 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- Config386Cache = 1024 ConfigApplDumpPath = Migrate ConfigApplMaxDumps = Migrate ConfigAutoStartFFST = Migrate ConfigAutoStartLS = Yes ConfigCopyDLR = CopyIfRequired ConfigCopyDOS = CopyIfRequired ConfigCopyLSP = CopyIfRequired ConfigCopyOS2Requester = CopyIfRequired ConfigDisplayMSG = Migrate ConfigDosVersion = Migrate ConfigDosNumber = 0 ConfigHeap = WSDetermineSize ConfigLazyWrite = Immediate ConfigMsgLogName = Migrate ConfigRouteAlertsTo = Migrate ConfigServerType = AdditionalServer ConfigSourceDrive = None ConfigSystemDumpPath = Migrate ConfigSystemMaxDumps = Migrate ConfigTargetDrive = C ConfigUpsPort = Migrate ConfigUseAllMem = Yes ConfigWsId = Migrate ConfigWsSerial1 = Migrate ConfigWsSerial2 = Migrate ConfigWsType1 = Migrate ConfigWStype2 = Migrate Install386HPFS = INSTALLIFREQUIRED InstallAPI = INSTALLIFREQUIRED InstallDosLanApi = INSTALLIFREQUIRED InstallDosRemoteIPL = INSTALLIFREQUIRED InstallFaultTolerance = INSTALLIFREQUIRED InstallFFST = INSTALLIFREQUIRED InstallGenericAlerter = INSTALLIFREQUIRED InstallInstallProgram = INSTALLIFREQUIRED InstallLocalSecurity = INSTALLIFREQUIRED InstallLoopBackDriver = INSTALLIFREQUIRED InstallOS2RemoteIPL = INSTALLIFREQUIRED InstallServer = INSTALLIFREQUIRED InstallUPM = INSTALLIFREQUIRED InstallUps = INSTALLIFREQUIRED InstallMSGPopup = INSTALLIFREQUIRED InstallGUI = INSTALLIFREQUIRED InstallClipBoard = INSTALLIFREQUIRED InstallDesktopIcons = YES ----------------------------------------------------------------------------- Figure 11 (Part 2 of 2). Sample LS 5.0 Server response file (CIDA124.RSP) Page 36 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.7.3 LAN Requester 5.0 Installation IBM LAN Requester 5.0 cannot be installed over IBM Peer for OS/2 from Warp Connect. IBM Peer for OS/2 must be removed before installing this version of LAN Requester. The profile in Figure 12 on page 38 and response file in Figure 13 on page 40 were used to install the LS 5.0 Requester code. -- Page 37 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.7.4 Sample LAN Requester 5.0 installation profile ----------------------------------------------------------------------------- TargetDir=C:\ Section Catalog Begin ObjectType=Software Globalname=IBM.LS.REF.50.US.WARPSERVER.REQ Description="Warp Server LS Requester 5.0" End Section Install Begin Program=SA:\IMG\STABLE\LS50WS\LANINSTR.EXE Parms=/REQ /L1:$(LogFile1) /R:$(ResponseFile) ResponseFile= $(SA)\rsp\LS50WS\$(WorkStatName).rsp LogFile1= $(SB)\log\LS50WS\$(WorkStatName).l1 PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 12. Sample LAN Requester Profile (LSR50WS.PRO) Page 38 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.7.5 Sample LAN Requester 5.0 Response File -- Page 39 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- DELETEIBMLAN = Networks< netlb = > UPDATEIBMLAN = Networks< net1 = NETBEUI$,*,LM10,*,75,* > UPDATEIBMLAN = Peer< security = SHARE > UPDATEIBMLAN = Requester< Domain = q4it002 Computername = CIDA078 useallmem = Yes > ADDIBMLAN = Requester< wrkservices = PEER > ConfigApplDumpPath = Migrate ConfigApplMaxDumps = Migrate ConfigAutoStartFFST = Migrate ConfigAutoStartLS = Migrate ConfigDisplayMSG = Migrate ConfigMsgLogName = Migrate ConfigRouteAlertsTo = Migrate ConfigSourceDrive = C ConfigSystemDumpPath = Migrate ConfigSystemMaxDumps = Migrate ConfigTargetDrive = C ConfigWsId = CIDA078 ConfigWsSerial1 = Migrate ConfigWsSerial2 = Migrate ConfigWsType1 = Migrate ConfigWStype2 = Migrate InstallAPI = INSTALLIFREQUIRED InstallDosLanApi = INSTALLIFREQUIRED InstallFFST = INSTALLIFREQUIRED InstallInstallProgram = INSTALLIFREQUIRED InstallPeerService = INSTALL InstallRemoteFaultTolerance = INSTALLIFREQUIRED InstallRequester = INSTALLIFREQUIRED InstallUPM = INSTALLIFREQUIRED InstallMSGPopup = INSTALLIFREQUIRED InstallGUI = INSTALLIFREQUIRED InstallClipBoard = INSTALLIFREQUIRED InstallDesktopIcons = YES ----------------------------------------------------------------------------- Figure 13. Sample LS 5.0 requester response file (CIDA078.RSP) Page 40 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.7.6 Additional Notes for LAN Server/Requester Installation o Sample response files are found on the Warp Server CD under - \CID\SERVER\SYSVIEW2\SERVER_2\NVDM_CLI\LS40SRV.RSP - \CID\SERVER\SYSVIEW2\SERVER_2\NVDM_CLI\LS40REQ.RSP 1.2.8 REMOTE INSTALLATION OF LAN SERVER ADVANCED USING SYSTEMVIEW If you are not familiar with SystemView Software Distribution, then please refer to the SystemView Up and Running! book. You can view this book online __________________________ from the Warp Server CD. Change to the directory \CID\SERVER\BOOKS on the Warp Server CD Drive and enter the command "view ikoo0mst.inf". Now you will see the contents of the book. Expand the entry "Getting Started With SystemView" by clicking on the + sign next to the entry. Now expand the sub- topic "Getting Started with CID". Review this section for information on: o CID Software Distribution Environment. o Setting up a Code Server. o CID Software Preparation process and the use of Application Definition Files (ADF) for creating profiles and response files. For more detail on ADF files please see the SystemView Up and Running! book in the section __________________________ entitled "Application Definition File Considerations". o How to catalog and distribute software objects via SystemView. 1.2.8.1 LAN Server Advanced ADF File and sample profiles and response files. The ADF file for LAN Server Advanced is located on the WARP Server CD in \CID\SERVER\ADFRSP\LANSRVA.ADF. The Eagle Integration Test team used the ADF file as input to SystemView's CID SOFTWARE PREPARATION process to create a profile and response file. See Figure 14 on page 42 for the sample profile generated by SystemView. 1.2.8.1.1 SAMPLE PROFILE NOTE: The PARAMETERS section of the following profile has been edited to fit this document. Please refer to the actual sample profile included in the PKZIP2 file called ELITE042.ZIP that is shipped with this document. -- Page 41 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- GLOBAL NAME: IBM.LANServerAdv50.LS50WS.REF.050000.US_EN DESCRIPTION: WARP SERVER LAN SRV ADV CHANGE FILE TYPE: OS2CID PREREQ COMMAND: cidmount IBMLS $(FREEDRIVE1) $(FREEDRIVE2) CIDA035S DDISK35 DDISK35 POSTREQ COMMAND: cidunmnt IBMLS $(FREEDRIVE1) $(FREEDRIVE2) INSTALL PROGRAM: PROGRAM NAME: $(FREEDRIVE1)\IMG\LS50WS\LANINSTR.EXE PARAMETERS: /SRV /R:$(FREEDRIVE1)\RSP\LS50WS\$(SYSTEMNAME).RSP /L1:$(FREEDRIVE2)\LOG\LS50WS\$(SYSTEMNAME).L1 /L2:$(FREEDRIVE2)\LOG\LS50WS\$(SYSTEMNAME).L2 ----------------------------------------------------------------------------- Figure 14. Sample LAN Server Advanced profile generated by SystemView (LS50WS.PRO) 1.2.8.1.2 SAMPLE RESPONSE FILE The Eagle Integration Test team tested the default LAN Server Advanced response file created via the CID SOFTWARE PREPARATION process. The response file can be further tailored to work in your environment via the SOFTWARE CONFIGURATION utility (refer to the SystemView Up and Running! book in the __________________________ section entitled "Getting Started with CID") or, if you wish, you can use the same response file used for distributions from NetView DM/2 . Please refer to Figure 11 on page 34 for a sample response file that can be used for dis- tributions from both NetView DM/2 and SystemView. Page 42 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.9 SYSTEMVIEW FOR OS/2 VERSION 1.01 Please review the following documentation before installing SystemView for OS/2. o README.1ST file located on the Warp Server CD. o Warp Server Up and Running Book (Systems Management section) ______________ 1.2.9.1 Prerequisite Software needed for Support of SystemView Manager SystemView Manager is supported for OS/2 Warp 3.0 SystemView Manager running on OS/2 Warp Server requires at least one the fol- lowing protocols: o TCP/IP - IBM TCP/IP for OS/2 2.0 with CSD UN64092 or later o NetBIOS - MPTS 1.0 (LAPS WR08000) or later o IPX/SPX - Novell NetWare Requester 2.10 or later If you choose to export data such as hardware and software inventory informa- tion to a database, you must have one of the following: o DB2/2 CAE Version 1.2 with Service Pack WR07037 or later o Lotus Notes Release 3.2 or later 1.2.9.2 Prerequisite Software needed for Support of SystemView Client SystemView Client is supported for o OS/2 2.11 o OS/2 Warp 3.0 o IBM DOS 6.3 and Microsoft Windows 3.1, 3.11 and Windows for Workgroups 3.11 o IBM DOS 7.0 and Microsoft Windows 3.1, 3.11 and Windows for Workgroups 3.11 o MS DOS 6.2 and Microsoft Windows 3.1, 3.11 and Windows for Workgroups 3.11 SystemView Client running on OS/2 requires at least one the following proto- cols: o TCP/IP - IBM TCP/IP for OS/2 2.0 with CSD UN64092 or later o NetBIOS - MPTS 1.0 (LAPS WR08000) or later o IPX/SPX - Novell NetWare Requester 2.10 or later -- Page 43 of 90 (C) COPYRIGHT IBM CORP. 1996 SystemView Client running on Windows requires at least one the following pro- tocols: o TCP/IP - IBM TCP/IP for OS/2 2.1.1 o NetBIOS - LAN Support Program (LSP) 1.35 or later o IPX/SPX - Novell NetWare Client for DOS and MS-Windows 1.21 1.2.10 MANUAL INSTALLATION OF SYSTEMVIEW FOR OS/2 VERSION 1.01 Please refer to the SystemView Up and Running! book provided on the Warp __________________________ Server CD. Go to the directory CID\SERVER\BOOKS and enter the command "view ikoo0mst.inf" for detailed instructions on manual installation. The Eagle Integration Test team noted the following special considerations for manual installation: o During the install, the "SystemView Configuration" window will appear providing an option to select what communication protocols to use. After selecting the protocol you MUST click on the box entitled "Enable driver". If you select the protocol and do not click on "Enable driver", then SystemView is not configured for that protocol. o If you select the protocol, NETBIOS, you must specify either the 12 char- acter Network Address or COMPUTERNAME as defined in the workstation's IBMLAN.INI file. The default entry that appears is the COMPUTERNAME of the workstation. Later on when you are configuring the SystemView Client workstation for software distribution, the COMPUTERNAME specified here must match what is defined in the DISTRIBUTION tab of the client's "SystemView Configuration" window. 1.2.11 REMOTE CID INSTALLATION USING NETVIEW DM/2 1.2.11.1.1 SYSTEMVIEW MANAGER o The installation command is SVINST.EXE and is located in the 'CID\SERVER\SYSVIEW2\SERVER_2' directory on the Warp Server CD. NOTE: A copy of the SVINST command, INSTALL.EXE, can also be used as the install program. Both SVINST.EXE and INSTALL.EXE are identical. o Response files are required and samples are provided with the product. The sample response file for the SystemView Manager is called SERVER.RSP and is located on the CD in directory CID\SERVER\SYSVIEW2\SERVER_2. o Following is the syntax: Page 44 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- path\SVINST /A: /L1: /L2: /O: /P: /R: /S: /T: /TU: /X action = D (delete), I (install), U (update) error log = specifies the drive, path, and file name of the installation error log history log = specifies the drive, path, and file name of the installation history file origin system = the value for this is DRIVE product name = provides the name of the product. The value must be Systemview Server Installation or SystemView Client Installation enclosed in double quotes. response file = specifies the drive, path, and file name of the response file you are using. source location = specifies the drive and path containing the source files to install target = specifies the drive and path where SystemView is to be installed update CONFIG.SYS = specifies the drive of the CONFIG.SYS to be updated by the SVINST program. /X = indicates unattended install ----------------------------------------------------------------------------- 1.2.11.2 Sample SystemView Manager Profile -- Page 45 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = C:\SYSVIEW2 Section Catalog Begin ObjectType=Software GlobalName=IBM.SYSVIEW2.REF.10.US.SERVER.WS Description="SYSTEMVIEW 1.0 Server" End Section Install Begin Program = SA:\IMG\STABLE\SV10SWS\SVINST.EXE Parms = /X /A:I /L1:$(LogFile1) /L2:$(LogFile2) /O:DRIVE /R:$(ResponseFile SourceDir = SA:\IMG\STABLE\SV10SWS ResponseFile = SA:\RSP\SV10SWS\$(WorkStatName).RSP LogFile1 = SB:\LOG\SV10SWS\$(WorkStatName).LOG LogFile2 = SB:\LOG\SV10SWS\$(WorkStatName).HST PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 15. Sample Profile (SV10SWS.PRO) Page 46 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.11.3 Sample SystemView Manager Response File -- Page 47 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- FILE = C:\SYSVIEW2 WORK = C:\SYSVIEW2 AUX1 = C: COMP = License Use Runtime - Server COMP = Software Distribution Object Preparation COMP = SystemView Administrator Console COMP = SystemView Documentation IPF format (.INF) COMP = SystemView Documentation Bookmanager format COMP = Software Distribution Server DELETEBACKUP = No SAVEBACKUP = Yes CFGUPDATE = Auto OVERWRITE = No SystemName=CIDA124 Driver.TCPIP = 1 Driver.NETBIOS = 1 Driver.SERIPC = 0 Driver.IPX = 0 Parm1.NETBIOS = CIDA124 Parm1.SERIPC = Keyword.1 = test NetTimeout = 15 Repository = C:\SYSVIEW2\REPOS WorkArea = C:\SYSVIEW2\WORK BackupArea = C:\SYSVIEW2\BACKUP ServiceArea = C:\SYSVIEW2\SERVICE RWC.CanTerminate = 1 RWC.StartMonitor = 1 RWC.TimeRefresh =100 SHA.Enabled=0 ;SHA.NOS = NFS ;SHA.Userid = UserID ;SHA.RemoteName = p56psm1:e:\shared ;SHA.RemoteDrive = Z: LIC.ConfigureAs=client LIC.Basedir=C: LIC.Custname=ELITE Tester LIC.Custcomp=IBM LIC.Custaddr=RTP,NC LIC.Custinfo=WARPSERVER TEST ;LIC.Username= ;LIC.Usergroup= LIC.Transport=netbios LIC.Machname=CIDA124 ;LIC.LogFile=C:\ifor\ls\conf\logfile ;LIC.LogLevel=0 ;LIC.LogMsgsMaxNum=10000 ;LIC.ConcurrentNodelock=yes ;LIC.LanAdapter=0 ;LIC.NCBS=40 ;LIC.Create=New ;LIC.Family=netbios Page 48 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ;LIC.RunGLBD=yes ;LIC.RunAlly=yes ;LIC.DisableRemoteAdmin=yes ;LIC.ServLogFile=C:\ifor\ls\conf\log_file ;LIC.LogAllEvents=yes ;LIC.LogGrant=yes ;LIC.LogCheckin=no ;LIC.LogWait=no ;LIC.LogVendor=no ;LIC.LogProduct=no ;LIC.LogTimeout=no ;LIC.LogErrors=no ;LIC.LogVendorMsg=no ;LIC.LogSvrStartStop=no ----------------------------------------------------------------------------- Figure 16. Sample Response File (SV10SWS.RSP) NOTE: To save space in this response file example, any comments in the response file were deleted. To see the actual response file with all the comments included, go to the PKZIP2 package, ELITE042.ZIP, and locate the response file under the RSP subdirectory. 1.2.11.3.1 REMOTE INSTALLATION OF SYSTEMVIEW MANAGER USING SYSTEMVIEW: When using SystemView for software distribution, the distribution client work- station must have SystemView already installed. Therefore we can not use SystemView in this case, to install the SystemView product. 1.2.11.4 SystemView Client o The installation command is SVINST.EXE and is located in the 'CID\CLIENT\SYSVIEW2\CLIENT_2' directory on the Warp Server CD. NOTE: A copy of the SVINST command, INSTALL.EXE, can also be used as the install program. Both SVINST.EXE and INSTALL.EXE are identical. o Response files are required and samples are provided with the product. The sample response file for the SystemView Client is called CLIENT.RSP and is located on the CD in directory CID\CLIENT\SYSVIEW2\CLIENT_2. o Following is the syntax: -- Page 49 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- path\SVINST /A: /L1: /L2: /O: /P: /R: /S: /T: /TU: /X action = D (delete), I (install), U (update) error log = specifies the drive, path, and file name of the installation error log history log = specifies the drive, path, and file name of the installation history file origin system = the value for this is DRIVE product name = provides the name of the product. The value must be Systemview Server Installation or SystemView Client Installation enclosed in double quotes. response file = specifies the drive, path, and file name of the response file you are using. source location = specifies the drive and path containing the source files to install target = specifies the drive and path where SystemView is to be installed update CONFIG.SYS = specifies the drive of the CONFIG.SYS to be updated by the SVINST program. /X = indicates unattended install ----------------------------------------------------------------------------- 1.2.11.5 Sample SystemView Client Profile Page 50 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = C:\SYSVIEW2 Section Catalog Begin ObjectType=Software GlobalName=IBM.SYSVIEW2.REF.10.US.CLIENT.WS Description="SYSTEMVIEW 1.0 CLIENT" End Section Install Begin Program = SA:\IMG\STABLE\SV10CWS\SVINST.EXE Parms = /X /A:I /L1:$(LogFile1) /L2:$(LogFile2) /O:DRIVE /R:$(ResponseFile SourceDir = SA:\IMG\STABLE\SV10CWS ResponseFile = SA:\RSP\SV10CWS\$(WorkStatName).RSP LogFile1 = SB:\LOG\SV10CWS\$(WorkStatName).LOG LogFile2 = SB:\LOG\SV10CWS\$(WorkStatName).HST PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 17. Sample Profile (SVIEW10C.PRO) -- Page 51 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.11.6 Sample SystemView Client Response File ----------------------------------------------------------------------------- WORK = C:\SYSVIEW2 AUX1 = C: CFGUPDATE = AUTO OVERWRITE = YES DELETEBACKUP = NO SAVEBACKUP = YES FILE = I:\SV10CWS COMP = SystemView Client Graphical Interface COMP = SystemView Client COMP = License Use Runtime Client COMP = Software Distribution Object Preparation ; SystemName=CIDA055 Driver.TCPIP = 1 Driver.NETBIOS = 1 Driver.SERIPC = 0 Driver.IPX = 0 Parm1.NETBIOS = CIDA055 ;Parm1.SERIPC = MACHINE1 Keyword.1 = test ;Keyword.2 = key2 ;Keyword.3 = key3 ;Keyword.4 = key4 ;Keyword.5 = key5 ;Keyword.6 = key6 ;Keyword.7 = key7 ;Keyword.8 = key8 NetTimeout = 25 ; Repository = C:\SYSVIEW2\REPOS WorkArea = C:\SYSVIEW2\WORK BackupArea = C:\SYSVIEW2\BACKUP ServiceArea = C:\SYSVIEW2\SERVICE ServerName = CIDA035S ServerDriver = NB ServerAddress = CIDA035 ; ;RWC.CanTerminate = 0 ;RWC.StartMonitor = 1 ;RWC.TimeRefresh = 100 ; LIC.Custname=ELITE Tester LIC.Custcomp=IBM RTP LIC.Custaddr=RTP, NC LIC.Custinfo=SystemView Integration Test ----------------------------------------------------------------------------- Figure 18. Sample Response File (SV10CWS.RSP) Page 52 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.11.6.1 REMOTE INSTALLATION OF SYSTEMVIEW CLIENT USING SYSTEMVIEW: When using SystemView for software distribution, the distribution client work- station must have SystemView already installed. Therefore you can not use SystemView in this case to install the SystemView product. -- Page 53 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.12 LAN DISTANCE CONNECTION SERVER VERSION 5.0 The ability to fully configure LAN Distance via a response file or INSTALL parameters does not exist. Manual definitions via the Settings panel are required to use the product after the installation is complete. If you prefer to use SystemView to install LAN Distance Server, please refer to section 1.2.13, "Remote Installation of LAN Distance Server using SystemView" on page 57. NOTE: IBM Software Installer INSTALL.EXE has the following syntax for LAN Distance: ----------------------------------------------------------------------------- INSTALL /T:target /R:resp_file /L1:logfile resp_file = fully-qualified path & name of the response file target = (optional) target drive to install product. - can be overridden by response file - if not specified here or in response file, current boot drive is used logfile = where installation messages are to be written ----------------------------------------------------------------------------- 1.2.12.1 Sample LAN Distance Connection Server Installation Profile Page 54 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = D:\ Section Catalog Begin ObjectType=Software GlobalName=IBM.LD.REF.50.US.WARPSERVER.SERVER Description="LD 5.0 WARP Server Connection Server" End Section Install Begin Program = SA:\IMG\STABLE\LD50WS\LO319A1\INSTALL.EXE Parms = /T:D: /R:$(ResponseFile) /L1:$(LogFile1) ResponseFile = SA:\RSP\LD50WS\LDSERV.RSP LogFile1 = SB:\LOG\LD50WS\$(WorkStatName).LOG End ----------------------------------------------------------------------------- Figure 19. Sample LAN Distance Connection Server Profile (LD50SWS.PRO) 1.2.12.2 Sample LAN Distance Connection Server Response File ----------------------------------------------------------------------------- ; Target = D:\ Target = C:\ ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ; Note: This value is not required. A default will be supplied that will ; use the boot drive if this value is not specified on the command ; line. This drive must be local to the user's workstation. ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ; WorkStationType = SERVER ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ; Note: This value is optional for the LAN Distance Connection Server. ; The WorkStationType parameter is ignored when the installation is ; for the Connection Server. However, in order to avoid possible ; confusion with the LAN Distance Remote workstation response file ; installation, you may wish to include this value in the LAN Distance ; Connection Server response file installation. ;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ----------------------------------------------------------------------------- Figure 20. Sample LAN Distance Connection Server response file (LDSERV.RSP) -- Page 55 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.12.3 Sample LAN Distance Remote Client Installation Profile ----------------------------------------------------------------------------- TargetDir = C: Section Catalog Begin ObjectType=Software GlobalName=IBM.LD.REF.50.US.WARPSERVER.REMOTE Description="Warp Server LAN Distance 5.0 Remote" End Section Install Begin Program = SA:\IMG\STABLE\LD50WS\LO319R1\INSTALL.EXE Parms = /L1:$(LogFile1) /R:$(ResponseFile) ResponseFile = SA:\RSP\LD50WS\$(WorkStatName).RSP LogFile1 = SB:\LOG\LD50WS\$(WorkStatName).LOG PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 21. Sample LAN Distance Remote Client Profile (LD50RWS.PRO) 1.2.12.4 Sample LAN Distance Remote Client Response File ----------------------------------------------------------------------------- Target = C:\ Phone = 4-5769 LANTYPE = TOKENRING Port = COM1 Modem = USRSPORT.PIF Address = 40000C1DA012 ----------------------------------------------------------------------------- Figure 22. Sample LAN Distance Remote Client Response File (CIDA012.RSP) 1.2.12.4.1 ADDITIONAL NOTES FOR LAN DISTANCE INSTALLATION o Sample response files are found on Warp Server CD under - \CID\SERVER\LDCS\LO319A1\LD_SRV.RSP - \CID\SERVER\LDCS\LO319A1\LD_REM.RSP - \CID\SERVER\SYSVIEW2\SERVER_2\LANDIST.RSP Page 56 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.13 REMOTE INSTALLATION OF LAN DISTANCE SERVER USING SYSTEMVIEW If you are not familiar with SystemView Software Distribution, then please refer to the SystemView Up and Running! book. You can view this book online __________________________ from the Warp Server CD. Change to the directory \CID\SERVER\BOOKS on the Warp Server CD Drive and enter the command "view ikoo0mst.inf". Now you will see the contents of the book. Expand the entry "Getting Started With SystemView" by clicking on the + sign next to the entry. Now expand the sub- topic "Getting Started with CID". Review this section for information on: o CID Software Distribution Environment. o Setting up a Code Server. o CID Software Preparation process and the use of Application Definition Files (ADF) for creating profiles and response files. For more detail on ADF files please see the SystemView Up and Running! book in the section __________________________ entitled "Application Definition File Considerations". o How to catalog and distribute software objects via SystemView. 1.2.13.1 LAN Distance Server ADF File and sample profiles and response files. The ADF file for LAN Distance Server is located on the WARP Server CD in \CID\SERVER\ADFRSP\LD_SRV.ADF. The Eagle Integration Test team used the ADF file as input to SystemView's CID SOFTWARE PREPARATION process to create a profile and response file. See Figure 23 on page 58 for the sample profile generated by SystemView. 1.2.13.1.1 SAMPLE PROFILE NOTE: The PARAMETERS section of the following profile has been edited to fit this document. Please refer to the actual sample profile included in the PKZIP2 file called ELITE042.ZIP that is shipped with this document. -- Page 57 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- GLOBAL NAME: IBM.LANDistanceSrv50.LDSRVWS.REF.050000.US_EN DESCRIPTION: WARP SERVER LDSRV CHANGE FILE TYPE: OS2CID PREREQ COMMAND: cidmount IBMLS $(FREEDRIVE1) $(FREEDRIVE2) CIDA035S DDISK35 DDISK35 POSTREQ COMMAND: cidunmnt IBMLS $(FREEDRIVE1) $(FREEDRIVE2) INSTALL PROGRAM: PROGRAM NAME: $(FREEDRIVE1)\IMG\LDSRVWS\INSTALL.EXE PARAMETERS: /S:$(FREEDRIVE1)\IMG\LDSRVWS /R:$(FREEDRIVE1)\RSP\LDSRVWS\$(SYSTEMNAME).RSP /L1:$(FREEDRIVE2)\LOG\LDSRVWS\$(SYSTEMNAME).L1 /G: ----------------------------------------------------------------------------- Figure 23. Sample LAN Distance Server profile generated by SystemView (LDSRVWS.PRO) 1.2.13.1.2 SAMPLE RESPONSE FILE The Eagle Integration Test team tested the default LAN Distance Server response file created via the CID SOFTWARE PREPARATION process. The response file can be further tailored to work in your environment via the SOFTWARE CONFIGURATION utility (refer to the SystemView Up and Running! book in the __________________________ section entitled "Getting Started with CID") or, if you wish, you can use the same response file used for distributions from NetView DM/2 . Please refer to Figure 20 on page 55 for a sample response file that can be used for dis- tributions from both NetView DM/2 and SystemView. Page 58 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.14 TCP/IP VERSION 3.1 There have been many enhancements in this version of TCP/IP. One change to be noted is TCPINST.EXE has been replaced by IBM Software Installer's INSTALL.EXE. If you are planning to use dynamic IP addresses in your network, you must configure the DHCP and DDNS servers after installation. Dynamic Host Config- uration Protocol (DHCP) server provides configuration information to IP hosts, and the Dynamic Domain Name System (DDNS) provides dynamic host name-to-IP address (and IP address-to-host name) mapping for the Dynamic IP clients. If you prefer to use SystemView to install TCP/IP, please refer to section 1.2.15, "Remote Installation of TCP/IP using SystemView" on page 62. NOTE: IBM Software Installer INSTALL.EXE has the following syntax for TCP/IP: ----------------------------------------------------------------------------- INSTALL /b- /S:source /T:target /R:resp_file /L1:logfile b- = turns off the beep that accompanies the prompt for the next diskette source = fully-qualified path & name of the source directory resp_file = fully-qualified path & name of the response file target = (optional) target drive to install product. - can be overridden by response file - if not specified here or in response file, current boot drive is used logfile = where installation messages are to be written ----------------------------------------------------------------------------- 1.2.14.1 Sample TCP/IP 3.1 Installation Profile -- Page 59 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=IBM.TCPIP.REF.31.US.WARPSERVER Description="Warp Server TCP/IP 3.1" End Section Install Begin Program = SA:\IMG\STABLE\TCP31WS\INSTALL.EXE Parms = /b- /R:$(ResponseFile) /S:$(SourceDir) /L1:$(LogFile1) ResponseFile = SA:\RSP\TCP31WS\$(WorkStatName).RSP SourceDir = SA:\IMG\STABLE\TCP31WS LogFile1 = SB:\LOG\TCP31WS\$(WorkStatName).LOG PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 24. Sample TCP/IP 3.1 Profile (TCP31WS.PRO) Page 60 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.14.2 Sample TCP/IP 3.1 Response File ----------------------------------------------------------------------------- // Default response file for WARP SERVER install INSTALL_WPS=Y IPADDR=9.67.142.124 NETMASK = 255.255.255.0 NAMESERVER = 9.67.128.3 ROUTE = 9.67.142.250 HOSTNAME=ELIT124 DOMAIN=raleigh.ibm.com DNS_DOMAIN=raleigh.ibm.com CONFIGURE=Y ATTENDED=N TARGET_PATH=C:\TCPIP // Default response file for WARP SERVER install INSTALL_NAME = BASE 8.48 1 5 "Client Kit" Base TCP/IP Applications INSTALL_NAME = INET 3.59 6 7 "Client Kit" Feature TCP/IP Applications: WE/2, NR/2, Gopher, and Internet Dialers INSTALL_NAME = DBOX 1.77 7 7 "Client Kit" DOS\Windows Access INSTALL_NAME = UMAIL 4.51 8 9 "Client Kit" UltiMail Lite INSTALL_NAME = DHCPSRV .90 10 10 "Client Kit" DHCP Server Support INSTALL_NAME = DDNSSRV 1.55 10 10 "Client Kit" DDNS Server Support INSTALL_XPG4 = SETLOC 11 11 1.0 "Client Kit" XPG/4 Support library INSTALL_XPG4 = LOCALE 11 11 1.0 "Client Kit" XPG/4 Locale LANG = ENUS437 EXEC = BASE call clntxt EXEC = BASE call tcpcoex EXEC = DBOX call dboxxt EXEC = UMAIL call umlitext ----------------------------------------------------------------------------- Figure 25. Sample TCP/IP Response File (CIDA124.RSP) 1.2.14.2.1 ADDITIONAL NOTES FOR TCP/IP INSTALLATION o Sample response file is found on Warp Server CD under - \CID\SERVER\SYSVIEW2\SERVER_2\NVDM2_CLI\TCPIP30.RSP -- Page 61 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.15 REMOTE INSTALLATION OF TCP/IP USING SYSTEMVIEW If you are not familiar with SystemView Software Distribution, then please refer to the SystemView Up and Running! book. You can view this book online __________________________ from the Warp Server CD. Change to the directory \CID\SERVER\BOOKS on the Warp Server CD Drive and enter the command "view ikoo0mst.inf". Now you will see the contents of the book. Expand the entry "Getting Started With SystemView" by clicking on the + sign next to the entry. Now expand the sub- topic "Getting Started with CID". Review this section for information on: o CID Software Distribution Environment. o Setting up a Code Server. o CID Software Preparation process and the use of Application Definition Files (ADF) for creating profiles and response files. For more detail on ADF files please see the SystemView Up and Running! book in the section __________________________ entitled "Application Definition File Considerations". o How to catalog and distribute software objects via SystemView. 1.2.15.1 TCP/IP ADF File and sample profiles and response files. The ADF file for TCP/IP is located on the WARP Server CD in \CID\SERVER\ADFRSP\TCPAPPS.ADF. The Eagle Integration Test team used the ADF file as input to SystemView's CID SOFTWARE PREPARATION process to create a profile and response file. See Figure 26 on page 63 for the sample profile generated by SystemView. 1.2.15.1.1 SAMPLE PROFILE NOTE: The PARAMETERS section of the following profile has been edited to fit this document. Please refer to the actual sample profile included in the PKZIP2 file called ELITE042.ZIP that is shipped with this document. Page 62 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- GLOBAL NAME: IBM.TCPIP30.TCP31WS.REF.030000.US_EN DESCRIPTION: WARP SERVER TCP/IP 3.1 CHANGE FILE TYPE: OS2CID PREREQ COMMAND: cidmount IBMLS $(FREEDRIVE1) $(FREEDRIVE2) CIDA035S DDISK35 DDISK35 POSTREQ COMMAND: cidunmnt IBMLS $(FREEDRIVE1) $(FREEDRIVE2) INSTALL PROGRAM: PROGRAM NAME: $(FREEDRIVE1)\IMG\TCP31WS\INSTALL.EXE PARAMETERS: /S:$(FREEDRIVE1)\IMG\TCP31WS /R:$(FREEDRIVE1)\RSP\TCP31WS\$(SYSTEMNAME).RSP /L1:$(FREEDRIVE2)\LOG\TCP31WS\$(SYSTEMNAME).L1 ----------------------------------------------------------------------------- Figure 26. Sample TCP/IP profile generated by SystemView (STCP31WS.PRO) 1.2.15.1.2 SAMPLE RESPONSE FILE The Eagle Integration Test team tested the default TCP/IP response file created via the CID SOFTWARE PREPARATION process. The response file can be further tailored to work in your environment via the SOFTWARE CONFIGURATION utility (refer to the SystemView Up and Running! book in the section enti- __________________________ tled "Getting Started with CID") or, if you wish, you can use the same response file used for distributions from NetView DM/2 . Please refer to Figure 25 on page 61 for a sample response file that can be used for distrib- utions from both NetView DM/2 and SystemView. -- Page 63 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.16 PERSONALLY SAFE AND SOUND (PSNS) VERSION 5.0 If you prefer to use SystemView to install PSnS, please refer to section 1.2.17, "Remote Installation of PSNS using SystemView" on page 67. NOTE: PSNSINST.CMD has the following syntax for PSNS: ----------------------------------------------------------------------------- PSNSINST /TU:C: /T:target /R:resp_file /L1:logfile1 /L2:logfile2 /S:source /TU = specifies the boot drive source = fully-qualified path & name of the source directory resp_file = fully-qualified path & name of the response file target = (optional) target drive to install product. - can be overridden by response file - if not specified here or in response file, current boot drive is used logfile1 = where installation error messages are to be written logfile2 = where installation messages are to be written ----------------------------------------------------------------------------- 1.2.16.1 Sample PSnS Installation Profile Page 64 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = C:\PSNS Section Catalog Begin ObjectType=Software GlobalName = IBM.PSNS.REF.50.US.WARPSERVER Description="Warp Server Personally Safe 'N Sound 5.0" End Section Install Begin Program = SA:\IMG\STABLE\PSNS50WS\PSNSINST.CMD Parms = /TU:C: /R:$(ResponseFile) /T:$(TargetDir) /S:$(SourceDir) /L1:$(LogFile1) /L2:$(LogFile2) SourceDir = SA:\IMG\STABLE\PSNS50WS ResponseFile = SA:\RSP\PSNS50WS\$(WorkStatName).RSP LogFile1 = SB:\LOG\PSNS50WS\$(WorkStatName).L1 LogFile2 = SB:\LOG\PSNS50WS\$(WorkStatName).L2 PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 27. Sample PSnS profile (PSNS50WS.PRO) -- Page 65 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.16.2 Sample PSnS Response File The comments were edited out of the PSnS response file for clarity. ----------------------------------------------------------------------------- *********************************************************************** * Warp/Server Backup/Restore CID Response File *********************************************************************** log = Warp Backup/Restore default response file. desktop = 1 audio = 1 samples = 1 optical = 1 lan_drive = 1 hard_disk = 1 diskette = 1 scsi_tape = 1 adsm_client = 1 ----------------------------------------------------------------------------- Figure 28. Sample PSnS Response File (CIDA124.RSP) 1.2.16.2.1 ADDITIONAL NOTES FOR PSNS INSTALLATION o After a successful install, you will need to remotely reboot the target workstation to put the changes into effect. The installation program does not do an automatic reboot after a successful install. o Sample response file is found on Warp Server CD under - \CID\SERVER\PSNS\PSNSINST.RSP Page 66 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.17 REMOTE INSTALLATION OF PSNS USING SYSTEMVIEW If you are not familiar with SystemView Software Distribution, then please refer to the SystemView Up and Running! book. You can view this book online __________________________ from the Warp Server CD. Change to the directory \CID\SERVER\BOOKS on the Warp Server CD Drive and enter the command "view ikoo0mst.inf". Now you will see the contents of the book. Expand the entry "Getting Started With SystemView" by clicking on the + sign next to the entry. Now expand the sub- topic "Getting Started with CID". Review this section for information on: o CID Software Distribution Environment. o Setting up a Code Server. o CID Software Preparation process and the use of Application Definition Files (ADF) for creating profiles and response files. For more detail on ADF files please see the SystemView Up and Running! book in the section __________________________ entitled "Application Definition File Considerations". o How to catalog and distribute software objects via SystemView. 1.2.17.1 PSNS ADF File and sample profiles and response files. The ADF file for PSNS is located on the WARP Server CD in \CID\SERVER\ADFRSP\PSNS.ADF. The Eagle Integration Test team used the ADF file as input to SystemView's CID SOFTWARE PREPARATION process to create a profile and response file. See Figure 29 on page 68 for the sample profile generated by SystemView. 1.2.17.1.1 SAMPLE PROFILE NOTE: The PARAMETERS section of the following profile has been edited to fit this document. Please refer to the actual sample profile included in the PKZIP2 file called ELITE042.ZIP that is shipped with this document. -- Page 67 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- GLOBAL NAME: IBM.PSNS50.PSNS.REF.050000.US_EN DESCRIPTION: WARP SERVER PSNS CHANGE FILE TYPE: OS2CID PREREQ COMMAND: cidmount IBMLS $(FREEDRIVE1) $(FREEDRIVE2) CIDA035S DDISK35 DDISK35 POSTREQ COMMAND: cidunmnt IBMLS $(FREEDRIVE1) $(FREEDRIVE2) INSTALL PROGRAM: PROGRAM NAME: $(FREEDRIVE1)\IMG\PSNS50WS\PSNSINST PARAMETERS: /R:$(FREEDRIVE1)\RSP\PSNS50WS\$(SYSTEMNAME).RSP /L1:$(FREEDRIVE2)\LOG\PSNS50WS\$(SYSTEMNAME).L1 /L2:$(FREEDRIVE2)\LOG\PSNS50WS\$(SYSTEMNAME).L2 /S:$(FREEDRIVE1)\IMG\PSNS50WS ----------------------------------------------------------------------------- Figure 29. Sample PSNS profile generated by SystemView (PSNS.PRO) 1.2.17.1.2 SAMPLE RESPONSE FILE The Eagle Integration Test team tested the default PSNS response file created via the CID SOFTWARE PREPARATION process. The response file can be further tailored to work in your environment via the SOFTWARE CONFIGURATION utility (refer to the SystemView Up and Running! book in the section entitled __________________________ "Getting Started with CID") or, if you wish, you can use the same response file used for distributions from NetView DM/2 . Please refer to Figure 28 on page 66 for a sample response file that can be used for distributions from both NetView DM/2 and SystemView. Page 68 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.18 NETWORK SIGNON COORDINATOR (NSC/2) VERSION 1.2 Separately installable, Network Signon Coordinator is now a CID enabled product. The new installation program is via Software Installer (INSTALL.EXE). (You will automatically get NSC/2 if you did a manual instal- lation of Warp Server via CD ROM). 1.2.18.1 Sample NSC Installation Profile ----------------------------------------------------------------------------- TargetDir=C:\NSC Section Catalog Begin ObjectType=Software GlobalName=IBM.NSC.REF.12.US.WARPSERVER Description="Warp Server Network SignOn Coordinator 1.2" End Section Install Begin Program= SA:\IMG\STABLE\NSC12WS\INSTALL.EXE Parms = /X /A:I /L1:$(LogFile1) /R:$(ResponseFile) /S:$(SourceDir) SourceDir= SA:\IMG\STABLE\NSC12WS ResponseFile= SA:\RSP\NSC12WS\NSC.RSP Logfile1= SB:\LOG\NSC12WS\$(WorkStatName).L1 PhaseEnd = Yes End ----------------------------------------------------------------------------- Figure 30. Sample NSC profile (NSC12WS.PRO) 1.2.18.2 Sample NSC Response File ----------------------------------------------------------------------------- FILE = C:\NSC COMP = Network SignON Coordinator/2 OVERWRITE = YES CFGUPDATE = AUTO SAVEBACKUP = YES AUX1 = C:\NSC\DLL ----------------------------------------------------------------------------- Figure 31. Sample NSC response file (NSC.RSP) -- Page 69 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.18.2.1 ADDITIONAL NOTES FOR NSC INSTALLATION o After a successful install, you will need to remotely reboot the target workstation to put the changes into effect. The installation program does not do an automatic reboot after a successful install. Page 70 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.19 ARRANGING YOUR DESKTOP AFTER A CID INSTALLATION When using CID procedure to install the individual services of Warp Server, use the following procedure to arrange your icons to create an OS/2 Warp Server Desktop after all services have been successfully installed and all system reboots are complete. To create your OS/2 Warp Server Desktop after a CID install: 1. Create a response file to arrange the icons. A sample response file tem- plate is located in \WARPSRV\TABLES\CIDICONS.TMP. This template tells the program where to move the appropriate icons on the desktop. 2. Run the CIDICONS program. CIDICONS.EXE can be found on the Warp Server CD under \WARPSRV. The Eagle Integration Test team copied the entire \WARPSRV subdirectory onto our code server under \IMG\STABLE\ICONSWS for our use. 1.2.19.1 Sample CIDICONS Installation Profile and Response File The Eagle Integration Test team used the following profile and response file to arrange the icons to complete the OS/2 Warp Server Installation: NOTE: CIDICONS.EXE has the following syntax: ----------------------------------------------------------------------------- CIDICONS /TU:C: /T:target /R:resp_file /L1:logfile /S:source /TU = specifies the boot drive source = fully-qualified path & name of the source directory resp_file = fully-qualified path & name of the response file target = (optional) target drive to install product. - can be overridden by response file - if not specified here or in response file, current boot drive is used logfile = where installation messages are to be written ----------------------------------------------------------------------------- -- Page 71 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=IBM.CIDICONS.REF.30.US.WARPSERVER Description="Warp Server Desktop Icons" End Section Install Begin Program = SA:\IMG\STABLE\ICONSWS\CIDICONS.EXE Parms = /T:$(TargetDir) /TU:C: /R:$(ResponseFile) /S:$(SourceDir) /L1:$(LogFile1) ResponseFile = SA:\RSP\OS230WS\CIDICONS\$(WorkStatName).RSP SourceDir = SA:\IMG\STABLE\ICONSWS LogFile1 = SB:\LOG\OS230WS\CIDICONS\$(WorkStatName).LOG End ----------------------------------------------------------------------------- Figure 32. Sample CIDICONS installation profile (CIDICONS.PRO) Page 72 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.19.2 Sample CIDICONS Response File ----------------------------------------------------------------------------- // This is the response file template to re-arrange the icons on the // desktop after the install. // // The format of the response is product_name:drive // // The possible values are: // FAPS - File and Print Sharing Services // MPTS - Adapters and Protocol Services // PSF2 - Advanced Print Services // PSNS - Software Backup and Recovery Services // LDCS - Remote Access Services // SYS2 - System Management Services // NETW - NetWare File and Print Gateway Services // BOOK - Books // TCPIP - TCP/IP Services // // Example: // // FAPS:D // MPTS:C // NETW:D // // FAPS:C MPTS:C PSNS:C LDCS:C SYS2:C NETW:C BOOK:C TCPIP:C ----------------------------------------------------------------------------- Figure 33. Sample CIDICONS response file (CIDA124.RSP) -- Page 73 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.20 ADDITIONAL WARP SERVER COMPONENTS INSTALLATION 1.2.21 NETWARE OS/2 REQUESTER Netware Requester does not provide remote, unattended Configuration Installa- tion and Distribution (CID) support. Because of this, we integrated the LCU command file NWINST.CMD into our NetView DM/2 install. The sample install command file for the Netware Requester, NWINST.CMD, is so long that, for the purposes of readability, it has been placed at the end of this section. See Figure 38 on page 78. After the NetWare Requester is installed, LAPS (MPTS) MUST be re-installed to ____ load the ODI2NDI driver which enables ODI packets to co-exist with NDIS. The re-configuration of MPTS must be done after the NetWare Requester is installed because MPTS uses some of the NetWare Requester's files. See 1.2.22, " MPTS & The Netware Requester" on page 76 for the sample profiles and response files used to reconfigure MPTS/LAPS after the installation of NetWare Requester. NOTE: NetWare Client Version 2.11 for OS/2 cannot be installed over previous versions of NetWare client. Previous versions of NetWare Client must be removed before this NetWare Client Version 2.11 can be installed. The command file, NWINST.CMD, which is used to install the NetWare Requester has the following syntax: ----------------------------------------------------------------------------- NWINST where logname = the full path for the log file cidpath = the full source path where the Netware Requester files reside targdrv = the target drive, specified without the colon, where the Netware Requester is to be installed Example NWINST D:\NW211\NWINST.LOG I:\IMG\NETWARE\ C ----------------------------------------------------------------------------- Figure 34. Syntax for the Netware Requester Command File NWINST.CMD Page 74 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.21.1 Sample NetWare OS/2 Requester Installation Profile ----------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=NOVELL.NETWARE.REF.211.US.WARPSERVER.OS2_REQ Description="NetWare OS/2 Requester from Warp Server" End Section Install Begin Program = SA:\IMG\STABLE\NW211WS\NWINST.CMD Parms = $(LogFile1) $(SourceDir) C SourceDir = SA:\IMG\STABLE\NW211WS\ LogFile1 = SB:\LOG\NW211WS\$(WorkStatName).LOG End ----------------------------------------------------------------------------- Figure 35. Sample NetWare OS/2 Requester Profile (NW211WS.PRO) -- Page 75 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.22 MPTS & THE NETWARE REQUESTER Once the Netware Requester is installed on the system, MPTS must be reinstalled so MPTS Netware Requester support can be added and the CONFIG.SYS file updated. The Netware Requester and MPTS installs can be executed as corequisites using NetView DM/2, with Netware Requester installing FIRST. _____ 1.2.23 SAMPLES USED BY EAGLE INTEGRATION TEST TEST GROUP: ----------------------------------------------------------------------------- TargetDir = C:\ Section Catalog Begin ObjectType=Software GlobalName=IBM.LAPS.ODI.REF.2.WR08200.US.WARPSERVER.ODINDIS Description="LAPS ODINDIS PROD install" End Section Install Begin Program = SA:\IMG\STABLE\LA8200WS\MPTS.EXE Parms = /E:PROD /R:$(ResponseFile) /TU:C:\ /S:$(SourceDir) /L1:$(LogFile1) SourceDir = SA:\IMG\STABLE\LA8200WS ResponseFile = SA:\RSP\LAPSODI\$(WorkStatName).RSP LogFile1 = SB:\LOG\LA8200WS\$(WorkStatName).LOG End ----------------------------------------------------------------------------- Figure 36. Sample MPTS Netware Profile (LA8200WO.PRO) Page 76 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- PROT_SECTION = ( NIF = ODI2NDI.NIF SECTION_NAME = ODI2NDI_NIF DRIVERNAME = odi2ndi$ BINDINGS = IBMMPC_NIF NETADDRESS="T40000C1DA124" TOKEN-RING = "yes" TOKEN-RING_SNAP = "no" ETHERNET_802.3 = "no" ETHERNET_802.2 = "no" ETHERNET_II = "no" ETHERNET_SNAP = "no" TRACE = 0x0 ) PROT_SECTION = ( NIF = IBMMPC.NIF SECTION_name = IBMMPC_NIF DRIVERNAME = IBMMPC$ ) ----------------------------------------------------------------------------- Figure 37. Sample MPTS Netware Response File (CIDA124.RSP) -- Page 77 of 90 (C) COPYRIGHT IBM CORP. 1996 1.2.23.1 Sample Netware Requester Install Command File (NWINST.CMD) ----------------------------------------------------------------------------- /*************************************************************************/ /* Licensed Materials - Property of IBM */ /* */ /* XXXX-XXX */ /* */ /* (C) Copyright IBM Corp. 1995. All Rights Reserved. */ /* */ /* US Government Users Restricted - Use, duplication, or */ /* disclosure restricted by GSA ADP Schedule Contract with IBM Corp. */ /* */ /*************************************************************************/ /* First get addressability to the required source directories and target workst Call RxFuncAdd SysLoadFuncs, RexxUtil, SysLoadFuncs Call SysLoadFuncs /* Replaced following with technique from Address.cmd */ /* call RxFuncAdd 'GetBootDrive', 'RLANUTIL', 'GetBootDrive' */ Parse upper arg logname CIDPath TargDrv msgfile = 'OSCINST.MSG' If CIDPath = '' then CIDPath = 'X:\' /* If GrpPath = '' then do */ /* err1.1 = SysGetMessage(201, msgfile) */ /* err1.2 = '' */ /* call errout 201 */ /* end (Do) */ /* *** Following four lines replace getbootdrive **** */ dpathstr = value("DPATH",,"OS2ENVIRONMENT") dpathstr = translate(dpathstr) parse var dpathstr first '\OS2\' . os2drv = right(first,2) /* os2drv = GetBootDrive() */ CFG_SYS = os2drv'\CONFIG.SYS' A=0 Do Until Lines(CFG_SYS) = 0 A = A+1 CFG_SYS.A = LineIn(CFG_SYS) End Call Stream CFG_SYS, 'C', 'CLOSE' ----------------------------------------------------------------------------- Figure 38 (Part 1 of 8). Sample Netware Requester Command File (NWINST.CMD) Page 78 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- /* Scan for Netware indicator in config.sys */ nwpath = '' do i = 1 to A parse upper var CFG_SYS.i kw'='kwval if kw = 'DEVICE' & pos('\LSL.SYS',kwval) > 0 then do /*Netware found in c.sys nwpath = strip(left(kwval,pos('\LSL.SYS',kwval)-1)) /*Install here even if nwdrv = left(nwpath,2) /* different from user selection */ end /* Do */ end /* For now do not try to upgrade existing installed Netware */ if nwpath \= '' then do err1.1 = SysGetMessage(209, msgfile) err1.2 = "" call errout 209 end /* Do */ /* Setup NetWare drive and path */ if nwpath = '' then do /* Netware not installed here */ /* drvfil = GrpPath'DRIVES.RSP' (Use drive selected by user) */ /* do while lines(drvfil) \= 0 */ /* this =linein(drvfil) */ /* if lastpos('NWDrv', this) \= 0 then do */ /* parse var this .'='nwdrv':'. */ /* end */ /* end (do) */ nwdrv=TargDrv nwdrv =strip(nwdrv)||':' /* Drive selected by user */ nwpath = nwdrv||'\NETWARE' /* call lineout drvfil */ end /* do */ /* Save the user's Config.sys and load the NetWare image on workstation */ "@Copy" CFG_SYS os2drv'\CONFIG.NVL 1>nul 2>nul' 'XCOPY 'CIDPath'IMG\NWREQ\NETWARE 'nwpath'\/S/E/V' /* Check for NET.CFG file, Don't change an existing one */ net_cfg = SysSearchPath('DPATH', 'NET.CFG') If net_cfg = '' then do /* No existing NET.CFG. Install a new default one */ '@COPY 'CIDPath'IMG\NWREQ\NET.CFG 'os2drv'\NET.CFG 1>nul 2>nul' end /* See if WIN-OS/2 is installed */ winpath = os2drv||'\os2\mdos\winos2' wininst = 'NO' if stream(winpath'\win.com','C','query exists') \= '' then wininst = 'YES' ----------------------------------------------------------------------------- -- Page 79 of 90 (C) COPYRIGHT IBM CORP. 1996 Figure 38 (Part 2 of 8). Sample Netware Requester Command File (NWINST.CMD) ----------------------------------------------------------------------------- /* Get the additional NetWare config.sys statements */ B=0 NVL_SYS = CIDPath'IMG\NWREQ\NETWARE.DAT' Do Until Lines(NVL_SYS) = 0 B = B+1 NVL_SYS.B= LineIn(NVL_SYS) End Call Stream NVL_SYS, 'C', 'CLOSE' /* Substitute real drives for parameterized drives in NetWare statements */ do i = 1 to B if lastpos('&NWPath', NVL_SYS.i) \= 0 then do t1 = NVL_SYS.i parse var t1 f1'&NWPath'l1 NVL_sys.i = f1||nwpath||l1 end /* Do */ else if lastpos('&OS2Drv', NVL_SYS.i) \= 0 then do t1 = NVL_SYS.i parse var t1 f1'&OS2Drv'l1 NVL_sys.i = f1||os2drv||l1 end /* Do */ end /* do */ /* Modify the config.sys file with the NetWare statements */ C=0 VemmFound = 'NO' BindFound = 'NO' Do i = 1 to A C = C+1 CFG_SYS.i = Strip(CFG_SYS.i,T) Parse Var CFG_SYS.i CFG_Stmt '=' MIDDLE 'OS2\' STMT If Strip(CFG_Stmt) = 'LIBPATH' Then Do If Right(CFG_SYS.i,1) \== ';' Then CFG_SYS.i = CFG_SYS.i || ';' CFG_SYS.i = CFG_SYS.i ||nwpath';'nwpath'\NLS\ENGLISH;L:\OS2;P:\OS2;' End If Strip(CFG_Stmt) = 'SET PATH' Then Do If Right(CFG_SYS.i,1) \== ';' Then CFG_SYS.i = CFG_SYS.i || ';' CFG_SYS.i = CFG_SYS.i ||nwpath';L:\OS2;P:\OS2;' End If Strip(CFG_Stmt)= 'SET DPATH' Then Do If Right(CFG_SYS.i,1) \== ';' Then CFG_SYS.i = CFG_SYS.i || ';' CFG_SYS.i = CFG_SYS.i ||nwpath';'nwpath'\NLS;'nwpath'\NLS\ENGLISH;L:\NLS;P: End ----------------------------------------------------------------------------- Figure 38 (Part 3 of 8). Sample Netware Requester Command File (NWINST.CMD) Page 80 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- If Strip(CFG_Stmt) = 'SET HELP' Then Do If Right(CFG_SYS.i,1) \== ';' Then CFG_SYS.i = CFG_SYS.i || ';' CFG_SYS.i = CFG_SYS.i ||nwpath'\NLS\ENGLISH;' End If Lastpos('VEMM.SYS',STMT) \= 0 & VemmFound = 'NO' & wininst = 'YES' then do /* Insert the NetWare Vipx & Vshell statements ahead of the */ /* DEVICE=d:\OS2\MDOS\VEMM.SYS statement. */ VemmFound = 'YES' Do j = 1 to 2 New_CFG.C = NVL_SYS.j C=C+1 End End /* if laspos */ If Lastpos('NETBIND.EXE',MIDDLE) \= 0 & BindFound = 'NO' then do /* Insert the NetWare config.sys statements ahead of the */ /* \IBMCOM\PROTOCOL\NETBIND.EXE statement. */ BindFound = 'YES' Do j = 4 to B New_CFG.C = NVL_SYS.j C=C+1 End End /* if laspos */ New_CFG.C = CFG_SYS.i End /* of do to modify config.sys */ /* Write out the new config.sys */ K=1 Call Lineout CFG_SYS,,1 Do Until New_CFG.k = 'NEW_CFG.' ||k Call LineOut CFG_SYS, New_CFG.k K=K+1 End Call Stream CFG_SYS, 'c' , "Close" /* Add the hidden install file to the root of the OS/2 drive */ '@'CIDpath'exe\os2\attrib -h 'os2drv'\nwinst.dat 1>nul 2>nul' nwinstin = LineIn(CIDPath||'IMG\NWREQ\nwinst.dat') Call Stream CIDPath||'IMG\NWREQ\nwinst.dat', 'C', 'CLOSE' nwinstout = Translate(nwpath)||Right(nwinstin, length(nwinstin)-length(nwpath)) '@del 'os2drv'\nwinst.dat 1>nul 2>nul' Call Charout os2drv'\nwinst.dat', nwinstout Call Charout os2drv'\nwinst.dat' '@'CIDpath'exe\os2\attrib +h 'os2drv'\nwinst.dat 1>nul 2>nul' ----------------------------------------------------------------------------- Figure 38 (Part 4 of 8). Sample Netware Requester Command File (NWINST.CMD) -- Page 81 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- /* If WIN-OS/2 is installed finish the installation of Windows support */ If wininst = 'YES' then do 'XCopy 'CIDpath'IMG\NWREQ\SYSTEM 'OS2drv'\OS2\MDOS\WINOS2\SYSTEM\ /V' /* Update the Autoexec.bat with NetWare statements */ autox = OS2drv||'\autoexec.bat' autox.1 = OS2drv||'\OS2\MDOS\WINOS2\SYSTEM\TBMI2.COM' autox.2 = nwpath||'\NETX.EXE' AA=2 Do Until Lines(autox) = 0 AA = AA+1 autox.AA = LineIn(autox) End Call Stream autox, 'C', 'CLOSE' /* Write the new Autoexec.bat */ K=1 Call Lineout autox,,1 Do Until autox.k = 'AUTOX.'||k Call LineOut autox, autox.k K=K+1 End Call Stream autox, 'C', "Close" /* Update \WINOS2\SYSTEM.INI for NetWare support */ /* First read in System.ini */ sys_ini = winpath||'\system.ini' A=0 Do Until Lines(sys_ini) = 0 A = A+1 sys_ini.A = LineIn(sys_ini) End Call Stream sys_ini, 'C', 'CLOSE' /* Now insert the NetWare stuff in the appropriate sections of system.ini */ C=1 Do i = 1 to A new_sys.C = sys_ini.i shout = Translate(sys_ini.i) C = C+1 If Lastpos('[BOOT]',shout) \= 0 then do new_sys.C = 'network.drv=netware.drv' C = C+1 End ----------------------------------------------------------------------------- Figure 38 (Part 5 of 8). Sample Netware Requester Command File (NWINST.CMD) Page 82 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- If Lastpos('[BOOT.DESC',shout) \= 0 then do new_sys.C = 'network.drv=Novell NetWare' C = C+1 End If Lastpos('[386ENH]',shout) \= 0 then do new_sys.C = 'FileSysChange=off' C = C+1 End End /* Do */ /* Write modified system.ini */ K=1 Call Lineout sys_ini,,1 Do Until new_sys.k = 'NEW_SYS.' ||k Call LineOut sys_ini, new_sys.k K=K+1 End Call Stream sys_ini, 'C' , "Close" end /* wininst = YES then do */ call nvldsk err1.1 = SysGetMessage(215, msgfile, 'Novell Update') err1.2 = '' call errout 0 RETURN 0 nvldsk: /* This procedure makes the Netware desktop folder and its included icons */ /* Call RxFuncAdd SysLoadFuncs, RexxUtil, SysLoadFuncs Call SysLoadFuncs */ '@Echo Off' /* Now create the Netware folder and place objects in it */ Classname= 'WPFolder' Title = 'Novell' Location = '' Setup = "OBJECTID=;ICONFILE="nwpath"\NVFLDR.ICO" result=SysCreateObject(classname,Title,Location,Setup) /* add the client program */ Classname= 'WPProgram' Title = 'NetWare Client' Location = '' Setup = "OBJECTID=;ICONFILE="nwpath"\NWOS2DOC.ICO;EXENAME="os2drv"\O result=SysCreateObject(classname,Title,Location,Setup) ----------------------------------------------------------------------------- -- Page 83 of 90 (C) COPYRIGHT IBM CORP. 1996 Figure 38 (Part 6 of 8). Sample Netware Requester Command File (NWINST.CMD) Page 84 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- /* add the utilities program */ Classname= 'WPProgram' Title = 'NetWare Utils' Location = '' Setup = "OBJECTID=;ICONFILE="nwpath"\NWOS2DOC.ICO;EXENAME="os2drv"\OS result=SysCreateObject(classname,Title,Location,Setup) /* add the install program */ Classname= 'WPProgram' Title = 'Install' Location = '' Setup = 'EXENAME='nwpath'\INSTALL.EXE;STARTUPDIR='nwpath';OBJECTID= result=SysCreateObject(classname,Title,Location,Setup) /* add the NetWare Printer program */ Classname= 'WPProgram' Title = 'Network Printer' Location = '' Setup = 'EXENAME='nwpath'\NPRINTER.EXE;STARTUPDIR='nwpath';OBJECTID= ' result=SysCreateObject(classname,Title,Location,Setup) /* add the Tools program */ Classname='WPProgram' Title = 'NetWare Tools' Location = '' Setup = 'EXENAME='nwpath'\NWTOOLS.EXE;STARTUPDIR='nwpath';OBJECTID= ' result=SysCreateObject(classname,Title,Location,Setup) Quit: RETURN 0 errout: if logname = '' then logname = 'C:\ERROR.OUT' parse arg retc if retc \= 0 then do say err1.1 say err1.2 end /* Do */ ----------------------------------------------------------------------------- Figure 38 (Part 7 of 8). Sample Netware Requester Command File (NWINST.CMD) -- Page 85 of 90 (C) COPYRIGHT IBM CORP. 1996 ----------------------------------------------------------------------------- err1.0 = 2 rc = stream(logname, 'C', 'QUERY EXISTS') if rc \= '' then '@del' logname '1>nul 2>nul' do i = 1 to err1.0 call lineout logname, err1.i end /* do */ call lineout logname EXIT retc ----------------------------------------------------------------------------- Figure 38 (Part 8 of 8). Sample Netware Requester Command File (NWINST.CMD) Page 86 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 1.2.24 PKZIP2 SAMPLES The sample profiles and response files shown are available in a PKZIP2 file called ELITE042.ZIP. The following table shows the specific directory infor- mation to locate the samples. +-----------------------------+---------------+-----------------------------+ | SAMPLE LOCATION IN THIS | FILE NAME IN | PKZIP2 DIRECTORY LOCATION | | DOCUMENT | PKZIP2 DIREC- | | | | TORY | | +-----------------------------+---------------+-----------------------------+ | Figure 1 on page 13 | OS230WP.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 2 on page 14 | LA8200WB.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 3 on page 14 | NDM2466B.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 4 on page 16 | CIDA124.RSP | ELITE042\WS\RSP\OS230WS | +-----------------------------+---------------+-----------------------------+ | Figure 5 on page 17 | CIDA124.RSP | ELITE042\WS\RSP\LA8200WS | +-----------------------------+---------------+-----------------------------+ | Figure 6 on page 20 | CIDA124.RSP | ELITE042\WS\RSP\NVDM2466 | +-----------------------------+---------------+-----------------------------+ | Figure 7 on page 22 | CIDA112.RSP | ELITE042\WS\RSP\LA8200WS | +-----------------------------+---------------+-----------------------------+ | Figure 8 on page 26 | CIDA016.RSP | ELITE042\WS\RSP\LA8200WS | +-----------------------------+---------------+-----------------------------+ | Figure 9 on page 30 | MPTSWS.PRO | ELITE042\SV\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 10 on page 32 | LSS50WS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 11 on page 34 | CIDA124.RSP | ELITE042\WS\RSP\LS50WS | +-----------------------------+---------------+-----------------------------+ | Figure 14 on page 42 | LS50WS.PRO | ELITE042\SV\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 12 on page 38 | LSR50WS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 13 on page 40 | CIDA078.RSP | ELITE042\WS\RSP\LS50WS | +-----------------------------+---------------+-----------------------------+ | Figure 15 on page 46 | SV10SWS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 16 on page 48 | SV10SWS.RSP | ELITE042\WS\RSP\SV10SWS | +-----------------------------+---------------+-----------------------------+ | Figure 17 on page 51 | SVIEW10C.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 18 on page 52 | SV10CWS.RSP | ELITE042\WS\RSP\SV10CWS | +-----------------------------+---------------+-----------------------------+ | Figure 19 on page 54 | LD50SWS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 20 on page 55 | LDSERV.RSP | ELITE042\WS\RSP\LD50WS | +-----------------------------+---------------+-----------------------------+ | Figure 23 on page 58 | LDSRVWS.PRO | ELITE042\SV\PROFILES | +-----------------------------+---------------+-----------------------------+ -- Page 87 of 90 (C) COPYRIGHT IBM CORP. 1996 +-----------------------------+---------------+-----------------------------+ | SAMPLE LOCATION IN THIS | FILE NAME IN | PKZIP2 DIRECTORY LOCATION | | DOCUMENT | PKZIP2 DIREC- | | | | TORY | | +-----------------------------+---------------+-----------------------------+ | Figure 21 on page 56 | LD50RWS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 22 on page 56 | CIDA012.RSP | ELITE042\WS\RSP\LD50WS | +-----------------------------+---------------+-----------------------------+ | Figure 24 on page 60 | TCP31WS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 25 on page 61 | CIDA124.RSP | ELITE042\WS\RSP\TCP31WS | +-----------------------------+---------------+-----------------------------+ | Figure 26 on page 63 | STCP31WS.PRO | ELITE042\SV\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 27 on page 65 | PSNS50WS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 28 on page 66 | CIDA124.RSP | ELITE042\WS\RSP\PSNS50WS | +-----------------------------+---------------+-----------------------------+ | Figure 29 on page 68 | PSNS.PRO | ELITE042\SV\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 30 on page 69 | NSC12WS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 31 on page 69 | NSC.RSP | ELITE042\WS\RSP\NSC12WS | +-----------------------------+---------------+-----------------------------+ | Figure 32 on page 72 | CIDICONS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 33 on page 73 | CIDA124.RSP | ELITE042\WS\RSP\CIDICONS | +-----------------------------+---------------+-----------------------------+ | Figure 35 on page 75 | NW211WS.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 36 on page 76 | LA8200WO.PRO | ELITE042\WS\PROFILES | +-----------------------------+---------------+-----------------------------+ | Figure 37 on page 77 | CIDA124.RSP | ELITE042\WS\RSP\LAPSODI | +-----------------------------+---------------+-----------------------------+ | Figure 38 on page 78 | NWINST.CMD | ELITE042\WS\UTILS | +-----------------------------+---------------+-----------------------------+ 1.3 REPORT CONTACT ___________________ The ELITE Team reports are available to IBM employees via the IBM internal MKTTOOLS and PCWIN conference disks. The reports are named ELITExxx, where the xxx represents an incremental number (e.g. 001, 002, etc.). The ELITE team has also authored a document called, "Quick Help for Installation of IBM Products via NetView DM/2". This document is available in a package called NVDM2HLP PACKAGE. Additionally, there is a package named ELITE, which con- tains an index of all ELITE documentation currently available. We encourage you to also obtain and review these reports for additional product specific information. The test reports and books are also available on the Internet World Wide Web. To access the ELITE reports and books on the Internet, simply go to the IBM Networking Home Page and click on "Resources", and then on "ELITE's LAN Page 88 of 90 -- Quick Help (C) COPYRIGHT IBM CORP. 1996 Product Integration Reports". You will then see an index into all of the available ELITE documentation. The IBM Networking Home Page can be accessed at HTTP://www.raleigh.ibm.com. IBM employees may need to use an alternate address of HTTP://wwwidd.raleigh.ibm.com. Questions or comments about this report or about integration testing can be sent: o via VNET to ELITE at RALVM12, o via Internet to elite@vnet.ibm.com o via IBMMAIL to USIB5K9S at IBMMAIL. Please reference this document (ELITE042) in your note. -- Page 89 of 90 (C) COPYRIGHT IBM CORP. 1996 1.4 NOTICES ____________ The information contained in this document is distributed AS IS. The use of this information or the implementation of any of these techniques is a cus- tomer responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. Customers attempting to adapt these techniques to their own environments do so at their own risk. IBM will accept no liability for consequences resulting from the use of this information. This report is to be used solely for the purpose of installing and supporting the product(s) discussed. This material must not be used for other purposes without the written consent of IBM. In addition, this material must not be redistributed outside your company. The following terms are trademarks of the International Business Machines Corporation in the United States and/or other countries. Those trademarks followed by an asterisk (*) are registered trademarks of the International Business Machines Corporation. o FFST o IBM* o LAN Distance o NetView* o OS/2* o SystemView* o WIN-OS/2 The following terms are trademarks or registered trademarks of Microsoft Cor- poration: o Windows The following terms are registered trademarks of Novell, Inc.: o Novell, NetWare Page 90 of 90 -- Quick Help ----------------------------------------------------------------------------- (C) COPYRIGHT IBM CORP. 1996 Printed in U.S.A.