z/OS Communications Server: IP Programmer's Guide and Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Running PAPI applications

z/OS Communications Server: IP Programmer's Guide and Reference
SC27-3659-02

At execution time, the PAPI application must have access to the PAPI DLL (papi.dll), which is available in the /usr/lib directory. Ensure that the LIBPATH environment variable includes this directory when running the application. The PAPI application must either run with superuser authority to use PAPI, or must have security product authority in the SERVAUTH class. These security product profiles can be defined by TCP/IP stack (TcpImage) and policy type (only ptype = QOS is applicable). Wildcarding of profile names is allowed. The security product profiles take the following form:

EZB.PAGENT.<sysname>.<TcpImage>.<ptype> where:
  • sysname - System name defined in sysplex
  • TcpImage - TCP name for the requested policy information
  • ptype - Policy Type that is being requested (QOS)
Note: Wildcarding is allowed on segments of the profile name.

See the EZARACF sample in SEZAINST for sample commands needed to create the profile name and permit users access to it.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014