OS/2 Professional/OS2PRO194.ISO/os2/wps/disk/psns2/manual.inf

OS/2 Help File | 1993-03-30 | 198.5 KB | 3,262 lines

ΓòÉΓòÉΓòÉ 1. Version Notice ΓòÉΓòÉΓòÉ

Third Edition (Spring 1993)

It is possible that this product may contain reference to, or information
about, concurrent products (machines or programs), programming or services that
are not announced in your country.  Such references or information must not be
construed to mean that IBM will announce such IBM products, programming or
services in your country.

This product may contain examples of data used in daily business correspondence
and operations.  In these examples we use names of hypothetical businesses and
persons.  These names are fictitious and any similarity to names of actual
businesses and persons is purely coincidental.

This product could contain technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of this product.

Requests for copies of this product and for technical information about the
system should be made to your authorised IBM Personal Computer dealer.  All
rights reserved.


ΓòÉΓòÉΓòÉ 2. Notices ΓòÉΓòÉΓòÉ

References in this publication to IBM products, programs or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
of IBM's intellectual property rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, is the user's
responsibility.

IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to the IBM Director
of Commercial Relations, IBM Corporation, Purchase, NY 10577.


ΓòÉΓòÉΓòÉ 2.1. Trademarks and Service Marks ΓòÉΓòÉΓòÉ

The following terms, denoted by an asterisk (*), used in this publication, are
trademarks or service marks of IBM Corporation in the United States or other
countries:

AS/400                             Personal System/2 (PS/2)
IBM                                Presentation Manager
IBM Personal Computer              SAA
OS/2                               System/370


ΓòÉΓòÉΓòÉ 3. Introduction ΓòÉΓòÉΓòÉ

This guide is divided into an introduction and three parts.

o Part 1. Introduction is a brief overview of PSnS/2.

o Part 2. User's Guide covers the installation and configuration of PSnS/2
  along with its most commonly used features. It is divided into four main
  areas:

   - Installing PSnS/2

   - Configuring PSnS/2

   - Taking Manual Backups

   - Restoring Data

o Part 3. The Technical Reference is provided for users in need of more
  detailed information or system administrators in charge of a networked system
  on which PSnS/2 is installed.

  It provides a reference for all the technical information on PSnS/2, and all
  the available options which are not described in the User's Guide. For most
  purposes however, information on how to use PSnS/2 will be given in the
  User's Guide and the online help windows.

o Part 4. Appendixes cover the following areas: c.

   - Outline of hardware and software requirements

   - Using PSnS/2 windows

   - Specifying patterns for file and directory matching.


ΓòÉΓòÉΓòÉ 4. Welcome to PSnS/2 ΓòÉΓòÉΓòÉ

At some stage in their use of personal computers, most people have experienced
losing files and data - often through no fault of their own. Each time disaster
strikes, people make resolutions to take more backups but unfortunately they
hardly ever follow them through for long.

The aim of PSnS/2 is to resolve this problem by backing up your files for you.
PSnS/2 is designed to do the tedious job of performing backups. Once you have
set up PSnS/2, most of its work will take place almost unnoticed, until you
have to restore lost files.

Another advantage of PSnS/2 is that it is able to manage the storage of backed
up files on many different devices ranging from, for example, diskettes, fixed
and optical disks to file servers and host computers connected by LANs, saving
you even more time.

Finally, PSnS/2 supports all the features of OS/2* 1.2 and above, including the
High Performance File System (HPFS). PSnS/2 supports long file names and
directory names, as well as backing up and restoring Extended Attributes (EAs).
The special needs of OS/2 2.0's Workplace Shell, User and System files are
likewise catered for.

PSnS/2 is easy to use even if you have little experience with computers. Most
of the time you do not have to deal with it directly but when you do run the
main program all of the windows which you see are designed in the same way as
many other OS/2 Presentation Manager* products. Thus, if you have used such
products before, it should not be too difficult to get to know this one.


ΓòÉΓòÉΓòÉ 5. Major Features ΓòÉΓòÉΓòÉ

PSnS/2 has many features:

It performs backups automatically, in "background"
   This is the main benefit of using PSnS/2. OS/2 allows more than one program
   or application to run at the same time; this is called multitasking. PSnS/2
   takes advantage of multitasking by checking for files to back up even when
   you are running other programs. This makes it easy to keep your PC fixed
   disk files safe. You do not have to remember or discipline yourself to take
   backups because PSnS/2 does it automatically, at whatever intervals you set.

Single, automatic daily backups are available
   You can use PSnS/2 to perform a backup at a specific time of day: to
   diskettes or a tape backup device before closing down your PC, for example,
   or to a central file server. In the latter case, you might like to arrange
   for this to happen when only a few people are using the system, such as at
   lunchtime or after everybody has gone home.

Automatic management of backed up files
   Once you designate how backups are stored, PSnS/2 manages their backup and
   retrieval.

It only backs up all those files you tell it to
   You do not waste valuable storage space and time on unnecessary backups.

Full support for OS/2 Version 1.2 and above HPFS and Extended Attributes
   Disks which use the OS/2 Version 1.2 High Performance File System, and files
   which use the Extended Attributes introduced in OS/2 Version 1.2 are fully
   supported. Long file names and long directory names on files being backed up
   or restored are also fully supported. Files with Extended Attributes are
   also backed up and restored along with the file itself.

It can be customised to your personal needs
   A great deal of customisation is possible so that you can tailor a version
   of PSnS/2 to your exact requirements for file checking and file restoring
   from backups. Some of the customisation may have to be performed by the
   system or network manager.

Extensive online help is available on every window
   The help given is always relevant to the window that is displayed.

It imposes standards for backing up across networks
   PSnS/2 has special files to control which files should be backed up. These
   can be shared over a network, so that you can make sure everybody's work is
   safeguarded.


ΓòÉΓòÉΓòÉ 6. How PSnS/2 Works ΓòÉΓòÉΓòÉ

This summary of how PSnS/2 works should be read before you install PSnS/2. If
you are unsure about some of the terms used here because you do not have much
computer experience, please use the glossary at the back of this manual.

PSnS/2 is a continuously running task under OS/2. At intervals which you
determine, it scans the directories and files on the hard disk (or disks
accessible by the machine on which it is running) and checks for files which
have been changed

When PSnS/2 finds a file which has changed, it puts it on the "Files spotted
for backup" list. After it has checked all the disks, PSnS/2 consults the
"trigger level" - another parameter set by the user - to see if it should back
up these files. This type of backup is called an automatic backup.


ΓòÉΓòÉΓòÉ 6.1. Backup Modes ΓòÉΓòÉΓòÉ

PSnS/2 can operate in one of two automatic backup modes:

Periodic
   PSnS/2 checks directories for new or changed files at intervals you specify.

Timed start
   The directories are checked at a specific time of day.

In addition to automatic backups, you may back up files manually using the
PSnS/2 menu system.

There are three types of manual backup:

Full manual backup now!
   All files PSnS/2 knows of, whether changed or not, will be backed up.

Files spotted
   All the files that PSnS/2 has spotted as changed will be backed up.

By pattern
   You can choose to backup a group of files according to your own
   requirements.

PSnS/2 knows which files you want backed up, and where to back them up to, by
means of special control files called rulebooks, which are described below.


ΓòÉΓòÉΓòÉ 6.2. Rulebooks ΓòÉΓòÉΓòÉ

There are two types of rulebook, local and global. You may have no more than
one of each type in use (that is, being used by PSnS/2 to control backups) at
any time. There must always be a global rulebook in use. Global rulebooks are
commonly used by groups of users on networked systems to ensure that they all
back up their most important files. Local rulebooks are optional and are
intended for use by individual users to ensure that their important personal
files are backed up.

Each rulebook contains one or more rules telling PSnS/2 which files it should
backup and where. Each rule is of the format:

<a group of files specified by pattern>  <drive letter>

If you are unsure about specifying files by pattern then refer to Specifying
Patterns for File and Directory Matching.

The <drive letter> might, for example, be C if you are backing up to a fixed
disk. It may also be set to [none] which means that PSnS/2 will not back up the
specified files.

By default, PSnS/2 checks the global rulebook before the local rulebook. This
can, however, be changed by the user.


ΓòÉΓòÉΓòÉ 6.3. Help ΓòÉΓòÉΓòÉ

You can always get help when running the PSnS/2 program. The immediate help is
always relevant to the window being displayed. You can also get more general
help whenever you require it by selecting the Help pushbutton if one appears on
the window you are using, or pressing the <F1> key.

You can always return to this guide for more detailed information.


ΓòÉΓòÉΓòÉ 7. User's Guide ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 8. Installing PSnS/2 ΓòÉΓòÉΓòÉ

If you are unsure whether PSnS/2 will run on your system, see Outline of
Hardware and Software Requirements.

The following sections describe how to install PSnS/2 on your fixed disk. Once
you have done this, you should turn to Initial Configuration of PSnS/2.

To get PSnS/2 running on your computer, you must install from the installation
diskette or diskettes that come with PSnS/2.

There are three steps to installing PSnS/2: c.

 1. Setting options and copying from diskette

 2. Modifying some OS/2 system files (OS/2 v1.2 or 1.3)

 3. Configuring your Backup Rulebooks, which tell PSnS/2 what to back up.


ΓòÉΓòÉΓòÉ 8.1. Running the Installation Program ΓòÉΓòÉΓòÉ

Start your computer and peripheral devices, external diskettes, LAN servers and
so on, and wait for the system to finish starting up. Select a diskette drive
and insert the diskette labelled PSnS/2 INSTALL.

With the mouse, open the drive object for the diskette drive you wish to use
(e.g. drive A) and select the PSNSINST object. With the left mouse button,
double-click PSNSINST and the installation program for PSnS/2 will begin to
run.

PSnS/2 is now ready to start installation, and the first installation panel is
displayed.


The First Installation Panel


ΓòÉΓòÉΓòÉ 8.1.1. Setting Options and Copying from Diskette ΓòÉΓòÉΓòÉ

In the first installation panel select the OPTIONS button and click it with
your mouse or press the letter "O" on the keyboard. This will take you into the
second, Installation Options panel of the PSnS/2 INSTALL program.


The Installation Options Panel

It is reccommended that you accept all the default settings. In particular, you
should ensure that the Sample Rulebooks checkbox has been selected. Otherwise,
the rulebook you specified (GENERAL, or your company rulebook) will not be
installed. Select any additional features, such as Host computer or Tape backup
support, by clicking the relevant checkboxes.

Here are some more notes to help you.

o Paths The default will be fine for most purposes. Please ensure that the
  entry for Help text points to a directory included in the SET HELP statement
  in your current CONFIG.SYS file.

o Rulebooks. Until you have created some of your own rulebooks, use the sample
  rulebooks provided by the Installation diskette (unless you have been
  provided with another one to use).

  If you are using PSnS/2 on a LAN, your company may have created a global
  rulebook for you to use, and placed it on your installation diskette.

  If you already know the name of the global rulebook you are going to use, you
  must:

    1. Make sure the rulebook is present in the \SAMPLE subdirectory of the
       INSTALL diskette

    2. Type <rulebook name> in the Global entry field of the Rulebooks section
       on the Installation Options Panel. (<rulebook name> is the name of the
       rulebook you want to use).

  If however you do not know the name of the global rulebook you are going to
  use, type GENERAL in this field or accept the default.

o Recovering PSnS/2 control files. If this is the first time you have installed
  PSnS/2, do not select this checkbox. You would only select it if, for
  example, you had to reinstall PSnS/2, if you lost the control files
  accidentally, perhaps because you had reformatted the disk on which you store
  PSnS/2

o Configuration-Update CONFIG.SYS This checkbox concerns users of OS/2 v1.2 or
  1.3 only.

  Having made all your selections, click OK to accept the settings or Cancel to
  reject them and you will return to the first installation panel From the
  first installation panel select Install to proceed to the installation of the
  PSnS/2 program files on to your fixed disk, or Cancel to abandon the
  installation process altogether.


ΓòÉΓòÉΓòÉ 8.1.2. Modifying OS/2 System Files (OS/2 version 2.0) ΓòÉΓòÉΓòÉ

If you are running OS/2 v2, then you must add PSnS/2 to your STARTUP folder
once the installation process is complete. The following section has
instructions on how to do this.

The operating system automatically remembers which applications are running
when it is shut down. Therefore, if PSnS/2 is left running, it will always
start when you reboot.

However, if PSnS/2 is shut down and you want it to start automatically with
OS/2, you must make a shadow of PSnS in your Startup folder:

 1. Select the Drive which PSnS is on.

 2. Select the PSS folder.

 3. Select the Code folder.

 4. Select the Startup folder from the OS/2 system folder.

 5. Press and hold Control and Shift and the right mouse button, and drag the
    PSnS/2 icon to the Startup folder.


ΓòÉΓòÉΓòÉ 8.1.3. Modifying OS/2 System Files (OS/2 version 1.2 or 1.3) ΓòÉΓòÉΓòÉ

STARTUP.CMD, is a special file in OS/2 which contains commands to be executed
every time the computer is started. You must modify STARTUP.CMD so PSnS/2 will
run automatically, every time you start your computer.


ΓòÉΓòÉΓòÉ 8.1.3.1. Changing STARTUP.CMD Manually ΓòÉΓòÉΓòÉ

To make sure PSnS/2 starts up every time you boot-up your computer:

o Add an OS/2 start command to your STARTUP.CMD file.

o If your STARTUP.CMD is an OS/2 command batch file, you should add this line:

    'start "PSnS/2" c:\pss\code\pss.exe'

o If your STARTUP.CMD is written in REXX/2, you should add this line:

    'start "PSnS/2" c:\pss\code\pss.exe'


