MDRCVIFS - Receive RFP/Settings from IFS command
When RFPs or settings are received via MDFTP (MDF), GoAnywhere™ (GOA) or a manual Save File (SFF) deployment from another system, they must be staged in IFS Folder /MDCMS/SEND/(instance).
If a DDM connection is defined in MDCMS between the sending system and the receiving system, and MDPUSH or MDPULL is also defined to run, then MDRCVIFS isn't necessary unless for SFF.
When for SFF or DDM isn't available, then Service MDRCVIFS - MDCMS Receive RFPs in IFS is used to check for, and process, those RFP files. MDRCVIFS can be started from the Service List in the MDCMS Setup Menu, but is recommended to be started from a scheduled job using command MDRCVIFS.
MDRCVIFS Parameters
| Option / Field | Description |
|---|---|
| Environment ID | The name of the MDCMS instance (or suffix) - *DFT refers to MDCMS being used in library MDCMS. For a different library suffix, this would be entered for the environment ID. |
| Submit Job | *YES - a job named MDRIFS(env) will be submitted to the entered Job Queue *NO - the MDRCVIFS process will run within the current job |
| Job Queue | *DFT - submit to the queue defined for the MDRCVIFS service *JOBD - submit to the default queue for the running job profile The name of the job queue to submit MDRCVIFS to |
| Job Queue Library | The library of the job queue to submit MDRCVIFS to or *LIBL if the job queue is located in the current library list |
| Delay between Checks | *DFT - the default number of seconds between checking the IFS folder for candidates that is defined for the MDRCVIFS service The number of seconds to wait between checks (1-9999) |
| Time of Day to auto-end Job | *DFT - end at the time defined for the MDRCVIFS service *NEVER - the MDRCVIFS job shouldn't end automatically - it should run until the job is forcibly ended. A specific time to end in format HH:MM:SS |