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]>
On Fri, 13 Sep 2019, 'Shelby Beach' [email protected] [H390-MVS] wrote:

> Whoa, this gives me an idea... Peppe, why don't you try running the compiler
> on MVS as V=R.
>
> Shelby

I've to admit I never run in V=R under MVS3.8j.

From my SYSGEN JCL I've:

CTLPG    CTRLPROG ASCII=INCLUDE,     ASCII TRANSLATE ROUTINE           C05080003
                OPTIONS=(RER,         REDUCED ERROR RECOVERY            C05090003
                DEVSTAT,              OFFLINE NOT READY DEVICES AT IPL  C05100003
                RDE,                  LOGREC DATA EXTRACTOR             C05110003
                BLDL),                BLDL IN FIXED STORAGE             C05120003
                SQA=5,                # 64K ADDITIONAL SQA BLOCKS       C05130003
                REAL=128,             # 1K V=R BLOCKS                   C05140003
                STORAGE=0,            DETERMINE MAX REAL DYNAMICALLY    C05150003
                WARN=0,               IGNORE POWER WARN FEATURE         C05160003
                ACRCODE=YES,          ALTERNATE PROCESSOR RECOVERY      C05170003
                APFLIB=(SYS1.VTAMLIB,PEP380, VTAM REQUIRES              C05180003
                SYS1.INDMAC,PEP380),         IND=YES REQUIRES           C05190003
                CSA=3072,             # 1K BLOCKS CSA                   C05200003
                VRREGN=64,            DEFAULT V=R REGION                C05210003
                TZ=(E,2)              TWO HOUR WEST OF GMT              05220003

so I bet I can run in V=R up to 128K, with the default
defined as 64K in my IEASYSxx:

VRREGN=64           64 BLOCKS OF V=R ALLOCATED TO VRREGN

So, I can run in a V=R region up to 128K, coding VRREGN=128.

Tested, it works:

//DUMMY    JOB (001),'PEPPE',MSGLEVEL=(1,1),ADDRSPC=REAL,REGION=128K,
//         MSGCLASS=X,CLASS=A,NOTIFY=PEPPE
//STEP EXEC  PGM=IEFBR14

But, unfortunately, the COBOL compiler doesn't seem happy to
run in a such a small region.

I tried some sample values for SIZE,BUF, I always end with RC=0016,
without XREF, with the message:

IKF0015I-C BUF PARM TOO SMALL FOR DD-CARD BLKSIZES - COMPILATION ABANDONED.

Moseley, on one of his notes, wrote:

The MVT COBOL compiler installs with a buffer default that is too small to 
handle blocked datasets for input (COBOL source read from the SYSIN DD) or 
output (object modules written to SYSLIN).  In order to read or write 
blocked datasets, or to copy source code from a library dataset, you will 
need to include a additional parameters to the compiler:

     PARM='SIZE=2048K,BUF=1024K'

So, I guess, I would need a new SYSGEN to test the COBOL compiler
in a V=R region larger than 128K, isn't it?

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.