MDCRTSCO - Create MDCMS Send RFP for Changed Objects command
Command MDCRTSCO in library MDCMS(env) provides the ability to create an RFP in the Send list containing all objects in a specific library that have been created or changed since a specified minimum date. If the date is unspecified, all objects in the library will be considered for sending. In order for an send request to be created for an object, an attribute must exist for the given level with the named library defined as the target object library for the attribute.
If successful, the RFP will be available in the Send listing ready to be sent.
Each MDCRTSCO transaction is logged in MDCMS/MDDCSCO. In addition to displaying the input parameters, the log also shows the generated RFP Number, number of requested objects and, if an exception occurs, a short description of the error.
Restrictions:
- The user entered for parameter USER must have MDSEC authority to Edit RFPs in Send List (code 48) for the entered Application Level as well as authority to use the Project (and Task/Subtask, if entered). .
- The user performing MDCRTSCO must have at least *USE authority for the USER parameter profile.
- The user performing MDCRTSCO must have been granted authority to execute the command in the MDSEC Command Security listing.
MDCRTSCO Parameters
| Name | Type | Length | Description |
|---|---|---|---|
| Name | Type | Length | Description |
| APPL | CHAR | 6 | Application to send from |
| LVL | INTEGER | 3 | Application Level to send from |
| OLIB | CHAR | 10 | An Object Library defined for at least 1 attribute for the given application and level. |
| RFPD | CHAR | 160 | The description to be placed on the RFP in the Send List |
| PROJ | CHAR | 12 | A valid Project ID to be applied to each object |
| TASK | INTEGER | 7 | The optional Task Number within the Project to be applied to each object |
| STSK | INTEGER | 7 | The optional Subtask Number within the Project Task to be applied to each object |
| DATE | INTEGER | 8 | The minimum date that an object was created or changed (based on parameter DATT). Leave 0 if no minimum. If entered, the value must be in format YYYYMMDD. |
| DATT | CHAR | 7 | The types of object dates to compare to the minimum date provided in parameter DATE. *CREATE only the creation date for the object is considered *CHANGE The last change date for the object is considered. If unchanged, the create date is considered. |
| USER | CHAR | 10 | The User ID to apply to the Send RFP and its objects *USER - the user of the job invoking the command |
| ENV | CHAR | 4 | Specifies the MDCMS environment that should be used when running the command. 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. |
| VREF | CHAR | 20 | Specifies the Vendor Generated Identifier in order for an external process to easily identify the transaction record in the MDDASOG table. Any value up to 20 characters in length can be used. |
| 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. |