Re: TRANS13 , IND$FILE and CA-TPX
Hello Mike, Please go back to your original failing setup, but see if there is setting within the emulator to control the packet size of the transfer. Adjust the packet to 576 (allowed by all TCP/Ip systems). Let me know what happens Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Horlick, Michael Sent: Friday, December 12, 2008 2:05 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX D4A3290, no go, gives me: 13:54:44 VTAM: IST663I BIND FAIL REQUEST RECEIVED, SENSE=0821 13:54:44 VTAM: IST664I REAL OLU=SYSCOR.TC4D0REAL DLU=SYSCOR.VMD 13:54:44 VTAM: IST889I SID = CC4F9B4CA20797EF 13:54:44 VTAM: IST890I AUTOLOGON SESSION SETUP FAILED 13:54:44 VTAM: IST314I END 13:54:44 VTAM: DTIV03I DTIVOPNX LOGON FOR SYSCOR.TC4D0 FAILED - OPNDST RETURN CODE = 1001 SENSE = 0821 USER SENSE = And COMMAND = D NET,ID=TC4D0,E VMYINI006I 0.000 Ready; 13:56:07 VTAM: Ready; 13:56:07 VTAM: IST097I DISPLAY ACCEPTED 13:56:07 VTAM: IST075I NAME = SYSCOR.TC4D0, TYPE = LOGICAL UNIT 13:56:07 VTAM: IST486I STATUS= ACTIV, DESIRED STATE= ACTIV 13:56:07 VTAM: IST977I MDLTAB=***NA*** ASLTAB=***NA*** 13:56:07 VTAM: IST861I MODETAB=ISTINCLM USSTAB=USSTCPIP LOGTAB=***NA*** 13:56:07 VTAM: IST934I DLOGMOD=D4A3290 USS LANGTAB=***NA*** Ok, need to do a little research on VTAM tracing/Wireshark. You wouldn't have a quick primer on how to do the trace, would you? Thanks, Mike -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: December 12, 2008 12:42 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX On Friday, 12/12/2008 at 10:13 EST, "Horlick, Michael" wrote: > Actually , it has nothing to do with TPX. > > For one virtual terminal (4D0) I changed the Logappl to VM: Try D4A3290 (it is an SNA logmode, D4B is non-SNA). > It still doesn't work for the client. I am thinking maybe a VTAM trace > could shed light on why it works for my emulator but not theirs. I would > not know how to read the trace and since IND$FILE is unsupported would > IBM accept my call on this issue and offer assistance? > > Is there anything else I could do on the mainframe side to diagnose the > error? It was explicitly stated in the relevant z/VM announcement letters that you won't be able to get any support from IBM for IND$FILE. A look at RETAIN shows me that 5664-281 (3270-PC FILE TRANSFER v1.1.1) ended support 31 JAN 2003. (That's odd since I can't find the withdrawal from marketing or service announcement.) So let's recap: You have a failing case and a working case. Get a data trace so you can look for differences. You don't really have to know what it all means, but knowing whether there are any difference and whether they are coming from the host or emulator will let us focus more on the problem. If the emulator has a trace capability (PCOMM does), or if you have Wireshark, that's probably best. Otherwise you'll need a VTAM LU data trace. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
D4A3290, no go, gives me: 13:54:44 VTAM: IST663I BIND FAIL REQUEST RECEIVED, SENSE=0821 13:54:44 VTAM: IST664I REAL OLU=SYSCOR.TC4D0REAL DLU=SYSCOR.VMD 13:54:44 VTAM: IST889I SID = CC4F9B4CA20797EF 13:54:44 VTAM: IST890I AUTOLOGON SESSION SETUP FAILED 13:54:44 VTAM: IST314I END 13:54:44 VTAM: DTIV03I DTIVOPNX LOGON FOR SYSCOR.TC4D0 FAILED - OPNDST RETURN CODE = 1001 SENSE = 0821 USER SENSE = And COMMAND = D NET,ID=TC4D0,E VMYINI006I 0.000 Ready; 13:56:07 VTAM: Ready; 13:56:07 VTAM: IST097I DISPLAY ACCEPTED 13:56:07 VTAM: IST075I NAME = SYSCOR.TC4D0, TYPE = LOGICAL UNIT 13:56:07 VTAM: IST486I STATUS= ACTIV, DESIRED STATE= ACTIV 13:56:07 VTAM: IST977I MDLTAB=***NA*** ASLTAB=***NA*** 13:56:07 VTAM: IST861I MODETAB=ISTINCLM USSTAB=USSTCPIP LOGTAB=***NA*** 13:56:07 VTAM: IST934I DLOGMOD=D4A3290 USS LANGTAB=***NA*** Ok, need to do a little research on VTAM tracing/Wireshark. You wouldn't have a quick primer on how to do the trace, would you? Thanks, Mike -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: December 12, 2008 12:42 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX On Friday, 12/12/2008 at 10:13 EST, "Horlick, Michael" wrote: > Actually , it has nothing to do with TPX. > > For one virtual terminal (4D0) I changed the Logappl to VM: Try D4A3290 (it is an SNA logmode, D4B is non-SNA). > It still doesn't work for the client. I am thinking maybe a VTAM trace > could shed light on why it works for my emulator but not theirs. I would > not know how to read the trace and since IND$FILE is unsupported would > IBM accept my call on this issue and offer assistance? > > Is there anything else I could do on the mainframe side to diagnose the > error? It was explicitly stated in the relevant z/VM announcement letters that you won't be able to get any support from IBM for IND$FILE. A look at RETAIN shows me that 5664-281 (3270-PC FILE TRANSFER v1.1.1) ended support 31 JAN 2003. (That's odd since I can't find the withdrawal from marketing or service announcement.) So let's recap: You have a failing case and a working case. Get a data trace so you can look for differences. You don't really have to know what it all means, but knowing whether there are any difference and whether they are coming from the host or emulator will let us focus more on the problem. If the emulator has a trace capability (PCOMM does), or if you have Wireshark, that's probably best. Otherwise you'll need a VTAM LU data trace. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
On Friday, 12/12/2008 at 10:13 EST, "Horlick, Michael" wrote: > Actually , it has nothing to do with TPX. > > For one virtual terminal (4D0) I changed the Logappl to VM: Try D4A3290 (it is an SNA logmode, D4B is non-SNA). > It still doesn't work for the client. I am thinking maybe a VTAM trace > could shed light on why it works for my emulator but not theirs. I would > not know how to read the trace and since IND$FILE is unsupported would > IBM accept my call on this issue and offer assistance? > > Is there anything else I could do on the mainframe side to diagnose the > error? It was explicitly stated in the relevant z/VM announcement letters that you won't be able to get any support from IBM for IND$FILE. A look at RETAIN shows me that 5664-281 (3270-PC FILE TRANSFER v1.1.1) ended support 31 JAN 2003. (That's odd since I can't find the withdrawal from marketing or service announcement.) So let's recap: You have a failing case and a working case. Get a data trace so you can look for differences. You don't really have to know what it all means, but knowing whether there are any difference and whether they are coming from the host or emulator will let us focus more on the problem. If the emulator has a trace capability (PCOMM does), or if you have Wireshark, that's probably best. Otherwise you'll need a VTAM LU data trace. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
Actually , it has nothing to do with TPX. For one virtual terminal (4D0) I changed the Logappl to VM: IST097I DISPLAY ACCEPTED IST075I NAME = SYSCOR.TC4D0, TYPE = LOGICAL UNIT IST486I STATUS= ACT/S, DESIRED STATE= ACTIV IST977I MDLTAB=***NA*** ASLTAB=***NA*** IST861I MODETAB=ISTINCLM USSTAB=USSTCPIP LOGTAB=***NA*** IST934I DLOGMOD=D4B3290 USS LANGTAB=***NA*** IST597I CAPABILITY-PLU INHIBITED,SLU ENABLED ,SESSION LIMIT 0001 IST351I LOCAL 3270 MAJOR NODE = DEVTERMS IST077I SIO = 00333 CUA = 04D0 IST082I DEVTYPE = LU , CONTROLLING LU = VMD IST654I I/O TRACE = OFF, BUFFER TRACE = OFF IST171I ACTIVE SESSIONS = 01, SESSION REQUESTS = 00 IST206I SESSIONS: IST634I NAME STATUS SID SEND RECV VR TP NETID IST635I VMD ACTIV/C-P CC4F9B4CA20789BF 0001 0002 SYSCOR IST314I END It still doesn't work for the client. I am thinking maybe a VTAM trace could shed light on why it works for my emulator but not theirs. I would not know how to read the trace and since IND$FILE is unsupported would IBM accept my call on this issue and offer assistance? Is there anything else I could do on the mainframe side to diagnose the error? Also... At http://gsf-soft.com/Documents/IND$FILE.shtml it mentions the following: "Setting of the Query bit in the VTAM LOGMODE (PSERVIC) and/or the 3270 emulator options may affect the ability of the emulator to use WSF (Write Structured Field) commands and impact the availability or speed of file transfer." I also tried NSX32705 and it also fails for the client. Strange, pure SNA with DLOGMOD SNX32705 works, TCP/IP and DIAL with DLOGMOD D4B3290/NSX32705 does not. Regards, Mike -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: December 12, 2008 9:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX On Friday, 12/12/2008 at 09:04 EST, "Horlick, Michael" wrote: >> D4B3290 > Yup, that's what I am using. That's the best logmode there is. But it assumes that the VTAM app (CA-TPX) is actually going to obey it. I don't think you're going to resolve this until the question "What is different about the 3270 data stream that the guest sees?" can be answered. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
On Friday, 12/12/2008 at 09:04 EST, "Horlick, Michael" wrote: >> D4B3290 > Yup, that's what I am using. That's the best logmode there is. But it assumes that the VTAM app (CA-TPX) is actually going to obey it. I don't think you're going to resolve this until the question "What is different about the 3270 data stream that the guest sees?" can be answered. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
Yup, that's what I am using. Regards, Mike -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: December 11, 2008 5:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX On Thursday, 12/11/2008 at 02:31 EST, "Horlick, Michael" wrote: > The client is supposed to be getting a new version of their software and > I have been looking at all the DLOGMOD's that I can use for a "dialled" > terminal. So far, nothing in the IBM ISTINCLM modetab works for them (it > works fine for my emulator). D4B3290 is for DIALed terminals (non-SNA, extended attributes, query for capabilities and screen size). Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
On Thursday, 12/11/2008 at 02:31 EST, "Horlick, Michael" wrote: > The client is supposed to be getting a new version of their software and > I have been looking at all the DLOGMOD's that I can use for a "dialled" > terminal. So far, nothing in the IBM ISTINCLM modetab works for them (it > works fine for my emulator). D4B3290 is for DIALed terminals (non-SNA, extended attributes, query for capabilities and screen size). Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
Greetings all, A little update. I went to the client yesterday and discovered that it wasn't TPX causing the problem. When I changed the logappl from TPX to VM for a virtual terminal and did a DIAL VTAM I was presented a VM logo and after logging on the file transfer failed as well (either with a TRANS13 for a large file or no created CMS file for a smaller one). The client is supposed to be getting a new version of their software and I have been looking at all the DLOGMOD's that I can use for a "dialled" terminal. So far, nothing in the IBM ISTINCLM modetab works for them (it works fine for my emulator). Regards, Mike -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Alan Altmark Sent: December 9, 2008 1:56 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX On Monday, 12/08/2008 at 02:11 EST, "Horlick, Michael" wrote: > For my emulator (myExtra!) it works fine but fails for their emulator. However, > under SNA it works. And so I state again for the record: You must gather diagnostic data from CA-TPX to see the difference in the data streams flowing to/from TCP/IP and from/to the emulator. Find where the flow is different as compared to using VM/VTAM. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
On Monday, 12/08/2008 at 02:11 EST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > For my emulator (myExtra!) it works fine but fails for their emulator. However, > under SNA it works. And so I state again for the record: You must gather diagnostic data from CA-TPX to see the difference in the data streams flowing to/from TCP/IP and from/to the emulator. Find where the flow is different as compared to using VM/VTAM. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
Hello Steven, For my emulator (myExtra!) it works fine but fails for their emulator. However, under SNA it works. Regards, Mike From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Imler, Steven J Sent: December 5, 2008 4:44 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Mike, I just hopped on to TPX (I normally don't go through TPX to access z/VM ... only things that run on z/OS under CICS) and tried a file transfer here ... it worked without any problem. My emulator sessions is set to 3279-4E ... TPX says: Terminal - A55T2627 Model- 3192-4A Unfortunately at this time I don't know what VTAM logmode is being used. JR (Steven) Imler CA Senior Sustaining Engineer Tel: +1 703 708 3479 [EMAIL PROTECTED] From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Horlick, Michael Sent: Friday, December 05, 2008 03:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Hello Alan et all, Just a little update. I created a 24 record file with 1234567890 repeated for 80 characters and asked the client to test. This time he says the file transfer doesn't issue messages but also doesn't upload the file to the host. It completes but the CMS file is not there. Again, this only happens with the combination of CA-TPX and TCP/IP for VM. When he tries with CA-TPX and SNA it works. The same settings for the emulator (same size screen, etc...) How could the same 3270 datastream cause this? They have their terminal set up as a model 5 My only thought is that it must be how the device appears to VM/VTAM. For SNA, it is a remote device. When he is on SNA and TPX and I display the user I see: Termid: TX262144 Model: PC92-5AG Logmode: SNX32705 I have no idea where it gets that PC92-5AG model info from. Would you or anyone else know? Then when he creates a virtual terminal session on TPX he gets: SessionApplidStatus VTermid--Status Flags---Appl.Logmode VM2VM<== ACTIVE TPXGR052 400010C1 T3278M2E This application logmode of T3278M2E is a CA-TPX one and when I do a 'CP Q' on his CMS user I see him on TPXGR052. For TCP/IP for VM, there is a DIAL VTAM and I set the DLOGMOD to D4B3290. I think I have tried different DLOGMOD's (NSX32705) and even asked them to configure as a Model 2 but still no go. The SNA DLOG of SNX32705 looks like this: SNX32705 MODEENT LOGMODE=SNX32705,FMPROF=X'03',TSPROF=X'03', PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080', RUSIZES=X'87F8', PSERVIC=X'028018501B847F00' I'm not much of a VTAM maven. Is there anything in that macro related to file transfer? Is there something I can use to replace IND$FILE with? I suggested native VM (whick works) and also ftp (but that's a hassle with write access to their A-disk) but they prefer the way they always work (but just with TCP/IP). Wednesday, I'll be visiting the client and be screwing around with DLOGMOD's etc... Regards, Mike
Re: TRANS13 , IND$FILE and CA-TPX
Hello Ed, CA-TPX is a VM/VTAM application. Regards, Mike From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Edward M Martin Sent: December 5, 2008 4:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Hello Micheal, TCP/IP to z/VM and IND$FILE works with a 40/140 connection using PCOM 5.6. Do you have to dial to VTAM? Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Horlick, Michael Sent: Friday, December 05, 2008 3:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Hello Alan et all, Just a little update. I created a 24 record file with 1234567890 repeated for 80 characters and asked the client to test. This time he says the file transfer doesn't issue messages but also doesn't upload the file to the host. It completes but the CMS file is not there. Again, this only happens with the combination of CA-TPX and TCP/IP for VM. When he tries with CA-TPX and SNA it works. The same settings for the emulator (same size screen, etc...) How could the same 3270 datastream cause this? They have their terminal set up as a model 5 My only thought is that it must be how the device appears to VM/VTAM. For SNA, it is a remote device. When he is on SNA and TPX and I display the user I see: Termid: TX262144 Model: PC92-5AG Logmode: SNX32705 I have no idea where it gets that PC92-5AG model info from. Would you or anyone else know? Then when he creates a virtual terminal session on TPX he gets: SessionApplidStatus VTermid--Status Flags---Appl.Logmode VM2VM<== ACTIVE TPXGR052 400010C1 T3278M2E This application logmode of T3278M2E is a CA-TPX one and when I do a 'CP Q' on his CMS user I see him on TPXGR052. For TCP/IP for VM, there is a DIAL VTAM and I set the DLOGMOD to D4B3290. I think I have tried different DLOGMOD's (NSX32705) and even asked them to configure as a Model 2 but still no go. The SNA DLOG of SNX32705 looks like this: SNX32705 MODEENT LOGMODE=SNX32705,FMPROF=X'03',TSPROF=X'03', PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080', RUSIZES=X'87F8', PSERVIC=X'028018501B847F00' I'm not much of a VTAM maven. Is there anything in that macro related to file transfer? Is there something I can use to replace IND$FILE with? I suggested native VM (whick works) and also ftp (but that's a hassle with write access to their A-disk) but they prefer the way they always work (but just with TCP/IP). Wednesday, I'll be visiting the client and be screwing around with DLOGMOD's etc... Regards, Mike
Re: TRANS13 , IND$FILE and CA-TPX
Mike, I just hopped on to TPX (I normally don't go through TPX to access z/VM ... only things that run on z/OS under CICS) and tried a file transfer here ... it worked without any problem. My emulator sessions is set to 3279-4E ... TPX says: Terminal - A55T2627 Model- 3192-4A Unfortunately at this time I don't know what VTAM logmode is being used. JR (Steven) Imler CA Senior Sustaining Engineer Tel: +1 703 708 3479 [EMAIL PROTECTED] From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Horlick, Michael Sent: Friday, December 05, 2008 03:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Hello Alan et all, Just a little update. I created a 24 record file with 1234567890 repeated for 80 characters and asked the client to test. This time he says the file transfer doesn't issue messages but also doesn't upload the file to the host. It completes but the CMS file is not there. Again, this only happens with the combination of CA-TPX and TCP/IP for VM. When he tries with CA-TPX and SNA it works. The same settings for the emulator (same size screen, etc...) How could the same 3270 datastream cause this? They have their terminal set up as a model 5 My only thought is that it must be how the device appears to VM/VTAM. For SNA, it is a remote device. When he is on SNA and TPX and I display the user I see: Termid: TX262144 Model: PC92-5AG Logmode: SNX32705 I have no idea where it gets that PC92-5AG model info from. Would you or anyone else know? Then when he creates a virtual terminal session on TPX he gets: SessionApplidStatus VTermid--Status Flags---Appl.Logmode VM2VM<== ACTIVE TPXGR052 400010C1 T3278M2E This application logmode of T3278M2E is a CA-TPX one and when I do a 'CP Q' on his CMS user I see him on TPXGR052. For TCP/IP for VM, there is a DIAL VTAM and I set the DLOGMOD to D4B3290. I think I have tried different DLOGMOD's (NSX32705) and even asked them to configure as a Model 2 but still no go. The SNA DLOG of SNX32705 looks like this: SNX32705 MODEENT LOGMODE=SNX32705,FMPROF=X'03',TSPROF=X'03', PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080', RUSIZES=X'87F8', PSERVIC=X'028018501B847F00' I'm not much of a VTAM maven. Is there anything in that macro related to file transfer? Is there something I can use to replace IND$FILE with? I suggested native VM (whick works) and also ftp (but that's a hassle with write access to their A-disk) but they prefer the way they always work (but just with TCP/IP). Wednesday, I'll be visiting the client and be screwing around with DLOGMOD's etc... Regards, Mike
Re: TRANS13 , IND$FILE and CA-TPX
Hello Micheal, TCP/IP to z/VM and IND$FILE works with a 40/140 connection using PCOM 5.6. Do you have to dial to VTAM? Ed Martin Aultman Health Foundation 330-588-4723 ext 40441 From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Horlick, Michael Sent: Friday, December 05, 2008 3:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Hello Alan et all, Just a little update. I created a 24 record file with 1234567890 repeated for 80 characters and asked the client to test. This time he says the file transfer doesn't issue messages but also doesn't upload the file to the host. It completes but the CMS file is not there. Again, this only happens with the combination of CA-TPX and TCP/IP for VM. When he tries with CA-TPX and SNA it works. The same settings for the emulator (same size screen, etc...) How could the same 3270 datastream cause this? They have their terminal set up as a model 5 My only thought is that it must be how the device appears to VM/VTAM. For SNA, it is a remote device. When he is on SNA and TPX and I display the user I see: Termid: TX262144 Model: PC92-5AG Logmode: SNX32705 I have no idea where it gets that PC92-5AG model info from. Would you or anyone else know? Then when he creates a virtual terminal session on TPX he gets: SessionApplidStatus VTermid--Status Flags---Appl.Logmode VM2VM<== ACTIVE TPXGR052 400010C1 T3278M2E This application logmode of T3278M2E is a CA-TPX one and when I do a 'CP Q' on his CMS user I see him on TPXGR052. For TCP/IP for VM, there is a DIAL VTAM and I set the DLOGMOD to D4B3290. I think I have tried different DLOGMOD's (NSX32705) and even asked them to configure as a Model 2 but still no go. The SNA DLOG of SNX32705 looks like this: SNX32705 MODEENT LOGMODE=SNX32705,FMPROF=X'03',TSPROF=X'03', PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080', RUSIZES=X'87F8', PSERVIC=X'028018501B847F00' I'm not much of a VTAM maven. Is there anything in that macro related to file transfer? Is there something I can use to replace IND$FILE with? I suggested native VM (whick works) and also ftp (but that's a hassle with write access to their A-disk) but they prefer the way they always work (but just with TCP/IP). Wednesday, I'll be visiting the client and be screwing around with DLOGMOD's etc... Regards, Mike
Re: TRANS13 , IND$FILE and CA-TPX
On Friday, 12/05/2008 at 03:20 EST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > I think I have tried different DLOGMOD's (NSX32705) and even asked them to > configure as a Model 2 but still no go. I would use D4A3290 to talk to an emulator in an SNA network, but that's just me. The days of needing logmodes that explicitly described the model were interesting when there were devices at the other end that would obey them. They don't. Further, the explicit logmode prevents the host from issuing a QUERY. What this means in the context of CA-TPX, I don't know. With VM/VTAM in place, CA-TPX app will simply create an LU2 session to VSCS on VM. It doesn't manipulate the data travelling back and forth, but simply acts as a proxy between the two LU-LU sessions. (VM-CA:TPX and CA:TPX-workstation) To use TN3270, CA-TPX has an LU2-TN3270 translator built into it. It must extract the 3270 data stream from one end and repackage it for sending to the other. This means that CA-TPX itself it the telnet client and is simply getting the data stream from the SNA 3270 emulator. But CA-TPX is responsible to connect to the VM telnet server and negotiate the TN3270 session. This includes any TN3270E issues. So, while the *emulator* may be sending the same things, CA-TPX may not. You need to compare the 3270 data stream that CA-TPX is sending to and receiving from VM. (Getting the trace from CA-TPX is probably best.) Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
To all, Some time ago I had a mysterious problem dealing with IND$FILE with symptoms similar to what you are having, although, mine was with CICS also. The problem that I encountered was with a getmain for storage to build additional messages. It turned out that the getmain was for 0 bytes and that wouldn't work. I had the source at the time and inserted my own check for 0 bytes and bypassed the getmain which allowed it to go to EOJ. I don't know whether this is the same, but that problem exhibited no symptoms at all and it was just plain luck that I found the error. I don't know if this is germane to the subject, but it was an undiscovered bug with the product. Even though it's been around a long time, you may be encountering a problem that heretofore has gone unreported. Just trying to help. Fred Hoffman -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Horlick, Michael Sent: Friday, December 05, 2008 2:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Hello Alan et all, Just a little update. I created a 24 record file with 1234567890 repeated for 80 characters and asked the client to test. This time he says the file transfer doesn't issue messages but also doesn't upload the file to the host. It completes but the CMS file is not there. Again, this only happens with the combination of CA-TPX and TCP/IP for VM. When he tries with CA-TPX and SNA it works. The same settings for the emulator (same size screen, etc...) How could the same 3270 datastream cause this? They have their terminal set up as a model 5 My only thought is that it must be how the device appears to VM/VTAM. For SNA, it is a remote device. When he is on SNA and TPX and I display the user I see: Termid: TX262144 Model: PC92-5AG Logmode: SNX32705 I have no idea where it gets that PC92-5AG model info from. Would you or anyone else know? Then when he creates a virtual terminal session on TPX he gets: SessionApplidStatus VTermid--Status Flags---Appl.Logmode VM2VM<== ACTIVE TPXGR052 400010C1 T3278M2E This application logmode of T3278M2E is a CA-TPX one and when I do a 'CP Q' on his CMS user I see him on TPXGR052. For TCP/IP for VM, there is a DIAL VTAM and I set the DLOGMOD to D4B3290. I think I have tried different DLOGMOD's (NSX32705) and even asked them to configure as a Model 2 but still no go. The SNA DLOG of SNX32705 looks like this: SNX32705 MODEENT LOGMODE=SNX32705,FMPROF=X'03',TSPROF=X'03', PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080', RUSIZES=X'87F8', PSERVIC=X'028018501B847F00' I'm not much of a VTAM maven. Is there anything in that macro related to file transfer? Is there something I can use to replace IND$FILE with? I suggested native VM (whick works) and also ftp (but that's a hassle with write access to their A-disk) but they prefer the way they always work (but just with TCP/IP). Wednesday, I'll be visiting the client and be screwing around with DLOGMOD's etc... Regards, Mike
Re: TRANS13 , IND$FILE and CA-TPX
Hello Alan et all, Just a little update. I created a 24 record file with 1234567890 repeated for 80 characters and asked the client to test. This time he says the file transfer doesn't issue messages but also doesn't upload the file to the host. It completes but the CMS file is not there. Again, this only happens with the combination of CA-TPX and TCP/IP for VM. When he tries with CA-TPX and SNA it works. The same settings for the emulator (same size screen, etc...) How could the same 3270 datastream cause this? They have their terminal set up as a model 5 My only thought is that it must be how the device appears to VM/VTAM. For SNA, it is a remote device. When he is on SNA and TPX and I display the user I see: Termid: TX262144 Model: PC92-5AG Logmode: SNX32705 I have no idea where it gets that PC92-5AG model info from. Would you or anyone else know? Then when he creates a virtual terminal session on TPX he gets: SessionApplidStatus VTermid--Status Flags---Appl.Logmode VM2VM<== ACTIVE TPXGR052 400010C1 T3278M2E This application logmode of T3278M2E is a CA-TPX one and when I do a 'CP Q' on his CMS user I see him on TPXGR052. For TCP/IP for VM, there is a DIAL VTAM and I set the DLOGMOD to D4B3290. I think I have tried different DLOGMOD's (NSX32705) and even asked them to configure as a Model 2 but still no go. The SNA DLOG of SNX32705 looks like this: SNX32705 MODEENT LOGMODE=SNX32705,FMPROF=X'03',TSPROF=X'03', PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080', RUSIZES=X'87F8', PSERVIC=X'028018501B847F00' I'm not much of a VTAM maven. Is there anything in that macro related to file transfer? Is there something I can use to replace IND$FILE with? I suggested native VM (whick works) and also ftp (but that's a hassle with write access to their A-disk) but they prefer the way they always work (but just with TCP/IP). Wednesday, I'll be visiting the client and be screwing around with DLOGMOD's etc... Regards, Mike
Re: TRANS13 , IND$FILE and CA-TPX
On Thursday, 12/04/2008 at 03:18 EST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > Hello Alan, > > Thanks for the info. I do have NOTN3270E specified Then the problem is not in VM's TN3270E support! :-) > MTU sizes? I have '1500' specified in my PROFILE TCPIP. I'll check with > the client. Is there any trace on the mainframe that I can do that would > help diagnose the error? No. The MTU is an administratively-defined value based on the technology you are using. E.g. maybe it should be 1492, not 1500. Have to talk to switch admin. Actually, since you're not getting a hang condition, it is probably *isn't* MTU. One of the ways to verify that MTU is/isn't interfering is to create a file that is 80 bytes wide (RECFM F) and 24 lines long. Each line consists of 8 copies of 1234567890. XEDIT the file. This will cause more than 1492 bytes to be sent. If you get a hang, the MTU is likely the problem, particularly if XEDITing a file with just one line in it works just fine. > I didn't realize IND$FILE wasn't supported. Do you have an idea how > IND$FILE does its business and reports on errors? To the best of my knowledge the 3270 file transfer protocol isn't published. I know that IND$FILE uses some special 3270 orders that target the "data mover" in the emulator rather than the display. And that's only because I've done some tracing in the past. The *orders* used *are* published in the 3270 Display Reference or in a 3174 Functional Description. I would be getting a 3270 trace from the emulator an compare the 3270 data streams in the working and failing cases. Oh, and David's post makes me think: Verify that in the failing and non-failing cases, the alternate screen sizes are the same. I.e. the VM logo screen is 32x80 or 24x80 or whatever in either case. If they are different, then there is an issue with extended attributes in the emulator. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
Note that CUT and DFT only matter for real coax. Not applicable to IP connections. Do you know the previous LOGMOD entry he was using on SNA? I think you needed to have extended data streams turned on for IND$FILE to work (and I think the IP stuff always provides that bit in response to a RSF). The emulator is the likely cause of the problem. You can do a telnet trace to look at the terminal type negotiation to determine whether it's negotiating a terminal type with a -E at the end. On 12/4/08 3:21 PM, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > Mike, > > Thanks for that info. Will ask client about CUT and DFT and other specs. > Will change his logon and get his console spooled. I have CA-VM:Spool > and can check his console.
Re: TRANS13 , IND$FILE and CA-TPX
Mike, Thanks for that info. Will ask client about CUT and DFT and other specs. Will change his logon and get his console spooled. I have CA-VM:Spool and can check his console. Regards, Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: December 4, 2008 3:15 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX Google turned up: - TRANS13 Error Writing File to Host: File Transfer Canceled Explanation: Host program has detected an error in the data file during the Send operation. User Action: Retry. If problem persists, call your host personnel. - Some listed the same Explanation for a "Receive" operation. Editing the IND$FILE MODULE and searching for '13' also turned up: 13 Error writing file to host: file transfer canceled $ Google also showed a number of different terminal emulators displaying TRANS13. One of them referred to the difference between CUT (Control Unit Terminals) and DFT (Distributed Function Terminals) terminals (if I remember those acronyms correctly). Which are you using? Often, the descriptions were for PC to MVS/TSO. Most referred to the DCB being wrong (LRECL, RECFM, and for MVS, BLKSIZE). What are the DCB specs for the file being transferred? Can you provide the exact command you are using? If it's from a GUI, then check the CMS command buffer for the previous command immediately after the failure. You can do that by issuing: SET PF07 RETRIEVE BACKWARD and the pressing PF7 twice. The first press will display the SET command. The second should show the IND$FILE command with all its arguments. That may provide a little bit more useful information. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Horlick, Michael" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" 12/04/2008 01:40 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject TRANS13 , IND$FILE and CA-TPX Greetings, My client is still having problems with using IND$FILE over TCP/IP for VM and CA-TPX. This does not occur with SNA. I have opened an issue with CA and they can?t see the problem and the client is supposed to be dealing with MicroFocus regarding the PC component of this puzzle (ProClient). The client has asked me about TN3270E and claims that the Cisco Router 7505 that he uses for SNA connectivity to the mainframe has TN3270E installed. I explained that I don?t think that is an issue (he pointed to me to an IBM web-site stating that TN3270E is not available in TCP/IP for VM for terminals, just printers). He think maybe it is an issue. Also, the file transfer works when he deselects extended attributes. Any clue on how to get to the bottom of this? What exactly does a TRANS13 error mean and how does IND$FILE communicate that info to the emulator so that a pop up window would appear with that error? Is it a return code from the IND$FILE module? Maybe I need to open an issue with IBM to help me understand IND$FILE and when this error message occurs? Of course, to complicate the issue, sometimes a file transfer works, sometimes it says it works but doesn?t actually create the file on the mainframe and sometimes he get the TRANS13 (but only moving a file from the PC to the mainframe and not the reverse). Why would something work in SNA and not TCP/IP when the same 3270 datastream is sent to it? Any nuggets of wisdom/advice would be appreciated. Mike Horlick CGI Montreal The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: TRANS13 , IND$FILE and CA-TPX
Hello Alan, Thanks for the info. I do have NOTN3270E specified INTERNALCLIENTPARMS PORT 23 PORT 2300 TIMEMARK 600 CCSTERMNAME TCPIP CONNECTEXIT SCEXIT NOTN3270E MTU sizes? I have '1500' specified in my PROFILE TCPIP. I'll check with the client. Is there any trace on the mainframe that I can do that would help diagnose the error? I didn't realize IND$FILE wasn't supported. Do you have an idea how IND$FILE does its business and reports on errors? Regards, Mike -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: December 4, 2008 3:05 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: TRANS13 , IND$FILE and CA-TPX On Thursday, 12/04/2008 at 02:40 EST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > The client has asked me about TN3270E and claims that the Cisco Router 7505 > that he uses for SNA connectivity to the mainframe has TN3270E installed. I > explained that I don?t think that is an issue (he pointed to me to an IBM > web-site stating that TN3270E is not available in TCP/IP for VM for terminals, > just printers). He think maybe it is an issue. You can always specify NOTN3270E in InternalClientParms to see if it a problem. (In all cases where NOTN3270E has fixed a problem, the defect was in the 3270 client software, not VM.) > Also, the file transfer works when he deselects extended attributes. ...which has nothing to do with TN3270E. (People sometimes confuse the "TN3270 Enhancements" RFC with "3270 extended attributes". > Any clue on how to get to the bottom of this? What exactly does a TRANS13 error > mean and how does IND$FILE communicate that info to the emulator so that a pop > up window would appear with that error? Is it a return code from the IND$FILE > module? Maybe I need to open an issue with IBM to help me understand IND$FILE > and when this error message occurs? Of course, to complicate the issue, > sometimes a file transfer works, sometimes it says it works but doesn?t > actually create the file on the mainframe and sometimes he get the TRANS13 (but > only moving a file from the PC to the mainframe and not the reverse). Remember that IND$FILE is provided as-is on the host. There is no support. As to what the pop-up is showing, that's in the realm of the emulator. It can show you whatever it wants. Talk to the emulator vendor. > Why would something work in SNA and not TCP/IP when the same 3270 datastream is > sent to it? The emulator could act differently when configured for TCP/IP vs. SNA. I would expect the 3270 data stream from the emulator to the host to be identical. > Any nuggets of wisdom/advice would be appreciated. Make sure the MTU sizes are correct all along the way between the host and the workstation. If a frame is truncated, you will get errors. Alan Altmark z/VM Development IBM Endicott
Re: TRANS13 , IND$FILE and CA-TPX
Google turned up: - TRANS13 Error Writing File to Host: File Transfer Canceled Explanation: Host program has detected an error in the data file during the Send operation. User Action: Retry. If problem persists, call your host personnel. - Some listed the same Explanation for a "Receive" operation. Editing the IND$FILE MODULE and searching for '13' also turned up: 13 Error writing file to host: file transfer canceled $ Google also showed a number of different terminal emulators displaying TRANS13. One of them referred to the difference between CUT (Control Unit Terminals) and DFT (Distributed Function Terminals) terminals (if I remember those acronyms correctly). Which are you using? Often, the descriptions were for PC to MVS/TSO. Most referred to the DCB being wrong (LRECL, RECFM, and for MVS, BLKSIZE). What are the DCB specs for the file being transferred? Can you provide the exact command you are using? If it's from a GUI, then check the CMS command buffer for the previous command immediately after the failure. You can do that by issuing: SET PF07 RETRIEVE BACKWARD and the pressing PF7 twice. The first press will display the SET command. The second should show the IND$FILE command with all its arguments. That may provide a little bit more useful information. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. "Horlick, Michael" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" 12/04/2008 01:40 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject TRANS13 , IND$FILE and CA-TPX Greetings, My client is still having problems with using IND$FILE over TCP/IP for VM and CA-TPX. This does not occur with SNA. I have opened an issue with CA and they can?t see the problem and the client is supposed to be dealing with MicroFocus regarding the PC component of this puzzle (ProClient). The client has asked me about TN3270E and claims that the Cisco Router 7505 that he uses for SNA connectivity to the mainframe has TN3270E installed. I explained that I don?t think that is an issue (he pointed to me to an IBM web-site stating that TN3270E is not available in TCP/IP for VM for terminals, just printers). He think maybe it is an issue. Also, the file transfer works when he deselects extended attributes. Any clue on how to get to the bottom of this? What exactly does a TRANS13 error mean and how does IND$FILE communicate that info to the emulator so that a pop up window would appear with that error? Is it a return code from the IND$FILE module? Maybe I need to open an issue with IBM to help me understand IND$FILE and when this error message occurs? Of course, to complicate the issue, sometimes a file transfer works, sometimes it says it works but doesn?t actually create the file on the mainframe and sometimes he get the TRANS13 (but only moving a file from the PC to the mainframe and not the reverse). Why would something work in SNA and not TCP/IP when the same 3270 datastream is sent to it? Any nuggets of wisdom/advice would be appreciated. Mike Horlick CGI Montreal The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: TRANS13 , IND$FILE and CA-TPX
On Thursday, 12/04/2008 at 02:40 EST, "Horlick, Michael" <[EMAIL PROTECTED]> wrote: > The client has asked me about TN3270E and claims that the Cisco Router 7505 > that he uses for SNA connectivity to the mainframe has TN3270E installed. I > explained that I don?t think that is an issue (he pointed to me to an IBM > web-site stating that TN3270E is not available in TCP/IP for VM for terminals, > just printers). He think maybe it is an issue. You can always specify NOTN3270E in InternalClientParms to see if it a problem. (In all cases where NOTN3270E has fixed a problem, the defect was in the 3270 client software, not VM.) > Also, the file transfer works when he deselects extended attributes. ...which has nothing to do with TN3270E. (People sometimes confuse the "TN3270 Enhancements" RFC with "3270 extended attributes". > Any clue on how to get to the bottom of this? What exactly does a TRANS13 error > mean and how does IND$FILE communicate that info to the emulator so that a pop > up window would appear with that error? Is it a return code from the IND$FILE > module? Maybe I need to open an issue with IBM to help me understand IND$FILE > and when this error message occurs? Of course, to complicate the issue, > sometimes a file transfer works, sometimes it says it works but doesn?t > actually create the file on the mainframe and sometimes he get the TRANS13 (but > only moving a file from the PC to the mainframe and not the reverse). Remember that IND$FILE is provided as-is on the host. There is no support. As to what the pop-up is showing, that's in the realm of the emulator. It can show you whatever it wants. Talk to the emulator vendor. > Why would something work in SNA and not TCP/IP when the same 3270 datastream is > sent to it? The emulator could act differently when configured for TCP/IP vs. SNA. I would expect the 3270 data stream from the emulator to the host to be identical. > Any nuggets of wisdom/advice would be appreciated. Make sure the MTU sizes are correct all along the way between the host and the workstation. If a frame is truncated, you will get errors. Alan Altmark z/VM Development IBM Endicott
TRANS13 , IND$FILE and CA-TPX
Greetings, My client is still having problems with using IND$FILE over TCP/IP for VM and CA-TPX. This does not occur with SNA. I have opened an issue with CA and they can't see the problem and the client is supposed to be dealing with MicroFocus regarding the PC component of this puzzle (ProClient). The client has asked me about TN3270E and claims that the Cisco Router 7505 that he uses for SNA connectivity to the mainframe has TN3270E installed. I explained that I don't think that is an issue (he pointed to me to an IBM web-site stating that TN3270E is not available in TCP/IP for VM for terminals, just printers). He think maybe it is an issue. Also, the file transfer works when he deselects extended attributes. Any clue on how to get to the bottom of this? What exactly does a TRANS13 error mean and how does IND$FILE communicate that info to the emulator so that a pop up window would appear with that error? Is it a return code from the IND$FILE module? Maybe I need to open an issue with IBM to help me understand IND$FILE and when this error message occurs? Of course, to complicate the issue, sometimes a file transfer works, sometimes it says it works but doesn't actually create the file on the mainframe and sometimes he get the TRANS13 (but only moving a file from the PC to the mainframe and not the reverse). Why would something work in SNA and not TCP/IP when the same 3270 datastream is sent to it? Any nuggets of wisdom/advice would be appreciated. Mike Horlick CGI Montreal
