Re: S/36 Environment, CHGS36

["Marc Zylka" <mzylka@xxxxxxxxxxx>]

John and Pat,

Thanks for the info.  I'll set up an initial program for the development
testing IDs which does a FILELIB NAME-QS36FDEV.  Also set up
a separate job description where the library list only contains the
libraries containing the modified code.   The user id(s) would
also be set up with special environment S36.

I'll be using CHGS36 to change the 'use library list' parameter
to 'Y' this weekend or early Monday morning.

Very few jobs are set up to use a job queue, they're mostly
interactive including reports.  When time permitts, we'll be
using job queues.

Thanks, Marc. ( mzylka@netpath.net)

> 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-?!?


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