Chapter 5: Resource Definitions

This chapter describes how to:

Introduction

The resource definitions stored by MTO are different in both content and form to those stored on the mainframe. Many resource types and attributes that you can define on the mainframe are meaningless in the Windows or UNIX environment, for example LSRPOOL. MTO recognizes these resource types and attributes but takes no action on them. Conversely, MTO understands some additional attributes that only make sense in the Windows or UNIX environment, and some of these are mandatory.

The following table lists all the types of resource definition used or recognized by MTO. For each type of resource definition, the name by which it is known in the .rdt file used for exchanging resource definitions with other Enterprise Server with MTO systems is given, followed by an indication of the support provided, then any abbreviation used within the interface and its meanings. Mainframe resource types are listed first, followed by Micro Focus extensions.

Keyword in .rdt file Used or recognized Abbreviation Meaning
CONNECTION Used
Sys62
SysC
LU6.2 connection
CCI connection
FILE Used FCT file control table
LSRPOOL Recognized    
MAPSET Recognized    
PARTITIONSET Recognized    
PARTNER Recognized    
PROFILE Recognized    
PROGRAM Used PPT program processing table
SESSIONS Recognized    
TERMINAL Used Term terminal
TRANCLASS Recognized    
TRANSACTION Used PCT program control table
TYPETERM Used T-type terminal type
TDQUEUE Used DCT destination control table
_JOURNAL Extension JCT journal control table
_PGMLIST Extension PLT program load table
_SIGNON Extension SNT signon table
_SIT Extension SIT system initialization table
_STARTUPLIST Extension    
_TEMPSTORAGE Extension TST temporary storage table
_XOPENCOMPAT Extension XAT XA-compliant database table

Note: For detailed information concerning the resource types and attributes that are used by MTO, see the help topic Resource Definitions.

The CICS resources are defined in the resource definition file dfhdrdat (with index dfhdrdat.idx). This is an ISAM file.

When Enterprise Server runs the application, it needs to know where the application's dfhdrdat file is. You specify its location using the TXRDTP environment variable.

Exchanging Resource Definitions Between Resource Definition Files

You can import and export resource definitions from and to other resource definition files held on the same or different installations of Enterprise Server with MTO.

You use the following command line tools for importing and exporting resources:

casrdtup Imports the resource definition tables in a specified file into the resource definition file dfhdrdat
casrdtex Exports the resource definition tables from the resource definition file dfhdrdat to a specified file

These tools use the TXRDTP environment variable to find the directory containing the dfhdrdat. You can enter casrdtex and casrdtup at the command line to display a full list of the switches available.

Maintaining Resource Definitions

When you have downloaded your resource definitions from the mainframe, they can be maintained in the Windows or UNIX environment. MTO uses several different types of resource, such as programs and files. The standard resources that can be used by most systems are predefined. You need to add definitions only for those resources that are used specifically by your system.

Types of Resource

Each type of resource is defined in a separate table. For example, programs are defined in a processing program table (PPT) and files in a file control table (FCT). For each resource type, more than one table can be defined for the same system. And more than one table for the same resource type can be used by the system, except for the system initialization table (SIT), which defines parameters to control the initialization of the system, and the sign-on table (SNT), which defines user sign-on authorizations.

Note: Not all programs need entries in the PPT. PPT entries are required for the following types of program:

They are also required for data tables.

Tables for the same or different resource types can be combined into a group. For example, you will probably find it convenient to combine all the tables for the resources used by an application (or set of related applications) into a single group.

All the groups that you want to be included in the enterprise server startup are defined in a startup list. During startup, MTO uses this list to check that the resources are available and performs appropriate initialization procedures on them.

More information about system initialization and the startup list is given in the chapter Configuring MTO-enabled Enterprise Servers.

Facilities for Maintaining Resources

You can edit the resource definitions using ESMAC, which provides a graphical user interface. For more information see the section Controlling CICS Resources in the chapter Administering MTO-enabled Enterprise Servers.

Alternatively, you can edit them using a text editor, but to do this, you first need to export the resource definition tables from the dfhdrdat file, and when you have finished editing, you need to import the tables back again. For more information about importing and exporting resources see the section Exchanging Resource Definitions Between Resource Definition Files.


Copyright © 2006 Micro Focus (IP) Ltd. All rights reserved.