| Previous | Contents | Index |
This chapter describes how to use SysWorks to manage software.
6.1 Overview
The Software Management Menu is selected using Manage =>
Software from the session manager. It displays the menu
illustrated in Figure 6-1 and prompts for a selection.
Figure 6-1 Software Management Menu
SysWorks manages software using the following objects:
Brief descriptions of these meta objects are given below. More detailed descriptions are available in the SysWorks Model Reference.
A product is a set of software purchased from a supplier and installed on a computer. For software created or modified for specific purposes, an application is used. See the SysWorks Application Development Guide for details about how to develop applications.
A license is a mechanism for products to determine if they can be used by a computer or user. Some licenses cover more than one product and similarly a product can check more than one license to validate its usage. Note that some products allow different levels of access based on different licenses.
A PAK is a mechanism for loading a license onto one or
more computers. A PAK consists of the supplier code, the license name,
the authorisation code (similar to a serial number) and a checksum.
6.2 Managing Licenses
This chapter describes how to use SysWorks to manage licenses.
Since most licenses are already registered in SysWorks, it is not generally necessary to manage licenses.
The License Management Menu is selected from the Software Management Menu. It displays the menu illustrated in Figure 6-2 and prompts for a selection.
Figure 6-2 License Management Menu
This task adds a new account to the network.
Example:
Account: |
This task modifies a licenses details.
Example:
Account: |
This task removes a license from the network.
Example:
Account: |
This task generates a report about licenses.
Example:
Output [SYS$OUTPUT]: |
This chapter describes how to use SysWorks to manage product authorisation keys (PAKs).
Since most PAKs are already registered in SysWorks, it is not generally necessary to manage PAKs.
The PAK Management Menu is selected from the Software Management Menu. It displays the menu illustrated in Figure 6-3 and prompts for a selection.
Figure 6-3 PAK Management Menu
This task adds a new account to the network.
Example:
Account: |
This task modifies a PAKs details.
Example:
Account: |
This task removes a PAK from the network.
Example:
Account: |
This task generates a report about PAKs.
Example:
Output [SYS$OUTPUT]: |
This chapter describes how to use SysWorks to manage layered products.
Since most layered products are already registered in SysWorks, it is not generally necessary to manage layered products.
The Layered Product Management Menu is selected from the Software Management Menu. It displays the menu illustrated in Figure 6-4 and prompts for a selection.
Figure 6-4 Layered Product Management Menu
This task adds a new account to the network.
Example:
Account: |
This task modifies a layered products details.
Example:
Account: |
This task removes a layered product from the network.
Example:
Account: |
This task generates a report about layered products.
Example:
Output [SYS$OUTPUT]: |
This chapter describes how to use SysWorks to manage storage. The storage management menu is selected using Manage => Storage from the session manager. It displays the menu illustrated in Figure 7-1 and prompts for a selection.
Figure 7-1 Storage Management Menu
SysWorks manages storage on disks and tapes using a number of objects. Those which are similar for all disks and tapes include:
Objects shared by disks tapes and other objects include:
Objects specific to tapes and removable disks include:
Objects specific to disks include:
Other objects include:
Standard operations include:
Brief descriptions of these meta objects are given below. More detailed descriptions are available in the SysWorks Model Reference.
A device is a piece of computer hardware and as such is also represented as equipment. Its includes information such as location, serial number and supplier etc.
A device type is the model for a device and as such is also represented an equipment type. Its description includes the OpenVMS device type (not to be confused with the SysWorks device type). SysWorks has a pre-installed list of all Digital disk and tape devices supported by OpenVMS.
Disk or tape media is the actual disk, diskette, tape cartridge, cassette or reel which is loaded into a device and initialized or mounted. Note that for fixed disk drives, the media is present inside the device. The media has a name or label which is usually affixed to its outer packaging.
The media type is the model for some media. Particular device types can use one or more media types and media types can be used by one or more device types. For instance, each newer model of a device type typically supports the media types of its previous models, although not always with the same functionality. An example is the TK70 tape drive (device type) which can read and write TK70 tapes (media type) while providing read only access to TK50 tapes (media type).
A volume is the information container placed on some media. A new media is initialized with a volume. Generally their is a one to one correspondence between a media and a volume. As such the volume name and the media name are the same. An exception to this model might be a software distribution package in which the same volume may exist on multiple media. A tape volume may have an expiry date at which it changes from the used state to the unused state.
A volume set is a set of two or more volumes which are bound together to form a larger storage container than a single volume. A volume set is referred to as a volume for most discussions.
A logical disk is a set of broadly related data spanning one or more disk volumes. For example SysWorks supports a user logical disk and a Pathworks logical disk. A logical disk is represented as a search list of logical sub-disks.
A logical sub-disk is a root directory on a disk volume which is placed in the search list which constitutes a logical disk.
A save-set is a special file created by a backup which contains the files which were backed up. With tape media a tape volume may contain one or more save sets. The last save set on the tape may be continue onto another tape i.e. a save-set may span two (or more) tape volumes. This practice is discouraged since it complicates storage management. By default, SysWorks creates one or more backup save-set for a single backup oeration on a single tape volume.
A catalog is a list of the files placed in storage. When each save-set is created, the backup utility produces a journal of which files have been stored in the save set. SysWorks later reprocesses this journal to add entries to the catalog. When a tape volume is erased or reused (i.e. re-initilized), all file entries belonging to all save-sets which were on the volume are removed from the catalog. A catalog can be searched from a number of perspectives including file name and type or extension, directory name, application environment, group or user name, disk volume, disk device, save-set, tape volume etc.
A pool is a set of media from which media can be selected. Attributes include the default tape media name format (eg. BCK###) and last used (eg. 000). When tape media are added to a tape pool, the tape media name defaults to the next unused name (eg. BCK001).
A storage model describes a backup which is used regularly and is usually executed as a system job. Attributes include expiry interval (eg. 10 days, 40 days, 366 days).
A system job is an operation performed on a regular
basis. It includes frequency (eg. daily, weekly, monthly), start window
(eg. must start between 2am and 4am), finish window (eg must finish
before 8am) etc. The operation can be represented by a DCL command
procedure or a storage model.
7.1.2 Operations
Brief descriptions of the operations relating to storage management are given below. More detailed descriptions are available in the SysWorks Object Model Glossary.
A backup makes copies of files onto removable media for storage. With SysWorks each backup operation creates one or more save-sets. Multiple save-sets are created when a backup spans more than one logical data structure. An example of this is when a disk volume is backed up - a disk volume may have multiple logical sub-disks so one save-set is created for each logical sub-disk. A backup may be based around an appropriate object including:
An archive is a backup operation followed by a delete of all the files which were backed up.
A recover operation brings back files from storage. Where the files constitute a database, a roll forward may be used to recover the latest data.
A restore operation brings back a total set of files
from storage. Where the files constitute a database, a roll backward to
the database state at backup may be used.
7.2 Starting to use Storage
This section describes how to start using SysWorks storage management.
First you need to register all your tapes with SysWorks. To do this, use the Add a tape media task from the Tape Media Management Menu.
For tapes which are new or are being recycled (i.e. the existing contents can be destroyed) answer yes to the Initialize prompt.
Tape pool [GENERAL]: Tape media [BCK001]: Tape volume [BCK001]: Initialize (Yes/No) [No]: State (Used/Offsite/Unused) [Used]: Expires (DD-MMM-YYYY/DDDD/Never) [30]: |
This chapter describes how to use SysWorks to manage disks.
The disk management dispatch menu is selected using Manage => Disks from the session manager or by using Manage => Storage from the session manager and selecting the DISKS menu. It displays the menu illustrated in Figure 7-2 and prompts for a selection.
Figure 7-2 Disk Management Dispatch Menu
The disk device management menu is selected by entering DEVICES at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-3 and prompts for a selection.
Figure 7-3 Disk Device Management Menu
The disk device type management menu is selected by entering DEVTYPES at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-4 and prompts for a selection.
Figure 7-4 Disk Device Type Management Menu
The disk media management menu is selected by entering MEDIA at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-5 and prompts for a selection.
Figure 7-5 Disk Media Management Menu
The disk media format management menu is selected by entering FORMATS at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-6 and prompts for a selection.
Figure 7-6 Disk Media Format Management Menu
The disk media type management menu is selected by entering MEDTYPES at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-7 and prompts for a selection.
Figure 7-7 Disk Media Type Management Menu
The disk volume management menu is selected by entering VOLUMES at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-8 and prompts for a selection.
Figure 7-8 Disk Volume Management Menu
The logical disk management menu is selected by entering LOGICALS at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-9 and prompts for a selection.
Figure 7-9 Logical Disk Management Menu
The logical sub-disk management menu is selected by entering SUBDISKS at the selection prompt of the disk management dispatch menu. It displays the menu illustrated in Figure 7-10 and prompts for a selection.
Figure 7-10 Logical Sub-Disk Management Menu
This chapter describes how to use SysWorks to manage tapes.
The tape management menu is selected using Manage => Tapes from the session manager or by using Manage => Storage from the session manager and selecting the TAPES menu. It displays the menu illustrated in Figure 7-11 and prompts for a selection.
Figure 7-11 Tape Management Dispatch Menu
The tape device management menu is selected by entering DEVICES at the selection prompt of the tape management dispatch menu. It displays the menu illustrated in Figure 7-12 and prompts for a selection.
Figure 7-12 Tape Device Management Menu
The tape device type management menu is selected by entering DEVTYPES at the selection prompt of the tape management dispatch menu. It displays the menu illustrated in Figure 7-13 and prompts for a selection.
Figure 7-13 Tape Device Type Management Menu
The tape media management menu is selected by entering MEDIA at the selection prompt of the tape management dispatch menu. It displays the menu illustrated in Figure 7-14 and prompts for a selection.
Figure 7-14 Tape Media Management Menu
The tape media type management menu is selected by entering MEDTYPES at the selection prompt of the tape management dispatch menu. It displays the menu illustrated in Figure 7-15 and prompts for a selection.
Figure 7-15 Tape Media Type Management Menu
The tape pool management menu is selected by entering POOLS at the selection prompt of the tape management dispatch menu. It displays the menu illustrated in Figure 7-16 and prompts for a selection.
Figure 7-16 Tape Pool Management Menu
The tape volume management menu is selected by entering VOLUMES at the selection prompt of the tape management dispatch menu. It displays the menu illustrated in Figure 7-17 and prompts for a selection.
Figure 7-17 Tape Volume Management Menu
This chapter describes how to use SysWorks to manage storage models.
| Previous | Next | Contents | Index |