Communicator 3000 MPE/iX Release 6.5 (Non-Platform Software Release C.65.00) HP 3000 MPE/iX Computer Systems Volume 11, Issue 1 Manufacturing Part Number: 30216-90291 E0300 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 1. Announcements Introducing MPE/iX 6.5 Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removal of Support for Servers and HP-IB in MPE/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Discontinuance of High Availability Fiber Link Disk Drives . . . . . . . . . . . . . . . . . . . . . . . . . Obsolete Products Removed from Release 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents OPTIONS Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Command Interpreter Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 Intrinsics Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 New Intrinsics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents C/iX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C/iX Supports 64-bit Integers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FTP/iX Support for Large Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents About the DLT Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 TurboSTORE Products and the DLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 About Fast Search on Tapes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Fast Search on DLT Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Large Transactions for IMAGE Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Current Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XM User Checkpoint Priority Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 8
Tables Table 5-1.. Data Type Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-2.. Data Type Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-3.. Unsupported Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-1.. MPE/iX Product Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-2..
Tables 10
Announcements Introducing MPE/iX 6.5 Release 1 Announcements Introducing MPE/iX 6.5 Release Welcome to the exciting MPE/iX 6.5 release. New releases of MPE/iX usually have a short set of focus areas where we have concentrated our efforts to have a major impact. In the case of MPE/iX 6.5, those areas of focus are performance scaling and capacity.
Announcements Removal of Support for Servers and HP-IB in MPE/iX Removal of Support for Servers and HP-IB in MPE/iX In order to streamline the development and test of future MPE/iX releases, the PBA-IB HP-IB Device Adapter (A1747A) and old CIB I/O based HP 3000 Servers will not work with MPE/iX Release 6.5 and later releases. The PBA-IB HP-IB Device Adapter was discontinued in May 1999 and has an end of support date of November 1, 2001.
Announcements Discontinuance of High Availability Fiber Link Disk Drives Discontinuance of High Availability Fiber Link Disk Drives In May 1993, Hewlett-Packard Company introduced a family of High Availability Fiber Link disk arrays. Those Fiber Link (HP-FL) disk arrays were discontinued in August of 1997, along with other standalone Fiber link disk drives. The Fiber Link disk arrays were HP’s first RAID devices built for high availability, high performance, high capacity and distances up to 500 meters.
Announcements Obsolete Products Removed from Release 6.5 Obsolete Products Removed from Release 6.5 by Allan Hertling CS R&D Numerous products that have reached their “End of Support Life” were removed from the SUBSYS tape for the 6.5 release. The following obsolete products have been removed.
Announcements Obsolete Products Removed from Release 6.5 This product removal from the SUBSYS tape will affect you if one or more of these products reside on your system. During an FOS Update If your system contained any of the above listed products, the associated library modules were removed from the system libraries.The product files will not be removed. NOTE The products listed above are obsolete and no longer supported.
Announcements Files Associated with Obsoleted Products: Resource Sharing, CCSY Access Server, CCSY Access SQL, Cooperative Services/XL Files Associated with Obsoleted Products: Resource Sharing, CCSY Access Server, CCSY Access SQL, Cooperative Services/XL by Sue Meloy CS-R&D The following products are obsolete and no longer being shipped: • B1718A Resource Sharing • B3160A CCSY Access Server • B3162A CCSY Access SQL • 32571A Coop.
Announcements Files Associated with Obsoleted Products: Resource Sharing, CCSY Access Server, CCSY Access SQL, Cooperative Services/XL Also, modules HP32589_01 and NWOLC_01 in XL.PUB.SYS and segment PPCDIAG in SL.PUB.SYS are installed by this product. Files Related to B3160A CCSY Access Server HDPMC000.PPC.SYS ADMENUS.PPCUTIL.HPOFFICE HDPHC000.PPC.SYS DHDPGINP.PPCUTIL.HPOFFICE ADFRM000.PPC.SYS DHDPMODS.PPCUTIL.HPOFFICE TRFRM000.PPC.SYS DHDPMAP.PPCUTIL.HPOFFICE HDSP.PPC.SYS SSAMPL1.PPCUTIL.
Announcements Files Associated with Obsoleted Products: Resource Sharing, CCSY Access Server, CCSY Access SQL, Cooperative Services/XL Files Related to 32571A Coop. Services/XL HCS.PPC.SYS HCSERVER.PPC.SYS SHCSAMP.PPCUTIL.HPOFFICE HCSMAST.NET.SYS SAMPXEQ.PPCUTIL.HPOFFICE HCSSERV.NET.SYS JHCSAMP.PPCUTIL.HPOFFICE HCSFILE.NET.
Announcements Important Support Changes in MPE/iX 6.5 Important Support Changes in MPE/iX 6.5 by Gary Robillard CS-R&D Product Overview HP Predictive Support provides proactive 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.
Announcements Important Support Changes in MPE/iX 6.5 You should insure that there is a “SPOOLER LP;OPEN” and a “STREAMS 10” command before the “STREAM JPSMON.PRED.SYS” command in the sysstart file. Also recognize that for your system, the line printer might have a different class name than “LP”, and your streams device might have a logical device number other than 10. Here is an example of what the lines in sysstart.pub.
Announcements Important Support Changes in MPE/iX 6.5 The following peripherals are no longer supported: Any HPIB or FLEX Interface Disk, including but not limited to: HPC2200A 335MB HPIB Disk HPC2202A 670MB HPIB Disk HPC2203A 670MB HPIB Disk HPC2281A 335MB HPIB Disk HPC2282A 670MB HPIB Disk HPC2201A 670MB Flex Disk HPC2204A 1.34GB Flex Disk The following SCSI disks are no longer supported: HPC2460x 420MB Disk HPC2461x 673 MB Disk HPC2462x 1.
Announcements Obtaining Software Security Patches for your HP Computer System 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).
Announcements Obtaining Software Security Patches for your HP Computer System 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.
Announcements Obtaining Software Security Patches for your HP Computer System 24 Chapter 1
Overview—MPE/iX Release 6.5 (C.65.00) 2 Overview—MPE/iX Release 6.5 (C.65.00) This Communicator 3000 provides general and detailed information on the new and enhanced functionality for the MPE/iX 6.5 Release (C.65.00), as well as information on release strategy and installation prerequisites. MPE/iX 6.5 has accumulated all of the functionality previously released on MPE/iX 6.0 Express releases such as Year 2000 enhancements, ODBCLink/SE—a 32-bit driver from M.B.
Overview—MPE/iX Release 6.5 (C.65.00) Communicator Summary Communicator Summary Following are brief descriptions of the articles and chapters. Chapter 1 Announcements Important announcements regarding availability of products and services are included in this chapter. • Introducing MPE/iX 6.5 Release -- provides overview of 6.5 enhancements. • Removal of Support for Servers and HP-IB in MPE/iX -- details the discontinuance of support for certain older servers and the HP-IB device adapter.
Overview—MPE/iX Release 6.5 (C.65.00) Communicator Summary • Increased Number of DSTs -- describes the increased number of data segments. • User-defined Job Queues and ALTJOB HIPRI Enhancements -- describes the enhancement to 255 user-defined job queues possible on Release 6.5. • NEWCI Command (CI Elimination) -- describes the functionality and implementation of the NEWCI command. • Compatibility Considerations for COBOL and C -- describes the issues for COBOL and C as they relate to Large Files.
Overview—MPE/iX Release 6.5 (C.65.00) Communicator Summary available for IMAGE users • XM User Checkpoint Priority Control--describes the Transaction Manager process to write out dirty pages to reduce response time. • Transact/iX Expanded B-Tree and File Open Enhancement--describes the enhancements to Transact/iX to support B-Trees and File Open. • Apache for MPE/iX -- describes new server software which enables your HP 3000 to function as a full-featured web server.
Overview—MPE/iX Release 6.5 (C.65.00) MPE/iX Patches on HP IT Resource Center MPE/iX Patches on HP IT Resource Center by Patch Support Team Commercial Systems Division MPE/iX patches for MPE/iX Release 5.5 and later, are available on the IT Resource Center (previously 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.5 (C.65.00) MPE/iX Patches on HP IT Resource Center 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. HP IT Resource Center will inform you proactively about newly developed security and GR patches.
Overview—MPE/iX Release 6.5 (C.65.00) MPE/iX Patches on HP IT Resource Center running an earlier version than is available, you should download and install the newer one from the download page. AUTOPAT Installation Document Retrieval AUTOPATINST is the “DOCID” of the document with instructions to assist you in installing one or more patches needed by your MPE/iX system using the AUTOPAT installation tool. 1.
Overview—MPE/iX Release 6.5 (C.65.
Growth Solution 3 Growth Solution This chapter contains the following articles about the Growth Solution.
Growth Solution MPE/iX Large Files Overview MPE/iX Large Files Overview by Craig Fairchild Commercial Systems Division Introduction This document describes the changes to the MPE/iX operating system as a result of the initial addition of Large File functionality. In this document, Large Files are defined as any file greater than 4GB - 64KB (4,294,901,760 bytes) which was the maximum file size prior to release 6.5.
Growth Solution MPE/iX Large Files Overview of an ordinary fixed-length record file can affect the maximum size of file.
Growth Solution MPE/iX Large Files Overview Problem Description Due to the way that existing MPE/iX compilers emit instructions to access memory, problems can result when accessing Large Files with a Large File pointer. Long pointers on PA-RISC hardware are defined to have two separate parts; a space ID, and an offset within that space.
Growth Solution MPE/iX Large Files Overview FLABELINFO Two current items of the FLABELINFO intrinsic are unable to return information on some Large Files. These items are described in the following table: Item # Description New Item # Description 28 This item returns the size of the file limit of a file in bytes. It returns the value in an unsigned 32-bit integer.
Growth Solution MPE/iX Large Files Overview Intrinsic Item # or Parameter Item Name Description FFILEINFO 9 FF_RECORD_PTR A 32-bit signed integer which returns the record number of the current logical data pointer associated with the specified file number FFILEINFO 10 FF_EOF_PTR A 32-bit signed integer which holds the current EOF record number of the specified file FFILEINFO 11 FF_FILE_LIMIT A 32-bit signed integer that returns the record number of the file limit of the file (the maximum siz
Growth Solution MPE/iX Large Files Overview AIF:OS Impact The Architected Interfaces for operating system information (AIF:OS) are a set of privileged routines that provide a supported means of accessing and altering internal system data structures. Because of the need to enhance these data structures to provide Large File support, some corresponding changes to a few AIF:OS routines are required. Each of the affected AIF:OS items follows a similar form.
Growth Solution MPE/iX Large Files Overview AIF Function Item # New Item # Description AIFFILEGPUT 5017 5101 These items allow the EOF of a file to be set to a specified byte offset. Item 5017 allows the caller to specify a 32-bit unsigned integer for the new EOF offset. Due to the size of this value, it is not possible to use this item to set an EOF beyond 4GB in any file.
Growth Solution MPE/iX Large Files Overview OPTIONS Enhancement As a side effect of adding support for the KSAM64 file type, a new file type value, 7, has been allocated for KSAM64 files. The foptions structure is a 16-bit value made up of various bit fields. Several intrinsics accept or return foptions including FOPEN, FFILEINFO, FLABELINFO, and FGETINFO.
Growth Solution MPE/iX Large Files Overview BUILD Command Changes With the first release of Large File support, only two file types are being supported for Large File sizes; ordinary, fixed length record files, and KSAM files. Because of inherent limitations in the internal format of KSAMXL and CM KSAM files, it is necessary to introduce a new type of KSAM file, KSAM64 files, in order to go beyond a 4GB sized KSAM file.
Growth Solution MPE/iX Large Files Overview records that had a maximum capacity of about 8GB, a file limit of 100,000,000 records would need to be specified. For example, the following command could be used: BUILD TESTFILE;REC=-80,,F,ASCII;DISC=100000000 Specifying a file limit that is greater than 4GB for any type of file other than ordinary fixed length record files and KSAM64 files will result in an error.
Growth Solution MPE/iX Large Files Overview FILE Command Changes The FILE and BUILD command syntaxes always mirror each other. It follows, then, that the new KSAM64 file type keyword is also being added to the FILE command, in the exact same way as the BUILD command.
Growth Solution MPE/iX Large Files Overview LISTF[ILE | TEMP] Command Changes The LISTF, LISTFILE, and LISTFTEMP commands all can be used to display information about Large Files. All of the various LISTF and LISTFILE formats continue to work with normal sized files as well as Large Files. File type information about KSAM64 files is displayed in the LISTF family of commands as a lowercase ‘k’. In order to display information about Large Files, two new file format options have been introduced.
Growth Solution MPE/iX Large Files Overview :listf @,11 ACCOUNT= SYS GROUP= EXAMPLE Name Access FCode RecSiz Type EOF File Limit Disk Usage Exts -------- ERWS ----- ------ ----- ------------- ------------- --------KB ----BIGFILE ICE XKSM64 XKSMXL XRAND XRAND2 YRAND E NMPRG RW W NMOBJ 1024 256 80 80 80 252 256 FA FB FAk FAK FA VA FB 0 832 1 1 157 396 22 1023456789 832 1023 1023 157 49 4000 0 208 64 52 16 16 8 0 1 1 1 1 1 1 :listfile .
Growth Solution MPE/iX Large Files Overview crosses a SID boundary. In order to ensure that programs are aware of this caveat, traditional attempts to open a Large File for user-mapped access will fail.
Growth Solution MPE/iX Large Files Overview FFILEINFO Changes Two new items have been added to the FFILEINFO intrinsic. These items are described in the table below: Item Name Item Number Item Size Description FF_FILE_LIMIT_BYTES 109 8 bytes This item returns a 64-bit integer indicating the maximum size of the file, or the file limit, in bytes.
Growth Solution MPE/iX Large Files Overview are encountered, status returns 32 bits of zero. If errors or warnings are encountered, status is interpreted as two 16-bit fields. Bits (0:16) comprise status.info. A negative value indicates an error condition, and a positive value indicates a warning condition. Bits (16:16) comprise status.subsys. The value represents the subsystem that set the status information.
Growth Solution MPE/iX Large Files Overview HPFMOVEDATALTOR NM callable only. This routine can be used to efficiently move data from a source buffer to a target buffer. If the source and target buffers were viewed horizontally, like a line of text, the data movement is performed by starting at leftmost position of the source buffer (to the leftmost position of the target buffer) and proceeding to the rightmost.
Growth Solution MPE/iX Large Files Overview HPFMOVEDATARTOL NM callable only. This routine can be used to efficiently move data from a source buffer to a target buffer. If the source and target buffers were viewed horizontally, like a line of text, the data movement is performed by starting at the rightmost position of the source buffer (to the rightmost position of the target buffer) and proceeding to the leftmost.
Growth Solution MPE/iX Large Files Overview HPFFILLDATA NM callable only. This routine can be used to efficiently initialize a buffer with a specified character value. Syntax I64 @64 CV I32 HPFFILLDATA ( count, buffer_ptr, fill_char, status ) Parameters count 64-bit signed integer by reference (required) A positive count of the number of bytes in the buffer indicated by the buffer_ptr parameter that should be initialized.
Growth Solution MPE/iX Large Files Overview If you rely on 3rd party backup tools, please refer to your vendor for information regarding the proper updates and procedures for using these tools on release 6.5. Backdating Procedures If for some reason it is necessary to “backdate” your system from the 6.5 release to a prior MPE/iX release, very little extra work is required due to Large Files. Before attempting the backdate operation, the 6.
Growth Solution MPE/iX Large Files Overview been enhanced to search KSAM64 and KSAMXL files. HPGLANCEPLUS/iX HPGlancePlus/iX has been changed to display file information about Large Files. Also, KSAM64 files are included in the File Display on the Process Screen and will show a type of KSM64. HPBROWSE/iX HPBrowse/iX supports viewing Large Files and KSAM64 Files. HPEDIT/iX HPEdit/iX does not support files of 2,000,000 records or more, and so, does not support Large Files.
Growth Solution AIFs for Large Files AIFs for Large Files by Rajesh Channabasavaiah Commercial Systems Division The Architected Interface Facility (AIF) Operating System product has been enhanced to handle the instances of Managing Large Files (Up to 1TB) with the AIF Intrinsics. AIFs are a software layer between non-operating system software and internals providing controlled access to MPE/iX internal functionality and data structure. For Release 6.
Growth Solution AIFs for Large Files Error Messages Two New Error Messages have been introduced for the AIF:OS product as part of the Large Files project to handle the existing items and the new items for the Intrinsics documented above.
Growth Solution AIFs for Multiple Job Queues AIFs for Multiple Job Queues by Rajesh Channabasavaiah Commercial Systems Division The Architected Interface Facility (AIF) OS product has been enhanced to return the information about the multiple job queues running on the MPE/iX Version 6.0 and above. The Job Queue information obtained will provide the job queue name, job queue limit, number of jobs executing and also the total number of jobs in the queue.
Growth Solution Increase in Number of TCP Connections Increase in Number of TCP Connections By Ganesh HS & Chandrashekar MN Commercial Systems Division Introduction Prior to the MPE/iX 6.5 release, TCP on MPE/iX allowed a maximum of 10240 connections. HP has enhanced the TCP module to get up to 20000 connections. Configuration through NMMGR You need to configure the machine to allow it to accommodate up to 20,000 connections.
Growth Solution Increase in Number of TCP Connections To reach this screen, “Transmission Control Protocol (TCP) Config” in NMMGR, do the following: 1. Go to [ Open Config ] 2. Go to [ NS ] 3. Go to [ Unguided ] 4. Go to [ Netxport ] 5. Go to [ Gprot ] 6. Go to [ TCP ] After the re-configuration, stop the network (via NETCONTROL) if it is already started and restart the network. Now TCP is ready to accommodate up to 20,000 TCP connections.
Growth Solution Dispatcher Multiple Runqueues Dispatcher Multiple Runqueues by Senthil Kumar R Commercial Systems Division Introduction The MPE/iX Operating System is continuously undergoing various enhancements to keep pace with the increasing performance needs of HP 3000 customers. The support for Dispatcher Multiple Runqueues is one such enhancement in MPE/iX Release 6.5 which is aimed at providing improved system performance to customers.
Growth Solution Dispatcher Multiple Runqueues Conclusion In summary, the support of multiple runqueues in MPE/iX 6.5 boosts the performance of the HP 3000 to a great extent and makes it more scalable with respect to number of processors used. It has been enabled for 997 systems with 10 or 12 processors on Release 6.5 The users can also experience better response time from the system.
Growth Solution Increased System Limits - An Overview Increased System Limits - An Overview by Ganapati Commercial Systems Division One of the major enhancements of the MPE/iX 6.5 release is increases to several former operating system limits. These enhancements are designed to help large HP 3000 sites continue to grow the workload on their systems. It is important to note that some of these limits can be achieved only under certain conditions. Further details will be provided in the articles which follow.
Growth Solution Support for 511 Disks on MPE/iX Support for 511 Disks on MPE/iX by N. A. Narayanan Commercial Systems Division Introduction Beginning with MPE/iX Release 6.5, it is possible to configure up to 511 spindles, an increase from the present limit of 255 disks. Configuring More Than 255 Disks The existing utilities volutil and mirvutil are used to configure more than 255 disks. There are no interface changes to these utilities to configure more than 255 disks.
Growth Solution Increased Number of DSTs Increased Number of DSTs by Senthil Kumar R Commercial Systems Division Introduction DSTs are Data Segments used in MPE/iX for supporting Compatibility Mode (CM) operation. With the increase in capabilities of HP 3000 systems and MPE/iX OS over the years, it became necessary to increase the total number of DSTs supported in MPE/iX. This article gives a technical overview of the changes done in MPE/iX Release 6.
Growth Solution Increased Number of DSTs HP 3000 customers and paves the way for future capacity expansions in many more areas of MPE/iX. The increase to 65535 DSTs is expected to meet the requirements for years to come and carry MPE/iX forward through its future enhancements.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements User-Defined Job Queues and ALTJOB HIPRI Enhancements by Jayaram and S Shashikala Commercial Systems Division Enhancements Summary Previously MPE/iX had one job queue into which all the submitted jobs went before getting launched by the dispatcher. Often this proved to be a hindrance, as a few long jobs could prevent a lot of short jobs from running.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements New Commands NEWJOBQ Syntax: NEWJOBQ qname [;limit=n] The NEWJOBQ command creates a new job queue. SM/OP capability is required to execute this command. Limit is the only queue controlling property. The jobs in the queue are sorted by their INPRI. In case of a tie for INPRI, jobs are sorted by their INTRO time. The global limit takes precedence over individual queue limits.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements PURGEJOBQ Syntax: PURGEJOBQ qname The PURGEJOBQ command deletes a job queue. The queue will be deleted only if it is empty, that is, if no jobs are waiting or executing in the queue. The default system job queue can not be purged. The user must have SM/OP capability to execute the command.This command is available in a session, job, or in BREAK. Pressing [Break] aborts the execution of this command.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements Modified Commands LIMIT Syntax: {numberjobs LIMIT [{ + }] [{,numbersessions { - } } }] {numberjobs,numbersessions} [;jobq= ] The LIMIT command allows users with OP capability to change the job and session limits. As a result of this enhancement, it can be used to change the limit value of individual job queues. The LIMIT command now accepts a new parameter ;jobq= .
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements JOB Syntax: JOB [jobname,]username[/userpass].acctname[/acctpass] [,groupname[/grouppass]] [;TIME=cpusecs] {BS} {CS} [;PRI= ] {DS} {ES} [{;INPRI=inputpriority}] {;HIPRI } [;RESTART] [;OUTCLASS=[device][,outputpriority[,numcopies]]] [;TERM={termtype}] [;PRIVATE] [;SPSAVE] [;JOBQ= ] The JOB command now accepts a new parameter ;jobq=. Users can specify the job queue name into which a particular job should logon.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements ALTJOB Syntax: ALTJOB [JOB=] {#Jnnn} {#Snnn} [[;INPRI=]inputpriority] [[;OUTDEV=]{ldev {devclass} }] [;JOBQ=qname] [;HIPRI] ALTJOB alters the attributes of waiting or scheduling jobs. ALTJOB now accepts a new parameter ;jobq=. Jobs waiting or executing in a queue can moved to other queues. Only users with SM/OP capability can move jobs.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements STREAM Syntax: STREAM [filename] [,char] [;AT = timespec] [;DAY = {day-of-week } {day-of-month } {day-until-month} ] [;DATE = datespec] [;IN = [days[, [hours] [,minutes]]]] [;JOBQ = qname] The 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.
Growth Solution User-Defined Job Queues and ALTJOB HIPRI Enhancements SHOWJOB Syntax: [[#]Snnn ] [[#]Jnnn ] SHOWJOB [STATUS ][;JOBQ][;*listfile] [SCHED ] [item[;item[;...]]] The SHOWJOB command displays status information about jobs/sessions. It now accepts a new parameter ;JOBQ which indicates the queue name to which the job belongs. If the ;JOBQ option is not specified, the SHOWJOB output is the same as before. A new field JOBQ is added to the showjob output format.
Growth Solution NEWCI Command (CI Elimination) NEWCI Command (CI Elimination) by Scott McClellan Commercial Systems Division MPE/iX Release 6.5 supports a new command called NEWCI. The NEWCI command is similar to the pre-existing RUN command in that it is used to execute a program. Every time a program executes, a new process is created. A process can be defined as an “independent instance or execution of a program”. Both the NEWCI and RUN commands create a new process.
Growth Solution NEWCI Command (CI Elimination) executes underneath the caller (which is generally the MPE/iX CI). By contrast the NEWCI command will cause the specified process to replace the MPE/iX CI process. The MPE/iX CI is terminated - thus one process is saved. Syntax NEWCI progfile[,[ “]entrypoint[ “]] [;NOPRIV] [;LMAP] [;DEBUG] [;MAXDATA=maxstack] [;PARM=parameternum] [;STACK=stacksize] [;DL=dlsize] [;NMSTACK=nmstacksize] [;NMHEAP=nmheapsize] {G} [;LIB={P}] {S} [;XL=”library[, ...
Growth Solution NEWCI Command (CI Elimination) • If the program is linked with PH capability, then users must have PH capability to load the program. • CM Programs cannot be loaded from the HFS directory. For detailed information on any of the other NEWCI parameters, refer to the RUN command help text. Operation and Use of New Command The syntax for the NEWCI command (and all of the parameters) is identical to the RUN command.
Growth Solution NEWCI Command (CI Elimination) • Any UDC files which were cataloged prior to the NEWCI are still cataloged (and thus are executable via the HPCICOMMAND intrinsic). • DSLINEs which were opened prior to :NEWCI will be closed. NEWCI CI.PUB.SYS The NEWCI command can be used to replace the current CI process (which may not be the standard MPE/iX CI if a NEWCI command was previously done) with the standard MPE/iX CI. This is done by executing the command “newci ci.pub.sys”. If CI.PUB.
Growth Solution NEWCI Command (CI Elimination) NOTE In the above example the “:newci payroll.pub.payroll” command would not be allowed if the RUN command had been used in place of the NEWCI command to load TDP. NEWCI CI.PUB.SYS The NEWCI command can be used to replace the current CI process with the standard Hewlett- Packard Command Interpreter (CI.PUB.SYS). When CI.PUB.SYS is executed using the NEWCI command it functions exactly the same as it does at logon time (see table above). :hello mgr.
Growth Solution Compatibility Considerations for COBOL and C Compatibility Considerations for COBOL and C by Walter Murray Support Technology Lab This article discusses compatibility concerns relating to HP COBOL II/iX and HP C/iX on MPE/iX 6.5. These concerns are the result of enhancements to provide better language support for 64-bit integers. The project to improve support for 64-bit integers involved changes to four products.
Growth Solution Compatibility Considerations for COBOL and C COBOL/iX Backward compatibility for COBOL II/iX executable programs (NMPRGs) and executable libraries (NMXLs) should not be a problem. If your COBOL code generates calls to any of the new Millicode routines, those routines will be copied from the Millicode library and bound into your program or XL.
Growth Solution Compatibility Considerations for COBOL and C • Your printf() and scanf() calls produce incorrect results. This could happen if your code uses the new functionality for handling 64-bit integers with these functions. If you do try to move a COBOL or C application from a 6.5 system to a pre-6.5 system and it doesn’t work, you probably can work around the problem. As a last resort, you may have to recompile on the pre-6.5 system.
Growth Solution C/iX Supports 64-bit Integers C/iX Supports 64-bit Integers by Walter Murray Support Technology Lab In response to a number of customer requests, we have enhanced the C/iX compiler, the C/iX Library, and the MPE/iX Millicode library to provide full support for a 64-bit integer data type. This article provides the information you need in order to declare, operate on, and perform input/output operations on 64-bit integers in C.
Growth Solution C/iX Supports 64-bit Integers The following sample program is an example of how to declare, use, and print a 64-bit integer using C/iX. /* Compile on MPE/iX 6.5. */ /* With CCXL use "-Aa +e" or "-Ae". */ /* With c89 use "-Wc,+e". */ #include
Growth Solution FTP/iX Support for Large Files FTP/iX Support for Large Files by R. Prakash Commercial Systems Division The enhancement “FTP/iX support for Large Files” which is part of MPE/iX Release 6.5 provides the capability for FTP on MPE/iX to transfer files of size greater than 4GB. This enhancement is an offshoot of the support for Large Files in MPE/iX 6.5. Until MPE/iX 6.0, you could transfer files up to 4GB in size through FTP.
Growth Solution FTP/iX Support for Large Files ftp> put ksm64001 Server Not compatible to transfer largefile Data Transfer Request Failed. (FTPERR 13) ftp> Installation There are no changes in the installation procedures.
Growth Solution FTP/iX Support for Large Files 86 Chapter 3
Data Center Management 4 Data Center Management This chapter contains technical articles that provide information about new or enhanced components of data center management in the MPE/iX 6.5 release.
Data Center Management Enterprise Management Solution Enterprise Management Solution by Saurabh Kelkar Commercial Systems Division The Current Need As data centers become larger, the complexity of managing them increases multifold. Today’s challenge is to manage distributed, heterogeneous IT environment that comprises various systems.
Data Center Management Enterprise Management Solution Short Term Plans In the next 1-2 years, we plan to strengthen our basic set of offerings. A very near future inclusion is providing support for the HP Secure Web Console (SWC). The inclusion of HP SWC in the list of devices supported by the HP 3000 means that the users have ‘Location Independence’ for accessing the HP 3000 system console. This is, of course, coupled with a high level of security to provide a secure access to the system’s console.
Data Center Management Enterprise Management Solution Summary We know that the data center management needs are going to grow. The need to handle large amounts of data, the need to have highly available data, the need for increased performance of backup, the need to have a better fault tolerant storage system, the need to have a scalable storage system etc. are some of the future needs.
Data Center Management Support Tools Manager (STM) Support Tools Manager (STM) by Bart Anderson Diagnostics and Support Tools With MPE/iX 6.5, the Support Tools Manager (STM) replaces the sysdiag diagnostic system on HP 3000 computer systems. STM has been the diagnostic platform for HP-UX since 1996. STM was ported to MPE/iX to provide a common diagnostics platform for MPE/iX and HP-UX systems.
Data Center Management Support Tools Manager (STM) • Different file structure. • No xstm (GUI) interface for MPE/iX. • MPE/iX version initially contains a subset of the tools on the HP-UX version. • An additional standalone version of logtool to handle MPE/iX system logs. • The first release of STM on MPE/iX is based on the A.12.00 version of STM (June 1998, IPR 9806). To learn how to use STM, refer to “Support Tools Manager (STM) for MPE/iX” in the MPE/iX 6.5 System Software Maintenance Manual.
Data Center Management Enhanced Message Source Template for HP 3000 Agents in ITO Enhanced Message Source Template for HP 3000 Agents in ITO by Shirin Mendonce Commercial Systems Division Introduction In a new ITO setup a default set of message source templates is installed on the Management Server for every managed node platform supported by ITO. These default templates are downloaded from the Management Server at the time of Agent installation onto the managed nodes.
Data Center Management Enhanced Message Source Template for HP 3000 Agents in ITO Disk Drive Monitor This template monitors the current status of the disk drives on MPE/iX systems. The executed script, DEVINFO, retrieves the disk drive status information and writes to the file DEVDATA.
Data Center Management Enhanced Message Source Template for HP 3000 Agents in ITO is returned. The threshold can be defined as increasing or decreasing depending on how the outfence is normally used for the given device. An outfence that is higher than expected will result in spoolfiles being deferred that would otherwise print. If the outfence is lower than expected, spoolfiles that should have been deferred are printed. The monitor can be used to monitor either of these conditions.
Data Center Management Enhanced Message Source Template for HP 3000 Agents in ITO Network Services Monitoring This template monitors the status of the NS Network Services. The monitor program NSSTATUS returns the status of the Network Services to the Management Server. Database Monitoring This template monitors the capacities and database flags for Image/SQL databases. The executed script, DBINFO.MONITOR.OVOPC, retrieves the database information and writes it to the file DBSTATUS.PUB.OVOPC.
Data Center Management Enhanced Message Source Template for HP 3000 Agents in ITO • User logons on LDEV 20 which is the console • User logons on LDEV 21 which is the remote console • Logons on LDEV 10 which are from jobs Backup/Tape Volumes Messages that come under this category are: • STORE Bad media messages • STORE Completion status messages • Tape not ready messages • Tape mount request pending messages Open View System Manager All OpenView System Manager messages generated by virtue of their being i
Data Center Management HP Secure Web Console HP Secure Web Console by Umakanth Rajsekhar C. Commercial Systems Division Product Overview This module gives an overview of the HP Secure Web Console. (Product No. J3591A) The HP Secure Web Console (SWC) is now available on the HP 3000 for its user community. The HP SWC is the first product from Hewlett-Packard’s new Internet Product family.
Data Center Management HP Secure Web Console the product will be available on the Internet. Software upgrade is easily achieved using a standard FTP server. Product Structure J3591A: HP Secure Web Console (includes localized power supply and quick installation guide).
Data Center Management HP Secure Web Console Support from the World Wide Web HP provides product and support information from the World Wide Web to identify and resolve problems. The site can be accessed at: http://www.hp.com/go/webconsole For further information you can contact: Umakanth umak@india.hp.com OR Saurabh saurabh@india.hp.
Data Center Management TurboSTORE Support for DLT TurboSTORE Support for DLT by Uma Bondada Commercial Systems Division About the DLT Drives DLT drives offers the following advantages: • Faster Backups and more reliable backups • High capacity (up to 70 GB uncompressed) • Faster Restore and hence faster disaster recovery TurboSTORE Products and the DLT The following Turbostore products support DLT without the fast search option: Product Number Product Description 31900B FOS Store B5151AA TurboStore/
Data Center Management TurboSTORE Support for DLT be applied are given in the following table: MPE/iX Releases 5.5 6.0 6.
Data Center Management DLT4000/DLT7000 Differential Tape Support on MPE/IX DLT4000/DLT7000 Differential Tape Support on MPE/IX by Larry Nichoalds, CSY Labs Jim Hawkins, SSD WTEC Beginning with Release 5.
Data Center Management DLT4000/DLT7000 Differential Tape Support on MPE/IX supporting the DLT Libraries for “normal” MPE/iX operations such as BOOT, FCOPY or STORE. DLT Libraries are supported only when used in conjunction with a third party software package, Legato’s “NetWorker.” Inquiries about DLT Library support should be made directly to Legato.
Data Center Management DLT4000/DLT7000 Differential Tape Support on MPE/IX IMPORTANT Tapes created on a DLT4000 can always be read by the DLT7000; however, DLT4000 drives are not capable of reading tapes created on DLT7000s. Since both drives use the same physical media type, shops with a mixture of DLT types will have to manage media created on DLT7000 separately so as not to attempt to read it on a DLT4000.
Data Center Management DLT4000/DLT7000 Differential Tape Support on MPE/IX Configuration Here is an example of what the configuration should look like on the HP 3000 for the DLT4000 and DLT7000. DLT4000 Example io> ld 90 LDEV: 90 DEVNAME: OUTDEV: ID: DLT4000 RSIZE: PATH: 4/4.2.0 MPETYPE: CLASS: TAPE DLTTAPE DDUMP 0 128 24 MODE: DEVTYPE: TAPE MPESUBTYPE: 8 io> lp 4/4.2.0 PATH: 4/4.2.0 ID: DLT4000 PMGR: SCSI_TAPE2_DM LOGICAL_DEVICE_MANAGER LDEV: TYPE: PMGRPRI: MAXIOS: io> lp 4/4.2 PATH: 4/4.
Data Center Management Announcing DLT8000 Differential Tape Support on MPE/iX Announcing DLT8000 Differential Tape Support on MPE/iX By Tina Wang, CSY Labs and Dave Black, MPE/iX Expert Center MPE/iX now supports the following Differential DLT Tape drive (this is in addition to the previously announced DLT4000 and DLT7000): DLT8000 (C6378A) F/W SCSI interface Stand-Alone DLT8000 (C6379A) F/W SCSI interface Rack-Mount Software Requirements Customers wishing to use this new DLT device must be running on
Data Center Management Announcing DLT8000 Differential Tape Support on MPE/iX NOTE While DLT Libraries are available for purchase, support for these devices is very limited on HP 3000 S900 systems. There are currently no plans for supporting the DLT Libraries for normal MPE/iX operations such as BOOT, FCOPY or STORE. DLT Libraries will be supported only when used in conjunction with a third party software package, Legato’s NetWorker. Inquiries about DLT Library support should be made directly to Legato.
Data Center Management Announcing DLT8000 Differential Tape Support on MPE/iX LMGR: Chapter 4 MAXIOS: 0 109
Data Center Management TERMDSM: User Interface Change under System Diagnostics TERMDSM: User Interface Change under System Diagnostics by Umakanth Rajasekhar Commercial Systems Division The underlying Diagnostics Interface has changed. This article gives information on what the user will see and what it means to invoke TERMDSM to diagnose the DTCs and its connected ports. Starting with MPE/iX Release 6.
Data Center Management TERMDSM: User Interface Change under System Diagnostics Use of this program is subject to the licensing restrictions described in “Help-->On Version”. HP shall not be liable for any damages resulting from misuse or unauthorized use of this program. cstm> cstm> ru termdsm -- Termdsm Utility. -******************************************************************* ***** ***** ***** TERMDSM ***** ***** ***** ***** (C) Copyright Hewlett Packard Co.
Data Center Management TERMDSM: User Interface Change under System Diagnostics CAUTION The user is advised NOT to try reset/dump operation from a session connected to the DTC that he/she is diagnosing. This may potentially cause TERMDSM to have an abnormal exit. Other Commands of Interest Tools Related UAL Utility Activity Log: This gives the status of invoking the tool.
Data Center Management HP SureStore E Disk Array 12H on the HP 3000 HP SureStore E Disk Array 12H on the HP 3000 Rich Bassett Walt McCullough Commercial Systems Division Site, Software and Hardware Requirements The following is a summary of Site, Software and Hardware requirements for support of the HP SureStore E Disk Array 12H. Device installation and support is to be provided by HP.
Data Center Management HP SureStore E Disk Array 12H on the HP 3000 • No support for shared SCSI busses. • F/W SCSI Device Adapter Card (28696A, known as “Wizard) firmware MUST be at level 3728 or greater • 9x9 Core I/O card (A2372-60004 or A3453-60010) will be conditionally supported with the following requirements: — Must disconnect all internal F/W SCSI drives — Must have firmware level of 3636. — Up to 8 LDEVs will be supported (Tested limit).
Data Center Management HP SureStore E Disk Array 12H on the HP 3000 Off-line Diagnostics There is a new off-line utility called ARDIAG that is supported within the support media off-line (ODE) diagnostics. See chapter 7 of the HP SureStore E Disk Array 12H System Administrators Guide for HP-UX, MPE/iX, and Microsoft Windows NT for how to use this command. Configuring the 12H for Performance on the HP 3000 • The single X controller is the only connection to the HP 3000 supported for this release.
Data Center Management DVD Supported on the HP 3000 DVD Supported on the HP 3000 by Alex Early and Dave Black Commercial Systems Division The embedded CD-ROM shipped with many HP 3000 servers has come to the end of its life. However, many customers purchased HP 3000s with CD-ROMs to take advantage of system update material and manuals that are available on CDs. The A3715A, a 12x CR-ROM, is being replaced by the new DVD-ROM. The DVD-ROM supports usage of the older CD-ROM disks.
Data Center Management DLT7000 and Legato Storage Node Usage DLT7000 and Legato Storage Node Usage Legato Storage Node and DLT libraries are now supported beginning with MPE/iX 5.5 with express 7 and MPE/iX 6.0 with express 1 plus patches. With Legato Storage Node software (B6266AA), the HP 3000 supports FWD SCSI connected DLT libraries with DLT7000s or DLT8000s directly connect to the HP 3000. DLT7000 support is beginning with MPE/iX 5.5 Express 7 and MPE/iX 6.
Data Center Management HP SureStore E Disk Array XP256 HP SureStore E Disk Array XP256 by Rich Bassett--CSY Lab Alex Early--CSY Product Marketing The Hewlett-Packard SureStore E Disk Array XP256 provides high-capacity, high-speed mass storage, with continuous data availability, ease of service, scalability, and connectivity. The disk array can be connected to multiple server systems. The HP 3000 supports the XP256 through Fast-wide SCSI connections. The disk array can have up to 32 SCSI ports.
Data Center Management HP SureStore E Disk Array XP256 — Only RAID 1 is support for LDEV 1. — Microcode down-loading, online memory replacements and disk adapter replacements must be performed with no jobs or sessions logged on. — LDEV 1 capacity limited to 4 Gbytes (due to NIO IODC limits). Support on MPE/iX has the following restrictions: • No logging to the host of any vendor unique error codes. These codes are used to identify any hardware component (FRU) that has failed.
Data Center Management SureStore E Disk Array XP256 Business Copy XP and/or Continuous Access XP in an HP 3000 Environment SureStore E Disk Array XP256 Business Copy XP and/or Continuous Access XP in an HP 3000 Environment by Walt McCullough Commercial Systems Division Product Descriptions Business Copy is an XP256 feature that allows for copy on demand of selected disk volumes. These volumes should be grouped as User Volumes, an MPE/iX term.
Data Center Management SureStore E Disk Array XP256 Business Copy XP and/or Continuous Access XP in an HP 3000 Environment Figure 4-1. Basic Setup of Business Copy System A Procedures Setup System A The first time setup requirements are as follows: 1. Create the Logical Unit Numbers (LUNs) and paths you will use on the XP256 and then using Sysgen or IOCONFIG create the LDEVs associated with the paths and LUNs. Make sure to use HPDARRAY as the ID type. We use the LDEV 60 through 62 for our examples.
Data Center Management SureStore E Disk Array XP256 Business Copy XP and/or Continuous Access XP in an HP 3000 Environment (MPE/iX Prompt):dstat all LDEV-TYPE STATUS VOLUME (VOLUME SET - GEN) -----------------------------------------60-OPEN-3 MASTER MEMBER1 (PRODUCTION_DATA-0) 61-OPEN-3 MEMBER MEMBER2 (PRODUCTION_DATA-0) 62-OPEN-3 MEMBER MEMBER3 (PRODUCTION_DATA-0) 4. Next, create the directory and accounting structure on the system that will use the User Volume.
Data Center Management SureStore E Disk Array XP256 Business Copy XP and/or Continuous Access XP in an HP 3000 Environment ---------60-OPEN-3 61-OPEN-3 62-OPEN-3 -------LONER-RO LONER LONER -------------------------MEMBER1 (PRODUCTION_DATA-0) MEMBER2 (PRODUCTION_DATA-0) MEMBER3 (PRODUCTION_DATA-0) The master volume should say LONER-RO, which means that it is closed and access is defined as Read-Only. MPE/iX will not let you mount a Read-Only disk because it is not supported on MPE/iX.
Data Center Management SureStore E Disk Array XP256 Business Copy XP and/or Continuous Access XP in an HP 3000 Environment Continuous Access The diagram below describes the use of both Continuous Access and Business Copy to provide both disaster recovery and off loading of work done by the remote data center. Figure 4-2.
Internet and Interoperability 5 Internet and Interoperability This chapter provides the following articles about the Internet and interoperability. • Large Transactions for IMAGE Users • XM User Checkpoint Priority Control • Transact/iX Expanded B-Tree and File Open Enhancement • Apache for MPE/iX • Introducing LDAP C-SDK/iX • MPE/IX Software Developer’s Kit (SDK) for Java, Version 1.
Internet and Interoperability Large Transactions for IMAGE Users Large Transactions for IMAGE Users By B T Vikram Kumar, B S Jyoti, Shobha Pradeep Commercial Systems Division Background Of late many of the users of TurboIMAGE and IMAGE/SQL have the requirement of transaction sizes larger than is currently possible today (4 MB). This is true, especially for users who run applications involving bulk puts/ deletes /updates.
Internet and Interoperability Large Transactions for IMAGE Users Solution Objective The main objective of this solution therefore has been to increase the transaction size from the existing 4 MB. The second objective is to increase the size of the XM userlog from the current value of 64 MB to support large transactions.The third objective is to ensure compatibility with existing applications, so that they can run without any problems even with these enhancements.
Internet and Interoperability Large Transactions for IMAGE Users message is written onto the console. One can also truncate the userlog after expansion if there are any disk space or performance issues. The volutil interface is same for this operation too. One can backdate the OS to an earlier version with the userlog in the expanded state. The expansion of the userlog may fail due to one or more reasons. In that case, the system reports it through a warning message on the console.
Internet and Interoperability Large Transactions for IMAGE Users • to commit the transaction (through a call to DBXEND) • to rollback the transaction (through a call to DBXUNDO) Thus, there will not be a situation in which the transaction size reaches the hard limit resulting in automatic rollback and process abort. Once the decision on rollback/ commit has been made and executed, you can start a new dynamic transaction to continue the job until the next softlimit warning is reached, and respond as above.
Internet and Interoperability Large Transactions for IMAGE Users Limitations If MPE/IX 6.5 is installed on a system, then TurboIMAGE/iX version C.08.00 also needs to be installed. However, this Image version can work with older versions of XM as well. In this case, XM will support transaction sizes only up to 4 MB, and will not issue a softlimit warning message.
Internet and Interoperability XM User Checkpoint Priority Control XM User Checkpoint Priority Control Jyothi BS Commercial Systems Division Background Whenever one half of the Transaction Manager (XM) user log gets full, XM starts the checkpoint process to write out all the dirty pages of the files which have transactions logged in that half. During user Checkpoint on many busy high-end systems, the response to on-line users is very poor. Sometimes, it almost stalls.
Internet and Interoperability Transact/iX Expanded B-Tree and File Open Enhancement Transact/iX Expanded B-Tree and File Open Enhancement by James Overman Commercial Systems Division Hewlett-Packard has implemented two more enhancements in Transact/iX (HP30138A.07.00).
Internet and Interoperability Transact/iX Expanded B-Tree and File Open Enhancement The B-tree search can only be used for the following data retrieval verbs: DELETE, FIND, GET, OUTPUT, REPLACE, and PATH. Only the CHAIN or RCHAIN modifiers can be used for the data retrieval verbs. The key and argument register should be set prior to the data retrieval. The STATUS count returned may not always be accurate. For example, DBFIND modes 21 and 24 do not return the correct chain count or entry numbers.
Internet and Interoperability Transact/iX Expanded B-Tree and File Open Enhancement << Uses parent/child items to devise Structured Argument. >> move (search-type) = "[]"; let (search-version) = 0; let (arg1-size) = 8; let (arg2-size) = 8; move (arg1) = "PROD1 ";<< Blank pad the full number of characters.>> move (arg2) = "PROD2 ";<< Blank pad the full number of characters.
Internet and Interoperability Transact/iX Expanded B-Tree and File Open Enhancement move (search-arg) = col("PROD1",9); move (search-arg) = col("PROD2",17); set(key) list(search-arg); list(key) prod-no; output(chain) inventory, list=(prod-no:ship-date),findmode=24; exit; File Open Transact "File Open" is the name of the feature which allows database and file ids to be passed into Transact/iX from other languages or Third Party packages.
Internet and Interoperability Transact/iX Expanded B-Tree and File Open Enhancement file when the file is first used in a Transact/iX program. PASSED does not open the file - generally the file id is passed from another program. If neither DEFER or PASSED is specified, then DEFER is assumed. DEFER is the way Transact/iX worked prior to this enhancement. KSAM= file-name[(access)[(file-option-list)]]. See FILE= for DEFER and PASSED options.
Internet and Interoperability Transact/iX Expanded B-Tree and File Open Enhancement end; . . . var data_buffer : data_record; . . . base_name := ' NAME; '; password := 'PASS1 '; mode := 1; dbopen (base_name, password, mode, db_status_array); { check db_status_array } . . . strmove (2, base_name, 1, data_buffer.id_type, 1); system_name := 'aci01 '; data_size := 58; tl_call_transact (system_name, addr(data_buffer), data_size, return_status); { check Transact's return_status } . . . end.
Internet and Interoperability Apache for MPE/iX 6.5 Apache for MPE/iX 6.5 by Barbara Dubbert Commercial Systems Division Overview Apache for MPE/iX is server software which turns your HP 3000 into a full-featured web server. With the Apache web server, HP 3000 users can now do business over the Internet. As a web server, your HP 3000 can provide users with direct access to documents and applications residing on your system.
Internet and Interoperability Apache for MPE/iX 6.5 Major Components The major components for Apache are the web server program (HTTPD), the job stream file which runs the HTTPD program (JHTTPD), a set of configuration files for enabling Apache features, the htdocs directory containing HTML pages, the logs directory, and the cgi-bin directory. Apache also comes with a full, on-line manual set. • HTTPD is the Apache web server program.
Internet and Interoperability Apache for MPE/iX 6.5 Prepare Your HP 3000 for Network Access Before your HP 3000 can act as a web server, it must be available for network access via TCP/IP. In preparation, you should: • Configure TCP/IP on your system • Have a domain name associated with your system’s IP address Apache communicates on the network using the HTTP Hypertext Transfer Protocol which, in turn, uses TCP/IP. Using NMMGR, configure your system’s IP address and subnet mask.
Internet and Interoperability Apache for MPE/iX 6.5 shell>/APACHE/PUB/HTTPD -t Configuration Recommendation We strongly recommend setting KeepAlive to off in http.conf. With KeepAlive on, sockets may eventually be used up. When this happens, Apache will appear to be hung and will need to be restarted. Edit the JHTTPD Job Stream File The JHTTPD Job Stream File is used to run the HTTPD web server program in standalone mode with your local timezone: !job jhttpd,www.
Internet and Interoperability Apache for MPE/iX 6.5 Verify that Apache is Running There are a number of ways to verify if the Apache web server is running or, if it is not, to isolate how far the startup process progressed. After streaming the JHTTPD file, use :SHOWJOB to view the running job: JOBNUM STATE IPRI JIN #J16 EXEC JLIST 10S LP INTRODUCED JOB NAME TUE 10:27A JHTTPD,WWW.APACHE Another method is to check server status using either ps from the POSIX shell or using :SHOWPROC at the CI.
Internet and Interoperability Apache for MPE/iX 6.5 3. Trying to telnet to Apache’s port (port 80 if you have not modified the port directive set in the httpd.conf.sample file)If you cannot telnet to Apache’s port, then your problem is not with the web server. You are not yet reaching your HP 3000 box. A successful telnet connection should look something like, telnet yourserver.com 80 Trying... Connected to yourserver.com. Escape character is ‘^]’.
Internet and Interoperability Apache for MPE/iX 6.5 mod_env.c mod_log_config.c mod_log_agent.c mod_log_referer.c mod_mime_magic.c mod_mime.c mod_negotiation.c mod_status.c mod_info.c mod_include.c mod_autoindex.c mod_dir.c mod_cgi.c mod_asis.c mod_imap.c mod_actions.c mod_speling.c mod_userdir.c mod_alias.c mod_access.c mod_auth.c mod_auth_anon.c mod_cern_meta.c mod_expires.c mod_headers.c mod_usertrack.c mod_unique_id.c mod_setenvif.
Internet and Interoperability Introducing LDAP C-SDK/iX Introducing LDAP C-SDK/iX by Joanne Gong Commercial Systems Division Lightweight Directory Access Protocol (LDAP) is an open standard which defines the communication protocol between an LDAP client and an LDAP server. LDAP C-SDK/iX is a set of client APIs in C language for MPE/iX applications to access X.500-based network directories. LDAP C-SDK/iX enables internet directory accesses from HP 3000.
Internet and Interoperability MPE/IX Software Developer’s Kit (SDK) for Java, Version 1.2.2 MPE/IX Software Developer’s Kit (SDK) for Java, Version 1.2.2 by Mike Yawn, Commercial Systems Division A major new release of Java, Version 1.2.2, is included with this release of MPE/iX. This article briefly describes some of the changes. One change is the name; the former Java Developer’s Kit (JDK) is now called the Software Developer’s Kit (SDK) for Java. You will also find in the literature that SDK 1.
Internet and Interoperability MPE/IX Software Developer’s Kit (SDK) for Java, Version 1.2.2 /usr/local/java/latest/bin as the location for executable programs. Further subdivision has happened in the libraries hierarchy; there is now a /classic subdirectory where the executable library (XL) containing most JVM functionality resides. This is in preparation for supporting multiple Java Virtual Machines running in the same directory hierarchy in a future release.
Internet and Interoperability HP Driver for JDBC HP Driver for JDBC Shu-Feng Wei Commercial Systems Division Java Database Connectivity (JDBC) is a Java API that enables development of Java applications and applets with a wide range of relational databases. It consists of a set of classes and interfaces written in Java. JDBC allows developers to write database applications using a standard, pure Java API.
Internet and Interoperability HP Driver for JDBC HP JDBC Components There are three components supplied with the HP JDBC product, the JDBC Driver, the JDBC Monitor, and the JDBC Server. The user is responsible for writing a Java application or applet that uses JDBC on the client, as well as providing the ALLBASE/SQL or IMAGE/SQL database on the server. • The HP Driver for JDBC is a set of Java classes that implement the java.sql.
Internet and Interoperability HP Driver for JDBC MPE/iX Server Requirements The HP JDBC Server components require MPE/iX version 6.0 or greater. MPE/iX components are only required if your JDBC Server platform is the MPE/iX operating system. ALLBASE/SQL or IMAGE/SQL Requirements The HP JDBC Server components require an ALLBASE/SQL G3.01 or IMAGE/SQL G3.00 or greater.
Internet and Interoperability HP Driver for JDBC Extracting the HP Driver for JDBC Class Files The HP Driver for JDBC class files must be installed in your Java class path so that the Java compiler and the Java class loader can find them. Example on the Win32 Platform CLASSPATH=C:\JDK1.1.4\LIB;. You would then install the HP Driver for JDBC class files in the directory: C:\JDK1.1.4\LIB\ Example on HP 3000 CLASSPATH=/usr/local/java/latest/lib:.
Internet and Interoperability HP Driver for JDBC The next set of lines are the LOGGING levels used to determine the type of information to be logged to the server log file. The meanings of the various logging levels are discussed in the Troubleshooting Section, under “Server Logging” of the HP Driver for JDBC User’s Manual. The server configuration file is read in each time a new server process is started.
Internet and Interoperability HP Driver for JDBC The only time the monitor should ever be brought down is to install a newer version. In this case, use the JSTOPMON stream job or ABORTJOB command to kill the monitor process. The ABORTJOB command to shut down the monitor is: : ABORTJOB #JXX where XX is the job number. To restart the monitor after it was shut down or accidentally terminated, use the JSTRTMON stream job to start it up. : STREAM JSTRTMON.JDBC.
Internet and Interoperability HP Driver for JDBC It shows how to use a dialog box to obtain user input, and also formats the result set output a lot better. The first step to using the sample client is to build it by compiling the Java source code. Normally, you would do this by using the Java compiler command (the command you use may be different, depending on your JDK): NOTE If you are using JDK1.2.1 or later, add the following line in SampleClient.java before the call to class.forName: DriveManager.
Internet and Interoperability HP Driver for JDBC uid Server host userid that is authorized to access the database. pwd Server host password that matches the user id provided above. trace Optional trace values separated by the vertical bar “|” character. For more information on tracing, see the Troubleshooting section. NOTE This connection method may result in the user name and password being logged in various places, as URLs are commonly logged on various web servers and proxy servers.
Internet and Interoperability HP Driver for JDBC indicates the data type mapping. Table 5-1. Data Type Mapping JDBC DATA TYPES (vertical) ALLBASE/SQL DATA TYPES (horizontal) SMALLINT (16-bits) INTEGER (32-bits) T I N Y I N T S M A L L I N T I N T E G E R B I G I N T R E A L F L O A T D O U B L E B I T C H A R V A R C H A R L O N G V A R C H A R B I N A R Y V A R B I N A R Y L O N G V A R B I N A R Y D A T E T I M E T I M E S T A M P X X FLOAT(1...24) X FLOAT(25...
Internet and Interoperability HP Driver for JDBC rounding, are denoted by a lowercase letter “x” in the conversion grid. Table 5-2.
Internet and Interoperability HP Driver for JDBC could result in a java.lang.NumberFormatException being shown when the conversion is performed. Again, the application developer should take the necessary precautions. Unsupported ALLBASE/SQL Data Types The ALLBASE LONG BINARY, and LONG VARBINARY data types are currently not supported by the HP Driver for JDBC. Acceptable SQL Syntax The HP JDBC Server accepts either ODBC SQL statement syntax or ALLBASE/SQL statement syntax.
Internet and Interoperability HP Driver for JDBC Stored Procedures The HP Driver for JDBC supports the following types of ALLBASE/SQL stored procedures through the java.sql.CallableStatement interface: 1. Procedures that return one or more result sets. 2. Procedures that take one or more input arguments. 3. Procedures that return one or more output arguments. 4. Procedures that have a return status value.
Internet and Interoperability HP Driver for JDBC OBJECT Include the object hash code in the format HHHHHHHH on all tracing output lines where HHHHHHHH is the eight digit hexadecimal value of the hash code. This information appears in the first column of the tracing output. THREAD Include the executing thread name on all tracing output lines. This information appears as the fourth column of the tracing output. DEBUG Trace debugging statements from the driver.
Internet and Interoperability HP Driver for JDBC affect performance. TIMESTAMP This causes each log entry to be prefaced by a timestamp of the form HH:MM:SS.mmm. WARNING Turns on logging of warning messages generated by the Server. ERROR Turns on logging of error messages generated by the Server. FATAL This is the same as specifying INFO, WARNING, and ERROR. DEBUG Turns on logging of a lot of debugging messages. This should only be done at the request of support personnel.
Internet and Interoperability HP Driver for JDBC 162 Chapter 5
Announcing a Post 6.5 Release Patch 6 Announcing a Post 6.5 Release Patch This chapter provides the following article about a software patch (B.G$.01) which is being released separate from and following the 6.5 base release. The software patch is not part of the 6.5 base release, but will be available shortly after the 6.5 release. This article provides information regarding mandatory changes which you must make to your system if you decide to install this patch.
Announcing a Post 6.5 Release Patch IMAGE/SQL Date Mapping Enhancement IMAGE/SQL Date Mapping Enhancement CAUTION The DATE MAPPING enhancement for IMAGE/SQL will be available in the first IMAGE/SQL patch released on MPE/iX version 6.5. This enhancement requires migration of the ATCINFO file since the ATCINFO file format has been changed to keep track of additional date related information. The IMAGE/SQL version number for 6.5 release is B.G3.01.
Announcing a Post 6.5 Release Patch IMAGE/SQL Date Mapping Enhancement SP(LIT) Divides a large mapped column into two or more smaller columns. Syntax SP[LIT] MappedTable.MappedColumn INTO NewMappedColumn:SourceType [FORMAT=FormatType[,lowvalue[,highvalue]]] [:MappedType [SIGNED ] [UNSIGNED]] [,...] If MappedType is 'DATE', then FORMAT must be specified. Example (i) SPLIT TABLE1.COLUMN5 INTO NEWCOLUMN1:I4:CHAR(8),& NEWCOLUMN2:X20,& NEWCOLUMN3:K3:DECIMAL(15,0) (ii) SPLIT TABLE2.
Announcing a Post 6.5 Release Patch IMAGE/SQL Date Mapping Enhancement U[PDATE] TYPE Updates data type mapping information for a specified TurboIMAGE/iX data type or a specified Mapped Column. Syntax U[PDATE] TYPE {SourceType IN {* } {MappedTable} [FORMAT=FormatType[,lowvalue[,highvalue]]]} {IN MappedTable.Col [FORMAT=FormatType[,lowvalue[,highvalue]]]} [TO NewMappedType [SIGNED ] [UNSIGNED]] If NewMappedType is 'DATE', then FORMAT must be specified.
Announcing a Post 6.5 Release Patch IMAGE/SQL Date Mapping Enhancement Format(TI)Type StorageType #Bytes Explanation Format (TI) Storage Type Bytes Explanation DT1 (I4,J4,K4) longint 8 MPE time-stamp (microseconds from 1970-01-01) DT2 (I2,J2,K2) integer 4 Upper 2 bytes: year next byte: month of year DT3 (I2,J2,K2) integer 4 Upper 2 bytes: year bottom 2 bytes: day of year DT4 (I2,J2,K2) integer 4 Upper 23 bits: # years from 1900 bottom 9 bits: day of the year.
Announcing a Post 6.5 Release Patch IMAGE/SQL Date Mapping Enhancement invalid value will be displayed as '9901-12-31' There will be no default values for lowvalue and highvalue. If lowvalue and/or highvalue are not provided, then the code checking for lowvalue/highvalue will not be exercised. 3. For integer DT types (DT1 - DT18), the lowvalue and the highvalue must be set to integer values. 4.
Announcing a Post 6.5 Release Patch IMAGE/SQL Date Mapping Enhancement : run imagesql.pub.sys > dbe yourdbe > migrate 4. How do you know that your ATCINFO file needs migration? (1) : imagesql >> dbe mydbe >> base yourdb >> display turbodb Incompatible ATCINFO file version number, migration is needed (ATCERR 2101). (2) isql=> connect to 'mydbe'; ATCINFO file contains incompatible version number, migration is needed. (DBERR 13516) 5.
Announcing a Post 6.
Product List—How to Order 7 Product List—How to Order You can order subsystem products through your HP Sales Representatives. • To order products in the U.S., call HP Computer Organization Order Fulfillment Center at 1-800-386-1117 option 3. • To order learning products manuals in the U.S., call HP Parts Director Ordering at 1-800-227-8164. • To order products and/or manuals in countries outside the U.S., call your local Trade Parts Sales Organization.
Product List—How to Order 172 Chapter 7
Product Release History Product Changes by Releases 8 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.5 Release.. 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.
Product Release History Product Changes by Releases Table 8-1. MPE/iX Product Releases Release SUBSYS Date Code Product(s) Introduced/Added 5.5 Exp. 2 C.55.02 R3715 Express 2 based on Release 5.5 CI enhancements VPlus enhancements DTS/TIO new functionality 5.5 Exp. 3 C.55.03 R3732 Express 3 based on Release 5.
Product Release History Product Changes by Releases Table 8-1. MPE/iX Product Releases Release SUBSYS 5.5 PP6 C.55.06 5.5 Exp. 7 C.55.07 Date Code Product(s) Introduced/Added PowerPatch 6 based on Release 5.5 Bug Fixes only R3910 Express 7 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, 6.0 or 6.5) and the update "UU" field of the V.UU.FF is changed.
Product Release History Supported Releases Table 8-2. Supported System Release Matrix Supported Releases Supported Systems Support Termination Date Release 5.5 (C.55.xx) 920*, 922*, 932*, 948*, 955**, 958*, 960**, 6 months following next Mainline release after 6.
Product Release History Supported Releases Table 8-2. Supported System Release Matrix Supported Releases Supported Systems Support Termination Date Release 6.0 (60.xx) 920*, 922*, 932*, 948*, 955**, 958*, 960**, 6 months following next Mainline release after 6.
Product Release History Supported Releases Table 8-2. Supported System Release Matrix Supported Releases Supported Systems Support Termination Date Release 6.5 (65.xx) 9x7, 9x7LX, 9x7RX, 9x7SX, 6 months following next Mainline release after 7.
Product Release History Supported Releases 180 Chapter 8
Catalog of User Documentation 9 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 New or Updated Manuals,” which lists all manuals that have been introduced or changed since the MPE/iX 6.0 Release. • “Manual Collections,” which lists manuals by collections in alphabetical order. For detailed information on a particular manual or manual collection, refer to the MPE/iX Documentation Guide.
Catalog of User Documentation MPE/iX 6.5 New or Updated Manuals MPE/iX 6.5 New or Updated Manuals This section lists customer manuals introduced or updated for MPE/iX 6.5. Table 9-1. MPE/iX 6.5 New or Updated Manuals Manual Title Part No. Latest Edition Accessing Files Programmer’s Guide 32650-90885 3/00 ALLBASE/SQL Reference Manual 36216-90216 3/00 Configuring and Managing MPE/iX Internet Services 32650-90891 3/00 Communicator 3000 MPE/iX Release 6.
Catalog of User Documentation MPE/iX 6.5 New or Updated Manuals Table 9-1. MPE/iX 6.5 New or Updated Manuals Manual Title Part No.
Catalog of User Documentation Manual Collections Manual Collections Table 9-2. Manual Collections Manual Title Order Part Number Part Number Latest Edition How Available? HC = Hardcopy only P = PDF CD B = PDF & Inst. Info View on the WEB* Communicators and System Software Maintenance Manuals Communicator 3000 (6.5) 30216-90291 30216-90291 Mar-00 B y Communicator 3000 (PowerPatch 1 based on 6.0) 30216-90286 30216-90286 Aug-99 B y Communicator 3000 (6.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2. Manual Collections Manual Title Order Part Number Part Number Latest Edition How Available? VISTA Plus for MPE Administrators Guide B3933-90004 B3933-90004 Jun-97 P .pdf VISTA Plus for MPE User’s Guide B3933-90003 B3933-90003 Jun-97 P .pdf VISTA Release Notes Version A.07 B3933-90006 B3933-90006 Jun-97 P .pdf HC = Hardcopy only P = PDF CD B = PDF & Inst.
Catalog of User Documentation Manual Collections Table 9-2. Manual Collections Manual Title Order Part Number Part Number Latest Edition How Available? Site Preparation and Requirements Guide (99X Family) - A1809-90002 May-97 P .pdf System Memory Upgrade Guide (9X9KS) - A2375-90009 Jan-98 P .pdf System Upgrade Installation Guide (CS 99X Family) (990/992 to 996) - A3310-90002 May-97 P .pdf System Upgrade Installation Guide (CS 99X Family) (991/995 to 996) - A3310-90001 May-97 P .
Catalog of User Documentation Manual Collections Table 9-2.
Catalog of User Documentation Manual Collections Table 9-2.
Index Numerics 12H configuration, 115 A ABORTJOB command, 153 acceptable SQL, 158 AIF:OS error messages, 56 AIFFILEGGET, 39, 40, 55 AIFFILEGPUT, 40, 55 AIFFILELGET, 39, 55 AIFFILELPUT, 39, 55 AIFJSGET, 57 AIFSYSWIDEGET, 57 ALLBASE/SQL database, 148 ALTJOB, 66, 71 Apache components, 139 configuring, 140 documentation, 144 error logging, 143 features, 138 starting, 139 stopping, 143 verify activity, 142 Apache for MPE/iX, 138 applet, 149 Architected interfaces, 39 archive file, 150 B Backdating, 53 B-TREE, 1
Index Java archive (JAR), 150 UNIX tape archive (TAR), 150 Windows ZIP (ZIP), 150 Driver Manager, 154 dropped connections, 153 dstat, 63 DSTs, 64 E Electronic Support Center, 23 Enterprise Management Solution, 88 ENVIRONMENT VARIABLE, 153 expanded B-tree, 132 extracting driver class files, 151 Win32 Platform, 151 extracting file, 150 F fast search, 101 Fast search on tapes, 101 FFILEINFO, 38 FGETINFO, 38 File Open, 135 file open, 132 FLABELINFO, 37, 38, 47 floating-point value, 157 H HiPRI, 66 HP Driver fo
Index L Large file 32-bit interger overflow, 37 AIF:OS impact, 39 backdating, 53 CI changes, 41 compatibility, 35 data access, 36 FILE command, 44 functionality, 34 IMAGE database, 53 intrinsic changes, 46, 47 LISTFILE command, 45 space ID boundary, 36 STORE/RESTORE impact, 52 support, 34 user-mapped access, 35 utility and subsys support, 53 Large files, 34 Large transactions limitations, 130 with IMAGE, 126 with transaction manager, 127 with TurboIMAGE, 128 LDAP C-SDK/iX, 145 learning products ordering, 1
Index non-platform, 176 platform, 176 product history, 173 supported, 176 requirements, 149 RUN command, 74 S sample client, 153, 154 Security messages, 96 SELECT statement, 158 servcfg, 151 Server Components MPE/iX, 150 server components, 150 server configuration file, 160 server log file, 152 Server Logging, 152 server logging, 160 server logging levels, 160 Server Requirements ALLBASE/SQL, 150 HP-UX, 149 IMAGE/SQL, 150 MPE/iX, 150 SHOWJOB, 73 shutdown, 152 simple client, 153 SimpleClient, 153 space char
