Author name: AS400 Decoded

Modernization

AI-Driven Anomaly Detection on IBM i Operational Data: DB2 Statistical Baselines, Python in PASE, Isolation Forest, and Automated Alerting in 2026

/

Build AI-driven anomaly detection for IBM i operational data in 2026: query QSYS2 system views for job and performance metrics, establish DB2 statistical baselines with SQL window functions, install Python and scikit-learn in PASE, train an Isolation Forest model on historical IBM i data, detect real-time anomalies, and trigger automated alerts via email or data queue when anomalies are found.

IFS & File Systems

IFS Permissions and Security on IBM i: CHGAUT, CHGOWN, ACLs, PASE umask, Authority Auditing, and Stream File Security Best Practices in 2026

/

Secure the IBM i Integrated File System (IFS) in 2026: manage stream file and directory authorities with CHGAUT and WRKOBJAUT, change ownership with CHGOWN, apply access control lists (ACLs) using SETFACL and GETFACL in PASE, configure the PASE umask for default creation permissions, audit IFS object access with QAUDJRN, and follow stream file security best practices.

Modern Integrations

IBM MQ Messaging from IBM i: Queue Managers, Channels, MQPUT, MQGET, Triggering, Dead Letter Queues, and RPG Integration in 2026

/

Integrate IBM MQ with IBM i in 2026: create and configure queue managers, define local and remote queues, set up sender/receiver channels, send and receive messages with MQPUT and MQGET from RPG programs, configure MQ Triggering to start IBM i jobs on message arrival, handle dead letter queues, and monitor MQ activity with AMQSPUT and AMQSGET.

Operations & Admin

IBM i Output Queue and Print Management: WRKOUTQ, CHGOUTQ, Spooled Files, CPYSPLF, SNDNETSPLF, PDF Conversion, and Printer Writers in 2026

/

Master IBM i output queue and print management in 2026: create and configure output queues with CRTOUTQ and CHGOUTQ, work with spooled files using WRKOUTQ and WRKSPLF, move and copy spooled files, convert spooled files to PDF with IBM i Transform Services, send spooled files over the network with SNDNETSPLF, and manage printer writers with STRPRTWTR and ENDWTR.

DB2 for i

DB2 for i CTEs and Recursive SQL: WITH Clause, Anchor and Recursive Members, Hierarchical Queries, Bill of Materials, and Cycle Detection on IBM i in 2026

/

Master DB2 for i common table expressions (CTEs) and recursive SQL in 2026: use the WITH clause to name intermediate result sets, chain multiple CTEs for readable multi-step queries, write recursive CTEs with anchor and recursive members to traverse bill-of-materials hierarchies and organisational trees, and detect cycles in self-referencing data on IBM i.

Modernization

ILE RPG String Handling: %SCAN, %SUBST, %REPLACE, %TRIM, VARCHAR Fields, Delimited Parsing, and CCSID-Safe String Operations on IBM i in 2026

/

Master ILE RPG string handling on IBM i in 2026: use %SCAN, %SUBST, %REPLACE, %TRIM, %TRIMR, and %TRIML for text manipulation, declare VARCHAR and VARYING fields for variable-length data, build and parse delimited strings, handle CCSID conversion, and use %CHAR, %INT, and %DEC for type conversion in free-format RPG programs.

Operations & Admin

IBM i TCP/IP Configuration and Troubleshooting: CFGTCP, ADDTCPIFC, NETSTAT, PING, TRACEROUTE, DNS, Virtual Ethernet, and Line Descriptions in 2026

/

Configure and troubleshoot IBM i TCP/IP networking in 2026: use CFGTCP to manage interfaces and routes, add IP addresses with ADDTCPIFC, configure DNS with CHGTCPDMN, diagnose connectivity with NETSTAT, PING, and TRACEROUTE, set up virtual Ethernet between LPARs, and manage Ethernet line descriptions on IBM i.

Modernization

Strangler Fig Pattern for IBM i Application Modernization: Decomposing Monolithic RPG, API Gateway Routing, Incremental Migration, and Coexistence Strategies in 2026

/

Apply the strangler fig pattern to IBM i modernization in 2026: identify seams in monolithic RPG applications, build a facade REST API over legacy RPG program calls, route traffic incrementally from old to new implementations, use an API gateway for transparent switchover, and keep DB2 for i as the shared data layer during coexistence.

Scroll to Top