View source for DFG:Predefined Registry Settings

<translate>
{{clickpic|DFG:Definitions & Recovery Guide|{{filepath:Back.gif}}}}
==Predefined System Registry Settings== <!--T:1-->
==Saving Replaced Objects==
If you want to update programs into an environment that is being used, you must instruct TD/OMS to move the objects being replaced to a different location. This is done by setting the value of registry setting OMQSAVRPLLIB to a valid library name on the system where you want this to happen.  If the library does not exist it is created. QRPLOBJ (The library being used by IBM when a program is created with REPLACE(*YES)) is not a bad choice. In addition to this, you have to set the value of OMQSAVRPLTYPES with a list of object types to save.

<!--T:2-->
Please note that manual maintenance of any other library than QRPLOBJ is required. You should empty this library after an IPL.

<!--T:3-->
The registry setting is global. It cannot be specified for a specific application or environment.

===OMQSAVRPLLIB - Save Replaced Objects Library=== <!--T:4-->
Contains the library that is used to store replaced objects in. Could be QRPLOBJ. Please note that QRPLOBJ is in the system ASP. In case of an iASP the library is called QRPLxxxxx (where xxxxx is the number of your iASP).If you have 1 iASP than the library will most likely be QRPL00033. Moving objects across ASP's is not possible. TD/OMS will generate the fallback library in the iASP so you need to use the iASP equivalent of QRPLOBJ or your own library in the same iASP.

<!--T:5-->
'''Example'''<br>
'''OMQCHGSR ACTC(*ADD) KEYW(OMQSAVRPLLIB) KEYV(QRPLOBJ)'''

===OMQSAVRPLTYPES - Save Replaced Objects Types=== <!--T:6-->
Contains a list of comma separated object types that must be saved when replaced. E.g. *PGM, *SRVPGM, *USRSPC

<!--T:7-->
'''Example'''<br>
'''OMQCHGSR ACTC(*ADD) KEYW(OMQSAVRPLTYPES) KEYV('*PGM, *SRVPGM')'''

<!--T:8-->
'''Since'''<br>
This setting is active in version V5.1M04 and higher

==OMQILEPRC - Automatically update programs and service programs== <!--T:182-->
If this registry setting is set for a specific application and environment combination then every module and service program that is processed automatically updates the program or service program with the new module or service program by using the UPDPGM and UPDSRVPGM commands. Please see the UPDILEOMS command for more information.

<!--T:183-->
'''Example'''<br>
'''OMQCHGSR ACTC(*ADD) APPL(''required application'') ENVC(''required environment) KEYW(OMQILEPRC) KEYV('1')'''

<!--T:184-->
'''Since'''<br>
This setting is active in version V5.1M04 and higher

==OMQPRDDLTLOCK - Disallow ''Delete Object and Source'' from Production Environments== <!--T:9-->
If an object is disconnected from the fix, or if the user uses option 4=Delete in Object Maintenance, the option to also remove the object and source is shown. This is often not desirable in a production environment and is potentially dangerous. Note that removing objects from production is only allowed to Application Managers and owners of the production environment. If you want to inhibit this behavior altogether for production environments then set this registry entry. Please note that the user is still invited to delete object and source but gets a message if the flag is set.

<!--T:10-->
'''Since'''<br>
This setting is active in version V5.1M07 and higher.

===OMQPRDDLTLOCK - Production delete lock=== <!--T:11-->
Contains '1' if the lock is active.<br>
Contains '0' if the lock is not active<br>
The effect of any other value is not defined.

<!--T:12-->
Create the registry setting like this:

<!--T:13-->
'''OMQCHGSR ACTC(*ADD) APPL(optional application) KEYW(OMQPRDDLTLOCK) KEYV('1')'''

== OMQALWOBJREG - Allow Object Registration== <!--T:14-->
This routine checks if it is possible to register an object in the database outside of the regular object registration functions. This prevents objects to be introduced outside certain allowed environments.
 
The check is done by querying OMQALWOBJREG. This registry setting can be set system-wide, per application or per environment. The value can be:
 
 *DEVONLY - Only allowed in development environments
 *NO      - Not allowed for this system/application/environment
 *YES     - Allowed for this system/application/environment
Finer definitions take preference over global definitions meaning that environment specifications override application specifications which in turn override system-wide specifications.

<!--T:15-->
'''Since'''<br>
This setting is active in version V5.0M12 and higher.

<!--T:16-->
Create the registry setting like this:

<!--T:17-->
'''OMQCHGSR ACTC(*ADD) APPL(''optional application'') ENVC(''optional environment) KEYW(OMQALWOBJREG) KEYV('*DEVONLY')'''

== OMQALWOBJREFILL - Allow Object Change== <!--T:18-->
This setting disables the possibility to refresh the status of an object in the database outside of the regular object registration functions. This prevents objects to be changed by outside forces (e.g. recompiled) outside certain allowed environments.
 
The check is done by querying OMQALWOBJREFILL. This registry setting can be set system-wide, per application or per environment. The value can be:

<!--T:19-->
<big><big>
 *DEVONLY - Only allowed in development environments
 *NO      - Not allowed for this system/application/environment
 *YES     - Allowed for this system/application/environment
</big></big>
Finer definitions take preference over global definitions meaning that environment specifications override application specifications which in turn override system-wide specifications.

<!--T:20-->
'''Since'''<br>
This setting is active in version V5.0M12 and higher.

<!--T:21-->
Create the registry setting like this:

<!--T:22-->
'''OMQCHGSR ACTC(*ADD) APPL(''optional application'') ENVC(''optional environment) KEYW(OMQALWOBJREFILL) KEYV('*DEVONLY')'''

