Daniel, You indicate that you had called CA support already, I will look it up and contact during the day tomorrow. With TLMS (and CA-1) you have the option of either doing real-time scratch syncronization (scratching the tapes inside the IBM robot as the tapes are scratched by the tape management system) or taking the output from the scratch-list and post-processing them through CTSSYNC. You also have the ability to simply take a list of ALL scratch tapes known to TLMS and scratching them inside the robot. So, with CTSSYNC you have lots of flexability.
Not sure exactly what has changed recently at your location. It sounds like everything had been running fine for some time, and all of a sudden things have stopped working. Either an exit has been lost or disabled, or a daily procedure has stopped running. First thing of course is to get the tapes back in scratch status. As for eject processing; again there are options. With TLMS there is an option to eject the tapes automatically when the LOCATION changes or to run an EARL report and create a list of all tapes changing location today and ejecting them in a post-process. Again, the choice is yours. It would be helpful if you knew what your existing procedures where, but that can wait until the scratch-tape situation has been resolved. Russell Witt TLMS Level-2 Support Manager -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] Behalf Of Daniel McLaughlin Sent: Thursday, July 12, 2007 9:04 AM To: [email protected] Subject: ATL and TLMS We put an ATL in last year. Not being familiar with all the goodies that TLMS has we rolled out some REXX code to produce ejects based on DSNs. Seemed to work until this past weekend we ran out of scratches in the ATL and all we had appeared to be offsite at the vault. This morning I re-inventoried the ATL and much to my surprise I had over 400 scratch tapes inside that weren't scratch before and should have been. Then today's library run produced an eject list in excess of 100 volumes, way beyond normal for a weekday. Then the CTSSYNC step kicked out a gaggle of errors about the ATL synchronization being bypassed and tape managment not active. According to CA I can run the eject followed by the synch or the synch followed by the eject with no difference. We're going crazy trying to figure out why we get so many errors and all the looking and questions sent to CA haven't yielded a good solid solution yet. I'm getting ready to install TLMS 11.5 SP1 to see if maybe it will help. Have any of you ATL users run into similar issues? We really want to nail this down as next month we add a VTS to the fray. Thank you in advance. ---------------------------------------------------------------------- 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
