Known Issues

Process Manager 7 has the following known issues:

  • When a user variable is used in a job definition's Name field, the value of the variable must be set when the flow is triggered. Otherwise the flow will fail to be triggered. For example, in Flow Manager, you may choose "Trigger" => "With Variables", or on command line use "jtrigger -v variable_list ...".

  • Applies to Linux hosts when JS_TIME_ZONE is set to “client”, the default. During Daylight Savings Time (in the March-November time period), some time events may trigger an hour early. This occurs when Java gets the wrong timezone information from the client machine. Solution: On the (Linux) client, edit the file /etc/sysconfig/clock and replace TIMEZONE=zone with ZONE=zone. For example, ZONE=”US/Eastern”.

  • The SGI IRIX 6.5.24 platform does not support the new Daylight Savings Time dates (that changed in 2007) when JS_TIME_ZONE is set to "client" (the default). Time-based scheduling is affected.

  • 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.

  • If a job command (command itself, not parameters) contains space and if the job is submitted to a queue with a job starter, the command doesn't work.

  • in xlsadmin, some menu items under Manage may be disabled after operating shutdown or close actions against LSF daemons.

  • In xlsadmin, lock/unlock LIM and start/stop service only has effect on the LIM that locates on the host where xlsadmin is started.

  • in xlsadmin, some menu items under Manage may be disabled when LSF_EGO_DAEMON_CONTROL="Y" is set in lsf.conf.

Effect of daylight savings time on flows

There are some known issues when running flows scheduled during and around the change to and from daylight savings time.


When...

Flow runs...

Expected behavior

A flow is scheduled to run between 2 a.m and 3 a.m. on the day daylight savings time begins (the second Sunday in March)

Never

This hour is the hour that is removed to start daylight savings time in North America. No flows run. Any subflows that are scheduled to start after this flow runs also will not run.

The client and server hosts have their time changed at different times:

  • Client before job submission, server after

  • Server before job submission, client after

At the time defined by the client.

The server receives the time from the client at the time of job submission and does any calculations in time difference between server and client at that time.

This applies on when JS_TIME_ZONE is set to client (the default). Server time is applied if JS_TIME_ZONE is changed to server.

You schedule the flow before the time change to run after the time change

At the time you scheduled (the correct time)

There is no impact. The flow is scheduled to run at 3 a.m. and it runs at 3 a.m., even after the time change.