Friday Fine-tune: How to discover the creation date of a STORE tape
Rootstock acquires ERP vendor Kenandy

Searching and finding in MPE/iX with MPEX

Searching ManIt's a world where it's ever-harder to find files of value. This week a story aired on NPR about a hapless young man who mislaid a digital Bitcoin wallet. The currency that was worth pennies eight years ago when he bought it has soared into the $15,000 range. Alas, it's up to the Bitcoin owner to find their own money, since the blockchain currency has no means for recovery. Another owner in the UK a few years back, James Howells, lost millions on a hard drive he'd tossed out. A trip to the landfill to search for it didn't reward him, either.

Being able to locate what you need on your HP 3000 involves going beyond the limits of MPE/iX. Searches with the Vesoft utility deliver more results and faster than any native capabilities.

Terry Floyd of the Support Group suggested MPEX as a searching solution. "MPEX with wildcards and date parameters is what I use for search," he said, "for instance"  

%LISTF @xyz@.@(CREDATE>12/1/2017),3    


%PRINT @.@;SEARCH="Look for this"

Seeing MPEX come up as a solution for search reminded us of a great column from the Transition Era for the 3000. Steve Hammond wrote "Inside Vesoft" for us during that time when 3000s not only continued to hold data for organizations, but production-grade data, too.

Gonna find her, gonna find her, Well-ll-ll, searching
Yeah I’m goin’ searching, Searching every which a-way, yeh yeh

— The Coasters, 1957

By Steve Hammond

I have to admit it — I’m a bit of a pack rat. It drives my wife crazy and I’ve gotten better, but I still hold onto some things for sentimental reasons. I still have the program from the first game I ever saw my beloved Baltimore Colts play. On my desk is the second foul ball I ever caught (the first is on display in the bookcase). I have a mint condition Issue 1 of the HP Communicator — dated June 15, 1975 (inherited when our e3000 system manager retired). It tells that all support of MPE-B terminated that month, and the Planning Committee chairman of the HP 3000 Users Group was a gentleman from Walnut Creek named Bill Gates (okay, not that Bill Gates).

My problem is even when I know I have something, I just can’t find it. I had an item the Baseball Hall of Fame was interested in; they had no ticket stub from the 1979 World Series, which I had — seventh game no less. But it took me over two years before I literally stumbled across it.

I wish I could add some sort of easy search capabilities to my massive collection of junk like we have in MPEX.

The most commonly used is the search option in the PRINT command. But there are a couple of other ways to search that I’ve used over the years for different reasons, and we’ll look at those too.

In the olden days, when passwords were embedded in job streams, when we changed passwords, we would have to find every job with the password in it. A long, tedious task that never found all of them. And yes, the ultimate answer was converting to STREAMX, but that’s a column for another month.

When MPEX added the PRINT;SEARCH command, life became much easier and we found many uses for it. As the versions of MPEX evolved, the command gained power. The simplest form is:


This will search for any line with the word “FILE” in it — exactly “FILE”, not “file” or “File” or “fILE”, you get the picture. Easily solved with:

%PRINT @.JOBS.PROD; SEARCH=caseless “file”



Either of those will get you the word “file” in any form.

You can do boolean searches:




The first returns any file that has a line or lines with both FILE and TEMP, the second looks for FILE or RUN and the third looks for files with any lines that contain RUN but do not have PRODPGM.

You can even delimit your searches — let’s say you have a tape drive that you call “DAT”. Well, doing the search


will find the reference to DAT as the tape drive you’re interested in, but as a bonus feature it will also find “DATA”, “DATABASE”, etc. By using the DELIMIT option:


you will find only occurrences of “DAT” with non-alphanumeric characters before and after it. Taking this a step further, you can right and left delimit your search



The first will files with lines containing DBSTORE but not PRODDB, and the second vice versa. You can even add the caseless option to delimited option:

%PRINT @.JOBS.PROD; SEARCH=caseless rdelim “DB”

Caseless can be abbreviated “CL” and delim can be “D”.

But there’s another way you can do searches, which I found very useful - searches that I used out of a LISTF, building an indirect file for later use. You can’t do that with PRINT, because PRINT well, prints the result, showing the occurrence of the string you are searching for. Let’s say we were changing the name of a database — DEVDB to PRODDB. All I really need to know is all the jobs that have the reference to “DEVDB” — I don’t need to see the context of the string, I just need to know the files. And I need to know the fully-qualified name of the file and I want it in a file named INDFILE1.

This is where the file attributes FCONTAINS FSEARCHSTRING and FSEARCHEXP come into play. The second and last are similar because you have to state that there are greater than 0 occurrences in the file (or any value for that matter), but otherwise they all work the same.






As I said, FCONTAINS looks for the existence of that string in a file and basically FSEARCHSTRING does the same thing. But with FSEARCHSTRING, you can do :


which says you want to find a file that has any line with a minimum of three occurrences of “DEVDB”. Why would you want to do that? If you haven’t learned yet that you don’t ask that question, then we need to talk later.

The better question is why the “FSEARCHEXP” attribute? I’m glad you asked. This is the one of these attributes that lets you to a caseless search:


Note the additional set of quotes in there. FSEARCHEXP also lets you do boolean searches, but that’s just getting way too complicated!

The final question is why did I do it this way? If I was going to change a string, I would do an overnight job that found the files that needed to be changed. I would put the output of that process into an indirect file in the LISTF,6 output format (fully qualified file name). I would then use the indirect file as input for the job or process to change the string.