When processing BMC Patrol data with IT Resource Management (ITRM), the
following error might be generated:

   ERROR: The ID value xxxxxxxx occurs twice in the same BY group.

As a result, the PRCBUSY variable might report a missing (.) value.

The preferred circumvention is to add the LET option to the PROC TRANSPOSE 
step stored in the PGMLIB.PATROL.SASDS.SOURCE member by following these steps:

  o Make sure that you have a working backup of any performance database (PDB) 
    affected by this change.
  o Copy the PGMLIB.PATROL.SASDS.SOURCE member to ADMIN.PATROL.SASDS.SOURCE.
  o Modify the ADMIN.PATROL.SASDS.SOURCE program:

    Change:

         proc transpose data=&&tab&i out=trans ;
           var value;
           id svarnm;
           by machine instanc datetime durgrp duration ltable;
         run;

         %if &syserr gt 0 %then %goto exit;

    To:

         proc transpose data=&&tab&i out=trans LET;
           var value;
           id svarnm;
           by machine instanc datetime durgrp duration ltable;
         run;

         %if &syserr gt 4 %then %goto exit;

Specifying the LET option on the PROC TRANSPOSE statement allows duplicate groups to exist 
in the incoming data, but accepts only the last value for each group. Additionally, the 
check of the &syserr variable must be changed to a 4, because the PROC TRANSPOSE step 
will produce warning messages. Note that depending on the release of ITRM, there might be 
multiple occurrences of invocations of PROC TRANSPOSE that must be modified.

An alternative circumvention is to make sure that the raw data file that is read into 
ITRM does not have records with the same datetime/instance by using PROC SORT with the 
NODUPKEY option.

A fix for this issue for SAS IT Resource Management Release 2.7 is available at:

http://www.sas.com/techsup/download/hotfix/itrm27.html#009201


A fix for this issue for SAS IT Resource Management Release 2.6 is available at:

http://www.sas.com/techsup/download/hotfix/itrm26.html#009201

Operating System and Release Information

A fix for this issue for SAS IT Resource Management 2.7 is available at:

A fix for this issue for SAS IT Resource Management 2.6 is available at: