Product Forums

If you'd like to see the new capabilities in action—including demonstrations of the new IFS Connector, AI Tuner, Replication Group Splitting, and AI-Powered Static Code Analysis—watch the full Q2 2026 IBM i Portfolio Update webinar recording at the bottom of this post.In our latest Q2 2026 webinar, we showcased new innovations spanning Rocket API, Rocket Modern Experience, Rocket iCluster, and Rocket DevOps. These enhancements are designed to help customers unlock more value from their IBM i environments while accelerating modernization efforts and reducing operational complexity. Continuous Modernization: Expanding What's PossibleNew IFS Connector for Rocket APIOne of the most requested enhancements from customers is now available in Rocket API 10.6.3: the new Integrated File System (IFS) Connector.With this capability, organizations can build secure REST APIs that directly read from and write to IFS files on IBM i.This opens the door to a wide range of automation scenarios:Expose fil

Wenn Sie die neuen Funktionen in Aktion sehen möchten – einschließlich Demonstrationen des neuen IFS Connectors, des AI Tuners, der Replication Group Splitting-Funktion und der KI-gestützten statischen Codeanalyse – sehen Sie sich die vollständige Aufzeichnung des IBM i Portfolio Update Webinars für Q2 2026 am Ende dieses Beitrags an.In unserem aktuellen Webinar zum zweiten Quartal 2026 haben wir zahlreiche Innovationen für Rocket API, Rocket Modern Experience, Rocket iCluster und Rocket DevOps vorgestellt. Diese Neuerungen helfen Unternehmen dabei, mehr Wert aus ihren IBM i-Umgebungen zu gewinnen, Modernisierungsprojekte zu beschleunigen und die operative Komplexität zu reduzieren. Continuous Modernization: Neue Möglichkeiten für IBM iNeuer IFS Connector für Rocket APIEine der am häufigsten nachgefragten Erweiterungen ist jetzt in Rocket API 10.6.3 verfügbar: der neue IFS Connector.Mit dieser Funktion können Unternehmen sichere REST-APIs erstellen, die direkt auf Dateien im Integrated

Si desea ver las nuevas funcionalidades en acción, incluidas demostraciones del nuevo IFS Connector, AI Tuner, Replication Group Splitting y AI-Powered Static Code Analysis, vea la grabación completa del seminario web de actualización de la cartera de IBM i del segundo trimestre de 2026 al final de esta publicación.Durante nuestro webinar de actualización del segundo trimestre de 2026 presentamos nuevas capacidades para Rocket API, Rocket Modern Experience, Rocket iCluster y Rocket DevOps. Estas innovaciones ayudan a las organizaciones a extraer más valor de sus entornos IBM i, acelerar la modernización y reducir la complejidad operativa.  Modernización Continua: ampliando las posibilidades de IBM iNuevo conector IFS para Rocket APIRocket API 10.6.3 incorpora el nuevo Conector IFS, que permite crear APIs REST para leer y escribir directamente en archivos del Integrated File System (IFS) de IBM i.Entre sus beneficios destacan:Exposición de procesos basados en archivos mediante APIs REST

The Tools for AI‑Ready Feeds with No Drama: The Complete RDRS-Powered Templates + KPI Starter Pack Want AI you can trust? Stop feeding it mystery data.Standardize your CDC feeds like products: owner + meaning + controls + SLAs + validation + ops.NOTE: This final step does not introduce new requirements.If you’ve worked through the earlier shifts—even for a single Tier‑1 feed—you already have everything you need. The Trusted Feed 1‑pager and KPI starter set simply assemble what you’ve already defined into one place, so you can answer a harder question with confidence: Is this a feed we trust enough to power AI?Trusted Feed 1‑pager (minimum fields): This 1‑pager is a practitioner‑owned contract (L2) that brings together what RDRS provides at the replication layer (L1) with validation, governance, and operations implemented downstream (L3).Source → target(s), pattern, tier Owner + on-call Keys + delete semantics + caveats (what the data means) SLAs (lag/success/errors/validation/recon) Ta

