User application data

User application data consists of the application data (programs) being developed for a single project. SCLM stores all user data associated with a single project as members within a hierarchical set of MVS™ partitioned data sets (ISPF libraries). These data sets are called the project partitioned data sets. Users refer to SCLM-controlled ISPF libraries with an SCLM naming convention containing three levels of qualification, specifically:

project_name.group_name.type_name

The first qualifier, project_name, is the unique project identifier associated with the hierarchy.

SCLM organizes project data sets into groups, the second identifier within the naming convention. Each group represents a different stage or state of the user data within the life cycle of a project. For example, assume a project has three groups named DEV1, TEST, and RELEASE. The DEV1 group represents data being modified. The TEST group represents data being tested. The RELEASE group represents data released for customer use. The groups of a project are organized into hierarchical order to form a tree-like hierarchy.

A group is made up of several data sets that can contain different types of data. Types, the third qualifier of the naming convention, are used to differentiate the kinds of data maintained in the groups of a project. For example, source code would be stored in one type and listings in another type. It is better not to mix different data types in SCLM. (Although SCLM allows you to do this, it is not recommended; data with different formats should be stored in different types.)

Thus a user working on an application for project PROJ1 might be assigned to the DEV1 group. The project can be using four different types of data. Therefore the user might have the following project partitioned data sets to work in:

PROJ1.DEV1.SOURCE        - all source modules
PROJ1.DEV1.OBJECT        - all compiler object files
PROJ1.DEV1.LISTING       - all compiler listings
PROJ1.DEV1.LOAD          - all executables (link-edit output)

Note: SCLM can use data sets with names consisting of three levels of qualification as is the practice in many ISPF environments. It can also use data sets with two or more levels of qualification. This is an option that the project manager must enable for a project to use. If this option is used, SCLM developers would still use the project_name.group_name.type_name naming convention when performing SCLM functions. See Flexible naming of project partitioned data sets for more information about this option.