CICS Transaction Server Resource Builder

https://www.ibm.com/docs/en/cics-resource-builder
Admin
CICS Transaction Server Resource Builder is a tool for defining, managing, and building CICS...
Tokens:70,890
Snippets:654
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### DFHCSDUP commands file example

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=building-input-files-dfhcsdup

An example of a DFHCSDUP commands file generated by the 'zrb build' command. It includes a header with metadata about the build process and the actual DEFINE commands for CICS resources.

```shell
* ---\n* createTime: 2022-07-15T10:08:48.1575117+01:00                                                                           
* createTimeFileEncoding: Cp1252                                                
* application:                                                                  
*   name: CICS Sandpit Application                                              
*   source: ""                                                                  
* resourceModel:                                                                
*   source: |-\n*     c:\\my-models\\my-simple.cicsresourcemodel.yaml                             
*   target: cicsts-6.1.0                                                        
* resourceDefinitions:                                                          
*   source: |-\n*     c:\\my-definitions\\my-simple.cicsresourcedefinition
*     s.yaml  
DEFINE URIMAP(APCLNT01) 
      DESCRIPTION(APP1 urimap for calling outbound URIs)
      GROUP(WEBAPP)
      HOST(10.11.12.13)
      PATH(/apclnt01)
      SCHEME(HTTPS)
      STATUS(ENABLED)
      USAGE(CLIENT)
DEFINE URIMAP(APSERV01) 
      DESCRIPTION (APP1 urimap for inbound HTTPS requests)
      GROUP(WEBAPP)
      HOST(*)
      PATH(/apserv01)
      PROGRAM(APSERV01)
      SCHEME(HTTPS)
      STATUS(ENABLED)
      TRANSACTION(CWBA)
      USAGE(SERVER)

```

--------------------------------

### Example DFHCSDUP commands file content

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=dfhcsdup-preparing-csd

This snippet shows example content of a DFHCSDUP commands file generated by the `zrb build` command. It defines two programs, APSERV01 and APSERV02, within the `WEBAPP` group, specifying various attributes for each program.

```text
DEFINE PROGRAM(APSERV01) GROUP(WEBAPP)
      RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
      STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
      CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
      EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)

DEFINE PROGRAM(APSERV02) GROUP(WEBAPP)
      RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
      STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
      CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
      EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)
```

--------------------------------

### Example prepare commands file content

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=dfhcsdup-preparing-csd

This snippet shows example content of a prepare commands file generated by the `zrb build` command. It contains a command to delete all resources from the `WEBAPP` group and remove the group from any lists it belongs to, preparing the CSD for new resource definitions.

```text
DELETE ALL GROUP(WEBAPP) REMOVE
```

--------------------------------

### Build DFHCSDUP commands from single resource model file

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=building-input-files-dfhcsdup

This example shows how to create a DFHCSDUP commands file from a single YAML file that contains both the resource model and application blocks. It takes a resource model file and an application file as input and outputs a DFHCSDUP commands file. No external dependencies are specified for this command itself, but it relies on the zrb tool being installed.

```bash
zrb build --model my-models/my-simple.cicsresourcemodel.yaml --resources my-definitions/my-simple.cicsresourcedefinitions.yaml --output my-DFHCSDUPcommands/my_DFHCSDUPcommands.out
```

--------------------------------

### Example of Successful GPG Verification Output

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-verifying-integrity-cics-ts-resource-builder-product-files

This example shows the expected output when the GPG verification of the CICS TS Resource Builder zip file is successful. It confirms the signature's validity and displays the public key's fingerprint.

```text
$ gpg --verify cics-resource-builder-RC-1.0.6.sig.asc cics-resource-builder-RC-1.0.6.zip
gpg: Signature made Tue 15 Jul 13:48:24 2025 BST
gpg:                using RSA key E648E5B9E5AF9E089F15BE3B7BEE92D8F99FAF9D
gpg: Good signature from "IBM CICS Products Set01 <psirt@us.ibm.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: E648 E5B9 E5AF 9E08 9F15  BE3B 7BEE 92D8 F99F AF9D
```

