Discussion:
[hercules-os380] iewfetch
kerravon86@yahoo.com.au [hercules-os380]
2018-06-12 13:25:00 UTC
Permalink
I'm mulling over making iewfetch the first
routine that is rewritten in C, to provide
proof of concept.

The new C iewfetch will be a drop-in replacement
for MVS380FT (which replaces the normal
iewfetch on MVS/380).

I would like to know if iewfetch is the place that
would need to be changed if I wanted to load
a PE-format load module (ie an IEBCOPY
unload that has RDW + data stored in a
RECFM=U dataset). As well as keeping the
existing load module format working of course.

Thanks. Paul.
kerravon86@yahoo.com.au [hercules-os380]
2018-06-12 14:09:06 UTC
Permalink
Post by ***@yahoo.com.au [hercules-os380]
I would like to know if iewfetch is the place that
would need to be changed if I wanted to load
I'd also like to know if the new IEWFETCH could
potentially reside above the 16 MiB line, rather
than taking up a large amount of LPA. Obviously
the replacement C code is going to be
AM-anything or at least AM32.

I've previously mentioned my desire for a pivot
point where each address space gets its own
memory. Maybe what we need is a pivot range,
so that memory common to all address spaces
can reside both above and below the line.

BFN. Paul.
Tony Harminc tharminc@gmail.com [hercules-os380]
2018-06-12 15:22:47 UTC
Permalink
Post by ***@yahoo.com.au [hercules-os380]
I've previously mentioned my desire for a pivot
point where each address space gets its own
memory. Maybe what we need is a pivot range,
so that memory common to all address spaces
can reside both above and below the line.
Sort of like, um, MVS/XA...?

Tony H.
kerravon86@yahoo.com.au [hercules-os380]
2018-06-12 15:43:12 UTC
Permalink
Post by Tony Harminc ***@gmail.com [hercules-os380]
Post by ***@yahoo.com.au [hercules-os380]
I've previously mentioned my desire for a pivot
point where each address space gets its own
memory. Maybe what we need is a pivot range,
so that memory common to all address spaces
can reside both above and below the line.
Sort of like, um, MVS/XA...?
Well yes, the goal is to provide some MVS/XA
functionality, but the pivoting would be done in
Hercules/380, as part of the "separate memory"
design.

I think we should just construct a table with
the MiB number and index into that to see if
we need to fetch the memory from "separate
memory" or from the initial memory block.

BFN. Paul.
Gerhard Postpischil gerhardp@charter.net [hercules-os380]
2018-06-14 15:50:08 UTC
Permalink
Post by ***@yahoo.com.au [hercules-os380]
I would like to know if iewfetch is the place that
would need to be changed if I wanted to load
a PE-format load module (ie an IEBCOPY
unload that has RDW + data stored in a
RECFM=U dataset). As well as keeping the
existing load module format working of course.
IEWFETCH is probably the worst place to change, because it is downstream
from the analysis and load process. It makes more sense to bite the
bullet and do it correctly to begin with.

Gerhard Postpischil
Bradford, VT

---
This email has been checked for viruses by AVG.
https://www.avg.com
kerravon86@yahoo.com.au [hercules-os380]
2018-06-14 17:06:29 UTC
Permalink
Post by Gerhard Postpischil ***@charter.net [hercules-os380]
Post by ***@yahoo.com.au [hercules-os380]
I would like to know if iewfetch is the place that
would need to be changed if I wanted to load
a PE-format load module (ie an IEBCOPY
unload that has RDW + data stored in a
RECFM=U dataset). As well as keeping the
existing load module format working of course.
IEWFETCH is probably the worst place to change, because it is downstream
from the analysis and load process. It makes more sense to bite the
bullet and do it correctly to begin with.
1. Which is the module that loads a module
into memory and then applies all the address
corrections?

2. What does IEWFETCH do?

Thanks. Paul.
Gerhard Postpischil gerhardp@charter.net [hercules-os380]
2018-06-14 19:49:40 UTC
Permalink
Post by ***@yahoo.com.au [hercules-os380]
1. Which is the module that loads a module
into memory and then applies all the address
corrections?
IEWFETCH is not the module that gets the directory information, decides
on AM (and RM), etc.. You specifically asked for support for other than
MVS format modules. By the time IEWFETCH gets control, it may be too
late to accommodate other formats.

Gerhard Postpischil
Bradford, VT

---
This email has been checked for viruses by AVG.
https://www.avg.com
kerravon86@yahoo.com.au [hercules-os380]
2018-06-14 22:11:38 UTC
Permalink
Post by Gerhard Postpischil ***@charter.net [hercules-os380]
Post by ***@yahoo.com.au [hercules-os380]
1. Which is the module that loads a module
into memory and then applies all the address
corrections?
IEWFETCH is not the module that gets the directory information, decides
on AM (and RM), etc.. You specifically asked for support for other than
MVS format modules. By the time IEWFETCH gets control, it may be too
late to accommodate other formats.
So which module do you think needs to be
changed to support non-standard modules?

And what role does IEWFETCH play?

Thanks. Paul.
Gerhard Postpischil gerhardp@charter.net [hercules-os380]
2018-06-15 13:50:59 UTC
Permalink
On 6/14/2018 6:11 PM, ***@yahoo.com.au [hercules-os380] wrote:>
So which module do you think needs to be> changed to support
non-standard modules?
Try IEAVLK01, possibly IEAVLK00, etc. in MVSSRC.SYM101.F19 - last time I
looked at the code was with regard to setting AM31.

Gerhard Postpischil
Bradford, VT

---
This email has been checked for viruses by AVG.
https://www.avg.com

Loading...