Change Solution Description (OMQCHGSO)
This Application Program Interface command enables you to
manipulate the OMS database. This can be done from a command line
or from within your own programs. The command enables you to perform
all allowed actions on a solution.
Error Messages
| Message Identifier | Text | Cause | Recovery | Severity |
| CPF0006 | Errors occurred in command. | | | |
| OMQ6001 | Application code &1 does not exist. | You have entered an application code which does not exist. | Enter a valid application code and try your request again. | 10 |
| OMQ5007 | Environment code &1 does not exist in application &2 | Environment &1 does not exist in application &2. | Correct the errors and try your request again. | 10 |
| OMQ101D | IFS-object &2 cannot belong to environment &1. | IFS-Object &3 does not start with a directory that is part of environment &1 | Specify a different directory and try your request again | 30 |
| OMQ100C | Object &2/&1 type &3 not found. | The requested action for object &2/&1 type &3 could not be done because the object was not found. | Add the object and try your request again. If type has the value *IFSOBJ, see the previous messages to determine why the IFS-object could not be found. | 30 |
| OMQ1009 | Object library &3 is not a part of environment &2 in application &1 | Your request has been denied because the object library &3 does not belong to environment &2 in application &1 | Change the object library to a library which belongs to environment &2 in application &1 or change the application- and environment code. | 20 |
| OMQ400E | Solution &3, type &4 not found in fix &2, application &1 | Your request for solution &3, type &4 and detail &5 in fix &2 of application &1 has not been processed because it was not found | Change the parameters and try your request again. | 10 |
Parameters
Action code (ACTC)
Specify the action to be performed on the solution. The possible
values are:
*CHANGE
Use this action code to change one or more solution attributes.
*CONNECT
Use this action code to connect an object to a fix. When an
object is connected to a fix, it is referred to as a solution.
*CLOSE
Use this action code to close the object database and to
perform last record processing. This option enables you to keep
the interface to the solution database open until you
explicitly close it. This will make the interface considerably
faster.
*DISCONNECT
Use this action code to disconnect the object from the fix.
*LOCK
When an object is connected to a fix, it cannot be connected
again unless the already connected occurrence is locked. Use
this action code to lock a solution. When a solution is locked
it cannot be transferred through the maintenance cycle.
*UNLOCK
Use this action code to remove a lock from a solution. This can
only be done if the object is not connected to another fix in
an unlocked state.
Note: This is not entirely true. If you use FRCI(*YES),
then other active occurrences of the object will be locked.
Application (APPL)
Specify the application code of the fix to which the object must be
connected.
Fix number (FIX)
Specify the fix to which the object must be connected.
Object code (OBJC)
Specify the object which must be connected to the fix.
*IFSOBJ
Use this value if you want to specify an object from the
integrated file system (IFS) instead of the normal OS/400
library structure.
character-value
Specify the object code of the object.
Object type (OBJT)
Specify the type of the object which must be connected to the fix.
Object library (OBJL)
Specify the library of the object. The possible values are:
*LASTVRS
Use this value to indicate that OMS must connect the last
version of the object to the fix. OMS will search its database
to find the correct library. This value is recommended.
library-name
Specify the name of the library where the object
to-be-connected resides.
IFS-Object code (IFSOBJ)
Specify the name of the object (e.g. file or directory) to be used.
The full name of the object is a concatenation of the value
specified in the IDRC-parameter followed by the value in this
(IFSOBJ) parameter.
*OBJC
Use this value if you want to specify an object from the OS/400
library structure instead of the integrated file system.
Directory code (IDRC)
Specify the directory containing the object specified on the
IFSOBJ-parameter. You cannot specify the directory QSYS.LIB or any
directory below QSYS.LIB
Environment code (ENVC)
Specify the environment code of the object. This attribute is used
to specify some special values for the solution. The possible
values are:
*OBJD
The environment is retrieved from the object's object
description. This value is not allowed if a new object is
connected. A new object is an object which is not yet known to
OMS.
*ANY
Use this special value to give the special status *ANY to the
object. The *ANY status is a virtual environment which is equal
to the actual environment of the object. The *ANY environment
is used to allow a quick transport of objects to the
development environment and is created because an object
transfer cannot handle objects originating from different
environments.
The only transfer possible from the *ANY environment is to the
development environment. This enables a mass connection and
transfer of related objects which are currently not in the same
environment.
environment-code
Enter the environment code to be used for the connected object.
Please note that when an object is connected, the values from
the database are used before the environment used here. If OMS
cannot determine the environment (e.g. a new object is
connected in a library which is used in more than one
environment) then a user specified environment code is used.
Detail code (DTLC)
When connecting a message or a source member the name of this
detail must also be specified. The possible values are:
*NONE
No detail is involved.
detail-code
Specify the name of the message or source member.
Route Code (ROTC)
Specify the route in which this solution resides. The route code
only needs to be specified if you are doing something other then
connect.
*ONLY
There is only one object with this name and type in the solution.
route code
Specify the name of the route code where this solution resides.
See the description of the route code. for more information.
Route Path Extension Code (PTXC)
Specify the path extension code of this solution. This code only
needs to be specified if you are doing something other then
connect.
*ONLY
There is only one object with this name and type in the
solution.
path extension code
Specify the path extension code where this solution resides.
See the description of the path extension code for more
information.
Solution status (STAT)
Specify the status assigned to the solution. The possible values
are:
*ACT
Connect this object as an active solution. The object can only
be connected once as an active solution.
*LOCK
Connect this object to the fix and lock it in the process. This
means that the same object can be connected to another fix.
*CMP
The object can be completed when it is in the highest
environment. You can use this status to build a solution
history.
Solution type (SOLT)
The solution type indicates what actions are planned on the
connected object. The possible values are:
*SAME
Indicates that the solution type does not change. This value
defaults to *CHANGE when an object is first connected connected
to a fix.
*CHANGE
Use this value to indicate an object on which maintenance is to
be performed. The connected source is also transferred through
the maintenance cycle and normal version numbering is executed
on the object.
*COMPILE
This solution type has not yet been implemented.
*COPY
This solution type has not yet been implemented.
*TERMINATE
Use this solution type to indicate an object which has reached
the end of its life. If this solution is transferred through
the maintenance cycle and it finds one or more copies of itself
then these copies are deleted. The last step is the deletion of
the object in the production environment.
Override code (OVRC)
If an object is transferred through the maintenance cycle, it is
possible that it is overtaking a copy of itself which has a locked
connection to another fix. In this case the solutions merge into
one single solution but connected to two or more different fixes.
possible to connect the same object to more than one fix without
locking one of the solutions. However, there is only one connection
allowed to be transferred. This connection is generally referred to
as the leader. The other solutions are called followers.
When the leader solution is transferred all followers will follow.
This is easy to understand if you see that it is actually the same
object which is transferred. The possible values are:
*SAME
Indicates that the override code does not change. If an object
is first connected to a fix the solution is not a follower or a
leader, not even when it is already connected to another fix.
In this case an error is reported to the calling program
stating that the object is already connected to another fix.
*LEAD
If the object you are about to connect is already connected to
another fix, this value will cause it to be connected as a
leader. The objects already connected to other fixes will
become followers.
*FOLLOW
If the object you are about to connect is already connected to
another fix, this value will cause it to be connected as a
follower. The object already connected to the other fix will
become the leader.
Source processing (SRCP)
Indicate if the source also has to be transferred through the
maintenance cycle. The possible values are:
*SAME
The source processing does not change. If the object is
connected to the fix the source processing will become *YES if
the object has a related source (found or not found) and *NONE
if the object does not have a source (like a data area). Future
solution types may cause the source processing to depend on it.
*YES
If the object is transferred through the maintenance cycle, so
will the related source.
*NO
The object is related to a source, but the source is not
transferred through the maintenance cycle.
*NONE
The object is not related to a source.
Close API indicator (EOPI)
Specify if the API has to close all files and free storage upon
completion of the requested action. The possible values are:
*YES
The files are closed and storage is freed by the API upon
completion of the requested action. Subsequent actions must
open the necessary files and programs again.
*NO
The state of the API was left when the requested action was
completed. Files remain open and status updates are postponed.
Subsequent calls to the API are considerably faster and storage
is not freed.
Note: Note that the last action of a series should close
the API in order to close spooled files and do status
processing.
Force active indicator (FRCI)
Use this element to force the object to become an active solution.
Since an object may only be active to one fix at the time, this
would indicate that other solutions must be locked before the
requested object can be connected. The possible values are:
*NO
The object is only connected to the fix if it is not an active
solution to another fix. If it is, the object cannot be
connected and an error is returned to the calling program.
*YES
The object is connected to the fix and all other occurrences of
the object are locked.
New object indicator (NEWI)
Specify if the object is already known to OMS or is still in the
construction stage. The possible values are:
*NO
Before the object is connected to a fix it is checked to see if
it is already loaded into the OMS database. If OMS cannot find
the object then an error is reported.
*YES
The object is connected to the fix even if it is does not exist
in the OMS database. The name is checked to see if the object
name is already in use (this is not allowed.) If the object is
connected, the new name cannot be used for other objects. Use
this value to reserve object names before they are really
created.
Include 4GL generated objects (GENI)
Use this value if a 4GL object is to be connected to a fix. The
possible values are:
*NO
Connect the 4GL object, but not the generated objects.
*YES
Connect the 4GL object and try to find the generated objects.
They are also connected to the fix if they are found.
Object attribute (OBJA)
Enter the object attribute if a new object is connected.
Object class (OCLS)
Enter the object class for the new object. The possible values are:
*SAME
The value of the element does not change. The class is
determined by OMS if *SAME is used when the object is first
added.
*OS400
The object is an OS/400 object.
*GL4
The object is an object from a fourth generation language.
*HFSOBJ
The object is an object from an hierarchical file system. This
can be a PC object or a document from an AS/400 folder.
*IFSOBJ
The object is an object from the Integrated File System.
