It's good that you got it working, but needing MOUNT attribute indicates that there's something wrong in your configuration. MOUNT is there mainly for tape volumes, which no one should have much need for. If a DASD volume is not online, then something else needs fixing.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ward, Mike S Sent: Thursday, March 02, 2017 3:00 PM To: [email protected] Subject: (External):Re: SMS Routines help Ok, problem solved. Second level came back and said to add the mount attribute to the sys1.uads user profile. We did, and problem solved. Thanks to all who replied. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ward, Mike S Sent: Thursday, March 02, 2017 11:15 AM To: [email protected] Subject: Re: SMS Routines help Same system name here. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Robert Harrison Sent: Thursday, March 02, 2017 9:54 AM To: [email protected] Subject: Re: SMS Routines help Hello, I thought of a couple other items that may be the cause. Does this sandbox system have a different SYSTEM name or SYSTEM GROUP name than any other? If so, doesn't it need to be defined to the SMS Base Configuration, and all volumes in all Storage Groups that you intend to use will need to have those volumes ENABLEd for that new system name? Robert Harrison ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
