Re: Library list in CGIDEV2

[ewart.desouza@xxxxxxxxxxx]

Hi Guys,

I continuation with my quest to have the user branch to the respective 
application after selecting the database. My next problem is how do I 
branch out ???

I have the division & the application as in the link below:
http://...:1097/spmwebp/spmstart.pgm?div=F&appl=outstg

My question now is do I need to make the branching out in the HTML 
file(using Java ?) or can it be done through the RPG program eg:

wdiv  = zhbgetvarupper('div'); 
wappl = zhbgetvarupper('appl'); 
 
   select; 
   when wdiv = 'F'; 
     wcmd='CHGLIBL LIBL(QTEMP QGPL SOPDTAF SPMLOCF SPMDTAF)' +
          '        CURLIB(SPMDTAF)'; 
     callp(e)  qcmdexc(wcmd:%len(%trim(wcmd))); 
     >>>>>>> here is where I want to branch to the respective application 
calling another RPG program, can it be done?  if so, how ??

   other; 
   endsl; 

My apologies if this is a stupid newbie question.

Thanks & best regards
Ewart



Scott Klement

From:
Scott Klement <web400@xxxxxxxxxxxxxxxx>


To:
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


Cc:



Date:
04/21/2011 11:05 PM


Subject:
Re: [WEB400] Library list in CGIDEV2



hello Ewart,

> I've done this using the usropn function in RPG but I plan to use SQL. 
So
> I feel it would be easier to use the CHGLIBL command to set the library
> list before using any SQL command. The problem is how ??

To use the CHGLIBL command, just do:

   CHGLIBL LIBL(LIB1 LIB2 LIB3 .. etc)

Is that really what you're asking?  Or are you asking us where to store 
the library lists for each database environment?  Or...?


> After the login screen I plan to have another screen where the various
> product areas are listed (using Radio buttons)&  the various 
applications
> are listed (in the form of links / Radio buttons, which is better ??). 
The
> user will then have to select any one product area&  an application to
> proceed. Is this a good way of doing it ??

I would use radio buttons if you want the "product area" and 
"application" to be submitted together. A link would be more appropriate 
if you want to go to the application without submitting anything else on 
the page long with it.

(At least... that's what a user would expect.)

It seems like an okay method to me -- but it's really hard to say 
whether it's a good design without being familiar with the application. 
  What's important here is that it's easy for the user to understand, 
use, and not cumbersome to repeat (if repetition is necessary.)