Receommendations required for adding new volume to a SG pool

Alan Playford · New User Joined: 22 Aug 2012 Posts: 48 Location: UK

Guys,
Looking for some advice here, please?

I have a perfectly valid COMMDS, SCDS and ACDS currently active in my SMS environment. Well, that is to say the active configuration is valid (ACDS and COMMDS) although the SCDS has been changed by some recent definitions.

I have been using ISMF to define a whole heap of new MC, DC, SC and SG to that SCDS, but this is very much a work in progress until I have completed my ACS routines to take advantage of them all.
But we need to add a further volume or two to an SMS SG pool.
I have of course initialised the volumes as SMS, and included in the volume list.
But I can't activate this configuration due to other errors in the configuration.
e.g.
VALIDATION RESULT: ERRORS DETECTED
SCDS NAME: SYS1.DFSMS.SCDS
ACS ROUTINE TYPE: *
DATE OF VALIDATION: 2018/02/14
TIME OF VALIDATION: 10:22

IGD06122I STORAGE GROUP CICS HAS NO VOLUMES
IGD06122I STORAGE GROUP DB2 HAS NO VOLUMES
IGD06122I STORAGE GROUP IMS HAS NO VOLUMES
IGD06122I STORAGE GROUP LARGE90 HAS NO VOLUMES
IGD06122I STORAGE GROUP PRIME90 HAS NO VOLUMES
IGD06023I STORAGE GROUP CICS IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUTINE
IGD06023I STORAGE GROUP DB2 IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUTINE
IGD06023I STORAGE GROUP IMS IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUTINE
IGD06023I STORAGE GROUP LARGE90 IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUTINE
IGD06023I STORAGE GROUP PRIME90 IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUTINE
IGD06023I STORAGE GROUP VIO IS NOT REFERENCED BY THE STORAGE GROUP ACS ROUTINE

Rather than have to complete this work-in-progress right now, is there a way of copying the current ACDS back to a new SCDS so that I can just add my new volumes to the required SG pool and then reactivate the changed SCDS back to the ACDS and COMMDS?

I am aware that you can have several SCDS versions, but I have never used more than a single SCDS/ACDS before and therefore my experience is limited as to what you can do or how to do it.

expat · Posted: Wed Feb 14, 2018 8:31 pm

SAVEACDS ?

Years since I've played DASD farmer, but it sort of rings a bell

Alan Playford · New User Joined: 22 Aug 2012 Posts: 48 Location: UK

If it helps, here's my current thinking ......

1. Issue SETSMS SAVEACDS(new.SCDSname) to save the ACDS configuration into a new SCDS dataset.
(Question: Do I have to define this LINEAR dataset new.SCDSname first, or can it define it dynamically?)
2. Work on this new.SCDSname, adding the new volume to the SG pool accordingly
3. Activate this new.SCDSname, thus making the ACDS reflect the changed pool of volumes
(Question: Can I do this, or do I have to issue SETSMS SCDS(new.SCDSname) first to bring the new SCDS into the fold, as it were?)

If all works as designed, then continue to work on the "in-progress" stuff as planned until I'm ready to activate that too.

Alan Playford · New User Joined: 22 Aug 2012 Posts: 48 Location: UK

If it helps, here's my current thinking ......

1. Issue SETSMS SAVEACDS(new.SCDSname) to save the ACDS configuration into a new SCDS dataset.
(Question: Do I have to define this LINEAR dataset new.SCDSname first, or can it define it dynamically?)
2. Work on this new.SCDSname, adding the new volume to the SG pool accordingly
3. Activate this new.SCDSname, thus making the ACDS reflect the changed pool of volumes
(Question: Can I do this, or do I have to issue SETSMS SCDS(new.SCDSname) first to bring the new SCDS into the fold, as it were?)

If all works as designed, then continue to work on the "in-progress" stuff as planned until I'm ready to activate that too.

Alan Playford · New User Joined: 22 Aug 2012 Posts: 48 Location: UK

UPDATE (Solved):
Managed to get this to work in the end.

Planned actions mostly worked as intended:-
1. Had to define a new SCDS first, but then SET SAVEACDS(newSCDS) copied active (ACDS) to this file.
2. Used this new SCDS specifically (rather than "ACTIVE" to add further volume to the required SG pool.
3. Activated the new SCDS successfully. A subsequent "D SMS" shows old existing ACDS but SCDS has been changed to my new SCDS.

So, generally does what we think, except that I now have to check and amend PARMLIB entry in case of IPL, or do a little more housekeeping to tidy up old and new SCDS's to reflect what I want.

Pete Wilson · Posted: Sat Jun 09, 2018 10:57 pm

Do the SAVEACDS back into your original named SCDS then activate that, then your D SMS should reflect the correct SCDS name. (Take a backup of your original SCDS first as a precaution)

If you have the SCDS that you'd defined all your new constructs in, you can do a copy from that to the SCDS you saved from the ACDS.

If you want to Validate an SCDS with new storgrps they must have at least one volume defined. It can just be a dummy volser in NOTCON status until you add some real ones.