Skip to content

Defining Library Types And Staging Library Attributes

A library type definition sets processing rules for the components stored under that library type. The definition also sets the data set attributes for the package staging library that is allocated for the library type. The Global Administrator defines the library types that are available to applications.

Global administration contains library types for all unique component types and processing requirements that might be required in any application. Library types can be changed at the application level, but they should be standardized on global definitions to simplify administration maintenance.

To define global library types, follow these steps:

  1. On the Update Global Administration Options menu (CMNGAMN1), type 2 on the Option line and press Enter. The Global Library Types Part 1 of 2 panel (CMNCGLT0) is displayed.

    The first time you access this panel to define global library types, the panel is empty. This is an example of the panel after library types are entered.

    CMNCGLT0         Global Library Types Part 1 of 2          Row 1 to 7 of 7 
Command ===> ____________________________________________ Scroll ===> CSR

    Lib                                     Order Lke Seq Defer Target Sel 
    type description                      +                     type   Opt
___ CLS CLIST                               0     C         Y 
___ JCL JCL Library Type                    0     P         Y 
___ LCT Linkedit Control Cards              0     P         Y 
___ LST Listing                             0     P         Y 
___ NCL NCAL subroutine load library        0     N         Y 
___ OBJ Object module library               0     O         Y
___ PKG Db2 Bind Package Commands           0     P         Y          D 
**************************** Bottom of data ******************************

    The following table describes the fields on the Global Library Types Part 1 of 2 panel.

    Field Description
    Line Command Enter a one-character to the left of a panel row.
    S - Select to see the next panel for this library type.
    I - Insert a blank library type row.
    R - Repeat an existing library type row.
    D - Delete an existing library type row.
    Lib type Enter a three character library type. The following library types are defined and reserved by ChangeMan ZMF . These lib types must have the following attributes: Like-types are defined in panel 2 of 2 CMNCGLT1
    CPY - Copybooks - Requires like-copy, DCB must be RECFM=F/FB, LRECL=80
    CTC - Control Cards - Requires Like-PDS. DCB must be RECFM=F/ FB, LRECL=80.
    DOC - Documentation or text files- Requires Like-PDS. DCB must be RECFM=F/FB/V/VB.
    JCL - Job Control Language - Requires Like-PDS, although libraries with this type are included in Impact Analysis JCL relationships. DCB must be RECFM=F/FB, LRECL=80.
    LCT - Link Edit Control Cards - Requires Like-PDS. DCB must be RECFM=F/FB, LRECL=80.
    LOD - Load Modules - Requires like-load. DCB must be RECFM=U, LRECL=0.
    LST - Compiler Listings - Requires Like-PDS. Cannot be explicitly staged; however they can be browsed. DCB must be RECFM=F/FB, LRECL=80, BLKSIZE=23440
    PRC - Cataloged JCL Procedures or PROCS - Default to Like-PDS and are included in Impact Analysis JCL relationships. DCB must be RECFM=F/FB, LRECL=80
    SRC - Source code - Requires like-source. DCB must be RECFM=F/ FB, LRECL=80
    Description Enter freeform text describing library type.
    Order Enter a number that will determine the order the Lib type list is displayed to users by default. Valid values are 0 to 65535. The display order option must be enabled in global parameters for the display order number to take effect.
    Lke (like type) Type a one-character LIKE code to define behaviors and characteristics of a library type.
    S - Like-SRC – Components in like-source library types are staged through a batch job defined by a Language and Procedure assigned to the component to create a component in a like-load library type. Every like-source library type must have a TARGET TYPE in its Library Type Definition. There is a source-load relationship between every like-source component and a like-load component. Members in like-source libraries are analyzed for Impact Analysis copybook relationships.
    C - Like-CPY – Components in like-copy library types are not processed through a procedure by stage. Like-copy libraries are included in SYSLIB concatenations for copybook libraries.
    L - Like-LOD – Components in like-load libraries are assumed to be the product of a stage procedure performed on a likesource component. Like-load libraries are included in SYSLIB concatenations for load libraries.
    N - Like-NCAL – NCAL load subroutines. Once staged they are concatenated in the SYSLIB for links within the same package (if the library type is present in the package).
    O - Like-Object – Object code subroutines. Once staged they are concatenated in the SYSLIB for links within the same package (if the library type is present in the package).
    P - Like-PDS - Components in Like-PDS library types are not processed through a procedure by stage. Like-PDS libraries are not included in SYSLIB concatenations for copybook or load libraries. Members in Like-PDS libraries are not analyzed for Impact Analysis relationships.
    Blank - Like-Other – If you leave the LIKE field blank in a Library Type Definition, the type is referred to as "like-other". Components in like-other library types are staged through a batch job created from an ISPF skeleton named CMN$$xxx where xxx is the like-other library type. Code like-other skeletons from a model named CMN$$OTH delivered in the product. You must also customize skeleton CMN$$CKO to check out components in a like-other library type. Search CMN$$CKO for "OTHER" to see instructions in the skeleton comments.
    NOTE: Like-other libraries are not analyzed for Impact Analysis relationships. Like-other components are not analyzed by Audit.
    Seq (library sequence) Type a numeric value from 001 to 255 for like-copy like-load library types.
    Sequence number influences two functions:

    ● In build processing, sequence numbers that are assigned to likecopy library types determine the order of compile SYSLIB library concatenations, sequence numbers that are assigned to likeobject, like-NCAL, and like-load library types determine the order of link edit SYSLIB library concatenations.
    ● In audit auto-resolve, sequence numbers that are assigned to like-source library types determine the order that stage and recompile jobs are submitted for file-tailoring, and sequence numbers that are assigned to like-load library types determine the order that relink jobs are submitted for file-tailoring.

    Sequence numbers can have a numeric value from 001 to 255 or blank, and there is no edit for unique values. Blank sequence numbers sort ahead of numeric values. When sequence numbers are blank, or when the same sequence number is assigned to library types with same like-type, the SYSLIB or audit auto resolve order is determined by how the library types are stored on the package master, which cannot be controlled by the administrator.
    Defer Y - Defer allocation of the staging library for this types until the fist component of the type is staged or checked out.
    N - Allocate the stage library for this type when the change package is created, even though there may never be any members of this library type in the package.
    CAUTION! An 'N' setting will always allocate a stage dataset even though that type may not be used.
    Target Type Type a like-load, like-object, or like-NCAL target library type for each SRC or Like-SRC library type.
    Sel Opt Use this field to associate a library type with a ChangeMan ZMF selectable option that you have licensed. The behavior of the library type may require further definition in administration panels or ISPF skeletons.
    I=IMS
    D=Db2

    ...

    ChangeMan ZMF sorts the library entries on the panel in ascending alphanumeric sequence by LIB TYPE before it redisplays the panel.

  2. For each library type on the Global Library Types Part 1 of 2 panel you must complete a second panel of information. Type S in the line command for a library type and press Enter. The Global Library Types Part 2 of 2 panel (CMNCGLT1) is displayed. The first time you access this panel for a library type, the panel is empty. This is an example of the panel after entering information for library type CPY.

    CMNCGLT1         Global Library Types Part 2 of 2 
