|
Jan Well some more investigation today revealed that: the as-svrmap job was actually ending after a connection attempt; I followed this further and checked the client connect or something job (QSADRCVSD) which revealed that the /QIBM/ProdData directories in the IFS don't have anything in them on the restored system. Yep, nothing at all - pretty clearly an error as far as I can tell. So either what happened to you happened to us (V4R5 system and I have seen some similar things that I usually attribute to operator problems) or the restore was dodgy. There are some things about the restore that are starting to seem a little fishy, so we are just going to do it again. I guess thats the purpose of testing these things anyway. Truth be known I probably stayed with this a little longer than I otherwise would have because it seemed worth trying to work out what had gone wrong from the testing point of view, and because I ad one guy report something similar. I was curious as to whether there was a way to fix it without recovering again. Thanks to all the others who reponded PS The cricket hasn't gone well for you guys recently ;) ('m an Aussie) Regards Evan Harris > > HI, > >You did a SAVE 21, as mentioned. On what version was this? I have had to >assist a customer to resolve the following: > >They did a SAVE 21. On V4R2M0, I think they were. >Restored all from IPL D, onto their DRP site. >Could connect neither local nor remote desktops to the 400. > > I checked on the system and all appeared fine. It was after running > CHKPRDOPT >on 5769TC1 that we noted errors. It appears that either the SAVE 21 or the >restore of the system had somehow whcked or corrupted TC1. Reloaded TC1 from >CD and after that it was running like a dream again. > >HTH. > >Cheers. > >Jan Megannon.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.