Browse Prior Art Database

Exercising LAN Server Lanprobe Inernal Errors

IP.com Disclosure Number: IPCOM000105791D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 59K

Publishing Venue

IBM

Related People

Arkeketa, WW: AUTHOR [+4]

Abstract

Disclosed is a function, a design, and a methodology for testing internal errors that can be encountered in the LAN Server* 3.0 LANPROBE function and the LAN Server 3.0 Generic Alerter service.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Exercising LAN Server Lanprobe Inernal Errors

      Disclosed is a function, a design, and a methodology for
testing internal errors that can be encountered in the LAN Server*
3.0 LANPROBE function and the LAN Server 3.0 Generic Alerter service.

      There are times when there is no easy way to "naturally" test
all of the internal error paths that are found in a function.
However, the need still exists to perform this verification, as much
as possible, in a controlled environment with as much confidence as
possible that the internal error code will work if presented with the
opportunity.

      The disclosed function takes advantage of the LANPROBE design
along with a simple methodology to make testing of internal errors
easier and more reliable.  The LANPROBE code is a dynamic link
library (DLL) that is divided into two main functions: the main
LANPROBE function and the error-handling function.

      The error-handling function consists of building the First
Failure Support Technology/2 (FFST/2) error log and message log
control blocks.  These control blocks are passed on to FFST/2 where
they are logged.  The error handling function is called with the
following input arguments:  internal error id, API return code
causing error, location in source where API return code was detected,
and the name of caller.  The call would appear as follows:

         if (rc = FunctionBeingUsed(....))
           {
            Handle_Err(FunctionBeingUsedError,rc,__LINE__,"name");
           }

      This is the methodology.  Since it is possible to easily cause
some FFST/2 error return codes, it i...