It appears that your storage admins have coded the SMS ACS routines so that based on some attributes you are providing, ie. It being a VSAM dataset, the dataset name etc. the dataset is assigned a STORAGE CLASS, making it SMS managed. You most likely have to talk to the storage group and see if there is a way to request that the dataset is NOT SMS managed. In some shops, this is done via requesting STORCLASS(NOTMGMD) (or NONSMS, NOSMS etc), but this is per installation, and use of this may be restricted. As an aside, why do you feel that this dataset should not be SMS managed?
Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Thursday, August 30, 2007 7:19 AM To: [email protected] Subject: SMS Question Good Morning, I am trying to allocate a VSAM dsn on 3 volumes which are not SMS managed. However, SMS tries to allocate the dsn in a SMS storage pool. How can I bypass SMS so as that I can allocate the dsn on these 3 vols. Below is my jcl and the error message. DEFINE CLUSTER (NAME (Z8002D.TESTE.CLIFCPRK) - INDEXED - KEYS (20 0) - RECSZ (2000 2000) - FSPC (10 10) - VOLUMES (VEBC5A,VEBC5B,VEBC5C) - SHAREOPTIONS (1 3)) - DATA (NAME (Z8002D.TEST.CLIFCPRK.KDATA) - CYL (3300,400) - CISZ(4096) ) - INDEX (NAME (Z8002D.TEST.CLIFCPRK.INDEX) - CYL(30 10) - CISZ(1024) ) IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET Z8002D.TEST.CLIFCPRK IGD17290I THERE WERE 1 CANDIDATE STORAGE GROUPS OF WHICH THE FIRST 1 WERE ELIGIBLE FOR VOLUME SELECTION. THE CANDIDATE STORAGE GROUPS WERE:LIBSG01 ---------------------------------------------------------------------- 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
