RE: Logon to only a specific workstation.

Thanks everyone,  I appreciate the help.  I will try the routing program.


Darrin Nelson

----- Original Message -----
From: QSRVBAS <qsrvbas@xxxxxxxxxxxx>
Date: Tue, 02 Mar 2004 18:05:17 -0800
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Logon to only a specific workstation.

> midrange-l-request@xxxxxxxxxxxx wrote:
> 
> >   3. RE: Logon to only a specific workstation.
> >      (Martin, Steve (MAN-Golden))
> >
> >One way I've seen it done, is to use a file of at least 2 fields, UserID &
> >WorkStn. Create a program that retrieves the user profile and workstation,
> >then does a lookup in the file. If the UserID exists, and workstation ==
> >WorkStn, then continue.
> >
> >Use the new program as the INLPGM in each user profile you want to control.
> 
> (Hi, Steve.) Suggestions to use an exit program might be reasonable, but 
> be extremely careful if you're writing your own. It's necessary to 
> understand critical details of the structures being passed because it's 
> easy to make at least one specific minor mistake which will throw your 
> system wide open.
> 
> 
> Authorization lists have also been suggested and can be an excellent 
> control mechanism. But it can get loose when auto-config creates new 
> devices. They take maintenance and it takes thought on setting them up 
> well in the beginning. Not exactly rocket science, but forethought makes 
> a difference.
> 
> Now, an INLPGM has its own merits; however, I'd go with a routing 
> program instead. The program itself could be an almost exact copy, but 
> it'd apply to everyone without needing to update individual profiles nor 
> would it interfere with any existing INLPGM.
> 
> The major logical difference between a routing program and an INLPGM for 
> this purpose would be that the routing program would end with a 
> statement like TFRCTL QSYS/QCMD instead of just a RETURN.
> 
> In the default case, use the CHGRTGE command to change the 9999-*ANY 
> and/or the compare value 'QCMDI' routing entry in QINTER to name your 
> program instead of QSYS/QCMD. Reapply as needed after upgrades.
> 
> If the program contains essentially nothing but the TFRCTL command, you 
> shouldn't even notice a defference. Add a SNDMSG command before TFRCTL 
> and you have a trivial program that demonstrates how it works without 
> being intrusive (unless you reference a message queue that the user has 
> insufficient authority for or some other problem without handling the 
> error). And once the program's in place, you can use it for a number of 
> purposes; I commonly use mine to pop-up bulletin windows at signon when 
> news needs to be sent -- "Shutdown at 2:00 PM today", e.g.
> 
> Tom Liotta
> 
> -- 
> Tom Liotta
> The PowerTech Group, Inc.
> 19426 68th Avenue South
> Kent, WA 98032
> Phone  253-872-7788 x313
> Fax    253-872-7904
> http://www.powertech.com
> 
> 
> _______________________________________________
> 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.
> 

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm