ViewPoint Manual Abstract This manual describes ViewPoint, a multifunction operations console application that allows management of a network of systems. The manual contains information on installing, configuring, and starting ViewPoint for custom applications. It also describes the concepts underlying ViewPoint operation. This manual is intended for use by operators, system or application managers, and programmers. Product Version ViewPoint D30 Supported Releases This manual supports D30.00 and G05.
Document History Part Number Product Version Published 426801-001 ViewPoint D30 July 2000 424874-001 ViewPoint D30 December 1999 133484 ViewPoint D20 April 1997 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice.
ViewPoint Manual Glossary Index Examples Figures What’s New in This Manual xiii Manual Information xiii New and Changed Information xiii About This Manual xv Introduction xv Related Documentation Summary of Contents xv xvi How to Use This Manual xvii Your Comments Invited xvii Notation Conventions xvii 1.
2. Using ViewPoint (continued) Contents 2.
3. Definition of ViewPoint Screens (continued) Contents 3.
4. Process Definition Commands (continued) Contents 4. Process Definition Commands (continued) WAITREADY Command 4-18 Issuing Commands to a Defined Process 4-18 5.
6. Customizing ViewPoint (continued) Contents 6.
7. Installation, Configuration, and Startup (continued) Contents 7.
E. Supplemental Information for D-Series Systems Contents E.
Figures (continued) Contents Figures (continued) Figure 3-4. Event Configuration Screen, Page 1 Format 3-15 Figure 3-5. Event Configuration Screen, Page 2 Format 3-19 Figure 3-6. Event Detail Screen Format Figure 3-7. Last Events Screen Format Figure 3-8. Network Status Summary Screen Format 3-28 Figure 3-9. Profile Screen Format 3-31 Figure 3-10. Status Configuration Screen Format Figure 3-11. Status Item Configuration Screen Format Figure 3-12. TACL Screen Format 3-38 Figure 4-1.
Figures (continued) Contents Figures (continued) Figure 5-21. Distribution of Primary and Alternate Events 5-30 Figure 5-22. Event Presentation Processes for Two Operators Figure 5-23. Other Event Presentation Features Figure 5-24. Event Presentation Architecture 5-34 Figure 6-1. Default Primary-Events Filter Source Code Figure 6-2. Default Alternate-Events Filter Source Code (page 1 of 4) Figure 6-3. DDL for Event-Detail Database Figure 6-4. Linkage Section of ZVPT-EXTRAS Figure 6-5.
Tables (continued) Contents Tables (continued) Table 7-1. Three Directories for ViewPoint TACL Routines Table 7-2. Files and Their Security Attributes Table A-1. Server Assigns (page 1 of 4) Table A-2.
What’s New in This Manual Manual Information ViewPoint Manual Abstract This manual describes ViewPoint, a multifunction operations console application that allows management of a network of systems. The manual contains information on installing, configuring, and starting ViewPoint for custom applications. It also describes the concepts underlying ViewPoint operation. This manual is intended for use by operators, system or application managers, and programmers.
New and Changed Information What’s New in This Manual ViewPoint Manual—426801-001 xii
About This Manual Introduction ViewPoint is a multiple-function application that allows you to manage a network of Compaq systems from a single terminal such as from an operator console. It provides an integrated view of the status of a group of distributed systems and the events that occur on the systems. ViewPoint is easily distributed, has fault-tolerant operation, supports multiple terminals, and can be customized by the user.
Summary of Contents About This Manual Summary of Contents The manual describes how to use the ViewPoint application in the following sections and appendixes: Sections • • • • • • • Section 1, Introduction to ViewPoint gives a concise overview of ViewPoint capabilities. Section 2, Using ViewPoint lists step-by-step procedures to help the person who monitors and controls the system to get started with using ViewPoint.
How to Use This Manual About This Manual How to Use This Manual You are probably responsible for specific tasks within your company or site. The following table is a guideline to which sections and appendixes are most useful for your responsibilities.
General Syntax Notation About This Manual lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required. For example: file-name [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none.
Notation for Messages About This Manual Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must enter as shown. For example: "[" repetition-constant-list "]" Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted.
Notation for Management Programming Interfaces About This Manual Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual lowercase letters. Words in lowercase letters are words that are part of the notation, including Data Definition Language (DDL) keywords. For example: token-type !r. The !r notation following a token or field name indicates that the token or field is required. For example: ZCOM-TKN-OBJNAME !o. token-type ZSPI-TYP-STRING. !r The !o notation following a token or field name indicates that the token or field is optional.
Change Bar Notation About This Manual ViewPoint Manual—426801-001 xx
1 Introduction to ViewPoint Introduction ViewPoint is a software product that runs on a console and is used to observe and control conditions in a Compaq system or network of systems. ViewPoint is a Compaq application of the Pathway transaction processing system. It is one of the set of products referred to as Distributed Systems Management (DSM).
ViewPoint Functions Introduction to ViewPoint • • High-PIN requesters can open ViewPoint processes. C-series systems can support remote EMS distributors. Also, ViewPoint can be customized to suit individual needs. Application managers can control what information is displayed on the status and event screens. Programmers can use ViewPoint as a foundation for new management applications.
Monitoring Network Status Introduction to ViewPoint Network Status Summary Screen The ViewPoint operator uses the Network Status Summary screen to observe the status of items (up to 16 at a time) in a network. A status item is usually an object such as a CPU, disk, or terminal; or it might be an average, such as the average CPU usage. Each item appears on a separate line and consists of a brief description followed by a bar graph that reports on the item’s availability or current usage.
Monitoring Events Introduction to ViewPoint However, the ViewPoint operator or application manager can use the Profile screen to specify another existing status configuration file as the current configuration file. Two configuration screens, the Status Configuration screen and the Status Item Configuration screen, allow the operator or application manager to control what is contained in a status configuration file.
Monitoring Events Introduction to ViewPoint Last Events Screen Any ViewPoint operator can display on the Last Events screen recent messages that describe events for whose subject is a particular object. The display is similar to that on the other events screens but is limited to one subject; for instance, messages about a particular device or messages originating in a particular process.
Monitoring Events Introduction to ViewPoint Figure 1-3. Overview of Monitoring Events CDT003.cdd As with the Network Status Summary screen, the operator can save all or selected event messages in a clipboard file for subsequent printing or editing or for input to a program. Configuring the Events Screens ViewPoint determines how to build an event display by looking at the current event configuration file. A default event configuration file is supplied with the application.
Control and Inquiry Introduction to ViewPoint In addition to the event configuration file, event displays are controlled by filters, with each filter kept in a filter object file. A filter can be associated with any EMS distributor to control the event messages retrieved by ViewPoint event collection servers. Default filters are supplied with ViewPoint.
Customizing ViewPoint Introduction to ViewPoint TACL Screen If available, the TACL screen provides all the existing capabilities of TACL (see the TACL Programmer’s Guide) plus access to the Define Process library of commands. The TACL screen is part of ViewPoint, so you can use function keys on this screen to switch readily to other parts of the ViewPoint application.
Customizing ViewPoint Introduction to ViewPoint • • • • • • • • • Add custom event-message text to display messages on the Event Detail screen that reflect your own operation policies and procedures. You do this by adding text to the event-detail database with the ENABLE application generator. Write custom filters that determine what events are displayed on ViewPoint events screens—for instance, you could specify as critical events those events that ViewPoint does not normally consider critical.
Customizing ViewPoint Introduction to ViewPoint ViewPoint Manual—426801-001 1- 10
2 Using ViewPoint Introduction This section is designed to help you get started quickly using ViewPoint.
Starting ViewPoint Using ViewPoint Starting ViewPoint To start ViewPoint on a monochrome monitor, give the following command at the TACL prompt: VIEWPT [pathmon-name] pathmon-name is the name of the PATHMON process with which ViewPoint is to establish communication. The default is $ZVPT. An example of starting ViewPoint is: VIEWPT $mar You will see the ViewPoint banner while ViewPoint initializes your access. When initialization is complete, you see the TACL screen and ViewPoint function keys.
Monitoring Status Using ViewPoint If you want to shut down the ViewPoint processes, first exit ViewPoint by pressing the SF16 function key, then at the TACL prompt, type: VIEWPT :shutdown [pathmon-name] pathmon-name is the name of the PATHMON process with which ViewPoint is to establish communication. The default is $ZVPT. VIEWPT :stopit [pathmon-name] pathmon-name is the name of the PATHMON process with which ViewPoint is to establish communication. The default is $ZVPT.
Freezing and Thawing the Screen Using ViewPoint The advice line says “Sampling” as ViewPoint collects data on the current usage of network resources. This data is then displayed and is continually updated with the most current information. If any status line is highlighted, it means that the item is above maximum or below minimum threshold values. For information on modifying the threshold of an item, see the subsection “Changing the Item Threshold” later in this section.
Changing the Status Interval Using ViewPoint 4. Press F10 to copy the selected lines to your clipboard file (ZZVPCLIP) in your default logon subvolume. If the clipboard file did not exist previously, it is created now. “Clipping” is displayed in the advice line. When the copying is done, “Lines clipped” is displayed. 5. Specify a printer. Move the cursor to the option line and type: $S.#printer where printer is the name of a printer on your system. 6.
Changing the Item Threshold Using ViewPoint 6. Move the cursor to the option line and press F12 to return to the Status Configuration screen. 7. Restore the original update interval noted in Step 3. (The interval value affects only this terminal.) 8. Press F12 to confirm the change and return to the Network Status Summary screen. Changing the Item Threshold You can cause a status item to be highlighted on the screen whenever its computed usage value falls above or below specified threshold values.
Monitoring Events Using ViewPoint 3. Move the cursor to an item you want to move. Select one that is easy to identify after it appears in a new position. 4. Press F6 to delete the item from the display; it is saved in memory to allow you to move it to another location. 5. Move the cursor to the new desired location and press F7 to display the item at the new location. Any item currently in that location is bumped down when you add the deleted item.
Changing the Delay Between Updates Using ViewPoint displayed on line 25 of your terminal, and the terminal’s bell tone sounds each time a new message is displayed in this line. Line 3 tells you the name of the event collector process currently being used, the name of the current filter, and the number of action and critical events on this display. Notice that the display for each event gives the time of the event, the system node name, and the event-message text (the first 62 characters). 3.
Restricting the Events Displayed Using ViewPoint 5. Press F12 to confirm the change and return to the Primary Events screen. Notice the difference in the timing of updates. If you changed the value to 0, the updates are more random, occurring as soon as each new event message arrives. If you changed the value to 15, the updates are at least 15 seconds apart. 6. Restore the original delay.
Observing Alternate Events Using ViewPoint To display message text associated with an event, follow these steps: 1. Press F1 to display the TACL screen, if it is not already selected. 2. Press F3 to display the Primary Events screen. 3. Press F8 to freeze the screen. Then, select 3 or 4 event messages that appear truncated (where the text is more than the 62-character limit). Do this by typing any character next to the message. 4. Press F11 to display the Event Detail screen.
Observing Historical Events Using ViewPoint Observing Historical Events You can see messages for events that occurred at an earlier date or time with the Alternate Event Configuration screen. For example, suppose you want to see messages for events that occurred since 1:00 p.m., yesterday. To see the messages for these earlier events, follow these steps: 1. Press F1 to display the TACL screen, if it is not already selected. 2. Press SF3 to request the Alternate Events screen.
Observing Events by Subject Using ViewPoint • To select the END page, press SHIFT-NEXT PAGE or by selecting a page number of 20 (or greater). Notice that only the END page gets updated as new event messages arrive. Note. The event cache, which contains the alternate event messages, retains its contents if you go to some other screen (such as Primary Events) and is accessible when you return. The cache is cleared only when you exit from ViewPoint or if you alter the configuration for alternate events.
Managing Configuration Using ViewPoint 6. Press F3 to display the Primary Events screen. 7. Move the cursor to the option line and enter the subject you noted down from the Last Events screen in Step 5. 8. Press F4 to display the Last Events screen by subject name. The display should be the same as before, except for any new events issued since then. 9. Press F1 to display the TACL screen.
Creating Configuration Files Using ViewPoint Creating Configuration Files You can create any number of configuration files, each with an alternate configuration. Having a set of configuration files allows you to switch easily from one configuration to another. In the following steps, you create a new configuration file for the Network Status Summary screen and a new configuration file for the Alternate Events screen. Caution.
Creating Configuration Files Using ViewPoint enter $SYSTEM in the Object Name field. (You should also type $SYSTEM after Disk Busy in the Item Description field so that the name of the disk appears on the screen.) e. Make any other changes to the template that you want. f. Press F12 to confirm the configuration change. You can continue to add new items; for instance, add all the disks on your system. ViewPoint continues to display the Status Item Configuration screen until you request a different screen.
Choosing an Alternate Configuration Using ViewPoint 12. Press F1 to return to the TACL screen. Note. You might also use the Alternate Events Configuration screen to specify remote collectors or log files on other systems from which events are to be collected (instead of using remote distributors); to specify a particular filter to control the events passed to the Alternate Events screen; or to pass information to a selected filter to further customize the filtered events.
Accessing DSM/PM from ViewPoint Using ViewPoint Accessing DSM/PM from ViewPoint There are different ways of accessing DSM/PM from ViewPoint. The method you choose depends on the task you are trying to perform. Each method, however, involves one of two function keys: F5 or SF5. The different methods are summarized as follows: • • • • To move to a specific DSM/PM screen, type the name of the screen you want to access (or a valid alias for it) on the ViewPoint option line and then press F5 or SF5.
Adding ViewPoint Events to DSM/PM Using ViewPoint The object name associated with the event you marked is displayed as the problem subject on the screen. DSM/PM does not automatically submit the problem, but is waiting for you to take further action. 6. When you are ready, follow the DSM/PM instructions for creating and submitting the record. 7. Press F16 to return to the ViewPoint Primary Event screen. At this point you are still logged on to DSM/PM. 8.
Using Define Process Using ViewPoint Using Define Process From ViewPoint you can enter any Define Process command. The Define Process commands allow you to start up to 100 background processes (such as PUP, FUP, and SPOOLCOM) without having to exit ViewPoint. You do not have to be within ViewPoint to enter the Define Process commands, but you must have access to the TACL process. For reference information on the Define Process commands, refer to Section 4, Process Definition Commands.
Using Define Process Commands Using ViewPoint Note that the name for the PERUSE defined process is the same as its program name. However, the defined process, FUP, is different; its name is FP. The input queues (for queuing input commands) are shown to be empty, as are the output queues (for receiving output information from the processes). Both processes are ready to accept commands. d. Type the command PERUSE.
Using Remote Processes Using ViewPoint Using Remote Processes The following instructions describe how you use remote processes. If you follow all the following steps in sequence, your ViewPoint files remain in your logon subvolume for future use and all temporary files and processes are eliminated. Note. These steps can be performed only if you have access to some other node of a Compaq network, so you must have remote passwords established on both systems—your local one and the remote one.
Using Remote Processes Using ViewPoint c. Type FUP. You are now in your local FUP process. d. Press BREAK to return to TACL. e. Type > A. You are now in your remote TACL process. f. Press BREAK to return to your local TACL. g. Type >MYREMOTEPATHMON1 You are now in your remote PATHMON. h. Press BREAK to return to your local TACL. 9. Type > UNDP * to remove the definitions of the defined processes. Press SF16 to exit.
3 Definition of ViewPoint Screens Introduction This section describes the screens provided by the ViewPoint application. It also defines the operation of the function keys for moving around the screens and for specific functions on each of the screens. The screens are described in alphabetic order.
Function Keys Definition of ViewPoint Screens All other screens use block mode, which is indicated by the word BLOCK in the same position on the twenty-fifth line. In conversational mode, characters are transmitted to the controlling process as they are typed. In block mode, information is transmitted as complete messages or blocks of data—typically when you press an appropriate function key. Function Keys Table 3-1 provides a summary of the ViewPoint function keys. Table 3-1.
Function Keys Definition of ViewPoint Screens Table 3-1. Summary of Function-Key Assignments (page 2 of 3) Key Function Description F6 Ack/ Delete Displays the Events screens, and acknowledges any action or critical events that are on by dimming them. Used on the Network Status Summary screen, deletes selected status items. Used on the Event Configuration screen, deletes that configuration.
Function Keys Definition of ViewPoint Screens Table 3-1. Summary of Function-Key Assignments (page 3 of 3) Key Function Description SF14 Recover Screen Used on the Event Configuration, Event Detail, Last Events, Network Status Summary, and Status Item Configuration Events screens, recovers the screen to its last known state. F15 Help Displays the Help screen and the first page of help information for the current screen.
Block-Mode Screen Format Definition of ViewPoint Screens Block-Mode Screen Format Figure 3-1 shows the general format for block-mode screens. Figure 3-1. Block-Mode Screen Format CDT031.cdd Line 1 of a block-mode screen is the screen header. It displays which screen you are using and the time the screen was last updated. Also, for multipage screens, line 1 displays your current page position. Line 2 is blank.
Screen Navigation Definition of ViewPoint Screens Line 24 is the option line, which is available for supplying information that is meant to be used with the function keys, such as to pass the name of a subject when using the Last Events function key. You can also specify a page number on line 24 to display a particular page of the Primary or Alternate Events screens or the Network Status Summary screen.
Screen Navigation Definition of ViewPoint Screens Extras. For example, use F3 to go to the Primary Events screen or F14 to go to the Profile screen. Figure 3-2. Screen Navigation Map CDT032.cdd You can also switch to the DSM/PM screens if DSM/PM is configured to run with ViewPoint. For an example of how to access DSM/PM from ViewPoint, see Section 2, Using ViewPoint.
Events Screen Definition of ViewPoint Screens The remainder of this section describes nine of the 12 ViewPoint screens. They are described in alphabetical order.
Field Descriptions Definition of ViewPoint Screens 2. Page. Page number of event messages you are currently viewing. The number of the END page (the only one that is updated as new event messages come in) continues to increment until it reaches the configured size of the cache; then, it remains at that number. A field following the page field tells you that you are on the END page. Earlier pages are numbered downward from the END page. Search through the various pages of earlier events.
Field Descriptions Definition of ViewPoint Screens Select any single event message by positioning the cursor in this field, or enter any nonblank character in this field to select any number of events, and press the appropriate function key for the operation you want. To avoid possible inaccurate marking due to sudden scrolling as new messages arrive, you should first freeze the screen using F8. 9. Generation Time. Time of day when the event displayed on that line was generated. 10. System.
Field Descriptions Definition of ViewPoint Screens ∗Τhis function key is active only if you have configured ViewPoint to run with DSM/PM; even when it is active, however, you will not see it in the list of functions keys appearing at the bottom of your screen. For more information on using this function key, see its listing under “Function Key Notes” in this section.
Field Descriptions Definition of ViewPoint Screens Table 3-2. Function Key Notes (Events Screen) (page 1 of 2) Function Key F4 Special Requirements Before displaying the Last Events screen, you must select a subject. Select a subject by positioning the cursor (or entering a nonblank character) in the selection field preceding a message that identifies the subject you want to know about. Then, press F4 to request the Last Events screen.
Field Descriptions Definition of ViewPoint Screens Table 3-2. Function Key Notes (Events Screen) (page 2 of 2) Function Key Special Requirements F5 Used in the following two ways: • Displays a particular DSM/PM screen. Type the name of the screen (or any valid alias) on the option line, and press F5. • Submits events as problems. Mark the events by typing any character next to them, and press F5.
Event Configuration Screen Definition of ViewPoint Screens Table 3-3. Summary of Event Acknowledgment for Critical and Action Events Event Dimmed Locally Dimmed Everywhere CRITICAL EVENTS Acknowledged on Primary Events Screen Acknowledged on Alternate Events Screen X X ACTION EVENTS Acknowledged Automatically X Acknowledged Manually On Primary Events Screen On Alternate Events Screen X X Action events are also dimmed when the requested action has been taken; that is, when the action is completed.
Page 1 of the Event Configuration Screen Definition of ViewPoint Screens Page 1 of the Event Configuration Screen Figure 3-4 shows the format for the first page (Page 1) of the Event Configuration screen. Figure 3-5 (later in this subsection) shows the format for the second page. Figure 3-4. Event Configuration Screen, Page 1 Format CDT034.cdd Field Descriptions 1. Page 1. Page identifier that tells you whether this is the END page or whether MORE pages are available.
Field Descriptions Definition of ViewPoint Screens 3. Event Display. This field, which is not modifiable, tells you whether this configuration applies to the primary display (PRIMARY) or to the alternate display (ALTERNATE). 4. Collector or Log File. Name of the collector or log file used. This field is modifiable for configuring only an Alternate Events screen. (For the Primary Events screen, the collector name or names are preconfigured; you cannot change them dynamically.
Field Descriptions Definition of ViewPoint Screens You must return to this screen each time you want to change your event view. Your most recent selection remains in the configuration file until the next time you change it. 7. After. These fields are modifiable only for alternate-event configurations, since the primary-event display is for current events only.
Page 2 of the Event Configuration Screen Definition of ViewPoint Screens default cache size is 20 pages. (The pages shown in this section refer to 16-line event-screen pages; thus the default cache size holds 320 event messages.) 3. Function keys F6 Delete configuration F12 Update configuration SF14 Recover F15 Help F16 Return without updating Function Key Notes The following notes describe the operation of some of the function keys and special requirements for using them. Table 3-4.
Field Descriptions Definition of ViewPoint Screens Figure 3-5.
Field Descriptions Definition of ViewPoint Screens 5. CPU or Process ID. This field can contain a process ID or a CPU number. The ID or CPU number of the process that reports an event must match the specified ID or CPU number to qualify that event to be selected or discarded by the filter. You specify a process ID as a process name (1 to 5 alphanumeric characters preceded by $) or as two integers (cpu-the CPU number, and pin-the process ID number).
Field Descriptions Definition of ViewPoint Screens screen for these parameters to be effective. (Refer to Section 6, Customizing ViewPoint for a discussion of how to add logic to FLTRALT or how to write a custom filter.) You specify custom parameters as a value followed by a type. For each parameter value, you must indicate its type. The type you mark determines how the value is interpreted. Table 3-5 describes the value for each type. Table 3-5.
Event Detail Screen Definition of ViewPoint Screens Event Detail Screen Figure 3-6 shows the format for the Event Detail screen. Figure 3-6. Event Detail Screen Format CDT036.cdd Field Descriptions 1. Page. Page you are currently viewing. This is followed by the word MORE if there are more pages or by the word END if you are viewing the final page. You can scroll forward with the NEXT PAGE (or PG DN) key and backward with the PREV PAGE (or PG UP) key.
Last Events Screen Definition of ViewPoint Screens 6. Effect. This field displays any possible effect on the system that this event might have caused. 7. Recovery. This field displays the recommended action (if any) for you to take for this event. 8. Function keys : F9 Print screen F10 Clip F11 Next SF14 Recover F15 Help F16 Return Note. If you have selected several events on the previous screen for detail viewing, press F11 to step from one to the next.
Field Descriptions Definition of ViewPoint Screens Figure 3-7. Last Events Screen Format CDT037.cdd Field Descriptions 1. Page. Page number of the last-events display you are currently viewing. A field following the page field tells you that you are on the END page. If there are more pages to be viewed, the initially viewed screen (with the most recent events) has the highest page number, and earlier pages are numbered downward. Earlier pages are numbered downward.
Field Descriptions Definition of ViewPoint Screens 2. Subject. Name of the subject associated with these event messages. This is the name you selected on the screen either by entering it on the option line or by marking an event message with the cursor or a nonblank character. To change the subject, type a new subject name on the option line and press F4. The subject name you select refers to the subject token associated with that event. (For an explanation of subject tokens, refer to the EMS Manual.
Field Descriptions Definition of ViewPoint Screens • • Subjects appear in uppercase letters so that they can be searched regardless of their capitalization. For each suitable subject found, ViewPoint makes an entry in the last events database using the subject as a key. Each subject included in the database has a maximum of 80 characters; longer subjects are truncated to 80 characters. 3. Event Selection.
Field Descriptions Definition of ViewPoint Screens Function Key Notes Table 3-6 describes the operation of some of the function keys and special requirements for using them. Table 3-6. Function Key Notes (Last Events Screen) Function Key Special Requirements F4 Before displaying the Last Events screen, you must select a subject.
Network Status Summary Screen Definition of ViewPoint Screens Network Status Summary Screen Figure 3-8 shows the format for the Network Status Summary screen. Figure 3-8. Network Status Summary Screen Format CDT038.cdd Field Descriptions 1. Page. Page number you are currently viewing. This is followed by the word MORE if there are more pages or by the word END if you are viewing the final page. You can scroll forward with the NEXT PAGE (or PG DN) key and backward with the PREV PAGE (or PG UP) key.
Field Descriptions Definition of ViewPoint Screens 4. Item Selection. Selection of displayed status items for deleting, adding, copying, and configuring. To select more than one status item, type any nonblank character in this field in front of each status item you want to select. Or, to select only one item, position the cursor in this field in front of the status item you want, then use the appropriate function key to operate on the selected items.
Field Descriptions Definition of ViewPoint Screens F14 Profile SF14 Recover F15 Help SF15 Extra SF16 Exit Note. When you press a function key to go to another screen, then return to the Network Status Summary screen, your current screen appears exactly as it did when last displayed: the same page is displayed, the same status items are selected, and the screen is either frozen or thawed. Context is preserved.
Profile Screen Definition of ViewPoint Screens Table 3-7. Function Key Notes (Network Status Summary Screen) (page 2 of 2) Function Key Special Requirements F9 Prints the entire screen—data and all headings and legends. F10 Copies selected status items to the end of the clipboard file. Enter nonblank characters in column 1 preceding the items you want to copy, and press F10. You can print these selected status items by pressing F9.
Field Descriptions Definition of ViewPoint Screens Field Descriptions 1. Status Configuration File. Name of the status configuration file that you are currently using. Select a different file by typing its name in this field, and press F14 (Change profile). 2. Event Configuration File. Name of the event configuration file you are currently using. Select a different file by typing its name in this field, and press F14. 3.
Status Configuration Screen Definition of ViewPoint Screens Status Configuration Screen Figure 3-10 shows the format for the Status Configuration screen. Figure 3-10. Status Configuration Screen Format CDT310.cdd Field Descriptions 1. Status Configuration File. Name of the configuration file you are currently using. To change files, you need to use the Profile screen. 2. Screen Update Interval. Interval at which the status requests are automatically sent out to update the displayed status items.
Status Item Configuration Screen Definition of ViewPoint Screens Status Item Configuration Screen Figure 3-11 shows the format for the Status Item Configuration screen. Figure 3-11. Status Item Configuration Screen Format CDT311.cdd Field Descriptions 1. Status Configuration File. Name of the status configuration file that you are modifying. Use the Profile screen if you want to modify a different Configuration file. 2. Display Type.
Field Descriptions Definition of ViewPoint Screens Table 3-9. Only certain display types can be broken down this way into separate objects. Table 3-9. Object Names for Display Types Display Type Object Name CPU-busy 0-15 Average-CPU-Busy None Disk-busy Device name Line-busy Device name PATHWAY-term PATHMON process name SNAX-lines-up $SSCP SNAX-PUs-up $SSCP SNAX-LUs-up $SSCP TMF-transaction-rate None 5. Server Class.
Field Descriptions Definition of ViewPoint Screens 11. Enable Upper Threshold. This is a one-character field in which you can enter a Y (yes) or an N (no). Entering a “Y” means highlight this line on the Network Status Summary screen when the computed percentage value rises above the percentage value stated in the next field (upper threshold value). Entering an “N” means ignore any upper threshold setting. 12. Value.
Field Descriptions Definition of ViewPoint Screens Function Key Notes Table 3-10 describes the operation of some of the function keys and special requirements for using them. Table 3-10. Function Key Notes (Status Item Configuration Screen) Function Key Special Requirements F12 Causes the current status-configuration file to accept the values on the screen.
TACL Screen Definition of ViewPoint Screens TACL Screen Figure 3-12 shows the TACL screen. This screen is not available in all ViewPoint manuals. Figure 3-12. TACL Screen Format CDT312.cdd Field Descriptions 1.
Field Descriptions Definition of ViewPoint Screens ∗This function key is active only if you have configured ViewPoint to run with DSM/PM. When you press F5 or SF5, the DSM/Problem Manager Menu displays on your screen. Note. When the TACL interactive field becomes full, the function-key legend (lines 1 and 2) rolls off the top of the screen. To get the legend back, press F15 to display the Help screen, then press RETURN.
Field Descriptions Definition of ViewPoint Screens ViewPoint Manual—426801-001 3- 40
4 Process Definition Commands Introduction This section describes the syntax and semantics of the Define Process commands. The Define Process command library provides a set of commands to the TACL command interpreter. The library is available to you when you log on to your system in the same way as your other TACL library files. Section 2, Using ViewPoint gives a brief introduction to using the Define Process capability.
Define Process (DP) Command Process Definition Commands Table 4-1. Define Process Commands (page 2 of 2) Command Description PSTART Starts a defined process. PSTOP Stops a defined process, leaving it in a stopped and defined state. TOSS Deletes accumulated output or unprocessed input from either an input or output queue. UNDP Removes a background process. WAIT Displays accumulated output from a background process and waits for the process to prompt for more input.
Define Process (DP) Command Process Definition Commands omit this option, the defined process executes in the same processor as your TACL, unless a $CMON dictates otherwise. (See the Guardian Programmer’s Guide for information about $CMON processes.) DEBUG See the INSPECT option below. DEFMODE { OFF | ON } enables or disables the current TACL DEFINEs. It is the initial definition mode state for the new process. If omitted, TACL uses its current definition mode.
Define Process (DP) Command Process Definition Commands The INSPECT option also sets the debugging environment for any descendants of the defined process. See the Inspect Manual for more information. JOBID [ jobid ] sets the job ID for the new process. LIB [ file-name ] selects a user library file of object routines that is searched before the system library file to satisfy external references in the program being run.
Define Process (DP) Command Process Definition Commands NOHISTORY disables history processing for commands that are interactive with the process. If history processing is enabled, each command passed to the process in interactive mode is saved in the TACL history buffer. In addition, previous commands can be fixed with FC, invoked again with !, or viewed again using ? at the interactive prompt. Note that FC processing is trapped by TACL, not by the process.
Define Process (DP) Command Process Definition Commands This option also causes the process’s banner, if present, to show up in the output variable of the process after startup. If this is a problem, use the TOSS command to clear the output queue before running the process. QUIET forces future PSTART commands not to print a message when starting the defined process. If this option is omitted, PSTART prints a starting verification message when it is starting the process.
Define Process (DP) Command Process Definition Commands Considerations • • To resolve the program name for the file you specify, DP uses the current setting of your TACL #PMSEARCHLIST. This is unlike the TACL command, RUN, which uses your current #DEFAULTS to resolve the program name for your specified file. The default symbolic name of a defined process is the file-name portion of the process program file name.
_PCHECK Command Process Definition Commands Figure 4-1. Examples of Using the DP Command 1> DP FUP /PNAME FU,MACRO VOLUMER/ ==define the first process pstart: starting \HOME.$SYSTEM.SYS01.FUP process 2> FU ==invoke the process VOLUME $DATA.MYSUBV -3-- INFO * ==issue a local FUP command CODE EOF LAST MODIF OWNER RWEP $DATA.
_PCHECK Command Process Definition Commands that _PCHECK provides. Refer to Section 6, Customizing ViewPoint for further details and examples of the use of this command. Note. If your TACL use list is not set up to include :utils:DP, you must precede the _PCHECK command with :utils:dp. _PCHECK [ / option [ , option ]... / ] [ process-list ] option is any of the following options: EXISTENCE returns -1 if the process is defined; otherwise, it returns 0.
_PCHECK Command Process Definition Commands PREPARSE returns the name of the process’s preparser, if defined. PROCESSID returns the operating system name of the process, if the process is running. PROGRAMFILE returns the file name of the program being executed. QUICK returns -1 if the process is restarted without waiting for the prompt; otherwise, it returns 0. QUIET returns -1 if the confirmation message is printed when starting the process; otherwise, it returns 0.
PHELP Command Process Definition Commands Considerations If you specify more than one request option, the pieces of information are separated by spaces and are listed in the same order as the requests. If you specify more than one process name, the groups of information for each process are separated by spaces and are listed in the same order as the requests. Information is returned for previously-defined processes.
PINFO Command Process Definition Commands PINFO Command Use the PINFO command to display the status and characteristics of one or more defined processes. Note. If your TACL use list is not set up to include :utils:DP, you must precede the PINFO command with :utils:dp. PINFO [ / DETAIL / ] [ process-list ] DETAIL gives detailed information on status and characteristics of the specified defined processes. See Figure 4-3 for the display format provided by the DETAIL option.
POUT Command Process Definition Commands Figure 4-3. PINFO Listing With Detail NAME PROGRAM PROCESS FILE INPUT OUTPUT READY FLUP P PS EDEDIT FUP PERUSE PSMAIL EDIT 2,82 6,24 7,104 \EASTUS.4,64 $F108.#S13 $F108.#S12 $F108.#S15 $F108.#S11 EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY YES YES YES YES WAIT HISTORY PROMPT YES YES YES YES YES YES YES YES NO NO NO NO In the READY column, YES is displayed if the process is running and ready to accept commands; if not, NO is displayed.
PSHOW Command Process Definition Commands Considerations If you press the BREAK key during output and the process is prompting, the portion of the output viewed since the process prompted is not removed from the output queue. PSHOW Command The PSHOW command displays accumulated output from a defined process or input that is yet to be sent to the process. The display can be sent to a specified file or variable instead of to your terminal.
PSTART Command Process Definition Commands the input to see how many commands are left to be executed by the process or by looking at the output to see how much output has been produced. PSTART Command The PSTART command starts a process if the process is not already running. If the process cannot be started, a message is displayed. Note. If your TACL use list is not set up to include :utils:DP, you must precede the PSTART command with :utils:dp.
TOSS Command Process Definition Commands Considerations • • You can use the PSTOP command if your current user ID is included for the permissions of this process. Removing a defined process automatically stops the process. TOSS Command The TOSS command deletes accumulated input or output from an input or output queue of the process. You can use TOSS to discard unwanted input or output after issuing a NOWAIT command or after pressing the BREAK key during output. Note.
WAIT Command Process Definition Commands process-list is a list of unique, symbolic names you have assigned to defined processes. If you specify an asterisk (*), information for all your defined processes is displayed. Considerations • • Once a process is undefined, all attributes of the process are lost. To restart the process, you must define it again using DP. UNDP issues the PSTOP command to stop a process.
WAITREADY Command Process Definition Commands WAITREADY Command The WAITREADY command simply waits for the specified process to prompt. Output from the process is preserved and not displayed. You can use WAITREADY after issuing a NOWAIT command to synchronize with the process. If you change your mind and want to return to the TACL prompt before the process prompts, press the BREAK key. Note. If your TACL use list is not set up to include :utils:DP, you must precede the WAITREADY command with :utils:dp.
Issuing Commands to a Defined Process Process Definition Commands IN file-name takes input from the specified existing file. INV variable takes input from the specified existing variable. out-option is any of the following options: OUT file-name waits for the process to finish and then directs its output to the named file. If the file does not exist, it is created. OUTV variable waits for the process to finish and then directs its output to the named existing variable.
Process Definition Commands Issuing Commands to a Defined Process To exit from passthrough mode and return to the TACL prompt, type CTRL-Y or BREAK. Considerations • • • • • • • The BREAK key is processed by TACL and cannot be passed to a defined process. If a process depends on the BREAK key to cancel processing, you can stop processing only by stopping the process. If a process produces output in which you are not interested, use the TOSS command to delete the output.
5 Functional Description The first three figures in this section provide an overview of the ViewPoint architecture. The remainder of the section illustrates and discusses three major aspects of the application—TACL (command and control), network status, and event presentation. The section also introduces all significant terms relevant to the ViewPoint application and shows their functional context. This section describes how ViewPoint works.
Overview of ViewPoint Architecture Functional Description Figure 5-1. Operator View of ViewPoint CDT051.cdd The TACL screen (if available) provides all the standard features of the TACL product, plus the set of commands constituting the Define Process feature. This feature allows you to define (and instantly switch among) various processes anywhere in the network. In addition, you can switch to any of the other ViewPoint screens without exiting from any of the defined processes.
Overview of ViewPoint Architecture Functional Description control node (NCN). Commonly, network operators log on at this node, although it is possible to log on remotely. Figure 5-2. Network Presentation for Multiple Nodes CDT052.cdd There can be more than one NCN in a network, allowing various operators to share responsibilities or to have different levels of responsibility in network control. Figure 5-2 assumes one NCN and four remote nodes. One operator is logged on at this NCN.
ViewPoint TCP Functional Description ViewPoint TCP The ViewPoint TCP is the terminal control process portion of a Pathway application (see Introduction to Pathway). The TCP has three major functions: terminal management, code management, and message management. The terminal management function routes information to and from each logged-on operator. The code management function manages the multithreaded execution of the network application programs (SCREEN COBOL programs) for each operator.
TACL Functional Description Figure 5-3. Basic Network Presentation Architecture CDT053.cdd TACL commands are transmitted to a particular subsystem by way of the TACL in queue, and responses are received in the TACL out queue. You can manipulate both queues with Define Process commands.
Status Functional Description Status Status reports on a selected set of objects are obtained by switching to the Network Status Summary screen. After you switch to this screen, the status display is updated automatically at intervals that you can specify, or you can update the display manually by pressing a function key. The status request is issued by one of the SCREEN COBOL programs running under control of the ViewPoint TCP.
Network Command Functions Functional Description Figure 5-4. Role of the TACL Switcher CDT054.cdd When you are done with TACL, you press one of the function keys for status, events, extras, or profile, which returns you to the ViewPoint environment. This causes TACL to send a message to the TACL switcher that tells it TACL is done and that it should reactivate your task in the ViewPoint process.
Network Command Functions Functional Description Figure 5-5. TACL Processes for Multiple Operators CDT055.cdd TACL switcher processes are created dynamically, as needed, within a server class. Therefore, as illustrated by Figure 5-5, one TACL switcher (of the server class) is running; it is associated with the active command interpreter of Operator B. Assume that at some later time, Operator A presses the TACL function key.
Define Process Functional Description Figure 5-6. TACL Environment CDT056.cdd You can page through the display of commands and responses using the PREV PAGE (or PG UP) and NEXT PAGE (or PG DN) keys on your terminal (limited to the extent provided by your terminal’s internal storage; the storage is cleared when you leave the TACL environment). Define Process Figure 5-7 shows the concept of the Define Process capability of the ViewPoint application.
Define Process Functional Description Figure 5-7. Operator Access to Background Defined Processes CDT057.cdd You define background processes with the DP command and undefine them with the UNDP command. Choose your own symbolic name for each process you define. Then, to pass a command to a defined process, you simply enter the symbolic name of the process followed by the command.
Status Presentation Functional Description Refer to Section 4, Process Definition Commands for complete descriptions of the Define Process commands. Status Presentation The next five figures illustrate the concepts of status reporting and presentation. The first, Figure 5-8, shows an overview of the scheme used to present network status. A single operator terminal is shown, along with the three status screens.
Operation of Status Components Functional Description Configuring a status item primarily consists of specifying the kind of item (display type) and the system node from which to obtain the item. You must specify the particular object, and provide a description (up to 22 characters) that will mean something to you when the item is displayed on the Network Status Summary screen.
Operation of Status Components Functional Description Figure 5-9. Main Components of Status Reporting Function CDT059.cdd The subsystem process generically represents the source of status information. This can be a process for command processing (such as COMMGR for SNAX), a monitor process (such as PATHMON for Pathway), or simply a collection of callable procedures, as in the case of Measure.
Status Reporting in Networks Functional Description When your task in the ViewPoint TCP has received the information for all 16 items, it performs the required percentage calculations (compensating for any failed subsystems that do not report status) and displays the results on the Network Status Summary screen on your terminal. When you request another page of status information, your task in the ViewPoint TCP specifies this request to the status configuration server.
Status Reporting in Networks Functional Description Figure 5-10. Status Reporting in a Network CDT510.cdd If more than one operator is using your network, each can receive different status reports. Figure 5-10 shows status information is supplied to the status servers from subsystem processes. Figure 5-11 illustrates the case of three network operators, showing the same network as in Figure 5-10.
Status Reporting in Networks Functional Description NCN. Thus the term remote is not used, and the nodes are simply numbered 0 through 4. For simplicity, the subsystem processes have been omitted. Figure 5-11. Reporting Status to Multiple Operators CDT511.cdd Node 1 (a network control node) obtains status information only from itself and from node 4. Node 0 (the other NCN) obtains status information from itself, from nodes 2 and 3, and (note the dashed-line connection) from node 4.
Example Configuration of Status Servers Functional Description Operator A and Operator B are logged on at Node 0, and Operator C is logged on at Node 1. Note that each operator has his or her own set of status configuration files— (labeled A, B, and C). Thus each operator can select independent status displays. Example Configuration of Status Servers Figure 5-12 shows an example of status information being collected from a single node that could be the NCN or another node.
Event Presentation Functional Description The types of information obtainable from Measure are CPU-BUSY and AVERAGECPU-BUSY percentage values from CPU objects in the node, DISK-BUSY percentage values from disk objects in the node, and LINE-BUSY percentage values for communications lines connected to the node. TMFSERVE provides a count of transactions per second, measured at the time of each status request from the NCN.
Event Presentation Functional Description Figure 5-13. Operator View of Event Presentation CDT513.cdd On your terminal, one line of text is displayed for each event in the order received. The most recent event is inserted at the bottom of the page, and older ones roll off the top of the page. In this mode, the page that displays the 16 most recent event messages is called the END page.
Current and Historical Modes Functional Description and then resume updates by using the Thaw function key (SF8). You can specify a delay time so that updates do not occur too rapidly for you to read comfortably. When you request a particular page on the Primary or Alternate Events screen, the content of the displayed page is relative to the current END page. As new events arrive, the END page changes, and the set of events displayed for a particular page number changes accordingly.
Current and Historical Modes Functional Description order received. The Event Management Service detects that new messages are in the log and accordingly forwards the next message in order to the ViewPoint primary-events cache. This forwarding of messages causes the oldest message to roll off the other end of the cache if the cache is full of event messages. If you are displaying the END page of current events, the newest message appears as the 16th message on your screen.
Logging of Events Functional Description At this time, you can view this first page of historical events on your screen, if you select alternate events (function key SF3). If the cache is not yet full, the display continues to be updated with incoming messages until the cache is full. No further pages can be retrieved. This is indicated by the word END displayed at the top right corner of the Events screen. You can view only pages currently in the cache.
Event Distribution Functional Description • • Specific subjects affected Event is a critical event (emphasis token) or an action event (action token) The kinds and number of tokens included in the buffer can vary from subsystem to subsystem. Once the buffer is complete, it is sent to the node’s event collector process. The event collector inserts its own token representing the log time and records all this information in its current log file.
Event Filters Functional Description Event Filters Each filter is contained in a separate filter object file. For primary-events displays, these files are kept in the ViewPoint program subvolume. One filter is loaded at startup time, and it cannot be changed until the ViewPoint TCP is stopped and restarted. This filter is common to all operators logged on at a given NCN.
Event Distributors Functional Description Figure 5-18. Reading of Log Files by Event Distributors CDT518cdd The ViewPoint application defines one primary-events distributor in an NCN (assuming only one instance of ViewPoint is running). The alternate-event distributor, however, belongs to the operator, and there can be one associated with each alternate-events display. The operator can configure the alternate-event distributor to read from a specific log file in any selected node.
Event Distribution in Networks Functional Description log—just like the primary-events distributor. However, in this case, you can specify your own filter for reading only selected events (note the filter shown attached to the alternate-event distributor). That is something you cannot do with the primaryevents display. 3.
Event Distribution in Networks Functional Description Figure 5-19. Event Collection and Distribution in a Network CDT519.cdd From the central events log, event messages are read out by the primary-events distributor, and distributed to you and any other operators logged on at the same NCN through the ViewPoint event collection server. If more than one operator is using the same ViewPoint system, all operators receive the same primary-events messages.
Event Distribution in Networks Functional Description Figure 5-20. Distributing Events to Multiple Operators CDT520.cdd Figure 5-20 (on the previous page) shows only the key processes in this network configuration; other processes involved are shown in figures later in this section. The NCN event log in node 0 receives event messages from all five nodes—from its own local system and from four forwarding distributors in the other four nodes. Note the connecting lines labeled A and B.
Event Display Operations Functional Description Operator A and Operator B are logged on at Node 0, and Operator C is logged on at Node 1. Note that Operator A and Operator B read from the same events cache, which gets current event messages from the NCN event log through the event collection server. Multiple Collectors Up to five remote collectors can be specified as the source of events for each of the event screens (primary, alternate, or last events).
Event Display Operations Functional Description Figure 5-21. Distribution of Primary and Alternate Events CDT521.cdd The selected events are passed on through the filter to their own individual tasks in the event collection server. In turn, the task in the event collection server inserts these event messages into each alternate-events cache stored in its memory. Primary events, however, consist of incoming current events from possibly several nodes and are shared by both operators.
Event Display Operations Functional Description Figure 5-22. Event Presentation Processes for Two Operators CDT522.cdd System components (one each in any NCN) consist of the following: two event collection servers (one for last events, the other for all other events) and the ViewPoint TCP and its program subvolume. (There is also a ViewPoint data subvolume, not shown.
Other Event Operations Functional Description Other Event Operations Figure 5-23 illustrates four additional features not covered in the preceding figures: display of last events for a subject, loading of filters, display of event detail, and printing of screen messages as a printed log. These features are separately discussed in the next four paragraphs. The last-events distributor examines all event messages that come in to the NCN event log.
Summary of Event Operations Functional Description If a displayed message is truncated (because it is longer than 62 characters) or if you should want an expanded explanation of a given event message, you can request the additional information by going to the Event Detail screen. The ViewPoint TCP retrieves the information from the event-detail database through the event-detail server (a server class of one or more processes) and displays it on your screen.
Summary of Event Operations Functional Description Figure 5-24. Event Presentation Architecture CDT524.
Summary of Event Operations Functional Description • • • • Logging a current event The subsystem that generated the event sends an event message to the node’s event collector, which records the event message in the current log file. Transferring event messages to the NCN The forwarding distributor gets the current log file name from the event collector, reads newly logged event messages from the log, puts them through the distributor filter, and (if they pass) sends them to the NCN event collector.
Functional Description Extending the Functionality of ViewPoint which stores them in the alternate-events cache. A page of event messages is sent from the cache to the ViewPoint TCP for display on your terminal. You can use function keys to switch among the primary-events, alternate-events, and last-events displays. The events-display process manages the selection. Screen context (page number, marked events, and frozen or thawed state) is preserved when you switch among these event screens.
6 Customizing ViewPoint Introduction The ViewPoint application is an extensible Pathway application that you can use as a foundation for your software. This section describes the ways you can extend or customize the ViewPoint software for your system and network management needs. It describes how to: • • • • • • • • • Add custom event-message filters and process operator-supplied filter parameters. Add advisory text to be displayed for individual event messages on the Event Detail screen.
Writing Custom Event-Message Filters Customizing ViewPoint Writing Custom Event-Message Filters The primary EMS filter and any optional alternate filters installed in the ViewPoint application determine which event messages are selected for display. ViewPoint provides two default filters on the installation subvolume: one for the Primary Events screen and the other for the Alternate Events screen. The default filters tell the ViewPoint application what event messages to display at the node.
Basic Default Filtering Rules Customizing ViewPoint • • • • Basic rules for the default filters provided with the ViewPoint application Source code for the default primary-events filter Source code for the default alternate-events filter A description of how the default alternate-events filter uses dynamic filterconfiguration parameters Basic Default Filtering Rules The default primary-events and alternate-events filters follow certain basic rules.
The Default Primary-Events Filter Customizing ViewPoint Table 6-1. Pass Values and Corresponding ViewPoint Action Pass Value ViewPoint Action 1 Displays the event message highlighted as an action event. 2 Displays the event message highlighted as a critical event. 3 Dims the corresponding action-needed message and decreases the event count by 1. The default primary-events filter follows the basic rules listed above in determining what to display on the Primary Events and Last Events screens.
The Default Alternate-Events Filter Customizing ViewPoint Figure 6-1. Default Primary-Events Filter Source Code FILTER ViewPoint^Default^Filter; BEGIN [#DEF zems^val^ss TEXT |BODY|[zspi^val^TANDEM].[zspi^ssn^zems].0] BEGIN SSID(zems^val^ss) == fails on suppress^display events which are not == action-completion.
The Default Alternate-Events Filter Customizing ViewPoint Figure 6-2. Default Alternate-Events Filter Source Code (page 1 of 4) --------------------------------------------------------------------------------------- ViewPoint default alternate event filter. --- This filter processes parameters which may be specified --- from the second page of the Alternate Events --- Configuration screen. ZEMS and ZVPT TACL definition --- must be loaded to compile this filter.
The Default Alternate-Events Filter Customizing ViewPoint Figure 6-2.
The Default Alternate-Events Filter Customizing ViewPoint Figure 6-2. Default Alternate-Events Filter Source Code (page 3 of 4) ) and -- Test for matching process name (if provided). ( not tokenpresent(zvpt^fltr^processname) or decompose(zvpt^fltr^processname,destination name,name part) = decompose(ssid(zems^val^ssid,zems^tkn^xsenderid^pd), destination name,name part) ) and -- Test for matching event text (if provided).
The Default Alternate-Events Filter Customizing ViewPoint Figure 6-2. Default Alternate-Events Filter Source Code (page 4 of 4) else fail; end; -- events which have not been discarded by above conditions -- are returned to Viewpoint. Action and critical events -- are identified by the following conditions: -if -if action events are identified by the action^needed token. tokenpresent (zems^tkn^action^needed) then pass 1; critical events are identified by the emphasis token.
Customizing ViewPoint Filter Parameters for Dynamic Configuration Filter Parameters for Dynamic Configuration You can specify filter parameter values that dynamically change the default alternateevents filter (FLTRALT). Enter these values on page 2 of the Alternate Event Configuration screen. (Refer to the description of the Event Configuration screen in Section 3, Definition of ViewPoint Screens.
Adding Advisory Text for Events Customizing ViewPoint Adding Advisory Text for Events The Event Detail screen provides detailed information about a selected event message, including the probable cause of the event and the action recommended to solve the problem.
EVENTCX Record Structure Customizing ViewPoint Example 6-3. EMS Template VERSION: "T9153C20 - 15JUN88" SSID: ZPWY-VAL-SSID SSNAME: "PATHWAY" == Probable cause text for event 1034 MSG: ZVPT-TKN-CAUSE, 10340001 "The following text is only for demonstration purposes:<*CR>" "<*CR>" "The dolphin is a marine mammal known for its intelligence and playfulness. Dolphins are related to whales, but are smaller and have a beak-like snout.
An Enable Application to Generate Event-Detail Records Customizing ViewPoint Figure 6-3. DDL for Event-Detail Database definition ZVPT-EVENT-SSID. 03 Z-OWNER type character 8. 03 Z-NUMBER type binary 16. end record ZVPT-EVENT-DETAIL. file is "EVENTCX" key-sequenced. * field identifying the event 02 Z-EVENT. 03 Z-EVENT-SSID type ZVPT-EVENT-SSID. 03 Z-EVENT-NUMBER type binary 16. * fields providing 6 lines of probable cause text 02 Z-PROBABLE-CAUSE. 03 Z-LINE pic x(77) occurs 6 times.
Altering Prefix Text for Events Customizing ViewPoint 4. Call Enable, set attributes, and generate the application: ENABLE %SET RECORD ZVPT-EVENT-DETAIL %SET PATHCOMFILE ENABPATH ! %GENERATE DETAIL-PROG %EXIT 5. Execute the command file and run the application: OBEY ENABEX 6. Enter your custom advisory text from the keyboard using the Enable application screen interface.
Recovering Events After a Shutdown Customizing ViewPoint mm the minute in the hour that the event was generated. sysname the name of the system that generated the event. If you use setting 3, he prefix is displayed with the time of the event, the system name, and an identifying character (!, * or blank) in the beginning of the prefix to indicate the type of event (critical, action, or other); it will be in the format: ^hh:mm \sysname...
Adding TACL Macros and Routines Customizing ViewPoint again, the primary and alternate event displays configured to monitor events begin displaying events as they occur; any events previously stored in the events cache are lost. You get the best performance by setting the RECOVER-CACHE parameter to False. True means that all events previously contained in the event cache are retrieved.
Adding TACL Macros and Routines Customizing ViewPoint Example 6-4. Sample TACL Macros for Background Processes ?SECTION dpstart MACRO ==** dpstart ==** Start PATHCOM, CMI, and DNSCOM. DP PATHCOM /PNAME pcom/ $ZVPT DP CMI /PNAME cm/ DP DNSCOM /PNAME dnsc/ ?SECTION dpstatus MACRO ==** dpdns ==** List status of PATHMON, CMP, and DNS. pcom STATUS PATHMON cm STATUS CMP dnsc STATUS ?SECTION dpstop MACRO ==** dpstop ==** Stop PATHCOM, CMI, and DNSCOM. UNDP pcom cm dnsc Note.
Adding Extras Screens Customizing ViewPoint Example 6-5. Sample TACL Routine to Examine ViewPoint Clipboard ?SECTION utils:dnsinfo ROUTINE ==** [utils:dnsinfo ] ==* Look up info on all devices named in . #FRAME #PUSH :^device :^dnsout [#LOOP |WHILE| [#MORE] |DO| [#IF ([#ARGUMENT /VALUE :^device/ FILENAME WORD/SPACE/] = 1) |THEN| [#IF ([#MATCH \*.
Linkage Section of ZVPT-EXTRAS Customizing ViewPoint ViewPoint application to include custom screens specific to your application or to display screens of other applications. The Extras feature allows you to add a custom screen by writing a SCREEN COBOL program to drive that screen, along with any Pathway servers needed to perform the functions the operator can request from the new screen.
Linkage Section of ZVPT-EXTRAS Customizing ViewPoint Figure 6-4. Linkage Section of ZVPT-EXTRAS 01 ZVPT-IPC-HDR. 02 Z-REQUEST-CODE pic s9(4) 02 Z-PW-REPLY-CODE redefines Z-REQUEST-CODE pic s9(4) 02 filler pic x. 02 Z-VERSION-CODE. 03 LETTER pic a. 03 REV-NUMBER pic 99. 02 Z-IPC-RETN-CODE pic s9(4) 02 Z-IPC-RETN-CODE-DETAIL pic s9(4) 02 Z-LOG-THIS-IPC pic a. 02 filler pic x. 01 ZVPT-LINK-DATA-L.
Linkage Section of ZVPT-EXTRAS Customizing ViewPoint Descriptions of the pertinent fields follow. Fields shown in Figure 6-8 that are not mentioned below exist for compatibility reasons; your ZVPT-EXTRAS program unit should not alter those fields or rely upon them for information. Z-VERSION-CODE of ZVPT-IPC-HDR provides the identifying letter (LETTER) and number (REV-NUMBER) indicating the version of the ViewPoint software that is running.
Linkage Section of ZVPT-EXTRAS Customizing ViewPoint Z-CURRENT-VOL-SUBVOL of ZVPT-LINK-DATA-L is the current default volume and subvolume for the TACL process associated with the terminal. The volume and subvolume names are in internal form (16 characters). This field is used to resolve file names. It corresponds to the user’s default subvolume as of the last time the TACL screen was entered. If no TACL connection is present, this field contains the name of the ViewPoint data subvolume.
Passing Marked Event Messages Customizing ViewPoint "Alt-Event" "Last-Event" "TACL" "Profile" "Exit" Alternate Events screen Last Events screen TACL conversational screen Profile screen Exit the ViewPoint application for this terminal Z-OPTION-LINE of ZVPT-USER-REQUEST is optional text to be passed to the invoked screen. On entry, this contains the text that was on the option line when the Extras screen was invoked.
Passing Marked Event Messages Customizing ViewPoint The DDL in Figure 6-5 shows the EVNTMRKD record structure. This DDL is distributed with ViewPoint in the file GDDL (with language versions in the files GTAL for TAL, GCOB for COBOL85, and GLNK for SCREEN COBOL). Figure 6-5. DDL for Marked Event Database (EVNTMRKD) definition ZVPT-MARKED-KEY. * Key of record within Event-Marked file. 02 Z-LOGICAL-TERM pic x(16). 02 Z-EVENT-COUNT type binary 16. end. definition ZVPT-EVENT-MARKED. 02 ZVPT-MARKED-KEY type *.
EXTRAS-DELETE Interface Customizing ViewPoint Z-DELETED-FLAG of ZVPT-EVENT-MARKED is a Boolean value indicating whether an event was deleted. TRUE (-1) indicates that the event was an action or critical event, and that it was deleted either automatically or by operator action. FALSE (0) indicates that the event was not deleted. Z-EVENT-BUFFER-LEN of ZVPT-EVENT-MARKED is the event message length in bytes. Z-EVENT-BUFFER of ZVPT-EVENT-MARKED is an SPI buffer containing the event message.
Preparing Your ZVPT-EXTRAS Program for Installation Customizing ViewPoint Figure 6-6. DDL for ZVPT-DELETE-ACCEPTED definition ZVPT-DELETE-ACCEPTED. 02 Z-DELETE-ACCEPTED-ALL-FLAGS pic x(50). 02 Z-DELETE-ACCEPTED-FLAGS pic 9 occurs 50 times redefines Z-DELETE-ACCEPTED-ALL-FLAGS. 88 Z-DELETE-ACCEPTED value 1. 02 Z-REASON pic x(66). end. Event messages selected for acknowledgment are passed as messages in SPI format in a data file.
Custom Status Servers Customizing ViewPoint to the Pathway SCREEN COBOL Reference Manual for instructions on using SEND to an externally defined server class. For information on how to add server classes to the Pathway application and on how to configure a ZVPT-EXTRAS-DELETE program unit into the ViewPoint application, refer to Section 7, Installation, Configuration, and Startup. Custom Status Servers The Network Status Summary screen gives an overview of the status of the system or network.
Status Servers Customizing ViewPoint You can customize the Network Status Summary screen to display other status items in addition to the standard items. These can include information from subsystems you write, such as information about the operation of automatic teller machines (ATMs). They can also include information from Compaq subsystems, such as the batch subsystem, that are not monitored by the basic ViewPoint application.
Customizing ViewPoint Commands for and Responses From the Status Server Figure 6-7. Example of Status Reporting Configuration CDT067.cdd Commands for and Responses From the Status Server The ViewPoint application maintains one or more status configuration files, one for each operator who is currently using the ViewPoint application.
Customizing ViewPoint Commands for and Responses From the Status Server certain function to be performed, the ViewPoint software sends a message to the status server requesting that function. The status server performs the specified function, then returns a response message to the requester. The ViewPoint requesters send six types of commands to the status server. The commands are: • • • • • SCAN-ITEM and NEXT-ITEM Ask the server for information about status items that the server supports.
Commands for and Responses From the Status Server Customizing ViewPoint Figure 6-8. Status-Server Message Header definition ZVPT-IPC-HDR. 02 Z-REQUEST-CODE type binary 02 Z-PW-REPLY-CODE redefines Z-REQUEST-CODE type binary 88 Z-RQST-OK value is 0. 88 Z-RQST-ERR value is 3. 02 filler pic x. 02 Z-VERSION-CODE. 03 Z-LETTER pic a. 03 Z-REV-NUMBER pic 99. 02 Z-IPC-RETN-CODE type binary value 0. 02 Z-IPC-RETN-CODE-DETAIL type binary value 0. 02 Z-LOG-THIS-IPC pic a. 02 filler pic x. end.
Status-Server Command Codes Customizing ViewPoint Figure 6-9. Status-Server Command Codes and Error Codes * REQUEST-CODE VALUES CONSTANT CONSTANT CONSTANT CONSTANT CONSTANT CONSTANT Z-GET-VERSION-CODE Z-SCAN-ITEM-CODE Z-NEXT-ITEM-CODE Z-CHECK-ITEM-CODE Z-SAMPLE-ITEM-CODE Z-SAMPLE-LIST-CODE VALUE VALUE VALUE VALUE VALUE VALUE IS IS IS IS IS IS 1. 2. 3. 4. 5. 6.
Status-Server Error Codes Customizing ViewPoint implemented by the server, the server should return the error code ZERR-STATEND-OF-TYPES. Z-CHECK-ITEM-CODE This command provides a status item that has been specified from the Status Item Configuration screen. The server should check the status item for consistency. Possible error codes returned are ZERR-STAT-NO-SUCH-TYPE, ZERR-STAT-NOSUCH-OBJECT, and ZERR-STAT-CNFG-INCOMPATIBLE.
Status Items Customizing ViewPoint ZERR-STAT-NO-SUCH-TYPE The display type provided in Z-ITEM-NAME of ZVPT-STATUS-ITEM (see Figure 6-14 and the discussion following it) did not match any that are implemented by this status server. ZERR-STAT-NO-SUCH-OBJECT The object name provided was not a valid object for the display type provided. ZERR-STAT-END-OF-TYPES The SCAN-NEXT command was made, but scanning has progressed past the last status item that is supported by this status server.
Status Items Customizing ViewPoint Figure 6-10. Status-Server Structures definition ZVPT-STATUS-VALUE type binary 64. definition ZVPT-TIMESTAMP type binary 64. definition ZVPT-BOOLEAN pic x. definition ZVPT-ITEM-NAME. 02 Z-ITEM-TYPE pic x(30). 02 Z-OBJECT-NAME pic x(24). end. definition ZVPT-STATUS-ITEM. 02 Z-ITEM-DESCRIPTION pic x(36). 02 Z-ITEM-NAME type ZVPT-ITEM-NAME. 02 Z-VALUE-FOR-100 type ZVPT-STATUS-VALUE. 02 Z-USE-MAXIMUM type ZVPT-BOOLEAN. 02 Z-REVERSE-SIGNIFY type ZVPT-BOOLEAN.
Status Items Customizing ViewPoint Z-VALUE-FOR-100 This is the value used to compute the percentage for counter-type values when Z-USE-MAXIMUM is FALSE. If the server allows Z-USE-MAXIMUM to be FALSE for an item, it should require that this field have a reasonable value when performing CHECK-ITEM for the item. If Z-USE-MAXIMUM is TRUE or if this is a busy-timer item, this field is ignored.
Message Structures for Status Commands and Responses Customizing ViewPoint busy. This value is a snapshot of the busy timer; successive snapshots are used to compute a percentage. Counters are scalar values that are used directly. They are a count of the number of objects up, or throughput counts. Counter values can be fractions; a Z-SCALE field is included in the ZVPT-STATUSITEM structure. Its value (0, 1, or 2) indicates the number of decimal positions assumed in the count.
Message Structures for Status Commands and Responses Customizing ViewPoint Figure 6-11. Status-Server Command and Response Messages (page 1 of 2) Request/Reply Headers definition ZVPT-REQUEST-HEADER. 02 Z-IPC-HDR type ZVPT-IPC-HDR. 02 Z-REQUEST-CODE type ZVPT-REQUEST-CODE. end. definition ZVPT-REPLY-HEADER. 02 Z-IPC-HDR type ZVPT-IPC-HDR. end.
Message Structures for Status Commands and Responses Customizing ViewPoint Figure 6-11. Status-Server Command and Response Messages (page 2 of 2) definition ZVPT-CHECK-ITEM-REPLY. 02 Z-STATUS-ITEM type ZVPT-STATUS-ITEM. end. definition ZVPT-SAMPLE-ITEM-REQUEST. 02 Z-ITEM-NAME type ZVPT-ITEM-NAME. end. definition ZVPT-SAMPLE-ITEM-REPLY. 02 Z-STATUS-VALUE type ZVPT-STATUS-VALUE. 02 Z-MAXIMUM-VALUE type ZVPT-STATUS-VALUE. 02 Z-TIMESTAMP type ZVPT-TIMESTAMP. end. definition ZVPT-SAMPLE-LIST-REPLY.
Integrating Your Status Server With the ViewPoint Application Customizing ViewPoint Integrating Your Status Server With the ViewPoint Application To integrate your custom status server with the ViewPoint application, you first define the status server as a dynamic server class to the ViewPoint application or to another Pathway system.
Using ViewPoint in the IOC Customizing ViewPoint ViewPoint Manual—426801-001 6- 41
Using ViewPoint in the IOC Customizing ViewPoint ViewPoint Manual—426801-001 6- 42
7 Installation, Configuration, and Startup This section describes the steps for installing, configuring, and starting ViewPoint. The procedures in this section must be completed before you can do the procedures shown in Section 2, Using ViewPoint. ViewPoint Installation The ViewPoint software is installed at your site with newly released Compaq software, using the Install program that is documented in the System Generation Manual.
Before You Begin Installation, Configuration, and Startup The Install routine provided by ViewPoint automates the installation and configuration of ViewPoint by using information you supply to install and update necessary program, data, and configuration files. The files that are affected include: • • • Program and configuration files for the ViewPoint Compaq NonStop™ TS/MP requesters and servers. Data files used by the NonStop™ TS/MP requesters and servers.
Installation Steps Installation, Configuration, and Startup system. To avoid a security error, make sure you check the security attributes of the ViewPoint ISV files. To use the ViewPoint TACL routines :UTILS:DP, :UTILS:VIEWPT, and :UTILS:VPTLIB, without typing :utils every time, include these TACL routines in your use list. To do this for all users on your system, type the following commands in your TACLLOCL file ($SYSTEM.SYSTEM.TACLLOCAL).
Installation Steps Installation, Configuration, and Startup • To update the ViewPoint configuration file, type: VIEWPT:INSTALL /configure/ [filename] filename is the name of the define file. If you do not specify a define file, ViewPoint prompts you for a file name. If you have not created a define file, you can use the default file; just press return when prompted for the file name.
Installation Steps Installation, Configuration, and Startup Example 7-2. Installation Options Viewpoint installation options: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. ISV PROGRAM-SUBVOL DATA-SUBVOL PATHWAY-POBJ EVENT-NOTIFY CPUS SERVER-PRIORITY TCP-PRIORITY PRIMARY-COLLECTOR PRIMARY-FILTER LAST-EVENT-COLLECTOR LAST-EVENT-FILTER CLEANUP-HOUR PRIMARY-CACHESIZE LAST-EVENT-CASHESIZE RECOVER-CACHE SupressUnanswered PATHWAY-OWNER PATHWAY-SECURITY PROGRAM-SECURITY $DSV.
NonStop™ TS/MP Configuration Installation, Configuration, and Startup NonStop™ TS/MP Configuration The Install routine lets you set the most commonly used parameters appearing in the PATHDEFS and PATHCONF configuration files. After installing ViewPoint, you may need to change other default parameter values that do not apply to your system (see Appendix A, Server Assigns and Parametersfor examples). Be sure to review these files for accuracy before starting ViewPoint.
STARTUP Considerations Installation, Configuration, and Startup • To cold start the ViewPoint NonStop™ TS/MP system, type: VOLUME program-subvol VIEWPT:STARTCOLD [/CPU pathmon-cpu, PRI process-priority-number/] [pathmon-name] pathmon-cpu is the PATHMON primary CPU. cpu must be different from the back up cpu number or you will receive a PATHCOM error (See error 2009 in Section 14 of the NonStop™ TS/MP Management Programming Event and Error Message Manual).
Default Configuration Files Installation, Configuration, and Startup The Event Management Service (EMS) forwarding distributor processes are not started automatically. You can include them in the ViewPoint NonStop™ TS/MP application. If included, these processes are started by the viewpt:startup routine. The processes of the Distributed Name Service (DNS) are not started automatically by when you start up ViewPoint. These processes, if applicable to your system, should be started independently.
Changing ViewPoint Configuration Installation, Configuration, and Startup • Adding a new custom status server to the application. To make such changes, you must stop ViewPoint, edit the PATHDEFS file, and then restart ViewPoint from a cold state. When you cold start ViewPoint, it uses the changed PATHDEFS file with its new configuration attributes. You should print a hardcopy of the default PATHDEFS file supplied by ViewPoint before you edit PATHDEFS; you can then edit the file with more confidence.
Changing ViewPoint Configuration Installation, Configuration, and Startup you add the CALL-EXTRAS-DELETE parameter to the attributes of the ZVPT-EVNTCOLL server, as shown: SET SERVER PARAM CALL-EXTRAS-DELETE "TRUE" Before you call either the ZVPT-EXTRAS or ZVPT-EXTRAS-DELETE program units, you must be sure they are compiled and available in your object library. You can use SCREEN COBOL Utility Program (SCUP) to check the contents of this library.
Running ViewPoint With TACL Installation, Configuration, and Startup Running ViewPoint With TACL The following is a description of how to run ViewPoint with TACL. Note. If your ViewPoint is to run without access to TACL, skip this discussion and read “Running ViewPoint Without TACL” later in this section. Once the ViewPoint application is installed and configured, individual terminals gain access to ViewPoint by executing the TACL routine, VIEWPT: VIEWPT [pathmon-name] The default pathmon-name is $ZVPT.
Logon Considerations Installation, Configuration, and Startup pathmon-name The name that you or your system manager has given the PATHMON. The default is ZVPT. If the COLOR option is requested, ViewPoint loads a color map into the PCT process during initialization and, if TACL is available, each time the user reenters block mode from the TACL screen. When the user exits from ViewPoint, the color map is reset to the default setting (PCT.INI). (PCT.
Exiting From ViewPoint Installation, Configuration, and Startup If ViewPoint is run without access to TACL (see “Running ViewPoint without TACL” later in this section), then users do not have access to the background processes available through Define Process commands. Exiting From ViewPoint If the ViewPoint application has access to TACL, the operator can exit ViewPoint from any of the base-level screens by pressing the exit key, SF16.
Restrictions When TACL is Not Present Installation, Configuration, and Startup terminal where you want ViewPoint to run, the Pathway configuration might include the following PATHCOM commands: SET TERM INITIAL ZVPT-MAIN SET TERM TCP ZVPT-TCP SET TERM FILE network-file-name-of-terminal SET TERM AUTORESTART 5 <--or whatever value is appropriate SET TERM BREAK ON <--if the BREAK key is to be disabled SET TERM TYPE T16-6530:0 SET TERM PRINTER print-device-name SET TERM MAXINPUTMSGS 1 ADD TERM logical-terminal
Installing and Starting Up ViewPoint Installation, Configuration, and Startup There are three aspects of ViewPoint security. It controls who can do the following: • • • Install and start ViewPoint Run ViewPoint Perform specific functions through defined processes Installing and Starting Up ViewPoint When the system Install program is running, the ViewPoint ISV files are restored with the operator’s current default security and ownership values.
Running ViewPoint Installation, Configuration, and Startup In addition, anyone starting up ViewPoint must have read or write access to the collector process $0 (or any EMS Alternate Collector which might be configured) and must have read access to PATHDEFS, PATHCONF, and PATHSTRT. Security settings in PATHDEFS and PATHCONF should be checked and changed, if necessary, so that they reflect the person starting up ViewPoint.
Executing Defined Processes Installation, Configuration, and Startup ^ *ERROR* Security violation Exiting from ViewPoint. Executing Defined Processes Define Process macros implement no security. They can be executed by anyone using TACL on a system where the ViewPoint application is installed. The assumption is that processes that are defined implement the desired security.
Version Information Installation, Configuration, and Startup You can text the existence of the version variable within a routine using ViewPoint to ensure that the correct version of the library is loaded, or the contents of _VIEWPOINTVERSION can be tested.
A Server Assigns and Parameters Server Assigns Table A-1 is a partial list of the SET SERVER ASSIGN values that are supported by ViewPoint servers. You can use these values to modify your ViewPoint configuration. The default values are shown in parentheses. You can change server assign values for a cold startup of ViewPoint by changing the Pathway configuration file PATHDEFS.
Server Assigns Server Assigns and Parameters Table A-1. Server Assigns (page 2 of 4) DISTRIBUTOR ($system.system.emsdist) identifies the program file name of the EMS distributor process for the primary-events, alternate-events, or last-events displays. If the default value is used (or defaulted to) for this assign, the distributor is started on a remote system if the collector(s) are all on a single remote system.
Server Assigns Server Assigns and Parameters Table A-1. Server Assigns (page 3 of 4) LAST-EVENT-COLLECTOR ($0) identifies the EMS collector(s) or the log file from which events are read for the last-event display. As many as five collectors or one log file can be selected. Events from all specified collectors are merged. Multiple collectors are specified by creating an edit file containing a list of the collector-process names. The edit file name is given as the value for this assign.
Server Parameters Server Assigns and Parameters Table A-1. Server Assigns (page 4 of 4) TANDEM-DETAIL (eventtd) identifies the file containing Compaq-provided text for the probable cause and recommended action for events. Servers: ZVPT-EVNT-DETL TERM-TO-TACL (termtacl) identifies the file used during ViewPoint invocation to provide a mapping from the physical terminal to the TACL server port name. Servers: ZVPT-TACL-SWCH TMF-SERVER ($system.system.
Server Parameters Server Assigns and Parameters Table A-2. Server Parameters (page 1 of 5) ALTERNATE-DISTRIBUTOR-CPU (-1) provides the CPU number in which ViewPoint runs the alternate events distributor. If the CPU field of the Alternate Event Configuration screen is left blank and this parameter is defined with a valid CPU, ViewPoint uses the value of the parameter; otherwise, ViewPoint uses the CPU of the server.
Server Parameters Server Assigns and Parameters Table A-2. Server Parameters (page 2 of 5) DISPLAY-KANJI (FALSE) supports displaying special characters, such as Kanji, that are embedded in the event text. If this parameter is set to FALSE or not defined, ViewPoint strips out non-displayable characters that have ASCII code values below 32 (space character) or between 126 (tilde character) and 160 (a graphic character) from the event text.
Server Parameters Server Assigns and Parameters Table A-2. Server Parameters (page 3 of 5) IGNORELASTEVENT (FALSE) allows two event collection servers to run simultaneously and thereby improve event reception performance. IGNORELASTEVENT indicates whether the server should ignore the last-event display. If the display is ignored, no events are collected for that display and any requests for service are rejected with a ViewPoint error 325.
Server Parameters Server Assigns and Parameters Table A-2. Server Parameters (page 4 of 5) MAXDELAY (1440) identifies the maximum time in minutes that ViewPoint allows the I/O of a message to a terminal's 25th line to be pending until the I/O completes. The default is 1440 minutes (one day). If a message does not complete in this amount of time, ViewPoint cancels the I/O. Servers: ZVPT-EVNT-NTFY MAXBUFFERS (50) provides the maximum number of messages that can be pending against all devices.
Server Parameters Server Assigns and Parameters Table A-2. Server Parameters (page 5 of 5) PRIMARY-DISTRIBUTOR-CPU (-1) provides the CPU number for the CPU in which ViewPoint runs the primary events distributor. If this parameter is defined with a valid CPU, ViewPoint uses the value of the parameter; otherwise, ViewPoint uses the CPU of the server.
Server Parameters Server Assigns and Parameters ViewPoint Manual—426801-001 A -10
B Error Messages This appendix gives a list of the error and advisory messages that are displayed by ViewPoint. (An advisory message, in contrast to an error message, advises the operator of successful completion of an operation or tells the operator what step to perform next.) Each error or advisory message has an associated message number. However, these numbers are displayed only for error messages; the number is not displayed for advisory messages.
Error Error Messages Error In this example, the first message indicates ViewPoint error number 0336, listed in this appendix as “Please enter a correct filter file name.” The second message is the P-register trace call location for the process. You should include all numbers provided with the error messages along with any documentation of a problem when you report the problem. For ease of reference, the error messages in this appendix list the error number first. 0001 (A) Screen printed. Cause.
Error Error Messages Recovery. N/A 0006 Select lines to clip. Then press F10. Cause. You did not select any lines on the screen to copy to your clipboard file. Effect. No lines are copied to the clipboard file. Recovery. Select lines on the screen by typing any character in column 1 of those lines and press F10. 0007 Couldn't clip to the clipboard file. Cause. ViewPoint could not copy the specified lines to your clipboard file because the file is inaccessible. Effect. No lines are copied. Recovery.
Error Error Messages Effect. Your current operation might be unsuccessful. Recovery. Press F15 for Help in choosing another key. 0012 Garbage Collection server send error: Cause. A server SEND error was received while ViewPoint was invoking the garbagecollection server. The termination status of the SEND is displayed as the second number in the error message. Effect. Garbage collection is not successful. Recovery. See the Pathway SCREEN COBOL Reference Manual for an explanation of SEND errors.
Error Error Messages 0019 An internal error was returned from SSINIT: Cause. An SSINIT on a buffer resulted in an error. The error number is included in the message. Effect. Your current operation may be unsuccessful. Recovery. See the SPI Programming Manual for an explanation of the error. 0020 An internal error was returned from SSGET: Cause. An SSGET on a buffer resulted in an error. The error number is included in the message. Effect. Your current operation may be unsuccessful. Recovery.
Error Error Messages 0023 An UMP message was rejected by the TCP: Cause. The Pathway on-error clause was triggered by the call to the EXTRAS program unit. The Pathway error number is provided as the second number in the message. Effect. Your current operation may be unsuccessful. Recovery. See the Pathway Application Programming Guide for an explanation of the error. 0024 A CALL error was returned when invoking an EXTRAS program. Cause.
Error Error Messages 0027 Enter correct page number. Cause. You entered an incorrect page number in the option line. Effect. The requested page is not displayed. Recovery. Enter a correct number that does not include decimal points or letters. 0030 A CALL error was returned when invoking the DSM/PM program: Cause. The Pathway on-error clause was triggered by the call to the DSM/PM program unit. The Pathway error number is provided as the second number in the message. Effect. DSM/PM is not invoked.
Error Error Messages Effect. Your current operation may be unsuccessful. Recovery. Supply the error numbers when reporting this internal error to a Compaq representative. 0102 ZVPT-TACL-WORK call error: Cause. A Pathway error was reported on the CALL. Effect. Your current operation may be unsuccessful. Recovery. See the Pathway SCREEN COBOL Reference Manual for an explanation of CALL errors. 0103 Error opening the terminal-to-TACL file: Cause.
Error Error Messages 0106 Reply from TACL was too small. Cause. The message received from TACL was too small. Effect. Your current operation may be unsuccessful. Recovery. Make sure the TACL library version matches the ZVPT-TACL-SWCH version. Supply the error numbers when reporting this internal error to a Compaq representative. 0107 Error writing to the terminal-to-TACL file: Cause. An error occurred while writing to the TERMTACL file. Effect. Initialization is aborted. Recovery.
Error Error Messages 0204 ZVPT-STAT-CNFG request error: Cause. A request error was received while ViewPoint was invoking the status configuration server. Effect. The current status configuration file is not updated. Recovery. Report this internal error to a Compaq representative, and be sure to supply the error numbers. 0205 Status collection server send error: Cause. An error was returned from the SEND to the collection server. The SEND error returned is included in the message. Effect.
Error Error Messages 0208 The object specified is not valid for the status type. Cause. The object specified in the Object Name field is not valid for the status type specified. Effect. No object name is selected. Recovery. Enter a valid object name and press F12. 0210 The parameters specified in the item configuration are incompatible. Cause. The configuration values given (aside from status type and object) are incompatible. Effect. No values are selected. Recovery.
Error Error Messages 0213 Provide PATHMON name on the specified system. Cause. You entered a system name without a PATHMON name in the Under PATHMON field on the Status Item Configuration screen. Effect. No PATHMON name is selected. Recovery. Enter a correct PATHMON name. If the current (NCN) PATHMON is desired, then both system and PATHMON names should be blank. 0214 (A) Item deleted from configuration. Cause. A status item was successfully deleted from the Network Status Summary screen. Effect.
Error Error Messages Effect. Status collection may not be successful. Recovery. Termination status should be examined to determine the cause of the error. 0218 Please select items and press F6 to delete. Cause. The Delete function key (F6) was pressed when no items were selected. Effect. No items are deleted. Recovery. Select an item by positioning the cursor next to it and press F6. 0219 (A) Items deleted from configuration. Cause. Items have been deleted from the status item configuration. Effect.
Error Error Messages 0222 MEASURE error returned while sampling the object: Cause. A Measure error was returned by the MEASREADACTIVE call for the specified object. Effect. An ILLEGALMEASNUM error results in an automatic restart of the measurement. Recovery. See the Measure Reference Manual for an explanation of Measure errors. 0223 File error reported while reading status configuration. Cause. A file-system error was reported while ViewPoint was opening or reading the status configuration file.
Error Error Messages 0226 Provide a correct status configuration file name. Cause. The file name provided could not be converted into a valid internal file name. Effect. No status configuration file is created. Recovery. Enter a new file name for your status configuration file. 0227 File error occurred during configuration file creation. Cause. A file-system error occurred while creating, opening, or writing to the new configuration file.
Error Error Messages Effect. Information only Recovery. N/A 0231 (A) The status configuration file has been created. Cause. The status configuration file has been created. This is reported from the Profile screen when the Configuration File field is modified and the confirmation flag is set. Effect. Information only Recovery. N/A 0232 Device information is unavailable due to internal error starting PUP. Cause.
Error Error Messages 0235 NEWPROCESS of subsystem server results in a file-system error. Cause. The NEWPROCESS procedure of the TMFSERVE or Measure subsystems report this error if an error is detected on the program file, the library file, the process name, the swap file, or the extended-segment swap file. The file-system error number is supplied. Effect. Certain status items may not be measured. Recovery.
Error Error Messages Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0239 An internal error was detected in the programmatic interface. Cause. An SSINIT, SSGET, SSPUT, or other SPI routine returned a nonzero status. This is an internal error. The SPI error number is included in this message. Effect. ViewPoint may not report correct information. Recovery. See the SPI Programming Manual for an explanation of SPI procedure errors.
Error Error Messages 0243 Status display server request error: Cause. A request to the status display server resulted in an internal error. Effect. Certain status items may not be measured. Recovery. Supply the error numbers when reporting this internal error to a Compaq representative. 0244 File error occurred while accessing the status cache file: Cause. A file-system error occurred while ViewPoint was accessing the status cache file.
Error Error Messages 0247 File error returned from NEWPROCESS while starting the measurement: Cause. The Measure subsystem is running, but a NEWPROCESS file-system error was returned from the MEASOPEN call in starting the measurement. This probably indicates an error during the start of the Measure file-handling program (MEASFH on SYSnn subvolume). The file-system error number is included in the message. Effect. Certain status items may not be measured. Recovery.
Error Error Messages Recovery. See the System Procedure Errors and Messages Manual for an explanation of NEWPROCESS errors. 0251 The status configuration file version is not recognized. Cause. This configuration file version is not recognized by the software. Effect. The configuration file cannot be used. Recovery. Try creating a new configuration file. 0252 SCP program must be owned by SUPER.SUPER and given PROGID authority. Cause. The requested sample requires that SCP be used.
Error Error Messages Recovery. Enter a Y or N in the indicated field. 0255 The CPU required for this sample is down or does not exist. Cause. The CPU required for this sample is down or does not exist according to PROCESSORSTATUS status values obtained during the sample. Effect. The CPU item is not measured. Recovery. Enter an existing CPU on the Status Configuration screen. 0256 Enter correct decimal value of MAXIMUM. Cause. The value entered in the “Use Maximum for 100%” field is not correct.
Error Error Messages Effect. Information only Recovery. N/A 0302 (A) Events acknowledged. Cause. The events you selected are acknowledged. Effect. Information only Recovery. N/A 0303 (A) Event configuration deleted. Cause. The settings in the current configuration screen are deleted. Effect. Information only Recovery. N/A 0304 The selected event does not have an appropriate subject. Cause. The first (or other) subject in the event cannot be externalized or does not exist. Effect.
Error Error Messages 0306 Please select events and press F11 for detail information. Cause. F11 was pressed when no event was selected. Effect. No detailed information is displayed. Recovery. Select an event and press F11 to get detailed information on the event. 0307 ZVPT-EVNT-DISP send error: Cause. A SEND to the event collection server resulted in an error. Effect. The event screen may not be updated correctly. Recovery.
Error Error Messages Recovery. Supply the error numbers when reporting this internal error to a Compaq representative. 0311 Please press F12 to configure this display. Cause. The Alternate-Events screen is not configured. Effect. Events are not collected. Recovery. Press F12 to configure the screen. 0312 The selected event is no longer available. Cause. The selected event is no longer in the event cache. Effect. The event is not available for your particular operation. Recovery. Select another event.
Error Error Messages Effect. The events screen might not be updated correctly. Or, default source code is not included in your custom filter, and you have supplied default parameter values. Recovery. See the EMS Manual for an explanation of distributor errors. For default source code, see Figure 6-2 in Section 6, “Customizing ViewPoint.” 0316 Error occurred when opening the event terminal file: Cause. This file-system error occurred when ViewPoint opened the event terminal file. Effect.
Error Error Messages 0320 ZVPT-EVNT-DETL Send Error: Cause. A SEND to the event detail server resulted in an error. Effect. Event detail information may not be available. Recovery. See the Pathway SCREEN COBOL Reference Manual for an explanation of SEND errors. 0321 ZVPT-EVNT-DETL Request Error: Cause. The event detail server detected an internal error. Effect. Event detail information may not be available. Recovery.
Error Error Messages 0324 (A)P No old events were found; continuing with current events. Cause. You tried to display old events when they were not available. Effect. No events are displayed. Recovery. Specify more recent events on the event configuration screen. 0325 Error occurred when opening the last event cache file: Cause. This file-system error occurred during an OPEN of the last event cache file. Effect. The Last Events screen might not be updated correctly. Recovery.
Error Error Messages Effect. The event configuration file may not be updated. Recovery. See the Pathway SCREEN COBOL Reference Manual for an explanation of SEND errors. 0330 ZVPT-EVNT-CNFG request error: Cause. The event configuration server detected an internal error. Effect. The event configuration file may not be updated. Recovery. Supply the error numbers when reporting this internal error to a Compaq representative. 0331 An error occurred during a read of the event configuration file: Cause.
Error Error Messages 0334 Please enter a correct event configuration filename. Cause. The file name you entered is not valid. Effect. No name is selected. Recovery. Enter a valid file name. 0335 Error occurred when creating the event configuration file: Cause. A file-system error was reported while ViewPoint was creating the status configuration file. The error reported is shown as the second number in the message. Effect. The values entered in the event configuration file may not be saved. Recovery.
Error Error Messages Recovery. Set the After field to an earlier date. 0339 Please enter a positive or zero delay time. Cause. An invalid delay time was entered on the configuration screen. Effect. No events are displayed. Recovery. Enter a delay time that is either positive or zero. 0340 Please use the correct number of pages desired. Cause. An invalid page number was entered. Effect. No page number is selected. Recovery. Enter a number between 1 and 750. 0341 (A) Event configuration updated.
Error Error Messages 0344 (A) Press F14 again to create the new event-configuration file. Cause. This confirmation message is displayed after a new file name is entered and F14 is pressed (Profile screen). Effect. Information only Recovery. N/A 0345 (A) The event configuration file has been changed. Cause. The event configuration file has been changed. This is reported from the Profile screen when the configuration file field is modified. Effect. Information only Recovery.
Error Error Messages Effect. Information only Recovery. N/A 0349 (A) Alternate event acknowledged. Cause. You acknowledged an event by pressing F6. Effect. Information only Recovery. N/A 0350 (A) Alternate events acknowledged. Cause. You acknowledged an event by pressing F6. Effect. Information only Recovery. N/A 0351 Error occurred while reading the event terminal file: Cause. This file-system error occurred while ViewPoint was reading the event terminal file. Effect. Events may not be displayed.
Error Error Messages 0353 Error occurred while reading the event cache file: Cause. This is an internal error. Effect. Events may not be displayed. Recovery. Report this internal error to a Compaq representative, and be sure to supply the error numbers. 0354 Error occurred while writing to the event cache file: Cause. This is an internal error. Effect. Events may not be displayed. Recovery. Report this internal error to a Compaq representative, and be sure to supply the error numbers.
Error Error Messages 0357 Error occurred while reading the last events cache file: Cause. This file-system error occurred while ViewPoint was reading the last-events cache file. Effect. Last events may not be accurately displayed on your screen. Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0358 Error occurred while writing to the last events cache file: Cause.
Error Error Messages 0361 An event contains an incorrect timestamp. Cause. An event contains an incorrect timestamp in the header. The CONVERTTIMESTAMP error is returned. Effect. The event is not displayed. Recovery. None 0362 Error occurred while starting an event distributor: Cause. A NEWPROCESS or CREATEPROCESSNAME error occurred while attempting to start an event distributor. Effect. Events may not be displayed. Recovery. If this is a NEWPROCESS error, the error is returned.
Error Error Messages 0365 Error occurred while reading from an event distributor: Cause. A file-system error occurred when attempting to read from an event distributor. Effect. Events may not be displayed. Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0366 The ZVPT-EVNT-COLL server is out of distributor pool space. Cause. The ZVPT-EVNT-COLL server ran out of internal I/O pool space for communication with event distributors. Effect.
Error Error Messages 0369 Error occurred while writing to the terminal list file: Cause. A file-system error occurred when writing to the terminal list file. The error reported is shown as the second number in the message. Effect. Events may not be updated. Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0370 The TCP name associated with this terminal is incorrect. Cause. A TCP name cannot be found for this terminal. This is an internal error.
Error Error Messages 0373 Error occurred while reading the TCP for this terminal: Cause. A file-system error occurred while reading the TCP for this terminal. The error reported is shown as the second number in the message. Effect. ViewPoint screens may not be available. Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0374 An incorrect unsolicited message reply length was received: Cause. An invalid unsolicited message reply length was received.
Error Error Messages 0377 Error occurred while writing the marked event file: Cause. A file-system error occurred while writing the marked event file. The error reported is shown as the second number in the message. Effect. Events may not be marked correctly. Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0378 Can't delete the event. Cause. The event selected for deletion could not be deleted. Effect. The event is not deleted. Recovery.
Error Error Messages 0381 The events are different from those on the most recently displayed page. Cause. The events on this page of the event display are different from those on the most recently displayed page of the event screen, although the page number is the same. Effect. None Recovery. Specify a different log file or a valid date in the current log file. 0382 Please use a correct system name. Cause. The system name you entered is invalid. Effect. No event is displayed. Recovery.
Error Error Messages Recovery. Enter a valid process name or process ID. 0386 Please use a correct event text. Cause. The event text is not properly enclosed in quotation marks. Effect. No event is displayed. Recovery. Enter event text that is properly enclosed in quotation marks. See the description of the Event Configuration screen in Section 3, Definition of ViewPoint Screens for information on enclosing event text in quotation marks. 0387 Please use either selected or discarded. Cause.
Error Error Messages 0390 One log file name or 5 collector process names may be specified. Cause. A log file was specified along with one or more other log file or collector process names. Only one log file or as many as five collector process names can be specified. Effect. No events are displayed. Recovery. Enter as many as five collector process names or one log file name. 0391 The specified page number is higher than the last page number Cause.
Error Error Messages 0394 Please specify a value for the custom token. Cause. You selected a type (file, string, or number) for a custom token, but did not specify a value for it. Effect. No events are displayed. Recovery. Enter a value appropriate for the type selected. 0395 Please specify a correct file name for the custom token. Cause. An invalid file name was specified as the value for the custom token. Effect. No events are displayed. Recovery. Enter a valid file name for the custom token.
Error Error Messages Effect. No events are displayed. Recovery. Enter only one log file. 0399 Please use a correct collector or log file name. Cause. The name specified for a collector or log file is not valid. Effect. No events are displayed. Recovery. Specify a valid collector or log file name. 0400 Please enter a known event subject and press F4. Cause. The subject name entered on the option line does not match any of the eventmessage subjects. Effect. No events are displayed. Recovery.
Error Error Messages 0403 The third collector could not be accessed and was skipped. Cause. The third collector specified is inaccessible and cannot be used. Effect. No events from the third collector are displayed. Recovery. Specify a collector that is accessible. 0404 The fourth collector could not be accessed and was skipped. Cause. The fourth collector specified is inaccessible and cannot be used. Effect. No events from the fourth collector are displayed. Recovery.
Error Error Messages 0408 A error occurred while reading the EMS Log File: Cause. A file-system error occurred while reading the EMS log file. Effect. No events are displayed. Recovery. See the System Procedure Errors and Messages Manual for an explanation of file-system errors. 0409 A error occurred while starting an event distributor: Cause. A file error occurred during NEWPROCESS of an event distributor. The error returned is a file error pertaining to the program file, swap file, or process name.
Error Error Messages 0412 Select a single display option for each event type. Cause. More than one display option was selected on a single row of options under the Event View of the Event Configuration screen. Only one option may be selected on each row. Effect. No events are displayed. Recovery. Select only one display option on each row. 0413 The ZVPT-EVNT-COLL server is unable to allocated memory for cache. Cause.
Error Error Messages 0502 An internal error was returned from SSGET on the event. Cause. An SSGET on the event buffer resulted in an error. The error number is included in the message. Effect. Events may not be displayed. Recovery. See the SPI Programming Manual for an explanation of SPI procedure errors.
Error Error Messages ViewPoint Manual—426801-001 B -50
C ViewPoint Event Messages ViewPoint Event Logging ViewPoint reports errors detected during the display of screens on a terminal on the advice line of the terminal. However, ViewPoint reports errors detected by servers that run in an asynchronous mode to terminal operation as event messages through the Event Management Service (EMS). An example of such a server is the garbage collection server (ZVPT-GARB-COLL); this server runs at a scheduled time and performs database maintenance.
ZVPT-EVT-OPEN-ERROR (2) ViewPoint Event Messages Event Text Example VIEWPT \NCN.$ZVPT: ERROR Garbage-Collect File I/O Error on \NCN.$DATA.VPTDATA.EVNTTERM, Error 60 Cause One of the ViewPoint data files has been removed, damaged, or made inaccessible. The file-management error number and file name in the message indicate the specific problem. Effect If the garbage collection server encounters this error, the cleanup operation is stopped.
ZVPT-EVT-SSGET-ERROR (4) ViewPoint Event Messages Event Text Example VIEWPT \NCN.$ZVPT: ERROR Garbage-Collect File Open Error on \NCN.$DATA.VPTDATA.EVNTCACH, Error 11 Cause One of the ViewPoint data files has been removed, damaged, or made inaccessible. The file-management error number and file name in the message indicate the specific problem. Effect If the garbage collection server encounters this error, ViewPoint stops the cleanup operation.
ZVPT-EVT-TOO-LONG (5) ViewPoint Event Messages Event Text Example VIEWPT \NCN.$ZVPT: ERROR Garbage-Collect SSGET returned error -8 Cause The ViewPoint server got an error while getting a core token from an event in an event cache data file. This is an internal error indicating improperly formatted events. Effect If the garbage collection server encounters this error, ViewPoint stops the cleanup operation.
ZVPT-EVT-EDITREAD-ERROR (6) ViewPoint Event Messages Cause The event collection server received an event message that is too long to be recorded in an event cache (greater than 3900 bytes). The subsystem and event number of the large event are indicated by the event text. Effect This event replaces the too-large event in the ViewPoint event cache. It does not appear on the ViewPoint event displays; it is sent to the EMS collector. Also, it does not appear in event logs.
ZVPT-EVT-MEM-ERROR (7) ViewPoint Event Messages Effect The event collection server ends abnormally after generating this error. The default is set for the server to restart as many as five times; if the error persists, users are not able to enter ViewPoint or use the event screens. Recovery The problem indicated by the error number should be corrected. For syntax errors, refer to the rules specified in this manual.
ZVPT-EVT-MEM-ERROR (7) ViewPoint Event Messages error and the error number received are included in the message. The segment ID indicates which event display produced the error: 1024 => primary event display 1 to 1023 => an alternate event display Effect ALLOCATESEGMENT errors for alternate event displays cause the alternate event display to stop; the alternate event display must be reconfigured. All other errors cause the event collection server to end abnormally after generating this error.
ZVPT-EVT-MEM-ERROR (7) ViewPoint Event Messages ViewPoint Manual—426801-001 C- 8
D Sample Custom Status Server This appendix contains the complete source code of a custom status server. If you are a programmer who needs to write a custom server for your ViewPoint application, you can use this code as an example; or, if it suits your purpose, you can use this code as is or extend it. The documentation for the sample server includes instructions for adding status items.
Custom Server Code Sample Custom Status Server !* decimal positions which are assumed in the count. SCALE is a static !* property of an item which can not be changed by configuration. !* !* The MAXIMUM-VALUE field is optionally set to contain the maximum value !* a counter could attain. !* !* A timestamp is supplied with each sample. This timestamp is the !* four-word, Julian-date-based, microsecond resolution timestamp at the !* time of the sample (or as soon as possible after the sample).
Custom Server Code Sample Custom Status Server LITERAL LITERAL LITERAL LITERAL False = 0; Fname^Wsz = 12; Recv^User^Msg = 0; ! A user message was read on $RECEIVE. Recv^System^Msg^From^User = 1; ! A system message related to an ! opener was read from $RECEIVE. ! Typically an OPEN, CLOSE, SETMODE ! or CONTROL message. LITERAL Recv^End^Of^File = 2; ! The server should terminate. No ! message is returned.
Custom Server Code Sample Custom Status Server ?PAGE "STATUS COLLECTION SERVER GLOBAL VARIABLES AND DEFINITION" --------------------------------------------------------------------------------- This section allocate global variables and initialize them. --- The Defined^Items define will be initialized to the number of item -- types supported by this server. --- STATUS ITEMS implemented by this server are defined in the table -- Item^Array who contains an element for each implemented item.
Custom Server Code Sample Custom Status Server -------------------------------------------------------------------------------INT .
Custom Server Code Sample Custom Status Server "N", 0, 0, 100, "N", "N", "CV" ); ! ! ! ! ! ! reverse signify scale low threshold high threshold low/high threshold enabled type (busy-timer or counter-value) END; ?PAGE "SERVER^SHUTDOWN" PROC Server^Shutdown; BEGIN --------------------------------------------------------------------------------- This procedure is called right before the server stops. A server -- may do any relevant housecleaning here.
Custom Server Code Sample Custom Status Server Length := FNAMEEXPAND ( Item^Name.Z^Object^Name, Processname, Temp^Fname ); IF Length < 2 OR Length > 14 THEN RETURN ( Zerr^Stat^No^Such^Object ); Temp^Fname ':=' " " & Temp^Fname FOR 7; IF Processname[4] <> Temp^Fname FOR 8 THEN RETURN ( Zerr^Stat^No^Such^Object ); RETURN ( Z^All^Ok^Code ); END; ! Check^Process^Exist ?PAGE "CHECK^VALID^FILE^NAME" INT PROC Check^Valid^File^Name ( Request, Reply ); INT .
Custom Server Code Sample Custom Status Server -------------------------------------------------------------------------------FIXED Primary^Process^Time := 0F; FIXED Backup^Process^Time := 0F; INT .Processname [ 0:Fname^Wsz - 1 ]; ! internal form of name. INT .Temp^Fname [ 0:Fname^Wsz - 1 ]; ! temp file name. STRUCT .Item^Name ( Zvpt^Item^Name^Def ); INT Cpu^Pin; INT .PPD[0:8]; INT Length; Zerow(Reply); Return^Error := 0; Return^Error^Detail := 0; Item^Name ':=' Request.
Custom Server Code Sample Custom Status Server ?PAGE "SAMPLE^FILE^USAGE" INT PROC Sample^File^Usage ( Request, Reply ); INT .EXT Request ( Zvpt^Sample^Item^Request^Def ); ! Input INT .EXT Reply ( Zvpt^Sample^Item^Reply^Def ); ! Output BEGIN ------------------------------------------------------------------------------- Compute File Usage for this file ...... -----------------------------------------------------------------------------INT(32) Current^File^Size; INT(32) Maximum^File^Size; STRUCT .
Custom Server Code Sample Custom Status Server RETURN ( Z^All^Ok^Code ); END; ! Sample^Disk^Usage ?PAGE "SAMPLE^DISK^LARGEST^FREE" INT PROC Sample^Disk^Largest^Free ( Request, Reply ); INT .EXT Request ( Zvpt^Sample^Item^Request^Def ); ! Input INT .
Custom Server Code Sample Custom Status Server RETURN ( Z^All^Ok^Code ); END; ! Sample^Disk^Fragmentation ?PAGE "SCAN ITEM" INT PROC Scan^Item ( Request, Request^Len, Reply, Reply^Len ); INT .EXT Request ( Zvpt^Scan^Item^Request^Def ); ! Input INT .EXT Request^Len; ! Length of data in 'Request' INT .EXT Reply ( Zvpt^Scan^Item^Reply^Def ); ! Output INT .EXT Reply^Len; ! Length of data in 'Reply'.
Custom Server Code Sample Custom Status Server --- Check^Item implements the checking of a defined items. The defined item -- index is determined by a search of the list of items. The actual checking -- is then performed by a procedure Check^Valid^........ -------------------------------------------------------------------------------INT Index; ! Index of item in item^array.
Custom Server Code Sample Custom Status Server BEGIN --------------------------------------------------------------------------------- Perform the processing necessary to perform the request contained in -- 'RequestBuffer'. Formulate a reply in 'ReplyBuffer'. -------------------------------------------------------------------------------INT .EXT Request^Header ( Zvpt^Request^Header^Def ) = Request^Buffer; INT .EXT Reply^Header ( Zvpt^Reply^Header^Def ) = Reply^Buffer; INT .
Custom Server Code Sample Custom Status Server -------------------------------------------------------------------------------INT Error := 0; LITERAL System^Message = 6; CALL READUPDATE ( Rcv^Fnum, Buffer, Zvpt^Ipc^Len, Actual^Length ); IF > THEN BEGIN CALL Fileinfo ( Rcv^Fnum, Error ); IF Error = System^Message THEN BEGIN CASE $ABS ( Buffer[0] ) - 30 OF BEGIN !0! Num^Requesters := Num^Requesters + 1; ! -30 Open Msg from Requester !1! Num^Requesters := Num^Requesters - 1; ! -31 Close Msg from Requester OT
Custom Server Code Sample Custom Status Server BEGIN --------------------------------------------------------------------------------- This version procedure is very nice, since we can list it using the VPROC -- tool and then know all the time the server version we are dealing with.
Custom Server Code Sample Custom Status Server ViewPoint Manual—426801-001 D -16
E Supplemental Information for D-Series Systems This appendix tells you how to use ViewPoint on a D-series system. It consists of two major subsections: The first is a brief overview of D-series operating system features applicable to ViewPoint; the second is a description of the specific D-series ViewPoint enhancements.
Supplemental Information for D-Series Systems Communication Between Low-PIN and High-PIN Processes Communication Between Low-PIN and High-PIN Processes A high-PIN process on a D-series system cannot communicate with a process on a C-series system without a low-PIN, D-series process, as an intermediate process. However, low-PIN processes on a D-series system can communicate directly with processes on a C-series system.
Supplemental Information for D-Series Systems ViewPoint Enhancements ViewPoint Enhancements This section describes specific D-series enhancements to ViewPoint.
Supplemental Information for D-Series Systems DP Command EXTSWAP Option If HIGHPIN ON is specified, the process runs at high PIN if it has been converted to run at high PIN. However, if the process has not been converted to run at high PIN, it runs at low PIN. The HIGHPIN option default is ON. Whether a process is designed to run at high or low PIN depends upon the HIGHPIN object-file attribute.
Supplemental Information for D-Series Systems Extraneous Parts of Filter Following are the four portions of the filter that have changed: Test for Matching System Name -- Test for matching system name (if provided). if ( not tokenpresent(zvpt^fltr^systemname) or zvpt^fltr^systemname = decompose(ssid(zems^val^ssid, zems^tkn^xsenderid^pd),system name) ) and Test for Matching CPU -- Test for matching cpu (if provided).
Supplemental Information for D-Series Systems Extraneous Parts of Filter END; ] [#def zspi_ddl_crtpid STRUCT BEGIN BYTE Z_PROCNAME (0:5); BYTE Z_CPU; BYTE Z_PIN; END; ] If you have customized filters, you might have to modify them. For more information, see the EMS Manual section describing D-series features. Figure E-2. D-Series Default Alternate-Events Filter (page 1 of 4) ----------------------------------------------------------- ViewPoint default alternate event filter.
Supplemental Information for D-Series Systems Extraneous Parts of Filter Figure E-2. D-Series Default Alternate-Events Filter (page 2 of 4) ------------------------------------------------------------ We need to #def our own replica of an ssid structure. -- This is necessary because the one in ZSPITACL does not -- have the fields broken out; instead that structure just -- consists of a single field of data type ssid. We need -- to refer to the fields separately in this filter.
Supplemental Information for D-Series Systems Extraneous Parts of Filter Figure E-2. D-Series Default Alternate-Events Filter (page 3 of 4) -- Test for matching event number (if provided). ( not tokenpresent(zvpt^fltr^eventnumber) or zvpt^fltr^eventnumber = ssid(zems^val^ssid,zems^tkn^eventnumber) ) and -- Test for matching cpu (if provided). ( not tokenpresent(zvpt^fltr^cpu) or zvpt^fltr^cpu = ssid(zems^val^ssid, zems^tkn^xsenderid).zems^ddl^xsenderid:zcpu ) and -- Test for matching pin (if provided).
Supplemental Information for D-Series Systems Extraneous Parts of Filter Figure E-2. D-Series Default Alternate-Events Filter (page 4 of 4) ------------------------------------------------------------ Events which have passed the conditions above will be -- processed using the ViewPoint default filtering rules: -- 1) Events with a suppress^display token value equal to -true fail unless the event is an action -completion event -- then it will pass with a pass -code value of 3.
Supplemental Information for D-Series Systems ViewPoint Manual—426801-001 E -10 Extraneous Parts of Filter
Glossary Introduction This glossary defines technical terms used in this manual. Some of these terms are also defined in the SPI Programming Manual. abend (abnormal end). (1) An abnormal end of a task or process. (2) An error condition that can result in the termination of a program. action event. An event for which the generating subsystem requires a response from the operator, such as mounting a tape.
clipboard file Glossary clipboard file. An EDIT file to which you can copy selected lines from a ViewPoint display screen. You, or a management application program, can then access the selected lines of text in that file at some later time. Copying to the clipboard file is called clipping. command. A demand for action by or information from a subsystem, or the operation demanded by an operator or application. A command is typically conveyed as an interprocess message from an application to a subsystem.
DSM Glossary application as the primary-events distributor, the alternate-events distributor, and the last-events distributor. DSM. See Distributed Systems Management. event. A significant change in some condition in the system or network. Events can be operational errors, notifications of limits exceeded, requests for action needed, and so on. Events are reported to ViewPoint as event messages to be displayed on a Primary Events, Alternate Events, or Last Events screen. event cache.
filter Glossary supply. The ViewPoint application calls the Extras program unit (which must have the name EXTRAS) when the user presses the Extras function key. filter. A file that contains a list of criteria against which incoming event messages can be compared so as to pass a given message (if it meets all criteria) or not pass it (if it fails one or more criteria). filter object file. A file containing the compiled filter code that determines which events are displayed on an events screen.
Network Status Summary screen Glossary it is possible to have more than one such process in a network, there can likewise be more than one NCN in a network of Compaq systems. Network Status Summary screen. The screen on which ViewPoint displays information about the status of objects in a network. object. In SPI, an entity subject to independent reference and control by a subsystem: for example, the disk file $DATA or the data-communications line $X2502.
programmed operator Glossary format, a set of message formats, or a set of procedures (such as the SPI procedures) to build and decode messages; definitions of message elements (commands, data types, objects, parameters, response data, errors, and so on); rules for communication between the requester and the server; and software to receive and respond to messages defined for the interface. programmed operator.
Status Configuration screen Glossary of status configuration files; operators specify on the Profile screen which file ViewPoint uses to display status at their terminals. Status Configuration screen. The ViewPoint screen on which the operator can specify configuration information to control the display of status items on the Network Status Summary screen. status item. A measurable condition in a system or network that is displayed on one line of a Network Status Summary display screen.
token code Glossary and retrieve them from the buffer with the SSGET procedure. A token has two parts: an identifying code—a token code or token map—and a value. For control and inquiry, a token normally represents a parameter to a command, an item of information in a response, or control information for SPI or the subsystem. For event management, a token normally represents an item of information about an event, or control information for EMS or the subsystem. token code.
Index A Accessing ViewPoint 2-2 Action event filters for 6-2 highlighting of 3-10 restricted view 2-9 Action field Events screen 3-9 Action token 5-22 Action-completion event and default filters 6-3 ACTION-TAGS assign A-1 ACTION^NEEDED token and default filters 6-3 Adding status items 6-27, 6-40 Additional information, D-series E-1 Advisory messages B-1 Advisory text adding with ENABLE application 6-13 for events 6-11, 6-15 After field Event Configuration screen 3-17 Alternate configuration 2-13 Alternate E
C Index C Cache alternate events 2-12, 5-6, 5-21, 5-29 display 5-6 primary events 5-6, 5-29, 5-30 Changing configuration events 2-15 status 2-14 CHECK-ITEM command 6-33, 6-36 ViewPoint status server 6-30 Clip function key 3-3, 5-33 Clipboard file 2-4, 3-3, 3-9, 5-4 example TACL routine using 6-17 name 6-21 See also ZZVPCLIP 2-4 Clipping message 2-4 Cold start 7-7 Collection server last events 5-32 Collector field Events screen 3-9 Collector or Log File field 2-11 Event Configuration screen 3-16 Collectors
C (continued) Index C (continued) CUSTOM-DETAIL assign A-1 D Data subvolume 5-4, 5-31 Database event-detail 5-31, 5-33 last events 5-32 DCT See Destination control table DDL source code for ViewPoint application 6-1 DEBUG key word 4-3 DECOMPOSE function, EMS E-2, E-4 Default filters for ViewPoint 6-2 DEFAULTS Define Process commands list of 4-2 concept of 5-9 directory 4-2, 4-16 example of TACL macros 6-16 facility 6-16 library overview 1-8 using 2-19 Define Process command definition 4-2 D-series additi
D (continued) Index D (continued) discarding input-output 4-16 Display cache 5-6 Display event text 2-9 Display field Events screen 3-8 Display type 5-12, 6-27 Display Type field Status Item Configuration screen 3-34 Distributed Name Service (DNS) startup 7-8 Distributor alternate events 5-24, 5-29 events 5-23 forwarding 5-6, 5-26 last events 5-32 primary events 5-24 DISTRIBUTOR Assign A-2 DNS startup 7-8 Documentation, additional D-series E-1 DP command 4-2 D-series additions E-3/E-4 using 2-19 Dynamic p
E (continued) Index E (continued) Event Detail screen (continued) description 3-22 D-series messages, new E-3 ENABLE application for adding text 6-13 Event Text field 3-22 introduction 1-5 Origin Header field 3-22 Page field 3-22 Recommended Action field 3-23 using 2-9 viewing multiple events 3-23 Event distributor 5-23 Event filter dynamic parameters 6-2 Event log 5-18 Event log file 5-6 Event Management Service retrieving event messages 6-2 Event message buffer 5-22 detail 2-10 display full text 2-9 gen
E (continued) Index E (continued) Event-message filter 5-23 Event-message text 3-26 EVENT-NOTIFY assign A-2 EVENT-TERM assign A-2 EVENT-TERM-LIST assign A-2 EVNTDFLT file 2-13, 7-8, 7-14 EVNTLECA file A-2 EVNTLESB file A-3 EVNTMRKD file 6-23, A-2 EVNTTERM file A-2 EVNTTLST file A-2 Example of custom server D-1 of filter for alternate events 6-5 of TACL macros using Define Process 6-16 of TACL routine using ViewPoint 6-17 Example configurationof status server 5-17 EXISTENCE key word, _PCHECK 4-9 Exit from
F (continued) Index F (continued) Filters D-series conversion E-2 FKEY key word 4-3 _PCHECK 4-9 FLTRALT default alternate-filter source code 6-5 FLTRALT file A-1 FLTRDFLT source code for 6-4 FLTRDFLT file 5-31 FLTRLAST source code for 6-4 FLTRLAST file 5-31, A-3 Forwarding distributor 5-6, 5-26 startup 7-8 Freeze events 3-9, 5-19 Freeze function key 3-3 Freeze screen 2-4 Freeze status 3-28, 5-12 Frozen field Events screen 3-9 Network Status Summary screen 3-28 FROZEN message 2-4, 3-9, 3-28 Function key in
I (continued) Index I (continued) Internal function of F1 key 5-6 Internal function of SF16 5-7 INV key word 4-19 ISV Installation Subvolume 7-1 Item description status 6-35 Item Description field Network Status Summary screen 3-29 Status Item Configuration screen 3-34 Item Selection field Network Status Summary screen 3-29 J JOBID key word 4-4 L Last events collection server 5-32 database 5-32 display 5-32 distributor 5-32 filter 5-32 Last Events function key 3-2 Last Events screen 2-12 description 3-2
M (continued) Index M (continued) Multiple Collectors Defining for EVNT-COLL server A-3 Multiple operators using TACL 5-7 N NAME key word 4-4 NCN (network control node) 5-2, 5-26 Network control node 5-2, 5-14, 5-26 Network status monitoring 1-3 Network Status Summary screen 6-27 description 3-28 Frozen field 3-28 introduction 1-3 Item Description field 3-29 Item Selection field 3-29 Page field 3-28 Page selection 3-28 Percentage Graph field 3-29 select page 2-4 Status field 3-28 Total field 3-29 Value f
P Index P Page size event 3-17 status 5-11 Pages field Event Configuration screen 3-17 Parallel processing with Define Process 6-16 PARAM adding to PATHDEFS file 7-9 Parameter BELLRESET A-5 BELLVOLUME A-5 IGNOREALTEVENT A-6 IGNORELASTEVENT A-7 IGNOREPRIEVENT A-7 LAST-EVENT-CACHESIZE A-7 LAST-EVENT-MAX-HOURS A-7 REPOSITION A-9 SAMPLE-AGE-MAX-MINUTES A-9 STOPDELAY A-9 SUPPRESSUNANSWERED A-9 Parameters for custom filter 3-20 Parameters, server A-4 Passthrough mode 4-3, 4-19 PATHCOM ALTER command for changing
Q Index P (continued) Q Primary/alternate event selection 3-8 Print function key 3-3, 5-33 Printing status information 2-4 Printing the screen 2-5, 3-3 Priority of defined process 4-5 Probable Cause display 6-11 event detail 2-10 Process descriptor E-2 Process file name E-2 Process ID synthetic E-1 Process name, D-series considerations Event Configuration Screen E-3 extracting from process descriptor E-2, E-4, E-5 PROCESSID key word, _PCHECK 4-10 Process-pair directory 4-4 Profile function key 3-3 Profi
R (continued) Index R (continued) Run ZVIEWPOINT running TACL-less ViewPoint 7-13 RUNNING key word, _PCHECK 4-10 Running ViewPoint execution errors 7-11 using a color monitor 7-11 with TACL 7-11 without TACL 7-13 RUNOPTS key word, _PCHECK 4-10 S SAFEGUARD 7-16 SAMPLE-AGE-MAX-MINUTES parameter A-9 SAMPLE-ITEM command 6-33, 6-36 ViewPoint status server 6-30 SAMPLE-LIST command 6-33 description of 6-37 ViewPoint status server 6-30 SAVEABEND key word 4-3 Scale factor for ViewPoint status displays 6-36 Scan f
S (continued) Index S (continued) Starting ViewPoint 7-6 considerations 7-7 starting ViewPoint 2-2 STARTUP key word _PCHECK 4-10 STATDFLT file 2-13, 7-8 Status changing configuration 2-14 object 5-12 reporting components of 5-12 concept of 5-11 example configuration 5-17 in networks 5-14 managed by TCP 5-6 to multiple operators 5-15 Status collection server 5-6, 5-13 Status collection servers See Status servers Status configuration file 3-30, 5-11, 6-29 name 6-22 selection 3-32 Status Configuration File f
S (continued) Index S (continued) T Status update 5-11, 5-12, 5-13 immediate 3-30 STATUSV key word, _PCHECK 4-10 STOPDELAY parameter A-9 Stopping a defined process 2-20, 4-15 Stopping ViewPoint 7-7 Subject for events 3-27, 3-30, 3-32, 3-37 name length 3-27 Subject field Last Events screen 3-25 Subsystem ID field Event Configuration screen, page 2 3-20 Subvolume data 5-4, 5-31 program 5-4 Subvolume, current for ViewPoint software 6-22 SUPPRESSUNANSWERED parameter A-9 SUPPRESS^DISPLAY token and default fi
T (continued) Index T (continued) Threshold of status item 5-12 status displays 6-27 status value 2-4 changing 2-6 Threshold fields, status 3-35 Thresholds for ViewPoint status displays 6-36 Timestamp status 6-37 TMFSERVE 6-28 TMFSERVE file A-4 TMF-SERVER assign A-4 Token action 5-22 emphasis 5-22 Tokens in event message 5-22 Tokens, ViewPoint event C-1 TOSS command definition 4-16 Total field Network Status Summary screen 3-29 TTY-FDX 3-1, 3-6 Twenty-fifth line importance of 3-1 twenty-fifth line 3-14 U
V (continued) Index V (continued) ViewPoint startup 7-6 considerations for 7-7 ViewPoint status server CHECK-ITEM command 6-30 GET-VERSION command 6-30 NEXT-ITEM command 6-30 SAMPLE-ITEM command 6-30 SAMPLE-LIST command 6-30 SCAN-ITEM command 6-30 VIEWPT command 2-2 to run ViewPoint 7-11 Volume and subvolume, current for ViewPoint software 6-22 VPTCSTM file 7-16 W WAIT command definition 4-17 WAIT key word 4-19 _PCHECK 4-10 Wait mode 4-5 WAITREADY command definition 4-18 X XVPT-EXTRAS program unit TACL-
Z (continued) Index Z (continued) Z-HIGH-THRESHOLD 6-36 Z-IPC-RETN-CODE 6-31, 6-33 for SAMPLE-LIST command 6-37 Z-ITEM-DESCRIPTION 6-35 Z-ITEM-INDEX 6-39 Z-ITEM-NAME 6-35 Z-LAST-SCREEN 6-22 Z-LOGICAL-TERM 6-24 Z-LOW-ENABLED 6-36 Z-LOW-THRESHOLD 6-36 Z-OPTION-LINE 6-23 Z-PATHMON-NAME 6-21 Z-PW-REPLY-CODE 6-31 Z-REQUEST-CODE 6-31, 6-33 Z-REVERSE-SIGNIFY 6-36 Z-SCALE 6-36 Z-STATUS-CONFIG-FILENAME 6-22 Z-SYSTEM-NAME 6-21 Z-USER-ID 6-22 Z-USE-MAXIMUM 6-36 Z-VALUE-FOR-100 6-36 Z-VALUE-TYPE 6-36 Z-VERSION-CODE 6
Special Characters Index ViewPoint Manual—426801-001 Index -18
