Re: On Rpg36

["Scott Klement" <infosys@xxxxxxxxxxxx>]

Hi,

Theres a few different ways...

1) At the top of your OCL proc, put:
   // FILELIB NAME-TESTLIB

   This is the option that I usually use, because otherwise I'll
   forget to set the library, and use the wrong ones, which creates
   all sorts of problems :)

2) At the command line, type:
   FLIB TESTLIB

   I've tried doing this in a proc instead, and it doesn't seem to
   work that way :)

3) You can also do it by doing CHGS36 and adjusting the attributes,
     but I don't use this method, because this will change it for
     everyone on the system, not just your tester...


Keep in mind that on the System 36, you had a "file library" that
files were kept in... it didn't look in a whole list of libraries,
all the files for a given program had to be in the same lib.

Therefore, when I'm testing S/36 stuff, I avoid the use of *LIBL,
and instead put everything in a test library, and go from there.

However, I have to say that the native AS/400 *LIBL approach is
usually a lot easier to deal with :)



"Seenivasan AKK, Gurgaon" <akks@ggn.hcltech.com> wrote:
> Hi,
> I have an application running in an S36 environment.I have modified
>  few
> programs of the legacy application. Now I have to test these program
> The problem i have is that the data file library it only recognises
>  QS36F
> which is my production library with live data i cannot test the
>  modified
> sources with files in the production library.
> How could i probably use a different data file library in an S36
> environment.
+---
| 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
+---