Previous Topic: NMFIND CommandNext Topic: Special Notes About Emergency Mode Processing


Length of Message Sent

The length of the message that is being sent is limited according to where you issue the NMFIND.REX. The TELL operand holds the message to be sent.

Messages can be sent in three ways:

Sending Messages from Rules

You can issue an NMFIND.REX from Rules using the REXX keyword. The length of the call is limited by the 512-character rule limitation. The template to issue NMFIND.REX from rules is MSGID() REXX(NMFIND.REX NAME() TELL ()), which is 38 characters long. This means the value defined for the TELL operand can be at most 474 characters. The TELL string maximum is reduced by the lengths of the values specified for MSGID and NAME. In addition, the length of any optional NMFIND operands (for example, ASK or FAILUREREXX) that are specified, as well as the lengths of their values, further reduce the maximum length of the TELL operand.

Sending Messages from the Command Line

You can issue an NMFIND from a command line. The length of the NMFIND call is limited to 2048 characters. This is a limitation imposed by the operating system. The template for launching an NMFIND.REX is ASOREXX NMFIND NAME() TELL(). The maximum length of the TELL operand is reduced the same way as described in the section above for Rules.

Sending Messages from Another REXX Program

Larger messages can be sent if the NMFIND is launched from within another REXX program. These NMFIND calls can have a length of up to 30K characters. To send such messages from within CA Automation Point, write the message to a data store that is accessible to the REXX environment. Next, launch a REXX program from Rules. This program should access the stored data, create the NMFIND call, and launch NMFIND.REX.

The basic template to issue NMFIND from another REXX program is CALL NMFIND.REX NAME() TELL(). The maximum length of the TELL operand is reduced the same way as described in Rules above with the specification of additional operands.

Note: The length of the message actually sent by a specific Notification Manager method is limited by the value specified for the MaxMsgLen parameter for the method. The MaxMsgLen parameter is set based on the limitations of the medium that is used to send the notification. This means an NMFIND with a message of 30K can be run, but contacts set up to receive pages will only receive the length of the message defined by the MaxMsgLen parameter. For paging methods, the setting has traditionally been 240 characters.