3.3 is what we are working with .. z/VM 5.3 901 .. This is not at my location but at a sister company.
-----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Edward M Martin Sent: Wednesday, August 26, 2009 11:30 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: CA VTERM Hello Tom, I am on z/5.3 but what is your service level? CAMC CA-VTERM 3.3 0110MC33 3.3 0110MC33 3.3 0110MC33 Ed Martin Aultman Health Foundation 330-363-5050 ext 35050 -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Huegel, Thomas Sent: Wednesday, August 26, 2009 12:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: CA VTERM Anyone successfully running CA-VTERM on z/VM 5.4? It seems to work fine on 5.3 and on 5.4 if the virt size is =>24m. On 5.4 if the virt size is > 24m a lot of bad stuff happens. DMSABE141T Protection exception occurred at 00E7E094 in routine RXPANMAN CMS Strange, but I can get by this by doing FLIST and BROWSE any file.. then re-execute VTERMM. Then when I exit I get the good stuff. DMSFRR818E Attempt to RELEASE free storage in subpool DMSBLOKU actually owned by DMSUSRM DMSABE152T System abend 0F8 called from 010725E8 while UFDBUSY = 01; re-IPL CMS HCPGIR450W CP entered; disabled wait PSW 000A0000 00F5438E Not really sure if it is CA or IBM that is the culprit.
