Named pipe as file event receiver
2003-10-13 10:53:42
We are looking into the possibility of migrating our OS/390 TSM
server to mainframe Linux. One of the issues we are looking into
is management facilities. Our current inclination is to define a
named pipe as a file event receiver and have a Perl script read
from the named pipe and respond to various messages. This appears
to have two advantages over running dsmadmc with the -console
option and piping its output to a script. First, it eliminates the
need to rejoin multi-line messages and figure out when the last
line of each message has arrived. Second, the named pipe eliminates
some inter-process synchronization issues. A dsmadmc process will
not start when the TSM server is down or in the early stages of
initialization. Has anyone used a named pipe as a file event
receiver in a Unix or Linux environment?
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Named pipe as file event receiver,
Thomas Denier <=
|
|
|