TOOL SESSSION 04:

1. COBOL 1. VERSION CONTROL TOOL 1. ENDAVOR**(SHOW) 2. CHANGEMAN

(PPT)
2. DEBUG TOOL 1. XPEDITOR(SHOW) 2. INTERTEST 3. IBM -
DEBUGGER

2. FILE 1. FILE MANAGEMENT TOOL 1. FILE-AID(SHOW) 2.

FILE-MANAGE (IN UR SOFTWARE)
3. JCL 1. SCHEDULER 1. ESP 2. CA 7 3. AJS(SHOW)
4. OPC 5 CTRL-M

4. JOB LOGS 1. ABEND TOOL 1. ABEND-AID (SHOW) 2. FAULT

ANALYSIZER 3. SYSDUMP

5. DB2 1. SPUFI 2. QMF 3. RC (SHOW)

-----------------------------------------------------------------------------------
-------------------

DEBUG -> ->CODE COBOL PGM + COMPILE + LOAD

-> CODE A RUN JCL 0> SUBMIT -> ALL U SEE IS END OF THE PROCESS
--> OUTPUT/FILE / SPOOL /FAILED

MANY TIMES -> WE NEED TO SEE THE INSIDE THE PROCESSW -> LINE BY LINE

> ANALYSIS
> FIND A BUG.

WE NEED TO SET THE PGM IN DEBUG MODE

1. TOOL 1. XPEDITOR 2. INTERTEST 3. IBM
DEBUGER

WE CAN USE FOR BATCH & ONLINE

BATCH -> 1. SET THE BATCH DEBUG

1. ONCE U JOIN THE PROJECT -> U NEED SETUP THE XP
PROFILE

COBOL+BATCH + JCL
COBOL+DB2
COBOL+VSAM

COBOL+ONLINE + CICS -- TAKE DIRECT

HELP OF THE TEAM

2. COBOL PGM:
1. U NEED TO COMPILE + XPED OPTION ->
ENDEVOR /CHANGEMAN --> DDIO FILES (REQUIRED FOR DEBUG)

1. GENERATE (CHECK OUT) -> PROD -> DEVL *OPTION -G

2.NO EDIT (OPTIONAL) -> G -> COMPILE -> USE XPED=
'Y'
3. U NEED TO MOVE THE CODE TO TEST-> DT -> DEPLOY
TO TEST
 3. BATCH -> PREPARE THE TEST JCL

COPY THE PROJECT -TEST/PROD JCL -> UR LIB

CHANGE THE REQUIRED INPUT - OUTPUT FILE

4. GOTO XP TOOL ->

-> 2 - TSO (BATCH DEBUG / ONLINE DEBUG)

BATCH:
1. SELECT THE PGM
2. SELECT THE JCL (DD NAME OF THE JCL CODE)

COMMAND-> END -> TO GET INTO DEBUG MODE;

ONCE UR IN DEBUG MODE:

F9 -> GO 1 -> USED TO EXECUTE THE PGM - LINE BY LINE

F12 -> GO -> + BREAK-POINT
S1.
S2.
..
S50
..
S100 -> UR LOGIC IS HERE 1. SET A BREAK-
POINT (B-BEFORE A-AFTER )

F12 -> IT WIL EXECUTE WHOLE PGM TILL IT FIND ANY BREAK
POINT.
BY DEFAULT - BREAK POINT WILL BE (STOP RUN)

--> EX: VAR-1 -> INPUT -> 10 --> OUTPUT - 20

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??
Tool session 03:-
---------------------------------------------------
> HOW TO DO CODE CHANGE & COMPILE IN THE PROJECT:

TRAINING -> 3.2 -> CRETED A DATASET - CODE POGM -> 3.4 --> COPY A
COMPILER = SUBMIT

TOOL -> VERSION CONTROL TOOL

1. ENDEVOR 2. CHANGEMAN

>> ENDEVOIR - 1. ENVEIRONEMNT 1. PROD --> REAL LIVE

EXECUTE PGM WILL BE HERE > WE CANNOT EDIT , DELETE , IN HERE.
2. DEVE --- CODING
3. TEST TESTING

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

PROD -> COPY -- DEVL

2. STAGE -> CODING -> EDIT THE DEVL -COPY -> E -EDIT ,
V-VIEW , B-BROWSE
- U MAKE REQUIRED CHANGES

3. ONCE UR IN THE PGM , U MADE A CHANGE -> EXIT (F3)

--> SHOW U A SCREEN TO SUBMIT - COMPILE JOB** --
TILL U SEE ->MAXCC=4

4. MOVE THE CODE -> DEVL --> TEST

--> DT -> DEPLOY TO TEST --> WHICH TEST
SYSTEM 1. UNIT 2. SYSTEM TEST** 3. USER A T

5. PREPare the 1. TEST RUN JCL

2. TEST INPUT FILE -WITH TEST DATA
3. TABLE -> PREPARE THE DATA

RUN THE JOB - AS MANY AS MANY AS U SEE THE RESULT.

6. REVIEW - DOCUMANTION -> MEETING -> APPORCAL

7. AFTER APPROCVAL -> CREATE A PACKAGE -> OPTION - P

