| Newsgroups |
gmane.comp.emulators.hercules390.mvs |
| Message-ID |
<CAPcd4G9OmG_q2s-8ipy+U7_fSOUkV0Zm6GmspAgnWycbejQNgg@mail.gmail.com> |
"Yep, I think I coded any possible value for REGION,
even values I didn't know, suggested from the IBM
manual GC28-6399-2 (by the way, an excellent manual,
it even review JCL/JES2 topics and a complete
reference for datasets definition in COBOL)."
Peppe ...
"COMPILATION: If the compiler is being executed--Under the MVT control
program of the System/360 Operating System, the REGION parameter, specified
as 86K bytes in the COBUC and COBUCLG cataloged procedures, becomes significant
(see the section "Using the Cataloged Procedures"). If the programmer
wishes to override this value, he can specify a region size in either the
JOB statement or in the EXEC statement of the compiler. *The size specified
should not be less than the value of SIZE in the PARM field of
the EXEC statement, **rounded to the next highest 2K multiple, plus 6K."*
I would try adjusting the SIZE parameter in the EXEC PARM field, i.e.
REGION =2048K, PARM="SIZE=1024000,BUF=512000,XREF,..."
Remember, the 360 had a core size of around 2MB. Since this is a MVT
compiler, Version 2 (not even version 4!!!!) there are probably some limits
as to what it can handle...
Joe
On Wed, Sep 11, 2019 at 4:17 AM Giuseppe Vitillaro giuseppe-yuD/ahkh7LvrZ44/[email protected]
[H390-MVS] <[email protected]> wrote:
>
>
> > As I said it has been like it since it was included in TK4 and with Jay..
> >
> > It is possible a fault with the compiler build/generation but as we do
> > not have the starter for it make some what difficult to fix despite have
> > the compiler sources - but these might have have been created from the
> > objects.
> >
> > I did play around with setting for region and memory but with zero
> > success and others reported the above facts.
> >
> > Hence my own use of the cobxref tool.
> > I did not know that it would not produce listing tables such as symbols
> > as I do not use them in debugging.
>
> Yep, I think I coded any possible value for REGION,
> even values I didn't know, suggested from the IBM
> manual GC28-6399-2 (by the way, an excellent manual,
> it even review JCL/JES2 topics and a complete
> reference for datasets definition in COBOL).
>
> Always the same error, as soon as XREF is requested.
>
> It looks like the compiler, when time to create
> the symbol table comes, needs to allocate memory
> for performing the task, but there is not any
> large enough contiguos area available in the job
> region.
>
> Mmm ... this is a COBOL compiler designed for MVT,
> isn't it?
>
> Is possible GETMAIN calls are different between
> MVS and MVT?
>
> Anyone used this compiler under MVT in our days?
>
> Peppe.
>
>