IBM OS/390 User Manual

Page of 673
25.3.2.2 CBPDO
Custom-Built Product Delivery Option is a software delivery package consisting
of uninstalled products without integrated service. You must use SMP/E to install
the individual OS/390 elements and features, and their service, before you can
IPL.
This method is not recommended for the new OS/390 installation.
25.4 Set Up Standards, Procedures, and Documentation
You now have a running system that is tailored to your environment and users.
Your next step is to set up and document standards and procedures for all those
people that will be using and operating it.
25.4.1 Installation Standards
As you develop your new OS/390 environment and your applications and user
community grow, it is very important to develop good standards for all your
resources and users. It is much easier to do this from the beginning than to go
in later and impose standards and procedures were there were little or none
beforehand.
25.4.1.1 Data Management Standards
DFSMS naming standards are not trivial, but there is a lot of guidance. This is
really part of the DFSMS implementation process, which is a whole study in
itself. The DFSMS FIT Redbooks have suggestions for naming the constructs and
worksheets to assist with the migration. A good rule, as always, is to keep it
fairly simple. Here are some suggestions for name-significant characters:
Data Classes - Start the name with D or DC, and include DSORG, RECFM,
LRECL, or Space requirements.
Storage Classes - Start it with an S or SC. Examples are SCSTAND, SCPREF,
SCFAST, and SCNOSMS. Distinguish service but don
t use parameter values.
Management Classes - Start the name with M or MC. Use the remaining
characters for indicating which service elements separate it from the other
classes. For example, MCNOMIG for data sets that you don
t want to have
migrate/recalled. Other attributes could include Backup, Archive, Migration,
and Space attributes.
Storage Groups - Start the name with G or SG. The name should identify the
type of data associated with the pool. For example, use things such as
SGWORK (for temp), SGPRIME (for batch production), or define storage
groups according to size, for example SGLARGE for large and SGSMALL for
small data sets. The advantage to this is reducing fragmentation on the
volumes and reducing out-space abends for new allocations and extents.
Storage systems education is available for your systems programming staff. See
IBM Education and Training
s storage systems course curricula for your area.
Contact your IBM Representative or their web site at:
http://www.training.ibm.com/ibmedu/roadmaps/mainframe/storsys/
Chapter 25. Prepare the Migration Environment
407