skills.rest
divalto
divaltoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

managing-diva-error-messages

Reads, compares, and manages DIVA application error messages in XXferr ISAM files.

6|Updated May 11, 2026
Search Tags:#diff#erp#downgrade#error messages#diva#isam#xxferr
One-click install
npx skills add https://github.com/divalto/divalto-ia-devkit --skill managing-diva-error-messages-divalto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-diva-error-messages
Source: https://github.com/divalto/divalto-ia-devkit/tree/main/plugins/divalto-devkit/skills/managing-diva-error-messages
Command: npx skills add https://github.com/divalto/divalto-ia-devkit --skill managing-diva-error-messages-divalto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? DIVA application error messages live in XXferr ISAM files (gtferr, ccferr, or partner-specific <prefix>ferr) that cannot be safely parsed with naive byte-level regex, and standard files must never be modified. This Skill reads codes and labels correctly, compares two error files to detect custom codes during downgrades, and documents the safe procedure for adding missing messages referenced by GererErreurCheck(NNN) controls. ## Core Features & Use Cases - List and check error codes: Enumerate all codes and labels (--list) or verify a specific code (--check) by reading real ISAM records via reading-isam-files, avoiding the undercounting trap of naive text extraction. - Diff two error files: Compare a current pack against a standard pack (--diff) to identify custom codes (only_in_a) that must be preserved during a downgrade or migration. - Safe message management: Documents the norm (standard XXferr files are read-only; partner-specific files are writable) and the safe add procedure: backup .dhfi/.dhfd, add via the standard IHM, then verify with --check. Never write binary directly. - Use Case: You added GererErreurCheck(30050) in a business object but no text displays. Use --check 30050 to confirm the code is missing, then add the message to your partner-specific XXferr via the standard IHM and verify. ## Quick Start Ask the assistant to list all error codes and labels from your gtferr.dhfi file and check whether code 1183 exists.

Frequently Asked Questions about managing-diva-error-messages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I list error codes and labels from a gtferr.dhfi file?▼

Run manage_error_messages.py with --list, pointing --file at the XXferr.dhfi and --read-isam-script at the reading-isam-files script. It returns JSON with total_codes and a codes array of code/message pairs read from real ISAM records.

Why does GererErreurCheck show no error text in DIVA?▼

The code number passed to GererErreurCheck(NNN) is missing from the XXferr file, so the field is blocked but no message displays. Verify with --check NNN, then add the message to your partner-specific XXferr via the standard IHM and re-verify.

Can I modify a standard gtferr or ccferr file to add custom messages?▼

No. Standard XXferr files are read-only by norm; custom messages must live in the partner-specific <prefix>ferr file, which is writable. A custom code found inside a standard file is a norm violation that the --diff mode helps detect.

How do I compare two DIVA error files before a downgrade?▼

Use --diff with the current pack file as A and the standard target as B. The output shows only_in_a codes, which are custom candidates to preserve; never blindly adopt the standard, and merge customs into the partner's own XXferr.

Why not parse XXferr files with regex on raw bytes?▼

Numeric ISAM keys are right-justified with spaces (e.g. 'A 9129'), so a naive regex undercounts massively—2182 versus the real ~4700 codes on a real gtferr. This skill reads actual records via reading-isam-files to avoid losing custom codes.

Can I write error messages directly into the .dhfi binary?▼

No. Records are variable-length, so direct binary writes cause silent corruption. Additions must go through the standard interactive IHM, which updates .dhfi and .dhfd atomically, followed by a --check verification.

Related Skills

Explore More Software Engineering Skills→
AcosmiAcosmi
6

list-dir

List directory contents with file names, sizes, and modification times.

Community
Basic
twentyhqtwentyhq
56.0k

twenty-partner-recap

Summarize Fireflies partner calls and inject recaps as Notes on matching Twenty CRM partner records.

Official
Advanced
amdamd
154

quark-onnx-result-validator

Validate Quark ONNX quantization outputs by checking auxiliary files, initializers, metadata, and QDQ signals.

Official
Advanced
RushuiGuanRushuiGuan

error-msg

Rewrite error messages to describe problem states with subject-first phrasing.

Community
Intermediate