ΓòÉΓòÉΓòÉ 9. Initial Configuration of PSnS/2 ΓòÉΓòÉΓòÉ

In order to configure PSnS/2 you must return to the desktop. The Install
program will have started PSnS/2 and the PSnS/2 main menu window will appear:


The PSnS/2 Main Menu Window

Note:  Under OS/2 v1.2 or 1.3, the panel at the bottom of the screen will say
Version 2.10 for 16-bit OS/2.

If the menu does not appear, refer to Diagnostics. If this is the first time
you are using an OS/2 Presentation Manager menu-driven program, or you are
unsure of how to use one, refer to Using PSnS/2 Windows.


ΓòÉΓòÉΓòÉ 9.1. Backing up control files ΓòÉΓòÉΓòÉ

When you have installed PSnS/2, the first thing you should consider is storage
of the PSnS/2 control files.

The PSnS/2 control files take a record of filenames and directories which are
used for files backed up. They can be saved either on hard disk or diskette.

Note:  If the control files are stored on hard disk, and the disk is
reformatted (or crashes), then the files will be lost.  PSnS/2 will not be able
to recover your files, even if they have been backed up to removable volumes.
Please ensure that you either:

o Back control files up to diskette.

o Back up to diskette before you reformat your hard disk partitions.

The default destination for backing up control files is the C drive. To change
this default refer to Rulebook Configuration.


ΓòÉΓòÉΓòÉ 9.2. PSnS/2 Configuration ΓòÉΓòÉΓòÉ

When the control files have been dealt with, other aspects of PSnS/2 can be
configured.  All these choices are optional.

Non-OS/2 supported drive configuration
   If a drive which you want PSnS/2 to back up files to, is a non-OS/2
   supported drive, for example an optical disk, read Specifying Drive
   Configurations.

   Your drive is directly supported by OS/2 if the normal OS/2 commands such as
   DIR and COPY work for that drive.

Removable volume configuration
   If you want to back up files to diskette or some other removable volume
   (such as an optical disk or tape drive), read Removable Volume
   Configuration.

Rulebook configuration
   If you do not wish to use the rulebook which PSnS/2 is set up to use (the
   one you selected during installation), refer to Rulebook Configuration.

Backup mode configuration
   When PSnS/2 is first installed it assumes that you want it to check your
   files at regular 15 minute intervals. If you want it to check more
   frequently or less frequently or if you want it to check only at a
   particular time of day, you should refer to Backup Mode Configuration.

When you have carried out these steps, PSnS/2 will be running as you want it on
your system: ready to back up the files you have chosen to the correct place.
In order to ensure that everything is working correctly, read Verifying
Installation.

You may now wish to take an initial backup of some of the files on your disk.
If you do, refer to Taking Manual Backups.

With installation and configuration complete, you can now look forward to using
your computer safe in the knowledge that PSnS/2 is keeping all the files you
value "Safe and Sound".


ΓòÉΓòÉΓòÉ 10. Specifying Drive Configurations ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 10.1. Viewing the Disk Drive Details ΓòÉΓòÉΓòÉ

If you want to use another disk drive that is not supported by OS/2, (**)
select the Drives option from the Setup pull-down on the PSnS/2 main menu.  The
Drive Letter Details window appears.


ΓòÉΓòÉΓòÉ 10.1.1. Drives Letter Details Window ΓòÉΓòÉΓòÉ

This window allows you to change and add information about the drives.


The Drive Letter Details Window

All the drive letters that PSnS/2 knows are shown in the Letters  list box.

To find information out about it, select a drive using the mouse or the cursor
keys.

For standard OS/2 drives, the command fields will be blank. Standard OS/2
devices are, for example: c.

o Fixed disk drives

o Diskette drives

o Network drives.

Non-OS/2 supported devices such as host processor systems, some optical disk
drives and tape backup systems may only send or receive data using commands
that are not part of OS/2.


ΓòÉΓòÉΓòÉ 10.2. Adding New Backup Devices ΓòÉΓòÉΓòÉ

If you want to add drives that are not directly supported by OS/2, select the
Add button from the Drive Letter Details window to display the Tell PSnS/2
about a new drive window.


Adding A New Drive Letter

Type a drive letter for the new drive, in the range A-Z. Do not choose a letter
belonging to your computer's standard drives, even if it has not been used yet.

To specify the type of device that you wish to back up to, select one of the
radio buttons shown in the panel.

Three check boxes are displayed:

o The volumes in the drive can be changed by the user
  This tells PSnS/2 that volumes such as diskettes can be changed, if
  necessary. PSnS/2 then knows that it should maintain a list of the backup
  volumes used in this drive, diskettes used for backup in the diskette drive,
  for example.

o Drive is directly supported by OS/2 commands drives. You must type in the
  commands to back up files to and restore files from this drive. The section
  Commands to Drives Not Directly Supported by OS/2 below describes how to
  compose these commands.

o Files should be batched when they are backed up to this drive

After adding the new drive letter, select OK and you will be returned to the
Drive Letter Details window.

If you decide not to add a new drive letter, select Cancel and you will be
returned to the Drive Letter Details window

If you want to abandon all the changes you have made, select Cancel from the
Drive Letter Details window and you will be returned to the PSnS/2 main menu.


ΓòÉΓòÉΓòÉ 10.2.1. Commands to Drives Not Directly Supported by OS/2 ΓòÉΓòÉΓòÉ

These commands can be edited in the Drive Letter Details window.

Commands for backing up files to and restoring files from non-OS/2 supported
drives are compulsory, whereas the command for deleting a backup copy is
optional.

You may want to specify a delete command if the command you are using to back
up files does not automatically overwrite existing versions of those files.

The commands must be used for all backing up of files. Because PSnS/2 will use
these commands on many different files, you must use tokens to represent parts
of the command. PSnS/2 will substitute the necessary file identifiers when the
commands are needed. Following is a description of the tokens:

&s  The full drive, path, name, and extension of the file to be backed up. This
    is the source file.

&t  The full drive, path, name, and extension for the backup copy PSnS/2 will
    make. This is the target file. The parts of this name are available as
    tokens as well.

   &d  The drive letter of the target file (with no colon). This is the letter
       which you specified in the Drive letter details window.

   &n  The file name of the target file (without a dot). This name is made up
       by PSnS/2 and will consist of four alpha-numeric characters in the range
       A-Z or 0-9.

   &x  The file extension of the target file (without a dot). This will be two
       digits made up by PSnS/2 in the range 0-99.

For example, a command to communicate with the non-OS/2 supported drive might
be:

MYCOPY [orig spec] [new spec]
size=5p6.

[orig spec] represents the complete file specification of the file being
          copied.

[new spec] represents the complete file specification of the copy being made.

You could type the backup command as:

MYCOPY  &s  &t

The restore command is then:

MYCOPY &t &s

When using the commands, PSnS/2 substitutes the file identifiers for the tokens
you supplied.

For example, if the original file was C:\SMP\FILE.EXE and the backup file is
ABCD.01, then:

&s  is  C:\SMP\FILE.EXE

&t  is  X:\PSSBKP\USER\ABCD.01

&d  is  X

&n  is  ABCD

&x  is  01

Note:  Make sure that the tokens you supply will give enough information for
the files to be processed as you intend. Using the above example, if you had
typed:

MYCOPY  &s  &n

your file would be backed up without the extension on the target file name.
PSnS/2 would not be able to recover the file.

To delete backed up files, the only tokens you can use in the delete command
are &t, &d, &n, and &x. You only need the delete command if the backup and
restore commands do not delete the files automatically. You would use the
delete command if you wanted to delete old generations of backups, for example,
if you had the fourth generation and were only requested to keep three
generations.

The commands must either be in the current path or you must specify the
complete path name, including drive, path, and file name. For example:

D:\DIR1\MYCOPY

Note:  The path is a OS/2 environment variable which is set up in your
initialisation files. For details of the use and function of path, consult your
OS/2 documentation.


ΓòÉΓòÉΓòÉ 10.2.1.1. Example of Commands For a Non-OS/2 Supported Drive ΓòÉΓòÉΓòÉ

This is an example of how to specify backup and restore commands to backup
files to a VM/CMS host system. You cannot use the standard SEND and RECEIVE
commands, because of restrictions in the OS/2 Extended Services. Instead, use
PSSSEND and PSSRECV.

These are only examples, consult the documentation for your own equipment.

The backup command could be:

PSSSEND  &s  a:&n  &x

The restore command could then be:

PSSRECV &s a:&n &x


ΓòÉΓòÉΓòÉ 10.3. Deleting a Drive ΓòÉΓòÉΓòÉ

Select the drive you want to delete from the list box by using the mouse or the
cursor keys. Select the Delete button from the Drive letter details window and
a dialog box will appear asking you to confirm the deletion.

Note that PSnS/2 will let you delete any drive from this list box. However, if
the drive you delete is used in the active rulebook or it is fundamental to the
operation of the program, then it will be added back to the list automatically.


ΓòÉΓòÉΓòÉ 11. Removable Volume Configuration ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 11.1. Informing PSnS/2 about Removable Volumes ΓòÉΓòÉΓòÉ

If you are using removable storage media, such as diskettes for storing
backups, you must tell PSnS/2.

Select the option Removable volumes from the Setup pull-down on the PSnS/2 main
menu to see what removable storage media are already available to PSnS/2. The
List of Removable Volumes window appears.


ΓòÉΓòÉΓòÉ 11.1.1. The List of Removable Volumes Window ΓòÉΓòÉΓòÉ

This window allows you to see information about removable volumes that PSnS/2
knows about. With this window, you can: c.

o Add new removable volumes and details

o Delete removable volumes

o Refresh removable volumes

o Assign a specific number to a removable volume.

The List of Removable Volumes window contains a list box showing the
identifying numbers for each removable volume. One of the numbers on the list
will always be highlighted. The home drive letter and the number of kilobytes
of free space on the highlighted volume appears next to the volume number.
Select any removable volume by scrolling up and down the list box using the
mouse or cursor keys.


The List of Removable Volumes Window

When you are finished with the window, click on OK to save your selections and
return to the PSnS/2 main menu. Select Cancel if you wish to discard what you
have done and return to the PSnS/2 main menu.


ΓòÉΓòÉΓòÉ 11.1.1.1. Adding New Removable Storage Volumes ΓòÉΓòÉΓòÉ

PSnS/2 must know about any removable storage medium you intend to use for
storing backup files. It must be able to identify each storage medium so it can
ask you to insert a particular one when it needs it.

Make sure you mark each volume you define with the identifying number you are
told it has been given by PSnS/2.

To update the list of removable volumes, you can:

o Let PSnS/2 ask for new volumes when it needs them; for example if PSnS/2 runs
  out of space on the removable volumes whilst performing a backup.

o Prepare some volumes in advance; for instance when you select the Add button
  from the List of Removable Volumes window.

In either case, the Allocate a volume for PSnS/2 to use window appears (see
"Figure: The Add New Removable Volume Window").

Note:  You cannot prepare diskettes which are to be used for backups of PSnS/2
control files in advance. PSnS/2 will ask for these when it needs them.


The Add New Removable Volume Window

Type in a drive letter for the new volume. If you have several drives of the
same type, each removable volume you add will only be used by the drive for
which it was defined. The number PSnS/2 intends to assign to the new volume is
shown immediately below the box displaying the relevant drive letter.

If you are adding a volume for an OS/2-supported drive, you can either have the
volume formatted by PSnS/2 or, if you have a pre-formatted volume, you can ask
PSnS/2 to find out how much free space there is automatically, by selecting the
relevant checkbox.  If you are adding a volume for a drive that is not
supported by OS/2 then you must enter the size, in kilobytes, of the removable
volume that you are using.

When you are ready, select OK and the new volume will be added to the list. You
will be asked to place the volume in its drive if the drive is OS/2-supported.
PSnS/2 will display the new identifying number and ask you to write the number
on the label of that particular volume immediately.

It is recommended to mark the volume as soon as PSnS/2 asks for it in order to
avoid confusing your backup volumes with similar ones used by someone else on
your system.


ΓòÉΓòÉΓòÉ 11.1.1.2. Deleting a Removable Volume ΓòÉΓòÉΓòÉ

To delete a removable volume from the list, highlight the volume you want to
remove by using the mouse or the cursor keys and select the Delete button.

Warning: When a volume is deleted, the backups it contains cannot be restored,
because all archive records about the volume are destroyed. This includes any
files only partly backed up to the volume.


ΓòÉΓòÉΓòÉ 11.1.1.3. Refreshing All Removable Volumes ΓòÉΓòÉΓòÉ

If you are using diskettes to backup many files, then several diskettes will be
required to hold all the data that has been backed up. In order to avoid
disruption to the user while it is backing up, PSnS/2 will avoid swapping
between diskettes as far as possible. To achieve this it does not remove any
old generations of backed up files during the backup process unless they happen
to be on the diskette that is currently being used. It simply 'remembers' that
the old generation of backup is no longer needed, and deletes it the next time
the diskette the file is on is used for a backup.

You can free this space manually by selecting the Refresh button from the List
of Removable Volumes window.  PSnS/2 will then ask for each diskette in turn,
and delete any old generations of backup that are no longer needed on the
diskette.

When you have finished looking at or changing the removable volume list, select
the OK button.


ΓòÉΓòÉΓòÉ 11.1.1.4. Assigning specific numbers to removable volumes ΓòÉΓòÉΓòÉ

