ISREDIT - Replace string - Exceeding line length issue

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Hi all,

Using ISREDIT macro, I am searching and replacing the string in PROClibs.

For example, in the below mentioned PROC, I need to change all the occurances of string XYZ to ZPNDVR.ABC and all the occurances of ABC to ZPNDVR.ABC.

//TESTN1 PROC ENVI1='XYZ',GNBO1='XYZ',GNVR2='ABC',JNKQ2='ABC',
// ZERO='(0)',QTRERFG='(+1)',HLQAO='ZPNDVR',

On running the ISREDIT macro,

ISREDIT MACRO (PROCESS)
ISREDIT C "'XYZ'" "'ZPNDVR.XYZ'" ALL
ISREDIT C "'ABC'" "'ZPNDVR.ABC'" ALL

the strings got replaced fine BUT the line exceeds above 72 bytes.
Could anybody guide me how to get rid of the exceeding line length issue

Thanks
Chidam

Pedro · Posted: Wed Aug 13, 2008 10:42 pm

1. Use FIND macro statement to locate the text.

2. Use the LINE macro statement to get the entire line into a rexx variable.

3. Use Length(Strip(abc)) to get length of text.

4. split the line if you need to. Use LINE_AFTER macro statement to add a new line.

And to it all within a loop so that you FIND one occurrence at a time instead of changing all with one command.

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Pedro,

Thanks for the steps.
As the third step, I tried getting the length of PROC but got some error

Code
ISREDIT CURSOR = 1 1
ISREDIT (LINE) = LINENUM .ZCSR
ISREDIT (LNE1) = LINE .ZCSR
SET LNELEN = &LENGTH(STRIP(&LNE1))
ISREDIT LINE_AFTER &LINE = DATALINE '&LNELEN'

When the above code is executed to retrieve the length of
//INS0202 PROC DERI1='AIR',ENVO1='AIR',ENVI2='ABC',ENVO2='ABC',

I got the error as
"THIS STATEMENT HAS AN EXPRESSION WITH OPERATORS OUT OF SEQUENCE"

Is it because of the quotes residing in the first PROC line.
Is there any way to get rid of that. Please help me.

Thanks
Chidam

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Hi,

The above problem regarding getting the length of lone is solved but landed in new problem

If a string has comma or special charcters, convert into string and then take the length
SET LNELEN = &LENGTH(&STRIP(&STR(&LNE1)))

Now the problem is, the line length is always given as 80bytes eventhough it has only 60 bytes and rest as blank spaces.
Since we are converting to string and then using STRIP command, it is showing as 80 bytes.

Could you plz help in getting the syntax of getting the exact line length without blank spaces.

Thanks
Chidams

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Hi all,

Any idea how to split up the line (which is converted to string as shown in above code) based on words

Thanks
Chidam

Pedro · Posted: Thu Aug 14, 2008 9:49 pm

I think you are running into CLIST issues. Can you use REXX?

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Ya..I think so
I am using ISREDIT macro to change all the prod qualifier to test qualifier
of the impacted jobs and procs.

As per my understanding the below code is CLIST macro, right

ISREDIT MACRO (USRID)
ISREDIT CURSOR = 1 1
ISREDIT (LINE) = LINENUM .ZCSR
ISREDIT (LNE1) = LINE .ZCSR
SET LNE2 = &STR(&LNE1)
SET LNELEN = &LENGTH(&STRIP(&STR(&LNE2)))

1. If itz not, how can we convert this to REXX macro
2. Is there any function to split the line based on the length

Your help is appreciated

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Ya..I think so
I am using ISREDIT macro to change all the prod qualifier to test qualifier
of the impacted jobs and procs.

As per my understanding the below code is CLIST macro, right

ISREDIT MACRO (USRID)
ISREDIT CURSOR = 1 1
ISREDIT (LINE) = LINENUM .ZCSR
ISREDIT (LNE1) = LINE .ZCSR
SET LNE2 = &STR(&LNE1)
SET LNELEN = &LENGTH(&STRIP(&STR(&LNE2)))

1. If itz not, how can we convert this to REXX macro
2. Is there any function to split the line based on the length

Your help is appreciated

Pedro · Posted: Fri Aug 15, 2008 12:02 am

Usage of rexx is similar to clists.

To convert to rexx:
1. put /* rexx */ as the first line
2. add ADDRESS ISREDIT statement
3. make your editor macro statements into literal strings
4. use rexx builtin functions

Example:

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Thanks for the info. I tried converting to REXX instead of CLIST and was able to get the correct line length.

