Defmes types, objects, and exceptions used for the administration of the File Transfer Service (FrS).
Access to this package is restricted to callers carrying a privileged ID. See your System Administrator for access.
Summary
This package defines service and entity objects and their parameters and status records.
Remote system objects, parameters, and remote user identifications are also defmed.
These definitions are used by the FTS_Admin package. A status record (transfer_info_
t) from the FTS _Transfer package is used to declare an array of status records for the FTS Admin. Get transfer info - - - call.
Terms in italics are defined in the ISO File Transfer, Access, and Management protocol, ISO 8571 FTAM.
Exceptions
state invalid
The service is in an improper state for a requested operation.
entity not idle
- An entity to be aborted is not idle.
already attached
- The ISO transport service is already attached.
no ts attached
- - The ISO transport service is not yet attached.
unknown entity
- An entity is not registered within the service.
unknown account
An account name is unknown within the service.
no entity attached
- No
local entity has been attached to the service.string too long
- A text parameter exceeded an implementation-defmed constraint (see s ubt ype identifier_t).
Declarations
type service_obj_t is limited private;
type entity_obj_t is limited private:
I
entity_AD_ttype default syntax t is
binary, -
-text) ;
Default syntax for data transfer.
Enumeration Literals:
binary text
Binary data is a sequence of uninterpreted octets.
Text data is a sequence of characters, with special handling of fonnat ef-fectors such as < CR>.
subtype line_t is System_Defs.text{252};
Used for directory pathnames.
FTS _ Contig_ Defs-2
(
~
\
subtype short_line_t is System_Defs.text(124);
Used for transport addresses, session and presentation selectors.
subtype identifier_t is System_Defs.text(28);
Used for titles, remote and local entities, and remote user's names and locations.
I
service J>arams _ ttype service-params_t is
for
record
max initiator connections:
max-direct connections:
max-responder connections:
timed requests offset:
low cost time:-checkpoint strategy:
bulk data size:
buffer size:
copy lImit:
publIc directory:
FTS directory:
requeue after boot:
timed queuing-enabled:
securIty attrIbute group:
private attribute group:
file access service class:
enhanced file mgt service class:
unconstrained-service class:
restart functIonal unIt:
recovery functional unit:
reject_unknown_users:
reject anonymous users:
reject-unauthorized users:
timeout deadline:
-finished requests deadline:
suspended deadline:
default syntax:
end record;
service-params_t use record
max initiator connections at 0 max-direct connections at 4 max=responder_connections at 8 timed_requests_offset at 12
low cost time at 16
public_directory at 36
FTS_directory at 292
requeue after boot at 548 timed_queuing=enabled at 549 security_attribute_group at 550
System. ordinal;
FTS _ Config_ Defs-3
private attribute group file access service class enhanced file mgt service class unconstrained-service class restart functIonal unit recovery functional unit reject unknown users reject-anonymous users reject-unauthorized users timeout deadline
-finished requests deadline suspended deadline
default syntax end record;
Defmes parameters for an FrS service. Some parameters may be compared against the im-plemented functionality.
Fields:
max initiator connections
-Maximum number of simultaneously running initiator processes
(including batched and non-batched processing), The batch daemon will not be started if the number ofbatched connections is zero.
max direct connections
- Maximum number of connections which can be established directly, with-out the batcher.
max responder connections
- -Maximum number of simultaneously running responder processes. If zero, the responder daemon will not be started.
timed requests offset
- Number of minutes by which the start time of a timed request must exceed the current time.
low cost time
- Hour of the day at which transfer costs are low.
checkpoint strategy
- selects the checkpoint strategy:
o
1 2 3
No checkpointing.
Checkpoints between data elements.
Checkpoints between data units.
Checkpoint insertion detennined by bulk data
size, below. -
-bulk data size
-
-buffer size copy_limit
Minimum number of bytes before inserting a checkpoint. Only used if checkpoint_strategy is 3.
Size of the protocol data unit (PDU) receive buffer, in bytes.
Maximum size of copied data elements, in bytes. Data elements which are smaller than copy _1 imi t are passed by value (copied) during encoding;
other (larger) elements are passed by reference.
public directory
- The directory, if any, for anonymous or unauthorized users.
FTS _ Config_ Defs-4
I
\~
FTS directory
- Root directory for the FrS directories.
requeue_after_boot
If true, connections interrupted by local system crash or reset should be requeued.
timed queuing enabled
- If true, timed batch transfer requests may be queued. If false, timed batch transfer requests are rejected.
security attribute group
- If true:the security attribute group should be supported.
private attribute group
- If true, the private attribute group should be supported.
file access service class
If true, the file access service class should be supported enhanced file mgt service class
- If true, the enhanced file management service class should be supported.
unconstrained service class
If true, the unconstrained service class should be supported.
restart functional unit
If true:the restart functional unit should be supported.
recovery functional unit
- If true, the recovery functional unit should be supported reject unknown users
- if
true, unknown users are not allowed access. If false, unknown users are treated like anonymous users.reject anonymous users
- If true, anon users are not allowed access. An accounting object must be defined for anonymous users; see FTS_Admin. Define_account.
reject unauthorized users
- If true, remote users who do not provide a filestore password are rejected.
If false, they are treated as unknown users.
timeout deadline
Default deadline, in seconds, after which timeout will be raised when the remote systems keeps quiet.
finished requests deadline
- Deadline, in minutes, when information about fInished requests (requests which have been completed or rejected) should be removed.
Information about transfer requests will also be removed if FTS Trans-fer. Transfer info is called after transfer completion.
-suspended deadline
- Deadline, in minutes, after which suspended requests (not timed
suspended) should be resumed. This parameter affects suspended transfers which may have been forgotten.
default syntax
- Default syntax to be used for data transfer, either binary or text.