SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
DEC-X500-VAX DXDVE02030 Digital X.500 Directory Service V3.0 VAX ECO Summary

NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. Copyright (c) Digital Equipment Corporation 1996. All rights reserved. PRODUCT: Digital X.500 Directory Service, Version 3.0 OP/SYS: OpenVMS VAX, Versions 6.1 through 7.0 COMPONENTS: Digital X.500 Directory Service Administration Facility for OpenVMS VAX Digital X.500 Directory Server for OpenVMS VAX SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: DXDVE02030 ECO Kits Superseded by This ECO Kit: DXDVE01030 ECO Kit Approximate Size: Saveset A - 774 Blocks Saveset B - 31,680 Blocks Saveset C - 89,964 Blocks Cover Letter - 22 Blocks Total of 4 files - 122,440 Blocks ECO KIT SUMMARY: An ECO kit exists for Digital X.500 Directory Service V3.0 on OpenVMS VAX V6.1 through 7.0. This kit addresses the following problems: o This kit fixes a problem that could occur if an attribute value modification failed between removing the last existing value and adding new values. The attribute could sometimes be left with no values. This caused database corruption errors next time the DSA was started. o This kit fixes a problem with the multiple entry management facility in the DXIM command line utility. If you used these facilities to write information from the directory to a file, and one of the attributes had a null value, DXIM failed to create the output file correctly. It is valid for some attributes to have a null value, and this kit supports such attributes. o This kit fixes a problem with searching for attributes which have the distinguishedNameSyntax. o This kit fixes a problem that was causing the DSA to crash if the schema defined a large number of object classes. o This kit fixes a problem with replication on OpenVMS systems. Problems with the update log files were causing full updates instead of incremental updates. These problems have been fixed. o This kit fixes a problem that was introduced in the ECO kit 1 with the syntax of access controls items. The problem prevented users from referring to ACIitems using the ACIitem identifier. o This kit fixes a problem with the storage of supplier knowledge attributes. Long supplier knowledge attributes were sometimes encoded incorretly. o This kit fixes a problem with the handling of continuation characters in DXIM command lines. o This kit fixes a problem with the handling of corrupt updates log files. Instead of reporting the DIT Corrupt message, the DSA was crashing. o The handling of search requests has been changed slightly in this kit. If the user specifies a search filter that includes an invalid attribute value assertion, the DSA ignores the invalid assertion and only processes valid assertions, if any. In previous kits, the invalid assertion would cause the search to fail and return an attribute error. For example, if a user asks for entries that have a surname longer than the permitted length of surnames, that element of the search filter is ignored. o This kit can provide additional diagnostic information for analysing problems caused by system crashes. This information is provided for support staff only. o A problem that could cause a DSA to exit when attempting to generate a Distributed Operation Failure event has been fixed. o A problem encoding network addresses has been fixed. In previous versions, there was a problem encoding TCP/IP network addresses that had a 0 as their second element. For example, the following network address would be incorrectly encoded: 1.0.16.16. o A problem encoding attribute keywords in distinguished names has been fixed. In V3.0, a distinguished name such as /dec-mts-routing-domain=ACME would be incorrectly encoded because the keyword dec-mts-routing-domain contains hyphen characters. o A problem with DXIM's encoding of the identification labels of access control items has been fixed. The labels can now be encoded as either printable or T.61 strings, and labels that contain characters that are not in those character sets are rejected. If you use MODIFY ENTRY command to try to refer to existing, invalid values of a prescriptiveACI attribute, the command returns an error. Use the SET ENTRY command instead. The SET ENTRY command enables you to specify the intended state of a value without having to specify the existing state. You could also use a MODIFY ENTRY command with a REMOVE ATTRIBUTE clause to completely remove the prescriptiveACI attribute without having to specify the existing values. If you use the access control template, as recommended in the documentation, you are using a SET ENTRY command, so the errors never arise. o The DSA's syntax checking of access control items has been im- proved. In previous versions, the DSA accepted access controls with slightly invalid syntax. o The DSA thread monitor has been fixed to handle all exceptions that can be raised during thread creation. o The DSA Information Tree Schema Incompatible error, which can arise when you create a DSA, has been extended to cover a schema problem that previously caused a DSA Information Tree Corrupt error. If the schema does not define a class of entry that is present in the DSA, this is now reported as an incompatibility. o A memory handling problem with the DXIM SET ENTRY command has been fixed. o This kit fixes an access control problem that could occur if you modified access controls on a Digital UNIX system. o This kit includes access control diagnostics for use by Digital support. INSTALLATION NOTES: See the Cover Letter and Release Notes for more information on installing this ECO. Checklist: 1. Read the Read Before Installing document. 2. Check prerequisite software, diskspace, and licenses. 3. Install V3.0 ECO 1 of the Directory Service. Print the release notes and run the IVP during the installation. 4. Edit SYSTARTUP_VMS.COM to submit the directory startup procedure during system startup. 5. If upgrading or reinstalling, recustomize any customized files, specifically: The schema files (recompile the schema if you customize it) DXD$DSA_STARTUP.NCL DXD$TEMPLATE_STARTUP.NCL Other files that might have been customized in a previous version are saved during installation. See Saving Files on Reinstallation. 6. Start the Directory Service.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

dxdve01030.README
dxdve02030.CHKSUM
dxdve02030.CVRLET_TXT
dxdve02030.a-dcx_vaxexe
dxdve02030.b-dcx_vaxexe
dxdve02030.c-dcx_vaxexe

privacy and legal statement