|
> > Good explanation, John, I learned something there. But if > the users don't > have command line access, then this is all moot, isn't it? > Maybe I'm > really missing something there, so go easy on me if I did. Ah! I understand what you are saying - I guess that I am assuming that just about every user has access to a command line - and while that is generally true, it's not universally true. When the original poster wrote "If the user had access to a command line..." I assumed LMTCPB(*NO) rather than no command line available through any of their menu options. My experience is that most users can find a command line from somewhere within their menu system - whether it be from the SysReq menu, or a WRKOUTQ prompt, or a GO to an OS/400 menu that supports command entry - but again, that assumption is not likely to be universally true. I still like the dedicated command route, but as you pointed out, you would have to ensure (or engineer) access to a command line prompt. jte -- John Earl | Chief Technology Officer The PowerTech Group 19426 68th Ave. S Seattle, WA 98032 (253) 872-7788 ext. 302 john.earl@xxxxxxxxxxxxxxxxxx www.powertech.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.