Steve Sibley, Vice President, IBM Power Product Management, Steve Will, DE, CTO, and Chief Architect of IBM i, and the IBM i Product Management team of Alison Butterill and Linda Hirsch will take the community through recent updates for subscription and what they mean for clients and users.
Steve Sibley is the vice president of IBM Power Systems Offering Management. Read More
Git Demystified: True Modern DevOps Tooling for IBM i Developers
Many IBM i developers are being asked by their leadership to adopt the same Git-based DevOps tooling used across the rest of their IT group.
But most long-time IBM i developers aren’t convinced that this approach will bear fruit as they haven’t had the opportunity to be exposed to even the fundamental concepts of Git.
So where do you start?
This webinar will explain the basics of Git, tailored for IBM i developers, including:
– IBM’s perspective on Git and modern tooling for the i
– Git principles and how they compare to traditional IBM i methods
– The benefits of using Git for managing your COBOL and RPG source code
– Free resources available to continue your learning
Whether it’s Git-Hub, Azure DevOps, or Bitbucket on your CIO’s mind, an understanding of Git fundamentals will equip you for the discussion. Read More
Announcing the Cloud Migration Acceleration Program with IBM Power Virtual Server Director of Product Management (Power and SAP)
Migrate to the cloud by creating an end-to-end IBM program from pilot and collaborating with Power and cloud migration specialists. Read More
Code for IBM i The Whole Picture: Part 2 Development Environment Bird’s-eye View | IBM i’s New Open Source Development Environment – Eye Magazine | i Magazine アイマガジン
Now, I would like to summarize the scope of Code for IBM i more concretely, focusing on the source code. When making comparisons, consider the coverage of SEU/PDM and RDi together (Chart 3).
Figure 3 Overview of development environment
Now, let’s summarize the source code storage location in the diagram of each tool and the correspondence status for each operation in the table.
(1) Source file
The source files are accessible by all three tools, but there are some differences. △ because Code for IBM i does not provide a prompt function for RPG III and IV. △. Although it is possible to ignore errors and save data, it is not very realistic (Figure 4).
Figure 4 Source file
(2) Source code on IFS
All × because SEU cannot directly modify the source code on IFS. Code for IBM i is △ (Chart 5) for the same reason as for source files.
Figure 5 Source code on IFS
(3) Source code on the development PC
Since SEU is a tool on IBM i, it is of course impossible to access the source code on the development PC, so all ×. Code for IBM i is the same reason as ②, △ (Figure 6).
Figure 6 Source code on development PC
④ Push the source code of development PC to IFS
RDiはIFSプロジェクト機能（リモート・リコンサイラ）を利用して、プッシュ可能。Code for IBM iについては後述（図表7）。
図表7 開発PC上のソースコードをIFSにプッシュ
⑤開発PC のソースコードをソースファイル（メンバー）にプッシュ
RDiは i プロジェクト機能を利用してプッシュ可能。Code for IBM iは不可なので、これだけだとRPG Ⅲのソースコードの保守は不可能との判断になる（図表8）。
図表8 開発PC上のソースコードをソースファイルにプッシュ
⑥コンパイラを実行
RPGの場合、コンパイラは2つ（CRTRPGPGM と CRTRPGMOD）。どの開発環境からも実行することが可能（図表9）。
図表9 コンパイラを実行
⑦IBM iオブジェクトの処理
オブジェクトの一覧表示や、削除などの基本操作はどのツールも利用可能（図表10）。
図表10 IBM iオブジェクトの処理
Gitの利用
Gitについては、前述したようにSEU/PDM環境では利用不可（図表11）。
図表11 Gitの利用
以上の比較を見ると、Code for IBM iはRDiが提供している機能をほぼ網羅している一方、以下が弱いことがわかる。
・プロンプト機能がない
・ローカルのコードを直接ソースファイルのメンバーにプッシュできない
逆を言えば、上記の問題が解決できればRDiの代替案として、Code for IBM iは十分に活用可能ということだ。その可能性も踏まえて、Code for IBM iの使い方を具体的に見ていこう。（Part３へ続く） Read More
Attending and presenting at IBM’s TechXchange conference? Yes, please! Charles Guarino
TechXchange is quickly approaching and with the opportunity to co-present two sessions on my favorite topics, I am super pumped. Meeting again at a conference of this scale never disappoints. Here are just some of the reasons why I am so looking forward to being there. You should be there too! The People First and … Continue reading “Attending and presenting at IBM’s TechXchange conference? Yes, please!” Read More
