RemoteWare OS/2 Client

Transcription

1 RemoteWare OS/2 Client User s Guide Version 4.1 Service Pack 1A

2 RemoteWare OS/2 Client User s Guide Version 4.1 Service Pack 1A This document was prepared to assist licensed users of RemoteWare by XcelleNet, Inc.; its contents may not be used for any other purpose without prior written permission. The material contained herein is supplied without representation or warranty of any kind and is based on typical use. Any unusual use may produce unpredictable results. XCELLENET ASSUMES NO RESPONSIBILITY AND SHALL HAVE NO LIABILITY OF ANY KIND ARISING FROM THE SUPPLY OR USE OF THIS DOCUMENT OR THE MATERIAL CONTAINED HEREIN. Companies, names, information, and data used in examples herein are fictitious unless otherwise noted. The information in this document is furnished for informational use only and is subject to change without notice. References in this manual to XcelleNet products, programs, or services do not imply that XcelleNet intends to make these available in all countries in which XcelleNet operates. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR XcelleNet, Inc. All Rights Reserved. All rights reserved, including the right to reproduce this document or any portion thereof in any form. Printed in the United States of America. RemoteWare is a trademark of XcelleNet, Inc. Other product and company names mentioned herein may be the brand names, trade names, trademarks or registered trademarks of their respective orders.

3 Contents USING THIS GUIDE About this guide... v Use Adobe Acrobat to view guide online... v Using RemoteWare online Help... vi What s in this guide... vii CHAPTER 1: INSTALLATION Client system requirements Installing a custom Client Installing a template Client Configuring communications settings Registering the Template Client Installing a text-mode Client Installing a text-mode Template Client CHAPTER 2: USING THE CLIENT SOFTWARE RemoteWare Client at a glance Starting the communications kernel Starting Client communications Client user interface Connecting with the Server Using the Dialing Directory Setting up the Client Setting up connection schedules Viewing the communications log Viewing the alerts Reinitializing the modem Unloading the Client Exiting Client communications Communicating automatically with OS2AUTO OS2TCOMM Text-Mode Communications Setting up the Client... 65

4 iv RemoteWare OS/2 Client User s Guide APPENDIX A: CLIENT DIRECTORY STRUCTURE Installation details File and directory changes APPENDIX A: ADDENDUM NOTES Installing a custom Client Installing a template Client Configuring communications settings Registering the template Client Installing a text-mode Client RemoteWare Client at a Client Starting the communications kernel Stopping the Communications kernel Alert conditions Electronic Software Distribution (ESD) Applying ESD Changing the modem setup Cancelling a session Viewing Alerts ESD update received Connecting with the Server... 80

5 Chapter X: Chapter Title <-- Apply chapter hidden style Using This Guide This guide introduces you to the RemoteWare Client for OS/2. It contains all of the fundamental information necessary to install the software, including a conceptual overview and highly interactive walkthroughs. The Client software allows a computer to communicate with a RemoteWare Server to exchange information. About this guide We recommend you print this guide so it is readily available as you perform your tasks. If you prefer to use this guide online, you may find it helpful to zoom to 150% for enhanced readability. Printing this manual From Acrobat Reader, you can print the entire guide or a range of pages. To print the guide: 1 On the File menu, click Print. 2 Select the printer and number of copies, and click OK. Use Adobe Acrobat to view guide online Use Adobe Acrobat Reader s hyperlinks and Find features to easily access information in this guide. Hyperlinks Hyperlinks take you directly to a topic or page. Hyperlinks are included for the following: Table of Contents and Index Topics at the beginning of each chapter Cross references To use hyperlinks: 1 Click the Hand tool on the Acrobat Reader toolbar. The pointer changes to a hand. 2 Place the hand symbol over the topic/page number you want to view and click. Acrobat Reader takes you to the page you selected.

6 vi RemoteWare OS/2 Client User s Guide Find feature You can use Find to search for text in any document you have open. To search for text: 1 On the toolbar, click Find. 2 Enter the term(s) you want to find in the Find What field. Click Cancel to close. 3 To narrow your search: Match Whole Word Only to search for the exact term only. Match Case to do a case-sensitive search. Find Backwards to move backwards instead of forwards through the document. 4 Click Find to begin your search. To continue to search for other instances of a term, select Edit and Find Again. In the Find dialog box, the original term displays in the Find What field. Click Find Again. Repeat this process until you have found the section you want to view. Using RemoteWare online Help RemoteWare online Help provides explanations of features and steps for how to complete tasks. To access RemoteWare online Help: On the application s Help menu, click Topics (or Help Topics), or press F1.

7 Using This Guide vii What s in this guide This guide includes the following: Table 1. Chapters in this guide Chapter Title Description Chapter 1 Installation Installing the OS/2 Client software Chapter 2 Using the Client Software Using the RemoteWare Client software, including connecting to the Server and setting up connection schedules. Appendix A Client Directory Structure Describes the files installed as well as the directories created during installation. Addendum Addendum Notes Additional information that relates to a variety of topics.

8 viii RemoteWare OS/2 Client User s Guide

9 Chapter X: Chapter Title <-- Apply chapter hidden style CHAPTER 1 1 Installation The RemoteWare OS/2 Client includes an installation program for installing the Client software on an OS/2 computer. This chapter includes: How to start the installation program on the Client computer Installation and registration of a template Client Install a text-mode Client, custom or template

10 10 RemoteWare OS/2 Client User s Guide Client system requirements To install and use the RemoteWare OS/2 Client, you need the following: A computer operating OS/2, version 3.x or 4.x. Hard drive with a minimum of 10 MB free space and one 3.5" disk drive. A minimum of 16 MB memory (RAM). An asynchronous or network connection to access the RemoteWare Server. A disk containing the Client installation kit, or a network share containing the installation kit files. The installation kit is provided by your RemoteWare Server administrator. Installing a custom Client The Server Administrator may have provided you with a set of installation disks or files containing a custom Client. A custom Client allows your administrator to completely configure the Client so you do not have to adjust settings (such as network addresses and modem settings) during installation. You install the Client software using the OINSTALL program. This program is available on the disk containing the Client installation kit, or in a specified directory if the files are on a network. To install the custom Client software: 1 Open an OS/2 command prompt. 2 To install the software from a floppy disk, insert the installation disk in the computer s disk drive, and change to the appropriate disk drive letter. To install the software from the network, change the appropriate disk drive letter. 3 Enter the following command at the prompt: OINSTALL

11 CHAPTER 1 / Installation 11 4 The RemoteWare Client Installation window is displayed. Complete the fields in the window: Destination Drive. Set the drive on which to install the Client. Destination Directory. Set the directory in which to install the Client. Local Time Zone. Select the appropriate time zone for the Client. 5 Select Start Installation. 6 The installation prompts you to confirm the command. Yes. Continues the installation to the specified drive and directory. No. Remains at the initial window, allowing you to change the installation settings. Once started, the installation program creates the necessary directories on the Client, and copies all the necessary files into those directories. 7 The program prompts you to add the RemoteWare program group to the desktop. Yes. Adds the program group to the desktop. No. Does not alter the current desktop.

12 12 RemoteWare OS/2 Client User s Guide 8 The program prompts you to modify the startup.cmd and config.sys files: n Change the x: in the examples to the drive letter for the Client software. Yes. Adds the \nodesys directory to your libpath and set path statements and sets the Client drive variable in the config.sys file. The following lines are added to the startup.cmd file: x: CD "\<install directory>\nodesys" IF EXIST "\<install directory>\nodesys\updates\*.*" COPY "\<install directory>\nodesys\updates\*.*" "\<install directory>\nodesys" >NUL DEL /N "\<install directory>\nodesys\updates\*.*" >NUL START /N /FS OS2NODE No. Makes no changes to the files. To apply Client software updates, you should add the <install directory>\nodesys directory to your libpath and set path statements and set the Client drive variable and time zone variable. Your config.sys statements should be similar to the following: LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;x:\<install directory>\nodesys; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS;x:\<install directory>\nodesys SET XNODE_DISK=x: TZ=XDT5 Note: If the time zone variable is not set, Client Electronic Software Distribution (ESD) may not function correctly. Change Drive. Allows you to select the drive where the files to be modified reside. A message is displayed once the files have been changed. If you chose not to have the files changed, the program continues. A message is displayed when the installation is finished. 9 Click OK to close the message. 10 Reboot the computer. The Client is installed and is ready to communicate with the RemoteWare Server.

13 CHAPTER 1 / Installation 13 Installing a template Client The Server Administrator may have provided you with a set of installation disks or files containing a Template Client. A Template Client allows your administrator to easily configure large quantities of Clients and allows you to adjust specific settings (such as network addresses and modem settings) during installation. The Template Client becomes a regular RemoteWare Client after installation and registration are complete. You install the Client software using the OINSTALL program. This program is available on the disk containing the Client installation kit, or in a specified directory if the files are on a network. To install the template Client software: 1 Open an OS/2 command prompt. 2 To install the software from a floppy disk, insert the installation disk in the computer s disk drive and change the current drive to the appropriate disk drive letter. To install the software from the network, change to the appropriate disk drive letter. 3 Enter the following command at the prompt: OINSTALL 4 The RemoteWare Client Installation window is displayed. Complete the fields in the window: Destination Drive. Set the drive on which to install the Client. Destination Directory. Set the directory in which to install the Client. Local Time Zone. Select the appropriate time zone for the Client. 5 Select Start Installation.

