topic Re: Decforms compilation output - mismatch with the Decform source file line numbers. in Operating System - OpenVMS

topic Re: Decforms compilation output - mismatch with the Decform source file line numbers. in Operating System - OpenVMS https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116361#M37191 <P>I don't think there is a /LIST quliflier there.</P> Thu, 27 Jun 2013 03:58:56 GMT Notilus007 2013-06-27T03:58:56Z Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116051#M37189 <P>When I compile a decform (IFDL) source file, I get a compilation output with error line numbers that do not match the line numbers in the source file itself.</P><P> </P><P>Does anybody know a way to tell the compiler to indicate the corresponding errors line number from the source file itself?</P> Wed, 26 Jun 2013 21:02:48 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116051#M37189 Notilus007 2013-06-26T21:02:48Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116305#M37190 Thu, 27 Jun 2013 03:22:17 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116305#M37190 Steven Schweda 2013-06-27T03:22:17Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116361#M37191 <P>I don't think there is a /LIST quliflier there.</P> Thu, 27 Jun 2013 03:58:56 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116361#M37191 Notilus007 2013-06-27T03:58:56Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116435#M37192 Thu, 27 Jun 2013 04:55:58 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6116435#M37192 Steven Schweda 2013-06-27T04:55:58Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117577#M37193 <P>The actual compilation command that I use is :</P><P>$FORMS TRANSLATE file_name.IFDL</P><P> </P><P>The compilation output that I get is :</P><P> </P><P>3016               Pan el ICA_TRT779_data_PANEL</P><P>%FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled.</P><P>-FORMS-I-EXPECTED, one of the following was expected: ALL, WAIT, ICON, FIELD, GROUP, PANEL, BUTTON, CORRESPONDING.</P><P> </P><P>3016               Pan el ICA_TRT779_data_PANEL</P><P>%FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled.</P><P>-FORMS-I-ONEXPECTED, the following was expected: ON</P><P> </P><P>3163           Copy</P><P>%FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled.</P><P>-FORMS-I-EXPECTED, one of the following was expected: APPLY, HELP, PANEL, MESSAGE, END.</P><P> </P><P>3165           End Copy</P><P>%FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled.</P><P>-FORMS-I-ONEXPECTED, the following was expected: LAYOUT</P><P> </P><P>3171              Copy</P><P>%FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled.</P><P>-FORMS-I-ONEXPECTED, the following was expected: _/End_of_Line/_</P><P> </P><P>3173           End Copy</P><P>%FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled.</P><P>-FORMS-I-ONEXPECTED, the following was expected: FORM</P><P>%FORMS-W-NONCOMMENT, non comment text after END FORM has been ignored.</P><P> </P><P>Unfortunately the line numbers do not match the line numbers on the source file (file_name.IFDL)</P> Thu, 27 Jun 2013 17:49:18 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117577#M37193 Notilus007 2013-06-27T17:49:18Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117601#M37194 Thu, 27 Jun 2013 18:11:48 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117601#M37194 Steven Schweda 2013-06-27T18:11:48Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117603#M37195 <P> </P><P>Hmmm, the user provided names reported in the error messages appear relatively unique. </P><P>Simply search for each occurance?</P><P>Are the line number in 'range' at all? </P><P>Are there copy/include files involved?</P><P> </P><P>Can create a DCL/Awk/Perl script to execute the includes inline 'blowing up' the source and compile the result or just use the indicate error line numbers as pointers into that exploded result?</P><P><SPAN>Maybe the line numbers will match that way?</SPAN></P><P><SPAN> </SPAN></P><P><SPAN>fwiw,</SPAN></P><P><SPAN>Hein</SPAN></P><P><SPAN> </SPAN></P><P> </P> Thu, 27 Jun 2013 18:13:23 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117603#M37195 Hein van den Heuvel 2013-06-27T18:13:23Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117613#M37196 There are copy/include files involved, but how can I have the output with error line numbers matching those in the original source file and not the LIST file ?<BR />Somehow it works fine when I compile HP Cobol files. Thu, 27 Jun 2013 18:28:24 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117613#M37196 Notilus007 2013-06-27T18:28:24Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117631#M37197 <P>I do not code in DECForms, but I appears to me that the compiler is telling you what the error is; the error appears to me to be an imbedded space in the verb "PAN EL"  in your defintion. OpenVMS does not like embedded spaces in most commands and languages.</P><P> </P><P>The other error is that the command COPY is not recognized by the DECforms compiler, is this the correct syntax and is the copy is the correct progression of the form definition ?   If it is, then it is just a secondary error caused because the PANEL verb failed from above.</P><P> </P><P>Please review your syntax.  Just curious, did you use some kind of automated program to generate this code in the first place ? This could explan the gotchas here.</P><P> </P><P> Line numbering in all OpenVMS langages and compilers is a bit complicated because all the included data, functions and library definitions are included in the source at compile time and are added to line counts. These additional line are accounted for in the compliation and can extensive.  There may be a way to do this but if the error is evident do you really need the line number to find the error?  </P> Thu, 27 Jun 2013 18:57:00 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117631#M37197 Tom Wetty 2013-06-27T18:57:00Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117651#M37198 Thu, 27 Jun 2013 19:11:02 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117651#M37198 Steven Schweda 2013-06-27T19:11:02Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117669#M37199 I have read section C.3 in "HP DECforms Guide to Commands and Utilities" and it seems that only with LSE I can do the correlation between the compilation errors and the line number in the IFDL source file. How can I do it without using LSE ? Thu, 27 Jun 2013 19:35:16 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117669#M37199 Notilus007 2013-06-27T19:35:16Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117691#M37200 <P> </P><P>In this specific case, as Tom indicates, you should just SEARCH the source for "PA NEL" and fix that!<BR /><BR /></P><P>For the general case is is indeed tricky as DECforms counts the lines from FILE COPY to the listing.</P><P>COPY FROM DICTIONARY poses no problem.</P><P> </P><P>I made a little example removing a few lines from a working IFDL, put it into a copy file (tmp.tmp) and broke a line further down just like the example</P><P> </P><P>The LISTING makes clear how the COPY impacts the lines:</P><P> </P><PRE> 658 COPY 659 "tmp.tmp" 660 END COPY 661C /* RECORD LIST DEefinitions */ 662C 663C RECORD LIST res_cust_num 664C vr_control_wksp 665C vr_reservations_wksp 666C vr_customers_wksp 667C END LIST 668C 669C 670 671 RECORD LIST cust_res_list</PRE><P> </P><P> </P><P>See how the reported line number moved:</P><P> </P><PRE>$ sea/num tmp.ifdl "pa nel" 3707 PA NEL confirm_panel $ form tran tmp.ifdl 3716 PA NEL confirm_panel %FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled. -FORMS-I-EXPECTED, one of the following was expected: ALL, WAIT, ICON, FIELD, GROUP, PANEL, BUTTON, CORRESPONDING. 3716 PA NEL confirm_panel %FORMS-E-SYNTAXERR, syntax error; an expected keyword, name or literal is missing or misspelled. -FORMS-I-ONEXPECTED, the following was expected: ON</PRE><P> </P><P> </P><P>TO map them back, you could use a script as I suggested.</P><P>I hacked one up in DCL. Crude...  Minimal parsing... but it works for me.</P><P>If you want to use it, then you need to verify the SYNTAX of your COPY / END COPY usage.</P><P> </P><P>Enjoy!</P><P>HEin</P><P> </P><P> </P><PRE>$ @IFDL_COPY.COM tmp.ifdl 3716 538/538 Copy tmp.tmp 3716 lines.3707 Lines in IFDL, 1 Copy Files $ $ type IFDL_COPY.COM $ IF P2.EQS."" THEN EXIT 16 $ line = p2 $ IF F$TYPE(line).NES."INTEGER" THEN EXIT 16 $ CLOSE/NOLOG ifdl $ OPEN/READ/ERROR=ooops ifdl 'P1 $ copy_file = 0 $ ifdl_line = 0 $ list_line = 0 $ quote = """" $ space = " " $main_loop: $ read/end=done ifdl rec $ ifdl_line = ifdl_line + 1 $ list_line = list_line + 1 $ if list_line.EQ.line THEN GOTO done $ x = f$edit(rec,"TRIM,COMPRESS,UPCASE,UNCOMMENT") $ IF x.NES."COPY" THEN GOTO main_loop $ read/end=done ifdl rec $ copy_file_name = f$edit(rec,"TRIM,COMPRESS,UPCASE,UNCOMMENT") - quote - quote $ IF F$ELEM(1,space,copy_file_name).NES.space THEN GOTO main_loop $ WRITE SYS$OUTPUT list_line, "/", ifdl_line, " Copy ", copy_file_name $ CLOSE/NOLOG copy $ OPEN/READ/ERROR=ooops copy 'copy_file_name $ copy_file = copy_file + 1 $ copy_loop: $ READ/END=main_loop/ERROR=ooops copy rec ! Just leave open $ list_line = list_line + 1 $ GOTO copy_loop $ $done: $ write sys$output list_line, " lines.", ifdl_line, " Lines in IFDL, ", copy_file, " Copy Files" $ close/nolog ifdl $ close/nolog copy $ooops: $ EXIT '$STATUS</PRE><P> </P><P> </P><P> </P><P> </P><P> </P><P> </P><P> </P><P> </P> Thu, 27 Jun 2013 20:34:48 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6117691#M37200 Hein van den Heuvel 2013-06-27T20:34:48Z Re: Decforms compilation output - mismatch with the Decform source file line numbers. https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6126641#M37201 <P>Thanks a lot Hein, we have tried your script and this solution of yours works great for us.</P> Sat, 06 Jul 2013 22:23:30 GMT https://community.hpe.com/t5/operating-system-openvms/decforms-compilation-output-mismatch-with-the-decform-source/m-p/6126641#M37201 Notilus007 2013-07-06T22:23:30Z