RE: small application -- RPG400-L

From: TomCruise TomCruise [mailto:indian_tomcruise_24@rediffmail.com]

hai

Ours is small team ...i am designing an application for fleet
management services..iam new to AS400 too....

> Welcome to the iSeries

how to start up with configuration of the system and other
terminals to connect to AS400(V3R7)....

> V3R7 is a little old, but should be very serviceable.  You should probably
> upgrade to V5R1 (soon to be V5R2) when you can though.
>
> "other terminals", are these PCs or dumb tubes?  Are the dumb tubes already
> installed, or do you need to install them?  And if you need to install them,
> is the wiring in place, or do you need to run it?

if iam working in group,do i need to create group profile to work
on same application?

> You do not need to, no, but it is a good idea.  It is easiest if you do create
> group profiles, however, then you really only have one profile you have to
> maintain security for, the other users you make part of this group.  I would
> suggest going that route, but you can also give specific users their own 
>rights
> also.  So just because someone wasn't in the group doesn't mean they couldn't
> run the application.

what r the other things i have to take care when working in
group??

> The main thing is security.  The best method is to give no access to anyone
> for anything, then start giving them access to the things they need to do.
> This is much better, IMO, than the practice of giving all users access to
> everything then trying to take away rights.

....how can i club various modules allotted to 3 members of the
team?...

> club? What do you mean club?  You mean like tie together?  The most common
> way would be to have those 3 programs on a menu.  And then give that group
> access to the menu and the programs.  Or were you meaning something else by
> module?

i ve analysed the project....Can anyone specify me correctly how
to proceed first...

> Are you going to be coding this yourself?  The first step is usually to start
> designing the database with thought as to what type of data you are going to
> need to keep.  Fleet management, is this for trucks or for 
>container/trailer/chassis?
> Or both?  If it's for trucks, then you would need a file for the trucks, a 
>file
> for the drivers on the minimum.  How far back do you want to store data?  
>Perhaps
> you'll need a transaction file.  How are the drivers going to be paid?  Need 
>some
> type of payroll file, or time punch file, or trip file depending on how you 
>pay.

> After you get a good part of the file design working, now you need to be able 
>to
> enter the truck information.  Design screen and program for that, with 
>add/change/
> delete, etc...  That is normally the way I go about application design.

> I would also start right off the bat about thinking about separate test and 
>production
> environments.  A lot easier to implement in the beginning than as an after 
>though.
> So you would have a library (or more) for production source and code, and one 
>for test
> source and code.  And a library for production data files and one for test 
>data files.
> With a CL program (which is like a DOS Batch program or a Linux script 
>program) you
> can manipulate your library list (similar to DOS/Linux PATHs) to use either 
>test or
> production.

> Display files are physical files created from source file members.  The common
> practice is to store display file members in a file called QDDSSRC.  V3R7, I 
>think
> you will need to use the Green Screen design tools.  The way I started, and 
>do most
> of my browsing, is to STRPDM (Start Program Development Manager).  Select 1, 
>work
> with libraries.  *ALL and you can browse through the libraries on your 
>system.  Either
> F6 to create a new library, or CRTLIB command (Create Library).  F5 to 
>refresh the list.
> Put a 12 to work with that library.  In that library create a source file 
>(CRTSRCPF or
> F6 and browse through create file commands).  QDDSSRC as file name.  Library 
>as the library
> you just created.  Record length defaults at 92, but that is usually too 
>short for me,
> I prefer 113 or longer.  Press enter.  Now F5 and 12 on that file
> F6 to create a new file.  Give it a name.  Type is PF for Physical File, LF 
>for Logical
> file, DSPF for display file.  Remember, these are SOURCE code files, not the 
>actually
> files.

> This is just the tip of the iceberg.  For your green screen application you 
>will need:
> 1. User accounts for logins
> 2. Group accounts if desired.
> 3. Physical Files to hold the data
> 4. Logical Files to hold views into the data
> 5. Menus
> 6. RPG and CL programs
> 7. Printers

> And this doesn't even begin to get into communications.  Do you need to 
>converse with
> other companies computers?  Over dial up?  Over TCP/IP?  Over the internet?

> I'm not sure how much you know about the iSeries, so went into a little more 
>detail
> than I normally would, and breezed over a few things I would normally go into 
>more
> detail on.  Feel free to ask anything you want.

Regards,

Jim Langston