all LUNs get assigned to FAs, it's just with dynamic lun masking VMAX is masquerading actual FA address. For example back in the days Redhat boxes could only see LUNs with addressed that did not exceed 0FF (256). Well if you were sharing FAs with other hosts you could use up 256 addresses pretty fast. So you could have a host with only 4 LUNs but because 0-0FF addresses on the FA were already used up by other hosts, you would not be able to add any more LUNs to the host with only 4 LUNs. By using dynamic lun masking, LUNs mapped to FA address 105 could be visible to hosts as host LUN 5. Does it make sense ?
When I run "symacess show view view_mask_name -sid 123" There will be a colume called "host luns" . This lun can be specified, or taken by default. However, when I run "symcfg list -address -FA 07E -P 0 -sid 123", there will be a colume called "LUN", this lun is assgned by FA, as I understand.  My questions: 1.  Without specifying the dynamic lun address when I create the  view mask, by default, would this host lun be the same as the lun assinged on the FA port?  2.  Are these two type of luns conceptualy the same or what are differences?  Thanks!
Host lun and luns assigned on FA port