Reference Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

CICS Runtime Configuration Files

 


Overview

The administration of CICS Runtime is based on Tuxedo native tools with the addition of a limited number of configuration tables for features that are specific to CICS. In CICS configurations, resources are nowadays defined in the CSD when previously they were defined as independent tables. This latter approach is the one used with CICS Runtime.

Each resource configuration table describes a resource of a particular type: transaction, transaction class, program, file, TS Queue model, etc. Each table contains the specific parameters relevant to the resource.

Shared Responsibilities Between Tuxedo and Resource Files

A CICS resource like a transaction with all its characteristics (first program, restartable, …) is described in resource configuration files. The Tuxedo configuration elements, like how many servers of which group on which machine will offer this transaction is described in the Tuxedo configuration file UBBCONFIG.

This way the responsibilities are clearly distributed:

Resource Definition Directory

All resource configuration files are stored in a common directory indicated by a well known environment variable: ${KIXCONFIG}.

Each table describing CICS type of information is stored in a file read by servers at start time.

 


Presentation of Configuration Files

General Content

Each resource configuration table describes a resource type: transaction, transaction class, program, files, TS Queue, …, with all the specific parameters relevant to this resource.

The central file defines the lists of resource groups. When configuring a ART CICS server, the administrator specifies which lists to load. A single list may contain a few tens of resource groups that include hundreds or thousands of individual resources.

Structure

Each resource table contains three columns of parameters:

Field Name
Type
Values
Description
Name of the parameter in the table.
The data type of the field.
When specific values are required they are listed here.
Description of the purpose of the field, and its usage

The rest of this section describes in detail each of these configuration files:

 


List of Groups Configuration File

Table 4-1 defines the lists of resource groups that may be loaded by application servers.

The filename is list_of_groups.desc.

Table 4-1 Group List Parameters
Field Name
Type
Values
Description
LIST
X(10)
Mandatory
Name of the list.
Referred by - L options of the application servers
GROUP
X(10)
Mandatory
Name of the group to be included in the list.
This table contains one line per group to in a list.
The same group may present in more than one list.

 


Transaction Configuration File

Table 4-2 lists the transactions available to application users, with their characteristics.

The filename is transactions.desc.

Table 4-2 Transaction Parameters
Field Name
Type
Values
Description
TRANSACTION
X(4)
Mandatory
Name of the transaction.
GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual comment zone for description of the resource.
PROGRAM
X(30)
Mandatory
Name of the first program to be called for this transaction.
ALIAS
X(4)
Optional
Reserved for future use.
Used to define an alias for the transaction (usually lower case).
CMDSEC
Bool
N|Y
Reserved for future use.
The ESM to be called for system programming requests.
The default value is N.
CONFDATA
Bool
N|Y
Optional
Reserved for future use.
As in confidential data: specifies whether CICS is to suppress user data from CICS trace entries when the CONFDATA system initialization parameter specifies HIDETC.
If the system initialization parameter specifies CONFDATA=SHOW, CONFDATA on the transaction definition is ignored.
The default value is N.
PRIORITY
9(3)
1 | n
Optional
Reserved for future use.
Specifies the transaction priority. This 1-to 3-digit decimal value from 0 to 255 is used in establishing the overall transaction processing priority. (Transaction processing priority is equal to the sum of the terminal priority, transaction priority, and operator priority, not exceeding 255.) The higher the number, the higher the priority.
The default value is 1.
RESSEC
Bool
N|Y
Specifies whether resource security checking is to be used for resources accessed by this transaction.
The default value is N.
RESTART
Bool
N|Y
Optional
Reserved for future use.
Specifies whether the transaction restart facility is to be used to restart those tasks that terminate abnormally and are subsequently backed out by the dynamic transaction backout facility.
The default value is N.
STATUS
X(10)
ENABLED| DISABLED
Specifies the transaction status.
  • ENABLED: Allows the transaction to be executed normally.
  • DISABLED: Prevents the transaction being executed.

The default value is ENABLED.

