How to Locate Spooled Files Restored

During a system migration, the customer saved spooled files and restored them; however, the spooled files could not be located on the new system.

Starting with R540 migration to a new system, it is possible to also save spooled files created on the source system. Internal job structure is not saved together with the spooled file. After the restore, it may be possible that users are not able to locate the spooled files restored using job-related commands such as the Work with Job (WRKJOB), Work with Submitted Jobs (WRKSBMJOB), or Work with User Jobs (WRKUSRJOB)

This occurs because when a spooled file is restored, it is reattached to the original job if the original job still exists on the system. If the original job does not exist, the spooled file is restored in a detached state. Therefore, because the job structures from the old system did not come over the spooled files, they are restored in detached state.

To locate the spooled files restored, the JOB parameter on the Work with All Spooled Files (WRKSPLF) command should be used:

Work with Spooled Files (WRKSPLF)

Type choices, press Enter.

Select files for:

-->User . . . . . . . . . . . > *ALL Name, generic*, *CURRENT
Print device . . . . . . . > *ALL Name, *ALL, *OUTQ
Form type . . . . . . . . > *ALL Form type, *ALL, *STD
User data . . . . . . . . > *ALL User data, generic*, *ALL
ASP . . . . . . . . . . . > *ALL 1-32, *ALL, *ASPDEV
--> Spooled file . . . . . . . > *ALL Name, generic*, *ALL
-->Job name . . . . . . . . . . > DGCJ477A Name, generic*, *ALL
--> User . . . . . . . . . . . > OPER Name, generic*, *ALL
--> Number . . . . . . . . . . *ALL 000000-999999, *ALL


Note: To find out a job with a specific spooled file name, the name should be specified on the Spooled file field; to find out only the joblog, you should insert the QPJOBLOG name in the Spooled file field.

Spooled file . . . . . . . > QPJOBLOG instead of *ALL