Exactly. It is (IMO) good practice to regenerate your IPLTEXT not just after the install of a new release but after the application of maintenance just in case.
David Elliot zSeries Software Support -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Starr, Alan Sent: Tuesday, September 28, 2010 12:46 PM To: [email protected] Subject: Re: IPLTEXT and NUCLEUS dates Hey Ayre, That's really neat! I'd never known that. It appears that there is a built-in association (in the CPAC that IBM delivers) between SYS1.NUCLEUS(IEAIPL01), which is the first IPL RIM module, and SYS1.SAMPLIB(IEAIPL00), which is the object code that ICKDSF loads into HDR1 of a sysres. Both the LMOD (IEAIPL01) and the object text (IEAIPL00) contain an FMID and a "compile" date. This information is carried over into the IPL Vector Table (see macro IHAIVT in SYS1.MODGEN). If they do not match, IPL fails. I believe that this is a safeguard to ensure that you re-initialize the IPL/Bootstrap on the sysres every time you upgrade to a new z/OS release. It appears that IEAIPL00 (on the sysres) builds the IVT and loads IEAIPL01 from SYS1.NUCLEUS into a 96-byte area of the IVT that is mapped by IHAIVT. If IEAIPL01's format has changed since IEAIPL00 was last copied to the sysres, unpredictable results could occur. Thanks for asking. That was fun! Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Elliot, David Sent: Tuesday, September 28, 2010 10:23 To: [email protected] Subject: Re: IPLTEXT and NUCLEUS dates How did you find this out? David Elliot zSeries Software Support -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Arye Shemer Sent: Tuesday, September 28, 2010 12:17 PM To: [email protected] Subject: IPLTEXT and NUCLEUS dates Hello Forumers, recently I found out that IPLTEXT and the NUCLEUS (not sure which module) must have the same date. If I remember correctly you get WAIT075 if the dates are not of the same day. Has anyone know the logic beyond this dependency ? What it is suppose to protect us from ? I could not find a reasonable explanation for this. Thanks, Arye. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
