November 11, 2014

Veterans get volunteered for transition's day

1stCavHere on Veteran's Day — I'm a vet of the '70's-era military — I'm remembering there are IT pros with another kind of veteran status. They are people who count more than a couple of decades of experience with the HP 3000, managing their servers since before the time that Windows was the default computing strategy. They've been through a different kind of conflict.

I've learned that the most embattled managers employ a surprising tool. It's a sense of humor, reflected in the tone of their descriptions of mothballing the likes of 25-year-old independent apps during migrations. They have to laugh and get to do so, because their attempts to advance their positions might seem like folly at first look, or even in a second attempt.

Really, an assignment like putting Transact code into an HP-UX environment? Or take the case of working around a financial app software from Bi-Tech -- an indie vendor that "really stopped developing it for the 3000 years ago," according to City of Sparks, Nevada Operations & Systems Administrator Steve Davidek. There's been some really old stuff doing everyday duty in HP 3000 shops. The age of the applications was often in line with the tenure of the project's management.

These pros typify the definition of veterans, a term we'll use liberally in the US today to celebrate their sacrifices and courage. Facing battle and bullets is not on par with understanding aged code and logic. But two groups of people do have something similar at heart. Both kinds of veterans have been tested and know how to improve the odds of success in a conflict. Youthful passion is important to bring fresh energy to any engagement, military or technological. What earns the peace is experience, however grey-haired it looks next to Windows warriors.

With each mission accomplished -- from what looks like the Y2K effort of 14 years ago to embracing a roll-your-own Unix that replaced MPE's integrated toolset -- these veterans moved forward in their careers. "Our knowledge base is renewed with this work," one said after migrating apps that served 34 Washington state colleges. "We're on the latest products."

Recruiting IT talent into small towns — and the 3000 runs in many small cities where manufacturing labor is less costly — meant hiring for Windows experience. Adopting Windows into an organization means leaving proprietary environments even more popular than MPE/iX. Like HP-UX.

Read "Veterans get volunteered for transition's day" in full

Posted by Ron Seybold at 04:23 PM in Homesteading, Migration, User Reports | Permalink | Comments (0)

Pivital Solutions: Your complete
HP e3000 resource

November 10, 2014

Sharing the Source of SLEEPER for MPE

Sleepy penguin,jpgSLEEPER is one of the best-known Contributed Software Library (CSL) programs in the history of the HP user group Interex. For years after the user group shut down, the CSL tapes -- created once a year and refreshed with new programs after every annual user meeting -- were the most significant Interex asset left to the community. But making the CSL a public asset, after the Interex shutdown, encountered a snag. How could those useful programs like SLEEPER get shared, if they didn't have clearance from the contributing companies?

SLEEPER and BOUNCER were the programs most often cited in the snags, since they were shared by way of the 3000 shop at Boeing. It was heard a lot, this caution, while people were searching for CSL collections after the Interex meltdown. "Oh, we can't go and release that swap tape," people like the Interex curators would say. "There's BOUNCER on there, and we'd have to get permission from Boeing." Well, that's not exactly true.

