John,

Did you ask this question back in 2009?  At least I think it was you.

In Infocenter this link has an answer to your question

http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ib
m.zos.r12.arcf000%2Fcase1.htm

Do you have the journal dumped frequently?  Do you have a small journal?  Or
really large?

Basically what Allen said - BACKVOL CDS.  When do you run this in HSM?  You
should have a daily dump of the CDS datasets and the Journal should be part
of that.  Check to see when your last run of this command occurred and see
if there were any errors.

Lizette


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of John McKown
Sent: Monday, April 15, 2013 6:15 AM
To: [email protected]
Subject: DFHSM message ARC0026E - EOV error on JOURNAL.

I've already entered a service request on IBM link about this, but thought
I'd ask here as well. On Saturday, we got the DFHSM message:

*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).

--
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

Reply via email to