Homesteading

3000-L newsgroup heads for new future

Jeff Kell shutdown
IT staff at the University of Tennessee at Chattanooga in 2014, switching off their last HP 3000

The manager of the university datacenter that hosts the 3000-L mailing list and newsgroup has told members the list will be moved in some way during the months to come. Without sharing a timeline for the changes, technical director Greg Jackson of the University of Tennessee at Chattanooga (UTC) Information Technology said, "UTC will stop support of the list in its present form, as we move to a different delivery method."

"In the fall [of 2019]," Jackson said, "I contacted the moderator of the hp3000 list and let them know that at some undetermined point in the future, UTC will stop supporting the listserv in its present form as we move to a different delivery method. Since this list is still active, when the time comes, we will work with the group to ensure a smooth transition."

News of the movement and rehosting of the biggest archive of 3000 community messaging surfaced after UK users couldn't access the archives. Robert Mills said that when he contacted Jackson about being locked out of the archives, he was told "Over the past few months, there have been several attacks on the listserv that originated from IP addresses outside the US. Therefore, we decided to restrict the ListServ to the US only."

The list's membership count stands at 371. Donna Hofmeister, a support engineer at Allegro and one of the list's moderators, said the community should decide now how the message service and 3000 knowledge archive can move forward.

"Due to the looming changes at UTC," she said in a message, "hp3000-l needs to do something." The archives of the list, which date back to 1994, will "somehow be made available for searching."

"As one of the said moderators," she added, "I think it's only appropriate to ask — do we want hp3000-l (in whatever form it might take) to continue? The amount of traffic (which is around five messages/month) makes it a question that should be asked."

Hofmeister said that "having access to the archives has real value. So my plans are to <somehow> make the archives available for searching. So what do you say? Keep HP3000-L active in some form (I'm leaning towards making it a Google Group) or let it go away when UTC takes down the listserv? In either case, the archive will be available."

Fourteen list members responded quickly to vote for keeping the list alive. Two alternatives emerged as options when the UTC hosting ends as it exists, using the LISTSERV software. Rehosting on groups.io was suggested by Tracy Johnson, while Keven Miller proposed a free version of another listserve program.

"The Lsoft Lite free version supports up to 10 lists, 500 members each," Miller said. "There are a few other lists [whose UTC] archives might be nice [to preserve]. HP9000-L, OpenMPE, and maybe a few hidden lists. I would think that Lsoft Lite would be the easiest to move archives to. But I'm sure there are other open source solutions."


Large Disk patch delivers 3000 jumbo limits

Marshmallows
As the HP 3000 was winding its way out of the HP product lineup, it gained a greater footprint. Storage capabilities grew with the rollout of Large Disk. The effort was undertaken because HP's disk module sizes were doubling in size approximately every two years: 4 GB to 9, 18, 36, 73, 146, and then 300 GB.

The disk project might have never seen its limited release without OpenMPE. The advocacy group that was formed after HP's exit announcement saw the same disk size trend. OpenMPE drove the initiative of "Support future large disks" in the Interex 2003 Systems Improvement Ballot.

Just two years later, Interex was dead. The directive from the 3000 community to HP labs lived onward, though. HP said its investigation found the need for more work to be done to support large disk configurations.

The MPE/iX 6.5 Large File enhancement allowed bigger Files. 6.5 also permitted more disk space in each MPE Group and Account. But several CI commands and utilities were limited in their ability to work with the resulting larger Groups and Accounts. All of these inputs were assessed during the Large Disk investigation and as many as possible were addressed by the Large Disk patches.

So what does Large Disk deliver? The patches provide the following enhancements for MPE/iX 7.5:

• Large Disk includes the ability to attach and use SYSGEN to configure any sized SCSI-2 compliant Disk. MPE/iX uses SCSI-2 protocol to connect to SE, HVD and LVD SCSI Disks as well as Fibre Channel over SCSI. The SCSI-2 standard allows for disks of up to 2 Terabytes. SCSI-3 disks may be larger but will only report up to 2 Terabytes of storage for SCSI-2 format inquiries.

• Large Disk includes the ability to initialize an MPE/iX Disk Volume of up to 512 Gigabytes on SCSI-2 compliant disks. SCSI-2 Disks that are larger than 512 GB are truncated at the 512 GB limit. No matter how big the disk, HP reported, the space beyond 512 GB will not be usable by the MPE/iX or any applications.

There are limits to how much Large Disk is available. And MPE/iX disk volume includes disk-resident OS data structures that use some disk space, so no more than 511 GB of user file space should be expected.

• Large Disk includes a number of opportunistic enhancements to MPE Command Interpreter commands and utility programs to 'smooth' user experience when dealing with large disks, large groups and large accounts. These commands and utilities are REPORT, :[ALT|LIST|NEW][GROUP|ACCT], FSCHECK, and DISCFREE.

HP strongly advises installing all of these patches at the same time using Patch/iX. The Large Disk Patches are:

• MPEMXX8(A) -- FSCHECK.MPEXL.TELESUP
• MPEMXU3(B) -- [ALT|LIST|NEW][ACCT|GROUP]
• MPEMXT3 -- SCSI Disk Driver Update
• MPEMXT4 -- SSM Optimization (>87 GB)
• MPEMXT7 -- DISCFREE.PUB.SYS
• MPEMXU3 -- REPORT
• MPEMXV2(A) -- CATALOG.PUB.SYS
• MPEMXW9(A) CIERR.PUB.SYS, CICATERR.PUB.SYS

Image by pixel1 from Pixabay


Adding a naked Seagate drive to a 3000

Seagate Barracuda 31841

James Byrne reported on a way to get a Seagate disk drive to mount in a Series 918. 

We have a 918LX that we are trying to configure as a spare. The unit has three 18Gb disc drives installed, Seagate model ST31841N. We can see the drives in Mapper at 52.56.6/5/4. We can use DISCUTIL to mount 52.56.4 and 52.56.6 — but we cannot get the drive at 52.56.5 to mount.

This problem drive is a new unit just removed from its factory packaging.

Naked Seagate SCSI drives require a low level format to a sector size of 512 for the HP 3000 to mount them. We have a Windows-based tool called Seatools from Seagate that can perform this formatting from a Windows host — at least, from a host that has a suitable 50N SCSI interface card installed.

The same thing can be accomplished by doing a full install of MPE/iX from tape to such a disc. The install of MPE/iX directly to that disk which we could not mount solved the mounting problem.


3000 market maven Charles Finley dies at 70

CharlesFinley_8_2_2013
Charles Finley, whose career in the HP 3000 community spanned eras from powerful regional user group conferences to trusted HP reseller status, then led to new success as a migration maven, has died at age 70.

Finley built a reputation with the community from his first steps in the Southern California 3000 market. Buoyed by the remarkable manufacturing community in the area, by the middle 1980s he was operating the ConAm reseller and worked to establish the Southern California Regional User Group. SCRUG hosted conferences successful enough to rival those from Interex in scope.

Finley also played an essential part in founding an invitation-only MPE developer conference, using a novel format called the un-conference. It delivered information that otherwise would not be presented if only one person were in charge of the agenda. In the early times for groundbreaking tech, the 3000 community had a forum to explore new choices. "Things that could be overlooked like NT, Linux, VMware are noticed, because one person in the group happened to notice it and think it was important," he once said. "The rest of us benefitted by it."

Once HP curtailed its 3000 futures, Finley evolved the ConAm reseller business into Transformix, owned and operated with his wife Deborah. She assumes the post of president of the firm that has created and deploys a migration suite for carrying legacy applications from MPE/iX and other environments applications onto new platforms, especially Linux.

Finley was a Vietnam-era Marine Corps veteran. His widow said the CEO of Transformix delivered his skill and innovation with a duty to the work and the customer.

"Charles was unsurpassed in his passion for the business, his drive for perfection and professionalism, and his commitment to the integrity of customer relationships," Mrs. Finley said. “I saw that every day in the way he spoke about his work."

"This is both a personal and professional loss for many of the people who have known and loved him. Everyone who knew Charles regarded him as a man devoted to his family, his employees, his customers, and his friends."

Condolences may be sent to Deborah via email. The family requests that donations in lieu of flowers can be made to the charity Charles held close: Copley-Price Family YMCA 619.280.9622. Deborah asks to please designate that your donation is in memory of Charles H. Finley, Jr.

The company he leaves in her management is an integration, reseller, and consulting organization specializing in migration of legacy systems to current hardware and software. Transformix is headquartered in San Diego.

Mrs. Finley said the passing was unexpected. Charles Finley is listed as a speaker at next month's SCALE 18X technology conference. His seminar, Transforming Legacy Applications to an Open Source Modern Technology Stack, was the latest in a line of talks at the Southern California Linux Expo.

This year's seminar would "provide attendees with an understanding of the steps involved to transform legacy applications by retargeting them to an Open Source Java Framework. The seminar shows how the CUBA-Platform framework—which was designed for development of modern web application—is also well suited to enhance and extend legacy applications."

Finley was a significant voice in the migration community. While outlining differences between legacy migration, modernization, and transformation,
his experience smoothed the way for legacy applications to use modern technology stacks, including Java.

His SCALE seminar for this year was "a hands-on workshop transforming a legacy application for those who want to know more."

"If you have a PostgreSQL database already, you can generate a working Java web application in minutes using the CUBA-Platform. Moreover, you can do this without knowing any Java! Also of interest is the fact that professional developers and 'citizen developers' can use the platform for development."


Chicken, egg: First the 3000's OS, then chips

Rooster
Editor's Note: A technical paper from the DEC world asserted that VMS was the first operating system designed before the chipset that it ran upon. MPE's earliest designs were just as innovative. We asked Stan Sieler for some history.

By Stan Sieler

I'd assume that the 16-bit Classic instruction set architecture and the original MPE were designed at about the same time — probably with the architecture being mostly ready/running (real or simulated/emulated) before the software was ready. Once MPE was up and running, some years later there were arguably one to three architectures designed for it (exclusively or not).    

FOCUS

A group of about 12 of us (labs, chip people, me for the OS lab) designed a 32-bit architecture for the next generation HP 3000.        

The architecture was an evolution of an earlier FOCUS used by Ft. Collins for some HP 9000s (after the 68000 models, before the PA-RISC models), and it (the earlier) was either used by the Amigo (HP 300) and/or was inspired by the Classic 3000 architecture. The project got dropped in favor of the VISION architecture.

VISION        

This was the object-oriented architecture (with 64-bit virtual addressing) that was going to be the next-gen HP 3000, running what was going to be called HPE. We had HP 3000/4x computers with rewritten firmware emulating it, and there were a couple of hand-made real CPU boards beginning to run when I left HP in September 1983 to start Allegro. 

