A few years ago I wrote a little REXX program that builds a LISTCAT LEVEL statement, calls IDCAMS and then reads the LISTCAT output to create a list of files to process.
The program worked fine for a while but after a migration to z/OS 1.7 it started to act oddly. At times the LISTCAT would get a return code 4 and no data in the output. This happened when I know that there were files to be found. In addition this odd behavior only happened when the CPU was very busy. I modified my program to replace the LISTCAT with a call to the Catalog Search Interface (CSI) and the problems went away. Well almost, my program also has a TSO LISTDSI command in it that sometimes fails. Again this only happens when the CPU is very busy. I have worked around the LISTDSI problem by ignoring any file that encounters the failure because I can process the file in a later run of the program. My guess is that LISTDSI is encountering the same problem that LISTCAT was. So now lets move on to a new problem under z/OS 1.10. I have a third-party product that does a LISTCAT and sometimes it cannot find files when the CPU is very busy. The vendor is now endeavoring to replace their LISTCAT code with CSI code but their programs are assembler so its going to take them a while to do it. I've searched the IBM databases and IBM-MAIN for similar problems but cannot find any. So I'm curious, has anyone else out there seen this odd behavior? If so, were you able to find a fix for it. Cheers, Rod. ---------------------------------------------------------------------- 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
