Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) HP 3000 MPE/iX Computer Systems Volume 10 Issue 1 Part Number 32650-90269 32650-90269 E1098 Printed in: U.S.A.
Notice The information contained in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for direct, indirect, special, incidental or consequential damages in connection with the furnishing or use of this material.
Contents HP Electronic Support Center Security-Related Services. . . . . . . . . . . 9 1. Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 MPE/iX Patches on HP Electronic Support Center . . . . . . . . . . . . . . . 18 HP Instant Information for Delivery of Learning Products . . . . . . . . 20 2. System Information and Preparation Updating to and Backdating from MPE/iX 6.0 . . . . . . . . . . . . . . . . . .
Contents 7. Interoperability and Internet Solutions Introducing 100VG-AnyLAN Network Adapter. . . . . . . . . . . . . . . . . . 86 Introducing 100Base-T Network Adapter . . . . . . . . . . . . . . . . . . . . . . 88 Introducing the REMSH Client Functionality. . . . . . . . . . . . . . . . . . . 90 Hewlett-Packard NetWorker ClientPak for MPE/iX . . . . . . . . . . . . . . 91 Introducing ODBCLink/SE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 DTS/TIO Subsystem . . . . . . . . . . .
Contents 12. Catalog of User Documentation MPE/iX 6.0 New or Updated Manuals . . . . . . . . . . . . . . . . . . . . . . . . 276 Manual Collections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 6
Tables Table 2-1. NIO/CIO Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Table 2-2. Disk Space Requirements in K Sectors for Supported Releases. . . . . . . . . . . . . . . . . . . . 28 Table 2-3. System Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Table 8-1. Supported Disk Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables 8
Obtaining Software Security Patches for your HP Computer System Hewlett-Packard would like to make you aware of a special free service provided for all customers of HP 3000 and HP 9000 computer systems. This service gives customers a direct route to Hewlett-Packard for obtaining information relating to the security of their Hewlett-Packard Computer System(s).
Remember, an HP support contract is not required to subscribe to HP Security Bulletin services. Subscribing to HP Electronic Support Center Security Bulletin Services Once you have placed your name on the subscriber list for future Security Bulletins (see instructions below), you will receive them via e-mail on the day they are issued by HP. As referenced below, you can also view a list of past Security Bulletins issued in the "HP Security Bulletins Archive".
Overview—MPE/iX Release 6.0 (C.60.00) 1 Overview—MPE/iX Release 6.0 (C.60.00) This Communicator 3000 provides general and detailed information on the new and enhanced functionality for the MPE/iX 6.0 Release (C.60.00), as well as information on release strategy and installation prerequisites. MPE/iX 6.0 will accumulate all of the functionality previously released on MPE/iX 5.5 Express releases such as Year 2000 enhancements, ODBCLink/SE—a 32-bit driver from M.B.
Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary Communicator Summary Following are brief descriptions of the articles and chapters. MPE/iX Patches on HP Electronic Support Center MPE patches are now available on HP Electronic Support Center via the Internet to all customers. For more details, refer to the article, "MPE/iX Patches Now on HP Electronic Support Center," in this chapter.
Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary • "Overview of HP Stage/iX" describes HP Stage/iX, which is an operating system facility for applying and managing MPE/iX patches on your systems. • "Transaction Manager Overview" gives an overview of System Log Expansion, Checkpoint Improvement, and Copy-Forward. • "Increase in Number of TCP Connections" explains how to configure your system to allow up to 5600 connections.
Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary • "HP ALLBASE/BRW" explains that this version of ALLBASE/BRW focuses on a TPI defect repair. • "COBOL II/iX Enhancements" describes the COBOL II/iX enhancements. • "Query/iX Enhancements" describes the enhancements made to QUERY to utilize the new B-tree index features in TurboIMAGE/XL.
Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary • "Overview of the DTS/TIO Subsystem" describes the new features of the Datacommunications and Terminal Subsystem (DTS). • "Telnet/iX Server—Full Functionality Release" describes the Telnet/iX Server enhancement on MPE/iX Release 5.5, which strengthens the HP 3000 as an open system by providing access between the HP 3000 and computers that support Telnet, such as UNIX-based systems and PCs. Describes the functionality added with Release 5.
Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary • "VPLUS Enhancements for Turn-of-Century" describes enhancements in B.06.07 version of VPLUS for the Turn-of-century enhancement. Refer to the technical article in Chapter 10 for other VPLUS enhancements. • "Predictive" announces that Predictive is year 2000 safe. • "HP MPE/iX Databases" describes the readiness of ALLBASE/SQL, IMAGE/SQL, and TurboIMAGE/XL to handle the year 2000. • "HP Stage/iX" announces that HP Stage/iX is Y2K compliant.
Overview—MPE/iX Release 6.0 (C.60.00) Communicator Summary • "CI Enhancements" describes POSIX filenames, COPY command enhancements, and new Evaluator functions. It also reviews the CI Enhancements in C.55.03. It describes the new functionality added to the CI software to improve the ease of use and overall functionality of these commands: LISTF,LISTFILE, PAUSE, PRINT, FLABELINFO and FINFO(), and INPUT. There are two new variables: HPLASTSPID and HPSPOOLID.
Overview—MPE/iX Release 6.0 (C.60.00) MPE/iX Patches on HP Electronic Support Center MPE/iX Patches on HP Electronic Support Center by Patch Support Team Commercial Systems Division MPE/iX patches for MPE/iX Release 5.0 and beyond, are available on the HP Electronic Support Center to all customers. Features and Benefits The new patch access and delivery system benefits all MPE/iX customers with: • Improved overall communication between HP and customers.
Overview—MPE/iX Release 6.0 (C.60.00) MPE/iX Patches on HP Electronic Support Center • European Web accessing address: http://europe-support.external.hp.com Electronic Digests If you want to keep yourself up-to-date on the latest development of MPE/iX patches, you can sign up for the daily Security Bulletin and weekly mpeix_patch Bulletin. Once you have subscribed to these two bulletins, you will receive these digests on a periodic basis via electronic mail.
Overview—MPE/iX Release 6.0 (C.60.00) HP Instant Information for Delivery of Learning Products HP Instant Information for Delivery of Learning Products Hewlett-Packard recently introduced HP Instant Information, a new way of delivering learning products on CD-ROM that gives you easier access to multiple HP support documents. Instant Information on CD-Rom replaces HP LaserROM as the viewing mechanism for documentation.
Overview—MPE/iX Release 6.0 (C.60.00) HP Instant Information for Delivery of Learning Products The first release of HP Instant Information for MPE/iX will include the most critical MPE/iX learning products. Books for which no revisions are planned will remain on the HP LaserROM (archive copy provided with Release MPE/iX 6.0) and will not be converted to HP Instant Information. You can subscribe to HP Instant Information through your support contact or by purchasing a stand-alone subscription.
Overview—MPE/iX Release 6.0 (C.60.
System Information and Preparation 2 System Information and Preparation This chapter includes the following articles on system information: • Updating to and Backdating from MPE/iX 6.0 • Planning Your Move to MPE/iX Release 6.0 • Upgrading a Pre-997 Corporate Business Server to a 997 • Special Note on SCSI Device Configuration for MPE/iX 6.
System Information and Preparation Updating to and Backdating from MPE/iX 6.0 Updating to and Backdating from MPE/iX 6.0 by MPE/iX System Release Team Updating to MPE/iX 6.0 To update or install MPE/iX Release 6.0, your system must already be on the MPE/iX 5.5 (C.55.xx) or the MPE/iX 5.0 General Release (C.50.xx). If your system is not on MPE/iX 5.5 or MPE/iX 5.0 General Release, you must first update your system to MPE/iX 5.0 before you can update to MPE/iX 6.0 (C.60.00).
System Information and Preparation Planning Your Move to MPE/iX Release 6.0 Planning Your Move to MPE/iX Release 6.0 by Rich Webber Commercial Systems Division This article lists requirements for installation of or updating to Release 6.0 system software. This includes requirements for adding-on subsystem purchased products (SUBSYS) and updating your system software version level, and installing your system software.
System Information and Preparation Planning Your Move to MPE/iX Release 6.0 • HP 3000 MPE/iX System Software Maintenance Manual Refer to the appropriate manuals for further information on what is required for updating to 5.0 or 5.5 including any hardware requirements. Contact your HP support representative if you need more information. Third-Party Software Compatibility Verify that any third-party software product you are running is compatible with the latest version of the operating system software.
System Information and Preparation Planning Your Move to MPE/iX Release 6.0 LDEV 1 Disk Drive Maximum Usage If you have a CIO system and you are using a disk drive with over 2 GBytes capacity as your LDEV 1, any disk space over the 2 GBytes is not available for use. It cannot and will not be used for system or user files. If you have an NIO system and you are using a disk drive with over 4 GBytes capacity as LDEV 1, any disk space over the 4 GBytes is not available for use.
System Information and Preparation Planning Your Move to MPE/iX Release 6.0 NOTE The disk space values listed in this section are estimated values only. The actual amount of disk space used on your system will vary. Non-Contiguous Disk Space Estimates The following table lists the amount of non-contiguous disk space sectors required for the three operating system components (SLT, FOS, and SUBSYS) of the currently supported versions of the operating system software.
System Information and Preparation Planning Your Move to MPE/iX Release 6.0 Estimate additional disk space requirements based on the number and kind of software subsystem products purchased. If you are not adding-on any new purchased products, the disk space sectors currently being used by your existing products will probably not change significantly.
System Information and Preparation Planning Your Move to MPE/iX Release 6.0 Reserving Disk Space The update and add-on process requires a minimum number of contiguous and non-contiguous disk space sectors. Ensure that you have enough contiguous disk space on LDEV 1 to complete your task. The total amount of non-contiguous disk space does not need be available on LDEV 1. Reserve enough contiguous and non-contiguous disk space on your system before you perform an install, update, or add-on.
System Information and Preparation Upgrading a Pre-997 Corporate Business Server to a 997 Upgrading a Pre-997 Corporate Business Server to a 997 by Hank Cureton Commercial Systems Division Introduction The I/O configuration on a 997 server has one additional hardware layer (the HP-PB I/O bus converter) compared to the earlier Corporate Business Servers (990, 991, 992, 995, and 996). As a result, the system I/O configuration on a 997 needs to be updated to reflect this additional hardware layer.
System Information and Preparation Upgrading a Pre-997 Corporate Business Server to a 997 target group is the name of the SYSGEN configuration group in the SYS account into which the "target system" configuration files will be stored. This is a required parameter. If the group does not exist, it will be created by the program. Examples: :IOCNVRT CONFIG, CONFIG This command converts a pre-997 configuration in the group CONFIG.SYS into a 997 configuration in the same group CONFIG.SYS.
System Information and Preparation Upgrading a Pre-997 Corporate Business Server to a 997 Recommended Sequence of Steps for Upgrading from a Pre-997 to a 997 The recommended order for upgrading a pre-997 Corporate Business Server (990, 991,992, 995 or 996) to a 997 server follows: 1. Update the system with C.55.05 or C.6.0. 2. Reboot the system. 3. Back up the S995 CONFIG.SYS group and the file NMCONFIG.PUB.SYS.
System Information and Preparation Special Note on SCSI Device Configuration for MPE/iX 6.0 Special Note on SCSI Device Configuration for MPE/iX 6.0 by Ruben Gallegos Commercial Systems Division Overview With the release of MPE/iX 6.0, all SCSI devices must have as part of their device configuration a pseudo device with a "transparent_mgr" that was created with SYSGEN. This requirement is for all SCSI devices on a system running MPE/iX 6.0.
System Information and Preparation Special Note on SCSI Device Configuration for MPE/iX 6.0 and MO disk drives. Not adding pseudo devices for an MO device on MPE/iX 6.0, will cause problems that could lead to the inability to access data from this device. Examples: Pre-MPE/iX 6.0 Configuration All SCSI devices, except Magneto-Optical devices should have a "transparent_mgr" configured in systems running MPE/iX versions prior to MPE/iX 6.0. This example shows the standard MPE/iX 5.
System Information and Preparation Special Note on SCSI Device Configuration for MPE/iX 6.0 ID: PMGR: LMGR: HPC1700A SCSI_AC_DM LOGICAL_DEVICE_MANAGER TYPE: AC PMGRPRI: 10 MAXIOS: 0 PATH: ID: PMGR: LMGR: 24.4 PSEUDO TRANSPARENT_MGR LDEV: TYPE: DA PMGRPRI: MAXIOS: PATH: ID: PMGR: LMGR: 24.4.0 HPC1701A SCSI_DISC_DM LOGICAL_DEVICE_MANAGER LDEV: 32 TYPE: DISC PMGRPRI: 8 MAXIOS: 0 PATH: ID: PMGR: LMGR: 24.5 PSEUDO TRANSPARENT_MGR LDEV: TYPE: DA PMGRPRI: MAXIOS: PATH: ID: PMGR: LMGR: 24.5.
System Information and Preparation Special Note on SCSI Device Configuration for MPE/iX 6.0 PATH: ID: PMGR: LMGR: 6/4.4 HP27251A CIO_SCSI_DAM LDEV: TYPE: DA PMGRPRI: MAXIOS: PATH: ID: PMGR: LMGR: 6/4.4.6 PSEUDO TRANSPARENT_MGR LDEV: TYPE: DA PMGRPRI: MAXIOS: PATH: ID: PMGR: LMGR: 6/4.4.6.
System Information and Preparation New MPE/iX Release Obsolescence Strategy New MPE/iX Release Obsolescence Strategy by Jon Cohen Commercial Systems Division The "MPE/iX Release Obsolescence Strategy" is a collection of guidelines that determines how long a particular MPE/iX Release is supported. In recent years, our Obsolescence Strategy has grown to be very complex, ambiguous, and confusing.
System Information and Preparation HP System Account and Directory Naming Structure HP System Account and Directory Naming Structure by The Release Delivery Team Commercial Systems Division Since the MPE operating system originated, Hewlett-Packard has developed and maintained a number of system accounts that are considered reserved. With the addition of POSIX, this idea is extended to include a number of Hierarchical File System (HFS) directories as well.
System Information and Preparation HP System Account and Directory Naming Structure System Directories The following directories are currently in use: Table 2-3 System Directories 40 /bin /usr/lib/terminfo/m /etc /usr/lib/terminfo/n /hpshell-examples /usr/lib/terminfo/o /hpshell-examples/lexyacc /usr/lib/terminfo/p /lib /usr/lib/terminfo/q /tmp /usr/lib/terminfo/r /usr /usr/lib/terminfo/s /usr/curses /usr/lib/terminfo/t /usr/include /usr/lib/terminfo/u /usr/include/sys /usr/lib/termin
System Management 3 System Management This chapter contains the following articles related to networking and client-server applications: • User-Defined Job Queues and ALTJOB HIPRI Enhancements • Overview of HP Patch/iX • Overview of HP Stage/iX • Transaction Manager • Increase in Number of TCP Connections • Overview of CI Enhancements • MPE/iX POSIX Installation Changes • DNS BIND/iX and Syslog/iX • Easytime/XL Bundled with MPE/XL 6.
System Management User-Defined Job Queues and ALTJOB HIPRI Enhancements User-Defined Job Queues and ALTJOB HIPRI Enhancements by Mohan Das Konanoor and Jayaram Enhancements Summary Previously MPE/iX had one job queue into which all the submitted jobs went before getting launched by the dispatcher. A few long jobs could prevent many short jobs from running. MPE/iX can now have up to 255 user-defined job queues, each having a separate limit on the number of jobs that can be run.
System Management User-Defined Job Queues and ALTJOB HIPRI Enhancements limit is increased. When a global slot becomes available, the next job is picked from among the eligible job queues (those which haven't yet reached their individual limits) using the following algorithm: • Across all job queues, the highest INPRI job is selected. In case of a tie for INPRI, the one which was introduced earliest is selected. There cannot be a tie in INTRO time.
System Management User-Defined Job Queues and ALTJOB HIPRI Enhancements The LISTJOBQ command allows the user to list all the existing job queues in the system. It displays the queue name, limit, number of jobs in the queue that are in the EXEC state and the total number jobs in the queue, (Number of jobs in the EXEC state + Number of jobs in the WAIT state). This command is not allowed in SYSSTART.
System Management User-Defined Job Queues and ALTJOB HIPRI Enhancements [;INPRI=inputpriority ;HIPRI ][;RESTART] [;OUTCLASS= [ [device] [,[outputpriority][,numcopies] ] ] ] [;TERM={termtype}] [;PRIVATE] [;SPSAVE] [;JOBQ= qname] JOB command now accepts a new parameter ;JOBQ=. Users can specify the job queue name into which a particular job should log on. If a job queue is specified in the STREAM command then it overrides the name specified in the JOB command.
System Management User-Defined Job Queues and ALTJOB HIPRI Enhancements STREAM command now accepts a new parameter ;JOBQ= User can specify the queue name into which a particular job should go. The name specified overrides the queue name specified in the JOB command. Parameters: qname is the name of the queue into which the job must log on. If no queue name is specified the default system job queue will be used.
System Management Overview of HP Patch/iX Overview of HP Patch/iX by Venugopal Commercial Systems Division Overview The MPE/iX Patch Management tool, HP Patch/iX, was introduced with PowerPatch C.50.05 based on MPE/iX General Release 5.0, and is available with the MPE/iX Release 6.0 Fundamental Operating System (FOS) software. HP Patch/iX provides a user-friendly environment for customization and installation of Hewlett-Packard supported patches on an MPE system.
System Management Overview of HP Patch/iX • PowerPatch tape • PowerPatch tape with Reactive patches • SUBSYS with a PowerPatch tape (referred to as an Express) • SUBSYS with a PowerPatch tape along with Reactive patches NOTE HP Patch/iX does not support the UPDATE of a system from one MPE release to another. A system installed with MPE/iX 5.5 cannot be UPDATEd to MPE/iX 6.0 via HP Patch/iX. The system must already be installed with MPE/iX 6.0 if patches are to be applied via Patch/iX.
System Management Overview of HP Stage/iX Overview of HP Stage/iX by Venugopal Commercial Systems Division HP Stage/iX is an operating system facility for applying and managing MPE/iX patches on your system. Using HP Stage/iX reduces system downtime and provides an easy and reliable method for backing out patches.Use HP Stage/iX to place PowerPatch and/or reactive patches into staging areas on disk while the system is up, then choose a staging area to use at boot time to apply the patches.
System Management Overview of HP Stage/iX Your operating system resides in what HP Stage/iX refers to as the Base. This is the set of files laid down by the last system installation or update (from tape). HP Stage/iX creates and manages staging areas, which are file containers on disk that hold versions of files that are different from the Base. (A staging area is actually an HFS directory which holds all the files associated with that staging area.) More than one staging area can exist at a time.
System Management Overview of HP Stage/iX STAGEMAN Utility Using the STAGEMAN utility, you can control and obtain information about your HP Stage/iX environment. Uninstalling HP Stage/iX The HP Stage/iX environment can be uninstalled any time there is no active staging area. This action deletes all staging areas and any files and directories that HP Stage/iX has built. This activity does not just turn off HP Stage/iX; it completely removes any and all files associated with the environment.
System Management Transaction Manager Transaction Manager Overview Transaction Manager (XM) is an integral part of the MPE/iX file system. It provides a facility to log all the transactions that are done on a file that is attached to XM via a system intrinsic. It ensures data integrity by protecting such files across system crashes. Three new enhancements are added to XM with 6.0 to provide improved performance and reliability.
System Management Increase in Number of TCP Connections Increase in Number of TCP Connections by Ganesh HS and Chandrashekar MN Commercial Systems Division Introduction Prior to the MPE/iX 6.0 release, TCP on MPE/iX allowed a maximum of 4096 connections. An enhancement to the TCP module allows up to 5600 connections. The version ID of TCP (NET_TCP_VERS in nmmaint,3) which supports this feature will start with B060.
System Management Increase in Number of TCP Connections After the re-configuration is validated, stop, then restart, the network to implement the increased TCP connection limit. It is not necessary to reboot the machine.Now TCP is ready to accept up to 5600 TCP connections.
System Management Overview of CI Enhancements Overview of CI Enhancements by Jeff Vance Commercial Systems Division Overview CI enhancements introduced in MPE/iX Release 6.0 are the following: • POSIX filenames support additional special characters. • COPY command was enhanced. • SHOWVAR command was enhanced. • New CI evaluator functions were added: ANYPARM(), BASENAME(), DECIMAL(), DIRNAME(), FQUALIFY(), FSYNTAX(), and XWORD(). Details for these enhancements are found in the article, "6.
System Management MPE/iX POSIX Installation Changes MPE/iX POSIX Installation Changes by Jeff Vance Commercial Systems Division MPE/iX Release 6.0 has fixed several POSIX install problems as well as adding a few POSIX enhancements. On 6.0, the System Manager should notice that: • POSIX files have the correct permissions so that all users can run the shell. • Several new symbolic links are created. • The original /etc/profile is saved. • A new file, /etc/profile.local, is defined.
System Management MPE/iX POSIX Installation Changes Of course the system manager can change the file permissions but the default is now correct. New Symbolic Links: UNIX users are accustomed to invoking FTP and other networking services and files by their common UNIX filenames. To this end, Release 6.0 has added many new symbolic links. Twelve networking related links are defined: POSIX Filename MPE Filename /bin/ftp FTP.ARPA.SYS /bin/telnet TELNET.ARPA.SYS /etc/protocols PROTOCOL.NET.
System Management MPE/iX POSIX Installation Changes Shell initialization: /etc/profile is invoked by the POSIX shell whenever the -L info string is supplied, assuming the user running the shell has execute permission to this file. /etc/profile contains global initialization for the shell; whereas, user-specific initialization is accomplished via the user's own .profile file. The main enhancement is that /etc/profile supports the execution of a custom initialization file named /etc/profile.local.
System Management MPE/iX POSIX Installation Changes • The popular "ll" alias is defined as "ls -l". • The cursor is not homed and the screen is no longer cleared. • The current working directory (CWD) is not altered (see also the SH UDC changes). The above changes in /etc/profile should make the shell more user-friendly. "SH" UDC: The HPPXUDC.PUB.SYS file contains the "SH" UDC, among other useful POSIX-related UDCs. This UDC file has been in FOS since Release 5.0 but is not cataloged by default.
System Management MPE/iX POSIX Installation Changes which is streamed during the update process. The shared library concept is familiar to MPE developers but relatively new in UNIX. The existence of shared libraries helps facilitate most modern UNIX ports.
System Management DNS BIND/iX and Syslog/iX DNS BIND/iX and Syslog/iX DNS BIND, which stands for Berkeley Internet Name Domain, is an implementation of the Domain Name System (DNS) and is the most common use of the Domain Name System (DNS). Now, the complete implementation of DNS BIND/iX runs on an MPE/iX shell operation system on MPE/iX release 6.0. Initially, DNS BIND/iX was written for UNIX; however, the latest version of DNS BIND/iX 8.1.1 runs on MPE/iX systems.
System Management Easytime/XL Bundled with MPE/iX 6.0 Easytime/XL Bundled with MPE/iX 6.0 by Gopalakrishnan & Kumaran, Commercial Systems Division Easytime/XL is a software tool that allows you to manage your system from easy-to-use screens. You will be able to perform most of the tasks for managing your system from the HP Easytime/XL screens. With this release, HP Easytime/XL is bundled with Fundamental Operating System and it is supported.
System Support Tools 4 System Support Tools This chapter contains the following articles related to MPE/iX system support tools: • Predictive Support • On-Line Diagnostic System (Sherlock) • GLANCE has a New Name and a New Home! Chapter 4 63
System Support Tools Predictive Support Predictive Support Product Overview HP Predictive Support provides hardware support and helps increase the uptime of your systems by monitoring system memory and disk/tape drives. When the HP Predictive Support software detects a potential problem, it sends a message to the HP Response Center. The Response Center portion of the system screens the data and forwards problems requiring further analysis to a Response Center Engineer.
System Support Tools Predictive Support • HPA3352A 4 GB 3.5 in. SCSI Disk • HPA3353A 4 GB 3.5 in. Fast Wide SCSI Disk • HPA3306A 2 GB 3.5 in. Fast Wide SCSI Disk • HPA3628A 9 GB 3.5 in. SCSI Disk • HPA3629A 9 GB 3.5 in.
System Support Tools On-Line Diagnostic System (Sherlock) On-Line Diagnostic System (Sherlock) by Mariano Nunez Commercial Systems Division The Sherlock diagnostic system is made up of a user interface program that provides access to the diagnostic programs, a diagnostic system monitor that provides control and logging functions, and a diagnostic system library (XL.DIAG.SYS) that provides a standard interface for all diagnostic program developers. The Sherlock system will add support for the 997 system.
System Support Tools GLANCE has a New Name and a New Home! GLANCE has a New Name and a New Home! by James Overman CSBU R&D Overview As of the MPE/iX 6.0 Release, the performance tool, HP GlancePlus/XL, has been renamed HP GlancePlus/iX. With version HPB1787B.09.06, the program file has been changed from GLANCEXL.PUB.SYS to GLANCEIX.PUB.SYS. For most users, these changes should have no impact, as the GLANCE.PUB.SYS command execute file has been changed to run the new program name.
System Support Tools GLANCE has a New Name and a New Home! 68 Chapter 4
Application Development 5 Application Development This chapter contains the following overview articles related to new applications and enhancements to existing applications: • Transact V and Transact/iX Enhancements • Dictionary /3000 • Inform/V • HP ALLBASE/BRW • COBOL II/iX Enhancements • QUERY/iX Enhancements Overview • IMAGE/SQL and TurboIMAGE/XL Overview • Features in ALLBASE/SQL Version G3 Additional technical information on many of these topics is in Chapter 10, “Technical Articles.
Application Development Transact V and Transact/iX Enhancements Transact V and Transact/iX Enhancements by Kelly Sznaider Support Technology Lab Overview Two new enhancements have been added to Transact/V as of version A.11.00 and also to Transact/iX as of version A.06.00: • Literal strings and numeric constants can now be passed as parameters in the PROC verb. • Transact now provides a method for increased decimal precision in arithmetic expressions.
Application Development Dictionary/3000 Dictionary/3000 by Kelly Sznaider Support Technology Lab Overview As of version A.03.00, Dictionary/3000 offers two new enhancements in the DICTDBM utility: • The capability of copying entities with the new COPY command. • The ability to enter elements multiple times within an HP Inform group. COPY Command for Entities For the COPY command, a category, class, element, file, group, location, or procedure is copied to a new like entity with a different name.
Application Development Inform/V Inform/V by Kelly Sznaider Support Technology Lab Inform/V has been enhanced to support the Dictionary/3000 version A.03.00 enhancements. As of Version A.11.01, Inform/V is capable of handling multiple items with the same primary name in an HP Inform group. The alias names for the same primary item must be unique. The Dictionary/3000 enhancement allows the definition of duplicate primary items in an HP Inform group within the dictionary.
Application Development HP ALLBASE/BRW HP ALLBASE/BRW by Kelly Sznaider Support Technology Lab The last few revisions of HP ALLBASE/BRW have concentrated on the integration of TurboIMAGE Third Party Indexing (TPI) with BRW. BRW version A.01.54 introduced the support of TPI. In BRW version A.01.55, more TPI enhancements were provided, as well as several defect repairs. In the latest version of BRW, A.01.56, the main focus is a TPI defect repair. This version of HP ALLBASE/BRW, A.01.
Application Development COBOL II/iX Enhancements COBOL II/iX Enhancements by Walter Murray Support Technology Lab Overview COBOL II/iX on MPE/iX 6.0 provides several enhancements that were requested by Interex SIGCOBOL. Some of these enhancements have already been made available in various patches to MPE/iX 5.5. This article gives an overview. For details, refer to "COBOL II/iX Enhancements" in chapter 10, "Technical Articles." 1.
Application Development QUERY/iX Enhancements Overview QUERY/iX Enhancements Overview by James Overman SSG Group R&D Overview The following are the new enhancements for QUERY/iX: • B-Tree Enhancement • Dynamic Dataset Capacities • Wildcard Retrievals • Wildcard Character Limitations • B-Tree Limitations • "NO MATCH" Enhancement With the HP32216D.03.11 and N.03.11 releases of QUERY, the new B-Tree access capabilities will be supported within QUERY on systems with the B-Tree software release.
Application Development QUERY/iX Enhancements Overview The FIND, MULTIFIND, and SUBSET commands have been enhanced to accept a NO MATCH alternative such that all data records NOT MATCHING the pattern provided are returned by the commands. For more information, refer to "QUERY/iX Enhancements" in chapter 10, "Technical Articles.
Application Development IMAGE/SQL and TurboIMAGE/XL Overview IMAGE/SQL and TurboIMAGE/XL Overview by Bharati Desai Commercial Systems Division Overview This is an overview of the enhancements to IMAGE/SQL and TurboIMAGE/XL that have been implemented since the release MPE/iX 5.5 (C.55.00).
Application Development IMAGE/SQL and TurboIMAGE/XL Overview STATISTICS command of ISQL for each of the tables you access frequently. If you have created SQL data using an earlier release of IMAGE/SQL, perform the ALLBASE/SQL migration to migrate your DBEnvironment to the current G3 format. For more information, refer to the ALLBASE/SQL Database Administration Guide.
Application Development Features in ALLBASE/SQL Version G3 Features in ALLBASE/SQL Version G3 by Doug Myers Database Lab, Commercial System Division Overview This is an overview of the features of ALLBASE/SQL version G3 on MPE/iX 6.0 release (C.60.
Application Development Features in ALLBASE/SQL Version G3 themselves. This is an important capability for those needing to move modules from a development DBEnvironment to a production DBEnvironment. Year 2000 Compatibility ALLBASE/SQL has always stored dates in a four-digit year format which largely eliminates the year 2000 compatibility problem. ALLBASE/SQL applications can be coded using four-digit year dates.
Data/Application Integration 6 Data/Application Integration This chapter contains the following article related to Data/Application Integration: • DCS RPC Clients for FOS through MPE/iX Chapter 6 81
Data/Application Integration DCE RPC Clients for FOS through MPE/iX DCE RPC Clients for FOS through MPE/iX by Sridhar Murthy T.R. Commercial Systems Division Overview For the MPE/iX 6.0 release and later, the DCE RPC Client (Version A.01.12) modules, will be included in the FOS. These DCE RPC modules are based on OSF DCE 1.0.2. These changes will support customers who were continuing to be dependent on NCS. NCS has been obsoleted from 6.0 release.
Data/Application Integration DCE RPC Clients for FOS through MPE/iX These commands will execute the script /usr/bin/rpcd which will invoke the command file 'RPCD.PUB.SYS'. The customer needs to run his applications as: :Run foo;xl="dcexl.hpdce.sys othdxl.threads.sys" OR Link this program as follows: :linkedit altprog foo.pub.sys;xl='dcexl.hpdce.sys,othdxl.threads.sys' Then run foo as a executable.
Data/Application Integration DCE RPC Clients for FOS through MPE/iX 84 Chapter 6
Interoperability and Internet Solutions 7 Interoperability and Internet Solutions This chapter contains the following articles on Interoperability and Internet solutions: • Introducing 100VG-AnyLAN Network Adapter • Introducing 100Base-T Network Adapter • Introducing the REMSH Client functionality • Hewlett-Packard NetWorker ClientPak for MPE/iX • Introducing ODBCLink/SE • DTS/TIO Subsystem • Telnet/iX Server--Full Functionality Release • FTP Enhancements • Samba/iX Overview • Introducing Java/iX Chapter
Interoperability and Internet Solutions Introducing 100VG-AnyLAN Network Adapter Introducing 100VG-AnyLAN Network Adapter by Randy Pawell Commercial Systems Division Overview 100VG-AnyLAN Network Adapter (B5426AA) is a high-speed network link providing HP 3000 Series 900 systems that have HP-PB (HP Precision Bus, also known as NIO) backplanes, with a connection to a 100VG local area network.
Interoperability and Internet Solutions Introducing 100VG-AnyLAN Network Adapter • Provides two traffic priorities: normal and demand. • Provides 100 Mb high-speed connectivity over CAT-5 or CAT-3 voice-grade unshielded twisted pair (UTP), RJ-45 terminated cabling. • Provides 10 Mb low-speed connectivity compatible with existing 10Base-T UTP networks. • Supports a maximum cable length of 100 meters in 100 Mb mode.
Interoperability and Internet Solutions Introducing 100Base-T Network Adapter Introducing 100Base-T Network Adapter by Randy Pawell Commercial Systems Division Overview 100Base-T Network Adapter (B5427AA) is a high-speed network link providing HP3000 Series 900 systems that have HP-PB (HP Precision Bus, also known as NIO) backplanes, with a connection to a 100Base-TX local area network.
Interoperability and Internet Solutions Introducing 100Base-T Network Adapter • Provides 10 Mb low-speed connectivity compatible with existing 10Base-T UTP networks, also with CAT-5 cabling. • Supports a maximum cable length of 100 meters in 100 Mb mode.
Interoperability and Internet Solutions Introducing the REMSH Client Functionality Introducing the REMSH Client Functionality by Cas Caswell Commercial Systems Division Overview Remsh allows a user to connect to the remote system and execute a command on that remote system. Output from the remote command is sent to remsh's standard output so the user can see the results of their command. Remsh is the same service as rsh on BSD Unix systems.
Interoperability and Internet Solutions Hewlett-Packard NetWorker ClientPak for MPE/iX Hewlett-Packard NetWorker ClientPak for MPE/iX by Lalitha Pejavar and Alex Early Commercial Systems Division Overview Available now for HP 3000 users is NetWorker from Legato, a client/server application that provides advanced storage management capabilities to a heterogeneous environment of servers and desktop computers.
Interoperability and Internet Solutions Hewlett-Packard NetWorker ClientPak for MPE/iX • Provides an easy-to-operate graphical user interface and maintains a file index and media index to track data backed up and recovered. • Supports a wide range of industry tape (DAT) and DLT libraries and furnishes a sophisticated media manager which allows for unattended backup and restore using autochange library.
Interoperability and Internet Solutions Hewlett-Packard NetWorker ClientPak for MPE/iX Legato NetWorker is the only third-party storage management solution supported by HP Worldwide Customer Support Operations. HP Response Center engineers have been fully trained on NetWorker server operations. HP support contracts are available for NetWorker from your HP sales representative.
Interoperability and Internet Solutions Introducing ODBCLink/SE Introducing ODBCLink/SE by Dawna Whitehead M. B. Foster Associates Limited Overview ODBCLink/SE is a replacement for HP PC/API. It is an implementation of Microsoft's Open Database Connectivity (ODBC) interface that enables Microsoft Windows based applications and tools to access IMAGE/SQL on the HP 3000 and ALLBASE/SQL on the HP 3000 and HP 9000, in a client/server environment. ODBCLink/SE is a part of IMAGE/SQL and ALLBASE/SQL.
Interoperability and Internet Solutions Introducing ODBCLink/SE Utilities are provided with ODBCLink/SE to verify that the driver is functioning correctly and to delete unwanted drivers or translation DLL's. For more detailed information, refer to "Introducing ODBCLink/SE" in Chapter 10, "Technical Articles.
Interoperability and Internet Solutions DTS/TIO Subsystem DTS/TIO Subsystem by Wendy Cheng Commercial Systems Division Overview The Datacommunications and Terminal Subsystem (DTS) consists of host (HP 3000) based software and the DTC (Datacommunications and Terminal Controller) terminal server. The DTC family of products supports X.25 communication and Telnet access to HP 3000 systems, and TCP/IP communication to HP 9000 and non-HP systems.
Interoperability and Internet Solutions DTS/TIO Subsystem • Port configuration parameters (data length and parity) can be specified as forced when binary mode is selected. • Dynamic Configuration of new port configuration parameters. For more information refer to "New Features for DTS/TIO Subsystems" in Chapter 10, "Technical Articles," and to the manual, Configuring System for Terminals, Printers, and Other Serial Devices.
Interoperability and Internet Solutions Telnet/iX Server—Full Functionality Release Telnet/iX Server—Full Functionality Release by Cas Caswell Commercial Systems Division The version of the Telnet/iX Server released with MPE/iX Release 5.5 had several functionality restrictions that were documented in the MPE/iX 5.5 Communicator article, "Telnet/iX Server Functionality Details." The Telnet/iX Server included with this MPE/iX release is now fully functional.
Interoperability and Internet Solutions Telnet/iX Server—Full Functionality Release 1. Line mode for the HP 3000 server was implemented to be consistent with the HPUX 9.0 Telnet product. Neither of these line modes comply with the RFC-1116 line mode standard. 2. We recommend that you do not use line mode when running block mode applications on the HP 3000. This may cause the applications to operate poorly.
Interoperability and Internet Solutions FTP Enhancements FTP Enhancements by Raghuram B. Commercial Systems Division The following is an overview of new features available with FTP/iX. Implementation of FTPSRVR under INETD Until now, FTP/iX server service, FTPSRVR, was initiated by the FTPMON process which was started by the JFTPSTRT.ARPA.SYS job. The INETD/iX process will now replace the FTPMON process and the JFTPSTRT.ARPA.SYS job will be replaced by JINETD.NET.SYS job.
Interoperability and Internet Solutions FTP Enhancements MOVE Option This FTP/iX user-controller option allows the user to selectively specify on the GET, PUT, MGET, or MPUT command whether to delete the source file after confirmation of a successful file transfer to the target system. Details and example of these options for FTP/iX are provided in the “Technical Articles” chapter of this book.
Interoperability and Internet Solutions Samba/iX Overview Samba/iX Overview by Wendy Cheng Commercial Systems Division Overview Samba/iX is a suite of programs which work together to allow clients to access a server's file space and printers via the Server Message Block (SMB) protocol. Samba is the SMB file server that runs on MPE/iX release 6.0.
Interoperability and Internet Solutions Introducing Java/iX Introducing Java/iX by Mike Yawn Overview MPE/iX 6.0 is the first MPE release to provide a bundled version of Java. Java is a platform-independent language and runtime environment with a wealth of information available.
Interoperability and Internet Solutions Introducing Java/iX version of Java/iX The AWT comprises the Java packages in the java.awt hierarchy. These interfaces are unsupported on the current release and will likely not be a part of future Java/iX releases.
Peripherals 8 Peripherals This chapter contains the following articles on peripherals: • 9 GB Disk Drive • New Disk Devices Supported • High Availability Disk Array (Nike) • A3716A 144 GB DDS-3 Autoloader for MPE/iX • EMC Symmetrix Disk Arrays Chapter 8 105
Peripherals 9 GB Disk Drive 9 GB Disk Drive by Alex Early Commercial Systems Division Overview The 9 Gigabyte (GB) disk drive has been available since March 1997 as an embedded disk and as of April 1997 in the mass storage enclosure on the HP 3000 computer systems. Due to the performance of these disks, there are special requirements for their use on MPE/iX HP 3000 computer systems. Before installing this disk drive, consider the following: 1.
Peripherals New Disk Devices Supported New Disk Devices Supported by Rakesh Saha and Sam Boles Commercial Systems Division Overview The HP 3000 supports the following disk devices on MPE/iX 6.0.
Peripherals New Disk Devices Supported Product ID New Disk Device Supported C6396A C6397A ST39173WC (9 GB DF) A5238A ST39173WC (9 GB DF) DGHS09Y (9 GB DF) A4909A ST118273WC (18 GB DF), A5239A ST118273WC (18 GB DF) Ambiguous Product ID In the continuing effort to provide the price-performance advantage of the latest disk technology and, at the same, timeprotect existing customer investment, HP uses the same disk mechanism for both Single-Ended and Differential disks.
Peripherals New Disk Devices Supported Table 8-3 Product ID for Configuring Disk Drives Product ID Product ID for Corresponding Device Adapter Drive Cap.
Peripherals High Availability Disk Array (Nike) High Availability Disk Array (Nike) With MPE/iX 6.0 there is support for 9 GB and 18 GB disk drives. Please note the following restrictions. 1. The 9 GB and 18 GB drives are supported as RAID 1 only (that is, NOT as RAID 5, since this would exceed the 18 GB volume limit currently in effect.) 2. The 9 GB and 18 GB drives may not be used as the boot device; however, that is not recommended.
Peripherals High Availability Disk Array (Nike) The following table shows the product numbers and descriptions of available disk drives. Table 8-5 Product Numbers and Descriptions for Disk Drives HP Product Number Description A3549A A3550A A3550AZ #341 5 ea 9.1 GB DD A3549A A3550A A3550AZ #342 10 ea 9.1 GB DD A3549A A3550A A3550AZ #343 15 ea 9.1 GB DD A3549A A3550A A3550AZ #344 20 ea 9.1 GB DD A3549A A3550A A3550AZ #351 5 ea 18.2 GB HH DD A3549A A3550A A3550AZ #352 10 ea 18.
Peripherals High Availability Disk Array (Nike) HP Product Number A3549A A3550A A3550AZ #364 Description 20 ea 4 GB LP DD A5132A 9.1 GB single disk A5132AM 9.1 GB multi-pack disk A5133A 18.2 GB single disk A5133AM 18.
Peripherals A3716A 144 GB DDS-3 Autoloader for MPE/iX A3716A 144 GB DDS-3 Autoloader for MPE/iX by Aida Silva Commercial Systems Division Product Overview The A3716A is a high-speed high-capacity tape product combined with an autoloader. The tape drive conforms to the DDS-3 standard. The autoloader houses six cartridges in the magazine. DDS-3 tape allows 12 GB of uncompressed data to be stored on 125m DDS-3 Tapes. It ensures backward compatibility in reading and writing existing DDS tapes.
Peripherals A3716A 144 GB DDS-3 Autoloader for MPE/iX Verify the configuration using the LDEV and LP commands as shown in the following example: Figure 8-1 io>ldev 31 LDEV: 31 DEVNAME: ID: HPC1557A PATH: 52.3.0 CLASS: TAPE OUTDEV: 0 RSIZE: 128 MPETYPE: 24 io>lp 52.3.0 PATH: 52.3.0 ID: HPC1557A PMGR: SCSI_TAPE_DM LMGR: LOGICAL_DEVICE_MANAGER LDEV: 31 TYPE: TAPE PMGRPRI: 10 MAXIOS: 0 MODE: DEVTYPE: TAPE MPESUBTYPE: 7 io>lp 52.3 PATH: 52.
Peripherals EMC Symmetrix Disk Arrays EMC Symmetrix Disk Arrays The new SYM4 version of the EMC Symmetrix Disk Array is supported on MPE/iX 5.5 starting with Express 3. The SYM4 has the CUDA-9 9 GB disk mechanism that spins at 7200 rpm, a 20 MBs fast-wide differential bus to replace the 5MBs back-end single-ended bus, larger integrated cache, and other features to boost capacity and performance. NOTE This is NOT an HP or customer installable device.
Peripherals EMC Symmetrix Disk Arrays 116 Chapter 8
Year 2000 Enhancements 9 Year 2000 Enhancements This chapter contains the following articles related to the enhancements for the compliance for Year 2000 readiness.
Year 2000 Enhancements Year 2000 Web Page Year 2000 Web Page For up-to-date information on the state of year 2000 readiness for specific HP products, refer to the web page, "HP Cure2000 Solution," at the following URL: http://www.hp.
Year 2000 Enhancements Year 2000 Enhancements for MPE/iX Year 2000 Enhancements for MPE/iX by M Gopalakrishnan Commercial System Division Overview This version of MPE/iX provides enhancements to the operating system for the year 2000 and beyond. The enhancements include the enhancements to the operating system commands, utilities, VPLUS and databases. This article explains the enhancements. Background The year 2000 issues stem from the ability to handle correctly the year 2000 and beyond.
Year 2000 Enhancements Year 2000 Enhancements for MPE/iX CALENDAR Intrinsic The CALENDAR intrinsic returns the CALENDAR date, including the day of year and the year of century. The existing CALENDAR intrinsic documentation refers to the year as "year of century." This should be interpreted as "year since 1900." The new definition of the CALENDAR intrinsic is as follows: Syntax U16 date:=CALENDAR; where date is a 16-bit unsigned integer (assigned functional return).
Year 2000 Enhancements Year 2000 Enhancements for MPE/iX Commands The following commands are enhanced to support both two- and four-digit years. For an interpretation of two-digit years, refer to the section, "Two-Digit Years Interpretation." New syntax for the commands with parameters accepting years follows: • STREAM command :STREAM jobname;DATE=datespec where datespec is the date for streaming the job in the format mm/dd/[yy]yy. If omitted, the current date is used.
Year 2000 Enhancements Year 2000 Enhancements for MPE/iX HPYYYY is a global variable used by the CI that shows the current year; the initial value is the year at logon. Type= R I For example, for year 2000, HPYYYY will have 2000. HPSPLITYEAR is a global variable used by the CI that shows the current century split year; the initial value is 50. Type=W I This variable is used in the new date intrinsics to manipulate dates in various formats.
Year 2000 Enhancements New Date Intrinsics for MPE/iX New Date Intrinsics for MPE/iX by M Gopalakrishnan Commercial Systems Division This release of the MPE/iX operating system has enhanced intrinsics for handling date formats. These intrinsics are targeted to support widely used existing date formats in MPE/iX and three new date formats. The date intrinsics are broadly categorized as follows: • HPDATECONVERT—Converting dates from one supported format to another.
Year 2000 Enhancements New Date Intrinsics for MPE/iX Table 9-2 Existing Date Formats Storage Type # Bytes longint a 8 Explanation Microseconds since 1970-01-01 Sortable ? Y2K Ready? yes yes yes yes yes yes yes yes yes yes (MPE time-stamp) integer 4 Upper 2 bytes: year next byte: month of year bottom byte: day of month integer 4 Upper 2 bytes: year bottom 2 bytes: day of year integer 4 Seconds since 1970-01-01 (POSIX.
Year 2000 Enhancements New Date Intrinsics for MPE/iX New Date Formats Three new date formats are listed in the table, “HP Standard Formats.” The first format is an integer representation of the ISO 8601 date format. The second is an ASCII representation of the same. The last date format is an extension of the existing 16-bit CALENDAR date format to a 32-bit format. These date formats will be referred to as “HP Standard Formats.
Year 2000 Enhancements New Date Intrinsics for MPE/iX Table 9-4 Supported Date Formats Date Type Code Storage Type # Bytes 1 longint 8 Explanation MPE time-stamp Sortable ? Y2K Ready? yes yes yes yes yes yes yes yes yes yes yes yes (microseconds since 1970-01-01) 2 integer 4 Upper 2 bytes: year next byte: month of year bottom byte: day of month 3 integer 4 Upper 2 bytes: year bottom 2 bytes: day of year 4 integer 4 Upper 23 bits: #years since 1900 bottom 9 bits: day of the
Year 2000 Enhancements New Date Intrinsics for MPE/iX Special Date Values Special date values to represent UNKNOWN, INVALID, NEVER, NEEDED, EXPIRED, and ILLEGAL dates are defined for dates in “HP standard formats.” The following table captures this date value information. The other date formats have been in existence for some time and hence the special date values are not defined for them. These special dates, when passed to the HPDATEFORMAT intrinsic, will result in a corresponding output string.
Year 2000 Enhancements New Date Intrinsics for MPE/iX HPDATECONVERT This intrinsic converts the dates from one supported format to another. Syntax I32V * I32V * I32 I32V HPDATECONVERT(inputcode,inputdate,outputcode,outputdate,status,cutoff) Parameters inputcode is a 32-bit signed integer by value. The value should be one of the date type codes listed in the table, “Supported Date Formats.” inputdate varies for type by reference. The interpretation depends upon the value of inputcode.
Year 2000 Enhancements New Date Intrinsics for MPE/iX HPDATEFORMAT You can use this routine to format the dates that can be combinations of display formats as explained below. Many of these elements are taken from ALLBASE/SQL date formats. You can convert dates in the “Supported Date Formats” to a display string of your choice (with restrictions). The HPDATEFORMAT intrinsic will accept these format strings.
Year 2000 Enhancements New Date Intrinsics for MPE/iX Table 9-7 Valid Characters for Punctuation - Hyphen / Slash . Dot Blank , Comma Null (or no delimiter) Thus, YYYY.MON.DAY, YY/MM/DD, DDMONYY, and DD-ZMM-YYYY are valid date formats. For example, “31 Jan 1997” when formatted through DD-ZMM-YYYY results in “31-1-1997,” formatted through YYYY.MON.DAY results in “1997.JAN.FRI,” while YYYYMMDD results in “19970131.
Year 2000 Enhancements New Date Intrinsics for MPE/iX If an invalid date is passed, on return from the intrinsic its contents will be UNKNOWN. For the “HP Standard Formats,” if special values in the table, “Special Date Values,” are passed for date parameter, on return from the intrinsic, the value of the string will be appropriately initialized.
Year 2000 Enhancements New Date Intrinsics for MPE/iX Parameters datecode is a 32-bit signed integer by value. This value should be one of the date type codes listed in the table, “Supported Date Formats.” firstdate is the first input date. The interpretation depends upon the value of datecode. See the table, “Supported Date Formats,” for the supported datecodes and their layouts. seconddate is the second input date. The interpretation depends upon the value of datecode.
Year 2000 Enhancements New Date Intrinsics for MPE/iX The number of days to be added to the input date. A negative value will result in a subtraction. outputdate is the output date. The result of the date offset operation. The interpretation depends upon the value of datecode. See the table, “Supported Date Formats,” for the supported datecodes and their layouts. status is the HPE_STATUS parameter through which the error codes are returned. A value of 0 indicates no error and no warnings.
Year 2000 Enhancements New Date Intrinsics for MPE/iX HPCALENDAR The new HPCALENDAR intrinsic returns the date in the supported date type code 4 listed in the table, “Supported Date Formats.” (This is also a HP standard format.) Syntax I32 date := HPCALENDAR ; where date is the 32-bit unsigned integer (assigned functional return).
Year 2000 Enhancements New Date Intrinsics for MPE/iX Pascal Example of New Date Intrinsics. $standard_level 'hp_modcal'$ Program dateintr(input,output); {Constants for the different date types.
Year 2000 Enhancements New Date Intrinsics for MPE/iX writeln('HPDATECONVERT intrinsic returned error',status); {Convert 'date1' to the YYYYMMDD integer format. With 50} {as the cutoff year. } outtype := hp_dt_int_yyyymmdd_fmt; HPDATECONVERT(inptype,date1,outtype,date1_18,status,cutoff); if( status <> 0) then writeln('HPDATECONVERT intrinsic returned error',status); {Convert the 'date2_pac' to a YYMMDD integer format.} {Default cutoff is assumed (i.e.
Year 2000 Enhancements New Date Intrinsics for MPE/iX COBOL Example of HPDATECONVERT. IDENTIFICATION DIVISION. PROGRAM-ID. DATEINTR. REMARKS. SAMPLE PROGRAM USING DATE INTRINSICS DATA DIVISION. WORKING-STORAGE SECTION. *Date code for YYMMDD is 25, for YYYYMMDD is 38 01 INDATE-CODE PIC S9(9) VALUE 25. 01 OUTDATE-CODE PIC S9(9) VALUE 38. 01 SPLITYEAR PIC S9(9) VALUE 70. 01 OUTDATE-YYYYMMDD PIC X(8) VALUE SPACES. 01 INDATE-YYMMDD PIC X(6) VALUE SPACES. 01 STATUS-VAR. 05 S-INFO PIC S9(4) COMP VALUE 0.
Year 2000 Enhancements VPLUS Enhancements for Turn-of-Century VPLUS Enhancements for Turn-of-Century VPLUS version B.06.07 (and later) contains enhancements to handle the year 2000 and beyond in applications. For more detailed information including syntax and parameters, refer to the article, "Year 2000 and Other Enhancements in VPLUS," in the chapter, "Technical Articles." Turn-of-century Enhancement VPLUS version B.06.07 contains enhancements to handle Year 2000 and beyond in applications.
Year 2000 Enhancements VPLUS Enhancements for Turn-of-Century Date output will be formatted with 4-digit years if the target field is wide enough to receive the date, and the user requests this action. Examples of such output include the SET statement in FORMSPEC. The target field should be at least 10 characters in length to have a 4-digit year output. VPLUS, by default, will format date output with 2-digit years.
Year 2000 Enhancements Other Products Other Products Predictive Hardware predictive (HP50779) has been modified to be year 2000 safe by modifications to internal date comparison routines and database access methods. Various other defect fixes which have been made since the release of MPE release 5.5 are also rolled into the 6.0 version of hardware predictive. HP MPE/iX Databases ALLBASE/SQL The ALLBASE/SQL functions TO_DATE and TO_DATETIME are enhanced to handle two-digit years appropriately.
Year 2000 Enhancements Documentation Changes for MPE/iX Languages Documentation Changes for MPE/iX Languages by Allan Hertling SSG Group R&D FORTRAN 77/iX Please make the following corrections to the FORTRAN 77/iX Reference Manual. This manual incorrectly states that a four-digit calendar year may be computed by adding 1900 to the YEAR parameter resulting from a IDATE subroutine call. As the year parameter is always in the range of 0 to 99, that calculation will not be correct after 1999.
Year 2000 Enhancements Documentation Changes for MPE/iX Languages BASIC Please make the following corrections to the BASIC INTERPRETER Reference Manual. The TIM function documentation on page E-3 should be changed as follows: For x >= 3, change “current year (0-99)” to “years since 1900”.
Year 2000 Enhancements Documentation Changes for MPE/iX Languages Table 9-9 DATE Field Descriptions Field Name *DATE *YEAR NOTE Contents Current date with 4-digit year Current 4-digit year Unedited Example Edited Example 10111988 10/11/1988 October 11, 1988 (Domestic Format) 11101988 11/10/1988 October 11, 1998 (United Kingdom Format) 11101988 11.10.
Year 2000 Enhancements RPG/iX 4-Digit Year Enhancement RPG/iX 4-Digit Year Enhancement by Sue Meloy Software and Services Group *DATE and *YEAR RPG/iX version A.00.18 contains support for new predefined fields that return a 4-digit year. *DATE is analogous to UDATE, except that the year is 4 digits instead of 2 digits. In the same way, *YEAR is analogous to UYEAR. RPGUDATE The RPGUDATE file format has also been changed to allow a 4-digit year.
Technical Articles 10 Technical Articles This chapter contains the following articles with additional technical information: • QUERY/iX Enhancements • COBOL II/iX Enhancements • IMAGE/SQL with TurboIMAGE/XL Enhancements • New Features in ALLBASE/SQL Version G3 • Year 2000 and Other Enhancements in VPLUS • CI Enhancements • The REMSH Client Functionality • Transaction Manager • New Features for DTS/TIO Subsystem • Introducing ODBCLink/SE • Introducing Samba/iX • Developer’s Kit for Java/iX • Hewlett-Packar
Technical Articles QUERY/iX Enhancements QUERY/iX Enhancements by James Overman SSG Group R&D Overview The following topics in this article review the new enhancements for QUERY/iX and some limitations on their use: • B-Tree Enhancement • Dynamic Dataset Capacities • Wildcard Retrievals • Wildcard Character Limitations • B-Tree Limitations • "NO MATCH" Enhancement B-Tree Enhancement The latest B-Tree enhancement to TurboImage/XL has required some enhancements to the QUERY product to utilize the new featu
Technical Articles QUERY/iX Enhancements Figure 10-1 FORM Example >FORM DATA BASE: TOYDB MON, MAY 30, 1997, 10:48 AM DATA BASE LANGUAGE ATTRIBUTE: NATIVE-3000 DATA BASE HAS 2 INDEXED SETS WITH WILDCARD CHARACTER= "~" NEW WARNING! DATA BASE BTREEMODE1 IS OFF. WILDCARD DISABLED.
Technical Articles QUERY/iX Enhancements Wildcard Character Limitations Certain possible wildcard characters are used by QUERY for syntax scanning and are limited in their usage. These special characters may be utilized when the data values are delimited by double quotes (for example, tilde, carat, comma, and parenthesis). Figure 10-2 >FIND CUSTOMERS.CUSTOMER-NO=01540~ Tilde is a limited wildcard EXPECTED A CONNECTOR OR 'END' INVALID CONNECTOR OR TERMINATOR! >FIND CUSTOMERS.
Technical Articles QUERY/iX Enhancements "NO MATCH" Enhancement The FIND, MULTIFIND, and SUBSET commands have been enhanced to accept a NO MATCH alternative such that all data records NOT MATCHING the pattern provided are returned by the commands. The new form of the FIND command is: FIND [#LIMIT=I;] RELATION/ITEM IDENTIFIER [NO] M[ATCHING] "PATTERN" [AND/OR RELATION/ITEM IDENTIFIER [NO] M[ATCHING] "PATTERN"]... [END] The MULTIFIND and SUBSET command syntax are similarly enhanced.
Technical Articles COBOL II/iX Enhancements COBOL II/iX Enhancements by Walter Murray Support Technology Lab Overview This release of COBOL II/iX on MPE/iX 6.0 provides several enhancements that were requested by Interex SIGCOBOL. Some of these enhancements have already been made available in various patches to MPE/iX 5.5. Secondary Entry Points COBOL II/iX now supports secondary entry points in a main program.
Technical Articles COBOL II/iX Enhancements CALL by plabel This enhancement provides an alternate way to achieve execution-time binding with the CALL statement. In standard COBOL, the CALL statement can use an identifier that specifies a nonnumeric data item containing the name of the desired subprogram. COBOL II/iX generates a call to the HPGETPROCPLABEL intrinsic to dynamically load the specified procedure, and that procedure is then executed.
Technical Articles COBOL II/iX Enhancements • HP_BYTE_UNPACK • HP_BYTE_PACK These procedures reside in the COBOL II run-time library in XL.PUB.SYS, but may be called from any program running in Native Mode. The routines HP_BYTE_AND, HP_BYTE_OR, and HP_BYTE_XOR perform bitwise AND, bitwise inclusive OR, and bitwise exclusive OR. The two operands and the result may be any length, but must be the same length, and must be an integral number of bytes. The three routines have identical calling sequences.
Technical Articles COBOL II/iX Enhancements The routine HP_BYTE_PACK is similar. The first parameter, the operand, is a sequence of ASCII bytes. Each byte of the operand is converted to a bit in the result, left to right. An ASCII "0" becomes a "zero" bit; anything other than an ASCII "0" becomes a "one" bit. The length specified is the length of the result in bytes. The byte length of the operand must be 8 times the byte length of the result. Example 01 BYTE-STRING PIC X(16). 01 RESULT-N PIC S9(4) COMP. .
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements IMAGE/SQL with TurboIMAGE/XL Enhancements by IMAGE/SQL Team Commercial Systems Division Overview This article discusses enhancements as well as other important information commencing with the Express 3 release of MPE/iX 5.5. Express 3 (and later releases) also includes the revised editions of some selected manuals. Highlights Highlights of this release of IMAGE/SQL, version B.G3.00 or later, and TurboIMAGE/XL, version C.07.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements • ALLBASE/SQL Performance and Monitoring Guidelines • ISQL Reference Manual for ALLBASE/SQL and IMAGE/SQL • ODBCLink/SE Reference Manual Updating IMAGE/SQL If you are updating from an earlier release of IMAGE/SQL and you have databases which are already ATTACHed to one or more DBEnvironments, you must DETACH and ATTACH again in order to benefit from the enhancements.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements TurboIMAGE/XL Enhancements The following are TurboIMAGE/XL enhancements, independent of SQL access: • Dynamic data set expansion for masters (MDX or DDXM) • 80 GB data sets • Performance Enhancement for databases with third-party indices • DBSCHEMA and P type with odd sub-item length • B-Tree indices • Scalability for DBPUT, DBDELETE, and DBUPDATE (CIU on) Dynamic Data Set Expansion for Masters Dynamic data set expansion feature for non-jumbo (f
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements anticipated growth, and synonym chain lengths. It should be such that a minimum number of expansions are necessitated. The initial capacity must be between 1 and 231 −1 inclusive but must be less than or equal to the maximum capacity.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Following the first expansion, the master data set can be perceived as having two areas, original area and expanded area, managed differently. The original area is managed in the same way as in releases prior to MDX, that is, the primary address for the new entry is calculated using the hashing algorithm and the secondary address is assigned according to the availability of the free entry, but with modifications in searching for a free entry.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements When there is no room in the expanded area and cannot be expanded further, however, there is room in the original area based on the free entry count, the original area is scanned once again (long search) to find a secondary address for the new entry. If a free entry is found, the new entry resides there, and it becomes the last entry in the synonym chain. Otherwise, the set is full and DBPUT will fail. 3.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Element Contents 6 High-water mark (0 for non-expanded masters) 7 Expansion threshold: -1 ... 2 billion blocks -1 this value means expansion not triggered by traversing 3 blocks without success, or it is a non-expandable set. 8…16 Reserved; 0 is returned DBINFO mode 208 returns information about internals which will be meaningful to only a few customers. • DBUTIL SHOW database ALL command shows the presence of MDX.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Performance Enhancement for Databases with Third-party Indices (TPI) TurboIMAGE/XL intrinsics DBGET and DBFIND are enhanced for improved performance in the following circumstances when the database is enabled for TPI: • DBFIND and DBGET when the set does not have TPI and the trace facility, if applicable, is turned off.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Key Features of B-Tree Indices Following are key features of B-Tree indices: 1. B-Tree index can be created only on the key item of the master data set. 2. B-Tree searches using the search items of all of its corresponding detail paths can be done. 3. You may create B-Tree indices for zero, one, or more master data sets. 4. DBSCHEMA has a new option, INDEXED, for the SET specification.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements • CREATE, ERASE, PURGE, SECURE, RELEASE, and SHOW commands include B-Tree index files in their operation. • The MOVE command does not allow moving the index file. 6. DBCONTROL has these modes pertaining to B-Tree indices: 13 is for B-Tree index file control. That is, to ADD, DROP, REBUILD, ATTACH, or DETACH a B-Tree index file. This mode requires PRIVILEGED mode, and hence, must be used carefully as improper use may damage your system.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements 10 allows you to simulate DBFIND mode 1 as if there were no B-Tree index. This is the same as TPI mode 10. Requires the classic mode 1 argument format. 21 is the same as B-Tree index search using DBFIND mode 1, except it is a faster version and does not return accurate chain counts. Requires the classic mode 1 argument format.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements :Run DBUTIL.PUB.SYS >SET database name [/maintword] BTREEMODE1=ON If your database is new, you will need to add data. You are now ready to perform B-Tree index searches. You can include the wildcard character in your DBFIND argument and observe the results. Scalability Prior to this enhancement, the modification intrinsics, DBPUT, DBDELETE, and DBUPDATE (Critical Item Update feature ON) were serialized for the database.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Dynamic Detail Dataset Expansion (DDX) Fix (SR# 5003-367607) The DDX feature of TurboIMAGE/XL has a known problem which may cause you to lose some of your new data entries added following the dynamic detail dataset expansion. This defect has been in the feature since its introduction, but has surfaced recently and has been reported by a few customers. The problem has been fixed both for MPE/iX 5.5 and MPE/iX 6.0. The patch ID for MPE/iX 6.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements How to tell if you already have this problem. If you use DDX, check each detail data set enabled for DDX. Remember, the problem is associated only with the detail data sets which have undergone dynamic expansion. You can check for this condition as follows: 1. Use the FORM SETS command of QUERY, which gives the Current Capacity (CC) and Blocking Factor (BF) of each data set. :query HP32216D.03.11 QUERY/3000 TUE, NOV COPYRIGHT HEWLETT-PACKARD CO.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Based on the above formula for calculating MPE records, the initial capacity was 1 MPE record ( (10+9)/10), and the increment was 50 MPE records ( (500+9)/10). The correct physical EOF should be 51 (1+50). However, IMAGE EOF as shown by QUERY is 101 (1+50+50). This establishes that the IMAGE EOF was adjusted twice.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Important Information 1. The default for Critical Item Update option was changed from DISALLOWED to ALLOWED starting with Express 3 for 5.5. 2. A jumbo data set cannot be enabled for dynamic expansion. 3. PURGE and ERASE commands of DBUTIL are enhanced to prompt the user in session mode only (not batch) for confirmation (starting with version C.07.07). 4.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements IMAGE/SQL Enhancements Information regarding enhancements to IMAGE/SQL for SQL access is described in this section: • Predicate level lock when updating masters • Support for B-Tree indices • Support for third-party composite indices • New ODBC driver, ODBCLink/SE Predicate Locks when Updating Manual Masters IMAGE/SQL version B.G2.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements :DBUTIL HP30391C.07.04 TurboIMAGE/XL: PANY 1987 DBUTIL (C) COPYRIGHT HEWLETT-PACKARD COM >>show Music locks For database MUSIC LOCKED ENTITY / ( - waiting process ) PIN/ PATH ALBUMS: MEDIUM = ca . . . . . . . . . . . . . . . 41/1 PROGRAM NAME JOBNUM ISQL #S18 Now, User B wants to update row(s) in the same data set via an update statement: UPDATE Music.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements Although the B-Tree index on the related search item of the detail set is not explicitly created using DBUTIL or DBSCHEMA, its definition is entered in the SQL catalog. For example, if a B-Tree index is created on a key item with paths to 16 detail data sets, a definition for a B-Tree index for all 16 data sets will be entered as well. That is, this will result into 17 (1+16) definitions, one for each data set.
Technical Articles IMAGE/SQL with TurboIMAGE/XL Enhancements For SQL access, the only step necessary to use the above enhancements pertaining to relational access, is to perform DETACH, if attached, and ATTACH. Important Information 1. If you have third-party indexing (TPI) enabled for the database and want to create B-Tree indices, obtain the correct version of the third-party software which recognizes this coexistence.
Technical Articles New Features in ALLBASE/SQL Version G3 New Features in ALLBASE/SQL Version G3 by Doug Myers Database Lab, Commercial System Division Overview This article includes information on the following features of ALLBASE/SQL included with this version G3 on MPE/iX 6.0 release (C.60.
Technical Articles New Features in ALLBASE/SQL Version G3 Syntax . [ LOWER (stringexpr)] Upper Converts all the characters in stringexpr to upper case Syntax . [ UPPER (stringexpr)] Position Searches for the presence of the string stringexpr1 in the string stringexpr2 and returns a numeric value that indicates the position at which stringexpr1 is found in stringexpr2 Syntax .
Technical Articles New Features in ALLBASE/SQL Version G3 Syntax. [ TRIM ({ LEADING | TRAILING | BOTH} (,charset ,stringexpr)] Examples: Example 1 SELECT LOWER (OWNER) || '.' || LOWER (NAME) FROM SYSTEM.TABLE WHERE NAME = UPPER ('vendors'); Returns "purchdb .vendors " Example 2 SELECT POSITION ('world', 'hello world') FROM SYSTEM.TABLE WHERE NAME = UPPER('vendors'); Returns the numeric value 7 Example 3 SELECT INSTR ('hello world hello world', 'world', 5, 2) FROM SYSTEM.
Technical Articles New Features in ALLBASE/SQL Version G3 • ALLBASE/SQL Database Administration Guide • ALLBASE/SQL Message Manual Security Two new authorities have been added to the G2 release of ALLBASE/SQL: MONITOR and INSTALL. These new authorities can be granted to users using the GRANT command, or can be revoked from users using the REVOKE command.
Technical Articles New Features in ALLBASE/SQL Version G3 Solution When YY is specified in the format specification of either TO_DATE or TO_DATETIME, and if its value of the year specified is less than 50, then the century part of the DATE or DATETIME defaults to 20, otherwise it is set to 19. This behavior can be overridden by setting the JCW HPSQLsplitcentury to a value between 0 and 100.
Technical Articles New Features in ALLBASE/SQL Version G3 CAST Syntax {CAST ({Expression NULL}{AS,}DataType[,FormatSpec])} Parameters Expression Column, USER function, host variable, local variable, AddMonths function, aggregate function, date/time conversion function, dynamic parameter, or procedure parameter, constant, current function, long column function, string function, or any combination of these in an arithmetic or concatenation expression.
Technical Articles New Features in ALLBASE/SQL Version G3 Converting Pseudo-Mapped Files to Mapped Files ALLBASE/SQL files in pseudo-mapped mode must be converted into mapped mode using the MOVEFILE command in SQLUtil. Use the SHOWACCESS command in SQLUtil to show which files are pseudo-mapped. Use the following procedures: 1. Check for pseudo-mapped files as shown in this example: :sqlutil >> showaccess DBEnvironment Name: mydbe Maintenance Word: GGF0 mapped MYF1 pseudo-mapped MYF2 pseudo-mapped >> 2.
Technical Articles Year 2000 and Other Enhancements in VPLUS Year 2000 and Other Enhancements in VPLUS by Kumar KN and Rajesh Channabasavaiah Commercial Systems Division Introduction This article provides information on the following VPLUS enhancements available in version B.06.07.
Technical Articles Year 2000 and Other Enhancements in VPLUS Parameters comarea must be comarea name specified when the forms file was opened with VOPENFORMF. If not already set, the following comarea items must be set before calling VGETYYYYMMDD: cstatus set to zero. comarealen set to total number of two-byte words in comarea. Must be at least 70 words in length. VGETYYYYMMDD may set the following comarea item: cstatus set to nonzero value if call is unsuccessful or requested field has an error.
Technical Articles Year 2000 and Other Enhancements in VPLUS Intrinsic VPUTYYYYMMDD Converts a numeric value representing a date from an application and copies the converted value to a field in the data buffer in memory. Syntax VPUTYYYYMMDD {comarea,fieldnum,variable} Parameters comarea must be comarea name specified when the forms file was opened with VOPENFORMF. If not already set, the following comarea items must be set before calling VPUTYYYYMMDD: cstatus set to zero.
Technical Articles Year 2000 and Other Enhancements in VPLUS Example COBOL CALL "VPUTYYYYMMDD" USING COMAREA FIELDNUM VARIABLE. SPL VPUTYYYYMMDD(COMAREA,FIELDNUM,VARIABLE); These calls will convert the contents of VARIABLE to a date value and place the converted value in the data buffer corresponding to the field specified by FIELDNUM. FORMSPEC Enhancements FORMSPEC Application Ready Buffer (ARB) processing has been enhanced with the addition of a new ARB data type.
Technical Articles Year 2000 and Other Enhancements in VPLUS by VPLUS. For example, this scheme will allow the user to enter 02/29/00 (MDY order) in an existing application and have it processed correctly. To invoke the above method of date interpretation, define a JCW called VSETNEXTCENTURY and set bit 14 to 1. Note that this method is used for processing only 2-digit year dates and not 4-digit year dates. Note also that the display of 2-digit year dates is not affected by this enhancement.
Technical Articles Year 2000 and Other Enhancements in VPLUS • If the Data Type is blank, all newly created fields for the form will have a Data Type of “CHAR.” Ability to Define More than 52 Single Character Fields per Form This enhancement allows more than 52 single character fields to be defined for a Form. Currently the field tag which is defined for a field at screen design (creation) time should begin with an alphabetic character.
Technical Articles Year 2000 and Other Enhancements in VPLUS Intrinsic VGETSAVEFIELD Copies contents of the specified save field from save field buffer in memory to an application. Syntax VGETSAVEFIELD {comarea,sfname,sfbuf,buflen,actualen} Parameters comarea must be comarea name specified when the forms file was opened with VOPENFORMF. If not already set, the following comarea items must be set before calling VGETSAVEFIELD: cstatus set to zero.
Technical Articles Year 2000 and Other Enhancements in VPLUS Example COBOL CALL "VGETSAVEFIELD" USING COMAREA SFNAME SFBUF BUFLEN ACTLEN. SPL VGETSAVEFIELD(COMAREA,SFNAME,SFBUF,BUFLEN,ACTLEN); These calls will transfer the contents of the save field specified by SFNAME to SFBUF. If the call is successful, ACTLEN will contain the exact number of bytes transferred. Intrinsic VPUTSAVEFIELD Copies data from an application to the specified save field in memory.
Technical Articles Year 2000 and Other Enhancements in VPLUS If the length of the save field is less than the length specified by buflen, the bytes to the right are truncated. Following a successful transfer, actualen is set to the actual number of bytes transferred to the save field in memory. Note that the contents of the save field as recorded in the forms file is not changed by a call to VPUTSAVEFIELD. Also VPUTSAVEFIELD does not convert the data moved to the save field in memory.
Technical Articles CI Enhancements CI Enhancements by M Gopalakrishnan and Jeff Vance Commercial Systems Division Introduction This article describes the CI enhancements introduced in MPE/iX Release 5.5 Express 5 and 6.0. The most notable enhancement is that POSIX filenames support additional special characters. The COPY command has been enhanced and several new CI evaluator functions have been added.
Technical Articles CI Enhancements File equations are supported for both the FROM= and TO= parameters. However, the TO= name cannot be a back reference to a file equation who's actual filename is a directory. As before, symbolic links are accepted as the source and/or target filenames. Enhancements to the SHOWVAR Command The SHOWVAR command now allows users with SM capability to see user-defined CI variables for a job or session other than their own.
Technical Articles CI Enhancements New Evaluator Functions ANYPARM ANYPARM() returns any combination of characters as a string. String function. Syntax ANYPARM(anything) This new function accepts all characters, including, commas, quotes, right parentheses, etc. and treats them as a single string value. This is handy when used in conjunction with the ANYPARM parameter type. The one exception is that the "!" character, which introduces a CI variable.
Technical Articles CI Enhancements then the suffix is removed from the BASENAME. suffix applies to MPE and POSIX names. The suffix portion of the BASENAME will not be deleted if this results in deleting the entire basename. Examples CALC basename('a.b.c') A CALC basename('/a/b/c') c CALC basename('./a/b') b CALC basename("./a.sl",".sl") a CALC basename('/') / CALC basename("*feq") *FEQ CALC basename('$null') $NULL CALC basename('abc.g','c') AB CALC basename('/usr/lib/liby.a','.
Technical Articles CI Enhancements then the first iteration would call FINFO on a file named 'FILE0' rather than a file named 'FILE1'. This is because explicit variable dereferencing is performed early by the CI, well before the setvar() function is called. DIRNAME DIRNAME()—returns the directory components of a POSIX or MPE filename. String function. Syntax DIRNAME(str) This new function returns the directory components for the passed filename. str can be any filename in MPE or POSIX syntax.
Technical Articles CI Enhancements CALC fqualify('a') A.GROUP.ACCOUNT # when the CWD is your logon group /CWD/A # when the CWD is a directory or CALC fqualify('a.b') A.B.ACCOUNT CALC fqualify('a.b.c') A.B.C CALC fqualify('./a') /ACCOUNT/GROUP/a CALC fqualify('./A') A.GROUP.ACCOUNT # when the CWD is your logon group /CWD/A # when the CWD is a directory or CALC fqualify('/a/b/c') /a/b/c CALC fqualify('*a') *A CALC fqualify('$null') $NULL CALC dirname(fqualify('.
Technical Articles CI Enhancements endif if word(FSYNTAX(a_file)) = "MPE" then # MPE filename elseif word(FSYNTAX(a_file)) = "POSIX" then # POSIX filename else # error if pos("WILD", FSYNTAX(another_file)) > 0 then # wildcarded MPE or POSIX filename XWORD XWORD()—returns a string less 'word'. String function.
Technical Articles CI Enhancements • The FLABELINFO intrinsic and FINFO() function are able to return the number of sectors and extents a file occupies, file creation time, and the number of accessors to a file. • The PAUSE command can now wait for one or more jobs to complete, to change state from waiting to executing, or to begin execution. • The INPUT command allows the number of characters to read from $STDIN to be specified.
Technical Articles CI Enhancements Format 8 . Both formats 8 and 9 show the fully qualified filename or absolute pathname followed by the accessor summary line (described below).
Technical Articles CI Enhancements The number of processes that have the file locked (L:) is seen next. The number of lockers includes all file system locks (semaphores) held by all detectable processes that are accessing the file. A single process can obtain multiple locks, and each time the count is incremented. When a process releases a lock, the count is decremented.
Technical Articles CI Enhancements Format 9 . In addition to the format 8 data, format 9 shows more details such as: • PIN number • program name • access method (for example, read, execute, or others) • share mode (for example, multi, gmulti) • current record number being accessed • file number • locks the accessing process owns and is waiting on Following is a format 9 example: :listfile hppxudc.pub.sys,9 ******************** FILE: HPPXUDC.PUB.SYS 5 Accessors(O:5,P:5,L:5,W:0,R:5),Share #S263 JEFFV,MGR.
Technical Articles CI Enhancements 4. If the process does not have any locks then "NONE" is displayed. If the PIN owns or is waiting on one or more of the relevant semaphores, then the semaphore name is shown under either the "Owner" or "Waiter" column. There are three semaphores (locks) considered. • The FLOCK semaphore is obtained when a processes calls the FLOCK intrinsic. This lock is exclusive; meaning that only one process at a time can own the FLOCK semaphore for a file.
Technical Articles CI Enhancements FLOCK #S2 JVREM,MANAGER.SYS #P58 (CI.PUB.SYS) ACCESS: n/a LOCKSOwner Waiter OPEN P:1,L:1,W:0,R:0 REC#: n/a REM : 15.28.88.18 FNUM: n/a Restrictions . Formats 8 and 9 are available to all users, however only more privileged users get to see individual accessor information. The user having SM or OP capabilities can see all accessors of a file—assuming the user has TD access to the file itself.
Technical Articles CI Enhancements OPEN is true if there are any processes that have formally opened the file by calling FOPEN, HPFOPEN, RESET, OPEN, or others. OPEN uses the same field that the "O:" count is derived from. LOCK is true if any process has locked (even if they are waiting) the FLOCK, OPEN or GUFD semaphores, or has called the HPFLOCK pseudo intrinsic (for POSIX record level locking). EXCL is true if the file was opened for exclusive access.
Technical Articles CI Enhancements FLABELINFO and FINFO Enhancements The FLABELINFO intrinsic returns information from the file label of a disk file and the FINFO function is a CI interface to FLABELINFO.
Technical Articles CI Enhancements Footnote: this is the same value as the total number of accessors in the LISTF format 8 summary line. Examples finfo('CI.PUB.SYS',"sectors") finfo('CI.PUB.SYS',"extents") finfo('CI.PUB.SYS',"createtime") finfo('CI.PUB.SYS', -60) finfo('CI.PUB.
Technical Articles CI Enhancements NOTEXIST means to pause while the matching job or jobs do not exist. As soon as any jobs matching jobid exist (in any state) the pause completes. PAUSE might miss finding short-lived jobs. This is particularly true for a match on a single job/session number. A more practical use might be: PAUSE job=@J;notexist which means to sleep while no jobs exist. As soon as the first job is streamed the above pause stops.
Technical Articles CI Enhancements When more than one job or session matches jobid, PAUSE sleeps while all matching jobs are in their "while_state." If the job executing PAUSE matches jobid it will not be selected. interval_ secs if specified, PAUSE sleeps for this many seconds between attempts to see if jobid is still in its "while_state." Otherwise, PAUSE sleeps a variable amount of seconds depending on the job state and the number of previous times a particular job has been polled.
Technical Articles CI Enhancements The final example polls the JMAT every 3 minutes looking for any job or session matching a user name that includes the letters “MGR”, and waits for all such job/sessions to terminate before the pause ends. :PAUSE , @mgr@.@ , 180 INPUT Enhancement The INPUT command was enhanced to accept the number of characters to read from $STDIN.
Technical Articles CI Enhancements With this enhancement, the PRINT command syntax is PRINT [ [FILE=] filename] [[;OUT=]outfile] [[;START=] m] [[;END=] n] [[;PAGE=] p] [;UNN | NUM ] [;NONUM] • With this new option, to print the line numbers as in the case of UNNUMbered files (that is, line numbers starting from 1 for the first record and so on), use this command: :PRINT infile;NUM;NONUM • To consider the file as UNNUMbered file even when the file is a NUMbered file and then print the contents as it is in
Technical Articles The REMSH Client Functionality The REMSH Client Functionality by Cas Caswell Commercial Systems Division An Overview of the REMSH Service The remote shell, or REMSH, service is used to connect to a specified host and execute a command on that remote host.
Technical Articles The REMSH Client Functionality To edit the services file: 1. You may edit the SERVICES.NET.SYS file from MPE/iX. Open the services file with a text editor. 2. Verify that the following line exists in the file. shell 514/tcp cmd # remote command, no passwd used a. Add the line if it does not exist. b. If the line already exists in the file and is preceded by a pound symbol (#), delete the # and any spaces before the service name to enable the service. 3.
Technical Articles The REMSH Client Functionality Using REMSH The REMSH service is accessed by running the REMSH.NET.SYS program. You may do so under the MPE/iX CI or under the Posix shell. While the format of the commands will differ depending on how you run the program, the parameter list remains the same. We'll first look at the parameters and then look at running the program under the Posix Shell or from MPE/iX CI.
Technical Articles The REMSH Client Functionality run remsh.net.sys;info="remotehost -l remoteuser [-n] remotecommand" jhereg(PUB): run remsh.net.sys;info="taltos -l cawti -n pwd" /u2/home/cawti jhereg(PUB): Posix Examples From the Posix Shell prompt, type: /SYS/NET/REMSH remotehost -l remoteuser [-n] remotecommand shell/iX> /SYS/NET/REMSH taltos -l cawti -n pwd /u2/home/cawti shell/iX> Since you are running under the Posix shell, there are a number of shell features that you can take advantage of.
Technical Articles The REMSH Client Functionality Message remsh: MPE/iX/X version won't support rlogin or rexec functionality usage: remsh host -l login -n command Meaning Be sure to provide a command to execute. Message remshd: Login incorrect Meaning There is probably an invalid entry in remote .rhosts file. Be sure host name and userid are correct. Userid must be in upper case. Be sure you provided an -l userid parameter, or that the remote system has a userid that matches your MPE/iX logon.
Technical Articles The REMSH Client Functionality Meaning The remote command tried to reopen stderror. This is not allowed under REMSH. Message : ... Meaning Error in executing system call. Appended to this error is a message specifying the cause of the failure.
Technical Articles Transaction Manager Transaction Manager by Nagarajan and Jyothi Commercial Systems Division Overview Transaction Manager (XM) is an integral part of the MPE/iX file system. It provides a facility to log all the transactions that are done on a file that is attached to XM via a system intrinsic. It ensures data integrity by protecting such files across system crashes. Files on MPE/iX are of two categories: system files and user files.
Technical Articles Transaction Manager Commands to Expand The VOLUTIL tool is enhanced to provide two new commands to facilitate the expansion (or truncation after initial expansion) of the XM system log file. They are as follows: 1. showsyslog This command accepts a valid MPE volume set name and shows the current size of the XM system log in sectors. For this to work correctly, the master volume has to be mounted in MASTER state.
Technical Articles Transaction Manager Backdating the OS You can backdate the OS to an earlier version with the system log in the expanded state. The only condition is that the residual logs also must have been expanded or truncated to match it before the backdating is done. That would mean a complete, proper recovery of the volume set in question has to be done before the backdate operation. Warnings The expansion of the system log or the residual logs may fail due to one or more reasons.
Technical Articles Transaction Manager Backdating the OS While XM logger is doing copyfwd operation, it temporarily elevates the version of the XM system log to a higher value and brings it back to its original value once copy forward is over. But if the system crashes while the XM syslog version is at a higher level, backdating it to an earlier version of the OS wouldn't be possible. The system gives an error and XM recovery fails.
Technical Articles Transaction Manager Since this solution remembers the dirty page ranges in a data structure associated with each open file, it can't affect files that were open before giving this request. However, it will come into effect for the files that were open (for the first time) after giving the request. So the best way to enable or disable the Checkpoint Improvement is to reboot the machine after giving the command.
Technical Articles New Features for DTS/TIO Subsystem New Features for DTS/TIO Subsystem by Wendy Cheng Commercial Systems Division Introduction The Datacommunications and Terminal Subsystem (DTS) consists of host (HP 3000) based software and the DTC (Datacommunications and Terminal Controller) terminal server. The DTC family of products supports X.25 communication and Telnet access to HP 3000 systems, and TCP/IP communication to HP 9000 and non-HP systems.
Technical Articles New Features for DTS/TIO Subsystem • Configuration to enable or disable flow control between the DTC and the attached device. • Configuration of the number of stop bits on Host-based DTC ports. • Specification of whether "Keep Alive" mechanism is to be activated on Host-based DTC ports to detect if connection is still there. • Specification of whether port configuration parameters- data length and parity- have to be forced when binary mode is selected.
Technical Articles New Features for DTS/TIO Subsystem The complete list of supported modem types with MPE/iX 6.0 is: • US modem In Out • European modem In Out • Five wires modem • US modem • European modem • None (no modem) Data Length/Parity List Support With MPE/iX release 6.0, you can now use NMMGR to configure the two new parity types in the Host-based terminal, printer and host profiles. These two new parity types are: 8 bits data length with even parity and 8 bits data length with odd parity.
Technical Articles New Features for DTS/TIO Subsystem With MPE/iX release 6.0, you can now use NMMGR to configure a parameter in the Host-based TIO profiles to enable or disable flow control. If this feature is enabled in NMMGR for terminal/ printer, the data flow between the DTC port and the connection device is made with Xon/Xoff characters. If this feature is disabled, the XON/XOFF characters sent from device are not interpreted by DTC. This function is also known as "software handshake.
Technical Articles New Features for DTS/TIO Subsystem connection is allowed to each system. This is because each system must configure the DTC port on a specific LDEV (nailed devices). if the connections are to HP3000 systems using PC-based management, then more than one connections is allowed. This is because it is allowed to configure the DTC port to use non-nailed LDEVs. If the DTC port on the PC-based system is configured as nailed, then only one connection is allowed to that system.
Technical Articles Introducing ODBCLink/SE Introducing ODBCLink/SE by Dawna Whitehead M.B. Foster Associates Limited Overview ODBCLink/SE is a replacement for the HP PC API. It is an implementation of Microsoft's Open Database Connectivity (ODBC) interface that enables Microsoft Windows based applications and tools to access IMAGE/SQL on the HP 3000 and ALLBASE/SQL on the HP 3000 and HP 9000, in a client/server environment. ODBCLink/SE is a part of IMAGE/SQL and ALLBASE/SQL.
Technical Articles Introducing ODBCLink/SE Client/Server Interface The networked HP 3000 Series 9xx with ALLBASE/SQL and IMAGE/SQL (or the HP 9000 Series 7xx or 8xx with ALLBASE/SQL) provide the relational database environment on the server. Security is provided by the MPE/iX or HP-UX logon system and ALLBASE/SQL or IMAGE/SQL. ODBCLink/SE connects the client to the server with a collection of dynamic link libraries (DLLs) on the client and runs under Microsoft Windows 3.1 and 3.
Technical Articles Introducing ODBCLink/SE Client requirements: • 486 processor at a minimum, preferably a Pentium • 8 MB memory at a minimum, preferably 16 MB • 5 MB of free disk space • Windows 3.1 or 3.11, Windows95, or WindowsNT V3.51 or 4.0 • Microsoft or WRQ TCP/IP software Software provided: • Server program for the HP 3000 or HP 9000 as appropriate • Client programs for both 16- and 32-bit platforms. When using a 32-bit operating system, you should use the 32-bit driver if possible.
Technical Articles Introducing ODBCLink/SE Supported Functions and Commands These are the ALLBASE/SQL and IMAGE/SQL functions and commands supported by ODBCLink/SE: • The complete ALLBASE/SQL and IMAGE/SQL syntax dynamic SQL • All SQL functions You can use the ODBC SQLGetFunctions call to obtain a list of the supported ODBCLink/SE driver functions. Areas Not Fully Implemented Some areas of certain functions are not fully implemented.
Technical Articles Introducing ODBCLink/SE SQL_TXN_REPEATABLE_READ Repeatable Read (RR) SQL_TXN_SERIALIZABLE Repeatable Read (RR) SQL_TXN_VERSIONING Not Implemented • SQLSetStmtOptions are not supported. The driver will return either of these messages: Driver not Capable (SQLState S1C00) Option value changed (SQLState 01S02) Supported Data Types ODBCLink/SE supports ALLBASE/SQL and IMAGE/SQL data types.
Technical Articles Introducing ODBCLink/SE ALLBASE/SQL or IMAGE/SQL Data Type ODBC Data Type FLOAT(24), REAL, or Image E2 SQL_REAL FLOAT(53), DOUBLE PRECISION, or Image E4 SQL_DOUBLE Image R2 (non-IEEE float) SQL_REAL Image R4 (non-IEEE float) SQL_DOUBLE DATE SQL_DATE TIME SQL_TIME DATETIME SQL_TIMESTAMP INTERVAL SQL_CHAR ALLBASE/SQL Storage space for BLOBs should be created using a LONG VARBINARY column.
Technical Articles Introducing ODBCLink/SE To use multiple statements when you are not writing your own SQL application, tell ODBCLink/SE to have SQLGetInfo report more than one statement per connection. ALLBASE/SQL Restrictions These are the ALLBASE/SQL and IMAGE/SQL restrictions on the ODBC grammar.
Technical Articles Introducing ODBCLink/SE Unsupported ALLBASE/SQL and IMAGE/SQL Statements There are several reasons why some ALLBASE/SQL and IMAGE/SQL statements are not supported in the ODBCLink/SE environment: • ODBCLink/SE does not support embedded SQL, therefore statements that work only with embedded SQL are not supported. See details that follow. • Statements that relate to functions, such as connection, that have been replaced by functions resident on the client. See details that follow.
Technical Articles Introducing ODBCLink/SE The following ALLBASE/SQL and IMAGE/SQL statements are not supported because they have been replaced by other functions resident on the client: Table 10-9 Replaced Functions CONNECT DISCONNECT RELEASE RESET SET CONNECT SET MULTITRANSACTION START DBE START DBE NEW START DBE NEWLOG STOP DBE Utilities The utilities provided with ODBCLink/SE do the following: • Test and verify that the driver is functioning correctly.
Technical Articles Introducing ODBCLink/SE ODBCLink ODBCLink/SE is a “Special Edition” of M. B. Foster Associates Limited ODBCLink option of DataExpress.
Technical Articles Introducing Samba/iX Introducing Samba/iX by Wendy Cheng Commercial Systems Division Overview Samba/iX is a suite of programs which work together to allow clients to access a server's file space and printers via the Server Message Block (SMB) protocol. Samba is the Server Message Block (SMB) file server that runs on MPE/iX shell operating system on MPE/iX release 6.0.
Technical Articles Introducing Samba/iX • A SMBCLIENT utility is part of Samba suite. SMBCLIENT is a client that can access to a SMB (Server Message Block) server. It provides a user interface similar to that of FTP program. Mainly, it is used on UNIX based servers as they typically do not have a Windows File Manager available. • A NMBLOOKUP utility allows to query WINS name-servers and to assist with manual NETBIOS name resolution.
Technical Articles Introducing Samba/iX You can also access server based printers using Samba/iX. Printer sharing works in such a way that the client creates a file on server directory associated with the printer, and then the server process triggers a configurable command to push that file into the MPE spooler. Starting Samba/iX Before you start to run Samba/iX server or client components, you should have set up the TCP/IP networking on your HP 3000 system as well as your PC.
Technical Articles Introducing Samba/iX NETWORK IP ADDRESS: $0F0DC750 15.13.188.80 NETWORK SUBNET MASK: $0FF000000 255.0.0.0 Starting SMBD and NMBD as Daemons 1. Logon as MGR.SAMBA 2. Copy the sample configuration file smap-smb.conf, samp-printcap and samp-user.map to smb.conf, printcap and user.map. Modify the entries to suit your Samba/iX environment. The samp-smb.conf, samp-princap and samp-user.map files reside in the /usr/local/samba/lib directory. 3.
Technical Articles Introducing Samba/iX 4. Use the following two commands to create symbolic links to make SERVICES.NET.SYS link to /etc/services and INETDCNF.NET.SYS links to /etc/inetd.cnf respectively: :newlink /etc/services, /SYS/NET/SERVICES :newlink /etc/inetd.conf, /SYS/NET/INETDCNF 5. Stream JINETD.NET.SYS or use INETD.NET.SYS -c (if INETD job was already running) to start SMND listener and NMBD server. 6. Use SHOWOUT JOB= Jobnumber 7. Print Oxxx.OUT.
Technical Articles Introducing Samba/iX Samba/iX Version The current version of Samba/iX on 6.0 is based on Samba/iX 1.9.16p9; the port uses the LIBBSD package (libraries and include files) available on Jazz (http://jazz.external.hp.com). This is to resolve the BSD style routines that are not part of POSIX to successfully compile with HPC/iX (c89 under the POSIX shell.
Technical Articles Developer’s Kit for Java/iX Developer’s Kit for Java/iX by Mike Yawn Commercial Systems Division Background The Java development environment (including compiler, runtime, and class libraries) was first ported to MPE in 1996, and various versions have been available as unsupported freeware since that time. Beginning with MPE/iX 6.0, a version of Java is now bundled with the MPE operating system.
Technical Articles Developer’s Kit for Java/iX the one included with the OS is more recent. If you have installed any version of Java on your system, you can determine the version by typing the following at the POSIX shell prompt (or at a CI prompt if you have set up the proper UDCs to allow Java to be accessed from the Command Interpreter): java -version You can compare this to the version number in the readme file (README.INSTALL.JAVA) after updating your MPE/iX system to 6.0. If the 6.
Technical Articles Developer’s Kit for Java/iX PATH (or HPPATH) Variable Example of setting PATH from the shell: shell/iX> export PATH=$PATH:/usr/local/java/latest/bin Example of setting HPPATH from the CI: :setvar HPPATH HPPATH+",/usr/local/java/latest/bin/PA-RISC/green_threads" These variables are not Java-specific, but rather the standard path variables used to search for executable program files. The Java executable program files are in the directory shown for the HPPATH variable.
Technical Articles Developer’s Kit for Java/iX shell/iX> export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:(add your stuff here) Example of setting LD_LIBRARY_PATH from the CI: :setvar LD_LIBRARY_PATH "/usr/local/java/latest/lib/PA-RISC/green_threa ds: (add your stuff here)" Again, we specify a colon-separated list of directories to search. In this case, we're providing the locations to search for library (XL) files that contain native (that is, platform-specific) code.
Technical Articles Developer’s Kit for Java/iX users probably won't need the AWT on the HP 3000; user-interface code is usually downloaded to a Web browser or run in some other client-server type of configuration. We certainly recommend this for your own development: • Design the user interface as a separable module that can be executed on a client, and leave application logic and database access modules on the server.
Technical Articles Developer’s Kit for Java/iX created at this level to hold that version of the binaries. The lib hierarchy follows the same structure as the bin hierarchy, with PA-RISC and green_threads subdirectories. One file residing at the top level of the lib hierarchy, classes.zip, is an archive file that contains all of the standard Java classes. You do not have to unzip it to access this archive (in fact, you can access it faster as a single zip file than as hundreds of individual disk files).
Technical Articles Developer’s Kit for Java/iX Because the class name is HelloWorld, this program needs to be saved as HelloWorld.java. Compiling a Program The compiler for Java programs is called javac, so the above program is compiled simply by: javac HelloWorld.java This command can be entered at either a CI prompt or at a shell prompt. The compiler will produce a class file called HelloWorld.class.
Technical Articles Developer’s Kit for Java/iX • The Home Page for Java on the HP 3000 http://jazz.external.hp.com/src/java contains the latest MPE-specific Java information and downloadable software. SIG JAVA is the Interex Special Interest Group for Java on all HP Platforms. SIG JAVA holds discussions via the JAVA mailing list. You can subscribe by sending an email to java-request@interex.org with the message "subscribe java yourname" in the body of the message.
Technical Articles Hewlett-Packard NetWorker Client for MPE/iX Hewlett-Packard NetWorker Client for MPE/iX by Lalitha Pejavar and Alex Early Commercial Systems Division Overview Available now for HP 3000 users is NetWorker from Legato, a client/server application that provides advanced storage management capabilities to a heterogeneous environment of servers and desktop computers.
Technical Articles Hewlett-Packard NetWorker Client for MPE/iX Features These are the key features of the NetWorker Client for MPE/iX: • Provides an easy-to-operate graphical user interface and maintains a file index and media index to track data backed up and recovered. • Supports a wide range of industry tape (DAT) and DLT libraries and furnishes a sophisticated media manager which allows for unattended backup and restore using autochange library.
Technical Articles Hewlett-Packard NetWorker Client for MPE/iX Legato NetWorker is the only third-party storage management solution supported by HP Worldwide Customer Support Operations. HP Response Center engineers have been fully trained on NetWorker operations. HP support contracts are available for NetWorker from your HP sales representative.
Technical Articles FTP Enhancements FTP Enhancements by Raghuram B. Commercial Systems Division The following is a description of new features available with FTP/iX. Implementation of FTPSRVR under INETD Prior to Release 6.0, the FTP/iX server, FTPSRVR, was initiated by the FTPMON process by the JFTPSTRT.ARPA.SYS job. For 6.0, the JFTPSTRT.ARPA.SYS job is no longer used. Instead the job, JINETD.NET.SYS is streamed to initiate the FTP server.
Technical Articles FTP Enhancements Support for Non-Standard MPE/iX File Types The following types of MPE/iX files can be transferred to a remote host using FTP. • Standard MPE files with fixed, variable or bytestream format. • Files with either binary or ASCII data types. In addition, the latest enhancements enable the transfer of the following types of non-standard files between two HP3000 machines.
Technical Articles FTP Enhancements ftp> get db000 200 PORT command okay 150 File: db000 opened; data connection will be opened 2816 bytes received in 0.02 seconds (130.95 Kbytes/sec) ftp> FILENAME CODE BIGRIO1 ------------LOGICAL RECORD----------SIZE TYP EOF 128B FAR 8193 LIMIT R/B 8192 ----SPACE---SECTORS #X MX 3 4128 1 8 ftp> get bigrio1 200 PORT command okay 150 File: bigrio1 opened; data connection will be opened 1054934 bytes received in 3.69 seconds (279.
Technical Articles FTP Enhancements Example ftp> hash Hash mark printing on (1024 bytes/hash mark). ftp> get TESTFILE 200 PORT command successful. 150 Opening BINARY mode data connection for TESTFILE (145915 bytes) ############################################################### ############################################################### ######## 226 Transfer complete 145915 bytes received in 0.32 seconds (438.
Technical Articles FTP Enhancements system. MPE/iX file security and access rights may prevent successful removal of the original source file despite the use of the MOVE command. Syntax { get } { put } { } source file [target file][;buildparms] [;move] { mget} { mput} Parameters : none Operation : This option requests that the specified source file be physically moved from the source location to the specified target location.
Technical Articles FTP Enhancements The Implementation of CI Environment Variables for Additional FTP/iX Status Information The following status information will be provided through these CI environment variables: FTPXFERFILES number of files successfully transferred during the last FTP/iX execution. FTPREQFILES total number of files requested for transfer during the last FTP/iX execution.
Technical Articles FTP Enhancements FTPREQFILES = 4 FTPREPLACE = TRUE :if FTPREQFILES <> 4 and FTPXFERFILES = 2 then Chapter 10 259
Technical Articles DNS BIND/iX and Syslog/iX DNS BIND/iX and Syslog/iX by Wendy Cheng Commercial Systems Division DNS BIND, which stands for Berkeley Internet Name BIND/iX Domain, is an implementation of the Domain Name System (DNS) and is the most commonly used of the Domain Name System (DNS). Now, the complete implementation of DNS BIND/iX runs on MPE/iX shell operation system on MPE/iX release 6.0. Initially, DNS BIND/iX was written for UNIX. Now, the latest version of DNS BIND/iX 8.1.
Technical Articles DNS BIND/iX and Syslog/iX dnsquery The dnsquery tool can be used to provide you all the DNS detail information. Overview of Syslog/iX Syslog is the standard event logging system for Syslog/iX UNIX. Now the Syslog/iX can run on the MPE/iX shell operating system on MPE/iX release 6.0. With the features of Syslog/iX available on MPE/iX systems, the event messages can be logged to files, terminal devices, or even forward to other syslog systems.
Technical Articles DNS BIND/iX and Syslog/iX Loopback Address Files A name-server needs one additional db.ADDR or zone.ADDR file to cover the loopback network. The loopback address is a special address that hosts use to direct traffic to themselves. This network is always 127.0.0. and the host number is always 127.0.0.1. Therefore, the name of this file is zone.127.0.0.
Technical Articles DNS BIND/iX and Syslog/iX Refresh The refresh field specifies the time interval that must elapse between each poll of the primary by the secondary name server (here 36,000 seconds or 10 hours). If the “serial number” has been updated on the primary server, the secondary name-server assumes its data is stale and requests updated information as a “zone transfer.
Technical Articles DNS BIND/iX and Syslog/iX How to Run Syslog/iX The following describes the important steps to start Syslog/iX: 1. Log on to the system as MGR.SYSLOG. 2. Create, examine and adjust the Syslog configuration file syslog.conf. The syslog.conf file resides in /SYSLOG/PUB directory. 3. You stream the following job to start Syslog/iX: STREAM JSYSLOGD.PUB.SYSLOG 4.
Technical Articles DNS BIND/iX and Syslog/iX ## :TELL MANAGER.SYS ## *.err MANAGER.SYS ## ## Forward to syslogd on another host via UDP ## *.warning @some.host.running.syslogd ## *.info ## ## Write to a file ## *.debug /tmp/syslog.log The error messages coming from a program are classified into critical informative and alert types of messages. The syslog configuration file tells the syslog daemon how to post these messages. They could be sent to the console or to a log file, or to another machine.
Technical Articles DNS BIND/iX and Syslog/iX The following describes how you can set up the debugging level in the JNAMED.PUB.BIND: JNAMED.PUB.BIND: !job jnamed,mgr.bind;outclass=,2 !run named;info=”-f /BIND/PUB/etc/named.conf” !eo The parameter “-d ” can be specified in the info string of the run command. Example !run named;info=” -d 4 -f /BIND/PUB/etc/named.conf” It will set the debugging level 4. The logging and trace messages can be seen in the spool files.
Product Release History 11 Product Release History This chapter contains tables that provide information on the currently supported Commercial Systems MPE/iX releases and products, and the systems supported for the 6.0 release.
Product Release History Product Changes by Releases Product Changes by Releases The following table provides information on the currently supported Commercial Systems MPE/iX releases and products. Included are the MPE/iX release or SUBSYS VUF and a list of products introduced. It also provides information on significant changes made to a release. Table 11-1 Release MPE/iX Product Releases SUBSYS C.50.00 Date Code R3504 Product(s) Introduced/Added MPE/iX Release 5.
Product Release History Product Changes by Releases Release SUBSYS C.55.00 Date Code R3628 Product(s) Introduced/Added MPE/iX Release 5.5 (Non-Platform Release) HP Loader Dependent Libraries Subsystem Dump Facility HP Stage/iX HP Patch/iX TurboSTORE/iX 7x24 True-Online Backup HP Optical Disk Libraries: C1150B - 40GB C1160B - 80GB C1170B - 100GB TCP/IP Network Printer Support Telnet/iX Server DTS/TIO Dynamic Configuration Online System Device Configuration C.55.
Product Release History Product Changes by Releases Release SUBSYS Date Code R3748 Product(s) Introduced/Added Express 4 based on Release 5.5 Year 2000 enhancements MPE/iX new date intrinsics 997/100-500 support Enhancements for: Transact V and Transact/iX Dictionary/3000 COBOL II/iX Inform/V HP ALLBASE/BRW QUERY/iX R3813 PowerPatch 5 based on Release 5.
Product Release History Supported Releases Supported Releases The naming conventions for the different types of releases have been changed slightly to clarify the type of release being discussed. The terms used to describe or refer to the releases are: Mainline Release A mainline release involves the recompilization and reintegration of all software release components (FOS, SLT, and SUBSYS tapes). The release number is changed (for example, 5.0 or 5.5) and the update "UU" field of the V.UU.FF is changed.
Product Release History Supported Releases Given the rate with which we ship releases, this new strategy implies that any particular release will be supported for at least three years, and in most cases, most releases will be supported for a significantly longer period of time. This new strategy is effective now. This implies that Release 5.0, which first shipped February 17, 1995, will become obsolete as early as six months after Release 6.0 ships.
Product Release History Supported Releases Supported Releases Release 6.0 (C.60.
Product Release History Supported Releases 274 Chapter 11
Catalog of User Documentation 12 Catalog of User Documentation This chapter provides listings of customer manuals for the HP 3000 computer system. The listings are divided into two sections: • "MPE/iX 6.0 New or Updated Manuals," which lists all manuals that have been introduced or changed since the MPE/iX 5.5 Release. • "Manual Collections," which lists manuals by collections in alphabetical order.
Catalog of User Documentation MPE/iX 6.0 New or Updated Manuals MPE/iX 6.0 New or Updated Manuals This section lists customer manuals introduced or updated from MPE/iX-Express 2 based on General Release 5.5 through MPE/iX 6.0 Release. Table 12-1 MPE/iX 6.0 New or Updated Manuals Manual Title Part No.
Catalog of User Documentation MPE/iX 6.0 New or Updated Manuals Manual Title Part No. Latest Edition Legato NetWorker ClientPak for MPE/iX User's Guide B5475-90002 12/97 Legato NetWorker ClientPak for MPE/iX Release 5.
Catalog of User Documentation Manual Collections Manual Collections Table 12-2 Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Previously Used CO Number Part Number Latest Edition Laser ROM 11/97 LR Instant Info 6.0 View on the WEB* HP ALLBASE/4GL Self-Paced Training Guide 30601-90203 30601-90207 May-92 y n y HP ALLBASE/4GL Software Update Notice B.06 Release 5961-7797 5063-3725 Feb-93 y n y HP ALLBASE/BRW Reference Manual 35360-90051 35360-90052 Jan-92 y n y HP ALLBASE/BRW SW Update Notice for MPE/iX (BRW A.01.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.0 View on the WEB* n n .pdf n n .pdf Dec-97 n n .pdf 30349-90005 Jun-92 y y y B3933-90002 B3933-90002 Jun-97 n n .pdf NBSpool Release Notes Version 9.7 B3933-90008 B3933-90008 Jun-97 n n .pdf NetBase for MPE Reference Guide B3933-90001 B3933-90001 Jun-97 n n .pdf NetBase Release Notes Version 9.7 B3933-90007 B3933-90007 Jun-97 n n .
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.0 View on the WEB* Nov-96 n n .pdf 09740-96001 May-90 n n n A1809-90009 A1809-96019 Apr-97 n n n A2051-90006 A2051-96006 Oct-93 n n n Previously Used CO Number Part Number - A2375-90073 HP 3000 and HP 9000 PA-RISC Computer System Support Log 09740-90013 HP 3000 CS 99x/890/T500 Families Operator’s Guide HP 3000 Series 9X8lx/RX Computer Systems Inst.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections Laser ROM 11/97 LR Instant Info 6.
Catalog of User Documentation Manual Collections 292 Chapter 12
Index Numerics 2 GB disk device, 107 4 GB disk device, 107 A account naming structure, 39 ALLBASE/SQL CAST function, 178 new features in version G2, 176 ODBCLink/SE, 226 pseudo-mapped files, 180 year 2000 compatibility, 177 ALLBASE/SQL version G3, 79 ALTJOB HIPRI enhancements, 42 Autoloader for MPE/iX, 113 B backdating from MPE/iX 6.
Index R releases mainline, 271 non-platform, 271 platform, 271 product history, 267 supported, 271 remote shell, 210 REMSH client, 210, 213 functionality, 210 troubleshooting, 213 RPG/iX 4-digit year enhancement, 144 and ALLBASE/SQL, 177 VPLUS enhancements, 181 year 2000 enhancements, 119, 181 year 2000 web page, 118 S Samba/iX, 236 SCSI device configuration, 34 Sherlock, 66 Stage/iX, 49 STORE with NetWorker Client, 251 supported devices, 107 supported releases, 271 SupportLine MPE/iX patches available,
