----------------------------------------------------------------------------

VCR AMENDMENT NOTICES SINCE PRODUCT ISSUE

This file contains a summary of all VCR 1.2 Amendment Notices published
since VCR 1.2 was issued. The most recent notices are described first.

Most of these notices include a software amendment.

----------------------------------------------------------------------------

Amendment number: 133                               Date:  19 December, 1997

RE: Ultracomp VME Products and the ICL Year 2000 Enabling Kit

Ref:  ICL PC-Paris SKE 93697

Describes a problem caused by the ICL Year 2000 enabling kit and proivides
a solution.

----------------------------------------------------------------------------

Amendment number: 132                              Date:  25 September, 1996

This amendment introduces three new VCR commands that enable the VME-VCR
log file to be accessed.  The commands are:

             UC_VCR_OPEN_LOG
             UC_VCR_READ_LOG
             UC_VCR_CLOSE_LOG

Further details on these commands can be found in a seperate document,
reference: VCRP132.

----------------------------------------------------------------------------

Amendment number: 129                                Date:  10 January, 1996

There is a problem with the VCR command UCV_SIGNAL_EVENT that can cause the
following program error:

PROGRAM ERROR TYPE 30 SUBTYPE 1 - SYSTEM CALL
MODULE: ICL8UCV0MAINT
IIN: 5
DISPLACEMENT: 00003E26

This is due to signal event attempting to use a RAM currency that no longer
exists.  This amendment corrects this problem by resetting the RAM currency,
if the file is not currently assigned.

----------------------------------------------------------------------------

Amendment number: 125/1                              Date:  7 December, 1995

This amendment corrects a problem that occurs following an execute action
from a VCR secondary responder which causes the wrong VCR event to be
displayed.


This amendment replaces version 0, which had an error that could cause the
following messages to be reported in the VCR session journal:

    UC_READ_LOG: BLOCK NUMBER OUT OF RANGE
    UC_READ_LOG: ACTION: 141
    UC_READ_LOG: REQUESTED BLOCK: -1
    UC_READ_LOG: REQUESTED BYTE: nnn
    UC_READ_LOG: LAST WRITTEN BLOCK: n
    UC_READ_LOG: RESULT CODE: 20007

----------------------------------------------------------------------------

Amendment number: 128                               Date:  23 February, 1995

In the VME Vigilant Collector/Responder (VC/R) system, if a failure occurs
when writing to the system control file, then the system appears to hang,
without reporting any problems to either the screen or the current session
journal.

This amendment corrects this problem, by reporting any system control write
failures to the current journal and to the VC/R screen.

----------------------------------------------------------------------------

Amendment number: 126                                 Date:  3 October, 1994

There is a problem with VCR that can cause the event log files to become out
of step with the values held in the VCR control record, i.e. the control
record does not contain the actual highest generation number.

This occurs if a new checksum is applied using UCV_DATE_CHANGE, whilst a
primary responder is running. 

This amendment corrects this problem.

----------------------------------------------------------------------------

Amendment number: 121                               Date:  November 11, 1992
          
There is a problem in VCR that can cause UCV_SIGNAL_EVENT to fail with a
permissions failure on the UCV_LOG_FILE due to the way the next generation
of the file is created.


This amendment corrects this problem.

----------------------------------------------------------------------------

Notice number: 120                                  Date:  November 20, 1991
          
There is a problem in VCR which results in a responder running in secondary
mode not recognising the creation of a new log file, also UCV_SIGNAL_EVENT
fails to close the control file at the end resulting in a failure message
in the jobs journal.

This amendment corrects these problems, it also removes some unnecessary
messages from UCV_SIGNAL_EVENT.

----------------------------------------------------------------------------