EQ – Equal to

NE – Not Equal to
LT – Less than
LE – Less than or Equal to
GT – Greater than
GE – Greater than or Equal to

IF condition in JCL
IF-ELSE-IF and IF is a better way to control the conditional processing of a JCL. In JCL IF
condition is better than the COND parameter because of 2 reasons –
And the IF condition in JCL is easy to code as compared to the COND parameter.
Sometimes, JCL programmers with less experience find COND parameter little con-
fusing and boring and it is easier to read and understand IF-ELSE-END-IF condition
in JCL.
Example
//MATEKSD JOB MSGLEVEL=(1,1),NOTIFY=&SYSUID
//*
//* EXAMPLE TO SHOW IF CONDITION IN JCL
//*
//STEP01 EXEC PGM=IFCOND1
//IFSTMT1 IF STEP01.RC = 0 THEN
//STEP02 EXEC PGM=IFCOND2
//STEP03 EXEC PGM=IFCOND3
// ENDIF
//STEP04 EXEC PGM=IFCOND4
//STEP05 EXEC PGM=IFCOND5
//IFSTMT2 IF STEP05.RC = 04 THEN
//STEP06 EXEC PGM=IFCOND6
// ELSE
//STEP07 EXEC PGM=IFCOND7
// ENDIF
//STEP08 EXEC PGM=IFCOND8
//*
Explanation
//IFSTMT1 IF STEP01.RC = 0 THEN
//STEP02 EXEC PGM=IFCOND2
//STEP03 EXEC PGM=IFCOND3
// ENDIF
This will check if the Return Code(RC) from STEP01 is 0, if yes then execute STEP02 and STEP03.
//IFSTMT2 IF STEP05.RC = 04 THEN
//STEP06 EXEC PGM=IFCOND6
// ELSE
//STEP07 EXEC PGM=IFCOND7
// ENDIF
This will check if the Return Code(RC) from STEP05 is 04, if yes then execute STEP06, else execute
STEP07.
-
Note:
There can be multiple COND Parameter in JCL but a maximum of 8 COND parameter is al-
lowed.
COND parameter can be used at JOB level or STEP level or at both the places.

==
UNLOAD SYSTIN CARD

SYSTSIN DD DSN=TEST.PROCLIB(UNLD) -> This will contain the

details like DB2 level(test or prod) ie, from where we are downloading.
Also the utility, plan and the library used to pickup the utility like be-
low.SYSREC00 will contain the actual unloaded records from DB2.

LOAD
LOAD DATA REPLACE LOG NO ENFORCE NO INDDN SYS-
REC00
INTO TABLE TST.CLIENT.

CHECK PENDING AND COPY PENDING:

Check pending is a tablespace/index status set when DB2 has reason to

believe that an object might be in an inconsistent state. Usually happens
as a result of running LOAD on a tablespace containing a table that has
Referential Integrity constraints, but that was not enforced during the
LOAD OPERATION (ENFORCE NO). (like we used in above exam-
ple). Recovering and RI tablespace to a previous point in time can also
set it. None of this is directly related to the design of the application. If
CHECK PENDING is set you can run the CHECK utility to instruct
DB2 to verify that the data is consistent and switch off the pending sta-
tus.
To remove the Checkpending condition we need to execute the follow-
ing commands on tablespace
for all the affected table space.
REPAIR OBJECT LOG NO
SET TABLESPACE TBLA00DB.TBLB01TS
NOCHECKPEND
REPAIR OBJECT LOG NO
SET TABLESPACE TBLB00DB.TBLB02TS
NOCHECKPEND

COPYPENDING
Any table space will be in copy pending status after load is per-
formed on the DB2 table,
with log no parameter
or
if load is performed without taking an image copy
or
if the job abend during load
or
if NOCOPYPEND parameter is not specified in syspunch dataset
To remove the Copypending condition we need to execute the follow-
ing commands on tablespace for all the affected table space.

REPAIR OBJECT LOG NO

SET TABLESPACE TBLA00DB.TBLB01TS
NOCOPYPEND
————
Connect Reset breaks a connection to a database ,
but does not terminate the back-end process. If an
application is connected to a database, or a process
is in the middle of a unit of work, TERMINATE
causes the database connection to be lost.
————v
How to terminate the abend job ?
Terminate the UTLITY
How to terminate?
use the command -TERM UTIL(UTIL-NAME)
What is this UTIL-NAME?
Its just the LDNM name we use in our load job. In the above exam-
ple, the utility name is
TBLOAD1
where to use this command?
Go to DB2I PRIMARY OPTION MENU -> option 7(DB2 COM-
MANDS)
3. Restart the load job
———————
ILBOABNO is the Abend routine total when user abend occurs in appli-
cation program execution
————————————

Db2 precompile pgm is DSNHPC

Compile step pgm IGYCRCTL
.LINK EDIT -IEWL
Bind and RUN IKJEFT01
CICS map assembled and link edited using pgm= ASMA90

Sysin dd * and parm card. How data retrieved in pgm

