The duplicate-checking process (DUPMODE=DISCARD) discards an observation that has a timestamp value less than or equal to the upper limit of a datetime range. However, in some cases, System Management Facility (SMF) records with exactly the same datetime stamp are split across tapes. In these circumstances, the first few records of the second tape are discarded because they match the criteria of being less than or equal to the upper limit of an existing datetime range.
No error messages, warnings, or notes are generated to indicate that there is a problem.
There is no workaround to the problem.
Click the Hot Fix tab in this note to access the hot fix for this issue.
To prevent these records from being discarded, apply the hot fix and specify the macro variable CPDUP_ALLOW_EQ.
When this macro variable is set to Yes, it specifies whether observations with equal timestamp values can be processed when they are the first records processed for the value that is specified in the IDVAR parameter. The default value for this macro variable is No.
If it is helpful for your site, you can also set the CDPUP_ALLOW_MSG macro variable.
This macro variable specifies whether messages should be produced when both of the following conditions are met:
- CPDUP_ALLOW_EQ is set to Yes.
- Observations with equal timestamps are encountered.
To set these macro variables, add the following statements to the beginning of the batch job.
%let cpdup_allow_eq=yesLET CPDUP_ALLOW_EQ=YES;
%let cpdup_allow_msg=yes;
If the macro variables are not specified in the batch job, their absence is interpreted as No. The following text shows the format of the messages that are produced when both of these macro variables are set:
Potential duplicate has been processed _n_=<observation number> system=<system name> id=<system id>
smftime=<SMF timestamp>
The following is an example of an actual message that might be produced:
Potential duplicate has been processed _N_=28833 SYSTEM=ABC1 ID=30 SMFTIME=17MAR2012:01:00:00
Operating System and Release Information
SAS System | SAS IT Resource Management-Server | z/OS | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows XP 64-bit Edition | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows 2000 Advanced Server | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 2.7 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise Edition | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Standard Edition | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows XP Professional | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Windows Vista | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Windows Vista for x64 | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
64-bit Enabled AIX | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
64-bit Enabled HP-UX | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
64-bit Enabled Solaris | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
HP-UX IPF | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Linux | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Tru64 UNIX | 2.7 | 3.3 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.