The line command <linecmd> is invalid because no logical paths exist to device <devname>.
The line command <linecmd> is invalid because the volume <volser> is permanently resident.
The line command <linecmd> is invalid when the unit has a status of <status>.
The line command <linecmd> is invalid for the device type <type>. Make sure that you want to perform the line command <linecmd> against the device type <type>.
The line command <linecmd> is invalid when no volume is mounted.
The line command <linecmd> lacks a volume serial number. Specify a volume serial number and issue the line command again.
The volume serial number is invalid because it contains embedded blanks. Remove the embedded blanks and issue the command again.
A usage parameter is required with the line command <linecmd>. Enter a usage parameter with the line command.
The highlighted usage keyword is invalid. Valid keywords are PRIVATE, PUBLIC, and STORAGE. Change the usage parameter and issue the command again.
The SAM line command (Start Activity Monitor) was issued for a volser where it had already been started.
The SAM line command (Start Activity Monitor) could not be completed because the activity monitor table is full. You must use the PAM line command (stoP Activity Monitor) on some other volser where it is active before the SAM line command can be issued for a new volume.
The PAM (stoP Actvity Monitor) or RAM (Refresh Activity Monitor) line command was issued for a volser where it had never been started.
Informational only.
Informational only.
|
Copyright © 2013 CA.
All rights reserved.
|
|