Re[4]: Runtime KLIST change?

[pcunnane@xxxxxxxxxxxxxx]

> >      Um, because the generated code is crap?
>
> Yes, BUT, just try to retrofit BPCS BMR's to AS/Set RPG that you've modified 
> outside of the tool.

Exactly.  This is an issue we came up against on a number of occasions:  either 
modify the code so that it was more or less useable, and forget about ever using
the CASE tool, or just shrug and tell the user that it can't be done.

> You should have tried Synon and Lansa back when CASE was big.  AS/Set had an 
> absolutely _STELLAR_ learning curve and generated better code compared to the 
> latter at the time.  You'd be surprised at what AS/Set can do if you throw the
> "tutorial" out the window and use it as it _works_, not as it was _intended_ 
> to work.

What unfortunately started to happen was that we began to essentially write RPG 
code within the CASE tool, re-writing most of the generated code.  Eventually it
dawned on us that it was easier to write RPG code in SEU, and we got AS/SET 
thrown out.

____________
Paul Cunnane
The Learning Company
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---