==Transfers only allowed in batch== <!--T:23-->
Set registry key BATCHONLY to '1' in order to activate the setting. This keyword must be set in combination with the application code and the program code. 

===BATCHONLY - Batch transfers only=== <!--T:24-->
'''OMQCHGSR ACTC(*ADD) APPL(DEMO) PGMN(OMO001) KEYW(BATCHONLY) KEYV('1')'''

==Force usage of connection rules== <!--T:25-->
Forces the use of connection rules. The GUI will not allow connecting without rules if this flag is set. In the green screen, even if the user uses '1=Select' in the object maintenance function, the connection rules are activated.

===FORCECONNRULE - Force Connection Rules=== <!--T:26-->
'''OMQCHGSR ACTC(*ADD) APPL(DEMO) KEYW(FORCECONNRULE) KEYV('1')'''

==Confirming a Transfer== <!--T:27-->
If you want a validation of the user before a transfer takes place, you are able to specify this in registry key CONFIRMTRANSFER. This will instruct TD/OMS to ask for the password of the current logged in user to ensure that this is actually the user that started the transfer.
===CONFIRMTRANSFER - Confirm Transfer===
====Green Screen====
*OMQCHGSR ACTC(*ADD) APPL(DEMO) PGMN(OMO001) KEYW(CONFIRMTRANSFER) KEYV('0')
*:Transfers do not need to be confirmed.
*OMQCHGSR ACTC(*ADD) APPL(DEMO) PGMN(OMO001) KEYW(CONFIRMTRANSFER) KEYV('1')
*:All transfers must be confirmed by entering the user's password.

====GUI==== <!--T:178-->
*OMQCHGSR ACTC(*ADD) APPL(DEMO) PGMN(OMX943) KEYW(CONFIRMTRANSFER) KEYV('0')
*:Transfers do not need to be confirmed.
*OMQCHGSR ACTC(*ADD) APPL(DEMO) PGMN(OMX943) KEYW(CONFIRMTRANSFER) KEYV('1')
*:All transfers must be confirmed by entering the user's password.

==Keep the source date== <!--T:28-->
This setting instructs TD/OMS not to change the source change date of the member being transferred. This is achieved by employing save/restore rather than CPYSRCF to copy a source member. In order for this to work, the from and to file must be of the same level. This means that keeping the source date does not work if the record lengths differ between source files. 

===KEEPSOURCEDATE - Keep the source date=== <!--T:29-->
* OMQCHGSR ACTC(*ADD) KEYW(KEEPSOURCEDATE) KEYV('0')
*:The sourcedate does not need to be kept in the source member. TD/OMS will guard the source change date in its database.
* OMQCHGSR ACTC(*ADD) KEYW(KEEPSOURCEDATE) KEYV('1')
*:Try to do a save and restore to keep the source date. If this is not possible then ignore the error and try to copy the source file with CPYF which will change the source change date information in the sourcemember.
* OMQCHGSR ACTC(*ADD) KEYW(KEEPSOURCEDATE) KEYV('2')
*:Try to do a save and restore to keep the source date. If this is not possible then an error is reported that will start fall-back processing.

<!--T:30-->
'''Since'''<br>
:'''This setting is NOT active anymore in version V6.4M00 and higher.'''
:As of IBM i/OS V6R1M0 this is solved in the CPYSRCF command.
:For IBM i/OS V5R4M0 PTF SI25844 is required.
:For IBM i/OS V5R3M0 PTF SI25796 is required.

==AS/SET System libraries== <!--T:31-->
In case your AS/SET libraries are not ASSETO or ASSETF then you can change this by setting registry entries per application.

===OMASSETO - Set the AS/SET object library=== <!--T:32-->
* OMQCHGSR ACTC(*ADD) APPL(''appl'') KEYW('OMASSETO') KEYV(''value'')

===OMASSETF - Set the AS/SET file library=== <!--T:33-->
* OMQCHGSR ACTC(*ADD) APPL(''appl'') KEYW('OMASSETF') KEYV(''value'')
*:Sets the AS/SET file library to a different value.

 <!--T:34-->
ASSETGPL cannot be changed. Please contact us if you need this.

==OMSCOPLIMLF - Logical File Creation Scope Limit== <!--T:35-->
* OMQCHGSR ACTC(*ADD) APPL(''appl or blanks for all applications'') ENVC(''environment or blanks for all environments'') KEYW('OMSCOPLIMLF ') KEYV(''0, 1 or 2'')

<!--T:36-->
The keyword restricts the library list scope of the logical file creation. If the value is not found then TD/OMS will use the standard way of creating a logical. This standard process includes a search of all environments until the correct or most probable physical file has been found. If the logical resides in an intermediate environment then all higher environments will be searched for the associated physical but never the production locations. 

<!--T:37-->
The possible values for KEYV are:

<!--T:38-->
*0 - Library
*:Only build logicals over physicals in the same library.

<!--T:39-->
*1 - Library List (Sub-environment)
*:Only build logicals over physicals in the same library list or sub-environment.

<!--T:40-->
*2 - Environment
*:Logicals can be build over any physical in the same environment.


<!--T:41-->
'''Since'''<br>
This setting is active in version V5.1M07 and higher.

==OMIFSSRCEXT - Stream File extension definition for Source data save== <!--T:42-->
* OMQCHGSR ACTC(*ADD) APPL(''appl or blanks for all applications'') ENVC(''only *NONE'') ROTC(''route or blanks for all Routes'')  KEYW('OMIFSSRCEXT ') KEYV(''any character string representing one or a series of file extension types or *ALL for all stream files'')

<!--T:43-->
Determines the extension type of Stream Files for which contents (source) save in an archive file will be activated. The source save procedure will be processed when the file component is transferred to the lowest (development or emergency) environment in the Application. If a KEYV has to be defined for a series of file extensions, remind that the first four positions of the extension string will be compared with blocks of maximal four characters in the file extension definition string. 


<!--T:44-->
'''Since'''<br>
This setting is active in version V5.1M13 and higher.

==OMQINLLIBL - Initial Library List For Batch Jobs== <!--T:45-->

<!--T:46-->
Sets the library list to be used with batch jobs submitted by TD/OMS: the value is used for the <code>INLLIBL</code> parameter on the <code>SBMJOB</code>-command.
If this entry is not registered in the TD/OMS System Registry, the value <code>*CURRENT</code> is used (this value is also used in all versions before V51KEM11). The value can be specified as follows:

<!--T:47-->
*<code>OMQCHGSR ACTC(*ADD) APPL(''application'' | *NONE) KEYW(OMQINLLIBL) KEYV(*CURRENT | *JOBD | *SYSVAL | *NONE)</code>

<!--T:48-->
The possible values for <code>KEYV</code> are all described in the help panel of the command <code>SBMJOB</code>. Only the single values are allowed: specifying a list of libraries is not possible. The listed valid values are valid for IBM i V5R1M0; the list may be extended in future releases.


<!--T:49-->
When TD/OMS submits a batch job, the value for <code>INLLIBL</code> is determined in three steps:

<!--T:50-->
# Retrieve the value of <code>OMQINLLIBL</code> for the current application
# If not found, retrieve the global value of <code>OMQINLLIBL</code> (application code is <code>*NONE</code>)
# If not found, use <code>*CURRENT</code>


<!--T:51-->
Step 1 is skipped for jobs that are not dependent on any application, like ''Reorganize Files''. It is not possible to define a value for a specific environment within an application.


<!--T:52-->
'''Since'''<br>
This setting is active in version V5.1M11 and higher.

==OMQFALBCKUSRX - Fall Back User Exit program== <!--T:53-->

<!--T:54-->
If you want to trigger a user defined program after a Fall Back has been executed, you should use this registry setting. If the call to the program defined fails a message is sent to the TD/OMS log. 

<!--T:55-->
* OMQCHGSR ACTC(*ADD) APPL(''appl or blanks for all applications'') KEYW('OMQFALBCKUSRX') KEYV(''program name'')

<!--T:56-->
The program is called with the following parameter list:

<!--T:57-->
*Transfer code (8 character)
*Application (5 character)
*From environment code (5 character)
*To environment code (5 character)
*Status (5 character)


<!--T:58-->
'''Since'''<br>
This setting is active in version V5.1M13 and higher.

==OMSCANPHASES - Scan source relationship== <!--T:263-->
Scan the source relationship based on the number of phases. This registry setting can be set system-wide, per application, or per environment. The value can be:

 <!--T:264-->
01 - To scan for included files (like copymembers) and external data structures only.
 02 - To scan for fields.
 The higher the number the slower the relationship processing will be but the more information can become available.

<!--T:265-->
'''Since'''<br>
This setting is active in version V5.3M00 and higher.

==OMQPRCLODINT - Load internal ILE procedures in TD/OMS relation database== <!--T:59-->

<!--T:60-->
If you want to load the internal ILE procedures into the TD/OMS relation database, you should use this registry setting. 

<!--T:61-->
* OMQCHGSR ACTC(*ADD) APPL('' blanks'') KEYW('OMQPRCLODINT') KEYV(''1'')

<!--T:62-->
'''Since'''<br>
This setting is active in version V6.0M02 and higher.



==OMQRMTJOBMONUSR - Remote Job Monitor User == <!--T:63-->
 
If you have set-up TD/OMS with another TD/OMS system user then the default user profile OMS and you want to use Remote Job Monitor functions, you should use this registry setting.
This registry setting must be set on the local machine and on the receiving machine(s).
 
* OMQCHGSR ACTC(*ADD) KEYW('OMQRMTJOBMONUSR') KEYV(''TD/OMS system user profile'')
 
'''Since'''<br>
This setting is active in version V6.0M03 and higher.

==OMQLODSQLOBJ - Load SQL Objects in TD/OMS == <!--T:67-->

<!--T:68-->
If you want to load the SQL long names of database objects and to see the relations with their counterpart native implementation, you shoulf use this registry setting.
The loaded SQL objects cannot be used as a solution in TD/OMS and therefore the SQL objects cannot be maintained with TD/OMS.

<!--T:69-->
* OMQCHGSR ACTC(*ADD) APPL(appl) ENVC(environment code or blanks for all environments) KEYW('OMQLODSQLOBJ') KEYV('1')

<!--T:70-->
'''Since'''<br>
This setting is active in version V6.0M03 and higher.

==OMQGUIDIAPORT - GUI Dialog Server Port == <!--T:71-->

<!--T:72-->
If you want to be able to start a dialog with a client running the TD/OMS GUI, you have to specify a TCP/IP port with this registry key. After the port is changed, clients must restart in order to listen to the new port.

<!--T:73-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQGUIDIAPORT') KEYV('01234')

<!--T:74-->
Replace '01234' with the required port. Please use 5 positions.

<!--T:75-->
'''Since'''<br>
This setting is active in version V6.4M00 and higher.

==OMQRATFIX - Ratification Fix setting== <!--T:76-->
* OMQCHGSR ACTC(*ADD) APPL(''appl or blanks for all applications'') ENVC(''environment or blanks for all environments'') KEYW('OMQRATFIX') KEYV(''0, 1 or 2'')
 
Determines the way the ratification authority validation is executed. If the value is not found then TD/OMS will use the classic way of ratification authority validation. 
 