My aim is to split the line if its length is greater than (say 45 bytes) and writing it to the immediate below line BEFORE changing the production high level qualifier to test high level qualifier in the PROC.

Could you plz correct me if my approach is wrong.

1. First find whether the qualifiers that I am converting is there in the line.

2. If YES, then get the length of the whole line to rexx variable. Positon
the cursor to the byte where " ', " is there from the 45th byte of the
whole line. (Mainly truncation happens only to symbolic variables which
is declared at the starting lines of the PROC).

3. Read the remaining contents after " ', " and storing it in REXX variable

4. Having a new line and add // to it and then the saved contents to the
next newly added line after pos 16.

Pedro · Posted: Fri Aug 15, 2008 3:52 am

Use the PARSE instruction to break the line apart, something like this:

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Pedro,

Thanks for the suggestion..
I had made the code as follows; i.e., finding the High level qualifier and then finding for " '," and then getting the line after " ', " in a variable and put it in next line.

Pedro · Posted: Fri Aug 15, 2008 9:14 pm

I do not think you need to know the number of them. Your loop should be controlled by the return code from FIND. Issue the FIND and only do your other processing if rc=0. If it is not zero, get out of the loop.

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Ya..that will be fine.
Now I am thinking for the other alternative because I had 15 production variables in a PROC to be changed to test naming standards. So i think it is not a good thing to check the same full logic for the 15 variables.

Will this approach works out

1. Just read a line of PROC and if the first 3 charcters of that line are
not //* (comments) then check for " ', " after the 45th byte of that line.

2. Get the remaining line contents of that line (if it is present) and then
insert it into new line.
Note: Obviously the " ', " won't be present in the DSN names and will
be present only for symbolic variable declarations in the PROC

If this approach holds good, how we can read each line by line by puting a loop in REXX

enrico-sorichetti · Posted: Fri Aug 15, 2008 9:45 pm

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

In the above code, first we are getting the first and last line numbers and then execute the loop that many times.

Can you please help me understand what the "LINE.I = TEMP" does.
Anyways we will be getting the current line in "temp" variable and we can manipulate the line with that, right

Also I didnt understand the "ISREDIT (temp) = LINE linenum ". Here from where LINE gets the value.

Please help

enrico-sorichetti · Posted: Fri Aug 15, 2008 10:13 pm

here is a link to the ispf bookshelf

Pedro · Posted: Fri Aug 15, 2008 11:11 pm

I think your first approach,of using FIND, is cleaner programming.

I think it should be something like this, where the change is done from a subroutine, and the driving program just tells it what to change:

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Thanks Pedro..That program logic holds good.I had implemented and it works gr8..:-)

Concern:
For changing the text DFG to UBA#BA,B2, we can code in REXX macro as
"ISREDIT C 'DFG' 'UBA#BA.C2' ALL"

But if I need to change the DFG qualifier if it between the quotes, whether there is any way to do so

If it is CLIST macro, i can code as
ISREDIT C " 'DFG' " " 'UBA#BA.C2' " ALL

But since we are using REXX macro, we already have quotes before ISREDIT statement. So whether there is any way to change the text only if it is between the single quotes.

Pedro · Posted: Mon Aug 18, 2008 10:01 pm

Whenever I have conflicts between macro syntax and data in the file, I temporarily change the file:

chidams78 · New User Joined: 29 May 2006 Posts: 59 Location: India

Thanks Pedro for your suggestion. Indeed it was somewhat tricky logic.:-)

The other problem I had encountered is,
When the macro is exeuted in the PROC, it changes the existing TAPE name to TAPE,RETPD=60, thereby truncating the below shown lines 5 and 8.

//TST0222W EXEC PGM=SORT
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=UBA.INS.QTRGRST.TEST1,
// DISP=(OLD,KEEP,KEEP),
// UNIT=&TAPE,LABEL=1,VOL=,RETAIN,REF=*.TST020.PRINTR)
// DD DSN=&ENVO2..INS.QTRUNIST.SPOOL,
DISP=(OLD,KEEP,KEEP),
// UNIT=&TAPE,LABEL=2,VOL=,RETAIN,REF=*.TST0202S.PRINTR)

The logic i thought to handle this situation is like
1. Just search for DISP= after the column number 35 and if it is
encountered, put it in new line. The same thing for UNIT= and VOL=
Note: The disadv with this logic is that we will be unneccessarily puting all
the DISP=, UNIT= and VOL= into the new line even if the variable
in that line is not changed.

Whether this logic holds good or is there any other good logic to acheive this result