A Second MONWRITE Machine

So, you need to collect some MONWRITE data, but the user ID named "MONWRITE" is busy doing something else?

Or, someone asked you to collect MONWRITE data without tinkering with the MONDCSS, or the CP Monitor settings, or the other CP-Monitor-related products you are already running on your system?

Here's how to collect a short specimen of whatever CP Monitor data your system is already emitting.

These steps won't interfere with the other CP Monitor activities already happening on your system.

  1. If your user called "MONWRITE" is already busy, create a userid in which you can run the MONWRITE program. Let's call this userid MONW2. Here's a CP directory template you can use: USER MONW2 xxxxxxxx 64M 256M G IPL CMS PARM AUTOCR MACH XC OPTION QUICKDSP IUCV *MONITOR MSGLIMIT 255 NAMESAVE MONDCSS SHARE ABSOLUTE 3% SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A CONSOLE 009 3215 T LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR a 191 disk big enough to hold the data

  2. If you created MONW2, log on to MONW2 and format its 191 disk. Otherwise log onto MONWRITE.

  3. Now, to start collecting, type this command: MONWRITE MONDCSS *MONITOR DISK MYDATA MONDATA A

  4. Wait until it is time to stop collecting.

  5. To stop collecting, type this command: MONWSTOP

Your data lands in file MYDATA MONDATA A. Package it up and send it to whoever asked for it. If you are sending the data to IBM, read here for packaging and transmission instructions.