Skip to Content

Milestone 7 Verify Product Installation

This milestone contains tasks to verify that Performance Test is usable.

Warning

Important

  • Figures shown below are representative of 3270 Global Recording via Performance Test being used for validation. Keep in mind that these figures will differ for other recording technologies.
  • Roles involved: Performance Test Installer

Complete the following tasks to verify product execution.

Task 7.1: Start Global Recording Started Task

The purpose of this task is to ensure the Global Recording started task starts and remains running. If improperly configured or running in an unsupported VTAM version, the Global Recording started task will shut down. This task should be performed if Global Recording/Archive Recording is being used.

  1. Issue the start command to start the Performance Test Global Recording task. This allows for the capturing of 3270, APPC, TCP, and MQ data.

  2. Look at the SVMPA195I and SVMAP196I messages in the message log of the Global Recording started task (Started Task Job Output) to ensure that parameters are coming from the correct PARMLIB member and data set.

    Performance Test Started Task Job Output
     

       Display  Filter  View  Print  Options  Search  Help
     -------------------------------------------------------------------------------
     SDSF OUTPUT DISPLAY HS       STC89780  DSID     2 LINE 0       COLUMNS 02- 81
     COMMAND INPUT ===>                                            SCROLL ===> CSR
    ********************************* TOP OF DATA **********************************
                           J E S 2  J O B  L O G  --  S Y S T E M  A C 0 6  --  N O

    14.11.53 STC89780 ---- MONDAY,    13 NOV 2017 ----
    14.11.53 STC89780  IEF695I START HS       WITH JOBNAME HS       IS ASSIGNED TO U
    14.11.53 STC89780  $HASP373 HS       STARTED
    14.11.53 STC89780  IEF403I HS - STARTED - TIME=14.11.53
    14.11.53 STC89780  SVMAP195I PARAMETERS LOADED FROM MEMBER: HSCMXML
    14.11.53 STC89780  SVMAP196I                       DATASET: AC06.CMSC.PARMLIB
    14.11.53 STC89780  SVMAP001I SCANNING GLOBAL RECORD INITIALIZATION PARAMETERS
    14.11.53 STC89780  SVMAP101I SECSYS(RACF)
    14.11.53 STC89780  SVMAP101I ALLNET
    14.11.53 STC89780  SVMAP101I ALLNBUFS(200)
    14.11.53 STC89780  SVMAP101I ALLNBUFL(1024)
    14.11.53 STC89780  SVMAP101I SESSCNT(2000)
    14.11.53 STC89780  SVMAP101I SCREATE(HC172717)
    14.11.53 STC89780  SVMAP101I REGISTRY(HSRGSTRY)
    14.11.53 STC89780  SVMAP101I SWITCH(HSEARCH)
    14.11.53 STC89780  SVMAP101I TCPIP(TCPIP)
    14.11.53 STC89780  SVMAP101I OMVS(OMVS)

  3. Validate that the following messages appear in the log:

    SVMAN391I  VTAM    CAPTURE REQUESTED - Hiperstation for VTAM & Hiperstation for
       Mainframe Servers
    SVMAN391I  TCPIP    CAPTURE REQUESTED - Hiperstation for Mainframe Servers
    SVMAN391I  MQSERIES CAPTURE REQUESTED - Hiperstation for Websphere MQ

  4. Look further in the message log and find the message:
       ETGRMN001I HIPERSTATION GLOBAL RECORDING ACTIVATED
  5. Ensure the Global Recording started task remains active.

Task 7.2: Start Global Recording Capture request

If you only installed Performance Test for Websphere MQ, skip ahead to Task 7.4: Start WebSphere MQ Global Recording Capture Request.

