PTF Install Instructions
Program Temporary Fix (PTF) Install Instructions:
VSSI product update files are available for download from our FTP site.
These fixes are distributed in VMARC format, and require the public-domain
VMARC program to unload (VMARC is included by VSSI as part of the product package distribution). All VSSI customers have been assigned a userid and password for access to this facility. You can request your userid and password by sending a request to support @ vsoftsys.com. VSSI maintains a VMARC file called VSTOOLS VMARC on the VSSI FTP site. This package contains the latest version of the VSSI BUILD EXECs (which change quicker than the actual product code), and is always available. All users should download the latest VSTOOLS VMARC from your 193 folder before attempting to apply the latest PTFs.
PTF Packages
VSSI maintains two types of PTF packages (PTF summaries viewable on the VSSI Web site www.vsoftsys.com):
- Single PTFs
Each PTF update can be downloaded separately (see PTF File Name and Format below) - Cumulative PTF Packages
All PTFs for a given package build are bundled in a VMARC file called prdvvvv PTFCUM, where:
prd is the product (VPVT for VPARS/VTAPE, VT for VTAPE-only, VD for ShadowDisk/Z)
vvvv is the build version (e.g., VPVT5514 contains cumulative PTFs for VPARS/VTAPE package
build 5514).
The CUM packages are refreshed each time VSSI Support posts a PTF to the Web site; they save you the hassle of downloading PTFs one at a time for your build.
PTF File Name and Format:
A VSSI PTF is named Vxvvnnnn VMARC (e.g., VP550012 VMARC), where:
x is the product component ID; e.g:
S for VSSI Common code
P for VPARS
D for ShadowDisk/Z
T for VTAPE
vv is the applicable product version (e.g, 55 for Version 55)
nnnn is the PTF number
The VMARC file contains the UPDATE file used to control the update process.
It may also contain any additional files required to complete the update (e.g., Object-Code-Only (OCO) TEXT files, new MACRO/COPY files).
Each VSSI PTF UPDATE contains the following prolog comment lines,
as shown by the prolog for VP550012:
Update VP550012 applies to VSSI installation builds through 5500
Symptom: * Handle IOT double-dequeue
Problem: A VPARS IOT was dequeued twice. The existing code checks for a valid buffer address at VTIREALA and ABENDs if an invalid address was found. The customer dump indicated a VTIREALA address of x’FFFFFFFF’, indicating that the IOT was already dequeued (probably by another virtual machine using the same IOT).
Resolution: Added logic to check for an invalid VTIREALA address and bypass the dequeue operation instead of generating a hard ABEND.
Prereqs: VP550008 VP550009 VP550010
Coreqs: None
BUILD_Reqd: VSSICP
Toolmin: 118 (2011-05-12)
Modules: RVPDBM ASSEMBLE RVPIOR ASSEMBLE
The prolog contents consist of the following sections:
| Section | Usage | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Title | The title line details the PTF number and applicable package version, as follows: Update As shown above, ptfid is the PTF filename, and vssi_ver is the applicable 4-digit VSSI product package release number (package version in the first 2 digits, and package build number in the last two digits). Build numbers for VPARS and ShadowDisk/Z packages are even, and build numbers for VTAPE-only packages are odd. You should only download PTFs which apply to your installed version (e.g., a PTF named VS55nnnn applies to Version 55, and not to any other VSSI product version). For PTFs applicable to the installed product version, the PTF should be downloaded and installed if you have a VSSI package build with a build number less than or equal to the PTF build number (the last 2 digits of vssi_ver); if you have a VSSI product package with a build number greater than the PTF build number, the PTF is already included in that package by VSSI Support, and you may therefore safely ignore the PTF. Users can determine their installed package version and build numbers via the vsqpkg EXEC, as follows: vsqpkg (no parameters required) |
||||||||||
| Symptom | Summary description of the issue addressed by this PTF | ||||||||||
| Problem | Detailed description of the issue addressed by this PTF | ||||||||||
| Resolution | Description of the code fixes required to address the issue | ||||||||||
| Prereqs | Any pre-requisite PTFs required by this PTF | ||||||||||
| Coreqs | Any co-requisite PTFs required by this PTF | ||||||||||
| BUILD_Reqd | The actions required to install this PTF:
|
||||||||||
| Toolmin | The minimum level of the VSTOOLS package required to install the PTF; the latest VSTOOLS VMARC file can be found on the FTP server, under your 193 directory |
||||||||||
| Modules | A list of modules affected by this PTF |
Download the PTF and/or VSTOOLS files from VSSI:
FTP to ftp2.vsoftsys.com
USER: your_VSSI_userid
PASSWORD: your_VSSI_password
BINARY
CD your_VSSI_userid.193
GET fn.ft
QUIT
Install the PTF or PTFCUM Package:
- If you downloaded one or more PTFCUM files, you can do as follows:
If not already done, move the PTFCUM file(s) to your A-disk.
VSFMTARC downloaded_package PTFCUM A (for each PTFCUM file)
Apply the Cumulative maintenance:
VSPTFCUM 55nn (55nn = the last 4 PTFCUM filename characters)
Proceed at step 7 below. - If you downloaded one or more single PTFs, the downloaded elements may have PREREQ/COREQ requirements for other PTFs. You can check this as follows:
If not already done, move the PTF file(s) to your A-disk.
vsptfreq nn (where nn is the highest PTF ID that you downloaded; e.g., vsptfreq 65)
This EXEC will issue a short report telling you which PTFs you may be missing. - If your VSTOOLS VMARC package is dated prior to Toolmin above:
Download the latest VSTOOLS VMARC from the FTP site (ftp2.vsoftsys.com, 193, BIN).
Unpack the VSTOOLS VMARC file to your VSSI installation disk (typically, disk G):
vmarc unpk vstools vmarc * = = g (repl - Access your VSSI install disk as your G-disk.
- Access the VSSI and CP maintenance disks:
VSSETUP (NOPPF - Apply the PTF(s):
VSPTF (with no parameters; all accessed PTFs evaluated)
or
VSPTF n1-n2 (all PTF IDs within numeric range n1-n2 evaluated) - If you get error messages complaining about missing or insufficient VSTOOLS build levels:
Perform step (3) above.
Restart at step (6) above. - Execute the VSSIPREP command to prepare for the remaining build tasks.
- Perform the following actions:
VSBLDNUC (build CP nucleus; if VSSIPL indicated)
VSCOPY NUC (copy NUC to CP PARM disk; if VSSIPL indicated)
VSCOPY CMS (copy CMS modules to installation shared CMS disk; if VSSICMS indicated)
VSCOPY HELP (copy VSSI HELP files to installation shared CMS disk; if VSSICMS indicated) - If VSSICP is indicated, and no IPL was required, use the VSCPX EXEC to unload and reload the VSSI CP modules. You will need to ensure that all VPARS, ShadowDisk/Z, and/or VTAPE users are inactive prior to the unload.