SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 40892: Staging jobs have errors after migrating from SAS® IT Resource Management 3.1.1 to 3.2

DetailsHotfixAboutRate It

When you are executing staging jobs in the SAS IT Resource Management 3.2 client or in batch deployment, you might receive errors similar to the following if the associated IT data mart has been migrated from SAS IT Resource Management 3.1.1:

Failure to start server
ERROR: User does not have appropriate authorization 
       level for library 

These error messages occur because the physical directories for the staging libraries do not exist before you execute the staging jobs. The root cause of this problem is due to incorrect behavior in the STAGEDLIBS= parameter in the %RMDMPKG migration macro. The %RMDMPKG macro is used to package IT data mart physical data from SAS IT Resource Management 3.1.1 so that it can be migrated to SAS IT Resource Management 3.2. The STAGEDLIBS= parameter defaults to NO, which means that staged libraries should not be packaged for migration. However, this incorrectly bypasses the allocation of the physical staging directories, which causes the error when the staging jobs are executed.

To prevent the errors described above, or any other miscellaneous errors that might occur from migrating the stage libraries, execute the %RMDMPKG macro by explicitly specifying STAGEDLIBS=YES as a macro parameter. This ensures that the target staging directories are allocated.

Alternatively, the target staging directories can be manually created before you run the staging jobs.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS IT Resource Management-Serverz/OS3.23.29.2 TS2M39.2 TS2M3
Microsoft® Windows® for 64-Bit Itanium-based Systems3.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Datacenter 64-bit Edition3.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Enterprise 64-bit Edition3.23.29.2 TS2M39.2 TS2M3
Microsoft Windows XP 64-bit Edition3.23.29.2 TS2M39.2 TS2M3
Microsoft® Windows® for x643.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Datacenter Edition3.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Enterprise Edition3.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 Standard Edition3.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2003 for x643.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 20083.23.29.2 TS2M39.2 TS2M3
Microsoft Windows Server 2008 for x643.23.29.2 TS2M39.2 TS2M3
Microsoft Windows XP Professional3.23.29.2 TS2M39.2 TS2M3
Windows 7 Enterprise 32 bit3.23.29.2 TS2M39.2 TS2M3
Windows 7 Enterprise x643.23.29.2 TS2M39.2 TS2M3
Windows 7 Home Premium 32 bit3.23.29.2 TS2M39.2 TS2M3
Windows 7 Home Premium x643.23.29.2 TS2M39.2 TS2M3
Windows 7 Professional 32 bit3.23.29.2 TS2M39.2 TS2M3
Windows 7 Professional x643.23.29.2 TS2M39.2 TS2M3
Windows 7 Ultimate 32 bit3.23.29.2 TS2M39.2 TS2M3
Windows 7 Ultimate x643.23.29.2 TS2M39.2 TS2M3
Windows Vista3.23.29.2 TS2M39.2 TS2M3
Windows Vista for x643.23.29.2 TS2M39.2 TS2M3
64-bit Enabled AIX3.23.29.2 TS2M39.2 TS2M3
64-bit Enabled HP-UX3.23.29.2 TS2M39.2 TS2M3
64-bit Enabled Solaris3.23.29.2 TS2M39.2 TS2M3
HP-UX IPF3.23.29.2 TS2M39.2 TS2M3
Linux3.23.29.2 TS2M39.2 TS2M3
Linux for x643.23.29.2 TS2M39.2 TS2M3
Solaris for x643.23.29.2 TS2M39.2 TS2M3
* 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.