HP World meetings converge for max MPE effect

SIG-MPE and SIG-Sysman are making plans to merge their efforts on behalf of the HP 3000 customers, and the first evidence will appear at next week's HP World conference in Los Angeles. SIG-MPE chairman John Burke announced that the two advocacy groups, which generated many improvement requests for the 3000's operating system, are combining their meeting times at their Thursday, Sept. 26 event. Line up at Room 406B at 11AM that day, if you're lucky enough to be attending the HP World show, to get regular SIG business out of the way and move on to plans for the future of the HP 3000.

Speakers from HP and OpenMPE, Inc. will be at the meeting. By that time, all of HP's current offers to homesteaders will be on the table -- which may prompt a lively discussion of their completeness, and how they might be improved to ensure customer satisfaction.

Lunch is going to be served at this meeting, as well as the prior day's SIG-IMAGE/SQL meeting, for those attending who have full registrations. Actually, there's likely to be lunch available for other attendees, the ones who can attend the SIG sessions for free by way of their free Expo pass. Interex limits the lunch to paid attendees, but SIG leaders have to reserve lunches in advance, so a few extra are likely to be available. The lunchtime meetings are just upstairs from the LA Convention Center food court, so getting fed while meeting about MPE's future shouldn't pose a problem in any case.

3000 customers heading to HP World should remember to set their alarm clocks early for that Thursday, too. HP's 3000 managers will be sitting at a roundtable meeting, starting at 8AM that day in Room 408A of the Convention Center, answering questions about their plans for the computer line. The meeting will provide direct response for customers to the OpenMPE homesteading news of the day before, when HP's first efforts for customers remaining on the platform will be revealed.

