You might consider restricting TAPEMAXRECALLTASKS(3) to a smallish number to avoid allocation failures. You might also want to take a look at the age of the datasets being recalled. Keeping these datasets on ML1 a bit longer may eliminate your problem entirely. To directly address your question, what do you have specified for the following parameters: ACTLOGTYPE ACTLOGMSG
________________________________ From: Lizette Koehler [mailto:[EMAIL PROTECTED] Sent: Thu 8/16/2007 9:26 AM To: [email protected] Subject: DFHSM messages in syslog Is there a way in DFSMShsm to get it to put more information in syslog for RECALLS? The past several nights with ARC0381A messages. The main cause was a lack of tape drives. So we have automated the message to reply WAIT. Also to do Q ACT and Q WAIT commands to see what might be happening at that time. I am hoping there is some way to put the recall inforamtion for HSM into SYSLOG/OPERLOG. Example if I am recalling dsn X.Y.Z is it possible for HSM to produce some sort of ARC message with ARCxxxxxI Recalling X.Y.Z for userid Which Needs Volume 123456 If not, I will look at the DFHSM exits to see if there is a mechanism there. Thanks for the input. Lizette ---------------------------------------------------------------------- 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
