Extended syntax check

[Former Member]

Hi All,

what is the role of extended syntax check in performance tuning?

Thanks,

Rakesh.

[ThomasZloch]

good luck with your interview or exam!

extended syntax check or code inspector will find non-performant database operations, e.g. when no primary key or index is used, bypassing of table buffers, nested selects, updates in loops etc.

[matt]

extended syntax check or code inspector will find possibly non-performant database operations...

It doesn't always get it right. Hence the requirement for exclusions.

matt

[Former Member]

Hi Rakesh,

Extended Program Check

Many checks are excluded from the standard syntax check for performance reasons. The extended program check performs a complete check that includes the interfaces of external procedures called from your program.

Errors in the extended program check cause exceptions, which in turn cause runtime errors when you run the program. You must correct them. The exception to this is coding that cannot be reached. However, you should delete this to minimize the size of your program and make the source code easier to understand.

Warnings in the extended program check should also be corrected. If your program contains statements that are definitely correct but still produce warnings in the extended program check, you can exclude them from the check using pseudocomments ( "#EC… ).

You should always run the extended program check on a new program. You have not finished developing a new program until you can run the extended program check on it without any errors or warnings. Messages are permissible, since they are generally not critical.

The extended program check is also only a static check. It cannot eliminate all of the circumstances that could lead to exception situations or runtime errors. For example, any statements in which you specify arguments dynamically as the contents of fields, or in which you call procedures dynamically, cannot be checked statically.

Plz Reward if it is useful,

Mahi.