










System Administrator Course














Copyright 1987 by Charles E. Brown
1. User files

A. Why and How to use User configuration files

	1. Security
	2. Control level of access to commands
	3. Contents of a user configuration file

B. Creating and Modifying User files

	1. User file editor
	2. Valid entries in a User file


2. Command files

A. Creating a New Command

	1. The New Command command

B. Removing a Command

	1. The Remove Command command

C. The Sys.Cmds File

	1. Specifying different commands files via a user file


3. Spooler  Queue Manager  Printers

A. Spooler

	1. SplCnfg.Sys file
	2. Format of SplCnfg.Sys file
	3. Spooler Status command

B. Queue Manager

	1. Queue.Index file
	2. Format of Queue.Index

C. Printer Config.Sys files

	1. The Create Configuration File command

D. Creating and Modifying Sys.PrintersWp.Printers

	1. What software uses the Sys.Printers file
		a. WriteOne
		b. MultiPlan
		c. Business Graphics

	2. Field definition in Sys.Printers
4. File System

A. File system hierarchy

B. What is a Directory

C. What is a Volume

D. Files is the <Sys> Directory

E. File naming conventions


5. IVolume Parameters

A. Difference between a data disk and a System (Boot) disk

B. Ivolume parameters


6. The LCopy command


7. Passwords

A. Why use passwords

	1. Security
	2. Problems using passwords
	3. Passwords and how to use the ^ (caret)

B. Protection levels

	1. How to assign the correct protection level

C. The Change Volume Name command


8. Backup Volume  Selective Backup  Restore

A. Backing up and Restoring

	1. Why use Backup Volume?
		a. Correcting disk fragmentation problems
		b. Recovering data from corrupted disks

	2. Why use Selective Backup?
		a. Backup of inportant data

	3. Restoring data

9. Submit files

A. Creating and Modifying Submit files

	1. The Record command

B. Commands that use submit files

	1. Making commands that use submit files
	2. SubCmd.Run

C. Software Installation command


10. JCL files

A. Why use a B25 JCL file

	1. Automatic program loading
	2. JCL files for cluster workstations.

B. Creating and Modifying JCL files

	1. Parameter passing in JCL files

C. Common error messages encountered during JCL installation.


11. Clustering Concepts

A. What is a cluster

	1. Services provided by a cluster
		a. Shared disk
		b. Print spooling

B. File names in a cluster

	1. Operating System naming conventions

C. Free Slave Clusters

	1. How does a free slave differ from a slave cluster?

D. Clusters with local disks and the Sys Volume

	1. What is the Sys or Scr volume?

E. Cluster Status command

F. System boot

	1. sequence of events


12. ISAM
A. What is ISAM

B. What Software uses ISAM?

	1. RBase
	2. Application Development System (ADS)
	3. Data Manager
	4. PDS Adept
USER FILES



Reference BTOS Standard Software Operation Guide, pages 21  225



The system administrator normally grants access to the system for a user by creating the file [sys]<sys>xxxx.User, where xxxx is the user's name entered in the SignOn screen for User name. If the administrator decides to enforce the use of a password for security, then password protection is placed on the user file with the Set Protection command.





A typical SignOn screen is shown below.



SignOn 5.0.4
                                                    Mon Mar 31, 1986 12:10 PM
=============================================================================
                   BURROUGHS B20 OPERATING SYSTEM BTOS 5.0.4
+++
|User name     | Enter an application name or leave this line blank         |
|              |   to display a Command form.                               |
+++
|Password      | Enter your assigned password (optional).                   |
+++
|DayDateTime | Enter the current day, date and time (if not already set). |
+++
                          Then press the GO key.
 
User name (e.g., Allen)
Password
DateTime (e.g., Fri Sep 9, 1983 8:00 am)


USER FILES


After the user enters their name and password and presses GO, SignOn attempts to open the user configuration file for reading. If the file is not on disk or if an improper password is supplied, SignOn returns an error message and requests a valid user name and password. Otherwise, the user file is searched for a series of arguments which characterize that particular user. The format for these arguments is :KeyWord:Data and they function as follows:


