Starting a backup controller

Before you begin

Before starting the backup controller for the first time, ensure that you have:

Set the same name for the primary and backup subsystems, and that the VSAM data set names are the same on both controllers.
Allocated the required GDG root (sample EQQPCS13) on both the primary and backup controllers. For detailed information about how to allocate the GDG root, see Allocating non-VSAM data sets.
Customized the required transfer and restore procedures on both controllers. For detailed information about how to customize procedures, see Step 4. Using the EQQJOBS installation aidthe section about using the EQQJOBS installation aid in HCL Workload Scheduler for Z: Planning and Installation.
Sent all the databases from the primary controller to the remote site where the backup controller is located, by running the following procedures:
- EQQSJS1
- EQQSJS2
- EQQSENDB
You must send also the JOBLIB and, on the remote site, make any changes required to run the jobs on the remote destination environment.
Restored the databases on the backup controller, by running the following procedures:
- EQQRJS1
- EQQRJS2
- EQQRESDB

About this task

To start the backup controller for the first time, complete the following steps:

Start the backup controller.

The backup controller establishes a connection with the primary controller and sends a synchronization request. The EQQMLOG of the backup controller shows the following messages:

EQQN135I SYNCHRONIZATION CHECK REQUEST SENT TO PRIMARY CONTROLLER      
EQQN135I BACKUP CONTROLLER                                             
EQQN135I CP RUN NUMBER     : 00000000         TOD:                     
EQQN135I LTP RUN NUMBER    : 00000000         TOD:                     
EQQN135I LAST JT SEQNO     : 00000000

The primary controller starts a synchronization process to send the required plans. The EQQMLOG of the backup controller shows the following messages:

EQQN136I SYNCHRONIZATION ANSWER RECEIVED FROM PRIMARY CONTROLLER:      
EQQN136I PRIMARY CONTROLLER                                            
EQQN136I CP RUN NUMBER     : 00000010         TOD: CD875679A8CF7B20    
EQQN136I LTP RUN NUMBER    : 00000025         TOD: CD87833C781C1FA1    
EQQN136I LAST JT SEQNO     : 000001AC                                  
EQQN136I CP WILL BE SENT   : Y                                         
EQQN136I LTP WILL BE SENT  : Y                                         
EQQN136I JT WILL BE RESENT : N

The primary controller starts sending plans, and the corresponding restore is performed on the backup controller:

EQQN164I LTP  TRANSFER COMPLETED SUCCESSFULLY (EQQSENLT  STC00622)    
EQQN168I LTP  RESTORE STARTED (EQQRESLT)                               
EQQN164I CP1  TRANSFER COMPLETED SUCCESSFULLY (EQQSECP1  STC00620)    
EQQN168I CP1  RESTORE STARTED (EQQRECP1)                               
EQQN164I NCP  TRANSFER COMPLETED SUCCESSFULLY (EQQSENCP  STC00621)    
EQQN168I NCP  RESTORE STARTED (EQQRENCP)                               
EQQN165I LTP  RESTORE COMPLETED SUCCESSFULLY (EQQRESLT  STC00623)      
EQQN165I NCP  RESTORE COMPLETED SUCCESSFULLY (EQQRENCP  STC00625)      
EQQN165I CP1  RESTORE COMPLETED SUCCESSFULLY (EQQRECP1  STC00624)

To check that the restore process for all the plans has completed, look for the following message in EQQMLOG:
```
EQQN134I RE-SYNCHRONIZATION PLANS RESTORE COMPLETED
```

On the primary controller, to check that all data was sent successfully, look for the following messages in EQQMLOG:

EQQN164I LTP  TRANSFER COMPLETED SUCCESSFULLY (EQQSENLT STC00622) 
EQQN164I CP1  TRANSFER COMPLETED SUCCESSFULLY (EQQSECP1 STC00620) 
EQQN164I NCP  TRANSFER COMPLETED SUCCESSFULLY (EQQSENCP STC00621)