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



--
Chuck...Thanks for the tips.  IPL does not seem to be helping...as we have 
tried that.  We then varyon the device and the writer fails to start....and we 
are right back in the same situation.

>>> clewis@iquest.net 10/15/02 09:01AM >>>
Yuck...

Seen stuff like this before...

Not really good choices, but:

(1) Try ending QSPL maybe (and then restarting it of course). Not really
sure if that will force QSYSARB to release it or not.

(2) IPL

The situations I've seen this in were with devices connected via Client
Access (Displays) and in some case killing QINTER (obviously NOT something
you can do during normal hours) would "fix" it (we ended QINTER each evening
for daily processing and backups). When that would not work, an IPL did the
job.

Chuck

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Rick Klopfer
Sent: Tuesday, October 15, 2002 7:15 AM
To: midrange-l@midrange.com
Subject: Printer problem.


--
We have this printer that will not vary on and sits at "vary on pending",
and we are sure the printer is functioning as we have tried it in another
situation, and it works.  But our real problem is that QSYSARB has an
*EXCLRD lock on the *DEVD and we cannot get it to relinquish it.

We are at V4R5 and have tried the VRYCFG FRCVRYOFF(*LOCK) command.  And that
does vary off the device but does not cause QSYSARB to give up this lock.

Any suggestions?

Rick Klopfer--

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
[ Converted text/html to text/plain ]
Chuck...Thanks for the tips.  IPL does not seem to be helping...as we have
tried that.  We then varyon the device and the writer fails to start....and we
are right back in the same situation.
>>> clewis@iquest.net 10/15/02 09:01AM >>>
Yuck...
Seen stuff like this before...
Not really good choices, but:
(1) Try ending QSPL maybe (and then restarting it of course). Not really
sure if that will force QSYSARB to release it or not.
(2) IPL
The situations I've seen this in were with devices connected via Client
Access (Displays) and in some case killing QINTER (obviously NOT something
you can do during normal hours) would "fix" it (we ended QINTER each evening
for daily processing and backups). When that would not work, an IPL did the
job.
Chuck
-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On[1] Behalf Of Rick Klopfer
Sent: Tuesday, October 15, 2002 7:15 AM
To: midrange-l@midrange.com
Subject: Printer problem.
--
We have this printer that will not vary on and sits at "vary on pending",
and we are sure the printer is functioning as we have tried it in another
situation, and it works.  But our real problem is that QSYSARB has an
*EXCLRD lock on the *DEVD and we cannot get it to relinquish it.
We are at V4R5 and have tried the VRYCFG FRCVRYOFF(*LOCK) command.  And that
does vary off the device but does not cause QSYSARB to give up this lock.
Any suggestions?
Rick Klopfer--
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l[2]
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.[3]

===References:===
  1. mailto:midrange-l-admin@midrange.com]On
  2. http://lists.midrange.com/cgi-bin/listinfo/midrange-l
  3. http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.