The Disk command LISTD can be used to list a set of files that were archived, in order to find out which JOB created those files.
Sometimes it can happen that in the LISTD command output, the job that created the file is set to IBMOSVS2, even if there isn't any job with that jobname that could have created the file.
Why this value and how to correctly manage it in Disk
Component : Disk Backup and Restore
In general, the literal 'IBMOSVS2' is copied from the DS1SYSCD field in the VTOC. To maintain the actual jobname of the job that created the file in this field it will be necessary to install the DISKOS SVC.
Here the link in the documentation:
Decide whether the Disk SVC maintains the job name or the accounting code. Then, update the source code in member ADSOPJBN provided in the CCUWSAMP library to reflect your selection. The default is to keep the creating JOBNAME. If this is appropriate, skip to substep 3....
so the default SVC keeps the creating JOBNAME.
Now, IBMOSVS2 is the IBM default jobname for data sets that are created but not opened. The field is not used by IBM. Once they are updated with a jobname, if the SVC is installed, it will update the field and put in the jobname.
But there are some observations to take into consideration:
This could explain why in the LISTD output, the jobname IBMOSVS2 is present for some datasets only.