Transfer Objects (TFROBJOMS) - Help

Transfer Objects (TFROBJOMS)

The Transfer Objects command is used to start an Object Transfer function via a command. The main difference with the Fix processing function is that you are able to process objects from more than one fix at a time, from all fixes of a request, or from all tasks that belong to a release. In contrast to Fix maintenance the TFROBJOMS command can not process empty fixes. Those are always skipped, but they never disrupt the transfer of valid fixes with content within the same run. Refer to Object Transfer concepts for more detailed information.

Check Only (CHECK)

Specify if the command only has to check the selected data. This is a required parameter. The possible values are:

YES: The entered data is validated and the results are printed on a report. The command ends after this has been completed, even if no errors and warnings are found.

NO: The entered data is validated and the results are printed on a report. The command starts to process the selected data if no errors or un-confirmed warnings were found after this has been completed.

Ignore Warnings (WARNINGS)

Specify if TD/OMS has to ignore warnings. The possible values are:

*NO: Warnings are not ignored. The transfer will not take place if any are found.

*YES: Warnings are ignored if possible.

Application (APPL)

Specify the application from which the selected data is taken. This is a required parameter.

Release (REL)

Specify that all fixes in the selected application with the indicated release number should be processed. The possible values are:

*NONE: The release number is not used to select fixes. You must specify either a request or a series of fixes (not both).

*CURRENT: The current release number from the selected application is used as the release number. The release number is defined in the application definition function (STRAD).

release-number: Enter a release number. All fixes with this release number are processed.

Request (REQ)

Specify that all fixes in the selected application which are connected to the indicated request are to be processed. The possible values are:

*NONE: The request number is not used to select fixes. You must specify either a release or a series of fixes (not both).

request-number: Enter a request number. All fixes connected to this request are processed.

Fix numbers (FIX)

Specify the fix numbers which are to be processed by the command. The possible values are:

*NONE: The fix numbers are not used to select fixes. You must specify either a release or a request to select fixes (not both).

*ALL: All fixes in the current application are selected for processing.

fix-numbers: Enter one or more fix numbers. All selected fix numbers are processed.

Fix application (FIXAPPL)

Specify the application of the connected fixes when a request is entered in the REQ keyword. The possible values are:

*ALL: All applications are selected for processing. An Object Transfer job is started per application.

fix applications: Enter the application code of the related fixes to be processed.

Fix path (FIXPATH)

Specifies which path must be selected in case the target environment defines is a *PATH or *USRPRF environment. The possible values are:

*DEFINED: If the target environment contains the *PATH or *USRPRF definitions then all fixes in the selection must contain the same PATH definition. If the path code in the selected fixes is not the same then the first fix in the selection determines the path code. If the target environment definition does not contain *PATH or *USRPRF then the path code in the fixes is ignored.

Path code: Enter the path code that must be used. This value is invalid if the target environment definition does not contain *PATH or *USRPRF. Only fixes with the specified path code are selected.

IFS Object code (IFSOBJ)

The IFS Full Path Name is a complete reference to an IFS object. This includes the directory and the object.

*OBJC: Use this value if you want to transfer one object from the i5/OS library structure instead of the integrated file system (IFS).

path-name: Specify a full pathname to the only object, you want to transfer.

Break-point Object (BKPOBJ)

Specify the object which is used as the break-point object. Refer to the Break-point object for a description of the data element. The possible values are:

*NONE: No break-point object is specified, if the 'quit-and-fall-back' option is set to '2' (follow rules). The fall-back will be started if the creation of an object in one of the library lists fails.

*LAST: Specifies that the last object in a batch of the specific type and attribute is to become the break-point object. E.g. you could code that the *LAST object of type *FILE, attribute PF is the break-point object which will cause the fall-back switch to turn off if the last physical file is successfully created in the target library list.

Name: Specifies the object code, type, and attribute of the object that is used as a break-point object.

Source environment (FROM)

Specify the source environment. The source environment selects the solutions which are to be processed from the selected fixes. A fix can contain solutions of different levels, but the transfer can only handle solutions originating from the same environment. The possible values are:

*LOW: The lowest environment found is used as the source environment. This means that all selected fixes are validated and the fix with the lowest environment determines the source environment. The rules for this are:

Objects from the production environment.
Objects from the *ANY environment.
Objects from the development environment.
Objects from the calamity environment.
Objects from environments between development and production.

*ANY: Selects all solutions in the specified fixes with the special status *ANY. Objects from *ANY always go to the development environment.

environment: Enter the environment from which the solutions must be transferred.

Target environment (TO)

Specify the target environment. The target environment indicates the environments to which the solutions are to be moved or copied. The possible values are:

