System Automation for z/OS 4.1 does not complete initialization

Resolving The Problem

Add the definitions for NetView operators AUTINIT1 and AUTINIT2

Refer to the SA/zOS 4.1 Planning and Installation publication:
Topic: Introduction of automated functions INITOPR1 and INITOPR2
SA z/OS initialization now runs on the dedicated automated functions INITOPR1 and INITOPR2.

These functions are represented by the NetView operators AUTINIT1 and AUTINIT2.

Add the automated functions INITOPR1 and INITOPR2 to the AOP policy entry hosting the automation base operator entry.
For more information, consult best practice policy *BASE and AOP entry BASE_AUTOOPS.
The DSIPARM definitions AUTINIT1 and AUTINIT2 are provided by the product by default.

However, if you placed private versions of NetView parameter members into your local DD DSIPARM, please review your local libraries and adapt the necessary definitions for AUTINIT1 and AUTINIT2 in your customized parameter members.
If you run in a SAF-based environment, add the definition for NetView operators AUTINIT1 and AUTINIT2. Therefore, consult the SINGSAMP member INGESAF and use the operator definition statements for these tasks.
Prior to SA z/OS 4.1, several NetView functions have been moved away from the autotasks AUTO1 and AUTO2 to prevent SA z/OS initialization delays.
Inspect your local NetView style include members and look for 'function.autotask.xxx'
statements. Look for these statements in the NetView delivered CNMSTYLE member and decide whether you want to keep it as is in your local NetView style include members or if you want to stick to the NetView provided by default.
In the latter case, remove the 'function.autotask.xxx' statements from your NetView style sheet include members. If necessary, change AUTO1 and AUTO2 in your private command authorization table to AUTINIT1 and AUTINIT2 appropriately.