View previous topic :: View next topic
|
Author |
Message |
harry143
New User
Joined: 05 Nov 2007 Posts: 21 Location: hyd
|
|
|
|
Hi all,
When we compare our enhanced program with production program, if we want to retrofit any lines that was missing in our program from production program, we will just type MD in the line numbers column of the mainframe screen. Then the line will be retofitted into our code. Can we do the same thing using rexx.
i.e., how can we code command like MD or D(for deleting a line) or I(for inserting a new line) or CC(for copying a set of lines) using rexx. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
Your post is, no ofense meant, completely unclear...
what has the line command MD ( make dataline from a mask line ) have to to with retrofitting..
clarify better what You want todo
THANK YOU ! |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
enrico, when you do a COMPARE within an edited file, new lines appear with a label, deleted lines appear with '======' (info lines).
These deleted lines can be reintroduced by typing MD in the prefix area.
The manual shows the line commands that can be used in a macro.
MD is not among them.
I have not found how info lines (the ones with '======') can be inserted from within a macro.
If you are really stuck, try using COMPARE with the SAVE option, then analyse the file created: prefix.ISPFEDIT.COMPARE.LIST |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
Still ISPF release dependent :-)
( with edit macros
You can insert ==== lines with mask token of the line insert commands )
Anyhow I do not see at all how a REXX can be used to do this kind of task..
They should have a STRONG standard enforced on the format of program updates
( tagging every modified line with a change level token ),
in order to programmatically select for partial upgrade/retrofit
I do not see how a rexx program can achieve that..
A strong change management program/standards with networked change capability would be the solution :-)
together with a standard enforced for small atomic changes and versioning
in order to apply/retrofit the changes in a bundle indepently
OK... messy append, but if You ask I can clarify later
anyway for the o/p request,, better to avoid any programmatic retrofit |
|
Back to top |
|
|
|