APAR status
Closed as documentation error.
Error description
RepAdmin context can no longer access the Replication Manager . Scenario: RepAdmin context can no longer access the Replication Manager with the same P&O that is in R17. . The clue was used to find the solution: . "In order to run the P&O editor, you must select a context . associated with a privilege authorizing the VPMAdmin.LOGIN process". . The unclear statement in LifeCycle Administration Guide, section Managing Replication Packages, About Managing Replication Package: . "You must have ADMIN privileges to be able to edit the packages, otherwise, you can only examine the packages." . Well, in order to examine the packages the context required VPMAdmin.LOGIN process, otherwise could not even start Package Manager. . The How to Manage Replication Packages section is in error. It says in step 1 that after catstart -run ManagePackages then the Package Manager window will appear. In fact, the "Welcome to application VPMAdmin" window appears where the user must select their context. . Need to request that correction, and clarification of granting VPMAdmin.LOGIN to the desired context before it is listed in the pull down. .
Local fix
Problem summary
RepAdmin context can no longer access the Replication Manager RepAdmin context can no longer access the Replication Manager . Scenario: RepAdmin context can no longer access the Replication Manager with the same P&O that is in R17. . The clue was used to find the solution: . "In order to run the P&O editor, you must select a context . associated with a privilege authorizing the VPMAdmin.LOGIN process". . The unclear statement in LifeCycle Administration Guide, section Managing Replication Packages, About Managing Replication Package: . "You must have ADMIN privileges to be able to edit the packages, otherwise, you can only examine the packages." . Well, in order to examine the packages the context required VPMAdmin.LOGIN process, otherwise could not even start Package Manager. . The How to Manage Replication Packages section is in error. It says in step 1 that after catstart -run ManagePackages then the Package Manager window will appear. In fact, the "Welcome to application VPMAdmin" window appears where the user must select their context. . Need to request that correction, and clarification of granting VPMAdmin.LOGIN to the desired context before it is listed in the pull down. .
Problem conclusion
THIS MODIFICATION WILL BE INCLUDED IN THE DOCUMENTATION DELIVERED WITH ENOVIA VERSION 5 RELEASE 19 SP02 LEVEL. Documentation Reference . LifeCylce Administration Guide Getting Started System and Data Administration/Partial Database Replication Setup and Admistration/Partial Replication Business Process/Managing Replication Packages . 1. Run the ManagePackages command by entering the following command line: catstart -run ManagePackages The Welcome to application VPMAdmin window appears. . 2. Select the context from the list and click OK. The Replication Package Manager window will appear. Note: You must have the administrator privileges in the selected context to make any package changes. .
Temporary fix
Comments
APAR Information
APAR number
HD78371
Reported component name
ENOVIA V5 VPM A
Reported component ID
569101400
Reported release
518
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-30
Closed date
2008-10-09
Last modified date
2008-10-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7P2G","label":"ENOVIA V5 VPM Discipline"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"518","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
09 October 2008