CAIENF Best Practices › Installation Considerations › Files

Files

CAIENF requires a parameter file to startup. This file should be customized to meet the needs of your site. Some best practices concerning these parameters are:

• If you do not wish to record CAIENF events, then make sure to specify NODB AND RECORD(NO) within the CAIENF Parameters.
• If you need to record events, then make sure to have RECORD(YES) specified.
• It is fairly likely that CA products that perform event checkpointing require only batch job activity. You can cut down on the number of events that are recorded on the CAIENF database and thus cut down on system overhead by filtering events that are recorded to the database. This is done with the CAIENF parameter SELECT. Unless you have specific reasons not to, run with the following SELECT statements:

  SELECT(JOBINIT,JOBNUM,EQ,J*)
  SELECT(JOBTERM,JOBNUM,EQ,J*)
  SELECT(JOBPURGE,JOBNUM,EQ,J*)
  SELECT(STEPTERM,JOBNUM,EQ,J*)
  

• If you are running a CA product that is interested in data set close events and thus has you turn on recording of data set close events, you should also add the following CAIENF parameter statement:

  SELECT(DSCLOSE,JOBNUM,EQ,J*)    
  

• There can be a very large number of data set close events on a system and CAIENF processing of these events does carry some overhead. CAIENF has the SCREEN parameter that filters out events at event creation time. Screening out events is not recommended unless CA Support has determined that it is in your best interest to do so since all CAIENF product listeners will be affected, not just products that use CAIENF event checkpointing. In addition CAIENF and CAICCI listen for some events. With that caution however, there is a data set close SCREEN setting that is typically safe. Data set close events can be screened out for non-update events and thus lower overhead on the system. The following statement can be added to CAIENF parameters:

  SCREEN(DSCLOSE,ACCESS,EQ,INPUT)
  

• You may also have some started tasks set up that have a system maintenance or utility purpose. If these started tasks or jobs are run frequently and you know that they have no relationship to any CA product, you can add SCREEN statements to keep their activity outside of CAIENF. For example, you could have the following SCREEN statements:

  SCREEN(JOBINIT,JOBNAME,EQ,JRDR)
  SCREEN(JOBTERM,JOBNAME,EQ,JRDR)
  SCREEN(STEPTERM,JOBNAME,EQ,JRDR)
  SCREEN(JOBPURGE,JOBNAME,EQ,JRDR)