While I clearly didn't recollect the correct command names, I do remember specifically that when one of the commands that used TPUT was encountered in the list of commands in my benchmark batch job, none of the subsequent commands in the input DD (SYSTSIN??) were executed, so I would delete that command and rerun until I had a list of commands that did execute in TSO in batch.
FWIW, this was one of 23 batch jobs in my benchmark job stream, each executing a different program/application/online-system, that was used for evaluation of new hardware and/or new software. I would read several hundred copies of each of these 23 jobs into a system with no initiators running, and then would start 5 inits every 5 minutes for an hour, and then could compare the results to the current system's benchmark, primarily to set the CPU billing factor for the new system, but I could also measure the increase in CPU time for each job as contention increased with the increased multiprogramming ratio from 0 to 60. I could also run the same benchmark with ONLY the TSO jobs running, to simulate up to 60 in/ready TSO users with 60 inits, which corresponded to over 600 users logged on, without a human at a terminal. Barry Herbert W. "Barry" Merrill, PhD President-Programmer MXG Software Merrill Consultants 10717 Cromwell Drive Dallas, TX 75229 [email protected] http://www.mxg.com - FAQ has Most Answers [email protected] - invoices/PO/Payment [email protected] - technical tel: 214 351 1966 - expect slow reply, use email fax: 214 350 3694 - prefer email, still works -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Shmuel Metz (Seymour J.) Sent: Tuesday, July 08, 2014 7:22 PM To: [email protected] Subject: Re: Authorizing 8 char technical userid to use TSO CONSOLE command In <[email protected]>, on 07/08/2014 at 08:22 AM, Barry Merrill <[email protected]> said: >Not sure if this applies to this issue, but I recall that TSO commands >that issue TPUT will simply stop the rest of the commands in a Batch >TSO job, They don't stop anything, but the TPUT also doesn't dis[play anything. More precisely, "In a batch environment, the only TPUTs that are processed are those with the ASID, ASIDLOC, or USERIDL keyword referencing an ASID or user ID other than the current one. TGET, TPG, and other types of TPUT macros are ignored." >but commands using PUTLOG work fine. ITYM commands using GETLINE, PUTGET and PUTLINE. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see <http://patriot.net/~shmuel/resume/brief.html> We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- 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