14 14 RemoteWare OS/2 Client User s Guide 6 The installation prompts you to confirm the command. Yes. Continues the installation to the specified drive and directory. No. Remains at the initial window, allowing you to change the installation settings. Once started, the installation program creates the necessary directories on the Client and copies all the necessary files into those directories. 7 The program prompts you to add the RemoteWare program group to the desktop. Yes. Adds the program group to the desktop. No. Does not alter the current desktop. 8 The program prompts you to modify the startup.cmd and config.sys files: n Change the x: in the examples to the drive letter for the Client software. Yes. Adds the \nodesys directory to your libpath and set path statements and sets the Client drive variable in the config.sys file. The following lines are added to the startup.cmd file: x: CD \<install directory>\nodesys" IF EXIST "\<install directory>\nodesys\updates\*.*" COPY "\<install directory>\nodesys\updates\*.*" "\<install directory>\nodesys" >NUL DEL /N "\<install directory>\nodesys\updates\*.*" >NUL START /N /FS OS2NODE No. Makes no changes to the files. To apply Client software updates, you should add the <install directory>\nodesys directory to your libpath and set path statements and set the Client drive variable and time zone variable. Your config.sys statements should be similar to the following: LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;x:\<install directory>\nodesys; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS;x:\<install directory>\nodesys SET XNODE_DISK=x: TZ=XDT5

15 CHAPTER 1 / Installation 15 Note: If the time zone variable is not set, Client Electronic Software Distribution (ESD) may not function correctly. Change Drive. Allows you to select the drive where the files to be modified reside. A message is displayed once the files have been changed. If you chose not to have the files changed, the program continues. To register a template Client: Many of the windows in this section appear only if the Server Administrator has enabled that feature. If you do not encounter any of the windows shown below, please skip to the next illustration that is familiar. 1 Enter your specific Client data in the Client Registration Information window. If you are not certain what values to enter, contact your Server Administrator or enter what you believe is appropriate information. Most of these values can be changed later. Client Name. (This field might not be present.) Type the Client name as given to you by the Server Administrator or supply your own Client name (up to 8 characters). Entering a name that already exists at the Server may cause the Client registration to fail. Note: Once you set the Client name, it cannot be changed. Password. Enter up to 10 characters for a password. Description. Enter up to 22 characters. This description tells the Server Administrator the location or function of this Client.

16 16 RemoteWare OS/2 Client User s Guide Click Next to continue. 2 Enter the Registration Security Information. The RemoteWare Server uses this information to authenticate your Client. Note: This window or some of its fields may not appear depending on the way the Server Administrator has set up the Client. All values on this window must be entered exactly as supplied or the Client registration process will fail. Server Serial Number. Enter the RemoteWare System serial number provided by the RemoteWare Server Administrator. Registration Key. Enter the registration key provided by the Server Administrator. (This field is defined by the Administrator.) Click Next to continue.

17 CHAPTER 1 / Installation 17 3 Provide the Registration Contact Information for this Client. The information in this window may be used by the Server Administrator for reference; it is not used by the RemoteWare Server. Complete these fields with the relevant information: Name. Provide a name or department that has access to the Client for operational issues. Phone. Enter a voice phone for the contact person. Address. Use the two fields for a geographical address. This may be the address where the Client resides, for the contact person, or for the Client operator. City/State. Enter the city name and state (region or province) name. Zip. Enter the zip code or postal code. Click Next to continue.

18 18 RemoteWare OS/2 Client User s Guide Configuring communications settings The Client installation program displays one or more windows to assist you in configuring communication setup parameters. The way the System Administrator has defined the Client at the Server determines the order and number of protocol tab(s) displayed. TCP/IP settings A Client set up to use the TCP/IP network protocol displays the TCP/IP Settings window during installation. Verify and adjust these values as necessary. Server Address. Displays the address used by the Client to contact the RemoteWare Server. This field may be blank if only the Server initiates an outbound connection to the Client. You cannot change this entry. Client Address. Defines the TCP/IP address the RemoteWare Server uses to contact the Client during an outbound session. Contact the Server Administrator if you need help completing this field. Click the ASYNC tab to complete the Async settings or click OK to move to the Client Registration window.

19 CHAPTER 1 / Installation 19 Async settings A Client set up to use the asynchronous (ASYNC) protocol displays the ASYNC Settings window during installation. Verify and adjust these values as necessary. Server Phone#. This is the number used by the Client to contact the RemoteWare Server. It may be blank if the Server Administrator intends to only place outbound calls to the Client. Verify the number, and add any calling prefixes (for example, 1 for long distance), area or country codes necessary to contact the Server. Client Phone#. This is the number used by the RemoteWare Server to contact the Client. It may be left blank if the Server Administrator intends for the Server to only place outbound calls to the Server. Otherwise, verify the number. Modem Type. Displays the modem descriptions that have been predefined at the RemoteWare Server. If the visible choice is not correct, click the down arrow to scan the list for a better choice. Contact your Server Administrator if you cannot determine which choice is appropriate. Port Device. Lists the hardware serial port to use for the modem. Choices may be from COM1 to COM20. If you are not certain of this value, see Auto detect option on page 20.. Data Rate. Displays the modem s transfer speed in bits per second (bps). Data rate options can range from 1200 to bps. If you are not certain of the correct data rate, see see Auto detect option on page 20.

20 20 RemoteWare OS/2 Client User s Guide Auto detect option OINSTALL includes a feature to detect what serial ports are available on the RemoteWare Client computer and whether a modem is connected and available. This utility also determines the modem s maximum data rate, and presents you with a list of results. You can choose from the results list to set the Port Device and Data Rate fields. To use the Auto Detect utility, verify that the modem is powered on and connected to the serial port. Then click the Auto Detect button. Auto detect searches for available communication ports, and then for any modems attached to the ports. A window displays each port on a separate line: For each port it displays the following information: Direct Connect. Auto detect found a serial port, but was not able to detect any modems. This port could be used as a direct connect Client, where the Client connects to the RemoteWare Server via a null modem cable. However, this is impractical unless the Client is in close proximity to the RemoteWare Server. Note: If all your COM port choices indicate direct connect and a modem is connected to the computer, verify the following and rerun Auto Detect: the modem is plugged in and powered on, it is connected to the serial (not parallel) port, the cable is functioning properly, appropriate software drivers are loaded and available for the modem(s), and other programs are not currently using the modem. You can use a standard terminal program to troubleshoot several of the items above. Modem at nnnnn bps. The serial port detected an active modem that can operate at this maximum data rate. Select a choice and click OK to set the Port and Data Rate. Click Cancel to end Auto Detect and leave the settings as they were.

21 CHAPTER 1 / Installation 21 Registering the Template Client To complete the Template Client installation you must perform the registration connection to the RemoteWare Server. If you choose not to connect at this point, the installation will not be complete and you will have to complete the install program again. To register the Template Client: 1 At the Client Registration window, select a resource to use to connect to the Server. 2 Click Connect. OINSTALL attempts to connect to the RemoteWare Server and register the Client. If successful, the Client can now communicate with the Server as a regular Client. Installation and registration is complete. If the registration is unsuccessful, you can retry the session now by clicking Connect, or select another resource and try again. Note: A Template Client is not registered at the RemoteWare Server until a successful communication session occurs and the Server Administrator verifies the new Client. An unregistered Client cannot perform any data or file transferfunctions until it has successfully sent the registration information to the RemoteWare Server. A message is displayed when the installation is finished. 3 Click OK to close the message. 4 Reboot the computer.

22 22 RemoteWare OS/2 Client User s Guide Installing a text-mode Client The Server Administrator may have provided you with a set of installation disks or files containing a text-mode Client. The text-mode Client program runs in an OS/2 system window with a text-mode user interface or an OS/2 system where the Presentation Manager is not installed. You install the Client software using the OTINSTAL program. This program is available on the disk containing the Client installation kit, or in a specified directory if the files are on a network. To install the text-mode Client software: 1 Open an OS/2 command prompt. 2 To install the software from a disk, insert the installation disk in the computer s disk drive and change the current drive to the appropriate disk drive letter. To install the software from the network, change to the appropriate disk drive letter. 3 Enter the following command at the prompt: OTINSTAL The RemoteWare Client Installation window is displayed: 4 Verify the Source Drive, then press [Enter]. 5 Set the drive on which to install the Client.

23 CHAPTER 1 / Installation 23 6 Press [Enter]. 7 The installation prompts you to confirm the command. Yes. Continues the installation to the specified drive and directory. No. Remains at the initial window, allowing you to change the installation settings. 8 The program prompts you to set the appropriate time zone. Use the up and down arrow keys to select the time zone. 9 When the time zone is set, press [Enter]. The installation program creates the necessary directories on the Client and copies all the necessary files into those directories. 10 The program prompts you to modify the startup.cmd and config.sys files:

