MDSNDRFP - Send RFPs command
Command MDSNDRFP in library MDCMS(env) provides the ability to schedule or programmatically send open RFPs to levels on target systems.
Restrictions:
- The RFP must be open in the send list and none of the objects in the RFP may be waiting for MDWorkflow acceptance or be blocked by a Status Boundary. The RFP will only be sent to unignored target levels where the installation hasn't completed yet.
- As a safety precaution, at least one of the following parameters must be passed with a value other than the default: APPL, FLVL, TLVL, FRFP, TRFP, LOC, LOCGRP, FTLVL, TTLVL or PROJ.
MDSNDRFP Parameters
| Name | Type | Length | Description |
|---|---|---|---|
| Name | Type | Length | Description |
| APPL | CHAR | 6 | Application Code or *ALL for any application |
| FLVL | INTEGER | 3 | Minimum Application Level to consider |
| TLVL | INTEGER | 3 | Maximum Application Level to consider |
| FRFP | INTEGER | 7 | Minimum RFP Number to consider |
| TRFP | INTEGER | 7 | Maximum RFP Number to consider |
| LOC | CHAR | 10 | The Location to send the RFP to *ALLDFT = All target locations defined for the RFP's level that have the Default to Send property set to Y=Yes or M=Yes for Manual Send. *ALL = All target locations defined for the RFP's level |
| LOCGRP | CHAR | 10 | The Location Group to send the RFP to. MDCMS will only send to locations that meet the value for parameter LOC and LOCGRP. *ALL = the locations to send to aren't limited to a specific group |
| FTLVL | INTEGER | 3 | The minimum application level on the target system to send to |
| TTLVL | INTEGER | 3 | The maximum application level on the target system to send to |
| MERGE | CHAR | 4 | Specifies if, in the case of multiple RFPs for the same local level, they should be merged into a single RFP before sending. The merge will occur for each level and result in the lowest RFP number for the level being the container for all of the impacted objects. *NO = each RFP will be sent separately *YES = All RFPs for the same application level will be merged into the lowest RFP so that a single RFP is sent to the target locations for that level. |
| RESEND | CHAR | 4 | Specifies if an RFP should be sent to a target level, if it has already been sent to that level. If the installation completed for the target level, then the RFP won't be resent. *NO = a target level will be omitted, if the RFP has already been sent to it *YES = the RFP will be resent to a target level, even if it had been sent before, as long as the installation hasn't completed on the target level. |
| INSDT | CHAR | 8 | Specifies the date that the RFP should be scheduled to be installed on the target level. It will be sent immediately, and then, if the validation, compile and approval phase is ok, will be installed at the given date and time, if the target level is set to install automatically. *CURRENT = the installation of the RFP will occur on the same date as the approval is given. If the installation time is set to *IMMED, the installation will occur immediately. Otherwise, specify a date in format YYYYMMDD |
| INSTM | CHAR | 6 | Specifies the time of day that the RFP should be scheduled to be installed on the target level. It will be sent immediately, and then, if the validation, compile and approval phase is ok, will be installed at the given date and time, if the target level is set to install automatically. *IMMED = the installation of the RFP will occur as soon as approval is given for the RFP on the target. Otherwise, specify a time in format HHMMSS |
| TZONE | CHAR | 7 | Specifies if the scheduled install date/time is based on the time zone of the sending system or the time zone of the target system. *TARGET = the installation date/time is based on the time zone of the target system. *LOCAL = the installation date/time is based on the time zone of the local sending system. |
| PROJ | CHAR | 12 | Project Filter - only send RFP if one or more Objects in the RFP are requested for the Project |
| TASK | INTEGER | 7 | Task Filter - only send RFP if one or more Objects in the RFP are requested for the Project Task |
| STSK | INTEGER | 7 | Subtask Filter - only send RFP if one or more Objects in the RFP are requested for the Project Subtask |
| 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. |
| BATCH | CHAR | 6 | Specifies if the target levels are part of a batch send, so that a single process will send to several different targets at the same time rather than each one individually. This provides a way to avoid conflicts when trying to send to multiple targets for the same RFP using multiple calls to this command. *ONLY - The send should be invoked immediately without batching multiple calls to this command together. *FIRST - Any selected targets in this call to MDSNDRFP are to be placed in an initialized batch list per RFP. This should be the value used for the first MDSNDRFP call for a batch. *ADD - Any selected targets in this call to MDSNDRFP will be appended to an existing list per RFP. If the list for a specific RFP doesn't exist yet, it will be started. *LAST - Any selected targets in this call to MDSNDRFP will be appended to an existing list per RFP. If the list for a specific RFP doesn't exist yet, it will be started. The send for the entire batch list per RFP will then be immediately processed. This must be the value used for the last MDSNDRFP call for a batch. |
| 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: MDSBMRFP 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. |