z/OS Sysopts
Systopts syntax and parameter that you can use on the z/OS operating System.
Syntax
SYSOPTS = “UNIQUE=YES”
“DBCS=(tablename,so,si,PAD|PAD=pc,LOGIC=A|B)”
“CODEPAGE=(from Unicode code set, to code set)”
“DATATYPE=TEXT|BINARY”
“XLATE=NO|YES”
“STRIP.BLANKS=NO|YES”
“PERMISS=nnn”
“SYSOUT=(sysout_keyword1, sysout_keyword2, . .)”
UNIQUE=YES
specifies that the Unique Member Name Allocation Exit (AXUNIQ) will be invoked in order to force the PDS member name to be unique on the z/OS TO node.
DBCS=(tablename,so,si,PAD|PAD=pc, LOGIC=A|B)) is used to invoke the double-byte character set translation facility.
tablename is the name of the requested DBCS translation table. The tablename is required with DBCS. If you only specify tablename, you do not need to enclose the parameters in parentheses. For an updated list of translation tables provided by Sterling Connect:Direct, see Supporting DBCS in IBM Sterling Connect:Direct for z/OS Administration Guide.
so is the SHIFT-OUT character denoting a shift from single-byte character set (SBCS) to double-byte character set (DBCS) mode. The default is the IBM standard x’0E’.
si is the SHIFT-IN character denoting a shift from DBCS to SBCS mode. The default is the IBM standard x’0F’.
Note: NOSO indicates no shift-out or shift-in
character and is denoted by the use of x’00’ for the SO and SI characters.
NOSO is used when the data is not in mixed form and is assumed to
contain all DBCS characters.
|
PAD|PAD=pc
specifies that padding characters are in use. When DBCS data is translated from EBCDIC to ASCII, PAD specifies that the SHIFT-OUT and SHIFT-IN characters will be replaced by a pad character. This allows the displacement of fields within a record to remain unchanged during translation.
When DBCS data is translated from ASCII to EBCDIC, PAD specifies that the input ASCII DBCS file is in a padded format. The character immediately preceding a DBCS character or string will be overlaid by the SHIFT-OUT character. The character immediately following a DBCS character or string will be overlaid with the SHIFT-IN character. This allows the displacement of fields within a record to remain unchanged during translation.
pc is the pad character to be used during EBCDIC to ASCII translation. pc is ignored for ASCII to EBCDIC translations. The default value for pc is x’00’.
LOGIC=A|B
tells Sterling Connect:Direct how to process data when it encounters SO (SHIFT-OUT) and SI (SHIFT-IN) characters. Normal mainframe data processing expects a pairing of SO/SI characters, and generates an error and terminates a Process when these SO/SI characters are not equally matched. You specify the DBCS keyword within the SYSOPTS parameter, the parameters that define the translation table and the SO and SI characters, and whether padding characters are in use. For example, the following two examples of a SYSOPTS parameter mean the same thing and tell Sterling Connect:Direct to use this normal method to process DBCS data (LOGIC=A):
SYSOPTS="DBCS=(EBCXKSC,0E,0F,PAD=00)"or
SYSOPTS="DBCS=(EBCXKSC,0E,0F,PAD=00,LOGIC=A)"The initial state of the data is SBCS. With normal logic translation processing, you are not required to specify the keyword, Logic=A. With normal logic, the mainframe system processes the data as SBCS until it encounters an SO character. After encountering the SO character, the system expects DBCS characters. Sterling Connect:Direct generates an error and terminates the Process if it encounters one of the following conditions:
An SI character before an SO character
A combination of SI and SO characters without data between the SI and SO characters
An alternate processing method exists. When you specify LOGIC=B, special rules apply to the normal DBCS translation. The system tells Sterling Connect:Direct to send the file before generating an error. LOGIC=B tells Sterling Connect:Direct to continue processing and keep the state as SBCS if the system encounters one of the following conditions:
An SI character before a SO character
An invalid combination of SI and SO characters
The system processes the data in the state that was in affect prior to the invalid SI-SO combination and sends the entire file. After sending the file, the system generates an error.
CODEPAGE=(from Unicode set, to code set)
invokes code set conversion utilities supported by the z/OS C/C++ compiler.
from Unicode set is the name of the Unicode set of the encoded data sent to the receiving node. The code set name is required and can be UTF-8 or UCS-2, or their equivalent on other operating systems. For example, 65001 is the UTF-8 equivalent on the Microsoft Windows system.
to code set is the name of the final code set that will be used on the remote node. You can use LOCALE to indicate the default code page set relevant to the receiving node.
DATATYPE = TEXT | BINARY
specifies the type of data in the file. Data can be either text or binary format. Can be a key word. Valid for HFS files only.
XLATE = NO | YES
specifies whether ASCII/EBCDIC character translation occurs. Can be a key word. Valid for HFS files only.
STRIP.BLANKS = NO | YES
specifies whether trailing blanks characters are removed from the text record before writing or transmitting the record. Can be a key word. Valid for HFS files only.
PERMISS = nnn
specifies the HFS file permissions for a file being created. This subparameter is ignored if the file already exists. Can be a key word. Valid for HFS files only.
//ENVIRON DD DISP=SHR,DSN=$CD.ENVIRON(TZ)
The first digit indicates the owner’s file permissions, the second digit indicates the owner’s group’s file permissions, and the third digit indicates the file permissions for all others.
The following table shows permission values:
| Value | Permissions |
|---|---|
| 0 | No file access allowed |
| 1 | Execute access allowed |
| 2 | Write access allowed |
| 3 | Write and Execute access allowed |
| 4 | Read access allowed |
| 5 | Read and Execute access allowed |
| 6 | Read and Write access allowed |
| 7 | Read, Write, and Execute access allowed |
For example, permiss=634 indicates that the file owner has read and write permissions, the owner’s group has write and execute permissions, and all others are allowed only read access. Permiss=751 indicates that the file owner has read, write, and execute access, the owner’s group has read and execute access, and all others have execute access to the file.
SYSOUT=(sysout_keyword1, sysout_keyword2, . .)
specifies various SYSOUT keywords. See the IBM Sterling Connect:Direct for z/OS Facilities Guide for a list and description of the SYSOUT keywords.