Re: DFHSM PROBLEM - RECALL
with the ab/sd37, i would assume that recall, and probably more, are in hsm hold. have you tried releasing recall, migrate, etc OR querying (tought reading but ) ? Jack Kelly LA Systems @ US Courts x 202-502-2390 John Dawes <[EMAIL PROTECTED]> Sent by: IBM Mainframe Discussion List 11/14/2006 09:12 PM Please respond to IBM Mainframe Discussion List To IBM-MAIN@BAMA.UA.EDU cc Subject DFHSM PROBLEM - RECALL Hallo, I issued a hrecall for two migrated datasets (ML1) & (ML2) and nothing is happening. I did the necessary health checks - hsend q req, hsend q act, hsend q setsys - and noticed nothing. I checked the started task and no error messages were displayed. I even ran a backvol cds (I had noticed that there was an d37-04 for the journal file.) After the backups for the MCDS, OCD, BCDS & JOURNAL) were down, I shut down the STC and brought it up. Still no action by DFHSM. I even issued hsend release recall but nothing happening. Is there something else I should do? Thanks Send instant messages to your online friends http://au.messenger.yahoo.com -- 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 -- 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
Re: DFHSM PROBLEM - RECALL
Did HSM abend or get cancelled while using the SDSP the ML1 data set is in and/or the tape the ML2 data set is on? If so, the "in-use" bit may be on for these resources. To check the system identifier for the tape TTOC record -- FIXCDS T L2-123456- DISPLAY(X'00') LENGTH(4) To turn off the system identifier for a TTOC record -- FIXCDS T L2-123456-000 VERIFY(X'00' X'F4') PATCH(X'00' X'00') where X'F4' is the HSM hostid To check the "volume in-use flag" for the ML2 volume -- FIXCDS V 123456 DISPLAY(X'09') LENGTH(4) FIXCDS V 123456 DISPLAY(X'58') LENGTH(4) To turn off the "volume in-use flag" for an ML2 volume if it is turned on -- FIXCDS V 123456 PATCH(X'09' BITS(...0) FIXCDS V 900123 VERIFY(X'58' X'F4') PATCH (X'58' X'00') where X'F4" is the HSM hostid To check the "SDSP in-use flag for an ML1 volume -- FISCDS V ML1008 DISPLAY(X'59) LENGTH(4) To turn off the "SDSP in-use flags" FIXCDS V ML1008 VERIFY(X'59' BITS(10..) PATCH(X'59' BITS(00..)) FIXCDS V ML1008 VERIFY(X'59' BITS(01..) PATCH(X'59' BITS(00..)) -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of John Dawes Sent: Tuesday, November 14, 2006 8:13 PM To: IBM-MAIN@BAMA.UA.EDU Subject: DFHSM PROBLEM - RECALL Hallo, I issued a hrecall for two migrated datasets (ML1) & (ML2) and nothing is happening. I did the necessary health checks - hsend q req, hsend q act, hsend q setsys - and noticed nothing. I checked the started task and no error messages were displayed. I even ran a backvol cds (I had noticed that there was an d37-04 for the journal file.) After the backups for the MCDS, OCD, BCDS & JOURNAL) were down, I shut down the STC and brought it up. Still no action by DFHSM. I even issued hsend release recall but nothing happening. Is there something else I should do? Thanks -- 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
Re: DFHSM PROBLEM - RECALL
Hsend release recall? I issued a hrecall for two migrated datasets (ML1) & (ML2) and nothing is happening. I did the necessary health checks - hsend q req, hsend q act, hsend q setsys - and noticed nothing. I checked the started task and no error messages were displayed. I even ran a backvol cds (I had noticed that there was an d37-04 for the journal file.) After the backups for the MCDS, OCD, BCDS & JOURNAL) were down, I shut down the STC and brought it up. Still no action by DFHSM. I even issued hsend release recall but nothing happening. Is there something else I should do? -- 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
Re: DFHSM PROBLEM - RECALL
Did you check the syslog for the time in question for any security type messages? When you did a hsend q w - were there 2 recall tasks waiting to execute or was the recall count = ? -Original Message- From: John Dawes [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 14, 2006 9:13 PM To: IBM-MAIN@BAMA.UA.EDU Subject: DFHSM PROBLEM - RECALL Hallo, I issued a hrecall for two migrated datasets (ML1) & (ML2) and nothing is happening. I did the necessary health checks - hsend q req, hsend q act, hsend q setsys - and noticed nothing. I checked the started task and no error messages were displayed. I even ran a backvol cds (I had noticed that there was an d37-04 for the journal file.) After the backups for the MCDS, OCD, BCDS & JOURNAL) were down, I shut down the STC and brought it up. Still no action by DFHSM. I even issued hsend release recall but nothing happening. Is there something else I should do? Thanks Send instant messages to your online friends http://au.messenger.yahoo.com -- 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 -- 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
DFHSM PROBLEM - RECALL
Hallo, I issued a hrecall for two migrated datasets (ML1) & (ML2) and nothing is happening. I did the necessary health checks - hsend q req, hsend q act, hsend q setsys - and noticed nothing. I checked the started task and no error messages were displayed. I even ran a backvol cds (I had noticed that there was an d37-04 for the journal file.) After the backups for the MCDS, OCD, BCDS & JOURNAL) were down, I shut down the STC and brought it up. Still no action by DFHSM. I even issued hsend release recall but nothing happening. Is there something else I should do? Thanks Send instant messages to your online friends http://au.messenger.yahoo.com -- 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
