HP3000-L Archives

November 1998, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Lane Rollins <[log in to unmask]>
Reply To:
Lane Rollins <[log in to unmask]>
Date:
Mon, 9 Nov 1998 09:58:14 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (88 lines)
>This message was sent to the following destinations:
>  1 HPLIST@INTERNET
>   [log in to unmask]
>  2 POWERH@INTERNET
>   [log in to unmask]
>______________________________________________________________________________
>I'm scratching my head on this (which usually means I'm missing something
>simple), and am looking for any suggestions.
>
>We are upgrading from Powerhouse 6.09 to 7.29C8 on an HP3000, and from QDD to
>PDL as the dictionary (all as part of the Y2K project here).
>
>Under 6.09, we had built a short 'compile' job to let us recompile the
>production dictionary at times when users weren't on.  I simply changed that
>job to compile the PDL. The problems I'm experiencing is: when the EXIT
>statement is processed, the job not only quits the PDL program, but ends. The
>whole job! It just ends!! All statements that follow the PDL statement do not
>get executed.
>
>I have isolated the problem to the EXIT command by commenting out everything
>else. I also tried using QUIT instead of EXIT...same result.  Below I've
>reproduced the job, and the $STDLIST produced by the job.
>
>If I comment out (or remove) the EXIT, the MPE commands are executed inside of
>PDL...until the EOJ is reached, which generates a 'COMMAND NOT PROGRAMATICALLY
>whatever' message (after which the job ends for lack of further commands).
>
>This is not a show stopper...I can recompile the PDL interactively, and the
>PDL compiles successfully in the job. I just can't execute anything after it.
>
>The job is:
>!JOB PPIPDL,{HPUSER}.PROD2000,PUB;OUTCLASS={PROGPDEV},1
>!CONTINUE
>!PDL
>; USE PPIPDL.PDLSRC.TEST2000 NOL
>
>EXIT
>!
>!LISTF @.PRINTMD
>!
>!CONTINUE
>!SAVE PPIPDL.PRINTMD
>!JTF S{hpjobnum},'Job finished.'
>!TELLOP #################### PPIPDL END OF JOB  #################
>!EOJ
>
>NOTE: the blank line before EXIT makes no difference. Tried it with and
>without.
>
>The $STDLIST is:
> JOB PPIPDL,STEVE.PROD2000,PUB.
> Priority = DS; HIPRI; Time = UNLIMITED seconds.
> Job number = #j3884.
> MON, NOV  9, 1998, 10:21 AM.
> HP3000  Release: C.55.00   User Version: C.55.00
> MPE/iX  HP31900 C.05.08  Copyright Hewlett-Packard 1987.
> All rights reserved.
> STREAMED BY STEVE.TEST2000 (#S6612) ON LDEV# 13
>    STREAM DATE:   MON, NOV  9, 1998, 10:21 AM
> JOB OK TO PROCESS
> :COMMENT   STREAM FILE PPIPDL.PDLJOBC.TEST2000
> :COMMENT     STREAMED BY STEVE.TEST2000,STEVE ON LDEV 13
> :COMMENT     RUNNING PROGRAM MAIN.PUB.VESOFT
> :COMMENT     ON MON, NOV 09, 1998, 10:21 AM
> :CONTINUE
> :PDL
>
> P D L   (7.29.C8)      Level 999
>(24/36) Continue?
> Copyright 1997 COGNOS INCORPORATED
>
> > ; USE PPIPDL.PDLSRC.TEST2000 NOL
> >
> > EXIT
>
>
> END OF PROGRAM
> CPU sec. = 1.  elapsed min. = 1.  MON, NOV  9, 1998, 10:21 AM.
>
>Thoughts, suggestions and wild guesses from the collective wisdom gladly
>accepted.

Try putting an !EOD after the exit. If the program is written in C it will
pre-fetch data from the job stream. Usually it's only one line, but they
might be using son processes that would cause this. The !EOD should stop it.

-Lane

ATOM RSS1 RSS2