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 Sat, 14 Sep 2019, Joe Monk [email protected] [H390-MVS] wrote:

> "But what the hell is the compiler doing which OS/VS2
> refrain to execute in V=R?"
>
> I think it probably revolves around this code :)
>
> ST    R6,GETTABLE+NX24                                         45060021
>         LR    R0,R6
> 45080021
>         GETMAIN R,LV=(0)
>
> Thats an unconditional GETMAIN for memory? If memory isnt available, the
> system waits right?
>
> Joe
Yep, thanks Joe, problem was 128K is too much ;-)

Now:

/COB1     JOB (001),'PEPPE',MSGLEVEL=(1,1),REGION=108K,ADDRSPC=REAL,
/         MSGCLASS=X,CLASS=A,NOTIFY=PEPPE
//COB  EXEC  PGM=IKFCBL00,PARM='XREF'

and we are back to RC=0016 :

*OPTIONS IN EFFECT*     SIZE =   81920  BUF =    2768 
IKF0030I-D FRAGMENTED CORE. RUN IN LARGER SIZE REGION.  COMPILATION ABANDONED.

running V=R.

So, I think we have an answer.

It doesn't matter V=V or V=R under MVS3.8j.

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.