--------------------------------

### DFHCSDUP File Output Example

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=tutorials-tutorial-building-dfhcsdup-file-using-cics-ts-resource-builder-images

This snippet shows a typical output from a DFHCSDUP file generated by the 'zrb build' command. It includes metadata like creation time and encoding, followed by resource definitions. The example demonstrates the DEFINE URIMAP command, specifying the resource type, group, description, and path.

```text
* ---
* createTime: 2024-10-22T14:23:18.003Z
* createTimeFileEncoding: IBM-1047
* application:
*   description: Urimap model
*   name: Urimap model
*   source: ""
* resourceModel:
*   source: /resourceModels/model.yaml
*   target: cicsts-6.1.0
* resourceDefinitions:
*   source: /resourceDefinitions/resource.yaml
DEFINE URIMAP(APCLNT01) GROUP(WEBAPP)
DESCRIPTION(URIMAP for calling outbound URIs)
       PATH(/apclnt01)

```

--------------------------------

### Generate DFHCSDUP ADD Command for Group and List

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=model-defining-groups-lists

This is an example of a DFHCSDUP ADD command generated by the CICS TS resource builder. It shows how the system programmer's configuration, linking a group name (derived from a constraint) to a specific list, is translated into an installation command for CICS.

```clist
ADD GROUP(MYAORGRP) LIST(AORLIST)
```

--------------------------------

### Install CICS Resource Definitions using CEDA

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=resources-installing-updated-resource-definitions-into-cics-region

This command installs CICS resource definitions from a specified list into the active CICS system. It requires the CEDA transaction to be available in the CICS environment. The input is a list name, and the output is the updated CICS system state.

```CICS EXEC
CEDA INSTALL LIST(APPLIST)
```

--------------------------------

### Verifying Environment Variables with echo

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-cics-ts-resource-builder-zos-unix-system-services

These commands verify that the environment variables `_BPXK_AUTOCVT` and `_CEE_RUNOPTS` have been correctly set and are accessible in the current shell session. They should output the values configured in the profile.

```bash
echo $_BPXK_AUTOCVT
echo $_CEE_RUNOPTS
```

--------------------------------

### Make zrb Executable on Linux/Mac

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-cics-ts-resource-builder-linux-z-windows-mac-linux

Grants execute permissions to the 'zrb' command for the current user on Linux and macOS systems. This allows the command-line tool to be run directly.

```shell
chmod u=rx zrb
```

--------------------------------

### resourceImport YAML Configuration Example

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=reference-cics-ts-resource-builder-yaml-syntax

This YAML configuration defines the settings for importing CICS resources. It specifies the schema version, output file destinations for application constraints, resource models, and resource definitions, along with input configurations for the application and model, and import selectors.

```yaml
schemaVersion: resourceImport/1.0
resourceImport:
  destinations:
    application: cics-application.yaml
    model: cics-model.yaml
    resources: cics-resources.yaml
    exceptions: cics-exceptions.yaml
    exceptionsModel: cics-exceptions-model.yaml

  applicationInput:
    name: My application
    description: Testing application constraints
    constraints:
     - id: app-name-prefix
       prefix: APCLNT
    configuration:
      - list:
          name:APPWEB
          group: 
            constraintId: app-name-prefix

  modelInput:
    target: cicsts-6.1.0
    defines:
     - id: client-urimap
       type: urimap
       attributes:
         public:
         name:
           required: true
           constraintId: app-name-prefix

  imports:
    - modelTypeId: client-urimap
      type: urimap
      exceptions: yes
      importAnalysis: complete
      selectors:  
        usage: client

```

--------------------------------

### Resource Model with Constraints (YAML)

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=troubleshooting

This YAML example defines a resource model for CICS TS, including application-level constraints for name prefixes and group names, and a specific constraint for SSL cipher suite file names. It also defines a 'client-urimap' resource type with attributes that reference these constraints.

