CEDA

ADD
>>-ADd--Group(groupname1)--LIst(name)--+--------------------+--><
+-After(groupname2)--+
'-Before(groupname3)-'

ALTER
>>-ALter--| Resource |--Group(name)--| attribute list |--------><

APPEND
>>-APpend--LIst(list1)--To(list2)------------------------------><

CHECK
>>-CHeck--+-Group(name)-------------+--+---------------------+-><
'-List(list1, ..., listn)-' '-Remotesystem(sysid)-'

COPY
.-ALl----------.
>>-COpy--+--------------+--+-----------+--+---------+----------><
'-| Resource |-' '-| Route |-' +-REPLACE-+
'-MERGE---'

DEFINE
>>-DEFine--| Resource |--Group(name)--| attribute list |-------><

DELETE
>>-DELete--+--------------+--Group(name)--+--------+-----------><
+-ALl----------+ '-REMOVE-'
'-| Resource |-'

DISPLAY
>>-DIsplay--+-LIst(name)--+-------------+---------------+------><
| '-Group(name)-' |
'-Group(name)--+--------------+--+--------+-'
+-All----------+ '-RENAME-'
'-| Resource |-'

EXPAND
>>-Expand--+-LIst(name)--+-------------+---------------+-------><
| '-Group(name)-' |
'-Group(name)--+--------------+--+--------+-'
+-All----------+ '-RENAME-'
'-| Resource |-'

INSTALL
>>-Install--+--------------+--+-Group(name)-+------------------><
+-All----------+ '-LIST(name)--'
'-| Resource |-'

LOCK
>>-Lock--+-Group(name)-+---------------------------------------><
'-List(name)--'

MOVE
.-ALl----------.
>>-Move--+--------------+--+-----------+--+---------+--+--------+-><
'-| Resource |-' '-| Route |-' +-REPLACE-+ '-REMOVE-'
'-MERGE---'

REMOVE
>>-REMove--Group(name)--List(name)-----------------------------><

RENAME
>>-REName--+--------------+--+-----------+--+--------+---------><
+-ALl----------+ '-| Route |-' '-REMOVE-'
'-| Resource |-'

UNLOCK
>>-UNlock--+-Group(name)-+-------------------------------------><
'-List(name)--'

USERDEFINE
>>-USerdefine--| Resource |--Group(name)--| attribute list |---><

VIEW
>>-View--Group(name)--+--------------+-------------------------><
+-ALl----------+
'-| Resource |-'

