ASAP

1. For DSM/SCM, use the IPSETUP.exe program to upload the files from the CD / PC to the NonStop server. Follow the screens on the Wizard and provide the necessary information as prompted. Once the IPSETUP program completes ensure that the files listed below have been transferred in the correct format and the file codes are correct.
2. Following are the steps needed to install Web ViewPoint ASAP:

The Web ViewPoint ASAP consists of the following files:

• TXT File containing product and basic installation information.
• SETWASAP Configuration and installation of Web ViewPoint on NonStop.
• WASAPPAK Web ViewPoint ASAP PAK file containing all the required files
• INSWASAP Program to add Web ViewPoint ASAP plug-in into Web ViewPoint.                        

• MAKEDCNF Script file used to create DISPCONF file
• SPMON Program handling state propagation management.
• TERMMAN Program to perform terminal management and store state propagation

Instructions:

1. FTP the following files to your Web ViewPoint subvolume.

(Note: These files need to be transferred to the WVP $volume.subvolume to which you want to integrate this plugin)

The following files have to be transferred in ‘BINARY’ Mode

• SETWASAP
• WASAPPAK

1. Run the setup file ‘SETWASAP’ (read the following instructions first)

 

• It prompts user to specify the parameters you want to use for Web ViewPoint ASAP

 

 

——————————————–         Web ViewPoint ASAP Plug-in Installation Menu   ——————————————–           1. Terminal Manager Process Name           : $TM         2. Environments Setup Menu         3. Install         4. Exit           Please select an option (select 1 or 2 to change values):

 

 

1. Terminal Manager Process Name: This is the process name of the Terminal Manager Program (TERMMAN). This process will be started alongside Web ViewPoint ASAP and will be a part of SATRTWVP. It will be the central process for WASAP functioning, starting up the State Propagation Monitors and SSGs and propagating data from these to the web browser.

By default, $TM is set as the Terminal Manager process name, to change the default parameter follow the below step:

• Input number 1 and enter, input desired Terminal Manager Process name and enter.

2. Environment Setup Menu: This includes the ASAP environment location ($volume.subvolume) identifying the database to collect information from and a unique name given to this environment. Web ViewPoint ASAP allows you to enter upto 20 environments.

• Input number 2 and enter, it prompts user to setup environments as shown below

 

—————————————————         Web ViewPoint ASAP Plug-in: Add/Delete Environments   —————————————————           1. Add Environment         2. Delete Environment         3. Exit Environment Setup          Please Enter Option:(1-3): 1

 

• Input number 1 and enter, it prompts user to enter ASAP Environment location on your Nonstop($vol.subvol)

 

—————————————————         Web ViewPoint ASAP Plug-in: Add/Delete Environments         —————————————————           1. Add Environment         2. Delete Environment         3. Exit Environment Setup      Please enter Environment ($vol.subvol) or exit to go to previous menu:                     $SYSTEM.ZASAP

 

• It now prompts to enter the name of the Environment, enter your desired name

—————————————————         Web ViewPoint ASAP Plug-in: Add/Delete Environments         —————————————————           1. Add Environment         2. Delete Environment         3. Exit Environment Setup      Name this Environment (Upto 20 alphabets/numbers only): WASAPENV

               

• Input number 3 and enter, this exits from the Environment setup prompt and takes you back to the main setup screen

—————————————————         Web ViewPoint ASAP Plug-in: Add/Delete Environments         —————————————————           1. Add Environment         2. Delete Environment         3. Exit Environment Setup          Please Enter Option:(1-3): 3

 

• In the main setup screen, input number 3 and enter, to install the plugin

——————————————–         Web ViewPoint ASAP Plug-in Installation Menu   ——————————————–           1. Terminal Manager Process Name           : $TM         2. Environments Setup Menu         3. Install         4. Exit           Please select an option (select 1 or 2 to change values): 3

 

• It displays all the values you configured in the previous step for your confirmation

Here are the values you set:                 Process Name : $TM                 Environment 1 (wasapenv) : $system.zasap           Confirm Submission? (y or n):Y

 

• Input Y to confirm the submission and to complete the install process.

2.3 Uninstall WASAP

