DFG:Pre Transfer Check Maintenance

From Remain Software
Jump to navigation Jump to search
Translate this page

Back.gif

Pre Transfer Check

The pre-transfer check mechanism is used to check if an object can safely be transported to the next environment. The pre-transfer check will check a couple of actions, e.g.

  • Level Checks for files,
  • Signature Level Check for service programs,
  • Etc...

A pre-transfer check defines how a check entry can be added to the pre-transfer check table OMPTC. It defines in which contexts the check entry can be added and describes the usage of the check.

Work with Pre Transfer Check

The Work with Pre transfer check display shows the currently defined checks, including their main parameters. To select an option, type the option number in the option field area and press Enter. For more information about an option move the cursor to the option column and press Help. For more information about a function key, move the cursor to the function key area and press Help.

The system indicator, the description of the function, a critical indicator, a local/remote indicator and the function owner are shown in addition to the functions. Refer to the Exception Concepts for more detailed information.

You can add a new check to the list, delete a check from the list, change the attribute of a check, or display the attribute of a check.


OMS02801.png


Filter

The Filter prompt can be used for a quick filtering of the list. Type the code or partial code of the below fields you wish to show in the list.

  • Sequence Number
  • Description
  • Program Name

Option

Use this column to perform different operations on individual entries. The possible values are:

  • 2=Change
    Type 2 to change the value of a check.
  • 3=Copy
    Type 3 to copy the check from the database.
  • 4=Delete
    Type 4 to remove a check from the database. TDOMS supplied checks can not be deleted.
  • 5=Display
    Type 5 to display the information about the check.
  • F6=Add
    Add a new occurrence of the entity you are working with.

Maintain Pre Transfer Check

The Maintain Pre Transfer Check display shows information and allows actions depending on the option chosen on the previous display. The chosen action on the previous display is shown on line three. The following modes can be activated:

  • Add
    You can add a new check. The sequence number, description, Authorization code and all other mandatory fields must be entered.
  • Change
    Change the attributes of an existing check.
  • Copy
    Copy the check from the database.
  • Delete
    The current pre-transfer check attributes are shown, including a confirmation message. The check is deleted from the list after pressing Enter.
  • Display
    Show the attributes of a check. The current values are shown.


Oms0282 1.png


Oms0282 2.png


Sequence Number

The Sequence Number is the order in which the check is being executed.

You can change the system-generated sequence number but it must be unique per check. A blank value is not allowed.

Description

The pre-transfer description contains a description of the pre-transfer check entry. A blank value is not allowed.

System indicator

The System Indicator indicates whether the check is supplied by TD/OMS or by the user. Value '1' indicates that the check is a TD/OMS supplied. Value '0' indicates check is created by user.

Only authorization code and disabled indicator value can be changed for TD/OMS supplied check.

Authorization code

Specify the authentication code that can confirm the errors or warnings coming from the pre-transfer check. The possible values are:

  • 2=Programmer
    Programmers can not confirm error or warning.
  • 3=Application manager
    Programmers can confirm error or warning.
  • 9=Block
    No one can confirm the issue. The issue has to be resolved before processing can continue.

Disable indicator

The disabled indicator is defined per pre-transfer check. It indicates if this check should execute or not. The possible values are:

  • 0=No
    The check will run.
  • 1=Yes
    The check will not run.

Object type

Specify the Object Type for which this check should be executed. Enter a valid object type or '*' for all object types.

Object attribute

Specify the Object Attribute for which this check should be executed. Enter a valid object attribute or '*' for all object attributes.

Application code

Specify the Application Code for which this check should be executed. Enter a valid application code or '*' if this check should be executed for all applications.

Environment code

Specify the Environment Code for which this check should be executed. Enter a valid environment code or '*' if this check should be executed for all environments.

Program name

The program name contains the name of a program which is called by TD/OMS during checkout.

Program library

The program library contains the OS/400 library where the exception program can be found.

Message id

The message id contains the name of the message-id of the pre-transfer check description text.

Message file

The name of the message file from which message-id is referred. By default "OMSMSG" message file is supplied, the user can change this value.

Gui Columns

It is now possible to configure which columns are visible and the header of these columns during the pre-transfer check. This is only possible for your own pre-transfer check definitions. Not for the system-supplied definitions. Please refer to the below description for more details.

  • Column
    The numbers match the column number.
  • Heading
    The columns for this particular check can be changed by entering the values in this field.
  • Weight
    The weight is the relative size of the column in the table. Value 0 will hide the column.

Command Start Pre Transfer Check Maintenance(STRPTCM)

This menu command starts the pre-transfer check function. Refer to the description of the function Pre Transfer Check for a detailed description.

This command has no parameters.

Pre Transfer Check details

Below are the detailed functions of each pre-transfer check.

Active Solutions Check
If you see this message, it means that you are going to replace an object that is currently attached to another task. This does not mean it is a version conflict. It just means that the object will, from this point on, be attached to your task and the other task as a *MERGE solution.
Unconfirmed Active Solutions Check
If version conflict confirmation is embedded in your organization then it means that you are going to replace an object that is currently attached to another task for which we could not find a confirmation record. This does not mean it is a version conflict. It just means that the object will, from this point on, be attached to your task and the other task as a *MERGE solution.
Object Without Target Check
If the configuration is not correct, you may see this error. It means that TD/OMS cannot find a suitable library or directory for the indicated objects in the target environment. This is sometimes related to location types and labels.
Possible Level check Check
You are processing a file that has dependencies that are not part of your transfer. This could mean that a level check could occur. The list will show which objects are depending on the object that you plan to process.
Target Version Check
You are going to overwrite an object version that is not a direct parent of your version. Note the objects and use the version conflicts view to resolve the issues.
Terminate Solution Check
All objects in the target environment which use the object will be checked. If they are not part of this transfer, then this message will be shown. You should probably not terminate an object which is in use by other objects.
Pending Transfer Check
There are still transfers pending completion on this or other systems. To close pending remote transfers, start the remote job monitor function.
Service Program Level Check
This check is done when not all dependent objects of a service program are processed. If you use a signature strategy, you may disable this check in the pre transfer check maintenance program.
Possible Signature violation check
Checks if the program to service program signatures match.
Check dependent logicals
It checks if there is an abnormal dependency. This occurs when either a dependent logical file exists but is not known to TD/OMS, or the dependent logical file exists in a different library than the physical file and its source does not exist.
Unconfirmed version conflict
It checks if there is a target higher environment that has a higher version of the solution.
User Defined
It is also possible to insert your own checking program. An example source is available in QUSRSRC. File a question in the helpdesk if you require support for this.