Re: CSVFETCH exit

In fact, I use LLA exit1, not exit2, because exit1 has the details of each fetch. Kees. -Original Message- From: Vernooij, CP (ITOPT1) - KLM Sent: 24 March, 2016 8:23 To: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Subject: RE: CSVFETCH exit Leo, We move the m

Re: CSVFETCH exit

Ok! Thanks for the clarification! -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, CP (ITOPT1) - KLM Sent: Thursday, March 24, 2016 10:57 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit We use it for modules under

Re: CSVFETCH exit

: CSVFETCH exit Still, you wouldn't know if the old module is still being used from a (non-LLA) steplib, right? Am I missing something? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vernooij, CP (ITOPT1) - KLM Sent: Thursday, March

Re: CSVFETCH exit

AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit Leo, We move the modules to a LNKLST library, so we are sure they are seen by LLA when they are fetched. Yes, CSVFETCH has more capabilities, but just for the task of catching certain, old, modules, the LLA trick is more simple. Kees

Re: CSVFETCH exit

List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Leonardo Vaz Sent: 23 March, 2016 18:32 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit Kees, The exit is called with the local lock held, so BPX4SMF wouldn't work, I couldn't find the requirements for SMFWTM but if that also doesn't

Re: CSVFETCH exit

, March 23, 2016 9:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit > Peter, the Rexx compiler produces object code that may be linked into > a z/OS > executable -- just like the COBOL compiler. I am sure to CSV it looks just > like any other load module. You can browse a c

Re: CSVFETCH exit

As to the question, what can you do with the information CSVFETCH makes available: can I write an SMF record from CSVFETCH? You should be able to use SMFEWTM BRANCH=YES can write a SMF record from the exit. Greg -- For

Re: CSVFETCH exit

ubject: Re: CSVFETCH exit To determine if certain loadmodules are still being used, we use LLA EXIT2 since decades. We move the modules to a special LNKLST library, monitor with LLA EXIT2 fetches from this library and write an SMF record for the event. CSVFETCH apparently is able to catch

Re: CSVFETCH exit

able code. But it is not in the format of an OBJ or load module or program object. So it cannot be processed directly by any Binder or CSV services. It is something that the Rexx interpreter reads into storage and invokes. This is an example of what the Rexx compiler documentation calls CEXEC format. The

Re: CSVFETCH exit

Of Peter Relson Sent: Wednesday, March 23, 2016 4:40 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit If compiling a REXX exec results in a load module (or program object) and if someone then does a LOAD to access it (or something similar), then the resulting fetch will drive the exit. I

Re: CSVFETCH exit

Sent: 21 March, 2016 14:47 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit I have a different question relative to this exit. I've been looking for doc on line and have found two manuals that have CSVFETCH as an exit point defined, and one has the parm area info. Peter did

Re: CSVFETCH exit

On Wed, 23 Mar 2016 06:39:40 -0500, Peter Relson wrote: >If compiling a REXX exec results in a load module (or program object) and >if someone then does a LOAD to access it (or something similar), then the >resulting fetch will drive the exit. > >I think that those two IF's

Re: CSVFETCH exit

On 3/23/2016 5:36 AM, David Crayford wrote: On 23/03/2016 5:41 AM, Charles Mills wrote: There is a compiler for Rexx but its performance improvement is moderate. It depends on what the REXX is doing. We compiled the ISPF DTL compiler and saw a significant performance improvement. IIRC,

Re: CSVFETCH exit

If compiling a REXX exec results in a load module (or program object) and if someone then does a LOAD to access it (or something similar), then the resulting fetch will drive the exit. I think that those two IF's are not true. Mostly because I don't recall having something that is compiled

Re: CSVFETCH exit

of mainframe products including a dynamic STEPLIB product. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Tuesday, March 22, 2016 2:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit There were three

Re: CSVFETCH exit

-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Edward Finnell Sent: Tuesday, March 22, 2016 2:23 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit There were three CLIST compilers that I'm aware of. XLR8(Fischer), TMON(Tone