Method 1: WASAP can be uninstalled by running UISTALL from the installation sub volume.

It removes WASAP from Web ViewPoint by updating the STARTWVP and STOPWVP files.

The following steps need to be followed:

• Stop Web ViewPoint, if already running
  • Set your working volume to $system.zwvps (or to $volume.sub volume where you have installed Web ViewPoint)
  • Issue ‘Obey STOPWVP’
• Run the Uninstallation program, UINSTALL
  • Issue ‘RUN UISTALL’

Figure showing the uninstall of Web ViewPoint ASAP.

$DATA01.WVPABU> RUN UISTALL           Confirm WASAP Uninstall? (y or n): Y           WASAP Uninstall Complete.

 

• Input Y to confirm the submission and to complete the uninstall process.

 

Method 1: WASAP can be uninstalled by running UISTALL from the installation sub volume.

It removes WASAP from Web ViewPoint by updating the STARTWVP and STOPWVP files.

When Web ViewPoint ASAP is first run through the Browser, it tries to activate itself by contacting the activation website over the internet. If you are a new user you will be prompted to enter your registration details. If you have an active Internet connection the activation will happen automatically, if not then the system will provide you with details and handle the registration and activation via email.

During activation, an activation key is written to the license repository (i.e. ULICENSE) that is identified by the LICENSE-FILE Assign. Once complete, Web ViewPoint ASAP will fully function from Web Viewpoint.

Following topics are presented:

• Locating and starting WASAP in Web ViewPoint
• Object Tree
• Entity Table
• Viewing Object History
• Viewing Objectives
• Refreshing WASAP data
• Switching Environments

Locating and starting WASAP in Web ViewPoint          

WASAP will show up as an option located within the Performance menu item. To access WASAP, move the cursor over the Performance menu present on the left panel.  This displays the available menu features.  Click on the displayed text of WASAP to select it.  Web ViewPoint activates that feature, and opens WASAP in a new Window.  This keeps the current function and display intact, while delivering WASAP on a separate Window.

When WASAP starts for the first time, it loads the first environment in the list of environments (if there is more than one environment). Subsequently, WASAP remembers the environment last opened and opens that environment when started up the next time. The environment name is displayed in the top left side of the screen.

Screen showing the WASAP started with environment named QA

Object Tree

WASAP has two main screen areas: the one on the left displaying the object tree and the right hand frame displaying tabular data for a selected Entity belonging to the selected System. When an environment first comes up, all systems for which data is being collected, show up in a tree in the left hand frame. Each system has alongside it, one of the following icons indicating the highest state among the objects within that node:

Expanding a System/node shows all the Entities within that system. These Entities are marked with icons similar to the above ones, representing their respective states.

Object Tree with one of the systems expanded to show its Entities

Entity Table

Each of the Entities within System in the object tree is a hyperlink, clicking on which displays the most recent data for that Entity-System combination in a table in the right hand frame. Since WASAP looks at the Entity Definition Language (EDL) of the selected environment to get the list of Entities and their Attributes, only those Attributes marked YES on GRID are shown in the table. The first column is the Entity specification.  The Node Name is typically listed next.  Then Status, as described above, is indicated with an icon and/or a written description. The remaining columns are attributes which are specific to each Entity.  The display order of other attributes is determined by the objectives (rank) defined for that particular entity, such that the ranked attributes (if any) appear before the unranked attributes.                    

One cell from each row of data has a state icon to represent the highest state amongst all State Pair Attributes of that row. The tabular data is bi-directionally sortable on any of the columns.

WASAP displaying data for Entity CPU on System \NSCLOUD

Viewing Object History

WASAP allows you to view the Object History for a selected object. You can view the last 5, 10, 15 or 20 collections for the selected object. To view historical data for a row of data, you need to click anywhere on the row. This brings up a popup menu giving the option of selecting between 5, 10, 15 and 20 collections. On selecting one of these options, a new window displays the history for that row in tabular format.

Object History screen showing last 10 collections for CPU 03 on System \NSCLOUD

Viewing Objectives

