UOA:OMQCHGSE

Change Sub-environment (OMQCHGSE) - Help

Change Sub-environment (OMQCHGSE)

This Application Program Interface command allows you to manipulate the TD/OMS database. This can be done from a command line or from within your programs.

The command enables you to perform all allowed actions on a sub-environment. You can use this command to add, change, copy, and delete the sub-environment definition.

Action code

Specify the action to be performed. The possible values are:

*ADD

Use this action code to add the sub-environment definition.

*CHANGE

Use this action code to change the sub-environment definition.

*COPY

Use this action code to copy the sub-environment definition.

*DELETE

Use this action code to remove the sub-environment definition.

Application code

Specify the application code. See the description of the application code for more information.

Environment code

Specify the environment code. See the description of the environment code for more information.

Sub-environment sequence number

Specify the sub-environment sequence number. See the description of the sub-environment sequence number for more information.

*NEXT

Use this value to allocate the next sub-environment sequence number. It will increment by 10 or round off to the nearest multiple of 10 if you are in add mode. However, if you are in change, copy, or delete mode, this value is not allowed.

Sub-environment new sequence number

Specify the sub-environment new sequence number.

*SAME

Use this value to indicate that the sub-environment sequence number does not change.

*NEXT

Use this value to modify the sub-environment sequence number to a new value. It will increase by 10 or round off to the nearest multiple of 10.

Sub-environment description

Specify the sub-environment description. See the detail of the sub-environment description for more information.

*SAME

Use this value to indicate that the sub-environment description does not change if you are in change mode.

Relation level

The relation level determines the extent of searching by TD/OMS for the related objects. TD/OMS uses the default highest value of 4 unless filled in otherwise. The possible values are:

0=Database, relations only (*LEVEL0)

TD/OMS keeps track of relations between physical files (PF) and logical files (LF) only. Other relations are not registered.

1=Relations only (*LEVEL1)

TD/OMS keeps track of relations between other object types besides the relations between PF and LF without, however, searching for a specific environment and library.

2=Database, relations, and locations in the same sub-environment (*LEVEL2)

This value is equal to value 1 (*LEVEL1) and it specifies the environment code and library name for related objects in the same sub-environment.

3=Relations in the same environment (*LEVEL3)

This value is equal to value 2 (*LEVEL2) and it specifies the environment code and library name for related objects in the same environment.

4=Relations and locations (*LEVEL4)

This value is equal to value 3 (*LEVEL3) plus it specifies the environment code and library name for related objects in the same application or related applications.

Note:  Value "4" (*LEVEL4) and "0" (*LEVEL0) are the most 
commonly used values.  

*SAME

Use this value to indicate that the relation level does not change if you are in change mode. If you are in add mode it contains the default value. The default value for the relation level is '*LEVEL4'.

Save replaced objects

The save replaced objects indicator instructs Object Transfer if replaced OS/400 objects or details of an OS/400 object have to be saved in the fallback save library.

This element only influences the saving of objects, not an automatic restore objects after an error during object transfer.

The default value is '0'. The possible values are:

0=No (*NO)

Replaced objects are not saved.

1=On error (*ONERROR)

Replaced objects or details of a replaced object are only saved if an error occurred during an object transfer to this sub-environment.

2=Always (*ALWAYS)

Replaced objects or details of a replaced object are always saved during an object transfer to this sub-environment.

*SAME

Use this value to indicate that the save replaced objects do not change if you are in change mode. If you are in add mode it contains the default value. The default value for the save replaced object is '*NO'.

Quit and Fall Back

The Quit and Fall Back indicator instructs Object Transfer if replaced native OS/400 objects or details of an OS/400 object in this sub-environment has to be automatically restored if an error occurred during an object transfer. The default value is '0'. The possible values are:

0=No (*NO)

No automatic fallback of replaced objects is executed if an error occurs during object transfer. TD/OMS will create as many objects as possible.

1=First failure (*ONERROR)

The processing of this sub-environment will stop and fallback will be executed for all replaced objects in this sub-environment if an error occurred during a transfer in this

sub-environment.

If the error occurred in the first selected sub-environments, further processing of other selected sub-environments will end. Processing will otherwise continue with the next selected sub-environment.

2=Follow rules (*FOLLOWRULES)

The decision to stop processing and start fallback will depend on a predefined critical object if an error occurred during a transfer in this sub-environment.

Processing will continue and no fallback is executed if this critical object has been processed successfully. The processing will stop and fallback will be executed for all replaced objects if this critical object has not been created at this point in the processing.

Further processing of other selected sub-environments will end if the error occurred in the first selected sub-environment. Processing will otherwise continue with the next selected sub-environment.

A critical object can be selected from the transfer proposal in the fix processing function just before you start the actual transfer.

*SAME

Use this value to indicate that the quit and fall-back do not change if you are in change mode. If you are in add mode it contains the default value. The default value for the quit and fall-back is '*NO'.

Sub-environment type

The sub-environment type is used in conjunction with the Object Distribution module at the moment of an object transfer.

If a sub-environment is selected (manually or automatically), the sub-environment type determines if the objects will be processed only on the current machine, only on remote machines specified in the distribution list, or on both remote and current machines. The possible values are:

0=Local (*LOCAL)

The sub-environment is only valid for the current machine. No distribution to remote machines will be started, even if a distribution list is specified. This is the default value for the sub-environment type.

1=Both (*BOTH)

The sub-environment is valid for both the current machine and for remote machines, specified in the distribution list. The distribution module is activated in order to handle the distribution of objects if a type "1" (*BOTH) sub-environment has been processed during an object transfer.

2=Remote (*REMOTE)

The sub-environment is only valid for remote machines specified in the distribution list. No objects are created on the current machine. The distribution module is activated immediately to handle the distribution.

Note:  Sub-environment types "1" (*BOTH) and "2" (*REMOTE)
will only work if you have the TD/OMS modules Object Distribution  
and Object Receiving installed on the sending and receiving     
machine.                                                                                                

*SAME

Use this value to indicate that the sub-environment type does not change if you are in change mode. If you are in add mode it contains the default value. The default value for the sub-environment type is '*LOCAL'.

Status

You can use the status option to disable this target or mark it as a branching template.

*SAME

Use this value to indicate that the status does not change if you are in change mode. If you are in add mode it contains the default value. The default value for status is '*ACTIVE'.

*ACTIVE

The sub-environment is used normally when transferring objects.

*DISABLED

The sub-environment is not used when transferring objects.

*TEMPLATE

The sub-environment is a branching template.

To application code

Specify the To application code. A blank value is not allowed.

To environment code

Specify the To environment code. A blank value is not allowed.

Copy directories

Specify the copy directories indicator. Use this field to indicate if the directories have to be copied. The possible values are:

*NO

Select value '*NO' to exclude them.

*YES

Select value '*YES' to include these definitions.

Copy distribution lists

Specify the copy distribution lists indicator. Use this field to indicate if the distribution list definitions have to be copied. The possible values are:

*NO

Select value '*NO' to exclude them.

*YES

Select value '*YES' to include these definitions.

Copy transfer paths

Specify the copy transfer paths indicator. Use this field to indicate if the transfer paths have to be copied. The possible values are:

*NO

Select value '*NO' to exclude them.

*YES

Select value '*YES' to include these definitions.

Copy compilation lists

Specify the copy compilation lists indicator. Use this field to indicate if the compilation lists have to be copied. The possible values are:

*NO

Select value '*NO' to exclude them.

*YES

Select value '*YES' to include these definitions.