Thanks Peter. They re-IPLed that LPAR on Sunday so that cleaned everything
up.
Regards,
John.
On 17 April 2012 17:31, Peter Relson rel...@us.ibm.com wrote:
Does anyone know if there is a way of finding out which address spaces
are using these previous versions with the non-zero use counts ?
Does anyone know if there is a way of finding out which address spaces
are using these previous versions with the non-zero use counts ?
Brute force: you could schedule an SRB to every address space and,
for every task in that address space, with appropriate serialization, run
the TCBLLS queue
We have a standard LPA module which is widely used. It's been changed quite
a few times recently. Here's the output of an LPA query utility:
SDSF OUTPUT DISPLAY T7516FBD JOB35267
COMMAND INPUT ===
* TOP
CSVLPAQ Parameter: QUERY SISX100
LPA query for SISX100
Regarding LPMEASVC and LpmeaxSvcnum (and LPMEAESVC and LpmeaxESvcrnum)::
We hope to document this functionality in a future release, after it has
gone through the proper level of testing (which as of now it has not).
Having it visible in the mapping without a caution that it is, for now, for
IBM
On Tue, 10 Feb 2009 06:50:06 +0100, Dr. Stephen Fedtke
max_mainframe_...@fedtke.com wrote:
hi,
does anybody know the function of this bit (dynamic LPA module handling),
and how to apply it:
+LPMEASVC EQU X'80' This entry is an SVC. The SVC number
hi,
does anybody know the function of this bit (dynamic LPA module handling),
and how to apply it:
+LPMEASVC EQU X'80' This entry is an SVC. The SVC number is in
+ LpmeaxSvcnum.
does its usage prevent any removal, or similar
Are the SYS1.PARMLIB(PROGxx) entries:
LPA ADD DSNAME(SYS1.MVS.EXITLOAD) MODNAME(...)
always processed before:
EXIT ADD EXITNAME(SYS.name) MODNAME(...)
during z/OS initialization?
All statements in a single parmlib PROGxx parmlib member are processed to
completion in the order they are seen.
In Don Ault's append, change exit to exit routine in the words. It is
MODULE or MODNAME in the command syntax.
And for IEFACTRT, as Barbara Nitz pointed out, the actual exit name is one
of SYS.IEFACTRT, SYSSTC.IEFACTRT, etc depending upon your SMF
specifications.
Peter Relson
z/OS Core
A question related to the topic being discussed:
Are the SYS1.PARMLIB(PROGxx) entries:
LPA ADD DSNAME(SYS1.MVS.EXITLOAD) MODNAME(...)
always processed before:
EXIT ADD EXITNAME(SYS.name) MODNAME(...)
during z/OS initialization?
Or, are they processed in as specified via PARMLIB
re: ms. Nitz's last contribution (i don't this will work )
actually, i think it does work:
i'm running z/os 14, and my smfprm00 reads (in part):
exits(iefactrt,iefusi, )
and when i do a d prog.exit the output is (in part):
sys.iefactrt
sys.iefusi.
and both of
exits(iefactrt,iefusi, )
and when i do a d prog.exit the output is (in part):
sys.iefactrt
sys.iefusi .
Exactly. *SYS*.iefactrt, not just *IEFACTRT* as Don specified. This is the
most common mistake one makes when dealing with replacing an SMF exit (I've
been down that road, myself).
Replacing a system exit:
First get your new exit into the active LPA. If it resides in a different
data set, then specify that data set.
SETPROG LPA,ADD,MODNAME=modname,DSNAME=SYS1.LPALIB
Then delete the old exit:
SETPROG EXIT DELETE EXITNAME(IEFACTRT) MODULE(modname)
Then add the exit back,
Barbara - thanks for taking the time to respond.
And how do they do it these days? Do they use the interfaces CSVDYNLPA and
CSVDYNEXIT (or whatever that one's called)? Or do they do it the way it
was
done before these interfaces became available - by altering addresses in
MVS
control blocks?
I
SETPROG EXIT DELETE EXITNAME(IEFACTRT) MODULE(modname)
Then add the exit back, which will pick up the new one you put in LPA:
SETPROG EXIT ADD EXITNAME(IEFACTRT) MODULE(modname) DSNAME
(dataset-where-it-now-lives)
I don't think that this will work. The exit name is normally not iefactrt,
it is
We recently attempted to replace our IEFACTRT routine in our production
platform using TMON..
Well, as luck would have it, our system appeared to freeze up. We had been
able to do this replace function
successfully on our test LPAR.
Anyone care to comment on this type of a replacement in dynamic
recently attempted to replace our IEFACTRT routine in our production
platform using TMON..
Well, as luck would have it, our system appeared to freeze up. We had been
able to do this replace function
successfully on our test LPAR.
Anyone care to comment on this type of a replacement in dynamic LPA
The OEM product TMON for MVS has a utility to dynamically load or replace
an exit(LPA module)
John Norgauer
University of California Davis Medical Center
2315 Stockton Blvd
ASB 1300
Sacramento, Ca 95817
916-734-0536
SYSTEMS PROGRAMMING.. Guilty, until proven innocent !! JN 2004
? For which types of work (TSO, STC,
JES)?
Anyone care to comment on this type of a replacement in dynamic LPA...
hazards, potential problems?
As long as I have used the MVS commands utilizing the dynamic interfaces I
never had any problem (other than code problems in the exit itself - which
has nothing
18 matches
Mail list logo
