Re: Named indicators (was DOW vs DOU)

RE:     Re: Named indicators (was DOW vs DOU)

>>Neil Palmer said:

>> Not that you would have a block of indicators in nicely structured code,
>> but again with MOVEA for setting on/off blocks of indicators aren't you
>> sacrificing readability and making it harder to scan/spot indicators
>> used in the source ?  If I remember correctly, they don't even show up
>> in the cross reference listing when you compile the program. -- ... Neil
>> Palmer                                      AS/400~~~~~      ... NxTrend

>I use a block of indicators to track all subfile settings. I haven't done 
>it, but I have toyed with the idea of creating block names for the 
>indicators to be set like CLRSFL and DLTSFL and just doing a MOVEA CLRSFL 
>before writing the ctl record. That way, I know I didn't forget to turn 
>off display ctl or something like that.
>Does that make any sense?
>Chris Rehm         

Chris
If your going to do it. It should be the SHOP STANDARD.  If the reason
is error indicators for DSPATR(RI PC) etc.  Try using from 80 or 90 Up.
Before I say anything else, -SHOP STANDARD, EVERYBODY DOES IT THIS WAY-
You could use MOVEA *ALL,'0' *IN(80) to set them all off.

This can be done in the mainline after the EXFMT statement.  ONCE AGAIN
this works because NOBODY Looks or scans for it, why? BECAUSE EVERY PROGRAM 
DOES IT THAT WAY.  If something is soooo understood in your shop that
its second nature, you can get away with a lot. However go to a different
shop, You'll get killed.   

Ladys and Gentlemen,  How many shops have you been in where when a new
employee or a consultant comes in to work they are sat down and given
a codified standards book, told to GROK it or understand it completely 
before writing the first line of code?

OR is the new person just given a User Profile and told to "Start Coding"?
BTW Who's program is it?  Who will maintain it when you leave? 
IOW, Who Owns The Code?

John P. Carr CDP
EdgeTech


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the Midrange System Mailing List!  To submit a new message,   *
* send your mail to "MIDRANGE-L@midrange.com".  To unsubscribe from     *
* this list send email to MAJORDOMO@midrange.com and specify            *
* 'unsubscribe MIDRANGE-L' in the body of your message.  Questions      *
* should be directed to the list owner / operator: david@midrange.com   *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *