# 14. Production Processing

The Data Processing Subsystem provides a batch processing environment to
support the generation of data products. It manages, queues, and
executes Data Processing Requests (DPR) on the processing resources at a
DAAC. A DPR can be defined as one processing job. Each DPR encapsulates
all of the information needed to execute this processing job. DPRs are
submitted from the Planning Subsystem, which in turn is triggered by the
arrival of data or internally through Planning itself. DPRs use Product
Generation Executives (PGEs) to perform processing. PGEs will result
from the integration and test of delivered science algorithms and also
user-specific methods in the subsystem. They will be encapsulated in the
ECS environment through the SDP Toolkit. The Data Processing subsystem
provides the Operational interfaces needed to monitor the execution of
science software PGEs.

Each procedure outlined will have an **Activity Checklist** table that
will provide an overview of the task to be completed. The outline of the
**Activity Checklist** is as follows:

Column one - ***Order*** shows the order in which tasks should be
accomplished.

Column two - ***Role*** lists the Role/Manager/Operator responsible for
performing the task.

Column three - ***Task*** provides a brief explanation of the task.

Column four - ***Section*** provides the *Procedure (P)* section number
or *Instruction (I)* section number where details for performing the
task can be found.

Column five - ***Complete?*** is used as a checklist to keep track of
which task steps have been completed.

The following Activity Checklist, Table 14.1-1, provides an overview of
production processing.

Table 14.1-1. Production Planning - Activity Checklist

+-----+-------------+-------------------------------+-------+---------+
| Or  | Role        | Task                          | Se    | Co      |
| der |             |                               | ction | mplete? |
+=====+=============+===============================+=======+=========+
| 1   | Production  | Configure AutoSys             | \(P\) |         |
|     | Monitor     |                               | 14.1  |         |
+-----+-------------+-------------------------------+-------+---------+
| 2   | Production  | Review Hardware Status        | \(P\) |         |
|     | Monitor     |                               | 14.2  |         |
+-----+-------------+-------------------------------+-------+---------+
| 3   | Production  | Review DPR Dependencies       | \(P\) |         |
|     | Monitor     |                               | 14.3  |         |
+-----+-------------+-------------------------------+-------+---------+
| 4   | Production  | Review DPR Production         | \(P\) |         |
|     | Monitor     | Timeline                      | 14.4  |         |
+-----+-------------+-------------------------------+-------+---------+
| 5   | Production  | Modify Job Priority           | \(P\) |         |
|     | Monitor     |                               | 14.5  |         |
+-----+-------------+-------------------------------+-------+---------+
| 6   | Production  | Review Alarms                 | \(P\) |         |
|     | Monitor     |                               | 14.6  |         |
+-----+-------------+-------------------------------+-------+---------+
| 7   | Production  | Review Job Activities         | \(P\) |         |
|     | Monitor     |                               | 14.7  |         |
+-----+-------------+-------------------------------+-------+---------+
| 8   | Production  | Modify Job Status             | \(P\) |         |
|     | Monitor     |                               | 14.8  |         |
+-----+-------------+-------------------------------+-------+---------+
| 9   | Production  | Display Activity Log          | \(P\) |         |
|     | Monitor     |                               | 14.9  |         |
+-----+-------------+-------------------------------+-------+---------+
| 10  | Production  | Display and Print Job         | \(P\) |         |
|     | Monitor     | Dependency Log                | 14.10 |         |
+-----+-------------+-------------------------------+-------+---------+
| 11  | Production  | Define Monitors/Browsers      | \(P\) |         |
|     | Monitor     |                               | 14.11 |         |
+-----+-------------+-------------------------------+-------+---------+
| 12  | Production  | Modify Database Maintenance   | \(P\) |         |
|     | Monitor     | Time Change                   | 14.12 |         |
+-----+-------------+-------------------------------+-------+---------+
| 13  | Production  | Generate Production Reports   | \(P\) |         |
|     | Monitor     |                               | 13.7  |         |
|     |             |                               | &     |         |
|     |             |                               |       |         |
|     |             |                               | \(P\) |         |
|     |             |                               | 14.13 |         |
+-----+-------------+-------------------------------+-------+---------+
| 14  | Production  | Time Synchronization          | \(P\) |         |
|     | Monitor     |                               | TBD   |         |
+-----+-------------+-------------------------------+-------+---------+

## 14.1 Configure AutoSys

The configure AutoSys process begins when the Production Monitor starts
AutoSys and changes Runtime Options or uses the vi editor to modify
configuration files.

The procedures in this section concern configuring AutoSys and hardware
groups.

### 14.1.1 AutoSys Runtime Options

The Runtime Options that may be defined by the Production Monitor
operator are:

Refresh Interval - The Refresh Interval is how often the View display
will be updated.

Ping Interval - The Ping Interval is defined by how often the
connectivity will be evaluated.

Hang Time - The Hang Time is the length of time jobs will continue to
display within a machine after they have completed running.

Inches/Hour- The Inches/Hour is how much information is displayed on the
screen. All values are initially set to default values by the AutoSys
system.

