Re: Prog 754 on Graphic device 2nd level zVM 5.2
5 years ago or more, a response from Alan about using NOTN3270E, solved a problem for me, altho I don't remember what the problem was. I think that at the time, he said that NOTN3270E really only applied to using printers and I think that I saw something to that effect in the TCP/IP Planning and Customization manual. SInce then I have, just as a matter of course, always included that parameter in PROFILE TCPIP. I don't know why z/OS has or had anything to do with it. I wasn't doing anything at the time that involved z/OS. Jim At 11:12 AM 9/6/2006, you wrote: On Wednesday, 09/06/2006 at 10:05 EST, Bob Forward <[EMAIL PROTECTED]> wrote: > On some older 3270 devices, any PROG7xx status was due to a program > check detected by a DFT. The user was then referred to documentation on > that particular terminal. We still see such status codes appear on > emulated terminals. We just press RESET, CLEAR or anything that will > clear the status and go on. There was a z/OS telnet server bug a while back for TN3270E sessions wherein the host would send a garbage response to a CLEAR operation. This caused a PROG 754. NOTN3270E bypassed that problem. Graeme: If you are telnetted into the first level system, try it with NOTN3270E in the InternalClientParms of PROFILE TCPIP. If the problem goes away, there's your workaround. If anyone has the same problem on a supported release, please call it in. Alan Altmark z/VM Development IBM Endicott Jim Bohnsack Cornell Univ. (607) 255-1760
Re: Prog 754 on Graphic device 2nd level zVM 5.2
On Wednesday, 09/06/2006 at 10:05 EST, Bob Forward <[EMAIL PROTECTED]> wrote: > On some older 3270 devices, any PROG7xx status was due to a program > check detected by a DFT. The user was then referred to documentation on > that particular terminal. We still see such status codes appear on > emulated terminals. We just press RESET, CLEAR or anything that will > clear the status and go on. There was a z/OS telnet server bug a while back for TN3270E sessions wherein the host would send a garbage response to a CLEAR operation. This caused a PROG 754. NOTN3270E bypassed that problem. Graeme: If you are telnetted into the first level system, try it with NOTN3270E in the InternalClientParms of PROFILE TCPIP. If the problem goes away, there's your workaround. If anyone has the same problem on a supported release, please call it in. Alan Altmark z/VM Development IBM Endicott
Re: Prog 754 on Graphic device 2nd level zVM 5.2
On some older 3270 devices, any PROG7xx status was due to a program check detected by a DFT. The user was then referred to documentation on that particular terminal. We still see such status codes appear on emulated terminals. We just press RESET, CLEAR or anything that will clear the status and go on. Graeme Moss wrote: Earlier this year people were having problems with DIAL sessions from 3.1 to 5.2 systems. Some people said they opened issues with IBM. I have done a search on Servicelink using arg 754 but couldn't find any entries. Can any-one describe resolutions to this problem ? Thanks Graeme
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Hello Graeme, I had this problem and opened an issue with IBM. It only happened if I was using TN3270 on a 3.1 system and then dialing to my 2nd level 5.2 system. It didn't occur for SNA or if I established a TN3270 session to the 5.2 system (via a vctca connection from 3.1 TCP/IP to 5.2 TCP/IP). As I recall, since 3.1 was no longer supported by IBM I could not send any traces from the 3.1 side. I left the issue as is. Regards Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Graeme Moss Sent: September 5, 2006 7:12 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Prog 754 on Graphic device 2nd level zVM 5.2 Earlier this year people were having problems with DIAL sessions from 3.1 to 5.2 systems. Some people said they opened issues with IBM. I have done a search on Servicelink using arg 754 but couldn't find any entries. Can any-one describe resolutions to this problem ? Thanks Graeme
Prog 754 on Graphic device 2nd level zVM 5.2
Earlier this year people were having problems with DIAL sessions from 3.1 to 5.2 systems. Some people said they opened issues with IBM. I have done a search on Servicelink using arg 754 but couldn't find any entries. Can any-one describe resolutions to this problem ? Thanks Graeme
Re: Prog 754 on Graphic device 2nd level zVM 5.2
I had the same problem! The second level Z/VM guest kept getting the 754 prog. I was moving from 3.1 to 5.2. The IBM sub contractor said it must be that. He had not seen that in any other upgrade he had done. When he & i installed Z/VM 5.2 as the first level, the problem went a way.
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Hello Alan, Thanks for the info. Started the PCOM trace and got something. My problem is using Model 4 emulation. Going to start the trace also on my 2nd level zVM 3.1 system and compare the trace log files. Will look at how to do host trace from 1st level TCP/IP stack. Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: May 3, 2006 2:04 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 On Wednesday, 05/03/2006 at 01:45 AST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > I have opened an issue. I don't see any hits with Service Link. What I > have done so far with a PC emulated NON 3278 Model 2 device is: > > 1) IPLed the CMS 190 minidisk from 2nd level at 1st level and everything > works fine. > 2) Accessed the 1st level system through an SNA network and then did a > DIAL to my 2nd level. This worked fine. > > For some strange reason only if I go through my TCP/IP stack first level > and then do the DIAL into 2nd level that I have this problem. I have no > problem dialing into a 2nd level zVM 3.1 system. > > I remember once doing, I think, a CP TRACE command to trace the I/O's to > a device. Not sure on usage and how I could decipher the 3270 datastream > but will investigate. Easiest is to activate the PCOMM trace facility. It will format the 3270 data stream for you and show you what PCOMM received. You can compare that to a sniffer trace (or host trace) of what VM is sending. (The PCOMM trace facility is in the Administrative and PD Aids folder in the IBM Personal Communications folder.) PROG 754 means "required parameters not provided" and from that I infer that the 3270 data stream was truncated somewhere along the way. (The fact that it works for mod 4 and not mod 2 is disturbing, however.) Comparing what PCOMM received and what VM sent will let you and the Support Center begin to narrow the problem. It will also reveal exactly which of the dozen conditions for a PROG 754 occurred. Alan Altmark z/VM Development IBM Endicott
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Yes, I reported this problem over a month ago. It also doesn't happen in a way I can reproduce but it does happen. I don't think there is a fix for it today but I am sure they are working on it. Aria. On Wed, 3 May 2006 13:45:21 -0400 Horlick, Michael said: >Aria, > >I have opened an issue. I don't see any hits with Service Link. What I >have done so far with a PC emulated NON 3278 Model 2 device is: =20 > >1) IPLed the CMS 190 minidisk from 2nd level at 1st level and everything >works fine. >2) Accessed the 1st level system through an SNA network and then did a >DIAL to my 2nd level. This worked fine. > >For some strange reason only if I go through my TCP/IP stack first level >and then do the DIAL into 2nd level that I have this problem. I have no >problem dialing into a 2nd level zVM 3.1 system.=20 > >I remember once doing, I think, a CP TRACE command to trace the I/O's to >a device. Not sure on usage and how I could decipher the 3270 datastream >but will investigate. > >Thanks > >Mike=20 >=20 > >-Original Message- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Aria Bamdad >Sent: May 3, 2006 1:08 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 > >Mike, > >I this is a known problem for 5.2. Please call the support center. > >Aria. >On Tue, 2 May 2006 14:03:06 -0400 Horlick, Michael said: >>I just tried with PCOMM as well and am getting the same symptoms.=3D20 >> >>Using Extra I am creating a TN3270 session connecting to Port 2300 (I >>use Port 23 for CA-TPX) through my first level VM TCP/IP stack. I have >>no problems with first level. I have extended attributes, any model >>(Model 2,3,4,5) configuration. Never a problem. >> >>After getting our first level logo I clear the screen and DIAL into my >>zVM 5.2 system. Everything looks ok until I XEDIT a file. If I'm >defined >>as a model 4 I can browse any file no problem, I can FLIST ok, it just >>seems to be XEDIT.=3D20 >> >>Maybe it's time to open a call to IBM support center. >> >>Mike >> >>-Original Message- >>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >>Behalf Of Eric Schadow >>Sent: May 2, 2006 1:27 PM >>To: IBMVM@LISTSERV.UARK.EDU >>Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 >> >>I dialed to z/VM 5.2 second level from z/vm 5.1 and xedit worked ok for >>me on Extra 6.5 SP2. >> >>How are you attaching to the first level system? >> >> >> >>At 01:18 PM 5/2/2006, you wrote: >>>Hello Eric, >>> >>>Thanks for your response. What's interesting is that it works fine for >>>zVM 3.1 but not for zVM 5.2. What could be different to account for >>>this? I went to the Attachmate site and could not find any hits for >>this >>>type of error.=3D3D20 >>> >>>Mike =3D3D20 >>> >>> >>>-Original Message- >>>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] >On >>>Behalf Of Eric Schadow >>>Sent: May 2, 2006 1:04 PM >>>To: IBMVM@LISTSERV.UARK.EDU >>>Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 >>> >>>Mike >>> >>>Extra has the same issues with VSE consoles. >>> >>>If you have a current support contract withe Attachmate I would >report >>>the issue to them. >>> >>> >>>eric >>> >>> >>> >>> >>>Eric Schadow >>>Mainframe Technical Support >>>www.davisvision.com=3D3D20 >>> >>> >>> >>>-- >- >>- >>>The information contained in this communication is intended >>>only for the use of the recipient(s) named above. It may >>>contain information that is privileged or confidential, and >>>may be protected by State and/or Federal Regulations. If >>>the reader of this message is not the intended recipient, >>>you are hereby notified that any dissemination, >>>distribution, or copying of this communication, or any of >>>its contents, is strictly prohibited. If you have received >>>this communication in error, please return it to the sender >>>immediately and delete the original message and any copy >>>of it from your computer system. If you have any questions >>>concerning this message, please contact the sender. >>>
Re: Prog 754 on Graphic device 2nd level zVM 5.2
On Wednesday, 05/03/2006 at 01:08 AST, Aria Bamdad <[EMAIL PROTECTED]> wrote: > I this is a known problem for 5.2. Please call the support center. Now THAT is way cool! A problem that doesn't require debug! Yippee!! :-) Alan Altmark z/VM Development IBM Endicott
Re: Prog 754 on Graphic device 2nd level zVM 5.2
On Wednesday, 05/03/2006 at 01:45 AST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > I have opened an issue. I don't see any hits with Service Link. What I > have done so far with a PC emulated NON 3278 Model 2 device is: > > 1) IPLed the CMS 190 minidisk from 2nd level at 1st level and everything > works fine. > 2) Accessed the 1st level system through an SNA network and then did a > DIAL to my 2nd level. This worked fine. > > For some strange reason only if I go through my TCP/IP stack first level > and then do the DIAL into 2nd level that I have this problem. I have no > problem dialing into a 2nd level zVM 3.1 system. > > I remember once doing, I think, a CP TRACE command to trace the I/O's to > a device. Not sure on usage and how I could decipher the 3270 datastream > but will investigate. Easiest is to activate the PCOMM trace facility. It will format the 3270 data stream for you and show you what PCOMM received. You can compare that to a sniffer trace (or host trace) of what VM is sending. (The PCOMM trace facility is in the Administrative and PD Aids folder in the IBM Personal Communications folder.) PROG 754 means "required parameters not provided" and from that I infer that the 3270 data stream was truncated somewhere along the way. (The fact that it works for mod 4 and not mod 2 is disturbing, however.) Comparing what PCOMM received and what VM sent will let you and the Support Center begin to narrow the problem. It will also reveal exactly which of the dozen conditions for a PROG 754 occurred. Alan Altmark z/VM Development IBM Endicott
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Aria, I have opened an issue. I don't see any hits with Service Link. What I have done so far with a PC emulated NON 3278 Model 2 device is: 1) IPLed the CMS 190 minidisk from 2nd level at 1st level and everything works fine. 2) Accessed the 1st level system through an SNA network and then did a DIAL to my 2nd level. This worked fine. For some strange reason only if I go through my TCP/IP stack first level and then do the DIAL into 2nd level that I have this problem. I have no problem dialing into a 2nd level zVM 3.1 system. I remember once doing, I think, a CP TRACE command to trace the I/O's to a device. Not sure on usage and how I could decipher the 3270 datastream but will investigate. Thanks Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Aria Bamdad Sent: May 3, 2006 1:08 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 Mike, I this is a known problem for 5.2. Please call the support center. Aria. On Tue, 2 May 2006 14:03:06 -0400 Horlick, Michael said: >I just tried with PCOMM as well and am getting the same symptoms.=20 > >Using Extra I am creating a TN3270 session connecting to Port 2300 (I >use Port 23 for CA-TPX) through my first level VM TCP/IP stack. I have >no problems with first level. I have extended attributes, any model >(Model 2,3,4,5) configuration. Never a problem. > >After getting our first level logo I clear the screen and DIAL into my >zVM 5.2 system. Everything looks ok until I XEDIT a file. If I'm defined >as a model 4 I can browse any file no problem, I can FLIST ok, it just >seems to be XEDIT.=20 > >Maybe it's time to open a call to IBM support center. > >Mike > >-Original Message- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Eric Schadow >Sent: May 2, 2006 1:27 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 > >I dialed to z/VM 5.2 second level from z/vm 5.1 and xedit worked ok for >me on Extra 6.5 SP2. > >How are you attaching to the first level system? > > > >At 01:18 PM 5/2/2006, you wrote: >>Hello Eric, >> >>Thanks for your response. What's interesting is that it works fine for >>zVM 3.1 but not for zVM 5.2. What could be different to account for >>this? I went to the Attachmate site and could not find any hits for >this >>type of error.=3D20 >> >>Mike =3D20 >> >> >>-Original Message----- >>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >>Behalf Of Eric Schadow >>Sent: May 2, 2006 1:04 PM >>To: IBMVM@LISTSERV.UARK.EDU >>Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 >> >>Mike >> >>Extra has the same issues with VSE consoles. >> >>If you have a current support contract withe Attachmate I would report >>the issue to them. >> >> >>eric >> >> >> >> >>Eric Schadow >>Mainframe Technical Support >>www.davisvision.com=3D20 >> >> >> >>-- - >- >>The information contained in this communication is intended >>only for the use of the recipient(s) named above. It may >>contain information that is privileged or confidential, and >>may be protected by State and/or Federal Regulations. If >>the reader of this message is not the intended recipient, >>you are hereby notified that any dissemination, >>distribution, or copying of this communication, or any of >>its contents, is strictly prohibited. If you have received >>this communication in error, please return it to the sender >>immediately and delete the original message and any copy >>of it from your computer system. If you have any questions >>concerning this message, please contact the sender. >>-- - >- > >Eric Schadow >Mainframe Technical Support >www.davisvision.com=20 > > > >--- - >The information contained in this communication is intended >only for the use of the recipient(s) named above. It may >contain information that is privileged or confidential, and >may be protected by State and/or Federal Regulations. If >the reader of this message is not the intended recipient, >you are hereby notified that any dissemination, >distribution, or copying of this communication, or any of >its contents, is strictly prohibited. If you have received >this communication in error, please return it to the sender >immediately and delete the original message and any copy >of it from your computer system. If you have any questions >concerning this message, please contact the sender. >--- -
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Mike, I this is a known problem for 5.2. Please call the support center. Aria. On Tue, 2 May 2006 14:03:06 -0400 Horlick, Michael said: >I just tried with PCOMM as well and am getting the same symptoms.=20 > >Using Extra I am creating a TN3270 session connecting to Port 2300 (I >use Port 23 for CA-TPX) through my first level VM TCP/IP stack. I have >no problems with first level. I have extended attributes, any model >(Model 2,3,4,5) configuration. Never a problem. > >After getting our first level logo I clear the screen and DIAL into my >zVM 5.2 system. Everything looks ok until I XEDIT a file. If I'm defined >as a model 4 I can browse any file no problem, I can FLIST ok, it just >seems to be XEDIT.=20 > >Maybe it's time to open a call to IBM support center. > >Mike > >-Original Message- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Eric Schadow >Sent: May 2, 2006 1:27 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 > >I dialed to z/VM 5.2 second level from z/vm 5.1 and xedit worked ok for >me on Extra 6.5 SP2. > >How are you attaching to the first level system? > > > >At 01:18 PM 5/2/2006, you wrote: >>Hello Eric, >> >>Thanks for your response. What's interesting is that it works fine for >>zVM 3.1 but not for zVM 5.2. What could be different to account for >>this? I went to the Attachmate site and could not find any hits for >this >>type of error.=3D20 >> >>Mike =3D20 >> >> >>-Original Message----- >>From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >>Behalf Of Eric Schadow >>Sent: May 2, 2006 1:04 PM >>To: IBMVM@LISTSERV.UARK.EDU >>Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 >> >>Mike >> >>Extra has the same issues with VSE consoles. >> >>If you have a current support contract withe Attachmate I would report >>the issue to them. >> >> >>eric >> >> >> >> >>Eric Schadow >>Mainframe Technical Support >>www.davisvision.com=3D20 >> >> >> >>--- >- >>The information contained in this communication is intended >>only for the use of the recipient(s) named above. It may >>contain information that is privileged or confidential, and >>may be protected by State and/or Federal Regulations. If >>the reader of this message is not the intended recipient, >>you are hereby notified that any dissemination, >>distribution, or copying of this communication, or any of >>its contents, is strictly prohibited. If you have received >>this communication in error, please return it to the sender >>immediately and delete the original message and any copy >>of it from your computer system. If you have any questions >>concerning this message, please contact the sender. >>--- >- > >Eric Schadow >Mainframe Technical Support >www.davisvision.com=20 > > > > >The information contained in this communication is intended >only for the use of the recipient(s) named above. It may >contain information that is privileged or confidential, and >may be protected by State and/or Federal Regulations. If >the reader of this message is not the intended recipient, >you are hereby notified that any dissemination, >distribution, or copying of this communication, or any of >its contents, is strictly prohibited. If you have received >this communication in error, please return it to the sender >immediately and delete the original message and any copy >of it from your computer system. If you have any questions >concerning this message, please contact the sender. >
Re: Prog 754 on Graphic device 2nd level zVM 5.2
I just tried with PCOMM as well and am getting the same symptoms. Using Extra I am creating a TN3270 session connecting to Port 2300 (I use Port 23 for CA-TPX) through my first level VM TCP/IP stack. I have no problems with first level. I have extended attributes, any model (Model 2,3,4,5) configuration. Never a problem. After getting our first level logo I clear the screen and DIAL into my zVM 5.2 system. Everything looks ok until I XEDIT a file. If I'm defined as a model 4 I can browse any file no problem, I can FLIST ok, it just seems to be XEDIT. Maybe it's time to open a call to IBM support center. Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Eric Schadow Sent: May 2, 2006 1:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 I dialed to z/VM 5.2 second level from z/vm 5.1 and xedit worked ok for me on Extra 6.5 SP2. How are you attaching to the first level system? At 01:18 PM 5/2/2006, you wrote: >Hello Eric, > >Thanks for your response. What's interesting is that it works fine for >zVM 3.1 but not for zVM 5.2. What could be different to account for >this? I went to the Attachmate site and could not find any hits for this >type of error.=20 > >Mike =20 > > >-Original Message- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Eric Schadow >Sent: May 2, 2006 1:04 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 > >Mike > >Extra has the same issues with VSE consoles. > >If you have a current support contract withe Attachmate I would report >the issue to them. > > >eric > > > > >Eric Schadow >Mainframe Technical Support >www.davisvision.com=20 > > > >--- - >The information contained in this communication is intended >only for the use of the recipient(s) named above. It may >contain information that is privileged or confidential, and >may be protected by State and/or Federal Regulations. If >the reader of this message is not the intended recipient, >you are hereby notified that any dissemination, >distribution, or copying of this communication, or any of >its contents, is strictly prohibited. If you have received >this communication in error, please return it to the sender >immediately and delete the original message and any copy >of it from your computer system. If you have any questions >concerning this message, please contact the sender. >--- - Eric Schadow Mainframe Technical Support www.davisvision.com The information contained in this communication is intended only for the use of the recipient(s) named above. It may contain information that is privileged or confidential, and may be protected by State and/or Federal Regulations. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
Re: Prog 754 on Graphic device 2nd level zVM 5.2
I dialed to z/VM 5.2 second level from z/vm 5.1 and xedit worked ok for me on Extra 6.5 SP2. How are you attaching to the first level system? At 01:18 PM 5/2/2006, you wrote: >Hello Eric, > >Thanks for your response. What's interesting is that it works fine for >zVM 3.1 but not for zVM 5.2. What could be different to account for >this? I went to the Attachmate site and could not find any hits for this >type of error.=20 > >Mike =20 > > >-Original Message- >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Eric Schadow >Sent: May 2, 2006 1:04 PM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 > >Mike > >Extra has the same issues with VSE consoles. > >If you have a current support contract withe Attachmate I would report >the issue to them. > > >eric > > > > >Eric Schadow >Mainframe Technical Support >www.davisvision.com=20 > > > > >The information contained in this communication is intended >only for the use of the recipient(s) named above. It may >contain information that is privileged or confidential, and >may be protected by State and/or Federal Regulations. If >the reader of this message is not the intended recipient, >you are hereby notified that any dissemination, >distribution, or copying of this communication, or any of >its contents, is strictly prohibited. If you have received >this communication in error, please return it to the sender >immediately and delete the original message and any copy >of it from your computer system. If you have any questions >concerning this message, please contact the sender. > Eric Schadow Mainframe Technical Support www.davisvision.com The information contained in this communication is intended only for the use of the recipient(s) named above. It may contain information that is privileged or confidential, and may be protected by State and/or Federal Regulations. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Hello Eric, Thanks for your response. What's interesting is that it works fine for zVM 3.1 but not for zVM 5.2. What could be different to account for this? I went to the Attachmate site and could not find any hits for this type of error. Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Eric Schadow Sent: May 2, 2006 1:04 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Prog 754 on Graphic device 2nd level zVM 5.2 Mike Extra has the same issues with VSE consoles. If you have a current support contract withe Attachmate I would report the issue to them. eric Eric Schadow Mainframe Technical Support www.davisvision.com The information contained in this communication is intended only for the use of the recipient(s) named above. It may contain information that is privileged or confidential, and may be protected by State and/or Federal Regulations. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
Re: Prog 754 on Graphic device 2nd level zVM 5.2
Mike Extra has the same issues with VSE consoles. If you have a current support contract withe Attachmate I would report the issue to them. eric Eric Schadow Mainframe Technical Support www.davisvision.com The information contained in this communication is intended only for the use of the recipient(s) named above. It may contain information that is privileged or confidential, and may be protected by State and/or Federal Regulations. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
Prog 754 on Graphic device 2nd level zVM 5.2
Greetings, We have 2 zVM systems running 2nd level under zVM 3.1 on our machine. One is running zVM 3.1 , the other, a new one, zVM 5.2. We use myExtra Enterprise 7.11 to create a TN3270 session from our PC. After creating a VM first level 3270 session we DIAL into each of our 2nd level systems. No problems whatsoever with zVM 3.1 but am getting Prog 754 when using XEDIT in zVM 5.2 system. I have the terminal defined in Extra as, say a Model 4 with extended attributes, and after dialing into zVM 5.2 it shows the logo properly as a Model 4. After logging in and do an XEDIT a file we get Prog 754. In both zVM systems SYSTEM CONFIG we have the following: Rdevice 0009-001F Type 3270 For both 2nd levels system on 1st level , the displays are defined as, for example : SPECIAL 0010 3270 Tried issuing several command ‘SET RDEVICE’ commands to change characteristics of device but no luck. Any ideas? Thanks Mike
