×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I'm a bit new to this, and I have searched the archives but did not find
anything that matches my question.
We have an AS/400 system that needs to communicate with an LU6.2 session
on z/OS. So a device file was built for the AS/400 side.
The application on the z/OS system was cancelled in an attempt to test
error recovery. The application was restarted, and it got its APPLID
re-established (per VTAM on z/OS). Now the z/OS application can't
connect to the AS/400 and the AS/400 can't connect to the application
until some amount of time has elapsed.
It appears that there is something wrong with the way the device file
was built/genned (yes, this is a problem with the AS/400, because the
same test with two other platforms worked and they both recovered).
What, as a NON-AS/400 person, do I need to look at, or change in this
device file? So far the networking manuals I've found are not giving me
much help. And the original programmers for this system are no longer
here (I have no idea who or when this was done).
Regards,
Steve Thompson
-- All opinions expressed by me are my own and may not necessarily
reflect those of my employer. --
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