By default PSnS/2 does not re-assign a number it has already used to a new
removable volume even though the volume the number originally applied to has
been removed from the List of Removable volumes using Delete. Instead it
assigns a new number, incrementing by one the number PSnS/2 last assigned. In
cases where you might wish to assign a specific number to a removable
volume-wanting to replace an old diskette with a fresh one, for instance- you
can assign the number of your choice by indicating it in the Next Volume Number
selection box, using your mouse or cursor keys to control the arrow buttons
raising or lowering the number shown.


ΓòÉΓòÉΓòÉ 11.2. Using Backup Diskettes ΓòÉΓòÉΓòÉ

PSnS/2 makes it easy to use diskettes as a storage medium because it only
stores backup files on diskettes that it knows.  This means that it cannot
accidentally overwrite your own diskettes.

PSnS/2 labels diskettes electronically and checks them when you load them. If
you do insert the wrong diskette PSnS/2 displays a message to tell you to load
the correct one.

Although PSnS/2 makes it easy to use diskettes, it is recommended that you use
fixed disks whenever possible, because:

o You do not need to load and unload a fixed disk

o You might accidentally use your backup diskettes for other purposes

o It is faster to back up to fixed disks

o You have to format the diskettes

o Fixed disks are harder to lose.


ΓòÉΓòÉΓòÉ 11.2.1. Using System Diskettes ΓòÉΓòÉΓòÉ

Diskettes used to hold backups of PSnS/2 control files are called system
diskettes. They can be used to control the restoring of an entire fixed disk
that contains the PSnS/2 system. Make sure you keep system diskettes separate
from your backup diskettes.

The first time the control files are backed up to diskette, you will be asked
to insert a new diskette. The control files will then be copied to it.

You will be asked to write a label to identify the new diskette as a system
diskette, so you can find it easily the next time it is needed. Do not use
ordinary backup diskettes or any diskette containing other data as all its data
will be lost.

In the unlikely event that all the control file data will not fit onto a single
system diskette, you will be asked to repeat the procedure for another
diskette.


ΓòÉΓòÉΓòÉ 12. Rulebook Configuration ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 12.1. Introduction ΓòÉΓòÉΓòÉ

Rulebooks are special files which PSnS/2 uses to control backups. Each rulebook
contains a list of one or more rules which tell PSnS/2 which files should be
backed up and where they should be stored.

There are two types of rulebooks; global and local. You may have any number of
different global and local rulebooks, but only one of each may be active at any
time. It is compulsory to have a global rulebook active.

This chapter describes how Rulebooks can be set up to meet your personal
requirements. The topics covered are:

o The default rule options, and backup disk for control files

o Editing a rulebook

o Selecting your active rulebooks

o Testing your active rulebooks

o Creating a rulebook, either from scratch or from existing rulebooks

o Deleting a rulebook.

Select the Rulebooks option from the Setup pull-down on the PSnS/2 main menu to
display the Rulebooks window, similar to the example shown in "Figure: The
Rulebooks Window".


The Rulebooks Window

You should read the rest of this introduction if you are unsure how PSnS/2 uses
rulebooks to control the backups which it performs.

If you are unsure about selecting files by pattern, read Specifying Patterns
for File and Directory Matching now.

PSnS/2 is supplied with an example rulebook which helps you to familiarise
yourself with rulebooks.  Select EXAMPLE from the Available Rulebooks listbox.
Choose the Open option from the Rulebook pull-down menu or double-click the
rulebook name in the Available Rulebooks listbox. This will invoke the Edit
rules window as shown below. This window shows the details of the EXAMPLE
rulebook, including a list of the patterns used in it.


The Edit Rules Window

When PSnS/2 checks your files for backup, it takes each file name and compares
it with the patterns in your rulebook. It starts at the first rule and works
down. Once PSnS/2 finds a match, it backs up the file to the drive specified or
ignores the file if the drive is [none]. The order of rulebooks is therefore
important - if your first rule tells PSnS/2 to backup everything to drive C,
and your second rule tells PSnS/2 not to backup any files beginning with the
letter A, PSnS/2 would backup all the files, because it would never check the
second rule.

The EXAMPLE rulebook has three rules. The first rule tells PSnS/2 to backup all
files with the extension TXT from the directory MYFILES on the C drive to drive
[none]. In other words, PSnS/2 should not backup these files. This is called an
exclusion rule.

The next rule tells PSnS/2 to backup all the other files in the MYFILES
directory to drive C.

The last rule tells PSnS/2 to backup everything from the ACCOUNTS\DATA
directory on any drive to drive A.

To select a rule either click on it with the mouse or move to it using the
cursor keys.

Select the second rule. Notice that Trigger backup when files changed this many
times is set to 1. This means that the files will be backed up after only one
change. Notice also that PSnS/2 has been told to keep three generations of each
file. Do not worry about the last field which is described in the Editing a
rulebook below.

The options for the third rule are the same as for the second.

Select OK to return to the Rulebooks window.


ΓòÉΓòÉΓòÉ 12.2. Default Rule Options ΓòÉΓòÉΓòÉ

The default options for a rulebook, and the backup disk for control files can
be displayed by selecting Change defaults from the Options pull-down on the
List of Rulebooks window:


The Rulebook Defaults Window

Backup device used in new rules
   When adding a new rule, this drive will automatically be selected as the
   backup drive.

Backup device for PSnS/2 control files
   PSnS/2 backs up its control files to this drive.

Backup trigger level
   The default number of changes that must be made to a file before it is
   backed up.

Backup generations
   The default number of generations of backup that will be kept.

To change the value of the drive letter, select the arrows on the boxes.  A
drop-down box appears showing the drive values you can select.

To change the values in the bottom two boxes, either click on the arrows on the
right of each box, or use the Tab key until the box is highlighted and press
the Up and Down cursor keys. The arrows on the other two boxes scroll up and
down through the range 1-99.

To search active global rulebooks before active local rulebooks, or vice versa,
then choose the Select Checking Order option from the Options pull-down menu in
the List of Rulebooks panel. If the Check Global before Local option is
selected, then global rulebooks will be checked first.  If the Check Local
before Global option is selected, then local rulebooks will be checked first.
Use this with caution as it could dramatically affect the way PSnS/2 will back
up files. The order in which the rulebooks are searched can make a difference
to which files are backed up and where they are stored because the first rule
matching a file will be used.  Thus, the different search orders may activate
different rules.


ΓòÉΓòÉΓòÉ 12.3. Editing a Rulebook ΓòÉΓòÉΓòÉ

This mode allows you to alter the rules and options within a rulebook. It
enables you to specify which groups of files PSnS/2 is to back up, and where to
store them.

Select the rulebook you wish to edit from the Rulebooks window, then select the
Open option from the Rulebook pull-down menu.  This will invoke the Edit rules
window as shown in "Figure: The Edit Rules Window".

The following describes how to: c.

o Edit rules

o Change the rulebook options for each rule

o Add rules

o Delete rules.


ΓòÉΓòÉΓòÉ 12.3.1. Editing Rules ΓòÉΓòÉΓòÉ

To edit rules, select the pattern that you want to change. Move the cursor to
the Pattern: field and change the rule there. You can also change the
description. The new pattern will appear in the list of rules when you select a
different rule.

You can have up to 128 characters in a Pattern field and 64 in the Description
fields. To see characters in parts of a field outside a box, drag the mouse or
use the Left/Right cursor keys to see the beginning or end of a box.

If you edit a global rulebook you have to enter the password of the current
active global rulebook (if it has one). Remember that passwords are sensitive
to upper and lower case.


ΓòÉΓòÉΓòÉ 12.3.2. Rulebook Options for Specific Rules ΓòÉΓòÉΓòÉ

Trigger backup when files changed this many times
   This shows how many times files matching the highlighted pattern will have
   to be spotted before a backup is triggered. Change the values by clicking on
   the up and down arrows at the side of the box.

Keep this many generations of backups
   This is the number of successive generations of files matching the
   highlighted pattern, that will be kept. Change the values by clicking on the
   Up/Down arrows at the side of the box or use your keyboard cursor keys.

Compress command
   This is the command that PSnS/2 uses to compress files before making backup
   copies. If a * is shown in the box, PSnS/2 will use its own compression
   program.

Uncompress command
   This is the command that PSnS/2 uses to uncompress files before retrieving
   them. If a * is shown in the box, PSnS/2 will use its own uncompression
   program.


ΓòÉΓòÉΓòÉ 12.3.3. Changing File Compression and Uncompression Commands ΓòÉΓòÉΓòÉ

The default commands that PSnS/2 uses to compress and uncompress files
(designated by *) compress most files well, but some, especially files
containing random data, do not. You may prefer to use your own file compression
programs for these files. Enter your own commands for compressing and
uncompressing files.

A blank in the box indicates that file compression should not take place.
Anything else will be interpreted as a compression command. The uncompress
command restores the files to their original size again when you restore them
from backup.

Warning: File compression takes place when files are about to be backed up. Do
not change compression and uncompression commands between backing up and
restoring a file matching the highlighted pattern. If you do, there is a danger
that a file might be uncompressed using the wrong uncompression program thus
ruining your data.

Furthermore, when PSnS/2 restores a file backed up using your own compression
program, it needs to refer to the rulebook so it can use the correct
uncompression program. You should therefore change your rulebooks with extreme
caution if you are using your own compression program as you may make files
previously backed up impossible to restore.

The commands you enter in these fields must either reside in the current path,
or you must specify the drive, path, and file name completely, as in:

D:\DIR1\MYCOMP  &s  &t /c

This single command will have to process many different files, so PSnS/2 uses
tokens as a way of expressing this. The full specification of drive, path, and
file name of the source file (the file to be backed up) can be represented by
the token &s, and &t represents the name and extension of the compressed file.

Suppose you want PSnS/2 to use a command MYCOMP, which has the form:

MYCOMP  <input spec> < output spec>  /  myoption

where:

input spec     Is the specification of the input file
output spec    Is the specification of the output file
myoption       Is c or u to indicate compress or uncompress.

This is how you might specify a compress command:

MYCOMP  C:\DIR1\EXAMP.FIL  D:\DIR2\EXAMP.COM /c
to compress the file C:\DIR1\EXAMP.FIL to give the compressed file
D:\DIR2\EXAMP.COM.

The actual compress command you type in would be:

MYCOMP  &s  &t  /c

Uncompress works in the same way but the source and compress files will be the
other way around:

MYCOMP  &t  &s  /u

When it needs to issue the commands, PSnS/2 will replace the tokens with the
correct file identifiers.

You can have 64 characters in the Compress command, and Uncompress command
fields. To see characters in parts of a field outside a box, or use the
Left/Right cursor keys to see the beginning or end of a box.


ΓòÉΓòÉΓòÉ 12.3.4. Adding Rules ΓòÉΓòÉΓòÉ

New rules are inserted into the rules list before the highlighted rule. Select
the Add option from the Rulebook pull-down menu in the List of Rulebooks
window. The Add a new rule window is displayed.

Type in the file-matching pattern that you want PSnS/2 to search for and select
the backup drive (or [none] if you are creating an exclusion rule). Type in the
description for the rule for reference and select OK.


ΓòÉΓòÉΓòÉ 12.3.5. Deleting Rules ΓòÉΓòÉΓòÉ

To delete a rule, simply highlight it in the usual manner, and select the
Delete option from the Rulebook pull-down menu on the List of Rulebooks window.


ΓòÉΓòÉΓòÉ 12.4. Selecting the Rulebook You Wish to Use ΓòÉΓòÉΓòÉ

PSnS/2 marks the rulebooks it is using with an <in use> tag on the Rulebooks
window. One global rulebook is always in use but a local rulebook is optional.

Select the rulebook you wish to use by clicking it with the mouse or by using
the keyboard cursor keys. Then press the Use option on the Rulebook pull-down
menu.

If you have selected a local rulebook, the <in use> tag will appear next to it
unless the rulebook was in use already in which case the <in use> tag will
disappear.

If the selected rulebook is a global rulebook, you will be prompted to type the
password if there is one. After you have typed the password, select OK.

Having entered the correct password, the <in use> tag switches to the
highlighted rulebook.

Note:  Passwords are sensitive to upper and lower case letters. :enote.


ΓòÉΓòÉΓòÉ 12.5. Testing Your Active Rulebooks ΓòÉΓòÉΓòÉ

To test a rulebook, select the Test Active Rulebooks option from the Rulebook
pull-down menu on the List of Rulebooks panel. The Testing Rulebooks screen
will then be displayed. The program will scan your disks and give a list of the
files that are covered by the active rulebooks.


ΓòÉΓòÉΓòÉ 12.6. Creating New Rulebooks ΓòÉΓòÉΓòÉ

There are two ways of creating new rulebooks

o From scratch using the Add option from the Rulebook pull-down menu.

o Copying an existing rulebook and giving it a new name using the Copy item on
  the Rulebook pull-down menu.

Note:  Passwords for global rulebooks are sensitive to upper and lower case. If
you are unsure about passwords, seek advice from someone more experienced or,
if your PC is connected to a network, see your system administrator.


ΓòÉΓòÉΓòÉ 12.6.1. Creating a Rulebook from Scratch ΓòÉΓòÉΓòÉ

Select New from the Rulebook pull-down in the List of Rulebooks window to
invoke the Add a new rulebook window. Type in the name for the new rulebook.
The radio buttons allow you to choose whether the new rulebook will be global
or local. Select OK to confirm your choices and pass directly into the rulebook
editing panel. To abandon creating your new rulebook select Cancel.


ΓòÉΓòÉΓòÉ 12.6.2. Copying a Rulebook ΓòÉΓòÉΓòÉ

Select a rulebook by using your mouse or the Up/Down cursor keys until the
rulebook which you want to copy is highlighted. Select the Copy item in the
Rulebooks pull-down menu. Press Enter or double-click to display a window which
asks you to enter a name for the new rulebook.

