https://community.hpe.com/t5/operating-system-hp-ux/printer-queue-disable-automatically/m-p/2656786#M47367 I have some print queues in HP-UX 10.20 which automatically disabled by lp scheduler if the request files generated in the following format.<BR />e.g.<BR />The control file is "cA123host1" ,data file name stored in it is "dA0123host1" and data file name is "dA0123host1". It seem to be normal in others machine, but in this machine, if the control file name and data file name do not have the same number of digits in seq#, this print queue will disable automatically. Fri, 01 Feb 2002 02:17:05 GMT Anthony Yau 2002-02-01T02:17:05Z https://community.hpe.com/t5/operating-system-hp-ux/printer-queue-disable-automatically/m-p/2656786#M47367 I have some print queues in HP-UX 10.20 which automatically disabled by lp scheduler if the request files generated in the following format.<BR />e.g.<BR />The control file is "cA123host1" ,data file name stored in it is "dA0123host1" and data file name is "dA0123host1". It seem to be normal in others machine, but in this machine, if the control file name and data file name do not have the same number of digits in seq#, this print queue will disable automatically. Fri, 01 Feb 2002 02:17:05 GMT https://community.hpe.com/t5/operating-system-hp-ux/printer-queue-disable-automatically/m-p/2656786#M47367 Anthony Yau 2002-02-01T02:17:05Z https://community.hpe.com/t5/operating-system-hp-ux/printer-queue-disable-automatically/m-p/2656787#M47368 This is the correct behavior. BSD remote printing defines 4-digit print IDs while SysV (HP-UX in particular) defines 5-digits. So the control file internal ID number must match the file names. A similar situation will exist if random filenames and control files are simply stored in the request directories. Fri, 01 Feb 2002 04:41:50 GMT https://community.hpe.com/t5/operating-system-hp-ux/printer-queue-disable-automatically/m-p/2656787#M47368 Bill Hassell 2002-02-01T04:41:50Z