As Lukas mentioned you'll have to restart the Qinter subsystem. What we
do when we make a change to the signon display is, we check to be sure
everyone is out of Qinter, we then do the command TFRJOB QCTL and press
enter - this moves our sign on job to QCTL so we can end QINTER and
still be signed on. Then ENDSBS QINTER and then STRSBS QINTER. Then
you can do the TFRJOB QINTER to put your job back into Qinter. Sign off
and you should see the changes to your sign on screen.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Laine, Rogers
Sent: Wednesday, September 09, 2009 3:56 PM
Subject: Custom DQSIGNON
I would like to create a custom SIGNON screen under v6.1, This is what I
have done thus far....
1. I copied the installed DSPF called QDSIGNON from QGPL\QDDSSRC to
QGPL/QDDSSRC and called it MYSIGNON using the below command.
4. I go to change my test user profile to use MYSIGNON.
CHGUSRPRF USRPRF(MISRML9) INLPGM(QGPL/MYSIGNON)
I get the below message...
Object MYSIGNON in library QGPL not found.
So this makes me believe that the compile of the sign on display did not
When I use Work with Library objects I so not find the MYSIGNON object.
What am I doing wrong, any help would be appreciate, as always.
This E-Mail transmission (and/or the documents accompanying it)
may contain information belonging to the sender which is confidential,
privileged and/or exempt from disclosure under applicable law. The
information is intended only for the use of the individual(s) or entity
named above. If you are not the intended recipient, you are hereby
notified that any disclosure, copying, distribution or the taking of any
action in reliance on the contents of this information is strictly
prohibited. If you have received this E-Mail transmission in error,
please immediately notify us by return E-Mail or telephone to arrange
for return of its contents including any documents.
This mailing list archive is Copyright 1997-2020 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