24 24 RemoteWare OS/2 Client User s Guide n Change the x: in the examples to the drive letter for the Client software. Yes. Adds the \nodesys directory to your libpath and set path statements and sets the Client drive variable in the config.sys file. The following lines are added to the startup.cmd file: x: CD "nodesys" IF EXIST "\nodesys\updates\*.*" COPY "\nodesys\updates\*.*" "\nodesys" NUL DEL /N "\nodesys\updates\*.*" >NUL START /N /FS OS2NODE Your config.sys statements should be similar to the following: LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;x:\NODESYS; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS;x:\NODESYS SET XNODE_DISK=x: TZ=XDT5 No. Makes no changes to the files. Note: If the time zone variable is not set, Client Electronic Software Distribution (ESD) may not function correctly. Change Drive. Allows you to select the drive where the files to be modified reside. 11 Press [Enter]. A message is displayed once the files have been changed. If you chose not to have the files changed, the program continues. A message is displayed when the installation is finished. 12 Press [Enter] to exit the installation program. 13 Reboot the computer.

25 CHAPTER 1 / Installation 25 Installing a text-mode Template Client The Server Administrator may have provided you with a set of installation disks or files containing a Template Client. A Template Client allows your administrator to easily configure large quantities of Clients and allows you to adjust specific settings during installation. The Template Client becomes a regular RemoteWare Client after installation and registration are complete. You install the Client software using the OTINSTAL program. This program is available on the disk containing the Client installation kit, or in a specified directory if the files are on a network. To install the text-mode Template Client software: 1 Open an OS/2 command prompt. 2 To install the software from a disk, insert the installation disk in the computer s disk drive and change the current drive to the appropriate disk drive letter. To install the software from the network, change to the appropriate disk drive letter. 3 Enter the following command at the prompt: OTINSTAL The RemoteWare Client Installation window is displayed: 4 Verify the Source Drive, then press [Enter].

26 26 RemoteWare OS/2 Client User s Guide 5 Set the drive on which to install the Client. 6 Press [Enter]. 7 The installation prompts you to confirm the command. Yes. Continues the installation to the specified drive and directory. No. Remains at the initial window, allowing you to change the installation settings. 8 The program prompts you to set the appropriate time zone. Use the up and down arrow keys to select the time zone. 9 When the time zone is set, press [Enter]. The installation program creates the necessary directories on the Client and copies all the necessary files into those directories. 10 The program prompts you to modify the startup.cmd and config.sys files:

27 CHAPTER 1 / Installation 27 n Change the x: in the examples to the drive letter for the Client software. Yes. Adds the \nodesys directory to your libpath and set path statements and sets the Client drive variable in the config.sys file. The following lines are added to the startup.cmd file: x: CD "nodesys" IF EXIST "\nodesys\updates\*.*" COPY "\nodesys\updates\*.*" "\nodesys" NUL DEL /N "\nodesys\updates\*.*" >NUL START /N /FS OS2NODE Your config.sys statements should be similar to the following: LIBPATH=.;D:\OS2\DLL;D:\OS2\MDOS;D:\;x:\NODESYS; SET PATH=D:\OS2;D:\OS2\SYSTEM;D:\OS2\MDOS;x:\NODESYS SET XNODE_DISK=x: TZ=XDT5 No. Makes no changes to the files. Note: If the time zone variable is not set, Client Electronic Software Distribution (ESD) may not function correctly. Change Drive. Allows you to select the drive where the files to be modified reside. 11 Press [Enter]. A message is displayed once the files have been changed. If you chose not to have the files changed, the program continues. 12 The program displays the Template Client Registration window.

28 28 RemoteWare OS/2 Client User s Guide 13 Enter the information requested for each item and press [Enter]. Press [Enter] to bypass a field and display the next field. If the information is required, you cannot bypass that field. If you are not certain what values to enter, contact your Server Administrator or enter what you believe is appropriate information. Most of these values can be changed later. The following information may be requested: Preferred Client Name. (This field might not be present.) Type the Client name as given to you by the Server Administrator or supply your own Client name (up to 8 characters). Entering a name that already exists at the Server may cause the Client registration to fail. Description. Enter up to 22 characters. This description tells the Server Administrator the location or function of this Client. Server Serial Number. Enter the serial number provided by the RemoteWare Server Administrator. Registration Key. Enter the registration key provided by the Server Administrator. (This field is defined by the Administrator.) Server Phone#. (ASYNC Clients). This is the number used by the Client to contact the RemoteWare Server. It may be blank if the Server Administrator intends to only place outbound calls to the Client. Verify the number, and add any calling prefixes (for example, 1 for long distance), area or country codes necessary to contact the Server. Client Phone#. (ASYNC Clients). This is the number used by the RemoteWare Server to contact the Client. It may be left blank if the Server Administrator intends for the Server to only place outbound calls to the Server. Otherwise, verify the number. Port. (ASYNC Clients). This is the hardware serial port to use for the modem. Choices may be from COM1 to COM20. Use the up and down arrow keys to set this field. Data Rate. (ASYNC Clients). Displays the modem s transfer speed in bits per second (bps). Data rate options can range from 1200 to bps. You can use the up and down arrow keys to set this field. Server Address #. (TCP/IP Clients). Displays the address used by the Client to contact the RemoteWare Server. This field may be blank if only the Server initiates an outbound connection to the Client. You cannot change this entry. Client Address #. (TCP/IP Clients). Defines the TCP/IP address the RemoteWare Server uses to contact the Client during an outbound session. Contact the Server Administrator if you need help completing this field. Primary Contact Name. Provide a name or department that has access to the Client for operational issues.

29 CHAPTER 1 / Installation 29 Primary Contact Phone. Enter a voice phone for the contact person. Secondary Contact Name. Provide a second name or department that has access to the Client for operational issues. Secondary Contact Phone. Enter a voice phone for the second contact person. 14 Once you have entered all of the information, a prompt asks if you want to change anything. 15 Press [Enter] to continue the installation program. Enter [Y] and press [Enter] to change any of the fields. 16 You are prompted to save the registration information. Press [Y] to save the data. Press [Enter] to save the information and continue. Enter [N] and press [Enter] to discard the information. The Client software is installed; however, the Client will not be viable until the information is saved and the Client is registered. 17 When the information is saved, you are prompted to register the Client.

30 30 RemoteWare OS/2 Client User s Guide Press [Enter] to attempt a connection to the Server. Enter [N] and press [Enter] to bypass registration. Note: A Template Client is not registered at the RemoteWare Server until a successful communication session occurs and the Server Administrator verifies the new Client. An unregistered Client cannot perform any data or file transfer functions until it has successfully sent the registration information to the RemoteWare Server. 18 A message indicates whether the registration was successful. Press [Enter] to continue. Another message is displayed when the installation is finished. 19 Press [Enter] to exit the installation program. 20 Reboot the computer.

31 Chapter X: Chapter Title <-- Apply chapter hidden style CHAPTER 2 2 Using the Client software The RemoteWare OS/2 Client consists of two applications that allow the computer to exchange files, messages, and information with a central RemoteWare Server. This chapter includes: RemoteWare Client applications Functions available from the Client user interface Communicating automatically with OS2AUTO Using the OS2TCOMM communications application for text-based operation

32 32 RemoteWare OS/2 Client User s Guide RemoteWare Client at a glance The RemoteWare OS/2 Client consists of four applications as described in the following table. Table 2. Client applications Icon Main window Program Name Common Name Description OS2COMM.EXE Client Communications None None OS2NODE.EXE Communications Kernel This application is the user interface you can use to set up, control, or monitor communications with the Server. OS2COMM depends on OS2NODE (described below) for access to communication resources. OS2COMM does not need to be active for communication to occur with the Server. This application enables the Client to communicate with the Server. It has no user interface. The program may be installed so that it is loaded when OS/2 starts. OS2NODE is automatically loaded when OS2COMM is started. It can also be loaded from a command line. None None OS2AUTO.EXE Auto Communications OS2TCOMM.EXE Text-mode Client Communications This application allows the Client to initiate an Auto Communications unattended inbound session with the Server using predefined settings. OS2AUTO is useful for Clients that must operate with little or no operator intervention, or for systems that want to start the connection from a batch file, command line or other application. This application is the text-mode user interface you use to set up, control, or monitor communications with the Server. It depends on OS2TNODE (described below) for access to communication resources. OS2TCOMM does not need to be active for communication to occur with the Server. None None OS2TNODE.EXE Communications Kernel This application enables the text-mode Client to communicate with the Server. It has no user interface. The program may be installed so that it is loaded when OS/2 starts. OS2TNODE is automatically loaded when OS2TCOMM is started. It does not interact with the OS/2 Presentation Manager and can be loaded from a command line.

