Universe : Rules for Phantom processes

Simon

unread,

Nov 21, 2003, 11:41:14 PM11/21/03

to

Are there limitations for a program running as a Phantom ?
I know that there can be no INPUT statements.
Are there any others ?

Can one use CRT statements or only PRINT statements?
Can the program being called contain INLUCDE INCBS etc ?
Can the program being called contain comments ? eg 0001: * This is my
prog

I have a process that I'm calling with PHANTOM RUN USER-BS CONFIRM but
there is no evidence of the 'phantom' starting when doing a LISTU from
TCL.
When editing the &PH& file(s) created, there's no entry in any of the
file(s), though they show 0001: ( but an empty entry).

Allen Egerton

unread,

Nov 22, 2003, 8:54:21 AM11/22/03

to

On 21 Nov 2003 20:41:14 -0800,
simon...@salmat.com.au (Simon) wrote:

You can use INPUT statements. But you'd have to include them as DATA
statements in a VOC (or VOCLIB) Paragraph and phantom the VOC item.

In that same vein, you have to watch out for full screen displays that
would cause the prompt "Press [NL} to continue", and thus cause the
phantom to wait indefinitely for input. If there's a chance that
that's occurring, add "DUMMY = @(0,0)" as a line of code to disable
pagination.

There are no limitations on comments, include files, or CRT
statements. The only differences between a phantom and a terminal
session are the input and output source and destination.

--
Allen Egerton
aege...@99main.com

rg

unread,

Nov 22, 2003, 10:10:56 AM11/22/03

to

"Allen Egerton" <aege...@99main.com> wrote in message
news:6bqurv04t4lldlbmg...@4ax.com...

Main thing to remember. For every Input statement, you must provide the
information. Think of the process as running on a terminal without anybody
being allowed to hit enter. If the job can run unsupervised, then it can
run in phantom.

You might want to keep the CRT/DISPLAY/Screen only PRINTs to a minimum. The
&PH& log can get very large.

Roger

iJah

unread,

Nov 23, 2003, 11:35:11 AM11/23/03

to

On 21 Nov 2003 20:41:14 -0800, simon...@salmat.com.au (Simon)
wrote:

>Are there limitations for a program running as a Phantom ?

you can do anything at all in a phantom that you can do in a regular
program, except of course get input from a user/keyboard. there are no
limitations.

one common problem you might run into:

if you have a login proc that does anything like send users into a
menu when they login - if it does anything that requires user input,
then you need to bypass that if the process is a phantom. a way to do
this would be to write little basic program with one line:

IF OCONV(@TTY,'MCU')='PHANTOM' THEN ABORT

and place the program strategically in the login proc.

to check and see if your test program is actually running, just have
it print something to the printer - PRINTER ON ; PRINT 'HELLO' that
will tell you.

rg

unread,

Nov 23, 2003, 11:38:34 PM11/23/03

to

"iJah" <ijahSp...@mindspring.com> wrote in message
news:93o1sv4hn4ahom28n...@4ax.com...

Don't forget, if you do the PRINTER ON, PRINT 'HELLO', then do PRINTER
CLOSE, otherwise there is no output until the program ends.

Roger

Angelo Collazo

unread,

Nov 25, 2003, 12:02:29 PM11/25/03

to

"rg" <rglenfl...@optonline.net> wrote in message news:<eXfwb.23116$Hb.82...@news4.srv.hcvlny.cv.net>...

Roger, If you would like to caoture output then you cana do the following:
ED VOC TEST
001 PA
002 COMO ON
003 PHANTOM RUN PROGFILE PROGRAM
004 COMO OFF
005 LIST &COMO&

Hope this helps,
Angelo