The GR32 or GR64 register TYPECHECK checking is based on the descriptions in Principles of Operation. In this case, the operations are generally described as inserting selected bits into a 64-bit register, and I presume whoever defined them (before my time in the HLASM team) used that as the basis of the typecheck definition.
You can of course use the more limited GR type to at least check for a register, but if there is any reference to the GR32 or GR64 type in an assembly the enhanced checking is applied which requires the correct type. I'm not aware of any previous RFE asking to modify the way TYPECHECK works in this sort of case. The original intention was to extend TYPECHECK features to make it much more powerful, including checking operand types, but so many limitations and special cases were identified that the enhancements would give too many spurious warnings when applied to existing code and would therefore be of very limited value. However, I think that it might be feasible at least to quietly modify the register TYPECHECK processing for a few instructions such as these to allow either 32 or 64. I'll add that to our suggestions list. Jonathan Scott, HLASM IBM Hursley, UK