TASKDATAKEY
X(5)
USER |CICS
Reserved for future use.
The default value is USER.
TPNAME
X(64)
Optional
Reserved for future use.
Specifies the name of the transaction that may be used by an APPC partner, if the 4-character length limitation of the TRANSACTION attribute is too restrictive. This name can be up to 64 characters in length.
TRACE
Bool
Y|N
Optional
Reserved for future use.
Specifies whether the activity of this transaction is to be traced.
The default value is Y.
TRANCLASS
X(8)
Optional
Specifies the name of the transaction class to which the transaction belongs. Transactions belonging to a transaction class are subject to scheduling constraints before they are allowed to execute.
See Tranclasses Configuration File for more information on the usage of this parameter on the target platform.
A Transaction with no tranclass defined will have no other scheduling constraints than the number of servers offering it.
TWASIZE
Short int
Optional
Specifies the size (in bytes) of the transaction work area to be acquired for this transaction. Specify a 1-to 5-digit decimal value in the range 0 through 32767.
The default value is 0.

Each transaction is advertised as an Oracle Tuxedo service by CICS Runtime servers, e.g. ARTSTRN, ARTATRN…. You can divide the transactions into different groups and assign the groups to different servers using option "– l", so that each server just advertise its own services.

Note: It is not recommended to define all transactions to one group, as it causes every service to be advertised by every server and results in enormous consumption of Oracle Tuxedo services.

 


Tranclasses Configuration File

Table 4-3 lists and defines tranclasses available to regulate parallel transactions activities.

The filename is tranclasses.desc.

Table 4-3 Transclass Parameters
Field Name
Type
Values
Description
TRANCLASS
X(8)
Mandatory

Name of the transaction class.

A tranclass defines a category of transactions, which should not be running in parallel; probably because they use some resources in a non-serializable way.

GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual comment zone for description of the resource.
MAXACTIVE
short
0 - 999

Defines the degree of parallelism of execution.

The only value for which we do a special processing is value 1, see below for more information.

Semantic Information

Native Source CICS Definition

Transactions that are defined as belonging to a transaction class are subject to scheduling constraints before they are allowed to execute. If transactions belonging to an active transaction class are already running, any new transactions are queued. Use the MAXACTIVE attribute to specify the maximum number of transactions that you want to run. To limit the size of the queue, you can use the PURGETHRESH attribute.

By putting your transactions into transaction classes, you can control how CICS dispatches tasks.

Mapping to Target Platform Concepts

On Tuxedo, the scheduling of transactions and the affectation of resources to groups of transactions is performed differently; it is the number of servers offering given transactions which manages the scheduling of transactions, and the relative amount of resources affected to a group of transactions.

The Special Case of MAXACTIVE 1

This case is very specific, because it impacts the functional characteristics of the application.

It ensures that two transactions of this class will never execute concurrently. It defines a mutually exclusive behavior that is preserved on the target platform to guarantee the correct behavior of the application.

A single server ARTSTR1 will offer the transactions belonging to one TRANCLASS with MAXACTIVE = 1.

 


Programs Configuration File

Table 4-4 lists and defines programs available to be referenced either as first program of a transaction, or being invoked by EXEC CICS LINK and XCTL.

The filename is programs.desc.

Table 4-4 Programs Parameters
Field Name
Type
Values
Description
PROGRAM
X(30)
Mandatory

Name of the program.

GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual comment zone for description of the resource.
LANGUAGE
X(8)
COBOL | C
The language of the program, required to know how to communicate with it.
Current release supports only COBOL.
EXECKEY
X(4)
 
Reserved for future use.
Concerns memory protection of CICS shared structures.
STATUS
X(10)
ENABLED|DISABLED
Specifies the program status.
  • ENABLED: Allows the program to execute normally.
  • DISABLED: Prevents the program being executed.
REMOTESYSTEM
X(4)
Optional
Specifies that the program is not offered locally but in a DPL server.
REMOTENAME
X(10)
Optional
Specifies for a DPL program the name of the program on the distant site.
Useful only if the remote name is different from the local name.

 


Files Configuration File

Table 4-5 lists and defines files available to be referenced by the CICS application.

The filename is files.desc.