```YAML
schemaVersion: resourceModel/1.0
application:
  name: CICS Sandpit Application
  constraints:
    - id: app-prefix
      prefix: AP
    - id: group-name
      pattern: "^[A-Z0-9]*$"
    - id: SSL-cipher-suite-files
      pattern: "^[A-Za-z0-9_#@\\-')]+(?i).xml$"

resourceModel:
  target: cicsts-6.1.0
  defines:
    - id: client-urimap
      description: for calling outbound URIs
      type: urimap
      attributes:
        public:
          name: 
            required: true
            constraintId: app-prefix
            description: Specfiy the name of URIMAP for outbound URIs
          group: 
            required: true
            constraintId: group-name
            description: Specify the name of the RDO group
          description: 
            required: false
          path:
            required: true
          ciphers:
            required: true
            constraintId: SSL-cipher-suite-files
        private:
          host: 10.11.12.13
          usage: CLIENT
          status: ENABLED
          scheme: HTTPS
```

--------------------------------

### Example Import Report of Discarded Resources

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=tiecrd-4-deal-resource-definitions-that-do-not-match-your-resource-model

This snippet shows how a resource exception is reported in the import report when it's discarded due to not aligning with the built resource model. It highlights the reason for the exception and the specific resources affected.

```yaml
Discarded:
    - Reason: Name model attribute did not match the application constraint id app-name-prefix with prefix APCLNT
      Resources:
        - name: "APHELP", group: "WEBAPP"
```

--------------------------------

### Expose Resource Attributes with YAML Blocks

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=tutorials-tutorial-creating-resource-model-yaml

This snippet demonstrates how to define public attributes for a resource model using YAML. It specifies which attributes are required or optional and provides descriptions for hover help in IDEs. The `client-urimap` resource type is used as an example, exposing `name`, `group`, `description`, and `path`.

```yaml
schemaVersion: resourceModel/1.0
resourceModel:
  target: cicsts-6.1.0
  defines:
    - id: client-urimap
      description: For calling outbound URIs
      type: urimap
      attributes:
        public:
          name: 
            required: true
            description: Specfiy the name of URIMAP for outbound URIs
          group: 
            required: true
            description: Specify the name of the RDO group
          description: 
            required: false
          path:
            required: true
            description: Specify path component of client URIs

```

```yaml
resourceDefinitions:
  - client-urimap:
      name: APCLNT01
      description: URIMAP for calling outbound URIs
      group: WEBAPP
      path: /apclnt01

```

--------------------------------

### Build DFHCSDUP commands with separate application constraints file

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=building-input-files-dfhcsdup

This example demonstrates building a DFHCSDUP commands file using a resource model YAML file and a separate application constraints YAML file via the `--application` argument. It generates the output file from a resource model, an application constraints file, and resource definitions. This command requires the zrb tool and the specified input files.

```bash
zrb build --model my-models/my-multiapp.cicsresourcemodel.yaml --application my-applications/my-app1.cicsappconstraints.yaml --resources my-definitions/my-app1.cicsresourcedefinitions.yaml --output my-DFHCSDUPcommands/my_DFHCSDUPcommands.out
```

--------------------------------

### Transferring Files with SFTP

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=resources-running-dfhcsdup-prepare-update-csd

Demonstrates how to use SFTP commands to create a directory, change into it, and upload a file to the z/OS UNIX System Services file system. This is a prerequisite for preparing DFHCSDUP input files.

```sftp
sftp> mkdir my-DFHCSDUPcommands
sftp> cd my-DFHCSDUPcommands
sftp> mput my_DFHCSDUPcommands.out
```

--------------------------------

### Navigate to CICS TS resource builder bin Directory

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-cics-ts-resource-builder-linux-z-windows-mac-linux

Changes the current directory to the 'bin' folder within the CICS TS resource builder installation directory. This is a prerequisite for making the 'zrb' command executable.

```shell
cd <install-dir>/cics-resource-builder/bin
```

--------------------------------

### Build prepare commands file with zrb build

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=dfhcsdup-preparing-csd

