My advice is to have a subroutine/function in your REXX that converts one or 
more physical lines from the ISFLINE stem into a logical message.

This will mean processing multiple ISFLINE variables when you encounter a 
multi-line WTO using the indicators in the first 2 bytes of ISFLINE and the 
correlation number ('nnn') - for example :

MR0000000  SYS1  yyyyddd hh:mm:ss.th jobname xxxxxxxx msgid text nnn
LR                                                                       nnn    
      title_text
DR                                                                      nnn     
     data_text
DR                                                                      nnn     
     data_text
ER                                                                      nnn     
     last_data_text


Rob Scott
Rocket Software

-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of 
ibmmain
Sent: 20 September 2021 17:03
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: How to use the FILTER command for OPERLOG in batch

EXTERNAL EMAIL





Hi Rob


&nbsp; Thanks for your help!


&nbsp; I have another question.


&nbsp; When we use the SDSF “FILTER" command on the operlog, the output of 
"FILTER" is the complete messages ( for multi-line messages)


&nbsp;If we use "POS" or "INDEX" on the OPERLOG&nbsp; rows, how to&nbsp; 
handle&nbsp; multi-line messages?


Thanks a lot!


Jason Cai




发件人:                                                                            
                                            "IBM Mainframe Discussion List"     
                                                                               
<rsc...@rocketsoftware.com&gt;;
发送时间:&nbsp;2021年9月20日(星期一) 晚上8:55
收件人:&nbsp;"IBM-MAIN"<IBM-MAIN@LISTSERV.UA.EDU&gt;;

主题:&nbsp;Re: How to use the FILTER command for OPERLOG in batch



The SDSF "FILTER" command normally applies to tabular panels like "DA" or "ST" 
and not browse panels (of which "LOG O" aka OPERLOG is one).

In 1995, SDSF added some special case code so that FILTER would work in 
TSO/ISPF with the "LOG O" panel , however it appears this was never implemented 
into the REXX interface. We will take a look to see if there were architectural 
reasons why this is the case or whether this is just an omission (or a 
regression).

Local testing shows that the ISFFILTER special variable is ignored for "ISFLOG 
READ TYPE(OPERLOG)" function calls on z/OS 2.3 and 2.4.

In the meantime, I suggest you implement some sort of REXX exec filtering using 
functions like "POS" or "INDEX" on the OPERLOG rows that are returned in the 
ISFLINE stem variables.

Rob Scott
Rocket Software

&nbsp;please notify Rocket Software immediately and destroy all copies of this 
communication. 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
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================

This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

----------------------------------------------------------------------
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