OpCenter GUI Failed to prepare update packages, and the button is greyed out.
We have never been able to use OpCenter client updates.
We’ve gone through the steps in the 8.1.007 release notes
* Command routing works from hub to spoke and spoke to hub.
* Every server has a FILE class, and half have a directory class pool.
* Every server has an HLA and LLA set.
* Most of our clients to use cad with passwordaccc=generate
We’ve gone through the dependencies in opcenter help, which is mostly the same.
We have tried deleting the DEPLOY nodes and letting them re-replicate.
Protect: TSM1>q act begind=-1 endd=today msgno=3759
02/07/23 08:00:31 ANR3759E An error occurred during the replication of client update packages from node IBM_DEPLOY_CLIENT_UNX to the monitored server, TSM2. The return code is 18. (PROCESS: 1612)
02/07/23 08:00:31 ANR3759E An error occurred during the replication of client update packages from node IBM_DEPLOY_CLIENT_WIN to the monitored server, TSM2. The return code is 18. (PROCESS: 1613)
Reset the remote clients that are failing
TSM2: DEL FI IBM_DEPLOY_CLIENT_UNX *
TSM2: DEL FI IBM_DEPLOY_CLIENT_WIN *
TSM2: remove replnode IBM_DEPLOY_CLIENT_UNX server=TSM1
TSM2: remove replnode IBM_DEPLOY_CLIENT_WIN server=TSM1
TSM2: remove node IBM_DEPLOY_CLIENT_UNX
TSM2: remove node IBM_DEPLOY_CLIENT_WIN
Reset deploypkgmgr – not really needed
SET DEPLOYPKGMGR off
SET DEPLOYREPOSITORY /sp/software/octemp/downloads/
SET DEPLOYMAXPKGS 4
SET DEPLOYPKGMGR on
HELPS – The underlying hidden command that does the sync.
refresh pkg clean=no startnow=yes
Once this processes, the button turned blue.
Asked IBM to address this because if there are multiple spokes, failure of one spoke should not block the others.