Copyright © Cloud Software Group, Inc. All Rights Reserved

Installing and Customizing the CICS Node Error Program

Installing and customizing the DFHZNEP CICS node error program enables TIBCO Object Service Broker to automatically terminate a user session when the terminal is disconnected and to free the resources allocated to the session.

Sample Routines

The S6BZNEPC sample is provided in the ASM data set to use as a guide when customizing the CICS supplied default node error program.

If your site already has a customized DFHZNEP CICS exit installed, review the sample and implement the logic necessary to call the TIBCO Object Service Broker lost-terminal processing routine.

Error Conditions That Call the Lost Terminal Processing Routine

 

In the sample provided, the TIBCO Object Service Broker routine is called under one of the following conditions: • When the “default action flags” field set by DFHZNAC (the CICS node abnormal condition program) is set to abnormally terminate or to cancel the task that is attached to this terminal • Error code X'49' — Terminal placed out-of-service with CEMT • Error code X'57' — Terminal released with CEMT Consider adding other codes appropriate to your processing needs.

Link to the S6BCSNEM Module

In the appropriate node error program handlers, invoke the TIBCO Object Service Broker routine by linking to the module S6BCSNEM (refer to the sample programs for coding details). When S6BCSNEM is invoked, the following occurs:

•	S6BCSNEM determines if the terminal being disconnected is running a TIBCO Object Service Broker session. This is done by retrieving a CICS temporary storage queue that is built when a TIBCO Object Service Broker session starts.

•	If no record is found, TIBCO Object Service Broker returns control to the calling DFHZNEP module since no session is active.

•	If a record is found, TIBCO Object Service Broker schedules a CANCELUSER operation before returning control to DFHZNEP.

CANCELUSER Operations

The CANCELUSER operation occurs in two ways, depending on the location of the canceled session:

•	If the canceled session is running in the same CICS system, S6BCSNEM schedules an HCUS CANCELUSER for the associated session.

•

In a Terminal Owning Region (TOR), where the TIBCO Object Service Broker session is running in another CICS system, an internal HOPT transaction starts locally. This transaction then starts an HCUS CANCELUSER in the remote CICS system running TIBCO Object Service Broker. The extra processing is due to CICS function shipping restrictions within the DFHZNEP environment.

Install the Supplied DFHZNEP Exit

To install the supplied DFHZNEP exit with SMP/E, complete the following steps:

1.	Select the USERMOD4 member in the JCL data set.

These are sample SMP/E usermods to apply a DFHZNEP module to implement TIBCO Object Service Broker CICS lost-terminal handling logic.

2.	Customize USERMOD4.

3.	Submit the usermod. It should end with a RC=0.

Proceed to Defining Resources to CICS.

Copyright © Cloud Software Group, Inc. All Rights Reserved