The possible values for KEYV are:
 
*0 - Any user can ratify a fix.
*:Any user who is a member of the ratification group can ratify the fix.
*1 - User can not ratify his own fix.
*:Any user who is a member of the ratification group can ratify the fix, except if the user is the programmer of the fix.
*2 - Only user can ratify his own fix.
*:Any user who is a member of the ratification group can only ratify their own fixes.
 
'''Since'''<br>
This setting is active in version V6.4M00 and higher.

==OMQDSTPROFILE - OMS Distribution Profile== <!--T:83-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQDSTPROFILE') KEYV([''user profile''|''*CURRENT''])
 
This user profile is used to perform TD/OMS distributions. If this registry setting is not defined it is taken from the owner of the file OMOBJ. This is normally the user OMS. However, on systems with more then one OMS installation you could need a different profile.
 
The possible values for KEYV are:
 
*''user profile''
*:Specify the user profile to be used for distributions.
*''*CURRENT''
*:The current user profile is used.
 
'''Since'''<br>
This setting is active in version V6.4M00 and higher.

==OMQTCPSYSNAME - OMS TCP Distribution System Name== <!--T:89-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQTCPSYSNAME') KEYV(''System name'')
 
This system name is used to send back the messages needed for the remote job monitor mechanism when the TD/OMS TCP distribution is used. If this registry setting is not defined the local location name from the network attributes is used.
This registry setting should only be used when the local location name (on the remote system) does not match the hostname used for TCP communication.
 
The possible values for KEYV are:
 
*''System Name''  
*:Specify the system name used for TCP communication.

==OMQSOCSRMV - Remove Solution After Split== <!--T:93-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQSOCSRMV') APPL(''application'') KEYV('1')

<!--T:94-->
The user option CS from supplied user option program OMUSROPTSO (source resides in QUSRSRC) is able to move a solution from one fix to another. 

<!--T:95-->
The possible values for KEYV are:

<!--T:96-->
*''1''  
*:The solution is removed after it was successfully attached to the new fix.

<!--T:97-->
*''other then 1 or not defined''
*:The solution stays connected to the old fix as a *FOLLOW solution

<!--T:98-->
'''Since'''<br/>
This setting is active in version V6.4M00 and higher.

==OMQAUTREFTYP - Adopt Authorization from OMSREFOBJ with specific object type== <!--T:99-->
* OMQCHGSR ACTC(*ADD) APPL(appl or blanks for all applications) ENVC(environment or blanks for all environments) KEYW('OMQAUTREFTYP') KEYV(0 or 1) 

