Velocity Software, Inc. is recognized as a leader in the performance measurement of z/VM and Linux on z. The Velocity Performance Suite consist of a set of tools that enable installations running z/VM to manage Linux and z/VM performance. In addition, many components of server farms can be measured and analyzed. Performance data can be viewed real-time through the use of either 3270 or a browser. The CLOUD Implementation (zPRO) component is designed for full cloud PaaS implementation as well as to extend the capabilities of the z/VM sysprog (system programmer) to the browser world. This feature moves system management to the point-and-click crowd. Archived data and reports can be kept available of long term review and reporting usine zMAP. The zVPS, formally ESALPS, components consist of: zMON (formally ESAMON - real-time display of performance data), zTCP (formally ESATCP - SNMP data collection), zMAP (formally ESAMAP - historical reporting and archiving), zVWS (formally ESAWEB - z/VM based web server), zTUNE (a subscription service), zVIEW (formally SHOWCASE - web based viewing of performance data), zPRO (new to the quality line of Velocity Software Products). Velocity continues to work with other software vendors to ensure smooth interface with or from other products such as VM:Webgateway, CA-Webgateway, EnterpriseWeb, MXG, MICS. Velocity software remains the leader and inovator in the z/VM performance, Linux performance, Managing cloud computing arenas.
About Us | Products | FAQ | Demo | Customer Area | Education | Linux Hints & Tips | Presentations | News | Industry and Events | Employment Opportunities
Home | Contact Us | License Info | Newsletter    

Moving MXG data to z/OS.

To move the data collected for MXG from the ESALPS collection to z/OS requires the following. This procedure will need to be updated to meet installation requirements.

MXG is capable of reading the HISTORY files created by ESALPS. The midnight processing of ESAMAP, collects the days worth of data and summarizes that data into installation defined intervals. Upon successful completion the MAPGOOD EXEC will be invoked.

The MAPGOOD EXEC needs to be copied to the "A" disk. There is a sample on the product disk (E-disk by default). This EXEC needs to have the following line added:


Here is an example of the contents of a proposed ESAMXG EXEC

/*                                                          */
/* S A M P L E                                              */
/*                                                          */
/* exec to send selected history files to ZOS               */
/* Set target ZOS system target variables                   */
  ZOS          = ''       /* Target IP address   */
  Myid         = 'George'            /* Authorized userid   */
  Mypswd       = 'Jungle'            /* Password            */
  zosdirectory = 'abc.def'           /* Target directory    */
/* Send file to ZOS via FTP                                 */
  queue myid mypswd                  /* Stack ID and PSWD   */
  queue 'cd',
      "'" || zosdirectory || "'"     /* ... target directory*/
  queue 'mode b'                     /* ... BLOCK mode      */
  queue 'type e'                     /* ... EBCDIC          */
/* Get the list of HISTORY files to ship                    */
    '| JOIN * \/ ! /\',
    '| SPEC W1.2 1',
    '| ALL /' || SHIPLIST || '/',
    '| spec \put\ 1 w1 nw \.\ n w2 n',
    '| stack fifo'
  queue 'quit'                       /* ... then QUIT       */
  'FTP' ZOS                          /* Issue FTP           */
  If rc <> 0 then
    Say '*** Error *** RC' RC 'from FTP to -',
      ZOS '>' zosdirectory
Exit rc

Don't miss Velocity Software's Performance Seminars