Pages

▼

Thursday, November 12, 2026

A couple of new IBM performance guides are available

IBM have published a couple of interesting guides in the past few days.

The first is the biannual update to the "IBM i on Power - Performance FAQ". This guide provides us, IBM i developers and administrators, with tips on how to measure and improve the performance of our IBM Power servers, IBM i partitions, the Db2 database, and the programs that run within it.

You can download the document from here.

The second is the "IBM Power11 performance optimization for IBM i" which endeavors to help us minimize the CPU utilization of our IBM i applications on IBM Power servers.

This document can be downloaded here.

I download these guides and read the passages I feel are relevant to my situation. I recommend you do the same with both of these.

Wednesday, November 11, 2026

Identifying IBM's libraries

I have always wanted the best way to identify which libraries, on the IBM i partition I was using, belong to IBM. I had come up with doing things like considering all libraries that start with "Q", "SYS", and "#". But that was never a guarantee to separate IBM's from others' libraries.

IBM gave me a way to identify their libraries, using the SQL OBJECT_STATISTICS table function. It allowed me to identify most of the IBM libraries, but not all. I have made some additions to what they told me to make it mostly work.

I need to use three columns from OBJECT_STATISTIC results:

  • OBJNAME:  Name of the returned object, which in this case will be a library
  • OBJDEFINER:  User profile who created the object
  • OBJNAME:  User profile that owns the object

IBM told me that any libraries created by the profiles QLPINSTALL and *IBM would allow me to identify what should be considered IBM libraries. On further investigation on several IBM i partitions I have found what I would also consider to be IBM libraries that were created by the user profile QSYS, or are owned by QSYS.

The statement I came up with is:

Tuesday, November 10, 2026

RPGPGM.COM-unity grows at TechXchange

At IBM’s TechXchange I had the opportunity to expand the RPGPGM.COM-unity. You can see who joined, and I gave ribbons to, here. I am sure you will recognize some of the faces and names of the people.

If you see me at an IBM i event, feel free to come over and say "Hi". In all likelihood I will have a RPGPGM.COM-unity ribbon on me, and you can join the community. All I ask in return is a photograph of you with it.

If you would like to learn more about the RPGPGM.COM-unity click here.

Wednesday, November 4, 2026

New parameters added to JOBLOG_INFO makes sorting and selecting so much better

One of what, IMHO, is the best modifications in the latest Technology Refreshes, IBM i 7.6 TR2 and 7.5 TR8, has been the new parameters added to the JOBLOG_INFO table function. These being:

  • MESSAGE_ORDER:  The order of the results returned
  • MESSAGE_LIMIT:  The number of messages to return in the results
  • MESSAGE_TIMESTAMP:  All messages that are equal or greater (newer) than the entered timestamp

I can view all of my job's joblog using the following SQL statement:

Monday, November 2, 2026

November’s presentations

I will be making two presentations this month, November, both of them online.

The first is for the Central Texas IBM i User Group. This month's meeting is on Tuesday November 10 at 6:30 PM (CT). I will be giving two 30-ish minute presentations, that proved very popular at COMMON PowerUp earlier this year:

  • Designing your own CL commands
  • Using SQL triggers to track file changes on IBM i

As I said the meeting is online, and free. You register from their web page here.


The following week, Tuesday November 17 starting at 2:00 PM (CT), I will be talking to the QUSER group of Minnesota. I will be making two presentations here too:

  • RPG Built-in Functions You Should Be Using (50-60 minutes)
  • RPG Arrays – Modern Features You Should Be Using (30-ish minutes)

This online meeting is only open to members of QUSER, who can register at their website here.