Pete, The PARSE.ALL script (the one that updates the scratch pool) was locally customised for our Luminex gateways customers to eliminate this problem. Processing was made faster by loading the whole list into memory before doing the necessary checks and the scratch pool on the Luminex was locked while this processing occurred.
I believe the Luminex guys have improved this script recently but we have not yet tried it. Richard Marchant Johannesburg -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Vander Woude Sent: 27 January 2011 04:12 PM To: [email protected] Subject: scratch tape processing and luminex We've got some luminex gateway appliances for virtual tape processing and are running into issues where between the time we generate the listing of scratch tapes, run update of the volcat, and send the scratch list to the luminex, some tapes are used and changed to master status in rmm. The window that this usually occurs in is a very short one (<30 seconds), but it has caused production jobs to fail. For those of you that have luminex devices, have you run into the same issue? If so, how did you change things to eliminate that issue? Pete ---------------------------------------------------------------------- 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
