The syntax for this command is as follows:
NOTIFY nn [n] NOTIFY nn [n] + <email address> [, <email address>....] NOTIFY nn + <email address> [, <email address>....] NOTIFY nn - NOTIFY ALL NOTIFY ALL [n] NOTIFY ALL [n] + <email address> [, <email address>....] NOTIFY ALL + <email address> [, <email address>....] NOTIFY ALL -
This command allows the user to enter one or more email address(s) to monitor system and report generates for the specified system nn or to globally (ALL) monitor system and report generates for all the systems . The email address(es) must be valid as validation checks are not performed.
System specific email address(es) takes precedence over any global email address(es). The following generate events are notified via an email:
system/report selected by client for generate
system/report generate started on Host
system/report generate completed ok {- warnings}
system/report generate failed
system/report generate waiting (suspended)
system/report generate resumed
system/report generate cancelled
system/report generate failed prior/during FTP xfer
system/report generate queued (no generate workers)
system/report generate queued (delayed generate)
system generate verify task looping
The generate events that are notified can be restricted by supplying a notify level ([n]) where the value of n means:-
0 – notify all generate events (default)
1 – notify start and end of generate events
2 – notify generate warnings (non fatal errors)
3 – notify generate exceptions (queued, waiting etc)
4 – notify generate errors only
The selected level [n] implies notification of events for level [n] and above. For example, setting level 2 notifies events for levels 2, 3, and 4. The notify level can be set for Global (ALL) or individual system nn (overrides Global).
Use the '+' option to assign email address(s) for system nn or ALL. This replaces all previously assigned address(s). You can assign upto 255 bytes of email address(s).
Use the '-' option to remove all nominated email address(s) for system nn or ALL (Global).
Use without the '+/-' options to see the current email address(s) associated with system nn or ALL (Global).
Email messages can also be initiated from the Developer client. When the Host deployment phase is 'Waiting', a dialog box stating the details of the reason is displayed on the client. An email can be sent from here by replying with EMAIL <message>. The <message> text is sent to the email address(es), if any, defined for this system or the email address(es), if any, defined for ALL (global) . The email is ignored if no email address(es) are defined .
You must install and configure the MCP EMAIL utility on the MCP Host. Before using NOTIFY, the e-mail address must be defined in either the EMAIL attribute of the corresponding USERDATA record or in the associated CANDE/MYOPTIONS file.
For a failed system or report generate, the associated Appl Bld generate log entries are included in the final notification email.
For a failed system or report generate, when ERRORDIAG is enabled, the diagnostic error file is sent as an attachment in a notification email.
You can also set default global email address(es) via a /ini file entry of notify=<address>,<address>,. Only a single line entry is supported via the /ini file. Any addresses supplied in the /ini file are overridden by a subsequent NA ... NOTIFY ALL +...
entry. You can also set the default global email notify level via a /ini file entry of level=<0 through 4>
By default, the email sender is no-reply@unisys.com. This can be overridden by adding an entry in the /INI file, sender=<your sender address>
Refer INDEX command to determine the appropriate nn index value.