Re: On Rpg36

Jim,

>FLIB seems like it would work.

Yes, it will.  But a caveat for you:  FLIB works just like SLIB; it
has both a SESSION-YES and NO variety in the underlying OCL statement.

The FLIB *procedure* always uses SESSION-YES, just like the SLIB
*procedure* does.  The OCL *statement* FILELIB can specify either.

The session YES variety does *not* modify the file library in effect
during the current or nested procedures.  It *does* modify the library
in effect when you get back to the menu, and therefore subsequent job
steps.

Conversely, the session NO variety affects the current and nested
procedures, but goes away when the current proc ends.

The net effect is that if you embed a FLIB procedure call in a
procedure hoping to change the test environment, and the same
procedure creates some files, they are still created in the old file
library because the FLIB procedure has not taken effect yet.  (But if
you rerun it, it will seem to on the second time. <g>)

FLIB run from the command prompt will have the anticipated effect;
when run from a procedure you need to understand the above.  In a
procedure, you will want to use // FILELIB instead of just FLIB so
that you can specify SESSION-NO.  And you may also want SESSION-YES if
you want it to continue to be the file library when the procedure
ends.

You will probably also want to make sure you have library list support
enabled, so that the test FILELIB only needs files you will be
updating.  If you do not have this enabled via CHGS36, you can do it
at a job level basis with the FILELIB ocl statement:

// FILELIB NAME-testlib,SESSION-NO,LIBL-YES

Doug
+---
| 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
+---