Creating a Library

Qualifiers for the LIBRARY Command

Libraries provide a tool that makes VMS LINKs easier to manage. Like VMS LINK, GT.M ZLINK can also access object libraries. However, ZLINKing from object libraries has some restrictions that limit its utility. If you wish to focus on program development from the GT.M environment rather than from the VMS environment, you can skip over this section and continue with the section on "Controlling Run-time Parameters" which follows.

When an object module contains frequently used routines, you can store the object module in a library for future use. A library simplifies file management and the linking process because VMS LINKs do not have to explicitly refer to object modules filed in a library.

You might store the previously developed LOOKUP and SUM routines in an object module library, TOOLS.OLB. Create the library file of object modules using the VMS Librarian utility. Invoke the Librarian using the DCL command, LIBRARY.

Example:

        $ LIBRARY/CREATE TOOLS LOOKUP,SUM
      

The Librarian creates a library in the file TOOLS.OLB. The default library type .OLB indicates an object library.

Example:

        $ LIBRARY TOOLS TAXES/INSERT
      

This adds the newly developed TAXES module to the library, TOOLS.

The fact that the Librarian accepts VMS wildcards makes the Librarian a powerful tool for gathering and managing modules. The Librarian creates and maintains indexed libraries, which can assist in linking.

This documentation focuses on those aspects of the Librarian relevant to the GT.M user's needs for object code management. The Librarian also manages other types of files. For more information refer to the VMS Librarian Reference Manual.

The format for the LIBRARY command is:

        LIBRARY[/qualifier[...]] library-file-spec 
        input-file-spec,[...]]