Custom Search



NOTE: In the summary section of the sysout, you can tell which elements contained the search string because they will have a number (for the number of matches found) in the far right column - SCL WRITTEN. You can then go back to that section of the scan and find the lines where a match was found.

If you need to scan for many search strings across many Endevor systems (ACES, SUBRO, etc.), take a copy of OTXX94.ENDEVOR.SCANS(SCANALF) and edit it to meet your needs.

- The first statement is a "SET WHERE TEXT" statement that lists all the strings to be searched for. This "WHERE" statement is in effect for each "LIST" statement that follows.

- Next is the "SET OPTIONS" statement. Leave this as is. the "SHOW TEXT" clause causes the scan to show the lines where the search string is found which is necessary if you're searching for more than one string.

- Use the "LIST" statements to search many elements (by using a wildcard) of a particular type in an Endevor system.

In order to submit this SCL, go into Endevor Batch option (3) and specify your dataset in the REQUEST DATA SET section. Use option 3 to submit the scan, make sure the jobname is OTXX94# and that the MSGCLASS on the job card is J for $AVRS. The sysout will show only those elements where one of the search strings was found.

===> //OTXX94# JOB (44001,FS01,00000,1111),'PROJECT C583', => PROJECT NAME
===> //*
===> //*$AVRS C=OTCACTSD =>(comment what program/linkcard/binddeck/sysin)

It's very important to use the proper project number in the jobcard, comment the project name in the comment field of the jobcard, notify your ID of job completion and use the $AVRS C= command to comment on what element you are adding/re-compiling/copying back...etc