🚀 go-pugleaf

In article <1994Jun8.062217.3605@lugb.latrobe.edu.au>, ccvj@misty.latrobe.edu.au (Vicki Jordan) writes:
=
=After the upgrade to VMS 6.1 resulted in terminal server ports not being
=disconnected, I moved some queues (mainly WordPerfect 5.1 use) to lpd
=queues from lat queues.  In this output, the queue TEX$DESKJET points to
=the same queue on another VMS system.   For say 80% of jobs, there is no
=problem, but occasionally a job shows up as follows.  
=How/where do I start looking for the cause? The queues are integrated.
=
=Any help would be appreciated :-(
=-------------
=Printer queue WPCB$PTR_MAIN_02, idle, on LUST1::, mounted form DEFAULT
=  /BASE_PRIORITY=4 /CHAR=(127) /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM] 
=  /PROCESSOR=WPCORP_PTR51_BACKGROUND_SMB 
=  /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR
=
=  Entry  Jobname         Username     Blocks  Status
=  -----  -------         --------     ------  ------
=    373  NONAME          CHSCND         1025  Retained on error
=       %PSM-E-CLOSEIN, error closing !AS as input
=       -RMS-F-COD, invalid or unsupported type field in XAB at !XL
=       -VAX-F-NOMSG, Message number 001364EC
=         Submitted  8-JUN-1994 14:12 /CHAR=(127) /FORM=DEFAULT 
=         /NOTE="{WPCORP PTR51 NOTE} Destination_Queue:TEX$DESKJET, 
=         Destination_Form:LN03_A4, Output_Type:7, Output_Flags:33620152, O
=         /NOTIFY /PRIORITY=100
=         File: _LUSTA$DKB100:[WPCORP.PTR051]HPDESPLU.PRS;2 /NOBURST /NOFLAG 
=         /SETUP=({WPCORP PTR51 PRS}) /NOTRAILER
=         File: _LUSTA$DKB100:[WPCORP.PTR051]WPCORP_PTR51_DRS.DRS;1 /NOBURST 
=         /NOFLAG /SETUP=({WPCORP PTR51 EXT 1/1}) /NOTRAILER
=         File: _LUSTA$DKB100:[CHSCND]NONAME.WP51_8JUN94_14121716;1 /DELETE 
=        /NOFLAG 
=        /SETUP=({WPCORP PTR51 DOC} Binding:0, Byte:0, Range:(0:9), Text:High, 
=        Graphics:Medium, No_Alt, Notify, Noendnotes, Copi
=             /NOTRAILER
=         Completed  8-JUN-1994 16:01 on queue WPCB$PTR_MAIN_02

OK, the first question is:  Was anything actually printed?  If so, then the
file that wasn't closed properly was, presumably, the last one printed.  Now,
as to the error message:
=       %PSM-E-CLOSEIN, error closing !AS as input

From the System Messages manual:

  CLOSEIN

    error closing input file

       Facility: Shared by several facilities

       Explanation: During a VMS RMS operation, an error is encountered
       while closing an input file. This message is usually accompanied
       by a VMS RMS message indicating the reason for the failure.

       User Action: Take corrective action based on the associated
       message.

OK, so we now look at the RMS message:

=       -RMS-F-COD, invalid or unsupported type field in XAB at !XL

  COD

    invalid or unsupported type field in XAB at 'address'

       Facility: RMS, VMS Record Management Services

       Explanation: The XAB at the indicated address contains an invalid
       type code field, or the XAB is not valid.

       User Action: The status value (STV) field of the FAB provides the
       address of the XAB in error. Verify that the call to the VMS RMS
       service is coded correctly.

OK, so there's an extended attributes block with a bad XAB$B_COD field.  Now,
it's not clear to me why the symbiont would want to use a XAB in the first
place, and without having access to the symbiont via the debugger, I don't see
how you're going to find out where the XAB in question is, or how it's set up
wrong.

=       -VAX-F-NOMSG, Message number 001364EC

And this message isn't terribly helpful, either :-(.  Sorry I couldn't've been
of more help to you.  But by checking what if anything was printed, and
comparing, say, any setup modules and so forth used by the jobs that fail in
this manner, you might be able to figure out exactly what input file isn't
being closed properly.  You might even be able to reproduce the problem on
demand, at which time contacting CSC would seem a good idea (assuming that
nobody here has already gone through the process).
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL

Disclaimer:  Hey, I understand VAXen and VMS.  That's what I get paid for.  My
understanding of astronomy is purely at the amateur level (or below).  So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it.  If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.