ASAP allows the user to set objectives and thresholds for each Entity. Using WASAP you can see what these objectives are. Whenever an Entity is selected, an Objectives Info  ⓘ icon shows up in the toolbar of the WASAP screen. Clicking on this icon opens a new window listing the objectives for the current Entity if any.

Refreshing WASAP data

WASAP fetches data from the ASAP database. The ASAP database gets continuously refreshed with the latest data, the frequency of refresh dependent on the Rate value specified in the EDL. WASAP fetches this value and automatically refreshes the tree and table data as soon as new data comes in. The time to the next refresh in seconds is shown at the bottom of the WASAP screen. You can however choose to stop this periodic refresh by clicking on the pause icon on the toolbar.  The icon then changes to: Play icon. You may click on this icon to resume the automatic refresh operation.

Switching Environments

At the time of installing WASAP, the user has the option of specifying upto 20 ASAP environments to monitor. When started from the menu, WASAP loads the default or the last selected environment. You can switch between environments by clicking on the Change Environment dropdown on the top left corner of the screen. Clicking this list shows a dropdown with all available environments. On selecting the environment desired, the new environment gets loaded into the same page, in place of the old one.

Following are the list of assigns and params used by objects TERMMAN and WASAP:

• ASSIGN LICENSE-FILE, <filename>                               [WASAP]

This provides Web ViewPoint ASAP with the location of license file that contains the activation key. By default, the installation program makes this assign point to the ULICENSE file present in the Web ViewPoint subvolume (the ULICENSE file present in the Web ViewPoint subvolume serves as a key-store and can store activation keys of Web ViewPoint Shell as well as Web ViewPoint ASAP). This assign is mandatory and is automatically set during plugin installation. This goes in the WVPCONF file of Web ViewPoint.

• PARAM WASAPENV-<Environment Name> <$Volume.Subvolume> [TERMMAN]

This is a mandatory param set by the installation program. There can be one or more of these depending on the number of environments there are. This goes in the STARTWVP file of Web ViewPoint, t is a runtime requirement for TERMMAN and shall not be removed from STARTWVP.

A. Support

Support for Web ViewPoint is available through HPE’s 24-hour Global Mission Critical Support Centers (GNSC) throughout the world.

For general questions on functionality you can email us at WebViewPoint@hpe.com.

For licensing questions please contact license manager at License.Manager@hpe.com

B. Event Messages

This section lists all EMS Events that can be generated specifically from the WASAP application conditions and processing.

WASAP EMS SSID: TANDEM.257 or TANDEM. 1500 (Depending on the SSID configured in UMPCONF file of Web ViewPoint)

 

WASAP Processing Errors – EMS Messages

WVPASAP 102

<Program Name> <Function Name>: Process/Backup Creation Error <Error Number>,<Error Detail>

Relating to one of the following functions or activities: a) Creating and verifying creation of a new process.  b) Primary process attempting to create a backup upon first coming up.

Cause: a) Occurs on the “PROCESS_CREATE_” Guardian procedure call if the process creation failed. The process creation error and the detail are part of the event. b) Occurs on the “__ns_start_backup” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. Process create failure could occur due to various reasons, for e.g. invalid process handle (Error 2).

Effect: a) The daily database updates or the one-time loads will not be completed. b) The primary process will be unable to create a backup process and the nonstop operation of WASAP will not take effect.

Recovery: For Primary Process, the error type and sub type can be located in the “Guardian Procedure Calls” reference manual. This manual will describe why the PROCESS_CREATE_ call failed. For backup process, recovery will depend on the specific Guardian error returned. For e.g. Error 2 can be recovered from by providing a valid process handle.

WVPASAP 103

<Program Name> <Function Name>: Decompose Error: <Error Number>

Relating to function or activity: Primary or backup TERMMAN, SPMON, WASAP or SHUTWAS process trying to retrieve process information from the process handle.

Cause: Occurs on the “PROCESSHANDLE_DECOMPOSE_” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, for e.g. non-existent process (Error 14).

Effect: The primary TERMMAN, SPMON, WASAP or SHUTWAS process will not be able to communicate with the backup and vice versa. This will prevent the backup process to take over as the primary in case the primary process goes down. The primary will not be aware if the backup goes down and the nonstop operation of WASAP will not take effect.

Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 14 can be recovered from by restarting the Web ViewPoint (and hence WASAP) processes.

