Host Environment Commands › ADDRESS AP Commands › AP NMFind—Invoke Notification Manager

AP NMFind—Invoke Notification Manager

The ADDRESS AP NMFIND invokes Notification Manager on an MSF-connected CA Automation Point system. You tell it:

• Whom to contact
• What to tell the person
• What action to take when the person responds

Note: NMFIND is a not a synchronous process, therefore CA OPS/MVS does not wait for an action or an answer from CA Automation Point.

The ADDRESS AP NMFIND command has the following format:

ADDRESS AP 'NMFIND 
SYSTEM(apsysname)
   {GROUP(group)|NAME(name)|PERSON(person)}
  TELL(tell-text)
  [ACKNOWLEDGEOPS(OPShost,string)]
  [ACKNOWLEDGEAP(string)]
  [ATTACHMENT(filename)]
  [FAILUREREXX(failure-action)]
  [MTUP(string)]
  [USERPARMS(parameter1(value1)[parameter2(value2)])]
  [DEBUG(YES|NO)]'

SYSTEM

Defines the 1- to 8-character MSF name of the CA Automation Point system. A system ID cannot exceed 8 bytes.

GROUP

Defines the 1- to 32-character name of the group to contact.

Mutually exclusive with NAME and PERSON.

NAME

Defines the 1- to 32-character name of the group or person to contact.

Mutually exclusive with GROUP and PERSON.

PERSON

Defines the 1- to 32-character name of the person to contact.

Mutually exclusive with GROUP and NAME

TELL

Sends the message to the specified group, name, or person.

The length of the TELL string is subject to restrictions on the local CA Automation Point machine. For details, see the CA Automation Point documentation.

ACKNOWLEDGEOPS

(Optional) Sends an acknowledgement message with string included in the message text to the OPSLOG and AOF of the CA OPS/MVS system whose MSF ID is OPShost.

string must be a character string with a maximum length of 240 characters.

ACKNOWLEDGEAP

(Optional) Writes an acknowledgement message with string included in the message text to the CA Automation Point Message window specified by apsysname. CA Automation Point rules may therefore be written to react to acknowledgement messages.

string must be a character string with a maximum length of 240 characters.

ATTACHMENT

(Optional) Identifies the user-supplied file that is to be attached to any notifications made using a method defined to send mail using the SENDMAIL command. The file must be accessible from the Notification Server that is issuing the SENDMAIL command. Only one file can be specified per NMFIND request. The maximum length of the filename (including path) is 512 characters.

Example:

ATTACHMENT('c:\Documents and Settings\All Users\Application Data\Application\ error.log')

Note: To use the ATTACHMENT option, you must configure the Notification Server to use SMTP for mail requests.

Default: There is no default.

FAILUREREXX

(Optional) Identifies the name of the REXX program to run on the CA Automation Point system when every action in the call tree fails. This value must be a valid CA Automation Point REXX program name and should be consistent with length capabilities of the AP REXX PROGRAM keyword, allowing enough space for the directory name.

MTUP

(Optional) Specifies which method the Methods to Use Profile (MTUP) uses for a particular instance of an NMFND notification request.

Valid values are:

profile

Any combination of method type codes B through W.

A

All method types specified for all active schedules.

Default: A

For more information on the MTUP operand, see the chapter “Notification Manager Commands” in the CA Automation Point Reference Guide.

USERPARMS

(Optional) Specifies a list of method parameters whose associated values override any like-named parameters during the execution of NMFIND.REX. The length of the USERPARMS list is subject to restrictions on the local CA Automation Point machine.

For example, assume this operand is defined as follows:

USERPARMS( SubjectText(UAP notification using NM))

The USERPARMS-defined value overrides the parameter SubjectText for any method using that parameter.

Default: There is no default.

DEBUG

(Optional) Indicates whether debugging messages are to be generated.

Valid values are:

YES-Generate debugging messages.

NO-Do not generate debugging messages.

Default: NO

Example: ADDRESS AP NMFIND

Suppose you have determined that when a particular JES is having difficulties, you need to NMFIND the lead JES systems programmer, Jim Smith. The CA OPS/MVS rule that trapped the error message from JES would contain this clause:

ADDRESS AP “NMFIND SYSTEM(SYS47) PERSON('JIM SMITH') TELL('JES is down')”

Notification Manager uses its database technology (which is based on a relational database) to determine the communications method it should use to contact Jim Smith, based on the time and day. Notification Manager proceeds to contact Jim Smith and relay the message according to the following:

• If the contact method was the CA Automation Point voice technology, Jim receives a phone call at the phone number pointed to by his notification schedule.
• If the contact method was the numeric pager, Notification Manager pages Jim with the numeric message consisting of the phone number that he needs to call and an ID number that will authorize him to receive the voice message.

If the contact method was the alphanumeric pager, the message appears on the pager that belongs to Jim along with a phone number and ID that he can use to obtain any information that was not sent through his pager. For instance, the message to be sent might be longer than the length supported by his paging service.