Use the `zrb build` command with the `--prepare` option to generate DFHCSDUP commands and prepare commands files. This command requires the paths to the resource model, resource definitions, and output location. Optionally, an application constraints file can be provided. The output includes a DFHCSDUP commands file and a prepare commands file.

```shell
zrb build --model <model file path> [--application <application constraints file path>] --resources <resources file path> --output <filepath to the DFHCSDUP commands file> --prepare <filepath to the prepare commands file>
```

--------------------------------

### Extract CICS TS resource builder Archive

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-cics-ts-resource-builder-linux-z-windows-mac-linux

This command extracts the CICS TS resource builder zip archive. Ensure you have a suitable unzipping tool installed. The command operates within the specified temporary directory.

```shell
unzip cics-resource-builder-<version>.zip
```

--------------------------------

### Build DFHCSDUP File using CICS TS Resource Builder (Container)

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=tutorials-tutorial-building-dfhcsdup-file-using-cics-ts-resource-builder-images

This command executes the CICS TS resource builder within a container to generate a DFHCSDUP file. It uses Podman to run the container, mounting local directories for input and output. The `build` command takes the resource definition and model YAML files as input and specifies the output location for the DFHCSDUP file. Different container images are available for Linux and IBM Z.

```bash
podman run --name <container-name> -it -v $PWD/resources:/input <internal-image-registry>/<image-name> build --resources /input/definitionfile.yaml --model /input/modelfile.yaml --output /output/DFHCSDUP

```

```bash
# Linux example
podman run --name <container-name> -it -v $PWD/resources:/input <internal-image-registry>/cics-resource-builder-ubi8:1.0.6 build --resources /input/definitionfile.yaml --model /input/modelfile.yaml --output /output/DFHCSDUP

```

```bash
# IBM Z example
podman run --name <container-name> -it -v $PWD/resources:/input <internal-image-registry>/cics-resource-builder-zos:1.0.6 build --resources /input/definitionfile.yaml --model /input/modelfile.yaml --output /output/DFHCSDUP

```

--------------------------------

### Copying Resource Builder Directory

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-cics-ts-resource-builder-zos-unix-system-services

This command copies the extracted CICS TS Resource Builder directory from a temporary location to the final installation directory on z/OS UNIX System Services. It uses the 'cp -R' command for recursive copying.

```bash
cp -R <temp-dir>/cics-resource-builder <install-dir>
```

--------------------------------

### JCL Example: Running DFHCSDUP with Prepare Commands File

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=dfhcsdup-preparing-csd

This JCL job executes the DFHCSDUP utility to process a CICS System Definition (CSD) file. It uses a 'prepare' commands file, generated by the 'zrb build' command, as input. The job specifies read-only access and a page size of 60, with no compatibility checks.

```JCL
//CSDPREP  JOB MSGCLASS=H,MSGLEVEL=(1,1),
//         CLASS=A,NOTIFY=USERX,REGION=4M
//STEP1    EXEC PGM=DFHCSDUP,REGION=0M,
//         PARM='CSD(READONLY),PAGESIZE(60),NOCOMPAT'
//STEPLIB  DD DSN=CICS.TS.SDFHLOAD,DISP=SHR
//DFHCSD   DD DISP=SHR,DSN=CICS.APPLICATIONS.DFHCSD
//outdd    DD SYSOUT=A
//SYSPRINT DD SYSOUT=A
//SYSIN    DD PATH='/u/userx/applications/prepare.csdup',
//         RECFM=F
//

```

--------------------------------

### Example Resource Exception in Exceptions File

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=definitions-creating-import-yaml-file

This is an example of a resource definition flagged as a resource exception, as it might appear in the exceptions file generated by CICS TS Resource Builder. It shows the structure of an exception, including its type (e.g., `client-urimap-exception`) and its attributes.

```yaml
resourceDefinitions:
- client-urimap-exception:
    name: APHELP
    path: /aphelp
    scheme: HTTP
```

--------------------------------

