The problem I found was that overlapping moves (to perform array 
initialization, for example) no longer worked.  I (and no doubt many others) 
flew into a rage after looking at the object code and realizing that there was 
no test for the overlapping move condition.  It was changed in a subsequent 
PTF, but by then it was too late - we had replaced the offending code with 
PERFORM loops.
David de Jongh

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On 
Behalf Of Gary Weinhold
Sent: Thursday, October 15, 2015 11:59 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Moves and others

I seem to recall when COBOL first started to compile to MVCL, Amdahl SEs 
zapped it to an MVC loop and greatly improved COBOL performance.  Or something 
like that...

Gary
On 2015-10-15 12:21, John McKown wrote:
> On Thu, Oct 15, 2015 at 11:16 AM, Paul Gilmartin < 
> 00000014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote:
>
>> On 2015-10-15, at 08:48, Robin Vowels wrote:
>>> IBM should have produced a special EXC instruction for characters, 
>>> that did what EX does, but accepts k, the number of bytes to move 
>>> (or
>> compare, etc),
>>> tests for zero (and performs a no-op if it is), subtracts 1, and 
>>> then
>> executes MVC.
>> MVCL?
>>
> ​There are many people who greatly dislike MVCL. I remember when it 
> first came out, my boss said he would never use it because it was way 
> too slow (this on a 3033). Personally, I like MVCL and CLCL too.​
>
>
>
>> -- gil
>>
>
>



Gary Weinhold
Senior Application Architect 

DATAKINETICS | Data Performance & Optimization 

Phone   +1.613.523.5500 x216
Email:  weinh...@dkl.com

Visit us online at www.DKL.com 

E-mail Notification: The information contained in this email and any 
attachments is confidential and may be subject to copyright or other 
intellectual property protection. If you are not the intended recipient, you 
are not authorized to use or disclose this information, and we request that you 
notify us by reply mail or telephone and delete the original message from your 
mail system. 

Reply via email to