|
FYI Several months ago there was a discussion of problems caused when the system date & time on a RISC processor AS/400 was reset to the default (1928/08/23) after power had been lost to the control panel (usually after a service action). If a manual IPL was done the date/time were cleared and you were forced to enter them. But on a normal IPL the system would come up with the default date/time. With these PTF's (already on cum packages) the system will force a manual IPL if it has reset to the default date/time. (Unfortunately, there does not appear to be a PTF for either V3R6 or V3R7). PTF List: Release 410 : SF42278 available 97/07/22 (7217 ) Release 414 : SF45311 available 97/12/04 (1000 ) APAR Identifier ...... SA66023 Last Changed..97/12/04 IPL-INCORROUT DATE AND TIME ALLOWED TO DEFAULT ON IPL Symptom ...... IN INCORROUT Status ........... CLOSED PER Severity ................... 2 Date Closed ......... 97/07/16 Component .......... 5769SS100 Duplicate of ........ Reported Release ......... 410 Fixed Release ............ 999 Component Name 5769 BASE V4 Special Notice Current Target Date .. Flags SCP ................... Platform ............ Status Detail: SHIPMENT - Packaged solution is available for shipment. PTF List: Release 410 : SF42278 available 97/07/22 (7217 ) Release 414 : SF45311 available 97/12/04 (1000 ) ERROR DESCRIPTION: The Time of Day (TOD) defaults back to the system default instead of being set at the TOD that was being used by the system before the last IPL. This usually happens after a service action such as replacement of an MFIOP, System Control Panel, or any other hardware action that requires the power to TOD clock to be lost. These failures happen on V3R6.0 and V3R7.0 levels of RISC code. PROBLEM SUMMARY: When a customer changes their hardware configuration, such as replacing an IOP like the service processor, the system date gets defaulted. The system should be IPLed in MANUAL mode to set the date, but this is not a requirement. It is possible for the customer to IPL in NORMAL mode, and have a corrupted system date on their machine. When the system date is defaulted, it gets set to August 23, 1928. Some of the problems customers can see are scheduled jobs which fail to run, applications containing an incorrect date field, profiles with expired passwords and expired license keys. If the system date is lost and an IPL occurs, on a MANUAL or attended IPL, the date and time fields are cleared on the IPL options panel and the customer is forced to enter a valid date in order to continue the IPL. This is how it works today. On a NORMAL or unattended IPL, the system will now force the IPL into a MANUAL or attended IPL. This is new. When this occurs, the system will sit at the initial SIGNON screen waiting for the customer to continue the IPL, and then will see all other normal screens associated with a MANUAL or attended IPL. A message will be sent to QHST and QSYSOPR explaining what happened to the IPL and it is MSGCPF095A with the following text: Message . . . . : IPL changed from unattended to attended mode Cause . . . . . : The start operating system function has been changed from unattended to attended because the system date was set to the default. Recovery . . . : Enter a new system date on the IPL options screen. The system date was set to the default. The IPL was changed from unattended to attended to allow a new system date to be entered. On an install, the customer is already required to provide a date and time, and the system date and time are updated. There are no changes required for an install. PROBLEM CONCLUSION: The system will not allow an unattended IPL after the system date has been set to the default. ... Neil Palmer AS/400~~~~~ ... NxTrend Technology - Canada ____________ ___ ~ ... Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||= ... Phone: (905) 731-9000 x238 |__________|_|______|_|______) ... Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\ ... Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... mailto:NPalmer@NxTrend.com http://www.NxTrend.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.