On Jan 24, 2017, at 5:59 PM, Gerhard Adam <[email protected]> wrote: > > I see that part of the problem may be identifying the job that is holding > spool space. I suggested spool offload, as a possible way to either (1) > move existing data, or (2) identify job holding it. If you know the job, > then you might be able to use the $Tjob command to SPIN the data currently on > the spool if the job is still active.
“[I]dentifying the job that is holding spool space” was the entire problem. We had already gone through an IPL since I started draining the volume, and I had identified and dealt with all the “job” jobs on the volume. My mistake was that instead of reading the manual I just scanned the table of contents, and I already knew $DJ to display jobs so when I saw the section heading “$D Job - Display information about specified jobs” I didn’t look more closely to see that it also included $DS, $DT, and $DJQ. Once Dave pointed me at $DJQ my problem was solved. Thanks. -- Pew, Curtis G [email protected] ITS Systems/Core/Administrative Services ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