At this stage you must choose whether you want the new rulebook to be global or
local by selecting the appropriate radio button. When you are satisfied with
your choice, select the OK button.

If you are creating a local rulebook, you will be returned to the List of
Rulebooks panel.

If the rulebook that you are creating is to be global, you must type in the
password of the active global rulebook if it has one. (The sample rulebooks on
the installation diskette don't have passwords, therefore this will not affect
you if one of them is in use). A similar dialog box will appear, now requesting
the password for the new global rulebook. Type in the new password (if you want
one) and press Enter or select the OK button.

If you want to make a global rulebook from a local rulebook and do not want to
change its name, you may want to delete the local rulebook version after you
have made the copy. To do this, refer to the section immediately below.


ΓòÉΓòÉΓòÉ 12.7. Deleting Rulebooks ΓòÉΓòÉΓòÉ

Select the Delete option from the Rulebooks pull-down menu if you want to
delete a rulebook. You will be asked to confirm your decision. Press OK to
delete the rulebook or Cancel if you decide not to delete it.

If you are attempting to delete a global rulebook, you must know the password
of the active global rulebook. A dialog box appears for you to type in the
password. You will see the usual message window asking you to confirm the
deletion. If you type the password incorrectly, you will get an error message.

Note:  Passwords are case sensitive.


ΓòÉΓòÉΓòÉ 12.8. Confirming the Changes ΓòÉΓòÉΓòÉ

If you are happy with the changes you have made to the list of rulebooks and
the default rulebook options, select Exit from the Rulebook pull-down. You will
be asked if you want to save the changes you have made.

If you want to abandon the changes select No.


ΓòÉΓòÉΓòÉ 13. Backup Mode Configuration ΓòÉΓòÉΓòÉ

If you have just installed PSnS/2 as described in this guide, it will have been
set to run in manual backup mode. In effect, PSnS/2's background backup
activity will be suspended until you have configured the program's settings to
suit your particular needs and circumstances and then have instructed PSnS/2 to
run in one of its two main background backup modes. This section explains how
you can: c.

o Select the backup mode

o Set the times when files are checked.

Select the Timed start... option from the Setup pull-down on the PSnS/2 main
menu to display the Change backup modes and times window.


The Change Backup Mode and Times Window

You must select one of three radio buttons:

Check disks for files to backup at intervals of:
   In this mode, PSnS/2 will check the disks for files to back up at the
   intervals specified by the boxes on this option. To change the interval, use
   the scroll bars to alter the time shown in the boxes.

Check for changed files and run backup at time:
   In this mode, PSnS/2 will check the disks for files to back up once a day,
   at the time shown in the boxes. To change the time, use the scroll bars.
   When PSnS/2 is in this mode, the disk(s) will be scanned as a whole before
   file transfers are done. The trigger level set previously, however, is
   ignored.

Backup files on request only
   With this radio button selected, PSnS/2 is in effect suspended until one of
   the two preceding choices has been selected or Force Backup Now! from the
   main Backup menu has been put into force.

Confirm any changes by pressing the OK button, or discard them with the Cancel
button.


ΓòÉΓòÉΓòÉ 14. Verifying Installation ΓòÉΓòÉΓòÉ

This section is a simple test to ensure PSnS/2 is working correctly on your
computer or networked system.  It describes the backup of a single file to your
C drive and its restoration.


ΓòÉΓòÉΓòÉ 14.1. Selecting the VERIFY rulebook ΓòÉΓòÉΓòÉ

Select the Rulebooks option from the Setup pull-down on the PSnS/2 main menu to
display the List of Rulebooks window. Choose the VERIFY rulebook with the mouse
or cursor keys and then select the Use item from the pull-down menu.

If you wish to check that PSnS/2 is backing up correctly todrives other than
the default, the VERIFY rulebook must be altered. To do this, select VERIFY and
double-click it, or choose the Edit item from the Rulebookpull-down menu. Move
to the to drive field and enter the new drive letter.

You can also use a different file for the initial backup.  Enter a different
pattern in the Pattern field, and press OK when you are happy with your
changes.  You will be returned to the List of Rulebooks window. Select Cancel
to discard the changes or select OK to confirm them. Either action will then
return you to the PSnS/2 main menu.


ΓòÉΓòÉΓòÉ 14.2. Backing up DUMMY.FIL ΓòÉΓòÉΓòÉ

Select the By pattern item from the Backup pull-down on the PSnS/2 main menu to
display the Backup selected files window.  Enter C in the top entry field and
DUMMY.FIL in the file names matching this pattern field.  Then press OK.

If everything is working correctly, PSnS/2 displays a panel telling you it is
backing up the file.  If this does not happen, please refer to Diagnostics.

You should now erase the file by opening an OS/2 command prompt and entering
ERASE C:\PSS\CODE\DUMMY.FIL.


ΓòÉΓòÉΓòÉ 14.3. Restoring DUMMY.FIL ΓòÉΓòÉΓòÉ

Return to the PSnS/2 main menu.

Choose the Specific files option from the Restore pull-down on the PSnS/2 main
menu. Select the C:\PSS\CODE directory, by: c.

o Selecting C: from the Directories and drives box.

o Select PSS.

o Select CODE.

o Finally, select DUMMY.FIL from the Files box and click the Restore button.
  PSnS/2 will ask you to confirm your choice of file.

Select OK to restore the file.  If all is well, PSnS/2 will tell you it is
restoring the file and returns you to the Select files from backup window.

You should check that the file has been restored properly.  Return to the OS/2
command prompt and enter:

TYPE C:\PSS\CODE\DUMMY.FIL

If you get the response:

This is a dummy file to be used during verification.
then PSnS/2 is working correctly on your system.  If not, refer to Diagnostics.


ΓòÉΓòÉΓòÉ 15. Taking Manual Backups ΓòÉΓòÉΓòÉ

On occasion you might need to back up files before the automatic backup takes
place.  For instance, it is a good idea to back up all the files you want
protected as soon as you install PSnS/2.  It is also sometimes convenient to
start a backup of the files already spotted, for example when you need to shut
down your computer unexpectedly, or if a large number of files are ready to be
backed up and you are going to lunch.

Note:  Backing up a large number of files can take a long time, particularly if
you are using a slow device such as a diskette. :enote.


ΓòÉΓòÉΓòÉ 15.1. Manually Backing Up Groups of Files ΓòÉΓòÉΓòÉ

This section explains how you can back up groups of files which PSnS/2 is
looking after. You might wish to do this if, for example, you have just run
PSnS/2 for the first time and you wish to take a backup of all your important
files.

Note:  You can only back up files that are described in active rulebooks.

Select the By pattern option from the Backup pull-down on the PSnS/2 main menu
to display the Backup selected files window.

Type the name of the directory you want to search using wildcards if necessary.
Do not enter wildcards on the directory line. If you do, a message box appears
telling you that you have entered an invalid pattern. Select OK to return to
the Backup selected files window and correct the entry you made. The way of
getting around specifying individual directories is to select the check box
Including files found in subdirectories of this directory.

Type the pattern that matches the group of files you want to back up in the
entry field (see Specifying Patterns for File and Directory Matching if you are
unsure). Only enter *.* if you want to backup all files in the directory you
have selected, except for those excluded by your current rulebook.

You can enter a date to tell PSnS/2 how recently files must have been created
or changed for them to be backed up. When you select OK, PSnS/2 searches for
files with the pattern you typed. If it finds files matching the patterns in
your active rulebooks and these files were created or changed on or after the
date you indicated, it will back them up.

If you want to back up the files regardless of whether they have changed since
the last backup, select the check box Including files not changed since last
backup from the Backup selected files window. This is the only way of
performing a selective full backup.

Note:  The date format used will be the date format you have selected for your
OS/2 system using the OS/2 Control Panel (OS/2 v.1.2 and 1.3) and System Setup
(OS/2 v2.x). The text after this entry field will give an example using the
selected date format.

 Select Cancel to discard your choices or, once you have selected all the
options you require, click OK. The message Copying files will appear and PSnS/2
now backs up the files which you have requested. It will let you know if it
needs any help (for example, when it needs any new diskettes for back up).


ΓòÉΓòÉΓòÉ 15.2. Manually Backing Up Files Spotted as Changed ΓòÉΓòÉΓòÉ

To back up all the files PSnS/2 has spotted as having been created or changed
since the last backup, select the Files spotted option from the Backup
pull-down on the PSnS/2 main menu. A window appears, asking you to select OK
when you want to start the backup.


The Backup Selected Files Window

When you select OK, PSnS/2 starts backing up files and a message window appears
which tells you which file is currently being backed up. You can check the
backup log to see if your files have been backed up successfully. See the
section Viewing the Log File in the Technical reference if you want to do this.

