Callable CICS Linkage - Finalist - 10.0

Finalist Guide

Product type
Software
Portfolio
Verify
Product family
Data Quality - Postals
Product
Finalist
Version
10.0
Language
English
Product name
Finalist
Title
Finalist Guide
Copyright
2023
First publish date
1984
Last updated
2024-05-15
Published on
2024-05-15T00:57:22.811031

This illustration shows how the callable Finalist CICS linkage works.

Figure 1. Callable Linkage
  1. Your program COMMAREA contains user data with additional data added to the end for use by Finalist CICS.
  2. XCTL 1 passes the full COMMAREA to LPWN511C.
  3. LPWN511C formats a Windows COMMAREA to pass to Windows (LPCF). The rest of the COMMAREA is saved in a temporary storage queue. The TS Queue is named LPCFxxxx where "xxxx"=EIBTRMID. LPWN511C saves the transaction code and changes it to LPCF. The Windows COMMAREA is passed to Windows in XCTL 2.
  4. Finalist CICS (LPCF in the previous figure) runs as usual until you press Clear ending CICS processing. Prompted by a flag passed by LPWN511C, CICS XCTLs to LPWN512C instead of returning to CICS. The CICS COMMAREA is passed in the XCTL.
  5. LPWN512C performs the following:
    • Reads and deletes the temporary storage queue
    • Merges the CICS CALLAREA into your COMMAREA
    • Restores your transaction code
    • XCTL's to a program named by you
      • This program can be the same one that passed control to CICS or a different program. This is a user decision. The user program (Program B in the previous figure) is responsible for knowing control is coming from CICS.
      • If the field PASSPGM in the Pass Control Block is not filled in by your application prior to calling LPW511C, abend LP71 occurs when Finalist CICS ends and attempts the XCTL.