RE: SAV/RST spool files function in OS/400

["Leland, David" <dleland@xxxxxxxxxx>]

You're missing the point - what happens if you save a spool file on one system and restore it to another and there is already the same job name, user, job number and spool file number on the target system.  IBM's gotta think about that scenario because it won't be very likely to happen but it could.

 

The way you've got to look at this entire situation, is that you would essentially be restoring a job to a different system and how could duplicate jobs be handled?  When you're just restoring objects, it's not nearly as complicated because it's a single thing.  A job has many parts to it.

 

Dave

-----Original Message-----
From: M. Lazarus [mailto:mlazarus@ttec.com]
Sent: Friday, September 22, 2000 3:07 PM
To: MIDRANGE-L@midrange.com
Subject: RE: SAV/RST spool files function in OS/400

Dave,

At 9/22/00 12:58 PM -0500, you wrote:

But what happens if you are restoring from a different system and the job number is already in use by another job on the target system?  I don't think this SAV/RST spool file thing is gonna be very easy.  Other AS/400 objects are not attached to jobs but spool files are.

 For the most part, people are interested in the contents of the spool file, not the ended job structure.  That would probably satisfy 90%+ of the /400 population.  Now for the rest, the originating job's attributes are available as information, probably in the spool header (reference DSPSPLFA, or option 8 from WRKSPLF).

 I see no reason that that information can't be saved along w/ the spool.  Maybe an additional command (or parm on the DSPJOB command) could xref that info.

 -mark