Since this year's Interex Web site didn't have an obvious place to submit questions for this roundtable, expect most of the questions to appear straight from the floor -- the most fun for the assembled customers -- questions like, "Why did HP decide not to give MPE and IMAGE a new home, and sell these assets to one of several suitors who appeared before the company last year?" (That's just a suggested question, of course.)

Ringmaster and moderator of this key early morning event will be none other than Birket Foster, whose company MB Foster is one of HP's four North American Platinum Migration partners. 

File system makes your 3000 great

If you're among those who are defending MPE to your management this year -- and we'd think nearly everyone has had some kind of conversation about this, given HP's November 2001 announcements -- you might wonder what's at the heart of that continued 3000 greatness. The technical answer that can fuel your passion for platform defense lies right at the bones of the computer: its file system.

Adager's Alfredo Rego recently posted an insightful defense of what makes MPE great, good reading for those who want to understand more about the advantage that no market forces have been able to erase. We think having an efficient and elegant file system is one of those "they don't build them that well anymore" aspects of 3000 ownership. Here's Rego's primer, in a virtual conversation with a friend of his, on why those files are so fine:

"I would keep quiet, but I have too much respect for HP's important contributions to the advancement of worldwide file-system material. Granted, HP's contributions with MPE date back to the early 1970s. But they are still way ahead of (most of) the competition. Why are people (particularly HP management) so arrogant when it comes to MPE? Please keep in mind that MPE -- according to overweening people from other rarefied spheres -- is supposed to be "old legacy stuff". Dream on :-)

Few people defend MPE's file system in public. I am happy to do so. And, believe me, I am NOT on HP's PR payroll."

His friend then notes, "It would be very difficult to write a database or isam package without this ability, as I am sure you are quite aware. Having said that, there must be a way because even the *nix folks wouldn't use the "elegant" algorithm of serially processing the whole file between two work files in order to get the results we want."

Rego replies, "Of course not. Here is an example, from SAP DB. You can download the source from http://www.sapdb.org/develop/dev_linux.htm

Take one file out of the blue hat: SAPDB_ORG/sys/src/eo/veo100c

Yes, there is no "." before the "c" at the end -- perhaps a typo, because other (not all) C source files in the "eo" directory (and other directories) end with the standard ".c" for C and ".cpp" for C++.

Perhaps I am missing some deep naming convention. Given the contents of the source file, though, you may wonder about a few more things besides potential typos...

Here is one function from that source file, for your edification:

/*----------------------------------------------------------------*/
static int replace_page ( devsp, devsp_pos, pno, new_page)
/*----------------------------------------------------------------*/
FILE *devsp ;
int devsp_pos ;
int pno ;
char *new_page ;
{
long pos_to_seek = devsp_pos * PAGE_SIZE;
int seek_ok = fseek ( devsp, pos_to_seek, SEEK_SET ) == 0 ;
if ( !seek_ok )
perror ( "can't seek to specified position" ) ;
else
{ char buf[PAGE_SIZE] ;
seek_ok = fread ( buf, sizeof (char ), PAGE_SIZE, devsp ) == PAGE_SIZE ;
if ( !seek_ok )
perror ( "can't reading from specified pos" ) ;
else
if ( !(seek_ok = *((int *)buf) == pno ) )
printf ( "\ninvalid page on specified position!(%d)\n",
*((int *)buf) );
else
{ seek_ok = fseek ( devsp, pos_to_seek, 0 ) == 0 &&
fwrite( new_page , sizeof(char), PAGE_SIZE, devsp )
== PAGE_SIZE &&
fclose ( devsp ) == 0 ;
if ( !seek_ok )
perror ( "can't write new page to specified position" ) ;
}
}
return ( seek_ok ) ;
}

---

Please notice the variable "seek_ok". In how many semantic "moments of truth" do you see this poor variable involved? I know that memory was a super-valuable resource in the old days of legacy systems. Nowadays, saving a few words of memory AND paying for the "saving" by recycling the same variable for totally different purposes is not necessary. This is not sufficient to automatically generate errors, of course, but this kind of "methodology" is an accident waiting to happen. What's wrong with defining a couple of other variables, such as "read_ok" and "write_ok"? Ok, ok: The function returns the value of "seek_ok", so it would be awkward to have many different names. With this reason (very reasonable) in mind, then why not choose a neutral name that applies to ALL the file operations? How about something like "result-ok". Why use a specific name for many different instances when a generic name will do (and will be less confusing)?

"Please notice the nice error messages, all written in a consistent style (never mind that they are all predicated on the falsehood of the SAME variable, "seek_ok", which goes through quite a semantic shake-up):

can't seek to specified position
invalid page on specified position
can't write new page to specified position

"And then, whamo, a message that obviously was written by somebody else from another planet (or perhaps by the same person under a different influence at a different time),

can't reading from specified pos

... Go figure. Is this the way of the future?"

Rego's friend then notes, "Comparing the richness of the MPE file system to the *nix file capability is obviously an apples and peanuts comparison, since the *nix facilities are so primitive. Perhaps there is an underlying set of undocumented file manipulation routines that all the "masters" use."

Rego replies, "Or, as Oracle did, some people just bypass the *nix file system and write their own. There are quite a few alternative file systems for Linux. I use the Reiser File System (ReiserFS) with SuSE Linux (as one of three native OSs on my Mac Titanium PowerBook, a beautiful big-endian PowerPC machine.)

"For some history on Linux file systems, see this article from December 2001: <http://www.extremetech.com/article2/0,3973,11602,00.asp>

"All users of MPE's file system will certainly appreciate the strength and robustness of MPE. MPE's file system is still ahead of the competition. HP: Please take note and be proud.

"Among many things, the article mentions:

"JFS is the journalized file system designed and used by IBM. Proprietary and closed at first, IBM recently decided to make JFS freely available.

"I didn't notice any HP contributions to the Linux file system projects. I wonder what the status of HP/Linux things will be now that Bruce Perens has decided not to continue as an HP employee. Here is an article from two days ago about Bruce's choice: http://www.pcworld.com/news/article/0,aid,104016,00.asp

"Politics appears to have divided Hewlett-Packard and one of its top Linux engineers. Bruce Perens, an icon in the open source community and a senior strategist with HP's Linux software group, disclosed that he plans to leave the company in order to become more politically active, a move that has been ill-received by HP management, he said."

HP begins to shed MPE expertise

Workforce reductions at HP haven't all been politically motivated like Perens' departure. Over the last two weeks, members of the 3000 workforce have been notified they're on the way out, and the dismissals show how a broad range of skills is being removed from your vendor's resources. Released to the open marketplace might be another way to think of it, considering the need to build a 3000 infrastructure independent of HP. Those being layed off will provide a good workforce for independent companies committed to continuing MPE and HP 3000 support and product.

For people who believe a vendor's support of a computer platform is essential to continue using it in business, these kinds of HP reductions should give them pause. A vendor's support for a platform is no better than the expertise it retains, and it's clear that HP's expertise is being pared back. HP managers have repeatedly said the company's decision to drop the HP 3000 from its line was unrelated to the merger. It that is true, then these merger-related staff cutbacks surely would have reduced HP's ability to serve 3000 customers.

Either way, HP is retreating from the 3000 customer's field. Pulling its troops because of its merger makes the vendor's lack of impact in the future a certainty. In a recent HP Webcast, all the company could promise about the HP 9000 systems is that they were "expected to be supported" in the next few years. Customers might want more than an "expectation" of support before converting their HP 3000s to HP 9000s with HP's free kits. Obsoleting PA-RISC HP 9000s could well happen before 2006, making those conversions a costly mistake.

Over at the OpenMPE.org Web site, a new link just appeared that tracks what the organization calls Former HP'ers. The first staffer listed came as a surprise: Mike Yawn, the chief architect of the Java virtual machine for the HP 3000. Yawn has a new Java textbook hitting streets this week, (details at Mike's Web page) but that cross-platform, standards-based accomplishment apparently didn't factor into HP's headcount decision. We're as baffled as anybody about why someone with this kind of Java expertise doesn't fit into HP's plans, but it's good fortune for the MPE community. Experience like Yawn's doesn't come onto the market very often. Employers can take advantage of HP's mistake by contacting him at mike@theyawns.com.

