GDPS

Showing 184 of 8255

The GDPS shutdown process of multiple LPARs today are done in parallel, however the monitoring of the progress of each LPAR is done serially. Since the shutdown is done in parallel, the checking should also be done in parallel so if a timeout occurs the GEO288A message is issued at the time of the timeout and not serialized.

To speed up the shutdown process and be notified of potential timeouts sooner so they can be actioned.

over 1 year ago in GDPS 0 Future consideration

Increase the maximum supported SafeGuarded Copy captures beyond the current 500

The current limit of 500 SGC captures means we have to have a trade-off between the frequency of captures, and the retention period of those captures. We have currently have a company-wide requirement for 7 days retention, which means we are limit...

over 1 year ago in GDPS 3 Future consideration

14 VOTE

OOS tracks in MGM3SITE recovery region

When production is failed over in the RECOVERY region, we will be in Global copy from C-B. When we are ready for failing back to main region, we run the MGM3SITE_GOHOME_CAS_RS1_RS1. During that, it will ensure EMPTYOOS. However, if there are lot o...

over 1 year ago in GDPS 6 Planned for future release

8 VOTE

LCP SGC support in MGM3SITE in RECOVERY region

When we are in failover state where production runs from recovery region, we can't take any LCP captures. We would like the ability to use GDPS/LCP to take a SGC capture in MGM 3-SITE topology when the production is failed over in the Recovery reg...

over 1 year ago in GDPS 6 Planned for future release

2 VOTE

FCWITHDRAW FORCE option for unreachable devices

GDPS Metro does not allow doing a GEOPARM config which removes devices if they are related to an existing FC relationship. Normal procedure is to remove that relationship using DASD FCWITHDRAW prior to that config. This scripts deletes, both FC re...

over 1 year ago in GDPS 2 Future consideration

36 VOTE

Checking connections between GDPS K-systems defined in GEOGROUP by GDPS Monitor I

GDPS has the ability that work in conjunction with Kp-systems, Kg-system, and Kr-system, such as the MGM3SITE and MGM4SITE procedures. To run the procedure, it is mandatory to establish connections between K-systems defined in GEOGROUP. But curren...

over 1 year ago in GDPS 0 Future consideration

3 VOTE

GDPS CA UI filter for the workload components

When Displaying the workload components in the UI for the workload , Ability to filter only the lines with status active,

over 1 year ago in GDPS 4 Future consideration

3 VOTE

Query and Set the Fence status of Db2 IMS and VSAM for GDPS CA workload

This is will be a useful command to query the fence status of the databases, before the switch process, Also ability to set fence / unfence the databases to put it back in a right state so the next workload switch will work without failure

over 1 year ago in GDPS 4 Planned for future release

25 VOTE

CopyOnce: too much frequent

As written in the manual "ZG246758" the restore procedure after an HYPERSWAP (scheduled or unattended) foresees 3 actions:1- START secondary on Master of MM;2- MGM3SITE_RESTORE;3- MGM3SITE_SWAP The 9th step of MGM3SITE_RESTORE_MT_RS* procedure for...

almost 2 years ago in GDPS 1 Is a defect

52 VOTE

Check primary DASD devices on all lpars with TEST CONFIG

Currently GDPS dasd TEST CONFIG checks, on the system on which the DASD Config is run (ie. master K), if the primary devices are accessible. With this idea we would like to extend this check, performed on the master K, to all the lpars of the rele...

almost 2 years ago in GDPS 6 Future consideration

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use