|
Jerry, Use the power scheduler. I have used it in the past and it worked reasonably well. YOu just have to remember to review it in the event special requirements come up and you do not want to IPL. > so, my question is: Which to use? > > system value or power off/on scheduleror both? > > jerry > > Quoting Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>: > > > > > > > > > > > > > The power scheduler sets QIPLDATTIM, however the PWRDWNSYS command is > > ignorant of the existence of this command. > > > > To make sure that the power scheduler is in synch with QIPLDATTIM, you need > > to execute the command CHGPWRSCDE *TODAY, and everything will be in synch. > > > > >From my perspective, the fact that PWRDWNSYS does not talk to the power > > scheduler is a bug, but IBM tells me that this is "working as designed". I > > suspect that the proper term is "working as coded". > > > > Al > > > > Al Barsa, Jr. > > Barsa Consulting Group, LLC > > > > 400>390 > > > > 914-251-1234 > > 914-251-9406 fax > > > > http://www.barsaconsulting.com > > http://www.taatool.com > > > > > > > > > > Jerry > > <jdraper@trilosof > > t.com> To > > Sent by: midrange-l@xxxxxxxxxxxx > > midrange-l-bounce cc > > s@xxxxxxxxxxxx > > Subject > > QIPLDATTIM and power off/on > > 11/14/2003 04:41 schedule > > PM > > > > > > Please respond to > > Midrange Systems > > Technical > > Discussion > > <midrange-l@midra > > nge.com> > > > > > > > > > > > > > > What is the relationship between the system value to IPL the system at a > > given > > date and time and the power off/on schedule? > > > > Our power off/on schedule is set to power off at 2am and power on at 2:45am > > Sunday. > > > > Our system value is set to ipl the system at 2:45 on Sunday. > > > > Are both needed? > > > > System value . . . . . : QIPLDATTIM > > Description . . . . . : Date and time to automatically IPL > > IPL date . . . . . . . : 11/16/03 *NONE, MM/DD/YY > > IPL time . . . . . . . : 02:45:00 HH:MM:SS > > > > Power Power > > Date Day On Off Description > > 11/16/03 Sun 02:45:00 02:00:00 > > > > > > Jerry > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
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.
midrange.com
