Messages
The messages library consolidates all BMC messages from the following product lines:
| Enter message ID or message text to locate your message:
|
Tip
To search for a message ID, use one of the following options:
| Search type | Valid example | Invalid example |
| Enter the entire message ID. | BMCACM0101I | ACM0101 |
| Enter an asterisk wildcard at the end of a partial message ID. | BMCACM* | *ACM or *ACM* |
| Enter a wildcard combination at the beginning ( /.* ) and end ( .*/ ) of a partial message ID. | /.*ACM01.*/ /.*ACM0101I.*/ | /.*ACM0101I |
You can access the complete set of messages from the
Message library
.
Performance-related messages
The following performance-related messages are written to the SYSPRINT data set.
You can use these messages to monitor the performance of the COPY process as well as to fine-tune future BMC AMI Copy runs.
| BMC30012 | Shows the elapsed time for each phase of BMC AMI Copy. |
|---|---|
| BMC30521 | Shows the number of pages copied to each of the output data set(s). Since the copy process is I/O bound, a full image copy with no changed pages should require an elapsed time that is roughly proportional to this number. Copying a table space with twice the number of pages should take about twice as long if all other factors are equal. However, when changed pages exist and the RESETMOD parameter is set to YES, estimating the runtime based on the number of pages becomes more complicated because BMC AMI Copy must update each space map to clear all of the modified page indicators. |
| BMC30522 | Shows the number of pages changed since the last time the modified-page indicators were reset. The number of changed pages affects performance when RESETMOD is YES, because BMC AMI Copy must update each space map to clear all of the modified page indicators. |
| BMC30594 | Warns that the output data set on DASD is not allocated in cylinder units. The I/O to this data set will be less efficient and will require many more EXCPs than if the data set were allocated with cylinder units. Consider reallocating the data set using cylinder allocation units. |
| BMC30591 | Is issued when MSGLEVEL(1) is specified as an BMC AMI Copy utility parameter and shows the number of times BMC AMI Copy waited for I/O to complete. If I/O operations were in progress for both reading the table space and writing the output data sets, the wait is termed an overlapped wait. If a read to the table space is counted as a read wait, writes to an output data set are counted as a write wait. You can use this information to determine if the performance of your run is balanced or if it is limited by the accesses to the table space (high read wait count) or by accesses to the output data sets (high write wait count). An imbalance occurs if the difference in the number of overlapped waits and the smaller of the number of read or number of write waits is more than 10%. Analyze the I/O channels causing the imbalance and consider moving the table spaces or output data sets to a channel with less contention. |
| BMC47499 | Is issued when page checking is performed because either the CHECKTSLEVEL 1 or 2 option was specified with BMC AMI Copy or the CHECKLVL=1 or 2 installation option was in effect. Additional CPU time was used to perform these checks. |
Comments
Log in or register to comment.