Duffy, Peter wrote: > Hi, all, > > For the past year and a half I have been in a slow dance with a software > company to get their performance analysis tool running in my shop. The > mainframe version is great, I can read reports and page through long > listings, and if I know what to look for I can understand where issues > are in online and batch jobs. Users of this product need to be fairly > highly skilled at performance issues, like senior programmers or > sysprogs. > > The company touts an XML based sort of extension to their product. Run > a mainframe job to create an XML file, FTP it, view it in a browser in > full color and anyone can click to dive into fuel gauge displays to see > modules, files, etc causing waits or consuming resources. Great tool, > anyone can see the issues. > > The problem is it needs a version of JAVA that is in conflict with the > JAVA we run. We have some older apps that need the version we run. The > slow dance has been around trying this and that to get it to work to no > avail.
Oh yes, JAVA: Write once, run everywhere. Unless you're down level. And levels change pretty quickly. I have some 30-year old Assembler code that was assembled and linked once and still runs. Even COBOL (although OS/VS COBOL and older are now not viable, well after 15 years from non-support) has a longer half-life than JAVA code, it seems. Kind regards, -Steve Comstock ---------------------------------------------------------------------- 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