Table 4-5 Files Parameters
Field Name
Type
Values
Description
FILE
X(8)
Mandatory
Name of the file. Logical name of the file used in EXEC CICS related to this file.
GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual comment zone for description of the resource.
DISPOSITION
X(5)
SHARE | OLD
Optional
Reserved for future use.
Specifies the disposition of this file. (shared or exclusive).
DSNAME
X(60)
Mandatory
Specifies the data set name (as known to the operating system) to be used for this file.
JOURNAL
X(20)
NO | journal
Optional
Reserved for future use.
Specifies whether you want automatic journaling for this file.
The journalized data is in the format of the VSAM record and is used for user controlled journaling. The data to be journalized is identified by the JNLADD, JNLREAD, JNLSYNCREAD, JNLSYNCWRITE, and JNLUPDATE attributes.
This Journal is for auditing.
KEYLENGTH
Short
Optional
Reserved for future use.
Specifies the length in bytes of the logical key of records in remote files, and in coupling facility data tables that are specified with LOAD(NO).
In the current release, we support neither remote (extra Tuxedo system) files, nor CFDT; In future we may support Remote file shipping and use this Key Length.
OPENTIME
X(8)
FIRSTREF |STARTUP
Mandatory
Reserved for future use.
Specifies when the file is opened.
READINTEG
X(12)
UNCOMMITTED| CONSISTENT| REPEATABLE
Mandatory
Reserved for future use.
Specifies the level of read integrity required for files defined with RLSACCESS(YES). You can use READINTEG to set a default level of read integrity for a file. This default is used by programs that do not specify one of the API read integrity options.
On the target platform the exact semantic of the three levels of integrity may vary from exact CICS/VSAM semantic to another.
RECORDSIZE
Short
1 - 32767
Optional
Reserved for future use.
Specifies the maximum length in bytes of records in a remote file or a coupling facility data table. The size specified can be in the range 1 through 32767.
In the current release, we support neither remote (extra Tuxedo system) files, nor CFDT; In future we may support Remote file shipping and use this Record Size.
REMOTENAME
X(8)
Optional
Reserved for future use.
Specifies the name of the file on the remote system.
REMOTESYSTEM
X(4)
Optional
Reserved for future use.
On source, specifies the name of the connection that links the local system to the remote system where the file resides.
On the target platform, will be used only in case of file shipping to another system, either another TUXEDO system or native CICS system.
STATUS
X(10)
ENABLED| DISABLED| UNENABLED
Mandatory
Reserved for future use.
Specifies the initial status of the file following a CICS initialization.
UNENABLED allows for explicit EXEC CICS SET FILE OPEN.

Journaling Attributes

Table 4-6 lists the journaling attributes.

Table 4-6 Journaling Attributes
Field Name
Type
Values
Description
JNLADD
X(6)
NONE| BEFORE| AFTER| ALL
Optional
Reserved for future use.
Specifies if you want the add operations recorded on the journal nominated by the JOURNAL attribute.
On the target platform the semantic is conserved with a simplification: for BEFORE/AFTER/ALL, a single record is logged.
JNLREAD
X(10)
NONE| UPDATEONLY| READONLY| ALL
Optional
Reserved for future use.
Specifies the read operations you want recorded on the journal nominated by the JOURNAL attribute.
Possible values are:
  • ALL: Journal all read operations.
  • NONE: Do not journal read operations.
  • READONLY: Journal only READ ONLY operations (not READ UPDATE operations).
  • UPDATEONLY: Journal only READ UPDATE operations (not READ ONLY operations).
JNLSYNCREAD
Bool
N|Y
Optional
Reserved for future use.
Specifies whether you want the automatic journaling records, written for READ operations to the journal, to be synchronous.
JNLSYNCWRITE
Bool
Y|N
Optional
Reserved for future use.
Specifies whether you want the automatic journaling records, written for WRITE operations to the journal, to be synchronous.
JNLUPDATE
Bool
N|Y
Optional
Reserved for future use.
Specifies whether you want REWRITE and DELETE operations recorded on the journal.

 


TS Queue Model Configuration File

Table 4-7 lists and defines theTS Queue models available to be referenced by the CICS application.

The filename is tsqmodel.desc

Table 4-7 TS Queue Parameters
Field Name
Type
Values
Description
TSMODEL
X(8)
Mandatory

Name of the TS Queue model.

GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual zone for description of the resource.
LOCATION
X(9)
AUXILIARY | MAIN
Specifies the kind of storage to use: file or memory.
Only used as a control: MAIN TS cannot be recoverable.
PREFIX XPREFIX
X(16)
Mandatory
Specifies the character string that is to be used as the prefix for this model. The prefix may be up to 16 characters in length.
RECOVERY
Bool
N|Y
Specifies whether or not queues matching this model are to be recoverable. On the target platform, a default queue is written to file, while a recoverable queue is stored in the RDBMS to provide recovery capabilities.
POOLNAME
X(8)
Optional
Deprecated. There are other ways on target to arrive to the same result.
Specifies the 8-character name of the shared TS pool definition that you want to use with this TSMODEL definition.
REMOTESYSTEM
X(4)
Optional
Reserved for future use.
On source platform, specifies the name of the connection that links the local system to the remote system where the temporary storage queue resides.
On the target platform, used only in case of TS shipping to another system, either another TUXEDO system or native CICS system.
REMOTEPREFIX XREMOTEPREFIX
X(16)
Optional
Reserved for future use.
Specifies the character string that is to be used as the prefix on the remote system. The prefix may be up to 16 characters in length.
These options are useful (on source and target platforms) only if one wants to translate queue name when shipping TS Queue access from one system to another.
SECURITY
Bool
N|Y
Reserved for future use.
Specifies whether security checking is to be performed for queues matching this model.
The default value is N.

 


ENQ-Model Configuration File

Table 4-8 lists and defines ENQ Models available to be referenced by the CICS application.

The filename is enqmodel.desc.

Table 4-8 ENQ Model Parameters
Field Name
Type
Values
Description
ENQMODEL
X(8)
Mandatory
Name of the ENQ model.
GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual zone for description of the resource.
ENQNAME
X(255)
Mandatory
Specifies the 1 to 255-character resource name.
ENQSCOPE
X(4)
Optional
If omitted or specified as blanks, matching enqueue models will have a local scope, else they will have a global scope
STATUS
bool
E|D
Reserved for future use.
E = Enabled.
D = Disabled.

 


TD Queue Extra Partition Configuration File

Table 4-9 lists and defines extra partitions TD queues available to the CICS application.

The filename is tdqextra.desc.

Table 4-9 TD Queue Parameters
Field Name
Type
Values
Description
TDQUEUE
X(4)
Mandatory
Specifies the 1- to 4-character name of a transient data queue.
GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual zone for description of the resource.
DDNAME
X(8)
Mandatory
Specifies a 1-to 8-character value that may refer to a data set defined in the startup JCL.
DISPOSITION
X(3)
Optional
Specifies the disposition of the data set.
  • MOD: ART-CICS first assumes that the data set exists. For an existing sequential data set, MOD causes the read/write mechanism to be positioned after the last record in the data set. The read/write mechanism is positioned after the last record each time the data set is opened for output. If ART-CICS cannot find volume information for the data set:
    • On the DD statement.
    • A data set allocated dynamically in this way is deleted when the queue is closed, and all records are lost. For a new data set, MOD causes the read/write mechanism to be positioned at the beginning of the data set.

  • OLD: The data set existed before this job step.
  • SHR: The data set existed before this job step and can be read by other concurrent jobs.
ERRORPTION
X(1)
I | S
UNSUPPORTED
Specifies the action to be taken if an I/O error occurs. This can be one of the following:
  • I = IGNORE: The block that caused the error is accepted.
  • S = SKIP: The block that caused the error is skipped.
OPENTIME
X(1)
D | I
UNSUPPORTED
Specifies the initial status of the data set. The initial status can be one of the following:
  • D = DEFERRED: The data set remains closed until you indicate that you want to open it by using the CEMT INQUIRE|SET TDQUEUE command.
  • I = INITIAL: The data set is to be opened at install time. However, if the DSNAME attribute is not specified, and the data set name is not specified in the DD statement in the startup JCL, the transient data queue is allocated to JES during CICS startup.
RECORDFORMAT
X(1)
F | V
Specifies the record format of the data set.
  • F= FIXED: Fixed records. If you specify RECORDFORMAT FIXED, you must also specify a block format.
  • V= VARIABLE: Variable records. If you specify RECORDFORMAT VARIABLE you must also specify a block format.
PRINTCONTROL
X(1)
A |
UNSUPPORTED
Specifies the control characters to be used. There is no default. If you allow RECORDFORMAT to default to blank, you cannot specify anything in the PRINTCONTROL field. The control characters that can be used are:
  • A= ASA: ASA control characters.
  • blank: No control characters are to be used.
