Your system administrator should be able to select the appropriate method for your particular environment. The three methods differ in their access control mechanisms and in their persistence mechanisms.
This method results in the generation of a resource definition JCL script that creates the required RDOs into the CSD system. You need someone with the proper access rights to submit the JCL job. Once complete, the RDO's are be persisted through the CSD mechanism. You need to manually install the resource group associated with these resource definitions.
For more information see the CICS Transaction Server for z/OS® Resource Definition Guide, which is part of the CICS Transaction Server for z/OS Information Center, available at http://publib.boulder.ibm.com/infocenter/cicsts/v4r1/index.jsp
Create resource definitions JCL (see Step B6. The File selection page of the Generate Runtime Code wizard).
Submit resource definition JCL (see Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
In this method the Generate Runtime Code wizard makes requests through the Application Deployment Manager component of Rational® Developer for System z® to dynamically create and install CICS Program, Transaction, and ProcessType resources on the remote z/OS system.
The Application Deployment Manager component of Rational Developer for System z provides a CICS Resource Definition client (CRD client) that communicates with a CICS Resource Definition server (CRD server) running inside a CICS primary connection region on a remote z/OS system (see the documentation for the Application Deployment Manager in the online help for Rational Developer for System z).
The CRD client sends requests to the CRD server to gather information and to create and install CICS resources. The CRD server uses the CICS primary connection region to retrieve default values for CICS resource attributes and as the default target region where resources are installed.
When the CRD server receives a request to create and install a resource definition the CRD server dynamically determines whether the CICS region is managed by CICSPlex® SM:
If CICSPlex SM does not manage the CICS region then the CRD server creates and installs the CICS resource definition using the CICS System Programming Interface (SPI) CREATE command. Resource definitions installed in this manner are persisted until the CICS region is cold started. Typically CICS regions are cold started only after service maintenance has been applied to CICS. Normally, CICS regions are warm started in order to install previously installed resource definitions.
In the Generate Runtime Code wizard select the check box Install the Program, Transaction, and ProcessType resources (see Step B8. The Compilation and Installation Options page of the Generate Runtime Code wizard).
For the CICS Service Flow Runtime for CICS Transaction Server for z/OS V3.2 or later, this option causes the Service Flow Runtime to dynamically creates the required CICS Resources when loading the service flow into memory. It requires that the Service Flow Runtime be granted the access rights to be able to create CICS Resource Definitions. The definitions are persisted in the sense that the Service Flow Runtime recreates the required resource definitions every time the service flow is loaded into memory.
For more information see the CICS Service Flow Runtime User's Guide (see the links in the topic Supported runtime environments for each project type).