Re: CSVFETCH exit

There were three CLIST compilers that I'm aware of. XLR8(Fischer), TMON(Tone), and CLICK(IBM Internal). In mid eighties we had good results with XLR8 and ADF II. As jobs changed fewer folks were willing to pay for it and development was less TSO sensitive. In a message dated 3/22/2016

Re: CSVFETCH exit

On 03/22/2016 07:39 AM, Peter Relson wrote: Will a "fetch" of a CLIST or REXX be caught by this exit? No. Contents Supervisor (and hence this exit) deals with load modules and program objects. Peter Relson z/OS Core Technology Design Thanks for the quick reply to this. And I kinda had a

Re: CSVFETCH exit

Peter Relson wrote: >>Will a "fetch" of a CLIST or REXX be caught by this exit? >No. Contents Supervisor (and hence this exit) deals with load modules and >program objects. Thanks for your clarification. Interpreted REXX and CLIST will not be caught, but I believe *compiled* REXX programs

Re: CSVFETCH exit

>Will a "fetch" of a CLIST or REXX be caught by this exit? No. Contents Supervisor (and hence this exit) deals with load modules and program objects. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe /

Re: CSVFETCH exit

I have a different question relative to this exit. I've been looking for doc on line and have found two manuals that have CSVFETCH as an exit point defined, and one has the parm area info. Peter did a presentation last week, and unfortunately for me, I had a hard conflict and couldn't

Re: CSVFETCH exit

On Tue, 16 Feb 2016 19:17:10 +, Gibney, David Allen,Jr wrote: >I am finding this interesting. One thing I think you are missing was the >advisability >to use STMG/LMG to save and restore all 64 bits of the registers. Not a lot of >stuff >running above the bar as yet, but it will be there

Re: CSVFETCH exit

, February 16, 2016 2:21 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit On Tue, 16 Feb 2016 19:11:38 +, Leonardo Vaz wrote: >I see. In the case of CSVFETCH there is a 1024-byte work-area passed, >so no getmain should be needed, in this case, STM should be the best option

Re: CSVFETCH exit

On Tue, 16 Feb 2016 19:11:38 +, Leonardo Vaz wrote: >I see. In the case of CSVFETCH there is a 1024-byte work-area passed, so no >getmain should be needed, in this case, STM should be the best option? You are passed a 144-byte save area, so I would use STMG to save the registers in F4SA

Re: CSVFETCH exit

m: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Leonardo Vaz > Sent: Tuesday, February 16, 2016 11:12 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: CSVFETCH exit > > I see. In the case of CSVFETCH there is a 1024-byte work-area passed, so no &g

Re: CSVFETCH exit

-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit I see. In the case of CSVFETCH there is a 1024-byte work-area passed, so no getmain should be needed, in this case, STM should be the best option? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU

Re: CSVFETCH exit

in those other overheads, which is faster? I don't know >as >I haven't set up the tests to validly compare the different methods possible. >I >have seen several different ways to avoid the GETMAIN/FREEMAIN overheads. The CSVFETCH exit is passed a 1K work area, likely eliminating th

Re: CSVFETCH exit

, February 16, 2016 1:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit BAKR/PR does take a lot more time then STM/LM, but most times you can't just use STM/LM, you also have a GETMAIN/FREEMAIN for a register save area and other setup/restore things to do. So, once you factor

Re: CSVFETCH exit

...@syncsort.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Leonardo Vaz Sent: Tuesday, February 16, 2016 1:41 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit Well, I guess using the linkage stack is cleaner because

Re: CSVFETCH exit

To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit On Tue, 16 Feb 2016 16:52:03 +, Leonardo Vaz wrote: >I apologize if the question is silly, but I am wondering if for a >performance sensitive exit like this one I should use STM/LM instead of >BAKR/PR. I believe it's "chea

Re: CSVFETCH exit

