|
Mike, The only way I know of to do this works under level 30, but not under level 40.... so I can't reccomend it. It involves adding a workstation entry to an interactive subsystem similar to this: ADDWSE SBSD(MYSBS) WRKSTN(MYDEV) JOBD(MYLIB/MYJOBD) AT(*ENTER) The AT(*ENTER) parameter states that the device is allocated when the enter key is pressed. The jobd (MYLIB/MYJOBD) has to have a user profile specified in it. This is the user profile that the terminal job will run as. You'll want to make sure that this user profile is captured into an initial program, and that it has the barest minimum authority, because anyone will be able to run jobs as this user. Again, this only works at Security level 30 and below. At level 40 and above the OS will generate AF (authority failure) journal entry types in QAUDJRN whenever someone attempts to use a jobd that with a user profile attached(*). Another option (I haven't actually tried this), might be to generate a special signon screen for these kiosk terminals. You could make the password non-display, and give it a fixed value in the dds. Not sure if this is possiblle, but maybe it will spark an idea. jte mcrump@ballfoster.com wrote: > We have a situation whereby we want to setup a terminal to be used in a > kiosk like function. We would like to have the terminal not be required to > be signed on by any user. Is this possible? > > Here's what we want to do: > > We use Kronos for time keeping. Since we have eliminated time cards an > employee has no way to determine hours worked etc. We would like to set up > a terminal for use for time card review. Assuming the terminal is already > signed-on the only program running would be the time card review program. > The terminal will be using a card-key authorization with a PIN. I really > don't want to have this terminal to be signed-on on a regular basis. Is > there a way to allocate a terminal to a subsystem and not require a userid > and password manually keyed in? > > Thanks > > Mike Crump > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- -- John Earl johnearl@toolnet.com PowerTech Toolworks 206-575-0711 PowerLock Network Security www.toolnet.com The 400 School www.400school.com -- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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 [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.