From: [email protected] <[email protected]> On Behalf Of Bernd Oppolzer via groups.io
Sent: 13 March 2022 09:20
To: [email protected]
Subject: Re: [h390-vm] COBOL compile error?
Hello Michael,
my guess is that the source file needs to be FIXED 80.
I wrote a small EXEC to convert such LRECL V files to LRECL F.
Don't have access to my VM machine at the moment,
but it goes like this:
two filedefs, INPUT with LRECL V, output with LRECL FIXED 80,
MOVEFILE INPUT OUTPUT
then rename to result to original
You could look at my Stanford Pascal Compiler sites, maybe you find the EXEC there:
HTH
kind regards
Bernd
?
?
Am 13.03.2022 um 10:01 schrieb Michael Grom:
Dear Group,
I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO) and thought I give COBOL a try, first, without?
the VSAM example. So I prepped a very small program and tried to compile. Before that, I linked to COBOL 191 and accessed the mini disk as B.?
cobol mycob
SYSTEM/360 COBOL COMPILER? ? ? ? ? CB545 V2 LVL78
OPEN ERROR CODE '03' ON 'SYSIN '.
?
Ready; T=0.01/0.04 08:48:47
That was kind of unexpected to me. As Ren¨¦ Ferland explained, the Cobol compiler is significantly older than the system itself and was lifted from a previous version of MVS. Hence the use of VSAMIO which brings VSAM capability to these old compilers. However, the problem seems to start much earlier, at least with my?
VM/370 CE 1.1 installation.
query cplevel
SYSTEM 4381-A
VM/370 Community Edition Version? 1 Release? 1.1 03/10/22 08:54:40
?
Ready; T=0.01/0.01 08:56:28
update: I created the source file with "ee" without any further specification, quite naively. A dir * cobol yields
Filename Filetype Fm? Format? ? Recs Blocks? ? Date? ? ?Time? ?Label
MYCOB? ? COBOL? ? A1? V? ? 32? ? ?10? ? ? 1? 03/12/22? ?16:29? CMS191
Could it be the old compiler chokes because of the file attributes V and lrecl=32??
Is there a way to specify that beforehand or to change the record attributes later??
kind regards
Michael