REQUIRED ENTRIES

:SignOnVolume:Sys
:SignOnDirectory:WorkSpace
:SignOnFilePrefix:
:SignOnPassword:
:SignOnExitFile:[Sys]<Sys>Exec.Run


OPTIONAL ENTRIES

:SignOnChainFile:
:SignOnTextFile:
:ExecCmdFile:
:SignOnUserName:


Word Processor OPTIONAL entries.

:WpFormatSet:[Sys]<Sys>Wp.Fmt
:WpPrinters:[Sys]<Sys>Sys.Printers
:WpPrintWheels:[Sys]<sys>Wp.Whl
:WpPhrases:[Sys]<wp>phrasefile
:WpDictionary:[sys]<Wpf>Wp.Words
:WpPersonalDictionary:[Sys]<Wp>My.dict1

:WpForceForegroundPrint:
:WpType:


Multiplan OPTIONAL entries.

:SysPrinters:[Sys]<sys>Sys.Printers


USER FILES


User files may be created or edited in one of three ways:

1. The Editor
2. The WriteOne (Make sure you remove formatting <CODER> before saving)
3. The User File Editor command

User file editor example:

Command  u f e
User File Editor
  User name          UserName
  [Old password]
  [New password]
  [Template file]
  [Command file]








Lab Exercise


Objective:		The ability to create and modify user configuration files based on departmental requirements.

Exercise:		Create a user file that sets the default path to a user directory and uses a unique Sys.Cmds file.

Step 1		Create a new directory (Create directory command) using your first name.

Step 2		Copy [sys]<sys>Sys.Cmds to the directory you created in step 1. This will be used for the unique set of commands for the new user.

Step 3		Create a new user file (User File Editor command) that sets the path to the directory created in step 1 and also uses the command file created in step 2.

Step 4		Logout and sign on with the new user name. Verify that the new user file performs correctly.

Step 5		Inspect and modify the new user file using the Editor (Edit command).
Command files


Reference BTOS Standard Software Operation Guide, pages 712  717

Creating a new command.

Command  new command
New Command
  Command name            __________________________________________
  Run file                __________________________________________
  [Field names]           __________________________________________
  [Description]           __________________________________________
  [Overwrite ok?]         __________________________________________
  [Case (default = '00')] __________________________________________
  [Command file]          __________________________________________




NOTES

1. If parameters contain spaces then the entire parameter must be enclosed in quote marks. Example, Command name 'New Command'.

2. If a parameter will not fit on a line because it is too large you will have to use an '@' file.

Example, [Field names]  @NewCommand.Args

The file NewCommand.Args would contain:
'Command name' 'Run file' '[Field names]' [Description] '[Overwrite ok]?' '[Case (default = ''00'')]' '[Command file]'

The above data is created with the Editor and is entered without using the <RETURN> key.





Removing a command.

Command  rem c
Remove Command
  Command name   ____________________________________________
  [Command file] ____________________________________________




The Command File Editor


Command files

Sys.Cmds

The name of the file that contains all of the information about the commands is the file [sys]<sys>Sys.cmds. This is the default Command file used by the New Command and Remove Command Executive commands.

The default Command file can be changed (for security or administrative reasons) by modifying the :ExecCmdFile: entry in the User configuration file.










Lab Exercise


Objective:	Customizing command files for departmental needs.

Exercise:	Remove unwanted or dangerous commands and add a new command.

Step 1:	Use the commands New Command, Remove Command and Command File Editor to modify the commands file.
SPOOLER



Reference BTOS Standard Software Operation Guide, Section 4



Installed at each workstation with a spooled printer physically attached.

Install Spooler
  [Spooler configuration file] _______________________________________

The Spooler can be installed with the Install Spooler command, but the more common method is to place an entry in the SysInit.JCL file to install the Spooler ($RUN [sys]<sys>InstallSpl.Run) whenever the workstation is turned on.

Spooler configuration files.

Default file name is [sys]<sys>SplCnfg.Sys

Format of the Spooler Configuration file: Page 412


                                    Printer
