z196: Performance: 2714887 REXX clauses per second z10: Performance: 1732967 REXX clauses per second
Marcy -----Original Message----- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of peter.w...@ttc.ca Sent: Friday, June 10, 2011 7:02 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] REXXCPS EXEC Well, I just tried it on our z9 BC E01: rexxcps ----- REXXCPS 2.1 -- Measuring REXX clauses/second ----- REXX version is: REXX370 4.02 01 Dec 1998 System is: CMS Averaging: 100 measures of 100 iterations Calibration (empty DO): 0.00014319 secs (average of 100) Spooling trace NOTERM Spooling now back on TERM Total (full DO): 0.91546694 secs (average of 100 measures of 100 iterations) Time for one iteration (1000 clauses) was: 0.0091546694 seconds Performance: 109234 REXX clauses per second Ready; It would be fun to try on an uncapped z196 (not that I'm ever likely to see one of those). Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Les Koehler Sent: June 10, 2011 06:18 To: IBMVM@LISTSERV.UARK.EDU Subject: REXXCPS EXEC I'm curious... Has anyone with real mainframe hardware (no emulation) recently run REXXCPS that MFC wrote way back when? See: http://speleotrove.com/misc/rexxcpslist.html for his collection of data. If you've never seen REXXCPS, there's a link to it at the top of the page. Just remove the hash-bang usr/bin to run it on a VM userid. Les The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot be guaranteed on the Internet. The sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on the basis of information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is property of the TTC and must not be altered or circumvented in any manner.
