Example sentences of "the dc have been [verb] " in BNC.
Next page| No | Sentence |
|---|---|
| 1 | LIFESPAN ABLE will check that the module is contained as a CONTAINS-SOURCE-OF relation in a user-supplied package ( if any ) or in the latest issue in LIFESPAN of the package through which the DC has been activated . |
| 2 | At the time of approval all modules referred to by a DC must be contained in the package through which the DC has been activated . |
| 3 | This call follows the LIFESPAN DC access rules which restricts access to a DC ( unless the optional switch has been set in the configuration file ) to the associated DC user or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 4 | This call follows the LIFESPAN DC access rules which restricts access to a DC to the associated DC user or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 5 | This call follows the LIFESPAN DC access rules which restricts access to a DC to the associated DC user or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 6 | Package through which the DC has been activated ( if appropriate ) |
| 7 | At the time of approval all modules referred to by a DC must be contained in the package through which the DC has been activated . |
| 8 | No special LIFESPAN privileges are required to use this option but you must be the user associated with the DC or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 9 | No special LIFESPAN privileges are required to use this option , but you must be the user associated with the DC or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 10 | No special LIFESPAN privileges are required to use this option but the DC must have been submitted , and you must be the user associated with the DC or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 11 | No special LIFESPAN privileges are required to use this option but the DC must have been submitted , and you must be the user associated with the DC or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 12 | The DC then changes state to ACTIVE , thus allowing the modules to which it refers to be updated , using the package through which the DC has been activated . |
| 13 | Option 2.8.1 , View One DC , enables the user to view the details of a specific DC , However the user must be associated with the DC or an interested user ( i.e. the manager of any modules on the DC or the manager of packages containing one or more of these modules ) or , if applicable , the nominated approver of the package via which the DC has been activated . |
| 14 | This may be necessary when , for instance , the DC has been activated through the wrong package . |
| 15 | identifier of each SPR to which the DC has been related |
| 16 | Once the DC has been created you should use option 2.1.2 — Update DC , to add further details to the DC and then option 2.1.3 — Submit DC , to submit the DC for assessment by other affected users . |
| 17 | Note also that the priority field defaults to Routine , if this is the first time the DC has been updated . |
| 18 | You should ensure that the DC has been submitted for agreement using option 2.1.3 — Submit DC . |
| 19 | The DC has been associated with a package . |