If the dataset is SMS managed and the dataset is not cataloged in your current catalog structure, you can't edit it without specifying the volser.
For instance, if you use 3.4 and display a SMS volume (by volser and not displaying by HLQ), and try to edit a SMS dataset that is not cataloged in that current catalog structure, then it will fail with the message you saw. Since it's a new system, possibly you didn't include the catalog that owns that dataset's HLQ in your 3.1 catalog structure, i.e. it's in a usercat which has not yet been imported into your new master catalog, or you did import the catalog, but didn't define the alias as being owned by that catalog in your "new" master catalog. If none of that is changed, then it's probably something simple like you need to update your ACS routines to make sure that zos knows that the volume is indeed a SMS volume and is part of some "valid" storage group. Sometimes people forget that you have to reload or at least catalog your SMS ACDS, SCDS and COMMDS for that new system and SMS comes up in null configuration mode, sometimes people will change the name of the LPAR (because it's new) and forget that their old ACDS doesn't know about that LPAR (yet), so it doesn't load the SMS routines and constructs that you need for that particular "new" LPAR. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
