The following might be of interest for all z/VSE customers that still use OSA-Express configured as CHPID type OSE in
non-Queued Direct Input/Output (non-QDIO) operating mode.
IBM would like to understand current client usage of native SNA (through OSE channels) on IBM Z, and what plans, if any, clients have in place to migrate to an alternative. If your enterprise is currently using OSA-Express in OSE mode (for SNA or TCP/IP) IBM would like to understand your plans. A survey has been provided to help IBM understand your current and future needs around this technology.
Based on the results of this survey IBM will evaluate the need for investment in alternative solutions or services to aid you in your migration.
You can read more about the survey in the blog post
IBM Z OSA-Express OSE CHPID Type Usage Survey. There you also find the link to the actual survey. The survey will be available until 6/30/2020.
For reference I have provided some more information below on how OSA-Express devices with CHPID type OSE are defined in z/VSE as well as how they are configured and can be identified/queried when using either of the available TCP/IP stacks in z/VSE.
In z/VSE OSA-Express devices with CHPID type OSE need to be defined in the IPL procedure using an ADD command. Following is a sample ADD command for a OSA-Express device tuple with CHPID type OSE, which also maps the physical device numbers B500 and B501 to the VSE device numbers B50 and B51:
ADD B500:B501 AS B50:B51,OSA
For further details please see the
z/VSE System Control Statements manual, chapter
Initial Program Load, section
ADD.
TCP/IP for z/VSE
In TCP/IP for z/VSE OSA-Express devices with CHPID type OSE are configured as 3172-compatible LAN Channel Station (LCS) communications controller using the TYPE=LCS parameter in the DEFINE LINK command. Possible synonyms for LCS in the TYPE parameter are OSA, OSA2, and 3172. Following are sample DEFINE LINK and DEFINE ADAPTER commands for a OSA-Express device tuple with CHPID type OSE:
DEFINE LINK,ID=OSELINK,TYPE=LCS,DEV=(B50,B51)
DEFINE ADAPTER,LINKID=OSELINK,NUMBER=0,TYPE=ETHERNET,MTU=1500
You can query for OSA-Express devices with CHPID type OSE using the QUERY LINKS command. OSA-Express devices with CHPID type OSE are reported as "Type: 3172". Following is a sample QUERY LINKS output containing one OSA-Express device tuple with CHPID type OSE:
MSG TCPIP01,DATA=QUERY LINKS
AR 0015 1I40I READY
F6 0135 IPN253I << TCP/IP LINKS >>
F6 0135 IPN437I ID: OSELINK Type: 3172 Dev: (0B50,0B51)
F6 0135 IPN350I Current Status: Active
F6 0135 IPN440I ID: OSELINK Type: 802.3 Adapter: 0
F6 0135 IPN438I MTU: 1500 IP Address: 192.168.1.1
F6 0135 IPN441I MAC address: AC:62:0D:09:03:AC
F6 0135 IPN350I Current Status: Active
F6 0135 IPN437I ID: *Internal Type: *Int Dev: (0000,0000)
F6 0135 IPN438I MTU: 32767 IP Address: 127.0.0.1
F6 0135 IPN350I Current Status: Active
For further details on the DEFINE LINK, DEFINE ADAPTER, and QUERY LINKS commands please see the TCP/IP for VSE Command Reference manual. It is available as PDF from the
z/VSE PDF Library TCP/IP section.
IPv6/VSE IPv4
In IPv6/VSE IPv4 OSA-Express devices with CHPID type OSE are configured as OSA in the DEVICE command. Note that while configuring them as LCS also seems to work at a first glance this is not recommended, as it does not provide the full error recovery of OSA. Following are sample DEVICE and LINK commands for a OSA-Express device tuple with CHPID type OSE:
DEVICE OSAB50 OSA B50 ETHERNET
LINK OSAB50 1 192.168.1.1 255.255.255.0 1500
You can identify OSA-Express devices with CHPID type OSE in the BSTTINET statup output. OSA-Express devices with CHPID type OSE are reported as "DEVOSA" in message BSTT600I and "TYPE OSA" in message BSTT605I. Note that they could also be reported as "DEVLCS" with "TYPE LCS", if they were erroneously configured as LCS, although this is not recommended (see above). Following is a sample BSTTINIT startup output excerpt containing one OSA-Express device tuple with CHPID type OSE:
...
BSTT613I OSEB50 Interface 1 IP address 192.168.1.1
BSTT004I CB=IPBH A=00994000 L=00011000
BSTT600I 13 INITIATED DEVOSA Build254 07/24/13 09.36
BSTT605I 13 DEVICE 01 OSEB50 TYPE OSA UNIT 0B50
...
For further details on the DEVICE and LINK commands please see the IPv6/VSE IPv4 Installation Guide manual. It is available as PDF from the
z/VSE PDF Library IPv6/VSE section.
VTAM for VSE/ESA
You can confirm that you are using OSA-Express devices with CHPID type OSE for SNA Ethernet support in VTAM for VSE/ESA in the DISPLAY ID command output for XCA mayor nodes.
- Display the major nodes and look for those reported as type "XCA":
D NET,MAJNODES
- Display information about each mayor node of type XCA and look for those that have a port that is reported as "MEDIUM=CSMA/CD" (Ethernet):
D NET,ID=<majornodename>,SCOPE=ALL
For further details on the DISPLAY MAJNODES and DISPLAY ID commands please see the VTAM for VSE/ESA Operation manual. It is available as PDF from the
z/VSE PDF Library VTAM section.
I greatly appreciate your feedback to this blog post either in the comments or via the
z/VSE contact form.
Disclaimer: My posts and opinions are my own.