There are two sections to the output, the second section has one entry for each outstanding stage file request. The first section shows the WORKER jobs for each TAPE that is staging. These jobs should be pending or executing. If there are missing WORKER jobs (i.e. a request to stage file from tape xxxxxx exists but there is no corresponding WORKER_xxxxxx job) you can start the missing jobs by logging on as SLDSTAGE and typing:
This allows you to see a chronological list of all staging file requests, and in the case of failures allows you to link to the correct log file. This is the best way to try to diagnose problems.
This shows all the files on disk, and the space used. You will occasionally see files listed as "error". This indicates some problem occured during staging.
Should the database become totally corrupted somehow it can be rebuild by logging on as SLDSTAGE and issuing the command:
@STAGE_$SRC:FIXUPbut this should ONLY be done when there are no staging jobs running or queued (see above).
Notice that to see the special SLDMCM area instead on the default staging are you must first redefine the STAGE$DIR logical name, as is done in SLDMCM's LOGIN.COM