Keeping workstation up even though QINTER is down
Scott Christopher
shut down QINTER. The problem is that makes me have to go to the
computer room to do the work i need to do. And all of my notes are on
my computer in the offices.
Isn't there a way that you can move or create a workstation in QCTL,
so that when QINTER is down, that particular workstation will still be
useable?
If so, can someone please tell me how to do this?
Thank you for any help you can give me.
Kirk
You can use the ADDWSE cmd to add Device names like this
ADDWSE SBSD(QCTL) WRKSTN(XXXXXX) where xxxxxx is a specific device name or
ADDWSE SBSD(QCTL) WRKSTN(AAA*) where the device name starts with AAA
You must set your iSeries Access Session to use the name in the ADDWSE
cmd. This will allow you to signon if QINTER is down as long as TCP/IP
is UP.
If you are alreaddy signed on to QINTER you could
TFRJOB QCTL and press enter. A WRKACTJOB should now show you running in
QCTL and you can end QINTER
Scott Christopher
Thank you so much! That's exactly what I was looking for.
Peter H. Coffin
It's clever, but ... couldn't any user determine that special
workstation name and use it to log on when Scott didn't want them to,
and deny Scott from connecting using that workstation ID in the process?
Doing something with the majority of the users' initial programs to
check whether logins are allowed at that particular time, and signing
the user off with a message if not, might be a good deal more reliable.
--
Random Wisdom: Let a pizza fresh from the oven stand for several minutes
before cutting; it will reduce the amount of sauce running
out, and help prevent mouth burns.
Robert Comer
>workstation name
He could set the permissions to that configuration object so that only
he could use it...
--
Bob Comer
Hal
> workstation name and use it to log on when Scott didn't want them to,
> and deny Scott from connecting using that workstation ID in the process?
> Doing something with the majority of the users' initial programs to
> check whether logins are allowed at that particular time, and signing
> the user off with a message if not, might be a good deal more reliable.
>
A clever user might be able to find out the device name for the
special workstations... .but the workstation name entries in a
subsystem definition support wildcards, on mine I have a QINTER2
subsystem that accepts connections from devices ID's named "TEST*". If
my usual does not work, say, testchris, I can put any kind of suffix
onto the end of the workstation name and the device will get created
when I try to connect, assuming of course that TCP/IP is working.
I have a rather funky custom sign-on screen for that subsystem, so
most users would get discouraged even if they found workstation names
and knew how to configure mochasoft/client access to use a custom
device name.
Good luck with it.
Chris
pdseay
> > It's clever, but ... couldn't any user determine that special
If you feel it is worth the effort, you could defeat the clever user
by creating a routing entry program that signs off those who are not
in with the in crowd.
Proof of concept routing entry program RESTRICTED/RESTRICTED:
PGM
DCL VAR(&USRPRF) TYPE(*CHAR)
RTVUSRPRF RTNUSRPRF(&USRPRF)
IF COND(&USRPRF *NE RESTRICTED) THEN(+
SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) +
MSGDTA('Sorry, you''re not authorized to this SBS') MSGTYPE
(*ESCAPE))
TFRCTL PGM(QCMD)
RETURN
ENDPGM
Minimum commands to create restricted access interactive subsystem:
CRTSBSD SBSD(RESTRICTED/RESTRICTED) POOLS((1 *BASE)) TEXT('Restricted
access interactive subsystem')
ADDWSE SBSD(RESTRICTED/RESTRICTED) WRKSTN(RSTRCTD*)
ADDRTGE SBSD(RESTRICTED/RESTRICTED) SEQNBR(10) CMPVAL(*ANY) PGM
(RESTRICTED/RESTRICTED) CLS(QINTER)
Regards,
Phil