I met one elderly gentleman about 10 years ago. He wrote a program on his HP3000 that interfaced with his phone switch using the FCONTROL intrinsic. No matter where a user was logged on, all the user's incoming calls would be forwarded to the nearest phone. Real spooky. The basis of his program of course, was that it was a Classic with all serial ports, so the locations were fixed. I imagine it would have also worked with nailed DTC ports. Tracy M. Johnson TRW Automotive Electronics Sensors & Components > -----Original Message----- > From: Donna Garverick [mailto:[log in to unmask]] > Sent: Wednesday, May 10, 2000 2:59 PM > To: [log in to unmask] > Subject: Re: Secret Identity -Reply > > > Bob Feighner wrote: > > > I've moved towards using separate udc files for each user > (or group of users), > > placing file assignments and initial login screens there. > > > > Alternately, you can use the HP variables hpuser and > hpaccount, programatically > > assigning the appropriate printers as needed. > > we do something quite similar here. each system has a simple > ascii file (we call it > 'storeid' because (duh) it's a store system :-) that lists > terminal ldev numbers in > one column and printer ldevs in another column. so (for > instance) if you're logging > onto ldev 100, the crossref in the file says you can print on > ldev 6. the user is > setup with a logon udc that executes (for us) a program (it > could easily be a > script...) that does all the setup work (issuing file > equations). this model works > for us because we're configured that particular users always > log on to specific > terminals. alternatively, you could enforce session names > where the session name is > somehow encoded to identify the user (like bob suggested). > - d > > -- > Donna Garverick Sr. System Programmer > 925-210-6631 [log in to unmask] > > >>>MY opinions, not Longs Drug Stores'<<< > >