1.   The module type in LIFESPAN must be the same as the module type on the primary directory.

2.   If the module types differ, an error message will be generated and LIFESPAN ABLE will stop at the end of the prepass phase.

3.   The user should ensure that the module types are the same.

4.   A subset of this module type is known as a PRODUCT package as it is a package intended for issue as a product.

5.   All the initial keywords are compulsory with the exception of FOREIGN-SET-IS which must be omitted if the module type is not foreign.

6.   This Listing is completed by an alphanumerical list of all the modules in the structure including their version number and module type.

7.   Note that some of these data types have other types associated with them eg.

8.   For every module name entered, the module type must be specified.

9.   This column enables you to specify the module type for the new name you wish to reserve.

10.   LIFESPAN will then display the module types for any names supplied.