The contents of all library process stacks to which the importing process is linked. For a server library, the library process stack is dumped from the base of the FREEZE environment down to the base of the stack. For a connection library, the library process stack is dumped from the highest environment containing a ready connection library interface down to the base of the stack. If no interfaces have been readied from the program, then the process stack will not be dumped even if there is a linked connection library element.

The contents of the library directory in each library process stack. There is one library directory for each export list in a library. For server libraries, only one library directory is in effect at the time a library freezes. For connection libraries, multiple library directories can be in effect at the same time. For each export object, the library directory stores the name, the type of object, and the type of provision used (direct, indirect, or dynamic). For exported procedures, the library directory also stores a description of the parameters of the procedure.

The contents of all library templates in the importing process stack. One library template exists for each library declaration executed by the importing process. A library template stores information about the library attributes. A library template also stores descriptions of all the objects imported from a particular library, including the name, type of object, and parameters.