You are encouraged to keep your z/VSE system on a healthy service level. In order to do that it is recommended to update you z/VSE system to stay on a supported release and service level.
For information on how to order and apply PTFs please refer to the How to order page.
|May 1, 2015||z/VSE 5.2.0 & 5.1.2 RSL updated to the Apr 30, 2015 level.|
|March 23, 2015||HIPER APAR PI35643/PI35642 DATA SEQUENCE ERROR WHEN USING Z/VSE FAST PATH TO LINUX ON SYSTEM Z:
In case you are using the z/VSE Fast Path to Linux on System z (LFP) ensure that PTF UI25399/UI25398 for APAR PI35643/PI35642 is installed. This PTF updates the Linux Fast Path daemon (LFPD). Make sure that you download the WBOOK IJBLFPLX.W and update the LFPD on Linux (using rpm -u). You can also download the latest LFPD code here.
|Dec 31, 2014||z/VSE 5.2.0, 5.1.2 & 4.3.1 RSL updated to the Dec 31, 2014 level.|
|Dec 18, 2014||Impact of POODLE (CVE-2014-3566) on z/VSE (PDF, 105KB)|
|October 31, 2014||z/VSE V4.3 end of service|
|Jul 1, 2014||z/VSE 5.2.0, 5.1.2 & 4.3.1 RSL updated to the Jun 30, 2014 level.|
|May 30, 2014||z/VSE 5.2.0 RSL has been added at the May 23, 2014 level. z/VSE 5.1.2 RSL & z/VSE 4.3.1 RSL updated to the May 16, 2014 level.|
|May 23, 2014||The IJSYSPF file (used to apply service from disk) was delivered with an incorrect definition on z/VSE 5.2. In order to apply service from disk it is necessary to redefine this file prior to service application. This can be done by changing and then submitting skeleton SKPTFILE in library 59 from:
RECORDSIZE (80,10320) - RECORDFORMAT(FIXBLK(10320)) -to
RECORDSIZE (80,10320) - RECORDFORMAT(FIXBLK(80)) -This skeleton is corrected in PTF UI17100. Once the IJSYSPF file has been redefined, if a PTF is to be transferred using TCP/IP the file must be transferred as follows:
ftp> binary <-- switch to binary mode 200 Command okay. ftp> quote site recfm fb <-- record format of your file 200 Command okay. ftp> quote site lrecl 80 <-- record size of your file 200 Command okay. ftp> quote site blksize 10320 <-- blocksize of your file 200 Command okay. ftp> put ptffile.bin PTF.FILE <-- enter your filenamesNote: If you used FSU to upgrade to z/VSE 5.2, then this skeleton SKPTFILE may not be available in your library 59. You can then use this job to restore it from the z/VSE 5.2 base tape. After you have restored it, you need to change it as described above and then submit it to redefine IJSYSPF.
|May 9, 2014||APAR DY47526 is available for z/VSE 5.1. It solves a problem created by a fix in error for DY47507, which results in error message MSG4228I RC X'22' VOLSER IN DLBL NOT MATCH CATALOG DEFINITION. This code is in the base of z/VSE 5.2 and the APAR DY47537 is available for z/VSE 5.2.|
|April 25, 2014||IBM z/VSE V5.2 is now available|
|Feb 15, 2014||z/VSE 5.1.2 RSL & z/VSE 4.3.1 RSL updated to the Jan 31, 2014 level.|
|Dec 1, 2013||z/VSE 5.1.2 RSL & z/VSE 4.3.1 RSL updated to the Oct 31, 2013 level.|
|Nov 13, 2013||Important info on APAR PM80542/UK91650
With APAR PM80542/UK91650, which was included in z/VSE 5.1.2 Upgrade, the transaction security phase DTSECTXN was delivered by error. This phase will get active in the system replacing transaction security settings for IBM provided transactions in case the new security concept based on BSTCNTL definition is used. If not yet migrated to the new concept it will even replace all customer defined transaction security settings.
In case the new concept is used (you can find out using IUI dialog 285, you will not get migration offered) delete DTSECTXN.PHASE from IJSYSRS.SYSLIB.
If the old concept is used, there should be the original phase stored in PRD2.SAVE, the new (IBM transactions only) phase in IJSYSRS.SYSLIB. It is recommended to merge the new IBM definition into existing setup as follows:
|Sep 30, 2013||z/VSE 5.1.2 RSL & z/VSE 4.3.1 RSL updated to the Aug 31, 2013 level.|
|June 28, 2013||z/VSE 5.1.2 RSL added & z/VSE 4.3.1 RSL updated to the June 18, 2013 level.|
|May 24, 2013||z/VSE 5.1.1 RSL & z/VSE 4.3.1 RSL updated to the April 9, 2013 level.|
|Oct 31, 2012||PM75512: RPG II users should apply PTF UK83060 when migrating to z/VSE V5.1. Batch RPG II applications that use the SETLL operation may abend or have unpredictable results when accessing VSAM control blocks in 31 bit storage.|
|Oct 31, 2012||z/VSE V4.2 end of service|
|Jul 26, 2012||PM67737: Customers who have developed, maintained or rebuilt COBOL/VSE applications on z/VSE 5.1 prior to installing UK80309 should apply this APARs PTF and then re-link all z/VSE 5.1 updated COBOL/VSE applications. COBOL/VSE applications that have not been linkedited on z/VSE 5.1 are not affected and do not require any action. APAR PM69182 is available for z/VSE 4.3 COBOL/VSE users as a preventative solution.|
|Jun 21, 2012||FSU from 5.1.0 to 5.1.1.
enter 0 exit r rdr,pausefsu 0 ALLOC BG=16M 0 SIZE BG=1280K 0 r rdr,dtrfsuab ... 0 resumeIf this does not work and M063 is still issued, enter
l rdr,dtr*and reipl from DOSRES and coontinue with step 1 above. The whole FSU needs to be rerun in this case.
|Jun 15, 2012||z/VSE V5.1.1 is now available|
|Sep 27, 2011||Important z/VSE V4.3 migration considerations regarding recoverable VSAM catalogs|
|Aug 12, 2011||z/VSE V4.3.1 is now available|
|Aug 2, 2011||Effective October 31, 2012, z/VSE V4.2, CICS/VSE V2.3, DL/I V1.10 and DL/I V1.11 will be withdrawn from service|
|Nov 26, 2010||z/VSE V4.3 is now available|
|Oct 14, 2010||New z/VSE Problem Determination Guide is available|
|Jul 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.
IBM z13 delivers a data and transaction system reinvented as a system of insight for digital business.