Re: MVT COBOL under MVS3.8j.

"Giuseppe Vitillaro giuseppe-yuD/ahkh7LvrZ44/[email protected] [H390-MVS]" <[email protected]>
Newsgroups gmane.comp.emulators.hercules390.mvs
Message-ID <[email protected]>
> 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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.