Administering
The EC for Venafi gateway address space does not issue ESM commands, so it does not require elevated permissions for ESM. The address space requires sufficient authority to access the data sets in the started task JCL procedure, listen on the TCP port specified and make TCP connections to the EC for Venafi agent systems.
The EC for Venafi agent address spaces require the necessary ESM permissions to issue RACDCERT and RLIST commands for a RACF system, or GENCERT and GEREQ commands for a Top Secret or ACF2 systems.
Starting and stopping the product
As the system administrator, you can start and stop the BMC AMI Enterprise Connector for Venafi product.
To start the gateway
Use a standard MVS start command:
S productName
Replace productName with the name of the member that you copied from the RSMSAMP library to your procedure library, for example, RSSPROC.
The gateway does not require a cold or warm start option.
To start the agents
Use a standard MVS start command:
S productName
Replace productName with the name of the member that you copied from the RSMSAMP library to your procedure library, for example, RSSPROC.
A COLD start is not recommended, but if it is required, you must delete and re-allocate the VSAM cluster.
The state information is automatically deleted during BMC AMI Enterprise Connector for Venafi processing so you do not need to cold start the gateway.
To stop the product
Stop the product in one of the following ways:
- Use a standard MVS purge command:
P productName - Use a SHUTDOWN command through the MVS MODIFY (F) command:
F productName,SHUTDOWN
Replace productName with name of the member that you copied from the RSMSAMP library to your procedure library, for example, RSSPROC.
No confirmation of the command is required and the product address space normally closes down immediately.
If the product does not shut down in a typical way, you can use a cancel command: C productName