Channel  Printer name*  Queue name  Configuration  Priority  Print banner
                                     file



Example of SplCnfg.Sys:

0DraftSPL[sys]<sys>LPTConfig.Sys130n
BLetterSPLB[sys]<sys>DiabloConfig.Sys64n





* Printer name must match ControlQueue name in <sys>Queue.Index.




The Spooler Status Command
QUEUE MANAGER



Reference BTOS Standard Software Operation Guide, Section 4



Installed on MASTER or STANDALONE ONLY.

The Queue Manager can be installed with the Install Queue Manager command, but the more common method is to place an entry in the SysInit.JCL file to install the Queue Manager ($RUN [sys]<sys>InstallQMgr.Run) whenever the workstation is turned on.



Uses [Sys]<sys>Queue.Index to define the available queues.

Format of Queue.Index: Page 416

Queue Name1  Queue File Name  Entry size in sectors  Queue Type2

1 Must match the Queue Name and Printer Name entrys in <sys>Splcnfg.Sys

2 Types:
	1  Spooler Queue
	2  RJE Queue
	3  Batch Queue


Example of Queue.Index:

SPL[sys]<spl>Spl.Queue11
DraftControl[Sys]<sys>DraftControl.Queue11
SPLB[sys]<spl>SplB.Queue11
LetterControl[Sys]<sys>LetterControl.Queue11
SpoolerStatus[sys]<sys>SpoolerStatus.Queue11








Printer configuration files


The Create Configuration file command
Q MANAGER and SPOOLER

           
              Master               
            Workstation  Printer     9253 (SPL)
                      
   
   
                       
 CWS  CWS  CWS 
                       
                                        
                          
 Printer   AP1302 (SPLA)            Printer   AP1351 (SPLB)
                          






NOTES


1) Queue manager must be installed in the Master Workstation.

2) Spooler is installed in each work station that has a printer attached. Splcnfg.Sys file identifies which Queue and Printer this work station serves.

3) Each printer has a configuration file (i.e., splconfig.sys)

4) Queue.index file contains:
               Spl[sys]<sys>Spl.Queue11
               9253Control[sys]<sys>9253Control.Queue11
               SplA[sys]<sys>SplA.Queue11
               AP1302Control[sys]<sys>AP1302Control.Queue11
               SplB[sys]<sys>SplB.Queue11
               AP1351Control[sys]<sys>AP1351Control.Queue11
               SpoolerStatus[sys]<sys>SpoolerStatus.Queue11

5) Splcnfg.Sys file contains:
               09253Spl[sys]<sys>Splconfig.Sys64Y

6) SplAcnfg.Sys file contains:
               BAP1302SplA[sys]<sys>SplAconfig.Sys64Y

7) SplBcnfg.Sys file contains:
               0AP1351SplB[sys]<sys>SplBconfig.Sys64Y

8) Using the Create Configuration File utility create 3 files:
               Splconfig.Sys, SplAConfig.Sys and SplBconfig.Sys
Queue Manager and Spooler









Lab Exercise


Objective: Correctly configure the software for a new printer.

Exercise:	Add entries to Queue.Index and SplCnfg.Sys to allow use of a new printer.

The Queue name should be SplC.

The printer name should be Laser and should print a banner.

The queue files should be on [sys]<spl>

This is a serial printer connected to communications port B.

Step 1:	Create or modify [sys]<sys>Queue.Index to add the new Spooler queue and Control queue.

Step 2:	Create or modify [sys]<sys>SplCnfg.sys to add the information for the new printer.

Step 3:	Create a hardware configuration file for the new printer called [sys]<sys>LaserConfig.Sys. The characteristics of this printer
are: 9600 baud
     7 data bits
     even parity
     XONXoff line control

Step 4:	Reboot your system or install the Queue Manager and Spooler to verify correct operation of your printer.

WRITEone  MULTIPLAN and Printers


The format of the printer description file (sys.printers) is:

PrinterName:   Printer Specification:   Letter Quality Type:   Graphics type

