rev message (iseries) 10.1 rev msg 000 datasheet.pdf• e-mail templates etc., across machines and...

Data Sheet - iSeries - ENT 10.1 www.revsoft.com1 of 14

REV MESSAGE (iSeries)Message Management & Control made easyREV MESSAGE allows you to Manage and Control messages on anyplatform in your Enterprise to increase:• Throughput, • Accuracy, • Efficiency.

Base Model is native on all platformsRun REV MESSAGE natively on: • AIX, • AS/400 • HP-UX, • LINUX, • SOLARIS, • WINDOWS.

The REV MESSAGE Base Model is native on all platforms and does NOTrely on a central database.

All Base Models operate independently but can communicate with multipleFocal Points.

View, Control & Manage all Servers & other platformsThe Windows interfaces allow you toView, Control and Manage theMessages for any servers that arerunning REV MESSAGE.

Drag and Drop:• Environments, • Filters,• Instructions, • Warnings,• Host Instructions, • SLA’s• Calendars • Rules,• E-mail templates etc.,across machines and platforms.

See Messages the instant they appear in your NetworkThe Windows interfaces allow to immediately see (colors) and hear(sounds) the status of Messages on any servers, in your Enterprise, that arerunning REV MESSAGE.

Utilizing push technology theinformation is pushed from thehost(s) directly (and immediately)from the servers directly to theWindows application.

Sounds can be configured to notifyyou of the Message types on anysystem in your Enterprise.

Major Features• Load and Go,• Powerful Filters,• Occurrence Rules,• Run Scripts based onOccurrence range,• Audit,• Undo changes,• Un Delete,• Environments,• Shadowing,• Ack Info messages,• Service LevelAgreements (SLA’s),• Security/LDAP,• Substitution values,• E-mail templates,• Message Consoles,• Fully Networked,• Push Technology,• Multiple Focal Points,• Histroy Logs,• What IF processing,• Instructions,• Knowledge Base,• Investigate,• Multiple Dispatchers,• Service multiplemachines & platforms,• Restricted State,• Notify Focal Points inRestricted State,• Scheduled outages,• Be notified if Poweror Machine Fails.

http://www.revsoft.com/

REV MESSAGE (iSeries)


Load and GoAs soon as REV MESSAGE is loaded you can start the REVMESSAGE ‘engine’ and you will immediately begin processingmessages as REV MESSAGE installs with a ‘base’ set of Filtersthat are normally used in an OS/400 operational Environment.e.g. CPF0907 (Serious storage condition may exist. PressHELP.) is sent by the OS/400 as an informational message theREV MESSAGE standard filter generates an Inquiry Message withthe same message details.

CPA5305 (or CPA3138) Record not added member is full issent when a message is full and the batch job will not do anyprocessing until this message is replied to. The standard REVMESSAGE filter will reply with an I for occurrences 1 though to 5 of this message (within the Job).

Powerful and Flexible FiltersMessage Filters are the key element in how REV MESSAGE processes the messages and this must beas powerful and flexible as possible.

Every message that is sent has what we term ‘vital statistics’ that allows REV MESSAGE to identify themessage such as:• From Job, • From User, • From Program,• Message Identifier • Date sent, • Time sent,• Message File name, • Message File library, • Severity,• 1st Level Message Text, • 2nd Level Message Text, • Message Data,• Message Type, etc.,

Each Filter in REV MESSAGE attempts to match the message vital statistics with the defined Filter vitalstatistics.

To make the REV MESSAGE Filters more powerful and flexible you can select any of the message vitalstatistics by:• Being equal or Not Equal to:

• *ANY value,• Specific value - e.g. Job is EOD,• Generic value - e.g. Job is EO*,• Contained value - e.g. Job matches *EOD*,• Element within a List,A List contains elements that contains a Lower value and an Uppervalue - so if a List element had a Lower value of EOA and an Uppervalue of EOZ - then EOD would be selected,• Meeting a definition of a Rule,A Rule contains lists of constraints such as-IF EO was found in position starting in position 1 through 10,AND D was found in position 3 only,then EOD would be selected.



