View previous topic :: View next topic
|
Author |
Message |
sivatechdrive
Active User
Joined: 17 Oct 2004 Posts: 191 Location: hyderabad
|
|
|
|
Hi,
I used the compare command to compare programs in 2 different libraries.
The newly inserted lines as highlighted with ===== at the first 1-6 columns.
i what to find all the newly inserted lines. i tried using Find '====' but it is of no use.
COuld you please let me know how to find all the new lines .
Code: |
VIEW KCP1NCS.LIB.SOURCE(U3O02005) - 01.99 Columns 00001 00072
Command ===> Scroll ===> CSR
000068 ISS003* (ALT-NA-END-DATE) IS NOT EQUAL TO ZERO. *
====== DK0237* 06/14/2016 - RUCHI SINHA - DK0237 NEW CUSTOMER INFORMATION *
====== DK0237* - CHANGED THE REFERENCE OF RES-DOC-ID-NBR TO ALT-RES-DOC-ID-*
====== DK0237* NBR. *
000069 DK0258* *
|
Thanks
Siva
12 years a member and you didn't use the code tags? Coded for you THIS time. Next time... |
|
Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008 Posts: 2010 Location: USA
|
|
|
|
You fully misunderstand the screen contents.
1) The lines marked as '========' (and highlighted in white) are those lines MISSING in the new version, but presented in the old version.
2) The lines INSERTED into new version are marked with ".OAAAA" etc., (and highlighted in blue).
3) You can use the command COMP oldversion X - option X used to exclude matching lines from view; then you will see only MISSING and INSERTED lines on your screen
4) The CHANGED lines are presented as pair(s) of MISSING+INSERTED lines highlighted in different colors (white, and blue), probably as groups of sequential updated lines.
5) After significant changes the COMP command is not able to synchronize matching lines. In that case the whole mess of MISSING + INSERTED lines is displayed. |
|
Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1306 Location: Vilnius, Lithuania
|
|
|
|
sergeyken wrote: |
You fully misunderstand the screen contents. |
And you are blabbering away without actually answering the question.
Use the command
to find non-data lines in the ISPF editor. |
|
Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010 Posts: 3048 Location: NYC,USA
|
|
|
|
or you can do EXCLUDE = 0 , which gives you only differences and no need of L SPE for each item.
Code: |
Display options:
Lines displayed
with EXCLUDE . . . 0 (0 - 12)
Label Prefix . . . A (A - Y) |
|
|
Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008 Posts: 2010 Location: USA
|
|
|
|
prino wrote: |
sergeyken wrote: |
You fully misunderstand the screen contents. |
And you are blabbering away without actually answering the question.
Use the command
to find non-data lines in the ISPF editor. |
1) "non-data lines" reflect MISSING lines, versus INSERTED lines requested by the author
2) Command L SPE just moves the cursor to the next MISSING line which is (a) not what is needed, (b) doesn't help to display "only inserted lines" as requested by the author
3) Unlike command FIND, the command L SPE needs to be re-typed again and again in the command line in order to jump to each next occurrence of "non-data line"
4) I'm really in doubt who of us is actually blabbering... |
|
Back to top |
|
|
John Del
New User
Joined: 27 Apr 2012 Posts: 42 Location: NY
|
|
|
|
Quote: |
3) Unlike command FIND, the command L SPE needs to be re-typed again and again in the command line in order to jump to each next occurrence of "non-data line" |
That's not entirely true.
Prefix the "L" command with the ampere sign "&" and then you would only need to press enter to advance to the next occurrence.
&L SPE |
|
Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1306 Location: Vilnius, Lithuania
|
|
|
|
sergeyken wrote: |
prino wrote: |
sergeyken wrote: |
You fully misunderstand the screen contents. |
And you are blabbering away without actually answering the question.
Use the command
to find non-data lines in the ISPF editor. |
1) "non-data lines" reflect MISSING lines, versus INSERTED lines requested by the author. |
The TS tells us that the "======" are INSERTED lines, this implies that he's doing a REVERSE compare!
sergeyken wrote: |
2) Command L SPE just moves the cursor to the next MISSING line which is (a) not what is needed, (b) doesn't help to display "only inserted lines" as requested by the author |
The TS tells us that the "======" are INSERTED lines, this implies that he's doing a REVERSE compare!
sergeyken wrote: |
3) Unlike command FIND, the command L SPE needs to be re-typed again and again in the command line in order to jump to each next occurrence of "non-data line" |
Obviously you've never prefixed a command with "&" and Enter will be your uncle!
sergeyken wrote: |
4) I'm really in doubt who of us is actually blabbering... |
I'm not! |
|
Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008 Posts: 2010 Location: USA
|
|
|
|
sergeyken wrote: |
sergeyken wrote: |
4) I'm really in doubt who of us is actually blabbering... |
I'm not! |
"Thrice blessed who believes; believing warms the heart!"(C) |
|
Back to top |
|
|
|