Hello Mike,
IND$FILE needs the extended data stream to be set in the DLOGMOD.
SNX32705 is an SNA 3270 with extended data stream.
Typically TCP/IP is uses a non-SNA logmode.
Try NSX32705 or NSX32702 in ISTINLCM.
Ed Martin
Aultman Health Foundation
330-588-4723
ext 40441
________________________________
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Dodds, Jim
Sent: Thursday, November 13, 2008 11:51 AM
To: [email protected]
Subject: Re: IND$FILE fails through CA-TPX and TCP/IP for VM
I remember I had a similar problem about 15 years ago when first started
using this a new job. The problem was that there is a bit set in the
logmode for file transfer to be able to use or not use. Check the
logmode you are currently using and see if that could be the problem.
Jim Dodds
Systems Programmer
Kentucky State University
400 East Main Street
Frankfort, Ky 40601
502 597 6114
________________________________
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Horlick, Michael
Sent: Thursday, November 13, 2008 10:17 AM
To: [email protected]
Subject: IND$FILE fails through CA-TPX and TCP/IP for VM
Greetings,
My client is moving away from SNA to TCP/IP. We use CA-TPX as our
session manager and the client uses a terminal emulator called
'Proclient OnWeb Web to Host'.
They use IND$FILE and are getting error - TRANS13 when uploading a file
from their PC to their CMS A-disk. It doesn't happen to them when native
VM and it doesn't happen doing a download from the mainframe to the PC.
I use myExtra! and under TPX I have no problems. They have no problems
if using SNA.
I specified the following in VM/VTAM. My SCEXIT does a DIAL to VTAM for
any IP terminals connected to port 23
TC070 LOCAL CUADDR=070,TERM=3277,USSTAB=USSTCPIP,FEATUR2=EDATS, *
LOGAPPL=TPX,MODETAB=ISTINCLM,DLOGMOD=D4B3290
I think when they connect via SNA they get a DLOGMOD of SNX32705.
Has this happened to anyone else? Any suggestions?
Thanks,
Mike
