Stored Procedure Libraries

A stored procedure must reside in the appropriate library in order for the server to locate it.

Type of Stored Procedure

Library

Dialogue Manager

Server Procedure Library.

The external names, EDARPC (MVS) or EDAPATH (all other platforms), are used to locate Dialogue Manager procedures. You can also use the APP PATH feature to locate and manage application code. This process is platform dependent. See the Server Administration for UNIX, Windows, OpenVMS, IBM i, and z/OS manual for details.

Compiled Program

Server Program Library.

The external name IBICPG or physical placement in the user directory of EDACONF is used to locate compiled programs. This process is platform dependent.

A common early practice was to place compiled procedures in the installation home bin directory/library, since it was always searched by default. This practice is no longer recommended since service pack installations will delete these types of files.

IMS/TM Transaction

Server Program Library.

Underlying routines are part of the server installation home bin directory; no library configuration is required.

Note: An external name is a generic name for a variable that is set at the operating system level. The various operating systems that support this feature have different names and methods (syntax) for setting and reviewing these variables. Some of the more commonly used terms for these external names and values are environment variables, registry variables, globals, symbols, defines, assignments, and ddnames. See the Configuration and Operations manual for your platform for specific aspects of working with external names.


iWay Software