I admire your determination! Keep it up - that's what keeps all of us young at heart!
As far as why you're getting a link edit operation doing things "Pat's way", I suspect the answer has to do with the complex process SMP/E uses to build load modules - a process which has been enhanced over the years. There must be some sort of subtle difference between object modules located in RELFILEs versus object modules located in TXLIBs. Check out Appendix C "Building load modules" in publication SMP/E for z/OS Commands. Also, the way I think about JCLIN is that JCLIN describes a product's *structure*, it does NOT describe a product's installation process. Brian On Thu, 9 Nov 2006 16:30:46 -0600, Patrick O'Keefe wrote: >On Thu, 9 Nov 2006 12:24:22 -0600, Brian Peterson wrote: > >>Talk about doing things the "hard way"....!! Here's some ideas you might >>consider. You probably already thought of them - if so, sorry! >>... > >One person's "hard" is another's "fun". I haven't had a hands-on fight >with SMP for several years and am really enjoying this. (Yup. I'm sick!) >This is the way I learn. > (snip) > >As you can tell from my comments above, I look at this differently. The >fact that I ran into this problem tells me I don't understand SMP (as if >that surprises anybody!). The fact that only 2 modules had problems says >either I had a reasonable grasp on what I was doing or I was VERY lucky. >More of the later than the former, I fear. > >A little more digging, very obvious digging that I should have done right >off the bat, showed me part of what was wrong ... and uncovered a glaring >hole in my understanding of SMP. I looked at the JCLIN (duh!) and saw > > /* > //******************************************************************** > //** STEP 15 ** > //** ** > //** MVS utility IEBCOPY will be used to COPY these two LMODs ** > //** from the installation tape into a Target Library. ** > //** These LMODs don't LINKEDIT well, and need to be copied ** > //** to ensure an overall return code of 00 for SMP/E ** > //** installation processing on this FMID. ** > //** ** > //** TARGLIB - SYS1.NVULIB ** > //** DISTLIB - SYS1.ANVULIB ** > //******************************************************************** > //STEP15 EXEC PGM=IEBCOPY > //SYSPRINT DD SYSOUT=A > //NVULIB DD DSN=SYS1.NVULIB,DISP=SHR > //ANVULIB DD DSN=SYS1.ANVULIB,DISP=SHR > //SYSIN DD * > COPY INDD=ANVULIB,OUTDD=NVULIB > SELECT M=CNMVLC > SELECT M=CNMNVLC > /* > >So why did SMP link it? Obviously it couldn't do the copy in the JCLIN >because there's noting in the DLIB until ACCEPT, but why didn't it copy >from the TXLIB. It obviously found the module in the TXLIB because that's >what it linked. Previous steps in the JCLIN had specified linking into >NVULIB. Does that make SMP always link into that library, regardless >what later JCLIN says? > >Pat O'Keefe ---------------------------------------------------------------------- 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
