*4 data. As of
*4 therefore be introduced with which the default value of the CCS
*4 name of a file is determined.
*4 Note:
*4
*4 character set since all programs in BS2000 assume that the
*4 data is provided with a
*4 Previous behavior:
*4 Up to
*4 default *NONE for the CCS name of the file
*4 a different character set is used, the file attribute CCS name
*4 must be specified explicitly.
*4 Changed behavior:
*4 The two commands
*4 been extended by the parameter
*4 default character set for the ID concerned.
*4 If it is not EDF03IRV, when a new file is now created the CCS
*4 name of the user entry of the destination pubset is taken over
*4 as the CCS name of the file. As previously, the file does not
*4 receive an entry for the CCS name
*4 is in the user entry. The file attribute CCS name is included in
*4 the transfer when copying, saving and restoring files. The
*4 behavior of LMS has also been changed analogously when new
*4 elements are added. If a CCS name is not explicitly specified,
*4 they are assigned the CCS name of the library.
*4 There is therefore no change if the default system character set
*4 is used. If an 8 bit character set is selected, the code is
*4 clearly specified on the file and library element level via the
*4 CCS name. However, explicit specification of the character set
*4 always has priority.
*4 You will find further information on converting from 7 bit to 8 *4 bit character sets in the white paper under
*4
2.16.3 New ASTI Subsystem
*4 ASTI (Assistant for Service Task Integration) is implemented as
*4 a subsystem and provides support for the system developer when
*4 developing client / server applications. ASTI takes over the
*4 communication between client and server by forwarding the orders
*4 placed by the client to the server, receiving the feedback
*4 messages and managing both in internal ASTI wait queues. A
*4 server application must be started via ASTI to allow it to be
*4 managed by ASTI. It is also possible to specify for client
*4 orders whether recovery measures are to be initiated for the
*4 orders concerned if the server terminates prematurely.
*4 The ASTI functions are made available to the developer via a
*4 macro interface.
*4 ASTI is part of the BS2000/OSD basic configuration and is
*4 initially only released for internal use by BS2000 products.
*4 The first user of ASTI is the product interNet Services V3.2.
*4 The ASTI subsystem is started automatically when the system is
*4 booted.
*4 You will find a detailed description of ASTI in the file
*4 SYSRME.ASTI.010.E.
Page 21