### zrb build command syntax

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=building-input-files-dfhcsdup

The command-line syntax for executing the 'zrb build' command. It specifies the required and optional file paths for resource model, application constraints, resource definitions, and the output file.

```bash
zrb build -m (--model) <resource model file path> [-a (--application) <application constraints file path>] -r (--resources) <resource definition file path> -o (--output) <filepath to the DFHCSDUP commands file generated by the `build` command>
```

--------------------------------

### CICS DFHCSDUP Resource Definitions (definitions.csdup)

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=reference-example-dfhcsdup-extract-file-definitionscsdup

This snippet contains example definitions for CICS resources in the DFHCSDUP format. It includes definitions for PROGRAM, TRANSACTION, and URIMAP resources, commonly used for configuring CICS environments. These definitions are part of the CICS TS resource builder and can be used for importing existing CSD resource definitions.

```cicsddup
DEFINE PROGRAM(APSERV01) GROUP(WEBAPP)
          RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
          STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
          CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
          EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)
          DEFINETIME(22/04/06 10:57:59) CHANGETIME(22/04/06 10:57:59)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE PROGRAM(APSERV02) GROUP(WEBAPP)
          RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
          STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
          CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
          EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)
          DEFINETIME(22/04/06 10:58:50) CHANGETIME(22/04/06 10:58:50)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE PROGRAM(APSERV03) GROUP(WEBAPP)
          RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
          STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
          CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
          EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)
          DEFINETIME(22/04/06 10:59:05) CHANGETIME(22/04/06 10:59:05)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE PROGRAM(APSERV04) GROUP(WEBAPP)
          RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
          STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
          CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
          EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)
          DEFINETIME(22/04/06 10:59:14) CHANGETIME(22/04/06 10:59:14)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE PROGRAM(WEBAPP) GROUP(WEBAPP)
          RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
          STATUS(ENABLED) RSL(0) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
          CONCURRENCY(QUASIRENT) API(CICSAPI) DYNAMIC(NO)
          EXECUTIONSET(FULLAPI) JVM(NO) HOTPOOL(NO)
          DEFINETIME(22/04/06 10:59:50) CHANGETIME(22/04/06 10:59:50)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE TRANSACTION(WAPP) GROUP(WEBAPP)
          PROGRAM(WEBAPP) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
          PRIMEDSIZE(0) TASKDATALOC(ANY) TASKDATAKEY(USER)
          STORAGECLEAR(NO) RUNAWAY(SYSTEM) SHUTDOWN(DISABLED) ISOLATE(YES)
          DYNAMIC(NO) ROUTABLE(NO) PRIORITY(1) TCLASS(NO)
          TRANCLASS(DFHTCL00) DTIMOUT(NO) RESTART(NO) SPURGE(YES)
          TPURGE(YES) DUMP(YES) TRACE(YES) CONFDATA(NO) OTSTIMEOUT(NO)
          ACTION(BACKOUT) WAIT(YES) WAITTIME(0,0,0) INDOUBT(BACKOUT)
          RESSEC(NO) CMDSEC(NO) EXTSEC(NO) TRANSEC(1) RSL(0)
          DEFINETIME(22/04/06 11:00:08) CHANGETIME(22/04/06 11:00:08)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE URIMAP(APCLNT01) GROUP(WEBAPP)
    DESCRIPTION(urimap for calling outbound URIs)
          STATUS(ENABLED) USAGE(CLIENT) SCHEME(HTTPS) PORT(NO)
          HOST(10.11.12.13) PATH(/apclnt01) SOCKETCLOSE(0) ANALYZER(NO)
          CIPHERS(defaultciphers.xml) AUTHENTICATE(NO) REDIRECTTYPE(NONE)
          DEFINETIME(22/04/06 10:56:28) CHANGETIME(22/05/27 11:02:53)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE URIMAP(APCLNT02) GROUP(WEBAPP)
    DESCRIPTION(urimap for calling outbound URIs)
          STATUS(ENABLED) USAGE(CLIENT) SCHEME(HTTPS) PORT(NO)
          HOST(10.11.12.13) PATH(/apclnt02) SOCKETCLOSE(0) ANALYZER(NO)
          CIPHERS(defaultciphers.xml) AUTHENTICATE(NO) REDIRECTTYPE(NONE)
          DEFINETIME(22/04/06 10:56:28) CHANGETIME(22/05/27 10:55:33)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE URIMAP(APCLNT03) GROUP(WEBAPP)
    DESCRIPTION(urimap for calling outbound URIs)
          STATUS(ENABLED) USAGE(CLIENT) SCHEME(HTTPS) PORT(NO)
          HOST(10.11.12.13) PATH(/apclnt03) SOCKETCLOSE(0) ANALYZER(NO)
          CIPHERS(defaultciphers.xml) AUTHENTICATE(NO) REDIRECTTYPE(NONE)
          DEFINETIME(22/04/06 10:56:44) CHANGETIME(22/05/27 10:55:43)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE URIMAP(APCLNT04) GROUP(WEBAPP)
          STATUS(ENABLED) USAGE(CLIENT) SCHEME(HTTPS) PORT(NO)
          HOST(10.11.12.13) PATH(/apclnt04) SOCKETCLOSE(0) ANALYZER(NO)
          CIPHERS(defaultciphers.xml) AUTHENTICATE(NO) REDIRECTTYPE(NONE)
          DEFINETIME(22/05/27 11:08:57) CHANGETIME(22/05/27 11:09:03)
          CHANGEUSRID(CICSUSER) CHANGEAGENT(CSDAPI) CHANGEAGREL(0740)
    DEFINE URIMAP(APHELP) GROUP(WEBAPP)
          STATUS(ENABLED) USAGE(CLIENT) SCHEME(HTTP) PORT(NO)
```

