Re: Difference between STSI instruction and SYSEVENT QVS?
On Thu, 1 Feb 2024 13:22:30 -0600, Joe Monk wrote:
>What (if any) is the difference between the STSI instruction and the
>SYSEVENT QVS service, other than maybe the C interface.
SYSEVENT QVS is defined to return information in MSUs. Architecturally, STSI
has unit-less values. ("There is no formal description of the algorithm used to
generate this integer" and the term "MSU" is not in the Principles of Operation.
"Any similarity is purely coincidental."
Alan Altmark
IBM
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Difference between STSI instruction and SYSEVENT QVS?
AFAIK (which admittedly might not be "far" enough), TFP prior to z16 had no information relevant to STSI. There are now TFP hardware records that apply variable capacity for which STSI surfaces information. Possibly QVS should surface that too and might be enhanced to do so. Peter Relsonz/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Difference between STSI instruction and SYSEVENT QVS?
I’m assuming that when STSI was enhanced for z16 – and it was a great enhancement – all the ways of calling it were able to support the new information (and any environmentals). Cheers, Martin From: IBM Mainframe Discussion List on behalf of Attila Fogarasi Date: Saturday, 3 February 2024 at 05:26 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: Difference between STSI instruction and SYSEVENT QVS? substantially the same in terms of information, also don't forget there is also CSRSI which may be a better choice. The callable services validate parameters before calling STSI for you under the covers, also simplify some of the returned info if you are running other than directly lpar on z hardware. On Fri, Feb 2, 2024 at 6:23 AM Joe Monk wrote: > What (if any) is the difference between the STSI instruction and the > SYSEVENT QVS service, other than maybe the C interface? > > Thanks, > > Joe > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Difference between STSI instruction and SYSEVENT QVS?
Just following on from Peter's reply, we recently activated Tailored Fit Pricing (TFP) on a z16 and found that STSI reports the new field, "Model-Variable-Capacity", but SYSEVENT QVS knows nothing about this field. Also, we were told by IBM that there was an MCL change, which we applied to our z16 in November, that modified how TFP was implemented, so maybe this wasn't an issue with the previous implementation of TFP. Cheers, John Date:Sun, 4 Feb 2024 08:48:30 + From:Peter Relson mailto:prel...@yahoo.com>> Subject: Re: Difference between STSI instruction and SYSEVENT QVS? How about: STSI returns a lot of data that is not returned by SYSEVENT QVS? (or so I assume) How about: SYSEVENT QVS returns a lot of data that is not provided by STSI? (or so I assume) Now, if you were to ask about specific fields in SYSEVENT QVS, I think for certain ones the answer is "none", that SYSEVENT QVS obtains them from STSI. Reference was made to CSRSI. Do note that not all of STSI information is accessible via the CSRSI service; the data not provided was not thought to be of general enough use to make it worth providing (and using up the cycles and common storage to make it happen). Peter Relsonz/OS Core Technology Design DXC Technology Australia Pty Limited (ACN: 008 476 944), whose registered office is at 26 Talavera Road, Macquarie Park NSW 2113. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Difference between STSI instruction and SYSEVENT QVS?
How about: STSI returns a lot of data that is not returned by SYSEVENT QVS? (or so I assume) How about: SYSEVENT QVS returns a lot of data that is not provided by STSI? (or so I assume) Now, if you were to ask about specific fields in SYSEVENT QVS, I think for certain ones the answer is "none", that SYSEVENT QVS obtains them from STSI. Reference was made to CSRSI. Do note that not all of STSI information is accessible via the CSRSI service; the data not provided was not thought to be of general enough use to make it worth providing (and using up the cycles and common storage to make it happen). Peter Relsonz/OS Core Technology Design I -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Difference between STSI instruction and SYSEVENT QVS?
substantially the same in terms of information, also don't forget there is also CSRSI which may be a better choice. The callable services validate parameters before calling STSI for you under the covers, also simplify some of the returned info if you are running other than directly lpar on z hardware. On Fri, Feb 2, 2024 at 6:23 AM Joe Monk wrote: > What (if any) is the difference between the STSI instruction and the > SYSEVENT QVS service, other than maybe the C interface? > > Thanks, > > Joe > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Difference between STSI instruction and SYSEVENT QVS?
What (if any) is the difference between the STSI instruction and the SYSEVENT QVS service, other than maybe the C interface? Thanks, Joe -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
