RE: Scoop on v5r3 CL enhancements

Hear, hear!!  ESPECIALLY this part, which is one-a the reasons I went
LOOKING for a job on a 38 what?.. 22 years ago:

"To me, CL has always been one of OS/400's strengths -- an integrated
command language accessing a *rich*, **logical**, *****consistent*****
operating system command set."  (Emphasis added...;-)  It is these (plus
decent Help-text) which make CL intuitive.  It didn't just happen outta some
blind luck.  And, again, just ONE-a the reasons I Really Wanted to find work
on a 400, but not the only one.  (Univac-mini job opportunities being scarce
was another, but there were several others.)


| -----Original Message-----
| [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jim Damato

| To me, CL has always been one of OS/400's strengths -- an
| integrated command
| language accessing a rich, logical, consistent operating system
| command set.
| CL is often the right tool for the job.  I do, however, agree that some
| folks abuse CL instead of writing a decent high-level program.  RPG is a
| high (OK, medium-high) level language once designed around operation of an
| ISAM database.  Even with its many functional and structural enhancements
| writing an RPG program to manipulate the OS can look as nasty as trying to
| create complex data structures in CL.
|
| API's are a mixed bag, for me.  Some OS interfaces need the depth
| of an API.
| Still I'm surprised when an API is produced for something that should have
| been built into a nice RTVxxxxxx command (particularly if I can't wait for
| the next release of TAATOOLS).  OS/400 traditionally provided a simple
| interface allowing developers and sys admins to work with the
| system through
| intuitive commands with built in documentation rather than researching
| API's.
|
| I think that much API programming is better suited to environments without
| an integrated command language accessing a rich, logical, consistent
| operating system command set
|
| -Jim