Required TCP/IP profile statements

For a detailed description of the statements mentioned here, see z/OS Communications Server: IP Configuration Reference. The following TCP/IP profile statements must be updated for OSA management support:

SACONFIG
On the SACONFIG statement, OSA Management support must be enabled by specifying OSAENABLED. Omission of OSAENABLED when TCP/IP is started will result in no OSA management support. The SACONFIG statement controls the operation of the subagent that runs in a TCP/IP address space as a separate task.

The OSASF parameter specifies which port IOASNMP should use to Listen for connections from subagents to OSA/SF. For an explanation of the usage of this parameter when starting multiple TCP/IP instances, see Subagent connection to OSA/SF when there are multiple TCP/IP instances. It is recommended that the OSASF port be reserved by also specifying it on a PORT statement.
For example:
```
 SACONFIG OSAENABLED OSASF 721
```
PORT
Prereserve the port to be used in communication with OSA/SF.
For example:
```
 PORT
    721  TCP IOASNMP ; OSA/SF TCP/IP Communications
```
In this example, because IOASNMP runs as a z/OS® UNIX application, the port could have been reserved for z/OS UNIX. Review the /etc/services file to ensure that there are no port conflicts.
DEVICE and LINK
Provide ATM DEVICE and LINK statements for any OSA ATM adapter for which you want SNMP ATM management data. For example:
```
DEVICE osaName ATM PORTNAME portname 
LINK linkName ATM osaName
```
Provide DEVICE and LINK statements for any OSA-Express Ethernet adapter for which you want SNMP Ethernet management data. For example:
```
DEVICE portname MPCIPA NONROUTER 
LINK linkName IPAQENET portname
```