o

1
Modules: COBOL, DB2 and
JCL
LAB2 Question ID:

Duration: 4 Hr

2D

Login Note:
o
o
o
o
o

Connect to IP Address 10.237.206.10 and Port 23.

Logon using the MF ID provided, for the Lab Assessment
Use password same as your User ID.
Enter the new password (8 characters combination of alphabetic and numeric.
Read INSTRUCTIONS section to create the deliverables.

NOTE
o

Use your own MF IDs provided, for the Lab Assessment

-> DATABASE: DBLAB01
-> TABLESPACE: Use the below details for Table space name based on the
provided MF ID.

-> PLAN:LABPL<yyy>, PACKAGE: LABPK<yyy>.

<yyy> Denotes last 3 digits of your new MF ID.
The Bus maintenance system maintains the bus organization details in the database
BUSORG_DET1 and the corresponding issue details of the buses in BUS_STAT1 for the
ease of access and maintenance. The system fetch the detail of buses who has an issue and
whose issue fine is greater than or equal to 100.
To make this team perform these operations and achieve its requirements, develop the below
modules:

DB2:
1. Using SPUFI, create a table BUSORG_DET1 with the below columns, to keep track
of the bus details:

(Bus_Num, Bus_Typ) together forms the Composite Primary Key

2. Using SPUFI, create a table BUS_STAT1 with the below columns, to keep track of
the bus details:

3. Using SPUFI, insert the sample values into the corresponding tables:
i)

BUSORG_DET1 table:- Input Values:

ii)

BUS_STAT1 table:- Input Values:

COBOL:
4. Using a COBOL program, with the help of embedded cursor get the bus details
(Bus number, bus start location, bus end location, bus type, bus issue ID, bus issue
description, fine) by joining BUSORG_DET1 table and BUS_STAT1 table whose bus issue
fine is greater than or equal to 100.00 into the PS file <TLABID>.BUS.ISSUE.DET of length
80 bytes in the below layout.
File Layout:-

Filler Details: One space between each field and the file length is 80 bytes._
DB2:
5. Using SPUFI, find the count of buses in each bus type is AC / UDX. (Form Table :
BUSORG_DET1)
JCL:
6.

Compile and execute the above COBOL program.

Note: Sample compile and run JCL is available in

TLABADM.LAB.SYS.COMPRUN.

INSTRUCTIONS:
o

Follow the coding standard and error handling as applicable.

Copy the final modules in the PDS <TLABID>.<X>.<Y>.PDS.

Where X -> L2/L2AT1 (L2 for first attempt, L2AT1 for second attempt) and
Y denotes 8 digit Batch name. Example: Y- CHNMJ010
[Example for Lab2 PDS - TLAB001.L2.CHNMJ001.PDS
Example for Lab2 Attempt-1 PDS - TLAB001.L2AT1.CHNMJ001.PDS].

Follow the below naming convention for the members, where the JCLs, SPUFI inputs
need to be placed:
o For JCLs, the member name should be JB<x>2D<yyy>
-> Note: Where <x> denotes the member number and <yyy> denotes the
last 3 digits of your user ID.
-> Ex: If there are 2 members for JCL created by ID TLAB001, the member
name should be JB12D001 andJB22D001
o

For SPUFI, the member name should be SB<x>2D<yyy>

-> Note: Where <x> denotes the member number and <yyy> denotes the
last 3 digits of your user ID.
-> Ex: If there are 2 members for SPUFI created by ID TLAB001, the
member name should be SB12D001 andSB22D001

For COBOL, the member name should be CB<x>2D<yyy>

-> Note: Where <x> denotes the member number and <yyy> denotes the
last 3 digits of your user ID.
-> Ex: If there are 2 members for COBOL created by ID TLAB001, the
member name should be CB12D001 andCB22D001

For DCLGEN, the member name should be DB<x>2D<yyy>

-> Note: Where <x> denotes the member number and <yyy> denotes the
last 3 digits of your user ID.
-> Ex: If there are 2 members for DCLGEN created by ID TLAB001, the
member name should be DB12D001 andDB22D001.

EXPECTED DELIVERABLES in Mainframe PDS:

o
o
o
o

COBOL program
RUN JCL
SPUFI Inputs
DCLGEN

EXPECTED DELIVERABLES to be uploaded:

o
o

Upload all the expected deliverables as separate notepads in the mentioned area.
Upload a notepad with name <TLABID>_DETAILS and mention your Associate ID
and Lab Mainframe ID used in the assessment.

Availabl
e from:
Due
date: