|
View previous topic :: View next topic
|
| Author |
Message |
ipavan
New User
Joined: 12 Jun 2005
Posts: 28
Location: Hyderabad
|
|
|
|
| I have an emp file . I got a change request to change the empno field size from 9(5) to 9(7). How to implement the change. First do we need to change the copybooks or whereever the variable empno is there in the programs recordlayout. How to do this . PLz help. |
|
| Back to top |
|
 |
kkk_81
New User
Joined: 09 Sep 2005
Posts: 3
|
|
|
|
| I have an emp file . I got a change request to change the empno field size from 9(5) to 9(7). How to implement the change. First do we need to change the copybooks or whereever the variable empno is there in the programs recordlayout. How to do this . PLz help. |
|
| Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005
Posts: 435
Location: chennai, India
|
|
|
|
| Quote: |
| First do we need to change the copybooks or whereever the variable empno is there in the programs recordlayout. How to do this . PLz help. |
wherever you find this variable in your shop,you should change it.
It is a field expansion project.It consumes around 80% of work in analysis phase. |
|
| Back to top |
|
|
ipavan
New User
Joined: 12 Jun 2005
Posts: 28
Location: Hyderabad
|
|
|
|
Hi Radhakrishnan,
I want to know whether it is sufficient to change the copybook and copy the copy book in our program so that it will be included during compilation time. Or is it sufficien tto change in the recordlayout in the program. |
|
| Back to top |
|
|
MGIndaco
Active User
Joined: 10 Mar 2005
Posts: 432
Location: Milan, Italy
|
|
|
|
What Radhakrishnan said, I suppose(but I can be wrong as usual), is that you must to think to your project and not only at your program.
If you modify this field from 9(5) to 9(7)(i.e. in DB2 or in other files), this change impact all the program that are reading this field!
In applicative concept, if you modify your copybook or your recordlayout(as you need...I'm not a cobol programmer but I suppose that you must to change the length in all the place) you are safe but only you.
Is for this reason that before to change the length of a field all the company do an Impact Analysis.
I hope in this post... |
|
| Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005
Posts: 435
Location: chennai, India
|
|
|
|
| Quote: |
| I want to know whether it is sufficient to change the copybook and copy the copy book in our program so that it will be included during compilation time. Or is it sufficien tto change in the recordlayout in the program. |
It is sufficient to change the copybook if the variable,to be changed,is present only in the copybook.Check whether it is being used as a working storage variable(for performing calculation or may be used for moving a value to the variable).
Better do a scan for that string in your program and copybook library.
Ipavan,
The change may look very simple but the impact proves very costly in case if you havent change it in a single program.
Hope this helps. |
|
| Back to top |
|
|
mmwife
Super Moderator
Joined: 30 May 2003
Posts: 1592
|
|
|
|
This is not a trivial change.
The 1st step is to search your source library (s) for references to the field.
If some pgms move the field to another field, the same process must be performed for that field, and so on.
You'll also find out if the field (s) reside in a copybook or inline or both.
Now you're ready to make your changes.
P.S. You also must check any fields at a higher level than the fields you've found. For example:
01 a-rec.
05 hi-level-fld.
10 your-field pic x(005).
You have to search for a-rec and hi-lev-fld as well and add any fields that they are moved to to your search list.
Gets complicated. |
|
| Back to top |
|
|
|
|