The PRINTERNAME field is a nickname or alias for the printer. This can be any character string such as Draft, Letter, Multi, or Oki. This name is used when specifying a printer other than Multiplan's or WRITEone's default printer.

The PRINTER SPECIFICATION field is the name which Multiplan or WRITEone provides to the operating system whenever you wish to print on a printer.

The LETTER QUALITY TYPE is the type of printer the Word Processing software is using (Diablo630 or QumeSprint9). This field is ignored by Multiplan.

The GRAPHICS TYPE is the type of graphics printer or plotter to be used by the Graphics software (OkiData, Prism or HP7475A). This field is ignored by WRITEone.

Some examples of a printer description file (sys.printers):

Example 1    Both printers are Spooled

Draft:   [Spl]:            Draft:          Prism
Letter:  [SplB]:           Diablo630


Example 2    One printer is Spooled, the other is Direct

Draft:    [Lpt]:    Draft:      OkiData
Letter:   [SplB]:   Diablo630



NOTES

If the default printer in sys.printers does not meet your requirements use the text Editor to move or edit the entry that meets your requirements to the first entry in the file.

There is a hardware configuration file associated with each printer. It has the file specification format of XXXXconfig.sys, where XXXX usually identifies the printer type. This file defines such things as the maximum print width of the printer and in the case of printers connected to the B20 serial ports what Baud Rate of the printer.

These configuration files can only be inspected or changed with the Create Configuration File command.
WRITEone  MULTIPLAN and Printers











Lab Exercise


Objective:	Modify Sys.Printers to allow users access to the new printer and change the default printer for Word Processor and Multiplan users.

Exercise:	Add an entry to Sys.Printers for the new printer installed in the previous exercise.

Step 1:	Edit Sys.Printers and add the appropriate entries for the new printer.
FILE SYSTEM



Reference BTOS Standard Software Operation Guide, Section 5



FILE SYSTEM HIERARCHY

BTOS uses a hierarchical structure for organizing files.



 VOLUME 


        
                                                                  
                  
   DIRECTORY    DIRECTORY     DIRECTORY     DIRECTORY        ETC
          
                                                    
                            
     FILE         FILE          FILE           FILE 
     FILE         FILE          FILE           FILE 
     FILE         FILE          FILE           FILE 
     etc          etc           etc            etc  
                            



[Volume]<Directory>FileName




VOLUME NAME             12 characters maximum


DIRECTORY NAME          12 characters maximum


FILE NAME               50 Characters maximum




Device Names

FILE SYSTEM

Files on the Standalone and Utilities diskettes

SysImage.Sys	The operating system

BawsSys.font	The font for a B27
t1Sys.font	The font for a B25
Sys.Cmds	The commands recognized by the Executive
SysInit.run	Runs the Sysinit.Jcl file
SysInit.Jcl	Contains the statements for installing Systems Services
SysInit.Txt	Contains the text to be displayed while SysInit.Run is executing
Sys.Keys	Keyboard table for a K1 keyboard
K2Sys.Keys	Keyboard table for a K2 keyboard
K3Sys.Keys	Keyboard table for a K3 keyboard
Sys.Printers	Contains the user friendly names of the system printers
Signon.run	Executes the statements in the .user file
Signon.txt	Text displayed at Sign on
DtConfig.Sys	System date and time configuration file

.User	The default .user file

BackupVolume.Run	Run file for the Backup Volume command
Batch.Run	Run file used by SysInit.Run to install the programs contained in SysInit.Jcl
Bootstrap.Run	Run file for the Bootstrap command
ChgVolName.Run	Run file for the Change Volume Name command
Command.run	Run file for New Command and Remove Command
Config.Sys	Contains information about the Cluster line speed and XBus window size
CmdFileEditor.Run	Run file for the Command File Editor command
CreateConfig.Run	Run file for Create Configuration File
Exec.run	Run file for Executive
Editor.Run	Front end of the Edit command
t1Editor.Run	Run file for a B25 Edit command
Files.run	Run file for Files Command
Floppycopy.run	Run file for Floppy Copy Command
Format.Run	Run file for the Format command
Dump.Run	Run file for the Dump command
InstallQMgr.Run	Run file for the Install Queue Manager command
Queue.Index	Contains a list of Queues that the Queue Manager will control
QueueMgr.Run	System Service (resident) part of the Queue Manager
InstallSpl.Run	Run file for the Install Spooler command
SplCnfg.Sys	Contains information about the spooled printers in the cluster
Spooler.Run	System Service (resident) part of the print Spooler
LptConfig.Sys	Parallel printer hardware configuration file
PtrBConfig.Sys	Serial printer hardware configuration file
IVArchive.Sub	Initialize Archive Volume submit parameters
IVolume.run	Run file for Initialze Volume Command
LCopy.Run	Run file for the LCopy command
Restore.run	Run file for Restore command
FILE SYSTEM