CEDA continued
>>-------------------------------------------------------------><
Resource:
|--+-Connection(name)---+---------------------------------------|
+-CORbaserver(name)--+
+-DB2Conn(name)------+
+-DB2Entry(name)-----+
+-DB2Tran(name)------+
+-DJar(name)---------+
+-DOctemplate(name)--+
+-Enqmodel(name)-----+
+-File(name)---------+
+-Journalmodel(name)-+
+-Lsrpool(name)------+
+-Mapset(name)-------+
+-PARTItionset(name)-+
+-PARTNer(name)------+
+-PIpeline(name)-----+
+-PROCesstype(name)--+
+-PROFile(name)------+
+-PROGram(name)------+
+-Requestmodel(name)-+
+-Sessions(name)-----+
+-TCpipservice(name)-+
+-TDqueue(name)------+
+-Terminal(name)-----+
+-TRANClass(name)----+
+-TRANSaction(name)--+
+-TSmodel(name)------+
+-TYpeterm(name)-----+
+-Urimap(name)-------+
'-Webservice(name)---'
Route (Copy and Move):
|--Group(from-name)--+-AS(newname)--------------+---------------|
+-TO(to-name)--------------+
'-AS(newname)--TO(to-name)-'
Route (Rename):
|--+------------------+--+-------------+--+-------------+-------|
'-Group(from-name)-' '-AS(newname)-' '-TO(to-name)-'
attribute list:
|--for details consult the Resource Definition Guide------------|
You can go directly to the working screen to make your changes by typing:
CEDA function resource_type
For example:
CEDA DEF CONN
The CEDA keywords are as follows:
- AFTER
- Controls the placing of a group name in a list.
- ALL
- All resources are to be copied, deleted, displayed, installed, moved,
or renamed.
- AS
- The new name specified for a definition.
- BEFORE
- Controls the placing of a group name in a list.
- CONNECTION
- The remote system that your CICS system communicates with, using ISC
or MRO.
- CORBASERVER
- Defines the execution environment for enterprise beans and stateless
CORBA objects.
- DB2CONN
- Defines the CICS DB2® connection.
- DB2ENTRY
- Defines resources to be used by a transaction or group of transactions
when accessing DB2.
- DB2TRAN
- Associates a transaction ID with a DB2ENTRY.
- DJAR
- Defines a deployed JAR file.
- DOCTEMPLATE
- Defines a document templates to CICS. Document templates allow you to
perform variable substitution on documents in a manner similar to that done
by BMS for 3270 screens.
- ENQMODEL
- Use of ENQMODEL definitions provides an enqueue mechanism that serializes
access to a named resource across a specified set of CICS regions operating
with a sysplex.
- FILE
- The FILE definition describes to CICS file control the physical and
operational characteristics of a file.
- GROUP
- Every resource definition must have a GROUP name. The resource definition
becomes a member of the group and is installed in the CICS system when the
group is installed. The GROUP name can be up to 8 characters in length.
- JOURNALMODEL
- The name of a journal model containing specifications of journal names.
An MVS log stream name is associated with each journal model entry.
- LIST
- The name of the list for which a specified group is to be added, appended,
checked, displayed, expanded, installed, locked, removed, or unlocked.
- LSRPOOL
- The local shared resources (LSR) pool is a reserve of data buffers,
strings, and hiperspace buffers that VSAM uses when processing access requests
for certain files.
- MAPSET
- A series of different BMS maps.
- PARTITIONSET
- A table that describes to CICS how a display screen is to be partitioned.
- PARTNER
- The PARTNER definition enables CICS application programs to communicate
via APPC protocols to a partner application program running on a remote logical
unit. PARTNER is one of the four resources (the other three are PROFILE, CONNECTION,
and SESSION) that you must specify to allow the System Application Architecture
(SAA) communications interface to be used.
PIPELINE
A PIPELINE resource definition is used when a CICS application is in
the role of a Web service provider or requester. It provides information about
the message handler programs that act on a service request and on the response.
- PROCESSTYPE
- Use the CICS® business transaction services (BTS) API to define and execute complex business applications
called processes.
- PROFILE
- A group of programs that control a number of transactions or partners.
- PROGRAM
- The name of the program that is to control a given transaction.
- REQUESTMODEL
- A REQUESTMODEL resource definition provides the connection between an
Internet Inter-ORB Protocol (IIOP).
- SESSIONS
- The logical link of two systems that communicate using ISC or MRO.
- TCPIPSERVICE
- Use this resource definition to define which TCP/IP services are to
use CICS internal sockets support. The internal CICS services that can be
defined are IIOP and the CICS Web Interface.
- TDQUEUE
- The definition of each transient data queue used in your CICS system.
Queue types can be intrapartition, extrapartition, or indirect. Remote queues
cannot be specified explicitly; see the the CICS Resource Definition Guide for more information about defining transient data queues
to be remote.
- TERMINAL
- The definition of each terminal used in your CICS system. A terminal
can be any device linked to your system, for example, visual display units,
printers, facsimile machines. To simplify matters, it is possible to group
resources that have common features by using TYPETERM and through AUTOINSTALL.
- TO
- The new group to which a definition is to be copied.
- TRANCLASS
- The name of a user-defined class of transactions.
- TRANSACTION
- The name of the transaction. Within the transaction definition, you
can specify options such as transaction priority and length of the transaction
work area. You also add to the transaction name the names of related resources:
PROGRAM, PROFILE, and PARTITIONSET.
- TSMODEL
- The TSMODEL resource allows you to specify a TS queue name prefix, and
associate attributes with that name. You can also map names directly to a
shared TS pool (without the need for a shared sysid).
- TYPETERM
- Some of the common attributes of your terminals. This has to be defined
as part of the terminal definition.
URIMAP
A URIMAP is a resource definition that matches the URIs of HTTP or Web
service requests, and provides information on how to process the requests.
WEBSERVICE
A WEBSERVICE resource defines aspects of the run time environment for
a CICS application program deployed in a Web services setting, where the mapping
between application data structure and SOAP messages has been generated using
the CICS Web services assistant.
[[ Contents Previous Page | Next Page Index ]]