HP seems to want it both ways, for now

HP looks like it's confused on more than just its headcount plans these days. The company has put a serious marketing effort into prompting customers to migrate off the platform, but at the same time continues to promote using the HP 3000. Out at the HP Web site, it's Advisor newsletter includes a profile of a customer still doing great work with the system.

We were a little surprised to find HP still promoting the use of a system it claims is not appropriate for its customers. Perhaps it's simply being fair to the customer who thinks that leaving a cost-of-ownership dream would spark a nightmare. We bet you can expect such reports to continue to surface from HP, even while it promotes migration, so long as there are N-Class HP 3000s to sell. You can read the HP about-face about Travis Credit Union at the HP Web site.

Migration meeting, or OpenMPE?

Customers are going to have make a decision about their future if they're attending HP World, because the conference organizers have scheduled SIG-Migrate's first meeting opposite the HP World gathering around OpenMPE. Nicolas Fortin of the SIG said his 3PM to 5PM meeting on Wednesday, opposite the MPE/iX 7.5 performance talk and then the OpenMPE report, will gather many of the market forces dedicated to helping you move away from the 3000:

"It is a fact that there are many presentations and sessions on the subject of migration at HPW, but many of them are technology/subject specific. By the nature of SIGs, I'm confident that this SIG will attract a significant number of people that share this common interest and be a unique opportunity to address all aspects of HP e3000 customers' migration issues, and bring everyone together on this common subject of interest."

"Here is a list of companies & vendors that we have planned to have present at the meeting: HP, Ordina-Denkart, Cognos, Exegesys, Transoft, Speedware, Neartek, AcuCorp, DISC, Quest, Ecometry and Microfocus, plus some key legends like Jeanette Nutsford (SIG Cobol chairman), Alvina Nishimoto, George Stachnik, Kevin Cooper and Bill Bennett (HP e3000 transition team)."

We're pretty sure HP's Cooper won't be in the room before 4PM, since he's talking up the improved performance of MPE/iX 7.5 in the room next door until then. If migration is in your near future, this is a meeting that can introduce you to those who believe it's the right choice. Of course, if the 7.5 talk isn't on your must-see list, you could always split the time between SIG-Migrate and OpenMPE, since the migration meeting is in 406B, and OpenMPE cranks up just down the hall in 408A.

RUGs mount fall meetings

Regional User Groups (RUGs) used to be the bedrock of the Interex user group experience, providing a legion of volunteers brimming with expertise to the national organization. The state of many RUGs has fallen significantly in recent years, as online access replaces the face to face meetings that tied the RUGs together. A few of the user groups are still mounting annual meetings of more than one day. MARUG, based in the Mid-Atlantic US states, is putting on a conference in mid-October, and the Texas HP users will have a conference to attend in early November.

Online access is much more prevelant these days, but training and briefings face to face still offer better instruction in many cases. And the networking that happens at a conference still is unparalleled. If you can break away from the office for a few days, these kinds of meetings can offer insights that can help your career and company. MARUG's meeting is Oct. 16-18 in Myrtle Beach, SC. Get details on it at the group's Web site. The Texas HP users will be meeting November 7 in Houston; more details are at the GHRUG Web site.

While MPE migration is obviously on the minds of conference organizers -- the early tracks listed for the Texas group only include "MPE Migration" and nothing else on the 3000 -- you can expect to hear more than just promotion of tools and services to help you go. Michael Anderson, one of the Greater Houston RUG board members, recently posted a message asking what MPE content they might add to the November meeting to spur attendance. (You can tell Anderson what you'd like to see at MichaelA@springisd.org). Anderson said users appear to be favoring a migration off, but added, "they have not been given a better option, or they have an emotionally motivated enthusiasm to go to a different/popular platform. I use the word "Emotionally" because I think that when you really think this through, in most cases you'll see that staying with MPE is the best choice, at least for the next 10 years. Ten years from today many more options will exist."

Speedware touts support certification

Speedware, providers of Web development and data migration tools as well as the Speedware 4GL, recently announced its technical support center has earned its third consecutive certification under the Support Center Practices (SCP) Certification program. Speedware officials said the company was awarded this certification after an extensive audit of its customer support center based in its Montreal headquarters. "Speedware's latest certification results reflect a level of performance that exceeds the SCP compliance requirements and is well above the benchmark average for the community of certified centers," according to a press release. Areas such as customer feedback, total quality management, employee development programs, and corporate communications were all rated above industry benchmarks.

"Speedware has been integral to our success," added Dave Kemp, Chief Technology Officer at OPENonline. "They consistently provide excellent technical support to our organization - the best I have ever experienced." OPENonline provides access to national public records and proprietary information through a user-friendly search and delivery system, built using the Speedware Autobahn II web development tool.