If PSnS/2 cannot backup a file (for example, because the diskette is
unavailable or the drive isn't working), it remains on the files spotted list.
If files were deleted before they were backed up, the number on the files
spotted display may not show the actual number backed up.

The PSnS/2 control files are backed up to the drive specified in the List of
Rulebooks window, and can be changed in the Change defaults for new rules
window. The device which the rulebooks <in use> back files up to is also shown
here, and can be changed in the same way.

It is possible to halt backup by pressing the Interrupt button in the Copying
files  panel.  When the user halts a backup, PSnS/2 displays the files that
have not yet been backed up in the Backup Interrupted window.  The user can
then remove any of these files and they will be removed from the Files spotted
for backup list until they are changed again.

The Backup Interrupted panel allows users to choose whether to continue backup
(having removed any files they do not wish to be backed up) or to abandon the
backup altogether. The Continue push button will continue backup and the
removed files will disappear from the Files spotted for backup list until they
are changed again.

The Exit push button will cancel the backup and return you to the PSnS/2 main
menu.


ΓòÉΓòÉΓòÉ 16. Restoring or Deleting Data from Backup ΓòÉΓòÉΓòÉ

The first part of this chapter tells you how to restore files from backup
copies.

There are two methods for restoring files:

o Specific files, by individual selection from the records of files backed up.

o Files by pattern, if there are groups of files to be restored.
The main PSnS/2 program must be activated to restore files by either method.


ΓòÉΓòÉΓòÉ 16.1. Restoring Specific Files ΓòÉΓòÉΓòÉ

If you have only lost one or two files, or if you want to retrieve a particular
generation of a file, the Restore specific files option should be used.  Select
the Specific files option from the Restore pull-down on the PSnS/2 main menu.
The Select files from backup window appears.

This window allows you to see which files have been backed up. Select the
backup copy you wish to restore. Any backup copy to be restored must be
selected from files in the Files box.

Note:  If you are using your own compression program for backing up, you can
only restore files that are described in an active rulebook.


The Select Files from Backups window

You can choose the drives and directories in which to search for backups.  The
selected directory is shown on the line Directory is: which will be blank at
first.

The pattern of file names to search for is shown on the line File name:.

Any files in the selected directory which match that pattern will appear in the
Files box.  If there are any subdirectories of this directory which also
contain backups, their names will appear in the Directories and drives list
box.

If you choose a subdirectory, the symbol for the parent directory (..) appears
in the Directories and drives box. Select this to return to the parent
directory.

If any files have been backed up there will be at least one drive in the
Directories and drives box.  Select a drive name and it will be displayed on
the Directory is: line. The drive's directories will appear underneath the
drive name highlighted in the box.

If a directory is selected, its name will also be displayed on the Directory
is: line.  If there are any backup copies from the directory which matches the
pattern displayed on the File name line, they will appear in the Files list.


ΓòÉΓòÉΓòÉ 16.1.1. Restoring a Specific File ΓòÉΓòÉΓòÉ

If you want to restore a specific file, you should find and select the file in
the list described above.

Now select Restore to display the Select generation of backup to restore
window.


Select Generation of Backup to Restore window

Select the generations of the file shown in the Date/Time list box. It can be
accepted unchanged, or the name of the directory to which you want to restore
the backup can be altered.  Then select OK.

To abandon the restore action, select Cancel.

You will be returned to the Select files from Backup window.  When you have
finished restoring files, select OK.


ΓòÉΓòÉΓòÉ 16.1.2. Dropping a file from the backup store ΓòÉΓòÉΓòÉ

If you want to remove a file from the store of backups, select a file as though
you were about to restore it. Then, select Drop on the Restore selected files
from backups window and the file will be deleted from the Files list box on the
PSnS/2 main menu.


ΓòÉΓòÉΓòÉ 16.1.3. Restoring Groups of Files ΓòÉΓòÉΓòÉ

To restore groups of files, select the By pattern item from the Restore
pull-down on the PSnS/2 main menu.

The Restore files matching a pattern window allows you to restore files which
match a directory and file name pattern.  You can use wildcard characters in
the file name part of the pattern, including the directory part.

Note:  If you are using your own compression program for backing up, you can
only restore those files which are described in an active rulebook.


Restore Files Matching a Pattern from Backups window

Move the cursor to the date entry field and type in a date. Then move the
cursor to the time entry field and type in a time. The files will be restored
from the generation of backup taken on or before this date and time.

After completing the date and time, select OK.  The files will be restored to
the state they were in at the time which you specified.

To abandon the restore operation, select Cancel.  You will be returned to the
PSnS/2 main menu in either case.

If your computer is part of a network with a backup server on which PSnS/2 has
been installed, additional backup copies of your file may also be available.
To find out, contact your system administrator.


ΓòÉΓòÉΓòÉ 17. Technical Reference ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 18. Technical Overview ΓòÉΓòÉΓòÉ

This part gives you an overview of various technical aspects of PSnS/2 such as:
c.

o The components which make up the PSnS/2 product

o Changes to PSnS/2

o The operating environment for PSnS/2.


ΓòÉΓòÉΓòÉ 18.1. The Components of PSnS/2 ΓòÉΓòÉΓòÉ

PSnS/2 is a set of programs and files. The package provided contains 5
operational programs:

o PSNSINST.EXE

  This is the installation program, which is run once when you install PSnS/2
  on your machine.

o PSS.EXE

  This is the main PSnS/2 program that provides all the primary user functions
  (such as defining rulebooks and initiating backup). It also provides
  interaction with the extensive help facility provided with PSnS/2. The help
  information itself is stored in the file MAGHELP.HLP

o PSSRECV.EXE

  A program that will download files from a host session. This is provided to
  save the user having to provide one of their own if they are in a standard
  IBM host processor and PC environment.

o PSSSEND.EXE

  A program that will upload files to a host session. This is included to save
  the user having to provide one of their own if they are in a standard IBM
  host processor/PC environment.

o UNHIDE.EXE

  Changes the attributes of the file PSS.PRO (the user profile) so that it is
  no longer hidden. This allows it to be deleted when PSnS/2 is removed from
  the machine.

In addition to these executable files, the installation diskette (or diskettes)
will contain the following files:

o README

  This contains the latest information about PSnS/2, including any known
  problems with the software and the latest release information.

o CPYRIGHT.DAT

  The copyright information for the software.

o GENERAL.MPG

  A general purpose rulebook that users are encouraged to install as their
  active global rulebook when they first use PSnS/2.

o CPROGS.MPG

  A sample rulebook that provides backup facilities for C programmers.

o SPREAD.MPG

  A sample rulebook that provides backup facilities for spreadsheet users.

o VERIFY.MPG

  The rulebook referred to in Verifying Installation.

o EXAMPLE.MPL

  The example rulebook referred to in Rulebook Configuration.

o DUMMY.FIL

  A dummy file used in Restoring or Deleting Data from Backup.  This can be
  deleted from your fixed disk when you are sure the program has been
  successfully installed.


ΓòÉΓòÉΓòÉ 18.2. Automatic Installation ΓòÉΓòÉΓòÉ

The PSnS/2 installation program

o Detects the version of OS/2 being used

o Installs the corresponding version of PSnS/2.

The 16-bit version of the code (for OS/2 v1.2 and 1.3) is in the OS/2
subdirectory on the installation diskette.

The 32-bit version of the code (for OS/2 v2) is in the OS22 subdirectory on the
installation diskette.


ΓòÉΓòÉΓòÉ 18.3. Changes to PSnS/2 ΓòÉΓòÉΓòÉ

The file README on the INSTALL diskette, contains details of any recent changes
to PSnS/2 that may have been made.

You may read it by using any editor program such as OS/2 E.EXE.


ΓòÉΓòÉΓòÉ 18.4. Operating Environment ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 18.4.1. Fixed Disk Usage ΓòÉΓòÉΓòÉ

Fixed disk space is required for:

o The main control file with an overhead for each file and directory.

o The installation of PSnS/2

o Backup copies.

As a guide, a control file for two generations of 100 unique files from one
directory requires about 6KB.

The main control file is held on disk in 2KB blocks, plus 768 bytes. Each 2KB
block is used to hold data for the generations of backed up files that are
stored. This amounts to 65 bytes for the first two generations of each file,
plus 8 bytes for each additional generation.

If the 2KB block becomes full, another 2KB block is created with the data
divided between the two blocks.


ΓòÉΓòÉΓòÉ 18.4.2. Main Memory Usage ΓòÉΓòÉΓòÉ

PSnS/2 requires a minimum of 384KB of free memory.


ΓòÉΓòÉΓòÉ 18.4.3. Network or Host System Attachment ΓòÉΓòÉΓòÉ

PSnS/2 may be used in a Local Area Network (LAN) or attached to a host
computer. Three options are available:

o Local Area Network rulebooks may be stored on remote disks or other devices.
  PSnS/2 may be used in this way on all LANs that are supported by DOS or OS/2
  for remote server functions.

o IBM mainframe host attachment If you are using a mainframe host, the hardware
  and software requirements are the same as those for IBM's Enhanced
  Connectivity Facility (ECF), as the host is supported through ECF. Access to
  the host may be provided over any of the LANs mentioned in this section.

o IBM Applications System/400 (AS/400)* family host attachment c.

   - IBM AS/400

   - IBM System/38 These hosts are supported using Personal Computer Support.

PCs can be connected over an IBM Token-Ring LAN, or over remote communications
lines, if used. The PC hardware requirements are the same as those for the PC
support you are using and the requirements for PSnS/2 must also be met.


ΓòÉΓòÉΓòÉ 19. PSnS/2 Command Line Switches ΓòÉΓòÉΓòÉ

PSnS/2 can be started in a number of different ways, allowing greater
flexibility in the way it is used. The actions the program takes when it starts
can be controlled by using command line switches.

The available switches are:

/B                  PSnS/2 will perform a backup as soon as it is started,
                    using the active rulebooks (see below).
/BL=<name>          PSnS/2 will perform a backup as soon as it is started,
                    using the specified local rulebook (see below).
/BG=<name>          PSnS/2 will perform a backup as soon as it is started,
                    using the specified global rulebook (see below).
/C                  When used with the /B, /BL or /BG switches, /C makes PSnS/2
                    back up only the files which have been changed since the
                    last back up. For example, /B /C will make PSnS/2 back up
                    files which are covered by the active rulebooks, and which
                    have been changed since the last back up. This switch must
                    be used in conjunction with /B, /BL or /BG. Used alone, it
                    does nothing.
/I                  PSnS/2 will start iconised.

Under OS/2 version 2.0, these switches can be set by opening the program
settings for PSnS/2. Enter the switches in the Parameters field.

Under all versions of OS/2, the command

start "Personally Safe'n'Sound" PSS.EXE /I
will force the program to be iconised as soon as it is started.

Of the switches above, /B requires further explanation. This switch can be used
in a number of ways. In its simplest form, /B will perform a standard backup as
soon as PSnS is started. This backs up all files which are covered by the
active rulebooks. This might be useful in a critical environment as it ensures
that you have a complete set of backed up files every time the program is run.

Using /BL=<name> or /BG=<name> performs a similar task, except that instead of
using the current active rulebooks, the program will use the rulebooks
specified by name Note that the switches only override the type of rulebook to
which they refer, so /BL=DAILY will override any active local rulebook but will
not affect the active global rulebook. Similarly /BG=ONCE will over-ride the
active global rulebook but will not affect any local rulebook.

One possible use of /BL=<name> and /BG=<name> would be to allow a daily backup
to diskette by using appropriate rulebooks in the switches, combined with
regular background backing up to hard drive during normal operations. This not
only provides greater security but also avoids repeated interruptions for the
program to backup to diskette during normal working hours.


ΓòÉΓòÉΓòÉ 20. Recovering Data after a Fixed Disk Format ΓòÉΓòÉΓòÉ

If you have had to reformat the disk on which PSnS/2 has been stored, you must
reinstall the program.  The control files PSnS/2 uses to keep track of your
backup files and their original directories will also have been lost.

If your control files were backed up to a different volume, you may restore
them in the same way as you would restore other files backed up to that volume.

o Insert the original PSnS/2 diskette and type the Install command as you did
  when initially installing PSnS/2.  Use the same directory names as before.

o A panel will appear asking if you wish to recover the PSnS/2 control files.
  Press Y.

o The panel will then ask in which drive the backups of the control files can
  be found.  Enter the drive letter of the disk drive.

o If you kept the control files on diskette, insert the diskette when prompted
  by PSnS/2.  If the files are on more than one diskette, PSnS/2 will ask you
  to insert any others as required.

When the control files have been recovered, you can restore any of the other
backed up files by using the By pattern item from the Restore pull-down on the
PSnS/2 main menu.  Please refer to Restoring or Deleting Data from Backup.


ΓòÉΓòÉΓòÉ 21. Removing PSnS/2 ΓòÉΓòÉΓòÉ

To remove PSnS/2 from your computer, do the following:

o Terminate the main, active part of PSnS/2 by selecting the Exit option from
  the Backup pull-down on the PSnS/2 main menu window. PSnS/2 can still be
  restarted, either directly or automatically after the computer is rebooted.

o Remove the extra lines in the STARTUP.CMD file. Use your usual editor or, if
  you are not sure, ask someone more experienced or your system administrator.
  Alternatively, you can erase STARTUP.CMD and rename STARTUP.PSS as
  STARTUP.CMD. (Take the second alternative only if you asked PSnS/2 to change
  STARTUP.CMD when you installed it).

o Using OS/2 v2.x, open the Startup Folder and delete the PSnS/2 object by
  either dragging it over to the Shredder object and dropping it there, or by
  clicking it with your right mouse button and selecting Delete from the drop
  down menu.

o Make the file PSS.PRO visible by opening a Command Prompt and typing
  C:\PSS\CODE\UNHIDE. Then type ERASE C:\PSS.PRO to delete it.

o Delete all the PSnS/2 files and directories. These will be called \PSS\CODE
  and \PSS\SYSDATA if you used the defaults during installation. Backed up
  files will be stored in the directories \PSSBKP\USER and \PSSBKP\SYSTEM.


ΓòÉΓòÉΓòÉ 22. Using PSnS/2 on a Network ΓòÉΓòÉΓòÉ

A local area network (LAN) allows people using PCs to share programs, data, and
devices such as printers. There are ways of using the properties of a LAN to
backup effectively.

The following sections give some advice on how to use PSnS/2 in different LAN
situations.

If you are responsible for a network of computers, you can use PSnS/2 to
implement general standards for backing up files over a network and allow users
some personal control over the files they want to back up.

Information is given about using PSnS as a: c.

o Single user on a LAN

o Administrator of a group of users on a LAN.


ΓòÉΓòÉΓòÉ 22.1. Single LAN User ΓòÉΓòÉΓòÉ

If you are using your own copy of PSnS/2 on a LAN, save backup copies of your
files to disks on the LAN server. LAN servers are less likely to suffer from
problems that affect local machines and have larger fixed disks than your own
computer.

Install PSnS/2 on your own computer in the same way as described for single
machines. To store your backup copies on LAN disks, the to drive: field in the
rulebooks should use the drive letters assigned to the disks by OS/2.

Note:  Only backup your files to LAN disks to which you have exclusive access.
Otherwise other users of PSnS/2 may overwrite your own backup files.


ΓòÉΓòÉΓòÉ 22.2. Administrator of a Large Group of Users on a LAN ΓòÉΓòÉΓòÉ

If you are system administrator responsible for allocating LAN disk space for a
group of LAN users, follow this procedure to make the best use of the disk
space.

You must install PSnS/2 on every workstation on which it is going to be used.
You can also install PSnS/2 on the LAN server in the same way as described for
a single computer.

To allow the LAN users to use LAN disk space for their backup files, allocate
to each of them a separate directory on a LAN disk. Each directory should have
exclusive write access; this will make sure each person's backup files are
protected from other LAN users.

Create a global rulebook which is to be used by everybody on the LAN.


ΓòÉΓòÉΓòÉ 22.3. Defining a Common Global Rulebook ΓòÉΓòÉΓòÉ

If you are responsible for installing PSnS/2 on many computers, you may wish to
impose common standards for backup procedures.  For example, if everyone in
your group uses a spreadsheet, you will want to keep backups of all their
spreadsheet files.

You can ensure these files will be backed up by installing PSnS/2 on all
computers in your group and making each use the same global rulebook. The
installation program for PSnS/2 is specially designed to make this process
easy.

o Install PSnS/2 on your computer as described in Installing PSnS/2 of the
  User's Guide.  Initially, you can use any rulebook.

o Design the rulebook for everyone to use. You should make this your global
  rulebook. Rulebook Configuration explains how to do this. Note that using
  very general inclusion or exclusion rules (like *.*  C or C:*.* [None])
  will prevent individual users of the LAN from customising the system, using
  their own local rulebooks.

o Once you have completed designing your rulebook, exit PSnS/2 and check that
  the file <rulebook>.MPG is in your C:\PSS\SYSDATA directory (or the
  equivalent directory if you are storing your PSnS/2 program somewhere other
  than C:\PSS\CODE).

o Take your group installation diskette and make sure it is not write
  protected.

o Type COPY C:\PSS\SYSDATA\<rulebook>.MPG A:\SAMPLE to copy your rulebook on to
  the installation diskette.

o Now make sure everyone knows that they should type A:\INSTALL <rulebook> to
  install PSnS/2 with your rulebook as the common global rulebook.


ΓòÉΓòÉΓòÉ 23. The Logged Record of Backups ΓòÉΓòÉΓòÉ

PSnS/2 keeps a record of all the files of which it takes backup copies. This is
called the log file. Select the Logfile pull-down from the PSnS/2 main menu and
you can: c.

o View the log file

o Choose what is recorded on the log file

o Choose a logview program.


ΓòÉΓòÉΓòÉ 23.1. Viewing the Log File ΓòÉΓòÉΓòÉ

To view the log of backed-up files, select the View log option from the Logfile
pull-down menu. This displays the Backup Log file which holds the date and time
of all the files backed up and the drive to which they were backed up.

When viewing the log file, PSnS/2 will use an editor program. Depending on the
editor, you may be offered options such as File, Edit, and Options for
selecting fonts, colours, and so on. The System Editor will also have a Help
option.

The log contains the date and time of each backup, an error number (if there
has been an error), the drive to which the file was backed up and the full file
specification (drive, path, and name).


ΓòÉΓòÉΓòÉ 23.2. Choosing Which Files Are Recorded on the Log File ΓòÉΓòÉΓòÉ

To select which records are written to the log file, select from the two
checkmark options underneath the View log option. These options are: c.

o Log successes

o Log failures.

You can choose to record the successful backups and the unsuccessful backups.
Successful backups are ones where the file has been backed up and all the
PSnS/2 control files have been updated correctly. A failed backup is one where
one of these steps cannot be performed, for example, if an attempt was made to
back up to an unknown drive.

This is what a few lines of a log file might look like:

- 03-05-90   08:30                    >C   <C:\STARTUP.CMD
- 03-05-90   18:30                    >C   <C:\AUTOEXEC.BAT
X 03-05-90   18:55      10            >H   <C:\FAIL.ME
- 03-05-90   18:58                    >C   <C:\MYDIR\PATCH.CMD
This shows that three files were backed up  successfully and one
unsuccessfully. The error code on the failed backup was 10. In the backup log
error codes below, you can see that the backup failed because drive H does not
exist.


ΓòÉΓòÉΓòÉ 23.2.1. Backup-Log Error Codes ΓòÉΓòÉΓòÉ

The error codes are:

10  Attempt to back up to unknown drive. Make sure the destination drive is in
    the drive tables.

20  There was an error with removable volumes. The user may have been unable to
    put the right removable volume in the drive or unable to add a new volume
    when the others were full.

30  The C drive is full on the machine running PSnS/2.

40  An error occurred in a user-specified function (a backup or restore
    command, or the compress/uncompress command).

50  An error occurred in the PSnS/2 compress function. It may have run out of
    memory, or the file may have been locked or inaccessible. This can also
    occur if you define a drive that does not exist or is inaccessible, and
    then try to backup to it.

60  A problem occurred in copying a file to an OS/2 supported drive. The drive
    may have been full or inaccessible.

70  A problem occurred with a user copy function used in backing up to a
    non-OS/2 supported drive. The program gave a non-zero ERRORLEVEL, or return
    code.


ΓòÉΓòÉΓòÉ 23.3. Choosing a Logview Program ΓòÉΓòÉΓòÉ

Selecting the Logview program option on the Log file pull-down on the PSnS/2
main menu window shows you what program PSnS/2 uses to view the log file. The
default program is the OS/2 System Editor. It is used automatically if the
entry field is blank.

To use your own Logview program, select the Logview program option. The Set
program to use for logview window is displayed. It asks you to enter the full
path and program name with which you wish to view the log. When you have done
this, select the OK button.

The log file is kept in a file called BACKUP.LOG, in the PSnS/2 System Data
directory, called \PSS\SYSDATA\, on the drive on which you installed PSnS/2.

If you decide not to change the Logview program that is used, select the Cancel
button.

Note:  It should be remembered that a windowed editor for OS/2 Presentation
Manager must be used to view the Logview program. Full-screen editors and those
running under DOS and Win-OS/2 are not supported.


ΓòÉΓòÉΓòÉ 24. Diagnostics ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 24.1. What to Do If PSnS/2 Does Not Run Correctly ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 24.1.1. If the PSnS/2 Main Menu Window Does Not Appear ΓòÉΓòÉΓòÉ

Go into a full-screen OS/2 session and type the command

DIR C:\PSS\CODE

Note:  If you have installed PSnS/2 in another directory you should list the
files in that directory.

The following files should be listed (plus some others):

PSS.EXE
MAGHELP.HLP

If any of these files are missing, you should reinstall PSnS/2 immediately, and
try to run it again.

If you have all of these files, run the program by typing

start "Personally Safe'n'Sound" C:\PSS\CODE\PSS.EXE
If it still does not work, check that you have the correct release of OS/2
(PSnS/2 only works with version 1.2 and above).

If you have carried all the above checks and PSnS/2 still does not work, seek
advice from someone more experienced or from your system administrator.
Finally, try reinstalling PSnS/2, and if this still does not solve the problem,
refer back to your supplier.


ΓòÉΓòÉΓòÉ 24.1.2. What to Do If PSnS/2 Does Not Work Correctly on a LAN ΓòÉΓòÉΓòÉ

Ensure that your rulebooks and control file destinations are defined
consistently (for instance, it is a good idea to store your backups and the
control files on the same drive).

Make sure you are logged on to the LAN whenever PSnS/2 is running. Problems
could arise if a rulebook specifies either searching or backing up to a LAN
disk when you are disconnected from the network.


ΓòÉΓòÉΓòÉ 24.2. Error Messages ΓòÉΓòÉΓòÉ

The following lists and describes error messages produced by PSnS/2.


ΓòÉΓòÉΓòÉ 24.2.1. Installation ΓòÉΓòÉΓòÉ

EAK0040E  There is an existing file that is not a directory

          Explanation: This error is produced when trying to create the path in
          which to store the program.

          User Response: Check that your path is valid.

EAK0041E  File not found

          Explanation: This error is produced when trying to create the path in
          which to store the program.

          User Response: Check that your path is valid.

EAK0042E  Path not found

          Explanation: This error is produced when trying to create the path in
          which to store the program.

          User Response: Check that your path is valid.

EAK0043E  Not DOS disk

          Explanation: This error is produced when trying to create the path in
          which to store the program.

          User Response: The program must be stored on a system-supported disk.

EAK0044E  Drive locked

          Explanation: This error is produced when trying to create the path in
          which to store the program.

          User Response: Check that the drive you are trying to use is
          available.

EAK0045E  Filename exceeded range

          Explanation: This error is produced when trying to create the path in
          which to store the program.

          User Response: Try using a shorter path name.

EAK0046E  Insufficient storage available

          Explanation: There is insufficient storage available for PSnS/2.

          User Response: Refer to Outline of Hardware and Software
          Requirements.

EAK0047E  Unable to spawn process

          Explanation: Produced when the installation program has called an
          external command. There may be a problem with the environment under
          which you are trying to run PSnS/2, for example, you may be trying to
          run too many programs under OS/2.

          User Response: Stop some other programs and start installation again.

EAK0048E  Argument list or environment required too big

          Explanation: Produced when the installation program has called an
          external command. There may be a problem with the environment under
          which you are trying to run PSnS/2.

          User Response: Stop some other programs, and start installation
          again. If the problem persists, refer to Outline of Hardware and
          Software Requirements.

EAK0049E  Too many processes

          Explanation: Produced when the installation program has called an
          external command. There may be a problem with the environment under
          which you are trying to run PSnS/2, for example, you may be trying to
          run too many programs under OS/2.

          User Response: Stop some other programs and start installation again.

EAK0050E  Invalid MODEFLAG

          Explanation: Produced when the installation program has called an
          external command. There may be a problem with the environment under
          which you are trying to run PSnS/2.

          User Response: Check you are running the installation program from a
          full-screen OS/2 session. If this problem occurs when you are in a
          full-screen OS/2 session, refer to Outline of Hardware and Software
          Requirements.

EAK0051E  File not found

          Explanation: Produced when the installation program has called an
          external command and has not found it. This could be because the file
          does not exist or because it is not in the current path.

          User Response: Check that you have the XCOPY program available on
          your machine, and that it is in the current path.

EAK0052E  File not executable

          Explanation: Produced when the installation program has called an
          external command. The command has been found, but it is not
          executable. This is probably because it has been corrupted on your
          machine.

          User Response: Replace the command on your machine with a working
          version.

EAK0053E  Insufficient memory

          Explanation: Produced when the installation program has called an
          external command. Your machine has insufficient memory to perform the
          operation

          User Response: Refer to Outline of Hardware and Software
          Requirements.

EAK0055E  You must install this product in an OS/2 session

          Explanation: The installation program will not run in the DOS box
          under OS/2.

          User Response: Go into a full-screen OS/2 session (by double-clicking
          on the full-screen OS/2 icon if it is visible), and run the
          installation program again.

EAK0056E  Return code xxx from internal routine xxx

          Explanation: One of PSnS/2's internal routines has caused an error.

          User Response: Check that all the path specifications you have given
          PSnS/2 are valid.

EAK0057E  Unable to create PSnS code directory xxx

          Explanation: The installation program has tried to create the
          directory C:\PSS\CODE (or some other path you have specified) but has
          failed. This may be because you have insufficient disk space, or
          because of a disk error.

          User Response: Check your hard disk, and start the installation once
          any problems have been corrected.

EAK0058E  Unable to create PSnS control data directory xxx

          Explanation: The installation program has tried to create the
          directory C:\PSS\SYSDATA (or some other path you have specified) but
          has failed. This may be because you have insufficient disk space, or
          because of a disk error.

          User Response: Check your hard disk, and start the installation once
          any problems have been corrected.

EAK0059E  The drive specified is not valid or is not a fixed disk

          Explanation: The PSnS/2 control data must be stored on a fixed disk.

          User Response: Specify a fixed disk drive, such as your C drive.

EAK0060E  Unable to retrieve Yes/No/Quit value from message file

          Explanation: The installation has attempted to read the message file
          INSTALL.MSG but has been unable to get the string representations for
          yes, no, and quit.

          User Response: There may be a fault with your installation diskette,
          check with your System Administrator, or refer back to your supplier.

EAK0061E  The drive specified is not valid

          Explanation: A drive you have specified does not exist or is not
          system-supported.

          User Response: Make sure that you specify a drive that exists, and
          that you are currently attached to. If you are installing on a LAN,
          ensure that you are logged on to the LAN.

EAK0062E  The install program cannot find the XCOPY command in your path.
          Change your path, or put XCOPY in a directory in your path, and
          retry.

          Explanation: The installation program uses the command XCOPY to copy
          files from the installation diskette to your specified target. It
          will not work without it.

          User Response: Make sure that you have the XCOPY program available on
          your machine, and that it is in the current path.

EAK0063E  PSS.EXE could not be found in the target directory of install.
          Installation must have failed. Please retry.

          Explanation: After installation, the installation program checks that
          PSS.EXE has been successfully copied on the hard disk. It returns
          this error if it cannot find the file.

          User Response: Go back to the start of the installation procedure and
          try to install again. If the problem persists, check with your System
          Administrator, or refer back to your supplier.

EAK0065E  Cannot open STARTUP.CMD; changes have not been made.

          Explanation: This may be because STARTUP.CMD is read-only.

          User Response:  Make sure you have write-access to STARTUP.CMD before
          asking PSnS/2 to change it automatically.  This only applies to OS/2
          Version 1.2 or 1.3.

EAK0066E  The only valid parameter is the name of a global rulebook to make
          active.

          Explanation: You may have tried to install using the name of
          something that is not a rulebook.

          User Response: Start installation again using a valid rulebook name.

EAK0067E  The global rulebook xxx cannot be found in the \SAMPLE subdirectory
          of this diskette.

          Explanation: You have tried to install using the name of a
          non-existent rulebook.

          User Response: Start installation again using a valid rulebook name.


ΓòÉΓòÉΓòÉ 24.2.2. Run-Time Errors ΓòÉΓòÉΓòÉ

PSS0100E  A fatal error has occurred: cause is xxx The program is shutting down

          Explanation: PSnS/2 has encountered an error from which it cannot
          recover.

          User Response: Restart PSnS/2.

PSS0101E  The PSnS profile has been destroyed. You should reinstall the product
          before continuing.

          Explanation: The PSnS profile contains information that PSnS/2 uses
          while it is running. If this profile is destroyed, the program must
          be reinstalled before it can operate correctly.

          User Response: Follow the instructions for removing PSnS/2 in the
          Technical Reference. Then reinstall the program.

PSS0102E  There has been a disk full error.

          Explanation: The disk you are backing up files to, the disk you are
          storing the PSnS/2 control files on, or possibly the disk you are
          backing up from may be full.

          User Response: Clear some disk space to allow PSnS/2 to operate
          properly.

PSS0103E  A valid backup command and restore command must be entered for
          non-OS/2 supported drives (use Full to see commands).

          Explanation: You have used a backup or restore command that is not
          valid, or is not in your current path.

          User Response: If the backup and restore commands are not visible,
          press the 'full' button to display them. Then type in the correct
          commands (see Specifying Drive Configurations for more details).

PSS0104E  The password you entered does not match that of the currently active
          global rulebook.

          Explanation: A global rulebook has a password which is defined by the
          person who created it.

          User Response: If you need to change the global rulebook, refer to
          the person who wrote it.

PSS0105E  Invalid drive and directory specified; the path you enter must exist,
          and be written out in full.

          Explanation: You have tried to use a non-existent drive or directory.

          User Response: Enter a valid drive and directory.

PSS0106E  The drive letter must be a letter of the alphabet.

          Explanation: Disk drives can only be referenced by the letters A to
          Z.

          User Response: Enter a valid drive letter.

PSS0107E  The 'kilobytes free' must be a number greater than one hundred.

          Explanation: PSnS/2 needs to have at least 100KB free on a removable
          volume before it can use it effectively.

          User Response: Find a removable volume with more than 100KB free.

PSS0108E  The pattern which you have given is invalid.

          Explanation: A pattern you have entered either contains invalid
          characters, or has an incorrect directory structure.

          User Response: See Specifying Patterns for File and Directory
          Matching for a full description of how to create patterns.

PSS0109E  The date is invalid. It must be specified in the country date format
          you are using.

          Explanation: PSnS/2 only accepts dates in the format that is commonly
          used in its country of origin.

          User Response: Enter the date in the correct date format.

PSS0110E  Drive xxx is not known. You should type details on the drive table.

          Explanation: You have referred to a drive that you have not yet
          defined to PSnS/2.

          User Response: See Specifying Drive Configurations for how to set up
          a non-system supported drive.

PSS0111E  There is no file fitting the description you typed.

          Explanation: PSnS/2 has failed to find the file, or files you
          specified.

          User Response: Check that you are using the correct pattern or file
          definition (see Specifying Patterns for File and Directory Matching
          for a full description of how to create patterns).

PSS0112E  You must have an active global rulebook before you can leave the
          rulebook list screen.

          Explanation: PSnS/2 cannot operate without an active global rulebook.

          User Response: Make a global rulebook active by selecting it in the
          rulebooks listbox, and pressing the Use item in the Rulebooks
          pull-down menu.

PSS0113E  There is no active global rulebook. Use the Setup action on the PSnS
          main panel to create one.

          Explanation: PSnS/2 cannot operate without an active global rulebook.

          User Response: Create one before continuing to use the program.

PSS0114E  A problem occurred backing up the current file to drive xxx.

          Explanation: PSnS/2 has detected an error with the drive.

          User Response: Check that the drive is operating correctly and retry
          the operation.

PSS0115E  You must specify a OS/2 supported system backup drive.

          Explanation: The system files PSnS/2 uses must be stored on a drive
          that is supported by OS/2.

          User Response: Change your selected system backup drive to one that
          is supported by OS/2 (for example your C drive).

PSS0116E  The add has failed.  Please retry with another volume.

          Explanation: PSnS/2 has been unable to add a new removable volume.

          User Response: Find another removable volume to use and retry the
          operation.

PSS0117E  Backup destination drive invalid; the A drive taken as the default.

          Explanation: You have tried to specify an invalid drive for backups.
          PSnS/2 has taken the default drive.

          User Response: If you do not want files backed up to the A drive,
          then choose your required destination.

PSS0118E  There is not enough free space for backup on volumes for drive xxx.
          Select OK to add another volume.

          Explanation: The current removable volume is full.

          User Response: Select OK and add another removable volume.

PSS0119E  The path entered is invalid.  Please try again.

          Explanation: The path you have entered either contains invalid
          characters or is in the wrong format.

          User Response: Enter a valid path. See Specifying Patterns for File
          and Directory Matching for a full description of how to create
          patterns).

