I have verified that the tables between production and the test
environment
are defined exactly alike, as far as I can tell. Has anyone run
into this
kind of an error? Any insight would be appreciated.. The
transistion
variable is defined as a char field(1) and I do understand that the
data
type inherits the subtype and CCSID of the column of the triggering
table.
They are defined the same, so I am really at a loss as to why this
works in
one environment and not another. I am probably overlooking
something
obvious, but I can't see the forest for the trees.. TIA..

I have verified that the tables between production and the test
environment
are defined exactly alike, as far as I can tell. Has anyone run
into this
kind of an error? Any insight would be appreciated.. The
transistion
variable is defined as a char field(1) and I do understand that the
data
type inherits the subtype and CCSID of the column of the triggering
table.
They are defined the same, so I am really at a loss as to why this
works in
one environment and not another. I am probably overlooking
something
obvious, but I can't see the forest for the trees.. TIA..

Martin W - CNF Killen

Thanks Mike.. I talked with our SYSPROG's and we do not have these
applied
to our production environment yet.. They were working on getting
these
applied, but hadn't got there yet.. Thanks for the quick response..
I did
hear from one other indvidual that they were having the exact same
problem.
It has to do with our production tables being created around the V4
time and
our test tables are much younger... Thanks again..

Thanks Mike.. I talked with our SYSPROG's and we do not have these
applied
to our production environment yet.. They were working on getting
these
applied, but hadn't got there yet.. Thanks for the quick response..
I did
hear from one other indvidual that they were having the exact same
problem.
It has to do with our production tables being created around the V4
time and
our test tables are much younger... Thanks again..

Steven Mallett

Actually we're getting away with just ALTER TABLESPACE
<TSNAME> CCSID 37;
in several of our non-Production environments (but only until the
fix is
implemented as it's not the recommended approach).

We do have a Trigger in a development environment where we instead
did an
ALTER DATABASE <DBNAME> CCSID 37;
and this has worked also. The Tablespace is still CCSID=0 so
apparently
either can be used in creating the Trigger, although the manual
seems to
recommend both be altered.

I do feel that we're lucky in that the former values of CCSID=0
equate to
our site default of CCSID=37 (through the DSNDECP zparm?) but we
still
unloaded/reloaded the data anyway.

jane mike

Hi guys
I have a peculiar problem while creating Trigger. I am using
Secondary
Auth-id. Using that I created all tables, Tablespaces,etc.
When creating a trigger with different schema (xxxx), the SQL got
executed
with sqlcode = 0 but its not actually written in the
SYSIBM.SYSTRIGGERS.
Several times I executed the sql but it returns SQLCODE = 0. I am
executing
the thru SPUFI.

This seems to be a ridiculous, the same SQL (create trigger) can be
executed
with PRIMARY AUTHID (I mean the userid, if that id has been given
authority
to use the schema xxxx). I tried in different way by giving CREATIN
ON
SCHEMA xxxx to SECONDARY-AUTHID, but that also not actually
creating the
trigger but it returns SQLCODE = 0 in the SPUFI.

Does trigger support only primary auth-id..?
Can you suggest on this..?

Gulin Atabek

Hi,
We had the same problem a while ago: execute the CREATE TRIGGER
statement under a secondary-auth-ID thru SPUFI, receive SQLCODE =
0, but have no trigger created (DB2 UDB for OS/390 V6.1).
We solved the problem by APAR PQ40202 (SERVICE CONTROLLER PROBLEM:
BIND OF IMPLICITLY-CREATED TRIGGER PACKAGE FAILS DURING CREATE
TRIGGER, BUT SQLCA'S SQLCODE = 0).
Hope this helps,

Hi guys
I have a peculiar problem while creating Trigger. I am using
Secondary
Auth-id. Using that I created all tables, Tablespaces,etc.
When creating a trigger with different schema (xxxx), the SQL got
executed
with sqlcode = 0 but its not actually written in the
SYSIBM.SYSTRIGGERS.
Several times I executed the sql but it returns SQLCODE = 0. I am
executing
the thru SPUFI.

This seems to be a ridiculous, the same SQL (create trigger) can be
executed
with PRIMARY AUTHID (I mean the userid, if that id has been given
authority
to use the schema xxxx). I tried in different way by giving CREATIN
ON
SCHEMA xxxx to SECONDARY-AUTHID, but that also not actually
creating the
trigger but it returns SQLCODE = 0 in the SPUFI.

Does trigger support only primary auth-id..?
Can you suggest on this..?

This e-mail communication is intended for the private use of the
persons named above. If you received this message in error, please
immediately notify the sender and delete it from your system. The
Central Bank of The Republic of Turkey does not accept legal
responsibility for the contents of this message.

Hi guys
I have a peculiar problem while creating Trigger. I am using
Secondary
Auth-id. Using that I created all tables, Tablespaces,etc.
When creating a trigger with different schema (xxxx), the SQL got
executed
with sqlcode = 0 but its not actually written in the
SYSIBM.SYSTRIGGERS.
Several times I executed the sql but it returns SQLCODE = 0. I am
executing
the thru SPUFI.

This seems to be a ridiculous, the same SQL (create trigger) can
be
executed
with PRIMARY AUTHID (I mean the userid, if that id has been given
authority
to use the schema xxxx). I tried in different way by giving CREATIN
ON
SCHEMA xxxx to SECONDARY-AUTHID, but that also not actually
creating the
trigger but it returns SQLCODE = 0 in the SPUFI.

Does trigger support only primary auth-id..?
Can you suggest on this..?

---------------------------------------------------------------------------------------------------------------
This message and any attachment are confidential and may be
privileged or otherwise protected from disclosure.
If you are not the intended recipient, please telephone or email
the sender and delete this message and any attachment from your
system.
If you are not the intended recipient you must not copy this
message or attachment or disclose the contents to any other
person.
---------------------------------------------------------------------------------------------------------------