No doubt, you're workstation is routing to QINTER sbs by default. You
need to add a workstation name entry to your new subsystem (so your
emulation session will be acquired by the new SBS for login).
I think the order you start those subsystems will alter how the devices
get acquired, so you might have to endsbs(qinter), then strsbs(newsbs),
strsbs(qinter) so that your new sbs will get the workstation device.
Obviously, you don't want to do that during the day...
It's been ages since I looked into this, so someone chime in if I got it
wrong, please...
-Eric
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Laine, Rogers
Sent: Wednesday, September 09, 2009 4:40 PM
To: Midrange Systems Technical Discussion
Subject: RE: Custom DQSIGNON
Jim,
I'm not ready to move this to production. I'm trying to use a test id
(MISRML9) and a SBS called TESTSBS so I can validate this change before
moving it to QCTL. At that time I would use your below steps.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rubino, Jim
Sent: Wednesday, September 09, 2009 4:16 PM
To: Midrange Systems Technical Discussion
Subject: RE: Custom DQSIGNON
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.
Jim
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Laine, Rogers
Sent: Wednesday, September 09, 2009 3:56 PM
To: midrange-l@xxxxxxxxxxxx
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.
CPYF FROMFILE(QGPL/QDDSSRC) TOFILE(QGPL/QDDSSRC) FROMMBR(QDSIGNON)
TOMBR(MYSIGNON) MBROPT(*YES)
2. I make a minor change to the heading on line one using the below
command.
STRSEU SRCFILE(QGPL/QDDSSRC) SRCMBR(MYSIGNON)
3. The next thing I believe is to compile the sign-on display using the
below command..
CRTDSPF FILE(QGPL/MYSIGNON) SRCFILE(QGPL/QDDSSRC) MAXDEV(256)
I got the below message...
File MYSIGNON created in library QGPL.
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
work correctly.
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.
Rogers
************************************************
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 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.
midrange.com
