|March 10, 2014||Update available for z/VSE's PAV (Parallel Access Volume) support:
APARs DY47396 (for z/VSE 4.3) and DY47501 (for z/VSE 5.1) address and correct several problems in z/VSE's support for PAV (Parallel Access Volume) devices. If you are using or plan to use PAV devices with z/VSE it is strongly recommended to apply these APARs.
|July 5, 2013||Improved Stand-Alone Dump Program
APAR DY47471 addresses several problems in the Stand-Alone dump program. After installing PTF UD53951 a rebuild of the Stand Alone Dump program on disk and/or tape is required.
In IUI select
4 Problem Handling then 6 Dump Program Utilities then 1 Create Standalone Dump Program on Tape or 2 Create Standalone Dump Program on Diskto create a job which will rebuild the Stand-Alone dump program and for disk reformat the IJSYSDU dump file.
|July 15, 2009||Updated list of PTFs for ACF/VTAM V4.2 31-bit I/O Buffer support
In 2006 IBM introduced the ACF/VTAM V4.2 31-bit I/O Buffer support. This support needs additional PTFs for its full functionality. For a complete list of PTFs for z/VSE 3.1 or z/VSE 4.1 or z/VSE 4.2 see here.
|May 28, 2009||Support for PAV is now available
Parallel Access Volume (PAV) is an optional licensed feature of the IBM System Storage DS8000 and DS6000, and IBM TotalStorage ESS series. It enables a single System z server to simultaneously process multiple I/O operations to the same volume.
PAV support is now available in z/VSE V4.2 with APAR DY46953/PTF UD53399 (01C) and UD53400 (01J).
Note: When running under z/VM and using z/VM's PAV minidisk support the ALIAS minidisks must be defined in the CP Directory for the guest (MINIOPT PAVALIAS). Using the CP command DEFINE PAVALIAS to dynamically define an alias might lead to z/VSE system hangs.
|June 18, 2007||The IBM System Storage TS1120 Tape Drive encryption feature support is now available for z/VSE V4.1 and V3.1.
Following APARs/PTFs must be installed to activate the support:
|April 13, 2007||Error in z/VSE 4.1 when trying to load DLA on disk
When using an old $0JCL from a previous release with
1S40I SYSTEM ERROR, LABEL RET.CODE=0E REASON CODE=06 1S40D SYSTEM ERROR, LABEL RET.CODE=0E REASON CODE=04Circumvention: remove the
CATALOG $0JCL.PROC DATA=YES REPLACE=YES STDOPT ACANCEL=NO,DECK=NO,DUMP=PART,... SYSDEF DSPACE,DSIZE=12M // EXEC PROC= STDLABEL (remove this statement) // VDISKUNIT=FDF,BLKS=2880,VOLID=VDIDLA,... * VDISKUNIT=CUU,BLKS=81920,VOLID=VDIWRK // EXEC PROC=STDLABEL CALLS STDLABUP AND ... // EXEC PROC=SETSDL SET SDL
|July 28, 2006||Installing Generation Feature may remove UD52824:
During installation of the VSE generation feature under releases z/VSE 3.1.1 or z/VSE 3.1.2, the PTF UD52824 is accidentally being removed from the MSHP history file, but the corrected code by UD52824 remains applied and intact. However, any subsequent installation by PTF UD52908 or any other PTF with a PRE REQ requirement of UD52824 will fail. Therefore, this archive job will provide the resolution to the above stated MSHP problem.
|July 21, 2006||z/VSE V3.1.2:
z/VSE V3.1.2 is now available. It contains hardware support and functional enhancements first introduced in z/VSE V3.1.1. z/VSE V3.1.2 contains accumulated service since the z/VSE V3.1 GA in March 2005.
Note: Special instructions have been provided that describe detailed procedures for a) an FSU, or b) a new install of z/VSE V3.1.2. It is essential that users follow correct procedures to make the process as smooth as possible and to avoid any possible loss of existing definitions.
|February 13, 2006||New ACF/VTAM V4.2 31-bit I/O Buffer support for z/VSE V3.1:
In the current ACF/VTAM implementation, VTAM I/O buffers use 24-Bit System Getvis storage. For some customers, this restriction creates a storage constraint. Customer requiremens (e.g. WAVV200414, WAVV200311, WAVV200242, WAVV200224) have requested that IBM allows to move these I/O buffers 'above the line' (into 31-Bit System Getvis storage).
IBM's response is the VTAM 31-Bit I/O Buffer Support in z/VSE 3.1. With this new function, ACF/VTAM can move I/O buffers (IOBUF pool) and all I/O CTC packing buffers in 31-Bit System Getvis storage (VTAM startup option IOBUF31=YES). This enhancement allows z/VSE customers to grow their communication workloads.
To use this support PTF UD52873 and PTF UD53035 (AF Base) or UD52874 and UD53060(Generation Feature) must be applied to z/VSE V3.1. In addition PTF UD52964 and PTF UD53054 must be applied to ACF/VTAM V4.2.
|February 9, 2006||With z/VSE 3.1.1, initial installation may fail, first IPL goes into a loop:
A few users experienced problems with the initial installation of z/VSE V3.1.1. For technical details and a local fix see here (PDF, 8KB). As a result, we developed a solution (APAR DY46515). We applied the APAR and replaced the z/VSE V3.1.1 tapes at the distribution centers as of February 8.
z/VSE V3 customers fall into three groups:
Last update: September 1, 2014
|UD54054-52S||Security fixes for OpenSSL (CVE-2014-3509, CVE-2014-3511)|
|UD54037-52S||Security fixes for OpenSSL (CVE-2014-0224)|
|UD54027-52S||Security fixes for OpenSSL (CVE-2014-0160)|
|UD54022-52C||Message 0S39I ERROR DURING OSA EXPRESS PROCESSING,REASON=0102 when two devices are configured in IJBOCONF with global VLAN.|
|UD54010-52C||Asynchronous EZASMI function calls like CONNECT, READ, and WRITE for non-blocking sockets do immediately return with the given ECB unposted.|
|5686-CF9-07||52C||VSE/AF 9.2 MSHP|
|5686-CF9-08||52C||VSE/AF 9.2 Info/Analysis|
|5686-CF9-09||52C||VSE/AF 9.2 IOCP|
|5686-CF9-06||52J||VSE/AF 9.2 Generation Feature|
|5686-CF9-06||52G||VSE/AF 9.2 Macros|
|5686-CF9-17||52S||z/VSE Cryptographic Services|
|5686-CF9-40||52Y||Encryption Facility for z/VSE|
The IBM zEnterprise System extends modern mainframe capabilities for enterprises of all sizes to help cut costs, improve service, and fuel innovation for business growth.