This topic applies only on the z/OS operating system.

Product data sets

This article describes the WebSphere® Application Server for z/OS® product data sets and recommends a product data set naming convention.

WebSphere Application Server for z/OS product code resides in MVS™ partitioned data sets (which contain the product data sets) and MVS hierarchical file system directories (which contain the product directory and its subdirectories). The default high-level qualifier for the product data sets is BBO.
Note: In this and subsequent articles, was_hlq is used to represent the high-level data set name qualifier for a particular set of WebSphere Application Server for z/OS product data sets.

Product data set contents

The WebSphere Application Server for z/OS product data sets are divided into target data sets (used during product customization and execution) and distribution libraries (used to "back off" maintenance if necessary).

The WebSphere Application Server for z/OS target libraries are as follows:
was_hlq.SBBOCLIB
REXX scripts used by the Customization Dialog
was_hlq.SBBODSD
Side decks
was_hlq.SBBOEXEC
CLIST scripts
was_hlq.SBBOJCL
JCL for installation jobs
was_hlq.SBBOLD2
Load modules that must NOT be placed in LPA; can be in link list
was_hlq.SBBOLOAD
Load modules that can be placed in LPA or link list
was_hlq.SBBOLPA
Load modules that must be in LPA or loaded in ECSA by the location service daemon
was_hlq.SBBOMAC
Assembler macros
was_hlq.SBBOMIG
Load modules for use with IPCS dump formatting
was_hlq.SBBOMJPN
Customization Dialog message library (Japanese)
was_hlq.SBBOMLIB
Customization Dialog message library (English)
was_hlq.SBBOMSG
Message translation skeletons
was_hlq.SBBOPJPN
Customization Dialog panel library (Japanese)
was_hlq.SBBOPLIB
Customization Dialog panel library (English)
was_hlq.SBBOSLB2
Customization Dialog skeleton library of variable-length record files
was_hlq.SBBOSLIB
Customization Dialog skeleton library of fixed length, LRECL=80 files
The WebSphere Application Server for z/OS distribution libraries are as follows:
was_hlq.ABBOANT
HFS files
was_hlq.ABBOCLIB
REXX scripts used by the Customization Dialog
was_hlq.ABBOEBCD
HFS files (EBCDIC)
was_hlq.ABBOEXEC
CLISTs used by the Customization Dialog
was_hlq.ABBOEXP
Export files
was_hlq.ABBOINC
Include files
was_hlq.ABBOJAR
JAR files
was_hlq.ABBOJCL
JCL for installation jobs
was_hlq.ABBOMAC
Assembler macros
was_hlq.ABBOMJPN
Customization Dialog message library (Japanese)
was_hlq.ABBOMLIB
Customization Dialog message library (English)
was_hlq.ABBOMSG
Message translation skeletons
was_hlq.ABBOOBJ
Object modules for load module creation
was_hlq.ABBOPJPN
Customization Dialog panel library (Japanese)
was_hlq.ABBOPLIB
Customization Dialog panel library (English)
was_hlq.ABBOSLB2
Customization Dialog skeleton library of variable-length record files
was_hlq.ABBOSLIB
Customization Dialog skeleton library of fixed length, LRECL=80 files

See WebSphere Application Server for z/OS: Program Directory (GI11-2825) for allocation information about each target library and distribution library. Updates to this information are included in the Preventive Service Planning (PSP) bucket for each release of WebSphere Application Server for z/OS.

Product data set naming restrictions

The IBM® ServerPac and SystemPac® and the IBM Custom-Build Product Delivery Option allow you to rename product data sets during installation. In addition, the IBM ServerPac and SystemPac allow you to merge members from similar target libraries into a single data set. However, keep in mind the following:
  • You should not merge SBBOLD2 with any other load module library.
  • You should not merge SBBGLOAD with any other library because it is a 64-bit library.
  • The Customization Dialog script library (SBBOCLIB), message libraries (SBBOMSG and SBOJPN), panel libraries (SBBOPLIB or SBBOPJPN, and skeleton libraries (SBBOSLIB and SBBOSLIB) are allocated directly by the Customization Dialog startup exec. You should not merge these libraries with any other ISPF libraries, and they should all have the same high-level qualifier as the SBBOEXEC data set that contains the Customization Dialog startup exec.
  • Ensure that the Customization Dialog data sets are cataloged.

Product data set naming convention

As noted above, certain WebSphere Application Server for z/OS data sets must have the same high-level data set name qualifier in order for the product to function correctly. Product maintenance and migration is easier if all product data sets have the same high-level qualifier.

On the other hand, in order to continue to run WebSphere Application Server for z/OS while applying maintenance, you must have at least two copies of the product data sets: one for the running application execution environment and one to which service is applied.

We recommend you choose a middle level qualifier for each separate release and maintenance level of WebSphere Application Server for z/OS. This middle level qualifier can reflect a very simple test/production distinction, such as with "BBO.V6PROD.*" or "BBO.V6TEST.*", or can include specific service level information, such as with "WAS.W600102.*" or "WAS.W600103.*".

There are many places where you must specify the product data set names, so, to avoid undue confusion, use the simplest data set naming scheme that accomplishes your maintenance goals.

Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=cins_plandatasets
File name: cins_plandatasets.html