At that time, I had a crude command interpreter running on it under my process management code (I was in charge of process management). VISION was very very interesting.  If I had access rights to an object (say, a record from an IMAGE database with an employee name, a date-of-hire, and other information), I could send another process a "descriptor" (virtual address) that would give them access to precisely the subset I wished (e.g., read access to date-of-hire field of the record). But, that concept is gone now.  No one can do that :(        

VISION was dropped in favor of PA-RISC about a month or so after I left. I commented to Joel Birnbaum that it was dropped because I'd left HP. His reply was, "If I knew that, I'd have gotten rid of you sooner."    

About 1982-1983 I began to hear about an architecture that HP Labs was working on that would allow you to run MPE, RTE, and maybe even HP-UX simultaneously.  It was code-named "Rainbow." I think Rainbow turned out to be PA-RISC.

PA-RISC

In the 1980s, RISC (Reduced Instruction Set Computer) was all the rage. People thought it meant quicker execution due to less complex instructions. I am still dubious. I think they underestimated the types of computations and instruction/memory interactions needed — and, indeed, you can see people throwing more and more and more cache towards RISC in an effort to address the speed imbalance between the CPU and memory.

HPE, essentially an extended version of MPE, was designed to run on PA-RISC. To the extent that the virtual memory (and IO) was quite different, that part of the OS was designed for the architecture.

Most of HPE, later MPE XL, then MPE/iX, doesn't care what the architecture is, any more than  Linux/Unix/Windows cares what the architecture is. I seem to recall that a few aspects of the memory protection mechanism (including the Protection ID registers) may have been influenced by HPE's needs.  

Of course, at the same time, HP-UX was being ported from 68000 / FOCUS to PA-RISC, so there may have been interactions there, as well. Note, however, that HP-UX never fully utilized the PA-RISC architecture — particularly the memory addressability, where HPE / MPE XL / MPE/iX had it beaten by far. I don't think HPE, HP-UX, or Netware (which was on PA-RISC briefly, circa 1993) used all the capabilities, including the ability to, in controlled circumstances, let user code directly access some IO instructions.

Itanium (IPF)  

I think I heard that a basic MPE/iX kernel of sorts had been successfully ported to Itanium before the HP 3000 was killed. Obviously, HP-UX was also ported to IPF.   The primary influence MPE/iX and HP-UX probably had was the Itanium ability to run in either little-endian mode (Intel X86 style for Windows) or big-endian (Class, and PA-RISC style, for MPE/iX and HP-UX).

Other operating systems running on Itanium — which have been released in some cases, not released in others — include Windows, Netware, Solaris, OpenVMS, and Tru64 Unix. This list of systems tends to imply that the architecture was not specifically oriented towards one particular operating system.

In short, I think most operating systems exist (perhaps in an earlier form) prior to the chip architecture, but that most architectures are mostly independent of the operating system design/features. The memory addressability mechanism almost always affects major aspects of the internals of the operating system (as it would with VISION).

Photo by Ashes Sitoula on Unsplash


Calendar date issues are already surfacing

Hurdles
The 2028 date hurdle for MPE/iX has been well documented and thoroughly discussed. Although the January 1, 2028 deadline — when MPE/iX CALENDAR processes will start to report dates as January 1, 1970, and so on — seems like it's years away, it's much closer. Calendar issues emerge as programs call for dates.

Programs that call for dates in the future are already facing the hurdle. Systems that use Unix, Linux, or other operating systems this month have triggered these involuntary date rollbacks already.

In one recent case, a top 100 pension fund had a nightly batch job that computed the required contributions, made from projections 20 years into the future. It crashed on January 19, 2018 — 20 years before Y2038.

HP 3000s have been key tools in many financial and resource planning operations. While dates are usually used to track transactions as a matter of history, some ERP users look forward to forecast their resource needs.

MPE/iX has a Y2028. Unix and Linux have a Y2038. This is important to know for a legacy system manager's planning and tactics. There's no good reason to tear down a legacy system if its only show-stopping flaw is date handling. A solution for the 3000 community is already at hand in several spots. 

Stromasys reports it has been working with an independent developer for a 2028 fix, something available to its Charon emulator sites. That update was shared with us in July of last year. It's not public yet, but that indie developer confirms the work is in progress. Beechglen has a 2028 solution it is selling as a service.

There are additional developers and consultants who say they're ready to repair 2028 issues with MPE/iX systems. It's important to know that the HP 3000, as one of the older legacy systems still working in businesses, is in no worse shape than systems driven by Linux or Unix. It's only a matter of when, not if, a date handling process will need to be addressed.

The legacy of an operating system is a condition defined very broadly. Legacy systems have been successful for a long time, and the vendor's focus has usually slipped away from these legacies. It can remind us of that term "proprietary" that was hurled at the 3000 for a decade before HP quit on its futures. Nearly all technology has a proprietary aspect, even if it only amounts to a support clause that makes one knowledge resource crucial to the OS health. 

Photo by Interactive Sports on Unsplash


What good are Nike arrays?

HP NIke Array
By John Burke

3000 users still can employ used HP Nike Model 20 disk arrays. There was once a glut of these devices on the market — meaning they were inexpensive — and they work with older models of HP 3000s. Here's a note from one company using these Nike arrays.

"We’re upgrading from a Model 10 to a Model 20 Nike array. I’m in the middle of deciding whether to keep it in hardware RAID configuration or to switch to MPE/iX mirroring, since I can now do it on the system volume set. It wasn’t in place when the system was first bought, so we stayed with the Nike hardware RAID. We’re considering the performance issue of keeping it Nike hardware RAID versus the safety of MPE Mirroring. You can use the 2nd Fast-Wide card on the array when using MPE mirroring, but you can’t when using Model 20 hardware RAID.

So, with hardware RAID, you have to consider the single point of failure of the controller card. If we ‘split the bus’ on the array mechanism into two separate groups of drives, and then connect a separate controller to the other half of the bus, you can’t have the hardware mirrored drive on the other controller. It must be on the same path as the ‘master’ drive because MPE sees them as a single device.

Using software mirroring you can do this because both drives are independently configured in MPE. Software mirroring adds overhead to the CPU, but it’s a tradeoff you have to decide to make. We are evaluating the options, looking for the best (in our situation) combination of efficiency, performance, fault tolerance and cost.

Note: Mirrored Disk/iX does not support mirroring of the System Volume Set – never did and never will. Secondly, you most certainly can use a second FWSCSI card with a Model 20 attached to an HP 3000

All of the drives are accessible from either controller but of course via different addresses. Your installer should set the DEFAULT ownership of drives to each controller. To improve throughput, each controller should share the load. Only one controller is necessary to address all of the drives, but where MPE falls short is not having a mechanism for auto-failover of a failing controller.

In other words, SYSGEN reconfiguration would be necessary to run on a single controller after SP failure in a dual SP configuration. You could have alternate configurations stored on your system to cover both cases of a single failing controller but the best solution is to get it fixed when it breaks. The best news is that SP failures are not very common.

There is a mechanism in MPE for ‘failover’ called HAFO - High Availability FailOver. It is only supported with XP and VA arrays, and not on Nike’s or AutoRAIDs (because it does not work with those).

Andrew Popay provided some personal experience.

"We have seven Nike SP20 arrays, totaling 140 discs spread across all the arrays, using a combination of RAID 1 (for performance) and RAID 5 (for capacity). We use both SP’s on all arrays, with six arrays used over three systems (two per system). One of our systems has two arrays daisy-chained. The only failures we have suffered on any of the arrays have been due to a disc mechanism failing.

"We never find any issues with the hardware raiding; in fact, as a lot of people have mentioned, hardware raiding is much more preferred to software raiding. Software raiding has several issues, system volume, performance, ease of use, etc. Hardware raiding is far more resilient.'

As for anyone concerned about single points of failure, I would not worry too much about the Nike arrays, I would say they are almost bulletproof. For those who require a 24x7 system and can’t afford any downtime whatsoever, maybe they should consider upgrading to an N-Class, with a VA or XP. Bottom line: SP20’s are sound arrays on the HP 3000s, easy to configure, set up and maintain.


Using RAID5 on an HP 3000

Hard-Drive
By Gilles Schipper
Homesteading Editor

RAID storage, including a low-cost MOD20 array, can improve a 3000's performance. Here are a few things to consider if you will be acquiring a MOD20.

Although possible, I would not recommend utilizing RAID5 LUNs in an HP 3000 environment — unless your greatest priority is to maximize disk space availability at the expense of performance.

RAID5 offers fail-safe functionality over a group of disks (minimum of three) by means of one disk of the RAID5 disk being allocated as a parity disc. The benefit of RAID5 over RAID1 is that it results in a greater amount of overall usable disk space than RAID1. However, it performs poorly in an HP 3000 environment, and cannot be booted from if specified as the system disk (LDEV 1).

Although the supported maximum memory configuration of each Storage Processor (SP) unit is 64MB, 128MB works best (although not all of it can be used).

Each SP has 4 memory slots. You can maximize the performance of the MOD20 by populating each SP with four 32MB memory SIMMs, 72-pin, FPM with parity, 60ns.

The NIKE MOD20 is a very capable and useful solution to the fragile environment afforded by a JBOD environment — particularly because most 3000 JBOD disk systems tend to be very mature and consequently relatively unreliable and prone to failure.

And, although the MOD20 disk system itself is also quite long in the tooth, it’s got built-in fail-safe mechanisms. Also, the MOD20 would appeal to those with very limited budgets, since the devices are quite inexpensive in the used-equipment market.

There are other, more advanced RAID systems that also support the HP 3000 environment. These include the HP Autoraid12H system, various VA7400 systems, some of the HP XP-family members, as well as EMC systems. This list is in order of increasing cost, for the most part.

The bottom line: if you are not already utilizing RAID technology for your 3000, now would be a good time to consider it seriously.


MPE/iX Command File Scripts Explained

Code on screenBy Ken Robertson

The MPE/iX command interpreter has a generous command set, pushing the shell into the realm of a true programming tool. Its ability to evaluate expressions and to perform I/O on files allows the end-user to perform simple data-processing functions. The CI can be used to solve complex problems. Its code, however, is interpreted, which may cause a CI solution to execute too slowly for practical purposes.

Command files are a collection of commands in flat files, of either variable or fixed length record structure, that reside in the MPE or POSIX file space. Basically, command files are what you could call MPE Macros. Anything that you can do in the CI interactively, you can do with command files, and then some. You can use command files in situations that call for repetitive functions, such as re-compiling source code, special spooler commands, etc. Command files are also great when you want to hide details from the end-user.

A command file is executed when its name is typed in the CI, or invoked from a command file or programming shell. Just as in program execution, the user’s HPPATH variable is searched to determine the location of the command file.

MPE Scripts Versus Unix Scripts

For the average task, the MPE scripting language is easier to read and understand than most Unix scripts. For example, command line parameters in MPE have names, just like in regular programming languages.

Of course, there are several script languages on Unix and only one on MPE! On Unix you can write shell scripts for any of the many shells provided (C shell, Bourne shell, ksh, bash, etc). Although there is also now a Posix shell on MPE, most scripts are written for the CI. Several third-party tools, such as Qedit and MPEX, emulate HP scripting and integrate it with their own commands.

A command file can be as simple as a single command, such as a Showjob command with the option to only show interactive sessions (and ignore batch jobs):

:qedit
/add
1      showjob [email protected]
2      //
/keep ss
/e
:

You have created a command file called SS — when you type SS you will execute showjob [email protected]

On MPE, the user needs read (r) or execute access (x) to SS. On Unix you normally must have x access, not just r access, so you do a chmod +x on the script. This is not necessary in MPE, although, if don’t want users to be see the script, you may remove read access and enable execute access.

Structure of a Command File (aka CI script)

A script is an ASCII file with maximum 511 byte records. Unlike Unix, the records may contain an ASCII sequence number in the last 8 columns of each line. The command file consists of 3 optional parts:

1. Parameter line with a maximum of 255 arguments:
parm sessionnumber
parm filename, length=”80”

2. Option lines:
option nohelp,nobreak
option list

3. The body (i.e., the actual commands)”
showjob job=!sessionnumber
build !filename;rec=-!length,,ascii
In MPE scripts, there is no inline data, unlike Unix ‘hereis’ files.

Parameters

Notice in the example above that parameters are used with an exclamation (!), as opposed to the $ in Unix. The same is true for variables. Parameters are separated by a space, comma or semicolon. All parameter values are un-typed, regardless of quoting.

In a typical Unix script, the parameters are referenced by position only ($1, $2, $3, …). In an MPE script, the parameters have names, as in the function of a regular programming language, and can also have default values. In Unix you use [email protected] for all of the parameters as a single string; in MPE you use an ANYPARM parameter to reference the remainder of the command line (it must be the last parameter).

Here is a script to translate “subsys” and “err” numbers from MPE intrinsics into error messages. The subsys and error numbers are passed in as parameters:

parm p_subsys=108,p_error=63
setvar subsys hex(!p_subsys)
setvar error hex(!p_error)
comment the hex conversion allows for negative numbers
comment the #32765 is magic according to Stan!
setvar cmd “wl errmsg(#32765,!subsys);wl errmsg(!error,!subsys);exit”
debug !cmd

As you can see above, the Setvar command assigns a value to parameter or to a new variable. But there are also system pre-defined variables. To see them all do Showvar @;hp. To get information on variables, do help variable and to get help on a specific variable, say hpcmdtrace, do help hpcmdtrace (set TRUE for some debugging help).
In most MPE commands, you must use an explicit exclam ! to identify a variable: build !filename

However, some MPE commands expect variables, and thus do not require the explicit !. For example, Setvar, If, ElseIf, Calc, While, and for all function arguments, and inside ![expressions].

Warning: variables are “session global” in MPE. This means that if a child process, or scripts, changes a variable, it remains changed when that child process terminates. In Unix you are used to the idea that the child can do whatever it likes with its copy of the variables and not worry about any external consequences.

Of course having global variables also means that it is much easier to pass back results from a script! And this is quite common in MPE scripts.

Options

Options allow you to list the commands as they are execute (option list), disable the Break key (option nobreak), enable recursion (option recursion), and disable help about the script (option nohelp).

The script body below shows active process information. This example shows many of the commands commonly used in scripts: If, While, Pause, Setvar, Input and Run. Other commands you will see are Echo, Deletevar, Showvar, Errclear.

WHILE HPCONNSECS > 0
    IF FINFO("SQMSG",0)
       PURGE SQMSG,TEMP
    ENDIF
    BUILD SQMSG;REC=-79,,F,ASCII;TEMP;MSG
    FILE SQMSG=SQMSG,OLDTEMP
    SHOWQ;ACTIVE >*SQMSG
    SETVAR PINLIST ""
    WHILE FINFO("SQMSG",19) <> 0
         INPUT SQLINE < SQMSG
         IF POS("#",SQLINE) <> 0 THEN
           SETVAR PIN RTRIM(STR(SQLINE,47,5))
           SETVAR PINLIST "!PINLIST" + "," + "!PIN"
         ENDIF
    ENDWHILE
    IF FINFO("SPMSG",0)
       PURGE SPMSG,TEMP
    ENDIF
    BUILD SPMSG;REC=-79,,F,ASCII;TEMP;MSG
    FILE SPMSG=SPMSG,OLDTEMP
    SETVAR PROC "SHOWPROC PIN="+"!PINLIST"+";SYSTEM >*SPMSG"
    !PROC
    WHILE FINFO("SPMSG",19) <> 0
         INPUT SPLINE < SPMSG
         IF POS(":",SPLINE) <> 0 THEN
           ECHO !SPLINE
         ENDIF
    ENDWHILE
    PAUSE 30
ENDWHILE

Handling Errors

In most Unix scripts, if a step fails, you check for an error with an If-conditional and then take some action, one of which is ending the script. Without an If, the script continues on, ignoring the error.

In MPE, the default action when a step fails is to abort the script and pass back an error. To override this default, you insert a Continue command before the step that may fail. You then add If logic after the step to print an error message and perhaps Return (back 1 level) or Escape (all the way back to the CI).

     continue
      build newdata
      if cierror<>100 then
         print "unable to build newdata file"
         print !hpcierrmsg
         return
      else
         comment - duplicate file, okay
      endif

You can set HPAUTOCONT to TRUE to continue automatically in case of errors, but this can be dangerous. The default behavior at least lets you know if an unexpected problem occurs.

User Defined Commands (UDC)

UDCs are like Command File scripts, except that several are combined in a single “catalog” file. They are an older feature of MPE, so you may see them in older applications even when scripts seem like a better solution. The primary reason that they are still useful is that they support Option Logon, which invokes the command when a user logs onto the system.

More Information

Tim Ericson’s collection of UDCs and Command files has recently been resurrected and re-published in the public domain at www.3kassociates.com/index_cmd.html

Image by fancycrave1 from Pixabay


Listserv still serving advice after 26 years

Bank vault safety deposit boxes
The 3000-L Listserv repository is the HP 3000 resource that's been in the longest continuous use for the MPE/iX ecosystem. HP had a Jazz website for about 13 years, content that was carried over to Fresche Legacy's servers once HP's labs closed. 3000-L was online for about a year or so before the NewsWire entered the Web.

The content on the 3000-L was a big reason I believed we could do a monthly HP 3000 newsletter. We curated and learned, education and advice we shared with readers. Even after 26 years, 3000-L can be searched for answers that go back to the era of MPE/iX 4.0.

That repository is full of history about the people who have created the MPE ecosystem, too. with enough patience, most answers will be hiding in the hundreds of thousands of email messages. All are logged by subject line. 3000-L can be searched within date ranges, too.

3000-L was once so robust that we could publish a column about its gems once a month as part of the first 10 years of the NewsWire. 

The columns are archived in our 1996-2005 pages. We called them NetDigest, and for awhile they were written by John Burke, who helped us found the NewsWire with his knowing voice and deep technical experience.

For the source material for those columns, refer to the 3000-L search panel.

For the columns, refer to the Tech Page of the '96 - '05 issues. Once you arrive at the Tech Page, just do a search within the page for the phrase net.digest. We've got 106 columns there.

Photo by Jason Pofahl on Unsplash 


So many owners = so much value

Office building colored floors
Editor's Note: While the MPE/iX MANMAN customers mull over their 2020 options, it's useful to look at the history of an application being orphaned by its creator. Cortlandt Wilson, a consultant on ERP systems, wrote this early-years history of how MANMAN's ecosystem evolved. The bottom line is proof that value in an application like MANMAN is baked-in — or it wouldn't have survived so much change.

Over the years MANMAN has experienced highs and lows. At one time the software's creator, ASK Computing, was a media darling — a successful high-tech company founded and run by a woman, Sandy Kurtzig. The MANMAN product has a good reputation in the mid-sized manufacturing systems market. The company, however, unsuccessfully tried to follow up its success with a next generation solution based on a new technology infrastructure.

When I was with ASK in the late 1980s, on several occasions I heard the president and co founder of ASK say that “we are an applications company, not a software tool company.” Unfortunately, the companies on top of the ERP market all developed their own technology infrastructure. The search for a new technology infrastructure led ASK to purchase Ingres for its relational DBMS and tools.

ASK finally purchased a infrastructure and the basic application software for a ERP system from a then little-known Dutch company named Baan. As part of the sales agreement ASK modified significant amounts of the functionality and called the application MANMAN/X. Strained by development costs and weak sales, the company floundered.

By 1994, ASK was facing a severe cash crisis. Looking for a financial angel or a buyer, the board of directors finally recommended a buyout offer from Computer Associates. Many ASK employees, however, responded to the takeover by resigning.

Industry analysts’ concerns about CA’s “ferocious reputation” and the loss of experienced staff highlighted the takeover of ASK. Many MANMAN customers expressed skepticism about CA’s ability to maintain the product, and the quality of support noticeably dropped. 

By 1996, CA concluded that application software and services shouldn’t be managed like software tools and utilities. CA spun off its manufacturing products into an independent business unit to be named the MK Group (MK for Manufacturing Knowledge). MANMAN/X was renamed MK to reflect its marketing role as the flagship product.

Note: Wilson reported from a user group meeting of CAMUS in the late 1990s that the MK Group began to prove stable and was responding better to customer needs. There's inherent value in MANMAN that the repeated transfers of ownership have scarcely erased. By this summer, sites using the ERP package will have right of use for a product that has endured three changes of ownership. The software went from ASK Computer Systems to Computer Associates to SSA Global to Infor. The final owner of MANMAN, Infor, kept up support for nearly 14 years.

Photo by Takafumi Yamashita on Unsplash


Even in apps retirement, 3000 data survives

Aging hands on keyboard
A notable manufacturing datacenter in the 3000 community is making changes to its application lineup over the coming year. Although the profile of the apps and their status is changing, there's no talk of removing MPE from the datacenter yet.

Al Nizzardi is part of the IT command at TE Connectivity, the company that has more MANMAN instances running than any other in that ERP ecosystem. There's been a devotion to the 3000 that's extraordinary. Terry Simpkins has been the face of using 3000s in manufacturing since the 1990s. The IT director at TE even appeared once in a magazine ad promoting the 3000.

At TE, plans for the future of ERP applications have been aimed at SAP for several years. It's a migration, but one with echoes. SAP shares a customization practice with MANMAN: both apps are better choices when they're tuned to individual business practices.

After a few decades of use, the data repository for a MANMAN site becomes an asset that deserves its own curation. Data from a 3000 goes back to the late 1970s. The final cutover to SAP is likely to take place in late 2020 or sometime in 2021, by Nizzardini's reckoning.

"Databases are slowly migrating to SAP," he said. "I believe the final cut over will be 12 to 24 months out from today. That does not mean the end of the HP 3000. Historical data will reside on a HP 3000 of some sort."

TE runs a production N-Class, a test N-Class, an N-Class disaster box, and an A-Class. The datacenter does some Netbase shadowing, Nizzardini added. "We are still formulating a plan on our options, whether it's using an emulator or the N-Class we have" for archival MPE computing. "Either one of those options will be moved to a co-lo."
 
Experts on managing MPE/iX computing never stray too far from a place of helping. "We will be ready for when the Phoenix arises," Nizzardini quipped. "I've often said they will have to yank that HP 3000 out of my cold dead hands."
 
Image by Steve Buissinne from Pixabay

Seeking forgiveness as a support plan

So sorry chalkboard
ERP software becomes wired in deeply at corporations. Now that MANMAN has seen the end date coming for its manufacturer support, customers who rely on the ERP suite are looking for a 2020 plan to keep using it.

One aspect is a ruling about whether a product or a vendor is dead, but the intentions for its product lives on. It's an aspect of law called droit moral in France. Droit moral is not recognized in the US. Intentions are preserved in droit moral.

Some HP 3000 owners considered HP a dead entity after 2008, when no more patches were being built. HP's intellectual rights to MPE and the HP 3000 remain in effect. But there are those moral rights, too. This computer would not have become the keystone at places like aircraft makers and airline ticket agencies without customers' contributions, work that started many years ago. In fact, HP once recognized this kind of help in the market with the e3000 Contributor of the Year Award.

Contributors earn rights when measured in terms of ethics. Droit moral preserves ethics.

Source code rights might belong to customers once a product goes into permanent hibernation at the manufacturer. In 2008, I wrote that I believed that in order to honor droit moral for the 3000 community, HP's increasingly restrictive statements of licensing needed to stop. The vendor's support group needed to move on to other profitable HP markets. The vendor needed to leave owners and customers to continue using their computer, without any extra licensing payments to HP.

Droit moral lived in the hearts of some of the 3000 advocates within HP. While I visited HP's 3000 group one afternoon, the former business manager Dave Wilde and I walked across the wooded HP campus to lunch. That entire campus site is now the location of Apple Park, Apple's worldwide HQ, so things have changed a lot. At the time, through, Wilde said the 3000 group wanted to give the system "the ending that it deserves." It sounded warm and genuine.

Infor, the owners of MANMAN, are not as warm and genuine, even though they have enough sense about branding to sponsor the NBA Brooklyn Nets with an Infor logo on Nets uniforms. At the moment there's no coordinated effort from the remaining MANMAN customers to establish whether MANMAN truly belongs to customers after the exit of its creator. The customers are unsure who might even respond to such ownership questions.

Continue reading "Seeking forgiveness as a support plan" »


Does orphaned source code belong to you?

Orphan with bike
Not many application vendors still have shingles hung out for business in the MPE market. It's also been awhile since any vendors made an exit from the MPE marketplace. Now that Infor, makers of MANMAN, will depart this coming June, its ERP customers are talking about what source code is rightfully theirs.

During a conference call, about a dozen customers and another dozen independent support vendors kicked around the idea. Every customer on the call had signed a MANMAN license agreement, way back in the 1980s or 1990s. It was generally accepted that you never own a piece of software unless your organization wrote it.

To put it more plainly, the use of a vendor's product is always governed by an agreement. Everybody agrees on the rules for ownership and use.

Then conditions change.

The vendor folds up a product line, or goes out of business altogether. It happened with MPE/iX, to note one instance of the former fate. 3000 users can scarcely take a few steps before they stumble on a software vendor who's closed down all business. That's what happens over time after a vendor has built the bulk of its business around a server that's no longer sold or supported by the manufacturer.

The new condition gets managers asking about why any license should apply to an orphaned product. Permission to own the code that's only been licensed — that's a matter for the courts, or at least lawyers represening both sides.

The hard place the managers encounter is the language that keeps software in a vendor's IP locker. In cases like these, IP not only means Intellectual Property. It means, "in perpetuity." If anyone has a digital copy of their contract, searching for that phrase will certainly bring up a hit.

Eleven years ago, the 3000 community talked this through while Hewlett-Packard considered the new licensing of MPE/iX source code. Customers wanted their intention of owning a 3000 — to run a business in perpetuity — to match the intentions of HP's product licensing. We invoked French law to give voice to our wishes for that outcome.

There is an aspect of French law which does not exist in US law. It's called "droit moral," meant to protect the moral rights of ownership of a work of art. Even more than HP's support group, the 3000 community considered MPE/iX to be a work of art.

One story about using droit moral in the movie business:

Droit moral is an intellectual right of an artist to protect his work. When an artist dies, the droit moral goes to his heirs, unless he appoints someone else. For example, a John Huston movie was colorized in the US, and the movie was shown this way in the States, despite the opposition of the Huston heirs who were trying to honor their father's artistic wishes. But in France, where the Huston heirs argued their father didn't want his film to be in color, the colorized film can't be shown because of droit moral.

The argument, one which might be tested in court, is that the intention of investing hundreds of thousands of dollars in a product is to use it in perpetuity. Ownership of source hasn't been much tested in US law. The places where cases have appeared before a judge are courtrooms where things went better for the customers than the manufacturers.

Image by Isa KARAKUS from Pixabay


Information for MPE/iX: Always Online

NClass movie

HP's movie tour of the first A-Class systems, still online

Time machines transport us through the power of timeless information. It can take us way back, into the era when legacy technology was current and popular. In the 3000 community we are connected by wires and circuits and pulses of power. We always were, from the days of black arts datacomm that pushed data off of cards of punched paper. We’ve lived through a glorious explosion of ideas and inspiration and instruction. It’s a movie that always has another story in waiting, this Internet, so ubiquitous we’ve stopped calling it by that name. In 2019, 45 years after MPE became viable and alive, the World Wide Web is named after an element common throughout the physical world: the cloud.

And through the magic of these clouds come stories that lead us forward and allow us to look back at solved challenges. My partner Abby and I sit on the sofa these days and play with paper together, crossword puzzles, especially on weekends with the New York Times and LA Times puzzles. We look up answers from that cloud, and it delivers us stories alongside the answers. Finding the Kingston Trio’s hit BMT leads us to the Smothers Brothers, who started out as a comic folksinger act. After HP 3000 strategy TV broadcasts came alive via satellite, there were webinars. Today, YouTube holds stories of the 3000’s shiniest moment, the debut of the ultimate model of that server's N-Class.

Gravity - George Clooney One night we sat on another couch and watched the splashiest celebration of stories in our connected world, the Academy Awards. Despite racking up a fistful and more of them, Gravity didn’t take the Best Picture prize that night. A thing can have many elements of success, enjoy parts of being the best, and not end up named the winner in the final balloting. The 3000 saw a similar tally, a raft of successes, but its light began to fade from HP's vision. In the movies they call the last light of the day magic time, because it casts the sweetest shades on the players and settings.

It’s magic time for many of the 3000’s stalwart members in its special academy. The 3000 is remaining a time machine in your reaches of space. It's data is like gravity, a force to unify and propel. MPE systems contain ample gravity: importance to users, plus the grounding of data. Data becomes information, then stories, and finally wisdom.

And in our magic time, we are blessed with the time machine of the Web, the cloud. Users and owners of HP 3000s will always be able to look up wisdom of this community online, written in stories, illustrated in video, told via audio. Find it here, as well as in the cloud at the following resources:

The HP Computer Museum

3K Associates

The host of the HP Jazz papers, Fresche Legacy

Then there are the fallen, resources no longer at their original addresses.

The MM II Support Group

MPE Open Source.org

Those last two are live links today, however, thanks to the Internet Wayback Machine. The Wayback is such an enterprise now that it's fundraising this week. The arrival of Wikipedia was met with skepticism at first, and it's still sneered at in some places. The popularity of Wikipedia is demonstrated in the way it appears as the first result in many a Web search.

The Wayback will save what we don't remember, even as it moves off of its legacy addresses. These very Web pages you're reading are likely to be Waybacked. We began putting the NewsWire on the Web in 1995. The dream was that our website would be like the 3000 in one way, Always Online. By now, by way of the Wayback, it seems the dream has come true.


Wayback: HP FAQ captured its OS visions

Canary close up
It's only available through the Internet Wayback Machine, but a record of HP's intent for its enterprise operating systems still exists. For reference we traveled to LegacyOS, a website devoted to the legacies of Sun and HP's enterprise products. The promised land, as HP imagined it 17 years ago, was getting its operating systems to the Itanium Processor Family.

HP's decision to keep MPE/iX away from IPF servers was the canary in the coal mine for the company's business intentions for HP 3000s. Such a canary roosted in mines while work proceeded. If the quality of the air turned poisonous, the canary died and the miners evacuated.

At the time there were only two models of Itanium processors in working servers from HP, so calling it a family was marketing optimism. Nevertheless, moving to the nascent IPF, as well as a new OS in HP-UX, was HP's vision of end-of-life. The life ending turned out to be at HP's MPE/iX labs eight years later, rather than any useful lifespan for MPE/iX.

There is a current-day lesson in any review of the HP 3000 plans of 2002. HP noted at the time the vendor created a Business Critical Systems group. That group, HP's cheerful-but-inaccurate 3000 plans, and HP itself in its classic makeup don't exist anymore. Users can count on their community, rather than the vendor, to see the conditions for any end of life canary.

Q: What is HP’s strategy moving forward with HP e3000 servers?

A: Our commitment to HP e3000 and MPE/iX operating system is to continue delivering on the roadmap we have already communicated, delivering the planned performance and functionality, with future MPE/iX releases in the 2002-2003 timeframe. Moving forward, we are focused on moving HP e3000 customers to IPF-based HP servers that deliver more benefits to the customer, using aggressive and innovative migration programs.

Q: Does HP plan to port MPE/iX to IPF-based platforms?

A: No. MPE/iX will not be ported to Itanium-based servers. The communicated HP e3000 roadmap includes PA-RISC based servers that deliver the performance and functionality customers need in the 2002-2003 timeframe. After that, HP e3000 customers benefit more by moving to HP Unix Servers using Itanium technologies and best-in-class migration programs, and taking advantage of the industry leading performance, functionality, and lasting value that Itanium and HP-UX will deliver.

Q: Should HP e3000 customers who need to stay longer on the platform than 2004 be concerned?

A: Absolutely not. HP will support the servers at least until the end of 2006. During this time, HP is committed not only to provide full support for the servers, but also to make available the aggressive and innovative migration programs, to help customers successfully move into Itanium-based HP-UX servers on their own pace.

To recap, the end of 2006 became the end of 2010, in part because HP's aggressive and innovative migration programs were undermatched to the needs of the customer. The Itanium technologies became an also-ran, lapped by Intel's modernization of x86 processors. Intel announced its departure from Itanium futures in 2015. Now commodity hardware rules the roost in today's mines.

Photo by David Clode on Unsplash


Set a Watch for Jobs That Hang Others

Guard tower
Jobstreams deliver on the HP 3000's other promise. When the server was introduced in the early 1970s it promised interactive computing, well beyond the powers of batch processing. Excellent, said the market. But we want the batch power, too. Running jobs delivered on the promise that a 3000 could replace lots of mainframes.

Decades later, job management is still crucial to a 3000's success. Some jobs get hung for one reason or another, and the rest of the system processing is halted until someone discovers the problem job and aborts it. When it happens over a weekend, it's worse. You can come in Monday and see the processing waiting in queue for that hung-up job to finish.

Is there a utility that monitors job run time, so that it can auto-abort such jobs after X number of hours? Nobix sells JobRescue, a commercial product for "automatically detecting errors and exception messages; JobRescue eliminates the need for manual review of $STDLISTs, making batch processing operations more productive."

Then there's Design 3000 Plus. The vendor still has a working webpage that touts JMS/3000, a job management system that was at one time deployed at hundreds of sites. Its powers include "automatic job restart and recovery. Whenever a job fails, a recovery job can be initiated immediately."

The home-grown solutions are just waiting out there, though, considering how few 3000 sites have a budget for such superior software. Mark Ranft of Pro3K shared his job to check on jobs. The system does a self-exam and reports a problem.

Continue reading "Set a Watch for Jobs That Hang Others" »


Where MANMAN support goes, post-Infor

Abandoned storefront
Sometimes established structures go vacant without even knowing they've been abandoned. That might be the case for the support service for the MANMAN ERP software. There are at least 35 companies making use of the application suite on HP 3000s.
 
Those users have been served by the Computer Aided Manufacturing User Society. It's not only an operating user group, it's got a surplus in its accounts. That's the opposite of Interex, which stopped operations while owing millions.
 
On a recent conference call, one CAMUS board member said CAMUS is the best source to contact other MANMAN customers. Nobody on the group's call reported using Infor support anymore. Many of the users have an arrangement for help from an independent company like The Support Group.
 
Doesn’t that mean the customers have already made arrangements for their MANMAN support outside of Infor?

Infor had said last year that its cutting out app support because system vendors don’t support the hardware and OS for MANMAN. That wasn't true up to July of this year for VMS MANMAN users. But it’s been true for the MPE people since 2011.
 
It looks like Infor was happy to collect support for MPE systems for years after HP left the 3000. Now it looks like the VMS support migration away from HP Enterprise and into VMS Systems Inc. is the trigger for shutting down all of the MANMAN support at Infor.
 
The systems haven't been turned off, but the vendor has departed. That's a familiar situation for MPE/iX customers.
 
Photo credit: Rafał Malinowski on Unsplash

HP still keeps MPE data behind a paywall

Payphone
Photo by John-Paul Henry on Unsplash

It can be surprising to see how much value remains in an operating system that's not been altered in almost a decade. Hewlett Packard Enterprise has 3000 documentation on its website that is still behind a paywall of sorts. Users access this info by validating their HP Passport credentials — the ones that indentify the user as being current on a support contract.

The HPE website has plenty of advice and instruction available without a validation. If you ask, for example, "Can the HP 3000 and GSP LAN configuration be on different subnets?" HPE reports

There are two server platforms (A-CLASS [A400/A500] and N-CLASS [N4000]) that can run MPE, which uses the GSP (Guardian Service Processor) console for offline hardware operations like startup and shutdown of the system, access hardware console or system logs, etc.

It is possible for management purposes to place the GSP operation on a different subnet from the MPE server LAN, thus isolating or protecting either environment from one another. One reason for that can be to prevent normal users from telneting or in other ways accessing the GSP console or the other way around.

Or, another morsel that's useful in the era of declining hardware know-how: A-Class IO path memory configuration guidelines. Useful for the manager who's trying to set up memory cards in one of those $5,000 replacement 3000s.

However, if you'd like to read the most current documents, a support contract stands in the way. An updated NMMAINT listing is behind the paywall. HPE created the document in August of 2019. There's no available support to be purchased from HP for MPE/iX.

The documents that survive can be extensively redacted. A HP3000 License Transfer Process document references a web address no longer in service. The address licensing.hp.com no longer answers to requests.

Some information on MPE/iX at HPE's website is among the 4,386 documents at the site. Having the confidence that it will remain in that place is the next step in learning to rely on HPE resources. Independent MPE/iX resources have been more reliable, although the web pages for MM Support went dark this year.


Values hidden by time get revealed by vets

Brass treasure key
Photo by Michael Dziedzic on Unsplash

Twenty-four years ago we started unlocking Hidden Value for HP 3000s: Commands that only the veterans know, plus the processes that have been plumbed to bypass MPE's blind alleys.

Some of the value is specific to a 3000 process like using EDIT/3000. It's antique, that editor, but it's on every HP 3000.

I use cut and paste with EDIT/3000 to enter data to batch files.  It works well except that I am limited by the size of the scratch file. Can I change the size of this file so I can paste more at a time?

Immediately after entering Editor, enter "set size=######" to give yourself more space.

For other tasks, like finding forgotten passwords, and keeping them fresh and the 3000's data secret, more elaborate answers have surfaced.

A system manager pitched his plight.

"My operator, in his infinite wisdom, decided to change passwords on manager.sys.  Of course he forgot, or fingerchecked... I don’t know.  At any rate I need some help. Any suggestions, other than a blindfold and cigarette?"

Several versions of help involved the use of utilities from security experts VEsoft. "Do you have the GOD program on your system? If so, it has PM capability, and so it can give the user who runs it SM capability. So it will allow you to do a LISTUSER MANAGER.SYS;PASS=

(That's why GOD should be secured, by the way. A randomized lockword will do the job, visible only to users who have SM capability. When VEsoft installs MPEX, for example, it installs a randomized password to MGR.VESOFT, and to GOD.PUB.VESOFT.)

Paul Edwards, ever a source for HP 3000 training, ran through the backstop methods every system manager should practice to avoid such a dilemma.

1. You run BULDACCT prior to each full backup so you can look in BULDJOB1 for the passwords 
2. You have another user on the system with SM capability and a different password as a backup in case this happens  
3. Your operator used LISTUSER MANAGER.SYS;PASS just after changing the password to verify the accuracy as spelled out in the Operations Procedures section in your Systems Manager Notebook   
4. You have a Systems Manager Notebook

  Then Duane Percox of K-12 app vendor QSS opened up a clever back door:

If your operator can log onto operator.sys:
file xt=mytape;dev=disc
file syslist=$stdlist
store command.pub;*xt;directory;show

Using your favorite editor or other utility search for the string: "ALTUSER MANAGER  SYS" You will notice: PAS=

, <passwd> which is your clue


Keep Passwords Fresh on 3000s: Methods

Fresh bread
Photo by Clem Onojeghuo on Unsplash

It's usually a good practice to keep passwords fresh. A 3000 development manager once posed a question about how to do this while staying inside the bounds of MPE/iX. He had the usual limited budget associated with HP 3000 ownership.

"Management wants users to be forced to change their passwords on a regular basis. Also, certain rules must be applied to the new password. I don't have budget for the good tools for this, like Security/3000, so I need to write something myself, or see if there's any contributed code to do the job."

Homegrown and bundled solutions followed. When Jeff Vance worked in the 3000 lab at HP, he offered the pseudo random password generator as a solution. It's in the HP Migrations webpage hosted on the website of the company formerly known as Speedware. These HP Jazz solutions that used to be on the HP website are still available at Fresche Solutions.  

There are UDCs on Jazz which force a password to be supplied when using NEWUSER, NEWACCT and NEWGROUP CI commands. These required passwords can be random (uses the script above) or user entered with a minimal length enforced.

Then Vance added as an afterthought, a strategy to program your own password system:

I haven’t thought about it much, but it seems you could have a password file (maybe a CIRcular file?) for each user on the system. This file would have their last N passwords, and the modified date of the file would be the date their password was most recently changed.

A logon UDC could detect if the password file for that user exists. If not create it and require a new password right then.  If the password file exists then get it’s modified date and compare that to today’s date. If greater than X days then in a loop prompt for a new password. Validate the entered password against previous N passwords and your other rules. Maybe run a dictionary checking program to make sure the password is not common, etc.

Update the user-specific password file with their new password, and then logon the user.

From the user community, Donna Hofmeister weighed in with this advice:

If you have no choice other than to develop your own software, then I’d certainly model it after what VEsoft has already done. That is:

Based on a system-wide UDC, examine all sessions (it is just sessions, yes?  By the way, a DSLOGON from inside a job is still a session....) against a ‘database’ (By the way, just how secure is this database?  A real database needs passwords... Who’s going to maintain that? A flat file could be lockworded... but that’s not a slamdunk answer.) which is looking for the ‘age’ of the password (By the way, are you going to provide an advance warning period?). 

If it is time to change the password, get the ‘new’ password from the user... but writing the rules is a pain, and keeping track of reused passwords is just annoying. Auditors in the states love when you can say the password is one-way encrypted.  Dunno what your management is saying for encrypting an MPE password.

Continue reading "Keep Passwords Fresh on 3000s: Methods" »


Welcome to Year 19 of the Afterlife

Cheated Death on printer
You remember where you were, perhaps, on the day you learned Hewlett-Packard was done with MPE/iX. You might have been in a meeting, or checked your email before heading home. You might have been installing something a 3000 needed to keep serving your company, or even ready to order a new server to replace the old 9x8 box. Some unlucky vendors were holding orders for new systems.

People did all of that and more on the day HP revealed its 3000 era was on its way to a finish. By 2003 the community was calling the new era The Afterlife. The lifespan of building new HP 3000 hardware was ended when a box rolled off the line at the Roseville plant in early November that year.

Afterlife shirt

And so, on November 14 of 2001, the afterlife of Hewlett-Packard's lifetime started with dismay, anger, and then resignation. The five stages of death proceeded through discussions in a lively 3000 newsgroup. Taking a cue from the horrors of 9/11 in that season, programmers and vendors howled about the relatively unimportant death in their lives.

Doug Greenup was leading Minisoft in that November week. The CEO of a software company whose products were on thousands of systems, he became aware of the HP pullout with just one day's notice.

Alvina Nishimoto from HP called me. She was in charge of third parties with HP at the time. She asked me to sign a non-disclosure which she'd just faxed me. She said she had important news. I signed it and faxed it right back. She called to tell me HP was announcing they were discontinuing the HP e3000, and that HP-UX was their future direction.

HP might have been worried the story was going to get into the world without its influence. The news had been roiling through the 3000 community for more than a week before I learned about it. I'd been away on a vacation in Europe when I got the call from my partner Abby. HP wanted to brief me. Wirt Atmar, the founder of AICS and a 3000 stalwart, threw off the lid 10 days earlier about the pullout by posting to a developers' mailing list.

I spoke to two of our oldest, most trusted customers yesterday, one a ten-year customer and the other 15 years, about this upcoming announcement. Their first reactions were that it simply sucked their breath away. When I told them about HP's proposed plans of migrating their applications to HP-UX — which as an option has all of the practicality to them of trying to establish a penguin colony in Death Valley — their second reaction was "the hell with HP. If we move, it will be to anything but HP." I think that that's going to be the general reaction.

HP learned a great deal about ending a product line with the lessons that began 18 years ago. Earlier this year the company made a graceful transfer of responsibility for OpenVMS, sending the software as well as support opportunities to an independent firm, VMS Software Inc. HP won't sell any more OpenVMS licenses, although it continues to build Itanium servers that will run the apps created for that OS.

This was a vision that the HP 3000 community took to heart during the first of the 18 years that followed. A similar group of OS experts, organized and led by Adager, wanted HP to transfer the future of MPE/iX to new, independent stewards. HP didn't know how to do this in 2001 or in 2002. The offer took another form in the OpenMPE advocate organization, but eight more years had to slip past before HP's source code made its way into independent software labs.

A new history began 18 years ago today, a chronicle of a group of customers who kept their own counsel about walking away from a corporate computing asset. The next two years or so will show HP Enterprise customers what might have been possible had MPE/iX found a third party home. VSI is predicting that it will have production-grade OpenVMS ready for a late 2021 release on Intel hardware.

This is more than a shift away from the HP Enterprise resources. VSI is carrying OpenVMS to a new chipset, a commodity home. In 2001, Atmar told HP's business manager for 3000 operations, Winston Prather, such a move was what the 3000 customers deserved.

Opening MPE up and migrating it to an Intel platform offers at least some real hope for a continued and bright future for MPE. More than that, it keeps a promise that most customers believe HP has made to them, and that is very much the nub of the moral and ethical question that faces you now, Winston.

Migrating MPE to Intel hardware would have permitted MPE to run on inexpensive but high-quality servers. Earlier this month, VSI announced a timeline for such a thing to happen with OpenVMS. A different HP paved the way to that decision—a vendor perhaps chastened by the past—than the corporation that launched the 3000's afterlife.

In the beginning, the launch of this server took place during this month. The slogan at the HP 3000 lab in 1972 was "November is a Happening." Nothing can change what happened nearly 30 years later. But the VSI transfer shows the decisions over what to do with a loyal enterprise customer base have changed in the years since 2001's happenings.


Customized code care can add time to apps

Sewing spool and scissors
Image by TooMuchCoffeeMan from Pixabay

Almost all MANMAN sites have the original ASK FORTRAN source code, but a few have lost track of some of their mods. It seems hard to believe for some analysts, but source code for applications can go missing, too.

It's easier to believe while considering the age of this software. A 3000 which first booted up a manufacturing site for TE Connectivity in 1978 recently got powered down for the last time. The software had outlasted a half-dozen servers, until finally the need lapsed for a host of an application launched 40 years ago.

TE has its source code for every 3000 instance it continues to run to manage manufacturing across North America and Asia. You can imagine, though, how much care it takes to keep that corporate asset in good working order from the era before PCs until today.

Managing the modifications is the other essential piece of the lifetime-extending effort for MPE/iX ERP solutions. No app suite is as often customized as ERP; the term itself is an extension of the Manufacturing Resource Planning of the 1980s. What was once MRP is now ERP. The planning always needs custom code, tailored to the business processes.

Terry Floyd, the founder of MANMAN support resource The Support Group, said most MANMAN sites — and there are under 100 by now — own and manage their own source code for the main application set. His company deals with modifications for its clients, too. Without the mods, using such apps is a matter of being frozen in time for features. It's like trying to take out a pair of pants without enough material.


What MANMAN sites didn't know until now

 
Just this week I sat in on a call among MANMAN users. There were not a lot of them, but 20 people dialed in or opened a GoToMeeting for a conference call. Regional Users Group meets have disappeared except for the Computer Aided Manufacturing User Society. Unlike some 3000 owners and managers, CAMUS still has something to talk about.
 
The discussion topic is change. Here in 2019, CAMUS users manage HP 3000s that continue to manage manufacturing. That situation will change sooner or later. Manufacturing software is wired in deeper to a company's nervous system. Enterprise Resource Planning (ERP) can apply to many MPE/iX shops. ERP has the longest lifespan of any application package.
 
Not long ago, an ERP system was shut down at TE Connectivity. TE is probably the biggest customer by number of ERP 3000s. The system that was powered off for good hosted software that had been running since 1978. Other ERP instances there, not as old, continue to run.
 
Forty years. One operating environment. A legacy within a legacy community. In essence, though, just the longest lived veteran in a room of greybeard application suites. The shutdown didn't even come up during the RUG call.
 
The meeting was organized by the CAMUS president Terri Lanza, who led the discussion. One of the more interesting parts was the group’s take on Infor support. The vendor's dropping support altogether for MANMAN customers next year. Some customers on the call were just learning that Infor's support verdict has been out since 2018. 
 
Support disappearances are not exactly news in the 3000 world. This strategy by Infor, though is notable. It's perhaps the last departure from an application vendor.
 
That might be due to the number of MANMAN sites still paying Infor support fees. Nine, in all, and that was as of last year. Revenue from support is the canary in the mine shaft for vendor decisions like this.
 
Infor is closing down an operation for MPE/iX that had been available in name only, if the RUG's intel is accurate. In less than a year, even the backup to the best engineers will be working on something else. By May, the app will stop being sold or supported. Go-time for software that's free, right? Not so fast there. The 3000 community has been through this before.

Continue reading "What MANMAN sites didn't know until now" »


Wayback Wed: Leaving a Wake on an exit

Chris Gauthier  Jackie at Wake
Simpkins  Nizzardini  Johnson Wake redux
Above, a 2019 commemorative lunch today at Tide Mill Café in Hampton, VA with Terry Simpkins, Al Nizzardini and Tracy Johnson, all 3000 experts and veterans of MPE. 3000s are in use at their company, TE Connectivity. At top, a 2003 World Wide Wake picture with Chris Gauthier and his co-worker Jackie Mitchell, both supporting 3000 customers as contractors to Terix.

Today we're marking the 16th anniversary of the World Wide Wake. The event was a marker of the end of HP’s 3000 manufacturing on Oct. 31, 2003. Alan Yeo, who passed away recently, organized the Wake and posted photos contributed from attendees onto what we were still calling the World Wide Web. A Web gallery for 3000 people was groundbreaking at the time.

Yeo said back in 2004, a few months after the event that drew more than 400 devotees to meetings in 15 countries, “We have created a simple single Web page that by country just lists the venues and who attended, and also has a link to any pictures for that venue," Yeo said. “The information will be condensed into a single Web page, linked to a directory of about 75 images. We have had several offers to host the information, so rather than try and pick a single host, we thought that allowing any interested attendee to host it would be best.”

Thanks to good Web hunting from Keven Miller, the Wayback Machine link to the original Web page tells the tale of who attended, and where, along with some of the photos.

Our own archive of the photos, sans captions, is here on the blog.

The photos from that day look like party pictures, even though nobody in them was celebrating anything except Halloween. The memories were on the minds of everyone in the frame, though. The future without any more new 3000s didn't seem to scare anyone on that day, at least not for the cameras. It was a coincidence that the building of new computers, as well as the licenses for the MPE/iX that made the boxes genuine 3000s, stopped on the spooky holiday. HP's fiscal year ends every year on October 31.

The Wake gatherings were all across the globe. New Zealand was the furthest away from the Epicenter of Grief, as the 3000 faithful had dubbed Lori's Little Shack in Roseville, the town where HP's 3000 factory was ending its birth of the servers. 

Loree's Epicenter Grief

Continue reading "Wayback Wed: Leaving a Wake on an exit" »


Crave sounds of connection? Call in Nov. 7

HP 3000 owners and managers, as well as developers working in manufacturing, can hear each other's voices next week. Those who crave the connection of conversation can call in on Nov. 7 at 10:30 CST (8:30 Pacific, 15:30 UK) for this year's CAMUS user group meeting. Email organizer Terri Lanza to register (it's free) and get the dial-in number.

For many years, the members of the Computer Aided Manufacturing Users Society gathered in person. The meetings were small in number compared to the attendance and exhibits at Interex events. But here in 2019, some 14-plus years after Interex died, CAMUS still hosts gatherings including this call. Sometimes the group, led by the cheerful and redoubtable Lanza, has met in person. This summer she set aside a meeting room at the local Dave & Busters in the Chicago suburbs for a Sunday afternoon gathering.

Everyone at this year's meeting was 20 years older than in this 1999 photo at the same Dave & Busters.

CAMUS RUG 1999 Larry_Vicky_Steven_Holly

At that same 1999 meeting, robotics toys were a part of the agenda. Because even in that year, it was easy to see that robotics was going to be a big part of manufacturing IT in the years to come.

VickyFalk 1999 CAMUS MWmeet

A conference call still has the word "conference" within, so the November 7 call is a gathering without the toys and games. There are important things on the agenda. In the wake of Infor announcing they're ending MANMAN support in 2020, the meeting will give attendees time to share strategies on hardware, software, hosting, application modifications, education options "and just plain answering questions forever," Lanza says, "or as long as you need it."

That's a better offer now than the one Interex was able to maintain. There's an advantage to running lean to stay in the game of gathering. Register with Lanza at [email protected]


HP's kids: Children who can't say yes, or no

Merry-go-round amusement parkPhoto by Marjorie Bertrand on Unsplash

Editor's note: Developer, vendor, and advocate Alan Yeo has passed away at age 65 after a lifetime of work for the 3000 community. His essay below was written in 2005 amid the early years of the computer's Transition Era. He wrote about the damage done after migrations were first triggered by HP's 2001 pullout, then postponed on a fuzzy timeline from the entity the community was calling the virtual HP division for the server, vCSY.

Vendors like Yeo who weathered HP's stormy strategy took on a lot of water because of HP's revision of its end of service deadline. Yeo's use of metaphor and allegory here are a fine tribute to his wit and intelligence that the world has lost. ScreenJet, his company, followed his insight to survive the turmoil.

By Alan Yeo

That's it, children, just give the merry-go-round another shove, just when passengers thought it was stopping and they could get off it and get on with planning the rest of their lives. Oh yes, some of the children will be happy; the period before they have to decide which ride to take next has been extended. But for the adults either already behind schedule, or struggling to get attention-deficit children to concentrate on important decisions, it's just another frustrating delay.

Now it wouldn't be too bad if the very Careless Stupid Youngsters ("vCSY") nudging the merry-go-round on weren't the same vCSY who had planned its retirement, and had then encouraged its customers and partners to seek out new more exciting future-proof rides. But no, to compound the disappointment they caused their passengers when they announced the ride was ending, they now have to say, “We lied, we didn't mean it, the ride's not ending yet!”

Is this because they think their passengers are still having the best ride in the fair? Perhaps they think they can just keep it spinning under their control for a while longer, that there are another 3000 pieces of silver to be extracted for their parents, the only Happy Party ("HP") in this.

And what of vCSY partners, and the encouragement they received to help transport the passengers to other rides when the Merry-go-round stopped. Or even those they encouraged to build an organisation to help those passengers that wanted to stay on the Merry-go-round and even maintain it after the ride had stopped.

For yes, there was an organisation of such Open Minded Passengers Established ("OpenMPE") that hoped to provide counseling and support for those who chose to stay, and even to build a work shop to repair the Merry-go-round Physical Environment ("MPE") for them. What of OpenMPE's chances now? Why would anyone invest in them when they need it, if the HP and vCSY are going to keep the ride spinning and the MPE supported?

And what of those who vCSY encouraged to build the transport for the passengers to other rides — their parents (the HP) had no transport of their own. Those vendors built the busses the planes and the trains, and even migrated some of the passengers to new rides. What are they to do now, just sit there with the engines running for a couple more years whilst the merry-go-round spins on?

And what of those partners vCSY encouraged to build infrastructures to keep old merry-go-round's functioning and provide support for the MPE? For them, the ride has been delayed for two more years, and it has reduced the number of potential passengers to the point where it may not be economic to hang around and wait.

Continue reading "HP's kids: Children who can't say yes, or no" »


Alan Yeo, 1954-2019

Yeo at Reunion

Alan Yeo, a software vendor and developer whose business ultimately led to success as a nexus for the 3000 community in its Transition Era, has died at age 65 after a battle with a small cell cancer. He is survived by his wife Helen, a lifetime of creations he designed with partners, and a gripping voice that gathered and rallied MPE customers after HP quit on their marketplace.

Yeo’s company Affirm, Ltd. rose up in the 1980s as a resource for manufacturers who used the HP 3000 to manage their enterprises. He served a group of customers across the UK and began to move in wider circles with the advent of ScreenJet, his software to modernize the 3000’s bedrock VPlus application interfaces.

ScreenJet arose in the years just before Hewlett-Packard scrapped its business developing 3000s and MPE. While the HP decision left Yeo undaunted in his business aspirations, it also led him to a new role as a leader for a 3000 community that was dissolving after the implosion of the Interex user group in 2005.

His first effort surrounded the final date of HP’s manufacture of the system. On Oct. 31, 2003, he organized and led the HP 3000 World Wide Wake, a collective of gatherings to celebrate the server and the people who’d made it their life’s work. Across North America and Europe, customers and managers held parties and met at pubs, bars, and restaurants. Photos from the events poured into a web server that Yeo hosted. Earlier in the year, Yeo asked out loud where else the HP 3000 community might gather in a user conference — a question he posed in a meeting at the Atlanta HP World, where few 3000 customers had appeared.

In the year that followed, he shared his strategy of being a master of one. It was built around the nugat of collaboration that led to his ability to connect.

"We’re starting to see more collaboration between migration tools providers and migration service partners," he said in a NewsWire Q&A. "To get some of this stuff right, you really, really need to know it. I think it’s too big for any one person to do anything right. If you want good fish you go to a fishmonger. If you want good meat, go to a butcher. If you just want food, go to Wal-Mart, and if you just want to eat, you go to McDonalds."

Community meets and reunions

Many of the stranded customers using the HP 3000 got an introduction to Yeo’s voice in those first years of the 3000’s Transition Era. He commissioned an editorial cartoon during 2002 that became a mainstay in his company’s ads, one built around the HP move to end its MPE plans and sever relations with the thousands of companies that grew up using the 3000’s extraordinary solution. The CEO of the company at the time, as well as the 3000 division’s GM Winston Prather, caught the brunt of the brilliance in a cartoon that compared killing off HP's 3000 futures to the evil in a Disney movie.

WinstonDalmations
A few years later, after the user group Interex folded its operations overnight and stranded users’ plans to meet at the now-canceled annual conference, the first of a series of Community Meets sprang up for 3000 owners. After an impromptu gathering in the Bay Area for community members already stuck with nonrefundable hotel reservations and air tickets, a single-afternoon lunch gathered several dozen managers, developers, and owners.

The first Bay Area meet was replicated and expanded twice more with single-day meetings in 2007 and 2009, organized and underwritten by Yeo and his business partner Michael Marxmeier of the database and language vendor Marxmeier Software. Other companies contributed to cover expenses, but the largest share of the organizing always went to Yeo.

In 2011, he and Marxmeier teamed up with some help from the NewsWire to mount the HP3000 Reunion, a multiple-day event with a meeting at the Computer History Museum. In addition to seminars and a group tour of the exhibits, a catered dinner, a briefing on the upcoming 3000 emulator, and a meeting of enterprise resource planning software users made for a busy weekend with dozens of community members.

Alan_Yeo_at_Reunion
Yeo was pragmatic while keeping his lights on for every software customer who’d invested in his products. Marxmeier Software has taken over support and services for ScreenJet Ltd. in the wake of Yeo’s death. ScreenJet and Marxmeier Software have had close ties for a long time. Yeo was a valued board member for Marxmeier Software and Michael Marxmeier is a director at ScreenJet.

To ensure the continuation of ScreenJet products and services, as of June 2019 support, license renewals and upgrades have been administered by Marxmeier Software. "This will not affect any ScreenJet customer product licenses or agreements which will remain with ScreenJet Ltd," said Marxmeier. "The teams at ScreenJet and Marxmeier will combine their long time experience and resources to guarantee efficient and reliable ongoing support and services."

Alan Yeo with dogsWith his beloved dogs at his Gloucester home

Ever-prepared, Yeo worked out the details of a smooth transfer over the months when his cancer recovery had failed. He'd rallied after treatments and recovered enough to race vintage cars on rural road rallies in 2018. In his last months the disease progressed to cut off motor functions of one arm. He resolutely typed long messages one-handed.

Failures were always a topic he could approach with candor as well as compassion. “Most software on the HP 3000 was too expensive, compared with other platforms,” he said in a 2004 interview examining the collapse of HP’s ecosystem. “However, because people could reliably write applications for the system, many of these were developed far too cheaply. Many customers got far too much for the money they actually spent.”

A reach for personal connections

The ScreenJet product was a recovery from a valiant effort to make the 3000 a vital part of the dot-com PC world. Millware was to deliver software that gave 3000 customers a way to make their VPlus interfaces behave like modern graphical interfaces. The software was to be free in exchange for giving over some of the screen real estate to messages from vendors. Before that user base could be established, dot-com computing staggered, a blow to the vendor element of the formula.

Yeo also picked up the pieces from the effort to market ScreenJet, developed as a connectivity product and sold by Millware.com until that marketing company went bust during the dot-com implosion. ScreenJet earned an award for migration solutions from Acucorp. But for all of his effort toward helping migration customers, Yeo was clear-eyed about 3000 transitions. ScreenJet achieved its best technical release just one month before HP announced its withdrawal from the 3000 market — and the product’s development up to that point was not driven by any need to move companies away from the platform.

Yeo also took a role as producer in a new feature for 3000 customers long abandoned by HP: Transact users. The advanced development language was kicked to HP’s curb in the middle 1990s, but sites continued to run extensive Transact applications, long after the “strategic” badge fell off the language. The TransAction software from his team give Transact sites service and tools to move programs to COBOL, a way to prepare for the journey away from the HP 3000.

Marxmeier, who reached out to break the news about Yeo's death, said he would miss his ally's organizational gifts, but even more so, Yeo's ability to write and speak with, well, eloquence. After drafting a heartfelt letter to inform the ScreenJet customers about the founders' demise, Marxmeier said he already felt a gap in the story. "It's something I would have liked Alan to read, before I released it," he said.

Yeo said he wanted no florid speeches of eulogy at his passing. Months before he died, he said if there was any afterlife at all, "I could be a little sprite, one who could occassionally make it rain on somebody who was being pompous, that would do me quite nicely." It's fair to say his narrative for the 3000's transition era was rich with the words that rained on misfortune and miscalculation.

Carly_cartoon_dalmations


How to make databases live past shutdown

Index card file drawer
Photo by Maksym Kaharlytskyi on Unsplash

In 2011, a systems manager for the power utility at the City of Anchorage was looking toward a shutdown of the municipal HP 3000. It's a situation that surfaces from time to time even now. Back in 2011, the manager could see another 10 years of useful service for the 3000. His management had other ideas. This might sound familiar.

Wayne Johnson said, "We have an HP 3000 that we are going to decommission, sadly. I have powers that be who want it turned off sometime next year, although I think it will be longer than that. Is there a service that will read DLT IV tapes or convert them to some other usable format on a Windows platform or some Unix server?"

He went on to say that most of his data files were TurboImage database files. They were for archival purposes only. "Of course, the simple solution is to run the HP 3000 N-Class, probably for the next 10 years. It never goes down. But that call is not mine to make. They want to unplug it."

Alan Yeo of ScreenJet supplied a database tape migration solution that still works today.

"One very simple but elegant solution is to get a copy of Marxmeier's Eloquence database which is very inexpensive for your choice of Windows, Linux, or HP-UX and just load the databases in. Then either with the Query3K tool or with ODBC, you can just access the data as and when required.

"You could copy the volume sets to Network Attached Storage. I'll make a bet that the smallest NAS device you can buy for less than $400 will comfortably store more data than you managed to create on the HP 3000 in its lifetime.

"Allegro has a product, Rosetta Store, that will directly load Eloquence from databases in STORE format on tape, if you want to skip the step of restoring from the 3000 tapes and then unloading for import into Eloquence. I think the Allegro product will also do flat file conversion."

Beyond the Marxmeier and Allegro software, there was another suggestion offered in 2011 about a product that has come to change the way MPE databases live on beyond hardware shutdown. HP's iron, after all, isn't the final resting place for 3000 applications and data.

Continue reading "How to make databases live past shutdown" »


Who's to blame when the lights go out?

Power-lines-towers
Photo by Peddi Sai hrithik on Unsplash

Yesterday the lights didn't come on in Northern California. Everywhere, it seems, because the Pacific Gas & Electric corporation didn't want to be sued for windstorm damages to its power lines. They cut the juice to prevent lawsuits. Tesla owners got a dashboard warning.

The surprise about the outage was as complete as the shock over Interex dowsing its lights overnight in 2005. Except the cynics could see the PG&E blackout coming.

Solar panel-owning residents of California and electric car owners were most surprised. I went to a 3000 tech mailing list to look for people worried about topping up their Teslas, because some people who picked 3000s are pioneers, so Teslas are well represented among MPE veterans. Like the usual chaff on a mailing list, there were turds of political opinion floating there about who's to blame for California's darkness.

So I wasn't surprised to see more attacks on the state of California. "A third world country" is the shorthand smear, although you can say lots of the US isn't a first world country any longer. In the exchange on the mailing list, it was apparently too much trouble to keep a state’s government separate from talk about Pacific Gas & Electric’s corporate moves. Once PG&E goes bankrupt, then the private corporation’s demise will be blamed on California voters, using that logic. It’s easier than keeping commerce and government separate, I suppose. 

Blaming the tough regulations about state rate hikes for the disaster that is PG&E business is having it both ways: Government is crucial, and government is ridiculous. On and on it goes, until we are supposed to trust a government that lets PG&E do whatever it wants, so long as profits stay high. 
 
Because every corporation with ample profits has always taken care of its customers in every need. 
 
Some people on that mailing list sure have a short memory about such nonsense. We are all survivors of a meltdown of a business model where corporate profits were ensured — because revenue growth was the only thing that mattered — while legacy technology got scrapped. Millions of dollars of investments, the fate of hundreds of vendors, and thousands of careers were lost.
 
The mailing list name still has the numerals 3000 in it. You’d think people would remember what brought us into each others' lives, along with the lesson we learned the hard way together. Oversight is important. The problem which hit the Hewlett-Packard 3000 customers was a lack of oversight from top-level management and the board of directors. It's sometimes hard to know what to do while things are changing (the computer business) and ambitions are high (make HP bigger than anybody, so it will win every deal).
 
A good rule to follow, though, is like a physician. First, do no harm. The 3000 community got treated by HP like a limb that had gone gangrenous. Old history that'll never be changed, yes. Also, a lesson for managers on how to treat older bodies like an operating system and software that's not new but is still performing well.  
 
Complaining about oversight, when you'd rather have none at all, is what got HP into the state it's in today. Two corporations, neither growing, both unable to honor the promises of forever-computing that drove companies to buy its products. HP's cut itself loose from the future of OpenVMS, and the thousands of companies that rely on that legacy OS need to trust VMS Software Inc., new owners of the OS's future.
 
It's a better deal than the one HP gave its 3000 customers. Private money would've taken over MPE futures in 2002. HP wouldn't sell or license it, but again, that's just history. Now that the lights aren't going on for the 3000 at HP anymore — so many of HP's 3000 web pages are dead or buried alive — it evokes the powerless situation in California.

Continue reading "Who's to blame when the lights go out?" »


Debugging the diagnostics

Fire-ant
Photo by Mikhail Vasilyev on Unsplash

The Command Support Tools Manager (CSTM) replaced SYSDIAG as of MPE/iX 6.5. Managers who are keeping MPE/iX working here in 2019 rely on CSTM, just as they did SYSDIAG before it.

There's evidence out there that CSTM has problems while running on 6.5 MPE/iX systems. One well-schooled developer recently noted while trying to run CSTM on his MPE/iX system that the diagnostic told him on startup, "an error dialog could not be built to display an error."

The developer community suggested a few fixes for this problem with the diagnostic software. CSTM was ported onto the HP 3000 from HP-UX, so the repairs that CSTM itself suggested regarding memory (increasing it, removing processes, reconfiguring kernel memory limits) probably don't fit.  CSTM has a special page in the Hewlett-Packard Enterprise website devoted to the problem.

The developer at least had another 3000 running the same version of MPE/iX, a system where CSTM was starting up without a problem. One bit of advice suggests that while using console debug, "check out what a your working system looks like at the CSTM prompt when idle. Use psuedomap “XL” to get symbols from the libraries and program. Attempt to set some breakpoints near initial program launch."

Using DEBUG, the open heart surgery of HP 3000 management, is sometimes a required diagnosis. When your diagnostics software requires diagnosis, nothing but DEBUG will get the job done.

Much more detail followed on using DEBUG to discover what's failing in CSTM.

Continue reading "Debugging the diagnostics" »


Shrink ray 3000 services: what you'd pay

Lens-shrink effect

Photo by Stephen Kraakmo on Unsplash

The number of MPE and HP 3000 experts is declining. It could hardly go in any other direction but downward, given the age of the expertise. There's still a number of companies — no one is sure how many — using the servers and wondering how they'll get along when something goes wrong.

One solution that's been successful up to now is shrinking the footprint of resources needed for using MPE/iX. Rather than each customer using up environmental conditioning and physical space for a server, owners of 3000s can have their systems hosted in a centralized location. It's co-location, but offered by companies which have MPE/iX and 3000 experience. The latter is most important because the components in an HP server are specialized. 

Good answers for hardware issues are the prize in a shrink ray hosted offering. Browsing the postings on the 3000-L newsgroup this month, I'm struck by the number of questions that are not only specific to MPE, but focused on component problems. Sending a 3000 off to a co-located datacenter has been offered for many years by now. The Support Group, an Austin-area firm for helping MANMAN owners, built a disaster-proof datacenter on its site that houses 3000s from customers.

There are others in this market who do the same service for 3000 owners. Beechglen Development has services that will harbor a 3000 and take the computer out of the everyday management stream for participating companies. Solutions for reducing the 3000's footprint to zero, while keeping MPE apps at work, use the shrink ray effect.

Less easier to measure: what such shrink ray services should cost, or what the remaining 3000 owners would be willing to pay. It's far better to imagine the cost of that fading HP iron becoming unresponsive, as they like to say when you're holding the line on life at an advancing age. Good resuscitation can be priceless; that's why people move into continuum of care facilities in their most golden of years.

A good friend has moved into one of the best independent living facilities in Chicago. When she had a heart scare this summer, though, she was able to get to a hospital through the help of her friend. Returning to her apartment the next day, she checked in with the facility director to see if the building's staff might look in on her that night. That's assisted-living, she was told, not independent living.

Some of the 3000 hardware still in production is too old for independent living. Shrinking it before sending it to assisted living is a good first step. Reducing a footprint, by shipping it away to a support company with a disaster-proof datacenter, is the shrink ray magic that can keep MPE alive for years to come.


Making a place for retired 3000s

Owners of HP 3000s are facing the end for their HP hardware. The MPE/iX software has a longer lifespan than the components that have carried it. Even in places where the apps will live on, the hardware is deteriorating. What to do with the aging iron is a question coming up more often.

The HP hardware isn't disposed of easily. It's got the same kind of environmental hazards as every other computer: rare minerals are the prize in there, but there's lots of the weight of a 3000 system that's just going to be classified as scrap.

In any conversation with an owner of a 3000, the solutions to this issue revolve around a reseller-broker. These third party companies have made a business of moving 3000s in and out of datacenters. Lately the movement has been almost exclusively outward.

In the reports from the field we've heard, used hardware often has little value unless it's from the latest generation of 3000s. There are individual items that still will return some dollars to the sellers. K-Class MFIO boards have become rare, and since those components prop up the older 9x9 servers, the boards can carry value that might be equal to a complete system of the A and N-Class generation. 

Used hardware has always been a marketplace with great malleability in its value. It's been a lot like being a coin collector for 3000 owners. The valuations might say your 969 should be worth $500, but you'll only get that from a buyer who can sell your coin for more — or one who needs the hardware enough to deliver that price.


Relative performance online as 3000 history

Snapshot of partial HP relative performance
As the HP hardware to run MPE/iX ages, it's on the recycling and scrapping block for companies that still have an HP 3000 box on-premise. Now hardware is so cheap you can throw 3000 gear away.

The slow, old, and heavy boxes go first, of course. I remember taking a trip with Stan Sieler in the Bay Area where he took me to a scrap facility. There, shrink wrapped on the outside of a pallette, were HP 2645 terminals, right alongside Compaq boxes.

Relative performance charts can be our friend as we triage our older HP gear. There's an adequate one available online at bitsavers.org as part of a breezy page covering the history of the 3000. 

We've got The One Chart to Rule Them All you can download to use while you have HP's gear on the chopping block. There's a section for A-Class comparisons, and another compares HP's boxes in the N-Class line to older system performance.

Such numbers are relative in more ways than just the comparison between servers. HP actually massaged the numbers themselves back in the late 1990s. Our story in 1998 reported that 

HP is “restating” the performance rankings for much of its hardware, starting with this month’s rollout of the Series 989 systems. The new rating is an HP 3000 Performance Unit, not based on Series 918 performance. And the new numbers are between 29 and 52 percent higher for all systems except HP’s largest ones, the Series 996 and 997 units.

As I observed, while looking askance at the new figures, "HP wants you to think of HP 3000s as faster than ever, but its new rating measurements don’t really make existing systems any faster. They just sport higher numbers than they did last month."

There was some technical logic to the HP adjustment. The 3000 hardware from HP had just acquired some newer and faster cousins.

Dave Snow, product manager for the 3000, said "the measuring techniques for our midrange and high-end platforms were producing results that were not consistent with each other. You had a 918 performance for the midrange and a different relative performance for the high end, but the two relative performance numbers weren’t the same.”

The discrepancy was a big deal, he added, “but it was a big deal we could sort of live with, so long as the 9x9 and 99x performances were dramatically different from each other,” Snow said. “As we added performance to the 9x9 platform, it is approaching the 99x. That’s caused us to have this quandary. In some sense we’ve had two different sets of 918 numbers. We had to bite the bullet and reconcile the numbers."


TBT: The Flying HP 3000

3000 Crash Test
Twenty-two years ago this month, HP thought enough of the 3000 to send it flying off a three-story rooftop. It was called the HP 3000 Crash Test. The demonstration was more like the tests conducted with safety dummies than anything from a software lab.

HP spent some of that year celebrating the 25th Birthday of the 3000 with fun stunts like this. The rooftop trip was called a skydiving event. Alas, no parachute.

A dazzling disco evening played out in Stuttgart during the same month as the Crash Test. The Europarty was held not far from the Hewlett-Packard manufacturing facility in Boeblingen. That soiree featured a saxophone player riding on a zip-line. Different times then — but maybe the 3000 was ahead of its time with a zip-line at a party.

The Crash Test was similar in its mission to make us smile. It also proved a point about the hardware that people can't seem to get rid of by now -- the boxes were built to withstand remarkable abuse. For example, Joe Dolliver told us about another Lazurus-like performance of HP's gear.

Back at Amisys in a previous life, Bud Williams sent an HP3000/957 to the Amisys Dubuque programmer office back in September of 1999. The system was there for Y2K issues testing for the staff in Dubuque. It was sent via North American Van Lines.

As the story goes, the system got crushed by another heavy skid of material and the 3000 looked like Gumby with broken sides and smashed connectors. Another 3000 expert, John Schick, got the box in place and the system ran fine. Yet another story of the HP 3000 taking a licking and still ticking.

The last line is a reference to a TV ad for Timex watches, a reference too obscure for anyone who's in charge of a datacenter today. The Crash Test lives on as a movie on the Newswire's YouTube page. When we started all of this, just about 24 years ago, YouTube was just a magic act in the mind of some wizard working for what would become Google. Instead, HP distributed the movie via VHS cassettes: perhaps another reference too old for the junior programmers on staff now, working on their virtual servers in the Amazon AWS cloud.

Continue reading "TBT: The Flying HP 3000" »


ERP Tips: Using work orders to backflush

Pipe-and-plumbingPhoto by Samuel Sianipar on Unsplash

MANMAN still runs operations at companies around the world. Not a lot of companies, of course. It's 2019 and everything is smaller in size, not just your hearing aids. The MANMAN managers are still looking for tips. Here's one generated from a question out of the Altra Industrial Motion Corp. from senior systems analyst James English.

We are on MANMAN version 9.1 on an HP 3000. We have all MANMAN modules, including MANMAN/Repetitive. Is it possible to backflush work orders without using Repetitive? Our one manufacturing location is looking at simplifying work order transactions. They are manually transacting each operation on their work orders, even though they don’t collect actual hours.

Short question: How can they use work orders instead of using Repetitive?

When a work order has been received into stock, it comes to the scheduler-planner to push the times through each sequence, since the operation no longer does time cards. Once that time-pushing is done, the work orders are closed for material and labor. Once a work order is received into FG, instead of pushing the time through each operation, could we just back flush?

Alice West of Aware Consulting says

You can set all the components on your bill as “consumable” and then when you complete the WO the system will consume all the materials.  We always called this feature “poor man’s Repetitive.” 

However, it sounds like you are trying to simplify the labor portion of the transaction.  For that, you can look at your COMIN variable settings. Here is a chart I put together to show how 3 different variables work together.

Continue reading "ERP Tips: Using work orders to backflush" »


Super summary: How 2028 challenges MPE

Joshua-earle-tUb9a0RB04k-unsplashPhoto by Joshua Earle on Unsplash

Editor's note: More than five years ago, Denys Beauchemin outlined his view of the future at that time for the upcoming 2028 date changes in MPE/iX. The years since then have given 3000 users several solutions for 2028. There are ways to keep using the 3000 into the year 2038, the year when Unix systems will face this kind of challenge. The technical challenges the 3000 solutions overcome are very real. Denys wrote this back in 2014.

It's December 31, 2027. The MPE/iX CALENDAR intrinsic uses the leftmost 7 bits to store the year, offset from 1900. But just like Y2K, the effect will start to be felt earlier than that as dealing with future dates will yield interesting results.

For example, using the standard CALENDAR, your new driver's license will expire in -46000 days when you renew it in 2026. Back in 1986, I was writing an article about calendars and Y2K for Supergroup Magazine. I changed the date on an nearby 3000 one night and let it cycle to January 1, 2000, just to see what would happen. The date displayed was funky and I noted a few other things, but I had to reset the clock back quickly for obvious reasons.

I wrote up those findings in the article and closed with something about HP having 14 years to fix it. The 2027 thing is much more difficult to fix than Y2K and given the state of HP support from MPE this millennium, it may not get fixed in time.

The issue is very simple. The calendar intrinsic returns the date in a 16 bit word. That format is basic to the HP 3000 and has been around forever. You could conceivably change the algorithm to make it offset from 2000, or 1950 or whatever, but all the stored value would instantly be incorrect. 

You could decide to rely on something like the Y2K trick of anything less than 50 is offset to 2000 and anything greater than 50 is offset to 1900. I still think 2028 is the final death date of the HP 3000. But I could be wrong, and do not want to stand in the way of someone trying to fix it.


More 2028 date help on its way for MPE/iX

January calendarPhoto by Kara Eads on Unsplash

3000 managers are still asking if the year 2028 will be the first one where MPE/iX can't run. The date handling roadblock has been cleared already, both by internal app software adjustments (MANMAN sites, worry not) and also through a third party solution from Beechglen. 

If you've had the Beechglen experience, we'd like to hear from you. The software has been in the 3000 world for almost a year and a half by now.

Beechglen holds one of the Select Seven licenses for MPE/iX source, as do Pivital, Adager, and several other active 3000 vendors. Not much has been discussed about how 2028 has been handled by these solutions, but 3000 owners are such a careful bunch that you can be sure there's been testing.

One source of date-testing software is among the Select Seven. Allegro created Hourglass for the Y2K date hurdle. It rolls date controls forward and back across any user-designated threshold for testing. Hourglass might already be in a lot of the remaining homesteaders' 3000 shops. The ones who still rely on MPE/iX make up a crafty, adept group.

Reggie Monroe manages the HP 3000 at the Mercury Insurance Group in Brea, Calif. He asked on the 3000-L mailing list if his MPE/iX was going to stop running at midnight of Dec. 31, 2027. Several other managers and vendors assured him that MPE/iX has a lifespan beyond that date.

"It doesn't stop running," said Neil Armstrong at Robelle, "but the dates will be incorrect — however, a solution is already available and a number of us vendors have resolved this issue in our software to continue to 2037." Armstrong pointed to an article at Beechglen for some details on one 2028 software workaround.

The latest solution is coming from Stromasys. The company has been referring its emulation customers to third party support for the 2028 fix. This week we heard there's a Stromasys-based workaround on its way, too.

Tracy Johnson suggests a fine idea for anyone who chooses to ignore the year that MPE/iX will report automatically starting on January 1, 2028. The 3000 will roll back to the year 1900 on that day. If you reset the 3000's date to the year 1972, or 2000, then the days of the week will align on the same ones in 2028. The year 2028 is a Leap Year, just like the ones in '72 or 2000.


How HP-UX has now helped MPE/iX users

Sam-warren-engine-block
Photo by Sam Warren on Unsplash

HP always had multiple operating environments wired into the design for PA-RISC systems. Now there's evidence that the vendor's deep engineering is paying off. Some of that benefit is even flowing down to HP's MPE/iX users.

This week we've heard that Stromasys is praising the improved performance of the company’s HP 3000 emulator Charon. Turns out the engineering the company had to do recently to make Charon ready for HP-UX PA-RISC servers has been a blessing for the MPE system emulation.

Every time software is revised, there's a chance for a little learning, or a lot. Creating an HP-UX edition of Charon was funded by the potential for new Stromasys sales.

HP-UX systems — the ones that run PA-RISC — could be a big new field for Stromasys to explore. Extra Stromasys attention to HP users, though, is a plus for HP 3000 sites. Stromasys is in several markets: Digital and Sun servers are both markets bigger than the HP 3000. A second set of HP customers will mean that good decisions will be easier to make when HP-related software engineering is required.

Maybe it's like being a Chevy Volt owner, as I am. Chevy stopped building and selling the Volt in March. But the Voltec engine, a marvel of blended electric and gas, is part of the new line of Chevy Electric Vehicles. Good news for us Volt owners whose cars are powered by the Voltec. That PA-RISC engine in your datacenter is getting more attention this year, lavished by the company which is emulating that HP design.

 


Dog days were always part of 3000 summers

Stealing_Home_Front_Cover_July 12_kirkus
A summertime gift, ready to play on your ebook reader

It's August and it's quiet in Texas. Step outside any building at 3 in the afternoon and you're struck by the silences. The birds know better than to chirp, the only sounds on the street are the wind ruffling along the curbs, and the hum of AC units and pool pumps boils down from the yards with stunted grass.

It's 104 out there, a summer that tamps down just about everything until after the sun sets. Things don't move much, a situation that was usually at hand during the last three decades and more of 3000 history.

We'd all wait for the middle or the end of the month of August, or sometimes until September, to hear the beat of each others' feet down hallways. There was the national conference to attend by then, the one called Interex for many years, then HP World once Hewlett-Packard sold the idea to the user group of branding the show around the vendor, instead of the user group.

That conference, whose heartbeat pulsed on the exhibits floor, was such a landmark we'd plan vacations around it. Rare were the years when the community gathered before the second full August week. People got their kids back into school right around conference time. Then we'd appear in person to learn our trade and our tech world's future better.

There's an annual conference in my life again, now that a user event is a rare MPE experience. The Writer's League of Texas Agents and Editors Conference brings authors together with book agents. Along the way, they stop by a trade show booth where I chatter about stories like I did in spots like San Francisco (three times) Detroit (only once) and Orlando (in a Florida August we endured like a database reload, waiting for the end of the heat).

I'm an editor anew at that conference, and this year I have a book of my own to debut. It took its opening cut at the plate during that authors' show. Stealing Home: A Father, a Son, and the Road to the Perfect Game was six years in the making. It's the story of an 11-day, 9-game road trip with my Little Leaguer in the final summer before the NewsWire came into the world. It was 1994 and the annual conference was almost as late as it's ever appeared: Sept. 25 in Denver. It snowed on the last day of the show.

Earlier in that year I was a divorced dad taking my best shot at being a full-time parent. In search of the perfect vacation and overcompensating like any divorced dad, I looked at my own history of being a son of a man who was epic himself. Then he took his own life and I drove away from the memory of that loss. The summertime trip in a rented convertible with my son was my best effort at remembering my dad, answering questions about why, and finding the path to make my road ahead a more peaceful place.

We can't change the past, but we can better understand it with earnest study. Every time August arrives I think about the summers where all of us came together to try to understand MPE, or HP, or just whatever new morsel was rolling off of data sheets and publication pages.

We call these dog days out of habit, a phrase that most of us don't know refers to the first rising of the Dog Star. I have a star to lift up with my memoir. I hope my readers here will download it, enjoy it, and leave some kindnesses in the review margins. I'm still pleased to find the constellations that continue to rise in our 3000 world. Like we always did in August, I hope to bring along a few new readers and tell a new story with words and pictures. Thanks for reading, clicking, and downloading my stories.


CAMUS gives the 3000 an Illinois play date

MANMAN 9 plate
The manufacturing society CAMUS is holding a Reunion Day for HP 3000 managers and owners. Since it's CAMUS, this is also a meeting for the Digital ERP users. The Computer Aided Manufacturing User Society, after all, is wrapped around MANMAN, for most of the attendees.

This is only the second meeting in as many years for MPE/iX users in North America. Last summer, the faithful and well-studied 3000 folk in Silicon Valley spent an afternoon at a famous pub across from the old HP campus on Homestead Road. There were songs and classic videos, plus a lot of talk to catch people up on their lives. A slide show caught people up with hardware maintenance.

Duke Reunion 2018

This year's event is Sunday, August 25 in 3 PM in Addison, Illinois, a town among the western Chicago suburbs. At the Dave & Buster's at 1155 N. Swift Road, Terri Lanza and Keith Krans will hold down a party room at the popular game palace and sports bar and restaurant. There's a buffet included with the $20 ticket, plus access to a cash bar. Lanza needs a count of attendees by August 19, so she can fully prepare for the buffet.

Lanza has a history of gathering 3000 folk. She started up the party in 2011 when CAMUS gathered as part of the HP3000 Reunion at the Computer History Museum. CAMUS had its event at a nearby hotel. That remains the best-attended event so far in the post-Interex era. A meeting in 2007 gathered a healthy array of anxious and resigned attendees. Vendors and support consultants are always in big number at these gatherings. Both of those post-Interex events were propelled by the enthusiasm engines of Alan Yeo and Mike Marxmeier, of ScreenJet and Marxmeier Software AG, respectively.

This year's reunion runs until 9 PM. Registration is by email or phone to Lanza ([email protected], 630.212.4314) or Krans ([email protected]). They also have advice and tips on where to stay for attendees arriving from out of town.

Meeting in person can connect you with a resource to help maintain a 3000 and forestall the ultimate migration 3000 sites face. Being in a room with others who know the 3000, the old HP which loved the server, and the legend of MPE — that's special. The 3000 was always a marketplace with a vibrant, personal community. This was a big part of our decision to deliver NewsWire to the market during a summer 24 years ago.


Making the numbers work for emulation

Screen Shot 2019-08-02 at 1.05.57 PM
Over at Stromays, the creators of the only PA-RISC virtualizing software for MPE/iX machines don't call what they do emulation. It's referred to as conversion. Using Charon converts hardware requirements from HP's 10-year-old PA-RISC boxes. The needs for MPE/iX become powerful Intel servers.

It might seem simple to see that and figure it will cost less to maintain MPE applications using Charon. A new calculator on the Stromasys site makes those numbers add up.

Even a simple calculation that has you paying no more than $650 a year for support can be a candidate for significant savings. A four-processor N-4000 probably won't have support that costs that little. But even if it did, the calculator says that a 3000 owner can save more than $52,000 by getting away from that old hardware. 

We're looking closer into the methodology that drives the calculator. At the moment it seems that the more you pay for maintenance, the lower the savings will be, so we'd like to know more about that.

An N-Class server can be bought for far less than the $52,000. So a 3000 manager might be tempted to reach for replacement N-Class HP hardware instead of virtualization. That's a solution which will work exactly once, though. When that hot-swap replacement HP gear fails, you're back to square one. You won't save on power or footprint, either, in that swapped in HP gear scenario. And there's the matter of finding another N-Class box.

 


Make that 3000 release a printer grip

Fist-artwork
A printer connected to our HP 3000 received a "non-character" input and stopped printing. The spooler was told to stop in order for the queue to be closed and restarted. When we do a show command on that spooler, it reports " *STOP .......CLOSING CONN " How do I force a close on the connection? The HP 3000 is used so much it can't really be shut down any time soon.

Tracy Johnson says

If it is a network printer, just "create" another LDEV with the same IP. The 3000 doesn't care if you have more than one LDEV to the same IP (or DNS). Raise the outfence on the original LDEV. Once created, do a SPOOLF of any old spool files on that LDEV to the new LDEV. You can do it in a job that reschedules itself if it persists. The first spool file still in a print state will probably be stuck, but this technique should fix subsequent spool files. The situation probably won't go away until the next reboot.

We've had our full backup on Friday nights abort several times and are not really able to discern why; sometimes it works while other times it doesn't. As a test/fix, we're swapping out the “not very old DLT tape” for a brand new DLT tape to see if that makes a difference. Our daily, partial backups work just fine—each day has its own tape.

Mark Ranft says

Let's talk tapes. How old are these unused new tapes? From my experience, new tapes and old tapes both have issues. I would not call a tape that was manufactured years ago, but hasn't been used, "New." It is still an old tape. But an unused tape will have microscopic debris from the manufacturing process. It may work just fine, but be prepared for more frequent cleaning if you are using unused tapes.

Old tapes are tried and true. That is, until they start stretching and wearing from overuse. If it was my STORE that failed, I would start by cleaning the drive. And cleaning cartridges can only be used a specific number of times. That is why they come with the check off label. After the allowed number of cleanings, you can put them in the drive but they don't do anything.

I was told by a trusted CE friend that cleaning a drive three times is sometimes necessary to get it working again. I don't know the science behind it, but that process did seem to save my behind more than once. After cleaning, do a small test backup and a VSTORE. Try to read (VSTORE) an old tape.


Compromises throw doubts about clouds

Thunder-cloud-3554670_1920

Cloud services show some promise for companies which are dropping their on-premise IT hardware to get costs down and put maintenance in the hands of service companies.

As the HP hardware ages, its reliability becomes a weak point. There’s a risk to using clouds, though, one that the 3000 community knows well and holds dear.

Outside services can be vulnerable to security attack. When the attack takes place outside a datacenter, the responsibility falls to the manager who selects the service.

A hacking campaign known as Cloud Hopper has been the subject of a US indictment, one that accused Chinese nationals of identity theft and fraud. Prosecutors described an operation that victimized multiple Western companies. A Reuters report at the time identified two: IBM and Hewlett Packard Enterprise.

Cloud Hopper ensnared at least six more major technology firms, touching five of the world’s 10 biggest tech service providers. Reuters also found compromises through Fujitsu, Tata Consultancy Services, NTT Data, Dimension Data, and Computer Sciences Corporation.

Another compromise pathway was DXC Technology. HPE spun-off its services arm in a merger with Computer Sciences Corporation in 2017 to create DXC. HP's Enterprise group represents one-fourth of all the known compromised Cloud Hopper attack points.

Assurances that a cloud is secure come with references, but the degree of safety remains largely in the eyes of the beholder. There’s not much in the way of audits and certifications from independent reviewers. MPE cloud computing is still on the horizon. Reports about unsafe clouds are helping to keep it that way.


Was a 3000 ever a personal computer?

Screen Shot 2019-06-27 at 7.14.50 PM
The information trotlines stay in the water here. I watch for mentions of HP 3000s in the wide world of the Web, using Google to automate the surveillance. Sometimes there's a bite on the trotline that nets a real report. Other times the phrase turns up stories about horsepower in autos and other motors. Searching on "HP" will do that.

For the first time, though, the Google net trawl picked up a story about a 3000 from another dimension. This would be the realm where everything a manager wished for in a business server was delivered — and long ago. I came into this market when MS-DOS hadn't yet reigned supreme, destroying all others but Apple. HP sold a PC in 1984 with a touchscreen, something a few steps away from being a tablet.

The report from a website was wired into that deep desire that MPE could be personal. 247 WallSt included an article identifying a 3000 as a personal computer.

Once wildly expensive and inaccessible but to the very rich, computers today are one of the most ubiquitous technologies worldwide. The most basic model of an HP 3000 sold for $95,000 in 1972, the equivalent of slightly over half a million in today’s dollars, but not all personal computers released in the early 1970s cost as much.

The sentence starts off well enough, with a 3000 selling in 1972. A handful did. By the time the price is reported you can be sure the story has run off the rails, since nothing connected to computing with MPE was sold for under six figures at first. HP found a way to drive down a 3000's sticker price to about $12,000, 25 years later. That device, a Series 918 DX, was closer to a personal computer in power.

What's an HP 3000? The question is still posed, once in a while, when a redoubtable and virtually invisible server is discovered under a staircase, chugging along. It certainly is not a PC, and it has had more of a string of successes than attributed in 247 WallSt.

The original 3000 was generally considered a failure, but the company would go on to make 20 different versions of the 3000 through 1993.

In some places the server still working at Fortune 500 corporations is considered a failure by now, because its vendor gave up on it. That understanding is as off base as thinking that computer in the picture above could be a PC. It was Hewlett-Packard's "first foray into smaller business computers," except for the smaller part. Making a mainframe's computing available in a minicomputer size might have been smaller than IBM's 360s. The 3000 is the first step HP took into business computing, full stop.


Being there now, right where we expect him

Birket-Chamber
Where Are They Now
?

Fifteen years ago, Birket Foster had an opening line for a history of the 3000 world. "It was a marketplace of names." Birket's is one of a group of well-known first-only names, along with Alfredo and Vladimir and Eugene. Earlier this spring he commemorated 42 years in the market. Every one has included a week of business serving HP's business server community.

In a few days he'll be doing what he's done, and in the same places, as he's done for years. There's a webinar that covers the promises and practices of application modernization and synchronization. Systems that look and behave like they're old are made new again. You can register for the June 12 event, to be held at 2 PM Eastern.

Right at the heart of the MB Foster business, though, pulses UDACentral. "We have completed its shakedown cruise at the Government of Canada in a BCIP program, and of course are moving another group of databases for customers that contract MBFoster to do the work using UDACentral."

Moving and managing data has always been at the center of MB Foster's competency. "We have been adding databases to the mix: Aurora (for AWS) and MongoDB are now part of what we are serving. We even did a paid Proof of Concept for UDASynch taking MongoDB back to Oracle."

The company's core team has been steady, but what's ahead is pushing UDACentral's wide array of improvements "to change them from a project to a product. That process will need additional sales talent and trainers, as well as more support and programming talent, so my hobby is expanding again." That's a hobby of assembling resources for new ideas.

In the meantime there is family life for Birket, the pleasures of two daughters and a son already old enough to be expanding and embracing lives in medicine and business, as well as building families of their own. Fishing the Ottawa River's massive muskies remains a passion, one he's pursuing this summer with HP 3000 tech guru Mark Ranft. Birket often has a hook in the water.


Third parties take over HP's OS support

Aircraft-instrument panel
The above headline doesn't describe a new situation for MPE/iX. HP gave up on its 3000 support, including MPE/iX, at the end of 2010. Even allowing for a few shadow years of 3000 contract completion — the time when some support contracts were running out their course, and HP ran out the clock — it's been a long time since the 3000's creator supported a 3000 system.

That's a situation that's about to kick in for the hundreds of thousands of VMS systems out there. HP's official OpenVMS support ends in December of 2020. A third party company, VMS Systems Inc., has earned a license to support VMS using its internals knowledge and experts. The company, VSI, will also become, by July, the only outlet for an OpenVMS customer to buy OpenVMS.

The 3000 customers already know how well third party support can succeed. VMS customers in the US government are going to learn how well it works for them. The Federal business in VMS was big.

This third party stewardship and development was the spot the 3000 community could never reach. The OpenMPE movement began as a way to get a third party group the access required to advance MPE/iX with features and new patches. That ground along for more than three years until HP announced it was extending its 3000 "End of Life" in 2005. The air quotes are needed before the only life that was ending was HP's life serving 3000 owners.

So any takeover of MPE/iX internals for extension and future customers' needs was out. So it then fell to the community to ask for enough access to do deep repairs and issue patches. Ultimately that license was created, sort of. Not the kind of access that VSI got for VMS. Just enough, for the seven special companies with an MPE/iX source license, to repair things for existing support clients.

It amounted to a CD with the millions of lines of internal MPE/iX code. The documentation was limited to what was inside the source file, according to some who saw the CD. One report said it was a $10,000 license.

That MPE/iX source goes above workarounds. Lots of the potential from extra source access has not been tapped after all of these years. But good customer-specific fixes have been built.

This is so much less than what the VMS community — which was in the final analysis what helped end HP's 3000 life — is getting now and in the years to come. Lots of years, because like the 3000, the VMS systems have Stromasys virtualization.

Because the VMS community was so much larger than the MPE community during 2001, and VMS had extensive government installations including Department of Defense sites, VMS won out. VMS got the engineering to support Integrity-Itanium servers. In the long run, we can all see how that mattered. Intel announced the final Itanium build this year. Some wags call the architecture the Itanic.

Many, many VMS sites remain. Everyone estimates, but it's easily a group bigger than the 3000 community ever was. Third party support is all that the OS will have in about a year and a half. That support resource, from independents like Pivital Solutions, been good enough for the 3000 for more than eight years since HP's support reached its end of life.


Get a job, won't you?

Resume Monster
Listening to the radio silence of a job hunt can be chilling. Experts whose lives have focused on the HP 3000 have faced declining options for the past 15 years, of course. The companies' need to upgrade and develop disappears. Then the installed 3000 systems, still serving their owners, don't seem to need professional service. At least not in the opinion of IT management, or in some cases, top management.

So DIY maintenance rules the day, and so the administrative tasks might fall to staff better-trained about websites than IMAGE database schemas, or the means to recover STDLISTs from jobs sent to printers.

The installed applications care about those things, unless they're simply installed for archival purposes. An MPE server should never be on autopilot and mission critical duty at the same time. If the archive breaks down, you can hire somebody to get it running.

That task might be an opportunity for MPE experts. Will Maintain Archival 3000s. Not exactly a new offer. The remaining support suppliers are doing just that, and sometimes more. Archive Support could turn out to be a thing.

Tim O'Neill, whose pondering and good questions have sparked several articles, asked a good question this month. "Can you speak to where the jobs might be and who the talent searchers are?"

The jobs are at the companies still managing 3000 activity on the behalf of 3000 owners. Few of the owners seem to be hiring now. Freshe Legacy was running a big bench for 3000 talent, but it is a back bench. An expert like O'Neill can contact the support companies. Few jobs, though, with actual employment. Lots of contracts, and maybe that's what Tim meant.

Who are the talent searchers? At first, the machines search. The workflow above shows how Monster processes its applicants. Acquaintances and contacts, friends, partners, people who you're hired and now have moved up. Stay in touch at the HP 3000 Community Group on LinkedIn. People who need 3000 help are up there. There's more than 700 in that group. There's a good jobs service there, too. Well worth the $29 a month for the Premium subscription.

The truth is that there's a genuine limit on how much work remains to cover the care of HP's MPE hardware. People will pay for it. The question becomes — is the pay enough to avoid needing to build other IT skills up?


Charon's orbit around our blog's pages

Pluto and its moons
Illustration by Melanie Demmer

With more than 3,200 stories across 14 years of writing, the Newswire blog brims with useful reports. It's big enough that important things can get overlooked. Charon, the Stromasys virtualization software, is just about the most important software product to emerge since HP announced its end-date for its MPE and PA-RISC operations. Here's a recap of the just the essentials we've reported over the last five years.

Taking a Stab at the Size of Your World

The Stromasys software will soon include a Unix PA-RISC edition of the Charon emulator, too. It's designed to bring the same kind of longer future to companies running Unix on the classic RISC systems that HP released alongside HP's 3000 iron. Any additional connection to HP business servers, no matter what the OS, will be good for the future of Charon — and by extension, the lifespan of MPE/iX. That's PA-RISC being emulated there, regardless of 3000 or 9000 designations.

Charon carries Boeing in new 3000 orbit

Charon is a moon of Pluto, so big that Charon is in tidal lock, as one scientist explains it. That moon reminds me of the Charon software that powers those apps at Boeing. Its emulation of the 3000 keeps it in lock with the PA-RISC chips that continued the orbit of MPE/iX at the world's largest aircraft maker.

Northeastern cooperative plugs in Charon

A leading milk and dairy product collective, a century-plus old, is drawing on the Stromasys emulator’s opportunity. A $1.2 billion milk marketing cooperative — established for more than 100 years and offering services to farmers including lending, insurance, and risk management — has become an early example of how to replace Hewlett-Packard’s 3000 and retain MPE software while boosting reliability.

One Alternative to $1 Million of 3000 Costs

Stromasys made its case for how shutting down HP's 3000 hardware can reduce an IT budget. Using data from Gartner analysts and other sources, the company estimates that downtime can cost companies $1 million per year on average.

Newest Charon version brings fresh features

The market is hungry for a forthcoming performance lift from the virtualizer. At Veritiv Corporation, Randy Stanfield will need the fastest version of Charon that Stromasys can provide.

Archival presents prospects for Charon

We're hearing from 3000 sites which are in archival mode with their 3000s, and several such customers have been installing and evaluating the Stomasys emulator

3000 Cloud Doings: Are, Might, and Never

The company selling the Charon virtualizer (many think of it as an emulator) announced a new bundled offer as well as announcing that any public cloud can run Charon. Sites that employ the Oracle Cloud to host their virtualization systems get un-metered cloud services as part of that deal with Stromasys.

Overview compares emulation strategies

There are many ways customers can re-host HP 3000 applications. Virtualization, using the Charon HPA solution from Stromasys, is the ultimate solution discussed in 45 minutes of presentation from MB Foster as it toured rehosting choices.

Making Plans for a 3000's Futures

There are always good reasons to move along to something newer, different, or improved. Emulating a 3000 in software seems to deliver a lot of those, as well as options for backup that are novel.

New DL325 serves fresh emulation muscle

When the Proliant DL325 shipped in July, it was  a newer and more powerful model of the DL380 server — one suitable for powering a virtualized HP 3000 driven by the Stromasys Charon HPA system.


Linux distro not an issue for Charon installs

Linux KVMHP 3000 manager James Byrne has wondered about the kind of Linux used as a platform for Charon on the 3000. His heart's desire has been preserving the ongoing lifespan of MPE apps. For 3000 managers who haven't much budget left for their legacy server, though, here's a matter of spending additional money on a proprietary part of a virtualization solution, no matter how stable it is.

That's not an issue that will hold up Charon from doing its work to preserve applications, according to our Stromasys contact there.

There's an alliance between Linux and MPE as a result of Charon. It also says something about MPE/iX and its continuing value. Stromasys believes as much, investing in R&D that not even HP could get budgeted so it might give MPE/iX a way to boot on Intel's hardware. Extend the value of your apps with fresh hardware, the vendor says about Charon. To this day, even HP-UX won't jumpstart on Intel systems—unless they're Itanium servers. X86-Xeon won't work with HP's Unix. Now there's word of an impending PA-RISC emulation coming for HP-UX for Charon.

There's another issue worth considering in Byrne's organization, Hart & Lyne. The Canadian logistics company has Linux wired extensively into its datacenter. Already having been burned with an HP pullout from MPE, the solutions that go forward at Hart & Lyne must meet strict open source requirements to run in the datacenter. Nobody wants to be caught in a vendor-controlled blind alley again.

Byrne has resisted using something called KVM, and how genuine open source Linux needs to adhere to that product. Byrne described KVM as a Linux-kernel-based virtualization system, and as such it is therefore open source software.

Doug Smith, the HP 3000 Director of Business Development at Stromasys, said KVM isn't a part of the Charon installation set. "KVM is part of the Linux kernel, the part that allows Linux within itself to create virtual machines—kind of like a hypervisor. This is not utilized by our software."

KVM users have strong feelings about following hard-line open source licensing. Byrne's issue is that VMware's software—which isn't required for every Charon install, by the way—looks like it might be operating outside the General Public License utilized by many open source solutions. Managers like Byrne only feel safe inside the bounds of GPL. This hasn't troubled untold thousands of VMware customers.

Continue reading "Linux distro not an issue for Charon installs" »