Manually Managing an Instance of the CA7 Server for AAI

After creating, configuring and implementing an instance of the CA7 Server for AAI, you can manage the start up and shut down either automatically (recommended method) or manually. This topic describes the tasks you need to perform if you must manage the instance manually.

 

In IMS use the M - Menu for Instance option to open the CA7 Server for AAI Instance Request Menu, where you have the following options:

• Browse CA7 Server for AAI Log

  The Browse CA7 Server for AAIAAI Log option opens a browse view into the CA7 Server for AAI active STC log messages. The Browse View option will use the output access API that was selected at installation time, either SDSF or Sysview.

  This option works only when the CA7 Server for AAI instance is active and the output access API is available to the user.

• Definition Data Delivery Request

  Usually the CA7 Server for AAI instances are configured to deliver definition data automatically at the time(s) that you have specified when you configured the CA7 Server for AAI settings. However, if a refresh of one or more of the CA7 definition data files is required, you can request it using this option. For more information, see Defining the CA7 Server for AAI Settings.

  This option is only available if the CA7 Server for AAI instance is active. Use it to open the Definition Requests menu where you can select the type of definition data that you want to request:

  

  1. ALL

     Select this option to start the Asynchronous Definition Data Delivery (ADD) child process. This process generates and delivers a complete set of the CA7 definition data files to the target location on the AAI Server.

  2. Job

  3. Dataset

  4. Calendar

  5. Timezone

  Select options 2 to 5 to issue a request where the ADD process generates and delivers that specific definition data file.

• Event Recovery Checkpoint Override

  Once the CA7 Server for AAI instance has successfully generated and delivered the event data file to the AAI Server, the current date and time values are saved to the yourHLQ.SRVRCKPT dataset. This is used during a WARM start for recovery purposes. The recovery process generates all the event data from the checkpoint date up to the current date. For this purpose it uses both the Active and the History CA7 log files. It delivers the data to the AAI Server before the Cyclic Event Data Delivery process begins.

  To recover data from a different start date and time, either earlier to recover additional data or later to limit the amount of data to be recovered, use option 3 from Instance Menu and change the checkpoint date and time values accordingly.

  This option is available only when the CA7 Server for AAI is not active.

  

  Note:

  If the checkpoint date and time is older than the oldest log entry on the History CA7 log files, this creates a "partial recovery" scenario. When this occurs, to avoid gaps in data sent to AAI, the server will fail by default.

  If you want to override the default behavior and allow partial recovery of event data, you must set ALLOWPR=Y inside the server STC proc as follows:

  

• CA7 Server for AAI Shutdown Request

  Usually, the CA7 Server for AAI instances are configured to start and stop the Primary STC automatically. However, on some occasions, you might want to shutdown a CA7 Server for AAI instance manually. Use this option for that purpose.

  This option is available only when the CA7 Server for AAI STC is active.

  For information about automating startup and shutdown of the server, see the related section in Automating an Instance of the CA7 Server for AAI.

See also:

• Implementing an Instance of the CA7 Server for AAI
• Configuring an Instance of the CA7 Server for AAI
• Automating an Instance of the CA7 Server for AAI