HP Integrity NonStop H-Series Guide de l'utilisateur Page 183

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 346
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 182
HP NonStop Shadowbase Command Definitions
Consumer Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
174
has generally been replaced by the use of the RESOLVETRANS
parameter. Extended Consumers should not be used unless
directed by HP Shadowbase Support.
Specifies whether Consumer is a basic or an extended type. BASIC
Consumers are the main Consumer processes for which DBS
Specifications are added (see Section 0 - Database Specification
Command Descriptions for more information). EXTENDED Consumers
are those that are attached, via the BASICCONSNAME parameter, to a
previously defined and added basic Consumer. They are responsible for
the same files/tables as the basic Consumer to which they relate. The
basic and related extended Consumers can be seen as a common
process, although they are multiple processes. They can be used to get
past an OS imposed limitation of 100 or 1000 simultaneous transactions
per process (see the TMFTRANS parameter for more details as this mode
generally makes the BASIC/EXTENDED Consumer mode obsolete).
Unless there is a requirement that the target data be written to the
files/tables in the precise order that the application (source) files/tables
were written to, the recommended CONTROLTYPE for an extended
environment is PARALLEL. If CONTROLTYPE is set to SERIAL, data will
be written into individual files/tables in the original sequence. The default
is BASIC.
Note: If you have multiple files/tables (fileset) being updated within one
transaction by an application(s), this fileset should all be attached to
the same Consumer. You can configure basic and related
extended Consumers to process this fileset. The CONTROLTYPE
is set to SERIAL to ensure that modifications to the target database
are processed in the same order as they were in the source
database. This may be important for some applications that use
the target database especially those that are time oriented.
USEREXITCOLCHECK { ON }
{ OFF }
Initial Changed
Version Version Values Default Minimum Maximum Alter
3.980C ON OFF ON No
Client Server Extended Open Target
The Consumer process requires column names for “get’s” and “put’s” to
be in upper case with “_” (underscore) characters instead of “-“ (hyphen)
characters. By default, the API functions will up-shift all lower case
characters and replace all hyphen characters with underscores
characters. This requires a scan of the column name. If your user exit
code uses all upper case column names with underscore characters, you
Vue de la page 182
1 2 ... 178 179 180 181 182 183 184 185 186 187 188 ... 345 346

Commentaires sur ces manuels

Pas de commentaire