You are here

Configuring Performance Toolkit to Allow Access outside the PERFSVM Virtual Machine (Tuco Bonno)

It has been suggested/requested of me by one of the respondents to the thread that I initiated that I write up and post to the list exactly what I DID that solved my problem (an after-action report), so here it is.

(1) SITUATION.

6.1 VM, pretty much vanilla the way I got it out of the box from ibm and installed it last august, running in its own IFL lpar on a Z10 box. RACF, DirMaint, and PerfToolKit installed, activated, and customized according to the respective Program Directories. I am the only person using VM; it’s not being used by any subordinate “virtual machines” (e.g., “linuxen”) to do any “work” of any kind. PerfToolKit works quite fine when I logon to the PERFSVM userid but when I try to invoke PerfTookKit from within the MAINT userid, nothing happens.

(2) MISSION.

Do what you have to do, modify VM environment, whatever, such that when I logon to MAINT and issue the “perfkit” command, the PerfToolKit screen fcx124 appears and all functions therein work just like they do when I log on to userid PERFSVM.

(3) EXECUTION.

  1. In PERFSVM’s FCONX $PROFILE file on its 1CC disk, uncomment the “FC MONCOLL VMCF ON” line.
  2. In PERFSVM’s FCONRMT AUTHORIZ file on its 191 disk, add the following line: “nodeid maint data cmd”
  3. On PERFSVM’s 191 disk, create a FCONRMT SYSTEMS file and put in the following line: “nodeid perfsvm esa y fcxres00”
  4. In AUTOLOG2’s PROFILE EXEC file on AUTOLOG2 191, add the following line : “ ‘cp xautolog perfsvm’ “

    NOTE: did NOT add the line to AUTOLOG1’s PROFILE EXEC b/c in my VM, RACF is the security product; AUTOLOG1’s sole function is to launch RACF, which in turn launches AUTOLOG2 which in turn launches the various service machines.
  5. On the userid you want to use to access PerfKit data, create the following file: ALLOCPTK EXEC and put in it the following lines:

    'LINK PERFSVM 201 202 RR'

    'LINK PERFSVM 29D 29D RR'

    'LINK PERFSVM 1CC 1CC RR'

    'ACC 202 E'

    'ACC 1CC F'

    'ACC 29D G'

    /* See Editor's Note Below */

    'CP MONITOR SAMPLE ENABLE PROCESSOR'

    'CP MONITOR SAMPLE ENABLE STORAGE'

    'CP MONITOR SAMPLE ENABLE USER ALL'

    'CP MONITOR SAMPLE ENABLE I/O ALL'

    'CP MONITOR SAMPLE ENABLE NETWORK'

    'CP MONITOR SAMPLE ENABLE APPLDATA ALL'

    'CP MONITOR EVENT ENABLE STORAGE'

    'CP MONITOR EVENT ENABLE I/O ALL'

    NOTE: contrary to what several people suggested to me, I did NOT need to uncomment the various ‘cp monitor ….’ statements in PERFSVM’s PROFILE EXEC; PerfToolKit was already working quite fine in PERFSVM; those line had been uncommented when PerfToolKit was originally installed, activated, and customized …
    Ed. Note: These CP MONITOR statements should actually go in PERFSVM's PROFILE EXEC -- Tuco's process works because he was running it in the MAINT virtual machine, which has sufficient privleges to issue them. If you move the CP MONITOR lines above to PERFSVM's PROFILE EXEC, his process will work on a normal non-privileged user -- always a safer option.
  6. Log PERFSVM off and back on.
  7. Logon to the userid you were using earlier, issue “q n” and make sure there’s an entry which reads “ PERFSVM - DSC “
  8. Still in that userid, issue “q resource” and make sure there are two entries which read as follows:

    Resource: FCXRES00 Type: Global Owning Userid: PERFSVM

    Resource: FCXSYSTM Type: System Owning Userid: PERFSVM

  9. Issue “ ALLOCPTK” command
  10. do “q disk” and make sure you’ve got the 1CC, 202, and 29d minidisks accessed.
  11. If you are using Fullscreen CMS, turn it off with SET FULLSCREEN OFF.
  12. Issue the following command: perfkit

    You should see the following screen ID: fcx001. There will be several red (in my 3178 session) error messages: fcxpmn440e, fcxapp524e, fcxapf524e, fcxapc523e, fcxrmt122i --- don’t worry about them (at least not NOW).

  13. At the command prompt in screen fcx001 issue this: fconappc

    The fcx124 screen appears.

NOTE: This is NOT a clean install, vide the misc error messages supra. that I’m still going to need to mess around with. but at least now, I can get to the fcx124 screen in PerfToolKit from a MAINT session, and see what I need to see therein ….

(4) ADMIN AND LOGISTICS.

My sincere thanks to the following individuals in the VM listserver community who responded to my original post, both in the listserver as well as offline: Bill Munson, Robert Nix, Aria Bamdad, Kris Buelens, William Mongan, Neale Ferguson, Tom Huegel, David Boyes

/s/ “sonny”

aka

tuco bonno;

Graduate, College of Conflict Management;

University of SouthEast Asia;

"I partied on the Ho Chi Minh Trail - tiến lên !! "

Theme provided by Danetsoft under GPL license from Danang Probo Sayekti