Removing an SAG
If you no longer need an SAG and want to remove it:
- Delete its MQ connection and all its SI endpoints
and message partners:
- Open the CLI for the instance (for example, INST1) and
DNFSYSOU:
dnicli -i INST1 -ou DNFSYSOU -s DNFSAGCFG - Issue the following commands to determine which of the
following are still associated with the SAG. For example, for SAG1:
- SI endpoints
lep -sag SAG1 -src cfg - Message partners
lmp -sag SAG1 -src cfg - MQ connection
lmqc -sag SAG1 -src cfg
- SI endpoints
- You must delete an SI endpoint before you can delete its corresponding message partner. Use the following configuration commands to delete from the SAG the objects listed in the previous step:
- To receive an event after the changes are deployed,
register to receive events from the SAG. If the deployment fails,
the event contains information about the possible causes:
- If an error occurs in the DNFSAGCFG service you get an error response and the actions are rolled back.
- If the error occurs in the SAG Add-on, you get an error information in the event log and the response that the deployment failed. The changes in FTM SWIFT are committed. The error message number provides the information whether it was issued by the DNFSAGCFG service (DNFG....E) or by the SAG Add-on (DNFS....E).
- Approve and deploy DNFSYSOU and the SAG from which you
removed the SI endpoints and message partners. This requires access
rights provided by both the SAG configuration administrator (SagCfgAdmin)
and system configuration administrator (DniSA) roles. To do this,
issue the SAG configuration app (approve) and dep (deploy)
commands. If dual authorization is disabled, you can skip approving
the changes and immediately deploy them. For example, to approve and deploy the SAG configuration for SAG1, enter:
approve -sag SAG1 deploy -sag SAG1The deployment of the SAG configuration data is not immediate. It can take several minutes after you issue the dep (deploy) command.
For a description of the commands' syntax and parameters, see approve and deploy.
- Open the CLI for the instance (for example, INST1) and
DNFSYSOU:
- Issue the stop command to the DNFSAGOP service for
DNFSYSOU. For example, to stop SAG1, which was configured in the instance
INST1, enter:
For more information about this command, see stop.dnicli -i INST1 -ou DNFSYSOU -s DNFSAGOP stop -sag SAG1 - To delete and remove the configuration entities
for the SAG that you no longer need, run the dnfcgrem script.
Note: This script and the scripts used in the following steps are stored in the following directory:For example, to delete and remove the configuration entities for the SAG SAG1, enter:
For more information about this path, see Setting environment variables for the CLI. To view the contents of the scripts, use a browser to open the scripts. Running the scripts requires access rights provided by both the SAG administrator (SagAdmin) and system configuration administrator (DniSA) roles. Run the scripts in a z/OS® UNIX command shell.$DNI_PATH/run/bin
This script is described in dnfcgrem.dnfcgrem SAG1 - If dual authorization is enabled, you must approve the
changes to the configuration entities of the SAG. If dual authorization
is disabled, you can skip this step and immediately deploy them.
To approve the changes, run the dnfcgapp script:
This script is described in dnfcgapp.dnfcgapp SAG1 - Deploy the changes by running the dnfcgdep script:
This script is described in dnfcgdep.dnfcgdep SAG1