IMS Basic Checkpoint concept

Robin Issac Philip · New User Joined: 19 Feb 2006 Posts: 1 Location: Kerala

Hi all,
I have encountered a problem while running a DLI IMS program.
The program does:
1. Reads a sequential file.
2. Access an IMS-DB in read mode (PROCOPT=GOTP)
3. Invalid records are written to a VSAM file

Problem:
While accessing the IMS-DB, my job ends up with status code GG. This is because the same database is being accessed in update mode (PROCOPT=AP) by some other job.

Question:
Can I issue a checkpoint (basic) without any restart logic in my IMS program (i dont need restart since db is not being updated by my program)?
If yes, what are the considerations to be taken?
If no, is there any other alternate approach to solve my issue

Robin

sudheer.nalubolu · New User Joined: 09 Dec 2005 Posts: 1

Hi Robin,

You can always issue a basic check point without restart logic, but how can that solve your problem....

Correct me if i am wrong...

Thanks and regards,

Sudheer.

martin9 · Posted: Mon Mar 13, 2006 2:56 pm

hy,

there are two things:

1. you can run an IMS job as a BMP
2. you can run an IMS job as a DLI

waht is now the difference?

as BMP, you can do everything, with almost no restrictions,
because you are running the job under IMS control region.
therefore also checkpointing is no problem.
database intergrity is done by the resource manager.

if you do this as a DLI and there is any update pcb,
you have to close the databases first! but note:
if you make updates and there is any error, you
have to reinstall database integrity youself!

correct the job and let it run as a BMP job!

martin9