One of the things that RPG isn’t particularly good at is string scanning & manipulation.
Many other programming languages support using Regular Expressions (or regex, as they are often referred to). Java, PHP, Node.JS, Python, & Perl have support for regex’s built in.
Regular expressions are a very powerful tools for parsing, analyzing, and manipulating text. It should be noted, however, that with such power also comes the possibility for complexity. Some regular expressions can get VERY VERY complex. See the end of this post for a VERY complex expression.
A true regex master can create a functioning expression that is indistinguishable from modem line noise. – Unknown (maybe me)
As a Mac user, I sometimes find my self needing to use Windows 10. To do this, I run it using the Parallels virtual machine manager.
One thing that bothered me, when was running Windows in full screen mode, was that the MacOS dock would pop up when I moved the mouse pointer to the Windows task bar.
I would have to move the mouse pointer away from the dock, let it drop back down, and then move the pointer back to the Windows task bar without going to the bottom of the screen.
I’ve started a personal open source project. Something I’ve been meaning to do for quite a while.
The project is PCMLTOOLS — utilities designed to make working with the Java Toolkit for IBM i (JT400)’s Program Call Markup Language (PCML) easier to use.
The first tool is a Java class to allow a developer to retrieve a ProgramCallDocument object (which is normally generated from PCML) directly from a *PGM or *SRVPGM object who’s modules were compiled with the PGMINFO(*PCML:*MODULE) option.
The URL for the PCMLTOOLS project is https://github.com/fallingrock/pcmltools.
This is the first open source project that I’ve started … and I’m still getting the hang of github, so it may be rough around edges.
This is a general warning for anyone who owns or manages multiple internet domains.
If you have ever used a domain name, and switched to another one, you should never let the original domain expire.
The reason is, there are nefarious people out there who will buy that abandoned domain, put up content they scraped from an internet archive, and add links to malware or scam sites.
This happened to Ginny’s church’s web site (which I was hosting). They had a domain that had been used but was abandoned in favor of a new domain. Because the old domain wasn’t being used, and all the content had been migrated over, we decided to save some money and stop paying for it.
About a year after that, the domain popped up on the internet as a local church. I was confused by this and looked at the site. It was an almost exact copy of the last version that had been published … except it had links that tried to redirect people to scam sites.
The only thing we could do is file a complaint with the domain registrar. I’m not sure if they ever took it down.
Now, if I have a domain that I had used, I keep paying for it and just set it to do a permanent redirect to the new domain.
The only real exception to this is when I bought a domain with the intention of using it, but never got around to it. In those cases, I just let it lapse, because it’s not going to have content to mimic.
This is a general warning about using the CHGCMDDFT command to change the default value of command parameters for commands in QSYS.
There are a number of reasons not to change parameter defaults on commands in QSYS…
- Any time you upgrade your systems, those default parameter changes will be lost because the commands are completely replaced.
- Although you can identify what commands have had parameter defaults changed, there is no indication of WHAT parameter defaults were changed on a command. To identify what commands have had defaults changed display the command objects description (DSPOBJD) with DETAIL(*SERVICE). If an object has had the parameter defaults changed, the APAR ID will show ‘CHGDFT’.
- Third party products may be expecting commands to have the IBM provided default values. Because 3rd party products usually have to work on a number of IBM i versions, it’s impossible for vendors to specify a specific value for every parameter. New parameters are added with almost every release.
A Better Approach
A better approach would be to create a library to hold copies of the commands you want to modify …
- Create a specific library to hold customized commands
- Add that library to the QSYSLIBL system value above QSYS
- Duplicate the *CMD objects into that library
- Change the default parameter values on the commands in that library.
This way the commands in QSYS are left with the IBM provided default parameter values. Since the custom command library is above QSYS in the system library list, applications that reference those command (that don’t qualify the command to QSYS), will use the modified command.
I like to create a simple CL program that does the work of deleting existing commands from the custom command library, duplicate the command from QSYS, and modifies the command parameter defaults. Not only does this make it easy to recreate the custom command parameter defaults when you do an OS upgrade, it documents what parameter defaults have been made.
You may be tempted to use the CRTPRXCMD to create a ‘proxy command’, that points to the original command, and change the defaults on the proxy command.
DO NOT DO THAT!
A proxy command isn’t a stand alone object that is independent of the actual command. It’s just a pointer to the real command.
Any real changes you make to a proxy command will actually be made on the real command.
Here’s a very simple example of a CL that will repopulate a custom command library with modified default parameter values.
DCL VAR(&LIB) TYPE(*CHAR) LEN(10) VALUE('CUSTCMD')
DCL VAR(&CMD) TYPE(*CHAR) LEN(10)
/* SAVLIB must default to *PRV target release for compatiblity */
CHGVAR VAR(&CMD) VALUE('SAVLIB')
CHGCMDDFT CMD(&LIB/&CMD) NEWDFT('TGTRLS(*PRV)')
CRTDUPOBJ OBJ(&CMD) FROMLIB(QSYS) OBJTYPE(*CMD) TOLIB(&LIB)
One of my favorite techniques for passing structured bulk data around is using datas queue’s with the format of the data defined in an external data structure.
In RPG this is very easy … you defined a data structure using the EXTNAME keyword.
dcl-ds stuct1 extname('EXTDS1') end-ds;
Then you just use the data structure name when calling the QRCVDTAQ or QSNDDTAQ api’s and the data will be nicely mapped into the appropriate structure field.
But what if you wanted to allow a Java application to consume or populate the data queue?
The folks at Amazon Lightsail have added a new, much needed, feature: Automatic snapshots.
Shapshots are a way of creating an exact backup of your Lightsail instance. You can use this snapshot to move the instance to another region, move it to the more flexible EC2 platform, or just create a new instance based on an existing one.
Previously, the only way to automate snapshots was to create AWS Lambda functions with Cloudwatch triggers. I was able to get that setup, but it took quite a while.
Every now and then someone asks me how I’ve got blogs setup on my servers.
As such, I’ve decided to create this post that documents my setup and why I made some of the decisions I did.
I’ve been using Amazon’s Lightsail service for quite a while now and, in general, I’m quite pleased with it.
There are, however, a few things they really could improve on.
Recently I encountered a problem with SSL on one of my websites … some web browser could not connect securely.
When I ran a test from Linux, I got the following error:
OpenSSL: error:1408E0F4:SSL routines:ssl3_get_message:unexpected message
After a bit of digging, I found that a recent upgrade to the certbot-auto tool, that creates LetsEncrypt certificates, caused the problem.
The fix was to modify /etc/letsencrypt/options-ssl-apache.conf so that the SSLSessionTickets setting was set to on.