|
Hi Fred, The symptoms you describe (immediate return after log-on) indicate that the program didn't or couldn't run for some reason (yeah, I know, profound). The common reasons are that the library list is not set up right, the invocation command is not correct, the user doesn't have authority, etc. So from what you have already done it seems like the libl is OK? However, knowing the myriad of errors that I've made I would go back and check that the library is the right one, not just for the program but for any PF or DSPF resources the program needs to run (I generally launch WF'd apps with a CL that sets up the libl and stuff so it doesn't need to be in the JOBD). Also check that there are no typos in the invocation command. If you don't have it on you might try turning on job logging as often the joblog for the failing invocation is useful in tracking down the cause of the failure. Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory "Fred Horvat" <horvat@xxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 2006-04-12 11:19 Please respond to Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx> To "'Websphere Development Studio Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc Subject Re: [WDSCI-L] Error Logging WebFacing The user being me has command line access. -----Original Message----- From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Carey Caile Sent: Tuesday, April 11, 2006 3:25 PM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] Error Logging WebFacing If the user doesn't have command line access, then you must use the Webfacing start job qqfinvoker as the intial program for the user profile. If they have command line access, then that is not necessary. That has burned us a couple of times. See if that helps. Carey "Fred Horvat" <horvat@xxxxxxxx> Sent by: To wdsci-l-bounces@m "'Websphere Development Studio idrange.com Client for iSeries'" <wdsci-l@xxxxxxxxxxxx> cc 04/11/2006 02:11 PM Subject [WDSCI-L] Error Logging WebFacing Please respond to Websphere Development Studio Client for iSeries <wdsci-l@midrange .com> I'm new to WDS and WebFacing. I am running WebSphere 5.1.2.6. I Webfaced an existing program on the iSeries. When I go to run it on my PC I get the User ID and Login prompt and then it just returns back to the initial Launch Application Screen. I have my user job description setup properly with the library list in order. I can log into a 5250 session and call the program and it runs fine. In the WebSphere Console no error messages show up. I get what appears to be normal runtime messages. The last four lines that are written to the log that get written when I click LAUNCH. [4/11/06 13:57:50:125 EDT] 653f7151 PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='org.apache.struts.taglib.html.LocalStrings', returnNull=true [4/11/06 13:57:50:125 EDT] 653f7151 PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='org.apache.struts.taglib.html.LocalStrings', returnNull=true [4/11/06 13:57:50:141 EDT] 653f7151 PropertyMessa I org.apache.struts.util.PropertyMessageResources Initializing, config='org.apache.struts.taglib.html.LocalStrings', returnNull=true [4/11/06 13:57:57:000 EDT] 64b7f151 WebGroup I SRVE0180I: [Test_DALY] [/Test_DALY] [Servlet.LOG]: /webfacing/jsp/common/html/last.jsp: init Any ideas on where to look on what the problem may be? Fred Horvat horvat@xxxxxxxx 216-426-5692 -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.