<!--T:100-->
If in the [[DFG:Application Definition#Authority conversion type |''Application Definition'']] the authority conversion type is set to value 1=adopt or 2=OMSREFOBJ, TD/OMS tries to adopt the authority from object OMSREFOBJ with type *DTAARA.
This registry setting makes it possible adopt the authority from object OMSREFOBJ with a specific object type.

<!--T:101-->
The possible values for KEYV are:

<!--T:102-->
*''1''  : The authority is adopted from object OMSREFOBJ with the specific object type if it exists, otherwise it is adopted from object OMSREFOBJ with type *DTAARA.

<!--T:103-->
*''0''  : The authority is adopted as described in [[DFG:Application Definition#Authority conversion type |''Application Definition'']].

<!--T:104-->
'''Since'''<br/>
This setting is active in version V6.5M04 and higher.

==OMQDISTR1ADDR - Distribution object set per address== <!--T:105-->
* OMQCHGSR ACTC(*ADD) APPL(application or blanks for all applications) ENVC(environment or blanks for all environments) KEYW('OMQDISTR1ADDR') KEYV(0 or 1) 

<!--T:106-->
According to default processing, TD/OMS creates one distribution set with all objects involved in a transfer and sends this set to all the addresses selected within that transfer. On the receiving systems, the final selection is made which objects should be processed at the specific address and which can be skipped according to conditions and selections in the environment definitions.

<!--T:107-->
If the requirement is to restrict the distribution set to only those objects that have been really passed selection criteria for the specific address, this registry setting must be activated.


<!--T:108-->
The possible values for KEYV parameter are:

<!--T:109-->
*''1''   : The object distribution set is restricted to objects filtered for the specific sub-environment.

<!--T:110-->
*''0''   : The object distribution set is created for all addresses at once.

<!--T:111-->
'''Since'''<br/>
This setting is active in version V6.5M05 and higher.

== OMQDISTRBASEDIR == <!--T:112-->
* OMQCHGSR ACTC(*ADD) KEY('OMQDISTRBASEDIR') VALUE''('path/to/dir')''

<!--T:113-->
This keyword is automatically set when the INZOMSSVR command is run. It contains the base queuing directory for this installation.

== TD/OMS Compilation settings == <!--T:114-->
===OMQCOMPJOBD - Compilation Job Description ===

<!--T:115-->
 OMQCHGSR ACTC(*ADD) APPL(application or blanks for all applications) ENVC(environment or blanks for all environments) KEYW('OMQCOMPJOBD') KEYV('*LIBL     YOURJOBD  ')

<!--T:116-->
If you use the TD/OMS compile in batch function the TD/OMS compile command is submitted to batch with the job description from the user. If you want to use a specific job description for TD/OMS batch compiles, you should use this registry setting. This job description is used for sequential compiles. Some object types can be compiled in parallel, for this, take a look at registry setting OMQCOMPJOBDP.

<!--T:164-->
The key value first ten positions must contain the job descriptions library and the key value positions 11-20 must contain the job description name.

<!--T:165-->
'''If you want to activate parallel compiles then see also'''<br> 
* OMQCOMPJOBDP
* OMQCOMPPRCSEQ

<!--T:117-->
'''Since'''<br>
This setting is active in version V6.5M00 and higher.

===OMQCOMPJOBDP - Job Description for Parallel Compilation === <!--T:166--> 

<!--T:167-->
* <code>OMQCHGSR ACTC(*ADD) APPL(application or blanks for all applications) ENVC(environment or blanks for all environments) KEYW('OMQCOMPJOBDP') KEYV('*LIBL     YOURJOBD  ')</code>

<!--T:168-->
If you use the TD/OMS compile in batch function the TD/OMS compile command is submitted to batch with the job description from the user. If you want to take advantage of the parallel compile function, you should use this registry setting. This job description is used for parallel compiles and is used in combination with OMQCOMPJOBD. Define a job description which uses a jobqueue for which multiple jobs can be active at the same time.

<!--T:169-->
The key value first ten positions must contain the job descriptions library and the key value positions 11-20 must contain the job description name.

<!--T:170-->
'''See also'''<br>
* OMQCOMPJOBD
* OMQCOMPPRCSEQ

<!--T:171-->
'''Since'''<br>
This setting is active in version V11.0M01 and higher.

===OMQCOMPPRCSEQ - Parallel Compilation Processing Sequence === <!--T:172--> 

<!--T:173-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQCOMPPRCSEQ') KEYV(Processing Sequence Number)

<!--T:174-->
If you use the TD/OMS parallel compilation functionality then you will have to use this registry setting. If you don't specify the processing sequence number then it would pick 67500 as a default processing number. 

<!--T:175-->
If the objects processing sequence value is less than the specified number then compile jobs will be submitted in the job queue specified in OMQCOMPJOBD. Otherwise, jobs will be submitted in a parallel queue which is specified by setting OMQCOMPJOBDP. The processing sequence [[DFG:Change Fix Processing Sequence|can be changed here]].

<!--T:176-->
'''See also'''<br> 
* OMQCOMPJOBD
* OMQCOMPJOBDP


<!--T:177-->
'''Since'''<br>
This setting is active in version V11.0M01 and higher.

==OMQAUTIFSDIR - Stream file authorization from target directory== <!--T:118-->
* OMQCHGSR ACTC(*ADD) APPL(application or blanks for all applications) ENVC(environment or blanks for all environments) KEYW('OMQAUTIFSDIR') KEYV(0, 1 or 2) 
According to default processing TD/OMS creates stream file objects with the authority settings from the from object (see parameter AUT(*OBJ) on the CPY command). 
If the requirement is to create stream file objects with authority settings from the directory it is created in, this registry setting must be activated.
 
 
The possible values for KEYV parameter are:
*''0''   : The stream file object is created default with authority (like parameter AUT(*OBJ) on the CPY command).
*''1''   : The stream file object is created default with authority from the target directory (like parameter AUT(*INDIR) on the CPY command).
*''2''   : The stream file object is created default with authority from the target directory and the from object (like parameter AUT(*INDIROBJ) on the CPY command).

<!--T:158-->
WARNING: Using a ''2'' on a receiving system may give unexpected results as the authorizations of the TD/OMS receiving directory (which is a temporary directory) are also taken into account.
 
'''Since'''<br/>
This setting is active in version V6.5M05 and higher, also IBM i/OS V6R1M0 or higher is required.

==OMQAUTPGMRCHG - Authorisation for fix programmer change== <!--T:126-->
* OMQCHGSR ACTC(*ADD) APPL(application or blanks for all applications) ENVC(environment or blanks for all environments) KEYW('OMQAUTPGMRCHG') KEYV(3)

<!--T:127-->
This registry setting can be used to prevent the change of the fix programmer.

<!--T:128-->
If it is required to prevent programmers to assign their own fixes to another programmer this registry setting must be activated.


<!--T:129-->
The possible values for KEYV parameter are:

<!--T:130-->
*''3''   : The fix programmer can only be changed by users with authorization code 3.

<!--T:131-->
'''Since'''<br/>
This setting is active in version V9.0M01 and higher.

==OMQWORKDIRCANDM - Work directory for compare and merge== <!--T:132-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQWORKDIRCANDM') KEYV('/QOpenSys/TD/tmp/CMWDIR')

<!--T:133-->
This registry setting can be used to point to a new working directory for source compare and merge.

<!--T:134-->
If this key is not defined, programs should assume the default value of '/QOpenSys/TD/tmp/CMWDIR'.

<!--T:135-->
'''Since'''<br/>
This setting is active in version V9.0M01 and higher.

==OMQ4GLGENOBJ - Scope limit for generated objects check== <!--T:136-->
* OMQCHGSR ACTC(*ADD) APPL(application) KEYW('OMQ4GLGENOBJ') KEYV('FIX') or 'TFR' 

<!--T:137-->
see: [[2E:Match_2E_and_generated_object#OMQ4GLGENOBJ:_scope_limit_for_generated_objects_check|''2E scope limit for generated objects check'']]

==OMQGITURL - Git base URL== <!--T:138-->
* OMQCHGSR ACTC(*ADD) APPL(application) ROTC(route) KEYW('OMQGITURL') KEYV('https://github.com/githubname/myapplication.git')

<!--T:142-->
This registry setting is used as the URL for the Git repository of the route of this application. This registry setting is automatically set by the INZGITOMS command. If you manually import your sources you have to manually set the values below as well.


<!--T:145-->
'''Since'''<br/>
This setting is active in version V9.1M00 and higher.

==OMQOMSGITDIR - TD/OMS Git Script Directory== <!--T:149-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQOMSGITDIR') KEYV('/QOpenSys/TD/Git/')

<!--T:150-->
This registry setting is used to indicate the directory where the Git scripts are saved. This setting is automatically created when command '''INZOMSSRV *GIT''' is performed.


<!--T:151-->
'''Since'''<br/>
This setting is active in version V9.1M00 and higher.

==OMQGITPRCRTE - GIT Process Route code == <!--T:152-->
* OMQCHGSR ACTC(*ADD) APPL(<application>) KEYW('OMQGITPRCRTE') KEYV(<route>)

<!--T:153-->
This registry setting is used to define the TD/OMS route code where the IBM i sources can be found. Use this registry setting when your IBM i sources are managed by TD/OMS and [[GIT:Git|Git]] to indicate additional processing (connect objects to a task when checking in an IFS source. See [[GIT:Git|the Git manual for more information.]] This registry setting is automatically set by the INZGITOMS command. If you manually import your sources you have to manually set the values below as well. 

<!--T:154-->
'''Since'''<br/>
This setting is active in version V10.0M01 and higher.


==OMQGITAMSTRPUSH - GIT Allow Push to Master == <!--T:159-->
* OMQCHGSR ACTC(*ADD) APPL(<application>) RPTC(<route>) KEYW('OMQGITAMSTRPUSH') KEYV(<0|1>)

<!--T:160-->
This registry setting is used to define if you allow (1) a direct push to master for the specified route. The default value is not to allow a direct push (2) but use feature branches.
 
'''Since'''<br/>
This setting is active since version V10.0M02

==OMQEXTCMPLIBL - Extended Compilation library list == <!--T:155-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQEXTCMPLIBL') KEYV('1')

<!--T:156-->
This registry setting is used to define that the Environment Compilation library lists are extended with additional libraries to locate object relations outside the active, current TD/OMS application.
When using this option all applications involved in the relationship search must be classified in Application Group definitions.



<!--T:157-->
'''Since'''<br/>
This setting is active in version V10.1M00 and higher.

==OMQOPENAPIRTE - Route for OpenAPI Generation == <!--T:161-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQOPENAPIRTE') KEYV(<route code>)
* OMQCHGSR ACTC(*ADD) APPL(<application>) KEYW('OMQOPENAPIRTE') KEYV(<route code>)

<!--T:162-->
This registry setting is used to define where OpenAPI specifications have to be generated. This can be set on the application level or on the system level. Application level will take precedence over system level.

<!--T:163-->
'''Since'''<br/>
This setting is active in version V10.0M03 and higher.



==OMQJRNWRKLIB  - Work Library for Journal Analyzer == <!--T:179-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQJRNWRKLIB') KEYV(<Work Library Name>)

<!--T:180-->
This registry setting is used to define the library where temporary information would be stored. Please specify the value of "<Work Library Name>" accordingly. The contents of this library may grow but can be discarded at any time. QTEMP will not work.
 

<!--T:181-->
'''Since'''<br/>
This setting is active in version V11.0M01 and higher.

==OMQTESTOBJREGEX - Test Objects Regex == <!--T:185-->
* OMQCHGSR ACTC(*ADD) APPC(<application|empty>) KEYW('OMQTESTOBJREGEX') KEYV(<valid java regex>)

<!--T:186-->
This registry setting is used to identify programs and service programs that are test objects. These objects will be folded in the Work Management tree under the Test node. Enter a valid java regular expression on the system level or fill in a specific application code to override the system level. The default value is "(TS.*|.*TST.*)".

<!--T:187-->
The objects are matched against a qualified name. For example, the qualified name for an RPGLE program object is '''NAME.PGM.RPGLE'''. If you only want RPGLE objects to match as test objects, the regex could be '''TST.*RPGLE$''' which matches all objects starting with TST and ending in RPGLE.

<!--T:189-->
Changes in this setting are active after restarting the GUI.


<!--T:188-->
'''Since'''<br/>
This setting is active in version V12.0M01 and higher.


==OMQJOBLOGGEN - Generate Job Log after GUI Call == <!--T:190-->
* OMQCHGSR ACTC(*ADD) KEYW('OMQJOBLOGGEN') KEYV('OMC022')

<!--T:191-->
This registry setting is used to determine which TD/OMS programs must generate a job log after being called from the GUI. The default program is OMC022 which is used to interactively compile an object. The program names must be uppercase and separated by a space.

<!--T:192-->
Changes in this setting are active after the GUI is restarted.

<!--T:193-->
'''Since'''<br/>
This setting is active in version V12.1M00 and higher.


==OMQLINKPREFIX - Generated Tracker Link Prefix == <!--T:194-->
When a Task or Request is connected to a tracker item like Jira or Gravity, a backlink is generated in the tracker item. This registry setting is used to define a custom link that is used as a prefix for the generated tracker backlink to TD/OMS. The total link length should be 150 positions or less.

<!--T:195-->
Syntax:
* OMQCHGSR ACTC(*ADD) KEYW('OMQLINKPREFIX') APPC(*NONE|_application_) PGMN(*NONE|'TASK'|'REQUEST') KEYV(_url_)

<!--T:200-->
'TASK' and 'REQUEST' are literals.

<!--T:201-->
You can define the variable multiple times in different combinations. Consider the following entries (stored in table OMAGP)

<!--T:202-->
{| class="wikitable"
!colspan="6"|Table OMAGP
|-
|Entry
|APPC
|PGMN
|KEYV
|-
|1
|*NONE
|TASK
|https://octo.remainsoftware.com/org/remain?handle=tdoms/tasks/{application}/{number}
|-
|2
|*NONE
|REQUEST
|https://octo.remainsoftware.com/org/remain?handle=tdoms/request/{application}/{number}
|-
|3
|ORDER
|*NONE 
|https://order.remainsoftware.com/org/remain?handle=orders/?number={number}&application={application}
|-
|4
|*NONE
|*NONE
|https://octo.remainsoftware.com/welcome.html/?type={type}&number={number}&application={application}
|}

<!--T:203-->
The following search order will be used:

<!--T:204-->
# Application / Type
# Application / *NONE
# *NONE / Type
# *NONE / *NONE


<!--T:205-->
Given application 'TEST' Type='TASK' and the Task number='T0001'<br>
'''Entry 1''' is taken because it is the only entry that matches application 'TEST' and type 'TASK'
 https://octo.remainsoftware.com/?handle=tdoms/tasks/TEST/T0001


<!--T:206-->
Given application 'ORDER' Type='TASK' and the Task number='T0001'<br> 
'''Entry 3''' is taken over entry 1 because the application takes precedence.
 https://order.remainsoftware.com/?handle=orders/?number=T0001&application=ORDER


<!--T:207-->
Given application 'BOOK' Type='REQUEST' and the number='R9999'<br>  
'''Entry 2''' matches 'Request' and application 'BOOK' does not have a key.
 https://octo.remainsoftware.com/?handle=tdoms/request/BOOK/R9999


<!--T:208-->
'''Entry 4''' is used only in cases where the type will not be 'Task' or 'Request'. This situation does not occur.


<!--T:196-->
You can use the following variables:

<!--T:209-->
; {type} : 'Task' or 'Request'
; {number} : The Task or Request number
; {application} : The Application code


<!--T:198-->
Changes in this setting are active after the GUI is restarted.

<!--T:199-->
'''Since'''<br/>
This setting is active in version V14.0M01 and higher.

==OMQFLBCOPYTYPES - Copy or Move the object to fall-back library== <!--T:210-->
*OMQCHGSR ACTC(*ADD) KEYW(OMQFLBCOPYTYPES) KEYV('*PGM *SRVPGM')
*: This registry setting is used during the promotion. The object type is matched with the value of the OMQFLBCOPYTYPES keyword, it contains a space-separated list of object types. If a match is successful, the object is copied to the fallback library else it is moved.

<!--T:211-->
'''Since''' <br>
This setting is active in version V14.0M03 and higher.

==OMQUSRDTALIB - User Session Data library== <!--T:212-->

<!--T:236-->
The OMQUSRDTALIB setting controls the location of the OMS user session data. When this registry setting is used, it can point to a library where the session data must be stored. The special value *OMSLIB is used to point to the OMS library. This entry is required if you use the TD/OMS REST API.   

                                               
<!--T:213-->
'''Since''' <br>
This setting is active in version V14.1M00 and higher.

==OMQCREATEBRANCH - Automatic Branch Creation== <!--T:214-->

<!--T:237-->
*OMQCHGSR ACTC(*ADD) APPL(optional application) KEYW(OMQCREATEBRANCH ) KEYV('1')

<!--T:238-->
This registry setting activates automatic branch creation when a new task is added.

<!--T:215-->
The possible values for KEYV are:

<!--T:216-->
*1
The branch will be created automatically.

<!--T:217-->
*other than 1 or not defined
The branch will not be created automatically.


<!--T:218-->
'''Since''' <br>
This setting is active in version V15.0M01 and higher.

==OMQAUTOTSKREQNR - Fill the task and request number automatically== <!--T:219-->
*OMQCHGSR ACTC(*ADD) KEYW(OMQAUTOTSKREQNR) KEYV('1')     
This registry setting is used to automatically fill the task and request number from a ticket.

<!--T:220-->
The possible values for KEYV are:

<!--T:221-->
*1
The task and request number will be filled out automatically.  

<!--T:222-->
*other than 1 or not defined
The task and request number will not be filled out automatically. 

<!--T:223-->
'''Since''' <br>
This setting is active in version V15.0M01 and higher.

==OMQRMTJDBSYNDFT - Local job descriptions automatically synchronize the remote job descriptions == <!--T:224-->

<!--T:239-->
*OMQCHGSR ACTC(*ADD) APPL(<application|empty>) ENVC(<environment|empty>) KEYW(OMQRMTJDBSYNDFT) KEYV('1')     

<!--T:240-->
When the user sets the local job description during transfer, then the remote job descriptions are automatically switched to the same value when this registry is active. You can override this value at three different levels.

<!--T:225-->
The possible values for KEYV are:

<!--T:226-->
*1
Synchronize.

<!--T:227-->
*other than 1 or not defined
Do not synchronize. 

<!--T:228-->
'''Since''' <br>
This setting is active in version V15.0M02 and higher.

==OMQJWTSECRET- This registry setting is used to store the JWT secret key == <!--T:229-->

<!--T:231-->
* OMQCHGSR ACTC(*ADD) KEYW(OMQJWTSECRET) KEYV('<secret key>')     

<!--T:232-->
This registry setting stores the JWT secret key, which is used to generate JWT tokens. If this key cannot be found when the JWT key generation process needs it, it is automatically generated.

<!--T:230-->
'''Since''' <br>
This setting is active in version V15.0M02 and higher.

==OMQJWTEXP - JWT expiration time in seconds == <!--T:282-->

<!--T:283-->
* OMQCHGSR ACTC(*ADD) KEYW(OMQJWTEXP) KEYV(numeric value)     

<!--T:284-->
Defines the JWT expiration time in seconds. It defauls to 43200 seconds (12 hours). 

<!--T:285-->
'''Since''' <br>
This setting is active in version V18.0M01 and higher.

==OMQSSHXFRDIR - The location of the SSH Transfer server == <!--T:233-->
 
* OMQCHGSR ACTC(*ADD)  KEYW(OMQSSHXFRDIR) KEYV('/QOpenSys/TD')     

<!--T:234-->
This registry setting is used to store the location of the SSH Transfer server. This key is installation-wide and is set automatically by the installation process.

<!--T:235-->
'''Since''' <br>
This setting is active in version V15.0M03 and higher.


==OMQWSWEBPATH - The location of the WebSmart Web Path == <!--T:241-->
 
* OMQCHGSR ACTC(*ADD)  KEYW(OMQWSWEBPATH) KEYV('http:\/\/100.64.64.40\/&OBJL\/&OBJC.pgm')     

<!--T:242-->
Stores the web path template for WebSmart. This path should be 'regex save,' meaning that special regex characters must be escaped with '\' as seen in the above example. The variables &OBJL and &OBJC can be placed in the path. See the online WebSmart manual for details.   
                                                                       
'''Since''' <br>
This setting is active in version V15.1M00 and higher.

== OMQTRACKERURL - Default Tracker URL== <!--T:243-->
This setting stores the default tracker URL. The URL is prefilled with this value when a new tracker server is created.

<!--T:244-->
'''Since'''<br>
This setting is active in version V16.0M01 and higher.

<!--T:245-->
Use the STRARM function to add the registry setting or create the registry setting from the command line like this:

<!--T:246-->
'''OMQCHGSR ACTC(*ADD) PGMN(''server'') KEYW(OMQTRACKERURL) KEYV(''server-url'')'''

<!--T:247-->
Replace ''server'' with the following keywords:

<!--T:248-->
* AZD (Azure Devops)       
* BBCLOUD (BitBucket Cloud)
* BBSERVER (BitBucket Server)   
* CW (ConnectWise)
* GITHUB     
* GITLAB    
* GRAVITY   
* JIRA      
* OTRS      
* SDP (ServiceDesk Plus)
* SERVICENOW
* ZENDESK

<!--T:249-->
This list is not exhaustive. If your tracker is not listed, don't hesitate to contact us.

==OMQDFTSRCFLEN - Default length for new source files== <!--T:250-->

<!--T:251-->
*OMQCHGSR ACTC(*ADD) KEYW(OMQDFTSRCFLEN ) KEYV('112')

<!--T:252-->
This registry setting sets the new default source file length if a new source file must be created.

<!--T:253-->
The value must be a numeric integer value.

<!--T:254-->
'''Since''' <br>
This setting is active in version V15.1M01 and higher.

==OMQUNAUTCOMPILE - Unauthorized compile command== <!--T:255-->
This setting controls the unauthorized compile overrides command during the transfer.

<!--T:256-->
*OMQCHGSR ACTC(*ADD) KEYW(OMQUNAUTCOMPILE) KEYV(*WARN)

<!--T:257-->
When set, log a warning message.

<!--T:258-->
*OMQCHGSR ACTC(*ADD) KEYW(OMQUNAUTCOMPILE) KEYV(*NONE)

<!--T:259-->
When set, unauthorized compile commands are not reported.

<!--T:260-->
*OMQCHGSR ACTC(*ADD) KEYW(OMQUNAUTCOMPILE) KEYV(*ERROR)

<!--T:261-->
When set, an error is logged and the object is not transferred to the target environment. The transfer starts the rollback procedure if rollback is required for the target environment.

<!--T:266-->
'''Since''' <br>
This setting is active in version V16.0M01 and higher.

==OMQDSTSVDTACPR - Data compression for save files== <!--T:267-->
This system-wide setting controls the compression of the savefile sent to the other machines. The value must be any of the values in the SAV commands for the DTACPR keyword. When not specified the value will be *YES.

<!--T:268-->
; Example
: OMQCHGSR ACTC(*ADD) KEYW(OMQDSTSVDTACPR) KEYV(*ZLIB)


<!--T:269-->
'''Since''' <br>
This setting is active in version V16.0M03 and higher.

==OMQDSTSVCOMPACT - Data compaction for save files== <!--T:270-->
This system-wide setting controls the compaction of the savefile sent to the other machines. The value must be any of the values in the SAV commands for the COMPACT keyword. When not specified the value will be *DEV.

<!--T:271-->
; Example
: OMQCHGSR ACTC(*ADD) KEYW(OMQDSTSVCOMPACT) KEYV(*NO)


<!--T:272-->
'''Since''' <br>
This setting is active in version V16.0M03 and higher.

==OMQOCTOORG - Link to your OCTO organization == <!--T:273-->
This system-wide setting contains the link to your OCTO organization.

<!--T:274-->
; Example
: OMQCHGSR ACTC(*ADD) KEYW(OMQOCTOORG) KEYV('https://octo.remainsoftware.com/org/remain')

<!--T:275-->
'''Since''' <br>
This setting is active in version V17.0M02 and higher.

== OMQDEPLOYCTL - Deployment control== <!--T:276-->
This registry setting determines whether the transfer is done through the Managed Deployment system or directly to the remote. If this setting is enabled, deployments are managed, otherwise, the deployment is immediate.                                                       

<!--T:277-->
; Example
: OMQCHGSR ACTC(*ADD) APPL(XMP) KEYW(OMQDEPLOYCTL) KEYV(0)                           

<!--T:278-->
Deployments are immediate.

<!--T:279-->
; Example
: OMQCHGSR ACTC(*ADD) APPL(XMP) KEYW(OMQDEPLOYCTL) KEYV(1) 

<!--T:280-->
The transfer is managed. It is placed in a staging area for further processing.

<!--T:281-->
'''Since''' <br>
This setting is active in version V17.0M03 and higher.
</translate>