You're correct that you can get the"Error holding Job ID xx" error if
the sub-job has already completed (e.g. if the sub-job runs very fast). We
could improve the error to say something like "Job ID xx cannot be
monitored because it is no longer running". Note that this only happens
for sub-jobs that run very fast and have the monitor="1" attribute set.
Unlike a STAX job that is submitted via the STAX Monitor (where the STAX
Monitor adds a HOLD option to the STAX EXECUTE request to keep it from
starting to execute until it has gathered information to start monitoring
the job), we can't do this with a sub-job because it is the STAX service
that is submitting the STAX EXECUTE request (not the STAX Monitor) and it
can't use the HOLD option on the STAX EXECUTE request for the sub-job
because if the sub-job isn't being monitored, then it will be stuck in a
HELD state and won't run until it is completed. Maybe we could add
support for some sort of holdUntilMonitored option so that STAX adds the
HOLD option on the STAX EXECUTE request for a sub-job, but I'm afraid that
people will then complain that the sub-jobs are being held if they some
monitoring the parent STAX job.
As far as the same process showing up twice in the "Active Job Elements"
panel of the STAX Monitor, if you stop monitoring the STAX job and restart
monitoring the STAX job, that should clear up the issue. Does it?
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: Strösser, Bodo <bodo.stroes...@ts.fujitsu.com>
To: Sharon Lucas/Austin/IBM@IBMUS
Date: 08/02/2011 01:33 PM
Subject: RE: [staf-users] Startig STAX SubJobs in
<paralleliterate>^
On the monitor window, just after the monitor started to watch the Job,
the icon
for a <process> is displayed twice, one below the other. Both exactly show
the
same job name.
The process definitely is running on the machine only once.
The error, that sometimes pops up is “STAX Error” (Window title),
“Error holding Job ID 55
Block ‘main’ does not exist”
I think, the monitor finds the Job, but before it can hold the job, it
already is gone.
Bodo
From: Sharon Lucas [mailto:luc...@us.ibm.com]
Sent: Tuesday, August 02, 2011 8:27 PM
To: Strösser, Bodo; Strösser, Bodo
Cc: "staf-users@lists.sourceforge.net"@us.ibm.com
Subject: RE: [staf-users] Startig STAX SubJobs in <paralleliterate>^
I don't know what you mean by "sometimes the monitor displays the same
process twice". Please explain.
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: Strösser, Bodo <bodo.stroes...@ts.fujitsu.com>
To: Sharon Lucas/Austin/IBM@IBMUS
Date: 08/02/2011 01:06 PM
Subject: RE: Startig STAX SubJobs in <paralleliterate>^
Thank you for the reply!
I know, that messages are lost while a yob isn’t monitored and also I’m
using
<message log=”True”>. But when starting a Job, we normally watch the
startup and the start of the Sub Jobs for early errors.
Under some circumstances some of the SubJobs are running very short only.
In this case, some of the Jobs are not monitored at all. So we can’t even
see
the result that is printed out at the end of the job and have to look into
Job User Log, which isn’t as handy as seeing the result on the monitor.
In some cases, I also saw an error message coming up from the monitor for
such a short running job. Next time I’ll take a screen shot from this.
For the longer running Jobs sometimes the monitor displays the same
process twice. Maybe this comes from the monitor not being synchronized
at start of the job?
Bodo
From: Sharon Lucas [mailto:luc...@us.ibm.com]
Sent: Tuesday, August 02, 2011 7:45 PM
To: Strösser, Bodo; Strösser, Bodo
Cc: staf-users@lists.sourceforge.net
Subject: Re: Startig STAX SubJobs in <paralleliterate>^
No, there's not currently a way to have a sub-job wait for the STAX
Monitor to start monitoring it before the job starts execution.
Note that a message logged in the STAX Job User Log is persistent, unlike
a message sent to the STAX Monitor which is only displayed if the job is
currently being monitored by the STAX Monitor running on any machine(s).
Also, the number of messages displayed in the "Messages" table in the STAX
Monitor is limited by default to the most recent 200 messages (though you
can change this via the STAX Monitor Properties). And, when you stop
monitoring a STAX job, any messages sent while the job isn't being
monitored are not displayed. So, messages sent only to the STAX Monitor
can easily be "lost". If it is important that you see messages for your
sub-job, then you should consider logging the messages to the STAX Job
User Log as messages logged in the STAX Job User Log are persistent.
For example, if you're using the <message> element to send messages to the
STAX Monitor, you can add the log attribute to it to also log it in the
STAX Job User Log. For example: <message log="1">'This is my
message</message>
Note that the log attribute value defaults to the STAXLogMessage variable
whose value will default to 0 (false). But you can set STAXLogMesasage =
1 to turn on logging (for the whole job or just within a function or
block, etc).
Then you can view your STAX Job User Log for the sub-job and your messages
will always be there (no matter whether you're monitoring the sub-job or
not).
--------------------------------------------------------------
Sharon Lucas
IBM Austin, luc...@us.ibm.com
(512) 286-7313 or Tieline 363-7313
From: Strösser, Bodo <bodo.stroes...@ts.fujitsu.com>
To: "staf-users@lists.sourceforge.net"
<staf-users@lists.sourceforge.net>
Cc: Sharon Lucas/Austin/IBM@IBMUS
Date: 08/02/2011 12:16 PM
Subject: Startig STAX SubJobs in <paralleliterate>^
Hi Sharon,
my STAX Job is starting 4 SubJobs from a <paralleliterate> using <job
name=”xyz” monitor=”True”>.
Unfortunately, the monitor windows for the SubJobs are missing the first
few messages from the
SubJobs. Surely, I could insert a delay at the beginning of the Jobs, but
that is not a sane method
I think.
It would be better to make the Jobs wait for the monitor to come up. Is
there a way to do this?
Bodo
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