Maybe one email would've gotten the process of permission started. It's different times by now. The SPL source for SLEEP, a progeny of SLEEPER, was shared up on the 3000-L mailing list last week. (That's a link to the 3000-L archive message, containing the code in the message body.) Ray Legault offered the code when John Korb, a 3000 consultant, was asking around for it.

Korb thinks so highly of SLEEPER that wants to port the program to PHP, for use on a Linux system. "My goal is to create a PHP version of SLEEPER," he said, "something that can run on Linux desktops and servers and Windows 8.1 desktops -- so I can avoid cron on the Linux box, and avoid the Windows task scheduler."

Read "Sharing the Source of SLEEPER for MPE" in full

Posted by Ron Seybold at 07:39 PM in Homesteading | Permalink | Comments (0)

November 07, 2014

Manual and Automatic Masters, Detailed

A few days ago we included a Hidden Value question about how manual and automatic masters work in TurboIMAGE. Our ally and friend Vladimir Volokh called to note that in part of the question, the system manager had found "one detail data set that has thousands of entries which do not appear to be connected to any master.

It wasn't exactly a question, but in a reply on the 3000-L mailing list and newsgroup, Roy Brown gave a fine tutorial on how these features do their jobs for MPE and the 3000 -- as well as how a detail dataset might have zero key fields.

Manual masters can contain data which you define, like Detail sets can, along with a single Key field. Automatic masters contain only the Key field.

In both cases, there can be only one record for a given key value in a Master dataset.

A Detail dataset contains data fields plus zero, one, or many key fields. There can be as many records as you like for a given key value, and these form a chain accessible from the Master record key value. This chain may be sorted, or it may just be in chronological order of adding the records.

Zero key fields in a Detail dataset would be unusual, but is permissible.

Read "Manual and Automatic Masters, Detailed" in full

Posted by Ron Seybold at 09:55 PM in Hidden Value, Homesteading | Permalink | Comments (0)

November 06, 2014

Throwback: Today's Empire of Invent3K

Five years ago today we watched for notice about a fresh 3000 resource on the Web. Invent3K, a public access development server created by HP in 2001, was searching out a new home in November 2009. The vendor shut off Invent3K in November 2008, along with the Jazz website that hosted shareware utilities created by HP and the user community.

Invent3K was an OpenMPE adoption project five years ago. The community probably didn't need a public access development web server by the end of 2009. But replacing HP's withdrawn assets seemed important. Invent3K harkened back to a more hopeful time. 3000 developers were first offered access to MPE accounts on that HP server only about six months before the vendor announced it would end its 3000 programs.

Invent3K was unique in the 3000's history. The server was the first and only place that hosted free, development-use-only subsystem software from HP. Working from an Invent3K account, a developers employed COBOL II, TurboStore, and other HP-branded products while building apps or utilities.

InventFor a time, OpenMPE wanted to sell $99 yearly development accounts on its replacement Invent3K. The community was not accustomed to paying for public access, so sales were slow. OpenMPE was trying to generate revenues for operating things like a Jazz replacement host where contributed tools could be accessed. By that time, much of Jazz had been re-hosted at servers owned by Client Systems and Speedware. Things were not hosted quite the same as on Jazz, though. HP insisted that those two vendors make users click through an End User License Agreement before using the contributed tools re-hosted from Jazz.

Last month, two of the replacement servers for delivering Jazz and Invent3K had online glitches. Speedware's server went offline for a weekend, so its hpmigrations.com website that hosts Jazz delivered only an error. The HP 3000 where Invent3K was headed in 2009 had a small hiccup, too: the 3000-based Empire 3.9 game server lost use of its domain name for awhile in October. Tracy Johnson is the caretaker for the Empire server and its parent -- Invent3K, whose domain name is invent3k.openmpe.com.

But Invent3K is operating today, at least for anyone who had an account established before OpenMPE curtailed its operations. Access is through any terminal emulator with Telnet or VT/Mgr protocol. Once you've configured your terminal emulator, connect to the address invent3k.empire.openmpe.com.

Read "Throwback: Today's Empire of Invent3K" in full

Posted by Ron Seybold at 08:42 PM in History, Homesteading, Web Resources | Permalink | Comments (0)

November 05, 2014

Migration plans: Rehost, Replace, or Retire

CircleRMigration begins with an inventory. Application by application, an IT manager does triage on every program on their 3000. The goal is to come up with a disposition for each app. Some ccan be rehosted. Apps built with PowerHouse might be moved to other servers, for example. For other apps, they can be replaced. Ecometry sites could adopt the CommercialWare application, in some cases. Or in other instances, an in-house program suite can be replaced by a Commercial Off The Shelf app. Migration services company MB Foster likes to call those replacements COTS. The company has a Wednesday webinar scheduled on Nov. 19 to explore planning to replace COTS and more.

Foster calls the strategy the Three R's of Migration: Rehost, Replace, Retire. At 2 PM Eastern Time in a couple of weeks (register here), Birket Foster will lead a slide talk with time for questions about what to do if you're migrating away from any one of the above types of applications. The word Retire is already on the minds of MPE-savvy managers, since most of them are older than 50. It turns out that applications can find the end of a career even before their caretakers do.

It's not always this way. At the San Bernadino County schools, the apps to run the California district will have a retirement date from the 3000 that falls after the district's 3000 expert. Sometimes, though, a migration can become easier when older programs that have fallen into disuse are simply erased. There's no need to migrate such an app.

However, there's only one sure way to discover these retirees: inventory and analysis. MB Foster's summary for the Nov. 19 webinar breaks that triage process into inventory of app environments; rating the functionality vs. business suitability of each app; then organizing and prioritizing with a study of interfaces and grouping used that applies to each app. COTS carries a different set of requirements to study during migration planning, the company says, than in-house apps.

Read "Migration plans: Rehost, Replace, or Retire" in full

Posted by Ron Seybold at 08:18 PM in Migration | Permalink | Comments (0)

November 04, 2014

Tips for Listing SCHEMAs, and FTP Listings

From my existing TurboIMAGE database, I want to generate a listing of data sets, data item names, and their relationships (master, detail). One detail data set has thousands of entries which do not appear to be connected to any master. 

Oh, and I cannot remember the difference between manual and automatic masters.

Francois Desrochers first replies, "Use Query's FORM command."

RUN QUERY.PUB.SYS
B=dbname
PASSWORD = >> password
MODE = >> 5
FORM

Manual masters: programs have to explicitly add entries before you can add related entries in detail sets. Programs have to explicitly delete entries when there are no related detail entries left. In other words, you have to do master dataset maintenance.

Automatic masters: entries are automatically created when a related detail set entry is created. Entries in the master are automatically removed when the last related detail entry is deleted. IMAGE takes care of the maintenance.

Consultant Ron Horner adds, "If you have a tool like Adager or DBGeneral, it can create a file of the database schema. The other way is by using QUERY to get a listing."

Read "Tips for Listing SCHEMAs, and FTP Listings" in full

Posted by Ron Seybold at 04:19 PM in Hidden Value, Homesteading | Permalink | Comments (0)

November 03, 2014

10 years ago, was the 3000 halfway gone?

I revisited a set of user conference slides from 2004 recently, and I found a scheduling milestone. A presentation at that final Interex show in Chicago included a schedule warning. In that year, it was about halfway through the period HP gave the community to get away from their HP 3000s. The deadline for the end of HP support was December 31, 2006, as of the week the presentation rolled out in Chicago.

Go 95%"Put your plan into the budget during this summer of 2004," one slide suggested. Using that timeline, an IT manager could commence migrating by the summer of '05 and complete a migration by the end of 2006. To be sure, 18 months is a swift migration schedule, but it's possible -- if a company can budget for some outside expertise for project management and coding. The tests will usually be handled in-house. That's up to one third of a migration project's timeline, according to migration services experts like MB Foster.

By the next fall, HP was pulling the carpet out from under such companies. That deadline for HP support got extended by 24 months. With that change, that halfway-gone point was still at the moment of HP's rescheduling. But now there were more than 36 months left. People had not migrated in enough numbers. A greater factor: HP made a business decision to keep support business alive and earning revenues for another two years. It was high-profit revenue. High enough that the deadline got moved again, out by another 24 months.

Since those days, we've seen many customers use the same sort of rolling-forward deadline for their migrations. They plan for the end of 2013, for example, then push out to the end of 2015. Just like HP, customers in places like California school districts and manufacturers in the Southwest are taking more time because they like the return on investment. They can afford to reset the halfway mark.

But what if 2004 was the start of 95 percent of migrations, and the decade since then represents halfway-gone? What's left by now in the user community still includes companies of serious size.

Read "10 years ago, was the 3000 halfway gone?" in full

Posted by Ron Seybold at 10:25 AM in Homesteading, Migration | Permalink | Comments (0)

October 30, 2014

ITMGR3K + YOLO = CHARON COSTINFO?

The formula above translates into an appeal for budget reporting. IT managers of HP 3000s can complete this formula. YOLO is the ubiquitous You Only Live Once, sometimes broadcast in a tattoo. When added to 3000 IT managers' experiences, the formula may yield some of the most crucial costs of the CHARON virtualization engine for emulation.

Elder-tattoosThe daring of YOLO is required because there's plenty at stake, even at MPE's advanced age. 3000 owners are often working with reduced budgets. Cost-effective computing is one good reason why the MPE/iX apps survive in a company. But some managers could acknowlege you'll only live once through homesteading your MPE/iX applications. It's not the hardware you're saving with Charon. The operating environment, your TurboIMAGE/SQL data, and the apps with their software helpers -- those are the orphans being rescued from any failing HP-branded computer.

So it figures that managers with nothing to lose can help other homesteaders get better information on the costs to virtualize. Costs can be fatal to a project. Many managers know they have something significant at stake: their relations with the software vendors who supply the help for HP 3000 operations. Surround code, it's been called. Some vendors are everywhere, like Robelle, Adager, Vesoft, PowerHouse, and so on. Add in the suppliers of key data transfer tools such as MB Foster. Everybody's got virtualization licensing practices in mind, if not executed yet.

The above list of vendors can include a show-stopper, by some customer reports. PowerHouse products, even something as fundamental as Quiz reports, have still been quoted at rates that can shelve a virtualization project. We recently heard about one at a 3000 manufacturer. The COSTINFO specifics were not forwarded. But in a budget-conscious community like the 3000's, even such prices in the low five figures can cause a HALT.

Then there's the manager whose operational best practices include lowering a profile with vendors. "I'm not old enough to retire," we often hear -- meaning that high visibility on vendors' radars could invite higher costs. Not good for any career built on economic prowess. No, not every vendor operates by watching for such an extra-fee opportunity. But enough do; some can be hungry for back-support revenues when they bring a customer back onto vendor support. Then there are the applications. Update fees for virtualizing an Ecometry installation, or something from the Infor stable of manufacturing apps, are not common-enough knowledge. Not for HP users.

Read "ITMGR3K + YOLO = CHARON COSTINFO?" in full

Posted by Ron Seybold at 06:18 PM in Homesteading | Permalink | Comments (0)

October 29, 2014

Security experts try to rein in POODLE

PoodlelocksSometimes names can be disarming ways of identifying high-risk exploits. That's the case with POODLE, a new SSL-based security threat that comes after the IT community's efforts to contain Heartbleed, and then the Shellshock vulnerability of the bash shell program. HP 3000s are capable of deploying SSL security protocols in Web services. Few do, in the field; most companies assign this kind of service to a Linux server, or sometimes to Windows.

The acronym stands for Padding Oracle on Downgraded Legacy Encryption. This oracle has nothing to do with the database giant. A Wikipedia article reports that such an attack "is performed on the padding of a cryptographic message. The plain text message often has to be padded (expanded) to be compatible with the underlying cryptographic primitive. Leakage of information about the padding may occur mainly during decryption of the ciphertext."

The attack can also be performed on HP's Next Generation Firewall (NGFW), a security appliance that is in place protecting thousands of networks around the world. Other firewalls are at risk. Just this week HP released a security patch to help the NGFW appliances withstand the attack. External firewalls are a typical element in modern web service architectures.

A POODLE attack takes a bite out of SSL protections by fooling a server into falling back to an older SSLv3 protocol. HP reported that its Local Security Manager (LSM) software on the NGFW is at risk. But a software update is available at the HP TippingPoint website, the home of the TippingPoint software that HP acquired when it bought 3Com in 2010. TippingPoint rolled out the first HP NGFW firewalls last year.

Read "Security experts try to rein in POODLE" in full

Posted by Ron Seybold at 08:48 PM in Migration, News Outta HP, Newsmakers, Web Resources | Permalink | Comments (0)

October 28, 2014

Strategies for Redirecting App Spoolfiles

An HP 3000 manager wrote that a 24x7 application at his shop is stable and never goes offline unless it's required. But the everyday management had to include aborting the app once a week.

We take that application offline to close out the spoolfile that the application generates. Is there a way to keep the application running, and just redirect the output to a new spoolfile? We're using an N-Class server.

Robert Schlosser of Global Business Systems replied: Short of closing and reopening the application after n number of pages, you could have the application read (without wait and checking status codes) a message file. It could then close and open the output file on demand, and possibly even close down the application gracefully (no abort).

Our Homesteading Editor Gilles Schipper replied: I think the only way you could do that would be to actually modify the application program to periodically (say, for example, every 10 pages or every 100 pages) close then re-open the print file.

Olav Kappert of IOMIT International added:

If the program can be slightly modified, then I would suggest creating a message file as a conduit to the application. The program would do a read of the message file with the nowait option every once and awhile.  If the application encounters a keyword indicating a new spoolfile, then the program would close the spoolfile and reopen it.

An alternate method would involve the application being modified to close and open the file at a particular day and time during the week.

Posted by Ron Seybold at 05:34 PM in Hidden Value, Homesteading | Permalink | Comments (0)

October 27, 2014

Early 3000 Flights: A New Embattled History

Bill FosterThe world is still full of computer aces who flew in the earliest skies of minicomputers. The HP 3000 has history to share about the dogfights to bring interactive computing to businesses and organizations. The new voice of a pilot of that early age, Bill Foster, tells a fresh story about historic 3000 events. (A tip of the hat here to former OpenMPE director and Allegro support engineer Donna Hofmeister, who spotted Foster's blog.)

Bill Foster was in charge of engineering for the first HP 3000 that became a production-grade computer, the Series II. Foster went on to co-found Stratus Computer. In a blog he's called TeamFoster he tells his compelling story I Remember HP, complete with characters memorable and regrettable, about the earliest times in the Data Systems Division labs in California. Up to now, most of the stories about the 3000's birth have had a more abbreviated telling, or they're summarized in less vivid accounts.

Foster's written 15,000 words on his blog to tell his Hewlett-Packard story, which begins in 1971. In that year the HP 3000 is still more than a year away from its ill-fated debut, so he can chronicle the inner workings of a lab where "The engineers were mostly out of control, particularly the programmers."

HP Journal 1973Foster's story about the earliest days of the 3000 includes accounts of important players such as Barney Oliver, Paul Ely and Ed McCracken. There's even a note about Jim Hewlett, son of HP co-founder Bill Hewlett. A golfer and a nature lover, Hewlett's son got Foster in trouble. As part of the system's revival there was even a face-saving video interview, designed to revive the ruinous reputation of the 3000.

Read "Early 3000 Flights: A New Embattled History" in full

Posted by Ron Seybold at 07:10 PM in History, Homesteading | Permalink | Comments (0)

October 24, 2014

Legacy Management: More than Rehosting

LooksoftwareSpeedware became Freshe Legacy several years ago, and in 2012 the company's business crossed the watershed from Hewlett-Packard sites to those running IBM's AS/400 servers. The latter is now called IBM i, and in one interview Fresche CEO Andy Kulakowski said the company's customers are now 85 percent IBM users.

The world of IBM i is still populated with product releases, vendor support, and the challenges of keeping a legacy line of computing looking current. Last month Fresche purchased the assets, intellectual property and customer base of looksoftware (yes, all lowercase and all one word.) Next week the newest tool in the Fresche belt goes on display in one of the oldest of enterprise venues: a $949 user conference, COMMON.

COMMON has served IBM users since before there was an Interex. The first meetings of the group surrounded the IBM Series 1800, a data acquisition and control system which was similar to the 3000 in that it used a Multi Programming Executive (MPX) operating system. COMMON meetings began in the 1960s, and the 1800 was used in product for more than 50 years. Even though COMMON attendance has dropped and the gatherings have gotten shorter, the group still assembles the experts and the faithful once a year for a classic expo and education event. This year's is in Indianapolis, following the model that Interex used for HP 3000 customers: a moveable feast taking place in cities both great and, well, common. One forgettable year the Interex show was held in Detroit. In the Midwest, however, a great number of manufacturers and distributors have always used business systems like the 3000 and the i.

ModernizationDrill into the looksoftware website and you'll find mention of the HP 3000 in the Modernization Solutions section. Along with methodologies such as cloud enablement, database modernization and automated code conversion, MPE/iX customers can find a relevant line, "Re-hosting (HP e3000)." COMMON attendees could very easily hear about rehosting at the conference. After decades of serving just the AS/400 family, it's now an expo that embraces Unix and Linux computing from IBM, too.

Read "Legacy Management: More than Rehosting" in full

Posted by Ron Seybold at 06:49 PM in Migration, Newsmakers | Permalink | Comments (0)

October 23, 2014

TBT: There Used to Be a Lab Around Here

Screen Shot 2014-10-23 at 4.56.26 PMAbove, the Glendenning Barn Picnic Area, one of the signature elements of Hewlett-Packard's Pruneridge Avenue campus, heartland of HP's 3000 business. It's all been razed to below-ground level, as Apple builds its new intergalactic headquarters on the site.

Screen Shot 2014-10-23 at 4.58.02 PMOne of the lesser-known tunes from the Frank Sinatra songbook is There Used to Be a Ballpark Around Here. The sentiment of the song wraps around the wistful view that something unique is now gone. Apple has posted the greatest quarter of business in the company's history. All through this year, it's been steadily displacing the HP labs where the 3000 and other products were designed and improved.

Screen Shot 2014-10-23 at 4.57.21 PMOne 3000 engineer posted pictures of the current state of the 3000's estate. Only a multi-story mound of earth can be seen where handsome walkways, cooperative parking and stately poplars and pines were once the sentinels around the campus. People called their journeys to this location "a factory visit." One day while I was there on a press briefing, I was shown downstairs to a lower level -- where a manufacturing line was rolling out Series 68 servers.

Screen Shot 2014-10-23 at 4.56.51 PMHP's been cutting back on many things to maintain its profitability. Real estate has been at the head of the list the company no longer needs. You can consider that HP has closed its MPE/iX labs in California, yes. But the labs themselves -- cubicles and miles of network cables and office furniture and meeting rooms named after types of trees like Oak and Maple -- those are all gone now, the home of more than 3000 enterprise computing. It's all been moved away and changed.

Screen Shot 2014-10-23 at 5.15.43 PMSteve Jobs and Larry Ellison once walked the streets of Palo Alto and bemoaned the changes at Hewlett-Packard, not quite five years ago this fall. Apple, Jobs hoped, would be built to last as long as HP and become the kind of headwater for inspiration and innovation that Hewlett-Packard was. The street that faced that Pruneridge Avenue entrance had Tandem Computer on the facing curb. Tandem, spun off from HP by James Treybig, until HP assimilated it to become its NonStop group. Now the spinning comes anew to this street, soon enough to be the site of a spaceship-sized Apple HQ.

Apple has done all that it can to become the HP of innovation, plus added an ability to capture the lightning in a bottle of excitement about new tech. It's a fulfullment of Jobs' dream to see the company rise up on the ballpark site of HP's enterprise computing labs.

Posted by Ron Seybold at 05:27 PM in History, News Outta HP | Permalink | Comments (0)

October 22, 2014

What Needs Replacing, at Its Heart?

Porsche-getaway-carHewlett-Packard's 3000 hardware has started to show its age this year. Even the newest of servers was built at least 11 years ago. Although that's an impossible age for PCs or tablets, more than a decade isn't outrageous for systems created by HP. These things were built to the specs of spacecraft, on the good days of the manufacturing line in Roseville, Calif. and elsewhere.

However, even a server of rigorous construction has moving parts and electrical components with a finite lifespan. Lately we're been hearing from customers whose managers have awoken from a peaceful slumber, dreaming of limitless hardware lifetimes. Hey, say they, how did we ever get to be relying on computers built before Y2K?

At this point there are no questions about MPE/iX, or TurboIMAGE, or the pedigree of bash shell software, or the built-in the ODBC data connection capabilities, or jobstream management. These are all stand-up, solid citizens, even through their range of motion can be limited. (So is mine, but like the software above, I work to stay limber.)

No, this is all about the age of the iron. HP stopped building servers that ran MPE apps more than a decade ago. So, is it out those apps go, the baby tossed with the hardware bathwater? It's a simplistic way to approach system reliability. However, until recent years there was no newer hardware to lift those apps onto. Fresh steeds, in the shape of faster and newer computers, hadn't been in the stable in many years.

Users would like to move to implementation straight away, once they get that "What's up?" inquiry from the boardroom. The fastest path to Get Me Outta Here -- indeed, the most ready getaway car -- seems to be the Stromasys virtualization solution. There are more complete, wider-ranging moves. They take a great deal longer, because their details demand they move slower.

Read "What Needs Replacing, at Its Heart?" in full

Posted by Ron Seybold at 09:14 PM in Homesteading, Migration | Permalink | Comments (0)

October 21, 2014

Macworlds expire. Apple soars. Not linked.

Screen Shot 2014-10-21 at 3.14.11 AMOne classy way to go out of the conference business: tell your sponsor vendors the next conference won't happen, six months early. Don't take their deposits for show space.

You can file this report under Types of End of Life. The HP 3000 had an alleged end of life. HP announced it about 13 years ago, but that was the vendor's report about its 3000 activities. There can be a demise in classic support structures for a system once it wanes. But those structures, like information and community events, might be wobbly all by themselves. Things do change.

Everything called Macworld has now gone away. There was a print magazine, roaring through the '80s, the '90s, and even until about 10 years ago. Printed publications about computer lines, focused on one vendor, built this industry. IDG owned Macworld, owns PC World, owns Computerworld. Only the last publication still prints news on paper and sends magazines into the mail. Things change. There's this invention called the Internet.

In another post I pointed to the HP publications no longer in print. All of them, except for the Newswire. HP Professional, InterACT, HP Omni. Long ago, SuperGroup, and HP User. Interex Press, HP World. Every one of them exited. The departure for some was the trigger of that HP end of life announcement. Others rolled over when something bigger died: their parent company, or interest in Hewlett-Packard's products. One of the last executive directors of the Interex user group asked a big question: "How do you make a vendor-specific user group relevant in a cross-platform world?" said Chuck Piercey.

HP World 2005


Another way to go out of the show business: tell your partners nothing about the departure, and market as if it's all going fine. This, from a web page less than four weeks before the final, canceled HP World conference -- a page still online on the day before the user group's demise.

IDG's expo division has asked the same stay-relevant question about the 30-year-old Macworld conference. And answered it. The expo is now on hiatus, and unlikely to emerge again. Macworld Expo added a sister expo called iWorld to embrace the rocketing mobile products from Apple. More than one third of Macworld/iWorld exhibitors bought booth spots in a bullpen called the Appalooza. More important, though, was the exodus of tens of thousands of square feet of show space, once purchased by the industry's giants. Adobe. HP. Canon. Microsoft. Little vendors in little booths were not enough to counter big changes in our industry's communication.

Apple reported a record profit yesterday, and its stock is trading at $716 a share (corrected for the 7:1 split of the springtime). Apple announced an end of life of its user show exhibitions four years ago. Macworld Expo never was the same. The vendor got healthier and bigger, so why did the magazine and show founder? Things change. Customers, always the prize for a conference or a magazine, found better ways to learn about owning products. And what to purchase.

Read "Macworlds expire. Apple soars. Not linked." in full

Posted by Ron Seybold at 06:06 PM in History, Newsmakers | Permalink | Comments (0)

October 20, 2014

3000's class time extended for schools

SB County schoolsThe San Bernadino County school district in California has been working on moving its HP 3000s to deep archival mode, but the computers still have years of production work ahead. COBOL and its business prowess is proving more complicated to move to Windows than expected. Dave Evans, Systems Security and Research officer, checked in from the IT department at the district.

We are still running two HP 3000s for our Financial and Payroll services. The latest deadline was to have all the COBOL HP 3000 applications rewritten by December 2015, and then I would shut the HP 3000s down as I walked out the door for the last time. That has now been extended to 2017, and I will be gone before then. 

We are rewriting the COBOL HP 3000 apps into .NET and Windows Presentation Foundation (WPF) technologies. Ideal says they can support our HP 3000s until 2017.

And with the departure date of those two HP 3000s now more than two years away, the school district steps into another decade beyond HP's original plans for the server line. The second decade of beyond-end-of-life service.

Read "3000's class time extended for schools" in full

Posted by Ron Seybold at 10:26 PM in History, Homesteading, Migration, User Reports | Permalink | Comments (0)

October 17, 2014

Tracking MPE/iX Vulnerability to Shellshock

Security experts have said that the Shellshock bug in the bash shell program is serious. So much so that they're comparing it to the Heartbleed breach of earlier this year. Many are saying Shellshock is even more of a threat.

Screen Shot 2014-10-17 at 8.22.33 PMOnce again, this has some impact on HP 3000s, just like Heartbleed did. But you'll need to be managing a 3000 that's exposed to the Internet to see some risks to address as part of system administration. Web servers, domain name servers, and other net-ready services provide the opportunity for this malware. There's not a lot of that running in the customer base today, but the software is still sitting on the 3000 systems, programs that could enable it.

Authorities fear a deluge of attacks could emerge. The US government has rated the security flaw 10 out of 10 for severity.

Bash is open source software, and our expert on that subject Brian Edminster is working on a specific report about the vulnerabilities. Hewlett-Packard posted a security bulletin that points to a safer version of the bash shell utility. But that version won't help HP 3000s.

It's not that HP doesn't know about the 3000 any longer. The patching menu above shows that MPE is still in the security lexicon at Hewlett-Packard. But Edminster thinks the only way to make bash safe again on MPE might be to port it a-fresh. "The 3000's bash is version 2.04, but the version that's considered 'current' is 4.x (depending on what target system you're on)," he said. "So if v2.04 is broken, the code-diffs being generated to fix the issues [by HP] in late-model bash software won't be of much (if any) use."

Read "Tracking MPE/iX Vulnerability to Shellshock" in full

Posted by Ron Seybold at 08:33 PM in Homesteading, Migration, News Outta HP, Newsmakers | Permalink | Comments (0)

October 15, 2014

Signed malware stalks HP's Windows boxes

HP will be revoking a security certificate for its Windows-based systems on Oct. 21, and the vendor isn't sure yet how that will impact system reliability.

StalkingThe bundled software on older HP PC systems has been at risk of being the front-man for malware, according to a report in the Kerbs on Security website. This code-signing is supposed to give computer users and network admins confidence about a program's security and integrity. HP's Global Chief Security Officer Brett Wahlin said the company is revoking a certificate it's been using even before 2010.

HP was recently alerted by Symantec about a curious, four-year-old trojan horse program that appeared to have been signed with one of HP’s private certificates and found on a server outside of HP’s network. Further investigation traced the problem back to a malware infection on an HP developer’s computer. 

HP investigators believe the trojan on the developer’s PC renamed itself to mimic one of the file names the company typically uses in its software testing, and that the malicious file was inadvertently included in a software package that was later signed with the company’s digital certificate. The company believes the malware got off of HP’s internal network because it contained a mechanism designed to transfer a copy of the file back to its point of origin.

The means of infection here is the junkware shipped with all PCs, including HP's, according to HP 3000 consultant and open source expert Brian Edminster. In this case, the revoked certificate will cause support issues for administrators. The certificate was used to sign a huge swath of HP software, including crucial hardware and software drivers and components that are critical to Windows.

"This is one of the reasons that I absolutely loath all the 'junkware' that is commonly delivered along with new PCs," Edminster said. "I end up spending hours removing it all before I use a new PC." Recovery partitions on Windows systems will be at unknown risk after the certificate is pulled Oct. 21, too.

Read "Signed malware stalks HP's Windows boxes" in full

Posted by Ron Seybold at 10:15 PM in Migration, News Outta HP, Newsmakers | Permalink | Comments (0)

October 14, 2014

Making a Migration Down the Mountain View

After an exit off the HP 3000, the City of Mountain View is now also saying goodbye to one of its longest-tenured IT pros. Even beyond the migration away from the municipality's Series 957, Linda Figueroa wanted to keep in touch with the HP 3000 community, she reported in a note. "I started working on a Series III back in the 1980s," she said.

Inside Pocket GuideBut after 38 years with the City, and turning 55, it's time to retire. At a certain time, city employees with as many years as I have get the "when are you retiring?" look. We had 3000s running at the City of Mountain View from 1979 until 2012. 

Pocket GuideOur first HP 3000 in 1979 was a Series III system (which I just loved; always felt so important pressing those buttons). It had a 7970E tape drive, four 7920 disc drives and a printer. Then we moved to the monster Series 68, and ended up with the Series 957 with DLT tapes — no more switching reel-to-reels! I still have my MPE:IV software pocket guide from January 1981. (I couldn't get rid of it — coffee stains and all.)

When Mountain View took down its HP 3000, a couple of years after the switchover, the City turned off all of its other Hewlett-Packard servers, too. Only its software suppliers have made the transition, proving the wisdom that customers are closest to their applications — and leave the platforms behind. But MPE — from System IV to MPE/iX 6.5 — and the HP 3000 did more than three decades of service at Mountain View.

Read "Making a Migration Down the Mountain View" in full

Posted by Ron Seybold at 11:22 PM in Migration, User Reports | Permalink | Comments (0)

October 13, 2014

A Little Uptick For Hope

There is new business a-brewing for HP 3000 owners. Not migration business, that wouldn't be news. We just got a small report in the in-box from a long-time 3000 expert about an uptick in Paul Edwards' world. Some of it seems to be wrapped around homesteading, too.

It's titled MPE: Consulting Interest

I have had a lot of interest in MPE consulting lately. It is a two-week training class overseas, a local migration, a file migration in Texas, and a Time & Materials consulting opportunity in Texas. This is after no billing for all of last year. Things are looking up, especially in Texas. I just thought you would like to know that MPE opportunities are still available.

Paul Edwards and Associates consults on Speedware, on Suprtool, on COBOL -- on many of the things that make the HP 3000 unique. He's shared practices for system management of 3000s. He's also got the rights to teach with HP's educational materials for MPE classes. Plus got some links to the Stromasys virtualization world of prospects.

The latest news is not entirely about who closed down their 3000 shop recently.

Posted by Ron Seybold at 09:06 PM in Homesteading | Permalink | Comments (0)

October 10, 2014

When Smaller Can Be Better

SmallgoldfishHewlett-Packard has chosen to cleave itself into two much smaller companies. It will take most of the next year to make that a reality. But it might be an advantage to return to working with a more nimble company. Well, an advantage to the 3000 site that's migrating to HP's other computer enterprise solutions, or has done so recently.

Over at the New York Times, the tech writers found something to praise even while they questioned the wisdom of the move. 

In one day, Meg Whitman has created two of America’s biggest companies. All she had to do was break apart Hewlett-Packard, the company credited with creating Silicon Valley. HP Enterprise is targeting a market that appears full of potential innovations, while HP Inc. seems stuck in the low-margin consumer hardware business that has proved a slog for companies not named Apple or Samsung.

It appears Whitman has found a vision: one that looks a bit like the IBM of the West — with an emphasis on products rather than IBM’s consulting services — and another that looks a bit like Compaq Computer, a Texas computer company that HP controversially merged with 12 years ago.

A long time ago, in a marketplace now far away, 3000 owners wished for some breaking off. The HP 3000 wasn't a part of Hewlett-Packard's vision? Fine. Sell the unit off and let's get on with a focused future. At the time, the business was said to turn over $1 billion yearly. Even at half that size, it would've been big enough to survive with customer loyalty. If the 3000 had nothing else going for it, you could count on loyalty.

All opportunities now gone, you say. You just cannot break up an enterprise tech player like that. Then Whitman chops a massive company into two much smaller parts. Smaller has been better for the typical 3000 customer for a long time. Yes, there are times when there are advantages of being big: When a 3000 user got more from a company which sprawls to supersize, in sales and scope of solutions. You get predictability, alliances and headroom from companies sized HP. The vendor so lusted after being No. 1, which did not become a path to long-term success.

3000 community members understand that smaller can be better -- not bigger -- especially when they use what the independent vendor lives upon. Small companies respond faster, polish relationships, and commit for life.

Faster response can mean software that is enhanced sooner, or answers that resolve problems more quickly -- because a smaller company has fewer layers for a customer to dive through. Relationship polishing is the personal attention to a company of any size: the kind of experience that HP 3000 managers, who may now be CIOs and CTOs, recall getting from a smaller HP.

Read "When Smaller Can Be Better" in full

Posted by Ron Seybold at 09:48 PM in Homesteading, Migration, News Outta HP | Permalink | Comments (0)

October 09, 2014

TBT: A 3000 Newsworthy Birth Day

Inaugural IssueThe first issue of the Newswire ran its black and red ink across 24 pages of an early October issue. Inside, the first FlashPaper late-news insert had been waiting a week for main-issue printing to catch up with mailing plans.

In our ThrowBack to this week of 1995, the first issue of The 3000 Newswire rolled out into the mails. The coverage of the HP 3000 was cheerful enough to encourage a belief that the computer would run forever -- but 19 years of future was far from certain for either the system or the first 3000-only publication. Volume 1 (the year), Issue 1 came out in a 24-page edition, the same page count of the printed issue that just mailed this Fall. At the Newswire's introduction, one user group leader wondered aloud, on a bus ride during the Interex '95 conference in Toronto, "what in the world you'll might be able to find to fill up the news in Issue No. 2."

The last of the competing HP-only publications closed its doors 10 years later, when Interex folded its user group overnight. Interact, HP Professional, SuperGroup, HP Omni and others turned out the lights during that decade.

The Newswire's first mailed issue was carrying the news circulating in mid-August during an Interex conference. For the first time in 10 years, an HP CEO spoke at the Interex event. However, Lew Platt was a current CEO when he spoke to the 3000 faithful. David Packard was a former CEO and board member when he addressed the multitudes at Interex '85 in Washington DC.

Platt said that HP 3000 users had nothing to fear from a future where Unix was in vogue at HP. Earlier in the day, speaking before the full assembly of users, he said HP was going to making new business by taking out older products. At an editor's luncheon we asked him what that mission held for the 3000.

Platt explained his prior comments on cannibalizing HP's business to maintain steady growth. MPE/iX won't be served up in a pot anytime soon. "I don't mean leaving customers high and dry," he said. "HP has worked extremely hard with products like the HP 3000 to make the people who have bought them have a good future. We've put an enormous amount of energy out to make sure we can roll those people forward. I'd say we've done a better job than just about any company in the industry in providing a good growth path for those customers."

The CEO went on to explain how cannibalization would work. HP would take a product, such as a printer, that was doing perfectly well and may still be a leadership printer in the market -- and bringing in a new one before it's reached its end of life. If you substitute "business server" for "printer" in that plan, you can see how a computer that was doing perfectly well might see a new computer brought in before the end of its life. In that issue, the Newswire story noted that the project we'd learn to call Itanium six years later was going undercover, so that new product wouldn't lock up existing server business for a year before it would ship.

HP was calling the joint effort with Intel the Tahoe architecture, and Platt would be retired from his job before anything shipped.

Read "TBT: A 3000 Newsworthy Birth Day" in full

Posted by Ron Seybold at 09:49 PM in History, Migration, News Outta HP | Permalink | Comments (0)

October 08, 2014

Another Kind of Migration

Change is the only constant in life, and it's a regular part of enterprise IT management, too. Another sort of migration takes place in one shop where the 3000 has been retired. Specialized scripts for automation using Reflection are being replaced. Thousands of them.

RhumbaMicro Focus, which owns Reflection now as well as its own terminal emulator Rumba, is sparking this wholesale turnover of technology. Customers are being sold on the benefits of the Micro Focus product as part of a suite of interlocking technologies. When that strategic decision is taken, as the British like to say (Micro Focus has its HQ in the country) the following scenario plays out.

Glenn Mitchell of BlueCross BlueShield of South Carolina reported his story, after reading our report on Micro Focus acquiring Attachmate.

I can certainly see many parallels between the latest change at our organization and the migrations many of us undertook from MPE to other platforms. 

It has been many years since I was heavily involved with the 3000 and the 3000 community.  One of the ties back to those old days has been that we use Reflection 3270 as our mainframe terminal emulator here. I’ve done a number of extensive macros in Reflection VBA to assist our customers and developers, and I understand we have thousands of Reflection VBA and Reflection basic scripts in use throughout the company. (We’re a mainframe-centric organization specializing in high-volume claims processing, including Medicare claims in the US.)

Some months ago, I was told we were dropping Reflection and moving to Rumba by Micro Focus (the old Wall Data product) as a cost-saving measure. As part of that move, all of my macros will need to be converted to use the EHLAPPI interface in Rumba.  According to the support staff here, a conversion was going to be required anyway to move to the latest version of Reflection. Well, the support staff has done a good job and many thousands of macros run pretty successfully with some special conversion tools they’ve provided.

Of course, mine don’t, yet.

Read "Another Kind of Migration" in full

Posted by Ron Seybold at 09:10 PM in Migration, User Reports | Permalink | Comments (0)

October 07, 2014

HP decides to break up the brand

HP Enterprise Corp. StrategyAnd in one stroke of genius, it's become 1984 again at Hewlett-Packard. Yesterday brought on a new chorus for an old strategy: sell computers to companies, and leave the personal stuff to others. Except that one of the others selling personal computers, plus the printers usually connected to PCs, is another generation of the company. The CEO of Hewlett-Packard is calling the split-off company HP Inc. But for purposes of mission and growth, you could call it HP Ink.

AnalysisTo be clear, that's a broad definition we used up there to define that stroke of genius. Brilliance is something else, but genius can be just a powerful force for good or for ill. Definition 3 of the word in Apple's built-in dictionary on my desktop calls genius "a person regarded as exerting a powerful influence over another for good or evil: He sees Adams as the man's evil genius." It's from Latin meaning an attendant spirit present from one's birth, innate ability, or inclination.

What's become the nature of Hewlett-Packard, its innate ability? The company was founded on one ability and then had a second grafted onto its first success. It's been 30 years now since 1984, when the vendor which invented MPE and the 3000 has been inventing products for consumers. The LaserJet opened the door for a torrent of ink and toner to sweep around traditional technology innovations. Before there was a need for a battalion of printing devices and a phalanx of personal devices, the old HP logo represented business and scientific computing. Plus a world-leading instruments business whose profile was an icon for what HP was known for best.

HP's been down this path before, splitting off those instruments into Agilent in 1999. A few months later Carly Fiorina won the approval of then-ink czar Dick Hackborn, placing her in the CEO's seat. Yesterday's announcement of splitting the company into two complementary entities returns the Hewlett-Packard name to enterprise computing. But it seems the core values of the only major IT vendor named after its founders won't rebound into favor. Not on the strength of just splitting off high-cost, high volume ink and PC business. HP needs to impress people with what it builds again. Not just what it can aggregate and integrate.

A few notes we took away from that announcement:

  • HP says it aims to be two Fortune 50 companies after breakup, but more nimble and focused
  • "The brand is no longer an issue," say HP executives, and breaking up the brand will create equal-sized businesses.
  • An extra 5,000 layoffs come along with the split-up. The running total is now 55,000 on the clock that started in 2011.
  • HP likes its own idea; prior chairman Ralph Whitworth called it a "Brilliant value-enhancing move at the perfect time in the turnaround."
  • CEO Meg Whitman says HP's turnaround made the breakup possible.
  • Its stock traded more than five times its usual daily shares on breakup news, and picked up almost 5 percent in share value. HPQ also gave away all of that gain, and more, the very next day.

That's how it goes in the commodity computing market: easy come, say the customers, and easy go. It might be why Whitman is helping the brand called Hewlett-Packard break away from the commodity business.

Read "HP decides to break up the brand" in full

Posted by Ron Seybold at 04:55 PM in History, Migration, News Outta HP | Permalink | Comments (0)

October 06, 2014

HP to break itself, dividing into 2 companies

Two public HP companiesCompanies of equal sizes will sell products branded HP. But the blue logo goes to the new HP Inc.

Hewlett-Packard announced this morning that it will divide itself into two publicly-traded corporations, a move that shareholders and stock analysts have been demanding and predicting for years. The division of the company will be along product lines. The business server operations will be contained in the new Hewlett-Packard Enterprise, while PC and printer businesses will comprise the new HP, Inc.

The vendor said in a press release that the restructuring will "define the next generation of technology infrastructure." The reorganization will also spin out the least profitable, but largest, segment of HP's business into its own unit. HP still ranks in the top five among PC makers and is one of the largest makers of printers in the world.

HP double logoMeg Whitman will be CEO and president of the Hewlett-Packard Enterprise company. Pat Russo will chair a new Hewlett-Packard Enterprise board of directors. Last month Hewlett-Packard -- the full corporation founded by Bill Hewlett and Dave Packard in 1939 -- had named Whitman as chairman of the board and CEO. By breaking up the company, Whitman will cede some control of its most competitive and popular product segments.

Dion Weisler will be the head of the new HP, Inc. as CEO and president. Whitman will chair the HP Inc. board of directors. HP said it will still meet its profit forecasts for the fiscal year that ends on Oct. 31. It also said that it "issues a fiscal 2015 non-GAAP diluted Earnings Per Share outlook of $3.83-$4.03." That is the sweetest way of forecasting a profit, using non-Generally Accepted Accounting Practices. But it's not clear if that's HP Inc. profits, or profits for Hewlett-Packard Enterprise. And the vendor said it would take all of fiscal 2015 to complete the transaction.

“The decision to separate into two market-leading companies underscores our commitment to the turnaround plan," said Whitman, who's led HP through three years of a five-year turnaround plan. "It will provide each new company with the independence, focus, financial resources, and flexibility they need to adapt quickly to market and customer dynamics, while generating long-term value for shareholders.

"In short, by transitioning now from one HP to two new companies, created out of our successful turnaround efforts, we will be in an even better position to compete in the market, support our customers and partners, and deliver maximum value to our shareholders."

Read "HP to break itself, dividing into 2 companies" in full

Posted by Ron Seybold at 11:40 AM in Homesteading, Migration, News Outta HP, Newsmakers | Permalink | Comments (0)

October 03, 2014

Wearable computing, cloud IT: not news

By Ron Seybold

Ever since the start of summer, there's been plenty of ThrowBack Thursday pieces available to run. Always with a photo, they seem to get highest readership among our customers.

Print-ExclusiveOne throwback piece that’s headed to my recycle bin today is a 1991 press release from Park Engineering. In that springtime, the Spokane company made its news by announcing in a press release, “First ‘Wearable’ Computer Brings Desktop Computing Power to Mobile Workers.” The CompCap weighed a full pound, and you were instructed to wear it on your head. A hardhat version was self-contained, while another to wear around your head or as a hatband needed electronics built into a belt or vest. 

What a marvel. What news, this device that had a virtual miniature display called the Private Eye, floating a few feet in front of the user. (Hope they weren’t driving a forklift at the time.) Starting at $1,500 and running up to $3,000 each, the CompCaps had their own OS, perhaps as unique as MPE/XL. Just without the thousands of apps that drove HP’s 3000 sales during year.

Editorial-IconIt would be news if a CompCap has ever been built, let alone sold. But it’s possible that an HP 3000 manufactured the same year could be running a company’s manufacturing today. It would be a 9x7 and well into antiquity. That would be news too, but of the amazing and astounding variety. That 9x7 is out there somewhere, proving there’s a need for a virtual 3000, the MPE/iX machine that’s not built by HP. Because the age of the iron is not the age of MPE.

Read "Wearable computing, cloud IT: not news" in full

Posted by Ron Seybold at 07:30 AM in History, Homesteading | Permalink | Comments (0)

October 02, 2014

TBT: A Race to Engineering Discipline

WhatIfHorsesA two-page ad, many months after the reckoning of the prior fall, asked the business community to imagine More Raw Horsepower from a system called the HP 3000 Series 930.

October was a month to remember from an engineering era that Hewlett-Packard would rather forget. The era was the cycle of what independent contractors called Destructive Testing, the repeated, broad-spectrum hammering on the new MPE/XL operating system that was going to power the first PA-RISC Series 900 HP 3000. HP paid these experts to break what it had built.

The computer rolled out in the early fall of 1987, a full year after its Unix counterpart. It was just 12 months earlier that HP's tech czar Joel Birnbaum swore that PA-RISC would emerge from a swamp of too-sweet project management.

More than 1,000 engineers would eventually work on pulling MPE/XL and its Reduced Instruction Set Computing steed 900 Series out of a ditch. During 1985 and through much of 1986, status reports about the development of this faster 3000 were encouraging. No show-stoppers there, not with so much pressure on horsepower improvements. The Series 70 was released in 1985, a stop-gap server that ran faster than the Series 64. But not fast enough at plenty of major HP customers, the group called the Red Accounts.

Series 930 SuperminiThose lab updates were being sweetened because a replacement for the Series 64 and 70 was overdue. HP had already scrapped the 3000's update plans for HP Vision, broadening the replacement project to call it HP Spectrum. This was design to be used in all HP servers, working through an HP-invented RISC chip architecture. The twinkle in Birnbaum's eye while he was in IBM, RISC was going to be a business success. HP hired him away to deliver on the RISC promise.

But by October 1986 at a conference whose theme was Focus on the Future, the 900 Series was undeliverable as addressed. Birnbaum had to deliver the news to pressmen, reporters assembled in a conference room. We circled him, standing and taking notes, quizzing Birnbaum as he said the horsepower would arrive. More important was stability. Birnbaum explained patiently that interfaces between MPE software modules were not working as forecast. Not yet.

This didn't appear to be a man accustomed to explaining delays to the public, especially critics from the press. But he uttered a phrase that afternoon in Detroit at Interex '86 that seemed to close down the probing questions. We wanted to know, after all, could anyone believe that the vanguard Series 930 server would appear after more than two years of reboots and delays?

Read "TBT: A Race to Engineering Discipline" in full

Posted by Ron Seybold at 11:20 AM in History | Permalink | Comments (0)

October 01, 2014

Steady pace means un-news isn't no news

By Ron Seybold

Editorial-IconWhat does it say about the HP 3000 when the steadiest story about the 3000 doesn’t involve an HP 3000? You can’t wear one, like an Apple Watch, or buy a brand-new HP 3000. Your server’s operating system is unchanged after more than four years, unless you’re buying a custom-crafted patch.  The mission for this general purpose machine hasn’t changed, either.

It might be that the most constant news about the HP 3000 of 2014 is there’s no fresh news. So what’s an editor to do when his blog and publication includes the word Newswire? To conjure content, I reach back, and I look ahead. What is ahead of us doesn’t involve much HP iron, and certainly nothing new wearing a Hewlett-Packard 3000 badge on its chest. I only have to reach back to see a story where wearing something to compute wasn’t a novel concept. Not according to my files here in the office. 

I work a lot out of the files these days.

Print-ExclusiveThis rambling is a way of describing my frustration and then a calm acceptance about the limited rate of change. I came into the journalism business with the knowledge that new was best. My first newspapering job came in a small Texas town with a competing paper just down the block. You’d wonder why a county seat of 3,500 would ever need two newspapers. It was 1982, a year when plenty of towns had two papers. Journalism has changed. Now there’s an infographic out there with the Then and Now of information. A reporter is now considered a blogger, and press conferences are now Twitter chats.

I came to tech journalism and got scooped within three weeks. Scoop, for any who’ve forgotten, is when a competitor learns and prints something before you can. One year at an Interex conference, we scooped all day at our booth. Ice cream, supplied by the hotel’s catering department. The word was synonymous with elite information.

There are press releases today, but they’re called content. Some still fill my inbox, but they come from non-3000 markets. The investment of an envelope and stamp is gone, just like an investment in HP-branded iron has been replaced by an offsite, up in the cloud server. Not free, but oh so less costly.

Read "Steady pace means un-news isn't no news" in full

Posted by Ron Seybold at 07:24 PM in Homesteading, Newsmakers | Permalink | Comments (0)

September 30, 2014

Reflection touchstone: a screen benchmark

Reflection boxThe most recent transfer of Attachmate's products and people into the Micro Focus organization sparked some study of what matters to 3000 migrators and homesteaders. Both kinds of customers need to pay mind to what their application's screens look like. Whatever's correct tends to be first measured by an Attachmate product.

That would be Reflection, still the terminal emulator in widest use among the homesteading community as well as a benchmark for any others making a 3000 change. ScreenJet's Alan Yeo kept his eye on the Micro Focus reverse-takeover, as the parent company is headquartered in the UK. (That's still a United Kingdom, after the Scotland vote, much to the UK citizen's relief.)

Reflection's fate remains as unchanged at Scotland's. There will be some modification over time. And the software's screen views are often evoked while change is afoot.

Attachmate "had a big push on re-launching its Rhumba terminal emulator about three years ago," he said. A few migration clients using Micro Focus COBOL were being pushed hard to drop Reflection, he explained. A battery of internal tests at ScreenJet determined that Rhumba would work, intrinsically, with ScreenJet's product. But the standard for terminal emulation, in the mind of somebody who knows VPlus screen handling better than most on the planet, remains Reflection.

"If anything doesn't work, and it works with Reflection, the go fix Rhumba," Yeo said he advised the customers being pressed into the Rhumba re-launch. "If you report a problem, re-test with Reflection." The tests at ScreenJet produced some suggested repairs to Rhumba, he added.

ScreenJet never heard from a migrating customer who made a choice to drop Reflection. He's got no prejudices. "I don't care what any customer uses, so long as what they use works, and doesn't break what they're using from us," Yeo said. "Reflection is pretty much a touchstone. It's not to say that I haven't gone back at times and done testing on a terminal to find out what really happens. Sometimes I have to go back to a customer and say 'I'm sorry, but it's an artifact of even Reflection not doing it right.' "

And so your community still may have some need for 3000 terminals, the real sort. The 3000 newsgroup recently carried an ad for some of this extra-focused HP iron -- offered by an independent broker.

Posted by Ron Seybold at 02:46 PM in Homesteading, Migration | Permalink | Comments (0)

September 29, 2014

Classic advice: COBOL Choices, Years Later

Five years ago on this day we ran a report from a conversion company about the lineup of COBOL choices. Just a few weeks ago, the largest provider of COBOL swallowed up Attachmate, owners of the Reflection lineup. It made the impact of the acquisitive Micro Focus on the 3000 migrator even greater.

Conversion and migration supplier Unicon Conversion Technologies had sent us a white paper that outlined decisions to enable 3000 conversions to Windows. Unicon's Mike Howard attended that year's e3000 Community Meet, which included plenty of COBOL discussion. Here's Howard's take on the COBOL choices for those headed to Windows. Much is of it is still on target.

By Mike Howard

When HP announced it was discontinuing the HP 3000, there were four main Windows COBOLs: RM COBOL, ACUCOBOL, Micro Focus COBOL and Fujitsu COBOL.

But in May 2007, Micro Focus acquired ACUCOBOL when they bought Acucorp. Shortly after they also acquired RM COBOL when they bought Liant. ACUCOBOL is very similar to RM COBOL but has more features and functions. Micro Focus immediately incorporated the RM COBOL product into ACUCOBOL and stopped selling RM COBOL. Micro Focus is now incorporating ACUCOBOL into the Micro Focus COBOL product. (Ed. The Project Meld was not completed, and ACUCOBOL is being called Micro Focus extend today.)

So today, for new Windows COBOL customers there are two COBOLs -- Micro Focus and Fujitsu. In summary, Micro Focus is an all-embracing, all-platform COBOL with excellent support, but it is expensive. Fujitsu is a Windows product with limited support but an extremely attractive price. We have found that both products are very stable and very fast in production. Both charge the same for support, 20 percent per year. The differences lie in cost of ownership vs. response time of support.

Read "Classic advice: COBOL Choices, Years Later" in full

Posted by Ron Seybold at 11:25 AM in Migration | Permalink | Comments (0)

September 26, 2014

Making History By Staying Together

ScotlandMontageWhat price and what value can we put on borders? While we put the latest 3000 Newswire print issue to bed last week, the United Kingdom’s region of Scotland was voting for its independence from Great Britain. One of our favorite 3000 resources and supporters, Alan Yeo, didn't know if he’d wake up at the end of last week using UK or GB as the acronym to define his country. If Scotland were to go, the Kingdom would no longer be United.

Cooler heads prevailed, and the No vote to block the push to secede squashed the Yes by a large margin. The country made history with the largest voter turnout every recorded. There's some good come of the competition, anyway.

The independence balloting called to mind what the Web has done with borders: erased them all, virtually. Some of the more draconian countries have fences up to keep their citizens’ thoughts and beliefs in, but even China with its Alibaba marketplace — where you can but a 747 or drone motors over the Web equivalent of eBay or Amazon — is erasing its borders. Scotland, inexplicably, wants to erect new ones.

Here in Austin, and through most of Texas, bumper stickers ride on trucks with the state’s outline the command, “Secede!” We are the United States of America, though. Pockets of rebellion boil up in places like the Texas border with Mexico, or up in Idaho. But there’s too much in common among government sentiment to break us up into pieces.

I know about the desire for borders. Our nitwit governor here was on TV last fall, here in Austin, describing our progressive town as “the blueberry in a sea of red.” Yes, we’re juicy, sweet, and different. But we’re Texans, too, much to the governor’s dismay. That TV show didn’t hit Jimmy Kimmel’s show from Dallas or Houston.

So it has gone for the Web and 3000 users. On pages over the years, both paper on on the Web, we cater to constituencies as diverse as possible. One set of readers is done with MPE, making plans to archive systems or scrap them. Another is devoted to their status quo, the devils they know rather than the devils they don’t know how much upset and cost they’ll trigger.

Read "Making History By Staying Together" in full

Posted by Ron Seybold at 10:13 AM in Homesteading, Migration, Newsmakers | Permalink | Comments (0)

September 25, 2014

TBT: Early winter's taste visits Interex '94

Uhh-coverIt stunned nearly everybody, but the final day of the annual Interex user conference, 20 years ago this week, did not herald the start of Fall. That season might have filled pages on everybody's calendar, but the skies over Denver were filled with snowflakes on Sept. 21. Thousands of HP 3000 customers had to scurry through soggy streets in a month where leaves were supposed to be falling.

Everything happened at an Interex, eventually. Robelle's Neil Armstrong wrote about it in the What's Up Doc newsletter the vendor produced that year.

Welcome to Winterex 1994.

Once again the weather attempted to upstage various announcements and goings on at the Interex Conference. This year it snowed on the Wednesday afternoon of the Denver conference. The "snow" storm, however, was nothing compared to hurricane Andrew which hit New Orleans during Interex '92.

This year's conference was certainly a hit with a lot of the people I talked to. The last Interex I attended was in Boston in 1990, which became known as the Great Unbundling of TurboImage Debate. Interex '94 was a pleasant contrast with HP's new product announcements, the bundling of ARPA services and a general positive tone regarding the future of the HP 3000. The HP booth was a beehive of activity with Client-Server demonstrations and huge printers on display.

Armstrong went on to say that his favorite view at the show was seeing a camera connected to an HP 9000 workstation, one that delivered a live pictures of people passing by the box. "The fun part was moving from side to side quickly and watching the CPU graph go up," he added.

This was the year when the pushback started to ruffle the Unix juggernaut that had promised open systems for so long. Windows was still a year away from being desktop-useful. But that didn't keep the technical leadership from creating a Unix Hater's Handbook.

Read "TBT: Early winter's taste visits Interex '94" in full

Posted by Ron Seybold at 02:49 PM in History, Newsmakers | Permalink | Comments (0)

September 24, 2014

Did Charon get to where HP could've gone?

The past can't be changed, but that doesn't mean it's not useful in planning. There are still a surprising number of companies that want to stand pat without regard to the future of their hardware running MPE/iX. Some of it is old already, while other servers -- even those newest -- are now moving into their 10th year of service.

Integrityrx2660_frontHewlett-Packard's planning for the future of MPE/iX hosts once included a bold move. The operating system was going to run natively on Itanium-based servers, the IA-64 Integrity line (above) that hosts VMS and NonStop today. It was a project that did not make HP's budget cuts of more than a decade ago, and so the whole lineup got canceled. There might have been another way, something that HP could arrive at -- years after Stromasys started selling the solution.

Native hosting is always the preferred solution for an OS and its iron, sure. But there's so much virtualization these days; VMware is a significant market force. What if HP had taken MPE/iX and just put it onto another operating system's back? What if the OS that drives 3000 apps might have taken a ride in a carriage of Unix, or Linux?

HP did this sort of miracle once for the 3000, calling it Compatibility Mode. There was a massive revison of hardware and software to arrive at the PA-RISC generation, but the changes were transparent to customers. You ran your apps in CM, until you could move them forward. In the '90s, companies used compatibility mode for years, installing newer hardware and moving up to better performance by revising their applications.

"If all HP had done was to create a Compatibility Mode for MPE on IA-64," said ScreenJet's Alan Yeo, "nobody would have batted an eyelid about swapping to an HP-UX box to run their company's software."

At its heart, this is what Stromasys has done with its software. The only difference to the customers is that it's a solution not sold and supported by their hardware vendor.

Read "Did Charon get to where HP could've gone?" in full

Posted by Ron Seybold at 07:31 PM in Migration, News Outta HP | Permalink | Comments (1)

September 23, 2014

Pre-Migration Cleanup Techniques

Migrations are inevitable. The Yolo County Office of Education is on its way to a Windows-based system, after many years of HP 3000 reliance. Ernie Newton of the Information and Technology Services arm of the organization is moving his 3000 data. He's doing a clean-up, a great practice even if you're not heading off of MPE.

I am cleaning up our IMAGE databases for the inevitable move to Microsoft’s SQL Server. One thing I've encountered is that Suprtool does not like null characters where there should be numbers.

I know that I have invalid characters, (non-numeric), in a field called ITEM-NUMBER.  But when I try to find those records, Suprtool chokes and abruptly stops the search. Here's what I get...

IF ITEM-NUMBER < 0 OR ITEM-NUMBER > 9999
X

Error:  Illegal ascii digit encountered. Please check all data sources
Input record number: 1

Is there a way to run Suprtool to help it find these records? Query finds them just fine, but Query doesn't have to ability to do what I want to do. 

After being reminded that "Nulls are not numbers," by Olav Kappert, and "try to use a byte string to compare (like < "a" or > "z") or something like that," Robelle's Neil Armstrong weighed in.

You can find any character you want by using the Clean, $findclean and $clean feature. The first issue to deal with is to re-define the item-number as a byte type in order to use the function.

Read "Pre-Migration Cleanup Techniques" in full

Posted by Ron Seybold at 05:50 PM in Hidden Value, Migration | Permalink | Comments (0)

September 22, 2014

Ways to Create PDFs from 3000 Output

Years ago -- okay, seven -- we reported the abilities of the Sanface Software solution to create PDF files out of HP 3000 output. But there are other ways and tools to do this, a task that's essential to sharing data reports between HP 3000s and the rest of the world's computers.

On the HP 3000 newsgroup, a veteran 3000 developer has asked,

Has anyone got any experience involving taking a file in an output queue and creating a PDF version of it?

"We use text2pdf v1.1 and have not had any problems since we installed it in October 2001," said Robert Mills of Pinnacle Entertainment. "I have e-mailed a copy of this utility and our command file to 27 people. Never knew that so many sites wanted to generate PDFs from their 3000s."

The program is a good example of 3000 source code solutions. This one was created as far back as the days of MPE/iX 6.0, a system release which HP has not supported since 2005.

Read "Ways to Create PDFs from 3000 Output" in full

Posted by Ron Seybold at 06:43 PM in Hidden Value, Homesteading | Permalink | Comments (0)

September 19, 2014

Passing FTP Capabilities to MPE

Ws-FTP ProHP 3000s do lots of duty with data from outside the server. The 3000's FTP services sit ready to handle transfers from the world of Windows, as well as other systems, and PCs far outnumber the non-Windows computers networked to 3000s. Several good, low-cost FTP clients on Windows communicate with the 3000, even though MPE/iX still has some unique "features" in its FTP server.

Our former columnist John Burke once reported that his HP 3000 emitted a second line of text during an FTP session that could confuse the open source FTP client FileZilla:

FileZilla issues the PWD command to get the working directory information. On every other system I've tried, the result is something like 257 "home/openmpe" is the current working directory However, MPE responds with something like 257-"/SYSADMIN/PUB" is the current directory. 257 "MGR.SYSADMIN,PUB" is the current session. The second line appears to be confusing FileZilla because it reports the current directory as /MGR.SYSADMIN,PUB/, which of course does not work.

Back when it was a freeware, Craig Lalley took note of a worthy solution, WS-FTP from IP Switch. The product is now for sale but its client is not costly. And an MPE setting can remove the problems that can choke up FileZilla.

Read "Passing FTP Capabilities to MPE" in full

Posted by Ron Seybold at 04:05 PM in Hidden Value, Homesteading | Permalink | Comments (0)

September 18, 2014

Beefy servers link VMware and MPE futures

DL580VMware is installed at the majority of HP 3000 sites. The virtualization software delivers flexibility in using a wider array of operating environments to virtualize Intel-based hardware, and so it's a useful tool for putting Windows, Linux and Apple's OS X on a variety of hosting hardware. Everything looks like Intel x86 -- to be exact, Xeon -- once VMware is on board.

This is one of the reasons VMware is a common companion with the Stromasys CHARON virtualized HP 3000. A partition of a server can be designated as an x86 box. And then on top of this emulation, according to Doug Smith of Stromasys

Some people already have VMware installed for the rest of their applications, and if they choose to use it with CHARON it's fine. There are others that see more of a perfomance issue -- there's more performance if they actually run it on a standalone server.

On VMware you have the host hardware, and a lot of the customers haven't specified the host hardware beefy enough to run the application. You run into a problem with that every once in awhile, so they end up going to a standalone server. That's because they don't want to go through the expense of updating all of their VMware hosts.

Initial testing performed under VMware in these under-spec'ed hosts "won't give you the performance you're looking for," Smith explained. "Under the right hardware, the numbers jump up big-time." A forthcoming case study will lay out the differences for CHARON HPA/3000, he added.

Read "Beefy servers link VMware and MPE futures" in full

Posted by Ron Seybold at 07:55 PM in Homesteading | Permalink | Comments (0)

September 16, 2014

Advice on uptime, net gateways and sockets

Is there a way to use the 3000's networking to check how long your system has been up?

James Hofmeister replies:

If you have SNMP running, a query to check system uptime is:

: snmpget ector.atl.hp.com public system.sysUpTime.0
Name: system.sysUpTime.0
Timeticks: (418638300) 48 days, 10:53:03

I get no awards for 48 days uptime, but I use my machines to duplicate, beta test and verify repair of customer network problems.

Is there a way to scan all the ports on my HP 3000 Series 996: How many are being used, and how many are available?

Mark Bixby replies:

SOCKINFO.NET.SYS can tell you which programs have opened which sockets.

NETTOOL.NET.SYS STATUS,TCPSTAT and STATUS,UDPSTAT can also give you useful information about sockets, particularly STATUS,TCPSTAT and CONNTABLE.

Read "Advice on uptime, net gateways and sockets" in full

Posted by Ron Seybold at 06:27 PM in Hidden Value | Permalink | Comments (0)

September 15, 2014

WRQ's Reflection goes deeper into coffers

Micro Focus logoNews came to me today about the Sept. 15 deal between Attachmate and Micro Focus. Two of the larger enterprise software makers which matter to 3000 vendors, the connectivity company and world's biggest COBOL vendor, will be doing a merger. With this, the consolidation of enterprise vendors takes another step into its future, and Reflection goes deeper into another software corporation's coffers.

Below is some of the story as told by Micro Focus, in a message to its clients and customers, about a $1.2 billion all-stock deal that leaves Micro Focus owning 60 percent of Attachmate.

Our intention is to preserve the full portfolios of strong, leading products in both Micro Focus and Attachmate going forward. We will draw on our recent acquisitions’ track record of successfully integrating any overlapping product sets.

Business logic and data that lies at the heart of operational effectiveness is increasingly exposed to very complex IT environments, as well as recent technology developments such as the cloud, mobility and virtualization. The combination of Micro Focus and Attachmate creates a leading technology company that will be well positioned to give organizations the ability to exploit the opportunities these trends produce whilst also leveraging prior investments and established IT assets to effectively bridge the old and the new.

For those who are counting up what kinds of products will be preserved -- in addition to the Reflection line -- the merger also brings Novell, NetIQ, and SUSE Linux under the control of Micro Focus. It would take some detailed calculating to figure the total number of products being preserved. But more than 200 in the portfolio would not be an errant guess.

Read "WRQ's Reflection goes deeper into coffers" in full

Posted by Ron Seybold at 03:44 PM in Homesteading, Migration | Permalink | Comments (3)

September 12, 2014

Can HP's cloud deals ground enterprises?

Editors at The New York Times seem to believe the above is true -- or more to the point, that cloud business will come at the expense of HP's hardware revenues. Nobody knows whether this is the way that HP's clouds will rise. Not yet. But a deal to buy an open source software company caught notice of a writer at the NYT, and then came a saucy headline.

Storm-cloudsHP Is Committed to the Cloud, Even If It Kills. The bulk of the story was about Marten Mickos, who sold his company Eucalyptus to Hewlett-Packard and got himself named as General Manager of HP Cloud Business, or somesuch. Open source followers will know Mickos as the man who sold mySQL to Sun, sparking some fury in a customer base that didn't want any connection to major vendor. (As it turned out, Sun wasn't really a major vendor at all, just an object for Oracle acquisition.)

This only matters to migrating customers who use HP 3000s, so if you're still reading and you're homesteading -- or migrating away from HP altogether -- what follows is more for sport than strategic planning. But once more, I'll remind readers that HP is looking for anything that can lift its fortunes. Selling enterprise hardware, like the Integrity servers which are the only island where HP-UX can live, has got a dim outlook. Selling cloud services instead of hardware has plenty more promise, even if it's largely unrealized at HP today.

The rain-clouds in HP's skies come from Amazon, mostly, whose Amazon Web Services is the leader in a growing segment. Eucalyptus works with AWS, and that seems to be the major reason that Mickos gets to direct-report to HP's CEO Meg Whitman. Eucalyptus manages cloud computing systems. HP still sells hardware and software to host private clouds, but an AWS arrangement is a public cloud concept. HP wants to be sure an AWS user can still be an HP customer.

Clouds have a penchant for carrying a customer away from a vendor. Or at least a vendor's hardware. In the NYT story, "HP will have to rely less on revenue from selling hardware, and more on software and service contracts. 'Success will be a tight alignment of many parts of the company,' said Mr. Mickos. 'We have to figure out how to work together.' "

If you go back 24 years, you can find some roots of this HP desire on a stranded pleasure boat in the San Francisco harbor. But until the business critical HP iron stopped selling, the company never believed it would have to set a rapid course for services.

Read "Can HP's cloud deals ground enterprises?" in full

Posted by Ron Seybold at 09:48 PM in Migration, News Outta HP | Permalink | Comments (0)

September 11, 2014

TBT: The things that we miss this season

Show badgesAppropriately enough, part of my well-worn collection of identity theft for ThrowBack Thursday rests in a leather briefcase, another bygone icon of trade show seasons.

This is the time of the year when we got to know each other better -- or for the first time. August and even September hosted annual conferences from Interex, yearly meetings that were an oasis of handshakes among the dusty flats of telephone calls or emails. We'd gather up a badge like one of these in my collection. I come from Depression-Era hoarders, so too much of this kind of thing still lingers on the shelves of my office.

Look, there's the trademark ribbon, colored to let an exhibitor know who was coming down an expo aisle. Often red for the press, because we were supposed to be the megaphones to the countless customers who couldn't come to chilly San Francisco (four times, on my tour of duty) glittery hot Las Vegas (where a waterpark hosted the signature party), or even the gritty streets of Detroit (scene of thefts from the expo floor, among other indignities. We pulled up to Cobo Hall there to see banners for Just Say No to Crack Day, with a phalanx of school busses parked outside. You can't make this stuff up.)

On my first annual conference trek, we took an artisanal booth to the basement expo hall of the Washington DC Hilton. This was an Interex with an HP founder as keynoter, but David Packard wasn't CEO at the time. He had worked in Washington as US Deputy Secretary of Defense while the 3000 was being created, a good post for someone who'd launched the most famous test instrument maker in the free world. (Yes, that's what we called it during the Cold War.) The HP Chronicle where first I edited 3000 stories had never taken a booth to a show before that week in September, and so we had one built out of 2x4s, birch panels, hinges and black carpet, so heavy it required a fork lift just to get it onto the concrete floor. That was the year we learned about the pro-grade booths you could check as luggage, instead of ship as trucked freight like a coffin.

Hey, there's a set of classic computer platform ID stickers, along the bottom of that '89 nametag. HP was calling its PC the Vectra at the time, another example of the company learning its way in the marketing lanes. You wore these to identify each other in a crowd, so you could talk about, say, the Series 100 HP Portable line. If somebody didn't have your sticker, you could move on. It was all about the conversations -- um, sort of in-person Facebook post or Twitter feed. Except what you said couldn't be repeated to 100 million people in the next minute.

There were ways to stand out, if you were inventive. Not necessarily like the buttons (Always Online! was the new 3000 News/Wire) or even the handsome pins (see one attached to the red ribbon of the HP World '96 badge.) You might have little wooden shoes pinned to a ribbon, so people would come by your Holland House software booth and pick up a pair for themselves. People gave away things at these events from glow in the dark yo-yos to chair massages to Polaroid snapshots that you posed for wearing headbands, flashing a peace sign in front of a '60s VW Bus.

PosterLargeThe show in '96 was notable for being the first that didn't bear the user group's name (Interex had struck a deal to call its event HP World) and being the only conference with a football-field-sized publicity stunt. We'd just finished our first year of publication and decided to sponsor the lunch that was served to volunteers putting up the World's Largest Poster on an Anaheim high school field. The booster club served the lunch to the 3000 faithful; some took away a souvenir sunburn from walking on the white panels in Southern California's August.

There are still trade shows in HP's marketplace, but all of them are run by HP with user group help and speakers. The trade is in secrets as well as techniques and sales strategies. It's been nearly a decade, though, since a hurricane postponed a show -- and that wasn't the only annual meeting to face the wrath of a storm. That's what you risk when you meet in August and September, and your moveable feasts include stops along the Gulf of Mexico.

Read "TBT: The things that we miss this season" in full

Posted by Ron Seybold at 09:59 PM in History, Homesteading | Permalink | Comments (0)

September 10, 2014

One Course to Sail a 3000 Into the Cloud

People in IT have come to understand the meanings and potential for the term cloud computing. But plenty of them don't trust it, according to a recent survey. Not with many mission-critical apps, anyway. Since HP 3000 managers have always had a belt-plus-suspenders approach to datacenter management, we'll bet that a great percentage of them are among the doubters about cloud security.

Docker_(container_engine)_logoRemote instances of HP 3000s have been with the community as long as MPE could boot a server. But now, knowing which precise server will deliver an application isn't part of the cloud's design. Even as recently as this year, companies are getting by with 3000 computing by using a server located outside their site, sometimes even outside their state.

It's the state of cloud computing security that gives IT pros some pause. According to a study conducted this year by Unisys (remember their mainframes?) and IDG Research, more than 70 percent of 350 respondents feel security is the chief obstacle in cloud deployment. IT executives want to collect data about the security of data that's in the cloud.

The technology to put Linux instances into cloud computing is already available. And Linux is essential to installing the HPA version of CHARON from Stromasys. There's been no announcement of a cloud edition of the virtualization product. But Docker looks like tech that could help, according to our contributor and 3000 consultant Brian Edminster.

"Docker struck me as an easy mechanism to stand up Linux instances in the cloud -- any number of different clouds, actually," Edminster said. According to a Wiki article Edminster pointed at, Docker is based upon open source software, the sort of solution he's been tracking for MPE users for many years.

Read "One Course to Sail a 3000 Into the Cloud" in full

Posted by Ron Seybold at 09:41 PM in Homesteading, Newsmakers | Permalink | Comments (0)

September 09, 2014

Remaining on Watch for HP Innovation

Apple WatchEarlier today Apple unveiled the descriptions and benefits of wearing a full functioning computer for the first time. Well, maybe not for the very first time. But for the first time in the modern era of computing, anyway. The Apple Watch defines the Tim Cook era at the company, and it will still need some tuning up through several generations. But this time around, the watch that breaks ground by riding on wrists won't need a stylus -- just an iPhone.

The instance of this is called the Apple Watch -- say goodbye to any new product lines being started with an "i" for now. A watch is not an enterprise computing tool, some will argue. But that was said about the iPhone, too -- a device that turned out to be a portable computer of breakthrough size. HP 3000 acolyte Wirt Atmar wrote a famous newsgroup post about the first iPhones, being like "beautiful cruise ships where the bathrooms don't work."

The Apple Watch, of course, won't be anywhere close to perfect on first release Early Next Year. People forget that the iPhone was a work in progress though most of its first year. That's a better track record than the HP 3000 had at first shipment, late in 1972. That system that's survived 40 years in a useful form -- 1974 marks the year when MPE and HP iron finally had an acceptible match -- got returned to HP in many instances.

Screen Shot 2014-09-09 at 4.55.43 PMThe elder members of our 3000 community will recall the HP-01, a wristwatch that wanted to be a calculator at the same time. Nobody had considered wearing a calculator, and nobody had asked for a wearable one, either. But HP felt compelled to innovate out of its calculator genius factory in Corvallis, Oregon, and so a short-lived product, designed to satisfy engineers, made its way into HP lore in 1977.


HP-01"All of the integrated circuits and three discrete components for the oscillator are combined in a hybrid circuit on a five-layer ceramic substrate," said the article in the HP Journal, the every other month paper publication where engineers read about innovations, and the more technical customer was steered to see how Hewlett-Packard could deploy superior design. The problem was that it was 1977, and the company was sailing too far afield from its customers' desires with the HP-01. 1977 was a year when HP had scrabbled to come up with a Series II of the HP3000, a device more important to anyone who wanted to leave IBM batch computing behind and get more interactive. People who bought calculators had no concept of mobile computing. Even a luggable computer was still six years away.

HP-01 closeupBut the HP-01 did accomplish one benefit for the HP customer, who even then was a consumer, of business products. It showed the company was ardent about the need to innovate. The HP Journal is long gone, and the heartbeat of the company feels like it runs through personal computers and miniaturization of internal parts that make more of a difference to manufacturing and product margins. Apple built an S1 processor that's "miniaturizing an entire computer system onto a single chip" to make the Apple Watch a reality, something like HP's five-layer hybrid circuit substrate of 1977.

Screen Shot 2014-09-09 at 5.35.45 PMApple's had its share of innovative flops, too -- but the most recent one was from 2001, the PowerMac G4 cube. A breakthrough like this S1 that Apple claims is an industry first. HP's innovations these days are not getting the kind of uptake that you'll see from the Watch next year. Nobody tells a story about computer promise like Apple, right down to calling parts of its team "horological experts," and saying it with a straight face. In contrast, HP's Moonshot and the like are important to very large customers, but the small business innovation has been limited to fan-cooling technology. Not sexy enough to earn its own video with a spacey soundtrack.

Why care? One reason might be that HP's working to convince the world, its customers, and its investors that innovation is still embedded in its DNA. It takes more than slapping the word "Invent" under the logo. Innovation is hailed by the markets, not the engineers who designed it. Everything is a consumer product by now, since we're consuming computing as if it were a wristwatch.

Read "Remaining on Watch for HP Innovation" in full

Posted by Ron Seybold at 05:55 PM in History, Newsmakers | Permalink | Comments (1)

September 08, 2014

Who else is still out there 3000 computing?

MaytagEmploying an HP 3000 can seem as lonely as being the Maytag Repairman. He's the iconic advertising character who didn't see many customers because a Maytag washing machine was so reliable. HP 3000s have shown that reliability, and many are now in lock-down mode. Nothing will change on them unless absolutely necessary. There is less reason to reach out now and ask somebody a question.

And over the last month and into this one, there's no user conference to bring people together in person. Augusts and Septembers in the decades past always reminded you about the community and its numbers.

Send me a note if you're using a 3000 and would like the world to know about it. If knowing about it would help to generate some sales, then send it all the sooner.

But still today, there have been some check-ins and hand-raising coming from users out there. A few weeks back, Stan Sieler of Allegro invited the readers of the 3000-L newsgroup to make themselves known if they sell gifts for the upcoming shopping season. "As the holiday shopping season approaches," he said, "it occurred to me that it might be nice to have a list of companies that still use the HP 3000... so we could potentially consider doing business with them."

If September 9 seems too early to consider the December holidays, consider this: Any HP 3000 running a retail application, ecommerce or otherwise, has gone into Retail Lockdown by now. Transitions to other servers will have to wait until January for anybody who's not made the move.

Sieler offered up a few companies which he and his firm know about, where 3000s are still running and selling. See's Candies, Houdini Inc, and Wine Country Gift Baskets are doing commerce with gift consumers. We can add that Thompson Cigar out of Tampa is using HP 3000s, and it's got a smoking-hot gift of humidor packs. (Sorry, couldn't resist.) Then there's American Musical Supply, which last year was looking for a COBOL programmer who has Ecometry/Escalate Retail experience.

Another sales location that could provide gifts for the holiday season is in airports. The duty free shops in some major terminals run applications on MPE systems. HMS Host shops, at least four of them, sell gifts using 3000s. Pretty much anything you'd buy in a duty free shop is a gift, for somebody including yourself.

Read "Who else is still out there 3000 computing?" in full

Posted by Ron Seybold at 08:18 PM in Homesteading, Migration, User Reports | Permalink | Comments (0)

September 05, 2014

How to make an HPSUSAN do virtual work

Interex 95 coverOut on the 3000-L newsgroup and mailing list, a 3000 user who's cloaked their identity as "false" asked about using HPSUSAN numbers while installing the CHARON emulator product from Stromasys. The question, and a few answers, were phrased in a tone of code that suggested there might be trouble from HP if an illicit number was used. HPSUSAN is a predefined variable on a 3000, one that's used to ensure software is not illegally replicated or moved to another system without the software vendor's consent.

People have been talking about HPSUSAN for decades by now, even as far back as the Toronto conference that produced the proceedings cover above. A 19-year-old paper from that meeting -- the last one which was not called HP World -- still has useful instructions on the utility of HPSUSAN. More on that in a moment, after we examine what HPSUSAN does today.

On the fully-featured edition of CHARON for the 3000, a current HP 3000's HPSUSAN number is required. Stromasys installs this number on a thumb drive, which is then plugged into the Intel-based server powering CHARON. There's a 36-hour grace period for using CHARON if that thumb drive malfunctions, or comes up missing, according to CHARON customer Jeff Elmer of Dairylea Cooperative.

But the HPSUSAN process and requirement is different for the freeware, A-202 model of CHARON that can be downloaded from the Stromasys website. As of this spring, users of this non-commercial/production model simply must enter any HPSUSAN number -- and affirm they have the right to use this number. Neither HP or Stromasys checks these freeware HPSUSAN numbers. That model of CHARON software isn't meant to replace any production 3000, or even a developer box.

The freeware situation and installing strategy all makes the newsgroup's answers more interesting. One consultant and 3000 manager suggested that a number from a Dell server would be just as binding as anything from a genuine Hewlett-Packard 3000 server.

Read "How to make an HPSUSAN do virtual work" in full

Posted by Ron Seybold at 08:16 PM in Homesteading, User Reports | Permalink | Comments (0)

September 04, 2014

TBT: Practical transition help via HP's files

2004 HPWworld Transition PartnersA 2004 slide of partner logos from an HP presentation.

10 years ago, at the final HP World conference, Hewlett-Packard was working with the Interex user group to educate 3000 users. The lesson in that 2004 conference room carried an HP direction: look away from that MPE/iX system you're managing, the vendor said, and face the transition which is upon you now.

And in that conference room in Atlanta, HP presented a snapshot to prove the customers wouldn't have to face that transition alone.

The meeting was nearly three years after HP laid out its plans for ceasing to build and support the 3000. Some migration was under way at last, but many companies were holding out for a better set of tools and options. HP's 3000 division manager Dave Wilde was glad to share the breadth of the partner community with the conference goers. The slide above is a Throwback, on this Thursday, to an era when MPE and 3000 vendors were considered partners in HP's strategy toward a fresh mission-critical future.

The companies along the top line of this screen of suppliers (click for a larger view) have dwindled to just one by the same name and with the same mission. These were HP's Platinum Migration partners. MB Foster remains on duty -- in the same place, even manning the phones at 800-ANSWERS as it has for decades -- to help transitions succeed, starting with assessment and moving toward implementations. Speedware has become Fresche Legacy, and now focuses on IBM customers and their AS/400 futures. MBS and Lund Performance Solutions are no longer in the transition-migration business.

Many of these companies are still in business, and some are still helping 3000 owners remain in business as well. ScreenJet still sells the tools and supplies the savvy needed to maintain and update legacy interfaces, as well as bring marvels of the past like Transact into the new century. Eloquence sells databases that stand in smoothly for IMAGE/SQL on non-3000 platforms. Robelle continues to sell its Suprtool database manager and its Qedit development tool. Suprtool works on Linux systems by now. Sure, this snapshot is a marketing tool, but it's also a kind of active-duty unit picture of when those who served were standing at attention. It was a lively brigade, your community, even years after HP announced its exit.

There are other partners who've done work on transitions -- either away from HP, or away from the 3000 -- who are not on this slide. Some of them had been in the market for more than a decade at the time, but they didn't fit into HP's picture of the future. You can find some represented on this blog, and in the pages of the Newswire's printed issues. Where is Pivital Solutions on this slide, for example, a company that was authorized to sell new 3000s as recently as just one year earlier?

HP probably needed more than one slide, even in 2004.

Read "TBT: Practical transition help via HP's files" in full

Posted by Ron Seybold at 08:24 PM in History, Homesteading, Migration | Permalink | Comments (0)

September 03, 2014

Moves to Windows open scheduler searches

Some HP 3000 sites are migrating from HP 3000s to Windows .NET systems and architecture. While there's one great advantage in development environment during such a transition -- nothing could be easier to hire than experts in Visual Studio, nee Visual Basic -- companies will have to find a scheduler, one with job handling powers of MPE/iX. Native Windows won't begin to match the 3000's strengths.

Scheduler demo shotMore than three years ago, MB Foster built a scheduler for Windows sites, and customers are sizing up this MBF Scheduler. There's even been interest from IT shops where a HP 3000 has never booted up. They are ofter users of the JDA Direct Commerce (formerly Ecometry-Escalate Retail) software on  Windows servers. These companies never seen an MPE colon prompt, but some need that level of functionality to manage its jobs.

"If senior management has simply decided that Windows was the place to be," said CEO Birket Foster, "we could help automate the business processes -- by managing batch jobs in the regular day and month-end close, as well as handling Ecometry jobs and SQL Server jobs." Automating jobs makes a Windows IT shop manager more productive, like creating another set of hands to help team members. And for a 3000 shop making a transition, something like an independent job handler means they'll be able to stay on schedule with the expected level of productivity.

Read "Moves to Windows open scheduler searches" in full

Posted by Ron Seybold at 05:33 PM in Migration | Permalink | Comments (2)

September 02, 2014

Archival presents prospects for CHARON

Five years ago this week we chronicled the story of Yosemite Community College, a 3000 site that fell to the Unix alternative hosted on then-Sun servers. The MPE apps at Yosemite were from a vendor who'd left the 3000 market, and so the college was doing its own app maintenance. There's a limit to how much of that which an IT department will perform. Eventually the pain of re-developing someone else's source code drives you into re-training and installling new datacenter mission-critical operations.

Edward Berner of Yosemite couldn't hold out, even though he said as far back as 2006 he could use such an emulator product. He was planning, back in 2009, to rent a 3000 for archival purposes.

Fortunately (for the college, but unfortunately for the emulator companies) we've finally managed to retire our HP 3000. I'll start advocating that we sell the hardware to a vendor or something.  After that we can rent a system, or use a service if we need to refer to something from our backup tapes.

But 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 CHARON.

An emulator wouldn't have kept MPE/iX and those applications in production use at Yosemite. "Our main use for an emulator would have been for running the HP 3000 software for a couple years after the migration was mostly done, for historical data and while the last few stray things were migrated," Berner said. "The attraction being that a 1- or 2-processor Intel system is a lot smaller than a 979 -- and the HP 3000 A Series always seemed too expensive to me."

At the University of Washington Medical Center, an HP 3000 has been in archival mode for more than three years. Computer Services Coordinator Deane Bell said the archival system might be in place for a total of 10 years. Given enough time, emulator providers usually catch up to and then lap the used hardware markets. Nobody's forecasting that the UW shop is buying CHARON. But around 2017, it might look better than a well-used Series 900 -- or even a by-then 14-year-old A-Class.

Posted by Ron Seybold at 10:12 PM in Homesteading | Permalink | Comments (0)

August 29, 2014

Finding the Labor Your 3000 Site Needs

LaborersHomesteading on the HP 3000 — whether it's the bridge until migration, archival operation where little changes except backup tapes, or unlimited future-style — takes labor to maintain. Labor is on our minds here at the NewsWire this weekend, when much of the US has taken a few days off from the office or away from the computer keyboard to celebrate the American labor movement. 

We're taking those days off, too. And we'll be back on Sept. 2, like a lot of you with work to do. There's a printed issue for the Fall for me to edit and write for, after all. We're flying in the face of advice that says it's a ticking clock to produce paper based information. We're betting you still count yourself as a pro who knows the movement to digital is not yet complete. When we started the NewsWire, we flew in the face of advice that said, 19 years ago, there was little future for the MPE user.

Your community has been experiencing that much movement, so any tools to track the travels of skilled 3000 pros can be useful. Let me recommend LinkedIn once again. The HP 3000 Community Group at the website -- and LinkedIn has started to specialize in finding people prospects for work -- well, the 3000 group began with a couple of questions that can still kickstart discussions. Again, the LinkedIn advantage is connecting to pros to share with specific work experience details, plus the chance to draw on others' networks through introductions.

Anybody can join for free. Since I launched the HP 3000 group in 2008, we've added 600 members in the group, and there are many others in the LinkedIn network with 3000 experience. Michael Boritz commented on our Group question back at the beginning about who's doing what with the HP 3000 these days.

I’m still working on the 3000. I’ve been working on 3000s since the 1980s, at J.D. Abrams at that time. Since leaving JDA, I worked at Tivoli in Austin (i.e., Unison-Tymlabs) for a couple of years. Since then, I have moved four times — all for new HP 3000 positions.

Read "Finding the Labor Your 3000 Site Needs" in full

Posted by Ron Seybold at 10:25 PM in Homesteading, Web Resources | Permalink | Comments (0)

August 28, 2014

TBT: Days of HP's elite software outlook

Business Software Brochure 83At the end of August of 1983, Hewlett-Packard mailed out a 92-page brochure that showed HP 3000 owners where to get the software they didn't want to create themselves. The Hewlett-Packard Business Software Guide covered the options for both the HP 3000 and the just-launching HP 250. The latter was a system that would sit on a large desktop, run software written for its BASIC operating system, and receive just six pages of specific notice out of the 90-plus in the HP sales guide.

What's interesting about this document -- apart from the fact that nearly all those photos have people in them -- is that HP's own programming development software and application tools are listed first in these pages. And in that order, too; owners of a system in 1983 seemed more likely to need software to create the bespoke applications so common in a system of 31 years ago. Applications from HP were always pushed before anything without the Hewlett-Packard brand.

But as I paged a bit deeper into this Throwback Thursday treasure, I found the genuine vitality that sold 10,000 of these minicomputers in less than 10 years' time: Third-party software, both in tools and in applications. HP made a distinction in this giveaway document for these programs, which they called HP PLUS software. A product could be Listed, or Referenced. But to get more information on either one of them, HP expected you to purchase a catalog with a lot more detail.

Not only was it an era without a Web, but these were the days when you'd pay for paper just to have a complete list of things you might purchase. The biggest issue was "will this run on my system?" That, and whether it really existed.

Read "TBT: Days of HP's elite software outlook" in full

Posted by Ron Seybold at 09:06 PM in History, Homesteading | Permalink | Comments (0)

Search