|
Unfortunately OS/400 spool support is really just a collection files, members and data records. Any save/restore process I'm aware of is unable to restore spool file data and maintain the original user job attributes. Once a spool file is restored, the original user won't be able to access it using the WRKSPLF *CURRENT command.
However, IBM's BRMS solution lets you back up spool files to *SAVF's. It then lets you search for these saved spool files based on several spool file attributes:
Work with Saved Spooled Files (WRKSPLFBRM)
Type choices, press Enter.
Output queue . . . . . . . . . . OUTQ *ALL
Library . . . . . . . . . . . *ALL
Auxiliary storage pool . . . . . ASP *ALL
File . . . . . . . . . . . . . . FILE *ALL
Job name . . . . . . . . . . . . JOB *ALL
User . . . . . . . . . . . . . . USER *ALL
User data . . . . . . . . . . . USRDTA *ALL
Select dates: SLTDATE
From date . . . . . . . . . . *BEGIN
To date . . . . . . . . . . . *END
Save status . . . . . . . . . . SAVSTS *ALL
Sequence option . . . . . . . . SORT *DATE
From system . . . . . . . . . . FROMSYS *LCL
Output . . . . . . . . . . . . . OUTPUT *
Using a product like this would allow you to save all the spool files into *SAVF's and then migrate this data to the new system. If a user needed to access an old spool file, he or she could easily locate and restored it.
That's about the best solution I can think of.
|
