Technical data

Setting Up and Maintaining Queues
14.8 Solving Queue Problems
2. Enter the SHOW LOGICAL/FULL SMBSRVSHR command to determine
whether the logical name SMBSRVSHR is assigned, and, if it is assigned,
its access mode (SUPERVISOR_MODE or EXECUTIVE_MODE). In most
cases, this logical name should not be defined. However, if SMBSRVSHR is
assigned, deassign it by entering the DEASSIGN SMBSRVSHR command
with the /USER_MODE, /SUPERVISOR_MODE, or /EXECUTIVE_MODE
qualifier.
3. If a print request returns a fatal error or does not print, perform the following
steps:
a. Stop the queue by entering STOP/QUEUE/RESET.
b. If the output device is spooled, despool it using the SET
DEVICE/NOSPOOLED command.
c. Copy the file you are attempting to print by entering the COPY command
in the following format:
COPY input-filespec output-filespec
If the COPY command does not produce output, a PRINT request will not
work.
4. If the problem is on a queue using the LATSYM symbiont, try using the
default symbiont, PRTSMB, and see if the problem persists. You can use the
PRTSMB symbiont for printers on LAT ports. However, only one queue at a
time will be able to send jobs to the printer.
To determine whether a queue is using the LATSYM symbiont, enter SHOW
QUEUE/FULL. If the queue is using the LATSYM symbiont, the display
shows the following words: /PROCESSOR=LATSYM.
To change the queue’s symbiont to PRTSMB, perform the following steps:
a. Stop the queue by entering STOP/QUEUE/RESET.
b. Restart the queue by entering START/QUEUE/NOPROCESSOR.
If a PRINT request succeeds when the queue is using PRTSMB, the problem
is with LATSYM or with the LAT driver LTDRIVER.
5. Attach a terminal at the end of the cable that is being used for the printer.
If the data shows up on the terminal, the Hold Screen key works, and no
data is lost, the problem is probably with the printer (an incorrect setting, for
example). If the problem exists with the terminal, it might be caused by the
cable, the hardware interface port, or a hardware port setting.
14.8.2 Making Pending Jobs Eligible for Scheduling
If a job does not execute when expected, the job might have a pending or holding
status. The SHOW QUEUE/FULL/ALL_JOBS command displays the status for
all jobs on a queue.
If the job is in a holding status, see Section 14.7.2.3 for information about holding
and releasing a job.
If the job is in the pending state, the /FULL qualifier enables you to see the
reason why the job is ineligible to execute. (Use a 132-character wide display to
make sure that all the information is displayed.)
Setting Up and Maintaining Queues 14–71