To run your system, CICS needs information about your other system resources, including software resources such as programs and data, and hardware resources such as terminals, printers, and telecommunications links. Resource definition is the process by which you tell your CICS/400 system which resources to use, what their properties are, and how to use them.Information for each related type of resource may be thought of as being stored in a table.There is one table for each resource; for example, the file control table holds information about files,the terminal control table holds information about terminal devices, and so on.
Each table is an OS/400 file object and has its own physical and logical files.CICS/400 resource definitions are held as records within the physical files.
CICS/400 uses the information in these tables to control the interactions between your resources: between programs and terminals, or between different CICS systems,for example.
For each resource table definition, there are OS/400 CL commands that allow you to add, change, or display information held in these tables.Alternatively, you can use the OS/400 “Work with” panels to perform these operations on resource definitions.
CICS/400 includes a supplied transaction, CEDA, that provides access to the “Work with” panels, allowing you to maintain resource definitions while in a CICS/400 shell environment. Some resources can be changed and installed while CICS/400 is running, but for others you have to close down and restart the control region,before they take effect.
Resource definitions are loaded into the runtime environment at startup.In addition, you can install or modify certain runtime resource definitions after startup and initialization.
A CICS/400 system administrator is responsible for performing runtime modifications or deletions of runtime resource definitions without requiring the installation of resource definitions. This capability is provided by the INQUIRE,SET, and DISCARD commands, which can be used in application programs, or by using the CICS-supplied transaction CEMT. Another feature of CICS/400 resource definition is the auto installation of terminal resources.In a distributed processing system, there is likely to be a large number of terminals. Creating resource definitions for each one would not only be time-consuming but the resulting definitions would take up a large amount of storage space. CICS/400 allows for the creation of model terminal definitions that would apply to a group of terminals, for example all the 3270 display devices. When the user accesses CICS, the definition for the terminal is created by the system from the model. The terminal identifier is generated by the Device masking element of the system initialization table parameter CICS device processing (DEVCTL)..
IBM - AS/400 Related Interview Questions
|IBM - RPG Interview Questions||IBM - VSAM Interview Questions|
|IBM Cognos Interview Questions||IBM DB2 Interview Questions|
|System Administration Interview Questions||IBM AIX Interview Questions|
|SQL Interview Questions||AS400 Interview Questions|
|IBM BPM Interview Questions||Synopsys Interview Questions|
|Rpgle Interview Questions|
Ibm - As/400 Tutorial
Introducing Cics® For Iseries™
Defining A Basic Control Region
Security Requirements For Cics/400
Defining Your Own Control Region
Administering The Control Region
Administering A Cics/400 Shell
Defining Resources-reference Information
Autoinstall For Terminal Definitions
Introduction To Cics/400-supplied Transactions
Cemt—cics Master Terminal Transaction
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.