![]() |
![]() |
![]() |
![]() |
![]() |
• The UNIX System ~/.profile file to centralize values and paths used by the CICS Runtime for its own needs or for Tuxedo.
• The Tuxedo envfile which contains parameters, variables and paths used by Tuxedo.
• The Tuxedo ubbconfig file to declare all the required CICS Runtime Tuxedo servers.For UNIX users, most required variables are defined in the .profile file that centralizes all of the common variables and paths used by a user for commands and applications.Set the following variables in the initial settings of ~/.profile file.
Table 3‑1 .profile Variables Listing 3‑1 .profile file Initial Settings Example
Table 3‑2 envfile Variables Listing 3‑2 envfile Initial Settings Example
• The Terminal Control Program Listener (ARTTCPL server) is needed because it establishes communication between end-users and CICS Runtime applications thru maps displayed on 3270 terminals or emulators.
• The Connection Server (ARTCNX server) is also required because it offers technical connections services during the user connection and disconnection phases. It is also used to display the CICS system transactions CICS Runtime Good Morning screen thru the System Transaction CSGM.
• The Administration Server (ARTADM server) is needed to replicate resources files for all other servers.
• The Synchronous Transaction Servers (ARTSTRN and ARTSTR1) that manage synchronous transaction CICS applications
• The Asynchronous Transaction Servers (ARTATRN and ARTATR1) that manage asynchronous transaction CICS applications.
• The Temporary Storage Server (ARTTSQ server) that manage TS QUEUES used in COBOL CICS programs.
Note: TMQUEUE must be started before ARTCNX to support the followings:
• Static LUNAME from 3270 terminalListing 3‑3 ubbconfig Initial Server Configuration ExampleFor the ARTTCPL server:Is the Tuxedo Group Name to which ARTTCPL belongs.Is the identifier of a ARTTCPL Tuxedo Server.For the ARTADM server:Is the Oracle Tuxedo group name to which ARTADM belongs.For the ARTCNX server:To be started, a Tuxedo Server must be defined in a Tuxedo Server Group previously defined in the ubbconfig file. As the ARTTCPL and ARTCNX servers are mandatory, verify that their groups are defined, present and not commented-out, in the ubbconfig file.In our example, ARTTCPL belongs to the Tuxedo Server Group TCP00 (SRVGRP=TCP00) and ARTCNX belongs to the Server Group (SRVGRP=GRP01); therefore the ubbconfig file contains these two Server Group definitions in the following example:Listing 3‑4 Server Group DefinitionsThese groups are used to contain the optional servers. The first group is used by the Tuxedo Server Servers Groups: ARTSTRN, ARTSTR1, ARTATRN, ARTATR1, ARTTSQ used by CICS Applications. The second one is used only for TS QUEUE management.All of the following files must exist in the ${KIXCONFIG} path, even when empty, for CICS Runtime to be operational.
1. The typeterms.desc Configuration FileListing 3‑5 typeterm Description Example
2. The mapsets.desc Configuration FileThis file must contain at least the following definition to start the CSGM transaction and see the Good Morning screen.Listing 3‑6 mapsets.desc ExampleIs the logical mapset name used inside the programs in the EXEC CICS SEND/RECEIVE MAP(map name) MAPSET(mapset name) … END-EXEC statements.
Note: For the particular case of the ABANNER system mapset, the filename is located under the ${KIXDIR} directory. The bracketed text <KIXDIR> must be replaced by the value of the ${KIXDIR} variable of your UNIX ~/.profile system file.Listing 3‑7 mapsets.desc Example with ${TUXDIR} Substitution
Note: If these files are left empty, when Tuxedo launches the CICS Runtime servers, some error messages "CMDTUX_CAT:1685: ERROR: Application initialization failure" could be displayed after the boot message of the ARTSTRN, ARTSTR1, ARTATRN and ARTATR1 servers indicating that the CICS Runtime considers this to be an anomaly.The real number and type of servers displaying these messages depends on the servers initially launched by your ubbconfig file.Once this first check is made, you can enter the Tuxedo tmadmin psr command to check that all the CICS Runtime servers are running and that their messages conform to the Tuxedo documentation and this document.When the mandatory servers ARTADM, ARTTCPL, and ARTCNX only are started, the following messages are displayed:Listing 3‑8 tmadmin psr Command ExampleYou can also check that the required Tuxedo services are running using the tmadmin psc command.Listing 3‑9 tmadmin psc Command Example
Note: From a certain point of view, this Tuxedo command is equivalent to the z/OS CICS system transaction CEMT I TRAN(…) which allows you to display the available transactions in a given z/OS CICS environment.Once this first audit is made, you can access CICS Runtime with a 3270 Terminal or Emulator using the following URL address ${HOSTNAME}:${TCPNETADDR}.Is the port number specified by the -n parameter of the ARTTCP server in the Oracle Tuxedo UBBCONFIG file.