Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 - Manual (Page 281)

PĆ3 Version Control Library (VCL)
Error Handling during a Snapshot Operation
If an error occurs during the processing of a snapshot operation, an error
message will be displayed and the snapshot operation will be aborted. If an error
occurs while executing one of the DOS files spawned by the Snapshot command,
the user will be returned to Windows and an error message will be displayed. If
PVCS fails, the error message will state that PVCS failed and will direct the user to
the file PVCS.OUT, which is contained in the AutoMax workspace subdirectory
(typically AMXWORK). This file will contain a message describing why PVCS
failed. If PVCS did not fail, the user will receive an error message stating only that
the snapshot operation failed. The AutoMax library will remain intact, but the VCL
may contain only a part of the complete snapshot. If the token was being
transferred, it will remain with the source copy of the files unless the snapshot is
completed successfully. After determining the cause of the failure, you should
execute the snapshot again to ensure that the VCL contains a complete and
accurate snapshot.
Tokens and Locking during a Snapshot Operation
If the Move Tokens to VCL check box is selected (checked), then all the tokens in
the AutoMax library within the scope of the snapshot will be transferred to the
Version Control Library. If the token for the system, section, or rack has a
password, the password will be prompted for before the token is transferred to
the VCL. However, the user may not write over any tokens already in the Version
Control Library. For example, suppose that a user is snapshotting a system with
three racks and he has tokens for two of the racks, but the token for the third rack
is in the VCL. When he tries to snapshot the system, he will receive an error
message telling him that he is trying to write over a system that has its token in
the Version Control Library. The snapshot will be aborted before anything is
snapshot. The user will need to fetch the third rack from the VCL with the token
before he will be allowed to snapshot the system. If the token were held by
another user and not the VCL, the snapshot would be successful.
Locks are taken out in the Version Control Library for any system, section(s),
rack(s), and task(s) (SSRT) that are being snapshot. For example, if a user is
snapshotting a system with two racks that belong to the same section, a lock will
be taken out in the Version Control Library for the system, section, and each rack.
No one else can snapshot the system, section, or either rack until the first user's
snapshot is complete. A lock is also taken out in the AutoMax library so that the
SSRT cannot be modified during the snapshot.
Retrieving Files from the Version Control Library
The Fetch command allows the user to retrieve versions of the system files from
the Version Control Library. Fetch can be performed at any level to retrieve a
single system, section, rack, or task. Fetch can only be used with no SSRT
selected or one SSRT selected. In addition, the user cannot fetch the SSRT
unless there is exactly one SSRT selected in the levels above. For example, if two
sections are multiĆselected, or if no sections are selected, Fetch will be disabled
under the Rack menu. This rule applies at all levels except the system level.
The same procedure is used to fetch systems, sections, racks, and tasks. Read
the remainder of this section carefully before executing the Fetch command.
System, rack, and task database files in the AutoMax library can be modified or
deleted by the Fetch command.
Step 1. Select Version Control Library from the System, Section, or Rack
menus in the System Configurator, or from the Tasks menu in the Task
Manager.
Step 2. Select Fetch from the subĆmenu. The Fetch dialog box will be displayed.
If an SSRT was selected, its name will be displayed in the dialog box. If