About cookies on this site Our websites require some cookies to function properly (required). In addition, other cookies may be used with your consent to analyze site usage, improve the user experience and for advertising. For more information, please review your options. By visiting our website, you agree to our processing of information as described in IBM’sprivacy statement. To provide a smooth navigation, your cookie preferences will be shared across the IBM web domains listed here.
Some of this is already available:
CANCEL SESSION ALL
CANCEL RESTORE ALL
CANCEL REQUEST ALL
CANCEL REPLICATION
CANCEL EXPIRATION
IDENTIFY DUP FILEPOOL NUMPROC=0
We're still stuck on CANCEL EXPORT (have to put in a name)
These processes have to be cancelled one at a time:
* BA STG
* RECLAIM
* CONVERT
* MIGRATE
* MOVE
* RECONCILE
* AUDIT
* REPAIR
* SHRED
* CHECKIN
* CHECKOUT
etc etc.
There is still no way to cancel a RUN script.
If the database is on SSD, it may be faster to HALT and restart TSM.
Externally, this could be done in a variety of ways, including:
dsmadmc -id=ADMIN -pa=ADMIN -dataonly=yes "select 'can proc',PROCESS_NUM from processes" \
| dsmadmc -id=ADMIN -pa=ADMIN -dataonly=yes -tab
However, that still does not prevent the next commands in a RUN script from starting.
There are messy ways to work with that too:
serial
select * from SESSIONS where CLIENT_NAME="ADMINSUPERCANCEL"
if (rc_ok) exit
parallel
/* some code here */
serial
select * from SESSIONS where CLIENT_NAME="ADMINSUPERCANCEL"
if (rc_ok) exit
Having both of these internal to ADSM / TSM / Protect would be a long-desired goodness.
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=81517 is similar to this RFE.
it would be nice to have a cancel process command by process name. IBM has implemented a cancel replication and expiration commands.
why not cancel process commands for all the other process types?