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


Requirements

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

Table 1 identifies the requirements for invoking the NMI requests.

Table 1. Requirements to invoke the NMI requests
  Requirements
Minimum authorization Authorization depends on the request that is invoked:
RCCOpen
The user ID of the caller must be permitted to the SAF profile for this request.
RCCSetFilters
The user ID of the caller must be permitted to the SAF resource profile for the trace type for which filter structures have been specified as input to the request. In addition to this requirement, the address space, task, and user ID of the caller must match those that were in effect when the RCCOpen request was invoked.
RCCStart
The address space, task, and user ID of the caller must match those that were in effect when the RCCOpen request was invoked.
RCCGetRecords
The address space and user ID of the caller must match those that were in effect when the RCCOpen request was invoked.
RCCStop
The address space, task, and user ID of the caller must match those that were in effect when the RCCOpen request was invoked.
RCCClose
The address space, task, and user ID of the caller must match those that were in effect when the RCCOpen request was invoked.
Dispatchable unit mode Task
Cross memory mode PASN=SASN=HASN
AMODE 31-bit or 64-bit
ASC mode Primary
Interrupt status Enabled for I/O and external interrupts
Locks Not applicable
Control parameters Must be in an addressable area in the primary address space and must be accessible using the execution key of the caller

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014