33 CHAPTER 2 / Using the Client software 33 Starting the communications kernel The executable file os2node.exe controls the Client s communications with the RemoteWare Server, and it MUST be running before the Client can communicate with the RemoteWare Server. If the installation program made changes to your Client s startup files, os2node.exe is loaded automatically when the Client computer is rebooted and will run in the background until it is removed. It will also be loaded and unloaded with OS2COMM. In addition, you can load the program from a command line. To load the Communications Kernel from a command line: 1 Access an OS/2 prompt and make sure that the current directory is <install directory>\nodesys. 2 Enter the command: START OS2NODE [-i] [-d] [-r] [-c<command>] The following table lists the optional parameters. Table 3. OS2NODE optional parameters Parameter Description -i Reintializes the modem. -d Starts a connection to the Server using the currently defined default resource. -r Removes the program from memory. -c<command> Starts the Client software and loads a program instead of the command interpreter. Specify the correct path and file name. For example, OS2NODE -cos2comm loads the Communications Kernel and starts the Communications Client. Notes:If OS2NODE is loaded with the command line, it must be unloaded with the command line that includes the -r parameter or with the Command Unload Client command in the Client Communications program. To run OS2NODE without Presentation Manager, you must start the kernel using the Detach OS2NODE command. To run the text-mode Client software (OS2TCOMM), load OS2TNODE instead of OS2NODE.

34 34 RemoteWare OS/2 Client User s Guide Starting Client communications You can start Client Communications by double-clicking its icon or you can start it from a command prompt. Table 4 lists the methods for starting the Client. Table 4. Starting the Client To Start the Client from its icon Start the Client from the command line Do this Double click the Client Communications icon in the RemoteWare program group. Access an OS/2 command prompt and enter the command: START OS2COMM After the Client user interface appears, it starts the Communications Kernel, OS2NODE, if it has not been previously loaded. The Client Communications application provides communication capabilities in the OS/2 environment. It allows you to initiate a connection to the Server, schedule an unattended session, view the Communications Log, edit the Client s setup, and more.

35 CHAPTER 2 / Using the Client software 35 Client user interface This section provides an overview of the major components in the Client Communications window, such as menus, buttons, and the status bar. The main window Starting Client Communications displays a window containing the menus, buttons, and current Client status. The illustration shows each part of the Client window. Menus and buttons The menu bar contains access to every Client function and command. The Buttons at the top of the window are available for quick access to commonly used commands. You can also access every button function from the menus. Move the mouse over a button to obtain a short description of the button's function in the lower-left corner of the window. The menu bar items and buttons are always available from the mouse or keyboard. To access them from the keyboard, press the [Alt] key and the underlined letter for that menu item. The following table lists the button and menu commands and gives a brief description of each.

36 36 RemoteWare OS/2 Client User s Guide Table 5. Client Communications menu commands Button Command Description File Setup... File Schedule... File View Log... Displays the connection parameters currently being used by the Client. The Client password may also be changed from this command. Opens the Schedule Connection window, which allows the Client user to start, modify, or stop a scheduled inbound call to the Server at a specific time. Displays the Communications Log. File Dialing Directory... File Exit Command Connect Shows the Dialing Directory, and allows the Client user to add, modify, or delete entries, settings, and tasks. Closes the Client Communications window. Also stops the OS2NODE application if the Client started the program and the Client is not currently connected to the Server. Initiates an inbound connection to the Server. This command toggles with the Cancel command. Command Cancel Command Reinitialize Command View Alerts... Command Unload Client Command Load Client Help Help for OS2COMM Aborts a connection in progress. This command toggles with the Connect command. Transmits the reinitialization commands to the modem or network device. Not available when a connection is in progress. Displays more information about any errors or events. The alerts also appear as icons in the right bottom portion of the status bar. See Table 6, Alert conditions, on page 37 for a list of alert icons and their functions. Removes the OS2NODE program from memory. The Client cannot transmit or receive unless this program is running. Starts the OS2NODE program. The Client requires this program to communicate with the Server. Displays the list of help topics. Help About OS2COMM Displays the About box, listing the application name, version, manufacturer, and copyrights.

37 CHAPTER 2 / Using the Client software 37 Status bar The status bar at the bottom of the Client Communications window provides information about your current resources and status. Default Dialing Directory entry Current resource in use Brief help description Client alert icons n For more details on alert icons, see Viewing the alerts on page 56. The status bar is split into four panes, each containing specific information: Default Directory. The top left pane in the status bar displays the Dialing Directory entry currently selected and used when the Client connects. Help overview. The bottom left pane continuously provides a brief description of each item as you move the cursor over a button or menu item. Current resource. The top right pane shows which communications resource is currently loaded. Alert icons. The bottom right displays the alert icons to indicate an event significant to the Client environment. Select one or more of the icons listed in the following table for specific information on the alert. Table 6. Alert conditions Alert icon Alert name Description Resource error ESD Arrived AA Disabled ESD Disabled The Client has detected a problem with the current resource. The Transport Error window explains what has happened. New files exist in the \updates directory. See Appendix A for more information. The modem s Auto Answer feature has been turned off by the Client user. The Server cannot place outbound calls to the Client until Auto Answer is enabled. Auto Answer may be disabled for inbound only Clients, or when the user might need to answer an incoming voice call on the same phone line. The Client cannot receive updated applications because the Client has disabled Electronic Software Distribution. This option is useful when the Client user may not have time for a lengthy download.

38 38 RemoteWare OS/2 Client User s Guide Connecting with the Server To contact the Server from the Client, select Command Connect or click the Connect button. This action starts an inbound connection to the Server using the default Dialing Directory entry. A bar between the representation of the Client and the Server shows that a connection is being attempted. To cancel the dialing, select Command Cancel Connection or click the Cancel button. Once a connection is made, the window displays the activity between the Server and the Client above and below the bar. File transfers display a progress indicator to show how much data has been exchanged and the direction of the file transfer. This transfer is receiving Server data. This transfer is sending Client data to the Server.

39 CHAPTER 2 / Using the Client software 39 Connecting using another Dialing Directory entry The Connect command uses the default setting in the Dialing Directory listing. To connect using another setting, move the mouse pointer over the Connect button and click the right mouse button. The Connect menu window appears. n For more information about the default setting, see Using the Dialing Directory on page 40. Select the Dialing Directory entry to use. The Client initializes the resource and initiates the connection. The selected resource becomes the default setting in the Dialing Directory listing.

40 40 RemoteWare OS/2 Client User s Guide Using the Dialing Directory The Client Dialing Directory allows you to customize the connection options available to connect to the Server. You can edit phone numbers and network addresses, set protocol parameters, define which tasks to complete, and disable ESD and Auto Answer. To display the Dialing Directory, select File Dialing Directory... or click the Directory button. The Dialing Directory window displays the Default Entry, followed by a list box containing available resources and settings. Descriptions followed by an asterisk * are those defined by the Server Administrator. Administrator defined entries cannot be deleted or directly modified, but they can be copied and then modified. Connecting using the directory To initiate an inbound connection using one of the entries in the directory, highlight the desired entry and select the Connect button. From the main Client Communications window, you can also click the right mouse button on the Connect button and choose the entry to use to start a connection with that entry. For more information, see Connecting using another Dialing Directory entry on page 39.

41 CHAPTER 2 / Using the Client software 41 Setting a default entry The Client uses the default entry settings whenever the Connect command is executed. To set a default from the Dialing Directory window, highlight the entry to use as the default and select Command Set Default. To set a default entry from the main Client Communications window, place the mouse pointer over the Directory button and click the right mouse button. The Set Default menu window allows you to select which default entry to use for a connection. Creating new entries To add entries to the directory, you can create new entries, or copy and modify existing entries. To create a new entry, choose File New at the Dialing Directory window. To copy and modify an existing entry, highlight the entry to copy in the Dialing Directory window, then select File Copy.

42 42 RemoteWare OS/2 Client User s Guide The Modify Dialing Directory Entry window is displayed. Complete the following for the entry: Description. Enter up to 50 characters describing the resource. The Client displays entries in alphabetical order based on the description. Phone Number or TCP/IP address. This field changes labels depending on the selected Resource value. Enter a phone number or network address for the resource. The Client does not verify the validity of this field; invalid fields for the resource will cause the connection to fail.

43 CHAPTER 2 / Using the Client software 43 Resource. Lists the available resources for this Client. The Resource determines the communication transport (ASYNC or TCP/IP) the Client will use to connect to the Server. Some resources may be listed more than once depending on how the Server Administrator defined the Client. Note: A resource type must appear in this field in order for the Client to use it. For example, a Client may not use or create a TCP/IP entry if the administrator has not defined at least one TCP/IP resource and assigned it to the Client. Disable Electronic Software Distribution. When this option is enabled and this dialing directory entry is being used, the Client does not receive any files that are part of the software distribution tasks. Use this option to prevent a potentially lengthy file download from taking place when time is of the essence or to allow such transfers to occur during off-peak hours. Disable Auto Answer. Check this option to prevent the modem from answering an incoming call. Disabling the Auto Answer function is helpful when the modem shares the phone line with a telephone or fax device, or when the Client always initiates inbound connections to the Server. System. If your Server Administrator has set up the Client to connect with more than one RemoteWare Server, then there will be a list of Servers in the drop down menu. Choose which Server this resource contacts when starting a connection. For example, you might choose #1 to connect to the Server at the main office to collect sales data and select #2 to connect to the Server at the plant to retrieve inventory files. Selected Tasks for Connection. This list shows the items that are assigned to the Client. All highlighted items will be executed during a communications session. To deselect items, click on the ones that you do not want to run. Use the Default button to return the list to the default state as defined by the System Administrator. Note that this selection affects only sessions initiated by the Client. If the Server initiates the session, then the selections made here are ignored. Note: Some tasks that are not in the list may execute during an inbound session. These tasks cannot be disabled because they have been defined as required by the Server Administrator. In addition, outbound connections from the Server process all tasks, regardless of their setting in this list box. Show tasks during connection. Check this option to display the name of the task about to be carried out in the main window. The task name appears in between file transfers. When you have defined the entry, click OK.

