Providing software solutions since 1976

• Log in
• Create profile
• Welcome
  [Log out]
• Edit profile

• Print  |
• Feedback  |
• Share

  • E-mail

  
  
  

  E-mail This Page

  Your Name:*
  Your E-mail:*
  Recipient E-mail:*
  Send a copy to me
  Personal Message:
  
  

  * indicates a required field

Attempting to run the CPMISC PDS member CMIMSLD IT Service Vision
(ITSV) job does not create any staged data.  It is possible to receive
the
following messages:

   WARNING: Staged data for table XIMSAPP could not be found in library
            IMSDATA
   NOTE: Table XIMSAPP with external name SAPIMSSP will not be
         processed.
   WARNING: Staged data for table XIMSAPB could not be found in library
            IMSDATA
   NOTE: Table XIMSAPB with external name SAPIMSBA will not be
         processed.
   WARNING: Staged data for table XIMSAPO could not be found in library
            IMSDATA
   NOTE: Table XIMSAPO with external name SAPIMSON will not be
         processed.
   WARNING: Staged data for table XIMTRAN could not be found in library
            IMSDATA
   NOTE: Table XIMTRAN with external name IMSTRAN will not be processed.
   WARNING: Staged data for table XIMFAST could not be found in library
            IMSDATA
   NOTE: Table XIMFAST with external name IMSFASTP will not be
         processed.
   WARNING: Staged data for table XIMBMPS could not be found in library
         IMSDATA
   NOTE: Table XIMBMPS with external name BMPS will not be processed.
   ERROR: No valid tables to be processed.

To circumvent this problem, instead of setting the macro variable
PIMSTRN to WORK as indicated in the documentation in the CMIMSLD member,
set PIMSTRN, PIMSBMP, PIMSFAS, PSAPION, PSAPIBA and PSAPISP to IMSDATA
using %LET statements in IMACIMSA.

The CMIMSLD member will be revised and updated in a future release of
ITSV.


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

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

Operating System and Release Information

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