This task should be performed if Global Recording will be used.

  1. Execute the Performance Test CLIST built by the guided customization dialog to enter Performance Test. The default name for this CLIST is (LIBDEF). The Performance Test Product Menu is displayed as shown in the following figure.
    Performance Test Product Menu

       ---------------- BMC AMI DevX Performance Test - Product Menu -----------------
       Option  ===>


         0  Profiles                           Set user profiles
         1  VTAM                               VTAM Application Testing
         2  Mainframe Servers                  SNA/APPC & HTTP Testing
         3  WebSphere MQ                       WebSphere MQ Message Testing
         4  ATV Manager                        Automated Testing Vehicle Manager

            Profile         ===> PROFILE
            Profile dataset ===> 'PMIJSS0.JMS.ATV.PROFILE'

            Leave Profile blank for selection list
            Leave Profile dataset blank to create new dataset
            Leave both blank to run with no Profile




             (C) Copyright 1994, 2022 BMC Software, Inc. All Rights Reserved.
        Unpublished-rights Reserved Under the Copyright Laws of the United States.

  2. Enter 1 in the Option field to select Performance Test for VTAM. The Performance Test Main Menu is displayed (See the following figure).
     Performance Test Main Menu

      ------------------  Performance Test for VTAM - Main Menu  --------------------
       Option  ===> 4

                                                            Product Release: 17.02.00
         1  Domain Traveler              Record and Playback
         2  Quick Play                   Select a Script and Go
         3  Session Demo                 Demonstrate Online Applications
         4  Global Recording             System and Application Test Creation
         5  Script Processors            Automatic Script Editing
         6  Unattended Processing        Setup Unattended Playback and Compare Jobs

     

  3. Enter 4 in the Option field to select Global Recording. The Global Recording screen (See the following figure) is displayed.
    Global Recording screen

       ------------------------------- Global Recording ------------------------------
       Option  ===> 1

       SNA (3270, LU0, APPC)
          1  Monitor Requests          Add, Review or Update your requests
          2  Review Repository         Review your captured sessions
          3  Global Record Manager     Manage Include/Exclude filter lists

       TCP/IP
          6  Monitor TCP/IP Requests   Add/Review your TCP/IP recording requests
          7  Create TCP/IP Scripts     Create TCP/IP scripts from a repository


             Enter END command to return to Performance Test for VTAM Main Menu.

     

  4. Enter 1 in the Option field to select Monitor Requests.

    1. If the screen shown in Global Recording Add Requests screen is displayed, go to Step 5.
    2. If the screen shown in Global Recording Monitor Requests screen is displayed, go to Step 6.

    Global Recording Add Requests screen

       ----------------------  Global Recording - Add Requests  ----------------------
       Command ===>

        Press ENTER to continue, or END to return.

        *****************************************************************************
        *                                                                           *
        *          No Global Recording Requests were found for your userid.         *
        *                                                                           *
        *****************************************************************************

        Type of request to add:
          1  1. 3270
             2. APPC
     

    Global Recording Monitor Requests screen

      --------------------- Global Recording - Monitor Requests ------ REQUEST ADDED
       Command ===>                                                  Scroll ===> PAGE

       Line commands are: (C)ancel, (F)orce, (P)Stop, (R)estart,  (D)isable,
                          (S)elect, (U)pdate,(V)iew,  (1)Add 3270,(2)Add APPC, or
                          (9)Switch repositories

          LU   Side-A/  Side-B/            Repository
       S  Type Applid   Terminal Userid    Dataset                               Users
       -  ---- -------- -------- --------  ------------------------------------- ----
       1  3270 *        *        *         PMIJSS0.EXAMPLE.REPOS001                 0
       ******************************* BOTTOM OF DATA ********************************

     

  5. Type 1 to select a 3270 request type (Global Recording Add Requests screen) and press Enter. The 3270/LU0 Capture Criteria screen (3270/LU0 - Capture Criteria) is displayed. Go to Step 7.

  6. Enter 1 in the S column of the first entry in the list to specify Add 3270 (Global Recording Monitor Requests screen) and create a new Global Recording request. The 3270/LU0 Capture Criteria screen is displayed.
    3270/LU0 - Capture Criteria
     

       ------------------------  3270/LU0 - Capture Criteria  ------------------------
       Command ===>

        Press ENTER to continue, or PF1 for help, or CANCEL to exit.

        Terminal . . . . . . . . . . . *        Use an asterisk for wildcarding
        Application  . . . . . . . . . *        the Terminal, Application or Userid
        Userid . . . . . . . . . . . . *        fields.
         OR
        Global Record Manager List . .          Second filter GRM List . .

                         HH : MM : SS                    MM / DD / YY
        Start Time . . . 00 : 00 : 00   Start Date . . . 00 / 00 / 00  (Optional)
        End Time . . . . 00 : 00 : 00   End Date . . . . 00 / 00 / 00  (Optional)

        Repository Dataset . . . 'PMIJSS0.EXAMPLE.REPOS*'
        First and last number. . 1       5       (If wildcard in dataset)

        Recording options:  (Enter "/" to select)
             Suspend script creation         /  Normal event notification
          /  Re-use repositories             /  Error event notification
             FORCE request at 'End Time'        Record from LOGON only
     

     

  7. Complete the 3270/LU0 Capture Criteria screen as follows:
    1. Enter your ID in the Userid field with an asterisk (*) in both Terminal and Application fields.
    2. Enter the name of a data set that does not exist in your environment in the Repository Dataset field.
    3. Under Recording options, use a slash (/) to select only Suspend script creation and Error event notification. Do not select Normal event notification, Re-use repositories, FORCE request at ‘End Time’, or Record from LOGON only.
    4. Press Enter. For testing purposes, accept the default allocations. The Global Recording Monitor Requests screen will be displayed, and your request should appear highlighted.
  8. Log off from your TSO session, then log back on. Return to the Global Recording Monitor Requests screen. The Users count should be 1.
  9. Enter the F line command to issue the Force command on the Global Recording Monitor Requests screen.
  10. Either browse the Global Recording repository or perform a script create to validate that data has been recorded.