*NEXT: Select the next logical environment as determined by the environment definitions.

*PREV: Select the previous logical environment as determined by the environment definitions.

*CAL: Select the emergency environment only if the from the environment is production.

*DEV: Select the development environment only if the environment is not developed.

*SAME: Perform a horizontal copy or move.

Option (OPTION)

Specify the move or copy option for this transfer. The possible values are:

*COPY_FROM_PROD_MOVE_THE_REST: If the source environment is the production environment perform a copy else perform a move.

*MOVE_FROM_DEV_COPY_THE_REST: If the source environment is either the emergency or the development environment perform a move (required for development environments) else perform a copy.

*MOVE: Move the selected solutions to the target environment. You can only move from an environment if you are authorized to alter objects in this environment.

*COPY: Copy the selected solutions to the target environment. Copy is not allowed from the development environments.

Target library lists (LIBL)

Specify the target library lists. The possible values are:

*ALL: Select all library lists in the target environment. *ALL is not allowed if you have specified anything other than *NONE or *ALL in the Include Library Lists attribute in the environment maintenance function. The transfer will fail if you select it anyway. If a *NONE environment has been defined, the LIBL parameter will be ignored.

list-of-library-list-sequences: Select up to 30 library list sequence numbers. The transfer will fail if you specify more library list sequence numbers than allowed as specified in the Include Library Lists attribute in the environment maintenance function.

Select Addresses (SELADDR)

Specify the remote addresses which have to be selected. This value must be *ALL if this is not a horizontal object transfer. One or more addresses may be left out for horizontal object transfers. The possible values are:

*ALL: All addresses (if any) are implicitly selected. This value is mandatory if it is not a horizontal transfer.

*LIST: Specifies that only the addresses specified in the ADDR keyword are selected. This value may not be used if it is not a horizontal transfer.

Target address list (ADDR)

Address

Specify the address, the schedule information, and the job description to be used for the remote job. The possible values are:

*ALL: Select all addresses specified in the environment definitions.

list-of-addresses: Select up to 30 addresses to which the solutions have to be distributed. The transfer will fail if an unspecified address is found. A warning will be issued if an address is left out.

Schedule date

Specify the scheduled date for the remote job. The possible values are:

*ARRIVAL: No scheduling is performed for the remote job.

Date: Enter the date on which the remote job has to be activated.

Schedule time

Specify the scheduled time for the remote job. The possible values are:

*ARRIVAL: No scheduling is performed for the remote job.

Date: Enter the time at which the remote job has to be activated.

Job description

Specify the job description to be used for the remote job. The possible values are:

*NORMAL: The default job description is used to start the remote job.

job description: Enter the job description which is used to start the remote job.

Hold Job

Specify the value to indicate whether you want to hold the transfer for the remote job. The possible values are:

*NO: Use this value to avoid holding the transfer for the remote job.

*YES: Use this value to hold the transfer for the remote job.

Note: The registry OMQDEPLOYCTL must be set to 1 for the application where you want to hold the job for remote transfer. If this registry does not exist or is not set to 1, the transfer for the remote job will not be held.

Output (OUTPUT)

Specify in what form the produced data must be listed. The possible values are:

*PRINT: The produced data is printed only.

*OUTFILE: The produced data is stored in an outfile, to be further specified. No data is printed.

*BOTH: The produced data is stored in an outfile and the data is printed.

Outfile (OUTFILE)

Specify for OUTPUT(*OUTFILE) and for OUTPUT(*BOTH) the file name and library where the data is stored in. The possible values are:

*LIBL: The library list is searched to locate the library of the existing outfile.

*CURLIB: The current library is used for the outfile.

library-name: Enter the name of the library for the specified outfile.

Output member options (OUTMBR)

Specify for OUTPUT(*OUTFILE) and for OUTPUT(*BOTH) the member name of the specified file and if the records are added to existing records or existing records are being replaced. The possible values are:

*FIRST: The first member is used to store the data.

member-name: Specify the name of the member to be used.

*REPLACE: Existing records are replaced by new records.

*ADD: New records are added to existing records.

Object Transfer Definition

To retain the records of the Object Transfer Definition (OMOTD) file, follow these steps:

1- Execute the STRSD command and update the following two fields:

Logging level: Set to 2 (Options: 1=Trace, 2=Debug, 3=Info, 4=Warning, 5=Error)
Program name: Specify as TRANSFER

Use the following command:

TFROBJOMS CHECK(*YES) WARNINGS(*YES) APPL(&APPC) FIX(&TASK)

UOA:TFROBJOMS

Contents

Transfer Objects (TFROBJOMS) - Help