FS
Documentation

Duty3G/Duty3G 5.1 Release Notes

From Documentation

(Difference between revisions)
Jump to: navigation, search
Revision as of 12:15, 20 September 2006
Moff (Talk | contribs)
(Upgrading duty3G)
← Previous diff
Revision as of 12:20, 20 September 2006
Moff (Talk | contribs)
(Technical Notes: Using duty3G V5.1)
Next diff →
Line 102: Line 102:
<br> <br>
-'''Temporary or trial licensing'''+==== Temporary or trial licensing ====
Duty3G may be issued with a temporary license for use in trials or demonstrations. Temporary licenses have an in-built expiry date. You must obtain a permanent license or a new temporary license from your COSMOS distributor to keep using COStask after the expiry date.NoteCOStask won’t install if the license key is due to expire within the next 7 days. In this case you will need to obtain a new license key from your COSMOS distributor. Duty3G may be issued with a temporary license for use in trials or demonstrations. Temporary licenses have an in-built expiry date. You must obtain a permanent license or a new temporary license from your COSMOS distributor to keep using COStask after the expiry date.NoteCOStask won’t install if the license key is due to expire within the next 7 days. In this case you will need to obtain a new license key from your COSMOS distributor.
<br> <br>
-'''COSMOS framework version required for duty3G V5.1'''+==== COSmanager framework version required for duty3G V5.1 ====
-Duty V5.1 requires COSMOS V4.2.5 or newer.+Duty V5.1 requires COSmanager V4.2.5 or newer.
<br> <br>
-'''Some platforms do not support all QUEUE features'''+==== Schedules and Schedtime ====
-Because duty3G uses the standard AT queues for job submission, any limitations in a platform’s implementation of AT queues may cause corresponding limitations in COStask’s queues. In particular some platforms restrict the number of queues available for use (for example HP/UX and DEC Unix), while some do not allow the specification of the maximum number of concurrent jobs (for example Linux). In most cases these limitations are very minor, and will only affect your site if you want to define new queues.+When duty3G V5.1 is installed on a system with a version of COSMOS V3.2.X, some new framework facilities are added to support more generalised scheduling. These include the datelist and schedule tables, which supersede the schedtime table (used in COStask V4.0). When the schedule table is installed, any locally added entries are copied into the schedule table. However, it is important to note that the schedtime and schedule tables are maintained separately, and so changes to one table will not be reflected in the other.If you are running COSMOS V3.2.X, the schedule and datelist tables can only be maintained from the COStask Configuration window.It is possible to update the schedule table with any new entries added to the schedtime table by running the program upg_sched which is installed in the COSMOS Install directory. Note however that this will NOT detect changes to existing entries in schedtime.
<br> <br>
-'''The QUEUEDEFS file'''+==== Audit Trails and Logfiles ====
-Most implementations of AT use a file called either /usr/lib/cron/queuedefs or /var/adm/cron/queuedefs. When COStask is installed, all existing entries in the QUEUEDEFS file are made available as COStask queues. Also, an extra AT queue, “t” is added for the main COStask queue. (On DEC Unix queue “f” is used instead, as queues beyond “f” are not permitted). After installation, QUEUEDEFS should NOT be edited directly, rather COStask’s queue maintenance (under COStask Configuration) should be used instead.+When duty3Gis installed, two new audit trails are created: duty_log and duty_compl. By default, these are created in the system spool area (usually /usr/spool or /var/spool).COStask is the primary audit trail, recording many actions that COStask performs:•Job Submission;•Start and end of job and task execution;•Most operator actions (cancel, hold etc.).Tasklog is used to hold all the logfiles created when a job or task executes. Depending on the amount of output produced by your jobs, this directory may become large, so it is important that audit trail cycling be configured correctly for your site to prevent these files from growing unbounded
<br> <br>
-'''Schedules and Schedtime'''+== New Features in this Release ==
-When duty3G V5.1 is installed on a system with a version of COSMOS V3.2.X, some new framework facilities are added to support more generalised scheduling. These include the datelist and schedule tables, which supersede the schedtime table (used in COStask V4.0). When the schedule table is installed, any locally added entries are copied into the schedule table. However, it is important to note that the schedtime and schedule tables are maintained separately, and so changes to one table will not be reflected in the other.If you are running COSMOS V3.2.X, the schedule and datelist tables can only be maintained from the COStask Configuration window.It is possible to update the schedule table with any new entries added to the schedtime table by running the program upg_sched which is installed in the COSMOS Install directory. Note however that this will NOT detect changes to existing entries in schedtime.+==== Generalised Calendaring for Automatic Jobs ====
 + 
 +Duty3G V5.1 uses the new schedule and datelist tables which provide more features than the old schedtime table:
 + 
 +*You can create named datelists, which, as the name implies, contain lists of arbitrary dates which can be used to either be included or excluded from a schedule.
 +*You can write your own program or script to determine if the current date and time is to be included in the schedule.Note that as with schedtime, scheduling of automatic jobs is still implemented via CRON.
