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


  • Subject: Re: changing signon display
  • From: Pete Hall <pbhall@xxxxxxxxxx>
  • Date: Wed, 17 Jan 2001 21:33:26 -0600

At 10:11 01/17/2001, Benjamin Budai wrote:
>I have changed the sigon display for QINTER in the subsystem description,
>but I get the old signon. The new DSPF has the same name as the old one,
>but is in a different library. DSPSBSD reports the new display file.
>Stopping and restarting QINTER doesn't help. I've renamed the old signon
>DSPF, but seems that OS/400 keeps a pointer reference to the object,
>because QINTER still starts with the old screen.
>How can I fix this without a IPL? (Anyway, is this normal behaviour or not?)

Could there be more than one QINTER SBSD on your system? At one time there 
were duplicate subsystem descriptions in QSYS and QGPL. Possibly duplicate 
display files too. Easy enough to check...


Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.