Using the SYSVIEW API to monitor Datacom LXX usage
Article ID: 36991
Updated On:
Products
Issue/Introduction
Monitoring system information in the Datacom environment is made much easier when using the SYSVIEW Rexx API. In the case of monitoring the current utilization of the LXX (Log Area), the easier you can get this information, the easier it could be to prevent some problems.
This article assumes that you can already use the DCLOG command to display this information from within the SYSVIEW environment.
Environment
Component : SYSVIEW
Component : Datacom/AD
Component : Datacom/DB
Resolution
There are three different methods listed here to get the LXX utilization for one or more Multi-User Facility (called MUF) tasks:
1. Using the GSVXBAT program through JCL
2. Using a Rexx Program to list details for one MUF’s LXX
3. Using a Rexx Program to list details for all MUFs on a given LPAR
Note that these are samples provided for your own use and can be customized according to your needs.
Using the GSVXBAT program through JCL
By using the GSVXBAT program, you can issue the same commands as if you were in the ISPF application for SYSVIEW. Here is a sample jobstream:
//STEP0001 EXEC PGM=GSVXBAT
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COMMAND=(ASID mufjobname)
COMMAND=(DCLOG)
COMMAND=(END)
/*
Using a Rexx Program to list details for one MUF’s LXX
By using a Rexx program called SVLXX, you can display information about the LXX for a single MUF. Please download this Rexx sample program from the attached .zip file and place it in a PDS where your Rexx programs can run. The syntax of this command is:
TSO SVLXX mufname
Where mufname is the name of the MUF you wish to query.
The output of this command is a simple box display:
---------------------------------------------------------------------------
- 23.10.19 11:07:41 -
- MY15MUF (STC14973) -
---------------------------------------------------------------------------
***************************************************************************
* *
* LXX has 1000 tracks, used 573 out of 997 blocks (57%) *
* *
* The LXX has not spilled during this MUF execution. *
* There are 572 blocks ready to be spilled *
* *
* Note: this value is dynamic and is constantly changing *
* *
***************************************************************************
Using a Rexx Program to list details for all MUFs on a given LPAR
By using a Rexx program called SVLXXALL, you can display the LXX details for every MUF currently running on the LPAR where the command is run. Please download this Rexx sample program from the attached .zip file and place it in a PDS where your Rexx programs can run. The syntax of this command is:
TSO SVLXXALL
The output of this command is a box display with one line for each MUF:
----------------------------------------------------------------------------
- 23.10.19 11:11:09 -
- LXX Statistics for Active MUFs on SYS1 in MYPLEX1 -
----------------------------------------------------------------------------
****************************************************************************
* *
* MUF JOB or Total Used Total Pct Last LXX Spill Blocks *
* Name STC ID Tracks Blocks Blocks Full Date Time Spillable *
* -------- -------- ------ ------ ------ ---- -------- -------- ------ *
* MY15MUF STC14973 1000 573 997 57 No spills 572 *
* BPRDMUF STC14974 2400 1856 2397 77 10/19/23 11:03:22 1855 *
* TESTCMUF STC14976 2400 1222 2397 51 No spills 1221 *
. . .
* MUFLFUL STC14900 2400 2347 2397 98 10/15/23 08:47:41 2346 *
* -------- -------- ------ ------ ------ ---- -------- -------- ------ *
* MUF JOB or Total Used Total Pct Last LXX Spill Blocks *
* Name STC ID Tracks Blocks Blocks Full Date Time Spillable *
* -------- -------- ------ ------ ------ ---- -------- -------- ------ *
* *
* Note: this value is dynamic and is constantly changing *
* *
****************************************************************************
Additional Information
Please download the attached file if you would like to use the TSO commands SVLXX and SVLXXALL.
As always, please contact Broadcom support for Datacom if you have further questions.
Attachments
Feedback
