Tables
- Example of channel names
- Three ways of using the remote queue definition object
- Reply-to queue alias
- Queue name resolution at queue manager QMA
- Queue name resolution at queue manager QMB
- Reply-to queue name translation at queue manager QMA
- Channel attributes for the channel types
- Negotiated HBINT value and the corresponding KAINT value
- Functions available in Windows systems and UNIX(R) systems
- Channel programs for Windows and UNIX systems
- Settings on the local Windows system for a remote queue manager platform
- Default outstanding connection requests on Windows
- Configuration worksheet for IBM(R) Communications Server for Windows systems
- Configuration worksheet for WebSphere MQ for Windows
- Default outstanding connection requests
- Settings on the local UNIX system for a remote queue manager platform
- Configuration worksheet for Communications Server for AIX(R)
- Configuration worksheet for WebSphere MQ for AIX
- Configuration worksheet for HP SNAplus2
- Configuration worksheet for WebSphere MQ for HP-UX
- Configuration worksheet for SNAP-IX
- Configuration worksheet for WebSphere MQ for Solaris
- Configuration worksheet for Communications Server for Linux
- Configuration worksheet for WebSphere MQ for Linux
- Channel tasks
- Settings on the local z/OS system for a remote queue manager platform
- Configuration worksheet for z/OS using LU 6.2
- Configuration worksheet for WebSphere MQ for z/OS
- Configuration worksheet for z/OS using LU 6.2
- Configuration worksheet for WebSphere MQ for z/OS using queue-sharing groups
- Channel attribute fields per message channel type
- Program and transaction names
- Channel states on i5/OS
- Settings on the local i5/OS system for a remote queue manager platform
- Configuration worksheet for SNA on an i5/OS system
- Configuration worksheet for WebSphere MQ for iSeries
- Channel exits available for each channel type
- Identifying API calls