Build and Configure Mainframe Integration Projects

Run mainframe file hash migration

Backfills missing content hashes for Mainframe pipeline files so editable-sync and conflict detection can operate reliably.

Feature Context:

  • Supports migration of legacy pipelines where file hashes were not persisted.
  • Enables hash-based compatibility checks required by pull/link-folder workflows.

Use Cases:

  • Targeted migration for specific files by providing fileIds.
  • Pipeline-wide migration by sending an empty request body or an empty fileIds list.

Request Semantics:

  • fileIds omitted or empty: migrate all eligible files in the pipeline.
  • fileIds present: migrate only matching IDs in the current pipeline.

Required Permissions: replication-pipeline::create when permission harmonization is enabled; otherwise, replication-pipeline::manage.

post/v1/integration/mainframe/projects/{projectId}/pipelines/{pipelineId}/files/migration

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}/files/migration
  • Auth: HTTP bearer

Path parameters

projectIdstring required

Unique identifier of the project

pipelineIdstring required

Unique identifier of the pipeline

Request body

fileIdsstring[]

Optional list of file IDs to migrate. If omitted or empty, migration targets all files in the pipeline that need hash backfill.

Example request

{
  "fileIds": [
    "file-101",
    "file-205"
  ]
}

Response

Hash migration completed

updatedinteger

Count of files considered updated during migration

skippedinteger

Count of files skipped during migration

failedinteger

Count of files that failed migration

compatibilityReadyboolean

Whether pipeline is compatibility-ready after migration

Example response

{
  "skipped": 12,
  "compatibilityReady": true
}

Changes

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