Title: Message
Hi Jan,
 
It's been years since I've worked with IND$FILE, so take this advice with a grain of salt, but try changing the packet size of the IND$FILE to 256 bytes.  I vaguely recall a problem that I had where a transfer would just hang, that was circumvented by drastically reducing the packet size like this.
 
Regards,
Doug
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: August 14, 2006 9:06 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: VM2.3 IN$FILE & 3174


I had a very interesting day working with a 3174.  The plan is to move from a 3274-41D to a 3174-01L.  The first part of the plan of making a copy of the already working configuration, which went fine.  (By the way, I walked into this shop.  Everything was already there, they just wanted copies made and then decided to move to the 3174. They only had one terminal on the 3174.)  

Then we moved a Terminal to the 3174, which I then found out had an emulation terminal board in it.  (AST-3270 Coax-II-CUT Control Program Version 2.01)
 
I found out the VM 2.3 IN$FILE file transfer no longer worked.  Plug it back into the 3274 and it worked fine.  The transfer screen just signals wait.  There no error log or error message on the VM screen.
 
Went back to the configuration and found question 125 digit 6 and changed it to zero.  No change.

Reset the error logs on the 3174 and redid the transfer.  No file transfer, but no error messages.

Checked out questions 222, and changed it to 1.  Note that this is a Fundamental Software type processor.  No change.

No error messages, no error logs.  The file transfer program on the PC just flashes “wait” forever.  

Anybody got any suggestions?  What am I overlooking?

Configuration support A vanilla…. the default options


Jan Canavan

This e-mail and any attachments may contain confidential and
privileged information. If you are not the intended recipient,
please notify the sender immediately by return e-mail, delete this
e-mail and destroy any copies. Any dissemination or use of this
information by a person other than the intended recipient is
unauthorized and may be illegal.

Reply via email to