Skip to main content

Impact Analysis


Impact Analysis :

I hope Below informaiton will provid you brief information on various steps involved in impact analysis ( when ur asked to add a new field?)

Impact Analysis : This is a process to identify the various Copy books or Programs of Jcls or DB2 table etc are to be modified/impacted due the new changes , to meet the requirement.As per the requirement, programmer will have an idea, like what are the New fields/Existing field to be added/modify in

1. Copy Books

2. Files/Jcl

3. Database

4. In online Screen etc.


1. Impact Analsys On Copy Books (used by cobol programs) :

  • Identify the copybooks to be modified as part of requirement in list1

  • Now search for various copy books Impacted because of the copy books listed in list1 and note them into new list List2

  • Now search for various copy books Impacted because of the copy books listed in list2 and note them into new list List3

  • Above process is continued till the search returns zero copy books impacted.
    Merge all above lists and eliminate the duplicate copy books from them.
    Now find out the various programes which are using the above list of copy books and list them in Excel Sheet

2. Impact Analsys On Files/JCL :

  • Find out the Varous JCL/Procs impacted due to change in File length.

  • Find Out Varous JCLs/Procs impacted due to Sort cards/ Datalibs impacted due to above change.

3. Impact Analsys On DB2 tables :

  • Find out all the tables impacted due to addition of new table fields
    Find out the load cards impacted due to these changes

4. Impact Analsys On CICS screens :

  • Identify various screens/screen programs impacted due to addition of new fieldsTip : Use 3.13 option on mainframes to search a field in specfic lib.


Comments

sanjuu said…
wow...excellent explanation...

the copy book impact analysis is really awesome idea..:)
February 1, 2012 at 3:15 AM
The Serene Land said…
I had developed an Xref and Impact Analysis Tool for Mainframe Applications sometime back. Please have a look at it at http://atomkpadhy.blogspot.in/2013/06/xref-and-impact-analysis-tool-for.html
July 3, 2013 at 6:18 AM
Post a Comment

Popular posts from this blog

Mainframe Written test @ Accenture

1. What r the 2 function we can get by using INSPECT verb? (c) A. file handling, error handling B. opening a file, closing a file. C. char counting, replacing. D. none of the above 2. Indicate which of the following is not true about the formal parameters in a subroutine? (c) A. every formal parameter must appear in the linkage section of the subroutine B. every formal parameter must appear in the using phrase of the procedure division header of the subroutine C. A formal parameter name can appear more than once in the using phrases of the procedure division header of the subroutine. D. A formal parameter can not be declared with value clause in a subroutine 3. What is the value of A? (B) 01 A pic 9(3). Move 100 to A. Perform 1000-para thru 1000-exit. Display the value of a=A Stop run. 1000-para. If A=100 Perform 1000-exit Else Move 150 to A End-if. Move 200 to A. 1000-exit. Exit. a.100 b.200 c.150 d. none of the above is correct. 4. What is the value of B? (A) Move 1 to A Evaluate tr
2 comments
Read more

NULL VALUES and NULL INDICATORS in DB2

In DB2, the columns defined as NULL needs to be handled carefully else it will throw null exception error, in order to over come this error data type can be handled by using null indicator . NULL is stored using a special one-byte null indicator that is "attached" to every nullable column. If the column is set to NULL, then the indicator field is used to record this. Using NULL will never save space in a DB2 database design - in fact, it will always add an extra byte for every column that can be NULL. The byte is used whether or not the column is actually set to NULL. The indicator variable is transparent to an end user Consider below Table : Create Table SAMP_TAB SN CHAR (10) SNAME CHAR (10) STATUS CHAR (2) NOT NULL BY DEFAULT CITY CHAR (10) NOT NULL Note :: Unless you specify NOT NULL, the default is to allow for NULL In above table SN and SNAME columns holds null values by default, in order to handle these null variables we need to have NULL-INDICATORS declares in the Pro
15 comments
Read more

How to Solve SOC7 Abend - with screen shots

Below process helps to find out the statement, caused the SOC7 error. Check the Sysout of RUNJCL . This shows the error statement and lists offset value Take the Offset Value 000003C0 Got to respective Compilation Job listing, check the sysprint Search for the offset value 0003C0 (delete +00 -- initial 3 letters of Offset value and search for it) check below 2 screen shots This Offset value is listed under line no 0045 – which refers to Move statement. Take this no. 045 and find for it in same sysprint. This points to the exact statement, caused SOC7 T his 045 pints to the Move statement 1526, this is the exact line in the program Check for the above line no. In source program . This points to the statement highlighted below . Check the statement, variable check-4, which is added to check-6. These are having different Picture clause. check-4 is alfhanumaric, holding some junk data, when this data is moved to Chcek-6 variable(of comp-3) creates SOC7 error. This is just an example to e
16 comments
Read more