3000 NewsWire Online Extra Welcome to our 26th edition of Online Extra -- the e-mail update of articles in the February 1998 3000 NewsWire, plus items that have surfaced since we mailed our latest First Class issue. This service is an exclusive to our paid subscribers. We e-mail subscribers this file between the First Class issues they receive by mail, updating stories and adding articles that have developed between issues. EDITORIAL: NOT SO FAST WITH THAT IA-64 REVOLUTION Intel started beating the drum for software development this month in its IA-64 campaign, and HP chimed in with a Software Development Kit (SDK) that helps get HP UX software ready for IA-64-based HP systems. But the revolution won't proceed at the breakneck pace that Intel's marketing department suggests. Loose talk from Intel said that developers who weren't already working on IA-64 porting "were already behind." Well, you're definitely behind the safe cover of pioneers getting arrows in their backsides while breaking in experimental technology. It's important to note that the whole Intel/Merced/Tahoe/IA-64 project is still promises at this point, bereft of even a single available benchmark. And there's no promise at all that the marriage of Unix and IA-64 will provide anything easier to administer than current Unix choices. About all you might hope for is that the ever present reboots associated with Unix systems might finish faster with any IA-64 performance increases. What IA-64 can probably count on is market momentum. Since it's backed by the two biggest suppliers of silicon and software, Intel and Microsoft, it's pretty easy to forecast a lemming-like move to the architecture in time, once systems running it become widely installed. Momentum is important in getting companies to adopt a new technology, and it was the very reason that HP took on Intel as a partner five years ago for its Very Long Instruction Word redesign of PA-RISC. That became the Tahoe project, with other code words to follow. Now it's IA-64. Before that marriage to Intel, HP didn't believe it could make a place for a better PA-RISC against Intel and IBM RISC projects. It was a rare moment of marketing candor from HP. As an HP 3000 customer you need to keep that momentum in mind which you watch HP-UX application suppliers step onto the IA-64 development path. For the moment, those Unix and NT applications are going to take the first arrows in the backside as they pioneer the IA-64 experiment. That was the way it turned out for HP's first RISC project in the 1980's, too. HP 9000 systems using PA-RISC shipped nearly a year before HP could get a 3000 out the door to customers that was RISC-powered. The lag between Unix-based IA-64 and MPE-based systems is likely to be even longer than a year. Why not? Unlike the aging 16-bit hardware HP was improving upon in 1987, there's nothing wrong with PA-RISC today. That's why the HP 3000 division (CSY) intends to keep developing business servers with the 8500, 8700 and later generations of the PA-RISC chips. PA-RISC has 10 years of business success behind it, and an ample base of software developers who understand how to make programs fly on it. IA-64 has neither. Companies that want to bet business results on unproven technology have always had many places to place that kind of wager. However, we'd be surprised if there was much desire to gamble through the coming Year 2000 maelstrom, at least among HP 3000 IT directors. What CSY's choice to "stick with PA-RISC for the near term" means is more stability and less experimentation for HP 3000 sites. You may have fewer applications to choose from as well -- although there's no guarantee that software companies will embrace the new architecture and rewrite for IA-64. CSY says it is glad to trail HP's Unix and NT groups in this effort. General Manager Harry Sterling told us that IA-64 benefits need to appear before his division commits to IA-64 work. "IA-64 has many immediate uses that are being addressed by some other systems," Sterling explained. "When, and if, it has a benefit to our customers' applications, we will address MPE on IA-64." A CLUE ON DNS FOR THE HP 3000 No official word has surfaced yet, but we noted on the Internet that Mark Bixby was passing along a message from HP asking for beta testers for the BIND/iX software that makes hosting Domain Name Services possible from HP 3000s. We know that as of this weekend there's no supported solution for DNS service on HP 3000s. But we do wonder why HP would be seeking beta testers for 3000 software that's still considered freeware and not a supported solution under MPE/iX. NO WORD YET ON THE DDX BUG PATCH STATUS It's been two months since the CSY database lab sent one patch into general release that fixes a bug in Dynamic Detail dataset expansion (DDX). The bug fix that went into general release lets IMAGE/SQL database administrators continue to use DDX without worrying about wiping out data. A second bug fix remained in beta test, as far as we could determine at presstime. The second bug fix is the only means of using the new b-tree indexes -- which CSY has started calling "indexed sequential access" -- along with DDX. B-trees -- we like the old name, for now -- promise performance improvements of up to 100 times faster than the version of IMAGE/SQL without them. We know that DDX gets used by many companies which have too heavy a workload to expand datasets manually. That sounds like the same kind of people who could most benefit from b trees, too. It looks like the people who care the most about DDX should get the biggest bang from b-trees, and this week that combination remains in beta testing out of production on HP 3000s. If you want to use the beta-test patch, ask the Response Center for patch TIXKX45A for MPE/iX 5.0 and TIXKX45B for MPE/iX 5.5. MORE TIPS ON FIGURING OUT EXPRESS 4 INSTALLS The release of the latest version of MPE/iX is another sign of how complex commercial operating system administration has become. Remember, MPE is not as complicated as HP-UX or Windows NT to administer, not by a longshot. Customers report that choosing from thousands of patches for HP-UX is still the norm, while some prayer and intuition is still required for many an NT Service Pack update. But terminology and labelling have gotten in the way of the fourth generation of MPE/iX 5.5. We'd keep calling it Express 4, but it appears it's not really an Express release. CSY's Jon Cohen, who's a key player in the division's release process, said that Express releases contain updates to subsystem products' code. There weren't any such updates for the most current release of MPE/iX 5.5, so technically it's a PowerPatch, not an Express release. There really isn't an Express 4 -- it's more like a PowerPatch 4. The only thing you can count on is HP's VUF number for the release: C.00.55.04. HP just had to call it Express 4 because it began to talk about the release long before it was clear there would be no subsys code updates on that release vehicle. That means, from an operational standpoint, that upgrading to the latest MPE/iX 5.5 release is a matter of getting your subsytems upgraded, and then upgrading your operating system. This requires two tapes, as it always did. But one of the tapes is called Express 3 -- the subsystem update -- and the other is called Express 4, the operating system update. The labelling on these tapes bears some close scrutiny. Express 3's subsys tape is labeled "MPE/IX5.5 EXPRESS 3" and doesn't have the word subsys on the label. HP says its ability to put a lot of information on tape labels is limited. One customer points out that Unison Software makes an HP 3000 application called TAPES/PLUS that permits as many as 245 characters on a six-line label. This application may not in use for MPE/iX releases. Meanwhile, the Express 4 tape is labelled "MPE/iX 5.5 POWERPATCH" and also includes the line "REV C.55.04" on the label. It's unfortunate that this magic combination doesn't have clear instructions on how to install them. In fact, the PowerPatch 4 tape don't come with a Communicator or a document on how to install it. Experienced HP 3000 system managers have been complaining about the confusion for a few weeks, and CSY's Cohen is promising some improvements if he has his way. Meanwhile, HP Response Center engineer and NewsWire subscriber Lars Appel suggests something much closer to 21st Century technology to manage MPE operating system updates: "I wonder if it would be helpful if the manual would be "converted" to a little program that is delivered on each PowerPatch media (or alike) to be "Restore and Run before Installing." It could prompt the user with a few questions about his planned activity, check his disc space, installed software and the like, then print a customized step-by-step extract from the former 'goto goto manual.' To be followed without any goto's. There could be either an option for brief or extended instructions, or it could always be brief but with references to a printed manual with details on special tasks like backup, configuration, error messages and the like." Again, the current process is still better than HP-UX updates, according to the following horror story supplied by Allegro's Michael Hensley after he'd carefully outlined the shortcomings of the PowerPatch 4 release: "I just recently installed a new Unix box for a customer, upgrading from 9.04 to 10.20 at the same time, and my appreciation of MPE is back up in the stratosphere again. HP-UX 10.20 and HP-UX 9.04 shouldn't even be considered the same operating system; the patching process is a nightmare (here's a list of 2,000 patches -- which ones do you want?); SAM broke, and after 16 hours the Response center still couldn't get it fixed and escalated it a second time (it *still* doesn't work)." However, customer comments would seem to indicate that "better than HP-UX upgrades" still isn't clear enough. Given the importance of PowerPatch 4's Year 2000 improvements, and the fact that CSY is going to support 5.5 through the Year 2000, there's still plenty of time and motivation to improve this. One final tip for customers who might be going from a 5.0 MPE/iX to the latest release. Donna Gaverick of Longs Drug reported that "When [5.5's] PowerPatch 2 was released, engineers were told to do the updates in two steps - do a SLT and FOS first with AUTOINST, followed by the subsys PowerPatch second with Patch/iX. THIS DOES NOT WORK anymore. If you are going from 5.0 to PowerPatch 4, do the whole thing in one step with AUTOINST." We got a short note from Dennis Heidner saying that taking the default patches from PowerPatch 4 through AUTOINST will install a potential bug on your system. He recommends installing PowerPatch 4 through the Patch/iX facility: PowerPatch 4 includes a patch MPEJXF7, which is supposed to fix a FSERR105 problem, it also introduces a new bug. The bug can be seen if CSL users have copies of the BOEING written DIRK program. Upon exiting DIRK the session will hang. The problem is a message file/process hang bug introduced by MPEJXF7. Other user mode programs that also use process handling and message files could also be impacted. AUTOINST will install the MPEJXF7 patch! The only way not to install it is to use PATCHiX. The PowerPatch 4 tape has a new copy of PATCHiX included. After installing MPEiX 5.5, and before installing PowerPatch 4, you must restore the new PATCHiX files from the PowerPatch tape. After that step the PATCHiX process will work correctly. With PATCHiX you can chose to veto MPEJXF7.   WHY YOU'D WANT POWERPATCH 4 or EXPRESS 3 If you're wondering what all the fuss is about, expert MPE administrator Andreas Schmidt (who wrote the OpReport on using OpenView ITO on MPE systems in our February issue) recently posted a summary of the enhancements you get after installing these releases. We like the document for its concise approach. In the following list, each enhancement is preceded with a * CI related (your normal interface to the O/S): * PAUSE can wait for jobs to be complete and more! PAUSE sec;JOB=... or INTERVAL= or ;EXIST|WAIT|NOTEXIST ... * INPUT allows to specify the # of characters to be read ;READCNT * PRINT ;NONUM prints numbered files (sic!) * New CI variables (some are already in place because of patches) HPLOCIPADDR, HPREMIPADDR, HPLOCPORT, HPREMPORT, HPSTREAMEDBY, HPLASTJOB, HPOSVERSION, HPRELVERSION, HPLASTSPID, HPSPOOLID, HPYYYY (!), HPSPLITYEAR * LISTF,8 and LISTFILE,8 show file accessors (incl. remote access) * LISTF,9 and LISTFILE,9 show locks * LISTFILE works now with ;SELEQ (These three functions are not described in HELP!) * Enhanced REDO and HELP * Y2K internal changes for some commands to specify a four-digit year, e.g. STREAM;DATE * ALTSEC enhancements for ACDs * more POSIX tools like MOVER, tar, lp, lpstat, lpalt, cancel * internet services inetd, telnet, bootpd, tftpd, remsh System Manager Tasks (but refer to Applications as well): * JOBSECURITY Feature:PASSEXEMPT STREAM jobs without passwords. Using MSTREAM or STREAMX, we have already this in place but now it will work also for the MPE native STREAM command (configured in the right way). We do not plan to make use of it - only if there is a need. Basically: there is no longer ANY need to have passwords in the jobcards! * TurboStore/iX 7*24 True-Online Backup Currently there are some problems in this feature regarding these new keywords. We will continue to run the "semi-true" online backup (=5.0). * TurboStore/iX allows now to store on disk! * FSCHECK enhancements * SubSystem Dumps and quarantine routines during System Aborts * Patch /iX and Stage/iX for patching and configuration switching * Predictive sSpport enhancements * Console switching over LAN * LAN printing, * DTS/TIO Dynamic configuration and host-based switching * on-line device configuration (without re-boot) * DEVCTRL to put tape drives on-line again In addition to the old functions for compression and eject Programmer's Suite: * File-Label LAST MODIFIED changed Only if a file is changed, the last modified date will be changed. * FLABELINFO and FINFO() can return # of sectors and extents * Y2K CALENDAR compliant intrinsic adapted, new date-related intrinsics available * Several AIF enhancements * exec enhancements, * POSIX developer's kit is bundled in * dependent libraries on MPE/iX loader, incl. enhancements of HP Link Editor/iX * RPG/iX enhancements * VPLUS enhancements especially for Y2K: new intrinsics & enhancements * HP Symbolic Debugger/iX enhancements * enhancements in BASIC, C. PASCAL, COBOL * correction of Inform/V and Transact defects (really an enhancement ?!?!) and real enhancements * DCE (Distributed Computer Environment) for Remote Procedure Calls etc. The Database Section: * HP Information Access Server SQL/iX supports now MS Winsock * HP Information Access Server MPE/iX enhancements * ALLBASE/4GL Developer enhancements LABEL, -Verbose, and more * ALLBASE/SQL enhancements ODBC PC API, ANSI standard, STOREONLINE, 50 transactions instead of two, new tools, and lots more CAST functions. But pseudo-mapped files are no longer supported! Security enhancements, Year 2000 compatibility. * IMAGE/SQL and TurboIMAGE/XL enhancements Indexed access, and lots more: new datetime routines, b-trees, scalability, 3rd party support. Jumbos, error messages are more verbose, especially for broken chains. * QUERY enhancements Like B-trees, wildcard retrievals, "no match" * 32-bit ODBC driver New H/W and N/W support: * New CD-ROM H/W (also Optical Libraries) * Supports up to 3.75 GB memory * 100VG-AnyLAN and 100Base-T supported * More mass storage et al. H/W supported (as always), especially DDS-3 Autoloader ! * Legato NetWorker Client available ST. PAUL SOFTWARE REVAMPS EXECUTIVE POSTS The EDI technology supplier for HP 3000s St. Paul Software has been restocking its management positions over the last two months, and we thought we'd bring you up to date on the changes. Mark Becker became Chief Financial Officer, responsible for overseeing all financial aspects of St. Paul Software's business. His past experience encompasses seven years at Deloitte & Touche Consulting Group. Rolf Holman was appointed vice president of sales. Most recently, Holman was the director of national sales and business relations for the Credit Union Industry Group at EDS, a professional services firm that specializes in consulting information and technology. The company appointed Carleton Perry to director of sales. Perry brings 10 years of management, sales and account management experience in the software industry to his new position. Prior to St. Paul Software, he was a channel sales manager at J. River, a connectivity and firewall software company. Finally, the company earlier this month appointed Kimberely Christiansen to director of client services for its EC Center service bureau. St. Paul's spokesperson said "her appointment is the result of the rapid growth the EC Center has experienced and increased volume due to the recent launch of a trading partner enablement program." Christiansen's responsibilities encompass the management of large client projects, including the planning and implementation of numerous vendors, multiple EDI transactions and overseeing EDI processes and personnel. She brings 13 years of management experience, including six years of EDI, information technology and project management expertise to St. Paul Software. Previously, Christiansen was vice president and EDI operations manager at First Bank System, Inc. MAESTRO GETS A MAILING LIST Users of the Maestro job scheduling and management software can enjoy the benefits of a new mailing list of Maestro users. By subscribing to a mailing list you receive messages sent to a public forum to discuss implementation issues and workarounds for using the software, which runs on HP-UX and NT systems as well as HP 3000s. Advanced Computing Environments, which resells and implements the solution, hosts the mailing list, and ACE's Scott Hirsh posted this announcement about it: "ACE has created a (moderated) Maestro listserver for information sharing, problem resolution and discussion of product futures regarding Tivoli's Maestro job scheduling software on all platforms (MPE, UNIX, NT). Of course, you should always first contact Maestro support at Tivoli when you have a question or problem with the product. However,in the unlikely event you have not been able to get from Tivoli the answers you need, the Maestro list is where you should turn. Those of us who spend the most time implementing Maestro will be contributing to the list. Your participation will add to the value of the discussion, and help everyone get the most value out of Maestro. To subscribe, point your browser to: http://www.acellc.com/h tml/maestro_listserver.htm For general information about Maestro, check out Maestro Central at: http://www.acellc.com/html /maestro_central.htm If you have any other questions, feel free to e-mail me directly at scott@acellc.com." If you don't have Web access at work because of firewall considerations, just use the e-mail only instructions to become a part of the mailing list: "To subscribe: Send e-mail to maestro-l-request@acellc.com. In the body of your message, include only the word SUBSCRIBE. The listserver will determine your e-mail address from the return address of your message. You will be notified by the listserver that your name has been added to the list. To unsubscribe: Send e-mail to maestro-l-request@acellc.com. In the body of your message, include only the word UNSUBSCRIBE. You will be notified by the listserver that your name has been removed from the list. " Copyright 1998, The 3000 NewsWire. All rights reserved.