---

Release Notes for Platform Process Manager 3.0

---

March 2006

Platform Computing

Comments to: doc@platform.com

Contents

• What's New in Process Manager Version 3.0
• Known Issues
• Learning About Process Manager Version 3.0
• Getting Technical Support
• Copyright

[ Top ]

---

What's New in Process Manager Version 3.0

Process Manager Version 3.0 has the following enhancements:

• New platforms
• Multiple domains
• Log in
• Backward compatibility
• Full time zone support
• Section 508 compliant
• LSF upgrade
• I18N: Internationalization
• Display release version

New platforms

Process Manager Version 3.0 now supports the following new platforms:

• AIX5.3
• HP UX 11.23
• Linux2.6 SLES9 and RHEL4 on x86
• Linux2.6 SLES9 and RHEL4 on AMD64
• Linux2.6 SLES9 and RHEL4 on EM64T
• Solaris 10 on Sparc

Multiple domains

Process Manager 3.0 now supports the use of multiple domains for user log on in a homogeneous environment (client and server are either both on Windows or both on Unix). If the server is on UNIX and the client is on Windows, the server can only accept Windows users from a single domain defined by LSF_USER_DOMAIN in lsf.conf.

Log in

You now have the ability to log in as any user (JS_LOGIN_REQUIRED=true).

Backward compatibility

Process Manager 3.0 client is not compatible with Process Manager 2.1 or JobScheduler 5.3 server.

Process Manager 3.0 client has limited compatibility with JobScheduler 5.31 server. All features of JobScheduler 5.31 function; however, new features from Process Manager 3.0 are not supported. For example, the Flow Editor of Process Manager 3.0 is able to submit flows to the JobScheduler 5.31 server (as long as JS_TIME_ZONE is set to "server") but you cannot duplicate flows, manually complete dependencies, or use the snapshot feature. We suggest you upgrade to Process Manager 3.0 server.

Full time zone support

Client can specify time-based scheduling based on server time, client time, or UTC time. In previous versions, scheduling was based on server time only.

Section 508 compliant

This software is section 508 compliant in most cases; it is accessible to people with disabilities.

LSF upgrade

Process Manager Version 3.0 works with Platform LSF version 6.0.

I18N: Internationalization

Process Manager Version 3.0 now has extensive capability to be translated into other languages. Many fields allow the input of local languages in double-byte character set such as Chinese and Japanese.

Display release version

JFD -V prints the Process Manager build date of JFD.

[ Top ]

---

Known Issues

Process Manager Version 3.0 has the following known issues:

• On Linux Redhat 7.0, due to a known java problem, scripts that run Process Manager commands and then monitor for exit code will never see an exit code 1 when it occurs--they see an exit code of 0.
• On HP, the failover feature does not work with a permanent license. Use a demo license.
• A Misschedule exception is not propagated through two consecutive link events in a flow.
• When using the Flow Editor or Flow Manager, and viewing or changing a job or job array definition, the entire job or job array definition dialog cannot be viewed if you are using a screen resolution lower than 1024 x 768. We recommend you set your resolution to 1024 x 768 or higher when using the Process Manager graphical user interface.
• When launching the graphical interfaces (Flow Editor, Calendar Editor and Flow Manager) on some UNIX systems, the user receives font not found warnings. The Java Virtual Machine user interface manager automatically determines which fonts are used on each machine. If the fonts are not available on the machine, the warning is issued. These warning messages do not affect the operation of the client.
• Process Manager does not validate the end date of a calendar expression. Consequently, if you define an end date prior to the start date, you receive no error message, but the calendar cannot be used in a time event to successfully trigger a flow or job.
• If you kill a job from the Flow Manager, the job state does not automatically refresh to reflect the change--you need to refresh manually, unless real-time status updates are being used.
• In the Flow Editor, on the Job Definition tabs, the Reset button only resets data on the current tab--it does not affect the hidden tabs. Values specified in the following fields do not reset at all when you click the Reset button:
  • Submit to queue/partition(s)--General tab
  • User name--General tab
  • Host requirements fields--Processing tab