Command ===> ____________________________________________   

Library type: CLS - CLIST  
Like value:   C    Defer value: Y   

Staging dataset attributes: 
Management class . . . . . . (Blank for default management class)   
Storage class  . . . . . . . (Blank for default storage class) 
 Generic unit name . . . . . SYSDA  (Generic group name or unit) 
 Volume serial . . . . . . . _____  (Required if generic unspecified)   
 Space units . . . . . . . . TRK    (trk, cyl or blk) 
 Primary quantity  . . . . . 3      (In above units) 
 Secondary quantity  . . . . 1      (In above units) 
 Directory blocks  . . . . . 5 
 Record format . . . . . . . FB   
 Record length . . . . . . . 80 
 Block size  . . . . . . . . 27920 
 Data set type . . . . . . . PDS    (library, pds, zfs or blank) 
 Data set version  . . . . .        (pdse version)   
 Extended attributes . . . .        (no, opt or blank)   
 Save staging version . . . . NO    (y/n/o) o=optional 

Enter "/" to select option: 
__ Checkout component description   
__ Checkout component activity file Library type . . . .  _____

    The following table describes the fields on the Global Library Types Part 2 of 2 panel.

    Field Description
    Management class Enter the management class for SMS managed dataset allocation. Leave blank for default class.
    Storage class Enter the storage class for SMS managed dataset allocation. Leave blank for default class.
    Generic unit name Type the DASD generic group or unit device name to be used for allocating staging libraries for this library type. This field may be left blank if the VOLUME SERIAL field is used.
    Volume serial Type the DASD volume serial number where stage libraries are to be allocated for this library type. This field may be left blank if the GENERIC UNIT NAME field is used.
    Space units Type the units to be used for the primary and secondary space allocations for staging libraries for this library type.
    TRK - Allocate staging datasets in tracks.
    CYL - Allocate staging datasets in cylinders.
    BLK - Allocate staging datasets in blocks.
    Space Allocations Enter the primary space, secondary space, and directory block allocation to be used for the staging libraries for this library type. Use MINIMUM space allocations, especially the PRIMARY QUANTITY. ChangeMan ZMF dynamically reallocates stage libraries if extents or directory blocks are exhausted as the change package grows. Unused space in PDS stage libraries is freed when the change package is frozen. ChangeMan ZMF does not automatically compress stage libraries, but you can compress stage libraries for a package with the ZP Package List command.
    Record format Type the staging library record format for this library type. Valid values include:
    F, FA, FB, FBA, FBM, FM, FS, V, VA, VB, VBA, VBM, VM, U
    Legend:
    F - Fixed length records
    V - Variable length records
    U - Undefined format records
    B - Blocked records
    S - Standard blocks
    A - ASA printer control characters
    M - Machine code printer control characters
    Record length Type the logical record length for components in this library type.
    Block size Type the staging library block size for this library type. Type 0 to let SMS calculate the best block size for the storage device.
    Data set type Leave blank for PDS staging library, or type one of the following:
    LIBRARY - Enter dataset type of LIBRARY to allocate a Partitioned Data Set Extended (PDSE). Except for BLKSIZE, all other DCB attributes will be ignored.
    PDS - Enter dataset type of PDS or leaving the field blank to allocate a standard Partitioned Data Set (PDS).
    zFS - zFS Directory
    Data set version For a PDSE you can enforce version 1, version 2, or allow the system default to be taken.
    Extended attributes NO - Data set cannot have extended attributes or reside in EAS.
    OPT - Data set can have extended attributes and reside in EAS.
    blank - Use default based on data type.
    Save staging versions Select to have prior versions of a component in a change package saved when it has been updated in the staging library. Prior versions can be displayed and acted on using the version control function within the package staging and query functions. This value has no effect if this facility is not installed. See "Staging Versions" on page 43
    YES - Prior versions for this application library type must always be defined to save prior staging versions.
    NO - Prior versions are not saved for this application library type.The application library type can never be defined to save staging versions.
    OPT Saving prior versions is optional for this library type and is defined by the application admin. for each application. The application administrator can define the library type to always save staging versions, never save staging versions, or prompt the developer to make a choice
    Checkout component description Select this option to allow description updates. This will copy the Component General Description from the component master to the change package when a component is checked out. Allow developers to create or update the Component General Description through a change package.type. Users update the description by entering 'ED' on the "Stage:Package Driven" component list.
    If not selected developers are prevented from creating or updating the Component General Description in a change package. The Component General Description can always be created or updated through Application Administration.
    Checkout component activity file This optional file, a free-form record of a component's activity, is maintained as a separate component within a change package, and a separate library type within ChangeMan. When a component is checked out, its Activity File will automatically be checked out with it. Users can then update activity records by entering 'EA' on the "Stage: Package Driven" component feature.
    Library type If 'YES' is entered above, enter the library type (3 characters) that will contain the Activity File for this component. Each component type can have its own Activity File, which must be defined as a Library type, with Baseline and (if necessary for this component) Promotion and Production libs.
    The library type you specify for the component activity file cannot be the same as the library type of the associated source component.
    NOTE: Establish Activity Files as LIKE PDS in Staging Libraries (1 of 2).

    ...

  3. When you finish updating fields on the Global Library Types Part 2 of 2 panel, press Enter to return to the Global Library Types 1 of 2 panel.

  4. When you finish updating library type definitions on the Global Library Types Part 1 of 2 panel, press PF3, or type End and press Enter, to store the global library type definitions in the ChangeMan ZMF package master file.