IBM InterConnect 2017: Day 4

Session 1: z/OS Panel Discussion

  • Third parties can now interface with other types of data. Rocket Data Virtualization is now available as another add-on for z/OS Connect. Current list is CICS, IMS, DB2, MQ, WAS, RDV (for VSAM, and other databases), and batch.
  • z/OS Provisioning Toolkit is being used to bring up z/OS Connect very quickly.
  • DB2 Stored Procedures can be exposed this way too.
  • Batch is providing API calls as well (Executes batch program or pauses and waits for the API call). Check Git repo for documents on how to connect to batch and provide examples.
  • There is tremendous momentum in this space and for this product.
  • Cuts cost due to the simplicity and ability of a direct connection to the mainframe without building extra infrastructure and software.
  • CICS Web Services has much more overhead and isn’t as ubiquitous as API calls. Can be done in as little as 30 minutes to setup an API.
  • There is an ability to do an “API Shack”, which is when IBM comes in and sits down with developers and system programmers to get a POC (proof of concept) together. Nationwide had a POC up and running in 2 days for Apple Pay.
  • There are opportunities to remove MQ from an equation, but it since REST is stateless its complementary. REST is not guaranteed delivery.
  • Developers should never know where the data is coming from (DB2, batch, whatever).
  • There are some dependencies for z/OS Connect. Some features need CICS 5.3 and up and MQ 9 and up.


Session 2: How to Develop New Insights into Your z Systems Data

  • zOI (z Systems Operational Insights)
  • Relatively new space that allows z System insights from an application on BlueMix.
  • Splunk and Operational Insights have a partnership with Splunk to be able to ship data into Splunk after crunching the data.

Session 3: Essentials for Java on z Systems

  • Can directly call DB2 and MQ in memory now.
  • This is the desired list to be supported for JEE7.

Session 4: Installing and Configuring GDPS: How JN Data Customized DR Testing in a Production Environment

  • Recommendation to have debug on for the primary system in use.
  • The Planned Actions panel is a list of scripts that are user defined.
  • JN Data’s test plan is 2 planned hyperswap (10 sec) and 1 unplanned hyperswap (10sec) per quarter.
  • Includes 5000 pairs and 120 TBs of data.
  • This is during full production functions. Never had any issues with CICS, IMS, or DB2 afterward.
  • Recommendation is that the case systems should not be in the group cap when performing the test otherwise queuing will occur. Weight on case LPARs should be higher then others as well.

Session 4: Garanti’s z Modernization Story: Creating and Managing New Workloads

Session 5: Mastering the z Systems Development and Test Environment Golden Image

  • There are twice a year updates that can allow for software updates without installing new software on the image.
  • Can bring way too much data though, but does work fine otherwise.
  • Using IBM Application Discovery, it can help limit the amount of data that needs to come over.
  • Do not have to do the second two steps if you do not have IBM AD (Application Discovery). You have to know what volumes you need though in order to do this.
  • This program then builds and installs everything (zD&T) on a Linux server. The Linux server should only have the OS and that’s about it.
  • This could be on-premise or in the cloud as long as SSH is available.

IBM Rocks

  • Zac Brown Band with Andy Grammer!

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s