COMMON POWERUp 2026

**update**  Tegratecs apologizes for their speaker representative not being able to make it to the conference.  Rexford is still dealing with 2 significant and separate dental issues that came up over the last two weeks.

Conference attendees are entitled to the presentation PDF and attachments and USB stick (for in person attendance or by request), but since the session was cancelled, COMMON has removed the links from view. So please contact Tegratecs for these resources based on your interest. If you were signed up for this session prior to the cancellation, everything but the actual USB stick contents should still be visible and enabled for download.
------

If you have internal Change Management and/or DevOps functions that need to handle SQL PL Stored Procedures or a dual source model, then this session will be of interest to you.  During this presentation, we’ll delve into programming specifics of how challenges were overcome and show examples.  The presentation will attempt to narrow down the conflicting techniques involved with storing source in the IFS versus native source files, and for pulling (extracting, generating) source from the SQL PL *PGM object. Pulling the source from the object is, at various times, something that is pretty much necessary for SQL PL stored procedures and views.  We’ll cover the different style of source and object handling (and source versus object precedence) probably required for SQL PL stored procedures (*PGMs with CLE attribute) in our custom C/M and DevOps commands.  This turned out to be quite a bit different than what we were doing before when distributing incremental updates to our accounting package or customer environments, because previously (1) source always took precedence over object, (2) source never needed to change during migration and (3) we were able to have a tight source code version level indicator in the object metadata.

Come to the presentation to find out why we thought it easier to store view and procedure source in both the IFS and traditional source files, at least during the first round of production IFS source implementation. Hear also how we managed to keep them synchronized, and similarly, how we kept a pretty tight rein on source and object versioning. Checkout, compilation, staging and promotion via a native CLP or *CMD call will be examined and (hopefully) shown to be enhanced and solved to everyone’s liking during the presentation.

Key CLP source code and SQL queries of SQL meta data will be covered in the presentation PDF or attachments available for download to all conference attendees. Some slides with a lot of code will be given to attendees in printed form. Attendees may want to have the attachments available to peruse (on some sort of device larger than a small smartphone) during the presentation in order to gain the most developer level understanding in the quickest manner and to participate interactively.

Several complete programs will be offered to live session attendees on USB stick (that we can't afford to offer unencumbered on Sched). Contact Tegratecs for USB stick if you can't make the live session.

Please feel out a survey if you find any of the downloads useful.

Learning Objectives:

1.  Get to a point where you can weed out the inefficiencies in locating, extracting, editing, compiling or promoting the source and object for your SQL PL Stored Procedures

2. Learn what one ISV and consultancy did to focus C/M and DevOps activities around the object, instead of the source, for SQL PL stored procedures, and to see how one might go about automating ways to help relieve synchronization concerns and reduce manual intervention

Git has become the standard for version control, but moving traditional IBM i source code into Git requires planning, the right tools, and some trial and error. This session walks through a complete migration experience: from the initial planning phase, through the technical steps of exporting source, to resolving issues with members, naming, syncing, and how AI can help. Along the way, we’ll discuss pitfalls, solutions, and strategies for adoption across development teams. Attendees will gain a clear roadmap for migrating to Git and the confidence to start their own journey.

Learning Objectives:

Identify key planning steps needed before migrating IBM i source code into Git, including repository structure, workflow design, and tool selection. Execute a practical migration process — from exporting IBM i source members to resolving naming and synchronization challenges. Recognize common pitfalls during migration (e.g., member-level management, library mapping, and CCSID issues) and apply effective solutions. Leverage AI-assisted tools to streamline source analysis, refactoring, and ongoing Git synchronization. Develop a strategy for team adoption, including training, workflow standardization, and integration with CI/CD or modern IDEs. Build confidence to begin their own Git journey, using a clear roadmap and lessons learned from real-world implementation.

Join me as we explore how to achieve end-to-end automation on IBM i, covering builds, tests, and impact analysis using open source tools (ibmi-ci, Source Orbit, and itest). The session will walk through a practical example of setting up a modern DevOps pipeline in GitHub. Imagine creating a pull request that automatically triggers a build, generates an impact analysis report, runs your test cases, and produces code coverage — with all results sent directly to the pull request for reviewers to see with ease.

Learning Objectives:

• Learn how objects get built from a Git repository • Explore what the modern development life cycle looks like with Git • Learn how to automate your builds, tests and impact analysis with GitHub Actions