Re: Re: MVT COBOL under MVS3.8j.
| Newsgroups | gmane.comp.emulators.hercules390.mvs |
|---|---|
| Message-ID | <[email protected]> |
Joe, Yep that was a typo on my part. The VER does verify for phase 4 as you said. The real problem is related to the GETALL not using any MASTAM but the first or second. By just forcing the XREF phase to not acquire a third is as Pepe calls it a hack but it does work in at least a few instances. There is one place the MVT/PCP vs MVS is tested and that is related to memory acquisition in phase 1 during initialization. There if running on MVS storage amounts are rounded to 2K boundaries. I think this has to do with the merging of MASTAMs if they are contiguous. Maybe changing the rounding to 4K for MVS might allow the merging to occur and prevent the additional MASTAM from actually occurring. That would be an interesting zap to test. The problem is other GETMAINs that implicitly occur after the first MASTAM GETMAIN "fragment" storage such that a third MASTAM won't be adjacent to prior MASTAMs. I did try to force XREF to use the third MASTAM but that caused a branch to TBERR4 from one of the other places in the code. Dave