Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 5 Installing the Service Gateway for CICS : Creating and Modifying Other CICS Definitions and Parameters

Creating and Modifying Other CICS Definitions and Parameters
Using CICS Dynamic Storage Area Parameters
TIBCO Object Service Broker runs as a CICS key task. It makes no use of CICS user-key storage. The storage for the CICS address space is allocated according to the following CICS initialization parameters:
 
Specifies the upper limit of the total amount of storage above the 16 MB line within which CICS can allocate individual extended dynamic storage areas (EDSAs).
The value for this parameter depends on the number of TIBCO Object Service Broker sessions you anticipate needing for your installation.
TIBCO Object Service Broker uses approximately 530 KB of the storage area limited by EDSALIM.
Specifies the upper limit of the total amount of storage below the 16 MB line within which CICS can allocate individual dynamic storage areas (DSAs).
TIBCO Object Service Broker uses approximately 0.5 KB of the shared storage area limited by DSALIM.
 
TIBCO Object Service Broker also uses storage that is outside CICS control, even though it is within the CICS address space. Refer to TIBCO Object Service Broker Parameters for a description of the CICSREGIONSIZE parameter.
Storage Areas Limited by EDSALIM
From the storage size specified on the EDSALIM parameter, TIBCO Object Service Broker allocates the following extended dynamic storage areas:
Extended user DSA. The user-key storage for all user-key 31‑bit task storage above the 16 MB line.
Extended read-only DSA. The key‑0 storage area for all reentrant 31‑bit programs and tables above the 16 MB line.
500 KB—for loading CICS-related TIBCO Object Service Broker modules that are related to CICS. These are permanently resident and persist as long as CICS is running.
Extended shared DSA. The user-key storage area for non-reentrant user-key RMODE(ANY) programs. Also for storage obtained by programs issuing CICS GETMAIN commands for shared storage above the 16 MB line.
30 KB of shared storage for major control blocks needed for the duration of each TIBCO Object Service Broker session under CICS storage
Extended CICS DSA. The CICS-key storage area for the following:
All non-reentrant CICS-key RMODE(ANY) programs
3 KB—released as soon as the CICS transaction terminates
Storage Areas Limited by DSALIM
From the storage size specified on the DSALIM parameter, TIBCO Object Service Broker allocates the following dynamic storage areas:
TIBCO Object Service Broker Value
User DSA. The user-key storage for all user-key 31‑bit task storage below the 16 MB line.
Not used by TIBCO Object Service Broker.
Read-only DSA. The key‑0 storage area for all reentrant 31‑bit programs and tables below the 16 MB line.
Not used by TIBCO Object Service Broker.
Shared DSA. The user-key storage area for non-reentrant user-key RMODE(24) programs. Also for storage obtained by programs issuing EXEC CICS GETMAIN commands for shared storage below the 16 MB line.
0.5 KB of shared storage used for the duration of each TIBCO Object Service Broker session
Not used by TIBCO Object Service Broker
See Also
The IBM manual CICS Transaction Server for z/OS System Definition Guide for more information about CICS storage areas and other CICS initialization parameters.
The IBM manual CICS Transaction Server for z/OS Performance Guide for information about calculating the amount of storage to specify on the EDSALIM and DSALIM parameters.
Create Processing Program Table (PPT) Definitions
Define the following TIBCO Object Service Broker programs using RDO. For either a standalone region or an Application-Owning Region (AOR), you can also use the CICSDEFS member in the JCL data set to create a group to contain these definitions. You must specify EXECKEY(CICS) and DATALOCATION(ANY).
Do not specify the RES=YES option for the following programs:
The value ANY for TASKDATALOC and DATALOCATION is not required in all situations. ANY is recommended to take advantage of CICS Virtual Storage Constraint Relief (VSCR). In a CICS environment where TIBCO Object Service Broker invokes (or is invoked by) an AMODE(24) program, the value for these parameters must be BELOW.
Create Definitions for MRO Terminal Owning Regions
Define the S6BCSNEM and S6BCSOPT programs in MRO terminal-owning regions (both programs are non-resident). For a Terminal-Owning Region (TOR), you can also use the CICSDEFS member in the JCL data set to create a group to contain definitions for these programs and TIBCO Object Service Broker TOR transactions.
Create Program List Table (PLT) Startup Definitions
Use the following as a guide to define the TIBCO Object Service Broker startup programs in the CICS Program List Table (PLT), or the equivalent in RDO:
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
DFHPLT TYPE=ENTRY,PROGRAM=S6BCSINT
In this example, the DFHDELIM CICS program must precede the S6BCSINT TIBCO Object Service Broker program.
Create Program List Table Shutdown Definitions
Use the following as a guide to define the TIBCO Object Service Broker shutdown program in the CICS PLT, or the equivalent in RDO:
DFHPLT TYPE=ENTRY,PROGRAM=S6BCSTRM
DFHPLT TYPE=ENTRY,PROGRAM=DFHDELIM
In this example, the S6BCSTRM TIBCO Object Service Broker program must precede the DFHDELIM CICS program.
Create Transaction List Table (XLT) Definitions
Use the following as a guide to define a list of TIBCO Object Service Broker transactions that can be executed during the first quiesce state of CICS termination in the CICS XLT, or the equivalent in RDO:
DFHXLT TYPE=ENTRY,
TRANSID=(HCSS,HCUS,HFUS,HINQ,HTRM,HSRV,hcus,hfus,hinq,htrm,hsrv)
Be sure to include transactions defined in your control table definitions (see Modify Terminal Control Table (TCT) Definitions, and sections following) in the set of transaction identifications, that is, HCSS, HCUS, HFUS, HINQ, HTRM, and HSRV in this example. Transactions allowing new TIBCO Object Service Broker sessions to be initiated should not be included in this list because regular sessions are being terminated during CICS termination.
Modify Terminal Control Table (TCT) Definitions
Terminals with mixed-case characters displayed must have their Terminal Control Table (TCT) definitions modified to include the UCTRAN parameter. If not done, text data is saved and reappears in uppercase only. You must specify UCTRAN(NO) in all terminal TYPETERM definitions where mixed case characters must be input and displayed. Before making this change, consider the following:
If NO is specified, the user must type the transaction ID in uppercase (for example, HURN) or CICS does not recognize the transaction as valid. Use the ALIAS parameter to define lowercase versions of each transaction identification.
In other applications, users could actually save records in lowercase, causing problems with key searches (for example, part~=PART).
Define a CICS Console
When using a TIBCO Object Service Broker CICS region to start a TIBCO Object Service Broker server, the CICS console facility is used to initiate the required non-terminal background CICS tasks. These tasks provide CICS services to the server. To use the console, you must define a CICS console definition. The values for the definition depend on the version of CICS you are using. Sample console definitions appear in the S6BTERM1 group of the CICSDEFS member in the JCL data set.
Make sure you define sufficient RACF authority to your CICS region's security identifier to allow TIBCO Object Service Broker to issue modify commands internally to CICS.
The console modify facility is also used in cancelling CICS sessions from the Data Object Broker region.
See Also
The IBM CICS Transaction Server for z/OS Resource Definition Guide documentation for more information about the use of the resource definition facility.
Specify System Initialization Table (SIT) Parameters
The following parameters should be specified in the CICS System Initialization Table (SIT) or via CICS SIT override facilities:
 
Customize Parameters
Sample initialization parameters used by TIBCO Object Service Broker in the CICS address space are provided in member PARMCICS of the CNTL data set. Step CICS in member EECONFIG in the JCL data set can be used to create a default option module for the CICS environment. Customize the initialization parameters and run the step to create the default option module.
During CICS TIBCO Object Service Broker initialization, the SVC (Supervisor Call) number is loaded from S6BDRCC0 regardless of the CONFIGURATION= specification. For a description of the sample initialization parameters included in this step, refer to TIBCO Object Service Broker Parameters.
Include the Authorized TIBCO Object Service Broker Data Set in Concatenations
TIBCO Object Service Broker modules are installed in an authorized data set. Include this data set in the CICS STEPLIB and DFHRPL concatenations. For more information on making the load library authorized, refer to Configuring Authorized Libraries.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved