One reason people will code 0 linecount/cardcount in the jobcard is that it can 
affect the jes input queue priority.  On systems where queuing is frequent this 
is one way to get your job bumped to the top or at least higher on the food 
chain.



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 Jesse 1 Robinson
Sent: Tuesday, June 13, 2017 3:17 PM
To: [email protected]
Subject: Re: [IBM-MAIN] Wacko S722 abend

Problem solved thanks to a colleague who put the right keywords on a Google 
search and found a past IBM-MAIN thread that provided the answer. This from the 
job card:

JOB (TE000MEJIC,DK6D,,0),...

In all my years I never learned about the 'other positional sub-parameters' of 
the accounting field. As spelled out in the JCL doc, the fourth sub-parameter 
means 'lines':

(pano,room,time,lines,cards,forms,copies,log,linect)

This job (as well as well a few others we discovered) were created by the same 
guy many years ago. Do not know what prompted him to add other sub-parameters, 
but that was the cause. As long as OPT=0 was in effect at the system level, we 
got the mysterious warning but no failure. When we set OPT=1, kaboom.

Thanks to all who chimed in.

.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
[email protected]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Peter Hunkeler
Sent: Tuesday, June 13, 2017 11:43 AM
To: [email protected]
Subject: (External):AW: Re: Wacko S722 abend

Can you post the JCL?


--
Peter Hunkeler


----------------------------------------------------------------------
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

Reply via email to