Settings for Connect:Direct Server CopyFrom Service

There are many copy options available when you use the Connect:Direct Server CopyFrom Service.

When you configure the Connect:Direct Server CopyFrom service, you must specify settings for the following fields in the Graphical Process Modeler. These fields are listed in alphabetical order.

Field Description Supported Remote Sterling Connect:Direct® Platforms
BinaryMode Specifies the mode for Sterling Connect:Direct File transfer. Optional. Valid values are:
  • Yes—simple binary mode
  • No—(default) - text mode
  • VB—a variable block binary transfer with Sterling Connect:Direct on z/OS
 Yes—All platforms

No—All platforms

VB—z/OS platform
CheckpointInterval Specifies the byte interval for checkpoint support, which allows restart of interrupted transmissions at the last valid checkpoint point and therefore reduces the time to retransmit the file. Optional. For more information, see How Checkpoint Restart and Retry Processing Works .

Valid value is number of bytes, in one of the following formats:

  • nnnnnnnnnn
  • nK or nM
  • nm or nk
 All platforms
Compression Specifies that the data is to be compressed, which reduces the amount of data transmitted as the file is copied from one node to another. The file will be automatically decompressed at the destination. Optional. Valid values are 1-9. Increasing the value indicates a greater attempt at compression and will consume more CPU. Values greater than 2 may not result in further compression. All platforms
Config Name of the service configuration. Required. All platforms
DCB Specifies Data Control Block (DCB), a group of attributes specified as name-value pairs separated by commas. Used only on the z/OS platform. Optional. Valid attributes are:
  • recordlength
  • blocksize
  • recordformat
  • datasetorganization
    Note: More DCB attributes are available but only these are supported in Application. Any other attribute will cause the copy to fail.
 z/OS platform
LocalDocumentName Name of the document in Application to which the remote file should be copied. Optional. All platforms
LocalFromCodePage Specifies a code page supported by Java VM. Used in conjunction with the value of the LocalToCodePage parameter. The Connect:Direct Server Adapter will apply a code page conversion to a document before transferring it to a remote Sterling Connect:Direct Server. This parameter is only valid with the following conditions:
  • Code page specified is supported by the local Java VM
  • Parameter LocalToCodePage is defined
  • Text mode file transfer (BinaryMode =No)

Optional. Valid value is the name of a codepage supported by the local Java VM.

For example:

<assign to="LocalFromCodePage">Cp1251</assign>

<assign to="LocalToCodePage">Cp1047</assign>

This example will translate the local file from windows latin-1 to ibm ebcdic. See http://java.sun.com for a complete list of supported encodings.

All platforms
LocalStripBlanks Specifies whether the Connect:Direct Server Adapter will strip blanks from the end of records in a received remote file before creating a new document. This option is only valid for Text mode file transfers (BinaryMode = No). Optional.

Valid value is Yes or No (default).

 All platforms
LocalToCodePage Specifies a code page supported by Java VM. Used in conjunction with the value of the LocalFromCodePage parameter. The Connect:Direct Server Adapter will apply a code page conversion to a document before transferring it to a remote Sterling Connect:Direct Server. This parameter is only valid with the following conditions:
  • Code page specified is supported by the local Java VM
  • Parameter LocalFromCodePage is defined
  • Text mode file transfer (BinaryMode =No)

Optional. Valid value is the name of a codepage supported by the local Java VM.

For example:

<assign to="LocalFromCodePage">Cp1251</assign>

<assign to="LocalToCodePage">Cp1047</assign>

This example will translate the local file from windows latin-1 to ibm ebcdic. See http://java.sun.com for a complete list of supported encodings.

All platforms
LocalXlate Used to indicate which translation table the service should use during transmission. It may be specified using the Graphical Process Modeler or by editing the XML source of the business process.. Optional.

Valid value is Yes (default) or No.

For example:

<assign to="LocalXlate">Yes

<assign to="LocalXlateTable">ascii-to-ebcdic-table</assign>

All platforms
RemoteFileName Name of the file that should be copied from the remote Sterling Connect:Direct server. Enter the legal characters in the file name. Required. All platforms
SessionToken Identifies an established session between two Sterling Connect:Direct nodes. Required. Session integrity cannot be guaranteed if the session token is omitted. For examples of session token usage, refer to Sample Business Processes on the Sterling B2B Integrator Side . All platforms
Sysopts Remote system operations to be implemented on the remote Sterling Connect:Direct node. Optional.

For example (for copying from Sterling Connect:Direct for Microsoft Windows only):

Datatype(text) xlate(yes)

 All platforms

Format of Sysopts varies by platform.