List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Phil Smith III
Sent: Friday, July 12, 2019 7:15 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
And.simply adding:
FREEPOOL ((4)) Release the buffers
Fixed it-thanks again. As I said before, I woul
uel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List on behalf
of Jon Perryman
Sent: Thursday, July 11, 2019 12:17 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
I agree with Mike
Subject: Re: Probably dumb assembler question
And.simply adding:
FREEPOOL ((4)) Release the buffers
Fixed it-thanks again. As I said before, I would NOT have tripped over this
any time soon from reading the doc!
.phsiii
again, I'm in
leave-things-alone-as-much-as-possible mode. But I do appreciate it and will
save the wisdom in case I need it later.
From: Phil Smith III [mailto:li...@akphs.com]
Sent: Friday, July 12, 2019 10:15 AM
To: 'IBM Mainframe Assembler List'
Subject: RE: Probabl
And.simply adding:
FREEPOOL ((4)) Release the buffers
Fixed it-thanks again. As I said before, I would NOT have tripped over this any
time soon from reading the doc!
.phsiii
Is the 'XDCBL ' value a multiple of 8? The STORAGE OBTAIN will round up to
multiple of 8; the STORAGE RELEASE might be using the actual 'XDCBL' length.
Why don't you get a dump of the 878 and try to debug? Maybe you can find 1900
chunks of the same storage eye-catchers.
) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List on behalf
of Keith Moe
Sent: Thursday, July 11, 2019 12:17 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
If the same DCB is closed and reopened, the 24-bit b
: Probably dumb assembler question
I agree with Mike that your storage leak may be somewhere else. When did
freepool become a requirement? I don't see anything in the code referencing a
buffer. If it is dynamically using a buffer pool, then the buffers should be
returned to the pool upon clos
11, 2019 12:17 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
I agree with Mike that your storage leak may be somewhere else. When did
freepool become a requirement? I don't see anything in the code referencing a
buffer. If it is dynamically using a b
Just to be clear. When a DCBE with RMODE31 specified, QSAM does free the
buffers at CLOSE. This has only been available for maybe 20-30 years.
It's so hard to keep up with changing technology.
sas
On Thu, Jul 11, 2019 at 8:18 AM Mike Shaw wrote:
> On Thu, Jul 11, 2019 at 1:46 AM Jon Perryman
On Thu, Jul 11, 2019 at 1:46 AM Jon Perryman wrote:
> <...snip> When did freepool become a requirement?<.snip..>
QSAM does not free the buffer pool. The user has to issue a FREEPOOL;
AFAIK, it has been that way since OS/MVT. You can get away without doing a
FREEPOOL until you issue thousands of
I would restructure to open/close the DCB once
Here using -ve value to indicate open has failed, or could use flags to track
DCB status
* Message is in WORKMSG on arrival here
LTR4,MYDCB@ Get DCB address
BM WRITTEN Previous open failed, skip
I agree with Mike that your storage leak may be somewhere else. When did
freepool become a requirement? I don't see anything in the code referencing a
buffer. If it is dynamically using a buffer pool, then the buffers should be
returned to the pool upon close and the next open should reuse that
: Probably dumb assembler question
Charles Mills (and others) wrote about using FREEPOOL and/or RMODE31=BUFF. I
will dig into those.
To Mike Hochee: I can't leave the file open. The calls to the API are atomic
and have no persistence, so I don't know if this is one invocation of many,
[mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On
Behalf Of Steve Smith
Sent: Wednesday, July 10, 2019 4:27 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
Frankly, after 1900 errors, maybe it is time to die anyway. OPEN/PUT/CLOSE
for each message is horrendous overhead.
Mr
s below the line utterly accounts for the 878.
>
> Charles
>
>
> -Original Message-
> From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU
> ]
> On Behalf Of Mike Hochee
> Sent: Wednesday, July 10, 2019 2:51 PM
> To: ASSEMBLER-LIST@LIST
Charles Mills (and others) wrote about using FREEPOOL and/or RMODE31=BUFF. I
will dig into those.
To Mike Hochee: I can't leave the file open. The calls to the API are atomic
and have no persistence, so I don't know if this is one invocation of many, or
the one and only. The good news is that
:51 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
I would also probably start to wonder about a memory leak in the code that
drives this little routine.
-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
Hi Phil,
Interesting question.
My approach would be to not answer it at all, if possible. (although I would
like to understand the underlying cause of the 878) If your execution
requirements/context accommodate, just obtain
@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
Hi Phil,
Interesting question.
My approach would be to not answer it at all, if possible. (although I would
like to understand the underlying cause of the 878) If your execution
requirements/context accommodate, just obtain the
@LISTSERV.UGA.EDU]
On Behalf Of Phil Smith III
Sent: Wednesday, July 10, 2019 1:48 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Probably dumb assembler question
Before I try to make the code below runnable as a standalone program, maybe
someone can suggest what's going on here. I have a program (an API)
Sent: Wednesday, July 10, 2019 2:12 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Probably dumb assembler question
Try FREEPOOL XDCB before the CLOSE.
Or ... a DCBE with RMODE31=BUFF will both do the FREEPOOL automatically and
get the buffers up above the line, where there is more storage.
Behalf Of Phil Smith III
Sent: Wednesday, July 10, 2019 1:48 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Probably dumb assembler question
Before I try to make the code below runnable as a standalone program, maybe
someone can suggest what's going on here. I have a program (an API) that may
wri
On Wed, 10 Jul 2019 at 16:48, Phil Smith III wrote:
> BUT it seems to eat storage. That is, if I run a program that calls the
> API repeatedly and invalidly, it writes the errors to SYSPRINT, but gets an
> S878 reason code 10 after 1900-odd iterations. I've tinkered, commenting
> out the PUT: no
: Wednesday, July 10, 2019 4:48 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Probably dumb assembler question
Before I try to make the code below runnable as a standalone program, maybe
someone can suggest what's going on here. I have a program (an API) that may
write to SYSPRINT (if there
Before I try to make the code below runnable as a standalone program, maybe
someone can suggest what's going on here. I have a program (an API) that may
write to SYSPRINT (if there's an error, and it hasn't been passed a buffer to
return the error message to the caller) using the following seque
27 matches
Mail list logo
