Re: Question about UDB on iSeries -- MIDRANGE-L

I don't know how stable your current applications are (i.e. no new
development), but if your current job is to simply maintain the
database, then no - you won't have much to do.

On the other hand, if you do new development or major enhancements to
the existing system, then your selling point will be the ability to
focus on new development exclusively.  the productivity gains will be
well above what you're used to.  in other words 'heavy techies' are
very much at home on iseries.

As far as application development is concerned, your biggest learning
curve will probably be in the following 2 areas:

DDS a fixed format data definition specification 'language'- required
for presentation I/O - green screens.  (Printer output can be done
this way as well, but not required).    DDS is also the 'native'
method of coding data definition specifications  (tables, views, etc).
  as was stated previously, you can also do data definition via SQL
DDL.  Pick your poison.   But if you're doing green screen
programming, you will need to learn DDS.

CLP - the job control language (compiled) used for stringing commands
and programs together into a single job - a JCL equivalent but does
not resemble it in the least.

hope this helps

Rick

On Tue, 30 Nov 2004 09:38:41 -0600, McKown, John
<john.mckown@xxxxxxxxxxxxxx> wrote:
<snip> 
> 
> This will be a conversion of all of our z/OS applications. When finished, 
> z/OS and zSeries go away. No OEM applications, just some other software such 
> as BRMS, Robot/???, and a couple of others that I cannot remember off-hand. 
> The vendor says that they can convert all of our batch and CICS programs 
> (COBOL, assembler, EasyTrieve, etc) to something, mainly ILE COBOL, which 
> will run natively on the iSeries (not using CICS for iSeries or whatever it's 
> called). We mainly do our own development.
> 
> 
> 
> > The answers to these questions, IMO, are probably your biggest hurdles
> > for moving to the platform.  I've seen some mainframe software that
> > was ported to iseries, and it's not pretty.  there are many things
> > that you HAVE to do in a mainframe environment to access the database
> > (and visual I/O as well) that are very much different and probably
> > easier when done on iseries.   your mileage may vary.
> >
> > One thing is for sure - you've found arguably the best resource
> > (midrange.com) to point you in the right direction for your endeavour,
> > and you'll find that everyone here is more than happy to help you in
> > your decision making.
> >
> > We just love it when other platforms move to ours.  We LOVE the
> > iseries, and most of us believe there's no better platform to be
> > found.
> []
> Here's hoping that, if we convert, we use the iSeries. We have a proposal to 
> go to a **SINGLE**, non-clustered Windows platform as well as to Sun/Solaris. 
> I may be able to keep my job if we go to iSeries. If we go to one of the 
> other two, I'm outta here. Even on the iSeries, there really doesn't seem to 
> be as much of a need for a "heavy techie". Of course, as I recall, that is a 
> big selling point.
> 
> > Good luck,
> >
> > Rick
> 
> 
> >
> 
> > --
> > John McKown
> > Senior Systems Programmer
> > UICI Insurance Center
> > Information Technology
> >
> > This message (including any attachments) contains confidential information 
> > intended for a specific individual and purpose, and its content is 
> > protected by law.  If you are not the intended recipient, you should delete 
> > this message and are hereby notified that any disclosure, copying, or 
> > distribution of this transmission, or taking any action based on it, is 
> > strictly prohibited.
> >
> >
> >
> >
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>