CEMT commands in JCL

Pandora-Box · Posted: Thu Aug 02, 2012 11:40 am

Hi all,

I encountered a strange thing while executing CEMT commanda in Jcl

The commands that I executed where

Close a file in FCT
Do process of replacing file contents
Open the file again

The job executed successfully as file contents were replaced
but the file was still closed

But where as I split the above function to two different jobs the file was closed,replced and opened again for cics process

I had

Close file
Replacing the file contents in one job and open file in another

The job executed successfully as expected

My question here is

Do the CICS commands given in jcl stack up like LIFO?

Please clarify

dbzTHEdinosauer · Posted: Thu Aug 02, 2012 12:05 pm

i have always used the sequence:

disable
close
proceess
enable
open

1 job

and it is FIFO

Pandora-Box · Posted: Thu Aug 02, 2012 1:43 pm

Ok will try it and get back to you Dick

Thanks

Robert Sample · Posted: Thu Aug 02, 2012 2:12 pm

How did you close the file -- using a program, or a vendor package, or issuing a console command via JCL?

How is the file defined in RDO (CEDA)?

dbzTHEdinosauer · Posted: Thu Aug 02, 2012 2:27 pm

my answers are predicated on my experience with a few vendor packages
that provide Batch CEMT transactions.

Robert's questions are more important,
since what ever you are doing may have nothing to do with my experience.

Pandora-Box · Posted: Thu Aug 02, 2012 3:58 pm

Hi Robert,

I issued console comands in JCL

dbzTHEdinosauer · Posted: Thu Aug 02, 2012 4:04 pm

dbzTHEdinosauer · Posted: Thu Aug 02, 2012 4:12 pm

Sorry, do you mean issuing CEMT transactions thru batch jobs
using either 3rd party tools or something written inhouse,
or is there an IBM utility that does this?

Pandora-Box · Posted: Thu Aug 02, 2012 4:17 pm

Hi Dick,

Apologies for my bad use of vocabulary

I issued CEMT commands via JCL Using IEFBR14 utility

Robert Sample · Posted: Thu Aug 02, 2012 4:30 pm

Then you need to be aware that console commands in JCL are executed as soon as the job gets an initiator -- ALL of the console commands. They don't wait until the appropriate moment when that step is executed, they run right away. Hence your batch job is NOT performing as you expected and you need to re-evaluate your approach.

dbzTHEdinosauer · Posted: Thu Aug 02, 2012 4:34 pm

ok, yeah i was bitchen about terminology, my apologies,also.

by the way, Pandora-Box,
what was the disposition of the VSAM file during the batch run?

if during the update, the disp=old,
that could be a reason the CEMT transactions to reopen the file in CICS,
if issued in the same job,
did not work.

Pandora-Box · Posted: Thu Aug 02, 2012 4:49 pm

Hi Robert,

Thnaks
So I would have three jobs

one to close
one to process
one to enable n open it

Hi Dick,

yes my vsam is of disp=old
As Robert explained Its better to have three different jobs

Thanks all

enrico-sorichetti · Posted: Thu Aug 02, 2012 4:55 pm

and even then You might not be sure about the proper sequence !
( if submitted by hand in one shot )
might work if a scheduler is used.

Pandora-Box · Posted: Thu Aug 02, 2012 5:00 pm

Hi Enrico,

Yes I am making use of scheduler only

Thanks

Robert Sample · Posted: Thu Aug 02, 2012 5:17 pm

If you're doing the close / disable in one command, you can get by with just two jobs: one to close / disable the file in CICS via console command in step 1 of the job, then step 2 of the job runs your update program, then a separate job to open / enable the file in CICS -- as long as the second job does not start until after the first job completes.

Pandora-Box · Posted: Thu Aug 02, 2012 5:33 pm

Hi Robert,

I just realised two jobs should suffice already and got it done

Thanks anyway

Robert Sample · Posted: Thu Aug 02, 2012 5:41 pm

Great! Hope it goes well, then.