Convert zSeries Trading Partner Data

You can convert trading partner data to import into Sterling B2B Integrator.

1. Navigate to the /install_dir/tp_import directory.
2. Edit the customized_mf_convert.sh script as needed to specify the trading partner or partners for which you want to convert data. Recommended strategy is to copy customized_mf_convert.sh to another file and customize the copy.

   To customize the script, edit the following parameters as needed to define how you want to convert your data:

   Note: Filename paths can be absolute or relative. You can specify these command line options in any order, except the -tp and -qualtp commands, which must be specified together in that order.

   Parameter	Description	Example
   -vers version	Valid zSeries version 6.0 or higher. Required.	-vers 6.0
   -part filename.par	Full path or filename of the trading partner file. It must have the .par extension. Required. Note: Supported records are: CONTROL, GP, and TC, except GP!!!DFT and TC!!!DFT.	-part partner.par
   -inbn filename.icn	Full path or filename of the inbound control number file. It must have the .icn extension. Enables the script to convert all the .icn files in this directory into an .xml file. Required.	-inbn partner.icn
   -outbn filename.ocn	Full path or filename of the outbound control number file. It must have the .ocn extension. Enables the script to convert all the .ocn files in this directory into an .xml file. Required.	-outbn partner.ocn
   -crf filename.crf	Full path or filename of the cross reference (XREF) file. It must have the .crf extension. The PartnerIDs in this file will be used as the SenderID for the inbound envelope definitions for the alias partner-ID being processed. Required.	-crf partner.crf
   -sEDI sysEDIcode	Your Sterling Gentran:Basic for zSeries system EDI code. This code will be used as the ReceiverID for the inbound envelope definitions. Required.	-sEDI yourEDIcode
   -qualEDI qual	Your Sterling Gentran:Basic for zSeries system EDI code qualifier. Optional.	-qualEDI 99 where 99 is the partner qualifier
   -xmlout filename.xml	Full path or filename of the .xml output file being created. It must have the .xml extension. This file contains the output of all the converted trading partner records. Optional. Consider specifying a meaningful name for the .xml file. The default name is final.xml.	-xmlout partner.xml
   -rpt filename.rpt	Full path or filename of the report file created by the utility. This report contains information about the conversion. Review this report using a text editor to determine if any errors or warnings occurred during the conversion. Optional. Consider specifying a meaningful name for the report file. The default name is mfconversion.rpt.	-rpt partner.rpt
   -tp tpCode	Trading partner code to convert. You can specify one or more. Optional. Must include -qualtp option if used. If you do not specify the trading partner code, Sterling B2B Integrator converts all trading partner codes.	-tp VENDOR-1 VENDOR-2 …
   -qualtp qual	Trading partner code qualifier used to generate envelope definitions. You can specify one or more. Optional. Must be used if using -tp option.	-qualtp 99 where 99 is the trading partner code qualifier.
   -send_recv send/recv	Send/Receive flag. Indicates whether the conversion utility will consider the Send or Receive flag when building envelopes. Optional. Options include: s – Create envelopes only for outbound partner records that have Send flag=Yes. r – Create envelopes only for inbound partner records that have Receive flag=Yes. b – Use both flags. Create envelopes for all records that have either the Send or Receive flag set to Yes or that have both the Send and Receive flags set to Yes. i – Ignore flag status; generate all inbound and outbound envelopes. i is the default value.	-send_recv s
   -rel_part rel/part	Relationship indicator: r – Partner file is for a relationship mode partner. p – Partner file is for a partner/qualifier mode partner. p is the default value. Optional.	-rel_part r
   -env_name envelope	Envelope naming conventions. Use one of the following four values to indicate the order in which you want the naming information to be included in the envelope name: pstei psite pstie pseit Where: p – partner ID and qualifier s – sender ID and qualifier i – inbound or outbound e – envelope indicator (interchange/group/transaction) t – transaction, functional group or interchange (value of 1) Consider your naming conventions. If you already have trading partner data in Sterling B2B Integrator, you may not want to save new envelopes with the same names. Optional. If you do not specify a naming convention, the default is partner ID_qualifier_envelope description_sender ID_qualifier_envelope information_inbound or outbound.	-env_name pstie For examples of converted envelope names using the different naming conventions, see Example Converted Envelope Names on page 24.
   -inb_bp inbound bp	Business process model to be used on inbound envelopes included in this conversion.	-inb_bp EDIFACTDeenvelope
   -inb_ebp inbound error bp	Business process model you want to invoke for inbound envelopes included in this conversion, in case of errors.	-inb_ebp alert
   -outb_bp outbound bp	Business process model to be used on outbound envelopes included in this conversion.	-outb_bp OverdueAckCheck

3. Convert the data. Depending on your conversion type, use the appropriate command.
   • For UNIX, enter: install_dir/tp_import/customized_mf_convert.sh
   • For Windows, enter: \install_dir\tp_import\customized_mf_convert.cmd
   install_dir is the directory on the host computer where Sterling B2B Integrator is installed.
4. Verify that each value in the XML data is correct.