Task 7.3: Start a Domain Traveler Session

If you did not install Performance Test for VTAM, skip ahead to Task 7.5: Additional Verification.

The purpose of this task is to ensure users can connect to an APPLID using Performance Test's Domain Traveler.

  1. Go to the Performance Test Main Menu ( Performance Test Main Menu).

  2. Enter 4 in the Option field to select Domain Traveler. The Performance Test * Domain Traveler screen (See the following figure) is displayed.
    Performance Test * Domain Traveler screen

       ------------------------------- Domain Traveler -------------------------------
       Command ===>

         Use this panel to connect to one of your site's domains.  When
         connected you can record your session or play back previous sessions.

          Domain Destination . TSO

          / Change session options (Enter "/")


           Start = ISPF , Zoom = F23  , LUName = Default  , Restore Keyboard
           Logmode = SNX32705 , Model = 5-(27X132), SNA = Yes , Queriable = Yes
           Application Profiling(Off) , IMS = Y

  3. In the Domain Destination field, type the APPLID of an environment used for testing, then type a slash (/) to select Change session options and press Enter. The Session Options screen (See the following figure) is displayed.
    Session Options Screen

       ------------------------------- Session Options -------------------------------
       Command ===>

         Logon data. . . .                                            (Optional)
         ZOOM mode . . . . N        Y=yes, N=No
         ZOOM key. . . . . F23
         LU name . . . . .          (Terminal name used to login to application)
         Logmode . . . . . SNX32705 (Overrides model, SNA and Queriable options)
         3270 model. . . . 5        1=12x40, 2=24x80, 3=32x80, 4=43x80, 5=27x132
         SNA . . . . . . . Y        Y=yes, N=no
         Queriable . . . .          Y=yes, N=no
         Trailing Blanks . 1        (Only applies to non-Zoom mode)
         Infirst . . . . . Y        Y = No Welcome Screen From Domain Destination
         Appl Profiling. .          "/" to View application profile settings
         The following PF key translations apply to the Domain Destination when
         in non-Zoom mode:
           PF01 = F1      PF04 = F4      PF07 = F7      PF10 = F10     PA1  =
           PF02 = F2      PF05 = F5      PF08 = F8      PF11 = F11     PA2  =
           PF03 = F3      PF06 = F6      PF09 = F9      PF12 = F12     CLEAR=

     

  4. Validate that the values shown for Logmode or 3270 model, SNA, and Queriable are valid for the environment to which you will connect. Change these fields to valid values if needed. You may want to change the default values for these parameters in the PARMLIB member for Performance Test.
  5. Press PF3.
  6. Press Enter to connect to the APPLID. You should see the initial screen for the APPLID to which you connected.

Task 7.4: Start WebSphere MQ Global Recording Capture Request

The purpose of this task is to ensure that a Global Recording task can be started and capture data for MQ.

Warning

Important

