markprod - Mark the State of a Customized Product Line

markprod [-kf] [-m message] [-v displayoptions] markname productline

The markprod utility saves the state of a customized product line and makes it available for checkout from the customization development branch using Lawson commands, such as createprod and updateprod.


Program Option	Description
`-m message`	Adds a short descriptive message to the mark.
`markname`	Assigns this name to the new mark. Note: The `markname` must be unique in the repository, among all Lawson releases. To see the marks in the repository, use `listproduct -abeir` or `listproduct -beir productname` .
`-k`	Invokes a prompt for repository credentials. Press Enter to accept the credentials shown.
`-f`	Forcibly make the mark even if one already exists.
`productline`	Assigns this name to the product line where the changes will be marked.
`-v displayoptions`	`errorlevel`, `tracelevel`, and `verbose` specified in any order, where: `errorlevel` = {n}one \| {f}atal \| {e}rror \| {w}arning (warning is the default) `tracelevel` = 0:6 where 0 is no message and 6 is everything `verbose` = whether to display exception stacktrace

Mark Name Guidelines

In the course of customizing an application and updating an application with new Landmark application releases, you will add many marks to the repository as a way of marking milestones on the branches. In order to make analysis easier, you need a logical system to the use of markprod. Below are suggested guidelines for the message and markname parameters:


Parameter	Guidelines
message	Use the message parameter to provide on the purpose of the mark or, in the case of marks added by individual developers, information that identifies the developer. For example `-m "Initial LMAPP release"` Marks the starting point for a branch for a product release. `-m "mjl - security mod 1"` Provides the developer's initials and some information on the code changes associated with the mark. `-m "TestStart - security mod set"` Marks the state of the source code at the start of testing a set of mods. `-m "Turnover - security mod set"` Marks the state of the source code when testing is complete and the modifications are ready to be turned over to another branch. `-m "Turnover - app update 0506"` Marks the state of the source code when testing is complete for a new release and so the new release is ready to be turned over to another branch. `-m "Update - app update 0506"` Marks the state of the source code when an update has been completed for a new release on a branch.
markname	Create the name of the mark from the following components: `branchIdentifier_release_changeID` where `branchIdentifier` is a short notation for the branch name, such as "D" for the development branch or "S" for the stage branch `release` is the application release in the format 00.00.00.00, for example, `05.02.00.01` for the 5.2.0.1 release of an application. `changeID` is a short notation for each mark in the sequence of customizations, such as `aa, ab, ac` and so on, through `zz`.