MakeTxlFile.Run	Run file for Make Printer Translation File
PartitionStatus.Run	Run file for the Partition Status command
PLog.Run	Run file for the PLog command
Print.Run	Run file for the Print command
SelectiveBackup.run	Run file for Selective Backup Command
SetDirectoryProt.Run	Run file for Set Directory Protection
SetTime.run	Run file for Set Time Command
Sort.run	Run file for Sort Command
Sys.Version	An audit trail of all the BTOS software loaded to the system
SubCmd.Run	Allows submit files to be commands for Exec.
Submit.run	Run file for Submit Command
UserFileEditor.Run	Run file for User File Editor
UserFileTemplate.Sys	Template file for the User file editor
VolumeStatus.run	Run file for Volume Status Command


Notes

The following files exist on every disk and can not be removed. They should not be copied to another volume as the information they contain pertains only to the volume where they reside.

Mfd.Sys	Master file directory.
Contains a list of all of the Directory names. The maximum number of directories on a volume is determined when a disk is initialized by the parameter in the IVolume form '[Max.directories]'.

FileHeaders.Sys	Contains a list of all the files on disk. The maximum number of files a disk can contain is determined by the size of this file. There is one sector reserved for information for each file. The size of this file is established ONLY when a disk is initialized. The parameter in the IVolume command '[Max. files on volume]' determines the size of this file.

BadBlk.Sys	A list of nonusable sectors. This information is entered in the Ivolume command parameter [Bad Spots] or is updated when IVolume finds a bad spot during a surface test.

SysImage.Sys	The Operating System resides in this file. If this is NOT to be a system disk the value in the IVolume form for [System Image] should be zero.

CrashDump.Sys	Contains a memory dump after a system crash.

Log.Sys	Log for System Errors. Use the PLog command to display or print the log.


File naming conventions
FILE SYSTEM









Lab Exercise


Objective:	Copy files between volumes.

Exercise:	Copy the files you have customized to a floppy disk. These will become your backup copies or a custom installation diskette.

Step 1:	Create a new directory on a floppy disk. Name this directory CUSTOM.

Step 2:	Copy your customized files to the new directory on the floppy.

The .User file

The unique Sys.Cmds file.

Queue.Index

SplCnfg.Sys

LaserConfig.Sys
IVOLUME PARAMETERS

IVolume
  Device name                     ________________________________
  [Device password]               ________________________________
  Volume name                     ________________________________
  [Volume password]               ________________________________
  [System Image (default = 384)]  ________________________________
  [Log file (default = 2)]        ________________________________
  [Crash file (default = 0)]      ________________________________
  [Max. directories]              ________________________________
  [Max. files on volume]          ________________________________
  [Primary file headers only?]    ________________________________
  [Max. files in Sys Directory]   ________________________________
  [Sys Directory password]        ________________________________
  [Write protect Sys Directory?]  ________________________________
  [Suppress format of medium?]    ________________________________
  [Surface tests]                 ________________________________
  [Debug?]                        ________________________________
  [Log file]                      ________________________________
  [Extended floppy tracks?]       ________________________________
  [Hard disk type code (def = A)] ________________________________
  [Bad spots (See Documentation)] ________________________________







Lab Exercise


Objective:	Initialize disks with the correct parameters. The parameters are determined by how the disk will be used.

