Can the OP live with a 4 character limited and no embedded blanks?

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3

________________________________________
From: IBM Mainframe Assembler List [[email protected]] on behalf 
of Tom Harper [[email protected]]
Sent: Wednesday, October 21, 2020 1:44 PM
To: [email protected]
Subject: Re: Another Macro question

As promised: As is, no warranties expressed or implied:


000001          MACRO
000002 &LABEL   XXXCBID &EYECATCHER=
000003
000032 .**********************************************************************
000033 .*                                                                    *
000035 .*                                                                    *
000036 .*        XXXXBMD   Init control block header ID                      *
000037 .*                                                                    *
000040 .*        EYECATCHER 4-character ID                                   *
000043 .*                                                                    *
000044 .**********************************************************************
000045 .*                                                                    *
000048          LCLC  &REYE(4)                EYECATCHER, reversed by byte
000049          LCLC  &CBID                   CBID, reversed
000050          LCLA  &KEYEC                  K'EYECATCHER
000051          LCLA  &KCBID                  K'CBID
000052 .**********************************************************************
000053 .*                                                                    *
000056 &KEYEC   SETA K'&EYECATCHER
000057          AIF  (&KEYEC LT 4).SKIP4
000058 &REYE(1) SETC '&EYECATCHER'(4,1) Swap
000059          AGO  .CONT4
000060 .SKIP4   ANOP
000061 &REYE(1) SETC ' '
000062 .CONT4   ANOP
000063          AIF  (&KEYEC LT 3).SKIP3
000064 &REYE(2) SETC '&EYECATCHER'(3,1) Swap
000065          AGO  .CONT3
000066 .SKIP3   ANOP
000067 &REYE(2) SETC ' '
000068 .CONT3   ANOP
000069          AIF  (&KEYEC LT 2).SKIP2
000070 &REYE(3) SETC '&EYECATCHER'(2,1) Swap
000071          AGO  .CONT2
000072 .SKIP2   ANOP
000073 &REYE(3) SETC ' '
000074 .CONT2   ANOP
000075          AIF  (&KEYEC LT 1).SKIP1
000076 &REYE(4) SETC '&EYECATCHER'(1,1) Swap
000077          AGO  .CONT1
000078 .SKIP1   ANOP
000079 &REYE(4) SETC ' '
000080 .CONT1   ANOP
000081 &CBID    SETC '&REYE(1)&REYE(2)&REYE(3)&REYE(4)'
000102 &KCBID   SETA K'&CBID
000103          MVCIN CB.CBIDEYECATCH,=CL(L'CBIDEYECATCH)'&CBID'+&KCBID-1 Eye
000115          MEND

Sent from my iPhone

> On Oct 20, 2020, at 6:51 PM, graeme <[email protected]> wrote:
>
> umm, another meme looking for idle minds to prosper in?
>
> I use eyecatchers A LOT, and I want every instance of the string to be easily 
> find-able.
>
> Cheers from Fort Lockdown,
> The Masked Marauder
>
>> On 21 Oct 2020, at 9:12 am, Keven <[email protected]> wrote:
>>
>>
>>
>>
>>
>>       For the 0.75 seconds it would take to differentiate an eye catching 
>> string in program storage from an instance of it in in use to nominate a 
>> control block, I have to wonder if this is a solution looking for a problem 
>> to solve.
>> Keven
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Oct 20, 2020 at 4:22 PM -0500, "Steve Smith" <[email protected]> 
>> wrote:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> It's not complicated if you know how to manipulate strings in Conditional
>> Assembly. There's no much way around the fact it's vanity programming
>> though.
>>
>> Besides, the technique is defeated by palindromes :-).
>>
>> sas
>>
>>
>> On Tue, Oct 20, 2020 at 4:16 PM Tom Harper
>> wrote:
>>
>>> I already have such a macro. I’ll post it later.
>>>
>>>


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

Reply via email to