Re: CICS kickoff online users

On Sat, 23 Sep 2006 21:42:40 GMT, Arnold Trembley
<arnold.trembley@xxxxxxxxxxxxxxxx> enlightened us:



excel wrote:
Hi,
I looking for a command/program to kickoff all the users using a cics
application so that batch can be started and allow users back in after
batch is completed.

Any suggestions?


TIA


The evil person in me wants to suggest CEMT P SHUT IMM, but that would
simply shut down the entire CICS Region.

I don't believe there is an easy way to do this. Also, depending on
how many applications may be hosted in CICS, you would need to
determine which users to kick off.

A better approach would be a CICS transaction initiated from a batch
job using EXCI interfaces, that would CLOSE and DISABLE all the VSAM
files used by that application. But then the application programs
should be changed to display a message saying the files are closed and
unavailable for update. At the end of batch processing, another batch
job using EXCI would initiate a CICS transaction that would OPEN and
ENABLE all the VSAM files for that application.

But this approach would not work for DB2 tables, and I am not sure if
there is any similar function for DB2.

Perhaps a global table in CICS could be used to hold an activity
status flag. The table/flag could be updated from batch jobs using
EXCI interfaces. When the flag says that batch processing is active,
all the application programs would refuse to allow any online updates.
When the status is reset, the CICS programs would then allow online
update.

That would probably work for DB2. For VSAM files, especially if you
need to reload them from the batch jobs, it would be better to CLOSE
and DISABLE the VSAM files inside CICS at the beginning of batch
processing, and then OPEN and ENABLE them at the end of batch processing.

With kindest regards,

In addition to Arnold's suggestion, you might also want to set the
transaction codes of the CICS application to disabled at the same time
that you close the files. Closing the files sets all the pointers and
makes them available to batch updating. Disabling the transactions
gives users different errors if they try to access the application and
generally gives remote users a system not availble error and not cause
a system dump.

Regards,
.

Relevant Pages

  • Re: CICS kickoff online users
    ... batch is completed. ... The evil person in me wants to suggest CEMT P SHUT IMM, but that would simply shut down the entire CICS Region. ... A better approach would be a CICS transaction initiated from a batch job using EXCI interfaces, that would CLOSE and DISABLE all the VSAM files used by that application. ... At the end of batch processing, another batch job using EXCI would initiate a CICS transaction that would OPEN and ENABLE all the VSAM files for that application. ...
    (comp.lang.cobol)
  • Re: JCL, Cobol and "Call Parameters"
    ... you are migrating to MF and Unix? ... or CICS applications as well? ... Yep we are planing to migrate CICS and Batch Jobs. ... Batch will be native Cobol with UC4 as Scheduling ...
    (comp.lang.cobol)
  • Re: VSAM random read error
    ... every RNF condition (doing it at file open won't solve the RNF during ... This temp dataset is shielded from the CICS updates. ... temp dataset at the end of batch. ...
    (bit.listserv.ibm-main)
  • Re: Single Source CICS/Batch
    ... running the load modulein Cics and Batch environment ... B04 77 WS-ORIGINAL-EIBRSRCE PIC XVALUE LOW-VALUES. ... B04 77 WS-LINK-EIBFN REDEFINES ...
    (comp.lang.cobol)
  • Re: VSAM random read error
    ... Occasionally a record not found condition was hit but the record ... I assume a CI/CA split happens after batch file open and the record ... The file is indeed open for update in CICS but the key for which the ... time and found that no other program running parallely was even using ...
    (bit.listserv.ibm-main)