开云体育

COBOL compile error

Michael Grom All Messages By This Member #4079 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
Bernd Oppolzer All Messages By This Member #4080 开云体育 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: toggle quoted message Show quoted text 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
Dave Wade All Messages By This Member #4081 开云体育 Michael, Yes it needs FB80 so :- ? copy mycob cobol a = = = (repl recfm f lrecl 80 ? or before you save in EE do ? RECFM F LRECL 80 ? You can customize it with a PROFILE EE file to set COBOL to be FB80 ? FTDEFaults COBOL F 80 ? Take a look at “FSHELP EE” and the sections on profile and configuration. (If you use FSHELP you can move the cursor over the entry you want to view and hit PF1) ? Dave ? ? ? toggle quoted message Show quoted text From: [email protected] <[email protected]> On Behalf Of Michael Grom Sent: 13 March 2022 09:01 To: [email protected] Subject: [h390-vm] COBOL compile error ? 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
Dave Wade All Messages By This Member #4082 开云体育 WHy? COPYFILE (REPL is fine. It creates a new file and then renames the source at the end. ? Dave ? toggle quoted message Show quoted text 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
Bernd Oppolzer All Messages By This Member #4083 开云体育 Thanks :-) didn't know about that ... much easier than my MOVEFILE approach with FILEDEFs Am 13.03.2022 um 12:44 schrieb Dave Wade: toggle quoted message Show quoted text WHy? COPYFILE (REPL is fine. It creates a new file and then renames the source at the end. ? Dave ? 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
René Ferland All Messages By This Member #4084 On Sun, Mar 13, 2022 at 01:01 AM, Michael Grom wrote: I was watching moshix' M94 video (Part 2 on how to use VSAM on VM/370 from COBOL + PL/I using VSAMIO) Michael, ? Be aware, again, that in Moshix video M94, VSAMIO usage is illustrated on a cloud extended Sixpack 1.2, which is different from VM/370 CE. In particular, the VSAMIO minidisk containing the MACLIBs, TXTLIB, and example programs used in the video is NOT available on VM/370 CE. Moreover, Jay Moseley has changed the way he distributes VSAMIO so the video instructions regarding its download and install (if there are any, I don't remember) are most probably obsolete now. ? If you are ever interested by VSAMIO, one possible way to get it on VM/370 CE would be to transfer it from my old obsolete 6PExt. On that system, minidisk 191 of the NOLOG virtual machine VSAMIO contains all the stuff mentionned in the video. ? Cheers, ? Rene FERLAND, Montreal
Michael Grom All Messages By This Member #4085 Dear René, downloaded your 6pack, ipl'ed VM and searched the sixpack direct up and down for that virtual machine, to no avail.? kind regards Michael
Michael Grom All Messages By This Member #4086 Found in the "extended sixpack" direct. :-) Now transferring to my VM/370 installation.. kind regards Michael

Previous Topic Next Topic