|
|
|
|
| LEADER |
02085nmm a2200457 u 4500 |
| 001 |
EB001926917 |
| 003 |
EBX01000000000000001089819 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 050 |
|
4 |
|a QA76.5
|
| 100 |
1 |
|
|a Lascu, Octavian
|
| 245 |
0 |
0 |
|a Introducing IBM Z System Recovery Boost
|c Octavian Lascu, Paul Schouten, Kazuhiro Nakajima
|
| 246 |
3 |
1 |
|a Introducing International Business Machines Z System Recovery Boost
|
| 260 |
|
|
|a [Tucson, Arizona]
|b IBM Corporation, IBM Redbooks
|c 2020
|
| 300 |
|
|
|a 1 volume
|b illustrations
|
| 653 |
|
|
|a Technologie de l'information / Gestion
|
| 653 |
|
|
|a Computer firmware / fast
|
| 653 |
|
|
|a Information technology / Management / fast
|
| 653 |
|
|
|a Computer systems / Reliability / fast
|
| 653 |
|
|
|a Microprogrammes
|
| 653 |
|
|
|a Ingénierie des systèmes
|
| 653 |
|
|
|a Systems engineering / http://id.loc.gov/authorities/subjects/sh85131750
|
| 653 |
|
|
|a Computer systems / Reliability
|
| 653 |
|
|
|a Systems engineering / fast
|
| 653 |
|
|
|a Computer firmware / http://id.loc.gov/authorities/subjects/sh88000353
|
| 653 |
|
|
|a Information technology / Management / http://id.loc.gov/authorities/subjects/sh2008006980
|
| 653 |
|
|
|a Systèmes informatiques / Fiabilité
|
| 653 |
|
|
|a systems engineering / aat
|
| 700 |
1 |
|
|a Schouten, Paul
|e author
|
| 700 |
1 |
|
|a Nakajima, Kazuhiro
|e author
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 490 |
0 |
|
|a IBM Redpaper
|
| 500 |
|
|
|a Date of publication from resource description page (Safari, viewed September 22, 2020). - Number on back cover: REDP-5563-00
|
| 776 |
|
|
|z 073845799X
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9780738459202/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 658
|
| 082 |
0 |
|
|a 000
|
| 082 |
0 |
|
|a 620
|
| 520 |
|
|
|a In this IBM® Redpaper publication, we introduce System Recovery Boost, which is a new function of the IBM z15™. System Recovery Boost delivers substantially faster system shutdown, restart, and catching up with accumulated backlog of work after a restart
|