When source VIPA is in effect, you can control which static VIPA is used for your IPv4 dynamic XCF interfaces by using the new SOURCEVIPAINTERFACE parameter on IPCONFIG DYNAMICXCF in z/OS V2R1. This designation removes the need to manage the order of the VIPAs in the HOME list. For the syntax of this new parameter, see the V2R1 IP Configuration Reference.
z/OS Communications Server
SamReynolds 270004DVAN 454 Visits
SamReynolds 270004DVAN 623 Visits
If your TCP/IP profile contains DEVICE/LINK/HOME statements for HiperSockets and static VIPA and you want to migrate these to the preferred (and much simpler) IPv4 INTERFACE statement, try this tip on z/OS V2R1: Take a dump of your TCP/IP stack. Use IPCS against the dump and issue the command TCPIPCS PROFILE(CONVERT). The resulting output will represent these IPv4 definitions as INTERFACE statements (and also show you what the updated HOME statement would look like.). You can then review this output to assist in modifying your TCP/IP profile. For more details on TCPIPCS PROFILE(CONVERT), see the V2R1 IP Diagnosis Guide.
SamReynolds 270004DVAN 527 Visits
One of the things that was easy to do with the older Bookshelf (BookManager) publications was search within a specific z/OS component like Communications Server. There is also a way to accomplish this with the z/OS V2R1 Information Center available at: http://pic.dhe.ibm.com/infocenter/zos/v2r1/index.jsp
Here are the steps to create a search scope of only the z/OS Communications Server books:
1. Access the search area and select Scope.
2. Select New.
3. Name your scope and select the z/OS Communications Server library. Optionally, select any additional criteria. Press OK.
Now when you click on Scope, you will see the following:
You can establish similar "book shelves" for other product publications you want to search, perhaps UNIX or LE. You can also create more granular scopes for just one book, such as this one:
Happy searching and reading!
Are you thinking about enabling FIPS140 mode for your AT-TLS connections? If so, check out the new techdoc entitled "Setting up AT-TLS for FIPS 140 mode." This techdoc provides one-stop shopping regarding the components you'll need to configure (and in which order) as well as verification steps along the way.
SamReynolds 270004DVAN 395 Visits
z/OS V2R1 is the last release which will support the GATEWAY statement. To migrate your static routing definitions to the BEGINROUTES block, try this tip: Take a dump of your TCP/IP stack. Use IPCS against the dump and issue the command TCPIPCS PROFILE(CONVERT). The resulting output will represent your GATEWAY definitions in BEGINROUTES format. You can then review this output to assist in modifying your TCP/IP profile. For more details on TCPIPCS PROFILE(CONVERT), see the IP Diagnosis Guide.
SamReynolds 270004DVAN 365 Visits
z/OS V2R1 supports IPv4 INTERFACE definitions for HiperSockets and Static VIPA in addition to the prior support for OSA-Express QDIO. The IPv4 INTERFACE statement combines the function of DEVICE/LINK/HOME into a single statement. This simplifies your stack configuration and also improves the usability of dynamically adding or removing these interfaces from your TCP/IP profile (which can be cumbersome when the HOME statement is involved). If you use the source VIPA function, the INTERFACE statement makes it much easier to designate which VIPA to use for the source IP address (without needing to manage the order of VIPAs in the HOME list). For the syntax of these statements, see the V2R1 IP Configuration Reference.
SamReynolds 270004DVAN 1,014 Visits
On June 26th, the z/OS Communications Server team held a Reddit AMA session that covered a variety of CS-related topics. Below is an edited summary of most of the discussion points. For each question, you can see the response from our CS team (preceded by "CS:"), as well as any follow-on questions or comments from the Reddit participants (preceded by "R:").
If you wish to read through the complete Reddit AMA transcript, it is available at:
Thanks to all who participated in this session! We think it was a very interesting experience and are going to strongly consider doing similar sessions in the future. Stay tuned to this blog, our Facebook page, and/or our Twitter feed for announcements of future sessions.
Summary of questions and responses for the June 26th Reddit AMA:
1) Where do you see SNA 10 years from now?
2) I been with a company for 17 years and have heard repeatedly the mainframe is dead. Why are we even commenting on this?
3) How do you make your IP stack perform faster than say the stacks on HP-UX or your sister OS, AIX?
4) Sysplex Distributor, what is it and why should it be implemented?
Regards, Big Retail Mainframer
5) What part does your development and support groups play when it comes to "Cloud" computing on the platform that you support? Specifically: 1) Automatic provisioning of resources 2) Browser access to processes like those used for interactive computing 3) True PaaS (Platform as a Service) for web based REST requests More to follow.........
6) When do you think IPv4 will become obsolete (if ever) and IPv6 take over and every device in the world, including appliances have an IPv6 address?
7) I missed the education conference yesterday detailing the new CS features in 2.1. Care to recap?
8) Hipersockets - I don't understand how hipersockets can be deployed if you are have the means to move application to different systems. If I understand hipersockets correctly its creating a virtual lan on a system and then giving ever lpar on that system an ip address. Then an application would have to use that virtual lan ip address to connect to another application if that appliation is bind to 0.0.0.0. If the application that we now change to point to the virtual lan ip address moves to a different system how is it going to be able to use the hipersocket ip address to connect now?
The Summer 2013 SHARE Conference is now in the history books! Five speakers from the z/OS Communications Server organization presented 16 sessions on various topics, with a significant focus on the just-announced z/OS V2R1 release. The V2R1 focus included an overview of z/OS V2R1 Communications Server, a detailed review of the new Shared Memory Communications for RDMA (SMC-R) capability, a V2R1 performance update, and a look at the newly-rewritten IBM Configuration Assistant for z/OS CS. Other topics discussed included Enterprise Extender, sysplex technologies, z/OS mail, OSA, and network security. Attendance at our sessions (and across the board at SHARE in Boston) was fantastic, and we would like to thank all of you who attended our sessions for the great feedback and dialogue.
Congratulations to Gus Kassimis for receiving a best session award for the session "Sysplex Networking Technologies and Considerations" that he presented at the Winter 2013 SHARE conference in San Francisco.
For those that couldn't be at the conference this week, I will remind you that you can download most of the charts for the topics we presented by going to the following link:
I especially recommend downloading and looking over the charts for the z/OS V2R1 CS Technical Update, and the sessions on SMC-R. Here are direct links for those downloads:
Please plan to join us for the Winter 2014 SHARE Conference in Anaheim, California, March 9-14, 2014.
The Summer 2014 SHARE Conference was a great educational event and continued celebration of the 50th anniversary of the mainframe! Six speakers from the Enterprise Networking Solutions organization presented 12 sessions on z/OS Communications Server and 4 on ISPF, and also participated in 3 z/OSMF hands-on labs. As with Winter SHARE, there continued to be a focus on z/OS V2R1, including an overview of z/OS V2R1 Communications Server, a detailed review of the Shared Memory Communications for RDMA (SMC-R) capability, and a V2R1 performance update. Other topics discussed included Enterprise Extender, sysplex technologies, network security, z/OS mail strategy, and z/OS CS hints and tips. We also had our first zNextGen session with our "Introduction to z/OS Communications Server." Attendance at our sessions (and across the board at SHARE in Pittsburgh) was very good, and we would like to thank all of you who attended our sessions for the great feedback and dialogue.
SHARE loves user experience sessions, and we were fortunate to have a z/OS CS-centric user experience session at this conference: Jim Darby of Nordstrom and Tom Cosenza of IBM Lab Services presented their experience with implementing IPSec on z/OS. Thanks to both of these gentlemen for their presentation!
For those that couldn't be at the conference last week, I will remind you that you can download most of the charts for the topics we presented by going to the following link:
Please plan to join us for the Winter 2015 SHARE Conference in Seattle, Washington, March 1 - 6, 2015.
SamReynolds 270004DVAN 438 Visits
The QDIO Accelerator function provides accelerated forwarding of packets (including Sysplex Distributor packets routed to a target stack) which come inbound over OSA-Express QDIO or HiperSockets and go outbound over OSA-Express QDIO or HiperSockets. This function occurs at the device driver layer such that the forwarding stack never processes the forwarded packets. In z/OS V2R1, you can now enable this function even if IP Security is enabled as long as the IP filter rules on your forwarding stack permit all routed traffic and do not perform logging of routed traffic. For more details, see the section titled "QDIO Accelerator and IP Security" in the V2R1 IP Configuration Guide.
SamReynolds 270004DVAN 549 Visits
On October 9th, z/OS Communications Server held a Twitter chat with a focus on z/OS V2R1 CS features. Below is a transcript of that chat (with minor edits for clarification).
Welcome to our Twitter chat on z/OS V2R1 CS! Tweet your V2R1 CS questions with the hashtag #zoscs21
Q1: Is the default for SOMAXCONN sufficient for 250,000 Telnet TN3270E sessions? #zoscs21
A1: In V2R1, we've raised the SOMAXCONN default from 10 to 1024. That should be sufficient for that TN3270 workload. #zoscs21
V2R1 Fact: V2R1 introduces support for RDMA, with up to an 80% reduction in latency. For more information, see: https://t.co/F6tatQuoAe #zoscs21
Q2: Any plans to have ACF/TAP analyze IP packet traces? #zoscs21
A2: We have no plans for any updates to ACF/TAP. #zoscs21
V2R1 Fact: In addition to RDMA, V2R1 supports many other new features. For an overview, see this screencast: http://t.co/MBt0y4AnqT #zoscs21
Q3: Not a CommServer question but mainframe network - will WLM ever be able to loadbalance geographically dispersed SYSPLEXs? #zoscs21
A3, Part 1: WLM can provide load balancing advice for a single sysplex even if it is geographically dispersed #zoscs21
A3, Part 2: With IBM's GDPS Active-Active solution, load balancing can span different sysplexes using ... #zoscs21
A3, Part 3: ... the IBM Multi-Site Workload Lifeline product and an external load balancer. #zoscs21
V2R1 Fact: No longer have to say "Oops!" With V2R1, you can check the syntax of a TCP/IP Profile prior to activating it. #zoscs21
That's it for today's #zoscs21 chat! Thanks for your participation!
SamReynolds 270004DVAN 551 Visits
On Wednesday, October 9th from 1:00 PM to 2:00 PM EDT, z/OS Communications Server will hold a question and answer session on Twitter, with a focus on z/OS V2R1 CS features including Shared Memory Communications over RDMA. Beginning at 1:00 PM on the 9th, please Tweet your V2R1-related Communications Server questions with hashtag #zoscs21. Several of our z/OS CS team members will be monitoring the questions, and we will Tweet out the questions followed by our answers. Please plan to join us for this Twitter chat!
SamReynolds 270004DVAN 642 Visits
IBM released the following announcement letter today: http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=897&letternum=ENUS114-009
Included in this letter are two Statements of Direction related to z/OS Communications Server:
Last z/OS release to provide software support for several TCP/IP device drivers: z/OS V2.1 is planned to be the last z/OS release to provide software support for several TCP/IP device drivers. IBM recommends that customers using any of these device drivers migrate to more recent device types, such as OSA-Express QDIO and HiperSockets™. The TCP/IP device drivers planned to be removed are: Asynchronous Transfer Mode (ATM), Common Link Access To Workstation (CLAW), HYPERChannel, Channel Data Link Control (CDLC), SNALINK (both LU0 and LU6.2), and X.25.
Note:Support for SNA device drivers is not affected.
Removal of SMTPD NJE Mail Gateway and Sendmail mail transports from z/OS Communications Server:It is the intention of IBM to remove the Simple Mail Transport Protocol Network Job Entry (SMTPD NJE) Mail Gateway and Sendmail mail transports from z/OS Communications Server in the future. If you use the SMTPD NJE Gateway to send mail, IBM recommends you use the existing CSSMTP SMTP NJE Mail Gateway instead. CSSMTP provides significant functional and performance improvements. The Sendmail client program can also be used to send mail messages; a replacement function using CSSMTP as the SMTP transport is planned. This function will be designed so that it does not require application programming changes. No replacement function is planned in z/OS Communications Server to support using SMTPD or Sendmail as a (SMTP) server for receiving mail for delivery to local TSO/E or z/OS UNIX System Services user mailboxes, or for forwarding mail to other destinations.
SamReynolds 270004DVAN 564 Visits
Welcome to the z/OS Communications Server Blog! We have created this blog to provide another avenue for communicating with customers interested in z/OS CS. While we have been on Facebook and Twitter for some time now, we know that some of our customers are not allowed to access either of those sites from their shops due to corporate I/T policies. While we will continue to use Facebook and Twitter for those that prefer that form of communication, we will place most of our hints, tips, announcements, etc. on this blog, with excerpts and links provided to Facebook and Twitter.
Today was the final day of the Winter 2012 SHARE conference in Atlanta. As always, those of us from Communications Server enjoyed the opportunity to speak with many of our customers, and discuss topics such as zEnterprise networking, network security, sysplex technologies, IPv6, and Enterprise Extender. If you were at the conference, we hope that you also enjoyed the experience and learned a few things that will help you back at your shops. Whether you were there or not, we hope you will consider joining us for the Summer 2012 SHARE conference in Anaheim, California (August 5th-10th).