Finally I have finished wading through the HSM starter set and customized it 
the way we want to use it - just migrating to ML1, no ML2, no backup, no 
recovery, no dumping, no tapes, a really minimal environment. That means I only 
start DFHSM with an MCDS (OFFCAT, BAKCAT, JOURNAL, ARCLOGX, ARCLOGY, ARCPDOX 
and ARCPDOY all set to DUMMY). According to the Implementation&Customization 
Guide, all of the dummied data sets are optional, even if some of them are 
'strongly recommended'.

After starting DFHSM in this really minimal config, I unfortunately get several 
errors:
*ARC0035E DFSMSHSM JOURNAL IS PERMANENTLY DISABLED,
 ARC0035E (CONT.) REASON=4     (DD DUMMY specified)                    
yes, this is intentional. Why is this an error? Journaling is optional 
according to the books.

*ARC0860E JOURNAL SPACE MONITORING DISABLED - RC=24.  094             
 ARC0860E (CONT.) MIGRATION, BACKUP, FRBACKUP, DUMP, AND RECYCLE HELD.
RC24 says "Backup control data set or journal is not being used by DFSMShsm." - 
yes, we don't want to use the backup function! And the book explicitly says 
that neither of the two data sets are *required* if all I want to use are space 
management functions.

Unfortunately this looks like I won't be able to use HSM at all, since 
migration is also held. Am I correct in assuming that the books are wrong and 
even for my minimal needs a BCDS and/or journals are *required*?

 ARC0945I OPEN OF DDNAME=      >0 FAILED, VSAM REASON
 ARC0945I (CONT.) CODE IS X'00'                      
*ARC0134I BACKUP CONTROL DATA SET NOT OPENED, BACKUP 
 ARC0134I (CONT.) WILL NOT BE ENABLED                
 ARC0945I OPEN OF DDNAME= §    >- FAILED, VSAM REASON
 ARC0945I (CONT.) CODE IS X'00'                      
 ARC0133I OFFLINE CONTROL DATA SET NOT OPENED, TAPE  
 ARC0133I (CONT.) SUPPORT WILL NOT BE ACTIVE         

Great. Don't you just love it when a simple DD DUMMY results in these messages? 
(I just love ddnames >0 and §    >-). At least these are only informational 
messages, so I can ignore them.

Then HSM reads my ARCCMDxx member and comes back with 
ARC0103I INVALID SETSYS PARAMETER TAPEMIGRATION 
for this statement: SETSYS TAPEMIGRATION(NONE)
I don't see the problem with this statement, why is it invalid?

I shut down HSM again, and it was started with SETSYS PRIMARYSPMGMTSTART (0000 
0000) to begin with, so hopefully it did not do anything just yet.

I also got this message:
*ARC1901E NUMBER OF VOLUMES ELIGIBLE FOR ON-DEMAND
 ARC1901E (CONT.) MIGRATION HAS REACHED 00004     
which I don't understand. I have exactly 4 volumes that are SMS-managed and I 
don't want HSM to touch any of my non-SMS volumes (no addvols for any other 
volumes defined). The ODMNOTIFICATIONLIMIT is set to 4, so I guess that is why 
I got that message. I still don't understand why I got it at all, though, since 
there was certainly nobody issuing hmigrate commands anywhere on our system. 
Assuming that that is what 'on-demand-migration' means (or did I get that 
wrong, too?)

I guess my main question is: Will I be able to migrate data sets after having 
gotten ARC860E?

Thanks in advance, Barbara

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to