Browse Prior Art Database

BVT Automation for z/OS SMP/e bypass install on VICOM

IP.com Disclosure Number: IPCOM000198329D
Publication Date: 2010-Aug-04
Document File: 1 page(s) / 43K

Publishing Venue

The IP.com Prior Art Database

Abstract

On z/OS, during product development time during testing continuous builds are created to test a product. The testing teams then need to run SMP/e to install a given build image on VICOM to it.This is a long process even if it is automated. However, a z/OS driver image can contain all the HFS structures and be transformed into a zip file so that it can be unzipped unto VICOM as an SMP/e bypass driver. This new kind of image will require a new process to detect a new build and start testing automatically. Therefore, we need an end-to-end plug-in automation solution to integrate this new process with current test automation infrastructure. In order to detect a new SMP/e bypass driver and send to the VICOM site. The VICOM site also needs to have new automation to know this driver is a special SMP/e bypass driver type and needs to be unzipped on VICOM. For feature pack releases which require base builds, this new automation will find out the required base build. It will also automatically install it so it can then unzip the feature pack release SMP/e bypass image. The new SMP/E bypass install process can save an average of twenty minutes when it's compared with the former native SMP/e install. Due to the time savings during the install process, the new method can shorten the duration of the build verification for any z product.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 73% of the total text.

Page 1 of 1

BVT Automation for z/OS SMP/e bypass install on VICOM

VICOM site has a new JCL for unzip the SMP/e Bypass image. When release manager request a new driver, it will specify it is SMP/e Bypass image. Build process builds the new driver with whole HFS structure. After the build process, a new SMP/e Bypass driver will put in the storage, This new automation system will detect it, start to parse build log file - iam.xml and other xml files associated with a new driver. iam.xml file will contain SMP/e Bypass image info so that automation can figure out this is a SMP/e Bypass image. Then it calls a STAF/STAX job to call a TSO command to use the new tooling on VICOM side to Vnzip SMP/e Bypass image. On VICOM side, when it received TSO command to install SMP/e Bypass image, it will find a free volume, unzip the SMP/e Bypass image unto HFS and assign a level number: BOSSLEVEL. Then notify the BVT automation so that BVT automation can continue as before to use that BOSSLEVEL to zosplex a VM system to kick off automated testing.

For feature pack release driver, this new automation system will used the build log xml files to figured out which base build is required, then call a VICOM tooling to find out the VICOM BOSSLEVEL for the base build, VICOM tooling will use the base build BOSSLEVEL volume as a base. Then this new automation system will call VICOM tooling by giving the feature pack release SMP/e bypass image info. VICOM tooling then use this feature pack info to unzip...