Appeal No. 1997-1009 Application 08/033,731 However, we agree with appellants that Cobb does not disclose the claimed steps of "selecting . . . at each potential exception condition in the code the appropriate subset . . . in an activation table . . . unique for each task" (emphasis added), and then, in response to detection of the occurrence of an exception condition, "retrieving . . . the pertinent data fields from the descriptions . . . contained in the last subset . . . selected in the activation table . . . associated with the faulty task" (emphasis added). These limitations make it clear that the activation table, throughout execution of the program code, identifies the subset in the data table which corresponds to the potential exception condition currently of concern. Cobb, in contrast, does not track potential errors or the corresponding information in the data table. Instead, Cobb waits until an actual error has been detected to determine which data in the data table corresponds thereto: The Early Detection Data Capture process uses permanently placed error detection points located strategically within a software program when initially developed. The detection points check the status of the software program throughout its execution. If an error is detected, the EDDC process is called. Unless an error is detected, the - 5 -Page: Previous 1 2 3 4 5 6 7 8 9 NextLast modified: November 3, 2007