Attributes for process definitions on IBM i
This topic summarizes the attributes that are specific to process definitions. The attributes are described in alphabetical order.
Note: The names of the attributes shown are the names used with the MQINQ and MQSET calls. When MQSC commands are used to define, alter, or display attributes, alternative short names are used; see MQSC commands for details.Attribute descriptions
A process-definition object has the following attributes:
- AlterationDate (12-byte character string)
-
Date when definition was last changed.
This is the date when the definition was last changed. The format of the date is YYYY-MM-DD, padded with two trailing blanks to make the length 12 bytes.
To determine the value of this attribute, use the CAALTD selector with the MQINQ call. The length of this attribute is given by LNDATE.
- AlterationTime (8-byte character string)
-
Time when definition was last changed.
This is the time when the definition was last changed. The format of the time is HH.MM.SS.
To determine the value of this attribute, use the CAALTT selector with the MQINQ call. The length of this attribute is given by LNTIME.
- ApplId (256-byte character string)
-
Application identifier.
This is a character string that identifies the application to be started. This information is for use by a trigger-monitor application that processes messages on the initiation queue; the information is sent to the initiation queue as part of the trigger message.
The meaning of ApplId is determined by the trigger-monitor application. The trigger monitor provided by IBM MQ requires ApplId to be the name of an executable program.
The character string cannot contain any nulls. It is padded to the right with blanks if necessary.
To determine the value of this attribute, use the CAAPPI selector with the MQINQ call. The length of this attribute is given by LNPROA.
- ApplType (10-digit signed integer)
-
Application type.
This identifies the nature of the program to be started in response to the receipt of a trigger message. This information is for use by a trigger-monitor application that processes messages on the initiation queue; the information is sent to the initiation queue as part of the trigger message.
ApplType can have any value. We can use the following values for standard types; user-defined application types are restricted to values in the range ATUFST through ATULST:- ATCICS
- CICS transaction.
- AT400
- IBM i application.
- ATUFST
- Lowest value for user-defined application type.
- ATULST
- Highest value for user-defined application type.
To determine the value of this attribute, use the IAAPPT selector with the MQINQ call.
- EnvData (128-byte character string)
-
Environment data.
This is a character string that contains environment-related information pertaining to the application to be started. This information is for use by a trigger-monitor application that processes messages on the initiation queue; the information is sent to the initiation queue as part of the trigger message.
The meaning of EnvData is determined by the trigger-monitor application. The trigger monitor provided by IBM MQ appends EnvData to the parameter list passed to the started application. The parameter list consists of the MQTMC2 structure, followed by one blank, followed by EnvData with trailing blanks removed.
The character string cannot contain any nulls. It is padded to the right with blanks if necessary.
To determine the value of this attribute, use the CAENVD selector with the MQINQ call. The length of this attribute is given by LNPROE.
- ProcessDesc (64-byte character string)
-
Process description.
This is a field that can be used for descriptive commentary. The content of the field is of no significance to the queue manager, but the queue manager might require that the field contain only characters that can be displayed. It cannot contain any null characters; if necessary, it is padded to the right with blanks. In a DBCS installation, the field can contain DBCS characters (subject to a maximum field length of 64 bytes).
Note: If this field contains characters that are not in the queue manager's character set (as defined by the CodedCharSetId queue manager attribute), those characters might be translated incorrectly if this field is sent to another queue manager.To determine the value of this attribute, use the CAPROD selector with the MQINQ call.
The length of this attribute is given by LNPROD.
- ProcessName (48-byte character string)
-
Process name.
This is the name of a process definition that is defined on the local queue manager.
Each process definition has a name that is different from the names of other process definitions belonging to the queue manager. But the name of the process definition can be the same as the names of other queue manager objects of different types (for example, queues).
To determine the value of this attribute, use the CAPRON selector with the MQINQ call.
The length of this attribute is given by LNPRON.
- UserData (128-byte character string)
-
User data.
This is a character string that contains user information pertaining to the application to be started. This information is for use by a trigger-monitor application that processes messages on the initiation queue, or the application which is started by the trigger monitor. The information is sent to the initiation queue as part of the trigger message.
The meaning of UserData is determined by the trigger-monitor application. The trigger monitor provided by IBM MQ 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 EnvData with trailing blanks removed.
The character string cannot contain any nulls. It is padded to the right with blanks if necessary.
To determine the value of this attribute, use the CAUSRD selector with the MQINQ call. The length of this attribute is given by LNPROU.
Parent topic: Attributes of objects on IBM i