Table 14.1-2 lists the Runtime options available for HostScape,
TimeScape, and JobScape. Not all options are available for all graphical
user interfaces (GUI).

HostScape displays jobs on a machine-by-machine basis, indicating which
AutoSys server/client machines are up and active, and which jobs are
running or have recently run on each machine. This interface is used to
monitor hardware status in real-time.

TimeScape presents a Gantt-like view of a job processing from a temporal
(or time-related) point-of-view. This interface depicts all job types:
Command Jobs, Box Jobs, and File Watcher Jobs**.** It also depicts the
nesting of jobs within boxes and the duration of time it will take for
jobs to complete. This interface is used to monitor job flow in
real-time.

JobScape presents a Pert-like view of job processing from a logical (or
job dependency) point of view. This interface depicts all job types:
Command Jobs, Box Jobs, and File Watcher jobs. It also depicts the
nesting of jobs within boxes and the dependencies between jobs. This
interface can be used to monitor job flow in real-time.

Table 14.1-2. Runtime Options Table

  ------------- ----------------- -------------- ----------- --------------
  Interface     Refresh Interval  Hangtime       PING        Inches/Hour

  HostScape     **X**             **X**          **X**       

  TimeScape     **X**                                        **X**

  JobScape      **X**                                        
  ------------- ----------------- -------------- ----------- --------------

To configure AutoSys use the following procedures. Perform only those
steps applicable to the interface, as defined in Table 14.1-2.

**1** Set the display and application environment variables by entering

-   Display environment is entered: **setenv DISPLAY
    ###.###.###.##:0.0**

where ###.###.###.## is the IP address of the workstation being used.

