On 9/11/06, Huegel, Thomas <[EMAIL PROTECTED]> wrote:
I was thinking along these lines.. Still do a DEFSEG and a SAVESEGS but the files would be written to a CP accessed mini disk call it CCF1. Then a new command LOADSEGS would move the files to 'temporary' spool space.
Since CP can already read files from a CMS formatted disk that you have under CPACCESS, why not change it that CP will simply read the pages from a file on one of those disks. With a few extra commands to make CP switch to a new file somewhere in the search order. You'd have your normal CMS facilities to copy, rename, backup and erase these files, manage them like any other system file. You could even alternate between disks to separate releases, etc. The VMSES/E code to build segments would have to be changed to replace the defseg / saveseg by something that creates a CMS file. The only good thing about NSS in spool is probably that you potentially spread the file over multiple spool volumes and have more bandwidth to bring it in the first time. But NSS files in spool is also a lot of evil. Since they are spread over all spool packs, any problem with a spool pack will make you lose the NSS files. Back when I was concerned about such things, I have considered to even drain all but one spool pack while build an NSS so that you keep the entire file on a single pack. Rob