WVPASAP 104

<Program Name> <Function Name>: PROCESS_GETINFO_ error: <Error Number>

Relating to function or activity: Creating and verifying creation of a new process or accessing information about an existing process.

Cause: Occurs on the “PROCESS_GETINFO_” Guardian procedure call that is triggered after process creation. The Guardian error number indicating what the cause was is part of the event text. This error condition could occur due to various reasons, for e.g. Error 1 for a file system error.

Effect: The daily database updates or the one-time loads will not be completed.

Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 5 means the processor where the process was to be run is unavailable. To correct this, run the process on another processor.

WVPASAP 108

<Program Name> <Function Name>: TermManager Process Name  Error <Error Number>,<Error Detail>

Relating to function or activity: WASAP Teminal Manager process name could not be found.

Cause: Wrong or Invalid name being specified to stop the Terminal Manager process during shutdown of WASAP.

Effect: The process will not be stopped.

Recovery: Specify a correct or valid process name and then retry the operation. Also make sure that the process name which you specify does not already exist.

WVPASAP 110

<Program Name> <Function Name>: Pair Info Error <Error Number>

Relating to function or activity: WASAP processes attempting to communicate with the primary.

Cause: Occurs on the “PROCESS_GETPAIRINFO_” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, for e.g. non-existent process (Error 9).

Effect: The backup process will not be able to communicate with the primary. This will prevent the backup process to take over as the primary in case the primary process goes down.

Recovery: Recovery will depend on the specific Guardian error returned. E.g. Error 9 can be recovered from by restarting the Web ViewPoint (and hence WASAP) processes.

WVPASAP 113

<Program Name> <Function Name>: WRITEREADX error <Filename>:<Error Number>

Relating to function or activity: Unable to write to a given process.

Cause: The Guardian Procedure call WRITEREADX failed to complete communication with the process. The process may not be running or an invalid buffer or count is specified in the WRITEREADX Guardian Call. Please refer to the Guardian Procedure Manual for a better description of the values returned by WRITEX.

Effect: The WRITEREADX Operation on the opened process fails. If the process is not running, then subsequent calls to the process will fail too.

Recovery:  If the process is not running, then make sure it is running again before trying the operation again.

WVPASAP 114

<Program Name> <Function Name>: READUPDATEX error <Filename>:<Error Number>

Relating to function or activity: Reading from some process and replying to that process failed

Cause: The process with which communication was being attempted has expired. The EMS Event indicates the error value returned by the Guardian Procedure call READUPDATEX

Effect: Any future I/O Operations with the deceased process will fail.

Recovery:  The parent process should restart the child process that died prematurely.

WVPASAP 115

<Program Name> <Function Name>: REPLYX Error <Error Number>

Relating to function or activity: TERMMAN process replying to a message it received from the SEEVIEW process.

Cause: Occurs on the “REPLYX” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text.

Effect: The communication with the SEVIEW process will not complete, the SEEVIEW process will be terminated and al files opened by it will be closed.

Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 14 (device non-existent) can be recovered from by ensuring that the processes are up and running.            

WVPASAP 130

<Program Name> <Function Name>: Error opening $RECEIVE <Filename>:<Error Number>

Relating to function or activity Unable to open $RECEIVE for communication.

Cause: FILE_OPEN on $RECEIVE failed. This may be because of too many opens already on $RECEIVE being specified.

Effect: The process will not be able to read from its $RECEIVE.

Recovery:  Make sure that the maximum opens on $RECEIVE has not reached and also make sure that every open on $RECEIVE is followed up with a corresponding FILE_CLOSE_ Guardian Procedure call.           

WVPASAP 143

<Program Name> <Function Name>: Error opening File <Filename>:<Error Number>

Relating to function or activity: The File could not be opened to perform I/O Operation.

Cause: The file could not be opened. The EMS Event indicates the error value returned by the Guardian Procedure call FILE_OPEN_.

Effect: Any future I/O Operations on the file will fail.

Recovery:  Make sure that the file exists before being opened. If the max numbers of File Opens have been reached, then close all open file handles and then try again.

