z/OS Implementation

Batch Processing

The edicc.ini file contains system information for the runtime system.
  • The exitlib value should be set to EDISVU

    exitlib=EDISVU

  • The ismvs value should be set to yes if IBM/TX is running in z/OS batch mode

    ismvs=yes

CICS Processing

The edicc.ini file contains system information for the runtime system. Although the settings in edicc.ini file are not used during the CICS processing, the file is used as input card 8 for compliance checking.

With CICS processing, the EDISVU exitlib is defined with the CICS CSD definitions. The recommended CICS CSD definitions are as follows:
  • DEFINE PROGRAM (EDISVU)
  • GROUP (DTXCICS)
  • DESCRIPTION (Packs Compliance)
  • LANGUAGE (LE)
  • CONCURRENCY (THREADSAFE)
  • DATA (ANY)
Note: Refer to the following topics for more information related to the CICS CSD definitions:
Additional changes may be needed depending on the pack version used. Verify the compliance check maps: ccedf, ccx12, etc to confirm the COMPLIANCE map function is being used.
  • main map : Output Card 1
    ExitDLLVersion DLLValidate Element:Runtime:SetupFramework
  • map rule:
    = VALID (COMPLIANCE ("X12", "GetHCIPVersion","n/a",ExitDLL DLLValidate Element:Runtime:SetupFramework), "FAILED - GetHCIPVersion call: " + LASTERRORCODE() + "/" + LASTERRORMSG () + "<NL>Check the edicc.ini file to make sure that it correctly specifies the edisvu shared library")

  • RunDLLSegCheck function map:

    = RunDLLCompliance(
			Transaction, 
			Structure_Detail_File, 
			Runtime)
The Supply Chain EDI components for compliance using X12, RAIL, and EDIFACT contain XML configuration files that are processed using input card 3. The default setting on input card 3 is set to schema validation and there are two options for handling the schema validation:
  • Modify the schema name in the metadata location on input card 3 to contain //DD:name, for example //DD:X12CFG which corresponds to the data set name in the execution JCL. The XML schema should be uploaded as binary to the dataset containing the maps
  • Modify the schema validation setting to Well Formed

The Supply Chain EDI component for compliance X12U contains a JSON configuration file that is processed using input card 3. Input card 3 is using a JSON template for processing. The JSON template is not required for processing on z/OS.

Each Supply Chain EDI component contains an XML or JSON configuration file to control output to files. Output cards 2 and 3 are defined as SINK with ONSUCCESS APPEND. Output cards 2 and 3 will require an output data set to be defined and an execution parameter override for -OF2 and -OF3 to be identified in the execution JCL.

File Output:

The default setting is file output and the map putmvs* in each component main execution map source file will be used to direct output for z/OS processing. With CICS execution, review the z/OS CICS execution commands.

Pre-defined data set names will be used as follows:
Card number Card name Description

Output Card 5

DD:DATAIN

Contains valid data results.

Output Card 6

 DD:REJECT

Contains rejected data results.

Output Card 7

DD:REJLOG

Contains validation error messages.

Output Card 8

DD:ACKIN

Contains 997 or 999 EDI found in the inbound EDI messages.

Output Card 9

DD:ACKOUT

Contains 997 or 999 outbound EDI messages.

Output Card 10

DD:TA1IN

Contains TA1 found in the inbound EDI message.

Output Card 11

DD:TA1OUT

Contains the TA1 outbound EDI message.

Output Card 12

DD:EDILOG

Fatal Error with framework.

Output Card 13

DD:JSONOUT

DD:JSONREJ

Optional JSON log report.x

Card Output:

Card output can be identified to override each output card which is defined as SINK.

<RuntimeInfo>
	<!-- This section will send output to map output cards -->
		<CardOutput/>

The z/OS JCL for a map execution provides output card overrides via the -OFx parameter. Any SINK output card may use the execution parameter override in the JCL.