Re: S/36 Environment, CHGS36

[John Cirocco <jcirocco@xxxxxxxxxx>]

Neil and Marc,

>>Thanks Neil.  I guess the only way to handle the  testing of a
>>separate set of libraries is to change all BLDFILES to
>>CRTPF and use a data area to determine which library to
>>build the files in.  For GSORTS, maybe I'll write a routine to check
>>if we're testing new code and use the // FILELIB statement
>>appropriately.
>>
>>Marc
>>
>>
>>>>I believe the S/36EE will still use QS36F to create new files, in
>>>>addition to using the library list to find existing files, unless you
>>>>use the FLIB command or // FILELIB OCL statement to change your current
>>>>'S/36EE File' library (or unless you named a different library for
>>>>S/36EE in CHGS36).

You do have another option.  Try the CHGS36A (Change S/36 Environment
Attributes).
Allows you to point to another library besides QS36F along with a host of
other handy little S/36 options.

HTH,
John W. Cirocco
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---