RSVP can be started from the z/OS® shell
or as a started task.
The RSVP agent uses the following search order to locate the configuration
file (highest priority is listed first):
When starting from the shell, note that the RSVP executable file
is in the /usr/lpp/tcpip/sbin directory. There is also a link from
the /usr/sbin directory. Make sure your path statement (in the profile)
contains either the /usr/sbin or /usr/lpp/tcpip/sbin directory.
Use the S RSVPD command on an MVS console
or SDSF to start RSVP as a started task. A sample procedure is shipped
in member EZARSVPP in SEZAINST.
The /tmp/rsvpd.pid.tcpname is
a temporary RSVP daemon pid file that the RSVP daemon creates. This
file contains the process ID of the current invocation of the RSVP
daemon.
Restrictions: - If /tmp/rsvpd.pid.tcpname is a symbolic link, it must have
an owning UID or GID that matches the EUID or EGID that is assigned
to the RSVP daemon.
- If /tmp/rsvpd.pid.tcpname is a hard link or the target
of a hard link, users that are outside the owner or group of
the directory in which /tmp/rsvpd.pid.tcpname is stored
cannot have write access to the directory. Additionally, write access
to /tmp/rsvpd.pid.tcpname must be limited to the owning
UID or group, for example, --w--w----permissions.
RSVP can be stopped using the cancel command (C RSVPD) or using
the kill command in the z/OS shell.
The following kill command with the TERM signal will enable RSVP
to clean up resources properly before terminating itself:
kill -s TERM pid
where
pid is
the RSVP process ID.
The RSVP process ID can be obtained using the following z/OS UNIX command:
ps -A
It can also be obtained from the /tmp/rsvpd.pid.tcpname file. See
z/OS Communications Server: IP Configuration
Reference for more information.