By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,611 Members | 2,259 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,611 IT Pros & Developers. It's quick & easy.

HIS 2000 connectivity problem

P: n/a
I was wondering if anybody has any insite into HIS 2000/SNA connectivty
problems. I work at a hospital with about 650 workstations. We run an
Ecplisys TDS console with SNA 4.0 SP4 or HIS 2000 SP1. Our backend
environment is an IBM MVS DB2 system. In most cases when our DB2 system
goes down or offline, our clients lose connectivty to the mainframe,
however, when the system is back online again, a majority of clients
never reconnect. The console is simply hung up and only ending the
ntvdm process or a reboot solves the problem.

Has anybody experceinced a similar issue? What could be causing this?

Also, is it possible to run more than one SNA/HIS session on a
workstation?

Thanks,
Brian

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
This is a Host Integration Server problem, not a DB2 issue. Suggest you post
on a HIS forum.

Personal experience: I never got HIS to work properly and eventually gave up
trying. DB2 Connect with IBM Communications Server worked fine. If you don't
have a firm commitment to HIS, migration to the IBM technologies is the
simplest solution.

<bj********@charter.net> wrote in message
news:11*********************@z14g2000cwz.googlegro ups.com...
I was wondering if anybody has any insite into HIS 2000/SNA connectivty
problems. I work at a hospital with about 650 workstations. We run an
Ecplisys TDS console with SNA 4.0 SP4 or HIS 2000 SP1. Our backend
environment is an IBM MVS DB2 system. In most cases when our DB2 system
goes down or offline, our clients lose connectivty to the mainframe,
however, when the system is back online again, a majority of clients
never reconnect. The console is simply hung up and only ending the
ntvdm process or a reboot solves the problem.

Has anybody experceinced a similar issue? What could be causing this?

Also, is it possible to run more than one SNA/HIS session on a
workstation?

Thanks,
Brian

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.