On Tue, 16 Feb 2016 16:52:03 +, Leonardo Vaz wrote: >I apologize if the question is silly, but I am wondering if for a performance >sensitive >exit like this one I should use STM/LM instead of BAKR/PR. I believe it's >"cheaper" to >do STM/LM, bur "cleaner" to do BAKR, right? Why do you

Re: CSVFETCH exit

ssage- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Tom Brennan Sent: Friday, February 12, 2016 12:50 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit I agree, unsafe. But I could probably argue that just letting a system programmer logon is unsa

Re: CSVFETCH exit

Just FYI, there's a pretty blatant doc error of my causing in the z/OS 2.2 data. A doc APAR has been, or soon will be, provided. The doc says that the exit routine gets control with reg 1 pointing to a a 2 word area, the first word being the address of a work area that the exit routine can

Re: CSVFETCH exit

I noticed that, was going to open a PMR on Monday, thanks for reporting here. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Relson Sent: Saturday, February 13, 2016 11:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH

Re: CSVFETCH exit

: Thursday, February 11, 2016 7:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit I guess I missed the first post. It interests me, maybe because at one time (when I had not much to do) I wrote some SVC hooks that did similar monitoring, and crazy enough, my code actually made

Re: CSVFETCH exit

I agree, unsafe. But I could probably argue that just letting a system programmer logon is unsafe :) I had various checks to try to prevent the hooks from causing issues, including (if I remember correctly) using the LRA instruction to check for a valid address in ECSA prior to access. I

Re: CSVFETCH exit

On 2/11/2016 1:46 PM, Leonardo Vaz wrote: Am I the only one excited about this new exit on the discussion list or is my email not reaching the list at all? You are not the only one. This exit is the result of SHARE requirement SSMVSE11018 that I authored and submitted in July 2011: Title:

Re: CSVFETCH exit

ERV.UA.EDU Subject: CSVFETCH exit CSVFETCH seems to be a new exit in z/OS 2.2 which would allow monitoring of module fetching. http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa800/csvfetch01.htm?lang=en This seems pretty interesting, and something that can't be e

Re: CSVFETCH exit

Sounds like there are not that many users on zOS 2.2 just yet. Bill J Sent from my Verizon 4G LTE Smartphone -- Original message-- From: Pommier, Rex Date: Thu, Feb 11, 2016 7:09 PM To: IBM-MAIN@LISTSERV.UA.EDU; Subject:Re: CSVFETCH exit Leo, The list has been reached. Rex

Re: CSVFETCH exit

I will take the lack of response as a "no". Am I the only one excited about this new exit on the discussion list or is my email not reaching the list at all? Leo From: Leonardo Vaz Sent: Wednesday, February 10, 2016 5:01 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: CSVFETCH exit CSVF

Re: CSVFETCH exit

Leo, The list has been reached. Rex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Leonardo Vaz Sent: Thursday, February 11, 2016 3:47 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: CSVFETCH exit I will take the lack of response

Re: CSVFETCH exit

Wow, ‎thanks for the info and thanks for submitting the requirement. Very useful indeed. ‎ Leo Original Message From: Ed Jaffe Sent: Thursday, February 11, 2016 5:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: CSVFETCH exit On 2/11/2016 1:46 PM

Re: CSVFETCH exit

Thanks for letting me know Rex :) zLeo Original Message From: Pommier, Rex Sent: Thursday, February 11, 2016 5:13 PM To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: CSVFETCH exit Leo, The list has been reached. Rex -Original Message- From: IBM

Re: CSVFETCH exit

Brennan Sent: Thursday, February 11, 2016 7:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: CSVFETCH exit I guess I missed the first post. It interests me, maybe because at one time (when I had not much to do) I wrote some SVC hooks that did similar

CSVFETCH exit

CSVFETCH seems to be a new exit in z/OS 2.2 which would allow monitoring of module fetching. http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa800/csvfetch01.htm?lang=en This seems pretty interesting, and something that can't be easily done another way. Has anyone