Re: Development ideas

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
There is a plethora of topics to be covered here:

- Languages
- Design
- Change Management
- Tools
- Backup
- Security
- Etc

As you are aware the iSeries supports COBOL, SQL, RPGLE, etc.  It also
supports C and C++.  Granted, it is not true object orientation, but ILE
and service programs get's you going in the right direction.

Joe Pluta had some great points as to what client, or clients, will be
accessing the same programs.

There are several change management packages out there.  Two that pop to
mind are Softlanding's Turnover, and Aldon's CMS.

The new Eclipse development environment should help the disparate teams
work together well.  Move to that, versus the traditional SEU and PDM.
You, showing your ability to change, might show the VB crowd that they
could compromise and change also.
Give these people all the features of iSeries Navigator, (formerly known
as Operations Navigator).  While you may feel more comfortable with a 5250
interface, history has shown that they will adopt more readily to the
Navigator.

You may want to do the bait-and-switch and postpone the suggestion for
mirrored systems until after the project gets going strong.  For a list of
High Availability vendors check out:
http://faq.midrange.com/data/cache/210.html

Since you may be having a mix of clients, at least more than the
traditional 5250 interface, then you might want to consider a different
security plan than menu based security.  Area's to consider:
Excluding users from all data.  Data access must be done via either stored
procedures which adopt authority, or traditional programs which adopt
authority.
Column security.  Either secure users from the physicals and only allow
access via views or logicals which contain their area of concern or break
apart the physicals.
Exit point security.  See  http://faq.midrange.com/data/cache/198.html

Now's the time to 'do it right' and not as how the packaged software
vendors have been doing it for years:
Use referential integrity, do not assume that all data access will be via
'that one maintenance program'.
Set up journalling.
Set up commitment control.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"McBride, Catherine" <CMcbride@kable.com>
Sent by: midrange-l-admin@midrange.com
10/17/2002 09:10 AM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Development ideas


This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
x-gfisavedcharset: iso-8859-1

                 Hello List,
     We have an opportunity to rewrite an entire system using whatever
platform we select.  It's currently mainframe based.  I have been asked
what
development languages and tools there are for the AS400.  We have an 820
and
use RPG and COBOL already.  What this programming group seems to be
looking
for is object-oriented type stuff, though.  We're fairly new to the AS400
world.  Is there GUI-based application development for the AS400?  What
languages?  The programming staff would like to be able to develop and
test
quickly, and have a full complement of programming tools to work with. The
programmers who would be writing this system have VB and SQL server
experience.  If any of you have suggestions for us, we'd be very
appreciative.   Thanks much!
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.