COBOL - Impact analysis in mainframe

GeekInterview.com > Interview Questions > Mainframe > COBOL

Go To First | Previous Question | Next Question

COBOL | Question 137 of 162

Impact analysis in mainframe

what is meant by impact analysis in mainframes

Total Answers and Comments: 3

Last Update: August 02, 2008 Asked by: ramya05

Sponsored Links

Best Rated Answer

—

Submitted by: kurapati76

Impact Analysis:
If a change requested to an existing process, need to analyse the impact on entities

Interview Purpose
-----------------
Requirement - Size of a field need to be increased in a copybook

Before giving estimation to above requirement, we need to do impact analysis

1. Validate the changes required to the copybook
- If FILLER (unused space) exist, use that space to increase above field. This will save from increasing copybook length
- If no FILLER exist in copybook, increase field length, which will increase copybook length
2. Search for Programs used this copybook. Analyse the usage of field in these programs. If the field value is moving to any working storage field, start analyse the impact of that working storage variable
- If the program is a sub-program, validate if this field moving to main program through linkage section variable
3. Validate the files linked to the copybook
4. If the filed value is moving to any database, then validate DCLGEN
5. If the value moving to any online programs, analyse if it requires any changes to online screen

Above answer was rated as good by the following members:
i_virus

May 06, 2008 02:12:10

guraddiv

Member Since: April 2008 Contribution: 18

RE: Impact analysis in mainframe

Hi Ramya

Impact analysis is not particularly for mainframe its a general one. In mainframe Impact analysis means if u want to change any program than we have to check what are all the programs jcl's copybooks procedures tables files related to that program will going to effect(change). if u r coding frm the scratch itself then no need of the impact analysis.

Is this answer useful? Yes | No

June 19, 2008 12:18:42

kurapati76

Member Since: June 2008 Contribution: 1

RE: Impact analysis in mainframe

Impact Analysis:
If a change requested to an existing process need to analyse the impact on entities

Interview Purpose
-----------------
Requirement - Size of a field need to be increased in a copybook

Before giving estimation to above requirement we need to do impact analysis

1. Validate the changes required to the copybook
- If FILLER (unused space) exist use that space to increase above field. This will save from increasing copybook length
- If no FILLER exist in copybook increase field length which will increase copybook length
2. Search for Programs used this copybook. Analyse the usage of field in these programs. If the field value is moving to any working storage field start analyse the impact of that working storage variable
- If the program is a sub-program validate if this field moving to main program through linkage section variable
3. Validate the files linked to the copybook
4. If the filed value is moving to any database then validate DCLGEN
5. If the value moving to any online programs analyse if it requires any changes to online screen

Is this answer useful? Yes | No

1 0

Overall Rating: +1

August 02, 2008 07:31:24

hmp_8304

Member Since: August 2008 Contribution: 3

RE: Impact analysis in mainframe

When you do some changes in any object (e.g. Cobol Copy book or table or proc or card). Due to that change how many elements are implected? This is called Implecte Analysis.

Is this answer useful? Yes | No

Go To Top

User Name		Remember Me?
Password

Question Bank