Problem Note 51784: A SAS® IT Resource Management 3.4 staging job might fail with an error for a migrated or upgraded System Activity Reporter (SAR) IT data mart
A SAS IT Resource Management 3.4 staging job might fail with the following error message.
NOTE: Variable _ENDSAR is uninitialized.
Rawdata: /install/users/sasdemo/rawdata/SAR/20121216.Linux.afssrv01.sar.asc
NOTE: The infile RAW is:
Filename=/install/users/sasdemo/rawdata/SAR/20121216.Linux.afssrv01.sar.asc,
Owner Name=sasdemo,Group Name=r&d,
Access Permission=-rw-r-----,
Last Modified=Tue Dec 18 06:31:10 2012,
File Size (bytes)=844246
OS=Linux MACHINE=afssrv01 version=2.4.21-40.ELsmp date=16DEC2012
ERROR: The SAS variable, _ENDSAR, specified by the ENDFILE parameter, is not in
use as an end-of-file indicator. The ENDFILE parameter must match the value of
the END= keyword on the INFILE statement being used to read the external source
data. To preserve the integrity of your IT DataMart, SAS will terminate with a
U1003 abend.
When a SAR IT data mart is migrated or upgraded, it might retain a legacy call to the
RMDUPCHK macro that is stored in the staging_library.SAR.RMDUPCHK.SOURCE entry, as shown in this code sample:
%rmdupchk(source=SAR,
idvar=MACHINE,
timestmp=DATETIME,
endfile=_ENDSAR,
int=01:15,
keep=250);
When a data mart retains a legacy call, the job failure occurs. Therefore, you need to update the value for the ENDFILE=parameter from "_ENDSAR" to "_EOF" to avoid any errors.
Operating System and Release Information
SAS System | SAS IT Resource Management-Server | z/OS | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft® Windows® for x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8 Enterprise 32-bit | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8 Enterprise x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8 Pro 32-bit | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8 Pro x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8.1 Enterprise 32-bit | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8.1 Enterprise x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8.1 Pro | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows 8.1 Pro 32-bit | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2008 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2008 R2 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2008 for x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2012 Datacenter | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2012 R2 Datacenter | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2012 R2 Std | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Microsoft Windows Server 2012 Std | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Windows 7 Enterprise x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Windows 7 Professional x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
64-bit Enabled AIX | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
64-bit Enabled Solaris | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
HP-UX IPF | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Linux for x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
Solaris for x64 | 3.4 | 3.4 | 9.4 TS1M1 | 9.4 TS1M1 |
*
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.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2014-03-21 15:37:33 |
Date Created: | 2013-12-10 09:21:44 |