|
|
Menu/Master Data/Control Parameters
Group: General
|
Parameter Name
|
Values
|
Effect
|
|
Use Customer Application
|
Yes/No
(Default = No)
|
Is this parameter set to 'Yes', applications can be assigned to customers. In
the change request overview for a selected customer only change requests of the
selected applications are displayed.
|
|
One promotion per CR
|
Yes/No
(Default = No)
|
If set to 'Yes', the user doesn't have to create a promotion to attach objects to
a change request. MatchPoint automatically creates a promotion. This option is
useful, if only one promotion can exist for a change request.
|
|
Version check in all environments
|
Yes/No
(Default = Non)
|
If set to 'Yes', the object version is checked in all environments of the
promotion path with a higher sequence number, and not only the next environment in
the sequence.
|
|
Target Release
|
available values for IBM System i save command parameter TGTRLS
|
This parameter overwrites the default value of the save command with the
specified target release. The target release parameter is used for any save
commands in MatchPoint (creation of backups, creation of udpate packages, creation
of savefiles for transfer to remote servers)
|
|
Dependency across applications
|
Yes/No
(Default = No)
|
Allows to specifying dependencies between change requests from different
applications. Please check separate documentation for details.
|
|
Dependency across versions
|
Yes/No
(Default = No)
|
Allows to specifying dependencies between change requests from different
versions of the same application. Please check separate documentation for details.
|
|
Enforce promotion of dependent change
request
|
Yes/No
(Default = No)
|
When set to 'Yes', ‘only-with’-dependencies can’t be ignored anymore. They
must be promoted together with the selected change request.
|
|
Cumulate hours to change request
|
Yes/No
(Default = No)
|
When set to 'Yes', the recorde hours in the timesheet of a change request are
cumulated to the field ‘Time actual’ on the change request
|
|
Calculate percentage completed
|
Yes/No
(Default = No)
|
When set to 'Yes', the percentage complete value is calculated (time actual *
100 / time estimated)
|
|
Move objects to backup
|
Yes/No
(Default = No)
|
When set to 'Yes', the objects are moved to the backup directory instead of
copied. This applies only to objects in the Windows file directory. When moving
objects, any existing locks on the object are moved with the object. This way a
promotion can be executed, even when a user is locking the object in the target
environment.
|
|
Online help Root URL
|
http://matchpoint.cmfirst.ch/mphelp.php?function=
|
|
|
Report Folder
|
<YourServerDirectory>
|
The report window will point to the specified directory. MatchPoint will story
any files that are dropped into the report window in this directory.
|
|
Check conflict at model object import
|
Yes/No
(Default = No)
|
When set to 'Yes', the model object import checks for each object, if the same
object is already in a change request, which is in the same environment (typically the development environment). If yes, a conflict message is displayed. The import can be continued or cancelled.
|
|
Customized field names
|
Yes/No
(Default = No)
|
When set to 'Yes', MatchPoint allows for changing any field name on the
change request.
|
|
Cancel Promotion if Error
|
Yes/No
(Default = No)
|
When set to 'Yes', the promotion will terminate in any case of a promotion
error. The default behaviour is to continue with the promotion even when an object
can’t be promoted.
|
|
Ignore Object Conflicts when
a Dependency exists
|
Yes/No
(Default = No)
|
When set to 'Yes', an object conflict is ignored if a dependency is defined
between the two change requests
|
|
TopEase Import
|
Yes/No
(Default = No)
|
If this flag is set to 'Yes', the menu option for the TopEase Import will be
activated. To use the import function refer to the interface documentation.
|
|
TopEase Export
|
Yes/No
(Default = No)
|
If this flag is set to 'Yes', the menu option for the TopEase Export will be
activated. To use the export function refer to the interface documentation.
|
|
TopEase RootURL
|
<URL>
|
This root url is used to access the requirement in TopEase associated with
the change request in MatchPoint via the TopEase webserver.
|
Group: Display
|
Parameter Name
|
Values
|
Effect
|
|
End Date Green
|
Number (of days)
|
For change requests, which are not completed, the planed end date will be
displayed in green, if the planed end date is less than this number of days in the
future (this applies for the display in the grid)
|
|
End Date Yellow
|
Number (of days)
|
For change requests, which are not completed, the planed end date will be
displayed in yellow, if the planed end date is less than this number of days in the
future (this applies for the display in the grid)
|
|
End Date Orange
|
Number (of days)
|
For change requests, which are not completed, the planed end date will be
displayed in orange, if the planed end date is less than this number of days in the
future (this applies for the display in the grid)
|
|
End Date Red
|
Number (of days)
|
For change requests, which are not completed, the planed end date will be
displayed in red, if the planed end date is less than this number of days in the future
(this applies for the display in the grid)
|
Group: Promotion
|
Parameter Name
|
Values
|
Effect
|
|
Use Promotion Trigger
|
Yes/No
(Default = No)
|
When set to 'Yes', a new option appears in the scheduled promotions dialog.
When this flag is checked, MatchPoint promotion can be triggered by an entry in the
trigger file.
|
|
Assign objects only in Development
|
Yes/No
(Default = No)
|
When set to 'Yes', objects can only be modified/assigned in a development
environment. By default, it’s possible in all types of environments except ‘Production’
|
|
Check Promotion History for Promotions
|
Yes/No
(Default = No)
|
If this flag is set to 'Yes', MatchPoint will perform the following additional
check in case there are multiple promotions for a change request and the change
request is being promoted to a ‘customer environment’ (ISV-Situation, going from a
‘promote to customer’ to a selected ‘customer environment’):
-
Has the promotion already been promoted to the selected environment (check in promotion history for successful promotion)?
-
If yes, do not promote this promotion again, but only promote the promotion(s) that haven’t.
Note: This check is ONLY performed, if there are multiple promotions in the selected change request.
|
|
Use FTP GET
|
Yes/No
(Default = No)
|
If this flag is set to 'Yes', a FPT transfer between two IBM i servers will be
executed with an FTP GET command from the target system. By default CM MatchPoint is executing an FTP PUT commend from the source system.
|
|
Allow parallel promotions
|
Yes/No
(Default = No)
|
If this flag is set to 'Yes', CM MatchPoint is able to promote Change Requests parallel.
|
|
Ignore conflicts when completed
|
Yes/No
(Default = No)
|
If this flag is set to 'Yes', CM MatchPoint will ignore conlfict with completed Change Requests
|
Group: Billing
|
Parameter Name
|
Values
|
Effect
|
|
VAT Number
|
<YourVATNumber>
|
This VAT-Number will be printed on your invoices
|
Group: ISV
|
Parameter Name
|
Values
|
Effect
|
|
Promote along non-customer environments
|
Yes/No
(Default = No)
|
When set to 'Yes', the current environment on a change request will only be
changed when the change request is promoted into a non-customer environment.
|
|
Only direct successors
|
Yes/No
(Default = No)
|
If set to 'Yes', the dialog to select an environment for a promotion only
displays environment that are directly following the current source environment in the promotion path, and not all following environments.
|
|
Promote to customer environment
|
Yes/No
(Default = No)
|
When set to ‘No’, the current environment will not be changed to the
customer environment, even if the customer is specified on the change request. The default behaviour would change the current environment to the customer
environment, because the change request is assigned to the specific customer.
|
Group: Olympic
|
Parameter Name
|
Values
|
Effect
|
|
Test Olympic Delivery
|
Yes/No
(Default = No)
|
If set to 'Yes', additional tests are run for the promotion objects in an Olympic
delivery, such as file format and data in physical files.
|
Group: Source Code
|
Parameter Name
|
Values
|
Effect
|
|
Source Code Editor
|
Name and path of the source code editor that is to be used for displaying
IBM System i source codes.
|
|
|
Activate Source Check Out
|
Yes/No
(Default = No)
|
|
|
Source Code Temp Path
|
Directory in the ISF that is used to display IBM System i source codes. Make
sure user has access to this directory.
|
|
|
Source Code Versioning
|
Yes/No
(Default = No)
|
Creates automatically a version of the source code when checked in.
|
|
Source Code Check from DEV
|
Yes/No
(Default = No)
|
When the source code is checked back in, the code will be retrieved from the
developer environment or if configured, the personal developer environment. This
enables to check in the source code that was used for compilation of the object.
Note: if this parameter is set to yes, the parameter 'delete check-out source' can not be set to 'Yes' for this environment. This would cause the source code to be delete and therefore not be available for the ckeck in process.
|
|
Use SAVRST for all members
|
Yes/No
(Default = No)
|
When set to Yes, the promotion of members always uses the SAVRSTOBJ
commend. The advantage is, that the change date of the member is not modified and can always be compared to the compiled object.
Attention: When this option is used, all involved source files of an object type
must have the same file format ID. If the format ID is different, the copy process is
cancelled or a copy of the source file will be created (i.e. QCLSRC0001).
|
Group: Plex Add-In
|
Parameter Name
|
Values
|
Effect
|
|
Show cumulated Change Request
|
Yes/No
(Default = No)
|
If set to 'Yes', the CM MatchPoint Plex Add-in "My Change Request" will show Change Requests, that are part of an cumulative Change Request, in the Change Request list.
|
|
Assign objects only in development environment
|
Yes/No
(Default = No)
|
If set to 'Yes', the CM MatchPoint Plex Add-in "Add to current Change Request" will no assign objects to the current promtion, if the current promotion or the current CR is not in an development environment.
|
|
|
