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



Hi Chris,

I don't have an answer, just something to be aware of that you didn't mention in your email -- all the input fields must be in the same order as the original display file so the buffer matches.

This is not to say you can't place them somewhere else on the screen, just make sure they are in the same order relative to each other in the source so they end up in the same positions in the i/o buffer.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 8/4/2020 12:07 PM, Chris Wager | 56K Projects wrote:
Evening,


I have tried to create a custom login screen it won't work.


I copied the display file QDSIGNON member from QSYS/QDDSSRC to SIGNON/QDDSSRC


STRPDM and selected the correct LIB/FILE and then Edified the QDSIGNON Member.


Option 14 / F4 to compile into the QSYS Library and name the compiled object LILYSIGNON


Changed the Object Authority as follows:


PUBLIC *EXCLUDE

QSYS *ALL


Used CHGSBSD to set the SGNDSPF to QSYS/LILYSIGNON.


Issued a PWRDWNSYS using F4 to set restart.


But I still have the default login screen, what have I done wrong :(


If any of you can help that would be great.


Thanks
Chris




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.