--------------------------------

### Import Public Key to GPG

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-verifying-integrity-cics-ts-resource-builder-product-files

This command imports the saved public key into the GPG keyring. This step is necessary to allow GPG to verify signatures made with that key.

```bash
gpg --import cics-resource-builder-product.pub.key
```

--------------------------------

### Specifying DFHCSDUP Input as PDSE Member in JCL

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=resources-running-dfhcsdup-prepare-update-csd

Provides an example of how to configure the `SYSIN` DD statement in a JCL job to read DFHCSDUP commands from a specific member of a PDSE. This is used when running DFHCSDUP as a batch program.

```jcl
//SYSIN    DD DSN=<HLQ>.CSDIN(DEFCMDS),DISP=SHR
/*
```

--------------------------------

### YAML Example: Attribute Precedence

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=release-notes

Demonstrates how multiple instances of the same attribute in a YAML block are handled, where the last instance takes precedence. This illustrates a known limitation of the resource builder.

```yaml
- bank-logic-program:
    name: BNKLG01
    cedf: NO
    cedf: NO
    cedf: YES
```

--------------------------------

### Error: CICS Resource Builder Signature Verification Failed

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=installing-planning-cics-ts-resource-builder-container-images

This example illustrates an error message encountered when the signature of a CICS Resource Builder container image cannot be verified, typically due to disabled sigstore attachment reading.

```bash
$ podman pull icr.io/ibm-cics-ts/<image-name>:1.0.6
zosError: Source image rejected: A signature was required, but no signature exists
```

--------------------------------

### Define Program Resource with Naming Convention (YAML)

Source: https://www.ibm.com/docs/en/cics-resource-builder/1.0_topic=model-defining-groups-lists

This YAML defines a resource model for a 'program-web-frontend' type. It enforces that the 'name' and 'group' attributes are required, with the 'group' attribute needing to conform to a specified naming convention identified by 'wor-group-prefix'.

```yaml
schemaVersion: resourceModel/1.0
resourceModel:
  target: cicsts-6.1.0
  defines:
  - id: program-web-frontend
    type: program
    attributes:
      public:
        name: 
          required: true
        group:
          required: true
          constraintId: wor-group-prefix
```
Tokens:
Raw