| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 132.1 | Kit queries | KAOFS::R_TASCHUK | | Tue Mar 25 1997 19:23 | 17 |
| Apparently, there was a problem with the ECO kits that were first
released for OVMS version 5.5-2.
Is the kit location that is given in note 131.1 now the latest
and correct one?
Also, is it really necessary to create an individual kit for
each version of OVMS, or will any one kit handle all versions?
For example, will any of the version 5 kits apply to any version
of OpenVMS? All the modification dates any file sizes are identical
for every one of the files, so it raises the question of whether
these are actually identical.
Thanks for any response.
Ron Taschuk
MVCS Canada
|
| 132.2 | | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Wed Mar 26 1997 10:30 | 24 |
|
The kit location in 131.1 is the correct location. However, if you
continue to have problems with those kits, then I suggest trying the
following location:
MINOTR:USER7:[SECURITY_KITS.OPENVMS...]
CISG is working with the CCS IT Security Operations group for
production support of security related patch kit archive servers to be
accessible across the three Zones - Americas, A/P, Europe. The
structure is intended to be by platform, by version. Over time, each
version will begin to have a different collection of patches, from
other versions for that platform. This is intended to make it a little
easier for system managers and support personnel to locate all the
reported security patches for a given version(s) they are
managing/supporting. To accomplish this, it is necessary to replicate
a single patch kit across all the versions it addresses.
This is also the same structure/process implemented for the DIGITAL
Patch Service on the Internet/WEB for customer access.
-- Chuck
|
| 132.3 | VAXLIBR06_070 ? | KAOFS::R_TASCHUK | | Tue Apr 01 1997 16:09 | 14 |
| Thanks for your reply, Chuck.
Can you provide me with the location for the VAXLIBR06_070.* Kits.
Apparently they supercede the VAXLIB05_070.* kits, so they should
be the ones that we need to get and install.
Also, the kits in MINOTR:: contain 10 files, the kits in ESRSRF::
contained 17. Why the difference?
Cheers,
Ron Taschuk
MVCS Edmonton, ALberta, Canada
|
| 132.4 | VIA TIMA/STARS for the short-term (internal) longterm for customers | BSS::BOREN | | Thu Apr 03 1997 12:40 | 98 |
| <RE: 132.2>
From TIM Patch folks:
<snip>***THIS ARTICLE IS AVAILABLE VIA STARS/TIMA....
ARTICLE TITLE: *OpenVMS] VAXLIBR06_070 VAX V5.5 - V7.0 LIBRTL ECO Summary
24-Mar-1997 1450" 24-MAR-1997 14:51:52.08
To: @PAT$DIS:ECO_NOTIFY.DIS
CC:
Subj: [I] VAXLIBR06_070 Is Now Available on DSNlink, Internet, and at SSB
NOTE: VAXLIBR06_070 is now available on DSNlink/DIA/WIS,
Internet, and at SSB.
*OpenVMS] VAXLIBR06_070 VAX V5.5 - V7.0 LIBRTL ECO Summary
Copyright (c) Digital Equipment Corporation 1996, 1997. All rights reserved.
INSTALLATION NOTES: If your system is running OpenVMS VAX V5.5-2* *AND*
you installed VAXLIBR05_070 on that system, in order
to avoid system crashes, you *MUST* install this
kit, VAXLIBR06_070, on your system.
If your system is running OpenVMS VAX V5.5, V5.5-1,
V6.0, V6.1, V6.2 or V7.0 and VAXLIBR05_070 has been
installed on your system, you *DO NOT* need to install
this kit, VAXLIBR06_070.
If your system is running OpenVMS VAX V5.5, V5.5-1,
V5.5-2*, V6.0, V6.1, V6,2, or V7.0 and VAXLIBR05_070
has not been installed on your system, you *MUST*
install this kit, VAXLIBR06_070, on your system.
OP/SYS: OpenVMS VAX
COMPONENTS: For OpenVMS VAX V5.5, V5.5-1, V5.5-2, V5.5-2H4, V5.5-2HF
and V6.0:
LIBRTL.EXE
LIBRTL2.EXE
MESSAGE_ROUTINES.EXE
STARLET.OLB - Updated with LIB$DATE_ARITHMETIC and
LIB$DATE_CVT
For OpenVMS VAX V6.1, V6.2, and V7.0:
LIBRTL.EXE
LIBRTL2.EXE
LIBRTL_INSTRUMENTED.EXE
MESSAGE_ROUTINES.EXE
STARLET.OLB - Updated with LIB$DATE_ARITHMETIC and
LIB$DATE_CVT
For OpenVMS VAX V5.5 through V7.0:
LIBRTL$ECO_DROP.COM (If desired, this command file
may be used to remove the ECO
and restore the original
files and libraries. If this
file is used to remove the kit
from the system, the system
needs to be rebooted after the
successful removal of the kit.)
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXLIBR06_070
ECO Kits Superseded by This ECO Kit: VAXLIBR05_070
VAXLIBR02_070
VAXLIBR01_070
VAXLIBR02_062
VAXLIBR01_062
ECO Kit Approximate Size: 4752 Blocks
Saveset A - 90 Blocks
Saveset B - 378 Blocks
Saveset C - 396 Blocks
Saveset D - 414 Blocks
Saveset E - 1134 Blocks
Saveset F - 1152 Blocks
Saveset G - 1170 Blocks
Kit Applies To: OpenVMS VAX V5.5, V5.5-1, V5.5-2, V5.5-2H4, V5.5-2HF,
V6.0, V6.1, V6.2, V7.0
System/Cluster Reboot Necessary: Yes
Installation Rating: 1 - To be installed on all systems running
the listed version(s) of OpenVMS.
NOTE: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
None
<snip>***THIS ARTICLE IS AVAILABLE VIA STARS/TIMA....
|
| 132.5 | ECO VAXLIBR06_070 Supersedes VAXLIBR05_070 | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Mon Apr 07 1997 14:52 | 46 |
|
ECO VAXLIBR06_070 has been loaded to the Security Patch Server on
Node/Host MINOTR::USER7:[SECURITY_KITS.OPENVMS.VAX...]
VAXLIBR06_070.CHKSUM
VAXLIBR06_070.README
VAXLIBR06_070.CVRLET_TXT
VAXLIBR06_070.A-DCX_VAXEXE
VAXLIBR06_070.B-DCX_VAXEXE
VAXLIBR06_070.C-DCX_VAXEXE
VAXLIBR06_070.D-DCX_VAXEXE
VAXLIBR06_070.E-DCX_VAXEXE
VAXLIBR06_070.F-DCX_VAXEXE
VAXLIBR06_070.G-DCX_VAXEXE
This ECO supersedes VAXLIBR05_070 for OpenVMS/VAX versions V5.5 - V7.0.
It includes a specific correction to the Delta-Time patch for V5.5-2.
Please read the following Installation Notes for clarification before
deciding to install this ECO.
INSTALLATION NOTES:
If your system is running OpenVMS VAX V5.5-2* *AND*
you installed VAXLIBR05_070 on that system, in order
to avoid system crashes, you *MUST* install this
kit, VAXLIBR06_070, on your system.
If your system is running OpenVMS VAX V5.5, V5.5-1,
V6.0, V6.1, V6.2 or V7.0 and VAXLIBR05_070 has been
installed on your system, you *DO NOT* need to install
this kit, VAXLIBR06_070.
If your system is running OpenVMS VAX V5.5, V5.5-1,
V5.5-2*, V6.0, V6.1, V6,2, or V7.0 and VAXLIBR05_070
has not been installed on your system, you *MUST*
install this kit, VAXLIBR06_070, on your system.
If you determine that you need to install this ECO, then please read
the VAXLIBR06_070.README and the VAXLIBR06_070.CVRLET_TXT documents
prior to installation.
regards,
chuck
|
| 132.6 | Problems with installation of VAXLIBR05_070 | ROM01::FRISINA | OMS Rome, Italy | Mon May 05 1997 12:21 | 57 |
| I have installed the VAXLIBR05_070 patch on a VAX system running
OpenVMS V5.5-2.
This morning it was the first reboot of the system after the
installation, and during the startup process there was a crash,
probably when Oracle (V6) was started. No dump was originated, because
there is not enough space on system disk. Analyzing the error log,
there is evidence of the Fatal Bugcheck, with the error
"KRNLSTAKNV, Kernel stack not valid", but there's not evidence of the
image causing the crash.
By removing the files provided with the patch VAXLIBR05_070 and
restoring the original ones, the boot was ok and the system is up and
running.
Now I have a series of questions...
1) Should the new ECO provided VAXLIBR06_070 solve the problem of the
crash in this case?
2) After the installation of VAXLIBR05_070, should I relink the Oracle
environment?
3) Is it REALLY necessary (advisable) to install the patch in case the
applications on the system don't use:
OpenVMS SECURITY Server OpenVMS Alpha V7.0 only
DECwindows Motif for OpenVMS OpenVMS Alpha V7.0 only
Distributed Computing Environment OpenVMS Alpha V6.2 only
(DCE) for OpenVMS
OpenVMS DECthreads OpenVMS Alpha and OpenVMS
VAX V5.5 through V7.0
(OSU) DECthreads HTTP Server (free- OpenVMS Alpha and OpenVMS
ware provided with the OpenVMS VAX V5.5 through V7.0
Internet_Product_Suite)
This question is originated by the fact that I should install the patch
on about 90 systems at a "critical" customer site and most of these
VAX and Alpha have Oracle (V6 and V7) installed on them... The
installation would then mean a heavy work, also considering the
possibility of relinking Oracle, if this is necessary.
Moreover, I would avoid crashes on production systems.
4) Does the fact that versions prior to OpenVMS V5.5 are not listed in
the cover letter mean there are no problems with Delta-Time for old VMS
versions or they were just not considered because not supported
anymore?
I would appreciate help on these matters.
Thanks for your support.
Iolanda
OMS Rome, Italy
|
| 132.7 | Response to 132.6 | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Tue May 06 1997 12:17 | 23 |
| Iolanda,
1. Yes, on V5.5-2 systems, VAXLIBR06_070 does correct a problem with
the Kernal Stack, which was caused by VAXLIBR05_070. (See details in
the README.)
2. For 3rd party applications, if the developer uses OpenVMS shareable
images, it is likely that relinkling is not necessary. You need to
varify with the developer, if you have questions. (See the Customer
Letter for details.)
3. Yes, it is advisable to install the patch kit. DIGITAL has no way
of knowing whether the customer has other 3rd party software which
might be incorrectly using the Delta Time function.
4. Versions prior to V5.5-2 are not impacted by the Delta-Time Limit.
Regards,
Chuck
|
| 132.8 | Thanks for the quick answer | ROM01::FRISINA | OMS Rome, Italy | Tue May 06 1997 12:26 | 9 |
| Chuck,
thanks for your precious answers.
I checked with the Oracle specialists and they said they need to relink
the environment.
Bye
Iolanda
|
| 132.9 | CORRECTION | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Tue May 06 1997 13:08 | 16 |
|
CORRECTION:
I just received information from OpenVMS Engineering that they are
releasing kits for older versions of OpenVMS/VAX V5.0 through 5.4-3.
There is no impact to DIGITAL products on those versions.
HOWEVER, some 3rd party products might be a problem. So OpenVMS is
releasing the additional kits to support customer demand. As soon as
those kits are released to customers, a CISG Security Bulletin 97-02
Addendum will be sent.
-- Chuck
|
| 132.10 | Kits for VAX/VMS V5.0 through V5.4-3 | ROM01::FRISINA | OMS Rome, Italy | Wed May 07 1997 11:11 | 6 |
| Could you give the pointer to these kits whenever they are available?
Thanks
Iolanda
|
| 132.11 | Bulletin needs an update | SHOGUN::LEONARD | | Mon May 12 1997 17:44 | 11 |
| Couple of questions.
1. Wouldn't it make sense to update the bulletin (sb9702.txt) at
corpsec.mso.dec.com to indicate the danger of installing VAXLIBR05_070
on a VAX VMS 5.5-2 system?
2. Why not update the contents of the directory for vms 5.5-2,
ESRSRF""::DISK$ESRSRF_DAT01:[SECURITY.OPENVMS.VAX.V55_2], to include
VAXLIBR06_070?
Rich Leonard
|
| 132.12 | Addendum #1 Supersedes Original Bulletin | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Tue May 13 1997 15:10 | 24 |
|
DIGITAL INTERNAL USE ONLY
The Corporate Information Security Group (CISG) has issued Security
Bulletin 1997-02 Addendum #1, Delta-Time Limit Problem for OpenVMS.
This problem may cause system problems on or about 19 May 1997 for
OpenVMS/Alpha and OpenVMS/VAX versions V5.0 through V7.0. Addendum #1
is intended for all DIGITAL OpenVMS system managers. This addendum
supersedes Security Bulletin 1997-02, dated 07 March, 1997.
DIGITAL OpenVMS has provided additional ECOs (Engineering Change
Orders) to remove the delta-time limit in OpenVMS/VAX versions prior to
V5.5. OpenVMS has also release ECO VAXLIBR06_070, which supersedes
VAXLIBR05_070. Addendum #1 contains additional and updated information
for obtaining and installing the appropriate ECO for both OpenVMS/VAX
and OpenVMS/Alpha systems. The full addendum can be obtained from The
Corporate Security internal WEB Site at URL
http://corpsec.mso.dec.com/ref-info.htm, or from the Security Advisory
Notefile at MINOTR::SECURITY_ADVISORY. Additional information
concerning the OpenVMS Delta-Time Limit Problem can be found at URL
http://www.openvms.digital.com/openvms/10k/index.html
CoC Managers hosting Contracted Personnel are responsible for
appropriate communication of this security bulletin addendum.
|
| 132.13 | UPDATE for V5.0 through V5.4-3 | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Thu May 15 1997 19:55 | 54 |
|
DESCRIPTION:
The ECOs for the older versions of OpenVMS (V5.0 through V5.4-3)
replace the existing LIBRT.EXE image with a new LIBRT.EXE.
IMPACT:
If a system has any customized versions of library routines in
the LIBRT.EXE image, those modifications will be lost.
SOLUTION:
This issue is clearly documented in the *.CVRLET_TXT files and
the Customer Letter publicly available on the WEB at URL
http://www.openvms.digital.com/openvms/10k/10kpre55.html
However, it was not highlighted in the CISG Security Bulletin
1997-02 Addendum #1.
Given the low probability of a user or 3rd party application
mis-using the Delta-Time function, system managers should be
sure they will have a problem before installing the ECO for
their system. Such problems should be limited to just the
application in question, and have no overall impact on system
functions.
If a system manager does install the ECO, and does lose
customized routines, (s)he will need to restore the old
LIBRT.EXE image from backup, or re-install the missing
customized routines.
If a system manager determines that they have an application
effected by the Delta-Time problem, they must consider one of
the following actions:
1. Discontinue use of the application
or,
2. Modify the application to handle time functions differently
or,
3. Install the ECO, then re-install customized library routines
or,
4. Upgrade to at least V5.5, then install the appropriate ECO.
Regards,
Chuck
Security Communication Program
Corporate Information Security
Chuck Noble, SCP Program Manager
noble@mail.dec.com
dtn 223-8728
Phone (508) 493-8728
FAX (508) 493-5464
|
| 132.14 | VAXeln Patch Information | MINOTR::NOBLE | Your Data, Your Job...Protect Both | Fri May 16 1997 13:17 | 300 |
|
This information was just received. The following reference
information is included in the body of the Customer Q&A section:
A: The patch will be on the DIGITAL web site at the following address:
http://www.digital.com/info/oem/software/vaxeln46-dt-update.zip
Q: How do I install the update?
A: The update is shipped in a "zip" file. You must have the VMS version
of the UNZIP utility installed on your system. For more information,
see the following web site:
http://www.openvms.digital.com/openvms/freeware/cd.html
CISG has no other information available at this time. Please contact
the DIGITAL VAXeln group with further questions -
Nancy Fredrickson, 237-2924, fredrickson@mail.dec.com
-<*>-
From: AESTLS::LPERUSSE "SUPAYwoman 15-May-1997 1659 -0600"
15-MAY-1997 16:59:46.97
To: @DSN$DBDATA:DSN$Flash_INTERNAL_RECIPIENT.DIS
CC:
Subj: DSNlink Flash for vaxeln
Dear Customer,
The following is important information about the product VAXELN.
Thank you,
Digital Customer Support Center
VAXELN Delta Time Limit Notification Cover Letter
May 1997
Dear VAXELN Customer,
The following is important information concerning a documented delta
time restriction in VAXELN.
The VAXELN operating system has a documented delta time limit that
may cause an error in some applications beginning on or around
19-MAY-1997. DIGITAL has provided an update to VAXELN V4.6 that
addresses some aspects of the delta time limit.
Applications likely to experience errors are those that pass delta
time arguments with values exceeding 9999 days to system-supplied
date routines. A possible date that these errors will occur is
19-MAY-1997, which is 10000 days after the common UNIX time origin
of 1-JAN-1970.
The following routines are affected:
LIB$SUB_TIMES
LIB$MULT_DELTA_TIME
LIB$MULTF_DELTA_TIME
LIB$ADD_TIMES
An update is available for VAXELN V4.6 which removes the restriction
for these routines. Please contact your normal DIGITAL support
channel for further information.
Routines that use ASCII delta time strings will not be updated. The
following routines accept or return ASCII delta time strings in
which the "Days" field must not exceed 9999 days.
ELN$TIME_VALUE
ELN$TIME_STRING
TIME_VALUE (EPascal and Ada only)
TIME_STRING (EPascal and Ada only)
SYS$BINTIM
SYS$ASCTIM
The remainder of this article provides detailed answers to questions
you may have concerning this issue. DIGITAL appreciates your
cooperation and patience. We regret any inconvenience applying this
update may cause.
Q: I've heard that certain VAXELN routines have a documented time
restriction that can cause errors in some applications. Can you tell
me more about this?
A: Some routines in the VAXELN operating system have a documented
limit of ten thousand (10000) days on delta times. Any software that
uses these routines to process a time interval of 10000 or more days
will encounter run-time errors upon reaching this limit. The date
19-May-1997 is 10,000 days from the UNIX and C base date of
1-Jan-1970. Applications using the routines with the delta time
restrictions in conjunction with the UNIX or C base date may
encounter problems with the conversion of the 19-May-1997 date and
later dates. These dates exceed 10000 days and exceed the documented
four-digit limit of the "Day" field in delta times. Other base dates
will encounter this ten-thousand day limit at other times. DIGITAL
has removed the 10000 day limit in some of the affected routines
with an update to VAXELN V4.6.
Q: What is a delta time?
A delta time is a time interval. An absolute time is a date. For
example, one second (0000 00:00:01.00) is a delta time and midnight
on May 19, 1997 (19-MAY-1997 00:00:00.00) is an absolute time. On
VAXELN, both are represented internally as a 64 bit count of clock
ticks. The LARGE_INTEGER data structure is provided for use with the
various routines which accept or return an internal time value.
Absolute times are not affected by this restriction.
Q: Why does the 10000 day limit exist in the first place?
A: It was a design decision made long ago. The format for the ASCII
representation of a delta time was defined to be "dddd hh:mm:ss.cc".
Delta times were never intended to be used for long periods of time.
On VAXELN, the most common use of a delta time is to pass to
ker$wait_any() to specify a short interval on which to delay.
Q: What are the VAXELN routines that have the 10000 day restriction?
A: The following routines have been updated to allow the internal
representation of a delta time to exceed 10000 days:
LIB$SUB_TIMES
LIB$MULT_DELTA_TIME
LIB$MULTF_DELTA_TIME
LIB$ADD_TIMES
The following routines will continue to have the restriction:
ELN$TIME_VALUE
ELN$TIME_STRING
TIME_VALUE (EPascal and Ada only)
TIME_STRING (EPascal and Ada only)
SYS$BINTIM
SYS$ASCTIM
Q: Why are some routines updated but not all of them?
A: The routines being updated deal strictly with the 64 bit internal
representation of time. An update is possible to these routines
without changing any data structures visible to user applications
and without causing any undesirable side effects. The routines which
are not being updated convert internal time to an ASCII string and
vice versa. DIGITAL believes that increasing the size of the string
which holds the ASCII representation (to add an extra "Day" digit)
could break more applications than it fixes. The size of the string
will remain unchanged for compatibility reasons.
Q: What are the symptoms of the problem on systems running VAXELN
V4.6 without this update?
A: If your application uses any of the routines being updated with a
delta time greater than 9999 days, an appropriate error status is
returned to the application indicating that an error has occurred.
An example of an application which might be affected is one which
attempts to convert the VAXELN representation of the current time
into a number of seconds since January 1, 1970. If it tried to
subtract the absolute time equivalent to January 1, 1970 from any
absolute time after May 19, 1997 (using LIB$SUB_TIMES, for example)
the result will be a delta time greater than 10000 days. An error
status will be returned by LIB$SUB_TIMES.
Q: For those routines which are not updated, what are the symptoms
of the problem and what can I do about it?
A: The restriction on the internal time to ASCII conversion routines
is well-documented on VAXELN. When these routines are supplied with
a delta time greater than 9999 days, an exception is raised
indicating the error. If your application uses these routines in
such an unsupported manner, it will have to be modified. This is a
permanent restriction.
Q: What if my application calls both the routines being updated and
the routines not being updated?
A: If your application calls any of the routines being updated with
a delta time greater than 9999 days, that call will succeed once the
patch has been applied. If you then pass that delta time to any of
the routines not being updated, it will fail as documented. The 9999
days limit is a permanent restriction for the mentioned time/string
conversion routines.
Q: Which versions of VAXELN are affected and who needs to install
the update?
A: Versions of VAXELN starting with V4.3 are affected. The LIB$
routines being updated were new in V4.3. DIGITAL recommends that all
customers running VAXELN V4.6 apply the update.
Q: What about versions V4.3, V4.4 and V4.5?
A: Only VAXELN V4.6 is currently supported. If you are running a
older version and have not updated for some reason, contact your
local DIGITAL office.
Q: If my application uses any of the routines being updated, what
changes do I need to make in my code as a result of this update.
A: None. This update removes a restriction in very specific areas
that previously would have generated an error.
Q: How will customers be notified?
A: Customers with current support contracts for VAXELN will be
notified that a patch exists for this problem with instructions on
how to obtain it.
Q: How do customers without support contracts obtain the update?
A: The patch will be on the DIGITAL web site at the following
address:
http://www.digital.com/info/oem/software/vaxeln46-dt-update.zip
Q: How do I install the update?
A: The update is shipped in a "zip" file. You must have the VMS
version of the UNZIP utility installed on your system. For more
information, see the following web site:
http://www.openvms.digital.com/openvms/freeware/cd.html
After you have installed UNZIP, you can extract the files to your
SYS$LOGIN directory like this:
$ SET DEF SYS$LOGIN
$ UNZIP VAXELN46_DT_UPDATE.ZIP
The following files will be extracted to your SY$LOGIN:
README.TXT ! this text
LIBMSC.EXE ! shareable library update
LIBSUBTIMES.OBJ ! object library update
To apply the update, first save the existing versions of
RTLSHARE.OLB, RTLOBJECT.OLB and LIBMSC.EXE in case you ever want to
revert to the pre-update behavior:
$ SET DEF ELN$
$ COPY RTLSHARE.OLB RTLSHARE.OLB_V46
$ COPY RTLOBJECT.OLB RTLOBJECT.OLB_V46
$ COPY LIBMSC.EXE LIBMSC.EXE_V46
Next, apply the patch:
$ SET DEF ELN$
$ LIB/REP RTLSHARE SYS$LOGIN:LIBMSC.EXE
$ COPY SYS$LOGIN:LIBMSC.EXE LIBMSC.EXE
$ LIB/REP RTLOBJECT SYS$LOGIN:LIBSUBTIMES.OBJ
Q: Does I have to do anything after the update has been applied?
A: Yes. After the update has been applied, the application must be
linked, the system image must be rebuilt and the target system must
be rebooted.
Q: Do I ever need to reapply this update once I have applied it?
A: If you ever choose to re-install VAXELN V4.6, the update needs to
be re-applied.
Q: How can the System Manager tell if the update has been applied?
A: LIBMSC.EXE has a unique "image file identification." To find it,
use the following command:
$ ANALYZE/IMAGE/INTER ELN$:LIBMSC.EXE
The "image file identification" will be under the "Image
Identification Information" section. The updated image
identification is "VAXELN V4.6-05."
LIBSUBTIMES.OBJ has a unique module identification. To find it, use
the following command:
$ LIB/LIST/FULL ELN$:RTLOBJECT
Look for the module "LIB$DATE_ARITHMETIC." The identification for
the updated version is "X-2."
Q: Does this update contain any other functional changes or bug
fixes to VAXELN V4.6?
A: No.
|
| 132.15 | V6.2-0HF forgotten | GADZUK::MEYER | | Mon May 19 1997 19:18 | 36 |
| For anyone attempting to install the ECO on V6.2-0HF, the following
note might help.
<<< PROXY::$7$DUA113:[NOTES$LIBRARY]FTVAX.NOTE;1 >>>
-< ftvax >-
================================================================================
Note 597.0 VAXft 810 and DELTA TIME problem No replies
PRSSOS::SPECTY "carpe diem" 28 lines Wed 14-May-97 12:29
--------------------------------------------------------------------------------
Hi,
There is a problem with VAXft 810 running VMS V6.2-0HF. If you
want to install the DELTA TIME patch ( VAXLIBR06_070 ) , the
KITINSTAL.COM is unable to recognize the VMS version and the
installation fails.
One workaround we found was to modify the KITINSTAL.COM file
by inserting one line as follows:
--------------------
$!
$! Since the V5 installation and upgrade produce special format
$! version numbers to identify the type of system we have, we
$! need to perform special version checks.
$!
$!
$ vms$version = f$edit (f$getsyi ("VERSION"), "TRIM")
$ vms$version = "V6.2" <-------that's it
$ vms$type_id = f$extract (0, 1, vms$version)
$ .............
----------------
The dead line for the patch is 19 May 1997 . Have fun,
Alain
|