| Newsgroups |
gmane.comp.emulators.hercules390.mvs |
| Message-ID |
<[email protected]> |
On Wed, 11 Sep 2019, Joe Monk [email protected] [H390-MVS] wrote:
> "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
>
Probably while furious testing I coded some wrong size parameter ;-(
But this time:
*STATISTICS* SOURCE RECORDS = 68 DATA DIVISION STATEMENTS =
11 PROCEDURE DIVISION STATEMENTS = 21
*OPTIONS IN EFFECT* SIZE = 1024000 BUF = 512000 LINECNT = 57
SPACE1, FLAGW, SEQ, SOURCE
*OPTIONS IN EFFECT* NODMAP, NOPMAP, NOCLIST, SUPMAP, XREF, LOAD,
NODECK, APOST, NOTRUNC, LIB, NOVERB
*OPTIONS IN EFFECT* ZWB
4
CROSS-REFERENCE DICTIONARY
5
IKF0030I-D FRAGMENTED CORE. RUN IN LARGER SIZE REGION. COMPILATION
ABANDONED.
I think I coded what Joe suggested:
REGION=2048K
EXEC PGM=IKFCBL00,PARM='LIB,SIZE=1024000,BUF=512000,XREF'
As you can see, same error. It doesn't seem to matter which
values I code, at least for XREF.
It always FAIL with the same error.
Peppe.