Please indicate if this is your situation (from your descriptions, this is my guess).
1) Some time ago, you installed Enterprise COBOL 3.4.1 into its own SMP/E environment. 2) Recently, you ordered z/OS 1.9, and Enterprise COBOL was included in the z/OS 1.9 serverpac order. 3) You've now noticed the z/OS 1.9 serverpack included some version of Enterprise COBOL. My observations. a) You are free to continue to use the separately installed Enterprise COBOL. At IPL, just mount it's file system at /usr/lpp/cobol, and use your separately- installed COBOL's target data sets for your application COBOL compiles. For an environment to be valid, the zFS and the target PDS data sets must match (see the recent "Re: SMP/E Error - Resolved" thread for a discussion of the confusion that happens when discipline regarding keeping a 1:1 match for a particular target library and the corresponding zFS is lax). b) Or, you can start to use the Enterprise COBOL which you ordered with your z/OS 1.9 serverpac. Please note - if you ordered z/OS 1.9 after the first of the year, your serverpac COBOL might actually be Enterprise COBOL 4.1, since that was GA on December 14, 2007. c) It is perfectly normal for z/OS serverpac to include an SIGYROOT data set - IF repeat IF you included Enterprise COBOL in the z/OS serverpac order. d) What I do is always include COBOL in the z/OS serverpac, and during the serverpac installation, I choose to merge the vaious product's zFS file systems into the main z/OS root file system data set, just because it is simpler to manage one big data set than several smaller ones. Brian On Thu, 5 Jun 2008 12:03:26 -0500, Chase, John wrote: >> -----Original Message----- >> From: IBM Mainframe Discussion List On Behalf Of Mark Zelden >> >> On Thu, 5 Jun 2008 09:54:23 -0500, Chase, John >> wrote: >> >> >Hi, All, >> > >> >We're doing post-install aceivities for z/OS 1.9, and I >> noticed there >> >is a SIGYROOT filesystem included in our ServerPac. I don't >> find any >> >mention of its release or service level in the Program Directory or >> >Installing Your Order document, but from its name it appears to be >> >COBOL-related. Our installed COBOL (E.C. 3.4.1) provided its own >> >filesystem, which we have mounted. >> > >> >Is the SIGYROOT filesystem supposed to replace the >> COBOL-provided one? >> > >> >> It is from Enterprise COBOL. Did you or did you not order COBOL >> with your serverpac? > >Not explicitly. We ordered a "z/OS 1.9 ServerPac". We already had >EntCob 3.4.1 installed on 1.7. But the x26L340 FMIDs are in the 1.9 >MVST100 and MVSD100 zones, even though they were not explicitly >installed (or re-installed) as part of the 1.9 ServerPac installation >(note: I was not the 1.9 ServerPac installer; I'm just the "mouthpiece" >here on IBM-MAIN). > >> If you did, then it should be mentioned >> in IYO. >> Do you have a mention of COBOL in hlq.CPAC.PGMDIR($INDEXPD)? > >Yes; along with a member that appears to be the "vanilla" ProgDir for >COBOL. No mention of SIGYROOT in there. > > -jc- > ---------------------------------------------------------------------- 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
