Assessments - 0, GPA: 0
(
)
)
|
por este dispositivo também tem outras instruções :
Computadores - HP Integrity NonStop H-Series (16.73 mb)
Computadores - HP Integrity NonStop H-Series (957.56 kb)
Computadores - HP Integrity NonStop H-Series (881.66 kb)
Computadores - HP Integrity NonStop H-Series (965.62 kb)
Computadores - HP Integrity NonStop H-Series (676.93 kb)
Computadores - HP Integrity NonStop H-Series (393.72 kb)
Computadores - HP Integrity NonStop H-Series (776.57 kb)
Facilidade de uso
Chapter 1 - Using a Command Server
Troubleshooting Tools
As data is validated, information about the data is recorded into workspace in
memory or work files that guide the output process. The workspace information
controls the data objects appearing in the data stream, whether they are related
to other data objects, and what (if any) the relationship is. This enables you to
specify any input within a map rule regardless of where the data appears in the
input stream. It also enables you to use rules about the presence of data so that,
for example, you can count objects or test their presence.
Output Objects Built
After all the input data has been validated and the input data is valid, output
objects are generated based on each output card specification, including the map
rules. If the output has an initiator defined, it is built first. Then, each output is
built, one rule at a time, beginning with the first rule of the first output card. The
entire first rule is evaluated, even if it refers to other maps and functions. When
the first output is built, it is a complete data object, identified and treated as any
other input data object is identified and treated. This enables you to refer to
earlier outputs in a map rule.
As outputs are built, syntax objects are inserted—such as a delimiter, initiator,
terminator, or release character—according to the type definition, and whatever
remaining bytes of a fixed-length item are filled with pad characters. The
execution process continues as the rules are evaluated and output data is built
through the completion of the last rule of the last card.
Troubleshooting Tools
When a map begins to run, the first thing that occurs is the validation of the input
data—performed by comparing the data to the type tree definition. After data
validation completes, the map rules are evaluated for the output cards and output
objects are built.
When a map executes, invalid or unknown input data may be encountered and
you may want to analyze what happened during the validation process. You may
also want to analyze the output data if the map did not produce the expected
results.
Many debugging aids are available to assist you through the troubleshooting
process including the following:
♦ A Command Server display of ongoing execution information
♦ Command Server return codes and messages
♦ Map audit log files, including data audit, execution audit, map settings, and
card settings information
C o m m a n d S e r v e r R e f e r e n c e G u i d e
9
... Este manual também é adequado para os modelos :
Computadores - HP NonStop G-Series (138.62 kb)
Computadores - HP NonStop L-Series (138.62 kb)