Coder Legion - Recent posts tagged ibm

IBM iSeries/AS400 Maintenance and Support: Keep Your Business Running

Mon, 12 Oct 2026 16:34:20 +0000

Reliable IBM iSeries/AS400 systems are essential for keeping critical business operations running smoothly. Regular maintenance, proactive monitoring, performance improvements, and timely issue resolution can help organizations reduce disruptions and get more value from their existing infrastructure.

This infographic highlights key areas of AS400 maintenance and support, including system monitoring, software updates, performance optimization, security management, and expert technical assistance. A proactive support approach can help businesses minimize downtime, maintain system stability, manage operational costs, and prepare their legacy applications for evolving business needs.

Explore how a structured maintenance strategy can help your organization maintain dependable IBM i/AS400 operations while supporting long-term business continuity.

Learn more: https://www.damcogroup.com/ibmiseries-as400-maintenance-support

From Napkin Sketch to Reference Architecture: Hardening the Agent Mesh with mTLS and Granite Guardia

Tue, 27 Jan 2026 18:34:00 +0000

In my previous post, we looked at the "Agentic Strangler" pattern — a way to modernize legacy monoliths using the December 2025 IWHI release. But as any architect who has survived a "Thundering Herd" or a JVM lockup knows: connectivity is not the same as security.

A "napkin sketch" architecture becomes a liability the moment an AI Agent attempts an unauthorized write to a core ERP system. To move from proof-of-concept to production, we need a Hardened Foundation.

In this reference architecture, I break down the "Spine" of the Agent Mesh:

The Identity Layer: Moving beyond basic API keys to full mTLS and identity federation.
The Guardrail Layer: Implementing Granite Guardian to intercept and filter model inputs/outputs before they hit the integration server.
The Observability Layer: Integrating CrowdStrike Falcon at the "mesh" level to ensure that agent-to-agent (A2A) communication doesn't become a shadow network.

The Code-Level Reality:

Note: This logic illustrates how a "Shield" policy might evaluate agentic risk at the gateway.*

# Reference logic for validating Agent intent via Falcon MCP
import requests

def shield_preflight_check(agent_intent):
    # The 'Shield' pattern evaluates if the action matches security baselines
    # before the request is routed to the legacy ERP.
    response = requests.post("https://api.falcon.crowdstrike.com/mcp/v1/validate", 
                             json={"intent": agent_intent},
                             headers={"Authorization": "Bearer ${FALCON_TOKEN}"})
    
    validation = response.json()
    return validation.get("is_safe", False)

Why it matters for IWHI Architects: We aren't just building pipes anymore; we are building the "Sovereign Core" for the enterprise.

Read the full technical breakdown on my blog here and join the live discussion on LinkedIn.

The Protocol of Doing: Why "Chat" is Over and "Agency" Has Begun

Wed, 24 Dec 2025 03:39:31 +0000

Introduction: The "Doing Problem"
We have officially exited the "Chat Phase" of AI. For the past two years, we treated LLMs like brilliant consultants trapped in a glass box—great at answering questions, writing poetry, or debugging snippets. But the moment we asked them to do something—log into SAP, update a PO, or restart a server—the architecture collapsed.

We hit the "Doing Problem."

LLMs are born context-blind. They don't know your schema, your security policies, or that your legacy mainframe requires a specific correlation ID header. To fix this, developers started hardcoding fragile "tools" into their agents, creating a maintenance nightmare.

The solution isn't better prompts; it's better architecture. We need a "TCP/IP moment" for AI—a standard way for intelligence to connect to infrastructure.

The Missing Piece: A "Global Catalog" for AI
If you want an agent to act safely, you can't just give it an API key and hope for the best. You need a Global Catalog—essentially a DNS for enterprise capability.

Instead of an agent guessing how to interact with your systems, it queries a centralized metadata layer.

Agent: "I need to update a customer address."
Catalog: "I have a Salesforce Update Action and an SAP Customer BAPI.
Here are the schemas and the required permission scopes for both."

This solves the N×M Integration Problem (N models connecting to M tools). By standardizing the metadata of actions and triggers, you create a unified interface. The agent doesn't need to know the specifics of the SAP BAPI; it only needs to know the Catalog Schema.

The "Immune System": Why You Need an AI Gateway
Deploying agents without a governance layer is a security disaster waiting to happen. This is the "Shadow AI" crisis: junior devs calling OpenAI directly from production services, potentially leaking PII.

A robust AI Gateway acts as a reverse proxy for intelligence, handling:

Rate Limiting: Prevents "loops of death" where two agents argue and rack up a $50k bill.
Response Caching: Serves repeated answers from memory to slash API costs.
PII Redaction: Automatically detects and masks sensitive data (like SSNs) before it ever leaves your perimeter.

The Mechanics of Execution
To make agents actually work, we need to move beyond "text-in, text-out" and focus on the "hands" of the system:

Flow Services as APIs: Logic should be decoupled from the agent. The agent shouldn't write the SQL query; it should call a deterministic Flow Service that handles the query safely.

Private Network Connections: Your agent needs to reach "dark data"—resources sitting inside private VPCs or on-prem data centers—without traversing the public internet.

Conclusion: The Boring Revolution
The future of AI isn't just about smarter models; it's about boring, reliable plumbing. It's about LDAP integration, metadata synchronization, and private network links.

We don't need another chatbot. We need a nervous system. We need a way to tell an AI, "Fix the supply chain bottleneck," and have it strictly, securely, and correctly identify the endpoint, authenticate, and execute the fix—all while being governed by a central platform.

For a full technical deep dive into how IBM webMethods is implementing this architecture, read my original article: The Protocol of Doing.

DB2TUI a minimal DB2i IDE running on AS/400 systems - Python

Fri, 19 Dec 2025 09:00:10 +0000

The first version of DB2TUI, a minimal TUI SQL IDE for DB2 databases on AS/400 is live. This project started as a side exploration, but I wanted to release it early—even without all the planned features—because real-world feedback matters more than perfection.
Why? Life (and daily obligations) happens, but progress shouldn’t wait. This initial release lets you:

✔ Navigate libraries and tables effortlessly

✔ Run SQL commands or scripts with keyboard shortcuts

✔ Handle large datasets with paging
It’s not everything I dreamed of yet, but it’s usable, practical, and ready for testing. And yes, I’m already working on making it more powerful—think smarter workflows, better error handling, and features that save you time.
Try it out, break it, and tell me what you think! Your input will shape what comes next.
https://github.com/tsgiannis/DB2TUI

Video Preview : https://www.linkedin.com/feed/update/urn:li:activity:7404966242190864385

PS I'd love some feedback if it works on your AS/400