44 44 RemoteWare OS/2 Client User s Guide Modifying a directory entry Use the Modify Dialing Directory Entry window to change an item to meet your connection needs. You can change any entry that is not an administrator defined entry (designated with an asterisk * after the description name). To modify an existing entry: Double click an entry in the Dialing Directory window. Highlight an entry in the Dialing Directory window and select File Edit. Highlight an entry in the Dialing Directory window and click the Edit button. The Modify Dialing Directory Entry window is displayed. Complete the following for the entry: Description. Enter up to 50 characters describing the resource. The Client places entries in alphabetical order based on the description. Phone Number or TCP/IP address. This field changes labels depending on the selected Resource value. Enter a phone number or network address for the resource. The Client does not verify the validity of this field; invalid fields for the resource will cause the connection to fail.

45 CHAPTER 2 / Using the Client software 45 Resource. Lists the available resources for this Client. The Resource determines the communication transport (ASYNC or TCP/IP) the Client will use to connect to the Server. Some resources may be listed more than once depending on how the Server Administrator defined the Client. Note: A resource type must appear in this field in order for the Client to use it. For example, a Client may not use or create a TCP/IP entry if the administrator has not defined at least one TCP/IP resource and assigned it to the Client. Disable Electronic Software Distribution. When this option is enabled and this dialing directory entry is being used, the Client does not receive any files that are part of the software distribution tasks. Use this option to prevent a potentially lengthy file download from taking place when time is of the essence or to allow such transfers to occur during off-peak hours. Disable Auto Answer. Check this option to prevent the modem from answering an incoming call. Disabling the Auto Answer function is helpful when the modem shares the phone line with a telephone or fax device, or when the Client always initiates inbound connections to the Server. System. If your Server Administrator has set up the Client to connect with more than one RemoteWare Server, then there will be a list of Servers in the drop down menu. Choose which Server this resource contacts when starting a connection. For example, you might choose #1 to connect to the Server at the main office to collect sales data and select #2 to connect to the Server at the plant to retrieve inventory files. Selected Tasks for Connection. This list shows the items that are assigned to the Client. All highlighted items will be executed during a communications session. To deselect items, click on the ones that you do not want to run. Use the Default button to return the list to the default state as defined by the System Administrator. Note that this selection affects only sessions initiated by the Client. If the Server initiates the session, then the selections made here are ignored. Note: Some tasks that are not in the list may execute during an inbound session. These tasks cannot be disabled because they have been defined as required by the Server Administrator. In addition, outbound connections from the Server process all tasks, regardless of their setting in this list box. Show tasks during connection. Check this option to display the task name about to be executed in the main window. The task name appears in between file transfers. When you have made the desired changes, click OK.

46 46 RemoteWare OS/2 Client User s Guide Setting up the Client A Client s password is one level of security that permits a connection with specific Servers. The password and other current connection information are available from the Client Setup window. Select File Setup... or click the Setup button to view this window. This window appears when the current resource is asynchronous. This window appears when the current resource is TCP/IP. You may change the Client Password at this window, if you are currently using an asynchronous resource to connect to the Server, you can change the setup, the data rate, and the port device for the modem.

47 CHAPTER 2 / Using the Client software 47 Changing the password The Server uses the Client password to recognize a valid Client of the system. Do not change this password without being directed to do so by your Server Administrator. Change the Client s password only if the same change occurs at the Server. The wrong password will prevent the Client from connecting. To change the Client password: 1 Select File Setup... or click the Setup button. 2 The Client Setup displays the current password. Type the new password in the Password field. The password may be from 1 to 10 characters. 3 Click OK to accept the new password. Changing the modem setup You can also change settings for the Client modem. To change the Client modem setup: 1 Click the Modem Type button. The Edit Modem Type window is displayed:

48 48 RemoteWare OS/2 Client User s Guide 2 Make the necessary changes to these fields in the window: Name. Displays the current name for the modem (you cannot change this). Modem Init. Use up to 60 characters to set up operating conditions for dialing and listening. Often this string is used to set up operating conditions, or to set result codes, set DTR response, turn echo on or off, turn the speaker on or off, etc. See your modem manual for details on its commands and the operating capabilities they enable or disable. Note: For the following fields that require character strings, an exclamation mark! must always be used at the end of the line to specify a carriage return. Auto Answer. Use up to 60 characters to specify conditions for letting the modem answer incoming calls. See your modem manual for details on the standard formats which usually include enabling the auto answer function, setting the number of rings before a connection, and other answering options. No Answer. Use up to 60 characters to specify conditions to not answer incoming calls. The Client sends this string to the modem after a connection has ended. See your modem manual for details on which command should be sent for this process. Modem Dial. Use up to 9 characters to define the AT command that is used to dial the number. This string is prepended to the phone number and generally instructs the modem to use pulse (ATDP) or tone (ATDT) dialing. See your modem manual for details on valid dialing commands and dial modifiers. Modem Escape. Use up to 9 characters for the code that places the modem into the command state before hanging up. When the modem is communicating, it passes any characters it receives directly to the other modem. When it recognizes this escape code, however, it becomes ready to respond to commands the program sends to it. If your modem uses a nonstandard escape code, you can edit this field to specify it. Typically, +++ is used as the modem escape code. Modem Hang Up. Up to 9 characters can be used to instruct the modem to terminate the connection. See your modem manual for details on valid commands. Modem Flow Control. Select this checkbox to enable hardware flow control between the Client and the modem. Hardware flow control allows the Client to transmit at the highest possible data speed, automatically adjusting for conditions such as line quality, busy destinations, and modem limitations. Note: Enabling Modem Flow Control is recommended.

49 CHAPTER 2 / Using the Client software 49 Result Codes. Displays the numerical result code returned from the modem and its meaning. Result codes are a modem s response to Client commands. During a connection, the Client expects to receive numeric result codes from the modem. Use this field and the New Result Code field to assign a new result definition to a number so that the Client interprets the number correctly during a connection. To change the number for a result code, select the entry you wish to change from the drop down menu. Use the spin buttons to change the New Result Code value to the correct numeric result code. New Result Code. Displays the result code that matches the Result Codes field. Use this field when you wish to change the number for the current result code. Max Data Rate. Select the bits per second (from 1200 to 57600) that defines the upper data transfer limit for the modem. Modem Delay. Specifies how long in milliseconds the Client pauses before sending the next command to the modem. With older modems, you might need to increase this value to allow more time for the modem to process commands. Modem Timeout. Determines how long the program waits for the presence of a carrier signal during a connection attempt. The modem stops the attempt if a carrier signal from the remote modem is not recognized during this number of seconds. Increase this value higher if your modem frequently fails to recognize the remote modem s carrier signal in time to set up a connection. This value should match the S7 register set in the Modem Init string. The S7 register tells the modem how long to wait for carrier detect. 3 Click OK to close the window and save any change you have made. Note: Any changes will be overwritten by what is defined on the Server if ESD is enabled.

50 50 RemoteWare OS/2 Client User s Guide Changing the data rate The Data Rate defines the data transfer rate for the currently selected modem. Normally, this value equals the maximum data rate for the modem. Data rates may be from 1200 to bits per second. To change the modem s data rate, select the down-arrow next to Data Rate and select the desired data rate. Changing the port device The modem port device refers to the communications port on the Client computer to which your modem is connected. Select the down-arrow next to Port Device and select the one to which your modem is connected.

51 CHAPTER 2 / Using the Client software 51 Setting up connection schedules Use the Client scheduler to set a time for the Client to contact the Server. Once active, the Client can initiate an inbound connection to the Server at a fixed time. The schedule you set is only run once. You must then reset it. The schedule is useful for unattended Client operation. For example, if you needed to retrieve a report generated on the Server after your regular working hours, you could schedule an unattended connection to begin at midnight. To do this, you would set the connection time for 00:00 and leave the Client computer on for the night. Note: The schedule cannot be modified if the Server Administrator has set it from the Server. The connection occurs at the scheduled time unless the Client software is not running or it cannot access the connection hardware. To set a time for a connection to start: 1 Choose File Schedule or click the Schedule button. 2 Check the Enable Scheduled Connection check box to activate the scheduler. Note: If every control on the Schedule Connection window is disabled, then the Server has set the Client s schedule. It is not possible for a Client to modify a schedule set at the Server. Contact your Server Administrator to adjust the schedule. 3 The Connection Time button displays the current starting time for the schedule. Click the Connection Time button to change the time. 4 The Set Connection Time window allows you to change the schedule. The time is set in 24-hour format. Remember to properly represent afternoon times, such as 14:52 for 2:52 PM. 5 Select OK to exit the Set Connection Time window. 6 Check the Enable Retries checkbox to permit the Client to retry the connection should the first attempt fail. When enabled, the Client

