Address Space Statements (CA 7 Server for iDash)

This topic describes statements available for the CA 7 Server for iDash address space.
cwac7e121
This topic describes statements available for the CA 7 Server for iDash address space.
  •  
    EVENTS
    (Required) Specifies whether CA 7 Server for iDash supports CA 7 Event Subscription. This setting should not be changed from the ONLY value. If it is, CA 7 Server for iDash emits an error and fails to initialize.
    Default:
     No default
    •  
      ONLY
      CA 7 Server for iDash publishes CA 7 events to subscribers. This value is the only valid choice.
  •  
    EVENTSOURCE
    (Optional) Specifies the transport mode for CA7LOG events. For more information about selecting a transport mode for CA7LOG events, see Interface with CA7LOG Events.
     
    Default:
     ENF
    The transport mode applies to all instances of CA7ONL monitored by this copy of CA 7 Server for iDash.
    •  
      ENF
      Listens for CA7LOG events that are generated through CAIENF.  ENF is the default.
    •  
      LOGR
      Reads CA7LOG events from the CA Common Logger managed log stream that is dedicated to the monitored instance.
     
    Example: EVENTSSOURCE statement
     
    EVENTSSOURCE(LOGR)
  •  
    EXTRACTPATH
    (Required) Specifies the absolute USS path name where 
    CA WA CA 7 Edition
     data extract files are placed.
    Specify a USS pathname from 1 to 60 characters.
    Default:
     No default
    Example: EXTRACTPATH statement 
     
    EXTRACTPATH(/u/users/myjfm/extractpath)
  •  
    FACILITY
    (Optional) Specifies the resource class to use on security calls in CA 7 Server for iDash for all XML queries. The value can range from 1 to 8 characters.
     Any value that is set takes effect on the next authorization call made.
     
    Default:
     NONE
    •  
      NONE
      Bypasses all resource authorization checks in CA 7 Server for iDash, including checks for access to CA 7 Server for iDash. This value is the default.
    •  
      YES
      Uses CA7JFM as the resource class on the security call.
      Example: FACILITY statement 
       
      FACILITY(NONE)
  •  
    JFMNAME
    (Optional) Specifies a name to associate with the CA 7 Server for iDash job or started task that is running.
    The value can range from 1 to 32 characters in length.
    The value can contain one or more of the following valid characters: period (.), dash (-), underscore (_), 0-9, a-z, and A-Z.
    Default:
     If not provided, a default in the following format is generated:
    JFM.jobname
    •  
       
      jobname
       
      Identifies the JOBNAME (or STC name) of the CA 7 Server for iDash that is running.
      Example: JFMNAME statement 
       
      JFMNAME(JFM.CAIJFM1)
  •  
    LOGLEVEL
    (Optional) Specifies whether to activate diagnostic logging and at what level.
    Use the LOGLEVEL setting and command only the direction of 
    Broadcom Support
    .
    Default:
     0
    •  
      0
      Performs no diagnostic logging. This value is the default.
    •  
      1
      Performs the least amount of diagnostic logging.
    •  
      2
      Performs more diagnostic logging.
    •  
      3
      Performs all logging except memory and data structure management.
    •  
      7
      Performs all logging except memory management.
    •  
      8
      Performs the most amount of diagnostic logging.
     If LOGLEVEL contains a value greater than zero, allocate the CAJFLOG DD in the CA 7 Server for iDash startup JCL, or no diagnostic logging occurs.
     
    Example: LOGLEVEL statement 
     
    LOGLEVEL(0)
  •  
    SAFRING
    (Required if SSLRINGTYPE(SAF) is specified; otherwise, optional) Specifies the name of the SAF keyring.
    The name is specified in the following format:
    userid/keyring
    •  
       
      userid 
       
      Indicates a 1 through 8 character user ID.
    •  
       
      keyring
       
      Indicates a 1 through 8 character key ring name.
    The current userid that is associated with the CA 7 Server for iDash job or started task is used when the userid is omitted. The user must have READ access to the IRR.DIGTCERT.LISTRING resource in the FACILITY class when using a SAF key ring that the user owns. The user must have UPDATE access to the IRR.DIGTCERT.LISTRING resource in the FACILITY class when using a SAF key ring that another user owns.
     Certificate private keys are not available when using a SAF key ring that another user owns.
    If this parameter is specified, the SSLRINGTYPE(SAF) parameter must also be specified.
    Examples: SAFRING statement 
     
    SAFRING(KEYRING1)
    SAFRING(MYUSERID/KEYRING2)
  •  
    SSLCERTLABEL
    (Optional) Specifies the label of the certificate in the key ring that is used to authenticate the application.
    Specify a string from 1 to 58 characters.
    If this parameter is specified, the SSLRINGTYPE parameter must also be specified.
    Default:
     If not specified, the default certificate from the key ring is used. 
  •  
    Example: SSLCERTLABEL statement 
     
    SSLCERTLABEL(
    My certificate label
    )
  •  
    SSLRINGTYPE
    (Optional) Indicates that System SSL is supported in the CA 7 Server for iDash job or started task and specifies the type of key database to use.
    Default: No default. If SSLRINGTYPE is not specified, SSL is not supported in the CA 7 Server for iDash.
    •  
      KDB
      Indicates the use of an HFS key database and the password stash file. The KEYDB and STASH DD statements in the CA 7 Server for iDash startup JCL specify the path to the USS files where the key database and the password stash file reside.
    •  
      SAF
      Indicates the use of a SAF key ring. The SAFRING parameter is required. 
     
    Example: SSLRINGTYPE statement
     
    SSLRINGTYPE(KDB)
  •  
    STATICNODE
    (Optional) Defines a replacement value for the z/OS System Name (SMF ID), which is typically acquired programmatically. This value is used when the host LPAR for CA 7 and CA 7 Server for iDash can change, but you want CA Workload Automation iDash to treat the events as though they were coming from the same CA 7. This setting is rarely needed. The value can be any combination of 4 characters, including alphabetic, numeric, and special characters.
    The identifier can range from 1 to 4 characters in length.
    The value can contain any valid EBCDIC or National character permitted by IBM as part of a System Name.
    Default:
     If not provided, the IBM System Name is used.
    Example: STATICNODE Statement 
     
    STATICNODE PRD1