IBM Support

SA was not starting as AUTO1 was not running AOFRANTL

Troubleshooting


Problem

Customer had modified some settings within CNMSTGEN and was not seeing SA start up. There was no AOF617I message issued.

Resolving The Problem

After reviewing the customer's style sheets and the netlogs from before the changes and after the changes we saw DSI220i being issued for a lot of autotasks causing the default of AUTO1 to be used. The problem occurred because the customer had some autotask statements for POLICY and AUTOIP in CNMSTGEN that specified INITCMD of NODATA. These should have resolved to AUTOAON but AUTOAON was not defined. Since AUTO1 became the default task, NetView used the last INITCMD instead of the INITCMD that was set in AOFSTYLE. Once AUTOAON was defined, SA was started since AUTO1 now ran AOFRANTL as the initial command.

[{"Product":{"code":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"--","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"3.3;3.4","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Document Information

Modified date:
08 August 2018

UID

swg21673973

Page Feedback