IIRC it could also pick up from the USER= or NOTIFY=
CIT | Ken Porowski | VP Mainframe Engineering | Information Technology | +1 973 740 5459 (tel) | [email protected] This email message and any accompanying materials may contain proprietary, privileged and confidential information of CIT Group Inc. or its subsidiaries or affiliates (collectively, "CIT"), and are intended solely for the recipient(s) named above. If you are not the intended recipient of this communication, any use, disclosure, printing, copying or distribution, or reliance on the contents, of this communication is strictly prohibited. CIT disclaims any liability for the review, retransmission, dissemination or other use of, or the taking of any action in reliance upon, this communication by persons other than the intended recipient(s). If you have received this communication in error, please reply to the sender advising of the error in transmission, and immediately delete and destroy the communication and any accompanying materials. To the extent permitted by applicable law, CIT and others may inspect, review, monitor, analyze, copy, record and retain any communications sent from or received at this email address. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, CP - SPLXM Sent: Monday, April 15, 2013 9:52 AM To: [email protected] Subject: Re: [IBM-MAIN] Strange response to SDSF PREFIX command Interesting enough to make me go search. For a change I jumped to RTFMing with PF1 and it shows: Purpose: Limit the jobs that are displayed by job name. (In some cases, this involves columns other than JOBNAME. See the note at the end of this topic.) ... With the PREFIX command, two additional columns may be used. For jobs that entered the system through the TSO/E Interactive Data Transmission Facility (netmail), SDSF compares the value for the PREFIX command with a value that is displayed in the Wtr column (output external writer name) or as part of the Dest column (JES print destination name). Does this help? Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of EXT-Schwarz, Barry Sent: Monday, April 15, 2013 15:41 To: [email protected] Subject: Strange response to SDSF PREFIX command We have a sequence of JES2 commands that run at 1600 every day to purge output more the 7 days old. For reasons almost lost in antiquity, the sequence avoided purging jobs/tasks that begin with S. When I first noticed several hundred jobs in the output queue (SDSF command O), I started looking for a pattern. I issued the PREFIX A* and saw a few but they were recent. I then issued PREFIX B* and dozens of jobs name SU00Y appeared. (If it matters, the prefix commands were entered in lower case. I capitalized them here for ease of reading.) I have never seen a response that didn't match the prefix before. This is on z/OS 1.11. Thoughts anyone? PS - After finally recalling the reason for this, the fix to the command sequence is to add $PJQ(S*),JM!=SYSLOG,A>7 but I'm still curious why SDSF thought SU00Y matched prefix B*. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ******************************************************** ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
