DbzTHEdinosauer Global Moderator Joined: 20 Oct 2006 Location: porcelain throne Posted: Sat Oct 30, 2010 6:51 pm Post subject: depends on: • invoke during edit/view mode• invoke as a batch job• make corrections• just generate an error list• insert error messages my experience with writing such tools is that i found writing it in COBOL or ASSEMBLER was easier, due to the probable required addition of additional checks. Construction Planning And Management By P S Gahlot Pdf Writer. Also, what happens to the source after the check. I found that the only way to enforce programming standards was to introduce the 'check program' in the standard compile jcl and if deviations to the standards were found, insert error messages in the source file (without comment notation), before the compile step, so that the source could not be compiled.

Abklex: Lexikon von Abkuerzungen aus Informatik und Telekommunikation. Some editors are Rexx-aware. They highlight elements of the language in different colors and assist in indenting code. Rexx-aware editors. Examples of Rexx-aware editors include: ❑ THE (The Hessling Editor) for Linux, Unix, Windows, and other platforms ❑ The Rexx Text Editor (or RexxEd), which.

Without the ability to enforce standards, a second best method would be to write several REXX edit macros each having a specific job • would create the indentation required• flag unordered section/para names• flag improper Performs (not allow the thru option• flag goto's that were not to a para/section exit - eliminate potential permanent loops• flag IF's and EVALUATE's that exceeded 3-levels of nesting• modify code lines to insure only one verb and one reference per line - this helps with missing OF/IN's• program-id/pds member name mismatch good 3rd party standards checkers cost quite a bit. So, decide • what your standards are going to be• if you are really going to enforce standards• how you are going to enforce the standards my suggestion is a lot of REXX edit macros, each performing a single task, all CALLed from a Control EDIT Macro or write it in COBOL or ASSEMBLE or PL1, so that the program is easier to maintain.

I have nothing at all against REXX Scripts (i have more than 800 in my personal library) but something as complex as a source program standards checker does not belong in one REXX script. And, spend some time googling. Enrico-sorichetti Global Moderator Joined: 14 Mar 2007 Location: italy Posted: Sat Oct 30, 2010 7:56 pm Post subject: Reply to: Rexx tool for cobol code standard checking google for cobol beautifiers such a tool belongs to the category. Design Cracker Paper Art. Do it right or do not do it at all in rexx it would be easy to build a token parser.