To restart a transaction at 2 AM every Day

mukun264 · New User Joined: 01 Jan 2008 Posts: 32 Location: Bangalore

How to restart the transaction at 2 AM every day or just after 2 AM?

Pandora-Box · Posted: Fri Jun 29, 2012 2:09 pm

Restart the transaction do you mean enable??

Garry Carroll · Posted: Fri Jun 29, 2012 2:20 pm

The Friendly Manual would suggest :

EXEC CICS START TRANSID('xxxx') AT HOURS(02) MINUTES (0)

Garry.

mukun264 · New User Joined: 01 Jan 2008 Posts: 32 Location: Bangalore

I mean suppose:

Today transaction executed at 020000( 02 AM) so after successful execution the transaction should schedule for tomorrow to execute at 02 AM and so on

Hope I explained

Pandora-Box · Posted: Fri Jun 29, 2012 2:34 pm

Have a job which executes the command suggested by Garry schedule it

mukun264 · New User Joined: 01 Jan 2008 Posts: 32 Location: Bangalore

I have gone through the manual. there is an drawback of the command.

Suppose the transition execute successfully at 02 and again schedule 02 then cics will execute immediately. i have tested also. the transaction is getting triggered at continuously after 02 AM.

I use below code before end of the transaction XXXX

START TRANSID(XXXX) AT HOURS(02) REQID(‘XXXXID’)

But xxxx is getting triggered every time after 02 AM

Nic Clouston · Posted: Fri Jun 29, 2012 3:09 pm

As Pandora-box suggested - have a job submit the command. Have your scheduling software submit the job at 2am.

mukun264 · New User Joined: 01 Jan 2008 Posts: 32 Location: Bangalore

Transaction is getting scheduled in online in same program.

Garry Carroll · Posted: Fri Jun 29, 2012 3:45 pm

You could modify the transaction so that, at the end, it issues a (short) EXEC CICS DELAY before issuing the EXEC CICS START ....

Garry.

Robert Sample · Posted: Fri Jun 29, 2012 4:57 pm

Why not use

mukun264 · New User Joined: 01 Jan 2008 Posts: 32 Location: Bangalore

in ideal scenario this will work to trigger the transaction at interval of 24 hours ( i mean 2 AM), but assume the transaction failed at 2 AM and after correction the issue its triggered at 3 AM then onward transaction will be triggered every time at 3 am.

Pandora-Box · Posted: Fri Jun 29, 2012 8:55 pm

Why not disable the transaction after run?

Nic Clouston · Posted: Fri Jun 29, 2012 8:55 pm

So extract the command to start it from the online and stick it into a batch job. You have a problem - you need a fix - a proper fix, not a band-aid. It may be a little bit of extra work but it fixes it properly.

Pandora-Box · Posted: Fri Jun 29, 2012 9:01 pm

What you can do is have an EXCI intetface calls the transaction and have a RC set for the transaction and return it back to EXCI intetface

so based on Rc from transaction set the return code for the step and disable the transaction

Experts would have better solution

Bill O'Boyle · Posted: Fri Jun 29, 2012 9:04 pm

The Batch part of product CAFC can issue START's of transactions in targeted regions or write an EXCI client program which issues a DPL to a target server program in a given region, which issues a START of the transaction.

There are many ways to do this, as others have suggested, but it might be more controllable via Batch.

Robert Sample · Posted: Fri Jun 29, 2012 9:26 pm

It sounds like you're trying to do system design on the fly, which rarely has good results. If the timing is that critical, you either need to have a job submitted by your job scheduler at the correct time each day to implement the CICS transaction (which can be done via JCL command, or FEPI, or by vendor product, or possibly even directly by your scheduler), or you need to handle it within CICS -- for example, write a record to a VSAM file that contains the time stamp the tranaction last ran; you can then use that value to verify the timing and even allow for restarts when necessary.

Shooting down the suggestions people on this forum make because you keep adding "requirements" not stated in your initial post, however, is NOT the way to design the system.

dick scherrer · Posted: Fri Jun 29, 2012 10:06 pm

Hello,

Is there any Business reason this needs to be run in CICS at 2am every day? Please do NOT say "this is the requirement". It is NOT the requirement. The requirement is to get this process accomplished once a day at 2am (whatever this process does).

If we knew why someone believes this is a proper implementation, we might be able to offer different suggestions.

dbzTHEdinosauer · Posted: Fri Jun 29, 2012 10:06 pm

i read back thru this thread (again!)
and a point comes to mind
that I not so politically correctly stated in another thread.

what event occurs at 0200 every night that this CICS transaction satisfies?

you have available about a billion or so years of computer experience,
so one (or many) may have already
bruised their knuckles on stone wheels
while trying to solve this exact same problem.

so, were we to be privy to the reason you need a cics task started every night a 0200 hrs,
there may float to the surface a solution that has been tried before and works.
an by works,
i mean a procedure that underwent the tests of time,
and the little patches here and there were jammed-in
and it doesn't cause any more problems.

but,
that is just me.

DEEPA MANI · New User Joined: 21 Oct 2022 Posts: 2 Location: India

@Muhun

I have similar requirement to start transaction every at same time. When I give hour as 01, it starts the transaction at 1 and running continous without stopping.

Is there any solution for this

Have you got any solution for your cics transaction

Garry Carroll · Posted: Fri Oct 21, 2022 2:42 pm

Don't tag on to 10year old posts - start a new thread and outline your issue clearly.

Garry.