|
Typically this means that program did not run or ended before putting up the first screen. As indicated earlier check the job logs. One very common cause for this problem is the library list. When you run a WF'd app it uses the libl set up by the user's jobd. If you rely upon the userid's startup program to init the libl then that may be the problem? The startup program does not get run by WF (though you can write a small CL to do this then launch your program). Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx "Chip Milosch" <cmilosch@xxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 2004-05-11 11:14 Please respond to Websphere Development Studio Client for iSeries To <wdsci-l@xxxxxxxxxxxx> cc Subject [WDSCI-L] Webfacing application I have a simple (one screen) appliacation web faced. I start the project and the get my basic index.html page. Clicking on a link brings up the logon screen. Once I logon, I immediately return to my index.html page. The project is setup to invoke a CL command for the index links. This CL command explicitly names both the library and program to run. I get no messages. Where do I look to resolve this problem? Chip Milosch Griffin Computing Cell: 847-309-620; Office: 630-203-2904; Fax: 413-702-7659 _______________________________________________ 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.