RECORDSIZE
9(4) COMP
Optional
Specifies the record length in bytes, in the range 0 through 32767.
TYPEFILE
X(6)
Optional
Specifies the type of data set the queue is to be associated with:
  • INPUT: An input data set.
  • OUTPUT: An output data set.
DSNAME
X(80)
Optional
Specifies the name of the file that is to be used to store records written to this extrapartition queue.
This file must exist even if empty.
SYSOUTCLASS
X(1)
Optional
UNSUPPORTED
Instead of allocating an extra partition queue to a physical data set, you can allocate it to a system output data set (referred to as SYSOUT). Use the SYSOUT CLASS attribute to specify the class of the SYSOUT data set.
A..Z|0..9 A single alphabetic or numeric character that represents an output class that has been set up on the z/OS system on which the CICS Runtime job is to run.
TRT
X(1)
S | I
New optional CICS Runtime argument, allowing integrators and customers to make their own specific implementation of extra partition queues.
No value or S (for Standard) will invoke normal CICS Runtime TDQueue functionalities
Setting the value I, will trigger the call to a function td_extra_actions_int, which must be provided by the integrator.

 


TD Queue Intra Partition Configuration File

Table 4-10 lists and defines intra partitions TD queues available to the CICS application.

The filename is tdqintra.desc.

Table 4-10 TD Queue Parameters
Field Name
Type
Values
Description
TDQUEUE
X(4)
Mandatory
Specifies the 1- to 4-character name of a transient data queue.
GROUP
X(10)
Mandatory
The group notion of CICS allowing a group of related resources to be declared and instantiated or not by a CICS system when starting.
DESCRIPTION
X(60)
Optional
A small textual zone for description of the resource.
RECOVSTATUS
X(8)
NO | LOGICAL
Specifies if the queue is logically recoverable or not.
If a queue is logically recoverable, its elements will be written to tuxedo /Q in the context of the transaction and will be rolled back with the rest of the transaction in case of a rollback.
If the queue is non-recoverable, then each enqueue in the /Q queue will be permanent and not rolled back in case of a rollback or abort.
TRANSID
X(4)
Optional
Specifies the name of the transaction that is to be automatically initiated when the trigger level is reached. Transactions are initiated in this way to read records from the queue. If the TRANSID attribute is not specified (or if TRIGGERLEVEL(0) is specified), you must use another method to schedule transactions to read records from transient data queues.
TRIGGERLEVEL
X(1)
1 | n
Specifies the number of records to be accumulated before a task is automatically initiated to process them. (This number is known as the trigger level.) If you specify the TRANSID attribute, TRIGGERLEVEL defaults to 1. Specify a trigger level of 0 if you want to disable ATI processing. If you do not specify a transaction ID, the trigger level is ignored.
For logically recoverable transient data queues, the ATI task is not attached until the task commits forward. This may mean that the trigger level is far exceeded before ATI occurs.
USERID
X(8)
optional
Specifies the userid you want CICS to use for security checking when verifying the trigger-level transaction specified in the TRANSID field.
WAIT
X(1)
YES | NO
INACTIVE field
accepted only in the resource loading
WAITACTION
X(6)
REJECT | QUEUE
INACTIVE field
Accepted only in the resource loading.
QSPACENAME
X(15)
mandatory
New mandatory CICS Runtime argument, specifying the name of the tuxedo /Q QSPACE into which this queue is physically stored.
Consult your Tuxedo /Q documentation for more information on qspaces and queue administration.
TRT
X(1)
S | I
New optional CICS Runtime argument, allowing integrators and customers to make their own specific implementation of intra-partition queues.
No value or S (for Standard) will invoke normal CICS Runtime TSQueue functionalities
Setting the value I, will trigger the call to a function td_intra_actions_int, which must be provided by the integrator.

 


Mapset Configuration File

Table 4-11 lists and defines mapsets available to be referenced by the CICS application. For more information, see tcxmapgen(1) in System Commands and Transactions.

The filename is mapsets.desc.

The format of a MAPSET definition is:

[mapset]
<field_name_1>=<field_value_1>
<field_name_2>=<field_value_2>
… …
<field_name_n>=<field_value_n>

For example,

[mapset]
name=ABANNER
filename=abanner.mpdef
Table 4-11 Mapset Parameters

