OPS/MVS

 View Only
  • 1.  no HWILIST in address HWS ?

    Posted Dec 19, 2019 06:57 AM
    Hello All,
    what is the recommended way to obtain a list of lpar names on one or more cpc's with OPS Rexx?
    In IBM system rexx I would use

    ListImages:
    PARSE ARG ConnectToken
    ListType = HWI_LIST_IMAGES
    ImageList. = 'Image names will be listed here'
    address bcpii "hwilist ",
    "ReturnCode ",
    "ConnectToken ",
    "ListType ",
    "ImageList. ",
    "DiagArea."

    Can I do the same with address HWS ?
    The doc for address HWS says I can do SENDCMD|GETATTR|SETATTR,   HWILIST is not an option.
    Thanks, Tim.


  • 2.  RE: no HWILIST in address HWS ?
    Best Answer

    Broadcom Employee
    Posted Dec 19, 2019 07:55 AM
    Hi, there is no direct interface to HWILIST in address HWS to list the LPAR's, however if you are running the OPS/MVS 13.5 and the OPSBCPII Server you can list the HMC Network's topology and parse the results as you desire. Here's a bit of code that allows this:

    /* REXX */
    ADDRESS TSO
    "OPSCMD C('F OPPTMBCP,DIS.OPSZ TOPOLOGY')"

    DO Queued() /* Returns command results */
    PULL msg
    SAY msg
    END

    In this case, OPSZ is my OPS subsystem id and OPPTMBCP is the OPSBCPII Server PROC name. If you are using HISRV it would look like this:

    /* REXX */
    ADDRESS TSO
    "OPSCMD C('F OPPTMHIS,SHOW HWITOP')"

    DO Queued() /* Returns command results */
    PULL msg
    SAY msg
    END


  • 3.  RE: no HWILIST in address HWS ?

    Posted Dec 19, 2019 09:08 AM
    Hello Anthony,
    thank you for confirming there is no HWILIST in HWS.
    I was hoping I wouldn't have to scrape stuff off a command response.
    Command responses have a habit of changing format in new releases,
    or they arrive a millisecond after you stopped waiting for them.
    Regards, Tim.


  • 4.  RE: no HWILIST in address HWS ?

    Broadcom Employee
    Posted Dec 19, 2019 10:18 AM
    Hi Tim, these displays are not likely to change. The HISRV version has been this way for years and the OPSBCPII version likely won't. In your case, I think if you ignore all lines except those that have the word "CPC" and "LPAR" it should give you a hierarchical picture of what LPAR's reside on a particular CPC. I suspect those keywords will always be present in the unlikely event of a change.