On 2016-07-22, at 15:03, Jesse 1 Robinson wrote:
>
> ... Surely I would like a DSN date/time stamp to reflect execution date/time,
> not submit date/time, but the latter is what I get. More uproar at the
> convention.
>
At what point does JES3 rear its ugly head. Data set names must be
fixed
Besides all the things that Bill mentioned, which as far as I see can
be activated by LE run time options, there is one additional technique
which requires some input into the ENV string (environment), which is
also a runtime parameter; you can replace the normal LE heap manager
by the so called "
On 2016-07-23 02:38, Peter Hunkeler wrote:
It will be cleared to X'00' by MVS.
YMMV on that...
"When you obtain storage, the system clears the requested storage to
zeros if you obtain either:
8192 bytes or more from a pageable, private storage subpool.
4096 bytes or more from a page
TYPRUN=JCLHOLD gives the same result as SYSAFF to an inactive member:
TIMETEST JOB03653 TSOSKIP 10 * LOCAL 27 X2 <-- inactive member with JCLHOLD
TIMETEST JOB03829 TSOSKIP 5 * LOCAL 27 X0 <-- active member with no HOLD
Neither job goes through conversion, hence '*' in the class column. Neith
Here's the link I failed to include, the suggested reading:
http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ceeam00/clsthp.htm
An overview, but, for the willing reader, follow the references and go as deep
as you want.
LE can report on storage used, and storage (like he
>SDSF display
>
>DFHSMDFHSMDFHSMSTC06087 DFHSM
>IEESYSAS DSSFRB01 IEFPROC STC06108 #STC
>
>but the priority of the IEESYSAS is lower than the one of DFHSM
>
>SDSF display
>
>DFHSM24 SYSTEM SYSSTC
>IEESYSAS 24 STC STCLOW
Have you tried to classify those address spaces i
Bill,thanks for your answer. I concur with everything you wrote. I don't know
what they intended to do with this if it was available. I doubt they want to do
their own storage management. I seem to remember they talked about "statistics"
or "bookkeeping", but I'll have to ask for more details.
A
I've documented this some time ago for my own use and
for the use of a customer of mine, and it is not very complicated.
But I don't recall the details at the moment.
I wrote a routine, too, that writes a report of all allocated areas,
if you give one valid address to it; that is possible, becaus
There is some evidence that the "control information" is stored in the heap
itself (see the Usage Notes for "CEEFRST—Free heap storage") and by
implication associated directly with the storage allocated. However, it is not
documented, and working it out through inspection would be pointless bey
