> On Sep 27, 2017, at 12:53 AM, Bruce Hewson <[email protected]> wrote: > > In my almost 40 years of MVS support, the only time I came across SYS3 was in > a very large, multi-site, company. > > For security segregation each subsystem group was assigned a unique SYS% > hlq.. SYS2,SYS3,SYS4,etc > > Not an issue for MVS support as all the product datasets were placed on > cloned sysres sets. > > All the SYS% datasets get cataloged in the system Master catalog. > > No sysres dataset is ever migrated by HSM. > > Once you get used to the site's dataset naming convention, anything can work. >
Bruce,, That looks like an idea situation. Most of us are in a less than idea situation. When say sys3 datasets are managed by another group, (we) could not dictate anything to them. They had their own methodology. One day during IPL, indeed one of their datasets somehow got migrated, if memory serves me it was a STK load lib. They were in a catch 22 situation. I let them fumble around for 30 minutes and since we were getting close to market open time. I fixed the issue. I left a note on their supervisors door and told him they had to conform to our standard or this would happen again. That afternoon we were invited to their group meeting and we gave them the rules. Everyone of them were argued about, I said look either you conform or we will take away this type of software so we won’t have anymore outages. That got a little a few more arguments. I said look, next time myself or any of the group might not be around and the markets won’t open and who will get blamed for that? We ended up taking control back for any system critical product. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
