MDDELRFP - RFP Deletion command
MDCMS is delivered with a command-based API that allows an external CL program, such as a program within End-of-Day, to delete (reset) RFPs. If the RFP has already been installed, or a job is currently compiling or installing the RFP, it will not be considered by the API.
The MDCMS command is named MDDELRFP and is located in library MDCMS*.
All MDDELRFP API transactions are logged to file MDCMS/MDDDRFP.
MDDELRFP Parameter Table
| Name | Type | Length | Description |
|---|---|---|---|
| Name | Type | Length | Description |
| APPL | CHAR | 6 | Application Code *ALL = The RFPs to delete 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 deleted. *ORIG = Each RFP to be deleted 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 delete from |
| TLVL | INTEGER | 3 | To Level - the upper limit for the level number to delete from |
| FRFP | INTEGER | 7 | From RFP - the minimum RFP number to be deleted |
| TRFP | INTEGER | 7 | To RFP - the maximum RFP number to be deleted |
| 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. |
| 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. |
| ENV | CHAR | 4 | 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. |
| 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: MDDELRFP 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. |