Initialization problems
Before you begin, if the RSVP Agent does not complete initialization, run it with LogLevel set to 511 and check the log file for error conditions.
Common problems are listed in Table 1:
| Problem | Cause or action |
|---|---|
| RSVP Agent not authorized to security product | The RSVP Agent must be authorized to a security product profile. See z/OS Communications Server: IP Configuration Guide for details on setting up the proper authorization. |
| Unable to read configuration file | Is the correct configuration file specified? See z/OS Communications Server: IP Configuration Guide for the search order used to locate the configuration file. Does the file exist? Are the permission bits correctly set for a z/OS® UNIX file system file? |
| Unable to associate with the TCP/IP stack | Is the associated TCP/IP stack started? The RSVP Agent uses the TCP/IP image name specified in the configuration file, or uses the standard resolver search order, to locate the name of the TCP/IP stack. The log file indicates the stack name being used. |
| Unable to initialize interfaces | The RSVP Agent needs to initialize
each interface for which it is configured. A pair of "mailboxes"
are created for each interface. Check for error messages while creating
the "rsvp" and "rsvp-udp" mailboxes for each interface. An error
received while trying to join a multicast group on an interface that
is not multicast capable is expected, and looks like: |