The following is an example of creating a procedure for starting the BCM Web API server, and an example of changing the login procedure to directly start the BCM Web API server.
To start the BCM Web API server by using a procedure
Create a procedure (procedure name: YKAPIPRC) to be specified for the statrcmd key in the request body when starting the BCM Web API server, and then link the dataset storing YKAPIPRC to the DD name SYSPROC of the login procedure.
The following is an example specification.
PROC 3 PRM1 PRM2 PRM3
ALLOC F(SYSEXEC) SHR REU DA('HDSYK.Vnnnnnn.HDSYEXET') ----(1)
ALLOC F(YKLOG01) SHR REU DA('USERID.BCMLOG.YKLOG01') ----(2)
ALLOC F(YKLOG02) SHR REU DA('USERID.BCMLOG.YKLOG02') ----(2)
ALLOC F(CLIDFLTS) SHR REU DA('USERID.BCMAPI.CLIDFTLS') ----(3)
YKAPISRV &PRM1 &PRM2 &PRM3 ----(4)
FREE(CLIDFLTS)
FREE(YKLOG01) ----(5)
FREE(YKLOG02) ----(5)
(1) Link the REXX Exec library to the DD name SYSEXEC.
(2) Allocate the BCM log dataset to the DD names YKLOG01 and YKLOG02. If BCM logs are output to the system logger service, this specification is not necessary. For details about BCM logs, see the Hitachi Business Continuity Manager User Guide.
(3) Allocate the dataset created in Creating a default parameter dataset to the DD name CLIDFLTS.
(4) Specify the BCM Web API server name: YKAPISRV.
(5) If you use the system logger service, this specification is not necessary.
To change the login procedure to directly start the BCM Web API server
Add the following DD statements to the login procedure:
//SYSEXEC DD DISP=SHR,DSN=HDSYK.Vnnnnnn.HDSYEXET ----(1) //CLIDFLTS DD DISP=SHR,DSN= USERID.BCMAPI.CLIDFTLS ----(2)
(1) Specify the REXX Exec library for the DD name SYSEXEC.
(2) Allocate the dataset created in Creating a default parameter dataset to the DD name CLIDFLTS.
The BCM log dataset cannot be shared. Therefore, if you want to share the login procedure, we recommend that you use the system logger service for BCM logs.
For details about BCM logs, see the Hitachi Business Continuity Manager User Guide.