Check around the same timeframe to see if anybody was messing with the printer. If he had sysout sitting in the JES queue and an operator changed the printer spec's to match his output, he wouldn't have had to do anything for the sysout to print. That's more what it looks like happened.
Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Sumi, Joseph J. (CMS/CTR) (CTR) Sent: Friday, September 16, 2011 9:00 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Printing Question I have a printout but no jcl.... some more info... - The job ran and finished Sept 8 but was sent to printer Sept 12th - SMF records for the 12th do not indicate user did anything to direct it to the printer. SYSA 11255 09:03:43.86 TSU31307 00000094 $HASP150 XXXX OUTGRP=1.1.1 ON PRT8 119 (119) RECORDS SYSA 11255 09:04:21.81 TSU31307 00000094 $HASP150 XXXX OUTGRP=2.1.1 ON PRT8 119 (119) RECORDS SYSA 11255 09:04:59.38 TSU31307 00000094 $HASP150 XXXX OUTGRP=3.1.1 ON PRT8 118 (118) RECORDS SYSA 11255 09:11:26.27 TSU31307 00000094 $HASP150 XXXX OUTGRP=4.1.1 ON PRT8 119 (119) RECORDS SYSA 11255 09:12:01.06 TSU31307 00000094 $HASP150 XXXX OUTGRP=5.1.1 ON PRT8 118 (118) RECORDS SYSA 11255 09:13:36.93 TSU31307 00000094 $HASP150 XXXX OUTGRP=6.1.1 ON PRT8 119 (119) RECORDS SYSA 11255 09:15:10.25 TSU31307 00000094 $HASP150 XXXX OUTGRP=7.1.1 ON PRT8 119 (119) RECORDS SYSB 11255 09:01:04.01 TSU31307 00000094 $HASP100 XXXX ON TSOINRDR SYSB 11255 09:01:04.07 TSU31307 00000290 OPS4320H XXXX OPSS *LOCAL* AOF verb DISABLE command DISABLE SYSB 11255 09:01:04.07 TSU31307 00000094 $HASP373 XXXX STARTED SYSB 11255 09:01:04.08 TSU31307 00000094 IEF125I XXXX - LOGGED ON - TIME=09.01.04 SYSB 11255 09:21:14.48 JOB31445 00000094 $HASP100 XXXX1106 ON INTRDR XXXXzzzzz FROM TSU31307 SYSB 11255 09:23:59.48 JOB31462 00000094 $HASP100 XXXX1106 ON INTRDR XXXXzzzzz FROM TSU31307 SYSB 11255 09:40:26.49 TSU31307 00000094 IEF450I XXXX TSUSER $TSUSER - ABEND=S522 U0000 REASON=00000000 709 SYSB 11255 09:40:26.51 TSU31307 00000094 $HASP395 XXXX ENDED ) Rgrds, Joseph Sumi -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Sumi, Joseph J. (CMS/CTR) (CTR) Sent: Friday, September 16, 2011 9:29 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Printing Question Hello, this happened last week so there is nothing to check in SDSF (actually IOF). Since it is from his TSO user, what action could he have done to initiate the HASP150 ?? I tried a couple things under my id but I can't replicate the HASP150. I will run SMF recs for him that day and look for clues there. Thanks. Rgrds, Joseph Sumi -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Binyamin Dissen Sent: Friday, September 16, 2011 9:15 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Printing Question On Fri, 16 Sep 2011 08:45:17 -0400 "Sumi, Joseph J. (CMS/CTR) (CTR)" <joseph.s...@cms.hhs.gov> wrote: :>I have a user that had his sysout go to the printer but he doesn't know why/how. The only clues I see are these JES2 messages. What activity would drive these messages ? When he ran the job, he did ~not~ have a print class specified. (I tried to recreate by changing my sysout to class A but I do not see the same hasp150 so it doesn't look like he did anything). :> :>TSU31307 00000094 $HASP150 xxxx OUTGRP=1.1.1 ON PRT8 119 (119) RECORDS :>TSU31307 00000094 $HASP150 xxxx OUTGRP=2.1.1 ON PRT8 119 (119) RECORDS :>TSU31307 00000094 $HASP150 xxxx OUTGRP=3.1.1 ON PRT8 118 (118) RECORDS Consider the TSU above, it wasn't from a job - it was from his TSO session. -- Binyamin Dissen <bdis...@dissensoftware.com> http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited and that you will be held responsible for any such unauthorized activity, including liability for any resulting damages. As appropriate, such incident(s) may also be reported to law enforcement. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
