SINGLE_PACKAGE

Enables the preprocessor to generate one BND file and package for the main program all of the nested programs contained in a given source file.

For all programs defined in the source file, the DB2 ECM creates a single BND file; thus a single package is bound and stored in your DB2 LUW database. Because they are all bound into the same DB2 LUW package, all programs in the package share the same BIND timestamp token(s) as the main program. The naming conventions of the BND and package files follow the same rules as for non-nested programs.

Important: Cursors that are shared among the programs in a given package must be uniquely named and defined within that package.

Tip: For detailed information on how the DB2 ECM handles nested programs, see Support for Nested COBOL Programs and PL/I External Routines.

Syntax:

[NO]SINGLE_PACKAGE

Properties:

Default:	NOSINGLE_PACKAGE
Synonym:	MULTI-NESTED

Dependencies:

SINGLE_PACKAGE is mutually exclusive to both the MULTI_PACKAGE and IGNORE-NESTED directives.