PSS0120E  There is not enough memory to do this action.

          Explanation: PSnS/2 needs more memory to carry out your request.

          User Response: See Outline of Hardware and Software Requirements for
          details of the program's memory requirements.

PSS0121E  This name is not allowed because a rulebook of this name already
          exists.

          Explanation: All rulebook names must be unique.

          User Response: Use a different name when creating or copying this
          rulebook.

PSS0122E  The time specified was invalid. It should be hh:mm, in 24 hour form.

          Explanation: PSnS/2 only accepts times in this form.

          User Response: Enter a time as suggested.

PSS0123E  The name specified is an invalid name

          Explanation: PSnS/2 does not recognise the name you have used.

          User Response: Retry the operation using a valid name.

PSS0124E  There is not enough disk space on the drive with \PSS\SYSDATA to
          continue.

          Explanation: PSnS/2 has run out of disk space while updating its
          control files. It has halted execution instead because there is a
          risk of backup information being corrupted.

          User Response: Clear some disk space before continuing.

PSS0125E  The compress command xxx gave an error when used.

          Explanation: The compression program you have supplied has failed to
          work correctly.

          User Response: Check that you are using the compress command
          correctly, or back up using the in-built compression. Back up without
          compression if you continue to have problems.

PSS0126E  The copy command for disk xxx gave an error when used.

          Explanation: The copy command that you have supplied has failed to
          work correctly.

          User Response: Check that you are using the copy command correctly.

