× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: "extract" command enhancement(subfiles and BIFs)
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 22 Sep 1999 14:07:49 -0400

Scott,

>Maybe I'm weird (okay, we're back to that again) but 
>subfiles don't take me long to write.   Even the people 
>that I train who have no prior exposure to the AS/400 
>seem to be able to pick up subfiles and write them 
>in less than the 2 days that someone else mentioned 
>on the list.  And we don't use templates (tho 
>programmers are welcome to make their own 
>templates, if they wish)

I find subfiles easy enough, but there's little question that trainees have
problems with the various combinations of PUTOVR, SLFCLR, SLFDSP, SLFDSPCTL,
SLFERRMSG and so on.  The big problem (it seems to me) is that the trainees
copy code fragments (especially DDS fragments) without understanding the
relationships between all the keywords.  When something goes wrong, they
can't readily debug, and have to resort to trial and error.

Buck Calabro
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.