More Debugging Issues
in [Cobol]
|
Prev: Day of Any Week
Next: ANN: OpenCOBOL Programmer's Guide
From: Michael Wojcik on 9 Feb 2010 16:36 Derek Schrock wrote: > On Feb 8, 12:31 pm, Derek Schrock <derekschr...(a)gmail.com> wrote: >> On Feb 8, 11:47 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: >>> The trick here is that rather than using the "anim" trigger to start >>> your program, you should run it with the rtsorta32 executable, as you >>> would if not debugging, but tell the runtime you want to animate: >>> COBSW="+A $COBSW" rtsorta32 ... >>> The +A value in COBSW tells the runtime to start in Animator. >> I thought I tried "rtsorta32 +A ...." but that didn't work. >> >> I'm guessing the reason for that is +A isn't a valid option for >> rtsorta32 however the cob runtime will pic up the $COBOPT env var? > > er COBSW... Right. COBSW settings aren't the same as COBOL RTS command-line options. This is one of the confusing aspects of the MF COBOL products; unfortunately, changing it now would break all sorts of scripts and probably cause quite a lot of confusion among existing customers. (If I *could* change it without causing problems, I'd go for a more GNU-style syntax for the various MF COBOL executables, with "--word" long options and "-x" abbreviations. I'd collapse a number of environment variables into a single COBOL_OPTIONS one, which would take the same flags as the RTS executable. And I'd make the Windows product use the same syntax as the Unix product.) -- Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University
From: Richard on 9 Feb 2010 18:52 On Feb 10, 10:36 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: > Derek Schrock wrote: > > On Feb 8, 12:31 pm, Derek Schrock <derekschr...(a)gmail.com> wrote: > >> On Feb 8, 11:47 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: > >>> The trick here is that rather than using the "anim" trigger to start > >>> your program, you should run it with the rtsorta32 executable, as you > >>> would if not debugging, but tell the runtime you want to animate: > >>> COBSW="+A $COBSW" rtsorta32 ... > >>> The +A value in COBSW tells the runtime to start in Animator. > >> I thought I tried "rtsorta32 +A ...." but that didn't work. > > >> I'm guessing the reason for that is +A isn't a valid option for > >> rtsorta32 however the cob runtime will pic up the $COBOPT env var? > > > er COBSW... > > Right. COBSW settings aren't the same as COBOL RTS command-line > options. This is one of the confusing aspects of the MF COBOL > products; unfortunately, changing it now would break all sorts of > scripts and probably cause quite a lot of confusion among existing > customers. > > (If I *could* change it without causing problems, I'd go for a more > GNU-style syntax for the various MF COBOL executables, with "--word" > long options and "-x" abbreviations. I'd collapse a number of > environment variables into a single COBOL_OPTIONS one, which would > take the same flags as the RTS executable. And I'd make the Windows > product use the same syntax as the Unix product.) Much of the command line originated in the days of CP/M where CIS Cobol was first implemented. Actually even this derived from Cogar/Singer/ICL Dataskill 1500 COBOL.
From: James J. Gavan on 9 Feb 2010 19:51 Richard wrote: > On Feb 10, 10:36 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: > >>Derek Schrock wrote: >> >>>On Feb 8, 12:31 pm, Derek Schrock <derekschr...(a)gmail.com> wrote: >>> >>>>On Feb 8, 11:47 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: >>>> >>>>>The trick here is that rather than using the "anim" trigger to start >>>>>your program, you should run it with the rtsorta32 executable, as you >>>>>would if not debugging, but tell the runtime you want to animate: >>>>> COBSW="+A $COBSW" rtsorta32 ... >>>>>The +A value in COBSW tells the runtime to start in Animator. >>>> >>>>I thought I tried "rtsorta32 +A ...." but that didn't work. >> >>>>I'm guessing the reason for that is +A isn't a valid option for >>>>rtsorta32 however the cob runtime will pic up the $COBOPT env var? >> >>>er COBSW... >> >>Right. COBSW settings aren't the same as COBOL RTS command-line >>options. This is one of the confusing aspects of the MF COBOL >>products; unfortunately, changing it now would break all sorts of >>scripts and probably cause quite a lot of confusion among existing >>customers. >> >>(If I *could* change it without causing problems, I'd go for a more >>GNU-style syntax for the various MF COBOL executables, with "--word" >>long options and "-x" abbreviations. I'd collapse a number of >>environment variables into a single COBOL_OPTIONS one, which would >>take the same flags as the RTS executable. And I'd make the Windows >>product use the same syntax as the Unix product.) > > > Much of the command line originated in the days of CP/M where CIS > Cobol was first implemented. > > Actually even this derived from Cogar/Singer/ICL Dataskill 1500 COBOL. > Richard, Just wondering. Were perhaps Messrs X and Y, who kick-started Micro Focus, former ICL employees ? I know M/F has been around a while now, but does anybody know the start-up date ? Jimmy, Calgary AB
From: Richard on 10 Feb 2010 01:17
On Feb 10, 1:51 pm, "James J. Gavan" <jgavandeletet...(a)shaw.ca> wrote: > Richard wrote: > > On Feb 10, 10:36 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: > > >>Derek Schrock wrote: > > >>>On Feb 8, 12:31 pm, Derek Schrock <derekschr...(a)gmail.com> wrote: > > >>>>On Feb 8, 11:47 am, Michael Wojcik <mwoj...(a)newsguy.com> wrote: > > >>>>>The trick here is that rather than using the "anim" trigger to start > >>>>>your program, you should run it with the rtsorta32 executable, as you > >>>>>would if not debugging, but tell the runtime you want to animate: > >>>>> COBSW="+A $COBSW" rtsorta32 ... > >>>>>The +A value in COBSW tells the runtime to start in Animator. > > >>>>I thought I tried "rtsorta32 +A ...." but that didn't work. > > >>>>I'm guessing the reason for that is +A isn't a valid option for > >>>>rtsorta32 however the cob runtime will pic up the $COBOPT env var? > > >>>er COBSW... > > >>Right. COBSW settings aren't the same as COBOL RTS command-line > >>options. This is one of the confusing aspects of the MF COBOL > >>products; unfortunately, changing it now would break all sorts of > >>scripts and probably cause quite a lot of confusion among existing > >>customers. > > >>(If I *could* change it without causing problems, I'd go for a more > >>GNU-style syntax for the various MF COBOL executables, with "--word" > >>long options and "-x" abbreviations. I'd collapse a number of > >>environment variables into a single COBOL_OPTIONS one, which would > >>take the same flags as the RTS executable. And I'd make the Windows > >>product use the same syntax as the Unix product.) > > > Much of the command line originated in the days of CP/M where CIS > > Cobol was first implemented. > > > Actually even this derived from Cogar/Singer/ICL Dataskill 1500 COBOL. > > Richard, > > Just wondering. Were perhaps Messrs X and Y, who kick-started Micro > Focus, former ICL employees ? I know M/F has been around a while now, > but does anybody know the start-up date ? They were (AFAIK) working for ICL Dataskill in Reading (been there). Dataskill was a contracting and software development company within the ICL group. The ICL 1500 was orginally created by Coagar and they were bought by Singer. ICL bought parts of Singer Business Machines (TRW bought the rest) and rebadged the System 10 and 1500 Series. Later they produced updated versions of these as the System 25 and DRS20 range. The 1500 were networked desktop machines (I still have some here) and desk sized servers with hard disks - 14inch 2.5Mb fixed disk plus 2.5Mb exchangable on the same spindle. The COBOL (I have a copy of the manual here) was written by Dataskill (allegedly the two that later started MF) in 1977 and was very limited. It required 16Kb memory for compiling but only 8Kb for running small programs. It used a run-time interpreter to run the intermediate code (equivalent to .int) programs. The first CIS COBOL from MF was 1978. |