Perhaps you have a default UNICODE image loaded by the OS. I remember there was an APAR introducing such a feature for a lazy sysprog and the default is a huge one and fixed storage.
Roland -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Norgauer Sent: Monday, January 30, 2006 6:57 PM To: [email protected] Subject: IPL anomoly with UNICODE When my production z/OS 1.4 system issues 'D UNI' command issued, we get the following: CUN3000I 10.16.01 UNI DISPLAY 589 ENVIRONMENT: CREATED 01/14/2006 AT 04.49.37 MODIFIED 01/14/2006 AT 04.49.37 IMAGE CREATED 01/14/2006 AT 04.49.37 The date associated for the image created is the date of IPL. When I issued the same command on my test system, we get: CUN3000I 09.27.50 UNI DISPLAY 913 ENVIRONMENT: CREATED 01/30/2006 AT 08.58.23 MODIFIED 01/30/2006 AT 08.58.23 IMAGE CREATED 01/28/2004 AT 11.56.25 We IPL'ed our test system today. Why is the date associated with image created not the same date of IPL as it is in our production platform? ---------------------------------------------------------------------- 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