REV MESSAGE (iSeries)User Defined Occurrence RulesEvery time a Message is processed the occurrence number of the message is assigned and Scripts canbe executed based on the Occurrence number.

The default Occurrence Rule is based on: • Message Identifier, • Message Type, • Number/User/Job, • 1st Level Message Text & Message Data.

User Defined Message Occurrence Rules can be defined to be based on: • Message Identifier - based on Value (*ANY, Specific, Generic or Contains), List or Rule, • Message Type - based on *ANY, *INQ, *DIAG etc., • Number/User/Job, • 1st Level Message Text or areas within the 1st Level Message Text, • 2nd Level Message Text or areas within the 2nd Level Message Text, • Message Data or areas within the Message Data.

Run Scripts based on Occurrence rangeWhen a message is processed Scripts can be executed that can contain: • Replies, • Commands to be executed.

Scripts are also defined to be executed for: • The occurrence of the message during the Job.

This can be defined as -• ANY, or • Range of From and To occurrence numbers.

• Time range, bounded by Start and End time, the message is issued.

e.g. The message CPA5305 is issued when a File is full.With the standard Filters shipped with REV MESSAGE for AS/400 message CPA5305 will:

• On first occurrence only of the message:• Send reply ‘I’,• Send an informational message to QSYSOPR detailing the Job andthe File name that has been incremented,

• On occurrences 2 thru 5:• Send reply ‘I’,

Should the message be received for a 6th occurrence it will not beautomatically replied to and appear in Red on the Message Consoles.

Should you wish to change the number of occurrences it is as simple as updating the Script processingoptions - no lengthy code or loops to create.




AuditThe Audit function in REV MESSAGE logs every change that is made to a Message Filter or any of itscomponents.

These details are logged in the REV MESSAGE database and canbe reviewed.

The details are simple to follow with 6 possible images:• Add new, • Delete,

• Update (Before), • Undo Update,

• Update (After) • Undo Delete.

The audit details will even log the: • Domain\System\User if the change is made in the Windows applications, • If the change was made by - • Keyboard - Manual Entry, • REV VIEW - Send from another machine, • Drag & Drop - Drag and Drop in the Windows interface.

Undo ChangesWhen updates are performed to the Message Filter or any of thecomponents the: • Before image - Data prior to the change, • After image - Data after the change,are captured and this does allow for the component to be ‘rolled back’ of‘Undo’ the change.

The Undo action is also registered in exactly the same manner and in thatcase you can actually ‘Undo the Undo’ should the need arise.

Un Delete Message Filters or ComponentsWhen a Message Filter or any of the components are deleted all the details are registered.

The Undo functionality allows you to: • Un Delete a complete Message Filter all its original components, • Un Delete a Message Filter component.



REV MESSAGE (iSeries)EnvironmentsEvery Message Filter defined to REV MESSAGE can optionally beregistered or belong to an Environment.

All Environments are user defined.

The shipped Environments are: • *BASE, • TEST.

ShadowingTo ensure that all Message Filters, and their components, are the identical on all LPAR’s or machines REVMESSAGE has built in ‘shadowing’ functionality.

Shadowing is performed by REV MESSAGE using REV VIEW as the transportmechanism to maintain the synchronization of the Message Filter and all thecomponents.

All Shadowing is registered within the Audit facility.

Shadowing can be selected by Environment - which will ‘shadow’ all theMessage Filters for the selected Environments - by ‘checking’ the Shadowedbox.

When an Environment is selected for Shadowing you can then select the Hoststhat it will be shadowed to.

Any new Message Filters, that are defined to a Shadowed Environment, willautomatically be ‘shadowed to the Networked system(s).

Any updates or deletions of message components are then automaticallyshadowed to defined systems.

This is very similar to the shadowing functionality built in to REV SCHEDULER for High Availability JobEvents.




Acknowledge MessagesMessages can be acknowledged as this can be defined to stop anescalation process.

Informational messages can also be defined to require anacknowledgment.

