IBM Support

Gentran Server for iSeries, Inbound Processing Functionality (PRCTRNIN)

Technical Blog Post


Abstract

Gentran Server for iSeries, Inbound Processing Functionality (PRCTRNIN)

Body

Processing Inbound-PRCTRNIN command is a CL that consists of a few different programs, depending on how the parameters are entered.
  1. When you put in a Communication Profile (COMPRF) on the PRCTRNIN:
    1.  The program looks at the data in the inbound queue for that specified communication profile, that has a RN status and processes it through the Editor (which resolves to the partner (using ISA05/06 and GS02 Sender Id)  against the Partner ID and/or Cross references.
    2. The program also compliance checks the data against the standards, writes data to the audit file, sends back out Functional Acknowledgements, AND it also splits (data separation) the data.
    3. Splitting (data separation) is based on Receiver ID (or your company), for example:  ALL 850 data might go to split file 1, while ALL 810 data will go to split file 2. 
    4. To view the designated split file setup, select option 15-Data Separation on your Receiver ID Partner (ISA07/08 and GS03 values on the inbound data will be cross referenced to this partner).   If you don’t have a Receiver ID partner, setup a partner for your own company, no groups/trans need to be setup, it’s just a shell.  Cross reference ISA07/08 and GS03 values from incoming data, and setup data separation

2.  If you put an Application Id (APPID) on the PRCTRNIN also:

  1. The application id has a split file assigned to it (5-view on each application id to see applicable split file), processing will go to that split file and read the data and pass it through the mapper and write to your application files.   If you don’t have data separation/splitting setup, then the split file parameter on Application id will be blank (which means data is being put in the Slide file, like a bucket of data for all those exceptions).

3.   PRCTRNIN with COMM PROFILE and APPLICATION ID parameters listed will process data with from the inbound queue with a RN status to a UNIQUE member in the split files  and then the application id (which has a split file assigned to it) looks at the unique member in split file and maps the data through the map and writes to the application files.  If an application isn’t run against some of the data (ie: 850 application run, but 810 data received also), then that data is rolled up to the *FIRST MEMBER of the split file. 

4. PRCTRNIN with COMM PROFILE only, moves the data from the communication profile inbound queue that has a RN status to the split files *FIRST member.

5. PRCTRNIN with APPLICATION ID only looks at *FIRST MEMBER of the split file and moves data through mapper to application files.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS6UY8","label":"Sterling Gentran:Server for iSeries"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

UID

ibm11123083