Before Cobol-RPC can execute remote program calls on a Windows server, the Cobol-RPC Server program must be started. Once started, there are several administrative capabilities offered by the server. This section reviews the features of the Windows Cobol-RPC Server.
To begin handling service requests, the Cobol-RPC Server must be started. The Cobol-RPC Server can be started by double clicking its icon in the Program Manager group containing its icon. The Cobol-RPC Server window will display as follows:
When the server is started it immediately initializes and begins accepting remote program calls. This is reflected by the word "Started" displaying in the title bar of the window and by a message displayed in the activity log, if the log is turned on.
The server may be stopped by selecting the Stop command from the Options menu. The word "Started" in the title will be replaced by "Stopped" and a message will be displayed in the activity log, if enabled. The server will not accept any remote program calls while stopped. The server may also be stopped by clicking on the button with the picture of the upright hand.
After stopping, the server may be restarted by selecting "Start" from the Options menu, or by clicking the toolbar button picturing the runner.
The server may be exited by selecting Exit from the File menu.
The server can be configured by editing the COBOLRPC.INI file as described in Chapter 3, or by selecting Configure... from the Options menu. This displays the Server Configuration dialog as follows:
You may change any of the configuration parameters and press OK to save them or Cancel to discard them. Changing the portPort number will cause the server to briefly stop and then restart to establish the new port. Changing the configuration parameters will not effect any currently connected clients, but will immediately effect any new clients.
The following sections describe each of the fields on the Server Configuration dialog.
Port number specifies the port number that will be used to listen for remote program calls. Port numbers are logical values, not physical. Select a unique number not used by any other service on the server. This number must also be set as the port value in the COBOLRPC.INI file of any clients using the server. The default value of this field is 5000.
Startup command specifies the command that will be used to start the Cobol runtime for each connection. Please see your release notes for a sample of how to complete this field for your implementation.
Complete path names should be included for all files. This makes them insensitive to the working directory the server is initiated from. A Cobol configuration file and other runtime parameters can be included in this command.
Object file path(s) specifies one or more locations for the Cobol programs that are called by clients. Multiple locations must be separated by a semicolon.
The directories specified are used only for remote programs called by the clients on some implementations. Please see the release notes to determine if this parameter is meaningful for your implementations. If server programs make additional Cobol calls the location of the called programs will be controlled by the working directory and the search logic of the Cobol being used.
Working directory specifies the working directory from which server programs should be executed. If no value is entered, the working directory will be the working directory specified in the icon for the Cobol-RPC Server.
The working directory has implications for locating both Cobol programs and data files and should be carefully established.
Log activity determines whether or not a log of activity is kept by the server. This log is displayed in the server window and can be printed or saved to disk.
The activity log keeps track of when the server is started and stopped, what port is used, and clients connecting to and disconnecting from the server. Server errors are also displayed in the log. Each activity is accompanied by a date and time stamp. Clients are identified by their network address.
Cobol Type specifies what type of Cobol is being used on the server. The different versions of Cobol have different techniques for passing command line parameters. If this option is not configured for the Cobol being used on the server, the server program will not execute properly
The activity log keeps a record of Cobol-RPC activity. Every time the server is started or stopped a message is added to the activity log. Every time a client connects to or disconnects from the server another message is added. All server errors are also recorded in the activity log.
The following commands are available for managing the log.
|Save As||The activity log can be saved to disk by selecting Save As... from the File menu.|
|Print Setup||The print configuration can be changed by selecting Print Setup... from the File menu.|
|Print Preview||The format of the activity log can be previewed by selecting Print Preview... from the File menu.|
|The activity log can be printed by selecting Print... from the File menu or clicking the toolbar button with the printer icon.|
|Clear||The contents of the activity log can be cleared by selecting Clear from the Edit menu.|
The display of the status bar at the bottom of the Cobol-RPC Cobol Server window can be toggled by selecting Status bar from the View menu.
The display of the toolbar just below the menu on the Cobol-RPC Server window can be toggled by selecting Toolbar from the View menu.
The entire Cobol-RPC Server window can be minimized without effecting server operation.
The Cobol-RPC copyright information can be displayed by selecting the About Cobol-RPC Server... option from the Help menu. This manual can be viewed on-line by selecting the "Help with Cobol-RPC" option from the Help menu.
Distributors | Library | Register
Copyright 1996 by England Technical Services, Inc.