 |
» |
|
|
|
This section describes the steps necessary to initially configure the dump-to-disk feature, using the BLDDUMP utility. You should have already defined your protection scheme and alternate dump device strategy. | | | |  | NOTE: Before proceeding with this section, read each of the steps and become familiar with the BLDDUMP commands BUILD and TAPE. Both commands are described in detail later in this chapter. | | | | |
The steps below describe how to create two new dump files, DUMP1 and DUMP2, on a two-volume nonsystem volume set called DISKDUMP_VOLUME_SET. The sample system supports 50 terminals during peak operating times. Main memory size is 96 megabytes. For more detailed information about BLDDUMP commands and features, refer to "Managing the Dump-to-Disk and Mini-Dump Features," later in this chapter. To configure the dump files, follow these steps: Log on as MANAGER.SYS. At the system prompt, enter:
:HELLO MANAGER [/userpass].SYS[/acctpass]
|
Invoke the BLDDUMP utility. At the system prompt, enter:
:RUN BLDDUMP.HP36375.TELESUP
|
Use the BUILD command to build a dump file, using the file size and protection scheme that you have already defined. At the BLDDUMP prompt, enter:
(#1) blddump > BUILD fileid file size protection
|
where: - fileid
The name of the dump file that you want to create. The fileid parameter can be up to five alphanumeric characters in length and must begin with an alpha character. The BLDDUMP utility appends the characters "MEM" to the fileid. For example, DUMP1 becomes DUMP1MEM.
- file size
The size, in megabytes, of the dump file. - protection
Indicates whether or not a dump file is protected from overwrites. If Y[es] is specified, the dump file is protected from overwrites by subsequent dumps to disk, if it contains dump information. If N[o] is specified, subsequent dumps to disk can write new dump data to the file, deleting any existing data. The YES option is the default.
If you want two or more dump files, use the BUILD command to create them. Use the TAPE command to specify your alternate dump device strategy. At the BLDDUMP prompt, enter:
(#2) blddump > TAPE dump_strategy
|
where: - dump_strategy
If Y[es] is specified, the dump facility initiates dump-to-tape if dump-to-disk is unsuccessful. If N[o] is specified, the dump facility terminates immediately if dump-to-disk is unsuccessful. If neither is specified, TAPE defaults to YES.
Use the LIST command to display the current state of the dump-to-disk feature: LIST displays information about the dump files that you just created and the dump strategy. Use the EXIT command to exit BLDDUMP. At the BLDDUMP prompt, enter: When you exit BLDDUMP, invoke both VSCLOSE and VSOPEN against the nonsystem volume set. This is necessary because you used the BUILD command, and it ensures posting of directory information. You must enter VSCLOSE and VSOPEN at the console. At the system prompt, enter:
:VSCLOSE DISKDUMP_VOLUME_SET
:VSOPEN DISKDUMP_VOLUME_SET
|
|
