Maintenance for the WebSphere Application Server optional materials is similar to that for the base WebSphere Application Server for z/OS product. Maintenance is applied using the System Modification Program / Extended (SMP/E), and then it is moved into production. The optional materials include feature packs and other interim deliverables.
In general, feature-pack maintenance levels for WebSphere Application Server Version 7.0 are closely linked to base WebSphere Application Server maintenance levels. On distributed platforms, feature-pack maintenance is applied automatically when base maintenance is installed. On z/OS systems, customers are responsible for upgrading feature-pack levels whenever base service levels are upgraded. If the WebSphere Application Server base service level is higher than the feature-pack service level, feature-pack enabled servers do not start.
The WebSphere Application Server for z/OS service support Web site provides program temporary fix (PTF) lists for the base WebSphere Application Server for z/OS product and for each feature pack or other interim deliverable. The general rule is that each feature-pack level runs correctly with the base WebSphere Application Server product at the same level or one level higher. Therefore, feature-pack Version 7.0.0.13 will run with base WebSphere Application Server Version 7.0.0.13 or Version 7.0.0.14. If you upgrade the base product code to Version 7.0.0.15, you also need to install a new level of feature-pack Version 7.0.0.15.
Contact the IBM Software Support Center or consult the WebSphere Application Server for z/OS service support Web site to determine the PTFs for the required feature pack or interim deliverable maintenance levels, and order or download these PTFs.
The WebSphere Application Server for z/OS nodes that are upgraded to the new service level are now running with compatible WebSphere Application Server for z/OS and optional-materials maintenance.
Restarting a WebSphere Application Server for z/OS node at a previous service level normally involves simply switching the runtime to use the previous level of code (datasets and product file system); the post-installer checks that any configuration changes made since the old level are backwards compatible.
backoutPTF.sh CEA target_service_level