ca.portal.admin

daylight savings time

Discussion created by ca.portal.admin on Feb 25, 2010
In the past, we have always IPL'ed when making the switch to or from
daylight savings time. This time, they want try leaving everything up.
I know that there are some steps to take for IDMS when ""falling back"",
but is anything special needed to ""spring forward""? Or can we just
leave the CV's up and continue on our merry way?

Kay Rozeboom
State of Iowa
Information Technology Enterprise
Department of Administrative Services
Telephone: 515.281.6139 Fax: 515.281.6137
Email: Kay.Rozeboom@Iowa.Gov
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"RLEs Increased, then BOOM!"
"We received the RLE messages below just before our CV crashed. The CV =
was humming along happily before this problem and it warmstarted fine =
afterward. Neither task 550832 nor 551906 appear in any of the logs. =
The other tasks listed in the messages look like innocent bystanders. =
Any suggestions on where to begin the hunt for the perp?

--------------------
Our Typical Counts: (we are ""always"" within the safe zone!)=20

INTERNAL: RLEs RCEs DPEs Stack
10534 9248 3956 1235 HWM
16300 14500 4400 2000 Sysgen Threshold
0 0 0 Times Exceeded =20
--------------------
From the Job Log:=20

13.28.29 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 20400.
13.28.33 +IDMS DC010007 V2 T551016 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 24480.
13.28.38 +IDMS DC010007 V2 T551127 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 28560.
13.28.45 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 32640.
13.28.52 +IDMS DC010007 V2 T551409 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 36720.
13.29.03 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 40800.
13.29.14 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN =
INCREASED TO 44880.
13.29.21 +IDMS DC027006 V2 T551906
13.29.59 IEA995I SYMPTOM DUMP OUTPUT 186
186 USER COMPLETION CODE=3D3970
186 TIME=3D13.29.21 SEQ=3D41595 CPU=3D0000 =
ASID=3D0085
186 PSW AT TIME OF ERROR 078D1E00 8000C6A2 ILC 2 IN
186 ACTIVE LOAD MODULE ADDRESS=3D000079A0 =
OFF
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"RLEs Increased, then BOOM!"
"We received the RLE messages below just before our CV crashed. The CV was humming along happily before this problem and it warmstarted fine afterward. Neither task 550832 nor 551906 appear in any of the logs. The other tasks listed in the messages look like innocent bystanders. Any suggestions on where to begin the hunt for the perp?

--------------------
Our Typical Counts: (we are ""always"" within the safe zone!)

INTERNAL: RLEs RCEs DPEs Stack
10534 9248 3956 1235 HWM
16300 14500 4400 2000 Sysgen Threshold
0 0 0 Times Exceeded
--------------------
From the Job Log:

13.28.29 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 20400.
13.28.33 +IDMS DC010007 V2 T551016 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 24480.
13.28.38 +IDMS DC010007 V2 T551127 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 28560.
13.28.45 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 32640.
13.28.52 +IDMS DC010007 V2 T551409 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 36720.
13.29.03 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 40800.
13.29.14 +IDMS DC010007 V2 T550832 THE NUMBER OF RLE'S HAS BEEN INCREASED TO 44880.
13.29.21 +IDMS DC027006 V2 T551906
13.29.59 IEA995I SYMPTOM DUMP OUTPUT 186
186 USER COMPLETION CODE=3970
186 TIME=13.29.21 SEQ=41595 CPU=0000 ASID=0085
186 PSW AT TIME OF ERROR 078D1E00 8000C6A2 ILC 2 IN
186 ACTIVE LOAD MODULE ADDRESS=000079A0 OFF
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
"Re: RLEs Increased, then BOOM!"
"Jerry, if you have the DBA Toolkit Journal Analyzer, you could run a
Chronological Event Report for an interval leading up to the crunch.
This might identify the apps for these tasks.=20

We have found this technique useful from time to time.


Hal Govan
Senior Database Administrator
Reed Elsevier - Technology Services
harold.govan@reedelsevier.com
Phone: (937) 865-7820

Outcomes