Instead of an ICM, IILH or OILH, you need a branch. I don't see how it's more convenient.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of João Reginato <[email protected]> Sent: Friday, March 6, 2026 6:38 AM To: [email protected] <[email protected]> Subject: RES: [External Sender] Re: Loading the pad byte for MVCL External Message: Use Caution That's why I prefer using MVCLE instead of MVCL -----Mensagem original----- De: IBM Mainframe Assembler List <[email protected]> Em nome de Robin Vowels Enviada em: sexta-feira, 6 de março de 2026 02:20 Para: [email protected] Assunto: Re: [External Sender] Re: Loading the pad byte for MVCL On 06/03/2026 10:45, David Clark wrote: > But what if the length is calculated (not from an equate or L' > attribute) > and is already in the target register? Then use ICM. The main reason for using MVCL is that the length is computed at run time. If the length is known as assembler time, you might use a few MVC's instead of MVCL.
