Waring MBB520 Datasheet Page 69

  • Download
  • Add to my manuals
  • Print
  • Page
    / 89
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 68
Release Notes - New Features included in Release 2.4.0
Page 69 of 89
and will insert one or more records into the background queue. Each time it runs, details will be
written to the MAA100 table (BAMQ enquiry) indicating the run-time parameter, and any errors
that may be detected by ith2remote. These errors will relate to the format of the parameter; the
format or contents of the specific parameter or input file. In addition ith2remote will abort if it finds
an error.
No specific transaction validation is performed by ith2remote; this is performed by the background
process. Errors and progress of the records inserted may be reviewed using the existing functions of
the QUEU transaction, or the functions written within the transaction (e.g. TIEQ for TIGI
transactions).
The field [yyyyyyy] is optional and indicates the user name under which the background entry is to
be inserted. This will then allow that user to see details of any error messages written to the
Background queue. If this field is not supplied, a unique name will be generated and used.
The field nn controls the processing of ith2remote.
If nn = 00, xxxxxxxxxxxx… will be inserted into the background queue, space filling the record if a
partial record is supplied.
If nn is in the range 01 – 20, a default file will be opened. This will be held in PKEEP, and will
have a file name of yyyynn.defaults. yyyy is the transaction code (the first 4 characters of xxxx).
This file will be used to supply field defaults for any character not specified on the command line.
E.g. TIGI requires a ‘U’ to be input into the ‘RUNMODE’ field. This ‘U’ can be specified in the
default file with a line RUNMODE=U, it then only being necessary to supply an xxx.. value of
TIGIinterface name.
Values 21 – 98 are reserved for future enhancement.
Value 99 is used to indicate that xxxxxxxx is the name of a file visible to the TROPOS server. Each
record from this file will be read and inserted into the background queue. This file will have the
same layout as the input file to ithsequ and so can be used as an alternative to ithsequ (so
performing the transactions in the background queue rather than online). Each record on this file
needs to be according to the screen library unit (e.g. the SIAD library unit is L127L.T) and not
according to the visible screen as shown by the clients (as it may have been changed by the screen
designer, or contain invisible fields).
Examples
ith2remote 00IADDFRED
This will insert the data IADDFRED into the background queue with a unique username (which
will be ith2remote HH:MM)
ith2remote [Fred Bloggs]01IADDFRED
This will read the file $PKEEP/IADD01.defaults and add the default values within that file to the
supplied data ‘IADDFRED’ which will then be inserted into the background queue with a username
of ‘Fred Bloggs’.
ith2remote [Fred Bloggs]99$PWORK/mydata
This will open the file ‘$PWORK/mydata’ and insert each record into the background queue with a
username of ‘Fred Bloggs’.
Page view 68
1 2 ... 64 65 66 67 68 69 70 71 72 73 74 ... 88 89

Comments to this Manuals

No comments