Re: RPG/COBOL/C

[R Bruce Hoffman <bruce.hoffman@xxxxxxxxxxxxxxxxx>]

Holden Tommy wrote:
> That would be the direction I would go in.  RPG is being enhanced, etc
> were COBOL is pretty much stagnant.  If I recall correctly the only
> thing that has happened in recent history is that it was made available
> for ILE environment changes. 
>
>   
oh no it isn't. it has pointers, it has bif's, it's string functions are 
no longer a performance nightmare, it's had qualified data structures 
forever... RPG has been playing catchup all these years.


> Thanks,
> Tommy Holden
>
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Ruthirapathi,
> Arulanandham
> Sent: Thursday, May 17, 2007 2:20 PM
> To: RPG programming on the AS400 / iSeries
> Subject: RPG/COBOL/C
>
> Hello all,
>
> Where does COBOL and C stands when compare to RPG.  I see more
> discussions on RPG.  Do you think we need to suggest our clients to
> convert from COBOL to RPG?
>
> - Arul
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of derek gonsalves
> Sent: Tuesday, May 15, 2007 1:25 PM
> To: RPG400-L@xxxxxxxxxxxx
> Subject: Validate Data library name
>
>
> Hi
>
> I have a program wherein the user enters the data library name on the 
> screen, and the company name. Now I first need to validate if the
> library is 
> a valid AS400 library and if yes then i need to validate the company
> number 
> from the company master file present in that data library.
> Any suggestions on how this can be handled??
>
> Thanks in advance
> Derek
>
> _________________________________________________________________
> More photos, more messages, more storage-get 2GB with Windows Live
> Hotmail. 
> http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migr
> ation_HM_mini_2G_0507
> E-mail messages may contain viruses, worms, or other malicious code. By
> reading the message and opening any attachments, the recipient accepts
> full responsibility for taking protective action against such code.
> Henry Schein is not liable for any loss or damage arising from this
> message.
>
> The information in this email is confidential and may be legally
> privileged. It is intended solely for the addressee(s). Access to this
> e-mail by anyone else is unauthorized.
>
>