24.12.2013 Views

TOPS-10 Monitor Calls Manual Volume 2 AA-K039D ... - Trailing-Edge

TOPS-10 Monitor Calls Manual Volume 2 AA-K039D ... - Trailing-Edge

TOPS-10 Monitor Calls Manual Volume 2 AA-K039D ... - Trailing-Edge

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

FILE DAEMON<br />

When a File Daemon is running, the monitor calls it every time someone<br />

tries to access a file or a directory that has a 4, 57 6, or 7 code in<br />

the owner's protection code field and the access fails due to a<br />

protection error. So that the monitor knows there is a File Daemon,<br />

the following must occur:<br />

1. The feature test switch F%FDAE must be set to -1,<br />

the condition.<br />

to enable<br />

2. The program that will be the File Daemon must be privileged<br />

(that is, it must be running under [1,2] or running with the<br />

JACCT bit set).<br />

3. This program must send an IPCF request to [SYSTEM] IPCC (code<br />

6, .IPCSC) requesting a special PID.<br />

4. This program must then send a request to [SYSTEM] IPCC<br />

specifying code 24 (.IPCWP). This code requests that the<br />

File Daemon's PID be entered in the Special PID table.<br />

After each request to [SYSTEM] IPCC, the File Daemon receives<br />

verification that the function occurred. After the verification<br />

resulting from the File Daemon specifying code 24, the monitor sends<br />

an IPCF packet to the File Daemon each time that a protection failure<br />

occurs on a file or a directory.<br />

The message portion of the IPCF packet that the monitor sends<br />

to the<br />

File Daemon when a protection failure occurs has the following format:<br />

+---------------------------------------------------------------------+<br />

Type of access I Code<br />

File structure name<br />

File name<br />

File name extension<br />

Project number<br />

Programmer number<br />

Sub-file directory 1 or 0<br />

Sub-file directory 2 or 0<br />

Sub-file directory 3 or 0<br />

Sub-file directory 4 or 0<br />

Sub-file directory 5 or 0<br />

+---------------------------------------_._----------------------------+<br />

In this data block, the type of access is the type of access being<br />

attempted to the file. The Access Type Codes are listed in Table C-2.<br />

And code is a File Daemon Code, which are listed in Table C-3.<br />

The remaining words in the IPCF packet message are the full file<br />

specification for the file being accessed.<br />

B-<strong>10</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!