|
>Do your users have access to a command line? If so, should they? Signon as a LMTCPB(*NO) user and do a System Rqs 3, 16 and hit F9. -Walden ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@xxxxxxxxxxxxxxx http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: michaelr_41@xxxxxxxxxxxxxx [mailto:michaelr_41@xxxxxxxxxxxxxx] Sent: Tuesday, November 11, 2003 4:16 PM To: Midrange Systems Technical Discussion Subject: Re: Problem implementing my first Webfacing application - User Profileis disabled when trying to run application I had the same issue...I changed the users to LMTCPB(*NO). Do you really need to limit capabilities? Do your users have access to a command line? If so, should they? On Tue, 11 Nov 2003 16:09:34 -0500, "Skinner, Fred" <fred.skinner@xxxxxxxxxx> said: > I am in the midst of my first Webfacing implementation and have run into > a major roadblock. I hope someone might be able to help me out. I have > Webfaced a Time Sheet entry application and it works fine under my user > profile (which has limit capabilities set to *NO). When I change my user > profile to limited capabilities *YES, I cannot log on the Webfaced > application and my profile is disabled. Most of our applications need to > run under our user's profile as we determine library lists, output > queues, etc based on their profile. I have found a IBM Software > technical document (28392049) that states you cannot run a Webfacing > application with a user profile that is set to limit capabilities *YES. > The work around (Changing the user profile to run initial program > QSYS/QQFINVOKER) is not workable for us. Has anyone else run into this > problem. If you could share how/if you worked around this issue, it will > be appreciated. > > > > Thanks, > > > > Fred Skinner > > > > > > ****************************** > This e-mail message and any attachments to it are intended for the named > recipients and may contain confidential information. If you are not one > of the intended recipients, please do not duplicate or forward this > e-mail message and immediately delete it from your computer. > ****************************** > > _______________________________________________ > 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. > -- michaelr_41@xxxxxxxxxxxxxx -- http://www.fastmail.fm - And now for something completely different... _______________________________________________ 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.
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.