Professional Documents
Culture Documents
Tool Session 05
Tool Session 05
Tool Session 05
-----------------------------------------------------------------------------------
DEBUG
1. COBOL 2. JCL TEST JOB
ONLINE:
1. COBOL -> 1. PROD - DEVL 2. COMPILE (SUBPGM + MAINPGM)
3. MOVE THEM TO TEST
----
CATCH -> DEBUG TOOL -> READY -> WAIT FOR TRIGGER
THROW -> ONLINE SCREEN - TRIGGER THE PROCESS
===================================================================================
=====
TOOL SESSSION 04:
-----------------------------------------------------------------------------------
-------------------
MANY TIMES -> WE NEED TO SEE THE INSIDE THE PROCESSW -> LINE BY LINE
> ANALYSIS
> FIND A BUG.
COBOL+BATCH + JCL
COBOL+DB2
COBOL+VSAM
2. COBOL PGM:
1. U NEED TO COMPILE + XPED OPTION ->
ENDEVOR /CHANGEMAN --> DDIO FILES (REQUIRED FOR DEBUG)
BATCH:
1. SELECT THE PGM
2. SELECT THE JCL (DD NAME OF THE JCL CODE)
F12 -> IT WIL EXECUTE WHOLE PGM TILL IT FIND ANY BREAK
POINT.
BY DEFAULT - BREAK POINT WILL BE (STOP RUN)
TO MONITOR THE VARIBALE -> K (KEEP) -> THIS WILL HELP TO KEEP
THE VARIABLE ON TOP OF THE SCREEN
SQL QUERY IN THE PGM -> FAILED -> U WANT TO KNOW - FOR DATA ITS FAILED
, SQLCODE??
TRAINING -> 3.2 -> CRETED A DATASET - CODE POGM -> 3.4 --> COPY A
COMPILER = SUBMIT
1. CHANGE IN A PGM:
1. CHECKOUT OF THE PROGRAM/COMPONENET /ELEMENT
-> OPEN THE TOOL -> GO TO PROD -ENV OF THE
COMPONENT ->
CHECK -> G - GENERATE
2. STAGE -> CODING -> EDIT THE DEVL -COPY -> E -EDIT ,
V-VIEW , B-BROWSE
- U MAKE REQUIRED CHANGES
1. CHECK OUT -> OPTION G - GENERATE -> COPY THE CODE FROM
PROD --> DEVL
2. STAGE -EDITING -> OPTION E - EDIT --> MAKE CHANGE IN THE PGM IN
DEVELOPER
3. COMPILE -> OPTION F3 + ENTER => COMPILE THE PGM -> NEW LOAD ==>
DEVL
4. MOVE TO TEST -> OPTION DT - DEPLOY TO TEST ==> COPY THE LOAD FROM
DEVL -> TEST
5. PACKAGE -> OPTION TSO PACKAGE / P --> CREATE CODE COPY IN A
PACKAGE
6. EXECUTE --> DONE BY ANOTHER TEAM <- --> MOVE THE CODE FROM DEVL
-> PROD
SCL** ? ->
--> DPLOY THE PACKAGE --> LOAD -> WILL BE MOVE -> PROD ENVIRONEMT OF
UR APPLICATION
ORGANIXZATION -> TRAINEE -> 1-3 -> SOFTWARE ENG -> 4-6 -> SSE --> TECH / MODULE
LEAD --> PROJECT TECH MANG --> DELIVERY MANAGER -> ACCOUNT MANGAME ->,.,
PROJECT:
--------------
OFF-SHORE (INDIA) ON SITE(US/UK/C..)
IT TEAM CLIENT/IT TEAM
--> TODAY U JOIN -> REQUEST/MANAGER -> LAPTOP -> COUPLE OF DAY TO GET A
LAPTOP -> SET UP.
>> MANAGER -> RAISE A REUQEST FOR - RACF-ID (USER-ID ==> IBMUSER)
U BEING NEW FOR THE PROJECT --> I AS ANIL -> 11 YEAR -> SOMEBODY ELSE IS
PLANNING A KT ME
-> COBOL , JCL , DB2 , CICS , Z/OS --> MAINFRAME TECH ->
INTERVIEW -> SELECTED U.
1. IN THE MAINFRAME
1. TEST EVV
2. PROD ENV
DEVELOPING PROJECT
SUPPRT & MAINTENACE PROJECT
SUPPORT -> 1. JOB MONITOR 2., FIX JOB ABEND 3. ROOT CAUSE ANALYSIS
4. USER REQUEST 5. BUF FIX(CODE CHANGE) -- 6 DOCUMENATION -
2. IN PROJECT MESSAGE
TEAMS / SYSPE FOR BUSINESS
4. MAINFRAME
1. COBOL 1. VERSION CONTROL TOOL 1.
ENDAVOR**(SHOW) 2. CHANGEMAN (PPT)
2. DEBUG TOOL 1.
XPEDITOR(SHOW) 2. INTERTEST 3. IBM -DEBUGGER
6. OTHER IF I REMEBER
--> CALL -> HELP DESK -> ANIL -> WE HAVE P2 TICKET (ON CALL SUPT )
TOOL -> ABEND-AID TOOL 1. CHOOSE THE JOB THAT GOT ABEND
2. - D - DAIGINISS -> 1. STATEMENT 2. DATA