Performing Initialization Processing

Initialization processing may not be required for simple automation procedures.

Initialization processing is responsible for:

• Setting up any error trap routines.
• Identifying the automation procedure by setting a local variable either explicitly or at execution time. This step makes it simpler to code routines that log messages and send notifications.
• Declaring the global variables, such as common and task global variables, that are used for subsystem definition values in the automation procedure.

  See Global Variables for descriptions of global variables.

• Checking whether debugging is on.
• Issuing debugging messages, if debugging is turned on.
• Validating the automation procedure call.

  This step can help prevent an operator from calling the automation procedure inappropriately. Automation procedures can also be validated using command authorization checking methods provided by NetView or an SAF product.

• Saving NetView message parameters. This step is necessary if your automation procedure uses the NetView WAIT statement and you need to access the original message text or control information.

For more information on coding automation procedure initialization sections, refer to Example Automation Procedure, to IBM Z® NetView Customization Guide and to IBM Z NetView Automation Guide.