VSSI Home
Product Support
Release 5.2.00 VTAPE updates.
Last modified on 07/05/07
There are several critical updates on the VSSI 293 FTP download disk.
You can change directories to that disk to download the required updates
We recommend you download the latest build and apply only updates that
apply to that build however you can download and apply all critical
updates for the build you are currently running.
The update descriptions and apply instructions are in the prolog of
the update file contained in the VMARC file on the 193 disk.
Update 520086 and above apply to build 5217
Update 520074 and above apply to build 5215
Update 520055 and above apply to build 5213
Update 520029 and above apply to build 5209
Update 520023 and above apply to build 5207
Update 520023 and above apply to build 5205
Update 520007 and above apply to build 5203
All updates apply to build 5200
VT520086 VMARC 3/23/07 23:54:02 * Remove vdev from CFG data sequence number
Update VT520086 applies to VSSI installation builds through 5217
Symptom: * Error after redefining a tape drive vdev to a new number
Description: The vdev was set in the VTAPE vdev extension block when
a drive was defined. The value in the extension block
was used as part of the manufacture sequence number in
the Read Configuration Data returned for an RCD CCW.
This caused a problem for TPF when a drive number was
redefined and later defined at the redefined address.
Resolution: The vdev number is now set for non-shared drives when the
RCD is received so it always reflects the current vdev
number. For shared drives the vdev number is not stored
in the manufacture sequence number because each shared
drive is assigned a unique sequence number when it is
defined.
VT520081 VMARC 3/06/07 12:07:32 * Lockout VTXSHRLK&VTABQLK Unload from RVTCCW
Update VT520081 applies to VSSI installation builds through 5215
Symptom: *
VT520081 5200 VT52081 * Lockout VTXSHRLK&VTABQLK Unload from RVTCCW
Description: HCPIOV acquired the share lock to serialize a VTAPE I/O.
VTQUERY ACTIVE ALL acquired the mounted tape queue lock
to display mounted tapes
VTQUERY ACTIVE atempted to acquire the shared drive lock
for every drive with a mounted tape to list any
shared drives and was waiting for the lock acquired
by HCPIOV
HCPIOV called by RVTCCW to handle an unload CCW and
RVTCCW called RVTREW to unload the tape
RVTREW atempted to acquire the mounted tape queue lock to
remove the tape from the mounted tape queue causing
the interlock
Resolution: This is a fix for users that do not use the shared tape
drive feature of VTAPE which is 99.9% of users. The share
drive feature was developed for a small subset of VTAPE
users to test shared drives between multiple z/OS systems.
The problem is the share lock was being acquired whether
the drive was defined as eligible to be shared or not.
This update tests the VDEV to determine if it was defined
with the share option and never acquires the share lock
if the drive was not defined as sharable.
A second update is being designed to correct the interlock
described above for users that use shared VTAPE drives.
Two other interlock situations for shared drives reported
by users that don't use shared drives have already been
corrected but no shared drive user has ever reported a
problem.
VS520074 VMARC 4/14/07 21:12:27 * Convert err in IOR does not return to caller
Update VS520074 applies to VSSI installation builds through 5214
Problem: * After the development for the architecural changes in
z/VM 5.2 for some errors the VPARS and VTAPE I/O modules
did not return to the call but only stacked the I/O error
to the interrupt address. This caused a hung user
situation.
Resolution: The I/O modules now stack the I/O interrupt and return to
call as they should.
VS520061 VMARC 11/18/06 10:25:46 * CMS modules built incorrectly in z/VM 5.1
Update VS520061 applies to VSSI installation builds through 5213
Symptom: *
VS520061 5200 VS52061 * CMS modules built incorrectly in z?VM 5.1
Description: VSSI version 5.2 incorrectly builds its CMS modules
in a z/VM 5.1 install. The resulying modules have
missing entry points and fail with a PRG001.
Resolution: The VSSASM and VSCMSBLD EXECs were corrected to work in
both z/VM 5.1 and 5.2
VT520060 VMARC 11/18/06 10:25:42 * HTT001 HCPENTER BASEREG s/b HCPENTER GOTO
Update VT520060 applies to VSSI installation builds through 5213
Symptom: *
VT520060 5200 VT52060 * HTT001 HCPENTER BASEREG s/b HCPENTER GOTO
Description: Two CPEBK return points were set up as BASEREG
instead of GOTO for entry type. This caused an
HTT001 when the CPEBK was unstacked.
Resolution: The HCPENTER type was changed to GOTO
VT520055 VMARC 11/08/06 10:33:06 * LCK003/PRG004 during VTRUN command
Update VT520055 applies to VSSI installation builds through 5213
Symptom: *
VT520055 4200 VT40132 * LCK003/PRG004 during VTRUN command
Description: After update VT400078 08/20/2002 a VTRUN specifying
a userid of the current user as other user branched
to the wrong label and the VDEV block scan was not
done so R6 was invalid.
Resolution: The code was updated to branch to the correct label.
VT520035 VMARC 7/16/06 11:46:24 * VTSABQLK not released during detach, lockout
Update VT520035 applies to VSSI install builds through 5208 for
VPARS and VTAPE users. 5209 for VTAPE only users.
Symptom: * Guests hung waiting for VTSABQLK lock.
Description: After update VT520023 was applied for an HTT001 problem
detach processing could exit without realeasing the
VTSABQLK. This caused all users that mounted a tape to
hang waiting for the lock.
Resolution: Change RVTSV2RS to always check for holding the VTSABQLK
before exiting.
VS520033 VMARC 6/28/06 13:14:09 * Rejcted I/O with SHARK in native mode
Update VS520033 applies to VSSI installation builds through 5209
Symptom: After IBM PTF H63855HP SLU UM31771 for PAV support all
VPARS and VTAPE CP CCW chains fail with a command reject
incorrect length indication on the Locate Record X'47'
CCW.
Description: The ESS(SHARK) control unit is set native mode after
PAV support is applied. VPARS and VTAPE were not
correctly setting up the I/O control blocks when the
control unit was set to native mode.
Resolution: VPARS and VTAPE no longer check the control unit type.
Support for any control unit that does not support
extended count, key, data has been removed.
VS520029 VMARC 6/21/06 7:53:28 * RVP/RVTIOR I/O error test invalid real address
Update VS520029 applies to VSSI installation builds through 5209
Problem: * I/O recovery fails in VPARS and VTAPE because compares
for the failing CCW are using virtual instead of real
storage addresses.
Resolution: The I/O error recovery code has been corrected to use
real storage addresses for the compares.
VT520023 VMARC 5/30/06 10:30:10 * HTT001 in RVSUTLMS called by AMNTED2 in RVTSCR
Update VT520023 applies to VSSI install builds through 5206 for
VPARS and VTAPE users. 5207 for VTAPE only users.
Symptom: * HTT001/STK017 Abend. These failures can only occur for
VTAPE drives shared by multiple guests.
Description: An HTT001 can occur if a guest participating in a
shared VTAPE drive configuration detaches their drive
or logs off while a tape mounted by another user is on
the drive. VTAPE reset code does not always remove the
detached VDEV from the chain of shared drives. When a
VTSCR or VTQ ACT is later issued the code attmpts to
process the released control blocks causing the HTT001.
The STK017 can occur when a VTCLOSE or System SHUTDOWN
is done after a released block has been left on the
queue, when VTAPE attempts to unload the device for
close.
Resolution: VTAPE reset code was changed to always remove the
detached VDEV from the VDEV extension block queue.
Code was also changed to correct a locking error
between the VTAPE device reset code and VTSCR and VTQ
ACT. Code was also changed to correct an error where
a VTQ ACT did not show a user an active tape on a shared
drive if that user did not issue the mount.
VS520011 VMARC 4/04/06 0:46:39 * VSSI utilities enter CP after update VS520007
Update VS520011 applies to VSSI installation builds through 5203
Symptom: * CP mode is entered when a VSSI CMS command is issued
requiring a Begin to continue.
Description: Update VS520007 left an extra DIAG X'A8' in VSSUBR
causing CP mode to be entered.
Resolution: The extra DIAG X'A8' was deleted.
VT520009 VMARC 3/22/06 18:16:19 * RVTQLB cleanup
Update VT520009 applies to VSSI installation builds through 5203
Symptom: * Logic errors in VTQuery LIbrary
Description: RVTQLB was doing mutiple scans of thr volume ranges
and reading directory blocks that were not required
for the requested volumes.
Resolution: Code in RVTQLB was was restructuredd to not scan the
ranges multiple times and only read required directory
blocks
VT520008 VMARC 3/22/06 18:16:15 * HTT001 abend in RVTQLB at +2D8
Update VT520008 applies to VSSI installation builds through 5203
Symptom: * HTT001 abend in RVTQLB
Description: RVTQLB was incorrectly setting up registers causing a
non CP owned page to be referenced.
Resolution: Code in RVTQLB was changed to correctly set up the
register
VS520007 VMARC 3/24/06 11:10:23 * Don't show set MDCACHE off messages
Update VT520007 applies to VSSI installation builds through 5200
Symptom: * MDCACHE set message for VSSI CMS commands.
Description: Code was added in VSSI version 5.2.0 to ensure MDISK
CACHE was off for VPARS amd VTAPE disks. The new code
caused a message to be issued for each mdisk being
processed.
Resolution: Code was added to suppress the CACHE messages.
VS520001 VMARC 1/13/06 19:02:36 * VSSLTAPE no value error volser s/b tvolser
Update VS520001 applies to VSSI installation builds through 5200
Symptom: * A no value error we encountered in user code in the
VSSLTAPE EXEC.
Description: MSG2301 Mount was using volser as a variable and all other
tape messages were using tvolser for the variable. This
caused confusion in the user interface code to the tape
management system.
Resolution: Set both the tvolser and volser variables to the volume
serial for MSG2301. This will not cause existing user
code that uses the volser variable to break but will allow
the tvolser variable to be used for all tape message
entries.