On Fri, 14 Apr 2023 at 16:58, Lionel B. Dyck <lbd...@gmail.com> wrote:

> You could try something like this:
>
> 1. while in edit (or view) exclude all
> 2. then md to convert all
> 3. then do a compare *
>
> Now all the 'new' records will have a indicator in the record number field
> - I don't recall if you can access that but suspect you might be able to do
> so.
>
> /* REXX edit macro to get information about line changes              */
/*** trace ?r ***************************************************** \| *
*               (C) Copyright Robert AH Prins, 2001-2001               *
************************************************************************
*  ------------+------+----------------------------------------------  *
* | Date       | By   | Changes                                      | *
* |------------+------+----------------------------------------------| *
* |            |      |                                              | *
* |------------+------+----------------------------------------------| *
* | 2001-05-15 | RAHP | Initial version                              | *
* |------------+------+----------------------------------------------| *
************************************************************************
* ELS is an edit macro that uses the 'line_status' command to display  *
* information about datalines in the member currently being edited.    *
************************************************************************
* Send questions, suggestions and/or bug reports to:                   *
*                                                                      *
* robert.ah.pr...@gmail.com                                            *
************************************************************************
* This program is free software: you can redistribute it and/or        *
* modify it under the terms of the GNU General Public License as       *
* published by the Free Software Foundation, either version 3 of       *
* the License, or (at your option) any later version.                  *
*                                                                      *
* This program is distributed in the hope that it will be useful,      *
* but WITHOUT ANY WARRANTY; without even the implied warranty of       *
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the         *
* GNU General Public License for more details.                         *
*                                                                      *
* You should have received a copy of the GNU General Public License    *
* along with this program. If not, see <http://www.gnu.org/licenses/>  *
***********************************************************************/
"isredit macro"
"ispexec control errors return"
"isredit (LS) = line_status .ELS"

if rc \= 0 then
  do
    zedsmsg = ''
    zedlmsg = 'Mark the line for which you want to get information ' ||,
              'with the label ''.ELS'''

    "ispexec setmsg msg(ISRZ001)"
    exit 1
  end

if substr(ls, 1, 1) = '1' then
  line = ' - Line is an original line'
else
  if substr(ls, 2, 1) = '1' then
    line = ' - Line was created using the M(ove) line command'
  else
    if substr(ls, 3, 1) = '1' then
      line = ' - Line was created using the C(opy) or R(epeat) ' ||,
             'line command'
    else
      if substr(ls, 4, 1) = '1' then
        line = ' - Line was created using the M(ove) primary ' ||,
               'or macro command'
      else
        if substr(ls, 5, 1) = '1' then
          line = ' - Line was created using the C(opy) primary ' ||,
                 'or macro command'
        else
          if substr(ls, 6, 1) = '1' then
            line = ' - Line was created using the TE line command'
          else
            if substr(ls, 7, 1) = '1' then
              line = ' - Line was created using the I(nsert) ' ||,
                     'line command'

"isredit line_before .ELS = noteline (LINE)"

if substr(ls, 8, 1) = '0' then
  do
    line = ' - Line was not changed'
    "isredit line_before .ELS = noteline (LINE)"
  end
else
  do
    if substr(ls, 9, 1) = '1' then
      do
        line = ' - Data on line was typed over'
        "isredit line_before .ELS = noteline (LINE)"
      end

    if substr(ls, 10, 1) = '1' then
      do
        line = ' - Data on line was changed by the C(hange) or ' ||,
               'O(verlay) command'
        "isredit line_before .ELS = noteline (LINE)"
      end

    if substr(ls, 11, 1) = '1' then
      do
        line = ' - Data on line was changed by the (, ((, ) or ' ||,
               ')) command'
        "isredit line_before .ELS = noteline (LINE)"
      end

    if substr(ls, 12, 1) = '1' then
      do
        line = ' - Data on line was changed by the <, <<, > or ' ||,
                 '>> command'
        "isredit line_before .ELS = noteline (LINE)"
      end

    if substr(ls, 13, 1) = '1' then
      do
        line = ' - Data on line was changed by the TE, TF or ' ||,
                   'TS command'
        "isredit line_before .ELS = noteline (LINE)"
      end

    if substr(ls, 14, 1) = '1' then
      do
        line = ' - The line was renumbered'
        "isredit line_before .ELS = noteline (LINE)"
      end
  end
exit 1

No clue if there's a flag for lines originating from "MD"

Robert
-- 
Robert AH Prins
robert(a)prino(d)org
The hitchhiking grandfather <https://prino.neocities.org/index.html>
Some REXX code for use on z/OS
<https://prino.neocities.org/zOS/zOS-Tools.html>


From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
Pommier, Rex

> Sent: Friday, April 14, 2023 11:28 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] ISPF usage question
>
> Thanks, all, for your suggestions.  It is as I feared/figured.  ISPF edit
> doesn't have any mechanism to actually search for information in =NOTE= or
> ==MSG> lines without converting them to full data lines.
>
> Rex
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf
> Of Horne, Jim
> Sent: Tuesday, April 11, 2023 6:03 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: [EXTERNAL] ISPF usage question
>
> Check out the ISPF Edit LOCATE command, especially LOCATE SPECIAL and
> LOCATE NOTE
>
> Jim Horne
> -----Original Message-----
>
> Running certain ISPF macros and/or  commands, we get lines added to the
> ISPF edit screen with "=NOTE=" or "==MSG>" lines.  Is there a way to make
> these lines searchable without converting them to full data lines?  The
> specific instance I'm asking about is running a third party JCL checker,
> the lines output from the checker are typically notes or messages.  The
> nice thing about them being such, is they aren't really part of the member
> being edited/checked so if I save the member, these lines aren't included
> in the member being saved.  The drawback of them is that they aren't
> searchable, so for example, if I'm looking at output with a called PROC,
> and I want to search for a particular piece of substituted JCL, I can't do
> so (that I know of) unless I do a full "make data" on the member, which
> then makes me vulnerable to accidentally saving the member with all the
> notes and messages still there.
>
> ________________________________
> NOTICE: All information in and attached to the e-mails below may be
> proprietary, confidential, privileged and otherwise protected from improper
> or erroneous disclosure. If you are not the sender's intended recipient,
> you are not authorized to intercept, read, print, retain, copy, forward, or
> disseminate this message. If you have erroneously received this
> communication, please notify the sender immediately by phone (704-758-1000)
> or by e-mail and destroy all copies of this message electronic, paper, or
> otherwise. By transmitting documents via this email: Users, Customers,
> Suppliers and Vendors collectively acknowledge and agree the transmittal of
> information via email is voluntary, is offered as a convenience, and is not
> a secured method of communication; Not to transmit any payment information
> E.G. credit card, debit card, checking account, wire transfer information,
> passwords, or sensitive and personal information E.G. Driver's license,
> DOB, social security, or any other information the user wishes to remain
> confidential; To transmit only non-confidential information such as plans,
> pictures and drawings and to assume all risk and liability for and
> indemnify Lowe's from any claims, losses or damages that may arise from the
> transmittal of documents or including non-confidential information in the
> body of an email transmittal. Thank you.
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> The information contained in this message is confidential, protected from
> disclosure and may be legally privileged. If the reader of this message is
> not the intended recipient or an employee or agent responsible for
> delivering this message to the intended recipient, you are hereby notified
> that any disclosure, distribution, copying, or any action taken or action
> omitted in reliance on it, is strictly prohibited and may be unlawful. If
> you have received this communication in error, please notify us immediately
> by replying to this message and destroy the material in its entirety,
> whether in electronic or hard copy format. Thank you.
>
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email
> to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to