Avaya Definity SI, Maintenance Manual, Page: 257 / 2968

busyout journal-printer
Issue 4 May 2002 8-7 555-233-123
Field descriptions
busyout journal-printer
This command places the maintenance object associated with a specified
pms-log or wakeup-log link in a maintenance busy state. No periodic or scheduled
tests are performed on the busied out maintenance object until it is released. Also,
no activity occurs over the links (for example, no data is transferred to the printer)
and the link drops. Warning alarms are generated (Error type 18) on each busied
out maintenance object, so that INADS can access object status. The release
journal-printer command will return the object to operation.
A link is comprised of several components: a far-end data module, a simulated
data channel on a PKTINT board, a manager that initiates and maintains the link,
and a controller/protocol that services the link. A controller/protocol is usually a
transient process that exists for as long as the link is up. A link is considered up if
a physical connection is established. A link can be considered to be up while no
useful work can be performed over it, in this case the link is insane and should be
torn down. These links provide asynchronous data connections from the switch to
peripherals.
For general information on journal printer links, see ‘‘busyout pms-link’’ .
For information on what a journal printer is and does, see ‘‘status journal-link’’ .
Port
Port address (cabinet-carrier-slot-circuit) or the data channel
number
Maintenance
Name
The name of maintenance object
Alt. Name
Alternate way to identify maintenance objects.
If the Object is The field contains
station extension
trunk xxx/yyy (xxx = trunk group, yyy = member
private CO line P/xxx (xxx = private CO line group number)
Result
Test result: Pass, Abort, or Fail
Error Code
Numeric code explaining why the release failed or aborted. Refer to
the detailed list of the codes by test number for each MO.