UNIX Sysopts Syntax

Systopts syntax and parameter that you can use on a UNIX operating System.

sysopts=":datatype=text | binary:"

":xlate=no | yes:"

":xlate.tbl=<pathname/filename>:"

":strip.blanks=yes | no:"

":permiss=nnn:"

":pipe=yes | no:"

":codepage=(source codepage, destination codepage):"

" :=yes | no:"

specifies system-specific parameters on the copy statement. The subparameters are specified in the same format as fields within a Sterling Connect:Direct UNIX configuration file. They are a series of field names and values (fldn=valn), each of which is delimited by a colon. Enclose the string of subparameters in double quotes; for example:

":fld1=val1:fld2=val2:...:fldn=valn:"

datatype

specifies the type of data contained within the file: text, binary, or vb.

text indicates it is a text file. The default is text. The following shows the default source file attributes assigned for UNIX text files, which are to be used if necessary by the remote Sterling Connect:Direct node:

  • dsorg=ps
  • recfm=vb
  • lrecl=23036
  • blksize=23040

binary indicates the file contains binary data. The following shows the default source file attributes assigned for UNIX binary files, which are to be used if necessary by the remote Sterling Connect:Direct node:

  • dsorg=ps
  • recfm=u
  • lrecl=0
  • blksize=23040

vb indicates the file is in variable block format. Variable block format is structured as follows:

BDW | RDW | Data . . . | BDW | RDW | Data . . .

  • BDW=block descriptor word containing 2 bytes for the length of the block (including 4 bytes of the BDW) and 2 bytes of zeros
  • RDW=record descriptor word containing 2 bytes for the length of the block (including 4 bytes of the RDW) and 2 bytes of zeros
  • Data=record of user data equal in length to the RDW minus the 4 bytes of the RDW (for example, an RDW of 76 bytes is followed by a record of 72 bytes)
Note: The vb feature does not support ASCII/EBCDIC translation. If you specify ":datatype=vb:", specify ":xlate=no:". The copy will fail if you specify ":xlate=yes:".

xlate = no | yes

indicates whether character translation should be performed using the default or user-supplied translation table. Typically, this translation is between ASCII and EBCDIC.

no specifies the translation is not performed. no is the default for binary files.

yes specifies the translation is performed. yes is the default for text files.

xlate.tbl =<pathname/filename>

specifies that a translation table is to be used that is different from the default table used by the Sterling Connect:Direct software.

strip.blanks

determines whether trailing blank characters are removed from a line of text before it is written to the UNIX text file.

yes specifies to remove trailing blank characters. This is the default.

no specifies trailing blank characters are not removed.

permiss=nnn

specifies the UNIX file permissions for a file being created by the copy operation. The permiss subparameter is ignored if it is specified for a file that already exists.

nnn is a 3-digit octal number that defines privileges for users. Each type of user (owner, group, and others, respectively) can be assigned read, write, and execute privileges.

The following table shows valid octal numbers and associated permissions for each n based on the binary numbering system:

Octal Binary Permissions
0 000 No permissions
1 001 Execute permission
2 010 Write permission
3 011 Write and execute permissions
4 100 Read permissions
5 101 Read and execute permissions
6 110 Read and write permissions
7 111 Read, write, and execute permissions
 

For example, permiss=634 indicates that the owner has read and write permissions, the group has write and execute permissions, and others have read permissions.

pipe = yes | no

specifies whether the pipe I/O function is activated. The pipe I/O function allows commands, programs, or shell scripts including any options and arguments to be copied to the destination file or from the source file

yes specifies the pipe I/O function is activated.

no specifies the pipe I/O function is not activated.

Note: Checkpoint/restart is not supported for the pipe I/O function.

codepage=(source codepage, destination codepage)=yes | no

Specifies whether Sterling Connect:Direct will automatically decompress a file that was precompressed with the cdsacomp utility. See the IBM Sterling Connect:Direct for UNIX User's Guide for more information on the cdsacomp utility.

Yes indicates that the from data set is precompressed and tells Sterling Connect:Direct to decompress the file as part of the Process.

No tells Sterling Connect:Direct that the from file is not precompressed, or to send the precompressed file in compressed format. Precompressed files copied with this value can be decompressed offline on another Sterling Connect:Direct for UNIX or Sterling Connect:Direct for z/OS system using the cdsacomp utility.

If sysopts are not coded or if sysopts=":=no:", a precompressed file is sent in compressed format and the receiver must run cdsacomp with "-mode decompress". If the from file is not precompressed, regular or extended compression may be used in the Copy step. Do not use regular or extended compression in the Copy step if the from file is precompressed.