<br> <br>
-'''Audit Trails and Logfiles'''+==== Notes Facility ====
-When duty3Gis installed, two new audit trails are created: duty_log and duty_compl. By default, these are created in the system spool area (usually /usr/spool or /var/spool).COStask is the primary audit trail, recording many actions that COStask performs:•Job Submission;•Start and end of job and task execution;•Most operator actions (cancel, hold etc.).Tasklog is used to hold all the logfiles created when a job or task executes. Depending on the amount of output produced by your jobs, this directory may become large, so it is important that audit trail cycling be configured correctly for your site to prevent these files from growing unbounded+You can now attach a text file of documentation to either a job or task. This text file can be view by the operator from the task monitor at any time, using the scroll facility. There is no facility provided to create notes files: you can simply use your favourite text editor (vi, emacs etc.). Notes files should be created in the local/notes directory.
<br> <br>

Revision as of 12:20, 20 September 2006

Contents

Overview and Features

Duty3G

Duty3G V5.1 encourages sound management practices by making it possible to perform the regular operations workload on UNIX, Linux and Windows servers in a way that is efficient, reliable, verifiable, compliant, and repeatable whilst protecting privileged user access. With duty3G you assign the privilege to the duty, and then assign the duty to the user.


New features in Duty3G V5.1

Key features of the new release are:

Enhanced operations

  • for a selected class
  • that run on a selected host
  • for a selected users' role

Improved auditing

  • by selected time period
  • that have ended in error
  • for selected duty
  • for selected user
  • for selected mode

Documentation


Installation Requirements

Software prerequisites

To install and run Duty3G V5.1 on a host, you must have:


Disk space required

Software Approximately 1 MB in the duty3G home directory.
Temporary Files While installing duty3G: less than 1 MB, to hold a copy of the software distribution.
While duty3G is running: less than 1 MB in /tmp.
Audit Trail For the duty3G audit trail, about 10 - 50 MB in the system spool area. The actual amount will depend on the activity on your system (e.g. how many duties are run), and how often you archive and delete the log files.
Compliance Reports For the duty3G compliance reports, about 5 - 20 MB in the system spool area.


Running Remote Duties on Windows

The current duty3G release supports running remote duties on Windows hosts which have the EWC (Enterprise Windows Client) V3.1.1 installed. This product may be purchased separately.


Upgrading duty3G

Figure 13 — Installation messages—upgrading from COSduty 3.0
Figure 13 — Installation messages—upgrading from COSduty 3.0
  1. Download the distribution file to /tmp on the target host.
  2. From the Configuration menu, select COSmanager configuration > Applications.
  3. Select Application > Install.
  4. Press Choose. You will see a list of the applications that can be installed. Choose the entry titled duty3G, and press Accept.
  5. COSmanager copies the duty3G files from the distribution file to the target directory, updates the duty3G audit trail and creates the duty3g compliance report directory.
  6. To migrate your existing COSduty 3.0 database to the newly installed version press Copy. Your existing database is copied and updated with new table columns.
  7. To make the newly install duty3G the default version press Accept, then press Continue.
Any automatic duties are added or re-added to the cosmos crontab.
This completes the upgrade installation. You must now restart COSmanager for the new version of duty3G to come into affect.


Technical Notes: Using duty3G V5.1

This section contains some technical notes and tips about using duty3G V5.1.


Temporary or trial licensing

Duty3G may be issued with a temporary license for use in trials or demonstrations. Temporary licenses have an in-built expiry date. You must obtain a permanent license or a new temporary license from your COSMOS distributor to keep using COStask after the expiry date.NoteCOStask won’t install if the license key is due to expire within the next 7 days. In this case you will need to obtain a new license key from your COSMOS distributor.


COSmanager framework version required for duty3G V5.1

Duty V5.1 requires COSmanager V4.2.5 or newer.


Schedules and Schedtime

When duty3G V5.1 is installed on a system with a version of COSMOS V3.2.X, some new framework facilities are added to support more generalised scheduling. These include the datelist and schedule tables, which supersede the schedtime table (used in COStask V4.0). When the schedule table is installed, any locally added entries are copied into the schedule table. However, it is important to note that the schedtime and schedule tables are maintained separately, and so changes to one table will not be reflected in the other.If you are running COSMOS V3.2.X, the schedule and datelist tables can only be maintained from the COStask Configuration window.It is possible to update the schedule table with any new entries added to the schedtime table by running the program upg_sched which is installed in the COSMOS Install directory. Note however that this will NOT detect changes to existing entries in schedtime.


Audit Trails and Logfiles

When duty3Gis installed, two new audit trails are created: duty_log and duty_compl. By default, these are created in the system spool area (usually /usr/spool or /var/spool).COStask is the primary audit trail, recording many actions that COStask performs:•Job Submission;•Start and end of job and task execution;•Most operator actions (cancel, hold etc.).Tasklog is used to hold all the logfiles created when a job or task executes. Depending on the amount of output produced by your jobs, this directory may become large, so it is important that audit trail cycling be configured correctly for your site to prevent these files from growing unbounded


New Features in this Release

Generalised Calendaring for Automatic Jobs

Duty3G V5.1 uses the new schedule and datelist tables which provide more features than the old schedtime table:


Notes Facility

You can now attach a text file of documentation to either a job or task. This text file can be view by the operator from the task monitor at any time, using the scroll facility. There is no facility provided to create notes files: you can simply use your favourite text editor (vi, emacs etc.). Notes files should be created in the local/notes directory.