DOCUMENT:Q130373 30-JUL-2001 [sms] TITLE :Obtaining Package ID from Within a Microsoft Test Script PRODUCT :Microsoft Systems Management Server PROD/VER:winnt:1.0 OPER/SYS: KEYWORDS:kbnetwork kbPCM smspcm ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Systems Management Server version 1.0 ------------------------------------------------------------------------------- When you write a custom detail status MIF, you may wish to obtain the package ID for the current package during the running of a Package Command Manager (PCM) job. You should be able to obtain the name of the directory one level up from the current working directory at the time PCM launches the job. This is available because PCM changes the current working directory to the package source before launching the specified workstation command. The parent directory name can be obtained from an executable file, or from within an Microsoft Test script, and then easily added to the information written by the administrator-written detail. For examples, see the BackOffice SDK Systems Management Server samples. Additional query words: sms prodsms ====================================================================== Keywords : kbnetwork kbPCM smspcm Technology : kbSMSSearch kbSMS100 Version : winnt:1.0 ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 2001.