• Some days of the week are not completely shown in the Calendar Editor for some platforms:
  • On Solaris: Mon, Wed, Thu are shown as M..., W..., T...
  • On HP: Mon, Wed are shown as M..., W...
  • On SGI: Sun, Mon, Wed are shown as S..., M..., W...
• Some historical information is not logged correctly in the following circumstances:
  • If a job or other activity has a rerun exception handler that is triggered, no information about the exit code of the job is logged.
  • When user variables are used for file transfer names, the resolved name of the file is not logged.
• When using the jsub -r command to submit and replace a flow definition, if the jsub command fails, the replacement does not occur, but the replaced flow definition is already deleted and cannot be restored.
• In the Flow Manager, it is possible for the user to have two different flows selected in the tree view and the right-hand pane. If the user selects an option in the Action menu, such as Kill, it is the flow selected in the tree view that is killed, not the one in the right-hand pane. This may not be the behavior the user expects.
• Process Manager does not support duplicate event logging in LSF. The lsb.events file must be in a shared location where the Process Manager server can locate job information.
• If a job using a rerun exception handler has a rerun delay specified, and the Process Manager restarts during the delay period (prior to rerunning the job), the job is never rerun.
• If a user tries to open the job dependency definition on the arrow coming out of the job with the variable in the job name field, the user sees an empty message dialog, prior to seeing the dependency definition. The user can click OK, to see the definition. However, the job name field is blank.

[ Top ]

---

Learning About Process Manager Version 3.0

World Wide Web and FTP

The latest information about all other supported releases of Process Manager is available on the Platform Web site at www.platform.com.

If you have problems accessing the Platform Web site or the Platform FTP site, send email to support@platform.com

[ Top ]

---

Getting Technical Support

Should you encounter problems or have questions regarding the use of Process Manager and scheduling jobs from SAS Management Console, please contact SAS directly. You can use one of the following methods to contact the SAS Technical Support staff.

1. Online problem/question submission:

   http://support.sas.com/techsup/contact/track_intro.html
   

   Choose SAS Management Console as the 'Product' value.

2. E-mail problem/question submission via EMITS facility:

   http://support.sas.com/techsup/contact/emits.html 
   

   Choose SAS Management Console as the 'Product' value.

3. Telephone Support Information for North America:

   http://support.sas.com/techsup/contact/telephone_support.ht
   ml  
   

4. If you are not based in North America, use the links in the following URL for information on how to contact other SAS Technical Support offices around the world:

   http://support.sas.com/techsup/contact/index.html  
   

While any SAS software user may contact Technical Support, priority is given to designated SAS support personnel at your site. (Note, you can use web-based forms to find out who the SAS support personnel are at your site or re-designate SAS support personnel at your site using links from this URL:

http://support.sas.com/techsup/contact/index.html

[ Top ]

---

Copyright

© 1994-2006 Platform Computing Corporation

All rights reserved.

Although the information in this document has been carefully reviewed, Platform Computing Corporation ("Platform") does not warrant it to be free of errors or omissions. Platform reserves the right to make corrections, updates, revisions or changes to the information in this document.

UNLESS OTHERWISE EXPRESSLY STATED BY PLATFORM, THE PROGRAM DESCRIBED IN THIS DOCUMENT IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL PLATFORM COMPUTING BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING WITHOUT LIMITATION ANY LOST PROFITS, DATA, OR SAVINGS, ARISING OUT OF THE USE OF OR INABILITY TO USE THIS PROGRAM.

^TM PLATFORM COMPUTING, and the PLATFORM and LSF logos are trademarks of Platform Computing Corporation in the United States and in other jurisdictions.

UNIX is a registered trademark of The Open Group.

Other products or services mentioned in this document are identified by the trademarks or service marks of their respective owners.

[ Top ]

---

Date Modified: March 31, 2006 Platform Computing: www.platform.com North America: +1 905 948 4297 Europe: +44 1256 370 530 Asia: +86 10 6238 1125 Toll-Free: 1-877-444-4LSF (+1 877 444 4573) Platform Technical Support: support@platform.com Information Development: doc@platform.com © 1994-2006 Platform Computing Corporation. All rights reserved.