Time-stamped checking is based on the fact that every program unit CARRIES a time STAMP, which is set when it is CREATED or recompiled. Whenever a program unit or a schema object is altered, all its dependent units are invalidated and must be recompiled before they can be executed. The time stamp is recorded in the p-code of the procedure.

The time stamp of the REMOTE procedure is also stored in the p-code of the local procedure when it is COMPILED. A local procedure, which refers to a remote procedure, is invalidated if the remote procedure is recompiled after the local procedure is compiled. When the time stamp of the remote procedure, which is stored in the local procedure, is compared with the time stamp of the recompiled remote procedure, both the time stamps differ. This invalidates the local procedure and returns a runtime error.

Time-stamped checking is based on the fact that every program unit carries a time stamp, which is set when it is created or recompiled. Whenever a program unit or a schema object is altered, all its dependent units are invalidated and must be recompiled before they can be executed. The time stamp is recorded in the p-code of the procedure.

The time stamp of the remote procedure is also stored in the p-code of the local procedure when it is compiled. A local procedure, which refers to a remote procedure, is invalidated if the remote procedure is recompiled after the local procedure is compiled. When the time stamp of the remote procedure, which is stored in the local procedure, is compared with the time stamp of the recompiled remote procedure, both the time stamps differ. This invalidates the local procedure and returns a runtime error.