IBM 51 ユーザーズマニュアル

ページ / 248
Cause
 
The
 
workflow
 
variable
 
values
 
are
 
limited
 
to
 
4000
 
bytes.
 
When
 
a
 
scriptlet
 
or
 
Java
 
plug-in
 
returns
 
a
 
value
 
longer
 
than
 
4000
 
bytes,
 
DB2
 
Universal
 
Database
 
will
 
throw
 
an
 
exception.
 
Solution
 
Keep
 
the
 
length
 
of
 
your
 
workflow
 
variables
 
to
 
less
 
than
 
4000
 
bytes.
 
 
DB2
 
Universal
 
Database
 
deadlocks
 
occur
 
when
 
the
 
system
 
runs
 
a
 
logical
 
operation
 
Cause
 
The
 
DB2
 
database
 
configuration
 
parameter
 
(lock
 
list)
 
value
 
is
 
not
 
large
 
enough.
 
Solution
 
Adjust
 
the
 
size
 
of
 
the
 
lock
 
list
 
value
 
from
 
50
 
to
 
2000.
 
Depending
 
on
 
the
 
volume
 
of
 
traffic
 
on
 
the
 
servers
 
and
 
the
 
size
 
of
 
your
 
data
 
center
 
model,
 
you
 
might
 
want
 
to
 
select
 
a
 
more
 
appropriate
 
value.
 
For
 
more
 
information
 
on
 
setting
 
the
 
lock
 
list
 
value,
 
go
 
to
 
Shell
 
command
 
error:
 
Resource
 
temporarily
 
unavailable
 
If
 
you
 
get
 
this
 
error:
 
bash:
 
fork:
 
Resource
 
temporarily
 
unavailable
,
 
it
 
might
 
be
 
accompanied
 
by
 
this
 
Tivoli
 
Intelligent
 
Orchestrator
 
message:
 
COPCOM123E
 
This
 
shell
 
command
 
error
 
occured:
 
Exit
 
value=128,
 
Error
 
stream=
 
"/usr/bin/bash:
 
fork:
 
Resource
 
temporarily
 
unavailable
 
",
 
Result
 
stream="".
 
Solution
 
Increase
 
the
 
maximum
 
number
 
of
 
processes
 
allowed
 
per
 
user
 
on
 
your
 
system.
 
For
 
instructions
 
on
 
setting
 
the
 
maximum
 
number
 
of
 
processes
 
allowed
 
per
 
user,
 
refer
 
to
 
the
 
documentation
 
for
 
your
 
operating
 
system.
 
Shell
 
command
 
error:
 
Exit
 
value=1,
 
Error
 
stream=",
 
Result
 
stream="no
 
bash
 
in
 
..."
 
When
 
you
 
are
 
running
 
a
 
workflow,
 
you
 
might
 
see
 
the
 
following
 
error:
 
COPCOM123E
 
This
 
shell
 
command
 
error
 
occurred:
 
Exit
 
value=1,
 
Error
 
stream="",
 
Result
 
stream="no
 
bash
 
in
 
/bin/usr/bin
 
/usr/sbin
 
/usr/local/bin
 
.
 
/usr/bin
 
/
 
etc
 
/usr/sbin
 
/usr/ucb
 
/usr/bin//usr/java131/jre/bin
 
/usr/java131/bin
 
/
 
nmlprod/common/scripts
 
/nmlprod/common/bin
 
/opt/seos/bin".
 
Solution
 
The
 
automation
 
package
 
that
 
you
 
are
 
running
 
requires
 
bash
 
on
 
the
 
endpoint.
 
IBM
 
Tivoli
 
Software
 
Support
 
personnel
 
have
 
requested
 
a
 
copy
 
of
 
a
 
workflow
 
Solution:
 
workflowLogExport
 
tool
 
This
 
command
 
line
 
utility
 
exports
 
the
 
run
 
history
 
of
 
one
 
or
 
more
 
specified
 
workflows
 
to
 
a
 
log
 
file
 
that
 
can
 
be
 
either
 
in
 
XML
 
format
 
(the
 
default
 
option)
 
or
 
in
 
any
 
other
 
file
 
format
 
of
 
your
 
choice.
 
 
Chapter
 
7.
 
Common
 
problems
 
and
 
known
 
limitations
 
in
 
Tivoli
 
Intelligent
 
Orchestrator
 
65