Any Informational messages that require acknowledgment will: • Appear in Pink in the message consoles, • Be displayed in Pending mode of the message console.

Multiple messages can be acknowledged at one time by following the standard Windows list selectionprinciples of using: • Shift key to define boundaries, • Control key to select individually.

Message Filter actionsWithin the Filtering actions you can define the following components thatare processed whenever a Message Filter is activated: • Recipients, • Escalation Levels, • Escalation Recipients, • Scripts • Instructions, • Warnings, • Requirements, • Message Queues.

Multiple ways to send messagesWithin REV MESSAGE for AS/400 messages can be forwarded to recipients (Pagers or SMS) and themessage sending can be performed in 2 ways: • Directly from the AS/400 using a modem, • From a networked PC using Message Dispatcher.

Administer Warnings and Service Level Agreements (SLA’s)Within REV MESSAGE for AS/400 you can define Warnings to assist you incomplying with Service Level Agreements (SLA’s).

Warnings can be defined in 2 ways: • Single - which is for a specific Message Filter and only is processed bythis Filter, • Multiple - which is for a group of Message Filters.



REV MESSAGE (iSeries)SecurityUsing REV MESSAGE Security you can define: • Users, • Authorization Groups,who are authorized to: • Command or Menu option, • Selection options from panels.All security is defined by: • User Profile, • *PUBLIC, • User defined Authorization groups..

LDAP Interface SecurityREV MESSAGE now has full support for LDAP (LightweightDirectory Access Protocol) which is an Open Systems protocol to allowprograms to look up information from a server.

In this way LDAP can be a central security repository that will contain thesecurity definitions for some of all of the servers where REV MESSAGE isoperational.

The LDAP Interface can support security checking for both of the: • 5250 Interface or terminal sessions, • Windows Interface.

The LDAP security also supports keyword values for: • *PUBLIC_SYSTEMS - these are Systems other than theSystems specifically defined, • *PUBLIC_USERS - these are Users other than the Usersspecifically defined.

Security PoliciesThere are two security policies available : • *SYSTEM, • * LDAP.

There is also a Tailoring Option that can allow the System policy to override the LDAP policy, and thiscan be set on a system by system basis.

Security violationsAll Security violations are logged and can be displayed by date or date range.

The security violation logs: • Domain, System, User - if from the Window application, • Function that was attempted to be accessed, • Operation that was attempted, • Date and Time of violation, • Policy type - if this value is *LDAP the LDAP server name will also be displayed.




Substitution VariablesEvery messages that is processed is registered within the REV MESSAGE database.

When executing scripts you can use the data from the message processed as a substitution variable andREV MESSAGE will automatically (and transparently) substitute the appropriate data.

Some examples are: • #SYSNAM - this is the System name e.g. ISERIES, • #MSGQ - message queue name e.g. QSYSOPR, • #TIMEM - message time in HH:MM:SS format e.g. 01:15:23, • #MTP - message type e.g. *COMP, *DIAG, *ESC, *INFO, *INQ, • #DATEM - message date in medium format e.g. Fri Oct 13, • #MID - message identifier e.g. CPF0907, • #SEV - message severity e.g. 99.

If message ID CPF9907 (severity 40) was processed from QSYSOPR on system REVSOFT at 16:00:01on 01/01/07 as an informational message (*INFO),

we could create a script that would look like:System - #SYSNAM has received Message #MID which is #MTYP and has severity of #SEV

When this was processed it would be:System - REVSOFT has received Message CPF9907 which is INFO and has severity of 40

E-mail TemplatesSome companies use E-mail as a mechanism to: • Alert personnel of messages, • Use E-mails as audit logs for auditors, • Use E-mails to generate SMS messages rather than modem connection.

Within REV MESSAGE you can create E-mail templates that contain fixed text as well as substitutionvariables.

Subject . . . . System - #SYSNAM has received Message #MID which is #MTYP and has severity of#SEV