WVPASAP 144

<Program Name> <Function Name>: Error Reading file <Filename>:<Error Number>

Relating to function or activity: Reading from a file to access contents.

Cause: Occurs on the “READX” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This error condition could occur due to various reasons, for e.g. the operation timed out (Error 40).

Effect: If the error occurs on the SA Host program, the daily database updates or the one-time loads will not be completed. If the error occurs on the UI, the screen or data requested will not be displayed.

Recovery: Recovery will depend on the specific Guardian error returned. For e.g. Error 11 can be recovered from by ensuring the file exists in its proper location or that the program is pointing to the right volume. This error on READX means the file was moved or purged after the open but before the read.

WVPASAP 146

<Program Name> <Function Name>: Error Setting Key for file <Filename>:<Error>

Relating to function or activity: Positioning the file pointer within a file to access contents.

Cause: Occurs on the “FILE_SETKEY_” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, for e.g. non-existent record (Error 11).

Effect: The File will be closed and the control will return back to the calling function.

Recovery: Make sure that the key is set for the proper length and with valid values. Also make sure that the file is opened before setting the key in the file.

WVPASAP 147

<Program Name> <Function Name>: Error Writing file <Filename>:<Error Number>

Relating to function or activity: Writing to a file to access contents.

Cause: Occurs on the “WRITEX” Guardian procedure call. The Guardian error number indicating what the cause was is part of the event text. This could occur due to various reasons, for e.g. no write permissions (Error 48).

Effect: The record will not be written to the file.

Recovery: Make sure that the file exists and the correct buffer and count is specified in the WRITEX procedure call before issuing the WRITE. Recovery will depend on the specific Guardian error returned. For e.g. Error 48 can be recovered from by assigning proper permissions to the file or the program trying to write to the file.

WVPASAP 550

TM No Environments Found (or PARAM WASAPENV missing)

Relating to function or activity: Environment (name) specified in STARTWVP file.

Cause:  The STARTWVP file in WVP sub volume does not have even one environment defined as “PARAM WASAPENV-<ENVNAME>   <$VOL.SUBVOL>“

Effect: The terminal manager process – TERMMAN will shut down and WASAP will not be accessible.

Recovery:  Edit the STARTWVP file to include at least one environment in the above specified format.

WVPASAP 551

TM Primary: Exiting, Limit number of environments to 20.

Relating to function or activity: Number of environments specified in STARTWVP file.

Cause:  The total number of environments configured in the STARTWVP file on the WVP sub volume is more than the allowed maximum (20).

Effect: The terminal manager process – TERMMAN will shut down and WASAP will not be accessible.

Recovery: Edit the STARTWVP file to include less than or equal to 20 environment(s).

WVPASAP 552

TM Primary: SPM Start failed for SPM <Error Number>

Relating to function or activity: Inability to start the SP Monitor process.

Cause: Could happen if a previously saved (in cookie) environment does not exist any longer and or the previously used SSG process is no longer running.

Effect: SPMON process will not be created.

Recovery:  Delete cookies. Stop WVP. Stop any SEEVIEW process with names $AAA<l>. Restart WVP

WVPASAP 553

TM Primary: Rate/EDL Obtain Failed for environment <ENV NAME>

Relating to function or activity: TERMMAN process trying to extract the EDL\Rate information

Cause: Occurs when the output of the SSG command does not return the EDL or Sample Interval Rate information in the output.

Effect: The terminal manager process – TERMMAN will shut down

Recovery: N/A

WVPASAP 554

TM Primary: Initial Term Obtain Failed for environment <ENV NAME>

Relating to function or activity: TERMMAN process trying to extract the Term number from the Terminal Monitor DB.

Cause:  If the Terminal Monitor DB is full or if the ASAPCi start fails.

Effect: The terminal manager process – TERMMAN will shut down

Recovery: N/A

WVPASAP 555

TM Backup: No SSG Info., Cannot take over as Primary

Relating to function or activity: TERMMAN process pair functionality

Cause: One of the causes is backup CPU is unavailable

Effect: TERMMAN will shutdown and terminals to issue SSG commands will not be available for SPMON and WASAP processes.

