Running PROIV Developer for the First Time

All developers must be members of one or more projects to allow them to edit PROIV objects.

A minimum of an active project with a member group containing all developers will provide basic security and access to all source objects. A tighter control model can be built by using active/inactive projects, controlling filtered member groups and setting up member developers with exclusively assigned objects.

Projects are normally added and maintained in the System Administration module. An exception to this is that the first user to enter PROIV Developer in a PROIV environment is given the option to maintain the default project that PROIV Developer supplies, or to add a new project.

This first user is first shown a screen where they can choose to maintain one or more projects immediately, or defer this until later.

If the project security is left until later, the user exits the wizard, and enters PROIV Developer. They can then maintain projects from within PROIV Developer System Administration. The user is warned to log on as SYS in order to do this, since SYS is the only operator id supplied with Administrator privileges. (Any number of operator ids can be given Administrator privileges by the Administrator).

If the user decides to maintain Project security immediately, then they enter the PROIV Developer Project Security Wizard. The default project is offered for maintenance, but the user can choose to add a new project name if they wish.

The first user can maintain only one project. Other projects can be added later in PROIV Developer System Administration if required.

The first user must set up at least one Administrator. The logged on developer has Administrator privileges by default.

Comment on this topic

Topic ID: 500319