The journal may be a bit small. It's only 25 cylinders. I'll expand it ASAP.

On Mon, Apr 15, 2013 at 8:57 AM, Staller, Allan <[email protected]> wrote:
> You might to review  "DFSMShsm in a multiple-image environment" in the 
> appropriate version of
> DFSMShsm Implementation and Customization Guide.
>
> You have not indicated if you are running primary and secondary dfHSM tasks. 
> The guide specifically suggests this to prevent race conditions
> during selected activities (migration, backup, recall, dump).
>
> If all is as indicated unless some *really really* serious activity 
> (migration, recall, backup) was going on, I would suggest a DASD error or 
> JOURNAL
> dataset too small. Review the size and/or move the JOURNAL dataset to another 
> volume.
>
> BTW, I have been running in the same configuration (multi-HSM, base SYSPLEX) 
> since 2010 with no occurrence of this issue.
>
> Feel free to contact me  off list if necessary...
>
> HTH,
>
> <snip>
> 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

Reply via email to