Recovery: Restart WASAP

WVPASAP 556

TM Primary SSGCheck: Failed Security Setting for ASAP. WASAP will function only for user that started Web ViewPoint.

Relating to function or activity: SSG SECURE command issued by the TERMMAN process to configure ASAP for use by all users.

Cause:  Security permissions don’t permit ASAP to be used by all the users.

Effect:  WASAP will only be accessible to the user that started WVP.

Recovery: N/A

WVPASAP 557

<Program Name> <Function Name>: No Term Error.

Relating to function or activity: Requesting Terminal information from SSG

Cause: Terminal information from SSG could not be retrieved. Possible reasons could be security permissions if the Terminal is already being used by another user/process or if the Terminal process is not present on the system.

Effect: The Terminal process will be stopped and WASAP data would not be refreshed.

Recovery: Depending on the cause. One way would be to stop WVP, stop any SEEVIEW process with names $AAA<l> and restart WVP

WVPASAP 558

SPM StartManager: Failed to open TM <Error Number>

Relating to function or activity: Opening the Terminal Manager process.

Cause:  An existing terminal manager process could not be opened. The error number identifies the exact cause of this problem.

Effect: The Terminal process will be stopped and WASAP data would not be refreshed.

Recovery: Depending on the cause. One way would be to restart WVP

WVPASAP 559

<Program Name> <Function Name>: EDL/Environment error.

Relating to function or activity: Parsing the EDL or Environment to display data.

Cause: Cannot get the EDL or Environment information as specified, from the Terminal

Effect: The data will not be displayed on the WASAP screen for the affected environment.

Recovery: N/A

WVPASAP 560

<Program Name> Primary  <Function Name>: Non-IDEL message received

Relating to function or activity: Communicating with the SPM process.

Cause:  An unrecognized/irrelevant message was transmitted/ received while communicating with the SPM process.

Effect: Communication with SPM process would not be complete and SPMON won’t work as expected.

Recovery: N/A

WVPASAP 561

<Program Name> <Function Name>: Parser Error  <Error Number>

Relating to function or activity: Getting all the entities configured in the EDL.

Cause: The SSG command to retrieve the entity returned with an error. Description of the error is contained in the error number.

Effect: The data for the entity will not be displayed.

Recovery: N/A

WVPASAP 562

<Program Name> <Function Name>: <Filename>: <SSG Error description> <Error Number>

Relating to function or activity: Communication with the SSGCOM process.

Cause:  Specific cause depends on the error number.

Effect: Depending on the cause, the Terminal process may stop or data might not be refreshed.

Recovery: Depends on the cause/ error number. One way would be to stop WVP, stop any SEEVIEW process with names $AAA<l> and restart WVP.

WVPASAP 563

WASAP  <Function Name>: Environment Data Not Found

Relating to function or activity: Retrieving a system’s configured environment’s data

Cause: Occurs if the specified environment’s data could not be fetched or if the environment does not exist anymore.

Effect: Data for that particular environment cannot be displayed.

Recovery: Reconfigure the environment to make sure it is running.

WVPASAP 564

WASAP <Function Name>: Entity Data Not Found

Relating to function or activity: Retrieving an environment’s configured entities data.

Cause: If a particular entity listed in an environment could not return data due to removal of that entity from that environment.

Effect: Data for that particular entity cannot be displayed.

Recovery: Reconfigure the environment to make sure the entity is included.

WVPASAP 565

WASAP: Attribute cannot be displayed

Relating to function or activity: Retrieving an entity’s configured attributes ranks.

Cause: Occurs when the all the attribute ranks stored in the DISPCONF file previously don’t match the attribute ranks obtained for the current interval.

Effect: Rank map of attributes for that particular entity cannot be displayed.

Recovery: N/A.

WVPASAP 566

WASAP GetTerm: Processhandle_Getmine_ Error <Error Number>

Relating to function or activity: WASAP process trying to get its process handle.

Cause: WASAP is unable to retrieve its process handle.

Effect: WASAP is unable to issue commands to SSG to retrieve the necessary ASAP information.

Recovery: Stop WASAP processes using STATUS *, PROG WASAP, STOP and retry the operation.