Robin, It depends on if you are doing it once per job (who cares), once per record (well maybe) or once per field (yea, I'm interested).
Chris Blaicher Technical Architect Mainframe Development P: 201-930-8234 | M: 512-627-3803 E: cblaic...@syncsort.com Syncsort Incorporated 2 Blue Hill Plaza #1563 Pearl River, NY 10965 www.syncsort.com Data quality leader Trillium Software is now a part of Syncsort. -----Original Message----- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Robin Vowels Sent: Monday, October 16, 2017 10:03 AM To: MVS List Server 2 <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Subject: Re: One Byte MVC Versus IC/STC From: "David S." <dlstaudac...@gmail.com> Sent: Thursday, December 17, 2015 6:10 AM >> > "... a good reason why small MVCs run slower than LG/STG pairs ... >> > overhead at the beginning of an MVC ... check if the operands are >> > on > 'good' >> > boundaries ... check for operand overlap ... length check ... > [meanwhile] the >> > LG/STG is far on its way. Anyone writing a length-1 MVC instead >> > of an IC/STC would be laughed out of their code review. >> >> Rubbish. >> KISS. >> A move of length 1 is clear and unequivocal. >> And it's only one line. > > Nevertheless, IC/STC is what the newer mainframe compilers generate > for a one-byte move. For the reasons given, it's less work for the > system than an MVC. It's a question of what is easiest and simplest for the programmer. Machines are supposed to do the work for us, not the other way around. Why write two lines when one will do the job? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