Body Text . . . The System #SYSNAM has received #MID. &NThis couldalso be sent to Support on #PGR(SUPPORT,NUMBER) or TechnicalSupport on #PGR(TECH_SUPPT,NUMBER) or even Operations Supporton #PGR(OP_SUPPORT,NUMBER). &NIndividual Number is - #IND withOccurrence Number #OCC. &NReceived by #NBR/#USR/#JOB.&NReceived at #TIMEM on #DATEM,#YEAR. &PFirst Level Text's #MSG.



REV MESSAGE (iSeries)Message ConsolesWhen Messages are detected and processed you need to have a mechanism to control and manage allthe messages and this is performed by the Message Consoles.

There is also a Network Message Console to allow you to control and manage Messages on networkedLPAR’s, machines and other platforms executing REV MESSAGE (eg., AIX, LINUX, UNIX andWINDOWS)

The Message Console will be the panel most used by theoperations personnel within your corporation to control theMessages detected and processed by REV MESSAGE.

There are various Message Consoles to provide varied views andfunctionality for the Local and Network Messages.

To make the Message Consoles more informative the Messagesare: • Displayed on color, • Defined to play sounds, • Pushed to the consoles so the notification is immediate.

Types of Message ConsolesThe Message Consoles are available for: • All Messages detected and processed on the directly connected Servers - this is the Local MessageConsole. • All Messages detected and processed on any networked machines (regardless) of Operating systemthat are running REV MESSAGE and this system is a Focal Point - this is the Network MessageConsole.

Authorization for optionsThe security for options can also restrict what options the user(s)can execute on the Message Consoles.




Fully Networked SolutionREV MESSAGE is a fully networked solutions not only to: • Local Servers, • Remote Servers,but also to other platforms.

REV MESSAGE currently has native messaging software thatruns on: • AIX, • AS/400, • HP-UX. • LINUX, • SOLARIS, • WINDOWS.

Push TechnologyThe Local and Network Message Consoles use Push Technology - where the information is pushed fromthe Host(s) directly to the Windows application software.

Using Push technology : • Eliminates unnecessary polling of machines, • Reduces network traffic, • Display the status immediately the host detects it, • Eliminates manual intervention to detect messages issued.

Multiple Focal PointsAll RevSoft products have been designed and constructed to have: • Multiple Focal Points, • Multiple Focal Points on multiple platforms.

Using this technology you can have - • Multiple major Focal Points on AS/400 for all AS/400, WINDOWS, LINUX and AIX machines, • Single or Multiple WINDOWS Focal Point only for the WINDOWS machines, • Single or Multiple LINUX Focal Point only for the LINUX machines, • Single or Multiple AIX Focal Point only for the AIX machines.

Configurable SoundsThe Local and Network Message Consoles can be configured for sounds to be played based on thedetection of messages.

The Message Consoles can be configured so they: • Automatically update, • Play sounds, • Change colors,whenever a message is detected in your network.



REV MESSAGE (iSeries)Process History Log entriesREV MESSAGE can optionally process History Logs entries (QHST* files).

This allows you to take actions based on: • Changes in System Values, • Objects saved during the day, • Incorrect Passwords entered,etc.,

Archive History Log entriesREV MESSAGE provides the RMARCHLOG command that allows you to translate the History Log entriesinto the corrected field data and then write that out to an archive file.

The History Log archive file can then be viewed, reported on or interrogated by SQL for audit ormanagement reporting purposes.

Use What IF processing to test FiltersWithin REV MESSAGE for AS/400 you can test the Message Filters registered by defining test messages,complete with message text and message data, and running this through the process to identify whichFilters will be used and why they have been selected.

This process also details why Filters were rejected in the process.

View Instructions for message correctionWithin REV MESSAGE for AS/400 you can register Instructions that aredisplayed to the users when viewing the Message Consoles.

These Instructions can be corrective or recovery actions to be taken whena message appears and this can be used in conjunction with theKnowledge Base to provide swift and unassisted message resolution.

Attach Notes & build a Knowledge BaseNotes can be attached to Inquiry Messages as it is replied to and thesedetails are registered in a ‘Knowledge Base’. The Knowledge Base can bereferenced in any of the Message Consoles to guide the user based on theregistered knowledge notes.




