MDWFARFP - MDWorkflow Acceptance for RFP command
MDCMS is delivered with a command-based API that provides for automated updates to the MDWorkflow Test Status for RFPs.
An RFP will be considered if already installed with an "ongoing" test status.
The MDCMS command is named MDWFARFP and is located in library MDCMS*.
All MDWFARFP API transactions are logged to file MDCMS/MDDWFAR.
MDWFARFP Parameter Table
| Name | Type | Length | Description |
|---|---|---|---|
| Name | Type | Length | Description |
| GRP | CHAR | 10 | The User Group ID of the user to update the Workflow test status for RFPs. This is a required parameter |
| USER | CHAR | 10 | The specific user in the Group to attribute the acceptance status to. The user must belong to the group that is involved with testing project(s) impacted by the RFPs to accept/reject. *USER = The user id of the job that invokes this command will be used. |
| ACT | CHAR | 7 | The action to carry out for each qualified project in each qualified RFP, based on the passed parameter values. *ACCEPT = Set the test status to accepted *REJECT = Set the test status to rejected *INPROG = Set the test status to In Progress *UNDO = Reset the provisional test status |
| CMNT | CHAR | 120 | A comment to apply to the status update for informational purposes |
| CONF | CHAR | 4 | Whether or not to set the RFP test status to confirmed, if all impacted projects for the RFP have been provisionally accepted or if at least one of the impacted projects for the RFP has been provisionally rejected. *NO = This command will only set the provisional status. Final confirmation will occur later. *YES = Set the RFP test status to confirmed and carry out any post-confirmation steps. |
| APPL | CHAR | 6 | Application Code *ALL = The RFPs to accept/reject can belong to any application |
| RFP | INTEGER | 7 | Specific RFP Number - if left blank, then the range of RFP numbers will be considered |
| RFPT | CHAR | 8 | Specific RFP Type - the type of specific RFP number passed in parameter RFP. *CURRENT = the current number for an RFP *FROM = The RFP number refers to the RFP installed into the prior level, which then automatically generated the RFP with a different number to be accepted. *ORIG = Each RFP to be accepted originated from the specified RFP number, which was installed into the initial level for a chain of migrations across systems. |
| FLVL | INTEGER | 3 | From Level - the lower limit for the level number to accept/reject |
| TLVL | INTEGER | 3 | To Level - the upper limit for the level number to accept/reject |
| FRFP | INTEGER | 7 | From RFP - the minimum RFP number to accept/reject |
| TRFP | INTEGER | 7 | To RFP - the maximum RFP number to accept/reject |
| PROJ | CHAR | 12 | Project - specifies the Project that must be assigned to one or more of the objects in an RFP for that RFP to be considered. If blank, then the RFPs won't be filtered by a project and the test status for all projects in the RFP will be updated. If not blank, the RFP must impact the Project and the test status will only be applied to that project. |
| TASK | INTEGER | 7 | Task - Specifies the Project Task that must be assigned to one or more of the objects in an RFP for that RFP to be considered. If TASK > 0, then the Project ID must also be passed. |
| STSK | INTEGER | 7 | Subtask - Specifies the Project Subtask that must be assigned to one or more of the objects in an RFP for that RFP to be considered. If STSK > 0, then the Project ID and Project Task must also be passed. |
| PIPE | CHAR | 10 | Pipeline Filter - Specifies the Pipeline Server ID of a Pipeline TraceKey request. This value is required if a value for TRCKEY is provided. If values for PIPE/TRCKEY are provided, an RFP will only be included if it contains an object request of type *PIPE with the Pipeline server ID and TraceKey in the object name. |
| TRCKEY | CHAR | 128 | Pipeline TraceKey Filter - Specifies the Pipeline TraceKey of a Pipeline TraceKey request. This value is required if a value for PIPE is provided. If values for PIPE/TRCKEY are provided, an RFP will only be included if it contains an object request of type *PIPE with the Pipeline server ID and TraceKey in the object name. |
| ENV | CHAR | 5 | Specifies the MDCMS environment that should be used to place the Request. The ID correlates to the suffix of the MDCMS library name. For example, TEST correlates to library MDCMSTEST. *DFT = The default environment will be used. This correlates to library MDCMS. *SAME = the current instance, in case the library list is already set |
| EMSG | CHAR | 7 | Specifies if and to what extent an exception message should be returned to the calling program. An exception message occurs when an input parameter value is invalid, causing the addition of the request to fail. *DIAG = A diagnostic message will be placed in the calling program's message queue in the following format: MDWFARFP Exception. Object= *ESCAPE = The full diagnostic message as described above will be placed in the calling program's message queue and then followed by escape message CPF0001 for which the calling program can monitor. *NONE = An exception message will not be returned to the calling program's message queue. |