In ancient times, Rob‘s employer didn’t have its own computer; it rented time on a mid-range computer and ran all its jobs using batch processing in COBOL. And in those ancient times, these stone tools were just fine.
But computing got more and more important, and the costs for renting time kept going up and up, so they eventually bought their own AS/400. And that meant someone needed to migrate all of their COBOL to RPG. And management knew what you do for those kinds of conversions: higher a Highly Paid Consultant.
On one hand, the results weren’t great. On the other, the code is still in use, though has been through many updates and modernizations and migrations in that time. Still, the HPC’s effects can be felt, like this block, which hasn’t been touched since she was last here:
// CHECK FOR VALID FIELD
IF FIELD1 <> *BLANKS AND FIELD1 < '1' AND FIELD1 > '5';
BadField1 = *ON;
LEAVESR;
ENDIF;
This is a validation check on a field (anonymized by Rob), but the key thing I want you to note is that what the field stores are numbers, but it stores those numbers as text– note the quotes. And the greater-than/less-than operators will do lexical comparisons on text, which means '21' < '5' is true.
The goal of this comparison was to require the values to be between 1 and 5. But that’s not what it’s enforcing. The only good(?) news is that this field also isn’t used. There’s one screen where users can set the value, but no one has– it’s currently blank everywhere- and nothing else in the system references the value. Which raises the question of why it’s there at all.
But those kinds of questions are par for the course for the HPC. When they migrated a bunch of reports and the users compared the results with the original versions, the results didn’t balance. The HPC’s explanation? “The users are changing the data to make me look bad.”
[Advertisement]BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!
Source: Read MoreÂ