|
Well, let's see... You would need to know which OUTQ to restore to and who to own it. The rest of the stuff I think is already available in the current descriptions or contents. Now, we have a sysval that describes whom the default owner is as I recall for when a object is restored and there's a lack of owner or security issue or when a user profile is removed and you want to assign the owned objects to a DFTOWN.... SO, what's the problem? SO, why not RSTSPLF file(xxxx) outq(xxx) job(123.abc.xyz) splnbr(32767) RSTTOQ(to_outq) SPLFOWN(*OLD/*SYSVAL/THEMADPGMR) BY DEFINITION: the system would have to assign it a new job ID and SPLF#... Further, by definition, the SAVSPLF object encapsulation would include any overlays, sigs, graphics, etc., that used. And, the splf data stream type would be the same as the original...ie, you couldn't save a AFP and restore it as a SCS...(although technically, you probably could). Frankly, I'm surprised Al doesn't have a tool that does something like this. Al? I'm not up to the latest on tools...feel free to fill in the blanks... I used to know all this spool data stream stuff back several years ago when I had to ripappart fax/400....but it's been several years. Right now I've got 3 dialects of linux, 2 dialects of unix, 2 dialects of Windows Server and OS/400 running amuck vying for a timeslice...so pardon the parity errors...:) ...and Oracle's in there somewhere as well...! Don in DC -------------------------------------- On Mon, 24 May 2004 michaelr_41@xxxxxxxxxxxxxx wrote: > Too hard to do probably. At least not so it's 100% accurate. > > On Mon, 24 May 2004 15:01:56 -0400 (EDT), "Don" <dr2@xxxxxxxxxxxx> said: > > > > > > Can someone refresh me as to the reason why Rochester doesn't allow SPLF > > save/restore? > > > > Don in DC > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing > > list > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > > To subscribe, unsubscribe, or change list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx > > Before posting, please take a moment to review the archives > > at http://archive.midrange.com/midrange-l. > > > -- > > michaelr_41@xxxxxxxxxxxxxx > > -- > http://www.fastmail.fm - Choose from over 50 domains or use your own > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.