How to cancel a hanging FFOR online reorg job which issues a system completion code, but cannot be cancelled by using common z/OS operator commands

Document ID : KB000011014
Last Modified Date : 14/02/2018
Show Technical Document Details
Question:

If an FFOR job ABENDS while running as BMP execution (e.g. during database unload), the job might be left in a "hanging" state, which cannot be cancelled by common z/OS operator commands (CANCEL, FORCE etc.).

Answer:

If the abending job is "hanging" and cannot be cancelled by z/OS operator command, follow these steps to abend the FFOR job:

  1. determine the region number '#' the FFOR/BMP job is running in, by answering the current IMS message reply with IMS command '/msgnumber/DIS A'
  2. stop region number '#' reported in 1. by answering the current IMS message reply with IMS command '/msgnumber/STO REGION # ABDUMP'

 

Before the same FFOR job can be restarted (after the error which caused the previous ABEND has been corrected), the DOPT PSB name used for this execution has to be re-started by using IMS command '/STA PGM psbname', and the DOPT PSB load module should be manually deleted from the DOPT ACBLIB being used on this online system (to avoid an U0456 error as a result of inconsistent information being left from the previous ABEND).