Rich Greenberg wrote:
On: Mon, Sep 11, 2006 at 08:48:33AM -0500,Huegel, Thomas Wrote:
} For what it's worth I am still doing flips at not having to deal with DMKSYS
} assemblies and IPL's for the saved segments. Now I am thinking 'Why keep
} them in spool space?' Wouldn't a more logical approach be to save the
} segments on a CP minidisk i.e. MAINT's CF1?
} That would solve a lot of backup/restore/format problems.
But then wouldn't you be back to HCPSYS? Unless you just have a section
of a CP-Owned volume allocated to say DCSS and you do DEFSEG and
SAVESEGS into there. But wouldn't that be spool by another name?
What I would like is more control over the classes, so you could have
several copies of a DCSS in the spool and the one you make class A is
the active one and other classes are there as backups, and class P works
as present. Perhaps a NEWCLS option on SAVESEG with the default being P.
Ahh ... HCP/DMKSYS . One function we lost when NSSs came along was the
ability to "rename" a DCSS
or IPLable Saved System at system boot time by changing the name of an
entry. We used this to flip-flop
CMS systems on at least one occasion at a former shop when (for details
I cannot recall now), the GENIPLer
could not handle the case. When NSSs were introduced into SPOOL, I
thought it would be nice to have
an option of the CP CHANGE command that would allow me to rename an NSS.
