Conference vaxaxp::vmsnotes

102.0. "QUEUE/RETAIN and 3270 queues..." by VAXRIO::MAURO () Wed Jan 29 1997 08:00

Hi,

I have looked through the VMSNOTES (since _v10) but was unable to find
anything perninent. Also, I'm not sure if it's a VMS problem, since
it involves 3270 symbiont, but I decided to start from here.

There are in the customer site lot of 3270 Services print queue. He noted 
that when he prints jobs that returns the %R3270-E-SYMBERR error and the
que is set to /RETAIN=ERROR nothing is retained in the queue. If you
set the queue /RETAIN=ALL the job is retained in the que but no 
error message is associated to it. It seems that job was completed
without error, even with the error status displayed, as you can see
below.

I looked for some informations in the 3270 log files (R3270$SYMBIONT.LOG) 
and no log entries exists there, about the error.

The matter is that if the user prints a job and it doesn't works and
he doesn't see the message displayed, he is not able to get the
error message from the queue, even if it set /RETAIN=ALL.

Any tip will be very welcome.

Thanks, Mauro.

-----------------------------------------------------------------------

FIELD>sh que/full n05r371$print
Server queue N05R371$PRINT, idle, on CEFBR1::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]
  /PROCESSOR=R3270$SYMBIONT /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR
FIELD>print/que=N05R371$PRINT ana1.lis
Job ANA1 (queue N05R371$PRINT, entry 428) started on N05R371$PRINT
FIELD>

Job ANA1 (queue N05R371$PRINT, entry 428) terminated with error status
%R3270-E-SYMBERR, internal error in symbiont
FIELD>

Job ANA1 (queue N05R371$PRINT, entry 428) completed
FIELD>sh que/full n05r371$print
Server queue N05R371$PRINT, idle, on CEFBR1::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]
  /PROCESSOR=R3270$SYMBIONT /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN=ERROR
FIELD>set que/retain=all   n05r371$print
FIELD>sh que/full n05r371$print
Server queue N05R371$PRINT, idle, on CEFBR1::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]
  /PROCESSOR=R3270$SYMBIONT /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN
FIELD>print/que=N05R371$PRINT ana1.lis
Job ANA1 (queue N05R371$PRINT, entry 429) started on N05R371$PRINT
FIELD>

Job ANA1 (queue N05R371$PRINT, entry 429) terminated with error status
%R3270-E-SYMBERR, internal error in symbiont
FIELD>

Job ANA1 (queue N05R371$PRINT, entry 429) completed
FIELD>sh que/full n05r371$print
Server queue N05R371$PRINT, idle, on CEFBR1::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]
  /PROCESSOR=R3270$SYMBIONT /PROTECTION=(S:M,O:D,G:R,W:S) /RETAIN

  Entry  Jobname         Username     Blocks  Status
  -----  -------         --------     ------  ------
    429  ANA1            FIELD             1  Retained on completion
         Submitted 29-JAN-1997 10:42:49.74 /FORM=DEFAULT /NOTIFY /PRIORITY=100
         File: _R5A1IE$DIA1:[SYS0.SYSMAINT]ANA1.LIS;1
         Completed 29-JAN-1997 10:42:49.99 on queue N05R371$PRINT

    

>%R3270-E-SYMBERR, internal error in symbiont

If the symbiont dies this way then all bets are off. Who created that
symbiont? If it's a DIGITAL product then escalate it.

Jur.

    .1
    
    The symbiont R3270$symbiont, I supose, comes with SNAPRE v1.2. I'll	
    check with this software support people if they known the problem. However,
    I would like to understand why the message "JOB X terminated with error
    status" doesn't causes the job retention in the queue? Which queue
    manager module decides what situation should to retain a job with 
    error status in the queue? Does the next message "Job X completed" avoid
    the job retention in the queue?
    
    Mauro.

    P.S.: The problem happens with any type of error status in these type
    of queue. The customer, at least in the beginning, doesn't care about 
    the message code. He wants to have the message logged/recorded in some 
    place, to later start the problem troubleshooting.

    I also posted this problem in SNAGWY conference.