ah ! that's the key, thanks so much Lucas $TS(2418),S=-IND $HASP890 JOB(CCITCP) 788 $HASP890 JOB(CCITCP) STATUS=(AWAITING PURGE),CLASS=STC, $HASP890 PRIORITY=1,SYSAFF=(ANY),HOLD=(NONE) $HASP250 CCITCP PURGED -- (JOB KEY WAS D1BEA56E) made my day ! carmen ----- Original Message -----
From: "Lucas Rosalen" <rosalen.lu...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, January 13, 2017 8:57:45 AM Subject: Re: strange JES2 purge queue issue I think the key here is the SYSAFF=(IND,ANY)... Try to take INDependent off before purging, with $TJQxxxxx,SYSAFF=(-IND) ------------------------------------------------------------------------------------------------------------------------------- *Lucas Rosalen* Emails: rosalen.lu...@gmail.com / *lrosa...@pl.ibm.com <lrosa...@br.ibm.com>* LinkedIn: http://br.linkedin.com/in/lrosalen Phone: +48 (71) 792 809 198 2017-01-13 15:55 GMT+01:00 Carmen Vitullo <cvitu...@hughes.net>: > all the DESTID's defined and all my print to these destinations are > working as designed. > the strange awaiting purge issue I found all the sysout was from my > initial failed attempt to bring these systems into a MAS back in December, > job display shows > > > $DS1883,LONG > $HASP006 $DS1883,LONG TRANSLATED BY EXIT HASX05C TO $DS(1883),LONG > $HASP890 JOB(CCITCPGW) 392 > $HASP890 JOB(CCITCPGW) STATUS=(AWAITING PURGE),CLASS=STC, > $HASP890 PRIORITY=1,SYSAFF=(IND,ANY),HOLD=(NONE), > $HASP890 CMDAUTH=(LOCAL),OFFS=(),SECLABEL=, > $HASP890 USERID=CCITCPGW,SPOOL=(VOLUMES=(SYSSA2), > $HASP890 TGS=1,PERCENT=0.0002),ARM_ELEMENT=NO, > $HASP890 CARDS=2,REBUILD=NO,CC=(COMPLETED,RC=0), > $HASP890 DELAY=(),CRTIME=(2016.339,15:03:56) > > > I've attempted to change the SYSAFF to (ANY,ANY), no good > I've attempted to change the SYSAFF to (SYSA,SYSC), no good > I think its PMR time, this is not causing a spool issue, I just would like > to get this output 'awaiting purge' to purge ! > again thanks all > Carmen > > > ----- Original Message ----- > > From: "Carmen Vitullo" <cvitu...@hughes.net> > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Friday, January 13, 2017 8:08:20 AM > Subject: Re: strange JES2 purge queue issue > > :) yep first thing I thought of - no good > I think my fellow team members may have shed some light, these jobs > originally ran on SYSA, now run on SYSC, well I don't have the Jobclasses > and destid's defined on that system, so I'm thinking this is causing both > issues, I'm thinking if the DESTID is not defined on the system the jobs > run, JES2 has no clue and put the job on user hold, same with the sysout > (jobclasses) maybe . > I'll let you know > thanks Allan > Carmen > > > From: "Allan Staller" <allan.stal...@hcl.com> > To: IBM-MAIN@LISTSERV.UA.EDU > Sent: Friday, January 13, 2017 7:54:39 AM > Subject: Re: strange JES2 purge queue issue > > Try releasing the jobs $AJnnnnn > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Carmen Vitullo > Sent: Friday, January 13, 2017 7:45 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: strange JES2 purge queue issue > > I've just completed the merging of 2 systems into a JES2MAS, we're z/OS > 2.1 RSU1508 on both systems, thanks to all the fine folks here the process > to get these systems into a MAS was sucesfully, the only issue I had was > with one CA-SPOOL print destination, for some reason the output status on > JES was 'USER' CA-Spool will not pick it up from the queue. When we print > to R21, which is the alias to ltrm4fe, it comes out without the status of > ‘user’ and prints to their printer without any issues. looking deeper into > the Queues, I see many jobs sitting in the purge queue 'awaiting purge' and > I cannot for the life of me figure out why, status shows > > $HASP890 JOB(VTAMCHK) > $HASP890 JOB(VTAMCHK) STATUS=(AWAITING PURGE),CLASS=STC, > $HASP890 PRIORITY=1,SYSAFF=(IND,ANY),HOLD=(NONE), > $HASP890 PURGE=YES,CMDAUTH=(LOCAL),OFFS=(), > $HASP890 SECLABEL=,USERID=VTAMCHK, > $HASP890 SPOOL=(VOLUMES=(SYSSA2),TGS=1, > $HASP890 PERCENT=0.0002),ARM_ELEMENT=NO,CARDS=2, > $HASP890 REBUILD=NO,CC=(COMPLETED,RC=0),DELAY=(), > $HASP890 CRTIME=(2016.339,15:03:32) > I've attempted to cancel via JES $CSxxxx and jes2 comes back 'job cannot > be cancelled' when I purge this job the status remains the same, they are > already awaiting purge, any clues? > thanks > Carmen > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ::DISCLAIMER:: > ------------------------------------------------------------ > ------------------------------------------------------------ > ---------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > E-mail transmission is not guaranteed to be secure or error-free as > information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or may contain viruses in > transmission. The e mail and its contents > (with or without referred errors) shall therefore not attach any liability > on the originator or HCL or its affiliates. > Views or opinions, if any, presented in this email are solely those of the > author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, > distribution and / or publication of this message without the prior > written consent of authorized representative of > HCL is strictly prohibited. If you have received this email in error > please delete it and notify the sender immediately. > Before opening any email and/or attachments, please check them for viruses > and other defects. > > ------------------------------------------------------------ > ------------------------------------------------------------ > ---------------------------- > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
