Hello

we are working in a Proof of Concept  ,with a full LPAR copy  scenario .

 Till now we've used the versioning feature for each dataset( alcckd DiskName -ve)

 . After the system shutdown I've decided to commit all the changes . After closing the system we have run the commit for each dataset  ( alcckd DiskName -vc)  when the system was already stopped ( after the awsstop command)

After this operation we are no more able to Run the IPL . We are receiving the IEA793A  message ( NO DUMP DATASET AVAILABLE FOR DUMPID-001 JOB(*MASTER*) , USER DUMPDS COMMAND OR REPL

 ( the resident dataset is accessible via ListVtoc command)

Do you have any suggestions ?

the steps that I did was exactly 

alcckd DiskName -ve
start
awsstop
alcckd DiskName -vc
alcckd DiskName -vi ( everithing seemd to be ok)

Unfortunately I  didn't use

alcckd DiskName -rs  ( in order to displays the CKD device attributes) so I cannot be sure about a wrong status of this disk

The problem has been solved thanks to a new copy of the RESIDENT volume from the mainframe .. so it seems that somethig has been corrupted during the alcckd DiskName -vc command  but I cannot be sure of this

Hi Giuseppe, we may need additional investigation about this corruption. As you are very experienced zD&T you certainly have used the correct process. If you haven't done yet, could you pls open a PMR and send us the required documentation.

Tks.