52 52 RemoteWare OS/2 Client User s Guide attempts to contact the Server a maximum of three (3) times 5 minutes apart before logging the attempt as unsuccessful. 7 Select OK to exit the Schedule Connection window. The schedule is not saved when you exit Client Communications. Note: If you try to exit Client Communications and a schedule is active, the Client displays the message Schedule is active. Deactivating the schedule There are two different scenarios and procedures for deactivating the schedule: Schedule set by the Client. Click the Setup button or choose File Setup. If the controls in the Schedule Connection window are active, then uncheck the Enable Scheduled Connection checkbox. The schedule is disabled. Schedule set by the Server. If the Schedule Connection window will not allow you to uncheck the Enable Scheduled Connection checkbox, then your schedule has been activated from the Server. The Server Administrator can disable the schedule from the Server, thereby returning control to the Client. The Client user can also exit Client Communications to temporarily delay the schedule. If the scheduled time arrives and Client Communications or OS2NODE is not running, the Client will not attempt to place an inbound connection to the Server. Viewing the communications log Each time the Client attempts to communicate with the RemoteWare Server, the Communications Log records the following information: Start Time. Lists the date and time when the connection was initiated or accepted from the Server. Duration. Displays the minutes and seconds elapsed from the Start Time to disconnection. Origin. Indicates whether the Client or Server initiated the connection. Status. Displays the outcome of the connection. Possible status values appear in the following table.

53 CHAPTER 2 / Using the Client software 53 Table 7. Client connection status Status Aborted Busy Signal Client disabled Client undefined Connect cancelled Invalid Password Lost Connection Modem error No answer No carrier No dialtone No status Resource error Scheduler off Server down Description The Client or Server requested an unexpected interruption in the connection. The Client could not contact the Server because the resource at the Server end was occupied. Try again later or contact the Server Administrator if the issue persists. The Server has disabled the Client. A connection to this Server is not allowed until the Server Administrator enables the Client. There is no Client by this name on the Server. The Client may have been deleted. Contact your Server Administrator. A request to stop the connection was issued by the Server or the Client during the connection phase (before the connection was complete). The password or security token at the Server and the Client do not match. Contact your Server Administrator to reset security or verify the password for this Client. An unexpected interruption in the connection occurred through no action by the Client or the Server. Retry the connection; if situation repeats contact your Server Administrator. The modem did not return a successful result code in response to a command. Check the modem cabling, restart the modem, and reinitialize the modem. The Server did not respond when the Client initiated a connection. Verify that the number or address is correct. The Server s modem answered the line, but no carrier signal was detected. Verify that the phone number is correct, the necessary prefixes or suffixes are supplied, and the Server modem is functional. Manually place the call to determine if the Server is answering and providing a carrier signal. The Client s modem does not detect a dial tone when it uses the phone line. Verify that the phone line is plugged into the correct modem socket, that a phone receiver can detect the dial tone, and that no other tones (such as a message or call waiting beep) occurs when the line is picked up. The Client could not assign a status to this connection. The Client received or detected an unexpected condition while using a network resource. Verify the correct network address, network access software, and correct network access protocols. The Server is operational but cannot process the tasks in a session because the Scheduler application is currently disabled. Try again later or contact the Server Administrator. The Server cannot accept the connection because it is not currently running. Try again later or contact the Server Administrator.

54 54 RemoteWare OS/2 Client User s Guide Table 7. Client connection status Status Server suspended Successful Time out Undefined Description The Server cannot accept connections because the Server Administrator has temporarily interrupted its operation. Try again later or contact the Server Administrator. The connection experienced no errors. A connection was stopped by the Client because the Server did not respond in a reasonable amount of time. An error occurred that did not match any of the defined status types. To view the log: 1 Select File View Log or click the View Log button.

55 CHAPTER 2 / Using the Client software 55 2 Double click an entry or highlight the entry and click the Detail button to view detailed information on the connection attempt. The Communications Log Detail contains session and resource information that explains the status and may help you troubleshoot a Client. 3 Use the Previous and Next buttons to view details about the other entries in the log. Click OK to return to the main log screen. 4 Click the Close button when you are finished viewing the log.

56 56 RemoteWare OS/2 Client User s Guide Viewing the alerts Icons in the lower right corner of the screen indicate significant events that involve the Client. These alert icons let the user know whether auto answer is enabled, ESD is enabled, if ESD files have been received, or if a transport error has occurred. Clicking the alert icon or using Commands View Alerts menu displays more information about the alert. Resource error The Client displays the Resource error alert icon ( ) when it believes that the current resource is no longer suitable for reliable communications. This may occur because of a modem or network interruption, power disruption, incorrect settings or network address, or contention for the resource from another application. The Transport Error window displays information about the resource, any information returned from the resource, and an interpretation of the error by the Client.

57 CHAPTER 2 / Using the Client software 57 ESD arrived The ESD Arrived alert icon ( \nodesys\updates directory. ) appears when files are detected in the Electronic Software Distribution is a Server feature that transfers the latest files from the Server to the Clients. The Server only sends the files when the Client does not possess the latest version. In addition, the Server automatically resends files that may have been inadvertently altered, moved, or deleted. This feature is valuable when the latest data is required or portions of the Client are deleted accidentally. The ESD files window lists the executables and DLLs in the \nodesys\updates directory. This is the default directory for RemoteWare Client software. These files are automatically copied if your startup.cmd file was modified during installation. If it was not, you may want to move these files into the \nodesys directory when the Client software is not running. AA Disabled Auto Answer is a modem function that picks up the line when the modem detects a ring signal. This feature is required for Clients accepting outbound calls from Servers. However, Auto Answer may be inconvenient when the phone line is shared with voice callers, fax machines, and other computers. The Auto Answer alert icon ( ) indicates that this Client cannot accept an incoming call. To accept incoming calls, remove the check mark in the Disable Auto Answer checkbox in the Modify Dialing Directory Entry - Async window. For more information, see Using the Dialing Directory on page 40.

58 58 RemoteWare OS/2 Client User s Guide ESD Disabled The ESD Disabled alert icon ( ) appears when the Client user has disabled ESD. (For a description of ESD, see ESD arrived on page 57.) It is possible to disable the ESD function by checking the Disable Electronic Software Distribution checkbox on the Modify Dialing Directory Entry window. Disable ESD to control when files are updated. This may be helpful to limit the amount of time needed for a connection, or to permit the Client to receive ESD at off-peak hours. It is also helpful when you want to only receive certain tasks without the risk of a lengthy file transfer. Reinitializing the modem Selecting Command Reinitialize sends the Auto Answer or the No Answer command string to the modem. It also sends the Modem Init string to the modem. Use this option if you have problems communicating with the modem at the Client, or when the Resource Error alert icon appears while using an asynchronous resource. Unloading the Client If Client Communications loaded the OS2NODE program at startup, then Client Communications stops OS2NODE when you exit the application. If OS2NODE was running before you started Client Communications, it will remain resident in memory after you exit the program. To unload OS2NODE without closing Client Communications, select Command Unload Client. To reload the OS2NODE program, select Command Load Client. Exiting Client communications When you have finished using Client Communications, select File Exit or click the Exit button.

59 CHAPTER 2 / Using the Client software 59 Communicating automatically with OS2AUTO OS2AUTO allows you to place a call to the RemoteWare Communications Server from the OS/2 prompt without having to start a Client communications program (OS2COMM or OS2TCOMM). After OS2AUTO has been started, it will automatically exit after a successful session has occurred (or timeout if you are using the -d or -w options described in Table 8). This allows you to use OS2AUTO in a batch file to load the Client Communications software, initiate a session, then remove the Client Communications software and exit. To start the Auto Communications application: 1 Open an OS/2 command prompt. 2 Change the current directory to RWCLIENT\NODESYS. 3 Start the program by typing the command: OS2AUTO Options For a list of options, see Command line options on page 60. Auto Communications automatically loads the communications engine (if it is not already active) and places the call to the RemoteWare Communications Server. If a connection cannot be established, an error message appears. If you want to retry the call, press [Y]. If not, press [N]. If you select [N], the communications engine is removed and you return to the OS/2 prompt.

