Description:
The first time you perform a deployment to an LPAR it goes successfully without getting a validate conflict prompt for dataset names. Performing a second deployment for the same product, using the same methodology to a different LPAR that is not sharing DASD with the first LPAR results in a validate conflict prompt for the datasets name.
Is this okay, why should it prompt for a possible overlay when the second deployment is to a different LPAR that doesn't share DASD with the first LPAR?
Solution:
The deployment will always prompt in this situation whether the LPARs are sharing DASD or not. This is just to get the user to acknowledge that there is a potential for a overlay even if the LPARs are not sharing DASD. In fact, CSM doesn't check to see whether they are sharing DASD or not.