IBM OS/390 User Manual

Here is a list of DFSMS 

″

Fast Implementation Techniques

″ (

FIT) Redbooks:

•

DFSMS FIT: Fast Implementation Techniques Process Guide, SG24-4478

•

Get DFSMS FIT: Fast Implementation Techniques, SG24-2568

•

DFSMS FIT Forms and Foils, SG24-2570

•

DFSMS FIT: Fast Implementation Techniques Installation Examples, SG24-2569

•

DFSMS/MVS V1R4 Technical Guide, SG24-4892

The following OS/390 resources are all identified by names. Some names are
seven or eight characters, others can be up to 16 or 44 characters in length. By
using significant positions of the name, you can more easily manage and control
them for registration, security, and general systems management purposes.

Most installations use the first character of the name to identify the resource
type or production application, such as P (Production), T (Test), S (Systems
Programming), and  I (Inventory Applications).

There are lots of entities to name in MVS. It is a good idea (if not required) to
start these names with an alphabetic character (A-Z). This is not a complete list,
but below are some resources that need names.

Names can be up to 44 characters long and start with a high-level qualifier that
identifies both who owns the data set (such as a user ID, project, application, or
group), along with an indication of production, test, or systems. Use these long
names, with specific levels of the DSName to indicate the following:

•

System vs. Production vs. Test; Temporary vs. Permanent

•

Application Name or ID

•

Version Level

The data set name doesn

′

t need to identify the access method being used. (The

main reason people used to do this was because of the old VSAM catalog
volume 

′

ownership

′. 

Since this is no longer an issue with ICF catalogs, there is

no need to include this.) Some other things

 not to include in the data set name

because they will probably change: department, location management criteria,
device type, or expiration date.

The only difference here is that the data set name loses one level of
qualification, the lowest level. Don

′

t use the generation to indicate a different

type of data. For example, don

′

t use 

′ ( + 1 ) ′  

for reports and 

′ ( + 2 ) ′  

for

intermediate files. Have separately named GDGs instead.

DASD and tape volumes are typically labeled so that they can be logically
related to an application, geometry, storage group, or purpose, for example
TSOxxx or PAYxxx. Keep in mind how you are going to list volumes from ISMF.
For example, if I want to list all of my work or TSO packs, it would be nice to
simply enter WRK* or TSO*.

VSE to OS/390 Migration Workbook