60 60 RemoteWare OS/2 Client User s Guide Command line options You can configure Auto Communications with custom settings from the command line. Table 8 lists each option, an example, and the function. Table 8. Auto Communications command line options Option Example Description -? os2auto.exe -? Displays a list of available command line options. -d retries minutes os2auto.exe -d 5 10 Places a call to the Server using a specified number of retries within a given time frame. The example allows up to 5 retries 10 minutes apart. -n os2auto.exe -n Disables the escape key. The application does not allow the user to exit until the session is successful or the number of retries have been exhausted. -r minutes os2auto.exe -r 30 Reschedules a call to the Server within a specified time after a session has occurred. This example calls the Server, then schedules another call in 30 minutes. -w minutes os2auto.exe -w 15 Specifies a period of time to wait for a successful inbound call from the Server. This example instructs the Client to wait for 15 minutes for a successful session, then exit. Note: You cannot use the -d, -w, or -r options together. Displaying help To display the available OS2AUTO command line options, enter the following command at the prompt: OS2AUTO -? Disabling the Escape key To disable the Escape key for OS2AUTO so that the program is not accidently terminated, add the -n parameter to the command. For example, OS2AUTO -n.

61 CHAPTER 2 / Using the Client software 61 Waiting for an inbound call Rather than using OS2AUTO to dial out, you can use OS2AUTO to set up your Client to wait for an inbound call. To do this, enter the OS2AUTO command with the -w <minutes> parameters. For example, to specify that you want the Client to wait for an inbound call for 90 minutes, you would enter: OS2AUTO -w 90 Rescheduling a call To reschedule a call to the RemoteWare Server, use the -r <minutes> parameter with the startup command. For example, to specify that you want the Client to place the call within 10 minutes after the session has run, you would enter: OS2AUTO -r 10 If you use this option, you will have to manually exit the program. If you use this option along with the -n option, you will have to reboot the machine or kill the process to exit OS2AUTO. Retrying a call The -d option and its parameters enable you to specify a number of retries and the time interval between retries. Enter the command as shown below: OS2AUTO -d <# of retries> <minutes> [retry to use #2] For example, to specify that you want 5 retries with a one minute interval between each retry, and that you want the second RemoteWare Communications Server phone to be used on retry number 2 and on each subsequent attempt you would enter: OS2AUTO -d OS2AUTO first uses the phone number defined as Server phone number 1. If you want to use only the phone number defined as Server phone number 2, specify 0 as the retry on which to use the Server phone number 2. For example, to specify 10 retries, each one a minute apart, and using Communications Server phone number 2, you would enter: OS2AUTO -d

62 62 RemoteWare OS/2 Client User s Guide OS2TCOMM Text-Mode Communications OS2TCOMM is a text-mode program that you can run in an OS/2 window or full-screen session, or on a system that does not have the Presentation Manager installed, to control communications with your Server. With OS2TCOMM, you can set up, control, or monitor communications with the Server. To start the OS2TCOMM program: 1 Open an OS/2 command prompt. 2 Change the current directory to \NODESYS. 3 Start the program by typing the command: OS2TCOMM The main menu is displayed: If the OS2TNODE program was not running in the background, it will load automatically when this command is typed. When you exit from OS2TCOMM, the program will remove OS2TNODE from memory. If OS2TNODE was running before you started OS2TCOMM, it will remain resident in memory after you exit the program. For instructions on loading OS2TNODE independently, see Starting the communications kernel on page 33.

63 CHAPTER 2 / Using the Client software 63 Connecting with the Server To call the Server from the Client, press [Enter] or [F1]. This starts an inbound connection to the Server using the entry designated as Phone #1. The status shows that a connection attempt is being made. To cancel dialing, press [F3]. To connect using the entry designated as Phone #2, press [F2]. Once a connection is made, the screen displays the activity between the Server and the Client below the Status indicator. File transfers display a message to show how much data has been exchanged and the direction of the file transfer (Sending or Receiving). Using the Client scheduler Use the Client scheduler to set a time for the Client to contact the Server. Once active, the Client can initiate an inbound connection to the Server at a fixed time. The schedule you set is only run once. You must then reset it. The schedule is useful for unattended Client operation. For example, if you needed to retrieve a report generated on the Server after your regular working hours, you could schedule an unattended connection to begin at midnight. To do this, you would set the connection time for 00:00 and leave the Client computer turned on. Note: The schedule set at the Client takes precedence over a schedule set at the Server. The connection occurs at the scheduled time unless the Client software is not running or it cannot access the connection hardware.

64 64 RemoteWare OS/2 Client User s Guide To set a time for a connection to start: 1 Press [F4] at the main OS2TCOMM menu screen. The Set Schedule dialog is displayed. 2 To enable the schedule, type Y and press [Enter]. (Press [Enter] to accept the default and display the next prompt.) 3 To enable retries, type Y and press [Enter]. (Press [Enter] to accept the default and display the next prompt.) When enabled, the Client attempts to contact the Server a maximum of three (3) times 5 minutes apart before logging the attempt as unsuccessful. 4 Set the hour for the session. Use the up and down arrow keys to select the hour you want the session to run. The time is set in 24-hour format. Remember to properly represent afternoon times, such as 14 for 2PM. 5 Press [Enter]. (Press [Enter] to accept the default and display the next prompt.) 6 Set the minutes for the session. Use the up and down arrow keys to select the minutes you want the session to run. Press [Enter] to accept the default and display the next prompt. 7 Press [Enter]. 8 Press [Enter] to accept the schedule you have set.

65 CHAPTER 2 / Using the Client software 65 9 Press [Esc] to return to the main menu. The scheduled dial-out time is displayed above the menu. The schedule is not saved when you exit Client Communications. Note: If you try to exit Client Communications and a schedule is active, the Client displays the message Schedule is active. Deactivating the schedule There are two different scenarios and procedures for deactivating the schedule: Schedule set by the Client. Press [F4] at the main OS2TCOMM menu screen. To disable the schedule, type N and press [Enter]. The schedule is disabled. Schedule set by the Server. The Server Administrator can disable the schedule from the Server. The Client user can also exit Client Communications to temporarily delay the schedule. If the scheduled time arrives and Client Communications or OS2NODE is not running, the Client will not attempt to place an inbound connection to the Server. Setting up the Client A Client s password is one level of security that permits a connection with specific Servers. The password and other current connection information are available from the Client Setup window. If you change a Client s password on the Server, or if you want to make changes to the Client s communications parameters, you can use the [F5] View Setup option to edit the current Client setup. Do this only at the direction of the System Administrator, and only if the same changes have been made on the RemoteWare Server computer.

66 66 RemoteWare OS/2 Client User s Guide To change the Client password 1 From the OS2TCOMM main menu, press [F5]. The Client Setup is displayed. 2 Press [F8]. The Client Setup displays the current password. 3 Type the new password in the Password field. The password may be from 1 to 10 characters. 4 Press [Enter] to accept the new password. 5 When finished, press [Enter] until the prompt Save changes appears. 6 Press [Enter] to save your changes. 7 Press [Esc] to return to the main menu. To change the Server phone numbers 1 From the OS2TCOMM main menu, press [F5]. The Client Setup is displayed. 2 Press [F8]. The Client Setup displays the current password. 3 Press [Enter] to bypass the password. Server Phone #1 is displayed. 4 Edit the phone number or address as necessary. 5 Press [Enter] to accept the edits. Server Phone #2 is displayed. 6 Edit the phone number or address as necessary. 7 Press [Enter] to accept the edit.

67 CHAPTER 2 / Using the Client software 67 8 Press [Enter] to save your changes. 9 Press [Esc] to return to the main menu. Changing the modem setup To change the setup of the modem at the Client: 1 From the OS2TCOMM main menu, press [F5]. The Client Setup screen is displayed. 2 Press [M]. The Modem Setup screen is displayed. 3 Press [F8] to edit the setup. Each entry is displayed. 4 Edit the current setting and press [Enter], or press [Enter] to display the next setting. 5 When prompted, enter [Y] to edit the modem result codes. If you enter [N], you are prompted to save your changes. See step 7.

68 68 RemoteWare OS/2 Client User s Guide 6 Each entry is displayed. Edit the current setting and press [Enter], or press [Enter] to display the next setting. 7 When prompted, press [Enter] to save your changes. Type [N] and press [Enter] to cancel any changes. 8 The Client Setup screen is displayed. Press [Esc] to return to the main menu. See Changing the modem setup on page 47. earlier in this chapter for guidelines on changing the modem s parameters. Viewing the Communications Log Each time the Client attempts to communicate with the RemoteWare Server, the Communications Log records the following information: Start Time. Lists the date and time when the connection was initiated or accepted from the Server. Duration. Displays the minutes and seconds elapsed from the Start Time to disconnection. Origin. Indicates whether the Client or Server initiated the connection. Status. Displays the outcome of the connection. Possible status values appear in Table 6 earlier in this chapter. To view the Client Communications Log, press [F6]. When you are finished viewing the log, press [Esc] to return to the main menu.

