The topics covered in this section are:
CICS®-deployed JAR files can be defined for CICS Transaction Server for OS/390® Version 2.1 and later systems.
Table 5 summarizes the action commands you can use with the EJDJDEF view.
Primary command | Line command | Description |
---|---|---|
ADD resdef version | ADD | Add a CICS-deployed JAR file definition to a resource group, as described in Adding resource definitions to a resource group. |
ALTER | n/a | Apply global changes to a set of CICS-deployed JAR file definitions as described in Figure 9. |
n/a | BRO | Browse a CICS-deployed JAR file definition in the data repository.
The format of the resulting panel is similar to that shown in Figure 37. All of the fields are nonmodifiable. |
CREate | CRE | Create a CICS-deployed JAR file definition and add it to the data repository, as described in Table 5. |
n/a | INS | For systems running CICS Transaction Server Version 2.1 and later, install a CICS-deployed JAR file in an active system, as described in Installing BAS CICS-deployed JAR file definitions. |
n/a | MAP | Display a visual map of business application services definitions using the specified definition as a starting point. |
REMove resdef version | REM | Remove a CICS-deployed JAR file definition from the data repository, as described in Remove a resource definition. |
n/a | UPD | Update a CICS-deployed JAR file definition in the data repository.
The format of the resulting panel is similar to that shown in Figure 37. Most of the fields are modifiable. |
There are no hyperlink fields in the EJDJDEF view.