-   Application home environment is entered: **setenv ECS_HOME
    /usr/ecs/**

**\-\-- THEN \-\--**

> Launch **AutoSys** by **double-clicking** on the **AutoSys** Icon
> located on the desktop.

-   The **AutoSys** GUI is displayed.

**\-\-- OR \-\--**

If the ECS desktop is not available, set the appropriate variables and
start **AutoSys** via the command line by entering:

cd **/usr/ecs/OPS*/*COTS/autotreeb/autouser**

**source autosys.csh.\<machine_name\>**

cd **/usr/ecs/OPS*/*CUSTOM/utilities/**

**EcDpPrAutosysStart \<*mode\> \<Application_ID\>***

\<MODE\> is current test (or ops) mode of operation.

-   The ***mode*** identifies your current operating mode

-   TS1 - Science Software Integration and Test (SSI&T)

-   TS2 - New Version Checkout

-   OPS - Normal Operations

```{=html}
<!-- -->
```
-   The ***application_id*** is a number from 1 to 5. Only one person at
    a time is permitted to run the application using a particular
    application_id. Consequently, there is a maximum limit of five (5)
    instances of the application running concurrently.

**2** **Single-click** on either **HostScape**, **TimeScape**, or
**JobScape**.

-   The desired **GUI** dialog box is displayed.

**3** Execute menu path: **Options** → **Edit Runtime Options**.

-   The **Runtime Options** dialog box is displayed.

**4** **Single-click** **Refresh Interval** **(Seconds)**, and enter a
value between **1** to **99999**.

-   Value is entered.

-   Default value is **30**

-   **Reloading Job Data** window reappears every **\##** seconds.

If Freeze Frame feature is enabled, changes will not take place until it
is disabled.

**6** **Single-click** **Ping Interval (Seconds)** and enter a value
between **1** to **99999.**

-   Value is entered.

-   Default value is **300**

-   99999 means no **ping** commands are issued.

If Freeze Frame feature is enabled, changes will not take place until it
is disabled.

**7** **Single-click** **Hang Time (Minutes)** and enter a value between
**1** to **99999**.

-   Value is entered.

-   Default value is **1**

If Freeze Frame feature is enabled, changes will not take place until it
is disabled.

**9** **Single-click** **Inches/Hr (inches)** and enter a value between
**1** to **\###**.

-   Value is entered.

-   Default value is **2**

If Freeze Frame feature is enabled, changes will not take place until is
disabled.

**9** **Single-click** **Apply**.

-   The Runtime Options are set.

**10** **Single-click** **OK**.

-   The dialog box closes.

### 14.1.2 Configure Hardware Groups

This section explains how to configure AutoSys hardware groups. The
default group is "All Machines." If the Production Monitor requires to
monitor a specific set of machines to be monitored, groups may be
defined.

To configure AutoSys hardware groups use the following procedures. (The
example for these procedures is HostScape.)

**1** Access the command shell.

-   The Command shell **\$** is displayed.

**2** Edit a file called **AUTOUSER/xpert.groups.\$AUTOSERV** using an
appropriate text editor..

**3** Enter "**groupname**: ***groupname***" and press **Return***.*

**4** Enter "***machine name***" and press **Return.**

> *(Repeat step 4 for each item in the group.)*
>
> *[Repeat steps 3 and 4 for additional groups]{.underline}.*

**5** Save the file.

> **Groupname: Modis**
>
> **Tabby**
>
> **Tomcat**
>
> **Groupname: Archive**
>
> **Sheltie**
>
> **Doberman**

Figure 14.1-1. AutoSys Hardware Group File Example

**6** Launch the **AutoSys** and **single-click HostScape**.

-   The **HostScape** GUI page is presented.

**7** Select **View** → **Select Machine Group.**

-   The **Machine Group Selection** dialog box is presented.

**8** Select ***machine group*** to be presented

-   The **Machine Group** is highlighted.

**9** **Single-click** **Apply** PushButton**.**

-   The selected **machine group** is applied.

**10** **Single-click** **OK** PushButton**.**

-   The **Machine Group Selection** dialog box is closed

-   The **HostScape** display should now show the selected group of
    machines**.**

## 14.2 Review Hardware Status

The review hardware status process begins when the Production Monitor
starts the AutoSys from the Production Monitor's desktop. Hardware
status is performed through the AutoSys HostScape GUI, which is used to
monitor hardware status in real-time.

### 14.2.1 Review Hardware Status

To review hardware status using AutoSys HostScape use the following
procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Single-click** on the **HostScape** PushButton.

-   The **HostScape** GUI page is presented.

-   View presented is **Normal** View.

**3** Review the Control Region (left side of display) to identify color
code for status of machines. This code will be displayed on the machine
box border in the **View Region**.

-   **MACHINE UP** (active) is Green.

-   **MACHINE DOWN** (inactive and cannot be reached) is Red.

-   Machine Inactive is Black**.** (Not shown in Control Region)

**4** Review machine type in **View Region**.

-   The ***machine name*** is displayed.

-   Server machines are in the first (top) row of the display.

-   Event Server name appears below list of jobs, if applicable.

-   Event Processor name appears below list of jobs, if applicable.

-   Client machines are in the subsequent rows of the display.

**5** Review machine boxes in the View Region to ascertain status of
individual machines.

-   The total number of jobs STARTING or RUNNING.

-   All jobs RUNNING are listed.

**6** Review the **Alarm** indicator/PushButtons of individual machines
in the View Region.

-   Red indicates an alarm has been generated.

-   Gray (default color) indicates normal operation.

If an Alarm is present, **single-clicking** alarm buttons will bring up
the Alarm Manager

**7** Review machine connection status in the View Region.

-   Solid black line indicates AutoSys can communicate with the client
    machine Internet daemon.

-   Solid red line indicates AutoSys cannot communicate with the client
    machine Internet daemon; however, the daemon does respond to
    **ping** commands.

-   Dashed red line indicates AutoSys cannot communicate with the client
    machine; machine is probably turned off.

**8** Exit **Hostscape.**

Select **File** → **Exit** from the pull-down menu then click on the
**OK** button to exit from **Hostscape**.

### 14.2.2 Hardware Status View Options

The View Options provide three methods to view the hardware status:

The Normal view (default) displays three rows of machines with job
activities.

The Global view displays seven rows of machines but not job activities.

The Zoom view displays one machine with great detail: Job name,
description, status, and commands.

The Performance Monitor operator may select the Global view to monitor
the entire system and in the case of a malfunction, use the Zoom view to
focus on the specific problem machine.

To view hardware status from HostScape use the following procedures:

**1** Select a machine by **single-clicking** on its ***name*** and
executing menu path: **View** → **Select View Level** → **Global View**.

-   The **Global** view is displayed.

-   Up to seven rows of machines are displayed.

-   No job information is displayed.

**2** Select a machine by **single-clicking** on its ***name*** and then
execute menu path: **View** → **Zoom in Machine**.

-   The **Zoom** view is displayed.

-   A table of **Job Name**, **Description**, **Status**, and
    **Commands** is displayed.

**3** Select **Dismiss**.

-   The **Global** view is displayed.

**4** Execute menu path: **View** → **Select View Level** → **Normal
view**.

-   The **Normal** view is displayed.

-   Up to three rows of machines are displayed.

-   Limited job information is displayed.

## 14.3 Review DPR Dependencies

The review DPR dependencies process begins when the Production Monitor
starts the AutoSys Jobscape from the Production Monitor's desktop. The
JobScape interface is used to monitor job flow in real-time.

To review DPR Dependencies from the JobScape mode use the following
procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Single-click** on the **JobScape** PushButton.

-   The **JobScape** GUI page is presented.

**3** Review the Control Region (left side of display) to identify
**True** or **False** Dependency Legend.

-   **True** (default **solid** arrow) indicates job dependencies have
    been met.

-   **False** (default **dashed** arrow) indicates job dependencies have
    **not** been met.

> Dependency arrows only indicate that a job dependency exists for a
> job. They do not define time-related starting conditions, nor do they
> describe the type of job dependency, such as success, failure, or
> running.

**4** Review the Job Display for status. Default colors are:

-   White indicates job status of **ACTIVATED**.

-   Blue indicates job status of **INACTIVE** or **ON-HOLD** or
    **ON-ICE**.

-   Yellow indicates job status of **QUE** **WAIT**.

-   Orange indicates job status of **RESTART**.

-   Forest Green indicates job status of **STARTING** or **RUNNING**.

-   Red indicates job status of **FAILURE** or **TERMINATED**.

-   Light Blue indicates job status of **SUCCESS**.

**5** Review the Job Display for job types:

-   **Rectangle** depicts **Box Jobs**.

-   **Ellipses** depicts **Command Jobs**.

-   **Hexagons** depicts **File Watcher Jobs**.

**6** Select a job by placing the **cursor** on a job and pressing the
**left** mouse button.

-   Border around selected job changes to **yellow**.

-   Job name appears in Current Job Name area of the Control Region.

**7** Review job descendants by placing the **cursor** on a job and
pressing the **right** mouse button.

-   **Descendants** popup menu appears.

-   Border around selected job changes to **yellow**.

-   Job name appears in Current Job Name area of the Control Region.

**8** Select **Show Children** on the **Descendants** popup menu.

-   Job's first level **Command, File Watcher,** and **Box Jobs**
    appear.

-   Repeat step 6 to change job selection.

**9** Select **Show All Descendants** on the **Descendants** popup menu.

-   Job's Command, File Watcher, and Box Jobs appear for all levels.

**10** Select **Hide All Descendants** on the **Descendants** popup
menu.

Default view is displayed.

All dependents are hidden.

**11** Exit **Jobscape.**

Select **File** → **Exit** from the pull-down menu then click on the
**OK** button to exit from **Jobscape**.

## 14.4 Review DPR Production Timeline

The review DPR Production Timeline process begins when the Production
Monitor starts AutoSys TimeScape from the Production Monitor's desktop.
The TimeScape interface is used to monitor job flow in real-time.

To review the DPR Production Timeline from TimeScape use the following
procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** If the ECS desktop is not available, start **AutoSys** via the
command line by entering:

**/usr/ecs/\<*mode\>/*CUSTOM/utilities/EcDpPrAutosysStart \<*mode\>
\<Application_ID\>***

**3** **Single-click** on the **TimeScape** button.

-   The **TimeScape** GUI page is presented.

-   Current time is displayed in red.

**4** Review **Actual/Projected** Legend in lower left of the **Control
Region** and compare to **View Region**.

-   **Projected** is a rectangular (blue filled) graphic, to show
    average job completion time.

-   **Actual** is a striped (white and blue) ribbon, to show how much of
    the job has completed.

-   If stripe is green, job is running.

-   If stripe is black, job has completed.

**5** Review job descendants by placing the **cursor** on a job and
pressing the **right** mouse button.

-   **Descendants** popup menu appears.

> An Asterisk (**\***) indicates that a Box Job's descendants have been
> hidden.

**6** Select **Show Children** on the **Descendants** popup menu.

-   Job's first level **Command, File Watcher,** and **Box Jobs**
    appear.

**7** Select **Show All Descendants** on the **Descendants** popup menu.

-   Job's **Command**, **File Watcher**, and **Box Jobs** appear with
    all levels.

**8** Select **Hide All Descendants** on the **Descendants** popup menu.

-   Default view is displayed.

**9** Exit **Timescape.**

Select **File** → **Exit** from the pull-down menu then click on the
**OK** button to exit from **Timescape**.

## 14.5 Modify Job Priority

The modify job priority begins when the Production Monitor starts
AutoSys from the Production Monitor's desktop.

Job Priority specifies the priority of the job, with 1 (one) being the
highest priority. Priorities have a \"Band\" associated with them; i.e.,
1-99 is band \"0\", 100 - 199 is band \"1\", etc. Higher band jobs
(lower numerically) completely block lower band jobs, preventing a
situation where a high-priority, resource intensive job cannot obtain
enough resources.

To configure AutoSys, use the following procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Single-click** on the Job Definition button.

-   The **Job Definition** GUI page is presented.

**3** Enter "**%**" in the Job Name field and click the **Search**
button below this field.

-   The **Selection List** GUI is displayed.

**4 Double-click** on a job for which the QUE priority value should be
updated.

-   The **Job Definition** screen is redisplayed with the job
    information filled in.

**5 Single-click** on the **Adv Features** button.

-   The Job Definition Advanced Features GUI page is presented.

**6** In the UNIX Command Information area, **single-click** and modify
the **Que Priority** to the desired value.

-   **Que Priority** value is updated.

CAUTION

> Do not modify other fields on the **Job Definition Advanced Features**
> GUI. ECS cannot disable these GUI features, because AutoSys/AutoXpert
> is a COTS product. Training and documentation will be provided to
> operations personnel, which will provide clear instructions concerning
> the intended use and which features to avoid.

**7** **Single-click** on the **Save&Dismiss** PushButton.

-   The **Job Definition** GUI page is presented. (The job definition is
    saved to the Autosys database.)

**8** **Single-click** on the **Exit** PushButton.

-   The **Job Definition** GUI page is presented.

**9** **Single-click** on the **Exit** PushButton.

-   The **Job Definition** GUI page is exited.

## 14.6 Review Alarms

The review alarms process begins when the Production Monitor starts
AutoSys Alarm Manager from the Production Monitor's desktop. The Alarm
Manager allows the Production Monitor to view alarms as they arrive,
provide a response, and change the alarm status. The Alarm Manager is
also configurable for the types of alarms that get displayed.

### 14.6.1 Review Alarms

To use AutoSys Alarm Manager to review alarms, use the following
procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Single-click** on the **Ops Console** Icon located on the
desktop.

-   The **Ops Console** GUI is displayed.

**3** **Single-click** on the **Alarm** PushButton.

-   The **Alarm Manager** GUI page is presented.

> Alarms are displayed in reverse order of occurrence; the newest alarm
> appears at the top of the list.

**4** **Single-click** on an alarm in the **Alarm List**.

-   Information for **Alarm Type**, **Job Name**, **Time**, **State**,
    **Comment** is displayed.

-   Alarm is displayed in detail in the **Currently Selected Alarm**
    region of the display.

**5** **Single-click** the **Response** edit box and enter
***response***, if desired.

-   Response is entered.

**6** Update **Alarm State** by **single-clicking** proper radio button
of **Open**, **Acknowledged**, or **Closed**.

-   Alarm State is updated.

**7** **Single-click Apply**.

-   Response is entered.

**8** **Repeat steps 4 - 7 to update/review multiple alarms**.

-   Alarms are updated/reviewed.

**9** **Single-click Ok**.

-   **Alarm Manager** GUI closes and the user is back to the **Autosys
    Job Activity Console**.

**10** Exit **Autosys Job Activity Console.**

-   Select **File** → **Exit**.

-   The user is prompted if they would like to exit the **Autosys Job
    Activity Console.**

**11 Single-click OK.**

-   The **Autosys Job Activity Console** quits.

### 14.6.2 Alarm Selection Configuration 

To configure the AutoSys Alarm Manager to control which alarms are
displayed, use the following procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Single-click** on the **Ops Console** Icon located on the
desktop.

-   The **Ops Console** GUI is displayed.

**3** **Single-click** on the **Alarm** PushButton.

-   The **Alarm Manager** GUI page is presented.

**4** Execute menu path: **View** → **Select Alarms\...**.

-   **Alarm Selection** GUI is displayed.

> Alarm Selection defaults are
>
> **All Types** for **Select by Type**,
>
> **Open** and **Acknowledge** for **Select by Stated**, and
>
> **All Times** for **Select by Time**.

**5** To select a single alarm, **single-click** on an alarm in the
**Select by Type** list or select **All Types**.

-   Alarm types are selected.

-   If **All Types**, button will turn yellow.

**6** To select multiple alarms: **press** **and** **hold** the
**Control** key while **single-clicking** alarms in the **Alarm List**.

-   Multiple alarms are selected.

**7** To **Select by State**, **single-click** on appropriate **Open**,
**Acknowledge**, **Closed**, or **All States** ToggleButtons.

-   Any or all buttons can be selected.

-   Button will turn yellow when selected.

**8** To **Select by Time**, enter **From Date (MM/DD/YY)** and press
**Tab,** or select **All Times**.

-   **MM/DD/YY** is entered.

-   If **All Times**, proceed to step 9.

**9** Enter **From Time (hh:mm),** and press **Tab**.

-   **hh:mm** is entered.

**10** Enter **To Date (MM/DD/YY),** and press **Tab**.

-   **MM/DD/YY** is entered.

**11** Enter **To Time (hh:mm),** and press **Tab**.

-   **hh:mm** is entered.

**12** Select **Apply**.

-   Selections are applied and the matching alarms are shown on the
    **Alarm Manager** display.

**13** Select **OK**.

-   **Alarm Selection** GUI is closed.

-   **Alarm Manager** GUI is displayed.

**14** Select **Options →** **Sound On**.

-   **Sound On** Toggle button appears yellow when sound is on.

**15** Exit **Alarm Manager.**

-   Select **Cancel** button.

-   **Alarm Manager** will quit.

## 14.7 Review Job Activities

The review Job Activities process begins when the Production Monitor
starts AutoSys from the Production Monitor's desktop. The Job Activity
Console is the primary interface that allows the operator to monitor all
jobs that are defined to AutoSys. The Job Selection GUI sets the
criteria for Job Status and Machine to display jobs.

### 14.7.1 Review Job Activities 

To review Job Activities using AutoSys, use the following procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Double-click** on the **Ops Console** PushButton.

-   The AutoSys Job Activity Console is presented.

**3** Review the **Job List** region.

-   **Job Name, Description, Status, Commands,** and **Machine** are
    displayed in a table.

**4** **Single-click** anywhere on a job row to display detailed
information.

-   Job details displayed in **Currently Selected Job** region.

**5** Review **Starting Conditions**.

-   Job **Starting Conditions** display.

-   **Atomic Condition, Current State,** and **T/F** are displayed.

> **Single-clicking** on a Starting Condition will update the Currently
> Selected Job to those "upstream" dependencies.

**6** Review **Report Area**. **Single-click** on **Summary**,
**Event**, or **None** in the **Reports** area to view different
reports.

-   **Summary**, **Event**, and **Job Reports** display as selected.

-   Select report button turns yellow.

**7** **Single-click** **Exit**.

-   **AutoSys JAC Exit** GUI appears.

**8** **Single-click** **OK**.

-   **AutoSys Job Activity Console** GUI is exited.

### 14.7.2 Review Job Selection Criteria

To review Job Selection Criteria use the following procedures.

**1** Execute menu path: **View** → **Select Jobs** from the menu bar on
the **Autosys Job Activity Console**.

-   The **Job Selection** view is displayed.

**Job Selection** defaults are **All Jobs** (Job Name) for **Select by
Name**

**All Statuses** for **Select by Status**

**All Machines** for **Select by Machine**

**Unsorted** for **Sort Order**.

**2** **Single-click** anywhere on a job row to display detailed
information.

-   Job details display in **Currently Selected Job** region.

**3** **Single-click** desired option in the **Select by Name** area,
and enter required name or select **All Jobs**.

-   Options are **Job Name, Box Name, or Box Levels or All Jobs**.

-   Selection button turns yellow.

**4 Single-click** desired status in the **Select by Status** area

-   Options are **Starting, Running, Success, Failure, Terminated,
    Restart, Que Wait, Activated, Inactive, On Hold,** and **On Ice**.

**5** **Single-click** desired machine in **Select by Machine** area or
select **All Machines**.

-   Machine is highlighted.

-   **All Machines** button turns yellow.

**6** **Single-click** desired Sort Order.

-   Options are **Start Time, End Time, Job Name, Job Status, Machine
    Name,** and **Unsorted**.

**7** **Single-click** **Apply** .

-   Selections are applied.

**8** **Single-click** **OK** .

-   **Job Activity Console** is displayed.

-   **Job List** displays in accordance with new selection criteria.

**9** **Single-click** **Exit**.

-   **AutoSys JAC Exit** GUI is displayed.

**10** **Single-click** **Ok**.

-   **Job Activity Console** GUI is closed.

## 14.8 Modify Job Status

The modify Job Status process begins when the Production Monitor starts
AutoSys from the Production Monitor's desktop.

To modify Job Status using **AutoSys Send Event** GUI, use the following
procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Double-click** on the **Ops Console** Icon.

-   The **AutoSys Job Activity Console** is presented.

**3** **Single-click Send Event** button in the **Actions** Region.

-   **Send Event** GUI displays.

> Send Event defaults are:
>
> **Start Job** for **Event Type**
>
> **Now** for **Time**
>
> **Normal** for **Send Priority**.

**4** **Single-click Event Type** to select desired status.

-   Options are **Start Job, Job On Hold, Job Off Hold, Comment, Stop
    Demon, Force Start Job, Job On Ice, Job Off Ice, Kill Job, Change
    Status, Change Priority, Set Global,** and **Set Signal**.

**5** **Verify Job Name**.

-   ***Job Name*** appears in field.

**6** **Enter** desired Date and Time, either **Now** or **Future**.
**Single-click Now** or **single-click Future** and enter **Date**
(mm/dd/yy ), **Time** (hh:mm), and **single-click A.M** or **P.M**.

-   **Now** for immediate execution.

-   **Future** for future time and date. (Current date and time are
    default values.)

**7** **Enter *comment.***

-   Free form field for text entry to associate with event.

**8** Review **AUTOSERV Instance** field**.**

-   Displays current Autosys server identifier.

**9** Review **Change Status** option menu**.** **Single-click** and
select from pop-up list desired status.

-   Options are: **Running**, **Success**, **Failure**, **Terminated**,
    **Starting**, and **Inactive**.

-   Can be changed only if **Change Status** was selected in the Event
    Type region.

**10** Review **Queue Priority** entry**.**

-   Can be changed only if **Change Priority** was selected in the
    **Event Type** region.

**11** Review **Send Priority** RadioBox**.**

-   Can be changed only if **Change Status** was selected in the **Event
    Type** region.

-   High priority is reserved for emergencies.

**12** **Single-click Execute**.

-   **Send Event** setting is set.

-   **Job Activity Console** is displayed.

-   To cancel an event that was previously scheduled *sometime in the
    future*:

-   In the **Event Type** region, to specify an event type, select on of
    the radio buttons.

-   Select the **Cancel Previously Sent Event** radio button.

-   In the **Job Name** field, enter the job name.

-   **Single-click** on the **Execute** button.

-   The event is cancelled.

## 14.9 Activity Log

The Activity Log process begins when the Production Monitor runs the
AutoSys AutoRep command. The AutoRep command reports information about a
Job, jobs within boxes, machines, and machine status. A sample Activity
Log is illustrated in Figure 14.9-1.

Job Name Last Start Last End Status Run Pri/Xit

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Nightly_Download 11/10 17:00 11/10 17:52 SUCCESS 170/1

Watch_4_file 11/10 17:00 11/10 17:00 SUCCESS 101/1

filter_data 11/10 17:00 11/10 17:00 SUCCESS 101/1

update_DBMS 11/10 17:00 11/10 17:00 SUCCESS 101/1

Figure 14.9-1. Sample Activity Log

To display and print the Activity Log use the following procedures:

**1** Desktop Access**\...**

Access will depend on System Configuration.

**2** Enter **/usr/ecs/\<*mode*\>/COTS/autosys/bin/autorep -J ALL** at
the UNIX prompt.

