Skip to content

Commit 5bca466

Browse files
authored
Update per review feedback
1 parent cc87dcb commit 5bca466

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/connectors/integrate-ims-apps-ibm-mainframe.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Connect to IMS Programs on IBM Mainframes
3-
description: Integrate IMS programs with Standard workflows in Azure Logic Apps by using the IBM IMS connector.
2+
title: Access IMS Programs from Standard Workflows
3+
description: Connect to IMS programs on IBM mainframes from Standard workflows in Azure Logic Apps by using the IBM IMS connector.
44
services: logic-apps
55
ms.suite: integration
66
author: haroldcampos
@@ -58,7 +58,7 @@ This operation also includes advanced parameters, which appear after you select
5858

5959
To create this HIDX file, [download and install the Host Integration Server (HIS) Designer for Azure Logic Apps](https://aka.ms/his-designer-logicapps-download). The only prerequisite is [Microsoft .NET Framework 4.8](https://aka.ms/net-framework-download).
6060

61-
To invoke a mainframe program, your workflow needs to understand the mainframe program's type, parameters, and return values. The IMS connector manages the process and data conversions. The conversions are used to provide input data from the workflow to the mainframe program and to send any output data generated from the mainframe program to the workflow. The connector also provides tabular data definition and code page translation. For this process, Azure Logic Apps requires that you provide this information as metadata.
61+
To invoke a mainframe program, your workflow needs to understand the mainframe program's type, parameters, and return values. The IMS connector manages the process and data conversions. These conversions provide input data from the workflow to the mainframe program and send any output data generated from the mainframe program to the workflow. The connector also provides tabular data definition and code page translation. For this process, Azure Logic Apps requires that you provide this information as metadata.
6262

6363
To create this metadata, use the [HIS Designer for Logic Apps](/host-integration-server/core/application-integration-ladesigner-2). With this tool, you can manually create the methods, parameters, and return values that you can use in your workflow. The tool also allows you to import COBOL or RPG program definitions (copybooks) that provide this information.
6464

@@ -68,7 +68,7 @@ This operation also includes advanced parameters, which appear after you select
6868

6969
The IMS connector doesn't have triggers, so use any trigger to start your workflow, such as the **Recurrence** trigger or **Request** trigger. You can then add the IMS connector actions. To get started, create a blank workflow in your Standard logic app resource.
7070

71-
### Limitations
71+
## Limitations
7272

7373
Currently, the IMS connector requires that you upload your HIDX file directly to your Standard logic app resource, not an integration account.
7474

0 commit comments

Comments
 (0)