Recovery Case 3: <tn>_task_is_not_available

There are cases where a BCP internal interface autotask, previously defined as an HWOPERnn task with an SA z/OS AUTOOPS policy entry, cannot be used. In these cases, a task definition problem or a mismatch of your current ACF configuration might be the reason for the problem.

The recovery procedure for this case is as follows:

  1. Verify the AUTOOPS definition statements in your PDB.
  2. Verify that the corresponding DSIOPF statements have AOFPRFHW defined as the operator profile name.
  3. Perform a Build operation after the policy changes.
  4. Activate your policy changes, for example by performing an ACF REFRESH.