× 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.



Been a while since we had a problem that could not be fixed by:
warning everyone still connected to get their jobs to a conclusion;
stopping any printers involved;
pulling all the plugs (power off controller, modems, modem-simulators, cisco, wireless, whatever);
varying off the stuff,
wait 5 minutes,
plug everything back in,
vary it all back on,
restart any printers involved,
ask the person with the device originally in trouble to retry & if they Ok, tell everyone else involved that they can get back on the network.

Sometimes there is a "hung" error message that does not go away.
The wait 5 minutes gives the system a chance to clear all error messages associated with whatever varied on, started, working, whatever.

I believe the Controller comes with a diskette drive, where the diskette has a backup copy of the config data & there is a process to reload whatever from the backup. Every time the config is updated, the backup is supposed to be replaced.

Assuming the AS/400 iSeries Systemi whatever is on automatic configuration, then it will recognize whatever new story is coming thru the controller.

Something you might want to check ... we have our system values set to limit the total number of connected devices, as security against hacker coming in on
QDEV WHATEVER 0010
doing the maximum password guesses, getting varied off, then trying
QDEV WHATEVER 0011 12 13 14 15 to infinity

If you going to be exercising the number of connections, you might want to adjust that system value until you get done here.

Last night all of our terminals went down in the factory. I was able
to get the RF terminals running again but can not get the 5494 twinax
devices to work.

Qsysopr message is:
System detected an internal error on controller GR5494WS.

My partner is traveling to the site this morning to inspect the
controller which may be dead.

I think another possible problem could be a damaged controller
description. I'm not experienced with fixing that.
Does one retrieve the configuration source, delete the current
controller description. compile and run the CLP script of the
configuration?

What about all of the devices associated with the controller. Do they
need to be deleted and recreated.

Thanks for your help,
Greg
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.