Jan,
Are you actually running VM (i.e. VM/ESA) v2.3 or is that the level of
IND$FILE?
If VM/ESA v2.3, that's older than dirt and I don't know if it runs TCP/IP.
However, if it does, you could consider converting IND$FILE to FTP and
bypass the whole 3174 issue.
Dennis
Mutual of Omaha
[EMAIL PROTECTED]
COM
Sent by: "The IBM To
z/VM Operating [email protected]
System" cc
<[EMAIL PROTECTED]
ARK.EDU> Subject
VM2.3 IN$FILE & 3174
08/14/2006 10:05
AM
Please respond to
"The IBM z/VM
Operating System"
<[EMAIL PROTECTED]
ARK.EDU>
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