Exercise:	Initialize a floppy disk as a System disk, a data disk and as an archive disk. Use the Volume status command to verify the results.

Step 1:	Use the Ivolume command and create a system disk.

Step 2:	Use the Ivolume command and create a data disk.

Step 3:	Use the Ivolume or IVArchive command and create an archive disk.

LCOPY PARAMETERS

LCopy
  File list              ________________________________
  [File prefix(es) from] ________________________________
  [File prefix(es) to]   ________________________________
  [File suffix(es)]      ________________________________
  [Overwrite OK?]        ________________________________
  [Confirm each?]        ________________________________
  [Continue on error?]   ________________________________
  [Verify copy?]         ________________________________









Lab Exercise


Objective:

Exercise:

Passwords



Reference BTOS Standard Software Operation Guide, Section 6



Password protection is available at three levels:

         Volume,

         Directory, or

         File.

A VOLUME PASSWORD protects a Volume.
A DIRECTORY PASSWORD protects a directory on a volume.
A FILE PASSWORD protects a file in a directory on a volume.

Volume passwords are assigned with the IVolume Command when a disk is initialized, or with the Change Volume Name Command.

Directory passwords are assigned with the Create Directory and Set Directory Protection Command.

File passwords are specified with the Set Protection utility.



The Change Volume Name command


Lab Exercise


Objective:	Correctly implement password security on disks.

Exercise:	Password protect a floppy disk, and verify directories and files cannot be accessed without a password.

Step 1:	Use the Change Volume Name or IVolume command and assign a volume password to your floppy disk.

Step 2:	Create a directory on the floppy that requires a password to modify files in this directory but does not require a password to read files.

Step 3:	Create a directory on the floppy that requires a password to modify and read files in this directory.

Step 4:	Verify correct operation of your passwords.
BACKUP PROCEDURES

BACKING UP FILES ON THE HARD DISK

The SELECTIVE BACKUP command backs up (copies) individual files or directories from the winchester to a floppy, thus allowing archiving of personal files and requiring only read access to the files being archived.

You must have the floppy disks already initialized (IVolumed) before you begin the backup.  To simplify the Selective Backup procedure, IVolume your floppy disks with a volume name of ARCHIVE or use the IVArchive command to create (initialize ) the floppy disks.

Consult the B20 Software Operations Guide for information on how the fill in the Selective Backup command form.


NOTE

Selective Backup is MUCH FASTER that a normal copy.

The Selective Backup command stores the  backed up files on the floppy disk(s) in a special way. Backed up floppies CAN NOT be inspected with the Files command to see what is on the floppy because of the special way the files are backed up.



RESTORING FILES TO THE HARD DISK

The RESTORE command restores files to the winchester disk drive that have been BACKED UP using the Selective Backup command.

Consult the B20 Software Operations Guide for information on how to fill in the Restore command form.


NOTE

The directory information is maintained only on the first volume of the archive file. Thus, when the operation begins from a volume other than the first, Restore creates any required directory 10 sectors in size and unprotected. If 10 sectors are insufficient, create the necessary directory before beginning the Restore operation.
BACKUP VOLUME PARAMETERS

Backup Volume
  Volume or device name                             __________________________
  [Volume or device password]                       __________________________
  [Incremental from (e.g., Mon Jun 1 1981 8:00 pm)] __________________________
  [Suppress backup?]                                __________________________
  [Suppress verification?]                          __________________________
  [Archive file]                                    __________________________
  [Delete existing archive file?]                   __________________________
  [Log file]                                        __________________________
  [Display structures?]                             __________________________








SELECTIVE BACKUP PARAMETERS


Selective Backup
  File list                                         __________________________
  [Incremental from (e.g., Mon Jun 1 1981 8:00 pm)] __________________________
  [Confirm each?]                                   __________________________
  [Archive file]                                    __________________________
  [Delete existing archive file?]                   __________________________
  [Log file]                                        __________________________






RESTORE PARAMETERS

Restore
  [Archive file]              ________________________
  [File list from]            ________________________
  [File list to]              ________________________
  [Overwrite ok?]             ________________________
  [Confirm each?]             ________________________
  [Sequence number]           ________________________
  [Merge with existing file?] ________________________
  [List files only?]          ________________________
  [Log file]                  ________________________

