| View previous topic :: View next topic |
| Author |
Message |
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
 Posted: Thu Aug 11, 2022 1:18 am Post subject: Set ==CHG> string in prefix area |
 |
|
I noticed that if I run a command such as
| Quote: |
change FRED BERT all
|
in a file, I see the string ==CHG> in the prefix area for each changed line.
I'm running an edit macro that performs a find, then change on individual lines where the before/after strings vary through the macro.
I was wondering if there is a way of creating the ==CHG> string in the prefix area via an edit command?
I know I can use the LINE_BEFORE command, but then the results look something like this
| Quote: |
==MSG> LINE CHANGED
001260 MOVE OBD IN HFADA1A-REC TO W-DATUM.
|
(not what I'm after since there will be hundreds of changes in the code, and the user won't be able to see the wood for the trees, IMO, compared to the equivalent results for change FRED BERT all)
_________________
Michael |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12367
Topics: 75
Location: San Jose
|
|
| Back to top |
|
|
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
| Posted: Fri Aug 12, 2022 5:53 am Post subject: |
|
|
That won't work since I need to actually change the code.
I can see the thinking behind the idea of marking the prefix area for a "change ..... ALL" (in case you made changes that weren't intended).
The docs indicate the following is valid
| Quote: |
(varname)-- = --LINE_STATUS--+-linenum-+
|
so based on most EDIT commands, I assumed something like the following might work
| Quote: |
"LINE_STATUS .zcsr = "varname
|
where varchar was defined as a 32 byte string.
Unfortunately, I got RC = 20, so I'm guessing it's simply not allowed.
_________________
Michael |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
