How do we do the remediation process in COBOL?.
Here my requirement is, I need to make some constant changes to the existing 1200 COBOL programs(i.e. Need to add a FILLER at the end of the existing record and have to find out the locations, where this record being used and accrdingly do the changes etc.), for that, I would like to know is there any methodology or any tool, we can use to do this process.
HI Mohan,
I will suggest to develop a tool to find out the position where your intended record is being used. Then add the statements regarding the newly-required FILLER. I dnt think there is any other way (except using a tool) you can do this.
Joined: 22 Nov 2005 Posts: 700 Location: Troy, Michigan USA
Mohan
What is the repository for the source code? PDS, Endevor, Panvalet ?
I hope that there is a copybook for the file layout. Even if there is, you will need to look for programs that are 'hard coded', sorts, utilities that do not have copybooks. I've done this type of change a couple of times. At the best it's a long, tedious process.
Come back with answers and I may be able to give some suggestions,
Joined: 22 Nov 2005 Posts: 700 Location: Troy, Michigan USA
Hi Mohan,
Do you have a PANVALET Reference book available? PANVALET has a utility 'PAN#8' that can scan for strings.
You will need to scan for the copybook name. You find them in COBOL "COPY" and PANVALET "++INCLUDE" statements.
I looked for an old PANVALET reference book, but we have not used PANVALET in over 10 years.
There is also an option that unloads the entire PANVALET source to a PDS. Then you can use ISPF 3.14 to look for your strings.
Once you have isolated all of the programs that use the copybook you'll somehow have to look for any programs that have it hard coded.
Then you'll have to track down all of the input/output datasets to see where they came from/going to.
You said that there are 1200 programs. Is this that number of programs you need to inspect, or the number you need to change?
If you are adding fields to the bottom of the copybook, any program that does not need to use the fields can simply be re-compiled with the larger copybook.
Have you given consideration to an implementation scenario? Depending upon the number of programs that need to change there are several scenarios you might consider.
1 ? The big bang implementation. All Programs, Utilities, and JCL get implemented the same day. If the number of programs is large, this can be a daunting endeavor.
2 ? The group implementation. All programs, Utilities, and JCL within a defined independent group get implemented the same day. This requires you to define small groups of jobs that are affected, maybe only 3 - 10 jobs. This probably will require multiple programs changes to some of the jobs.
----i.e. JOB A feeds JOB B that feeds JOBs C and D. JOB D is a report and does not pass the file along. JOB C processes the file and feeds JOB F. For the copybook, you define a new copybook with the new layout. JOB A reads the OLD Copybook format, processes and creates a NEW copybook format. Jobs B, and D all are changed to use the NEW copybook format, JOB C is changed to read the NEW copybook format, and write the OLD copybook format. These are implemented as a controllable group, but at some time you will need to change JOBs A and C to fully use the NEW copybook format.
3 ? Another Scenario might be the Auxiliary file implementation. Don?t change the copybook. Depending on how many programs are going to be using the new fields, you can create another file, keyed the same as the original file with the additional fields added. This only needs to be added to the programs/JOBs that will use the new fields. It does require additional programming for those programs to read both files and keep them in sync. You could even write a common subroutine that would perform the task.
I?ll still continue to look for a PANVALET Manual. Maybe you could do a search of the forum to see if anyone has posted something before on PANVALET PAN#8 Scan. If not, try posting the question. A lot of people use PANVALET, I?m sure you would get responses.
Also, you will need to give consideration to change control. How do you make program changes and warehouse the change until implementation, and still allow for PRODUCTION Fixes and enhancements to the same programs. I can tell you this will be very frustrating when there is an abend that requires a change to one of the programs you have changed, or a client call with a ?HOT? change that?s needed, and you find your change has taken a back seat to their change. This is one of the reasons that the small implantations are nice, you have to warehouse the changes for a shorter period of time.
