Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Application program coding requirements for the CNM interface z/OS Communications Server: SNA Programming SC27-3674-00 |
|
For an application program to use the CNM interface, AUTH=CNM must be specified on its APPL definition statement. To receive unsolicited RUs, an application program must be authorized to use the CNM interface and be designated in the CNM routing table (with the name specified in the name field of the APPL definition statement). Refer to z/OS Communications Server: SNA Customization for more information about authorizing application programs to use the CNM interface and designating the application program name in the CNM routing table. If a VTAM® application program has been authorized to use the CNM interface, the program can gain access to the SSCP-LU session by specifying PARMS=(NIB=nib address) in its ACB. This NIB contains parameters describing the session to be established (the SSCP-LU session) just as an NIB does when it is used to establish an LU-LU session with OPNDST or OPNSEC. After OPEN completes processing for the ACB, the NIB contains the CID of the SSCP-LU session that was established. The application program uses a subset of the RPL-based macroinstructions (SEND, RECEIVE, RESETSR, EXECRPL, and CHECK) to communicate on the SSCP-LU session just as it uses these macroinstructions to communicate on LU-LU sessions. Because the SSCP-LU session uses FM profile 6, it uses only a very limited set of data-flow-control functions; for example, the SSCP sends no data-flow-control requests and sends and receives only single-request chains. Refer to SNA Formats for details about FM profile 6. Similarly, because you use TS profile 1 on the SSCP-LU session, you do not send or receive session-control requests. Thus, do not use SESSIONC. The NIB macroinstruction specified by PARMS=(NIB=nib address)
has the permissible values listed here. See NIB—Create a node initialization block for details.
RPL, SEND, RECEIVE, RESETSR, and EXECRPL macroinstructions
used to access the SSCP-LU session can have the following subset of
RPL operands specified. See the macroinstruction descriptions in Conventions and descriptions of VTAM macroinstructions for details.
1 FM profile 6 does
not allow any expedited data-flow-control requests to be sent to or
from the SSCP.
|
Copyright IBM Corporation 1990, 2014
|