TSO PACKAGE == IN THE
TOOL

8. CREATE A TASK -> CHANGE CONTROL TEAM -> TO DEPLOY THE

PACKAGE --

DEVL -> PROD -> BACKUP VER

PGM1 -> 1.1 VERSION

CHECK -> 1.1 -> DEVL
CHANGE > COMPILE -> 1.2 - DEVL
CREATE A APCKAGE -=> DEPLOY --> DEVL (1.2) -COPY
-> PROD 1.2

PROD -> COBOL PGM -> 1.2 < NEW VERSION

 COBOL PGM -> 1.1 < OLD VERSION

I NEED TO CHANGE A PGM

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** ? ->

COBOL PGM A LOAD EV-1 --> SRCPGM & LOAD TEST/DEVL

TDSO - DEV
2 -> LOAD 2 -> QUAL
TSO - QUAL
4 -> LOAD 4 ==> PROD
TSO - PROD

--> DPLOY THE PACKAGE --> LOAD -> WILL BE MOVE -> PROD ENVIRONEMT OF
UR APPLICATION

Tool Session 01:-

---------------------------------------------
JUST JOIN THE PROJECT TODAY:

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)

>> KT KNOWLEDGE TRANSFER ->

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.
 2 THING 1. FUNCTIONAL -> WHAT THE APPLICATION IS DOING
2. TECHINCAL --> WHERE IS CODE? , PROD , TEST , QUAL ,
TOOL??

1. IN THE MAINFRAME
1. TEST EVV
2. PROD ENV

2. ALL DATASET NAME 1. ALL COBOL PGM 1. MAINPGM 2. SUBPGM -->

WHAT ARE UR PGM NAME'S
2. ALL JCL JOB
3. ALL PROC LIB
4. CONTROL LIN
5. LOAD LOCATION
6. COPYBOOK*****
7. DB2 -> SUB-SYSTEM - SSID , SCHEMA (TEST - PROD)

3. DAY-TO-DAY WORK

DEVELOPING PROJECT
SUPPRT & MAINTENACE PROJECT

DEVELOPER -> 1. REQURIEMNT 2. DESIGN DOCUMANTION 3. CODEING 4.

TESTING 5. DOCUMENTATION 6. IMPLEMTNTING THE,

SUPPORT -> 1. JOB MONITOR 2., FIX JOB ABEND 3. ROOT CAUSE ANALYSIS
4. USER REQUEST 5. BUF FIX(CODE CHANGE) -- 6 DOCUMENATION -

BOTH DEVE / SUPPORT -> MEETING TO ATTEND.

1. OUTLOOK - MAIL INBOX -- CALNDER**

--> PLACE WHERE U GET UR WORK

-> IN TEAM COMMUCATION 1. MAIL

2. CALL /MISS CALL
3. WHATSMSG
2 MAIL-ID 1. COMPNAY -> XXX@YASH.COM - HR , MANAGE,
TEAM -> BIRTHDAY
2. CLEINT -> XXX@CAT.COM -- WORK ,
ISSUE , .

2. IN PROJECT MESSAGE
TEAMS / SYSPE FOR BUSINESS

3. TICKET TOOL --> SERVICE NOW

-> PLANCE WHERE WE LEAVE EVERY DAY.

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

2. FILE 1. FILE MANAGEMENT TOOL 1.

FILE-AID(SHOW) 2. FILE-MANAGE (IN UR SOFTWARE)
 3. JCL 1. SCHEDULER 1. ESP
2. CA 7 3. AJS(SHOW) 4. OPC 5 CTRL-M

4. JOB LOGS 1. ABEND TOOL 1. ABEND-AID

(SHOW) 2. FAULT ANALYSIZER 3. SYSDUMP

5. DB2 1. SPUFI 2. QMF 3. RC

(SHOW)

6. OTHER IF I REMEBER

A DAY OF A MAINFRAME SUPT PERSON -:

--> START OF THE MONTH -> I SHOULD BE IN NIGHT SHIFT

--> CALL -> HELP DESK -> ANIL -> WE HAVE P2 TICKET (ON CALL SUPT )

SLA -> SERVICE LEVEL AGREENMENT

ACK RESOLUTION
--> TICKET -> PRTY P1 - URGENT 15MIN 2HR -4 HR ->
PROD DOWN -> WORK IS STOPPED -- LOOSING MONEY
P2 - HIGH 30MIN 4-8 -> SAME DAY
=> TODAY WE GOT THIS ONE
P3 - MEDIUM 1 DAY/HR > ANALYSIS = TEST ISSUE
P4 - LOW
P5 - PLANNING -> ADHOC WORK

HOW TO RESOLVE S0C7 ABEND

1. STATEMENT CASUSING THE ISSUE -> COMPUTE , MOVE , IF
COND -> WRONG DATA
2. WHAT RECORD IS CAUSING ABEND -> RECORD

TOOL -> ABEND-AID TOOL 1. CHOOSE THE JOB THAT GOT ABEND
2. - D - DAIGINISS -> 1. STATEMENT 2. DATA

-- WE FOUND THE RECORD -> 1. ABEND-AID / FAULT ANALYSIS

2. FILE-AID
3.SCHEDULER TOOL