ASF Installation

This section describes how to set up the ASF environment for the first time. Information concerning upgrading an existing ASF installation is contained in the section Upgrading an ASF Installation.

This document covers the following topics:

Step 1: Customizing Natural

The Natural environment should be customized as follows:

  • The parameter MAXCL must be at least 1500.

  • The parameter MADIO must be at least 512.

  • Ensure that the following data is included in the PARAMETER module of Natural: 

    NTPRM ....
   CSTATIC=(AOSASM,...)
NTFILE ID=181,DBID=???,FNR=???          ASF-DATA (File 1)
NTFILE ID=182,DBID=???,FNR=???          ASF-PROFILES (File 2)

    The DBID and FNR of ID=181 must be the database ID and file number into which the dataset ASFvrs.SYS1 was loaded.

    The DBID and FNR of ID=182 must be the database ID and file number into which the dataset ASFvrs.SYS2 was loaded.

  • If you plan to use the Con-nect API feature, ensure that the following additional data is included in the PARAMETER module of Natural: 

    NTFILE ID=251,DBID=???,FNR=???               CON-NECT Files

    The DBID and FNR of ID=251 must be the database ID and file number of the file which contains the CON-NECT interface modules.

  • ASF uses the module AOSASM. AOSASM must be linked to the Natural nucleus and also to the Natural Batch nucleus, since ASF can run online as well as in batch mode. Please make sure that the Adabas Online Services are installed (both Batch and Online) before using ASF. For information on how to install Adabas Online Services see the installation notes for that product. Ensure that the Link Job for Natural is modified appropriately

  • Assemble and link the Natural parameter module.

  • Re-link both Online and Batch Natural with this new parameter module.

Note:
The modifications in the parameter module are essential for both Online Natural and Batch Natural.

Step 2: Customizing Adabas

The ADARUN parameter LFP must be set to at least 100 000, otherwise the ASF evaluation reports cannot run.

Step 3: Loading ASF System Files

(Job I050, Step 4100 and 4101)

Note:
Follow these instructions for first-time installation only! For an upgrade installation, see the appropriate description in the section Upgrading an ASF Installation.

The files ASFvrs.SYS1 and ASFvrs.SYS2 are delivered on the installation medium in Adabas unload format.

Load these system files with LOAD function of the Adabas load utility ADALOD:

  • ASFvrs.SYS1 (ASF-DATA).

  • ASFvrs.SYS2 (ASF-PROFILES).

You can use the following ADALOD parameters to save ISNs and disk space:

  • ISNREUSE=YES

  • DSREUSE=YES

Step 4: Loading Programs and Messages

(Job I061, Step 4100)

Use the INPL utility to load the ASF programs and messages into the Natural system file. The programs and messages are in the dataset ASFvrs.INPL. All messages start with "ASF" and are application specific.

Refer to the Natural Administration documentation for further information about usage of this utility and its parameters.

Please check the reports produced to ensure that no errors have occurred.

Step 5: Setting up User Security

If you are using Natural Security, you must define the group ASFGROUP, containing the names of all users permitted to use ASF. Additionally, one user must be defined as the Administrator. This group must be linked to the ASF application. When you subsequently run ASF, and select the option U (User Maintenance) in the main menu, the names which you have defined in the Natural Security group ASFGROUP will be displayed. You must then grant or deny permission to the users to modify Store Profiles, to modify Evaluation Profiles, to store data, or to run evaluations.

You can copy the following modules from the SYSSEC library to SYSASF:

  • NSC---O

  • NSCDA

  • NSCDU

  • NSCLU-G

Alternatively, you can add the library "SYSSEC", or any other library which contains these modules, to the steplibs of "SYSASF".

If you are not using Natural Security, then all users who have access to ASF are allowed to access all ASF functions.

Step 6: Creating the user BATCH

For certain batch ASF operations, it is necessary to access the user account "BATCH". You create the account in ASF by typing the command "PROFILE BATCH" in the Direct Command Line. Configure the parameters of the BATCH account as required for your batch operations with ASF (for example, default printer for output reports).

If you are using Natural Security, you must also include the user BATCH in the group ASFGROUP (see the previous step "Setting up User Security"). Then, in the User Maintenance service of ASF, grant permission to BATCH for all functions.

Step 7: Customizing the Workplan

The Workplan is the set of predefined evaluations supplied with the ASF product. If you wish, you can modify or extend the Workplan according to your environment. Refer to the section Workplan: Predefined Evaluations and Reports in the ASF User's Guide for details of using the Workplan.

Step 8: Setting up Con-nect

If you are using the ASF feature to send the output of Critical Reports to CON-NECT cabinets, you must set up the correct CON-NECT environment:

  • You must define a Con-nect shared cabinet named "SYSASF" whose password is "SYSASF".

You must copy the following Con-nect API subprograms from SYSCNT2 to SYSASF:

  • Z-ADD11

  • Z-MAILA

  • Z-ERA11

Furthermore you must copy all Con-nect API subprograms which are called by the subprograms listed above. The names of these subprograms can be found in the Con-nect Application Programming Interface documentation.

If you are using Natural Security, you do not need to copy the Con-nect API subprograms. Instead you can define "SYSCNT2" in the steplibs of the library maintenance of "SYSASF".