Shift 5: Ops Guardrails — Production AI Needs Production Ops If It Pages at 3am, It’s telling you it needs guardrails, not better heroics. If your AI depends on CDC and your CDC depends on manual babysitting… your AI is not “production.” It’s a live demo with payroll.RDRS exposes the operational signals required to build guardrails (L1), but deciding what to alert on, who responds, and how recovery works is a practitioner responsibility outside of RDRS (L2), typically implemented using external monitoring and incident tooling (L3).What RDRS Contributes (Ops Guardrails)Operational signals (L1) Replication status End‑to‑end lag Apply / replication errors Replication controls (L1) Start / stop processes Restart after failure Controlled recovery Automation surfaces (L1) REST APIs for status REST APIs for process actions Failure characteristics (L1) Observable Restartable Diagnosable RDRS provides the signals and control surfaces; guardrails like alerting, runbooks, and escalation

Shift 4: Change-Resilient Pipelines — Meaning changes break AI faster than BI Why this shift matters: Even when RDRS correctly replicates schema changes (including DDL where supported), AI fails when change meaning, compatibility, and consumer impact are not explicitly managed—making change resilience a critical practitioner responsibility beyond CDC mechanics.Make Change Boring: Contracts, Versions, and Zero SurprisesBI complains when schemas change. AI hallucinates confidently when meanings change.Both are bad. One is sneakier.What RDRS contributes:Replicates DDL changes where supported (L1) Preserves change order and integrity at the mechanics level (L1) Ensures changes are not silently dropped during replication (L1)That’s it — and that’s enough.Minimum change resilience per Tier‑1 feed (L2)Document grain + keys + delete semantics (yes, really) Publish a simple change policy (who approves, timeline) Define evolution rules (new columns/type changes/renames) Version breaking changes

Shift 3: Sovereignty by Design — AI + Replicated Data Without Controls is the Fast Track to Compliance FinesCDC makes data accessible. AI makes it usable.That combo is powerful—and dangerous—without guardrails because you’ve just turned sensitive data into something that can be searched, summarized, and repeated everywhere—in seconds.What RDRS contributesSecure, controlled data movement (L1) Explicit source → target paths (L1)RDRS provides the mechanics of controlled data movement (L1); defining what is allowed, where data may land, and under what conditions is a practitioner responsibility outside of RDRS (L2). That responsibility is enforced through a small set of explicit sovereignty controls for AI‑critical feeds.Minimum sovereignty controls (Tier‑1 / AI-critical)Classify the feed (Public/Internal/Confidential/Restricted + PII flags) Enforce masking/tokenization downstream where required Ensure audit logging + retention exists at the target Define an exception/break-glass processPr

