System Software Library NonStop NET/MASTER RMS Management and Operations Guide Abstract This manual describes NonStop NET/MASTER Rule Management Services (RMS), and explains how to manage and operate the product on a Tandem system. This manual is intended for experienced users of NonStop NET/MASTER MS and Tandem systems who need to install and control access to NonStop NET/MASTER RMS, or to develop rules to facilitate the operation of Tandem systems.
Document History Edition Part Number Product Version Earliest Supported Release Published First Second 108106 115415 D30 D30 D30.00 C30.08/D00.00 December 1994 September 1995 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT).
New and Changed Information The following sections in this guide contain new or changed information: Notation Conventions The subsection “Boldface” now precedes the subsection “Underline _.” Section 1 Introduction to RMS Editorial changes only. Section 2 Message Handlers, Timers, Rulesets, and Rules The subsection “Continuity of Message Handler Operation” has been updated. If the Event Management Service Process (EMSP) fails and is recreated, EMSPROC fails and is restarted.
New and Changed Information The subsection “Specifying the Message Action Rule Actions” has been updated. The RMS : System Action panel segment shows the new NCL Queue field. The subsection “Specifying an NCL Queue” is new. It describes how to specify an NCL queue for the message action rule actions. The subsection “Specifying the Message Group Rule Actions” has been updated. The RMS : System Action panel segment shows the new NCL Queue field. The subsection “Specifying an NCL Queue” is new.
New and Changed Information ( GETQUEUED ) procedure call to obtain information about queued rule actions. You can use the RMS DELETE ACTIVE command or the ZRMSAPIN ( DELACTIVE ) procedure call to delete active subjects. The subsection “Displaying the Details of an Active Message Subject and Deleting its Rule Actions” has been updated. The table in Step 2 has information about two new fields: NCL Queue and Region. The table in Step 2 shows two new fields: NCL Queue and Region.
New and Changed Information The following RMS commands have been changed: RMS FREEZE (was formerly called the ZRMSFRZN command) RMS THAW (was formerly called the ZRMSTHWN command) RMS XFER (was formerly called the ZRMSXFRN command) Appendix C RMS Procedure Calls The following RMS procedure calls are new: ZRMSAPIN ( DELACTIVE ) ZRMSAPIN ( DELDELAYED ) ZRMSAPIN ( DELQUEUED ) ZRMSAPIN ( GETACTIVE ) ZRMSAPIN ( GETDELAYED ) ZRMSAPIN ( GETFROZEN ) ZRMSAPIN ( GETQUEUED ) The following RMS procedure calls have be
Contents About This Manual xvii Notation Conventions Section 1 xxi Introduction to RMS What Is RMS? 1-1 Functional Description 1-3 Creating and Maintaining Rulesets 1-4 Testing Rulesets Using Simulated Events 1-5 Controlling Message Handlers and RMS Timers Capturing Message Handler Statistics 1-6 1-5 Message Flow Environments 1-7 External Messages 1-8 Messages to the NonStop NET/MASTER MS Activity Log 1-8 Messages to the OCS Window 1-9 Messages to the Dependent Queues of a Message Handler 1-9 Sect
Contents Section 3 Planning For, Installing, and Managing RMS Planning For RMS 3-1 Installing RMS on Your System 3-1 Default File Locations 3-1 Customizing File Locations 3-2 Securing RMS Files 3-3 Making RMS Operational 3-3 Making RMS Operational During NonStop NET/MASTER MS Startup 3-3 Making RMS Operational After NonStop NET/MASTER MS Startup 3-5 Verifying That RMS Is Successfully Initialized Allocating Default Rulesets 3-7 3-7 Migrating From NonStop NET/MASTER MS System-Level NCL Procedures to
Contents Moving Between Input Fields 4-5 Scrolling 4-5 Scrolling Forward and Backward Scrolling Right and Left 4-5 4-5 Using the Command Prompt and RMS Commands Using the ? Command 4-6 Using the CMD Command 4-6 Using the COPY Command 4-6 Using the FIND Command 4-6 Using the Locate Command 4-6 Using the LOG Command 4-6 Using the REFRESH Command 4-6 Using the X Command 4-7 Using Data Entry Panels 4-6 4-7 Using Action Codes in Selection Lists Getting Online Help in RMS 4-8 4-10 Online Help for RMS M
Contents Specifying the Message Action Rule Actions 5-36 Registering the Message Action Rule as a Member of a Message Group Rule 5-42 Implementing a %INCLUDE Rule 5-44 Implementing a %START Rule 5-45 Implementing a Dynamic Rule 5-46 Adding a Message Group Rule 5-46 Naming the Message Group Rule 5-50 Identifying the Message Group Rule Members 5-51 Specifying a Message to Be Delivered 5-51 Specifying the Message Group Rule Actions 5-55 Using Automatic Retry for Rule Action NCL Procedures 5-59 Adding a Time
Contents Modifying the Control Options of a Ruleset 6-24 Adding or Modifying the Environmental Profile Associated With a Ruleset 6-26 Adding or Modifying the Function Key Settings Associated With a Ruleset 6-28 Deleting the Environmental Profile and Function Key Settings Records Maintaining Comments Deleting Rulesets 6-32 6-33 6-34 Transferring Rulesets Between RMS Databases 6-36 Specifying the Source Database 6-38 Specifying the Destination Database 6-38 Printing Ruleset Reports 6-40 Printing a Deta
Contents Section 9 Controlling Message Handlers and Rules Controlling Message Handlers 9-1 Starting a Message Handler by Using the RMS Panel Interface 9-2 Starting a Message Handler by Using the RMS Command Interface 9-6 Displaying the List of Message Handlers and Their Descriptions 9-8 Explicitly Purging Message Handlers by Using the RMS Panel Interface 9-8 Explicitly Purging a Message Handler by Using the RMS Command Interface 9-9 Implicitly Purging Message Handlers 9-9 Modifying a Ruleset Dynamically 9
Contents Section 11 RMS Variables Ruleset Variables 11-1 Global Variables 11-1 User Variables 11-1 Rule Contents Variables RMS Message Variables 11-2 11-4 Section 12 Base Rulesets BASERULE 12-1 ZCPUDOWN 12-3 ZCPUUP 12-4 ZDEVICEDOWN 12-5 ZSUBDEVDOWN1 12-6 ZSUBDEVDOWN2 12-6 ZEXPANDNOTRY 12-7 ZPATHTCPFAIL 12-8 ZPATHTRMABRT 12-9 ZPATHTRMSUS1 12-10 ZPATHTRMSUS2 12-11 ZSNAXINOP 12-11 ZSNAXNOTRDY 12-12 ZTACLFAIL 12-13 STATSCAP Appendix A 12-15 RMS Messages Looking for Additional Information A-1 Before Con
Contents Appendix B RMS Commands RMS DELETE ACTIVE B-2 RMS DELETE DELAYED B-3 RMS DELETE QUEUED B-4 RMS DISPLAY ACTIVE B-5 RMS DISPLAY DELAYED RMS DISPLAY FROZEN B-8 RMS DISPLAY QUEUED B-9 RMS FREEZE RMS THAW RMS XFER Appendix C B-6 B-11 B-12 B-14 RMS Procedure Calls ZRMSAPIN ( DELACTIVE ) C-2 ZRMSAPIN ( DELDELAYED ) ZRMSAPIN ( DELQUEUED ) ZRMSAPIN ( GETACTIVE ) C-3 C-4 C-5 ZRMSAPIN ( GETDELAYED ) C-7 ZRMSAPIN ( GETFROZEN ) C-10 ZRMSAPIN ( GETQUEUED ) C-12 ZRMSAPIN ( FREEZE ) Z
Contents Figure 4-2. Developing a Ruleset 4-22 Figure 5-1. Ruleset Creation—Panel Hierarchy Figure 5-2. Message Action Rule Addition—Panel Hierarchy Figure 5-3. Message Source Criteria Figure 5-4. Triggering a Message Group Rule Figure 5-5. Message Group Rule Addition—Panel Hierarchy Figure 5-6. Time-Based Rule Addition—Panel Hierarchy Figure 6-1. Rule Addition Using a Model—Panel Hierarchy Figure 6-2. Rule Copy—Panel Hierarchy Figure 6-3.
Contents Tables Table 3-1. xvi &OPTION Values 3-12 Table 5-1. Rule Ranking Elements 5-9 Table 11-1. Rule Contents Variables 11-3 Table 11-2.
About This Manual This manual describes NonStop NET/MASTER Rule Management Services (RMS), and explains how to manage and operate the product on a Tandem system.
About This Manual Where to Go for More Information Section 5, “Creating and Developing Rulesets and Rules,” provides the details on how to create and develop rulesets and rules. Section 6, “Updating and Maintaining Rulesets, Rules, and Command Groups,” describes how to update and maintain existing rulesets, and how to generate reports that you can print. Section 7, “Managing Default Rulesets,” describes how to use, allocate, and maintain default rulesets.
About This Manual Your Comments Invited Guardian Procedure Errors and Messages Manual Install User's Guide Guardian User’s Guide File Utility Program (FUP) Reference Manual This manual is part of the NonStop NET/MASTER manual set. Figure 1 shows the functional breakdown of the NonStop NET/MASTER manual set and its relationship to other Distributed Systems Management (DSM) manuals.
About This Manual Documentation Road Map Figure 1.
Notation Conventions General Syntax Notation UPPERCASE LETTERS The following summarizes the notation conventions for syntax presentation in this manual. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation Conventions General Syntax Notation Underline _ An underlined syntax item in a horizontal or vertical list is the default value. If you do not choose any item in a list, the default value is used. For example: NONE RED Ellipsis ... BLUE TURQUOISE GREEN WHITE PINK YELLOW An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}..
1 Introduction to RMS This section introduces the NonStop NET/MASTER Rule Management Services (RMS) product and explains the concepts and terms used in this manual. The intent of this section is to introduce you to the following: Overview of RMS Functions available through RMS Message flow environments in which RMS can be used What Is RMS? NonStop NET/MASTER Rule Management Services (RMS) is a NonStop NET/MASTER application.
Introduction to RMS What Is RMS? Improve productivity as follows: Routine tasks are performed automatically, reducing the number of tasks that require human intervention. Different messages are selectively passed to operators who perform different functions, presenting operators with less nonessential messages, thus reducing the operator response time. RMS uses rules to determine the message filtering and task automation actions.
Introduction to RMS Functional Description subject, the message cannot trigger any rules. You can thaw a frozen subject to reactivate the messages containing that subject as triggers for the rules. Simulate message flows and system times to test your rulesets. You can capture real messages and save the messages in message sets. You can use a message set as a source of repeatable test messages. Capture statistics on a message handler to see how well the handler is working.
Introduction to RMS Functional Description Control your message handlers and timers. Capture statistics on your message handler so that you can analyze how well the handler is handling the message flow. Creating and Maintaining Rulesets The RMS panel interface allows you to create and maintain rulesets and rules as follows: Create new rulesets. You must create a ruleset before you can implement any rules. Create a new ruleset by copying another ruleset and modifying the copy.
Introduction to RMS Functional Description Testing Rulesets Using Simulated Events The RMS panel interface allows you to test your rulesets against simulated events. If you are testing the ruleset when the ruleset is used with a message handler, you can temporarily change the control options of the ruleset when the message handler starts. If you use the narrative feature of the ruleset, the message handler sends you messages about the ruleset activities.
Introduction to RMS Functional Description Manage the subjects that have triggered rules. For example, you may want to delete certain recovery actions on the subject if you determine that recovery is not possible. Freeze or thaw subjects. You may want to freeze a subject when you plan to perform certain maintenance functions on it. Freezing a subject inactivates the rules for messages containing that subject. Similar messages containing other subjects, however, can still trigger the rules.
Introduction to RMS Message Flow Environments Number of NonStop NET/MASTER MS commands issued Number of NCL procedures started Number of command groups executed Number of time-based rules activated by other rules Number of message group rules triggered Number of messages not affected by a rule Number of times a rule is triggered (also expressed as a percentage of the total number of times rules are triggered) RMS can capture the following statistics on the messages received by a message handler: Total numb
Introduction to RMS Message Flow Environments Figure 1-2.
Introduction to RMS Message Flow Environments Messages to the OCS Window Messages to the Dependent Queues of a Message Handler Through your OCS window, you can view the messages that tell you about your system and network activities. The OCS details of your user ID definition and the profile of the OCS environment determine the messages that your OCS window can receive. You use the message handler as a MSGPROC to process these messages before they arrive at your OCS window.
Introduction to RMS Message Flow Environments (This page left intentionally blank) 1–10 115415 NonStop NET/MASTER RMS Management and Operations Guide
2 Message Handlers, Timers, Rulesets, and Rules This section describes the RMS message handlers, timers, rulesets, rules, and other major elements of RMS. The following sections provide information on how to work with the RMS elements described here: For information on starting and controlling message handlers and timers, see Section 9, “Controlling Message Handlers and Timers.
Message Handlers, Timers, Rulesets, and Rules Message Handlers An MSGPROC message handler executes in an OCS window. When the window closes, MSGPROC terminates. In the event of a failure, MSGPROC does not restart. An INT-type message handler executes in either an OCS window or a background environment. If executing in an OCS window, the handler terminates when the window closes (for example, when the window closes because the user who started the handler logs off).
Message Handlers, Timers, Rulesets, and Rules Message Handlers The message handler processes a received message as follows: 1. If the message is one of EMS0001 through EMS0511 that starts with the word LDEV and if the message comes from the local system, the handler sets the message subject to the name of the device indicated by the message. 2. The handler checks the rules in the ruleset to determine if the message satisfies the triggering conditions in a rule (that is, if the message triggers a rule).
Message Handlers, Timers, Rulesets, and Rules Message Handlers Figure 2-1.
Message Handlers, Timers, Rulesets, and Rules Message Handlers Queuing of Rule Actions RMS queues the following rule actions: issuing a NonStop NET/MASTER MS command and starting an NCL procedure. The message handler invokes separate NCL processes to handle each of these actions. The rule actions are placed on the NCL queue specified in the rule definition. The NCL queue execution limit determines the number of rule actions that can execute concurrently.
Message Handlers, Timers, Rulesets, and Rules RMS Timers RMS Timers An RMS timer is a time-based rule that the RMS timer driver has loaded. You use a timer to perform tasks at specific times under the control of a user specified in the rule. You can set up time-based rules that are loaded when one of the following occurs: RMS initializes. A message handler receives a certain message or certain messages. You explicitly load a time-based rule. You can change the characteristics of a timer dynamically.
Message Handlers, Timers, Rulesets, and Rules RMS Timers Figure 2-2.
Message Handlers, Timers, Rulesets, and Rules Rulesets Rulesets A ruleset contains a collection of rules that define responses to events such as message arrival or time conditions. You must have a ruleset before you can implement any rules. A message handler uses a ruleset to set up its working environment and, in response to incoming messages, as a basis for its actions. The timer driver uses a ruleset as a basis for determining whether a timer action is enabled or disabled when responding to time events.
Message Handlers, Timers, Rulesets, and Rules RMS Rules What statistics should a message handler using the ruleset capture? You can specify the type of statistics to capture for the ruleset. Use the statistics to analyze how your ruleset is operating, and optimize the ruleset accordingly. For example, use the statistics to determine which messages you should suppress or to determine the effectiveness of each rule in the ruleset.
Message Handlers, Timers, Rulesets, and Rules RMS Rules Message Action Rules A message action rule governs how a message handler acts when a message arrives. The identification of the message is either specific or generic (generic identification uses wild-card characters).
Message Handlers, Timers, Rulesets, and Rules RMS Rules Define your own subject for a triggering message. If you define the subject, the state (frozen or not frozen) of the new subject determines if the message triggers the rule. If you do not define your own subject, the state of the original message subject determines if the message triggers the rule. Restrict the triggering message further by implementing your own message validation exit NCL procedure. Dynamic Rule.
Message Handlers, Timers, Rulesets, and Rules RMS Rules Replace the message with a new message and deliver the message line by line or in a panel. You can extract text from the original message and include the extracted text in the new message. Rule Actions in Message Action Rules When a message triggers a message action rule, the rule determines the actions to take. A message action rule can perform the following actions: Issue NonStop NET/MASTER MS commands.
Message Handlers, Timers, Rulesets, and Rules RMS Rules %INCLUDE Rule The %INCLUDE rule is a special type of message action rule that does not act in response to messages. The message handler processes %INCLUDE rules as part of the handler startup sequence. Use the rule to load additional rulesets that the message handler needs to use. The %INCLUDE rule allows you to implement several small rulesets instead of a big ruleset.
Message Handlers, Timers, Rulesets, and Rules RMS Rules Rule Actions in Message Group Rules When the member rules trigger a message group rule, the message group rule determines the actions to take. A message group rule can perform the following actions: Execute a user-specified rule action exit NCL procedure.
Message Handlers, Timers, Rulesets, and Rules Base Rulesets Command Groups A command group contains NonStop NET/MASTER MS commands. You use a command group when you want a triggered rule to issue a sequence of NonStop NET/MASTER MS commands. There can be more than one command group in a ruleset. Only the rules within the same ruleset as the command groups can use the command groups. Base Rulesets RMS comes with two base rulesets that you can use immediately: BASERULE and STATSCAP.
Message Handlers, Timers, Rulesets, and Rules Base Rulesets (This page left intentionally blank) 2–16 115415 NonStop NET/MASTER RMS Management and Operations Guide
3 Planning For, Installing, and Managing RMS This section provides the following information on how to plan for, install, and manage RMS: Planning for RMS Installing RMS on your system Securing RMS files Making RMS operational Verifying that RMS is successfully initialized Identifying users to whom you may want to allocate default rulesets Migrating from NonStop NET/MASTER MS system-level NCL procedures to RMS message handlers Describing what to do when the RMS database becomes full Using the RMS security e
Planning for, Installing, and Managing RMS Installing RMS on Your System The file named RMSPCODE should be in the NonStop NET/MASTER MS distribution panel library $vol.ZNNMPDS, where vol is the name of the volume. Other ZRMSx files (x can be up to four alphanumeric characters) should be in the NonStop NET/MASTER MS subvolume $vol.ZNNMDATA, where vol is the name of the volume.
Planning for, Installing, and Managing RMS Making RMS Operational Securing RMS Files Ensure that the installed RMS files are secured as follows: Files with names of the forms ZRMSxN and ZRMSxP are secured so that users can only read the files. Other ZRMSx files are secured so that users (except the NonStop NET/MASTER MS system user) can only read the files. The NonStop NET/MASTER MS system user (that is, the user that starts NonStop NET/MASTER MS) should be able to both read and write to the files.
Planning for, Installing, and Managing RMS Making RMS Operational Refer to the NonStop NET/MASTER MS System Management Guide for more information about customizing the INIT NCL procedure. Initializing RMS and Activating the EMSPROC Message Handler With the BASERULE Ruleset To initialize RMS and activate the EMSPROC message handler with the BASERULE ruleset, follow these steps: 1. Leave the distributed INIT NCL procedure provided by Tandem in the distribution procedure library.
Planning for, Installing, and Managing RMS Making RMS Operational The following CALL statement from a customized INIT NCL procedure preloads NCL procedures and panel description files, and initializes RMS and activates an EMSPROC message handler with the BASERULE ruleset: CALL INIT(PRELOAD,RMSBASE) The following CALL statement from a customized INIT NCL procedure does not preload NCL procedures and panel description files, but initializes RMS and activates an EMSPROC message handler with the BASERULE rules
Planning for, Installing, and Managing RMS Making RMS Operational Initialized,” later in this section, for information on how to verify that RMS is successfully initialized. 4. When message NNM1005 appears, RMS is initialized and available on your system. Log off from and then log on again to NonStop NET/MASTER MS.
Planning for, Installing, and Managing RMS Migrating From NonStop NET/MASTER MS System-Level NCL Procedures to RMS Message Handlers Verifying That RMS Is After NonStop NET/MASTER MS startup completes, verify that RMS is initialized by Successfully Initialized following these steps: 1. The NCL procedure ZRMSININ, which initializes RMS, starts the timer driver NCL procedure ZRMSTDRN. From OCS, issue the SHOW NCL=ALL PROC=ZRMSTDRN command to verify that the corresponding NCL process exists.
Planning for, Installing, and Managing RMS Managing the RMS UDB File 3. Change the name of the file used in the command for each system-level NCL procedure to ZRMSMGHN (the name of the message handler NCL procedure file). For example, you may have the following statement in your READY procedure: CMD 'SYSPARMS EMSPROC=filename' filename is the name of the NCL procedure that you want to start as an EMSPROC.
Planning for, Installing, and Managing RMS Implementing the Security Exit NCL Procedure to Control Access Implementing the Security Exit NCL Procedure to Control Access RMS uses the NCL procedure ZRMSSECN to control user access to its functions. If you do not want to control access to RMS functions, leave the NCL procedure ZRMSSECN as is. To control access to RMS functions, customize the NCL procedure.
Planning for, Installing, and Managing RMS Implementing the Security Exit NCL Procedure to Control Access b. Check the character reserved in the user installation attributes for the selected RMS option (as indicated by the value of the &OPTION variable).
Planning for, Installing, and Managing RMS Implementing the Security Exit NCL Procedure to Control Access 5. Set the character set reserved for RMS. The following example sets the first character of the User Attribute 2 field to Y: HY-------------------- UMS : User Installation Attributes ----------Page 4 of 5 Command ===> Function=UPDATE The fields displayed below represent user attributes allocated by this installation.
Planning for, Installing, and Managing RMS Implementing the Security Exit NCL Procedure to Control Access Customizing ZRMSSECN Customize the NCL procedure ZRMSSECN as follows: 1. Edit ZRMSSECN and search for the text string gosub .SECCHK. 2. Add */ and /* around gosub .SECCHK as shown below to make the NCL core statement executable (modification is in boldface): /* */ gosub .SECCHK /* - or gosub .NCLCHK */ 3. INSTALLATION ATTRIBUTE SECURITY CHECK USERWRITTEN SECURITY CHECK. Search for .
Planning for, Installing, and Managing RMS Implementing the Security Exit NCL Procedure to Control Access Table 3-1. &OPTION Values (Page 2 of 3) Value RMS Option 1.M 1.C 1.B Start a Message Handler as MSGPROC on RMS : Start Message Handler panel Start a Message Handler in Current Region on RMS : Start Message Handler panel Start a Message Handler in Background Region on RMS : Start Message Handler panel 2.0 Active Message Handler Control on NonStop NET/MASTER RMS primary menu panel 2.S 2.P 3.
Planning for, Installing, and Managing RMS Setting Up User IDs for RMS Table 3-1. &OPTION Values (Page 3 of 3) Setting Up User IDs for RMS Value RMS Option 7.2 7.3 7.4 7.5 Timer Activation Simulation on RMS : Event Simulation panel Capture Message and RMS Activity on RMS : Event Simulation panel Simulate RMS Activity on Saved Message Set on RMS : Event Simulation panel Edit Saved Message Set on RMS : Event Simulation panel 8.0 Statistics Capture on NonStop NET/MASTER RMS primary menu panel 8.S 9.
Planning for, Installing, and Managing RMS Setting Up User IDs for RMS Setting Up a User for BASERULE To use the BASERULE ruleset with a message handler, the owner of the environment that the message handler services must meet certain prerequisites. You must set up the user that uses BASERULE as follows: Ensure that the owner of the environment can receive EMS messages. Set the Receive EMS Messages field in the user ID definition to Y if necessary.
Planning for, Installing, and Managing RMS Limiting Concurrent Rule Actions Limiting Concurrent When a message triggers a rule, RMS can perform specific rule actions. You can limit Rule Actions the number of rule actions that can concurrently execute by defining an NCL queue in which to execute the rule actions. To ensure that the rule actions execute in an NCL queue, follow these steps: 1.
Planning for, Installing, and Managing RMS Customizing BASERULE Customizing If you plan to use the BASERULE ruleset, customize the ZCPUUP and the BASERULE ZTACLFAIL rules to reflect the requirements of your system. It is strongly recommended that you also customize the ZCPUDOWN rule to change the volume on which the CPU dump files reside to a volume other than $SYSTEM. The $SYSTEM volume is reserved for system files, and you do not want to use up space by filling $SYSTEM with dump files.
Planning for, Installing, and Managing RMS Customizing BASERULE 4.
Planning for, Installing, and Managing RMS Customizing BASERULE 6. Press ENTER. The following RMS : Ruleset Copy panel appears: SDPL----------------------- RMS : Ruleset Copy ---------------------Page 1 of 1 Command ===> Copy from BASERULE to .... F1=Help F2=Split ˚˚˚˚˚˚˚ F3=Copy F9=Swap F12=Cancel 7. Specify the name of the ruleset to create. The name must be unique, and consist of one to eight alphanumeric characters, @, #, or $ (for example, BSRLCUST). 8.
Planning for, Installing, and Managing RMS Customizing BASERULE Customizing the BASERULE Rules Customize the ZCPUDOWN, ZCPUUP, and ZTACLFAIL rules by modifying them as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance.
Planning for, Installing, and Managing RMS Customizing BASERULE 4. Select option 2 to access Display/Modify/Delete/Add With Model as on the following panel: SDPL-------------- RMS : Message Action Rules Maintenance -------------ZRMSUPDP Select Option ===> 2 1 2 X - Add Using Defaults - Display/Modify/Delete/Add With Model - Exit Selection Key .... ˚˚˚˚˚˚˚˚˚˚˚˚ Opt 2 - Blank or partial key for list.
Planning for, Installing, and Managing RMS Customizing BASERULE Note If you do not select the ZCPUDOWN rule in Step 5, skip Steps 7 through 9. If you do not select the ZCPUUP rule in Step 5, skip Steps 10 through 12. If you do not select the ZTACLFAIL rule in Step 5, skip Steps 13 through 15. 6. Press ENTER. 7.
Planning for, Installing, and Managing RMS Customizing BASERULE Press F8 four times to page to the following RMS : System Action panel: SDPL------------------------ RMS : System Action --------------------Page 5 of 6 Command ===> Command Text ..... NCL Proc Name .... Exec Cmd Group ... Submit Actions ... Activate Timer ... Set Variables .... Load Ruleset ..... NCL Exit Name ....
Planning for, Installing, and Managing RMS Customizing BASERULE Press F8 four times to page to the following RMS : System Action panel: SDPL------------------------ RMS : System Action --------------------Page 5 of 6 Command ===> Command Text ..... NCL Proc Name .... Exec Cmd Group ... Submit Actions ... Activate Timer ... Set Variables .... Load Ruleset ..... NCL Exit Name .... OPSYS SEND TACL PUP /IN $SYSTEM.STARTUP.
Planning for, Installing, and Managing RMS Customizing BASERULE Press F8 four times to page to the following RMS : System Action panel: SDPL------------------------ RMS : System Action --------------------Page 5 of 6 Command ===> Command Text ..... NCL Proc Name .... Exec Cmd Group ... Submit Actions ... Activate Timer ... Set Variables .... Load Ruleset ..... NCL Exit Name ....
Planning for, Installing, and Managing RMS Operational Considerations 21.
Planning for, Installing, and Managing RMS Operational Considerations As a general rule, configure NonStop NET/MASTER MS processes with relative priorities in the following order (from highest to lowest): 1. 2. 3. 4. 5. 6. 7. Security exit processes GMM processes NCP processes BK processes NC processes EM processes IS and MS processes As a general rule, configure the following processes between NC processes and EM processes with relative priorities in the following order (from highest to lowest): 1. 2.
Planning for, Installing, and Managing RMS Operational Considerations The number of NCL utilities and applications that are expected to be running at the same time that RMS is processing recovery actions For further information on the SYSPARMS NCLUMAX parameter, refer to the NonStop NET/MASTER MS Command Reference Manual.
4 Getting Started This section helps you to get started with RMS. It describes the features that facilitate your use of the product.
Getting Started RMS Menu Hierarchy Figure 4-1 shows the hierarchy of the RMS menu panels. Figure 4-1.
Getting Started Accessing RMS Functions From the NonStop NET/MASTER RMS primary menu panel, you can access the following RMS functions: Start a message handler (option 1). Control the operation of a message handler (option 2). Control the operation of a timer (option 3). Allocate a default ruleset to be used when a user starts a message handler without specifying a ruleset (option 4). Create, maintain, and transfer rulesets (option 5). Add and maintain rules, and develop rulesets (option 6).
Getting Started Exiting RMS Panels If you are at a menu panel and want to access a panel that requires you to pass through a panel higher up in the RMS panel hierarchy, you must precede the path with the equal sign (=). The = character brings you back to the NonStop NET/MASTER MS primary menu panel. You can specify this at any => (or ===>) prompt. For example, if you are in an OCS window and want to create a ruleset, type =R.5.1 at the command line and press ENTER.
Getting Started Scrolling Press F3 to file the data. Press F12, or type X at the Command prompt and press ENTER, to cancel the data entry operation. Specify a path to jump to another panel and cancel the data entry operation. If you want to exit from a NonStop NET/MASTER MS window, type =X at any => prompt on any panel or next to an item on a selection list panel. If the window is the only window open, using =X also logs you off from NonStop NET/MASTER MS.
Getting Started Using the Command Prompt and RMS Commands Using the Command The Command prompt is available on selection list and data entry panels. The prompt Prompt and RMS accepts panel path specifications for skipping panels. Depending on the panel, some Commands of the following commands may be valid at the Command prompt: ? (or HELP), CMD, COPY, FIND, LOCATE, LOG, REFRESH, and X. Using the ? Command Use the ? or HELP command to obtain a list of the commands that may be valid at command prompts.
Getting Started Using Data Entry Panels The syntax of the REFRESH command is as follows: REFRESH [ OFF | ON | seconds ] OFF stops automatic refresh. ON starts automatic refresh. Refresh takes place every 20 seconds. seconds starts automatic refresh and sets the refresh time interval. Use a value in the range 2 through 86400. Issuing the REFRESH command without specifying an operand is equivalent to pressing the F6 function key. The operation refreshes the displayed information once.
Getting Started Using Action Codes in Selection Lists Using Action Codes in While using RMS, you will encounter various selection list panels. On selection list Selection Lists panels, you can use the displayed action codes to operate on selected items in the list. The action codes are as follows (each selection list panel has a subset of these codes): Action Codes Function A AC and IN C CP Adds an item using the selected item as a model. Activates or inactivates the selected item.
Getting Started Using Action Codes in Selection Lists The following example shows a panel on which you want to select rule NNM0001 for modification. (The rule was created on October 30, 1994 and was last modified on October 31, 1994 at 4:12 p.m. by user NMTHY). You typed an S next to rule NNM0001. When you press ENTER, RMS allows you to modify the rule.
Getting Started Getting Online Help in RMS Getting Online Help in RMS provides an online help facility that displays help text describing the function of RMS a particular panel. Use online help as follows: 1. While you are at a panel that you need help on, press F1. The online help for that panel appears. 2. While on a help panel, you can perform the following: Use F7 and F8 to page backward or forward through the panels. Use F11 and F12 to jump to the end or the beginning of the online help. 3.
Getting Started Getting Online Help in RMS 2. The user has tried a number of times but failed to supply the correct password, resulting in the following monitor-class message: NNM0686 USER userid FAILED TO PROVIDE CORRECT PASSWORD, AFTER TRYING n TIMES ON devname userid is the ID of the user trying to log on, and devname is the device name of the terminal from which the user is trying to log on. 3.
Getting Started Getting Online Help in RMS 4.
Getting Started Getting Online Help in RMS 6. Press ENTER. The following RMS : Control Options Definition—Suppression panel appears: SDPL----------- RMS : Control Options Definition - Suppression -----Page 1 of 4 Command ===> Ruleset .... SAMPLE˚˚ Delivery Philosophy ..... POSITIVE (NEGATIVE or POSITIVE) Note: Message Delivery Philosophy may be NEGATIVE or POSITIVE. That is messages may be delivered unless explicitly suppressed (POSITIVE) or suppressed unless explicitly delivered (NEGATIVE).
Getting Started Getting Online Help in RMS 11. Ensure that the values in the fields on your panel are as follows: SDPL------------ RMS : Control Options Definition - Run Parms ------Page 3 of 4 Command ===> RUN PARAMETER Message Suppression ............ Message Modification ........... Message Replacement ............ System Command ................. NonStop NET/MASTER Command ..... Start NCL Procedure ............ Exec Command Group ............. Activate Timer ................. Action Message Group .....
Getting Started Getting Online Help in RMS 13. Press F3 to file the profile of the ruleset. The RMS : Ruleset Maintenance panel reappears, and message RMS5004 RULESET CREATED confirms the creation of the ruleset. 14. Next, add a rule to the ruleset to achieve your third objective as discussed under “Objective” earlier in this section. Press F4 to return to the NonStop NET/MASTER RMS primary menu panel. 15. Select option 6 to access Rule Maintenance. The RMS : Rule Maintenance panel appears. 16.
Getting Started Getting Online Help in RMS 18. Select option 1 to access Add Using Defaults as on the following panel: SDPL-------------- RMS : Message Action Rules Maintenance -------------ZRMSUPDP Select Option ===> 1 1 2 X - Add Using Defaults - Display/Modify/Delete/Add With Model - Exit Selection Key .... ˚˚˚˚˚˚˚˚˚˚˚˚ Opt 2 - Blank or partial key for list. F1=Help F2=Split F3=Exit F4=Return F9=Swap Page 1 of the RMS : Message Validation panels appears. 19.
Getting Started Getting Online Help in RMS 21. Type Y in the Alarm field to instruct RMS to ring your terminal bell when message NNM0686 triggers the rule. 22. Type P in the Replacement Method field to instruct RMS to display a panel on your OCS window instead of the original message. 23. Type &ZZZMSGTEXT in line 1 of the Replacement Text field. &ZZZMSGTEXT is an RMS message variable that contains the text of the original message that is to be displayed as line 1 on your panel. 24.
Getting Started Getting Online Help in RMS 27. Type CLOSTERM &WORD14 in the Command Text field to instruct RMS to close the terminal at which logon attempts have failed due to incorrect passwords. Your panel should be similar to the following: SDPL------------------------ RMS : System Action --------------------Page 5 of 6 Command ===> Command Text ..... NCL Proc Name .... Exec Cmd Group ... Submit Actions ... Activate Timer ... Set Variables .... Load Ruleset ..... NCL Exit Name ....
Getting Started Getting Online Help in RMS 4. Type M at the Select Option prompt (you want to start a message handler to process messages that come to your OCS window) and name your ruleset SAMPLE in the Ruleset Name field.
Getting Started Getting Online Help in RMS You have started a MSGPROC that uses ruleset SAMPLE. The value 000024 in the sample display is the NCL ID of the message handler. The NCL ID of your message handler may be different. Remain at your RMS : RMS Message Display panel and proceed to “Seeing Your Message Handler Working” next in this section. Seeing Your Message Handler Working You can test that your message handler is working by generating message NNM0686 yourself.
Getting Started Implementing a Ruleset for a Message Handler Implementing a Armed with the basic operational characteristics of RMS and having stepped through Ruleset for a Message the sample session (described earlier in this section), use the guidelines presented here Handler to implement your rulesets for use by message handlers. The stages in implementing a ruleset for a message handler are as follows (shown graphically in Figure 4-2): 1.
Getting Started Implementing a Ruleset for a Message Handler Figure 4-2. Developing a Ruleset Start message handler together with STATSCAP to determine message flow. Analyze statistics on message flow. Develop ruleset and rules to process messages. Test rules by using simulated events. See Section 9 See Section 10 See Sections 5 and 6 See Section 8 Ruleset Modification Required Start message handler together with ruleset in actual environment. Analyze statistics on message handler.
Getting Started Implementing a Ruleset for a Message Handler Factors That Can Affect the Performance of a Message Handler While developing your ruleset, you need to consider the following factors that affect the performance of your message handler: Using wild-card characters in the trigger criteria means that the handler has to accommodate a large number of rule triggering possibilities. Minimize the use of wild-card characters. Use the STATSCAP ruleset to identify your trigger events.
Getting Started Implementing a Ruleset for a Message Handler If the message-delivery philosophy is set to POSITIVE, the filter table is type FAIL. Messages that are defined by rules to be suppressed are processed by the filter table. Rules processed by the filter table must meet the following criteria: No message validation is specified. The delivery of the message is specified as N (suppressed). No message threshold processing is specified. Rule actions are not specified for when the rule is triggered.
5 Creating and Developing Rulesets and Rules This section provides instructions on how to create and develop rulesets as follows: Create a ruleset. You must create a ruleset before you can implement any rules. Add message action rules, message group rules, or time-based rules to a ruleset. You use these rules to automate your tasks. For each task, the section first gives the following high-level information: 1. How to access the function. 2.
Creating and Developing Rulesets and Rules Creating a Ruleset Whether to enable or disable certain ruleset features What ruleset statistics to capture You can also specify what needs to be changed in the environmental profile for a message handler that uses the ruleset (effective only if you start the message handler as a MSGPROC, or as an INT-type message handler in the current or a background environment).
Creating and Developing Rulesets and Rules Creating a Ruleset Figure 5-1. Ruleset Creation—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 5 RMS : Ruleset Maintenance 1 Create RMS : Control Options Screen Screen Screen Definition Title Title Title Panels Here Here Here RMS : Profile Definition 007 3. From the RMS : Ruleset Maintenance panel, perform the following: a. Specify the name of the ruleset in the Ruleset field.
Creating and Developing Rulesets and Rules Creating a Ruleset RMS : Control Options Definition—Statistics RMS : Profile Definition Note If you are creating the ruleset specifically for time-based rules, only the parameters in the RMS : Control Options Definition—Run Parms panel have relevance. Leave the other parameters as they are.
Creating and Developing Rulesets and Rules Creating a Ruleset develop your ruleset, you can include additional comments. A ruleset takes on the comments you add to the control options record. You have created a new ruleset. You can add rules to the ruleset and make changes to the ruleset (for example, control options) to suit any new requirements. Remember to update the comments as you do so.
Creating and Developing Rulesets and Rules Creating a Ruleset Note If the default delivery exit NCL procedure returns a nonzero return code to an EMSPROC, LOGPROC, or MSGPROC message handler, and the exit NCL procedure does not explicitly (1) use the appropriate NCL verb xxxCONT to return the message to NonStop NET/MASTER MS or (2) use the appropriate NCL verb xxxDEL to delete the message, the handler returns the message to NonStop NET/MASTER MS for normal delivery.
Creating and Developing Rulesets and Rules Creating a Ruleset Implementing User-Defined Preprocessing You can use your own exit NCL procedure to process messages before RMS rule processing is performed. You must use the EXIT core statement in your procedure to return a value to RMS. If the return code is zero, RMS continues to deliver or suppress the message according to the specified delivery philosophy.
Creating and Developing Rulesets and Rules Creating a Ruleset ruleset with a message handler. Your NonStop NET/MASTER MS user ID definition contains the name of this library. Specify the name of the preprocessing exit NCL procedure in the following Pre-Processing NCL Exit field on the RMS : Control Options Definition—Suppression panel: Pre-Processing NCL Exit ......... Note: Initial message processing exit procedure. (Before Rule lookup) 073 The exit NCL procedure must exist.
Creating and Developing Rulesets and Rules Creating a Ruleset Select fields and in each of the 13 Merge—MSG MOD fields. The 13 ranking elements that you use when you define a rule are given in Table 5-1. Table 5-1.
Creating and Developing Rulesets and Rules Creating a Ruleset RMS selects the rule that contains the ranking elements of the highest priorities. Typically, if a ranking element makes a rule more restrictive, the element has a higher priority.
Creating and Developing Rulesets and Rules Creating a Ruleset Specify values in all the fields on the RMS : Control Options Definition—Run Parms panel. The values can be any of the following: Value Description N Y S B Do not perform the action. Perform the action. Do not perform the action but send a message describing what would have been done. Perform the action and send a message describing what has been done.
Creating and Developing Rulesets and Rules Creating a Ruleset Default Propagation field, RMS delivers the message as if the delivery philosophy is negative; that is, it suppresses the message. Solicited messages—The Process Solicited Msgs field controls whether solicited messages can trigger rules. (A solicited message is a message that is generated in response to an explicit request.
Creating and Developing Rulesets and Rules Creating a Ruleset Field Description System Command Number of NonStop NET/MASTER MS PROGRUN and OPSYS commands directly issued by rules Number of NonStop NET/MASTER MS commands (excluding PROGRUN and OPSYS) directly issued by rules Number of NCL procedures directly started by rules Number of command groups executed by rules Number of time-based rules loaded by rules Number of message group rules triggered Number of messages not affected by a rule Number of time
Creating and Developing Rulesets and Rules Creating a Ruleset Specifying the Message Statistics to Capture Using the fields on the right half of the RMS : Control Options Definition—Statistics panel, you can instruct RMS to gather the following message statistics: Keep a count of the total number of processed messages using the Total Msgs Processed field. The valid values are N (no) and Y (yes). The initial value is N.
Creating and Developing Rulesets and Rules Adding a Message Action Rule You specify your special profile requirements using the following Base Profile fields on the RMS : Profile Definition panel: SDPL---------------------- RMS : Profile Definition ----------------Page 1 of 1 Command ===> Ruleset .... HYRLST02 Base Profile (Y/N) CMDKEEP ..... (Y/N) CMDSEP ...... CMDSTACK .... DELCHAR ..... EMS ......... YES GUID ........ HOLD ........ INITCMD ..... MONMSG ...... N (Y/N) MSG ......... (Y/N) MSGALARM ....
Creating and Developing Rulesets and Rules Adding a Message Action Rule Figure 5-2 shows the panels you encounter when adding a message action rule to a ruleset. Figure 5-2.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Add a message action rule as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance. The RMS : Rule Maintenance panel appears.
Creating and Developing Rulesets and Rules Adding a Message Action Rule b. Select option 1 to access Message Action Rules Maintenance. If a selection list panel appears, select the appropriate ruleset by typing an S next to the name of the ruleset and pressing ENTER. The RMS : Message Action Rules Maintenance panel appears.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Work your way through the six panels, filling in the required fields. (See the following subsections for a detailed description of the fields.) 4. Before you file the rule definition, you should specify the filing method.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Naming the Message Action Rule Name the rule in the Message Action ID field (page 1 of the message action rule definition panels). Message Action ID .... Default value: MESSAGE RECOGNITION ELEMENTS ---------------------------Message ID ........ SS ID ............. MDO Element Name Value 042 The name, if specified, must consist of one through twelve characters. Each character must be an alphanumeric character, @, #, or $.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specifying the Criteria That Trigger the Message Action Rule The seven types of criteria that determine if a message may trigger the message action rule are as follows: Message recognition elements (you must specify at least one element) Source of the message Time of message arrival User-defined criteria User-defined rule trigger priority State (frozen or not frozen) of the message subject Message text elements Using the Message Recog
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specifying the Message ID. RMS regards the first word of a message as the message ID. You use a message ID as a criterion by specifying a value in the Message ID field (for example, NNM0001). The field accepts up to 32 characters. Use the wild-card characters, question mark (?) and asterisk (*), to match multiple messages. An asterisk must follow at least one character and must be the last character in the field.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Using the Message Source You can restrict the messages that can trigger the rule by specifying the source of the messages (page 1 of the message action rule definition panels). You identify the source by the following: Domain ID of the NonStop NET/MASTER MS or the SOLVE management services system from which the message comes Name of the process that sends the message MESSAGE SOURCE -------------Domain ID ......... Process Name ......
Creating and Developing Rulesets and Rules Adding a Message Action Rule Use a variable to allow the domain ID criterion to change dynamically (for example, you can set the value of the variable by using another rule). If you specify an asterisk (*) in the Domain ID field, the rule is triggered by messages from all domains. Also, if you leave the field blank, the rule is only triggered by messages from the current NonStop NET/MASTER MS system. Specifying the Process Name.
Creating and Developing Rulesets and Rules Adding a Message Action Rule N if you do not want a message arriving on the day to trigger the rule. Specifying the Time Range. You can specify up to two time ranges to restrict the message arrival time. The four fields are Time1 and Time2 for the first range and Time3 and Time4 for the second range. The value, if specified, must conform to the following: The value must be in the range 00:00:00 through 23:59:59. You can omit the 00 strings.
Creating and Developing Rulesets and Rules Adding a Message Action Rule You may place the procedure in your NonStop NET/MASTER user procedure library if you are the only person who will use this ruleset with a message handler. Your NonStop NET/MASTER MS user ID definition contains the name of this library. Specify the name of your message validation exit NCL procedure in the User Exit field shown on the next partial panel (page 2 of the message action rule definition panels). The procedure must exist.
Creating and Developing Rulesets and Rules Adding a Message Action Rule subject, that is, the 14th word in the message, and the word contains devname. When you freeze a subject (for example, device $ATP5.#TERM4), message NNM0686 that contains the frozen subject as devname cannot now trigger the rule. Note In RMS, when you attempt to freeze a subject without specifying a manager, all subjects with the same name are frozen.
Creating and Developing Rulesets and Rules Adding a Message Action Rule You can specify up to five tests and base the validation on a logical combination of the tests. If you do not want to place any restrictions, leave the fields blank. Specifying a Test. You can test for a specified string in a message.
Creating and Developing Rulesets and Rules Adding a Message Action Rule 2. Specify the type of test to be performed in the Opr field. The values consist of the following Boolean relational operators: Operator Description CT (ConTain) RMS searches the test string for the text specified in the Scan Text field. The match can occur anywhere within the test string. RMS tests for a match between the first part of the test string and the text specified in the Scan Text field.
Creating and Developing Rulesets and Rules Adding a Message Action Rule For example, the following message arrives: NNM0686 USER NMTJT FAILED TO PROVIDE CORRECT PASSWORD, AFTER TRYING 3 TIMES ON $ATP5.#TERM4 Depending on the test criteria, the results are as follows: Start Pos 14 13 14 14 4 14 14 4 4 5 5 14 14 3. Word Num 3 1 14 14 3 3 Opr Scan Text Result CT CT EQ EQ EX EX GE GE GT GT LE LE LT LT LK LK JT JT NMTJT NMTJT NMTJT JT NMTJT NMTSR 1 1 9 5.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specifying How You Want the Message Modified Once a message satisfies the triggering criteria of the rule, RMS can modify the message presentation according to the rule (for example, to enhance message presentation). You specify how you want RMS to modify the message using the RMS : Message Modification panel (page 4 of the message action rule definition panels).
Creating and Developing Rulesets and Rules Adding a Message Action Rule only if the Deliver field has the value Y, L, or N. You specify the parameters for message threshold processing on the RMS : Message Modification panel. Threshold Maxcnt .... Correlation Key ..... Interval .... Do Actions .... 050 Specify the number of messages (message threshold) in the Maxcnt field and the time interval in the Interval field.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Using the Message Threshold for Each Variation of the Message. Instead of applying the message threshold to the message as a whole, you can apply the threshold to each variant of the message. To use this feature, specify a key in the Correlation Key field on the RMS : Message Modification panel.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specifying Changes to Message Attributes You can instruct RMS to change the attributes of the message that triggers the rule. Specify the new settings in the following fields on the RMS : Message Modification panel (if you do not want to change an attribute, leave the corresponding field blank): Field Description Alarm Determines if the message should sound an alarm. The value must be blank, N (no), or Y (yes).
Creating and Developing Rulesets and Rules Adding a Message Action Rule Note If you use a panel to display the new text, the user needs to press a function key to remove the panel and return to normal message display. If you want to replace the message, you must specify both the Replacement Method field and the Replacement Text fields on the RMS : Message Modification panel; otherwise, leave the fields blank.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specifying the Message Action Rule Actions You can instruct RMS to perform specified actions when this rule is triggered (for example, to automate tasks). You specify the actions using the RMS : System Action panel (page 5 of the message action rule definition panels). SDPL------------------------ RMS : System Action -------------------Page 5 of 6 Command ===> Command Text ..... NCL Proc Name .... Exec Cmd Group ... Submit Actions ...
Creating and Developing Rulesets and Rules Adding a Message Action Rule For certain actions to be effective, you must also ensure that the control options of the ruleset allow them. You can enable or disable these actions using the RMS : Control Options Definition—Run Parms panel.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specifying an NCL Procedure to Be Started You can instruct RMS to start an NCL procedure when this rule is triggered. The procedure should be in the NonStop NET/MASTER customized procedure library. The name of the library is in the NonStop NET/MASTER MS startup parameter NCLCUSTSRC. Use the NonStop NET/MASTER MS SHOW PARAM command on the OCS command line to display the value of NCLCUSTSRC.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Specify the name of the background environment in the Submit Actions field on the RMS : System Action panel. If the field is left blank, the system actions are executed in the same environment as the message handler. Specifying an NCL Queue You can instruct RMS to execute the rule actions in a specified NCL queue when this rule is triggered. Specify the name of the NCL queue in the NCL Queue field on the RMS : System Action panel.
Creating and Developing Rulesets and Rules Adding a Message Action Rule To use this feature, specify Y (YES) in the Set Variables field on the RMS : System Action panel (the default is NO). Press F8 to access the RMS : Set Ruleset Variables panel (page 6 of the message action rule definition panels) to specify the variables.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Controlling How the Variables Are Set. You can instruct RMS when to set the variables. Specify this control in the Set Variables field on the RMS : Set Ruleset Variables panel using the following values: Value Description AFTER Sets the variables as the last action of the rule. Use AFTER if you want to pass the values of the variables to rules and exit NCL procedures after this rule processing has completed.
Creating and Developing Rulesets and Rules Adding a Message Action Rule Place the rule action exit NCL procedure in the NonStop NET/MASTER customized procedure library. The name of the library is in the NonStop NET/MASTER MS startup parameter NCLCUSTSRC. Use the NonStop NET/MASTER MS SHOW PARAM command on the OCS command line to display the value of NCLCUSTSRC.
Creating and Developing Rulesets and Rules Adding a Message Action Rule For example, a message group rule contains three members, rule A, rule B, and rule C. Rule A has a trigger life of 1 minute, rule B has a trigger life of 30 seconds, and rule C has a trigger life of 15 seconds. The following can occur (Figure 5-4): Figure 5-4.
Creating and Developing Rulesets and Rules Adding a Message Action Rule A message triggers rule A. Twenty seconds later, a second message triggers rule C. Another twenty seconds later, a third message triggers rule B. Because rule C has expired when rule B is triggered, the message group rule is not triggered. To register the rule, you must specify both the Message Group ID and the Purge After fields as follows: Specify the name of the message group rule in the Message Group ID field.
Creating and Developing Rulesets and Rules Adding a Message Action Rule If you have more than one %INCLUDE rule in the ruleset, RMS loads the oldest rule first. Add a %INCLUDE rule as follows: 1. Access page 1 of the message action rule definition panels to perform the following: a. Set the initial status of the rule at the Status field: ACTIVE or INACTIVE. b. Name the rule using the Message Action ID field. c. Implementing a %START Rule Type %INCLUDE in the Message ID field. 2.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Implementing a Dynamic Rule A dynamic rule is a message action rule in which the primary trigger is determined by a variable. If the variable is not set, the message handler does not match any messages against the rule. Once the variable is set, the message handler starts matching messages against the rule. You turn on and turn off the rule by setting and resetting the variable using another rule.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Figure 5-5.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Add a message group rule as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance. The RMS : Rule Maintenance panel appears.
Creating and Developing Rulesets and Rules Adding a Message Group Rule b. Select option 2 to access Message Group Rules Maintenance. If a selection list panel appears, select the appropriate ruleset by typing an S next to the name of the ruleset and pressing ENTER. The RMS : Message Group Rules Maintenance panel appears.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Note 4. When finished filling in the fields, press F3 to file the definition. The rule is immediately accessible by a message handler using this ruleset. The RMS : Message Group Rules Maintenance panel reappears, and a message confirms the addition of the new group rule. 5. To make rule management easier, you should always add comments to describe a new rule as described in “Maintaining Comments” in Section 6.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Identifying the Message Group Rule Members You can have up to 20 message action rules as members of the message group rule. Together, the rule members trigger the group rule. When first creating a group rule, you must specify at least one message action rule.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Ensure that you place your panel in the NonStop NET/MASTER customized panel library. The name of the library is in the NonStop NET/MASTER MS startup parameter PNLCUSTSRC. Use the NonStop NET/MASTER MS SHOW PARAM command on the OCS command line to display the value of PNLCUSTSRC. You may place the panel in your NonStop NET/MASTER user panel library if you are the only person who will use this ruleset with a message handler.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Specifying the Message Attributes You can instruct RMS to deliver your message with certain attributes. Specify the settings in the following fields (if you do not want to set an attribute, leave the corresponding field blank): Field Description Alarm Determines if the message should sound an alarm. The value must be blank, N (no), or Y (yes). If the value is blank, RMS delivers the message using Alarm=N.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Note Panels require a terminal for display. If you use panels in a rule within the ruleset, you should ensure that the handler delivers the message to a terminal. For example, specify Y in the Deliver field and start the message handler as a MSGPROC in an OCS environment. If the environment does not support panels, the panel cannot be delivered but the message handler continues operating.
Creating and Developing Rulesets and Rules Adding a Message Group Rule Specifying the Message Group Rule Actions You can instruct RMS to perform specified actions when this rule is triggered (for example, to automate tasks). You specify the actions using the RMS : System Action panel (page 3 of the message group rule definition panels). SDPL------------------------ RMS : System Action -------------------Page 3 of 3 Command ===> ACTIONS (ANY combination may be entered) Command Text ...... NCL Proc Name .
Creating and Developing Rulesets and Rules Adding a Message Group Rule For certain actions to be effective, you must also ensure that the control options of the ruleset allow them. You can enable or disable these actions using the RMS : Control Options Definition—Run Parms panel.
Creating and Developing Rulesets and Rules Adding a Message Group Rule provide the value of the delay period before the rule action is retried. For further information on retrying rule action NCL procedures, refer to the subsection “Using Automatic Retry for Rule Action NCL Procedures,” later in this section. Specify the name of the procedure, followed by any parameters to be passed, in the NCL Proc Name field on the RMS : System Action panel. The field accepts up to 59 characters.
Creating and Developing Rulesets and Rules Adding a Message Group Rule no execution limit for rule actions sent to an NCL queue that you have not yet defined or if you explicitly specify no NCL queue name. See Section 2, “Message Handlers, Timers, Rulesets, and Rules,” for more information about how rule actions are queued. See Section 3, “Planning for, Installing, and Managing RMS,” for information about defining NCL queues and setting the execution limit.
Creating and Developing Rulesets and Rules Using Automatic Retry for Rule Action NCL Procedures Using Automatic Retry If you instruct RMS to start a rule action NCL procedure when a rule is triggered, your for Rule Action NCL NCL procedure can set a return code to instruct RMS to retry the rule action. The rule Procedures action NCL procedure can also specify message text to describe the rule action retry, and provide the value of the delay period before the rule action is retried.
Creating and Developing Rulesets and Rules Adding a Time-Based Rule INTCMD ‘opsys status snax lu‘ &ZZZMSUBJECT INTREAD VARS=(*(4),&state) IF &STATE == ‘Up’ THEN /* Recovery was successful */ /* Terminate with return code 0 */ EXIT 0 ELSE /* Recovery failed */ IF &$RETRY <= 5 THEN /* There will be retry left */ DO /* Assign text of message to be delivered */ &SYSMSG = ‘AUTO RECOVERY OF’ &ZZZMSUBJECT ‘FAILED.
Creating and Developing Rulesets and Rules Adding a Time-Based Rule Figure 5-6.
Creating and Developing Rulesets and Rules Adding a Time-Based Rule Add a time-based rule as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance. The RMS : Rule Maintenance panel appears.
Creating and Developing Rulesets and Rules Adding a Time-Based Rule b. Select option 3 to access Time-Based Rules Maintenance. If a selection list panel appears, select the appropriate ruleset by typing an S next to the name of the ruleset and pressing ENTER. The RMS : Time-Based Rules Maintenance panel appears. SDPL---------------- RMS˚:˚Time-Based Rules Maintenance ---------------ZRMSUPDP Select Option ===> 1 2 X - Add Using Defaults - Display/Modify/Delete/Add With Model - Exit Selection Key ....
Creating and Developing Rulesets and Rules Adding a Time-Based Rule Setting the Status of the Time-Based Rule 5. When finished filling in the fields, press F3 to file the definition. The RMS : Time-Based Rules Maintenance panel reappears, and a message confirms the addition of the new rule and states whether the rule is activated. 6. To make rule management easier, you should always add comments to describe a new rule, as described in “Maintaining Comments” in Section 6.
Creating and Developing Rulesets and Rules Adding a Time-Based Rule Specifying the Time to Perform Time-Based Rule Actions You can set the times of a day when a timer should perform the rule actions (RMS : Time-Based Rule Definition panel). Clock Settings (Activation and Frequency) MON Y On Days ..... OR On Date ..... At .......... Every ....... Limit ....... User ID .....
Creating and Developing Rulesets and Rules Adding a Time-Based Rule the range 00:00:00 through 23:59:59. You can omit the 00 strings. For example, ::01 is the same as 00:00:01. Specifying the Repeat Times You can instruct the timer to repeat the rule actions at regular time intervals. Specify the repeat interval in the Every field and the number of times to repeat in the Limit field.
Creating and Developing Rulesets and Rules Adding a Time-Based Rule Specifying the Time-Based Rule Actions You can instruct the RMS timer to perform specified actions at specific times (for example, to automate tasks). You specify the actions using the RMS : Time-Based Rule Definition panel. Actions (ANY combination may be entered) Command Text ...... NCL Proc Name ..... Exec Cmd Group ....
Creating and Developing Rulesets and Rules Adding a Time-Based Rule Specify the name of the procedure, followed by any parameters to be passed, in the NCL Proc Name field on the RMS : Time-Based Rule Definition panel. The field accepts up to 59 characters. The procedure must exist. Furthermore, for the procedure to be valid in this field, the procedure must contain no compilation errors.
6 Updating and Maintaining Rulesets, Rules, and Command Groups This section provides instructions on how to maintain your rulesets as follows: Add (based on a model), copy, modify, or delete rules. During the development of a ruleset or as your system changes, you may want to change the rules in the ruleset. Add, copy, modify, or delete command groups. You use a command group when you want to automate the issuing of a group of NonStop NET/MASTER MS commands. Copy a ruleset.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding a Rule Using Another Rule as a Model Figure 6-1.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding a Rule Using Another Rule as a Model 2. At the Selection Key field, you can request a list of some or all of the rules of the selected type (message action rules, message group rules, or time-based rules) in the ruleset as follows: If you want a particular rule, specify the name of the rule. If you want a partial list, specify a partial text string (that is, the first few characters of the name of a rule or rules).
Updating and Maintaining Rulesets, Rules, and Command Groups Copying Rules Copying Rules 6. Press F3 to file the modified definition as a new rule. A message confirms the addition of the new rule. 7. Change the comments to describe the new rule, as described in “Maintaining Comments,” later in this section.
Updating and Maintaining Rulesets, Rules, and Command Groups Copying Rules Figure 6-2.
Updating and Maintaining Rulesets, Rules, and Command Groups Copying Rules Copying Rules From a Selected Ruleset Copy rules from a selected ruleset into an existing ruleset as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance. The RMS : Rule Maintenance panel appears. a. Specify the name of the ruleset from which to copy rules in the Ruleset field. If you wish to be prompted by a selection list panel, ensure that the field is blank. b.
Updating and Maintaining Rulesets, Rules, and Command Groups Modifying a Rule b. Select the appropriate option to access the type of rules to copy (for example, option 1 for message action rules). A selection list panel appears listing all the rules of the selected type in RMS. 2. Type CP next to the names of the rules to copy. Press ENTER to start copying the rules. An inset appears prompting for the name of the ruleset to copy to. a. Specify the name of the ruleset in the RULESET NAME field. b.
Updating and Maintaining Rulesets, Rules, and Command Groups Modifying a Rule If you want a full list, leave the field blank. RMS lists all the rules in the ruleset. Select option 2 to access Display/Modify/Delete/Add With Model. A selection list panel appears. 3. Note Type an S next to the name of the rule to modify and press ENTER. The first rule definition panel appears. You can select more than one rule to work on.
Updating and Maintaining Rulesets, Rules, and Command Groups Deleting Rules 6. Press F3 to file the modified definition. A message confirms that the rule has been modified. 7. Update the comments to reflect the changes to the rule, as described in “Maintaining Comments,” later in this section. You may also want to update the comments on the ruleset itself. Deleting Rules When a rule becomes obsolete, you can delete it.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups 3. Note On the selection list that appears, type a D next to the names of the rules to delete. Press ENTER. A message appears prompting you to confirm the deletion. If you change your mind and do not want to delete the selected rules, cancel the delete operation by pressing F12 and do not perform Steps 4 and 5. 4. Press ENTER to confirm the deletion. A rule is flagged as **DELETED** if the operation is successful.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups Figure 6-3.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups 2. Select option 1 to access Add Using Defaults. The RMS : Command Group Definition panel appears. SDPL------------------- RMS : Command Group Definition -------------Page 1 of 1 Command ===> Command Group ID ....
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups Adding a Command Group Using Another Command Group as a Model Note 4. When you finish filling in the fields, press F3 to file the definition. The RMS : Command Groups Maintenance panel reappears, and a message appears confirming the addition of the new command group. 5.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups 4. Modify the command group definition. Use the following function keys to move between fields and to validate entries: TAB and SHIFT TAB to move between input fields ENTER to validate your changes Copying Command Groups Into a Selected Ruleset 5. Press F3 to file the modified definition as a new command group. A message confirms the addition of the new command group. 6.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups Copying Command Groups From a Selected Ruleset Copy command groups from a selected ruleset into an existing ruleset as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance. The RMS : Rule Maintenance panel appears. a. Specify the name of the ruleset from which to copy command groups in the Ruleset field. If you wish to be prompted by a selection list panel, ensure that the field is blank.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups a. Specify ALL in the Ruleset field. b. Select option 4 to access Command Groups Maintenance. A selection list panel appears listing all the command groups in RMS. 2. Type CP next to the names of the command groups to copy. Press ENTER to start copying the command groups. An inset appears prompting for the name of the ruleset to copy to. a. Specify the name of the ruleset in the RULESET NAME field. b.
Updating and Maintaining Rulesets, Rules, and Command Groups Developing Command Groups 3. Note Type an S next to the name of the command group to modify and press ENTER. The RMS : Command Group Definition panel appears. You can select more than one command group to work on. When you have finished with one command group, the RMS : Command Group Definition panel for the next command group appears. 4. Modify the commands in the command group.
Updating and Maintaining Rulesets, Rules, and Command Groups Copying a Ruleset If you want a full list, leave the field blank. RMS lists all the command groups in the ruleset. Select option 2 to access Display/Modify/Delete/Add With Model. 3. Note Copying a Ruleset 6–18 On the selection list panel that appears, type a D next to the names of the command groups to delete. Press ENTER. A message appears prompting you to confirm the deletion.
Updating and Maintaining Rulesets, Rules, and Command Groups Copying a Ruleset Figure 6-4.
Updating and Maintaining Rulesets, Rules, and Command Groups Copying a Ruleset Copy a ruleset as follows: 1. At any => prompt, type =R.5 and press ENTER to access Ruleset Maintenance. The RMS : Ruleset Maintenance panel appears. SDPL--------------------- RMS : Ruleset Maintenance -------------------ZRMSRSMP Select Option ===> 1 2 3 4 5 9 X Create Ruleset Copy Ruleset Merge Rulesets Delete Ruleset Transfer Ruleset Ruleset Report Functions Exit Ruleset ................
Updating and Maintaining Rulesets, Rules, and Command Groups Copying a Ruleset b. Select option 2 to access Copy Ruleset. If a selection list panel appears, select the name of the ruleset to copy by typing an S next to the name of the ruleset and pressing ENTER. The RMS : Ruleset Copy panel appears. SDPL----------------------- RMS : Ruleset Copy ---------------------Page 1 of 1 Command ===> Copy from HYRLST02 to .... F1=Help F2=Split ˚˚˚˚˚˚˚ F3=Copy F9=Swap F12=Cancel 2.
Updating and Maintaining Rulesets, Rules, and Command Groups Merging Rulesets Merging Rulesets You can merge two rulesets together. Of these two, you merge a source ruleset into a target ruleset. The source ruleset remains unchanged; the target ruleset is updated with the records from the source that are not yet in the target. A record can be, for example, a rule or the environmental profile.
Updating and Maintaining Rulesets, Rules, and Command Groups Merging Rulesets Merge two rulesets as follows: 1. At any => prompt, type =R.5 and press ENTER to access Ruleset Maintenance. The RMS : Ruleset Maintenance panel appears. SDPL--------------------- RMS : Ruleset Maintenance -------------------ZRMSRSMP Select Option ===> 1 2 3 4 5 9 X - Create Ruleset Copy Ruleset Merge Rulesets Delete Ruleset Transfer Ruleset Ruleset Report Functions Exit Ruleset ................
Updating and Maintaining Rulesets, Rules, and Command Groups Modifying the Control Options of a Ruleset Modifying the Control Options of a Ruleset You can modify the control options of a ruleset and, depending on how you file the changes, have the changes reflected immediately in the message handlers. Figure 6-6 shows the panels encountered when modifying control options. Figure 6-6.
Updating and Maintaining Rulesets, Rules, and Command Groups Modifying the Control Options of a Ruleset Modify the control options of a ruleset as follows: 1. At any => prompt, type =R.6 and press ENTER to access Rule Maintenance. The RMS : Rule Maintenance panel appears. a. Specify the name of the ruleset in the Ruleset field. If you wish to be prompted by a selection list panel, either ensure that the field is blank or specify ALL in the field. b.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding or Modifying the Environmental Profile Associated With a Ruleset Adding or Modifying the Environmental Profile Associated With a Ruleset Note 4. Use F3 to file the changed control options. The RMS : Rule Maintenance panel reappears, and a message appears confirming the modification of the control options of the ruleset. 5.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding or Modifying the Environmental Profile Associated With a Ruleset Figure 6-7. Environmental Profile Modification—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 6 RMS : Rule Maintenance 5 Ruleset Specified No Ruleset Specified or ALL Ruleset Selection List Panel RMS : Profile Definition 019 2. Add or modify the environmental profile associated with the ruleset.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding or Modifying the Function Key Settings Associated With a Ruleset If you want to save the profile but do not want to make the profile available to existing message handlers that use the ruleset, leave the initial value D (deferred) in the Activation field. If you want to save the profile and make the profile available to existing message handlers that use the ruleset, specify I (immediate).
Updating and Maintaining Rulesets, Rules, and Command Groups Adding or Modifying the Function Key Settings Associated With a Ruleset 6530 and Compatible Terminal 3270 and Compatible Terminal F12 PF12 and PF24 F13 F14 PF14 SF1 through SF15 None Function Orders the displayed messages chronologically. Exits from the OCS recall buffer.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding or Modifying the Function Key Settings Associated With a Ruleset Figure 6-8. Function Key Settings Modification—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 6 RMS : Rule Maintenance 6 No Ruleset Specified or ALL Ruleset Specified Ruleset Selection List Panel RMS : Function Screen Screen Screen Key Settings Title Title Title Panels Here Here Here 020 2.
Updating and Maintaining Rulesets, Rules, and Command Groups Adding or Modifying the Function Key Settings Associated With a Ruleset ENTER to validate your entries F7 and F8 to page through the RMS : Function Key Settings panels RMS bases the definition of function key settings on the NonStop NET/MASTER MS FK command. Refer to the NonStop NET/MASTER MS Command Reference Manual for the FK command syntax. You can map two types of functions to a function key.
Updating and Maintaining Rulesets, Rules, and Command Groups Deleting the Environmental Profile and Function Key Settings Records If you want to save the function key settings and make the settings available to existing message handlers that use the ruleset and your OCS window, specify I (immediate).
Updating and Maintaining Rulesets, Rules, and Command Groups Maintaining Comments Maintaining Comments You can only add comments to a record that you have already created. You can update existing comments.
Updating and Maintaining Rulesets, Rules, and Command Groups Deleting Rulesets 2. On the list that appears, type a C next to the record to comment on and press ENTER. The RMS : Comments Maintenance panel appears.
Updating and Maintaining Rulesets, Rules, and Command Groups Deleting Rulesets Figure 6-9. Ruleset Deletion—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 5 RMS : Ruleset Maintenance 4 Delete Ruleset Specified RMS : Ruleset Deletion No Ruleset Specified RMS : Ruleset Selection (Delete) 021 Delete rulesets as follows: 1. At any => prompt, type =R.5 and press ENTER to access Ruleset Maintenance. The RMS : Ruleset Maintenance panel appears. a.
Updating and Maintaining Rulesets, Rules, and Command Groups Transferring Rulesets Between RMS Databases 2. Press ENTER to confirm the deletion. A ruleset is flagged as **DELETED** if the operation is successful. Transferring Rulesets You can transfer a ruleset, and the records of the ruleset, from one RMS database to Between RMS another RMS database. When a ruleset is transferred, the source ruleset remains Databases unchanged.
Updating and Maintaining Rulesets, Rules, and Command Groups Transferring Rulesets Between RMS Databases 2. Select option 5 to access Transfer Ruleset. Leave the Ruleset field blank for the Transfer Ruleset option. The RMS : Ruleset Transfer panel appears. SDPL-------------------- RMS : Ruleset Transfer -----------------------ZRMSRXIP Command ===> From RMS Database: UDB File ID ..... or filename ..... (ZRMSDB = Current RMS Database) Ruleset Name .... To RMS Database: UDB File ID ..... or filename .....
Updating and Maintaining Rulesets, Rules, and Command Groups Transferring Rulesets Between RMS Databases Specifying the Source Database You must specify the RMS database and the name of the source ruleset you want to transfer by filling in the following fields: From RMS Database: (ZRMSDB = Current RMS Database) UDB File ID ..... or filename ..... Ruleset Name .... 071 You must enter either a UDB file ID or the name of the file in which the source ruleset is located.
Updating and Maintaining Rulesets, Rules, and Command Groups Transferring Rulesets Between RMS Databases You must enter either a UDB file ID or the name of the file in which you want to receive the source ruleset. The UDB File ID field and the Filename field are mutually exclusive, and must represent an RMS database. The fields are described below: The UDB File ID field indicates the logical file ID of an open user database in the current NonStop NET/MASTER MS system.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports The Activation field can consist of the following values: Value Description I Determines whether the target ruleset and records are immediately available to any message handlers using the target ruleset. Immediate activation only occurs when the destination database is the current RMS database ZRMSDB. Immediate activation of the ruleset occurs when the current message has completed processing.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Figure 6-11.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Printing a Detailed Report Print a detailed report on a ruleset as follows: 1. At any => prompt, type =R.5 and press ENTER to access Ruleset Maintenance. The RMS : Ruleset Maintenance panel appears. a. Specify the name of the ruleset on which you want a report in the Ruleset field. If you wish to be prompted by a selection list panel, ensure that the field is blank. b.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports c. Type the number of copies of the report to be printed in the Number of Copies field. The default is 1. d. Press ENTER. 3. If you choose to include rules or command groups in the report in Step 2a, selection list panels appear. You can select the rules and command groups to be included in the report as follows: a. Type a P next to the names of the rules or command groups to be included.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Example In the following example, the user NMTHY generates a detailed report on the BASERULE ruleset and the user default ruleset allocation. Of the message action rules, only the ZCPUDOWN rule is included.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE 2 USER : NMTHY DATE : 30-OCT-1994 TIME : 17:53:30 PRINT A RULE OF RULESET : BASERULE RULETYPE : RULESET CONTROL PARAMETERS RULEID : RULEDESC : Base ruleset provided with RMS - performs automated recovery of objects -------------------------------------------------------------------------------S U P P R E S S I O N A N D R A N K I N G ------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE USER : NMTHY DATE : 30-OCT-1994 TIME : 17:53:30 3 PRINT A RULE OF RULESET : BASERULE RULETYPE : RULESET CONTROL PARAMETERS RULEID : RULEDESC : Base ruleset provided with RMS - performs automated recovery of objects -------------------------------------------------------------------------------R U N P A R A M E T E R S ----------------------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE 4 USER : NMTHY DATE : 30-OCT-1994 TIME : 17:53:30 PRINT A RULE OF RULESET : BASERULE RULETYPE : RULESET CONTROL PARAMETERS RULEID : RULEDESC : Base ruleset provided with RMS - performs automated recovery of objects -------------------------------------------------------------------------------S T A T I S T I C S ----------------------------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services -----------------------USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:16 PRINT A RULE OF RULESET : BASERULE RULETYPE : MESSAGE ACTION RULES RULEID : ZCPUDOWN RULEDESC : CPU0101 starts proc ZRMSCPUN to dump and reload failed CPU -------------------------------------------------------------------------------R U L E D O C U M E N T A T I O N ------------------------------------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE 6 USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:16 PRINT A RULE OF RULESET : BASERULE RULETYPE : MESSAGE ACTION RULES RULEID : ZCPUDOWN RULEDESC : CPU0101 starts proc ZRMSCPUN to dump and reload failed CPU -------------------------------------------------------------------------------M E S S A G E V A L I D A T I O N ------------------------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services -----------------------USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:16 PRINT A RULE OF RULESET : BASERULE RULETYPE : MESSAGE ACTION RULES RULEID : ZCPUDOWN RULEDESC : CPU0101 starts proc ZRMSCPUN to dump and reload failed CPU -------------------------------------------------------------------------------M E S S A G E M O D I F I C A T I O N --------------------------------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE 8 USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:16 PRINT A RULE OF RULESET : BASERULE RULETYPE : MESSAGE ACTION RULES RULEID : ZCPUDOWN RULEDESC : CPU0101 starts proc ZRMSCPUN to dump and reload failed CPU -------------------------------------------------------------------------------S Y S T E M A C T I O N ----------------------------------------------------------
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services -----------------------USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:47 PRINT A RULE OF RULESET : BASERULE RULETYPE : RULESET PROFILE RULEID : RULEDESC : -------------------------------------------------------------------------------R U L E D O C U M E N T A T I O N ------------------------------------------------------------------------------- RULE DOCUMENTATION -----------------1 2 3 4 5 6 7 8
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE 10 USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:47 PRINT A RULE OF RULESET : BASERULE RULETYPE : RULESET PROFILE RULEID : RULEDESC : -------------------------------------------------------------------------------P R O F I L E ------------------------------------------------------------------------------- BASE PROFILE -----------CMDKEEP ........ CMDSEP .........
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Rule Management Services ------------------------ PAGE 11 USER : NMTHY DATE : 30-OCT-1994 TIME : 17:54:53 PRINT A RULE OF RULESET : HYRLST01 RULETYPE : DEFAULT RULESET ALLOCATION RULEID : RULEDESC : -------------------------------------------------------------------------------D E F A U L T R U L E S E T A L L O C A T I O N ------------------------------------------------------------------------------- REGION OWNER .
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports 5. On the selection list panel that appears, type a P next to the records on which you want a report and press ENTER. An inset appears prompting for the spooler location. 6. Specify the following: Name of the spooler location in the LOCATION field. The default is $S.#RMS. Number of copies to be printed in the COPIES field. The default is 1. 7. Press ENTER to start printing the report.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports 2. Select option 2 to access Print a Ruleset (Compressed) to Spooled Output. The RMS : Print Ruleset Selection panel appears. SDPL------------------- RMS : Print Ruleset Selection -----------------ZRMSCATP Command ===> Enter required category types from ruleset BASERULE Select category type: S To select category type X Indicates that this category type is unavailable for this option Ruleset Control Options ......
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Example In the following example, the user NMTHY generates a summarized report on the rules in the BASERULE ruleset.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Printing a Summarized Report Using Criteria Print a summarized report on rules and command groups that match specified criteria as follows: 1. At any => prompt, type =R.5 and press ENTER to access Ruleset Maintenance. The RMS : Ruleset Maintenance panel appears. a. Specify the name of the ruleset that contains the rules and command groups on which you want a report in the Ruleset field.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports c. Type the number of copies of the report to be printed in the Number of Copies field. The default is 1. d. Press ENTER. The criteria panels for the first item selected appear. The panels are similar to the panels you use to define the rules or command groups. Note 3. Specify the criteria that place restrictions on which rules or command groups to include in the report.
Updating and Maintaining Rulesets, Rules, and Command Groups Printing Ruleset Reports Example In the following example, the user NMTHY generates a summarized report on the message action rules in the BASERULE ruleset according to a specified criterion. The criterion is that the NCL Proc Name field in the rule definition contains a string that starts with ZRMSDSNN.
7 Managing Default Rulesets This section provides instructions on how to allocate and maintain default rulesets. A user needs a default ruleset to start a message handler without specifying a ruleset. Using Default Rulesets When you start a message handler without specifying a ruleset, the message handler uses the default ruleset of the user that owns the environment in which the message handler operates.
Managing Default Rulesets Allocating a Default Ruleset to a User Allocating a Default Allocate a default ruleset to a user as follows: Ruleset to a User 1. At any => prompt, type =R.4 and press ENTER to access Default Ruleset Allocation. The RMS : Default Ruleset Allocation panel appears. 2. Select option 1 to access Add Using Defaults. The Default Ruleset Allocation definition panel appears. SDPL----------------- RMS : Default Ruleset Allocation -------------Page 1 of 1 Region Owner .......
Managing Default Rulesets Maintaining Default Rulesets 5. To make default ruleset management easier, add a brief comment to describe a new allocation. Access the selection list panel by specifying the user ID in the Selection Key field and selecting option 2. Type a C next to the user ID and press ENTER. The RMS : Comments Maintenance panel appears.
Managing Default Rulesets Maintaining Default Rulesets Proceed as follows to perform these maintenance functions: 1. At any => prompt, type =R.4 and press ENTER to access Default Ruleset Allocation. The RMS : Default Ruleset Allocation panel appears. 2. Specify the user ID to identify the allocation in the Selection Key field as follows: Specify the user ID. A panel appears listing the default ruleset allocation for that user ID. Specify a partial text string.
Managing Default Rulesets Maintaining Default Rulesets Number of copies to be printed in the COPIES field. The default is 1. An allocation is flagged as **PRINTED TO SPOOL** if the operation is successful. The allocation is printed if a printer is associated with the selected spooler location. You can use the Guardian spooler utility PERUSE to manage your RMS spooler jobs. Refer to the Guardian User’s Guide for information on how to use PERUSE.
Managing Default Rulesets Maintaining Default Rulesets (This page 7–6 left intentionally blank) 108106 Tandem Computers Incorporated
8 Testing Rules Using Simulated Events This section provides instructions on how to test your ruleset using simulated events as follows: Test rules by generating a simulated message. Test rules by using a simulated message flow. The section explains how to capture and save the real message flow on your system. You can use the saved messages (modified if necessary) to test your rules. Check the RMS timers that may be started by generating a simulated time event.
Testing Rules Using Simulated Events Testing Rules Against a Simulated Message Figure 8-1.
Testing Rules Using Simulated Events Testing Rules Against a Simulated Message Generate a simulated message to test the rules in a ruleset as follows: 1. At any => prompt, type =R.7 and press ENTER to access Event Simulation. The RMS : Event Simulation panel appears. a. At the Ruleset field, specify the name of the ruleset to test. If you wish to be prompted by a selection list panel, ensure that the field is blank. b. Select option 1 to access Message Arrival Simulation.
Testing Rules Using Simulated Events Testing Rules Against a Simulated Message The following two panels define the simulated message NNM0686 USER NMTJT FAILS TO PROVIDE CORRECT PSWRD, AFTER TRYING 3 TIMES ON $ATP5.#TERM4. The message arrives on a Thursday at 10:40:44. SDPL------------ RMS : Event Simulation - Message Parameters -------Page 1 of 2 Command ===> Status ===> ACTIVE MESSAGE RECOGNITION ELEMENTS ---------------------------Message ID ........ NNM0686˚˚˚˚˚ SS ID .............
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages 5. Analyze the displayed messages to determine what you want to do next and proceed as follows: If you want to check the parameters of your simulated message, press F6. The parameters of your simulated message appear in two RMS : Event Simulation—Message Parameters panels. You cannot modify the parameters on these panels.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Testing a Ruleset Against Real Messages You can use the RMS panel interface to test a ruleset against the messages that flow in your OCS environment and to capture the processed messages. RMS starts an INT-type message handler that uses the ruleset under test to process the messages. Figure 8-2 shows the panels encountered when testing a ruleset. Figure 8-2.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages 2. At any => prompt, type =R.7 and press ENTER to access Event Simulation. The RMS : Event Simulation panel appears. a. At the Ruleset field, specify the name of the ruleset to test. If you wish to be prompted by a selection list panel, ensure that the field is blank. b. Select option 3 to access Capture Message Flow and RMS Activity.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Line and Column tell you where you are in the captured messages. The numbers refer to the top left corner of the message display area. The numbers may change as you scroll through the messages by using the function keys F7, F8, F10, and F11, or jump to a message by using the FIND command and the function key F5. 4. Analyze the displayed messages to determine if the ruleset is satisfactory.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Testing a Ruleset Against a Saved Message Set You can use a set of saved messages (either as is or after modification) to test a ruleset. Thus, you can simulate a message flow and do not have to depend on your system and network to generate the messages for testing. The process is similar to when you test a ruleset against the real messages.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Use a saved message set to test a ruleset as follows: 1. If necessary, modify a message set to simulate the message flow you require. You can modify a message set using option 5 on the RMS : Event Simulation panel. See “Modifying a Message Set” next in this section. 2. At any => prompt, type =R.7 and press ENTER to access Event Simulation. The RMS : Event Simulation panel appears. a.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Modifying a Message Set You can modify a saved message set to simulate the message flow you require as follows: Add messages to the message set. Modify messages in the message set. Copy messages from or to another message set. Delete messages from the message set. You can then use your modified message set to test your ruleset. Figure 8-4 shows the panels encountered when modifying a message set.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Figure 8-4.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages 3. Type an S next to the name of the message set to modify and press ENTER. The RMS : Captured Message Set Edit panel appears. You can use the action codes A, CP, D, and S, and the command COPY on this panel.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Adding or Modifying a Message You can add a message that is based on an existing message in the message set. When you add a message, RMS creates a copy of the model message that you can modify. Also, you can modify a message. On the RMS : Captured Message Set Edit panel, type an A or S next to the message you want to add or modify and press ENTER. The RMS : Saved Message Editing panel appears.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages RMS constructs the message by appending the text of the message to the value you specify in the Message ID field under MESSAGE COMPONENTS. If you specify a value in the Message ID field, this value becomes the message ID. If you leave the Message ID field blank, the first word of the message text becomes the message ID.
Testing Rules Using Simulated Events Testing Rules Against a Set of Messages Maintaining Message Sets You can perform the following maintenance functions on the message sets that you use to test your rulesets by using the RMS : Captured Message Set Selection panel. To get to the panel, type =R.7.5 at any => prompt and press ENTER. You can also get to the panel as shown in Figure 8-4. Add a message set by using another message set as a model. Merge the messages in one message set into another message set.
Testing Rules Using Simulated Events Testing Time-Based Rules Testing Time-Based You can simulate a specific time or a time range to test which time-based rules in a Rules ruleset satisfy the time criteria. You can interactively change the rules in the ruleset and the simulated time. Figure 8-5 shows the panels encountered when simulating a time to test a ruleset. Simulate a specific time or a time range to test the time-based rules in a ruleset as follows: 1. At any => prompt, type =R.
Testing Rules Using Simulated Events Testing Time-Based Rules Figure 8-5. Time Simulation—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 7 RMS : Event Simulation No Ruleset Specified 2 Ruleset Specified RMS : Ruleset Selection RMS : Event Simulation— Time-Based Rules RMS : Event Simulation—Triggered Actions A or S RMS : Time-Based Rule Definition D F3 Delete 028 2. Define your simulated time.
Testing Rules Using Simulated Events Testing Time-Based Rules day indicated by the date. If you leave the Day field blank, the value in the field defaults to the correct day. If you want to stop the simulation, press F12 and do not perform Steps 3 and 4. 3. Press F3 to send the simulated time event. The RMS : Event Simulation— Triggered Actions panel appears with a list of the triggered rules. 4.
Testing Rules Using Simulated Events Testing Time-Based Rules (This 8–20 page left intentionally blank) 115415 NonStop NET/MASTER RMS Management and Operations Guide
9 Controlling Message Handlers and Rules This section provides instructions on how to control message handlers and rules. Rules include message action rules and RMS timers. The section also describes how to dynamically modify the characteristics of message handlers and RMS timers, and how to use message subjects to modify message handler actions. Controlling Message The rulesets you develop contain a set of rules that a message handler should follow Handlers when processing messages.
Controlling Message Handlers and Rules Controlling Message Handlers Starting a Message Handler by Using the RMS Panel Interface You can start message handlers by using the RMS panel interface. Figure 9-1 shows the panels you encounter when starting a message handler by using the RMS panel interface. Start a message handler by using the RMS panel interface as follows: 1.
Controlling Message Handlers and Rules Controlling Message Handlers Figure 9-1.
Controlling Message Handlers and Rules Controlling Message Handlers 2. Select option 1 to access Start RMS Message Handler. The RMS : Start Message Handler panel appears. SDPL-------------------- RMS : Start Message Handler ------------------ZRMSSTRP Select Option ===> E L M C B X - Start Start Start Start Start Exit a a a a a Ruleset Name ....
Controlling Message Handlers and Rules Controlling Message Handlers Option B to start an INT-type message handler in a background environment If a selection list panel appears, select the appropriate ruleset by typing an S next to the name of the ruleset and pressing ENTER. The RMS : RMS Message Display panel appears. Messages appear advising you of the progress of the starting operation.
Controlling Message Handlers and Rules Controlling Message Handlers 3. Press ENTER to start the printing operation. Messages appear advising you of the printing operation. The messages are printed if a printer is associated with the selected spooler location. You can use the Guardian spooler utility PERUSE to manage your RMS spooler jobs. Refer to the Guardian User’s Guide for information on how to use PERUSE.
Controlling Message Handlers and Rules Controlling Message Handlers The handler uses the default ruleset of the user who owns the OCS window in which the handler is being started. Note If a MSGPROC message handler was previously started for this user and window from the RMS : Start Message Handler panel using a ruleset other than the default allocated ruleset, that other ruleset is used instead. Starting a MSGPROC Automatically.
Controlling Message Handlers and Rules Controlling Message Handlers Displaying the List of Message Handlers and Their Descriptions You can display the list of message handlers by selecting option 2 from the NonStop NET/MASTER RMS primary menu panel. The RMS : Active Message Handlers panel appears and provides the following information on the handlers: Column Head Description NCL ID Type Region Identifies the NCL process that is the message handler. Identifies the type of the message handler.
Controlling Message Handlers and Rules Controlling Message Handlers If you want to purge a MSGPROC in an OCS window using the RMS panel interface, you must have started the user interface in the same OCS window. You cannot use the RMS panel interface to purge MSGPROCs in other OCS windows.
Controlling Message Handlers and Rules Controlling Message Handlers Modify the control options (Activation field on page 4 of the control options definition panels). See “Creating a Ruleset” in Section 5 for a detailed description of the fields on the control options panels. Modify the environmental profile (Activation field on the RMS : Profile Definition panel). See “Specifying the Environmental Profile Requirements” in Section 5 for a description of the RMS : Profile Definition panel.
Controlling Message Handlers and Rules Controlling Message Action Rules Controlling Message You can control message action rules by using the RMS panel interface or, in most Action Rules cases, by using the RMS command interface. You can perform the following tasks: Display, freeze, and delete active subjects, and display and delete queued rule actions. Display and thaw frozen message subjects. Freeze a message subject. Display and delete delayed message actions.
Controlling Message Handlers and Rules Controlling Message Action Rules Figure 9-2 shows the panels encountered when managing active subjects. Figure 9-2.
Controlling Message Handlers and Rules Controlling Message Action Rules Obtain and operate on the list of active subjects as follows: 1. At any => prompt, type =R.9 and press ENTER to access Message Action Control. The RMS : Message Action Control panel appears.
Controlling Message Handlers and Rules Controlling Message Action Rules Select option 1 to access Display/Freeze/Delete Active Message Subjects. The RMS : Active Message Subjects panel appears and provides the following information: Field Description Message Subject Displays the values you specify in the Subject and the Manager fields on the RMS : Message Action Control panel. If you leave those fields blank, the Message Subject field displays an asterisk (*).
Controlling Message Handlers and Rules Controlling Message Action Rules Note You can issue the REFRESH ON or REFRESH seconds command at the Command prompt on the RMS : Active Message Subjects panel to enable automatic refresh of the information on the panel. You can also use the RMS DISPLAY ACTIVE command from an OCS window or the ZRMSAPIN ( GETACTIVE ) procedure call from a user NCL procedure to, respectively, display or retrieve information about active subjects.
Controlling Message Handlers and Rules Controlling Message Action Rules Displaying the Details of an Active Message Subject and Deleting its Rule Actions You can display the details of an active message subject and selectively delete its rule actions. Proceed as follows: 1. On the RMS : Active Message Subjects panel, type an S next to the subject you want and press ENTER.
Controlling Message Handlers and Rules Controlling Message Action Rules Note You can issue the REFRESH ON or REFRESH seconds command at the Command prompt on the RMS : Message Action Queue panel to enable automatic refresh of the information on the panel. 2. Type the appropriate action codes next to the action to act on and press ENTER. The action codes are as follows: Use the action code S to obtain the detailed information on an action.
Controlling Message Handlers and Rules Controlling Message Action Rules SDPL------------------- RMS : Message Action Details ------------------ZRMSMADP Message Details Subject............. $BXYZ Manager............. Arrival Time........ 13:46:13 Text.... NNM0597 USER 100,7 AT HOMETERM $ICIP.#V000000 STARTED NCP $DAT A9.INNM.NCP IN CPU 1:1 WITH CONFIGURATION FILE $DATA2.G.TC0800 08 Rule Details Ruleset............. KFTEST Msg-Handler NCLID... 001504 Rule ID ... ANYNNM Rule-Action NCLID....
Controlling Message Handlers and Rules Controlling Message Action Rules Figure 9-3. Frozen Subject Thaw—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 9 RMS : Message Action Control 2 RMS : Frozen Message Subjects T Thaw 067 Display and thaw frozen subjects as follows: 1. At any => prompt, type =R.9 and press ENTER to access Message Action Control. The RMS : Message Action Control panel appears.
Controlling Message Handlers and Rules Controlling Message Action Rules 2. Leave the Subject and the Manager fields blank to display a list of all the frozen subjects. If you wish, you can use the two fields to restrict the listing. The Subject field accepts 34 characters. If you specify a value in the field, the list contains only the frozen subjects that have names of that value or beginning with that value. The Manager field accepts 32 characters.
Controlling Message Handlers and Rules Controlling Message Action Rules ZRMSAPIN ( THAW ) procedure call from a user NCL procedure to thaw a frozen subject. For more information on using RMS commands and procedure calls, see Appendix B, “RMS Commands,” and Appendix C, “RMS Procedure Calls,” respectively. Freezing a Message Subject You can freeze a subject so that when a message handler receives a message containing that subject, the message cannot trigger any rules.
Controlling Message Handlers and Rules Controlling Message Action Rules 2. Use the Subject field (34 characters long) and the Manager field (32 characters long) to identify the subject to freeze as follows: If you only specify a name in the Subject field, all messages containing a subject of that name (irrespective of the manager) are affected. If you only want to freeze a subject under a particular manager, specify values in both the Subject and the Manager fields.
Controlling Message Handlers and Rules Controlling Message Action Rules Display and delete delayed message actions as follows: 1. At any => prompt, type =R.9 and press ENTER to access Message Action Control. The RMS : Message Action Control panel appears.
Controlling Message Handlers and Rules Controlling Message Action Rules Select option 4 to access Display/Delete Delayed Message Actions. The RMS : Delayed Message Actions panel appears and provides the following information: Field Description Message Subject Displays the values you specify in the Subject and the Manager fields on the RMS : Message Action Control panel. If you leave those fields blank, the Message Subject field displays an asterisk (*).
Controlling Message Handlers and Rules Controlling Message Action Rules You can also use the RMS DISPLAY DELAYED command from an OCS window or the ZRMSAPIN ( GETDELAYED ) procedure call from a user NCL procedure to, respectively, display or retrieve limited information about delayed message actions. For more information on using RMS commands and procedure calls, see Appendix B, “RMS Commands,” and Appendix C, “RMS Procedure Calls,” respectively.
Controlling Message Handlers and Rules Controlling Message Action Rules SDPL------------------- RMS : Delayed Action Details ------------------ZRMSDMAP Message Details Subject............. $DEV09 Manager............. Arrival Time........ 12:57:38 Text.... MSGNCLD $DEV09 FAILED Rule Details Ruleset............. QTEST Rule-Action NCLID... 000518 Retry Date/Time..... Action NCL Proc..... NCL Queue........... Retry Message....... F1=Help F2=Split Rule ID... MSGNCLD 23-APR-1995 13:02:54 Delay...
Controlling Message Handlers and Rules Controlling Message Action Rules Figure 9-5. Rule Control—Panel Hierarchy NonStop NET/MASTER RMS Primary Menu Panel Option 6 RMS : Rule Maintenance 1 No Ruleset Specified Ruleset Specified ALL Specified RMS : Ruleset Selection RMS : Message Action Rules Maintenance 2 Message Action Rules Maintenance Selection List Panel 030 Activate or inactivate rules as follows: 1.
Controlling Message Handlers and Rules Controlling an RMS Timer in all the rulesets in RMS. If you wish to be prompted by a selection list panel, ensure that the field is blank. b. Select option 1 to access Message Action Rules Maintenance. If a selection list panel appears, select the appropriate ruleset by typing an S next to the name of the ruleset and pressing ENTER. If you specified ALL at the Ruleset field, proceed to Step 3. 2. The RMS : Message Action Rule Maintenance panel appears.
Controlling Message Handlers and Rules Controlling an RMS Timer If (1) the Status field is ACTIVE and (2) the Activation field is D (rule definition saved but not activated immediately), the RMS timer is activated only when RMS initializes.
Controlling Message Handlers and Rules Controlling an RMS Timer SDPL--------------------- RMS : Active RMS Timers ---------------------ZRMSTDSP Command ===> Scroll ===> PAGE S=Select P=Purge StartTime Dmap/Date Frequency Limit Auth/Route Ruleset Rule ID NextTmr 10:00:00 YYYYYYY LOG PRINTTST TIMERID1 15:00:00 YYYYYYY LOG HYRLST01 HYTMBSDRL001 <==== 18:00:00 YYYYYYY NMTHY HYRLST01 HYTMBSDRL002 *END* F1=Help F7=Backward Purging an RMS Timer Note F3=Exit F9=Swap F4=Return F5=Comments F6=Refresh When yo
Controlling Message Handlers and Rules Purging a NonStop NET/MASTER MS Timer Started by RMS 2. Type an S next to an RMS timer (listed by the time when the timer should first perform the rule actions) and press ENTER. The RMS : Time-Based Rule Definition panel appears. 3. Make your modifications. 4. Press F3 to file the new definitions. The RMS : Active RMS Timers panel reappears. The RMS timer is listed with the new definitions.
Controlling Message Handlers and Rules Purging a NonStop NET/MASTER MS Timer Started by RMS (This page left intentionally blank) 9–32 115415 NonStop NET/MASTER RMS Management and Operations Guide
10 Capturing Statistics This section provides instructions on how to capture statistics on a message handler. It explains the captured statistics so you can interpret your results. Evaluating the Before you develop your ruleset, you need to determine the message flow in the Message Flow on Your environment in which you intend to use the ruleset.
Capturing Statistics Capturing Statistics on a Message Handler Capturing Statistics on The control options of a ruleset determine if you can capture certain statistics on a a Message Handler message handler that uses the ruleset. You define the control options on statistics using the RMS : Control Options Definition—Statistics panel (page 4 of the control options definition panels).
Capturing Statistics Capturing Statistics on a Message Handler Capture the statistics on a message handler as follows: 1. At any => prompt, type =R.8 and press ENTER to access Statistics Capture. The RMS : Active Message Handlers panel appears. SDPL------------------- RMS : Active Message Handlers -----------------ZRMSMHCP Command ===> Scroll ===> PAGE S=Select NCL ID 000009 000012 002000 *END* F1=Help F7=Backward 2.
Capturing Statistics Capturing Statistics on a Message Handler 3. Specify how you want the statistics to be sorted (see “Specifying How You Want to Sort the Statistics” next in this section) and press ENTER to continue. The RMS : Statistics Capture panel appears with the status CAPTURE IN PROGRESS.
Capturing Statistics Capturing Statistics on a Message Handler SDPL---------------------- RMS : Statistics Capture -------------------ZRMSCAPP Command ===> CAPTURE STOPPED Current Capture: 53 Max Capture: 9999 Line 35 Column 1 ------------------------------------------------------------------------------ZCPUDOWN 0 0 ---- MESSAGE STATISTICS ---TOTAL MESSAGES PROCESSED 12 MESSAGES SORTED BY COUNT IN DESCENDING ORDER MSGID -----------TPD GIO0106 NNM1402 NNM0990 NNM0580 NNM0579 F1=Help F7=Backward COUNT ---
Capturing Statistics Capturing Statistics on a Message Handler Line and Column tell you where you are in the captured statistics. The numbers refer to the top left corner of the display area. The numbers may change as you scroll through the display by using the function keys F7, F8, F10, and F11, or jump to a text string by using the FIND command and the function key F5. You can press F12 to print the captured statistics.
Capturing Statistics Interpreting Captured Statistics reverse alphabetic order. Option 1 is the initial sorting option, represented by the value 1. Option 2 displays the messages in ascending order according to the number of times a message arrives. The displayed list starts with the messages that arrive least frequently. Messages that arrive the same number of times are arranged in alphabetic order. Option 3 displays the messages in alphabetic order.
Capturing Statistics Interpreting Captured Statistics SYSTEM CMDS ISSUED provides a count of the NonStop NET/MASTER MS commands PROGRUN and OPSYS issued through message action rules. These do not include commands issued using the command groups. NNM CMDS ISSUED provides a count of the NonStop NET/MASTER MS commands (excluding PROGRUN and OPSYS) issued through message action rules. These do not include commands issued using the command groups.
11 RMS Variables This section describes the RMS variables that you can use in your rules. RMS variables enable the transfer of data within a message handler (for example, between rules) and the extraction of information on a message. Being able to transfer data allows one rule in a message handler to affect another rule in the message handler (for example, the activation of a dynamic rule).
RMS Variables Ruleset Variables Rule Contents Variables 11–2 Rule contents variables are of the form &$RMS* (see Table 11-1). The variables contain the value of certain rule definition elements: for example, the value specified for the Deliver field on page 4 of the message action rule definition panels. When a message action rule or a message group rule is triggered, RMS sets the value of these variables with the contents of the triggered rule.
RMS Variables Ruleset Variables Table 11-1.
RMS Variables RMS Message Variables RMS Message RMS message variables contain information on a message that arrives at a message Variables handler. Depending on the message, some of the variables may not be applicable to the rule. Table 11-2 describes the RMS message variables. Table 11-2. RMS Message Variables (Page 1 of 2) Variable Description The following variables are visible to message action rules and message group rules, and their rule action NCL procedures and command groups.
RMS Variables RMS Message Variables Table 11-2. RMS Message Variables (Page 2 of 2) Variable Description &ZZZMSSID Contains the ID of the subsystem that generates the message and is the value of the &$xxx.SPI.TANDEM.ZSPI_TKN_SSID (converted event-message token ZSPI-TKN-SSID). The following variables are visible to message action rules and message group rules, and their rule action NCL procedures and command groups.
RMS Variables RMS Message Variables (This page left intentionally blank) 11–6 108106 Tandem Computers Incorporated
12 Base Rulesets This section describes the two base rulesets that RMS provides: BASERULE, which automates error recovery tasks, and STATSCAP, which captures statistics on the message flow in an environment. BASERULE The BASERULE ruleset enables you to automate various system error recovery tasks. The ruleset contains the following message action rules that act in response to event messages: Rule Function ZCPUDOWN Dumps the memory of a failed central processing unit (CPU) and reloads the CPU.
Base Rulesets BASERULE The active Guardian user ID for the user that owns the environment in which the message handler that uses BASERULE is executing must be a member of the super group: a Guardian user ID of 255,n, where n is in the range 1 through 255. The NonStop NET/MASTER MS user ID definition defines the active Guardian user ID for a user as follows: If the definition does not specify a Guardian ID, the active Guardian user ID defaults to the ID of the user that starts NonStop NET/MASTER MS.
Base Rulesets BASERULE ZCPUDOWN ZCPUDOWN is a message action rule that acts in response to event number 101 from the CPU subsystem. The rule dumps the memory of the failed CPU and reloads the CPU. Message Delivery The rule instructs the message handler to deliver the original message (event number 101 from the CPU subsystem) which appears in NonStop NET/MASTER MS as the following: CPU0101 Processor Down, CPU nn nn identifies the failed CPU. The subject is nn (for example, 1).
Base Rulesets BASERULE Customizing the Rule It is strongly recommended that you change the volume on which you place the CPU dump files to a volume other than $SYSTEM. The $SYSTEM volume is reserved for system files, and you do not want to use up space by filling $SYSTEM with dump files.
Base Rulesets BASERULE The following is an example of the contents of an IN file that sets the disk primary processes: PRIMARY PRIMARY PRIMARY PRIMARY PRIMARY PRIMARY PRIMARY PRIMARY $SYSTEM, 0 $DATA, 0 $DATA1, 1 $DATA2, 1 $DATA3, 2 $DATA4, 2 $DATA5, 3 $DATA6, 3 You can also customize the rule by changing the execution limit of the NCL queue in which the rule actions execute. Use the NCLQUEUE SET command from the OCS command line to change the execution limit.
Base Rulesets BASERULE NCL Queue The rule actions execute in the BASERULEZDEVICEDOWN NCL queue, which has a default execution limit of 5. Customizing the Rule You can customize the rule by changing the execution limit of the NCL queue in which the rule actions execute. Use the NCLQUEUE SET command from the OCS command line to change the execution limit. See Section 3, “Planning for, Installing, and Managing RMS,” for more information.
Base Rulesets BASERULE Message Delivery The rule instructs the message handler to replace the original message (event number 67 from the EMS subsystem) by the following: EMS0067 SUBDEV subdevice-name ERROR #errno The subject is subdevice-name (for example, $ATP1.#TERM1). Rule Actions When a message triggers the rule, the message handler starts NCL procedure ZRMSDEVN to perform the following: 1. Issue Guardian utility CMI commands to restart the subdevice.
Base Rulesets BASERULE Rule Actions When a message triggers the rule, the message handler starts NCL procedure ZRMSDSNN to perform the following: 1. Issue DSNM commands to restart the Expand line identified in the message. If the restart operation is successful, the procedure logs the following message in the NonStop NET/MASTER MS activity log: RMS9902 EXPAND LINE line-name RECOVERY COMPLETE. STATUS: UP 2. If Step 1 fails, delay one minute and then retry Step 1.
Base Rulesets BASERULE Rule Actions When a message triggers the rule, the message handler starts NCL procedure ZRMSDSNN to perform the following: 1. Issue DSNM commands to restart the Pathway terminal control process (TCP) identified in the message and the associated terminals. If the restart operation is successful, the procedure logs the following message in the NonStop NET/MASTER MS activity log: RMS9902 PATHWAY TCP tcp-name UNDER process-name RECOVERY COMPLETE.
Base Rulesets BASERULE NCL Queue The rule actions execute in the BASERULEZPATHTRMABRT NCL queue, which has a default execution limit of 10. Customizing the Rule You can customize the rule by changing the execution limit of the NCL queue in which the rule actions execute. Use the NCLQUEUE SET command from the OCS command line to change the execution limit. See Section 3, “Planning for, Installing, and Managing RMS,” for more information.
Base Rulesets BASERULE line to change the execution limit. See Section 3, “Planning for, Installing, and Managing RMS,” for more information. ZPATHTRMSUS2 ZPATHTRMSUS2 is a message action rule that acts in response to event number 1049 from the Pathway subsystem. ZPATHTRMSUS2 acts the same way as ZPATHTRMSUS1 but in response to different messages. The rule restarts a suspended Pathway terminal.
Base Rulesets BASERULE Message Delivery The rule instructs the message handler to replace the original message (event number 21 from the SNAX/XF subsystem) with the following: SX10021 SNAX LINE line-name INOP - REASON CODE : reason-code line-name is the name of the failed SNAX/XF line, and reason-code identifies the reason for the failure. The subject is line-name with System Services Control Point as the manager (for example, \SDPL.$SNA01 as subject and \SDPL.$SSCP as manager).
Base Rulesets BASERULE Point as the manager (for example, \SDPL.$SNA01 as subject and \SDPL.$SSCP as manager). Rule Actions When a message triggers the rule, the message handler starts NCL procedure ZRMSDSNN to perform the following: 1. Issue DSNM commands to restart the SNAX/XF line identified in the message. If the restart operation is successful, the procedure logs the following message in the NonStop NET/MASTER MS activity log: RMS9902 SNAX LINE line-name RECOVERY COMPLETE. STATUS: UP 2.
Base Rulesets BASERULE 2. Issue the commands to restart a TACL process for the terminal. If the restart operation is successful, the procedure logs the following message in the NonStop NET/MASTER MS activity log: RMS9902 TACL TERM terminal-name RECOVERY COMPLETE. STATUS: RUNNING 3.
Base Rulesets STATSCAP STATSCAP The STATSCAP ruleset enables you to capture statistics on the message flow in an environment. The ruleset contains no rules and does not affect the message flow. A message handler using STATSCAP captures all statistics on the message including the most recent message text of a message. STATSCAP allows the message handler to capture statistics on the first 1000 different messages. You can change this value. Valid values are 1 through 9999.
Base Rulesets STATSCAP (This page left intentionally blank) 12–16 115415 NonStop NET/MASTER RMS Management and Operations Guide
Appendix A RMS Messages Looking for Additional This appendix refers to topics that are discussed in other manuals.
RMS Messages Messages NCL Procedure or Panel Problem DSNM Problem If the problem occurred in an NCL procedure or a panel, have ready the procedure file and the panel description file.
RMS Messages RMS0006 RMS0003 FUNCTION KEY function-key IS NOT ACTIVE IN THIS WINDOW Cause. You pressed function-key but the key is not available on your panel. function-key is the name of a function key. Effect. The function key has no effect. Recovery. Select the function key for the type of processing you want to do from the list of available function keys at the bottom of your panel and press the key. RMS0004 INVALID COMMAND Cause.
RMS Messages RMS0007 RMS0007 INVALID USER ID Cause. You specified an invalid value in the User ID field on your Time-Based Rule Definition panel. Effect. The value is not accepted. The action is not performed. Recovery. Change the invalid value to a valid user ID before requesting the action again. Valid user IDs can contain only alphanumeric, @, #, and $ characters.
RMS Messages RMS0014 RMS0011 MUST BE Y(ES) OR N(O) Cause. You specified a value that is not one of Y, YES, N, or NO in a field on your menu or data entry panel (for example, the Parm Override field on the Start Message Handler panel). Effect. The value is not accepted. The action is not performed. Recovery. Change the invalid value to one of Y, YES, N, or NO before requesting the action again. RMS0012 MUST BE IN THE RANGE lower-limit TO upper-limit Cause.
RMS Messages RMS0015 RMS0015 DAY MUST BE IN THE FORMAT DDD Cause. You specified a value that is not a valid three-letter abbreviation of a day in the Day field on your panel (either page 2 of the Event Simulation—Message Parameters panels or the Event Simulation—Time-Based Rules panel). Effect. The value is not accepted. The action is not performed. Recovery.
RMS Messages RMS0021 Effect. The FIND command is not executed. Recovery. Type FIND or F, followed by a space and the text string you want to search for, at the Command ===> prompt, and press ENTER. RMS0019 TEXT find-text FOUND Cause. You entered the FIND (F) command followed by the text string find-text at the Command ===> prompt on a Message Display panel, an Activity Capture panel, or a Statistics Capture panel; or you pressed F5 to repeat a previous FIND command for find-text.
RMS Messages RMS0022 RMS0022 MDO VALUE MUST BE SPECIFIED IF MDO NAME IS NOT BLANK Cause. You specified a value in the MDO Element Name field but no value in the MDO Element Value field on your panel (either page 1 of the message action rule definition panels or page 1 of the Event Simulation—Message Parameters panels). You must specify the MDO element name and value together or not at all. Effect. The action is not performed. The MDO Element Value field is highlighted. Recovery.
RMS Messages RMS0029 Recovery. Change the invalid value in the Process Name field to a valid Guardian process name of the form \systemname.$processname before requesting the action again. systemname is the name of the system on which the process is executing and can contain up to seven characters; processname is the name of the process and can contain up to five characters. The first character of each component must be alphabetic, and the rest must be alphanumeric.
RMS Messages RMS0030 Recovery. Change the invalid value to a positive integer before requesting the action again. RMS0030 INVALID SUBMIT ACTION VALUE Cause. You specified an invalid value in the Submit Actions field on your data entry panel. This panel could be the System Action panel (page 5 of the message action rule definition panels), or the System Action panel (page 3 of the message group rule definition panels). Effect. The value is not accepted. The action is not performed. Recovery.
RMS Messages RMS0100 Recovery. Change the invalid value to a value that contains only alphanumeric, @, #, and $ characters before requesting the action again. Alphanumeric characters are A through Z, a through z, and 0 through 9. RMS0034 MUST BE ALPHANUMERIC, STARTING WITH ALPHA Cause. You specified an invalid value in a field on your panel. The field requires a value that starts with an alphabetic character and contains only alphanumeric, @, #, and $ characters. Effect. The value is not accepted.
RMS Messages RMS0101 RMS0101 error-text Cause. An error occurred in the internal processing of RMS. error-text describes the error. There are four variations of this message as follows: error-description procedure-name(ncl-id) SYS.ERROR.LIB: library-name procedure-name(ncl-id) SYS.ERROR.FILE: file-name procedure-name(ncl-id) SYS.ERROR.LINE: line-number error-description is a general description of the error. procedure-name is the name of the NCL procedure that raised the error and is the value of &SYS.
RMS Messages RMS0301 Effect. The function requiring database access is aborted. This could be an RMS panels function, the loading of rules for a message handler, or some other message handler processing. Recovery. Refer the problem to your system manager. Your system manager should run the NCL procedure ZRMSININ to initialize RMS. RMS0201 RULESET ruleset-name DOES NOT EXIST Cause. The function requested requires the ruleset named ruleset-name but the ruleset does not exist in the RMS database. Effect.
RMS Messages RMS0303 Effect. No report is sent to the spooler. The Ruleset Maintenance panel appears with this message on the third line of the panel. Recovery. This message is informational only; no recovery action is necessary. RMS0303 PRINTING Cause. You invoked the printing function while in a Message Display panel, Activity Capture panel, or Statistics Capture panel. You provided the required information on the inset that appeared and pressed ENTER. The printing operation started and is in progress.
RMS Messages RMS0312 Recovery. Change the value to a number in the range 1 through 9999 before requesting the action again. RMS0309 UNABLE TO OPEN SPOOLER spooler-location Cause. You started a printing operation but specified an invalid spooler location or failed to specify a spooler location. When you use the printing function, you must nominate a spooler location to receive the output. spooler-location is the specified name of the spooler location or blank if no name was specified. Effect.
RMS Messages RMS0313 RMS0313 record-count RECORDS READY TO BE PRINTED Cause. You selected an option from your Ruleset Print Report panel and were printing some records from the RMS database. The records were found and formatted for printing. record-count is the number of formatted records that are ready to be sent to the spooler for printing. Effect. The records that you requested to be printed are ready to be sent to the spooler for printing. Recovery.
RMS Messages RMS1006 RMS1004 ENTER REGION NAME Cause. You selected option B to start a message handler in a background environment from the Start Message Handler panel, but failed to specify the owner of the background environment in the Exec Region field. Effect. The message handler is not started. Recovery. Enter BLOG, BMON, BSYS, or EMSP in the Exec Region field and press ENTER. RMS1005 handler-typePROC(ncl-id) MESSAGE HANDLER START COMMENCED Cause. A user started a message handler.
RMS Messages RMS1007 INT The message handler is executing in the user's current environment or in a background environment. ruleset-name is the name of the ruleset to be loaded for this message handler. Effect. The Control Options Definition panels appear to the user and the control options can be modified. The message handler waits for the user to save the control options before continuing on to the next step in the starting operation. Recovery.
RMS Messages RMS1010 INT The message handler is executing in the user's current environment or in a background environment. ruleset-name is the name of the ruleset to be loaded for this message handler. Effect. The initialization of the message handler is complete as follows: Ruleset control options overridden (optional) Control options loaded Rules loaded and optimized Function keys set (handlers of type MSG only) Profile set (handlers of type MSG and INT only) Recovery.
RMS Messages RMS1011 MSG The message handler is executing as a MSGPROC. INT The message handler is executing in a user's current environment or in a background environment. rule-id is the name of the %START rule. Effect. The %START rule is executed. Recovery. This message is informational only; no recovery action is necessary. RMS1011 handler-typePROC(ncl-id) RULESET (ruleset-name) DYNAMICALLY MODIFIED BY (user-id) Cause.
RMS Messages RMS1014 The message handler is executing as an NCL process with NCL ID, ncl-id. handler-type is the type of message handler and can have one of the following values: EMS The message handler is executing as an EMSPROC. LOG The message handler is executing as a LOGPROC. MSG The message handler is executing as a MSGPROC. INT The message handler is executing in a user's current environment or in a background environment. Effect.
RMS Messages RMS1014 RMS1014 handler-typePROC(ncl-id) RULESET REFRESH REQUESTED BY (user-id) ACCEPTED Cause. There are two possible causes as follows: A group of messages triggered a message group rule in the ruleset associated with a message handler. One of the group rule actions is to load a new ruleset, and the request to do so was made.
RMS Messages RMS1019 INT The message handler is executing in a user's current environment or in a background environment. user-id is the user ID of the user that requested that the ruleset associated with the message handler be changed. Effect. The request to load a new ruleset is accepted and the message handler loads the ruleset named in the Ruleset field. Recovery. This message is informational only; no recovery action is necessary.
RMS Messages RMS1020 INT The message handler is executing in a user's current environment or in a background environment. ruleset-name is the name of the ruleset that the user modified. Effect. The profile of the environment the message handler is servicing is updated with the modified settings. Recovery. This message is informational only; no recovery action is necessary. RMS1020 handler-typePROC(ncl-id) %START RULE (rule-id) REJECTED Cause.
RMS Messages RMS1022 RMS1021 handler-typePROC(ncl-id) RULE (rule-id) DOMAIN ID NOT MATCHED Cause. A message handler encountered a %START rule with a domain ID that does not match that of the NonStop NET/MASTER MS on which the handler is executing. The message handler is executing as an NCL process with NCL ID, ncl-id. handler-type is the type of message handler and can have one of the following values: EMS The message handler is executing as an EMSPROC.
RMS Messages RMS1023 Recovery. If you want this %START rule to be executed by a message handler executing on this day, change the day criteria in the rule to allow the current day. Then restart the message handler. Otherwise, no recovery action is necessary. RMS1023 handler-typePROC(ncl-id) RULE (rule-id) TIME SPECIFICATION NOT MATCHED Cause. A message handler encountered a %START rule with time criteria that do not allow the current time.
RMS Messages RMS1026 RMS1025 handler-typePROC(ncl-id) SKIPPING RECURSIVE %INCLUDE OF ruleset-name-called IN ruleset-name Cause. A message handler encountered a %INCLUDE rule in the ruleset ruleset-name that the handler is currently loading, but the ruleset named in this rule was already loaded by the message handler. ruleset-name-called is the name of the ruleset identified in the %INCLUDE rule. The message handler is executing as an NCL process with NCL ID, ncl-id.
RMS Messages RMS1027 RMS1027 handler-typePROC(ncl-id) RULESET (ruleset-name) LOAD ENDED rule-count RULES LOADED Cause. A message handler completed loading the ruleset, ruleset-name. rule-count is the number of message action rules that were loaded. The message handler is executing as an NCL process with NCL ID, ncl-id. handler-type is the type of message handler and can have one of the following values: EMS The message handler is executing as an EMSPROC.
RMS Messages RMS1030 RMS1029 handler-typePROC(ncl-id) RULESET (ruleset-name) OPTIMIZED Cause. The message handler loaded all message action rules in ruleset-name (including the rules loaded through the %INCLUDE rules) into a vartable in memory. The vartable entries were optimized to enable faster searching of the vartable for each message read by the message handler. The message handler is executing as an NCL process with NCL ID, ncl-id.
RMS Messages RMS1031 Recovery. This message is a warning only; no recovery action is necessary. If the message handler uses rules that process event messages EMS0001 through EMS0511 (for example, some rules in the BASERULE ruleset) and you want to use the name of the device in the message as the subject, correct the problem identified by a previously logged NonStop NET/MASTER MS message (usually a command authority or DSNM availability problem), and restart the message handler.
RMS Messages RMS1035 Recovery. Restart ZRMSMGHN using a valid message handler type: EMS (EMSPROC), LOG (LOGPROC), MSG (MSGPROC), or INT (for current or background environment). RMS1034 handler-typePROC(ncl-id) RULE (rule-id) USER VALIDATION EXIT RC NOT ZERO, RC=return-code Cause. A message handler encountered a %START rule that failed validation. The rule contains a user-defined message validation exit NCL procedure that returned a nonzero return code. return-code is the value of the return code.
RMS Messages RMS1036 Recovery. This message is informational only; no recovery action is necessary. RMS1036 handler-typePROC(ncl-id) RULE INSTIGATED RULESET SWAP ACTIONED Cause. A message triggered a message action rule that requested to load a new ruleset. The action to load the new ruleset was started. The message handler is executing as an NCL process with NCL ID, ncl-id.
RMS Messages RMS1040 Recovery. Change the invalid owner to a valid owner of a background environment (one of BLOG, BMON, BSYS, or EMSP) in the Exec Region field. RMS1039 handler-typePROC(ncl-id) ABORTING Cause. A message handler experienced a fatal error that stopped the handler from operating. The message handler was executing as an NCL process with NCL ID, ncl-id. handler-type is the type of message handler and can have one of the following values: EMS The message handler is executing as an EMSPROC.
RMS Messages RMS1041 RMS1041 EMSPROC(ncl-id) EMS FILTER TABLE filter-table-name REMOVED FROM EMSDIST FILTER LIST Cause. The EMSPROC message handler disabled the use of the filter table, filter-table-name, by the EMS distributor. SYSPARMS EMSDISTFLT was updated. The EMSPROC is executing as an NCL process with NCL ID, ncl-id.
RMS Messages RMS1044 The ruleset contains suppression rules when the delivery philosophy is set to POSITIVE. Suppression rules have no validation or actions when the delivery philosophy is set to POSITIVE. EMSPROC generated the filter table according to the rules defined in the associated ruleset. Effect. If the delivery philosophy is POSITIVE, suppression rules are performed using a filter table.
RMS Messages RMS1045 RMS1045 INVALID VARIABLE NAME variable-name IN COMMAND GROUP(command-group-id) RULESET(ruleset-name) Cause. A command in the command group was executed. The command contained an invalid variable name. variable-name is the value that is invalid as a variable name (the & is not displayed) command-group-id is the name of the command group that contains the command that uses the invalid variable ruleset-name is the name of the ruleset that contains the command group Effect.
RMS Messages RMS1101 Recovery. Either delete the reference to the message group rule from the message action rule, or create the message group rule in the ruleset and include the message action rule as a member of the group rule. RMS1100 *** RULESET(ruleset-name) PROCESSING SOLICITED MESSAGE Cause. A message handler read a solicited message that required full processing to check if the message triggered any rules in the ruleset, ruleset-name.
RMS Messages RMS1102 If the Message Suppression setting is S, then this narrative message only describes the action of message threshold processing—the message handler disregards message threshold processing and delivers the message as if there were no message threshold processing. Recovery. This message is informational only; no recovery action is necessary. RMS1102 *** RULESET(ruleset-name) RULE(rule-id) SUPPRESS COUNT= message-count MAX=message-threshold Cause.
RMS Messages RMS1104 Effect. If the Message Replacement setting is B, the replacement by and the delivery of the multiline message are carried out. If the Message Replacement setting is S, then this narrative message only describes the action that would have been performed—either the original message is delivered and no replacement takes place (message action rule), or no message is delivered (message group rule). Recovery. This message is informational only; no recovery action is necessary.
RMS Messages RMS1106 RMS1106 *** RULESET(ruleset-name) RULE(rule-id) SET USER VARIABLE(S) Cause. A message triggered a message action rule that requested the setting of certain ruleset variables to specified values. rule-id is the name of the triggered rule, and ruleset-name is the name of the ruleset that contains the rule. The message handler sent this narrative message to describe the action of setting variables.
RMS Messages RMS1110 RMS1108 *** RULESET(ruleset-name) RULE(rule-id) END USER VARIABLE(S) Cause. A message triggered a message action rule that requested the setting of certain ruleset variables to specified values. rule-id is the name of the triggered rule, and ruleset-name is the name of the ruleset that contains the rule. The message handler sent this narrative message to describe the completion of the action of setting variables.
RMS Messages RMS1112 The Delivery Philosophy control option of the ruleset used is set to POSITIVE, and the message handler sent this narrative message to describe the action of delivering the message. message-id is the first word of the message to be delivered. The Default Propagation control option of the ruleset used is set to B or S to narrate this action. Whether the message handler actually delivers the message depends on this setting. Effect.
RMS Messages RMS1115 This narrative message describes the action of issuing the command (this is the command that you specified in the Command Text field on the rule definition panels or in a command group that was used in the rule). The System Command control option of the ruleset used (and the Exec Command Group control option if the command was issued through a command group) is set to B or S to narrate this action. Whether the command is actually issued depends on this setting. Effect.
RMS Messages RMS1116 This narrative message describes the action of issuing the command (this is the command that you specified as INTCMD command-text in the Command Text field on the rule definition panels or in a command group that was used in the rule). The NonStop NET/MASTER Command control option of the ruleset used (and the Exec Command Group control option if the command was issued through a command group) is set to B or S to narrate this action.
RMS Messages RMS1119 This narrative message describes the action of executing the command group (this is the command group that you specified in the Exec Cmd Group field on the rule definition panels). The Exec Command Group control option of the ruleset used is set to B or S to narrate this action. Whether the command group is actually executed depends on this setting. Effect. If the Exec Command Group setting is B, the command group specified in the rule is executed.
RMS Messages RMS1120 The message could appear as a result of a message action rule or a message group rule or a time-based rule being triggered, and either this command is specified in the Command Text field of the rule definition or this command is part of a Command Group specified in the Exec Cmd Group field of the rule definition. Effect. If the related control option setting is B, the command specified by command-text is issued.
RMS Messages RMS1125 mon-attribute MON={ YES | NO } msg-code-attribute MSGCODE=xx Effect. If the Message Modification setting is B, the message handler delivers the triggering message with the modified attributes. If the Message Modification setting is S, then this narrative message only describes the action that would have been performed—the message handler does not modify the attributes of the triggering message and the message is delivered with the original attributes. Recovery.
RMS Messages RMS1128 Recovery. This message is informational only; no recovery action is necessary. RMS1128 *** REPLTEXT===> replacement-text Cause. A message triggered a message action rule, or a group of messages triggered a message group rule that requested the delivery of a message (replacing the triggering message if this is a message action rule). This narrative message displays the message (or one line of a multiline message) replacement-text that was specified in the rule.
RMS Messages RMS1134 Only the message attributes that are set in the rule definition appear in the message.
RMS Messages RMS1135 intens-attribute INTENS={ HIGH | LOW } alarm-attribute ALARM={ YES | NO } nrd-attribute NRD={ YES | NO } scan-attribute SCAN={ YES | NO } mon-attribute MON={ YES | NO } msg-code-attribute MSGCODE=xx Effect. If the Message Modification setting is B, the message handler delivers the triggering message with the modified attributes to the activity log.
RMS Messages RMS1139 Only the message attributes that are set in the rule definition appear in the message.
RMS Messages RMS1140 The message handler sent this narrative message to describe the action of checking the status of the members of the message group rule to determine if the message group rule should be invoked. The Action Message Group control option of the ruleset used is set to B or S to narrate this action. Whether the message handler actually checks the message group rule and executes the rule depends on this setting. Effect.
RMS Messages RMS3000 RMS2001 ANOTHER USER IS ACCESSING THIS MSG HANDLER, TRY AGAIN LATER Cause. You typed the S (Select) or P (Purge) action code next to a message handler on your Active Message Handlers panel and pressed ENTER, but another user was already operating on that message handler. Effect. The message handler is not selected or purged. Recovery. Wait a few minutes, then press F6 to refresh your panel. Repeat the procedure if the message handler is still listed.
RMS Messages RMS3001 You may have accessed your NonStop NET/MASTER RMS primary menu panel by starting the RMS user interface NCL procedure ZRMSMENN from your OCS window. However, RMS has not been initialized on your system. The timer driver NCL procedure may have been flushed. Effect. The Active RMS Timers panel does not appear. Recovery. Start NCL procedure ZRMSININ to initialize RMS.
RMS Messages RMS4000 RMS3005 TIMER rule-id OF RULESET ruleset-name DYNAMICALLY MODIFIED Cause. You typed the S (Select) action code next to a timer on your Active RMS Timers panel, pressed ENTER, and modified the timer. The active copy of the corresponding time-based rule record was updated. The modifications are only valid for this instance of the timer.
RMS Messages RMS4001 Effect. The default ruleset allocated to the user is changed. The Default Ruleset Allocation selection list panel is redisplayed with the new ruleset name in the Ruleset column for the user. Recovery. This message is informational only; no recovery action is necessary. RMS4001 DEFAULT RULESET ALLOCATED Cause. You allocated a default ruleset to a user. You may have added the allocation by using option 1 (Add Using Defaults) on the Default Ruleset Allocation menu panel.
RMS Messages RMS5002 RMS5000 RULESET ALREADY EXISTS Cause. You selected option 1 to create a ruleset from the Ruleset Maintenance panel, but specified the name of an existing ruleset in the Ruleset field. Effect. No ruleset is created. The name of the ruleset is highlighted. Recovery. Change the name of the ruleset to a name that is not used by any existing ruleset in the Ruleset field, and press ENTER. RMS5001 ENTER RULESET NAME Cause. You failed to specify the name of a ruleset in a Ruleset field.
RMS Messages RMS5003 RMS5003 ANOTHER USER HAS LOCKED THIS RECORD, TRY AGAIN LATER Cause. You typed an S (Select) or D (Del) action code next to an item on a selection list panel and pressed ENTER, but another user was using the database record of that item. Effect. The item is not selected for modification or deletion. Recovery. Wait for a few minutes, then press F6 to refresh the selection list. Repeat the action if the item is still listed. RMS5004 RULESET CREATED Cause.
RMS Messages RMS5103 Recovery. This message is informational only; no recovery action is necessary. RMS5007 RULESET DELETED Cause. You requested the deletion of a ruleset on your Ruleset Deletion panel, or the deletion of one or more rulesets on your Ruleset Selection (Delete) panel, and pressed ENTER to confirm the request. Effect. The ruleset(s) are deleted. Recovery. This message is informational only; no recovery action is necessary. RMS5102 INVALID RANKING ELEMENT Cause.
RMS Messages RMS5104 Recovery. Change the invalid values to one of Y (Action), N (No action), S (Write narrative only), or B (Both narrate and action) before requesting the action again. RMS5104 MUST BE Y, N, OR T Cause. You specified an invalid value in the Msgs by Message ID field on your Control Options Definition—Statistics panel. Effect. The value is not accepted. The action is not performed. Recovery.
RMS Messages RMS5200 RMS5108 MESSAGE DELIVERY PHILOSOPHY MUST BE POSITIVE OR NEGATIVE Cause. You specified an invalid value in the Delivery Philosophy field on your Control Options Definition—Suppression panel. Effect. The value is not accepted. The action is not performed. Recovery. Change the invalid value to POSITIVE or NEGATIVE, or leave the field blank to use the default value POSITIVE, before requesting the action again. RMS5109 *WARNING* POSSIBLE DESTRUCTIVE EFFECTS Cause.
RMS Messages RMS5201 You selected option 2 to copy a ruleset from the Ruleset Maintenance panel and either specified source-ruleset in the Ruleset field, or left the Ruleset field blank and selected source-ruleset on the Ruleset Selection (Copy) panel. On the Ruleset Copy panel, you specified ruleset-name as the ruleset you want to create and copy to, and pressed F3 to start copying the ruleset. Effect. ruleset-name is created.
RMS Messages RMS5206 Effect. record-count records of category, record-category, are copied from the source ruleset. Recovery. This message is informational only; no recovery action is necessary. RMS5203 ENTER TARGET RULESET Cause. You failed to specify the name of the ruleset to be created on the Ruleset Copy panel or the name of the ruleset to merge into on the Ruleset Merge panel. Effect. The action is not performed.
RMS Messages RMS5206 RMS5206 TRANSFER OF total-record-count RECORDS to UDB udb-to-file-id COMPLETED SUCCESSFULLY Cause. You transferred a ruleset, and the records of the ruleset, from a source RMS database to a target RMS database. The number of records, total-record-count, were transferred to the RMS user database, udb-to-file-id. You selected option 5 to transfer rulesets from the Ruleset Maintenance panel. You specified the source RMS database by entering either the UDB file ID or file name.
RMS Messages RMS6005 Effect. The message handler loads the message action rule, but the rule is not saved in the RMS database. Recovery. This message is informational only; no recovery action is necessary. RMS6001 TIMER INACTIVATED Cause. You selected a time-based rule from your Active RMS Timers panel, changed the value in the Status field on the Time-Based Rule Definition panel to INACTIVE, and pressed F3 to save the change. Effect. The timer based on the rule is inactivated.
RMS Messages RMS6006 rms-record can have one of the following values: ELEMENT can be the record of the control options, profile, or function key settings TIMER is the record of a time-based rule function-performed can have one of the following values: ADDED indicates that a new record was created MODIFIED indicates that an existing record was selected and modified Effect.
RMS Messages RMS6010 RMS6007 RULE MODIFIED AND INACTIVATED Cause. You typed an IN (INact) action code next to a message action rule on your Message Action Rules Maintenance selection list panel, and pressed ENTER to inactivate the rule. The rule is in a ruleset that is associated with a message handler. The value in the Status column on the panel, and for the Status field in the definition for this rule, becomes INACTIVE. Effect.
RMS Messages RMS6011 RMS6011 rms-record DELETED Cause. You typed the D (Del) action code next to one or more rules on your Message Action Rules Maintenance selection list panel or Time-Based Rules Maintenance selection list panel, and pressed ENTER to delete the rules. For message action rules, some of the selected rules are either in an INACTIVE status or are in rulesets that are not associated with a message handler. You pressed ENTER and confirmed the deletion request.
RMS Messages RMS6015 RMS6013 rms-record function-performed AND ACTIVATED Cause. You added or modified a control options, profile, function key settings, message action rule, or time-based rule record in the RMS database through the Rule Maintenance option, and saved the record with the Activation field set to I (Immediate).
RMS Messages RMS6017 Effect. The record is saved in the RMS database but is not available to currently executing message handlers. Recovery. This message is informational only; no recovery action is necessary. RMS6017 RULE(S) ALREADY EXIST Cause. You typed the CP (Copy) action code next to one or more rules or command groups on your selection list panel, and pressed ENTER to copy the rules or command groups to another ruleset.
RMS Messages RMS6025 Note that you can swap to your other OCS window to access the Time-Based Rules Maintenance panel and perform the recovery action without having to exit your current panel. RMS6019 COMMAND GROUP DOES NOT EXIST FOR RULESET ruleset-name Cause. You were adding or modifying a message action rule, a message group rule, or a time-based rule in the ruleset, ruleset-name, but the command group in the Exec Cmd Group field on your rule definition panel does not exist in ruleset-name.
RMS Messages RMS6030 function-performed can have one of the following values: ADDED indicates that a new record was created MODIFIED indicates that an existing record was selected and modified If rms-record is ELEMENT, the record belongs to a ruleset that is associated with currently executing message handlers; if rms-record is TIMER, the status of the time-based rule is ACTIVE. Effect.
RMS Messages RMS6034 RMS6032 ACTIVATION MUST BE I, N, OR D Cause. You specified an invalid value in the Activation field on your data entry panel. This panel could be the last page of the control options definition panel (the Control Options Definition—Statistics panel), page 5 of the message action rule definition panels (the System Action panel), the Time-Based Rule Definition panel, the Profile Definition panel, or the last page of the Function Key Settings panels. Effect. The value is not accepted.
RMS Messages RMS6035 You cannot copy records in a ruleset or a message set to itself. Effect. The value is not accepted. The copying operation is not performed. The invalid name is highlighted. Recovery. Change the invalid name to a valid name before requesting the action again. If the copy operation is between rulesets, valid values are the names of existing rulesets in the RMS database that are different from the ruleset from which you are copying the records.
RMS Messages RMS6038 RMS6036 AT LEAST ONE DAY MUST BE SELECTED Cause. You specified the value N in each of the On Days fields on your data entry panel. This panel could be page 2 of the message action rule definition panels (the second Message Validation panel) or the Time-Based Rule Definition panel. The action you requested requires a value of Y in at least one of the On Days fields. Effect. The value is not accepted. The action is not performed. The invalid values are highlighted. Recovery.
RMS Messages RMS6039 RMS6039 INTENSITY MUST BE H(IGH), L(OW), OR BLANK Cause. You specified an invalid value in the Intens field on your data entry panel. This panel could be page 4 of the message action rule definition panels (the Message Modification panel) or page 2 of the message group rule definition panels (the Message Parameters panel). Effect. The value is not accepted. The action is not performed. Recovery.
RMS Messages RMS6050 RMS6042 REPLACEMENT METHOD MUST BE ENTERED Cause. You specified text in one or more of the Replacement Text fields (lines 1 through 10) but no value in the Replacement Method field on your data entry panel. This panel could be page 4 of the message action rules definition panels (the Message Modification panel) or page 2 of the message group rules definition panels (the Message Parameters panel). You must specify the replacement method and text together or not at all. Effect.
RMS Messages RMS6051 You cannot copy messages to a message set that is not in the RMS database. The name of the message set to which you want to copy the messages must exist in the RMS database. Effect. The value is not accepted. The copying operation is not performed. Recovery. Change the invalid name to a valid name before requesting the action again.
RMS Messages RMS6104 RMS6102 WARNING - MESSAGE GROUP DOES NOT EXIST FOR RULESET ruleset-name Cause. You were adding or modifying a message action rule in the ruleset, ruleset-name, but the name in one or more of the Message Group ID fields on your System Action panel did not refer to existing message group rules in the ruleset. The action you requested requires either names of message group rules that exist in the ruleset, or blanks in those fields. Effect. The action is not performed.
RMS Messages RMS6105 A default for the Message Action ID field is available under the following conditions: You specify a value in the Message ID or the SS ID field. The value does not contain wild-card characters and is not a variable. You can press ENTER to check that a default for the Message Action ID field is available. The default is displayed in the Default value field on your panel.
RMS Messages RMS6111 Recovery. Change the invalid value to one that uses the wild-card characters correctly before requesting the action again. The question mark (?) character represents one character, and can be used anywhere in the value except as the first character. The asterisk (*) character represents zero or more characters, and can only be used as the last character in the value where this character is not the only character.
RMS Messages RMS6113 Recovery. Change the invalid value to one of BEFORE (set the variables before any rule actions are executed) or AFTER (set the variables after all rule actions are executed) before requesting the action again. RMS6113 DO ACTIONS MUST BE ENTERED Cause. You specified values in the Threshold Maxcnt and Interval fields but no value in the Do Actions field on page 4 of the message action rule definition panels (Message Modification panel).
RMS Messages RMS6120 Recovery. Specify the time interval within which messages below the message threshold (defined in the Maxcnt field) are delivered or suppressed (as defined through the Deliver field) in the Interval field before requesting the action again. The value is in the format hh:mm:ss, and in the range 00:00:00 through 23:59:59. If you have not specified a value in either the Maxcnt or Do Actions field, you should also specify a value in that field.
RMS Messages RMS6122 RMS6122 PURGE TIME MUST BE BLANK IF MESSAGE GROUP ID IS BLANK Cause. You specified a value in one of the Purge After fields on page 5 of the message action rule definition panels (System Action panel) but no value in the corresponding Message Group ID field. Effect. The value is not accepted. The action is not performed. Recovery. Ensure that the Purge After field is blank before requesting the action again.
RMS Messages RMS6127 Recovery. Specify the text (with which the message text is to be compared using the specified operator) in the corresponding Scan Text field before requesting the action again. If the operator is LK, you can use the underscore (_) wild-card character to represent one character and the percent (%) wild-card character to represent zero or more characters.
RMS Messages RMS6128 Recovery. Specify the text (with which a word in the message text identified by the position specified in the Word Num field is to be compared) in the corresponding Scan Text field and ensure that there is an operator in the Opr field before requesting the action again. If the operator is LK, you can use the underscore (_) wild-card character to represent one character and the percent (%) wild-card character to represent zero or more characters.
RMS Messages RMS6132 The expression must relate all the tests specified under MESSAGE TEXT ANALYSIS: The numbers 1 through 5 identify the tests (which are Boolean expressions). You relate them by the operators AND and OR to form a single Boolean expression. You use the parentheses to order the evaluation of the expression. You use the unary operator NOT or ^ to negate a Boolean result. The following is a sample expression: (1 AND 3) OR ^(2 AND 4).
RMS Messages RMS6133 The following is a sample expression: (1 AND 3) OR ^(2 AND 4). An AND or OR operator must be between two Boolean expressions. A NOT or ^ operator must be followed by a Boolean expression. Parentheses must be matched pairs, and there must be a Boolean expression between each pair of parentheses. RMS6133 MISMATCHED PARENTHESES Cause.
RMS Messages RMS6141 Effect. The action is not performed. This error message appears on the third line of the your current panel. If you are on the System Action panel, the Load Ruleset field is highlighted. Recovery. If you are not currently on the System Action panel, page to the System Action panel. Specify the name of an existing ruleset in the Load Ruleset field before requesting the action again.
RMS Messages RMS6141 RMS6141 SCAN TEXT NOT REFERENCED IN SCAN OPERATOR STRING Cause. You specified an invalid expression in the RELATIONSHIP BETWEEN ANALYSIS CRITERIA field on page 3 of the message action rule definition panels (third Message Validation panel). The expression did not include one or more of the numbers that refers to specified tests under MESSAGE TEXT ANALYSIS. The action you requested requires that the expression includes all (and only) the specified tests. Effect.
RMS Messages RMS6201 RMS6143 ACCESS TO NEXT PAGE REQUIRES SET VARIABLES=YES Cause. You pressed the F8 function key on page 5 of the message action rule definition panels (System Action panel) to page forward to page 6 (Set Ruleset Variables panel) but the Set Variables field on the panel did not have the value YES. Paging forward on this panel requires the Set Variables field to have the value YES. Effect. Your System Action panel remains displayed. Recovery.
RMS Messages RMS6202 Effect. The action is not performed. The first Rule ID field is highlighted. Recovery. Specify a value in at least one of the Rule ID fields before requesting the action again. The values must be valid message action rule names: that is, up to eight characters, each of which must be an alphanumeric character, @, #, or $. If you specify the name of a message action rule that does not exist in this ruleset, a warning message will appear.
RMS Messages RMS6309 Recovery. This message is a warning only—if you request the action a second time, the value will be accepted and the action performed. RMS6205 NO DUPLICATES ALLOWED FOR RULE ID Cause. You specified the name of the same message action rule in more than one of the Rule ID fields on your Message Group Definition panel. Effect. The values are not accepted. The Rule ID fields that contain duplicated rules are highlighted. Recovery.
RMS Messages RMS6309 RMS6309 TIMER ID MUST BE ENTERED Cause. While adding a time-based rule, you left the Timer ID field blank on your Time-Based Rule Definition panel. Effect. The action is not performed. Recovery. Specify the name of the time-based rule in the Timer ID field before requesting the action again. The name can contain up to 12 characters. Valid characters are alphanumeric characters, @, #, and $.
RMS Messages RMS6317 Recovery. Specify a value in the Every field before requesting the action again. The value is a time interval in the format hh:mm:ss, and between the value specified in the EVCMDMIN system parameter and 24:00:00, inclusive. The value indicates the time interval at which you want the rule actions repeated. Alternatively, if you want the rule actions performed only once on specified days or a date, delete the value in the Limit field before requesting the action again.
RMS Messages RMS6401 Effect. The timer is not activated. If the Activation field setting is I, the definition of the time-based rule is saved in the RMS database. Recovery. Issue the command SUBMIT BMON START ZRMSTMRN to restart the timer driver.
RMS Messages RMS6505 RMS6404 COMMAND GROUP ID ALREADY EXISTS Cause. While adding a command group, you specified the name of a command group that already exists in this ruleset in the Command Group ID field on your Command Group Definition panel. Effect. The value is not accepted. The action is not performed. Recovery. Change the value in the Command Group ID field to one that is not the name of an existing command group in this ruleset before requesting the action again.
RMS Messages RMS6506 Recovery. Change the invalid value to one of YES, Y, NO, N, HM (hour and minute), or HMS (hour, minute, and second) before requesting the action again. If you do not want to change the PRFTM profile parameter (which determines whether to prefix unsolicited messages with a timestamp), delete the value in the PRFTM field. RMS6506 GUID MUST BE IN THE FORMAT nnn,nnn Cause. You specified an improperly formatted value in the GUID field on your Profile Definition panel. Effect.
RMS Messages RMS7008 Recovery. This message is informational only; no recovery action is necessary. If you expect to trigger some rules, check the rule definitions. RMS7005 SIMULATION STARTING - LOADING TABLES Cause. You selected option 1 (Message Arrival Simulation), option 3 (Capture Msg Flow and RMS Activity), or option 4 (Simulate RMS Activity on Saved Msg Set) on your Event Simulation panel. RMS was initializing the simulation session before starting the message handler. Effect.
RMS Messages RMS7008 RMS7008 PARAMETER OVERRIDE CANCELED AFTER 5 RETRIES Cause. You selected option 1 (Message Arrival Simulation), option 3 (Capture Msg Flow and RMS Activity), or option 4 (Simulate RMS Activity on Saved Msg Set) on your Event Simulation panel. RMS initialized the simulation session and was waiting for the start of the message handler. RMS was unable to detect the start of the handler and aborted the simulation session. Effect. RMS aborts the simulation session. Recovery.
RMS Messages RMS7018 RMS7013 (PARTIAL) RULE ID rule-id NOT FOUND Cause. You issued the LOCATE rule-id command at the Command prompt on your Event Simulation—Triggered Actions panel. rule-id does not match, either partially or fully, the name of a triggered rule. Effect. The list of triggered rules displayed on your panel is unchanged. Recovery. This message is informational only; no recovery action is necessary. RMS7014 record-count RECORDS DELETED Cause.
RMS Messages RMS7019 Effect. The messages are not copied. The field in which you should specify the message set is highlighted. Recovery. Enter the name of the message set in the highlighted field before requesting the action again. The message set may or may not have to be an existing message set depending on the function selected. If you want, you can cancel the operation by pressing F12. RMS7019 TARGET NAME ALREADY EXISTS Cause.
RMS Messages RMS7024 Recovery. This message is informational only; no recovery action is necessary. You can delete messages that you do not need anymore from the filled message set and retry the operation. RMS7022 MUST BE MON, TUE, WED, THU, FRI, SAT, OR SUN Cause. You typed the S (Select) action code next to a message on your Captured Message Set Edit panel, and pressed ENTER. You specified an invalid value in the Day field on the Saved Message Editing panel. Effect. The value is not accepted.
RMS Messages RMS8008 Effect. The new message set is created in the RMS database to which the messages are copied. Recovery. This message is informational only; no recovery action is necessary. RMS8008 ENTER MESSAGE STATISTICS SORT CRITERIA Cause. You specified a value in the Sort Rule Hit Statistics by field but deleted the value in the Sort Messages Statistics by field on your Statistics Sort Options panel. Effect. The action is not performed. The Sort Messages Statistics by field is highlighted.
RMS Messages RMS9006 Recovery. This message is informational only; no recovery action is necessary. RMS9003 SUBJECT NO LONGER ACTIVE Cause. The active subject you were operating on is no longer active. The message appears when one of the following occurs: You used the S action code to display the rule actions on an active subject on your Active Message Subjects panel, but the subject you selected is no longer active.
RMS Messages RMS9007 RMS9007 ERROR READING RESPONSE TO SHOW LOCKS/NCL: intread-error Cause. An error occurred while you were attempting to retrieve a list of active subjects or rule actions. intread-error is one of the following: TIMEOUT System loading problems caused a timeout to occur. Look for activities that may cause the loading problems, and correct the problems before retrying. MSGS LOST Excessive RMS activities caused loss of messages.
RMS Messages RMS9014 RMS9012 SUBJECT ALREADY THAWED Cause. You used the T action code to thaw a subject listed on your Frozen Message Subjects panel, but another user thawed the subject since your list of frozen subjects was displayed. Effect. The selected subject remains thawed. Recovery. This message is informational only; no recovery action is necessary. RMS9013 SUBJECT USER MANAGER DATE/TIME FROZEN BY Cause. An RMS DISPLAY FROZEN command was issued and the message is part of the response.
RMS Messages RMS9015 RMS9015 subject-name manager-name freeze-date freeze-time user-id Cause. An RMS DISPLAY FROZEN command was issued and the message is part of the response. The line contains information about a frozen subject. Message RMS9013 contains the headings for the information. subject-name is the name of the subject. manager-name is the name of the manager of the subject if it was specified in the freeze operation.
RMS Messages RMS9020 Effect. The headings are displayed. Recovery. This message is informational only; no recovery action is necessary. RMS9018 ---------------- ------------ -------- ------------ -------- ----Cause. An RMS DISPLAY command was issued and the message is part of the response. The line separates the headings from the details of the RMS DISPLAY command. Effect. The separation line is displayed. Recovery. This message is informational only; no recovery action is necessary.
RMS Messages RMS9021 RMS9021 ID MSG ID SYSTEM ACTION RULESET RULE ID MSGTIME Cause. An RMS DISPLAY QUEUED command was issued and the message is part of the response. The line contains the headings for information about queued rule actions for a given subject. Other messages provide the actual information. ID is the heading for the NCL ID of the rule action. SYSTEM ACTION is the heading for the action defined in the rule. RULESET is the heading for the ruleset containing the triggered rule.
RMS Messages RMS9027 Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. RMS9024 STATUS: action-status HANDLER: mh-nclid ACTION TYPE: action-type MSG Cause. An RMS DISPLAY QUEUED command was issued with DETAIL=YES. This is part of the detailed response containing information about the queued rule actions. action-status is ACTIVE (currently executing), QUEUED (queued in memory), or DISK (queued on disk to an NCL queue).
RMS Messages RMS9028 This message could be one of several RMS9027 messages displaying the message text of the triggering message. message-text is detailed message text. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. RMS9028 number-queued QUEUED ACTIONS DISPLAYED Cause. An RMS DISPLAY QUEUED command was issued and the message is the last line of the response. number-queued is the number of queued actions displayed.
RMS Messages RMS9034 SYSTEM ACTION is the heading for the action defined in the rule. RULESET is the heading for the ruleset containing the triggered rule. RULE ID is the heading for the triggered rule ID. RETRYTIME is the heading for the time the action will retry. RETRY is the heading for the retry number of this action. Effect. The headings are displayed. Recovery. This message is informational only; no recovery action is necessary.
RMS Messages RMS9035 date-time is the date and time that the rule action procedure is scheduled for execution. delay-secs is the number of seconds of delay requested by the rule action procedure before it is retried. Effect. The information is retrieved and displayed. Recovery. This message is informational only; no recovery action is necessary. RMS9035 MSG TIME: msg-time SUBJECT: subject-name Cause. An RMS DISPLAY DELAYED command was issued with DETAIL=YES.
RMS Messages RMS9041 RMS9038 NO DELAYED MESSAGE ACTIONS Cause. You selected option 4 from your Message Action Control panel to display the delayed actions on your system, but no delayed actions that matched your selection criteria in the Subject and Manager fields were found. Effect. The action is not performed. Recovery. This message is informational only; no recovery action is necessary. RMS9039 DELAYED MESSAGE ACTION DELETED Cause.
RMS Messages RMS9900 RMS9900 subsystem-name component-type component-name UNEXPECTED RESPONSE TO OPSYS COMMAND: Cause. A message triggered a message action rule in ruleset BASERULE associated with a message handler and caused the issue of an OPSYS command to perform recovery action on the component, component-name. An unexpected response was returned by NonStop NET/MASTER MS. subsystem-name is the name of the subsystem that owns the component, and component-type is the type of component.
RMS Messages RMS9904 RMS9902 subsystem-name component-type component-name RECOVERY COMPLETE. STATUS: current-state Cause. A message triggered a message action rule in ruleset BASERULE associated with a message handler and caused the message handler to perform recovery action on the component, component-name. The component was recovered. subsystem-name is the name of the subsystem that owns the component, and component-type is the type of component.
RMS Messages RMS9905 subsystem-name is the name of the subsystem that owns the component, and component-type is the type of component. For example, subsystem-name can be EXPAND, component-type can be LINE, and component-name can be the name of the Expand line. Effect. The recovery action on the component fails. Recovery. Perform the recovery action on the component manually. RMS9905 subsystem-name component-type component-name UNEXPECTED RESPONSE TO: command-type Cause.
RMS Messages RMS9910 RMS9907 TACL TERM terminal-name io-type ERROR ON FILE file-name error-text Cause. A message triggered the message action rule ZTACLFAIL in ruleset BASERULE associated with a message handler and caused the execution of the file operation, io-type, on the file, file-name, as part of the recovery action on the TACL process for the terminal, terminal-name. The indicated error occurred: error-text. io-type is one of the following: OPEN or READ.
RMS Messages RMS9911 RMS9911 GUARDIAN CPU cpu-number - message-text Cause. An RMS rule could not perform an automated function that was not essential to recover the CPU, cpu-number. message-text provides information on the problem. Effect. Recovery of the component continues. Recovery. This message is informational only; no recovery action is necessary.
Appendix B RMS Commands This appendix describes the syntax and use of the RMS commands. RMS commands are issued at an Operator Control Services (OCS) window. RMS commands are NCL procedures that can be executed from the OCS command input line. You can use the following RMS commands: Command Function RMS DELETE ACTIVE RMS DELETE DELAYED RMS DELETE QUEUED RMS DISPLAY ACTIVE RMS DISPLAY DELAYED RMS DISPLAY FROZEN RMS DISPLAY QUEUED RMS FREEZE Deletes active subjects. Deletes delayed message actions.
RMS Commands RMS DELETE ACTIVE RMS DELETE ACTIVE The RMS DELETE ACTIVE command deletes active subjects. RMS DELETE ACTIVE SUBJECT=subject [ MANAGER=manager ] SUBJECT=subject specifies the name of a subject. You can specify a subject from 1 through 34 characters long. MANAGER=manager specifies the name of the manager. You can specify a manager from 1 through 32 characters long. If there is a manager associated with the specified subject, you must specify the manager.
RMS Commands RMS DELETE DELAYED RMS DELETE The RMS DELETE DELAYED command deletes delayed message actions. These are DELAYED message actions that have requested a retry after a delay. RMS DELETE DELAYED ID=ncl-id ID=ncl-id specifies the NCL ID of a delayed message action. You can determine an NCL ID by using the RMS DISPLAY DELAYED command. Consideration You can use the EQUATE command to assign a lengthy command string to a single character or sequence of characters.
RMS Commands RMS DELETE QUEUED RMS DELETE QUEUED The RMS DELETE QUEUED command deletes queued rule actions. RMS DELETE QUEUED ID=ncl-id ID=ncl-id specifies the NCL ID of a queued rule action. You can determine an NCL ID by using the RMS DISPLAY QUEUED command. Consideration You can use the EQUATE command to assign a lengthy command string to a single character or sequence of characters.
RMS Commands RMS DISPLAY ACTIVE RMS DISPLAY ACTIVE The RMS DISPLAY ACTIVE command displays information about active subjects. If you do not specify a subject or a manager, information about all active subjects under all managers are displayed. RMS DISPLAY ACTIVE [ SUBJECT=subject [ MANAGER=manager ] ] SUBJECT=subject specifies the name of a subject and, additionally, names beginning with subject. You can specify a subject from 1 through 34 characters long.
RMS Commands RMS DISPLAY DELAYED RMS DISPLAY The RMS DISPLAY DELAYED command displays information about delayed message DELAYED actions. If you do not specify a subject or a manager, information about all delayed message actions under all managers are displayed. RMS DISPLAY DELAYED [ SUBJECT=subject [ MANAGER=manager ] ] [ DETAIL={ YES | NO } ] SUBJECT=subject specifies the name of a subject and, additionally, names beginning with subject. You can specify a subject from 1 through 34 characters long.
RMS Commands RMS DISPLAY DELAYED Examples 1. The following example displays information about all delayed message actions under all managers: RMS DISPLAY DELAYED 2. The following example displays information about all delayed message actions for subjects beginning with $LINE (for example, $LINE1, $LINE2, $LINEZ, $LINE99, and so on): RMS DISPLAY DELAYED SUBJECT=$LINE 3.
RMS Commands RMS DISPLAY FROZEN RMS DISPLAY The RMS DISPLAY FROZEN command displays information about frozen subjects. If FROZEN you do not specify a subject or a manager, information about all frozen subjects under all managers are displayed. RMS DISPLAY FROZEN [ SUBJECT=subject [ MANAGER=manager ] ] SUBJECT=subject specifies the name of a subject and, additionally, names beginning with subject. You can specify a subject from 1 through 34 characters long.
RMS Commands RMS DISPLAY QUEUED RMS DISPLAY The RMS DISPLAY QUEUED command displays information about rule actions QUEUED queued to a specific subject. RMS DISPLAY QUEUED SUBJECT=subject [ MANAGER=manager ] [ DETAIL={ YES | NO } ] SUBJECT=subject specifies the name of a subject. You can specify a subject from 1 through 34 characters long. MANAGER=manager specifies the name of the manager. You can specify a manager from 1 through 32 characters long.
RMS Commands RMS DISPLAY QUEUED Examples 1. The following example displays information about all rule actions queued to the subject $LINE1: RMS DISPLAY QUEUED SUBJECT=$LINE1 2.
RMS Commands RMS FREEZE RMS FREEZE The RMS FREEZE command enables you to freeze a subject so that when a message handler receives a message containing that subject, the message cannot trigger any rules. RMS FREEZE SUBJECT=subject [ MANAGER=manager ] SUBJECT=subject specifies the name of the subject. You can specify a subject from 1 through 34 characters long. When you specify only a subject, only messages containing a subject of that name (irrespective of the manager) are frozen.
RMS Commands RMS THAW RMS THAW The RMS THAW command enables you to thaw a frozen subject so that when a message handler receives a message containing that subject, the message can trigger any rules again. RMS THAW SUBJECT=subject [ MANAGER=manager ] SUBJECT=subject specifies the name of the subject. You can specify a subject from 1 through 34 characters long. If you specified a manager when freezing a subject, you must specify the same manager when thawing the subject.
RMS Commands RMS THAW Examples 1. The following example thaws the subject named $LINE1: RMS THAW SUBJECT=$LINE1 2. The following example thaws the subject named TERM1 under the manager $XXPM: RMS THAW SUBJECT=TERM1 MANAGER=$XXPM 3.
RMS Commands RMS XFER RMS XFER The RMS XFER command enables you to transfer a ruleset, and the records of the ruleset, from one RMS database to another RMS database. If the transfer is successful, a message is displayed indicating the number of records transferred.
RMS Commands RMS XFER RULESET=ruleset2 specifies the new name for the transferred ruleset. If no ruleset name is specified, the ruleset name defaults to the name of the ruleset being transferred. OPTION={ M | R } specifies whether the ruleset from the source database entirely replaces the target ruleset in the destination database, or whether the source ruleset merges with the target ruleset in the destination database. To replace the target ruleset, specify R; to merge the rulesets, specify M.
RMS Commands RMS XFER Immediate activation, if specified, occurs only when the destination database is the current RMS database ZRMSDB. Immediate activation of the ruleset occurs when the current message has completed processing. You can use the EQUATE command to assign a lengthy command string to a single character or sequence of characters. For example: EQUATE XFER RMS XFER Example The following example transfers the ruleset SAMPLE from the current database ZRMSDB to the file $DATA2.HENRY.
Appendix C RMS Procedure Calls This appendix describes the syntax of RMS procedure calls. RMS procedure calls enable you to call NCL procedures that have been defined to perform RMS functions from a user NCL procedure. RMS procedure calls allow you to automate some RMS functions by using RMS rules and customer applications. RMS procedure calls include the name of the NCL procedure and the invocation parameters.
RMS Procedure Calls ZRMSAPIN ( DELACTIVE ) ZRMSAPIN ( DELACTIVE ) The ZRMSAPIN ( DELACTIVE ) procedure call deletes active subjects. CALL ZRMSAPIN ( DELACTIVE, subject [, manager ] ) SHARE &SYSMSG subject specifies the name of a subject. You can specify a subject from 1 through 34 characters long. manager specifies the name of the manager. You can specify a manager from 1 through 32 characters long. If there is a manager associated with the specified subject, you must specify the manager.
RMS Procedure Calls ZRMSAPIN ( DELDELAYED ) ZRMSAPIN ( DELDELAYED ) The ZRMSAPIN ( DELDELAYED ) procedure call deletes delayed message actions. These are message actions that have requested a retry after a delay. CALL ZRMSAPIN ( DELDELAYED, ncl-id ) SHARE &SYSMSG ID=ncl-id specifies the NCL ID of a delayed message action. You can determine an NCL ID by using the ZRMSAPIN ( GETDELAYED ) procedure call. Consideration After the ZRMSAPIN ( DELDELAYED ) procedure call completes, the system variable &SYS.
RMS Procedure Calls ZRMSAPIN ( DELQUEUED ) ZRMSAPIN ( DELQUEUED ) The ZRMSAPIN ( DELQUEUED ) procedure call deletes queued rule actions. CALL ZRMSAPIN ( DELQUEUED, ncl-id ) SHARE &SYSMSG ID=ncl-id specifies the NCL ID of a queued rule action. You can determine an NCL ID by using the ZRMSAPIN ( GETQUEUED ) procedure call. Consideration After the ZRMSAPIN ( DELQUEUED ) procedure call completes, the system variable &SYS.
RMS Procedure Calls ZRMSAPIN ( GETACTIVE ) ZRMSAPIN ( GETACTIVE ) The ZRMSAPIN ( GETACTIVE ) procedure call retrieves information about active subjects. If you do not specify a subject or a manager, information about all active subjects under all managers is retrieved. CALL ZRMSAPIN ( GETACTIVE [, subject [, manager ] ] ) SHARE &RMS., &SYSMSG SUBJECT=subject specifies the name of a subject and, additionally, names beginning with subject. You can specify a subject from 1 through 34 characters long.
RMS Procedure Calls ZRMSAPIN ( GETACTIVE ) Examples 1. The following example illustrates a user NCL procedure that retrieves information about all active subjects under all managers: SAMPLE: PROCEDURE CALL ZRMSAPIN (GETACTIVE) SHARE &RMS.,&SYSMSG END SAMPLE 2.
RMS Procedure Calls ZRMSAPIN ( GETDELAYED ) ZRMSAPIN ( GETDELAYED ) The ZRMSAPIN ( GETDELAYED ) procedure call retrieves information about delayed message actions. CALL ZRMSAPIN ( GETDELAYED [, subject [, manager ] ] ) SHARE &RMS., &SYSMSG SUBJECT=subject specifies the name of a subject and, additionally, names beginning with subject. You can specify a subject from 1 through 34 characters long. MANAGER=manager specifies the name of the manager. You can specify a manager from 1 through 32 characters long.
RMS Procedure Calls ZRMSAPIN ( GETDELAYED ) After the ZRMSAPIN ( GETDELAYED ) procedure call completes, the following variables contain additional information: Variable Contains &RMS.DELAYED.ACTNAME.n &RMS.DELAYED.ACTION.n Type of delayed action n: NCLPROC or COMMAND. NCL procedure or command, and arguments for rule action n. Manager of subject n. Message text for delayed action n. Message time for delayed action n. NCL ID of rule action n. NCL queue of execution for delayed action n.
RMS Procedure Calls ZRMSAPIN ( GETDELAYED ) Examples 1. The following example illustrates a user NCL procedure that retrieves information about all delayed message actions under all managers: SAMPLE: PROCEDURE ZRMSAPIN (GETDELAYED) SHARE &RMS.,&SYSMSG END SAMPLE 2.
RMS Procedure Calls ZRMSAPIN ( GETFROZEN ) ZRMSAPIN ( GETFROZEN ) The ZRMSAPIN ( GETFROZEN ) procedure call retrieves information about frozen subjects. If you do not specify a subject or a manager, information about all frozen subjects under all managers is retrieved. CALL ZRMSAPIN ( GETFROZEN [, subject [, manager ] ] ) SHARE &RMS., &SYSMSG SUBJECT=subject specifies the name of a subject and, additionally, names beginning with subject. You can specify a subject from 1 through 34 characters long.
RMS Procedure Calls ZRMSAPIN ( GETFROZEN ) Examples 1. The following example retrieves information about all frozen subjects under all managers: SAMPLE: PROCEDURE CALL ZRMSAPIN (GETFROZEN) SHARE &RMS.,&SYSMSG END SAMPLE 2. The following example retrieves information about all frozen subjects beginning with $LINE (for example, $LINE1, $LINE2, $LINEZ, $LINE99, and so on): SAMPLE: PROCEDURE &SUB=“$LINE” CALL ZRMSAPIN (GETFROZEN,&SUB) SHARE &RMS.,&SYSMSG END SAMPLE 3.
RMS Procedure Calls ZRMSAPIN ( GETQUEUED ) ZRMSAPIN ( GETQUEUED ) The ZRMSAPIN ( GETQUEUED ) procedure call retrieves information about rule actions queued to a specific subject. CALL ZRMSAPIN ( GETQUEUED, subject [, manager ] ) SHARE &RMS., &SYSMSG SUBJECT=subject specifies the name of a subject. You can specify a subject from 1 through 34 characters long. MANAGER=manager specifies the name of the manager. You can specify a manager from 1 through 32 characters long.
RMS Procedure Calls ZRMSAPIN ( GETQUEUED ) After the ZRMSAPIN ( GETQUEUED ) procedure call completes, the following variables contain additional information: Variable Contains &RMS.QUEUED.ACTION.n &RMS.QUEUED.MANAGER &RMS.QUEUED.MHNCLID.n &RMS.QUEUED.MSGTEXT.n &RMS.QUEUED.MSGTIME.n &RMS.QUEUED.NCLID.n &RMS.QUEUED.NCLQUEUE.n &RMS.QUEUED.NUM &RMS.QUEUED.REGION.n &RMS.QUEUED.RULEID.n &RMS.QUEUED.RULESET.n &RMS.QUEUED.STATUS.n &RMS.QUEUED.SUBJECT &RMS.QUEUED.TYPE.
RMS Procedure Calls ZRMSAPIN ( FREEZE ) ZRMSAPIN ( FREEZE ) The ZRMSAPIN ( FREEZE ) NCL procedure call enables you to freeze a subject so that when a message handler receives a message containing that subject, the message cannot trigger any rules. CALL ZRMSAPIN ( FREEZE, subject [, manager ] ) SHARE &SYSMSG SUBJECT=subject specifies the name of the subject. You can specify a subject from 1 through 34 characters long.
RMS Procedure Calls ZRMSAPIN ( FREEZE ) Examples 1. The following example illustrates a user NCL procedure that freezes the subject named $LINE1: SAMPLE: PROCEDURE &SUB=“$LINE1” CALL ZRMSAPIN (FREEZE,&SUB) SHARE &SYSMSG END SAMPLE 2. The following example illustrates a user NCL procedure that freezes the subject named TERM11 under the manager $XXPM: SAMPLE: PROCEDURE &SUB=“TERM1” &MGR=“$XXPM” CALL ZRMSAPIN (FREEZE,&SUB,&MGR) SHARE &SYSMSG END SAMPLE 3.
RMS Procedure Calls ZRMSAPIN ( THAW ) ZRMSAPIN ( THAW ) The ZRMSAPIN ( THAW ) procedure call enables you to thaw a frozen subject so that when a message handler receives a message containing that subject, the message can trigger any rules. CALL ZRMSAPIN ( THAW, subject [, manager ] ) SHARE &SYSMSG SUBJECT=subject specifies the name of the subject. You can specify a subject from 1 through 34 characters long.
RMS Procedure Calls ZRMSAPIN ( THAW ) Examples 1. The following example illustrates a user NCL procedure that thaws the subject named $LINE1: SAMPLE: PROCEDURE &SUB=“$LINE1” CALL ZRMSAPIN (THAW,&SUB) SHARE &SYSMSG END SAMPLE 2. The following example illustrates a user NCL procedure that thaws the subject named TERM1 under the manager $XXPM: SAMPLE: PROCEDURE &SUB=“TERM1” &MGR=“$XXPM” CALL ZRMSAPIN (THAW,&SUB,&MGR) SHARE &SYSMSG END SAMPLE 3.
RMS Procedure Calls ZRMSAPIN ( XFER ) ZRMSAPIN ( XFER ) The ZRMSAPIN ( XFER ) procedure call enables you to transfer a ruleset, and the records of the ruleset, from one RMS database to another RMS database. CALL ZRMSAPIN ( XFER, from-db-type, from-db, from-ruleset, to-db-type, to-db [, to-ruleset ] [, option ] [, activate ] ) SHARE &SYSMSG from-db-type specifies whether from-db is a Guardian-format file name or a UDB file ID. If you are transferring from a Guardian-format file name, specify FNAME.
RMS Procedure Calls ZRMSAPIN ( XFER ) The file name is in the following format: [ \sys. ][ $volume. ][ subvolume. ]filename If you specify the UDB file ID, you must specify a file ID that is one through eight characters long, beginning with a character other than a digit. If you are transferring to the current database, specify ZRMSDB. to-ruleset specifies the new name for the transferred ruleset.
RMS Procedure Calls ZRMSAPIN ( XFER ) If the target ruleset does not exist on the destination database, a new ruleset is created with the specified ruleset name. Records belonging to the source ruleset are also transferred to the new ruleset in the destination database. Record locking occurs automatically during the transfer of the ruleset if the specified UDB file ID to which the ruleset is to be transferred is the current RMS database ZRMSDB; this is to ensure that the transferred data is consistent.
Glossary This glossary defines NonStop NET/MASTER and Tandem system terms and abbreviations used in this manual. %INCLUDE rule. An RMS message action rule that allows a message handler to use rules from more than one ruleset. %START rule. An RMS message action rule that instructs a message handler to perform user-defined initialization actions on startup. => prompt. Any prompt that ends with =>: for example, Command ===>, M=>, and Select Option ===>. absolute time.
Glossary attribute byte. The data that defines the display attributes of a field on a screen. The attribute byte is displayed as a blank on the screen. It is represented by a field character in a panel description file. authority level. A number assigned to users, NonStop NET/MASTER MS commands, and NonStop NET/MASTER MS operands that signifies the authority to execute a command or operand. Authority levels range from 0 (lowest) through 255 (highest). autohold.
Glossary BIU. See basic information unit. BK process. See background services process. blank concatenation operation. An operation that replaces multiple blanks between two terms in an expression by a single blank. block. A logical group of statements. Blocks are bounded by core statements such as PROCEDURE and END, FUNCTION and END, DO and END, and SELECT and END. BLOG. See Background Logger. BMON. See Background Monitor. Boolean.
Glossary COBOL85. The Tandem compiler and run-time support for the American National Standard Programming Language COBOL, X.3.23-1985. The code for most Pathway server processes is written using COBOL85. Command Entry facility. The NonStop NET/MASTER MS facility used as an alternative to OCS for entering commands. See also Operator Control Services. Command prompt. Command ===>. You enter commands at a Command prompt. Command Server Process.
Glossary communications network management (CNM). An IBM architecture that describes the structure of messages traveling to and from SNA devices. compilation. The process of creating object code from a source file of NCL statements. compilation error. An error in an NCL procedure detected during compilation (before execution). There are three types of compilation errors: from least to most severe these are warnings, errors, and fatal errors. See also error, fatal error, run-time error, and warning.
Glossary correlation key. An RMS key that restricts the use of a rule feature to messages with the same key. One example of a key is a text string containing variables. CPU weight. The relative availability of a CPU for the creation of dynamic processes. cultural indicator. An indicator that identifies the culture of command help information. culture.
Glossary DDL. See Data Definition Language. DDL data dictionary. A database consisting of prenamed and predefined files created by the DDL compiler or Pathmaker. deadly embrace. A situation in which a resource required by one NCL process is indefinitely locked by another NCL process. debug. To locate and correct errors in an NCL process. decompilation. The process of creating NCL statements from object code. Decompilation occurs during the debugging of an NCL process, when using the DEBUG commands.
Glossary delayed NCL process. An NCL process whose execution has been explicitly delayed. delete operator message (DOM) ID. The attribute of a full non-roll-delete message that uniquely identifies the message and is used to delete it. It consists of the domain ID of the system from which the message originated, and a NRD ID (a unique number assigned by NonStop NET/MASTER MS to the NRD message). delete record. A record in one file that logically deletes a record in a related file. delimited UDB.
Glossary distributed panel object file. The file distributed with NonStop NET/MASTER MS that contains the object code for most panel description files required by NonStop NET/MASTER MS. distributed procedure. An NCL procedure in the distribution procedure library. distribution panel library. A library that contains distributed panel description files. distribution procedure library.
Glossary element header. The beginning of an element. An element header consists of two parts: a length field and a key field. EM process. See event management services process. emergency shutdown. A shutdown operation started by the NonStop NET/MASTER MS control process (NCP). See also immediate shutdown and normal shutdown. EMS. See Event Management Service. EMS event collector. A Guardian process, part of the Tandem EMS subsystem, that collects and stores messages. The default EMS event collector is $0.
Glossary environment. An area in which NonStop NET/MASTER MS users, NonStop NET/MASTER MS commands, and NCL processes operate. An environment is designed to limit the default activities of these users, commands, and processes. environmental profile. A profile that determines what a user can do in an environment. The user can change certain aspects of this profile by using the NonStop NET/MASTER MS PROFILE command.
Glossary execution error. An error detected during the execution of an NCL process. execution limit. The maximum number of times a timer command executes or the maximum number of NCL processes that can concurrently execute in the specified queue for each NCL processing environment. exit NCL procedure. A user-written NCL procedure that can be invoked by and executes in line with an RMS message handler.
Glossary field-level justification. In a panel, the process of stripping trailing blanks, padding, and justifying the data in a field. fields list. In NCL, a list used by certain VARTABLE verbs introduced by the FIELDS operand. file pair. Two key-sequenced files that are treated as a single logical file in all file operations. See also UDB pair. fixed data. Data in an output field of a panel that cannot change when the panel is displayed. fixed length data section.
Glossary global memory (GM). Memory that holds information required by all NonStop NET/MASTER MS processes. Information is maintained by the global memory manager (GMM). global memory manager (GMM). The NonStop NET/MASTER MS component that manages information in global memory. global time-based rule. An RMS time-based rule that is independent of message flow. global variable. An NCL variable that is visible throughout NonStop NET/MASTER MS (the name begins with GLBL). global vartable.
Glossary implicit declaration. The definition of a procedure that does not begin with the PROCEDURE core statement. implicit execution. The execution of an NCL procedure without an explicit START or EXEC command. import. To transfer command help information from a command help edit file to the command help database. See also export. inbound message. An unsolicited message received by ISR on a local NonStop NET/MASTER MS system from a remote NonStop NET/MASTER MS or SOLVE management services system.
Glossary inter-system services (IS) process. The application process that supports INMC, ISR, and ROC for the multiprotocol exchange of commands, command-response messages, and event messages with another network management application (NonStop NET/MASTER MS, the SOLVE management services, or NetView). internal function. A function inside a source file. internal procedure. A procedure inside a source file. internal trace.
Glossary label. Within an NCL statement, a label is a symbol or quoted string (excluding hexadecimal and binary strings) that ends in a colon (:) and begins a statement. Labels are used to mark segments of code. length field. Part of a map header or element header. The value contained in the length field is the length of the data item. The length of the length field is normally included in the length of a data item. length variable specification.
Glossary logical name. A sequence of characters that can be used as an alias for a device name. logical NOT. The Boolean operator that negates 1 (TRUE) to 0 (FALSE) and FALSE to TRUE when evaluating two terms in an expression. logical unit (LU). An IBM term for a unit through which end user application programs and I/O devices access the SNA network to communicate with other end users. An LU2 is an IBM 3270 or compatible terminal using SNA protocols. logon screen.
Glossary Mapping Services. A proprietary architecture that allows data to be represented in a tokenized form suitable for passing between network management platforms. mask. A string of characters used as the basis of comparison with another string of characters. MDO variable. See mapped data object (MDO) variable. menu. A screen display that allows you to select an option to access a function. Message Services. The NonStop NET/MASTER MS service that controls message flow within NonStop NET/MASTER MS.
Glossary message trace. A trace of one or more message types. (Types are CNM messages, EMS messages, messages in dependent processing environments, log messages, and OCS messages). NonStop NET/MASTER MS supports multiple simultaneous message traces. message trace point. A NonStop NET/MASTER MS code position that can be identified for a message trace. message validation exit NCL procedure. An optional user exit NCL procedure that provides a final check on whether a message triggers the RMS rule. minor name.
Glossary native character set. For Tandem computers, the ASCII character set; for IBM computers, the EBCDIC character set. NC process. See NonStop NET/MASTER MS consolidated services process. NCL. See Network Control Language. NCL base procedure. See base procedure. NCL ID. See NCL process identifier. NCL object file search path. The search order through the NCL object file(s) defined as part of the search path for NCL procedures. NCL PATHSEND requester. A PATHSEND requester written in NCL. NCL procedure.
Glossary NMVT. See Network Management Vector Transport. NNM program. A program distributed with NonStop NET/MASTER MS that allows a user to log on to NonStop NET/MASTER MS from a dynamic terminal. non-roll-delete (NRD) message. A message that does not roll off the message display area of an OCS window. NRD messages report events of critical importance. There are two classes of NRD messages: full NRD messages and NRD messages with the OPER attribute. NonStop NET/MASTER Management Services (MS).
Glossary object. In NCL, the object code of a specific NCL procedure that is loaded into memory. In SPI, an entity subject to independent reference and control by a subsystem: for example, a disk file or a data communications line. An object typically has a name and a type known to the controlling subsystem. object code. NCL code in executable form. object file. A key-sequenced file containing the object code of all NCL procedures owned by a certain user. object procedure library.
Glossary operating mode. The mode in which NonStop NET/MASTER MS is running, defined by the mix and presence or absence of application processes. See also advanced mode, basic mode, and extended basic mode. Operator Control Services (OCS). The NonStop NET/MASTER MS service that provides the central point of operational control of the local Tandem system, the local NonStop NET/MASTER MS system, and remote systems. operator. In NCL, a lexical element used for working on terms in expressions.
Glossary panel queue. A central queue, maintained by NonStop NET/MASTER MS, that holds panels currently in use. The maximum size of the queue is set by the SYSPARMS MAXPANEL command. panel skipping. The ability to chain menu-selection requests together without having to display intermediate selection panels. Panel skipping is used in conjunction with direct function selection. parameter. A value passed from one procedure or function (the caller) to another procedure or function (the callee).
Glossary Pathway system. The TCPs, servers, terminals, programs, and any subsystems associated with Pathway that run together under the control of one PATHMON process. pend-unload list. A list, maintained by NonStop NET/MASTER MS, that holds in memory copies of NCL procedures that have been unloaded from the active list while still being executed. Peripheral Utility Program (PUP).
Glossary primary processing environment. A processing environment that is controlled and owned by an OCS window or a virtual user. The output from this environment goes to the OCS window or virtual user, respectively. primary program operator (PPO). In IBM terminology, an operator who is authorized to receive unsolicited messages. primary trigger. One of the RMS message recognition elements. You cannot change a primary trigger. private loading.
Glossary protected field. A field in a panel that cannot be updated by a user. PU. See physical unit. PUP. See Peripheral Utility Program. purge ID. An ID used to purge a timer command or NRD message. purge message. A message sent when a timer command is purged from the timer queue. qualification name list. A mapped data object variable specification that uniquely identifies an enclosed element. qualifier. The part of a NonStop NET/MASTER MS command that modifies the action taken by the command.
Glossary Remote Operator Control (ROC). The NonStop NET/MASTER MS service that allows users to log on from a local NonStop NET/MASTER MS system to a remote system; to execute NonStop NET/MASTER MS commands at the remote system; and to receive the results at the local system. remote command. A NonStop NET/MASTER MS command sent to a remote system. remote system. Any NonStop NET/MASTER MS or SOLVE management services system other than the local system. remote user.
Glossary retain list. A list, maintained by NonStop NET/MASTER MS if procedure sharing is allowed, that holds in memory copies of NCL procedures that have been previously executed but are currently not being executed. RETURN key. A key that returns to a NonStop NET/MASTER MS primary menu from any menu level when pressed. By default, the RETURN key is the F4 function key. RH. See request/response header. RMS. See Rule Management Services. RMS message variable.
Glossary ruleset. A set of RMS rules that defines responses to events such as message arrival and time conditions. A message handler uses the information in a ruleset to set up its execution environment and respond to incoming messages. A timer driver uses the information in a ruleset to set up the execution environments for the timers that respond to time events. run-time error. An error detected by NCL during the execution of an NCL process that can be trapped using an error handler. running trace.
Glossary server process. A process that implements requests for an application and returns replies to the requester process. server program. A program in a Pathway system written using a language such as COBOL85, TAL, MUMPS, FORTRAN, BASIC, C, or Pascal. session definition record. A record, created by the SESSION DEFINE command, that names and establishes the characteristics of an INMC session type. share list. The list of elements after a SHARE, NOSHARE, SHRVARS, or NOSHRVARS keyword. shared loading.
Glossary special character. In NCL, a lexical element that is a single character and acts as a delimiter in a statement. Its meaning depends on the current context. SPI. See Subsystem Programmatic Interface. SPLIT grid. The grid composed of one vertical and one horizontal line that appears after the SPLIT key is pressed on a Tandem 6530 or compatible terminal. splitting. The opening of a new window or adjusting of the current window.
Glossary strict test of equality. A test of equality by a strict relational operator. stripping. The removing of characters (including blanks) from text. In a panel, usually to either left justify, right justify, or center the text on a screen. In an expression, usually to perform a test of equality on the text. structured file. An Enscribe file type consisting of records, each of which consists of defined fields and keys. Entry-sequenced UDBs and key-sequenced UDBs are structured files. subject.
Glossary System Services Control Point (SSCP). The subsystem responsible for managing and allocating all resources in a domain in an IBM Systems Network Architecture (SNA) network and for communicating with network operators. There is one SSCP for each domain in an SNA network. System Support Services. A group of NonStop NET/MASTER MS services that includes the Activity Log Browse facility, the Command Entry facility, and the Display/Update SYSPARMS Settings facility. system panel library.
Glossary term. The basic unit of an expression in NCL. There are five types of terms: symbols, quoted strings, variables, parenthesized expressions, and function references. terminal control process (TCP). The Guardian process that interprets SCREEN COBOL object code, handles input-output to operator terminals, and sends messages to server processes. terminal definition record. The record created when defining a terminal to NonStop NET/MASTER MS. test mode.
Glossary trace parameter. A value in the trace parameter list specifying the events to trace. trace parameter list (TPL). A list associated with an OCS window that holds the current trace parameter settings. trace point. A NonStop NET/MASTER MS code position that can be traced. trace record. An entry in a trace file: a message mapped by the map $MSG, text data, or binary data. Transaction Application Language (TAL).
Glossary unmapped UDB. A user database in which NCL treats the data in each record as a sequence of contiguous bytes. NCL does not interpret the data in an unmapped user database: an unmapped user database can contain any binary data. unprotected field. A panel field that can accept input. unquoted string. Within an NCL statement, a sequence of characters that do not begin and end with quotes, do not result in a number, and do not have a predefined meaning when used in a particular context.
Glossary user NCL procedure. An NCL procedure created by a user. user panel library. A panel library containing the panel description files belonging to a particular user or group of users. user procedure library. A procedure library containing the NCL procedures belonging to a particular user or group of users. user variable. A variable created by an NCL procedure. Parameters are user variables. user-defined error handler. An error handler defined by a user. user-defined map.
Glossary verb. Sometimes called a “verb statement,” an NCL statement that is not an intrinsic part of NCL. Its availability depends on the enabling of a NonStop NET/MASTER MS feature. Verbs do not affect the structure and flow of NCL process execution. virtual user. A NonStop NET/MASTER MS user that does not have a terminal associated with it. A virtual user acts the same way as a real user and has the same attributes as a real user operating in OCS. wake-up timer.
Index A A action code 4-8 AC action code 4-8 Action codes 4-8 ACTION field 6-31 Action Message Group field 5-11, 5-12 Activate Timer field 5-11, 5-12, 5-39, 5-58 Activation field 5-19, 5-63, 6-39 Alarm field 5-34, 5-53 Assigned Value field 5-40 At field 5-65 Authority requirements BASERULE ruleset 3-15, 12-1 RMS product 3-14 ZRMSININ initialization NCL procedure 3-5 automatic retry of rule action NCL procedures 5-59 setting &$RETRY variable 5-59 setting &$RETRYDELAY variable 5-59 B Base Profile fields 5-15
Index BASERULE ruleset (continued) customizing the ZCPUUP rule 3-20, 12-4 customizing the ZTACLFAIL rule 3-20, 12-14 prerequisites 12-1 C C action code 4-8 CMD command 4-6 Cmd Groups Executed field 10-8 CMI utility commands 3-15, 12-2 Color field 5-34, 5-53 Command group 2-15, 6-10 adding 6-10 adding with model 6-13 Command Group ID field 6-12 copying from more than one ruleset 6-15 copying from one ruleset 6-15 copying into ruleset 6-14 deleting 6-17 maintaining comments 6-33 modifying 6-16 printing 6-54
Index Control options definition - ranking Merge—MSG MOD field 5-9 ranking elements 5-8 Rule Overlap Control field 5-8 Select field 5-9 Control options definition - run parms Action Message Group field 5-11 Activate Timer field 5-11 Default Propagation field 5-11 Exec Command Group field 5-11 Message Modification field 5-11 Message Replacement field 5-11 Message Suppression field 5-11 narration 5-10 NonStop NET/MASTER Command field 5-11 Process Solicited Msgs field 5-12 Set Defined Variables field 5-11 Sta
Index D D action code 4-8 Database 1-3 Default delivery exit NCL procedure 5-5 Default Delivery NCL Exit field 5-6 Default Propagation field 5-11, 5-12 Default ruleset 7-1, 9-6 allocating 7-2 allocating with model 7-3 changing allocation 7-3 commenting on 7-3 Default Ruleset field 7-2 deleting allocation 7-3 printing allocation details 7-3 Region Owner field 7-2 use of 3-7 Default Ruleset field 7-2 Deliver field 5-31 Delivery Philosophy field 5-5 Do Actions field 5-32 Domain ID field 5-23 DSNM 12-1 DSNM co
Index Every field 5-66 EX operator 5-29 Exec Cmd Group field 5-38, 5-57, 5-68 Exec Command Group field 5-11, 5-12 Exec Region field 9-4 External messages 1-8 F Filename field 6-38 FIND command 4-6 FIRST field 10-8 Function key settings record 6-28 ACTION field 6-31 deleting 6-32 function type 6-31 IMM/CONV/PREF/SUFF field 6-31 initial settings 6-28 maintaining comments 6-33 printing 6-54 specifying 6-30 G GE operator 5-29 GT operator 5-29 Guardian utility commands 3-15, 12-2 H HELP command 4-6 Help Panel f
Index L LAST field 10-8 LE operator 5-29 Limit field 5-66 LK operator 5-29 Load Ruleset field 5-41, 5-58 LOCATE command 4-6 LOCATION field 6-55 LOG command 4-6 LOGPROC message handler 1-8, 2-1 continuity of operation 2-1 LT operator 5-29 M Manager field 9-13, 9-20, 9-22, 9-23 Max Capture field 8-7, 10-5 Maxcnt field 5-31 MDO Element Name field 5-22 MDO Element Value field 5-22 Merge/Replace field 6-39 Merge—MSG MOD field 5-9 Message Action ID field 5-20 Message action rule 2-10, 5-15 Activate Timer field 5
Index Message action rule (continued) Exec Cmd Group field 5-38 Help Panel field 5-33 Hlight field 5-34 Intens field 5-34 Interval field 5-31 Load Ruleset field 5-41 maintaining comments 6-33 Maxcnt field 5-31 MDO Element Name field 5-22 MDO Element Value field 5-22 Message Action ID field 5-20 Message Group ID field 5-44 Message ID field 5-22 message presentation 2-11, 5-31 message recognition elements 5-21 message subject 5-26 message text analysis 5-27 message threshold processing 2-11, 5-31 modifying 6
Index Message action rule (continued) specifying rule actions 5-36 SS ID field 5-22 Start Pos field 5-28 Status field 5-19 Subject Override field 5-27 Submit Actions field 5-39, 5-57 Suffix field 5-40 Time 1 field 5-25 Time 2 field 5-25 Time 3 field 5-25 Time 4 field 5-25 transferring between databases 6-36 trigger criteria 2-10, 5-21 UDP field 5-26 User Exit field 5-26 Word Num field 5-28 %INCLUDE rule 2-13 %START rule 2-13 Message flow, parameters affecting 10-1 Message Group ID field 5-44 Message group
Index Message group rule (continued) Msgs Group ID field 5-50 NCL Exit Name field 5-58 NCL Proc Name field 5-57 NRD field 5-53 printing 6-54 Replacement Method field 5-54 Replacement Text field 5-54 retry rule action 5-59 rule actions 2-14 Rule ID field 5-51 Scan field 5-53 specifying message attributes 5-53 specifying message text 5-53 specifying rule actions 5-55 specifying rule members 5-51 transferring between databases 6-36 Message Groups Actioned field 10-8 Message handler 1-2, 2-1 activating message
Index Message handler (continued) starting using the RMS command interface 9-6 statistics 10-1 using more than one ruleset 9-1 Message handler type 2-1 Message ID field 5-22 Message Modification field 5-11, 5-12 Message Modified field 10-7 Message Propagated by Default field 10-8 Message recognition elements 5-21 Message Replacement field 5-11, 5-12 Message set 1-5 adding a message 8-14 adding with model 8-16 commenting on 8-16 copying messages from a set 8-15 copying messages into a set 8-15 deleting 8-16
Index N Narration 1-5, 2-8, 5-10 NCL Exit Name field 5-42, 5-58 NCL Proc Name field 5-38, 5-57, 5-68 NCL Procs Executed field 10-8 NCL queues 3-16 Negative message delivery philosophy 5-5 NNM Cmds Issued field 10-8 NonStop NET/MASTER Command field 5-11, 5-12 NonStop NET/MASTER MS system-level NCL procedure, migrating to message handler 3-7 NRD field 5-34, 5-53 O On Date field 5-65 On Days fields 5-24 Online help 4-10 Opr field 5-28 OPSYS command 3-15, 12-2 P P action code 4-8 COPIES field 6-55 LOCATION fie
Index Process Solicited Msgs field 5-12 PUP utility commands 3-15, 12-2 Purge After field 5-44 R REFRESH command 4-6 Region Owner field 7-2 RELATIONSHIP BETWEEN ANALYSIS CRITERIA field 5-30 Replacement Method field 5-35, 5-54 Replacement Text field 5-35, 5-54 retry rule action NCL procedures 5-59 &$RETRY variable 5-59 &$RETRYDELAY variable 5-59 RMS commands RMS DELETE ACTIVE 9-15, B-2 RMS DELETE DELAYED 9-26, B-3 RMS DELETE QUEUED 9-18, B-4 RMS DISPLAY ACTIVE 9-15, B-5 RMS DISPLAY DELAYED 9-25, 9-26, B-6 R
Index RMS panels (continued) menu panel 4-1 moving between input fields 4-5 navigating through data entry panels 4-7 options 4-3 panel skipping 4-3 selecting an option 4-3 selection list panel 4-1 RMS product 1-1 authority requirements 3-14 controlling user access 3-9 customizing the security exit NCL procedure 3-12 disk space requirement 3-1 installation subvolumes 3-1 installing 3-1 managing the UDB file 3-8 planning 3-1 UDB file 3-8 RMS THAW command 9-20, B-12 RMS timer 2-6 activating at initialization
Index Rule Overlap Control field 5-8 Ruleset 2-8, 5-1 copying 6-18 creating 5-3 deleting 6-34 merging 6-22 printing 6-40 printing detailed report 6-42 printing summarized report 6-55, 6-58 printing using selection list panel 6-54 testing 8-1 transferring between databases 6-36 Ruleset field 5-3, 6-6 Ruleset global variable 5-40 Ruleset Name field 6-38 Ruleset record categories 2-8 control options 2-8 environmental profile 2-9 function key settings 2-9 Ruleset user variable 5-40 Run parameters 5-10 S S acti
Index Statistics Cmd Groups Executed field 10-8 COUNT field 10-8 FIRST field 10-8 LAST field 10-8 Max Capture field 10-5 Message Groups Actioned field 10-8 Message Modified field 10-7 Message Propagated by Default field 10-8 MESSAGE STATISTICS 10-8 Message Suppressed field 10-7 MESSAGE TEXT field 10-8 Messages Replaced field 10-7 MSGID field 10-8 NCL Procs Executed field 10-8 NNM Cmds Issued field 10-8 RMS STATISTICS 10-7 RULE HIT STATISTICS 10-8 RULE ID field 10-8 Sort Message Statistics By field 10-6 Sor
Index Subject Override field 5-27 Submit Actions field 5-39, 5-57 Suffix field 5-40 Super group 3-15, 12-2 System Cmds Issued field 10-8 System Command field 5-11, 5-12 T TACL program 3-15, 12-2 TACL utility commands 3-15, 12-2 Testing 8-1 Max Capture field 8-7 MESSAGE SET field 8-8 modifying triggered rules during testing 8-5 printing messages captured in OCS environment 8-8 saving messages captured in OCS environment 8-8 using a simulated message 8-3 using messages in OCS environment 8-6 using saved mess
Index Time-based rule (continued) NCL Proc Name field 5-68 On Date field 5-65 On Days fields 5-65 printing 6-54 rule actions 2-14 specifying rule actions 5-67 Status field 5-64 time criteria 5-65 Timer ID field 5-64 transferring between databases 6-36 User ID field 5-66 Timer driver 1-2 Timer ID field 5-64 Timers Activated field 10-8 TOTAL MESSAGES PROCESSED field 10-8 Total Msgs Processed field 5-14 trigger criteria 5-21 Trigger life 2-12, 5-42 U UDB File ID field 6-38 UDP field 5-26 User Exit field 5-26
Index Z ZCPUDOWN rule 12-3 and $SYSTEM volume 3-17, 12-4 customizing 3-20, 12-4 ZCPUUP rule 12-4 customizing 3-20, 12-4 ZDEVICEDOWN rule 12-5 ZEXPANDNOTRY rule 12-7 ZPATHTCPFAIL rule 12-8 ZPATHTRMABRT rule 12-9 ZPATHTRMSUS1 rule 12-10 ZPATHTRMSUS2 rule 12-11 ZRMSAPIN ( DELACTIVE ) procedure call 9-15, C-2 ZRMSAPIN ( DELDELAYED ) procedure call 9-26, C-3 ZRMSAPIN ( DELQUEUED ) procedure call 9-18, C-4 ZRMSAPIN ( FREEZE ) procedure call 9-22, C-14 ZRMSAPIN ( GETACTIVE ) procedure call 9-15, C-5 ZRMSAPIN ( GE
Index Special characters $SYSTEM volume 3-17, 12-4 % field 10-8 %INCLUDE rule 2-13, 5-44 adding 5-45 nesting 5-44 %START rule 2-13, 5-45 adding 5-45 naming multiple rules 5-45 &$RETRY variable 5-59 &$RETRYDELAY variable 5-59 &$RMS-type variable 11-2 &$UV-type variable 11-1 &GLBL-type variable 11-1 &OPTION variable 3-9, 3-12 &SETNAME variable 3-9 &USERID variable 3-9 &WORD-type variable 11-4 &ZZZ-type variable 11-4 * wild-card character 4-7 ? command 4-6 ? wild-card character 4-7 115415 Tandem Computers In
