last BACKVOL CDS was at 17:33:09 Saturday. The first ARC0026E message that I can find in either SYSLOG is at 18:00:30 on Saturday, or about 30 minutes later.
On Mon, Apr 15, 2013 at 8:28 AM, Staller, Allan <[email protected]> wrote: > When was the last time you successfully ran a BACKVOL CDS command? > > <snip> > *ARC0026E JOURNALING DISABLED DUE TO EOV ERROR ON 852 ARC0026E (CONT.) > JOURNAL. MIGRATION, BACKUP, FRBACKUP, DUMP, TAPECOPY, ARC0026E (CONT.) > TAPEREPL, RECYCLE, ARECOVER, AUDIT, AND EXPIREBV HELD. > ARC0020I ****************************** > > This has happened before. This time, it appears that in addition to the > above, that every job which issues a request to DFHSM via SVC-109, code x'18' > went into a WAIT (SVC 1) on some ECB which was never POSTed. > > Has anybody seen this message before? How did you eliminate it? I have done > what the book said: stop all DFHSM; rename old JOURNAL; all new JOURNAL data > set;S DFHSM,EMERG=YES on one system; wait for it to come up; S DFHSM on > second system. We have two systems sharing all the DFHSM data sets in a > __basic__ sysplex (not parallel, we won't get a ICF engine). > </snip> > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
