>> yes, every hsm instance sharing the journal dataset must be put in emergency >> > mode (1), and also be stopped (3).
>> Walter Marguccio >Walter, very kind of you. I will go it this weekend before we IPL with the >new time here in the US. We ran into problems. We put HSM in emergency in 3 LPARS (all of them sharing HSM). We ran the BACKVOL command in the main LPAR. Then, we stopped HSM in all 3 LPARS. But, for some reason, in the main LPAR, HSM would restart automatically everytime we stopped it. So I could not drop the existing Journal to switch to a bigger one. The procedure we followed: F DFSMSHSM, SETSYS EMERGENCY (in all 3 LPARS) F DFSMSHSM, BACKVOL CONTROLDATASETS (in main LPAR) F DFSMSHSM, STOP (in al 3 LPARS) But then we noticed that in the main LPAR, DFSMSHSM would just start by itself. I could not switch to a bigger Journal file so we issued the "S DFSMSHSM" command in the remaining 2 LPARS. Why is DFSMSHSM re-starting by itself? We successfully took DFSMSHSM down in the main LPAR earlier that day and it would stay down. Is the emergency request creating a situation where at least one of the LPARs must be running HSM? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