Data recovery techniques for 301 and 329 error codes


Error Code 301  IO Error (ReadWrite Error)
May be caused by hardware or media fault. Try to read the disk in another drive. If it reads with no errors the original disk drive is bad. If you still get 301 Errors in a different drive the diskette media is bad.


Error Code 329  Floppy disk timeout
May be caused by hardware or media fault. Usually caused by defective media. Check to see if the floppy disk will spin freely in it's jacket. If the disk spins freely in it's jacket the cause of the error is probably a defective disk drive.

Some 301 errors may be caused by disks not spinning freely in their jackets. This speed variation during a SAVE can cause a 301 error.  If you continue to use the disk in this situation the 301 errors can progress to 329 errors.

For 329 errors caused by the disk not spinning in the jacket try manually rotating the disk several times to see if it will free up. Be very careful not to touch the disk in the cigar shaped cutout area of the disk jacket. If it frees up, immediately copy the disk to good media.

Any time a disk appears to be corrupted or the data not readable you should execute the BACKUP VOLUME command to recover any data on the disk that is recoverable. BACKUP VOLUME should be used even if BTOS does not recognize the disk, as Backup Volume can recover any data that is still readable on a disk.

NOTE

If you use Backup Volume have some floppy disks available that have been initialized with a Volume Name of ARCHIVE or use the Change Volume Name command and change the Volume Name to ARCHIVE. This is necessary because Backup Volume looks for a floppy disk with this name.

If you are trying to recover data from a floppy disk by using Backup Volume it will be easier if you use a DualFloppy System.

Use the RESTORE Command to retrieve data from the backed up disk. 


IMPORTANT

Make sure your path is set to the Volume where you want the data  RESTOREed to, before you execute the Restore command.

Backup and Restore (cont.)


Objective:	Backup of data and recovery of data from corrupted disks.

Exercise:	Backup and restore data from a corrupted disk.

Step 1:	Use backup volume and backup a corrupted floppy disk to your hard disk or F1 if you have a dual floppy system.

Step 2:	Restore the data to a new floppy disk.
SUBMIT FILES


Reference BTOS Standard Software Operation Guide, pages 717  20  Appendix C

Submit files can be created with the record command and then edited with the Editor or they may be created by the Editor.

Record
  File to record on      SubmitFileName.Sub



The file naming convention used is that a submit file has a suffix of '.Sub'. It is strongly recommended that you adhere to this convention.





Submit                SubmitFileName.Sub
  File list
  [Parameters]
  [Force Expansion?]
  [Show Expansion?]








Lab Exercise


Objective:	The ability to create and modify submit files and commands that use submit files.

Exercise:	Using the record command and the Editor prepare a submit file. Create a command to invoke the submit file.
JCL FILES


Reference BTOS Standard Software Operation Guide, pages 417


$JOB Init
$RUN [sys]<sys>InstallQMgr.Run
$RUN [sys]<sys>InstallSpl.Run
$END















Objective:	Add and remove entries in JCL files.

Exercise:	Add an entry to the JCL file to install the spooler.
CLUSTERING CONCEPTS

Cluster (Slave) WorkStation

A cluster workstation is a B25 workstation connected via special (cluster) cable to other B25s in a local network. One of the B25s in the cluster is designated as the master, determined by the Operating System (master) this workstation uses. The other workstations are all cluster workstations or slaves. All communications between the workstations are controlled and routed through the master workstation. A Slave cluster workstation loads all of it's programs from the master's hard disk. If it has any local disk they are only used for data storage.

Free Slave Clusters

A free slave cluster has a hard disk and loads the programs that it uses most often from this disk. This gives a free slave the performance of a standalone system with resource sharing advantages of a cluster workstation. A free slave has the basic B25 standalone software loaded to it's hard disk and then a cluster workstation Operating System is copied over its standalone Operating System.

Resource Sharing

B20 workstations may be clustered together to provide computer resource sharing. The resources that may be shared include, but are not limited to:

