In a past life, when my employer was too cheap to pay for the REXX compiler, we removed comments from public tools and wrote them as 65K blocks for two reasons. First, it saves space in the saved segment and second, it helped prevent support woes caused by incorrect cannibalization. We always kept the original with all comments and formatting. The maintainability was always present and the code was kept obscure to those not privileged to see the original version.
Another use for uncommented EXECs is for code comparisons. By stripping comments, leading and trailing blanks, and deblocking with a semi-colon as the line end, it is easy to spot differences in the code of two programs that may have tons of differences in their comments. I realize that the process that I have listed is simplified; it does not take into account semi-colons that are included in literals. CMPRREXX does take them into account. Regards, Richard Schuh > -----Original Message----- > From: CMSTSO Pipelines Discussion List > [mailto:[email protected]] On Behalf Of Ian S. Worthington > Sent: Thursday, September 10, 2009 3:46 PM > To: [email protected] > Subject: Re: Strip /* */ type comments > > Each to their own of course but anyone in my team who did > this, or stripped the comments, would be getting it back for > rework: I'm *much* more concerned about future > maintainability and access to fully-commented source code > than I am about the possibilities of a rogue user modifying > execs and breaking something. > > i > > ------ Original Message ------ > Received: 04:40 PM COT, 09/10/2009 > From: "Schuh, Richard" <[email protected]> > To: [email protected] > Subject: Re: Strip /* */ type comments > > ... > > > > One of the neat features of is that it can write the REXX output as > > 65K > records. It makes it difficult for someone to glom onto your > code, modify it and then complain that it doesn't work. That > is optional. > > > > Regards, > > Richard Schuh > > > > > > > > > -----Original Message----- > > > From: CMSTSO Pipelines Discussion List > > > [mailto:[email protected]] On Behalf Of Frank > M. Ramaekers > > > Sent: Thursday, September 10, 2009 1:59 PM > > > To: [email protected] > > > Subject: Re: Strip /* */ type comments > > > > > > This is the only reference I can find in the PIPELINES > documentation: > > > > > > Should You Compile Your REXX Filters? > > > The performance of filters that do little processing for > each record > > > will be dominated by the EXECCOMM processing that moves > records into > > > and out of the REXX variable pool. > > > This processing takes roughly the same time for compiled and > > > interpreted REXX; there will be no speed-up from compiling the > > > examples in this chapter. On the other hand, the cmprrexx utility > > > program showed a marked performance improvement when it was > > > compiled. > > > > > > Frank M. Ramaekers Jr. > > > Systems Programmer MCP, MCP+I, MCSE & RHCE > > > American Income Life Insurance Co. Phone: (254)761-6649 > > > 1200 Wooded Acres Dr. Fax: (254)741-5777 > > > Waco, Texas 76710 > > > > > > > > > > > > > > > > > > -----Original Message----- > > > From: CMSTSO Pipelines Discussion List > > > [mailto:[email protected]] On Behalf Of Schuh, Richard > > > Sent: Thursday, September 10, 2009 3:54 PM > > > To: [email protected] > > > Subject: Re: [CMS-PIPELINES] Strip /* */ type comments > > > > > > I forgot to mention, CMPRREXX is/was a REXX filter from > IBM at least > > > as early as VMESA 2.1.0. I don't know where it lives > today, except > > > for the copy on my Tools disk, that is. > > > > > > Regards, > > > Richard Schuh > > > > > > > > > > > > > -----Original Message----- > > > > From: CMSTSO Pipelines Discussion List > > > > [mailto:[email protected]] On Behalf Of SPITZ, HOBART > > > > CTR DFAS > > > > Sent: Thursday, September 10, 2009 1:47 PM > > > > To: [email protected] > > > > Subject: Re: Strip /* */ type comments > > > > > > > > See new split. > > > > > > > > "PIPE (endchar ?)", > > > > " < SYSTEM CONFIG T", > > > > "| STRIP", > > > > "| INSERT x01 AFTER", > > > > "| SPLIT BEFORE STR '/*'", > > > > "| SPLIT BEFORE STR '*/'", > > > > "| split after str '*/'", > > > > "| NOT BETWEEN '/*' '*/'", > > > > "| JOINCONT NOT TRAILING x01", > > > > "| CONSOLE" > > > > > > > > -----Original Message----- > > > > From: CMSTSO Pipelines Discussion List > > > > [mailto:[email protected]] On Behalf Of Frank M. > > > > Ramaekers > > > > Sent: Thursday, September 10, 2009 4:37 PM > > > > To: [email protected] > > > > Subject: Re: [CMS-PIPELINES] Strip /* */ type comments > > > > > > > > This close: > > > > > > > > "PIPE (endchar ?)", > > > > " < SYSTEM CONFIG T", > > > > "| STRIP", > > > > "| INSERT x01 AFTER", > > > > "| SPLIT BEFORE STR '/*'", > > > > "| SPLIT BEFORE STR '*/'", > > > > "| NOT BETWEEN '/*' '*/'", > > > > "| JOINCONT NOT TRAILING x01", > > > > "| CONSOLE" > > > > > > > > Except for: > > > > > > > > Features , > > > > > > > > Disable , Set_Privclass , > > > > Auto_Warm_IPL , Clear_TDisk , > Enable, > > > > Dynamic_I/O, > > > > > > > > Set_Devices, > > > > > > > > Set_Dynamic_I/O, > > > > > > > > New_devices_Initialized_When_Added, > > > > > > > > Retrieve , Default 20 , > > > Maximum > > > > 255 , MaxUsers noLimit , Password > > > > s_on_Cmds , Autolog No , > Link No , > > > > Logon No , Vdisk Userlim 1440 > > > > 00 blocks > > > > > > > > > > > > Which was: > > > > > > > > Features , > > > > > > > Disable , /* Disable the following > > > features */ > > > > Set_Privclass , /* Disallow SET PRIVCLASS > > > command */ > > > > Auto_Warm_IPL , /* Prompt at IPL always > > > */ > > > > Clear_TDisk , /* Don't clear TDisks at > > > IPL time */ > > > > Enable, > > > > > > > Dynamic_I/O, > > > > > > > Set_Devices, > > > > > > > Set_Dynamic_I/O, > > > > > > > New_devices_Initialized_When_Added, > > > > > > > Retrieve , /* Retrieve options > > > */ > > > > Default 20 , /* Default.... default is > > > 20 */ > > > > Maximum 255 , /* Maximum.... default is > > > 255 */ > > > > MaxUsers noLimit , /* No limit on number of > > > users */ > > > > Passwords_on_Cmds , /* What commands allow > > > passwords? */ > > > > Autolog No , /* ... AUTOLOG does > > > */ > > > > Link No , /* ... LINK does > > > */ > > > > Logon No , /* ... and LOGON does, > > > too */ > > > > Vdisk Userlim 144000 blocks /* Maximum vdisk allowed > > > per user */ > > > > > > > > Frank M. Ramaekers Jr. > > > > Systems Programmer MCP, MCP+I, MCSE & RHCE > > > > American Income Life Insurance Co. Phone: (254)761-6649 > > > > 1200 Wooded Acres Dr. Fax: (254)741-5777 > > > > Waco, Texas 76710 > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: CMSTSO Pipelines Discussion List > > > > [mailto:[email protected]] On Behalf Of SPITZ, HOBART > > > > CTR DFAS > > > > Sent: Thursday, September 10, 2009 3:25 PM > > > > To: [email protected] > > > > Subject: Re: [CMS-PIPELINES] Strip /* */ type comments > > > > > > > > Sorry. I did it from memory. It's "insert x01 after", > of course. > > > > > > > > Any suitable end of line marker will do. > > > > > > > > -----Original Message----- > > > > From: CMSTSO Pipelines Discussion List > > > > [mailto:[email protected]] On Behalf Of Frank M. > > > > Ramaekers > > > > Sent: Thursday, September 10, 2009 4:20 PM > > > > To: [email protected] > > > > Subject: Re: [CMS-PIPELINES] Strip /* */ type comments > > > > > > > > PIPCHA060E Delimiter missing after string "AFTER x01". > > > > PIPSCA003I ... Issued from stage 3 of pipeline 1. > > > > PIPSCA001I ... Running "INSERT AFTER x01". > > > > > > > > > > > > +------------------------------------------------------------- > > > > ---------- > > > > ----+ > > > > ! | > > > > | > > > > ! | +-BEFORE-+ > > > > | > > > > ! | > > > > >>--INSERT--delimitedString--+--------+--+------------+------- > > > > ---------> > > > > < | > > > > ! | +-AFTER--+ +-inputRange-+ > > > > | > > > > | > > > > | > > > > > > > > +------------------------------------------------------------- > > > > ---------- > > > > ----+ > > > > > > > > Frank M. Ramaekers Jr. > > > > Systems Programmer MCP, MCP+I, MCSE & RHCE > > > > American Income Life Insurance Co. Phone: (254)761-6649 > > > > 1200 Wooded Acres Dr. Fax: (254)741-5777 > > > > Waco, Texas 76710 > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > From: CMSTSO Pipelines Discussion List > > > > [mailto:[email protected]] On Behalf Of SPITZ, HOBART > > > > CTR DFAS > > > > Sent: Thursday, September 10, 2009 3:13 PM > > > > To: [email protected] > > > > Subject: Re: [CMS-PIPELINES] Strip /* */ type comments > > > > > > > > ... | insert after x01 | split before '/*' | split before > > > '*/' | not > > > > between '/*' '*/' | joincont not trailing x01 | ... > > > > > > > > -----Original Message----- > > > > From: CMSTSO Pipelines Discussion List > > > > [mailto:[email protected]] On Behalf Of Frank M. > > > > Ramaekers > > > > Sent: Thursday, September 10, 2009 4:03 PM > > > > To: [email protected] > > > > Subject: [CMS-PIPELINES] Strip /* */ type comments > > > > > > > > Is there a way to strip the /* */ type comments from a stream? > > > > Same line / Partial line / Spanned lines > > > > > > > > Frank M. Ramaekers Jr. > > > > Systems Programmer MCP, MCP+I, MCSE & RHCE > > > > American Income Life Insurance Co. Phone: (254)761-6649 > > > > 1200 Wooded Acres Dr. Fax: (254)741-5777 > > > > Waco, Texas 76710 > > > > > > > > > > > > _____________________________________________________ > > > > > > > > This message contains information which is privileged and > > > confidential > > > > and is solely for the use of the > > > > > > > > intended recipient. If you are not the intended recipient, be > > > > aware that any review, disclosure, > > > > > > > > copying, distribution, or use of the contents of this > message is > > > > strictly prohibited. If you have > > > > > > > > received this in error, please destroy it immediately and > > > notify us at > > > > [email protected]. > > > > > > > > _____________________________________________________ > > > > > > > > This message contains information which is privileged and > > > confidential > > > > and is solely for the use of the > > > > > > > > intended recipient. If you are not the intended recipient, be > > > > aware that any review, disclosure, > > > > > > > > copying, distribution, or use of the contents of this > message is > > > > strictly prohibited. If you have > > > > > > > > received this in error, please destroy it immediately and > > > notify us at > > > > [email protected]. > > > > > > > > _____________________________________________________ > > > > > > > > This message contains information which is privileged and > > > confidential > > > > and is solely for the use of the > > > > > > > > intended recipient. If you are not the intended recipient, be > > > > aware that any review, disclosure, > > > > > > > > copying, distribution, or use of the contents of this > message is > > > > strictly prohibited. If you have > > > > > > > > received this in error, please destroy it immediately and > > > notify us at > > > > [email protected]. > > > > > > > > > > _____________________________________________________ > This message > > > contains information which is privileged and confidential and is > > > solely for the use of the intended recipient. If you are not the > > > intended recipient, be aware that any review, disclosure, > copying, > > > distribution, or use of the contents of this message is strictly > > > prohibited. If you have received this in error, please destroy it > > > immediately and notify us at [email protected]. > > >
