DOCSLIB.ORG

BN-0011-01: Installation and Use of T4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
BN-0011-01: Installation and Use of T4 INSTALLING AND USING T4 TECHNICAL AND INFORMATIONAL VERSION 1.01 INSTALLING AND USING T4 Installing and Using T4 BN-00011-01 (14-JUL-2017) © 2017 AVT/Vere vtAlpha and vtVAX are marketed jointly by AVT and Vere Technologies LLC BN-00011-01 (6/2017) Page 2 of 10 INSTALLING AND USING T4 Table of Contents 1. Introduction ......................................................................................................................... 4 2. Installing T4 ......................................................................................................................... 4 2.1. The classic method ................................................................................................... 4 2.2. The disk method ........................................................................................................ 5 2.3. The saveset method .................................................................................................. 6 3. Installing TLViz ................................................................................................................... 7 3.1. Download and installing ............................................................................................ 7 4. Collecting T4 data ............................................................................................................... 7 4.1. Start collecting ........................................................................................................... 7 4.2. Stop collecting ........................................................................................................... 8 5. Viewing and analysing data ............................................................................................... 8 5.1. Copy and unzip the collected data ............................................................................ 9 5.2. Use TLViz .................................................................................................................. 9 5.3. Examples and tips ..................................................................................................... 9 BN-00011-01 (6/2017) Page 3 of 10 INSTALLING AND USING T4 1. Introduction This document is about installing and using T4. And what is T4? Here’s an explanatory snippet from the official HPE website: “T4 stands for Total Timeline Tracking Tool. It runs on HP OpenVMS systems with the purpose of capturing and consolidating important OpenVMS performance statistics. Pulling from several (currently seven) independent yet cooperating sources, T4 lets you create a relatively compact composite timeline view of the day-to-day performance of each important OpenVMS node.” The collected T4 data can be viewed with TLViz (Time Line Visualizer), a graphical viewer for the Microsoft Windows platform. We made this document to make it easier for users to gain insight into the behavior of their OpenVMS systems, and to possibly relieve performance bottlenecks. NOTE: All mentioned software is free to use and can be downloaded via the HPE website (see the links in the next chapters). 2. Installing T4 In this chapter, we describe several ways to install T4 on your OpenVMS system(s). The first, “the classic way”, is the standard way software on OpenVMS Alpha is installed. The software is downloaded from a vendor, and installed via the “$product” command. It’s fast, easy and reliable. We added two more easy, fast and just as reliable options. The second way is connecting a “ready- to-go” disk with T4 already installed. The third is restoring a backup saveset which “installs” the T4 without using the “product” command. These two alternative options provide you with a way to create an isolated (and possibly temporary) T4 environment in a very quick and easy way. All three options have the same end result. Depending on your company policies or technical limitations, you can choose an installation method that suits you best. NOTE: The “disk” and “saveset” method create a specific batch queue (T4$BATCH) where the T4 procedure will run. 2.1. The classic method The standard method of installing software products on OpenVMS via the “product” command. The downside is that, during the installation, you specifically have to input an installation disk (otherwise it will default to the system disk). And you have to setup your system so the collected data isn’t stored on the system disk. These are not complex tasks for an experienced systems manager, but the other two methods are just as easy to install, without the need to modify the T4 setup. And these installations are very easy to “remove” from your system. Here are the instructions for this installation method. Download the package (for free) from the HP site (ftp://ftp.hp.com/pub/openvms/t4/T4_T44_KIT.ZIP). The installation is a standard “product” install on OpenVMS. 1. Unzip the file (on Windows or OpenVMS), and copy the extracted files to an OpenVMS disk. 2. If necessary, fix the file-attribute settings of the PCSI file with this command a. $ set file/att=(rfm:fix,lrl:512,mrs:512,org:seq,rat:none) HP-VMS-T4-T0404-- 1.PCSI$COMPRESSED BN-00011-01 (6/2017) Page 4 of 10 INSTALLING AND USING T4 3. Go to the location where the extracted files are located and execute the product command a. $ product install T4 It will install to SYS$SYSDEVICE:[VMS$COMMON.T4$SYS] Or b. $ product install T4/DESTINATION=disk$somewhere:[dir.tree] 4. Now create a storage area where the T4 collected data will be stored. Make sure you have sufficient free disk space (at least 500 MB). And do not point to a location on your system disk! a. $ create/dir disk$somewhere:[T4DATA] 5. Create the necessary logicals. a. $ DEFINE /SYSTEM /EXEC T4$SYS SYS$SYSDEVICE:[VMS$COMMON.T4$SYS] b. $ DEFINE /SYSTEM /EXEC T4$DATA disk$somewhere:[ T4DATA] and make sure to place these commands in one of your startup files! 2.2. The disk method This method involves connecting the “ready-to-go” disk where T4 is already installed.. On this disk, two versions of T4 are available. Version 4.0 for OpenVMS 7.3-1, and version 4.4 from OpenVMS 7.3-2 and higher. The main advantage this installation offers is that no files are copied to the system disk or any other disk on your system (unless you explicitly tell T4 to do so). The T4DISK contains all the necessary files and all the data it collects will be placed on this disk. So there will be no “contamination” of your system. Simply adding or removing the T4DISK from your “mount- procedure” adds or removes T4 from the system. The disadvantage of this method is that you need to restart the emulator to connect the T4DISK. Use the “saveset” method (see the next chapter) to achieve the same results as the “disk” method, without the need to restart the emulator. Follow the installation procedure described here. If you downloaded the “disk-package” (T4DISK.ZIP) from our site, take the following steps: 1. Unzip the T4DISK.ZIP file, and copy the newly extracted disk to a location which is available to the emulator (where your other disks are located) 2. Attach the new disk to the OpenVMS system in your emulator-configuration 3. Restart the emulator (shutdown the OpenVMS system first) for the OpenVMS system to be able to see and use the new disk 4. Mount the new disk on OpenVMS after rebooting 5. Setup T4 via the following procedure a. $ @<newdisk>:[T4SETUP]T4SETUP <T4-version> <diskname> i. $ @DKA400:[T4SETUP]T4SETUP 40 DKA400 ! T4 version 4.0 OR ii. $ @DKA400:[T4SETUP]T4SETUP 44 DKA400 ! T4 version 4.4 BN-00011-01 (6/2017) Page 5 of 10 INSTALLING AND USING T4 6. Next, to make sure T4 is available after a reboot, put the following command in the procedure where you mount your disks (DKA400 is used in these examples) i. $ mount/system DKA400 T4DISK T4DISK and place the command you used to setup T4 in one of your system startup files after the T4DISK is mounted ii. $ @DKA400:[T4SETUP]T4SETUP 44 DKA400 NOTE: Pay attention to the output when starting the T4SETUP procedure. If there are errors or insufficient process quotas that prevent T4 from running, it will say so during the setup. 2.3. The saveset method The advantage of the saveset method (opposed to the “disk” method) is that you do not need to restart/reboot the emulator to connect the T4DISK. And you can choose to install the T4 package to any disk you like. In other aspects it has the same advantages as the “disk” method. You can install it on a free/isolated disk you have available and your system disk won’t be touched. If you downloaded the “T4 saveset-package” (T4KITSAVESET.ZIP) from our site, take the following steps to install T4: (depending on the VMS version, for VMS 7.3-1 you need to install T4 version 4.0; for VMS 7.3-2 and higher use T4 version 4.4; both versions are included in the package) First unzip the file T4KITSAVESET.ZIP. 1. FTP the zip file to the OpenVMS system you plan to use for collecting data (or unzip on a Windows system and ftp the extracted files) 2. Unzip the file a. $ unzip T4KITSAVESET.ZIP This will unzip 5 files, i. T4KIT40.BCK ii. T4KIT44.BCK iii. T4INSTALL.COM iv. T4STARTUP.COM v. FIX_SAVESET.COM 3. Go to the directory where you unzipped the files to, and restore the original file attributes of the savesets a. $ @FIX_SAVESET T4KIT40.BCK b. $ @ FIX_SAVESET T4KIT44.BCK 4. Now you can install the T4 product via the T4INSTALL.COM procedure (in this example to disk DKA500) a. $ @T4INSTALL 40 DKA500 ! for VMS 7.3-1 or b. $ @T4INSTALL 44 DKA500 ! for VMS 7.3-2 and higher BN-00011-01 (6/2017) Page 6 of 10 INSTALLING AND USING T4 This will install the T4
Load more

Recommended publications
  • Openvms Record Management Services Reference Manual
    OpenVMS Record Management Services Reference Manual Order Number: AA-PV6RD-TK April 2001 This reference manual contains general information intended for use in any OpenVMS programming language, as well as specific information on writing programs that use OpenVMS Record Management Services (OpenVMS RMS). Revision/Update Information: This manual supersedes the OpenVMS Record Management Services Reference Manual, OpenVMS Alpha Version 7.2 and OpenVMS VAX Version 7.2 Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3 Compaq Computer Corporation Houston, Texas © 2001 Compaq Computer Corporation Compaq, AlphaServer, VAX, VMS, the Compaq logo Registered in U.S. Patent and Trademark Office. Alpha, PATHWORKS, DECnet, DEC, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. in the United States and other countries. UNIX and X/Open are trademarks of The Open Group in the United States and other countries. All other product names mentioned herein may be the trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. Compaq shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.
    [Show full text]
  • Oracle Database Installation Guide 10G Release 2 (10.2)
    Oracle®[1] Database Installation Guide 11g Release 2 (11.2) for HP OpenVMS Itanium E56668-01 June 2015 Oracle Database Installation Guide, 11g Release 2 (11.2) for HP OpenVMS Itanium E56668-01 Copyright © 2008, 2015, Oracle and/or its affiliates. All rights reserved. Primary Author: Nisha Sridhar Contributors: Dave Hayter, Gary Huffman, Marc Noel, Chris Schuetz, David Miller, Kevin Duffy, Steve Holck, Grant Hayden, Gary Tate This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Software Product Description and Quickspecs
    VSI OpenVMS Alpha Version 8.4-2L2 Operating System DO-DVASPQ-01A Software Product Description and QuickSpecs PRODUCT NAME: VSI OpenVMS Alpha Version 8.4-2L2 DO-DVASPQ-01A This SPD and QuickSpecs describes the VSI OpenVMS Alpha Performance Release Operating System software, Version 8.4-2L2 (hereafter referred to as VSI OpenVMS Alpha V8.4-2L2). DESCRIPTION OpenVMS is a general purpose, multiuser operating system that runs in both production and development environments. VSI OpenVMS Alpha Version 8.4-2L2 is the latest release of the OpenVMS Alpha computing environment by VMS Software, Inc (VSI). VSI OpenVMS Alpha V8.4-2L2 is compiled to take advantage of architectural features such as byte and word memory reference instructions, and floating-point improvements, which are available only in HPE AlphaServer EV6 or later processors. This optimized release improves performance by taking advantage of faster hardware-based instructions that were previously emulated in software. NOTE: VSI OpenVMS Alpha V8.4-2L2 does not work on, and is not supported on, HPE AlphaServer pre-EV6 systems. OpenVMS Alpha supports HPE’s AlphaServer series computers. OpenVMS software supports industry standards, facilitating application portability and interoperability. OpenVMS provides symmetric multiprocessing (SMP) support for multiprocessing systems. The OpenVMS operating system can be tuned to perform well in a wide variety of environments. This includes combinations of compute-intensive, I/O-intensive, client/server, real-time, and other environments. Actual system performance depends on the type of computer, available physical memory, and the number and type of active disk and tape drives. The OpenVMS operating system has well-integrated networking, distributed computing, client/server, windowing, multi-processing, and authentication capabilities.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • Openvms Security
    OpenVMS Security Presented by Paul Williams PARSEC Group 999 18th Street, Suite 1725 Denver, CO 80202 www.parsec.com | 888-4-PARSEC To Download this Presentation, please visit: http://www.parsec.com/public/openvmssecurity.pdf To E-mail Paul [email protected] www.parsec.com | 888-4-PARSEC Outline • OpenVMS Security Design • Physical Security • Object Security • UIC/ACL Security • User Access • Break-in Detection • Network and Internet Considerations • Encrypted Network Communication • Kerberos • Secure Socket Layer (SSL) Goals • Discuss the important points and consideration of OpenVMS Security • Concentrate on the mechanics and mechanisms of OpenVMS features. • Show how OpenVMS is one of the most secure operating systems on the market. OpenVMS Security Design • Security was designed into OpenVMS since V1.0 • Many different levels of security in OpenVMS Physical Security Object Security User Management Network Security • Has never had a virus Physical Security • System • System Console • Storage devices and media System Disk Data and Database Volumes Backups • Network devices and media Physical Security: System • Increase system reliability through restricted access Prevent intentional tampering and outage Prevent outage due to accidents • Prevent Front Panel Access Halts Reset/initializations Power switch/source Power on action settings (VAX) switch Physical Security: Console • Can be a big security hole for OpenVMS Anyone with physical access to the console can break into OpenVMS buy getting into the SYSBOOT utility. Then OpenVMS can be broken into: Buy redirecting startup Buy changing system parameters Physical Security: Getting to SYSBOOT on the Integrity Console Example • On the Integrity shutdown to the EFI Boot Manager and select the EFI Shell and create a alias.
    [Show full text]
  • Getting Even More Grip on Your Security with Pointsecure Or
    OpenVMS and Security getting even more grip on your security with Pointsecure or NDC Gerrit Woertman VSI Professional Services Alliance member VSI OpenVMS trainer EMEA & VSI OpenVMS Ambassador [email protected] www.vmsconsultancy.com Agenda • OpenVMS and Security • EU security laws to report security issues • Non‐HPE/VSI Security packages • Pointsecure – PointAudit – System Detective • Networking Dynamics Corporation (NDC) – Peek & Spy – KEY Capture – Assassin • Questions OpenVMS and Security ‐ 1 • OpenVMS – secure by design • No viruses • One of the first to become US DoD C2‐rating • Declared “Cool and Unhackable” at 2001 DefCon9 as described in 4AA0‐2896ENW.pdf (HP, 11/2005) Alpha OpenVMS with the help of Pointsecure System Detective OpenVMS and Security ‐ 2 • OpenVMS has got optional security solutions – OpenSSL (Secure Socket Layer) https://www.openssl.org/ – Common Data Security Architecture (CDSA) – Kerberos • Everything fine? Seems so, but there is still need for more and better implementation – On VSI’s research list OpenVMS and Security – 3 • OpenVMS ‐ Linux – Windows • With 100% OpenVMS no problems – fine – That’s not real; today’s softwarestacks complex – Splendid isolation? • OpenSource – is that safe? ? OpenVMS and Security – 4 • From http://vmssoftware.com/products.html Unmatched Security Compare OpenVMS' security vulnerability record against other operating systems at CVE Details: http://www.cvedetails.com. The following are direct links to reports for OpenVMS, Linux and Windows: • OpenVMS http://www.cvedetails.com/product/4990/HP‐Openvms.html?vendor_id=10
    [Show full text]
  • Oracle Rdb7™ Guide to Using the Oracle SQL/Services™ Client API
    Oracle Rdb7™ Guide to Using the Oracle SQL/Services™ Client API Release 7.0 Part No. A41981-1 ® Guide to Using the Oracle SQL/Services Client API Release 7.0 Part No. A41981-1 Copyright © 1993, 1996, Oracle Corporation. All rights reserved. This software contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error free. Restricted Rights Legend Programs delivered subject to the DOD FAR Supplement are ’commercial computer software’ and use, duplication and disclosure of the programs shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are ’restricted computer software’ and use, duplication and disclosure of the programs shall be subject to the restrictions in FAR 52.227-14, Rights in Data—General, including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065. The programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee’s responsibility to take all appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications if the programs are used for such purposes, and Oracle disclaims liability for any damages caused by such use of the programs.
    [Show full text]
  • Guide to Openvms Performance Management
    Guide to OpenVMS Performance Management Order Number: AA–PV5XA–TE May 1993 This manual is a conceptual and tutorial guide for experienced users responsible for optimizing performance on OpenVMS systems. Revision/Update Information: This manual supersedes the Guide to VMS Performance Management, Version 5.2. Software Version: OpenVMS VAX Version 6.0 Digital Equipment Corporation Maynard, Massachusetts May 1993 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1993. All rights reserved. The postpaid Reader’s Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ACMS, ALL–IN–1, Bookreader, CI, DBMS, DECnet, DECwindows, Digital, MicroVAX, OpenVMS, PDP–11, VAX, VAXcluster, VAX DOCUMENT, VMS, and the DIGITAL logo. All other trademarks and registered trademarks are the property of their respective holders. ZK4521 This document was prepared using VAX DOCUMENT Version 2.1. Contents Preface ............................................................ ix 1 Introduction to Performance Management 1.1 Knowing Your Workload ....................................... 1–2 1.1.1 Workload Management .................................... 1–3 1.1.2 Workload Distribution ..................................... 1–4 1.1.3 Code Sharing ............................................ 1–4 1.2 Evaluating User Complaints .
    [Show full text]
  • GSI OPERATING SOFTWARE MIGRATION Openvms to Linux
    MOX02 Proceedings of PCaPAC08, Ljubljana, Slovenia GSI OPERATING SOFTWARE MIGRATION OpenVMS TO Linux R. Huhmann, G. Fr¨ohlich, S. J¨ulicher, V. RW Schaa, GSI, Darmstadt, Germany Abstract TECHNICAL ASPECTS This section covers main aspects of porting VMS spe- The current operating software at GSI has been devel- cific Fortran software to Linux. Due to the limited size of oped over a period of more than two decades using Open- this paper it is impossible to mention all aspects or to go in VMS now on Alpha-Workstations. Parts of this complex much detail. software will have to be integrated within the control sys- tem of the new FAIR accelerator. To ease future mainte- nance a migration to Linux is considered a precondition. DEC Fortran Extensions For porting to Linux a set of libraries and tools have been DEC Fortran was established as a quasi standard which developed covering the necessary OpenVMS (referred to as exceeds and improves the Fortran77 specifications. It cov- VMS in the paper) system functionality. The interoperabil- ers a lot of compiler directives and language extensions to ity with FAIR controls applications is achieved by adding increase possibilities for Fortran programmers. An exam- a simple but generic middle-ware interface to access the ple is the type STRUCTURE to create composed data objects ported software in a service-like manner from modern Java like struct in C. Other important examples are the com- applications. piler directives %REF, %LOC, %VAL which enable the For- tran programmer to use pointers. Luckily most of the ex- tensions are supported by main Fortran compiler manufac- GENERAL ASPECTS turers.
    [Show full text]
  • VSI Openvms Version 8.4-1H1 Installation and Upgrade Manual
    VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual VSI OpenVMS Version 8.4-1H1 Installation and Upgrade Manual: Software Version: VSI OpenVMS Version 8.4-1H1 for HP Integrity Servers Publication date 5-May-2015 - Release Version 1.0 Copyright © 2015 VMS Software, Inc., (VSI), Bolton Massachusetts, USA Legal Notice Confidential computer software. Valid license from VSI required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for VSI products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. VSI shall not be liable for technical or editorial errors or omissions contained herein. HP, HP Integrity, HP Alpha, Proliant and Superdome are trademarks or registered trademarks of Hewlett Packard Development Company, L.P. Intel, Itanium and IA64 are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java, the coffee cup logo, and all Java based marks are trademarks or registered trademarks of Oracle Corporation in the United States or other countries. Kerberos is a trademark of the Massachusetts Institute of Technology. Microsoft, Windows, Windows-NT and Microsoft XP are U.S. registered trademarks of Microsoft Corporation. Microsoft Vista is either a registered trademark or trademark of Microsoft Corporation in the United States and/or other countries.
    [Show full text]
  • Unix Portability Changes in V8.4
    UNIX PORTABILITY CHANGES IN V8.4 Rupesh Shantamurty OpenVMS Engineering 1 © Copyright 2010 Hewlett-Packard Development Company, L.P. AGENDA –Overview of Unix Portability Initiative –Semaphores –UTF-8 support –GNV Update –Q & A 2 © Copyright 2010 Hewlett-Packard Development Company, L.P. UNIX PORTABILITY - OVERVIEW 3 © Copyright 2010 Hewlett-Packard Development Company, L.P. UNIX PORTABILITY INITIATIVE OBJECTIVE GOAL BENEFIT • Ease Porting of • OpenVMS will be • Less OpenVMS applications from like any other development UNIX, LINUX “UNIX flavor” for cost and Open easy application • Enhanced Source to portability application OpenVMS • Cost of porting portfolio on from UNIX to OpenVMS, OpenVMS is including Open comparable to Source porting one applications "flavor" of UNIX • Familiar UNIX- to another style development environment 4 © Copyright 2010 Hewlett-Packard Development Company, L.P. RECENT DEVELOPMENTS & V8.4 Byte Range File Lock APIs Standard Stat Locking Structure SEMAPHORES Symbolic Links POSIX style GNV Updates pathnames statvfs/fstatvfs Pthreads Encryption UTF-8 Routines Shared Objects SUPPORT 5 © Copyright 2010 Hewlett-Packard Development Company, L.P. SEMAPHORES 6 © Copyright 2010 Hewlett-Packard Development Company, L.P. INTRODUCTION - SEMAPHORES Semaphores - Inter Process Communication mechanism for synchronization across multiple processes. –System V Semaphores –POSIX Semaphores 7 © Copyright 2010 Hewlett-Packard Development Company, L.P. NEED FOR SEMAPHORES ON OPENVMS PRE V8.4 SOLUTION IN IMPACT V8.4 • Semaphore API Implements Reduces porting implementation was Semaphore APIs time Reduces cost of not available Applications using porting • Implement emulator semaphores can be Facilitates porting solutions ported without code of other Open Source • Performance issues change applications to due to layered OpenVMS emulator solutions 8 © Copyright 2010 Hewlett-Packard Development Company, L.P.
    [Show full text]
  • HP Openvms Utility Routines Manual
    HP OpenVMS Utility Routines Manual Order Number: BA554-90019 June 2010 This manual describes the OpenVMS utility routines, a set of routines that provide a programming interface to various OpenVMS utilities. Revision/Update Information: This manual supersedes the HP OpenVMS Utility Routines Manual, OpenVMS Alpha Version 8.3. Software Version: OpenVMS Version 8.4 for Integrity servers OpenVMS Alpha Version 8.4 Hewlett-Packard Company Palo Alto, California © Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. ZK4493 The HP OpenVMS documentation set is available on CD. This document was prepared using DECdocument, Version 3.3-1B. Contents Preface ............................................................ xvii 1 Introduction to Utility Routines 2 Access Control List (ACL) Editor Routine 2.1 Introduction to the ACL Editor Routine ........................... ACL–1 2.2 Using the ACL Editor Routine: An Example ....................... ACL–1 2.3 ACL Editor Routine . ........................................ ACL–2 ACLEDIT$EDIT ...........................................
    [Show full text]