On Fri, 11 Jan 2008 22:27:51 +0000, Ted MacNEIL <[EMAIL PROTECTED]> wrote:

>>What would you suggest as a means of making sure that customers use the
proper release of the binder?
>
>I cannot think of anything stronger than documenting it an making customers
read the funny manual.
>
>Of course, I also find it hard to understand why people won't use current
tools.
>

It's not about not wanting to use the tools, it's about applying maintenance 
from a driving system that is at a lower level than the target system.

It should be S.O.P. to use the STEPLIB, but I'm not sure if/where it is 
documented. ServerPac builds JCL with the MIGLIB STEPLIB.

I've always thought about needing the STEPLIB when the SMP/E level
is higher on the target system (and SMP/E is very good about complaining
when it doesn't recognize a new element type if you forget) but I usually
don't think about it for the binder.  Because I installed SMP/E 3.4 under
z/OS 1.6, I ran into a similar glitch when applying a usermod for one of my
JES2 exits when I upgraded to z/OS 1.8.  That JCL now has the STEPLIB
for MIGLIB.  

One thing not in MIGLIB that you may need in your STEPLIB for applying
maintenance / usermods from a lower level system is a STEPLIB  to
hlq.SASMMOD1 (high level assembler) when that changes.  Hence, almost
all of our usermod JCL (which usually get installed from a driving system
at a lower level) has a STEPLIB to both.  I'm pretty sure ServerPac jobs
also include it when needed.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:[EMAIL PROTECTED]
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to