LEADER 01333nam--2200397---450- 001 990005910080203316 005 20131120125100.0 010 $a88-14-18138-1 035 $a000591008 035 $aUSA01000591008 035 $a(ALEPH)000591008USA01 035 $a000591008 100 $a20131120d2013----km-y0itay50------ba 101 $aita 102 $aIT 105 $a||||||||001yy 200 1 $a<> contratti a distanza nel codice del consumo e nella direttiva 2011/83/UE$everso un codice europeo del consumo$fFabio Bravo$gpresentazione di Guido Alpa 210 $aMilano$cGiuffrè$d2013 215 $aXVI, 345 p.$d24 cm 225 2 $aTemi di diritto privato e di diritto pubblico 410 0$12001$aTemi di diritto privato e di diritto pubblico 454 1$12001 461 1$1001-------$12001 606 0 $aConsumatori$xTutela$xDiritto comunitario$2BNCF 676 $a343.24071 700 1$aBRAVO,$bFabio$0267654 702 1$aALPA,$bGuido 801 0$aIT$bsalbc$gISBD 912 $a990005910080203316 951 $aXXIII.4.B. 299$b78454 G.$cXXIII.4.B.$d00344607 959 $aBK 969 $aGIU 979 $aFIORELLA$b90$c20131120$lUSA01$h1207 979 $aFIORELLA$b90$c20131120$lUSA01$h1251 996 $aContratti a distanza nel codice del consumo e nella direttiva 2011$9825929 997 $aUNISA LEADER 01157nas 2200349-- 450 001 9910145226903321 005 20170626064720.7 035 $a(CKB)991042745971502 035 $a(CONSER)sn-84011367- 035 $a(EXLCZ)99991042745971502 100 $a20790124a19779999 -b- a 101 0 $aeng 200 00$aMosquito control research, annual report 210 $aDavis$cUniversity of California 215 $a1 online resource 300 $aTitle from cover. 311 08$aPrint version: Mosquito control research, annual report. 0886-6309 (DLC)sn 84011367 (OCoLC)4581789 531 0 $aMosq. control res. annu. rep. 606 $aMosquitoes$xControl$zCalifornia$vPeriodicals 606 $aMosquitoes$xControl$2fast$3(OCoLC)fst01026776 607 $aCalifornia$2fast 608 $aElectronic journals. 608 $aPeriodicals.$2fast 615 0$aMosquitoes$xControl 615 7$aMosquitoes$xControl. 676 $a595 712 02$aUniversity of California, Davis. 906 $aJOURNAL 912 $a9910145226903321 920 $aexl_impl conversion 996 $aMosquito control research, annual report$92008181 997 $aUNINA LEADER 03595nam 2200589Ia 450 001 9910783105003321 005 20200520144314.0 035 $a(CKB)1000000000023255 035 $a(SSID)ssj0000943209 035 $a(PQKBManifestationID)11593667 035 $a(PQKBTitleCode)TC0000943209 035 $a(PQKBWorkID)10975318 035 $a(PQKB)10264899 035 $a(Au-PeEL)EBL3306701 035 $a(CaPaEBR)ebr10112788 035 $a(OCoLC)80245797 035 $a(CaSebORM)0738429007 035 $a(MiAaPQ)EBC3306701 035 $a(EXLCZ)991000000000023255 100 $a20041111d2003 uy 0 101 0 $aeng 135 $aurcn||||||||| 181 $ctxt 182 $cc 183 $acr 200 00$aSAP on DB2 Universal Database for OS/390 and z/OS$b[electronic resource] $eMultiple Components in One Database (MCOD) /$fFlorence Dubois ... [et al.] 205 $a1st ed. 210 $aWhite Plains, N.Y. $cIBM$dc2003 215 $axvi, 279 p. $cill 225 1 $aRedbooks 300 $a"This edition applies to SAP Basis Release 4.6C, 4.6D, 6.10, and 6.20, as well as all SAP products based on these SAP Basis Releases, for use with IBM DB2 Universal Database for OS/390 and z/OS." 300 $a"Hands-on scenarios to merge SAP components into an MCOD landscape. How to clone one SAP component using the Control Center. Recovery considerations in an MCOD landscape." 311 $a0-7384-2900-7 320 $aIncludes bibliographical references and index." 330 $aThe Multiple Components in One Database (MCOD) feature of SAP enables a reduction in the number of DB2 systems that need to be installed and maintained. This significantly simplifies overall database administration and is considered one of the major DB2 competitive advantages. This IBM Redbooks publication will help systems administrators, database administrators, managers, and operation staff to plan, implement, and administer an SAP MCOD landscape with DB2 Universal Database (UDB) for OS/390 and z/OS as the database management system. We describe how to merge existing systems into a single DB2 subsystem. Two different methods are developed, each of them addressing different needs. For small-to-medium SAP systems where high availability is not a requirement, we explain how to use SAP tools. For large systems, where the down time needed by SAP standard procedures is not acceptable, we document a technique to merge SAP components without moving the data. We also provide a cloning procedure using the Control Center. We show how to clone one component out of an MCOD landscape. We address the backup and recovery implications in an MCOD environment, to help database administrators plan accordingly. We also describe how to set up and use the Computer Center Management System (CCMS) in an MCOD landscape. Please note that the additional material referenced in the text is not available from IBM. 410 0$aIBM redbooks. 606 $aIBM computers$xProgramming 606 $aBusiness$xComputer programs 606 $aComputer systems$xEvaluation 615 0$aIBM computers$xProgramming. 615 0$aBusiness$xComputer programs. 615 0$aComputer systems$xEvaluation. 676 $a650/.0285/53769 702 $aDubois$b Florence$4aut 712 02$aInternational Business Machines Corporation.$bInternational Technical Support Organization. 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910783105003321 996 $aSAP on DB2 Universal Database for OS$93782480 997 $aUNINA