|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) // VDISK UNIT=FDF,BLKS=2880,VOLID=VDIDLA,... * VDISK UNIT=CUU,BLKS=81920,VOLID=VDIWRK // EXEC PROC=STDLABEL CALLS STDLABUP AND ... // EXEC PROC=SETSDL SET SDL
|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 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:
|November 25, 2005||z/VSE V3.1.1:
z/VSE V3.1.1 is now available. It contains hardware support for the IBM z9-109, TS1120 Tape Drive, IBM 3953 Tape System and 3584 Tape Library, as well as FCP/SCSI qualification of DS6000 and DS8000 disks. In addition, z/VSE V3.1.1 contains significant enhancements to the VSE Basic Security Manager. Several VSE/POWER enhancements are included as well. z/VSE V3.1.1 contains accumulated service since z/VSE V3.1 GA in March 2005. For more information, please see the z/VSE V3.1.1 Release Guide.
Note: Special instructions have been provided that describe detailed procedures for a) an FSU, or b) a new install of z/VSE V3.1.1. 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.
|November 25, 2005||Under certain circumstances PTF application may fail:
z/VSE 3.1.0 and VSE/ESA 2.7 customers running with the Generation Feature installed, may encounter message
|March 4, 2005||FSU from VSE/ESA 2.6 or 2.7 to z/VSE V3.1
Please read the important FSU information (PDF, 13 KB) before performing a Fast Service Upgrade to z/VSE V3.1.
Last update: Nov 25, 2014
|UI21979-52C||TCPIP delete Job DELTCPIP from ICCF LIB 59 uses wrong VSE Lib PRD1.BASE instead of PRD2.TCPIPC and wrong COMPONENT-ID and CLC|
|When updating an existing USER RECORD, E.G. modifying 'RECEIVE NEWS' from YES TO NO, the 'PROGRAMMER NAME' is not retained.|
|UI19157-52C||SEVERAL PROBLEMS WITH CSD SETUP AND BSM SETUP
|UI18749-52C||SKPTFILE MISSING IN IMVERUP
FSU version upgrade does not restore SKPTFILE member. CSD definition for IESSCCIC defined incorrectly with RELOAD=YES.
|UI17100-52C||REENTRANT PARAMETER MISSING FOR C/VSE COMPILE SKELETON
REENT parameter missing in C compile skeleton for online programs. PTF file defined with wrong BLKSIZE During initial install and FSU version/release upgrade IJSYSPF file is defined with BLKSIZE 10320. This requires that FTP is done with appropriate BLKSIZE parameter. But old definition FIXBLK(80) is the better solution. Use skeleton SKPTFILE in ICCF 59 to redefine the file. Compile skeletons for CICS programs should generate reentrant code.
|5686-CF9-01||52C||VSE/SP Unique Code|
|5686-CF9-02||52E||z/VSE MRI Japanese|
|5686-CF9-02||52D||z/VSE MRI English|
IBM z13 delivers a data and transaction system reinvented as a system of insight for digital business.