skills/message-handling/SKILL.md
Read and analyze message queues, system history log, reply lists, and message file definitions on IBM i via SQL services. Use when user asks about: (1) reading QSYSOPR or other message queues, (2) searching the system history log (QHST), (3) finding high-severity messages, (4) viewing the system reply list, (5) looking up message definitions (CPF, MCH, SQL messages), (6) message severity analysis, (7) replacing DSPMSG, DSPLOG, WRKMSGQ commands, or (8) any message handling or troubleshooting task.
npx skillsauth add ajshedivy/ibmi-agent-skills message-handlingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read and analyze message queues, system history log, reply lists, and message file definitions using SQL services from QSYS2.
The ibmi CLI is the primary tool for executing message queries. Set SKILL_DIR to this skill's installed location (the directory containing this SKILL.md file):
# SKILL_DIR = directory containing this SKILL.md
# Examples: ./skills/message-handling, ~/.claude/skills/message-handling
# List all message handling tools
ibmi tools --tools "$SKILL_DIR/tools/" --toolset message_handling_default
# Run a specific tool
ibmi tool read_message_queue --tools "$SKILL_DIR/tools/"
# Ad-hoc SQL for custom queries
ibmi sql "SELECT * FROM QSYS2.MESSAGE_QUEUE_INFO WHERE MESSAGE_QUEUE_NAME = 'QSYSOPR' AND MESSAGE_QUEUE_LIBRARY = 'QSYS' FETCH FIRST 10 ROWS ONLY"
ibmi tool read_message_queue --tools "$SKILL_DIR/tools/"
ibmi tool read_high_severity_messages --tools "$SKILL_DIR/tools/" --severity-min 40
ibmi tool search_history_log --tools "$SKILL_DIR/tools/" --search-term CPF1124
SELECT MESSAGE_ID, MESSAGE_TEXT, SEVERITY
FROM QSYS2.MESSAGE_FILE_DATA
WHERE MESSAGE_FILE = 'QCPFMSG'
AND MESSAGE_FILE_LIBRARY = 'QSYS'
AND MESSAGE_ID = 'CPF1124';
SELECT SEVERITY, COUNT(*) AS MESSAGE_COUNT
FROM QSYS2.MESSAGE_QUEUE_INFO
WHERE MESSAGE_QUEUE_NAME = 'QSYSOPR'
AND MESSAGE_QUEUE_LIBRARY = 'QSYS'
GROUP BY SEVERITY
ORDER BY SEVERITY DESC;
The tools/message-handling.yaml file provides 8 ready-to-use tools:
| Tool | Description |
|------|-------------|
| read_message_queue | Read messages from any message queue (defaults to QSYSOPR) |
| read_high_severity_messages | Messages filtered by minimum severity level |
| get_history_log | System history log entries with severity filter |
| search_history_log | Search history log by message ID or text |
| get_reply_list | System reply list entries for automatic responses |
| search_message_file | Look up message definitions by ID or prefix |
| count_messages_by_severity | Message count distribution by severity level |
| get_joblog_info | Job log messages for a specific job or the current job |
ibmi tool <tool_name> --tools "$SKILL_DIR/tools/" # Execute
ibmi tool <tool_name> --tools "$SKILL_DIR/tools/" --dry-run # Preview SQL
ibmi tools show <tool_name> --tools "$SKILL_DIR/tools/" # View details
tools
Query, monitor, and analyze jobs on IBM i using SQL table functions via the ibmi CLI. Use when user asks about: (1) finding jobs by status, user, subsystem, or type, (2) monitoring active job performance (CPU, I/O, memory), (3) detecting long-running SQL statements, (4) analyzing lock contention, (5) checking job queues, (6) scheduled jobs, (7) job logs, (8) replacing WRKACTJOB, WRKUSRJOB, WRKSBSJOB, WRKSBMJOB commands, or (9) any IBM i work management task.
testing
Monitor IBM i system health including CPU, memory, disk, ASPs, system limits, and network status via SQL services. Use when user asks about: (1) CPU utilization or system status, (2) memory pool sizes or page faults, (3) disk capacity or ASP usage, (4) system limits approaching thresholds, (5) TCP/IP connections and network status, (6) system activity overview, (7) replacing WRKSYSSTS, WRKDSKSTS, WRKTCPSTS commands, or (8) any system health monitoring task.
development
Monitor and analyze IBM i storage resources including ASPs, disk units, temporary storage, user storage consumption, and NVMe devices via SQL services. Use when user asks about: (1) ASP capacity, usage, or health, (2) disk unit status or I/O performance, (3) temporary storage consumption by jobs, (4) storage used per user profile, (5) NVMe device health, (6) IASP vary operations, or (7) replacing WRKDSKSTS, WRKSYSSTS storage info, or WRKSTG commands.
testing
Manage and analyze spooled files, output queues, and printer configurations on IBM i via SQL services. Use when user asks about: (1) listing or searching output queues, (2) viewing spooled file entries by queue, user, or status, (3) reading spool file content, (4) identifying top spool consumers or old spool files, (5) printer file definitions, (6) spool storage analysis, (7) replacing WRKSPLF, WRKOUTQ, WRKOBJLCK commands, or (8) any spool file management task.