Faults in Imported Procedures
If an importing process encounters a fault while executing an imported procedure, the system treats this as a fault in the importing process rather than in the process that exported the procedure. If neither the imported procedure nor the importing program incorporates fault-handling code, the fault causes the importing process to terminate. The fault has no effect on the status of the exporting library process.
Conditions That Can Discontinue the Library Process
A server library with a permanent or temporary freeze cannot incur any faults while frozen, because it is not executing any statements. However, an operator can terminate the process with a DS (Discontinue) system command. Further, a server library with a control freeze can incur faults while executing the control procedure, even while the library is frozen.
Effects of Library Termination
If a library process is terminated by a fault or operator action while client processes are linked to it, the system discontinues all processes currently executing procedures imported from that library, and it delinks all other libraries linked to that library.
APPROVAL Procedure Errors
If an error or fault occurs in an APPROVAL procedure, the system prevents the linkage from completing. However, neither the linking process nor the library being linked to incurs an error.
CHANGE Procedure Errors
If an error or fault occurs in a CHANGE procedure, the system prevents the change in connection state from completing. Further, the error or fault is propagated to the requesting process (the process that initiated the linkage or delinkage that is in progress). If the requesting process does not include code to handle the fault, the system discontinues the requesting process.
Errors Linking to Server Libraries
For information about errors that can occur when a process links to a server library or uses an object imported from a server library, refer to Linking to Server Libraries.
Errors Linking to Connection Libraries
For information about errors that can occur when a process links to a connection library or uses an object imported from a connection library, refer to Matching Connection Library Objects.
