---
title: "Generate mainframe application scripts"
method: POST
path: "/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/application"
tags: ["Build and Configure Mainframe Integration Projects"]
---

# Generate mainframe application scripts

`POST /v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/application`

## Request

- Base URL: `https://integration-adapter.connect.cloud.precisely.com`
- URL: `https://integration-adapter.connect.cloud.precisely.com/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/application`
- Auth: HTTP bearer

Generates the mainframe pipeline scripts for a given pipeline.

**Process Overview:**
1. **Request Validation** - Validates pipeline ID and parameters
2. **Script Generation** - Generates the mainframe application scripts
3. **Response** - Returns success status and message

**Parameters:**
- **forceRegeneration**: When true, regenerates scripts even if they already exist. When false (default), skips regeneration if scripts are already present.
- **useSchemaVariables**: When true (default), uses variables for schema references in generated scripts. When false, uses hardcoded schema names.
- **sourceObjectCase**: Applies case transformation to source object names (schemas, tables, columns) in the generated scripts. Options include NONE, MATCH_ORIGINAL_CASE, SENTENCE_CASE, LOWER_CASE, UPPER_CASE, TOGGLE_CASE, CAPITALIZE_EACH_WORD.
- **targetObjectCase**: Applies case transformation to target object names (schemas, tables, columns) in the generated scripts. Same options as sourceObjectCase.

**Key Features:**
- Supports case transformation for object names
- Optional force regeneration
- Variable usage for schema

**Use Cases:**
- Generate mainframe scripts for a pipeline
- Re-generate scripts with updated configurations

**Required Permissions:** Either `replication-pipeline::create` or `replication-pipeline::update` when permission harmonization is enabled; otherwise, `replication-pipeline::manage`.

## Path parameters

- `projectId` string, required
- `pipelineId` string, required

## Query parameters

- `forceRegeneration` boolean
- `useSchemaVariables` boolean
- `sourceObjectCase` 'NONE' | 'MATCH_ORIGINAL_CASE' | 'SENTENCE_CASE' | 'LOWER_CASE' | 'UPPER_CASE' | 'TOGGLE_CASE' | 'CAPITALIZE_EACH_WORD'
- `targetObjectCase` 'NONE' | 'MATCH_ORIGINAL_CASE' | 'SENTENCE_CASE' | 'LOWER_CASE' | 'UPPER_CASE' | 'TOGGLE_CASE' | 'CAPITALIZE_EACH_WORD'

## Response `201`

Application scripts generated successfully

- GenerateApplicationResponse: Response containing the result of an application generation operation
  - `success` boolean: Indicates whether the application generation was successful
  - `statusMessage` string: Status message providing details about the generation result

## Other responses

- `400`: Bad Request - Invalid pipeline ID or parameters
- `401`: Unauthorized - Authentication required, valid credentials not provided
- `403`: Forbidden - User lacks 'replication-pipeline::create' or 'replication-pipeline::update' when permission harmonization is enabled, or legacy 'replication-pipeline::manage' otherwise
- `404`: Not Found - Pipeline does not exist
- `409`: Conflict - Application scripts already exist
- `500`: Internal Server Error - Failed to generate application

---

[API](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service.md) · [All operations](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service/llms.txt) · [OpenAPI document](https://skmtc.dev/precisely/apis/precisely-integration-adapter-service/revisions/2d2629f4987d?raw)