This section describes the copy daemon bs2fsd.
The notational conventions which are used in the command syntax are explained in "Notational conventions".
The copy daemon bs2fsd transfers BS2000 files and elements of PLAM libraries from BS2000 to the corresponding area of the bs2fs container and vice versa.
A file or library element is transferred from BS2000 to the bs2fs container automatically when the first access to the file takes place in the bs2fs file system (first open); in the case of write access, transfer back to BS2000 takes place after editing in POSIX has been completed (last close).
If the file or library element has been opened for writing, it remains open in BS2000 from the start of transfer from BS2000 until its transfer back to BS2000 has been completed. It can therefore not be modified by other users while it is being edited in POSIX. This guarantees that the file has a consistent status.
By default 2 bs2fsd daemons are started when the bs2fs container is mounted. However, the system administrator has the option of starting further copy daemons when required (e.g. a large number of bs2fs file systems, a large number of files, large files) using the start_bs2fsd command.
The daemons run as POSIX background processes mainly in the TU under the TSOS user ID. After they have been started, they "sleep" until they are "woken up" by a request.
You can monitor the daemons by, for instance, entering the following POSIX command:
ps -ef | grep bs2fsd
In addition, you can use the start_bs2fsd command to determine how many copy daemons are running at the moment.
When the bs2fs container is unmounted, all copy daemons are terminated automatically.