• June 30, 2022

Monitor iCluster commands in your batch routines or exits using DMGENEXC

If you have built your own user exits for switching iCluster, or batch CL programs for ending iCluster, you may be wondering …”how can I programmatically monitor for an iCluster command that fails?”. For example for IBM i commands like DLTF you can monitor for CPF2125 and either carry on if it’s unimportant or send a message to the user.

Well you can do the same thing with iCluster commands using the DMGENEXC (Generate command exceptions) command. In your user exit or batch CL program after doing a CHGCURLIB ICLUSTER, issue the DMGENEXC GENEXC(*YES) command before any iCluster commands. Then after each iCluster command that you wish to monitor, monitor for msgid CSI9954 and then either ignore the failure or do whatever you need to do to fix the issue, notify an end user or just end the program.

Here is an example where the DMENDGRP and DMENDNODE commands are being monitored as part of a CL to bring down iCluster before an IPL.

DMGENEXC

iCluster Tech Tuesday 0 Posts

iCluster TechTuesday is a set of posts covering technical tips and techniques to help get the most out of your Rocket iCluster installation.

1 Comments

  • holipaz Reply

    March 13, 2014 at 12:34 am

    Image cannot be loaded when I click on it.

Leave a Comment

Your email address will not be published.