Does it support structured logging?

It provides implementation patterns for both simple Conout logging and preferred structured logging via the FWLogMsg system for better observability.

Can it help with database performance?

Yes, it includes specific patterns for identifying wrong index usage and comparing Embedded SQL vs ISAM performance to reduce table scans.

How does this skill help with Protheus runtime errors?

It provides a quick diagnosis guide for common symptoms like NIL access and type mismatches, offering immediate code-level fixes and stack trace analysis.

How does it handle database deadlocks?

The skill provides a methodology for using RecLock with timeout checks and non-blocking parameters to prevent thread exhaustion and data corruption.

ADVPL & TLPP Debugging Specialist

Name: ADVPL & TLPP Debugging Specialist
Author: thalysjuvenal

bythalysjuvenal

•

Analíticas y Monitorización

Diagnoses and resolves ADVPL/TLPP compilation errors, runtime failures, and performance bottlenecks in the TOTVS Protheus environment.

The ADVPL & TLPP Debugging Specialist skill provides a systematic methodology for troubleshooting TOTVS Protheus applications, offering domain-specific guidance on handling everything from syntax errors to complex database deadlocks. It empowers developers to analyze AppServer logs, implement structured logging with FWLogMsg, and optimize slow queries using a blend of embedded SQL and ISAM techniques. Whether dealing with 'variable does not exist' errors or memory leaks in long-running loops, this skill ensures rapid identification and resolution of Protheus-specific issues through detailed diagnostic patterns and best practices.

Características Principales

01Database lock troubleshooting for RecLock and deadlocks

02Performance bottleneck identification and ISAM/SQL optimization

0363 GitHub stars

04Protheus-specific log analysis for AppServer and SmartClient logs

05Systematic diagnostic workflows for compilation and runtime errors

06Structured logging implementation using Conout and FWLogMsg

Casos de Uso

01Analyzing complex stack traces to identify root causes in legacy ADVPL code

02Resolving 'Variable does not exist' or 'Array access out of bounds' runtime errors

03Optimizing slow SQL queries and improving record locking efficiency

Características Principales

01Database lock troubleshooting for RecLock and deadlocks

02Performance bottleneck identification and ISAM/SQL optimization

0363 GitHub stars

04Protheus-specific log analysis for AppServer and SmartClient logs

05Systematic diagnostic workflows for compilation and runtime errors

06Structured logging implementation using Conout and FWLogMsg

Casos de Uso

01Analyzing complex stack traces to identify root causes in legacy ADVPL code

02Resolving 'Variable does not exist' or 'Array access out of bounds' runtime errors

03Optimizing slow SQL queries and improving record locking efficiency