March Products 204 - Manual (Page 39)

——————————————————————————————————————————
Invocation Techniques for Background Monitoring
——————————————————————————————————————————
——————
CHAPTER 11
Invocation Techniques for Background
Monitoring
SirFile's background monitor runs as a special user in the SIRFILE APSY; this performs
the periodic refresh operation. Messages to users and the audit trail are only sent
during a periodic refresh (that is, by the background task).
Any user ID can be the background monitor, and any SirFile user can initiate the
background task. The most useful way to run the background monitor is in one of the
sdaemon IODEVs set up in the online. If you are going to run the background file
monitor in an sdaemon, you should allocate an extra one explicitly for this task. Failing
to allocate an extra sdaemon can slow down other jobs initiated from Sirius products
which require sdaemon servicing.
When the background monitoring task is sent to an sdaemon, the task appears as the
sdaemon thread number and the user ID of the submitting user. The sdaemon sits in a
WAIT state until the specified number of minutes has passed, then it wakes up and runs
a SirFile database refresh, sends warnings as appropriate, then returns to a “sleep”
state. The background task may be BUMPed the same as any user. To change the
time parameter for the background task, it should be bumped and resubmitted.
PF5 from the Background Monitor specification screen (see
“Background Monitor
Specification Screen” on page 31 ) will run the monitoring task in an sdaemon; it can also
be initiated via one of the following commands:
SIRFILE BACKGROUND interval
This command, typed at command level or inserted in the USER0 stream,
initiates the background task under an sdaemon. Interval specifies the
number of minutes the background task should sleep between refresh
operations; it is a required value and must be between 1 and 1440 (24
hours).
If no sdaemon is available or if the background task is already running, the
submitting user is warned, and the request is ignored.
SIRFILE SDAEMON interval
This command, typed at command level, causes the session to become the
background task. Interval specifies the number of minutes the background
task should sleep between refresh operations; it is a required value and must
be between 1 and 1440 (24 hours).
The command may be placed in a BATCH2 or IODEV3 input stream, or it
may be typed at command level from any terminal. Typing this command on
——————————————————————————————————————————
SirFile User's Guide 33