ca.portal.admin

DC205011 No Journals are AVAILABLE

Discussion created by ca.portal.admin on May 25, 2005
Has anyone come up with an automated or exit solution for those times in
which a run unit fills up the journals which requires a manual cancel run
unit to resolve?

Limits is active, however they are set high for legitimate run units.

SYSLOG Example.....

+IDMS DC205013 All Disk Journals are UNAVAILABLE; Reasons below.
+IDMS DC205004 Disk Journal is OFFLOADING/CONDENSING. Waiting for J1JRNL
+IDMS DC205014 ARCHIVE JOURNAL NOT yet RUN against full Journal J2JRNL
+IDMS DC205014 ARCHIVE JOURNAL NOT yet RUN against full Journal J3JRNL
+IDMS DC205011 NO Journals are AVAILABLE.   IDMS Waiting

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DC205011 No Journals are AVAILABLE
"I don't know of any exit solution, either. However, it defies my
imagination as to how any legitimate run unit could span 3 journals. It
seems to me that more discipline should be applied to your application
programmers and limits should me lowered to reasonable levels. As
Dennis Miller would say, that's just my opinion, I could be wrong.

Dan Miley
Lockheed Martin

Outcomes