Shift 2: Standardize Bulk and CDC Patterns— Because AI at Scale Can’t Live on Bespoke FeedsIf Every Feed Is Special, None of Them Are ReliableAI doesn’t scale on bespoke feeds. It scales on repeatable patterns and a predictable operating model.Pick 2–3 RDRS-supported pattern familiesInitial bulk load followed by continuous CDC Capture once, replicate to multiple targets  Continuous synchronization/coexistence patterns RDRS supports these replication patterns, but selecting which patterns are allowed and enforcing consistency across teams are practitioner responsibilities outside of RDRS. That consistency is enforced through an explicit feed‑level contract (L2)*.Standardize the “AI-ready contract” per feed (minimum)Keys + delete semantics Tier + SLAs (lag + correctness) Owner + on-call Validation bundle What changes trigger versioning Kill click-ops: Use RDRS REST API for light orchestration: automate routine tasks you currently click through in the dashboard (health/status checks, proc

Shift 1: Make CDC Trustworthy (SLAs + Validation) — Because AI Hates “Maybe Data”If your only metric is “job running,” your AI is training on hope and good intentions.So let’s start with the right signals. RDRS gives you deep operational information:Process status and lifecycle (L1) Latency, throughput, and replication statistics (L1) Error and failure reporting (L1)Trust starts by putting these on the scoreboard.Start with a handful of SLAs you can actually measure, then back them up with target-side validation that catches problems before your users (or your AI). These are the minimums to move from “it’s running” to “it’s reliable.”SLAs (pick 3–5): Defining and operating to these SLAs is a practitioner responsibility (L2); RDRS provides the signals needed to measure them.P95 end-to-end lag ≤ X minutes (AI use cases usually need tighter) Success rate ≥ Y% Apply errors ≤ Z/day Process restarts/day Time above lag thresholdThese are RDRS‑observable metrics.Target-Side Validation (Not Per

This series is written for data integration pipeline owners and practitioners who leverage Rocket Data Replicate and Sync (RDRS). While RDRS plays a critical role in that journey by providing high‑fidelity, observable replication mechanics, trusted enterprise data integration requires more than replication alone. It requires clear ownership, repeatable patterns, explicit contracts, operational guardrails, and disciplined interfaces with downstream platforms. It’s about everything it takes to deliver reliable, always‑on data integration at scale beyond “it worked in the demo.”To keep responsibilities clear, the series explicitly distinguishes between:What RDRS provides (replication mechanics, telemetry, and control surfaces) What data integration and CDC pipeline owners must define and operate around RDRS to make outputs trustworthy What is implemented downstream using non‑RDRS platforms and toolsEach post covers one of five shifts:Operational Trust: knowing what’s late, broken, or fall

We recently released ChangeMan ZMF 8.3.2 and on 5th May, 2026 we will have a live webinar where we will review a healthy sample of the new features, as well as providing an overview of other key capabilities.In addition to the feature review, this time will also be used to give an update of the roadmap and upcoming events. These include the Customer Advisory Board and planned Customer-Facing Sprint Reviews for the coming months.The presentation will be followed by a live Q&A.Can’t attend live? We’ve got you covered. Be sure to register and we’ll make sure you get the recording link. Register Now

Why are Data Integration Practitioners Feeling the Ground Shift?If your job includes being on call, you’ve already learned an important rule:Anything that only works in the demo will eventually page you.Usually at 2:47am…right after a “minor” upstream change…with the extremely helpful alert message:“job running”AI hasn’t changed that rule. It just made the blast radius bigger.Most AI failures don’t explode loudly. They quietly deliver outputs built on late, partial, or misunderstood data—and do it with complete confidence. When someone finally asks “can we trust this?”, the answer usually traces back to the same place it always has: The data pipelines everyone assumed were fine.Because you’re responsible for CDC-powered data integration and, unless you operate (or manage) Rocket® Data Replicate and Sync (RDRS) specifically—this should feel uncomfortably familiar. AI isn’t creating new problems. It’s dragging existing ones into the spotlight.This post isn’t a checklist or a tutorial. It

You’ve come to the right place, to stay on top of C\Prof updates and articles on product content and capabilities.Click the Subscribe button at the top right corner of the  C\Prof | Rocket Forum, to get notified of all new updates.Note: To modify your notification parameters (what activity you get notified of), please go to your profile -> Edit profile -> Notifications.A step by step guide is available here. 

Hello and welcome to the new Rocket Mainframe Optimization Community Forum! Whether you are new to the world of the mainframe or you are a 40-year veteran we’re excited to have you join this space dedicated to Rocket Software’s TMON and C\Prof products and related technologies. This forum is designed for technical users like you to connect, share insights, and stay ahead in mainframe performance optimization. As a regular visitor and participant, you’ll benefit from:Access to Expertise: Learn from peers and Rocket Software specialists. Latest Updates: Stay informed on product roadmaps and related technologies. Interactive Discussions: Exchange ideas, troubleshoot challenges, and share best practices. Community Engagement: Participate in polls, contribute suggestions, and help shape future enhancements. Please browse the forum and check out the links and material currently posted. Expect this material to grow and discussions to evolve over the coming weeks so check back regularly to see

If your saved view name reads like a filing cabinet label, no one clicks it. Microcopy is your growth hack: name it like a button people want to press.The formula (keep it simple)Name pattern: [Emoji] [Job to be done] — [Scope or threshold] (Audience if needed) One‑liner: “Why this view exists” in one sentence. Action + payoff.Naming rules that earn clicksLead with the job, not the noun. Action beats category. Keep it under ~30 characters. Truncated names don’t get love. Use consistent emojis. Pick 6–8 and stick to them. Scope it. Add “>30d,” “High,” or “This Week” so expectations are clear. If it’s personal, say so. “(Me)” or “My Queue” prevents confusion.Your emoji shortlist (use sparingly)🔎 find/triage 🚩 risk/attention ✅ done/clean 🧹 cleanup/dedupe 💤 stale/aging 📥 imports ⚙️ ops/system 🧪 test/sandboxBefore/after names with one-linersBefore: Potential Duplicates After: 🧹 Needs Merge — High Why: Highest confidence dupes first; clear 5 in 5 minutes. Before: Validation Errors

It’s a privilege to post the very first message and personally welcome each of you. I’m Pat Kelly, marketing lead for the DataEdge suite of products.You’re here because you get it: Managing mission-critical data from core-to-cloud (and back) without the drama shouldn't be a nightmare of complexity, cost, or risk. That’s our shared mission, and this forum is your new launchpad. This is where the people who are actually doing it—your peers, our experts, and the sharpest minds in data replication, integration, and synchronization—hang out. Let's make your data strategy an unfair advantage!What You’ll Find Here (The High-Value Stuff)Forget endless manuals. We’re all about cutting straight to the solution and driving high-speed, high-value wins:The Cheat Codes (practical resources): You’ll get instant access to product updates, step-by-step how-tos, field-tested runbooks, and tuning tips—the exact patterns our solutions engineers use to save the day. The Squad (peer power): Connect directly

Have questions about the Product Lifecycle?Check out the MV Product Lifecycle FAQ for answers to common questions, and don’t forget to review the MV PLC Handbook for detailed guidance.

MultiValue Product Lifecycle Handbook and FAQ  

Here’s how to make the most of this community resource:Find your way around Accessing the Library In the Mega Menu, look for MultiValue Innovation Library. This is the central page where you’ll find links to all our sub-topics Explore sub-topics From the MultiValue Innovation Library page, you’ll see a roster of all discussions and dedicated links to specific areas: MultiValue Innovation Library Home AI Cloud Containerization HA/DR - Replication MV Integration Server (MVIS) Authorization/Licensing MV eLearning Not sure where to post? If you’re unsure which topic is best, you’re welcome to post your entry right on the Home page. Our moderators will gladly transfer it to the appropriate topic page for you! Stay in the loop!Subscribe to any (or all!) topic pages, or just the Home page, to get notified whenever someone posts something new You’ll find the Subscribe button at the top right of each pageGet involvedBrowse what others have posted—feel free to comment, ask q

All MV Innovation Library entries are moderated, reviewed on a weekly basis. Click the New Post button in the top right on any page Select your post type. We recommend the “Discussion” post type Add a clear title: Give your Entry a descriptive title so others can gain an at-a-glance understanding of its purpose or what it's about Write your post and attach files (.pdf, .doc, .zip, .png, and more).  Please note that file uploads in the community don’t support special characters such as @, #, $, %, ^, +, etc. The file size must be under 5MB Choose the forum: MultiValue Innovation Library Home or any of the topic pages: AI Cloud Containerization HA/DR - Replication MV Integration Server (MVIS) Authorization/Licensing MV eLearningNot sure where to post? If you’re unsure which topic is best, you’re welcome to post your entry right on the Home page. Our moderators will gladly transfer it to the appropriate topic page for you!Add or select tags  Hit Post!