PSS0127E  Disk xxx gave an error; it may be full or write-protected. Please
          correct this before continuing.

          Explanation: PSnS/2 has tried to use the disk and failed.

          User Response: Check the disk. If there seems to be nothing wrong
          with it, try continuing anyway - it may have been an operating system
          error.

PSS0128E  Backup is already in progress.

          Explanation: You have tried to start a manual backup while PSnS/2 is
          backing up automatically.

          User Response: Wait for PSnS/2 to finish backing up before continuing
          with the manual backup.

PSS0129E  The file cannot be restored because there is no rulebook entry for
          it.

          Explanation: Files cannot be restored if they do not match any of the
          rules in the active rulebooks.

          User Response: If you want to restore this file, add a temporary rule
          to your active local rulebook that specifies where it should have
          come from. Then attempt to restore it again.

PSS0131E  The minimum update count was invalid; it must be from 1 to 99.

          Explanation: PSnS/2 will only accept trigger levels in the range 1 to
          99.

          User Response: Change the value in the trigger level field so it is
          within range.

PSS0132E  The number of backup generations was invalid; it must be from 1 to
          99.

          Explanation: PSnS/2 will only keep between 1 and 99 generations of
          backup.

          User Response: Change the value in the backup generations field so it
          is within range.

PSS0134E  There was an error from the internal compress function: reason code
          is xxx

          Explanation: The compression function has reported an error.

          User Response: Check that you have space on your backup disk. If the
          error remains, try to back up without compression.

PSS0135E  Integrity error found in control file xxx. You must recover this file
          from the control file backups, and restart PSnS/2.

          Explanation: One of the control files PSnS/2 uses to record
          information about files it has backed up has been damaged. Using it
          could cause problems with either backing up or restoring files.

          User Response: Restore the named control file and restart PSnS/2.

PSS0136E

          Explanation: Reserved

PSS0137E  Backup of this file is cancelled because there was not enough space
          on drive C for a temporary file.

          Explanation: PSnS/2 has attempted to compress and backup a file to a
          drive that is not system-supported and has not found sufficient space
          to perform the initial compression.

          User Response: Clear some disk space before continuing.

PSS0138E  PSnS/2 cannot check the space free on a non-OS/2 supported drive. You
          must enter free space yourself.

          Explanation: PSnS/2 cannot access non-OS/2 supported drives, so you
          must tell it how much free space is available.

          User Response: Find out how much space is free on the drive and tell
          PSnS/2 that number.

PSS0139E  The help file xxx cannot be found, so it cannot be loaded.

          Explanation: The help panels that are supplied with PSnS/2 have been
          damaged in some way or deleted.

          User Response: Refer to the relevant section of this manual for the
          information, or reinstall PSnS/2.

PSS0140E  You do not have an active global rulebook. You will now be placed in
          the Rulebook List screen, where you must create one.

          Explanation: PSnS/2 cannot operate without an active global rulebook.

          User Response: Create a rulebook and make sure it is active before
          leaving the List of Rulebooks panel.

PSS0141E  This directory has subdirectories with backups in them. You must Drop
          the subdirectories before you can drop this directory.

          Explanation: PSnS/2 will not allow you to drop a directory for
          restoring purposes unless you drop all the subdirectories within it.

          User Response: Drop the subdirectories, and then drop the main
          directory.

PSS0142E  A problem occurred during backup; OS/2 returned the message "xxx".

          Explanation: There has been an error in communication between PSnS/2
          and OS/2.

          User Response: Retry the operation.

PSS0143E  Backup of this file to drive xxx could not take place, because no
          backup volume was made available.

          Explanation: PSnS/2 has been unable to backup files to a drive
          because no diskettes were made available.

          User Response: Prepare some removable volumes now to be ready for
          future backups

PSS0144E  You cannot restore this file because the target file exists and is
          read-only.

          Explanation: PSnS/2 cannot over-write files which have the
          'read-only' attribute set.

          User Response: If you want to restore the file, either delete the
          file or change its attribute so it is not read-only.

PSS0145E  Backup failed because a temporary file could not be opened - check
          your disk and try again.

          Explanation: During backup PSnS/2 creates a number of temporary
          files. It has failed to open one, possibly because the disk is full.

          User Response: Check your C drive before continuing.

PSS0146E  Backup cannot take place because files are being checked. Please try
          again when the checking has finished.

          Explanation: PSnS/2 carries out its disk checking in the background,
          but while it is doing its checking it will not allow the user to take
          a backup.

          User Response: Wait until PSnS/2 has stopped checking files, and then
          do your backup.

PSS0147E  Backup of files spotted cannot take place because another backup is
          already in progress.

          Explanation: PSnS/2 cannot carry out two backups at the same time.

          User Response: Wait until the backup has finished, and then perform
          your backup if it is still needed.

PSS0148E  You cannot delete your active global rulebook. Press OK to continue.

          Explanation: PSnS/2 will not allow you to delete the active global
          rulebook.

          User Response: None

PSS0149E  You cannot make an empty rulebook active. Add some rules to this
          rulebook, or use a different rulebook.

          Explanation: PSnS/2 will not allow you to use an empty rulebook.

          User Response: Add some rules to the selected rulebook by selecting
          the Edit option from the Rulebooks pull-down menu.

PSS0150E  The file you are trying to restore cannot be found, so it has not
          been restored.

          Explanation: PSnS/2 has been unable to find a backed up file
          (probably because it has been deleted).

          User Response: Check that the backup drive is working correctly, and
          that PSnS/2 can access it.

PSS0151E  The file you are trying to restore cannot be restored due to a
          problem with the target drive.

          Explanation: PSnS/2 has tried to restore a file, but it has
          encountered a problem with the drive that it is trying to restore to.

          User Response: Check that the target drive is not full, and that
          PSnS/2 can access it.

PSS0152E  Attempted restore using built-in compression method failed.

          Explanation: PSnS/2 has tried to restore a file, but it has
          encountered a problem with its internal compression method.

          User Response: Check that the drive you a trying to restore to is not
          full, and that PSnS/2 can access it.

PSS0153E  Attempted restore using your compression program failed.

          Explanation: PSnS/2 has failed to restore a file using a compression
          program that you supplied it with.

          User Response: Check that you have correctly defined the
          uncompression command in the Edit Rules panel.

PSS0154E  Attempted restore failed - check your backup files, and your
          hard-disk.

          Explanation: PSnS/2 has failed to restore a file due to a problem
          with either the source or the target drive.

          User Response: Check the drive that you are trying to restore from,
          and the drive you are trying to restore to.


ΓòÉΓòÉΓòÉ 24.2.3. Informational Messages ΓòÉΓòÉΓòÉ

PSS0200I  An empty global rulebook called 12345678 has been created for you.

PSS0201I  Format cannot take place because drive is in use. Try again later.

PSS0202I  Backup for this file will be delayed because the drive is in use.


ΓòÉΓòÉΓòÉ 25. Appendixes ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 26. Outline of Hardware and Software Requirements ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 26.1. Which Computers to Use ΓòÉΓòÉΓòÉ

To use PSnS/2 you require one of these computers: c.

o IBM Personal System/2 with an 80286, or higher, processor

o IBM PC-AT or PC-XT 286.


ΓòÉΓòÉΓòÉ 26.2. Possible Backup Devices ΓòÉΓòÉΓòÉ

PSnS/2 allows you to choose where backups are stored. Files can be backed up
to: c.

o Diskettes

o Fixed disks

o A host computer

o A central server on a LAN

o An optical disk.


ΓòÉΓòÉΓòÉ 26.3. Memory and Disk Requirements ΓòÉΓòÉΓòÉ

PSnS/2 will take up to 384KB of additional memory under OS/2. PSnS/2 occupies
about 300KB of disk space.


ΓòÉΓòÉΓòÉ 26.4. Network or Host System Requirements ΓòÉΓòÉΓòÉ

PSnS/2 may be used in a LAN or attached to a host computer. Three options are
available: c.

o LAN

o IBM processor host attachment

o IBM Application Systems host attachment.


ΓòÉΓòÉΓòÉ 26.5. Software Requirements ΓòÉΓòÉΓòÉ

PSnS/2 operates under IBM OS/2 Version 1.2 and above.

LANs are supported by the IBM Personal Computer LAN Program, or other LAN
sharing programs that provide transparent access from an application in one
Personal Computer to a disk on another Personal Computer.

Note:  Since PSnS/2 uses advanced features of the OS/2 Presentation Manager*,
it will not run under version 1.0 or 1.1 of OS/2.


ΓòÉΓòÉΓòÉ 27. Using PSnS/2 Windows ΓòÉΓòÉΓòÉ

PSnS/2 uses windows in the same way as any other application uses OS/2 windows.
(They are designed in accordance with IBM's Systems and Applications
Architecture (SAA) standards.) If you are not familiar with OS/2 concepts such
as radio buttons and menu bars, please run the tutorial Introducing OS/2, which
comes with the OS/2 operating system itself.


ΓòÉΓòÉΓòÉ 27.1. Reading the Main PSnS/2 Menu Window ΓòÉΓòÉΓòÉ

This section explains the information on the PSnS/2 main menu window.


The PSnS Main Menu Window


ΓòÉΓòÉΓòÉ 27.1.1. Backup Restore Setup Logfile Help ΓòÉΓòÉΓòÉ

This is the menu bar showing all the actions available in PSnS/2. If you select
or click on any of the items, a pull-down menu appears. You may then select
from the options, by clicking with the mouse if you have one. If you are not
using a mouse, either press Alt+<highlighted letter>, or press <F10> to move
the cursor to the menu bar and then the Left/Right and Up/Down cursor keys.


ΓòÉΓòÉΓòÉ 27.1.2. Files spotted for incremental backup ΓòÉΓòÉΓòÉ

This shows the number of files on the PSnS/2 list of files created or changed
since the last backup that match rules in the active rulebooks.


ΓòÉΓòÉΓòÉ 27.1.3. Next disk check in <nn> minutes ΓòÉΓòÉΓòÉ

This shows when the next disk check for files which have been changed since the
last backup will be.


ΓòÉΓòÉΓòÉ 27.1.4. Last backup was on <date> at <time> ΓòÉΓòÉΓòÉ

This shows the time and date of the last backup if there was one, or No last
backup time if there has not been one.


ΓòÉΓòÉΓòÉ 27.1.5. Active Global rulebook ΓòÉΓòÉΓòÉ