The following example assumes your user ID has update access to the Global Recording request data set.

  1. Execute the Performance Test CLIST built by the guided customization dialog to enter Performance Test. The default name for this CLIST is (LIBDEF). The Performance Test Product Menu is displayed as shown in  Performance Test Product Menu.

  2. Enter 3 in the Option field to select Performance Test for WebSphere MQ. The Performance Test for WebSphere MQ Main Menu is displayed (See the following figure).
    Performance Test for WebSphere MQ Main Menu

       ---------------- Performance Test for WebSphere MQ - Main Menu ----------------
       Option  ===> 1
                                                        Product Release: 17.02.00

          1  Monitor MQ Requests       Add/Review your MQ recording requests
          2  Create MQ Scripts         Create MQ scripts from a repository
          3  Playback MQ Scripts       Execute and save playbacks of MQ scripts
          4  MQ Playback Reporting     Report on database created from playback

     

  3. Enter 1 in the Option field to select Monitor MQ Requests.

    1. If the screen shown in Global Recording * Requests screen is displayed, go to Step 4.
    2. If the screen shown in Global Recording Monitor MQ Requests screen is displayed, go to Step 5.

    Global Recording * Requests screen

       ------------------------- Global Recording * Requests -------------------------
       COMMAND ===>

     

      ******************************************************************************
      *                                                                            *
      *           No Global Recording Requests were found for your userid.         *
      *                                                                            *
      ******************************************************************************




                         Enter END to exit, ENTER to add a new request.

    Global Recording Monitor MQ Requests screen

       -------------------- Global Recording - Monitor MQ Requests ---- REQUEST ADDED
       Command ===>                                                  Scroll ===> PAGE

       Line commands are: (C)ancel, (F)orce, (P)Stop, (R)estart, (D)isable,
                          (S)elect, (U)pdate, (A)dd, (V)iew, or
                          (9)Switch repositories

          Request   Active     Total   Repository
          Owner    Sessions  Sessions  Dataset
          -------  --------  --------  --------------------------------------------
          PMIJSS0                      PMIJSS0.SMOKEM.D22S.REPOS001
       ******************************* BOTTOM OF DATA ********************************

    Press Enter. The WebSphere MQ Data Collect - Output screen (WebSphere MQ Data Collect - Output screen) is displayed. Go to Step 6.

  4. Enter A to the left of the first entry in the list (Global Recording Monitor MQ Requests screen) to create a new Global Recording request. The WebSphere MQ Data Collect screen (See the following figure) is displayed.
    WebSphere MQ Data Collect screen
     

       -------------------------- WebSphere MQ Data Collect --- Enter record criteria
       Command ===>                                                  Scroll ===> CSR

       Make changes to data collection criteria below or select a filter to edit the
       expanded fields. Use OK command when complete.

       Restrict script input to certain times:
                      HH : MM : SS                  MM / DD / YYYY
       Start Time . . 00 : 00 : 00   Start Date . . 00 / 00 / 0000
       End Time . . . 00 : 00 : 00   End Date . . . 00 / 00 / 0000

       Force at End Time . . .

       Line commands are: (S)elect, (R)epeat, (D)elete, or (I)nsert

       S Ftr Act  QMGR Queue/Object name                            Jobname  Comp Reas
       * *** **** **** ******************************************** ******** **** ****
       _ 001 INCL
       * *** **** **** ******************************************** ******** **** ****

  5. In the OMGR field, type the name of a queue manager on which your site plans to do recordings, in the Queue/Object name field, type an asterisk (*), and on the Command line, type OK. Press Enter. The WebSphere MQ Data Collect - Output screen is displayed as shown in the following figure.
    WebSphere MQ Data Collect - Output screen

       ---------------------- WebSphere MQ Data Collect - Output ---------------------
       Command ===>

       Choose where to store the data, then press ENTER to continue.

       Repository dataset:
         Dataset name . . . . . . 'PMIJSS0.SMOKEM.D22S.REPOS*'
         First and last number  . 0000001 5       (Needed if wildcard in dataset name)

       Re-use repository options: (Enter "/" to select)
         /  Delete existing data
            Append to existing data
         /  Overwrite existing data when all segments are full

       Amount of data to use:
         Message data from GETs . . . ALL      (ALL or number of bytes)
         Message data from PUTs . . . ALL      (ALL or number of bytes)
     
  6. Complete the WebSphere MQ Data Collect - Output screen (WebSphere MQ Data Collect - Output screen) as follows:
    1. Enter the name of a data set that does not exist in your environment in the Dataset name field.
    2. Under Re-use repository options, use a slash (/) to select only Append to existing data. Do not select Delete existing data or Overwrite existing data when all segments are full.
    3. Specify ALL for both Message data from GETs and Message data from PUTs.
    4. Press Enter. For testing purposes, accept the default allocations. The Global Recording Monitor MQ Requests screen will be displayed, and your request should appear highlighted.
  7. Either wait for MQ activity to occur or run a program that does MQ activity on the MQ manager you specified on the Global Recording request.
  8. Wait to see Active Sessions and Total Sessions increase for your Global Recording request.
  9. Enter the F line command to issue a Force command on the Global Recording Monitor MQ Requests screen.
  10. Either browse the Global Recording repository or perform a script create to validate that data has been recorded.

Task 7.5: Additional verification

You may want to perform further verification by exercising additional features of Performance Test.

Information
Example

Record/playback via domain traveler, script create, playback, session demo, and so on.

For details on these features and how to perform them, see the appropriate section in the Performance Test User Guide.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI DevX Performance Test 17.02