Add this code to /opt/IBM/JazzSM/profile/registry/TdwcGlobalSettings.xml

<NewsFeed>
  <property name="FeedURL" value="http://warrengill.com/rss.xml" />
  <property name="FeedType" value="RSS" />
  <property name="PollInterval" value="3600" />
</NewsFeed>

Now you see a lightbulb when I add new articles to this blog.

One of the most common requests is for Workload Scheduler to send the output of jobs ended in error to a user. The built-in event-driven workload automation module seems well-suited to the task. However, there are a few problems.

Here's how to schedule around the Canadian holiday celebrating Queen Victoria's birthday.

Here's a small script I wrote to wait until no jobs are running in Workload Scheduler.

Want to ssh to one of your Workload Scheduler agents, but don't remember the nodename or hostname? Or, you know the name, but workstation name is much shorter? Try this:

ssh $(cpuinfo agent2 node)

The cpuinfo command reveals information that Workload Scheduler knows about the computer assigned to the workstation (nee CPU) definition you choose. When you run cpuinfo with only the workstation name, you see text similar to the following output.

We saw this question on one of the online Workload Scheduler forums recently.

Is anyone aware of a way to set up a rule to send an e-mail when a workstation fence is > 0?  I know there are no event specifically for this, however if anyone can think of a way to accomplish this, I would appreciate it.

Solving the problem (alerting when specific supplied event triggers do not exist) involves a few preliminary steps.

Even though IBM Workload Scheduler has lots of built-in run cycle settings (like 6th-day-of-the-month, or 2nd-Wednesday), these do not accommodate work days. To do that, you must use two calendars:

Sometimes your IBM Workload Scheduler job streams suddenly quit running. Maybe it's because the calendars that are used to schedule them have no future dates in them.

This short shell script (run as the "tws user") shows a list of calendars that have no future days, the last date contained in the calendar, and which job streams refer to the calendar.

If you use the Linux shell very much, you find its history functions very useful. You can recall previous commands very easily, just using the arrow keys.
If you use the Workload Scheduler command-line interfaces, conman and composer, you really miss the history. Sure there's the redo command, but its editing capability is limited to the last command you typed.