Product Support

Version 55 Availability

Concurrent with the General Availability (GA) release of z/VM 6.2, VSSI announces the immediate availability of Version 55 of our product suite (VPARS and VTAPE). 

Summary of Changes for Version 55

.       Version 55 supports all z/VM releases from 5.4.0 thru 6.2.0.

.       This version implements a new software licensing scheme. Each registered user of VSSI products will need to download the following files from the VSSI FTP site:
        .       The software package (via public userid.191 MDISK; e.g., ZVM620 VPVT5502)
        .       The license file (via private userid.192 MDISK).
               (e.g., if your userid is VPnnnnyy, download and expand Pnnnn.VMARC;
                if your userid is VTnnnnyy, download Tnnnn.VMARC).
        After download, the license file needs to be copied to the VSSI CP PARM disk as VSSI LICENSE. The product will not run without a valid VSSI license file.
        The software license code uses the customer license key to check the VSSI expiration date
        and/or running machine CPUID, as follows:
        License Type            Duration   CPUID_Checked
        Trial                           60 days       No
        1-Machine                 1 year          Yes
        2-Machine                 1 year          Yes
        3-Machine                 1 year          Yes
        Site                            1 year          No 

        The following actions are taken based on the number of days remaining until expiration:
        Days Remaining                  Action
        Greater than 30 days                  No action, no messages;
                                                        processing continues
        Between 30 and 15 days          Warning message written to OPERATOR console;
                                                        processing continues
        Between 14 and 0 days           Critical message written to user and OPERATOR consoles;
                                                        processing continues
        Between 0 and -30 days          Critical message written to user and OPERATOR consoles;
                                                        processing continues
        Greater than -30 days           Critical message written to user and OPERATOR consoles;
                                                        soft ABEND issued.                            
.       This version is designed to support a CPXLOAD/CPXUNLOAD environment.
        The code will be automatically loaded during an IPL; additionally, VSSI modules can now be dynamically loaded and unloaded by the Systems Administrator after IPL via the VSCPX EXEC,
        by component, as follows:

        Component               Load Command            Unload Command

        VSSI Common     VSCPX ENAble VS   CF1   VSCPX DISAble VS   CF1
        VPARS           VSCPX ENAble VP   CF1   VSCPX DISAble VP   CF1
        VTAPE           VSCPX ENAble VT   CF1   VSCPX DISAble VT   CF1
        All                     VSCPX ENAble ALL CF1    VSCPX DISAble ALL CF1

        The VSCPX EXEC is copied to the specified PARM disk; you can use it by
        accessing the PARM disk in read-only mode after IPL.
        For CF1 above, substitute your CP PARM disk virtual address. On z/VM 6.2,
        the primary PARM disk is typically PMAINT CF0, not MAINT CF1 as set
        in prior z/VM releases.

        VSSI has moved the bulk of product code to a TXTLIB used by the CPXLOAD commands in VSSI
        PARM disk CONFIG files to load the system. Several critical stub files, however, remain in the
        CP Nucleus (NUC). Future maintenance of the stub file code will require a system reboot;
        all of the TXTLIB code (approximately 95% of the code base) will not require a z/VM IPL.

        This approach is designed to reduce or eliminate the number of CP BLDNUC and subsequent
        re-IPL disruptions required by the application of VSSI fixes.

.       This version is designed to support a CPEXIT environment. All hooks to IBM
        HCP modules, as well as all cross-component VSSI module calls, have been converted
        to CPEXIT calls. This conversion makes it possible for the customer to disable/enable
        VSSI exits (via the VSCPX EXEC described above) while the system is still running.

.       All previous fixes applied to VSSI version 53xx have been applied to this release.

.       The VSSI build EXECs have been upgraded to support a CPXLOAD environment.
        For example, the VSCOPY EXEC now invokes a new EXEC, VSBLDCFG, to copy
        generated CONFIG files to the appropriate PARM disk. Additionally, many EXEC build
        messages have been improved for clarity. 

.       This version does not yet support the SSI facility in z/VM releases 6.2 and above;
        SSI support is forthcoming shortly.

.       This version drops previous requirements for modification of the DIRECTXA module.
        Previous VSSI DIRECTXA modifications involved the support of SPECIAL statements
        for VTAPE devices (e.g., V3480) in the user directory, which is no longer necessary
        since IBM provided directory COMMAND support. All users are therefore requested to
        change any directory SPECIAL VTAPE directory statements (e.g., SPECIAL V3480)
        to CMD DEFINE type (e.g., CMD DEFINE V3480) statements.

System Requirements

        Hardware:       zSeries Processor or higher
        Software:       z/VM 5.4 or higher
                        HLASM 1.5 or higher (HLASM 1.6 or higher is highly recommended)