This API procedure function call retrieves information about an EventView rule set or message rule definition in the knowledge base.
If you make this call from an NCL procedure, ensure that you share the &ZRE-prefixed variables, for example, by adding the following statement before the call:
&CONTROL SHRVARS=(ZRE)
Syntax
This API procedure function call has the following format:
$REDBAPI SERVICE=GET
[NAME=rule-object-name]
CLASS=cc
RULESET=ruleset-name
Operands
This API procedure function call has the following operands:
Specifies that information about a definition is to be retrieved from the knowledge base.
Specifies the object name of the message rule definition for which information is to be retrieved.
The name is contained in the &ZRENAME variable returned by a previous $REDBAPI SERVICE=CREATE call.
This operand is not required if you are retrieving information about a rule set definition.
Specifies the two-digit identifier of the EventView class to which the definition belongs.
Specifies the rule set class.
Specifies the message rule class.
Specifies the name of the rule set for which information is to be retrieved or the name of the rule set that owns the message rule for which information is to be retrieved.
Return Variables
This API procedure function call returns the following variables:
Contains the returned message.
Contain the returned knowledge base information about the specified rule set or rule.
Return Codes
Return codes indicate the success or failure of processing. This API procedure function call returns the following return codes in the &RETCODE variable:
Indicates that processing was successful.
Indicates that processing failed.
Indicates that error occurred in the call syntax.
Example: Retrieve Information About a Message Rule
This example retrieves information about a message rule (class 94) previously created in the SUPP rule set:
&CALL PROC=$REDBAPI PARMS=(SERVICE=CREATE,…) … &JAA992I=&ZRENAME … &CALL PROC=$REDBAPI + SHARE=(ZRE>) + PARMS=(SERVICE=GET,+ NAME=&JAA992I,+ CLASS=94,+ RULESET=SUPP)
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |