This document covers the following topics:

• Monitor Start Network

• Day Start Network

• Common Start Network Considerations

• Cleanup in Batch Mode

---

Monitor Start Network

You can define a job network to be executed after each Monitor start and before the activation of any other job.

If a network with the name MON-START is defined under the owner SYSDBA, it is executed at Monitor start time.

Execution

The start network is intended to run exclusively before any other network. Therefore, the absolute condition MON-START-RUNNING (owner SYSDBA) is set at activation time.

The setting of this condition is automatically taken over by the first job of the start network. This job sets no conditions during End-of-Job checking and actions.

Day Start Network

You can define a job network to be executed at the start of each day and before the activation of any other job.

If a network with the name DAY-START is defined under the owner SYSDBA, it is executed at Monitor start time.

Day Start Execution

The start network is intended to run exclusively before any other network. Therefore, the absolute condition DAY-START-RUNNING (owner SYSDBA) is set at activation time.

The setting of this condition is automatically taken over by the first job of the start network. This job sets no conditions during End-of-Job checking and actions.

Common Start Network Considerations

• Exclusive Execution

• Use

The considerations in this section apply to the Monitor start network and the day start network.

Exclusive Execution

While a start network is running, a warning message is repeatedly written to the log.

During the execution of the start network, the following Monitor activities are blocked:

• Schedule extraction

• Activation (except start network)

• Cleanup

Use

Some possibilities for the use of the start network are:

• Preparation of symbol tables for other networks;

• Activation of other networks;

• Condition setting;

• Any Entire System Server functions.

Cleanup in Batch Mode

• Parameter for CLEAN

• Example for CLEAN

• Cleanup of Mailbox Messages to SYSDBA

• Parameter for MX-DEL1P

• Example for MX-DEL1P

In addition to an automatic cleanup, or alternatively, you can also do a cleanup of the active database in batch mode outside of the Entire Operations Monitor.

Use a Natural batch job with the following commands:

LOGON SYSEOR
CLEAN <function> <log-target> 
FIN

Parameter for CLEAN

Use	Name	Description
function	ALL CLEAN DEACT	Cleanup, deactivation, deletion of work files Cleanup only Deactivation, deletion of work files only
log-target	NOP SO ALL	The cleanup is logged in the Entire Operations Log. The cleanup is logged in the SYSOUT of the batch job. The start and end messages of the cleanup are also logged in the Entire Operations Log. The cleanup is both logged in the Entire Operations Log and the SYSOUT of the batch job.

The batch cleanup can take place with the Monitor running or not. It is recommended to do the cleanup at times of low monitor utilization.

Like the automatic cleanup the batch cleanup should be performed at least once a day. Several runs a day are possible. This may be useful to reduce the data amount of each cleanup run.

The Entire Operations retention periods also apply to batch cleanup.

Example for CLEAN

CLEAN ALL SO   complete cleanup, log after SYSOUT

Cleanup of Mailbox Messages to SYSDBA

The cleanup of mailbox messages to SYSDBA can be executed in batch mode. To do this, use a Natural batch job including the following commands:

LOGON SYSEOR
MX-DEL1P <yyyymmdd> <hhiiss>
FIN

Parameter for MX-DEL1P

Name	Description
yyyymmdd	Day up to which cleanup is to take place.
hhiiss	Time up to which cleanup is to take place.

Example for MX-DEL1P

MX-DEL1P 20020201 100000