Sysin data will be defined in w.s.section.max is 80 chars.
Data via parm received thru Linkage section. MAX IS 100 CHARS.
And use using in P.D statement.

Empty file check

Using ICETOOL,
//TOOLIN DD *
COUNT FROM(SORTIN) EMPTY RC12
/*
In IDCAMS,
//SYSIN DD *
PRINT INFILE(INPUTFL) CHARACTER COUNT(1)
/*

This job returns 04 as return code if the file is EMPTY,other-

wise return code is ZERO. Return code 04 can be checked in
the next
step to identify that the file is EMPTY.
——————
Inspect
Here tallying for no. of chars counted, REPLACING to replace a char
from one to other, DELIMITED BY SIZE or space will stop the adding
upon the ring when it encounters thee SIZE limit of SPACES in the
string to be concatenated.

———————————
———————-
PDS or PS - How you know while creation
PDS - DSORG id PO, for Seq file, DSORG =PS
————————
Versions
—————————————————
OS390 and Z/OS
IBM implemented z/Architecture providing 64-bit real storage address-
ability (from 31-bit = 231 = 2GB) to achieve unprecedented scale in
memory addressing. Note – that this support for 64-bit was retro'd to
OS/390 R10 (last S390 Release) thus began the wane of old to new. The
z/OS 64-bit storage support was available on the new (at the time only)
z900 hardware machines. The new addressing now provides virtual stor-
age capability of 264 equaling 16 Exabytes. That’s 8 Billion times more
virtual storage than offered under 31-bit. IBM also introduced new in-
structions to exploit the 64-bit address scheme. This provided applica-
tions, middleware and subsystems (i.e. DB2) new vertical growth allow-
ing more users and more concurrent transactions. Note – 64-bit apps can
coexist with 31-bit apps, therefore sophisticated applications or middle-
ware can choose to design their support to combine the strength of both
horizontal and vertical growth capabilities. Thus this supports the foun-
dation (backward compatibility) of instruction set commonality between
os390 and z/OS.
—————————————-

ZOS connectivity from from end to cigs

Swagger
Jasan MESSAGES (API). API name, input values
RESTFULL Interface - carries JASAN msg to Liberty server in Z/OS

Server contains API names , request format and equal ant cics Cobol
program name and copybook structure. Jason format msg will be con-
verted to Cobol equalent format as copybook.
Tcp/ip connects and pass the converted API Request to CICS Commn.
Hub.
Rest is backend to extract the response details and the response flows
back to front end after converted to JASAON format.
————————————————————-

AGILE
—————
—————

MQ
—————
—————

CICS Response codes, DB2 SQL Cdes,Batch Abend code, response

code
————-
————-
Syntel tools
———-
CONTROL - M - To submit job
JHL - Job spool

TSO BMC DB2T - To query data in

Or
TSO FAD - File aid

Sputil - Native SP resided in DB2 Server consists of only SQL state-

ments . Can be coded and compiled thru SPUFI or SPUTIL options and
RUN.
COBOL SP is a COBOL Pgm calling SPs as subroutines.

———————-
Citi Treasury and Trade Solutions (TTS)
——————————————————————

MQ
—————-
AGILE-
—————-
Ameriprise Financial, Inc. is one of the leading diversified financial service
companies in the USA,
which provides a wide range of financial planning, products and services de-
signed to be utilized
as solutions for its clients’ cash and liquidity, asset accumulation, income,
protection, estate
and wealth transfer needs including wealth management, asset man-
agement, insurance,
annuities and estate planning.
Project:
CAPS
Project Description

• Project involves managing enhancement and maintenance of multiple sys-

tems for
Ameriprise Financial. This includes Policy Source Systems like Vantage,
TRAD, Claims Processing
Systems CAPS, Client Asset Transmittal, Accounting etc. covering both In-
surance & Annuities.
• CAPS - Claims Administration & Processing System in Ameriprise
handles the Claim set-up,
Payment to beneficiaries & Accounting Reports for different types of
Insurance & Annuity
Products.

Prod support
These are the terms used in IT Support projects to define the level of service
(SLA) and triage for support tickets.
L1 - Level 1 - is the first level of support. L1 support team will respond to
your call/mail/request through other forms, acknowledge, create a support
ticket (if not automatically created already), and assign it to appropriate team.
They monitor the production jobs and applications and check the alerts. They
may also do quick fixes like password reset, account unlock, job restarts
Some of these are already automated/or in the process of being automated
with bots and RPA.
L2 - Level 2 - is the second level of support. L2 team will handle minor en-
hancements, bug fixes, data corrections, business rules, minor framework up-
grades on the servers, etc - generally, fixes that could be deployed within a
day/week instead of waiting for the next Release. Some of the jobs here are
also reduced, esp. in DevOps with CI/CD pipelines.
L3 - Level 3 - is the third level of support, the actual IT team that would un-
dertake major enhancements, functionality changes, business logic changes,
migrations/upgrades that need higher testing effort, etc.