System services can be installed on a workstation during system initialization, or you can install them with Executive commands.
Table 9-1 lists the Executive commands and run-file names for installing system services supplied with Standard Software. See the eTOS
Executive Reference Manual for information about parameter values.
See the release documentation for information about installing system services for other applications.
Installing From the Executive
9-14
You can install system services with Executive commands. This method is generally used in the following circumstances:
• You install a system service for the first time and want to make sure that it works as you expect.
• You need a system service only at certain predictable times, for example, if you use the Sequential Access Service once a day for backups.
Note: You must install system services before you start Context Manager on a workstation.
To install a system service with the Executive, follow these steps:
1. Type the command name on the Executive command line; then press RETURN (see Table 9-1).
2. Fill in parameter fields as required; see the appropriate manual or release documentation.
3. Press GO.
Installing System Services
Table 9-1. System Service Commands and Run Flies
System Service Executive Command Run File
CD-ROM Service Install CORaM Service CDROMService.run
Cluster File Access Install CFA File Filter CfaFf.run File Filter
Cluster File Access Server Install CFA Server Service CfaM.run Service
Cluster File Access Install CFA Workstation Agent CfaWa.run Workstation Agent
Command Access Service Install Command Access AccessService. run Service
DataComm Service Install OataComm Service DcxService. run
Math Service Install Math Service MathService.run
MCRService Install MCR Service MCRService.run
Mouse Service Install Mouse Service Mouse.run
Queue Manager Install Queue Manager InstallQMgr.run
Remote Keyboard None RKVS.run
Video Service
Remote User Manager None RUM. run
Screen Print Service Install Screen Print InstallScreenPrint.run Sequential Access Install Sequential Access InstallSeqService.run
Service Service
Spooler Install Spooler Spooler. run
Statistics Service Install Statistics Service Sta tis tics. run
Voice Service Install Voice Service AudioService.run
XBI F Service Install XBIF Service Xbif.run
XC-002 Service Install XC002 Service XCOO2Service.run
CTOS System Administration Guide
Installing During System Initialization
9-16
System services that you use all the time, such as printing or electronic mail, can be installed during system initialization. This is convenient and automatic; whenever you reboot the workstation, system services are installed.
Mter the workstation bootstraps, the system initialization program searches for a file named [Sys]<Sys>Syslnit.jcl. If it exists, its contents are read and executed. You create SyslnitJcl to install the appropriate system services on the workstation. Figure 9-5 shows a system
initialization file for a workstation.
Job Syslnit ContinueOnError Run [Sys]<Sys>Xbif.run
Run [Sys]<Sys>lnstaIlOMgr.run, y, 30 Run [Sys]<Gps>Gpslnstall.run Run [Sys]<Sys>MaiIServer.run Run [Sys]<Sys>ModemServer.run
Run [Sys]<Sys>CommunicationsManager.run, Line1 Run [Sys]<Sys>lnstaIlSeqService.run, [OIC]
Run [Sys]<Sys>MouseService.run End
Figure 9-5. Workstation System Initialization File
Installing System Services
Creating a System Initialization File
To create a system initialization file, you use the Editor to write a simple program in Job Control Language (JCL). Table 9-2lists the JCL state-ments you use in this file. See "JCL Syntax," Jater in this section, for rules about punctuation and spacing. See the CTOS Editor User's Guide for information about using the Editor.
After you create the file, reboot the workstation to install the system services.
Note: Prior to 12.0 Standard Software, JCL statements were preceded by a dollar sign ($). The dollar sign is no longer required, however, it does not interfere with the execution of existing JCL files.
Table 9-2. JCL Statements for Workstations
Statement
Command
ContinueOnError
CancelOnError
End
Job
Run
Description
This statement specifies the name of an Executive command.
To be executed during system initialization, the command must be present in [Sys]<Sys>Sys.cmds.
This statement forces continuation of the system initialization file, even if an error occurs. It affects statements that follow it until the end of the file, or until a CancelOnError statement occurs.
This statement reinstates the CancelOnError condition, which terminates system initialization when an error occurs.
This statement defines the end of a Batch job. End your system initialization file with it, as shown in Figure 9-5.
This statement defines a name for the batch job. For system initialization, specify Syslnit, as shown in Figure 9-5.
This statement specifies the name of a run file to be executed.
CTOS System Administration Guide
JCL Syntax
When you create a system initialization file, you are writing a program in Job Control Language. (JCL files are processed by the Batch facility, which can be used for jobs other than system initialization.) The following sections describe syntax rules that apply to system initializa-tion. See the CTOS Batch Manager II Installation, Configuration, and Programming Guide, for more detailed information.
Specifying Run Files and Command Names
Separate the name of a run file or command from the Run or Command statement with at least one space or tab, as shown in the following examples:
Run file
Run [Sys]<Sys>MouseService.run
Command
Command Install Mouse Service
Specifying Parameters
9-18
When a run file or command requires parameters, separate them with commas, as shown in the following examples:
Run file
Run [Sys]<Sys>lnstaIlQMgr.run, yes, 10
Command
Command Install Queue Manager, yes, 10
Each pair of commas defines one field. If you leave a parameter blank, you must enter commas as a place holder for the field. The following example shows three blank fields between the parameter values 75 and 50:
Run [Sys]<Sys>Net.run, SJ-Node, 67, 2, 75",,50
Commas are not required, however, for parameter values omitted at the end of a statement.
Installing System Services
Specifying Subparameters
When a parameter consists of more than one value per field, enclose subparameters in parentheses, as shown in the following example:
Command Disable Cache, (File1, File2), yes
Entering Multiple-Line Parameters
When parameters exceed a single line, use an ampersand (&) to indicate that the statement continues on the next line, as shown in the following example:
Run [Sys]<Sys>CommunicationsManager.run,&
VeryLongNamelsCarriedOver
Entering Comments
To enter a comment, precede text with a semicolon (;), as shown in the following example:
;This is a comment
You can add comments to clarify the contents of a file (for yourself or others who might edit it) or to temporarily disable a JCL statement. The following example shows both:
Job Syslnit ContinueOnError Run [Sys]<Sys>Xbif.run
;Alan borrowed my tape drive, so I have disabled the Seq Service
;Run [Sys]<Sys>lnstallSeqService.run, [OIC]
Run [Sys]<Sys>MouseService.run Run [Sys]<Sys>AudioService.run End
CTOS System Administration Guide
Creating WsNNN>Syslnlt.jcl
You can create system initialization files for cluster workstations that boot from the server. Such files must be located in [Sysl<Sys> on the server and are named as follows:
[Sysl<Sys>WsNNN >Syslnit.jcl
where NNN is the three-digit workstation-type number or, if that file does not exist for a particular workstation type:
[Sysl<Sys> Ws>Syslnitjcl
Ifneither WsNNN>Syslnit.jcl nor Ws>Syslnit.jcl exists, no system initialization sequence is executed on the workstation.
See also Section 5, "Bootstrapping," for detailed information about workstation-type numbers and diagrams of the system initialization sequence.