Siemens SM2 monitoring system Manuale Utente
U3585-J-Z125-8-76
197
SM2 operation
SM2 output file
1)
It is advisable to select a file name that indicates the date and time of file creation, so
as to facilitate file sequencing in the input order required by SM2U1.
as to facilitate file sequencing in the input order required by SM2U1.
2)
Only block lengths of 16 are used. If no block length is specified, this is set to 16 by SM2.
If BUFFER-LENGTH is specified without the SPACE operand, SM2 uses the default
value 512 for the primary storage allocation and for the secondary storage allocation.
If BUFFER-LENGTH is specified without the SPACE operand, SM2 uses the default
value 512 for the primary storage allocation and for the secondary storage allocation.
3)
ACCESS-METHOD=*UPAM,SHARED-UPDATE=*YES should be selected if the SM2
monitored data is to be analyzed using SM2R1-PC or SM2ONLINE-PC (V1.0 only).
This means that BUFFER-OUTPUT = *IMMEDIATE must be selected in the OPEN-
LOG-FILE statement.
monitored data is to be analyzed using SM2R1-PC or SM2ONLINE-PC (V1.0 only).
This means that BUFFER-OUTPUT = *IMMEDIATE must be selected in the OPEN-
LOG-FILE statement.
If the SM2 output file is created on a private volume (additional operands in the CREATE-
FILE command VOLUME=..,DEVICE-TYPE=...), the private disk must be defined as
"SYSTEM" with /SET-DISK-PARAMETER .. USER-ALLOCATION=*SHARE.
FILE command VOLUME=..,DEVICE-TYPE=...), the private disk must be defined as
"SYSTEM" with /SET-DISK-PARAMETER .. USER-ALLOCATION=*SHARE.
Note
The high block length may result in mismatches, which in turn cause the file to become
very large, particularly if BUFFER-OUTPUT=*IMMEDIATE was selected in the OPEN-
LOG-FILE statement. However, this setting allows you to minimize the number of
“MISSED RECORDS”. The majority of mismatches can be eliminated by executing an
SM2U1 run, which means the advantages of this setting far outweigh the disadvan-
tages.
very large, particularly if BUFFER-OUTPUT=*IMMEDIATE was selected in the OPEN-
LOG-FILE statement. However, this setting allows you to minimize the number of
“MISSED RECORDS”. The majority of mismatches can be eliminated by executing an
SM2U1 run, which means the advantages of this setting far outweigh the disadvan-
tages.
“MISSED RECORDS” are records that could not be written to the SM2 output file due
to an input/output bottleneck and were therefore lost. They are indicated in the STATUS
TABLE screen and by SM2R1 in EVALUATION STATISTICS.
to an input/output bottleneck and were therefore lost. They are indicated in the STATUS
TABLE screen and by SM2R1 in EVALUATION STATISTICS.
Managing the SM2 output file
PAM output file
PAM output files are formatted in blocks.
The records are not separated by block boundaries.
An SM2 output file created with SHARED-UPDATE=*YES can be analyzed by SM2R1-PC
during the monitoring process or converted to a SAM file by SM2U1 and then analyzed
using SM2R1.
during the monitoring process or converted to a SAM file by SM2U1 and then analyzed
using SM2R1.