I have this figured out thanks to all your tips / suggestions ...
We use IOF .... IOF lets you SNAP to sysout (SS) or SNAP to a dataset (SD). I
can tell by the SMF records he snapped to a dataset but that was after all the
prints took place. What looks to have happened is that he first issued SS
accidently .... (the default class for SS is "A" for the printer).
If I issue SS and then SNAP my job, my screen just blinks but under my userID,
there is a new DD created and this gets processed and sent to the printer:
For example:
4 SYS00013 TSOACCNT TSOACCNT A 1 W 160 L HCFJES
Thanks for helping me clear up this mystery, Rgrds, Joseph Sumi
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Walt Farrell
Sent: Friday, September 16, 2011 2:47 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Printing Question
On Fri, 16 Sep 2011 14:20:14 -0400, Sumi, Joseph J. (CMS/CTR) (CTR)
<joseph.s...@cms.hhs.gov> wrote:
>Maybe this is ISPF related and he somehow triggered an ISPF log or something
>(that contains what I'm seeing in print) to go to the printer. The printout I
>have has "XXXX - TSU31307" on the cover with a print date of sept 12 .... the
>associated job printout is for job "XXXX1106-JOB25279" that ran on Sept 8th.
>
>(Xxxx = his userid)
That sounds like he was in SDSF and viewing job 25279 and asked SDSF to print
the job. That would create one or more SYSOUT files for his TSO session,
containing output from his batch job.
--
Walt
----------------------------------------------------------------------
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
