I would try the following steps. Under SDSF go to the ST, O and H queues and see if there is anything there. If not then you might be able to use the $ZAPJOB command of JES2 to purge the output.
I would probably take a dump of JES2 and open an ETR with IBM to see if there is anything else you would need to collect to try and determine cause and effect of this issue. The $ZAPJOB is very effective in removing jobs from JES2, I would just make sure that there is nothing there you might want. You may receive a JES2 error message when this is used, but that maybe okay. Lizette > > Hi: > > I have some held JES2 output that will not purge from the system. > Messages associated with the purge request are: > $COJ(29612),OUTGRP=2.1.1 > $HASP003 RC=(52),CO 890 > $HASP003 RC=(52),CO J(29612) - NO SELECTABLE ENTRIES FOUND > > Listing the job shows: > $DJ(29612),LONG > $HASP890 JOB(xxxxxxxx) > $HASP890 JOB(xxxxxxxx) STATUS=(ON SAPI/MVSC),CLASS=A, > $HASP890 PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE), > $HASP890 PURGE=YES,CANCEL=YES,CMDAUTH=(LOCAL), > $HASP890 OFFS=(),SECLABEL=,USERID=uuu, > $HASP890 SPOOL=(VOLUMES=(SPLC00),TGS=5, > $HASP890 PERCENT=0.0300),ARM_ELEMENT=NO,CARDS=48, > $HASP890 REBUILD=NO,CC=(CANCELLED),DELAY=(), > $HASP890 CRTIME=(2009.314,02:28:28) > > There is nothing to indicate it has a delay, but it is being processed by the Sysout > API. > Guessing, I had the user logoff/logon, in case it was SDSF. Had VPS (report > management software) bounced. > Didn't help. > > Does anyone know how to determine what is using the SAPI to hold up the sysout > purge? > > This is on a z/OS 1.11 system. > > Thanks, Ant. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
