Program Packaging — A Simple Scenario

To understand the various program packaging options available to you, it helps to understand how the program packaging process works. For example, assume you are designing and developing an assembler language program named DOITALL. From development to execution, DOITALL can be in one of three basic formats, each of which is identified by its file type:

1. An assemble file (DOITALL ASSEMBLE) — This is the file that contains the actual assembler language program. Before you can run DOITALL, you need to compile (or assemble) it, thus creating a text file. You can assemble a program using one of the following:
   1. With Assembler XF, use the CMS ASSEMBLE command.
   2. With Assembler H, use the HASM command.
   3. With the high level assembler, use the HLASM command.

   For more information on assembling files, see Assembling, Loading, and Executing Programs.

2. A text file (DOITALL TEXT) — This is the output of the assembly process. To execute a text file, you must load it into storage and start it. There are several ways to load and start text files, see Loading and Executing Text Files for details.
3. A module file (DOITALL MODULE) — Module files, or modules, consist of one or more text files that have been linked to form a single program package. After the required text files are loaded into storage, you can use the CMS GENMOD to create a module. See Generating and Executing Modules for details.

In addition to the three basic forms a program can take (assemble file, text file, and module file), you can package programs as nucleus extensions, subcommands, or immediate commands. For example, you could create a nucleus extension, a subcommand, or an immediate command from either DOITALL TEXT or DOITALL MODULE.