DOCSLIB.ORG

VMS Version 5.5-2 Release Notes

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
VMS Version 5.5-2 Release Notes VMS Version 5.5-2 Release Notes Order Number: AV-PQZAB-TE August 1992 This document describes software problems, corrections, restrictions, documentation changes, and new hardware support that pertain to Version 5.5-2 of the VMS operating system. Revision/Update Information: This is a new manual. Software Version: VMS Version 5.5-2 Digital Equipment Corporation Maynard, Massachusetts August 1992 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © Digital Equipment Corporation 1992. 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: ALL-IN-I, CI, DECdtm, DECmcc, DECnet, DEC PHIGS, DECwindows, DEQNA, Digital, HSC, KLESI, PATHWORKS, Q-bus, Q22-bus, RA, RSX, RRD42, TMSCp, TURBOchannel, UNIBUS, VAX, VAX Ada, VAX C, VAX DOCUMENT, VAXstation, VMS, and the DIGITAL logo. BASIC (Dartmouth Structured Basic) is a registered trademark of the Trustees of Dartmouth College, D.B.A. Dartmouth College. UNIX is a registered trademark of UNIX System Laboratories, Inc. ZK5961 This document was prepared using VAX DOCUMENT, Version 2.1. Contents Preface. .. .. .. .. .. ... .. .. .. xi 1 General User Release Notes 1.1 Digital Command Language (DCL) ............................. 1-1 1.1.1 EDITfI'PU Command INOWORK Qualifier-Problem Corrected .... 1-1 1.1.2 Error Message Displayed When Non-Modem Port Is Set to Modem .. 1-1 1.1.3 ON Condition Response-Problem Corrected ................... 1-1 1.1.4 READ Command Error Message ............................ 1-2 1.1.5 SET DEFAULT and SHOW DEFAULT Commands-Behavior Changed ............................................... 1-2 1.1.6 SET MESSAGE Command Changed-Problem Corrected ......... 1-2 1.1.7 SET TERMINAUSPEED Command-Problem Corrected ......... 1-3 1.1.8 SET TERMINAUCOMMSYNC Command-Support Added ....... 1-3 1.1.9 SHOW DEVICEIFULL Command-Problem Corrected ........... 1-3 1.1.10 TYPE Command /PAGE Qualifier-Enhanced Screen Usage ....... 1-4 1.2 Mail Utility (MAIL) ......................................... 1-4 1.2.1 MAIL Sends and Receives Compound DDIF and DTIF Documents .. 1-4 1.2.2 Missing Error Message in MAIL-Problem Corrected ............ 1-4 1.3 VAXstation 4000 Keyboard Problem ............................. 1-4 1.4 VAX Text Processing Utility (VAXTPU) ...... : ................... 1-4 1.4.1 EVE Key Name Definitions-Problem Corrected ................ 1-4 1.4.2 FILL Built-In Procedure-Problems Corrected ................. 1-5 1.4.3 Tabs in Overstrike Mode-Problem Corrected .................. 1-5 1.4.4 Work Files-Problem Corrected ............................. 1-5 2 System Manager Release Notes 2.1 Allocation Classes in VAXcluster Configurations-Restriction ........ 2-1 2.2 Audit Analysis Utility /SELECT=STATUS=FAILURE Qualifier-Problem Corrected ................................................. 2-1 2.3 AUTOGEN Command Procedure Notes ........ ; ................. 2-1 2.3.1 AUTOGEN Problem When Executed from SYSMAN ............. 2-1 2.3.2 Specifying a Minimum Required Age for AUTOGEN Feedback Data .................................................. 2-2 2.3.3 Specifying the Number of Ethernet Adapters for AUTOGEN ...... 2-2 2.3.4 Specifying the Number of VAX cluster Nodes for AUTOGEN ....... 2-2 2.3.5 Suggested Workaround to SYSMAN Value Error ................ 2-2 2.3.6 TMSCP_LOAD Parameter-Problem Corrected ................. 2-3 2.4 Backup Utility (BACKUP) .................................... 2-4 2.4.1 BACKUP Denies Privileged Users Access to a Tape ............. 2-4 2.4.2 BACKUPILIST Operations on a Save Set ..................... 2-4 2.4.3 Data Compactions on Tape Drives ........................... 2-4 2.4.4 Extending Index Files .................................... 2-4 iii 2.4.5 Message Status Codes Restored ............................. 2-5 2.4.6 Multivolume Logical Names ................................ 2-5 2.4.7 Multivolume Save Operations from a Subprocess ............... 2-5 2.4.8 Saving and Restoring Alias Directories ....................... 2-5 2.4.9 Tape Volume Protection ................................... 2-6 2.5 Batch and Print Queuing System ............................... 2-6 2.5.1 ALL-IN-l and Batch and Print Queuing System-Interaction Problems Corrected ...................................... 2-7 2.5.2 Chance of Queuing System Shutting Off During Node Shutdown ... 2-7 2.5.3 Corruption Detection for Queues ............................ 2-7 2.5.4 DEFINE/CHARACTERISTIC Command Allows Only One Name to a Number ............................................... 2-8 2.5.5 VAX Distributed Queuing Service (DQS) Print Symbiont-Suggested Workaround ............................................ 2-8 2.5.6 Generic Queues with Implicit Target Lists-Change in Behavior ... 2-9 2.5.7 Queue Manager CPU Limit-Problem Corrected ................ 2-10 2.5.8 Queue Manager Stop_Pending Status-Problem Corrected ........ 2-10 2.5.9 Queue Manager SYMDEL Message-Problem Corrected .......... 2-10 2.5.10 Saving Information in the Queue Database-Problem Corrected .... 2-10 2.5.11 SUBMITIUSER and PRINTIUSER Commands Provide In.correct Account Name-Problem Corrected .......................... 2-11 2.5.12 SYNCHRONIZE Command-Problem Corrected ................ 2-11 2.6 CLUSTER_CONFIG.COM Command Procedure-Updated to Read Undefined System Disks ..................................... 2-11 2.7 Data Corruption on Disk with New Allocation Class ................ 2-11 2.8 DECnet-VAX Notes ......................................... 2-12 2.8.1 Adjusting NETACP Quotas with NETACP$ Logical Names ........ 2-12 2.8.2 Cluster Synchronization Improved ........................... 2-13 2.8.3 Event Logger-Problem Corrected ........................... 2-13 2.8.4 EXECUTOR NODE Corruption-Problem Corrected ............. 2-13 2.8.5 FDDI and Token Ring Device Support-Problem Corrected and Improvements Added ..................................... 2-13 2.8.6 FDDI Line Parameters for Phase IV Network Management ....... 2-14 2.8.6.1 SHOW LINE Display Modified ........................... 2-16 2.8.7 NCP Command Prevents Unauthorized Connections to the Mail Server ................................................ 2-17 2.8.8 NCP Commands for DNS Interface .......................... 2-17 2.8.9 NETACP Allocation of Node Counter Blocks Changed ............ 2-18 2.8.10 NETDRIVER PATH SPLIT POLICY Call-Problem Corrected ..... 2-19 2.8.11 NETACP Endnode Failover-Problem Corrected ................ 2-19 2.8.12 NDDRIVER Queue Corruption-Problem Corrected ............. 2-19 2.8.13 NCP Module Configurator-Problem Corrected and Improvements Added ................................................. 2-19 2.8.14 NCP SHOW KNOWN NODES Display-Problem Corrected ....... 2-20 2.8.15 Patched Images for DNS Version 1.1 ......................... 2-20 2.8.16 Phase IV Support for DSW-21 and DSW-41142 Devices ........... 2-20 2.9 DECwindows .............................................. 2-20 2.9.1 Dashed Lines Drawn Incorrectly-Problem Corrected ............ 2-20 2.9.2 DECwindows Monitor Density Is Now Definable ................ 2-21 2.9.3 DECwindows Server Incompatibility with DEC PHIGS ........... 2-22 2.9.4 DECwindows Use of SMP with DEC sound and SODRIVER ....... 2-22 2.9.5 SoftPC with DECwindows Server-Keyboard Problem ........... 2-22 2.9.6 Tiled Operations Drawn in Wrong Window-Problem Corrected .... 2-23 2.10 DeltalXDelta Utility (DELTAlXDELTA) .......................... 2-23 iv 2.10.1 DeltalXDelta Utility-Booting New VAX Computers ............. 2-23 2.11 Disk Class Drivers .......................................... 2-24 2.11.1 MSCPCLASS Error-Problem Corrected ...................... 2-24 2.11.2 Opcode for MSCP Message Improperly Set-Problem Corrected .... 2-24 2.11.3 Shutdown Error While Copy Operation in Progress-Problem Corrected .............................................. 2-24 2.11.4 Volume Shadow Set Members Race Condition-Problem Corrected .. 2-24 2.12 Distributed Lock Manager .................................... 2-24 2.12.1 Block Transfer to an Unavailable Node Caused System Failure- Problem Corrected ....................................... 2-24 2.12.2 Lock Range Value Corruption-Problem Corrected .............. 2-24 2.12.3 Remastering Routine Race Condition-Problem Corrected ........ 2-24 2.12.4 RSPFATAL Status Caused System Failure-Problem Corrected .... 2-25 2.12.5 System Parameter Added to Lock Manager .................... 2-25 2.13 InfoServer Client-Startup Behavior Change ..................... 2-25 2.14 LAT Not Supported on DEQNA ................................ 2-25 2.15 Mount Utility (MOUNT) ..................................... 2-25 2.15.1 Bound Volume Set Problem Using Volume Shadowing Phase I and Phase II-Suggested Workaround ........................... 2-25 2.15.2 MOUNT Commands Delayed Other Nodes-Problems Corrected ... 2-26 2.15.3 MOUNT Command Caused CPUs to Halt-Problem Corrected ..... 2-26 2.15.4 Shadow Sets Improperly Allowed-Problem Corrected ........... 2-26 2.15.5 Shadow
Load more

