![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Your initialization parameters are defined in CNTL(PARMCICS) and are instantiated by executing the JCL(EECONFIG) job, step CICS. You can override parameters at the CICS job level by including a DD statement in your CICS job step, such as the following://HRNIN DD *
* place your override options here ...
*
* define communications id for your CICS region EE
* make sure to add to CNTL(RELAYCFG) HCS RELAY configuration
EENAME=eeeeeeee, /* should not end with a numeric */
STANDBYNUM=3, /* standby sessions to start for Eclipse */
TDS=$TDS$ /* your DOBs communication id */
/*The CICS Environment can be executed as a batch job or a started task. CICS must execute from authorized data sets. For more information on making the load library authorized, see Configuring Authorized Libraries.You must add the TIBCO Object Service Broker load library to the CICS STEPLIB and DFHRPL DD statement concatenations. Make sure that the DFHPLT startup and shutdown tables are customized as well as all CICS resources (transactions, profiles, programs, and so on) defined to your CICS system. For more information, see Creating Control Table Definitions. DFHZNEP must be customized to include Object Service Broker lost terminal error handling. For details. see Installing and Customizing the CICS Node Error Program.To connect the Eclipse User Interface (UI) to your CICS system, you will need to review the CICS requirements listed in Chapter 18, Introducing TIBCO Object Service Broker SDK (C/C++) Server, in TIBCO Object Service Broker for z/OS External Environments. Make sure that the EENAME parameter chosen for your CICS system is defined in the TCP/IP section of the HCS relay file, CNTL(RELAYCFG). For details, see The Relay File.
1. Bring up your CICS system in the usual way after customizing CICS for TIBCO Object Service Broker.
2. Using a VTAM defined terminal or terminal emulator, connect to your CICS system as per your usual connection instructions. Depending on your VTAM USSTAB entries, the logon sequence would be something like the following:If your CICS system uses operator signon, you may have to use the CICS signon transaction CESN to identify yourself before proceeding.
3. If you have defined TIBCO Object Service Broker in your startup PLT list, the Execution Interface will have been started automatically. Issue the CICS transaction:to obtain the current status of the CICS Execution Environment interface. The result will be something like the following:S6BDR021I EXECUTION ENVIRONMENT IS ATTACHED - S6ELDOBA
S6BCS022I 7 user(s).
S6BCS052I USER ID TERM ID USER ID TERM ID
S6BCS050I U0043000 T0043000 $0043000 $0043000
S6BCS050I U0043001 T0043001 $0043001 $0043001
S6BCS050I U0043002 T0043002 $0043002 $0043002
S6BCS050I U0043003 T0043003In this case, the EE is running and has seven standby sessions available. These can be used to support your Eclipse User Interface sessions.This transaction can have override parameters, such as TDS=, which identifies the Data Object Broker's communication identifier to be connected when the EE initializes. If no parameters are provided, the EECONGIF defaults will be used for the CICS region type. Response from the HINT transaction will be:S6BCS014I TIBCO(r) Object Service Broker/CICS interface initialization complete.S6BDR136I Execution Environment initialization complete, Version: V600
4. Logon via a native CICS terminal session to the TIBCO Object Service Broker. Enter your CICS defined transaction to invoke the TIBCO Object Service Broker. Typically, this will be HURN. Enter your user identification if you are not using the CESN default userid that you logged on to CICS with earlier. For example:You will be prompted for your password if required. If you successfully logon to the EE, should be presented with the TIBCO Object Service Broker workbench. Press PF12 to terminate your EE session and return to native CICS. You should receive a message such as the following:
5. To check the printing capability of your CICS EE, logon to the EE using HURN U=SYSADMIN or another userid that can update the system table @SCHEDULEMODEL. Edit the table as shown below:Type the table name to the right of the ED Edit Table ==> literal and press ENTER. You will be prompted for the instances of the table to edit:EDITING TABLE : @SCHEDULEMODEL
ENTER PARM VALUE OPERATING_SYSTEM: MVS
ENTER PARM VALUE MODELNAME : SPOOLSTRIP
ENTER PARM VALUE LOCATION :Alter the table contents so that the JCL is acceptable to your CICS and z/OS environment. You may need to change the JCL wherever {USERID} appears, especially on the JOB card as some TIBCO Object Service Broker user identifiers may not be valid to your external security system. SYSADMIN may be one example. For information on customizing the @SCHEDULEMODEL table, see Customization of the TIBCO Object Service Broker @SCHEDULEMODEL Table.When you have completed the customization of the @SCHEDULEMODEL table instance MVS,SPOOLSTRIP, save the updates by pressing PF3.To test the changes, enter Edit of the @SCHEDULEMODEL MVS,SPOOLSTRIP instance again and check that your changes are still there. Now press PF13 to print the table instance, then press PF3 to exit Edit. Check your JES log or your printer for the output. The JES log will contain a message such as the following:$HASP100 <jobname> ON INTRDR <jobcard identification> FROM JOB##### <cicsjobname>
6. To check your ability to connect to the TIBCO Object Service Broker CICS EE, install the Eclipse User Interface (UI) on an Open Systems platform. Ensure that you have set the following EECONFIG or HRNIN override parameters for your CICS system:and also define yourEEcommunicationsname in the TCP/IP section of the HCS relay file. For details, see Customizing and Executing the CICS Environment.Start Eclipse and select a suitable workspace location on your drive if prompted. Then select Window > Open Perspective > Other > OSB Perspective. Open a new project for your CICS session by selecting File > New >OSB Project and specify the following:
− Project Name – a meaningful description of the project, such as “Test CICS Eclipse UI for 6.0."
− Host – name of system where CICS is executing, such as sandbox.your.company.com or IP address.
− Port – the Execution Environment listening port identified in the CICS EE startup message, such as the following:S6BRA008I TCP/IP RELAY started; Accepting connections on socket port 10061
− Userid and password to connect and start a session within the TIBCO Object Service Broker Execution EnvironmentOnce these have been specified, press the Test Connection button to see if the physical connection works. If so, you will receive the message:If you have a failure, review the settings in your profile against your z/OS and CICS specifications. Check the CICS JES and error logs for error messages. Make sure you have configured your SDK support.Once the connection test is successful, press Finish to begin your Eclipse session with TIBCO Object Service Broker. To make sure that data can be retrieved, hover your cursor over Tables under OSB Projects and right mouse click, selecting Show Tables. This should retrieve a list of tables defined to your system. If no list is displayed, check the CICS JES joblog and error logs for failure messages if no reason is supplied by your Eclipse session.If a list of tables is displayed. Your Eclipse OSB UI is working successfully. You may then select Exit Eclipse to terminate your session and Eclipse.
7. To test the lost terminal processing under DFHZNEP, you will need to customize and stage the CICS DFHZNEP module according to the instructions mentioned previously. Start a native VTAM session with your CICS region, then start a TIBCO Object Service Broker session by entering the following:and respond with your password if prompted. When the workbench is displayed, terminate your VTAM session by disconnecting the session to drive the lost terminal processing in CICS. If DFHZNEP has been correctly customized, you should see a message on the CICS JES joblog such as the following:S6BKC017L <userid> LOGGED OFF #=nnnnnn TYPE=CICSUSER COMM=TCP/IP SOURCE=<tttt>
8. To test out the automated PLT shutdown of the Execution Environment, logon to CICS using a 3270 session and issue the following command:You should see on the CICS JES joblog the following messages if the shutdown is successfully executed for the TIBCO Object Service Broker EE:DFHTM1715 <CICS-jobname> CICS is being quiesced by userid <userid> in transaction CEMT at netname <nnnnnnnn>.
DFHTM1709I <CICS-jobname> About to link to PLT programs.
. . .
S6BDR078I COMMAND 'SHUTI ' ISSUED
S6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPPOSIX
S6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPINTRP
S6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPSIN
S6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPOPER
S6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPSORTS6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPMISC
S6BDR065I TERMINATION COMPLETE FOR SERVER CLASS DSPFILIO
S6BRA009I TCP/IP RELAY stopped
S6BTK002I TRACKER Task termination complete
DFHTM1710I <CICS-jobname> Control returned from PLT programs.This concludes the basic installation verification procedure for CICS Execution Environments.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |