An attempt to log a procedure is regarded as a read access. If the file to be logged has a read password, then this password must have been entered in the current password list with ADD-PASSWORD. If this is not the case, a counter for unsuccessful attempts in the system is incremented and the task is aborted if the limit specified in the system parameter for PWERRORS is reached. However, such behavior could be an unacceptable restriction for the user if, for example, he or she activates logging globally with MODIFY-PROCEDURE-TEST-OPTIONS and his/her calling hierarchy includes password-protected procedures whose passwords he/she does not know.
For this reason, procedures protected by read passwords can never be logged with MODIFY-PROCEDURE-TEST-OPTIONS, even if their passwords are in the current password list. This ensures that no unsuccessful read access attempts are executed and the error counter is not incremented. Such procedures can thus be logged only directly with the aid of the LOGGING operand in CALL-PROCEDURE or in INCLUDE-PROCEDURE. If this is done, an access attempt with an invalid password will again increment the error counter. The same applies to the TRACE-PROCEDURE command.