VSSI Home
Product Support
Release 5.3.00 VTAPE updates.
Last modified on 05/13/10
There are several critical updates on the VSSI 193 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.
VT530103 VMARC 4/26/10 9:14:51 * vtrest error when number of tape > 10
Update VT530103 applies to VSSI installation builds through 5314-15
Symptom: * VTREST error if restore tape number > 10
Problem: VTBKUP creates a cycle file consisting of up to 10
volume serials per line. A logic error in VTREST
causes VTREST to read the 11th tape volser from
the end of the first cycle file line, instead of from
the beginning of the 2nd line
(index (10) was off-by-one).
Resolution: Indexing fixed to point to proper volume serial in the
cycle file generated by VTBKUP.
Prereqs: VT530042
Coreqs: None
Toolmin: 49
Modules: VTREST
VS530102 VMARC 3/24/10 14:02:52 * Extended TRACE support
Update VS530102 applies to VSSI installation builds through 5314
Symptom: * Extended TRACE support
Problem: Extended TRACE APIs.
Resolution: Added extended TRACE APIs and new MACRO function
for extended TRACE support.
Before attempting to apply this PTF, you MUST:
. Download the latest VSTOOLS VMARC from the VSSI
FTP site (your_vssi_userid.193);
. VMARC UNPK VSTOOLS VMARC to your local
distribution disk.
Prereqs: VS530020
VS530033
VS530054
VS530058
VS530095
VS530099
Coreqs: None
Toolmin: 49
Modules: VSCLR
VSCPSTOR
VSMODID
VSSTOR
VSSTRC
VSSUBR
VSTRACE
VSTRCBK
VSXBLR
VSXCALL
VSXCREG
VSXENTR
VSXEXIT
VSXRID
VS53MAC
VT530101 VMARC 3/15/10 12:59:32 * IOR103/HTT001 ABENDs in RVTIOR
Update VT530101 applies to VSSI installation builds through 5312-13
Symptom: * IOR103/HTT001 ABENDs in RVTIOR
Problem: RVTIOR is attempting to schedule an I/O which
already appears scheduled (i.e., double-scheduling).
This error return CSWPRG (channel program check)
in the ORB returned to HCPHTT, which then promptly kills
CP.
Resolution: Comment out the setting of CSWPRG in the ORB,
and return only CE|DE|CUE (which are already set
by the error handling code).
Prereqs: VT530009
VT530014
VT530046
VT530070
VT530094
Coreqs: None
Modules: RVTIOR
VT530100 VMARC 2/15/10 6:06:22 * test fix drain pending status ssch cc=1
Update VT530100 applies to VSSI installation builds through 5312-13
Symptom: * test fix drain pending status ssch cc=1
Problem: VTBKUP process hung after VSSVTB2505E message.
VDEV 181 remains in a status-pending condition
until CP timeout.
Resolution: It appears that we are not clearing pending status
after SSCH returns CC=1 while attempting tape drive I/O. .
Code added to invoke TSCH after SSCH CC=1, for a
retry count of 20 times max. Each retry attempt will be
accompanied by VSSI message VSSVTB2505E (status-pending).
If the maximum retry is reached, a VMDUMP of the
user virtual machine is taken.
Prereqs: VT530059
Coreqs: None
Modules: VTBKVOL
VS530099 VMARC 2/18/10 15:23:30 * Inconsistent result with VPBKUP/VPREST cycles
Update VS530099 applies to VSSI installation builds through 5312
Symptom: * Inconsistent results with VPBKUP/VPREST cycles
Problem: Customer ran several VPBKUP/VPCLEAR/VPREST job cycles
with no intervening data modifications.
After several attempts, an IPL of TPF crashed
due to a record-not-found condition.
Resolution: This PTF adds diagnostic trace support to VPBKUP/VPREST.
If the (TRACE option is specified, the job will trace
VPARS control block to the VPBKUP or VPREST TRCLOG file
on the invoker's A-disk.
The TRCLOG files will by used by VSSI to further debug
this error.
Prereqs: VS530020
VS530033
VS530054
VS530058
Coreqs: None
Modules: VSSUBR
VS530095 VMARC 2/12/10 13:26:12 * Added VSIDENT macro
Update VS530095 applies to VSSI installation builds through 5310
Symptom: * Added VSIDENT macro
Problem: VSSI IDENT strings are not standardized across modules.
Resolution: Set framework for mass replacement of VSSI IDENT strings
across modules.
Prereqs: None
Coreqs: None
Modules: VSIDENT
VS53MAC
VT530098 VMARC 1/27/10 12:31:59 * PRG009 (divide by 0) at RVTQLB+8A2
Update VT530098 applies to VSSI installation builds through 5310
Symptom: * PRG009 (divide by 0) at RVTQLB+8A2
Problem: A VTAPE Query Library command failed during statistics
calculation after assembler label DETAIL6.
The tape block count derived from VTVVOLSZ is used
as a divisor to determine the TAPE FULL percentage
for the volume. VTVVOLSZ was 0 (i.e., an empty volume),
so a divide-by-zero exception was encountered.
Resolution: RVTQLB has been modified to check VTVVOLSZ prior to
the division. If the value is 0, the division is bypassed,
and the percentage is simply reported as 0%.
Prereqs: VT530006
VT530013
VT530014
VT530016
VT530057
Coreqs: None
Modules: RVTQLB
VS530094 VMARC 11/11/09 13:04:50 * Fix TPF IPL crash in RVPDBS
Update VS530094 applies to VSSI installation builds through 5310
Symptom: * Fix TPF IPL crash in RVPDBS
Problem: Various VSSI code points use the &HCPVRSN global
to determine pending actions.
This global is unsuitable for VSSI use,
especially if the z/VM level crosses a version
boundary, as the following example illustrates:
z/VM 5.4 = &HCPVRSN 'EME405'
z/VM 6.1 = &HCPVRSN 'EME106'
Any LT/GT compares between &HCPVERSN and a macro constant
may yield the wrong code, because the version numbers
are in RMV (Release/Modification/Version) order
instead of VRM order.
Resolution: Code added to generate and use the &VSSIZVM global
now built via the VSIPROLG macro. This global
is in VRM order, so LT/GT compares will work properly.
Prereqs: None
Coreqs: None
Modules: VSIPROLG
VT530094 VMARC 11/11/09 14:56:42 * Fix TPF IPL crash in RVPDBS
Update VT530094 applies to VSSI installation builds through 5310
Symptom: * Fix TPF IPL crash in RVPDBS
Problem: Various VSSI code points use the &HCPVRSN global
to determine pending actions.
This global is unsuitable for VSSI use,
especially if the z/VM level crosses a version
boundary, as the following example illustrates:
z/VM 5.4 = &HCPVRSN 'EME405'
z/VM 6.1 = &HCPVRSN 'EME106'
Any LT/GT compares between &HCPVERSN and a macro constant
may yield the wrong code, because the version numbers
are in RMV (Release/Modification/Version) order
instead of VRM order.
Resolution: Code added to generate and use the &VSSIZVM global
now built via the VSIPROLG macro. This global
is in VRM order, so LT/GT compares will work properly.
Prereqs: VT530009
VT530014
VT530046
VT530070
VS530094
Coreqs: None
Modules: RVTIOR
VT530093 VMARC 11/07/09 8:42:04 * Correct handling of residual count
Update VT530093 applies to VSSI installation builds through 5310-11
Symptom: * Correct handling of residual count
Problem: incorrect block size when reading tapes with
blocksize=32768.
copytape uses data chained ccws with data count=32k
with number of ccw's large enough to read the largest
specified tape data block.
when tape blocksize=32k and more that 2 data chained
ccws are used, copytape computes the blocksize
as 32k+32k+32k instead of 32K+32k-32k.
Resolution: residual count computations are now taking into
account the possibility of the field sgiresct (2 bytes)
to be equal to x'8000'. Halfword instructions are no
longer used.
Prereqs: *
VT530042
VT530055
VT530082
Coreqs: None
Modules: COPYTAPE
TBROWSE
VS530090 VMARC 11/06/09 17:09:04 * Fix MDLAT z/VM version check logic
Update VS530090 applies to VSSI installation builds through 5310
Symptom: * Fix MDLAT z/VM version check logic
Problem: MDLAT macros had incorrect version checking
which broke across versions.
Resolution: Fixed macro logic to check for correct v.r.m.
Prereqs: VS530030
Coreqs: None
Modules: RVSMDLAT
VT530090 VMARC 11/06/09 17:09:04 * Fix MDLAT z/VM version check logic
Update VT530090 applies to VSSI installation builds through 5310
Symptom: * Fix MDLAT z/VM version check logic
Problem: MDLAT macros had incorrect version checking
which broke across versions.
Resolution: Fixed macro logic to check for correct v.r.m.
Prereqs: None
Coreqs: None
Modules: RVTMDLAT
VT530088 VMARC 10/14/09 10:37:42 * Fix crash if VTAPE lib mdisk full (final)
Update VT530088 applies to VSSI installation builds through 5310-11
Symptom: * Fix crash if VTAPE lib mdisk full (final)
Error: VTAPE running for a VSE guest crashes if writing
to a library minidisk which is already full.
RVTDBMWC attempts to allocate the library database
block.
Resolution: 1. Several modules modified to truncate volume size
if minidisk is running short on free blocks.
2. Minidisk per-tape free block threshold increased
from 32 to 255.
Prereqs: VT530006
VT530014
VT530017
VT530035
VT530047
VT530070
VT530073
Modules: RVTCMD
RVTDBM
RVTMET
RVTSUM
RVTSV1
RVTSV3
VT530082 VMARC 10/14/09 10:37:42 * COPYTAPE fails to stop if lib mdisk near full
Update VT530082 applies to VSSI installation builds through 5310-11
Symptom: * Force COPYTAPE termination if minidisk full
Error: COPYTAPE continued to attempt data writes
after receiving EOR signal (i.e., lib disk full).
Resolution: This fix forces COPYTAPE termination if EOR
(Channel-End, Device-End, Control-Unit-End,
Unit Exception).
Prereqs: VT530042
VT530055
Modules: COPYTAPE
VT530075 VMARC 10/14/09 10:37:42 * Control blocks not cleared after HCPGETST
Update VT530075 applies to VSSI installation builds through 5310-11
Symptom: * Control blocks not cleared after HCPGETST
Error: Several control blocks were not cleared after HCPGETST,
causing spurious bits which were set ON,
and subsequent logic errors.
Resolution: RVTMNT modified to clear VTACTBK storage after HCPGETST.
Prereqs: VT530014
VT530064
Modules: RVTMNT
VS530074 VMARC 10/18/09 14:54:09 * Tape expiration date invalid if past 2041
Update VS530074 applies to VSSI installation builds through 5310-11
Symptom: * Vtape expiration date calculations
Problem: When expiration date for a tape volume is after 2041,
computations are wrong, and tape shows as expired.
RVTSCR will scratch such non-expired volumes.
Resolution: z/VM uses STCK instruction to obtain the value of TOD
clock. STCK returns unsigned 8-bytes integer in clock
unit resolution since 1900, that will wrap around 2041.
Vtape volumes have TOD for the creation date and a keep
value (retention in days) that is a halfword with max
value up to 32767 which is about 89 years.
A. RVTSCR is corrected to first determine the difference
between the current time and a volume creation time
in clock units, then this value is converted to days
and the result is compared with the keep value.
Such computations avoid overflow.
B. CMS data extract module VTRPT1 is changed to
request all the computations to be done in
microseconds, not in clock units, thus avoiding
overflow. It also has been changed to report
all 5 possible digits of a KEEP value, instead
of 4.
C. VSSUBDT utility (CMS) has 2 new functions added
to support necessary time computation requests
from VTPRT1.
D. RVTMSG (CP VTAPE message repository) is updated
to display all 5 possible digits of a KEEP value
larger than 9999 (only 4 digits were displayed).
E. VTQRPTS copy with mapping macros is updated to
support VTRPT1 updates.
Prereqs: None
Coreqs: None
Modules: VSSUBDT
VT530074 VMARC 10/18/09 15:06:29 * Tape expiration date invalid if past 2041
Update VT530074 applies to VSSI installation builds through 5310
Symptom: * Vtape expiration date calculations
Problem: When expiration date for a tape volume is after 2041,
computations are wrong, and tape shows as expired.
RVTSCR will scratch such non-expired volumes.
Resolution: z/VM uses STCK instruction to obtain the value of TOD
clock. STCK returns unsigned 8-bytes integer in clock
unit resolution since 1900, that will wrap around 2041.
Vtape volumes have TOD for the creation date and a keep
value (retention in days) that is a halfword with max
value up to 32767 which is about 89 years.
A. RVTSCR is corrected to first determine the difference
between the current time and a volume creation time
in clock units, then this value is converted to days
and the result is compared with the keep value.
Such computations avoid overflow.
B. CMS data extract module VTRPT1 is changed to
request all the computations to be done in
microseconds, not in clock units, thus avoiding
overflow. It also has been changed to report
all 5 possible digits of a KEEP value, instead
of 4.
C. VSSUBDT utility (CMS) has 2 new functions added
to support necessary time computation requests
from VTPRT1.
D. RVTMSG (CP VTAPE message repository) is updated
to display all 5 possible digits of a KEEP value
larger than 9999 (only 4 digits were displayed).
E. VTQRPTS copy with mapping macros is updated to
support VTRPT1 updates.
Prereqs: VT530006
VT530014
VT530035
VT530039
VT530042
VT530043
VT530061
VT530073
Coreqs: None
Modules: RVTMSG
RVTSCR
VTQRPTS
VTRPT1
VT530073 VMARC 10/14/09 10:37:42 * Fix crash if VTAPE lib mdisk full (interim)
Update VT530073 applies to VSSI installation builds through 5310-11
Symptom: * Fix crash if VTAPE lib mdisk full (intermim)
Error: VTAPE running for a VSE guest crashes if writing
to a library minidisk which is already full.
RVTDBMWC attempts to allocate the library database
block.
Resolution: RVTDBMWC modified to check available minidisk blocks
prior to data write attempt. If the per-tape
minimum block threshold has been reached,
the EOT (VTAFLG1.VTATPIND) and Allow Write Tape Mark
(VTAFLG3.VTAEOTM) flags will be set, causing
Recovery routines to present a unit check
(i.e., EOT) to the guest, rather than a crash.
A subsequent guest Write Tape Mark (WTM)
(such as done by MVS and VSE guests)
will be allowed if the library minisk has
more than 0 blocks available.
Additional EOT flag added to VTACTBK.VTAFLG3 to indicate
that EOT reached (i.e., disallow data writes to the tape)
but WTM OK (allow TM|EOF1|EOF2|TM to the tape).
Prereqs: VT530014
VT530035
VT530039
VT530043
VT530061
VT530070
Modules: RVTCCW
RVTCMD
RVTDBM
RVTMSG
VTACTBK
VT530070 VMARC 10/14/09 10:37:42 * LCK001 trying to release IOT lock in RVTDBM
Update VT530070 applies to VSSI installation builds through 5310-11
Symptom: * LCK001 trying to release IOT lock in RVTDBM.
Error: RVTDBM can follow a code path that tries to unlock a
VTIOTBK Vtape buffer when it is not held. The
timer-driven routine at RVTDBMRT branches to an incorrect
label when a call to RVTIORTR to trans and lock a buffer
is not successful. RVTIORUL can decrement the VTILKCNT
twice in the code path that's followed for an unsuccessful
call to get a buffer frame and lock it in real storage.
Resolution: The I/O return address code at RVTDBMRD is updated to make
sure the lock is held before trying to release it. The
code at RVTDBMTM is updated to branch to the correct label
in case of an I/O error at CKDOIO2.The code at RVTIORUL
is updated to remove the extra decrement.
Prereqs: VT530009
VT530014
VT530046
Modules: RVTDBM
RVTIOR
VT530066 VMARC 11/02/08 10:34:47 * VTADD space bit map & volume directory errors
Update VT530066 applies to VSSI installation builds through 5308-9
Symptom: * VTADD space bit map error or volume directory I/O errors
Error: Incorrect setup of the new library disk blocks caused
VTADD to fail with errors processing the space bit maps
for any disk and copying the volume directory when adding
linrary disk 2
Resolution: The new library disk block values are now set correctly.
VS530065 VMARC 11/02/08 10:33:55 * Allow parameters on VSASMACP & VSASMALL execs
Update VS530054 applies to VSSI installation builds through 5304
Symptom: * CP assembly errors when a use set COMPAT(SYSLIST)
as a default HLASM option
Problem: * This caused CP assemblies to fail using normal SES
or VSSI assembly exec and PPF files.
Resolution: VSVMFASM was updated to force the COMPAT option to
NOCOMPAT unless COMPAT is specified on the VSSI assemble
EXEC. VSASMALL and VSASMACP have been updated to allow
assembler options.
VT530064 VMARC 10/17/08 21:58:51 * Use HCPSTKIO for unsolicited interupt
Update VT530064 applies to VSSI installation builds through 5308-9
Symptom: * Guest hang doing VTRUN after SPXTAPE DUMP command
Error: An error was found in VTRUN were the IORSNS flag was
turned on when the drive did not support concurrent
sense
Resolution: The IORSNS set was moved to follow the test for concurrent
sense support.
VS530058 VMARC 11/27/09 15:21:16 * Library status processing error "Not Defined"
Update VS530058 applies to VSSI installation builds through 5306-7
Problem: * Library not defined in system error message.
Cause: * Update VT530033 to VSSUBR for routine VSCNVTDB was using
R2 which cause an error wnen routine VSLSTST called
VSCNVTDB
Resolution: VSLSTAT now uses R4 to svoid the conflict with VSCNVTDB
VT530057 VMARC 3/20/08 1:00:25 * HTT001 in RVTQLB after update VT530006 VTQ LIB n
Update VT530057 applies to VSSI installation builds through 5306-7
Problem: * HTT001 hard abend in VTQuery LIbrary nn after update
VT530006.
Description: Update VT530006 used R14 as a work regester after it had
already been initilized for another routine.
Resolution: R14 is now correctly initialized after the VT530006 code
has executed.
VT530055 VMARC 1/30/08 11:23:56 * >65535 byte records for COPYTAPE & TBROWSE
Update VT530055 applies to VSSI installation builds through 5304-5
Problem: * COPYTAPE does not support blocks larger than 65,535 bytes.
Resolution: COPYTAPE has been updated to support any size block up to
the size of your available machine size. A new BLKsize
option has been added to specify the largest block size
on the input tape. The value you specify with the BLKsize
option is in K bytes (value*1024) so a value of 128 would
be 131,072 bytes. The default maximum BLKsize value
64K, 65,536 bytes.
VT530047 VMARC 11/17/07 0:13:06 * UE not presented early enough Ldisk low
Update VT530047 applies to VSSI installation builds through 5304-5
Prereq: Update VT530017 is a prereq for this update
Problem: * Tape unloaded instead of presenting unit exception when
space on library disk gets low.
Description: The routine that checks for low available space when a
block is allocated on a library disk was allowing for 8
library blocks per mounted tape. A user had 1 output tape
mounted and was writting 65K tape blocks so the library
disk filled up before the current block finshed being
written to present unit exception.
Resolution: This update changes the blocks reserved for completing
a write when a library disk is getting low on space to
32. A 65K block takes a maximum of 16 library blocks
to contain the data so 32 should be sufficient to correct
the problem. I believe the error might still occur if
a user coded a channel program that used chain data to
write a >128K tape record and there was only one output
tape assigned to the library disk.
VT530039 VMARC 5/04/08 10:24:51 * Updates for SPXTAPE processing
Update VT530039 applies to VSSI installation builds through 5304-5
Problem: * Hangs and other problems using SPXTAPE to VTAPE
VT530006.
Resolution: Extensive testing was done on SPXTAPE and all reported
and other problems found were corrected.
VT530017 VMARC 11/16/07 21:18:03 * Block alloc incorrectly calculates % in use
Update VT530017 applies to VSSI installation builds through 5304-5
Problem: * Percent full value for over 90% full somtimes incorrectly
calculated.
Description: The routine that calculates the percent full number for
the over 90% full message did not always correct number
Resolution: This update corrects the percent number calculation
for the message
VT530046 VMARC 11/13/07 23:45:21 * I/O errors on last library cylinder
Update VT530046 applies to VSSI installation builds through 5304-5
Problem: * I/O errors on last cylinder of ne format library disk
Description: The end of extent in the DE plist for the library disk was
set incorrectly. The head number was to set zero instead
of the last track of the cylinder.
Resolution: This update correctly sets end of extent.
VT530016 VMARC 7/09/07 17:00:46 * HTT001 VTQ LIB and missing library disk
Update VP530016 applies to VSSI installation builds through 5304-5
Problem: * HTT001 in VTQ LI for an input library when disks are
missing.
Description: A user added 4 new disks to their output library but
didn't update the config and directory on a second system
that opens the library for input. A fix for this problem
was written over a year ago however one of the compares in
the fix was comparing the requested disk number to the
maximum library disks and doing a branch high. Because
the library disks have a base of zero and the maximum
disk count has a base of one, the branch should have
been a branch not low.
Resolution: This update changes the branch from a BH to a BNL to
the error routine for the missing disk.
VT530013 VMARC 7/03/07 22:29:43 * VTQ LI nnn-nnn incorrect output
Update VP530013 applies to VSSI installation builds through 5304-5
Problem: * Incorrect output from VTQ LIB nnn-nnn if an empty
volume directory block is encountered.
Description: In testing VTQ LI nnn-nnn I found if an empty directory
block is encountered when displaying a range it stops
the query for that range.
Resolution: This update corrects VTQ to correctly handle ranges
that start with or span and empty directory block.