Build and Configure Mainframe Integration Projects

Set the entry file (main script) for a Mainframe pipeline

Designates which script the pipeline should run as its main entry point.

Features:

  • Lets users clearly choose the script that should run first during pipeline execution.
  • Prevents accidental updates across projects by validating project and pipeline association.

Use Cases:

  • Set a .sqd or .rpl file as the main script from VS Code after create, pull, or refactor.
  • Correct the entry script path after files are moved or renamed.

Entry File Name Format:

  • entryFileName must be the fully qualified file name within the pipeline workspace (include relative folders when applicable).
  • Example values: main.sqd, scripts/main/main.sqd, flows/reverse/entry.rpl.

Authorization: Requires either replication-pipeline::create or replication-pipeline::update when permission harmonization is enabled; otherwise, replication-pipeline::manage.

post/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/entry-file

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}/entry-file
  • Auth: HTTP bearer

Path parameters

projectIdstring required

Unique identifier of the project

pipelineIdstring required

Unique identifier of the pipeline

Request body

entryFileNamestring required

Fully qualified file name to set as the pipeline entry (main) script within the pipeline workspace

Example request

{
  "entryFileName": "scripts/main/main.sqd"
}

Response

Entry file name updated successfully

Changes

No recorded changes to this operation across all 1 revision of this API.