Field Name
Type
Values
Description
NAME
X(8)
Mandatory
Name of the mapset.
DESCRIPTION
X(60)
Optional
A small textual comment zone for description of the resource.
FILENAME
X(79)
Mandatory
This specifies the physical (binary) file name of the mapset, which is generated by the tcxmapgen tool.
It will be searched in directories defined by the KIX_MAP_PATH environment variable if the absolute path is not specified.
If this field is not specified, the default mapset binary file name <MAPSET_name>.mpdef will be used, in which the <MAPSET_name> is the MAPSET name parameter specified in CICS MAP related APIs
RESIDENT
Bool
NO | YES
Specifies the residence status of the map set.
  • NO: The map set is not to be permanently resident.
  • YES: The map set is to be loaded on first reference and is then to be permanently resident in virtual storage, but is to be pageable by the system.
swastatus
X(10)
ENABLED|DISABLED
Specifies the resource status.•If set to ENABLED, the resource is available.•If set to DISABLED, the resource is unavailable for use by the system.
Usage
X(10)
NORMAL | TRANSIENT
This attribute specifies the caching scheme to be used once the MAPSET is loaded. NORMAL keeps the MAPSET loaded in a cache. Unload it when the cache overflows and it is the oldest, least used MAPSET in the cache.TRANSIENT unloads the MAPSET if it is not being used.

 


Typeterm Configuration File

Table 4-12 lists and defines Typeterms supported by ARTTCP.

The filename is typeterms.desc

The format of a TYPETERM definition is:

[typeterm]
<field_name_1>=<field_value_1>
<field_name_2>=<field_value_2>
… …
<field_name_n>=<field_value_n>

For example,

[typeterm]
name=IBM-3278-2
userarealen=255

Table 4-12 Typeterm Parameters
Field Name
Type
Values
Description
ALTSCREENCOLUMN
Short
{80|132|…}
Specifies the terminal screen size total columns. If the SCRNSIZE=alternate, this parameter is mandatory.
ALTSCREENROW
Short
{24|32|43|27|…}
Specifies the terminal screen size total rows If the SCRNSIZE=alternate, this parameter is mandatory.
DESCRIPTION
X(79)
Optional
A small textual zone for description of the resource.
EXTERCODE
X(10)
{ibm-37 | ibm-1388|ibm-1380|…}
Specifies which encoding type of outbound data is used. The value of this attribute could be any EBCDIC encoding type used in z/OS platform. The default value is ibm-37.
INTERCODE
X(10)
{ASCII | UTF-8|Shift-JIS|…}
Specifies which encoding type of inbound data is used. The value of this attribute could be any encoding type used in universal platform. The default value is ASCII.
NAME
X(79)
Mandatory
Name of the typeterm.
PROGSYMBOLS
Bool
NO | YES
Specifies whether the programmed symbol (PS) facility is supported or not. The default value is NO.
SCRNSIZE
Bool
DEFAULT|ALTERNATE
Optional. Specifies whether to send/receive map/text with alternative screen size or not.
The default value is DEFAULT which does not send/receive map/text with alternative screen size.
SOSI
Bool
NO | YES
Specifies whether mixed EBCDIC and double-byte character set (DBCS) is supported or not. The default value is NO.
color
Bool
NO | YES
Designates extended color attributes.
defscreencolumn
Short
80
Number of columns of the default screen size.
defscreenrow
Short
24
Number of rows of the default screen size.
hilight
Bool
NO | YES
Indicates whether a terminal supports the highlight feature or not.
logonmsg
Bool
NO | YES
Indicates whether the “Good Morning” (CSGM) transaction is automatically started on the terminal or not.
Oracle Tuxedo ART provides a default CSGM transaction. Please refer to section for the configuration of the default “Good Morning” (CSGM) transaction.
outline
Bool
NO | YES
Indicates whether the terminal supports field outlining or not.
swastatus
X(10)
ENABLED| DISABLED
Specifies the resource status.
  • If set to ENABLED, the resource is available.
  • If set to DISABLED, the resource is unavailable for use by the system
uctran
X(10)
NO | YES | TRAN
  • YES: translate lowercase alphabetic characters to uppercase.
  • NO: do not translate lowercase alphabetic characters to uppercase
  • TRAN: only translate the transaction ID from lowercase to uppercase.
userarealen
Short
0 ~ 255
The terminal control table user area (TCTUA) area size for the terminal.


  Back to Top       Previous  Next