Recommended publications
  • Exniffer: Learning to Rank Crashes by Assessing the Exploitability from Memory Dump
    Exniffer: Learning to Rank Crashes by Assessing the Exploitability from Memory Dump Thesis submitted in partial fulfillment of the requirements for the degree of MS in Computer Science & Engineering by Research by Shubham Tripathi 201407646 [email protected] International Institute of Information Technology Hyderabad - 500 032, INDIA March 2018 Copyright c Shubham Tripathi, March 2018 All Rights Reserved International Institute of Information Technology Hyderabad, India CERTIFICATE It is certified that the work contained in this thesis, titled “Exniffer: Learning to Rank Crashes by Assessing the Exploitability from Memory Dump” by Shubham Tripathi, has been carried out under my supervision and is not submitted elsewhere for a degree. Date Adviser: Prof. Sanjay Rawat “Contemplate and reflect upon knowledge, and you will become a benefactor to others.” To my parents Acknowledgments I would like to express my gratitude to my adviser, Dr. Sanjay Rawat. Sanjay sir helped me staying focused on problems and provided new directions to approach them. Working with him, I have devel- oped my problem solving skills, learnt about research, about life in general. I would be thankful to him for all my life, for providing me the guidance on various matters, always motivating and boosting me with confidence, which really helped me in shaping my life. I must also thank all my lab-mates who are working or have worked earlier in CSTAR - Vijayendra, Spandan, Satwik, Charu, Teja, Ishan and Lokesh. I really enjoyed working with them in the lab. I would like to thank all my friends in IIIT, for making my stay in the campus a memorable one.
    [Show full text]
  • Alphaserver ES40 Service Guide
    AlphaServer ES40 Service Guide Order Number: EK–ES240–SV. A01 This guide is intended for service providers and self- maintenance customers responsible for Compaq AlphaServer ES40 systems. Compaq Computer Corporation First Printing, July 1999 The information in this publication is subject to change without notice. COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN, NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. THIS INFORMATION IS PROVIDED “AS IS” AND COMPAQ COMPUTER CORPORATION DISCLAIMS ANY WARRANTIES, EXPRESS, IMPLIED OR STATUTORY AND EXPRESSLY DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, GOOD TITLE AND AGAINST INFRINGEMENT. This publication contains information protected by copyright. No part of this publication may be photocopied or reproduced in any form without prior written consent from Compaq Computer Corporation. © 1999 Digital Equipment Corporation. All rights reserved. Printed in the U.S.A. The software described in this guide is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement. COMPAQ and the Compaq logo are registered in United States Patent and Trademark Office. Tru64 is a trademark of Compaq Computer Corporation. AlphaServer and OpenVMS are trademarks of Digital Equipment Corporation. Prestoserve is a trademark of Legato Systems, Inc. UNIX is a registered trademark in the U.S. and other countries, licensed exclusively through X/Open Company Ltd. Microsoft, Windows, and Windows NT are registered trademarks of Microsoft Corporation. Other product names mentioned herein may be the trademarks of their respective companies.
    [Show full text]
  • How Do I Use Windbg Debugger to Troubleshoot a Blue Screen of Death?
    How do I use WinDBG Debugger to troubleshoot a Blue Screen of Death? Have you ever wondered how to obtain extra information from the infamous Blue Screen of Death (BSOD) that will sometimes show up and give you a cryptic, Stop: 0x00000000 error message, before flashing off the screen. The error message is trying to point you to a fatal operating system error that could be caused by a number of problems. Microsoft's WinDBG will help you to debug and diagnose the problem and then lead you to the root cause so you can fix it. Steps in a nutshell The first step is to create and capture the memory dump, associated with the BSOD you are trying to troubleshoot. The second step is to install and configure WinDBG and the Symbols path to the correct Symbols folder. We can then use WinDBG to Debug and analyze the screen dump, and then get to the root cause of the problem. Create memory dump Keep in mind that if you are not experiencing a blue screen fatal system error, there will be not memory dump to capture. 1. Press the WinKey + Pause 2. Click Advanced and under Start up and Recovery select Settings. 3. Uncheck Automatically restart. 4. Click on the dropdown arrow under Write debugging information. 5. Select Small memory dump (64 KB) and make sure the output is %SystemRoot%\Minidump. 6. Restart the PC normally as this will allow the System to error and Blue Screen and then create the Minidump. The location of the Minidump Files can be found here: C:\WINDOWS\Minidump\Mini000000-01.dmp To download and install the Windows debugging tools for your version of Windows, visit the Microsoft Debugging Tools Web.
    [Show full text]
  • Oracle® VM Paravirtual Drivers for Microsoft Windows Release 3.4.5
    Oracle® VM Paravirtual Drivers for Microsoft Windows Release 3.4.5 F26652-03 November 2020 Oracle Legal Notices Copyright © 2020, 2020, Oracle and/or its affiliates. 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 embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Fix DRIVERVERIFIERDMAVIOLATION Blue Screen Error on Windows
    Fix DRIVER_VERIFIER_DMA_VIOLATION Blue Screen Error On Windows Fix DRIVER_VERIFIER_DMA_VIOLATION Blue Screen Error On Windows 1 / 5 2 / 5 Driver Verifier is a tool included in Microsoft Windows that replaces the default ... How to fix the BSOD Error 0xE6 DRIVER_VERIFIER_DMA_VIOLATION This .... Blue Screen of Death (BSOD) is a very common error screen, usually caused by ... Although BSOD screen most commonly appears during Windows boot up ... which you can use to identify what's causing the problem and how to fix it. ... DRIVER_VERIFIER_DMA_VIOLATION, Occurs when Driver Verifier .... If your PC's windows are suffering from Windows Stop Errors or Blue Screen error, our guide of Windows Stop Code Errors will help you fix Windows Update Errors. ... 0x000000E6, DRIVER_VERIFIER_DMA_VIOLATION. 0x000000E7 ... Steps to Troubleshoot Blue screen of Death Error on Lenovo Laptop windows by ... A Complete Guide to Fix BSOD Errors in Windows 10, 8, 7, Vista, and XP: ... may also show “DRIVER_VERIFIER_DMA_VIOLATION” on the same blue screen.. The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. ... If it finds a driver problem, you'll see a blue screen of death. ... Bug Check 0xE6 DRIVER_VERIFIER_DMA_VIOLATION - Windows drivers .... I have been getting this error (BSOD DRIVER_VERIFIER_DMA_VIOLATION (e6)) ... was one of the first things I tried to do to fix it after Googling the error. ... for the particular BSOD code (0xE6) because according to Microsoft's .... A BSOD is an error that causes Windows to STOP (hence the name “STOP ... How to fix BlueScreen (STOP) errors that cause Windows Vista to .... DRIVER_VERIFIER_DMA_VIOLATION "Microsoft sees red over blue screen of ..
    [Show full text]
  • System Error Codes Logon Process Terminated Unexpectedly Fix
    System Error Codes Logon Process Terminated Unexpectedly Fix Fix the 0xC000021A (or c000021a) boot error for the following Windows Windows SubSystem system process terminated unexpectedly with a status of 0xc0000005. 8.1, the error message appears like this (but with the same error code): Hit Enter, Login as Administrator, When Command Prompt Appears, type. What Causes This Error, How to Fix This Error, Uninstall Program(s), Run a The Windows Logon Process system process terminated unexpectedly with a status this tool, I suggest you check out my post on resolving error code 800b0100. The bulletin that affects Vista but no other client operating system is MS15-066 which MS15-058 - Vulnerabilities in SQL Server Could Allow Remote Code The windows Logon Process System process terminated unexpectedly with a status of I wonder if microsoft will step up with a fix for it, or if it is just a big middle. How To Fix The Windows Stop C000021a Fatal System Error. (Fatal System Error) The windows subsystem process terminated unexpectedly The windows logon process system process terminated I am looking as well, but if the Windows screen of death error code I'm getting is a "C000021a (fatal system error) The The Windows Logon Process system process terminated unexpectedly with a Here are some do it yourself methods to fix this error code right away. c00021a Fatal System Error Message – Windows XP Home and … windows logon process system process terminated unexpectedly with a status of fatal error, windows retained error. code:805306296. and also the following error code:. System Error Codes Logon Process Terminated Unexpectedly Fix Read/Download STOP: c000021a (Fatal System Error) the verification of KnownDLL failed.
    [Show full text]
  • IM: U: System Errorhandler
    CHAPTER 2 System Error Handler 2 This chapter describes the System Error Handler. The System Error Handler assumes control of the system when a system error occurs and is also responsible for displaying certain alert boxes in response to a system startup. The System Error Handler displays an alert box when a system error occurs and manages display of the “Welcome to Macintosh” alert box and the disk-switch alert box. This chapter explains what the Operating System does when a system error is encountered, describes the routine and resource that the System Error Handler uses when generating a system error alert box, and discusses how you can provide code that 2 can help your application recover from an system error. System Error Handler Although your application may call the routine provided by the System Error Handler, ordinarily there is no need to do so; this routine is primarily used by the Macintosh Operating System. This chapter also contains a list of all currently defined system errors and the conditions under which they can arise. About the System Error Handler 2 The System Error Handler employs a mechanism that allows for display of simple alert boxes even when the Control Manager, Dialog Manager, and Memory Manager might not be able to function properly. System Error Handler alert boxes can therefore be displayed at times when the Dialog Manager cannot be called. This mechanism is useful at two times. First, at system startup time, the Dialog Manager may not yet have been initialized. Second, after a system error occurs, using the Dialog Manager or Memory Manager may be impossible or cause a system crash.
    [Show full text]
  • Error Correction Code in Soc FPGA-Based Memory Systems
    Error Correction Code in SoC FPGA-Based Memory Systems WP-01179-1.2 White Paper, with contributions from Micron Technology This paper examines the potential sources and implications of soft errors and a method implemented by Altera Corporation and Micron Technology to make embedded systems more resilient to these types of soft errors through error detection and correction. Introduction Continuously advancing semiconductor process technologies have enabled increased component integration, functionality, and performance in embedded systems. While the increased capabilities reap huge rewards, one of the side effects of higher- performance systems is that more attention must be paid to the probability of soft errors. Decreasing supply voltages cause integrated circuits to be increasingly susceptible to various types of electromagnetic and particle radiation. As memory size in embedded systems grows to 100s of megabytes, soft errors due to naturally occurring alpha particles may exceed acceptable levels. As interface speeds exceed 1 Gigabits per second, excessive noise and jitter may cause errors in the transmission lines to and from external memory. Memory Bit Error Sources Bit Cell Soft Errors Commonly used memory bit cells retain their programmed value in the form of an electrical charge. Writing a memory bit cell consists of reprogramming and forcing the electrical charge to represent the new desired value. Memory bit cells will retain their value indefinitely, as long as basic requirements are met, e.g. power is applied, and— for dynamic memory types—a refresh method is active. The stored charge can be negatively impacted by injection of a charge foreign to the memory device. Cosmic particles colliding with atoms in the atmosphere cause energetic rays which may affect the stored charge.
    [Show full text]
  • Fatal System Error
    Fatal system error Stop c000021a Fatal System Error. This is a Windows stop error, (also referred to as âœThe Blue Screen of Deathâ or BSOD error or kernel error). The stop error message usually reads: STOP: c000021a {Fatal System Error} The Windows Logon Process system process terminated unexpectedly with a status of 0xc06d007e (0×00000000 0×00000000). The system has been shut down. What Causes Stop Error c000021a? A fatal system error, also known as a system crash, stop error, kernel error, or bug check, occurs when an operating system halts, because it has reached a condition where it can no longer operate safely. In Microsoft Windows, a fatal system error can be deliberately caused from a kernel-mode driver with either the KeBugCheck or KeBugCheckEx function. However, this should only be done as a last option when a critical driver is corrupted and is impossible to recover. This design parallels that in Stop: c000021a {Fatal System Error} The initial session process or system process terminated unexpectedly with a status of 0x00000000 (0xc0000221 0x001003a8). The system has been shut down. This thread is locked. This error occurs when a user-mode subsystem, such as WinLogon or the Client Server Run-Time Subsystem (CSRSS), has been fatally compromised and security can no longer be guaranteed. In response, the operating system switches to kernel mode. fatal system error. I have an almost 6 year old Dell Dimension 8250 and have been having trouble all week with blue screens. However I was always able to get back into Windows. I have been running chkdsk and it found loads of problems with the hard disk.
    [Show full text]
  • Oracle Timesten In-Memory Database Error Messages and SNMP Traps Release 7.0
    Oracle TimesTen In-Memory Database Error Messages and SNMP Traps Release 7.0 B31690-02 Copyright ©1996, 2007, Oracle. All rights reserved. ALL SOFTWARE AND DOCUMENTATION (WHETHER IN HARD COPY OR ELECTRONIC FORM) ENCLOSED AND ON THE COMPACT DISC(S) ARE SUBJECT TO THE LICENSE AGREEMENT. The documentation stored on the compact disc(s) may be printed by licensee for licensee’s internal use only. Except for the foregoing, no part of this documentation (whether in hard copy or electronic form) may be reproduced or transmitted in any form by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without the prior written permission of TimesTen Inc. Oracle, JD Edwards, PeopleSoft, Retek, TimesTen, the TimesTen icon, MicroLogging and Direct Data Access are trademarks or reg- istered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs (which include both the software and documenta- tion) contain proprietary information; they are provided under a li- cense agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or de- compilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, 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. This document is not warranted to be error-free. Except as may be expressly permitted in your li- cense agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, elec- tronic or mechanical, for any purpose.
    [Show full text]
  • Openvms System Messages and Recovery Procedures Reference Manual: M–Z
    OpenVMS System Messages and Recovery Procedures Reference Manual: M–Z Order Number: AA–PVXLA–TE May 1993 The OpenVMS System Messages and Recovery Procedures Reference Manual: M–Z alphabetically lists and describes messages produced by the OpenVMS operating system that begin with the letters M through Z. Each message is accompanied by an explanation and, where applicable, a suggested recovery procedure. Revision/Update Information: This manual supersedes the VMS System Messages and Recovery Procedures Reference Manual: Part II, Version 5.4. Software Version: OpenVMS AXP Version 1.5 OpenVMS VAX Version 6.0 Digital Equipment Corporation Maynard, Massachusetts May 1993 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. © 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: Alpha AXP, AXP, BI, Bookreader, CDA, CI, CMI, DEC, DECdtm, DECnet, DECtalk, DECthreads, DECwindows, DEUNA, Digital, EDT, LAT, MASSBUS, MSCP, OpenVMS, Q–bus, RC25, RT–11, RX02, SBI, TU, UDA, UETP, ULTRIX, UNIBUS, VAX, VAX BASIC, VAX C, VAXcluster, VAX DOCUMENT, VAX FORTRAN, VAX MACRO, VAX PL/I, VAXport, VAX–11, VAX–11 RSX, VAX–11/750, VAX–11/780, VAX 8200, VAX 8300, VMS, VMScluster, the AXP logo, and the DIGITAL logo.
    [Show full text]
  • Troubleshooting Sunpci™ II CD-ROM Access Problems
    The Blue Screen Of Death (BSOD) Primer By SunPCi Product Development Team http://www.sun.com/desktop/products/sunpci/ Wednesday, February 19, 2003 1 Copyright 2003 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 94054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, SunPCi, Solaris and Ultra are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227- 14(g)(2)(6/87) and FAR 52.227-19(6/87), or DFAR 252.227-7015(b)(6/95) and DFAR 227.7202-3(a).
    [Show full text]