Tectia Server for IBM z/OS can transfer files to and from cataloged, online DASD (direct access storage device) data sets. The following data set types are supported:
uncataloged DASD data sets
migrated DASD data sets
offline DASD data sets
cataloged tape data sets
uncataloged tape data sets
offline tape data sets
Tectia relies on the system security product for access control to datasets. Because of this, tape datasets must have identifying tape labels. Tectia will not allow the use of
NL (No Label) or
BLP (Bypass Label Processing). Tectia does not read labels and does not have any label exits.
Using an offline tape data set requires that a tape drive is available and that the tape cassette is mounted on the drive. The operator must mount the drive or cancel the mount request. Outstanding mount requests can cause shortages, locking and deadlocks in resource handling in the system.
Using data sets on offline DASD volumes requires that the operator varies the volume device online. This requires the operator to decide whether the device can be varied online (it is probably offline for a good reason) and to enter the vary command or cancel the request.
Using a migrated data set requires the system to recall the data set to a user-accessible (level 0) volume before it can be read or overwritten. If the data set is on a migration level 1 (DASD) or migration level 2 (tape) volume, it is first copied to level 0.
The z/OS system operators must monitor mount requests to make sure they do not go unanswered or cause problems. They must also monitor the system for Tectia SFT Server processes and Tectia file transfer clients that are hanging on allocation requests for offline data sets.
In Tectia Server for IBM z/OS, mounting an offline data set is by default not allowed and recalling a migrated data set is by default allowed.
The Tectia end user controls mounting and recalling with the extended file attributes
autorecall. The user must set
immed for Tectia to attempt to mount offline data sets. The user can set
no to avoid recalling a data set by mistake.
In addition, the administrator must set up access rights to the RACF facility
SSZ.MOUNT for the users who will be mounting offline data sets with Tectia client tools for z/OS. For more information, see Tectia Server for IBM z/OS Administrator Manual.
Existing data sets that do not have entries in the catalog can be accessed by specifying a volume serial number and unit. For example, to read a tape data set that has the data set name
SRVACC1.SPECS.PDF and is the third data set on volume
sftp> site unit=TAPE,volumes=456123,dataset_sequence_number=3 sftp> sget //'SRVACC1.SPECS.PDF' /home/clusr1/tmp/specs.pdf
To create a data set without cataloging it use the
sftp> site unit=tape,normdisp=keep sftp> sput /home/clusr1/tmp/specs-v2.pdf //'SRVACC1.SPECS.V2.PDF'
mgmtclass attributes are also available.
For Tectia to request the system to mount an offline volume, you must use the
automount=yes attribute. You must also have
READ access to
SSZ.MOUNT. For example, to read a data set on a tape volume, assuming that the data set has a catalog entry, use the following commands:
sftp> site automount=yes sftp> sget //'SRVACC1.SPECS.PDF' /home/clusr1/tmp/specs.pdf
automount=yes, Tectia first attempts to allocate the data set without allowing the system to mount the data set if it is offline. If this allocation fails, Tectia retries the allocation with the mount request. You can make Tectia omit the first attempt by specifying
Tectia has a facility for low-level access to dynamic file allocation because of the large number of attributes that can be specified when allocating tape data sets.
Tectia allocates data sets by calling the SVC 99 interface. This interface has a table of text units. Each text unit consists of key, parameter count, and parameters. The parameters have a length field and data. The interface is documented in the Authorized Assembler Services Guide.
Tectia allocates files at the start of a file transfer (except if the file is already allocated and is represented by a DD name). Tectia sets text units based on the extended attributes. The site parameter
svc99_text_units allows the user to add and change text units in the table. The value of
svc99_text_units is a sequence of text units delimited by underscores ('
_'). Each text unit has the format
xxxx is the key in hexadecimal,
F is a format character and
values is a character string. The
values part is empty or consists of one string or of several strings delimited by plus signs ('
+'). No value may contain spaces, tabs, newlines or any of the characters '
values part must not exceed 80 characters in length.
The format character indicates how the value(s) are encoded. The possible values are:
S: character string
F: decimal number with length 4 in the text unit
H: decimal number with length 2 in the text unit
C: decimal number with length 1 in the text unit
-: no text unit
When the format character is '
-', Tectia removes the text unit with the given key if it is in the table. For the other characters, Tectia replaces the value in the text unit with the given key or adds a new text unit.
The following attributes show how to encode some of the examples in the Authorized Assembler Services Guide. The attributes are not intended to be practical cases.
To specify an accessibility code of Z for an ANSI tape data set:
sftp> site svc99_text_units=8001XE9
To specify a RACF profile that was defined generically and request unallocation when a DCB is closed:
sftp> site svc99_text_units=800EXD9D7D9D6C6+80_001CX
To enter a Key Encode Specification and a Key Label:
sftp> site svc99_text_units=8026SH_8024SLABELQ1.LABELQ2.LABELQ3