I'm not sure what Gil means by 'exportable'. There was a period some years
ago when our mgmt couldn't decide whether to spring for the latest release
of Netview, which they considered very expensive. On the other hand, we had
no other product in house to do the job, so for a few releases we used
BUILDMCS to roll our old Netview from one z/OS (or OS/390) level to the
next. We were licensed to run the old Netview but could no longer order it
in ServerPac. This process actually worked amazingly well until we decided
to go whole hog on the new release. A couple of gotchas:
1. You must ACCEPT *all* product related maintenance in the old CSI before
running BUILDMCS. If not, you get error messages that (at least then) were
not at all clear.
2. Be careful with a tricky product like Netview that puts components into
NUCLEUS. At one new MVS release, NUCLEUS structure changed such that the
JCLIN for the old Netview broke it. Ouch! We got around the problem by
editing out the NUCLEUS portion of the old JCLIN. I wouldn't think that
many products have hooks in NUCLEUS.
In any case, I consider transporting a BUILDMCS from an old CSI to a new
CSI an example of 'exportability'. All this happened to take place on the
same image, but as long as all files are 'moved', there should not be an
'export' problem.
.
.
JO.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
Paul Gilmartin
<paulgboul...@aim
.COM> To
Sent by: IBM IBM-MAIN@bama.ua.edu
Mainframe cc
Discussion List
<ibm-m...@bama.ua Subject
.edu> Re: How to APPLY FMID's again
02/05/2009 06:20
AM
Please respond to
IBM Mainframe
Discussion List
<ibm-m...@bama.ua
.edu>
On Thu, 5 Feb 2009 07:03:13 -0600, Chase, John wrote:
>> >
>> Will BUILDMCS unwind the DLIBs into SMPMCS? I didn't know
>> that. RELFILE/LKLIB format, I'd guess?
>
>I've only done it once, when I "copied" the XML Toolkit from the z/OS
>1.7 to the 1.9 CSI. It appears to just copy from the existing DLIBs. I
>still have the SMPPUNCH output; I'll send you a "sanitized" copy
>off-list if you like (187 lines).
>
Ah, no need: I RTFM:
4.8.3 "SMP/E V3R5.0 for z/OS V1R10.0 Commands"
__________________________________________________________________________________
4.8.3 Determine elements for all associated SYSMODs
...
SMP/E creates a FROMDS operand on the element MCS to specify the data
set name
associated with the element's DISTLIB value. SMP/E extracts the data set
name from the
DDDEF entry for the DISTLIB ddname. If a DDDEF entry is not found in the
set-to zone
for the DISTLIB ddname, then only the ddname is specified on the FROMDS
operand.
... so the built MCS contains references to the local DLIBs. As
such, it seems tied to the originating site; not exportable to other
site; and subject to peculiar corruption if subsequent maintenance
is ACCEPTed in the originating CSI.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