Shows the name of the global rulebook in use. If you installed PSnS/2 with
GENERAL as the global rulebook, you will see GENERAL written here.


ΓòÉΓòÉΓòÉ 27.1.6. Active Local rulebook ΓòÉΓòÉΓòÉ

Shows the name of the local rulebook in use. If there is no local rulebook in
use, nothing will be displayed here.


ΓòÉΓòÉΓòÉ 28. Specifying Patterns for File and Directory Matching ΓòÉΓòÉΓòÉ

"Patterns" are fundamental to PSnS/2. They are much used to identify compactly
groups of files on which you want to perform some action. Examples include: c.

o Rules in rulebooks

o Backing up groups of files manually

o Restoring groups of files

All OS/2 files are identified by:

drive:\...path...\name.ext

where:

drive     Is the drive letter of the drive where the directories may be found

path      Represents all the directories and subdirectories

name      Is the file name

ext       Is the optional three-letter file extension

For instance, a file called FRED.A in the directory DOC of drive C can be
completely identified by:

C:\DOC\FRED.A

To specify groups of files or directories you can use the special wildcard
characters which you may know from their use in OS/2 commands such as DIR.

PSnS/2 uses the following wildcard characters:

?   Represents any single character in this position in the pattern

*   Represents any number of characters (including none) in this position in
    the pattern.

You may put any combination of wildcards in a pattern, but there is no point in
putting two stars next to each other, as in a**b, because the second one will
be ignored, as a*b means the same thing.

You can also use wildcards in a directory path, but in this case there is an
important additional rule to remember: Anything after the last backslash in a
pattern refers to the filename of the file, and anything before the last
backslash refers to its drive and path.

In addition to wildcards, there are other ways of specifying patterns. If you
omit "drive:", all drives will be included; if you omit "\...path...\", all
directories and subdirectories will be included. If you omit ".ext", then files
with any file extension will be included.

Some examples of patterns are:

aa?bb          Includes aa3bb and aacbb, but not aaccbb.

aa*bb*         Includes all of the above examples and aa32bbcd.

*.*            Includes all files on every drive; as would *:*.*. However, *.
               would only match files which had no extensions.

c:\x           Includes all files called X, with any extension in the root
               directory of the C drive.

c:x.           Includes all files called X, with no extension, in any directory
               of the C drive.

c:\user\*.*    Includes all files in the directory C:\USER\

c:\user\*\*.*  Includes all files in all subdirectories of the directory
               C:\USER.

jim*\*         Includes all files with any extension, in any subdirectory
               within a directory which has a name starting with jim, on any
               drive. It will include: C:\JIM\FILE.SYS, because the * after jim
               can match zero characters. C:\JIMBO\AND\UNCLE.BOB, because the *
               after jim catches any number of characters. However *jim* will
               also include C:\COUSIN\JIM\AND\UNCLE.BOB, because the * before
               jim matches anything too.

Note:  A colon is a special case because it will only be recognised when it is
the second character of a specification. For example, c?xyz will include c3xyz
but not c:xyz. The last backslash is also a special case. Any characters after
the last backslash are assumed to refer only to the file name and extension. If
there are no backslashes, all the characters refer only to the file name and
extension - all drives and paths are checked in this case.

You should use patterns with great care because, if they are too vague, you
might include a great many files you do not need. Especially avoid * on its
own. Make sure you have specified only the files you need and no more.

You can only use the wildcard characters * and ? in directories when specifying
patterns in rulebooks. If you do use a pattern where it is not allowed, you
will see a message telling you that the pattern supplied is invalid.


ΓòÉΓòÉΓòÉ 29. Glossary ΓòÉΓòÉΓòÉ


ΓòÉΓòÉΓòÉ 29.1. A ΓòÉΓòÉΓòÉ

action    A defined task that is performed by an application to modify or
          manipulate the properties of a file or data.


ΓòÉΓòÉΓòÉ 29.2. B ΓòÉΓòÉΓòÉ

backup

    1. A copy of a file stored in case the original file is lost or damaged.

boot, or boot-up To start (the computer or system) either by switching it on,
          or by using Ctrl-Alt-Delete.


ΓòÉΓòÉΓòÉ 29.3. C ΓòÉΓòÉΓòÉ

Cancel    A standard button that abandons any changes which have not been
          confirmed (by the OK button: see OK) and returns to the previous
          window.

Checkbox  A square box with associated text that represents a choice.  When the
          user selects the choice, an "X" (or a / under OS/2 Version 2) appears
          in the check box to indicate that the choice is selected.  The user
          can clear the check box by selecting the choice again, thereby
          cancelling selection (compare radio button).

checkmark The symbol / that indicates a settings choice is active.

click     To press and release the mouse button (the left-hand button, if there
          is more than one), without moving the mouse pointer from the
          selection.

command line The line of a screen in DOS or OS/2 on which a command or data is
          entered. The command line often begins with a prompt, such as C:\ to
          indicate the drive and path currently being used.

compress  To reduce the size of file so the same amount of data takes up less
          storage space. PSnS/2 automatically compresses backups using its own
          compress program, unless otherwise informed in the rulebook.
          Compressed files must be uncompressed before the original file can be
          used again.

CONFIG.SYS A special DOS and OS/2 file that contains details of system
          configurations to be set up when the system is booted.

control files Special PSnS/2 files used to store information describing the
          files which have been backed-up and the locations of the backup
          copies.


ΓòÉΓòÉΓòÉ 29.4. D ΓòÉΓòÉΓòÉ

default   The assumed input to be used if no other input is given.

directory A named group of files and/or sub-groups (subdirectories) used in DOS
          and OS/2.

DOS       IBM's Disk Operating System. An operating environment used on IBM
          Personal Computers.


ΓòÉΓòÉΓòÉ 29.5. E ΓòÉΓòÉΓòÉ

ECF (Enhanced Connectivity Facility) An IBM product which provides for resource
          sharing and data exchange between IBM Personal Computers and IBM
          System/370 computers.

Enter     A command that submits information to the computer for processing.

entry field A field on a window that PSnS/2 displays with text or data, which
          may be changed or entered again by the user.

Exit

    1. The action that closes PSnS/2 and all windows associated with it.

    2. To leave or close-down any application.


ΓòÉΓòÉΓòÉ 29.6. F ΓòÉΓòÉΓòÉ

field     An identifiable area in a window, for example an entry field into
          which a user can type text, or a field of radio buttons from which a
          user can select one choice in the field.

file      A unit of data, used by applications and DOS or OS/2 or other
          operating system.

Format (a disk) To erase a disk completely and prepare it for new data.

Full backup A backup of all the files in a specific group, regardless of
          whether they have been altered since the last backup was taken.
          (compare incremental backup)


ΓòÉΓòÉΓòÉ 29.7. G ΓòÉΓòÉΓòÉ

generation One version of a backup copy of a file. If there is more than  one
          generation, the most recent version is the first generation, the
          second-most recent is the second generation, and so on. When the
          number of generations of a file exceeds the maximum specified, the
          oldest generation is lost.


ΓòÉΓòÉΓòÉ 29.8. H ΓòÉΓòÉΓòÉ

Help      A standard action and button; present on every PSnS/2 window, that
          provides information about the current window, the actions available
          and general information about the application. Can also be activated
          using the <F1> key.

host      A larger computer to which one or more smaller computers are
          connected, so they can use the resources of the larger computer.


ΓòÉΓòÉΓòÉ 29.9. I ΓòÉΓòÉΓòÉ

incremental backup A backup of files which have been altered since the previous
          backup. (compare Full backup)

initial value Information in an entry field that PSnS/2 fills in when a window
          is first used.


ΓòÉΓòÉΓòÉ 29.10. K ΓòÉΓòÉΓòÉ

kilobyte (KB) 1024 bytes of data.


ΓòÉΓòÉΓòÉ 29.11. L ΓòÉΓòÉΓòÉ

Local Area Network (LAN) A standard IBM method of connecting small computers in
          a network.


ΓòÉΓòÉΓòÉ 29.12. M ΓòÉΓòÉΓòÉ

menu      A list of choices that can be applied to an object.  A menu can
          contain choices that are not available for selection in certain
          contexts.  These choices are indicated by reduced contrast.

menu bar  The area at the top of a window which contains routing choices that
          provide access to pull-down menus.  There are menu bars in the PSnS/2
          main menu and the List of Rulebooks windows.

mouse button A switch on a mouse used to select choices or start actions.

mouse pointer The symbol displayed on the screen, moved by the mouse, to show
          where the next click will have effect.


ΓòÉΓòÉΓòÉ 29.13. O ΓòÉΓòÉΓòÉ

OK        A common action or button used to confirm the information displayed
          on the current window; including any changes made, and to return to
          the previous window in the hierarchy.

OS/2      IBM's Operating System/2.* An operating system used to provide the
          operating environment on IBM Personal System/2 computers.

optical disk A storage device in which data are stored on a disk as a sequence
          of tiny pits which are created or read by a very small laser beam.

overwrite To write data at the same place on a storage device as data already
          there, so erasing the original data. For example, if a file is
          created which has the same drive, path and file name specifiers as a
          previously existing file, and it is written on a disk drive, the file
          originally stored under that name will be replaced.


ΓòÉΓòÉΓòÉ 29.14. P ΓòÉΓòÉΓòÉ

panel     an entire screenful of information.

parent    The directory which contains the current directory as a subdirectory.
          Denoted by ...

path      A sequence of directories which DOS or OS/2 will automatically search
          through if a called program is not found on the current directory.

pointer   A visible cue, usually in the shape of an arrow, that a user can move
          with a pointing device.  Users place the pointer over the object they
          want to work with.

pull-down menu A menu that extends from a selected choice on a menu bar or from
          the system-menu symbol.  The choices in a pull-down menu are related
          to one another in some manner.


ΓòÉΓòÉΓòÉ 29.15. R ΓòÉΓòÉΓòÉ

radio button A circle with text beside it.  Radio buttons are combined to show
          a user a fixed set of choices from which the user can select one.
          The circle becomes partially filled when a choice has been selected
          (compare check box).

read-only access Access to a storage device in which the computer can only read
          data from the device and not write data to the device. See write
          access.

removable volume A volume which can be used to store backups, but which is
          interchangeable with other volumes in a particular drive. For
          example, there will be several diskettes available for backups in a
          diskette drive. PSnS/2 must be told if a drive uses removable volumes
          so that it can prompt the user to ensure the correct one is in the
          drive before it writes or reads backup files on it.

rulebook  A special PSnS/2 file that describes which sets of files are to be
          backed-up and where the backup copies are stored. There are two types
          of rulebooks: local and global. A global rulebook can be shared by
          many computers on a network, to provide a way of ensuring a
          particular standard of backup and to provide a common rulebook for
          backups to a central computer. A local rulebook, however, applies
          only to the computer on which PSnS/2 is installed.

root      The directory on a drive which contains all other subdirectories.


ΓòÉΓòÉΓòÉ 29.16. S ΓòÉΓòÉΓòÉ

select    To mark or choose an item or action on a window or menu.

server, backup A computer in a network that takes and stores backups of files
          from other computers on the network.

spreadsheet An application program that provides a large matrix or grid for the
          manipulation of numbers and figures; especially financial
          information. A special OS/2 file that contains commands which are
          executed when an OS/2 system is booted.  This only applies to Version
          1.2 or 1.3 of OS/2.

stand-alone Of or relating to a Personal Computer which is not connected to any
          other computer by any means directly supported by DOS or OS/2 (such
          as by a LAN).

Stop      A standard button used in progress indicator windows, such as the
          backup in progress indicator, which, when activated, cancels the
          progress of the action, such as cancelling the backup, at the next
          convenient stopping point.

subdirectory A directory contained within another directory.

System backup diskette A diskette used to hold backups of PSnS/2 control files.


ΓòÉΓòÉΓòÉ 29.17. T ΓòÉΓòÉΓòÉ

tab       To use the Tab key to move the cursor, or screen position to the next
          object, button, action or item on a window. The cursor or screen
          position moves in sequence, from top to bottom and left to right.
          After the bottom-right-most item, the next position will be the
          top-left-most item.

tape streamer A high-capacity, tape-based storage device that is used with
          Personal Computers for storing large amounts of information;
          especially backup copies of files.

token     A symbol that represents all or part of a file identifier.

transparent access Access to a device; such as a disk drive, on another
          computer, where the remote device cannot be seen to be different or
          separate from the accessing computer.


ΓòÉΓòÉΓòÉ 29.18. U ΓòÉΓòÉΓòÉ

uncompress To restore a file which has been compressed so that it may be used
          by an application again.


ΓòÉΓòÉΓòÉ 29.19. V ΓòÉΓòÉΓòÉ

volume    A device providing the storage medium in a drive; such as a diskette,
          but not the diskette drive.


ΓòÉΓòÉΓòÉ 29.20. W ΓòÉΓòÉΓòÉ

window    An area with visible boundaries that presents a view of an object, or
          with which a user conducts a dialog with a computer system.

write access Access to a storage device where the computer is permitted to
          store data to the storage device.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

PSnS/2 looks at the archive bit on each file; if the archive bit is on, the
file is counted as having changed.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

A drive is directly supported by OS/2 if the normal OS/2 commands such as DIR
and COPY work for that drive. If you can type DIR X:, where X is the name of
the drive, and see a list of files on the drive, then it's directly supported
by OS/2.

If you want to use drives not directly supported by OS/2, you must inform
PSnS/2 and provide the commands it must use to communicate with these devices.


ΓòÉΓòÉΓòÉ <hidden>  ΓòÉΓòÉΓòÉ

Note that name should be the name of a rulebook you already have defined.