Investigate why Filters were selected or not selectedWithin REV MESSAGE you can view the details of any messageprocessed and see why the processed Filter was selected.

This easy to follow panel also displays why other Message Filterswere not selected.

You can then drill down on any Filter and view the registered vitalstatistics (component) for the Message Filter and the actualmessage.

A Message Filter component can be: • Rejected, • Selected, • Passed.

On Line manuals can be referenced by HyperlinksWithin REV MESSAGE for AS/400 you can use a URL in the body of the: • Instructions, • Host Instructions,of a Message Filter.

When the Instructions or Host Instructions are displayed from the MessageConsole on the Windows Client the URL is detected and is displayed andoperates as a Hyperlink.

This Hyperlink allows you to click on it and automatically launch a browserand proceed to that URL location.

Using a URL will allow you to enter text or a URL that will allow you toenable Recovery instructions to be actioned in a short period of time and this will decrease times forproblem resolution.

The decreasing of problem resolution time will give greater throughput and accuracy.

By having your: • Operational Procedures, • Soft copy manuals,on the Intranet or a departmental server will allow them to be accessed via the URL.



REV MESSAGE (iSeries)Send messages via Message DispatcherThe Message Dispatcher is Windows based software that will send messages or e-mails to definedmessage recipients.Message Dispatcher can also: • Check for availability of web sites and IP connections (Routers etc.,), • Be contacted when a connection:

• Fails,• Reconnects,

• All the forwarding network overhead (redials, retried etc.,) are performed on the Windows machine andthere is no overhead on the AS/400. • Message Dispatcher logs the details for the message:

• Number of dial attempts,• Date and time of acceptance by the network,

and these details are forwarded to the AS/400 host and logged with the message.

Message Dispatcher can service multiple HostsMessage Dispatcher can service multiple Hosts, regardless of theOperating System, as long as they are running REV MESSAGE.

In this example Message Dispatcher is monitoring: • GALATEA running RED HAT, • HYPERION running i5OS, • OCEANIA running Windows Server 2003, • PORTIA running AIX, • REVUSA running OS/400,all are running REV MESSAGE.

Multiple Message Dispatcher can be usedMultiple Message Dispatchers can be used concurrently to service different: • States, • Buildings, • Data Centers, • Companies, • Divisions, etc.,




Notify Message Dispatcher for a scheduled outageWhen a scheduled outage is determined (IPL etc.,) REV MESSAGE cannotify Message Dispatcher and that machine will be ‘flagged’ as out for thenotified amount of time.

When the scheduled outage time has expired Message Dispatcher will thenattempt to reconnect and if that fails notification will then be sent.

Be notified if any machine is down or failsMessage Dispatcher will contact you if a machine loses power duringnormal processing times.

You will also be notified if a machine is not operational after an IPL or rebootprocedure.

If an unscheduled outage occurs the system will attempt to reconnect thepredefined number of times (shipped value is 3) and after that the systemwill be flagged as ‘Lost’ and the Lost Systems grid will appear.

When the system is registered as Lost any Termination Messages definedwill be sent out.

Reconnection messages can also be defined so that notification can be made upon the Reconnection of aLost system.

Be notified of Inquiry Messages in Restricted StateREV MESSAGE can still communicate with Message Dispatcher when the machine is in Restricted Stateand you can still be notified on any Inquiry Messages.

Restricted State definitions for the message recipients are referenced for any Restricted State messageprocessing.

Focal Points notified in Restricted StateIf and Inquiry Message occurs when the machine is in RestrictedState all Focal Points will be notified and the message will appear inNetwork Message Consoles.

As the machine is still in Restricted State the messages cannot bereplied to from the Focal Point Network Message Consoles.

When the machine is back in normal service, and REV MESSAGE isoperational, the reply to the message(s) (in Restricted State) will bedetected, processed and forwarded to the Focal Points.

rev message (iseries) 10.1 rev msg 000 datasheet.pdf• e-mail templates etc., across machines and...

Documents