| Previous | Contents | Index |
This chapter describes actions specific to managing individual layered
products.
12.1 DECfax
If SysWorks is installed at the Turnkey level or at the System level and overnight processing is enabled, it will manage the cleanup of the DECfax database in place of the default DFX$CLEANER procedure provided with DECfax. To enable the correct operation of overnight processing it is necessary to edit the following DECfax startup command procedure to stop submission of the DFX$CLEANER job:
SYS$STARTUP:DFX$START_COMPONENTS.COM |
Normally this command procedure starts various DECfax components and
then submits the DFX$CLEANER job. Placing the DCL command line $
exit after the last DECfax manager utility and before the use of
the lexical f$getqui(...) will stop the command procedure from
submitting the DFX$CLEANER job.
12.2 Pathworks (LAN Manager)
SysWorks provides a utility to directly access the LAN Manager share
database from DCL so that the SWRK_MANAGE_PATHWORKS.COM command
procedure can manage share as appropriate.
12.3 Pathworks (Macintosh)
This chapter describes what and how to use SysWorks to monitor the system.
The monitor process watches various activites on the system and takes
appropriate action when an undesirable state exists. Basically, a scan
of the system is made every SWRK_MONITOR_INTERVAL (usually 1) minutes.
The following notes outline the activites watched and the actions to be
taken.
13.1 Application and Group Control Jobs
Application and group control jobs (eg. BOOT and SHUTDOWN) are
submitted to the SWRK$BATCH batch queue. These control jobs should be
aborted if they accumulate more than SWRK_CONTROL_JOB_TIMEOUT worth of
elapsed time. Note that the queues are scanned each
SWRK_CONTROL_JOB_TIMEOUT minutes rather that SWRK_MONITOR_INTERVAL,
except that when jobs are detected which would timeout before the next
SWRK_CONTROL_JOB_TIMEOUT minutes are elapsed, the time until the next
batch queue scan is reduced from SWRK_CONTROL_JOB_TIMEOUT minutes down
to a time which should match the timeout time of the next job to
timeout. This algorithm reduces the overhead of checking the batch
queues every SWRK_MONITOR_INTERVAL minutes. Note also that if the node
is a cluster member, a check is only made of batch queues executing on
the local node.
13.2 Disk Free Space Low
Every SWRK_DISK_CHECK_INTERVAL minutes all the disk volumes directly attached to the local node, or served by a non host (eg HSC or DSSI) and having the appropriate allocation class are checked for a low space condition. This low space threshold is specified as a percentage of total disk space. Each volume may have a specific low space level, or by default a system wide low space level is used.
This scan takes some time which is why it is done only every
SWRK_DISK_CHECK_INTERVAL minutes rather than SWRK_MONITOR_INTERVAL
minutes - the main weakness being the increased time to detection.
13.3 Node Shutdown or Reboot
A check is made to see if the node is to be shut down. Appropriate
warning messages are sent to all users, and at the indicated time, the
monitor shuts down the node.
13.4 Restart
A check is made to see if the monitor should be restarted. The restart
flag is set by the "Restart monitor" task in the operations menu, and
by installations (or downloads) of the SWRK software.
13.5 Special Times
A number of special times are detected and appropriate action taken.
These times include system wide application start (typically 8:00 am),
system wide application stop (typically 6:00 pm), midnight (at which
time the overnight system analysis and repair job is submitted and the
monitor is automatically restarted), and a security domain time
synchronization.
13.6 DECfax Servers
Every SWRK_DECFAX_CHECK_INTERVAL minutes a check is made that all of the defined DECfax servers are running. If any server is not running, a message is broadcast and that server is started using the FAX/MANAGER START SERVER command.
This scan takes some time which is why it is done only every SWRK_DECFAX_CHECK_INTERVAL minutes rather than SWRK_MONITOR_INTERVAL minutes - the main weakness being the increased time to detection.
This chapter describes the remaining miscellaneous system management tasks that are not directly related to meta objects or described elsewhere in this manual.
This glossary contains an alphabetic list of all the common prompts
used in task dialogs. If a task has a specific prompts not used
elsewhere, it is documented under that task. All other prompts are
documented here.
: An account code may be entered. When adding an
application environment, group or user, or when managing an account,
this item is mandatory.
:
:
:
[SYS$BATCH]:
:
[Normal]:
[Yes]:
:
:
[USR]:
: A cluster name should be entered. By default, the
cluster name from which the operation is being initiated is assumed.
Note that this question will not be asked on clusters which are below
the site level within the network.
:
:
[No]:
:
:
:
[Yes]: Indicates whether the associated environment
should also be created. This question is only asked for add
operations where an associated create operation also exists.
[Yes]:
: An optional value for a members details. The format
is the DEC standard absolute date which is DD-MMM-YYYY.
[Yes]:
:
[No]:
[No]:
: A free text single line description may be entered.
When adding an object, this attribute should be used, althiugh some
objects use a default description if this attribute is left blank.
_Directory/Tape):
:
:
:
:
:
:
:
:
:
:
[TODAY]:
:
:
[No]:
:
:
:
:
:
:
:
[Source]:
:
: A required value for a member's details. The first
letter of the given name is used to form part of the member lookup key.
It also forms part of the default owner name.
:
:
:
:
:
:
[Yes]:
[Yes]:
[Yes]:
:
:
:
:
: A location code may be entered. When adding an
application environment, group or user, or when managing a location,
this item is mandatory.
:
:
:
:
:
:
:
[Ascii]:
: An optional value for a member's details. The first
letter of the each middle name is used to form part of the member
lookup key. These first letters also form part of the default owner
name.
[Yes]:
_type:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
[SYS$OUTPUT]: A specific output file specification may
be entered. By default, SYS$OUTPUT (the standard output stream) is
assumed.
[No]:
: The free format full name of the member. Where the
member is a user who is granted access to the PATHWORKS system user
class
, this name is used as the AppleShare
network alias name.
:
: A password may be entered. By default, a random
password is used when objects are being added. Note that the minimum
and maximum password lengths can be set as system wide parameters. In
general the minimum password lengtn is 6 characters. If AppleShare
or Microsoft products are being used, the maximum password length is 8
characters.
:
[Yes]:
[No]:
:
[Yes]:
:
:
:
:
:
:
:
[No]:
:
:
:
:
: An optional value for a members details. Used to
indicate an alternative the the persons given name when generating a
letter. For example the members given name may be William, but their
salutation could be Bill.
:
:
:
:
:
[BEGINNING]:
:
:
:
:
:
: A required value for a member's details. The surname
is used to form part of the member lookup key. It also forms part of
the default owner name.
:
:
:
:
:
:
:
:
:
:
:
[TODAY]:
[Yes]:
:
:
[Default]: Indicates whether a secure task should secure files using the default action (i.e. SET SECURITY/DEFAULT) or an explicit action (i.e. SET SECURITY/ACL=(...)/OWNER=.../PROTECTION=(...)).
The advantage of the default secure action is that it is faster and does not change the modification dates of the secured files. This preservation of modification dates stops an incremental build following a secure task turning into an effective full build.
The advantage of the explicit secure action is that it is more thorough. It was also the action used in earlier versions of SysWorks. Note that an incremental build following a secure task using the explicit action effectively becomes a full build since all sources appear to be new.
By default the default action is used.
:
:
:
:
[Yes]:
:
:
:
[No]:
:
:
:
:
| Index | Contents |