69 CHAPTER 2 / Using the Client software 69 Canceling an active session To cancel an active session from the Client, use [F3]. You are prompted to confirm the command. Press [Enter] to confirm the command. Type [N] then press [Enter] to cancel the command. If you cancel a session, the status of the session in the Communications Log shows that the session was aborted at the Client. Reinitializing the modem Pressing [F7] sends the Auto Answer or the No Answer command string to the modem. It also sends the Modem Init string to the modem. Use this option if you have problems communicating with the modem at the Client, or when the Status shows a Resource Error while using an asynchronous resource. When you press [F7] the message Reinitialization Requested is displayed on the screen. Disabling Electronic Software Distribution Electronic Software Distribution (ESD) is a Server feature that transfers the latest files from the Server to the Clients. The Server only sends the files when the Client does not possess the latest version. In addition, the Server automatically resends files that may have been inadvertently altered, moved, or deleted. This feature is valuable when the latest data is required or portions of the Client are deleted accidentally. To prevent a potentially lengthy file download from taking place when time is of the essence or to allow such transfers to occur during off-peak hours, you can disable ESD for the next session at the Client. Press [Ctrl][E] to disable ESD for the next session at the Client. The message Disabling ESD is displayed on the screen. When disabled, ESD:Off is displayed in the upper-left portion of the screen. Disabling Auto Answer Auto Answer is a modem function that picks up the line when the modem detects a ring signal. This feature is required for Clients accepting outbound calls from Servers. However, Auto Answer may be inconvenient when the phone line is shared with voice callers, fax machines, and other computers. To toggle the auto answer feature on and off, press [Ctrl][A]. The message Disabling Auto Answer is displayed on the screen. When disabled, AA:Off is displayed in the upper-left portion of the screen.

70 70 RemoteWare OS/2 Client User s Guide Exiting OS2COMM To exit from the OS2TCOMM program, press [Esc] or [F10] at the main OS2TCOMM screen. If you set a time to run an unattended session, a prompt reminds you that the schedule is active. To exit, press [Y] and [Enter]. To cancel, press [Enter]. If the OS2TNODE program was loaded by OS2TCOMM, it will be removed from memory when you exit from OS2TCOMM. If OS2TNODE was running before you started OS2TCOMM, it will remain resident in memory after you exit the program.

71 APPENDIX A A Client Directory Structure This appendix discusses the following file system information: Installation details RemoteWare Client directory and file structure

72 72 RemoteWare OS/2 Client User s Guide Installation details An installation of the RemoteWare Client begins with a set of files generated by a RemoteWare Server. The group of files are called an installation kit (or makekit). Although makekits generally reside on one or more floppy disks, they may also be created on a hard disk or a network volume. Only one makekit can be created on a hard drive or network volume, but the files and directories can be moved to another location for storage. The OINSTALL.EXE (OTINSTAL.EXE) application installs the makekit from any floppy disk, hard drive, or network volume. The OINSTALL.EXE (OTINSTAL.EXE) application performs the following tasks: Obtains the destination directory and creates the \NODESYS and \RWNODE subdirectories. OTINSTAL.EXE creates the \NODESYS and \RWNODE directories off of the root directory. Copies the files provided in the \FILES directory to the \UPDATES directory; they are moved to the \NODESYS directory at startup. Provides the option to automatically update files during bootup. For template Clients, obtains necessary configuration and security information. Provides the option to view and change connection numbers or addresses. Removes temporary files from the hard disk.

73 APPENDIX A / Client Directory Structure 73 File and directory changes A RemoteWare Client installation and subsequent operation performs these tasks: Creates the specified destination directory (if necessary). Creates the \NODESYS directory and all its files and subdirectories. Creates the \RWNODE directory and sets up the Client information. Optionally modifies the STARTUP.CMD file to contain commands to automatically copy and then delete files from the \NODESYS\UPDATES directory to the \NODESYS directory; also copies the original STARTUP.CMD to STARTUP.BAK. Optionally adds the Client drive and time zone variables to the CONFIG.SYS file. Creates the RemoteWare program group and icons for the RemoteWare Client applications. (OINSTALL.EXE only.)

74 74 RemoteWare OS/2 Client User s Guide

75 ADDENDUM A Addendum Notes These notes are applicable to RemoteWare 4.1 for the OS/2 Client. These notes affect the following: Installing a custom Client on a local drive Installing a template Client - United States Zip code Configuring communications settings Registering the template Client Installing a text-mode Client RemoteWare Client at a Client Starting and stopping the communications kernel Alert conditions Electronic Software Distribution (ESD) Applying ESD Changing the modem setup Cancelling a session Viewing alerts Connecting with the Server

76 76 RemoteWare OS/2 Client User s Guide Installing a custom Client This note applies to Installing a custom Client. Refer to step 4, page 13 in this guide. Note: The RemoteWare Client software should be installed on a local drive. XcelleNet does not support running the Client from a network drive. Installing a template Client This note applies to registering a template Client. Refer to step 3, page 19 in this guide. Note: Enter only the first five digits of a United States zip code. Configuring communications settings This note applies to TCP/IP settings. Refer to page 20 in this guide. Note: The template install does not auto-detect the TCP/IP address. You must enter it manually after the installation. Registering the template Client These notes apply to the registration process. Refer to page 23 in this guide. Note: If you cancel the registration process before it successfully completes, the modem is not disconnected. To disconnect correctly, retry the registration process, letting it process completely. Note: During the registration portion of the template installation, the Status dialog remains blank until the connection is made. Installing a text-mode Client This note applies to a Date Rate. Refer to step 13, page 30 in this guide. Note: For a Direct Connect asynchronous connection, the Max Data Rate setting for the Server s asynchronous resource must match the Data Rate of the asynchronous resource defined for the Client.

77 Addendum Notes 77 RemoteWare Client at a Client This note applies to Table 2: Client Applications. Refer to page 34 in this guide. Program Name: OS2NODE.EXE Common Name: Communications Kernel Addition to the Description: It is also automatically loaded when the Client UI OS2COMM is started. It can also be loaded from a command line. Starting the communications kernel This note applies to the unloading the kernel. Refer to page 35 in this guide. Note: Attempting to unload the kernel immediately after cancelling a session may result in an error indicating the address is in use. Wait at least two minutes for the system to relinquish the resource, then unload the kernel. Stopping the Communications kernel Important: The RemoteWare Server and Client cannot communicate if the kernel is not loaded. If the communications kernel was loaded when the Client UI was opened, it unloads automatically when you close the Client UI. If the kernel was loaded before the UI was opened, it continues to run until you stop it manually. The table below shows the methods you can use to unload the kernel. Table 1. Methods to unload the communications kernel manually Method From the Command menu, choose Unload Client From a command prompt, type OS2NODE -r Description Removes the OS2NODE program from memory. Use this method if the program was loaded from a command line. To reload, use Command Load Client. Removes the OS2NODE program from memory. Use this method if the program was loaded from a command line. Note: To run OS2NODE without Presentation Manager, you must start the kernel using the Detach OS2NODE command. To run the text-mode Client software (OS2TCOMM), load OS2TNODE instead of OS2NODE.

78 78 RemoteWare OS/2 Client User s Guide Alert conditions This information applies to a new Alert icon. Refer to page 39 for other alert icons. Table 2. Alert conditions Alert icon Alert name Description ESD update received The Server has delivered updated files to the \updates directory. To use these files, you should apply ESD. For steps, see Applying ESD on page 79. Electronic Software Distribution (ESD) Electronic Software Distribution is a feature that transfers the latest files from the Server to the Clients. The Server only sends the files when the Client does not possess the latest version or when files have been inadvertently altered, moved, or deleted. This feature is valuable when the latest data is required or portions of the Client are deleted accidentally. When ESD files are delivered during a communication session, they are placed in the nodesys\updates directory and aren t used until they are moved to the proper location. The RemoteWare Client notifies you that ESD files have been received by displaying the ESD update received alert icon in the status bar. To use the files, you apply ESD which tells the Client to move the files.

79 Addendum Notes 79 Applying ESD n ESD files are automatically applied if your startup.cmd file was modified during installation. When updated files are delivered by the RemoteWare Server, it is important for you to apply ESD so the files can be used. You know ESD files have been received when you see the ESD update received icon on the status bar. To apply ESD: 1 Click the ESD update received icon or select Commands View Alerts. The ESD Files dialog box appears. 2 Select the file or files you want to apply, then click OK. Changing the modem setup This note applies to Max Data Rate. Refer to page 51 in this guide. Note: For a Direct Connect asynchronous connection, the Max Data Rate setting for the Server s asynchronous resource must match the Data Rate of the Asynchronous resource defined for the Client. Cancelling a session To cancel the session in progress, select Command Cancel Connection or click the Cancel button. Note: Attempting to unload the kernel immediately after cancelling a session may result in an error indicating the address is in use. Wait at least two minutes for the system to relinquish the resource, then unload the kernel.

80 80 RemoteWare OS/2 Client User s Guide Viewing Alerts This note applies to a Resource Error. Refer to page 58 in this guide. Note: If you receive a Resource Error while using an asynchronous resource, you may need to reinitialize the modem. ESD update received This information replaces the ESD arrived information on page 59. The ESD update received alert icon ( ) appears when ESD files have been delivered to the \nodesys\updates directory. The ESD files window lists the executable and DLL files the Server delivered. To move them to their correct directories (referred to as applying ESD), select the files then click OK. For more information about applying ESD, see Applying ESD on page 79. Connecting with the Server This note applies to the first client assigned in the Client Profile. Refer to page 65 in this guide. Note: The first resource assigned to the OS/2 Client in the Client profile determines whether the Client will be Async or TCP/IP. You can, however, change the resource manually after installation.