-   Activity Log will be displayed to the standard UNIX output.

-   Enter ***Job_Name*** in place of **ALL** for a specific job.

-   Enter **-M *machine_name*** for Machine Report.

-   Enter **-s** for summary report.

-   Enter **-d** for Detailed Report.

-   Enter **-q** for Query Report.

**3** Add **\| lpr** to the above line to print the document.

-   Activity Log will print.

## 14.10 Job Dependency Log

The Job Dependency Log process begins when the Production Monitor runs
the AutoSys Job Depends command. The job_depends command reports
information about the dependencies and conditions of a job. This command
can be used to determine the current state of a job, its job
dependencies, the dependencies and nested hierarchies (for boxes) as
specified in the job definition, and a forecast of what jobs will run
during a given period of time. A sample Job Dependency Log is
illustrated in Figure 14.10-1.

[Job Name]{.underline} [Status]{.underline} [Date Cond?]{.underline}
[Start Cond?]{.underline} [Dependent Jobs?]{.underline}

DPR## Activated No Yes No

Condition: (success(DPR\_##) and exit code(execute.DPR\_##)\<5)

[Atomic Condition]{.underline} [Current Status]{.underline}
[T/F]{.underline}

SUCCESS(SPR\_##) SUCCESS T

EXIT_CODE(execute.DPR\_##) SUCCESS F

Figure 14.10-1. Sample Job Dependency Log

To display and print the Job Dependency Log, use the following
procedures:

**1** Enter UNIX window.

**2** Enter **/usr/ecs/\<*mode*\>/COTS/autosys/bin/job_depends -c -J
*job_name*** at the UNIX prompt.

-   Job Dependency log will be displayed.

-   **-c** is used for current condition status.

-   **-d** is used for dependencies only.

-   **-t** is used for time dependencies.

-   **-J *job_name*** indicates the job on which to report. Use **ALL**
    for all jobs.

**3** Add **\| lpr** to the above line to print the document.

-   Job Dependency log will print.

## 14.11 Defining Monitors/Browser

The define monitors/reports process begins when the Production Monitor
starts the AutoSys Monitor/Browser from the Production Monitor's
desktop. The Monitor/ Browser screen contains fields representing all
the information you need to define a monitor or report. See Figure
14.11-1.

Alarm: STARTJOBFAIL Job: execute.DPR_15 06/14 19:18:18 Run #782:9

Exit Code = 0

Job: execute.DPR_15 FAILURE 06/14 19:20:20 Run \# 782

\<Have EXCEEDED the Max \# of times (10) to attempt a restart. Something
is wrong and needs to be investigated\>

Alarm: STARTJOBFAIL Job: execute.DPR_15 06/14 19:18:18 Run #782:9

Exit Code = -655

Figure 14.11-1. Sample Browser Screen

### 14.11.1 Defining Monitors/Browser

To define Monitors/Reports use the following procedures:

**1** Launch AutoSys - Refer to Step 1 of Section 14.1.1.

**2** **Single-click** on the **Monitor/Browser** PushButton.

-   The **Monitor/Browser** GUI page is presented.

**3** Enter ***name***, then press **Tab.**

Monitor/Browser defaults are:

**Monitor** for **Mode**

**ALL EVENTS** for **Types of Events**

**ALL Jobs** **for Job Selection Criteria**

**4** Select **Alarms** or **ALL EVENTS** for Type of Events by
**single-clicking** on the ToggleButton:

-   **Light** **Blue** indicates job status of **success**.

**5** Select desired Job Status Events by **single-clicking** on the
ToggleButton:

-   Desired Status Events are selected.

**6** Select desired Job Selection Criteria by **single-clicking** on
the ToggleButton:

-   Either **All Jobs**, **Box with its jobs**, or **Single Job** is
    selected.

-   If **Single Job** is selected, then enter the ***jobname*** in the
    **Job Name** field.

**7** Select desired **Monitor Option** by **single-clicking** on the
ToggleButton:

-   **Sound** or **Verification Required for Alarms** is selected.

**8** Select desired Browser Time Criteria by **single-clicking**
**Yes** or **No** for Current Run Time and/or **Events After Date/Time
(mm/dd/yy hh:mm)**:

-   Desired Job Selection Criteria is selected.

**9** **Single-click Mode** selection of **Monitor** or **Browser**.

-   If **Monitor**, settings are defined for a monitor.

-   If **Browser**, setting are defined for a report.

**10** **Single-click Save**.

-   Monitor definition is saved to the database.

> You must **Save** the configuration first before results are seen by
> selecting **Run MonBro**.

**11** **Single-click** **Run MonBro**.

### 14.11.2 Monitor/Browser Reports

To run a monitor or browser that has been created, use the following
procedures:

**1** Access the command shell.

-   The Command shell **\$** is displayed.

**2** Change directory to the AutoSys directory, **cd
/usr/ecs/\<*mode\>*/COTS/autosys/bin**

-   The Command shell **\$** is displayed.

**3** Report, type **monbro -N *name.***

-   Report is displayed.

> Refer to the AutoSys Manual for all options and displays for all
> **monbro** reports.
>
> The monitor or report (browser) must have be previously defined using
> the **Monitor/Browser** GUI.

## 14.12 Database Maintenance Time Change

Once a day, the Event Processor goes into an internal database
maintenance cycle. During this time, the Event Processor does not
process any events and waits for the maintenance activities to complete
before resuming normal operations. The time of day that this maintenance
cycle starts up is pre-set to 3:30 PM. If necessary to change the time
it runs, you should reset this time to one of minimal activity. The time
required for the Database Maintenance cycle is approximately one minute.

To modify the Database Maintenance Time use the following procedures:

**1** Access UNIX window.

**2** Enter **vi \$AUTOSYS/install/data/config.\$AUTOSERV.**

-   The configuration file is displayed.

**3** Find **DBMaintTime=15:30**. Enter the desired time in 24 hour
format.

-   New time is entered.

-   Save the file.

## 14.13 Production Reports[^1]

The Production Reports process begins with the Production Request Editor
GUI and opening the Report Generator GUI.

Report options are: Job Dependency Report

Processing Status Report

Processing Errors Report,

Actual Vs Plan Report,

Production Disk Availability Report.

Other reports can be generated from the Monitor/Browser GUI. AutoSys
also has the capability to generate Job Reports, Machine Reports, and
Reports on AutoSys Global Variables being used.

The following Activity Checklist, Table 14.13-1, provides an overview of
generating production reports.

Table 14.13-1. Production Reports - Activity Checklist

  ---------------------------------------------------------------------------
  Order   Role                Task                     Section    Complete?
  ------- ------------------- ------------------------ ---------- -----------
  1       Production Monitor  Job Dependency Report    \(P\) 13.7 

  2       Production Monitor  Processing Status Report \(P\) 13.7 

  3       Production Monitor  Processing Errors Report \(P\) 13.7 

  4       Production Monitor  Actual Vs Plan Report    \(P\) 13.7 

  5       Production Monitor  Production Disk          \(P\) 13.7 
                              Availability Report                 

  6       Production Monitor  Monitor/Browser Reports  \(P\)      
                                                       14.11.2    

  7       Production Monitor  AutoSys Reports          \(P\)      
                                                       14.13.1    
  ---------------------------------------------------------------------------

### 14.13.1 AutoSys Reports

Table 14.13-2 presents, in a condensed format, the steps required to
print AutoSys reports about: a job, a job within boxes, machines, and
machine status, along with reports on global variables being used. If
you are already familiar with the procedures, you may prefer to use this
quick-step table. If you are new to the system, or have not performed
this task recently, you should use the following detailed procedures:

**1** Access the command shell.

-   The Command shell **\$** is displayed.

**2** Change directory to the AutoSys directory, **cd
/usr/ecs/\<*mode\>*/COTS/autosys/bin**

-   The Command shell **\$** is displayed.

**3** Detailed Job Report, type **autorep -J *job_name* -d*.***

-   Detailed Job Report is displayed.

-   To specify all jobs, enter **ALL** for ***job_name.***

-   See **Note 1.**

**4** Summary Job Report, type **autorep -J *job_name* -s*.***

-   Summary Job Report is displayed.

-   To specify all jobs, enter **ALL** for ***job_name***

-   See **Note 1.**

**5** Machine Report, type **autorep -M *machine_name*.**

-   Machine Report is displayed, including Max Load, Current Load, and
    Factor.

-   To specify all machines, enter **ALL** for ***machine_name***

-   See **Note 1.**

**6** AutoSys Global Variables, type **autorep -G*.***

-   AutoSys system configuration parameters are displayed.

-   See **Note 1.**

**Note 1**: Refer to the AutoSys Manual for all options and displays for
all reports.

Table 14.13-2. AutoSys Reports - Quick-Step Procedures

  -------------------------------------------------------------------------
  Step    What to Enter or Select                   Action to Take
  ------- ----------------------------------------- -----------------------
  **1**   Access **UNIX command line \$**           **Return**

  **2**   Type cd /**TBD**                          **Return**

  **3**   Type **autorep -J *job_name* -d*.***      **Return**

  **4**   Type **autorep -J *job_name* -s*.***      **Return**

  **5**   Type **autorep -M *machine_name*.**       **Return**

  **6**   Type **autorep - G*.***                   **Return**
  -------------------------------------------------------------------------

This page intentionally left blank.

[^1]: Production Reports are not available in Version 2, Release 2.0 of
    the software.