To start we are running bot a production (MM) & test (TT) environment of XA (MAPICS).
We have separated the environments by logical partition on the IBM i.
Looking for a way to keep “we” developers out of production, we needed a way
to keep the test environment data current.
To accomplish this we turned to Rockets, iCluster. iCLUSTER
We created 2 refresh (*RFSH) Groups. One for library AMFLIB to AMFLIBT and a second for
our proprietary library RBSLIB to RBSLIBT.
Groups panel in iCLUSTER
We automated the refresh by adding the following 2 commands into one of our Never ending programs (NEP).
This could also have been added as a scheduled job… That said we were able to write RPGLE programs
to monitor and take corrective action(s) which to me was the better solution in this case.
[cc lang=”java”]DMSTRGRP GROUP(REFRESH_TT) BACKUP(DTASTORE) STRAPY(*NOCHG) [/cc]
Notice the group REFRESH_TT is highlighted
the object setup for group REFRESH_TT:
include *ALL files from AMFLIB
Exclude table(s) & Logicals/Indexes;
Opt Group Inc Object Type Library Attr
REFRESH_TT INC *ALL *FILE AMFLIB *ALL
REFRESH_TT EXC JOBACT* *FILE AMFLIB *ALL
REFRESH_TT EXC MZF0RE* *ALL AMFLIB *ALL
REFRESH_TT EXC UJBCTL* *FILE AMFLIB *ALL
We still have to make 2 changes in test once refresh is complete.
1st — change RBSLIB – to RBSLIBT under PowerLink/Enterprises/RockfordBallScrew/User Exits
2nd — change Organization Node to DATASTORE.RBS.TT under Environment/Application Settings/Business Information Services/
Thanks it test environment synced.
We do this every Sunday or on demand if needed.
To see this running – WRKACTJOB SBS(XDMCLUSTER)
look for jobs with name (REFRESH_TT) — HADTUP is the processor job – display that jobs, job log to see where it is in the refresh.
REFRESH_TT DMCLUSTER BCH .0 PGM-HADDASR DEQW
REFRESH_TT DMCLUSTER BCH .3 PGM-HADSFPR DEQW
REFRESH_TT DMCLUSTER BCH .7 PGM-HADTUP DEQW