1) The disks located at the master workstation.
2) Spooled printers attached to ANY workstation in the cluster.
3) In general, any computer resource controlled by the master workstation.

Cluster Operating System naming conventions

	B25 no disk	B25 dual floppy	B25 Hard disk

At master	Ws252>SysImage.Sys	Ws251>SysImage.Sys	Ws250>SysImage.Sys

Local		SysImage.Sys	SysImage.Sys

Actual Name	t1ClstrSp.Run	t1ClstrLfsSp.Run	t1ClstrLfsSp.Run


The Sys Volume

The volume Sys is a special volume name and applies to the disk from which a workstation loaded (bootstraped) it's operating system. The Sys volume can be a floppy disk, a hard disk or a disk located at the master workstation. 

For free slaves, their local hard disk is the Sys volume. To refer to a volume located at the master, prefix the volume name with an . For example [Sys], pronounced Bang Sys, is the Sys volume located at the master. [d0], [f0] and [Chas] all refer to volumes located at the master workstation.
CLUSTERING CONCEPTS


To force a B20 to BOOT from the master


Turn power on or press the RESET button at the rear of the CPU while holding the space bar down. Release the space bar when you see the letters separated by commas.

  The B25 workstation will display
  B,C,D,L,M,P,T
  Depress T <Return>

  The B25 workstation will display
  OS:
  Depress nnn <Return>         nnn = WS nnn >SysImage.Sys *
  Depress B

  The workstation will now boot from the cluster Communications line as long as the Master Workstation has the file WSnnn>SysImage.Sys.



  * nnn is 125 for a B27 with a hard disk
    nnn is 126 for a B27 with dual floppy disks and no hard disk.
    nnn is 127 for a B27 with no disk

  * nnn is 230 for a B38 with a hard disk
    nnn is 231 for a B38 with dual floppy disks and no hard disk.
    nnn is 232 for a B38 with no disk

  * nnn is 240 for a B28 with a hard disk
    nnn is 241 for a B28 with dual floppy disks and no hard disk.
    nnn is 242 for a B28 with no disk

  * nnn is 250 for a B26 with a hard disk
    nnn is 251 for a B26 with dual floppy disks and no hard disk.
    nnn is 252 for a B26 with no disk

  * nnn is 253 for a B214,5,6
    nnn is 254 for a B212,3
    nnn is 255 for a B211

POWER ON SEQUENCE OF EVENTS


1) Power on.

2) Bootstrap ROM
            a) performs system confidence routines
            b) loads Operating System from disk or communications line.

3) Operating System
            a) performs system confidence routines
            b) initializes hardware and calls SysInit.Run.

4) SysInit.Run 
            a) displays most recent Crash Status
            b) displays SysInit.Txt if it exists
            c) runs Batch stream contained in SysInit.JCL
            d) calls SignOn.Run

5) SignOn.Run
            a) displays most recent Crash Status
CLUSTERING CONCEPTS


            b) displays SignOn.Txt
            c) displays SignOn form
           	d) checks attempted access to the system by users when they begin
               operations and accepts the system configuration (User name) 
               each user uses. (The .user file is User name.user)

6) What happens next is dependent on the contents of the .user file. 
   (SignOnChainFile or SignOnExitFile)








Lab Exercise


Objective:	The ability to cause a free slave cluster to boot from its local disk or from the Master (for diagnostic purposes).

Exercise:	1. Use of the cluster status command.
2. Make a free slave cluster boot from the master workstation.
ISAM

Indexed Sequential Access Method is a software product that provides efficient and flexible random access to data located on disk. Data base programs like RBase and advanced programs like Application Development System (ADS) use ISAM to store and retrieve data.

Features of ISAM

   o  shared or exclusive access to ISAM data sets, with transaction and record or data setlevel locking

   o  an ISAM server installed in memory at the master workstation of a cluster or at a standalone workstation.


ISAM in a cluster system

The ISAM server software must be loaded into the master workstation.
All ISAM data sets must reside on the master's hard disk, because the ISAM server software is only in the master workstation.