On Friday, 12/12/2008 at 10:13 EST, "Horlick, Michael" <michael.horl...@cgi.com> 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
