The parameter descriptions also apply to the ALTER PROCESS command, with the following exceptions:
The name must not be the same as any other process definition currently defined on this queue manager (unless REPLACE is specified).
For a CICS application this is a CICS transaction ID, and for an IMS(TM) application it is an IMS transaction ID.
On z/OS, for distributed queuing using CICS it must be "CKSG", and for distributed queuing without CICS(R), it must be "CSQX START".
For certain values in the system range, a parameter from the following list can be specified instead of a numeric value:
Only application types (other than user-defined types) that are supported on the platform at which the command is executed should be used:
CMDSCOPE must be blank, or the local queue manager, if QSGDISP is set to GROUP.
You can specify a queue manager name other than the queue manager on which it was entered, only if you are using a shared queue environment and if the command server is enabled.
It should contain only displayable characters. The maximum length is 64 characters. In a DBCS installation, it can contain DBCS characters (subject to a maximum length of 64 bytes).
The meaning of ENVRDATA is determined by the trigger-monitor application. The trigger monitor provided by WebSphere MQ appends ENVRDATA to the parameter list passed to the started application. The parameter list consists of the MQTMC2 structure, followed by one blank, followed by ENVRDATA with trailing blanks removed.
SERVICENAME=servname,SERVICESTEP=stepnamewhere:
This parameter applies only to the DEFINE PROCESS command.
If this field is not filled in, and you do not complete the parameter fields related to the command, the values are taken from the default definition for this object.
This is equivalent to specifying:
LIKE(SYSTEM.DEFAULT.PROCESS)
A default definition for each object type is provided, but these can be altered by the installation to the default values required. See Rules for naming WebSphere MQ objects.
On z/OS, the queue manager searches page set zero for an object with the name you specify and a disposition of QMGR or COPY. The disposition of the LIKE object is not copied to the object you are defining.
Specifies the disposition of the object to which you are applying the command (that is, where it is defined and how it behaves).
QSGDISP | ALTER | DEFINE |
---|---|---|
COPY | The object definition resides on the page set of the queue manager that executes the command. The object was defined using a command that had the parameters QSGDISP(COPY). Any object residing in the shared repository, or any object defined using a command that had the parameters QSGDISP(QMGR), is not affected by this command. | The object is defined on the page set of the queue manager that executes the command using the QSGDISP(GROUP) object of the same name as the 'LIKE' object. |
GROUP | The object definition resides in the shared repository.
The object was defined using a command that had the parameters QSGDISP(GROUP).
Any object residing on the page set of the queue manager that executes the
command (except a local copy of the object) is not affected by this command.
If the command is successful, the following command is generated and sent to all active queue managers in the queue-sharing group to attempt to refresh local copies on page set zero: DEFINE PROCESS(process-name) REPLACE QSGDISP(COPY)The ALTER for the group object takes effect regardless of whether the generated command with QSGDISP(COPY) fails. |
The object definition resides in the shared repository.
This is allowed only if the queue manager is in a queue-sharing group.
If the definition is successful, the following command is generated and sent to all active queue managers in the queue-sharing group to attempt to make or refresh local copies on page set zero: DEFINE PROCESS(process-name) REPLACE QSGDISP(COPY)The DEFINE for the group object takes effect regardless of whether the generated command with QSGDISP(COPY) fails. |
PRIVATE | The object resides on the page set of the queue manager
that executes the command, and was defined with QSGDISP(QMGR) or QSGDISP(COPY).
Any object residing in the shared repository is unaffected. |
Not permitted. |
QMGR | The object definition resides on the page set of the queue
manager that executes the command. The object was defined using a command
that had the parameters QSGDISP(QMGR). Any object residing in the shared repository,
or any local copy of such an object, is not affected by this command.
This is the default value. |
The object is defined on the page set of the queue manager
that executes the command.
This is the default value. |
This parameter applies only to the DEFINE PROCESS command.
The meaning of USERDATA is determined by the trigger-monitor application. The trigger monitor provided by WebSphere MQ simply passes USERDATA to the started application as part of the parameter list. The parameter list consists of the MQTMC2 structure (containing USERDATA), followed by one blank, followed by ENVRDATA with trailing blanks removed.
For WebSphere MQ message channel agents, the format of this field is a channel name of up to 20 characters. See the WebSphere MQ Intercommunication manual for information about what these need as APPLICID.
On Compaq NSK, a character string containing spaces must be enclosed in double quotation marks.
Notices |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
csqzaj1045 |