× 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.



Marc Zylka wrote:
> 
> 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:
 That's not necessary, why not do somthing like this.....

1. At sign on, run a program that prompts for library that you want
to use for files....
2. All the program does then is issue a FILELIB NAME-?1? which is good
   until they sign off or another program issues a FLIB or FILELIB
   statement.....
3. In the S36EE the default is QS36F "unless" it is told otherwise....
4. You can have PROCS & programs in one library & data files in another
   with "NO" problem.......
5. If you want a seperate library for data,,programs,data files, again,
   NO problem as long as you set the environment up correct at SIGN ON
TIME...
6. "IF" you wish to use more than one JOBQ it gets a little tougher, but
   again, you can use native SBMJOB mixed with OCL, again setting the 
   environment at the sign on...... here you would need to pass a parm
   to a proc to issue the FILELIB NAME-?!? but you have to do the
command
   "before" the OCL ever gets processed....somthing like this

           strs36prc prc(setlib) curlib(mylib) parm('?1?')

while SETLIB looks like this

// FILELIB NAME-?!?

Although the S36EE gets a lot of bad press, you can make it work
very well with a little planning..... and it runs pretty well...
the slick part being a mixed environment of S/36 AND 400 at the same
time.....
+---
| 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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.