This happened some years ago, different incident. We had a nightly job that ran on four different parallel sysplexes to [list catalog stuff]. Don’t remember the details. Essentially the same job ran on three sysplexes in about 2 minutes. On the fourth it ran over 20 minutes. I looked at the environments to see what was different in molasses world. The only difference I could see was that the three speedy sysplexes were set up for GRS star. The fourth, because it had only one active member, was still GRS ring. (I was stingy in those days with CF storage.) So on a lark I converted Mr. Snail to GRS star. From then on the job ran in 2 minutes. Sounds like a tall tale, but it really happened.
. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Brennan Sent: Tuesday, November 17, 2015 5:19 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Fastest way to read OLDEST GDG entry Paul Gilmartin wrote: > Naively, I'd expect that LISTCAT use CSI, or something very similar. Years ago a Storage Admin mentioned that his "List every dataset" nightly job was running more than an hour. I was playing around with CSI at the time (via assembler) and modified some existing code to list every alias, and then every dsn under each alias. I think the result ran in less than 5 minutes, so at the time I assumed LISTCAT wasn't calling CSI. Maybe things have changed though. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
