Re: iSeries 25% Growth 3rd Quarter

On 10/19/05, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote:
> This is what he was saying, Steve.  If you were to write this for a PC
> would you write the whole thing in a .BAT file or would you use a HLL or
> some combination thereof?
>

I can agree with that.   my only disagreement is that .BAT files are
so 1990s at best.  As others in this thread have said, any language
that handles exceptions can be used as a control language.  I think
you can argue that nowadays, a control language is one that sacrifices
execution speed for audit trails, other means of problem determination
and compatibility with all the other languages on the platform.  
Using this definition, you can build all the HLL features into CL  -
only you would not use it for all purposes because all the built in
auditing and interfacing with any and all code modules would cause it
to run relatively slow.

-Steve




> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> Steve Richter <stephenrichter@xxxxxxxxx>
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 10/19/2005 07:21 AM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
>
>
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
>
> Fax to
>
> Subject
> Re: iSeries 25% Growth 3rd Quarter
>
>
>
>
>
>
> On 10/19/05, michael@xxxxxxxxxxxxxxxxxx <michael@xxxxxxxxxxxxxxxxxx>
> wrote:
> > Do you do PC development using command files?
> >Or do you use a higher
> > level language when it comes to accessing a database and performing
> > business logic? You can twist command languages a great deal, and I've
> > done it with CL and PC commands and Unix shell scripts, but there's a
> > place for a programming language vice a control language.
>
> I dont know what that means.  I started a CLLE program yesterday.  It
> receives files from vendors FTP sites.  First it has to examine the
> FTP site for the actual name of the file to get.  That is a separate
> CLLE program. That program does things like crack the extension off
> the end of the file name.   Should that code not be in the CLLE
> program?  Then my main CLLE program chains to some files to calc where
> to store the file once I get it.  Is that sort of thing not approriate
> for a CLLE program?  The next step is to CPYFRMIMPF to get the data
> from the FTP text file into a database file.  Then it calls an SQL
> procedure to process the data.  The code modules are already in place
> to do all of this.  I just cant get to them easily from CLLE.
>
> The focus of CL should be on calling other modules, catching and
> handling exceptions and tracing execution in the joblog.  Because of
> the lack of support for SQL, Java and ILE procedures, CL does not do
> this job very well.
>
> -Steve
>
> >
> >
> > > -------- Original Message --------
> > > Subject: Re: iSeries 25% Growth 3rd Quarter
> > > From: Steve Richter <stephenrichter@xxxxxxxxx>
> > > Date: Wed, October 19, 2005 7:35 am
> > > To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > >
> > > On 10/19/05, Larry Bolhuis <lbolhuis@xxxxxxxxxx> wrote:
> > > > Steve,
> > > >
> > > > CL received a HUGE bunch of updates in V5R3 and more are coming.
> V5R3
> > > > introduced (to CL) the DO loop the FOR Loop,
> > >
> > > thanks for the reminder.  I will check into that!
> > >
> > > > multiple files in a single
> > > > CL,
> > >
> > > I cant chain to a file in CL.  yesterday, I had to write a command and
> > > rpg to write a "rtv" type command so my CL program could get the info
> > > it needed. Took about an hour of my time.
> > >
> > > better for IBM to improve the way CLLE calls ILE procedures.  That
> > > way, I could call the recio.h procedures directly from CL.  This would
> > > enable CL to work with display files, database files, ...
> > >
> > > > new data types
> > >
> > > varying and data struct data types are needed.
> > >
> > > >and more. Upcoming releases will introduce
> > > > subroutines among other things.  Sorry but you can't call that
> 'Serious
> > > > Neglect'.
> > >
> > > subroutines are a great idea.   I just disagree with the IBM timeframe
> > > and lack of urgency.  It is taking me twice as long to program things
> > > on the 400 as it would if I had better language support. My current
> > > job is not very secure because of this.
> > >
> > > I am trying to be helpful and what do I get in return - attacked by
> > > the boosters!  oh the burden :)   CL commands need to be improved so
> > > the programmer can call SQL and ILE procedures.  The 10 character
> > > system name limit has to be removed.  CLLE modules should be able to
> > > contain multiple procedures, just like RPG.   A = B + C ; is much more
> > > readable than CHGVAR VAR(A) VALUE(B + C)
> > >
> > > -Steve
> > >
> > > --
> > > 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.
> >
> > --
> > 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.
> >
> >
>
> --
> 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.
>
>
> --
> 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.
>
>