Re: Display File for SQLRPGLE program.

It does make sense. I will try and implement this approach too. I appreciate
all the input, thanks again.

Jake.

On 4/5/06, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
>
> Actually you do not need a CL program.  You could easily do it with a
> display file in the program.  Or you could write a CMD object to run the
> program.  For example these few lines of code would generate a screen that
> would prompt a person for the screen and then pass that as a parameter to
> the RPG program
> CMD        PROMPT('Prompt for warehouse')
> PARM       KWD(WAREHOUSE) TYPE(*CHAR) LEN(2) RSTD(*YES) +
>              VALUES('01' '02') MIN(1) PROMPT(WAREHOUSE)
> Then you could do a CRTCMD against those lines of code.
>
> More detailed steps:
> CRTSRCPF mylib/QCMDSRC     (if not already there)
> WRKMBRPDM mylib/QCMDSRC
> F6 to create  I suggest one of two things:  1 - name the command the same
> as the program (if the user doesn't have to remember the name because it's
> called from a menu or CL program), 2 - Give it a name that the users
> groove on.
> Add those above lines.
> Compile it.
> Then, instead of calling your RPGLE program with the CALL command you type
> in the name of this new command, WITH NO CALL! and you now have a prompt
> screen with edit checking.
> Rather crude for adding new warehouses, granted.  At that point you can
> either continue to use a command and add a "Prompt Override Program" or
> configure a display file in your RPG program and do it there.  You may
> decide to break up your RPG program into two programs.  One will do the
> prompting.  The second one will be as you already have written.  The
> benefit of that is that if you want to run it in batch you can bypass the
> first program that does the prompting.
>
> Most people aren't used to using a CMD object to front end a RPG program
> directly.  Most people use them to run a CL program first.  And, there are
> some that never call a RPG program without wrapping it in a CL program. In
> fact, I've worked with CASE tools that insist on this.  However, I say,
> that if you are going to call a rpg program anyway, just call it without
> the CL.  RPG can execute commands just as easily.  It can also do many of
> the overrides using F spec keywords that many people often did in CL.
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> "Jake M" <jakeroc@xxxxxxxxx>
> Sent by: rpg400-l-bounces@xxxxxxxxxxxx
> 04/04/2006 04:33 PM
> Please respond to
> RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>
>
>
> To
> "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
> cc
>
> Subject
> Re: Display File for SQLRPGLE program.
>
>
>
>
>
>
> Michael and Pete,
> Thanks a lot for the suggestions and I agree with Michael my programming
> style is really crude because I am just trying to get the code to work for
> now...:-) but I will definitely take your suggestions into consideration
> as
> a matter of fact I already modified my code. Pete, I never coded a display
> file before and you are right I have to get comfortable with that concept.
> Too bad that it is not as easy as a .jsp front end!! So, a CL program is a
> must to go with it? or is it just a good thing to have? Thanks for all the
> help coming my way
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>
> --
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
> To post a message email: RPG400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
> or email: RPG400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.
>
>