Transfer Activity Rules do not exist.

kastanek

Well Known Member
Hello list!

I've got a situation here where I'm getting an error message of "Transfer
Activity Rules do not exist" when our developers are using OMW. Here's
what's happening:

How we're set up:
--------------------------
We have two user groups: ADMIN and CORETEAM. Both have the same security
setup. Each has a record in Security Workbench to allow run and install
access to ALL applications. *PUBLIC is NOT locked out yet. (Eventually
we will want to tighten security for group CORETEAM)

Transfer activity rules are setup for project status 21 to 21 for *PUBLIC
such that all the development objects have transfer rule records.

Default projects are at status 21.

Users are OWNERS of the project at status 02 - Developers

Users log into the AS/400 using the same User Security (security server is
turned on) with Group Profile JDE.

So effectively both groups and the users in those groups have the exact
same authority on the system in both OW and the AS/400.

USER1 is in group ADMIN.
USER2 is in group CORETEAM


What's happening:
----------------------------
We are in the DV7333 environment.
We created a project at status 21 and added USER1 and USER2 BOTH as
developers to this project.
We added UBE R014021 to this project.

USER1 can check it out and in without issue.
USER2 get error: (From the Debug log)
Mar 01 11:59:43 ** 540/1640 Could not find release in the Trf Act Rule
Map for obj type, UBE; release, B7333.
Mar 01 11:59:43 ** 540/1640 Attempting to end a transaction with a NULL
hUser.

All the Transfer Activity rules have a valid release associated with them
and are set for user *PUBLIC.

When USER1 is put in group CORETEAM he can no longer check things in and
out - he gets the same error.
When USER2 is put in group ADMIN everything works fine.

It seems that the user group ADMIN has no problems but user group CORETEAM
does even though their security is exactly the same.

Has anyone seen this before?
Any ideas??

Please advise.

Regards,
Gerald.
 
Hi List,

Never mind I found it.

In an attempt to prevent the developers from making themselves PVC Admins
and giving themselves the right to promote projects out of DV and into PY
and beyond I had restricted the Project STATUS activity rules to ADMIN from
*PUBLIC. Unfortunately, I had done this for Project Status 21 to 21 as
well as 21 to >21 (23, 26, 28, etc..) This made the system think that
there were no Transfer Activity rules either for status 21 to 21 and only
ADMIN got perform any actions.

Thanks anyway.

Regards,
Gerald.




Gerald
Kastanek/Toronto/ To: Gerald Kastanek/Toronto/IBM@IBMCA
IBM@IBMCA cc:
Sent by: Subject: Transfer Activity Rules do not exist.
owner-jdelist@jde
list.com


03/01/2002 04:44
PM
Please respond to
jdelist






Hello list!

I've got a situation here where I'm getting an error message of "Transfer
Activity Rules do not exist" when our developers are using OMW. Here's
what's happening:

How we're set up:
--------------------------
We have two user groups: ADMIN and CORETEAM. Both have the same security
setup. Each has a record in Security Workbench to allow run and install
access to ALL applications. *PUBLIC is NOT locked out yet. (Eventually
we will want to tighten security for group CORETEAM)

Transfer activity rules are setup for project status 21 to 21 for *PUBLIC
such that all the development objects have transfer rule records.

Default projects are at status 21.

Users are OWNERS of the project at status 02 - Developers

Users log into the AS/400 using the same User Security (security server is
turned on) with Group Profile JDE.

So effectively both groups and the users in those groups have the exact
same authority on the system in both OW and the AS/400.

USER1 is in group ADMIN.
USER2 is in group CORETEAM


What's happening:
----------------------------
We are in the DV7333 environment.
We created a project at status 21 and added USER1 and USER2 BOTH as
developers to this project.
We added UBE R014021 to this project.

USER1 can check it out and in without issue.
USER2 get error: (From the Debug log)
Mar 01 11:59:43 ** 540/1640 Could not find release in the Trf Act Rule
Map for obj type, UBE; release, B7333.
Mar 01 11:59:43 ** 540/1640 Attempting to end a transaction with a NULL
hUser.

All the Transfer Activity rules have a valid release associated with them
and are set for user *PUBLIC.

When USER1 is put in group CORETEAM he can no longer check things in and
out - he gets the same error.
When USER2 is put in group ADMIN everything works fine.

It seems that the user group ADMIN has no problems but user group CORETEAM
does even though their security is exactly the same.

Has anyone seen this before?
Any ideas??

Please advise.

Regards,
Gerald.




--------------------------
 
Are the transfer rules the same for the 2 groups? I ran into an issue where I couldn't define a transfer rule for type *ALL, I actually had to define transfer rules for the individual objects, you may want to check that.


Matthew Scott
XE, SP 17.1, AS/400, Win2000 Logic Servers, Win2000 Term. Servers, Win2000 Java Servers, Central Objects in Oracle.
 
Please! how i can define a transfer activity rule for a DEMO environment?

Regards.

Ismail
 
Back
Top