I tend to use mixed case data area tags since I believe they help identify the
field contents better -- a practice I loosely refer to as "capital separated
words." This example is from the initialization code of a test data generation
program:
CLI DgwaParmCount,X'00' Anything for COUNT parameter?
BE Init0020 No ==> Stay with default
*
PACK DgwaDWord,DgwaParmCount Convert desired record ...
CVB R3,DgwaDWord ... count to binary
*
Init0020 DS 0H
CLI DgwaParmObid,X'00' Anything for OBID parameter?
BE Init0030 No ==> Stay with default
*
PACK DgwaDword,DgwaParmObid Convert desired ...
CVB R4,DgwaDWord ... OBID to binary
*
Init0030 DS 0H
ST R3,Dgwa#Records Save binary record ...
STH R4,DgwaObid ... count and OBID
*
NI DgwaParmSeed,X'7F' Ensure positive initial seed
*
* _________________ Copy Model DCB and DCBE to DGWA _________________
*
MVC DgwaOutDcb,OutDcbModel Initialize DCB
MVC DgwaOutDcbe,OutDcbeModel Initialize DCBE
*
PUSH USING Save current USING state
*
USING IHADCB,DgwaOutDcb Map encapsulated DCB
*
LA R0,DgwaOutDcbe Get DCBE's address
ST R0,DCBDCBE Set DCBE's address in DCB
MVCFI DCBDDNAM,'SYSUT1 ' Set "SYSUT1" as DDNAME
*
POP USING Restore earlier USING state
(MVCFI - MVC From Inverted - is a macro that generates "MVCIN DCBDDNAM(8),=C'
1TUSYS'+7")
-- Art Celestini
At 08:39 PM 12/22/2011, Paul Gilmartin wrote:
>On 12/22/2011 16:10, Bodoh John Robert wrote:
>>I do it a little different. I like mixed case for comments and remarks but
>>like uppercase for the actual code. The mixed case comments and remarks are
>>easier to read and the uppercase code is quite distinguishable from the
>>comments and remarks.
>Plays well with case-sensitive searches in an editor, which will
>find either code or comments, but not both.
>
>-- gil
