The original contents of this page have become obsolete, go to this page for up-to-date information.
Advice about programming, operations, communications, and anything else I can think of
The original contents of this page have become obsolete, go to this page for up-to-date information.
Today, September 30 2015, marks the end of support for IBM i 6.1. It became available March 21 2008 and has been the second longest supported release of the operating system, for 7 years 6 months and 9 days. You can see a list of all the operating system releases with their dates here.
If you are still using 6.1 you need to think about moving to a later release, as further upgrades and PTFs not available for you.
IBM's notification of the end of support for 6.1 can be found here.
This leaves 7.1 and 7.2 as the only supported releases of IBM i.
Have you ever had one of those "Aha!" moments when, as we say in England, the penny drops when someone says something and you are left thinking: "Why didn't I think of that?" I had one of those moments at the OCEAN user group technical conference during a presentation by Paul Tuohy on embedded SQL in RPG.
I have described before what SQL Views are. If you look at the object attribute it is a "LF", but it is not Logical file. Confused?
I was surfing through IBM's developerWorks website looking for information about a Technology Refresh, TR, when I noticed that pages for IBM i 7.1 TR11 and 7.2 TR3 are now on that website.
On Friday I was asked if I could help with a compilation error for a RPGIII program. When the source was compiled it produced a CPF6301 message, see below, and the programmer could not understand what it meant or how to fix it.
Message . . . . : Program PGM1 in library LIB1 is not created as CPF6301 received. Cause . . . . . : Compile terminated in phase QRGRT at MI instruction number '00000'X with message CPF6301. Text for message is: ERROR IN COMPILER. COMPILE TERMINATED. |
The original contents of this page have become obsolete, go to this page for up-to-date information.
For many releases of IBM i we have been able to put keyword in the H-spec/Control options that are the same as the parameters in RPG's compile options, see here. The same is also available in SQL for RPG objects with embedded SQL, SQLRPGLE.
I have given some examples in the past of using the SET OPTION statement in SQL to turn off commitment control. There are a multitude of other options that mirror options in the SQLRPGLE compile commands. I am not going to list all of the options in this post as IBM provides them all on their web site, there is a link at the bottom of this article to the page. I am only going to show what I think are the most useful.
This video was produced by COMMON Europe of a presentation given by Aaron Bartell on how Node.js can interface with DB2 and RPG on the IBM i.
The germ for this post came from a comment made by Glenn Gundermann on last week's Display screens of results without having to press Enter:
How would you do it for the times you don't want to lock the keyboard? You might want to have a screen being displayed to allow the user to do actions but if they don't, perform an action after a timeout.
After a bit of playing I have a solution that will have a screen time out if someone does not press a key in a certain amount of time. This is just simple example to demonstrate the method I found. In the example the user will be presented with a screen they can either press Enter, F3 to exit, or do nothing. If they do nothing after two seconds the program will proceed and display a second screen.