On 12/21/2018 9:50 AM, Mike Baldwin wrote:
(X) <== LIKE button
Cool answer! (Did not try it at home)
It reminds me of back in my Waterloony days, experiments with unforeseen
consequences.
At worst, only temporarily revoked, not fired! (being a student)
Haha! I tried it just to be sure it ha
(X) <== LIKE button
Cool answer! (Did not try it at home)
It reminds me of back in my Waterloony days, experiments with unforeseen
consequences.
At worst, only temporarily revoked, not fired! (being a student)
Thanks,
Mike Baldwin
Cartagena Software Limited
Markham, Ontario, Canada
https://car
On 11/26/2018 3:14 AM, Sean Gleann wrote:
... Bumping the parm value to
1G was enough to get the test through, but I'm still arguing for all such
limits to be removed - "let the system sort itself out, don't try and
'second guess' things..."
Haha! Remove all memory constraints and take bets to
On 11/21/2018 11:39 AM, Jackson, Rob wrote:
This is what standalone restore is for, Sean. But if you don't have one built,
you could try this: http://www.cbttape.org/~jjaeger/zzsa.html.
I've used it before but not on anything more recent than a z10. If it will
IPL, you can find your IEFUSI
_
> From: IBM Mainframe Discussion List on behalf
> of Sean Gleann
> Sent: Monday, November 26, 2018 6:14 AM
> To: IBM-MAIN@listserv.ua.edu
> Subject: Re: Region size for OMVS tasks
>
> Hello Peter
> Problem solved!
> Your idea(s) regar
lf of
Sean Gleann
Sent: Monday, November 26, 2018 6:14 AM
To: IBM-MAIN@listserv.ua.edu
Subject: Re: Region size for OMVS tasks
Hello Peter
Problem solved!
Your idea(s) regarding the SMF30 record analysis eventually led me to
reproducing the test environment used by the developer so that I could ru
Sean Gleann wrote:
>Hello Peter
>Problem solved!
Excellent. Thanks to Peter Hunkeler.
>Your idea(s) regarding the SMF30 record analysis eventually led me to
>reproducing the test environment used by the developer so that I could run the
>tests myself.
This is what IBM (and other vendors) al
Hello Peter
Problem solved!
Your idea(s) regarding the SMF30 record analysis eventually led me to
reproducing the test environment used by the developer so that I could run
the tests myself.
One look at the command being used showed what the problem was - there was
a parametrised upper limit of 768
One more thought: Look At he SMF30 records for one such session. You should get
an idea of what‘s going on in that process and its child processes. There will
be one record for each command, i.e. when a fork()ed or spawd()ed process
ends, and at each exec(). You may find the one program eatin
Peter, Mike: Yes, I remember Peter pointing at Mark's page, but for some
reason I moved on past that to some other line of enquiry.
I've now done what you said, and the results from REXXSTOR in PuTTY are:
V I R T U A LS T O R A G EU S A G E
---
Peter, Mike: Yes, I remember Peter pointing at Mark's page, but for some
reason I moved on past that to some other line of enquiry.
I've now done what you said, and the results from REXXSTOR in PuTTY are:
V I R T U A LS T O R A G EU S A G E
---
>http://mzelden.com/mvsutil.html
Yep, this is the invaluable link. As I wrote before, try the REXXSTOR rexx
found there and run it in a) TSO, b) TSO -> OMVS (shell under TSO), c) putty
(shell vie TCP/IP). If possible run in the environment where you‘re getting the
out of stroage, and ru
http://mzelden.com/mvsutil.html
On Thu, Nov 22, 2018 at 2:43 AM Sean Gleann wrote:
>
> Thanks to all that have responded - we're back and running again, but not
> due to any work on my part.
>
>
>
> My description of the failed system was not complete, for fear of confusing
> the issue - it is a
Thanks to all that have responded - we're back and running again, but not
due to any work on my part.
My description of the failed system was not complete, for fear of confusing
the issue - it is a guest z/OS under z/VM that is supplied by a.n. other
party. I contacted them and the bad IEFUSI wa
Just recognized that the parameter STATE=INACTIVE was missing in my
previous post
SETPROG EXIT,MODIFY,EXITNAME=SYS.IEFUSI,MODNAME=IEFUSI,STATE=INACTIVE
--
Peter Hunkeler
--
For IBM-MAIN subscribe / signoff / archive access i
Trying to follow-up on the stuff that Peter has suggested, I'm still
chasing that elusive '54M' - Who sets it? Where is it set? How can I
override it?
It seems you missed this statement in my first reply in this thread:
IEFUSI will gin control in the BPXAS address space before the UNIX process
This is what standalone restore is for, Sean. But if you don't have one built,
you could try this: http://www.cbttape.org/~jjaeger/zzsa.html.
I've used it before but not on anything more recent than a z10. If it will
IPL, you can find your IEFUSI module and make it like IEFBR14.
First Tennes
essage -
From: "Sean Gleann"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, November 21, 2018 10:56:00 AM
Subject: Re: Region size for OMVS tasks
Thanks, Allan, but I can't get any tasks of any nature started - no VTAM, no
TSO, so no copy is possible.
(I'll squirrel that
leann"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Wednesday, November 21, 2018 10:56:00 AM
Subject: Re: Region size for OMVS tasks
Thanks, Allan, but I can't get any tasks of any nature started - no VTAM,
no TSO, so no copy is possible.
(I'll squirrel that 'SYS1.AOSB3' i
have customized IEFUSI, reassemble you customized exit.
> IF not, copy SYS1.AOSB3 to SYS1.LLPALIB and re-ipl.
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Sean Gleann
> Sent: Wednesday, November 21, 2018 10:20 AM
> To: IBM-MAIN@LISTSER
size for OMVS tasks
Trying to follow-up on the stuff that Peter has suggested, I'm still chasing
that elusive '54M' - Who sets it? Where is it set? How can I override it?
So, I created an IEFUSI that, whatever size is requested, whether it be below,
above or MEMLIMIT, you get
Trying to follow-up on the stuff that Peter has suggested, I'm still
chasing that elusive '54M' - Who sets it? Where is it set? How can I
override it?
So, I created an IEFUSI that, whatever size is requested, whether it be
below, above or MEMLIMIT, you get '0M'.
Which, I agree, is probably a bit ex
Where did you get all this from? Is it documented somewhere, or is it something
you've 'soaked up through your fingertips' over the years?
So I went back to the FMs. For any question of kind "How does that UNIX
service behave regarding MVS resources, attributes, etc.", I always read
what the
For an LPAR, you should have enough dasd to back real memory. To take
a system dump, you need to copy the memory and the paging. So you
need 3X the amount of real memory. If paging on any LPAR is over 30%,
you should be reducing usage or adding space.
On Tue, Nov 20, 2018 at 6:02 AM Peter Hunkel
>Peter: I'm still trying to fully assimilate what you've said - very
detailed & complete. Where did you get all this from? Is it documented
somewhere, or is it something you've 'soaked up through your fingertips'
over the years?
I pasted one section which is one part of the „documented some
Thanks for the responses, gents
Carmen: yes - that is what I see in the manual
Jim: Thanks for the update - it would appear that the manual requires an
update
Peter: I'm still trying to fully assimilate what you've said - very
detailed & complete. Where did you get all this from? Is it documented
s
From fading memory, so things might have change slightly, but I think most of
this still applies.
The REGION and MEMLIMIT values that apply to z/OS UNIX processes depend on how
and where the process is running:
a) BATCH jobs, started tasks, TSO user sessions
A program run as batch job, star
gt; Date: 11/19/2018 04:28 PM
> Subject: Re: Region size for OMVS tasks
> Sent by: "IBM Mainframe Discussion List"
>
> Interesting stuff, here...
> Before making any changes, analysis of the type-30 data showed
> SMF30RGN=56623104 (54M) and SMF30MES - the source of MEMLIT
ot;Sean Gleann"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday, November 19, 2018 10:12:18 AM
Subject: Re: Region size for OMVS tasks
Interesting stuff, here...
Before making any changes, analysis of the type-30 data showed
SMF30RGN=56623104 (54M) and SMF30MES - the source of MEMLIT -
Interesting stuff, here...
Before making any changes, analysis of the type-30 data showed
SMF30RGN=56623104 (54M) and SMF30MES - the source of MEMLIT - as '1', which
apparently means that MEMLIMIT is set by SMF. Also, SMF30MEM was coming
back as 1280M - the same as the MEMLIMIT in SMFPRMxx. So far,
Sean Gleann wrote:
>None of the suggestions so far check out, unfortunately.
>David: all limits associated with memory come back as 'Unlimited'
>Carmen: Yes, I've got MEMLIMIT(1280M) specified
>Alan: BPXPRMxx MAXASSIZE is set to 2G, and the OMVS segment ASSIZEMAX and
>MEMLIMT values are not specif
k ASSIZEMAX and MEMLIMT in the OMVS segment for the UID in
> question
>
> HTH,
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Carmen Vitullo
> Sent: Monday, November 19, 2018 8:03 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Regi
size for OMVS tasks
do you have a MEMLIMIT in the SMFPRMxx member ?
Carmen Vitullo
- Original Message -
From: "Sean Gleann"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday, November 19, 2018 7:51:04 AM
Subject: Region size for OMVS tasks
We have a problem here that is proving
do you have a MEMLIMIT in the SMFPRMxx member ?
Carmen Vitullo
- Original Message -
From: "Sean Gleann"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Monday, November 19, 2018 7:51:04 AM
Subject: Region size for OMVS tasks
We have a problem here that is proving to be … um...
] Region size for OMVS tasks
We have a problem here that is proving to be … um... "resistant to
analysis" & I wonder if anyone on this list might be able to help.
Most of our developers submit work to the system from a PuTTY session, that
will result in multiple OMVS tasks being fork()e
We have a problem here that is proving to be … um... "resistant to
analysis" & I wonder if anyone on this list might be able to help.
Most of our developers submit work to the system from a PuTTY session, that
will result in multiple OMVS tasks being fork()ed or spawn()ed. Of late,
such work has b
36 matches
Mail list logo
