VSSI Home
Product Support
Release 5.3.00 VPARS/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.
VP530104 VMARC 5/13/10 15:22:45 * cycle file processing by vprest
Update VP530104 applies to VSSI installation builds through 5314
Symptom: * cycle file processing by vprest
Problem: VPBKUP creates a cycle file consisting of up to 9
volume serials per line. A logic error in VPREST
causes VPREST 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 (9) was off-by-one).
Resolution: Indexing fixed to point to proper volume serial in the
cycle file generated by VPBKUP.
Prereqs: VP530007
VP530042
VP530056
VP530099
VP530102
VS530102
Coreqs: None
Toolmin: 49
Modules: VPREST
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
VP530102 VMARC 3/24/10 14:02:52 * Extended TRACE support
Update VP530102 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: VP530007
VP530042
VP530045
VP530056
VP530099
Coreqs: VS530102
Toolmin: 49
Modules: VPBKUP
VPREST
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
VP530099 VMARC 2/18/10 15:23:30 * Inconsistent result with VPBKUP/VPREST cycles
Update VP530099 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: VP530007
VP530042
VP530045
VP530056
Coreqs: None
Modules: VPBKUP
VPREST
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
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
VP530097 VMARC 12/09/09 13:38:28 * Error in NOBASE restore
Update VP530097 applies to VSSI installation builds through 5310
Symptom: * Error in NOBASE restore
Problem: the VPBXREST utility allows the user to specify
a record exclude file containing the 2-digit record IDs
of records to be bypassed during database restore from
a TPF (BXA) tape.
No specification was provided for specifying hexadecimal
IDs in the file; VPBXREST always assumes normal
character data; each line in the exclude file is thus
converted to upper case prior to validating the
record IDs. The current method thus trashes
manually-inserted hexadecimal data
(i.e., record ID X'8102' becomes X'C142', which is
probably what the user wants).
Resolution: VPBXREST has been modified to accept hexadecimal
record IDs via support of any of the following
character strings representing hex data; e.g:
. 8102X
. 0X8102
. X'8102'
Character data record IDs coded in one of the above
formats will be converted to the proper hexadecimal
representations in the internal exclude record ID
table entries.
Prereqs: VP530033
VP530059
Coreqs: None
Modules: VPBXREST
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
VP530094 VMARC 11/11/09 14:56:42 * Fix TPF IPL crash in RVPDBS
Update VP530094 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: VP530001
VP530003
VP530009
VP530010
VP530011
VP530012
VP530014
VP530015
VP530018
VP530024
VP530026
VP530028
VP530030
VP530031
VP530032
VP530034
VP530036
VP530041
VP530060
VP530062
VP530069
VP530089
VS530094
Coreqs: None
Modules: RVPCCW
RVPCSP
RVPDBS
RVPIOR
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
VP530092 VMARC 11/06/09 17:15:26 * VPSET ECHO ON causes NOBASE init failure
Update VP530092 applies to VSSI installation builds through 5310
Symptom: * VPSET ECHO ON causes NOBASE init failure
Problem: VPSET ECHO ON command causes TPF BASE reads to be
written to the VPARS database, thus allowing the user
to capture both read and write data in VPARS
(e.g., to build a complete NOBASE system).
ECHO ON is inapplicable in an existing NOBASE environment
because there is no BASE system to echo.
Resolution: Configuration and VPSET modules have been modified to
turn ECHO OFF unconditionally in a NOBASE environment.
If the user attempts a VPSET ECHO ON in a NOBASE
environment, the following warning message is issued:
RVPxxx225W - NOBASE and ECHO are mutually exclusive;
ECHO set OFF.
Prereqs: VP530010
VP530025
VP530027
VP530049
Coreqs: None
Modules: RVPMSG
RVPPRC
RVPSET
VP530091 VMARC 11/06/09 17:09:23 * Fix PRG001 in RVPDBT+6B4
Update VP530091 applies to VSSI installation builds through 5310
Symptom: * Fix PRG001 in RVPDBT+6B4
Problem: This error occurs during a database queue add failure.
Several statements branched to label QAERROR, which was
commented out by PTF VP530071.
Resolution: This PTF modifies all such branches to label QADDX97,
which will generate a soft ABEND instead of the
hard DBT002 ABEND.
Prereqs: VP530053
VP530071
Coreqs: None
Modules: RVPDBT
VP530090 VMARC 11/06/09 17:09:04 * Fix MDLAT z/VM version check logic
Update VP530090 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: VP530001
VP530030
VP530031
Coreqs: None
Modules: RVPMDLAT
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
VP530089 VMARC 11/06/09 17:08:56 * Remove NOP CCW address validation code
Update VP530089 applies to VSSI installation builds through 5310
Symptom: * Remove NOP CCW address validation code
Problem: VPARS validating CCW address even if NOP CCW.
Resolution: Validation now bypassed if NOP CCW,
since NOP addresses are not used anyway.
Prereqs: VP530001
VP530012
VP530024
VP530030
VP530031
Coreqs: None
Modules: RVPDBS
VP530071 VMARC 11/06/09 17:08:14 * Avoid CP crash if index queue updates fail
Update VP530071 applies to VSSI installation builds through 5310
Symptom: * Avoid CP crash if index queue updates fail
Problem: VPARS crashes with a hard CP ABEND if an index
record insert is requested, but the corresponding
index slot is already occupied.
This action crashes the entire VM machine.
Resolution: Change the hard ABEND to a soft ABEND.
This circumvention avoids penalizing the
uninvolved users.
The root cause for this issue may in fact be
previous data corruption via VPBKUP/VPREST;
this issue is under investigation, and subsequent
fixes may be forthcoming.
Prereqs: VP530001
VP530003
VP530010
VP530011
VP530014
VP530015
VP530018
VP530019
VP530026
VP530027
VP530030
VP530031
VP530036
VP530053
VP530060
VP530063
Coreqs: None
Modules: RVPDBM
RVPDBT
VP530069 VMARC 11/06/09 17:07:50 * Force VP1WRKBK clear
Update VP530069 applies to VSSI installation builds through 5310
Symptom: * Force VP1WRKBK clear
Problem: VP1WRKBK was not cleared after an HCPGETST.
Since HCPGETST does not guarantee 0-filled storage,
some requests returned memory where the FBA flag was
set, resulting in FBA logic exercised against
non-FBA disks.
Resolution: MVCL added after VP1WRKBK HCPGETST.
Prereqs: VP530003
VP530010
VP530015
VP530018
VP530031
VP530032
VP530034
VP530041
VP530060
Coreqs: None
Modules: RVPCCW
VT530088 VMARC 10/14/09 11:03:29 * 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 11:03:29 * 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 11:03:29 * 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:06 * 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:22 * 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 11:03:29 * 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 11:03:29 * 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.
VP530062 VMARC 7/26/08 12:31:41 * Errors processing trk zero, NOBase/REQOL
Update VP530062 applies to VSSI installation builds through 5306
Symptom: * Invalid count data length on read CKD '1E' when
open for nobase and record is not on VPARS.
Problem: * This code has been bad since VSSI version 4.2 in VM/ESA
2.4 through z/VM 4.4.
Resolution: Calculate count field length from CCW data length minus
count field length and key length. Maximum data length
for label record 80 bytes.
HCPDTD32 VMARC 10/29/08 18:21:54 * Sequence error after I64347HP
Update HCPDTD32 applies to z/VM 5.3.0 VSSI install builds through 5309
Symptom: * Sequence error appling VTAPE update after IBM PTF
I64347HP UM32474
Resolution: The Sequence numbers were changed in the VSSI update to
accommodate the IBM PTF.
HCP54VT2 VMARC 9/19/08 0:38:11 K53002VT * SPXTAPE LOAD tape error ind
Update HCP54VT2 applies to z/VM 5.4 builds through 5308-09
Symptom: * Tape I/O error indication during SPXTAPE LOAD function.
Description: An LRA needed to be a LA if the restore was from a virtual
tape.
HCP53VT2 VMARC 9/19/08 0:38:07 I53002VT * SPXTAPE LOAD tape error ind
Update HCP53VT2 applies to z/VM 5.3 VSSI builds through 5308-09
Symptom: * Tape I/O error indication during SPXTAPE LOAD function.
Description: An LRA needed to be a LA if the restore was from a virtual
tape.
HCP52VT2 VMARC 9/19/08 0:38:02 H53002VT * SPXTAPE LOAD tape error ind
Update HCP52VT2 applies to z/VM 5.2 VSSI builds through 5308-09
Symptom: * Tape I/O error indication during SPXTAPE LOAD function.
Description: An LRA needed to be a LA if the restore was from a virtual
tape.
VP530060 VMARC 7/13/08 17:24:34 * IL not preserved if SILI flag off
Update VP530060 applies to VSSI installation builds through 5306
Symptom: * Zero residual when SILI flag not set.
Problem: * If the SILI flag is off and a long read is done for a
record on thge VPARS database, the residual count gets
set to zero in the IORBK
Resolution: Ensure that VP1RESCT always contains the residual count so
the correct value is stored in IORCNT.
VS530058 VMARC 11/27/09 15:21:10 * 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.
VP530056 VMARC 2/23/08 11:14:51 * Checkpoint flag turned off by VPREST
Update VP530056 applies to VSSI installation builds through 5306
Symptom: * Checkpoint flag off after VPREST restore of checkpointed
database
Problem: * Code added to support VPARS databases on FBA disks
was causing the flag to be altered.
Resolution: The checkpoint flag is now correctly maintained during the
restore.
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.
VS530054 VMARC 1/30/08 10:35:00 * Misc. CMS utility corrections VSSUBR, VPFMT
Update VS530054 applies to VSSI installation builds through 5304
Symptom: * MIsc. errors in VPFMT and VSSUBR
Problem: * VPFMT was checking for a two instead of a zero to
terminate the format during the request to verify.
The VSSUBR routine that converts decimal values to binary
was doing a compare on the length register to a halfword
constant for maximum input length. It should have been a
compare halfword.
Resolution: Both coding errors have been corrected.
VP530048 VMARC 11/19/07 23:42:59 * I/O err, wrong end extent value set in DE plist
Update VP530048 applies to VSSI installation builds through 5304
Symptom: * I/O error using VPUTIL MOVE function
Problem: * The end of extent in the Define Extent plist was being
set to the end of the VPARS disk instead of the TPF
disk.
Resolution: The DE end of extent is now set to the same CCHH as the
value as the DE start of extent and seek address in the
Locate Record plist. Code to List the CCWs and their data
areas when an I/O error occurs that was used to diagnose
this problem is also included in this update.
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.
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.
VP530045 VMARC 11/13/07 23:44:50 * VPBKUP with VTAPE option fails
Update VP530045 applies to VSSI installation builds through 5304
Problem: * VPBKUP keyword VTAPE was incorrectly changed to CONVTAPE
making the option unavailable unless you specify CONVTAPE
as the option.
Resolution: The keyword definition has been changed back to VTAPE.
VP530041 VMARC 11/05/07 22:34:06 * Alignment error in VPCHCCW for E7 prefix plist
Update VP530041 applies to VSSI installation builds through 5304
Symptom: * VPARS incorrect output when using prefix CCWs.
Problem: An update in VSSI v520 caused an alignment error in the
VPCHCCW block. A fullword between the E7 prefix plist
and DE plist cause data to be in the wrong fields.
Resolution: An alignment fullword was added in front of the E7 plist
to make it start in the second word of a double word.
VP530040 VMARC 11/06/07 8:35:00 * Corrections to parm processing PFXSYSMP -> VM
Update VP530040 applies to VSSI installation builds through 5304
Symptom: * PRG004 using private VPARS parm disks.
Problem: A change in VSSI R530 to use the SYSTEMMP VMDBK instead of
the SYSTEM VMDBK caused a PRG004. Config processing from
a parm disk must run master only.
Resolution: PFXSYSMP was changed back to PFXSYSVM to ensure master
only processing. This update also changes the way VPACC
works to make it more like CPACC. VPACC now allows you to
re-access the private parm disk after a config file change
without first using VPREL to release system access to the
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.
VP530029 VMARC 8/09/07 22:57:40 * Hung user doing VPSET CHK LOC/LCK lockout
Update VP530029 applies to VSSI installation builds through 5304
Problem: * Hung user doing VPSET CHKPOINT if a buffer release
occurs at the same time.
Description: A new symbolic lock to serialize command functions
was also being acquired by the buffer release routine.
VPSET CHKPOINT was holding the RDQ lock and attempting to
acquire the symbolic lock. The buffer release routine
was holding the symbolic lock and attempting to acquire
the RDQ lock.
Resolution: The buffer release routine is not a command function and
no longer acquires the symbolic lock
VP530024 VMARC 8/04/07 19:55:15 * PRG005 in RVPDBS retrieving data from IDA addr
Update VP530024 applies to VSSI installation builds through 5304
Problem: * PRG005 in RVPDBS with PTV mode set on.
Description: There is an error in the routine that retrieves data to
determine if a record should be recorded in the PTV
directory. A bad value in register 2 cause the failure.
Resolution: The code that retrieves the data has been corrected.
VP530023 VMARC 8/01/07 19:24:22 * Handle unformatted tracks in VPBLDFMT
Update VP530023 applies to VSSI installation builds through 5304
Symptom: * VPBLDFMT I/O errors on unformatted tracks and track
zero range.
Problem: If there is a large unformatted area on the disk many
I/O errors are issued. An error in the code also caused
a range to be built for track zero.
Resolution: A range is now build for unformatted tracks with a
record length of zero and the word unformatted is added
to that range display. A return code of 4 is returned at
end of the build. The range for track zero has also been
corrected.
VP530022 VMARC 7/28/07 10:10:49 * VPUTIL move fails invalid DE block size
Update VP530022 applies to VSSI installation builds through 5304
Symptom: * Error writting to TPF disks during VPUTIL MOVE
Problem: An update in the VSSI 530 code deleted the store of the
record length into the Define Extent plist causing a
Unit check with invalid track format sense data.
Resolution: The store of the record length was put back into the
VPUTIL I/O code.
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.
VP530015 VMARC 7/05/07 20:24:35 * X'1E' read CKD fails with incorrect length
Update VP530015 applies to VSSI installation builds through 5304
Problem: * X'1E' read CKD fails for track zero
Description: The record number was being set in the wrong field do to
changes in field use.
Resolution: Changes were made to all 4 modules that referenced the
incorrect field.
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.